Copartner Usb To Serial Cable Driver

admin



Have you had difficulty using a USB to RS-232 adapter to connect your RS-232 device to a computer? If so, you are not alone. Our customers frequently encounter issues with these adapters. In this article, I’ll briefly discuss the origin of these issues and provide you with some suggestions for successfully handling them.

The Evolution from RS-232 to USB

Cable

In the old days of personal computers, one of the primary connections available was the RS-232 serial port. Apart from the parallel port, it was the primary means to connect an external device. The connector was reduced from a 25-pin connector to a 9-pin connector, but RS-232 ports remained present on every computer for many years. Built-in RS-232 ports featured direct mapping to memory and worked at a high priority. Data practically flowed directly to and from the software that was accessing the serial port.

What I did to overcome this was to 'roll back' my driver to the 3.3.3.114 dated 2009. I did an internet search for this driver, downloaded the driver and installed the driver. I then switched the comm port I was plugging the Prolific USB Serial Adapter into, to the older driver, and everything worked fine again. Hope this helps. Fully Serial / RS232 compatible We proudly boast about our 99% device compatibility ratio with this product! We also stand behind it. You may see others that look like ours, but ours comes with a driver for Windows 7, 32-bit as well as 64-bit. Commercial quality Our USB to Serial Adapter Cable is used mainly by AV pros and other industrial techs. If the cable is moved to a different USB slot, Windows will now load the newest driver to that port. (not 3.2.0.0) When this occurs, you will need to either load driver 3.2.0.0 to the new USB slot, or plug the cable back into its original USB slot. You can check the driver loaded using the procedure above. The first cable is a usb end and a serial (male) end and the other cable is a serial (female) and rj45 end. When I plug it in a windows update pops up and try to install 'Prolific+USB-to-Serial+Comm+Port+(COM3)' but then it says 'failed'. I can' seem to install the drivers. Can someone please help?

Ll84201

In 1996, the Universal Serial Bus (USB) standard was introduced as a replacement for the serial connector and other connector types that were typically found on the back of computers. The USB provided smaller connectors and more data throughput than the serial and parallel interfaces it replaced.

USB devices have high throughput, but they use a shared data bus. Data is wrapped up and transferred in packets. To handle the packets and move data in and out of the program accessing the USB device, a software driver is needed. The software driver sits between the hardware and the computer program you are using, and it must be installed and working correctly.

The Necessity of an Adapter

With the widespread adoption of USB, most computers sold now do not have an RS-232 port. Therefore, to connect an RS-232 device (such as a CR1000) to a computer, you need to use a USB to RS-232 adapter, such as the 17394 converter.

While USB to RS-232 adapters perform a necessary function, they do have some limitations. For example, there are three types of problems that you may encounter when using a USB to RS-232 adapter:

  • Driver issues
  • Hardware issues
  • Performance issues

Issue #1: Driver

The most common problem that our customers encounter with a USB to RS-232 adapter is getting the proper driver installed. The driver must correspond to the chip inside the cable—not to the manufacturer of the cable.

For USB to RS-232 chips, there are two primary manufacturers: Prolific and FTDI. Because off-brand chips with poor drivers are unreliable, Campbell Scientific recommends and currently sells a cable using an FTDI chip (part number 17394). We chose this cable because it uses a chip that has a certified driver available on Windows Update. (The older cables were silver in color and did not have a driver available for Windows beyond version 7.)

Tip: Test your USB adapters in the office with your field computer. When you are in the field, your computer won’t have an Internet connection to automatically download and install the driver.

If the driver for your adapter is not automatically installed or cannot be installed from a CD, you will need to identify the chip in your cable and locate the driver on the Internet. Some manufacturers identify on their packaging which chip is used inside their cable. You can also identify a cable’s chip from the Windows Device Manager by following these steps:

  1. In the Windows Device Manager, right-click your device from the list.
  2. In the drop-down menu that opens, select Properties.
  3. In the Properties dialog box, select the Details tab.
  4. In the Property field, select Hardware Ids from the drop-down menu.
  5. In the Value field, there is both a VID (Vendor ID) and a PID (Product ID). These IDs respectively indicate the manufacturer and the model number of the chip.
  6. In the example above, I did a quick Internet search for VID 0403 PID 6011, which revealed to me that the chip is an FT4232 manufactured by FTDI.
  7. After you know your chip type and manufacturer, you can locate and download the correct driver for your version of Windows.

Issue #2: Hardware

USB to RS-232 adapters are commodity pieces of computer equipment. As much as we all wish that everything was as reliable as the CR1000, all adapter cables eventually fail.

Although there are two primary companies that manufacture USB to RS-232 adapter chips, there are many cable manufacturers who offer varying levels of cable quality.

  • Higher-quality, industrial models should last longer, but they wear out over time—just like any field tool.
  • A poorly constructed cable could have components that fail in a short period of time—perhaps even by the time you receive the cable.

I have seen several cases where old cables could no longer handle 115200 baud, but the cables still worked on low baud rates. There have been many more cases where a USB cable stopped working half-way through a day in the field.

Tip: If your field site is far from your office, take two USB to RS-232 cables with you. Lost time in the field can be a lot more costly than the purchase price of a second cable.

Issue #3: Performance

As mentioned previously, USB uses a shared data bus with packetized communication. The packetized communication introduced some latency (data transfer time) that wasn’t present with built-in RS-232 ports. Unfortunately, latency makes a noticeable difference when you download large amounts of data or upload a new operating system.

The driver for FTDI chips allows you to lower the latency time on packets. To do this, you can use the Latency Timer field, which is accessed through the Windows Device Manager. Follow these steps:

  1. From the Windows Device Manager, right-click your device from the list.
  2. In the drop-down menu that opens, select Properties.
  3. Click the Port Settings tab.
  4. Click the Advanced… button.
  5. In the Advanced Settings window, navigate to the Latency Timer field, and reduce the setting to 1 for best performance.

In addition to lowering your latency time, I also recommend disabling the Selective Suspend option for your cable. The Selective Suspend option allows Windows to put your hardware to sleep, which can result in corrupt data packets. To disable the Selective Suspend option, clear the checkbox for the Enable Selective Suspend field on the Advanced Settings window for your device.

Note: The Selective Suspend option is already disabled by default in the FTDI driver.

Conclusion

Newer data logger designs, such as the CR6, feature a native USB connection. Many devices, however, will feature RS-232 connections for years to come, and we’ll need to continue using USB to RS-232 adapter cables. I hope the suggestions I’ve provided help. Feel free to share any USB to RS-232 issues that you have encountered by posting a comment below.

USB to Serial converter HL-340: download 32 and 64 bit windows drivers (PID/VID 4348:5523)

Due to some reasons I had to run Windows XP on Virtualbox. After connected my classic pretty blue usb/serial cable converter, I found out that, as usual, Windows couldn’t recognize it. I wasted lot of time to find the appropriate working driver.

Copartner Usb To Serial Cable Drivers

Copartner Usb To Serial Cable Driver

The converter is identified as

Copartner Usb To Serial Cable Driver Modem

ID 4348:5523 WinChipHead USB->RS 232 adapter with Prolifec PL 2303 chipset

Factory website: http://wch-ic.com/ Rise of nations gold edition download.

Chip page: http://wch-ic.com/product/usb/ch340.asp

I don’t have the time to investigate because lsusb reports that it mounts the chip PL2303 while Windows XP identifies it as USB-SERIAL CH340, but I guess this is due for some “cloning” reasons.
Anyway here are the most updated windows drivers I could find:

Copartner Hdmi Cable 20276

32 bit: ch341_hl-340_windows_drivers_32bit

Copartner 20276

64 bit: usb_serial_converter_ch340_windows_x64_drivers

Hope it helps.