Page 1 of 1
Problem with Tommy's USB JP1 cable - correct VID/PID info?
Posted: Sun Feb 15, 2009 3:32 pm
by kwazy
Purchased Tommy's JP1 (eeprom) cable, trying it for the first time today. Unfortunately it doesn't seem to work - keeps listing as "Unknown Device" and not recognizing the Delcom driver inf. When listing details about the unknown device, it lists the Manufacturer as "Standard USB Host Controller" (I expected to see Delcom), and the VID/PID info under the "Device Instance Id" is USB\VID_0000&PID_0000\5&4D757D6&0&1. I suspect a hardware problem at this point, as the above info is consistent between my desktop and my laptop. Can anyone else confirm the Manufacturer and VID/PID info for this cable?
Thanks,
Jeff
Posted: Sun Feb 15, 2009 4:47 pm
by unclemiltie
Mine is VID 0FC5, PID 1222
I suspect that you have a hardware problem, if the VID/PID isn't right the devcie won't install the right software on the USB plug event.
Posted: Sun Feb 15, 2009 5:53 pm
by Tommy Tyler
Jeff,
You caught me with no USB JP1s in stock, so I had to quickly build a couple to check out the problem. I was able to duplicate it with a bad solder joint on the USB connector ground pin. There are four surface mount pins on the connector, and if it isn't completely flat against the board during assembly it's possible for the solder to fail to bridge completely. What's really worse is that it can make contact just enough to pass my tests, and then work loose in shipping and handling. That's why I warrant my stuff for a year.
For your information, each time I lifted pin four of the connector I got the same "Windows can't find it" messages you got, and Device Manager showed USB\VID_0000&PID_0000\5&B114931&0&1. I suppose all Windows saw was the pull-up resistor that tells it a USB device has been plugged in, but with no ground to bring the chip to life there was no chance of completing enumeration.
I'm shipping you a replacement interface tomorrow morning, along with postage for returning the defective unit. Once I confirm your unit failed for this reason I will be able to put additional quality control measures in place.
I'm very sorry for the inconvenience this has caused you. I have learned a valuable lesson, unfortunately at your expense.
Tommy
Posted: Sun Feb 15, 2009 9:17 pm
by kwazy
Tommy - thanks for the fast reply and quick debugging. I did lose a couple hours messing around this afternoon, but I'm happy it seems to be a real problem and not just something I was doing incorrectly. Great support!

Posted: Fri Feb 20, 2009 8:21 am
by kwazy
Hi Tommy - just wanted to follow up and let you know that I received the new cable yesterday and it works as expected. Thanks again for the fast support, and I'm very happy with the build quality of your cable.