Hi All,
Thanks for the great and always improving software!
This is a report being made in case the behavior that I have observed is
not what the developers intended. It is not a complaint and it is not a
request for any changes to be made in the WJSTX code.
I am working with the UDP message facility and v 2.0.0 and all is going
well without issues.
The "message types" references below relalte to the message types of UDP
messages as defined in the document "NetworkMessage.hpp" and have
nothing to do with the type designations relating to callsign/compound
callsign structure.
My question regards the documentation and implementation of the message
structure for Type 2 messages asd defined in that document. For the
most part, the documentation in NetworkMessage.hpp regarding message
structure matches with what I have found.
However, in type 2 messages the documentation says that "Mode" is to be
sent in UTF8, so I expected to see in type 2 messages what I see sent
for Mode in the Type 1 messages, e.g for FT8 "03 46 54 38" which is of
course just the size index "03" followed by the ascii bytes for "FT8".
Instead, in the type 2 messages I see for example for FT8 "01 7E" in the
byte array, 01 being the size index and 7E being the payload, which is
the extended ascii code for "~". For each of the modes that I checked I
see as the mode designation in type 2 messages:
With HF Settings:
FT8: 01 7E
JT4: -----
JT9: 01 40
JT65: 01 23
MSK144: 01 26
ISCAT: -----
QRA64 02 3A 2A
With VHF Settings:
FT8: 01 7E
JT4: -----
JT9: 01 40 (all submodes, fast and slow)
JT65: 02 23 2A (all submodes)
MSK144: 01 26
ISCAT: (01 2D)
QRA64 02 3A 2A (all submodes)
Also, I do not see any evidence of type 2 messages being sent with
successful decodes of JT4 or ISCAT messages with HF settings, and have
only once seen an ISCAT type 2 message sent with VHF settings, after
giving the GUI a heavy workout, and I have not been able to reproduce
that condition where I did see an ISCAT type 2 message. As is the case
with HF, I never see any type 2 message being sent after successful JT4
decodes.
Is all of this (mode designations differing between type 2 and type 3
messages, and the lack of sending of type 2 messages for JT4 and ISCAT
decodes) expected and desired behavior?
Thanks in advance for the info, and
73,
Roger Rehr
W3SZ
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
