How to change default name for FTDI USB serial node to use cable ID
开云体育Hi All, ? I did a quick YouTube video on how to change the default FTDI based USB serial node name from /dev/TTYUSB0 to the path by ID name which includes the FTDI cable/device serial number. This is unique for each FTDI interface. ? The order you plug FTDI USB to serial cables in to a Raspberry Pi running Node Red will determine the default name, so if you have multiple USB to serial cables it is possible to have the wrong device connected to a flow. By using the By ID path for the serial node it will ensure the flow always uses the proper cable. ? Here’s a link to the video. As of the writing of this post the video is still rendering to HD. The HD rendering should be completed soon. ? 73 Dave wo2x ? |
|
Thanks to Dave for putting out that video.? I'm going to use it on my RCS-4 replacement flow I'm starting.??
...but another question now has emerged on another project that I did some digging around in. I got to looking at my pi in the amp rack that has a couple of EA4TX boxes (2x6 pack antenna & tail twister rotator) control.?? I'm using ser2net to send the serial data over the network to another pi running Node Red, so the Pi in the amp rack is basically a serial to network media converter. Works great.?? In the /dev/by-id folder, I only see 1 of my EA4TX boxes. pi@elayerrack:/dev/serial/by-id $ ls -lah
total 0
drwxr-xr-x 2 root root 60 Dec 18 15:09 .
drwxr-xr-x 4 root root 80 Dec 18 14:17 ..
lrwxrwxrwx 1 root root 13 Dec 18 15:09 usb-EA4TX_USB_Serial_22465-if00 -> ../../ttyACM1
pi@elayerrack:/dev/serial/by-id $
?
but in the /dev/by-path folder, I see both of them. pi@elayerrack:/dev/serial/by-path $ ls -lah
total 0
drwxr-xr-x 2 root root 80 Dec 18 15:09 .
drwxr-xr-x 4 root root 80 Dec 18 14:17 ..
lrwxrwxrwx 1 root root 13 Dec 18 14:17 platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.3:1.0 -> ../../ttyACM0
lrwxrwxrwx 1 root root 13 Dec 18 15:09 platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.4:1.0 -> ../../ttyACM1
pi@elayerrack:/dev/serial/by-path $
Any ideas on why that is? Kyle AA0Z |
开云体育The EA4TX boxes probably do not have genuine FTDI chipsets in them. Either a different chip that does not have unique serial numbers or Chinese clones of FTDI.?This is an issue with some USB to serial converters you buy from eBay and Amazon. They close an FTDI chip and all the closes have no serial number or the same serial number. Prolific chipsets also do not have unique serial numbers.? If you ever reboot the api and wind up controlling the wrong rotor, you’ll know why.? 73 Dave wo2x Sent from my waxed string and tin cans.? On Dec 19, 2022, at 8:53 AM, Kyle K <kylekrieg@...> wrote:
|
|
HI Dave I am sitting here with some problem whit ser2net there will not recognize my usb port ?? a new version of net2ser need a YAML config file and that is out of my range to figure it out ;-) sadly this has worked before but I cant rember how I did it last time ;-) but I have try your solution where I go in to the file browser in my ubuntu pc /dev/serial/by-id and copy the path of the usb /dev/serial/by-id/usb-Arduino__www.arduino.cc__0042_85534313837351F0C180-if00 but it will not use the path to show the way to my usb ??? it is a arduino board , but when I use the Arduino node I can get in contact whit the board ...no problem. 73" Ben Den man. 19. dec. 2022 kl. 15.06 skrev Dave wo2x <RocketNJ@...>:
|
|
Maybe this will help you.
Here is my ser2net.yaml config file in /etc/.? in the connector line, I just used nr8001 to say designate node red is sending to port 8001.? I think you can have any short description there.? %YAML 1.1
---
# This is a ser2net configuration file, tailored to be rather
# simple.
#
# Find detailed documentation in ser2net.yaml(5)
# A fully featured configuration file is in
# /usr/share/doc/ser2net/examples/ser2net.yaml.gz
#
# If you find your configuration more useful than this very simple
# one, please submit it as a bugreport
?
define: &banner \r\nser2net port \p device \d [\B] (Debian GNU/Linux)\r\n\r\n
?
admin:
? ? accepter: tcp,8000
?
connection: &nr8001
? ? accepter: tcp,8001
? ? enable: on
? ? connector: serialdev,
? ? ? ? ? ? ? ?/dev/ttyACM0,
? ? ? ? ? ? ? ?38400n81,local
?
connection: &nr8002
? ? accepter: tcp,8002
? ? enable: on
? ? connector: serialdev,
? ? ? ? ? ? ? ?/dev/ttyACM1,
? ? ? ? ? ? ? ?38400n81,local
? |
|
toggle quoted message
Show quoted text
On Dec 19, 2022, at 9:34 PM, Jerome K8LF <da2sv@...> wrote:
|
开云体育Thanks Dave Great video. I added it to my site so I can use it again. 73, VE7TIT Shanta On 2022-12-18 19:42, Dave wo2x wrote:
|
开云体育Hi Kyle, ? When you have several of my devices connected to the same RsPi, I recommend that you use the UDEV service, because it will allow you to assign a nmemonic to each device so that you can identify each one of the boxes by serial number. ? As you can imagine if you have only one device (for example a RemoteBox) you will find that when connected it appears as /dev/ttyACM0. When connecting a second (for example an ARS motor controller), it appears as /dev/ttyACM1, and so on with others. But the problem is that you can never know if a device is assigned to ttyACM0 or ttyACM1. ? The solution is to use the UDEV service. All RemoteBox, ARS, StackMain, or any EA4TX device use the same Microchip microprocessor, so they have the same VID (Vendor Id) "04d8" and PID (Product Id) "000a" but they have the serial number recorded in the USB descriptor, then using that option in the UDEV service, you can customize and identify each device, so that you can associate a name to each device, for example in your case ARS01 and RB2x8. ? And with this specific configuration in UDEV, you can make the ser2net service instead of using the generic and ambiguous name /dev/ttyACM0 and /dev/ttyACM0, can use /dev/ARS01 and /dev/RB2x8 ? Example of a UDEV file for 4 devices: ? I have pending to include a help tutorial on the operation of the UDEV file during these holidays ? 73s Pablo EA4TX ? ? De: [email protected] <[email protected]> En nombre de Kyle K ? Thanks to Dave for putting out that video.? I'm going to use it on my RCS-4 replacement flow I'm starting.?? pi@elayerrack:/dev/serial/by-id $ ls -lah total 0 drwxr-xr-x 2 root root 60 Dec 18 15:09 . drwxr-xr-x 4 root root 80 Dec 18 14:17 .. lrwxrwxrwx 1 root root 13 Dec 18 15:09 usb-EA4TX_USB_Serial_22465-if00 -> ../../ttyACM1 pi@elayerrack:/dev/serial/by-id $ ?
pi@elayerrack:/dev/serial/by-path $ ls -lah total 0 drwxr-xr-x 2 root root 80 Dec 18 15:09 . drwxr-xr-x 4 root root 80 Dec 18 14:17 .. lrwxrwxrwx 1 root root 13 Dec 18 14:17 platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.3:1.0 -> ../../ttyACM0 lrwxrwxrwx 1 root root 13 Dec 18 15:09 platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.4:1.0 -> ../../ttyACM1 pi@elayerrack:/dev/serial/by-path $
|
Dave wo2x
Kyle AA0Z
Bent Andersen