[Elecraft] [K3] MCU 4.47 serial recovery

[Wayne Burdick]

Leigh,

No firmware changes were made that should affect this. All I did was  
provide more robust rejection of ill-formatted commands that were  
coming from HRD and other programs when allowed to poll at too fast a  
rate. I heard from over a dozen users of various programs that this  
change completely cleared up the artifacts they had seen.

I suspect buffer overrun by multiple programs combined polling too  
quickly.

73,
Wayne
N6KR

On Jan 29, 2012, at 5:44 PM, Leigh L. Klotz Jr WA5ZNU wrote:

> I've noticed that the ability of the K3 to "recover" from  
> disturbances in
> RS232 isn't what my memory of it used to be.
>
> For example, if I start a second program sending query commands the  
> the K3,
> I can never get it to answer any more serial commands.  My belief is  
> that it
> used to eventually get back in sync.  I've verified this with my own  
> serial
> programs and also with k3util.  For example, when it's stuck, it  
> won't reply
> to "FA;" at all until power cycle.  (Other rig operation other than  
> RS232 is
> unaffected.)
>
> I don't know if it's related to the input parsing code in the K3 or  
> if it's
> related to some DTR state that gets asserted briefly during the  
> serial port
> open.  But I can't find any reliable way to clear this other than  
> rig power
> cycle.  Resetting the K3 baud rate from the front panel, for example,
> doesn't cause it to come back.
>
> Leigh/WA5ZNU
>
>
> --
> View this message in context: http://elecraft.365791.n2.nabble.com/K3-MCU-4-47-serial-recovery-tp7235321p7235321.html
> Sent from the Elecraft mailing list archive at Nabble.com.
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:Elecraft at mailman.qth.net
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html