[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [USRP-users] Re: Question on the usrp

From: Marcus D. Leech
Subject: Re: [USRP-users] Re: Question on the usrp
Date: Thu, 05 Aug 2021 08:25:20 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0

On 08/05/2021 07:45 AM, Daniel Ozer wrote:
Hi about this question im using gnuradio and its the one who call the recv function in the background and i cant access that part of the code. Do you know a way I can get the interrupt within a block of gnuradio while I'm not the one who call the recv function

3. While using high sample rate 50M+ i saw that once in a while  'D' is written to the terminal . How can get an interrupt that indicates that a packet has lost ? Is it one packet every time or only some of the packet not arriving ? Is there a way to make sure that packets won't lost ?
The recv() call returns metadata that includes an error code.  See:


In which case, you want to look at the tags produced by the gr-uhd interface:


Whenever an overrun type event happens, gr-uhd inserts a fresh timestamp into the tag stream associated with the sample stream.  That allows
  you to:

  (A) Infer that an over-run type event occurred
  (B) Know how many samples were dropped--by computing the difference between what the expected timestamp should be and what
        it actually is in the timestamp tag.

I've cross-posted to discuss-gnuradio, where there's a bigger audience for Gnu Radio questions.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]