Contest definition

From DXLog.net
Jump to navigation Jump to search

Introduction

Contest rules vary greatly and are typically defined by the contest organizers.
The differences can be in points per QSO, multiplier determination and calculations etc.
To support a wide variety of rules and to allow for easy adding/changing of contest rules in DXLog,
contest rules are defined and controlled through a contest config file.

Contest config files are "semi human readable", plain text files located in the Contest sub-folder in
DXLog's installation folder. A wide range of contest definition files are included in the DXLog standard installation.
The contest config files in the protected installation folder are however not intended for editing or modification
For this, there is a copy of the folder in Windows' unprotected AppData folder structure.
Since this is a hidden folder, a drop down menu item is provided for easy access. (File | Open configuration directory)

Each time DXLog is started, the content of the installation sub-folder and the AppData sub-folder is compared.
If a contest config file in the installation sub-folder is newer than its copy in the AppData sub-folder
(e.g. due to it being updated as part of a new DXLog release), the AppData file is overwritten.

In the opposite case (e.g. due to own modifications of a contest config file), the AppData file remains unchanged.
This means that any modifications of existing contest config files should be done in the AppData folder, but that
such modifications may be overwritten if a newer version is distributed in a later DXLog release.
To secure that a contest config file is not overwritten by future DXLog releases, create a file with a new name.
The same mechanic, with a master folder and an AppData copy, applies to data base (i.e. pre-fill or call history) files.

If you have developed a contest config file that is proven to be correct and that could be useful others, Please contact
the development team to discuss adding it to DXLog's standard contest repertoire.


Configurationpaneltagged3.png
Relation between configuration keys and macros and their related text boxes and drop down menus in the contest configuration panel.

File structure

Each line in a contest definition file usually contains KEY + VALUE pairs. The pair is always separated by the "=" sign. For example:

CONTESTNAME=9A CW

This means the field key is CONTESTNAME and the field value is 9A CW.

Regular expressions

You will see that in many cases DXLog is using regular expressions to verify condition validation and process entries.

If you are not familiar with regular expressions (regex for short) there are many online resources available.
One tutorial can be found here.

For example, regular expressions are used to check if the user keyboard entry is valid against a condition or
set of conditions, for QSO points calculations etc.

Regular expressions in the contest configuration file can be defined as fixed values, but they can
also compare QSO data against fixed values.

Example: We want to validate the user entered data in some of the fields. For example, we want
to validate that the user is allowed to enter NY, FL, GA, or MA in the EXCHANGE field on the contest
configuration screen.

The contest configuration key for this operation is: CFG_MULT_RGX_CHECK.

So to create a validation, as per the previous example, we need the following definition
in the contest config file:

CFG_MULT_RGX_CHECK=^NY$|^FL$|^GA$|^MA$
^ denotes start of the string
$ denotes end of the string
| separates alternative matching patterns, forming a logical or

Another example is to validate that the Exchange field is a two digit number or a six position grid:

CFG_MULT_RGX_CHECK=^([0-9]{2}|[A-R]{2}[0-9]{2}[A-X]{2})$
() surrounds alternative matching patterns
{} forms a repetition of the preceding matching pattern

QSO data is addressed using a origin key (CONFIG, SOURCE, or DEST) and a content key (CALLSIGN, EXCHANGE, DXCC, etc.).
They are combined using "->". Examples of QSO data keys are CONFIG->POWER, SOURCE->DXCC, and DEST->RCVD.

Not all possible combinations of origin keys and content keys are valid. Please see below for valid combinations.

Available origin keys
CONFIG Information originating from contest configuration panel. If empty, derived from callsign.
SOURCE Information relating to own station. NB. Always derived from callsign.
DEST Information relating to other station.
Available content key combinations
CONFIG or SOURCE or DEST -> CALL or CALLSIGN Callsign.
CONFIG -> CLASS The contest's active power class as selected in the contest configuration panel in upper case.
SOURCE or DEST -> CONT Continent. Two letter acronym.
CONFIG or SOURCE or DEST -> CQZONE CQ/WAZ Zone.
CONFIG or SOURCE or DEST -> DXCC Official DXCC prefix.
CONFIG -> EXCHANGE The content of the contest exchange field in the contest configuration panel.
CONFIG or SOURCE or DEST -> ITUZONE ITU zone.
CONFIG -> OPNAME The content of the operator name field in the contest configuration panel.
CONFIG -> OVERLAY The overlay text in upper case. (NB. Not the Cabrillo overlay)
CONFIG or SOURCE or DEST -> PFX or WPX Callsign prefix per WPX rules.
SOURCE or DEST -> PFX_AREA The callsign prefix formatted as main DXCC prefix plus "." and the prefix digit. E.g. "SM.0" or "EA.7".
NB. DXCC prefixes that contain a number keep this E.g. OH0DX is prefix area "OH0.0".
CONFIG -> POWER The content of the power field in the contest configuration panel.
DEST -> RCVD First element in the received contest exchange.
DEST -> RECINFO Second element in the received contest exchange.
DEST -> RECINFO2 Third element in the received contest exchange.
DEST -> RECINFO3 Fourth element in the received contest exchange.
CONFIG -> STATE The content of the State/Province/Other field in the contest configuration panel.
DEST -> TIME_HOUR The hour of the QSO time as a string with values from "0" to "23".

Example: We want to validate a value which could change on each entry into the log.

For example, we want to calculate points for each QSO with the same country, on the 160m band, in the CW and SSB mode, with 1 point.

The relevant contest configuration key for QSO points calculation is POINTS_FIELD_BAND_MODE.
To create the calculation, as per the previous example, we need the following definition in the contest config file:

POINTS_FIELD_BAND_MODE=SOURCE->DXCC:DEST->DXCC;ALL;^160$;^(CW|SSB)$;1

We can read this definition in the following way:
If the SOURCE (our) DXCC is the same as DEST (other station) DXCC and the
band is 160 and the mode is CW or SSB then the QSO is worth 1 point. In the above definition notice
the SOURCE and DEST keys. We can also use the CONFIG key.

Functions and FX expressions

Some keys allow not only keywords but also functions as arguments.

Functions follow C# syntax and have access to all string, number, and boolean manipulation functions in the language plus a number of helper functions.

The keywords available for regular expressions (see above) area also available in functions.

Some keywords assume an expression that returns a string, like MULT1_FX and FIELD_RCVD_CHECK_FORMAT_FX.

Examples:
MULT1_FX=$FIELDVALUE.Substring(0,4)
MULT1_FX=$FIELDVALUE.Substring(0,$FIELDVALUE.IndexOf('/'))

The first example picks the first four characters in the string as multiplier.
The second example picks the string following the first slash ("/") character as multiplier.
Two variables are available: $FIELDVALUE which is the multiplier itself, and $CALLSIGN which is the other station's call.

The available helper string functions are:

Helpers.GetLastLetter($FIELDVALUE) - Returns the last character in the field (e.g. callsign)

Helpers.GetPureCall($FIELDVALUE) - Returns the field (callsign) without prefix, slashes, etc.

Helpers.GetPrefixArea($FIELDVALUE, $CALLSIGN) - Returns the prefix area as NN.0

Helpers.GetPrefixAreaVEGeo($FIELDVALUE, $CALLSIGN) - Returns the prefix area as NN.0 but treats
Canadian geographical prefixes (VY2, etc.) as own call areas.

Helpers.GetOblast($FIELDVALUE) - Returns the Russian region based on field which should be callsign.<

Helpers.GetOblastSPLO($FIELDVALUE,$CALLSIGN) - Returns the Russian region based on field which should be RCVD.
Uses the RDA exchange for SP/LO stations to determine oblast and the callsign for all others. Used in UA1DZ Memorial contest.

Some keywords assume an expression that returns a list of strings, like WINDOWS_CML_LIST_FX.

The available helper list functions are:

GetList_PrefixArea(dxccList,regex) - Creates a multiplier list with all call areas prefixes
Example: GetList_PrefixArea(dxccList,"^LA$") - Creates a multiplier list with all Norwegian call areas.

GetList_PrefixAreaVEGeo(dxccList,regex) - Creates a multiplier list including Canadian (VY1, etc.) call areas
Example: GetList_PrefixAreaVEGeo(dxccList,"^(VE|K)$) - Creates a multiplier list with all US and Canadian prefixes.

GetList_CustomRange(format,start,end) - Creates a list of numbered multipliers
Example: GetList_CustomRange("00",1,6) - Creates the list 00, 01, 02, 03, 04, 05, and 06

GetList_CustomArray(string,separator) - Creates a custom list
Example: GetList_CustomArray("AB|AC|AD|AK|AM","|") - Creates the list AB, AC, AD, AK, and AM

GetList_Oblast() - Creates a list containing the 85 Russian regions

GetList_GridArray(center,height,width)) - Creates a list of four letter grids around center
Example: GetList_GridArray(ownGrid,11,11) - Creates a list of 121 grids centered around own location
Example: GetList_GridArray("JP81",9,9) - Creates a list of 81 grids centered around JP81

Some keywords assume an expression returning a number, such as SCORE_TOTAL_FX and POINTS_CALC_F.

SCORE_TOTAL_FX is the formula for the score for an individual QSO. There variables available are
$FIELDVALUE.Points, $FIELDVALUE.Mult1, $FIELDVALUE.Mult2, and $FIELDVALUE.Mult3.
The arithmetic syntax is FLEE. (See below).

Example: SCORE_TOTAL_FX=$FIELDVALUE.Points+$FIELDVALUE.Mult1*2+$FIELDVALUE.Mult2*5
Example: SCORE_TOTAL_FX=$FIELDVALUE.Points*($FIELDVALUE.Mult1+If($FIELDVALUE.Mult2>10,10,$FIELDVALUE.Mult2))

POINTS_CALC_F is the formula for the points for certain QSO conditions.
The syntax for its second element, the points calculation, is also FLEE.

Other keys assume a boolean expression which can be either a regular expression (as described above) or
an FX() expression. Examples are FIELD_RCVD_FX_CHECK and the first argument of MULT1_EXCEPTION.

Examples:
MULT1_EXCEPTION=FX(Helpers.GetLastLetter("CONFIG->CALLSIGN").Equals(Helpers.GetLastLetter("DEST->CALL")));NONE
MULT1_EXCEPTION=FX(("CONFIG->CALLSIGN").Substring(0,3).Equals(("DEST->CALL").Substring(0,3)));NONE

The first example does not count the QSO as a multiplier if the last letter is the same in the station's
callsign and own callsign. The second example does not count the QSO as a multiplier if the first three characters
is the same in the station's callsign and own callsign.

The available boolean helper functions are:

Helpers.Between(number, min, max) - Returns true if number is between min and max.

Available syntax for arithmetic expressions

Fleesyntax.png

Custom multiplier lists

NB. A custom multiplier list can only be used for multiplier type CUSTOM.
FX type multipliers can not use a listed set of multipliers but rely on a
helper function to create its multiplier list, such as GetList_CustomRange().

Plain list of custom multipliers

A list of custom multipliers is started by [MULTIPLIERS START] and ends with [MULTIPLIERS END].
The syntax for a multiplier having more than one name is shown below. In this example both NK and NR
will count as the same multiplier; Norwich.

Example:

[MULTIPLIERS START]
...
NL=London N1-22
NN=Northampton
NP=Newport
NK{NK;NR}=Norwich
NW=London NW1-11
OL=Oldham
OX=Oxford
...
[MULTIPLIERS END]

Conditional lists of custom multipliers

For contests such as US state QSO parties there are two types of participants with different sets of custom multipliers.
To support this, a multiplier list can be conditional just like default messages. The regular expression can be of any type
and check EXCHANGE, DXCC, CONT or whatever is suitable.

Syntax:

[MULTIPLIERS START]
[VALID FOR=Regexp1]
M1=First multiplier 1
M2=First multiplier 2
...
[END VALID FOR]
[VALID FOR=Regexp2]
L1=Second multiplier 1
L2=Second multiplier 2
...
[END VALID FOR]

Example:

[MULTIPLIERS START]
[VALID FOR=CONFIG->EXCHANGE:^ADA$|^ALL$|^ARM$|^BEA$|^BED$|^BER$|^BLA$|^BRA$|^BUX$]
AK=Alaska
AL=Alabama
AR=Arkansas
AZ=Arizona
CO=Colorado
...
[END VALID FOR]
...

Grouped list of custom multipliers

Multipliers can be grouped for better display in the custom worked multipliers window enabled
with the WINDOWS_CML_ENABLED key. The string following Group-> is the displayed
name of the group. The name has no impact on scoring. The syntax for alternative names for the same
multiplier is different from the straight list. Alternative names for the same multiplier are
instead separated with a slash. In the example below, QU, QC, and QUE will all count as the same
multiplier; Quebec.

Example:

[MULTIPLIERS START]
Group->K1: CT,MA,ME,NH,RI,VT
Group->K2: NJ,NY
Group->K3: DE,PA,MD/DC
...
Group->VE1: NS
Group->VE2: QC/QU/QUE
Group->VE3: ON/ONT
Group->VE4: MB/MAN
...
[MULTIPLIERS END]

General contest description keys

These keys are used for general contest description in the contest config file, such as the contest name, link to the rules etc.
CONTESTGROUP Used for group contest when displaying the config screen for contest selection. For example: DIGITAL MODES, 9A LOCAL CONTEST, etc.
CONTESTNAME The contest name as it will be shown and recognized in the contest selection box.
Note: this can be same as the Cabrillo contest name, but usually it is the full contest name.
This field is mandatory and must be unique for all files in contest definition folder.
CONTESTEXCH Web link to definition of contest exchange. Shown when entering invalid data in configuration panel's exchange field. e.g. https://www.iota-world.org/
CONTESTRULES External HTTP Link to contest rules. Adds "Contest rules" item to Help menu. e.g. https://www.cqww.com/rules.htm
CONTESTWEB External HTTP Link to contest rules. Adds "Contest web" item to Help menu. e.g. https://www.cqww.com

Contest configuration panel control keys

These keys are used for setting the contest configuration variables in the user configuration window.
CATEGORIES Semicolon-separated list of contest categories shown in the category selection
dropdown menu in the contest configuration panel.
NB. When defining own categories, the values of CABRILLO_OPERATOR,
CABRILLO_TRANSMITTER, and CABRILLO_ASSISTED may have to be changed from
their defaults. Also contests with only EDI export needs correct keys.
C.f the Cabrillo section below.
Default value: Single operator;Single operator assisted;
Multioperator, single transmitter;Multioperator, two transmitter;
Multi operator, multi-transmitter
CATEGORY_MODES Semicolon-separated list of contest modes shown in the mode selection
dropdown menu in the contest configuration panel.
NB. There is no contest mode key for Cabrillo export. The
category mode string (in upper case) is also used for Cabrillo export.
Default value: CW;SSB;Mixed
CLASS Semicolon-separated list of contest classes shown in the class selection
dropdown menu in the contest configuration panel.
Default value: High;Low;QRP
OVERLAY Semicolon-separated list of contest overlays shown in the overlay selection
dropdown menu in the contest configuration panel.
Default value: ---;Band restricted;Radio Club;Dxpedition;
Headquarters; Open;Restricted;Novice;
Classic;Rookie;Tribander/Single element;
QRP;Fixed station;Portable station
CFG_EMAIL_MANDATORY Controls if the Email field in the contest configuration panel requires an entry or can be empty.
Valid values are: YES and NO
Default value: NO
CFG_MULT Controls the use of the exchange field in contest configuration panel. Valid values are: ON and OFF.
If OFF, the exchange field is greyed out.
Default value: OFF
CFG_MULT_DX_ALLOWED Controls if "DX" is an acceptable entry in exchange field. For example in ARRL DX Contest,
all USA/VE stations>needs to enter their state/province, while all other stations enters DX here.
Valid values are: YES and NO
Default value: NO
CFG_MULT_SLASH_ALLOWED Controls if "/" is acceptable as part of entry in exchange field.
Used as separator in contests with multi-part exchange multipliers.
Valid values are: YES and NO
Default value: NO
CFG_MULT_MANDATORY Controls if the exchange field requires an entry or can be empty. Valid values are: YES and NO Default value: NO
CFG_MULT_ERRORTEXT Defines error text which is shown if the validity test for the exchange field fails.
For example, in ARRL DX Contest, if the user enters a state abbreviation which is not in the approved list.
Default value: "Invalid value in exchange field!"
CFG_MULT_FROM Alternative to using a regular expression to check validity of entry in Exhange field.
Valid values are CUSTOM_MULT_LIST and ITUZONE.
Default value: Unused
CFG_MULT_RGX_CHECK Regular expression used to test validity of entry in Exchange field.
Note that the regular expression can include the key CUSTOM_MULT_LIST
meaning that any entry listed in the custom multiplier list is considered valid.
Example: CFG_MULT_RGX_CHECK=^AF$|^AS$|^EU$|^NA$|^OC$|^SA$|CUSTOM_MULT_LIST
Default value: ALL
CFG_CQZONE_ERRORTEXT Defines the error text shown if the entry in the WAZ field fails the validity test. Default value: "Invalid CQ/WAZ zone!"
CFG_CQZONE_MANDATORY Controls if the WAZ field requires an entry or can be empty. Valid values are: YES and NO Default value: NO
CFG_GRID_ERRORTEXT Defines the error text shown if the entry in the GRIDSQUARE field fails the validity test. Default value: "Invalid entry in gridsquare field!"
CFG_GRID_MANDATORY Controls if the GRIDSQUARE field requires an entry or can be blank. Valid values are: YES and NO.
Is automatically set to YES if contest has QRB-based scoring.
Default value: NO
CFG_GRID_RGX_CHECK Regular expression used to test validity of data entered in the GRIDSQUARE field. Default value: ^[A-R][A-R][0-9][0-9][A-X][A-X]$
CFG_ITUZONE_ERRORTEXT Defines error text shown if the entry in the ITU zone field fails the validity test. Default value: "Invalid ITU zone!"
CFG_ITUZONE_MANDATORY Controls if the ITU requires an entry or can be empty. Valid values are: YES and NO Default value: NO
CFG_MYDXCC_ERRORTEXT Defines the error text shown if the entry in the DXCC field fails the validity test. Default value: "Unrecognized DXCC from DXCC field.
Please enter valid country prefix in DXCC field"
CFG_MYDXCC_MANDATORY Controls if the DXCC field requires an entry or can be empty. Valid values are: YES and NO Default value: NO
CFG_OPNAME_ERRORTEXT Defines the error text shown if the entry in the operator name field fails the validity test. Default value: "Operator name field is mandatory!"
CFG_OPNAME_MANDATORY Controls if the operator name field requires an entry or can be empty. Valid values are: YES and NO Default value: NO
CFG_POWER_ERRORTEXT Defines the error text shown if the entry in the power field fails the validity test. Default value: "Invalid value in power field!"
CFG_POWER_MANDATORY Controls if the power field requires an entry or can be empty. Valid values are: YES and NO Default value: NO
CFG_POWER_RGX_CHECK Regular expression used to determine the validity of the power field entry. Default value: ALL
CFG_STATE_ERRORTEXT Defines the error text shown if the entry in the state/province/other field fails the validity test. Default value: "Invalid value in state/other field!"
CFG_STATE_FROM=CUSTOM_MULT_LIST Defines a list-based validity test for the state/province/other field.
Alternative to to using a regular expression.
Default value: absent
CFG_STATE_MANDATORY Controls if the state/province/other field requires an entry or can be empty.
Valid values are: YES and NO
Default value: NO
CFG_STATE_RGX_CHECK Regular expression used to test validity of entry in state/province/other field.
Note that the regular expression can include the key CUSTOM_MULT_LIST
meaning that any entry listed in the custom multiplier list is considered valid.
Example: CFG_STATE_RGX_CHECK=^YL$|^OM$|CUSTOM_MULT_LIST
Default value: ALL

Cabrillo export keys

Contest configuration keys

CABRILLO_ASSISTED Semicolon-separated list of mapping of categories to Cabrillo assistance types.
MUST have the same number of entries as the defined contest categories.
Valid list items are ASSISTED and NON-ASSISTED.
Default value:
NON-ASSISTED;ASSISTED;
ASSISTED;ASSISTED;ASSISTED
CABRILLO_ASSISTED_DISABLED No CATEGORY-ASSISTED line will be included in exported file. Default value: NO.
CABRILLO_BAND Semicolon-separated list of frequency definition names for contests with band-limited categories.
MUST have the same number of entries as the defined contest categories.
For value ALL the band category will be ALL unless the log only contains QSO from a single band.
In this case the band category will be this single band. For all other values of the key, log content is ignored.
Default value: ALL;ALL;ALL;ALL;ALL;ALL
CABRILLO_CONTEST_NAME Formal contest name for Cabrillo export. No default value
CABRILLO_DEF_RECINFO
CABRILLO_DEF_RECINFO2
CABRILLO_DEF_RECINFO3
Value to use in Cabrillo export if field is empty. Default value: Empty
CABRILLO_EXPORT_TYPE Controls structure of Cabrillo export.
Valid values: PER_MODE and ALL.
Default value: ALL
CABRILLO_LINE Use: CABRILLO_LINE=FREQ{F=R,6, };MODE{F=L,2, };DATE;TIME;MYCALL{F=L,13, };SENT{F=L,3, };NR{F=R,3,0,4}
Data is taken from the field names and added to the Cabrillo line in the
order entered. FREQ represents frequency of QSO, MODE represents mode etc.
For more details on valid keywords and the use of conditional entries, see below.
No default value
CABRILLO_LOCATION Semicolon-separated list of mapping of contest categories to Cabrillo
LOCATION key. If defined, MUST have the same number of entries as the defined
contest categories. Any string is a valid value. If left undefined, contest category
has no effect on LOCATION in Cabrillo export.
Default value: None
CABRILLO_LOCATION_CHECK NB. Legacy key kept only for backwards compatibility
Regular expression that checks the entered location for validity when prompted.
Default value: Empty
CABRILLO_LOCATION_IS_EXCHANGE If set to YES, creates the LOCATION key in the Cabrillo export for all
values of the contest configuration Exchange field except "NONE".
Default value: NO
CABRILLO_LOCATION_IS_STATE If set to YES, creates the LOCATION key in the Cabrillo export for all
values of the contest configuration State/Province/Other field except "NONE".
Default value: NO
CABRILLO_LOCATION_DEFAULT NB. Legacy key kept only for backwards compatibility
Default value of geographical location for Cabrillo export when prompted.
No default value
CABRILLO_LOCATION_PROMPT NB. Legacy key kept only for backwards compatibility
Regular expression that controls for if user is prompted for location information at Cabrillo export.
Default value: Empty
CABRILLO_MODES Semicolon-separated list of mapping of the contest's modes (as defined by the MODES key) to Cabrillo
modes in QSO lines. MUST have the same number of entries as the defined number of modes for the contest.
Valid list items are CW, PH, DG, RY, and FM. Some contests use non-standard keys such as PS.
Default value: CW;PH
CABRILLO_OPERATOR Semicolon-separated list of mapping of categories to to Cabrillo operator count.
MUST have the same number of entries as the defined contest categories.
Valid list items are SINGLE-OP, MULTI-OP, and CHECKLOG.
Default value:
SINGLE-OP;SINGLE-OP;
MULTI-OP;MULTI-OP;MULTI-OP
CABRILLO_OVERLAY Semicolon-separated list of mapping of category overlays to Cabrillo overlays.
MUST have the same number of entries as the defined overlays.
Any string is a valid entry.
NB. Overlays that correspond to a valid Cabrillo station location (fixed, mobile,
portable, rover, rover-unlimited, rover-limited, expedition, headquarter, and school) generate
a CATEGORY-STATION key instead of a CATEGORY-OVERLAY key in the export.
Default value:
;BAND RESTRICTED;RADIO CLUB;
DXPEDITION;HEADQUARTERS;
OPEN;RESTRICTED;NOVICE;
CLASSIC;ROOKIE;TB-WIRES;
QRP;FIXED STATION;PORTABLE STATION
CABRILLO_OVERLAY_DISABLED No OVERLAY line will be included in exported file. Default value: NO.
CABRILLO_POWER Semicolon-separated list of mapping of category power classes to Cabrillo power classes.
MUST have the same number of entries as the contest's power classes.
Valid list items are HIGH, LOW, and QRP.
Default value: HIGH;LOW;QRP
CABRILLO_QTC_LINE Definition of Cabrillo output for QTC. C.f. CABRILLO_LINE.
Valid keywords are: FREQ, MODE, DATE, TIME, RCVDBY, GRNUM, SENTBY,
QTCTIME, QTCCALL, and QTCSERIAL.
No default value
CABRILLO_TIME Semicolon-separated list of duration for each contest category.
MUST have the same number of entries as there are contest categories.
No default value
CABRILLO_TRANSMITTER Semicolon-separated list of mapping of categories to Cabrillo operator counts.
MUST have the same number of entries as the defined contest categories.
Valid list items are ONE, TWO, LIMITED, UNLIMITED, and SWL.
Default value:
ONE;ONE;ONE;TWO;UNLIMITED;UNLIMITED

CABRILLO_LINE keywords

Important note: If you want to take full control of the colums to e.g. concatenate fields in the export,
this is done by adding a trailing asterisk ("*") to the keys below. This will remove the extra space
following a field to guarantee separation. Extra spaces required to align to certain character positions
can be added using the DUMMY keyword.

Key Content Default format
FREQ Frequency in kilohertz. {F=R,6, }
FREQMHZ Frequency in Megahertz. {F=R,6, }
MODE QSO mode with Cabrillo coding. {F=L,2, }
DATE Date of QSO. Format YYYY-MM-DD. {F=L,10, }
TIME Time of QSO. Format HHMM. {F=L,4, }
PERIOD Contest period. {F=L,2, }
MYCALL Own call. {F=L,13, }
SENT Sent exchange. {F=L,3, }
NR Serial number sent. {F=L,4, }
PREV_RCVD First element in previously received exchange. {F=L,3, }
PREV_RECINFO Second element in previously received exchange. {F=L,3, }
PREV_RECINFO2 Third element in previously received exchange. {F=L,3, }
PREV_RECINFO3 Fourth element in previously received exchange. {F=L,3, }
EXCHANGE Exchange as defined in contest configuration panel.
Can optionally take a string function instead of formatting arguments within curly brackets.
E.g. EXCHANGE{FX=$FIELDVALUE.Substring(0,4)}
Breaks up slashed entries.
{F=L,5, }
CALL Logged station's call. {F=L,13, }
RCVD1 First half of received exchange, typically RST. {F=L,3, }
RCVD2 First element in received exchange without RST.
Can optionally take a string function instead of formatting arguments within curly brackets.
E.g. RCVD2{FX=$FIELDVALUE.Substring(0,4)}
{F=L,5, }
RECINFO Second element of received exchange.
Can optionally take a string function instead of formatting arguments within curly brackets.
E.g. RECINFO{FX=$FIELDVALUE.Substring(0,4)}
{F=L,5, }
RECINFO2 Third element of received exchange.
Can take optionally a string function instead of formatting arguments within curly brackets.
E.g. RECINFO2{FX=$FIELDVALUE.Substring(0,4)}
{F=L,5, }
RECINFO3 Fourth element of received exchange.
Can optionally take a string function instead of formatting arguments within curly brackets.
E.g. RECINFO3{FX=$FIELDVALUE.Substring(0,4)}
{F=L,5, }
MYCQZONE Own CQ zone. {F=L,2, }
MYITUZONE Own ITU zone. {F=L,2, }
MYDXCC Own DXCC. {F=L,5, }
DXCC DXCC of logged station. {F=L,5, }
MULTSENT Exchange as defined in contest configuration panel. {F=L,5, }
STATE State or province as set in contest configuration panel. {F=L,5, }
POWER Station power as set in contest configuration panel. {F=L,5, }
OPNAME Operator name as set in contest configuration panel. {F=L,5, }
GRID Grid locator as set in contest configuration panel. {F=L,6, }
GRID4 First four positions of grid as set in contest configuration panel. {F=L,6, }
PTS Points of QSO. {F=R,3, }
DUMMY Nothing. {F=L,5, }
STN Station. "0" for all stations except radio 2 in SO2R and multiplier
station in Multi/Single which both are "1".
{F=L,2, }

CABRILLO_LINE formatting and conditionals

CABRILLO_LINE formatting information is contained within curly brackets with the following syntax:

{F=AL,PS,PC(,TS)}

F=: Formatting flag
AL: Alignment, can be L (for left) or R (for right)
PS: Paddes size. Total size of text including character padding.
PC: Character used for filling up to padded size. E.g. 0 for serial numbers.
TS: Total size of field. Space padding to the right is used to reach this size. Optional.

Example: RCVD2{F=R,3,0,4}

Means RCVD2 field value will be aligned right, to a length of 3 characters. The "0" character is
used to pad to the specified length. Total size will be 4 characters (padding with spaces to reach 4).
This means that if RCVD2 field value is "1", it will be formatted as " 001" in the Cabrillo QSO line.

Regardless if total size is specified or not, each field will always be surrounded by spaces.

For some keys it is possible to replace the formatting information with a string operation, using an FX=
syntax and the $FIELDVALUE keyword to represent a string containing the field's characters.

CABRILLO_LINE also supports conditional formatting using a *RGX: syntax.

Example: *RGX:SOURCE->DXCC:^(DL|OE)$>>EXCHANGE{F=L,6, }/NR{F=R,3,0,6};

means the content of the Exchange box in the contest configuration panel station for German and Austrian
stations, otherwise a three position serial number. Both of total length 6.

per-own-DXCC conditional formatting is also supporting using a *NN> syntax

Example: *DL>EXCHANGE{F=L,6, }/NR{F=R,3,0,6};

means the same as the above example, but only for German stations. This conditional can
also be repeated, to cover several DXCC entities.

CABRILLO_QTC_LINE keywords

Key Content Format
FREQ Frequency in kilohertz 6 positions, right adjusted
MODE Mode when receiving QTC 3 positions, left adjusted
DATE Date QTC exchanged 12 positions
TIME Time QTC exchanged 4 positions
RCVDBY Call of receiving station 13 positions, left adjusted
GRNUM Group number of QTC 10 positions, left adjusted
SENTBY Call of sending station 13 positions, left adjusted
QTCTIME Time in QTC line 4 positions
QTCCALL Call in QTC line 13 positions, left adjusted
QTCSERIAL Serial in QTC line 3 positions, right adjusted

Configuration keys' relation to Cabrillo export

Relation between contest category configuration and Cabrillo export
Key type DXLog Key Cabrillo key Default values
Configuration CATEGORIES Single operator Single operator assisted Multi-operator, single transmitter Multi-operator, two transmitter Multi-operator, multi-transmitter Checklog
Cabrillo CABRILLO_OPERATOR CATEGORY-OPERATOR SINGLE-OP SINGLE-OP MULTI-OP MULTI-OP MULTI-OP CHECKLOG
Cabrillo CABRILLO_TRANSMITTER CATEGORY-TRANSMITTER ONE ONE ONE TWO UNLIMITED UNLIMITED
Cabrillo CABRILLO_ASSISTED CATEGORY-ASSISTED UNASSISTED ASSISTED ASSISTED ASSISTED ASSISTED ASSISTED
Cabrillo CABRILLO_BAND CATEGORY-BAND ALL ALL ALL ALL ALL ALL
Relation between contest overlay configuration and Cabrillo export
Key type DXLog Key Cabrillo key Default values
Configuration OVERLAY --- Band restricted Radio Club Dxpedition ...
Cabrillo CABRILLO_OVERLAY CATEGORY-OVERLAY Key not present BAND RESTRICTED RADIO CLUB DXPEDITION ...
Relation between contest power class configuration and Cabrillo export
Key type DXLog Key Cabrillo key Default values
Configuration CLASS High Low QRP
Cabrillo CABRILLO_POWER CATEGORY-POWER HIGH LOW QRP
Relation between contest mode categories and Cabrillo export
Key type DXLog Key Cabrillo key Default values
Configuration CATEGORY_MODES CW SSB Mixed
Cabrillo N/A CATEGORY-MODE Value is determined automatically by capitalizing contest mode from configuration.
Relation between available contest QSO modes and Cabrillo export
Key type DXLog Key Cabrillo key Default values
Configuration MODES CW SSB
Cabrillo CABRILLO_MODES QSO CW PH
Relation between contest band category and Cabrillo export
Key type DXLog Key Cabrillo key Default values
Configuration BANDS 160 80 40 20 15 10
Cabrillo N/A CATEGORY-BAND Value is determined automatically. If log contains QSO on only one band, this is used. Otherwise value defaults to ALL.

De-facto standard Cabrillo QSO line formatting

Cabrilloqsocolumns.png

Band and mode keys


BANDS A semicolon-separated list of allowed bands for the contest.
Valid band names are: 2190, 630, 560, 160, 80, 60, 40, 30, 20, 17,
15, 12, 10, 6 or 50, 4 or 70, 2 or 144, 222, 432, 902, 1296, 2300,
3400, 5650, 10G, and 24G.
Default value: 160;80;40;20;15;10
MODES A semicolon-separated list of modes usable for the contest.
Not to be confused with CATEGORY_MODES.
Default value: CW;SSB
EDI_BANDS A semicolon-separated list of EDI values for bands specified in BANDS key.
Must contain same number of entries as BANDS key.
Used for generating EDI log files for VHF/UHF/SHF contests in IARU Region I.
Valid values are: 28 MHz, 50 MHz, 70 MHz, 144 MHz, 432 MHz, 1,3 GHz, 2,3 GHz,
3,4 GHz, 5,7 GHz, 10 GHz, 24 GHz, 47 GHz, 76 GHz, 120 GHz, 144 GHz, and 248 GHz.
Note the space between the number and the frequency multiplier and that
commma is used as decimal separator.
No default value and if not set, EDI export is disabled.
MODE_GROUP Semicolon-separated list of mode group names. Used as an alternative to CABRILLO_MODES
to group modes together for special dupe rules. One list entry per MODES mode entry.
No default value
DISPLAY_MODE_GROUPING Formatting of display of modes in check multiplier window.
Syntax: DISPLAY_MODE_GROUPING=modename1:mode1+mode2;modename2:mode3+mode4
No default value

QSO entry field definition keys

These keys are used to control the layout and behavior of QSO entry fields. The keys set the visibility, length, labels, checking procedures etc.
for each of the fields which the user can enter data or display for any QSO.
FIELD_AZ_VISIBLE Controls the visibility of the Azimuth field.
Mostly used on VHF/UHF/SHF to get the azimuth angle from a gridsquare.
Valid values are YES and NO.
Default value: NO
FIELD_CALLSIGN_WWL_CHECK If YES, an entry in the log callsign field will be checked for a gridsquare entry.
If a gridsquare is found, the callsign field value will be copied to the gridsquare
entry field and the azimuth angle will be calculated and shown. Recommended for VHF/UHF
contests where you turn your antenna a lot. Valid values are YES and NO.
Default value: NO
FIELD_MODE_VISIBLE If YES, overrides menu option Options|Log|Always show mode in QSO lines and makes the mode
column always visible in the log. If NO, has no effect. Good for mixed mode contests.
Default value: NO
FIELD_MODE_NAME Heading for mode column. Default value: "Mode"
FIELD_MULT_NAME Heading for multiplier column. Default value: "Mult"
FIELD_MULT_VISIBLE If MULT field is visible on the screen. Valid values are YES and NO. Default value: YES
FIELD_MULT_MAX_LENGTH Width of MULT column. Default value: 5
FIELD_NR_VISIBLE If sent QSO SERIAL NUMBER is visible on the QSO entry line.
Valid values are YES and NO.
Default value: NO
FIELD_NR_HIDDEN_DXCC Semicolon separated list of DXCC. If our own DXCC is on this list,
sent serial number field will be hidden. Useful for contests where some
stations are sending a serial number exchange and other stations are
sending other data (for example a local province).
Default is to hide none
FIELD_NR_HIDDEN_RGX Regular expression. If the condition is valid, sent serial number
field will be hidden. Useful for contests where some stations are sending
a serial number exchange and other stations are sending other data
(for example a local province).
No default value
FIELD_PERIOD_VISIBLE If PERIOD number column is visible. Valid values: YES and NO. Default value: NO
FIELD_PERIOD_NAME Heading for PERIOD number column. Default value: "P"
FIELD_PTS_VISIBLE If POINTS column is visible. Valid values: YES and NO. Default value: YES
FIELD_PTS_NAME Heading for POINTS column. Default value: "Pts"
FIELD_RCVD_CHECK_FORMAT_FX C# expression to reformat entered value in the field before further
validity checking. The value in the field is represented as $FIELDVALUE. Example:
FIELD_RCVD_CHECK_FORMAT_FX=$FIELDVALUE.Substring(0,2)+$FIELDVALUE.Substring(2).TrimStart('0')
will reshape RCVD by taking the first to characters and then remove any leading zeroes in the
remainder before further validity or multiplier checking.
Default value: $FIELDVALUE
FIELD_RECINFO_CHECK_FORMAT_FX
FIELD_RECINFO2_CHECK_FORMAT_FX
FIELD_RECINFO3_CHECK_FORMAT_FX
One or several, semicolon separated, regular expressions to conditionally reformat the entered
value in the field before further validity checking.
The regular expression and the formatting expression are separated by ">>" as in CABRILLO_LINE.
The entered value is represented as $FIELDVALUE. Example:
FIELD_RECINFO_CHECK_FORMAT_FX=!DEST->DXCC:^YO$>>'.'+$FIELDVALUE
will add a period before the second part of the exchange for all stations that are not from Romania.
FIELD_RECINFO_CHECK_FORMAT_FX=!DEST->DXCC:^K$|^KL$|^KH6$|^VE$>>""
will ignore any value in the second exchange field for all stations not from US, Hawaii, Alaska, or Canada.
Default value: ALL>>$FIELDVALUE
FIELD_RCVD_COPY
FIELD_RECINFO_COPY
FIELD_RECINFO2_COPY
FIELD_RECINFO3_COPY
If the field's value is automatically copied from previous QSO with same station.
Also controls if the exchange is shown with callsign in bandmap when Display options|Exchange
is selected. Valid values: YES and NO.
Default value: NO
FIELD_RCVD_COPY_EXC_DXCC
FIELD_RECINFO_COPY_EXC_DXCC
Semicolon separated list DXCC entities for which RCVD/RECINFO is copied
from earlier QSO in spite of FIELD_RCVD_COPY/FIELD_RECINFO_COPY=NO.
Useful in case only some DXCC have a fixed exchange in the contest.
Default value: NONE
FIELD_RCVD_COPY_EXC_RGX
FIELD_RECINFO_COPY_EXC_RGX
Regular expression. For QSO where the condition is true, the
content of the field will be copied from earlier QSO in spite of
FIELD_RCVD_COPY/FIELD_RECINFO_COPY=NO.
Useful if only certain types of exchanges are fixed for stations in contest.
No default value
FIELD_RCVD_COPY_FX C# expression used to determine value to be copied from earlier QSO.
The value of the field is $FIELDVALUE. For example:
FIELD_RCVD_COPY_FX=$FIELDVALUE.Substring(0,6)
will copy the first six characters from the RCVD field from the
previous QSO with the same station.
Default value: $FIELDVALUE
FIELD_RCVD_DEFAULT_VALUE Value to be used in export if RCVD field is empty.
Valid values are: CQZONE, ITUZONE, CONT, or any string, which will be used verbatim.
No default value
FIELD_RCVD_EXC_CHECK_DXCC List of destination DXCC countries separated by ":" (or keyword ALL for all) for which CUSTOM_MULT_LIST
validity checking is enforced.
E.g. FIELD_RCVD_EXC_CHECK_DXCC=K:KL:KH6:VE:XE
For legacy reasons, any expression following a semicolon is ignored.
Note that this key only applies to FIELD_RCVD_TYPE=MULT.
Also note that this key does not override FIELD_RCVD_RGX_CHECK, so if used,
this key needs to accept all possible values of RCVD.
E.g. FIELD_RCVD_RGX_CHECK=DEST->RCVD:^[0-8][0-9]?$|^90$;DEST->RCVD:CUSTOM_MULT_LIST
No default value
FIELD_RCVD_FORMAT_FX
FIELD_RECINFO_FORMAT_FX
FIELD_RECINFO2_FORMAT_FX
FIELD_RECINFO3_FORMAT_FX
C# expression used to format entered value before saving. No default value
FIELD_RCVD_FX_CHECK
FIELD_RECINFO_FX_CHECK
FIELD_RECINFO2_FX_CHECK
FIELD_RECINFO3_FX_CHECK
Boolean C# expression used to check if value entered in the field is valid. For example:
FIELD_RCVD_FX_CHECK=Helpers.Between($FIELDVALUE,1,40)
checks if RCVD is between 1 and 40.
No default value
FIELD_RCVD_MANDATORY
FIELD_RECINFO_MANDATORY
FIELD_RECINFO2_MANDATORY
FIELD_RECINFO3_MANDATORY
If RCVD field entry is mandatory. Valid values are YES and NO. Default value: NO
FIELD_RCVD_MANDATORY_RGX_EXC
FIELD_RECINFO_MANDATORY_RGX_EXC
FIELD_RECINFO2_MANDATORY_RGX_EXC
FIELD_RECINFO3_MANDATORY_RGX_EXC
Defines exceptions from mandating rule via a regular expression. For example:
FIELD_RCVD_MANDATORY_RGX_EXC=!DEST->DXCC:^G$|^GD$|^GI$|^GJ$|^GM$|^GU$|^GW$
means RCVD is not mandatory for UK stations.
No default value
FIELD_RCVD_MAX_LENGTH Maximum number of characters accepted in the field. Default value: 10
FIELD_RECINFO_MAX_LENGTH
FIELD_RECINFO2_MAX_LENGTH
FIELD_RECINFO3_MAX_LENGTH
Maximum number of characters accepted in the field. Default value: 6
FIELD_RCVD_MIN_LENGTH
FIELD_RECINFO_MIN_LENGTH
FIELD_RECINFO2_MIN_LENGTH
FIELD_RECINFO3_MIN_LENGTH
Minimum number of characters accepted in the field. Default value: 0
FIELD_RCVD_AUTOSKIP Controls whether RCVD and RECINFO fields are treated as one continuous field.
E.g. when typing in the RCVD field, the cursor will automatically skip to the RECINFO
field when the maximum length of the RCVD field is reached.
Also, when deleting characters with [Back], the cursor will automatically move to the previous field.
Only recommended for contests where all exchange elements have a fixed length.
Default value: NO
FIELD_RCVD_NUMERIC
FIELD_RECINFO_NUMERIC
FIELD_RECINFO2_NUMERIC
FIELD_RECINFO3_NUMERIC
Controls if the field accepts only numeric characters.
Valid values are YES and NO.
Default value: NO
FIELD_RCVD_NAME Column heading for RCVD field. Default value: Rcvd
FIELD_RCVD_SLASH_ALLOWED
FIELD_RECINFO_SLASH_ALLOWED
FIELD_RECINFO2_SLASH_ALLOWED
FIELD_RECINFO3_SLASH_ALLOWED
Controls if the field accepts a slash "/" character.
Valid values are YES and NO.
Default value: NO
FIELD_RCVD_RGX_CHECK
FIELD_RECINFO_RGX_CHECK
FIELD_RECINFO2_RGX_CHECK
FIELD_RECINFO3_RGX_CHECK
Regular expression. Used to check if entry in the field is valid.
For contests with more than one type of exchange (e.g. grid and serial
number or oblast and grid), more than one rule can be listed, separated
by semicolon. The check is then done against the union of the rules, i.e.
if any of the rules checks OK, the entry is approved.
No default value
FIELD_RCVD_TYPE Defines data type of the field.
Valid values are: GRID, GRID4, CONT, NR, CUSTOM (any text), MULT (a listed keyword, associated
with MULT#_TYPE=CUSTOM), CQZONE, ITUZONE, and NAME.
NB. There is no automatic validity checking for CUSTOM, CQZONE, NAME, and ITUZONE.

Validity checking of MULT is enabled using the key FIELD_RCVD_EXC_CHECK_DXCC.
This means a FIELD_RCVD_RGX_CHECK or key may be required. The type can also be per-DXCC
using the syntax DXCC:regex=type1;!DXCC:regex=type2 where regex is matched against the
station's main DXCC prefix and can be e.g. ^(JA|JD/o|JD/m)$
NB. Since the types are used to determine e.g. ADIF export, only use NAME for a real name
and only use NR for the exchange serial number.

Default value: Empty
FIELD_RECINFO_TYPE
FIELD_RECINFO2_TYPE
FIELD_RECINFO3_TYPE
Defines data type of the field.
Valid values are: GRID, GRID4, NR, CONT, CUSTOM, MULT, CQZONE, ITUZONE, and NAME.
There is an automatic validity check on all types except CUSTOM and NAME.
NB. Since the types are used to determine e.g. ADIF export, only use NAME for a real name
and only use NR for the exchange serial number.
Default value: Empty
FIELD_RCVD_WWL_CHECK If YES, entry in RCVD field will be checked if it can be possible gridsquare entry.
It it is gridsquare, then RCVD field value will be copied to gridsquare entry field
and Azimuth will be calculated and shown. Valid values are YES and NO.
Default value: NO
FIELD_RECINFO_NAME
FIELD_RECINFO2_NAME
FIELD_RECINFO3_NAME
Heading for field's column. Default value: Empty
FIELD_RECINFO_RGX_SEL_POS
FIELD_RECINFO2_RGX_SEL_POS
FIELD_RECINFO3_RGX_SEL_POS
Filtering function for composite multipliers.
Only FIELD_RECINFO_RGX_SEL_POS is used, in AGCW QRP contest.
No default value
FIELD_RECINFO_VISIBLE
FIELD_RECINFO2_VISIBLE
FIELD_RECINFO3_VISIBLE
Controls if the the field is visible.
Valid values: YES, NO, HIDDEN, and READONLY.
Default value: NO
FIELD_RST_3RD_LETTER Semicolon-separated list of allowed third characters apart from numbers. For example:
FIELD_RST_3RD_LETTER=A;S
allows 59A and 59S as reports.
Default value: None
FIELD_RST_VISIBLE Controls visibility of RST field. Valid values are: YES and NO. Default value: YES
FIELD_SENT_VISIBLE Controls visibility of Sent field in log. Valid values are: YES and NO. Default value: YES

Default message keys

Default messages for F-keys, Plus and Ins.
CW_MESSAGE_1 Default F1 message for Run Default value: "CQ $MYCALL $MYCALL TEST"
CW_MESSAGE_2 Default F2 message for Run Default value: "$RST $EXCHANGE"
CW_MESSAGE_3 Default F3 message for Run Default value: "$EXCHANGE"
CW_MESSAGE_4 Default F4 message for Run Default value: "$MYCALL"
CW_MESSAGE_5 Default F5 message for Run Default value: "$LOGGEDCALL"
CW_MESSAGE_6 Default F6 message for Run Default value: "NR?"
CW_MESSAGE_7 Default F7 message for Run Default value: "?"
CW_MESSAGE_INS Default Insert message for Run Default value: "$F2"
CW_MESSAGE_PLUS Default Plus message for Run Default value: "$CORRECT TU $CR $MYCALL"
SP_CW_MESSAGE_1 Default F1 message for S&P Default value: "$MYCALL"
SP_CW_MESSAGE_2 Default F2 message for S&P Default value: "$RST $EXCHANGE"
SP_CW_MESSAGE_3 Default F3 message for S&P Default value: "$EXCHANGE"
SP_CW_MESSAGE_4 Default F4 message for S&P Default value: "$MYCALL"
SP_CW_MESSAGE_5 Default F5 message for S&P Default value: "$LOGGEDCALL"
SP_CW_MESSAGE_6 Default F6 message for S&P Default value: "NR?"
SP_CW_MESSAGE_7 Default F7 message for S&P Default value: "?"
SP_CW_MESSAGE_INS Default Insert message for S&P Default value: "$F2$CR"
SP_CW_MESSAGE_PLUS Default Plus message for S&P Default value: "TU$CR"
CW_MESSAGE_EXCHANGE_FILTER Message definitions following this key will only be effective if regular expression
after equal sign evaluates true for content in exchange entry box.
Example: CW_MESSAGE_EXCHANGE_FILTER=^DX$ means that messages
below this line will be used for stations entering DX in the exchange entry box.
NB. Only has effect for the first log created. All subsequent logs for the
same contest will inherit the messages from the previous log.

Additional configuration keys

DXCC related keys

DXCC_DB_TYPE This entry allows the use of a custom country file (for example, R150S.dat).
If a custom country file is defined, the selection
in Option|Data files|Country files will be ignored and
the country file defined in the contest config file will be used.
Valid values are: CUSTOM_CTY and CTY
Default value is CTY which will use
the data base set in the
Options|Data files|Country files
panel.
DXCC_DB_FILENAME Used to enable the use of an alternative country data base.
Used in conjunction with the DXCC_DB_TYPE key to define the data
file name. The file format is the same as the normal CTY.DAT file.
Default value: CTY.DAT
DXCC_DB_USE_ARRL_LIST Controls the use of the ARRL country list instead of CQ/WAE country list.
Valid values: YES and NO.
Default value: NO

Contest timing and period keys

MIN_OFF_TIME Minimum time in minutes without QSO to count as off time.
C.f. OFF_TIME_ROUND_UP.
Default value: 30
OFF_TIME_ROUND_UP Off time is calculated based on time difference between QSO instead of minutes without QSO.
YES means that QSO at e.g. 4:12 and 5:12 represents 60 minutes of off time.
NO means that QSO at e.g. 4:12 and 5:13 represents 60 minutes of off time.
Valid values: YES and NO.
Default value: NO
CONTEST_LENGTH Duration of contest in minutes.
Ignored for contests without periods.
No default value
CONTEST_FIRST_HOUR Time of day for start of contest in UTC. Ignored for contests without periods.
Valid formats: H, HH, HMM, and HHMM.
No default value
PERIOD Whether the contest has periods.
Valid values: ON and OFF.
Default value: OFF
PERIOD_LENGTH The length of each contest period in minutes.
Valid values: Any integer.
Default value: 0
PERIOD_AUTOSWITCH If the next period should start automatically.
NB. Does not work if contests stretches past midnight UTC.
Valid values: YES and NO.
Default value: NO
PERIOD_NUMBER Number of periods in contest.
Valid values: CALC_FROM_TIME or any integer.
CALC_FROM_TIME means duration divided by period length.
Default value: 0
PERIOD_MODES Semicolon-separated list of modes for each period in the contest.
Must have the same number of items as number of periods.
No default value

Database, prefill, and check keys

DB_FILE or DB_FILE1
DB_FILE2
DB_FILE3
DB_FILE4
DB_FILE5
File name of prefill data base.
DB_FILE_TYPE or DB_FILE1_TYPE
DB_FILE2_TYPE
DB_FILE3_TYPE
DB_FILE4_TYPE
DB_FILE5_TYPE
Extension of data base file. Default value: .TXT
DB_FILE_COL_RCVD or
DB_FILE1_COL_RCVD
DB_FILE2_COL_RCVD
DB_FILE3_COL_RCVD
DB_FILE4_COL_RCVD
DB_FILE5_COL_RCVD
Column number of RCVD field in data base file.
NB. At least one DB_FILE_COL* statement must be included for each data base file.
NB. Since look-up for RCVD is enabled by default, it needs to
be actively disabled if not wanted. Set it to -1 to disable undesired look-up.
DB_FILE_COL_RECINFO or
DB_FILE1_COL_RECINFO
DB_FILE2_COL_RECINFO
DB_FILE3_COL_RECINFO
DB_FILE4_COL_RECINFO
DB_FILE5_COL_RECINFO
Column number of RECINFO field in data base file.
DB_FILE_COL_RECINFO2 or
DB_FILE1_COL_RECINFO2
DB_FILE2_COL_RECINFO2
DB_FILE3_COL_RECINFO2
DB_FILE4_COL_RECINFO2
DB_FILE5_COL_RECINFO2
Column number of RECINFO2 field in data base file.
DB_FILE_COL_RECINFO3 or
DB_FILE1_COL_RECINFO3
DB_FILE2_COL_RECINFO3
DB_FILE3_COL_RECINFO3
DB_FILE4_COL_RECINFO3
DB_FILE5_COL_RECINFO3
Column number of RECINFO3 field in data base file.
DB_FILE_FILL_FORMAT or
DB_FILE1_FILL_FORMAT
DB_FILE2_FILL_FORMAT
DB_FILE3_FILL_FORMAT
DB_FILE4_FILL_FORMAT
DB_FILE5_FILL_FORMAT
C# expression defining how prefill from data base file will be used.
Example: /{0} will precede prefill with a slash.
This function is often combined with the menu option to use INSERT mode in the RCVD field.
RGX_GUESS_DB Regular expression "rule base" for guessing exchange of unworked stations.
Syntax is RGX_GUESS_DB=Field;DXCC Regexp;Callsign Regexp2;Filename[;Result regex]
A look-up is done for stations fulfilling at least one of the regular expressions.
If the result regex is used, the look-up returns nothing for all look-ups not matching it.
The syntax of the file callsign regexp=multvalue or DXCC:regex=multvalue
The file is parsed from top to bottom and the first match is used.
DXC_COMMENT_EXTRACT This entry is used to extract exchange or multiplier information from DX cluster comments.
For example, the line:
DXC_COMMENT_EXTRACT=RECINFO;(AF|AN|AS|EU|NA|OC|SA)[ /\-\.]?\d{1,3};[ /\-\.]
will extract a typical IOTA designation such as AF-025 and insert it into the RECINFO prefill
field for the spot.
The first part of the configuration (before the ;) defines into which entry field the data should be placed.
The second part of the configuration is a regular expression that defines the data that is to be matched.
The third part defines which characters should be removed from the matched result.
It is mandatory but can be empty.
SCP_DATABASE_DISABLE Disable check partials database. (for e.g. WRTC).
Valid values are: YES and NO.
Default value: NO
DB_SCP_FROM_EXCHANGE or
DTB_SCP_FROM_RECINFO
Enables reverse look-up.
Searches for all instances of either RCVD or RECINFO in first and second column of all data base files.
Search is triggered when pressing space and all entry fields are empty except RCVD or RECINFO.
Search hits are displayed in Check Partials window.
Default value: NO

QSO exchange and numbering keys

INITIAL_SERIAL_NUMBER Starting value of sent serial number. Default value: 1
QSO_NUMBER QSO numbering principle.
Valid values: ALL, PER_MODE, PER_BAND, PER_PERIOD, PER_BAND_MODE, PER_PERIOD_MODE.
ALL means chronological numbering.
Default value: ALL
QSO_NUMBER_CATEGORY Semicolon-separated list of numbering principles for each contest category.
Must contain the same number of elements as contest categories.
Valid values: ALL, PER_MODE, PER_BAND, PER_PERIOD, PER_BAND_MODE, PER_PERIOD_MODE.
If not present, the value
of QSO_NUMBER is used.
FIRST_PREV_RCVD Initial return value of macro $PREV_RCVD.
Any string is allowed but also the keyword EXCHANGE
Default value: "000"
FIRST_PREV_RECINFO Initial return value of macro $PREV_RECINFO.
Any string is allowed but also the keyword EXCHANGE
Default value: "000"
FIRST_PREV_RECINFO2 Initial return value of macro $PREV_RECINFO2.
Any string is allowed but also the keyword EXCHANGE
Default value: "000"
FIRST_PREV_RECINFO3 Initial return value of macro $PREV_RECINFO3.
Any string is allowed but also the keyword EXCHANGE
Default value: "000"
SLASH_MULTIPLE_QSOS Controls whether slashed ("/") multipliers are used in the contest. Default value: NO

Double QSO keys

DOUBLE_QSO The definition of a dupe.
Valid values: PER_PERIOD, PER_BAND, PER_MODE, PER_PERIOD_BAND,
PER_PERIOD_MODE, PER_BAND_MODE, PER_BAND_MODE_RECINFO,
PER_BAND_MODE_RCVD, PER_PERIOD_BAND_MODE, PER_MINUTE_DIFFERENCE,
PER_BAND_DAY
Required. Lacks default value.
DOUBLE_QSO_MINUTE_DIFFERENCE Minimum time difference in QSO time to not be counted as a dupe.
Used in conjunction with DOUBLE_QSO=PER_MINUTE_DIFFERENCE.
MIN_VALID_QSO_DIFFERENCE Minimum allowed time between QSO with the same station (e.g. on other band or mode). Default value: 0
DOUBLE_QSO_MODE_CHECK Definition of dupe principle when it comes to mode.
Valid values: PER_MODE, PER_CABRILLO_MODE, and PER_MODE_GROUP.
Default value: PER_MODE

Multiplier keys

MULT_SUM Summing method for multipliers.
Valid values: NO, ALL, PER_BAND, and PER_PERIOD.
Default value: ALL
OWN_MULT_VALID Controls if own multiplier is valid. NB. Controls the validity of ALL own multipliers but
does not consider calculated or derived multipliers, e.g. DXCC or WPX. This means that for the NO
option to work, the own multiplier must be specified in the Exchange field
in the contest configuration panel and only this multiplier will not count.
Default value: NO
CUSTOM_MULT_LENGTH Length of an enumerated numeric multiplier. If number is shorter, it is left padded with zeroes.
Used with enumerated multipliers, e.g. "=1-1999".
Default value: 0
CONTINENT_LIST Custom, semicolon-separated continent list. Syntax is: CONTINENT_LIST=continent1;continent2;continent3 Default value: EU;NA;SA;AS;AF;OC
MULT1_CONT_LIST
MULT2_CONT_LIST
MULT3_CONT_LIST
Custom, semicolon-separated continent list. Syntax is: MULT1_CONT_LIST=continent1;continent2;continent3 Default value: EU;NA;SA;AS;AF;OC
MULT1_TYPE
MULT2_TYPE
MULT3_TYPE
Type of MULT.
Can be CALLSIGN, DXCC, CQZONE, WPX, CUSTOM, HQ, NUM, FIELD, LETTER1, or FX.
Default value: None
MULT1_FX
MULT2_FX
MULT3_FX
A C# expression used to create the actual value of MULT from the entered value.
The entered value is available in the object $FIELDVALUE.
For example MULT1_FX=$FIELDVALUE.Substring(0,$FIELDVALUE.IndexOf('/'))
will make the characters before the slash the actual multiplier.
MULT1_COUNT
MULT2_COUNT
MULT3_COUNT
Counting method for MULT1, MULT2, and MULT3. Can be PER_BAND, PER_PERIOD, PER_MODE,
PER_BAND_MODE, PER_PERIOD_MODE, PER_PERIOD_BAND, PER_PERIOD_BAND_MODE, or ALL.
NB. Do not use e.g. PER_BAND for a single band contest or PER_MODE for a single mode contest.
Default value: None
MULT1_ADD_DXCC
MULT2_ADD_DXCC
MULT3_ADD_DXCC
Only used with multiplier type HQ. Determines if a HQ station counts as a DXCC multiplier.
Can be canceled for a selected condition using the multiplier exception REMOVE_DXCC.
Example: MULT2_EXCEPTION=DEST->RCVD:^R[1-3]$;REMOVE_DXCC
means that HQ stations sending R1, R2, or R3 as exchange will not count for DXCC multipliers.
Valid values: YES and NO.
Default value: NO
MULT1_FIELD
MULT2_FIELD
MULT3_FIELD
Source of MULT.
Valid values: RCVD, CALLSIGN, FROM_DXCC, FROM_WPX, RECINFO, RECINFO2, RECINFO3, NONE
Default value: None
MULT1_DISPLAY
MULT2_DISPLAY
MULT3_DISPLAY
Text to show in MULT column. Syntax: MULT1_DISPLAY=Regexp;String. The Regexp can be omitted.
Example: MULT1_DISPLAY=DEST->DXCC:^K$|^KL$|^KH6$;S
Example: MULT1_DISPLAY=FN
Default value: None
MULT1_SHOWERROR
MULT2_SHOWERROR
MULT3_SHOWERROR
Highlight errors in MULT.
Valid values: YES and NO.
Default value: YES
MULT1_BAND_BONUS
MULT2_BAND_BONUS
MULT3_BAND_BONUS
Per band multiplier scaling factor. Syntax MULT1_BAND_BONUS=band;scaling.
Example: MULT1_BAND_BONUS=80;2 doubles the multiplier count for the 80m band.
MULT1_BONUS
MULT2_BONUS
MULT3_BONUS
General multiplier scaling factor. Syntax MULT1_BONUS=scaling.
Example: MULT1_BONUS=4 gives four multiplier points for every multiplier.
Default value: 1
MULT1_EXCEPTION
MULT2_EXCEPTION
MULT3_EXCEPTION
Exception from the general rule for MULT.
Syntax: MULT1_EXCEPTION=boolean;multiplier definition.
The boolean function can either be a regular expression (c.f. above) or FX() expression.
Example: MULT1_EXCEPTION=DEST->DXCC:^K$|^VE$;CUSTOM_MULT_LIST
will use the custom list to determine multipliers for US and Canadian stations.
Example: MULT1_EXCEPTION=FX("CONFIG->CALLSIGN"<>"K1DG");NONE
will not count this multiplier for anyone except Doug K1DG.
Valid values of the multiplier definition are: PFX_AREA, WPX, NONE,
CUSTOM_MULT_LIST, REMOVE_DXCC, or LETTER1.
MULT1_MULTIPLIER
MULT2_MULTIPLIER
MULT3_MULTIPLIER
Multiplication factor for a selected value of MULT. Syntax multiplier;factor.
For instance MULT1_MULTIPLIER=AZ;4 means all "AZ" are worth four multipliers.
One MULT1_MULTIPLIER line is required for each value of MULT1 which has a multiplier.
MULT1_REPEAT
MULT2_REPEAT
MULT3_REPEAT
Specifies a list of values of MULT and the number of times they count as multipliers.
For instance MULT1_REPEAT=VD[3];PA[2] means the first three "VD" and the first
two "PA" count as multipliers. If only a multiplier without a bracketed number is listed,
the number is one. NB. This function is not fully implemented throughout DXLog.
By default multipliers only count once
MULT1_CONT_LIST
MULT2_CONT_LIST
MULT3_CONT_LIST
List used when MULT is of type CONT. Default value: EU;NA;SA;AS;AF;OC

Rate window keys

STATS_TYPE Type of statistics in Rate window.
Valid values: STANDARD and WRTC.
Default value: STANDARD
DISPLAY_TIME_ON_PER_MODE Display time on per mode in Rate window. Default value: NO
DISPLAY_LAST_MODE_CHANGE Display time of last mode change in Rate window. Default value: NO
RATE_ODX_VISIBLE Show distance statistics in Rate window. Default value: NO

Band change rule keys

BAND_MIN_LIMITS Bandwise minimum and maximum times. Only used by Bande Basse local Italian contest.
Syntax: BAND_MIN_LIMITS=band;maxminutes;minfromlastqsominutes.
MULTISINGLE_RULE10_ENABLED 10-minute rule for Multi-single operation enabled. Default value: YES
MULTISINGLE_RULE10_FOR_MULT 10-minute rule for Multi-single operation applies for multiplier station. Default value: YES
MULTISINGLE_RULE10_MINUTES Actual number of minutes for 10-minute rule for Multi-single operation. Default value: 10
MULTISINGLE_RULE10_CHECKMODE Checking principle for 10-minute rule. Default value: PER_BAND
MULTIOP_BANDCHANGECOUNTER_ENABLED Band change counter for multi operator operation enabled. Default value: YES
MULTIOP_BANDCHANGES_ALLOWED Semicolon-separated list with number of band changes allowed in one hour in multi operator operation.
The same number of entries as MULTIOP_BANDCHANGES_CBR_TRANSMITTERS.
Default value: 8
MULTIOP_BANDCHANGES_CHECKMODE Type of counting method for band changes in multi operator operation.
Valid values: PER_BAND or PER_BAND_MODE
Default value: PER_BAND
MULTIOP_BANDCHANGES_TYPE Semicolon-separated list with type of band changes counted for band change rule in multi operator operation.
R, RM, or ALL. (Run station, Run+Mult station, all stations)
The same number of entries as MULTIOP_BANDCHANGES_CBR_TRANSMITTERS.
Default value: R
MULTIOP_BANDCHANGES_CBR_CATEGORIES Semicolon-separated list of Cabrillo operator categories subject to band change rule. Default value: MULTI-OP
MULTIOP_BANDCHANGES_CBR_TRANSMITTERS Semicolon-separated list of Cabrillo transmitter categories subject to band change rule. Default value: TWO

Contest score keys

SCORE Scoring principle.
Valid values: BY_BAND, BY_BAND_MODE, BY_PERIOD, BY_PERIOD_BAND,
and BY_PERIOD_BAND_MODE
Default value: BY_BAND
SCORE_DISPLAY Displayed columns in Summary window. Available elements: BAND, QSO, POINTS, MULT1,
MULT2, MULT3, DUP, AVG, AVG0, QTC, PERIOD, BAND, and MODE.
A string within parenthesis following the element name will set the column header.
Per mode display can be achieved by including the relevant mode(s) within curly brackets.
Multiple modes are separated by '+'.
Example: SCORE_DISPLAY=BAND;QSO(SSB){SSB};QSO(CW){CW};QSO(DIGI){RTTY+PSK31+PSK63};DUP
will group all RTTY, PSK31, and PSK63 QSO under the same heading.
Elements can be conditional using the *+NN:MM:LL> syntax or *RGX: followed by a regular expressions (see above).
Example: *-K:VE> will display the column if your station is not a K or VE station.
Example: *+SM:OZ:LA:OH> will display the column only if you are a SM, OZ, LA, or OH station.
Default value: BAND;QSO;POINTS;MULT1
SCORE_TOTAL Principle for total score.
Valid values: BY_BAND_GROUP and BY_MODE_GROUP.
Default value: Empty
SCORE_TOTAL_FX Formula for calculating total score for a QSO. Uses FLEE syntax which includes e.g. If().
Example: SCORE_TOTAL_FX=$FIELDVALUE.Points*$FIELDVALUE.Mult1+$FIELDVALUE.Mult3
No default value
SCORE_BAND_GROUP List of bands for PER_BAND_GROUP scoring.
Syntax: SCORE_BAND_GROUP=bandgroup1{band1,band2,band3};bandgroup2{band4,band5}
No default value
SCORE_MODE_GROUP List of modes for PER_MODE_GROUP scoring.
Syntax: SCORE_MODE_GROUP=modegroup1{mode1,mode2};modegroup2{mode3,mode4}
No default value

QSO points keys

POINTS_TYPE Type of points.
Valid values: CALC, QRB, QRB_EXCHANGE+CALCF, QRB+CALCF, RAEM, and FROM_TABLE()
CALC expects the presence of POINTS_FIELD_BAND_MODE keys. QRB means one point per kilometer.
QRB_EXCHANGE+CALCF requires at least one POINTS_CALC_F key and uses a grid in the configuration
panel's Exchange field for QRB calculation. QRB only works with 6-position grids.
QRB+CALCF requires at least one POINTS_CALC_F key and uses the configuration panel's
Grid field for QRB calculation. RAEM uses the special RAEM contest point system.
FROM_TABLE(filename;keytype;sourcekey;destkey) requires a database text file
that maps an exchange value to points. keytype is always INT,
sourcekey is always "EXCHANGE", destkey can be RCVD, RECINFO, RECINFO2, or RECINFO3.
The format of each line in the file is sourcekey value;destkey value=points.
Default value: CALC
POINTS_BAND_BONUS Per band scaling factor. Syntax POINTS_BAND_BONUS=band;scaling.
Example: POINTS_BAND_BONUS=160;2 doubles the points number on the 160m band.
Default value: 1 on all bands.
POINTS_FIELD_BAND_MODE Conditional point calculation.
Syntax: POINTS_FIELD_BAND_MODE=regexp1;regexp2;bandregexp;moderegexp;points;optionalregexp
NB. When designing points rules, be aware that the first valid rule encountered,
reading from the top, overrides all subsequent rules.
No default value
POINTS_CALC_F Formula for points calculation.
Syntax: POINTS_CALC_F=sourceregexp;pointsformula;bandregexp;calculationregexp
Example:POINTS_CALC_F=ALL;VALUE*5.0;^15$;QRB>=100&&QRB<=800
multiplies points with 5 on 15m if QRB is between 100 and 800km.
All mathematical functions in C# syntax, plus the points number (VALUE) are
available for expressions. In the calculationregexp, QRB can also be used.
Additionally, the two alternative syntaxes VALUE{QRB:grid}
which has the value of the distance (in km) to a particular grid square, and
VALUE{*QRB:grid} which has the value of distance from a particular grid square.
No default value

Progress tracking keys

WINDOWS_CML_ENABLED Enable custom multiplier window #1. Default value: NO
WINDOWS_CML2_ENABLED Enable custom multiplier window #2. Default value: NO
WINDOWS_CML3_ENABLED Enable custom multiplier window #3. Default value: NO
WINDOWS_CML_NAME Name of custom multiplier #1. No default value
WINDOWS_CML2_NAME Name of custom multiplier #2. No default value
WINDOWS_CML3_NAME Name of custom multiplier #3. No default value
WINDOWS_CML_LIST_FX
WINDOWS_CML2_LIST_FX
WINDOWS_CML3_LIST_FX
C# expression for the multipliers listed in custom multiplier window for MULT.
Syntax: WINDOWS_CML_LIST_FX=function.
Example: WINDOWS_CML_LIST_FX=GetList_PrefixArea(dxccList,"^VE$|^VK$|^JA$|^ZL$")
Example:
WINDOWS_CML_LIST_FX=GetList_CustomArray("A|C|CA|CC|CE|GR|IB|J|LO||MU|NA|O|SS|T|V|VI|Z","|")
No default value
WINDOWS_CML_DATA
WINDOWS_CML2_DATA
WINDOWS_CML3_DATA
Source of data for custom multiplier window 1, 2, and 3.
Valid values: MULT1, MULT2, MULT3, QSODIFF, QSODIFF_SP, and QSODIFF_CQ.
No default value
WINDOWS_CML_SHOW_GROUP
WINDOWS_CML2_SHOW_GROUP
WINDOWS_CML3_SHOW_GROUP
Controls if customer multiplier window 1, 3, and 3 show the multipliers grouped, is such are defined.
Valid values: YES and NO.
Default value: NO
WINDOWS_CML_RESIZABLE
WINDOWS_CML2_RESIZABLE
WINDOWS_CML3_RESIZABLE
Controls if custom multiplier windows are resizable. Default value: NO
WINDOWS_CML_LABELS_IN_ROW
WINDOWS_CML2_LABELS_IN_ROW
WINDOWS_CML3_LABELS_IN_ROW
Controls number of MULT labels in each row of its custom multiplier window.
Valid values: -1 and positive integers. -1 means DXLog default.
Default value: -1
WINDOWS_CML_ALL_LABELS_IN_ROW
WINDOWS_CML2_ALL_LABELS_IN_ROW
WINDOWS_CML3_ALL_LABELS_IN_ROW
Controls the number of MULT labels in all each row of its custom multiplier window
when there is no fixed list of allowed multipliers and the window therefore grows gradually
during the contest, such as the HQ multiplier in IARU HFC.
Valid values: -1 and positive integers. -1 means DXLog default.
Default value: -1
WINDOWS_CML_HIDDEN_CONT
WINDOWS_CML2_HIDDEN_CONT
WINDOWS_CML3_HIDDEN_CONT
Hides a custom multiplier window for stations from selected continents. Currently not used in any contest. Default value: None
WINDOWS_CML_HIDDEN_DXCC
WINDOWS_CML2_HIDDEN_DXCC
WINDOWS_CML3_HIDDEN_DXCC
Hides a custom multiplier window for stations from selected DXCC.
Syntax: WINDOWS_CML_HIDDEN_DXCC=list
Example: WINDOWS_CML_HIDDEN_DXCC=*+G;GI;GW;GM;GJ;GU;GD
hides the custom multiplier window for UK stations.
Example: WINDOWS_CML_HIDDEN_DXCC=*-SM;LA;OZ;OH
shows the custom multiplier window only for Scandinavian stations.
No default value
WINDOWS_WKD_DXCC_ENABLED Enables worked DXCC window.
Valid values: YES and NO.
Default value: NO
WINDOWS_WKD_DXCC_HIDDEN_CONT Hides worked DXCC window for stations from selected continent.
Example: WINDOWS_WKD_DXCC_HIDDEN_CONT=*-AS shows only the
worked DXCC window for Asian stations.
No default value
WINDOWS_WKD_DXCC_HIDDEN_DXCC Hides worked DXCC window for stations from selected DXCC.
C.f. WINDOWS_CML_HIDDEN_DXCC above for syntax.
No default value
WINDOWS_WKD_DXCC_SHOW_ONLY_CONT Show only entities from the listed continents in the worked DXCC window.
Example: WINDOWS_WKD_DXCC_SHOW_ONLY_CONT=NA;SA shows
only NA and SA entities in the worked DXCC window.
No default value
WINDOWS_WKD_DXCC_CONT_FILTER Defines which DXCC entities from a selected continent to show in the worked DXCC window.
Example: WINDOWS_WKD_DXCC_CONT_FILTER=SA:9Y;P4;PJ2;PJ4 will only
include 9Y, P4 and PJ2 from South America.
You can have several of this key.
No default value
WINDOWS_WKD_DXCC_HIDE_DXCC Hides a list of DXCC entities from the worked DXCC window.
Example: WINDOWS_WKD_DXCC_HIDE_DXCC=K;VE hides US
and Canada from the worked DXCC window.
No default value
WINDOWS_WKD_GRID_ENABLED Enables worked grids window.
Valid values: YES and NO.
Default value: NO
WINDOWS_WKD_PFX_ENABLED Enables worked prefixes window.
Valid values: YES and NO.
Default value: NO
WINDOWS_WKD_PFX_HIDDEN_CONT Hides worked prefixes window for stations from selected continent.
C.f. WINDOWS_WKD_DXCC_HIDDEN_CONT above for syntax.
Default is to hide nothing
WINDOWS_WKD_PFX_HIDDEN_DXCC Hides worked prefixes window for stations from selected DXCC.
C.f. WINDOWS_CML_HIDDEN_DXCC above for syntax.
Default is to hide nothing
WINDOWS_WKD_PFX_DATA Source of worked prefixes data.
Valid values: MULT1, MULT2, and MULT3.
No default value

Livescore keys

LIVESCORE_CONTEST_NAME Contest name used for live score reporting. Default value: CABRILLO_CONTEST_NAME.
LIVESCORE_OPERATOR List of types of operation used for live score reporting.
List must have the same number of items as mode categories.
Default value: CABRILLO_OPERATOR
LIVESCORE_POWER List of output power classes used for live score reporting.
List must have the same number of items as mode categories.
Default value: CABRILLO_POWER
LIVESCORE_TRANSMITTER List of number of transmitters categories used for live score reporting.
List must have the same number of items as mode categories.
Default value: CABRILLO_TRANSMITTER
LIVESCORE_ASSISTED List of assistance categories used for live score reporting.
List must have the same number of items as mode categories.
Default value: CABRILLO_ASSISTED
LIVESCORE_MODE List of modes used for live score reporting.
List must have the same number of items as mode categories.
Default value: CABRILLO_MODE
LIVESCORE_MULT List of multiplier "names" in numerical order used for live score reporting.
Must have the same number of items as contest multipliers.
By default DXLog uses "country",
"zone", "prefix", and "state".

QTC keys

QTC_ENABLED Enables QTC mechanics. Default value: NO
QTC_SEND_ENABLED Enables QTC sending. Default value: !SOURCE->CONT:^EU$
QTC_RECV_ENABLED Enables QTC receiving. Default value: SOURCE->CONT:^EU$
QTC_SEND_RGX Regular expression controlling the transmission of QTC. Default value: DEST->CONT:^EU$
QTC_RECV_RGX Regular expression controlling the reception of QTC. Default value: !DEST->CONT:^EU$

Other keys

ASTROPHYSICS Enables DXLog's propagation enhancing features.
Valid values: YES and NO.
Default value: NO
WARNING_FILE Name of frequency range warning file located in %appdata%\DXLog\Database.
The format of each line in the warning file is Mode regular expression;frequency range;Message
Example:
# Format=Mode regex pattern;Frequency range;Warning message
CW;3400-3520;Warning: Operation not allowed on this frequency
CW;3550-3900;Warning: Operation not allowed on this frequency
SB;3400-3600;Warning: Operation not allowed on this frequency
SB;3675-3700;Warning: Operation not allowed on this frequency
SB;3725-3900;Warning: Operation not allowed on this frequency
No default value
ADIF_KEYS Allows for including custom keys in ADIF export. The syntax is ADIF_KEYS=ADIFKEY;Expression;Regexp.
Regexp is optional but must evaluate as true for the key to be included in the export.
The syntax for Expression is C# and based on internal DXQSO object structure.
Received exchanges are $VALUE.Rcvd, $VALUE.Rcvd4, $VALUE.RecInfo, $VALUE.RecInfo2,
and $VALUE.RecInfo3. Rcvd4 is the Rcvd object without the signal report. So to, for instance, export the
received exchange as US/VE state use ADIF_KEYS=STATE;$VALUE.Rcvd4;DEST->DXCC:^K$|^VE$.
To export the second part of the exchange as operator name use ADIF_KEYS=NAME;$VALUE.RecInfo
The following $VALUE.xxx keys are available: Sent, Rcvd, Rcvd4, RecInfo, RecInfo2, RecInfo3,
Az, Mult, Mult1, Mult2, Mult3, Lp, Period, Band, Mode, Callsign, QRB (integer),
Stn, OriginStndID, Operator,
and RadioVFO.
Please note that you can also use C# style string manipulation such as Substring(start, length) etc.
There is no limit on the number of ADIF_KEYS lines in a contest definition file.
Default value: None
WINDOWS_ON4KST_ENABLED Enables ON4KST messaging window Default value: No
SPRINT_LOGIC_ALLOWED Allow sprint logic. Default value: NO
OVERRIDE_INVALID_QSO_MESSAGE Suppress invalid QSO message for selected cases.
Syntax is OVERRIDE_INVALID_QSO_MESSAGE=IncaseRegexp1;AndRegexp2
Example: OVERRIDE_INVALID_QSO_MESSAGE=DEST->DXCC:^K$;DEST->RCVD:^$ will
not complain about empty RCVD field for US stations. (It will however not allow logging.)
Default value: None