Cabrillo Definition for Helvetia Contest

In 2002 eletronic logs were introduced to HF-Contests sponsored by USKA. After looking at the time spent to reformat the logs received it was clear that a definition was missing. Approximately 90% of the time spent for during the adjudication process is used to bring all logs into a convertable format. Furthermore, HB is not a very well known Contest-country and a lot of education will be required. Several author run articles in our magazine old man. Covered were so far: Writelog (by HB9CZF), CT (by HB9CRV), RCK-Log (by HB9CVE), and TR Log (by HB9FMU).

For the adjudication I'm using software written by Dietmar, DL3DXX for converting almost any log into the STF file format. Furthermore, I adapted the software written by Ben, DL6RAI, for my needs. This software package - all written in PERL - can directly read STF and Cabrillo files and that is my way forward.

After a quick poll with the developper of the most common contest software it became obvious that we do not have to invent a new Cabrillo definiton for the Helvetia Contest. We will re-use the RSGB IOTA definition.

This example was taken from http://www.kkn.net/~trey/cabrillo/qso-template.html

Cabrillo QSO template for RSGB IOTA Contest

                              -----------info sent--------- ----------info rcvd----------
QSO: freq  mo date       time call          rst ex1  ex2    call          rst ex1  ex2    t
QSO: ***** ** yyyy-mm-dd nnnn ************* nnn nnnn aa-nnn ************* nnn nnnn aa-nnn n
QSO:  3799 PH 2002-07-28 0359 HC8N          59  0901 SA-004 G3XTT         59  0031 EU-005 0
QSO:  3799 PH 2002-07-28 0359 HC8N          59  0902 SA-004 HA1AG         59  0399 ------ 0
0000000001111111111222222222233333333334444444444555555555566666666667777777777888888888899
1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901

Deviation for Helvetia Contest - HB side

                              -----------info sent--------- ----------info rcvd----------
QSO: freq  mo date       time call          rst ex1  ex2    call          rst ex1  ex2    t
QSO: ***** ** yyyy-mm-dd nnnn ************* nnn nnnn aa-nnn ************* nnn nnnn aa-nnn n
QSO: 21025 CW 2004-04-24 1300 HB9CZF        599 0001 AG     JA6GCE        599 0001 --    
QSO: 21025 CW 2004-04-24 1304 HB9CZF        599 0004 AG     HB9APJ/P      599 0002 SZ 
0000000001111111111222222222233333333334444444444555555555566666666667777777777888888888899
1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901

Deviation for Helvetia Contest - EU/DX side

                              -----------info sent--------- ----------info rcvd----------
QSO: freq  mo date       time call          rst ex1  ex2    call          rst ex1  ex2    t
QSO: ***** ** yyyy-mm-dd nnnn ************* nnn nnnn aa-nnn ************* nnn nnnn aa-nnn n
QSO: 21025 CW 2004-04-24 1400 EI5DI         599 0001 --     HB9CZF        599 0123 AG    
QSO: 21225 PH 2004-04-24 1401 EI5DI         59  0002 --     HB9HFN        59  0234 FR 
0000000001111111111222222222233333333334444444444555555555566666666667777777777888888888899
1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901

• freq:
  For HF: integer frequency in kHz; if freq not known then 28000, 21000, 14000, 7000, 3500, 1800
• mo:
  CW, PH, RY or PS    (One section is called Digital and modes supported are RTTY and PSK31.)
• date:
  UTC date in yyyy-mm-dd form
• time:
  UTC time in nnnn form
• call:
  callsign
• rst:
  RST 
• ex1:
  contest exchange serial number (please include leading "0" to make up a 4-digit number)
• ex2:
  contest exchange canton (for EU/DX-side use "--")
• t:
  transmitter id 0 or 1 (used in the multi-two category). This field can be omitted.

Summary Sheet

START-OF-LOG: version-number

Must be the first line of the log submission. The current version-number is 2.0.

END-OF-LOG:

Must be the last line of the log submission.

CALLSIGN: callsign

The callsign used during the contest.

CATEGORY: operator-category band-category power-category [mode-category]

For HF contests the operator-category must be one of the following: SINGLE-OP, MULTI-ONE, SWL, or CHECKLOG.

For HF contests the band-category must be one of the following: ALL.

The power-category must be HIGH or QRP. Helvetia Contest does not have a LOW section so far.

The mode-category must be CW, SSB, MIXED or DIGITAL.

CATEGORY-ASSISTED: [assisted-status]

The value or assisted-status must be ASSISTED or NON-ASSISTED and may be specified for any contest.
Although DX-Cluster is allowed to everybody we leave it here.

CLAIMED-SCORE: n

The claimed-score of the log submission, in integer form such as 1217315 or 19113 or 12.

CLUB: text

Name of the radio club with which the score should be aggregated.

CONTEST: contest-name

The contest-name must be one of the following: ..., HELVETIA, ...

CREATED-BY: text

Name and version of the logging program used to create the Cabrillo file.

NAME: text
ADDRESS: text

Name and address.

OPERATORS: callsign1 [callsign2 callsign3...]

A space-delimited list of operator callsign(s). You may also list the callsign of the host station by placing an "@" caracter in front of the callsign within the operator list, such as

OPERATORS: @N6IJ

OFFTIME: begin-time end-time

This tag is used to indicate off-time that must be claimed by single operators in the WAE contest.

         -----begin----- ------end------
OFFTIME: date       time date        time
OFFTIME: yyyy-mm-dd nnnn yyyy-mm-dd nnnn
OFFTIME: 2002-03-22 0300 2002-03-22 0743
0000000001111111111222222222233333333334
1234567890123456789012345678901234567890

It seems no software is supporting the OFFTIME: field. According to the current rules offtime must be declared under SOAPBOX: (I think when the rules were written nobody knew OFFTIME:). Offtime will be recalculated during adjudication process.

SOAPBOX: text

Soapbox comments.

QSO: qso-data