[Discuss-gnuradio] not receiving sound of FM receiver
Thanks Nino and Marcus for the answer I also get some peaks but no sound just like you on n210 with WBX. I set the gain to 30 and using VHF Armature antenna for 100Mhz. still no sound. the same antenna works with any radio receiver. I have spent plenty of time to get something out of n210 with no success. can you help me on this or show me a working FM example or can you give me the right setting parameters for UHD Source WBFM receiver blocks on GRC.I have downloaded some UHD examples from internet but not working. By the way, I have put the constant block after WBFM receiver not before as Marcus suggested. Ahmad ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] not receiving sound of FM receiver
On 25 Sep 2011, at 09:40, ahmad aassbb...@gmail.com wrote: Thanks Nino and Marcus for the answer I also get some peaks but no sound just like you on n210 with WBX. I set the gain to 30 and using VHF Armature antenna for 100Mhz. still no sound. the same antenna works with any radio receiver. I have spent plenty of time to get something out of n210 with no success. can you help me on this or show me a working FM example or can you give me the right setting parameters for UHD Source WBFM receiver blocks on GRC.I have downloaded some UHD examples from internet but not working. By the way, I have put the constant block after WBFM receiver not before as Marcus suggested. Ahmad Hi Ahmad I finally managed to pick up some FM radio stations! I found the antenna was the issue, I followed a tutorial on building a home made fm antenna and set the gain to 300 on the N210. When I get to my computer I'll mail you the GRC file I'm using :0) Nino ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] sine output between packets
It seems my old patch that zeroed out the output of the USRP didn't make it into UHD- we're seeing a constant sine output between packets- and in our case this messes with the receiver unless we use some custom TX cards that have an amp we can shut down with ATR. Is there any way to fix this? ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] X-Ray flare observations with Gnu Radio software
Most interesting, Tell us more how you did it. - antenna used? - daugherboard? - etc Many SDR users in Northern Scandinavia are up day and night listening on submarine traffic on VLF. Patrik - Original Message - From: Marcus D. Leech To: Discuss-gnuradio@gnu.org Sent: Sunday, September 25, 2011 0:06 Subject: [Discuss-gnuradio] X-Ray flare observations with Gnu Radio software Some of you know that among my various activities involving the application of radio to space science, I operate a VLF receiver, called SIDsuite, that is a Gnu Radio based application. Today, sunspot group 1302 has been putting on a great show, and I wanted to share the plot of one of the VLF paths I monitor, which is strongly affected by solar X-Ray flare activity, due to X-Ray flux changing the refractive index of the ionosphere. -- Marcus Leech Principal Investigator Shirleys Bay Radio Astronomy Consortium http://www.sbrac.org -- ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio naa-20110924.png___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] X-Ray flare observations with Gnu Radio software
On 25/09/11 08:29 AM, Patrik Tast wrote: Most interesting, Tell us more how you did it. - antenna used? - daugherboard? - etc Many SDR users in Northern Scandinavia are up day and night listening on submarine traffic on VLF. I use a square-loop antenna, roughly 1.5M in diameter. I have roughly 80M of 22ga wire wound onto it. This feeds a Behringer Mini-Mic 800 microphone preamplifier, which is then fed into a 96KHz sound card--no USRP required. The software I wrote for this I call SIDsuite. It's available via GitHub: https://github.com/patchvonbraun/SIDSuite It works by measuring the received signal stength for various VLF transmitters--most of them are indeed submarine communications systems. The signal strength follows a diurnal pattern involving solar radiation and the D and E layers of the ionosphere. When there are strong solar X-ray events, that pattern is disturbed--sometimes spectacularly. -- Principal Investigator Shirleys Bay Radio Astronomy Consortium http://www.sbrac.org ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] X-Ray flare observations with GnuRadio software
Many thanks for the info. Will try it! Patrik - Original Message - From: Marcus D. Leech To: discuss-gnuradio@gnu.org Sent: Sunday, September 25, 2011 17:04 Subject: Re: [Discuss-gnuradio] X-Ray flare observations with GnuRadio software On 25/09/11 08:29 AM, Patrik Tast wrote: Most interesting, Tell us more how you did it. - antenna used? - daugherboard? - etc Many SDR users in Northern Scandinavia are up day and night listening on submarine traffic on VLF. I use a square-loop antenna, roughly 1.5M in diameter. I have roughly 80M of 22ga wire wound onto it. This feeds a Behringer Mini-Mic 800 microphone preamplifier, which is then fed into a 96KHz sound card--no USRP required. The software I wrote for this I call SIDsuite. It's available via GitHub: https://github.com/patchvonbraun/SIDSuite It works by measuring the received signal stength for various VLF transmitters--most of them are indeed submarine communications systems. The signal strength follows a diurnal pattern involving solar radiation and the D and E layers of the ionosphere. When there are strong solar X-ray events, that pattern is disturbed--sometimes spectacularly. -- Principal Investigator Shirleys Bay Radio Astronomy Consortium http://www.sbrac.org -- ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Status of GNU Radio on Mac OS X
I tried this out, and it almost worked perfectly. Two things needed fiddling: Gnuradio and most of the python dependencies were installed for python2.6. My default was 2.5 so I had to switch to using the 2.6 version installed by macports. Most of the python dependencies were installed to: /opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/ The gnuradio python stuff was installed to: /opt/local/lib/python2.6/site-packages which was not on the python-path and had to be added manually. On Fri, Sep 23, 2011 at 11:57 AM, Michael Dickens m...@alum.mit.edu wrote: If you use MacPorts under Mac OS X 10.5, .6, or .7, sudo port install gnuradio should work as of this morning for installing all of the background dependencies (and, version GR 3.3.0 from the tarball if that's good enough). I had to fix SDCC 2.9 to work under 10.7, as well as tweak GNU Radio 3.3.0 tarball's configure script to correctly set the MD_CPU types under 10.7 (just like when 10.6 came out). It looks like the MD_CPU issue has been fixed since the 3.3.0 release, as the current GIT master seems to build cleanly and make check (as correctly as possible) on 10.7 (64 bit) with no changes (and with Volk disabled). The UDP QA code doesn't work any better on 10.7 than on 10.6. I think the primary OSX issue right now is setting the audio input device sample rate using using it as an audio source. There are a few of us looking into this issue as time allows; hopefully nobody is truly dependent on this feature when using OSX. - MLD ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] error compiling 3.4.1 on ubuntu maverick
i experienced this error while compiling on Ubuntu 10.10 i386 /make[6]: uscita dalla directory /home/artynet/Downloads/gnuradio-3.4.1/gruel/src/swig make[5]: uscita dalla directory /home/artynet/Downloads/gnuradio-3.4.1/gruel/src/swig Making all in python make[5]: ingresso nella directory /home/artynet/Downloads/gnuradio-3.4.1/gruel/src/python make all-am make[6]: ingresso nella directory /home/artynet/Downloads/gnuradio-3.4.1/gruel/src/python make[6]: Nessuna operazione da eseguire per all-am. make[6]: uscita dalla directory /home/artynet/Downloads/gnuradio-3.4.1/gruel/src/python make[5]: uscita dalla directory /home/artynet/Downloads/gnuradio-3.4.1/gruel/src/python make[4]: uscita dalla directory /home/artynet/Downloads/gnuradio-3.4.1/gruel/src make[4]: ingresso nella directory /home/artynet/Downloads/gnuradio-3.4.1/gruel make[4]: Nessuna operazione da eseguire per all-am. make[4]: uscita dalla directory /home/artynet/Downloads/gnuradio-3.4.1/gruel make[3]: uscita dalla directory /home/artynet/Downloads/gnuradio-3.4.1/gruel make[2]: uscita dalla directory /home/artynet/Downloads/gnuradio-3.4.1/gruel Making all in volk make[2]: ingresso nella directory /home/artynet/Downloads/gnuradio-3.4.1/volk make[2]: *** Nessuna regola per generare l'obiettivo all. Arresto. make[2]: uscita dalla directory /home/artynet/Downloads/gnuradio-3.4.1/volk make[1]: *** [all-recursive] Errore 1 make[1]: uscita dalla directory /home/artynet/Downloads/gnuradio-3.4.1 make: *** [all] Errore 2/* *where is the issue ? I always compiled the gnuradio tarball without any problems. thx in advance, Arturo ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Status of GNU Radio on Mac OS X
On Sun, Sep 25, 2011 at 11:15 AM, Ben Reynwar b...@reynwar.net wrote: I tried this out, and it almost worked perfectly. Two things needed fiddling: Gnuradio and most of the python dependencies were installed for python2.6. My default was 2.5 so I had to switch to using the 2.6 version installed by macports. Thanks for the report. Did you see where Python 2.5 failed to work? We're supposed to be compatible with it, so if it's stuff we can fix to make it compatible again, we will. Tom Most of the python dependencies were installed to: /opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/ The gnuradio python stuff was installed to: /opt/local/lib/python2.6/site-packages which was not on the python-path and had to be added manually. On Fri, Sep 23, 2011 at 11:57 AM, Michael Dickens m...@alum.mit.edu wrote: If you use MacPorts under Mac OS X 10.5, .6, or .7, sudo port install gnuradio should work as of this morning for installing all of the background dependencies (and, version GR 3.3.0 from the tarball if that's good enough). I had to fix SDCC 2.9 to work under 10.7, as well as tweak GNU Radio 3.3.0 tarball's configure script to correctly set the MD_CPU types under 10.7 (just like when 10.6 came out). It looks like the MD_CPU issue has been fixed since the 3.3.0 release, as the current GIT master seems to build cleanly and make check (as correctly as possible) on 10.7 (64 bit) with no changes (and with Volk disabled). The UDP QA code doesn't work any better on 10.7 than on 10.6. I think the primary OSX issue right now is setting the audio input device sample rate using using it as an audio source. There are a few of us looking into this issue as time allows; hopefully nobody is truly dependent on this feature when using OSX. - MLD ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Status of GNU Radio on Mac OS X
It wasn't that python2.5 didn't work, rather that macports didn't attempt to install gnuradio for that version. Instead it installed python2.6 and setup gnuradio for that. I've never messed about with macports scripts so I don't know why that might happen. On Sun, Sep 25, 2011 at 3:42 PM, Tom Rondeau trondeau1...@gmail.com wrote: On Sun, Sep 25, 2011 at 11:15 AM, Ben Reynwar b...@reynwar.net wrote: I tried this out, and it almost worked perfectly. Two things needed fiddling: Gnuradio and most of the python dependencies were installed for python2.6. My default was 2.5 so I had to switch to using the 2.6 version installed by macports. Thanks for the report. Did you see where Python 2.5 failed to work? We're supposed to be compatible with it, so if it's stuff we can fix to make it compatible again, we will. Tom Most of the python dependencies were installed to: /opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/ The gnuradio python stuff was installed to: /opt/local/lib/python2.6/site-packages which was not on the python-path and had to be added manually. On Fri, Sep 23, 2011 at 11:57 AM, Michael Dickens m...@alum.mit.edu wrote: If you use MacPorts under Mac OS X 10.5, .6, or .7, sudo port install gnuradio should work as of this morning for installing all of the background dependencies (and, version GR 3.3.0 from the tarball if that's good enough). I had to fix SDCC 2.9 to work under 10.7, as well as tweak GNU Radio 3.3.0 tarball's configure script to correctly set the MD_CPU types under 10.7 (just like when 10.6 came out). It looks like the MD_CPU issue has been fixed since the 3.3.0 release, as the current GIT master seems to build cleanly and make check (as correctly as possible) on 10.7 (64 bit) with no changes (and with Volk disabled). The UDP QA code doesn't work any better on 10.7 than on 10.6. I think the primary OSX issue right now is setting the audio input device sample rate using using it as an audio source. There are a few of us looking into this issue as time allows; hopefully nobody is truly dependent on this feature when using OSX. - MLD ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Status of GNU Radio on Mac OS X
On Sep 25, 2011, at 8:39 PM, Ben Reynwar wrote: It wasn't that python2.5 didn't work, rather that macports didn't attempt to install gnuradio for that version. Instead it installed python2.6 and setup gnuradio for that. I've never messed about with macports scripts so I don't know why that might happen. If you do port info gnuradio, you'll see: gnuradio @3.3.0 (science) Variants: docs, python25, [+]python26, python27 which means that if you do sudo port install gnuradio -- install with default variants -- then it will do so for use with Python 2.6. If you want to use gnuradio with Python 2.5, then you'll want to do sudo port install gnuradio +python25. Hope that helps makes sense. - MLD ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Status of GNU Radio on Mac OS X
On Sun, Sep 25, 2011 at 5:54 PM, Michael Dickens m...@alum.mit.edu wrote: On Sep 25, 2011, at 8:39 PM, Ben Reynwar wrote: It wasn't that python2.5 didn't work, rather that macports didn't attempt to install gnuradio for that version. Instead it installed python2.6 and setup gnuradio for that. I've never messed about with macports scripts so I don't know why that might happen. If you do port info gnuradio, you'll see: gnuradio @3.3.0 (science) Variants: docs, python25, [+]python26, python27 which means that if you do sudo port install gnuradio -- install with default variants -- then it will do so for use with Python 2.6. If you want to use gnuradio with Python 2.5, then you'll want to do sudo port install gnuradio +python25. Hope that helps makes sense. - MLD Makes sense. I didn't know about that. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] making gnuradio blocks entirely in python
So there is a useful feature I think gnuradio is missing, and thats the
ability to rapidly prototype signal processing in python. It would be
great if a python block would have access to all the facilities
available to a block written in a c++ environment.
So I put together pyblock (not to be confused with those other project
by the same name). Its a stand-alone build that links against gnuradio.
https://github.com/guruofquality/pyblock
Theres a few demos: an adder, using tags, interp and decim blocks.
https://github.com/guruofquality/pyblock/tree/master/examples
The interesting thing is that the work functions just call into numpy
routines, so there is a chance that the implementations can be
reasonably fast.
I would like to be able to support history so i can implement a filter
using numpy but I am a little lacking in the basic understanding so fill
me in if you know. Suppose I have this work function:
int work(int noutput_items, gr_vector_const_void_star
input_items,gr_vector_void_star output_items){
const float *in = reinterpret_castconst float *(input_items[0]);
I am assuming history is on the input buffer.
Is the vector in ninput_items + history() items long? Where
ninput_items = noutput_items*/some_factor.
Whats the first index of the first item? Is in[0] or in[0-history()]?
-Josh
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] making gnuradio blocks entirely in python
The in buffer should start at in[0] the history comes into play at allowing
enough valid indices to perform the filtering operation over the entire buffer
which allows N valid output data versus N-nTAPS. When I looked at filtering in
gnuradio the way I thought about it as and at the end I've included some ASCII
art to demonstrate it, from the illustration you can see how the history comes
into play. I'm no DSP engineer but this seems to work for me someone can feel
free to correct me if I'm wrong.
adapted from gr_fir_fff_generic.cc
for(i=0; in; i++)
for(j=0; j ntaps; j++)
out[i] += taps[j] * input[i+j]
0 1 2 3 4 5 6 7 8 9
hist0 hist1 hist2 hist3 in0 in1 in2 in3 in4 in5
tap3 tap2 tap1 tap0
0 1 2 3 4 5 6 7 8 9
hist0 hist1 hist2 hist3 in0 in1 in2 in3 in4 in5
tap3 tap2 tap1 tap0
0 1 2 3 4 5 6 7 8 9
hist0 hist1 hist2 hist3 in0 in1 in2 in3 in4 in5
tap3 tap2 tap1 tap0
0 1 2 3 4 5 6 7 8 9
hist0 hist1 hist2 hist3 in0 in1in2 in3 in4 in5
tap3 tap2 tap1 tap0
0 1 2 3 4 5 6 7 8 9
hist0 hist1 hist2 hist3 in0 in1 in2 in3 in4 in5
tap3 tap2 tap1 tap0
0 1 2 3 4 5 6 7 8 9
hist0 hist1 hist2 hist3 in0 in1 in2 in3 in4 in5
tap3 tap2 tap1 tap0
0 1 2 3 4 5 6 7 8 9
hist0 hist1 hist2 hist3 in0 in1 in2in3in4in5
tap3 tap2 tap1 tap0
al fayez
-Original Message-
From: Josh Blum j...@joshknows.com
To: Discuss-gnuradio Discuss-gnuradio@gnu.org
Sent: Sun, Sep 25, 2011 6:59 pm
Subject: [Discuss-gnuradio] making gnuradio blocks entirely in python
So there is a useful feature I think gnuradio is missing, and thats the
ability to rapidly prototype signal processing in python. It would be
great if a python block would have access to all the facilities
available to a block written in a c++ environment.
So I put together pyblock (not to be confused with those other project
by the same name). Its a stand-alone build that links against gnuradio.
https://github.com/guruofquality/pyblock
Theres a few demos: an adder, using tags, interp and decim blocks.
https://github.com/guruofquality/pyblock/tree/master/examples
The interesting thing is that the work functions just call into numpy
routines, so there is a chance that the implementations can be
reasonably fast.
I would like to be able to support history so i can implement a filter
using numpy but I am a little lacking in the basic understanding so fill
me in if you know. Suppose I have this work function:
int work(int noutput_items, gr_vector_const_void_star
input_items,gr_vector_void_star output_items){
const float *in = reinterpret_castconst float *(input_items[0]);
I am assuming history is on the input buffer.
Is the vector in ninput_items + history() items long? Where
ninput_items = noutput_items*/some_factor.
Whats the first index of the first item? Is in[0] or in[0-history()]?
-Josh
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
