Hi,
So, I had to upgrade the old shack PC to something newer, and I lost my real RS232 ports... I've not had much issue with usb-->serial in the past, but this has me a bit stumped.
Running rigctld/hamlib 1.2.15.3 and cqrlog 1.9.0. What I've noticed is that cqrlog will start up and not see the rig. If I run in debug mode I see rigctld (usually) pop up, and then cqrlog report that it's connected. If I telnet to 4532, or whatever rigctld port, I can issue rigctl commands (say f) and get responses. The only way to get cqrlog to wakeup and talk is to go in and make a change in Pref-->TRX, like change the polling. Then it'll follow the rig OK.
I've tried starting rigctld by hand, verifying that it is up, and then starting cqrlog (telling cqrlog not to start rigctld) and have similar issues.
Anyone have any ideas why it needs a slight kick to chat? Waiting for a while to see if eventually it starts polling info from rigctld doesn't seem to change anything.
*note*
Further playing with the dummy rig seems to indicate that things behave as expected on startup; I can have cqrlog manage rigctld, and then I can telnet into the dummy rig and set frequencies and have them appear in cqrlog. I will experiment a bit more with real rig and see what I can replicate.
Can anyone explain if cqrlog stops talking to rigctld for some reason? (command timeout, or botched reply from rigctl?) I wonder if there is some issue with rigctld talking to the rig; but only sometimes.
73's
Joe KC0VKN
It must just happen on startup; Playing with it it seems that once it's talking, CQRLog keeps talking to rigctld, and rigctld keeps talking to the rig.
I'll experiment more and see if I can come up with a fix.
I have the same issue. I have to "tweak" the polling value by "changing" it from 500 to 500 (yes, same value) and saving preferences. Then everything snaps to and works great.
I discovered this because of another issue I have. Once I start cqrlog and open my logbook, it takes somewhere around 15 seconds for the log to populate with contact information if I double click on a spot in the cluster window. I tried resetting polling and a number of things, but no joy. However, if I then select and open another log and then tweak the polling as described above, it works fine. So I have to start cqrlog by opening a dummy log first, then selecting and opening my real log and then reset polling to get rigtctl to work right.
Anyone else? Petr looked into this for me a couple of years ago and never found a cause. I suspect it has more to do with rigctl and the USB dongle used to replace the hardware COM port than with cqrlog itself. This issue happened with two separate laptops, and is the same regardless of which Linux distro I am using (Ubuntu or Fedora).
Cheers,
Dave, N1KX