WriteLog
[Top] [All Lists]

Re: [WriteLog] %Z

To: <writelog@contesting.com>
Subject: Re: [WriteLog] %Z
From: "Charles Morrison" <cfmorris@bellsouth.net>
Reply-to: cfmorris@bellsouth.net
Date: Wed, 25 Jul 2007 09:28:51 -0500
List-post: <mailto:writelog@contesting.com>
> From: "Don Hill AA5AU" <aa5au@bellsouth.net>
> Subject: Re: [WriteLog] %Z
> To: "'Bob Raker'" <bob.raker@gmail.com>, <writelog@contesting.com>
> Message-ID: <002001c7cda8$e9347f00$6501a8c0@AA5AU>
> Content-Type: text/plain;     charset="us-ascii"
> 
> Ed and I both use the two-PC method and therefore only have to use one
> buffer on each PC for this message - one has %ZA1, the other
> %ZA2.
> 
> Bob, the real reason I'm replying, and maybe others can be helped by
> this advice, is that I believe it's better not to put "TU"
> before putting "ALSO %ZA1" in the message for one reason.  When I'm S&P
> and I see "TU", I'm immediately off the frequency looking
> for the next contact.  I don't wait around to see the rest of the
> message.  I S&P as fast as I can possibly do it.  Maybe others
> aren't so fast to move away, but once I know the contact is confirmed,
> I'm out of there.  Instead I use:
> 
> %R QRV %ZA1 TU DE AA5AU CQ %E
> 
> OR
> 
> %R PSE %ZA1 (or %ZA2) TU DE AA5AU CQ %E
> 
> In NAQP, it may be proper just to put:
> 
> %R %ZA1 (or %ZA2) TU DE AA5AU CQ %E
> 
> Most folks already know what you are trying to do.  The %Z is SO COOL.
> I just love it.  It worked well for me in last weekend's
> RTTY test.  I had lots of people move, especially when ten meters was
> open.  Got quite a few to move from 40 to 80 as well.

I used it extensively during the NAQP.  I made changes during the contest to
the messages (always seem to do that).  I ended up with 2 messages.  One was
for if that rig was SP'ing and another for if the rig was running.  The only
thing was there isn't a way to change the INSERT function on the fly.  That
would be nice if it were automatic like NA in the sprint.  If the VFO moves,
the program knows its an SP'ing radio.  If it doesn't change, it knows it's
a RUN radio, thereby NA sends a different message if you can/cant QRZ or you
have to move. 

In either event, if it's a SP'ing radio, I sent a Fkey that sent "%C CHAS LA
LA ALSO %ZB1 %E".  If it's a run rig AND I had a clear frequency on the
other rig OR I was dueling CQ's, I'd send a different Fkey that sent "ALSO
%ZB1 TU QRZ KI5XP %E", otherwise if the second radio wasn't in the clear or
wasn't CQ'ing, I sent INSERT which just sent regular F2, "TU QRZ KI5XP
NAQP".  The entries on the second radio were similar, just replacing the B
with A for the first rig.  I only have 1 radio per computer, so the number
is always 1, but the letter changes for differing station/computer ID's.

I agree however, the %Z is almost revolutionary for moving.  One other hint
that I use to reduce confusion is the placement of the message keys.  Along
with the message stuck to the keybrd above the key, I ordered them so that
the messages fall on one side of the row of keys or the other.  Since the
Fkeys are split, 1-4, 5-8, and 9-12, messages sent at the beginning of the
qso (exchange, etc) fall on the LEFT side of the row (F1, F2, F5, F6).
Messages sent at the end (TU, QRZ, PSE MOVE, etc) fall on the RIGHT side of
the row (F3, F4, F7, F8).  9-11 were ones that I played around with.  This
way, even if I had a brain fart and didn't send the message I really wanted,
it was some semblance of something that was still appropriate.  It might not
have moved them, but it got the job done with out wasting time.  

Charlie
KI5XP



_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web:  http://www.writelog.com/

<Prev in Thread] Current Thread [Next in Thread>