discuss-gnuradio
[Top][All Lists]
Advanced

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

Re: [Discuss-gnuradio] usrp_probe fails with AttributeError: 'Param' ob


From: Jacinda Shelly
Subject: Re: [Discuss-gnuradio] usrp_probe fails with AttributeError: 'Param' object has no attribute 'get_input'
Date: Fri, 9 Jul 2010 14:49:29 -0400

> can you post the warnings? and what version of gnuradio?

Sorry - I meant to include that.  I'm using Version 3.3.1
(v3.3.1git-30-g278b6db3).

There are many multiples of these; this is a sample of the last five.  I
get the exact same warning with grc, but that runs fine.

Warning: Block with key "wxgui_histosink2" already exists.
  Ignoring: /usr/share/gnuradio/grc/blocks/wxgui_histosink2.xml
Warning: Block with key "wxgui_numbersink2" already exists.
  Ignoring: /usr/share/gnuradio/grc/blocks/wxgui_numbersink2.xml
Warning: Block with key "wxgui_scopesink2" already exists.
  Ignoring: /usr/share/gnuradio/grc/blocks/wxgui_scopesink2.xml
Warning: Block with key "wxgui_waterfallsink2" already exists.
  Ignoring: /usr/share/gnuradio/grc/blocks/wxgui_waterfallsink2.xml
Warning: Block with key "xmlrpc_client" already exists.
  Ignoring: /usr/share/gnuradio/grc/blocks/xmlrpc_client.xml
Warning: Block with key "xmlrpc_server" already exists.
  Ignoring: /usr/share/gnuradio/grc/blocks/xmlrpc_server.xml




>
>> Traceback (most recent call last):
>>    File "/usr/local/bin/usrp_probe", line 114, in<module>
>>      USRPProbeWindow()
>>    File "/usr/local/bin/usrp_probe", line 71, in __init__
>>      vbox.pack_start(get_input(usrp_which_param), False)
>>    File "/usr/local/bin/usrp_probe", line 42, in get_input
>>      input = param.get_input()
>> AttributeError: 'Param' object has no attribute 'get_input'
>>
>
> it works here, this may have more to do with the warnings.
>
>> I am confused about this as everything else gnuradio related is
>> functioning correctly.  Is usrp_probe no longer being supported and
>> the get_input() method was removed for some other reason?
>>
>
> nope
>
> -JOsh



reply via email to

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