On 14/05/2020 15:02, Stephen Ireland wrote:
Hi Folks,
I have analysed the logic of the anomaly in this report These forms of
anomaly - though rare – are something that we may have to watch for
manually … Hence “grit and bare”.
73
Steve i
VK3VM / VK3SIR
*From:*Stephen Ireland <vk3...@hotmail.com>
*Sent:* Thursday, 14 May 2020 11:47 PM
*To:* WSJT software development <wsjt-devel@lists.sourceforge.net>
*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:
i.e.
200514_032030 18.100 Tx FT8 0 0.0 700 CQ VK3VM QF11
200514_032045 18.100 Rx FT8 -16 0.3 763 JA2ATE N4QS RR73
200514_032045 18.100 Rx FT8 -24 2.4 2463 VK3VM 1P4ZBI/R R
JH60 ? a2
200514_032100 18.100 Tx FT8 0 0.0 700 1P4ZBI/R VK3VM RR73
200514_032115 18.100 Rx FT8 -13 0.3 763 JA2ATE N4QS RR73
200514_032115 18.100 Rx FT8 -15 0.1 2016 JF7ELG YB0AA -15
This responded with an attempt to log. I now have recorders on and
hopefully can catch a snippet of the audio stream for analysis.
Perhaps a “catch” for such grossly out-of-sequence false decodes may
be needed?
73
Steve I
VK3VM / VK3SIR
Steve,
a priori decoding for replies to you CQ calls are only attempted for a
short time after your last CQ call. 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.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
