From: Paul C. <pau...@ot...> - 2011-05-31 03:16:29
|
Hi Thomas and Sylvian, Here's the commands I ran with the usrp_fft.py, all of them resulted in failed to set initial frequency (I've got a screen shot if needed --- it's definitely unexciting!). If there was a problem with one daughterboard, then I would expect half the commands below to work (indicating which board had the problem). Again, if it were a problem with the frequencies then I would expect half of them to work (indicating which frequency they find impossible to tune to). Please, correct me if I'm wrong. [root@localhost ~]# usrp_fft.py -R B -f 1900M ^C [root@localhost ~]# usrp_fft.py -R B -f 1980M ^C [root@localhost ~]# usrp_fft.py -R A -f 1900M ^C [root@localhost ~]# usrp_fft.py -R A -f 1980M ^C One thing I noticed was that the application wouldn't shut down if I clicked the close button (hence the ^Cs). On 26/05/11 7:20PM, Sylvain Munaut wrote: >> Two things can cause the frequency tuning to return an error: either a >> lack of daughterboard lock or the register write itself for the tune >> failed. I suspect the prior. > Or you're not using the git version and still using the tarball that > has a bug in it ... Definitely using the git version. The last item in my git log is this: commit a2d4ed5c71835ad2c327bd9ad52de9abde613247 Author: Alexander Huemer <ale...@xx...> Date: Mon May 23 19:04:50 2011 +0200 configure.ac: use AM_SILENT_RULES if available Cheers, Paul |