I am trying to get CQRLog to key my Elecraft K4 radio's built-in voice memories via the use of keyboard Fx (Function keys) just like on CW.
When I am using Windoze 10 and N1MM logger for contests, there is a VERY simple command that can be easily modified in a text editor to execute a radio command via CAT control. The command to use in the N1MM program is: {CAT1ASC PB1;} This command tells the radio to use CAT and send radio memory push button #1, in which I have recorded my CQ message. The radio can store up to 8 different voice messages PB1 - PB8.
I looked at this old thread (https://www.cqrlog.com/node/2326) related to an Icom radio, but it seems quite complex and involved and WAY more effort than I want to try and get into. There HAS to be a simpler way to make this happen. Any thoughts?
Bob, WG9L
Linux Mint 20.3
CQRLog Ver 2.6.0 (001) Gtk2
Bob, you need to update.
Update your Hamlib to latest one by doing compile from GitHub source.
Update Cqrlog to Alpha (124) or (125) if you like to compile it by yourself.
With those updates you can send voice messages by F-buttons when mode is ssb, am, fm. Either with old external voice script that plays voice file to rig's audio, or use rigctld command to launch rig's internal voice memories. Selecton "Send rig voice" is in preferences/trxcontrol.
--
Saku
OH1KH
Hi, Saku.
Related to (https://www.cqrlog.com/node/3825)
Thanks for your information. What is the easiest way to upgrade my version of Hamlib? It looks like the most recent, stable release is, Hamlib 4.5.4 I'm still a noob and am unsure of the best way to get this utility downloaded and installed. Any help would be appreciated.
Thanks,
Bob, WG9L
I decided to wipe my old Linux Mint version 21 and do a fresh install of Mint 22. Then I installed Mariadb and CQRLog Alpha 130 and upgraded my version of HAMLIB to 4.5.5. Everything works perfectly, except for voice keying the radio. The CQRLog help information for using a radio that has an internal voice keyer contains no information. I have tried every option I can think of in order to get the logging program to execute a command to send the voice keyer internal messages in my radio.
TRX control setting of "Send rig voice" is checked.
I MUST be missing something. Can you assist?
TNX.
Bob, WG9L
HI!
I have fixed help files, but that appears only at source until 131 of CqrlogAlpha is released.
Everything is based on Hamlib's rigctld commands. If they do not work Cqrlog does not work.
While Cqrlog is is running and your rig is connected (I.E: Cqrlog shows right frequency) open command terminal and start telnet with command:
telnet localhost 4532
Then type line (ended with return key):
\dump_caps
You get many lines. Try to find line:
Can send Voice: Y
If there is "Y" rigctld shoud be able to launch voice messages. In case of "N" it is not possible with your rig model.(In that case it might work with latest Hamlib, if the current one you are using is very old. You have to update then)
If the answer is "Y" then try to launch voice message manually from telnet connection with command:
+\send_voice_mem 1
Be sure that before you press return key an the end of command line your rig is in phone mode and that internal message #1 has some contents to send.
if internal message is sent OK it should look like:
[saku@hamtpad ~]$ telnet localhost 4532
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
+\send_voice_mem 1
send_voice_mem: currVFO:1
RPRT 0
If your rig is in wrong mode the "RPRT" will show "-9" instead of "0". Same if the contents of internal message is empty (at least with Icom 7300)
If you succeed to launch message with telnet connection Cqrlog should also succeed with it if "Send rig voice" is checked and your rig is in phone mode (by Cqrlog)
If you can't do it with telnet you maybe need to upgrade Hamlib.
See https://github.com/Hamlib/Hamlib
There are good instructions in file "INSTALL"
You get the source code to your computer by pressing green "code" button and selection "Download zip"
--
Saku
OH1KH
I tried to update to the latest version of HAMLIB (v4.6) using the written instructions on the hamlib web site but couldn't quite figure out exactly how to do it. The instructions looked fairly easy but I ran into problems with missing dependencies. Then today I found this YouTube video: https://www.youtube.com/watch?v=iUOfsOnOmvQ that showed how to install hamlib from source on a Raspberry-Pi. I am using Linux Mint 22, but the instructions seemed to be very similar so I decided to try it, and it worked perfectly - exactly as shown on the YouTube video.
I now have HAMLIB v4.6 successfully installed and operating correctly. Unfortunately, even with this latest version, I still cannot make my Elecraft K4 send an internal voice memory from CQRLOG. When I type in the commands in a terminal window:
telnet localhost 4532
\dump_caps
hamlib reports "Can send Voice: N"
It's obvious that hamlib is still not updated enough to key the voice keyer messages in my K4. Unfortunately, It looks like I will still need to wait for this to be implemented. I'm quite sad that this is the case, and am hopeful that it will get updated soon. On a side note, keying the K4 voice memories is super easy on Windows and N1MM, however my daily logger is CQRLOG. I need to be patient, I guess.
Bob
WG9L
Hi Bob!
Just downloaded latest Hamlib from GitHub this morning to study a bit your case.
I am not familiar with C programming language but have used it a bit.
When digging down to hamlib/rigs/kenwood I found that file k3.c has something
----cut-----
And further on...
By all this it looks like there is voice_mem support with K4.
Are you sure you have latest Hamlib running? If you have installed ham programs that have Hamlib in dependencies list they have installed it and it is some of the old versions.
Now when you compile Hamlib from source you should somehow get rid of the package installed Hamlib and have just the one you did compile.
With Fedora it is very easy with command "rpm --erase --nodeps hamlib". That removes Hamlib even when there are programs that need it.
With Ubuntu and varants I do not know how to do it.
Try "whereis -b rigctld" command in console. Do you get several answers?
if you start "rigctld --version" from console does it report proper version, and is the date ok
Check the lib64 folder do you have several "libhamlib" there. If any.
Self compiled Hamlib should set its library (if defaults used) to /usr/local/lib and there the libhamlib should have the date of your compile.
I tried to start rigctld using K4 model, but because I have not one I can not do \dump_caps and see what it says.
--
Saku
OH1KH