Date   
Re: Installed QSO relay with JTAlert, WSJT-X and HRD V6 but nothing get loaded into HRD

Roel Vreeburg
 

Hi Chris,

Thanks for your very quick response.
The HDR documentation seems to mis these kind of details on available ports numbers etc. I got confused on the 7825 and 7826 and suspected a typo as HDR did not show new logs from WSJT-X. So I tried. Wrong idea :-)
But you have clarified that bit.

I am using QSO relay because of the many blogs on internet talking about this combination and the need for QSO relay. But I understand your point and will remove QSO relay and see if that setup works with the JTalert setup for HDR6.

Thanks so far. I will test this next week. If I am not succeeding, I will send you the QSO relay logs.

Again thanks and 73.

Roel (PA3RNV)

On 7 Sep 2018, 03:21 +0200, Chris VK2BYI <chris@...>, wrote:

Port 7826 is the Logbook API port that implements a proprietary command line interface that allows third party applications like QSO Relay and JTAlert to add contacts to the Logbook using TCP. Port 7825 is a completely different interface that uses XML packets sent using UDP to log contacts from DM-780. You must use 7826 as the port number for the Logbook TCP port in QSO Relay, and you should reset the port to 7825 in DM-780. In hindsight, I should not have made the Logbook TCP port setting in QSO Relay editable. It should have been read-only, or not displayed at all, as I don't believe the port number can be changed in Logbook.

Please refer to the YouTube video or documentation, both of which are available from www.vk2byi.com, for further information. You need to use Standard ADIF File logging in JTAlert, and refer to the QSO Relay Settings and Data Flow topic in particular for an overview of the data flow..

If you would like me to take a closer at what might be happening, please read the Reporting an Issue - MUST READ topic for the steps to take to capture a session during an attempt to log a contact.

I should also mention that QSO Relay is no longer required to log contacts from JTAlert to Logbook. Later versions of JTAlert support direct logging to Logbook via the HRD V5/V6 setting. This was not always the case in the past which is why QSO Relay was developed. So you can try using direct logging from JTAlert to Logbook, and close down QSO Relay to see if that helps.

73 Chris
VK2BYI

New file uploaded to vk2byi-qsorelay@groups.io

vk2byi-qsorelay@groups.io Notification <vk2byi-qsorelay+notification@...>
 

Hello,

This email message is a notification to let you know that a file has been uploaded to the Files area of the vk2byi-qsorelay@groups.io group.

File: Alternative Configuration Options.pdf

Uploaded By: Chris VK2BYI

Description:
Alternative Configuration Options for WSJT-X, HRD Logbook, JTAlertX and QSO Relay.

You can access this file at the URL:
https://groups.io/g/vk2byi-qsorelay/files/Alternative%20Configuration%20Options.pdf

Cheers,
The Groups.io Team

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