Rigctld

3 posts / 0 new
Last post
N0NC
Rigctld

Lots of people are having problems with TRX control, Rigctld, But after 4 years of reporting bugs it still not fixed.

repost from earlier

I've been having this problem since 2013. I start rigctld at boot, it works fine with fldigi, gMFSK, and Xlog. Repeated program starts and stops have no effect, rigctld survives. With CQRLOG, the first time the program starts, it connects to rigctld, and works normally. When I close CQRLOG, rigctld crashes with the message broken pipe.

Here is a snippet from the terminal window where I ran rigctld.

root@devuan:/home/dad# rigctld -m 125 -r /dev/ttyS0 -s 4800 &
[1] 9791
root@devuan:/home/dad#
root@devuan:/home/dad# pidof rigctld
9791
root@devuan:/home/dad# pidof rigctld
[1]+ Broken pipe rigctld -m 125 -r /dev/ttyS0 -s 480

Also, if you refresh TRX control, rigctld crashes with same message.

I don't think that rigctld likes the way CQRLOG disconnects from it on program closure. However fldigi, Xlog, and gMFSK do not cause rigctld to die.

I'm running CQRLOG vers. 2.0.4

oh1kh
Rigctld

Hi!
Since version 2.0.4 the rigctld has been very stabile. (I'm running now 2.0.5 testversion).

What version of hamlib do you use? ( rigctl --version You should get 3.1 )
Have you UNchecked preferences/TRX control/"Run rigctld when program starts" as you start it manually ?

Your serial speed seems to be rather slow. What is the preferences/TRX control/"Poll rate" ? It should be something from 1500 upwards with that serial speed.

--
73 Saku
OH1KH

--
Saku
OH1KH

on4ezj
on4ezj's picture
Hi all,

Hi all,
After a long time of try and errors with my setup to get it stable, I found some hints.
My main problem was the fact that every manipulation at the rig (TenTec Omni VII - later also Orion) caused rigctld to stop working.
here is my command string for rigctld that finally works:
rigctld -m 1611 -r /dev/ttyS0 -t 4532 --set-conf=timeout=10000.0 -s 57600 --set-conf=data_bits=8,stop_bits=1,serial_handshake=None
It helps to add the config of data_bits, stop_bits and handshake - don't know why but it works ...
I think the timeout- parameter (in mS) is self-explaining.
Concerning the serial parameters, the manual of your Yaesu says : “4800,N,8,2” (4800 baud, No Parity, 8 Data Bits, and 2 Stop Bits)
So you should try:
rigctld -m 125 -r /dev/ttyS0 -t 4532 --set-conf=timeout=10000.0 -s 4800 --set-conf=data_bits=8,stop_bits=2 &
Let us know if this helps please.
73 de Peter - ON4EZJ