Re: unexplained received power fluctuations with usrp b210 and gnuradio
Hello,
thank you for your answer. In the past few days I've made further tests,
including using a 50 ohm load. I can confirm that it is not visible with a
load, but shows up when connected to an antenna. I was naively thinking that
playing with the analog bandwidth would help, but I guess non linear effects
occur before the bandwidth is set.
I am still a bit puzzled why this behaviour isn't the same wether or not one
uses gr-uhd or the uhd python api, but I will continue to check this,
all the best,
Christophe
> On 20 Apr 2022, at 16:43, Marcus D. Leech wrote:
>
> On 2022-04-20 08:20, Christophe Marqué wrote:
>> Hi,
>>
>> I'm not sure this is the right place to ask this question, but I will try
>> anyway.
>>
>> I am using a usrp b210 to simply record the received power at a certain
>> frequency. The receiver is plugged to a bicone antenna and an amplifier for
>> testing, but the behaviour I describe below has shown up in more elaborated
>> setups. I attach the simple flowgraph. The receiver is tuned with a tune
>> request and an offset equal to half the sample rate.
>>
>> In short, the power I am recording is not stable and I see large excursions
>> (up or down) appearing abruptly, even in frequency bands where I expect no
>> signal (e.g. radio astronomy bands). I know RFI are expected even in quiet
>> bands, but I would not expect drops in the power levels. I see this at
>> different gain settings for the receiver, although a higher gain makes
>> things worse. Without any tune request, it improves a bit but not much.
>>
>> I have made a similar set of measurements using directly the UHD python API,
>> and it seems to me that on comparable timescales, no suspicious fluctuations
>> appear. (see plots, the one of the uhd python api has been integrated by a
>> factor 1000 to get the same rate as the gnuradio generated ones)
>>
>> Has this behavior been seen in the past? I'm using fairly recents uhd and
>> gnuradio libraries (UHD_4.2.0.0, gnuradio 3.10.1), and python 3.8 on a linux
>> (ubuntu 20.4) pc, but I encountered this with older library versions.
>>
>> Thanks for any suggestions,
>>
>> Best regards,
>> Christophe
>>
>> ###Code for the python uhd-api (derived from online example):
>> import uhd
>> import numpy as np
>> import argparse
>>
>> def parse_args():
>> parser = argparse.ArgumentParser()
>> parser.add_argument("-a", "--args", default="", type=str)
>> parser.add_argument("-o", "--output-file", type=str, required=True)
>> parser.add_argument("-f", "--freq", type=float, required=True)
>> parser.add_argument("-r", "--rate", default=1e6, type=float)
>> parser.add_argument("-d", "--duration", default=5.0, type=float)
>> parser.add_argument("-c", "--channels", default=0, nargs="+", type=int)
>> parser.add_argument("-g", "--gain", type=int, default=10)
>> return parser.parse_args()
>>
>> def main():
>> args = parse_args()
>> usrp = uhd.usrp.MultiUSRP(args.args)
>> num_samps = int(np.ceil(args.duration*args.rate))
>> if not isinstance(args.channels, list):
>> args.channels = [args.channels]
>> samps = usrp.recv_num_samps(num_samps, args.freq, args.rate, args.channels,
>> args.gain)
>> with open(args.output_file, 'wb') as f:
>> np.save(f, np.real(samps*np.conj(samps)),
>> allow_pickle=False, fix_imports=False)
>>
>> if __name__ == "__main__":
>> main()
>> ###
> Have you repeated your experiments with a terminator on the input of the
> receiver? I've been using Gnu Radio for radio astronomy applications since
> 2005 or so. The only
> anomaly I've found that was GR-related in this regard was that the
> single-pole IIR filter has some numerical instability for very small inputs.
>
> Also, for a total-power radiometer, I normally just use complex-to-mag**2
> followed by integration and decimation.
>
> In the analog world, you can often get dips in received power due to what
> some call "receiver de-sense" which is caused by a strong out-of-band signal
> exceeding the
> linearity limits of an early gain stage, but since it's out of band, you
> don't see the signal, just the non-linearity effects its causes.
Trying to compile gr-osmosdr on windows
Hello there, I finaly decided to upgrade to GNURadio 3.9 and decided to
build everything from source because precompiled versions outthere didn't
include everything I needed
I knew there would be pain, I just didn't knew how much til I started
tinkering with it
So I a fresh Windows 11 install and installed all the prerequisites for my
build enviroment (to not disturb my precious work computer running windows
7 and gnuradio3.7 install until I make 3.9 work on it)
Visual studio 2019
Python 3.9 x64
Git
Cmake
Perl (to build QT5)
Boost 1.75
CyAPI:(for LimeSDR)
SDRplayAPIv3 (to build gr-sdrplay)
then I started to build all the prerequsites
pthreads (sdr hw libs), libusb (sdr hw libs), zeromq (gr-zeromq), cppzmq
(gr-zeromq)
portaudio (gr-audio), qt5 (gnuradio), qwt (gr-qtgui), faac (gr-drm)
faad2 (gr-drm), cppunit (gnuradio), gsl (gnuradio), libxml2 (libiio)
pybind11 (gnuradio), log4cpp (gnuradio), gmp (gnuradio), libsndfile
(gr-blocks)
I also opted to install some prebuilt stuff (just because it was easier
then to compile them):
zadig (prebuilt executable), boost (prebuilt runtime dlls), fx3 (prebuilt
static libs), swig (prebuilt generator),
fftw (prebuilt runtime dlls), SDL 1.2 (prebuilt runtime dlls), liquiddsp
(prebuilt runtime dlls)
which built fine
then it was hardware build part
## osmo-sdr
## rtl-sdr
## bladerf
## hackrf
## uhd/usrp
## airspy
## airspy-hf+
## mirisdr
## libiio (plutosdr)
## libad9361 (plutosdr)
which also built fine
then after waiting about 10 hours for every prerequisite to eather install
or build it was finaly gnuradio built part
this is what I mean by gnuradio part
## volk
## gnuradio
## gr-osmosdr
## gqrx
## gr-sdrplay3
## volk -- builds fine
## gr-sdrplay3 -- builds fine
even gnuradio builds fine
this is how I built it (incase it matters)
cmake ../ -G "Visual Studio 16 2019" -Wno-dev ^
-DCMAKE_BUILD_TYPE=${CMAKE_BUILD_TYPE} ^
-DCMAKE_INSTALL_PREFIX=${CMAKE_INSTALL_PREFIX} ^
-DLOG4CPP_INCLUDE_DIR=${CMAKE_INSTALL_PREFIX}/include ^
-DLOG4CPP_LIBRARY=${CMAKE_INSTALL_PREFIX}/lib/log4cpp.lib ^
-DMPIR_INCLUDE_DIR=${MPIR_INCLUDE_DIR} ^
-DMPIR_LIBRARY=${MPIR_LIBRARY} ^
-DMPIRXX_LIBRARY=${MPIRXX_LIBRARY} ^
-DENABLE_INTERNAL_VOLK=OFF ^
-DBOOST_ROOT=${BOOST_ROOT} ^
-DBOOST_LIBRARYDIR=${BOOST_LIBRARYDIR} ^
-DBOOST_ALL_DYN_LINK=TRUE ^
-DPYTHON_EXECUTABLE=${PYTHON3_EXECUTABLE} ^
-DPYTHON_INCLUDE_DIR=${PYTHON3_INCLUDE_DIR} ^
-DPYTHON_LIBRARY=${PYTHON3_LIBRARY} ^
-DGR_PYTHON_DIR=${PYTHON3_INSTALL_DIR} ^
-DFFTW3f_INCLUDE_DIRS=${FFTW3F_INCLUDE_DIRS} ^
-DFFTW3f_LIBRARIES=${FFTW3F_LIBRARIES} ^
-DUHD_INCLUDE_DIRS=${UHD_INCLUDE_DIRS} ^
-DUHD_LIBRARIES=${UHD_LIBRARIES} ^
-DENABLE_TESTING=ON ^
-DCPPUNIT_INCLUDE_DIRS=${CPPUNIT_INCLUDE_DIRS} ^
-DCPPUNIT_LIBRARIES=${CPPUNIT_LIBRARIES} ^
-DENABLE_PYTHON=ON ^
-DPORTAUDIO_INCLUDE_DIRS=${PORTAUDIO_INCLUDE_DIR} ^
-DPORTAUDIO_LIBRARIES=${PORTAUDIO_LIBRARY} ^
-DZEROMQ_INCLUDE_DIRS=${ZEROMQ_INCLUDE_DIRS} ^
-DZEROMQ_LIBRARIES=${ZEROMQ_LIBRARIES} ^
-DGSL_INCLUDE_DIRS=${GSL_INCLUDE_DIRS} ^
-DGSL_LIBRARY=${GSL_LIBRARY} ^
-DGSL_CBLAS_LIBRARY=${GSL_CBLAS_LIBRARY} ^
-DENABLE_GR_QTGUI=ON ^
-DCMAKE_PREFIX_PATH=${QT5_ROOT} ^
-DQWT_INCLUDE_DIRS=${QWT_INCLUDE_DIR} ^
-DQWT_LIBRARIES=${QWT_LIBRARY} ^
-DENABLE_GRC=ON
I hope this this variables don't confuse anyone, but they are properly set
on my system
this gnuradio build-process is also part of a larger script because
building this by hand would probably take more then 12hours (it already
took to this point) (as you would have to be physically present instead of
ordering a computer to do it while you do something else, also
"^" does the same thing on windows as does "\" on linux (it allows you to
split command to multiple lines if anyone wonders why there is "^" at the
end of every line instead of more usual "\")
this was all going great, but then it was GROsmoSDR part
I clone master branch off their git: git://git.osmocom.org/gr-osmosdr
started to build
cmake ../ -G "Visual Studio 16 2019" ^
-Wno-dev
-DCMAKE_BUILD_TYPE=${CMAKE_BUILD_TYPE} ^
-DCMAKE_INSTALL_PREFIX=${CMAKE_INSTALL_PREFIX} ^
-DLOG4CPP_INCLUDE_DIR=${CMAKE_INSTALL_PREFIX}/include ^
-DLOG4CPP_LIBRARY=${CMAKE_INSTALL_PREFIX}/lib/log4cpp.lib ^
-DMPIR_INCLUDE_DIR=${MPIR_INCLUDE_DIR} ^
-DMPIR_LIBRARY=${MPIR_LIBRARY} ^
-DMPIRXX_LIBRARY=${MPIRXX_LIBRARY} ^
-DFFTW3f_INCLUDE_DIRS=${FFTW3F_INCLUDE_DIRS} ^
-DFFTW3f_LIBRARIES=${FFTW3F_LIBRARIES} ^
-DUHD_INCLUDE_DIRS=${UHD_INCLUDE_DIRS} ^
-DUHD_LIBRARIES=${UHD_LIBRARIES} ^
-DBOOST_ROOT=${BOOST_ROOT} ^
-DBOOST_LIBRARYDIR=${BOOST_LIBRARYDIR} ^
-DBOOST_ALL_DYN_LINK=TRUE ^
-DPYTHON_EXECUTABLE=${PYTHON3_EXECUTABLE} ^
Re: Trying to compile gr-osmosdr on windows
Hi Mitja,
On 4/26/22 11:52 AM, Mitja kocjančič wrote:
Hello there, I finaly decided to upgrade to GNURadio 3.9 and decided to
build everything from source because precompiled versions outthere
didn't include everything I needed
I knew there would be pain, I just didn't knew how much til I started
tinkering with it
I commend the effort, and now that you know the pain I hope to convert
you to the conda way of life :)
...
even gnuradio builds fine
this is how I built it (incase it matters)
cmake ../ -G "Visual Studio 16 2019" -Wno-dev ^
-DCMAKE_BUILD_TYPE=${CMAKE_BUILD_TYPE} ^
-DCMAKE_INSTALL_PREFIX=${CMAKE_INSTALL_PREFIX} ^
-DLOG4CPP_INCLUDE_DIR=${CMAKE_INSTALL_PREFIX}/include ^
-DLOG4CPP_LIBRARY=${CMAKE_INSTALL_PREFIX}/lib/log4cpp.lib ^
-DMPIR_INCLUDE_DIR=${MPIR_INCLUDE_DIR} ^
-DMPIR_LIBRARY=${MPIR_LIBRARY} ^
-DMPIRXX_LIBRARY=${MPIRXX_LIBRARY} ^
-DENABLE_INTERNAL_VOLK=OFF ^
-DBOOST_ROOT=${BOOST_ROOT} ^
-DBOOST_LIBRARYDIR=${BOOST_LIBRARYDIR} ^
-DBOOST_ALL_DYN_LINK=TRUE ^
-DPYTHON_EXECUTABLE=${PYTHON3_EXECUTABLE} ^
-DPYTHON_INCLUDE_DIR=${PYTHON3_INCLUDE_DIR} ^
-DPYTHON_LIBRARY=${PYTHON3_LIBRARY} ^
-DGR_PYTHON_DIR=${PYTHON3_INSTALL_DIR} ^
-DFFTW3f_INCLUDE_DIRS=${FFTW3F_INCLUDE_DIRS} ^
-DFFTW3f_LIBRARIES=${FFTW3F_LIBRARIES} ^
-DUHD_INCLUDE_DIRS=${UHD_INCLUDE_DIRS} ^
-DUHD_LIBRARIES=${UHD_LIBRARIES} ^
-DENABLE_TESTING=ON ^
-DCPPUNIT_INCLUDE_DIRS=${CPPUNIT_INCLUDE_DIRS} ^
-DCPPUNIT_LIBRARIES=${CPPUNIT_LIBRARIES} ^
-DENABLE_PYTHON=ON ^
-DPORTAUDIO_INCLUDE_DIRS=${PORTAUDIO_INCLUDE_DIR} ^
-DPORTAUDIO_LIBRARIES=${PORTAUDIO_LIBRARY} ^
-DZEROMQ_INCLUDE_DIRS=${ZEROMQ_INCLUDE_DIRS} ^
-DZEROMQ_LIBRARIES=${ZEROMQ_LIBRARIES} ^
-DGSL_INCLUDE_DIRS=${GSL_INCLUDE_DIRS} ^
-DGSL_LIBRARY=${GSL_LIBRARY} ^
-DGSL_CBLAS_LIBRARY=${GSL_CBLAS_LIBRARY} ^
-DENABLE_GR_QTGUI=ON ^
-DCMAKE_PREFIX_PATH=${QT5_ROOT} ^
-DQWT_INCLUDE_DIRS=${QWT_INCLUDE_DIR} ^
-DQWT_LIBRARIES=${QWT_LIBRARY} ^
-DENABLE_GRC=ON
What might be helpful is if you could note the components that are
enabled/disabled after running CMake for GNU Radio.
this was all going great, but then it was GROsmoSDR part
I clone master branch off their git: git://git.osmocom.org/gr-osmosdr
started to build
cmake ../ -G "Visual Studio 16 2019" ^
-Wno-dev
-DCMAKE_BUILD_TYPE=${CMAKE_BUILD_TYPE} ^
-DCMAKE_INSTALL_PREFIX=${CMAKE_INSTALL_PREFIX} ^
-DLOG4CPP_INCLUDE_DIR=${CMAKE_INSTALL_PREFIX}/include ^
-DLOG4CPP_LIBRARY=${CMAKE_INSTALL_PREFIX}/lib/log4cpp.lib ^
-DMPIR_INCLUDE_DIR=${MPIR_INCLUDE_DIR} ^
-DMPIR_LIBRARY=${MPIR_LIBRARY} ^
-DMPIRXX_LIBRARY=${MPIRXX_LIBRARY} ^
-DFFTW3f_INCLUDE_DIRS=${FFTW3F_INCLUDE_DIRS} ^
-DFFTW3f_LIBRARIES=${FFTW3F_LIBRARIES} ^
-DUHD_INCLUDE_DIRS=${UHD_INCLUDE_DIRS} ^
-DUHD_LIBRARIES=${UHD_LIBRARIES} ^
-DBOOST_ROOT=${BOOST_ROOT} ^
-DBOOST_LIBRARYDIR=${BOOST_LIBRARYDIR} ^
-DBOOST_ALL_DYN_LINK=TRUE ^
-DPYTHON_EXECUTABLE=${PYTHON3_EXECUTABLE} ^
-DPYTHON_INCLUDE_DIR=${PYTHON3_INCLUDE_DIR} ^
-DPYTHON_LIBRARY=${PYTHON3_LIBRARY} ^
-DGR_PYTHON_DIR=${PYTHON3_INSTALL_DIR} ^
-DENABLE_RFSPACE=OFF ^
-DENABLE_REDPITAYA=OFF
BTW: -DCMAKE_BUILD_TYPE=RelWithDebInfo
and then it went donwhill :(
that's what the error looks like:
https://user-images.githubusercontent.com/6347325/161424913-e10c0ee7-8901-49e4-a093-b34c39e68053.png
it seams it wants BindingGenerator from GNURadio.bindtool
but I checked there is nothing like that anywhere on my system (I
checked where gr python binding normaly reside
CMAKE_INSTALL_PREFIX\lib\python3.9\site-packages\gnuradio\gr
CMAKE_INSTALL_PREFIX can be different for everyone in my case its
C:\GnuRadio
now What is GNURadio.bindtool and where can I find it?
It's a component of the gr-utils portion of the main GNU Radio build, so
I'd suggest checking to see that you built that (seems not). I think it
would be easy to miss a dependency here and not end up with the bindtool.
That said, I'm not entirely sure why the build is trying to run
bind_oot_file.py as that is more of a developer activity and I don't
think it's something that happens in my builds. I do know that I don't
install pygccxml, and perhaps if you do have that dependency available
then it might be triggering this when I wouldn't see it.
It seams people managed to build GROsmoSDR on windows with GNURadio 3.9
awhile ago: https://osmocom.org/issues/5021
because there is GRCon
Re: Trying to compile gr-osmosdr on windows
Thanks for hinting to gr-utils
I am one step closer now (I missed gr-utils, gr-modtool (click,
click-plugins), gr-filter (scipy was missing) and gr-video-sdl (SDL 1.2 was
missing),
I also found some missing dependencies that I had to enable like this
-DENABLE_GRC=ON
-DENABLE_GR_UTILS=ON
-DENABLE_GR_VIDEO_SDL=ON
-DENABLE_GR_MODTOOL=ON
now gr-utils is built, but for some reson GROsmoSDR still wants to invoke
it (its failing to invoke it now, but it does try):
https://user-images.githubusercontent.com/6347325/165409049-73253f38-c5f2-40c1-923e-a06df46e5f33.png
I also tried to delete pygccxml but it made no diference
maybe the problem might be that you are building with
DCMAKE_BUILD_TYPE=Release
while I am building with DCMAKE_BUILD_TYPE=RelWithDebInfo
and the thing wants to invoke something different, idk
BTW: if I go with 0.2.3, tag of GROsmoSDR how should I go about applying
your patches (is there a tool that would take a patch and apply it
automaticly, because I don't want to patch this by hand because then it
would surely take another month or 2 for me to patch this manualy :)
Now I guess I need to figure out why does GROsmoSDR invoke bind_oot_file.py
BTW: I am trying to use PothosSDR build enviroment (without pothos, since
SoapySDR doesn't want to built and I don't need it if I have OsmoSDR)
(since it served me well in 3.7 days (without it I would never be able to
use GNURadio on windows in early days (back when I got my hackRF you could
only run GNURadio on linux and for some reason it had to be physycal linux
machine since it didn't work in VM) and here is my modified
BuildGNURadio.cmake script:
https://github.com/veso266/PothosSDR/blob/master/BuildGNURadio.cmake
V V tor., 26. apr. 2022 ob 19:59 je oseba Ryan Volz
napisala:
> Hi Mitja,
>
> On 4/26/22 11:52 AM, Mitja kocjančič wrote:
> > Hello there, I finaly decided to upgrade to GNURadio 3.9 and decided to
> > build everything from source because precompiled versions outthere
> > didn't include everything I needed
> >
> > I knew there would be pain, I just didn't knew how much til I started
> > tinkering with it
>
> I commend the effort, and now that you know the pain I hope to convert
> you to the conda way of life :)
>
> >
> > ...
> >
> > even gnuradio builds fine
> > this is how I built it (incase it matters)
> >
> > cmake ../ -G "Visual Studio 16 2019" -Wno-dev ^
> > -DCMAKE_BUILD_TYPE=${CMAKE_BUILD_TYPE} ^
> > -DCMAKE_INSTALL_PREFIX=${CMAKE_INSTALL_PREFIX} ^
> > -DLOG4CPP_INCLUDE_DIR=${CMAKE_INSTALL_PREFIX}/include ^
> > -DLOG4CPP_LIBRARY=${CMAKE_INSTALL_PREFIX}/lib/log4cpp.lib ^
> > -DMPIR_INCLUDE_DIR=${MPIR_INCLUDE_DIR} ^
> > -DMPIR_LIBRARY=${MPIR_LIBRARY} ^
> > -DMPIRXX_LIBRARY=${MPIRXX_LIBRARY} ^
> > -DENABLE_INTERNAL_VOLK=OFF ^
> > -DBOOST_ROOT=${BOOST_ROOT} ^
> > -DBOOST_LIBRARYDIR=${BOOST_LIBRARYDIR} ^
> > -DBOOST_ALL_DYN_LINK=TRUE ^
> > -DPYTHON_EXECUTABLE=${PYTHON3_EXECUTABLE} ^
> > -DPYTHON_INCLUDE_DIR=${PYTHON3_INCLUDE_DIR} ^
> > -DPYTHON_LIBRARY=${PYTHON3_LIBRARY} ^
> > -DGR_PYTHON_DIR=${PYTHON3_INSTALL_DIR} ^
> > -DFFTW3f_INCLUDE_DIRS=${FFTW3F_INCLUDE_DIRS} ^
> > -DFFTW3f_LIBRARIES=${FFTW3F_LIBRARIES} ^
> > -DUHD_INCLUDE_DIRS=${UHD_INCLUDE_DIRS} ^
> > -DUHD_LIBRARIES=${UHD_LIBRARIES} ^
> > -DENABLE_TESTING=ON ^
> > -DCPPUNIT_INCLUDE_DIRS=${CPPUNIT_INCLUDE_DIRS} ^
> > -DCPPUNIT_LIBRARIES=${CPPUNIT_LIBRARIES} ^
> > -DENABLE_PYTHON=ON ^
> > -DPORTAUDIO_INCLUDE_DIRS=${PORTAUDIO_INCLUDE_DIR} ^
> > -DPORTAUDIO_LIBRARIES=${PORTAUDIO_LIBRARY} ^
> > -DZEROMQ_INCLUDE_DIRS=${ZEROMQ_INCLUDE_DIRS} ^
> > -DZEROMQ_LIBRARIES=${ZEROMQ_LIBRARIES} ^
> > -DGSL_INCLUDE_DIRS=${GSL_INCLUDE_DIRS} ^
> > -DGSL_LIBRARY=${GSL_LIBRARY} ^
> > -DGSL_CBLAS_LIBRARY=${GSL_CBLAS_LIBRARY} ^
> > -DENABLE_GR_QTGUI=ON ^
> > -DCMAKE_PREFIX_PATH=${QT5_ROOT} ^
> > -DQWT_INCLUDE_DIRS=${QWT_INCLUDE_DIR} ^
> > -DQWT_LIBRARIES=${QWT_LIBRARY} ^
> > -DENABLE_GRC=ON
> >
>
> What might be helpful is if you could note the components that are
> enabled/disabled after running CMake for GNU Radio.
>
> >
> > this was all going great, but then it was GROsmoSDR part
> > I clone master branch off their git: git://git.osmocom.org/gr-osmosdr
> >
> >
> > started to build
> > cmake ../ -G "Visual Studio 16 2019" ^
> > -Wno-dev
> > -DCMAKE_BUILD_TYPE=${CMAKE_BUILD_TYPE} ^
> > -DCMAKE_INSTALL_PREFIX=${CMAKE_INSTALL_PREFIX} ^
> > -DLOG4CPP_INCLUDE_DIR=${CMAKE_INSTALL_PREFIX}/include ^
> > -DLOG4CPP_LIBRARY=${CMAKE_INSTALL_PREFIX}/lib/log4cpp.lib ^
> > -DMPIR_INCLUDE_DIR=${MPIR_INCLUDE_DIR} ^
> > -DMPIR_LIBRARY=${MPIR_LIBRARY} ^
> > -DMPIRXX_LIBRARY=${MPIRXX_LIBRARY
