I'm no expert but the reader is probably reading exactly what you send. I will frequently see my K3S read "NR4TR". It's all in the spacing and we know what we mean to send but the reader has no idea until it hears it. And, it has no "context" to assist it.
Sent from my iPhone ...nr4c. bill > On Jan 2, 2017, at 3:59 PM, n...@zianet.com wrote: > > Emory Schley writes: > >> Whenever I use the built-in keyer to send my callsign, the screen readout >> interprets my call as N4LEG instead of the correct N4LP. > > I had the same problem when I first got my KX2. The CW weighting was set for > 1.0; I changed it to 1.25 for a better dit-to-dah ratio and my sent CW became > much more readable. Don't know if that addresses your problem, but worth > checking. The reader does seem to slice certain letters into two (like F > into I N) if you're not real snappy :-) > > 72, Paul NA5N > ______________________________________________________________ > 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 > Message delivered to n...@widomaker.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 Message delivered to arch...@mail-archive.com
