Re: K3S - N1MM+ CW Message Transmit Decode Question

[Richard Ferch-2]

N1VH wrote:

> Any idea why the K3S decodes the CW message transmission using the CAT
> command, but not the MYCALL command?  I have verified that the radio is
> transmitting in both cases.  I have tried various decode threshold values
as well.

First off, when you use the CAT command the radio is not decoding
transmitted CW at all, it is simply echoing the ASCII text you sent to it
in the command.

Second, the only transmitted CW the K3/K3S can decode is keying from the
paddle input to the radio's internal CW keyer. Keying input from a straight
key, a computer or an external keyer, whether it comes into the radio on
the DTR line of the radio control port or via the CW Key jack, does not get
decoded.

73,
Rich VE3KI
______________________________________________________________
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]

[Jim Brown-10]

On 8/18/2017 1:05 PM, Richard Ferch wrote:
> Second, the only transmitted CW the K3/K3S can decode is keying from the
> paddle input to the radio's internal CW keyer.

And if we want to program K3 or K3S memories, we must either send with a
paddle connected to the K3/K3S keyer port or program them using the
K3/K3S Utility. That's one reason that, even though my primary paddle
feeds a WinKey compatible keyer in my YCCC SO2R box, I always have
separate paddles connected directly to both radios in my SO2R setup.

73, Jim K9YC

______________________________________________________________
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]