Hi Bill,

That's clear, I should have checked available report range first, many thanks 
for the explanation.

Do you plan to make special message AP mask working in FT8 decoder? In current 
version there is necessary code missed in ft8apset.f90 to generate  proper 
apsym() array to special messages. In result wrong masks being applied in 
ft8b.f90.

Have a great afternoon&evening there,
73 Igor


>Четверг, 28 ноября 2019, 16:33 +03:00 от Bill Somerville 
><[email protected]>:
>
>On 28/11/2019 10:25, Игорь via
>      wsjt-devel wrote:
>>Hi Joe,
>>.
>>Just in case this behavior has not yet been reported to the team,
>>      looks like all WSJT-X 2.1.x versions are affected:
>>.
>>transmitting:  UA3DJY RR73; K1JT <KH1/KH7Z> -11
>>decoding:      UA3DJY RR73; K1JT <KH1/KH7Z> -12
>>.
>>where signal report is broken.
>>.
>>73,
>>Igor UA3DJY
>Hi Igor,
>that is an invalid message, you can check this with the ft8code
>      application shipped with WSJT-X:
>>ft8code "UA3DJY RR73; K1JT <KH1/KH7Z> -11"
>    Message                               Decoded                             
> Err i3.n3
>----------------------------------------------------------------------------------------------------
> 1. UA3DJY RR73; K1JT <KH1/KH7Z> -11      UA3DJY RR73; K1JT <KH1/KH7Z> -12     
>  *  0.1 DXpedition mode
>
>Message bits:
>11011001011001000000100100000000100110111111100110111001001100100101001001000
>
>Channel symbols (tones):
>3140652443430110011677164321133302553140652055776737626476617233270722273140652
>
>Note the error marker '*'. OTOH this is a valid message:
>>ft8code "UA3DJY RR73; K1JT <KH1/KH7Z> -12"
>    Message                               Decoded                             
> Err i3.n3
>----------------------------------------------------------------------------------------------------
> 1. UA3DJY RR73; K1JT <KH1/KH7Z> -12      UA3DJY RR73; K1JT <KH1/KH7Z> -12     
>     0.1 DXpedition mode
>
>Message bits:
>11011001011001000000100100000000100110111111100110111001001100100101001001000
>
>Channel symbols (tones):
>3140652443430110011677164321133302553140652055776737626476617233270722273140652
>
>FT8 software should not be generating that invalid message .
>      Note the message is invalid because only five message bits are
>      available for reports in this type of message, the reports should
>      be adjusted to the nearest even dB point between -30dB and +32dB
>      inclusive. It is your choice whether to round or truncate, WSJT-X
>      truncates to the next lower even dB value.
>73
>Bill
>G4WJS.


-- 
Игорь
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to