Re: [Discuss-gnuradio] Detecting underflows with uhd_usrp_sink

> > Ok, makes sense. So lets say I scheduled 20 minutes of bursts (1 second > period with 50/50 duty cycle) and I started the flowgraph 10 minutes > late. With the "next_burst" policy, could I rely on the USRP to > dutifully drop all late bursts? Are the packets dropped in the Ethernet > buffer o

Re: [Discuss-gnuradio] Detecting underflows with uhd_usrp_sink

On 06/10/2013 01:17 PM, Josh Blum wrote: On 06/10/2013 09:43 AM, Sean Nowlan wrote: Do late packets always get dropped by the USRP? What happens if its buffers get filled up with samples, all of which are late? The stream args have a policy parameter. Also, these args can be set from a parame

Re: [Discuss-gnuradio] Detecting underflows with uhd_usrp_sink

On 06/10/2013 09:43 AM, Sean Nowlan wrote: > Do late packets always get dropped by the USRP? What happens if its buffers > get filled up with samples, all of which are late? The stream args have a policy parameter. Also, these args can be set from a parameter in the USRP GRC blocks, as well as

Re: [Discuss-gnuradio] Detecting underflows with uhd_usrp_sink

See this post in context http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/2012-September/005352.html On Mon, Jun 10, 2013 at 7:13 AM, Marcus Leech wrote: > I believe that they are all dropped, but Josh can comment more > definitively. > > > on Jun 10, 2013, *Sean Nowlan* wrote: > >

Re: [Discuss-gnuradio] Detecting underflows with uhd_usrp_sink

I believe that they are all dropped, but Josh can comment more definitively.   on Jun 10, 2013, Sean Nowlan wrote: Do late packets always get dropped by the USRP? What happens if its buffers get filled up with samples, all of which are late?"Marcus D. Leech" wrote:>> L = late p

Re: [Discuss-gnuradio] Detecting underflows with uhd_usrp_sink

Do late packets always get dropped by the USRP? What happens if its buffers get filled up with samples, all of which are late? "Marcus D. Leech" wrote: >> L = late packet, there was a time on the packet which was> time on >> device when >> >> >There are two different "cases" for late packets h

Re: [Discuss-gnuradio] Detecting underflows with uhd_usrp_sink

L = late packet, there was a time on the packet which was> time on device when There are two different "cases" for late packets happening. The first is that you haven't sent your packet far enough in advance to account for latency variations on the host. Unfortunately, on a general-purpose

Re: [Discuss-gnuradio] Detecting underflows with uhd_usrp_sink

On 06/08/2013 02:26 PM, Juha Vierinen wrote: > Hi, > > I've recently been working with a coded CW radar system that just loops > over a fairly long IQ vector. It works all fine for a while, but after a > few days, the transmission timing has drifted away from where it should be. > I'm comparing

[Discuss-gnuradio] Detecting underflows with uhd_usrp_sink

Hi, I've recently been working with a coded CW radar system that just loops over a fairly long IQ vector. It works all fine for a while, but after a few days, the transmission timing has drifted away from where it should be. I'm comparing the leading edge of the transmit waveform with the PPS prov