[ct-user] CT log outputs versus ARRL requirements

[Michael S. Mitchell, W6RW]

Jim Pratt wrote:
> 
> Group:
> 
> With the ARRL's new-found fervor for enforcing log format and deadline
> requirements, I wanted to make sure the multi-two log I send in to the
> league is in compliance.  The requirements from the ARRL web page include
> the following:
> 
> ****
> 
> 5.The log file must consist of one line of data per QSO (no more than 80
> characters wide), without headers, footers, page breaks or other
> non-ASCII characters.
> 
> 6.All QSO data must appear in each line, aligned by columns, and must include:
> 
>     1.band: wavelength for HF and frequency for VHF.
> 
>     2.mode: designator such as CW, PH, etc.
> 
>     3.date: in MM/DD/YY or DD/MM/YY format.
> 
>     4.time: 4-digit UTC without colons.
> 
>     5.call sign of station worked.
> 
>     6.complete exchange sent.
> 
>     7.complete exchange received.
> 
>     8.indication of multipliers: for example an asterisk (*),
>     section/prefix/zone, etc. for the first time the multiplier is
>     contacted.
> 
>     9.points claimed: ALL unclaimed QSOs must be "0" points.
> 
> 7.Multi Operator, Two Transmitter category logs must indicate which
> transmitter made each QSO.
> 
> ****
> 
> Great.  So, I did a "writelog" in CT as usual and found the following:
> 
> * the .log output does not include:
> 
>       * the transmitted "state" information;
>       * an indication of which station made the QSO.
> 
> So that won't work.  CT also produces the two files , one for each
> transmitter.  But, they include header information and page breaks.  And
> that information does note include the transmitted state OR signal report.
> 
> Thus it appears that CT doesn't produce ARRL-compliant logs for the
> multi-two category.  It also appears like I have a lot of work ahead of
> me with a text editor, either:
> 
> * adding the transmitted State and the station designation to the .log
> file;
> 
> OR
> 
> * deleting the header and page break information from each page of the
> two logs, and adding the transmitted information.
> 
> Before I get started with this task...any chance of the ARRL waiving this
> requirement for the 1999 log entries, assuming that CT becomes "Y2K"
> compliant in the sense of the log format for multi-two meeting ARRL
> requirements?
> 
> Standing by, awaiting a ruling from Newington...
> 
> 73, Jim  N6IG
> 
> --
> Submissions:              ct-user@contesting.com
> Administrative requests:  ct-user-REQUEST@contesting.com
> WWW:                      http://www.contesting.com/ct/
> Questions:                owner-ct-user@contesting.com

Hi Jim...we used CT version 9.27 for the ARRL CW contest as a
multi-two entry. The "W6RW.LOG" file produced by CT is in perfect
compliance with the ARRL requirements....including the state sent,
a zero or a one for which transmitter made the qso. Also all QSOs
are listed continuous without page headers. Our CT log file is
named ARRLCW.BIN which produces a W6RW.LOG file that complies
with the ARRL requirements when the WRITELOG and the WRITEARRL
commands are typed in the Callsign field when CT is up and
running. Maybe the newer versions of CT don't do the ARRL logs
right....we have stayed with version 9.27 as it seems bulletproof
and we have been hearing a lot of horror stories about newer
versions.. Hope this has been helpful....

73 es cu in the contest de Mike/W6RW

--
Submissions:              ct-user@contesting.com
Administrative requests:  ct-user-REQUEST@contesting.com
WWW:                      http://www.contesting.com/ct/
Questions:                owner-ct-user@contesting.com