[Top][All Lists]

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

Re: [Discuss-gnuradio] Threaded c++ only USRP "cfile" dump

From: Ian Larsen
Subject: Re: [Discuss-gnuradio] Threaded c++ only USRP "cfile" dump
Date: Wed, 22 Aug 2007 19:31:01 -0400


This looks great, how does it work out in practice?
Does simply adding extra buffering in a separate thread eliminate all
overruns?  Do you know the lower limit on how much buffer space you

If that's the case, it might be possible to implement a Buffer
component that could be used from python that does the same thing, if
I'm not mistaken.


On 8/20/07, Chris Stankevitz <address@hidden> wrote:
> Recently I have been asking questions about overruns, threaded blocks,
> and c++ only USRP reading.  My application requires uninterrupted data,
> which I was unable to get from the USRP with my laptop, even just
> recording data to a file_sink.  Attached is a program that records data
> from the USRP.  It is entirely in c++ and uses threads to prevent losing
> data by writing to the hard drive while it reads from the USRP.
> Thanks to Ian Larsen for a C++-only USRP example and to Greg Heckler for
> the DBSRX c++ driver.
> In addition to the attached, you also need db_dbs_rx.cpp and db_dbs_rx.h
> from http://lists.gnu.org/archive/html/patch-gnuradio/2007-08/msg00000.html
> Compile with -lusrp and -lpthread
> Chris
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio

My PGP Public Key:

reply via email to

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