ERR KEY

[Dennis Egan]

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:[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]

[Gerry Hull]

Were you remote, Dennis?

I notice on the VY1AAA remote, if the sequencing is not right, I would get
ERR_KEY on the rig as well.
It seemed to happen just as I was logging a QSO (no ESM, just VOX).

This was Windows 10 locally, with the RRC.  I wonder if this is the dreaded
serial overlap issues that the N1MM and Microbit team has discovered
(manifests itself by causing WinKey to stop sending after a few characters
on CW.)   May be a completely different issue.

Gerry W1VE

Gerry Hull, W1VE   | Hancock, NH USA | [phone]
AKA: VE1RM | VY2CDX | VO1CDX | 6Y6C | 8P9RM
<http://www.yccc.org> <http://www.yccc.org/>
<http://www.facebook.com/gerryhull>
<https://plus.google.com/+GerryHull/posts>     <http://www.twitter.com/w1ve>

On Mon, Mar 28, 2016 at 7:54 AM, Dennis <[hidden email]> wrote:

> 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:[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]
>

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

[Dennis Egan]

I do have an op that is having problems with this in conjunction with
his Remote Rig setup, but that wasn't the case for me this past
weekend.  No remote rig was involved this past weekend.

Dennis W1UE

On 3/28/2016 8:23 AM, Gerry Hull wrote:

> Were you remote, Dennis?
>
> I notice on the VY1AAA remote, if the sequencing is not right, I would
> get ERR_KEY on the rig as well.
> It seemed to happen just as I was logging a QSO (no ESM, just VOX).
>
> This was Windows 10 locally, with the RRC.  I wonder if this is the
> dreaded serial overlap issues that the N1MM and Microbit team has
> discovered (manifests itself by causing WinKey to stop sending after a
> few characters on CW.)   May be a completely different issue.
>
> Gerry W1VE
>
> Gerry Hull, W1VE   | Hancock, NH USA | [phone]
> AKA: VE1RM | VY2CDX | VO1CDX | 6Y6C | 8P9RM
> <http://www.yccc.org><http://www.yccc.org/>
> <http://www.facebook.com/gerryhull>
> <https://plus.google.com/+GerryHull/posts> <http://www.twitter.com/w1ve>
>
> On Mon, Mar 28, 2016 at 7:54 AM, Dennis <[hidden email]
> <mailto:[hidden email]>> wrote:
>
>     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:[hidden email]
>     <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] <mailto:[hidden email]>
>
>

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

[Cady, Fred-2]

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 <[hidden email]> on behalf of Dennis <[hidden email]>
Sent: Monday, March 28, 2016 5:54 AM
To: [hidden email]
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:[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]

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

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:[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]

[Richard Ferch-2]

Dennis,

Some questions that might perhaps throw some light on what is happening:

What method are you using for CW keying? Are you using PTT control in CW?
How is N1MM+ configured to do CW and PTT keying?

One particular area to look at:

What is CONFIG:PTT-KEY set to on the K3? In the N1MM+ configuration is the
CW/Other check box checked for the radio control port, and what are DTR and
RTS set to for that port?

73,
Rich VE3KI

________________________________________
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:[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]