locked Re: B4 Behavior


Laurie, VK3AMA
 

On 17/09/2021 11:41 pm, WB5JJJ - George wrote:
JTAlert is apparently behaving as it should, based on the bad information it gets from WSJTx, even though I think JTAlert should have recognized the entry as a B4 itself.
To be clear, WSJTX does not send bad or good information to JTAlert, it simply sends what was decoded. The extra information about a decoded callsign, like B4 and Wanted status, is determined by WSJTX or JTAlert after examining the decoded callsigns.

You cannot rely on the differences in what JTAlert and WSJTX are reporting as an indication of a problem. The reported status of a Callsign by JTAlert and WSJTX is coming from 2 different log files. WSJTX uses its internal adif file and JTAlert uses the log file of the LOgger you have enabled in JTAlert. Unless you keep both logs in sync, there will be instances of different reporting.

de Laurie VK3AMA

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