Hi Roger,
You will probably get a better answer to your query from Bill, G4WJS.
But it seems that the messages you are flagging as "bad" are simply the
ones resulting from successful "a priori" decoding. This is described
in the Section 12.1 of the WSJT-X 2.1 User Guide:
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.1.2.html#_ap_decoding
-- 73, Joe, K1JT
On 1/19/2020 7:25 PM, Roger Rehr W3SZ wrote:
This message is informational only, for the developers. The issue
raised does not represent an operational problem for me as the issue is
simple to handle in code at the receiving end. But I thought that you
should be made aware of the behavior in case it is unintended. It may
well be intended, and in that I case I apologize for missing the memo
and creating unnecessary bandwidth :)
Today I noticed a very occasional variation in type 2 UDP network
messages sent by WSJTX version 2.1.2. The issue of variation is that
the length of the text message as specified in the UDP message is longer
than the "correct" text message length, and in fact the "text message"
portion of the UDP message consists of the "correct" text message
followed by a number of spaces, followed sometimes other character and
finally followed by "a1" before the Low Confidence and Off air bits of
the message are given (in their correct position based on the specified
"text message" length).
I don't think that this represents mangling of the UDP packet in transit
because the size of the text message as specified in the message is
correct for the included data, and as just noted the Low Confidence and
Off air bits appear at their expected positions given the specified text
message length. If the observed anomaly were a result of mangling of
the message in transit, there would not be this congruity.
Below are print outs of a couple of examples of this anomaly, and then
of a "good" message. The "0 Array" is the entire network UDP message.
"1 Array" thru "11 array" represent the corresponding message parts as
specified in NETWORK_MESSAGE_HPP. I used 3 carets and then 3 percentage
markers to bracket the text message in the first line so that, when
analyzing this, I could tell where the text message actually began and
ended if there were non printing characters present.
Here is an example of a "bad" message:
From handleMsg2 Routine msg is ^^^CQ TEST N2CG FN20 ?
a1%%% CQ2 is --- Grid is FN20 Call is N2CG
The 0 Array is AD BC CB DA 00 00 00 02 00 00 00 02 00 00 00 10 57 53 4A
54 2D 58 20 2D 20 4D 61 69 6E 32 31 30 01 04 CE ED 30 FF FF FF EF 3F F1
99 99 A0 00 00 00 00 00 06 60 00 00 00 01 7E 00 00 00 28 43 51 20 54 45
53 54 20 4E 32 43 47 20 46 4E 32 30 20 20 20 20 20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 3F 20 61 31 00 00
The 1 Array is AD BC CB DA 00 00 00 02 00 00 00 02 00 00 00
The 2 Array is 57 53 4A 54 2D 58 20 2D 20 4D 61 69 6E 32 31 30
The 3 Array is 01
The 4 Array is 04 CE ED 30
The 5 Array is EF FF FF FF
The 6 Array is 00 00 00 A0 99 99 F1 3F
The 7 Array is 60 06 00 00
The 8 Array is 7E 01
The 9 Array is 43 51 20 54 45 53 54 20 4E 32 43 47 20 46 4E 32 30 20 20
20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 3F 20 61 31
The 10 Array is 00
The 11 Array is 00
2 ID SIZE is 16
2 Rig Name is WSJT-X - Main210
3 IsNew is 1
5 snr is -17
6 Delta time is 1.10000002384186
7 Delta freq is 1632
8 Mode is FT8
9 message is is CQ TEST N2CG FN20 ? a1
10 Low confidence is 0
11 Off Air is 0
------------------end of Bad Type 2 message
Here is another example of a Bad Type 2 message:
From handleMsg2 Routine msg is ^^^CQ TEST N4HB FM17 a1%%% CQ2 is ---
Grid is FM17 Call is N4HB
The 0 Array is AD BC CB DA 00 00 00 02 00 00 00 02 00 00 00 10 57 53 4A
54 2D 58 20 2D 20 4D 61 69 6E 32 31 30 01 04 CF D7 90 FF FF FF E9 3F F6
66 66 60 00 00 00 00 00 04 41 00 00 00 01 7E 00 00 00 28 43 51 20 54 45
53 54 20 4E 34 48 42 20 46 4D 31 37 20 20 20 20 20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20 20 61 31 00 00
The 1 Array is AD BC CB DA 00 00 00 02 00 00 00 02 00 00 00
The 2 Array is 57 53 4A 54 2D 58 20 2D 20 4D 61 69 6E 32 31 30
The 3 Array is 01
The 4 Array is 04 CF D7 90
The 5 Array is E9 FF FF FF
The 6 Array is 00 00 00 60 66 66 F6 3F
The 7 Array is 41 04 00 00
The 8 Array is 7E 01
The 9 Array is 43 51 20 54 45 53 54 20 4E 34 48 42 20 46 4D 31 37 20 20
20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 61 31
The 10 Array is 00
The 11 Array is 00
2 ID SIZE is 16
2 Rig Name is WSJT-X - Main210
3 IsNew is 1
5 snr is -23
6 Delta time is 1.39999997615814
7 Delta freq is 1089
8 Mode is FT8
9 message is is CQ TEST N4HB FM17 a1
10 Low confidence is 0
11 Off Air is 0
------------------end of Bad Type 2 message
Here is a Good Type 2 message:
From handleMsg2 Routine msg is ^^^CQ TEST N4HB FM17%%% CQ2 is --- Grid
is FM17 Call is N4HB
The 0 Array is AD BC CB DA 00 00 00 02 00 00 00 02 00 00 00 10 57 53 4A
54 2D 58 20 2D 20 4D 61 69 6E 32 31 30 01 04 CF 62 60 FF FF FF E8 3F F6
66 66 60 00 00 00 00 00 04 0B 00 00 00 01 7E 00 00 00 11 43 51 20 54 45
53 54 20 4E 34 48 42 20 46 4D 31 37 00 00
The 1 Array is AD BC CB DA 00 00 00 02 00 00 00 02 00 00 00
The 2 Array is 57 53 4A 54 2D 58 20 2D 20 4D 61 69 6E 32 31 30
The 3 Array is 01
The 4 Array is 04 CF 62 60
The 5 Array is E8 FF FF FF
The 6 Array is 00 00 00 60 66 66 F6 3F
The 7 Array is 0B 04 00 00
The 8 Array is 7E 01
The 9 Array is 43 51 20 54 45 53 54 20 4E 34 48 42 20 46 4D 31 37
The 10 Array is 00
The 11 Array is 00
2 ID SIZE is 16
2 Rig Name is WSJT-X - Main210
3 IsNew is 1
5 snr is -24
6 Delta time is 1.39999997615814
7 Delta freq is 1035
8 Mode is FT8
9 message is is CQ TEST N4HB FM17
10 Low confidence is 0
11 Off Air is 0
--------------------end of Good Type 2 message
73,
Roger Rehr
W3SZ
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
