Forum: GNU Radio uhd_fft problems (runtime error)

40ff8f60ca87d242ef8a9e51b7ffee13?d=identicon&s=25 Victor User (Guest)
on 2013-08-20 19:14
(Received via mailing list)
Hello, I'm new to using GNURadio and the USRP.

I'm running Fedora 17 with GNURadio (3.5.3.1) and UHD (3.4.3) installed
with yum.

I'm trying to run uhd_fft.py and I get the following error:

$ ./uhd_fft.py
linux; GNU C++ version 4.7.0 20120507 (Red Hat 4.7.0-5); Boost_104800;
UHD_003.004.003-0-unknown

Using Volk machine: sse4_1_64_orc
Traceback (most recent call last):
 File "./uhd_fft.py", line 180, in <module>
 tb = uhd_fft(gain=options.gain, freq=options.freq,
address=options.address, samp_rate=options.samp_rate)
 File "./uhd_fft.py", line 110, in __init__
 channels=range(1),
 File
"/usr/local/lib64/python2.7/site-packages/gnuradio/uhd/__init__.py",
line 116, in constructor_interceptor
 return old_constructor(*args)
 File
"/usr/local/lib64/python2.7/site-packages/gnuradio/uhd/uhd_swig.py",
line 2296, in usrp_source
 return _uhd_swig.usrp_source(*args)
RuntimeError: send_to: Network is unreachable


I'm wondering if there is a mismatch on my UHD driver and the
firmware/fpga images?

Because when I do:

$ uhd_find_devices
linux; GNU C++ version 4.7.0 20120507 (Red Hat 4.7.0-5); Boost_104800;
UHD_003.004.003-0-unknown

No UHD Devices Found

BUT:
$ uhd_find_devices --args="addr=192.168.10.2"
linux; GNU C++ version 4.7.0 20120507 (Red Hat 4.7.0-5); Boost_104800;
UHD_003.004.003-0-unknown

--------------------------------------------------
-- UHD Device 0
--------------------------------------------------
Device Address:
 type: usrp2
 addr: 192.168.10.2
 name:
 serial: E0R22N8UP


A similar thing happens when I run 'uhd_usrp_probe' ... if I do not
specify the address then nothing is found, but if I supply the IP
address then it prints out information that looks good.

I can ping 192.168.10.2 successfully as well.

Any ideas?
Thanks
7d89a70df32c0ae27c1235016f9e5441?d=identicon&s=25 "Marcus Müller" <marcus@hostalia.de> (Guest)
on 2013-08-20 19:28
(Received via mailing list)
Hi Victor,
this looks like a network malconfiguration.
With redhat/fedora-based Distributions usually a rather restrictive
firewall is shipped, disabling a range of types of broadcast traffic.
The issue is described at
http://files.ettus.com/uhd_docs/manual/html/usrp2.... ;
use the firewall administration utility to change the settings
accordingly.

Greetings,
Marcus M
558c40b97bd1af8d912424757714bda9?d=identicon&s=25 Marcus D. Leech (Guest)
on 2013-08-20 23:24
(Received via mailing list)
On 08/20/2013 01:27 PM, Marcus Mller wrote:
> Marcus M
>> Boost_104800; UHD_003.004.003-0-unknown
>> line 116, in constructor_interceptor
>>     return old_constructor(*args)
>>   File
>> "/usr/local/lib64/python2.7/site-packages/gnuradio/uhd/uhd_swig.py",
>> line 2296, in usrp_source
>>     return _uhd_swig.usrp_source(*args)
>> RuntimeError: send_to: Network is unreachable
Basically what's going on is that UHD, when given no hint about what
device to go looking for, goes down a list of things to try.
   When it tries to do a broadcast "probe" to find a USRP2 or N210
device, it can get an error back from the kernel.

But if you use an *explicit* device address, you can avoid that problem.

You don't indicate what type of USRP you have, but:

uhd_fft --args "addr=192.168.10.2"

or

uhd_fft --args "type=b100"

or

uhd_fft --args "type=usrp1"

Will avoid this problem, as will tweaking your firewall and network
configuration
Please log in before posting. Registration is free and takes only a minute.
Existing account

NEW: Do you have a Google/GoogleMail, Yahoo or Facebook account? No registration required!
Log in with Google account | Log in with Yahoo account | Log in with Facebook account
No account? Register here.