Which would lead me to believe that it's a driver issue with Prolific and 7/64 The Cables to Go adapter is capable of operating under XP32 115200 baud Win7/64 can program it and that it's not a direct OS issue sighĪs a for-kicks-and-grins, I installed the same Cables to Go adapter on an old XP32 laptop I had laying around and of course, it worked without issue. He said he's never found a machine that had Win7/64 on it with a physical COM port for him to test it on. I called the manufacture today, 'we don't support Win7/64', he started backpeddling when I told him it ran fine on my Win7/64 machine that had a physical COM port, so clearly the issue is with the USB adapter. Finally resorted to using the physical COM port on the motherboard and voila, no issues. I installed the Cables to Go adapter on one of my home workstations (Win7/64) and still no dice. After 3 hours dicking around with different versions of drivers for the USB adapters, thinking there was something goofy going on with my laptop, I said screw it and took one of the signs home. The software requires that they talk at 115200, so I have a feeling that is part of the issue (all of my other stuff talks fine at 9600). NONE of my cables will talk to the signs, at all. They're basic two color LED panels that use the manufactures software package to do the programming, over RS232 of course. The RS cable doesn't work at all, the IO Gear is heavily glitchy and the Cables-to-Go version seems to have a pretty decent success, though it has glitches here and there.įast forward to last week, I got two new giant 12' x 84' programmable LED signs.

I have a line of controllers that I program (think along the lines of an industrial PLC) and ever since I switched to Win7/64 I've had issues off and on. Currently, I have 3 different USB>Serial cables an IO Gear GUC232A, a Cables to Go (Prolific PL2302 chipset) and a older Radio Shack cable (with an older Prolific chipset). In my line of work I use serial on a near daily basis.

Best usb serial adapter windows 7