search

n4af / TR4W

TRLOG 4 Windows free amateur radio logging application
GNU General Public License v3.0
19 stars 6 forks source link

Add function key commands for <MESSAGE1>, <MESSAGE2>...<MESSAGE8> #639

Closed ny4i closed 1 year ago

ny4i commented 1 year ago

Rather than require the user to code a command sequence, add support for sending the values of DVK memory 1 - 8. This will be different for each radio that supports it. I will start with Elecraft of course. Note the K4 commands are different than the K3.

ny4i commented 1 year ago

The pattern for this would be just turning the RIT off so the radio objects should implement functions called PlayMessage(msgNum: integer)

ny4i commented 1 year ago

We also need a command to say StopMessage to hit call when an ESC is hit. Note some radios may not support interrupting the message. Elecraft does.

ny4i commented 1 year ago

Icom 7610 command is 28, no sub cmd, 00 to stop voice memory, 01 - 08 to play voice memory 01 - 08 respectively so 280001 to play voice memory 1.

The 7300 is the same command as I suspect are others.

ny4i commented 1 year ago

K3 is SWT01; to play memory 1 and SWT04 to play memory 04. K3 just has 4 memories.

ny4i commented 1 year ago

Some Yaesu radios support Playback with the PB command. On the FT-710 for example, PB00 to stop, PB01 to play memory 1 and PB05 to playback memory 5 (it goes up to 5).

ny4i commented 1 year ago

I have the basic support now in ProcessCommands. The commands ended up being PLAYMESSAGE_ACTIVE and PLAYMESSAGE_INACTIVE. I am not sure if it would ever be needed to play a voice message on the inactive radio but this seems more flexible.

I still do not like that we have to embed a <03> CTRL-C and terminate with a <04> CTRL-D. That is really clunky. I guess I am not sure why we really need to have that anymore. I would still support it as I am sure there are plenty of macros that have it, but I do wonder if I could change the code to just look for the command if CTRL-C is not the first character of a command.

n4af commented 1 year ago

Hi Tom - I see

ny4i commented 1 year ago

Not quite. I’ll be ready after I test it out this weekend. TomPrincipal Solutions ArchitectBetter Software Solutions, Inc. 727-437-2771On Mar 23, 2023, at 6:19 AM, Howie Hoyt @.***> wrote: Hi Tom - I see

[new branch] voice-msg-commands -> origin/voice-msg-commands Is this ready to integrate ? It would be 4.120.4 ?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were assigned.Message ID: @.***>

ny4i commented 1 year ago

Kenwood commands as follows:

ny4i commented 1 year ago

To play messages, instead of adding the actual CAT commands, you can include commands to PLAYMESSAGE and the program figures out what commands to send to the radio. For example, 

[Messages]
CQ SSB MEMORY F1=<03>PLAYMESSAGE_ACTIVE=1<04>
CQ SSB MEMORY F1 CAPTION=DVK M1
CQ SSB MEMORY F2=<03>PLAYMESSAGE_ACTIVE=2<04>
CQ SSB MEMORY F2 CAPTION=DVK M2
QSL SSB MESSAGE=<03>PLAYMESSAGE_ACTIVE=3<04>

You can of course still send native commands the regular way with the SRS commands but this saves you having to look this up. You can also set the commands in the O section of the P. The above example shows where I set the QSL SSB Message to play a memory. SO when I am calling CQ, this plays memory 3 after I hit ENTER to log the callsign.

I have not tried the INACTIVE memory as I do not have two radios setup. Also, this was only tested on a K4 using both TCP/IP and a serial connection. I have not checked it against Icom or Yaesu but the commands are from the manual. This has to be tested.

For a list of radios that support this feature, please consult the WIki page Radios that Support Voice Keying Commands