[SOLVED] Have multiple USB<->RS2332 devices. Which /dev/ttyUSBx goes to each device?
ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Have multiple USB<->RS2332 devices. Which /dev/ttyUSBx goes to each device?
I have multiple USB<->serial devices. They use the FTDI chip. As each USB device is plugged in, they are correctly detected by the kernel and given a serial port, /dev/ttyUSB0, /dev/ttyUSB1, etc.
Devices can be plugged in any order, they can be unplugged, and plugged in again, etc. How do I map which serial port is which USB device? i.e. I want to ask the kernel which /dev/ttyUSBx device it assigned to a specific USB<->serial device.
This question has come up a few times on stackexchange. Using shell scripting, it can be done by following directory links in /sys/bus/usb/devices, looking for a line in uevent files, etc. I want to do this from C or C++, and was wondering if there's system calls I can use to query the kernel/driver, instead of searching directories for files, parsing links and open/reading/parsing text files.
I am familiar with libusb, so I already know how to get the list of USB devices and find my devices: bus #, device #, ID, manufacturer string, serial number string, etc.
IMO, having a separate /dev/ttyUSBx for each device is the cleaner solution. I am not allowed to make any changes to system configuration files (for reasons of work policy).
IMO, having a separate /dev/ttyUSBx for each device is the cleaner solution. I am not allowed to make any changes to system configuration files (for reasons of work policy).
I will parse the files in /sys.
Hi
I have a question.
What application do you use to communicate the host with the device?
Some derivative of SynCE? What version of Linux do you use? Device?
I am writing the application that communicates with the devices. The application is written in C++.
One of the devices is the Thorlabs FW102C filter wheel. When plugged into the USB port, its USB chip is detected by the kernel as a USB<->RS232 bridge, and the FTDI device-driver creates a device-file named /dev/ttyUSBx (where 'x' is the next available number). The device-file can be opened and used to communicate with the device as if it was a classic serial port.
The system is Redhat Enterprise Linux, but the application I'm developing is distribution-agnostic.
Last edited by intestinal fortitude; 11-02-2022 at 01:23 PM.
Remember that "directories" such as /sys, /dev, /proc, are actually kernel interfaces. They do not correspond to any physical resource although they appear to be "directories" containing "files." It's all done by the kernel. Some of the files can be written to, usually only by root, and when this happen it causes changes to occur. I have never before seen anything as simplyelegant as this.
Last edited by sundialsvcs; 11-02-2022 at 09:46 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.