Brett L. Trotter wrote:
Got a few good replies on my question about lost bytes. I appreciate the
input, that sounds like it'll work great in conjunction with the error
correction then. I'm hoping to have that in place within the next couple
of hours and start testing.
Two words ... preambles
Got a few good replies on my question about lost bytes. I appreciate the
input, that sounds like it'll work great in conjunction with the error
correction then. I'm hoping to have that in place within the next couple
of hours and start testing.
___
Disc
--- "Brett L. Trotter" <[EMAIL PROTECTED]> wrote:
> But the thought was, what if a byte is completely obliterated- then
> everything would be shifted over one (or more) and my groupings
> wouldn't align
No it's not like that. The transmitter clocks out
bits at a fixed rate. When some of the
--- "Brett L. Trotter" <[EMAIL PROTECTED]> wrote:
> But the thought was, what if a byte is completely obliterated- then
> everything would be shifted over one (or more) and my groupings
> wouldn't align
No it's not like that. The transmitter clocks out
bits at a fixed rate. When some of the
nuradio@gnu.org
Subject: Re: [Discuss-gnuradio] lost bytes and reed-solomon
Brett L. Trotter wrote:
> I'm working on a self-educational project to replace the simple CRC in
> the tunnel apparatus with a very heavy reed-solomon encoding for very
> lossy and low-bandwidth links. On
Brett L. Trotter wrote:
> I'm working on a self-educational project to replace the simple CRC in
> the tunnel apparatus with a very heavy reed-solomon encoding for very
> lossy and low-bandwidth links. One thought just occurred to me.
> Originally, I was going to group up all of my data in 127 byte
I'm working on a self-educational project to replace the simple CRC in
the tunnel apparatus with a very heavy reed-solomon encoding for very
lossy and low-bandwidth links. One thought just occurred to me.
Originally, I was going to group up all of my data in 127 byte blocks,
r/s encode it with a 25
