Re: GRC version 3.9.0.0 git master (python 3.8.2) + OOT blocks

David, As far as I know, 3.15 is the long term support UHD release, and should be considered the most stable. 4.0 has not been officially released yet (looks like release candidate went out last week). If your research does not involve the newest features of GNU Radio, but you need a stable vers

Re: Ho to use Limesdr and rtl dongles with GNURadio 3.8.2

Thanks Paul This in fact is an important information. To resume I found that following packages installed from source under Ubuntu 20.04 (compiling some of them is tricky) are fully functionnal with GNURadio 3.8.2: librtlsdr gr-osm

Using forgotten id breaks gnuradio-companion

Hi One of my flowgraph was generating the error:     self.audio_sink_0 = audio.sink(audio_rate, '', True)     AttributeError: 'int' object has no attribute 'sink' This error was not easy to debug since the error message sounds like there was a library error (which was not the case here). My

Re: Using forgotten id breaks gnuradio-companion

Since there is no way of knowing what global names will conflict in the future, it could be useful for GRC to prefix ids (id_audio), make them part of another structure (ids.audio), or something similar. This adds complexity to manual coding in Python, so it's a tradeoff. On Mon, Aug 31, 2020 at 1

Funcube Dongle Pro Plus help

Hello Please I am trying to install the FCDPROPLUS which is the Funcube Dongle Pro Plus. This is what I've done following the instructions on the author page: git clone https://github.com/dl1ksv/gr-fcdproplus cd ~/gr-fcdproplus mkdir build cd b

Re: Using forgotten id breaks gnuradio-companion

On Mon, Aug 31, 2020 at 8:11 AM Jeff Long wrote: > Since there is no way of knowing what global names will conflict in the > future, it could be useful for GRC to prefix ids (id_audio), make them part > of another structure (ids.audio), or something similar. This adds > complexity to manual codin

Re: Funcube Dongle Pro Plus help

Vincenzo, please don't open a new thread for every other email you have sent. You have gotten easily confused in the past, and we can avoid that if you can try to focus on staying on a single email thread, and it was a big problem for you. Please don't open a new thread before having solved t

Re: Using forgotten id breaks gnuradio-companion

I'd categorize this somewhere between feature request and bug report. Could you raise this as an issue on github.com/gnuradio/gnuradio/issues , please? Generally, tracking could be possible, but is rather complicated, because we have different namespaces in which parts of the flow graph gene

R: Funcube Dongle Pro Plus help

Sorry Marcus, I thought it was closed as I did not get any reply from a long time. Please what I need to check as I still did not understood how to know The gnuradio path for the correct command: cmake -DCMAKE_INSTALL_PREFIX= "path to gnuradio installation" ../ Thanks 73’s de Enzo IK8OZV EasyLo

Re: R: Funcube Dongle Pro Plus help

Hi Vincenzo, no such thing as "closed" :) Well, that path is where your GNU Radio is installed to. You should be able to check it through `gnuradio-config-info --prefix`. To repeat my questions: 1. Did `cmake...` run through successfully? Or did it end with an error? 2. Did `make` run throu

R: R: Funcube Dongle Pro Plus help

Hi Marcus, thanks for your reply. I gave the command: gnuradio-config-info --prefix and got : /usr/local So I have tried to give the command: cmake -DCMAKE_INSTALL_PREFIX= "/usr/local/" ../ - Checking for module 'mpir >= 3.0' -- No package 'mpir' found -- Could NOT find MPIR (missing: MPIRX

Re: R: R: Funcube Dongle Pro Plus help

You need to be more careful, Vincenzo. The space between = and " is wrong. There mustn't be any space. It should be: cmake -DCMAKE_INSTALL_PREFIX="/usr/local/" ../ Best regards, Marcus On 31/08/2020 20.18, Vincenzo Mone wrote: Hi Marcus, thanks for your reply. I gave the command: gnuradio-co

how to run gdb with gnuradio 3.8 ?

I am trying to debug an OOT in gnuradio 3.8 using gdb. It's a problem with double free() that seems to have popped up with 3.8.2 I rebuilt my OOT with debug symbols. WIthout gdb, it all runs, but of course tells me about the double free() when it shuts down. 1. I've altered the top_block.py to

Re: how to run gdb with gnuradio 3.8 ?

You can run the python interpreter under gdb, outside GRC, and that should capture library errors. Another stranger idea would be to change the "interpreter" under GRC options/advanced to run your program under GDB. I got this to work using something along the lines of: gdb {python} -ex "run -u

R: R: R: R: Funcube Dongle Pro Plus help

Thanks Marcus, it worked no Missing blocks now but when I go to run the Funcube grc file I get tis on the bottom: Generating: '/media/enzo/243A-C1DB/BY70-2/BY70-2/frontend_by702_rx_fcdpp.py' Executing: /usr/bin/python3 -u /media/enzo/243A-C1DB/BY70-2/BY70-2/frontend_by702_rx_fcdpp.py Traceback

Re: how to run gdb with gnuradio 3.8 ?

Interact in which way, enabling what? Maybe I / we have some hints :) On 31.08.20 22:52, Jeff Long wrote: > You can run the python interpreter under gdb, outside GRC, and that should > capture library errors. Another stranger idea would be to change the > "interpreter" under GRC options/advanced t

Re: how to run gdb with gnuradio 3.8 ?

If the console window in GRC were interactive, then you could debug right there, using gdb as the interpreter. I spent a grand total of 5 minutes looking into this, so maybe this is already possible. There's no particular advantage to doing it this way, though, since we assume that the user is fair

Re: how to run gdb with gnuradio 3.8 ?

On 08/31/2020 07:34 PM, Jeff Long wrote: If the console window in GRC were interactive, then you could debug right there, using gdb as the interpreter. I spent a grand total of 5 minutes looking into this, so maybe this is already possible. There's no particular advantage to doing it this way,