[ADXA] Question on FT8 Identifiers/reports

[Pat Patterson]

Scott
Looks like a random noise decode to me. While the calls may match the
structure of a valid call, neither are found in a QRZ search.  With deep
decoding WSJT-x is trying hard to find something valid.   A long runing
stream of random noise bits will eventually yield a match of some valid
structure for a decode.  It happens more frequently on 2M MSK144 with the
SH option enabled.   SH is used for the Tx3, Tx4 and Tx5. It sends a
shorter packet of only about 28 bits with compressed representations of
calls. Report and RR73 and 73.  It doesn't take long for a string of noise
bits to match a valid message structure.  Hope I've explained it clearly.

73,
Pat. W5VY

On Wed, Dec 2, 2020, 10:28 AM <sbranyan at cox.net> wrote:

> Lately, I've noticed more use of different identifiers after callsigns in
> FT8.
>
>
>
> Such as TU; OL9MKZ 8Q2BVK 529 4295
>
>
>
> The TU; I took as occurring on FT8 F/H. But not sure. I was not in F/H
> mode.
>
>
>
> Any help on what's going on?
>
>
>
> Thanks.
>
>
>
> 73,
>
>
>
> Scott/W5AAJ
>
>
>
>
>
>
> ______________________________________________________________
> ADXA mailing list
> Home: http://mailman.qth.net/mailman/listinfo/adxa
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:ADXA at mailman.qth.net
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qth.net/pipermail/adxa/attachments/20201202/06a4eb6c/attachment.html>