In a real RTTY contest, the "PLEASE COPY" is surprisingly rare. (It was pretty common on field day, which thank God is not an actual contest!) More common in real RTTY contests, are long preambles of
I'll just make one fill button for each variable, that sends it two or three times. 90% of the time that's enough for the conditions. If I need to send more I just tap the same button two or three ti
with great reluctance,,, I was going to eliminate the "TU" in the exchange--I have always felt, and still feel that the rtty bunch is the nicest group of competitors that I have ever encountered, and
John I also send TU in contests for the same reason. Thank You! Dave Greig N3BUO *801 Tactical* Phone: (682) 422-6667 http://www.801tactical.com Google Plus: gplus.to/801Tactical Facebook: https://ww
Absolutely. Keep the TU. Indeed, TU is equivalent to QSL. CQ TEST W6SX W6SX CQ P40X P40X 599 03 W6SX 599 P40X TU W6SX CQ My TU to P40X says Thank You AND QSL, the contact is complete. Keep the TU. Co
I'm confused; is someone advocating dropping the TU? Most guys use it. And from a S&P rate standpoint, it's very helpful for the run station to lead with that TU - as it let's the S&P caller know he'
ORIGINAL MESSAGE: (may be snipped) REPLY: Leading with the TU could cause problems when there are two stations that both think they are the one you are working. If they both see the TU and take off,
Bill, You are correct. That was my meaning but got in a rush to type the reply. 73/jeff/ac0c www.ac0c.com alpha-charlie-zero-charlie ORIGINAL MESSAGE: (may be snipped) REPLY: Leading with the TU coul
Absolutely! A QSO is not complete until BOTH stations have received an acknowledgement of the information they have sent - which means that the run station must <send> that final acknowledgement befo
Efficiency is a good thing however rather than eliminate the TU, QSL or other form of acknowledgment, I would eliminate sending the callsign of the station that you are working. Sending P40X before T
ORIGINAL MESSAGE: (may be snipped) On 7/17/2014 4:25 AM, john@kk9a.com wrote: I would eliminate sending the callsign of the station that you are working. Sending P40X before TU W6SX serves no purpose
no just spinning the than you This unending debate between 'speed' and 'security' is why advanced operators are moving towards modular messages that can be optimized on the fly. Program the default
My QSL message is typically: TU W0YK CQ If I have stacked call signs, it is: W6WRT TU, NW KK9A 599 03 In the first case, I've opted to trade-off a few cases of confusion for far more cases of a short
.......and please send the signal report if required :-)!!! John N1JM Absolutely! A QSO is not complete until BOTH stations have received an acknowledgement of the information they have sent - which
There are many ways to skin a cat. Below is an piece I wrote for National Contest Journal (November/December 2013). My most important point is the W6SX Prime Directive: The first rule of contesting i
Just to be clear, Since the original post was regarding dropping TU from the acknowledgement, I suggested not sending the callsign in the last line of W6SX's example and only sending TU W6SX CQ. Of c
The messages when running are interesting. I normally use HISCALL 599001 001 HISCALL. The reasoning is as follows. If I am working through a number of stations calling then often the first call sent
I agree with everything (though the casual contester we all rely on may not have clued in to TOO) but... 599 001 001 We like to click on the exchanges - 599001 means you have to type it when the seco
Jeff If you use N1MM then N2AMG is very nifty with the programming. Click on 599001 when on the exchange window guess what no 599 appears... It is even clever on processing time exchange used for the
/"//This selfish practice can easily be stamped out by working those individuals but not logging the QSO."/ If I were a contest adjudicator and detected this practice, I would DQ the operator (the on