locked Re: Worked B4 Not Working

HamApps Support (VK3AMA)

On 31/05/2020 7:46 am, Charles Ristorcelli wrote:

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. Release;   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 shown.

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

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 Release notes...

    - HRD All JTAlert FT4 functionality broken, B4 checks, Logging
       confirmations, Log scanning and Callsign QSO History when run against
       HRD with an updated adif 3.1 compliant log.
       See JTAlert help file, "HRD, JTAlert settings" topic.

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 broken functionality).

See the JTAlert Help File,
"HRD, JTAlert settings" topic for the simple changes (along with pictures) needed to be made to JTAlert.

de Laurie VK3AMA

Join Support@HamApps.groups.io to automatically receive all group messages.