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 |
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" <[hidden email]> 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:[hidden email] > > 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:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html |
In reply to this post by Jim - W6VAR
On 9/24/2012 8:27 AM, Jim - W6VAR 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. Long standing issue with 4.51, it's on the list for the next update. 73, Fred K6DGW - Northern California Contest Club - CU in the 2012 Cal QSO Party 6-7 Oct 2012 - www.cqp.org ______________________________________________________________ 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 |
It still does pretty good even now. I just worked T6JG (559 to 579 signals on 15 meters), who sends CW well above 30 wpm and the K3 is copying his call and most of the calls he is replying to almost 100%. Only when the qsb takes hold of the signal does the decode suffer (as expected).
THR = 3 CW 30-90 AGC THR 012 Roger W5RDW
Roger W5RDW
|
Free forum by Nabble | Edit this page |