Hi there, I have a Garmin eTrex Camo GPS unit, and the cable for it has a serial port, so I purchased a QinHeng Electronics HL-340 USB-Serial adapter online, assured by a Linux-using friend that it would work - and indeed, my netbook recognises that the cable exists, but is not picking up the cable (and GPS device) on the other end of the adapter.
Kernel 4.8.0-0.rc7.git0.1.fc25.x86_64 USB-Serial Adapter driver: ch341 idVendor=1a86, idProduct=7523 The chipset is recognized, and the ch341 kernel module is loaded, but the baud rate is not set correctly, and so garbage is sent/received through the usb/serial adapter instead of valid characters (for instance with minicom).
HL-340 usb to serial driver for windows 7 64 bit (CH341SER.EXE) Posted on February 4, 2011 by res akhirnya setelah pencarian yang hampir putus asa nemu juga driver usb to serial HL-340 buat windows 7 64 bit yang bisa diambil di.

Qinheng Electronics Hl-340 Usb-serial Adapter Windows Driver
Qinheng Electronics Hl-340 Usb-serial Adapter Raspberry Pi

Active1 year ago

if i run the common lsusb i get something like:

This thing (1a86:7523) is a 'QinHeng Electronics HL-340 USB-Serial adapter.' Let's say you have the 'usb' section right. Have you the 'serial' section right?

Bus 003 Device 003: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter

but it doesn't show the device file path (i.e ttyUSB0). does it exist a command which does this?

about dmesg and udevadm info they are too verbose.

I would rather to have a simpler output, the best would be to append just the device file path to the output of lsusb, something like:

Bus 003 Device 003: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter /dev/ttyUSB0

aster94

aster94aster94

1 Answer

a lot of copy/paste brought me again here hoping that this would be helpful for others and also to improve my code

I used the almost perfect code from the answer in this question and added/removed some little stuff

output:

Bus 003 Device 005: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter - /dev/ttyUSB0

NOTE: i don't have any unix experience so if you would like to improve the code please do!

aster94aster94

Not the answer you're looking for? Browse other questions tagged command-lineusb or ask your own question.

Active4 years, 2 months ago

When I connect the USB interface from my arduino nano to my openwrt router then the command lsusb shows:

But I do not get a new serial device in /dev/tty*

I have kmod-usb-serial installed.

meesernmeesern

1 Answer

Posting this in case it is useful to others. The answer turns out to be that I needed the kmod-usb-serial-ch341 kernel package:

The HL-340 is a CH 340 compatible device.

Once the ch341 driver is installed the nano appears as /dev/ttyUSB0 and defaults to 115200 baud. From dmesg

meesernmeesern

Qinheng Electronics Hl-340 Usb-serial Adapter Windows Driver

Got a question that you can’t ask on public Stack Overflow? Learn more about sharing private information with Stack Overflow for Teams.

1 Answer

Not the answer you're looking for? Browse other questions tagged command-lineusb or ask your own question.

1 Answer

Qinheng Electronics Hl-340 Usb-serial Adapter Windows Driver

Qinheng Electronics Hl-340 Usb-serial Adapter Raspberry Pi

Not the answer you're looking for? Browse other questions tagged arduinoopenwrt or ask your own question.