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 and JTDX (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 ( IP address that only the workstation can 'hear'. With version, 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 and Merged. Unless you have a really good reason for doing otherwise, we recommend using the "Merged" 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:

WSJT-X QSO Reporting.PNG

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

If after this the QSO forwarding is not working, look up our Multicasting guide.

Continue to next section