You used -m 606 before.
- rotctld -m 606 ____
Engagein Gpredict- netstat -n | grep 4533
Either 606 or 603 will work, however when I do either
rotctld -m 606 -r /dev/ttyACM0
or
rotctld -m 603 -r /dev/ttyACM0
all that happens is I get a flashing cursor and nothing happens, even after Engage in Gpredict
It seems to be a problem with rotctld, could it be anything do with permissions?
I re-did this command and got this:
m0jtl@ian-Shack:~$ rotctld -m 606 -r /dev/ttyACM0 --port=4533 -vvvvv | tee -a /home/m0jtl/rotctld.txt
rotctld, Hamlib 4.6~git 2024-05-30T22:34:02Z SHA=745e72 64-bit
Report bugs to hamlib-developer@lists.sourceforge.net
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
rot_open called
serial_open: /dev/ttyACM0
serial_open(230): open failed#1 Permission denied
serial_open(230): open failed#2 Permission denied
serial_open(230): open failed#3 Permission denied
serial_open(230): open failed#4 Permission denied
serial_open: Unable to open /dev/ttyACM0 - Permission denied
rot_open: error = 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
rot_open called
serial_open: /dev/ttyACM0
serial_open(230): open failed#1 Permission denied
serial_open(230): open failed#2 Permission denied
serial_open(230): open failed#3 Permission denied
serial_open(230): open failed#4 Permission denied
serial_open: Unable to open /dev/ttyACM0 - Permission denied
IO error
Run
sudo usermod -aG dialout m0jtl
to add your user to the group dialout and try again.
I have been informed by EA4TX to use 601 in Hamlib, not 606, so I did your command
sudo usermod -aG dialout m0jl
and this is what I got, I still get the cursor just blinking when itâs done and I canât do anything apart from close Terminal
Is this correct now?
It seems to me, I maybe wrong that Hamlib is working but itâs Gpredict that isnât working correct
I still get nothing when i run the command:
netstat -n | grep 4533
it just goes to the command prompt
First, the group membership did it, now the permission denied error has gone.
The cursor blinking after the rotctld command is normal.
And you have to leave this terminal window open.
If you close it, rotctld will quit.
601 seems to me a better approach.
The RCI-USB emulates a Yaesu GS232A interface, so any
program that supports this tracker interface with work with it.
(ARS-USB Reference Manual, page 21)
And
rotctl -l | grep GS-232A
will show you
601 Yaesu GS-232A 20220109.0 Stable ROT_MODEL_GS232A
However, please also try 1101:
1101 EA4TX ARS RCI AZ&EL 20200112.0 Stable ROT_MODEL_RCI_AZEL
rotctl -l will give you a list.
So again:
- Start rotctld (601 or 1101) and leave the terminal window open with a blinking cursor.
- Engage Gpredict
- netstat -n | grep 4533
I am thinking 1101 is not correct as I get this:
m0jtl@ian-Shack:~$ rotctld -m 1101 -r /dev/ttyACM0
rot_open: error = rotctld, Hamlib 4.6~git 2024-05-30T22:34:02Z SHA=745e72 64-bit
Report bugs to hamlib-developer@lists.sourceforge.net
rot_init called
initrots4_ars called
rot_register (1102)
rot_register (1101)
rot_open called
par_open called
par_open: PPSETMODE â/dev/ttyACM0â: Inappropriate ioctl for device
IO error
so 601 is the way to go
However when I try to Enagae Gpredict and do
netstat -n | grep 4533
it just goes to the command prompt
It seems to me that Hamlib is communicating with the EA4TX controller, but Gpredict isnât communicating with Hamlib, it doesnât seem to be sending information on port 4533
I know when I run it in Windows 10 I use PCSat32 and I have to set a virtual port up for the ARS software and when getting JTDX or WSJT-X to work on my radio I had to change the permissions to m0jtl on the ttyUSB2
I donât know what has happened, but I switched the EA4TX controller off and back on, it was reassigned ttyACM1 and I changed the permissions from root to me and run netstat -n | grep 4533 and got this:
m0jtl@ian-Shack:~$ netstat -n | grep 4533
tcp 0 0 127.0.0.1:4533 127.0.0.1:40614 ESTABLISHED
tcp 0 0 127.0.0.1:40614 127.0.0.1:4533 ESTABLISHED
now it seems to be working and at the moment it is tracking the ISS 
1 Like
Is there anyway of making Hamlib starting up with you boot the PC, as I can only get Gpredict running when I run rotctld -m 606 -r /dev/ttyACM1 in Terminal and leave it open
Iâd say one quick solution is @reboot in cron, search for âcrontab rebootâ and youâll find guides.
Is it really always ACM1?
And you donât have to use a terminal window. This was only for testing.
You may just run
rotctld -m 606 -r /dev/ttyACM1
from WIN+R
When searching for serial devices, I usually use the convenient aliases that is set up automagically.
ls -lR /dev/serial/
looks like:
/dev/serial/:
total 0
drwxr-xr-x 2 root root 60 Nov 4 2023 by-id
drwxr-xr-x 2 root root 60 Nov 4 2023 by-path
/dev/serial/by-id:
total 0
lrwxrwxrwx 1 root root 13 Nov 4 2023 usb-u-blox_AG_-_www.u-blox.com_u-blox_GNSS_receiver-if00 -> ../../ttyACM0
/dev/serial/by-path:
total 0
lrwxrwxrwx 1 root root 13 Nov 4 2023 platform-3f980000.usb-usb-0:1.4:1.0 -> ../../ttyACM0
These are pretty nice as they keep the name, using the by-id lets you choose the correct one even if thereâs a lof of ttyUSBx. although not all programs support using symlinks, but most do.
in my example: /dev/serial/by-id/usb-u-blox_AG_-_www.u-blox.com_u-blox_GNSS_receiver-if00 will always point to the correct device.
another example on a computer with two usb-serial:
lrwxrwxrwx 1 root root 13 Jun 1 14:24 usb-1a86_USB2.0-Serial-if00-port0 -> ../../ttyUSB0
lrwxrwxrwx 1 root root 13 Jun 1 14:24 usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_05670031BD0A-if00-port0 -> ../../ttyUSB1