Re: [Discuss-gnuradio] Mode S // DME // Classical SSR

Hi Andrew, I am glad to find you have done the work of SSR detection and decoding. I am struggling to do the same things . Could you send your whole project to me? Thanks, Tang -- View this message in context: http://gnuradio.4.n7.nabble.com/Mode-S-DME-Classical-SSR-tp9400p46610.html Sent fro

Re: [Discuss-gnuradio] Segmentation fault in narrowband benchmark_rx.py

Sorry that I forgot to run "bt" yesterday. Here is the output of bt. = manu@radio1:narrowband$ gdb python GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2.1) 7.4-2012.04 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 o

[Discuss-gnuradio] RuntimeError: audio_oss_sink

Hi Alex, I ran into the same problem with pybombs on Ubuntu. It seems there is a missing dependency for audio support for Ubuntu based distros. The missing package is libasound2-dev. I never figured out how to rebuild just the gr-audio portion, so I just rebuilt the gnuradio package. -Scott___

Re: [Discuss-gnuradio] (GSoC) MIMO system

On 02/26/2014 01:57 AM, Karan Talasila wrote: > Hi Alick, > Do you have an english copy of your thesis? I am looking to > read up on MIMO implementation and try a few basic things on gnuradio. > Sorry, but I do not. I suggest you read the application notes "Synchronization and MIMO C

Re: [Discuss-gnuradio] OOT Decimation Module dropping data samples

I have figured out what was happening for me. As I was deprecating the source code to put out publicly, I noticed something that looking at now was a glaring red flag. Inside my OOT, I was copying the GNURadio buffered data into a vector for computation on the large set of data. I knew that it w

Re: [Discuss-gnuradio] RuntimeError: audio_oss_sink

Hi Alex, the dial_tone.py that comes with my version of GR from the git (docs/exploring-gnuradio/dial_tone.py) uses the audio_sink, and not the audio_oss_sink, and works quite fine on an alsa-only system. Generally, when I grep my git repo for "oss_sink", only gr-audio/lib/oss/oss_sink.cc match

Re: [Discuss-gnuradio] OOT Decimation Module dropping data samples

Martin, Thank you for the quick response to my issue! I cannot release the source code as is, however I can describe what I am doing, and possibly if need be I can release a deprecated version that still exhibits this behavior. I am taking 1 MHz of spectrum and putting this through a 50 channel

Re: [Discuss-gnuradio] Segmentation fault in narrowband benchmark_rx.py

Also hoping that it would solve the issue, I rebuilt GNU Radio from todays pull. But that didn't help. manu@radio1:narrowband$ gnuradio-config-info -v v3.7.2.1-251-g67882eec On Thu, Feb 27, 2014 at 12:26 AM, Manu T S wrote: > > Thanks for the help. Here is the output. > >

Re: [Discuss-gnuradio] Segmentation fault in narrowband benchmark_rx.py

Thanks for the help. Here is the output. manu@radio1:narrowband$ gdb python GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2.1) 7.4-2012.04 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later

Re: [Discuss-gnuradio] Segmentation fault in narrowband benchmark_rx.py

Hi, Thanks for the responses. Output to "lscpu", "cat /proc/cpuinfor", "gcc -v", "python" can be found in the link below: http://home.iitb.ac.in/~manu.ts/cpu-info I am still figuring out how to get the backtrace. On Wed, Feb 26, 2014 at 11:26 PM, West, Nathan wrote: > On Wednesday, February

Re: [Discuss-gnuradio] Segmentation fault in narrowband benchmark_rx.py

> On Wed, Feb 26, 2014 at 11:26 PM, West, Nathan > wrote: >> >> On Wednesday, February 26, 2014, Tom Rondeau wrote: >>> >>> On Wed, Feb 26, 2014 at 12:01 PM, Manu T S wrote: >>> > Hello Everyone, >>> > >>> > Not sure if this is already discussed here. >>> > >>> > I am facing segmentation fault w

[Discuss-gnuradio] RuntimeError: audio_oss_sink

I just installed gnuradio using pybombs, and the install appeared to complete with no errors. When trying to run dial_tone.py, I receive the following error: audio_oss_sink: /dev/dsp: No such file or directory Traceback (most recent call last): File "./dial_tone.py", line 61, in my_top_blo

Re: [Discuss-gnuradio] Segmentation fault in narrowband benchmark_rx.py

On Wednesday, February 26, 2014, Tom Rondeau wrote: > On Wed, Feb 26, 2014 at 12:01 PM, Manu T S > > > wrote: > > Hello Everyone, > > > > Not sure if this is already discussed here. > > > > I am facing segmentation fault when running benchmark_rx in narrowband > > examples. It seems like those e

Re: [Discuss-gnuradio] broken gnuplot

On Wed, Feb 26, 2014 at 6:23 AM, Nemanja Savic wrote: > When I use nongl option, then the gui looks like on the figure I posted, and > when I use gl option, the follosing error occures: > Traceback (most recent call last): > File "/home/savi_ne/work/gnuradio/GRC/top_block.py", line 14, in >

Re: [Discuss-gnuradio] Segmentation fault in narrowband benchmark_rx.py

On Wed, Feb 26, 2014 at 12:01 PM, Manu T S wrote: > Hello Everyone, > > Not sure if this is already discussed here. > > I am facing segmentation fault when running benchmark_rx in narrowband > examples. It seems like those example used to work fine before, but now they > are having these issues.

[Discuss-gnuradio] Async message flow control

How does one achieve flow control with the new style message passing API? I have a use case in which I'm generating packets in one flowgraph and pushing them through a pdu_to_tagged_stream (P2TS) block to be modulated in another flowgraph. I believe I'm overwhelming the P2TS block's queue becaus

[Discuss-gnuradio] Segmentation fault in narrowband benchmark_rx.py

Hello Everyone, Not sure if this is already discussed here. I am facing segmentation fault when running benchmark_rx in narrowband examples. It seems like those example used to work fine before, but now they are having these issues. on the receiver side === manu@

Re: [Discuss-gnuradio] gr-audio OSX fixes test branch

On Feb 26, 2014, at 4:57, Michael Dickens wrote: >> The behavior on not finding the specified device should not be using the >> default device; instead, it should fail in a way the caller can observe. >> Doing otherwise creates or hides bugs. (For example, suppose I'm building a >> publicly ac

Re: [Discuss-gnuradio] gr-audio OSX fixes test branch

On Wed, Feb 26, 2014 at 7:57 AM, Michael Dickens wrote: > Hi Kevin - Thanks for the feedback and related info; it's nice to hear from > another GR on OSX user! I'll push changes to the sink either today or > tomorrow for testing. - MLD > > On Feb 26, 2014, at 12:33 AM, Kevin Reid wrote: >> For

Re: [Discuss-gnuradio] Message API questions

On Wed, Feb 26, 2014 at 9:26 AM, Nowlan, Sean wrote: > > > From: Aditya Dhananjay [mailto:adi...@cs.nyu.edu] > Sent: Wednesday, February 26, 2014 8:53 AM > To: Nowlan, Sean > Cc: discuss-gnuradio@gnu.org > Subject: Re: [Discuss-gnuradio] Message API questions > > > On Wed, Feb 26, 2014 at 8:45 AM,

Re: [Discuss-gnuradio] Message API questions

From: Aditya Dhananjay [mailto:adi...@cs.nyu.edu] Sent: Wednesday, February 26, 2014 8:53 AM To: Nowlan, Sean Cc: discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] Message API questions On Wed, Feb 26, 2014 at 8:45 AM, Nowlan, Sean mailto:sean.now...@gtri.gatech.edu>> wrote: I have a f

Re: [Discuss-gnuradio] Message API questions

On Wed, Feb 26, 2014 at 8:45 AM, Nowlan, Sean wrote: > I have a few questions regarding messages in GR. > > > > 1) Is it possible to mix-and-match the old style message sink/source > blocks with the new style message passing API? Any guidance on how to make > the connections? I didn't have m

Re: [Discuss-gnuradio] Loopback flowgraph

Remove the printf. Put in "tag debug" blocks at different points in your flowgraph to see what's going on. On Wed, Feb 26, 2014 at 8:34 AM, raf raf wrote: > Hello all GnuRadio users, > > I wanted to have a flowgraph without an USRP source and USRP sink, only by > using the software blocks. The

Re: [Discuss-gnuradio] Loopback flowgraph

Hi Raf Raf, I'm not quite sure this is what's happening here, but: Threading with python and GNU Radio can be a bit tricky, and even more tricky when you use a GUI framework. Maybe you should elaborate on what you mean with "I attached a thread", so we can understand your architecture better :)

[Discuss-gnuradio] Message API questions

I have a few questions regarding messages in GR. 1) Is it possible to mix-and-match the old style message sink/source blocks with the new style message passing API? Any guidance on how to make the connections? I didn't have much luck with msg_connect. I don't think the message sink/source

Re: [Discuss-gnuradio] Link FFTW3 in OOT module

Hi Mischa, we need to make an FAQ of this :) actually, to use the fftw, you need to directly link to the fftw. Depending on whether you need the single precision floating point version ("fftwf_*" which GNU Radio uses) or the double precision one ("fftw_*"), you can use the FindFFTW3(f).cmake sc

[Discuss-gnuradio] Loopback flowgraph

Hello all GnuRadio users, I wanted to have a flowgraph without an USRP source and USRP sink, only by using the software blocks. The objective is to transmit and receive the BPSK modulated packets. I attached a thread at the receiver to watch if the packets are demodulated. When I run my flowg

[Discuss-gnuradio] Link FFTW3 in OOT module

Dear all I try to link the FFTW3 lib to my OOT module but always get the error: Linking CXX executable test-mymodule libgnuradio-mymodule.so: undefined reference to `fftw_plan_dft_1d' libgnuradio-mymodule.so: undefined reference to `fftw_destroy_plan' libgnuradio-mymodule.so: undefined reference

Re: [Discuss-gnuradio] Bypassing CIC and half-band filter on N2x0

Thanks, I did manage to sample two real channels at 25 MHz! I set the NCO to 0 and the mux to "A:AB". I don't know why I didn't think of this trick earlier. Now the real part is channel 0 and and imaginary part channel 1. I will next try to do the fpga mod. Can you point me to the correct file in

Re: [Discuss-gnuradio] gr-audio OSX fixes test branch

Hi Kevin - Thanks for the feedback and related info; it's nice to hear from another GR on OSX user! I'll push changes to the sink either today or tomorrow for testing. - MLD On Feb 26, 2014, at 12:33 AM, Kevin Reid wrote: > For the audio source, flowgraph start/stop/reconfiguring and specifyin

Re: [Discuss-gnuradio] broken gnuplot

When I use nongl option, then the gui looks like on the figure I posted, and when I use gl option, the follosing error occures: Traceback (most recent call last): File "/home/savi_ne/work/gnuradio/GRC/top_block.py", line 14, in from gnuradio.wxgui import fftsink2 File "/usr/local/lib64/pyt

Re: [Discuss-gnuradio] OOT Decimation Module dropping data samples

On 02/26/2014 01:31 AM, Michael Berman wrote: > I am seeing some odd behavior with an OOT decimation block. What I am > seeing is chunks of data are being dropped down to noise for random > calls of the work function in my OOT. To observe this happening, I > tee'd off the connection going into my

Re: [Discuss-gnuradio] QPSK over air

Hi Mark, the gr-dvbt has a QPSK, QAM-16 and QAM-64 implementation of constellation for both Tx/Rx. The standard it implements is ETSI 300 744 which is OFDM based in which each subcarier is modulated using the modulations above. Regards, Bogdan On Tuesday, February 25, 2014 8:12 PM, "SOUTH

Re: [Discuss-gnuradio] GSoC2014 Turbo Equalizer

On 25.02.2014 19:09, Martin Braun wrote: On 02/25/2014 04:39 PM, Achilleas Anastasopoulos wrote: Just FYI, the gr-trellis has implementations of all these components you suggested. One interesting project is to take the core algorithms of gr-trellis (Viterbi and SISO) and make them threaded for

Re: [Discuss-gnuradio] Bypassing CIC and half-band filter on N2x0

You could only do that by modifying the FPGA. It would be a very minor mod, though. Hook up the undecimated ADC values to where the output of the decimators go, and leave everything else intact. Then just set the decimators as normal and you will get the rate you request. Matt On Tue, Feb 25,