Running CQRLOG built from current git - when I try to look at log on my laptop away from shack I get a warning about radio did not respond (or some such); when I hit OK, I get Access Violation popup.
Never had that problem with a paper logbook :-)
Mon, 2025-01-20 20:32
#1
Current loc_testing won't start without radio
Hi!
Thanks for pointing out this.
I have made big changes to rig control, but missed testing without any rigs. I need to add rig model "NoRig" to selection list.
As the branch name "loc_testing" says it is for testing.
If problems, check daily if you compile from source. Version date will tell you the current state.
Ready compiled ones are more stable versions.
If you want to compile at level of ready compiled ones (134) give command:
git reset --hard 9caae774
before compile. That should bring you to level of (134) version.
git pull
Returns you back to current state, if needed.
I am moving stable versions to repository CqrlogAlpha, but there are only ready compiled ones now. Not yet the source of same version.
--
Saku
OH1KH
Uh, you scared me.
I started to test this issue because I was afraid there is a bug in case rig was not defined at all.
How ever I did not find any issue.
From preferences/TRXcontrol I cleared rig (paint the exisiting model and press delete) and unchecked "Run rigctld when program starts"
Started CqrlogAlpha version (135), version date 2025-01-20. All went fine. No error splash.
Then opened command console and typed:
ps ax | grep rig
To ensure that no rigctld was running.
All ok. I can not see any problem here.
If you start your computer without radio, that is defined in CqrlogAlpha preferences, there should be error splash as you rig does not answer.
That is not a bug.
When you clear out the splash you are still able to use your CqrlogAlpha to do all things you can without radio.
Tested also with rig defined and if rigctld did not start I got error splash from it. If rigctld started but I did pull rig USB out I got splash that I should check rig cables and power ON.
In both cases closing the splash did not cause any error. CqrlogAlpha opened normally (but without rig control functions, of course).
What is the version date of your compile?
--
Saku
OH1KH
My bad. I did not describe the problem fully, so let me do it right.
I do almost all my ham computing on my laptop(using openSUSE Tumbleweed) - operating, logging, programming, mailing lists, etc. Obviously when I'm operating it is connected to my rig. Other times, it's not. When I'm away from the rig, I sometimes fire up cqrlog; maybe to look at the statistics, watch the cluster in the background, etc. Before it would start silently without a connection.
Now it brings up a window complaining about the radio not responding - if I click OK on that window (without connecting to the rig - it's out on the back porch, and I'm inside where it's warm), the next thing I get is a 'Access Violation'. I click Abort.
CQRLOG is built from the latest loc_testing; hamlib also built from git. CQRLOG config has 'Open last log on start' checked, log config has rig defined and 'Run rigctld when program starts' checked - just as they have been for the past 2 years.
OK, thanks for details.
Latest bug fix for rig control is at 2025-01-13. Latest version is 2025-01-21 (date shown at bottom left of QSO list window)
Will try again test to find a way to produce Access violation (I have left one combination to try).
Would you please try to set "Preferences/TRXControl/Show communication with TRX in console"
and then start cqrlog again from command console:
cqrlog > /tmp/debug.txt
and after closed by Access violation attach file /tmp/debug.txt to your forum message.
Thanks!
--
Saku
OH1KH
Hi!
Good news!
I can reproduce this, so it might be that also the bug can be found!
While testing I also found a bug (or property) from new rigctld (2025-01-21).
It can not find rig if rig's speed settings are different than "auto" or "115200" and "Unlink from [remote]"
All other speeds, and also always if "Link to [remote]" is set, Preferences/TRXControl must have right serial speed set instead of "Default".
If these settings are not correct rigctld will start and allow telnet connection (localhost 4532) like it would work normally but if any command is sent there will be no response ever.
--
Saku
OH1KH
Hi!
Please try now source version date 2025-01-23.
It looks like I managed to fix that.
At least It did not happen any more with several tests while it happened every time with previous version.
--
Saku
OH1KH
BTW:
It looked like to happen only with QT5 and QT6 versions, not GTK2.
And it did not happen when running from lazarus-ide debug.
Only when started compiled binary from system.
--
Saku
OH1KH
Looks like that fixed it. i could open my log when not connected to rig.