[Elecraft] CQWW RTTY - K3 Experience
Bill W4ZV
btippett at alum.mit.edu
Mon Sep 29 20:09:31 EDT 2008
Arie Kleingeld PA3A wrote:
>
> Using the CW memories made it even more easy. I think it must have been
> a bit strange on the other side of the QSO seeing the long pause after
> the 5nn because the "1" takes a reletive long time in CW.
> That's also why a kept going on with the 5nn instead of 599.
>
Next time load your memory with 599 14 IM (dididahdah with no space
between). The IM is for IMmediate end of transmission. Don't send 5NN
since 599 is just as fast in RTTY and less confusing to RTTY ops. Using my
paddle, I loaded:
M1: W4ZV W4ZV IM
M3: 599 05 NC IM
(if I needed linked repetitions I just double-tapped M1 or M3).
Using the memories, I was later told I sounded like regular RTTY (i.e. no
delays due to CW sending speed since my memory exchanges were sent at full
RTTY speed of ~60 WPM).
I didn't see any point in repeating the call of the other station since I
was always dead zero beat (thanks to CWT) and was responding to his CQ (i.e.
not CQ-ing myself). I found the K3's CW TX decoder more sensitive to
perfect CW timing than my poor fist, so after mangling my first QSO with the
key I used the memories exclusively for my other QSOs. I tuned for a CQ,
pressed M1, if answered I pressed M3, got my confirmation and went looking
for another. My only slight confusion was when my call would appear in the
buffer after answering a station. The first time I thought that was the
station answering me but quickly realized it was left over in the display
from my call (i.e. M1) since the DX often answered someone else in the
pileup.
This was my first experience with RTTY after 51 years on the air. I would
never have bothered were it not for the K3. I now feel very comfortable
using the above technique to call DX stations in a pileup, should the need
ever arise (i.e. in case a new one should show up on RTTY and not CW).
73, Bill
--
View this message in context: http://n2.nabble.com/CQWW-RTTY---K3-Experience-tp1126034p1127632.html
Sent from the Elecraft mailing list archive at Nabble.com.
More information about the Elecraft
mailing list