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

[Marcus D. Leech]

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:

https://files.ettus.com/manual/structuhd_1_1rx__metadata__t.html

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

https://www.gnuradio.org/doc/doxygen-3.7.2/group__uhd__blk.html

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.