Re: [Hamlib-developer] ROTCTld usb0 issue on pi5
Library to control radio transceivers and receivers
Brought to you by:
n0nb
Menu
▾
▴
Re: [Hamlib-developer] ROTCTld usb0 issue on pi5
|
From: Randy R. <ran...@gm...> - 2025-04-13 19:37:20
|
Bob, Linux is case sensitive. /dev/ttyusb0 is not the same as /dev/ttyUSB0. Also you can use ls -l /dev/serial/by-if to see only the serial devices. For some reason real serial port ( /dev/ttyS0 ) don show up. Randy KB0NAV On 4/13/25 18:05, Bob Nazro wrote: > Here is > pi@rpq5:~ $ ls /dev > autofs gpiomem2 media2 ram3 tty11 tty33 > tty55 vcs vga_arbiter > block gpiomem3 mem ram4 tty12 tty34 > tty56 vcs1 vhci > btrfs-control gpiomem4 mmcblk0 ram5 tty13 tty35 > tty57 vcs2 vhost-net > bus gps1 mmcblk0p1 ram6 tty14 tty36 > tty58 vcs3 vhost-vsock > cec0 hwrng mmcblk0p2 ram7 tty15 tty37 > tty59 vcs4 video19 > cec1 i2c-13 mqueue ram8 tty16 tty38 > tty6 vcs5 video20 > char i2c-14 net ram9 tty17 tty39 > tty60 vcs6 video21 > console initctl null random tty18 tty4 > tty61 vcs7 video22 > cpu_dma_latency input pio0 rfkill tty19 tty40 > tty62 vcsa video23 > cuse kmsg port rtc tty2 tty41 > tty63 vcsa1 video24 > disk kvm ppp rtc0 tty20 tty42 > tty7 vcsa2 video25 > dma_heap log pps0 serial tty21 tty43 > tty8 vcsa3 video26 > dri loop0 ptmx shm tty22 tty44 > tty9 vcsa4 video27 > fd loop1 ptp0 snd tty23 tty45 > ttyACM1 vcsa5 video28 > full loop2 pts spidev0.0 tty24 tty46 > ttyAMA0 vcsa6 video29 > fuse loop3 ram0 spidev0.1 tty25 tty47 > ttyAMA10 vcsa7 video30 > gpiochip0 loop4 ram1 spidev10.0 tty26 tty48 > ttyprintk vcsu video31 > gpiochip10 loop5 ram10 stderr tty27 tty49 > _ttyUSB0_ vcsu1 video32 > gpiochip11 loop6 ram11 stdin tty28 tty5 > uhid vcsu2 video33 > gpiochip12 loop7 ram12 stdout tty29 tty50 > uinput vcsu3 video34 > gpiochip13 loop-control ram13 tty tty3 tty51 > urandom vcsu4 video35 > gpiochip4 mapper ram14 tty0 tty30 tty52 > v4l vcsu5 watchdog > gpiomem0 media0 ram15 tty1 tty31 tty53 > vcio vcsu6 watchdog0 > gpiomem1 media1 ram2 tty10 tty32 tty54 > vc-mem vcsu7 zero > > ttyusb0 is there when the unit is plugger in. > Using lsusb > pi@rpq5:~ $ lsusb > Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 003 Device 003: 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 003: ID 1a86:7523 QinHeng Electronics CH340 serial > converter_ > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > I try rotctld -vvvvv -m 2401 -r /dev/ttyusb3 -s 115200 -t 4533 > and it always tries to open serial_open: /dev/ttyS0 and fails. > thanks for getting back to me > Bob, W1RPQ > > > > On Sun, Apr 13, 2025 at 1:24 PM Nate Bargmann <n0...@n0...> wrote: > > 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 > > _______________________________________________ > Hamlib-developer mailing list > Ham...@li... > https://lists.sourceforge.net/lists/listinfo/hamlib-developer > > > > -- > Bob Nazro, W1RPQ > phone: (860) 941-7993 > b <mailto:Jos...@cp...>na...@gm... > > > > _______________________________________________ > Hamlib-developer mailing list > Ham...@li... > https://lists.sourceforge.net/lists/listinfo/hamlib-developer |
