Re: [Discuss-gnuradio] Detecting transmit underruns on UHD

[Josh Blum]

On 09/02/2010 01:46 PM, Eric Schneider wrote:
> Oh cool! When was that implemented? I missed it...

http://old.nabble.com/UHD-Announcement---August-16th-2010-td29457066.html

> I assume there is no problem with timeout = 0?

should be fine

> Is the interface thread safe? read/write/recv_async?

You can have a separate thread for send, recv, async recv, control 
(sets/gets). So thats fine, but dont (for example) use multiple threads 
to call send, or multiple threads to set properties.

-josh

> --Eric
>
> On Thu, 2010-09-02 at 13:23 -0400, Josh Blum wrote:
> > See recv async message:
> > http://www.ettus.com/uhd_docs/doxygen/html/classuhd_1_1device.html#afe4ec312d71c669fbd86ce9a7d350605
> >
> > And the async metadata:
> > http://www.ettus.com/uhd_docs/doxygen/html/structuhd_1_1async__metadata__t.html
> >
> > -Josh
> >
> > On 09/02/2010 12:58 PM, Marc Epard wrote:
> > > With UHD, how can I programmatically detect when transmit underruns have 
> > > occurred?
> > >
> > > I see Us in the output both on the host and from the USRP2 serial port, but I 
> > > haven't spotted an API to test for this condition.
> > >
> > > -Marc
> > >
> > >
> > > _______________________________________________
> > > Discuss-gnuradio mailing list
> > > address@hidden
> > > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> >
> > _______________________________________________
> > Discuss-gnuradio mailing list
> > address@hidden
> > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio