- 1 Introduction
- 2 Screen Layout
- 3 Setup & Configuration
- 3.1 Appearance
- 3.2 Backups
- 3.3 Bands
- 3.4 Callsign Lookups
- 3.5 ClubLog
- 3.6 DX Cluster
- 3.7 eQSL.cc
- 3.8 Favorites
- 3.9 HRDLog.net
- 3.10 Modes
- 3.11 My Station
- 3.12 Network Server
- 3.13 QRZ.com
- 3.14 QSO Forwarding
- 3.15 Radio Pane
- 3.16 Rotator
- 3.17 RST Options
- 3.18 Sharing
- 3.19 Tuning Dial
- 4 Managing Logbook Databases
- 5 Creating & Managing QSOs
- 5.1 Add Logbook Entry (ALE)
- 5.1.1 Menu Bar
- 5.1.2 Logbook Tab
- 5.1.3 Worked Tab
- 5.1.4 Country Tab
- 5.1.5 Contact Tab
- 5.1.6 Location Tab
- 5.1.7 IOTA Tab
- 5.1.8 Antenna/Satellite Tab
- 5.1.9 Award Tab
- 5.1.10 Contest Tab
- 5.1.11 Custom Tab
- 5.1.12 My Station Tab
- 5.1.13 Propagation Tab
- 5.1.14 QSL, eQSL.cc, and LOTW Tabs
- 5.1.15 Logbook Search
- 5.2 Bulk Editing QSOs
- 5.3 Importing Log Files
- 5.4 Exporting Log Files
- 5.5 Backup and Restore
- 5.6 Country Data
- 5.7 External Log Interfaces
- 5.1 Add Logbook Entry (ALE)
- 6 DX Cluster
- 7 Awards Tracking
It is time to be impressed! Ham Radio Deluxe Logbook is probably the best logbook program and it keeps getting better. As you will see later, the awards tracking capability is second to none.
In the Logbook section, we'll begin with describing what the operator will see on the screen. We'll follow with how to fully configure Logbook. Then the feature and functionality will be described.
In this section, the default layout of the Logbook screen will be described so that the Operator is familiar with the application's layout. The configuration and use of these features will be described later.
- Application Ribbon - This provides an easy way to change layouts, flip between Ham Radio Deluxe applications, Main and Sub band tuning sliders, Add Logbook Entry, databases Manager, and configuration. The ribbon will show the user's call and the main and sub band VFO readings.
- Left Pane - This has three functions. Favorites is a quick way to access saved frequencies for quick band and mode changes. Lookup pane provides a quick way to invoke the callsign lookup function and get information based on what is in the operator's logbook or lookup source, details about the operator (by callsign), country information. Radio Pane provides a quick way to access rig control features without flipping over to the Rig Control application.
- Audio Recorder - This gives the operator the ability to record audio from the radio's AF source.
- Logbook - This tab gives the user the ability to view the recent contents of the log.
- DX Cluster - This shows DX spotter information from the DX spotting network.
- Clock - This shows the current time.
- Grayline Map - This shows the grayline map, with regards to the operator's location.
- Band Map - This shows all collected spots for a selected band.
Setup & Configuration
You will need to go through a few steps to configure logbook.
The setup options for Logbook can be found under the Tools > Configure menu. This section of this manual will review each of these items in the Configure menu.
There are three options for changing the appearance of Logbook.
- In this tab, it is possible to configure the application's Font (style and size), colors, and default Time.
- It is worth experimenting with these. For example, it is possible to alternate the colors in the logbook pane, making it easier to read. Those who wish to change the default time between UTC (GMT) and Local time can do so here.
- In this tab, it is possible to configure the background and text color of the frequency display, as well as the font style of the frequency.
- In this tab, it is possible to configure the colors of the face, markings, and rim of the rotator display.
IMPORTANT: This is one of the most important sections of this manual. Failure to properly configure Logbook to automatically create backup copies of your log could lead to very unfortunate circumstances of lost data - up to and including your entire log.
- There are a few different backup types as options. All these backups are stored in a file referred to as an "XML file." The main thing to know about this XML file is that it is a file type that has been optimized to backup or restore the Logbook database. These options will be discussed first, followed by strategies regarding the storage type and location.
- Backup file is an option that creates a stand-alone backup copy of the log. This is a very common method. But because these files are not compressed, they can take up a lot of disk space if old copies are not managed.
- Archives is an option that comes in two styles.
- Compress to folder is an option that uses standard Windows file compression techniques to reduce the size of the backup and put it in a specific folder.
- Add to Archive is an option that places an uncompressed copy of the file into a compressed folder (known as a Windows archive folder).
- In all, it is possible to place a backup of the logbook in five different file locations. It is our recommendation that all of them are used. Further, given that there are so many free cloud storage options available, it is possible to place a backup copy of the log on Dropbox, Google Drive, Microsoft OneDrive, Box, Apple iCloud... and others. These are generally free services and far more secure than any disk attached to your computer.
- The following video on our YouTube channel demonstrates how to configure backup options "in-the-cloud."
- Backup Databases configures the timing or events that cause a backup to be created automatically. The choices are:
- On opening - this causes a backup to be created when the Logbook application launches (In our opinion, this is the least desirable time to make a backup.)
- On closing - this causes a backup to be created when the Logbook application closes (In our opinion, this is highly desirable.)
- Every x changes - this is useful when the operator desires to create a backup after adding a certain number of QSOs into the logbook. There are a number of standard options to chose from.
- Every x hours - this is useful when the operator desires to let Logbook create the backup on a timed basis.
- Because these files are created frequently, it is recommended that a strategy be used for deleting very old backup copies to avoid taking up excessive storage space.
- Guidance about restoring a logbook from backup will be discussed in a different section of this manual.
This is where it is possible to add custom band ranges. This may be useful for SWL or MARS operation. It is recommended that the standard bands included with Logbook remain unchanged.
- To add a band, click on the Add button and the following dialog box appears:
- Simply add the band in the format of "75m" in the first box. The ADIF field refers to the standard name given to the modes in the Amateur Data Interchange Format (www.adif.org). A comment is optional.
- Bands can be shared and imported using the Load function.
This is a very useful and popular option. It has many choices (methods) for free and subscription-based access to callsign databases. This feature enables users to lookup a callsign in various callsign databases to obtain information about that callsign's owner such as - name, address/QTH, email address, locator/grid, age, ham club membership, CQ and ITU zones.
Enabling Callsign Lookup Methods
- NOTE: It's important to understand the way this feature works.
- The Enabled (selected) methods are shown on the left. The Disabled (unselected) methods are on the right.
- The Enabled methods work in the order in which they are displayed. Using the example above as a point of reference, when the Add Logbook Entry (ALE) form is displayed and a callsign is entered in the ALE, the user may then invoke the callsign lookup process by using the TAB key or by clicking the Lookup button. Then, the process would work as follows:
- The callsign will be looked up in the active logbook. If that call exists in the log, all empty fields will be populated with the data from the data from that QSO.
- Regardless if found by a previous method, the callsign will then be looked up in QRZ.com. All remaining empty fields will be populated with the data from that QSO.
- Regardless if found by a previous method, the callsign will then be looked up in the HRD Country File. All remaining empty fields will be populated with the data from that QSO. (Though the HRD Country List will only populate the Country field.)
- This process continues through as many selected methods that are included.
- CAVEAT: The HRD Country File includes a list of unique calls in a Unique Callsign Database (UCSDB). That information takes priority over all the enabled methods by design.
- RECOMMENDATION: We strongly recommend using the logbook as the first enabled method and the HRD Country List as the last enabled method. In other words - use them in the order from most specific content to less specific content.
- Using the logbook as the first enabled method enables the log to become a de facto UCSDB. Once the user gets a callsign correctly entered into their log, that same information will be used for subsequent callsign lookups. This is helpful for cases where a DXpedition announces a callsign on the first day of operation and is active before the call is available in the UCSDB or on QRZ.com.
- Because the HRD Country List will only populate the Country field based on the callsign's prefix, it should be used as a last resort. All other sources of information will be more specific and accurate.
- This form is used for (a) entering the username and password for enabled methods, (b) configuring Logbook to use data from a CD, and (c) testing these methods.
- The entry of username and password for these methods is self-explanatory.
- Data from a CD can be used from the CDROM drive or the data can be copied to a local disk and specified there for faster access.
- The testing mechanism is a very useful tool for investigating cases where the callsign lookup is either not working or rendering odd results. Simply put a call into the field and click Lookup and the enabled methods will be used to bring back an XML file with the data in it. That information can be used to investigate the results.
- Club Log users enter their username and password in this form. Users can choose to upload QSOs as they are added to the log.
- NOTE: This is for upload only. There is no download function in Club Log.
There are 11 tabs that are useful in configuring the DX cluster options.
A DX cluster is a server, usually on the Internet, where hams around the world participate in a form of "crowd-sourcing." That is - hams around the world share information about where they hear active DX stations on-the-air with other hams connected to this network. Using the functionality in Logbook, the operator can select a DX spot and the radio will automatically tune to that frequency and mode, the rotator will direct the antenna in the direction of the DX station, callsign lookup features populate information about the DX station's licensee, and the computers date and time are populated in the QSO. All the operator needs to do is work the station, save the QSO, and move on to the next one.
The first step in using the DX cluster feature is to configure the connection.
- This tab provides a list of DX cluster nodes around the world.
- NOTE: We recommend using the WA9PIE-2 node because it has the most complete country data that is automatically updated and it has the best uptime availability of any DX cluster node in the world. WA9PIE-2 is normally connected to as many as 30 peer cluster nodes around the world. This enables WA9PIE-2 to provide the most complete list of spots to the operator without the need to surf around to other cluster nodes.
- In the upper left, the user can select:
- Connect on startup - this makes the DX cluster connection when Logbook starts
- Reconnect if connection lost - this causes Logbook to automatically attempt a reconnect, if the connection to the cluster node is lost (generally due to local network connectivity issues)
- Reset Spots on Connect" - this option provides a choice for whether or not the list of spots is discarded when a connection is made to a different DX cluster node. This is useful when the operator desires to collect some spots from a standard DX cluster node, then also collect some spots from a skimmer node, and display both or clear them.
- Operators can also add a DX cluster node by clicking the Add button and then entering a Title, (IP) Address (or DNS name), an IP port, and a username and password where applicable.
- This tab provides the ability to change the fonts and row colors in the DX cluster pane.
The layout options are a very important component of the DX cluster pane. This enables the operator to select the fields that will be included as columns in the DX cluster display.
- The left hand side of this tab shows the available information fields that can be included as columns in the DX cluster display. The right hand side shows the selected fields that will be included in the DX cluster display.
- The selected fields can be arranged in the display by using the up/down buttons above the selected fields.
- NOTE: The following guidelines define the source of the data that is being displayed.
- Fields that begin with "Spot" display data just as it was received by the DX cluster node without modification. Logbook is not the source for this information.
- Fields that begin with "HRD" display data that is derived by Logbook, based on data in the DX spot and information available within Logbook. The DX cluster is not the direct source for this information.
- Fields that begin with "WSI" provide an indication about whether that country or station has been worked or confirmed in the past. (WSI, or Worked Status Indicators, will be explained in more detail in a section to follow.)
- Fields that begin with "Member" provide information about whether or not that station is known to participate in LOTW or eQSL. (QSL Member will be explained in more detail in a section to follow.)
- Fields that begin with "Worked" displays information from the log regarding what bands or modes the spotted station's country has been worked in the past.
- There are lots of options here for obtaining rich content from the DX cluster network and displaying it so the operator can make decisions in real-time about what DX to chase and what pile-ups to jump into.
The Selection tab defines the behavior of Logbook when DX spots are selected from the DX cluster pane.
Selecting a Spot
- There are two choices for mouse click behavior in DX cluster.
- When Single-click is selected, Logbook will (a) invoke the callsign lookup for the Lookup Pane (b) populate the open ALE with information about that spot, and (c) tune the radio to the frequency and mode of the spot, based on the options selected in the lower right of this dialog box when the operator clicks once on a DX spot.
- When Double-click is selected, Logbook will (a) invoke the callsign lookup for the Lookup Pane (b) populate the open ALE with information about that spot, and (c) tune the radio to the frequency and mode of the spot, based on the options selected in the lower right of this dialog box when the operator double-clicks once on a DX spot. With Double-click selected, a single-click will only invoke the callsign lookup for the Lookup Pane.
- NOTE: We recommend using the "Double-click" because this enables the operator to use a single-click to quickly populate the Lookup Pane.
- This option defines whether or not Logbook is allows to open multiple ALE windows.
Spider and CC Cluster Options
- This is a very important, but often over-looked, feature.
- DX cluster nodes have the ability to filter spots before they are sent to you. This is a good idea, given that there's not a real good reason to receive 160m spots from Greece at 3pm in Chicago. So operators can setup DX cluster filters - on the DX cluster node itself (not within Logbook) - keep reduce the "noise" of irrelevant spots. For DX Spider and CC cluster nodes, the command "sh/dx" sends the first "lot" of spots (quantity specified in the Connection tab) unfiltered. The "sh/mydx" causes the initial "lot" of spots to honor the filter options that the operator has set directly on the DX cluster node. Given that - in the absence of filters - these two commands have the exact same behavior, we strongly recommend using the "sh/mydx" option.
- Region is where you select your ITU region. This invokes the appropriate "band plan" for your location.
- The option boxes on the right enable you to turn on or off the automatic rig tuning for frequency, mode, and QSX (and reset split, which are strongly recommended except for DX station).
- "Limit Comment to 30 Letters" causes the comment field in the spot to be truncated at 30 characters.
NOTE: Before continuing, it's important to distinguish the difference between "server-side" filters and "client-side" filters.
- "Server-side" filters are created by the operator, outside of Logbook, on the DX cluster node itself. These filters prevent spots from being sent to Logbook. These are most useful when the operator desires prevent spots from a geographically irrelevant part of the world to come to Logbook. These types of filters will not be discussed in this manual. The following resources are online and available to explain "server-side" filters in more detail:
- DX Spider Filtering Manual: http://wiki.dxcluster.org/index.php/DXSpider_Filtering_Manual (including WA9PIE-2)
- CC Cluster Filtering Manual: http://bcdxc.org/ve7cc/ccc/CCC_Commands.htm
- AR Cluster Filtering Manaul: http://www.73.ru/help/cluster/ArcFilters.htm
- "Client-side" filters; The spot filters in Logbook are "client side" filters. They work by "hiding" spots that have been received from the DX cluster node (server) into the DX cluster pane in Logbook. This guide will focus on how these filters work in Logbook.
The Spot Filters tab enables the operator to create filters for the data being delivered to the DX Cluster window (ie. after the application of server‐side filters). These filters are displayed in the dropdown menu in the DX Cluster window.
- Logbook contains the most common filters. Operators can create additional filters on their own using default filters as their guide.
- One useful filter to create is a filter that combines HF frequencies with 6m (given that many modern HF rigs include 6m). To create this one either click Add or select the HF filter and Copy, then Modify:
- Name the filter "HF + 6m", enter the "Freq min" and "Freq max" values (in MHz) of 1.800 and 54.000. Set the "Max entries" to a desirable number. Then click "Ok".
- The Up/Down buttons enable the operator to arrange them in the desired order in the dropdown list (which will be covered in more detail in the DX cluster section of this guide):
WSI stands for "Worked Status Indicators" and it is a very important tool for DX award-seekers. This feature was dramatically improved over the Ham Radio Deluxe 5.x versions. The WSI will now indicate whether the country has been worked at all, worked - but not confirmed, or worked - and confirmed. Using WSI properly will absolutely accelerate your progress in the DXCC awards program.
There is also a WSI that will indicate whether or not the specific callsign ("station") has been previously added to your log.
- As indicated in the reference information in the WSI tab above:
- Station (callsign)
- The Light Pole option allows operators who have connected a light pole to their computer to use it to indicate these same colors for incoming spots.
- "User ONLY open logbook for WSI" causes the active logbook to be the only database queried for WSI.
- On the right hand side of the WSI tab, it is possible to configure the WSI to color-code the rows in the DX cluster for needed bands and modes. It should be noted, however, that (a) the colors may be difficult for those who have color-blindness issues and (b) the granularity of the colors does not provide as much information as the symbols on the left. Use sparingly.
- WSI examples will be discussed in the DX cluster section of this guide.
The operator can setup alarms that will alert them by E-Mail (including a text message to a cellphone), Text to Speech, or with the Lightpole.
- The example above shows how to create a number of alarms for needed countries and zones. To build an alarm, click Add to bring up the following Add/Modify Alarm Definition dialog box.
- As an example, we'll build an alarm for a callsign that will be operating from Kerguelen.
- Give the alarm a name in the Title field, we'll use "Kerguelen"
- Enter the specific callsign we want an alarm for in the Callsign field.
- Enter the interval in minutes for which alarms can be sent.
- Select the delivery options from the Options below
- Click on the box to the left of "Enable"
- Then click "OK"
- The new alarm is now active.
This tab enables the operator to configure Logbook to send alerts via email (per the alarms enabled in the Alarms tab).
- There are a number of pre-populated options for sending email. They include - AOL, Gmail, Hotmail, Yahoo!, MSN, Lycos, Mail.com, and Netscape. The dropdown box populates the required information.
- NOTE: If using Gmail, Google requires that you change a setting in your email account to allow "Access for less secure apps". Google this phrase for additional information.
- You will need to enter the username and password for your selected email account in the fields provided.
- Add your email address into the "Outgoing e-mail address (from)" field.
- Add your destination email address in the "Outgoing e-mail address (to)"
- TIP: It is possible to send directly as a text message to your smartphone. For example, Verizon Wireless smartphones would be addressed at <your phone number>@vzwpix.com. Check your carrier for your specific details.
- You can test this by clicking the "Send Test" button.
- Click "OK" to complete the setup.
This table enables the operator to configure speech alarms from your computer speakers.
- Select the desired options and click "Speak" to test them.
When viewing the DX cluster, it's desirable to know whether the spotted station participates in Logbook of the World or eQSL (explained further in the DX cluster section of this user guide).
- The eQSL and LOTW import URL fields are shown with Reset buttons.
- NOTE: We strongly recommend that you do not change these URLs unless instructed to do so by HRD Software, LLC. In case they are accidentally changed, the Reset button will set them back to their original URLs.
- The two rows show the number of callsigns in the eQSL and LOTW files that have been downloaded.
- The Update button forces an immediate update.
- NOTE: We recommend using both the eQSL and LOTW boxes for "Auto" and that you do not check the "Ask before doing automatic updates" box. This will ensure that Logbook will check for updates each time you launch Logbook without being prompted.
This tap provides information about the Locator (gridsquare) and Region with a display on the Greyline map for reference.
- NOTE: It is strongly recommended that this page be used only for reference. Changes to Locator (gridsquare) are best made on the "My Station" form.
Users can check the box to have each QSO uploaded automatically or choose to upload QSOs as they are added to the log.
eQSL users enter their username and password in this form.
The "Nickname" field must be populated and should match the target nickname in eQSL ("nicknames" are generally equivalent to station locations. You set this up in eQSL.) The upload process will fail if they don't match.
The operator can setup frequently visited frequencies and modes as Favorites".
HRDLog users enter their username and password in this form. They can choose to upload QSOs as they are added to the log.
- NOTE: This is for upload only. There is no download function in HRDLog.
- The On Air function enables Logbook to report your frequency, mode, and radio for display on HRDLog.net in real-time.
This is where it is possible to add custom modes. This may be useful when new modes are created before we can update them in the software. Otherwise, it is recommended that the standard bands included with Logbook remain unchanged.
- To add a band, click on the Add button and the following dialog box appears:
- Simply add the mode in the format of "FT8" in the first box. The ADIF field refers to the standard name given to the modes in the Amateur Data Interchange Format (www.adif.org). A comment is optional.
- Modes can be shared and imported using the Load function.
If you have not already set up the necessary information within my station you will need to do that now. This will prove to be critical later so best do it now.
- 1. From within Logbook select from the Tools menu, Tools > Configure > My Station.
- 2. Information in the My Station screen is used by Ham Radio Deluxe Logbook
- Note: If you have already set up the DM-780 portion of the suite, this screen should be populated with the required information and you can just close it out and continue with the set up.
My Station Set Up
Ham Radio Deluxe allows you to set up multiple QTH locations. This allows you to have a Home location as well as other locations such as a vacation home or favorite portable locations.
If you haven’t already set up the My Station data, in the Description field you see the word HOME for a profile of your Home QTH. This generates your main location. Then go ahead and fill in all the rest of the information for this location. Please note which fields are required if you use one of the DX Clusters.
Most of the fields are self-explanatory. A couple of the fields do need a little explanation. The field SIG stands for Special Interest Group. This could be a club or any organization you belong to. The SIG Info field could be a website address for a group. You could leave these fields blank if you like.
Another spot you might need help is once you enter your Locator, for example EN36QR, if you hit the little arrow that points downward, that will automatically fill in your Latitude and Longitude fields.
THIS SECTION NEEDS UPDATING
Network Server is the feature in the application that allows other programs to make a connection to HRD Logbook. Normally, it is recommended to leave these settings as-is to enable DM-780 to connect to Logbook without issues.
- Autostart causes the server to be active when HRD Logbook is running (default is checked).
- Same PC connections only determines whether connections are made from the local computer (localhost) or across a LAN or WAN (default is checked).
- The target logbook is selected here.
- A connection logfile is available.
This is the setup page for QRZ.com Logbook (not callsign lookups).
- It's necessary to login to QRZ.com Logbook and obtain an API key from QRZ.com first. Enter that key here. Then choose whether or not to upload QSOs automatically.
This option provides an application programming interface (API) in and out of HRD Logbook. Examples about the use of this integration feature include WSJT-X (for modes like FT8, JT65, and JT9) and N1MM (for contesting).
Without going into IP networking fundamentals too deeply, it's worth understanding how this integration works.
Ham radio programs that use this method set up their applications to "Send QSO broadcasts", "receive QSO broadcasts", or both, with a UDP broadcast over the localhost (127.0.0.1) IP address that only the workstation can 'hear'. With version 220.127.116.116, Ham Radio Deluxe is able to both.
- NOTE: This type of integration is not used for JTAlert. This is why it's not listed in this dialog box. The options for logging from JTAlert are contained within JTAlert.
Ok, enough of the IP networking stuff. What you really need to know is the following:
- UDP Send: Ham Radio Deluxe Logbook has the ability to generate UDP broadcasts that other compatible programs can receive. This is the "UDP Send" section at the top of the QSO Forwarding dialog box. Use this if you are sending QSO data FROM Logbook TO other programs.
- Send Address (localport, the internal IP address to the machine, is the default)
- UDP Receive: Ham Radio Deluxe Logbook has the ability to receive UDP broadcasts that other compatible programs send. This is the "UDP Receive" section in the middle of the QSO Forwarding dialog box. Use this if you are sending QSO dta TO Logbook FROM other programs.
- NOTE: The ports used must be different.
It is this last example that has recently gained a lot of attention. It is with this capability that it is possible to automatically log QSOs from WSJT-X or N1MM into Ham Radio Deluxe Logbook.
If you want to send QSO data from WSJT-X, unless you're an advanced user, use the settings shown below under "UDP Receive".
- Check all the boxes. The Fill and Lookup options enable Logbook to perform callsign lookup features as selected in the Callsign Lookup options.
- Use the IP ports shown below (12060 for N1MM and 2333 for WSJT-X)
- Select a "Target Database" (generally, select your primary log from the dropdown)
- Choose how to handle the population of the My Station fields in Logbook's QSO records. The options are Ignore, Merge, and Overlaid. Unless you have a really good reason for doing otherwise, we recommend using the "Overlaid" selection. This will ensure that each QSO has your My Station data populated in it.
To complete the idea, regarding WSJT-X, the following is the current configuration screen for QSO "Reporting" (aka "broadcasting) for WSJT-X:
In this WSJT-X example - because WSJT-X and N1MM are using the same broadcast method - it's a matter of clicking the box under "N1MM Logger + Broadcasts" and leave the IP address as 127.0.0.1 and port at 2333. Once both Ham Radio Deluxe Logbook and WSJT-X are configured this way, QSOs will populate into Ham Radio Deluxe Logbook immediately after WSJT-X prompts the user to log the QSO and clicks "Ok".
- IMPORTANT: We recommend that you do not use JTAlert if you are planning on using this method. If you attempt to enable this method while using the JTAlert integration, it will likely end up creating duplicates in Logbook. This is because both integration methods are enabled. It is recommended to use only one of the two methods, or search for VK2BYI's paper on how to configure JTAlert to prevent it from creating duplicates.
There are two configuration tabs for configuring the rig settings into Logbook.
This tab configures the radio connection to Logbook. Generally, the defaults should be left as-is.
- Address is the IP address that Logbook is making a rig control connection to (localhost by default)
- Port is the IP port being used (cannot be the same as other used ports; 7809 by default).
- Automatically connect is checked by default with "Normal" Update Speed.
- Operator can choose to connect to the last radio when Logbook launches. This is used when multiple radios are configured.
This enables the operator to add or remove buttons in the rig control pane. This is useful when it's faster to get to the radio pane in Logbook than to switch over to the Rig Control application.
In this tab, it is possible to configure the colors of the face, markings, and rim of the rotator display in Logbook.
All modes have default values for RST loaded into Logbook. This data will be maintained through future software releases. Therefore, generally, these should not be changed.
- The default items are shown in the image above.
- In the RST Definition, all the modes included are on the left. They can be included (selected) into this definition. The RST values are on the right. These will be listed in the ALE for these modes. The default values are shown below.
This dialog box provides polling when an Access database is shared between multiple computers running HRD Logbook.
- When using MySQL or similar variants (MariaDB, etc).
This dialog box enables the operator to configure the rig control tuning dials within Logbook.
- Bands are created an enabled in the Bands tab.
- For information on configuring Favorites, visit this Rig Control description of this same option
- The colors and fonts can be changed in the Dial tab.
Managing Logbook Databases
Ham Radio Deluxe Logbook is built on Microsoft Access. The driver normally used is the Microsoft Access Driver (*.mdb)ODBC driver. You do not need a license to use Access databases - the runtime DLLs are included in Windows 7 or newer.
- You can create and manage additional databases for use within Logbook. You can, if you desire, create a separate database for contest work or a special event. Beware that this can create issues if you are interested in awards tracking.
- To manage your database(s), select Manager from the Toolbar.
This opens the Logbook Databases window.
- Within this window you can add new or modify existing databases.
- Logbook can be built on MySQL if you choose. Support for MySQL is beyond the scope of this document.
- Other (non-Ham Radio Deluxe) logbooks are supported via a DDE interface (see DDE Support) and a serial port (see 3rd Party Programs). So you can use the logbook of your choice with Ham Radio Deluxe provided it supports DDE or the Kenwood protocol via a COM port.
Creating & Managing QSOs
Add Logbook Entry (ALE)
Ham Radio Deluxe Logbook has a number of powerful features for tracking QSO data. This information is contained within the Add Logbook Entry (ALE) window and its fifteen tabs. This section will describe these areas. The ALE window is opened by clicking on the Add button in the toolbar.
But first, it’s necessary to understand the options for the ALE. The ALE’s menu bar has a number of menu items.
- Clicking the Options menu renders the following choices:
- The Times option can be selected for UTC or Local time.
- The Start and End times can be set according to the operator’s operating style.
- DXers and Contesters should use Current Time in the Times selection. This uses the time of the computer clock when the QSO is logged. Because DX and Contest exchanges are so short – lasting for only a few seconds – there’s an increased likelihood of making a QSL match to services like LOTW if the QSO is set to Current Time.
- Rag-chewers may want to use Set by user. This accommodates QSOs of longer durations.
- This enables the operator to change the fonts used in the dialog ALE.
- This enables the operator to choose the initial values for the three QSL fields. This is helpful when using a value like Queued to set the LOTW value so that it’s easy to do a search for QSLs that need to be uploaded to LOTW.
RST Rcvd / Sent
- This provides options for canned values of RST.
- The operator can select from bottom, middle, and right side location of the Update, Cancel, Reset, and Add Spot buttons. This is useful when vertical or horizontal space is restrained.
- The choices of positioning the menu on top or bottom are provided.
- Toggle on/off options
- Show Tooltips
- Save VFO B in database
- Keep Propagation Mode
- Mirror Locator on Location Tab
Show Worked Status
- This option enables a W icon to display for Call, Country, and Locator fields. This lets the operator know that these items have been worked before.
- The Tracking menu enables the ALE to use the data coming from the rid for frequency or mode and automatically populated into the ALE. (Default is ON for both.)
- This option enables the operator to choose which of the thirteen fields will be displayed in the ALE. (Default is all ON.)
- This option enables the operator to choose which of the fifteen tabs will be displayed in the ALE. (Default is all ON.)
The Logbook tab which is the first of many tabs at the bottom of the ALE window provides detail on previous QSOs with the station being logged. Partial and Exact matches are options.
The Worked tab provides detail about previous QSOs with that callsign, country, continent, zone, IOTA, or locator… by band and/or mode.
The country tab contains the DXCC information about the country being logged. This data is ‘display only’ and is not saved in the QSO record. As such, it's dynamically displayed.
The Contact tab provides a place to store information about the station operator’s age, Special Interest Group (SIG, or club), SIG website, email address, website URL 10-10 number, equipment, and biography. Callsign Lookup sources often provide much of this information.
The Location tab provides a place to store information about the station operator’s location – including State/province, City (QTH), County, ARRL Section, postal address, CQ and ITU Zone, continent, distance, and polar coordinates. Callsign Lookup sources often provide much of this information.
The IOTA tab provides a place to store information about the IOTA reference number and Island name.
The Ant/Sat tab provides a place to store beam heading and satellite information.
The Award tab is for tracking the award credits within the various awards programs. A QSO record cannot have both Submitted and Granted status for a given award. Selecting one de-selects the other. More information about the use of this tab can be found in the Awards Tracking section of this manual. These values are determinants of what is displayed in the Not Submitted, Submitted, and Granted columns in the Awards Tracking tab.
The Contest tab provides a place to store data related to contest exchanges.
Six Custom fields can be defined and used by the operator. This is useful for tracking awards that are not hard-coded within Ham Radio Deluxe such as Summits on the Air (SOTA). Clicking on the Configure button enables the operator to rename these fields.
My Station Tab
The My Station tab is particularly useful when the operator has multiple operating locations. The operator can select from profiles (stations) created in Ham Radio Deluxe Logbook.
The propagation tab saves solar data into the QSO record. Be sure to check the Track box to turn this feature on. The information comes from the most recent WWV or WCY information.
QSL, eQSL.cc, and LOTW Tabs
The QSL tab is for tracking paper and electronic QSLs. QSL Sent and Rcvd have the following values:
Y yes (confirmed); an incoming QSL card has been received, or the QSO has been confirmed by the online service
N no; an incoming QSL card has not been received, or the QSO has not been confirmed by the online service
R requested; the logging station has requested a QSL card, or the logging station has requested the QSO be uploaded to the online service
I ignore or invalid
V (deprecated) verified
Y yes; an outgoing QSL card has been sent, or the QSO has been uploaded to, and accepted by, the online service
N no; do not send an outgoing QSL card; do not upload the QSO to the online service
R requested; the contacted station has requested a QSL card, or the contacted station has requested the QSO be uploaded to the online service
Q queued; an outgoing QSL card has been selected to be sent, or a QSO has been selected to be uploaded to the online service
I ignore or invalid
- Note: These values are determinants of what is displayed in the Confirmed and Need QSL columns in the Awards Tracking tab.
The Filter button enables the operator to perform a logbook search, based on selected field criteria.
- Once selected, the operator can find QSOs based on Callsign, Date range, and a combination of any three additional fields. This is helpful when trying to find something unique in the log. These types of database queries are also used in displaying awards totals.
- The QSL filter button enables the operator to search and update QSL Status in bulk. This is helpful when printing a significant number of QSL cards over a given date range.
- The Award filter button enables the operator to search and update award tracking status in‐bulk. This is helpful when making an award application.
Bulk Editing QSOs
The bulk-editor is a powerful tool for making mass changes to the data in the logbook. It is highly recommended that a logbook back be made prior to using this tool.
- To use the bulk-editor, first select a number of QSO records where the same change is desired by using the “Filter” (search) or by selecting some number of records manually within the log.
- There are a number of places to find the Bulk Editor menu option. To use one as an example, right-click on any of the highlighted QSO records, and select one of the provided options.
- Any Fields is a very powerful choice, as it enables the operator to change anything in the database in mass (use with care). For this example, Any Fields is selected and the option to backup the logbook is provided.
- 1. Select Any Fields.
- 2. Next, select the “Add Field” button.
- 3. Select the desired field (CQ Zone, in this example)
- 4. Enter the desired value (10, in this example)
- 5. Click “Ok”
- All the selected QSO record will be updated with the desired value.
Importing Log Files
Logs can be easily imported from other logging programs. To import a log from another logging program, follow these steps:
- 1. Export the log into ADIF format from the other logging program. Make sure that it is configured to provide all available fields.
- 2. From the menu in Logbook, select Logbook >File > Import, and then choose the relevant option from the list of five shown. Most often, ADIF 2 is used.
- 3. Then select the ADIF file for input by clicking the button to the right of “DIF Filename. The recommended options are shown here:
- NOTE: It is strongly recommended that the top two boxes are always checked. This will ensure that the country stands the best chance of being converted correctly. Use the "Insert Local Station Information on Import" with care. If you have older QSOs in your log, and a newer QTH, you may not want to have the old QSOs show up in your log under the net QTH.
- 4. Once the file has been analyzed, the results will be shown. select Save to Database”.
- If there are errors in the source ADIF, the operator will see this in the results displayed below. Make note of them. It may be necessary to clean up the source data - using the errors as your guide - and attempt the import again.
- NOTE: Be aware of the “garbage-in/garbage-out” scenario. The information provided in Ham Radio Deluxe Logbook (for awards and QSO fields) is only as good as the data that comes from the other logbook source. There will always be some anomalies that the operator will have to sort out. This is generally because other programs may not have country data that is up-to-date.
Exporting Log Files
Logs can be easily exported for import into other logging programs. To export a log from Ham Radio Deluxe Logbook, follow these steps:
- 1. From the menu in Logbook, select Logbook > File > Export, and then choose the relevant option from the list of five shown. Most often, ADIF 2 is used.
- 2. Provide the export filename by clicking the button to the right of “ADIF Filename”.
- 3. Options are provided to select the field set for exporting.
- 4. The operator can export All or Selected logbook entries.
- Tip: Exporting selected logbook entries is a great way to update standalone logbook databases located on multiple computers.
Backup and Restore
Operators are encouraged to allow the automatic log backup to keep their log data safe.
- The “Automatic Backups” is found in the file menu under Tools, Configure, Backups. Backup files are saved in a proprietary XML format that ensures that information that is unique to Ham Radio Deluxe Logbook (like user-defined fields) are safely backed up. Some, but not necessarily all, of the backup locations should be used.
- Note: For this reason, making copies of ADIF files is not considered a backup method. Using an ADIF as a backup method could result in data loss. ADIF is an “amateur radio interface format” and was intended to interface logs between dissimilar systems by defining common fields.
- The Backup file field is the folder where the native XML file is created. This is the most commonly utilized backup file.
- The configuration of the backup function is described in more detail in the Configuration section of this guide.
Ham Radio Deluxe utilizes a country and prefix database that is roughly equivalent to the AD1C list (http://www.country-files.com). The country data itself doesn’t require constant maintenance. It is updated when new countries are added or removed from the DXCC list or when unique callsigns are in use that do not easily map to standard prefix parsing algorithms. The prefix masks contained within this data is rather complex and it is recommended that operators do not modify it. Updates will be made as frequently as necessary.
- The countries information can be seen by clicking on Countries and then Manager within the Logbook main menu.
- This prompts the operator for the Public or Private UCSDB.
- It is recommended that operators do not add or modify the entries in the Public UCSDB. These will be maintained and updated as frequently as necessary by Ham Radio Deluxe Software. Operators can create entries in the UCSDB by clicking Private and entering specific information about a callsign.
- Clicking the Add button provides a dialog box that the operator can use to enter the information.
- NOTE: While this method can be very effective, the operator should consider that using the Logbook as a callsign lookup source provide the same capability in real-time. That is – if the operator gets a call logged to the correct country on the first QSO, then the need to maintain a Private USCDB is unnecessary.
- Hint: The lookup methods already use the Public UCSDB to assist the operator in logging the QSO to the correct country on the first try.
External Log Interfaces
Ham Radio Deluxe Logbook has the ability to interface with a number of external online logging and awards systems. Presently the following systems are supported - LOTW, eQSL, HRDLog.net, and ClubLog.
Logbook of the World (LOTW) is supported when the Trusted QSL application is installed (required). Configuring LOTW is as follows:
- Click the LOTW Download button, or access the download function through the Ham Radio Deluxe Logbook menu by selecting Logbook, File, LOTW, Download. The following dialog box will be displayed.
- NOTE: Trusted QSL is not used or required for LOTW Download.
- 1. The LOTW URLs should not be changed or the download will not work correctly.
- 2. The operator adds the Username and Password for the LOTW account.
- 3. The ADIF field will populate automatically and it’s rarely necessary to change it.
- 4. Select a date range.
- Hint: By default, the download will begin where the last one left off.
- 5. Then click the Download button and the results will be shown after the file is downloaded.
- If there are any errors in the downloaded file, they will be described in the above dialog box. Most commonly, there is a mismatch between the mode or band for the data previously uploaded to LOTW and the data in Ham Radio Deluxe Logbook. This will tell the operator what needs to be resolved. Then a repeated upload will be successful.
- 6. Click Save To Database
- 7. Click Finish
- Hint: This is the method that updates the QSL and (some) Award status fields in the Awards Tracking module. You will have to hit the Refresh button in the Awards Tracking tab in order to update the totals.
- Begin by selecting the QSOs that the operator wants to upload. From within Logbook, this is done by using the Ctrl button and either left-click or shift-click to select records.
- Then click the LOTW Upload button, or access the download function through the Ham Radio Deluxe Logbook menu by selecting Logbook > File > LOTW > Upload.
- NOTE: TrustedQSL is required for LOTW Upload. The following dialog box will appear:
- 1. The LOTW URLs should not be changed or the upload will not work correctly.
- 2. The operator adds the Username and Password for the LOTW account.
- 3. The operator must tell Ham Radio Deluxe Logbook what folder TrustedQSL is installed.
- 4. If a Private password is used in TrustedQSL, it must be entered into the provided field.
- 5. The Station location must match exactly to the station location created and listed in the TQSL application under Add/Edit Stations.
- HINT: This is the most frequent cause of upload failures. The file fields will populate automatically and it’s rarely necessary to change them.
- 6. Then click the Upload button and the results will be shown after the file is uploaded.
- Tip: In order to know which QSOs to upload, it is quite helpful to add the LOTW sent field to the logbook layout (by clicking the Layout button and adding LOTW sent). Select the QSOs where LOTW sent is No before clicking the LOTW Upload button.
The configuration of the DX cluster is discussed in the Logbook Configuration section. This section will discuss the use of DX cluster features.
DX Cluster Status Bar
- DX Cluster connection status bar shows four things (using the information in the above image as an example to describe it):
- The operator's station (WA9PIE-10),
- is connected to a DX cluster node (WA9PIE-2),
- which is a DXSpider type node, and
- there is one active DX alarm.
- Connect or Close a DX cluster connection with the button on the far left.
- The Show menu is very important and it does five things:
- Spots - Displays the DX spots received from the connected DX cluster node; or submit an DX spot on the DX cluster system or node
- Announcements - Displays announcements that have sent to stations connected to the DX cluster system or node; or submit an announcement on the DX cluster system or node
- WCY - Displays solar weather from DK0WCY solar weather bulletins
- WWV - Displays solar weather from WWV solar weather bulletins from NIST
- Console - Displays the raw data sent and received between Logbook and the connected DX cluster node. This is very important for troubleshooting.
- NOTE: Many users are unaware of this feature. It can be very useful. Remember to change back to Spots after looking at these selections. The dropdown menu will always simply display "Show".
- Cluster Filters are changed using this dropdown.
- WSI Filters are changed by using this dropdown. Generally, this is a very important feature. It will hide spots based on what you have not yet Worked or Confirmed by Band, Mode, or both (Band+Mode).
- Copy the contents of the DX cluster to the Windows clipboard.
- View the contents of the DX cluster in a Notepad text file.
- Cluster Alarms Manager is a shortcut to enable, create, or manage DX cluster alarms within Logbook.
- DX Cluster Options is a shortcut to access configuration options for DX cluster.
- Silence Alarms quiets active audio alarms.
- QRZ.com opens the QRZ.com information page for a selected DX spot.
- Spot is a shortcut for submitting a DX spot .
- The number of spots displayed or updating with the current filter settings are shown at the right of the Spot button. This is useful when changing filters, as the operator is able to see the status of spots being updated in the display.
The information in the DX cluster is displayed in the following tabular format:
- This is rather self-explanatory. The operator can add, remove, or rearrange the columns displayed here using the "Layouts" tab in DX Cluster Options. The meaning of the columns are best found in description section of that Layout tab.
- The operator can right-click on a spot in the display and the following shortcut options are displayed:
- New ALE Window opens a new logbook entry form for the selected spotted call
- QRZ.com opens the QRZ.com information page for a selected DX spot.
- Copy Line copies the contents of the DX cluster to the Windows clipboard.
- Copy Raw Spot opens the contents of the DX cluster in a Notepad text file.
The Awards Tracking module in Ham Radio Deluxe Logbook provides the most complete award tracking features of any software available on the market. It tracks over 200 awards and endorsements in sixteen awards programs. Additionally, users have the ability to create and track additional awards of the operators choosing.
To open the Awards Tracking tab, click on the Awards Tracking icon in Logbook.
- The Awards Tracking tab will be displayed. On the left of your screen you will see a list of sixteen Award Programs that are currently supported by Ham Radio Deluxe.
- To the right of the list of awards programs, you will see the awards totals for the selected awards program (DXCC, in this example). When the award name is followed by “(Ham Radio Deluxe)”, this signifies that the award is hard-coded into the program and cannot be modified. It is possible to copy these hard-coded awards and customize them to suit the user’s liking (this will be covered later). The awards totals panel consists of “rows, columns, and cells” – similar to a spreadsheet. Understanding the meaning of the rows, columns, and cells is an easy but important step in using the awards feature. All awards programs conform to this format.
- The rows represent awards or endorsements within the selected awards program.
- Endorsements are listed beginning with an asterisk below the related award.
- The columns represent QSO, QSL, and Award credits within the selected awards program.
- Column descriptions are as follows:
- Worked - This is the total number of entities within the awards program that have been worked, regardless of QSL or award credits. This is a QSO status column.
- Confirmed - This is the total number of entities within the awards program that have qualifying QSL confirmations. Each awards program accepts different QSLs (for example, QSL cards, eQSL, and LOTW confirmations may not be accepted for all awards). The award is created to only include the QSL types relevant for that award. This is a QSL status column.
- Need QSL - This is the number of entities within the awards program that have been worked but not confirmed. The information directs the operator to the QSOs that can be pursued for confirmation. This is a QSL status column.
- Entities Needed - This is the number of entities within the awards program that have not been worked. This is a QSO status column.
- Not Submitted - This is the number of entities within the awards program that have been confirmed, but not yet included in an awards application. This information will be used by the operator to make an awards application. QSOs are not included in this total once they have been included in an application and appear in the Submitted column. This is an awards status column.
- Submitted - This is the number of entities within the awards program that are part of a current application and awaiting approval. QSOs are not included in this total once they have been granted award credit within the program and appear in the Granted column. LOTW download provides this data for confirmations obtained through LOTW. This is an awards status column.
- Granted - This is the number of entities within the awards program that have been included and approved for award credit. LOTW download provides this data for confirmations obtained through LOTW. (Cards included in applications prior to LOTW are not included in the LOTW download information and must be added manually.) This is an awards status column.
- Note: The “Not Submitted”, “Submitted”, and “Granted” awards status columns are “transitional” columns. That is – a given QSO can be in only one of these columns.
The awards feature in Logbook acts like a calculator that counts things. It would count things in Logbook where the entity selected match to the awards and QSO and QSL statuses indicated in the report.
- The data that rolls-up to the totals in these columns come from information contained within the QSO records in the logbook as follows:
- The Worked, Confirmed, Need QSL, and Entities Needed data comes from the QSL, eQSL, and LOTW tabs in the ALE. The Not Submitted, Submitted, and Granted data comes from the Award tab in the ALE. When the Award tab is not populated automatically from the online system (like LOTW), the information should be populated manually when applications are made. (Again, a given QSO cannot have both Submitted and Granted values. Selecting one de-selects the other.)
- The cells provide the totals for the column within the selected award. When you double-click on a cell, it will produce a list of the entities that represent that total. For example, the following image indicates that there are ten entities worked for the DXCC Digital award where QSLs are needed:
- Double-clicking on the “10” provides a list of those entities:
- There are three choices for displaying the QSOs represented by this list. These three choices are available in the Filter icon in the icon bar above the list. Clicking this button “toggles” the filter between the three values.
The Filter [Newest] assumes the operator wants to see only one QSO among the list of entities shown. This is most helpful for making award submissions (Not Submitted column) where only one qualifying QSO is needed.
- Once the desired filter is selected, the operator can display the results by clicking the View All button.
What QSOs do I need to obtain cards from to increase my DXCC Digital Awards confirmation?
- Going back to the ten entities in the Need QSL column, the operator would want to select Filter [Off] and View All. This would render a complete list of QSOs with those ten entities where a QSL could be obtained.
- Notice that, for the 10 entities where a QSL is needed, there are fourteen QSOs. This gives the operator the ability to decide which QSOs to pursue. The operator can select QSOs in this view and print QSL cards or labels from this list.
- Hint: Select Ctrl + A will select all the QSO. Press the Ctrl button, while clicking individual QSOs, will select a number of individual QSOs as desired.
What QSLs do I need to submit to include in my next awards application for the DXCC Phone Award?
- The awards totals indicate that five QSLs are ready for to be submitted in an award application:
- Double-clicking on the “5” generates a list of the entities that will be submitted:
- Because there may be more than one QSL for some of these entities in this list, I will select Filter [Oldest] and View All. This provides the list needed for submission:
- The operator can print this list by clicking File/Print in the Ham Radio Deluxe Logbook menu. Additionally, the operator can save this list as an Excel or delimited text file so that the information can be combined into a single award application.
- Clicking on the Matrix button generates a matrix report for the selected awards program. This is very similar to the style of report that is provided by the ARRL for DXCC awards. But this report shows Granted (G), Confirmed (C), and Worked (W) countries by award.
Creating Custom Awards
Operators can create (define) their own awards by selecting the Definitions button in the Awards Tracking tab.
- The operator can create a new award based on one of the hard-coded (Locked) awards by selecting one and clicking Copy, or build a new award from scratch by selecting Add.
- Because the awards definition builder is very flexible, it would be hard to describe a specific example. It is recommended that the operator tinker with this by creating a copy of a hard-coded (Locked) award and learning it through trial-and-error.