On Mon, Jun 13, 2011 at 17:06, Marcus D. Leech wrote:
> As long as overruns aren't happening *frequently* (like more than once
> every few dozen higher-layer-data-frames), then one can regard
> such interrupts in data flow as equivalent to channel noise, which is
> something you have to cope wi
Is the data coming in the buffer FIFO? Is there a way to keep track of
how much data is lost?
Yes, the data are delivered FIFO.
In UHD, you can arrange for there to be timestamps on the data, so you
could look at the data and detect interruptions in the
monotonicity.
As long as overruns a
Is the data coming in the buffer FIFO? Is there a way to keep track of how
much data is lost?
On Mon, Jun 13, 2011 at 6:35 PM, Marcus D. Leech wrote:
> Hi,
>> What happens to the incoming data from USRP, over the USB bus, when a
>> gnuradio block takes a lot of time to process its output? Is the
Hi,
What happens to the incoming data from USRP, over the USB bus, when a
gnuradio block takes a lot of time to process its output? Is the data
buffered indefinitely or is it dropped as new samples come in case the
consumption rate is slow.
Thanks
That's what's called an "overrun". Data gets
GNURadio will indicates that overruns are occuring via the console. I
believe it is the u0 character.
On Mon, Jun 13, 2011 at 3:51 PM, John Andrews wrote:
> Hi,
> What happens to the incoming data from USRP, over the USB bus, when a
> gnuradio block takes a lot of time to process its output? Is
Hi,
What happens to the incoming data from USRP, over the USB bus, when a
gnuradio block takes a lot of time to process its output? Is the data
buffered indefinitely or is it dropped as new samples come in case the
consumption rate is slow.
Thanks
___
Di
