The Main window's Export QSOs tab enables you to export QSOs to a file
in standard ADIF format
in the ancient ADIF 1.0 format
in ADIF targeted to the ARRL's Logbook of the World (LotW)
in ADIF that DXBase can import
in tab-delimited format
using the Cabrillo template specified for the currently selected contest.
If the Log Page Display is filtered, only QSO present in the Log Page Display are exported, making it easy to export a selected subset of QSOs in the current log file. If the Log Page Display is not filtered, then all QSOs in the log will be exported.
Check the export QTH definitions box to include the contents of a QTH definition in the ADIF record of each QSO containing a myQTH item. The QTH definition contents are exported with the following ADIF 2.0 tags:
MY_CITY
MY_CNTY
MY_COUNTRY
MY_CQZONE
MY_GRIDSQUARE
MY_IOTA
MY_ITUZONE
MY_LAT
MY_LON
MY_POSTAL_CODE
MY_STATE
MY_STREET
QSOs whose callsigns begin with an exclamation point are only exported if the Export callsigns with leading ! box is checked; such callsigns will not be exported if either the Export ADIF for LOTW, Export ADIF for eQSL.cc, or Export Cabrillo radio buttons are checked, even if the Export callsigns with leading ! box is checked.
To export QSOs, first make the appropriate selections in the Options panel:
if you are exporting a file in standard ADIF, check the Export standard ADIF button
if you are exporting a file in ADIF 1.0 format, check the Export ADIF 1.0 button; in this format
only tags specified in ADIF 1.0 are exported: ADDRESS, BAND, CALL, CNTY, COMMENT, CONT, CONTEST_ID, CQZ, DXCC, FREQ, GRIDSQUARE, IOTA, ITUZ, MODE, NAME, OPERATOR, PFX, QSL_RCVD, QSL_SENT, QSL_VIA, QSLMSG, QSLRDATE, QSLSDATE, QSO_DATE, QTH, RST_RCVD, RST_SENT, SAT_MODE, SAT_NAME, SRX, STATE, STX, TIME_OFF, TIME_ON, TX_PWR, VE_PROV
the STATE tag is only used for US states, including Alaska and Hawaii
the CNTY tag is only used for US counties, including Alaska and Hawaii
the VE_PROV tag is used for Canadian provinces (this is deprecated in ADIF 2.X)
if you are exporting a file to be uploaded to LotW, check the Export ADIF for LOTW radio button to export modes accepted by LotW and update each QSO's status as described below
if you are exporting a file to be uploaded to eQSL.cc, check the Export ADIF for eQSL.cc radio button to export modes accepted by eQSL.cc and update each QSO's status as described below
if you are exporting a file to be imported by DXBase, check the Export ADIF For DXBase radio button to use its two-decimal-point representation of frequencies
if you are generating QSLs with another application using mail merge techniques, check the Export tab-delimited file radio button to export QSO information in tab-delimited format
if you are exporting a Cabrillo file, check the Export Cabrillo radio button; note that the Export Cabrillo radio button will be disabled unless you've selected a Contest ID for which DXKeeper can generate Cabrillo
to insert text into the header of the exported ADIF file, enter this text into the Insert in ADIF Header textbox
to append text to the QSO notes item of each exported QSO, enter this text in the Append to QSO Notes textbox
Click the Start button, and use the file selector to choose the file to which QSOs will be exported. The Progress panel provides real-time statistics of the operation. Click the Abort button to terminate the export operation before it completes.
If you export a Cabrillo file, DXKeeper will display the file in Notepad after the operation is complete so that you can complete the necessary descriptor fields and delete any unnecessary descriptor fields.
The format of the date placed in exported ADIF file
headers is governed by the Date
Format sub-panel on the Config window's Awards tab.
Each QSO submitted to LotW must include a Callsign, Band, Mode, Begin date and time, and Propagation mode. If the propagation mode is SAT, then Satellite Name and Satellite Mode are also required.
Exporting ADIF to LotW translates modes unsupported by LotW as shown in the following table:
| QSO Mode in log | Exported QSO Mode |
| ASCI | DATA |
Each exported QSO will be updated to reflect the correct status:
the QSO's LotW Sent will be set to U, reflecting the fact that these QSOs have been uploaded, but their acceptance by LotW is unknown.
the QSO's LotW Date Sent will be set to the current UTC date
the QSO's LotW Rcvd will be set to R
Invoke TQSL
and direct it to encrypt and sign the file you just exported; the resulting file
will have a file extension of .tq8. You can submit this .tq8 file to LotW
by emailing it to lotw-logs@arrl.org, or
by logging on to your LotW web
page and uploading the file from there. You can then proceed with the LotW
QSL workflow by click the Sync LotW QSOs
button.
If Use each QSO's myQTHID as its QTH Nickname when uploading or exporting is enabled, each QSO will be exported with an eQSL.cc Nickname whose value is taken from the QSO's myQTHID. If Use each QSO's myQTHID as its QTH Nickname when uploading or exporting is not enabled and a QTH Nickname is specified, DXKeeper will ask if it should be included with each exported QSO.
Each exported QSO will be updated to reflect its status:
the QSO's eQSL Sent will be set to U
the QSO's eQSL Date Sent will be set to the current UTC date
the QSO's eQSL Rcvd will be set to R
After logging into eQSL.cc,
upload the file you just exported. Since eQSL.cc
does not presently provide a means of verifying that a QSO has been successfully
uploaded, you must inspect the upload report and manually clear the eQSL
Sent, eQSL
Date Sent, and eQSL
Rcvd fields for each QSO that was rejected. Then click the Update
eQSL Sent button to change eQSL
Sent from U to Y for all QSOs in your log; note that the Update
eQSL Sent button is only enabled when the Options panel is set to Export
ADIF for eQSL.cc.
If the on the the Export header in tab-delimited files box is checked on the Main window's Export QSOs tab, the first record in the generated file will specify a caption for each of the above items. This is required if you plan to later import the file.
For each exported QSO, the following information will be stored in the following order: