Thank you Laurie for the info. RTFM, oh dear! Now need to figure why some fields such as Name are not being updated by HRD when logging QSO. Same problem as PC1Y.

#HRD

Oh and I doe have HRD set as the logging program in JT-Alert. Warren KC0GU

#HRD

Under JTAlert, Settings, Logging -> Last QSO section... I unchecked 'Enable transmission of last QSO. And under WSJT-X, Settings, Reporting tab I don't see anything regarding Secondary UDP Server (see

#HRD

Aha! That may have been the problem. I thought I had the firewall and anti-virus programs under control, but maybe not. 73, Frank KF6E

#HRD

Laurie: Been doing some digging. They had server issues earlier in the week that I reported. You cannot get into their help website/page. I'm guessing it is there problem as you suggested. Bob W8RID

#HRD #JTDX #FT8

You can have WSJT-X log directly to HRD Explanation in this link: https://forums.hamradiodeluxe.com/node/48816 And there's an add-on for DXKeeper to publish to QRZ and HRDLog.net -- doesn't appear in

#HRD #TIP

Got it fixed. I mistyped one of the TCP server numbers. Bob

#JTDX #HRD

Thanks . Problem Solved . 73 PY8WW Em qui, 17 de jan de 2019 às 07:47, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> escreveu:

#FT8 #HRD

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