Pl2303 Prolific Driver Installer Windows 10 64 Bit

[Shari Alvine]

azzido no problem, windows 11 always updates drivers if newer cones out if the software don't see the programer it's easy just removed the recent update driver by windows 11 and all will work perfect. The drivers I provide are from the pl2303 maker so the latest for Windows 11 and 10. Regards

For reference, I attache the 2 drivers that work for me to this message. Only one is needed, just that they have different install methods (one is .exe and the other is right click on the INF), if you run the .exe version and you already have another version of the driver it will ask you if you want to uninstall (which I usually do) and then run again the .exe to install the driver.

[See next post]

I bought an Arduino nano clone on ebay. It came with PL2303 instead of FTDI chip. When I plugged it in the usb port, it gets recognized and win 8.1 installed a driver automatically. But the driver can't start.

I can't even find where the pl2303 driver install program unzipped the drivers. A PL2303 driver IS installed after I plugged in the Nano but it shows error messages. The manufacturer specifically says PL2303 HXA is obsolete and has no win8 driver. Have you tried it yourself?

I haven't tried but I have used that way to install some old drivers. I don't think it is a hardware limitation, it might be something like chineses cloned that chip too much that prolific stopped supporting these old versions or something like that.

eried:

I haven't tried but I have used that way to install some old drivers. I don't think it is a hardware limitation, it might be something like chineses cloned that chip too much that prolific stopped supporting these old versions or something like that.

That was in my thoughts too. Make it obsolete. If you have the driver, can you tell me the file name. I just couldn't find where the install program unzipped the driver so I can't specify where to find driver

Not really an argument, when you can't afford to buy everything genuine ... well you just can't _o - pretty much the same thing as saying "another good reason to only buy industrial-grade laser CNC machines / 3D printer / insert really expensive device here".

I will be moving from PC to Mac, but will need to run a Windows application that uses a serial port, using boot camp. Would I be right in thinking I would need to install this adapter under Windows using a Windows driver?

Loaded it all up fine, however my main purpose was that so I can telnet to devices on the serial port.

My question is running the telnet what would I put after the telnet command to identify the port,

Prolific seem to be deliberately isolating compatibility against these devices in the newest Windows drivers, and wondered if thats the same with the mac drivers. Its just not worth wasting time putting in drivers to have to fight them out again when prolific deliberately make them to not work.

Fazed, I would l look baud rate you are using for your device. I just had a similar issue connecting to an APC UPS management interface. if you are using screen try this command: screen /dev/cu.usbserial (Baud Rate). The baud rate is standard 9600 but you can change it by typing in the baud rate you wanna use i.e. 2400.

After following these directions, and the install of the PL2303_1.4.0 appearing to be successful, I do not see the USB serial monitor option anywhere. Whether I look on system preferences under network or in terminal.

I followed the instructions, and got the driver to show in system report, but never in the network control panel. ZTerm worked, showing me that the driver works (and helped as a step), but minicom is the best app for the job- easy to configure, and remotely accessible with terminal. Great site- thanks for the help!

I am using a mac. Wine is a Windows port making it possible to run Windows applications on Mac or Linux. It can use the Mac Hardware such as the adapter and forward it to the Windows application. Nonetheless i found my answer already but thanks anyway

The Problem is OSX10.11 does not allow unsigned kext to be loaded except for a workaround i described to andrius (either its the post down or up to this one) The driver itself is fine and i am using it on 10.11. The problem is the unsigned state. What you guys would have to do to make it work again is to sign the KEXT with apple and provide it in a signed state. Thats all.

By the way. This method works with any unsigned driver!!! If you have a non working USB device check the /System/Library/Extensions path for a .kext file with the name of your device. if you find it there and your device is not working you can be sure its a signature problem. just use the commands i described above and change the filename of the .kext to the filename you need.

Hi Doug,

If you have the Plugable adapter, the latest driver for OS X is properly signed and there is no need to turn off SIP in order to install it. If you are having problems getting it installed, please contact us at sup...@plugable.com and we can help.

David, thanks for the response, I should start at the beginning, I have an older Cables 2 Go USB2Serial cable and my research indicated that the driver I needed was this one. It works on a windows PC but since I use a MAC most of the time I was trying to get it to work. However, I have since ordered a plugable adapter and I think it should be here today and I am sure that will solve my problem. I will keep you posted.

I have developed a code in LabVIEW 2011 to communicate with XY linear stage. It's actually two stages mounted perpendicularly. The setup of the system is that a joystick (made by the same manufacturer as the stage) is connected to the USB port of the computer though a USB to Serial converter. One stage is daisy chanied to the joystick and the other stage is daisy chained to the first stage.

For the purpose of our application, it's required to continuously check the status and position of the X and Y stages. Because the joystick also returns responses when a request sent to all devices, I need to send the requests individually; i.e.. one request per command per device making it total of 4 commands. This takes care of the error received from the joystick. The issue, though, is that after a while either the program freezes or the computer crashes and restarts. It happens about 13 minutes (in average) after the program starts. It also happens even when no move commands are sent to the devices. I have put to 50 ms delays before sending each two commands (position and status) per device. Basically, the app waits for 50 ms before sending two commands to X stage and receiving the response and when all is done with X stage, it waits for another 50 ms to do the same for Y stage. This procedure should goes on until the app is stopped. But as I said, a problem occurs. Now, I am assuming the problem is that the serial port buffer overflows. It's not preferred to increase the delay time, but if it helps resolve the issue, then I have no other option!

AFAIK a buffer overflow should only generate an error at the device level (e.g. OVERRUN). When the computer crashes usually the culprit is the device driver, not the application. I suggest to try with another USB-serial adapter.

Most adapters feature either a FTDI chip or a Prolific chip. Personally I had more problems with Prolific than FTDI. However the performance could also depend not only on the chip but on the specific driver implementation.

Thanks for the reply! Just to give you some more info, I am using Windows 8 Home Edition OS and a Prolific USB-to-Serial converter. The driver for the converter updated and I have a feeling it's when the issue started. I'm not sure if rolling back the driver might help.

I have found recently that multiple Prolific USB to serial converters on the same buss or hub will eventually fail. Even if your computer has four USB ports they could all be on one USN hub internally.

What I have had to do is plug one adaptor in to the front USB ports and one into the rear USB ports. But of course there is nothing that says that will always work, it just happend that the fron and rear ports are on different USB busses in teh computers we use.

The USB to Serial adapter I have has two serial port ends, so I get two serial ports from one USB port. However, I only need one and the other serial port is always free. The one I am using is manufactured by Manhattan.

It is confirmed that counterfeit (fake) PL-2303 USB to Serial Controller ICs using Prolific's trademark logo and device drivers were being sold in the China market. Counterfeit IC products show exactly the same outside chip markings but generally are of poor quality and causes driver compatibility issues. We issue this warning to all our customers and consumers to avoid confusion and false purchase. Only buy from Prolific authorized distributors.

I bought this adapter from Unicorn Electronics in New York state. Unfortunately, I don't have the package anymore to confirm if it's made in China. Any thoughts if switching to a FTDI chip adapter would resolve the issue?

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.

3a8082e126