Date   
locked Ham Radio Deluxe v6.4.0.866 and QSO Forwarding

Chris VK2BYI
 

Several changes have been made to the QSO Forwarding features in Logbook in the latest Ham Radio Deluxe 6.4.0.886 release.  One new feature is a UDP datagram listener for the N1MM Logger+ Broadcasts feature that was first implemented in WSJT-X version 1.9.0. which allows direct, automatic logging of QSOs from WSJT-X to Logbook.  This new feature is great for those users running just WSJT-X and HRD Logbook or other loggers with N1MM compatible interfaces.

For those users like myself who routinely use JTAlertX and possibly QSO Relay, using this new listener allows for an alternative configuration that I have managed to get working.  However, I don't recommend using it with JTAlertX for a few reasons:

  • JTAlertX continues to support direct logging to HRD Logbook using the Logbook API;
  • it requires a more complicated set of application settings which offers no real advantage;
  • it makes using QSO Relay mandatory and I am happy for it to remain an option.

So, to provide further explanation and to avoid confusion, I have written a paper that describes various scenarios and the configuration options required to successfully implement working configurations.  The file can also be found in the Files section of this support group.

In summary, if you are using JTAlertX (with or without QSO Relay), no need to change anything.  If you are using QSO Relay, v1.7 remains the latest version.

73 Chris
VK2BYI

 

locked QSO Relay version 1.8

Chris VK2BYI
 

Please be advised that a new release of QSO Relay (Version 1.8) is now available for download at http://www.vk2byi.com.au/qsorelay/, or by selecting the Check for Updates... item on the QSO Relay menu if you are using a previous version of QSO Relay.

This version fixes an error where the ADIF header in the Last QSO API packet sent by JTAlertX v2.12.8 or later, was not being parsed correctly which resulted in the contact not being logged in HRD Logbook.

I do apologize for any inconvenience caused.

73 Chris
VK2BYI

QSO Relay Not Logging Contacts after JTAlert v2.15.1 Update

Chris VK2BYI
 

A new option has been added in version 2.15.1 of JTAlert (HamApps.com) to optionally include an ADIF header in the 'LastQSO.adi' file.  The default setting for this new option is to include the header.

Unfortunately, QSO Relay fails to correctly parse the ADIF record being received from JTAlert if this header is included.  A new version of QSO Relay will be released shortly that will correctly parse the ADIF record regardless of whether or not the header is included.

In the meantime, you can temporarily turn off the option in JTAlert so that the ADIF record will be handled correctly by the current version QSO Relay (v1.8.6930.23917).  Open the JTAlert Settings window, and select Last QSO API under the Logging node and uncheck the Include ADIF Header:



I apologise for any inconvenience caused.

73 Chris VK2BYI