Pl2303hx Usb 2.0 To Rs232 Com Port Serial Adapter Driver Download
Giuliana
Find many great new & used options and get the best deals for USB to RS232 TTL PL2303HX Converter Module Arduino Raspberry Pi Atmega -UK Stock at the best online prices at eBay! Free delivery for many products.
Recently I bought one similar and plugged it to my lily pad, it works really good, you can see the pinout in the picture, I guess that most of the arduinos with a similar interface can be programed wit this configuration, but please check first the pin out of your boards and compare it with the wire's colors in the picture, by the way in order to upload a sketch in the arduino, at least in my case with the lilypad 168(don't know others) you need to reset the arduino and you have 8 sec to upload the sketch through the "USB to RS232 ttl adapter".
I have to mention that this adapter need a driver in windows, I'm on linux and I don't know what I did but when I plugged it the first time the arduino IDE didn't show me a serial port but after a few days and a system upgrade i guess (sudo apt-get update... upgrade...) the IDE sow me this port "/dev/ttyUSB0" and after that it works really good.
Prolific Technology is a IC design house company and ASIC design service provider for USB Smart I/O (USB to UART, Card Readers, External USB Drive), Intelligent Green Energy Saving, and Mixed-Mode Hall Sensor solutions.
Easily add an RS-232 9-pin serial port to any computer with our PL2303-DB9 USB to Serial Adapter!
This adapter will let you connect older serial devices to modern computers, for terminal services, data transferring, remote control, and programming. Supports baud rates from 75bps to 12Mbps, multiple stop bit and parity types.
Plugable's USB to Serial Adapter features Prolific's PL-2303GT chip for the best combination of support and performance with a wide range of RS-232 serial devices. Drivers are built-into Windows 11, 10, 8.x, 7, and most Linux distributions, drivers are available for Windows XP, Vista, and macOS.
This adapter replaces a legacy built-in or PCI serial port and features a fixed male port with screw in connection. For connecting devices that also have a male connector an inexpensive DB9 coupler or standard serial cable can be purchased separately.
Works with devices with RS-232 serial ports such as other PCs with RS-232 ports, Bluetooth serial adapters, telescopes, amateur radio gear, GPS receivers, routers, firewalls, modems, plotters, embedded character displays, scan tools, sonar units, embedded boards and many others. Specific devices include: Garmin eTrex GPS, Seiko Label Printer, iRobot Create, Cisco products with serial consoles, US Robotics Modems, NexStar telescopes, Equus Scan Tools, Uniden Hand Held Scanners, etc. Works with software like: HyperTerminal, TeraTerm, WinDBG, all open source serial software on Linux, etc.
We use only genuine Prolific serial chipsets in our adapter. Some inexpensive serial adapters use cloned Prolific serial chipsets that will not work with the latest Prolific drivers, both those available for download and the drivers embedded in Windows. Because we only use genuine Prolific chips, our adapter is always compatible with the latest drivers from Prolific.
The original Plugable PL2303-DB9 adapter with Prolific PL2303-HXD chipset has a blue plastic case, while the updated adapter with the Prolific PL2303-GT chipset has a brown plastic case for ease of identification.
Following the installation instructions provided by the manufacturer of your serial devices, install any needed software or drivers. Connect the serial device to the adapter, and make any needed settings, such as COM port, baud rate, flow control, stop bits, etc.
Windows 7 SP1 installation media does not include support for Windows 7's latest driver signing functionality and requires installing the following updates from Microsoft manually before installing the Prolific drivers, or running Windows Update:
The Plugable USB serial adapter allows you to connect legacy devices that use RS232 serial communications to computers that do not have a serial port. Although this usually works well, a number of problems can crop up because many of the devices people want to connect are older devices with various issues. A frequent problem is that the software that is necessary to connect to the device does not work under modern operating systems such as Windows 7 or above. Other problems can include using an improper cable, incorrect port settings, or a basic incompatibility between the Plugable USB serial adapter and the device it is being connected to.
When the cable is plugged into Windows 7 or higher computers, the necessary driver should load automatically. If it does not load, make sure the computer is connected to the internet. If an internet connection is not available, download the latest drivers for the cable from the Plugable driver site here. For earlier Windows XP and Vista computers, the drivers must be downloaded from the Plugable website and installed.
Serial communications over RS232 is a legacy from an earlier age in computer when devices were not necessarily plug-and-play. Several different variables come into play, and all must be set up correctly to ensure communications.
In Windows, serial communications proceed through a COM port that is assigned by Windows when the USB serial adapter is plugged in. You can find out this COM port by opening Device Manager, going to Ports (COM & LTPT) and looking for Prolific USB-to_Serial Comm Port (COM#). The # symbol represents the port number of the COM port assigned by Windows. This port must be set correctly in whatever application is trying to communicate through that port.
Screen commands consist of "C-a" or ctrl+a (holding down the control key, and then pressing the 'a' key, then releasing both), to enter the command input mode, then commands may be entered with another key stroke.
We can directly write to the serial device from bash by redirecting the output of the 'echo' command to the serial device. First we need to set the serial port speed and then send the text "helloworld" to the serial device:
Most permission denied error messages can be resolved by adding your user account to the 'dialout' group or the group with control of the serial port. We can check the group ownership of the port with the following:
This is most often caused by incorrect baud rate settings on either the computer or device. Most serial devices like network routers and switches will have either a sticker with the serial port settings, or these can be found in the user manual for the device. For device with additional settings minicom may prove to be the easiest to configure.
The original PL2303-DB9 was revised with an updated chipset in April of 2021. The original version of PL2303-DB9 featured a Prolific PL2303HXD chipset which was discontinued by Prolific in 2020. This version of the adapter featured a blue plastic casing as shown below:
The adapter has since been updated to use the more recent PL2303GT chipset from Prolific. This chipset offers many of the same features as PL2303HXD and is a drop-in replacement in most applications. The new version of the adapter features a grey plastic casing as shown below:
Two way communication between the PC and the UART is generally stable until a large (but variable) number of characters is sent from the UART to the PC. When this happens, the PLC2303 appears to buffer the latest one or two characters coming from the UART and refuses to flush them to the PC until new characters are received. As characters are received at this point, the newly received characters are buffered, and the old buffered characters are pushed to the PC.
I have putty 0.61 on my machine. When I tried it with the USB adapter, I experienced two blue screen crashes on Windows 7 when working with the same output as teraterm. I wonder why putty gets crashes and teraterm only gets buffered characters. Could this be a driver issue? I am will to try other (free) terminal apps if you have any suggestions.
FYI, I am came here to report this exact same problem with TeraTerm v4.71 running on Windows7 using driver v3.3.17.203. However, PuTTY v0.61 works fine for me and does not exhibit the buffer issue. Thanks.
MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed. This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened. Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it. The
first actually works, and the second fails. Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second. However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
From the stack, it looks like the problem is both the Windows Driver Foundation core components (wdf01000.sys from Microsoft) and the Prolific ser2pl64.sys driver are completing the same IRP, which then triggers this crash.
I am trying to connect minicom to a serial device that is connected via a USB-to-serial adapter. This is a PL2303 and from everything I've read no additional drivers are required. The device is recognised as a PL2303.
The serial port communication programs moserial or gtkterm provide an easy way to check connectivity and modify /dev/ttyUSB0 (or /dev/ttyUSB1!) settings. Even though there maybe only a single USB to RS232 adapter, the n designation /dev/ttyUSBn can and does change periodically! Both moserial and gtkterm will show what port designation is relevant in their respective pull down menus when selecting an appropriate port to use.
I had fix this with adduser *username* dialout. I never had this error again, even though previously the only way to get it to work was to reboot the PC or unplug and replug the usb to serial adapter.
c80f0f1006