RE: [Discuss-gnuradio] Question about UHD output data type.
Hi, The range of an int16 is +/-2^15, the minimum step is 1 because its an integer. Did you by any change change the io type to int16, but interpret the buffer as a complex float? -josh I figure out that UHD output small endian data. But I use it as big endian,that is the reason why I met such problem. Thank you! Liang ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] shmat issue
On 10/19/2010 10:51 PM, Eric Blossom wrote: On Tue, Oct 19, 2010 at 08:34:40PM -0400, Philip Balister wrote: I'm seeing this issue on my omap3 install with the dialtone flowgraph: # python /usr/share/gnuradio/examples/audio/dial_tone.py gr_vmcircbuf_createfilemapping: createfilemapping is not available gr_vmcircbuf_sysv_shm: shmat (3): Invalid argument l# python /usr/share/gnuradio/examples/audio/dial_tone.py From $ man shmat EINVAL Invalid shmid value, unaligned (i.e., not page-aligned and SHM_RND was not speci- fied) or invalid shmaddr value, or can’t attach segment at shmaddr, or SHM_REMAP was specified and shmaddr was NULL. I hate system calls that have one error code for several errors. In both cases I can hear the dial tone fine. I'm curious why I get the shmat error the first time only. You should see it only once ever, if the program can write to ~/.gnuradio/prefs. Generally this gets written during make check. Does make check work? Insert whining about make check for the cross compiled case :) Why are you running as root? I am lazy :) It looks like gnuradio falls back to another method of creating the shared segment. Yes it does. I'd like to resolve the shmat issue though, Set a breakpoint with gdb, or add printfs. OK, it looks like x86 sets SHMLBA to PAGE_SIZE and arm uses 4 * PAGE_SIZE. Need to puzzle through this a little more. This is the failing check in the kernel. Philip because I am also trying to run the kalibrate program and have the same shmat issue there, but it does not have a fall back method. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] shmat issue
On Wed, Oct 20, 2010 at 01:02:15PM -0400, Philip Balister wrote: On 10/19/2010 10:51 PM, Eric Blossom wrote: In both cases I can hear the dial tone fine. I'm curious why I get the shmat error the first time only. You should see it only once ever, if the program can write to ~/.gnuradio/prefs. Generally this gets written during make check. Does make check work? Insert whining about make check for the cross compiled case :) Why are you running as root? I am lazy :) And foolish :) It looks like gnuradio falls back to another method of creating the shared segment. Yes it does. I'd like to resolve the shmat issue though, Set a breakpoint with gdb, or add printfs. OK, it looks like x86 sets SHMLBA to PAGE_SIZE and arm uses 4 * PAGE_SIZE. Need to puzzle through this a little more. This is the failing check in the kernel. OK. What's PAGE_SIZE on arm? I wonder how we can determine the actual value of SHMLBA at runtime? We currently use the result of gr_pagesize() as the required alignment value. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Moon Bounce Experiment
Hello All, I'm working on a receiver to detect an 8 MHz signal being bounced off the moon. We have constructed a dipole array and the RF receivers are complete. I just purchased a USRP kit for data acquisition. The goal is to stream downconverted I/Q time-series with ~ 1 MHz bandwidth over the USB to a linux box. I've looked through the wiki and I'm going to start installation of gnuradio on Ubuntu 9.04 What examples should I start running first to make sure I've installed correctly? Great group, I'm really excited to start working with gnuradio. Thanks, Joe Craig ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] shmat issue
On 10/20/2010 01:49 PM, Eric Blossom wrote: On Wed, Oct 20, 2010 at 01:02:15PM -0400, Philip Balister wrote: On 10/19/2010 10:51 PM, Eric Blossom wrote: OK, it looks like x86 sets SHMLBA to PAGE_SIZE and arm uses 4 * PAGE_SIZE. Need to puzzle through this a little more. This is the failing check in the kernel. OK. What's PAGE_SIZE on arm? PAGE_SIZE is still 4096, there is an additional restriction on the address passed to shmat(). I wonder how we can determine the actual value of SHMLBA at runtime? We currently use the result of gr_pagesize() as the required alignment value. It looks to me like the there are several shm sections created, with varying access rights. Then shmat is used to reserve a chunk of memory. Then the sections created first are attached to with addresses based on the result of the shmat used to get the address space. The weird thing on arm, the shmat returns a page aligned section, but if you pass that address back to shmat it fails, because that address needs to be aligned to SHMLBA (found in arch/arm|x86/include/asm/shmparam.h. What does it mean? Well gnuradio falls back to a mmap approach to get the circular buffer. It is a bigger problem for kalibrate, which just fails. I'm not sure who is to blame :) Is there another way to get reserve the memory on you process to use when you attach the shared memory segments? Philip ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] C++ and python in OFDM doubt
Hi, I think you can take a look at those files ofdm.py and ofdm_receiver.py (in gnuradio/gnuradio-core/src/python/gnuradio/blks2impl/*.) The C++ blocks are all used inside those files. The ofdm_receiver.py does the synchronization, remove cp, fft, and equalization. FIsheep Laser_s wrote: Hello, I am working on OFDM. I have several questions about OFDM codes, and in general GNU radio. As I understand, there are functions in C + + that are linked through python, right? if I look on the web: http://www.gnuradio.org/doc/doxygen/ I can find the C + + blocks there for OFDM: gr_ofdm_bpsk_demapper, gr_ofdm_cyclic_prefixer, gr_ofdm_frame_acquisition ect On the other hand, if you look at the code: benchmark_ofdm_rx.py, it calls another function that is ofdm_demod belonging to ofdm.py. Then call ofdm_receiver.py later ofdm_sync_ml.py But I never see the function calls in C + + mentioned above. For me this raises several questions: Benchmark_ofdm_rx.py program uses C + + functions OFDM? Is there any way to see a python code in graphical form? as block diagrams or something? My ultimate goal is to take the blocks C + + and use them in simulink for a receiver, is it possible? Thanks -- View this message in context: http://old.nabble.com/C%2B%2B-and-python-in-OFDM-doubt-tp29969780p30012769.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] UDP driver
Hello, I burned in my SD card the UDP FPGA image and the FIRMWARE of basic tx and rx for UDP http://code.ettus.com/redmine/ettus/attachments/74 http://ettus.com/u2bin/txrx_udp_20100507.bin After powering the USRP2, only the two leds of Image and FPGA and on, which is fine. My feeling was that I can be able to ping the USRP to 192.168.10.2 being my host computer 192.168.10.1 I cannot see the USRP. In fact running a sniffer I see nothing from the USRP. (Neither in Windows nor Ubuntu) I made sure that there is no firewall blocking the UDP traffic. What can be wrong? Many thanks, Jorge. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Flex900 TX gain question
We are planning to use the flex900 gnu radio on a project. In reviewing the schematic it appears to me that the gain is too high in the transmit path. The AD8349 puts out about 4 dBm. This is followed by a MGA82563 with a gain of 14, followed by the power amp RF3315 with a gain of 18. If the amplifiers had no compression this would result in an output signal of 36 dBm, 4 Watts. The RF3315 has 25 dBm 1 dB compression point. What am I missing or is the modulator lightly driven? Thanks, /Hugh ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] UDP driver
On 10/20/2010 03:57 PM, Jorge Miguel wrote: Hello, I burned in my SD card the UDP FPGA image and the FIRMWARE of basic tx and rx for UDP http://code.ettus.com/redmine/ettus/attachments/74 http://ettus.com/u2bin/txrx_udp_20100507.bin After powering the USRP2, only the two leds of Image and FPGA and on, which is fine. My feeling was that I can be able to ping the USRP to 192.168.10.2 being my host computer 192.168.10.1 I cannot see the USRP. In fact running a sniffer I see nothing from the USRP. (Neither in Windows nor Ubuntu) I made sure that there is no firewall blocking the UDP traffic. What can be wrong? Many thanks, Jorge. The UDP Beta firmware does *not* have a complete IP stack, and doesn't reply to ICMP ECHO (ping) traffic. If you are heading down the UHD road (which you should be), then you'll need the latest UHD Firmware/FPGA images: http://www.ettus.com/downloads/uhd_images/ -- 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] Can't install AIS package on Beagleboard
As far as I understand gnuradio shouldn't work without gnuradio-core package. Yet it works on Beagle. So I guess the only difference is package name. Probably need to change some lines in configure file. I'll copy here list of all gnuradio packages available for Beagle Ubuntu as soon as I can. Probably then someone could help me with this. Thunder87 wrote: I have problems with gr-ais installation on my Beagleboard running Ubuntu Lucid. ./configure wants gnuradio-core package Searched with aptitude, and it seems threre is no such package for ARM EABI Ubuntu distribution. Gnuradio was installed without problems and seem to work as usual. What to do? Has anyone tried to setup gr-ais on beagleboard running lucid? -- View this message in context: http://old.nabble.com/Can%27t-install-AIS-package-on-Beagleboard-tp29985304p30014419.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Moon Bounce Experiment
I have managed to install gnuradio and run usrp_fft.py with success! Now for the questions... 1) I'm always seeing... Exception RuntimeError: 'maximum recursion depth exceeded while calling a Python object' in type 'exception.AttributeError' ignored . What does this mean, and how to fix it? 2) How do I save the I/Q stream to disk? I'm interested in the maximum bit resolution for the best dynamic range. I just want the raw time samples. 3) Some of the examples (like usrp_wfm_rcv.py) spit out ...aUaUaUaUaU... to the console and the sound is choppy. What does this mean, and is there a way to turn it off? 4) Is it possible to tweak parameters such as quadrature downconverter bandwidth/decimation, etc? thanks, Joe Craig On Oct 20, 2010, at 12:28 PM, Joseph Craig wrote: Hello All, I'm working on a receiver to detect an 8 MHz signal being bounced off the moon. We have constructed a dipole array and the RF receivers are complete. I just purchased a USRP kit for data acquisition. The goal is to stream downconverted I/Q time-series with ~ 1 MHz bandwidth over the USB to a linux box. I've looked through the wiki and I'm going to start installation of gnuradio on Ubuntu 9.04 What examples should I start running first to make sure I've installed correctly? Great group, I'm really excited to start working with gnuradio. Thanks, Joe Craig ___ 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] multi usrp, 1 odd channel, HW problem?
On Thu, Oct 14, 2010 at 12:47 PM, Matt Ettus m...@ettus.com wrote: Probe R201 on all 4 WBX boards with an oscilloscope while running. One side of the resistor is ground and the other side is the reference clock. They should all be around the same amplitude, and have the exact same frequency and phase. Matt On 10/14/2010 09:13 AM, Steven Clark wrote: Hi all- I have a multi-usrp setup with 2 USRP 1s and 4 WBX daughtercards. I have performed the clock synching described here: http://gnuradio.org/redmine/wiki/1/MultiUsrp I'm doing 4-channel receive, using a power splitter to send the same CW signal into all 4 d'cards, and tuning them all identically. 3 of the 4 channels are nicely phase-locked. The 4th seems a little...off. ClockMasterUSRP (Serial #5821): Side A: red channel ClockMasterUSRP (Serial #5821): Side B: green channel ClockSlaveUSRP (Serial #2087): Side A: blue channel ClockSlaveUSRP (Serial #2087): Side B: black channel --- problem with this guy Please see these 3 images to see the problem: http://picasaweb.google.com/steven.p.clark/MultiUsrpGlitches?feat=directlink You can see the problem in both the frequency domain, and in the time domain. I tried swapping daughtercards around, and the problem is not tied to any one daughtercard, but rather to slave USRP side B. Any idea what could be causing this? Shouldn't the same clock be going to both sides of the USRP? (why does blue look fine, but black does not?) -Steven Matt- Sorry for the delay in getting back to you. I took a look at R201 on all dboards as you suggested. All 4 looked fairly similar -- a clean-looking 64MHz sine wave. Amplitudes were close, in the 700-800mV p-p range. Comparing between 2 dboards on the same USRP, the phases matched pretty well (within a few degrees I would say). Comparing from one USRP to the other, there was a definite phase offset (~90degrees). Since the SMA cable bringing the clock from master to slave is a few feet long, this seems reasonable. What's the next step? -Steven ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Error when installing Boost
I get an error with I use ./configure when I am installing boost. The following commands are entered in the terminal when I am installing. cd boost_1_44_0 BOOST_PREFIX=/opt/boost_1_44_0 ./tools/jam/src/boehm_gc/configure --prefix=$BOOST_PREFIX --with-libraries=thread,date_time,program_options confchecking if f77 PIC flag -fPIC works... yes checking if f77 static flag -static works... yes checking if f77 supports -c -o file.o... yes checking whether the f77 linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... /usr/bin/f77: Illegal option: -print-search-dirs GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking sys/dg_sys_info.h usability... no checking sys/dg_sys_info.h presence... no checking for sys/dg_sys_info.h... no checking whether Solaris gcc optimization fix is necessary... no checking atomic_ops.h usability... no checking atomic_ops.h presence... no checking for atomic_ops.h... no configure: error: Missig libatomic_ops. Can someone help? Thanks Ismael -- View this message in context: http://old.nabble.com/Error-when-installing-Boost-tp30015069p30015069.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Moon Bounce Experiment
On 10/20/2010 07:13 PM, Joseph Craig wrote: I have managed to install gnuradio and run usrp_fft.py with success! Now for the questions... 1) I'm always seeing... Exception RuntimeError: 'maximum recursion depth exceeded while calling a Python object' in type 'exception.AttributeError' ignored . What does this mean, and how to fix it? In what application are you seeing this error? 2) How do I save the I/Q stream to disk? I'm interested in the maximum bit resolution for the best dynamic range. I just want the raw time samples. You should investigate gnuradio-companion (GRC), which allows you to put a signal processing graph together graphically--like LEGO building blocks. You can very easily put together a baseband recorder application in about 5 minutes this way. 3) Some of the examples (like usrp_wfm_rcv.py) spit out ...aUaUaUaUaU... to the console and the sound is choppy. What does this mean, and is there a way to turn it off? It means that you're experiencing a audio underrun, likely because your processing chain can't keep up. Perhaps because you haven't specified a high enough decimation, and the chain is trying to keep up with a unpleasantly-large torrent of data. 4) Is it possible to tweak parameters such as quadrature downconverter bandwidth/decimation, etc? thanks, Joe Craig Yes, absolutely. Most of the example programs take a -d option that controls decimation in the USRP hardware. For example, if you only wanted 1MHz bandwidth, you'd use a -d option to the examples (like usrp_fft.py) of -d 64, which will give you 1Msps of complex samples between the USRP and the host--because the A/D in the USRP is 64Msps. For the USRP2, the A/D operates at 100Msps, so you'd need to adjust your decimation appropriately. You should keep in mind that except for trivial algorithms at modest bandwidths, you'll need a fairly-decent computer to get the best results from your Gnu Radio experiments. Although I think you mentioned that at first you only want to record baseband data to disk at 1Msps, I'm guessing you'll want to go beyond that at some point. I'd explore gnuradio-companion as well. Good luck! -- 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] Moon Bounce Experiment
Hi Marcus, Thanks for the quick reply... On Oct 20, 2010, at 5:51 PM, Marcus D. Leech wrote: On 10/20/2010 07:13 PM, Joseph Craig wrote: I have managed to install gnuradio and run usrp_fft.py with success! Now for the questions... 1) I'm always seeing... Exception RuntimeError: 'maximum recursion depth exceeded while calling a Python object' in type 'exception.AttributeError' ignored . What does this mean, and how to fix it? In what application are you seeing this error? python 2) How do I save the I/Q stream to disk? I'm interested in the maximum bit resolution for the best dynamic range. I just want the raw time samples. You should investigate gnuradio-companion (GRC), which allows you to put a signal processing graph together graphically--like LEGO building blocks. You can very easily put together a baseband recorder application in about 5 minutes this way. 5 minutes is pretty enticing seeing how this has to be working friday. How long does it take to setup GRC? Is there a guide? 3) Some of the examples (like usrp_wfm_rcv.py) spit out ...aUaUaUaUaU... to the console and the sound is choppy. What does this mean, and is there a way to turn it off? It means that you're experiencing a audio underrun, likely because your processing chain can't keep up. Perhaps because you haven't specified a high enough decimation, and the chain is trying to keep up with a unpleasantly-large torrent of data. ah, yes. should have thought of this. I will check out increasing the decimation. 4) Is it possible to tweak parameters such as quadrature downconverter bandwidth/decimation, etc? thanks, Joe Craig Yes, absolutely. Most of the example programs take a -d option that controls decimation in the USRP hardware. For example, if you only wanted 1MHz bandwidth, you'd use a -d option to the examples (like usrp_fft.py) of -d 64, which will give you 1Msps of complex samples between the USRP and the host--because the A/D in the USRP is 64Msps. For the USRP2, the A/D operates at 100Msps, so you'd need to adjust your decimation appropriately. Got it! You should keep in mind that except for trivial algorithms at modest bandwidths, you'll need a fairly-decent computer to get the best results from your Gnu Radio experiments. Although I think you mentioned that at first you only want to record baseband data to disk at 1Msps, I'm guessing you'll want to go beyond that at some point. it's a year old linux box we were using for fairly high bandwidth recording from ethernet, so it should be ok. Joe I'd explore gnuradio-companion as well. Good luck! -- 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 ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Moon Bounce Experiment
On Wed, 2010-10-20 at 18:49 -0600, Joseph Craig wrote: Hi Marcus, Thanks for the quick reply... On Oct 20, 2010, at 5:51 PM, Marcus D. Leech wrote: On 10/20/2010 07:13 PM, Joseph Craig wrote: I have managed to install gnuradio and run usrp_fft.py with success! Now for the questions... 1) I'm always seeing... Exception RuntimeError: 'maximum recursion depth exceeded while calling a Python object' in type 'exception.AttributeError' ignored . What does this mean, and how to fix it? In what application are you seeing this error? python I think Marcus is asking which Python application you are seeing the exception in. Is it in usrp_fft.py? 2) How do I save the I/Q stream to disk? I'm interested in the maximum bit resolution for the best dynamic range. I just want the raw time samples. You should investigate gnuradio-companion (GRC), which allows you to put a signal processing graph together graphically--like LEGO building blocks. You can very easily put together a baseband recorder application in about 5 minutes this way. 5 minutes is pretty enticing seeing how this has to be working friday. How long does it take to setup GRC? Is there a guide? You can also use usrp_rx_cfile.py to save the raw complex stream to disk. The help info for that file is pretty self-explanatory. However, GRC is very very useful for putting together flowgraphs quickly. Follow the Gnuradio build guide to get GRC built. 3) Some of the examples (like usrp_wfm_rcv.py) spit out ...aUaUaUaUaU... to the console and the sound is choppy. What does this mean, and is there a way to turn it off? It means that you're experiencing a audio underrun, likely because your processing chain can't keep up. Perhaps because you haven't specified a high enough decimation, and the chain is trying to keep up with a unpleasantly-large torrent of data. ah, yes. should have thought of this. I will check out increasing the decimation. You might also have the infamous two-clocks problem, which I won't explain in detail here. But basically the soundcard clock might not be exactly what it says it is, and if it's off enough from what the flowgraph assumes it is, you will drop samples or underrun depending on which way the error lies. We really need a better sound driver in GR and if I ever see free time again I'll be working on it. Nick 4) Is it possible to tweak parameters such as quadrature downconverter bandwidth/decimation, etc? Yes, absolutely. Most of the example programs take a -d option that controls decimation in the USRP hardware. For example, if you only wanted 1MHz bandwidth, you'd use a -d option to the examples (like usrp_fft.py) of -d 64, which will give you 1Msps of complex samples between the USRP and the host--because the A/D in the USRP is 64Msps. For the USRP2, the A/D operates at 100Msps, so you'd need to adjust your decimation appropriately. Got it! You should keep in mind that except for trivial algorithms at modest bandwidths, you'll need a fairly-decent computer to get the best results from your Gnu Radio experiments. Although I think you mentioned that at first you only want to record baseband data to disk at 1Msps, I'm guessing you'll want to go beyond that at some point. it's a year old linux box we were using for fairly high bandwidth recording from ethernet, so it should be ok. Joe I'd explore gnuradio-companion as well. Good luck! -- 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 ___ 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] Moon Bounce Experiment
On 10/20/2010 08:49 PM, Joseph Craig wrote: Hi Marcus, Thanks for the quick reply... On Oct 20, 2010, at 5:51 PM, Marcus D. Leech wrote: On 10/20/2010 07:13 PM, Joseph Craig wrote: I have managed to install gnuradio and run usrp_fft.py with success! Now for the questions... 1) I'm always seeing... Exception RuntimeError: 'maximum recursion depth exceeded while calling a Python object' in type 'exception.AttributeError' ignored . What does this mean, and how to fix it? In what application are you seeing this error? python I should perhaps have clarified. Which application, written, obviously, in Python, was producing this error for you? 2) How do I save the I/Q stream to disk? I'm interested in the maximum bit resolution for the best dynamic range. I just want the raw time samples. You should investigate gnuradio-companion (GRC), which allows you to put a signal processing graph together graphically--like LEGO building blocks. You can very easily put together a baseband recorder application in about 5 minutes this way. 5 minutes is pretty enticing seeing how this has to be working friday. How long does it take to setup GRC? Is there a guide? If built/installed Gnu Radio, you already have GRC/GnuRadioCompanion: gnuradio-companion At the prompt in a terminal window should bring up a GRC instance. All you should need is a usrp-source block, and a file-sink block. The usrp-source block takes parameters like decimation, center-frequency, gain. -- 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] Moon Bounce Experiment
On 10/20/2010 08:57 PM, Nick Foster wrote: You can also use usrp_rx_cfile.py to save the raw complex stream to disk. The help info for that file is pretty self-explanatory. However, GRC is very very useful for putting together flowgraphs quickly. Follow the Gnuradio build guide to get GRC built. Forgot about usrp_rx_cfile.py doh! -- 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] Moon Bounce Experiment
On Wed, Oct 20, 2010 at 06:49:21PM -0600, Joseph Craig wrote: Hi Marcus, Thanks for the quick reply... On Oct 20, 2010, at 5:51 PM, Marcus D. Leech wrote: On 10/20/2010 07:13 PM, Joseph Craig wrote: I have managed to install gnuradio and run usrp_fft.py with success! Now for the questions... 1) I'm always seeing... Exception RuntimeError: 'maximum recursion depth exceeded while calling a Python object' in type 'exception.AttributeError' ignored . What does this mean, and how to fix it? In what application are you seeing this error? python Which version of GNU Radio are you using? tarball? If so, which one? git? If so, which branch? Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Error when installing Boost
On Wed, Oct 20, 2010 at 04:47:47PM -0700, ish13 wrote: I get an error with I use ./configure when I am installing boost. The following commands are entered in the terminal when I am installing. Why are you building boost? It's packaged for pretty much every reasonably modern distribution. cd boost_1_44_0 BOOST_PREFIX=/opt/boost_1_44_0 ./tools/jam/src/boehm_gc/configure --prefix=$BOOST_PREFIX --with-libraries=thread,date_time,program_options confchecking if f77 PIC flag -fPIC works... yes checking if f77 static flag -static works... yes checking if f77 supports -c -o file.o... yes checking whether the f77 linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... /usr/bin/f77: Illegal option: -print-search-dirs GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking sys/dg_sys_info.h usability... no checking sys/dg_sys_info.h presence... no checking for sys/dg_sys_info.h... no checking whether Solaris gcc optimization fix is necessary... no checking atomic_ops.h usability... no checking atomic_ops.h presence... no checking for atomic_ops.h... no configure: error: Missig libatomic_ops. Can someone help? Thanks Ismael ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] More on latency
I had a flow-graph that earlier today had a latency of roughly 1 second or so. When I tested it this evening, after it had been running for several hours, the latency was back up to *several tens of seconds*!!!. Which means that external events at the source take several tens of seconds to show up at the sinks -- two graphical, and one filesink. WTF? !! The CPU load at the time was modest -- about 38% -- 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] Moon Bounce Experiment
On Oct 20, 2010, at 7:07 PM, Eric Blossom wrote: On Wed, Oct 20, 2010 at 06:49:21PM -0600, Joseph Craig wrote: Hi Marcus, Thanks for the quick reply... On Oct 20, 2010, at 5:51 PM, Marcus D. Leech wrote: On 10/20/2010 07:13 PM, Joseph Craig wrote: I have managed to install gnuradio and run usrp_fft.py with success! Now for the questions... 1) I'm always seeing... Exception RuntimeError: 'maximum recursion depth exceeded while calling a Python object' in type 'exception.AttributeError' ignored . What does this mean, and how to fix it? In what application are you seeing this error? python Which version of GNU Radio are you using? tarball? If so, which one? git? If so, which branch? I've install gnuradio from Synaptic Package Manager. Looks like 3.0.4 I see this error when every gnuradio python application is run. thanks, Joe Craig Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Moon Bounce Experiment
On Oct 20, 2010, at 6:58 PM, Marcus D. Leech wrote: On 10/20/2010 08:49 PM, Joseph Craig wrote: Hi Marcus, Thanks for the quick reply... On Oct 20, 2010, at 5:51 PM, Marcus D. Leech wrote: On 10/20/2010 07:13 PM, Joseph Craig wrote: I have managed to install gnuradio and run usrp_fft.py with success! Now for the questions... 1) I'm always seeing... Exception RuntimeError: 'maximum recursion depth exceeded while calling a Python object' in type 'exception.AttributeError' ignored . What does this mean, and how to fix it? In what application are you seeing this error? python I should perhaps have clarified. Which application, written, obviously, in Python, was producing this error for you? 2) How do I save the I/Q stream to disk? I'm interested in the maximum bit resolution for the best dynamic range. I just want the raw time samples. You should investigate gnuradio-companion (GRC), which allows you to put a signal processing graph together graphically--like LEGO building blocks. You can very easily put together a baseband recorder application in about 5 minutes this way. 5 minutes is pretty enticing seeing how this has to be working friday. How long does it take to setup GRC? Is there a guide? If built/installed Gnu Radio, you already have GRC/GnuRadioCompanion: gnuradio-companion At the prompt in a terminal window should bring up a GRC instance. nope, command not found. I thought it was because I installed gnuradio with synaptic, so I installed gnuradio-companion via apt-get, still nothing. where should the program files appear? All you should need is a usrp-source block, and a file-sink block. sounds like simulink. should be easy. Joe The usrp-source block takes parameters like decimation, center-frequency, gain. -- 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] Moon Bounce Experiment
On 10/21/2010 01:02 AM, Joseph Craig wrote: On Oct 20, 2010, at 7:07 PM, Eric Blossom wrote: On Wed, Oct 20, 2010 at 06:49:21PM -0600, Joseph Craig wrote: Hi Marcus, Thanks for the quick reply... On Oct 20, 2010, at 5:51 PM, Marcus D. Leech wrote: On 10/20/2010 07:13 PM, Joseph Craig wrote: I have managed to install gnuradio and run usrp_fft.py with success! Now for the questions... 1) I'm always seeing... Exception RuntimeError: 'maximum recursion depth exceeded while calling a Python object' in type 'exception.AttributeError' ignored . What does this mean, and how to fix it? In what application are you seeing this error? python Which version of GNU Radio are you using? tarball? If so, which one? git? If so, which branch? I've install gnuradio from Synaptic Package Manager. Looks like 3.0.4 I see this error when every gnuradio python application is run. thanks, Joe Craig Eric My recollection is that there was a compatibility issue between older Gnu Radio code, and the Python2.6 that's in Ubuntu 9.X and more recent. Really, you'll have much better joy if you install from GIT source, following the directions found here: http://gnuradio.org/redmine/wiki/gnuradio/BuildGuide You'll have to uninstall the version that Synaptic installed. Gnu radio is still very much a rapidly-evolving beast, which means that installing from GIT source is really a good way to go. The packagers for various Linux distributions can't possibly keep up with the codebase. -- 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] Error when installing Boost
I am new at this. But I was just following the instructions that are on the wiki page. It said that boost needed to be installed. So I was following the steps and I ran into the error message. Which approach am I supposed to take to complete the installation of gnu radio. Ismael Eric Blossom wrote: On Wed, Oct 20, 2010 at 04:47:47PM -0700, ish13 wrote: I get an error with I use ./configure when I am installing boost. The following commands are entered in the terminal when I am installing. Why are you building boost? It's packaged for pretty much every reasonably modern distribution. cd boost_1_44_0 BOOST_PREFIX=/opt/boost_1_44_0 ./tools/jam/src/boehm_gc/configure --prefix=$BOOST_PREFIX --with-libraries=thread,date_time,program_options confchecking if f77 PIC flag -fPIC works... yes checking if f77 static flag -static works... yes checking if f77 supports -c -o file.o... yes checking whether the f77 linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... /usr/bin/f77: Illegal option: -print-search-dirs GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking sys/dg_sys_info.h usability... no checking sys/dg_sys_info.h presence... no checking for sys/dg_sys_info.h... no checking whether Solaris gcc optimization fix is necessary... no checking atomic_ops.h usability... no checking atomic_ops.h presence... no checking for atomic_ops.h... no configure: error: Missig libatomic_ops. Can someone help? Thanks Ismael ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio -- View this message in context: http://old.nabble.com/Error-when-installing-Boost-tp30015069p30016337.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
