Bill,
Ø Similarly a priori decoding based on the DX Call field are disabled by
clearing the DX call field. If you are going to leave WSJT-X unattended then
clearing the DX Call field is a good idea.
Thanks for that. Noted. It is fully noted and makes sense. Some observations
had occurred
:* Thursday, 14 May 2020 11:47 PM
*To:* WSJT software development
*Subject:* [wsjt-devel] WSJTX 2.2 RC1 - FT8 Intermittent/Irregular
False Decodes
Folks,
Reports are asked for ! Do NOT consider this a “knock” … it is just a
report !
I am recording approximately 1 serious “false decode” every 12
development
Subject: [wsjt-devel] WSJTX 2.2 RC1 - FT8 Intermittent/Irregular False Decodes
Folks,
Reports are asked for ! Do NOT consider this a “knock” … it is just a report !
I am recording approximately 1 serious “false decode” every 12 hours on
average. Note that I am using “AP” mode
Folks,
Reports are asked for ! Do NOT consider this a “knock” … it is just a report !
I am recording approximately 1 serious “false decode” every 12 hours on
average. Note that I am using “AP” mode:
i.e.
200514_03203018.100 Tx FT8 0 0.0 700 CQ VK3VM QF11
200514_032045
