[USRP-users] E100 + GnuRadio

Marcus D. Leech mleech at ripnet.com
Fri Oct 23 09:21:38 EDT 2015


On 10/23/2015 04:18 AM, Vidak Kazic wrote:
>
> Dear Marcus,
>
> Thank you for your reply and help. First, I’ve checked the “no gui” 
> field in GRC. Secondly, I’ve installed the older version of gnuradio 
> on my host PC too, so now the command:
>
> from gnuradio import gr
>
> gr.version()
>
> returns *3.7.6.1* for both my host PC and the E100 device, so they 
> have a matching version of gnuradio.
>
> However,  the error I get now when I try to run the .py file is:
>
> root at ettus-e1xx:~# python fir.py
>
> linux; GNU C++ version 4.9.1; Boost_105600; UHD_003.008.000-0-unknown
>
> Traceback (most recent call last):
>
>   File "fir.py", line 71, in <module>
>
>     tb = fir()
>
>   File "fir.py", line 34, in __init__
>
> channels=range(1),
>
>   File "/usr/lib/python2.7/site-packages/gnuradio/uhd/__init__.py", 
> line 122, in constructor_interceptor
>
>     return old_constructor(*args)
>
>   File "/usr/lib/python2.7/site-packages/gnuradio/uhd/uhd_swig.py", 
> line 1728, in make
>
>     return _uhd_swig.usrp_source_make(*args)
>
> RuntimeError: LookupError: KeyError: No devices found for ----->
>
> Empty Device Address
>
> Also, uhd_find_devices returns:
>
> root at ettus-e1xx:~# uhd_find_devices
>
> linux; GNU C++ version 4.9.1; Boost_105600; UHD_003.008.000-0-unknown
>
> No UHD Devices Found
>
> I don’t know how to overcome this error, I’ve looked at all the 
> mailing list and forum posts with similar problems, but haven’t found 
> a solution.
>
> Thank you in advance,
>
> Best,
>
> Vidak
>
Try putting "type=e100"  into the device address.


> *From:*Marcus D. Leech [mailto:mleech at ripnet.com]
> *Sent:* Mittwoch, 21. Oktober 2015 17:49
> *To:* Vidak Kazic
> *Cc:* usrp-users at lists.ettus.com
> *Subject:* Re: [USRP-users] E100 + GnuRadio
>
> On 10/21/2015 11:25 AM, Vidak Kazic wrote:
>
>     Dear Marcus,
>
>     Thank you very much for your prompt and helpful response. By
>     “module” I do indeed refer just to the flow graph, and I do use
>     GRC. I successfully transferred the .py script, but after trying
>     to run it I’m getting an unexpected error:
>
>     root at ettus-e1xx:~# python fir2.py
>
>     Traceback (most recent call last):
>
>       File "fir2.py", line 18, in <module>
>
>         from PyQt4 import Qt
>
>       File "/usr/lib/python2.7/site-packages/PyQt4/Qt.py", line 1
>
>         from PyQt4.QtCore import *\n
>
>     ^
>
>     SyntaxError: unexpected character after line continuation character
>
> So, one issue is that Qt isn't supported on the E100, and in general, 
> since the E100 isn't really "desktop computer in a small package",
>   running flow-graphs that require graphics support is not 
> recommended.  But looking at your flow-graph, I see that you haven't
>   changed to the "NO Gui" option in the options block.
>
> But a larger issue is that the version of GR on the E100 image is 
> older, and so you have to have a matching version on the host that
>   you develop flow-graphs on.
>
> I'm not sure that there is a newer version of GR available--Phil 
> Balister was working on it, but ran into extreme problems.
>
>
>
>     Could you perhaps have an idea about the reason for this error?
>     The script was generated by GRC so I’m somewhat confused by this.
>     Maybe trying to update the software would help?
>
>
>
>     Moreover, would the “source” and “sink” components from GRC
>     automatically be mapped to the LFRX and LFTX buses(ports?not sure
>     about terminology) on the E100 device? My RF1 port is connected to
>     the LFTX daughteroard, and RF2 to LFRX daughterboard, so my goal
>     is to send a signal to RF2, and get a filtered signal on RF1. I’ve
>     attached the screenshot of the GRC graph, and the .grc file too.
>
> In GRC, "source" corresponds to the receiver side, and "sink" 
> corresponds to the transmitter side.
>
> You should probably spend some time on the gnuradio website, and also 
> with the UHD manual here:
>
> http://files.ettus.com/manual/
>
>
>
>     Again, your help and  time are highly appreciated.
>
>     Best regards,
>
>     Vidak
>
>     *From:*USRP-users [mailto:usrp-users-bounces at lists.ettus.com] *On
>     Behalf Of *Marcus D. Leech via USRP-users
>     *Sent:* Mittwoch, 21. Oktober 2015 16:26
>     *To:* usrp-users at lists.ettus.com <mailto:usrp-users at lists.ettus.com>
>     *Subject:* Re: [USRP-users] E100 + GnuRadio
>
>     On 10/21/2015 07:49 AM, Vidak Kazic via USRP-users wrote:
>
>         Hello,
>
>         I have created a simple FIR filter module in Gnuradio
>         companion, i.e. the interface. I’ve exported the module to a
>         Python script, fir.py. Now, I’d like to load the script onto
>         my E100, and map one RF input to the source in the FIR module,
>         and the other as sink. If I do this, am I right to assume that
>         I will have an active FIR filter?
>
>         So far I found the IP address of the device through a USB
>         connection and ifconfig, and then used: $ ssh
>         root at 10.41.78.208 <mailto:root at 10.41.78.208> (the ip address)
>         to make  a connection to the device. Now I’m not sure how to
>         use this connection to communicate with my device, and my
>         script is giving errors of “No device found”. How can I write
>         the FIR module from gnuradio to my E100 device?
>
>         Thanks in advance,
>
>         Vidak
>
>     If by "module" you just mean a flow-graph, then you can copy the
>     generated (you used GRC?) python file over to your E100, using
>       the SSH copy command, "scp":
>
>     scp <your-python-file> root at 10.41.78.208 <mailto:root at 10.41.78.208>:
>
>     Then you can ssh to the E100, and run the python file.
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20151023/42a55564/attachment-0002.html>


More information about the USRP-users mailing list