Configuring DXKeeper is primarily accomplished via the Configuration window and the QSL Configuration window. Defining bands and defining or eliminating modes, however, are accomplished by editing files.
DXKeeper's Configuration window presents 8 tabs:
the General tab enables you to set or reset various options, and configure the online help system
the Log tab lets you select a log file, and configure the log display
the Awards tab enables you to specify the bands and modes for which you seek QSLs
the Reports tab lets you configure the reports award status reports that DXKeeper generates
the Callbook tab enables you to specify the location of the Radio Amateur Callbook on your PC so that DXKeeper can query it
the Contest tab enables you specify the settings that govern DXKeeper's support for contest operation
the User Items tab lets you configure up to 8 user-defined items stored with each QSO
the Defaults tab lets you specify default values for QSO items, shows pathnames and versions for the DXCC, IOTA, and LotW databases, and provides control over DXKeeper's TCP/IP server
| Display seconds in date/time fields |
When checked, begin and end items are displayed using the locale's standard date/time format with hours, minutes, and seconds When unchecked, begin and end items are displayed using the locale's standard date/time format with hours, and minutes |
| Display Previous QSOs on Lookup |
When checked, entering a new callsign in the Main window or clicking the QSO Capture window's Lookup button filters the log to only display previous QSOs with the captured Callsign, and initializes the Capture window with information extracted from those QSOs |
| Highlight duplicate QSOs | When checked, QSOs in the Log Page Display that match the QSO Capture window's callsign, band, and mode will be highlighted in red font |
| Set QSO start when RST Rcvd | When checked, automatically set the QSO start time when a received signal report is entered in the Capture window |
| Initialize RST fields to default | When checked, automatically sets the Main and Capture window RST sent and RST rcvd items to the specified default value; if no default value is specified, these items are initialized to 59 (for phone modes) or 599 (for non-phone modes) unless another report has already been entered, and selects the entire contents of these fields whenever they gain focus |
| New QSO on DX Spot activation | When checked, create a QSO in the Main window when a DX Spot is activated (in SpotCollector, DXView or Commander) with the Capture window closed and Optimize for realtime QSO entry checked |
| Spot split frequency | when checked, outgoing spot notes will include the difference between the Capture window's TX and RX frequencies unless that difference exceeds 9.9 KHz, in which case the full TX frequency will be included |
| Backup log on shutdown | when checked, automatically creates a Log backup on shutdown if a log file is open |
| Flag invalid callsigns | When checked, callsigns not containing at least one number and one letter will be flagged when you attempt to Save in the Main window or Log in the Capture window; QSOs containing such callsigns will be marked Broken by the Recompute function |
| Provide audible feedback |
When checked,
|
| Display information in title bars | When checked, displays log information in the Main window's title bar and UTC time in the Capture window's title bar (uncheck when running on Vista) |
| Use multiple monitors | When checked, windows that resided on a secondary monitor during the previous session will be restored to the same secondary monitor on startup; when not checked, all windows are restored to the primary monitor on startup |
| Log debugging information | When checked, records debugging information to the file ErrorLog.txt in DXKeeper's folder |
| Require Edit to modify logged QSOs | if this box is checked, the QSO currently selected on the Main window's Log QSOs tab cannot be modified without first clicking the Edit button |
| Confirm QSO deletion |
if this box is checked, DXKeeper will request confirmation before deleting a QSO |
| Optimize for realtime QSO entry |
When this box is checked, DXKeeper's Main window is optimized for logging QSOs in real time:
When this box is unchecked, DXKeeper's Main window is optimized for manually entering past QSOs:
Note that the Optimize for realtime QSO entry setting has no effect on the Capture window's behavior, which is always optimized for logging QSOs in real time. |
| Optimize for roundtable QSOs |
When this box is unchecked and Optimize
for realtime QSO entry is unchecked, a new QSO's begin
item is initialized to the last manually-entered
QSO's end
item incremented by 1 second.
When this box is checked and Optimize for realtime QSO entry is unchecked, a new QSO's begin item is initialized to the last manually-entered QSO's begin item incremented by 1 second. |
| Allow direct Subdivision entry | when checked, for QSOs with DXCC entities that specify Primary and Secondary Administrative Subdivisions, these subdivision items can be directly entered and edited in the Award panel on the Main window's Log QSOs tab |
| Run-mode checkbox |
If this box is checked, striking the enter key in the call textbox will
If this box is checked, striking the enter key in the QSO Capture window's Call textbox will set the RST sent and RST rcvd items to 59 (if the mode is SSB or FM) or 599 (if the mode is CW, RTTY, or PSK) |
| Capture always on top | When checked, the Capture window always appears atop other windows |
| Capture callsign generates prop forecast | When checked with DXView running, entering a callsign in the Capture window and striking the Enter or Tab key or clicking the Lookup button directs PropView (if running) to generate a propagation forecast for the station's location on the captured TX frequency |
| Local spot on callsign acquisition | When checked with SpotCollector running, an outgoing local spot will automatically be generated entering a callsign in the Capture window and striking the Enter or Tab key |
| Capture window F-keys via WW |
When checked
|
| Prompt on Capture overwrite | When checked, if an action -- e.g. activating a Spot Database entry in SpotCollector-- would overwrite unsaved Capture window data from an active QSO, DXKeeper will display a dialog box allowing the user to allow or disallow the overwrite. A QSO is considered active if its start time has been set, either by clicking the Begin button or by capturing a received signal report (if Set QSO start when RST Rcvd is checked) |
| Prompt on Capture clear | When checked, clicking the Capture window's Clear button displays a dialog box confirming the user's intention to clear the Capture window items |
| Call textbox | place the mouse cursor in the QSO panel's Call textbox after completing an operation on the Main window's Log QSOs tab |
| Filter textbox | place the mouse cursor in the Filter panel textbox after completing an operation on the Main window's Log QSOs tab |
| Miles | QSO distance is displayed in miles |
| Kilometers | QSO distance is displayed in kilometers |
| Browser pathname textbox |
if this setting is blank, DXKeeper displays online help using your PC's default HTML browser; if this setting contains the pathname of an HTML browser, DXKeeper displays online help using that browser. |
| Select button |
displays a file selector dialog that allows you to choose a Browser pathname |
| show control explanations |
when checked, enables the display of explanatory information when the mouse cursor lingers over a textbox, button, checkbox, display pane, or setting. |
| DXCC Database panel | shows the pathname and version of the DXCC Database being used by DXKeeper |
| IOTA Database panel | shows the pathname and version of the IOTA Database being used by DXKeeper |
| LotW Database panel | shows the pathname and version of the LotW Database being used by DXKeeper |
| eQSL AG Database panel | shows the pathname and version of the eQSL Authenticity Guaranteed Database being used by DXKeeper |
| Pathname textbox |
This textbox specifies the pathname of the current log file. To open a different log file or create a new log file, you can enter or paste the appropriate pathname into this textbox and then click the Select or Create buttons in this panel. Alternatively, you can click the Select button in this panel and use the file selector dialog to choose the log file you wish to open or create. Note: If you start DXKeeper with a command line argument that specifies a valid pathname, DXKeeper will place this argument in the Pathname textbox and attempt to open the designated file as a log. |
| Open Button |
closes any open log and opens the log in the file specified by the Pathname textbox; this button is only present when the Pathname textbox specifies an existing file |
| Create Button |
closes any open log, and creates a new log in the file specified by the Pathname textbox; this button is only present when the Pathname textbox specifies a non-existent file If DXView has been installed on your PC, the newly-created log's progress table will be initialized using the DXCC database managed by DXView. If DXView has not been installed, the newly-created log's progress table will be initialized from the file DXCC.mdb in the Databases subfolder of your DXKeeper application folder. |
| Compact Button | If you delete QSOs in a log, the log file can become fragmented and use disk space inefficiently. Compacting the log file re-arranges the files contents to improve storage efficiency. |
| Select Button | displays a file selector dialog with which you can navigate to a desired folder and select a log file to open; if the selected file exists, any currently-open log is closed and the selected log file is opened |
| New Button |
displays a
file selector dialog with which you can navigate to a desired folder and
specify a new log file to be created; if the specified file does not
exist, any currently-open log is closed, and the specified log file is
created and then opened
If DXView has been installed on your PC, the newly-created log's progress table will be initialized using the DXCC database managed by DXView. If DXView has not been installed, the newly-created log's progress table will be initialized from the file DXCC.mdb in the Databases subfolder of your DXKeeper application folder. |
|
this textbox specifies the pathname of folder into which log backups will be stored |
|
|
creates a backup copy of the current Log file in the specified backup folder pathname |
|
| Recover button | replaces the contents of the current Log file with the contents of a specified backup copy |
|
when checked, setting a needed QSL's QSL Rcvd field to 'Y' will display a dialog box reminding you to submit the QSL to the DXCC desk |
|
| Partial DXCC Credit |
when checked, a QSO's QSL
Rcvd item can also be set to E,
B, or M:
(use these settings for QSL cards submitted to the DXCC desk before its records were computerized, where a card's Entity-Band and/or Entity-Mode was not recorded) |
| Include radio name in QTH ID | when checked, the default QTH ID is assembled by appending the Radio Name specified for the currently-selected transceiver in Commander to the specified root QTH ID |
| DXCC account # | specifies the DXCC account from the ARRL's DXCC Entity, Entity-Band, and Entity-Mode verification data is downloaded in order to report any discrepancies with the current log's DXCC Entity, Entity-Band, and Entity-Mode verification data. |
| root QTH ID | text to which the currently-selected transceiver's Radio name is appended to assemble a default QTH ID (only visible if the Include radio name in QTH ID option is enabled) |
|
identifies the operator's current QTH
|
| Auxiliary fields checkbox |
Checking this box shows the Log's Aux panel, which contains textboxes for each of the following fields:
Depressing the CTRL key while checking this box will display the Log's Aux panel and decrease the number of visible Log Page Display entries rather than expand the Main window's height. Unchecking this box will hide the Log's Aux panel and vertically shrink the Main window; depressing the CTRL key while unchecking this box will hide the Log's Aux panel and increase the number of visible Log Page Display entries. |
| QSL fields checkbox |
Checking this box shows the Log's QSL panel, which contains textboxes for each of the following fields: Depressing the CTRL key while checking this box will display the Log's QSL panel and decrease the number of visible Log Page Display entries rather than expand the Main window's height. Unchecking this box will hide the Log's QSL panel and vertically shrink the Main window; depressing the CTRL key while unchecking this box will hide the Log's QSL panel and increase the number of visible Log Page Display entries. |
| Online QSL fields checkbox |
Checking this
box shows the Log's Online QSL panel, which contains textboxes for each of the
following fields:
Depressing the CTRL key while checking this box will display the Online Log's QSL panel and decrease the number of visible Log Page Display entries rather than expand the Main window's height. Unchecking this box will hide the Log's Online QSL panel and vertically shrink the Main window; depressing the CTRL key while unchecking this box will hide the Log's Online QSL panel and increase the number of visible Log Page Display entries.
|
| Award fields checkbox |
Checking this box shows the Log's Awards panel, which contains textboxes for each of the following fields:
Depressing the CTRL key while checking this box will display the Log's Awards panel and decrease the number of visible Log Page Display entries rather than expand the Main window's height. Unchecking this box will hide the Log's Awards panel and vertically shrink the Main window; depressing the CTRL key while unchecking this box will hide the Log's Awards panel and increase the number of visible Log Page Display entries. |
| Contest fields checkbox |
Checking this box shows the Log's Contest panel, which contains textboxes for each of the following fields: Depressing the CTRL key while checking this box will display the Log's Contest panel and decrease the number of visible Log Page Display entries rather than expand the Main window's height. Unchecking this box will hide the Log's Contest panel and vertically shrink the Main window; depressing the CTRL key while unchecking this box will hide the Log's Contest panel and increase the number of visible Log Page Display entries. |
| Propagation fields checkbox |
Checking this box shows the Log's Propagation panel, which contains textboxes for each of the following fields:
Depressing the CTRL key while checking this box will display the Log's Propagation panel and decrease the number of visible Log Page Display entries rather than expand the Main window's height. Unchecking this box will hide the Log's Propagation panel and vertically shrink the Main window; depressing the CTRL key while unchecking this box will hide the Log's Propagation panel and increase the number of visible Log Page Display entries. |
| Details fields checkbox |
Checking this
box shows the Log's Details panel, which contains textboxes for each of
the following fields:
Depressing the CTRL key while checking this box will display the Log's Details panel and decrease the number of visible Log Page Display entries rather than expand the Main window's height. Unchecking this box will hide the Log's Details panel and vertically shrink the Main window; depressing the CTRL key while unchecking this box will hide the Log's Details panel and increase the number of visible Log Page Display entries. |
| User-defined fields checkbox |
Checking this
box shows the Log's User-definedn panel, which lets you specify up to
eight user-defined fields.
Depressing the CTRL key while checking this box will display the Log's User-defined panel and decrease the number of visible Log Page Display entries rather than expand the Main window's height. Unchecking this box will hide the Log's User-defined panel and vertically shrink the Main window; depressing the CTRL key while unchecking this box will hide the Log's User-defined panel and increase the number of visible Log Page Display entries. |
| Font Button |
Enables you to specify the font and font metrics (size, bold, italic) used in the Main window's Auxiliary, QSL, Online QSL, Awards, Contest and Satellite panels, and the Capture window. If a bold font is selected, then information in the Award Progress and Progress Details grids will also be rendered in bold font. |
| Log page fields control |
This control enables you to specify
To add a field to the Log Page Display,
To see the newly added field, you may need to horizontally scroll the log page display or widen your DXKeeper window. The order in which fields appear in the log page display, and the width of each column in the log page display are controlled by direct manipulation. To remove a field from the log page display,
|
| Font Button |
Enables you to specify the font and font metrics (size, bold, italic) used in the log page display |
| Reset button | Set's the Log Page Display row height and column widths to default values based on the current font size |
| Log Page Display layout file |
the pathname of a file whose contents specify a Log
Page Display layout:
|
| Select | displays a file selector that lets you choose a Log Page Display layout file and then format the Log Page Display as specified by the selected file's contents |
| Save | displays a file selector that lets you choose a file into which will be saved the Log Page Display's current layout |
| Frequency precision | specifies the number of decimal digits shown in transmit frequencies and receive frequencies appearing in the Log Page Display and in Log Reports; the valid range is 3 to 6. |
| Automatically update layout file | when checked, the specified Log Page Display layout file will automatically be updated to reflect changes made to the Log Page Display layout |
The Automatically recompute realtime award tracking checkbox determines whether DXKeeper will automatically update realtime award tracking information when you delete a QSO or indicate a regression in the QSO's progress, e.g. demoting its status from confirmed to worked, or from worked to unworked. If this box is unchecked, DXKeeper will not direct SpotCollector to initiate progress recomputations.
The Deduce CQ and ITU zones from US callsigns checkbox determines whether callsigns of US stations will be used to deduce CQ and ITU zones if more precise information (previous QSOs, state, ARRL section, Callbook) is unavailable and the call area fits entirely in the zone.
The Include LotW confirmations in VUCC, & Maidenhead progress box will, when checked, include QSOs confirmed by the ARRL's Logbook of the World (LotW) in the VUCC Progress, VUCC Submission, Maidenhead Field, and Maidenhead Gridsquare reports.
The Include eQSL.cc confirmations in DXCC, WAS, WAC, & Maidenhead Grid progress box will, when checked, will include QSOs confirmed by eQSL.cc in the the DXCC, Challenge, TOPLIST, WAS, WAC, and Maidenhead Gridsquare awards progress and reports. The ARRL, and TOPLIST do not accept eQSL.cc confirmations for their awards, but if your personal DXing program considers eQSL.cc confirmations to be valid, then checking this box will generate correct status. If you change this setting, immediately running the By QSL Mode, WAS, WAC, and Maidenhead Gridsquare reports will produce correct results. However, the Progress Grid, Progress Details Grid, and all other reports will not reflect the change until you invoke the Recompute function.
Checkboxes in the DXCC/Top Bands & Modes Panel specify the bands and modes you are pursuing for the ARRL DX Century Club award (DXCC), the ARRL DX Century Club Challenge award , and/or the Top List award. When you click the QSL tab's Add Needed button, these settings are used to identify QSOs for which QSLs would advance your progress. When you prepare a DXCC Submission, confirmed QSL cards and/or LotW credits will only be submitted for bands and modes selected in this panel. If SpotCollector is running, the settings of these checkboxes are used to determine whether a QSO with a spotted station would advance your progress. If no awards tab boxes are checked, DXKeeper and SpotCollector assume that you are pursuing DXCC without focus on specific bands or modes.
| Award Program | boxes to check in DXKeeper's DXCC/Top Bands & Modes panel |
| DXCC | none |
| 5-band DXCC | 80m, 40m, 20m, 15m, 10m |
| DXCC Challenge | 160m, 80m, 40m, 30m, 20m, 17m, 15m, 12m, 10m, 6m, Phone, CW, RTTY |
| TopList | 160m, 80m, 40m, 30m, 20m, 17m, 15m, 12m, 10m, Phone, CW, RTTY |
Checkboxes in the WAZ Bands & Modes Panel specify the bands and modes you are pursuing for awards in the CQ Worked All Zones (WAZ) family. The contents of a WAZ Progress Report are controlled by these settings. The Realtime Award Progress checkbox indicates whether realtime award tracking for the WAZ award family is enabled; if unchecked, checking this box directs DXKeeper to enable realtime award tracking for WAZ in the current log. When enabled,
clicking the QSL tab's Add Needed button identifies QSOs for which QSLs would advance your WAZ progress.
If SpotCollector is
running, the settings of this panel's band and mode checkboxes are used to determine whether a QSO
with a spotted station would advance your WAZ progress. If no awards
tab boxes are checked, DXKeeper and SpotCollector assume that you are pursuing
mixed WAZ without focus on specific bands or modes.
Checkboxes in the WPX Bands & Modes Panel specify the bands and modes you are pursuing for awards in the CQ Worked All Prefixes (WPX) family. If this panel's Mixed box is checked,
invoking a CQ WPX progress report with Add Unconfirmed enabled populates the QSL Queue with QSOs needed to confirm
unconfirmed WPX prefixes
unconfirmed WPX prefix-bands for which this panel's band boxes are checked
unconfirmed WPX prefix-modes for which this panel's mode boxes are checked
the Recompute operation computes a WPX prefix for logged QSOs that don't specify one
the Import operation computes a WPX prefix for imported QSOs that don't specify one
when logging a QSOs from another application (e.g. WinWarbler or MultiPSK), a WPX prefix will be computed if when one is not supplied
Unchecking this panel's Mixed box will uncheck all of the panel's band and mode boxes. Clicking this panel's HF button will check the 160m through 10m band boxes.
The Marathon panel lets you specify
In the Other Panel,
when the Subdivisions box is checked
the validity of Primary and Secondary Administrative Subdivisions is recorded with each QSO
the Broke filter displays QSOs with invalid primary or secondary administrative subdivisions
when importing QSOs from a file, logging QSOs from another application (e.g. WinWarbler or MultiPSK), or synchronizing LotW QSLs, corrects common misspellings of Primary and Secondary Administrative Subdivisions
when the CQ, DARC WAE, Holyland box is checked, DXKeeper enables the ? buttons to the right of the region boxes on the Capture window and on the Main window's Log QSOs tab; these ? buttons display an Award Selector window that lets you select a region by its full name
when the DARC DOK box is checked, DXKeeper enables the ? buttons to the right of the DOK boxes on the Capture window and on the Main window's Log QSOs tab; these ? buttons display an Award Selector window that lets you select a DOK by its full name
the IOTA checkbox determines whether generating an IOTA progress report will also create IOTA_Worked and IOTA_Confirmed update files for IOTAMem4WIN in DXKeeper's Reports sub-folder
The QSL Aging panel's Expiration
age textbox lets you specify a time interval in weeks that the Card
Aging function can use to automatically flag QSOs as expired,
meaning that a confirmation is no longer expected.
The DXCC Submission panel lets you specify
whether QSL cards should be submitted as proof of confirmed QSOs
whether LotW credits should be submitted as proof of confirmed QSOs
if an unverified QSO is confirmed by both QSL card and LotW credit, which should be submitted
whether QSOs that confirm deleted DXCC entities should be submitted
the
number of lines to be printed on each page of the generated Card
Record Sheet and LotW
Record Sheet reports
The Date Format panel lets you specify the format of dates used in reports, and in the headers of exported ADIF files.
dd-mmm-yyyy (local month abbreviations) uses the standard month abbreviations for your PC's locale
dd-mmm-yyyy (English month abbreviations) uses the English month abbreviations independent of your PC's locale
yyyy-mm-dd (ISO 8601) uses the ISO 8601 standard date format independent of your PC's locale
The Frequency precision setting specifies the number of decimal digits shown in frequencies appearing in progress reports; the valid range is 3 to 6.
The DXCC Summary panel's Optional HTML textbox lets you insert HTML at the beginning of the DXCC Summary's body, prior to the data table.
DXKeeper can obtain name, address, and location information from multiple sources:
the Flying Horse Radio Amateur's Callbook installed on your PC
the HamCall callbook installed on your PC
HamCall.net (requires a subscription)
the QRZ Callsign Database installed on your PC
Use this tab's radio buttons to specify which source of information is used for Callbook Lookup operations:
| None |
no callbook lookup is performed |
| RAC (PC) | use the RAC callbook installed on your PC; specify the pathname of the folder containing the RAC's Callbook.exe file |
| HamCall (PC) | use the HamCall callbook installed on your PC; specify the pathname of the folder containing the HamCall database |
| HamCall Online | use your subscription to HamCall.net; specify the callsign and password registered with HamCall.net, and set the HamCall Online timeout to indicate how long to wait before abandoning a request made to HamCall |
| QRZ (PC) |
use the QRZ callbook installed on your PC; specify
the pathname of the folder
containing the QRZ database callbkc.dat
file
If you use QRZ's default installation location, the correct pathname will be C:\Program Files\QRZ Ham Radio\CALLBK |
| QRZ.com | use your subscription to QRZ.com; specify the callsign and password registered with QRZ.com, and set the QRZ.com timeout to indicate how long to wait before abandoning a request made to QRZ.com |
| QRZ.com via Pathfinder | use Pathfinder to obtain information from QRZ.com; make sure Pathfinder (version 4.2.6 or later) is running, and set the QRZ.com timeout to indicate how long to wait before abandoning a request made to QRZ.com |
Use this tab's checkboxes to govern callbook behavior:
| Automatically use callbook data... checkbox |
if checked
|
| Warn when Callsign Lookups fail | When checked, a Callsign lookup that fails to locate Callbook information for the Call will display a warning message requiring confirmation |
From the Capture window, you can add name, QTH information, and address information from the selected Callbook to the current QSO by clicking the Lookup button, as described above.
Using the CBA button on the Main window's Log QSOs tab, you can update or replace name, QTH information, and address information in the current QSO or in all QSOs visible in the Log Page Display.
You can also configure
DXKeeper to lookup each imported QSO in the selected callbook and the DXCC database and fill in any items not present in the imported QSO with
information from these sources.
These settings govern DXKeeper's support for contest operation.
| Contest-mode |
when contest-mode is enabled,
Enabling Contest mode automatically enables Run-mode; disabling Contest-mode automatically disables Run-mode Contest-mode can also be enabled or disabled via the Capture window's contest-mode checkbox. |
| Increment TX serial# | when checked, increments the TX serial# after each QSO (if the Contest-mode box is checked, and if the TX serial# contains a numeric value) |
| Place focus in RX# on DX spot activation |
when checked, activating a DX spot in SpotCollector,
DXView
or Commander
will place the mouse cursor in the Capture window's RX#
item if the Capture window has not been closed
if the Capture window is closed, Optimize for realtime QSO entry is checked, and New QSO on DX Spot activation is checked, then activating a DX spot will create a new QSO and display it in the Main window; if the Contest panel on the Main window's Log QSOs tab is visible, then the mouse cursor will be placed in its RX# item |
| Don't log Capture window Contest, TX#, RX# if contest mode disabled | when checked with contest mode disabled, don't log the Capture window's Contest, TX#, and RX# items |
| Contest ID |
the Contest Identifier recorded with each QSO, and used to select the Cabrillo template used when generating a Cabrillo log |
| TX serial# |
the transmit serial number or exchange to be recorded with the next QSO |
| TX Exchange | fixed portion of transmit exchange (see the table describing how Contest information is recorded to enable Cabrillo generation) |
This panel determines what information is placed in the header section of a generated Cabrillo file; some of this information is also incorporated in recorded contest exchanges, as noted in the table below. If no value for an item is specified, then its Cabrillo tag will not appear in the header section.
| Item | Cabrillo Tag | Description |
| Contest | CONTEST | the name of the contest (initialized when you select a Contest ID) |
| Name | NAME | submitter's full name |
| Address | ADDRESS | up to 4 lines of postal address (do not include your name) |
| Operators | OPERATORS | callsigns of participating operators, separated by commas |
| Soapbox | SOAPBOX | Cabrillo Soapbox |
| Operator's first name | your first name (used in contest exchanges) | |
| Club | CLUB | name of your contest or radio club |
| Score | CLAIMED-SCORE | your claimed score in the contest (obtained from your contesting application, or manually computed) |
| Category | CATEGORY | Cabrillo category |
| Category Assisted | CATEGORY-ASSISTED | Cabrillo assistance category |
| Category Operator | CATEGORY-OPERATOR | Cabrillo operator category |
| Category Station | CATEGORY-STATION | Cabrillo station category |
| Category Band | CATEGORY-BAND | Cabrillo band category |
| Category Mode | CATEGORY-MODE | Cabrillo mode category |
| Category Power | CATEGORY-POWER | Cabrillo power category |
| Category Overlay | CATEGORY-OVERLAY | Cabrillo overlay category |
| Category Transmitter | CATEGORY-TRANSMITTER | Cabrillo transmitter category |
| Category Time | CATEGORY-TIME | Cabrillo time category |
| Location Section | LOCATION | the ARRL section from which you are operating |
| Location ST/PR | LOCATION | two-letter abbreviation for the US State or Province from which you are operating operating (for use in contest exchanges) |
| Location IOTA | LOCATION | Islands on the Air tag or Island Name from which you are operating (for use in contest exchanges) |
| Location Grid | LOCATION | Maidenhead Grid Square from which you are operating (for use in contest exchanges) |
| Location CQ | LOCATION | CQ Zone from which you are operating (for use in contest exchanges) |
| Location RDA # | LOCATION | RDA number from which you are operating (for use in RDXC contest exchanges) |
DXKeeper can record up to 8 user-defined items with each QSO. This tab lets you specify a caption, style, alignment, and default value for each user-defined item.
| Caption | specifies the caption that appears to the left of the item in the User-defined panel on the Main window's Log QSOs tab, in the Capture window, and in WinWarbler's QSO Info panel | ||||||||||||||||||||||||
| Style |
specifies the type of information captured in the
item:
|
||||||||||||||||||||||||
| Align |
specifies whether values are displayed as Left-aligned,
Centered, or Right-aligned
|
||||||||||||||||||||||||
| Init | If checked and the Display Previous QSOs on Lookup box is checked, then new QSOs with be initialized with information extracted from previous QSOs with the same callsign | ||||||||||||||||||||||||
| Default | specifies an optional default value for use in initializing a new QSO in the Capture window, in the Main window's Log QSOs tab, and in WinWarbler's QSO Info panel |
The List style is appropriate when a user-defined item's value is limited to a small discrete set, for example the set {Y, N}, or the set {Alinco, Elecraft, FlexRadio, Icom, Kachina, Kenwood, TenTec, Yaesu}. A text file specifying the latter set would contain 8 lines:
Alinco
Elecraft
FlexRadio
Icom
Kachina
Kenwood
TenTec
Yaesu
Its is usually appropriate to offer a choice representing "not specified"; this can be accomplished by having the first line of the specifying file be blank. When exporting a QSO, any of its user-defined items whose value is "not specified" are not included.
| Station callsign |
the station callsign used over the air (label is highlighted in red if maximum length is exceeded)
|
| Operator callsign |
the callsign of the operator of the station (label is highlighted in red if maximum
length is exceeded)
|
| Owner callsign |
the callsign of the owner of
the station (label is highlighted in red if maximum
length is exceeded)
|
| QTH latitude |
the QTH latitude used to compute QSO distance
and azimuth if no myQTH
is specified, or if the specified myQTH does not include a grid
square or latitude and longitude
|
| QTH longitude |
the QTH longitude used to compute QSO distance
and azimuth if no myQTH
is specified, or if the specified myQTH does not include a grid
square or latitude and longitude
|
| Transmit power |
transmitter power, in watts (label is highlighted in red if maximum length is exceeded); if Default Transmit power by band is disabled, or if Default Transmit power by band is enabled by the QSO frequency is not within a recognized band,
|
| RST sent & rcvd |
if enabled,
the specified default value is used to initialize the
RST
sent and RST
rcvd items in the Capture window or in the
Main window's Log QSOs tab. If the default value includes a slash, e.g.
59/599, characters before the slash are used with phone modes, and
characters after the slash are used with non-phone modes.
if enabled with no default value specified, the RST send and RST rcvd items in the Capture window or in the Main window's Log QSOs tab are initialized to 59 for phone modes and 599 for non-phone modes. |
| QSL msg |
selects message to be printed on each QSL card from among the standard messages defined in the QSL Msgs tab
if a message is selected, you can modify it by editing the displayed text |
| Antenna Path |
|
| Propagation mode |
|
| SFI |
|
| A |
|
| K |
|
| Satellite name |
|
| Satellite mode |
|
| Meteor shower |
|
| Default Transmit power by band panel |
specifies the default transmitter power, in watts,
for the amateur bands from 160m through 23cm; if enabled and the
QSO frequency lies within one of the bands for which a default is
specified,
|
| Network Service panel | lets you specify the Base Port for TCP/IP service, set the Base Port to its default value, and restart the TCP/IP server |
DXKeeper is driven by a set of band definitions contained in a file. Any attempt to log a QSO on a frequency not falling within a defined band will be flagged.
At startup, DXKeeper checks its Databases folder for the file Bands.txt ; if found, the contents of this file are interpreted as user-defined band specifications in the format shown below. If Bands.txt is not found, then DXKeeper checks its Databases folder for the file DefaultBands.txt, which every DXKeeper release installs. DefaultBands.txt, is a file containing one line per band::
2190M, 0.136,0.137
160M, 1.800, 2.000
80M, 3.500,4.000
60M, 5.3305,5.405
40M, 7.000,7.350
30M, 10.100, 10.150
20M, 14.000, 14.350
17M, 18.068, 18.168
15M, 21.000, 21.450
12M, 24.890, 24.990
10M, 28.000, 29.900
6M, 50.000, 54.000
4M, 70.0, 71.0
2M, 144.000, 148.000
1.25M,222.0,225.0
70CM, 420.0, 450.0
33CM, 902.0, 928.0
23CM, 1240, 1300
13CM,2400,2450
9CM, 3300, 3500
6CM, 5650, 5925
3CM, 10000, 10500
1.25cm,24000,24250
6MM, 47000, 47200
4MM, 75500, 81000
2.5MM, 119980,120020
2MM, 142000, 149000
1MM, 241000,250000
SUBMM, 300000,1000000
Each line contains three parameters, separated by commas: the band name, the band's lower edge in megahertz, and the band's upper edge in megahertz. The band name cannot exceed its defined maximum length.
To add or subtract bands, make a copy of DefaultBands.txt in DXKeeper's Databases folder and name it Bands.txt. Delete or add lines as required, ensuring that
each band's lower band edge is less than its upper band edge
the upper band edge defined on one line is less than the lower band edge defined on the next line
DXKeeper provides built-in support for six modes: SSB, CW, RTTY, AM, FM, and PSK31. At startup, DXKeeper checks its Databases folder for the file Modes.txt ; if found, the contents of this file are interpreted as user-defined mode specifications, as described below. If Modes.txt is not found, then DXKeeper checks its Databases folder for the file DefaultModes.txt and if found interprets its contents as user-defined mode specifications. Every DXKeeper release installs a DefaultModes.txt file that contains the following mode specifications:
| Mode Name | DXCC Phone credit | DXCC CW credit | DXCC RTTY credit | WAZ RTTY credit | WAZ Digital credit | WPX SSB credit | WPX CW credit | WPX Digital credit | PSK credit |
| AMTORFEC | a | a | a | ||||||
| ASCI | a | a | a | ||||||
| ATV | |||||||||
| CHIP64 | a | a | a | ||||||
| CHIP128 | a | a | a | ||||||
| CLO | a | a | a | ||||||
| CONTESTI | a | a | a | ||||||
| DOMINO | a | a | a | ||||||
| DOMINOF | a | a | a | ||||||
| DSTAR | |||||||||
| FAX | |||||||||
| FMHELL | a | a | a | ||||||
| FSK31 | |||||||||
| FSK441 | a | a | a | ||||||
| GTOR | a | a | a | ||||||
| HELL | a | a | a | ||||||
| HELL80 | a | a | a | ||||||
| HFSK | |||||||||
| JT44 | a | a | a | ||||||
| JT4A | a | a | a | ||||||
| JT4B | a | a | a | ||||||
| JT4C | a | a | a | ||||||
| JT4D | a | a | a | ||||||
| JT4E | a | a | a | ||||||
| JT4F | a | a | a | ||||||
| JT4G | a | a | a | ||||||
| JT65 | a | a | a | ||||||
| JT65A | a | a | a | ||||||
| JT65B | a | a | a | ||||||
| JT65C | a | a | a | ||||||
| MFSK8 | a | a | a | ||||||
| MFSK16 | a | a | a | ||||||
| MT63 | a | a | a | ||||||
| OLIVIA | a | a | a | ||||||
| PAC | a | a | a | ||||||
| PAC2 | a | a | a | ||||||
| PAC3 | a | a | a | ||||||
| PAX | a | a | a | ||||||
| PAX2 | a | a | a | ||||||
| PKT | a | a | a | ||||||
| PSK10 | a | a | a | a | |||||
| PSK63 | a | a | a | a | |||||
| PSK63F | a | a | a | a | |||||
| PSK125 | a | a | a | a | |||||
| PSK220F | a | a | a | a | |||||
| PSKAM10 | |||||||||
| PSKAM31 | |||||||||
| PSKAM50 | |||||||||
| PSKFEC31 | a | a | a | a | |||||
| PSKHELL | |||||||||
| Q15 | |||||||||
| QPSK31 | a | a | a | a | |||||
| QPSK63 | a | a | a | a | |||||
| QPSK125 | a | a | a | a | |||||
| ROS | a | a | a | ||||||
| RTTYM | a | a | a | ||||||
| SSTV | a | ||||||||
| THRB | a | a | a | ||||||
| THRBX | a | a | a | ||||||
| TOR | a | a | a | ||||||
| VOI | |||||||||
| WINMOR | a | a | a | ||||||
| WSPR | a | a | a |
Users wishing to define additional modes or remove modes that aren't built-in can do so by creating the file Modes.txt in SpotCollector's Databases folder. The specification format used in DefaultModes.txt and Modes.txt is identical: each line of the file specifies a mode's name, followed optionally by a list of awards for which QSOs in the mode produce credit; the mode name and optional awards are separated by commas. The mode name cannot exceed its defined maximum length. Valid award designators are shown in the following table:
| Award Designator | Meaning |
| DXCC_Phone | QSOs in this mode "count" for DXCC Phone credit |
| DXCC_CW | QSOs in this mode "count" for DXCC CW credit |
| DXCC_RTTY | QSOs in this mode "count" for DXCC RTTY credit |
| WAZ_RTTY | QSOs in this mode "count" for WAZ RTTY credit |
| WAZ_DIGITAL | QSOs in this mode "count" for WAZ Digital credit |
| WPX_Phone | QSOs in this mode "count" for WPX Phone credit |
| WPX_CW | QSOs in this mode "count" for WPX CW credit |
| WPX_Digital | QSOs in this mode "count" for WPX Digital credit |
| PSK | QSOs in this mode "count" for PSK credit |
Thus, the first line of the file DefaultModes.txt, which is
ASCI, DXCC_RTTY, WAZ_RTTY
defines the new mode ASCI, and specifies that QSOs in ASCI should be credited as DXCC RTTY and WAZ RTTY QSOs.
The easiest way to create a custom Modes.txt file is by starting with a copy of DefaultModes.txt and editing as required. Be sure to make your changes in Modes.txt as DefaultModes.txt will be overwritten by the next DXKeeper release.