Prolific Usb Serial Cable Driver Vista
Berry Spitsberg
The USB serial converter cable required USB driver, available from prolific website ( -usb-serial-uart-bridge-controller/), which are used to make the PL2303TA on the PCB board appear as virtual COM port (VCP driver). It allows users to communicate with the USB interface via a standard PC serial emulation port.
So I did something stupid and I would like the communities anecdotal feedback on this. I have the Celestron RS232 cable and have been successfully been using it for a year or so with a trendnet TU-S9 SerialRS232 adapter. I have been running W10 the entirety of this time. The other day, I attempted to run a second, older iOptron mount. Turns out iOptron uses different pinouts and I needed a different cable however that's not the issue. During the attempt I installed a different Prolific driver which has effectively severed the capability for my W10 laptop to connect to the CGEM-DX mount. When I connect the CGEM, it is given a com port designation however the Celestron Telescope driver doesn't see it when it scrapes ports. The dropdown just remains blank. I've uninstalled all the drivers and re-installed the TU-S9 specific driver and have yet to be able to restore connection to the CGEM. I've done a system restore. I've used three or four different third party tools to clean out residual configs and drivers...to no avail. I ended up calling it a night in failure. I am an engineer and am at my wits end for the first time in forever with this hobby. I ordered a new FTDI cable that should be more compatible but I dont like that I left the room in failure and it will be a day or so until that solution arrives. Have you run across this before? Did I miss anything?
Update. The official iOptron all in one cable came today and upon connecting that. Again, I see a com port register but iOptron Commander cannot see the mount. Gotta be a windows/driver issue at this point. I can't see how I would go about fully cleaning out old drivers better than I already have however. This should not be this difficult.
However, programming a Baofeng radio from a computer isn't all that intuitive and can become messy even for the most experienced ham who is not used to Chinese-made radios. The USB cable driver offered by Baofeng is buggy and the programming software made by the manufacturer is, for all intents and purposes, junk.
2. Locate the correct USB programming driver for your operating system. You can download the Prolific driver for Windows, Mac and Linux at _Drivers.php. If you purchased the Baofeng UV Series USB Programming Cable from Buy Two Way Radios, the driver for Windows will be on the CD included with the cable in the USB Cable Driver folder. Insert the CD and go to USB Cable Driver > USB Cable Driver Prolific 3.2.0.0.exe. This is the correct driver.
Hi, I recently had the driver issue with a Prolific USB to serial cable on windows 10, this website proved to be very informative -usb-to-serial-fix-official-solution-to-code-10-error Apparently the info there is sourced from I hope this heIps
This driver is for the SBT-USC6K USB to Serial cable (CSI Part# 17394 - Silver Cable). Support is for Windows XP/Vista/7. This driver is not compatible with Windows 8 and above or the SC-USB Interface.
Several years back I had a problem with a prolific converter and windows vista. 10-20minutes would cause a BSOD and the crash log traced it wown to the driver dll. I replaced the converter and all went away.
Description
Maximum Compatibility
Connect to any Serial / RS232 device that you want to connect to the USB port of your computer. We proudly boast about our 100% device compatibility ratio with this product! Who currently uses this product?
We have sold this USB to Serial Adapter Cable mainly colleges, Audio / Visual Centers, as well as some Audio / Visual manufacturers. This cable will integrate flawlessly with all of the serial applications available. Other brands of USB to Serial Adapters that are comparable in quality, compatibility and reliability, such as Keyspan's are being sold by many audio visual manufacturers for at least $40-$50. Compatible with all Serial PDA's
This is also compatible with all PDA cradles or cables that use a serial connector.
Easy SetupS232
Setup is quick and easy. Just plug it in, pop in the driver disk, and be done within a minute or two. USB to RS232
What's included
If your programming cable has a Prolific type USB-to-Serial chip inside, you not only have to install the Prolific v3.2.0.0 device driver, you have to go into Device Manager and select that specific driver. As you can see from the picture that I have attached, I have several Prolific device driver versions installed in my computer for testing. I keep the v3.2.0.0 device driver selected for daily use. Instructions for installing and selecting the driver are "here": _Drivers.php.
I agree that chirp is not the problem and may be a good program, however, I have been doing a lot of reading and see there is an issue with Prolific 3.2.0.0 not compatible with Windows 10, the driver is actually for vista. When I did a compatibility check Widows stated it is only for Vista.
In my opinion it is possible there is a possibility of a problem with the chip set in the cable, why would I have the same problem with windows 8.
Problem is, I have spent an entire day screwing with this thing. I will return the cable and buy RT systems cable and program, why?, so far I have no confidence in the package that is offered by Baofeng. If I have issues with the RT system they won't be able to say it is CHIRP if I by both the cable and program.
I suspect it is mostly the cable and the the current version of prolific, but as you can see, no one on the other end of this message wants to say buy a different cable set. By The Way, the radio works great, manual programing is not fun.
be well
James, the only way to get around this is to buy a good cable. Cheap cables usually contain fake chips, cloned from Prolific; Prolific drivers recognize the counterfeit and inject garbage. Go with cables using genuine FTDI or Prolific chips, and avoid cheap ones (these often come with counterfeits - if a cable is less than $25, don't trust it). RTsystems can be problematic because they often use proprietary chips which can only be supported by RTsystems software. These cables may or may not work with Chirp.
aa06259810