I agree with each of Mike's several very good points below. A key inference
from all his comments is to make messages modular so that two or more can be
dynamically combined to create the appropriate message depending on the
situation. Don't pre-suppose that the "perfect" exchange message can be
programmed into one Fn key and used universally. <your call>, <his call>,
and each exchange element should be each on its own Fn key just once. Then,
you can send them the appropriate number of times per the specific situation
and/or combine them with your nominal Fn messages (CQ, exchange and QSL)
when needed.
Ed - W0YK
> -----Original Message-----
> From: rtty-bounces@contesting.com
> [mailto:rtty-bounces@contesting.com] On Behalf Of Mike
> Sent: Tuesday, 01 March, 2011 09:04
> To: rtty@contesting.com
> Subject: Re: [RTTY] Three lessons from NAQP
>
> Hello Gordon,
>
> Keep "Bambi", but go to VT. Missed the VT mult. in the recent NAQP:>)
>
> Regarding the sending of the other stations call at the start
> of a run QSO, this is what I've been recently using:
>
> - Hit the F2 macro programed as %R%C exchange %E which
> translates to Line
> feed, his call, exchange, end of transmission. This is
> used when there
> isn't anyone else calling and the call is solid on the screen.
> - Hit F2 then F5 This sends the F2 macro above followed
> by %C %E as
> programmed in F5. F5 translates to his call, end of
> transmission. The
> extra his call is sent when there may have been two calls
> or I may have
> started transmission before he actually ended calling me.
> - Hit F2 the F6. F6 is %C?? %E which translates to his
> call, "??", end
> of transmission. This combination is used when there is
> some question on
> having copied the correct call.
>
> If the run station didn't get your call correct, please send
> it at the beginning and end of your response transmission.
> If the run station still didn't get the call correct, then
> too bad for him as, I believe, the log checking programs will
> not credit the run station with the QSO, but the answering
> station does get credit since the answering station got all
> the information correct.
>
> Regarding confirming a QSO with the answering station, I've
> been using:
>
> - F3 macro of %R%C TU%RK4GMH CQ %E. This translates to
> line feed, his
> call, "TU", line feed, "K4GMH CQ", end of transmission.
>
> In the recent NAQP, the initial "his call" was not sent as
> this was mostly a domestic contest and the signals were okay
> for the most part. So the NAQP
> F3 macro was: %RTU K4GMH CQ %E. When a call correction was
> made during the information exchange part of a NAQP QSO, the
> F5 macro button was hit followed by hitting F3. This macro
> combination sent %C %RTU K4GMH CQ %E.
> This let the other station know I got his call correct.
> Sometimes, while I am running, a station will send the wrong
> call, e.g. K4GM rather than K4GMH. Then I'll send my F4
> macro, %B%BK4GMH K4GMH (the "%B%B" will not allow the F4
> macro to be sent if the station already has been worked)
> before my F3 macro to emphasize my call. Again, if the other
> station still doesn't get my call correct, hopefully the log
> checking program will give me credit for the QSO since I got
> all the correct information logged.
>
> Responding to a run station, the F7 macro (S&P) I use is:
> %R%C TU exchange %L%E. This is line feed, his call, "TU",
> exchange, log the QSO, end transmission. This lets the run
> station know I have his call correct.
>
> This is what I've been recently using. The above will be
> tampered with, from time to time, to "improve" obtaining a
> quick and successful exchange of the critical contest information.
>
> Whether these are optimum exchanges is a decision to be made
> by each operator. YMMV
>
> On Tue, Mar 1, 2011 at 6:02 AM, Gordon LaPoint
> <n1mgo1@verizon.net> wrote:
>
> > Gary,
> > We use "Bambi" because using our names was too
> confusing! We always
> > run Multi-2,
> > and the rules state that you can send each operators name,
> as they operate.
> > When we
> > tried that we got people telling us that we were "Charlie"
> or "Gordon"
> > , not what we had just sent. We were operating from a
> hunting camp in
> > the green mts. of VT then so we switched to one name,
> "Bambi" and have
> > been Bambi for years now! Very well known by lots of RTTY
> operators
> > as Bambi.
> >
> > The "Bambi" team, Gordon - N1MGO, Charlie - KT1I, Ray-
> KB1LRL, Pauline
> > - KB1JXJ, and others some years!
> >
> > Thanks for all the contacts over the years!
> >
> > What would you suggest we use as a name?
> >
> > Gordon - N1MGO
> >
> >
> > On 28 Feb 2011 at 9:37, Gary AL9A wrote:
> >
> > > If you want to talk about overkill, then you needed to
> work the guy
> > > who
> > sent
> > > his state as MINNESOTA. I guess he figures everyone out there is
> > > too
> > dumb
> > > to comprehend what MN means despite the fact that we all have to
> > > manually type MN in the state field as no amount of mouse
> clicking
> > > is going to
> > make
> > > MINNESOTA fit into a 2 position field! Another favorite
> was the guy
> > > in
> > MA
> > > sending his name as BAMBI. Needed lots of AGNs to get
> that one right.
> > > Finally, for those using the first name of AL, don't!
> Use ALLEN or
> > > ALAN, but please not ALFONSO!
> > >
> > > 73,
> > > Gary AL9A
> > >
> > >
> > > ----- Original Message -----
> > > From: "Jim Reisert AD1C" <jjreisert@alum.mit.edu>
> > > To: "RTTY Reflector" <rtty@contesting.com>
> > > Sent: February 27, 2011 8:06 PM
> > > Subject: Re: [RTTY] Three lessons from NAQP
> > >
> > >
> > > On Sun, Feb 27, 2011 at 6:20 PM, Jim Reisert AD1C
> > > <jjreisert@alum.mit.edu> wrote:
> > >
> > > I forgot one:
> > >
> > > 4. Use the standard 2-letter postal abbreviation for
> your state or
> > > province. Don't spell it out, and don't put punctuation after it!
> > > One station sent something like:
> > >
> > > <name> SS. <name> SS,
> > >
> > > so there was no way to click on the state abbreviation (SS) and
> > > *not* get the period or comma along with it, at least in WriteLog.
> > >
> > > I won't even get started about the guy who separated the
> two copies
> > > of his exchange with:
> > >
> > > <space><hyphen><space>
> > >
> > > Talk about overkill!
> > >
> > > --
> > > Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us
> > > _______________________________________________
> > > RTTY mailing list
> > > RTTY@contesting.com
> > > http://lists.contesting.com/mailman/listinfo/rtty
> > >
> > > _______________________________________________
> > > RTTY mailing list
> > > RTTY@contesting.com
> > > http://lists.contesting.com/mailman/listinfo/rtty
> >
> >
> > _______________________________________________
> > RTTY mailing list
> > RTTY@contesting.com
> > http://lists.contesting.com/mailman/listinfo/rtty
> >
>
>
>
> --
> 73,
> Mike, K4GMH
> _______________________________________________
> RTTY mailing list
> RTTY@contesting.com
> http://lists.contesting.com/mailman/listinfo/rtty
_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty
|