Hello David,

I was facing the exact same issue, and the fix I use is identical to yours.
I consume 4 symbols less than I need to, so the subsequent packet is not
lost.

Best,
Aditya



On Tue, Jan 21, 2014 at 11:14 AM, David Halls
<david.ha...@toshiba-trel.com>wrote:

> Hi Martin,
>
> Making good progress with the relay but on another topic, I find if I use
> a random data source (rather than the 1...range in the original example)
> the trigger signal arrives occasionally one or two samples earlier than
> expected.
>
> Say we have 96B data this gives 768/48 = 16 data symbols. Adding 3
> preamble gives 19×80 samples = 1520. Sometimes there are only 1519 or 1518
> samples between triggers.
>
> This means that in the HPD code, too many items are consumed by the
> processing of the previous packet and thus the next trigger = 1 item is
> consumed in error so it is never found.
>
> A simple hack is to consume 'x' fewer samples in the HPD code I.e. In the
> line
>
> consume_each (d_header_len * (d_items_per_symbol + d_gi));
>
> And the equivalent in the payload case, we can append ' - 3'
> A slightly more robust way would be to check where the next trigger occurs
> and remove the corresponding number of times.
>
> Are you able to recreate this issue? I realise that the problem only
> occurs when using a different data source than the standard demo, so of
> course it's not a bug as such at all.
>
> Many thanks,
>
> David
>
> ________________________________
>
> NOTE: The information in this email and any attachments may be
> confidential and/or legally privileged. This message may be read, copied
> and used only by the intended recipient. If you are not the intended
> recipient, please destroy this message, delete any copies held on your
> system and notify the sender immediately.
>
> Toshiba Research Europe Limited, registered in England and Wales
> (2519556). Registered Office 208 Cambridge Science Park, Milton Road,
> Cambridge CB4 0GZ, England. Web: www.toshiba.eu/research/trl
>
>
> ------------------------------
> This email has been scanned for email related threats and delivered safely
> by Mimecast.
> For more information please visit http://www.mimecast.com
> ------------------------------
>
> _______________________________________________
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Reply via email to