On 03/03/2015 00:22, Joe Taylor wrote:
> Hi Bill,
Hi Joe,
>
> On 3/2/2015 5:45 PM, Bill Somerville wrote:
>> to anyone using the test version linked below. I would advise not using
>> it on air as there is a flaw in my proposal.
>>
>> The messages like:
>>
>> DE TI4/N0URE R-10
>>
>> will not work because the report will not be collected at the far end :(
> Not sure why you say this.  As described in the WSJT-X User Guide,
> http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main.html#COMP-CALL
> messages like  "DE TI4/N0URE R-10" are legitimate in WSJT-X.  Here's the
> output from jt9code showing that this is so:
The message is indeed a valid standard message but that is not the 
issue. The issue is that current software will not extract the report 
from a message that doesn't contain the DE call. My plan was to make 
auto  generated messages work for everyone including those who have 
older different versions. My proposal would have caused incorrect 
reports to be logged at the DX end of a type 2 call holders QSOs :(
>
> $ jt9code "DE TI4/N0URE R-10"
> Message                 Decoded                 Err?
> -----------------------------------------------------------------
> DE TI4/N0URE R-10       DE TI4/N0URE R-10           4: Type 2 pfx
>
> Channel symbols
>    0 0 5 5 0 4 4 6 5 0 2 3 6 6 3 0 3 8 3 7 7 4 0 1 8 5 1 6 2 5
>    6 5 0 8 0 5 3 5 8 5 6 1 2 7 4 6 7 6 2 1 0 0 5 1 0 3 1 7 4 0
>    2 4 8 1 6 0 6 7 7 5 2 2 0 7 3 1 6 8 1 2 7 5 0 7 0
>
> Similarly, from JT65code:
>
> $ jt65code "DE TI4/N0URE R-10"
> Message                 Decoded                 Err?
> -----------------------------------------------------------------
> DE TI4/N0URE R-10       DE TI4/N0URE R-10           4: Type 2 pfx
>
> Packed message, 6-bit symbols  63 46 62  3  3 55 38 50 37 23 58 57
>
> Information-carrying channel symbols
>      26 24 63 11  6 51 23 33  5 57 15  4 28 54  0  1 30 30  5  2  4
>      63 23 57 28  9 12 13 20 58 63 35 31 45 52 10  1 42 36 45  5 41
>       7  4 23 37 34  8 57 10 43 63 46 62  3  3 55 38 50 37 23 58 57
>
> The only possible downside of using these messages with a "Type 2"
> prefix/suffix is that other "JT-compatible" programs (JT65-HF, etc.) may
> not decode the messages correctly.
And WSJT-X :(
>
>       -- Joe. K1JT
73
Bill
G4WJS.

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to