K3/P3: RX; Macro command behavior change

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

K3/P3: RX; Macro command behavior change

NK7Z
Hi,

I have a set of macros stored in the P3.  One of them is "RX;"  Another
is a CQ message, a 5NN, or my call.  I trigger them via a keyboard, or
via a Genovation Keypad connected to the P3.

In the past, the RX; command, (sent via Genovation, or Keyboard), would
drop the K3 into receive mode no matter what was happening, no matter
how it was triggered, no matter what was going on.  That behavior seems
to have changed recently.

Today I noticed that if I send a CW message via the macro method,
(loading the the message via a trigger from the P3), when I issue an RX;
command in the middle of the transmit sequence, nothing happens, (the
radio continues to transmit), if on the other hand, the message was
triggered using one of the K3 memories, and I issue the RX; command, it
stops dead in it's tracks, as it used to do, and as I believe it is
intended to do.  

In the past the RX; command used to behave exactly the same for either a
macro generated message, or a message sent via K3 memory.  This behavior
appears to have changed.  

Is this by intent, or a software issue with the last update?  This began
after the last update.

To reproduce the problem perform the following steps:

1.  Load up a message into a memory of the P3.
2.  Load up an RX; command into a memory of the P3.
3.  Send the message by triggering the P3.
4.  While the message is transmitting, issue a trigger to send the RX; 
    command.
5.  The old behavior was to stop the transmit.  The new behavior is to 
    ignore the RX; command, and continue until the message is complete. 
    It is as if the RX; command was never issued.
6.  Now, trigger a message by pressing one of the M buttons on the K3.
7.  While it is transmitting, issue the RX; via the P3 trigger.  The K3 
    stops, as it should, and has in the past. 

Could Elecraft comment on this please.  Is it an issue, and if so, will
it be corrected in a future software release?  

I use the RX; in this manner because-- if I am in a pileup and sending
my call over and over again, I sometimes want to stop transmitting
instantly, because I heard something, or I mis hit a trigger.  

In the past I just issued an RX; via the P3.  Now that fails if I have
triggered my call sign via the P3, but works if the memory is used to
send my call.

-- 
73's, and thanks,
Dave (NK7Z)
For software/hardware reviews see:
http://www.nk7z.net


--
73's, and thanks,
Dave (NK7Z)
For software/hardware reviews see:
http://www.nk7z.net



______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: K3/P3: RX; Macro command behavior change

Joe Stone (KF5WBO)
The RX command can't be used in CW mode with the K2,

RX (Receive Mode; SET only)
SET format: RX; (no data). Terminates transmit in all modes, including message play and repeating messages. RX/TX status is available via the TQ command and is also included in the IF response. Note: RX is not usable in CW mode in the K2.


Esc is a P3 command,

Pressing Esc stops the transmission and clears any unsent text.

Joe Stone
KF5WBO