[Discuss-gnuradio] implementing state flow
To implement MAC layer elements, i.e. waiting for data to arrive, is the best strategy to program these elements in python? Are there any example apps that implement packet modem like functionality? ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] new wide-coverage receiver
this new wide-coverage receiver might interest some on the list. interesting specs. the manufacturer is hobbyist-friendly, so it might be actually priced somewhere in the range of reality... -bernieS http://radio.tentec.com/Commercial/RX400 RX-400 PRELIMINARY SPECIFICATIONS FREQUENCY COVERAGE: 2 - 3000 MHz. Cellular blocked within USA - unblocked version available to authorized users only. MODE: USB, LSB, ISB, CW, AM, NFM, WFM TUNING RESOLUTION: 1 Hz steps. (10 kHz steps at WB-IF output) OPERATING TEMPERATURE RANGE : 0 - 50 degrees C @ full specification. -10 to 60 degrees C with degraded performance. FREQUENCY STABILITY: standard TCXO: below 30 MHz +/-20Hz,above30 MHz +/- 3 ppm Optional TCXO: above 30 MHz +/- 0.6 ppm ACCURACY: All internal oscillators are locked to either internal or external frequency standard. EXTERNAL FREQUENCY REFERENCE: 1, 2, 5 or 10 MHz. Receiver automatically switches to this reference upon application, at power up or after any serial link activity. SPURIOUS RESPONSES: (design target) all spurious to be less than -105 dBm equivalent input max. with approx. 6 less than 80 dBm IMAGE REJECTION: 80 dB typical 2 - 3000 MHz. IF REJECTION: 80 dB typical 2-3000 MHz BFO: Tunable in CW mode only, +/- 8 kHz. Tuning in 10 Hz steps. Fixed frequency in SSB, disabled in AM and FM. MEMORIES: 1000 SCAN RATE: 100 channels/sec or faster SYNTHESIZER LOCK TIME: approx. 1 ms SQUELCH: c/n ratio 0-99 dB SELECTIVITY: selection is mode independent. Approx. 50 filter bandwidths with 8-10 chosen appropriately for each of the 5 modes. Shape factor 1.5:1 or better. (6 to 60 dB). Examples, useful for: CW 100, 150, 200, 250, 300, 400, 500, 600, 700, 800, 1000 Hz. SSB 1.5, 1.6, 1.7, 1.8, 1.9, 2.0, 2.2, 2.4, 2.6, 3.0, 3.4 kHz . AM 4.0, 5.0, 6.0, 7.0, 8.0, 9.6, 10.4, 12.0, 13.6, 15.2, 16 kHz.. WFM100, 120, 140, 150, 160, 180, 200, 250, 300 kHz. INBAND RIPPLE: 2-3 dB, referenced to IF output SENSITIVITY: Mode BW dBm (for 12 dB NF) SSB 10 db S/N 3 kHz -11 AM (50% mod) 6.0 kHz -10 FM-N @ 6 kHz dev 16 dB SINAD 15 kHz -107 FM-W @ 10-20 kHz dev 3050 kHz -102 FM-W @ 75kHz dev 200 kHz -9 DYNAMIC RANGE: 3rd Order Intercept (dBm) typical 0, minimum -5. Noise figure (dB) typical 10, minimum 12. 2nd ORDER INTERCEPT: 50 dBm minimum AGC: Fast, Medium, Slow, Programmable. Manual gain setting is provided in all four modes, adjustable over 120 dB range. DUMP feature provided in all modes. Mode Attack(dB/ms) Hang(sec) Decay(dB/sec) Fast 0.8 0 1200 Medium 0.8 0 100 Slow 0.8 0 25 Prog. 0.01-1.0 0.01-99.9 0.01-99.9 WIDEBAND IF OUTPUT, ANALOG: 21.4 MHz center frequency, fixed gain, 6 MHz bandwidth capable, 10 kHz tuning steps. 2 MHz bandwidth if receiver tuned below 20 MHz. S-METER: reports signal level in dBm to host upon request OPTIONS: (only one may be installed) NARROWBAND IF OUTPUT: 21.4 MHz center frequency, bandwidth determined by filter selection, delayed AGC. DIGITAL DATA OUTPUT: 16 bit, I&Q, serial. Baseband representation of NB-IF output. CONTROL INTERFACE: built-in MULTI-DROP RS-232 (DB9 connector) and TCP/IP Optional: POTS allows customer to remote unit anywhere with access to nothing but a phone line. No PC required. FIRMWARE: can be updated remotely in Flash ROM ANTENNA INPUT: 50 ohm, unbalanced, SMA connector. 2.5:1 VSWR max @ receiver's tuned frequency. RF INPUT PROTECTION: accepts +20 dBm w/o damage AUDIO LINE OUTPUT: 0 dBm (+/- 3 dBm) 600 ohm outputs. Terminals may be grounded or shorted together without damage. One AC coupled, one DC coupled HEADPHONE OUTPUT: both 1/4" and 1/8 stereo phone jacks. 10 mw maximum into 600 ohms. Front panel volume control. POWER REQUIREMENTS: 90-264 VAC, 48-440 Hz @ approx. 40 watts. Removable six foot line cord included. Optional: substitute 11-28 VDC supply at additional cost. DIMENSIONS: 7.5W x 15.5D x 3.5H. Rack mountable with optional bracket kits for either half rack or full rack widths. MTTR: less than 30 minutes for replacement of any of 8 major subassemblies. ADDITIONAL FEATURES: MUTE,for use in transmit/receive applications, mutes audio and IF outputs. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] CVS compilation problem (actually a test fails)
On Tuesday 03 May 2005 04:13, Eric Blossom wrote: > On Mon, May 02, 2005 at 09:27:19AM -0700, Matt Ettus wrote: > > [EMAIL PROTECTED] wrote: > > > Hi, > > > > > > I can't check the archives at the moment as lists.gnu.org doesn't want > > > to talk to anyone, but I don't remember anyone saying anything about > > > this. > > > > > > A couple of weeks ago I compiled and ran all the gnuradio code. I then > > > had a disk failure and had to rebuild the whole of my system. I > > > downloaded all of the source code again (from CVS) and rebuilt it, but > > > now I get the following error: > > > > I'm not sure why this test is being run in the core directory. But > > anyway, it looks like you need to get the gr-gsm-fr-vocoder module. > > > > Matt > > I've backed out digital_voice.py until I find a better solution. > > Eric FYI: The examples for voice codec work fine here. Suspect that gr-gsm-fr-vocoder wasn't installed. cheerio Berndt -- Every man who says frankly and fully what he thinks is doing a public service. [Leslie Stephen] ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] What is this?
On Monday 02 May 2005 11:31, Bob McGwier wrote: > Just installed SUSE 9.3 on a clean drive and am getting this problem. > gnuradio-core goes first in the for-all-dirs list with ../buildit and > this error is the first in the list of tests. I then tried making and > installing > the gr-gsm vocoder stuff first and this still results. I have fiddled with > PYTHONPATH, PYTHONHOME, PYTHON . . . . .Ideas? > > Bob > > > = > ERROR: test_blks_import (__main__.test_head) > -- > Traceback (most recent call last): > File "./qa_kludged_imports.py", line 35, in test_blks_import > from gnuradio import blks > File > "/usr/local/src/gr-build/gnuradio-core/src/python/gnuradio/blks/__init__.py >", line 37, in ? > exec "from gnuradio.blksimpl.%s import *" % (f,) > File "", line 1, in ? > File > "/usr/local/src/gr-build/gnuradio-core/src/python/gnuradio/blksimpl/digital >_voice.py", line 33, in ? > from gnuradio.vocoder import gsm_full_rate > ImportError: No module named vocoder Did you get and install the gr-gsm-fr-vocoder module? cheerio Berndt -- Every man who says frankly and fully what he thinks is doing a public service. [Leslie Stephen] ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Alternate list archive locations (was:Re: [Discuss-gnuradio] CVS compilation problem (actually a test fails))
On Monday 02 May 2005 12:16, [EMAIL PROTECTED] wrote: > I can't check the archives at the moment as lists.gnu.org doesn't want > to talk to anyone, but I don't remember anyone saying anything about > this. A note on archives: Another archive is available on gmane.org under comp.gnu.radio.general. Last night, while attempting to read some archives (lists.gnu.org being basically unavailable) I found the gmane archive. This archive even allows you to download mboxes of the archive, so I got their entire set, going back to March 2002. Would someone who was here in the beginning see how long before the gmane archive picks up this list existed? That is, how much of the archive is gmane missing? -- Lamar Owen Director of Information Technology Pisgah Astronomical Research Institute 1 PARI Drive Rosman, NC 28772 (828)862-5554 www.pari.edu ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] 2.5 GS/sec 14-bit A/D converter
On Monday 02 May 2005 00:16, Tim Ansell wrote: > The question is how would you get this into a computer? If we round it > up to 16 bits, it makes 4.6 Gigabytes per second. Would a FPGA even be > able to keep up? Could people a lot smarter then me, discuss how this > chip could even possibly be used? You would have to widen the data path to reduce clock rates. Something like an SRC MAP processor can handle 4.8GBps rates on GPIO, but the GPIO is 216 bits wide. So, you'd build a shift register of sorts, clocking in x 16 bit samples across the width of the register and then dumping all the bits in one swoop. Say you did 160 bits; you'd then be able to clock in at 460MWps (where a word is 160 bits). That would be a ten-stage register pipeline with serial words in, parallel words out. The SRC MAP processor is very expensive, by the way, and interfaces with the host CPU using their SNAP system, where the dat comes in on a DDR-SDRAM interface, the only thing in a PC that can hope to keep up with those rates. Of course, the MAP processor itself is a trio of high-speed Xilinx FPGAs, and SRC provides tools to program the FPGA's from C or Fortran; they call it reconfigurable computing (it was featured a few months back in LJ). So the FPGA's on the MAP do you decimation and DDC prior to hitting the CPU. We have a grant application for an SRC MAPstation with 16 200Msps 8 bit ADC's; cost is going to be around $160K. We're getting our feet wet in FPGA stuff with the USRP in the mean time. -- Lamar Owen Director of Information Technology Pisgah Astronomical Research Institute 1 PARI Drive Rosman, NC 28772 (828)862-5554 www.pari.edu ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
RE: [Discuss-gnuradio] Using USRP from multiple applicationssimultaneously
The fsk modulator/demodulator from the examples may be something you could use http://www.mail-archive.com/discuss-gnuradio@gnu.org/msg00281.html Run these commands in different windows: $ ./fsk_rx.py -f /dev/null -c 10M -r 100k -N $ ./fsk_tx.py -f /boot/vmlinuz -R -c 10M -r 100k -N > -Original Message- > From: [EMAIL PROTECTED] [mailto:discuss- > [EMAIL PROTECTED] On Behalf Of Angilberto Muniz > Sb > Sent: Sunday, May 01, 2005 5:00 PM > To: Eric Blossom; Harald Welte > Cc: discuss-gnuradio@gnu.org > Subject: Re: [Discuss-gnuradio] Using USRP from multiple > applicationssimultaneously > > Matt, > Would you provide a very simple analog-loop-back > sample application? I mean, I'd like to hookup a cable > between Analog-out to Analog-in, generate some signal > e display its waveform on the oscope... > > I cant seem to make it work -- may be my analog > d'board are not working -- unfortunately I dont have a > real scope on handy to check it... > > Angilberto. > > > > ... > > The Tx and Rx sides are completely independent and > > we often run > > different apps for Tx and Rx simultaneously. The Tx > > and Rx paths have > > different USB endpoints for their streaming data. > > ... > > __ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > > ___ > 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] What is this?
The fix to cvs and the removal of the broken file cleaned up everything here. FYI, with SUSE 9.3, the only thing I had to install from source with two subversions later SWIG. I was able to find an archive that actually worked (The Mail Archive) and got the URL to the usrp_fpga.rbf which is STILL not being distributed with cvs and everything works. On the usrp_fft.py, what is the scale on the Y axis? dB, linear? Bob Eric Blossom wrote: On Sun, May 01, 2005 at 10:01:40PM -0400, Bob McGwier wrote: Just installed SUSE 9.3 on a clean drive and am getting this problem. gnuradio-core goes first in the for-all-dirs list with ../buildit and this error is the first in the list of tests. I then tried making and installing the gr-gsm vocoder stuff first and this still results. I have fiddled with PYTHONPATH, PYTHONHOME, PYTHON . . . . .Ideas? Bob I assume we've got a bit of a mailing list timewarp going on here. In any event, I've fixed a couple of problems in CVS and have just confirmed that it all builds from scratch for me. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
RE: [Discuss-gnuradio] using a 48k sound card with wfm_rcv_gui
With USB north, the RX board is on the West (left) side. i.e. RXA are the block letters below the board. > -Original Message- > From: 'Eric Blossom' [mailto:[EMAIL PROTECTED] > Sent: Monday, May 02, 2005 12:36 PM > To: Richard Cagley > Cc: discuss-gnuradio@gnu.org > Subject: Re: [Discuss-gnuradio] using a 48k sound card with wfm_rcv_gui > > On Mon, May 02, 2005 at 01:26:00PM -0700, Richard Cagley wrote: > > Tried that and didn't work. > > I also tried with the basic RX card. I just put a wire in the middle of > the > > RX-A SMA connector but nothing came out there either. > > Very odd. > > Looking at the USRP oriented such that the USB connector is to the > north, are you connecting to the daughterboard on the left or the > right? left is "Side A", right is "Side B". > > Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] using a 48k sound card with wfm_rcv_gui
On Mon, May 02, 2005 at 01:26:00PM -0700, Richard Cagley wrote: > Tried that and didn't work. > I also tried with the basic RX card. I just put a wire in the middle of the > RX-A SMA connector but nothing came out there either. > Very odd. Looking at the USRP oriented such that the USB connector is to the north, are you connecting to the daughterboard on the left or the right? left is "Side A", right is "Side B". Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
RE: [Discuss-gnuradio] using a 48k sound card with wfm_rcv_gui
Tried that and didn't work. I also tried with the basic RX card. I just put a wire in the middle of the RX-A SMA connector but nothing came out there either. Very odd. > -Original Message- > From: 'Eric Blossom' [mailto:[EMAIL PROTECTED] > Sent: Monday, May 02, 2005 10:53 AM > To: Richard Cagley > Cc: discuss-gnuradio@gnu.org > Subject: Re: [Discuss-gnuradio] using a 48k sound card with wfm_rcv_gui > > On Mon, May 02, 2005 at 11:12:07AM -0700, Richard Cagley wrote: > > That worked. Thanks. > > But, I still only get static (I even have an actual antenna hooked up to > the > > TV card). Is it because of the warning I'm getting? > > > > [EMAIL PROTECTED] usrp]$ wfm_rcv_gui.py 93.7 > > RX d'board A: TV Rx > > RX d'board B: > > usrp_standard_rx::set_decim_rate: WARNING rates > 128 result in > incorrect > > gain. > > >>> gr_fir_fff: using SSE > > Since you are using the TVRX daughter board, you should be using the > tvrx_wfm_rcv_gui.py program. wfm_rcv_gui is for people with no RF > front end. > > Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] CVS compilation problem (actually a test fails)
On Mon, May 02, 2005 at 10:51:07AM -0700, [EMAIL PROTECTED] wrote: > I've posted an installation guide for GNU radio that might be helpful: > > http://www.kd7lmo.net/ground_gnuradio_install.html > > Maybe someone can post a link from the Wiki to my site. Done. Thanks, Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] 2.5 GS/sec 14-bit A/D converter
Tim - On Mon, May 02, 2005 at 01:46:48PM +0930, Tim Ansell wrote: > So where do we request free samples from :P Good question. I'd be happy with a data sheet, for the moment. I'm in the low-latency business, so this chip _may_ be useless to me. > The question is how would you get this into a computer? If we round it > up to 16 bits, it makes 4.6 Gigabytes per second. Would a FPGA even be > able to keep up? Could people a lot smarter then me, discuss how this > chip could even possibly be used? Look at the table again (as corrected by Krzysztof? I can't verify because lists.gnu.org is currently refusing port 80 connections): >ParameterGaAsSiGe > >Maximum clock frequency > 5 GHz> 15 GHz >SINAD (signal to noise+distortion) > 70 dB > 110 dB >Eff. resolution bits at 2.5 GHz carrier: >10 MHz BW 14 bits 18 bits >100 MHz BW 11 bits 14 bits So what you need coming out is N bits at something over twice the bandwidth. For the SiGe chip, that's 14 bits at > 200 MS/s. Even with generous provision for filter guard bands and compatibility with maximum accuracy, you have 20 bits at 300 MS/s, well within reach of a modern FPGA. The patent looks -- well, too obvious to be patentable [*]. They seem to be trying to patent a mixer followed by a sigma-delta converter, in particular the case where the same frequency is used for the mixer LO and the sigma-delta modulator clock. - Larry [*] but then, what do I know. I'm an engineer, so I must not count as someone "skilled in the art". signature.asc Description: Digital signature ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] What is this?
On Sun, May 01, 2005 at 10:01:40PM -0400, Bob McGwier wrote: > Just installed SUSE 9.3 on a clean drive and am getting this problem. > gnuradio-core goes first in the for-all-dirs list with ../buildit and > this error is the first in the list of tests. I then tried making and > installing > the gr-gsm vocoder stuff first and this still results. I have fiddled with > PYTHONPATH, PYTHONHOME, PYTHON . . . . .Ideas? > > Bob I assume we've got a bit of a mailing list timewarp going on here. In any event, I've fixed a couple of problems in CVS and have just confirmed that it all builds from scratch for me. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] 2.5 GS/sec 14-bit A/D converter
On Mon, May 02, 2005 at 01:46:48PM +0930, Tim Ansell wrote: > So where do we request free samples from :P > > The question is how would you get this into a computer? If we round it > up to 16 bits, it makes 4.6 Gigabytes per second. Would a FPGA even be > able to keep up? Could people a lot smarter then me, discuss how this > chip could even possibly be used? > > Tim Ansell Bandpass sampling. You only need on the order of 2x the bandwidth of interest. If the bandwidth of interest is 100 MHz you need about 230 - 250 Msamples/sec. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] using a 48k sound card with wfm_rcv_gui
On Mon, May 02, 2005 at 11:12:07AM -0700, Richard Cagley wrote: > That worked. Thanks. > But, I still only get static (I even have an actual antenna hooked up to the > TV card). Is it because of the warning I'm getting? > > [EMAIL PROTECTED] usrp]$ wfm_rcv_gui.py 93.7 > RX d'board A: TV Rx > RX d'board B: > usrp_standard_rx::set_decim_rate: WARNING rates > 128 result in incorrect > gain. > >>> gr_fir_fff: using SSE Since you are using the TVRX daughter board, you should be using the tvrx_wfm_rcv_gui.py program. wfm_rcv_gui is for people with no RF front end. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] CVS compilation problem (actually a test fails)
On Mon, May 02, 2005 at 09:27:19AM -0700, Matt Ettus wrote: > [EMAIL PROTECTED] wrote: > > Hi, > > > > I can't check the archives at the moment as lists.gnu.org doesn't want > > to talk to anyone, but I don't remember anyone saying anything about > > this. > > > > A couple of weeks ago I compiled and ran all the gnuradio code. I then > > had a disk failure and had to rebuild the whole of my system. I > > downloaded all of the source code again (from CVS) and rebuilt it, but > > now I get the following error: > > > I'm not sure why this test is being run in the core directory. But > anyway, it looks like you need to get the gr-gsm-fr-vocoder module. > > Matt I've backed out digital_voice.py until I find a better solution. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Using USRP from multiple applications simultaneously
Matt, Would you provide a very simple analog-loop-back sample application? I mean, I'd like to hookup a cable between Analog-out to Analog-in, generate some signal e display its waveform on the oscope... I cant seem to make it work -- may be my analog d'board are not working -- unfortunately I dont have a real scope on handy to check it... Angilberto. > ... > The Tx and Rx sides are completely independent and > we often run > different apps for Tx and Rx simultaneously. The Tx > and Rx paths have > different USB endpoints for their streaming data. > ... __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
RE: [Discuss-gnuradio] using a 48k sound card with wfm_rcv_gui
That worked. Thanks. But, I still only get static (I even have an actual antenna hooked up to the TV card). Is it because of the warning I'm getting? [EMAIL PROTECTED] usrp]$ wfm_rcv_gui.py 93.7 RX d'board A: TV Rx RX d'board B: usrp_standard_rx::set_decim_rate: WARNING rates > 128 result in incorrect gain. >>> gr_fir_fff: using SSE > -Original Message- > From: Eric Blossom [mailto:[EMAIL PROTECTED] > Sent: Monday, May 02, 2005 10:04 AM > To: Richard Cagley > Cc: discuss-gnuradio@gnu.org > Subject: Re: [Discuss-gnuradio] using a 48k sound card with wfm_rcv_gui > > On Mon, May 02, 2005 at 07:38:51AM -0700, Richard Cagley wrote: > > Eric, > > Ok, this makes sense, but where do I make the change? Do I need to > recompile > > the audio sink code? I see this hw:0.0 thing mentioned in a header file > in > > gr/include/gnuradio but I can't seem to find the actual code location. > > Thanks, > > -rich > > Looks like these programs need to be updated to support a few more > command line options. > > In the mean while, in wfm_rcv_gui.py, change this: > > # sound card as final sink > audio_sink = audio.sink (int (audio_rate)) > > To this: > > # sound card as final sink > audio_sink = audio.sink (int (audio_rate), "plughw:0,0") > > Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Using USRP from multiple applications simultaneously
On Sun, May 01, 2005 at 06:00:13PM -0700, Angilberto Muniz Sb wrote: > Matt, > Would you provide a very simple analog-loop-back > sample application? I mean, I'd like to hookup a cable > between Analog-out to Analog-in, generate some signal > e display its waveform on the oscope... > > I cant seem to make it work -- may be my analog > d'board are not working -- unfortunately I dont have a > real scope on handy to check it... > > Angilberto. Fire up two windows. In each do: $ cd gnuradio-examples/python/usrp In one of them them: $ ./usrp_siggen.py In the other $ ./usrp_oscope.py or $ ./usrp_fft.py They all have command line options. Try $ ./usrp_siggen.py --help Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] using a 48k sound card with wfm_rcv_gui
On Mon, May 02, 2005 at 07:38:51AM -0700, Richard Cagley wrote: > Eric, > Ok, this makes sense, but where do I make the change? Do I need to recompile > the audio sink code? I see this hw:0.0 thing mentioned in a header file in > gr/include/gnuradio but I can't seem to find the actual code location. > Thanks, > -rich Looks like these programs need to be updated to support a few more command line options. In the mean while, in wfm_rcv_gui.py, change this: # sound card as final sink audio_sink = audio.sink (int (audio_rate)) To this: # sound card as final sink audio_sink = audio.sink (int (audio_rate), "plughw:0,0") Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] What is this?
Just installed SUSE 9.3 on a clean drive and am getting this problem. gnuradio-core goes first in the for-all-dirs list with ../buildit and this error is the first in the list of tests. I then tried making and installing the gr-gsm vocoder stuff first and this still results. I have fiddled with PYTHONPATH, PYTHONHOME, PYTHON . . . . .Ideas? Bob = ERROR: test_blks_import (__main__.test_head) -- Traceback (most recent call last): File "./qa_kludged_imports.py", line 35, in test_blks_import from gnuradio import blks File "/usr/local/src/gr-build/gnuradio-core/src/python/gnuradio/blks/__init__.py", line 37, in ? exec "from gnuradio.blksimpl.%s import *" % (f,) File "", line 1, in ? File "/usr/local/src/gr-build/gnuradio-core/src/python/gnuradio/blksimpl/digital_voice.py", line 33, in ? from gnuradio.vocoder import gsm_full_rate ImportError: No module named vocoder ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] 2.5 GS/sec 14-bit A/D converter
So where do we request free samples from :P The question is how would you get this into a computer? If we round it up to 16 bits, it makes 4.6 Gigabytes per second. Would a FPGA even be able to keep up? Could people a lot smarter then me, discuss how this chip could even possibly be used? Tim Ansell On Wed, 2005-04-27 at 12:54 -0700, Eric Blossom wrote: > The punchline is towards the end of this article: > > http://rfdesign.com/mag/radio_new_technology_facilitates > > TechnoConcepts' RF to digital converter is the first 5 GHz carrier > speed RF to digital converter capable of direct conversion of a 5 GHz > RF carrier, eliminating all analog IF circuits. This receiver is based > on a very high speed 5 GHz delta-sigma converter that digitizes > signals by modulating the analog input (radio signal) into a > high-speed 1-bit digital datastream. The datastream is then digitally > processed on the same IC to produce a high-resolution multiple bit > word stream sent at a slower data rate. This is the first device to > completely eliminate the need for conventional radio receiver > downconverters and the associated external analog components. This RF > to digital converter is a closed-loop system in which the order of the > loop and the input bandwidth may be changed to achieve the desired > resolution. A narrow bandwidth results in higher resolution than a > wide bandwidth. > > > > Parameter GaAsSiGe > > Maximum clock frequency > 5 GHz > 15 GHz > SINAD (signal to noise+distortion) > 70 dB > 110 dB > Eff. resolution bits at 2.5 GHz carrier: 14 bits 18 bits > 10 MHz BW 11 bits 14 bits > > > ___ > 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] CVS compilation problem (actually a test fails)
On Mon, May 02, 2005 at 05:16:30PM +0100, [EMAIL PROTECTED] wrote: > > Hi, > > I can't check the archives at the moment as lists.gnu.org doesn't want > to talk to anyone, but I don't remember anyone saying anything about > this. > > A couple of weeks ago I compiled and ran all the gnuradio code. I then > had a disk failure and had to rebuild the whole of my system. I > downloaded all of the source code again (from CVS) and rebuilt it, but > now I get the following error: > > >>> gr_fir_fff: using 3DNow! > . > -- > Ran 1 test in 0.011s > > OK > E. > == > ERROR: test_blks_import (__main__.test_head) > -- > Traceback (most recent call last): > File "./qa_kludged_imports.py", line 35, in test_blks_import > from gnuradio import blks > File > "/data/matt/usrp/gr-build/gnuradio-core/src/python/gnuradio/blks/__init__.py", > line 37, in ? > exec "from gnuradio.blksimpl.%s import *" % (f,) > File "", line 1, in ? > File > "/data/matt/usrp/gr-build/gnuradio-core/src/python/gnuradio/blksimpl/digital_voice.py", > line 33, in ? > from gnuradio.vocoder import gsm_full_rate > ImportError: No module named vocoder > -- > Ran 2 tests in 0.100s > > FAILED (errors=1) > . This is an unintended consequence of how I'm handling the blks module. I'll see if I can come up with a better solution. Background: I've just recently added a digital voice hierarchical block that glues together the GSM 06.11 full rate vocoder and the GMSK code. It's trying to load the vocoder module (which you haven't installed and shouldn't have to) and failing. To get past this: $ rm gnuradio-core/src/python/gnuradio/blksimpl/digital_voice.py You know you're in trouble when test code named "qa_kludged_imports.py" is failing ;-) Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] CVS compilation problem (actually a test fails)
I've posted an installation guide for GNU radio that might be helpful: http://www.kd7lmo.net/ground_gnuradio_install.html Maybe someone can post a link from the Wiki to my site. On Mon, 2 May 2005, n4hy wrote: > I wasted an entire WEEKEND trying to figure this out. > > Bob > > > [EMAIL PROTECTED] wrote: > > >Hi, > > > >I can't check the archives at the moment as lists.gnu.org doesn't want > >to talk to anyone, but I don't remember anyone saying anything about > >this. > > > >A couple of weeks ago I compiled and ran all the gnuradio code. I then > >had a disk failure and had to rebuild the whole of my system. I > >downloaded all of the source code again (from CVS) and rebuilt it, but > >now I get the following error: > > > > > > > gr_fir_fff: using 3DNow! > > > >. > >-- > >Ran 1 test in 0.011s > > > >OK > >E. > >== > >ERROR: test_blks_import (__main__.test_head) > >-- > >Traceback (most recent call last): > > File "./qa_kludged_imports.py", line 35, in test_blks_import > >from gnuradio import blks > > File > > "/data/matt/usrp/gr-build/gnuradio-core/src/python/gnuradio/blks/__init__.py", > > line 37, in ? > >exec "from gnuradio.blksimpl.%s import *" % (f,) > > File "", line 1, in ? > > File > > "/data/matt/usrp/gr-build/gnuradio-core/src/python/gnuradio/blksimpl/digital_voice.py", > > line 33, in ? > >from gnuradio.vocoder import gsm_full_rate > >ImportError: No module named vocoder > >-- > > > > > > > > ___ > 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] Prof. Moglen's speech at linux.conf.au
Yes, the recording of Bdale's talk will be up shortly. (I will post to this list when I have a URL.) Don't know the quality yet, but the sound seems okay. Thanks for producing such a cool project, and thanks Bdale for giving the talk :P Tim Ansell On Wed, 2005-04-27 at 11:05 -0600, Bdale Garbee wrote: > [EMAIL PROTECTED] (Ramakrishnan Muthukrishnan) writes: > > > There is an article (only for paid readers at the moment) on Prof Moglen's > > speech at linux.conf.au. Here is a quote on SDR situation in Japan. > > This came in response to a question from the audience from someone who had > attended the talk I gave on SDR and gnuradio at the embedded Linux miniconf > prior to LCA. Thanks to Eric for the slide set, which I updated with hardware > photos and a few of my own observations (will get that out where others can > see it sometime soon, too busy today). My talk was very well received. > > In fact, after Eben's keynote and this discussion in the Q&A, someone > suggested > to the organizers that I should give the talk again as one of the three "best > of" repeats on the afternoon of the last day, and they agreed. So I gave the > talk again to a much larger (but less focussed/intimate) audience just before > the closing session, hopefully raising the awareness of many LCA attendees to > what SDR is all about and what some of the issues are. > > I believe audio and video of at least some of the LCA talks will show up on > the web in a few weeks. > > Bdale > > > ___ > 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] CVS compilation problem (actually a test fails)
Same here and I was on a fresh installation: SUSE 9.3 using Python 2.4 and nothing I did would get it straight. Bob [EMAIL PROTECTED] wrote: Matt Ettus writes: > [EMAIL PROTECTED] wrote: > > Hi, > > > > I can't check the archives at the moment as lists.gnu.org doesn't want > > to talk to anyone, but I don't remember anyone saying anything about > > this. > > > > A couple of weeks ago I compiled and ran all the gnuradio code. I then > > had a disk failure and had to rebuild the whole of my system. I > > downloaded all of the source code again (from CVS) and rebuilt it, but > > now I get the following error: > > > I'm not sure why this test is being run in the core directory. But > anyway, it looks like you need to get the gr-gsm-fr-vocoder module. > > Matt I tried to compile the gr-...-vocoder module and it made a directory in /usr/local/lib/python2.3/site-packages/gnuradio/vocoder with files in it. So that seemed to work OK, however gnuradio-core still failed to 'see' it when doing the 'make check' part of the build script (exactly the same error as before). At this point I deleted the contents of the digital_voice.py file and everything now works! (Well, the compliation has moved onto the next directory). I think someone needs to check the build process (for a fresh installation). Thanks, Matt ___ 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] Using USRP from multiple applications simultaneously
On Sun, May 01, 2005 at 02:17:29PM -0700, Eric Blossom wrote: > The Tx and Rx sides are completely independent and we often run > different apps for Tx and Rx simultaneously. The Tx and Rx paths have > different USB endpoints for their streaming data. This is what allows > different apps/processes to open them. They share a common control > endpoint (EP0), but that can be opened by more than one processes > since only usb command packets are used. I seem to be unable to run usrp_siggen and usrp_fft simultaneously. I will try to investigate what exactly the issue is, and get back to you. > It would be possible with a bit of hacking to run endpoints 2, 4, 6 > and 8 "double buffered", 2 512 byte buffers each. That would give us > 4 bulk endpoints to work with (and would also lower the worst case > latency). that would allow us to have two bulk-in and two bulk-out, each belonging to one of the daughterboards. Only complex samples of the same channel would be multiplexed within one endpoint. Sounds good. > > Seperating it into four interfaces (2rx, 2tx) might be complicated, > > since there certainly are shared data structures and functional blocks. > > Mostly the complication comes in the FPGA. [...] Thanks for your elaboration on that. This was what I actually feared. Especially since I've noticed that you're already running out of cells on the FPGA... -- - Harald Welte <[EMAIL PROTECTED]> http://gnumonks.org/ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) pgpfZtCMaM01v.pgp Description: PGP signature ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] CVS compilation problem (actually a test fails)
I wasted an entire WEEKEND trying to figure this out. Bob [EMAIL PROTECTED] wrote: Hi, I can't check the archives at the moment as lists.gnu.org doesn't want to talk to anyone, but I don't remember anyone saying anything about this. A couple of weeks ago I compiled and ran all the gnuradio code. I then had a disk failure and had to rebuild the whole of my system. I downloaded all of the source code again (from CVS) and rebuilt it, but now I get the following error: gr_fir_fff: using 3DNow! . -- Ran 1 test in 0.011s OK E. == ERROR: test_blks_import (__main__.test_head) -- Traceback (most recent call last): File "./qa_kludged_imports.py", line 35, in test_blks_import from gnuradio import blks File "/data/matt/usrp/gr-build/gnuradio-core/src/python/gnuradio/blks/__init__.py", line 37, in ? exec "from gnuradio.blksimpl.%s import *" % (f,) File "", line 1, in ? File "/data/matt/usrp/gr-build/gnuradio-core/src/python/gnuradio/blksimpl/digital_voice.py", line 33, in ? from gnuradio.vocoder import gsm_full_rate ImportError: No module named vocoder -- ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] CVS compilation problem (actually a test fails)
Matt Ettus writes: > [EMAIL PROTECTED] wrote: > > Hi, > > > > I can't check the archives at the moment as lists.gnu.org doesn't want > > to talk to anyone, but I don't remember anyone saying anything about > > this. > > > > A couple of weeks ago I compiled and ran all the gnuradio code. I then > > had a disk failure and had to rebuild the whole of my system. I > > downloaded all of the source code again (from CVS) and rebuilt it, but > > now I get the following error: > > > I'm not sure why this test is being run in the core directory. But > anyway, it looks like you need to get the gr-gsm-fr-vocoder module. > > Matt I tried to compile the gr-...-vocoder module and it made a directory in /usr/local/lib/python2.3/site-packages/gnuradio/vocoder with files in it. So that seemed to work OK, however gnuradio-core still failed to 'see' it when doing the 'make check' part of the build script (exactly the same error as before). At this point I deleted the contents of the digital_voice.py file and everything now works! (Well, the compliation has moved onto the next directory). I think someone needs to check the build process (for a fresh installation). Thanks, Matt ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
RE: [Discuss-gnuradio] ImportError: libwx_gtk2d_xrc-2.6.so.0
Yes, it was a library path problem. Thanks. > -Original Message- > From: LRK [mailto:[EMAIL PROTECTED] > Sent: Sunday, May 01, 2005 11:45 AM > To: Rich Cagley > Cc: Discuss-gnuradio@gnu.org > Subject: Re: [Discuss-gnuradio] ImportError: libwx_gtk2d_xrc-2.6.so.0 > > On Fri, Apr 29, 2005 at 04:11:08PM +, Rich Cagley wrote: > > I just got my usrp installed with Fedora Core 3 and am having the > > > > [EMAIL PROTECTED] usrp]# usrp_oscope.py > > Traceback (most recent call last): > > File "./usrp_oscope.py", line 26, in ? > > from gnuradio.wxgui import stdgui, fftsink, scopesink > > File "/home/rcagley/gr/lib/python2.3/site- > > packages/gnuradio/wxgui/stdgui.py", line 24, in ? > > import wx > > File "/home/rcagley/gr/lib/python2.3/site-packages/wx-2.6-gtk2- > > ansi/wx/__init__.py", line 42, in ? > > from wx._core import * > > File "/home/rcagley/gr/lib/python2.3/site-packages/wx-2.6-gtk2- > > ansi/wx/_core.py", line 4, in ? > > import _core_ > > ImportError: libwx_gtk2d_xrc-2.6.so.0: cannot open shared object file: > > No such file or directory > > > > any ideas? > > I find that file in the lib directory. You may need LD_LIBRARY_PATH > set to /home/rcagley/gr/lib > > > -- > LRK > [EMAIL PROTECTED] ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
RE: [Discuss-gnuradio] using a 48k sound card with wfm_rcv_gui
I couldn't get this to work: [EMAIL PROTECTED] usrp]$ wfm_rcv_gui.py 92.9 Traceback (most recent call last): File "./wfm_rcv_gui.py", line 4, in ? from gnuradio import audio_oss as audio ImportError: cannot import name audio_oss > -Original Message- > From: [EMAIL PROTECTED] [mailto:discuss- > [EMAIL PROTECTED] On Behalf Of mjam01 > Sent: Sunday, May 01, 2005 1:07 PM > To: discuss-gnuradio@gnu.org > Subject: Re: [Discuss-gnuradio] using a 48k sound card with wfm_rcv_gui > > hey, > > if eric's doesn't work and alsa is forcing 48k then change: > > from gnuradio import audio > > to: > > from gnuradio import audio_oss as audio > > it worked for me anyhow > > mike > m0mik.org/gnuradio/ > > On 5/1/05, Eric Blossom <[EMAIL PROTECTED]> wrote: > > On Fri, Apr 29, 2005 at 05:19:46PM -0700, Richard Cagley wrote: > > > Is there a way to use a 48k sound card with the wfm_rc_gui.py? I can't > seem > > > to come up with a adc and audio decimation that works out to 48k > instead of > > > the standard 32k. > > > Thanks, > > > -rich > > > > If you're using ALSA, use plughw:0,0 (or is hwplug:0,0 ??) instead of > the > > default hw:0,0 for the audio PCM device name. plughw will perform > > sample rate conversion for you. > > > > Eric > > > > > > ___ > > 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] CVS compilation problem (actually a test fails)
[EMAIL PROTECTED] wrote: > Hi, > > I can't check the archives at the moment as lists.gnu.org doesn't want > to talk to anyone, but I don't remember anyone saying anything about > this. > > A couple of weeks ago I compiled and ran all the gnuradio code. I then > had a disk failure and had to rebuild the whole of my system. I > downloaded all of the source code again (from CVS) and rebuilt it, but > now I get the following error: I'm not sure why this test is being run in the core directory. But anyway, it looks like you need to get the gr-gsm-fr-vocoder module. Matt ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
RE: [Discuss-gnuradio] using a 48k sound card with wfm_rcv_gui
Eric, Ok, this makes sense, but where do I make the change? Do I need to recompile the audio sink code? I see this hw:0.0 thing mentioned in a header file in gr/include/gnuradio but I can't seem to find the actual code location. Thanks, -rich > -Original Message- > From: Eric Blossom [mailto:[EMAIL PROTECTED] > Sent: Sunday, May 01, 2005 10:53 AM > To: Richard Cagley > Cc: discuss-gnuradio@gnu.org > Subject: Re: [Discuss-gnuradio] using a 48k sound card with wfm_rcv_gui > > On Fri, Apr 29, 2005 at 05:19:46PM -0700, Richard Cagley wrote: > > Is there a way to use a 48k sound card with the wfm_rc_gui.py? I can't > seem > > to come up with a adc and audio decimation that works out to 48k instead > of > > the standard 32k. > > Thanks, > > -rich > > If you're using ALSA, use plughw:0,0 (or is hwplug:0,0 ??) instead of the > default hw:0,0 for the audio PCM device name. plughw will perform > sample rate conversion for you. > > Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] CVS compilation problem (actually a test fails)
Hi, I can't check the archives at the moment as lists.gnu.org doesn't want to talk to anyone, but I don't remember anyone saying anything about this. A couple of weeks ago I compiled and ran all the gnuradio code. I then had a disk failure and had to rebuild the whole of my system. I downloaded all of the source code again (from CVS) and rebuilt it, but now I get the following error: >>> gr_fir_fff: using 3DNow! . -- Ran 1 test in 0.011s OK E. == ERROR: test_blks_import (__main__.test_head) -- Traceback (most recent call last): File "./qa_kludged_imports.py", line 35, in test_blks_import from gnuradio import blks File "/data/matt/usrp/gr-build/gnuradio-core/src/python/gnuradio/blks/__init__.py", line 37, in ? exec "from gnuradio.blksimpl.%s import *" % (f,) File "", line 1, in ? File "/data/matt/usrp/gr-build/gnuradio-core/src/python/gnuradio/blksimpl/digital_voice.py", line 33, in ? from gnuradio.vocoder import gsm_full_rate ImportError: No module named vocoder -- Ran 2 tests in 0.100s FAILED (errors=1) . -- Ran 5 tests in 0.003s OK ... -- Ran 3 tests in 0.017s OK . -- Ran 1 test in 0.005s OK -- Ran 4 tests in 0.025s OK ... -- Ran 3 tests in 0.018s OK FAIL: run_tests === 1 of 1 tests failed === make[5]: *** [check-TESTS] Error 1 make[5]: Leaving directory `/data/matt/usrp/gr-build/gnuradio-core/src/python/gnuradio/gr' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/data/matt/usrp/gr-build/gnuradio-core/src/python/gnuradio/gr' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/data/matt/usrp/gr-build/gnuradio-core/src/python/gnuradio' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/data/matt/usrp/gr-build/gnuradio-core/src/python' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/data/matt/usrp/gr-build/gnuradio-core/src' make: *** [check-recursive] Error 1 >>> build FAILED in /data/matt/usrp/gr-build/gnuradio-core I'm not sure how to debug this as I'm not that familiar with python. To be it seems that the 'vocoder' module was not included in the gnuradio python module. As its using the libtool stuff, I'm not exactly sure where its picking any of its dependencies up from, or even if its picking up some from the previous installation. Any help in getting it to work would be appreciated (as I have my USRP sitting here on my desk looking bored!). Thanks, Matt ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
