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
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
Emory,
I suspect a little too much time between the first dit of the "P" and
the following dah.
at slower speed, the element spacing is probably OK.
73,
Don W3FPR
On 1/2/2017 1:48 PM, Emory Schley wrote:
I'm having a bit of a problem with my KX2, not a serious one, but a confusing
one.
I'm having a bit of a problem with my KX2, not a serious one, but a confusing
one. Whenever I use the built-in keyer to send my callsign, the screen readout
interprets my call as N4LEG instead of the correct N4LP. This happens at 13
wpm, but if I change the speed to 12 wpm, then my callsign is
4 matches
Mail list logo
