Yes this is a known issue, however, I found if you raise threshold to 15 and slope to 2 that it performs slightly better. I was using it along with Fldigi with good success this weekend. Zambia on 10m and Liechtenstein on 17. Both new ones thanks to the K3 decode and fldigi.
We are all waiting for the next iteration of a substantive fix for this situation and I'm sure the Elecraft folks are hot on it. Keith AG6AZ Sent from my iPhone please excuse typos On Sep 24, 2012, at 8:28 AM, "Jim - W6VAR" <w6...@comcast.net> wrote: > I updated firmware a few weeks ago and recntly noticed the CW decode feature > appears to be working differently. > > I used to be able to adjust the threshold on band noise until the flickering > stopped and a signal would cause the indicator to flicker. > > Now, the indicator flickers regardless of the setting on band noise and > spews unintelligible characters accross the display until a signal is > detected, then it decodes and the indicator looks correct, until there is a > sufficient pause at which point the indicator flickers again and more > jibberish is displayed. > > Has anyone else experienced this? > > Jim > > > > -- > View this message in context: > http://elecraft.365791.n2.nabble.com/K3-CW-Decode-FW-04-51-tp7563207.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@mailman.qth.net > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html ______________________________________________________________ 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
