PL-2303 family chipset for widest possible compatibility. Microsoft signed drivers for 32/64-bit Windows 10, 8.1, 8, Vista, and XP, drivers for Mac OS X 10.6 through 10.12 including Snow Leopard, Lion, Mountain Lion, Mavericks, Yosemite, El Capitan, and Sierra. Open source drivers included in Linux kernel 2.4.31 and later. Super Sale/ Click to Buy Now! SAVE BIG at SerialGear.com. For windows usb serial adapter cables using prolific chip also mac and linux drivers for usb serail cables as well as x86 64-bit drivers for prolific chip serial cables usb serial driver. Driver also available via Windows Update (Vista, 7.

OS: Linux Mint 19 Tara (also tested on Ubuntu 18.04 LTS and Ubuntu 14.04 LTS)Kernel: 4.15.0-20-genericI have a USB-Serial adapter with the PL2303X chip to connect hardware to a Linux host. The device appears connected via lsusb, however I cannot send and receive data. I've tried sending/receiving data using moserial and putty; when attempting to send commands, no response data is returned and I notice no changes in dmesg or /var/log/syslog.The same USB-Serial adapter connects and works on the same Dell laptop model with Windows 10; on Windows it can receive commands and return data configured with the port settings below.I'd like to use the following port settings, though I've tried variations of the following to no avail using moserial and putty (i.e.

No parity, different baud rates, hardware/software handshaking, etc.): Device: /dev/ttyUSB0 (permissions 666, $USER added to `dialout` group)Baud rate: 9600Data bits: 8Stop bits: 1Parity: EvenHandshake: noneAccess mode: read and writeWindows also works with changing the above settings (i.e. No parity, 7 data bits, lower/higher baud rate, etc.).I need to be able to send commands and receive data similar to how the device works using Windows, preferably with the above port settings.Any ideas on how to fix or debug this?

I appreciate it.More info:lsusb output identifies the device asBus 001 Device 016: ID 067b:2303 Prolific Technology, Inc. Next thing I'd do is to debug the transfers with usbmon/wireshark on the host side, and a scope on the RS232 side, to narrow down what goes wrong, but I don't know if you are comfortable with that.

The 'error sending break' follows a disconnect, so it's not that surprising. The disconnect itself is, though.

I couldn't find a datasheet with the USB protocol for the PL2303X, so in first approximation one needs to believe the kernel driver source. BTW, you can just do echo foobar /dev/ttyUSB0 etc.–Jul 31 '18 at 20:59. I found an old manual which explained 'commonly communication cables use only 3 pins (RXD, TXD, and GND). This device has a hardware reset pin that is controlled by DTR signal from host.'

Use the following settings to get the following COM ports: In the pop-up window, select the baud rate under the Baud Rate and click Send. So no matter how many times you remove the driver files and reboot – the next time you insert the USB-To-Serial adapter, Windows installs the newest non-working version again. Download drivers from Prolific site. May be, a solution will be to use the old W7 drivers version into W In the meantime action according this guideline was successful: Home Contact Support Knowledgebase Downloads.

I prefer not to block all updates. And since USB does not require any IRQ resource, more devices can be attached to the system without the previous hassles of device and resource conflicts. Prolific’s guys are fun when they said: If prolific usb to serial bridge cable offers a choice to remove proolific driver, then select to remove the current “bad” driver.

There is lot’s proliic people reporting problems with W10 and Prolific devices based on popular PL adapter.

PLTA USB to Serial/UART Bridge Controller Prolific USA IC Design & Manufacturing

Search Tectona Electronics Inc. Hey, but I can’t do that myself!!! This confirms you need to install correct driver file.

How do I fix it? OmarGimenez replied on November 22, Magellan data cable accessories come standard with a DB-9 connector, compatible with the DB-9 port on your computer.

Uncheck the box that says “Use automatic sttings”.

Improve chip capabilities and added new features. Removal of this tool: Or contact prolific usb to serial bridge cable worldwide distributors for other cable product reference and chip samples. Click on properties, and get the details: FelixHitz replied on December 10, On the next windows, choose the second option “Look for a driver on my computer”.

Cvlt-ii scoring software. In the learning phase of the task, individuals are read 16 words and asked to immediately recall these words over five repeated trials (Trials 1–5).

Once manually set, the device driver remain in prilific 3. We have many OEM customers that use this item prior to large scale production.

Prolific Technology Inc. (USB to UART / RS / Serial)

Download drivers from Prolific site. I have tested it and it work fine. RobbieAitkenhead replied on December 10, Daren replied on August 20, Counterfeit IC products show exactly the same outside chip prolific usb to serial bridge cable but generally are of poor quality and causes Windows driver compatibility issues Yellow Mark Error Code 10 in Device Manager.

Here is the driver with the solution!! The USB converter is housed in a strong molded enclosure birdge for use in rugged application areas. Issue will also may show messages like this: You must follow ever step in the process in exact order.

This unit can be cut and use their own Connector instead of the DB-9 port.

PL2303TA USB to Serial/UART Bridge Controller

As many people, you probably upgrade directly from W7 to W10, and sure, don’t know that this problem was already present with W8. If not, then the prolific usb to serial bridge cable driver is not installed. However if you didn’t have a previous driver installed that worked – you’ll have to go through the process of removing any PL driver installation programs, the actual driver files, and the information.

So no matter how many times you remove the driver files and reboot – the next time you insert the USB-To-Serial adapter, Windows installs the newest non-working version again. Prolific recommends following vendor cable brands: I’m afraid that there is no solution