On 03/01/2019 21:56, Martin Davies G0HDB wrote:
I'll have to try to restrict my directional CQ qualifiers to letters only,
although I suspect if
someone saw a CQ call in the form <CQ_W6W7> G0HDB IO82 they might be able to
work
out which call areas I was looking for...:-)
If someone saw a CQ in that format and double-clicked on my callsign would the
normal
QSO sequence start, or is a message in that format treated as free-text and
therefore not
clickable?
--
73, Martin G0HDB
Hi Martin,
as always with WSJT-X messages the actual message sent appears with a
yellow background in the status bar while it is being transmitted. In
this case you will see:
<...> G0HDB IO81
which is exactly how it will be decoded by anyone who receives it, so
they will not have a clue what you intended. Sorry.
You can use the ft8code application shipped with WSJT-X to investigate
message encoding and decoding:
C:\WSJT\wsjtx\bin\ft8code "CQ W6W7 G0HDB IO82"
Message Decoded
Err i3.n3
----------------------------------------------------------------------------------------------------
1. CQ W6W7 G0HDB IO82 <...> G0HDB IO82
* 1. Standard msg
Message bits:
00000001111101111100111010000000010001111101000011111111000011111000001010001
Channel symbols (tones):
3140652002727145005273077407403524153140652367512254570000144765005753023140652
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
