DCO-OFDM for discuss-gnuradio@gnu.org
Hi everyone, I am currently working on the construction of a optical wireless OFDM communication chain from Gnuradio and USRP. I particularly wish to use the DCO-OFDM modulation. Are there people in the community who have already implemented or work on DCO-OFDM with Gnuradio? If so, is it possible to share documentation and/or code links? Thank you in advance Steve JOUMESSI
LimeSDR USB parameter help
I have been trying to help a newbie get a broadcast FM receiver working with a LimeSDR USB. The OS is ubuntu 18.04; gnuradio version is 3.8.0.0 The user has loaded https://github.com/myriadrf/gr-limesdr/blob/master/examples/FM_receiver.grc but it is built for GR 3.7 * should it work for GR 3.8? Right now the Frequency sink just shows random noise. * are there any other working examples for GR 3.8 available? Here is output from the console: LimeSuite Source (RX) info ## LimeSuite version: 19.04.1-ga5b3a10f gr-limesdr version: 3.0.0.0 ## Device list: Nr.:0 device:LimeSDR-USB, media=USB 3.0, module=FX3, addr=1d50:6108, serial=0009081C05C13425 ## INFO: device_handler::enable_channels(): SISO CH0 set for device number 0. INFO: device_handler::set_samp_rate(): set sampling rate: 2 MS/s. INFO: device_handler::set_rf_freq(): RF frequency set [RX]: 88.1 MHz. INFO: device_handler::set_analog_filter(): RX LPF configured INFO: device_handler::set_digital_filter(): digital filter CH0 [RX]: 1.8 MHz. INFO: device_handler::set_gain(): set gain [RX] CH0: 30 dB. INFO: device_handler::set_antenna(): CH0 antenna set [RX]: LNAL. INFO: device_handler::calibrate(): Rx calibration finished On the "Properties: LimeSDR Source (RX)" screen: Channel A Properties: NCO frequency Calibration bandwidth LNA path Analog filter bandwidth Digital filter bandwidth Gain (dB) * What should these parameters be set to? * is the output signal centered at the RF frequency, or is there an offset? on the board there are RX1_L, RX_H, RX_W, RX2_L, RX2_H, RX2_W connectors INFO: device_handler::set_antenna(): CH0 antenna set [RX]: LNAL. * which connector corresponds to LNAL? Is it RX1_L? Any help will be much appreciated! -- Barry Duggan KV4FV
Re: LimeSDR USB parameter help
> * should it work for GR 3.8? > Right now the Frequency sink just shows random noise. I have worked with the LimeSDR on 3.7, but not on 3.8. According to github, work is still in progress to port LimeSuite to 3.8 (https://github.com/myriadrf/gr-limesdr/issues/44) > On the "Properties: LimeSDR Source (RX)" screen: > > Channel A Properties: >NCO frequency The NCO is used a secondary digital mixer to allow you to tune down to below the 30Mhz limit on the LMS7000. Set it to 0 to allow the driver to automatically calculate it for you. >Calibration bandwidth This should be set to at least the sampling rate. It sets the bandwidth across which the LimeSDR calibrates out the LO frequency bleeding into the received signal, if I'm not mistaken. >LNA path This sets the RF input port that is connected to the LMS7000 chip. The LimeSDR has 3 RF inputs per input channel: Low, High and Wideband. >Analog filter bandwidth This is a programmable analogue filter on the RF input. Like the calibration bandwidth, you can set this to 0 to let the driver calculate it for you. >Digital filter bandwidth This is a digital filter present after the NCO digital mixer. Again, set to 0. >Gain (dB) RF input gain - goes from 0-60dB. Probably start with something like 30dB and work from there. > > * is the output signal centered at the RF frequency, or is there an > offset? The output signal should be centred around the RF frequency. > > on the board there are RX1_L, RX_H, RX_W, RX2_L, RX2_H, RX2_W connectors > INFO: device_handler::set_antenna(): CH0 antenna set [RX]: LNAL. > * which connector corresponds to LNAL? Is it RX1_L? If this is the Channel A tab, then LNAL refers to RX1_L. If it's the Channel B tab then LNAL refers to RX2_L.
Re: LimeSDR USB parameter help
Amr: Thank you very much! this is valuable information which I could not find anywhere else. Best regards, --- Barry Duggan KV4FV On 2020-01-24 17:00, Amr Bekhit wrote: * should it work for GR 3.8? Right now the Frequency sink just shows random noise. I have worked with the LimeSDR on 3.7, but not on 3.8. According to github, work is still in progress to port LimeSuite to 3.8 (https://github.com/myriadrf/gr-limesdr/issues/44) On the "Properties: LimeSDR Source (RX)" screen: Channel A Properties: NCO frequency The NCO is used a secondary digital mixer to allow you to tune down to below the 30Mhz limit on the LMS7000. Set it to 0 to allow the driver to automatically calculate it for you. Calibration bandwidth This should be set to at least the sampling rate. It sets the bandwidth across which the LimeSDR calibrates out the LO frequency bleeding into the received signal, if I'm not mistaken. LNA path This sets the RF input port that is connected to the LMS7000 chip. The LimeSDR has 3 RF inputs per input channel: Low, High and Wideband. Analog filter bandwidth This is a programmable analogue filter on the RF input. Like the calibration bandwidth, you can set this to 0 to let the driver calculate it for you. Digital filter bandwidth This is a digital filter present after the NCO digital mixer. Again, set to 0. Gain (dB) RF input gain - goes from 0-60dB. Probably start with something like 30dB and work from there. * is the output signal centered at the RF frequency, or is there an offset? The output signal should be centred around the RF frequency. on the board there are RX1_L, RX_H, RX_W, RX2_L, RX2_H, RX2_W connectors INFO: device_handler::set_antenna(): CH0 antenna set [RX]: LNAL. * which connector corresponds to LNAL? Is it RX1_L? If this is the Channel A tab, then LNAL refers to RX1_L. If it's the Channel B tab then LNAL refers to RX2_L.
Re: GNU Radio 3.8 and Centos 7: Is it possible?
Hi Andrew, Take a look at centos-7.6.Dockerfile[1] that is used by the gnuradio's buildbots[2]. Builds from the master branch currently fail because of some recently merged changes but I just tested build of maint-3.8 branch successfully. Most of the dependencies are installed from the CentOS and EPEL[3] repositories but some are installed by rebuilding source RPMs, from source release tarballs or using pip3. The python version is 3.6 and is installed from the base CentOS repository (python36-devel package) [1] https://github.com/gnuradio/gnuradio-buildbot/blob/public/worker/centos-7.6.Dockerfile [2] https://ci.gnuradio.org/buildbot/#/builders/59 [3] https://fedoraproject.org/wiki/EPEL Regards, Vasil On 21/01/2020 05.15, Andrew J Wolfram wrote: > Hi All, > > Has anyone out there been able to install GNU Radio 3.8 on Centos 7? I have > gotten close compiling from source, but ultimately ran into a segmentation > fault when running gnuradio-companion. The gdb output was not really > helpful. Frame 1 said "Cannot access memory at address 0x170e70>) at > /usr/include/string.h". I'm guessing something is wonky with the library > linking due to the piecemeal dependency resolution I had to do. When > running the cmake command I get a few "Cannot generate a safe runtime > search path for target because files in some directories may conflict with > libraries in implicit directories" errors. Perhaps that's related. I've had > a very difficult time installing dependencies since some of the most recent > versions are not available via yum. I've had luck using Anaconda (conda), > but that's contributed to the linking issues since the old version is > installed somewhere in /usr/ and the newest version is under the Anaconda > prefix. > > I got absolutely nowhere with pybombs. > > Is this a doomed endeavor? > > Thanks, > Andrew >
Re: GNU Radio 3.8 and Centos 7: Is it possible?
This is perfect. Thank you! On Fri, Jan 24, 2020 at 4:22 PM Vasil Velichkov wrote: > Hi Andrew, > > Take a look at centos-7.6.Dockerfile[1] that is used by the gnuradio's > buildbots[2]. Builds from the master branch currently fail because of some > recently merged changes but I just tested build of maint-3.8 branch > successfully. > > Most of the dependencies are installed from the CentOS and EPEL[3] > repositories but some are installed by rebuilding source RPMs, from source > release tarballs or using pip3. The python version is 3.6 and is installed > from the base CentOS repository (python36-devel package) > > [1] > https://github.com/gnuradio/gnuradio-buildbot/blob/public/worker/centos-7.6.Dockerfile > [2] https://ci.gnuradio.org/buildbot/#/builders/59 > [3] https://fedoraproject.org/wiki/EPEL > > Regards, > Vasil > > On 21/01/2020 05.15, Andrew J Wolfram wrote: > > Hi All, > > > > Has anyone out there been able to install GNU Radio 3.8 on Centos 7? I > have > > gotten close compiling from source, but ultimately ran into a > segmentation > > fault when running gnuradio-companion. The gdb output was not really > > helpful. Frame 1 said "Cannot access memory at address 0x170e70>) at > > /usr/include/string.h". I'm guessing something is wonky with the library > > linking due to the piecemeal dependency resolution I had to do. When > > running the cmake command I get a few "Cannot generate a safe runtime > > search path for target because files in some directories may conflict > with > > libraries in implicit directories" errors. Perhaps that's related. I've > had > > a very difficult time installing dependencies since some of the most > recent > > versions are not available via yum. I've had luck using Anaconda (conda), > > but that's contributed to the linking issues since the old version is > > installed somewhere in /usr/ and the newest version is under the Anaconda > > prefix. > > > > I got absolutely nowhere with pybombs. > > > > Is this a doomed endeavor? > > > > Thanks, > > Andrew > > > >
Issues with gnuradio paths and syntax errors
Hello, I'm having some issues using gnuradio with python programs. I am trying to use gnuradio with gr-satellites' python programs to decode packets from CubeSats. When I try to run a python file, I receive the following output *Traceback (most recent call last): File "taurus1_telemetry_parser.py", line 23, in from gnuradio import gr File "/usr/local/lib/python3/dist-packages/gnuradio/gr/__init__.py", line 39, in from .runtime_swig import * File "/usr/local/lib/python3/dist-packages/gnuradio/gr/runtime_swig.py", line 117def value(self) -> "PyObject *":^SyntaxError: invalid syntax* I have read that syntax errors result from different python versions, but I am also wondering if this might be the result of something else. I first tried investigating the syntax error, but when I didn't find anything, I became sucked into the black hole that is my potential issue below. I received the syntax error after editing my bash.rc file to include the path to the python3 library where the gnuradio folder is contained. In the process of investigating the path issue, it appeared that I didn't have all of the path dependencies that people normally do for running gnuradio with python. I'm not sure if this issue and my syntax error are related, so I thought I would inquire on here. The following command is in my bashrc file: *export PYTHONPATH=$PYTHONPATH:/usr/local/lib/python3/dist-packages* as reference, you can see that `/python3/dist-packages` contains gnuradio, along with a few other folders *WorkStation-T5500:/usr/local/lib/python3/dist-packages$ ls gnuradio pmt satellites volk_modtool* In addition, the gnuradio folder contains the following: [image: image.png] However, based on the following references for installing gnuradio, it seems that I am missing the paths to gnuradio/lib and gnuradio/bin. I have not been able to find information that will allow me to fix this. Based on posts that I have read with similar questions as mine, I thought this may be one issue with my setup, but I could also be misinterpreting something. [Ref 1 (Ghithub) ]( https://github.com/gnuberries/raspberry-radio/wiki/GNU-Radio-Installation-Instructions-(for-desktop-or-notebook) ) [Ref 2 (lists.gnu.org)]( https://lists.gnu.org/archive/html/discuss-gnuradio/2016-08/msg00017.html) I installed gnuradio through ppa, as well as pybombs. Do you think the missing paths could be the source of my issue, or are there actually multiple issues here? If so, would it be better to just delete gnuradio entirely and try to install it fresh using pybombs? Thank you for any advice you may have here. I'm still getting used to linux and solving installation issues in general, so please let me know if I can clarify anything further. ~Sarah
