Using usrp_fft.py one RX tunes correctly, the other fails to tune to my ARFCN. 

The failed RX started out with a center frequency of 0MHz and failed to tune to anything that I tried. There were also a suspicious number of evenly spaced peaks displayed. 

Would this pinpoint a particular failed component on the dboard?

Regards,

Jie

On Mon, Oct 18, 2010 at 1:35 PM, Thomas Tsou <ttsou@vt.edu> wrote:
On Sun, Oct 17, 2010 at 10:18 PM, Jie M <jiejiejie112@gmail.com> wrote:
> Hi Thomas,
> It doesn't appear to be either of the eeproms, usrp_probe reads them both
> correctly.
> For both RX A and B:
> --------------------------------
>>>> USRP Probe
> Name:
> Flex 900 Rx
> Converter Rate:
> 64000000
> Uses Quadrature:
> True
> Gain Range (min, max, step size):
> 0.0
> 90.0
> 0.0500000007451
> Freq Range (min, max, step size):
> 750000000.0
> 1050000000.0
> 1
> --------------------------------
> TX A and B:
>>>> USRP Probe
> Name:
> Flex 900 Tx
> Converter Rate:
> 128000000
> Uses Quadrature:
> True
> Gain Range (min, max, step size):
> 0.0
> 0.0
> 1.0
> Freq Range (min, max, step size):
> 750000000.0
> 1050000000.0
> 1
> --------------------------------
> Any other ideas?

Try running usrp_fft.py on each side tuned to the uplink frequency of
the desired ARFCN.

 Thomas