discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] uhd_fft problems (runtime error)


From: Marcus D. Leech
Subject: Re: [Discuss-gnuradio] uhd_fft problems (runtime error)
Date: Tue, 20 Aug 2013 17:23:16 -0400
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111108 Fedora/3.1.16-1.fc14 Thunderbird/3.1.16

On 08/20/2013 01:27 PM, Marcus Müller wrote:
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.html#firewall-issues ;
use the firewall administration utility to change the settings accordingly.

Greetings,
Marcus M
On 20.08.2013 19:13, Victor User wrote:
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
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





-- 
Marcus Leech
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org

reply via email to

[Prev in Thread] Current Thread [Next in Thread]