Regarding osmocom source missing in gnuradio
Hi, I am using gnu radio v3.8 and UHD v4.2. I can see that there is no specific block for the osmocom source. Is the osmocom source behave as a UHD source? I can also see that there is no specific block for energy detection, cyclostationary detection, and PSK modulation. But, I have seen these blocks in many videos on youtube. So, I need help regarding how to make these blocks. -- *Thanks & Regards,Sumit Kumar AgrawalPh.D. (Electrical Engineering)Indian Institute of TechnologyJodhpur, Rajasthan-342037* *Mob. No.- 8410957412* ᐧ
Re: Regarding osmocom source missing in gnuradio
Hello Sumit: GNU Radio has a feature called "out-of-tree modules". It basically lets you to add 3rd-party signal processing blocks to your GNU Radio installations. Osmocom source is a out-of-tree module from osmocom, called gr-osmosdr. You can replace that with a UHD source, if (and only if) your radio is a USRP from Ettus Research. There are also some out-of-tree modules for energy detection and cyclostationay analysis (like gr-specest). I think the PSK modulation block has been removed from GNU Radio, as it was somewhat buggy and you are better off impelemting it manually as suggested in GNU Radio Wiki ( https://wiki.gnuradio.org/index.php/Guided_Tutorial_PSK_Demodulation ), but I could be wrong about that. If you installed GNU Radio via a package manager (like apt in Debian/Ubuntu), then maybe you can also install some out-of-tree modules via that package manager (like apt install gr-osmosdr). If you manually installed GNU Radio or the modules are not available for your package manager, then you may have to manually build and install the modules (usually involves git clone -> cmake -> make -> make install -> ldconfig). Regards, Kyeong Su Shin 보낸 사람: Sumit Agrawal (P19EE207) 대신 Discuss-gnuradio 보낸 날짜: 2022년 9월 12일 월요일 오후 3:58 받는 사람: discuss-gnuradio@gnu.org 제목: Regarding osmocom source missing in gnuradio Hi, I am using gnu radio v3.8 and UHD v4.2. I can see that there is no specific block for the osmocom source. Is the osmocom source behave as a UHD source? I can also see that there is no specific block for energy detection, cyclostationary detection, and PSK modulation. But, I have seen these blocks in many videos on youtube. So, I need help regarding how to make these blocks. -- Thanks & Regards, Sumit Kumar Agrawal Ph.D. (Electrical Engineering) Indian Institute of Technology Jodhpur, Rajasthan-342037 Mob. No.- 8410957412 [https://mailfoogae.appspot.com/t?sender=aYWdyYXdhbC4xNUBpaXRqLmFjLmlu&type=zerocontent&guid=e21f5a4f-ad52-4270-84d3-c4d9b3e18e7e]ᐧ
Re: Regarding osmocom source missing in gnuradio
Hello Sumit: Sorry, I made some typos in my previous e-mail (I was rushing). Especially, I said "Osmocom source is a out-of-tree module from osmocom," but what I meant is that "Osmocom Source is a part of an out-of-tree module from Osmocom". Regards, Kyeong Su Shin 보낸 사람: Kyeong Su Shin 보낸 날짜: 2022년 9월 12일 월요일 오후 4:17 받는 사람: Sumit Agrawal (P19EE207) ; discuss-gnuradio@gnu.org 제목: Re: Regarding osmocom source missing in gnuradio Hello Sumit: GNU Radio has a feature called "out-of-tree modules". It basically lets you to add 3rd-party signal processing blocks to your GNU Radio installations. Osmocom source is a out-of-tree module from osmocom, called gr-osmosdr. You can replace that with a UHD source, if (and only if) your radio is a USRP from Ettus Research. There are also some out-of-tree modules for energy detection and cyclostationay analysis (like gr-specest). I think the PSK modulation block has been removed from GNU Radio, as it was somewhat buggy and you are better off impelemting it manually as suggested in GNU Radio Wiki ( https://wiki.gnuradio.org/index.php/Guided_Tutorial_PSK_Demodulation ), but I could be wrong about that. If you installed GNU Radio via a package manager (like apt in Debian/Ubuntu), then maybe you can also install some out-of-tree modules via that package manager (like apt install gr-osmosdr). If you manually installed GNU Radio or the modules are not available for your package manager, then you may have to manually build and install the modules (usually involves git clone -> cmake -> make -> make install -> ldconfig). Regards, Kyeong Su Shin 보낸 사람: Sumit Agrawal (P19EE207) 대신 Discuss-gnuradio 보낸 날짜: 2022년 9월 12일 월요일 오후 3:58 받는 사람: discuss-gnuradio@gnu.org 제목: Regarding osmocom source missing in gnuradio Hi, I am using gnu radio v3.8 and UHD v4.2. I can see that there is no specific block for the osmocom source. Is the osmocom source behave as a UHD source? I can also see that there is no specific block for energy detection, cyclostationary detection, and PSK modulation. But, I have seen these blocks in many videos on youtube. So, I need help regarding how to make these blocks. -- Thanks & Regards, Sumit Kumar Agrawal Ph.D. (Electrical Engineering) Indian Institute of Technology Jodhpur, Rajasthan-342037 Mob. No.- 8410957412 [https://mailfoogae.appspot.com/t?sender=aYWdyYXdhbC4xNUBpaXRqLmFjLmlu&type=zerocontent&guid=e21f5a4f-ad52-4270-84d3-c4d9b3e18e7e]ᐧ
AW: Struggling with 3.10 OOT Module Porting: AttributeError: module has no attribute
Hello Vasil,
Thank you for your help. Editing python/__init__.py did solve my current
problem: After changing the exception handling to the following I was able to
move on to other issues while porting.
try:
# this might fail if the module is python-only
from .myModule_python import *
except ImportError:
dirname, filename = os.path.split(os.path.abspath(__file__))
__path__.append(os.path.join(dirname, "bindings"))
from . myModule _python import *
except ModuleNotFoundError:
dirname, filename = os.path.split(os.path.abspath(__file__))
__path__.append(os.path.join(dirname, "bindings"))
from . myModule_python import *
Re-installing my module gave me this cmake error:
CMake Error at lib/CMakeLists.txt … Target “gnuradio-myModule”
links to: gnuradio::gnuradio-fec but the target was not found.
I was able to solve this by removing the gnuradio:: qualifier from gnuradio-fec
and gnuradio-analog. For some reason, only gnuradio-fec but not
gnuradio::gnuradio-fec is known. Could this be an unintended bug? Under Gnu
Radio 3.8.5 gnuradio::gnuradio-fec was able to be found.
But right now I’m struggling with a new problem that I’m unable to solve:
Calling import myModule_python in gr-myModule/build/python/myModule/bindings/
throws a segmentation fault which gets traced back to
/usr/local/lib/python3.10/dist-packages/gnuradio/gr/__init__.py
The line responsible for the segfault is:
log.set_level(prefs().get_string("LOG", "log_level", "notset"))
Context for the line:
log = gr.logger("log")
log.set_level(prefs().get_string("LOG", "log_level", "notset"))
log_debug = gr.logger("log_debug")
Again I would be very thankful if someone could help me.
Thank you and regards,
Luca
>-Ursprüngliche Nachricht-
>Von: Vasil Velichkov
>Gesendet: Freitag, 9. September 2022 15:06
>An: Bachmaier, Luca ; discuss-
>gnura...@gnu.org
>Betreff: Re: Struggling with 3.10 OOT Module Porting: AttributeError: module
>has no attribute
>
>Hi Luca,
>
>On 09/09/2022 10.58, Bachmaier, Luca wrote:
>> Dear all,
>>
>> I'm currently porting some of my modules from GNU Radio 3.8 to 3.10 and
>experiencing issues with (probably) pybind. My system setup is: Debian 11,
>GNU Radio 3.10.3.0.
>>
>> My flow graphs that include the 3.8 modules are able to compile, but are not
>able to run due to the following error:
>> File "home/user/.grc_gnuradio/myModule_sync.py", line 56 in
>__init__
>> Self.myModule_myblock_0 = myModule.myblock(0, 0)
>> AttributeError: module 'myModule' has no attribute 'myblock'
>
>Open `python/__init__.py`, check if there is `except ImportError:` and replace
>it with `except ModuleNotFoundError:`, then reinstall and try again.
>
>See also https://github.com/gnuradio/gnuradio/issues/3884
>
>Regards,
>Vasil
Installed Gnuradio release 3.9 and see 3.10
Hello GNURadio Community, I installed Ubuntu 22.04 on my computer and then tried to installing Gnuradio 3.9 using PPA installation where I explicitly request for gnuradio-releases-3.9. The Gnuradio version installed is 3.10.1.1. Why am I not getting a Gnuradio version 3.9? Am I missing something? Thanks for any clarifying explanation. George
Re: Installed Gnuradio release 3.9 and see 3.10
On 2022-09-12 13:24, George Edwards wrote: Hello GNURadio Community, I installed Ubuntu 22.04 on my computer and then tried to installing Gnuradio 3.9 using PPA installation where I explicitly request for gnuradio-releases-3.9. The Gnuradio version installed is 3.10.1.1. Why am I not getting a Gnuradio version 3.9? Am I missing something? Thanks for any clarifying explanation. George I"m going to guess that your apt command installed the already-packaged Gnu Radio 3.10 from the official Ubuntu repository, and that either the PPA packages the same version, or you didn't install the PPA properly.
Re: [Discuss-gnuradio] Impulse response in DVB-T, someboby knows how to
Adding two continuous pilot carriers out of phase in time and then applying an IFFT to them from which the frequency domain components could be removed may seem simple but I can't do it. Converting that results in the original time difference, not surprisingly, much less.
Hier-block parameter-propagating possibly mishandled by GRC resulting in source/sink IO size mismatch error
Hi, I have the following major hier-block parameter-passing problem using GRC version 3.8.5.0 (and not an earlier version). Not sure if anyone has experienced this. Scenario I have a hier block that uses as a parameter the input vector length, block_size, the value of which is set in the main flowgraph and is passed into the hier block. When does error occur? Error occurs whenever the value of block_size set in the main flowgraph does not match the value of the corresponding parameter initialized in the hier block. This is not an issue with any of the other parameters passed into the hier block. What is the error? The block following the hier block is expecting an input vector of length block_size as set in the main flowgraph, but the flowgraph error message claims that the hier block is outputting a vector of the size corresponding to the initial/default value set inside the hier block. Therefore, whenever the initial parameter value does not match that set in the top flowgraph, error occurs. Hypothesis The error message generated in GRC may not be a problem due to the failure of the passing of parameters during run-time but the problem of GRC using the initial parameter value defined internally in the hier block when it comes to determining the source/sink I/O size. Thank you for any insights you may provide. Grace -- Grace K. Yeung, MS NorthWest Research Associates 301 Webster Street Monterey, CA 93940 gr...@nwra.com https://www.nwra.com/
