usrp-users@lists.ettus.com

Discussion and technical support related to USRP, UHD, RFNoC

View all threads

Question on using USRP sink/sources in GNU Radio recent release

SE
Samudra E Haque
Mon, Nov 14, 2011 3:49 PM

Hello, as some of you may know I recently installed a fresh GNURADIO
package, after a manual install of a UHD package on my Ubuntu 10.04 LTS
workstation.

dpkg -i UUHD-003.003.001-Ubuntu-10.04-x86_64.deb

(from git)
cat version.sh
MAJOR_VERSION=3
API_COMPAT=5
MINOR_VERSION=0rc0
MAINT_VERSION=0

So far so good, Gnu Radio Companion works etc., uhd_fft.py, Audio examples
work etc.

My test setup: USRP/TVRX2 -- USB -- USB (UHD) -- HOST

However, as I had attempted earlier installs, some old files remain. My
question is: are the files provided in the following list already
deprecated? The majority of them include "from gnuradio import usrp" or
"from gnuradio import usrp2" string in their header, and I have confirmed
even the most basic example listed in http://www.joshknows.com/gnuradio
(See USRP Examples) fails. So, is there a recommended way to modify these
python files to use the UHD driver instead of (missing?) USRP or USRP2
blocks? If these files will not be needed anymore (as UHD supercedes
USRP), why keep them around on public websites? But if they have any
educational value, then why not keep a "stub" usrp entry that spits out an
error message to the calling script with a blurb of something like
"feature deprecated, please use UHD".. so that old code examples can be
ported to newer coding standards?

Traceback (most recent call last):
File "foo.py", line 2, in <module>
from gnuradio import usrp
ImportError: cannot import name usrp

Now a general question for the archive-maintainers, is there a handy
reference of the supported/tested status of each of these files? I see
that (I believe..) none of the files have a timestamp or author
information, or even a specification block as to the exact test
environment this code was executed in. Is that information available
elsewhere as a release note accompanying the package or only available
through a git log entry?

Regards,

Samudra N3RDX

usrp2_fft.py
usrp_oscope.py
usrp_rx_nogui.py
usrp_siggen_gui.py
usrp_siggen.py
usrp_fft.py
usrp_sounder.py
qt_digital_window.ui
usrp_display_qtgui.ui
usrp_psr_receiver.py
usrp_ra_receiver.py
usrp_radar_mono.py
file_rx_lrit.py
usrp_rx_lrit.py
gpio_rx_sfile.py
gpio_usrp_fft.py
gpio_usrp_siggen.py
usrp2_probe
usrp2_rx_cfile.py
usrp_probe
lsusrp
usrp_print_db.py
usrp_rx_cfile.py
usrp_test_counting.py
usrp_test_loopback.py
usrp2_burn_mac_addr
find_usrps
usrp2_socket_opener
usrp_cal_dc_offset
usrper
bitbake

Hello, as some of you may know I recently installed a fresh GNURADIO package, after a manual install of a UHD package on my Ubuntu 10.04 LTS workstation. dpkg -i UUHD-003.003.001-Ubuntu-10.04-x86_64.deb (from git) cat version.sh MAJOR_VERSION=3 API_COMPAT=5 MINOR_VERSION=0rc0 MAINT_VERSION=0 So far so good, Gnu Radio Companion works etc., uhd_fft.py, Audio examples work etc. My test setup: USRP/TVRX2 -- USB -- USB (UHD) -- HOST However, as I had attempted earlier installs, some old files remain. My question is: are the files provided in the following list already deprecated? The majority of them include "from gnuradio import usrp" or "from gnuradio import usrp2" string in their header, and I have confirmed even the most basic example listed in http://www.joshknows.com/gnuradio (See USRP Examples) fails. So, is there a recommended way to modify these python files to use the UHD driver instead of (missing?) USRP or USRP2 blocks? If these files will not be needed anymore (as UHD supercedes USRP), why keep them around on public websites? But if they have any educational value, then why not keep a "stub" usrp entry that spits out an error message to the calling script with a blurb of something like "feature deprecated, please use UHD".. so that old code examples can be ported to newer coding standards? Traceback (most recent call last): File "foo.py", line 2, in <module> from gnuradio import usrp ImportError: cannot import name usrp Now a general question for the archive-maintainers, is there a handy reference of the supported/tested status of each of these files? I see that (I believe..) none of the files have a timestamp or author information, or even a specification block as to the exact test environment this code was executed in. Is that information available elsewhere as a release note accompanying the package or only available through a git log entry? Regards, Samudra N3RDX usrp2_fft.py usrp_oscope.py usrp_rx_nogui.py usrp_siggen_gui.py usrp_siggen.py usrp_fft.py usrp_sounder.py qt_digital_window.ui usrp_display_qtgui.ui usrp_psr_receiver.py usrp_ra_receiver.py usrp_radar_mono.py file_rx_lrit.py usrp_rx_lrit.py gpio_rx_sfile.py gpio_usrp_fft.py gpio_usrp_siggen.py usrp2_probe usrp2_rx_cfile.py usrp_probe lsusrp usrp_print_db.py usrp_rx_cfile.py usrp_test_counting.py usrp_test_loopback.py usrp2_burn_mac_addr find_usrps usrp2_socket_opener usrp_cal_dc_offset usrper bitbake