Re: [Discuss-gnuradio] USRP1 full C++ API update merged into trunk
On Sat, 2008-12-27 at 22:01 -0500, Marcus D. Leech wrote: > This code worked as of a couple of weeks ago: > > self.subdev[0].set_bw(lbw) Okay, I'll dig into it. -Johnathan ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] USRP1 full C++ API update merged into trunk
Johnathan Corgan wrote: > On Sat, 2008-12-27 at 20:55 -0500, Marcus D. Leech wrote: > > >> I just re-built from the latest trunk SVN (complete re-build, including >> complete SVN co), and the usrp objects still >> don't have a set_bw() method in Python. >> > > The set_bw() is a method on the daughterboard, not USRP. > > -Johnathan > > > This code worked as of a couple of weeks ago: self.subdev[0].set_bw(lbw) It now provokes: File "/usr/local/lib64/python2.5/site-packages/gnuradio/wxgui/stdgui2.py", line 60, in __init__ self.panel = stdpanel (self, self, top_block_maker) File "/usr/local/lib64/python2.5/site-packages/gnuradio/wxgui/stdgui2.py", line 81, in __init__ self.top_block = top_block_maker (frame, self, vbox, sys.argv) File "/usr/local/bin/usrp_ra_receiver.py", line 439, in __init__ self.subdev[0].set_bw(lbw) AttributeError: 'db_base_sptr' object has no attribute 'set_bw' -- Marcus Leech Principal Investigator, Shirleys Bay Radio Astronomy Consortium http://www.sbrac.org ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] USRP1 full C++ API update merged into trunk
On Sat, 2008-12-27 at 20:55 -0500, Marcus D. Leech wrote: > I just re-built from the latest trunk SVN (complete re-build, including > complete SVN co), and the usrp objects still > don't have a set_bw() method in Python. The set_bw() is a method on the daughterboard, not USRP. -Johnathan ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] USRP1 full C++ API update merged into trunk
Johnathan Corgan wrote: > On Thu, Dec 25, 2008 at 11:21 PM, Johnathan Corgan > wrote: > > >>> But I'm also running into a problem with set_bw() not being recognized >>> as an attribute of >>> a USRP object. Did this get missed? >>> >> Yep, sure did (at least from the Python API). I'll fix in the morning. >> > > This is done, please update and let me know how it works for you. > > -Johnathan > > I just re-built from the latest trunk SVN (complete re-build, including complete SVN co), and the usrp objects still don't have a set_bw() method in Python. -- Marcus Leech Principal Investigator, Shirleys Bay Radio Astronomy Consortium http://www.sbrac.org ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Upgrade (downgrade?) to a Q6600 CPU
Can we implement some block in FPGA to reduce the CPU consumption? Have any work like this done already ? Thanks Jing On Mon, Dec 15, 2008 at 12:36 PM, Johnathan Corgan wrote: > On Fri, Dec 12, 2008 at 4:48 PM, Marcus D. Leech wrote: > >> I think what's happening is that the I/O thread is going as fast as it >> can, but it just isn't fast enough to service the >> data coming off of the USB. Could it also be that my USB subsystem is >> just not that good? > > You can try running the usrp_benchmark_usb.py example to see if your > USB is not handling the highest data rate of 32 MB/sec. But it isn't > likely that the USB is the issue. > > Are you familiar with the 'oprofile' profiler? > > -Johnathan > > > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] which Options shall i enable
On Sat, Dec 27, 2008 at 09:46:47AM -0800, Eric Blossom wrote: > On Sat, Dec 27, 2008 at 05:27:35AM +0100, Markus Feldmann wrote: > > > > My last Options were, > > ./configure --enable-gnuradio-core --enable-usrp --enable-usrp2 > > --enable-gr-usrp --enable-gr-usrp2 --enable-doxygen --enable-grc > > > > My Gnu Radio has 2 Basic Receivers, 1 LF Receiver and 1 LF Transmitter. > > The Motherboard is an USRP Board. > > > > Regards Markus > > If you don't specify any options, it will build all of the parts that > it finds the prerequisites form. That's the usual approach. > > The doxygen docs are only built if explicitly requested, so specify > --enable-doxygen if you want those. They're off by default because > they take quite a while to build. > > Thus, in your case: > > ./configure --enable-doxygen > > should get you what you want. When configure is done, it will print > out lists of which modules will get build and which ones won't. Check > the list of of what's getting built to ensure that it's got everything > in it that you want. > > Your list above looks fine, though unless you've got a USRP2 you don't > need --enable-usrp2 or --enable-gr-usrp2. > > Eric Actually you'll need one of the audio interfaces. It's probably building gr-audio-alsa by default, so I expect everything is still OK. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] which Options shall i enable
On Sat, Dec 27, 2008 at 05:27:35AM +0100, Markus Feldmann wrote: > Hi All, > > i just downloaded and compiled Gnu Radio from Trunk, but > i am not sure which Option i have to use? > Or which Option should be useful for Gnu Radio Companion. > > I want the use the Gnu Radio Companion to build an FM and AM-Radio.. > > My System is a Debian Sid 386 System with AMD Athlon CPU. > > My last Options were, > ./configure --enable-gnuradio-core --enable-usrp --enable-usrp2 > --enable-gr-usrp --enable-gr-usrp2 --enable-doxygen --enable-grc > > My Gnu Radio has 2 Basic Receivers, 1 LF Receiver and 1 LF Transmitter. > The Motherboard is an USRP Board. > > Regards Markus If you don't specify any options, it will build all of the parts that it finds the prerequisites form. That's the usual approach. The doxygen docs are only built if explicitly requested, so specify --enable-doxygen if you want those. They're off by default because they take quite a while to build. Thus, in your case: ./configure --enable-doxygen should get you what you want. When configure is done, it will print out lists of which modules will get build and which ones won't. Check the list of of what's getting built to ensure that it's got everything in it that you want. Your list above looks fine, though unless you've got a USRP2 you don't need --enable-usrp2 or --enable-gr-usrp2. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Another GSM project
http://events.ccc.de/congress/2008/Fahrplan/events/3007.en.html Philip ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
