I suspect its due more to the fact that he was using the Tx5 message
with its 13 character limit, and not the Tx6 which allows the addition
of up to 4 characters between the 'CQ' and the callsign, and will also
include the full 4 character grid in the transmission.
Neil, KN3ILZ
On 8/18/2020 2:34 AM, 5p1kzx Michael wrote:
Hi Steve
I don't think that 5CT is a valid callsign. A search on the Internet
gave no result.
73 de Michael 5p1kzx
Den 18-08-2020 kl. 08:06 skrev Stephen VK3SIR:
Hi Folks,
I am unsure whether this has been reported:
30m:
055130 -11 0.2 1626 ~ CQ CO8LY FL20 Cuba
055130 -17 0.3 1342 ~ R3BV F1LYV RR73
055130 -19 0.3 618 ~ CQ DX 5CT JN0 Morocco <-- Will not
allow this to be picked this up
055200 -12 0.2 1627 ~ CQ CO8LY FL20 Cuba
No matter what you do or how you try to pick up this calling station
and pick up its call (i.e. click on it, double click, even use
JTAlert) WSJT-X will not pick up this call !
I can see that this is being primarily interpreted as a text message
(i.e. > 13 chars) ... with the call framed in a " bad" format
(missing the final char of the maidenhead).
[ It is fully understandable and understood why the logic will not
allow this call to be picked up as the truncated maidenhead is
confusing things ]
Unfortunately I do not have a recording of this to post back ...
The screen is going nuts here with PM's so it needs be reported.
73
Steve I
VK3VM / Vk3SIR
_______________________________________________
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
