Wednesday, February 20, 2013
To close for CW comfort
So why did I title this post "To close for CW comfort" this has to do with the other CW "events" that I was exposed to! I have read about this in other blogs from other op's which are CW operators who seem for some reason to blend letters together regarding their call. I had at least 6 op's who's call I had a very very hard time making out. There was one DX station who's call ended in WVR BUT for the longest time I was not sure if it was W##, even the code reader on the KX3 was having a real hard time. I then ran across 10+ on the S meter European station but I could not give him a call as I had (and I mean NO CLUE) what his call was!! It was very hard to tell were the CQ stopped and the call was being sent. Now folks for any of you reading my blog and who also have had a CW QSO with me I know my code elegance has left you scratching your head at times.....but I just can't understand how code that has no spaces and just runs as one long word how these op's ever get answers to their CQ requests.
When I got home I put my Elecraft k3 into test mode (meaning no code is sent over the air) and tried to send some sloppy code and watched to see if the K3 was able to decode. (you can setup the K3 to not only show incoming code but also your code as you send it) The only reading the K3 would give me were not letters or numbers just lots of *****......translation...the K3 also has no idea. As with most CW op's out there you also have your code being sent to you through your headphones. Does the code not sound odd to these op's???
Anyway time to get off my soapbox now.............