You are here

Wrong frequency shown in Frequency field in New QSO window

7 posts / 0 new
Last post
Wrong frequency shown in Frequency field in New QSO window


After several years of happy usage, suddenly the frequency field shows wrong values. For instance, I have my IC7300 now tuned in 7190 and field shows 153.040. I move the dial and the frequency on the field changes but with wrong values.

And amazingly I call wsjtx from the application and frequencies of FT8 QSOs are transferred and shown properly.

No changes in the configuration were made, at least on purpose. My Hamblib version is 4.5.
I have the following parameters in TRX control window:

Path: /usr/local/bin/rigctld
RIG Model: 3073 Icom IC-7300
Host: localhost
Device: (port of the radio, no issue with this)
Poll rate: 500
Port number: 4532
Run rigctld when program starts: checked
SErial speed: 19200 (checked that same than in radio)
Data bits: default
Stop bits: default
Parity: default
Handshake: None

Please help??!!??

Wrong frequency shown in Frequency field in New QSO window


Please try this.
In command console give command:
rigctld --version

And command:

whereis rigctld

And paste those answers to your message.

Have run (or automated run) any linux updates recently when this started?
Could it be that your linux has now two versions of rigctld?

I have just seen same kind of report in Cqrlog Telegram forum. The difference of rig and TRXConsole was always 145.850, same as you have.
In that case you should remove all Hamlibs and then install just the 4.5 version.

I have feeling that some "__buntu" now update Hamlib so that there are rigctld in /usr/bin and /usr/local/bin and then the library may point to wrong version according to rigctld that is running.


VikaGreg (not verified)
Achten Sie darauf, eine

Achten Sie darauf, eine vertrauenswürdige und lizenzierte Casinoseite zu wählen. Es gibt viele Seiten, die nicht seriös sind, daher ist es wichtig, dass Sie sich vor der Auswahl einer Seite auf informieren.

Frequency update

I have noted a problem with updating the frequency shown on the rig vs what is displayed in CQRlog. Rig: K4, using Hamlib NET rigctl. Rigctld string /usr/bin/rigctld --model=2047 --rig-file=/dev/ttyUSB1 --port=14532 --serial-speed=115200 --set-conf=C cache_timeout=0. CQRlog version 2.6.0(116) Gtk2. Hamlib version 4.6.

On starting CQRlog, frequency displays correctly.
Same band frequency change from CQRlog #1 - may or may not update radio. Does not update CQRlog displayed frequency
Next change from CQRlog: updates CQRlog to last frequency change. Does not update radio
Next change: band change - updates radio and CQRlog
Next change: band change - updates radio, does not update CQRlog
Band buttons in TXR control change bands properly; both radio and CQRlog update

I scoured the forums for Hamlib to see if this was a known problem, but it does not appear to be.
I see the same behavior for CQRlog with my FT-991A, running locally on my laptop as a profile, launching rigctld from CQRlog. K4 is launched separately because the K4 is connected to a different computer than the one running CQRlog. This all ran flawlessly in the past. Is this a CQRlog bug in 2.6.0 (116) or should I look elsewhere? JS8call and WSJT-X seem to change frequencies appropriately using Hamlib.

73, Charles - NK8O


Frequency update

Hi Charles!

Do you use TRXcontol's frequency display (click+enter freq+enter) to change frequency ? (when "same band, frequency change")

Or do you use mouse roll (TRXControl freq click and then roll)? That one does work if roll is turned a lot and fast. Rig does not follow and may get overflow. It works just on small changes properly. (caused by rig communication design in Cqrlog)

Would you please tell how to reproduce changes that do not work. So far I have not noticed similar with my IC7300 that I also run via Hamlib Net rigctld.

What is "in past"? Different Hamlib version and/or different Cqrlog version, what versions?

Note that JS8call and WSJT-X should also use "Hamlib NET rigctld" even when they are running in same computer that have rig connected.
Otherwise there can be collisions in rig communication if they are using named rig model instead of Hamlib NET rigctld.

You could check "preferences/TRXControl/Show communication with TRX in console" and then start Cqrlog from command console.
Then you will see if the frequency change command comes from Cqrlog and what rig responses to it.

For testing it may be good to increase poll rate (poll delay) so that you can catch all lines of communication.


Frequency update

Dear Saku,

Typically I was just entering frequency in the "Call" box and hitting enter. When Hamlib 3.3 was installed it worked well. You have alerted me to a new feature - I was unaware of the "click and roll" in the TRX control, I suppose because I never had to use it before. It seems to work. The "Call" box is convenient because using it there is no need to change the focus field to use the Function key macros, or to enter a new callsign. Nonetheless if the TRX control solves the problem I will use it. WSJT-X and JS8Call don't seem to care if CQRlog is running. Since there are typically only band changes involved, I haven't run into any problems. I'm using logging WSJT-X with Remote mode for wsjtx.

Also, I will soon be receiving an updated laptop with a fresh Ubuntu 20.04 install, more memory, and a larger HD. I will compile the latest CQRlog specifically for that machine and see what happens. When I get that up and running I will do a clean install of Ubuntu 22.10 and do the same experiment with a clean complie of CQRlog and see if I still get the same behavior. After I have done some proper clean installs I will see if I still have the problem. There are several things squirrely on this laptop after a couple of upgrades from Ubuntu from 20.04 to 22.04 to 22.10. If I have problems, then I will send the debug information. Thanks for the quick reply and new tricks for CQRlog.


Charles - NK8O


Frequency update

Hi Charles!
Still wondering what is "Call" box that enables to adjust rig frequency?
Do you mean NewQSO window's Frequency column, or what?
Cqrlog has so many properties that I may have missed some.

Remember about TRXControl's "click->roll->new click" is meant just for fine tune. Not for large jumps. Use "click -> Ctrl+A -> enter completely new frequency->press enter" for that.

BTW test also what happens if you press SHIFT, or CTRL or BOTH during rolling ! (Perhaps see the help too :-)

Fine if you do not have problems running JS8/WSJT and Cqrlog. As I do not know your station setup I still recommend you to read this just for future.