On 31/05/2020 7:46 am, Charles
A month or so ago, HRD changed their log to be
ADIF 3.1 compliant with respect to FT4 QSOs. JTAlert released
2.16.4 to accommodate those changes with the following in the
Here is the architecture.
Transceiver YAESU FT-5000MPDX
Intel I9 processor; 16 GB RAM; 1 TB Hard drive
Windows 10 64 bit; Ham Radio Deluxe V. 126.96.36.1999 Release
188.8.131.529; WSJT-X V 2.100068f9 ; JT Alert V 2.16.6
The issue I have is that JT Alert does not show Worked Before
status, whether I worked the contact last week, or worked it
immediately and then the staion continued active but was not so
All the software versions prior to the recent JT Alert upgrade
showed the same issue starting about 1 month ago.
The issue continues with JT Alert Version 2.6.16
Looking forward to VK3AMA assist.
73 de NN3V
- HRD 184.108.40.2069: All JTAlert FT4 functionality broken, B4
confirmations, Log scanning and Callsign QSO History when
HRD 220.127.116.119 with an updated adif 3.1 compliant log.
See JTAlert help file, "HRD 18.104.22.1689, JTAlert settings"
A quick look on HamSpots shows that your primarily running FT4. If
you upgraded your HRD Log FT4 QSOs but didn't also update the
JTAlert Settings telling it your log is now FT4 compliant than
broken FT4 B4 reporting will be the result (as well as some other
See the JTAlert Help File, "HRD 22.214.171.1249, JTAlert settings" topic for the
simple changes (along with pictures) needed to be made to
de Laurie VK3AMA