[Discuss-gnuradio] Digital scope usrp code

2006-06-08 Thread Moritz von Buttlar
Hi ! I'm planing to use the usrp as a 4-channel 64 MHz transient recorder. Has anybody done something like that so far ? Also, I want to send a stimulus signal with the usrp (e.g. a chirp) and then record the response of my system. The RX channels have to be synchronized to the TX channels. A

[Discuss-gnuradio] gr.feval_ff

2006-06-08 Thread Eric Blossom
I've justed added 3 classes (not GR blocks) that allow C++ code to evaluate functions defined in Python. This isn't for performance critical things, but will be useful in certain situations. It uses SWIG "directors" to perform the magic. Basically you subclass gr.feval_{dd,cc,ll} in python and d

[Discuss-gnuradio] Re: Wav transmitter / intro to Tx with USRP

2006-06-08 Thread Eric Blossom
On Thu, Jun 08, 2006 at 01:23:23AM -0500, Brett L Trotter wrote: > I've got a copy of dsb_tx and tx_am here, if I took my stereo 16bit > signed PCM 48kHz wav file and ran it through sox and turned it into a > 48khz mono raw file (no headers), what would I need to do to transmit it > with either of

Re: [Discuss-gnuradio] Comments on "BBN's Proposed extensions for data networking"

2006-06-08 Thread Eric Blossom
On Thu, Jun 08, 2006 at 02:27:34PM +0100, John Aldridge wrote: > Michael Dickens wrote: > >>In reality, it will work with any C++ element for which memcpy is a > >>valid copy constructor. This includes many structures and classes, > >>but not all. > > I.e. those things which the C++ standard call

Re: [Discuss-gnuradio] Comments on "BBN's Proposed extensions for data networking"

2006-06-08 Thread John Aldridge
Michael Dickens wrote: In reality, it will work with any C++ element for which memcpy is a valid copy constructor. This includes many structures and classes, but not all. I.e. those things which the C++ standard calls "POD types" (see section 3.9 paras 2 & 10)? -- John ___

Re: [Discuss-gnuradio] Comments on "BBN's Proposed extensions for data networking"

2006-06-08 Thread Michael Dickens
* p56, 4.6.4: "These items are typically floats, doubles or complex values." --> I would rewrite this to state that "These items can be any standard C/C++ element, including ints, floats, doubles, complex values, and even structs." Yes, I've done testing on structs and it's possible to send thos

Re: [Discuss-gnuradio] Comments on "BBN's Proposed extensions for data networking"

2006-06-08 Thread David Lapsley
Eric Blossom wrote: On Thu, Jun 08, 2006 at 12:38:02AM -0400, David Lapsley wrote: --> These seem in conflict with each other. Further, the only obvious reference in 4.8.2 to the relinquishing of control is the "yield()" function. Maybe: The "gr single threaded scheduler" is run in a separat