Hi,
Running 2.4.0 on Linux Mint 19 and bleeding edge (source pull) gpredict and hamlib.
When in new QSO screen with Satellite tab selected there is a space for "RX Frequency".
Above on the same screen is the Frequency that is read in from the radio that IS the RX Frequency.
Since all (assumption) satellite work is done in split mode, can you not use the hamlib get_split_freq to get the TX frequency?
That leaves the question, Shouldn't the space on the satellite tab be "TX Frequency" and could it not be filled in automatically with data from get_split_freq?
Thanks Randy
Have same issue. Agree with your recommendation
Hi!
Added to Alpha version 2.6.0(124) date 2024-02-26
--
Saku
OH1KH
Perhaps the best solution to cover all types of transceivers is to have a setting that allows user to select which VFO is recorded as the frequency field when the transceiver is in split mode. Currently the AVFO is recorded but in split frequency mode my transceiver transmits on the BVFO.
Hi!
Starting point is that Icom rigs can not answer get_vfo command.
So there is no way to use vfo information globally.
Logging should always be done with TX frequency. That is what the telecommunication authors are interested in.
Using rigctld get_split_freq it gives "Get 'TX Frequency', in Hz." It does not take side what vfo will be used.
When get_split_freq is used the frequency is moved to TRXControl display and from there it always goes to NewQSO/freq column.
Other vfo's frequency shows up in NewQSO/satellite tab as rx frequency if Lofreq tab has RX lo cheked vith value 0.0. It is also saved as rxferquency when qso is logged.
Cheking Tx lo as well as Rx lo and use other values than 0.0 allows rig ( HF rig) to be used with transverter and still use also get_spit_freq.
Or make crossband qsos like 60/50 or 40/50 MHz qsos.
--
Saku
OH1KH
Please clarify. Should CQRLOG v 2.5.2 be properly logging my TX and RX frequencies properly in split mode or is that capability coming in 2.6? If it should be doing this in 2.5.2 it is not. I have manually sent the rigctl commands you mention below to my Yaesu FT-991A and it gives the correct replies for split mode and split frequency. However CQRLOG v2.5.2 is only reading one vfo(RX) and putting that in the “Frequency” field. No data is being populated in the “RX frequency” field of the Satellite tab.
Hi.
2.5.2 reads just one vfo. Rxfreq is generated from Rxlo multiplier, or typed in directly.
2.5.2 is over two years old. You should try alpha 2.6.0.(124) instead.
I added get_tx_vfo checkbox to it.
Update script can be found from https://github.com/OH1KH/cqrlog/tree/loc_testing/compiled
Waiting for next official version might take time and at the moment it does not have this feature.
--
Saku
OH1KH
Tried installing 2.6 via the script file. Now CQRLOG will not launch and I get this message.
cqrlog: error while loading shared libraries: libgdk-x11-2.0.so.0: cannot open shared object file: No such file or directory
Hi!
Did you select right version for your mint 19?. Is it 32bit operating system?
That will show up at scirpt start.
You can always return to old version. Go to /usr/bin folder.
You find file cqrlog there. That is the updated version.
Then there is another cqrlog file with date and time in name. That is your old cqrlog.
Just copy that file with date and time in name to name cqrlog an you can start your old cqrlog again.
From command terminal it would be like:
sudo cp cqrlog-20240101-010101 cqrlog
Of course your date-time of filename is different, and note you need sudo to touch /usr/bin contents.
Same way you can restore help folder in /usr/share/cqrlog folder.
But that is only if you need old help, it does not affect cqrlog running.
You do not need to restore old cqrlog if you try update script again.
In that case remember that the original cqrlog is the one with oldest date-time in name.
--
Saku
OH1KH
Not sure what "mint 19" is refering to? I am running the latest Raspberry PI OS 64bit on a RPI4. When it gets to the Make your selection step I was choosing 3. I also tried option 7 and I get the same error message.
So I decided to try and build 2.6.0 (124) from source following your instructions. It now seems to be working. I will use it going forward and let you know if I have any issues. Under the LO config tab I clicked the "Use split TX freq" and it is now populating the Frequency field with the actual TX freq.
Thanks for you help and patience. Keep up the good work on this app.
Dave
Sorry Dave. Just rolled back to top, but did not check the thread origin callsign.
I think it is mentioned that ready compiled version is done with rpi4 32bit version.
So only thing to do is to compile from source for rpi 64bit.
Nice to hear that you got it working!
You need also check rx lo with multiplier 0.0 to get the rx frequency from other vfo.
--
Saku
OH1KH
This version seems to be reading both vfo in split mode correctly but I observed some issues.
1) Previously I could double tap the ESC key to clear a log entry in process that I wanted to cancel and start over. With this version that seems to kill the TRX polling. I have observed the change in polling messages when running with "Show communication with TRX in console" and starting up from terminal. If I clear and start new entry over by using Ctrl+F2 all is well and things work as normal.
2) If I get into the state described in 1 above I can restore comms to the TRX by using Refresh TRX/ROT control in the file menu. However even though Use split TX freq is still checked to be active it is only polling one frequency. To get split to work again I need to un-check and then re-check the Use split TX freq.
Hope this observation and feedback is helpful.
Hi!
1) procedure: enter a callsign to NewQSO - press TAB to get RST sent column - press 2xESC to cancel qso.
If I do this it does not stop rig polling. Tested several times and always polling continues.
Having NewQSO/Auto check box checked or not.
Do I have wrong procedure?
2) Does it really poll only +f? Or do you just get same response to +i and +f ? See the communication with rig in console.
With my IC7300 I can make "one frequency" appear of I switch A/B vfos while Split is on at rig.
Cqrlog polls still with +f and +i but gets same response for both commands even if I use A/B again and set VFOs as they were in beginning.
Restarting rigctld will fix this.
--
Saku
OH1KH
Attached is a file containing console output when I run cqrlog from the console.
You can see program is initially polling correctly.
After about 32 polls I entered a call sign in new qso window and tabbed to the RST field then I hit 2xESC.
You can see that the polling stops with a message :
"Queue in:
+\stop_voice_mem
Queue Sending[0]:+\stop_voice_mem
Queue out:
Polling - allowcommand:-1
Polling - allowcommand:-1
Polling - allowcommand:-1"
Then I click the Refresh TRX/ROT control and the polling restarts without the -i command.
Then I toggle the Use split TX freq and then polling continues with the -i command and operation is back to normal.
I hope this helps.
I will download the new source and re-compile later next week as I will be away from home for a few days.
File:
HI!
Very good report again!
Now I know where to seek. I was using CW mode all the time.
It looks like your rig does not respond to +\stop_voice_mem command.
What happens if you open telnet connection
telnet localhost 4532
when cqrlog is running and type in command
+\stop_voice_mem
I am interested to hear the result. For me it works like this:
[saku@hamtpad ~]$ telnet localhost 4532
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
+\stop_voice_mem
stop_voice_mem: currVFO
RPRT 0
Cqrlog keeps waiting for "RPRT" and some number. It seems like your rigctld does not give any response.
At start of debug dump I can see that your rig should support that command: "Cqrlog can launch voice memories: TRUE"
You can also try to uncheck preferences/TRXControl "Send rig voice" of used rig's setup.
I think it should help as quick fix, but of course prevents using rig's internal voice memories.
Perhaps I should make counter for "Polling - allowcommand:-1" messages and release waiting after something like 10-20 counts.
--
Saku
OH1KH
I telnet to my rigctld service and the +\stop_voice_mem does not provide a response.
Actually when I do "rigctld --help" it does not even list that command as valid for rigctld. It does have the send_voice_ mem command but not the stop.
Not sure what to make of that.
I am running this version of rigctld - rigctl Hamlib 4.5.4 Jan 10 01:31:41Z 2023
I am now running CQRLOG 2.6.0(125). Thanks for the fixes and work arounds. I appreciate how quickly you have looked into my issues.
Hi!
There is now fixed source that should release "Polling - allowcommand:-1" after 15 tries. Of course then sent command does not pass through rig and maybe rigctld gets confused for a while.
How ever it should not hang up polling if rig and rigctld just can survive from false command/response missing.
--
Saku
OH1KH
HiI
2) bug was found: Value of checkbox was not read at rigctld init. Default is "not checked" that was used. Should now read correct value.
1) Can't make happen. can not fix.
Added read of "+s" and if split is 0 TX vfo is not used even it is polled by "+i" all the time "use TX split freq" is checked.
This should work, but not with IC7300. Once Split is set OFF from rig and after a while set ON again ICOM still shows only one frequency for TX and RX.
Root reason is that rigctld has a fake "get_vfo" for icoms as they can not respond to +v. That fake system gets mixed when spilt is switched on and of from rig button.
State can be fixed by clicking buttons A and B of TRXControl/Vfo in right order when Spit is ON again at rig side. What a mess.
--
Saku
OH1KH
Forgot to say: There is fixed source in GitHub
--
Saku
OH1KH
Do the ICOM rigs support the RIGCTL "s" command, which is "get_split_vfo"? You said they don't support the "v" command. The "s" command returns a 0 for not split and a 1 for split on my Yaesu. You could then trigger off of that to determine if you only use "f" command or also use the "i" command to get the split TX freq.
Thanks for reports.
I use same version and use ESC, never Ctrl+F2, and have not noticed that kind of problem.
On the other hand I usually do not use split so I have test this more carefully.
Same as I have to test rigctld "s" with Icoms. I assume it does not work as "v" does not work either. I'll test that too.
Using it for automated switching may cause unwanted effects. For example if rig is off when starting cqrlog.
--
Saku
OH1KH