QSLing

DXKeeper Online Help Contents

 

DXKeeper supports three independent kinds of QSLing:

You can choose to confirm a QSO by any one of these QSL kinds, any two, or all three. DXKeeper can also generate cards and labels that confirm reports from Shortwave Listeners (SWLs)

Paper QSL cards and labels can be printed

Paper QSL cards can be routed

Note that how a QSO's paper QSL card is conveyed is independent of whether the QSO is uploaded to eQSL.cc or LotW.

Traditionally, the need to load your printer with index stock or labels has made QSLing a batch operation, rather than an activity accomplished at the time you log a QSO. After accumulating some number of QSOs for which confirmation is desired, you identify the QSOs, load the printer with index stock or blank QSL labels, print QSL cards or labels for each designated QSO, reload the printer with envelopes or blank address labels, print addresses for each QSL, and finally update the original QSOs to indicate that  QSLs have been sent and, if appropriate, that return QSLs have been requested.  DXKeeper thus provides a QSL Queue in which to assemble a batch of outgoing QSLs; the QSL Queue is stored in each log file; if you switch log files, you will also switch QSL Queues. 

The eQSL.cc service provides a new mode of operation; by depressing the Ctrl key while logging a QSO via the Main or Capture windows, DXKeeper will immediately upload the QSO to eQSL.cc; if you check the Upload an eQSL... box, simply logging a QSO via the Capture window will perform the immediately upload without your having to depress the Ctrl key. Real-time uploads are attractive if you are always connected to the internet, but those using dialup connections will prefer to connect to the internet, upload a batch of QSLs to eQSL.cc and then disconnect; the QSL Queue supports this latter mode of operation.

Because LotW QSOs must be digitally encrypted before transmission to the ARRL, its it is more efficient wait until a batch of QSLs are needed before uploading them. Batches of outgoing QSLs are collected in the QSL Queue. From here, they can be printed or uploaded, and then used to update your log to indicate the operation's success. 

DXKeeper provides a set of immediate QSLing operations. If the QSL Queue is empty, right-clicking on a QSO in the Log Page Display will produce a popup menu containing the following options:

Left-clicking on one of these options will immediately perform the action; before selecting Print QSL card, Print Envelope or Print Self-addressed Envelope, load your printer with the appropriate media. Note that selecting Print QSL card will uncheck the Print Preview option.

The workflows for batch QSLing via cards, labels, eQSL.cc, LotW, files, or EFT are similar:

  1. choose the QSL kind (cards, labels, eQSL.cc, LotW, ADIF file, or tab-delimited file )

  2. identify the QSOs for which QSLs should be sent and load them into the QSL Queue

  3. print or upload the QSLs, or place the QSL information in a file for printing and/or distribution by another application or service

  4. print addresses on envelopes or labels (only if QSLing via cards or labels)

  5. remove each successfully processed entry from the QSL queue, and update its associated QSO to indicate that QSLs have been sent and, if appropriate, that return QSLs have been requested (this step is automatic when uploading to eQSL.cc or LotW)

When a QSL Queue entry is created from a logged QSO in step 2 above, a snapshot of the  information in that logged QSO is used to populate the QSL Queue entry. If you subsequently modify the logged QSO -- for example, by editing the logged QSL Message -- this modification will not be automatically propagated to QSL Queue entry; to accomplish this propagation, you must clear and then repopulate the QSL Queue.

You will also wish to update your log to reflect incoming confirmations, whether in the form of QSL cards received via postal mail or via eQSL.cc or LotW; the process of updating your log to reflect confirmations received from eQSL.cc and LotW is automated, and is referred to as synchronization.

If you intend to upload a large number of QSOs to eQSL.cc, the following workflow will be faster than identifying individual QSOs and loading them into the QSL Queue:

  1. Filter the Log Page Display so that all QSOs to be uploaded are visible

  2. Use the Main window's Export to eQSL.cc function to generate an ADIF file that can be uploaded to eQSL.cc

The exact threshold depends on your CPU and hard drive speed, as well as the bandwidth of your internet connection, but more than a few hundred QSOs is a good guideline for using the Export functions rather than the Upload functions.

Similarly, uploading more than 1000 QSOs to LotW is best accomplished with the following workflow:

  1. Filter the Log Page Display so that all QSOs to be uploaded are visible

  2. Use the Main window's Export to LotW function to generate an ADIF file that can be processed by the ARRL's TQSL program to produce a file that can be uploaded to LotW

 

Choosing the QSL kind: cards/labels, eQSL.cc, LotW, ADIF files, or tab-delimited files

You choose the QSL kind by making a selection in the QSL Via panel on the Main window's QSL tab:

 

Selection

Meaning

Cards

print QSL cards, 4 per page

single labels

print QSL labels via a label printer

2-column labels print QSL labels, typically 20 per page
3-column labels print QSL labels, typically 30 per page
eQSL.cc upload QSOs to eQSL.cc
LotW upload QSOs to LotW
ADIF file save QSO information in a specified file using ADIF format (for QSL generation by another application or to convey QSL information via EFT)
tab-delimited file save QSO information in a specified file using tab-delimited format (for QSL generation by another application using mail merge techniques)

Cards, labels, ADIF files, and tab-delimited files are all used to produce hardcopy QSL cards that are physically conveyed to the station you worked; these four kinds are therefore collectively referred to as QSL Cards.

Once you populate the QSL Queue with one or more entries, your ability to change the QSL Via panel's selection becomes limited. You can switch among cards, labels, ADIF files, and tab-delimited files, but you cannot switch from any of these to the LotW or eQSL.cc selections, or vice versa. You also can't switch between LotW and eQSL.cc. If you've populated the QSL Queue and decide you must change the QSL Via panel's selection, first clear the QSL Queue.

Identifying QSOs for which QSLs should be sent and loading them into the QSL Queue

You can place an individual QSO in the QSL Queue by right-clicking on its entry in the Log Page Display and then left-clicking on the Add to QSL Queue option. To add a Shortwave Listener (SWL) confirmation for a QSO to a batch of outgoing QSL cards or labels, place an SWL confirmation of that QSO in the QSL Queue by right-clicking on its entry in the Log Page Display and then left-clicking on the Add SWL Entry to QSL Queue option. 

You can direct DXKeeper to populate the QSL Queue with multiple QSOs in order to

Responding to requests for confirmation and soliciting confirmation require status information to be recorded with each QSO. DXKeeper separately tracks the confirmation of each QSO by QSL Card, eQSL.cc, and LotW. For each of these three kinds of QSLing, there are four fields stored with each QSO:

  QSL Card eQSL.cc LotW Meaning
outgoing status QSL sent eQSL sent LotW sent
  • N - no outgoing QSL should be sent or uploaded

  • R - an outgoing QSL should be printed or uploaded

  • U - the outgoing QSL has been uploaded but acceptance is unknown (LotW only)

  • Y - the outgoing QSL has been printed or uploaded and accepted

  • I - no outgoing QSL should be sent or uploaded

outgoing date QSL date sent eQSL date sent LotW date sent date on which the outgoing QSL was printed or uploaded and accepted
confirmation status QSL rcvd eQSL rcvd LotW rcvd
  • R - the outgoing QSL should (or did) include a request for a confirming QSL

  • Y - confirmation has been received

  • S - confirmation has been submitted to the ARRL for verification (cards & LotW only)

  • V - confirmation has been verified by the ARRL (cards & LotW only)

  • E - Entity-only confirmation has been verified by the ARRL (cards only)

  • B - Entity-and-Entity-Band-only confirmation has been verified by the ARRL (cards only)

  • M - Entity-and-Entity-Mode-only confirmation has been verified by the ARRL (cards only)

  • I - this QSO is invalid for award purposes

    • QSL rcvd: invalid for DXCC awards and Marathon country credit

    • LotW rcvd: invalid for DXCC awards

    • eQSL rcvd: invalid for eQSL.cc awards

    • WAZVerified: invalid for WAZ and Marathon awards

  • X - this QSO can't be confirmed

confirmation date QSL date rcvd eQSL date rcvd Lotw date rcvd date on which the incoming QSL was received

 

To designate a QSO for which an outgoing QSL should be printed or uploaded, set the outgoing status to R. If you'd like the QSO confirmed, also set the appropriate confirmation status to R; in the case of cards and 2-column labels, this will result in the a "please!" being printed in the card's QSL? column. To have every outgoing card print "please!" in its QSL? column unless its QSO is already confirmed, enable the Outgoing QSLs request confirmation unless already confirmed option.

To designate a QSO for which no outgoing QSL card should be generated, set its QSL sent to N.

The Main window's QSL and Online QSL panels provide full access to the outgoing status fields for QSL Card, eQSL.cc, and LotW. These panels also provide RR buttons for each kind of QSL; clicking an RR button simultaneously sets the outgoing status to R and the confirmation status to R. Having to click all these buttons for each logged QSO would clearly be inconvenient. While we may only send a QSL card if asked or if needed to solicit a confirmation,  there is good reason to upload every logged QSO to eQSL.cc and LotW, assuming you have accounts with each; by doing so, you provide confirmation of your QSO to those in need. Thus DXKeeper provides an Initialize eQSL sent to 'R'  box that when checked will automatically set the eQSL.cc outgoing status to R whenever you log a QSO, and an Initialize LotW sent to 'R'  box that when checked will automatically set the LotW outgoing status to R whenever you log a QSO. Even if you have no immediate plans to use eQSL.cc or LotW, leaving these boxes in their default checked setting is a good idea; if you eventually change your mind, your QSOs will already be flagged for uploading.

With DXKeeper configured to always designate QSOs for upload to eQSL.cc and LotW, the only decision you must make is whether to send a paper QSL Card. If you are logging QSOs from the Capture window and decide that you'd like a QSL card -- or are asked for a card by your QSO partner -- check the Capture window's QSL Requested box; if you log the QSO with this box checked, both the QSL Card outgoing status and confirmation status will be recorded as R. If you are logging QSO's via the Main window, clicking the QSL panel's RR will have the same effect.

Add Requested

The Add Requested function on the Main window's QSL tab responds  to requests for confirmation from a QSO partner; it

LotW requires that only QSOs made with the same station callsign be uploaded together. The Add Requested operation enforces this by ignoring any QSO whose  station callsign does not match the station callsign specified in the current LotW station location; a message will be displayed if one or more QSOs have not been added to the QSL Queue for this reason.

If the Add Requested no dup band-modes option is enabled, the Add Requested function will not create a QSL Queue entry unless doing so would give the receiving station a new band or mode, or unless the QSL Via panel is set to LotW or eQSL.cc .

Add Needed

Besides memorializing memorable QSOs, we send QSL Cards to solicit QSO confirmations needed to achieve our DXing objectives. DXKeeper provides the Add Needed function to automate this process for the following awards:

The Add Needed function scans all QSOs in the Log Page Display for QSOs whose confirmations are required for the awards you've selected, considering the DXing objectives you have specified - but ignoring any QSO whose QSL sent item is set to N or I; for each such QSO, the Add Needed function

On the assumption that all QSOs will be uploaded to LotW and/or eQSL.cc, the Add Needed function is only available when the QSL kind is QSL cards, QSL labels, ADIF files, or tab-delimited files. When Add Needed finds a QSO whose confirmation is required, it adds this QSO to the QSL Queue.

Add Needed can optionally specify routing by setting QSL Via to 'B' or 'D' or 'E' for each QSO it adds to the QSL Queue. 

Add All

The Add All function creates an entry in the QSL Queue for each QSO in the Log Page Display - independent of whether its needed and/or requested. By filtering the Log Page Display before invoking Add All, you can choose only those QSOs within a date range, or with a particular DXCC entity, or on a specified band.

LotW requires that only QSOs made with the same station callsign be uploaded together.  If the QSL Via panel is set to LotW, the Add Requested operation enforces this by ignoring any QSO whose  station callsign does not match the station callsign specified in the current LotW station location; a message will be displayed if one or more QSOs have not been added to the QSL Queue for this reason.

 If you are just starting with LotW, Add All is an efficient way to select all of a log's QSOs for uploading; because eQSL.cc uploading is optimized for interactivity, it will be faster to upload a large number of QSOs by using Export to eQSL.cc. The Add All function will ignore any QSO 

For other awards -- VUCC, ARRL Worked All States, ARRL Worked All Continents, Islands On The Air, CQ Worked All Zones, or CQ Worked All Prefixes, you must designate needed confirmations by clicking  the RR button on the Main window's QSL panel, and then click Add Requested; reports generated from the Main window's Check Progress tab do indicate which confirmations are required for these awards.

Routing: Direct, via the QSL bureau, or via Electronic File Transfer (EFT)

Each QSL Queue entry's Sent Via item indicates how the QSL should be sent:

Routing Sent_Via 
 - by postal mail directly to your QSO partner D
 - by postal mail to a QSL bureau B
 - by EFT (Global QSL, OQRS E

To change a QSL Queue entry's routing, click in it's entry's Sent Via cell, and a down-facing black triangle will appear. Click the triangle, and a dropdown selector will appear that lets you choose the desired routing; the entry's left-most column will display a pencil icon, indicating that the entry has been modified but not saved. Click any other QSL Queue entry to save the modified entry; DXKeeper will propagate the modified Sent Via item to the QSO from which the QSL Queue entry was generated. Note: if the QSL Queue contains a single entry that you've modified, save it by clicking the right-facing arrow button and then the left-facing arrow button in the group of VCR-like buttons below the QSL Queue's lower-right corner. When the Update Log function is initiated, each QSO's Sent Via item will be updated from its QSL Queue entry's Sent Via  item

Constraints

Once one or more entries have been added to the QSL Queue with Add Requested, Add Needed, or Add All, you can no longer change the selected QSL kind until you either complete this batch of QSLs -- either by printing or by uploading --  and update your log accordingly, or until you abort this batch by clicking the QSL tab's Clear button.

Because eQSL.cc confirmations currently do not "count" for ARRL DXing awards, the Add Needed function is disabled when the selected QSL Via panel is set to is eQSL.cc. While LotW confirmations do "count" for ARRL DXing awards, it is assumed that users with an LotW account will upload every QSO (in batches); thus the Add Needed function is also superfluous when the selected QSL kind is LotW

The LotW implementation of digital encryption requires that all QSLs in an uploaded batch share the same station callsign and the same station QTH.  If all QSOs in your log meet this requirement, then you can freely use Add Requested and Add All. If not, you must either filter the Log Page Display to meet this requirement prior to invoking these operations, or you must configure the Add Requested and Add All operations to ignore QSOs except those with a specified callsign when the QSL Via panel is set to LotW.

QSL Queue Operations

The topics below describe how to 

You can sort the QSL Queue in ascending or descending order of any of its columns. Double-clicking on a column's caption sort's the QSL Queue in ascending order of that column; double-clicking on the same column's caption again sorts the QSL Queue in descending order of that column.

With the QSL Via panel set to Cards, 2-column labels, 3-column labels, ADIF file, or tab-delimited file, QSL Queue entries that are missing an Address item and have a Sent Via item not set to buro are highlighted in red font.

To specify or modify the Address item of a entry in the QSL queue, to change its Sent Via item, or to change its QSL Msg item, double-click its entry to display DXKeeper's QSL Editor window; from this window, you can direct Pathfinder (if running) to perform a QSL route lookup on the callsign, or on the QSL manager's callsign. When you click the QSL Editor's Save button, any changes you've made will update both the QSL Queue entry and the logged QSO. If the Alt key is depressed when the entry is double-clicked, DXKeeper will also direct DXView (if running) to display information about the entry's callsign, including DXCC progress by band and mode.

Double-clicking a QSL Queue entry while depressing the Ctrl key will locate the log entry from which the QSL Queue entry was created, and display it in the Main window's Log QSOs tab.

 

Each entry in the QSL Queue contains a QSL box. By default, each entry's box is checked, which enables the entry for QSL Queue operations. A QSL Queue entry whose QSL box is not checked will be ignored by all operations except clearing the QSL Queue. You can use the EnableAll and DisableAll function to quickly enable or disable all QSL Queue entries. Disabling a QSL Queue entry is useful when you're not yet ready to send a QSL card or label, perhaps because you expect to make additional QSOs with the station and want to print them all on a single card or label.

 

Click the QSL Queue panel's Clear button will remove each QSO from the QSL Queue:

 

QSLing with Paper: Printing QSL cards, QSL labels, Envelopes, and Address Labels from the QSL Queue

QSL cards can be printed either one card per page, or four cards per page, with dimensions you specify; a printer capable of handling card stock is recommended. Information to be printed on each card can be specified on the configuration window's QSL Cards tab; you can optionally specify a background image to be printed on each card. QSL cards are sorted in DXCC prefix order. When printed four cards per page, each page can be thought of as having four quadrants, with quadrant1 in the upper left, quadrant 2 in the upper right, quadrant 3 in the lower left, and quadrant4 in the lower right. DXKeeper places QSL cards into quadrants in a specific order that, if maintained, avoids the need to sort the final deck by DXCC prefix after the cards are separated with a paper cutter. To achieve this order, start with the cards in quadrant 1, then append the cards in quadrant 2, then quadrant 3, and finally those in quadrant 4. If the QSL Via item contains a valid callsign, its DXCC prefix will be used for sorting purposes.

Most printers cannot print right to an edge; each printer imposes a set of margins. If the QSL card  dimensions you specify will not fit within these margins or would produce a card that is too small to contain the minimum information, DXKeeper will so inform you. Your printer's margins are depicted in the Print Preview window as shaded areas. You can optionally direct DXKeeper to ignore the printer imposed margins; this could damage your printer, so do so at your own risk.

Single labels, two-column labels, and three-column labels can be printed with QSL information and with addresses; Dimensions of each can be specified on the configuration window's QSL Labels tab and Address Labels tab. On installation, DXKeeper is pre-configured to support 

You can specify QSL label dimensions in either inches or millimeters. QSL labels are also sorted in DXCC prefix order, starting with the top row of labels and proceeding down the page. As with QSL cards, If the QSL Via item contains a valid callsign, its DXCC prefix will be used for sorting purposes.

The Station Callsign printed on a QSL card or label is taken from the QSO's station callsign item, which should specify the callsign you used over the air.

Dates are printed on QSL cards and labels using a specified format

While a RST_Sent item can contain up to 8 characters, QSL cards, single labels, and 2-column labels only print the first 3 characters of the signal report; 3-column labels print all 8 characters of the signal report.

When QSLing via cards or labels, DXKeeper will by default confirm multiple QSOs with the same station on the same card or label if

If desired, you can restrict QSL cards or labels to confirm exactly one QSO -- uncheck the Confirm Multiple QSOs per QSL box

If you want outgoing cards or labels to bear the word "thanks!" if the QSO is already confirmed in LotW, then check the Set outgoing QSL? to "thanks!"... box.

If you want QSL cards to include a background image, select and enable an appropriate bitmap image file.

If you want QSL cards to include the QSL manager (from the QSO's Via item if this contains a valid callsign)  in the confirmation line, then check the Include QSL Mgr in confirmation box. An example of a confirmation line including a QSL manager is

confirming a 2X QSO with YV1DIG via FJ/AA6YQ

If you want single labels or 2-column labels to include the QSL manager (from the QSO's Via item if this contains a valid callsign)  in the confirmation line, then check the Include QSL Mgr in confirmation box. An example of a confirmation line including a QSL manager is

7O1NU confirms 2X QSO with AA6YQ via F6FNU

If you want 3-column labels to display the QSL manager (from the QSO's Via item if this contains a valid callsign) and the words 'pse QSL!' (unless every QSO on the card is confirmed, in which case the words 'tnx QSL!') along each label's bottom edge, then check the Include QSL Mgr & pse/tnx QSL box. To have every outgoing 3-column label display the words 'pse QSL!' unless all QSOs on the label are confirmed, enable the Outgoing QSLs request confirmation unless already confirmed option.

For QSLs to be sent via the QSL bureau, you can configure QSL cards, single labels, 2-wide labels, and 3-wide labels to include the designation [x buro] (where x is the DXCC prefix for the destination QSL bureau).

QSL substitution commands found in a QSO's QSL message item will be replaced before printing on QSL cards or labels. This allows you to personalize the QSL message with information about you, your QSO partner, your equipment, or the conditions.

Each QSL Queue entry's Sent Via item indicates whether the QSL should be sent via the QSL bureau, direct, or via EFT. You can change this routing. To print only cards or labels with a specified routing, check or uncheck the Include QSLs to be sent via the QSL Bureau, Include QSLs to be sent via Direct mail, and Include QSLs to be sent via Electronic File Transfer boxes.

You can select different printers to be used for printing QSL cards, labels, and envelopes - or perform all printing with the same printer.

If you are printing QSL cards, then 

If you are printing QSL labels, then 

If the previewed cards or labels are unsatisfactory, you can make corrections to settings on the QSL Configuration window's QSL Cards tab or QSL Labels tab and then repeat the Print QSL Cards or Print QSL Labels operation. If incorrect logged data other than callsign or begin time has been printed on any cards or labels, correct the erroneous logged data by double-clicking on a QSL Queue entry to display the associated QSO in the Main window, where you can correct the error and click the Log button. If a QSO has been logged with the wrong callsign or begin time, 

If you intend to print envelopes or address labels, you should verify that an address is available for each entry in the QSL Queue. Entries shown in red font are missing an address; to specify or modify the address of a station in the QSL queue, double-click its entry to display DXKeeper's QSL Editor window. When you click the QSL Editor's Save button, any changes you've made will update both the QSL Queue entry and the logged QSO. 

Click the Create Address File button on the Main window's QSL tab to generate a report showing the address for each station that will receive a QSL. This report can be used to double-check the addresses, and later to ensure that the correct card is placed in the correct envelope.

The Address via panel on the Main window's QSL tab determines whether addresses will be printed on envelopes, single labels, 2-column labels, or 3-column labels.

If you are printing addresses on envelopes, then

If you are printing addresses on labels, then

When you have completed the printing of all QSL cards, QSL labels, envelopes, and/or address labels, click the Update Log button on the Main window's QSL tab. For each entry in the QSL Queue, this function will locate the logged QSO from which it was generated and

The Self-addressed panel on the Main window's QSL tab provides a Print button that when clicked produces a batch of self-address envelopes, single labels, 2-column labels, or 3-column labels. Envelopes are addressed to the return address specified on the QSL Configuration window's Envelopes tab; labels are addressed to the return address specified on the QSL Configuration window's Address Labels tab. The Count box specifies the number of self-addressed envelopes or labels that will be printed.

When you receive a QSL card, you can use the Call filter to quickly locate the logged QSO; if the QSO parameters match, click the QSO panel's CFM button; this will set the logged QSO's QSL card QSL rcvd to Y and, if Optimize for Realtime QSO Entry is checked, set its QSL card QSL date rcvd to the current UTC date.

While reviewing your ARRL DXCC status report, you can also use the Call filter to quickly locate newly-verified QSOs, and then click the QSO panel's VFY button to set the QSL rcvd to V.

 

QSLing via eQSL.cc: uploading QSLs from the QSL Queue, synchronizing confirmed QSLs, and downloading eQSL images

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

To upload the contents of the QSL Queue to eQSL.cc

If you've specified a QTH Nickname, that QTH Nickname is displayed beneath the last date and time of upload; clicking this QTH Nickname will display the QSL Setup window's eQSL tab, where the QTH Nickname setting can be modified.

DXKeeper transmits the following information to eQSL.cc for each entry in the QSL Queue:

QSL substitution commands found in a QSO's QSL message item will be replaced before uploading to eQSL.cc. This allows you to personalize the QSL message with information about you, your QSO partner, your equipment, or the conditions.

If you have multiple station callsigns and multiple eQSL.cc  accounts, you can prevent the upload of QSOs whose station callsigns don't match the currently specified eQSL.cc username by checking the Don't upload QSOs whose station callsign isn't the specified Username box. You can optionally specify an eQSL.cc QTH Nickname to select a QTH in your eQSL.cc profile for each uploaded QSO, or you can specify that each QSO's myQTHID be used to as an eQSL.cc nickname to select a QTH in your eQSL.cc profile. If not needed, leave the QTH Nickname textbox empty.

Any uploaded QSO rejected by eQSL.cc as a duplicate is treated as if it had been uploaded successfully.

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

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,

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

You can now disconnect from the internet. 

Under certain circumstances, you may wish to manually download an eQSL.cc Inbox and direct Sync eQSL.cc QSLs 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:

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. 

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

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 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.

Clicking the 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.

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

Each QSO uploaded 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.

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.

To upload QSOs in the QSL Queue to LotW

The UTC date and time of your last LotW upload appears under the Upload to LotW button to remind you when you last invoked this function; this information is stored in the current log. The  LotW station location that will be used in uploading QSOs to LotW is displayed beneath the last date and time of upload; clicking this station location will display the QSL Setup window's LotW tab, where the LotW station location setting can be modified. The station callsign specified in the currently-selected LotW station location is displayed to its right.

After a successful upload to LotW, DXKeeper will perform the following for each enabled entry in the QSL Queue

QSLs 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. 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.

LotW generally processes successfully uploaded QSLs within an hour, unless a contest has recently been completed. After waiting an hour, 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

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

To synchronize your log with LotW  by downloading confirmations (QSLs) and matching them with logged QSOs,

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 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:

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

Right-clicking a QSO in the Log Page Display and selecting the Update from LotW menu item performs the 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 US state or Maidenhead gridsquare information.

Clicking the Update from LotW button on the Main window's QSL tab performs the 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.

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. 

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

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:

Each QSL is compared with its matching logged QSO. Information downloaded from 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 logged with QSO 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

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 int he 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.

When the Sync LotW QSLs function completes, DXKeeper displays a report showing

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 Log Page Display is filtered to show only QSOs confirmed via  LotW , and sorted 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.

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 your PC 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

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.

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:

  AA6YQ.mdb FJ-AA6YQ.mdb KP2-AA6YQ.mdb
Station callsigns contained in log's QSOs KC6IGZ, N6YBG, AA6YQ FJ/AA6YQ KP2/AA6YQ
Limit Sync operations to this station callsign   FJ/AA6YQ KP2/AA6YQ
Report unmatched QSLs as errors no yes yes

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.

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 

Incoming QSLs will match one or the other, depending upon the station callsign logged by the QSLing station. 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.

Note: Upload to LotW sends the following information for each QSL Queue entry:

QSL substitution commands found in a QSO's QSL message item will be replaced before uploading to LotW. This allows you to personalize the QSL message with information about you, your QSO partner, your equipment, or the conditions.

 

QSLing via ADIF or tab-delimited files: Generating QSL cards via an external application or service by way of the QSL Queue

While DXKeeper can generate QSL cards, their design is utilitarian, optimized for soliciting a confirmation at the lowest cost. There are applications that allow you to design more attractive QSL cards and print them with QSL information extracted from a file of QSO data in ADIF format:

There are also services like Global QSL that accept your uploaded QSO data in ADIF format, print QSL cards using a design you create, and distribute these cards via QSL bureaus. Setting the QSL kind to ADIF file allows you to generate QSL cards using such applications and services. You can also use mail merge techniques with applications like Microsoft Word to produce QSO cards; setting the QSL kind to tab-delimited file allows you to generate QSL cards using such applications. Options are provided to compensate for Global QSL's lack of compliance with ADIF

Each QSL Queue entry's Sent Via item indicates whether the QSL should be sent via the QSL bureau, direct, or via EFT. You can change this routing. To include only cards or labels with a specified routing in the generated file, check or uncheck the Include QSLs to be sent via the QSL Bureau, Include QSLs to be sent via Direct mail, and Include QSLs to be sent via Electronic File Transfer boxes.

To generate a file containing ADIF data for each entry in the QSL Queue

 The following replacements are made for each character in an exported tab-delimited field

DXKeeper stores the following ADIF information for each QSL Queue entry:

QSL substitution commands in a QSO's QSL message item will be replaced before being placed in the ADIF file. This allows you to personalize the QSL message with information about you, your QSO partner, your equipment, or the conditions.

To generate a file containing tab-delimited data for each entry in the QSL Queue,

 DXKeeper stores the following tab-delimited information in the following order for each QSL Queue entry:

QSL substitution commands found in a QSO's QSL message item will be replaced before being placed in the tab-delimited file. This allows you to personalize the QSL message with information about you, your QSO partner, your equipment, or the conditions.

If you are using a service like Global QSL, be aware that some QSOs may be rejected because there is no destination QSL bureau. Upload the generated ADIF file to the service, and note any QSOs not accepted. For each such QSO, uncheck its QSL Queue entry's QSL box before proceeding.

After the ADIF or tab-delimited file has been created and processed, click the Update Log button on the Main window's QSL tab. This will do following for each successfully-processed entry in the QSL Queue:

Any unsuccessfully-processed entries - denoted by an unchecked QSL box - will remain in the QSL Queue. Remove these by clearing the QSL Queue; their logged QSOs will continue to indicate that no outgoing QSL has been generate, so you can use an alternative QSLing strategy (e.g. printing cards or labels for direct mail).

When you receive a QSL card, you can use the Call filter to quickly locate the logged QSO; if the QSO parameters match, click the QSO panel's CFM button; this will set the logged QSO's QSL card QSL rcvd to Y and, if Optimize for Realtime QSO Entry is checked, its QSL card QSL date rcvd to the current UTC date.

While reviewing your ARRL DXCC status report, you can also use the Call filter to quickly locate newly-verified QSOs, and then click the QSO panel's VFY button to set the QSL rcvd to V.

 

Confirming Reports from Shortwave Listeners (SWLs)

DXKeeper can generate QSL cards or labels that confirm reports from SWLs. To confirm such a report for a QSO, first, set the QSL Via panel to Cards, 2-column labels, or 3-column labels as desired. Then right-click on the QSO in the Log Page Display; in the popup menu, choose the Add SWL entry to QSL Queue option. DXKeeper will display a small window that prompts you for the SWL station's callsign; after you enter this callsign and click the window's OK button, an entry will be added to the QSL Queue. Such entries will generate QSL cards or labels when you invoke the Print QSL Cards or Print QSL Labels functions, as described above. Note that the QSL Queue can simultaneously contain entries that generate confirmations for QSO partners and entries that generate confirmations for SWLs.

 

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

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

Command

Replacement

<band> the QSO's band
<buro> if the QSO's QSL_VIA is set to 'B' (bureau), [x buro] where x is the destination entity's DXCC prefix
<callsign> the callsign of the station specified in the QSO
<city>

the QTH's city

<contestid> the contest identifier
<country>

the QTH's country

<county>

the QTH's county

<cq>

the QTH's CQ zone

<destination> the QSL manager's callsign if one is specified, otherwise the callsign of the station specified in the QSO
<distance> if the QSO's specifies a distance item, the replacement is the word "DX: " followed by the distance in miles or kilometers followed by either "mi" or "km"
<dx> if the QSO's specifies a distance item, the replacement is the distance in miles or kilometers followed by either "mi" or "km"
<dxccentity> the station's DXCC entity
<email> your email address (associated with the QTH)
<grid>

if the QTH's grid square is specified, then the replacement is the word "grid:" followed by the specified grid square; otherwise, the replacement is empty

<iota>

if the QTH's Iota designator is specified, then the replacement is the specified Iota designator; otherwise, the replacement is empty

<itu>

the QTH's ITU zone

<latitude>

the QTH's latitude in degrees and minutes

<latitudewsecs> the QTH's latitude in degrees, minutes, and seconds
<longitude>

the QTH's longitude in degrees and minutes

<longitudewsecs> the QTH's longitude in degrees, minutes, and seconds
<meteor shower> meteor shower name
<mode> the QSO's mode
<mycall> station callsign used during the QSO
<myqthid> the myQTH identifier recorded with the QSO
<name> the station's operator's name
<opcall> callsign of the station operator
<opname> your name (associated with the QTH)
<ownercall> callsign of the station owner
<postalcode>

the QTH's postal code

<propmode> if the QSO specifies a propagation mode, then the replacement is the word "prop: " followed by the propagation mode; otherwise, the replacement is empty
<qth> the station's QTH (up to 30 characters)
<rig> your station equipment (associated with the QTH)
<rstrcvd> the signal report you gave your QSO partner
<rxband> if the QSO specifies a satellite, then the replacement is the phrase "rx band: " followed by the receive band; otherwise, the replacement is empty
<rxfreq> if the QSO specifies a satellite, then the replacement is the phrase "rx freq: " followed by the receive frequency; otherwise, the replacement is empty
<satconfirm> if the QSO specifies a satellite, then the replacement is the phrase "via Satellite (" followed by the satellite name followed by ")"; otherwise, the replacement is empty
<satmode> if the QSO specifies a satellite, then the replacement is the phrase "sat mode: " followed by the satellite mode; otherwise, the replacement is empty
<satname> if the QSO specifies a satellite, then the replacement is the word "sat: " followed by the satellite name; otherwise, the replacement is empty
<SFI_A_K> if the QSO specifies a solar flux, then the replacement is the phrase "SFI: sfi, A: a, K: k"  where sfi, a, and k are the solar flux, a-index, and k-index logged with the QSO
<sig> your special interest group name (associated with the QTH)
<signinfo> your special interest group information (associated with the QTH)
<srx> the receive serial number or exchange logged with the QSO
<srx_info> the QSO's receive exchange info
<state>

the QTH's state

<streetaddress>

the QTH's street address

<stx> the transmit serial number or exchange logged with the QSO
<stx_info> the QSO's transmit exchange info
<txpower> your transmitter's power
<userdefined_0> the QSO's user-defined item #0
<userdefined_1> the QSO's user-defined item #1
<userdefined_2> the QSO's user-defined item #2
<userdefined_3> the QSO's user-defined item #3
<userdefined_4> the QSO's user-defined item #4
<userdefined_5> the QSO's user-defined item #5
<userdefined_6> the QSO's user-defined item #6
<userdefined_7> the QSO's user-defined item #7
<via>

if the QSO specifies a QSL manager, then the replacement is the word "via" followed by the QSL manager's callsign; otherwise, the replacement is empty

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.