DXLog.net - User contributions [en]

Menu Windows

2016-08-20T10:22:14Z

Dl6rai: /* Contest Recorder */

==Worked Zones==
Shortcut: <code>ALT+Z</code> 

[[image:zones.png]]

Worked zones window.
The title of this menu item will fit to the chosen contest. The window displays the worked multipliers (in blue) or not (in white) on the current band, and possibly the current mode.

[[image:zones_ab.png]]

Also ff the contest is multi-bands and/or multi-modes, you can display the distribution of these multipliers by band (and/or mode).
To change to by band, right mouse click on the zones window for the context menu and select all bands.

[[image:zones_rc.png]]

Right mouse click on the zones window for the context menu.

Zones window can be copied as an image to save for later use or paste into an email from the context menu.

==Worked DXCC==

Shortcut: <code>ALT+M</code> 

[[image:dxcc.png]]

If one DXCC country has been worked on a band (possibly a mode), this band will be displayed in blue, otherwise it remains in white.
This window is resizable.

Continents are selected from the radio buttons at the top of the screen.

All the data included in this window can be copied as a text file, and pasted in text or directly in an OpenOffice spreadsheet, for a later analysis from the right mouse click context menu.

[[image:dxcc_rc.png]]

==Worked gridsquares==
Shortcut: <code>ALT+L</code> 

Note: this selection will only be available if the current contest uses Gridsquares as multipliers.

[[image:Gridsquare_map.png]]

Right click on the map and select Properties to open the settings form:

[[image: Gridsquare_map_properties.png]]

This form allows customization for your particular area and contest.

==Check callsign==

Shortcut: <code>F9</code> 

[[image:band_check.png]]

This window displays a checkmark if and on which bands a specific callsign has been logged before. Depending on the type of the contest, the display may show more than one column to display the different possible modes.

==Check multipliers==

Shortcut: <code>F10</code> 

[[image:check_mult.png]]

When a callsign or country prefix is entered in main logging window this window will indicate whether this multiplier has been worked or not on the current (highlighted by a blue line) or other bands (and in other modes if the contest rules permit). If the callsign entered has been worked on other bands, DXlog.net displays those QSOs. Otherwise, the callsign of the first station worked in that multiplier on that band is displayed, if any.

Additional information about the multiplier is displayed at the bottom: 
The official country prefix and country name. 
The short (Az) and long path (Lp) beam headings (azimuths) to this multiplier (based on the station locator entered in the Contest configuration screen) 
The sunrise (SR) and sunset (SS) time in this country, expressed as UTC (suffixed by a lowercase "z"). These times are computed from the geographical coordinates given taken from the CTY* file or your QTH locator, if specified in the setup dialog.

==Check partials==

Shortcut: <code>F12</code> 

[[image:check_part.png]]

Check partial callsign search window, When at least 3 characters are entered in the log call entry field, DXlog.net Check Partial looks in the master database for the callsigns including the 3-character string.

In the above example M0C was entered into the log call entry field and the Check Partial database search found all the callsigns with the 3 characters in that order and displayed those.

A callsign can be moved to the log call entry field by double clicking on the callsign in the Check Partial window.

White callsigns are those not yet in the log, green callsigns are stations worked on another band, but not the current band and red callsigns are dupes.

[[image:check_part_rc1.png]]

Right mouse click on the window shows the context menu.

Search can be activated after 2 characters entered into the log call entry field by ticking the option in the context menu.

Search can be limited to the current log data only by ticking the "in log only" option in the context menu.

Show data from prefil database option will pull the relevant data from the prefil database and display next to the callsign in (), this is useful for VHF / UHF contests and locator squares

[[image:Check_part_pfd.png‎]]

==Check N+1==

Shortcut: <code>F8</code> 

[[image:n+1.png]]

N+1 window, when at least 3 characters are entered in the log call entry field, DXlog.net looks in the master database for callsigns differing from the partial callsign by one character.

N+1 also detects a 2-character swap (dyslexia), as well as one missing character.

A callsign can be moved to the log call entry field by double clicking on the callsign in the Check Partial window.

White callsigns are those not yet in the log, green callsigns are stations worked on another band, but not the current band and red callsigns are dupes.

[[image:n+1_rc.png]]

Right mouse click on the window shows the context menu.

Search can be limited to the current log data only by ticking the "in log only" option in the context menu.

==Summary==

Shortcut: <code>ALT+S</code> 

[[image:summary.png]]

The summary window displays the number of QSO (which does not include the dupes), along with multipliers relevant to the contest type for each band in the blue section, with the dark blue strip showing the current band being operated.

Grey section at the bottom shows totals for the contest and final raw score.

[[image:summary_rc.png]]

The right mouse click context menu allows you to copy the scoring summary data in the clipboard as an image or as a text file.

==Rate==

Shortcut: <code>ALT+R</code> 

[[image:rate.png]]

Rate data information window displays live qso rate data relating to the current contest.

Top section shows QSO's in last hour, last 10 rate, last 100 rate, rate since last time hour passed and if selected in the context menu, a projected score.

Second section shows time on and time off in hours and minutes.

Third section shows differential between run and s&p mode.

Fourth section shows time since last mult, mult and qso points worth.

Fifth section shows operating mode and if in CW the CW send speed

[[image:rate_rc.png]]

Right click context menu allows you to set Target QSO's / Hr, global QSO rate and add a calculated projected final score.

[[image:rate_ru.png]]

Right click context menu and Rate units allows you to set the rate unit display type.

==Operating info==

[[image:operating_info.png]]

Operating info window displays the radio active mode, if in SO2R it will display Radio 1: and Radio 2:

The CW repeat timer interval and the CW speed set in DXlog.net.

==Statistics==
Shortcut: <code>CTRL+F9</code> 

==Gab==
Shortcut: <code>ALT+I</code> 

[[image:gab.png]]

Gab window displays all the chat between networked stations.
In the context menu, the option "Save history to file" allows all the gab chat to be recorded in the .gab file of the current contest.
A double-click in a station name in this window will open the chat dialog, with this station name as default destination.

To send a message use Shortcut: <code>ALT+G</code> and the chat entry window will appear.

[[image:chat.png]]

Type a message and select either the individual station you wish to message or all to message all networked computers then click ok

Gab window context menu - right mouse click on gab window.

[[image:gab_rc.png]]

==Status window==

Shottcut: <code>ALT+J</code> 

[[image:status.png]] 
The status window indicates the status of each station connected to the network. From left to right, are displayed :
Station name, Current band and mode, Station type, QSY frequency of the current band and mode, Radio 1 frequency, Radio 2 frequency, Time left before a possible QSY, according to the 10 minutes M/S rule, or "OK" if the station is allowed to make a QSY on another band (only appears if the contest specifies this particular rule).
Your own station is displayed in a deep blue background.
The active radio of each station has its frequency in red characters.
A double left click on a station name will display the chat dialog with this station name as default destination.
A double left click on any frequency displayed will tune the current radio to that frequency. 
Open the context menu by right mouse clicking in the window. 
[[image:status_rc.png]] 
The Station name may be changed in '''Options -> Configure Network''' even if networking is disabled.

==QSY Wizard==
The QSY Wizard can only be used if HamCAP is installed and running. You must also have Options | HamCAP | Tab set to Charts.

After entering a callsign into the log callsign entry field, pressing Ctrl-P will bring up the HamCAP window with a propagation prediction to this station. Then, the QSY Wizard will display the bands on which to which a QSY or sked may be useful

[[image:qsy_wiz.png]] [[image:qsy_wiz_hamcap.png]]

In the above example ZS6TX has been worked on 20m. After pressing Ctrl-P the wizard tells us that a QSY may be promising on 15m. For 10, 40, 60, 160m however, the wizard recommends a sked time instead. This is the peak time predicted by HamCap for this path, hovering the mouse curser over the yellow square on the Hamcap chart will give more information including the MUF and signal elevation etc.

==Extra Information==

[[image:extra_info_window.png]]

The Extra Information window displays information contained in a text file based on the call entered in the log callsign entry field. Files should be named with the .xdt file extension. 
The format of the Extra information file is:
#TITLE Name of info
K6MR Ken 1270 CA (typical data line)
The text on the #TITLE line will be shown on the header line. If the #TITLE line is omitted, the complete path and filename will be shown. Data lines (one per call) begin with the call sign and a single space. Any information present after the first space will be shown exactly as formatted in the file. 
Multiple files may be opened at the same time to show data from different sources. 
* '''To add a file''' - Right mouse click in the extra information window and select "Extra data files". Click 'Add' and select the file from the file selection form. 
* '''To remove a file''' - Right mouse click in the extra information window and select "Extra data files", select the file to be removed, and click 'Remove'. 
If a file is updated while open in the window, right click and select "Reload files" to use the new data.

==Partner==

[[image:partner.png]]

This feature is especially useful in a Multi-OP environment when facing large pile-ups and/or weak signals.

Set up a second operator as support with a second computer which has DXlog.net installed and a pair of headphones connected to the receiver, on both comptuers open up the Partner window.

The running operator continues as before,working the callsign he hears. The support operator listens at the same time and tries to copy additional callsigns from the pile-up by entering the callsign on the QSO entry field and then pressing Alt-Enter.

This callsign will now be displayed in the Partner Window stack for the running operator to use as his next contact

The Partner window can hold up to 9 callsigns, and theses calls can be pulled into the callsign field with Alt-(1-9).
Once the QSO is logged, that callsign will disappear from both partner windows.

The Partner can remove a callsign if incorrect or no longer valid using Alt-(1-9).

A field in the partner window can be overwritten by a new entry by pressing Ctrl-(1-9). 

* '''Partner window use in RTTY''' 
The Partner window is also useful when used in a RTTY environment. 
In addition to using the Ctrl-(1-9) and Alt-(1-9) keys as previously noted, calls may be entered into the stack by selecting a call in the rtty receive window using the mouse pointer. Two callsign selection methods are available: 

Alt-LeftClick (left mouse click while holding down the Alt key) 
MiddleClick (a scroll wheel click on most mice)

Subsequent selections in the rtty receive window will populate the next empty line in the Partner window.

To place calls from the Partner window stack into the active QSO line, the ''$GRABPARTNER'' variable is used in a macro message to grab the first call from the Partner window stack. Typically this can be used in a special TU message to confirm the current qso, enter the next call, and send the report: 
$13 $CORRECT TU $GRABPARTNER NOW $LOGGEDCALL $F2 $CR
 

==Radio/Ant status window==

[[image:radio_ant_status.png]]

Radio/Ant status info window

If you are using a MK2R/MK2R+/u2R, OTRSP device or LPT port to control your antenna selection, this window will show the status of that interface.

The antenna names, select codes, and band selection must be set up using the appropriate configuration page:

MK2R/MK2R+/u2R: Options->MK2R/MK2R+/u2R configuration.
OTRSP: Options->OTRSP device configuration.
LPT: Options->Configure interfaces->Printer port Setup.

If you wish to select a different antenna between RX and TX this must be enabled using:

Options->Interface specific options->Allow different RX/TX antenna

Note: Separate RX/TX antenna selection is not available when using the LPT port.

Only antennas defined for the band that is active on each radio will be shown. The selected antenna on each radio will be highlighted. When changing bands, the antenna defined first (for that band) on the interface will be selected.

There are two methods of selecting an antenna:

1. Alt-F11 (RX Ant) and Alt-F12 (TX Ant). If the separate RX/TX antennas option is not enabled, either key combination will select both the RX and TX antenna.

2. Select the antenna by clicking on the required antenna in the Radio/Ant status window using the mouse.

Note: the separate RX/TX antenna selection will only work when DXLog.net is controlling RX/TX switching, such as when it is sending messages. To enable RX/TX antenna switching when keying manually you must provide a PTT signal to enable RX/TX antenna switching.

==World Map==

[[image:map.png]]

World map showing Daylight, Greyling and Night.

World map context menu is available by right mouse clicking on the map window.
Grey line display options can be adjusted from this menu.

[[image:map_rc.png]]

Map size can be increased by using the zoom in option in the right click menu.

==Radio 1==

[[image:Radio1.png]]

Radio information displaying VFO A and VFO B frequency information.

Single click on VFOA or VFOB to change focus to this VFO.

Band map tab shows radio band in focus and any DX Cluster received or locally entered callsigns plus other optional information.

List tab shows a list of call signs which can be sorted in various ways.

Colours are:- RED = Double Mult, GREEN = Mult, Black = Unworked, GREY = Worked

Information below the horizontal divider is available mult numbers, available QSO's and points available.

Double clicking on a callsign sets the focus radio VFO to that frequency (and in split mode if information available from split DX Cluster spot) and puts the callsign into the log callsign field. This can be changed to a single click by selecting the enable single click selection from the context menu.

[[image:Radio1_rc_so.png]]

In list mode the data can be sorted in a number of ways from the context menu and sort

[[image:Radio1_rc_do.png]]

Display options for both Band Map and List mode are set from the context menu and display options

[[image:Radio1_rc_pr.png]]

Various properties can be set by a right mouse click in the bandmap and selecting Properties.

Bandplan Settings for Bandplan spots to be displayed are set from the Properties form. Select Setup in the Bandplan section of the Properties form to display the current Bandplan settings. The current band will be displayed by default. Be sure to save your changes to the appropriate Bandplan memory (Default or Bandplan 1 - Bandplan 9).

To edit a different Bandplan than the one currently active, select the Bandplan button under Load. If a Bandplan has no settings, the Load Bandplan n button will be greyed out. To use a new Bandplan memory, save the current settings to a new memory. Then edit as necessary and save the new bandplan using the appropriate Save As button.

If you wish to activate a new or different Bandplan for the current log, check the box in the lower left corner of the form.

Note: If the spot mode is included in the spot comment, the spot will be displayed using the mode shown in the comment. Otherwise the mode will be determined by the active Bandplan.

[[image:Radio1_rc_pr_bp.png]]

Context menu is available by right mouse clicking on the radio window

==Radio 2==

Radio 2 is as per Radio 1 but for SO2R mode when 2 radios are connected to the one instance of DXlog.net

==Digital Decoder Windows==

There are four digital decoder windows (two for each radio), each enabled by selecting separately from the Windows menu. 
The four selections are located just below the Radio1/Radio2 band map menu picks, and the exact wording is dependent on the RTTY Configuration. IMPORTANT: Radio 2 windows will only be active if '''SO2V''', '''SO2R''' or '''Advanced SO2R''' are enabled in '''Operating > Technique'''. 
[[image:data_radio_menu.png]] 
Before using the decoder windows, they must be configured using the RTTY Configuration form: '''Options-> RTTY Configuration''' 
[[image:RTTY_Config.png]] 
After configuration, each decoder window menu selection will show which decoder has been configured, for each selection (Primary/Secondary) and radio (Radio 1/Radio 2). Note that the Primary decoder is the decoder used for the transmit interface, usually MMTTY. 
Selecting the appropriate menu pick will open the decoder window. The Primary decoder window will display a set of clickable buttons at the bottom that duplicates all message function keys. The Altx buttons provide access to the messages defined in the Alt-C (Other Messages) form. In addition, there is an Alt-K button (open keyboard mode window) and a (C) button (clear decoder window). 
[[image:RTTY_R1.png]] [[image:RTTY_R1R.png]] 
When the decoder windows are opened the first time, it will be necessary to configure each one for input and output parameters such as sound card, FSK port, etc. These settings will be saved by the decoder program and only need to be configured the first time. 
Note: MMTTY will only save the FSK port settings if you close the MMTTY windows before closing DXLog.net. If you let DXLog.net close the MMTTY windows the FSK port will reset to NONE and will need to be selected at the next use. 
[[image:MMTTY.png]] 
Example of MMTTY engine window.

==DX-Cluster monitor==

Shortcut: <code>ALT+O</code> 

[[image:dx_cluster_monitor.png]]

Floating window displaying live information from the connected DXCluster as received.

Right mouse click on the window for context menu.

[[image:dx_cluster_monitor_rc.png]]

Stream logging - if checked, will save last 500 lines of DXCluster monitor window to temp file. File will be read on a restart to restore data.

Show network stream - if more than one networked PC is in use, and you run a connection to DXClusters on more than one of the PC's in the network, checking this option will show data from all DXCluster connections in the DXCluster monitor window, but with different color.

==DX-Cluster announcements==

Shortcut: <code>ALT+A</code> 

[[image:Dx_cluster_announcement.png‎]]

Floating window showing received DX Cluster spots with total valid spots for Mult QSO's, Standard QSO's and Total QSO's per band at the top of the window

Double left click the mouse on a spot to tune connected radio to this frequency and auto enter the callsign into the log callsign entry field.

Spots displayed can be set manually per band or any number of bands or automatically from the connected radio band data, or display just multipliers, user can set by right clicking the displayed bands window and selecting from the context menu that appears.

[[image:dx_cluster_announcment_1.png]]

Information displayed in the window can be filtered using the context menu and selecting display options.

[[image:dx_cluster_announcment_2.png]]

Incorrect spot callsigns can be modified by right clicking the callsign and selecting modify from the menu.

[[image:spot_mod.png]]

Spots can be deleted by right clicking the callsign and selecting Delete.

Context menu is available by right mouse clicking on the dx cluster announcements window.

==Clock==

[[image:clock.png‎]]

Time information bar, including Sunrise and Sunset times and the active station callsign. 
When the time is coming up to the hour the clock will turn dark red, when the time is on the hour the clock will be red (If default colours are used). 
When the SR and SS times are close the SR and SS times will turn dark red, When SR and SS times are reached the times will turn red (If the default colours are used). 
Left mouse click and drag to move. 
Right mouse click on bar for context menu. 
Fonts and colours can be set from this menu. 
[[image:clock_rc.png‎]] 
When '''Tools > Data entry > Enable run / SP switching''' is enabled the Clock bar will show the mode of operation, in Run mode the clock background is grey but in S&P mode the Clock bar background is yellow (If default colours are used). 
''Clock bar in run mode.'' 
[[image:clock1.png]] 
''Clock bar in S&P mode.'' 
[[image:clock2.png]]

==Contest Recorder==

[[image:Contest_recorder.jpg]] 
The contest recorder allows you to record both main and sub VFO audio for the whole contest in MP3 format onto your PC hard disc. 
If you want to record using DXLog, you have to download libmp3lame.dll win32 version from '''[http://www.rarewares.org/mp3-lame-libraries.php]'''. 
[[image:win32dll.jpg]] 
Note that the 64 Bit DLL version '''definitely does not work''' on Windows 7 64 Bit systems.

Extract the dowloaded archive file into DXLog.net installation folder. 
For 32 bit Processors this is usually ..\Program Files\DXLog.net 
For 64 bit processors this is usually ..\Program Files(x86)\DXLog.net 
Before recording, see Options->MP3 config to set parameters which fits to your PC sound card setup. 
Encoding rate is currently fixed to 32000 kHz, stereo, 96kbps which is more than adequate for good recordings with a reasonable file size. 
Recording levels are set in the Windows Recording Devices of your PC, strongest signals should peak top yellow on the Contest Recorder bar graph display for best results. 
To playback, select the qso in Dxlog you wish to hear, either by searching for the QSO number or manually using the up down arrows, then right click on the contest recorder and select PLAY QSO. For more playback options use the contest recorder right click context menu:- 
[[image:Contest_recorder_rc.png‎]] 
[1] - Link to libmp3lame.dll download

==SSB Bargraph==

[[image:SSB_Bargraph.png‎]]

Bargraph showing output of recorded files for Function Keys.

Drag to move

Right mouse click on bargraph for context menu.

[[image:SSB_Bargraph_rc.png‎]]

Contest definition

2016-07-08T09:31:26Z

Dl6rai:

==Description==

Rules for most contests are different and are usually written by the group adjudicating the contest. 
The differences can be points per QSO, multiplier determination and calculations etc. 

To support all these different rules and to allow for easier adding / changing contest rules in DXLog.net,
all parameters for complying with the specific contest rules are defined and controlled through the specific contest config file. 
Contest config files are plain text files which are located in the '''Contest''' sub-folder of the DXLog.net installation folder. 

When DXlog.net is started, the contents of Contest folder are copied into the ApplicationData folder in your Windows OS. 
During the copying process, DXLog.net compares modified date of each file in the installation folder with the version in the ApplicationData folder. 
If a newer version exists in the ApplicationData folder, the original file would not be copied over from the contest folder. 

The end user can modify an existing file or may create a new file in the ApplicationData folder, so changes can be made to the contest definition file for testing, or the end user can create a new contest definition file to support a new or previously unsupported contest. 

==File structure==

Each line in a contest definition file usually contains '''KEY + VALUE''' pairs. 
The pair is always separated by the "=" sign. For example:
CONTEST_NAME=9A CW
This means the field KEY is '''CONTEST_NAME''', and '''9A CW''' is the field value.

==Regex expressions==

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: <tt>CFG_MULT_RGX_CHECK</tt>. 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 regex denotes start of the string value 
: "$" in regex denotes end of string value 
: "|" in regex is 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 <tt>POINTS_FIELD_BAND_MODE</tt>. 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 (correspondent) 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 own continent
SOURCE->DXCC - our own DXCC
SOURCE->CALL - our own CALLSIGN
SOURCE->PFX - our own prefix
SOURCE->WPX - our own prefix
DEST->CONT - correspondent continent
DEST->DXCC - correspondent DXCC
DEST->CALL - correspondent CALLSIGN
DEST->RCVD - value entered in the received 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 exchange field entered in the contest configuration screen
CONFIG->CQZONE - value from the WAZ field entered in the contest configuration screen
CONFIG->ITUZONE - value from the ITU field entered in the contest configuration screen
CONFIG->OPNAME - value from the OPNAME field entered in the contest configuration screen
CONFIG->POWER - value from the POWERfield entered in the contest configuration screen

More details about point calculation and the POINTS_FIELD_BAND_MODE key can be found in a later section of this document. 

==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'''
Link to contest rules. 
'''CONTESTWEB'''
Link to contest web.

==Configuration screen control==

'''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, EG 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. 
EG: 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'''
Contains list of available bands separated by ";" for specific contest. 
Default value: 160;80;40;20;15;10

'''MODES'''
Contains list of available modes separated by ";" for specific contest. 
Default value: CW;SSB

'''EDI_BANDS'''
Contains 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. 
Acceptable values: YES/NO
Default value: NO 

'''FIELD_CALLSIGN_WWL_CHECK'''
If YES, entry in the log callsign field will be checked for a gridsquare entry.
If a gridsquare is found, then the callsign field value will be copied to the gridsquare entry field and the Azimuth angle will be
calculated and shown. 
Acceptable values: YES/NO
Default value: NO 

'''FIELD_MODE_VISIBLE'''
Mode field visable on the qso entry line. 
Acceptable values: YES/NO 
Default value: NO 

'''FIELD_MODE_NAME'''
Header name for field mode. 

'''FIELD_MULT_VISIBLE'''
MULT field visable on the screen. 
Acceptable values: YES/NO 

'''FIELD_NR_VISIBLE'''
SENT QSO SERIAL NUMBER visible on the qso entry line. 
Acceptable values: YES/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.
Usable 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'''
Regex expression. If the condition is valid, SENT QSO SERIAL NUMBER will be hidden.
Usable 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. 
Acceptable values: YES/NO 

'''FIELD_PERIOD_NAME'''
Header name for field NAME. 

'''FIELD_PTS_VISIBLE'''
Is field POINTS visible in qso entry line. 
Acceptable values: YES/NO 

'''FIELD_PTS_NAME'''
Header name for field POINTS.

'''FIELD_RCVD_CHECK_FORMAT_FX'''
C# expression to reformat RCVD field value before any further checking. 

'''FIELD_RCVD_COPY'''
Is field RCVD automatically copied from previous qso with same station. 
Acceptable values: YES/NO 

'''FIELD_RCVD_COPY_EXC_DXCC'''
List of DXCC countries separated by ";" which are exception for copy value. 
Usable in case when we want to copy value from previous QSO for some station. 

'''FIELD_RCVD_COPY_EXC_RGX'''
Regex 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'''
If RCVD field is empty, this is default value to be filled in cabrillo output. 

'''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 save. 

'''FIELD_RCVD_FX_CHECK'''
C# expression used to check is value entered in RCVD field is valid. 

'''FIELD_RCVD_MANDATORY'''
Is RCVD field entry is mandatory. 
Acceptable values: YES/NO 

'''FIELD_RCVD_MANDATORY_RGX_EXC'''
Regex 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_NUMERIC'''
Controls if RCVD field accepts only numeric characters. 
Acceptable values: YES/NO 

'''FIELD_RCVD_RGX_CHECK'''
Regex 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. 
Acceptable values: YES/NO
Default value: NO 

'''FIELD_RECINFO_CHECK_FORMAT_FX'''
'''FIELD_RECINFO_COPY'''
'''FIELD_RECINFO_COPY_RGX_EXC'''
'''FIELD_RECINFO_FORMAT_FX'''
'''FIELD_RECINFO_FX_CHECK'''
'''FIELD_RECINFO_MANDATORY'''
'''FIELD_RECINFO_MANDATORY_RGX_EXC'''
'''FIELD_RECINFO_MAX_LENGTH'''
'''FIELD_RECINFO_MIN_LENGTH'''
'''FIELD_RECINFO_NAME'''
'''FIELD_RECINFO_NUMERIC'''
'''FIELD_RECINFO_RGX_CHECK'''
'''FIELD_RECINFO_RGX_SEL_POS'''
'''FIELD_RECINFO_TYPE'''
'''FIELD_RECINFO_VISIBLE'''
'''FIELD_RECINFO2_CHECK_FORMAT_FX'''
'''FIELD_RECINFO2_COPY'''
'''FIELD_RECINFO2_COPY_RGX_EXC'''
'''FIELD_RECINFO2_FORMAT_FX'''
'''FIELD_RECINFO2_FX_CHECK'''
'''FIELD_RECINFO2_MANDATORY'''
'''FIELD_RECINFO2_MANDATORY_RGX_EXC'''
'''FIELD_RECINFO2_MAX_LENGTH'''
'''FIELD_RECINFO2_MIN_LENGTH'''
'''FIELD_RECINFO2_NAME'''
'''FIELD_RECINFO2_NUMERIC'''
'''FIELD_RECINFO2_RGX_CHECK'''
'''FIELD_RECINFO2_RGX_SEL_POS'''
'''FIELD_RECINFO2_TYPE'''
'''FIELD_RECINFO2_VISIBLE'''
'''FIELD_RECINFO3_CHECK_FORMAT_FX'''
'''FIELD_RECINFO3_COPY'''
'''FIELD_RECINFO3_COPY_RGX_EXC'''
'''FIELD_RECINFO3_FORMAT_FX'''
'''FIELD_RECINFO3_FX_CHECK'''
'''FIELD_RECINFO3_MANDATORY'''
'''FIELD_RECINFO3_MANDATORY_RGX_EXC'''
'''FIELD_RECINFO3_MAX_LENGTH'''
'''FIELD_RECINFO3_MIN_LENGTH'''
'''FIELD_RECINFO3_NAME'''
'''FIELD_RECINFO3_NUMERIC'''
'''FIELD_RECINFO3_RGX_CHECK'''
'''FIELD_RECINFO3_RGX_SEL_POS'''
'''FIELD_RECINFO3_TYPE'''
'''FIELD_RECINFO3_VISIBLE'''
'''FIELD_RST_3RD_LETTER'''
'''FIELD_SENT_VISIBLE'''
'''FIELD_STN_VISIBLE'''

Contest definition

2016-07-08T09:19:46Z

Dl6rai: /* Regex expressions */

==Description==

Rules for most contests are different and are usually written by the group adjudicating the contest. 
The differences can be points per QSO, multiplier determination and calculations etc. 

To support all these different rules and to allow for easier adding / changing contest rules in DXLog.net,
all parameters for complying with the specific contest rules are defined and controlled through the specific contest config file. 
Contest config files are plain text files which are located in the '''Contest''' sub-folder of the DXLog.net installation folder. 

When DXlog.net is started, the contents of Contest folder are copied into the ApplicationData folder in your Windows OS. 
During the copying process, DXLog.net compares modified date of each file in the installation folder with the version in the ApplicationData folder. 
If a newer version exists in the ApplicationData folder, the original file would not be copied over from the contest folder. 

The end user can modify an existing file or may create a new file in the ApplicationData folder, so changes can be made to the contest definition file for testing, or the end user can create a new contest definition file to support a new or previously unsupported contest. 

==File structure==

Each line in a contest definition file usually contains '''KEY + VALUE''' pairs. 
The pair is always separated by the "=" sign. 
For example: 
CONTEST_NAME=9A CW 
This means the field KEY is '''CONTEST_NAME''', and '''9A CW''' is the field value.

==Regex expressions==

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: <tt>CFG_MULT_RGX_CHECK</tt>. 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 regex denotes start of the string value 
: "$" in regex denotes end of string value 
: "|" in regex is 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 (correspondent) 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.
m
* Keys Reference:
SOURCE->CONT - our own continent
SOURCE->DXCC - our own DXCC
SOURCE->CALL - our own CALLSIGN
SOURCE->PFX - our own prefix
SOURCE->WPX - our own prefix
DEST->CONT - correspondent continent
DEST->DXCC - correspondent DXCC
DEST->CALL - correspondent CALLSIGN
DEST->RCVD - value entered in the received 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 exchange field entered in the contest configuration screen
CONFIG->CQZONE - value from the WAZ field entered in the contest configuration screen
CONFIG->ITUZONE - value from the ITU field entered in the contest configuration screen
CONFIG->OPNAME - value from the OPNAME field entered in the contest configuration screen
CONFIG->POWER - value from the POWERfield entered in the contest configuration screen

More details about point calculation and the POINTS_FIELD_BAND_MODE key can be found in a later section of this document. 

==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'''
Link to contest rules. 
'''CONTESTWEB'''
Link to contest web.

==Configuration screen control==

'''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, EG 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. 
EG: 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'''
Contains list of available bands separated by ";" for specific contest. 
Default value: 160;80;40;20;15;10

'''MODES'''
Contains list of available modes separated by ";" for specific contest. 
Default value: CW;SSB

'''EDI_BANDS'''
Contains 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. 
Acceptable values: YES/NO
Default value: NO 

'''FIELD_CALLSIGN_WWL_CHECK'''
If YES, entry in the log callsign field will be checked for a gridsquare entry.
If a gridsquare is found, then the callsign field value will be copied to the gridsquare entry field and the Azimuth angle will be
calculated and shown. 
Acceptable values: YES/NO
Default value: NO 

'''FIELD_MODE_VISIBLE'''
Mode field visable on the qso entry line. 
Acceptable values: YES/NO 
Default value: NO 

'''FIELD_MODE_NAME'''
Header name for field mode. 

'''FIELD_MULT_VISIBLE'''
MULT field visable on the screen. 
Acceptable values: YES/NO 

'''FIELD_NR_VISIBLE'''
SENT QSO SERIAL NUMBER visible on the qso entry line. 
Acceptable values: YES/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.
Usable 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'''
Regex expression. If the condition is valid, SENT QSO SERIAL NUMBER will be hidden.
Usable 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. 
Acceptable values: YES/NO 

'''FIELD_PERIOD_NAME'''
Header name for field NAME. 

'''FIELD_PTS_VISIBLE'''
Is field POINTS visible in qso entry line. 
Acceptable values: YES/NO 

'''FIELD_PTS_NAME'''
Header name for field POINTS.

'''FIELD_RCVD_CHECK_FORMAT_FX'''
C# expression to reformat RCVD field value before any further checking. 

'''FIELD_RCVD_COPY'''
Is field RCVD automatically copied from previous qso with same station. 
Acceptable values: YES/NO 

'''FIELD_RCVD_COPY_EXC_DXCC'''
List of DXCC countries separated by ";" which are exception for copy value. 
Usable in case when we want to copy value from previous QSO for some station. 

'''FIELD_RCVD_COPY_EXC_RGX'''
Regex 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'''
If RCVD field is empty, this is default value to be filled in cabrillo output. 

'''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 save. 

'''FIELD_RCVD_FX_CHECK'''
C# expression used to check is value entered in RCVD field is valid. 

'''FIELD_RCVD_MANDATORY'''
Is RCVD field entry is mandatory. 
Acceptable values: YES/NO 

'''FIELD_RCVD_MANDATORY_RGX_EXC'''
Regex 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_NUMERIC'''
Controls if RCVD field accepts only numeric characters. 
Acceptable values: YES/NO 

'''FIELD_RCVD_RGX_CHECK'''
Regex 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. 
Acceptable values: YES/NO
Default value: NO 

'''FIELD_RECINFO_CHECK_FORMAT_FX'''
'''FIELD_RECINFO_COPY'''
'''FIELD_RECINFO_COPY_RGX_EXC'''
'''FIELD_RECINFO_FORMAT_FX'''
'''FIELD_RECINFO_FX_CHECK'''
'''FIELD_RECINFO_MANDATORY'''
'''FIELD_RECINFO_MANDATORY_RGX_EXC'''
'''FIELD_RECINFO_MAX_LENGTH'''
'''FIELD_RECINFO_MIN_LENGTH'''
'''FIELD_RECINFO_NAME'''
'''FIELD_RECINFO_NUMERIC'''
'''FIELD_RECINFO_RGX_CHECK'''
'''FIELD_RECINFO_RGX_SEL_POS'''
'''FIELD_RECINFO_TYPE'''
'''FIELD_RECINFO_VISIBLE'''
'''FIELD_RECINFO2_CHECK_FORMAT_FX'''
'''FIELD_RECINFO2_COPY'''
'''FIELD_RECINFO2_COPY_RGX_EXC'''
'''FIELD_RECINFO2_FORMAT_FX'''
'''FIELD_RECINFO2_FX_CHECK'''
'''FIELD_RECINFO2_MANDATORY'''
'''FIELD_RECINFO2_MANDATORY_RGX_EXC'''
'''FIELD_RECINFO2_MAX_LENGTH'''
'''FIELD_RECINFO2_MIN_LENGTH'''
'''FIELD_RECINFO2_NAME'''
'''FIELD_RECINFO2_NUMERIC'''
'''FIELD_RECINFO2_RGX_CHECK'''
'''FIELD_RECINFO2_RGX_SEL_POS'''
'''FIELD_RECINFO2_TYPE'''
'''FIELD_RECINFO2_VISIBLE'''
'''FIELD_RECINFO3_CHECK_FORMAT_FX'''
'''FIELD_RECINFO3_COPY'''
'''FIELD_RECINFO3_COPY_RGX_EXC'''
'''FIELD_RECINFO3_FORMAT_FX'''
'''FIELD_RECINFO3_FX_CHECK'''
'''FIELD_RECINFO3_MANDATORY'''
'''FIELD_RECINFO3_MANDATORY_RGX_EXC'''
'''FIELD_RECINFO3_MAX_LENGTH'''
'''FIELD_RECINFO3_MIN_LENGTH'''
'''FIELD_RECINFO3_NAME'''
'''FIELD_RECINFO3_NUMERIC'''
'''FIELD_RECINFO3_RGX_CHECK'''
'''FIELD_RECINFO3_RGX_SEL_POS'''
'''FIELD_RECINFO3_TYPE'''
'''FIELD_RECINFO3_VISIBLE'''
'''FIELD_RST_3RD_LETTER'''
'''FIELD_SENT_VISIBLE'''
'''FIELD_STN_VISIBLE'''

Contest definition

2016-07-08T09:08:44Z

Dl6rai: /* Description */

==Description==

Rules for most contests are different and are usually written by the group adjudicating the contest. 
The differences can be points per QSO, multiplier determination and calculations etc. 

To support all these different rules and to allow for easier adding / changing contest rules in DXLog.net,
all parameters for complying with the specific contest rules are defined and controlled through the specific contest config file. 
Contest config files are plain text files which are located in the '''Contest''' sub-folder of the DXLog.net installation folder. 

When DXlog.net is started, the contents of Contest folder are copied into the ApplicationData folder in your Windows OS. 
During the copying process, DXLog.net compares modified date of each file in the installation folder with the version in the ApplicationData folder. 
If a newer version exists in the ApplicationData folder, the original file would not be copied over from the contest folder. 

The end user can modify an existing file or may create a new file in the ApplicationData folder, so changes can be made to the contest definition file for testing, or the end user can create a new contest definition file to support a new or previously unsupported contest. 

==File structure==

Each line in a contest definition file usually contains '''KEY + VALUE''' pairs. 
The pair is always separated by the "=" sign. 
For example: 
CONTEST_NAME=9A CW 
This means the field KEY is '''CONTEST_NAME''', and '''9A CW''' is the field value.

==Regex expressions==

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 regex denotes start of the string value
"$" in regex denotes end of string value
"|" in regex is 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 (correspondent) 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 own continent
SOURCE->DXCC - our own DXCC
SOURCE->CALL - our own CALLSIGN
SOURCE->PFX - our own prefix
SOURCE->WPX - our own prefix
DEST->CONT - correspondent continent
DEST->DXCC - correspondent DXCC
DEST->CALL - correspondent CALLSIGN
DEST->RCVD - value entered in the received 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 exchange field entered in the contest configuration screen
CONFIG->CQZONE - value from the WAZ field entered in the contest configuration screen
CONFIG->ITUZONE - value from the ITU field entered in the contest configuration screen
CONFIG->OPNAME - value from the OPNAME field entered in the contest configuration screen
CONFIG->POWER - value from the POWERfield entered in the contest configuration screen

More details about point calculation and the POINTS_FIELD_BAND_MODE key can be found in a later section of this document. 

==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'''
Link to contest rules. 
'''CONTESTWEB'''
Link to contest web.

==Configuration screen control==

'''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, EG 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. 
EG: 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'''
Contains list of available bands separated by ";" for specific contest. 
Default value: 160;80;40;20;15;10

'''MODES'''
Contains list of available modes separated by ";" for specific contest. 
Default value: CW;SSB

'''EDI_BANDS'''
Contains 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. 
Acceptable values: YES/NO
Default value: NO 

'''FIELD_CALLSIGN_WWL_CHECK'''
If YES, entry in the log callsign field will be checked for a gridsquare entry.
If a gridsquare is found, then the callsign field value will be copied to the gridsquare entry field and the Azimuth angle will be
calculated and shown. 
Acceptable values: YES/NO
Default value: NO 

'''FIELD_MODE_VISIBLE'''
Mode field visable on the qso entry line. 
Acceptable values: YES/NO 
Default value: NO 

'''FIELD_MODE_NAME'''
Header name for field mode. 

'''FIELD_MULT_VISIBLE'''
MULT field visable on the screen. 
Acceptable values: YES/NO 

'''FIELD_NR_VISIBLE'''
SENT QSO SERIAL NUMBER visible on the qso entry line. 
Acceptable values: YES/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.
Usable 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'''
Regex expression. If the condition is valid, SENT QSO SERIAL NUMBER will be hidden.
Usable 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. 
Acceptable values: YES/NO 

'''FIELD_PERIOD_NAME'''
Header name for field NAME. 

'''FIELD_PTS_VISIBLE'''
Is field POINTS visible in qso entry line. 
Acceptable values: YES/NO 

'''FIELD_PTS_NAME'''
Header name for field POINTS.

'''FIELD_RCVD_CHECK_FORMAT_FX'''
C# expression to reformat RCVD field value before any further checking. 

'''FIELD_RCVD_COPY'''
Is field RCVD automatically copied from previous qso with same station. 
Acceptable values: YES/NO 

'''FIELD_RCVD_COPY_EXC_DXCC'''
List of DXCC countries separated by ";" which are exception for copy value. 
Usable in case when we want to copy value from previous QSO for some station. 

'''FIELD_RCVD_COPY_EXC_RGX'''
Regex 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'''
If RCVD field is empty, this is default value to be filled in cabrillo output. 

'''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 save. 

'''FIELD_RCVD_FX_CHECK'''
C# expression used to check is value entered in RCVD field is valid. 

'''FIELD_RCVD_MANDATORY'''
Is RCVD field entry is mandatory. 
Acceptable values: YES/NO 

'''FIELD_RCVD_MANDATORY_RGX_EXC'''
Regex 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_NUMERIC'''
Controls if RCVD field accepts only numeric characters. 
Acceptable values: YES/NO 

'''FIELD_RCVD_RGX_CHECK'''
Regex 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. 
Acceptable values: YES/NO
Default value: NO 

'''FIELD_RECINFO_CHECK_FORMAT_FX'''
'''FIELD_RECINFO_COPY'''
'''FIELD_RECINFO_COPY_RGX_EXC'''
'''FIELD_RECINFO_FORMAT_FX'''
'''FIELD_RECINFO_FX_CHECK'''
'''FIELD_RECINFO_MANDATORY'''
'''FIELD_RECINFO_MANDATORY_RGX_EXC'''
'''FIELD_RECINFO_MAX_LENGTH'''
'''FIELD_RECINFO_MIN_LENGTH'''
'''FIELD_RECINFO_NAME'''
'''FIELD_RECINFO_NUMERIC'''
'''FIELD_RECINFO_RGX_CHECK'''
'''FIELD_RECINFO_RGX_SEL_POS'''
'''FIELD_RECINFO_TYPE'''
'''FIELD_RECINFO_VISIBLE'''
'''FIELD_RECINFO2_CHECK_FORMAT_FX'''
'''FIELD_RECINFO2_COPY'''
'''FIELD_RECINFO2_COPY_RGX_EXC'''
'''FIELD_RECINFO2_FORMAT_FX'''
'''FIELD_RECINFO2_FX_CHECK'''
'''FIELD_RECINFO2_MANDATORY'''
'''FIELD_RECINFO2_MANDATORY_RGX_EXC'''
'''FIELD_RECINFO2_MAX_LENGTH'''
'''FIELD_RECINFO2_MIN_LENGTH'''
'''FIELD_RECINFO2_NAME'''
'''FIELD_RECINFO2_NUMERIC'''
'''FIELD_RECINFO2_RGX_CHECK'''
'''FIELD_RECINFO2_RGX_SEL_POS'''
'''FIELD_RECINFO2_TYPE'''
'''FIELD_RECINFO2_VISIBLE'''
'''FIELD_RECINFO3_CHECK_FORMAT_FX'''
'''FIELD_RECINFO3_COPY'''
'''FIELD_RECINFO3_COPY_RGX_EXC'''
'''FIELD_RECINFO3_FORMAT_FX'''
'''FIELD_RECINFO3_FX_CHECK'''
'''FIELD_RECINFO3_MANDATORY'''
'''FIELD_RECINFO3_MANDATORY_RGX_EXC'''
'''FIELD_RECINFO3_MAX_LENGTH'''
'''FIELD_RECINFO3_MIN_LENGTH'''
'''FIELD_RECINFO3_NAME'''
'''FIELD_RECINFO3_NUMERIC'''
'''FIELD_RECINFO3_RGX_CHECK'''
'''FIELD_RECINFO3_RGX_SEL_POS'''
'''FIELD_RECINFO3_TYPE'''
'''FIELD_RECINFO3_VISIBLE'''
'''FIELD_RST_3RD_LETTER'''
'''FIELD_SENT_VISIBLE'''
'''FIELD_STN_VISIBLE'''

Contest configuration

2016-07-08T09:04:56Z

Dl6rai: /* Message macros */

<big><big>Configuration</big></big>

==Contest configuration==
[[image:DXL ContestConfig.png]]
 
* <code>Callsign</code> - The Callsign which will be used during the contest
* <code>Grid square</code> - your Maidenhead gridsquare (6 letters) which will be used for VHF/UHF/SHF contests for QRB calculations
* <code>Exchange</code> - contest specific exchange field
* <code>DXCC prefix</code> - your DXCC standard prefix
* <code>WAZ zone</code> - your CQ zone number
* <code>ITU zone</code> - your ITU zone number
* <code>State/Province/Other</code> - your US state, Canadian province or DX
* <code>Name</code> - The name which will be inserted in the final Cabrillo file
* <code>Address</code> - The address which will be inserted in the final Cabrillo file
* <code>Club</code> - The name of your club for club competitions 
After pressing enter (or mouse click on OK button) all fields are checked against contest rules defined in contest config file. 
If any fields contain incorrect data, DXLog.net will supply a warning with instructions on how to correct the data, It may also show possible links to the contest rules (if link is defined in contest config file).

==Message macros==

The following commands when entered into a message macro enables automated functions as listed 

$ALTERNATECQ: (or $ACQ) swaps primary and secondary radios and sends CQ on the secondary radio 
$CHECK: send license year (ARRL SS only) 
$CHECKCALL: - move focus to callsign and press spacebar 
$CORRECT: send a call correction, if any 
$CQ: same as $ALTERNATECQ but does not swap radios 
$CR: works like hitting [Enter] (log QSO) 
$CTRLPLUS: - same as $LOGQSO 
$CURRENT (or $CURRENTCALL): Sends the callsign of the current QSO despite the presence of a $CR later in the message. 
The $CR (carriage return) is always executed on message keypress. It is also useful in ESM (Enter Sends Message) mode in lieu of $LOGGEDCALL.
$FOCUS1: change Focused radio to Radio 1 
$FOCUS2: change Focused radio to Radio 2 
$FOCUSCALL: move entry focus to Callsign field 
$FOCUSRCVD: move entry focus to Rcvd field 
$FOCUSREC1: move entry focus to RecInfo field 
$FOCUSREC2: move entry focus to RecInfo2 field 
$FOCUSREC3: move entry focus to RecInfo3 field 
$FREQnn: Where nn is a band (e.g. $FREQ160, $FREQ80 etc.). Useful in a multi-op as a canned message "PSE QSY $FREQ15". 
Sends the frequency of the primary radio of the first networked station found on this band with the following priority: R, R+, M, and M+.
$FREQP: contains the frequency of the primary radio (useful for passing mults) 
$FREQS: contains frequency of the secondary radio (useful for passing mults) 
$F1...$F7: send the message associated with F1 ... F7 function key 
$GRABPARTNER: grabs the first callsign from the Partner window and inserts it in the callsign field. 
$GRABSPOT: grabs spot on the current frequency 
$GRNR: sends gr/num of the received QTC 
$GUESSZONE: fill in exchange field(s) if possible, but cursor remains in the same edit field 
$GUESSEXCH: (or $GUESSEXCHANGE) mimics a space bar hit, filling the exchange field(s) if possible, but the cursor remains in the same edit field. 
$INSERT: sends message in the [Ins] key 
$ISLAND: sends IOTA Reference (i.e. EU001, AF001, ...) (IOTA Contest) 
$LATCH: sets latch mode 
$LOGGED: (or $LOGGEDCALL): sends what is typed in the callsign field of the current QSO, or if blank, the previous QSO 
$LOGQSO: silently saves QSO (useful in ESM + S&P mode) 
$MK2R=cmd: send a specific MK2R command to the microHAM MK2R SO2R box. 
$MSG1...$MSG12: send additional CW messages (see Alt + C) 
$MYCALL: sends callsign set in contest configuration 
$MYNAME: sends operator name, set in contest configuration 
$NEXT: (or $NEXTCALL): sends the callsign of the next QSO line when a $CR is included in the message. 
$NEXTSERIAL: sends next QSO serial number (current QSO serial number plus 1) 
$PLUS: send messages in the [+] key 
$PREV: (or $PREVCALL): sends the callsign on the previous QSO line. 
$PREVSERIAL: sends previous QSO serial number (current QSO serial number minus 1) 
$QQSLC: sends Quick QSL message based QSOs made (see Intelligent Quick QSL)· 
$QQSLT: sends Quick QSL message based on time passed (see Intelligent Quick QSL)· 
$QQSLRESET: reset the timer or the counter like if the long QSL message were just sent.· 
$QSOB4: sends the QSOB4 message and cancels the remainder of the current message, if the current QSO is a dupe, otherwise sends nothing 
$REPEAT: restarts the automatic repeating CQ sequence (if enabled), after pausing for the specified interval. 
Most useful at the end of the [Plus] key message to avoid having to press [F1] to start CQing again. 
$RESET: cancels any manual change made in the audio control 
$RST: sends report from RST Sent field (normally 5NN) 
$RSTEXCHSENT: Resets the "exchangeSent" flag of the active QSO (useful only for ESM scripts) 
$R1R1, $R1R2, $R2R1, $R2R2: which can be entered in the predefined CW messages to set the headphone 
$SERIAL: sends current QSO Serial Number, or previous serial number if the line with the cursor is blank. 
$SETEXCHSENT: Sets the "exchangeSent" flag of the active QSO (useful only for ESM scripts) 
$SPACEBAR: same as $SPACE (press spacebar in currently active field, move to next field) 
$STATE: sends State/Province set in contest configuration (Exchange) 
$SWAPFOCUS: - change Focused radio to opposite Radio 
$TAB: works like hitting [Tab] (move cursor to next field) 
$TR1 and $TR2: primary radio or secondary radio tx 
$YEAR: sends year nr set in contest configuration (i.e. EUHFC, AA) 
$ZONE sends zone nr set in contest configuration 
$13: RTTY send carriage return character (start print on a new line)· 

&xy: sends a Morse prosign where xy represents the two characters forming the prosign, e.g. &AS, &AR, &BK, &BT, &CL, &KN, &SK, etc. 

+: increase speed by 4 wpm 
-: decrease speed by 4 wpm 
^: the halfspace character with 1/2 dot duration 
~: (tilde) at the end of a variable means "no space" will be inserted, e.g. $NEXT~? sends the next callsign followed by a question mark, with no space in between 
 
WAEDC QTC related 

$CALLSIGN: send callsign of the current QTC· 
$DONE: if all QTC are sent: mimic the [+] key· 
$FIELD: this variable takes the value "GROUP", "TIME", "CL" or "NR", depending on the kind of QTC field where the cursor is located 
$GRNR: sends group & number of the received QTC· 
$NEXT: move focus to the next QTC line· 
$QTC: sends group & number of the transmitted QTC· 
$QTCROW: Row number of cursor location in the QTC window. Very useful to create a function key sending the message PSE RPT QTC NR $QTCROW $QTCROW in WAEDC RTTY to request repetition of a specific QTC. 
$SERIAL: send serial number of the current QTC· 
$SERIE: send the complete QTC block (specific to RTTY)· 
$TIME: send time of the current QTC· 
$VALID: save everything and close the window· 
 
Setup for NOW message on RTTY 
$13 $CORRECT TU $CR $GRABPARTNER NOW $LOGGEDCALL (EXCH)

Installation

2016-07-08T08:55:30Z

Dl6rai: /* Register your copy */

==Download the software==
DXLog.net is available for download at http://www.dxlog.net/sw. 
 

==Prerequisites==

DXLog.net is written with the latest Microsoft technologies, using Microsoft Visual Studio 2010 C# and being compiled for Microsoft.NET Framework 4.0. 
It should run on any Windows version which can accept Microsoft.NET Framework version 4.0. 
Before installation of DXLog.net, you need to check that you have Microsoft.NET Framework 4.0 installed on your PC system. 
If you are not sure, you can start DXLog.net installation and the installer will warn you if .NET Framework 4.0 (or above) is not installed on your PC system. 
 
Microsoft.NET Framework 4.0 is available for free from the Microsoft website. 
Direct download link http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=17718. 
 
If you plan to use the Pc systems LPT port for CW keying and other functions, because of Windows limitations you need to download and install DLLPORTIO.dll driver. 
You can download it from DXLog.net downloads section. The file is called port95nt.exe http://www.dxlog.net/sw/tools/port95nt.exe. 
 
As of version 2.1.1 DXLog.net is using SQLite database for data storage. 
On some WinOS Microsoft Visual C++ 2010 RTM Redistributable Package (x86 version) needs to be installed. 
If this package isn't found during installation, DXlog.net installer will warn you that it's not installed on your system. 
You can download and install this package from: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=5555 

==Install the software==

Software is installed by default into your PC systems Windows Program Files folder. 
For 32 bit Processor machines this is usually <tt>C:\Program Files\DXLog.net</tt>. 
For 64 bit processor machines this is usually <tt>C:\Program Files(x86)\DXLog.net</tt>. 
 
Application configuration files as well contest and database definitions are copied into a special windows folder called '''Application Data'''
during the first run of DXLog.net. 

==Unregistered limitations==

All versions of DXLog.net can be used to evaluate software functionality with some limits. 
 
Unregistered version can be used without any limits for '''DXPeditions'''. 
 
For all contests, DXLog.net will have following limits: 
- DXLog.net will restart itself every 10-20 minutes. 
- Logging is limited to 100 QSOs 
- Log file cannot be exported to different formats (ADIF, EDI, Cabrillo etc.) 
 

==Register your copy==

To register your copy of DXLog.net and unlock full version functionality goto http://www.dxlog.net 
From then main menu, click on the "Buy/Register" link (at the top of the screen) and you will be redirected to Avangate secure purchasing web site. 
Avangate is our secure provider which will securely process your transaction. 
After entering all the required detail and making a successful payment, you will receive a registration key by email @ the address provided in the purchasing process. 
In DXLog.net, go to '''Help->Register''' menu and fill in the registration details: 
- username or registered user as per the registration email. 
- callsign of registered user as per the registration email. 
- license key of registered user as per the registration email. 

Be careful when entering this data, if it is not exactly the same as the data you've used in registration process, the registration process will fail. 
 
Your license key is valid for one year from the day of purchase. 
During that period, you can upgrade existing installations with newer versions as they become available. 
 
After the one year period has expired, the existing version of DXLog.net will continue to work with full functionality but further software updates would require a new licence key. 
 
You can use same license key on all your computers. 
The registered callsign does not have to be the same as the callsign you're using in the contest log.