Difference between revisions of "Getting started"

From DXLog.net
Jump to navigation Jump to search
(Voice memory playback)
(The bandmap and other windows)
 
(181 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
==Introduction and plea==
 +
 +
DXLog is a very powerful contesting software with enormous flexibility.
 +
 +
Unfortunately this comes with complexity and a significant learning curve for new users.
 +
 +
This wiki is written by DXLog experts who may be somewhat blind of the needs of a new user.
 +
 +
If you have ideas for improvement of this section, please share them with the development<br>
 +
team via the support reflector.
 +
 
==User interface==
 
==User interface==
  
Line 6: Line 17:
 
should very rarely have to take your hands off the keyboard.
 
should very rarely have to take your hands off the keyboard.
  
Contrary to e.g. N1MM Logger+, DXLog's default setting is to use a main window, a "desktop". <br>
+
Contrary to e.g., N1MM Logger+, DXLog's default setting is to use a single window, a "desktop". <br>
 
There are many benefits with this, for instance the fact that you can rapidly switch between <br>
 
There are many benefits with this, for instance the fact that you can rapidly switch between <br>
 
the logger and another application, such as a web browser, with <code>[Alt][Tab]</code>.
 
the logger and another application, such as a web browser, with <code>[Alt][Tab]</code>.
Line 25: Line 36:
  
  
DXLog shares many characteristics with other loggers but for those used to N1MM Logger+, <br>
+
DXLog shares many characteristics with other loggers but for those used to e.g. N1MM Logger+,<br>
there are two noteworthy differences.
+
there are two very important differences.
  
 
* The log and the entry lines are connected. Using the arrow keys, moving up past the top  
 
* The log and the entry lines are connected. Using the arrow keys, moving up past the top  
Line 33: Line 44:
 
* You can modify a logged QSO but not delete it. In the spirit of old school contest logging,  
 
* You can modify a logged QSO but not delete it. In the spirit of old school contest logging,  
 
: you can only mark it invalid. This is done by navigating to the QSO and pressing <code>[Ctrl][X]</code>.
 
: you can only mark it invalid. This is done by navigating to the QSO and pressing <code>[Ctrl][X]</code>.
 +
: The "old school" method of changing the callsign of the QSO to your own is also supported.
 +
 +
* The numbering and use of the standard messages is different.
 +
 +
The entry line is divided into fields, most of them are read-only like QSO number, band, mode, time, etc.<br>
 +
Each contest has at least callsign and one exchange field. Some contests have several exchange fields.<br>
 +
You move between major fields by pressing <code>[Space]</code> and between all fields with <code>[Tab]</code>.<br>
 +
RS/RST is not a major field.
 +
 +
The callsign is checked for validity using this regular expression:
 +
 +
<tt><nowiki>^((([A-Z1-9]+0?\/)?[1-9]?[A-Z]{1,3}[0-9]+[A-Z]+(\/[A-Z0-9]+)?(\/[AMP]{1,2})?)|RAEM|EA0)$</nowiki></tt>
 +
 +
When you have completed your entry, you typically log the QSO using either <code>[Enter]</code> or <code>[+]</code>.
 +
 +
The location and visibility of the log and entry line column headers can be controlled with <code>Options|Log|Headers</code>.
 +
 +
Note that the rightmost ''Stn'' station type column becomes visible only when activating networking or selecting<br>
 +
an operating technique other than SO1R.
  
 
==Creating a log file==
 
==Creating a log file==
Line 44: Line 74:
 
standard file permissions for this. This means that some types of shared or synchronized<br>  
 
standard file permissions for this. This means that some types of shared or synchronized<br>  
 
folders, or folders in virtualized environments, may not work for log file storage.
 
folders, or folders in virtualized environments, may not work for log file storage.
 +
 +
'''Unlike most other loggers, DXLog is compatible with Microsoft OneDrive.'''
  
  
Line 66: Line 98:
 
for instance run a weekly test in which you want a particular layout or color scheme, it is a good idea <br>
 
for instance run a weekly test in which you want a particular layout or color scheme, it is a good idea <br>
 
to open the previous' weeks log before creating a new one.
 
to open the previous' weeks log before creating a new one.
 +
 +
Also note that messages are stored on a per-contest basis. This means that when creating a new log, the<br>
 +
messages from the previous, same contest will be used. If there is none, the contest's default messages will<br>
 +
be used. Since some contests have messages based on location or participation status, this is important<br>
 +
to be aware of.
  
 
You will find much more information in the [[Configuration#Contest_configuration|contest configuration section]].
 
You will find much more information in the [[Configuration#Contest_configuration|contest configuration section]].
Line 76: Line 113:
  
  
[[File:Portconfig2410.jpg]]
+
[[File:Portconfig.png]]
  
  
Line 92: Line 129:
 
==Databases==
 
==Databases==
  
The next step is to make sure two important data bases are up to date; the country data base <tt>CTY.DAT</tt> <br>
+
The next step is to make sure two important data bases are up to date; the country data base <tt>CTY.DAT</tt><br>
and the callsign database <tt>MASTER.SCP</tt>.
+
(and its siblings) and the callsign database <tt>MASTER.SCP</tt>.
  
The menu <code>Options|Data files|Country files</code> opens a window that allows you to update the three <br>
+
The menu <code>Options|Data files|Country files</code> opens a window that allows you to update three <br>
alternative country databases. Chose one at the time and click ''Download''. Normally the most detailed, <br>
+
alternative country databases. Chose one at the time and click ''Download''. Normally the most detailed,<br>
 
<tt>CTY_WT_MOD.DAT</tt> is the recommended one to use.
 
<tt>CTY_WT_MOD.DAT</tt> is the recommended one to use.
  
Line 108: Line 145:
 
The next step is to chose your operating method, ''Technique'' in DXLog terminology.  
 
The next step is to chose your operating method, ''Technique'' in DXLog terminology.  
  
Each technique supports two operating "states"; ''Run'' and ''Search & Pounce'' or ''S&P''.
+
DXLog supports four different techniques; SO1R, SO2V, SO2R, and SO2R Advanced.
 +
 
 +
SO1R means Single Operator, One Radio. SO2R means Single Operator, Two Radios. SO2V means Single Operator,<br>
 +
Two VFO but in practice this is normally also Two Receiviers. In a multi-operator setting you typically use<br>
 +
SO1R but an advanced operator can also use SO2V.
 +
 
 +
The menu <code>Operating|Technique</code> let you choose between SO1R, SO2R, Advanced SO2R and SO2V.
 +
 
 +
Each technique supports two operating "states"; ''Run'' and ''Search & Pounce'' (or ''S&P'' for short).
 +
 
 +
Run means you call CQ and work calling stations. S&P means you search for stations and work them by calling them.
 +
 
 +
Each state has a separate set of predefined messages (see below) and ESM behavior (also see below).<br>
 +
The keyboard shortcut to switch between the states is <code>[Ctrl][Tab]</code>.
 +
 
 +
There are also some options for forcing an automatic change, such as<br>
 +
<code>Tools|Data entry|F1 returns to Run always</code> and <code>Tools|Enable automatic Run/S&P selection</code>.
 +
 
 +
===SO1R===
 +
 
 +
SO1R is the most basic and it is the method you use in a single operator setting using a single<br>
 +
receiver radio or in multi-station setting.
  
Run means you call CQ. S&P means you call other stations. Each state has a set of unique <br>
+
When using this technique, you have a single entry line and one radio with one receiver.<br>
predefined messages (see below) and ESM behavior (also see below). The keyboard shortcut to <br>
+
The band map shows the band map for the currently selected VFO.<br>
switch between the states is <code>[Ctrl][Tab]</code>. There is also some optional mechanics<br>
+
 
that force an automatic change, such as the option <code>Tools|Data entry|F1 returns to Run always</code> and <br>
+
In the top of the bandmap the frequencies of VFO A and VFO B are shown in boxes.<br>
<code>Tools|Enable automatic Run/S&P selection</code>.
+
The boxes are clickable and you can also switch between the VFO using <code>[Keypad *]</code>.<br>
 +
If you want to make a rapid excursion to work e.g. a multiplier, you can always jump back to<br>
 +
your Run frequency with <code>[Alt][F4]</code>.<br>
 +
 
 +
SO1R only works for Radio 1 in the <code>Options|Configure interfaces</code> panel.
  
In the sub menu <code>Operating|Technique</code> you can chose between SO1R, SO2R, Advanced SO2R and SO2V.
 
  
'''SO1R'''
 
: is the most basic and it is also the method you typically use in a single operator setting using a radio with only one
 
: receiver or in multioperator/multi-station setting.
 
: With this technique, you have a single entry line and one radio with one receiver.
 
: The band map shows the band map for the currently active VFO.
 
: In the top of the bandmap the frequencies of VFO A and VFO B are shown in boxes. The boxes are clickable and you can
 
: also switch between the VFO using <code>[Keypad *]</code>. If you want to make a rapid excursion to work
 
: e.g. a multiplier, you can always jump back to your Run frequency with <code>[Alt][F4]</code>.
 
: SO1R only works for Radio 1 in the <code>Options|Configure interfaces</code> panel.
 
 
:[[image:so1r-cqww.png]]
 
:[[image:so1r-cqww.png]]
  
  
'''SO2R and Advanced SO2R'''
+
===SO2R and Advanced SO2R===
: uses two radios which operate in parallel, each having a separate entry line. (Although you never transmit  
+
 
: with more than one at any time.)  
+
uses two radios which operate in parallel, each having a separate entry line. (Although you never<br>
: In "standard" SO2R you operate by manually switching your "focus" between the two radios.  
+
transmit with more than one at any time.)
: This is done using the up and down arrow keys or <code>[Keypad *]</code>.
+
 
: SO2R also supports external audio control by a large range of SO2R controllers such as all [https://www.microham.com/ microHAM]  
+
In "standard" SO2R you operate by manually switching your "focus" between the two radios.<br>
: keyers/controllers or devices such as the [http://www.k1xm.org/SO2R/ YCCC SO2R box] or [https://nn1c.org/so2r/ SO2R mini].
+
This is done using the up and down arrow keys or <code>[Keypad *]</code>.<br>
: In Advanced SO2R the focus shifting is typically scripted, using up to eight different "scenarios" for different  
+
 
: situations such as hunting for multipliers, alternating CQ, or managing a large pile-up.  
+
SO2R also supports external audio control by a large range of SO2R controllers such as all [https://www.microham.com/ microHAM]<br>
: This feature is particularly appreciated by advanced contesters.
+
keyers/controllers or devices such as the [http://www.k1xm.org/SO2R/ YCCC SO2R box] or [https://nn1c.org/so2r/ SO2R mini].
: SO2R requires two radios (Radio 1 and Radio 2) configured in the <code>Options|Configure interfaces</code> panel.
+
 
: [[image:so2r-cqww.png]]
+
In Advanced SO2R the focus shifting is typically scripted, using up to eight different "scenarios" for different<br>
 +
situations such as hunting for multipliers, alternating CQ, or managing a large pile-up.
 +
 
 +
More information can be found in the [[Menu_Operating#Advanced_SO2R|Advanced SO2R section]].<br>
 +
This feature is particularly appreciated by advanced contesters.<br>
 +
 
 +
SO2R requires two radios (Radio 1 and Radio 2) configured in the <code>Options|Configure interfaces</code> panel.<br>
 +
 
 +
'''Important:''' If running a contest where the exchange is a serial number, you must use a number server and number<br>
 +
reservation to secure that the transmitted and logged serial number are the same. You will find more<br>
 +
information about this in the [[Additional_Information#Using_a_number_server|using a number server section]].<br>
 +
 
 +
 
 +
[[image:so2r-cqww.png]]
 +
 
 +
===SO2V===
 +
 
 +
At a first glance, SO2V looks similar to SO2R but uses only a single radio (two "R" entry lines).<br>
 +
This method is primarily intended for dual receiver radios (such as Elecraft K4, ICOM IC-7610, or Yaesu FTDX101D)<br>
 +
but offer some usability and efficiency benefits also for single receiver radios.<br>
 +
 
 +
Like in SO2R, mastering having one receiver in each ear will maximize your efficiency.<br>
 +
The logical model of SO2V is two radios with a shared transmitter.<br>
 +
 
 +
Unlike SO2R, the two radios are typically on the same band.
  
 +
Split band SO2V puts very challenging requirements on antenna and amplifier band switching speed<br>
 +
and requires a very careful station design. DXLog offers no protection against e.g., hot switching
 +
in such a situation.
  
'''SO2V'''
+
The most common way to operate SO2V is to switch focus between the two "radios" the same way<br>
: looks similar to SO2R at first sight but uses only a single radio (two "R" entry lines).
+
as in "standard" SO2R; using the arrow keys or <code>[Keypad *]</code>. However, dual keyboards may also be used.
: This method is primarily intended for dual receiver radios (such as Elecraft K3S, ICOM IC-7610, or Yaesu FTDX101D)
 
: but offer some usability and efficiency benefits also for single receiver radios.
 
: Like in SO2R, mastering having one receiver in each ear will maximize your efficiency.
 
: The logical model of SO2V is two radios with a shared transmitter.
 
: Unlike SO2R, the two radios are typically on the same band. This is because
 
: antenna and power amplifier band switching may have a significant response time.
 
: The most common way to operate SO2V is to switch focus between the two "radios" the same way  
 
: as in standard SO2R; using the arrow keys or <code>[Keypad *]</code>. However, dual keyboards is also supported.
 
: It is common practice to run (i.e. call CQ) on the main VFO (left ear) and S&P on the sub VFO (right ear).
 
: One of the reasons for this is tradition but another is that RIT is only supported on the main VFO on many radios.
 
: More information about operating SO2V can be found in the [[Menu_Operating#SO2V|SO2V menu item section]].
 
: On selected radios (such as more advanced ICOM radios), automatic VFO knob focus and sub receiver control
 
: is supported. (More details can be found in the [[Radios|supported radios section]].)
 
: It is also possible to use SO2V with single-receiver radios. There is a benefit in having separate band<br>
 
: map for each VFO and being able to rapidly switch between VFO A and B.
 
: SO2V only works for Radio 1 in the <code>Options|Configure interfaces</code> panel.
 
: [[image:so2v-cqww.png]]
 
  
 +
It is common practice to run (i.e. call CQ) on the main VFO (left ear) and do S&P on the sub VFO (right ear).<br>
 +
One of the reasons for this is tradition but another is that RIT is only supported on the main VFO on many radios.
  
More information about the four possible techniques can be found in the [[Menu_Operating#Technique|technique section]].
+
More information about operating SO2V can be found in the [[Menu_Operating#SO2V|SO2V menu item section]].<br>
 +
On selected radios (such as more advanced ICOM radios), automatic VFO knob focus and sub receiver control<br>
 +
is supported. (C.f. the [[Radios|supported radios section]].)<br>
 +
 
 +
'''Important:''' RTTY SO2V requires the use of FSK together with a radio controller that offers two<br>
 +
FSK keying COM-ports for the same radio, such as the microHAM series of keyers.
 +
 
 +
It is also possible to use SO2V with single-receiver radios. There is a benefit in having separate band<br>
 +
map for each VFO and being able to rapidly switch between VFO A and B.
 +
 
 +
SO2V only works for Radio 1 in the <code>Options|Configure interfaces</code> panel.
 +
 
 +
 
 +
[[image:so2v-cqww.png]]
 +
 
 +
 
 +
More information about the four possible techniques can be found in the [[Menu_Operating#Technique|operating technique section]].
  
 
==Standard messages==
 
==Standard messages==
  
One of the most fundamental features of a contest logger for CW or digital modes is the ability <br>
+
A fundamental feature of a contest logger is the ability to send predefined messages.
to send predefined messages containing e.g. a correct serial number.  
+
 
 +
DXLog has two types of predefined messages; the Standard messages and the [[Menu_Options#Modify_additional_messages|Additional messages]].
 +
 
 +
The standard messages contain two sets; one for RUN and one for Search & Pounce.
 +
 
 +
You reach the configuration panel for the standard messages with <code>Options|CW/Digi|Modify standard messages</code> or the text command <tt>MSGS</tt>.
 +
 
 +
Each standard message is associated with a function key; <code>[F1]</code> to <code>[F7]</code>, <code>[Insert]</code> and <code>[+]</code>.<br>
 +
In this wiki, they are also referred by these names.
 +
 
 +
The use of each message follow a long standing tradition in contest loggers and since functions in DXLog (e.g., ESM and DVK) assume<br>
 +
the messages are used this way, <u>do not use them differently unless you know exactly what you do</u>.
 +
 
 +
{|class="wikitable"
 +
|+style="text-align:Left;"|Contest loggers' tradition
 +
|-
 +
| Message
 +
| Use
 +
|-
 +
| F1
 +
| CQ (RUN) or own call (S&P)
 +
|-
 +
| F2
 +
| RST and contest exchange
 +
|-
 +
| F3
 +
| Contest exchange
 +
|-
 +
| F4
 +
| Own callsign
 +
|-
 +
| F5
 +
| Other station's callsign
 +
|-
 +
| F6
 +
| Request for repetition
 +
|-
 +
| F7
 +
| Query (CW) or QRZ (digital)
 +
|-
 +
| Insert
 +
| Make QSO. Conclude QSO in S&P.
 +
|-
 +
| Plus
 +
| Confirm QSO. Conclude QSO in RUN.  
 +
|}
  
DXLog has two sets of such messages; one for RUN and one for Search & Pounce. <br>
+
When creating a new log in DXLog, the standard messages are automatically populated.
You reach the set up panel for the messages with <code>Options|CW/Digi|Modify standard messages</code> <br>
 
or the text command <tt>MSGS</tt>.  
 
  
Each message is associated to a function key; <code>[F1]</code> to <code>[F7]</code>, <code>[Insert]</code> and <code>[+]</code>.
+
Below is one example.  
  
  
Line 183: Line 306:
  
 
The messages are composed by regular letters and numbers, special characters, and macro commands. <br>
 
The messages are composed by regular letters and numbers, special characters, and macro commands. <br>
Macros always start with a dollar sign, e.g. <tt>$RST</tt>, <tt>$LOGGEDCALL</tt>, or <tt>$CORRECT</tt>.<br>
+
Macros always start with a dollar sign, e.g., <tt>$RST</tt>, <tt>$LOGGEDCALL</tt>, or <tt>$CORRECT</tt>.<br>
Special characters are mainly used to control the CW keying, e.g. <nowiki>^</nowiki> means a half word space <br>
+
Special characters are mainly used to control the CW keying, e.g., <nowiki>^</nowiki> means a half word space <br>
and <nowiki>&</nowiki> removes the character space to allow the creation of prosigns.
+
and <nowiki>+</nowiki> means an increase of the CW speed by 4WPM.
 +
 
 +
A full list can be found in the [[Configuration#Macro_commands_and_special_characters|macro commands and special characters section]].
  
Since the exchange, CQ etc. varies between contests, every contest has its unique set of default messages.<br>
+
Since the exchange, CQ etc. varies between contests, every contest has its own set of default messages.<br>
 
These default messages are however only used the first time a log is created for the particular contest.<br>
 
These default messages are however only used the first time a log is created for the particular contest.<br>
 
To allow customization, all following logs created for a particular contest use the messages from the <br>
 
To allow customization, all following logs created for a particular contest use the messages from the <br>
Line 194: Line 319:
 
You can even call own scripts in the message using the <tt>$!scriptname</tt> syntax.
 
You can even call own scripts in the message using the <tt>$!scriptname</tt> syntax.
  
A complete list of macros and special characters can be found in the [[Configuration#Message_macros|message macros section]].
+
<u>You can always return to the default messages by clicking the <i>Defaults</i> button.</u> This can also be helpful<br>
 +
when switching "role" from a previous time you participated in the same contest, such as member/non-member,<br>
 +
IOTA station/non-IOTA station.
 +
 
 +
'''Important:''' If you run CW and want to secure good spotting by the Reverse Beacon Network, do not use speed changes<br>
 +
in your CQ message. Short calls (4 characters or less) should typically be repeated.
 +
 
 +
A complete list of macros and special characters as well as the very powerful conditionals syntax<br>
 +
can be found in the [[Configuration#Macro commands and special characters|message macros section]].
 +
 
 +
Space characters in the beginning or end of the message are always ignored. To introduce a delay, use <code>$DELAY</code>.
  
 
==Voice memory playback==
 
==Voice memory playback==
  
In phone contesting having a means to transmit pre-recorded messages is invaluable. Particularly for CQ.  
+
In phone contesting having a means to transmit a pre-recorded CQ message is a great help.<br>
 +
Sometimes for other messages too.
  
 
DXLog has a built-in voice recorder (often referred to as a DVK - digital voice keyer) but also supports the<br>
 
DXLog has a built-in voice recorder (often referred to as a DVK - digital voice keyer) but also supports the<br>
 
use of that built into many radios. (More information can be found in the [[Menu_Options#Digital_Voice_Keyer|Digital Voice Keyer]] section.)
 
use of that built into many radios. (More information can be found in the [[Menu_Options#Digital_Voice_Keyer|Digital Voice Keyer]] section.)
  
If you want to use ESM (see the [[Getting_started#ESM|ESM section]]) also on phone there are some message conventions to be followed.
+
'''Important:''' If you use the radio's built in voice keyer, make sure to check the box<br>
 +
"Don't set PTT when using voice keyer" on the COM port controlling your radio's<br>
 +
PTT to avoid a self-locking PTT loop.
 +
 
 +
If you want to use ESM (see the [[Getting_started#ESM|ESM section]]) also on phone the message number convention<br>
 +
from CW and digital modes need to be followed.
  
 
{|class="wikitable"
 
{|class="wikitable"
Line 209: Line 350:
 
|-
 
|-
 
| Message #1
 
| Message #1
| CQ message. E.g. "SM7IUN, contest".
+
| CQ message. E.g. "SM7IUN, contest"
 
|-
 
|-
| Message #1
+
| Message #2
| Exchange, when the contest allows. E.g. "Roger, you are five nine fourteen".
+
| S&P exchange, when the contest allows. E.g. "Roger, you are five nine fourteen"
 
|-
 
|-
 
| Message #4
 
| Message #4
| Own call. E.g. "SM7IUN".
+
| Own call. E.g. "SM7IUN"
 
|-
 
|-
 
| Message #6
 
| Message #6
| Request repeat. "Again, again".
+
| Request repeat. "Again, again?"
 
|}
 
|}
  
Another useful message can be the one associated with logging the QSO in Run. E.g. "Thank you and good luck, SM7IUN, contest".<br>
+
'''Important:''' On Phone in SO1R, SO2V, and SO2R, macro commands are only recognized in the INSERT and PLUS messages<br>
For this to work, the RUN PLUS message must contain the macro commands to log and send the message. (e.g. <code>$F7 $CR</code>, or similar).
+
and are ignored in messages 1 through 7. In SO2R Advanced, however, each used scenario needs to include the wanted<br>
 +
playback macros, $F1, $F2, etc.
 +
 
 +
'''Important:''' A useful message can be the one associated with logging the QSO in RUN. E.g. "Thank you and good luck, SM7IUN, contest".<br>
 +
However, for this to work, the RUN PLUS message must contain the macro commands to send a message and log. (e.g. <code>$PBPLUS $CR</code>).
 +
 
 +
Since the INSERT message i RUN contains the other station's call it can not be prerecorded.<br>
 +
Following the conventions above, the standard INSERT message will however work for S&P.
  
 
==Useful settings==
 
==Useful settings==
  
 
Since this is just a quick-start guide, only the most commonly used or misunderstood settings will be covered here.
 
Since this is just a quick-start guide, only the most commonly used or misunderstood settings will be covered here.
 
<code>Operating|Bandmap|QSY Opposite radio instead of 2nd VFO</code>
 
: Makes operations normally affecting the other VFO instead affect the other radio.
 
: For instance, in SO2R and SO2V this option should be enabled to allow jumping between
 
: spots on the other radio with <code>[Ctrl][Alt][Up/Down]</code>.
 
  
 
<code>Options|Load contest at startup</code>
 
<code>Options|Load contest at startup</code>
Line 239: Line 382:
 
: a merging of the logs which normally is highly undesired.
 
: a merging of the logs which normally is highly undesired.
  
<code>Options|Interface specific options|Use SPLIT command in SO2V technique</code>
+
<code>Options|Interface specific options|Dual receiver radio (Use split in SO2V)</code>
 
: A very important setting for SO2V. Should be enabled for dual receiver radios and  
 
: A very important setting for SO2V. Should be enabled for dual receiver radios and  
 
: disabled for single receiver radios.
 
: disabled for single receiver radios.
  
<code>Options|Interface specific options|Change band of both VFO</code>
+
<code>Options|Interface specific options|Band change keys affect both VFO</code>
 
: Makes band changes with <code>[Alt][F1]</code> and <code>[Alt][F2]</code>  
 
: Makes band changes with <code>[Alt][F1]</code> and <code>[Alt][F2]</code>  
 
: switch the band of the selected radio's both VFO. Recommended.
 
: switch the band of the selected radio's both VFO. Recommended.
 
<code>Options|CW/Digi|Work dupes</code>
 
: Shall always be enabled. Not working dupes in a contest is a legacy practice and belongs with paper logs.
 
: DX-peditions may however decide differently. 
 
 
<code>Options|CW/Digi|Add spacing when stacking messages</code>
 
: Should be enabled. Adds a word space when standard messages are stacked.
 
: Please notice that <code>[Enter]</code> does not stack but restarts the message.
 
  
 
<code>Options|Log|Show border on TX</code>
 
<code>Options|Log|Show border on TX</code>
Line 264: Line 399:
  
 
<code>Options|Log|Show cursor in entry line without focus</code>
 
<code>Options|Log|Show cursor in entry line without focus</code>
: Shows a shadow cursor in the unselected entry line. Recommended.
+
: Shows a shadow cursor in the unselected entry line. Highly recommended.
  
 
<code>Tools|Data entry|Enable ESM mode</code>
 
<code>Tools|Data entry|Enable ESM mode</code>
Line 277: Line 412:
  
 
<code>Tools|Data entry|Exchange guessing|Automatic</code>
 
<code>Tools|Data entry|Exchange guessing|Automatic</code>
: Gives immediate feedback if e.g. the station is a dupe or multiplier when you type a call or grab a spot.
+
: When applicable, produces an exchange guess as you type.  
: (The default is to not do this until you hit <code>[Space]</code>.)
+
: Does the same also for dupe and new multiplier information.
 +
: Highly recommended.
  
<code>Tools|Data entry|F1 returns to Run always</code>
+
<code>Tools|Data entry|F1 forces Run mode</code>
 
: Makes the <code>[F1]</code> key always switch to ''Run'', mark the CQ frequency and send CQ.  
 
: Makes the <code>[F1]</code> key always switch to ''Run'', mark the CQ frequency and send CQ.  
 
: Recommended.
 
: Recommended.
Line 286: Line 422:
 
==ESM==
 
==ESM==
  
With ESM, or Enter Sends Message, which the acronym stands for, there are different schools.  
+
With ESM, or <i>Enter Sends Message</i>, which the acronym stands for, there are different schools.  
  
DXLog has a very straightforward and predictable ESM. It is stateless which means that it<br>
+
DXLog has a very straightforward and deterministic ESM. It is stateless which means that it<br>
 
does not try to guess the intentions of the operator based on past actions.
 
does not try to guess the intentions of the operator based on past actions.
  
The message sent by <code>[Enter]</code> only depends on three factors: Operating state (''Run'' or ''S&P''),<br>
+
The message sent by <code>[Enter]</code> only depends on three factors:
the location of the cursor and whether the field is filled or not. This makes DXLog's ESM<br>
+
 
very predictable and easy to learn.
+
: Operating state (''Run'' or ''Search & Pounce'')
 +
: The location of the cursor
 +
: The content of the current field
 +
 
 +
This makes DXLog's ESM very predictable and easy to learn.
  
 
Since ESM may be undesired on Phone the option <code>Tools|Data entry|ESM mode only for CW</code><br>
 
Since ESM may be undesired on Phone the option <code>Tools|Data entry|ESM mode only for CW</code><br>
allows you to use it only for CW in e.g. a mixed contest.
+
allows you to use it only for CW in e.g., a mixed mode contest entry.
 +
 
 +
DXLog ESM assumes the following configuration of the standard messages:
 +
 
 +
: RUN F1 - CQ message
 +
: RUN F6 - Request exchange
 +
: RUN INSERT - Send other call and exchange
 +
: RUN PLUS - Send corrected call if required, log and send semi-CQ (such as own call)
 +
 
 +
: S&P F1 - Own call
 +
: S&P F6 - Request exchange
 +
: S&P INSERT - Send exchange and log
  
 
The function is as follows:
 
The function is as follows:
Line 302: Line 453:
 
===Run===
 
===Run===
  
* With the cursor in an empty callsign field, <code>[Enter]</code> sends ''Run'' F1, typically CQ
+
Pressing <code>[Enter]</code> in RUN will:
* With the cursor in a partially or correctly filled callsign field, <code>[Enter]</code> sends the RUN INSERT message
+
 
* With the cursor in the exchange field, <code>[Enter]</code> sends the ''Run'' PLUS message which (typically) concludes the QSO and logs.
+
* with the cursor in an empty callsign field send RUN F1, typically CQ
 +
* with the cursor in a partially or correctly filled callsign field send RUN INSERT
 +
* with the cursor in an incorrectly filled exchange field send RUN F6
 +
* with the cursor in a correctly filled exchange field send RUN PLUS
 +
 
 +
'''Important:''' If a number server is used, serial number reservation must be correctly configured.
  
 
When the party station has received the exchange correctly, focus is shifted to the exchange<br>
 
When the party station has received the exchange correctly, focus is shifted to the exchange<br>
 
field by pressing <code>[Space]</code>
 
field by pressing <code>[Space]</code>
  
For a big gun station, where correct reception of the exchange is (almost) guaranteed, you can <br>
+
For a large station, where correct reception of the exchange is (almost) guaranteed, you can <br>
 
automatically shift focus to the exchange field after having sent the exchange by enabling the <br>
 
automatically shift focus to the exchange field after having sent the exchange by enabling the <br>
menu option <code>Tools|Data entry|ESM mode change focus on $LOGGEDCALL macro</code>.
+
menu option <code>Tools|Data entry|Focus received exchange after sending exchange in Run</code>.
 +
 
 +
===Search & Pounce===
 +
 
 +
Pressing <code>[Enter]</code> in S&P will:
  
===S&P===
+
* with the cursor in the callsign field send S&P F1
 +
* with the cursor in an empty or incorrectly filled exchange field send S&P F6
 +
* with the cursor in a correctly filled exchange field send S&P INSERT
  
* With the cursor in the callsign field, <code>[Enter]</code> sends ''S&P'' F1, typically your own callsign
+
'''Important:''' If a number server is used, serial number reservation must be correctly configured.
* With the cursor in an empty exchange field, <code>[Enter]</code> sends ''S&P'' F6, which is typically a request to repeat the exchange.
 
* With the cursor in a filled exchange field, <code>[Enter]</code> sends ''S&P'' INSERT, which is typically a confirmation and semi-CQ, and logs.
 
  
For a big gun station, where correct reception of the exchange is (almost) guaranteed, you can <br>
+
For a big gun station, where correct reception of the exchange is (almost) guaranteed, you can automatically<br>
automatically shift focus to the exchange field after having called the station by adding the <tt>$SPACE</tt> <br>
+
shift focus to the exchange field after having called the station by adding the <tt>$SPACE</tt> macro to the S&P F1 message.
macro to the ''S&P'' F1 message.
 
  
 
You can find more information on ESM in the [[Menu_Tools#Data_entry|Data entry menu section]].
 
You can find more information on ESM in the [[Menu_Tools#Data_entry|Data entry menu section]].
 +
 +
==Connecting to the DX cluster==
 +
 +
DXLog offers two ways of connecting to the DX cluster, one basic, included in DXLog, and one advanced,<br>
 +
relying on a companion program.
 +
 +
'''Important:''' If your current log is unassisted (either by selection or since the contest rules generally<br>
 +
forbid assistance), DXLog will not display any cluster spots, even when connected.
 +
 +
===Basic connection===
 +
 +
Since an increasing number of contests allow self-spotting, also on unassisted entries, DXLog always allows<br>
 +
connecting to the DX cluster but does not display incoming spots when the log is set to an unassisted entry category.
 +
 +
DXLog's default cluster node is VE7CC. If you prefer another node, you click <code>Options|DX cluster|Edit connection list</code>.<br>
 +
This opens a window that allows you to edit existing entries, add new ones, and select a new default node. (More [[Menu_Options#Edit_connection_list|HERE]]).
 +
 +
If you get lost editing the list, you can always reset it to "factory" settings with <code>Options|DX cluster|Reset connection list</code>.
 +
 +
Checking <code>Options|DX cluster|Reconnect default cluster node at startup</code> will make sure you are always<br>
 +
connected when running DXLog.
 +
 +
You connect by clicking <code>Commands|DX cluster|Connect default</code> or <code>Connect other</code>.<br>
 +
This will bring up a dialog with your default login information. Its content is remembered by DXLog between sessions.
 +
 +
Clicking <code>Windows|DX cluster monitor</code> or pressing <code>[Alt][O]</code> will bring up a window that shows the<br>
 +
telnet text flow from the cluster node. Although meaningless to use for catching spots, it can be used to make sure<br>
 +
the connection is correct and see error messages if the login procedure fails.
 +
 +
Spots should now start appearing in your bandmap.
 +
 +
DXLog will only display spots of the mode or modes relevant for your contest entry.
 +
 +
===Advanced connection===
 +
 +
If you are in a multi-station setting and want to separate the cluster connection from your operating positions or<br>
 +
have a need to connect to multiple spot sources, you can use the <tt>DXLog.net.DXC</tt> companion program.
 +
 +
<tt>DXLog.net.DXC</tt> distributes spots on a LAN to one or several instances of DXLog via the normal DXLog multi-station<br>
 +
networking protocol. This means networking must be enabled and correctly configured.
 +
 +
Make sure <code>Options|Enable network</code> is checked and that "networking for multiple stations" is checked in the<br>
 +
network configuration panel. Also make sure that the station's networking IP address is correct. It should typically <br>
 +
be the computer's IP address with the last number replaced by 255.
 +
 +
<tt>DXLog.net.DXC</tt> offers a rich set of features including blacklisting and skimmer control. More information can be found [[DXLog.net.DXC|HERE]]
 +
 +
In <tt>DXLog.net.DXC</tt>, enter your callsign by clicking <code>Settings|User data</code>. Also check your network settings <br>
 +
under <code>Settings|Network</code>. For a single station setting, you can click the ''Local defaults'' button which will not <br>
 +
send spots outside your computer. Clicking ''LAN defaults'' will distribute spots to your entire LAN.
 +
 +
The checkbox ''Cluster cmd'' should be checked for at least one cluster connection.<br>
 +
This checkbox controls to which nodes commands from DXLog (such as self spots) are forwarded.
 +
 +
You connect to the cluster node by clicking the ''Connect'' button.
 +
 +
If everything is correct, you should now see spots arriving in the <code>Windows|DX cluster monitor</code> window on all networked stations. <br>
 +
If the current log's category is assisted, they will also appear in the bandmap.
 +
 +
If you are running <tt>DXLog.net.DXC</tt> on a separate computer or server and want to establish all cluster connections automatically<br>
 +
when <tt>DXLog.net.DXC</tt> is started, check <code>Operating|Connect all tabs at startup</code>.
  
 
==The bandmap and other windows==
 
==The bandmap and other windows==
Line 336: Line 556:
  
 
With an internet connection to the DX Cluster you will see the spots spread out over an intuitive, <br>
 
With an internet connection to the DX Cluster you will see the spots spread out over an intuitive, <br>
thermometer-like representation of a part of the current frequency band or as a color-coded listing.  
+
thermometer-like representation of a part of the current frequency band or as a color-coded listing.<br>
 +
You can either let DXLog connect directly to the DX Cluster (as described in the [[Menu_Commands#DX_cluster|DX Cluster section]])<br>
 +
or via the DXLog.net.DXC cluster connectivity utility, described in the [[DXLog.net.DXC|DXLog.net.DXC section]].
  
The bandmap can be set up to contain a massive amount of useful information such as if a spot represents <br>
+
The bandmap can be set up to convey a large amount of useful information such as if a spot represents <br>
a new multiplier, if it has been worked before, the required antenna direction, the sun's position at the <br>
+
a new multiplier, if it has been worked before, a suitable antenna direction, the sun's position at the <br>
 
station's location etc. You can quickly jump between spots by holding down <code>[Ctrl]</code> while pressing <br>
 
station's location etc. You can quickly jump between spots by holding down <code>[Ctrl]</code> while pressing <br>
 
the up and down arrow keys. (There are many more keyboard shortcuts associated with the band map, for more <br>
 
the up and down arrow keys. (There are many more keyboard shortcuts associated with the band map, for more <br>
Line 346: Line 568:
 
the bandmap and selecting <code>Properties</code>. Further information about the bandmap can be found in the [[Menu_Windows#Radio_1|bandmap section]].
 
the bandmap and selecting <code>Properties</code>. Further information about the bandmap can be found in the [[Menu_Windows#Radio_1|bandmap section]].
  
Besides the bandmap there are many useful windows available. ''Check Partials'' and ''Check N+1'' helps <br>
+
The bandmap is also very useful when operating without a DX cluster connection, a.k.a. unassisted.<br>
you guess callsigns you are unsure of. ''Check Multipliers'' gives information on which bands you have <br>
+
You can add stations to the bandmap by entering the call and pressing <code>[Ctrl][Enter]</code>.<br>
worked a certain multiplier.  
+
Such manually entered stations are automatically erased when worked in Run.<br>
 +
Stations worked in S&P are also added to the bandmap to avoid you having to identify them again.
 +
 
 +
'''Important:''' The bandmap contains some S&P features, such as wiping the currently entered call and/or adding an<br>
 +
entered call to the bandmap when tuning away from it, that are active also with no bandmap window open.<br>
 +
You find these settings by selecting <code>Properties</code> in the bandmap context menu.
 +
 
 +
In the Bandmap properties panel you will also find the spot lifetime settings. These control how long a spot will<br>
 +
be displayed before erased. A suitable number for cluster spots is 11 minutes for CW and RTTY (RBN has a respotting<br>
 +
timer of 10 minutes) and 20 minutes or more minutes for phone and other digital modes. For manual spots, 30 minutes<br>
 +
is a reasonable number.
 +
 
 +
Besides the bandmap there are many useful windows available. ''DX cluster announcements'' can show you a<br>
 +
list of all valuable spots as one single list.
 +
 
 +
''Check Partials'' and ''Check N+1'' helps you guess callsigns you are unsure of. ''Check Multipliers'' gives<br>
 +
information on which bands you have worked a certain multiplier.  
  
 
Finally ''Clock'' is a very helpful little bar showing essential information like exact time, operating <br>
 
Finally ''Clock'' is a very helpful little bar showing essential information like exact time, operating <br>
state, logged in operator etc.
+
state, logged in operator etc.
 
 
You may find the menu system of DXLog somewhat idiosynchratic. The development team has a long term <br>
 
ambition to improve its structure and user friendliness.
 
  
 
==After the contest==
 
==After the contest==
  
After the contest you typically want to create a Cabrillo or EDI file for submission and <br>
+
After the contest you typically want to create a Cabrillo or EDI file for submission and perhaps an ADIF file to<br>
perhaps an ADIF file to upload to LoTW or import in a bulk logger.
+
upload to LoTW or import in a bulk logger.
  
Cabrillo files are exported using <code>File|Export|Cabrillo</code> and ADIF files <br>
+
Cabrillo files are exported using <code>File|Export|Cabrillo</code> and ADIF files using <code>File|Export|ADIF</code>.<br>
using <code>File|Export|ADIF</code>. ADIF exports offers you the option to also include<br>
+
ADIF exports offers you the option to also include ''X-QSO'', which you normally do not want to do. There however situations<br>
''X-QSO'', which you normally do not want to do.  
+
when you may want to include them, such as when excluding valid QSO on another band for a single band contest entry.
  
 
If your contest uses a prefill database, and you trust your log, you can update the database using <br>
 
If your contest uses a prefill database, and you trust your log, you can update the database using <br>
 
<code>Options|Data files|Update database</code>. It is possible to update data files of any supported type.
 
<code>Options|Data files|Update database</code>. It is possible to update data files of any supported type.
  
Be however aware that your own updates will be lost the next time an updated database is included <br>
+
Be however aware that your own updates will be lost the next time an updated database is included in a new DXLog release that you install.<br>
in a new DXLog release that you install. If you really want to preserve your updates, make <br>
+
If you really want to preserve your updates, make a copy of DXLog's database in the same folder as the log file.<br>
a copy of DXLog's database in the same folder as the log file. More on how to manage prefill <br>
+
More on how to manage prefill databases can be found in the [[Menu_Options#Prefill_database_settings|prefill database settings section]].
databases can be found in the [[Menu_Options#Prefill_database_settings|prefill database settings section]].
 
  
Entering postcontest mode with <code>Edit|Postcontest mode</code> will allow you to edit all<br>
+
Entering postcontest mode with <code>Edit|Postcontest mode</code> will allow you to edit all properties of the logged QSO using <code>[Alt][F]</code><br>
properties of the logged QSO using <code>[Alt][F]</code> and <code>[Ctrl][F1]</code>/<code>[Ctrl][F2]</code>.<br>
+
and <code>[Ctrl][F1]</code>/<code>[Ctrl][F2]</code>. It also allows entering a paper log by opening the time field for direct entry.
It also allows entering a paper log by opening the time field for direct entry.
 
  
 
==Tips and tricks==
 
==Tips and tricks==
  
On most radios <code>[Shift][Up]</code> och <code>[Shift][Down]</code> as RIT in ''Run'' and frequency adjustment in ''S&P''.  
+
* Try the world map. It will show where you are spotted on the DX cluster.
 +
 
 +
* Try SO2V. You will have more fun and become a an even more productive operator.
 +
 
 +
* Get acquainted with ESM. Once familiar with it, you will find it very convenient.
 +
 
 +
* If you connect to the DX cluster and see no spots in your bandmap, make sure you<br>are not using an unassisted contest entry.
  
<code>[Ctrl][Up]</code> and <code>[Ctrl][Down]</code> jumps between spots in the bandmap and grabs them onto the focused entry line.  
+
* On most radios <code>[Shift][Up]</code> and <code>[Shift][Down]</code> work as RIT in ''Run''<br>and frequency adjustment in ''S&P''.<br><code>[Shift][Delete]</code> zeroes RIT regardless of operating mode.
  
<code>[Ctrl][Alt][Up]</code> and <code>[Ctrl][Alt][Down]</code> jumps between spots in the other VFO or radio,<br>
+
* <code>[Ctrl][Up]</code> and <code>[Ctrl][Down]</code> jumps between spots in the bandmap and<br>grabs them onto the focused entry line.  
depending on if <code>Operating|Bandmap|QSY Opposite radio instead of 2nd VFO</code> is checked or not.
 
  
<code>[Shift][Ctrl][Up]</code> and <code>[Shift][Ctrl][Down]</code> jumps to the next <br>
+
* <code>[Ctrl][Space]</code> grabs the spot in the bandmap on or close to your current frequency.  
spot that is a multiplier.  
 
  
Double-clicking a spot or pressing <code>[Ctrl][Space]</code> grabs a spot from the bandmap.  
+
* <code>[Ctrl][Alt][Up]</code> and <code>[Ctrl][Alt][Down]</code> jumps between spots in the other VFO or radio,<br>depending on if <code>Operating|Bandmap|QSY Opposite radio instead of 2nd VFO</code> is checked or not.
  
<code>[Ctrl][Enter]</code> creates a spot using an entered callsign and the focused radio's frequency.
+
* <code>[Shift][Ctrl][Up]</code> and <code>[Shift][Ctrl][Down]</code> jumps to the next spot that is a multiplier.  
  
<code>[Alt][K]</code> opens a panel for sending CW or a conversational digital mode directly<br>
+
* Double-clicking a spot in the bandmap grabs it. There is a menu option change this to single click.
from the keyboard. It is closed by pressing <code>[Alt][K]</code> or <code>[Enter]</code>.
 
  
<code>[Ctrl][Alt][+]</code> or <code>[Ctrl][Alt][Keypad +]</code> forces a QSO to be logged,<br>
+
* <code>[Ctrl][Enter]</code> creates a spot using an entered callsign and the focused radio's frequency.
disregarding all validity checks.  
 
  
<code>[Shift][Ctrl][F1]</code> shifts focus to radio 1, switches to ''Run'', and sends CQ in SO2R and SO2V.<br>
+
* <code>[Alt][K]</code> opens a panel for sending CW or a conversational digital mode directly<br>from the keyboard. It is closed by pressing <code>[Alt][K]</code> or <code>[Enter]</code>.
In SO1R and SO2R Advanced it just sends the F1 message.<br>
 
Depending on your operating preferences you may want to redefine <code>[F1]</code> to always execute this key.  
 
  
<code>[Alt][Q]</code> activates "intelligent quick QSL" which is a very nice function for <br>
+
* <code>[Ctrl][Alt][+]</code> or <code>[Ctrl][Alt][Keypad +]</code> forces a QSO to be logged,<br>disregarding all validity checks.  
DX-peditions and large contest stations. It uses rate statistics to send a short confirmation <br>
 
at the end of each QSO but still regularly send the full callsign.  
 
  
The text commands ''RELOAD'' and ''RELOADNOW'' reloads the current log. The latter skips the confirmation <br>
+
* Pressing <code>[Ctrl][X]</code> with the cursors on a QSO in the log will "delete" the QSO by marking it invalid.
popup. (Please note that this command also refreshes contest definitions and scripts without event handlers.)
 
  
''RESET'' eller <code>[Ctrl][Alt][R]</code> resets all hardware interfaces. <br>
+
* <code>[Shift][Ctrl][F1]</code> shifts focus to radio 1, switches to ''Run'', and sends CQ in SO2R and SO2V.<br>In SO1R and SO2R Advanced it just sends the F1 message.<br>Depending on your operating preferences you may want to redefine <code>[F1]</code> to always execute this key.  
When connecting/disconnecting equipment or in the presence of EMC or RFI issues, this can be very helpful.
 
  
To search for a certain callsign in your log, type the callsign in the entry field.<br>
+
* <code>[Alt][Q]</code> activates "intelligent quick QSL" which is a great convenience for<br>DXpeditions and large contest stations. It uses rate statistics to send a short confirmation<br>at the end of each QSO but still regularly send the full callsign.
The <i>Check Callsign</i> window will show you which bands you have worked the callsign on.<br>
+
 
Double-click the red checkmark to jump to the corresponding QSO in the log.<br>
+
* The text commands ''RELOAD'' and ''RELOADNOW'' reloads and rescores the current log.<br>The latter skips the confirmation popup. (This command also refreshes contest definitions<br>and scripts without event handlers.)
Return to the entry line with <code>[Ctrl][End]</code>
+
 
 +
* ''RESET'' eller <code>[Ctrl][Alt][R]</code> resets all hardware interfaces.<br>When connecting/disconnecting equipment or in the presence of EMC or RFI issues, this can be very helpful.
 +
 
 +
* To search for a certain callsign in your log, type the callsign in the entry field.<br>The <i>Check Callsign</i> window will show you which bands you have worked the callsign on.<br>Double-click the red checkmark to jump to the corresponding QSO in the log.<br>Return to the entry line with <code>[Ctrl][End]</code>
 +
 
 +
* Holding down <code>[Ctrl]</code> during start-up of DXLog will give you the option to not restore the<br>previous layout and log file.
 +
 
 +
* On many contests you can do a reverse look-up from a prefill data file by entering the exchange<br>and pressing <code>[Space]</code>. This will show the candidate matches in the Check Partials window.
 +
 
 +
* On many contests where the exchange is a grid, you can type a six-character grid in the callsign<br>entry field and press <code>[Space]</code> to get distance and azimuth.
 +
 
 +
* If you have problems starting DXLog, as a last resort go to the folder <code>%appdata%</code> using<br>the <code>[Win][R]</code> key and rename the <tt>DXLog.net</tt> folder. Then try again.
  
 
==DXLog system files==
 
==DXLog system files==
Line 427: Line 667:
 
<tt>%appdata%\DXLog.net</tt> or using DXLog's menu item <code>File|Open configuration folder</code>.
 
<tt>%appdata%\DXLog.net</tt> or using DXLog's menu item <code>File|Open configuration folder</code>.
  
'''NB.''' The only real need a regular user has to open this folder is to install urgent contest or<br>
+
'''Important:''' The only real need a regular user has to open this folder is to install contest or<br>
database updates between regular DXLog releases or emergencies.  
+
database updates between regular DXLog releases or at emergencies.
 +
 
 +
Updates to contest definitions and/or databases are better updated by clicking <code>File|Update contest</code>.
  
 
The content of the configuration folder is the following:
 
The content of the configuration folder is the following:
Line 439: Line 681:
 
: when exists contains custom form DLL files.  
 
: when exists contains custom form DLL files.  
 
* File '''DefMsgs.sdb'''  
 
* File '''DefMsgs.sdb'''  
: Default messages for all contests worked. Not editable.
+
: Default messages for all contests operated. Not editable.
 
* File '''deftest.dxl'''
 
* File '''deftest.dxl'''
 
: Default contest configuration. Not editable.
 
: Default contest configuration. Not editable.
 
* Optional file '''DXCSpotHistory.txt'''
 
* Optional file '''DXCSpotHistory.txt'''
: Result of checking "Incoming spots logging" in DX Cluster Announcement window.
+
: Result of checking "Incoming spots logging" in DX Cluster announcement window.
 
* Optional file '''DXCStreamHistory.txt'''
 
* Optional file '''DXCStreamHistory.txt'''
: Result of checking "Stream logging" in the DX Cluster window.
+
: Result of checking "Stream logging" in the DX Cluster monitor window.
 
* File '''DXLog.net.config.backup'''
 
* File '''DXLog.net.config.backup'''
 
: A backup copy of the most recent working DXLog.net.config
 
: A backup copy of the most recent working DXLog.net.config

Latest revision as of 11:41, 4 March 2024

Introduction and plea

DXLog is a very powerful contesting software with enormous flexibility.

Unfortunately this comes with complexity and a significant learning curve for new users.

This wiki is written by DXLog experts who may be somewhat blind of the needs of a new user.

If you have ideas for improvement of this section, please share them with the development
team via the support reflector.

User interface

Contest loggers are a little like clothes. Some like a particular style, some don't.
DXLog has a classic look and feel and builds on a long tradition when it comes to
keyboard shortcuts and other UI elements. It is keyboard-centric and designed so you
should very rarely have to take your hands off the keyboard.

Contrary to e.g., N1MM Logger+, DXLog's default setting is to use a single window, a "desktop".
There are many benefits with this, for instance the fact that you can rapidly switch between
the logger and another application, such as a web browser, with [Alt][Tab].

It also allows other applications that have the ability to stay "on top" to do this also with DXLog.


Dxl prev2.png


DXLog follows the tradition of many other loggers and have one or two entry lines and the nine
most recent log entries in fixed locations in the main window. The entry lines are either on
top or beside each other and, unless you are using dual keyboards, you move between them
using the arrow keys.


Entryfields.png


DXLog shares many characteristics with other loggers but for those used to e.g. N1MM Logger+,
there are two very important differences.

  • The log and the entry lines are connected. Using the arrow keys, moving up past the top
entry line will take you into the log.
  • You can modify a logged QSO but not delete it. In the spirit of old school contest logging,
you can only mark it invalid. This is done by navigating to the QSO and pressing [Ctrl][X].
The "old school" method of changing the callsign of the QSO to your own is also supported.
  • The numbering and use of the standard messages is different.

The entry line is divided into fields, most of them are read-only like QSO number, band, mode, time, etc.
Each contest has at least callsign and one exchange field. Some contests have several exchange fields.
You move between major fields by pressing [Space] and between all fields with [Tab].
RS/RST is not a major field.

The callsign is checked for validity using this regular expression:

^((([A-Z1-9]+0?\/)?[1-9]?[A-Z]{1,3}[0-9]+[A-Z]+(\/[A-Z0-9]+)?(\/[AMP]{1,2})?)|RAEM|EA0)$

When you have completed your entry, you typically log the QSO using either [Enter] or [+].

The location and visibility of the log and entry line column headers can be controlled with Options|Log|Headers.

Note that the rightmost Stn station type column becomes visible only when activating networking or selecting
an operating technique other than SO1R.

Creating a log file

To start using DXLog, the first step is to create a log file. Without an open log file,
DXLog will just show an empty desktop.

To create a log, select File|New. This opens the contest configuration window.

DXLog needs exclusive and unrestricted access to its log file and relies on Windows'
standard file permissions for this. This means that some types of shared or synchronized
folders, or folders in virtualized environments, may not work for log file storage.

Unlike most other loggers, DXLog is compatible with Microsoft OneDrive.


DXL ContestConfig1.png


There are many text boxes to fill and not all are used by all contests, but it is a good idea to
fill as many of them as possible since it will save you typing each time you create a new log.

Should DXLog miss information from you when you click the OK button, you will get a helpful popup
window and the cursor will be placed in the field with missing or invalid information.

After having clicked OK you will get a browser window that allows you to decide the name and location
of your new log file. It is good practice to use a separate folder for each contest since you will have
other files related to the contest, call history files, export files like Cabrillo, ADIF, SUM, etc.

It is also a good practice to include things like contest name, station callsign and year in the log's filename.

The first time a log is created after the installation, "factory default" colors and window locations
will be used. From this point on, every time you create a new log, the color settings, the active
windows and their location will be inherited from the most recently opened log. This means that if you
for instance run a weekly test in which you want a particular layout or color scheme, it is a good idea
to open the previous' weeks log before creating a new one.

Also note that messages are stored on a per-contest basis. This means that when creating a new log, the
messages from the previous, same contest will be used. If there is none, the contest's default messages will
be used. Since some contests have messages based on location or participation status, this is important
to be aware of.

You will find much more information in the contest configuration section.

Controlling the radio

The next step is to set up the communication with the radio. You reach the radio interface by
either clicking Options|Configure interfaces or by typing the text command SETUP
and pressing [Enter] on the entry line.


Portconfig.png


There are numerous settings and alternatives in how to set up your radio. On some models special
features like diversity, or the built in voice keyer, is supported. In this panel you can also
configure the control of peripherals such as SO2R controllers. You can find more information in the
Configure interfaces section.

You can also find general recommendations about settings for particular radio models in the
supported radios section.

Setting up DXLog for digital operation involves many settings.

John G4IRN has prepared an excellent tutorial on this topic which can be viewed here.

Databases

The next step is to make sure two important data bases are up to date; the country data base CTY.DAT
(and its siblings) and the callsign database MASTER.SCP.

The menu Options|Data files|Country files opens a window that allows you to update three
alternative country databases. Chose one at the time and click Download. Normally the most detailed,
CTY_WT_MOD.DAT is the recommended one to use.

The callsign database is updated with the menu Options|Data files|Super check partials|Update.

To make all updates come into effect, type RELOADNOW followed by [Enter] or simply
close and restart DXLog.

Operating techniques

The next step is to chose your operating method, Technique in DXLog terminology.

DXLog supports four different techniques; SO1R, SO2V, SO2R, and SO2R Advanced.

SO1R means Single Operator, One Radio. SO2R means Single Operator, Two Radios. SO2V means Single Operator,
Two VFO but in practice this is normally also Two Receiviers. In a multi-operator setting you typically use
SO1R but an advanced operator can also use SO2V.

The menu Operating|Technique let you choose between SO1R, SO2R, Advanced SO2R and SO2V.

Each technique supports two operating "states"; Run and Search & Pounce (or S&P for short).

Run means you call CQ and work calling stations. S&P means you search for stations and work them by calling them.

Each state has a separate set of predefined messages (see below) and ESM behavior (also see below).
The keyboard shortcut to switch between the states is [Ctrl][Tab].

There are also some options for forcing an automatic change, such as
Tools|Data entry|F1 returns to Run always and Tools|Enable automatic Run/S&P selection.

SO1R

SO1R is the most basic and it is the method you use in a single operator setting using a single
receiver radio or in multi-station setting.

When using this technique, you have a single entry line and one radio with one receiver.
The band map shows the band map for the currently selected VFO.

In the top of the bandmap the frequencies of VFO A and VFO B are shown in boxes.
The boxes are clickable and you can also switch between the VFO using [Keypad *].
If you want to make a rapid excursion to work e.g. a multiplier, you can always jump back to
your Run frequency with [Alt][F4].

SO1R only works for Radio 1 in the Options|Configure interfaces panel.


So1r-cqww.png


SO2R and Advanced SO2R

uses two radios which operate in parallel, each having a separate entry line. (Although you never
transmit with more than one at any time.)

In "standard" SO2R you operate by manually switching your "focus" between the two radios.
This is done using the up and down arrow keys or [Keypad *].

SO2R also supports external audio control by a large range of SO2R controllers such as all microHAM
keyers/controllers or devices such as the YCCC SO2R box or SO2R mini.

In Advanced SO2R the focus shifting is typically scripted, using up to eight different "scenarios" for different
situations such as hunting for multipliers, alternating CQ, or managing a large pile-up.

More information can be found in the Advanced SO2R section.
This feature is particularly appreciated by advanced contesters.

SO2R requires two radios (Radio 1 and Radio 2) configured in the Options|Configure interfaces panel.

Important: If running a contest where the exchange is a serial number, you must use a number server and number
reservation to secure that the transmitted and logged serial number are the same. You will find more
information about this in the using a number server section.


So2r-cqww.png

SO2V

At a first glance, SO2V looks similar to SO2R but uses only a single radio (two "R" entry lines).
This method is primarily intended for dual receiver radios (such as Elecraft K4, ICOM IC-7610, or Yaesu FTDX101D)
but offer some usability and efficiency benefits also for single receiver radios.

Like in SO2R, mastering having one receiver in each ear will maximize your efficiency.
The logical model of SO2V is two radios with a shared transmitter.

Unlike SO2R, the two radios are typically on the same band.

Split band SO2V puts very challenging requirements on antenna and amplifier band switching speed
and requires a very careful station design. DXLog offers no protection against e.g., hot switching in such a situation.

The most common way to operate SO2V is to switch focus between the two "radios" the same way
as in "standard" SO2R; using the arrow keys or [Keypad *]. However, dual keyboards may also be used.

It is common practice to run (i.e. call CQ) on the main VFO (left ear) and do S&P on the sub VFO (right ear).
One of the reasons for this is tradition but another is that RIT is only supported on the main VFO on many radios.

More information about operating SO2V can be found in the SO2V menu item section.
On selected radios (such as more advanced ICOM radios), automatic VFO knob focus and sub receiver control
is supported. (C.f. the supported radios section.)

Important: RTTY SO2V requires the use of FSK together with a radio controller that offers two
FSK keying COM-ports for the same radio, such as the microHAM series of keyers.

It is also possible to use SO2V with single-receiver radios. There is a benefit in having separate band
map for each VFO and being able to rapidly switch between VFO A and B.

SO2V only works for Radio 1 in the Options|Configure interfaces panel.


So2v-cqww.png


More information about the four possible techniques can be found in the operating technique section.

Standard messages

A fundamental feature of a contest logger is the ability to send predefined messages.

DXLog has two types of predefined messages; the Standard messages and the Additional messages.

The standard messages contain two sets; one for RUN and one for Search & Pounce.

You reach the configuration panel for the standard messages with Options|CW/Digi|Modify standard messages or the text command MSGS.

Each standard message is associated with a function key; [F1] to [F7], [Insert] and [+].
In this wiki, they are also referred by these names.

The use of each message follow a long standing tradition in contest loggers and since functions in DXLog (e.g., ESM and DVK) assume
the messages are used this way, do not use them differently unless you know exactly what you do.

Contest loggers' tradition
Message Use
F1 CQ (RUN) or own call (S&P)
F2 RST and contest exchange
F3 Contest exchange
F4 Own callsign
F5 Other station's callsign
F6 Request for repetition
F7 Query (CW) or QRZ (digital)
Insert Make QSO. Conclude QSO in S&P.
Plus Confirm QSO. Conclude QSO in RUN.

When creating a new log in DXLog, the standard messages are automatically populated.

Below is one example.


Standard messages cw2.png


The messages are composed by regular letters and numbers, special characters, and macro commands.
Macros always start with a dollar sign, e.g., $RST, $LOGGEDCALL, or $CORRECT.
Special characters are mainly used to control the CW keying, e.g., ^ means a half word space
and + means an increase of the CW speed by 4WPM.

A full list can be found in the macro commands and special characters section.

Since the exchange, CQ etc. varies between contests, every contest has its own set of default messages.
These default messages are however only used the first time a log is created for the particular contest.
To allow customization, all following logs created for a particular contest use the messages from the
last time a log was saved for this contest. This means that you never have to repeat customizations
such as adding $CLEARRIT to your CQ macro, etc. There is a very large repertoire of macros available.
You can even call own scripts in the message using the $!scriptname syntax.

You can always return to the default messages by clicking the Defaults button. This can also be helpful
when switching "role" from a previous time you participated in the same contest, such as member/non-member,
IOTA station/non-IOTA station.

Important: If you run CW and want to secure good spotting by the Reverse Beacon Network, do not use speed changes
in your CQ message. Short calls (4 characters or less) should typically be repeated.

A complete list of macros and special characters as well as the very powerful conditionals syntax
can be found in the message macros section.

Space characters in the beginning or end of the message are always ignored. To introduce a delay, use $DELAY.

Voice memory playback

In phone contesting having a means to transmit a pre-recorded CQ message is a great help.
Sometimes for other messages too.

DXLog has a built-in voice recorder (often referred to as a DVK - digital voice keyer) but also supports the
use of that built into many radios. (More information can be found in the Digital Voice Keyer section.)

Important: If you use the radio's built in voice keyer, make sure to check the box
"Don't set PTT when using voice keyer" on the COM port controlling your radio's
PTT to avoid a self-locking PTT loop.

If you want to use ESM (see the ESM section) also on phone the message number convention
from CW and digital modes need to be followed.

Voice memory convention
Message #1 CQ message. E.g. "SM7IUN, contest"
Message #2 S&P exchange, when the contest allows. E.g. "Roger, you are five nine fourteen"
Message #4 Own call. E.g. "SM7IUN"
Message #6 Request repeat. "Again, again?"

Important: On Phone in SO1R, SO2V, and SO2R, macro commands are only recognized in the INSERT and PLUS messages
and are ignored in messages 1 through 7. In SO2R Advanced, however, each used scenario needs to include the wanted
playback macros, $F1, $F2, etc.

Important: A useful message can be the one associated with logging the QSO in RUN. E.g. "Thank you and good luck, SM7IUN, contest".
However, for this to work, the RUN PLUS message must contain the macro commands to send a message and log. (e.g. $PBPLUS $CR).

Since the INSERT message i RUN contains the other station's call it can not be prerecorded.
Following the conventions above, the standard INSERT message will however work for S&P.

Useful settings

Since this is just a quick-start guide, only the most commonly used or misunderstood settings will be covered here.

Options|Load contest at startup

Guarantees that the right log file is opened after e.g. a power outage or a reboot.
Very important to enable in a multistation setting.
Opening the wrong log file while networked with other stations will force
a merging of the logs which normally is highly undesired.

Options|Interface specific options|Dual receiver radio (Use split in SO2V)

A very important setting for SO2V. Should be enabled for dual receiver radios and
disabled for single receiver radios.

Options|Interface specific options|Band change keys affect both VFO

Makes band changes with [Alt][F1] and [Alt][F2]
switch the band of the selected radio's both VFO. Recommended.

Options|Log|Show border on TX

Shows a colored frame around the entry line of the currently transmitting radio.
Recommended.

Options|Log|Show previous/current messages

Shows the current and previous messages sent on the screen.
Very convenient e.g. when running SO2R with low or no sidetone.

Options|Log|Show cursor in entry line without focus

Shows a shadow cursor in the unselected entry line. Highly recommended.

Tools|Data entry|Enable ESM mode

Makes [Enter] send relevant messages in both Run and S&P.
Also toggles with [Ctrl][M]. For for more details, see the ESM introduction.

Tools|Data entry|Enable Run/S&P switching

Allows switching between Run and S&P. Recommended setting unless in a DX-pedition.

Tools|Data entry|Enable automatic Run/S&P selection

Makes DXLog automatically switch to S&P when you move the VFO knob or grab a spot. Recommended.

Tools|Data entry|Exchange guessing|Automatic

When applicable, produces an exchange guess as you type.
Does the same also for dupe and new multiplier information.
Highly recommended.

Tools|Data entry|F1 forces Run mode

Makes the [F1] key always switch to Run, mark the CQ frequency and send CQ.
Recommended.

ESM

With ESM, or Enter Sends Message, which the acronym stands for, there are different schools.

DXLog has a very straightforward and deterministic ESM. It is stateless which means that it
does not try to guess the intentions of the operator based on past actions.

The message sent by [Enter] only depends on three factors:

Operating state (Run or Search & Pounce)
The location of the cursor
The content of the current field

This makes DXLog's ESM very predictable and easy to learn.

Since ESM may be undesired on Phone the option Tools|Data entry|ESM mode only for CW
allows you to use it only for CW in e.g., a mixed mode contest entry.

DXLog ESM assumes the following configuration of the standard messages:

RUN F1 - CQ message
RUN F6 - Request exchange
RUN INSERT - Send other call and exchange
RUN PLUS - Send corrected call if required, log and send semi-CQ (such as own call)
S&P F1 - Own call
S&P F6 - Request exchange
S&P INSERT - Send exchange and log

The function is as follows:

Run

Pressing [Enter] in RUN will:

  • with the cursor in an empty callsign field send RUN F1, typically CQ
  • with the cursor in a partially or correctly filled callsign field send RUN INSERT
  • with the cursor in an incorrectly filled exchange field send RUN F6
  • with the cursor in a correctly filled exchange field send RUN PLUS

Important: If a number server is used, serial number reservation must be correctly configured.

When the party station has received the exchange correctly, focus is shifted to the exchange
field by pressing [Space]

For a large station, where correct reception of the exchange is (almost) guaranteed, you can
automatically shift focus to the exchange field after having sent the exchange by enabling the
menu option Tools|Data entry|Focus received exchange after sending exchange in Run.

Search & Pounce

Pressing [Enter] in S&P will:

  • with the cursor in the callsign field send S&P F1
  • with the cursor in an empty or incorrectly filled exchange field send S&P F6
  • with the cursor in a correctly filled exchange field send S&P INSERT

Important: If a number server is used, serial number reservation must be correctly configured.

For a big gun station, where correct reception of the exchange is (almost) guaranteed, you can automatically
shift focus to the exchange field after having called the station by adding the $SPACE macro to the S&P F1 message.

You can find more information on ESM in the Data entry menu section.

Connecting to the DX cluster

DXLog offers two ways of connecting to the DX cluster, one basic, included in DXLog, and one advanced,
relying on a companion program.

Important: If your current log is unassisted (either by selection or since the contest rules generally
forbid assistance), DXLog will not display any cluster spots, even when connected.

Basic connection

Since an increasing number of contests allow self-spotting, also on unassisted entries, DXLog always allows
connecting to the DX cluster but does not display incoming spots when the log is set to an unassisted entry category.

DXLog's default cluster node is VE7CC. If you prefer another node, you click Options|DX cluster|Edit connection list.
This opens a window that allows you to edit existing entries, add new ones, and select a new default node. (More HERE).

If you get lost editing the list, you can always reset it to "factory" settings with Options|DX cluster|Reset connection list.

Checking Options|DX cluster|Reconnect default cluster node at startup will make sure you are always
connected when running DXLog.

You connect by clicking Commands|DX cluster|Connect default or Connect other.
This will bring up a dialog with your default login information. Its content is remembered by DXLog between sessions.

Clicking Windows|DX cluster monitor or pressing [Alt][O] will bring up a window that shows the
telnet text flow from the cluster node. Although meaningless to use for catching spots, it can be used to make sure
the connection is correct and see error messages if the login procedure fails.

Spots should now start appearing in your bandmap.

DXLog will only display spots of the mode or modes relevant for your contest entry.

Advanced connection

If you are in a multi-station setting and want to separate the cluster connection from your operating positions or
have a need to connect to multiple spot sources, you can use the DXLog.net.DXC companion program.

DXLog.net.DXC distributes spots on a LAN to one or several instances of DXLog via the normal DXLog multi-station
networking protocol. This means networking must be enabled and correctly configured.

Make sure Options|Enable network is checked and that "networking for multiple stations" is checked in the
network configuration panel. Also make sure that the station's networking IP address is correct. It should typically
be the computer's IP address with the last number replaced by 255.

DXLog.net.DXC offers a rich set of features including blacklisting and skimmer control. More information can be found HERE

In DXLog.net.DXC, enter your callsign by clicking Settings|User data. Also check your network settings
under Settings|Network. For a single station setting, you can click the Local defaults button which will not
send spots outside your computer. Clicking LAN defaults will distribute spots to your entire LAN.

The checkbox Cluster cmd should be checked for at least one cluster connection.
This checkbox controls to which nodes commands from DXLog (such as self spots) are forwarded.

You connect to the cluster node by clicking the Connect button.

If everything is correct, you should now see spots arriving in the Windows|DX cluster monitor window on all networked stations.
If the current log's category is assisted, they will also appear in the bandmap.

If you are running DXLog.net.DXC on a separate computer or server and want to establish all cluster connections automatically
when DXLog.net.DXC is started, check Operating|Connect all tabs at startup.

The bandmap and other windows

Beside the entry lines, the bandmap is one of the most central functions in a contest logger.
The two bandmaps are enabled with Windows|Radio 1 and Windows|Radio 2.
(Note that only one is available in SO1R.)


Bandmaptherm.png Bandmaplist.png


With an internet connection to the DX Cluster you will see the spots spread out over an intuitive,
thermometer-like representation of a part of the current frequency band or as a color-coded listing.
You can either let DXLog connect directly to the DX Cluster (as described in the DX Cluster section)
or via the DXLog.net.DXC cluster connectivity utility, described in the DXLog.net.DXC section.

The bandmap can be set up to convey a large amount of useful information such as if a spot represents
a new multiplier, if it has been worked before, a suitable antenna direction, the sun's position at the
station's location etc. You can quickly jump between spots by holding down [Ctrl] while pressing
the up and down arrow keys. (There are many more keyboard shortcuts associated with the band map, for more
details, see the keyboard functions section.)
The bandmap can be zoomed in and out using the scroll-wheel on the mouse. The settings are available by right-clicking
the bandmap and selecting Properties. Further information about the bandmap can be found in the bandmap section.

The bandmap is also very useful when operating without a DX cluster connection, a.k.a. unassisted.
You can add stations to the bandmap by entering the call and pressing [Ctrl][Enter].
Such manually entered stations are automatically erased when worked in Run.
Stations worked in S&P are also added to the bandmap to avoid you having to identify them again.

Important: The bandmap contains some S&P features, such as wiping the currently entered call and/or adding an
entered call to the bandmap when tuning away from it, that are active also with no bandmap window open.
You find these settings by selecting Properties in the bandmap context menu.

In the Bandmap properties panel you will also find the spot lifetime settings. These control how long a spot will
be displayed before erased. A suitable number for cluster spots is 11 minutes for CW and RTTY (RBN has a respotting
timer of 10 minutes) and 20 minutes or more minutes for phone and other digital modes. For manual spots, 30 minutes
is a reasonable number.

Besides the bandmap there are many useful windows available. DX cluster announcements can show you a
list of all valuable spots as one single list.

Check Partials and Check N+1 helps you guess callsigns you are unsure of. Check Multipliers gives
information on which bands you have worked a certain multiplier.

Finally Clock is a very helpful little bar showing essential information like exact time, operating
state, logged in operator etc.

After the contest

After the contest you typically want to create a Cabrillo or EDI file for submission and perhaps an ADIF file to
upload to LoTW or import in a bulk logger.

Cabrillo files are exported using File|Export|Cabrillo and ADIF files using File|Export|ADIF.
ADIF exports offers you the option to also include X-QSO, which you normally do not want to do. There however situations
when you may want to include them, such as when excluding valid QSO on another band for a single band contest entry.

If your contest uses a prefill database, and you trust your log, you can update the database using
Options|Data files|Update database. It is possible to update data files of any supported type.

Be however aware that your own updates will be lost the next time an updated database is included in a new DXLog release that you install.
If you really want to preserve your updates, make a copy of DXLog's database in the same folder as the log file.
More on how to manage prefill databases can be found in the prefill database settings section.

Entering postcontest mode with Edit|Postcontest mode will allow you to edit all properties of the logged QSO using [Alt][F]
and [Ctrl][F1]/[Ctrl][F2]. It also allows entering a paper log by opening the time field for direct entry.

Tips and tricks

  • Try the world map. It will show where you are spotted on the DX cluster.
  • Try SO2V. You will have more fun and become a an even more productive operator.
  • Get acquainted with ESM. Once familiar with it, you will find it very convenient.
  • If you connect to the DX cluster and see no spots in your bandmap, make sure you
    are not using an unassisted contest entry.
  • On most radios [Shift][Up] and [Shift][Down] work as RIT in Run
    and frequency adjustment in S&P.
    [Shift][Delete] zeroes RIT regardless of operating mode.
  • [Ctrl][Up] and [Ctrl][Down] jumps between spots in the bandmap and
    grabs them onto the focused entry line.
  • [Ctrl][Space] grabs the spot in the bandmap on or close to your current frequency.
  • [Ctrl][Alt][Up] and [Ctrl][Alt][Down] jumps between spots in the other VFO or radio,
    depending on if Operating|Bandmap|QSY Opposite radio instead of 2nd VFO is checked or not.
  • [Shift][Ctrl][Up] and [Shift][Ctrl][Down] jumps to the next spot that is a multiplier.
  • Double-clicking a spot in the bandmap grabs it. There is a menu option change this to single click.
  • [Ctrl][Enter] creates a spot using an entered callsign and the focused radio's frequency.
  • [Alt][K] opens a panel for sending CW or a conversational digital mode directly
    from the keyboard. It is closed by pressing [Alt][K] or [Enter].
  • [Ctrl][Alt][+] or [Ctrl][Alt][Keypad +] forces a QSO to be logged,
    disregarding all validity checks.
  • Pressing [Ctrl][X] with the cursors on a QSO in the log will "delete" the QSO by marking it invalid.
  • [Shift][Ctrl][F1] shifts focus to radio 1, switches to Run, and sends CQ in SO2R and SO2V.
    In SO1R and SO2R Advanced it just sends the F1 message.
    Depending on your operating preferences you may want to redefine [F1] to always execute this key.
  • [Alt][Q] activates "intelligent quick QSL" which is a great convenience for
    DXpeditions and large contest stations. It uses rate statistics to send a short confirmation
    at the end of each QSO but still regularly send the full callsign.
  • The text commands RELOAD and RELOADNOW reloads and rescores the current log.
    The latter skips the confirmation popup. (This command also refreshes contest definitions
    and scripts without event handlers.)
  • RESET eller [Ctrl][Alt][R] resets all hardware interfaces.
    When connecting/disconnecting equipment or in the presence of EMC or RFI issues, this can be very helpful.
  • To search for a certain callsign in your log, type the callsign in the entry field.
    The Check Callsign window will show you which bands you have worked the callsign on.
    Double-click the red checkmark to jump to the corresponding QSO in the log.
    Return to the entry line with [Ctrl][End]
  • Holding down [Ctrl] during start-up of DXLog will give you the option to not restore the
    previous layout and log file.
  • On many contests you can do a reverse look-up from a prefill data file by entering the exchange
    and pressing [Space]. This will show the candidate matches in the Check Partials window.
  • On many contests where the exchange is a grid, you can type a six-character grid in the callsign
    entry field and press [Space] to get distance and azimuth.
  • If you have problems starting DXLog, as a last resort go to the folder %appdata% using
    the [Win][R] key and rename the DXLog.net folder. Then try again.

DXLog system files

Log and export files can be stored anywhere on your computer but in line with
Windows' application programming standard, DXLog keeps its internal system files
in a special, normally hidden, folder.

This folder can be opened either via Windows' file explorer, using the symbolic address
%appdata%\DXLog.net or using DXLog's menu item File|Open configuration folder.

Important: The only real need a regular user has to open this folder is to install contest or
database updates between regular DXLog releases or at emergencies.

Updates to contest definitions and/or databases are better updated by clicking File|Update contest.

The content of the configuration folder is the following:

  • Folder Contest
contains a working copy of all contest configuration files.
  • Folder Database
contains a working copy of all database, country, warning and regexp files.
  • Optional folder CustomForms
when exists contains custom form DLL files.
  • File DefMsgs.sdb
Default messages for all contests operated. Not editable.
  • File deftest.dxl
Default contest configuration. Not editable.
  • Optional file DXCSpotHistory.txt
Result of checking "Incoming spots logging" in DX Cluster announcement window.
  • Optional file DXCStreamHistory.txt
Result of checking "Stream logging" in the DX Cluster monitor window.
  • File DXLog.net.config.backup
A backup copy of the most recent working DXLog.net.config
  • File DXLog.net.DXC.config
DXLog.net.DXC configuration data
  • File DXLog-debug.txt
Crash and error logging file
  • File SERIAL-TRACE-...
Serial communications debugging log