Although my working IoGear GUC232A adapter obviously has a different VID/PID, it uses the Linux 'pl2303' kernel module, so I strongly suspect that your adapter will work.csete wrote:The controller on the USB/serial Cable is a Prolific PL2303 (0x067b:0x2303). Any idea if this is a cable that will work?
This sounds to me like you built what's currently called the "JP1.1" design but left off the extra parts (Q1, R1, and D1) that would have been needed to actually use it with an ancient JP1.1 remote control. In essence, this would be a JP1.2/JP1.3 interface but with the DTR line controlling the remote's "reset" line, unlike the other 2 designs from Tommy Tyler, both of which use the RTS line to control the reset line.csete wrote:My JP1 cable is an older JP1.x cable. It has 3 transistors and a couple of capacitors. I don't see any capacitors on the newer schematic. I'm planning to rewrite my JP1 cable to match the latest schematics... perhaps tonight.
Personally, I don't think there's any reason to rewire your hardware just yet. I've breadboarded the full JP1.1 interface described above (including Q1, R1, and D1, so I have all 4 transistors and 2 capacitors) and it works fine with my JP1.2 and JP1.3 remote controls (using special software that won't accidentally put a JP1.2 remote into the undesired Background Debug Mode [BDM]).
I think Vicky is correct, but I'm sure you'd both agree that it's wise to make sure that you don't have more than 1 problem (e.g. software and USB/RS-232 adapter) simultaneously.vickyg2003 wrote:Since your remote is downloading, I don't think its an interface problem, I think you have a software issue.
Bill
