Hl-340 Usb-serial Adapter Driver

[Sandi Loisel]

It sounds like you still had an application talking to the device at the time the cable was disconnected. If you were to do a fresh reboot with no devices attached, and then attach/detach the device without running any programs, does the same issue occur?

Just a hint: In most cases when you add a driver you simply need to add a module and not change the kernel itself. Once you go down the road of changing the whole kernel you have to find a starting config which basically matches the running system, and then install both the kernel and the entire module directory tree.

Hi,
I am trying to connect a GPS with my TX2 through a HL340 USB serial adapter. THe GPS came with a DB9 connector and I used a DB9 to USB connector to connect it with TX2. When connected, I was getting faulty output on the serial monitor. Please refer to the link below which directs to the issue.

Once you download your new driver, then you need to install it. To install a driver in Windows, you will need to use a built-in utility called Device Manager. It allows you to see all of the devices recognized by your system, and the drivers associated with them.

In the Device Manager window, locate the device for which you want to install or update the driver. You can find devices under their respective categories, such as Display adapters, Sound, Video and Game Controllers, or Network adapters.

Click on the Browse button and navigate to the location where you saved the downloaded driver files. Select the appropriate driver file and click OK. Then, click Next to begin the installation process.

Many device drivers are not updated through the Microsoft Windows Update service. If you are having trouble finding the right driver, stop searching and fix driver problems faster with the Automatic Driver Update Utility. Automatic updates could save you hours of time.

The Driver Update Utility automatically finds, downloads and installs the right driver for your hardware and operating system. It will Update all of your drivers in just a few clicks, and even backup your drivers before making any changes.

After finishing its analysis, the driver scanning tool will present a summary of outdated or missing drivers on your system. You'll then have the option to either update each driver separately or perform a bulk update of all required drivers simultaneously:

If you have had recent crashes, power outages, viruses or other computer problems, it is likely that your drivers may have become damaged. Browse the list above to find the driver that matches your device hardware. To see more matches, use our custom driver search engine to find the exact driver.

I have a nano-style boad with a QinHeng Electronics HL-340 USB-Serial adapter, which clearly isn't an FTDI chip, and the FTDI programmer therefore doesn't work. Does anyone know of an alternative utility/where I can find information to do the same with this chip?

There is no storage on the CH340 and family of UARTs where you could put a unique ID. This is also a problem for the PL2303 type. I have been trying to find solutions for this problem. First and easiest is the position of the device on the USB bus. It will be unique for each device. If you're using linux you can find each device under /dev/serial/by-path . There is also a /dev/serial/by-id but there will only be one entry there for this device because it shows the last one connected. FTDI chips will each have unique entries here. Cheap chips won't, but they each have an entry under /dev/serial/by-path.This position, and the device names, should persist across reboots. If you have a lot of changes to your USB devices, plug all the CH340 devices into the same hub, then plug that in. The devices will enumerate in the order that they are plugged in to the hub. This one-hub trick should work for MacOS and windows too, they should come up in the same order.

Then the cheapduino script connects by serial to the device and sends the string 'ID' and the software on the device responds DEVID=THX1138 or whatever. The script then creates a symlink /dev/THX1138 that points to /dev/ttyUSB0

There are a lot of drawbacks to this method. The script must time out if the software on the cheapduino doesn't answer. Also this is not using the SYMLINK function of udev so it won't clean up dead links on disconnect, but it will overwrite them on reconnect. All of your cheapduinos must have this functionality in their software, with different device IDs set. They all must use the same baud rate as the script unless you want to write a very complex script that takes a long time. Finally, this method works much better at low baud rate than at high baud rate, which for timing reasons may not succeed every time. (cheapduinos are cheap!) 9600 works much better than 115200 which works after several tries. But since all your CH340 arduinos must be the same speed with this method, you can only go as slow as your fastest device.

I have the same problem, where I have multiple (4+) usb-serial converters, any one could be plugged into any port, and they were purchased at the same time and therefore are identical in every way (including iSerial of 0).

Put a Maxim DS18S20 on your board, each has a unique serial number and are very inexpensive. There are a lot of software examples on the internet using this device. You could dead-bug it to the nano. to operate it needs a 4.7K resister connected to +5 and a ground connection. You can connect both the 5V and Ground connections of the device to ground. It would be easy to dead bug this to the nano then by simple communication via one pin you can get the serial number. There are several packages available. With care you could use an input pin, read the serial and save it for future use. When it Inits it will do this again. Just be sure the input is not driven low during the init process.

Here is a software tool that I wrote which can be used to update serial number of WinChip Head CH340B. This will be useful for some one who wants to connect multiple CH340B Virtual COM Port devices to their Windows PC.

THE PROBLEM: when I try to connect the Raspberry with the sensors or with the PC with same Python script the Raspberry can only receive messages from the outside but it can't send messages outside (with different parameters, program languages, etc.). They are just lost. There are no any exceptions, error codes or something else.

Does anyone know what could be the problem? Help me please! Googling does not help. Maybe the problem is in permissions? Maybe I forgot about some settings of serial ports? Or do I use wrong devices (but they work with my PC)?

First, USB-RS485, recognized as /dev/ttyUSB0. But his driver (ch341) does not support mode 9600/7databits/even/1stopbit (as writen here ( -electrons.com/source/drivers/usb/serial/ch341.c?v=4.4), this does not support parity, various count databits and stopbits).However, there is driver ( _LINUX_ZIP.html) where fixed some problems. E.g. serial device now responds on changing count of databits. But not for parity. To test this i connect 2 same devices between themselves via RS485 and connect them to Raspberry Pi. Then i use picocom to change device paramters and trancive data between them. When i use this adapter with Windows, this works perfectly in mode 9600/7databits/even/1stopbit. Because used other driver.

The problem of connecting the Raspberry Pi to my PC via serial port has been solved by setting all port parameters more precisely in both sides. The pySerial is working perfectly for all mentioned devices in case of using simple serial port.

But I couldn't set up communication with sensors via RS-485 standard where it is required. I couldn't receive any signal from any sensor. Nevertheless, I am newbie in serial ports and RS-485 and I'm not sure that I clearly understand such parameters as delay_before_tx/rx, RTS/CTS, DSR/DTR etc. Maybe I have just set it up wrong for my devices.

I found with my mac book air it wouldn't connect using eqmod (using parallels) but I had better luck using EQMAC. Although eventually I rebuilt my machine using a bootcamp partition as all of my other bits (cameras, filters etc) run natively on windows. It can be done natively on a Mac built to do so is beyond me.

I suggest you use the search function on this forum for 'EQMAC' as a starting point but as a Mac user myself I would consider other options. Such connectivity is rarer than rocking horse do do in my experience.

Getting anything to run on a Mac in regards to astronomy software/hardware is a challenge! Took me 2 days to get my CCD to function. Even with parallels I still get lots of problems. Windows machine is very much on the Christmas list! Although I cannot help you with your current issues I do feel your pain! Hope you get things sorted

Which drivers you need, if any, depend on which chipset is in the USBserial interface. If you're not sure it's possible that you can find out by going to the hardware section of the system information and displaying all the stuff there about USB devices. I have no idea what it will say, but hopefully you can work out which one it is.

Well, 1a86:7523 is apparently a QinHeng Electronics HL-340 USB-Serial adapter, so it does look at least like you have the correct driver installed though something doesn't appear to be making a very good job of recognising the device.

c80f0f1006