RTTY
[Top] [All Lists]

Re: [RTTY] Trailing CQ

To: RTTY Reflector <rtty@contesting.com>
Subject: Re: [RTTY] Trailing CQ
From: Lee Sawkins <ve7cc@shaw.ca>
Date: Thu, 24 Mar 2016 15:40:35 -0600 (MDT)
List-post: <rtty@contesting.com">mailto:rtty@contesting.com>
Ed 

The trailing CQ in RTTY CQ messages is equivalent to the trailing TEST in CW CQ 
messages. I will not be eliminating it. When I see or hear a call a couple of 
times, I really want to know if I can call the person immediately or if I need 
to wait and see if the person is calling CQ. If other station does not call CQ 
again in a couple of seconds, I may move on if it is not a multiplier. It is 
really annoying when I call a rare multiplier and cannot get my serial number 
through the QRM of others calling me. 

73 Lee 

----- Original Message -----

From: "Ed Muns" <ed@w0yk.com> 
To: "RTTY Reflector" <rtty@contesting.com> 
Sent: Thursday, March 24, 2016 8:35:51 PM 
Subject: [RTTY] Trailing CQ 

The rationale for a trailing 'CQ' in CQ and TU messages is no more true for 
RTTY than CW. CW contesting has decades of existence proof that such a 
trailing CQ is not needed, i.e., the rationale is flawed. 

The only valid reason for the trailing 'CQ' in RTTY messages is that it has 
(unnecessarily) been done that way for many years now. RTTY contesters 
expect it and can be confused if it isn't there. 

The advent of RTTY Skimmer offers a good reason to stop this practice, but 
changing such an entrenched technique will take concerted effort by RTTY 
contesters over a long period of time. However, the longer we wait, the 
longer it will take to accomplish. 

Why don't we drop 'CQ' from the end of our messages now and get on with the 
transition? 

Ed W0YK 

_______________________________________________ 
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

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