![]() ![]() However, to make matters even more annoying, the PL2303 chip, which typically identifies itself as VID 067B and PID 2303, reports PID 0609 in this device, making it impossible to recognize this. HXA, XA, HXD, EA, RA, SA, TA, TB versions). Windows Driver Installer Setup Program(For PL2. I've read the following thread from this forum about being able to reprogram the EEPROM - /thread62529.html - however for adaptor 1 if I leave the eeprom writer program settings as default, change the serial number or the PID and press write, I get an error message 'Compare EEPROM failed!'įollowed by an alert 'Write EEPROM successful!' But it clear isn't as the PID hasn't changed and (although I'm not certain I know where to look for the serial number) the serial number doesn't appear to change either when reviewing device info (nothing seems to change). I've compared the devices in Windows Device Manager, and also with 'lsusb -v' in linux and there's little to distinguish between them. If serial device X is connected to adaptor X and serial device Y connected to adaptor Y, when in linux the kernel can detect an assign these USB devices different device names between reboots. I would like to be able to identify them through software without having to know which adaptor is plugged into which USB bus or whatever. Here's the problem - I have two USB to serial adaptors (identified as using the Prolific PL-2303) which *aren't* identical in appearance but appear the same when detected by OS's. First post here (sorry it's quite a length one). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |