Difference between revisions of "Menu Windows"

From DXLog.net
Jump to navigation Jump to search
(Check callsign)
(Band notes)
 
(156 intermediate revisions by the same user not shown)
Line 9: Line 9:
 
Shortcut: <code>[Alt][L]</code>
 
Shortcut: <code>[Alt][L]</code>
  
Note: this selection is only be available if enabled by the current contest.
+
This selection is only available when relevant for the contest.  
  
  
Line 55: Line 55:
  
  
[[image:dxcc.png]]
+
[[image:spotteddxcc.png]]
  
  
 
If one DXCC country has been worked on a band (possibly a mode), this band will be displayed <br>
 
If one DXCC country has been worked on a band (possibly a mode), this band will be displayed <br>
in blue, otherwise it remains in white. This window is resizeable.
+
in blue (default), otherwise it remains in white (white). This window is resizeable.
  
Continents are selected from the radio buttons at the top of the screen.<br>
+
Continents are selected from the radio buttons at the top of the screen. The window's content<br>
All the data included in this window can be copied as a text file, and pasted in <br>
+
can be copied as text or a png image to the Windows clipboard and pasted into any<br>
text or directly in an OpenOffice spreadsheet, for a later analysis from he right mouse click context menu.  
+
Windows application.
 +
 
 +
Display of spotted (default red) and expected (default yellow) DXCC is only be available<br>
 +
if enabled with <code>Options->Statistics files</code>.
  
DXCC expected and spotted information is also available on this window. <br>
 
The colors used for this information are selectable on the right click context menu Colors.
 
Note: this selection is only be available if enabled by the current contest.
 
  
 
[[image:dxcc_rc.png]]
 
[[image:dxcc_rc.png]]
Line 99: Line 99:
  
  
When a callsign or country prefix is entered in main logging window this window will indicate whether this multiplier has <br>
+
When a callsign or country prefix is entered this window will indicate whether this multiplier has <br>
been worked or not on the current (highlighted by a blue line) or other bands (and in other modes if the contest rules permit). <br>
+
been worked or not on the current (highlighted by a blue line) or other bands (and in other modes if the contest rules permit).
 +
 
 
If the callsign entered has been worked on other bands, DXlog displays those QSOs. <br>
 
If the callsign entered has been worked on other bands, DXlog displays those QSOs. <br>
 
Otherwise, the callsign of the first station worked in that multiplier on that band is displayed, if any.  
 
Otherwise, the callsign of the first station worked in that multiplier on that band is displayed, if any.  
  
Additional information about the multiplier is displayed at the bottom:<br>
+
If the contest has overlapping multipliers, meaning multipliers can be double (or even triple),
The official country prefix and country name.<br>
+
only the first multiplier will be displayed in the window.
The short (Az) and long path (Lp) beam headings (azimuths) to this multiplier (based on the station locator entered in the Contest configuration screen)<br>
+
 
The sunrise (SR) and sunset (SS) time in this country, expressed as UTC (suffixed by a lowercase "z"). <br>
+
Additional information about the multiplier's country is displayed at the bottom:
These times are computed from the geographical coordinates given taken from the CTY* file or your QTH locator, if specified in the setup dialog.
+
 
 +
* Official country prefix and name
 +
* Average short (Az) and long path (Lp) antenna headings
 +
* Sunrise (SR) and sunset (SS) times
 +
 
 +
The update timing of the Check multipliers window is controlled by <code>Tools|Data Entry|Exchange Guessing</code>.
  
The display of the additional information is controlled by Tools-Data Entry-Exchange Guessing
 
 
* Pressing the space bar - information will be displayed when you press the spacebar.
 
* Pressing the space bar - information will be displayed when you press the spacebar.
 
* Automatically - Information will be displayed while you are typing the call-sign.
 
* Automatically - Information will be displayed while you are typing the call-sign.
 
* After timeout - information will be displayed automatically after few seconds of filling in the call-sign field.
 
* After timeout - information will be displayed automatically after few seconds of filling in the call-sign field.
 +
 +
You can double-click on a line to jump to the corresponding QSO in your log.
  
 
==Check partials==
 
==Check partials==
Line 122: Line 129:
 
[[image:check_part.png]]
 
[[image:check_part.png]]
  
 +
With three or more characters entered, the Check partials window will show all callsigns<br>
 +
in the master callsign database that includes the entered string.
  
Check partial callsign search window, When at least 3 characters are entered in the log call entry <br>
+
DXLog's master callsign data base contains the callsigns from all active prefill databases<br>
field, DXlog Check Partials looks in the master database for the callsigns including the 3-character string.
+
together with those from the [http://www.supercheckpartial.com public check partials database].  
  
DXLog's master data base for callsigns is formed by adding the callsigns from all active prefill data bases<br>
+
With the default color settings, white callsigns are not in log, green callsigns are worked on another <br>
to the public Check Partials data base.
+
band, and red callsigns are dupes. A bold callsign is an exact match.
  
In the above example M0C was entered into the log call entry field and the Check Partial database search <br>
+
A callsign can be grabbed to the entry field by double clicking on it.  
found all the callsigns with the 3 characters in that order and displayed those.
 
 
 
A callsign can be moved to the log call entry field by double clicking on the callsign in the Check Partial window. <br>
 
White callsigns are those not yet in the log, green callsigns are stations worked on another band, <br>
 
but not the current band and red callsigns are dupes.
 
  
 +
The callsign in the upper left corner can be grabbed by pressing <code>[Alt][Y]</code>.
  
 
[[image:check_part_rc1.png]]
 
[[image:check_part_rc1.png]]
  
  
Right mouse click on the window shows the context menu.<br>
+
Right-clicking the window will display the context menu. Search can be started after only two characters<br>
Search can be activated after 2 characters entered into the log call entry field by ticking the option in the context menu.<br>
+
entered (not recommended), search can be limited to only the log, and prefill data can be displayed.
Search can be limited to the current log data only by ticking the "in log only" option in the context menu.<br>
 
Show data from prefil database option will pull the relevant data from the prefil database and display next <br>
 
to the callsign in (), this is useful for VHF / UHF contests and locator squares.
 
  
If more than one data base is used, the content of database's entry for the callsign is displayed, separated by slash "/".
+
If more than one database is used, the values from each database are separated by slash "/".
  
  
Line 164: Line 166:
  
 
[[image:Reverse_look-up2.png]]
 
[[image:Reverse_look-up2.png]]
 
  
 
==Check partials 2==
 
==Check partials 2==
Line 180: Line 181:
  
  
N+1 window, when at least 3 characters are entered in the log call entry field, DXlog <br>
+
With at least three 3 characters are entered in the callsign entry field, the Check N+1 window will list all<br>
looks in the master database for callsigns differing from the partial callsign by one character.<br>
+
callsigns from the [http://www.supercheckpartial.com super check partial database] having a [https://en.wikipedia.org/wiki/Damerau%E2%80%93Levenshtein_distance Damerau-Levenshtein distance] of 1 or less.  
N+1 also detects a 2-character swap (dyslexia), as well as one missing character.<br>
 
A callsign can be moved to the log call entry field by double clicking on the callsign in the Check Partial window. <br>
 
White callsigns are those not yet in the log, green callsigns are stations worked on another <br>
 
band, but not the current band, and red callsigns are dupes.
 
  
 +
In plain English this means all callsigns in the valid callsign database that can be created by either <br>
 +
removing a character, adding a character, or swapping two characters in the entered callsign.
 +
 +
With the default color settings, white callsigns are not in log, green callsigns are worked on another <br>
 +
band, and red callsigns are dupes. A bold callsign is an exact match.
 +
 +
A callsign can be grabbed to the entry field by double clicking on it.
  
 
[[image:n+1_rc.png]]
 
[[image:n+1_rc.png]]
  
  
Right mouse click on the window shows the context menu.<br>
+
Right mouse click on the window shows the context menu. Optionally, search can be limited to only the current <br>
Search can be limited to the current log data only by ticking the "in log only" option in the context menu.
+
log and content from an active prefill database can be displayed.
  
 
==Check N+1 2==
 
==Check N+1 2==
Line 199: Line 203:
 
open the Check N+1 window will show the information for Radio 1 if  SO2R and VFO A if SO2V and<br>
 
open the Check N+1 window will show the information for Radio 1 if  SO2R and VFO A if SO2V and<br>
 
the Check N+1 2 window will show the information for Radio 2 if SO2R and VFO B if SO2V.
 
the Check N+1 2 window will show the information for Radio 2 if SO2R and VFO B if SO2V.
 +
 +
==Search and Pounce==
 +
 +
The Search and Pounce window serves as a scratchpad, remembering stations with their frequency.<br>
 +
For instance you may find a rare multiplier but you may want to try again a bit later when <br>
 +
the pile-up is less intense.
 +
 +
Note that the Search and Pounce window is local to the station and not networked.<br>
 +
Just as with the Partner window, Callsigns with frequency are added to the window with <code>[Alt][Enter]</code>
 +
 +
Except for also remembering the frequency and that double-clicking an entry does not delete it,<br>
 +
the window behaves like the [[Menu_Windows#Partner|Partner window]].
 +
 +
If both the Partner window and the Search and Pounce windows are open, the operating mode will determine which one is used.<br>
 +
The Partner window will be used in RUN, and the Search and Pounce window will be used in... S&P.
 +
 +
[[image:Searchandpounce.png]]
  
 
==Summary==
 
==Summary==
Line 211: Line 232:
 
to the contest type for each band in the blue section, with the dark blue strip showing the current band being operated.
 
to the contest type for each band in the blue section, with the dark blue strip showing the current band being operated.
  
'''NB.''' The QSO and multiplier counts does not include bonuses etc. whereas the total score does.
+
'''Important:''' The Points and Multiplier counts may not include bonuses whereas the total score does.
 +
 
 +
'''Important:''' The QSO count includes X-QSO but excludes dupes.  
  
 
Grey section at the bottom shows totals for the contest and final raw score.
 
Grey section at the bottom shows totals for the contest and final raw score.
Line 226: Line 249:
  
  
[[image:rate.png]]
+
[[image:rate2.png]]
 +
 
 +
 
 +
The panel displays live QSO rate data for the current contest log.
 +
 
 +
The top section shows QSO's in last hour, last 10 QSO rate, last 100 QSO rate,<br>
 +
rate for the current hour so far and, if enabled in the context menu, a projected score.<br>
 +
 
 +
There is also a menu option for additionally showing the rate over the past 10 minutes.
 +
 
 +
The second section shows time on and time off in hours and minutes. The minimum off time<br>
 +
defined in the rules for the current contest is used in this calculation.<br>
 +
 
 +
'''Important:''' Since DXLog does not know the starting time or duration of a contest,<br>
 +
the on/off time calculation starts and ends with the first and last QSO. This means that <br>
 +
if you do not join the contest from start, or end early, you will need to add this off time<br>
 +
time to the displayed off time manually.
  
 +
The third section shows Run and S&P statistics. Both in total QSO count and the count since<br>
 +
the last full hour.
  
Rate data information window displays live qso rate data relating to the current contest.<br>
+
For a contest entry with band change limitations, the next section displays these.  
Top section shows QSO's in last hour, last 10 rate, last 100 rate, rate since last time hour passed and if selected in the context menu, a projected score.<br>
 
Second section shows time on and time off in hours and minutes.<br>
 
Third section shows differential between Run and S&P mode.
 
  
Fourth section shows time since last multiplier, multiplier and QSO points worth.<br>
+
For a contest with QRB-based scoring, the next section displays distance statistics.  
'''NB.''' The calculation of multiplier points does not include factors like bonuses.
 
  
Fifth section shows operating mode and, if in CW, the CW speed
+
The second to lowest section shows time since last multiplier, multiplier and QSO points worth.
 +
 
 +
'''Important:''' The calculation of multiplier points does not include factors like bonuses.
 +
 
 +
The last section shows operating mode and audio focus status.
  
  
Line 260: Line 301:
  
  
[[image:operating_info.png]]
+
[[image:operating_info2.png]]
  
  
Line 266: Line 307:
 
The CW repeat timer interval and the CW speed set in DXlog.
 
The CW repeat timer interval and the CW speed set in DXlog.
  
* '''Interlock blocking'''
+
If you software interlock is active, the interlock status will be shown in the Operating info window.<br>
 +
Interlock blocking can be forbidden by clicking on the Interlock status line as shown below. <br>
 +
Interlocks can also be controlled by the $PILOCK (forbid) and $AILOCK (allow) macros.
  
If  you have interlocks active, the interlock status will be shown in the Operating info window.<br>
+
The current interlock status/activity is shown in the [[Menu_Windows#Radio_status|Radio status]] window.
Interlock blocking can be forbidden by clicking on the Interlock status line. <br>
+
 
The status will change to 'Blocking forbidden' as shown below.<br>
+
 
Interlocks can also be controlled by the $PILOCK (forbid) and $AILOCK (allow) macros.
+
[[image:Operating_info_interlock.png]]
 +
 
 +
[[image:Operating_info_interlock_forbidden.png]]
 +
 
 +
 
 +
In SO2R Advanced mode the window will also show the currently active scenario.<br>
 +
Double-clicking the scenario name will bring up the scenario editor.
 +
 
 +
 
 +
[[image:Operating_info_so2r.png]]
 +
 
 +
 
 +
The Operating Info window also shows the current status of Intelligent Quick QSL, ESM, and Auto-CW.
 +
 
 +
 
 +
[[image:Opinfostatus.png]]
  
The current interlock activity is shown in the ''Radio status'' window.
 
  
 +
If RUN/S&P switching is disabled, this is indicated with parentheses.
  
[[image:Operating_info_blocking_forbidden.png]]
 
  
 +
[[image:Opinfolocked.png]]
  
==Statistics==
+
==Contest statistics==
  
 
Shortcut: <code>[Ctrl][F9]</code>
 
Shortcut: <code>[Ctrl][F9]</code>
Line 296: Line 354:
 
Without any logged QSO, the graphs may not show any meaningful information.
 
Without any logged QSO, the graphs may not show any meaningful information.
  
<b>Log Tab Options</b><br>
+
===Log Tab Options===
 +
 
 
[[image:statsdispdata.png]]
 
[[image:statsdispdata.png]]
  
Line 319: Line 378:
 
** Overall: Displays a cumulative (overall total) comparison
 
** Overall: Displays a cumulative (overall total) comparison
  
<b>Target Tab Options</b><br>
+
===Target Tab Options===
 +
 
 
[[image:statstargetmenu.png]]
 
[[image:statstargetmenu.png]]
  
Line 332: Line 392:
 
* Load a target file: Loads a previously created *.obf file for use as a target file.
 
* Load a target file: Loads a previously created *.obf file for use as a target file.
  
==Gab==
+
==Operator statistics==
 +
 
 +
A resizeable window showing the operator QSO statistics.
 +
 
 +
QSO without a logged operator are counted as the station's callsign.
 +
 
 +
[[image:Operatorstatistics.png]]
 +
 
 +
==Azimuth statistics==
 +
 
 +
A resizeable panel showing the direction statistics of all QSO in the log as a spider web diagram.
 +
 
 +
The menu item is only visible for logs with distance-based scoring.
  
Shortcut: <code>[Alt][I]</code>
 
  
 +
[[image:Azimuthstatistics.png]]
  
[[image:gab.png]]
+
==Gab==
  
 +
Shortcut: <code>[Alt][I]</code>
  
Gab window displays all the chat between networked stations.<br>
 
In the context menu, the option "Save history to file" allows all the gab chat to be recorded in the .gab file of the current contest.<br>
 
A double-click in a station name in this window will open the chat dialog, with this station name as default destination.<br>
 
To send a message use Shortcut: <b><code>ALT+G</code></b> and the chat entry window will appear.
 
  
 +
[[image:gabcontext.png]]
  
[[image:chat.png]]
 
  
 +
The Gab window displays the chat between networked stations.<br>
  
Type a message and select either the individual station you wish to message or all to message all networked computers then click OK.<br>
+
In the context menu,
Gab window context menu - right mouse click on gab window.
 
  
 +
* ''Save history to file'' will save the gab chat history in a .gab file for the current contest.
 +
* ''Clear history'' will do exactly what it says.
 +
* ''Flash on new message'' will briefly change the background color of the Gab window with all incoming messages.
 +
: Regardless of this setting, messages containing "!" will always trigger this visual alert.
 +
* ''Sticky flash'' will make the alert background color stay until confirmed. Confirmation is done either
 +
: by sending a response or clicking anywhere inside the Gab window.
  
[[image:gab_rc.png]]
+
<b><code>ALT+G</code></b> opens a chat dialog for sending messages. It offers the option of either broadcasting<br>
 +
or directing the message to an individual station.
  
 +
Double-clicking on a station name in the [[Menu_Windows#Status|Status window]] will open the same chat dialog,<br>
 +
with the selected station's name as the selected destination. Double clicking your own station name will select<br>
 +
all stations as destination.
  
==Status==
+
==Network status==
  
 
Shortcut: <code>[Alt][J]</code>
 
Shortcut: <code>[Alt][J]</code>
Line 398: Line 477:
 
* Double click on a list entry to QSY to its frequency.  
 
* Double click on a list entry to QSY to its frequency.  
 
* Hold down <code>[Ctrl]</code> and double click on a list entry to delete it.
 
* Hold down <code>[Ctrl]</code> and double click on a list entry to delete it.
* Hold down <code>[Alt]</code> and double click on a list entry to QSY to its frequency  
+
* Hold down <code>[Alt]</code> and double click on a list entry to QSY to its frequency on the second VFO
: on the second VFO or the other radio depending on the setting of
+
: or the other radio in SO2R if <code>Operating|Bandmap|QSY opposite radio instead of 2nd VFO</code> is checked.
: <code>Operating|Bandmap|QSY opposite radio instead of 2nd VFO</code>.
 
  
Right click on the window for a context menu (as shown below) to add, edit, and delete skeds.
+
Right click on the window for a context menu (as shown below) to add, edit, and delete skeds.<br>
 
There are also sorting options and for hiding past skeds.  
 
There are also sorting options and for hiding past skeds.  
  
Line 409: Line 487:
  
  
For more information on how to populate and use the Skeds window, see the<br>
+
For more information on how to populate and use the Skeds window, see the [[Menu_Commands#Pass_a_station|Pass a station]] section.
[[Menu_Commands#Pass_a_station|Pass a station]] section.
 
  
 
==QSY wizard==
 
==QSY wizard==
Line 470: Line 547:
 
==Extra Information==
 
==Extra Information==
  
<br>[[image:extra_info_window.png]]
+
<br>[[image:extrainfowindow.png]]
  
  
 
The Extra Information window displays information contained in a text file based on the call entered in the <br>
 
The Extra Information window displays information contained in a text file based on the call entered in the <br>
log callsign entry field. Files should be named with the .xdt file extension.
+
log callsign entry field. Files should have the .xdt file extension.
  
The format of the Extra information file is:
+
The format of the Extra information file is very simple:
:: #TITLE Name of info
+
 
:: K6MR Ken 1270 CA   (typical data line)
+
<tt>
 +
: #TITLE Name of info
 +
: K6MR Ken #1270 Anderson CA
 +
: K6NA Glen #548 Valley Center CA
 +
: K6NR Dana #2380 Irvine CA
 +
: K6NV Bob #675 Truckee CA
 +
: K6PB Pete #2469 Irvine CA
 +
</tt>
 +
 
 +
For proper display of non-ASCII characters, make sure the file is UTF-8 encoded.
 +
 
 +
The text following #TITLE keyword will be shown on the window's header. <br>
 +
If the #TITLE line is omitted, the complete path and filename will be shown.
  
The text on the #TITLE line will be shown on the header line. <br>
 
If the #TITLE line is omitted, the complete path and filename will be shown. <br>
 
 
Data lines (one per call) begin with the call sign and a single space. <br>
 
Data lines (one per call) begin with the call sign and a single space. <br>
 
Any information present after the first space will be shown exactly as formatted in the file.<br>
 
Any information present after the first space will be shown exactly as formatted in the file.<br>
Multiple files may be opened at the same time to show data from different sources.
+
Multiple files may be used to show data from different sources.
  
 
* '''To add a file''' - Right mouse click in the extra information window and select "Extra data files".  
 
* '''To add a file''' - Right mouse click in the extra information window and select "Extra data files".  
Line 492: Line 579:
  
 
If a file is updated while open in the window, right click and select "Reload files" to use the new data.
 
If a file is updated while open in the window, right click and select "Reload files" to use the new data.
 +
 +
The window is also used to display the result of online look-ups from hamQTH and QRZ, configured via<br>
 +
the [[Menu_Options#Data_files|<code>Options|Data files|Extra info plugins</code>]] menu.
 +
 +
A selection of XDT files for download can be found on the [http://dxlog.net/sw/#files%2Fdownload%2Fextrainfo DXLog.net web server].
  
 
==Partner==
 
==Partner==
Line 516: Line 608:
 
A field in the partner window can be overwritten with a new entry by using <code>[Ctrl][1]</code> to <code>[Ctrl][9]</code>.
 
A field in the partner window can be overwritten with a new entry by using <code>[Ctrl][1]</code> to <code>[Ctrl][9]</code>.
  
'''Partner window use in RTTY'''<br>
+
'''Partner window use in RTTY'''
 +
 
 
The Partner window is also useful when used in a RTTY environment.<br>
 
The Partner window is also useful when used in a RTTY environment.<br>
 
In addition to using <code>[Alt][1-9]</code> and <code>[Ctrl][1-9]</code>, calls may be entered onto<br>
 
In addition to using <code>[Alt][1-9]</code> and <code>[Ctrl][1-9]</code>, calls may be entered onto<br>
Line 531: Line 624:
 
<tt>$13 $CORRECT TU $GRABPARTNER NOW $LOGGEDCALL $F2 $CR</tt>
 
<tt>$13 $CORRECT TU $GRABPARTNER NOW $LOGGEDCALL $F2 $CR</tt>
  
'''Multi Partners and real time updates'''<br>
+
'''Multi Partners and real time updates'''
 +
 
 
[[image:partnercont.png]]
 
[[image:partnercont.png]]
  
  
The partner window can be made to update in real time, right click on the window and select <code>Real time|Enabled</code>,<br>
+
The partner window can also be set to display the typing done by support stations in real time.<br>
this will give an additional line at the top of the window that will auto fill as the partner station enters the callsign<br>
+
Right click on the window and select <code>Real time|Enabled</code>. This option will give you up<br>
into the partner log entry field.<br>
+
to three additional lines at the top of the window that will reflect the typing of your partner stationn.
  
The options for real time are for the runner or the partner, as the runner you can have a live entry field that is <br>
+
Normally the only the run stations displays the typing of the support stations but by checking the<br>
1, 2 or 3 slots long. As the partner you can select to post into either of the 3 slots, this gives the option of up<br>
+
option ''Always send data'' will make the station broadcast its typing to other partners regardless of role.
to 3 additional partners each with a specific line to live update as the callsign is typed into the partners local log.
+
 
 +
The options for real time are for the runner or the support, as runner you can have a live entry field that is<br>  
 +
1, 2 or 3 slots long. As support you can select to post into either of the 3 slots, this gives the option of up<br>
 +
to 3 support stations each with a specific line to update live as the callsign is typed on the support station.<br>
 +
When ''Always send data'' is checked, both the runner and support options are valid.  
 +
 
 +
'''Partner window use for M/2'''
  
'''Partner window use for M/2'''<br>
 
 
For M/2 stations the station type - partner is grayed out, each station can have up to 3 partners, the partner window<br>
 
For M/2 stations the station type - partner is grayed out, each station can have up to 3 partners, the partner window<br>
 
should be set to real time and the partner stations on the same band and mode as the run station.  
 
should be set to real time and the partner stations on the same band and mode as the run station.  
  
'''No Band / Mode Filter option'''<br>
+
'''No Band/Mode Filter option'''
This option if ticked will display all callsigns entered from support stations irrespective of the DXLog band or mode,<br>
+
 
this should be used with caution.
+
With this option checked all callsigns entered from support stations irrespective of band or mode will be displayed.  
  
 
==Radio status==
 
==Radio status==
Line 575: Line 674:
 
are set up in the configuration panel for the used device.  
 
are set up in the configuration panel for the used device.  
  
* MK2R/MK2R+/u2R configuration: <code>Options|MK2R/MK2R+/u2R configuration</code>
+
* microHAM configuration: <code>Options|microHAM configuration</code>
 
* OTRSP device configuration: <code>Options|OTRSP device configuration</code>
 
* OTRSP device configuration: <code>Options|OTRSP device configuration</code>
 
* Printer port: <code>Options|Configure interfaces</code> Printer port Setup
 
* Printer port: <code>Options|Configure interfaces</code> Printer port Setup
  
For more detailed information on how to configure each interface, see [[Menu_Options#MK2R.2FMK2R.2B.2Fu2R_configuration|MK2R/MK2R+/u2R configuration]],<br>  
+
For more detailed information on how to configure each interface, see [[Menu_Options#microHAM_device_configuration|microHAM configuration]],<br>  
 
[[Menu_Options#OTRSP_device_configuration|OTRSP device configuration]], and [[Menu_Options#Printer_port_configuration|Printer port configuration]].
 
[[Menu_Options#OTRSP_device_configuration|OTRSP device configuration]], and [[Menu_Options#Printer_port_configuration|Printer port configuration]].
  
Line 586: Line 685:
 
Different antennas for receive and transmit when using an OTRSP device or printer port is not supported.<br>
 
Different antennas for receive and transmit when using an OTRSP device or printer port is not supported.<br>
  
NB. Using a different antenna for receive and transmit only works when DXLog either exclusively controls, or is<br>  
+
'''Important:''' Using a different antenna for receive and transmit only works when DXLog either exclusively controls, or is<br>  
aware of, the transmit/receive status, e.g. through a foot switch.<br>
+
aware of, the transmit/receive status, e.g. through a footswitch.<br>
 
Tip: For microHAM devices DXLog is aware of the keyer's PTT status if ''Enable TX lock/unlock'' is checked.  
 
Tip: For microHAM devices DXLog is aware of the keyer's PTT status if ''Enable TX lock/unlock'' is checked.  
 +
 +
'''Important:''' Cross band operation is not supported. The band of VFO A always determines the antenna selection.
  
 
It is possible to have several antennas for each band (as well as antennas covering multiple bands,<br>
 
It is possible to have several antennas for each band (as well as antennas covering multiple bands,<br>
Line 600: Line 701:
 
and <code>[Alt][Shift][F11]</code> (transmit antenna) or by clicking on the name of the desired antenna in the window.
 
and <code>[Alt][Shift][F11]</code> (transmit antenna) or by clicking on the name of the desired antenna in the window.
  
==Antenna rotor R1/R2==
+
==Antenna controller R1/R2==
 +
 
 +
Only visible when using a networked antenna server.
 +
 
 +
==Antenna rotator R1/R2==
  
 
<br>[[image:rotatorr1.png]]
 
<br>[[image:rotatorr1.png]]
Line 616: Line 721:
  
 
Right click on the window to access the context menu, the menu has turn antenna to - with a list of basic directions.<br>
 
Right click on the window to access the context menu, the menu has turn antenna to - with a list of basic directions.<br>
 
  
 
==World Map==
 
==World Map==
Line 623: Line 727:
  
  
World map showing Daylight, Greyling and Night.<br>
+
A color world map showing the current distribution of daylight and the location of the greyline.
World map context menu is available by right mouse clicking on the map window.<br>
+
 
Grey line display options can be adjusted from this menu.
+
Unlike most other DXLog windows, the World map can be '''resized'''.
 +
 
 +
The properties of the map can be configured by right-clicking on it.
 +
 
 +
The map can show the location of stations and skimmers spotting the own station's call.<br>
 +
The spots fade when they reach the age of the spot lifetime set in the bandmap properties panel.
 +
 
 +
By default, spots on the band of radio 1 (or of any band, when all bands are displayed)<br>
 +
are red and spots on the band of radio 2 are yellow.
 +
 
 +
 
 +
[[image:Map_rc.png|330px]]
 +
 
 +
[[image:Worldmap2radios.jpg|330px]]
 +
 
 +
 
 +
Either only spots on the station's active band(s) or on all bands can be shown.<br>
 +
The size of the map can also be changed using the zoom option in the right click menu.
 +
 
 +
'''VERY IMPORTANT''' When using this function, it is essential that the DX cluster node connected<br>
 +
to is set up to forward all spots of own callsign. Otherwise the display will not be reliable.
 +
 
 +
: '''DXSpider''' - Make sure the node you connect to is version 1.57 build 434 or later.
 +
:::Send the command '''<tt>SET/SEEME</tt>''' to make all spots of the logged in call pass through unfiltered.
 +
 
 +
: '''CC Cluster''' - Send the command '''<tt>SET/OWN</tt>''' to make all spots of the logged in call pass through unfiltered.
 +
 
 +
: '''AR Cluster''' - If you are using filters, make sure to add an exception for your own call, e.g.,
 +
:::'''<tt>...OR CALL=SM7IUN</tt>''' (If you are SM7IUN, that is)
 +
 
 +
Note that you need to log on to the cluster node with the station's call for the above features to work.
 +
 
 +
[[image:Map_menu.png]]
 +
 
 +
==Band notes==
 +
 
 +
[[image:Bandnotes.png]]
 +
 
 +
A user configurable window that shows information about the current active band.  
 +
 
 +
It can be used to show license band segments, antenna tuner or PA settings, etc.
 +
 
 +
DXLog looks for configuration information in two places.
 +
 
 +
* The first place is the folder of the current log file. DXLog looks for a file with the same name as
 +
: the log file but ending with <tt>_BandNotes.txt</tt>, e.g., <tt>CQWW2023_CW_BandNotes.txt</tt>
 +
 
 +
* The second place is the <tt>%appdata%\DXLog.net</tt> configuration folder.
 +
: DXLog looks for a file called <tt>BandNotes.txt</tt>
 +
 
 +
If none of these files exist, DXLog uses a standard file that is part of the installation.
 +
 
 +
The formatting of the band notes file is as follows:
 +
 
 +
* Blank lines or lines beginning with a hash symbol are ignored.
 +
 
 +
* The structure of a line is '''<tt>Mode;Lower Freq;Upper Freq;Color;Text</tt>'''
 +
 
 +
: The keyword '''<tt>ALL</tt>''' matches any mode.
 +
 
 +
: A line is highlighted if the frequency of the currently focused radio falls within its range and has the right mode.
 +
 
 +
: The color is a number between 1 and 5 and can be changed in the Band Notes window's color settings.
 +
 
 +
: If color is followed by the letter '''<tt>H</tt>''' it is hidden when the frequency is not in range.
 +
 
 +
: If the color is followed by the letter '''<tt>N</tt>''' it is never highlighted.
 +
 
 +
: The color number can be followed by both H and N, e.g., '''<tt>5HN</tt>'''.
 +
 
 +
One obvious application of this panel is PA settings, like shown below.<br>
 +
Since this is not contest-specific information it is best stored as <tt>%appdata%\DXLog.net\BandNotes.txt</tt>
  
  
[[image:map_rc.png]]
+
[[image:bandnotespa.png]]
  
 +
Example file content:
  
Map size can be increased by using the zoom in option in the right click menu.
+
<pre>
 +
# 160m
 +
ALL;1800;1850;3H;Load 44 Tune 67
 +
ALL;1850;1900;3H;Load 47 Tune 65
 +
ALL;1900;1950;3H;Load 52 Tune 62
 +
ALL;1950;2000;3H;Load 55 Tune 59
 +
CW;1800;1900;3H;Power 33
 +
CW;1900;2000;3H;Power 35
 +
SSB;1800;1900;3H;Power 27
 +
SSB;1900;2000;3H;Power 29
 +
</pre>
  
 
==Radio 1==
 
==Radio 1==
  
<br>[[image:Radio1.png]]
+
<br>[[image:Radio1.png]][[image:Radio1list.png]]
  
  
 
Radio information displaying VFO A and VFO B frequency information.<br>
 
Radio information displaying VFO A and VFO B frequency information.<br>
 
Click on the VFOA and VFOB boxes to switch to select the respective VFO.<br>
 
Click on the VFOA and VFOB boxes to switch to select the respective VFO.<br>
Note: If you have automatic RUN/S&P selection enabled, a switch of VFO will change operating mode to S&P.<br>
 
For convenience, it is recommended to combine this option with the option "F1 always return to Run".
 
  
The Band map tab shows radio band in focus and any DX Cluster received or locally<br>
+
Note: If you have automatic RUN/S&P selection enabled, a switch of VFO will change operating mode to S&P.<br>
entered callsigns plus other optional information.<br>
+
For convenience, it is recommended to combine this option with the option ''F1 always return to Run''.
Callsigns preceeded by bullets are skimmer spots. Callsigns preceeded by a plus sign are manual spots.<br>
+
 
Callsigns preceeded by a star contain split ("QSX") information.<br>
+
The Band map tab shows the currently selected radio band and any DX Cluster received or locally<br>
 +
entered callsigns plus other optional information.
  
The List tab shows a list of call signs which can be sorted in various ways.<br>
+
Callsigns preceded by bullets are skimmer spots. Callsigns preceded by a plus sign are manual spots.<br>
 +
Callsigns preceded by a star contain split ("QSX") information.
  
Colours are: RED = Double Multiplier, GREEN = Multiplier, Black = Unworked, GREY Italics= Worked<br>
+
The List tab shows a list of call signs which can be sorted in several ways.
Information below the horizontal divider is available multiplier numbers, available QSO count, and points available.<br>
+
 
 +
In the list mode an colored bar will show the position of the currently selected<br>
 +
VFO and an underline indicates the position of the unselected VFO.
 +
 
 +
The default coloring is: RED = Double Multiplier, GREEN = Multiplier, Black = Unworked, GREY Italics= Worked<br>
 +
Information below the horizontal divider is available multiplier numbers, available QSO count, and points available.
  
 
Double clicking on a callsign sets the focused radio VFO to that frequency and mode <br>
 
Double clicking on a callsign sets the focused radio VFO to that frequency and mode <br>
Line 658: Line 849:
 
selecting the enable single click selection from the context menu.
 
selecting the enable single click selection from the context menu.
  
Double clicking while holding down [Alt] will grab the spot to the other VFO. <br>
+
Double clicking while holding down <code>[Alt]</code> will grab the spot to the other VFO. <br>
If the option <b>Operating->Band map->QSY other radio instead of 2nd VFO</b> <br>
+
If the option <code>Operating|Band map|QSY other radio instead of 2nd VFO</code> <br>
 
is checked, the spot is grabbed to other radio.
 
is checked, the spot is grabbed to other radio.
  
Double clicking while holding down [Ctrl] will erase the spot.  
+
Double clicking while holding down <code>[Ctrl]</code> will erase the spot.  
 
    
 
    
<b>Context Menu</b><br>A right click anywhere in the band map will bring up the context menu.<br>
+
===Context menu===
 +
 
 +
A right click anywhere in the band map will bring up the context menu.<br>
 
Band map options are changed by selecting the appropriate menu.
 
Band map options are changed by selecting the appropriate menu.
  
Line 671: Line 864:
  
  
Most menu picks are self explanatory. <br>
+
Most menu selections are self explanatory.
  
<b>Show from higher to lower frequency</b><br>
+
<i>Show from higher to lower frequency</i> will show the higher band segment edge at the top.<br>
The default band map display is to show lower <br>
+
The default band map display is to show lower frequencies at the top, higher frequencies at the bottom. <br>
frequencies at the top, higher frequencies at the bottom. <br>
 
 
As you tune up the band, the band map will move up as the cursor points to a higher frequency. <br>
 
As you tune up the band, the band map will move up as the cursor points to a higher frequency. <br>
 
If you would prefer that the band map show higher frequencies at the top (with resulting <br>
 
If you would prefer that the band map show higher frequencies at the top (with resulting <br>
Line 688: Line 880:
  
  
 +
[[image:Radio1_rc_do3.png]]
 +
 +
 +
Display options for both Band Map and List mode are set by right-clicking the pane and selecting ''Display options''.<br>
 +
Note that when ''Multiplier only in list view & grabbing'' is enabled, <code>[Ctrl][Up]</code> and <code>[Ctrl][Down]</code><br>
 +
will only grab multiplier spots. Using the mouse or <code>[Ctrl][Space]</code>, any spot can still be grabbed.
 +
 +
''Spot quality'' will display spot quality tags reported by AR version 6 cluster nodes.<br>
 +
More information on spot quality display can be found in the [[Additional_Information#Special_support_for_AR_Cluster_6|section about AR 6 clusters]].
 +
 +
''Exchange'' will show prefill database or zone data depending on the type of exchange.
 +
 +
''Spectrum'' enables the display of a real time spectrum overlaid on the bandmap.<br>
 +
It requires a supported radio or external SDR. An example display is shown below.
  
[[image:Radio1_rc_do3.png]]
 
  
 +
[[image:Spectrum_1.png]]
  
  
Display options for both Band Map and List mode are set from the context menu and display options.<br>
+
The option ''Show station information'' will show information from the most recent spot of the currently<br>
Note that when the "Multiplier only in list view & grabbing" is enabled, <code>[Ctrl][Up]</code> and <code>[Ctrl][Down]</code><br>
+
selected/highlighted callsign at the bottom of the bandmap, replacing the available QSO information.
will only grab multiplier spots. Using the mouse or <code>[Ctrl][Space]</code>, any spot can still be grabbed.
 
  
  
Line 703: Line 908:
 
Various properties can be set by a right mouse click in the band map and selecting Properties.
 
Various properties can be set by a right mouse click in the band map and selecting Properties.
  
Bandplan Settings for spots to be displayed are set from the Properties form. <br>
+
'''Important:''' The <i>Wipe QSO</i> setting is prone to false triggers and may clear the entry line also when not wanted,<br>  
 +
such as when using keys such as <code>[Alt][F4]</code> or <code>[Shift][Ctrl][F1]</code>.
  
Click Setup in the bandplan section of the Properties panel to display the current bandplan settings. <br>
+
===Bandplan settings===
The current band will be displayed by default. Be sure to save your changes to a Bandplan memory (Default or Bandplan 1 - Bandplan 9).<br>
 
Note that clicking OK will save any changes to the currently active bandplan.<br>
 
To edit a different bandplan than the one currently active, click its button in the Load button group. <br>
 
  
If a bandplan has no settings, its Load group button will be grayed out. <br>
+
The <i>Bandplan Settings</i> panel is accessed from the <i>Properties</i> form.
 +
 
 +
Important: The sole purpose of the bandplan is for guessing the mode of spots that do not explicitly<br>
 +
show their mode in their comment.
 +
 
 +
Click <i>Setup</i> in the bandplan section of the <i>Properties</i> panel to display the current bandplan settings. <br>
 +
The current band will be displayed by default. Be sure to save changes to a Bandplan memory (Default, or Bandplan 1 through 9).<br>
 +
Note that clicking <i>OK</i> will save any changes to the currently active bandplan.<br>
 +
To edit a different bandplan than the one currently active, click its button in the Load button group.
 +
 
 +
If a bandplan has no settings, its <i>Load group</i> button will be grayed out. <br>
 
To use a new Bandplan memory, save the current settings by clicking its button in the Save as button group. <br>
 
To use a new Bandplan memory, save the current settings by clicking its button in the Save as button group. <br>
Modify as required and save using the same button. <br>
+
Modify as required and save using the same button.
If you wish to activate the currently selected bandplan, check the box in the lower left corner of the form.<br>
+
 
 +
The ''Reset'' button will reset the Default bandplan to its original settings and select it.
 +
 
 +
If you wish to activate the currently selected bandplan, check the box in the lower left<br>
 +
corner of the form before you click <i>OK</i>.
 +
 
 +
'''Important:''' Spots falling outside <b>all</b> of the defined mode segments for a band will be ignored, regardless of their comment.
 +
 
 +
The mode of a spot is determined either by an explicit tag in beginning of the spot's comment ("SSB", "CW", etc.)<br>  
 +
or, when this is missing, by the bandplan segment it falls within. In the case of overlapping mode segments,<br>
 +
the search order is: CW, SSB, RTTY. The first segment found that includes the spot's frequency determines its mode.
  
Spots falling outside any of the defined mode frequency ranges for a band will be ignored.<br>
+
Mode checking is enforced based on contest entry category. In a single mode entry, only spots of the contest entry's<br>
Mode checking is not enforced. A CW spot falling within the SSB segment will not be ignored.
+
mode are displayed. In a mixed mode entry, spots for all the allowed modes are displayed.  
  
The frequency ranges serve two purposes:
+
This means that spots <b>with</b> an explicit mode tag, falling within <b>any</b> of the band's mode segments, and relevant<br>
 +
for the contest entry, will be displayed.
 +
 
 +
It also means that for spots <b>without</b> an explicit mode tag, only spots falling within the band segments relevant<br>
 +
for the contest entry will be shown. Spots without an explicit mode tag are often manual spots or spots received from a<br>
 +
local skimmer. This makes it important to sometimes adjust the bandplan.
 +
 
 +
Example: For a massive CW contest like CQ WW it may be a good idea to extend the CW segments in your bandplan, e.g.<br>
 +
14000-14125 for 20m. For a CW contest like this, skimmer spots (which all have a mode tag) will be displayed regardless of<br>
 +
frequency as long as they are within any of the active mode segments (SSB etc.) for the band.<br>
 +
Human spots (or others lacking a mode tag) will however only be displayed if they fall within the CW segment for the band.<br>
 +
The exception is however for spots CW originating from the Telnet ports of RBN Aggregator and CW Skimmer Server.<br>
 +
They will always be considered CW spots and not be subject to the bandplan rules.
 +
 
 +
The bandplan's frequency ranges thus serve two purposes:
  
 
* Spots not falling inside any of the mode frequency ranges will be ignored
 
* Spots not falling inside any of the mode frequency ranges will be ignored
Line 725: Line 962:
 
For more information about handling spots, see [[Menu_Options#DX Cluster|DX Cluster options]]
 
For more information about handling spots, see [[Menu_Options#DX Cluster|DX Cluster options]]
  
Note: If the spot mode is included in the spot comment, the spot will be displayed using the mode shown in the comment. <br>
 
Otherwise the mode will be determined by the active Bandplan.
 
  
 +
[[image:Radio1_rc_pr_bp2.png]]
  
[[image:Radio1_rc_pr_bp.png]]
+
==Radio 1 spectrum parameters==
 +
 
 +
Resizeable panel for configuring the display of spectrum data in radio 1's bandmap.
 +
 
 +
 
 +
[[image:Spectrumparamsr1.png]]
  
 
==Radio 2==
 
==Radio 2==
Line 735: Line 976:
 
All properties and settings are as per Radio 1. In SO2R this panel represents the second radio, in SO2V it represents VFO B of the radio.
 
All properties and settings are as per Radio 1. In SO2R this panel represents the second radio, in SO2V it represents VFO B of the radio.
  
==Digital Decoder Windows==
+
==Radio 2 spectrum parameters==
 +
 
 +
As per Radio 1. In SO2R this panel represents the second radio.
 +
 
 +
==Digital modes submenu==
  
 
There are four digital decoder windows (two for each radio), each enabled by selecting separately from the Windows menu.<br>
 
There are four digital decoder windows (two for each radio), each enabled by selecting separately from the Windows menu.<br>
Line 789: Line 1,034:
 
Example of MMTTY engine window.
 
Example of MMTTY engine window.
  
==DX-Cluster monitor==
+
==DX cluster monitor==
  
 
Shortcut: <code>[Alt][O]</code>
 
Shortcut: <code>[Alt][O]</code>
Line 807: Line 1,052:
 
* '''Stream logging'''
 
* '''Stream logging'''
 
: If checked, will save all lines displayed in the window to the file <tt>%appdata%\DXLog.net\DXCStreamHistory.txt</tt>
 
: If checked, will save all lines displayed in the window to the file <tt>%appdata%\DXLog.net\DXCStreamHistory.txt</tt>
: '''NB. This function is mainly intended for debugging and there is no automatic pruning of this file so it may grow very large with time.'''
+
: '''Important: This function is mainly intended for debugging and there is no automatic pruning of this file so it may grow very large with time.'''
 
: '''It is the responsibility of the user to prune or delete the file on a regular basis.'''
 
: '''It is the responsibility of the user to prune or delete the file on a regular basis.'''
  
Line 815: Line 1,060:
 
: connections in the DX Cluster monitor window, but with different color.
 
: connections in the DX Cluster monitor window, but with different color.
  
==DX-Cluster announcements==
+
==DX cluster announcements==
  
 
Shortcut: <code>[Alt][A]</code>
 
Shortcut: <code>[Alt][A]</code>
Line 830: Line 1,075:
  
 
Double click on a spot while holding down <code>[Ctrl]</code> to delete a spot.  
 
Double click on a spot while holding down <code>[Ctrl]</code> to delete a spot.  
 +
 +
Incoming spot logging can be useful when you want to analyze the spots post-contest. It also helps when<br>
 +
restarting DXLog, restoring your bandmap and DX Cluster announcements immediately. The log file can however<br>
 +
grow quite large and can be deleted if you find it impacts the performance of DXLog. The file is called<br>
 +
<tt>%appdata%\DXLog.net\DXCSpotHistory.txt</tt>.
  
 
For SO2V or SO2R mode: [Alt]-doubleclick on a spot will tune connected Radio 2 VFO A (or Sub VFO in SO2V with a dual<br>
 
For SO2V or SO2R mode: [Alt]-doubleclick on a spot will tune connected Radio 2 VFO A (or Sub VFO in SO2V with a dual<br>
Line 840: Line 1,090:
  
  
The window can display multipliers only, or spots for stations which can be worked in the current contest or stations<br>which may not be in the contest.
+
The window can display multipliers only, or spots for stations which can be worked in the current contest or stations<br>
 +
which may not be in the contest.
  
Spots displayed can be set manually per band or any number of bands or automatically from the connected radio band
+
Spots displayed can be set manually per band or any number of bands or automatically from the connected radio band.<br>
 +
The "current" band is the band of the active radio. In SO2R and SO2V, this means the currently focused radio.<br>
 +
The active band(s) can be selected either using the right-click menu or by clicking the band/Current labels in<br>
 +
the upper part of the window. In SO2R Advanced, the active radio is selected by pressing <code>[Keypad Multiply]</code>
  
  
Line 853: Line 1,107:
 
[[image:dx_cluster_announcement_2c.png]]
 
[[image:dx_cluster_announcement_2c.png]]
  
 +
 +
The spot quality tag from AR6 cluster nodes with CT1BOH skimmer quality tags enabled can be displayed. In addition to the<br>
 +
four standard tags V, B, ?, and Q, DXLog will show L for locally entered spots and C for B and ? spots containing a corrected<br>
 +
call in the comment field.
 +
 +
More information on skimmer spot quality can be found in the [[Additional_Information#Special_support_for_AR_Cluster_6|section about AR 6 clusters]].
  
 
Incorrect spot callsigns can be modified by right clicking the callsign and selecting ''Modify'' from the menu.
 
Incorrect spot callsigns can be modified by right clicking the callsign and selecting ''Modify'' from the menu.
Line 869: Line 1,129:
  
 
Spots can be deleted by right clicking the spot and selecting ''Delete'' or by holding down <code>[Ctrl]</code> and<br>double-clicking the spot.
 
Spots can be deleted by right clicking the spot and selecting ''Delete'' or by holding down <code>[Ctrl]</code> and<br>double-clicking the spot.
 +
 +
Spots can be sorted by in many ways. Most are self-explanatory but "SNR weighted by spotter" may not be. It means SNR non-linearly reduced<br>
 +
by spotter distance. In essence it means that SNR and spotter proximity is combined into a priority.
 +
 +
===Special features for SO2R===
 +
 +
The DX Cluster Announcements window has two features targeting advanced SO2R users.
 +
 +
Checking the menu option <i>SO2R Show both radios</i> will show spots from both current bands in SO2R allowing<br>
 +
efficient use of <i>SO2R Intelligent double-click</i> which offers very convenient S&P<br>
 +
on either of the radios. 
 +
 +
The "intelligence" is to do the below checks in sequence and act on the first one fulfilled:
 +
 +
If the shift key is pressed and the control key is not pressed use radio 1.
 +
If the shift key and control key are pressed use radio 2.
 +
If radio 1 is on the same band as the spot use radio 1.
 +
If radio 2 is on the same band as the spot use radio 2.
 +
If radio 1 is S&P use radio 1.
 +
If radio 2 is S&P use radio 2.
 +
If radio 1 has called CQ (F1 key) more recently than radio 2 use radio 2.
 +
If radio 2 has called CQ (F1 key) more recently than radio 1 use radio 1.
 +
Use radio 1.
 +
 +
==DX cluster own station spots==
 +
 +
Lists all spots of the own station's call on the DX cluster.
 +
 +
 +
[[image:ownspots.png]]
 +
 +
 +
You have a selection of what spots to show, depending on your operating situation,<br>
 +
SO1R, SO2V/SO2R, Multi-single, Multi-two, or Multi-multi.
 +
 +
Make sure to enable own spots from your cluster node. Read more in the [[Menu_Windows#World_Map|World map section]].
 +
 +
 +
[[image:ownspots_context.png]]
  
 
==Clock==
 
==Clock==
  
  
<br>[[image:clock.png‎]]
+
[[file:clock.png‎]]
  
  
Time information bar, including Sunrise and Sunset times and the active station callsign.
+
Time information bar, including Sunrise and Sunset times and the active station callsign  
 +
and the call of a logged in operator.
  
When the time is coming up to the hour the clock will turn dark red, when the time is on<br>
+
With default colors used, the text will turn
the hour the clock will be red (If default colours are used).
 
  
When the SR and SS times are close the SR and SS times will turn dark red, When SR and SS times<br>
+
* dark red when the time is within 30 minutes of sunset or sunrise.
are reached the times will turn red (If the default colours are used).
+
* clear red when the time is within 15 minutes of sunset or sunrise.
 +
* dark red during the 59th minute of each hour.
 +
* clear red during the first minute of each hour.
  
Left mouse click and drag to move.<
+
Left mouse click and drag to move. Right click on bar for options menu.
  
Right mouse click on bar for context menu.<br>
 
Fonts and colours can be set from this menu.<br>
 
  
 
+
[[file:clock_rc.png‎]]
::[[image:clock_rc.png‎]]
 
  
  
Line 898: Line 1,196:
 
In Run mode the clock background is grey but in S&P mode the Clock bar background is yellow (If default colors are used).
 
In Run mode the clock background is grey but in S&P mode the Clock bar background is yellow (If default colors are used).
  
 +
''Clock bar in run mode.''
  
''Clock bar in run mode.''<br>
+
[[file:Clock1.png]]
[[image:clock1.png]]
 
  
''Clock bar in S&P mode.''<br>
+
 
[[image:clock2.png]]
+
''Clock bar in S&P mode.''
 +
 
 +
[[file:Clock2.png]]
  
 
==Contest Recorder==
 
==Contest Recorder==
Line 916: Line 1,216:
  
 
The open source encoder libmp3lame.dll can be downloaded from '''http://www.rarewares.org/mp3-lame-libraries.php''' (see picture below) or <br>
 
The open source encoder libmp3lame.dll can be downloaded from '''http://www.rarewares.org/mp3-lame-libraries.php''' (see picture below) or <br>
from DXLog's web server repository '''http://dxlog.net/sw/files/utilities/libmp3lame-3.99.5x86.zip'''
+
from DXLog's web repository '''http://dxlog.net/sw/files/utilities/libmp3lame-3.99.5x86.zip'''
  
 
[[image:win32dll.jpg]]
 
[[image:win32dll.jpg]]
  
'''NB: Download the 32 bit version. The 64 Bit DLL version does not work on Windows 7,8 or 10 64 Bit systems.'''
+
'''Important: Download the 32 bit version. The 64 Bit DLL version does not work on Windows 7,8 or 10 64 Bit systems.'''
 
 
Extract the dowloaded archive file into DXLog installation folder.<br>
 
  
For 32 bit Windows this is usually <tt>C:\Program Files\DXLog.net</tt><br>
+
Extract the dowloaded archive file into DXLog installation folder which is usually <tt>C:\Program Files(x86)\DXLog.net</tt>
For 64 bit Windows this is usually <tt>C:\Program Files(x86)\DXLog.net</tt><br>
 
  
 
Encoding rate can be selected in a number of steps from 8kHz sample rate and 24kb/s coding rate to 32kHz sample rate and 96kb/s coding rate.<br>
 
Encoding rate can be selected in a number of steps from 8kHz sample rate and 24kb/s coding rate to 32kHz sample rate and 96kb/s coding rate.<br>
Line 934: Line 1,231:
 
Signals should peak top yellow on the Contest Recorder bar graph display for best results.
 
Signals should peak top yellow on the Contest Recorder bar graph display for best results.
  
To playback or extract, '''select the desired QSO in the log''', either by searching for the QSO number or manually selecting using the up/down arrows,<br>
+
To playback or extract, select the desired QSO in the log, either by searching for the QSO number or manually selecting<br>
then right click on the contest recorder and select PLAY QSO. For more playback options use the contest recorder right click context menu.
+
using the up/down arrows, then right click on the contest recorder and select PLAY QSO. For more playback options use<br>
 +
the contest recorder right click context menu.
 +
 
 +
The menu option "Auto-start recording" is saved on a per-log basis and makes recording start automatically<br>
 +
after opening the log. The option is automatically disabled when the recording is stopped manually or if the<br>
 +
most recent QSO in the log was more than 6 hours ago.
  
  
[[image:Contest_recorder_rc.png‎]]
+
[[file:Contest_recorder_rc.png‎]]
  
 
==SSB Bargraph==
 
==SSB Bargraph==

Latest revision as of 15:14, 29 December 2023

Custom multiplier windows

Windows for non-standard multipliers are shown at the top of the menu.

Examples are "Worked AGB" in AGB contests, "IT provinces" in ARI DX, etc.

Worked gridsquares

Shortcut: [Alt][L]

This selection is only available when relevant for the contest.


Gridsquare map.png


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


Gridsquare map properties.png


This form allows customization for your particular area and contest.

Worked Zones

Shortcut: [Alt][Z]


Zones.png


Worked zones window.

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


Zones ab.png


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


Zones rc.png


Right mouse click on the zones window for the context menu.
Zones window can be copied as an image to save for later use or paste into an email from the context menu. Note: this selection is only be available if enabled by the current contest.

Worked DXCC

Shortcut: [Alt][M]


Spotteddxcc.png


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

Continents are selected from the radio buttons at the top of the screen. The window's content
can be copied as text or a png image to the Windows clipboard and pasted into any
Windows application.

Display of spotted (default red) and expected (default yellow) DXCC is only be available
if enabled with Options->Statistics files.


Dxcc rc.png

Worked prefixes

Shortcut: [Alt][P]

Shows worked prefixes if enabled by contest. Note: this selection is only be available if enabled by the current contest.

Check callsign

Shortcut: [F9]


Band check.png


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

You can double-click a check mark to jump to the QSO in your log.

Check multipliers

Shortcut: [F10]


Check mult.png


When a callsign or country prefix is entered this window will indicate whether this multiplier has
been worked or not on the current (highlighted by a blue line) or other bands (and in other modes if the contest rules permit).

If the callsign entered has been worked on other bands, DXlog displays those QSOs.
Otherwise, the callsign of the first station worked in that multiplier on that band is displayed, if any.

If the contest has overlapping multipliers, meaning multipliers can be double (or even triple), only the first multiplier will be displayed in the window.

Additional information about the multiplier's country is displayed at the bottom:

  • Official country prefix and name
  • Average short (Az) and long path (Lp) antenna headings
  • Sunrise (SR) and sunset (SS) times

The update timing of the Check multipliers window is controlled by Tools|Data Entry|Exchange Guessing.

  • Pressing the space bar - information will be displayed when you press the spacebar.
  • Automatically - Information will be displayed while you are typing the call-sign.
  • After timeout - information will be displayed automatically after few seconds of filling in the call-sign field.

You can double-click on a line to jump to the corresponding QSO in your log.

Check partials

Shortcut: [F12]


Check part.png

With three or more characters entered, the Check partials window will show all callsigns
in the master callsign database that includes the entered string.

DXLog's master callsign data base contains the callsigns from all active prefill databases
together with those from the public check partials database.

With the default color settings, white callsigns are not in log, green callsigns are worked on another
band, and red callsigns are dupes. A bold callsign is an exact match.

A callsign can be grabbed to the entry field by double clicking on it.

The callsign in the upper left corner can be grabbed by pressing [Alt][Y].

Check part rc1.png


Right-clicking the window will display the context menu. Search can be started after only two characters
entered (not recommended), search can be limited to only the log, and prefill data can be displayed.

If more than one database is used, the values from each database are separated by slash "/".


Check part pfd.png


Reverse look-up

The Check Partials window is also where results from a reverse look-up is shown.
On supported contests, the call sign associated with an exchange can be displayed.
When only one one of the two first exchange fields is populated, pressing [Space]
will trigger a reverse look-up. DXlog will search for the entered exchange in all active
prefill data bases and show the matching callsigns in the Check Partials window.

In the picture below, the context menu option Show data from prefill database is also enabled.


Reverse look-up2.png

Check partials 2

The Check Partials 2 window behaves in the same way as the Check Partials window. If both windows
are open the Check Partial window will show the information for Radio 1 if SO2R and VFO A if SO2V
and the Check Partial 2 window will show the information for Radio 2 if SO2R and VFO B if SO2V.

Check N+1

Shortcut: [F8]


N+1.png


With at least three 3 characters are entered in the callsign entry field, the Check N+1 window will list all
callsigns from the super check partial database having a Damerau-Levenshtein distance of 1 or less.

In plain English this means all callsigns in the valid callsign database that can be created by either
removing a character, adding a character, or swapping two characters in the entered callsign.

With the default color settings, white callsigns are not in log, green callsigns are worked on another
band, and red callsigns are dupes. A bold callsign is an exact match.

A callsign can be grabbed to the entry field by double clicking on it.

N+1 rc.png


Right mouse click on the window shows the context menu. Optionally, search can be limited to only the current
log and content from an active prefill database can be displayed.

Check N+1 2

The Check N+1 2 window behaves in the same way as the Check N+1 window. If both windows are
open the Check N+1 window will show the information for Radio 1 if SO2R and VFO A if SO2V and
the Check N+1 2 window will show the information for Radio 2 if SO2R and VFO B if SO2V.

Search and Pounce

The Search and Pounce window serves as a scratchpad, remembering stations with their frequency.
For instance you may find a rare multiplier but you may want to try again a bit later when
the pile-up is less intense.

Note that the Search and Pounce window is local to the station and not networked.
Just as with the Partner window, Callsigns with frequency are added to the window with [Alt][Enter]

Except for also remembering the frequency and that double-clicking an entry does not delete it,
the window behaves like the Partner window.

If both the Partner window and the Search and Pounce windows are open, the operating mode will determine which one is used.
The Partner window will be used in RUN, and the Search and Pounce window will be used in... S&P.

Searchandpounce.png

Summary

Shortcut: [Alt][S]


Summary.png


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

Important: The Points and Multiplier counts may not include bonuses whereas the total score does.

Important: The QSO count includes X-QSO but excludes dupes.

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


Summary rc.png


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

Rate

Shortcut: [Alt][R]


Rate2.png


The panel displays live QSO rate data for the current contest log.

The top section shows QSO's in last hour, last 10 QSO rate, last 100 QSO rate,
rate for the current hour so far and, if enabled in the context menu, a projected score.

There is also a menu option for additionally showing the rate over the past 10 minutes.

The second section shows time on and time off in hours and minutes. The minimum off time
defined in the rules for the current contest is used in this calculation.

Important: Since DXLog does not know the starting time or duration of a contest,
the on/off time calculation starts and ends with the first and last QSO. This means that
if you do not join the contest from start, or end early, you will need to add this off time
time to the displayed off time manually.

The third section shows Run and S&P statistics. Both in total QSO count and the count since
the last full hour.

For a contest entry with band change limitations, the next section displays these.

For a contest with QRB-based scoring, the next section displays distance statistics.

The second to lowest section shows time since last multiplier, multiplier and QSO points worth.

Important: The calculation of multiplier points does not include factors like bonuses.

The last section shows operating mode and audio focus status.


Rate rc.png


Right click context menu allows you to set Target QSO's per hour, global QSO rate and other window properties.


Rate ru.png


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


Ratepermodeband.png


It is also possible to display a selective rate based on band and/or mode.

Operating info

Operating info2.png


Operating info window displays the radio active mode, if in SO2R it will display Radio 1: and Radio 2:
The CW repeat timer interval and the CW speed set in DXlog.

If you software interlock is active, the interlock status will be shown in the Operating info window.
Interlock blocking can be forbidden by clicking on the Interlock status line as shown below.
Interlocks can also be controlled by the $PILOCK (forbid) and $AILOCK (allow) macros.

The current interlock status/activity is shown in the Radio status window.


Operating info interlock.png

Operating info interlock forbidden.png


In SO2R Advanced mode the window will also show the currently active scenario.
Double-clicking the scenario name will bring up the scenario editor.


Operating info so2r.png


The Operating Info window also shows the current status of Intelligent Quick QSL, ESM, and Auto-CW.


Opinfostatus.png


If RUN/S&P switching is disabled, this is indicated with parentheses.


Opinfolocked.png

Contest statistics

Shortcut: [Ctrl][F9]


Statslog.png Statstarget.png Statsconts.png


The statistics window is a powerful tool for monitoring the station rates by band, mode, overall and optionally
against a pre-loaded target created from a previous year or competitor's previous public log.

There are three tabs, the first is the current log data, the second is comparison of the current log against
a pre-loaded target file and the third is % of continents worked for the log total.
Right clicking on any of the 3 tabs gives access to the tabs display options.

Without any logged QSO, the graphs may not show any meaningful information.

Log Tab Options

Statsdispdata.png


It is possible to copy any of the Statistics windows as image or text to the Windows clipboard.
This data can then be transferred into text document, Excel® or OpenOffice spreadsheet for further analysis during or post contest.

  • Displayed Data
    • Select which kind of data to display: QSOs, Multipliers, QSO Points, etc.
  • Band
    • All (total): Single color display, all bands combined
    • All (detailed): Multicolor display, one color per band
    • Current: Displays statistics for the current band
    • According to QSO: Displays statistics for the band of the currently selected QSO
  • Mode
    • All (total): Single color display, all modes combined
    • All (detailed): Multicolor display, one color per mode
    • Current: Displays statistics for the current mode
    • According to QSO: Displays statistics for the mode of the currently selected QSO
  • Display
    • By time: Displays an hour by hour comparison
    • Overall: Displays a cumulative (overall total) comparison

Target Tab Options

Statstargetmenu.png


  • Displayed Data
    • Select which kind of data to display: QSOs, Multipliers, QSO Points, etc.
  • Display
    • Overall Difference: Displays the overall difference to the target
    • Hourly Comparison: Displays a Comparison per hour + or - the target
    •  % Diff Per Hour: Displays a Percentage Difference + or - the target per hour
  • Export a target file: Exports the currently loaded log to a *.obf file for use as a target file.
  • Load a target file: Loads a previously created *.obf file for use as a target file.

Operator statistics

A resizeable window showing the operator QSO statistics.

QSO without a logged operator are counted as the station's callsign.

Operatorstatistics.png

Azimuth statistics

A resizeable panel showing the direction statistics of all QSO in the log as a spider web diagram.

The menu item is only visible for logs with distance-based scoring.


Azimuthstatistics.png

Gab

Shortcut: [Alt][I]


Gabcontext.png


The Gab window displays the chat between networked stations.

In the context menu,

  • Save history to file will save the gab chat history in a .gab file for the current contest.
  • Clear history will do exactly what it says.
  • Flash on new message will briefly change the background color of the Gab window with all incoming messages.
Regardless of this setting, messages containing "!" will always trigger this visual alert.
  • Sticky flash will make the alert background color stay until confirmed. Confirmation is done either
by sending a response or clicking anywhere inside the Gab window.

ALT+G opens a chat dialog for sending messages. It offers the option of either broadcasting
or directing the message to an individual station.

Double-clicking on a station name in the Status window will open the same chat dialog,
with the selected station's name as the selected destination. Double clicking your own station name will select
all stations as destination.

Network status

Shortcut: [Alt][J]


Status.png


The status window indicates the status of each station connected to the network.

From left to right, are displayed:
Station name, Current band and mode, Station type, QSY frequency of the current band and mode, Radio 1 frequency, Radio 2 frequency,
Time left before a possible QSY, according to the 10 minutes M/S rule, or "OK" if the station is allowed to make a
QSY on another band (only appears if the contest specifies this particular rule).

Your own station is displayed in a deep blue background.
A double left click on a station name will display the chat ("Gab") dialog with this station as the preselected destination.
A double left click on your own station name will display the chat ("Gab") dialog with ALL as the preselected destination.

With QSY focused radio unchecked a double left click on a valid frequency will set the VFO A on radio 1 to this frequency.

With QSY focused radio checked a double left click on a valid frequency will set:

The currently selected VFO to this frequency in SO1R and SO2V
The currently selected VFO on the focused radio to this frequency in SO2R

The context menu is accessed by right clicking the display part of the window.


Status rc.png


The Station ID may be changed in Options|Configure Network even if networking is disabled.

Skeds

Passed stations and scheduled QSO are listed in the Skeds window.

Recently added or skeds occurring soon have a bright yellow background, past skeds have a grey
background and future skeds have none.

  • Double click on a list entry to QSY to its frequency.
  • Hold down [Ctrl] and double click on a list entry to delete it.
  • Hold down [Alt] and double click on a list entry to QSY to its frequency on the second VFO
or the other radio in SO2R if Operating|Bandmap|QSY opposite radio instead of 2nd VFO is checked.

Right click on the window for a context menu (as shown below) to add, edit, and delete skeds.
There are also sorting options and for hiding past skeds.


Skedpass.png


For more information on how to populate and use the Skeds window, see the Pass a station section.

QSY wizard

The QSY wizard can be used with or without HamCAP installed and running.

One of its most important uses is for passing multipliers to other bands.
The Pass station panel is opened when clicking a band in the QSY wizard.

Operation with HamCAP is strongly recommended since it then offers real time
recommendations on contacts on other bands (QSY or sked).
(Options|HamCAP|Tab must be set to Charts.)

If used without HamCAP, it will always show "SKED" but is still very useful since
it offers single-click passing of e.g. multiplier stations to another band.

The QSY wizard is refreshed manually by pressing [Ctrl][P] with a valid
call in the entry field or automatically by checking the menu option
Options|Networking|Show QSY notification in QSY Wizard.

HamCAP can run in the background to avoid consuming screen real estate.

The wizard's recommendation (QSY or sked) will be based on HamCAP's propagation prediction.


Qsy wiz.png Qsy wiz hamcap.png


In the above example ZS6TX has been worked on 20m. After pressing [Ctrl][P] the
wizard tells us that 15m may be promising for a QSY.

For 10, 40, 60, 160m, however, the wizard instead recommends a sked.
This is the best time predicted by HamCap for this path. Hovering the mouse cursor over the yellow square
on the Hamcap chart will give more information including the MUF and signal elevation etc.

Bands for which a multiplier is needed are highlighted using a diffrent background color.
In the picture below S5 is needed 160, 40, and 10m.


Qsywizard-needed.png


The the colors used are selectable via the right click context menu Colors.

Clicking on a band line brings up the Pass a Station panel filtered pre-populated for the clicked band.

QTC Editor


Qtceditor.png


This window allows editing of QTC (as used in e.g. WAE DX contest) in ways not possible using
the regular receive and send QTC windows mechanics. Double click an item to modify it.

The right-click menu offers additional features, such as scrolling to the top or bottom and searching for a station callsign.

Clicking the column headers enables sorting.

Extra Information


Extrainfowindow.png


The Extra Information window displays information contained in a text file based on the call entered in the
log callsign entry field. Files should have the .xdt file extension.

The format of the Extra information file is very simple:

#TITLE Name of info
K6MR Ken #1270 Anderson CA
K6NA Glen #548 Valley Center CA
K6NR Dana #2380 Irvine CA
K6NV Bob #675 Truckee CA
K6PB Pete #2469 Irvine CA

For proper display of non-ASCII characters, make sure the file is UTF-8 encoded.

The text following #TITLE keyword will be shown on the window's header.
If the #TITLE line is omitted, the complete path and filename will be shown.

Data lines (one per call) begin with the call sign and a single space.
Any information present after the first space will be shown exactly as formatted in the file.
Multiple files may be used to show data from different sources.

  • To add a file - Right mouse click in the extra information window and select "Extra data files".
Click 'Add' and select the file from the file selection form.
  • To remove a file - Right mouse click in the extra information window and select "Extra data files",
select the file to be removed, and click 'Remove'.

If a file is updated while open in the window, right click and select "Reload files" to use the new data.

The window is also used to display the result of online look-ups from hamQTH and QRZ, configured via
the Options|Data files|Extra info plugins menu.

A selection of XDT files for download can be found on the DXLog.net web server.

Partner


Partner.png


This feature is especially useful in a Multi-OP environment when facing large pile-ups and/or weak signals.
Set up an additional operator, as support with an additional computer which has the same version of DXlog installed.
Connect a pair of headphones to the same receiver as the operator, then on both comptuers open up the Partner window,
on the partner computer enter the same band and mode as the run station. Note that deleting the call on the partner
computer when grabbing is optional.

Networking needs to be enabled on all stations.

The running operator continues as before, working the callsign he hears.
The support operator listens at the same time and tries to copy additional callsigns from the pile-up
by entering the callsign on the QSO entry field and then pressing Alt-Enter.
This callsign will now be displayed in the Partner Window stack for the running operator to use as his next contact.
The Partner window can hold up to nine callsigns which can be grabbed into the callsign field with [Alt][1] to [Alt][9].

Once the QSO is logged, that callsign will disappear from both partner windows.
The partner can remove a callsign if incorrect or no longer valid using [Alt][1] to [Alt][9].
A field in the partner window can be overwritten with a new entry by using [Ctrl][1] to [Ctrl][9].

Partner window use in RTTY

The Partner window is also useful when used in a RTTY environment.
In addition to using [Alt][1-9] and [Ctrl][1-9], calls may be entered onto
the stack by selecting a call in the RTTY receive window using the mouse pointer.
Two callsign selection methods are available:

1. [Alt][LeftClick] (left mouse click while holding down the Alt key)
2. [MiddleClick] (pressing hte scroll wheel click on most mice)

Subsequent selections in the RTTY receive window will populate the next empty line in the Partner window.
To place calls from the Partner window stack into the active QSO line, the $GRABPARTNER macro can be used
in a message to grab the first call from the Partner window stack.
Typically this can be used in a special TU message to confirm the current QSO,
enter the next call, and send the report, e.g.:

$13 $CORRECT TU $GRABPARTNER NOW $LOGGEDCALL $F2 $CR

Multi Partners and real time updates

Partnercont.png


The partner window can also be set to display the typing done by support stations in real time.
Right click on the window and select Real time|Enabled. This option will give you up
to three additional lines at the top of the window that will reflect the typing of your partner stationn.

Normally the only the run stations displays the typing of the support stations but by checking the
option Always send data will make the station broadcast its typing to other partners regardless of role.

The options for real time are for the runner or the support, as runner you can have a live entry field that is
1, 2 or 3 slots long. As support you can select to post into either of the 3 slots, this gives the option of up
to 3 support stations each with a specific line to update live as the callsign is typed on the support station.
When Always send data is checked, both the runner and support options are valid.

Partner window use for M/2

For M/2 stations the station type - partner is grayed out, each station can have up to 3 partners, the partner window
should be set to real time and the partner stations on the same band and mode as the run station.

No Band/Mode Filter option

With this option checked all callsigns entered from support stations irrespective of band or mode will be displayed.

Radio status

The radio status window shows the transmit and interlock status of each enabled radio.
When successfully transmitting, this is indicated by a green bar.
When blocked, this is indicated by a red bar which also includes information
about the source and reason of the blocking.


Radiostatustransmit.png Radiostatusblocked.png

Antenna selector R1/R2

The antenna selector windows are showing the available antennas for the chosen band for each radio.


Antennaselector1.png Antennaselector2.png


DXLog's antenna selection mechanics can use a microHAM keyer with an ACC port (e.g. MK2R+),
an OTRSP device with at least two Aux ports or a parallel printer interface (i.e. LPT port).

The band/antenna association, required control pin values, and operator friendly name
are set up in the configuration panel for the used device.

  • microHAM configuration: Options|microHAM configuration
  • OTRSP device configuration: Options|OTRSP device configuration
  • Printer port: Options|Configure interfaces Printer port Setup

For more detailed information on how to configure each interface, see microHAM configuration,
OTRSP device configuration, and Printer port configuration.

With a microHAM keyer it is possible to use a different antenna for receive and transmit.
To enable this functionality Options|Interface specific options|Allow different RX/TX antenna must be checked.
Different antennas for receive and transmit when using an OTRSP device or printer port is not supported.

Important: Using a different antenna for receive and transmit only works when DXLog either exclusively controls, or is
aware of, the transmit/receive status, e.g. through a footswitch.
Tip: For microHAM devices DXLog is aware of the keyer's PTT status if Enable TX lock/unlock is checked.

Important: Cross band operation is not supported. The band of VFO A always determines the antenna selection.

It is possible to have several antennas for each band (as well as antennas covering multiple bands,
such as a triband yagi or a trap vertical).

All allowed antennas for the current band are listed. The selected antenna is highlighted.
The last used antenna on a band is not remembered. When switching to a new band, the first
allowed antenna listed in the configuration will always be selected.

The antenna selection can either be made through keyboard shortcuts [Alt][F11] (receive or transceive antenna)
and [Alt][Shift][F11] (transmit antenna) or by clicking on the name of the desired antenna in the window.

Antenna controller R1/R2

Only visible when using a networked antenna server.

Antenna rotator R1/R2


Rotatorr1.png


The Antenna rotor R1 and Antenna rotor R2 windows links with an external rotator software using UDP messages for setting the desired direction as well as showing the current direction.
The window takes the information from the rotator configuration window for band, rotator, IP address and UDP port of the rotator server.
The windows link nicely with PSTrotator, in PSTrotator the UDP control setup must be set to the same UDP port as the rotator in DXL for the relevant band.
UDP control must be enabled in PSTrotator, then when a band is selected that has a rotator in the rotator onfiguration the window will show the AZ for that antenna.
Turn the rotator by either inserting a callsign, a prefix, or an azimuth in degrees into the log entry line and press [Ctrl][F12] for SP or [Alt][F12] for LP.


Rotatorr1op.png


Right click on the window to access the context menu, the menu has turn antenna to - with a list of basic directions.

World Map


Map.png


A color world map showing the current distribution of daylight and the location of the greyline.

Unlike most other DXLog windows, the World map can be resized.

The properties of the map can be configured by right-clicking on it.

The map can show the location of stations and skimmers spotting the own station's call.
The spots fade when they reach the age of the spot lifetime set in the bandmap properties panel.

By default, spots on the band of radio 1 (or of any band, when all bands are displayed)
are red and spots on the band of radio 2 are yellow.


Map rc.png

Worldmap2radios.jpg


Either only spots on the station's active band(s) or on all bands can be shown.
The size of the map can also be changed using the zoom option in the right click menu.

VERY IMPORTANT When using this function, it is essential that the DX cluster node connected
to is set up to forward all spots of own callsign. Otherwise the display will not be reliable.

DXSpider - Make sure the node you connect to is version 1.57 build 434 or later.
Send the command SET/SEEME to make all spots of the logged in call pass through unfiltered.
CC Cluster - Send the command SET/OWN to make all spots of the logged in call pass through unfiltered.
AR Cluster - If you are using filters, make sure to add an exception for your own call, e.g.,
...OR CALL=SM7IUN (If you are SM7IUN, that is)

Note that you need to log on to the cluster node with the station's call for the above features to work.

Map menu.png

Band notes

Bandnotes.png

A user configurable window that shows information about the current active band.

It can be used to show license band segments, antenna tuner or PA settings, etc.

DXLog looks for configuration information in two places.

  • The first place is the folder of the current log file. DXLog looks for a file with the same name as
the log file but ending with _BandNotes.txt, e.g., CQWW2023_CW_BandNotes.txt
  • The second place is the %appdata%\DXLog.net configuration folder.
DXLog looks for a file called BandNotes.txt

If none of these files exist, DXLog uses a standard file that is part of the installation.

The formatting of the band notes file is as follows:

  • Blank lines or lines beginning with a hash symbol are ignored.
  • The structure of a line is Mode;Lower Freq;Upper Freq;Color;Text
The keyword ALL matches any mode.
A line is highlighted if the frequency of the currently focused radio falls within its range and has the right mode.
The color is a number between 1 and 5 and can be changed in the Band Notes window's color settings.
If color is followed by the letter H it is hidden when the frequency is not in range.
If the color is followed by the letter N it is never highlighted.
The color number can be followed by both H and N, e.g., 5HN.

One obvious application of this panel is PA settings, like shown below.
Since this is not contest-specific information it is best stored as %appdata%\DXLog.net\BandNotes.txt


Bandnotespa.png

Example file content:

# 160m
ALL;1800;1850;3H;Load 44 Tune 67
ALL;1850;1900;3H;Load 47 Tune 65
ALL;1900;1950;3H;Load 52 Tune 62
ALL;1950;2000;3H;Load 55 Tune 59
CW;1800;1900;3H;Power 33
CW;1900;2000;3H;Power 35
SSB;1800;1900;3H;Power 27
SSB;1900;2000;3H;Power 29

Radio 1


Radio1.pngRadio1list.png


Radio information displaying VFO A and VFO B frequency information.
Click on the VFOA and VFOB boxes to switch to select the respective VFO.

Note: If you have automatic RUN/S&P selection enabled, a switch of VFO will change operating mode to S&P.
For convenience, it is recommended to combine this option with the option F1 always return to Run.

The Band map tab shows the currently selected radio band and any DX Cluster received or locally
entered callsigns plus other optional information.

Callsigns preceded by bullets are skimmer spots. Callsigns preceded by a plus sign are manual spots.
Callsigns preceded by a star contain split ("QSX") information.

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

In the list mode an colored bar will show the position of the currently selected
VFO and an underline indicates the position of the unselected VFO.

The default coloring is: RED = Double Multiplier, GREEN = Multiplier, Black = Unworked, GREY Italics= Worked
Information below the horizontal divider is available multiplier numbers, available QSO count, and points available.

Double clicking on a callsign sets the focused radio VFO to that frequency and mode
(including split if such information is provided in the spot comment) and puts the callsign
into the log callsign field. This can be changed to a single click by
selecting the enable single click selection from the context menu.

Double clicking while holding down [Alt] will grab the spot to the other VFO.
If the option Operating|Band map|QSY other radio instead of 2nd VFO
is checked, the spot is grabbed to other radio.

Double clicking while holding down [Ctrl] will erase the spot.

Context menu

A right click anywhere in the band map will bring up the context menu.
Band map options are changed by selecting the appropriate menu.


Bandmap context menu.png


Most menu selections are self explanatory.

Show from higher to lower frequency will show the higher band segment edge at the top.
The default band map display is to show lower frequencies at the top, higher frequencies at the bottom.
As you tune up the band, the band map will move up as the cursor points to a higher frequency.
If you would prefer that the band map show higher frequencies at the top (with resulting
movement down as you tune up the band), check this option.
This option may be changed at any time and the band map will redraw automatically.


Radio1 rc so2.png


In list mode the data can be sorted in a number of ways. This is set with the context menu.


Radio1 rc do3.png


Display options for both Band Map and List mode are set by right-clicking the pane and selecting Display options.
Note that when Multiplier only in list view & grabbing is enabled, [Ctrl][Up] and [Ctrl][Down]
will only grab multiplier spots. Using the mouse or [Ctrl][Space], any spot can still be grabbed.

Spot quality will display spot quality tags reported by AR version 6 cluster nodes.
More information on spot quality display can be found in the section about AR 6 clusters.

Exchange will show prefill database or zone data depending on the type of exchange.

Spectrum enables the display of a real time spectrum overlaid on the bandmap.
It requires a supported radio or external SDR. An example display is shown below.


Spectrum 1.png


The option Show station information will show information from the most recent spot of the currently
selected/highlighted callsign at the bottom of the bandmap, replacing the available QSO information.


Radio1 rc pr.png


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

Important: The Wipe QSO setting is prone to false triggers and may clear the entry line also when not wanted,
such as when using keys such as [Alt][F4] or [Shift][Ctrl][F1].

Bandplan settings

The Bandplan Settings panel is accessed from the Properties form.

Important: The sole purpose of the bandplan is for guessing the mode of spots that do not explicitly
show their mode in their comment.

Click Setup in the bandplan section of the Properties panel to display the current bandplan settings.
The current band will be displayed by default. Be sure to save changes to a Bandplan memory (Default, or Bandplan 1 through 9).
Note that clicking OK will save any changes to the currently active bandplan.
To edit a different bandplan than the one currently active, click its button in the Load button group.

If a bandplan has no settings, its Load group button will be grayed out.
To use a new Bandplan memory, save the current settings by clicking its button in the Save as button group.
Modify as required and save using the same button.

The Reset button will reset the Default bandplan to its original settings and select it.

If you wish to activate the currently selected bandplan, check the box in the lower left
corner of the form before you click OK.

Important: Spots falling outside all of the defined mode segments for a band will be ignored, regardless of their comment.

The mode of a spot is determined either by an explicit tag in beginning of the spot's comment ("SSB", "CW", etc.)
or, when this is missing, by the bandplan segment it falls within. In the case of overlapping mode segments,
the search order is: CW, SSB, RTTY. The first segment found that includes the spot's frequency determines its mode.

Mode checking is enforced based on contest entry category. In a single mode entry, only spots of the contest entry's
mode are displayed. In a mixed mode entry, spots for all the allowed modes are displayed.

This means that spots with an explicit mode tag, falling within any of the band's mode segments, and relevant
for the contest entry, will be displayed.

It also means that for spots without an explicit mode tag, only spots falling within the band segments relevant
for the contest entry will be shown. Spots without an explicit mode tag are often manual spots or spots received from a
local skimmer. This makes it important to sometimes adjust the bandplan.

Example: For a massive CW contest like CQ WW it may be a good idea to extend the CW segments in your bandplan, e.g.
14000-14125 for 20m. For a CW contest like this, skimmer spots (which all have a mode tag) will be displayed regardless of
frequency as long as they are within any of the active mode segments (SSB etc.) for the band.
Human spots (or others lacking a mode tag) will however only be displayed if they fall within the CW segment for the band.
The exception is however for spots CW originating from the Telnet ports of RBN Aggregator and CW Skimmer Server.
They will always be considered CW spots and not be subject to the bandplan rules.

The bandplan's frequency ranges thus serve two purposes:

  • Spots not falling inside any of the mode frequency ranges will be ignored
  • Spots lacking mode information will be assigned a mode based on the frequency range they fall inside.

For more information about handling spots, see DX Cluster options


Radio1 rc pr bp2.png

Radio 1 spectrum parameters

Resizeable panel for configuring the display of spectrum data in radio 1's bandmap.


Spectrumparamsr1.png

Radio 2

All properties and settings are as per Radio 1. In SO2R this panel represents the second radio, in SO2V it represents VFO B of the radio.

Radio 2 spectrum parameters

As per Radio 1. In SO2R this panel represents the second radio.

Digital modes submenu

There are four digital decoder windows (two for each radio), each enabled by selecting separately from the Windows menu.
The four selections are located just below the Radio1/Radio2 band map menu picks, and the exact wording is dependent on the RTTY Configuration.

IMPORTANT: Radio 2 windows will only be active if SO2V, SO2R or Advanced SO2R are enabled in Operating|Technique.


Data radio menu.png


Before using the decoder windows, they must be configured using the RTTY Configuration panel: Options|RTTY Configuration


RTTY Config.png


After configuration, each decoder window menu selection will show which decoder has been configured, for each selection (Primary/Secondary)
and radio (Radio 1/Radio 2). Note that the Primary decoder is the decoder used for the transmit interface, usually MMTTY.

Selecting the appropriate menu pick will open the decoder window. The Primary decoder window will display a set of clickable buttons
at the bottom that duplicates all message function keys. The Altx buttons provide access to the messages defined in the
Alt-C (Other Messages) form. In addition, there is an Alt-K button (open keyboard mode window) and a (C) button (clear decoder window).

Callsign and exchange can be grabbed from the decoder window by clicking. Holding down [Alt] while clicking will grab a
call to the partner stack.


Rttymmtty.png RTTY R1R.png


When the decoder windows are opened the first time, it will be necessary to configure each one for input and output parameters such
as sound card, FSK port, etc. These settings will be saved by the decoder program and only need to be configured the first time.

Right click on the main decoder screen opens the options dialog


Parse.png


Clear window will clear the receive screen characters.

When Parse is checked, it will parse full line and sends to other windows for processing.
For example, in QTC receive window, it will parse full qtc line and populate all fields (utc, call, serial)

Note: MMTTY will only save the FSK port settings if you close the MMTTY windows before closing DXLog.
If you let DXLog close the MMTTY windows the FSK port will reset to NONE and will need to be selected at the next use.


MMTTY.png


Example of MMTTY engine window.

DX cluster monitor

Shortcut: [Alt][O]


Dx cluster monitor.png


Floating window displaying live information from the connected DX Cluster as received.

Right mouse click on the window for context menu.


Dx cluster monitor rc.png


  • Stream logging
If checked, will save all lines displayed in the window to the file %appdata%\DXLog.net\DXCStreamHistory.txt
Important: This function is mainly intended for debugging and there is no automatic pruning of this file so it may grow very large with time.
It is the responsibility of the user to prune or delete the file on a regular basis.
  • Show network stream
If more than one networked PC is in use, and you run a connection to DX Clusters
on more than one of the PC's in the network, checking this option will show data from all DX Cluster
connections in the DX Cluster monitor window, but with different color.

DX cluster announcements

Shortcut: [Alt][A]


Dx cluster announcement b.png


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

Double click a spot and it will tune connected Radio 1 VFO A (or Main VFO of a Dual RX radio) to the
spot frequency and auto enter the callsign into the log callsign entry field.

Double click on a spot while holding down [Ctrl] to delete a spot.

Incoming spot logging can be useful when you want to analyze the spots post-contest. It also helps when
restarting DXLog, restoring your bandmap and DX Cluster announcements immediately. The log file can however
grow quite large and can be deleted if you find it impacts the performance of DXLog. The file is called
%appdata%\DXLog.net\DXCSpotHistory.txt.

For SO2V or SO2R mode: [Alt]-doubleclick on a spot will tune connected Radio 2 VFO A (or Sub VFO in SO2V with a dual
receiver radio) to the spot frequency and auto enter the callsign into the log callsign entry field.

Spot display choices can be set by right clicking on the window and selecting from the context menu.


Dx cluster announcement 0.png


The window can display multipliers only, or spots for stations which can be worked in the current contest or stations
which may not be in the contest.

Spots displayed can be set manually per band or any number of bands or automatically from the connected radio band.
The "current" band is the band of the active radio. In SO2R and SO2V, this means the currently focused radio.
The active band(s) can be selected either using the right-click menu or by clicking the band/Current labels in
the upper part of the window. In SO2R Advanced, the active radio is selected by pressing [Keypad Multiply]


Dx cluster announcement 1c.png


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


Dx cluster announcement 2c.png


The spot quality tag from AR6 cluster nodes with CT1BOH skimmer quality tags enabled can be displayed. In addition to the
four standard tags V, B, ?, and Q, DXLog will show L for locally entered spots and C for B and ? spots containing a corrected
call in the comment field.

More information on skimmer spot quality can be found in the section about AR 6 clusters.

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

Based on preference, you can select single-click selection, the default being double-click.


Spot mod.png


Double-clicking while holding down [Alt] offers several options for grabbing the spot to the other
radio or VFO.


Dx cluster announcement 3c.png


Spots can be deleted by right clicking the spot and selecting Delete or by holding down [Ctrl] and
double-clicking the spot.

Spots can be sorted by in many ways. Most are self-explanatory but "SNR weighted by spotter" may not be. It means SNR non-linearly reduced
by spotter distance. In essence it means that SNR and spotter proximity is combined into a priority.

Special features for SO2R

The DX Cluster Announcements window has two features targeting advanced SO2R users.

Checking the menu option SO2R Show both radios will show spots from both current bands in SO2R allowing
efficient use of SO2R Intelligent double-click which offers very convenient S&P
on either of the radios.

The "intelligence" is to do the below checks in sequence and act on the first one fulfilled:

If the shift key is pressed and the control key is not pressed use radio 1.
If the shift key and control key are pressed use radio 2.
If radio 1 is on the same band as the spot use radio 1.
If radio 2 is on the same band as the spot use radio 2.
If radio 1 is S&P use radio 1.
If radio 2 is S&P use radio 2.
If radio 1 has called CQ (F1 key) more recently than radio 2 use radio 2.
If radio 2 has called CQ (F1 key) more recently than radio 1 use radio 1.
Use radio 1.

DX cluster own station spots

Lists all spots of the own station's call on the DX cluster.


Ownspots.png


You have a selection of what spots to show, depending on your operating situation,
SO1R, SO2V/SO2R, Multi-single, Multi-two, or Multi-multi.

Make sure to enable own spots from your cluster node. Read more in the World map section.


Ownspots context.png

Clock

Clock.png


Time information bar, including Sunrise and Sunset times and the active station callsign and the call of a logged in operator.

With default colors used, the text will turn

  • dark red when the time is within 30 minutes of sunset or sunrise.
  • clear red when the time is within 15 minutes of sunset or sunrise.
  • dark red during the 59th minute of each hour.
  • clear red during the first minute of each hour.

Left mouse click and drag to move. Right click on bar for options menu.


Clock rc.png


When Tools|Data entry|Enable Run/S&P switching is enabled the Clock bar will show the mode of
operation for each radio/VFO.

In Run mode the clock background is grey but in S&P mode the Clock bar background is yellow (If default colors are used).

Clock bar in run mode.

Clock1.png


Clock bar in S&P mode.

Clock2.png

Contest Recorder


Contest recorder.jpg


The contest recorder allows you to record two audio channels for a whole contest in MP3 format onto your hard drive.
The two channels can be radio 1 and 2 for SO2R or main and sub receiver for SO2V.

Since Windows does not come with a native MP3 encoder enabled, it is necessary to install a third party encoder.

The open source encoder libmp3lame.dll can be downloaded from http://www.rarewares.org/mp3-lame-libraries.php (see picture below) or
from DXLog's web repository http://dxlog.net/sw/files/utilities/libmp3lame-3.99.5x86.zip

Win32dll.jpg

Important: Download the 32 bit version. The 64 Bit DLL version does not work on Windows 7,8 or 10 64 Bit systems.

Extract the dowloaded archive file into DXLog installation folder which is usually C:\Program Files(x86)\DXLog.net

Encoding rate can be selected in a number of steps from 8kHz sample rate and 24kb/s coding rate to 32kHz sample rate and 96kb/s coding rate.
For most users 8kHz/24kb/s is adequate and the least consuming on storage.
The rate is set in the MP3 Configuration panel accessible via Options|MP3 configuration.

Recording levels are not set in DXLog, but in Windows' Recording Devices settings.
Signals should peak top yellow on the Contest Recorder bar graph display for best results.

To playback or extract, select the desired QSO in the log, either by searching for the QSO number or manually selecting
using the up/down arrows, then right click on the contest recorder and select PLAY QSO. For more playback options use
the contest recorder right click context menu.

The menu option "Auto-start recording" is saved on a per-log basis and makes recording start automatically
after opening the log. The option is automatically disabled when the recording is stopped manually or if the
most recent QSO in the log was more than 6 hours ago.


Contest recorder rc.png

SSB Bargraph


SSB Bargraph.png

Bargraph showing output of recorded files for Function Keys.

Drag to move

Right mouse click on bargraph for context menu.


SSB Bargraph rc.png