As far as the usrp->gnuradio block goes - the frame to stream 'conversion' happens in the usrp (or usrp2) source block (and on the tx side that similarly gets hidden by the sink block). You can look in the gr-usrp (or gr-usrp2) directories to see how that happens. But in general, you don't have to worry about what format the samples get to/from the usrp in, that's taken care of by the gr-usrp blocks.
For learning about some of the basics of GNURadio, I'd recommend looking at some of the simpler examples (802.11 is not the simplest standard to deal with) in the gnuradio-examples directories (the digital-bert example for example). On Wed, Aug 26, 2009 at 7:23 AM, Ulrika Uppman<[email protected]> wrote: > Thank you very much for your explenation Colby! I now understand how the > message queue is used in the rx code. > > However, I would still like to know more about how the data is transported > between for example the usrp block and the next block (in the 802.11b rx case > this would be the resampling block). If I understand it right, the usrp sends > frames of data including a header, timestamp and a number of data samples. > When connecting the blocks in the python code, where does the transformation > from frames into a stream happen? I've tried to read the code and > documentation about the connection and starting of flow graphs, but I could > still use some hints... > > Tnx, > /Ulrika > -- Doug Geiger [email protected] _______________________________________________ Discuss-gnuradio mailing list [email protected] http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
