hamlib-developer — hamlib developers forum

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

[Bob N. <bn...@gm...>]

Randy helped me with:
sudo ln -s /dev/ttyUSB0 /dev/ttyS0
This crested the TTYL port and it ran rotctld . Thanks for everyone's help.

Bob Nazro, W1RPQ
phone: (860) 941-7993
b <Jos...@cp...>na...@gm...


On Sun, Apr 13, 2025, 19:34 Nate Bargmann <n0...@n0...> wrote:

> * On 2025 13 Apr 14:54 -0500, Bob Nazro wrote:
> > Her you go:
> > pi@rpq5:/dev $ ls -l /dev/ttyUSB0
> > crw-rw---- 1 root dialout 188, 0 Apr 13 13:55 /dev/ttyUSB0
>
> What does the "groups" command return.  If it doesn't have 'dialout' in
> the list, then you'll need to add your user to the 'dialout' group (I
> can help with that).  If it's there, then we need to look elsewhere.
>
> 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
>

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

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

* On 2025 13 Apr 14:54 -0500, Bob Nazro wrote:
> Her you go:
> pi@rpq5:/dev $ ls -l /dev/ttyUSB0
> crw-rw---- 1 root dialout 188, 0 Apr 13 13:55 /dev/ttyUSB0

What does the "groups" command return.  If it doesn't have 'dialout' in
the list, then you'll need to add your user to the 'dialout' group (I
can help with that).  If it's there, then we need to look elsewhere.

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

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

[Randy R. <ran...@gm...>]

I'm trying this on my Pi-Star so I get a different version of Hamlib and 
have a different rotor attached.

It seems to work on mine but I have seen a error like this at one time.

On my Desktop I see what looks like your problem:

/bin/rotctl -vvvvv -m 601 -r /dev/ttyUSB7
rotctl Hamlib 4.6~git 2024-11-09T13:02:04Z SHA=32e6b9 64-bit
Report bugs to <ham...@li...>

rot_init called
initrots4_gs232a called
rot_register (601)
rot_register (609)
rot_register (610)
rot_register (602)
rot_register (603)
rot_register (611)
rot_register (612)
rot_register (604)
rot_register (605)
rot_register (606)
rot_register (607)
rot_register (608)
gs232a_rot_init called
set_conf: called
rot_open called
serial_open: /dev/ttyS0
serial_setup: tcgetattr

On my system I really have a /dev/ttyS0 so the open works, on your Pi 
you don't.

For a work around:

sudo ln -s /dev/ttyUSB0 /dev/ttyS0

This will create a symbolic link so when rotctl attempts to open 
/dev/ttyS0 it will find one and it will open /dev/ttyUSB0...

Or git a newer version.

On 4/13/25 19:45, Bob Nazro wrote:
> tried this:
> pi@rpq5:~ $ rotctld -vvvvv -m 2401 -r /dev/USB0 -s 115200 -t 4533
> 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
>
> Then this.
> pi@rpq5:~ $ ls -L /dev/serial/by-if

Correction:

% ls -l /dev/serial/by-id/
total 0
lrwxrwxrwx 1 root root 13 Feb 10 14:56 
usb-FTDI_FT232R_USB_UART_AQ048BP6-if00-port0 -> ../../ttyUSB1

Randy KB0NAV

> Bob Nazro, W1RPQ
> phone: (860) 941-7993
> b <mailto:Jos...@cp...>na...@gm...
>

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

[Bob N. <bn...@gm...>]

Her you go:
pi@rpq5:/dev $ ls -l /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 0 Apr 13 13:55 /dev/ttyUSB0

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 <Jos...@cp...>na...@gm...

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

[Randy R. <ran...@gm...>]

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

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

[Bob N. <bn...@gm...>]

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 <Jos...@cp...>na...@gm...

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

Re: [Hamlib-developer] Correctly setting CTCSS tones?

[George B. <geo...@gm...>]

The output from dump_caps is the real CTCSS frequency.  The c & C 
commands take their argument in tenths of Hertz, so it can be handled as 
an integer.

On 4/12/25 3:29 PM, Richard Emling wrote:
> Hello everyone,
>
> I would like to understand how to interpret the CTCSS tones from the 
> --CAPS-DUMP list when transmitting them to the transceiver. They are 
> listed with a decimal point. However, when I transmit them using the C 
> command and later query with the c command, only the number before the 
> decimal point is returned, as if the part after the decimal point is 
> lost. What am I doing wrong?
>
> Best regards,
>
> Richard (DO9RE)
>
>
> _______________________________________________
> Hamlib-developer mailing list
> Ham...@li...
> https://lists.sourceforge.net/lists/listinfo/hamlib-developer

Re: [Hamlib-developer] Introduction and Question about S-Meter-Reading

[<gm...@bt...>]

Hi Richard,

That looks good.

73 Phil GM3ZZA
________________________________
From: Richard Emling <DO...@ho...>
Sent: 13 April 2025 10:44 AM
To: Phil GM3ZZA <gm...@bt...>
Cc: Stephen Pattinson <st...@bi...>; ham...@li... <ham...@li...>
Subject: Re: [Hamlib-developer] Introduction and Question about S-Meter-Reading

Hi.

Many thanks. So, did I interpret your words right with my script?

functions/levels/get_strength



73

Richard, DO9RE

Am 13.04.2025 um 11:07 schrieb Phil GM3ZZA via Hamlib-developer <ham...@li...>:


IIRC hamlib does its best to standardise all meter level readings for the different rigs. So S9 should always be a reading of 0 regardless of how the rig CAT encodes it.

Phil GM3ZZA

Get Outlook for Android<https://aka.ms/AAb9ysg>

________________________________
From: Stephen Pattinson via Hamlib-developer <ham...@li...>
Sent: Sunday, April 13, 2025 5:56:49 AM
To: ham...@li... <ham...@li...>
Subject: Re: [Hamlib-developer] Introduction and Question about S-Meter-Reading

Hi Richard,

Sounds like an awesome project - good on you.

As it happens, I've just finished getting STRENGTH data from an Icom-7300, so I can explain how that works. However, looking through various posts and the documentation, I suspect the return of STRENGTH information may not be perfectly aligned across various rigs.

The IC-7300 returns a dB figure, with 0dB corresponding to S9 - 50 microvolts into 50 ohms.
Given this, any positive number is dB above S9.
To determine S0 to S8, just consider that for each 6dB the STRENTH value decreases below S9, its one less S point

My implementation is  (Python, but probably valid C code as well)
spoint= 9 + ((int((levInt+1)/6))-1)
where levInt is the value returned by STRENGTH when negative
Any positive value of STRENGTH is just S9

Officially, S9 is really -73dBm, so if you want a dBm figure from the IC-7300, just subtract 73 from the STRENGTH amount.

Cheers
Steve
VK3SPX



On 13/04/2025 04:36, Richard Emling wrote:
Hello.


My name is Richard. I have been blind since birth and am currently working on a project that uses Hamlib to develop a system that helps blind individuals, especially those who are not very computer-savvy, to operate amateur radio transceivers. Particularly, people who have lost their sight later in life and older individuals often lack the ability to adapt to the changed situation and therefore require special assistance.

A Raspberry Pi hosts the Hamlib, transceiver functions can be controlled via a connected numeric keypad, and a speech output reads everything aloud.
Optionally, a MIDI controller can be connected to control the functions of the radio device.
Anyone interested in seeing the current progress of the project and willing to provide tips on how I might use some Hamlib functions more effectively is welcome to visit https://github.com/do9re/midi2hamlib .


My first question concerns reading the S-meter on a transceiver. As I understand it, the STRENGTH level provides this information.

But where can I find a conversion table that tells me which S-level corresponds to the read value?


I am excited to be part of the Hamlib family and look forward to a good exchange.


73

Richard (DO9RE)


_______________________________________________
Hamlib-developer mailing list
Ham...@li...<mailto:Ham...@li...>
https://lists.sourceforge.net/lists/listinfo/hamlib-developer


_______________________________________________
Hamlib-developer mailing list
Ham...@li...
https://lists.sourceforge.net/lists/listinfo/hamlib-developer

Re: [Hamlib-developer] Introduction and Question about S-Meter-Reading

[Richard E. <DO...@ho...>]

Oh, forgot to paste the right link.

https://github.com/DO9RE/midi2hamlib/blob/main/functions/levels/get_strength

73

Richard, DO9RE

Am 13.04.2025 um 11:07 schrieb Phil GM3ZZA via Hamlib-developer <ham...@li...>:


IIRC hamlib does its best to standardise all meter level readings for the different rigs. So S9 should always be a reading of 0 regardless of how the rig CAT encodes it.

Phil GM3ZZA

Get Outlook for Android<https://aka.ms/AAb9ysg>

________________________________
From: Stephen Pattinson via Hamlib-developer <ham...@li...>
Sent: Sunday, April 13, 2025 5:56:49 AM
To: ham...@li... <ham...@li...>
Subject: Re: [Hamlib-developer] Introduction and Question about S-Meter-Reading

Hi Richard,

Sounds like an awesome project - good on you.

As it happens, I've just finished getting STRENGTH data from an Icom-7300, so I can explain how that works. However, looking through various posts and the documentation, I suspect the return of STRENGTH information may not be perfectly aligned across various rigs.

The IC-7300 returns a dB figure, with 0dB corresponding to S9 - 50 microvolts into 50 ohms.
Given this, any positive number is dB above S9.
To determine S0 to S8, just consider that for each 6dB the STRENTH value decreases below S9, its one less S point

My implementation is  (Python, but probably valid C code as well)
spoint= 9 + ((int((levInt+1)/6))-1)
where levInt is the value returned by STRENGTH when negative
Any positive value of STRENGTH is just S9

Officially, S9 is really -73dBm, so if you want a dBm figure from the IC-7300, just subtract 73 from the STRENGTH amount.

Cheers
Steve
VK3SPX



On 13/04/2025 04:36, Richard Emling wrote:
Hello.


My name is Richard. I have been blind since birth and am currently working on a project that uses Hamlib to develop a system that helps blind individuals, especially those who are not very computer-savvy, to operate amateur radio transceivers. Particularly, people who have lost their sight later in life and older individuals often lack the ability to adapt to the changed situation and therefore require special assistance.

A Raspberry Pi hosts the Hamlib, transceiver functions can be controlled via a connected numeric keypad, and a speech output reads everything aloud.
Optionally, a MIDI controller can be connected to control the functions of the radio device.
Anyone interested in seeing the current progress of the project and willing to provide tips on how I might use some Hamlib functions more effectively is welcome to visit https://github.com/do9re/midi2hamlib .


My first question concerns reading the S-meter on a transceiver. As I understand it, the STRENGTH level provides this information.

But where can I find a conversion table that tells me which S-level corresponds to the read value?


I am excited to be part of the Hamlib family and look forward to a good exchange.


73

Richard (DO9RE)


_______________________________________________
Hamlib-developer mailing list
Ham...@li...<mailto:Ham...@li...>
https://lists.sourceforge.net/lists/listinfo/hamlib-developer


_______________________________________________
Hamlib-developer mailing list
Ham...@li...
https://lists.sourceforge.net/lists/listinfo/hamlib-developer

Re: [Hamlib-developer] Introduction and Question about S-Meter-Reading

[Richard E. <DO...@ho...>]

Hi.

Many thanks. So, did I interpret your words right with my script?

functions/levels/get_strength



73

Richard, DO9RE

Am 13.04.2025 um 11:07 schrieb Phil GM3ZZA via Hamlib-developer <ham...@li...>:


IIRC hamlib does its best to standardise all meter level readings for the different rigs. So S9 should always be a reading of 0 regardless of how the rig CAT encodes it.

Phil GM3ZZA

Get Outlook for Android<https://aka.ms/AAb9ysg>

________________________________
From: Stephen Pattinson via Hamlib-developer <ham...@li...>
Sent: Sunday, April 13, 2025 5:56:49 AM
To: ham...@li... <ham...@li...>
Subject: Re: [Hamlib-developer] Introduction and Question about S-Meter-Reading

Hi Richard,

Sounds like an awesome project - good on you.

As it happens, I've just finished getting STRENGTH data from an Icom-7300, so I can explain how that works. However, looking through various posts and the documentation, I suspect the return of STRENGTH information may not be perfectly aligned across various rigs.

The IC-7300 returns a dB figure, with 0dB corresponding to S9 - 50 microvolts into 50 ohms.
Given this, any positive number is dB above S9.
To determine S0 to S8, just consider that for each 6dB the STRENTH value decreases below S9, its one less S point

My implementation is  (Python, but probably valid C code as well)
spoint= 9 + ((int((levInt+1)/6))-1)
where levInt is the value returned by STRENGTH when negative
Any positive value of STRENGTH is just S9

Officially, S9 is really -73dBm, so if you want a dBm figure from the IC-7300, just subtract 73 from the STRENGTH amount.

Cheers
Steve
VK3SPX



On 13/04/2025 04:36, Richard Emling wrote:
Hello.


My name is Richard. I have been blind since birth and am currently working on a project that uses Hamlib to develop a system that helps blind individuals, especially those who are not very computer-savvy, to operate amateur radio transceivers. Particularly, people who have lost their sight later in life and older individuals often lack the ability to adapt to the changed situation and therefore require special assistance.

A Raspberry Pi hosts the Hamlib, transceiver functions can be controlled via a connected numeric keypad, and a speech output reads everything aloud.
Optionally, a MIDI controller can be connected to control the functions of the radio device.
Anyone interested in seeing the current progress of the project and willing to provide tips on how I might use some Hamlib functions more effectively is welcome to visit https://github.com/do9re/midi2hamlib .


My first question concerns reading the S-meter on a transceiver. As I understand it, the STRENGTH level provides this information.

But where can I find a conversion table that tells me which S-level corresponds to the read value?


I am excited to be part of the Hamlib family and look forward to a good exchange.


73

Richard (DO9RE)


_______________________________________________
Hamlib-developer mailing list
Ham...@li...<mailto:Ham...@li...>
https://lists.sourceforge.net/lists/listinfo/hamlib-developer


_______________________________________________
Hamlib-developer mailing list
Ham...@li...
https://lists.sourceforge.net/lists/listinfo/hamlib-developer

Re: [Hamlib-developer] Introduction and Question about S-Meter-Reading

[Phil G. <gm...@bt...>]

<html><body><div dir="auto">IIRC hamlib does its best to standardise all meter level readings for the different rigs. So S9 should always be a reading of 0 regardless of how the rig CAT encodes it.</div><div dir="auto"><br></div><div dir="auto">Phil GM3ZZA</div><div id="ms-outlook-mobile-body-separator-line" dir="auto"><br></div><div id="ms-outlook-mobile-signature" dir="auto">Get <a href="https://aka.ms/AAb9ysg">Outlook for Android</a></div><div dir="auto" id="mail-editor-reference-message-container"><br><hr style="display: inline-block; width: 98%;"><div id="divRplyFwdMsg" style="font-size: 11pt;" dir="auto"><b>From:</b>&nbsp;Stephen Pattinson via Hamlib-developer &lt;ham...@li...&gt;<br><b>Sent:</b>&nbsp;Sunday, April 13, 2025 5:56:49 AM<br><b>To:</b>&nbsp;ham...@li... &lt;ham...@li...&gt;<br><b>Subject:</b>&nbsp;Re: [Hamlib-developer] Introduction and Question about
 S-Meter-Reading<br></div><br>

  
    
  
  
    Hi Richard,<br>
<br>
    Sounds like an awesome project - good on you.<br>
<br>
    As it happens, I've just finished getting STRENGTH data from an
    Icom-7300, so I can explain how that works. However, looking through
    various posts and the documentation, I suspect the return of
    STRENGTH information may not be perfectly aligned across various
    rigs.<br>
<br>
    The IC-7300 returns a dB figure, with 0dB corresponding to S9 - 50
    microvolts into 50 ohms.<br>
    Given this, any positive number is dB above S9.<br>
    To determine S0 to S8, just consider that for each 6dB the STRENTH
    value decreases below S9, its one less S point<br>
<br>
    My implementation is&nbsp; (Python, but probably valid C code as well)<br>
    spoint= 9 + ((int((levInt+1)/6))-1)<br>
    where levInt is the value returned by STRENGTH when <u>negative</u><br>
    Any positive value of STRENGTH is just S9<br>
<br>
    Officially, S9 is really -73dBm, so if you want a dBm figure from
    the IC-7300, just subtract 73 from the STRENGTH amount.<br>
<br>
    Cheers<br>
    Steve<br>
    VK3SPX<br>
<br>
    &nbsp;<br>
<br>
<div dir="auto" class="moz-cite-prefix">On 13/04/2025 04:36, Richard Emling
      wrote:<br>
</div><blockquote>Hello.
<br>
<br>
<br>
      My name is Richard. I have been blind since birth and am currently
      working on a project that uses Hamlib to develop a system that
      helps blind individuals, especially those who are not very
      computer-savvy, to operate amateur radio transceivers.
      Particularly, people who have lost their sight later in life and
      older individuals often lack the ability to adapt to the changed
      situation and therefore require special assistance.
<br>
<br>
      A Raspberry Pi hosts the Hamlib, transceiver functions can be
      controlled via a connected numeric keypad, and a speech output
      reads everything aloud.
<br>
      Optionally, a MIDI controller can be connected to control the
      functions of the radio device.
<br>
      Anyone interested in seeing the current progress of the project
      and willing to provide tips on how I might use some Hamlib
      functions more effectively is welcome to visit
 <a href="https://github.com/do9re/midi2hamlib" class="moz-txt-link-freetext">https://github.com/do9re/midi2hamlib</a>&nbsp;.
<br>
<br>
<br>
      My first question concerns reading the S-meter on a transceiver.
      As I understand it, the STRENGTH level provides this information.
<br>
<br>
      But where can I find a conversion table that tells me which
      S-level corresponds to the read value?
<br>
<br>
<br>
      I am excited to be part of the Hamlib family and look forward to a
      good exchange.
<br>
<br>
<br>
      73
<br>
<br>
      Richard (DO9RE)
<br>
<br>
<br>
      _______________________________________________
<br>
      Hamlib-developer mailing list
<br>
      <a href="mailto:Ham...@li..." class="moz-txt-link-abbreviated">Ham...@li...</a>
<br>
      <a href="https://lists.sourceforge.net/lists/listinfo/hamlib-developer" class="moz-txt-link-freetext">https://lists.sourceforge.net/lists/listinfo/hamlib-developer</a>
<br>
</blockquote><br>
  

<br></div></body></html>

Re: [Hamlib-developer] Introduction and Question about S-Meter-Reading

[Stephen P. <st...@bi...>]

Hi Richard,

Sounds like an awesome project - good on you.

As it happens, I've just finished getting STRENGTH data from an 
Icom-7300, so I can explain how that works. However, looking through 
various posts and the documentation, I suspect the return of STRENGTH 
information may not be perfectly aligned across various rigs.

The IC-7300 returns a dB figure, with 0dB corresponding to S9 - 50 
microvolts into 50 ohms.
Given this, any positive number is dB above S9.
To determine S0 to S8, just consider that for each 6dB the STRENTH value 
decreases below S9, its one less S point

My implementation is  (Python, but probably valid C code as well)
spoint= 9 + ((int((levInt+1)/6))-1)
where levInt is the value returned by STRENGTH when _negative_
Any positive value of STRENGTH is just S9

Officially, S9 is really -73dBm, so if you want a dBm figure from the 
IC-7300, just subtract 73 from the STRENGTH amount.

Cheers
Steve
VK3SPX



On 13/04/2025 04:36, Richard Emling wrote:
> Hello.
>
>
> My name is Richard. I have been blind since birth and am currently 
> working on a project that uses Hamlib to develop a system that helps 
> blind individuals, especially those who are not very computer-savvy, 
> to operate amateur radio transceivers. Particularly, people who have 
> lost their sight later in life and older individuals often lack the 
> ability to adapt to the changed situation and therefore require 
> special assistance.
>
> A Raspberry Pi hosts the Hamlib, transceiver functions can be 
> controlled via a connected numeric keypad, and a speech output reads 
> everything aloud.
> Optionally, a MIDI controller can be connected to control the 
> functions of the radio device.
> Anyone interested in seeing the current progress of the project and 
> willing to provide tips on how I might use some Hamlib functions more 
> effectively is welcome to visit https://github.com/do9re/midi2hamlib .
>
>
> My first question concerns reading the S-meter on a transceiver. As I 
> understand it, the STRENGTH level provides this information.
>
> But where can I find a conversion table that tells me which S-level 
> corresponds to the read value?
>
>
> I am excited to be part of the Hamlib family and look forward to a 
> good exchange.
>
>
> 73
>
> Richard (DO9RE)
>
>
> _______________________________________________
> Hamlib-developer mailing list
> Ham...@li...
> https://lists.sourceforge.net/lists/listinfo/hamlib-developer

[Hamlib-developer] Correctly setting CTCSS tones?

[Richard E. <DO...@ho...>]

Hello everyone,

I would like to understand how to interpret the CTCSS tones from the 
--CAPS-DUMP list when transmitting them to the transceiver. They are 
listed with a decimal point. However, when I transmit them using the C 
command and later query with the c command, only the number before the 
decimal point is returned, as if the part after the decimal point is 
lost. What am I doing wrong?

Best regards,

Richard (DO9RE)

[Hamlib-developer] Introduction and Question about S-Meter-Reading

[Richard E. <DO...@ho...>]

Hello.


My name is Richard. I have been blind since birth and am currently 
working on a project that uses Hamlib to develop a system that helps 
blind individuals, especially those who are not very computer-savvy, to 
operate amateur radio transceivers. Particularly, people who have lost 
their sight later in life and older individuals often lack the ability 
to adapt to the changed situation and therefore require special assistance.

A Raspberry Pi hosts the Hamlib, transceiver functions can be controlled 
via a connected numeric keypad, and a speech output reads everything aloud.
Optionally, a MIDI controller can be connected to control the functions 
of the radio device.
Anyone interested in seeing the current progress of the project and 
willing to provide tips on how I might use some Hamlib functions more 
effectively is welcome to visit https://github.com/do9re/midi2hamlib .


My first question concerns reading the S-meter on a transceiver. As I 
understand it, the STRENGTH level provides this information.

But where can I find a conversion table that tells me which S-level 
corresponds to the read value?


I am excited to be part of the Hamlib family and look forward to a good 
exchange.


73

Richard (DO9RE)

[Hamlib-developer] ROTCTld usb0 issue on pi5

[Bob N. <bn...@gm...>]

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.
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
rot_open: error = 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
IO error

DEvice info from hamlib.

2401  BG5DIW                 GRBLTRK via Serial      20220515.0      Beta
       ROT_MODEL_GRBLTRK_SER
2402  BG5DIW                 GRBLTRK via Net         20220515.0      Beta
       ROT_MODEL_GRBLTRK_NET


-- 
Bob Nazro, W1RPQ
phone: (860) 941-7993
b <Jos...@cp...>na...@gm...

Re: [Hamlib-developer] guidelines or template for adding a new rig?

[Bill B. <bi...@wi...>]

Thanks George. I confess to being aware of that doc but not reading it 
as thoroughly as I should have.

On 4/11/2025 10:32 AM, George Baltz wrote:
> See README.developer in the top level directory of the source tree.
>
> On 4/11/25 12:40 PM, Bill Bennett wrote:
>> Some time ago I think I remember someone pointing to a guidelines or 
>> cookbook document, how to add a new rig to hamlib. But I can't find 
>> it... Does anyone know of such a thing, or more generally, any 
>> detailed guidance on how to get started?
>>
>> I am perhaps one of very few still using a Kachina 505DSP as the main 
>> daily rig here. There is a bare stub of an implementation - I'd like 
>> to flesh it out.
>>
>> Thanks for any suggestions.
>>
>> 73 - Bill N7DZ
>>
>>
>>
>> _______________________________________________
>> Hamlib-developer mailing list
>> Ham...@li...
>> https://lists.sourceforge.net/lists/listinfo/hamlib-developer
>
>
> _______________________________________________
> Hamlib-developer mailing list
> Ham...@li...
> https://lists.sourceforge.net/lists/listinfo/hamlib-developer

Re: [Hamlib-developer] rotctl-error

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

* On 2025 11 Apr 12:43 -0500, Henry Ketter wrote:
> Sorry the infomation was not complete:
> 
> I use Inerface IF-100 from AMSAT on /dev/parport0.

Hi Henry.

Welcome to Hamlib!  Sorry to hear you are having trouble.

To help us help you, please add '-vvvvv' to the rotctl command line and
post all of the output including the full command you used to start
rotctl.

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

Re: [Hamlib-developer] guidelines or template for adding a new rig?

[George B. <geo...@gm...>]

See README.developer in the top level directory of the source tree.

On 4/11/25 12:40 PM, Bill Bennett wrote:
> Some time ago I think I remember someone pointing to a guidelines or 
> cookbook document, how to add a new rig to hamlib. But I can't find 
> it... Does anyone know of such a thing, or more generally, any 
> detailed guidance on how to get started?
>
> I am perhaps one of very few still using a Kachina 505DSP as the main 
> daily rig here. There is a bare stub of an implementation - I'd like 
> to flesh it out.
>
> Thanks for any suggestions.
>
> 73 - Bill N7DZ
>
>
>
> _______________________________________________
> Hamlib-developer mailing list
> Ham...@li...
> https://lists.sourceforge.net/lists/listinfo/hamlib-developer

[Hamlib-developer] guidelines or template for adding a new rig?

[Bill B. <bi...@wi...>]

Some time ago I think I remember someone pointing to a guidelines or 
cookbook document, how to add a new rig to hamlib. But I can't find 
it... Does anyone know of such a thing, or more generally, any detailed 
guidance on how to get started?

I am perhaps one of very few still using a Kachina 505DSP as the main 
daily rig here. There is a bare stub of an implementation - I'd like to 
flesh it out.

Thanks for any suggestions.

73 - Bill N7DZ

[Hamlib-developer] rotctl-error

[Henry K. <dh...@t-...>]

Sorry the infomation was not complete:

I use Inerface IF-100 from AMSAT on /dev/parport0.

Have a niche weekend!

73 Henry

[Hamlib-developer] rotctl-error

[Henry K. <dh...@t-...>]

Hallo,

I use Yeasu-Rotor AZ/EL.
Befor update Hamlib all okay.

In Moment Problem :

Rotator command: R
Reset: 1
error = rotctl Hamlib 4.6.2 2025-02-09T21:03:50Z SHA=870364 64-bit
Report bugs to <ham...@li...>

rot_init called
initrots4_amsat called
rot_register (1201)
rot_token_lookup called lookup south_zero
rot_token_lookup called lookup south_zero
rot_set_conf called
frontrot_set_conf called
rot_open called
par_open called
ser_set_dtr: DTR=0
ser_set_dtr: Cannot change DTR - Invalid argument
ser_set_rts: RTS=0
ser_set_rts: Cannot change RTS - Invalid argument
Backend version: 20110531.0, Status: Stable
rotctl_parse: input_line: R
rot_reset called


Rotator command: p
error = rot_init called
initrots4_amsat called
rot_register (1201)
rot_token_lookup called lookup south_zero
rot_token_lookup called lookup south_zero
rot_set_conf called
frontrot_set_conf called
rot_open called
par_open called
ser_set_dtr: DTR=0
ser_set_dtr: Cannot change DTR - Invalid argument
ser_set_rts: RTS=0
ser_set_rts: Cannot change RTS - Invalid argument
Backend version: 20110531.0, Status: Stable
rotctl_parse: input_line: R
rot_reset called
Feature not available
rotctl_parse: input_line: p
rot_get_position called
Feature not available

Command P ist works.

Can you help?

73 Henry


Feature not available

[Hamlib-developer] [Hamlib/Hamlib] 285a86: Restore libtool default of building shared and sta...

[Nate B. <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 285a865d9ff9a0dff484b5c880f3d17097692175
      https://github.com/Hamlib/Hamlib/commit/285a865d9ff9a0dff484b5c880f3d17097692175
  Author: Nate Bargmann <n0...@n0...>
  Date:   2025-04-09 (Wed, 09 Apr 2025)

  Changed paths:
    M configure.ac

  Log Message:
  -----------
  Restore libtool default of building shared and static libs

Commit 43159e5 prevented the libtool default of building both shared and
static libraries during a compilation run.

This addresses GitHub issue 1500 that seeks to enable both shared and
static libs.

At this point, I have not found the motivation for commit 43159e5
despite searching all forums and the mailing list.  While the reason
might not now be ever known, restoring the default behavior alligns the
project with other software package.


  Commit: 34698df17acf6cc2ee72d3944b4149f0f621515a
      https://github.com/Hamlib/Hamlib/commit/34698df17acf6cc2ee72d3944b4149f0f621515a
  Author: Nate Bargmann <n0...@n0...>
  Date:   2025-04-09 (Wed, 09 Apr 2025)

  Changed paths:
    M configure.ac

  Log Message:
  -----------
  Merge pull request #1694 from N0NB/static_lib

Restore libtool default of building shared and static libs


Compare: https://github.com/Hamlib/Hamlib/compare/d8a3aac62587...34698df17acf

To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications

[Hamlib-developer] Builds of shared and static libraries

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

Going through the issue list I found issue #1500:

https://github.com/Hamlib/Hamlib/issues/1500

Wherein Mike notes that it should be possible to build both shared and
static libraries.  I thought that odd as I seemed to recall that in the
past both were built as SOP.  I spent some time with configure and its
options and not working out why it was either/or.

Not thinking (we could probably stop right there) that it was anything
to do with Hamlib I posted to the libtool mailing list seeking some
help:

https://mail.gnu.org/archive/html/libtool/2025-04/msg00005.html

A kind soul by the name of Simon helped out and pointed out a section in
our configure.ac file that sets the variables that control shared and
static libraries in an exclusive OR fashion.  The use of 'git blame'
showed this section was added in the following commit:

https://github.com/Hamlib/Hamlib/commit/43159e55a1c4351199fada21eb6be4632001d930

My testing shows that commenting that section enables the default
libtool behavior of building both shared and static libraries and
dynamically linking the executables (rigctl, etc.) to the shared
library.  I've also tested the Windows 32 and 64 bit binaries and I
don't see any build issues (I've not tested run time).

I've looked through the closed issues, the discussion and mailing list
archives, and even my private mail and don't see anything that prompted
that commit.  Even more puzzling is the opening of the issue two and a
half months later.

Regardless, it is my intent to temporarily revert that commit by
commenting the relevant lines and seeing who yells.  🤔

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

Re: [Hamlib-developer] Building Python bindings

[Phil <phi...@gm...>]

On 8/4/25 21:49, George Baltz wrote:
>
> You need to add PYTHON_VERSION=3 to the command.
>
Thank you George. Using the python binding is going to keep me occupied 
for quite some time.

-- 
Regards,
Phil