I think W1UE is already a very proficient CW operator! I had the ERR Key
message while operating as WP2AA this month. If I recall it was from
accidentally plugging the headphones into the PTT connection of the Heil
mic adapter. It was a little bit of a scare just minutes before the ARRL
DX Phone contest started! Assuming that everything is wired correctly,
could there be a timing issue with your N1MM PTT?

GL,
John KK9A


Cady, Fred fcady at montana.edu
Mon Mar 28 09:12:10 EDT 2016

Hi Dennis,
Good for you!  N1NN+ is great and CW contesting is even better.
There are a couple of programs that will help you improve your copy for
call signs and numbers.  These are Morse Runner and Rufz.
http://www.dxatlas.com/morserunner/
http://www.rufzxp.net/

Morse runner even simulates N1MM in a pileup and you can adjust the speed,
pileup conditions etc.
Rufz sends one call at a time and if you get it right, ups the speed for
the next one, wrong, slows down a notch.

Try to develop the following habits:
In Morse Runner Hit enter to start sending the call before you type the
last letter of the call.
In Rufz when speeds get high, let the whole call go by before you type it it.

Use these a few minutes each day and you will be amazed how much better
you will be.
73,
Fred KE7X

For all KE7X Elecraft books, see www.ke7x.com

________________________________________
From: Elecraft <elecraft-bounces at mailman.qth.net> on behalf of Dennis
<egan.dennis88 at gmail.com>
Sent: Monday, March 28, 2016 5:54 AM
To: elecraft at mailman.qth.net
Subject: [Elecraft] ERR KEY

This past weekend I experienced numerous ERR KEY messages. According to
the manual, this ERR code is returned when one "attempts to key the
transmitter or activate PTT during power on". When this would happen,
there was no power turn on, nor shorted keying lines- it was in
operation with N1MM+ in an SO2R mode.

What else would cause that error message?  If I tried to key the radio
before the PTT had been fully asserted, would I get that error?  I am
thinking that there is some connection between that error message and
some timing elements of the PTT/Keying process that I could correct.

I have another op that is getting this error in an unrelated setup. We
are both using the latest K3 firmware, 5.38.

Dennis W1UE

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to arch...@mail-archive.com

Reply via email to