Sorry, I sent this message in a garbled form.
Meant to delete the line "Suppose all data symbols in the wrong", just
above the last paragraph.
-- Joe
On 11/2/2015 4:10 PM, Joe Taylor wrote:
> Hi Steve,
>
> On 11/2/2015 3:59 PM, Steven Franke wrote:
>> Wait. What? Very cool example, but I’m confused.
>>
>> When the user changes messages in mid-stream, my assumption
>> was that the program would jump to the beginning of the new
>> message symbol-stream, i.e. start at the beginning of a new
>> message. But then the second message would decode with a
>> big dt, which doesn’t show on your screenshot. So is the
>> program smart enough to just seamlessly start sending the
>> new symbols while retaining continuity on the sync sequence?
>
> Correct. The sync sequence continues un-interrupted; only the data
> symbols are changed.
>
> Let's say the Tx message was changed half-way through, at about t=25s.
> Data symbols up to that time -- say, 31 of them -- correspond to the
> first message. The remaining 32 data symbols will be those of the
> second message. All 63 sync symbols are as they should be for a normal
> (unmodified) message.
>
> Suppose all data symbols in the wrong
> The signal was pretty strong, so data symbols in the "right" half of the
> message are nearly all received without error. Those in the "wrong"
> half nearly all produce a hard error. Still, that's only about 30 hard
> errors -- so there's a good chance that sfrsd will decode both messages
> correctly.
>
> -- Joe, K1JT
>
> ------------------------------------------------------------------------------
> _______________________________________________
> 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
