Re: [Discuss-gnuradio] Failed to tune to low frequency with usrp.tune

2007-08-22 Thread Eric Blossom
On Wed, Aug 22, 2007 at 01:46:06PM -0700, Matt Ettus wrote: > Bahn William L Civ USAFA/DFCS wrote: > > > >> That is because the onboard VCO typically won't tune below 2.3 GHz. You > >> can change line 456 in gr-usrp/src/db_flexrf.py to allow you to try > >> going lower. > >> > >> Matt > >>

Re: [Discuss-gnuradio] Failed to tune to low frequency with usrp.tune

2007-08-22 Thread Matt Ettus
Bahn William L Civ USAFA/DFCS wrote: > >> That is because the onboard VCO typically won't tune below 2.3 GHz. You >> can change line 456 in gr-usrp/src/db_flexrf.py to allow you to try >> going lower. >> >> Matt >> > > Is there someplace where the (nominal) tunable ranges of each of the >

RE: [Discuss-gnuradio] Failed to tune to low frequency with usrp.tune

2007-08-22 Thread Bahn William L Civ USAFA/DFCS
> > That is because the onboard VCO typically won't tune below 2.3 GHz. You > can change line 456 in gr-usrp/src/db_flexrf.py to allow you to try > going lower. > > Matt Is there someplace where the (nominal) tunable ranges of each of the daughterboards is available? ___

Re: [Discuss-gnuradio] Failed to tune to low frequency with usrp.tune

2007-08-22 Thread Matt Ettus
DiX wrote: > Hi, > > I am playing with a program which transmits music with narrow band freq > modulation between two FLEX2400 broads. > > The program works like a charm when I tune to 2.4Ghz with the sentence: > > " self.tx.tune(self.subdev._which, self.subdev, freq) ". > > But