Send USRP-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of USRP-users digest..."
Today's Topics:
1. Re: Trouble building gr-ettus (using custom install prefix,
and (rfnoc-)radio-redo) (Collins, Richard)
2. Re: Trouble building gr-ettus (using custom install prefix,
and (rfnoc-)radio-redo) (Marcus M?ller)
3. Re: Trouble building gr-ettus (using custom install prefix,
and (rfnoc-)radio-redo) (Martin Braun)
4. Tune request with frequency Offset (LEMENAGER Claude)
5. Re: Tune request with frequency Offset (Dave NotTelling)
6. Re: Tune request with frequency Offset (LEMENAGER Claude)
7. Octoclock updating firmware & change ip (Pol Henarejos)
8. E310 firmware downgrade (Mike Williams)
9. Re: E310 firmware downgrade (Philip Balister)
----------------------------------------------------------------------
Message: 1
Date: Tue, 31 May 2016 12:02:03 -0400
From: "Collins, Richard" <[email protected]>
To: Marcus M?ller <[email protected]>,
[email protected]
Subject: Re: [USRP-users] Trouble building gr-ettus (using custom
install prefix, and (rfnoc-)radio-redo)
Message-ID:
<cabgq8cacwukwfrvtqn5wiugvzdkysnmc8u2t+jpk35ygmqt...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hello Marcus,
I followed that install order, all-the-while blindly assuming the
PKG_CONFIG_PATH, LD_LIBRARY_PATH, and PYTHONPATH would be taken care of by
the cmake switch -DCMAKE_INSTALL_PREFIX.
My system is Ubuntu 16.04 (x86-64, kernel 4.4.0-22-generic, "Server"
version), and it seems the majority of .pc files live in the pkgconfig
folder, */usr/lib/x86_64-linux-gnu/pkgconfig/*, and UHD and GNURadio
pkgconfig files ended up in */opt/gnuradio-rfnoc/lib64/pkgconfig/ *(including
*uhd.pc*).
The custom environment file that I source before trying to load/run any
uhd_{anything} or gnuradio-companion may be a bit different since I last
reported it. It is as follows:
BASE=/opt/gnuradio-rfnoc
export PATH=${PATH}:${BASE}/bin
export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${BASE}/lib64
export PKG_CONFIG_PATH${PKG_CONFIG_PATH}:${BASE}/lib64/pkgconfig
export PYTHONPATH=${PYTHONPATH}:${BASE}/lib/python2.7/dist-packages/
All those directories have things in them that both UHD and GNURadio
installed into them (except for the PYTHONPATH, which only has GNURadio
things in it). Nothing that starts with "uhd_" or "gnur" is accessible
until I source that file, so I assume the (bin) PATH assignment is correct.
I assume the PKG_CONFIG_PATH is correct because it contains the only uhd.pc
on the system except for the uhd source build directory (where I ran cmake,
make, etc.). I'm not sure about LD_LIBRARY_PATH, but it seems to have all
the things that would go into /usr/local/lib during a standard install
(except for libthrift ..., which I think I might have I chosen to not
install).
My notes indicate that the last time I used PyBOMBS was in early February,
less than two weeks after the official switch from the old Pybombs to
Pybombs2. I had enough trouble with it that I found it easier to install
UHD and GNURadio (granted, in the default directories) and all dependencies
by hand. I bet, by now, it's a bit more user friendly and would be a good
place to start for using a custom directory. I probably shouldn't be trying
all this by hand without understanding CMake.
Thanks for taking the to explain a bit of what's going on. I hope this
helps to explain my current configuration, though I'm still not too sure
why gr-ettus can't find FindUHD.cmake (which exists in
/opt/gnuradio-rfnoc/lib64/cmake/gnuradio/, with /opt/gnuradio-rfnoc/lib64
being my "LD_LIBRARY_PATH" which is exported when I try to build gr-ettus).
I wonder if it's because I used "-DLIB_SUFFIX=64" when building UHD, but
again, I probably don't know enough about cmake, compilers, or C++ in
general.
Also, it might be good to mention that when I run "uhd_usrp_probe
--init-only", I get the following output:
*linux; GNU C++ version 5.3.1 20160413; Bost_105800;
UHD_003.010.rfnoc-471-g37ffaef2*
which seems to indicate that I do have an RFNOC version of UHD built and
installed.
Thanks,
Richard
On Sat, May 28, 2016 at 4:09 AM, Marcus M?ller <[email protected]>
wrote:
> Hi Richard,
>
> I'll address both issues one after the other. First the "not finding UHD"
> issue:
>
> to be honest, I'd rather not change the CMake scripts if avoidable;
> instead, we should teach the build system too look for your things in
> opt/gnuradio-rfnoc!
> So, CMake asks pkg-config where UHD is installed. pkg-config has a default
> directory (for my distro, it's /usr/lib64/pkgconfig, but this might be
> different for yours) where it looks for .pc files that contain info on how
> to include headers and link against libraries.
>
> Now, my assumption is that you built your UHD in a manner that did not put
> its .pc where pkg-config can find them (makes sense). Look into your
> installation prefix: is there a lib/pkgconfig/ directory somewhere that
> contains an uhd.pc file? If so:
>
> you will need to inform pkg-config to look into that directory. That's
> easy, just
>
> export PKG_CONFIG_PATH=/path/to/the/uhd.pc:$PKG_CONFIG_PATH
>
> It's also important to make sure the UHD that you find this way is the
> first UHD your compiler and linker use. Otherwise, it might use another
> installation of UHD, and as it seems, that doesn't have RFNoC. Also, the
> build and installation order MUST be:
>
> 1. UHD (with RFNoC) build & install
> 2. GNU Radio (which by itself is RFNoC-agnostic, but needs to link
> against the right UHD) build & install
> 3. gr-ettus (which depends on both GNU Radio and RFNoC'ed UHD) build &
> install
>
> So, you'd do about the same you did for PKG_CONFIG_PATH with
> LD_LIBRARY_PATH for the directory containing the freshly built libuhd.so.
> Then there's the issue of Python needing to find the GNU Radio packages, so
> you'll need to fix PYTHONPATH, too (but I'll cover that as soon as you've
> come as far as being able to find the right UHD with RFNoC).
>
> Frankly, doing this non-default prefix install by hand is a bit complex,
> especially, if you haven't done this a couple of times before. That's
> really really the purpose of PyBOMBS, to install libraries and software
> into a non-system prefix, and giving you a readily written script that you
> can source with your shell, giving you full access to what is installed to
> that prefix. So, in an attempt to conserve as much of your sanity as
> possible: What Linux distribution are you using? Many popular ones are
> fully covered by pybombs, and it's easy to make pybombs install UHD with
> RFNoC, GNU Radio and gr-ettus
>
> Best regards,
> Marcus
>
>
> On 28.05.2016 01:41, Collins, Richard via USRP-users wrote:
>
> Hello,
>
> The quick and dirty:
>
> I'm trying to build gr-ettus but I get an error that UHDConfig.cmake can't
> be found, as seen in [1]. It was suggested in the #gnuradio Freenode irc
> chatroom to "modify the paths in it to [my] local installation", and that I
> might need to put it in gr-ettus.
>
> So I modified it as can be seen in [2], and moved it like this:
> <user>@<machine>:/opt/src/gr-ettus/build$ cp
> ../../gnuradio-rfnoc/cmake/Modules/FindUHD.cmake ../cmake/Modules/
>
> After running cmake again, I get the error that can be seen in [3] that
> says "RFNoC not found."
>
> --------
> The longer explanation:
>
> It may be good to know that I originally thought the problem [1] was due
> to my installing UHD and GNURadio into separate directories.
>
> First, i used build-gnuradio script to install dependencies (since that
> script now seems to work for ubuntu16.04) and then
> created/chown'ed/chgrp'ed destination folders in /opt/. I then git cloned
> the projects and ran cmake for uhd (first) and gnuradio (second) before
> running "make", "make test", "make install", and "sudo ldconfig", but
> targeted to /opt/uhd-rfnoc and /opt/gnuradio-rfnoc, respectively.
>
> Since ending up with this error [1], I uninstalled them in the reverse
> order (gnuradio first, then uhd) with the following commands from each's
> build directory:
> make uninstall
> git clean -d -x -f
> sudo ldconfig
>
> I then re-installed both using the following commands (now both targeted
> to /opt/gnuradio-rfnoc/), and tried (again) to get gr-ettus working before
> getting* the same exact error in [1].*
>
> UHD:
> git clone --recursive git://github.com/EttusResearch/uhd.git uhd-rfnoc
> cd uhd-rfnoc
> git checkout -b *rfnoc-radio-redo* -t origin/rfnoc-radio-redo
> mkdir host/build && cd host/build
> *cmake -DCMAKE_INSTALL_PREFIX=/opt/gnuradio-rfnoc/ -DENABLE_X300=ON
> -DENABLE_E300=ON -DENABLE_B200=OFF -DLIB_SUFFIX=64 -Wno-dev ../*
> make -j8 && make test && make install && sudo ldconfig
>
> GNURadio:
> git clone --recursive <https://github.com/gnuradio/gnuradio.git>
> https://github.com/gnuradio/gnuradio.git gnuradio-rfnoc
> cd gnuradio-rfnoc
> git checkout *maint*
> *cmake -DCMAKE_INSTALL_PREFIX=/opt/**gnuradio-rfnoc/ -DLIB_SUFFIX=64
> -DENABLE_GR_COMEDI=OFF -Wno-dev ../*
> make -j8 && make test && make install && sudo ldconfig
>
> gr-ettus:
> git clone <https://github.com/EttusResearch/gr-ettus.git>
> https://github.com/EttusResearch/gr-ettus.git
> cd gr-ettus
> git checkout
> *radio-redo *mkdir build && cd build
> * cmake -DCMAKE_INSTALL_PREFIX=/opt/**gnuradio-rfnoc/ Wno-dev ../*
> # (tried with and without the -DLIB_SUFFIX=64)
> # Again, in case it wasn't clear, error [1] happened again right here.
>
> Installing into a separate directory is important to me for the sake of
> not having to reinstall the operating system if I want to uninstall a
> version of UHD or switch between versions of UHD/GNURadio. (Also, "make
> uninstall" doesn't seem to work cleanly, or i did some command out of order
> almost a year ago on my laptop, and am perpetually stuck with an rfnoc
> version of uhd being detected no matter what I do.)
>
> It's been suggested to use rfnoc-radio-redo instead of rfnoc-devel, and to
> use Vivado 15.04 instead of 14.04, so I hope that's correct. I haven't seen
> the "radio-redo" version of gr-ettus mentioned, but i figured it should
> match.
>
> Any advice on where to go from here would be appreciated. Although, I'm
> pondering blowing it all away and reverting to an old image of the hard
> drives before installing UHD and GNURadio, just this time not using custom
> directories, and maybe not worrying about a "LIB_SUFFIX".
>
> --------
>
> [1]: http://pastebin.com/1cfVuu35
> [2]: http://pastebin.com/8XaAcBiZ
> [3]: http://pastebin.com/FDZyQY4y
> [4]: http://pastebin.com/31yJjUNu
>
>
> Thanks,
>
> Richard
>
>
> _______________________________________________
> USRP-users mailing
> [email protected]http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
>
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20160531/77718506/attachment-0001.html>
------------------------------
Message: 2
Date: Tue, 31 May 2016 21:34:34 +0200
From: Marcus M?ller <[email protected]>
To: "Collins, Richard" <[email protected]>,
[email protected]
Subject: Re: [USRP-users] Trouble building gr-ettus (using custom
install prefix, and (rfnoc-)radio-redo)
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
Hi Richard,
On 31.05.2016 18:02, Collins, Richard wrote:
> Hello Marcus,
>
> I followed that install order, all-the-while blindly assuming the
> PKG_CONFIG_PATH, LD_LIBRARY_PATH, and PYTHONPATH would be taken care
> of by the cmake switch -DCMAKE_INSTALL_PREFIX.
That's sadly not the case ? that really only sets the installation
/destination/.
>
> My system is Ubuntu 16.04 (x86-64, kernel 4.4.0-22-generic, "Server"
> version), and it seems the majority of .pc files live in the pkgconfig
> folder, */usr/lib/x86_64-linux-gnu/pkgconfig/*, and UHD and GNURadio
> pkgconfig files ended up in */opt/gnuradio-rfnoc/lib64/pkgconfig/
> *(including *uhd.pc*).
>
> The custom environment file that I source before trying to load/run
> any uhd_{anything} or gnuradio-companion may be a bit different since
> I last reported it. It is as follows:
>
> BASE=/opt/gnuradio-rfnoc
>
> export PATH=${PATH}:${BASE}/bin
>
> export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${BASE}/lib64
>
> export PKG_CONFIG_PATH${PKG_CONFIG_PATH}:${BASE}/lib64/pkgconfig
>
> export PYTHONPATH=${PYTHONPATH}:${BASE}/lib/python2.7/dist-packages/
>
>
> All those directories have things in them that both UHD and GNURadio
> installed into them (except for the PYTHONPATH, which only has
> GNURadio things in it). Nothing that starts with "uhd_" or "gnur" is
> accessible until I source that file, so I assume the (bin) PATH
> assignment is correct.
Yep, good work!
> I assume the PKG_CONFIG_PATH is correct because it contains the only
> uhd.pc on the system except for the uhd source build directory (where
> I ran cmake, make, etc.).
Test with pkg-config itself. For example,
pkg-config --libs uhd
and
pkg-config --cflags gnuradio-runtime
should return sensible linker/compiler options.
> I'm not sure about LD_LIBRARY_PATH, but it seems to have all the
> things that would go into /usr/local/lib during a standard install
> (except for libthrift ..., which I think I might have I chosen to not
> install).
>
> My notes indicate that the last time I used PyBOMBS was in early
> February, less than two weeks after the official switch from the old
> Pybombs to Pybombs2. I had enough trouble with it that I found it
> easier to install UHD and GNURadio (granted, in the default
> directories) and all dependencies by hand.
Yeah, the start of things that need to adapt to a variety of platforms
is usually a bit rough ? Pybombs2 was no exception.
> I bet, by now, it's a bit more user friendly and would be a good place
> to start for using a custom directory. I probably shouldn't be trying
> all this by hand without understanding CMake.
>
> Thanks for taking the to explain a bit of what's going on. I hope this
> helps to explain my current configuration, though I'm still not too
> sure why gr-ettus can't find FindUHD.cmake (which exists in
> /opt/gnuradio-rfnoc/lib64/cmake/gnuradio/, with
> /opt/gnuradio-rfnoc/lib64 being my "LD_LIBRARY_PATH" which is exported
> when I try to build gr-ettus). I wonder if it's because I used
> "-DLIB_SUFFIX=64" when building UHD, but again, I probably don't know
> enough about cmake, compilers, or C++ in general.
Hm, it's possible cmake is really expecting some hint where to look for
Cmake scripts ? I must admit I don't know whether such an environment
variable exists, or so. Maybe someone else has an idea!
>
> Also, it might be good to mention that when I run "uhd_usrp_probe
> --init-only", I get the following output:
>
> *linux; GNU C++ version 5.3.1 20160413; Bost_105800;
> UHD_003.010.rfnoc-471-g37ffaef2*
>
> which seems to indicate that I do have an RFNOC version of UHD built
> and installed.
That's great :)
Best regards,
Marcus
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20160531/4b2608e4/attachment-0001.html>
------------------------------
Message: 3
Date: Tue, 31 May 2016 18:25:57 -0400
From: Martin Braun <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] Trouble building gr-ettus (using custom
install prefix, and (rfnoc-)radio-redo)
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252
For the E310, you can set up the entire environment (including SDK)
using PyBOMBS:
$ pybombs recipes add ettus
https://github.com/EttusResearch/ettus-pybombs.git
$ pybombs prefix init -R e3xx-radio-redo
I'll add another recipe for vanilla X-Series installation.
M
On 05/31/2016 03:34 PM, Marcus M?ller via USRP-users wrote:
> Hi Richard,
>
> On 31.05.2016 18:02, Collins, Richard wrote:
>> Hello Marcus,
>>
>> I followed that install order, all-the-while blindly assuming the
>> PKG_CONFIG_PATH, LD_LIBRARY_PATH, and PYTHONPATH would be taken care
>> of by the cmake switch -DCMAKE_INSTALL_PREFIX.
> That's sadly not the case ? that really only sets the installation
> /destination/.
>>
>> My system is Ubuntu 16.04 (x86-64, kernel 4.4.0-22-generic, "Server"
>> version), and it seems the majority of .pc files live in the pkgconfig
>> folder, */usr/lib/x86_64-linux-gnu/pkgconfig/*, and UHD and GNURadio
>> pkgconfig files ended up in */opt/gnuradio-rfnoc/lib64/pkgconfig/
>> *(including *uhd.pc*).
>>
>> The custom environment file that I source before trying to load/run
>> any uhd_{anything} or gnuradio-companion may be a bit different since
>> I last reported it. It is as follows:
>>
>> BASE=/opt/gnuradio-rfnoc
>>
>> export PATH=${PATH}:${BASE}/bin
>>
>> export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${BASE}/lib64
>>
>> export PKG_CONFIG_PATH${PKG_CONFIG_PATH}:${BASE}/lib64/pkgconfig
>>
>> export PYTHONPATH=${PYTHONPATH}:${BASE}/lib/python2.7/dist-packages/
>>
>>
>> All those directories have things in them that both UHD and GNURadio
>> installed into them (except for the PYTHONPATH, which only has
>> GNURadio things in it). Nothing that starts with "uhd_" or "gnur" is
>> accessible until I source that file, so I assume the (bin) PATH
>> assignment is correct.
> Yep, good work!
>> I assume the PKG_CONFIG_PATH is correct because it contains the only
>> uhd.pc on the system except for the uhd source build directory (where
>> I ran cmake, make, etc.).
> Test with pkg-config itself. For example,
>
> pkg-config --libs uhd
> and
> pkg-config --cflags gnuradio-runtime
>
> should return sensible linker/compiler options.
>
>> I'm not sure about LD_LIBRARY_PATH, but it seems to have all the
>> things that would go into /usr/local/lib during a standard install
>> (except for libthrift ..., which I think I might have I chosen to not
>> install).
>>
>> My notes indicate that the last time I used PyBOMBS was in early
>> February, less than two weeks after the official switch from the old
>> Pybombs to Pybombs2. I had enough trouble with it that I found it
>> easier to install UHD and GNURadio (granted, in the default
>> directories) and all dependencies by hand.
> Yeah, the start of things that need to adapt to a variety of platforms
> is usually a bit rough ? Pybombs2 was no exception.
>> I bet, by now, it's a bit more user friendly and would be a good place
>> to start for using a custom directory. I probably shouldn't be trying
>> all this by hand without understanding CMake.
>>
>> Thanks for taking the to explain a bit of what's going on. I hope this
>> helps to explain my current configuration, though I'm still not too
>> sure why gr-ettus can't find FindUHD.cmake (which exists in
>> /opt/gnuradio-rfnoc/lib64/cmake/gnuradio/, with
>> /opt/gnuradio-rfnoc/lib64 being my "LD_LIBRARY_PATH" which is exported
>> when I try to build gr-ettus). I wonder if it's because I used
>> "-DLIB_SUFFIX=64" when building UHD, but again, I probably don't know
>> enough about cmake, compilers, or C++ in general.
> Hm, it's possible cmake is really expecting some hint where to look for
> Cmake scripts ? I must admit I don't know whether such an environment
> variable exists, or so. Maybe someone else has an idea!
>>
>> Also, it might be good to mention that when I run "uhd_usrp_probe
>> --init-only", I get the following output:
>>
>> *linux; GNU C++ version 5.3.1 20160413; Bost_105800;
>> UHD_003.010.rfnoc-471-g37ffaef2*
>>
>> which seems to indicate that I do have an RFNOC version of UHD built
>> and installed.
> That's great :)
>
> Best regards,
> Marcus
>
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
------------------------------
Message: 4
Date: Wed, 1 Jun 2016 14:36:49 +0200
From: LEMENAGER Claude <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [USRP-users] Tune request with frequency Offset
Message-ID:
<59957d668d245c4eb38e8f85c054e901080e553...@thsonea01cms09p.one.grp>
Content-Type: text/plain; charset="us-ascii"
Hello,
I am looking for acquisition, in gnu radio (companion) of signal in IF (75MHz)
through a basic RX installed in a X310.
If I know how to build a tune request in C++ (with frequency offset), I didn't
find such a way in GRC and GR (python).
The question is: how to fill the RF center frequency with such "object" in the
usrp_source or usrp_sink blocks?
Is it possible in gnuradio companion?
Thank for answers.
Claude
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20160601/f55cd892/attachment-0001.html>
------------------------------
Message: 5
Date: Wed, 1 Jun 2016 08:55:34 -0400
From: Dave NotTelling <[email protected]>
To: LEMENAGER Claude <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [USRP-users] Tune request with frequency Offset
Message-ID:
<cak6gvuo+p7gy10dqtjp1rypvyqtdxslxuyasdcbdv13nlba...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Claude,
Check out
https://github.com/gnuradio/gnuradio/blob/master/gr-uhd/examples/python/usrp_spectrum_sense.py.
Line 249 is what I think you want.
I seem to recall being able to put something like
`uhd.tune_request(target_freq,
lo_offset)` in the GNU Radio UHD source/sink block as the frequency. Then
target_freq and lo_offset can be variables in the GNU Radio graph. I can't
seem to find the example that uses it though :(
Hope that helps!
-Dave
On Wed, Jun 1, 2016 at 8:36 AM, LEMENAGER Claude via USRP-users <
[email protected]> wrote:
> Hello,
>
>
>
> I am looking for acquisition, in gnu radio (companion) of signal in IF
> (75MHz) through a basic RX installed in a X310.
>
> If I know how to build a tune request in C++ (with frequency offset), I
> didn?t find such a way in GRC and GR (python).
>
> The question is: how to fill the RF center frequency with such ?object? in
> the usrp_source or usrp_sink blocks?
>
> Is it possible in gnuradio companion?
>
>
>
> Thank for answers.
>
>
>
> Claude
>
>
>
>
>
>
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20160601/15cf8705/attachment-0001.html>
------------------------------
Message: 6
Date: Wed, 1 Jun 2016 15:16:17 +0200
From: LEMENAGER Claude <[email protected]>
To: Dave NotTelling <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [USRP-users] Tune request with frequency Offset
Message-ID:
<59957d668d245c4eb38e8f85c054e901080e553...@thsonea01cms09p.one.grp>
Content-Type: text/plain; charset="utf-8"
Thank you Dave,
GRC accepts the syntax and seems to work.
Best regards
Claude
De : Dave NotTelling [mailto:[email protected]]
Envoy? : mercredi 1 juin 2016 14:56
? : LEMENAGER Claude
Cc : [email protected]
Objet : Re: [USRP-users] Tune request with frequency Offset
Claude,
Check out
https://github.com/gnuradio/gnuradio/blob/master/gr-uhd/examples/python/usrp_spectrum_sense.py.
Line 249 is what I think you want.
I seem to recall being able to put something like
`uhd.tune_request(target_freq, lo_offset)` in the GNU Radio UHD source/sink
block as the frequency. Then target_freq and lo_offset can be variables in the
GNU Radio graph. I can't seem to find the example that uses it though :(
Hope that helps!
-Dave
On Wed, Jun 1, 2016 at 8:36 AM, LEMENAGER Claude via USRP-users
<[email protected]<mailto:[email protected]>> wrote:
Hello,
I am looking for acquisition, in gnu radio (companion) of signal in IF (75MHz)
through a basic RX installed in a X310.
If I know how to build a tune request in C++ (with frequency offset), I didn?t
find such a way in GRC and GR (python).
The question is: how to fill the RF center frequency with such ?object? in the
usrp_source or usrp_sink blocks?
Is it possible in gnuradio companion?
Thank for answers.
Claude
_______________________________________________
USRP-users mailing list
[email protected]<mailto:[email protected]>
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20160601/e4918cbf/attachment-0001.html>
------------------------------
Message: 7
Date: Wed, 1 Jun 2016 15:30:57 +0200
From: Pol Henarejos <[email protected]>
To: "usrp-users lists.ettus.com" <[email protected]>
Subject: [USRP-users] Octoclock updating firmware & change ip
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
Dear all,
Recently we acquired an Octoclock-G. When I try to upgrade the firmware to the
newest image, I get the following error:
phenarejos@pc :/usr/local/lib/uhd/utils$ sudo uhd_image_loader
--args="type=octoclock,addr=192.168.10.3"
linux; GNU C++ version 4.9.2; Boost_105500; UHD_003.009.002-0-gf18abe54
Unit: OctoClock (192.168.10.3)
Firmware: /usr/local/share/uhd/images/octoclock_r4_fw.hex
-- Resetting into bootloader...failed.
Error: RuntimeError: Failed to reset OctoClock.
And no additional messges.
Plus, when I try to change the default IP I get:
phenarejos@pc :/usr/local/lib/uhd/utils$ ./octoclock_burn_eeprom
--args="addr=192.168.10.3"
--values="ip-addr=10.1.1.10,netmask=255.0.0.0,gateway=10.1.1.1"
linux; GNU C++ version 4.9.2; Boost_105500; UHD_003.009.002-0-gf18abe54
Creating OctoClock device from args: addr=192.168.10.3
-- Opening an OctoClock device...
-- Detecting internal GPSDO...No GPSDO found
UHD Warning:
Device reports that it has a GPSDO, but we cannot communicate with it.
-- Detecting external reference...false
-- Detecting switch position...Prefer external
-- Device is using internal reference
Fetching current settings from EEPROM...
EEPROM ["ip-addr"] is "192.168.10.3"
EEPROM ["netmask"] is "255.255.255.0"
EEPROM ["gateway"] is "192.168.10.1"
Setting EEPROM ["ip-addr"] to "10.1.1.10"...
Setting EEPROM ["netmask"] to "255.0.0.0"...
Setting EEPROM ["gateway"] to "10.1.1.1"...
Error: RuntimeError: Error writing to OctoClock EEPROM.
Could someone help me to update and change IP of the octoclock?
Thank you so much.
--
Pol Henarejos
Research Engineer, MSc
[email protected]
Centre Tecnol?gic de Telecomunicacions de Catalunya (CTTC)
Engineering Unit
Parc Mediterrani de la Tecnologia
Av. Carl Friedrich Gauss, 7
08860 Castelldefels
Tel: +34 93 396 71 70 Ext: 2177
Fax. +34 93 645 29 01
www.cttc.es
------------------------------
Message: 8
Date: Wed, 01 Jun 2016 09:02:03 -0500 (CDT)
From: Mike Williams <[email protected]>
To: [email protected]
Subject: [USRP-users] E310 firmware downgrade
Message-ID:
<15075391.706172.1464789723588.javamail.r...@vznit170126.mailsrvcs.net>
Content-Type: text/plain; charset="us-ascii"
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20160601/df8fb210/attachment-0001.html>
------------------------------
Message: 9
Date: Wed, 1 Jun 2016 10:16:04 -0400
From: Philip Balister <[email protected]>
To: Mike Williams <[email protected]>, [email protected]
Subject: Re: [USRP-users] E310 firmware downgrade
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252
On 06/01/2016 10:02 AM, Mike Williams via USRP-users wrote:
> Is there a way to downgrade the E310 firmware from 2.0 to a prior version?
> Thanks.
All the previous file system images are on file.ettus.com? Can you
explain exactly what you are trying to do?
Philip
>
>
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
------------------------------
Subject: Digest Footer
_______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
------------------------------
End of USRP-users Digest, Vol 70, Issue 1
*****************************************
