K3S bug in FW Beta 5.46 Keyer Memories

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

K3S bug in FW Beta 5.46 Keyer Memories

Jim Sheldon
Just found a bug in the keyer memories when programming for PSK/RTTY.  
The memory loads fine until you send the ..__ (IM) character to
terminate transmission and then it locks up as if you had a constant
"key down" with a hand key.  I was programming memory 4 to call CQ on
RTTY when I discovered this.  I tried the other memories and got the
same results.  It never did this on the K3 I used to have so I don't
know if it's unique to the K3S or whether it does this on the K3 as
well.

Whoever is handling the FW for the K3/K3S might want to take a look at
this as it could get annoying.  The anomaly only shows up when
programming the memories, not when sending direct with the paddles and
the IM character does terminate transmission as it should.  It just
causes the keyer to hang when the IM character is sent during memory
programming.

Anyone Else notice this?  (Can't be RFI as there is no RF output during
CW memory programming).  Can't call Support as they don't give any help
on Beta FW.

Jim - W0EB

______________________________________________________________
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: K3S bug in FW Beta 5.46 Keyer Memories

Mike Harris-9
And where is Beta 5.46 hidden? Some of us like to live on the edge.

Regards,

Mike VP8NO

On 25/05/2016 10:35, Jim Sheldon wrote:

> Just found a bug in the keyer memories when programming for PSK/RTTY.
> The memory loads fine until you send the ..__ (IM) character to
> terminate transmission and then it locks up as if you had a constant
> "key down" with a hand key.  I was programming memory 4 to call CQ on
> RTTY when I discovered this.  I tried the other memories and got the
> same results.  It never did this on the K3 I used to have so I don't
> know if it's unique to the K3S or whether it does this on the K3 as well.
>
> Whoever is handling the FW for the K3/K3S might want to take a look at
> this as it could get annoying.  The anomaly only shows up when
> programming the memories, not when sending direct with the paddles and
> the IM character does terminate transmission as it should.  It just
> causes the keyer to hang when the IM character is sent during memory
> programming.
>
> Anyone Else notice this?  (Can't be RFI as there is no RF output during
> CW memory programming).  Can't call Support as they don't give any help
> on Beta FW.
>
> Jim - W0EB
______________________________________________________________
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: K3S bug in FW Beta 5.46 Keyer Memories

Nr4c
In reply to this post by Jim Sheldon
Did you actually input "..--" or did you use the "|" vertical bar or "pipe" symbol?  The "|" is mentioned in the K3 utility under CONFIG/Edit CW memories I think. It works for RTTY, PSK and is not processed on CW so it had no effect on CW. One set of messages works for all.
Also I noted you used the underscore instead of a dash. This might also be an issue.

Sent from my iPhone
...nr4c. bill


> On May 25, 2016, at 9:35 AM, Jim Sheldon <[hidden email]> wrote:
>
> Just found a bug in the keyer memories when programming for PSK/RTTY.  The memory loads fine until you send the ..__ (IM) character to terminate transmission and then it locks up as if you had a constant "key down" with a hand key.  I was programming memory 4 to call CQ on RTTY when I discovered this.  I tried the other memories and got the same results.  It never did this on the K3 I used to have so I don't know if it's unique to the K3S or whether it does this on the K3 as well.
>
> Whoever is handling the FW for the K3/K3S might want to take a look at this as it could get annoying.  The anomaly only shows up when programming the memories, not when sending direct with the paddles and the IM character does terminate transmission as it should.  It just causes the keyer to hang when the IM character is sent during memory programming.
>
> Anyone Else notice this?  (Can't be RFI as there is no RF output during CW memory programming).  Can't call Support as they don't give any help on Beta FW.
>
> Jim - W0EB
>
> ______________________________________________________________
> 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]
Reply | Threaded
Open this post in threaded view
|

Re: K3S bug in FW Beta 5.46 Keyer Memories

Mike Reublin NF4L
In reply to this post by Mike Harris-9
I'm sure the elves would like to hear about a flaw in a release, beta or not.

73, Mike NF4L

> On May 25, 2016, at 9:55 AM, Mike Harris <[hidden email]> wrote:
>
> And where is Beta 5.46 hidden? Some of us like to live on the edge.
>
> Regards,
>
> Mike VP8NO
>
> On 25/05/2016 10:35, Jim Sheldon wrote:
>> Just found a bug in the keyer memories when programming for PSK/RTTY.
>> The memory loads fine until you send the ..__ (IM) character to
>> terminate transmission and then it locks up as if you had a constant
>> "key down" with a hand key.  I was programming memory 4 to call CQ on
>> RTTY when I discovered this.  I tried the other memories and got the
>> same results.  It never did this on the K3 I used to have so I don't
>> know if it's unique to the K3S or whether it does this on the K3 as well.
>>
>> Whoever is handling the FW for the K3/K3S might want to take a look at
>> this as it could get annoying.  The anomaly only shows up when
>> programming the memories, not when sending direct with the paddles and
>> the IM character does terminate transmission as it should.  It just
>> causes the keyer to hang when the IM character is sent during memory
>> programming.
>>
>> Anyone Else notice this?  (Can't be RFI as there is no RF output during
>> CW memory programming).  Can't call Support as they don't give any help
>> on Beta FW.
>>
>> Jim - W0EB
> ______________________________________________________________
> 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]