I upgraded from Mint 20.3 to Mint 21. CQRLOG works great except when I use a rig not connected to the computer and TRX control. There is a 0 (zero) permanently in the frequency display in TRX control and the NEW QSO frequency display. I cannot erase the 0 and when I try to manually enter a frequency it always reverts back to the 0. TRX control and New QSO frequency displays work perfectly when I'm using a rig connected to the computer.
Any help appreciated!
73, Bill NZ0T
Hi Bill!
If your rig is not connected you should not check "run rigctld when program stars".
Then your TRXcontrol shows 0.00000 and you can select predefined frequencies from NewQSO/Frequency selector box.
If you have one of the latest versions of Cqrlog you can select rig #1 "Hamlib Dummy" and you see "run rigctld when program stars" grayed and checked (thing that tells you have new enough version of Cqrlog) and keep NewQSO/Auto checkbox checked.
That way you should see 145.00000 in TRXControl window and you can set bands and modes with TRXControl buttons that may be more convenient way to enter frequency and mode than using NewQSO frequency and mode selector boxes.
--
Saku
OH1KH
Hi Saku,
I am running 2.5.2 (001). I tried unchecking "run rigctld when program starts" and restarting but the 0 is still there and I can't manually enter a frequency. If I select "Hamlib Dummy" nothing is grayed out. So no change here. I am running Hamlib 4.3.1-1 build 2 and Mint 21 which is based on Ubuntu 22.04.
Hi Bill,
I am using Ubuntu Mate 22.04. I start CQRLOG with checked "run rigctld when program starts". I use 1 Radio at place "Radio 1", the second place is leaved untouched. When I start CQRLOG, I also open the window "TRX Control". When I choose in this window radio 1, it is connected to my TRX. When I choose radio 2, I can enter the frequency manual. Maybe this option works also at your side.
73, Hardy DL8YDU
I re-started my computer (duh) and now I can enter frequencies manually as before. Not sure why but glad it's fixed. But I accidentally erased the "Path to rotary binary" (don't ask) and after I re-entered "/usr/bin/rotctld" I get and error "rotctld binary not fount, cannot load list of supported rotators! Fix path to rotctld in ROT control tab." when I click on preferences. I don't use rotor control so it's no big deal just annoying. How can I fix that?
73, Bill NZ0T
Hi Bill!
It looks like rigctld left running as daemon and that kept your "0". Restart killed rigctld and "run rigctld when program starts" not checked made it.
also command line
ps ax | grep rig
would have shown still running rigctld process and
killall rigctld
would have killed it without reboot. But reboot is always one choice that Windoze has learned to us, hi.
Cqrlog should kill rigctld that it has started in normal situations. Missing rig or some other problems may sometimes prevent that.
Cqrlog needs rigctld and rotctld path to fill the rig and rotor model selection boxes with supported model names as they depend on the used version of Hamlib.
The splash warns user for missing information. There is no way Cqrlog could know would you like to set up rig or rotor, or not.
Only way to fix it is to set right paths for rigctld and rotctld. As Hamlib is required for Cqrlog both programs, that are parts of Hamlib, should be installed with Cqrlog.
I recommend to upgrade to Cqrlog 2.6.0. Then you can use rig #1 "Hamlib dummy" and can set freq/mode from TRXControl form.
You can either compile it from source. Forum has many threads about that, or upgrade from my ready built files with update script at https://github.com/OH1KH/cqrlog/tree/loc_testing/compiled
I think that none of Linux distributors have yet made package from version 2.6.0
--
Saku
OH1KH
I don't think any of the distributions will package a 2.6.0 until there is an official release, and the website has an official tarball. Until then it's just like a Release Candidate.