Difference between revisions of "Contest definition"

From DXLog.net
Jump to navigation Jump to search
(Additional Configuration Entries)
(Additional Configuration Entries)
 
Line 753: Line 753:
 
{|class="wikitable"
 
{|class="wikitable"
 
|+style="text-align:Left;"|Additional configuration entries.<br>
 
|+style="text-align:Left;"|Additional configuration entries.<br>
| '''Key'''
 
| '''Description'''
 
| '''Default'''
 
|-
 
 
| '''BAND_BONUS'''
 
| '''BAND_BONUS'''
 
|  
 
|  
Line 851: Line 847:
 
| '''DB_FILE_TYPE'''
 
| '''DB_FILE_TYPE'''
 
| Extension of data base file
 
| Extension of data base file
| .TXT
+
| Default value: .TXT
 
|-
 
|-
 
| '''DB_FILE1_TYPE'''
 
| '''DB_FILE1_TYPE'''
 
| Extension of data base file
 
| Extension of data base file
| .TXT
+
| Default value: .TXT
 
|-
 
|-
 
| '''DB_FILE2_TYPE'''
 
| '''DB_FILE2_TYPE'''
 
| Extension of data base file
 
| Extension of data base file
| .TXT
+
| Default value: .TXT
 
|-
 
|-
 
| '''DB_FILE3_TYPE'''
 
| '''DB_FILE3_TYPE'''
 
| Extension of data base file
 
| Extension of data base file
| .TXT
+
| Default value: .TXT
 
|-
 
|-
 
| '''DB_FILE4_TYPE'''
 
| '''DB_FILE4_TYPE'''
 
| Extension of data base file
 
| Extension of data base file
| .TXT
+
| Default value: .TXT
 
|-
 
|-
 
| '''DB_FILE5_TYPE'''
 
| '''DB_FILE5_TYPE'''
 
| Extension of data base file
 
| Extension of data base file
| .TXT
+
| Default value: .TXT
 
|-
 
|-
 
| '''DB_FILE_COL_RCVD'''
 
| '''DB_FILE_COL_RCVD'''
Line 1,339: Line 1,335:
 
| '''WINDOWS_CML_ENABLED'''
 
| '''WINDOWS_CML_ENABLED'''
 
| Enable custom multiplier window #1
 
| Enable custom multiplier window #1
| No
+
| Default value: No
 
|-
 
|-
 
| '''WINDOWS_CML2_ENABLED'''
 
| '''WINDOWS_CML2_ENABLED'''
 
| Enable custom multiplier window #2
 
| Enable custom multiplier window #2
| No
+
| Default value: No
 
|-
 
|-
 
| '''WINDOWS_CML3_ENABLED'''
 
| '''WINDOWS_CML3_ENABLED'''
 
| Enable custom multiplier window #3
 
| Enable custom multiplier window #3
| No
+
| Default value: No
 
|-
 
|-
 
| '''WINDOWS_CML_NAME'''
 
| '''WINDOWS_CML_NAME'''
Line 1,399: Line 1,395:
 
| '''WINDOWS_CML_RESIZABLE'''
 
| '''WINDOWS_CML_RESIZABLE'''
 
| Controls if custom multiplier window #1 is resizable
 
| Controls if custom multiplier window #1 is resizable
| No
+
| Default value: No
 
|-
 
|-
 
| '''WINDOWS_CML2_RESIZABLE'''
 
| '''WINDOWS_CML2_RESIZABLE'''
 
| Controls if custom multiplier window #2 is resizable
 
| Controls if custom multiplier window #2 is resizable
| No
+
| Default value: No
 
|-
 
|-
 
| '''WINDOWS_CML3_RESIZABLE'''
 
| '''WINDOWS_CML3_RESIZABLE'''
 
| Controls if custom multiplier window #3 is resizable
 
| Controls if custom multiplier window #3 is resizable
| No
+
| Default value: No
 
|-
 
|-
 
| '''WINDOWS_CML_LABELS_IN_ROW'''
 
| '''WINDOWS_CML_LABELS_IN_ROW'''
Line 1,503: Line 1,499:
 
| '''WINDOWS_ON4KST_ENABLED'''
 
| '''WINDOWS_ON4KST_ENABLED'''
 
| Enables ON4KST messaging window  
 
| Enables ON4KST messaging window  
| No
+
| Default value: No
 
|-
 
|-
 
| '''CABRILLO_EXPORT_TYPE'''
 
| '''CABRILLO_EXPORT_TYPE'''
Line 1,539: Line 1,535:
 
| '''QTC_ENABLED'''
 
| '''QTC_ENABLED'''
 
| Enables QTC mechanics
 
| Enables QTC mechanics
| No
+
| Default value: No
 
|-
 
|-
 
| '''QTC_SEND_ENABLED'''
 
| '''QTC_SEND_ENABLED'''

Latest revision as of 19:11, 9 January 2020

Description

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.net,
contest rules are defined and controlled through a contest config file.

Contest config files are "human readable", plain text files located in the Contest sub-folder in
DXLog.net's installation folder. A wide range of contest definition files are included in the DXLog.net 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.net 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.net 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.net release.
To secure that a contest config file is not overwritten by future DXLog.net 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.net's standard contest repertoire.

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 9A CW is the field value.

Regular expressions (regex)

You will see that in many cases DXLog.net is using regular expressions (regex) to verify condition validation and possibly to process an entry in a special way.

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

Regex expressions in the config file can be defined as fixed values, but regex can also compare QSO data against fixed values.

Case one: 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 DX in the EXCHANGE field on the contest configuration screen.

The regex key field 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$|^DX$


^ in expression denotes start of the string value
$ in expression denotes end of string value
| in expression is the logical or operation


Case two: 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 regex key field for qso points calculation is POINTS_FIELD_BAND_MODE. So 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.

Keys Reference:
SOURCE->CONT Our continent
SOURCE->DXCC Our DXCC
SOURCE->CALL Our callsign
SOURCE->PFX Our prefix
SOURCE->WPX Our WPX prefix
DEST->CONT Other station's continent
DEST->DXCC Other station's DXCC
DEST->CALL Other stations' callsign
DEST->RCVD Value entered in the RCVD field of QSO line
DEST->RECINFO Value entered in the RECINFO field of QSO line
DEST->RECINFO2 Value entered in the RECINFO2 field of QSO line
DEST->RECINFO3 Value entered in the RECINFO3 field of QSO line
CONFIG->EXCHANGE Value from the contest exchange field in the contest configuration panel
CONFIG->CQZONE Value from the WAZ/CQ Zone field in the contest configuration panel
CONFIG->ITUZONE Value from the ITU zone field in the contest configuration panel
CONFIG->OPNAME Value from the OPNAME field in the contest configuration panel
CONFIG->POWER Value from the POWER field in the contest configuration panel

General contest description

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, 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.
CONTESTRULES External HTTP Link to contest rules. eg. https://www.cqww.com/rules.htm
CONTESTWEB External HTTP Link to contest rules. eg. https://www.cqww.com

Contest Configuration Window Control

These keys are used for setting the contest configuration variables in the user configuration window.
CATEGORIES List of available categories separated by ";" to build category selection list at contest configuration screen. Default value: Single operator;Single operator assisted;Multioperator, single transmitter;Multioperator, two transmitter; Multi operator, multi-transmitter
CATEGORY_MODES List of available modes separated by ";" to build mode selection list at contest configuration screen. Default value: CW;SSB;MIXED
CLASS List of available classes separated by ";" to build class selection list at contest configuration screen. Default value: High;Low;QRP
OVERLAY List of available category overlays separated by ";" to build overlay selection list at contest configuration screen. Default value: Band restricted; Radio Club; Dxpedition; Headquarters; Open; Restricted; Novice; Classic; Rookie; Tribander/Single element; QRP; Fixed station; Portable station
CFG_MULT Controls exchange field at contest configuration screen. Acceptable values are: YES/NO. If set to YES, exchange field will be enabled for entering data. Usually in exchange field user enters own multiplier, zone or some other info. Default value: NO
CFG_MULT_DX_ALLOWED Is "DX" acceptable entry in exchange field at contest configuration screen. For example in ARRL DX Contest, all USA/VE stations needs to enter their state/province, while all other stations enters DX here. Acceptable values are: YES/NO
Default value: NO
CFG_MULT_MANDATORY Is exchange field mandatory (needs to be filled) or can be blank. Acceptable values are: YES/NO
Default value: NO
CFG_MULT_ERRORTEXT Defines error text which will be shown in case that user enters wrong data in exchange field at contest configuration screen. For example, in ARRL DX Contest, user enters state abbreviation which isn't on predefined list.
CFG_MULT_FROM Defines where we can check if user entry in exchange field is valid. Can have value like CUSTOM_MULT_LIST or ITUZONE. Can be blank if we are using regex expression to check the value or we can accept any entry.
CFG_MULT_RGX_CHECK Regex expression which will be used to verify if data entered in exchange field at contest configuration screen is valid. Please note that regex expression can contains special tag CUSTOM_MULT_LIST too. This means that any entry specified in custom multiplier list will be valid entry.
CFG_CQZONE_ERRORTEXT Defines error text which will be shown in case that user enters wrong data in WAZ field at contest configuration screen.
CFG_CQZONE_MANDATORY Is WAZ field mandatory (needs to be filled) or can be blank. Acceptable values are: YES/NO
Default value: NO
CFG_GRID_ERRORTEXT Defines error text which will be shown in case that user enters wrong data in GRIDSQUARE field at contest configuration screen.
CFG_GRID_MANDATORY Is GRIDSQUARE field mandatory (needs to be filled) or can be blank. Acceptable values are: YES/NO
Default value: NO
CFG_GRID_RGX_CHECK Regex expression which will be used to verify if data entered in GRIDSQUARE field at contest configuration screen is valid.
CFG_ITUZONE_ERRORTEXT Defines error text which will be shown in case that user enters wrong data in ITU field at contest configuration screen.
CFG_ITUZONE_MANDATORY Is ITU field mandatory (needs to be filled) or can be blank. Acceptable values are: YES/NO
Default value: NO
CFG_MYDXCC_ERRORTEXT Defines error text which will be shown in case that user enters wrong data in DXCC field at contest configuration screen.
CFG_MYDXCC_MANDATORY Is DXCC field mandatory (needs to be filled) or can be blank. Acceptable values are: YES/NO
Default value: NO
CFG_OPNAME_ERRORTEXT Defines error text which will be shown in case that user enters wrong data in OPNAME field at contest configuration screen.
CFG_OPNAME_MANDATORY Is OPNAME field mandatory (needs to be filled) or can be blank. Acceptable values are: YES/NO
Default value: NO
CFG_POWER_ERRORTEXT Defines error text which will be shown in case that user enters wrong data in POWER field at contest configuration screen.
CFG_POWER_MANDATORY Is POWER field mandatory (needs to be filled) or can be blank. Acceptable values are: YES/NO
Default value: NO
CFG_POWER_RGX_CHECK Regex expression which will be used to verify if data entered in POWER field at contest configuration screen is valid.
CFG_STATE_ERRORTEXT Defines error text which will be shown in case that user enters wrong data in STATE/PROVINCE/OTHER field at contest configuration screen.
CFG_STATE_FROM Defines where we can check if user entry in STATE/PROVINCE/OTHER field is valid. Can have value like CUSTOM_MULT_LIST or ITUZONE. Can be blank if we are using regex expression to check the value or we can accept any entry.
CFG_STATE_MANDATORY Is STATE/PROVINCE/OTHER field mandatory (needs to be filled) or can be blank. Acceptable values are: YES/NO
Default value: NO
CFG_STATE_RGX_CHECK Regex expression which will be used to verify if data entered in STATE/PROVINCE/OTHER field at contest configuration screen is valid. Please note that regex expression can contains special tag CUSTOM_MULT_LIST too. This means that any entry specified in custom multiplier list will be valid entry.

Cabrillo

 CABRILLO_ASSISTED
 CABRILLO_BAND
 CABRILLO_CONTEST_NAME
 CABRILLO_DEF_RECINFO
 CABRILLO_DEF_RECINFO2
 CABRILLO_DEF_RECINFO3
 CABRILLO_DXPEDITION
 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 name and entered into the Cabrillo file in the order entered, E.g. FREQ will enter Frequency of QSO, MODE will enter Mode etc
Formatting information is contained within the {} F= is the formatting call and should be followed by the following parameters: Alignment: L(eft), R(ight) Total size for alignment: How many characters is used for formatting, padding, alignment. Padding character: Which character will be used for filling empty spaces And last one is optional: Total size of the field in Cabrillo field.
E.g.: RCVD2{F=R,3,0,4} RCVD2 field value will be aligned Right, on length of 3 characters. For padding, we using "0" characters. End total size will be 4 characters (so we will add one more space if needed to have size of 4 chars). This means that if RCVD2 field value is "1", it will be formatted as " 001" and this value will be written in Cabrillo QSO line.
 CABRILLO_LOCATION_CHECK
 CABRILLO_LOCATION_DEFAULT
 CABRILLO_LOCATION_PROMPT
 CABRILLO_MODES
 CABRILLO_OPERATOR
 CABRILLO_OVERLAY
 CABRILLO_OVERLAY_DISABLED
 CABRILLO_POWER
 CABRILLO_QTC_LINE
 CABRILLO_TIME
 CABRILLO_TRANSMITTER

Band and mode specific


BANDS A semicolon-separated list of available bands for the contest. Default value: 160;80;40;20;15;10
MODES A semicolon-separated list of available modes for the contest. Default value: CW;SSB
EDI_BANDS A list of EDI values for bands specified in BANDS key. Must contain same number of entries as BANDS key. This is used for generating EDI log files for VHF/UHF/SHF contests in IARU Region I.

Entry field definitions

These keys are used to control the layout of QSO entry screen. 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. Allowed values: YES/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. Allowed values: YES/NO
Default value: NO
FIELD_MODE_VISIBLE Mode field visible on the QSO entry line. Allowed values: YES/NO
Default value: NO
FIELD_MODE_NAME Header for mode field.
FIELD_MULT_VISIBLE MULT field visible on the screen. Allowed values: YES/NO
Default value: NO
FIELD_MULT_MAX_LENGTH Max length of MULT field.
FIELD_NR_VISIBLE SENT QSO SERIAL NUMBER visible on the QSO entry line. Allowed values: YES/NO
Default value: NO
FIELD_NR_HIDDEN_DXCC List of DXCC separated by ";". If our own DXCC is on this list, SENT QSO SERIAL NUMBER 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).
FIELD_NR_HIDDEN_RGX Regular expression. If the condition is valid, SENT QSO SERIAL NUMBER will be hidden. Useful for contests where some stations are sending a serial number exchange and other stations are sending other date (for example a local province).
FIELD_PERIOD_VISIBLE Is field PERIOD number visible on QSO entry line. Allowed values: YES/NO
Default value: NO
FIELD_PERIOD_NAME Header for PERIOD field.
FIELD_PTS_VISIBLE Is field POINTS visible in QSO entry line. Allowed values: YES/NO
Default value: NO
FIELD_PTS_NAME Header for POINTS field.
FIELD_RCVD_CHECK_FORMAT_FX C# expression to reformat entered value in RCVD field before further checking.
FIELD_RCVD_COPY If field RCVD is automatically copied from previous QSO with same station. Allowed values: YES/NO
FIELD_RCVD_COPY_EXC_DXCC List of DXCC countries separated by ";" which are exception for copy value. Useful in case when we want to copy value from previous QSO only for some station.
FIELD_RCVD_COPY_EXC_RGX Regular expression. If condition is true, we have a value copy exception for the QSO.
FIELD_RCVD_COPY_FX C# expression used to copy value from previous QSO.
FIELD_RCVD_DEFAULT_VALUE Value to be used in Cabrillo output if RCVD field is empty.
FIELD_RCVD_EXC_CHECK_DXCC List of DXCC countries separated by ";" which are exception for value checking procedure.
FIELD_RCVD_FORMAT_FX C# expression used to format entered value before saving.
FIELD_RCVD_FX_CHECK C# expression used to check if value entered in RCVD field is valid.
FIELD_RCVD_MANDATORY If RCVD field entry is mandatory. Allowed values: YES/NO
Default value: NO
FIELD_RCVD_MANDATORY_RGX_EXC Regular expression. If condition is true, we have exception from mandatory rule.
FIELD_RCVD_MAX_LENGTH Maximum number of characters accepted in RCVD field.
FIELD_RCVD_MIN_LENGTH Minimum number of characters accepted in RCVD field.
FIELD_RCVD_AUTOSKIP Controls wether RCVD field is automatically skipped when pressing space bar.
FIELD_RCVD_NUMERIC Controls if RCVD field accepts only numeric characters. Allowed values: YES/NO
Default value: NO
FIELD_RCVD_SLASH_ALLOWED Controls if RCVD field accepts a slash "/" character. Allowed values: YES/NO
Default value: NO
FIELD_RCVD_RGX_CHECK Regular expression. Used to check if entry in RCVD field is valid.
FIELD_RCVD_TYPE Define type of RCVD field for possible calculations and check routines. For example: MULT, NR, CONT etc.
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. Allowed values: YES/NO
Default value: NO
FIELD_RECINFO_CHECK_FORMAT_FX C# expression to reformat entered value in RECINFO field before further checking.
FIELD_RECINFO_COPY If field RECINFO should be automatically copied from previous QSO with same station. Allowed values: YES/NO
Default value: NO
FIELD_RECINFO_COPY_RGX_EXC Regular expression. If condition is true, we have exception from mandatory rule.
FIELD_RECINFO_FORMAT_FX C# expression used to format entered value before saving.
FIELD_RECINFO_FX_CHECK C# expression used to check if value entered in RECINFO field is valid.
FIELD_RECINFO_MANDATORY If RECINFO field entry is mandatory. Allowed values: YES/NO
Default value: NO
FIELD_RECINFO_MANDATORY_RGX_EXC Regular expression. If condition is true, we have exception from mandatory rule.
FIELD_RECINFO_MAX_LENGTH Maximum number of characters accepted in RECINFO field.
FIELD_RECINFO_MIN_LENGTH Minimum number of characters accepted in RECINFO field.
FIELD_RECINFO_NAME Header for RECINFO field.
FIELD_RECINFO_NUMERIC Controls if RECINFO field accepts only numeric characters. Allowed values: YES/NO
Default value: NO
FIELD_RECINFO_RGX_CHECK Regular expression. Used to check if entry in RECINFO field is valid.
FIELD_RECINFO_RGX_SEL_POS
FIELD_RECINFO_TYPE Define type of RECINFO field for possible calculations and check routines. For example: MULT, NR, CONT etc.
FIELD_RECINFO_VISIBLE Controls wether the RECINFO field is visible. Allowed values: YES/HIDDEN/READONLY. Default value: HIDDEN
FIELD_RECINFO2_CHECK_FORMAT_FX C# expression to reformat entered value in RECINFO2 field before further checking.
FIELD_RECINFO2_COPY Is field RECINFO2 automatically copied from previous QSO with same station. Allowed values: YES/NO
FIELD_RECINFO2_COPY_RGX_EXC Regular expression. If condition is true, we have exception from mandatory rule.
FIELD_RECINFO2_FORMAT_FX C# expression used to format entered value before saving.
FIELD_RECINFO2_FX_CHECK C# expression used to check if value entered in RECINFO2 field is valid.
FIELD_RECINFO2_MANDATORY If RECINFO2 field entry is mandatory. Allowed values: YES/NO
Default value: NO
FIELD_RECINFO2_MANDATORY_RGX_EXC Regular expression. If condition is true, we have exception from mandatory rule.
FIELD_RECINFO2_MAX_LENGTH Maximum number of characters accepted in RECINFO2 field.
FIELD_RECINFO2_MIN_LENGTH Minimum number of characters accepted in RECINFO2 field.
FIELD_RECINFO2_NAME Header for RECINFO2 field.
FIELD_RECINFO2_NUMERIC Controls if RECINFO2 field accepts only numeric characters. Allowed values: YES/NO
Default value: NO
FIELD_RECINFO2_RGX_CHECK Regular expression. Used to check if entry in RECINFO2 field is valid.
FIELD_RECINFO2_RGX_SEL_POS
FIELD_RECINFO2_TYPE Define type of RECINFO2 field for possible calculations and check routines. For example: MULT, NR, CONT etc.
FIELD_RECINFO2_VISIBLE Controls wether the RECINFO2 field is visible. Allowed values: YES/HIDDEN/READONLY. Default value: HIDDEN
FIELD_RECINFO3_CHECK_FORMAT_FX C# expression to reformat entered value in RECINFO3 field before further checking.
FIELD_RECINFO3_COPY Is field RECINFO3 automatically copied from previous QSO with same station. Allowed values: YES/NO
Default value: NO
FIELD_RECINFO3_COPY_RGX_EXC Regular expression. If condition is true, we have exception from mandatory rule.
FIELD_RECINFO3_FORMAT_FX C# expression to reformat entered value in RECINFO3 field before further checking.
FIELD_RECINFO3_FX_CHECK C# expression used to check if value entered in RECINFO3 field is valid.
FIELD_RECINFO3_MANDATORY If RECINFO3 field entry is mandatory. Allowed values: YES/NO
Default value: NO
FIELD_RECINFO3_MANDATORY_RGX_EXC Regular expression. If condition is true, we have exception from mandatory rule.
FIELD_RECINFO3_MAX_LENGTH Maximum number of characters accepted in RECINFO3 field.
FIELD_RECINFO3_MIN_LENGTH Minimum number of characters accepted in RECINFO3 field.
FIELD_RECINFO3_NAME Header for RECINFO3 field.
FIELD_RECINFO3_NUMERIC Controls if RECINFO3 field accepts only numeric characters. Allowed values: YES/NO
Default value: NO
FIELD_RECINFO3_RGX_CHECK Regular expression. Used to check if entry in RECINFO3 field is valid.
FIELD_RECINFO3_RGX_SEL_POS
FIELD_RECINFO3_TYPE Define type of RECINFO field for possible calculations and check routines. For example: MULT, NR, CONT etc.
FIELD_RECINFO3_VISIBLE Controls wether the RECINFO3 field is visible. Allowed values: YES/HIDDEN/READONLY. Default value: HIDDEN
FIELD_RST_3RD_LETTER
FIELD_RST_VISIBLE Controls visibility of RST field Allowed values: YES/NO
Default value: YES
FIELD_SENT_VISIBLE
FIELD_STN_VISIBLE

Default Messages

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"
SP_CW_MESSAGE_PLUS Default Plus message for S&P Default value: "$CR"
CW_MESSAGE_EXCHANGE_FILTER

Special Configuration Entries

DXC_COMMENT_EXTRACT
This entry is used to extract exchange or multiplier information from DXCluster 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 exchange field. 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 Regex expression that defines the data that is to be matched. Refer to any Regex definition text to determine the proper expression for the data to be extracted.
DXCC_DB_TYPE=CUSTOM_CTY
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 config file will be used.
DXCC_DB_FILENAME=<filename.dat>
This entry is used in conjunction with the DXCC_DB_TYPE entry to define the actual data file name. The file format is the same as the normal CTY.DAT file.

Additional Configuration Entries

Additional configuration entries.
BAND_BONUS
MODE_GROUP
DISPLAY_MODE_GROUPING
MIN_OFF_TIME
DXCC_DB_USE_ARRL_LIST
CONTEST_LENGTH
CONTEST_FIRST_HOUR
PERIOD
PERIOD_LENGTH
PERIOD_AUTOSWITCH
PERIOD_NUMBER
CALC_FROM_TIME
PERIOD_MODES
SPRINT_LOGIC_ALLOWED
INITIAL_SERIAL_NUMBER
WARNING_FILE
ADIF_KEYS
DB_FILE File name of prefill data base
DB_FILE1 File name of second prefill data base
DB_FILE2 File name of third prefill data base
DB_FILE3 File name of fourth prefill data base
DB_FILE4 File name of fifth prefill data base
DB_FILE5 File name of sixth prefill data base
DB_FILE_TYPE Extension of data base file Default value: .TXT
DB_FILE1_TYPE Extension of data base file Default value: .TXT
DB_FILE2_TYPE Extension of data base file Default value: .TXT
DB_FILE3_TYPE Extension of data base file Default value: .TXT
DB_FILE4_TYPE Extension of data base file Default value: .TXT
DB_FILE5_TYPE Extension of data base file Default value: .TXT
DB_FILE_COL_RCVD Column number of RCVD field in data base field
DB_FILE1_COL_RCVD Column number of RCVD field in data base field
DB_FILE2_COL_RCVD Column number of RCVD field in data base field
DB_FILE3_COL_RCVD Column number of RCVD field in data base field
DB_FILE4_COL_RCVD Column number of RCVD field in data base field
DB_FILE5_COL_RCVD Column number of RCVD field in data base field
DB_FILE_COL_RECINFO Column number of RECINFO field in data base field
DB_FILE1_COL_RECINFO Column number of RECINFO field in data base field
DB_FILE2_COL_RECINFO Column number of RECINFO field in data base field
DB_FILE3_COL_RECINFO Column number of RECINFO field in data base field
DB_FILE4_COL_RECINFO Column number of RECINFO field in data base field
DB_FILE5_COL_RECINFO Column number of RECINFO field in data base field
DB_FILE_COL_RECINFO2 Column number of RECINFO2 field in data base field
DB_FILE1_COL_RECINFO2 Column number of RECINFO2 field in data base field
DB_FILE2_COL_RECINFO2 Column number of RECINFO2 field in data base field
DB_FILE3_COL_RECINFO2 Column number of RECINFO2 field in data base field
DB_FILE4_COL_RECINFO2 Column number of RECINFO2 field in data base field
DB_FILE5_COL_RECINFO2 Column number of RECINFO2 field in data base field
DB_FILE_COL_RECINFO3 Column number of RECINFO3 field in data base field
DB_FILE1_COL_RECINFO3 Column number of RECINFO3 field in data base field
DB_FILE2_COL_RECINFO3 Column number of RECINFO3 field in data base field
DB_FILE3_COL_RECINFO3 Column number of RECINFO3 field in data base field
DB_FILE4_COL_RECINFO3 Column number of RECINFO3 field in data base field
DB_FILE5_COL_RECINFO3 Column number of RECINFO3 field in data base field
DB_FILE_FILL_FORMAT
DB_FILE1_FILL_FORMAT
DB_FILE2_FILL_FORMAT
DB_FILE3_FILL_FORMAT
DB_FILE4_FILL_FORMAT
DB_FILE5_FILL_FORMAT
RGX_GUESS_DB
QSO_NUMBER
QSO_NUMBER_CATEGORY
DOUBLE_QSO
MULT_SUM
DOUBLE_QSO_MINUTE_DIFFERENCE
MIN_VALID_QSO_DIFFERENCE
DOUBLE_QSO_MODE_CHECK
POINTS_TYPE
SCP_DATABASE_DISABLE
POINTS_BAND_BONUS
DXC_COMMENT_EXTRACT
OWN_MULT_VALID
CUSTOM_MULT_LENGTH
CFG_GRID_MANDATORY
CFG_GRID_ERRORTEXT
CFG_GRID_RGX_CHECK
RATE_ODX_VISIBLE
CONTINENT_LIST
OVERRIDE_INVALID_QSO_MESSAGE
MULT1_TYPE
MULT1_FX
MULT2_TYPE
MULT2_FX
MULT3_TYPE
MULT3_FX
MULT1_COUNT
MULT2_COUNT
MULT3_COUNT
MULT1_ADD_DXCC
MULT2_ADD_DXCC
MULT3_ADD_DXCC
MULT1_FIELD
MULT2_FIELD
MULT3_FIELD
MULT1_DISPLAY
MULT2_DISPLAY
MULT3_DISPLAY
MULT1_SHOWERROR
MULT2_SHOWERROR
MULT3_SHOWERROR
MULT1_BAND_BONUS
MULT2_BAND_BONUS
MULT3_BAND_BONUS
MULT1_BONUS
MULT2_BONUS
MULT3_BONUS
MULT1_EXCEPTION
MULT2_EXCEPTION
MULT3_EXCEPTION
MULT1_MULTIPLIER
MULT2_MULTIPLIER
MULT3_MULTIPLIER
MULT1_REPEAT
MULT2_REPEAT
MULT3_REPEAT
MULT1_CONT_LIST
MULT2_CONT_LIST
MULT3_CONT_LIST
FIRST_PREV_RCVD
FIRST_PREV_RECINFO
FIRST_PREV_RECINFO2
FIRST_PREV_RECINFO3
STATS_TYPE
DISPLAY_TIME_ON_PER_MODE
DISPLAY_LAST_MODE_CHANGE
BAND_MIN_LIMITS
MULTISINGLE_RULE10_ENABLED
MULTISINGLE_RULE10_MINUTES
MULTISINGLE_RULE10_CHECKMODE
MULTIOP_BANDCHANGECOUNTER_ENABLED
MULTIOP_BANDCHANGES_ALLOWED
MULTIOP_BANDCHANGES_CHECKMODE
MULTIOP_BANDCHANGES_TYPE
MULTIOP_BANDCHANGES_CBR_CATEGORIES
MULTIOP_BANDCHANGES_CBR_TRANSMITTERS
SLASH_MULTIPLE_QSOS
SCORE
SCORE_DISPLAY
SCORE_TOTAL
SCORE_TOTAL_FX
SCORE_BAND_GROUP
SCORE_MODE_GROUP
POINTS_FIELD_BAND_MODE
POINTS_CALC_F
DTB_SCP_FROM_RECINFO
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
WINDOWS_CML2_NAME Name of custom multiplier #2
WINDOWS_CML3_NAME Name of custom multiplier #3
WINDOWS_CML_LIST_FX
WINDOWS_CML2_LIST_FX
WINDOWS_CML3_LIST_FX
WINDOWS_CML_DATA Source of data for custom multiplier window #1, e.g. MULT1
WINDOWS_CML2_DATA Source of data for custom multiplier window #2, e.g. MULT1
WINDOWS_CML3_DATA Source of data for custom multiplier window #3, e.g. MULT1
WINDOWS_CML_SHOW_GROUP
WINDOWS_CML2_SHOW_GROUP
WINDOWS_CML3_SHOW_GROUP
WINDOWS_CML_RESIZABLE Controls if custom multiplier window #1 is resizable Default value: No
WINDOWS_CML2_RESIZABLE Controls if custom multiplier window #2 is resizable Default value: No
WINDOWS_CML3_RESIZABLE Controls if custom multiplier window #3 is resizable Default value: No
WINDOWS_CML_LABELS_IN_ROW
WINDOWS_CML2_LABELS_IN_ROW
WINDOWS_CML3_LABELS_IN_ROW
WINDOWS_CML_ALL_LABELS_IN_ROW
WINDOWS_CML2_ALL_LABELS_IN_ROW
WINDOWS_CML3_ALL_LABELS_IN_ROW
WINDOWS_CML_HIDDEN_CONT Hides custom multiplier #1 window for stations from selected continent
WINDOWS_CML2_HIDDEN_CONT Hides custom multiplier #2 window for stations from selected continent
WINDOWS_CML3_HIDDEN_CONT Hides custom multiplier #3 window for stations from selected continent
WINDOWS_CML_HIDDEN_DXCC Hides custom multiplier #1 window for stations from selected DXCC
WINDOWS_CML2_HIDDEN_DXCC Hides custom multiplier #1 window for stations from selected DXCC
WINDOWS_CML3_HIDDEN_DXCC Hides custom multiplier #1 window for stations from selected DXCC
WINDOWS_WKD_DXCC_ENABLED Enables worked DXCC window
WINDOWS_WKD_DXCC_HIDDEN_CONT Hides worked DXCC window for stations from selected continent
WINDOWS_WKD_DXCC_HIDDEN_DXCC Hides worked DXCC window for stations from selected DXCC
WINDOWS_WKD_DXCC_SHOW_ONLY_CONT
WINDOWS_WKD_DXCC_CONT_FILTER
WINDOWS_WKD_DXCC_HIDE_DXCC
WINDOWS_WKD_GRID_ENABLED Enables worked grids window
WINDOWS_WKD_PFX_ENABLED Enables worked prefixes window
WINDOWS_WKD_PFX_HIDDEN_CONT Hides worked prefixes window for stations from selected continent
WINDOWS_WKD_PFX_HIDDEN_DXCC Hides worked prefixes window for stations from selected DXCC
WINDOWS_WKD_PFX_DATA Source of worked prefixes data
WINDOWS_ON4KST_ENABLED Enables ON4KST messaging window Default value: No
CABRILLO_EXPORT_TYPE
LIVESCORE_CONTEST_NAME Contest name used for live score reporting
LIVESCORE_OPERATOR
LIVESCORE_POWER
LIVESCORE_TRANSMITTER
LIVESCORE_ASSISTED
LIVESCORE_MODE
LIVESCORE_MULT
QTC_ENABLED Enables QTC mechanics Default value: No
QTC_SEND_ENABLED Enables QTC sending
QTC_RECV_ENABLED Enables QTC receiving
QTC_SEND_RGX
QTC_RECV_RGX