[Discuss-gnuradio] gr-howto OOT tutorial crash

Hi, I have been having some trouble with one of my OOT custom blocks in GRC (check this out: https://lists.gnu.org/archive/html/discuss-gnuradio/2017-07/msg00225.html) so I decided to try a bare bones version of the OOT module flow described here:

Re: [Discuss-gnuradio] Spurious Spikes in RX Data

On 07/16/2017 08:38 PM, Sean Horton wrote: Hi Marcus, I'm not getting overruns, and the signal source was the N210 (I was doing a loopback test). I switched to a hardware radio to transmit data, and the spikes went away. Is that what you'd expect? The spikes were 2000-3000 samples apart. If

Re: [Discuss-gnuradio] Core Dump with Simple_ra and an upgraded Ubuntu system from 14.04 to 16.04 LTS today.

Hi Marcus, Found the issue with command line you gave, namely simple_ra is not the python file so I changed the line to simple_ra_receiver and changed some of the command parameters as and got it to run: john@i7ubuntu:/usr/local/lib$ ls libgnuradio-osmosdr*.* -l -a lrwxrwxrwx

Re: [Discuss-gnuradio] Adding Attenuation in GNU radio

Hi Marcus, Thanks for your response. I'm trying to make a channel simulator where my signal going into the USRP gets attenuated by free space path loss. Typically, I know that this is done through the use of hardware, like fixed attenuators, but I wanted to go into an all DSP approach with the

Re: [Discuss-gnuradio] Adding Attenuation in GNU radio

You can also check out the channel model block in GRC, there's also several other useful blocks under the imparements category that may be useful for modeling different kinds of environments like multipath or doppler. On Jul 16, 2017 6:20 PM, "Jose Ruvalcaba" wrote: > Hi

Re: [Discuss-gnuradio] Spurious Spikes in RX Data

Hi Marcus, I'm not getting overruns, and the signal source was the N210 (I was doing a loopback test). I switched to a hardware radio to transmit data, and the spikes went away. Is that what you'd expect? The spikes were 2000-3000 samples apart. If you don't think I should see those spikes even

Re: [Discuss-gnuradio] gr-howto OOT tutorial crash

Here is the system config: vipin@pp001:~/a1/gr-howto/build$ uname -a Linux pp001 4.8.0-58-generic #63~16.04.1-Ubuntu SMP Mon Jun 26 18:08:51 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux On Sun, Jul 16, 2017 at 12:25 PM, Vipin Sharma wrote: > Hi, > > I have been having

Re: [Discuss-gnuradio] Core Dump with Simple_ra and an upgraded Ubuntu system from 14.04 to 16.04 LTS today.

On 17/07/17 03:08, Marcus D. Leech wrote: On 07/16/2017 11:03 PM, John Shields wrote: Hi Marcus, An update - i reinstalled python-wxgtk2.8 and that dependency was satisfied when I re-ran Marcus' build_gnuradio script. When I run the same command as before, I

Re: [Discuss-gnuradio] gr-howto OOT tutorial crash

I can try re-building the OOT module. I don't think I know how to 'with logging same-same as GR's'. I have two questions: 1) How do I know how GR was built? With logging? 2) Assuming I know the answer to 1) above, where do I change things so that OOT compiles with with same setting for

Re: [Discuss-gnuradio] Core Dump with Simple_ra and an upgraded Ubuntu system from 14.04 to 16.04 LTS today.

On 17/07/17 03:08, Marcus D. Leech wrote: On 07/16/2017 11:03 PM, John Shields wrote: Hi Marcus, An update - i reinstalled python-wxgtk2.8 and that dependency was satisfied when I re-ran Marcus' build_gnuradio script. When I run the same command as before, I

Re: [Discuss-gnuradio] Core Dump with Simple_ra and an upgraded Ubuntu system from 14.04 to 16.04 LTS today.

On 07/17/2017 12:47 AM, John Shields wrote: Even after I re-installed pyephem (for python 2) the issue continues i.e. logger_tp undefined and malloc error. GRC is sane in that I can instantiate a USRP source and display it's FFT. Since the logger issue is a

Re: [Discuss-gnuradio] Runtime AttributeError for custom block

I still continue to shoot in the dark to figure this SWIG issue. I decided to run the 'make test' step as well (after 'sudo make install') step and as expected it fails as well. Looking deeper a bit (using 'ctest -V' under 'build' directory), I see one of the symbols being undefined (see below for

Re: [Discuss-gnuradio] gr-howto OOT tutorial crash

Maybe you're hitting the logger_ptr bug? See < https://github.com/gnuradio/gnuradio/issues/1383[1] > for more info. It happens when GR is built with logging enabled but not log4cpp, and then the OOT is built either with logging enable and log4cpp or logging not enabled. The "free" on gr::block

Re: [Discuss-gnuradio] Core Dump with Simple_ra and an upgraded Ubuntu system from 14.04 to 16.04 LTS today.

Hi Marcus, An update - i reinstalled python-wxgtk2.8 and that dependency was satisfied when I re-ran Marcus' build_gnuradio script. When I run the same command as before, I now get: john@i7ubuntu:~$ ./simp_10.sh linux; GNU C++ version 5.4.0 20160609;

Re: [Discuss-gnuradio] Core Dump with Simple_ra and an upgraded Ubuntu system from 14.04 to 16.04 LTS today.

On 07/16/2017 11:03 PM, John Shields wrote: Hi Marcus, An update - i reinstalled python-wxgtk2.8 and that dependency was satisfied when I re-ran Marcus' build_gnuradio script. When I run the same command as before, I now get: john@i7ubuntu:~$ ./simp_10.sh

Re: [Discuss-gnuradio] Adding Attenuation in GNU radio

Hi Jose, yep, multiply const with a real value |·| < 1 would be **equivalent** to an analog attenuator. anyway, it's very uncommon to do such an operation in DSP, unless you need a fair comparison between different signals or such. Maybe you'd want to explain why you want to do that? Best

[Discuss-gnuradio] Core Dump with Simple_ra and an upgraded Ubuntu system from 14.04 to 16.04 LTS today.

Hi, While I usually regret it, I decided to update my Ubuntu system from 14.04 LTS to 16.04 LTS and it seemed to go fine. I rebuilt GNURadio and UHD and that seemed to go fine but when I run Simple_ra with: simple_ra --aperture 2.4 --ant RX2 --srate 10.0e6 --dbw 8.0e6 --freq 1420.4057e6

Re: [Discuss-gnuradio] Core Dump with Simple_ra and an upgraded Ubuntu system from 14.04 to 16.04 LTS today.

Thanks Marcus, I used the other Marcus' build_gnuradio script and I believe that it rebuilt gr-osmosdr. How would I check? I built 3.7.11.1 on July 7th on 14.04 LTS and today, I rebuilt again on 16.04. Kind

Re: [Discuss-gnuradio] Core Dump with Simple_ra and an upgraded Ubuntu system from 14.04 to 16.04 LTS today.

Hi John, looks like the the problem /might/ (not sure) be that something tries to access a different version of the python libraries than you use now – so, seeing that simple_ra doesn't come with any code that needs to be compiled itself, it does look like there might be a remnant of your

Re: [Discuss-gnuradio] Core Dump with Simple_ra and an upgraded Ubuntu system from 14.04 to 16.04 LTS today.

Hi John, you could find the exact libosmosdr*.so that is used at runtime. Of course, searching your filesystem for any libosmosdr* would be clever, but it might be that you have multiple prefixes or so, so we might as well make sure that at the time python actually starts loading libraries,