Logging New QSOs with the Capture window

DXKeeper Online Help Contents

To facilitate rapid real-time logging with minimum screen space consumption, DXKeeper provides a QSO Capture window, activated by clicking the Capture button located on the Log QSOs tab. The QSO Capture Window records 38 items, all but four of which (call, DXCC, tx frequency, and mode) are optional. By dragging the Capture window's lower border up or down, the Capture window can be configured to display from as few as two items to all items.

Clicking the Lookup button,  or striking the Enter key in the Call textbox, or striking the Tab key in the Call textbox results in the following actions:

If a callsign is found to be a known participant of LotW but not an Authenticity-Guaranteed member of eQSL.cc, the callsign's background color is set to yellow. If a callsign is found to be an Authenticity-Guaranteed member of eQSL.cc but not a known participant of LotW, the callsign's background color is set to pink . If a callsign is found to be a known participant of LotW and an Authenticity-Guaranteed member of eQSL.cc, the callsign's background color is set to cyan (light blue). If SpotCollector is installed, however, the background colors specified on the Spot Database Display tab of SpotCollector's Configuration window - if not too dark - are used in place of yellow, pink, and cyan. The eQSL AG and LotW databases can be installed via the Databases tab of DXView's Configuration window.

Allowing the mouse cursor to linger over the DXCC item when it contains a DXCC entity prefix will prompt DXKeeper to display a popup window containing the full name of the DXCC entity. Similarly, allowing the mouse cursor to linger over a State or Province item will prompt DXKeeper to display a popup window containing the full name of the state or province.

If the first letter of the callsign you enter is an exclamation point, DXKeeper assumes that you are logging a CQ, an unsuccessful call, a test, or some other transmission that you wish to record but does not represent a QSO. Such log entries are not assigned a DXCC prefix, do not initiate a Callbook database lookup, and are not included in award tracking statistics.

Double-clicking or striking the Enter key in the grid textbox updates DXView's display to show the specified grid square as its current position. Depressing the CTRL key while double-clicking the Grid textbox updates DXView's display and rotates the antenna to the short-path heading; depressing the ALT key while double-clicking the Grid textbox updates DXView's display and rotates the antenna to the long-path heading.

Clicking the Begin button, entering a received signal report in the RST rcvd field with the Set QSO start when RST Rcvd box is checked, striking Alt-B in any Capture window field, or striking CTRL-B in any Capture window field

Note that if both the Initialize RST Items and Set QSO start when RST Rcvd options are enabled, the QSO's  start time will be set when you click the Lookup button,  strike the Enter or Tab key in the Call textbox, or take an action in another application that causes DXKeeper to capture a new Callsign. This may significantly precede the actual start of the QSO, preventing a match within QSLing services like eQSL or LotW.

Clicking the End button or striking CTRL-E in any Capture window item

Checking the QSL Requested box indicates that a QSL card or label should be sent and a confirmation requested. If logged, the QSO's QSL Sent and QSL Rcvd items will be set to 'R' (for requested); when you later run the QSL Workflow, the Add Requested button will automatically generate a QSL card or label for this QSO; printed cards and 2-column labels will bear a "please!" in their QSL? column.

Checking the use bureau box indicates that the QSL should be sent via the QSL bureau. If logged, the QSO's QSL Sent Via item will be set to 'B'.

Checking the LotW member box indicates that the callsign participates in the ARRL's Logbook of the World. If logged, the QSO's LotW Member item will be set to 'Y'.

Checking the eQSL.cc member box indicates that the callsign is an Authenticity Guaranteed member of eQSL.cc . If logged, the QSO's eQSL.cc Member item will be set to 'A'.

Checking or unchecking the contest-mode box enables or disables Contest-mode.

Double-clicking the RST_Sent or RST_Rcvd item with a Mode selected will set the item to 59 (if the selected mode is a phone mode) or 599 (if the selected mode is not a phone mode).

Double-clicking the QSL Via item invokes the Address Editor .

Double-clicking the Comment item will invoke a Comment editor window  that makes it easier to enter or modify lengthy content; click the Save button to preserve your changes, or the Cancel button to abandon them.

Double-clicking an item's label will filter the Log Page Display to show all QSOs whose item matches the value in the Capture window.  If the Capture window's IOTA item contains OC-005, for example, double-clicking the IOTA label will filter the Log Page Display to show all QSOs whose IOTA item is OC-005.

If an item has a default value, Ctrl-double-clicking that item's label will display the Configuration window and place the mouse cursor in the default value,

Uncapitalized first letters of each word entered into the Name or QTH items will be automatically capitalized unless the word contains a capitalized letter.

Striking the Enter key in the QTH item initiates a word-by-word inspection of the QTH item.

Clicking the Clear button with Contest-mode unchecked requests confirmation (if Prompt on Capture Clear is enabled) and then clears all Capture items, presents the Begin button, clears the Log Page Display filter, and selects the last QSO in the Log Page Display; if Contest-mode checked, the TX# item is not cleared.

Clicking the Log button 

Note that striking CTRL-<enter> or CTRL-L in any Capture Window item is equivalent to clicking the Log button.

If the Log Page Display is filtered to show previous QSOs with the station in the Call item, the number of previous QSOs is parenthetically appended to the Call item's label, whether or not the main log window is visible. Clicking on the Call item's label will display the main log window, should it be minimized. Information about the most recent QSO -- date, time, frequency, mode, and QSL status -- is displayed in the Capture window is appropriately resized; click the window maximize button on the right side of the title bar to expand the Capture window enough to show all information.

With Contest Mode disabled, a  Log Page Display entry will be rendered in red font if its Callsign, Band, and Mode match those in the Capture window; this can help avoid duplicate QSOs; with Contest Mode enabled, a  Log Page Display entry will be rendered in red font if its Callsign, Band, Mode and Contest ID match those in the Capture window.

If required items are missing or contain invalid values, clicking the Log button highlights the labels of these items in red, but does not enter the QSO into the current log. Frequencies not falling within a defined band are considered invalid. Callsign validity checking can be enabled or disabled via the Flag Invalid Callsigns setting. If a Capture item's data exceeds its specified maximum length, its label will be highlighted in red and the Log button will not enter the QSO into the current log. 

You can include substitution commands in the QSL msg item to include information determined by your current location.

Uncapitalized first letters of each word entered into the Name or QTH items will be automatically capitalized unless the word contains a capitalized letter.

To allow operation without removing one's hands from the keyboard, DXKeeper provides keyboard shortcuts for navigating among the Capture Window's items.

Clicking in the call box or tx freq box with the middle mouse button will direct Commander to activate its Bandspread window.

While DXKeeper can log a receive frequency (distinct from a transmit frequency) for each QSO, the Capture window does not provide a means of recording this information. For cross-band QSOs -- Satellite QSOs, for example -- use the Main window for logging.

If SpotCollector is running and has been configured to generate cluster spots, then clicking the Spot button will use the Capture window's Call, TX frequency, and Mode items to generate a DX spot; if the Mode is not CW or SSB, it will be included as a spot note. If the Spot split frequency setting is enabled, outgoing spot notes will include the difference between the Capture window's TX and RX  frequencies unless that difference exceeds 9.9 KHz, in which case the full TX frequency will be included. If the band is 6m or above and a gridsquare has been captured, it will also be included as a spot note; if the operator's gridsquare is specified in the current myQTH, then the spot note will be of the form "DX_Grid > Operator_Grid".  

If WinWarbler is running and Capture window F-Keys via WW is checked, then striking the function keys F5 through F12 in a Capture window textbox will invoke a WinWarbler macro, with Shift key and Alt key modifiers functioning as they would within WinWarbler. Striking the Esc key in a Capture window textbox will abort any active WinWarbler transmission.


Logging Information Required for Award Tracking

To track progress towards awards like WAS, USA-CA, RDA, WAJA, JCC, JCG, and AJA, DXKeeper provides items in its Capture window that let you record a callsign's Primary Administrative Entity and its Secondary Administrative Entity. Some DXCC entities formally define a set of Primary Administrative Subdivisions, e.g. States in the United States, Oblasts in Russia, and Prefectures in Japan; unique abbreviations or codes are used to identify these primary subdivisions. For such entities, DXKeeper provides an appropriately-labeled (e.g. state, oblast, prefecture) selector lets you choose from among the valid codes; if you click the ? button to the left of this selector, DXKeeper's Capture Administrative Subdivision Selector window will appear, which provides a cross-reference between code or abbreviation and full name, and lets you choose a primary subdivision by clicking in either the window's Code or Name selector. 

Some of the DXCC entities that define a set of Primary Administrative Subdivisions formally define a set of Secondary Administrative Subdivisions for each of their Primary Administrative Subdivision, e.g. Counties in the United States, Districts in Russia, and Cities and Guns in Japan; unique abbreviations or codes are used to identify these secondary subdivisions. For such entities, DXKeeper provides an appropriately-labeled (e.g. county, district, city/gun) selector lets you choose from among the valid codes; if you click the ? button to the left of this selector, DXKeeper's Capture Administrative Subdivision Selector window will appear, which lets you choose a secondary subdivision by clicking in either the window's Code or Name selector. 

For entities that do not define Primary or Secondary Subdivisions, DXKeeper provides pri sub and sec sub textboxes with which any subdivision name can be recorded; you could use this to capture a subdivision name for QSO with a country that does not formally define its subdivisions. 

The Capture window also provides  region and DOK items to record entity-specific information required for certain awards.

For a summary of what information to record in what item for each supported award, see the table here.