Difference between revisions of "Menu Options"

From DXLog.net
Jump to navigation Jump to search
(Update database)
(Configure network)
Line 758: Line 758:
:: (Except support stations as these stations do not log).
:: (Except support stations as these stations do not log).
:: The number server must be used also for SO2R in contests that requires chronological serial numbers.  
:: The number server must be used also for SO2R in contests that requires chronological serial numbers.  
:: See also
:: See also the [[Menu_Operating#Advanced_SO2R|section on operating advanced SO2R]].
==Network is enabled==
==Network is enabled==

Revision as of 17:41, 23 November 2020

Load contest at startup

  • Enabled
If checked last opened log will be opened automatically when DXLog is started.
  • Disabled
If checked, DXLog is started but no log is opened.

Automatic backup

When clicked, this will open the log automatic backup settings window. Here parameters for log automatic backup can be set according to the user's preference.

Auto backup.png


Chooses the user interface language.

Keyboard selector

This option allows the assignment of a different keyboard to each entry line which is
highly recommended for advanced SO2R but also useful for advanced users in SO2V.

NB. Dual keyboard in SO2V only works for dual receiver radios and
Options|Interface specific options|Use SPLIT command in SO2V technique checked.

To use this feature you (obviously) must have more than one keyboard connected to the PC.

Select Options|Keyboard selector. A window opens showing the current keyboard assignment.

Keyboard select default.png

Now click on Define. A popup will appear asking you to identify the Radio 1 keyboard.

Keyboard select keyboard 1.png

This keyboard will be assigned to the Radio 1 (upper) log entry line. Press any key on keyboard 1.
Now press any key on the keyboard to be assigned to the Radio 2 (lower) entry line. If successful,
the form will show some cryptic identifiers for the keyboards.

If you really do have separate keyboards ensure that the identifiers are different.
It is possible to use one keyboard and assign it to both positions, which will show as the same
identifier for both Radio 1 and Radio 2. The form should look something like this:

Keyboard select success.png

Now click OK to save your assignments and close the window.

If you find that something doesn't work or need to reset to the default Any Keyboard configuration, open
the Keyboard selector form and select the Reset button. Click OK and any previous keyboard assignments will be removed.


  • No sound
Text command: SOUND and NOSOUND
Off by default. When checked, no CW side tone will be produced.
If a smart keyer (e.g. WinKey) is configured on any of the interfaces, this function is disabled.
  • Enable different R1/R2 speed
Text command: SYNCCW and NOSYNCCW
If checked, allows the CW speed to be independently set on Radio 1 and Radio 2.
  • Speed
    • Decrease [Alt][F9]
      Decrease active radio CW speed by 2 WPM.
    • Decrease other [Shift][Alt][F9]
      Decrease inactive radio CW speed by 2 WPM.
    • Increase [Alt][F10]
      Increase active radio CW speed by 2 WPM.
    • Increase other [Shift][Alt][F10]
Increase inactive radio CW speed by 2 WPM.
  • Modify standard messages
Text command: MESSAGES or MSGS
This option is used to edit the contents of all standard F-key, INS and PLUS messages
for RUN and Search & Pounce mode.

Standard messages cw2.png

Any edited content is saved for the currently selected contest and will be used for
any new log for the same contest.
If you want to reset all messages back to their default values for all contests, click
File|Open configuration folder and delete the file called DefMsgs.sdb.

Standard messages options2.png

The Options tab allows the setting of additional message options:
$QSOB4 macro
This text will be sent if $QSOB4 macro is activated due to a duplicate QSO.
NB. The use of QSOB4 mechanics in contests is a heritage from paper log days and not a recommended practice.
Only use RUN messages
DXLog will use only RUN messages, even if you switch mode to Search & Pounce.
Sprint Exchange Logic
This setting is applicable only for contests where Sprint Exchange Logic is enabled in config file.
When this option is checked, if the operator presses the INSERT key, DXLog will send the INS message in RUN mode if the
received serial number field is empty. Otherwise, DXLog will only send the INS message in Search & Pounce mode.
  • Modify additional messages [Alt][C]
Define or edit additional CW/Digital mode messages which can be invoked in a macro using commands
$MSG1..12 or by pushing keys [Ctrl][Alt][F1..12]


While the window is open, pressing [F1] through [F12] will send message 1 through 12 and then close window.
Content of additional messages are saved in the DXLog config file and is thus common for all contests.
  • Serial number
    Chooses serial number abbreviation type when sending serial number during the contest.
    Available options are:
    • Leading zeros: When checked, leading zeros are sent (for example 001 instead of 1).
      Text command: LZ and NOLZ
    • Use 'O' instead of 'T' for zero: When checked, all number 0 are replaced with the letter O.
    • Not abbreviated: When checked, all numbers are sent without any abbreviation.
      Text command: NOABBREV
    • Half abbreviated: When checked, all number 0 are replaced with the letter T.
      Text command: SEMIABBREV
    • Abbreviated: When checked, all numbers 0 and 9 are replaced with the letters T and N.
      Text command: FULLABBREV
    • Pro: When checked, all numbers 0, 1, 4, 5 and 9 are replaced with letters T, A, V, E and N
      Text command: PROABBREV
    • Custom: When checked the Custom Abbreviation table will be used to substitute characters
    • Set custom abbreviation table: Enables editing of substitutions character by character
      When clicked, a form will open to allow assignment of character substitutions.

Custom cw digi abbreviation table form.png

Add Adds a new substitution. First enter the character to be replaced. Then enter the character to be used in its place.
Delete Removes the currently selected substitution.
OK Saves changes and closes the form
Cancel Discards changes and closes the form
  • Shortened spaces (CT spaces)
Text command: CTSPACE and NOCTSPACE
When checked, shortened spaces will be activated (CT style). A shortened word space is 5 units instead of normal 7.
  • Remap keys in keyboard mode
When checked, keyboard remapping will be active also when sending CW/RTTY text in keyboard mode.
  • Work dupes
When checked, the $QSOB4 message will not be sent if QSO is a dupe.
Checked by default. It is generally a bad practice to not work dupes in a contest.
  • Speed limits
Sets the minimum and maximum CW speeds that can be selected by the increase/decrease speed menu options and keyboard shortcuts.
  • Add spacing when stacking messages
Adds a word space when pressing two F-keys in rapid succession.
Enabled by default.
  • Use smart double buffer
If Winkey is attached, this option sends 2 characters to the Winkey before waiting for a response,
which means that DXLog will always be one character ahead of the attached Winkey.
Enabling this option may also solve some compatibility issues with Winkey clones that are not 100% K1EL compatible.
  • Auto sending
Text command: CWAUTO and AUTOCW
When enabled and the mode is CW, DXLog will autosend the INSERT message after 3 or 4 characters of
the callsign have been typed into the log callsign entry field removing the need to press the insert key during a QSO.
For example, you're operating in run mode..
Now 9A5K is calling you..
You're typing in callsign field: 9A5 ... as you've typed "5", DXLog starts the INSERT message. in meantime you press K completing the
callsign.. So DXL will send 9A5K 5NN 001 without pressing the insert key
  • Enable smart correction
When checked, DXLog will send only the part of the callsign that was corrected.
Example: if you correct W6ABB to W6ABC, only ABC will be sent by the $CORRECT macro.
  • Copy hour in received QTCs
When checked, the two hour digits from the previous line will be automatically
copied to a new line in the receive QTC window.

Configure interfaces

Text command: SETUP


DXLog currently supports interfaces for up to 8 COM ports and one LPT port.
To use any of the ports to connect to the hardware and perform a function,
you must enable the port by checking "Enabled" box.

Serial ports

DXLog can communicate with up to eight devices; peripherals or radios.

For each device, you can select to use a COM port or a "pipe".
COM ports can be in the range of COM1 to COM40.

There are two types of "pipe" connections; OTRSP and WINKEY.
These are direct connections and do not rely on a COM port for communication.
You can only have one of each of these.

You can not select the same COM port for more than one interface.

Apart from communications interface (COM or pipe) the device type needs to be selected (Winkey, Radio, etc.).
Additional settings for the device are available by clicking on the setup button on the far right.

The "-" port type

The "-" device type is a COM port where only the hardware handshake signals are used, such as keying or PTT.

It does not have a defined bit rate, which may cause problems in some cases, such as when
used with a microHAM virtual COM port.

To make sure a port used for only keying is opened at the right speed do the following:

Open the interface configuration panel.

  • Select the wanted port and check the enable box.
  • Select it as Radio 1 and click Setup.
  • Select a random radio model and set the correct speed.
  • Set the wanted keying (e.g. CW = DTR, PTT = RTS, Foot switch, Active with Radio 1, etc.)
  • Click OK
  • Change from "Radio 1" to "-". Do not click Setup.
  • Click OK


Be sure to select 1200bps for older, serial Winkey for proper operation.


This device type will support also other microHAM keyers. Serial speed and handshaking signals are ignored when
connecting to a microHAM USB device router virtual COM port.


Software PTT (commands X1/X0) is available only with "pipe" connection, otherwise disabled.

Digital Voice Keyer

The Digital Voice Keyer (DVK) section allows a PC audio card or adapter to be used to record and
play back SSB DVK messages.

For radios where it is supported, it is also possible to use the voice keyer built into the radio.
The radio's built-in voice keyer is enabled in the radio settings.
Also, see the supported radios section for more information.

If you have a microHAM keyer controller, its built-in voice keyer may also be used.
The microHAM voice keyer is enabled in the MK2R+/MK2R/u2R settings.

It is important to not enable more than one of these three voice keyer options.

To use DXLog's voice keyer:

  • Check the enable DVK box.
  • Select the relevant DVK playback device (audio from this device is physically connected the the radio audio input).
  • Select the relevant DVK record device (Usually a microphone connected to the PC microphone or line input).
  • Enable the DVK using the tick box.
  • Select muting as required.

The built-in DVK in DXLog will support up to nine different messages: 1, 2, 3, 4, 5, 6, 7, INS, and PLUS.
NB. Your external voice keyer may support fewer.

Recording the messages is done by pressing [Shift] and the wanted function key.
With no operator logged in, the recordings are stored in WAV format in the folder %appdata%\DLog.net\Ops.
The filenames are 1.WAV through 7.WAV, INS.WAV and PLUS.WAV.
If an operator is logged in, the recordings are located in a subfolder with the operator's callsign.

The INS and PLUS messages have no key association and can only be played back by a macro.
$PBINS plays back message INS (#8 on external devices) and $PBPLUS plays back message PLUS (#9 on external devices).

The voice keyer can be used with ESM if DXLog's message convention is used.
It is described in the getting started section.

SO1R, SO2R, and SO2V

Messages #1 to #7 are played back by pressing function keys [F1] through [F7] regardless of
operating mode; Run or S&P. The [Insert] and [+]/[Keypad +] keys have no association
with a voice memory but "sends" the standard message associated with the key, regardless of mode; SSB, CW or Digital.
They are also mode sensitive and will send the standard message associated with the key and operating mode; Run or S&P.

In SSB mode, all macros sending CW or Digital characters are ignored. In CW, the $PBINS and $PBPLUS macros are ignored.
This means that you can create standard messages for the [Insert] and [+]/[Keypad +] keys
that works for a mixed contest, i.e. both for CW and SSB.

The example below is for Worked All Germany in the Mixed class.


Advanced SO2R

In Advanced SO2R, the function keys [F1] through [F7] are not directly associated with a
voice memory but instead executes the active scenario's macro string associated with the key.
More information on creating and using SO2R scenarios can be found in the SO2R Scenarios section.

The message/playback macros $F1 through $F7 are mode sensitive. The $PGBINS and $PBPLUS are not.
In SSB e.g. $F1 plays back voice memory #1, in CW and Digital it sends the F1 standard message so
there is no problem using Advanced SO2R also in a mixed mode contest.

Radio polling rate

The two Polling rate text boxes determine how often DXLog requests information from the radio over the CAT interface.

A good starting point is 300ms but this can be reduced for high speed interfaces (38.4kbps and above).

It is important to know that DXLog sends three poll requests per period, i.e. with a setting of 300ms,
one poll request is sent every 100ms.

Particularly with ICOM, which has a duplex CAT interface, you may experience slow or even missing response
from the radio if the polling period is set too short since DXLog's polling will fill up the capacity of
the CI-V interface.


  • PTT lead delay determines the time between PTT activation and start of transmission
  • PTT tail delay determines the time between end of transmission and PTT deactivation
  • PTT seq delay determines the time between activation of the four available PTT signals: PTT, PTT1, PTT2, and PTT3.

Printer port configuration

To use the parallel printer port (i.e. LPT port), it must be enabled by checking the "Enabled"
box in the interface configuration panel's Printer port section.

Additional data for printer port are configured by clicking Setup in printer port group.

Antenna selection with up to 16 different antennas is supported.
For multi-band antennas, the covered bands should be entered as a comma-separated list as in the example below.
The operator friendly antenna name in the Description column is used in the Antenna selector window.

For more information on antenna selection, see the Antenna selector section.

Dxl printer port config.png

Radio configuration

If a COM port is configured as a radio interface, click on 'Setup' to open the Radio Setup form.
In addition to the generic settings, several radio specific options are available.

Radio setup form3.png

  • Radio
Select your radio model. If it is not in the list, feel free to contact the development team.
Note that many times a similar radio model can be successfully used.
E.g. many Chinese QRP radios use the Kenwood protocol.
  • Speed
For best performance, use the highest available speed on your radio's CAT interface.
If there is an "Auto" speed setting, do not use it. It is strongly advised to use a virtual USB CAT port, if available.
Note that on modern ICOM radios it is necessary to "Unlink" the two CAT interfaces to achieve maximum speed.
  • Bits, Parity, Stop
Set according to the recommendations in your radio's documentation.
  • ICOM CI-V address (hex)
This is by default set to the selected ICOM radio model's factory setting.
If you change the address in your radio's settings, this has to be set to the same value.
  • Use radio's internal voice keyer
Enables the use of the built-in digital voice keyer on supported radio models (E.g. Elecraft, later ICOM, some Yaesu).
NB. If the Enable DVK option is checked in the Port Configuration panel,
this setting has priority and the radio's DVK will not be used.
NB. Due to limitations in the CAT command repertoire for some radios, DXLog may
not be able to track the radio's transmit/receive state. You can use the
Options|Log|Show border on TX menu option to determine if this is the case.
If DXLog can not determine the radio's transmit state, this means 1) software interlock in a
multi-radio setting will not work reliably with the radio's DVK, and 2) CQ autorepeat will not work.
NB. Make sure the option Do not use PTT with voice keyer is checked for
any device controlling the radio's PTT. If it is not, DXLog will assert the PTT at the start
of DVK playback and then wait for it to be released, which obviously will never happen.
  • Use CAT PTT command on PHONE
Uses a CAT command to switch between receive and transmit on phone, instead of a
COM-port or LPT signal.
  • Use CAT PTT command on CW
Uses a CAT command to switch between receive and transmit on CW, instead of a COM-port or LPT signal.
Only use this option as a last resort. Since the time to convey the command to the radio is not
insignificant, you may need to increase the PTT lead time to avoid hot-switching or lost leading dits.
  • Use ICOM CI-V "Transceive" mode (reduced polling)
An ICOM specific feature where "CI-V Transceive" must be enabled on radio.
Can offer an improved user experience at lower speeds (e.g. 19200bps) but comes with some limitations.
Some simple USB-to-serial adapters may suffer from CAT interface lock-up because of CI-V bus collisions
due to the large amount of data transferred.)
The recommended setting for modern ICOM radios is to have this feature disabled, an interface rate of 115200bps,
"CI-V Transceive" enabled in the radio's set up menu, and polling rate of 200ms. USB Echo Back should be off. (Important).
  • Control FlexRadio DAX on Phone
Intended for remote operation with e.g. Maestro. Will enable DAX during DVK playback but keep it off otherwise.
  • Use radio DATA mode for voice keyer playback
Switches the radio to data mode during voice keyer playback.
A valuable setting for radios that have a built-in sound card or only can use an external modulation input in data modes.
  • Always use radio DATA mode for any DIGI mode
If your radio has a DATA mode for RTTY/PSK/AFSK, checking this
option will force the DATA mode whenever a DIGI mode is selected.
  • Use transverter offsets
Opens up a configuration panel allowing setting per-band transverter offsets in kHz.
  • Do not poll radio during TX
Stop polling radio (stop updating frequency, etc.) during transmit.
For e.g. Elecraft this is a recommended option.
  • Reinitialize port after switching from TX to RX
Upon return to receive, reinitialize the COM port attached to that radio.

These last two options may be useful in cases where RF feedback are causing strange things to happen to a radio.
If these options seem to: clear up control problems, you may want to investigate adding bonding between the computer
and radio(s), and addition of ferrite suppression devices to cables.

Configure antenna server


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.
When using e.g. FSK RTTY, this option should be disabled. When using e.g. AFSK RTTY, this option should be enabled.
  • Prevent TX if another radio on the same band
If checked the Transmitter connected to this DXLog will have it's TX disabled if another radio on the network is on the same band.
  • Use Split command in SO2V technique
If checked (and the technique selected is SO2V) DXLog will send the Split command to change the transmit VFO.
NB. This is only intended for dual receiver radios.
Select this if you are using e.g. an Elecraft K3 with subreceiver, ICOM IC-7610, or IC-7851 for SO2V.
  • Use different bandmap background for active radio
If checked, the background color of radio 1 or radio 2 bandmap will be changed when the radio becomes active.
NB: the color used in this mode needs to be selected by using the Colors menu in the bandmap right click menu.
By default it is set to the same color as the normal background.
  • Round frequency to nearest kHz when sending from macro
If checked, the frequency sent by the $FREQS, $FREQP, and $FREQnn macros will be rounded to the nearest kHz.
If not checked, the frequency is rounded to the nearest 100 Hz. An 'R' is sent between the kHz and 100 Hz digits.
  • Automatically open/close digital window on mode change
If checked, the digital window for the active radio will be opened when a digital mode is selected.
If a non-digital mode is selected and the digital window is open, it will be closed. Note that the
contest configuration must allow both digital and non-digital modes in the same time period (mixed mode).
The digital window must be configured properly in the RTTY configuration form.
  • Sync radio 1/2 freq & mode
If checked, synchronizes the frequency and mode of physical radio 1 and 2. Does not synchronize VFO in SO2V.
This option requires radio auto reporting (e.g. ICOM "Transceive") to be disabled or oscillation will occur.
  • Change band of both VFO in SO2V
With this option checked, [Alt][F1] and [Alt][F2] will change the band of both VFO in SO2V.
  • Select first available antenna on band change
If checked, selects the first available antenna on band change.

RTTY configuration

Settings for RTTY decoder types and paths to decoders.

Rtty conf1.png

Up to two decoders can be used per audio channel (radio). Set the path to each decoder, please note that the decoder for each radio must be in a separate folder on the PC hard drive.

  • MMVARI Multimode - For MMVARI select MMVARI from the radio buttons.
  • GRITTY RTTY Decoder - To use VE3NEA's GRITTY decoder then select the tickbox, GRITTY must be installed and running, GRITTY uses it's own decode window, simply click on the callsign required in the GRITTY decode screen and it will be transfered to DXLog callsign input line.

Set the radio buttons for the correct RTTY decoder engine
Set the paths to the relevant RTTY decoder engines
Set tick box options as appropriate for your operation.

microHAM device configuration

Settings for integration with microHAM keyers and SO2R controllers


  • Enable microHAM device DVK
Enables the use of the microHAM devices's DVK instead of DXLog's built in DVK.
Supported for microHAM DKII, MKII, MKIII, MK2R, MK2R+, and u2R.
  • Footswitch is PTT
Enables the use of the microHAM devices's footswitch input for PTT.
On devices with more than one footswitch/PTT input, DXLog regards them as one.
No longer optional as of version 2.4.17 due to removal of this option in microHAM's firmware.
  • Enable TX lock/unlock
Enables control of the hardware transmit locking/unlocking built into the device.
Checking this will enable the software interlock in DXLog to act on all possible means
of transmission: Message transmission, PTT, Footswitch, and paddle*.
Mainly intended for multi-station interlock but can have other uses since with
this option checked, keyer PTT, Winkey BKIN*, and Footswitch status are recognized
by DXLog and is available e.g. for scripting or transmit/receive antenna selection.
*) Requires microHAM USB device router 9.3.0 or later.
  • Enable SW PTT
Enables the use of software PTT. With this enabled, DXLog will control the devices's
software PTT via the control interface. Can replace COM-port PTT but comes with some
latency so e.g. PTT lead time may need to be increased.
  • Dual radio device
Selects single or dual radio microHAM device.
Should be checked for dual radio devices such as microHAM MK2R, MK2R+, and u2R.
Should be unchecked for single radio devices, i.e. microHAM DIGI KEYER and micro KEYER, regardless of model.
  • Device without CAT interface
With this option checked, DXLog will force the operating mode of the device.
This is required for devices such as u2R which lacks a CAT interface and thus can not determine this by itself.
It can also be used for more advanced devices, such as MK2R+, if its CAT interface is not used.
Works for both single and dual radio devices.
NB. For digital modes, DXLog will not send any mode command to the device since DXLog is not aware if e.g. FSK or AFSK is used.
However, the $MK2R macro can be used to send commands to the microHAM device.
E.g. $MK2R=K1F $MK2R=K2F will set both radio interfaces in a microHAM u2R to FSK.
  • Operator logon selects DVK bank
With this option checked, logging on (using e.g. [Ctrl][O] or OPON) will select the DVK message
bank for this callsign. If there is no such memory bank defined, it is created.
  • RTTY is FSK
This option is only active for microHAM devices without CAT.
When checked, it will force the device into FSK mode in RTTY and Voice mode for all other digital modes.
If unchecked, the device will be set to Voice mode for all digital modes.
  • Radio 1 RX, Radio 1 TX, Radio 2 RX, and Radio 2 TX tabs
Each tab defines a rule for the two 4-bit BCD outputs on the ACC connector on the back side of the MK2R, MK2R+, or u2R.
The two ACC outputs are typically used for antenna or PA band selection but can have other uses too.
The location of the checked box is translated into a 4 bit binary pattern.
NB. This means only one box can be checked per row.
Please refer to the latest microHAM documentation for possible changes to this rule.
NB. The coding is not BCD. Check mark location number 1 means 0000, 2 = 0001, ... 13 = 1100, 14 = 1101, 15 = 1110, and 16 means 1111.
The bit pattern in the Radio 1 RX and Radio 1 TX tabs control the RADIO 1 ACC port and the Radio 2 tabs control the RADIO 2 ACC port.
The configuration allows up to 25 different band/antenna associations.
Having multiple antennas on the same band is supported.
For multi-band antennas you need to include a band line for each band it covers.
The 60m band has was added in release 2.4.15 so if not visible, clicking RESET will make it appear.
For information on antenna selection, see the Antenna selector section.
NB. To enable the use of different RX and TX antennas, Options|Interface specific options|Allow different TX/RX antenna
must be checked. The keyer's respective ACC outputs must also be configured for microHAM protocol control.
This is done in the ACC tab in the microHAM's Device Router set up as shown below.


OTRSP device configuration

  • Enable OTRSP device DVK
Enables the use of a digital voice keyer in the OTRSP device.
Supports recording and playback of up to nine messages, just like DXLog's built-in voice keyer.
  • Radio 1 and Radio 2 tabs
Each tab defines a selection of states for up to four four-bit Aux outputs. Unlike microHAM, any bit pattern is allowed.
Each state (i.e. line) associates a band with an antenna usable on that band.
The configuration allows up to 25 different band/antenna associations.
Each group of four pins is associated with an Aux output, as listed in the upper left of the panel.
It is possible to have several antennas for the same band.
A multi-band antenna needs to have one band-line for each band it covers.
The bit pattern presented to the Aux outputs is the combination (logical OR) of the currently selected antenna for each radio.
This means that if Aux 1 is used to control the antenna for radio 1 and Aux 2 is used to control the antenna for
radio 2, columns 5 through 8 must be unchecked for radio 1 and columns 1 through 4 must be unchecked for radio 2.
C.f. the example configurations below.
The 60m band has was added in release 2.4.17 so if not visible, clicking RESET will make it appear.
NB. The use of different antennas for transmission and reception is not supported.
For more information on antenna selection, see the Antenna selector section.

OTRSP Setup radio 1.png

OTRSP Setup radio 2.png

Winkey Configuration

Configure the WinKey properties
Text command : WKSETUP or WKEY


NB. If you are using a microHAM keyer, the below settings will only have effect if
the "Allow logger control" option is checked on the USB device router's CW/Winkey tab.

  • Keying mode:
    • Iambic A - Curtis A iambic timing
    • Iambic B - Curtis B iambic timing
    • Ultimatic - Non iambic mode
    • Dit
    • Dah
    • Bug (semi-automatic) - WinKey makes the dits and you make the dahs. Vibroplex style.
In either iambic mode, alternating dits and dahs are sent while both paddles are held closed.
In Iambic mode B, an extra alternate dit or dah is sent after both paddles are released.
In Ultimatic mode, when both paddles are pressed, the keyer will send a continuous stream of whichever paddle was last pressed.
  • Second Output (pin 5) (Not available on all WinKey products but useful for e.g. the WKmini to get keying right.)
  • Reverse - Reverses the dit/dah paddles (e.g. for keying with the left hand)
  • Autospace - If you pause for more than one dit time between a dit or dah, Winkey will interpret this as
    a letter-space and will not send the next dit or dah until a full letter-space time (3 dits) has passed
  • PTT - Enable PTT control from Winkey. Preferrably disabled on WKmini.
  • Sidetone - Sets or disables the sidetone frequency on keyers with speaker
  • Weight - Controls the weight of the transmitted CW. A setting of 50 means normal CW.
  • Use two Outputs - WinKey pin 5 keys a second radio. Enable with WKmini to key tip of connector.
  • Pot controls
    • Nothing: Winkey speed knob/potentiometer has no action
    • Paddle only: Winkey speed knob affects only paddle CW speed (Recommended)
    • Paddle and DXLog : Winkey speed knob changes both DXLog and paddle CW speed
  • Min Speed: Speed with potentiometer at minimum
  • Max Speed: Speed with potentiometer at maximum
  • Two wire: Makes the Winkey assume it is controlled by a 2-wire potentiometer. Rarely used.

MP3 Configuration

Sets the configuration for the MP3 encoder used by the Contest Recorder window.

Player is the output device, normally your PC speaker.

Recorder is the recording device, e.g. the audio device in your SO2R controller or the built-in soundcard in your radio.

Recordings are made in stereo, so both radio 1 and radio 2 (or the main and sub receiver) can be recorded.

The sample rate and coding rate can be set at different values. For normal purposes 8000Hz sample rate and
24kbps coding rate is sufficient and consumes the least disk space.


Rotator Configuration

DXLog supports rotator control using UDP communications to PstRotatorAz by YO3DMU and the EA4TX rotator controller.
Configuration steps are as follows:

PSTRotator DXLog config2.png

Check the "Enable Rotator communication" box at the top of the form.

Enter the required data in each column. Use the Add, Edit, and Delete buttons as required. Here are descriptions of each column:

  • Band
Value in meters for which this rotator is active. Comma-separated list if several.
  • Ant #
The number of the antenna for this band turned by this rotator, beginning at 1. Antennas are numbered in the order shown on the <t>Radio/Ant Status Window.
  • IP Address
If you are running PstRotatorAz or EA4TX on the same machine as DXLog, enter Otherwise enter the IP address of the rotator control server.
  • Port
The UDP port used to communicate with the rotator interface. Normally PSTRotator uses
12040 for the first rotator, 12041 for the second, etc. However, any port that is free can be used.
Write down the ports used as they are needed for PstRotatorAz or EA4TX configuration.
  • Send freq
Check this box if you need the radio frequency to be sent to PstRotatorAz.

Select the rotator software type from the drop down list, currently either PstRotatorAz or EA4TX

When completed, press OK.

To configure PstRotatorAz, you may need to refer to the PstRotatorAz manual. Here are the basic steps:

From the PstRotatorAz menu bar, Select Setup|Trackers Setup|DXLog/UR5EQF/LogHX Setup. The Setup form will be displayed:

Rotator tracker setup DXLog.png

Enter the port number used for this rotator in the Ethernet box. Select 'Azimuth' in the "Tracking by" box. Click Save Settings.

Select Tracker|DXLog from the PstRotatorAz menu bar.

In the main display, select 'Tracking' from the Mode box. Depending on the view you have selected, you may need to select
View -> Full View to see the Mode box. The following shows the location of the Mode box in PstRotatorAz:

PSTRotator tracking mode.png

If you have more than one rotator, repeat the steps on each instance of PstRotatorAz, using the appropriate UDP Port number.
See the PstRotatorAz documentation to enable multiple instances of PstRotatorAz.

Once you have everything configured, return to DXLog. Ensure you are on the appropriate band (and the proper antenna selected).
Enter a callsign or an azimuth value into the callsign field. Press [Ctrl][F12]. DXLog will show the value sent on the status line, and the rotator should rotate to the selected azimuth.

Enter a callsign and press [Alt][F12]. Rotator will turn to the long path azimuth.

This completes Rotator configuration.

Configure network

Network parameters form4.png

This form allows configuration of network addresses and identification.

Text command: NETCONFIG

  • Station ID
The name/identity of the station used in DXLog networking.
The name is used for e.g. software interlock, gab messaging, and passing.
It is recommended to use explanatory station names such as "SK3W_INBAND", "LZ5R_RUN1", etc.
If you intend to use some of the advanced macros such as $BANDID or $FREQID it is important
to avoid characters that have a special function in messages, such as '-' and '+'.
  • UDP network broadcast for multiple stations (checkbox)
    Enables UDB based networking. DXLog can use both broadcast-based UDP networking and client-server based networking.
    Note that UDP is a protocol without confirmation or retransmission and thus vulnerable to packet loss.
    Wi-Fi networking is not recommended for any contest station but if used, UDP networking should be avoided.
    • UDP network parameters
      IP address and port information for UDP networking. The Default button will enter the DXLog default parameters.
  • Start server (checkbox)
    Enables client-server based networking with this station as server.
    Only one server is allowed on the network. All other stations must have this box checked.
    • Server parameters
      IP address and port information for the multi station server.
  • No spots via client/server (checkbox)
    Spots will only be carried over the UDP network.
    Valuable feature when e.g. networking over WAN.
  • Connect as client (checkbox)
    Enables client-server based networking with this station as a client.
    • Client parameters
      IP address and port information for the client.
  • Live score UDP broadcast
IP and Port for broadcast of Live Score info.
  • DXC spots UDP broadcast
IP and port for broadcast of DX Cluster spot information. Up to three port numbers can be specified, separated by space.
For more information, see UDP broadcast.
  • Radio UDP broadcast
IP and port for broadcast of radio information. Up to three port numbers can be specified, separated by space.
For more information, see UDP broadcast.
  • Direction UDP broadcast
IP and port for broadcast of antenna direction information. Up to three port numbers can be specified, separated by space.
For more information, see UDP broadcast.
  • QSOs UDP broadcast
IP and port for broadcast of logged QSO information. Up to three port numbers can be specified, separated by space.
For more information, see UDP broadcast.
  • UDP broadcast listener
IP and port for listening to commands via UDP. Up to three port numbers can be specified, separated by space.
For more information, see UDP broadcast.
  • Other parameters
  • Network timeout (sec): timeout value for network connections.
  • Start time sync (checkbox)
Enable time synchronization between stations. No more than one station per network must have this option checked and
all other stations must run DXLog as administrator to allow adjustment of the computer's time.
To run DXLog as administrator, right-click the desktop icon and select the option.
  • Start number server (checkbox)
Enables the serial number server which allows multiple stations/radios to use serial numbers in chronological
sequence for contests that require this, e.g. CQ WPX.
No more than one station per network may have this option checked. (Usually the main run station)
Note: All stations must have Options|Networking|Use number server checked to use the server.
(Except support stations as these stations do not log).
The number server must be used also for SO2R in contests that requires chronological serial numbers.
See also the section on operating advanced SO2R.

Network is enabled

Enable or disable station networking
Text command: NETON or NET and NETOFF or NONET

NB. If you intend to use the number server for SO2R or in a multi-station setting it is not sufficient to only enable the network.
A network interface (UDP or client/server TCP) must also be enabled in the network configuration panel (see above).



Options networking menu.png

  • Synchronize CW messages
Force the CW/Digi messages on this station onto all other stations on the network.
  • Don't log QSO on this PC
When checked, QSO cannot be added to the log at this PC.
Instead, the callsign entered into the log entry callsign field will be added to the bandmap and the log entry callsign field will be cleared.
This option is usually used for Partner mode or operator training.
  • Software interlock
Text command: ILOCK and NOILOCK enables interlock
Text command: ILOCKON and ILOCKOFF disables interlock
Note: ILOCK and ILOCKON will only open the Interlock configuration panel when interlock is disabled.

Interlock options.png

When this option is checked, software interlock is active.
Transmit is only possible if the other networked DXLog stations allow it.
The Radio Status window illustrates blocking status through its background color.
Green means successful transmission, yellow means an interruptable block, and
red means an uninterruptable block.
NB. Messages sending "nothing" such as setting S&P PLUS
to only "$CR" may cause interlock deadlocks.
  • Interlock options
NB. These options are only available when software interlock is activated.
  • First one wins
No transmissions are interruptable. The station that first starts
to transmit is always allowed to complete its transmission.
  • Last one wins
All transmissions are interruptable. All stations can always
interrupt the transmission of another station. (Not recommended.)
  • Last one wins if msg not
All but a defined set of messages are interruptable.
  • Last one wins if msg is
Only a defined set of messages are interruptable.
  • If msg/is not selection
Selectable list of messages for more granular control of last one wins strategies.
Although it is considered a good practice to use symmetrical blocking strategies, i.e. having
identical settings in each participating station, it is possible to have different settings in each station.
If experimenting with this, keep in mind that the interlock strategy settings refer to the
behavior of blocked station, not the blocking station.
NB: For software interlock to work on Phone, a external PTT recognized by DXLog must be used.
The by far simplest solution is to use a footswitch connected to a microHAM device.
See the microHAM configuration section for more details.
It is also possible to connect a footswitch directly to the computer's RS-232 port, providing it has one.
How to do this is described HERE.
K3 settings2.png
  • Use number server
This option, when selected, enables the use of a number server. The purpose of a number server
is to allow all networked stations (or both radios in case of SO2R) to use serial numbers
in chronological order. The most well known contest with this requirement is CQ WPX.
Only one DXLog on the network can be the number server, all other DXLog must have this option unchecked.
When checked, the DXLog number server will be used to determine/reserve the next serial number.
The reservation of a serial number can either be done with [Space] by checking the option
Tools|Data entry|Spacebar reserves serial number or by including the $RESERVENR
macro in the F2 message. If the macro method is used, the Spacebar menu option must not be enabled.
Typically the first is preferred for SSB whereas the latter is preferred for CW.
Options|Networking|Use Number Server must be checked on all stations on the network that require
the use of serial numbers (which means all stations logging. Not supporting, non logging stations)
With Tools|Data entry|Spacebar reserves serial number set, number reservation from the server is made when
[Space] is pressed in the log callsign entry field.
If successful, the user will be notified in the main status window that the number has been reserved,
and the serial number will change colour (Default red).
If a number is reserved but the QSO is not made, number reservation will be revoked using the Wipe QSO command.
([Alt][W] or [F11]).
NB: if you are using the number server on a single computer (for SO2R) you should not enable
the server/client selections. Ensure that the "Start server" and "Connect as client" checkboxes
are unchecked. Simply check the "Start number server" box on the Configure Network
form and ensure that "UDP network broadcast" is enabled and configured with the broadcast address
for your computer's particular network setup. Selecting the "Default" button will determine the
proper broadcast address for you.
  • Show QSO status when blocking
Show QSO progress status ("CQ", "QSO", "EXCHANGE") instead of "MAN" on the blocked station when asserting PTT on blocking station.
Mainly intended for phone contesting. NB. This setting controls the message sent by the blocking station.
The rule for determining the status is:
  • If the call sign field is empty, the block request reason message is "CQ"
  • If the call sign field is not empty and focused, the block request reason message is "QSO"
  • If the call sign field is not empty and not focused, the block request reason message is "EXCHANGE"
  • Don't allow QSO logging if number isn't reserved
When using the serial number server, QSO logging will be prevented if a serial number is not reserved from the number server.
Also, when the number server is used and the reservation process has started, DXLog will show the active QSO NR as 000 until the new
reserved number is successfully received or the reservation is canceled.
  • Don't allow QSO logging if band change rule is broken
Only relevant when 10 min band change rule is used in a contest (E.g. CQ WW M/2 category)
When operating a contest in a Multi transceiver environment, this option will prevent the contest
band change rule being broken by stopping the mult station logging a QSO if the band change quantity has been exceeded.
Although intended to prevent contest rule violations, it is not recommended to enable this option.
  • Show different active QSO line colour during wait status
Only relevant when 10 min band change rule is used in a contest (E.g. CQ WW M/2 category)
When operating a contest in a Multi transceiver environment, this option will change the color of
the active log so entry line when the band change rule is violated.
Example: You make QSO on the mult radio on 40m band at 00:00Z.
In that case, you have to stay with mult station on 40m until 00:10Z when you are then allowed
to QSY to other band with the multiplier station.
If you do it earlier, or you have multiple mult stations, each of them will see the QSO line in
a different color until the 10 minutes has expired. By default the color is red, until last
minute when it changes to yellow... and after that it reverts back to the normal background
color of the logging screen.
In multi/single environment it is very useful for each operator to see if a QSO is allowed on
that band or not. It's easy, you just have to look at the screen, and if the log entry line is
red in color, you are not allowed to make a QSO. There are also timers visible in Status
window, when a QSY is allowed.
  • Don't allow QSO logging if operator isn't logged
If checked, logging is blocked if there is no logged on operator.
  • Show QSY notification in QSY Wizard
If checked, HamCAP will be automatically invoked when [Space] is pressed and
QSY recommendations will be shown in the QSY wizard window
  • Use optimistic interlock blocking method
Applies to software interlock. If a "blocking allowed" confirmation is not received from all
stations requested before timeout, assume that all relevant stations are blocked and start transmission.

DX Cluster

Dx Cluster telnet settings and options


  • Spot handling policy
Introduced in version 2.4.3. Controls how incoming spots (local and cluster) are handled.
This menu option is only available with an active log.
Three options are available:
Standard - The normal setting that only keeps one copy per band and mode of each spot.
However, also erases all spots less than half a spot bandwidth (as set in bandmap properties) away from a new spot.
This will provide a sparser spot view with only the most recent spots visible and never more than one spot per frequency.
Preferably used with a narrow spot bandwidth.
Pro: Only shows the most recent spot on each frequency.
Pro: Spot grabbing with arrow keys will grab all visible spots.
Con: In Run you will not be warned if a station you can not hear, e.g. in your skip zone, is calling CQ on your frequency.
Con: In a busy, global contest, the band map content can be somewhat volatile.
Prior to release 2.4.3 this option was called "Bandmap type: Standard".
Complete - A more forgiving setting that also only keeps one copy per band and mode of each spot.
Erases no spots with the exception of previously worked spots less than half a spot bandwidth (as set in bandmap properties) away from a new spot, to reduce clutter.
Preferably used with a shorter setting of "Spot lifetime". Mathematically equivalent to setting spot bandwidth to zero with "standard" policy.
Pro: Provides a complete picture with no risk of missing valuable spots.
Con: Spot grabbing using arrow keys will only grab one spot per frequency.
Prior to release 2.4.3, this policy was called "Bandmap type: Inband"..
None - All spots are kept. Mostly for testing purposes since it will result in an increasingly cluttered bandmap.
Resembles "Bandmap type: Multiplier" option prior to release 2.4.3.
  • Edit connection list
Add/remove/edit DX Cluster information.
DXC list.png

To set a default DX cluster connection, select the connection from the list and click the Default button.
When editing or adding a new connection, give the connection a meaningful name and enter the address, either an IP address or a domain name plus the access port for the telnet connection.

DXC def.png

The DX Cluster connection list can also be bulk edited by loading the file dxclist.txt in a text editor like Notepad++.
The dxclist.txt file is stored in C:\Program Files (x86)\DXLog\Database and should be overwritten with the latest file available.
DXLog will automatically use this latest file upon running after the file has been updated.
The dxclist.txt file is formatted as follows:
Display Name=internet_address;port_no;Login_Required_(Yes/No);;
W9PA - No Skimmer=dxc.w9pa.net;23;YES;;
W9PA - FT8 Only=dxc.w9pa.net;7374;YES;;
A leading Asterisk "*" before the display name marks the default connection.
  • Reset connection list
Resets the connection list content to its default content. Deletes user additions and changes.
  • Reconnect default DXC at start
Auto connect to DX Cluster on loading or creating a new log.
  • Show talk messages from DXC in GAB window
Cluster talk messages will be shown in the GAB window.
  • Default comment
A default comment when submitting spots to the cluster with e.g. Alt-F3
This menu option is only available with an active log.
  • Send spots to SmartSDR
Sends spots via UDP broadcast for display in SmartSDR waterfall/bandmap.
  • Get exchange from comments
Gets the contest exchange from the comments on the spot or the callsign if spotted as callsign/exchange. This is useful for contests such as US state QSO parties where the spots often include the stations's county.
  • Add first exchange field to spot
Adds the exchange when submitting spots to the cluster. This only works for contests with a simple exchange, such as RST and country.


Hamcap options.png


HamCAP and VOACAP must be installed for these options to work.

HamCAP can be downloaded from http://www.dxatlas.com/Download.asp
The most recent SSN database for HamCAP can be downloaded here http://dxatlas.com/HamCap/Files/Ssn.zip
VOACAP can be downloaded from http://www.greg-hand.com and install

HamCAP is a HF propagation prediction tool and is useful for contest strategy and watching for
possible openings for multipliers. VOCAP works in the background supplying HamCAP with the data it requires.

HamCAP options are:-

  • In background - prevents HamCAP from grabbing focus, also when on top.
  • Always on top - makes sure HamCAP is always visible, also in front of DXLog.
  • Tab - controls which HamCAP tab is displayed when invoked from DXLog.

To enable automatic HamCAP prediction by pressing [Space] check Options|Networking|Show QSY notification in QSY Wizard.

With this option checked, pressing [Space] with a call sign in the entry field will trigger a propagation forecast.

Data files

This menu is used to update the SCP and Country files from the internet and set Extra
info and exchange guessing data base options.

Options data files menu.png

It is recommended to update the Country Files and SCP database before every contest

Country files

Opens the panel below:

Dxl country files.png

Allows you to choose which of the country files you will use for calculation of DXCC, CQ zone,
ITU zone etc. in the currently active contest.
CTY_WT_MOD.DAT will typically provide you with the most accurate information.
Click on Download to update selected country file from the internet and click OK.
After clicking OK, DXLog will ask you to reload the currently active log in order to
refresh all calculations. This can easily be done using the text command RELOADNOW.

Super check partials | Update

Downloads the latest version of the super check partials MASTER.SCP database.
On successful download and update you will be asked to restart DXLog, which
is easily done with the text command RELOADNOW.


Update database

Updates your local prefill database with information from the currently opened log.
Missing information will be added and prefill data that was modified will be changed.
Please note that all comments in the original data base file (lines starting with # or !) will be lost in this process.
All three types of databases, TXT, CSV, and DTB can be updated.

Extra info plugins | HamQTH

Enable or Disable, If enabled, a valid Username and Password must be set in the configuration panel.

HAMqth conf.png

Prefill database settings

Prefill database settings2.png

One or more prefill database(s) may be configured using this panel.
All information entered here will override the default database settings in the contest configuration.
However, when a new log file is created, the default settings from the contest configuration file will be used.
To configure the use of a database file, click Browse and select the database file.
Select the database file type using the pull down menu.
Standard DXLog prefill database files are type TXT. N1MM Logger+ database files are type CSV, and
WinTest database files are type DTB. Be careful to chose the correct file type.
TXT and CSV files typically have a .TXT filename ending. DTB files typically have a .DTB filename ending.
DXLog supports up to four contest exchange elements. Their name, from left to right, are RCVD, RECINFO, RECINFO2, and RECINFO3.
You map an information element in a prefill data base file to an exchange element by specifying its number.
The first information element following the callsign is number 1, the next is number 2, and so on.

The line format in a DXLog prefill data base file is: callsign=information1;information2;information3;information4
The line format in a N1MM Logger+ prefill data base file is: callsign,information1,information2,information3,information4
The format for a standard Win-Test prefill data base file is binary and not possible to easily edit or view.

To not use data for a selected exchange element from a database file, set its number to -1.
This can be relevant in the case of having several data base files, each contributing to individual exchange elements.
For example, one data base file for grid locator and another for operator name or state.
In the example above the first exchange element (name) is collected from information element
number 1 in the CWOps data basefile, whereas the second exchange element (state) is collected
from information element number 2 in the NAQP database.
DTB files only have one information element per call sign and the column numbers should be left at zero.
The Fill format text box allows you to optionally specify special formatting of the looked up prefill information,
using C# string formatting syntax. For example, to append a slash to the prefill, the fill format would be {0}/.
Note that the argument {0} is of the type string which means that numerical operations, such as zero padding, will not work.
You can have multiple, overlapping databases. For instance you may have two data bases with grid locator information.
DXLog will start looking for the call in database #1 and then continue down the list until a match is found.
This means that as a rule, the most up-to-date database should be placed highest in the list.
In the Check Partials window the context menu option "Show data from prefill database" will show you the content of all
databases used.
Exchange elements not used in the current contest (most only have one) are ignored and can be safely left as zero.

Statistics files

Allows the creation and saving of statistics.

Statistics menu.png

DXCC: Statistics related to DXCC.

Create multiplier statistics - Create DXCC multiplier statistics during the contest.
Save multiplier statistics in file - Saves the DXCC multiplier statistics in a file. The file format is SQLite (.sdb).
Import expected mult list from log file - Import expected mults from a previous contest log (*.dxn) file.
Clear expected mult list - Clear the expected DXCC multiplier list.


Log display options. Controls the appearance and functionality of the log fields.

NB. This sub menu can also invoked by right-clicking the DXLog desktop or log entry window (when run in "floating mode).

Options log menu 3.png

  • Fonts - Set the size of the log text.
  • Headers - Controls the display of log column headers.
  • Hide QSO numbers - Hides the QSO numbers in the log lines.
  • Always show mode in QSO line - Controls the display of mode in the log lines. Useful for multimode contests.
  • Show date in QSO lines - Show date in QSO lines. Can only be modified for a logged QSO.
  • Show frequency in QSO lines - Show the frequency in the log line in addition to the band. Updates in real time.
  • Show operator name in QSO lines - Show the logged on operator name in the QSO lines.
  • Colors - Edit log background and text colors.
  • SO2R/V view type - Sets the way the two entry lines in SO2R and SO2V are displayed.
Classic: show entry lines one above the other.
Side by side: show entry lines with one on the left and one on the right.
  • Stay in field when moving up and down log - When editing log this option keeps the cursor in the same log field when moving up through the QSO's.
  • Use focus background color in SO2R(V) - Use a different background color for entry line of the currently focused radio.
  • Show previous and current messages - Show CW message as it is being sent below the entry line with the previous message above the log line.
  • Show RX color status - Change the entry line background when radio's audio is active. NB. Overrides focus color.
  • Show border on TX - Display a colored border around the entry line of the transmitting radio.
  • Show RX wait border - Display a border around the entry line of the radio being held in wait status.
  • Show cursor in entry line without focus - Shows a ghost cursor in the entry line without focus. Very useful for SO2R.


There are two different ways that DXLog handles the opening of information windows.

  • Included in the main window: All windows are opened inside the main window.
  • Floating: Enable to use multiple monitors. All windows will be opened outside of the main window and can be moved as needed.
Please note that in this mode, the color of the title bar of each window is not settable.


Enable or Disable DXLog toolbar


Reset window positions

This option brings all windows back to the upper left corner of the screen, useful if a window has been lost off the screen when changing resolution or in a multi screen environment.