CQ-Contest
[Top] [All Lists]

[CQ-Contest] TU?

Subject: [CQ-Contest] TU?
From: rbrandon@austin.ibm.com (Robert Brandon)
Date: Mon Apr 2 20:15:34 2001
To my mind, you just want to make sure the running station's switched to
receive and is ready to copy.  So it depends on what the exchange is.  If
5NN leads off the exchange, I'd rather not get a "TU".  If I miss a dit or
two, no problem.  If, as in Sweepstakes, vital data begins from the first
dit (e.g., with the serial number), then I actually like TU or R.  A one
second pause, however, is just as good.

I'm far from a big gun, but most of the guys who contest aren't either.  8^)
See you in the next one.

Robert K5PI

-----Original Message-----
From: owner-cq-contest@contesting.com
[mailto:owner-cq-contest@contesting.com]On Behalf Of K4BEV@aol.com
Sent: Monday, April 02, 2001 8:57 AM
To: CQ-Contest@contesting.com
Subject: [CQ-Contest] TU?



In CW tests some S&P stations send TU exchange.
Some just send the exchange.
I usually include the thank you -- and mean it.
Sometimes I send R TU exchange.

When I'm running (I use the term loosely) you could include info about your
station and probably not hurt my rate much. The folks at the W4CAT multi, on
the other hand, don't have the time to hear about your radio, and they know
it. The clock is ticking and (as I am finally figuring out) time IS the name
of the game.
Am I inadvertently squandering too much of your valuable contest time by
thanking you for the Q?
It doesn't seem like much time is used sending TU, but for the top stations
I
can certainly see where this would add up.
I'll drop the "R " -- I wouldn't send you my exchange if I didn't copy yours
anyway, so it seems that receipt is implied. Should the "TU" go too??

TU Don K4BEV


--
CQ-Contest on WWW:        http://lists.contesting.com/_cq-contest/
Administrative requests:  cq-contest-REQUEST@contesting.com


--
CQ-Contest on WWW:        http://lists.contesting.com/_cq-contest/
Administrative requests:  cq-contest-REQUEST@contesting.com


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