RTTY
[Top] [All Lists]

Re: [RTTY] WHY put CQ at the end?

To: "'reflector RTTY'" <rtty@contesting.com>
Subject: Re: [RTTY] WHY put CQ at the end?
From: "Don Hill AA5AU" <aa5au@bellsouth.net>
Date: Tue, 17 Feb 2015 12:02:53 -0600
List-post: <rtty@contesting.com">mailto:rtty@contesting.com>
Dave wrote: " But CW contest have been going on for 87 years, and nobody puts 
CQ at the end.  There is no confusion."

Many contesters send "TEST" at the end of their CQ message - same thing.

There may not be confusion, but if you come across someone sending their 
callsign during a CW contest, you still have to wait and listen to see if that 
station is running or S&P.

73, Don AA5AU

-----Original Message-----
From: RTTY [mailto:rtty-bounces@contesting.com] On Behalf Of Dave Hachadorian
Sent: Tuesday, February 17, 2015 11:53 AM
To: reflector RTTY
Subject: Re: [RTTY] WHY put CQ at the end?

>My own personal preference is to know who's calling CQ

But CW contest have been going on for 87 years, and nobody puts CQ at the end.  
There is no confusion.

With RTTY skimmers now in the mainstream, and most RTTY contests allowing 
Telnet assistance, most S&P operators are going to arrive on your frequency 
already knowing who you are.  They want to hear your call sign, or even a 
fragment of it, to confirm your identity.  They don’t need to hear CQ.  They 
already know someone is CQ’ing here.  

The CQ at the end is now more of a hindrance than a help, at least for those 
contests that allow Telnet assistance, which is the majority of RTTY contests.

Dave Hachadorian, K6LL
Yuma, AZ




.

_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty

-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2015.0.5646 / Virus Database: 4284/9130 - Release Date: 02/17/15

_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty
<Prev in Thread] Current Thread [Next in Thread>