Re: [Hamlib-developer] ROTCTld usb0 issue on pi5

[Nate B. <n0...@n0...>]

Hi Bob.

* On 2025 12 Apr 11:22 -0500, Bob Nazro wrote:
> I have a AntRunner rotor unit that connects to my raspberry pi with a usb
> cable. The instructions say to run "rotctld -vvvvv -m 2401 -r /dev/ttyUSB0"
> to connect. It fails each time.

My suggestion of the first step is to be sure that '/dev/ttyUSB0'
actually is present.  Use "ls /dev" to check.  If it is present, you can
post the output of "ls -l /dev/ttyUSB0" which should show the
permissions, owner, and group of the device file.  On Debian and
Raspberry Pi OS the owner is 'root' and the group is 'dialout'.  It's
imperative that your user be in the 'dialout' group.

> The connection is Device 004. I am at a loss , as to getting the connection
> up and running. It does work on my laptop with hamlib so I know that the
> unit works. Any help is greatly appreciated.
> 
> pi@rpq5:~ $ lsusb
> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 003 Device 005: ID 1546:01a7 U-Blox AG [u-blox 7]
> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 004: ID 1a86:7523 QinHeng Electronics CH340 serial converter
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> 
> 
> Running the script.
> 
> pi@rpq5:~ $ rotctld -vvvvv -m 2401 -r /dev/ttyUSB0
> rotctld, Hamlib 4.5.4 Jan 10 01:31:41Z 2023 SHA=921cc5
> Report bugs to <ham...@li...>
> 
> rot_init called
> initrots4_grbltrk: _init called
> rot_register (2401)
> rot_register (2402)
> grbltrk_rot_init:454 rot->caps->rot_model: 2401
> set_conf: called
> rot_open called
> serial_open: /dev/ttyS0
> serial_open(229): open failed#1
> serial_open(229): open failed#2
> serial_open(229): open failed#3
> serial_open(229): open failed#4
> serial_open: Unable to open /dev/ttyS0 - No such file or directory

This is why I am asking about the serial devices on your system.  The
command is telling rotcld to use '/dev/ttyUSB0' but it is trying to open
'/dev/ttyS0' which is usually a system serial port.  But, the Raspberry
Pi's I've dealt with don't even have that port.  Instead they have
'/dev/ttyAMA0' which is present on the GPIO header strip.

The actual name of the USB to Serial adapter should show in the
directory '/sys/bus/usb-serial/devices/'.  On my desktop system I get:

$ ls -l /sys/bus/usb-serial/devices
total 0
lrwxrwxrwx 1 root root 0 Apr 13 08:55 ttyUSB0 -> ../../../devices/pci0000:00/0000:00:14.0/usb2/2-10/2-10.4/2-10.4:1.0/ttyUSB0/

Which, I really can't correspond to the output of 'libusb':

Bus 002 Device 008: ID 0557:2008 ATEN International Co., Ltd UC-232A Serial Port [pl2303]

At this point without knowing what exists on your system, I can't offer
much more guidance.

73, Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819