[Discuss-gnuradio] Re: GRC graphical sink buffer size - how to increase?
Youll probably want to install more current gnuradio from the development trunk or possibly the 3.2 release candidate. Enable the GL sinks: http://gnuradio.org/trac/wiki/CompGrWxgui#GLSinks The opengl scope has a lot more capability including the time scaling you need. Also grc comes with this gnuradio versions, so dont bother with 0.7, its old and dead. http://gnuradio.org/trac/wiki/GNURadioCompanion -Josh Richard Clarke wrote: Hi, I'm using GRC 0.7 at the moment. I am using the Scope graphical sink to try and display the output of calculation on a complex baseband signal @ 250Kthat gives the magnitude squared (i.e power envelope). Ideally I want to be able to display approximately 100ms of the signal at a time in the scope window, however it seems to default to showing the waveform over only approx 8ms (2000 samples). The scope has a sample rate of 250K set. Changing the scopes sampling rate only changes the calculated timescale of the graph. Does the scope block, when used via the GRC UI, use a fixed input buffer size? Is there a simple way to overcome this and still use GRC or do I need to construct the flow graph manually? Thanks very much. Cheers Richard ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] GNU Radio 3.2 Release Candidate 2 available for testing
On Fri, Apr 17, 2009 at 7:25 PM, Eric Blossom e...@comsec.com wrote: On Fri, Apr 17, 2009 at 07:04:25PM -0700, Karthik wrote: On Tue, Apr 14, 2009 at 3:23 PM, Johnathan Corgan jcor...@corganenterprises.com wrote: GNU Radio 3.2 release candidate 2 is now available for download and testing: http://gnuradio.org/releases/gnuradio/gnuradio-3.2rc2.tar.gz http://gnuradio.org/releases/gnuradio/gr-howto-write-a-block-3.2rc2.tar.gz The associated firmware and FPGA bitstream images for the USRP2 are: http://gnuradio.org/releases/usrp2-bin/release/txrx_edk10.1_r3.2rc2.bin http://gnuradio.org/releases/usrp2-bin/release/u2_rev3_ise10.1sp3_r3.2rc2.bin This release contains all the features, fixes, and bugs of the GNU Radio development trunk as of 4/14/09. Our goal is for this to be the last release candidate before the formal 3.2 release. Those of you with your own GNU Radio projects who wish to stabilize on the 3.2.x API should begin using the above instead of the development trunk. We will be making changes to the trunk software that will break API compatibility soon after the formal release. As always, we will maintain the 3.2.x series of releases such that upgrades to newer releases will not break existing code. In addition, to the extent possible, we will merge and release selected functionality from the development trunk that is consistent with this requirement. Johnathan Corgan Corgan Enterprises LLC Here is my setup: OS: Ubuntu 8.04 USRP1 with 2 LFRX and 2LFTX daughterboards I primary use the USRP as a 4 channel Digitizer and have been running gnuradio-3.1.3 without any problems so far. To test 3.2rc2 I tried running the multi_fft.py which is available in the gnuradio-examples/python/multi-antenna/ directory. I commented out the portion which checks for the the number of channels available and the daughterboard ID since I didn't have the BASIC_RX. Here is the major change that I found. The value of len(self.subdev) = 4 in 3.1.3 and =6 in 3.2rc2. Shouldn't this be 4 as it was previously? Thanks for pointing this out. Fixed in [10877] to work with old and new handling of Basic Rx d'boards. Eric I checked out the trunk and tried compiling the code. I get the following error message in in the middle of the compile. I have tried compiling the latest trunk and also R10877 and still get the same error. I did the regular ./bootstrap and used ./configure --enable-doxygen --with-boost=/opt/boost_1_36 --enable-usrp2=no --enable-gr-usrp2=no g++ -g -O2 -g -O2 -pthread -pthread -Wall -Woverloaded-virtual -o .libs/test_inband test_inband.o ./.libs/libusrp-inband-qa.so /home/anankekarthik/gnuradio/usrp/host/lib/inband/.libs/libusrp-inband.so.0: undefined reference to `usrp_standard_rx::tune(int, boost::shared_ptrdb_base, double, usrp_tune_result*)' /home/anankekarthik/gnuradio/usrp/host/lib/inband/.libs/libusrp-inband.so.0: undefined reference to `usrp_standard_tx::tune(int, boost::shared_ptrdb_base, double, usrp_tune_result*)' /home/anankekarthik/gnuradio/usrp/host/lib/inband/.libs/libusrp-inband.so.0: undefined reference to `usrp_standard_rx::determine_rx_mux_value(usrp_subdev_spec const)' /home/anankekarthik/gnuradio/usrp/host/lib/inband/.libs/libusrp-inband.so.0: undefined reference to `usrp_standard_tx::determine_tx_mux_value(usrp_subdev_spec const)' /home/anankekarthik/gnuradio/usrp/host/lib/inband/.libs/libusrp-inband.so.0: undefined reference to `usrp_basic::selected_subdev(usrp_subdev_spec const)' /home/anankekarthik/gnuradio/usrp/host/lib/inband/.libs/libusrp-inband.so.0: undefined reference to `db_base::dbid()' Karthik ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] GRC:Suitable Sink required
Hi, I am trying to implement a periodogram in gnu radio. http://img25.imageshack.us/img25/1606/powerdetectorgrc.png Currently, I am stuck in deciding what sink i should use and how. I want the output in the the form of an array so that I can have calculations on the periodogram samples. As the input are the realtime complex baseband samples from the USRP (here shown with a signal source), thus the sink should be flexible enough to be updated. Thus I think that a fixed length float vector sink doesnt suits here. I dont know how to proceed from here :-) Regards, Ali ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] GRC:Suitable Sink required
You should probably start by looking at the existing wx gui sinks, copy and modify one: http://gnuradio.org/trac/browser/gnuradio/trunk/gr-wxgui/src/python The vector sink is not what you want here. -Josh Saleem Akhtar wrote: Hi, I am trying to implement a periodogram in gnu radio. http://img25.imageshack.us/img25/1606/powerdetectorgrc.png Currently, I am stuck in deciding what sink i should use and how. I want the output in the the form of an array so that I can have calculations on the periodogram samples. As the input are the realtime complex baseband samples from the USRP (here shown with a signal source), thus the sink should be flexible enough to be updated. Thus I think that a fixed length float vector sink doesnt suits here. I dont know how to proceed from here :-) Regards, Ali ___ 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] GRC:Suitable Sink required
Thanks, but i dont want to use GUI sink. I want to get an array of samples which represent the periodogram. So that i can do further processing on them. Regards From: Josh Blum j...@joshknows.com Subject: Re: [Discuss-gnuradio] GRC:Suitable Sink required To: Saleem Akhtar saleemakhta...@yahoo.com Cc: discuss-gnuradio@gnu.org Date: Monday, April 20, 2009, 3:55 AM You should probably start by looking at the existing wx gui sinks, copy and modify one: http://gnuradio.org/trac/browser/gnuradio/trunk/gr-wxgui/src/python The vector sink is not what you want here. -Josh ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] GRC:Suitable Sink required
You can use a file sink to write the samples out to a file, and write some program to process the file. Or, you need to create your own block in c++ or python. If c++, the how to write a block example is a good reference. If python, the wxgui sinks are a good reference (see gr.message_sink and gr.msg_queues to get data out of the stream and into python). -Josh Saleem Akhtar wrote: Thanks, but i dont want to use GUI sink. I want to get an array of samples which represent the periodogram. So that i can do further processing on them. Regards From: Josh Blum j...@joshknows.com Subject: Re: [Discuss-gnuradio] GRC:Suitable Sink required To: Saleem Akhtar saleemakhta...@yahoo.com Cc: discuss-gnuradio@gnu.org Date: Monday, April 20, 2009, 3:55 AM You should probably start by looking at the existing wx gui sinks, copy and modify one: http://gnuradio.org/trac/browser/gnuradio/trunk/gr-wxgui/src/python The vector sink is not what you want here. -Josh ___ 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] GRC:Suitable Sink required
Thanks! I will look into it. --- On Mon, 4/20/09, Josh Blum j...@joshknows.com wrote: From: Josh Blum j...@joshknows.com Subject: Re: [Discuss-gnuradio] GRC:Suitable Sink required To: Saleem Akhtar saleemakhta...@yahoo.com Cc: discuss-gnuradio@gnu.org Date: Monday, April 20, 2009, 4:37 AM You can use a file sink to write the samples out to a file, and write some program to process the file. Or, you need to create your own block in c++ or python. If c++, the how to write a block example is a good reference. If python, the wxgui sinks are a good reference (see gr.message_sink and gr.msg_queues to get data out of the stream and into python). -Josh ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
