On Tue, May 17, 2011 at 2:45 AM, Colby Boyer <[email protected]> wrote:
> On Mon, May 16, 2011 at 6:22 PM, Josh Blum <[email protected]> wrote: > > > > > > On 05/16/2011 05:26 PM, Colby Boyer wrote: > >> Hi Tom, > >> > >> I tried running the uhd_fft.py script with the USRP1, but I run into > >> an error with > >> > >> RuntimeError: LookupError: KeyError: cannot set this property > >> in void usrp1_impl::mboard_set(const wax::obj&, const wax::obj&) > >> at /home/csboyer/uhd/host/lib/usrp/usrp1/mboard_impl.cpp:392 > >> > >> due to a call in the .py file: > >> self.u.set_clock_config(uhd.clock_config.internal(), uhd.ALL_MBOARDS) > >> > > > > Aha, no clocking options were implemented on USRP1. Thats why you see > > the error. I suppose it would be better to properly handle setting clock > > config even though its not really configurable. > > > > -Josh > > > > _______________________________________________ > > Discuss-gnuradio mailing list > > [email protected] > > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > > > Hi Josh, > > I ended up editing out that line and it works fine. > > Also the .py threw an error on > > File "./uhd_fft.py", line 212, in set_freq > self.myform['baseband'].set_value(r.actual_inter_freq) > AttributeError: 'tune_result_t' object has no attribute 'actual_inter_freq' > > It should really be r.actual_rf_freq > > Maybe you can be kind enough to push the change. . .I don't have access. I can certainly push a change, but patches are always welcome, too. Josh, was there are change in the tune_result_t names? When I made the code last week, the actual_inter_freq existed but now it doesn't. Tom
_______________________________________________ Discuss-gnuradio mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
