DXLog.net - User contributions [en]

Installation

2014-10-09T11:35:16Z

9a5k: /* Register your copy */

==Download the software==
DXLog.net is available for download at http://www.dxlog.net/sw. 
 
This is fully functional version with all features included. 
 
DXLog.net software is currently available for usage free of charge. 

==Prerequisites==

DXLog.net is written in latest Microsoft technologies, using Microsoft Visual Studio 2010 C# and it is 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 do you have Microsoft.NET Framework 4.0 installed on your system. 
If you are not sure in this, you can start DXLog.net installation and installer will warn you if there isn't .NET Framework 4.0 (or above) installed on your system. 
 
Microsoft.NET Framework 4.0 is available for free download on Microsoft web. 
Direct download link is http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=17718. 
 
Also, if you plan to use LPT port for CW keying and other functions, because of Windows limitations you need DLLPORTIO.dll driver. 
You can download it from DXLog.net web. File is called port95nt.exe and it is available for download on http://www.dxlog.net/sw/tools. 
 
As of version 2.1.1 DXLog.net using SQLite database for data storage. 
On some WinOS Microsoft Visual C++ 2010 RTM Redistributable Package (x86 version) needs to be installed. 
In case that this package isn't found during installation, installer will warn you about this. 
You can download and install this package from here: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=5555 

==Install the software==

Software is installed by default in your Windows Program Files folder. 
Usually that is <tt>C:\Program Files\DXLog.net</tt>. 
For some newer Windows versions (Vista, Win7), folder where application will be installed by default is <tt>C:\Program Files(x86)\DXLog.net</tt>. 
 
Application configuration files as well contest and database definitions are copied into special windows folder called '''Application Data'''
during first run of DXLog.net, if version of file in "Program Files folder" is newer. 

==Unregistered copy 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 DXPedition modes. 
 
For other contests, DXLog.net will have following limits: 
- Application will be restarted each 10-20 minutes 
- Log file is limited to 100 QSOs 
- Log file can't be exported to different formats (ADIF, EDI, Cabrillo etc.) 
 

==Register your copy==

To register your copy of DXLog.net and to unlock full version functionality you have to go at http://www.dxlog.net website. 
From main menu, click on "Buy/Register" link (on the top of the screen) and you will be redirected to Avangate secure web site. 
Avangate is our secure provider which will securely process your transaction. 
After entering all details needed and after payment will be confirmed, you will receive registration key on your email. 
In DXLog.net, go to Help->Register menu and fill registration details: 
- username of registered user (usually first and last name), 
- callsign of registered user 
- license key (the key you've received by email during registration process) 

Be careful when entering this data because they have to be exactly same as the data you've used in registration process. 
 
Your license key is valid for one year from purchase day. 
During that period, you can upgrade existing installations with newer versions. 
 
After this one year period is expired, existing version of DXLog.net will continue to work with full functionality. 
It wouldn't be possible to upgrade to newer version with expired license key. 
 
You can use same license key on all your computers and registered callsign doesn't need to be the same as the callsign you're using in the contest.

Installation

2014-10-09T11:32:03Z

9a5k: /* Unregistered copy limitations */

Main Page

2014-10-09T11:31:37Z

9a5k:

__NOTOC__
{|width=100%
| style="vertical-align:top;" colspan=2|
{{Main Page header}}
|-
|width=70% |
<ol type="I">
<li>'''[[Preface]]'''
<ol>
<li>[[Preface#Authors and Contributors|Authors and Contributors]]
</ol>
<li> '''[[Installation|Installation]]'''
<ol>
<li>[[Installation#Download_the_software|Download the software]]
<li>[[Installation#Prerequisites|Prerequisites]]
<li>[[Installation#Install_the_software|Install the software]]
<li>[[Installation#Unregistered_copy_limitations|Unregistered copy limitations]]
<li>[[Installation#Register_your_copy|Register your copy]]
</ol>
<li> '''[[Features|Features]]'''
<ol>
<li>[[Features#Supported_contests|Supported contests]]
<li>[[Features#Contest_config_file|Contest config file]]
</ol>
<li> '''[[Configuration|Configuration]]'''
<ol>
<li>[[Configuration#Contest_configuration|Contest configuration]]
</ol>
<li> '''[[Contest_definition|Contest definition]]'''
<ol>
<li>[[Contest_definition#Description|Description]]
<li>[[Contest_definition#File_structure|File structure]]
<li>[[Contest_definition#Regex_expressions|Regex expressions]]
<li>[[Contest_definition#General_contest_description|General contest description]]
<li>[[Contest_definition#Cabrillo|Cabrillo]]
<li>[[Contest_definition#Band_and_mode_specific|Band and mode specific]]
<li>[[Contest_definition#Entry_field_definitions|Entry field definitions]]
</ol>
<li> '''[[Menus|Menus]]'''
<ol>
<li>[[Menu_File#File|File]]
<li>[[Menu_Edit#Edit|Edit]]
<li>[[Menu_Operating#Operating|Operating]]
<li>[[Menu_Commands#Commands|Commands]]
<li>[[Menu_Messages#Messages|Messages]]
<li>[[Menu_Tools#Tools|Tools]]
<li>[[Menu_Options#Options|Options]]
<li>[[Menu_Windows#Windows|Windows]]
<li>[[Menu_Help#Help|Help]]
</ol>
</ol>
|style="vertical-align:top;"|
|}

Installation

2014-10-09T11:31:00Z

9a5k:

==Download the software==
DXLog.net is available for download at http://www.dxlog.net/sw. 
 
This is fully functional version with all features included. 
 
DXLog.net software is currently available for usage free of charge. 

==Prerequisites==

DXLog.net is written in latest Microsoft technologies, using Microsoft Visual Studio 2010 C# and it is 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 do you have Microsoft.NET Framework 4.0 installed on your system. 
If you are not sure in this, you can start DXLog.net installation and installer will warn you if there isn't .NET Framework 4.0 (or above) installed on your system. 
 
Microsoft.NET Framework 4.0 is available for free download on Microsoft web. 
Direct download link is http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=17718. 
 
Also, if you plan to use LPT port for CW keying and other functions, because of Windows limitations you need DLLPORTIO.dll driver. 
You can download it from DXLog.net web. File is called port95nt.exe and it is available for download on http://www.dxlog.net/sw/tools. 
 
As of version 2.1.1 DXLog.net using SQLite database for data storage. 
On some WinOS Microsoft Visual C++ 2010 RTM Redistributable Package (x86 version) needs to be installed. 
In case that this package isn't found during installation, installer will warn you about this. 
You can download and install this package from here: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=5555 

==Install the software==

Software is installed by default in your Windows Program Files folder. 
Usually that is <tt>C:\Program Files\DXLog.net</tt>. 
For some newer Windows versions (Vista, Win7), folder where application will be installed by default is <tt>C:\Program Files(x86)\DXLog.net</tt>. 
 
Application configuration files as well contest and database definitions are copied into special windows folder called '''Application Data'''
during first run of DXLog.net, if version of file in "Program Files folder" is newer. 

==Unregistered copy limitations==

All versions of DXLog.net can be used to evaluate software functionality with some limits. 
 
Unregistered version can be used without any limit for DXPedition modes. 
 
For other contests, DXLog.net will have following limits: 
- Application will be restarted each 10-20 minutes 
- Log file is limited to 100 QSOs 
- Log file can't be exported to different formats (ADIF, EDI, Cabrillo etc.) 
 

==Register your copy==

To register your copy of DXLog.net and to unlock full version functionality you have to go at http://www.dxlog.net website. 
From main menu, click on "Buy/Register" link (on the top of the screen) and you will be redirected to Avangate secure web site. 
Avangate is our secure provider which will securely process your transaction. 
After entering all details needed and after payment will be confirmed, you will receive registration key on your email. 
In DXLog.net, go to Help->Register menu and fill registration details: 
- username of registered user (usually first and last name), 
- callsign of registered user 
- license key (the key you've received by email during registration process) 

Be careful when entering this data because they have to be exactly same as the data you've used in registration process. 
 
Your license key is valid for one year from purchase day. 
During that period, you can upgrade existing installations with newer versions. 
 
After this one year period is expired, existing version of DXLog.net will continue to work with full functionality. 
It wouldn't be possible to upgrade to newer version with expired license key.

Installation

2014-10-09T11:26:37Z

9a5k: /* Register your copy */

==Download the software==
DXLog.net is available for download at http://www.dxlog.net/sw. 
 
This is fully functional version with all features included. 
 
DXLog.net software is currently available for usage free of charge. 

==Prerequisites==

DXLog.net is written in latest Microsoft technologies, using Microsoft Visual Studio 2010 C# and it is 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 do you have Microsoft.NET Framework 4.0 installed on your system. 
If you are not sure in this, you can start DXLog.net installation and installer will warn you if there isn't .NET Framework 4.0 (or above) installed on your system. 
 
Microsoft.NET Framework 4.0 is available for free download on Microsoft web. 
Direct download link is http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=17718. 
 
Also, if you plan to use LPT port for CW keying and other functions, because of Windows limitations you need DLLPORTIO.dll driver. 
You can download it from DXLog.net web. File is called port95nt.exe and it is available for download on http://www.dxlog.net/sw/tools. 
 
As of version 2.1.1 DXLog.net using SQLite database for data storage. 
On some WinOS Microsoft Visual C++ 2010 RTM Redistributable Package (x86 version) needs to be installed. 
In case that this package isn't found during installation, installer will warn you about this. 
You can download and install this package from here: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=5555 

==Install the software==

Software is installed by default in your Windows Program Files folder. 
Usually that is <tt>C:\Program Files\DXLog.net</tt>. 
For some newer Windows versions (Vista, Win7), folder where application will be installed by default is <tt>C:\Program Files(x86)\DXLog.net</tt>. 
 
Application configuration files as well contest and database definitions are copied into special windows folder called '''Application Data'''
during first run of DXLog.net, if version of file in "Program Files folder" is newer. 

==Register your copy==

To register your copy of DXLog.net and to unlock full version functionality you have to go at http://www.dxlog.net website. 
From main menu, click on "Buy/Register" link (on the top of the screen) and you will be redirected to Avangate secure web site. 
Avangate is our secure provider which will securely process your transaction. 
After entering all details needed and after payment will be confirmed, you will receive registration key on your email. 
In DXLog.net, go to Help->Register menu and fill registration details: 
- username of registered user (usually first and last name), 
- callsign of registered user 
- license key (the key you've received by email during registration process) 

Be careful when entering this data because they have to be exactly same as the data you've used in registration process. 
 
Your license key is valid for one year from purchase day. 
During that period, you can upgrade existing installations with newer versions. 
 
After this one year period is expired, existing version of DXLog.net will continue to work with full functionality. 
It wouldn't be possible to upgrade to newer version with expired license key.

Installation

2014-10-09T11:26:25Z

9a5k: /* Register your copy */

==Download the software==
DXLog.net is available for download at http://www.dxlog.net/sw. 
 
This is fully functional version with all features included. 
 
DXLog.net software is currently available for usage free of charge. 

==Prerequisites==

DXLog.net is written in latest Microsoft technologies, using Microsoft Visual Studio 2010 C# and it is 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 do you have Microsoft.NET Framework 4.0 installed on your system. 
If you are not sure in this, you can start DXLog.net installation and installer will warn you if there isn't .NET Framework 4.0 (or above) installed on your system. 
 
Microsoft.NET Framework 4.0 is available for free download on Microsoft web. 
Direct download link is http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=17718. 
 
Also, if you plan to use LPT port for CW keying and other functions, because of Windows limitations you need DLLPORTIO.dll driver. 
You can download it from DXLog.net web. File is called port95nt.exe and it is available for download on http://www.dxlog.net/sw/tools. 
 
As of version 2.1.1 DXLog.net using SQLite database for data storage. 
On some WinOS Microsoft Visual C++ 2010 RTM Redistributable Package (x86 version) needs to be installed. 
In case that this package isn't found during installation, installer will warn you about this. 
You can download and install this package from here: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=5555 

==Install the software==

Software is installed by default in your Windows Program Files folder. 
Usually that is <tt>C:\Program Files\DXLog.net</tt>. 
For some newer Windows versions (Vista, Win7), folder where application will be installed by default is <tt>C:\Program Files(x86)\DXLog.net</tt>. 
 
Application configuration files as well contest and database definitions are copied into special windows folder called '''Application Data'''
during first run of DXLog.net, if version of file in "Program Files folder" is newer. 

==Register your copy==

To register your copy of DXLog.net and to unlock full version functionality you have to go at http://www.dxlog.net website. 
From main menu, click on "Buy/Register" link (on the top of the screen) and you will be redirected to Avangate secure web site. 
Avangate is our secure provider which will securely process your transaction. 
After entering all details needed and after payment will be confirmed, you will receive registration key on your email. 
In DXLog.net, go to Help->Register menu and fill registration details: 
- username of registered user (usually first and last name),
- callsign of registered user
- license key (the key you've received by email during registration process)

Be careful when entering this data because they have to be exactly same as the data you've used in registration process. 
 
Your license key is valid for one year from purchase day. 
During that period, you can upgrade existing installations with newer versions. 
 
After this one year period is expired, existing version of DXLog.net will continue to work with full functionality. 
It wouldn't be possible to upgrade to newer version with expired license key.

Installation

2014-10-09T11:25:57Z

9a5k: /* Register your copy */

==Download the software==
DXLog.net is available for download at http://www.dxlog.net/sw. 
 
This is fully functional version with all features included. 
 
DXLog.net software is currently available for usage free of charge. 

==Prerequisites==

DXLog.net is written in latest Microsoft technologies, using Microsoft Visual Studio 2010 C# and it is 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 do you have Microsoft.NET Framework 4.0 installed on your system. 
If you are not sure in this, you can start DXLog.net installation and installer will warn you if there isn't .NET Framework 4.0 (or above) installed on your system. 
 
Microsoft.NET Framework 4.0 is available for free download on Microsoft web. 
Direct download link is http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=17718. 
 
Also, if you plan to use LPT port for CW keying and other functions, because of Windows limitations you need DLLPORTIO.dll driver. 
You can download it from DXLog.net web. File is called port95nt.exe and it is available for download on http://www.dxlog.net/sw/tools. 
 
As of version 2.1.1 DXLog.net using SQLite database for data storage. 
On some WinOS Microsoft Visual C++ 2010 RTM Redistributable Package (x86 version) needs to be installed. 
In case that this package isn't found during installation, installer will warn you about this. 
You can download and install this package from here: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=5555 

==Install the software==

Software is installed by default in your Windows Program Files folder. 
Usually that is <tt>C:\Program Files\DXLog.net</tt>. 
For some newer Windows versions (Vista, Win7), folder where application will be installed by default is <tt>C:\Program Files(x86)\DXLog.net</tt>. 
 
Application configuration files as well contest and database definitions are copied into special windows folder called '''Application Data'''
during first run of DXLog.net, if version of file in "Program Files folder" is newer. 

==Register your copy==

To register your copy of DXLog.net and to unlock full version functionality you have to go at http://www.dxlog.net website.
From main menu, click on "Buy/Register" link (on the top of the screen) and you will be redirected to Avangate secure web site.
Avangate is our secure provider which will securely process your transaction.
After entering all details needed and after payment will be confirmed, you will receive registration key on your email.
In DXLog.net, go to Help->Register menu and fill registration details:
- username of registered user (usually first and last name),
- callsign of registered user
- license key (the key you've received by email during registration process)

Be careful when entering this data because they have to be exactly same as the data you've used in registration process.

Your license key is valid for one year from purchase day.
During that period, you can upgrade existing installations with newer versions.

After this one year period is expired, existing version of DXLog.net will continue to work with full functionality.
It wouldn't be possible to upgrade to newer version with expired license key.

Main Page

2014-10-09T11:15:57Z

9a5k:

__NOTOC__
{|width=100%
| style="vertical-align:top;" colspan=2|
{{Main Page header}}
|-
|width=70% |
<ol type="I">
<li>'''[[Preface]]'''
<ol>
<li>[[Preface#Authors and Contributors|Authors and Contributors]]
</ol>
<li> '''[[Installation|Installation]]'''
<ol>
<li>[[Installation#Download_the_software|Download the software]]
<li>[[Installation#Prerequisites|Prerequisites]]
<li>[[Installation#Install_the_software|Install the software]]
<li>[[Installation#Register_your_copy|Register your copy]]
</ol>
<li> '''[[Features|Features]]'''
<ol>
<li>[[Features#Supported_contests|Supported contests]]
<li>[[Features#Contest_config_file|Contest config file]]
</ol>
<li> '''[[Configuration|Configuration]]'''
<ol>
<li>[[Configuration#Contest_configuration|Contest configuration]]
</ol>
<li> '''[[Contest_definition|Contest definition]]'''
<ol>
<li>[[Contest_definition#Description|Description]]
<li>[[Contest_definition#File_structure|File structure]]
<li>[[Contest_definition#Regex_expressions|Regex expressions]]
<li>[[Contest_definition#General_contest_description|General contest description]]
<li>[[Contest_definition#Cabrillo|Cabrillo]]
<li>[[Contest_definition#Band_and_mode_specific|Band and mode specific]]
<li>[[Contest_definition#Entry_field_definitions|Entry field definitions]]
</ol>
<li> '''[[Menus|Menus]]'''
<ol>
<li>[[Menu_File#File|File]]
<li>[[Menu_Edit#Edit|Edit]]
<li>[[Menu_Operating#Operating|Operating]]
<li>[[Menu_Commands#Commands|Commands]]
<li>[[Menu_Messages#Messages|Messages]]
<li>[[Menu_Tools#Tools|Tools]]
<li>[[Menu_Options#Options|Options]]
<li>[[Menu_Windows#Windows|Windows]]
<li>[[Menu_Help#Help|Help]]
</ol>
</ol>
|style="vertical-align:top;"|
|}

Installation

2014-10-09T11:15:04Z

9a5k:

Installation

2014-04-22T21:55:40Z

9a5k: /* Prerequisites */

Installation

2014-04-22T21:28:16Z

9a5k:

Main Page

2014-02-07T18:14:53Z

9a5k:

__NOTOC__
{|width=100%
| style="vertical-align:top;" colspan=2|
{{Main Page header}}
|-
|width=70% |
<ol type="I">
<li>'''[[Preface]]'''
<ol>
<li>[[Preface#Authors and Contributors|Authors and Contributors]]
</ol>
<li> '''[[Installation|Installation]]'''
<ol>
<li>[[Installation#Download_the_software|Download the software]]
<li>[[Installation#Prerequisites|Prerequisites]]
<li>[[Installation#Install_the_software|Install the software]]
</ol>
<li> '''[[Features|Features]]'''
<ol>
<li>[[Features#Supported_contests|Supported contests]]
<li>[[Features#Contest_config_file|Contest config file]]
</ol>
<li> '''[[Configuration|Configuration]]'''
<ol>
<li>[[Configuration#Contest_configuration|Contest configuration]]
</ol>
<li> '''[[Contest_definition|Contest definition]]'''
<ol>
<li>[[Contest_definition#Description|Description]]
<li>[[Contest_definition#File_structure|File structure]]
<li>[[Contest_definition#Regex_expressions|Regex expressions]]
<li>[[Contest_definition#General_contest_description|General contest description]]
<li>[[Contest_definition#Cabrillo|Cabrillo]]
<li>[[Contest_definition#Band_and_mode_specific|Band and mode specific]]
<li>[[Contest_definition#Entry_field_definitions|Entry field definitions]]
</ol>
<li> '''[[Menus|Menus]]'''
<ol>
<li>[[Menu_File#File|File]]
<li>[[Menu_Edit#Edit|Edit]]
<li>[[Menu_Operating#Operating|Operating]]
<li>[[Menu_Commands#Commands|Commands]]
<li>[[Menu_Messages#Messages|Messages]]
<li>[[Menu_Tools#Tools|Tools]]
<li>[[Menu_Options#Options|Options]]
<li>[[Menu_Windows#Windows|Windows]]
<li>[[Menu_Help#Help|Help]]
</ol>
</ol>
|style="vertical-align:top;"|
|}

Contest definition

2014-02-07T16:00:34Z

9a5k:

==Description==

Rules for each of the contests are more or less different from each other. 
It can be difference in points per qso calculations, multiplier determination and calculations etc. 

To support all these different rules and to allow easier adding / changing contest rules in DXLog.net,
all parameters in contest rules are defined and controlled through contest config files. 
Contest config files are plain text files which are installed in '''Contest''' sub-folder in DXLog.net installation folder. 

When application is started, content of Contest folder is copied into ApplicationData folder in your Windows OS. 
During copying process, DXLog.net compares modify date of each file in installation folder with version in ApplicationData folder. 
If newer version already exists in ApplicationData folder, file wouldn't be copied there. 

User can change existing or create new files in Application folder, in case it is needed for some testing purposes, or if user
wants to create new contest definition file to support some new contest. 

==File structure==

Each line in contest config file usually contains of KEY + VALUE pairs. 
This pair is separated by "=" sign. 
For example: 
CONTEST_NAME=9A CW 
This means that field KEY is '''CONTEST-NAME''', and '''9A CW''' is value for that field.

==Regex expressions==

You will see that in many cases DXLog.net is using regular expressions (regex) to verify if some condition is valid and possibly to process such entry on special ways. For example, it is used to check if user entry is valid against some condition, to determine how to calculate points for QSO etc. 

Regex expression in config file can be defined as fixed value, but can also compare some QSO data against fixed values. 
Case one is the case where we want to validate user entry in some of the fields. 
For example, we want to validate that user is allowed to enter NY,FL,GA, or DX in EXCHANGE field at contest configuration screen. 
Key field for this operation is CFG_MULT_RGX_CHECK. 
And to create validation as in previous example we need following definition in contest config file: 
CFG_MULT_RGX_CHECK=^NY$|^FL$|^GA$|^DX$ 
"^" sign in regex denotes start of the string value
"$" sign in regex denotes end of string value
"|" sign in regex is logical or operation

Case two is the case where we want to validate some value which is possibly changing on each entry in the log. 
For example, we want to calculate points for QSO with same country on band 160 mode CW and SSB with 1 point.
Key field for points calculation is POINTS_FIELD_BAND_MODE.
To achieve calculation from previous example, it should be defined like this:
POINTS_FIELD_BAND_MODE=SOURCE->DXCC:DEST->DXCC;ALL;^160$;^CW$|^SSB$;1 
We can read this definition on the following way:
If SOURCE (our) DXCC is same as DEST (correspondent) DXCC and band is 160 and mode is CW or SSB, qso is worth 1 point.
In above definition, we can notice, SOURCE and DEST keys. Also, we can use CONFIG key.
Such reference keys can be:
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 received field in qso line
DEST->RECINFO - value entered in recinfo field in qso line
DEST->RECINFO2 - value entered in recinfo2 field in qso line
DEST->RECINFO3 - value entered in recinfo3 field in qso line
CONFIG->EXCHANGE - value from exchange field entered at contest configuration screen
CONFIG->CQZONE - value from WAZ field entered at contest configuration screen
CONFIG->ITUZONE - value from ITU field entered at contest configuration screen
CONFIG->OPNAME - value from OPNAME field entered at contest configuration screen
CONFIG->POWER - value from POWERfield entered at contest configuration screen

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

==General contest description==

These keys are used for general contest description in config file, such as contest name, link to the rules etc. 

* '''CONTESTGROUP'''

Used for group contest when displaying on config screen for contest selection. 
For example: Digital, 9A Local Contest etc. 

* '''CONTESTNAME'''

Contest name as it will be shown and recognized in contest selection box. 
Note: this can be same as cabrillo contest name, but usually it is 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'''

* '''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 layout of QSO entry screen. Allows to define visibility, length, labels, checking procedures etc. for each of the field which user can enter or display for any QSO. 

* '''FIELD_AZ_VISIBLE'''

Controls visibility of Azimuth field. Mostly used on VHF/UHF/SHF to get Azimuth from gridsquare. 

Acceptable values: YES/NO 
Default value: NO 

* '''FIELD_CALLSIGN_WWL_CHECK'''

If YES, entry in callsign field will be checked if it can be possible gridsquare entry. 
It it is gridsquare, then callsign field value will be copied to gridsquare entry field and Azimuth will be calculated and shown. 

Acceptable values: YES/NO 
Default value: NO 

* '''FIELD_MODE_VISIBLE'''

Is mode field visible on qso entry line. 

Acceptable values: YES/NO 
Default value: NO 

* '''FIELD_MODE_NAME'''

Header name for field mode. 

* '''FIELD_MULT_VISIBLE'''

Is field MULT visible on the screen. 

Acceptable values: YES/NO 

* '''FIELD_NR_VISIBLE'''

If field SENT QSO SERIAL NUMBER visible on 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 serial number and other stations are sending some other date (for example some local province). 

* '''FIELD_NR_HIDDEN_RGX'''

Regex expression. If condition is valid, SENT QSO SERIAL NUMBER will be hidden. 
Usable for contests where some stations are sending serial number and other stations are sending some other date (for example some local province). 

* '''FIELD_PERIOD_VISIBLE'''

Is field PERIOD number visible in 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

2014-02-07T15:50:12Z

9a5k: /* Entry field definitions */

==Description==

Rules for each of the contests are more or less different from each other. 
It can be difference in points per qso calculations, multiplier determination and calculations etc. 

To support all these different rules and to allow easier adding / changing contest rules in DXLog.net,
all parameters in contest rules are defined and controlled through contest config files. 
Contest config files are plain text files which are installed in '''Contest''' sub-folder in DXLog.net installation folder. 

When application is started, content of Contest folder is copied into ApplicationData folder in your Windows OS. 
During copying process, DXLog.net compares modify date of each file in installation folder with version in ApplicationData folder. 
If newer version already exists in ApplicationData folder, file wouldn't be copied there. 

User can change existing or create new files in Application folder, in case it is needed for some testing purposes, or if user
wants to create new contest definition file to support some new contest. 

==File structure==

Each line in contest config file usually contains of KEY + VALUE pairs. 
This pair is separated by "=" sign. 
For example: 
CONTEST_NAME=9A CW 
This means that field KEY is '''CONTEST-NAME''', and '''9A CW''' is value for that field.

==Regex expressions==

You will see that in many cases DXLog.net is using regular expressions (regex) to verify if some condition is valid and possibly to process such entry on special ways. For example, it is used to check if user entry is valid against some condition, to determine how to calculate points for QSO etc. 

Regex expression in config file can be defined as fixed value, but can also compare some QSO data against fixed values. 
Case one is the case where we want to validate user entry in some of the fields. 
For example, we want to validate that user is allowed to enter NY,FL,GA, or DX in EXCHANGE field at contest configuration screen. 
Key field for this operation is CFG_MULT_RGX_CHECK. 
And to create validation as in previous example we need following definition in contest config file: 
CFG_MULT_RGX_CHECK=^NY$|^FL$|^GA$|^DX$ 
"^" sign in regex denotes start of the string value
"$" sign in regex denotes end of string value
"|" sign in regex is logical or operation

Case two is the case where we want to validate some value which is possibly changing on each entry in the log. 
For example, we want to calculate points for QSO with same country on band 160 mode CW and SSB with 1 point.
Key field for points calculation is POINTS_FIELD_BAND_MODE.
To achieve calculation from previous example, it should be defined like this:
POINTS_FIELD_BAND_MODE=SOURCE->DXCC:DEST->DXCC;ALL;^160$;^CW$|^SSB$;1 
We can read this definition on the following way:
If SOURCE (our) DXCC is same as DEST (correspondent) DXCC and band is 160 and mode is CW or SSB, qso is worth 1 point.
In above definition, we can notice, SOURCE and DEST keys. Also, we can use CONFIG key.
Such reference keys can be:
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 received field in qso line
DEST->RECINFO - value entered in recinfo field in qso line
DEST->RECINFO2 - value entered in recinfo2 field in qso line
DEST->RECINFO3 - value entered in recinfo3 field in qso line
CONFIG->EXCHANGE - value from exchange field entered at contest configuration screen
CONFIG->CQZONE - value from WAZ field entered at contest configuration screen
CONFIG->ITUZONE - value from ITU field entered at contest configuration screen
CONFIG->OPNAME - value from OPNAME field entered at contest configuration screen
CONFIG->POWER - value from POWERfield entered at contest configuration screen

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

==General contest description==

These keys are used for general contest description in config file, such as contest name, link to the rules etc. 

* '''CONTESTGROUP'''

Used for group contest when displaying on config screen for contest selection. 
For example: Digital, 9A Local Contest etc. 

* '''CONTESTNAME'''

Contest name as it will be shown and recognized in contest selection box. 
Note: this can be same as cabrillo contest name, but usually it is 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. 

==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 layout of QSO entry screen. Allows to define visibility, length, labels, checking procedures etc. for each of the field which user can enter or display for any QSO. 

* '''FIELD_AZ_VISIBLE'''

Controls visibility of Azimuth field. Mostly used on VHF/UHF/SHF to get Azimuth from gridsquare. 

Acceptable values: YES/NO 
Default value: NO 

* '''FIELD_CALLSIGN_WWL_CHECK'''

If YES, entry in callsign field will be checked if it can be possible gridsquare entry. 
It it is gridsquare, then callsign field value will be copied to gridsquare entry field and Azimuth will be calculated and shown. 

Acceptable values: YES/NO 
Default value: NO 

* '''FIELD_MODE_VISIBLE'''

Is mode field visible on qso entry line. 

Acceptable values: YES/NO 
Default value: NO 

* '''FIELD_MODE_NAME'''

Header name for field mode. 

* '''FIELD_MULT_VISIBLE'''

Is field MULT visible on the screen. 

Acceptable values: YES/NO 

* '''FIELD_NR_VISIBLE'''

If field SENT QSO SERIAL NUMBER visible on 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 serial number and other stations are sending some other date (for example some local province). 

* '''FIELD_NR_HIDDEN_RGX'''

Regex expression. If condition is valid, SENT QSO SERIAL NUMBER will be hidden. 
Usable for contests where some stations are sending serial number and other stations are sending some other date (for example some local province). 

* '''FIELD_PERIOD_VISIBLE'''

Is field PERIOD number visible in 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

2014-02-07T15:37:15Z

9a5k: /* Entry field definitions */

==Description==

Rules for each of the contests are more or less different from each other. 
It can be difference in points per qso calculations, multiplier determination and calculations etc. 

To support all these different rules and to allow easier adding / changing contest rules in DXLog.net,
all parameters in contest rules are defined and controlled through contest config files. 
Contest config files are plain text files which are installed in '''Contest''' sub-folder in DXLog.net installation folder. 

When application is started, content of Contest folder is copied into ApplicationData folder in your Windows OS. 
During copying process, DXLog.net compares modify date of each file in installation folder with version in ApplicationData folder. 
If newer version already exists in ApplicationData folder, file wouldn't be copied there. 

User can change existing or create new files in Application folder, in case it is needed for some testing purposes, or if user
wants to create new contest definition file to support some new contest. 

==File structure==

Each line in contest config file usually contains of KEY + VALUE pairs. 
This pair is separated by "=" sign. 
For example: 
CONTEST_NAME=9A CW 
This means that field KEY is '''CONTEST-NAME''', and '''9A CW''' is value for that field.

==Regex expressions==

You will see that in many cases DXLog.net is using regular expressions (regex) to verify if some condition is valid and possibly to process such entry on special ways. For example, it is used to check if user entry is valid against some condition, to determine how to calculate points for QSO etc. 

Regex expression in config file can be defined as fixed value, but can also compare some QSO data against fixed values. 
Case one is the case where we want to validate user entry in some of the fields. 
For example, we want to validate that user is allowed to enter NY,FL,GA, or DX in EXCHANGE field at contest configuration screen. 
Key field for this operation is CFG_MULT_RGX_CHECK. 
And to create validation as in previous example we need following definition in contest config file: 
CFG_MULT_RGX_CHECK=^NY$|^FL$|^GA$|^DX$ 
"^" sign in regex denotes start of the string value
"$" sign in regex denotes end of string value
"|" sign in regex is logical or operation

Case two is the case where we want to validate some value which is possibly changing on each entry in the log. 
For example, we want to calculate points for QSO with same country on band 160 mode CW and SSB with 1 point.
Key field for points calculation is POINTS_FIELD_BAND_MODE.
To achieve calculation from previous example, it should be defined like this:
POINTS_FIELD_BAND_MODE=SOURCE->DXCC:DEST->DXCC;ALL;^160$;^CW$|^SSB$;1 
We can read this definition on the following way:
If SOURCE (our) DXCC is same as DEST (correspondent) DXCC and band is 160 and mode is CW or SSB, qso is worth 1 point.
In above definition, we can notice, SOURCE and DEST keys. Also, we can use CONFIG key.
Such reference keys can be:
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 received field in qso line
DEST->RECINFO - value entered in recinfo field in qso line
DEST->RECINFO2 - value entered in recinfo2 field in qso line
DEST->RECINFO3 - value entered in recinfo3 field in qso line
CONFIG->EXCHANGE - value from exchange field entered at contest configuration screen
CONFIG->CQZONE - value from WAZ field entered at contest configuration screen
CONFIG->ITUZONE - value from ITU field entered at contest configuration screen
CONFIG->OPNAME - value from OPNAME field entered at contest configuration screen
CONFIG->POWER - value from POWERfield entered at contest configuration screen

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

==General contest description==

These keys are used for general contest description in config file, such as contest name, link to the rules etc. 

* '''CONTESTGROUP'''

Used for group contest when displaying on config screen for contest selection. 
For example: Digital, 9A Local Contest etc. 

* '''CONTESTNAME'''

Contest name as it will be shown and recognized in contest selection box. 
Note: this can be same as cabrillo contest name, but usually it is 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. 

==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 layout of QSO entry screen. Allows to define visibility, length, labels, checking procedures etc. for each of the field which user can enter or display for any QSO. 

* '''FIELD_AZ_VISIBLE'''

Controls visibility of Azimuth field. Mostly used on VHF/UHF/SHF to get Azimuth from gridsquare. 

Acceptable values: YES/NO 
Default value: NO 

* '''FIELD_CALLSIGN_WWL_CHECK'''

If YES, entry in callsign field will be checked if it can be possible gridsquare entry. 
It it is gridsquare, then callsign field value will be copied to gridsquare entry field and Azimuth will be calculated and shown. 

Acceptable values: YES/NO 
Default value: NO 

* '''FIELD_MODE_VISIBLE'''

Is mode field visible on qso entry line. 

Acceptable values: YES/NO 
Default value: NO 

* '''FIELD_MODE_NAME'''

Header name for field mode. 

* '''FIELD_MULT_VISIBLE'''

Is field MULT visible on the screen. 

Acceptable values: YES/NO 

* '''FIELD_NR_VISIBLE'''

If field SENT QSO SERIAL NUMBER visible on 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 serial number and other stations are sending some other date (for example some local province). 

* '''FIELD_NR_HIDDEN_RGX'''

Regex expression. If condition is valid, SENT QSO SERIAL NUMBER will be hidden. 
Usable for contests where some stations are sending serial number and other stations are sending some other date (for example some local province). 

* '''FIELD_PERIOD_VISIBLE'''

Is field PERIOD number visible in qso entry line. 

Acceptable values: YES/NO 

* '''FIELD_PERIOD_NAME'''

Header name for field NAME. 

* '''FIELD_PTS_NAME'''
* '''FIELD_PTS_VISIBLE'''
* '''FIELD_RCVD_CHECK_FORMAT_FX'''
* '''FIELD_RCVD_COPY'''
* '''FIELD_RCVD_COPY_EXC_DXCC'''
* '''FIELD_RCVD_COPY_EXC_RGX'''
* '''FIELD_RCVD_COPY_FX'''
* '''FIELD_RCVD_DEFAULT_VALUE'''
* '''FIELD_RCVD_EXC_CHECK_DXCC'''
* '''FIELD_RCVD_FORMAT_FX'''
* '''FIELD_RCVD_FX_CHECK'''
* '''FIELD_RCVD_MANDATORY'''
* '''FIELD_RCVD_MANDATORY_RGX_EXC'''
* '''FIELD_RCVD_MAX_LENGTH'''
* '''FIELD_RCVD_MIN_LENGTH'''
* '''FIELD_RCVD_NUMERIC'''
* '''FIELD_RCVD_RGX_CHECK'''
* '''FIELD_RCVD_TYPE'''
* '''FIELD_RCVD_WWL_CHECK'''
* '''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

2014-02-07T15:28:48Z

9a5k: /* Band and mode specific */

Contest definition

2014-02-07T15:25:48Z

9a5k: /* Configuration screen control */

Contest definition

2014-02-07T15:25:13Z

9a5k: /* Regex expressions */

Contest definition

2014-02-07T15:01:24Z

9a5k:

Contest definition

2014-02-07T15:01:02Z

9a5k: /* Configuration screen control */

Contest definition

2014-02-07T14:58:32Z

9a5k: /* Configuration screen control */

Contest definition

2014-02-07T14:57:56Z

9a5k: /* Configuration screen control */

Contest definition

2014-02-07T14:51:13Z

9a5k: /* Configuration screen control */

Contest definition

2014-02-07T14:47:05Z

9a5k: /* Configuration screen control */

Contest definition

2014-02-07T13:51:16Z

9a5k: /* General contest description */

Contest definition

2014-02-07T13:33:21Z

9a5k:

Contest definition

2014-02-07T13:31:50Z

9a5k:

Contest definition

2014-02-07T13:30:48Z

9a5k: /* File structure */

Contest definition

2014-02-07T13:30:40Z

9a5k: /* File structure */

Contest definition

2014-02-07T13:30:25Z

9a5k:

Contest definition

2014-02-07T13:28:04Z

9a5k: /* Description */

Contest definition

2014-02-07T13:20:27Z

9a5k: Created page with "==Description== ==Keys=="

==Description==

==Keys==

Main Page

2014-02-07T13:19:34Z

9a5k:

__NOTOC__
{|width=100%
| style="vertical-align:top;" colspan=2|
{{Main Page header}}
|-
|width=70% |
<ol type="I">
<li>'''[[Preface]]'''
<ol>
<li>[[Preface#Authors and Contributors|Authors and Contributors]]
</ol>
<li> '''[[Installation|Installation]]'''
<ol>
<li>[[Installation#Download_the_software|Download the software]]
<li>[[Installation#Prerequisites|Prerequisites]]
<li>[[Installation#Install_the_software|Install the software]]
</ol>
<li> '''[[Features|Features]]'''
<ol>
<li>[[Features#Supported_contests|Supported contests]]
<li>[[Features#Contest_config_file|Contest config file]]
</ol>
<li> '''[[Configuration|Configuration]]'''
<ol>
<li>[[Configuration#Contest_configuration|Contest configuration]]
</ol>
<li> '''[[Contest_definition|Contest definition]]'''
<ol>
<li>[[Contest_definition#Description|Description]]
<li>[[Contest_definition#Keys|Keys]]
</ol>
<li> '''[[Menus|Menus]]'''
<ol>
<li>[[Menu_File#File|File]]
<li>[[Menu_Edit#Edit|Edit]]
<li>[[Menu_Operating#Operating|Operating]]
<li>[[Menu_Commands#Commands|Commands]]
<li>[[Menu_Messages#Messages|Messages]]
<li>[[Menu_Tools#Tools|Tools]]
<li>[[Menu_Options#Options|Options]]
<li>[[Menu_Windows#Windows|Windows]]
<li>[[Menu_Help#Help|Help]]
</ol>
</ol>
|style="vertical-align:top;"|
|}

Main Page

2014-02-07T13:18:03Z

9a5k:

__NOTOC__
{|width=100%
| style="vertical-align:top;" colspan=2|
{{Main Page header}}
|-
|width=70% |
<ol type="I">
<li>'''[[Preface]]'''
<ol>
<li>[[Preface#Authors and Contributors|Authors and Contributors]]
</ol>
<li> '''[[Installation|Installation]]'''
<ol>
<li>[[Installation#Download_the_software|Download the software]]
<li>[[Installation#Prerequisites|Prerequisites]]
<li>[[Installation#Install_the_software|Install the software]]
</ol>
<li> '''[[Features|Features]]'''
<ol>
<li>[[Features#Supported_contests|Supported contests]]
<li>[[Features#Contest_config_file|Contest config file]]
</ol>
<li> '''[[Configuration|Configuration]]'''
<ol>
<li>[[Configuration#Contest_configuration|Contest configuration]]
</ol>
<li> '''[[Contest definition|Contest definition]]'''
<ol>
<li>[[Contest_Definition#Description|Description]]
<li>[[Contest_Definition#Keys|Keys]]
</ol>
<li> '''[[Menus|Menus]]'''
<ol>
<li>[[Menu_File#File|File]]
<li>[[Menu_Edit#Edit|Edit]]
<li>[[Menu_Operating#Operating|Operating]]
<li>[[Menu_Commands#Commands|Commands]]
<li>[[Menu_Messages#Messages|Messages]]
<li>[[Menu_Tools#Tools|Tools]]
<li>[[Menu_Options#Options|Options]]
<li>[[Menu_Windows#Windows|Windows]]
<li>[[Menu_Help#Help|Help]]
</ol>
</ol>
|style="vertical-align:top;"|
|}

Main Page

2014-02-07T13:16:14Z

9a5k:

Introduction

2014-02-07T12:54:39Z

9a5k: /* Authors and Contributors */

DXLog.net project is started by Kresimir Kovarik, 9A5K during summer 2011.

==Authors and Contributors==

There are couple of people active in testing and development of DXLog.net currently. 
Big thanks to 9A1AA, 9A6C, DK8ZZ/VE3ZIK, E77DX/OE1EMS, IK2NCJ, N6TV, W9PA, YT3W and all others for continuous support, ideas and testing of new DXLog.net versions. 

==Want to help?==

If you have some time available and want to join us and help in any of possible areas (testing, development, documentation etc), it will be our pleasure to have you as a part of the team. 
Just contact 9A5K by e-mail (9a5k (at) 9a5k.com) for further details.

Menu Windows

2014-02-07T12:40:21Z

9a5k:

<big><big>Menu:Windows</big></big>

==Worked DXCC==
Shortcut: <code>ALT+M</code> 

==Check callsign==
Shortcut: <code>F9</code> 

==Check multipliers==
Shortcut: <code>F10</code> 

==Check partials==
Shortcut: <code>F12</code> 

==Check N+1==
Shortcut: <code>F8</code> 

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

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

==Operating info==

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

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

==Status window==
Shrotcut: <code>ALT+J</code> 

==Partner==

==Radio/Ant status window==

==Radio 1==

==Radio 2==

==Primary decoder Radio 1==

==Secondary decoder Radio 1==

==Primary decoder Radio 2==

==Secondary decoder Radio 2==

==DX-Cluster monitor==
Shortcut: <code>ALT+O</code> 

==DX-Cluster announcements==
Shortcut: <code>ALT+A</code> 

==Clock==

==SSB Bargraph==

Menu Operating

2014-02-07T12:37:11Z

9a5k:

<big><big>Menu:Operating</big></big>

==Period autoswitch==
Some contests are splitted in couple of periods defined by time length. 
In contest configuration file, it is possible to define this lengths and number of periods. 
When this option is activated, DXLog.net automatically switch contest period in next one when time for active period elapses.

==Bandmap==
* Add with SPACEBAR
By default, you can add new entry to bandmap by pressing <code>CTRL+ENTER</code>. 
After callsign is added to bandmap, entry is cleared. 
When this option is activated, new entry in bandmap will be created when spacebar is pressed on current QSO. 
Of course, callsign isn't cleared.

* Grab first valid upper spot
Shortcut: <code>CTRL+UP ARROW</code> 
You can select upper '''valid''' call moving up into bandmap and grab it into call entry field by pressing <code>CTRL+UP ARROW</code>. 

* Grab first upper spot
Shortcut: <code>CTRL+SHIFT+UP ARROW</code> 
You can select '''any''' upper call moving up into bandmap and grab it into call entry field by pressing <code>CTRL+SHIFT+UP ARROW</code>. 

* Grab first valid lower spot
Shortcut: <code>CTRL+DOWN ARROW</code> 
You can select lower '''valid''' call moving down into bandmap and grab it into call entry field by pressing <code>CTRL+DOWN ARROW</code>. 

* Grab first upper spot
Shortcut: <code>CTRL+SHIFT+UP ARROW</code> 
You can select '''any''' lower call moving down into bandmap and grab it into call entry field by pressing <code>CTRL+SHIFT+UP ARROW</code>. 

==Technique==
This selects the category you are going to join and enable/disable software features according. 

* SO1R/Multi op
Must be selected if you are SO with 1 radio or any Multi operators category. 
Headphone audio options are '''DISABLE''' 
Only one entry QSO line is enable.

* SO2R
Must be selected if you are SO with 2 radios. 
Headphone audio options menu is '''ENABLE''' 
''Listen to primary radio'' 
''Shortcut: '''CTRL+ALT+A'''''
''You can ear primary radio audio on both ears'' 

''Listen to secondary radio '' 
''Shortcut: '''CTRL+ALT+T'''''
''You can ear secondary radio audio on both ears'' 

''Listen to secondary radio during transmit '' 
''Shortcut: '''CTRL+ALT+L'''''
''You can ear secondary radio audio on both ears while TX with primary'' 

''Listen to both radios '' 
''Shortcut: '''CTRL+ALT+S'''''
''You can ear primary audio in one ear and secondary radio audio in the other at same time'' 

'''All commands work if your are managing the 2 radios using machine like EZMaster or Microham MK2R+/MK2R/U2R'''

Two entry QSO line are enable, one controlling R1 and the other R2. You can swap between them using "*" or "Caps lock" key

* Advanced SO2R
'''All commands work if your are managing the 2 radios using machine like EZMaster or Microham MK2R+/MK2R/U2R''' 
Must be selected if you are SO with 2 radios. 
Headphone audio options menu is '''ENABLE''' (same commands as per SO2R) 
Special strings of command called '''SCENARIO''' are '''ENABLE''' 
Scenario string is a sequence of commands that can be sent to control radios behave and audio status automatically. 
It can be assigned to each Fx key both for R1 and R2.There are some "ready to go" scenarios or you can programm your own. To program scenario you must select the proper window in menu OPERATING -> Edit SO2R scenarios 
Scenario can work all modes: CW,SSB and RTTY. 
String can be composed by a logic of commands sequence that starts when pressing a Fx key. 
An simple example of string can be: 
[[File:scenario.jpg]] 
Primary radio is not R1 but is radio '''with TX FOCUS''', secondary radio is not R2 but is radio '''without TX FOCUS''' 

If you press primary radio F1 you will have automatically switched left and right headphone ears on secondary radio audio (command $R2R2)in this case R2 then message of F1 start to play (command $F1) and, at the end of it, you have audio back to primary radio (command $R1R1) in this case R1 on both ears. 

If you need to call a multiplier on R2, for example, you press F4 on secondary radio and you have: 
Audio to primary radio (command $R1R1) in this case R1 on both ears. 
F4 message starts to play (command $F4) on primary radio in this case R2 
Audio to secondary radio (command $R2R2) in this case R2 on both ears 
Change TX focus on secondary radio in this case R1 (command $STR2) 
Start to play additional message 1 set into ALT+C window such as "CQ TEST" to secondary radio in this case R1 (command: $MSG1) 
When finished msg1 audio is switched R1 on left ear and R2 on right ear simultaneously (command $R1R2) 

The variables to programm each string are: 

$GRNR sends gr/num of the received QTC
$SERIAL sends QSO #
$LOGGEDCALL send what's typed in callsign field
$TR1 and $TR2 primary radio or secondary radio tx
$GRABSPOT, which grabs spot on the current frequency
$ZONE sends zone nr set in contest configuration
$R1R1, $R1R2, $R2R1, $R2R2 which can be entered in the predefined CW messages to set the headphone
$INSERT and $PLUS send messages behind ins or +
$RESET cancels any manual change made in the audio control
$ALTERNATECQ (or $ACQ) swaps primary and secondary radios and send CQ on the secondary radio
$CQ same as $ALTERNATECQ but does not swap radios
$MSG1...$MSG12: additional CW messages (see Alt + C)
$SPACEBAR works like hitting spacebar-key (move cursor to exchange field)
$TAB work like hitting tab-key (move cursor to next field)
$GUESSZONE filling exchange field(s) if possible, but cursor remains in the same edit field
$GUESSEXCH (or $GUESSEXCHANGE) mimics a space bar hit (filling exchange field(s)
$CR works like hitting enter-key (log QSO)
$MYCALL sends callsign set in contest configuration
$REPEAT Reset the automatic repeat mode interval
$CORRECT send a call correction, if any
$F1...$F6 send the message associated with F1 ... F6 function key
$LATCH sets latch mode
$QSOB4 send QSOB4 message if the current QSO is a dupe
$CHECK: send license year (ARRL SS only)
$CORRECT: sends a call correction, if any (see correction)
$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.
$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 the frequency of the secondary radio (useful for passing mults)
$INSERT: sends message in the [Ins] key
$ISLAND: sends IOTA Reference (i.e. EU001, AF001, ...) (IOTA Contest)
$LOGGED (or $LOGGEDCALL): sends what is typed in the callsign field of the current QSO, or if blank, the previous QSO
$MSG1...$MSG12: sends additional CW messages (see Modify additional messages)
$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: sends message 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)
$QSOB4: sends the QSOB4 message and cancels the remainder of the current message, if the current QSO is a dupe, otherwise sends nothing
$RST: sends report from RST Sent field (normally 5NN)
$SERIAL: sends current QSO Serial Number, or previous serial number if the line with the cursor is blank.
$STATE: sends State/Province set in contest configuration (Exchange)
$YEAR: sends year nr set in contest configuration (i.e. EUHFC, AA)
$ZONE: sends zone nr set in contest configuration
&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 then 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
$CR: works like hitting [Enter] (log QSO)
$GRABPARTNER: grabs the first callsign from the Partner window and inserts it in the callsign field.
$GRABSPOT grabs spot on the current frequency
$GUESSEXCH (or $GUESSEXCHANGE): mimics a space bar hit, filling the exchange field(s) if possible, but the cursor remains in the same edit field.
$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.
$RSTEXCHSENT: Resets the "exchangeSent" flag of the active QSO (useful only for ESM scripts)
$SETEXCHSENT: Sets the "exchangeSent" flag of the active QSO (useful only for ESM scripts)
$SPACEBAR: works like hitting spacebar-key (move cursor to the next most-used field)
$TAB: works like hitting [Tab] (move cursor to next field)
$ALTERNATECQ (or $ACQ): swaps primary and secondary radios and send CQ on the secondary radio
$CQ: same as $ALTERNATECQ but does not swap radios
$LATCH: sets latch mode
$SPACEBAR - same as $SPACE (press spacebar in currently active field)
$CHECKCALL - move focus to callsign and press spacebar
$GUESSEXCH - try to guess exchange, focus stays in currently active field
$LOGQSO - silently save QSO (useful in ESM + S&P mode)
$CTRLPLUS - same sa $LOGQSO
$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
$FOCUS1 - change Focused radio to Radio 1
$FOCUS2 - change Focused radio to Radio 2
$SWAPFOCUS - change Focused radio to opposite Radio
$GRABPARTNER - grab next call from partner window into callsign field in current entry line
$MK2R=cmd: send a specific MK2R command to the microHAM MK2R SO2R box. 

All strings can be edited "on-the-fly" pressing '''Shift+Fx''' keys. 

'''All commands work if your are managing the 2 radios using machine like EZMaster or Microham MK2R+/MK2R/U2R''' 

==Listen to the primary radio==

==Listen to the secondary radio (headphone toggle)==

==Listen to the secondary radio (headphone latch)==

==Listen to both radio (headphone Split)==

==Edit SO2R Scenarios==

==SO2R scenario selection==

Menu Options

2014-02-07T12:35:41Z

9a5k:

<big><big>Menu:Options</big></big>

==Load contest at startup==

* '''Enabled'''

If checked last opened log will be opened automatically after DXLog.net is started. 

* '''Disabled'''

If checked, it disables automatically log opening. 

==Automatic backup==

If clicked, it will open log backup window, where parameters for log backup can be chosen according to the user's preference. 

==CW==

* '''No sound'''
Text command: <code>SOUND / NOSOUND</code> 
Turns on or off CW monitor sound. 
If smart keyer (WinKey) is configured on any of interfaces, this function doesn't produce the sound. 

* '''Enable different R1/R2 speed'''

If checked, different CW speed can be set for Radio 1 and Radio 2. 

* '''Speed'''

''Decrease''
Shortcut: <code>ALT+F9</code> 
Decrease active radio CW speed by 2 WPM. 

''Decrease other''
Shortcut: <code>CTRL+ALT+F9</code> 
Decrease inactive radio CW speed by 2 WPM. 

''Increase''
Shortcut: <code>ALT+F10</code> 
Increase active radio CW speed by 2 WPM. 

''Increase other''
Shortcut: <code>CTRL+ALT+F10</code> 
Increase inactive radio CW speed by 2 WPM. 

* '''Modify standard messages'''
Text command: <code>MESSAGES / MSGS</code> 
This option is used to edit the contents of all standard F1..F2, INS, PLUS messages for RUN and S&P mode. 
 [[File:Dxl_msgs1.png]] 
Edited content is saved in currently opened DXLog.net contest file. 

 [[File:Dxl_msgs2.png]] 
Tab Options allows you to fix some additional options: 
'''$QSOB4 macro''' 
Which text will be sent $QSOB4 macro is activated in case of dupe qso 
'''Only use RUN messages''' 
DXLog.net will use only RUN messages, even if you switch mode in Search & pounce 
'''Sprint Exchange Logic''' 
This setting is applicable only for contest where Sprint Exchange Logic is enabled in config file. 
When this option is checked, during the contest, when user press INSERT key, DXLog.net will send INS message for RUN mode in case that received serial number field is empty.
Otherwise, DXLog.net will send INS message for S&P mode. 

* '''Modify additional messages'''
Shortcut: <code>ALT+C</code> 
Here you can edit additional CW messages which can be used as macro $MSG1..12. 
 [[File:Dxl_othermsgs.png]] 
Content of additional messages is saved in DXLog.net config file. 

* '''Serial number'''

Choose serial number abbreviation type when sending serial number during the contest. 
Possible options are: 
''Leading zeros'' 
When checked leading zeros are sent (for example 001 instead of 1). 
''Not abbreviated'' 
''Half abbreviated'' 
''Abbreviated'' 
''Pro'' 

* '''Shortened spaces (CT spaces)'''

When checked, shortened spaces will be activated (CT style). 

* '''Remap keys in keyboard mode'''

When checked, keyboard remapping will be active when sending CW/RTTY text in keyboard mode. 

* '''Work dupes'''

When checked, QSOB4 message wouldn't be sent if qso is a dupe. 

* '''Speed limits'''

Allows you to set cw speed limits (lowest and highest cw speed which can be selected). 

* Add spacing when stacking messages

When stacking messages during CW/RTTY contest (pressing for example F5 and F2 keys), if this option is checked one space character will be added between this each message added in buffer. 

==RTTY configuration==

==MK2R/MK2R+/u2R configuration==

==Configure interfaces==

[[File:DXL_port_config.png]]
 
DXLog.net currently supports interfaces on 8 com ports and one LPT port. 
Also, you can use PC sound board as Voice keyer during the contest. 
To use any of ports to connect to the hardware and perform some of the functions, you must enable the port by checking "Enabled" box. 
 
To use a printer port (LPT), you must enable it by checking "Enabled" box in printer port group. 
Additional data for printer port are configured by clicking Setup in printer port group. 
 
[[File:Dxl_printer_port_config.png]]
 
 
In serial port section, you can select any COM port in range COM1 to COM20. 
The only restriction is that you can't select same COM port only on one of the interfaces. 
In each serial port interface you can select appropriate device type in combo box in same row. 
Each of devices have some additional parameters available for setting. You can change them by clicking on Setup button for each interface. 

==Interface specific options==
* '''Allow different TX/RX antenna'''

If checked this option allows different selection for TX and RX antenna with Operating->Antenna selection menu. 

* '''Use decoder freq correction'''

If checked and audio decoder is used in digi mode contest, audio frequency in decoder will be added/decreased to cat frequency to get exact frequency for station. 

==Configure network==

==Network is enabled==

==Networking==

* '''Synchronize CW messages'''

Initiate CW message synchronization to all PC's in network. 

* '''Don't log QSO on this PC'''

When checked, QSO can't be added in the log at this PC. 
Instead, callsign will be just added in bandmap and QSO line will be cleared. 

* '''Software interlock'''

When checked, software interlock will be active. 
Transmit is possible only if other station with id selected during interlock activation isn't blocking TX. 
Current blocking status is visible in Radio/Ant status window. 
Interlock scenario depends on Interlock option selected. 

* '''Interlock options'''
These options are effective when software interlock is activated. 

''First one wins'' 
First station which request block goes on TX. 
Other station needs to wait for unblock message. 
''Last one wins''
Last station which request block goes on TX when unblocking request is successful. 
This means that if your station is blocked by other one, unblock request will be sent to other station. 
After receiving unblock confirmation, block request to other station will be sent. 
When block request is confirmed, your station will be switched to TX. 
''Last one wins if msg not'' 
''Last one wins if msg is'' 
These two options are same as ''Last one wins'' option, but they must meet additional condition defined in ''If msg is/not selection'' option. 
For example: 
''Last one wins if msg is'' option is selected and ''F1'' submenu option in ''If msg is/not selection'' menu is checked. 
In case that your station is blocked with F1 message from other station (which usually means that other station is calling CQ), you can request unblock,
block and switch to TX. 
Otherwise, if your station is blocked with INS message (or any other except F1), your TX request will be discarded and you have to wait for other station
to finish with TX. 
''If msg is/not selection''
F1-F7, INS, PLUS, KEYB, MAN
Message selections for conditional ''Last one wins'' interlock scenarios. 
F1-F7, INS, PLUS are standard messages. 
KEYB - TX in keyboard mode. 
MAN - manual TX request (usually with footswitch). 
* '''Use number server'''
When checked, number server will be used to determine/reserve next serial number. 
This is usable in multi op environment when serial number should be sent. 
Number reservation is made when spacebar is pressed in callsign field. 
If successful, user will be notified in main status window. 
In case that qso isn't made, number reservation is cancelled when Wipe qso option is called (ALT+W / F11 shortcuts). 

==DX cluster==

==HamCAP==

==Data files==
There are two sub-menus in this menu, Country files and Super check partials. 
 
By clicking on Country files sub-menu, following screen will appear: 
[[File:Dxl_country_files.png]]
 
 
Here you can choose which country file you will use for calculation of DXCC, CQ zone, ITU zone etc. in the contest. 
Also, you are able to update selected country file from the web. 
After clicking OK, DXLog.net will ask you to reload currently active log in order to refresh all calculations. 
 
In Super check partials you can update the software to new version of master.scp file from the web. 

==Log==

==Windows==
There are two different way how DXLog.net handles child windows opened during the contest. 
By default, all child windows are opened inside main window. 
To be able to use dual monitors, you should enable Floating windows option. 
In that case all child windows will be opened outside of main window and you can easily drag & drop them to desired position (for example on second monitor). 

==Restore windows positions==

Menu Options

2014-02-07T12:34:24Z

9a5k: /* Networking */

<big><big>Menu:Options</big></big>

==Load contest at startup==

* '''Enabled'''

If checked last opened log will be opened automatically after DXLog.net is started. 

* '''Disabled'''

If checked, it disables automatically log opening. 

==Automatic backup==

If clicked, it will open log backup window, where parameters for log backup can be chosen according to the user's preference. 

==CW==

* '''No sound'''
Text command: <code>SOUND / NOSOUND</code> 
Turns on or off CW monitor sound. 
If smart keyer (WinKey) is configured on any of interfaces, this function doesn't produce the sound. 

* '''Enable different R1/R2 speed'''

If checked, different CW speed can be set for Radio 1 and Radio 2. 

* '''Speed'''

''Decrease''
Shortcut: <code>ALT+F9</code> 
Decrease active radio CW speed by 2 WPM. 

''Decrease other''
Shortcut: <code>CTRL+ALT+F9</code> 
Decrease inactive radio CW speed by 2 WPM. 

''Increase''
Shortcut: <code>ALT+F10</code> 
Increase active radio CW speed by 2 WPM. 

''Increase other''
Shortcut: <code>CTRL+ALT+F10</code> 
Increase inactive radio CW speed by 2 WPM. 

* '''Modify standard messages'''
Text command: <code>MESSAGES / MSGS</code> 
This option is used to edit the contents of all standard F1..F2, INS, PLUS messages for RUN and S&P mode. 
 [[File:Dxl_msgs1.png]] 
Edited content is saved in currently opened DXLog.net contest file. 

 [[File:Dxl_msgs2.png]] 
Tab Options allows you to fix some additional options: 
'''$QSOB4 macro''' 
Which text will be sent $QSOB4 macro is activated in case of dupe qso 
'''Only use RUN messages''' 
DXLog.net will use only RUN messages, even if you switch mode in Search & pounce 
'''Sprint Exchange Logic''' 
This setting is applicable only for contest where Sprint Exchange Logic is enabled in config file. 
When this option is checked, during the contest, when user press INSERT key, DXLog.net will send INS message for RUN mode in case that received serial number field is empty.
Otherwise, DXLog.net will send INS message for S&P mode. 

* '''Modify additional messages'''
Shortcut: <code>ALT+C</code> 
Here you can edit additional CW messages which can be used as macro $MSG1..12. 
 [[File:Dxl_othermsgs.png]] 
Content of additional messages is saved in DXLog.net config file. 

* '''Serial number'''

Choose serial number abbreviation type when sending serial number during the contest. 
Possible options are: 
''Leading zeros'' 
When checked leading zeros are sent (for example 001 instead of 1). 
''Not abbreviated'' 
''Half abbreviated'' 
''Abbreviated'' 
''Pro'' 

* '''Shortened spaces (CT spaces)'''

When checked, shortened spaces will be activated (CT style). 

* '''Remap keys in keyboard mode'''

When checked, keyboard remapping will be active when sending CW/RTTY text in keyboard mode. 

* '''Work dupes'''

When checked, QSOB4 message wouldn't be sent if qso is a dupe. 

* '''Speed limits'''

Allows you to set cw speed limits (lowest and highest cw speed which can be selected). 

* Add spacing when stacking messages

When stacking messages during CW/RTTY contest (pressing for example F5 and F2 keys), if this option is checked one space character will be added between this each message added in buffer. 

==RTTY configuration==

==MK2R/MK2R+/u2R configuration==

==Configure interfaces==

[[File:DXL_port_config.png]]
 
DXLog.net currently supports interfaces on 8 com ports and one LPT port. 
Also, you can use PC sound board as Voice keyer during the contest. 
To use any of ports to connect to the hardware and perform some of the functions, you must enable the port by checking "Enabled" box. 
 
To use a printer port (LPT), you must enable it by checking "Enabled" box in printer port group. 
Additional data for printer port are configured by clicking Setup in printer port group. 
 
[[File:Dxl_printer_port_config.png]]
 
 
In serial port section, you can select any COM port in range COM1 to COM20. 
The only restriction is that you can't select same COM port only on one of the interfaces. 
In each serial port interface you can select appropriate device type in combo box in same row. 
Each of devices have some additional parameters available for setting. You can change them by clicking on Setup button for each interface. 

==Interface specific options==
* '''Allow different TX/RX antenna'''

If checked this option allows different selection for TX and RX antenna with Operating->Antenna selection menu. 

* '''Use decoder freq correction'''

If checked and audio decoder is used in digi mode contest, audio frequency in decoder will be added/decreased to cat frequency to get exact frequency for station. 

==Configure network==

==Network is enabled==

==Networking==

* '''Synchronize CW messages'''

Initiate CW message synchronization to all PC's in network. 

* '''Don't log QSO on this PC'''

When checked, QSO can't be added in the log at this PC. 
Instead, callsign will be just added in bandmap and QSO line will be cleared. 

* '''Software interlock'''

When checked, software interlock will be active. 
Transmit is possible only if other station with id selected during interlock activation isn't blocking TX. 
Current blocking status is visible in Radio/Ant status window. 
Interlock scenario depends on Interlock option selected. 

* '''Interlock options'''
These options are effective when software interlock is activated. 

''First one wins'' 
First station which request block goes on TX. 
Other station needs to wait for unblock message. 
''Last one wins''
Last station which request block goes on TX when unblocking request is successful. 
This means that if your station is blocked by other one, unblock request will be sent to other station. 
After receiving unblock confirmation, block request to other station will be sent. 
When block request is confirmed, your station will be switched to TX. 
''Last one wins if msg not'' 
''Last one wins if msg is'' 
These two options are same as ''Last one wins'' option, but they must meet additional condition defined in ''If msg is/not selection'' option. 
For example: 
''Last one wins if msg is'' option is selected and ''F1'' submenu option in ''If msg is/not selection'' menu is checked. 
In case that your station is blocked with F1 message from other station (which usually means that other station is calling CQ), you can request unblock,
block and switch to TX. 
Otherwise, if your station is blocked with INS message (or any other except F1), your TX request will be discarded and you have to wait for other station
to finish with TX. 
''If msg is/not selection''
F1-F7, INS, PLUS, KEYB, MAN
Message selections for conditional ''Last one wins'' interlock scenarios. 
F1-F7, INS, PLUS are standard messages. 
KEYB - TX in keyboard mode. 
MAN - manual TX request (usually with footswitch). 
* '''Use number server'''
When checked, number server will be used to determine/reserve next serial number. 
This is usable in multi op environment when serial number should be sent. 
Number reservation is made when spacebar is pressed in callsign field. 
If successful, user will be notified in main status window. 
In case that qso isn't made, number reservation is cancelled when Wipe qso option is called (ALT+W / F11 shortcuts). 

==DX cluster==

==Data files==
There are two sub-menus in this menu, Country files and Super check partials. 
 
By clicking on Country files sub-menu, following screen will appear: 
[[File:Dxl_country_files.png]]
 
 
Here you can choose which country file you will use for calculation of DXCC, CQ zone, ITU zone etc. in the contest. 
Also, you are able to update selected country file from the web. 
After clicking OK, DXLog.net will ask you to reload currently active log in order to refresh all calculations. 
 
In Super check partials you can update the software to new version of master.scp file from the web. 

==Log==

==Windows==
There are two different way how DXLog.net handles child windows opened during the contest. 
By default, all child windows are opened inside main window. 
To be able to use dual monitors, you should enable Floating windows option. 
In that case all child windows will be opened outside of main window and you can easily drag & drop them to desired position (for example on second monitor). 

==Restore windows positions==

Menu Options

2014-02-07T12:34:08Z

9a5k: /* Networking */

<big><big>Menu:Options</big></big>

==Load contest at startup==

* '''Enabled'''

If checked last opened log will be opened automatically after DXLog.net is started. 

* '''Disabled'''

If checked, it disables automatically log opening. 

==Automatic backup==

If clicked, it will open log backup window, where parameters for log backup can be chosen according to the user's preference. 

==CW==

* '''No sound'''
Text command: <code>SOUND / NOSOUND</code> 
Turns on or off CW monitor sound. 
If smart keyer (WinKey) is configured on any of interfaces, this function doesn't produce the sound. 

* '''Enable different R1/R2 speed'''

If checked, different CW speed can be set for Radio 1 and Radio 2. 

* '''Speed'''

''Decrease''
Shortcut: <code>ALT+F9</code> 
Decrease active radio CW speed by 2 WPM. 

''Decrease other''
Shortcut: <code>CTRL+ALT+F9</code> 
Decrease inactive radio CW speed by 2 WPM. 

''Increase''
Shortcut: <code>ALT+F10</code> 
Increase active radio CW speed by 2 WPM. 

''Increase other''
Shortcut: <code>CTRL+ALT+F10</code> 
Increase inactive radio CW speed by 2 WPM. 

* '''Modify standard messages'''
Text command: <code>MESSAGES / MSGS</code> 
This option is used to edit the contents of all standard F1..F2, INS, PLUS messages for RUN and S&P mode. 
 [[File:Dxl_msgs1.png]] 
Edited content is saved in currently opened DXLog.net contest file. 

 [[File:Dxl_msgs2.png]] 
Tab Options allows you to fix some additional options: 
'''$QSOB4 macro''' 
Which text will be sent $QSOB4 macro is activated in case of dupe qso 
'''Only use RUN messages''' 
DXLog.net will use only RUN messages, even if you switch mode in Search & pounce 
'''Sprint Exchange Logic''' 
This setting is applicable only for contest where Sprint Exchange Logic is enabled in config file. 
When this option is checked, during the contest, when user press INSERT key, DXLog.net will send INS message for RUN mode in case that received serial number field is empty.
Otherwise, DXLog.net will send INS message for S&P mode. 

* '''Modify additional messages'''
Shortcut: <code>ALT+C</code> 
Here you can edit additional CW messages which can be used as macro $MSG1..12. 
 [[File:Dxl_othermsgs.png]] 
Content of additional messages is saved in DXLog.net config file. 

* '''Serial number'''

Choose serial number abbreviation type when sending serial number during the contest. 
Possible options are: 
''Leading zeros'' 
When checked leading zeros are sent (for example 001 instead of 1). 
''Not abbreviated'' 
''Half abbreviated'' 
''Abbreviated'' 
''Pro'' 

* '''Shortened spaces (CT spaces)'''

When checked, shortened spaces will be activated (CT style). 

* '''Remap keys in keyboard mode'''

When checked, keyboard remapping will be active when sending CW/RTTY text in keyboard mode. 

* '''Work dupes'''

When checked, QSOB4 message wouldn't be sent if qso is a dupe. 

* '''Speed limits'''

Allows you to set cw speed limits (lowest and highest cw speed which can be selected). 

* Add spacing when stacking messages

When stacking messages during CW/RTTY contest (pressing for example F5 and F2 keys), if this option is checked one space character will be added between this each message added in buffer. 

==RTTY configuration==

==MK2R/MK2R+/u2R configuration==

==Configure interfaces==

[[File:DXL_port_config.png]]
 
DXLog.net currently supports interfaces on 8 com ports and one LPT port. 
Also, you can use PC sound board as Voice keyer during the contest. 
To use any of ports to connect to the hardware and perform some of the functions, you must enable the port by checking "Enabled" box. 
 
To use a printer port (LPT), you must enable it by checking "Enabled" box in printer port group. 
Additional data for printer port are configured by clicking Setup in printer port group. 
 
[[File:Dxl_printer_port_config.png]]
 
 
In serial port section, you can select any COM port in range COM1 to COM20. 
The only restriction is that you can't select same COM port only on one of the interfaces. 
In each serial port interface you can select appropriate device type in combo box in same row. 
Each of devices have some additional parameters available for setting. You can change them by clicking on Setup button for each interface. 

==Interface specific options==
* '''Allow different TX/RX antenna'''

If checked this option allows different selection for TX and RX antenna with Operating->Antenna selection menu. 

* '''Use decoder freq correction'''

If checked and audio decoder is used in digi mode contest, audio frequency in decoder will be added/decreased to cat frequency to get exact frequency for station. 

==Configure network==

==Network is enabled==

==Networking==

* '''Synchronize CW messages'''

Initiate CW message synchronization to all PC's in network. 

* '''Don't log QSO on this PC'''

When checked, QSO can't be added in the log at this PC. 
Instead, callsign will be just added in bandmap and QSO line will be cleared. 

* '''Software interlock'''

When checked, software interlock will be active. 
Transmit is possible only if other station with id selected during interlock activation isn't blocking TX. 
Current blocking status is visible in Radio/Ant status window. 
Interlock scenario depends on Interlock option selected. 

* '''Interlock options'''

These options are effective when software interlock is activated. 
''First one wins'' 
First station which request block goes on TX. 
Other station needs to wait for unblock message. 
''Last one wins''
Last station which request block goes on TX when unblocking request is successful. 
This means that if your station is blocked by other one, unblock request will be sent to other station. 
After receiving unblock confirmation, block request to other station will be sent. 
When block request is confirmed, your station will be switched to TX. 
''Last one wins if msg not'' 
''Last one wins if msg is'' 
These two options are same as ''Last one wins'' option, but they must meet additional condition defined in ''If msg is/not selection'' option. 
For example: 
''Last one wins if msg is'' option is selected and ''F1'' submenu option in ''If msg is/not selection'' menu is checked. 
In case that your station is blocked with F1 message from other station (which usually means that other station is calling CQ), you can request unblock,
block and switch to TX. 
Otherwise, if your station is blocked with INS message (or any other except F1), your TX request will be discarded and you have to wait for other station
to finish with TX. 
''If msg is/not selection''
F1-F7, INS, PLUS, KEYB, MAN
Message selections for conditional ''Last one wins'' interlock scenarios. 
F1-F7, INS, PLUS are standard messages. 
KEYB - TX in keyboard mode. 
MAN - manual TX request (usually with footswitch). 
* '''Use number server'''
When checked, number server will be used to determine/reserve next serial number. 
This is usable in multi op environment when serial number should be sent. 
Number reservation is made when spacebar is pressed in callsign field. 
If successful, user will be notified in main status window. 
In case that qso isn't made, number reservation is cancelled when Wipe qso option is called (ALT+W / F11 shortcuts). 

==DX cluster==

==Data files==
There are two sub-menus in this menu, Country files and Super check partials. 
 
By clicking on Country files sub-menu, following screen will appear: 
[[File:Dxl_country_files.png]]
 
 
Here you can choose which country file you will use for calculation of DXCC, CQ zone, ITU zone etc. in the contest. 
Also, you are able to update selected country file from the web. 
After clicking OK, DXLog.net will ask you to reload currently active log in order to refresh all calculations. 
 
In Super check partials you can update the software to new version of master.scp file from the web. 

==Log==

==Windows==
There are two different way how DXLog.net handles child windows opened during the contest. 
By default, all child windows are opened inside main window. 
To be able to use dual monitors, you should enable Floating windows option. 
In that case all child windows will be opened outside of main window and you can easily drag & drop them to desired position (for example on second monitor). 

==Restore windows positions==

Menu Options

2014-02-07T12:33:45Z

9a5k:

<big><big>Menu:Options</big></big>

==Load contest at startup==

* '''Enabled'''

If checked last opened log will be opened automatically after DXLog.net is started. 

* '''Disabled'''

If checked, it disables automatically log opening. 

==Automatic backup==

If clicked, it will open log backup window, where parameters for log backup can be chosen according to the user's preference. 

==CW==

* '''No sound'''
Text command: <code>SOUND / NOSOUND</code> 
Turns on or off CW monitor sound. 
If smart keyer (WinKey) is configured on any of interfaces, this function doesn't produce the sound. 

* '''Enable different R1/R2 speed'''

If checked, different CW speed can be set for Radio 1 and Radio 2. 

* '''Speed'''

''Decrease''
Shortcut: <code>ALT+F9</code> 
Decrease active radio CW speed by 2 WPM. 

''Decrease other''
Shortcut: <code>CTRL+ALT+F9</code> 
Decrease inactive radio CW speed by 2 WPM. 

''Increase''
Shortcut: <code>ALT+F10</code> 
Increase active radio CW speed by 2 WPM. 

''Increase other''
Shortcut: <code>CTRL+ALT+F10</code> 
Increase inactive radio CW speed by 2 WPM. 

* '''Modify standard messages'''
Text command: <code>MESSAGES / MSGS</code> 
This option is used to edit the contents of all standard F1..F2, INS, PLUS messages for RUN and S&P mode. 
 [[File:Dxl_msgs1.png]] 
Edited content is saved in currently opened DXLog.net contest file. 

 [[File:Dxl_msgs2.png]] 
Tab Options allows you to fix some additional options: 
'''$QSOB4 macro''' 
Which text will be sent $QSOB4 macro is activated in case of dupe qso 
'''Only use RUN messages''' 
DXLog.net will use only RUN messages, even if you switch mode in Search & pounce 
'''Sprint Exchange Logic''' 
This setting is applicable only for contest where Sprint Exchange Logic is enabled in config file. 
When this option is checked, during the contest, when user press INSERT key, DXLog.net will send INS message for RUN mode in case that received serial number field is empty.
Otherwise, DXLog.net will send INS message for S&P mode. 

* '''Modify additional messages'''
Shortcut: <code>ALT+C</code> 
Here you can edit additional CW messages which can be used as macro $MSG1..12. 
 [[File:Dxl_othermsgs.png]] 
Content of additional messages is saved in DXLog.net config file. 

* '''Serial number'''

Choose serial number abbreviation type when sending serial number during the contest. 
Possible options are: 
''Leading zeros'' 
When checked leading zeros are sent (for example 001 instead of 1). 
''Not abbreviated'' 
''Half abbreviated'' 
''Abbreviated'' 
''Pro'' 

* '''Shortened spaces (CT spaces)'''

When checked, shortened spaces will be activated (CT style). 

* '''Remap keys in keyboard mode'''

When checked, keyboard remapping will be active when sending CW/RTTY text in keyboard mode. 

* '''Work dupes'''

When checked, QSOB4 message wouldn't be sent if qso is a dupe. 

* '''Speed limits'''

Allows you to set cw speed limits (lowest and highest cw speed which can be selected). 

* Add spacing when stacking messages

When stacking messages during CW/RTTY contest (pressing for example F5 and F2 keys), if this option is checked one space character will be added between this each message added in buffer. 

==RTTY configuration==

==MK2R/MK2R+/u2R configuration==

==Configure interfaces==

[[File:DXL_port_config.png]]
 
DXLog.net currently supports interfaces on 8 com ports and one LPT port. 
Also, you can use PC sound board as Voice keyer during the contest. 
To use any of ports to connect to the hardware and perform some of the functions, you must enable the port by checking "Enabled" box. 
 
To use a printer port (LPT), you must enable it by checking "Enabled" box in printer port group. 
Additional data for printer port are configured by clicking Setup in printer port group. 
 
[[File:Dxl_printer_port_config.png]]
 
 
In serial port section, you can select any COM port in range COM1 to COM20. 
The only restriction is that you can't select same COM port only on one of the interfaces. 
In each serial port interface you can select appropriate device type in combo box in same row. 
Each of devices have some additional parameters available for setting. You can change them by clicking on Setup button for each interface. 

==Interface specific options==
* '''Allow different TX/RX antenna'''

If checked this option allows different selection for TX and RX antenna with Operating->Antenna selection menu. 

* '''Use decoder freq correction'''

If checked and audio decoder is used in digi mode contest, audio frequency in decoder will be added/decreased to cat frequency to get exact frequency for station. 

==Configure network==

==Network is enabled==

==Networking==

* '''Synchronize CW messages'''

Initiate CW message synchronization to all PC's in network. 

* '''Don't log QSO on this PC'''

When checked, QSO can't be added in the log at this PC. 
Instead, callsign will be just added in bandmap and QSO line will be cleared. 

* '''Software interlock'''

When checked, software interlock will be active. 
Transmit is possible only if other station with id selected during interlock activation isn't blocking TX. 
Current blocking status is visible in Radio/Ant status window. 
Interlock scenario depends on Interlock option selected. 

* '''Interlock options'''

These options are effective when software interlock is activated. 

''First one wins'' 
First station which request block goes on TX. 
Other station needs to wait for unblock message. 
''Last one wins''
Last station which request block goes on TX when unblocking request is successful. 
This means that if your station is blocked by other one, unblock request will be sent to other station. 
After receiving unblock confirmation, block request to other station will be sent. 
When block request is confirmed, your station will be switched to TX. 
''Last one wins if msg not'' 
''Last one wins if msg is'' 
These two options are same as ''Last one wins'' option, but they must meet additional condition defined in ''If msg is/not selection'' option. 
For example: 
''Last one wins if msg is'' option is selected and ''F1'' submenu option in ''If msg is/not selection'' menu is checked. 
In case that your station is blocked with F1 message from other station (which usually means that other station is calling CQ), you can request unblock,
block and switch to TX. 
Otherwise, if your station is blocked with INS message (or any other except F1), your TX request will be discarded and you have to wait for other station
to finish with TX. 
''If msg is/not selection''
F1-F7, INS, PLUS, KEYB, MAN
Message selections for conditional ''Last one wins'' interlock scenarios. 
F1-F7, INS, PLUS are standard messages. 
KEYB - TX in keyboard mode. 
MAN - manual TX request (usually with footswitch). 
* '''Use number server'''
When checked, number server will be used to determine/reserve next serial number. 
This is usable in multi op environment when serial number should be sent. 
Number reservation is made when spacebar is pressed in callsign field. 
If successful, user will be notified in main status window. 
In case that qso isn't made, number reservation is cancelled when Wipe qso option is called (ALT+W / F11 shortcuts). 

==DX cluster==

==Data files==
There are two sub-menus in this menu, Country files and Super check partials. 
 
By clicking on Country files sub-menu, following screen will appear: 
[[File:Dxl_country_files.png]]
 
 
Here you can choose which country file you will use for calculation of DXCC, CQ zone, ITU zone etc. in the contest. 
Also, you are able to update selected country file from the web. 
After clicking OK, DXLog.net will ask you to reload currently active log in order to refresh all calculations. 
 
In Super check partials you can update the software to new version of master.scp file from the web. 

==Log==

==Windows==
There are two different way how DXLog.net handles child windows opened during the contest. 
By default, all child windows are opened inside main window. 
To be able to use dual monitors, you should enable Floating windows option. 
In that case all child windows will be opened outside of main window and you can easily drag & drop them to desired position (for example on second monitor). 

==Restore windows positions==

Menu Options

2014-02-07T12:04:57Z

9a5k:

Menu Options

2014-02-07T12:02:06Z

9a5k:

Menu Options

2014-02-07T11:56:46Z

9a5k: /* CW */

Menu Options

2014-02-07T11:53:22Z

9a5k: /* CW */

Menu Tools

2014-02-07T11:51:40Z

9a5k: /* Repeat loop */

<big><big>Menu:Tools</big></big>

==Repeat loop==

Text command: <code>RPT / NORPT</code> 
Turns on or off CQ repeat loop function. 
After pressing F1 (CQ memory) and when message is transmitted, loop will wait for n sec and if there isn't any key pressed in qso callsign field (or esc key), after n sec period is exceeded, content of F1 memory will be transmitted again automatically. 
Repeat loop status function is visible in Rate window, if it is activated. 
Also, if during transmitting of message any key is pressed in callsign qso filed (or esc key is pressed), transmit stops immediately and repeat loop is deactivated. It will be automatically activated again when F1 key is pressed. 

==Redefine keyboard keys==
==Data entry==
* '''Exchange guessing'''
Pressing the space bar
Automatically
After timeout
* '''Enable ESM mode'''
* '''ESM mode change focus on LOGGEDCALL macro'''
* '''Enable Run/SP switching'''
* '''Enable Automatic Run/SP selection'''
* '''Enable CW Cut Numbers Translation'''
==Message editors==
* '''Enable SO2R scenarion on the fly editor'''
* '''On the fly editor focus on scenario line'''

Menu Options

2014-02-07T11:51:19Z

9a5k: /* CW */

Menu Options

2014-02-07T11:49:50Z

9a5k: /* CW */

Menu Options

2014-02-07T11:48:50Z

9a5k: /* CW */