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. -- 73, Bernie, VE3FWF

I realized I did not have latest version. After update from 2.15.7 to 2.16.3 I no longer hear "DX" for /MM. 73, Andy, k3wyc

Laurie, ave also the HD .269 and Jtalert .2.16.3 build 2 working together ok........ Only notices that the propagation details are now not transferred into HRD .... don't know if it is in hrd or

There are several maritime mobile stations active on 40 m and some of the call signs are those of DX I have not worked on 40 m. JTAlert calls "DX" each time one of these /MM stations is decoded but

This does not exist in JTAlert and there are no plans to create such an intrusive feature. How are you determining that the logged station is receiving a text message from you?

Just loaded v2.16.3 to a clean install meaning all previous files removed. Setup all my preferences. Ran some tests and works faster and this is a great update. One thing it does when logging the

*** IMPORTANT PLEASE READ*** JTAlert users who have upgraded their version of HRD to 6.7.0.269 and followed HRD instructions on updating their existing FT4 QSOs to be adif 3.1.0 compliant, Mode-MFSK,

Hi Laurie Must have disappeared into the ether, I replied to your locked post. They have introduced a number of issues for third party apps! Note second para, this from Mike at HRD

No need. I have already provided the answer here https://hamapps.groups.io/g/Support/message/28940 de Laurie VK3AMA

I don't see any waiting moderation message from you. This issue is easily resolved by telling JTAlert it needs to log ADIF 3.1.0 compliant FT4 now that your HRD log has been

If JTAlert is logging as Mode=FT4, then you have not followed all the instructions provided by HRD when they first released 6.7.0.269 and you needed to update your log. You have changed

It looks like a Mode mapping issue in JTAlert. Laurie, if you need a trace log, please let me know. -- 73, Bernie, VE3FWF

It sounds like you are set up to send logs from both WSJT-X and JTALERT to HRD. You need to turn one of them off. If you using WSJT-X to send your contacts to HRD logging, then you do not need to

Hi Bernie Experiencing same issue, have reported to Laurie. My response is in moderation as I replied to his locked message. 73 Gavin, ZL3GAV

I am having a configuration issue with WSJT-X v2.1.2, JTAlert 2.16.3.beta 002 and HRD 6.7.0.269 logging FT4. WSJT-X logs directly into HRD with no problem with the correct Mode (MFSK) and Submode

If you are using HRD, you will need to go into HRD Tool > Configure > QSO Forwarding and uncheck the UDP Receive. I recently changed from WSJT-X feed of my HRD lot to JTALERT and had the same

Suggestion:Take a look at AVG's privacy policy and what they do with your data. -- --Kyle-- K7KE

I did reselect the correct speaker. Did not work. I uninstalled 2.16.1 and then installed 2.16.3 and it seems to work for today anyway. Gary

It is the user's fault when they don't even try to understand how AV software works. This isn't a "2020" issue - AV heuristics have been throwing generic warnings on unsigned code for over half of a

I just tried it, and got the same thing. Herb WB8ASI