Club Log introduced its Online QSL Request Service  (OQRS), which enables DXers to request confirmation of a QSO uploaded to Club Log without mailing an outgoing QSL accompanied by a self-addressed stamped envelope and funds for return postage. Unless you're located in a rare DXCC Entity, CQ Zone, or administrative subdivision, QSL Managers for DXPeditions and rare DX stations are not interested in your QSL card; having to open thousands of incoming envelopes bearing small bills and self-addressed envelopes can consume large amounts of QSL Manager time. OQRS eliminates this overhead by enabling a DXer to electronically convey a request for confirmation to the QSL Manager; the DXer can optionally include funds (using PayPal) for postage and a return envelope for QSL card delivery via direct mail, or the DXer can instead request that the QSL card be delivered at no cost via the QSL buro.

After this operation completes, DXKeeper will display an eQSL.cc Upload Report in a browser window; any QSLs rejected by eQSL.cc will be noted in this window. The current UTC date and time will appear under the Upload to eQSL.cc button to remind you when you last invoked this function; this information is stored in the current log. You can now disconnect from the Internet.

For each successfully uploaded QSL Queue entry, DXKeeper will perform the following for each enabled entry in the QSL Queue: 

• set the associated logged QSO's eQSL sent to Y

• set the associated logged QSO's eQSL date sent to the current UTC date

• set the associated logged QSO's eQSL rcvd to R

• remove the entry from the QSL Queue

QSLs that were disabled or not successfully uploaded will remain in the QSL Queue after the Upload to eQSL.cc operation. If incorrect logged data other than callsign or begin time is at fault, double-clicking on the  QSL Queue entry to display its associated QSO in the Main window, where you can correct the error and click the Log button. If an incorrect callsign or begin time was logged,

• empty the QSL Queue by clicking the QSL tab's Clear  button

• correct the logged data

• repeat the Add Requested operations you originally used to load the QSL Queue

• reconnect to the Internet and repeat the Upload to eQSL.cc operation

If you need to convey more than a few hundred QSOs to eQSL.cc, using Export to eQSL.cc will likely be faster.

Uploading QSOs to eQSL.cc by Right-clicking a Log Page Display entry

Right-clicking a QSO's entry in the Log Page Display and selecting the Upload to eQSL.cc command from the pop-up menu immediately uploads that QSO to eQSL.cc; if a QTH Nickname nickname is specified, it will be conveyed with the uploaded QSO.

The Upload to eQSL.cc command will be disabled if the selected QSO begins with an exclamation point (!) and the Upload QSOs whose callsigns begin with ! box is unchecked.

Uploading QSOs to eQSL.cc when Logging via the Capture window

With the Upload each QSO logged via the Capture window to eQSL option enabled, logging a QSO via the Capture window immediately uploads that QSO to eQSL.cc; if a QTH Nickname nickname is specified, it will be conveyed with each uploaded QSO.

Synchronizing: Updating Logged QSOs to Reflect Confirmation via eQSL.cc

To synchronize your log with eQSL.cc by downloading QSLs and matching them with logged QSOs,

• if desired, specify an eQSL.cc QTH Nickname to limit the downloaded QSLs to those made from a specific QTH in your eQSL.cc profile

• verify that the setting that establishes the maximum time variance for a match is correct

• click the Sync eQSL.cc QSLs button on the Main window's QSL tab; DXKeeper will download the eQSL.cc Inbox for the specified username and update each confirmed QSO's eQSL rcvd  item.

Under certain circumstances, you may wish to manually download an eQSL.cc Inbox and use the Sync eQSL.cc QSLs function to process its contents; to do so, check the Prompt the user to specify a file containing the already-downloaded contents of an eQSL.cc Inbox box before invoking Sync eQSL.cc QSLs. To manually download an eQSL.cc Inbox, log in to eQSL.cc and then navigate to http://www.eqsl.cc/qslcard/DownloadInbox.cfm .

The Sync eQSL.cc QSLs function remembers the date and time at which the last QSL reported was uploaded to eQSL.cc;  this date and time is stored in the current log and shown beneath the Sync eQSL.cc QSLs button. When activated, this function directs  eQSL.cc to supply only newly-arrived QSLs, thereby minimizing the amount of information to be downloaded and inspected. You can modify this date and time by double-clicking it; you'll be prompted to specify a new date and time, which will default to the date and time before the most recent invocation of the Sync eQSL.cc QSLs function after starting DXKeeper. Alternatively, you can force all QSLs to be downloaded and inspected by depressing the CTRL key while clicking the Sync eQSL.cc QSLs button.

A logged QSO will be confirmed if it matches a downloaded QSL:

• the callsigns are identical

• the bands are identical

• the modes are identical

• the difference between start times must be less than the maximum time variance for a match setting

For each confirmed QSL,  DXKeeper will set the logged QSO's  eQSL rcvd to Y and its eQSL date rcvd to the current UTC date. Any errors encountered while inspecting the downloaded QSLs -- including QSLs that match no QSO in the current log  -- will be displayed in an error report. 

Each logged QSO's eQSL Member item indicates how the QSO's callsign participates in eQSL:

• N - not known to participate

• Y - known to participate

• A - known to participate, authenticity guaranteed

You can direct DXKeeper to update the eQSL Member item of each QSO in the Log Page Display.

When the Sync eQSL.cc QSLs function completes, DXKeeper displays a report showing

• any errors encountered while inspecting the downloaded QSLs; each is preceded by Error:

• any confirmations of desired (per your specified WAZ award objectives) but previously unconfirmed CQ zones, CQ zone-modes, or CQ zone-bands

If reports from Shortwave Listeners (SWLs) were received, a report containing them will be displayed.

After all logged QSOs have been updated, the Log Page Display is filtered to show only QSOs confirmed via eQSL.cc, and sorted in ascending or descending order of eQSL date rcvd ; the QSOs most recently confirmed  via eQSL.cc will thus appear at the bottom of the Log Page Display. The Filter and Sort panel's captions will indicate how the Log Page Display is being filtered and sorted respectively. Depressing the CTRL key while clicking the Filter panel's X button both resets the Log Page Display filter and sorts the Log Page Display in ascending or descending order of each QSO's Begin time.

If you modify the callsign, QSO begin, band, mode, or submode item of a logged QSO that has already been uploaded to eQSL, the Sync eQSL.cc QSLs function will be unable to locate the QSO in your log to update it; to correct this situation,

1.  right-click the Log Page Display entry for the QSO, and select Upload to eQSL.cc from the popup menu

2. wait a few minutes for eQSL.cc to process your submitted QSO

3. on the Main window's QSL tab,

   • set the QSL Via panel to eQSL.cc

   • click the Sync eQSL.cc QSLs button

To be prompted when you modify the callsign, QSO begin, band, mode, or submode item of a logged QSO that has already been uploaded to eQSL, enable the Prompt on change to logged QSO already uploaded to eQSL.cc and/or LoTW option.

If a QSO has been confirmed via eQSL.cc, you can display an image of the QSL by clicking the Display button in the eQSL.cc sub-panel on the Online QSL panel on the Main window's Log QSOs tab. If the Retain eQSL images option is enabled, then DXKeeper will save downloaded images in its eQSL Images  folder; when you click the Display button, DXKeeper will check for an already-downloaded image and display it if present, rather than download the image from eQSL.cc. Depressing the CTRL key while clicking the Display button directs DXKeeper to download a new image, replacing the already-downloaded image if one exists.

• eQSL.cc can be configured to provide QSL images in JPG or PNG format; DXKeeper will place the downloaded image in a file whose extension is .jpg or .png as a function of the URL provided by eQSL.cc.

• if Retain eQSL images is enabled, when you click the Display button, DXKeeper will check for an already-downloaded .jpg file and display its contents if present; if no .jpg issue is found, DXKeeper will check for an already-downloaded .png file and display its contents if present.

Clicking the b>Download Images button will  enable Retain eQSL images, and download QSL images for all QSOs in the Log Page Display that have been confirmed via eQSL.cc and for which no QSL image is present in DXKeeper's eQSL Images  folder. Depressing the CTRL key while clicking Download Images will download QSL images for all QSOs in the Log Page Display that have been confirmed via eQSL.cc whether or not a QSL image is already present in DXKeeper's eQSL Images  folder. At the request of  eQSL.cc management, images will be downloaded at the rate of 4 per minute; if there are more than 5 QSOs in the Log Page Display, DXKeeper will display the estimated time required and ask you to confirm before proceeding to download images.

QSLing via LoTW: uploading QSLs from the QSL Queue, verifying uploads, and synchronizing confirmed QSLs

When configured for use with LoTW and connected to the internet with TQSL version 2.0 or later installed, DXKeeper will on startup inform you if

• your Callsign Certificate will expire within the next 60 days, in which case you should Run TQSL and request a renewal

• a new Configuration Data file is available, in which case you should Run TQSL and initiate an update

• a new version of TQSL is available

Each QSO uploaded to LoTW must at minimum include a Callsign, Band, Mode, and Begin date and time; satellite QSOs must specify a Propagation mode of SAT, as well as a Satellite Name. The following information is uploaded:

• Callsign of the station worked
• UTC date at which the QSO began
• UTC time at which the QSO began
• QSO Mode  (mapped to modes accepted by LoTW)
• QSO Frequency
• QSO Band
• QSO receive frequency
• QSO receive band
• Satellite name
• Propagation mode

LoTW accepts only QSOs with specified modes; before uploading QSOs with a data mode not yet accepted by LoTW, configure TQSL to map this mode to DATA.

There are three ways to upload QSOs to LoTW:

1. Add QSOs to the QSL Queue, and then invoke the Upload to LoTW function.

2. Right-click an entry in the Log Page Display, and select the Upload to LoTW command

3. With the Upload each QSO logged via the Capture window to LoTW option enabled, log a QSO via the Capture window

Uploading QSOs to LoTW via the QSL Queue

Because QSOs submitted to LoTW QSOs must be digitally encrypted before transmission to the ARRL, it is more efficient wait until a batch of QSLs are needed before uploading them. Batches of outgoing QSLs can be automatically assembled in the QSL Queue. From there, they can be uploaded, and then used to update your log to indicate the operation's success. You can optionally enable automatic uploading of QSOs logged via the Capture window by checking the Upload each QSO logged via the Capture window to LoTW box. box. You can also upload a QSO to LoTW by right-clicking its entry in the Log Page Display and selecting the Upload to LoTW command.

To upload QSOs in the QSL Queue to LoTW, 

• disable any QSL Queue entries that you don't want uploaded

• confirm that the LoTW station location and station callsign shown beneath the Upload to LoTW button on the Main window's QSL tab are consistent with the geographic location from which you made each of the QSOs in the QSL queue, and the callsign that you used over the air when making those QSOs; if not, select the appropriate station location and station callsign in the TQSL panel on the QSL Configuration window's LoTW tab before proceeding.

• click the Upload to LoTW button on the Main window's QSL tab; if TQSL version 2.0 or later is installed, DXKeeper will create an ADIF file containing the enabled QSL Queue entries, invoke TQSL using the specified TQSL full pathname and TQSL station location, and direct TQSL do digitally sign (encrypt) your QSOs and upload them over the internet to LoTW.

  • if the callsign certificate associated with the selected LoTW station location is password-protected, TQSL's Enter password dialog box will appear; enter the password that unlocks the certificate's private key, and then click the OK button; to remove the password from a callsign certificate so that TQSL does not prompt you for a password each time you upload QSOs to LoTW, see Removing Password Protection from a Callsign Certificate.

  • DXKeeper's LoTW Upload dialog box will report progress as each QSO in the QSL Queue is processed

The Upload to LoTW function will not submit QSOs that would be rejected by LoTW or that are inconsistent with the selected LoTW station location; the QSL Queue entries of such QSOs will be disabled, and will remain in the QSL Queue at the completion of the Upload to LoTW operation:

• Any QSO whose Propagation Mode item is set to SAT but whose Satellite Name item is unspecified

• Any QSO that specifies a Satellite Name item but whose Propagation Mode item is not set to SAT

• Any QSO whose Station Callsign item is inconsistent with the Station Callsign specified in the selected LoTW station location

• Any QSO that references a myQTH that specifies an LoTW Station Location that doesn't match the selected LoTW station location

If the selected LoTW station location specifies a station callsign of [NONE], the Upload to LoTW operation will not upload any of the entries in the QSL Queue; it will disable every entry in the QSL Queue.

The UTC date and time shown immediately below the Upload to LoTW button indicate when you last uploaded QSOs to LoTW; this information is stored in the current log.

At the completion of the Upload to LoTW operation, DXKeeper will display

• a report listing any QSL Queue entries not submitted to LoTW with an explanation for this inaction.

• an LoTW Upload dialog box bearing the response from TQSL for those QSOs that were submitted to LoTW. If this response is not "all QSOs submitted were signed and uploaded", inspect the associated message to understand the problem, correct it, and invoke Upload to LoTW again.

DXKeeper will perform the following actions for each enabled entry in the QSL Queue that was successfully uploaded to LoTW: 

• set the associated logged QSO's LoTW sent to U, reflecting the fact that the QSO has been uploaded, but its individual acceptance by LoTW is unknown. 

• set the associated logged QSO's LoTW date sent to the current UTC date

• set the associated logged QSO's LoTW rcvd to R

• remove the entry from the QSL Queue

QSOs that were disabled or not successfully uploaded will remain in the QSL Queue after the Upload to LoTW operation. 

If you've configured DXKeeper to use TQSL version 1.14 or later, QSOs that have already been uploaded to LoTW and not subsequently changed (e.g. by correcting the band or by specifying a Gridsquare in your Station Location) will not be uploaded to LoTW, and will prevent any other QSOs in the QSL Queue from being uploaded. TQSL refers to such QSOs as duplicates, by which it means "QSOs already uploaded to LoTW".  If you have good reason to re-upload a QSO that's already been uploaded but not subsequently changed, enabled the Permit uploaded of QSOs already uploaded to LoTW option before initiating an upload.

Depressing the CTRL key while clicking the Upload to LoTW button will direct DXKeeper to invoke the Check LoTW Queue function after QSOs have been submitted to LoTW.

Uploading QSOs to LoTW by Right-clicking a Log Page Display entry

Right-clicking a QSO's entry in the Log Page Display and selecting the Upload to LoTW command from the pop-up menu immediately uploads that QSO to LoTW using the Station Location specified by the QSO's myQTH ID item; if the myQTH doesn't specify a Station Location, or if the QSO doesn't specify a myQTH ID item, then the QSO is uploaded using the LoTW station location and station callsign specified in the TQSL panel on the QSL Configuration window's LoTW tab.

The Upload to LoTW command will be disabled if the selected QSO begins with an exclamation point (!) and the Upload QSOs whose callsigns begin with ! box is unchecked.

Uploading QSOs to LoTW when Logging via the Capture window

With the Upload each QSO logged via the Capture window to LoTW option enabled, logging a QSO via the Capture window immediately uploads that QSO to LoTW using the Station Location specified by the QSO's myQTH ID item; if the myQTH doesn't specify a Station Location, or if the QSO doesn't specify a myQTH ID item, then the QSO is uploaded using the LoTW station location and station callsign specified in the TQSL panel on the QSL Configuration window's LoTW tab.

Synchronizing: Updating Logged QSOs to Reflect Their Acceptance and Confirmation by LoTW

LoTW places submitted QSOs in a Queue that is processed in "first-come, first-served" order, typically successfully within a few minutes unless a contest has recently been completed. The ARRL provides a web page that displays the approximate duration of the LoTW Queue as of the beginning of the current hour and each of the 11 previous hours. Clicking the Check LoTW Queue button will download this web page, extract the estimated queue duration for the current hour, and display it immediately beneath the Check LoTW Queue button for the remainder of the current hour; letting the mouse cursor hover over this estimated duration for a second or three will display an explanatory popup containing both the estimated duration and the time at which it was estimated. At the end of the current hour, the displayed duration estimate will be cleared. Depressing the CTRL key while clicking the Check LoTW Queue button will direct your default web browser to display the entire LoTW Queue Status web page.

After waiting an appropriate interval, verify that the uploaded QSLs were accepted by connecting to the Internet and clicking the Sync LoTW QSOs button. This will direct LoTW to download all newly-accepted QSOs, where newly-accepted is with respect to the last time you invoked Sync LoTW QSOs;  this date and time is stored in the current log and shown beneath the Sync LoTW QSOs button. Logged QSOs whose LoTW sent is set to U will have that status update to Y, reflecting acceptance by LoTW. The UTC date and time that the last uploaded QSO was accepted  will appear under the Sync LoTW QSOs button; this information is stored in the current log. 

QSOs not accepted by LoTW will remain in the log with their  LoTW sent set to U; you can filter the Log Page Display to show such QSOs by clicking the LoTW button in the Main window's Filter panel. 

If you find such QSOs, check your LoTW account to determine whether they've simply not yet been processed, or been processed and generated errors. After correcting any erroneous QSOs

• set each QSO's LoTW sent to R

• repeat the Add Requested operations you originally used to load the QSL Queue

• connect to the Internet and repeat the Upload to LoTW operation

• repeat the Sync LoTW QSOs operation

You can modify the date and time shown beneath the Sync LoTW QSOs button double-clicking it; you'll be prompted to specify a new date and time. The next invocation of Sync LoTW QSOs will then direct LoTW to download all QSOs newly-accepted after the date and time you specified.

If you depress the CTRL key while invoking the Sync LoTW QSOs operation, DXKeeper will direct LoTW to download all accepted QSOs, and the update logged QSOs to reflect their acceptance as described above. If you depress the ALT key while invoking the Sync LoTW QSOs operation, DXKeeper will set the Select item of each accepted QSO to 'Y'. This can be used to identify any QSOs in your log that are not shown as accepted by LoTW. The ALT and CTRL keys can be simultaneously depressed while invoking the Sync LoTW QSOs to check for acceptance of all QSOs.

LoTW marks an uploaded QSO as confirmed if your QSO partner also uploads his or her QSO information to LoTW, and

• the callsign in each uploaded QSO matches the station callsign of the other, including portable identifiers

• the modes in each upload QSO belong to the same Mode Group (CW, DATA, IMAGE, PHONE)

• the dates and times in each uploaded QSO are within 30 minutes of each other

• for terrestrial QSOs, each uploaded QSO's band and RX band must match the values of the other QSO (band = band, RX band = RX band), or must match the opposite values of the other QSO (band = RX band, RX band = band)

• for satellite QSOs, the propagation mode in each uploaded QSO must be SAT, and the satellite names must be identical

If more than one copy of a QSO reported by LoTW in response to the Sync LoTW QSOs operation is present in your log, each duplicate QSO's Select item will be set to Y.

To synchronize your log with LoTW  by downloading confirmations (QSLs) and matching them with logged QSOs, click the Sync LoTW QSLs button on the Main window's QSL tab.

The Sync LoTW QSLs function remembers the date and time at which the last QSL reported was uploaded to LoTW;  this date and time is stored in the current log and shown beneath the Sync LoTW QSLs button. When activated, Sync LoTW QSLs directs LoTW to supply only newly-arrived QSLs, thereby minimizing the amount of information to be downloaded and inspected. You can modify this date and time by double-clicking it; you'll be prompted to specify a new date and time, which will default to the date and time before the most recent invocation of the Sync LoTW QSLs function after starting DXKeeper. Alternatively, you can force all LoTW confirmations to be downloaded and inspected by depressing the CTRL key while clicking the Sync LoTW QSLs button.

A logged QSO will be marked as "confirmed via LoTW" if it matches a QSL downloaded from LoTW:

• the callsigns are identical

• the bands are identical

• the modes are identical

• the start times fall within the same minute

• the station callsigns are identical (this requirement can optionally be eliminated, as discussed below)

All QSLs reported by LoTW specify a DXCC entity; QSLs downloaded from LoTW may include additional information provided by the QSLing station:

• Continent

• CQ zone

• ITU zone

• IOTA tag

• Grid 1

• Grid 2

• Grid 3

• Grid 4

• State

• County

Each logged QSO that matches a QSL downloaded from LoTW will be updated to reflect its confirmation:

• the QSO's LoTW rcvd item will be set to Y

• the QSO's LoTW date rcvd item will be set to the current UTC date

• the QSO's LoTW cfm item will be set to indicate additional WAS, WAZ, VUCC, and NPOTA confirmations

  • an S in the LoTW cfm item means that the LoTW QSL specifies a valid US state that matches the US state specified in the logged QSO (required for WAS award credit)

  • an M in the LoTW cfm item means that the QSO's mode exactly matches the mode uploaded to LoTW by your QSO partner (required for CQ Worked All Zones( WAZ) awards, and some ARRL Worked All States  and CQ Worked All Prefixes Endorsements)

  • a D in the LoTW cfm item means that the QSO's mode and the mode uploaded to LoTW by your QSO partner don't exactly match, but are both considered to be digital modes for CQ Worked All Zones( WAZ

  • a G in the LoTW cfm item means that the LoTW QSL specifies a valid grid square that matches the grid 1 item specified in the logged QSO (required for VUCC award credit)

  • a 2 in the LoTW cfm item means that the LoTW QSL specifies a valid grid square that matches the grid 2 item specified in the logged QSO (required for VUCC award credit)

  • a 3 in the LoTW cfm item means that the LoTW QSL specifies a valid grid square that matches the grid 3 item specified in the logged QSO (required for VUCC award credit)

  • a 4 in the LoTW cfm item means that the LoTW QSL specifies a valid grid square that matches the grid 4 item specified in the logged QSO (required for VUCC award credit)

  • an I in the LoTW cfm item means that the LoTW QSL specifies a valid IOTA designator that matches the IOTA item specified in the logged QSO

  • an N in the LoTW cfm item means that the LoTW QSL specifies park codes that match each of the park codes specified in the logged QSO's user item whose caption is NPOTA (required for NPOTA award credit)

  • a Z in the LoTW cfm item means that the LoTW QSL specifies a valid CQ zone that matches the CQ zone item specified in the logged QSO (required for WAZ award credit)

Right-clicking a QSO in the Log Page Display and selecting the Update from LoTW menu item performs the Sync LoTW QSLs operation on the selected QSO; this provides a quick way to update a QSO's LoTW cfm item after your QSO partner has re-uploaded the QSO with additional or corrected mode, US State, grid square, national park, or CQ zone information.

Clicking the Update from LoTW button on the Main window's QSL tab performs the Sync LoTW QSLs operation on every QSO in the Log Page Display. This operation should only be invoked after re-uploading QSOs that LoTW may not consider "new", and thus would not be updated by the Sync LoTW QSOs or Sync LoTW QSLs operation -- for example, uploading QSOs with the Permit uploaded of QSOs already uploaded to LoTW option enabled. Update from LoTW should not be used when the Log Page Display contains more than 100 QSOs; instead, depress the CTRL key and invoke Sync LoTW QSLs, as this will complete more rapidly.

If the Sync LoTW QSLs or Update from LoTW function encounter a QSO with one or more items that don't match the information reported by LoTW, that QSO's Select item will be set to 'Y'.

Any errors encountered while inspecting the downloaded QSLs will be displayed in a results report. QSLs that match no QSO in the current log are reported as errors if the Report unmatched QSLs as errors box is checked; this setting defaults to unchecked, and is maintained independently for each log. 

If the Subdivisions box is checked, any LoTW confirmation with a station in the US, Hawaii, or Alaska that does not specify a valid US state will be reported. 

If band or Sat boxes are checked in the VUCC Panel, any LoTW confirmation with a station on a band sought for VUCC (or with a propagation mode set to Satellite if the Sat box is checked) will be reported under any of these conditions:

• the LoTW QSL does not specify a grid square, or specifies one or more  invalid grid squares

• the LoTW QSL specifies one or more grid squares that don't match any grid square specified in the logged QSO

• the LoTW QSL does not specify one or more grid squares specified in the logged QSO

Each LoTW QSL is compared with its matching logged QSO. Information reported by LoTW that is not present in the logged QSO will be automatically added unless it is inconsistent with the callsign; for example, a logged QSO missing a Iota tag will be updated with the Iota tag contained in its matching QSL, but a QSO with AA6YQ missing a CQ zone will not updated with a CQ zone of 6. The comparison process compensates for syntactic differences; eu1 and EU-001 are considered identical, for example. If the a logged 4-character gridsquare matches the first 4 characters of the matching QSL's 6-character gridsquare, then the logged QSO will be updated with the 6-character gridsquare. When information reported by LoTW is inconsistent with the information contained in the QSO's matching QSL, however, the conflict is resolved as specified in the Handling of LoTW detail inconsistencies setting, which provides four choices

• always replace the logged data with the LoTW QSL data

• always preserve the logged data, ignoring the LoTW QSL data

• always preserve the logged data, ignoring the LoTW QSL data, and describe each inconsistency in the report displayed when the Sync LoTW QSLs or Update from LoTW operation completes

• display a dialog presenting the logged data and the LoTW QSL data so that the user can choose (the default setting)

If either the LoTW QSL or the logged QSO specifies more than one grid square, the Sync LoTW QSLs will as described above report logged grids that are not specified in the QSL, and grids specified in the QSL that are not logged in the QSO, but will not modify the logged grids with LoTW QSL data regardless of the Handling of LoTW detail inconsistencies setting.

If you submit a DXCC application using LoTW, the QSOs confirmed via LoTW to which DXCC credit is newly granted will not be reported the next time that you invoke the Sync LoTW QSLs function unless a newly-confirmed QSO has already been granted DXCC award credit.. The Update from LoTW function will update your logged QSOs to reflect the granting of DXCC credit by setting their LoTW rcvd items to V. If a confirmed QSO to which DXCC award credit has been granted is reported by the Sync LoTW QSLs function, that QSO's LoTW rcvd item will be set to V

When the Sync LoTW QSLs or Update from LoTW function completes, DXKeeper displays a report showing

• any errors encountered while inspecting the downloaded QSLs; each is preceded by Error:

• any confirmations of desired (per your specified DXCC award objectives) but previously unconfirmed entities, entity-modes, or entity-bands

• any granting of DXCC award credit to desired (per your specified DXCC award objectives) entities, entity-modes, or entity-bands for which DXCC credit had not been previously granted

• any changes to logged QSOs made as a result of

  • resolving inconsistencies

  •  adding location information newly reported by LoTW, e.g. a CQ zone

  • deducing location information from location information newly reported by LoTW, e.g. an ARRL Section from a newly reported state and county

If the resolution of inconsistencies between LoTW QSL data and logged data resulted in changes to logged data that impact Realtime Award Tracking and SpotCollector is running, DXKeeper will offer to direct SpotCollector to recompute (update the Realtime Award Tracking information for each Spot Database Entry).

After logged QSOs have been updated, the Sync LoTW QSLs function filters the Log Page Display to show only QSOs confirmed via  LoTW , and sorts it in ascending or descending order of LoTW date rcvd. The Filter and Sort panel's captions will indicate how the Log Page Display is being filtered and sorted respectively. Depressing the CTRL key while clicking the Filter panel's X button both resets the Log Page Display filter and sorts the Log Page Display in ascending or descending order of each QSO's Begin time.

If you modify the callsign, QSO begin, band, mode, submode or station callsign item of a logged QSO that has already been uploaded to LoTW, the Sync LoTW QSLs function will be unable to locate the QSO in your log to update it; to correct this situation,

1.  right-click the Log Page Display entry for the QSO, and select Upload to LoTW from the popup menu

2. wait a few minutes for LoTW to process the uploaded QSO

3. right-click the Log Page Display entry for the QSO, and select Update to LoTW from the popup menu

To be prompted when you modify the callsign, QSO begin, band, mode, submode or station callsign item of a logged QSO that has already been uploaded to LoTW, enable the Prompt on change to logged QSO already uploaded to eQSL.cc and/or LoTW option.

The Sync LoTW QSOs and Sync LoTW QSLs functions remember the acceptance and confirmation dates and times of the most-recently processed QSO and QSL respectively; these times are shown beneath their buttons. When activated, these functions direct  LoTW to supply only newly-arrived QSOs or QSLs, thereby minimizing the amount of information to be downloaded and inspected. You can, however, force all QSOs or QSLs to be downloaded and inspected by depressing the CTRL key while clicking the buttons that activate these functions.

If DXKeeper is unable to download uploaded QSOs or QSLs, verify that the ARRL's LoTW web site is operational; also verify that ARRL personnel have not changed your username and/or password.

If all of your QSOs are logged with the same station callsigns from the same location in a single log file, then the above facilities are all that are required to successfully maintain synchronization between your log and LoTW; If you have logged QSOs with multiple station callsigns, from multiple QTHs, and/or in multiple log files, then the following facilities can be used to accelerate processing. 

By default, LoTW will download all of your accounts QSOs or QSLs when you click Sync LoTW QSOs and Sync LoTW QSLs respectively. If your current log contains only QSOs made from a single station callsign, however, you can reduce both the download and inspection times by specifying that callsign in the Limit Sync operations to this callsign setting. This setting is maintained independently for each log; loading a new log will automatically restore the setting value you established when that log was loaded. When the setting contains no callsign, all QSOs and QSLs in your LoTW will be downloaded by Sync LoTW QSOs and Sync LoTW QSLs respectively. Here's an example:

Enabling Report unmatched QSLs as errors is only practical when downloading is limited to a single station callsign -- either because the LoTW account contains only QSOs and QSLs made with that station callsign, or because Limit QSO and QSL downloads to this callsign is set to a specific callsign, as in the FJ-AA6YQ.mdb and KP2-AA6YQ.mdb logs in the example above.

Uncertain Station Callsigns

In circumstances where you are uncertain as to the station callsign used in one or more QSOs -- for example, AA6YQ vs. AA6YQ/1 -- one approach you can take is to 

• upload them all with the operator callsign set to AA6YQ

• modify them all to have an station callsign of AA6YQ/1 and upload them again

QSOs submitted by your QSO partners will match one or the other.. By checking the Exclude station callsign when matching QSOs & QSLs to logged QSOs box, your QSOs will be properly confirmed when you run the Sync LoTW QSLs function.

Computer is not connected to the Internet

If your computer is not connected to the Internet but you have access to an Internet connection from another PC, check the PC has no internet connection box. When you click the Prep LoTW upload button, DXKeeper will invoke TQSL as described above to generate a signed (.tq8) file, and then display the name of this file so you can move it to an internet-connected PC and manually upload it to LoTW. After this upload is accomplished, click the Update Log button; DXKeeper will then perform the following for each enabled entry in the QSL Queue: 

• set the associated logged QSO's LoTW sent to U, reflecting the fact that the QSO has been uploaded, but its individual acceptance by LoTW is unknown. 

• set the associated logged QSO's LoTW date sent to the current UTC date

• set the associated logged QSO's LoTW rcvd to R

• remove the entry from the QSL Queue

With the PC has no internet connection box checked, invoking the Sync LoTW QSO, Sync LoTW QSL, or Update from LoTW functions will result in DXKeeper prompting you to manually query LoTW from an internet-connected PC and then move the file containing the query results to a specified file on your PC. When you click the OK button, DXKeeper will process the query results as if they had been directly downloaded from LoTW.

Uploading a Batch of QSOs to Club Log

Clicking the Club Log operations panel's  Upload to Club Log button will upload all logged QSOs whose Station_Callsign items matche the specified Club Log Callsign and that have never before been uploaded to Club Log, and whose uploads are not "prohibited" by their Club Log Sent items being set to N.

• To instead upload all QSOs whose Station_Callsign items match the specified Club Log Callsign and whose uploads are not "prohibited" by their Club Log Sent items being set to N - whether or not they've already been uploaded to Club Log - depress the CTRL key while clicking the Upload to Club Log button

• To instead upload all QSOs in the Log Page Display whose Station_Callsign items match the specified Club Log Callsign - no matter what their Club Log Sent items specify - depress the ALT key while clicking the Upload to Club Log button

• The date and time shown beneath the  Upload to Club Log button will be updated to show the time at which this operation was initiated; its only purpose is to provide a reminder to the user.

QSOs with callsigns that begin with an exclamation point (!) are not uploaded to Club Log unless the Upload QSOs whose callsigns begin with ! box is checked - in which case the ! is removed from the callsign before it is sent to Club Log.

Club Log accepts QSOs on these bands.

If more than 5000 QSOs will be uploaded, DXKeeper automatically segments the action into files of 5000 QSOs; as Club Log limits the number of queued files to 10, a maximum of 50,000 QSOs can be submitted via the Upload button. Checking the Slow net box segments the action into groups of 250 QSOs, ensuring delivery when uploading via a slow internet connection; with this option enabled, a maximum of 2500 QSOs can be submitted via the Upload button. To submit larger numbers of QSOs to Club Log, use the Export ADIF for Club Log function to generate an ADIF file, and then upload that file to Club Log.

Uploading a QSO to Club Log by Right-clicking a Log Page Display Entry

Right-clicking a QSO's entry in the Log Page Display and selecting the Upload to Club Log: C command from the pop-up menu immediately uploads that QSO to Club Log using the station callsign C.

The Upload to Club Log command will be disabled if the selected QSO begins with an exclamation point (!) and the Upload QSOs whose callsigns begin with ! box is unchecked.

Uploading QSOs to Club Log as they are Logged

You can configure DXKeeper to automatically upload each QSO to Club Log when it is initially logged via the Capture window or via the Main window's Log QSOs tab.

Items Uploaded to Club Log

The following items are included with each QSO uploaded to Club Log.

Deleting a QSO from Club Log

Right-clicking a QSO's entry in the Log Page Display and selecting the Delete from Club Log command immediately directs Club Log to remove that QSO from your account.

Synchronizing: Updating Logged QSOs to Reflect their Confirmation via Club Log

Clicking the Club Log operations panel's Sync Club Log QSLs button will direct Club Log to report all confirmations created on or after the date shown beneath the Sync Club Log QSLs button. DXKeeper will direct Club Log to report all such confirmed QSOs. Each reported QSO's Club Log Rcvd item will be set to Y, and the date shown beneath the Sync Club Log QSLs button will be updated to the current date.

• Depressing the CTRL key while clicking the Sync Club Log QSLs button will direct Club Log to report all confirmations, and set each confirmed QSO's Club Log Rcvd item to Y.

• Double-clicking the date beneath the Sync Club Log QSLs button will display the Club Log QSL Synchronization window, which will enable you to specify a date of your choosing.

Club Log confirms QSOs on these bands.

Requesting a Confirmation via Club Log

If your QSO partner has configured Club Log to accept confirmation requests, you can log in to your Club Log account and request confirmation of an uploaded QSO that matches what your QSO partner uploaded.

• Clicking the Club Log operations panel's Home button will direct your web browser to display the Club Log home page.

  • Log in to your Club Log account

  • Select Log Search from the Tools menu along the left side of the Club Log home page

  • On the Log Search page that appears, specify the callsign of the Log to search

  • If one or more QSOs with the specified callsign have been confirmed, click the Request QSL Card button

• After requesting a confirmation via Club Log, select the QSO in DXKeeper's Log Page Display, and click the QSL panel's OQRS button to indicate that you have requested its confirmation via an electronic QSLing service.

Using the Main window's Log QSOs tab to modify any item of a QSO whose Club Log status is set to Y will change the QSO's Club Log status to M.

Processing Inbound OQRS Requests from Club Log

If you receive many requests for confirmations, accepting OQRS requests will reduce the amount of incoming postal mail containing QSL cards, self-addressed envelopes, and small bills for postage. This Inbound OQRS service makes it easy to populate DXKeeper's QSL Queue with OQRS requests for confirmation via QSL cards/labels, eQSL,cc, and/or LoTW. Your PayPal account will be credited with funds for postage and return envelopes, and with donations.

Clicking the Club Log operations panel's Inbound OQRS button directs Club Log to report all new confirmation requests received since the date-and-time that the Inbound OQRS button was last clicked, which is shown beneath the Inbound OQRS button. Each confirmation request received will be matched with a logged QSO, using the +/- 15 minutes matching rule employed by Club Log. For each logged QSO that matches an incoming confirmation request,

1. if the Inbound OQRS sub-panel's Set 'QSL Sent' to 'R' box is checked and the logged QSO's QSL Sent item is not set to N or I, or QSL Sent is set to Y but QSL Sent Via is not set to B or D,

   • the QSL Sent item is set to R

   • the QSL Sent Via item to B (for bureau) or D (for direct) as indicated in the confirmation request

2. if the Inbound OQRS sub-panel's Set 'eQSL QSL Sent' to 'R' box is checked and the logged QSO's eQSL QSL Sent item is not set to N, I, U, or Y, the eQSL QSL Sent item is set to R

3. if the Inbound OQRS sub-panel's Set 'LoTW QSL Sent' to 'R' box is checked and the logged QSO's LoTW QSL Sent item is not set to N, I, U, or Y, the LoTW QSL Sent item is set to R

4. the address item  is set to the postal address specified in the confirmation request (note: addresses specified in UTF-8 Unicode will be ignored)

5. the email item is set to the email address specified in the confirmation request

6. any payment or donation information specified in the confirmation request is appended to the contents of the comment item

After each logged QSO matching a confirmation has been updated, a report listing confirmation requests that contained errors or did not match a logged QSO will be displayed, and the date-and-time shown beneath the Inbound OQRS button will be updated; this updated date-and-time is stored in the current log file.

With the QSL Sent, eQSL QSL Sent, and LoTW QSL Sent items of each matched QSO set as specified by the Inbound OQRS sub-panel checkboxes, confirmations requests can be fulfilled by

1. setting the QSL Via panel to Cards, Labels, ADIF file, tab-delimited file, eQSL.cc, or LoTW

2. invoking the Add Requested function to populate the QSL Queue

3. printing outgoing QSL cards or labels and their envelopes or address labels, uploading confirmations to eQSL.cc, or confirmations to LoTW

Inbound OQRS Variations

• Depressing the Ctrl key while clicking the Inbound OQRS button directs Club Log to report all confirmation requests, and update matching logged QSOs as described above.

• Depressing the Alt key while clicking the Inbound OQRS button displays a file selector with which you can choose an ADIF file containing Inbound OQRS requests that you manually downloaded from Club Log; DXKeeper will process the requests in the file you select as described above.

• Clicking the date-and-time displayed immediately below the Inbound OQRS button displays a window with which you can modify the date-and-time that will be used when the Inbound OQRS function is next invoked.

QSLing via QRZ

Before using DXLab's QRZ automation for the first time,

1. obtain a QRZ XML subscription; this is required to enable interoperation with DXKeeper via QRZ's programmatic interface

2. if you don't have a QRZ logbook for your current primary station callsign, click My Logbook in the dropdown menu that appears when you click on your callsign in the upper-right corner of your QRZ web page, and then click the Settings button in the upper-right corner of your QRZ Logbook web page; in the Settings window that appears,

   • in the Logbook Info section,

     • set the Start Date to be as early as the earliest QSO in your log

     • set the End Date to be an appropriately distant date in the future

   • click the QRZ Logbook API section's Show button to reveal your Logbook API Key

3. in the QRZ Logbook Selection panel on DXKeeper's QSL Configuration window's QRZ tab

   • click the New button

   • in the New QRZ Logbook Station Callsign and API Key window that appears, specify your Station Callsign and Logbook API Key, and then click the OK button

If you make (or made) QSOs with more than one station callsign, repeat steps 2 and 3 above for each station callsign.

The functions described in this section are available on the Main window's QSL tab when you set the the QSL Via panel to QRZ.

Uploading QSOs to QRZ

When a QSO is uploaded to QRZ,

• the QSO's QRZ Sent item is set to Y

• the QSO's QRZ date sent item is set to the current date

• the QSO's QRZ LogID item is set to a unique logid generated by QRZ

Uploading a Batch of QSOs to QRZ

Clicking the QRZ operations panel's Upload to QRZ button will upload all logged QSOs whose Station_Callsign items match the selected QRZ Logbook and that have never before been uploaded to QRZ, and whose uploads are not "prohibited" by their QRZ Sent items being set to N.

• To instead upload all QSOs whose Station_Callsign items match the selected QRZ Logbook and whose upload is not "prohibited" by their QRZ Sent items being set to N - whether or not they've already been uploaded to QRZ, depress the CTRL key while clicking the Upload to QRZ button

• To instead upload all QSOs in the Log Page Display whose Station_Callsign items match the selected QRZ Logbook - no matter what their QRZ Sent  items specify - depress the ALT key while clicking the Upload to QRZ button

• The date and time shown beneath the Upload to QRZ button will be updated to show the time at which this operation was initiated; its only purpose is to provide a reminder to the user.

QSOs with callsigns that begin with an exclamation point (!) are not uploaded to QRZ unless the Upload QSOs whose callsigns begin with ! box is checked - in which case the ! is removed from the callsign before it is sent to QRZ.

Uploading a QSO to QRZ by Right-clicking a Log Page Display Entry

Right-clicking a QSO's entry in the Log Page Display and selecting the Upload to QRZ: C command from the popup menu immediately uploads that QSO to QRZ using the station callsign C.

The Upload to QRZ command will be disabled if the selected QSO begins with an exclamation point (!) and the Upload QSOs whose callsigns begin with ! box is unchecked.

Uploading QSOs to QRZ as they are Logged

You can configure DXKeeper to automatically upload each QSO to QRZ when it is initially logged via the Capture window or via the Main window's Log QSOs tab.

Items Uploaded to QRZ

The following items are included with each QSO uploaded to QRZ.

• call

• DXCC

• QSO begin

• freq

• band

• rx band

• rx_freq

• mode

• submode

• CQZ

• IOTA

• ITUZ

• SOTA_Ref

• grid 1

• grid 2

• grid 3

• grid 4

• comment

• operator

• propagation mode

• sat_name

• sat_mode

• rst_sent

• rst_rcvd

• Operator

• Name

• Address

• QTH

• TX_Power

• QSLMsg

• Contest_ID

• SFI

• A_Index

• K_Index

• QSL_Via

• PFX

• ARRL_Sect

• State

• Cnty

• Rig

• Email

• Web

• Ant_Az

• Ant_El

• Ant_Path

• Distance

• QSL_Sent_Via

• QSL_Rcvd_Via

• QSL sent

• QSL rcvd
  • if the value is E or B or M, uploads the value V
  • if the value is S, uploads the value Y
  • if the value is X, uploads the value I - unless LoTW QSL rcvd is set to Y or S or V, in which case no value is uploaded

• date sent

• date rcvd

• LoTW_QSL_sent

• LoTW QSL rcvd

• if the value is S, uploads the value Y

• if the value is X, uploads the value I - unless QSL rcvd is set to Y or V or E or B or M, in which case no value is uploaded)

• eQSL_QSL_Sent

• eQSL QSL rcvd

• if the value is X, uploads the value I - unless QSL rcvd is set to Y or V or E or B or M, in which case no value is uploaded)

• Club_Log_Sent

• Club_Log_Rcvd

• Credit_Submitted

• Credt_Granted

• IOTAVerified

• VUCCVerified

• WASVerified

• WAZVerified

• WPXVerified

• MY_DXCC

• MY_STATE

• MY_CQ_ZONE

• MY_ITU_ZONE

• MY_CNTY

• MY_CITY

• MY_GRIDSQUARE

• MY_IOTA

• MY_NAME

• MY_LAT

• MY_LON

• Each user-defined item that specifies a Caption and whose ADIF box is checked

Deleting a QSO from QRZ

Right-clicking a QSO's entry in the Log Page Display and selecting the Delete from QRZ command immediately directs QRZ to remove that QSO from your account.

Synchronizing: Updating Logged QSOs to Reflect their Confirmation via QRZ

Clicking the QRZ operations panel's Sync QRZ QSLs button will direct QRZ to report all confirmations created on or after the date shown beneath the Sync QRZ QSLs button. DXKeeper will direct QRZ to report the logid all such confirmed QSOs. Each reported QSO's QRZ rcvd item will be set to Y,  and its QRZ rcvd date item and the date shown beneath the Sync QRZ QSLs button will be updated to the current date.

• depressing the CTRL key while clicking the Sync QRZ QSLs button will direct QRZ to report all confirmations, and set each confirmed QSO's QRZ rcvd item to Y

• double-clicking the date beneath the Sync QRZ QSLs button will display the QRZ QSL Synchronization window, which will enable you to specify a date of your choosing

If you have already established and populated a QRZ Logbook - for example, by exporting an ADIF file from your log in DXKeeper and then importing that file into your QRZ Logbook - you must first upload your logged QSOs from DXKeeper to your QRZ Logbook before you can update logged QSOs to reflect their confirmation via QRZ using the Sync QRZ QSLs function described above. Doing so will not create duplicate QSOs - or have any other adverse impact - on your QRZ logbook, but it will require you to direct your QRZ Logbook to re-import your LoTW confirmations.

 QSL Substitution Commands

Any substitution command found in a QSL Information textbox will be replaced as described in the table below before printing that textbox's content on a generated QSL card. This allows you to incorporate information about your operating location, equipment, and conditions that can vary from QSO to QSO.

Any substitution command found in a QSL msg will be replaced as described in the table below before the message is

• printed on a QSL card

• printed on a QSL label

• uploaded to eQSL.cc

• uploaded to LoTW

• placed in an ADIF file from the QSL queue

• placed in a tab-delimited file from the QSL queue

• exported to an ADIF file with the Export ADIF for eQSL.cc option selected

This allows you to personalize the QSL msg with information about you and your QSO partner.

The substitution command <via> lets you include contents of the QSO's Via item on the QSL card. if the QSO's Via item is specified, then the replacement is the word "via:" followed by the contents of the Via item; otherwise, the replacement is empty. The <propmode> and <satname> fields work in a similar fashion. The <satmode>, <rxfreq>, and <rxband> commands only produce replacements if the QSO specifies a satellite name.