Of course Rob is right here.. though there is a
simpler way if the cabling on the host never changes:?
/dev/serial/by-id .? For example, I can see the various serial
ports on my host:
??? ls -la /dev/serial/by-id/
??? total 0
??? drwxr-xr-x 2 root root 80 Jul 15 08:27 .
??? drwxr-xr-x 4 root root 80 Jul 15 08:27 ..
??? lrwxrwxrwx 1 root root 13 Jul 15 08:27
usb-FTDI_usb_serial_converter_FTCAWZIA-if00-port0 ->
../../ttyUSB0
??? lrwxrwxrwx 1 root root 13 Jul 15 08:27
usb-Prolific_Technology_Inc._USB-Serial_Controller-if00-port0
-> ../../ttyUSB1
With this, instead of using the command:
?? rigctld -m 3068 -v -r /dev/ttyUSB0 -s 19200 -c 0x7c
you would use say:
?? rigctld -m 3068 -v -r
/dev/serial/by-id/usb-FTDI_usb_serial_converter_FTCAWZIA-if00-port0
-s 19200 -c 0x7c
--David
KI6ZHD
??
On 08/26/2024 07:56 AM, Rob Giuliano
via groups.io wrote:
toggle quoted message
Show quoted text
Since it appears the radio provides 2 USB devices (USB0 and
USB1), the operating system may not "ALWAYS" present them in the
same order.
This will cause no end to interfacing headaches.
?
If you are running this on a Linux distribution, you may look
into udev rules.
Depending on the USB device, you should be able to find a way
to separate the 2 and provide more descript '/dev/{device-name}
sim-links to make things easier to keep track of.
They may be using the same ProductID and VendorID, so you may
need to dig a bit deeper to find the identifying USB
characteristic to separate them.
-------
Robert Giuliano
KB8RCO
