OM, The HamApps web page had not been updated after HRD 6 support was reinstated within JTAlert. That has been corrected. de Laurie VK3AMA

#HRD

It appears that the readback from JTAlertX from a remote HRD Log Server (latest version) is failing. The log is written successfully to the remote HRD Log server but the verification step is failing.

#HRD

Folks, I did try Log4OM and miraculously enough, it does not show this problem. It will take me some time to get used to it's other features.

#HRD #JTDX

Thanks Laurie. David

#HRD #FT8

For those who are sending support requests for the intermittent HRD logging failure of JTAlert 2.11.1 it is important that you enable debug recording in JTAlert otherwise there is no data for me to ex

#Important #HRD

After updating to 2.11.1 HRD will not accept a log fill after the 73 TXT.. It says it can't confirm the data. The only way to log a contact is to log it from WSJT-x button. I tried enabling the Automa

#HRD

JTAlert Settings, Logging section. Turn off the "Mark QSO upload to LoTW as Requested" setting and similarly for the eQSL setting. settings. de Laurie VK3AMA

#HRD

I missed that completely. It's under Logging (main heading) > Log full name returned from XML Lookups as well as Log Full QTH returned from XML lookups. Also the Log Address returned from an XML looku

#HRD

Vince, check your settings in WSJT-X under the Reporting Tab, make sure you have the "Prompt me to log QSO" option ticked. 73 Bruce VK2RT

#HRD

Mike, Please use your spell-checker. It is very hard to follow what your asking. With relation to JTAlert, the only thing you have to do is set it to use HRD as the enabled Logger. JTAlert automatical

#HRD

Bob, The problem is due to 1.9.0-rc2 and its popup Release Candidate Warning window. Until the next WSJT-X release (which alters the Window title naming that causes incorrect JTAlert docking) you will

#FT8 #HRD

Hi Laurie, Thanks again. It is exactly as you said. Upgraded JT-Alert and now it works like a dream!!! Thank you again! 73 ON5UN Erwin

#HRD

The extra hash tags were added by the Forum web site interface. Interesting. I guess that I won’t select to add hash tags any more.

#HRD

Morning That was a long time ago (in FT8 terms) - HRD v6 works fine with current version (now 2.10.13) Tom

#HRD

Dan, Thanks for the update. Hopefully this long standing defect (first reported Nov 2015) will finally get corrected. de Laurie VK3AMA

#HRD

Thanks. It is working now. Merry Christmas.

#HRD

Kenneth, Please don't start another message thread for the same problem. de Laurie VK3AMA

#HRD

Erwin, Thanks for the feedback. Good to hear that all is working correctly. de Laurie VK3AMA

#HRD

OM, JTAlert has always supported HRD V5 logging. It was only for HRD 6.3+ that support was dropped for several JTAlert versions. At the time of this message, all HRD versions are supported by JTAlert

#HRD

GM Laurie.. I believe you are right. HRD was 6.4.078. When I made a new log, the HRD log manager did not make the new log the default. It seems that the action of moving the log entry to the top of th

#HRD