[WriteLog] 160 Log reject due to category

ronsue ronsue@attbi.com
Wed, 18 Dec 2002 12:41:31 -0500


Hi Mike,

I believe the same options are present regardless of contest.  Yes, you must
know . . . and you get that from the contest rules along with hours of
operation, dates, log submission addresses, etc.

A lot of guys got stung in the 160 contest assuming that the start was at
0000Z, but that contest actually started at 2200Z.  I always run the rules
out on my printer and review them before the contest.

I ran the 10 meter contest exclusively CW one year and entered CW Assisted.
Well it turns out that if you use the cluster you are also forced into the
Mixed category.

Once burned, twice smart . . . I now read the rules.

Ron ND5S

----- Original Message -----
From: <N5MT@aol.com>
To: <writelog@contesting.com>
Sent: Wednesday, December 18, 2002 11:29 AM
Subject: [WriteLog] 160 Log reject due to category


Received this from the ARRL 160 contest robot.
I assume that from what I see when Writelog is creating the Cabrillo output,
that I MUST KNOW that there is NO ASSISTED category and I must pick the
MULTI-ONE category to make my log correct.
Or is there an internal parameter for the 160 contest, that needs updating
for this contest that would not list the OLD Assisted category?

Happy Holidays.  73  Mike  N5MT

CATEGORY: SINGLE-OP 160M QRP
CATEGORY: SINGLE-OP 160M LOW
CATEGORY: SINGLE-OP 160M HIGH
CATEGORY: MULTI-ONE
CATEGORY: CHECKLOG

Please note that there is no Single Op Assisted category in this
contest. Single operators who use packet assistance must submit their
logs in the Multi Op category.

160 METER CONTEST LOG WARNING MESSAGE REPORT FROM THE ROBOT

CATEGORY: SINGLE-OP-ASSISTED 160M HIGH CW
Line 4 was discarded. Invalid Cabrillo category specification


--- StripMime Report -- processed MIME parts ---
multipart/alternative
  text/plain (text body -- kept)
  text/html
---
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog