Rigctld not working

10 posts / 0 new
Last post
Rigctld not working

My rigctld has stopped working. I am using 2.6.0_122-Gtk2 Alpha. When I run whereis -b rigctld I get /usr/bin/rigctld /usr/local/bin/rigctld which is two diferent paths. Hamlib version in synaptic is 4.3.1-1 build 2. My WSJTX Hamlib version is 4.6. WSJTX rigctld works just fine. I tried switching the rigctls path in CQrlog to the WSJTX version with no luck. My guess is that somehow a second path has appeared and is causing rigctld to not work - how can I fic this?

73, Bill NZ0T

OK, I looked in synaptic and

OK, I looked in synaptic and it shows cqrlog 2.5.2-+-1 and cqrlog-data installed and not the alpha 2.6 I m using. It does not show the 2.6 alpha at all. Do I need to completely remove the 2.5.2-1? This is really weird because the 2.6 alpha rigctld was working fine until today.

cqrlog no cat control

hi as new here please be gentle
cannot get cat control to work in cqrlog
NOTE it works in fldigi , wsjtx no problem
below is terminal debug?

Cqrlog Ver:2.5.2 (001) Date:2021-02-12
**** DEBUG LEVEL 0 ****
**** CHANGE WITH --debug=1 PARAMETER ****

Linux version 6.1.0-17-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.69-1 (2023-12-30)

RigCtldArgs:-m 1042 -r /dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0 -t 4532 -s 4800
RunRigCtld: TRUE
RigDevice: /dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0
RigPoll: 500
RigId: 1042

Starting RigCtld ...
rigProcess.Executable: /usr/bin/rigctld

rigctld started!
Connected to rigctld @ localhost:4532
Sending: fmv

Sending: fmv

WARNING: TGtk2WidgetSet.InvalidateRect refused invalidating during paint message: TStringGrid
Sending: fmv

cqrlog no cat control

So far looks good.
Open two command terminals. Keep Cqrlog, fldigi, wsjtx closed.
In first one type one line:
/usr/bin/rigctld -m 1042 -r /dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0 -t 4532 -s 4800 -vvvvv

If there seems to be no errors and promt does not come back leave terminal window open and jump to the other terminal window and type
telnet localhost 4532

You should get conneted to rigctld running in other terminal.
And enter
Then look at rigctld terminal. What happens there? Any errors?
You can try also with separate letters in telnet terminal
Do you get any replay for them? How about errors in rigctld terminal?

When you end test you can just close terminals.

Remember that you can not run Cqrlog and wsjtx or fldigi with same rig model number if they are running at same time.
See: https://github.com/OH1KH/cqrlog/blob/loc_testing/compiled/setting_rigctl...


Rigctld not working

Hi Bill.
If you get two paths for rigctld then you have somehow got two of them installed. Usually packet install installs /usr/bin path and self compile default is /usr/local/bin.
Ubuntu has had updates where it has suddenly installed new rigctld to /usr/local/bin.
In that case the other one in /usr/bin should disappear
If your wsjtx Hamlib works you should find rigctld-wsjtx from either of rigctl paths you have.
You can put that to Cqrlog preferences path to rigctld.

You can test rigctld versions by starting them from command terminal using full path you got from whereis command like this:
/usr/local/bin/rigctld --version

Try whereis also with rigctld-wsjtx, and when found test also -- versin of it.
Select latest version fot testing with Cqrlog.

You have updated to alpha 2.6.0 with script. That is not packet install and synaptic still thinks version is 2.5.2. Does not affect, but if your system ever updates packet 2.5.2 then you need to run update script again to get alpha back.


Hi Saku,

Hi Saku,

for some reason rigctld is working agin even thoughj I stil;l have the two paths when I run whereis -b rigctld. I have /ust/local/bin in the path which is what has always been there. Guess we will see if it keeps working.

73, Bill NZ0T

w4bru's picture
Same failure, ow to fix

Bill, on my Raspberry Pi (Raspbian GNU/Linux 11 (bullseye)) CQRLog stopped working this weekend (with three great contests running! QRZ logging is slow.). Last weekend and for the last several months it has work well. This seems a sudden failure.

It starts fine from the terminal ad flrig works flawlessly. I checked he terminal session and the desktop session and they both have "/usr/local/bin/rigctld". For the desktop "Preferences TRX Control RIG model" does not allow a selection so it doesn't seem to ""see" hamlib. Do you know how yours got "fixed"? I'd like to get mine "fied".

dk9he's picture
Hi Bill,

Hi Bill,
it sounds your that hamlib is no more installed well and anyway gone. Could you please check the solid installation of hamlib?

Andy DK9HE

w4bru's picture
Suddenly CQRlog reconnected

I tried rebooting the computer and turning CQRlog on and off and nothing worked. I was busy on the bands so logged via QRZ, a bit slow and clumsy. Later that day I started CQRlog and it connected and has been working correctly for a few days!

dk9he's picture
Rigctld not working

Again a bit off topic...
Bill, let me mention, the alpha 2.6.0 runs here always very stable like also the 2.5.2. I'm using it every day with much fun.
Take care you running environment.
73 and gl

Distro: Kubuntu 22.04.