[Top] [All Lists]

[CQ-Contest] Defining CQ's Operating Time

To: <cq-contest@contesting.com>
Subject: [CQ-Contest] Defining CQ's Operating Time
From: Robert Chudek - KØRC <k0rc@citlink.net>
Reply-to: Robert Chudek - KØRC <k0rc@pclink.com>
Date: Fri, 22 Sep 2006 13:43:16 -0500
List-post: <mailto:cq-contest@contesting.com>
Is it possible this time qualification is in the rules to avoid awarding 
certificates to a (semi) rare DX station that gets on, makes 10 contacts in a 
half hour, and then claims top honors for that country/zone (when there's no 
other competitor in that class/country/zone)?

Not that this would ever happen.

73 de Bob - KØRC in MN

Message: 9
Date: Fri, 22 Sep 2006 10:44:50 -0000
From: "David Robbins K1TTT" <k1ttt@arrl.net>
Subject: Re: [CQ-Contest] Defining CQ's Operating Time
To: "'CQ-Contest eMail Remailer'" <cq-contest@contesting.com>
Message-ID: <001901c6de34$21540d20$0800a8c0@k1tttibm>
Content-Type: text/plain; charset="us-ascii"

In at least some contests there is the phrase 'listening time counts as
operating time'... which is of course meant to stop time limited classes
from listening for an opening or scanning bands for multipliers while they
are in their 'off' time.  but that is of course assuming they will be trying
to operate up to their category max time.  and since Cabrillo has no way to
note 'time on' and 'time off' in the log all you can do is put in a total
operating time.  The other confusion factor of course would be those REALLY
slow contests where time between qso's is greater than the off time limit,
if you don't log a contact for 30 minutes or so the automatic checkers may
count it as time off when you were hard at work trying to make a contact.

David Robbins K1TTT
e-mail: mailto:k1ttt@arrl.net
web: http://www.k1ttt.net
AR-Cluster node: 145.69MHz or telnet://dxc.k1ttt.net
CQ-Contest mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [CQ-Contest] Defining CQ's Operating Time, Robert Chudek - KØRC <=