Difference between revisions of "Contest definition"
(→Additional Configuration Entries) |
(→Special Configuration Entries) |
||
Line 803: | Line 803: | ||
The file format is the same as the normal CTY.DAT file. | The file format is the same as the normal CTY.DAT file. | ||
− | + | Normal text | |
==Additional Configuration Entries== | ==Additional Configuration Entries== |
Revision as of 08:39, 8 March 2020
Contents
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.
SOURCE->CONT | Own continent |
SOURCE->DXCC | Own DXCC |
SOURCE->CALL | Own callsign |
SOURCE->PFX | Own prefix |
SOURCE->WPX | Own 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
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. |
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
CATEGORIES | Semicolon-separated list of contest categories shown in the category selection dropdown menu in the contest configuration panel. | 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. | 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_MULT | Controls the use of the exchange field in contest configuration panel. Valid values are: YES and NO. If NO, the exchange field is greyed out. |
Default value: NO |
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_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=CUSTOM_MULT_LIST | Alternative to using a regular expression to check validity of entry in Exhange field. | 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 | Default value: NO |
CFG_GRID_RGX_CHECK | Regular expression used to test validity of data entered in the GRIDSQUARE field. | Default value: ALL |
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
CABRILLO_ASSISTED Semicolon-separated list of mapping of categories to Cabrillo assistance types MUST have the same number of entries as the defined categories. Allowed values are ASSISTED and NON-ASSISTED.
CABRILLO_BAND Semicolon-separated list of frequency definition for contests with band-limited categories. MUST have the same number of entries as the contest's category if defined. Defaults to all.
CABRILLO_CONTEST_NAME Formal contest name for Cabrillo export.
CABRILLO_DEF_RECINFO Value to use for RECINFO field at Cabrillo export if empty.
CABRILLO_DEF_RECINFO2 Value to use for RECINFO2 field at Cabrillo export if empty.
CABRILLO_DEF_RECINFO3 Value to use for RECINFO3 field at Cabrillo export if empty.
CABRILLO_DXPEDITION Semicolon-separated list of mapping of categories to Cabrillo CATEGORY-DXPEDITION types MUST have the same number of entries as the defined categories. Allowed values are NON-DXPEDITION and EXPEDITION. By default, this category is not included in Cabrillo export.
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 Regular expression that checks the entered location for validity when prompted. Default value: Empty
CABRILLO_LOCATION_DEFAULT Default value of location for Cabrillo export when prompted.
CABRILLO_LOCATION_PROMPT 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 category modes to Cabrillo modes in QSO lines. MUST have the same number of entries as the defined number of modes for the contest. Allowed entries are CW, PH, DG, RY, and FM
CABRILLO_OPERATOR Semicolon-separated list of mapping of categories to to Cabrillo operator count. MUST have the same number of entries as the defined categories. Allowed entries are SINGLE-OP, MULTI-OP, and CHECKLOG.
CABRILLO_OVERLAY Semicolon-separated list of mapping of category overlays to Cabrillo overlays. MUST have the same number of entries as the defined overlays. Allowed entries are CLASSIC, ROOKIE, TB-WIRES, NOVICE-TECH, and OVER-50.
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. Allowed entries are HIGH, LOW, and QRP.
CABRILLO_QTC_LINE Definition of Cabrillo output for QTC. C.f. CABRILLO_LINE
CABRILLO_TIME Semicolon-separated list of duration for each contest category. MUST have the same number of entries as there are contest categories.
CABRILLO_TRANSMITTER Semicolon-separated list of mapping of categories to Cabrillo operator counts. MUST have the same number of entries as contest categories. Allowed entries are ONE, TWO, LIMITED, UNLIMITED, and SWL.
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
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. Valid values are YES and NO. |
Default value: NO |
FIELD_MODE_VISIBLE | Mode field visible on the QSO entry line. Valid values are YES and NO. | Default value: NO |
FIELD_MODE_NAME | Header for mode field. | |
FIELD_MULT_VISIBLE | MULT field visible on the screen. Valid values are YES and 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. Valid values are YES and 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. Valid values: YES and NO. | Default value: NO |
FIELD_PERIOD_NAME | Header for PERIOD field. | |
FIELD_PTS_VISIBLE | Is field POINTS visible in QSO entry line. Valid values: YES and 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. Valid values: YES and NO. | Default value: 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 determine copied value from earlier QSO. | |
FIELD_RCVD_DEFAULT_VALUE | Value to be used in export if RCVD field is empty. | |
FIELD_RCVD_EXC_CHECK_DXCC | List of DXCC countries separated by ":" which are exception for value checking procedure followed by a definition of the multipliers after ";". | |
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. Valid values are YES and 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. Valid values are YES and NO. | Default value: NO |
FIELD_RCVD_SLASH_ALLOWED | Controls if RCVD field accepts a slash "/" character. Valid values are YES and NO. | Default value: NO |
FIELD_RCVD_RGX_CHECK | Regular expression. Used to check if entry in RCVD field is valid. | |
FIELD_RCVD_TYPE | Defines type of the RCVD field. Valid values are: GRID, GRID4, NR, CUSTOM, MULT, CQZONE, ITUZONE, and NAME | 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_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. Valid values are YES and 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. Valid values are YES and 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. Valid values are YES and 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 | Defines type of the RECINFO field. Valid values are: GRID, GRID4, NR, CUSTOM, MULT, CQZONE, ITUZONE, and NAME | Default value: Empty |
FIELD_RECINFO_VISIBLE | Controls if the RECINFO field is visible. Valid values: YES, HIDDEN, and 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. Valid values are YES and 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. Valid values are YES and 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. Valid values are YES and 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 | Defines type of the RECINFO2 field. Valid values are: GRID, GRID4, NR, CUSTOM, MULT, CQZONE, ITUZONE, and NAME | Default value: Empty |
FIELD_RECINFO2_VISIBLE | Controls if the RECINFO2 field is visible. Valid values: YES, HIDDEN, and 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. Valid values are: YES and 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. Valid values are YES and 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. Valid values are YES and 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 | Defines type of the RECINFO field. Valid values are: GRID, GRID4, NR, CUSTOM, MULT, CQZONE, ITUZONE, and NAME | Default value: Empty |
FIELD_RECINFO3_VISIBLE | Controls wether the RECINFO3 field is visible. Valid values: YES, HIDDEN, and READONLY. | Default value: HIDDEN |
FIELD_RST_3RD_LETTER | ||
FIELD_RST_VISIBLE | Controls visibility of RST field. Valid values are: YES and NO. | Default value: YES |
FIELD_SENT_VISIBLE | ||
FIELD_STN_VISIBLE |
Default Messages
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.
Normal text
Additional Configuration Entries
z
BAND_BONUS | Semicolon-separated list of band bonuses, aligned with band list. | |
MODE_GROUP | Semicolon-separated list of modes. Function unclear. | |
DISPLAY_MODE_GROUPING | Formatting of display of modes in summary window. Syntax: DISPLAY_MODE_GROUPING=modename1:mode1+mode2;modename2:mode3+mode4 |
|
MIN_OFF_TIME | Minimum time without QSO to count as off time. In minutes. | Default value: 30 |
DXCC_DB_USE_ARRL_LIST | Allows to use ARRL country list instead of CQ country list. | Default value: NO |
CONTEST_LENGTH | Duration of contest in minutes. | |
CONTEST_FIRST_HOUR | Time of day for start of contest in UTC. Format HH:MM | |
PERIOD | Whether the contest has periods. | Default value: OFF |
PERIOD_LENGTH | The length of each contest period. | |
PERIOD_AUTOSWITCH | ||
PERIOD_NUMBER | ||
CALC_FROM_TIME | ||
PERIOD_MODES | ||
SPRINT_LOGIC_ALLOWED | Allow sprint logic. | Default value: NO |
INITIAL_SERIAL_NUMBER | Starting value of sent serial number. | Default value: 1 |
WARNING_FILE | Name of frequency range warning file located in %appdata%\DXLog.net\Database. |
|
ADIF_KEYS | Allows for exporting custom keys in ADIF. The syntax is ADIF_KEYS=ADIFKEY;Expression;Regexp. Regexp 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;. 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, Mult, Mult1, Mult2, Mult3, Lp, 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 |
DB_FILE or DB_FILE1 | File name of prefill data base #1. | |
DB_FILE2 | File name of prefill data base #2. | |
DB_FILE3 | File name of prefill data base #3. | |
DB_FILE4 | File name of prefill data base #4. | |
DB_FILE5 | File name of prefill data base #5. | |
DB_FILE_TYPE or DB_FILE1_TYPE | Extension of data base file #1. | Default value: .TXT |
DB_FILE2_TYPE | Extension of data base file #2. | Default value: .TXT |
DB_FILE3_TYPE | Extension of data base file #3. | Default value: .TXT |
DB_FILE4_TYPE | Extension of data base file #4.. | Default value: .TXT |
DB_FILE5_TYPE | Extension of data base file #5. | Default value: .TXT |
DB_FILE_COL_RCVD or DB_FILE1_COL_RCVD | Column number of RCVD field in data base file #1. NB! At least one DB_FILE_COL* statement must be included for each data base file. |
|
DB_FILE2_COL_RCVD | Column number of RCVD field in data base file #2. NB! At least one DB_FILE_COL* statement must be included for each data base file. |
|
DB_FILE3_COL_RCVD | Column number of RCVD field in data base file #3. NB! At least one DB_FILE_COL* statement must be included for each data base file. |
|
DB_FILE4_COL_RCVD | Column number of RCVD field in data base file #4. NB! At least one DB_FILE_COL* statement must be included for each data base file. |
|
DB_FILE5_COL_RCVD | Column number of RCVD field in data base file #5. NB! At least one DB_FILE_COL* statement must be included for each data base file. |
|
DB_FILE_COL_RECINFO or DB_FILE1_COL_RECINFO | Column number of RECINFO field in data base file #1. | |
DB_FILE2_COL_RECINFO | Column number of RECINFO field in data base file #2. | |
DB_FILE3_COL_RECINFO | Column number of RECINFO field in data base file #3. | |
DB_FILE4_COL_RECINFO | Column number of RECINFO field in data base file #4. | |
DB_FILE5_COL_RECINFO | Column number of RECINFO field in data base file #5. | |
DB_FILE_COL_RECINFO2 or DB_FILE1_COL_RECINFO2 | Column number of RECINFO2 field in data base file #1. | |
DB_FILE2_COL_RECINFO2 | Column number of RECINFO2 field in data base file #2. | |
DB_FILE3_COL_RECINFO2 | Column number of RECINFO2 field in data base file #3. | |
DB_FILE4_COL_RECINFO2 | Column number of RECINFO2 field in data base file #4. | |
DB_FILE5_COL_RECINFO2 | Column number of RECINFO2 field in data base file #5. | |
DB_FILE_COL_RECINFO3 or DB_FILE1_COL_RECINFO3 | Column number of RECINFO3 field in data base file #1. | |
DB_FILE2_COL_RECINFO3 | Column number of RECINFO3 field in data base file #2. | |
DB_FILE3_COL_RECINFO3 | Column number of RECINFO3 field in data base file #3. | |
DB_FILE4_COL_RECINFO3 | Column number of RECINFO3 field in data base file #4. | |
DB_FILE5_COL_RECINFO3 | Column number of RECINFO3 field in data base file #5. | |
DB_FILE_FILL_FORMAT or DB_FILE1_FILL_FORMAT | C# expression defining how prefill from data base file #1 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. |
|
DB_FILE2_FILL_FORMAT | C# expression defining how prefill from data base file #2 will be used. | |
DB_FILE3_FILL_FORMAT | C# expression defining how prefill from data base file #3 will be used. | |
DB_FILE4_FILL_FORMAT | C# expression defining how prefill from data base file #4 will be used. | |
DB_FILE5_FILL_FORMAT | C# expression defining how prefill from data base file #5 will be used. | |
RGX_GUESS_DB | Regex "rule base" for guessing exchange of unworked stations. Syntax is RGX_GUESS_DB=Field;Regexp1;Regexp2;Filename |
|
QSO_NUMBER | QSO numbering principle. Valid values are: ALL, PER_MODE, PER_BAND, PER_PERIOD, PER_BAND_MODE, PER_PERIOD_MODE. |
|
QSO_NUMBER_CATEGORY | Semicolon-separated list of numbering principles for each contest category. Must contain the same number of elements as contest categories. |
|
DOUBLE_QSO | The definition of a dupe. Allowed values are: PER_BAND, PER_BAND_MODE, PER_PERIOD, PER_MINUTE_DIFFERENCE, PER_PERIOD_BAND, PER_PERIOD_MODE, PER_PERIOD_BAND_MODE, PER_BAND_DAY |
Required. No default value. |
MULT_SUM | Summing method for multipliers. Valid values are: NO, ALL, PER_BAND, and PER_PERIOD. |
Default value: ALL |
DOUBLE_QSO_MINUTE_DIFFERENCE | Minimum time difference 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 are: PER_MODE, PER_CABRILLO_MODE, and PER_MODE_GROUP. |
|
POINTS_TYPE | Type of points. Valid values are CALC, QRB, QRB_EXCHANGE+CALCF, RAEM, FROM_TABLE(filename;INT;EXCHANGE;field) | |
SCP_DATABASE_DISABLE | Disable check partials database. (for WRTC). | Default value: NO |
POINTS_BAND_BONUS | Per band scaling factor, often used for VUSHF contests. Syntax POINTS_BAND_BONUS=band;scaling. Example: POINTS_BAND_BONUS=144;2 doubles the points number on the 2m band. |
|
DXC_COMMENT_EXTRACT | Regular expression used to extract mult information from DX cluster spots for highlighting in band map and prefill. Syntax is DXC_COMMENT_EXTRACT=field;regexp. Example: DXC_COMMENT_EXTRACT=RECINFO;(AF|AN||AS|EU|NA|OC|SA)[ /\-\.]?\d{1,3};[ /\-\.] extracts IOTA keys into a RECINFO prefill for the call. |
|
OWN_MULT_VALID | Controls if own multiplier is valid. | 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 |
CFG_GRID_MANDATORY | Grid locator is mandatory in the contest configuration. | Default value: NO |
CFG_GRID_ERRORTEXT | Text to display when an invalid grid is entered. | |
CFG_GRID_RGX_CHECK | Regular expression to check for a valid value of configuration grid locator. | |
RATE_ODX_VISIBLE | Show distance statistics in Rate window. | Default value: NO |
CONTINENT_LIST | Custom, semicolon-separated continent list. Syntax is: CONTINENT_LIST=continent1;continent2;continent3 | Default value: EU;NA;SA;AS;AF;OC |
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.) |
|
MULT1_TYPE | Type of MULT1. Can be DXCC, CQZONE, WPX, CUSTOM, or FX. | Default value: None |
MULT1_FX | A C# expression used to create the actual value of MULT1 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. |
|
MULT2_TYPE | Type of MULT2. Can be DXCC, CQZONE, WPX, CUSTOM, or FX. | Default value: None |
MULT2_FX | As MULT1_FX but for MULT2. | |
MULT3_TYPE | Type of MULT3. Can be DXCC, CQZONE, WPX,CUSTOM, or FX. | Default value: None |
MULT3_FX | As MULT1_FX but for MULT3. | |
MULT1_COUNT | Counting method for MULT1. Can be PER_BAND, PER_PERIOD, PER_MODE, PER_BAND_MODE, PER_PERIOD_MODE, or ALL. | Default value: None |
MULT2_COUNT | Counting method for MULT2. Can be PER_BAND, PER_PERIOD, or ALL | Default value: None |
MULT3_COUNT | Counting method for MULT3. Can be PER_BAND, PER_PERIOD, or ALL | Default value: None |
MULT1_ADD_DXCC | Default value: NO | |
MULT2_ADD_DXCC | Default value: NO | |
MULT3_ADD_DXCC | Default value: NO | |
MULT1_FIELD | ||
MULT2_FIELD | ||
MULT3_FIELD | ||
MULT1_DISPLAY | ||
MULT2_DISPLAY | ||
MULT3_DISPLAY | ||
MULT1_SHOWERROR | Default value: YES | |
MULT2_SHOWERROR | Default value: YES | |
MULT3_SHOWERROR | Default value: YES | |
MULT1_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. |
|
MULT2_BAND_BONUS | As MULT1_BAND_BONUS but for MULT2. | |
MULT3_BAND_BONUS | As MULT1_BAND_BONUS but for MULT3. | |
MULT1_BONUS | General multiplier scaling factor. Syntax MULT1_BONUS=scaling. Example: MULT1_BONUS=4 gives two multiplier points for every multiplier. |
Default value: 1 |
MULT2_BONUS | As MULT1_BONUS but for MULT2. | Default value: 1 |
MULT3_BONUS | As MULT1_BONUS but for MULT3. | Default value: 1 |
MULT1_EXCEPTION | ^VE$;CUSTOM_MULT_LIST will only count multipliers from US and Canadian stations and the multiplier is determined from a custom list. |
|
MULT2_EXCEPTION | As MULT1_EXCEPTION but for MULT2. | |
MULT3_EXCEPTION | As MULT1_EXCEPTION but for MULT3. | |
MULT1_MULTIPLIER | Multiplication factor for a selected value of MULT1. 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. |
|
MULT2_MULTIPLIER | As MULT1_MULTIPLIER but for MULT2. | |
MULT3_MULTIPLIER | As MULT1_MULTIPLIER but for MULT3. | |
MULT1_REPEAT | Specifies a list of values of MULT1 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. |
|
MULT2_REPEAT | As above but for MULT2. | |
MULT3_REPEAT | As above but for MULT3. | |
MULT1_CONT_LIST | List used when MULT1 is of type CONT. | Default value: EU;NA;SA;AS;AF;OC |
MULT2_CONT_LIST | List used when MULT2 is of type CONT. | Default value: EU;NA;SA;AS;AF;OC |
MULT3_CONT_LIST | List used when MULT3 is of type CONT. | Default value: EU;NA;SA;AS;AF;OC |
FIRST_PREV_RCVD | Initial return value of macro $PREV_RCVD. | Default value: "000" |
FIRST_PREV_RECINFO | Initial return value of macro $PREV_RECINFO. | Default value: "000" |
FIRST_PREV_RECINFO2 | Initial return value of macro $PREV_RECINFO2. | Default value: "000" |
FIRST_PREV_RECINFO3 | Initial return value of macro $PREV_RECINFO3. | Default value: "000" |
STATS_TYPE | Type of statistics in Rate window. Valid values are: 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 last mode change in Rate window. | Default value: NO |
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_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 multioperator operation enabled. | Default value: YES |
MULTIOP_BANDCHANGES_ALLOWED | Number of band changes allowed in one hour in multioperator operation. | Default value: 8 |
MULTIOP_BANDCHANGES_CHECKMODE | Type of counting method for band changes in multioperator operation. PER_BAND or PER_BAND_MODE | Default value: PER_BAND |
MULTIOP_BANDCHANGES_TYPE | Type of bandchanges counted for band change rule in multioperator operation. R, RM, or ALL. (Run stn, Run+Mult stn, All stn) | Default value: R |
MULTIOP_BANDCHANGES_CBR_CATEGORIES | Default value: MULTI-OP | |
MULTIOP_BANDCHANGES_CBR_TRANSMITTERS | Default value: TWO | |
SLASH_MULTIPLE_QSOS | Default value: NO | |
SCORE | Scoring principle. Valid values are BY_BAND, BY_BAND_MODE, BY_PERIOD, BY_PERIOD_BAND, and BY_PERIOD_BAND_MODE | Default value: BY_BAND |
SCORE_DISPLAY | Default value: BAND;QSO;POINTS;MULT1 | |
SCORE_TOTAL | Principle for total score. Valid values are BY_BAND_GROUP, BY_MODE_GROUP | |
SCORE_TOTAL_FX | Formula for calculating total score for a QSO. Example: SCORE_TOTAL_FX=$FIELDVALUE.Points*($FIELDVALUE.Mult1+$FIELDVALUE.Mult3)*$FIELDVALUE.Mult2 |
|
SCORE_BAND_GROUP | List of bands for PER_BAND_GROUP scoring. Syntax: SCORE_BAND_GROUP=bandgroup1{band1,band2,band3};bandgroup2{band4,band5} |
|
SCORE_MODE_GROUP | List of modes for PER_MODE_GROUP scoring. Syntax: SCORE_MODE_GROUP=modegroup1{mode1,mode2};modegroup2{mode3,mode4} |
|
POINTS_FIELD_BAND_MODE | Conditional point calculation. Syntax: POINTS_FIELD_BAND_MODE=regexp1;regexp2;bandregexp;moderegexp;points |
|
POINTS_CALC_F | Formula for points calculation. Syntax: POINTS_CALC_F=sourceregexp;pointsformula;bandregexp;calculationregexp Example: POINTS_CALC_F=ALL;VALUE*5;^15$;QRB>=100 && QRB<=800 multiplies points with 5 on 15m if QRB is between 100 and 800km. |
|
DTB_SCP_FROM_RECINFO | Use RECINFO in DTB for reverse look-up. DOES NOT SEEM TO WORK. | |
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 | Default value: ALL | |
LIVESCORE_CONTEST_NAME | Contest name used for live score reporting instead of CABRILLO_CONTEST_NAME. | |
LIVESCORE_OPERATOR | Type of operation used for live score reporting instead of CABRILLO_OPERATOR. Must have the same number of values as contest categories. |
|
LIVESCORE_POWER | Output power used for live score reporting instead of CABRILLO_POWER.Must have the same number of entries as power categories. |
|
LIVESCORE_TRANSMITTER | Number of transmitters used for live score reporting instead of CABRILLO_TRANSMITTER. Must have the same number of entries as contest categories. |
|
LIVESCORE_ASSISTED | Assisted class used for live score reporting instead of CABRILLO_ASSISTED. Must have the same number of entries as contest categories. |
|
LIVESCORE_MODE | Mode used for live score reporting instead of CABRILLO_MODE. Must have the same number of entries as mode categories. |
|
LIVESCORE_MULT | ||
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 | Default value: DEST->CONT:^EU$ | |
QTC_RECV_RGX | Default value: !DEST->CONT:^EU$ |