USRP Software Radio

cancel
Showing results for 
Search instead for 
Did you mean: 

My New N210 always show "1074118626 local oscillator did not lock within the alloted time"

Solved!
Go to solution

Hi,

 

About error "1074118626 local oscillator did not lock within the alloted time" I found the alike thread in here, but at my case that error only occures when I used two N210-newly purchase.

 

When I put them two on transmitter side, that error occures at write-VI (niUSRP Write Tx Data (2D CDB).vi<ERR>The local oscillator did not lock within the alloted time)

When I make them as receiver, that erroor come up again a block initiate-VI (nuISRP Initiate.vi)<ERR>The local oscillator did not lock within the alloted time)

 

I replace those two with the old N210 and that error, disappear. Why ?

 

Thank you~

 

0 Kudos
Message 1 of 3
(4,302 Views)

Hi atafa,

 

It could be that the old and new N210s do not have the same firmware. You could try updating the firmware on your new boards and see if this fixes the behaviour:

http://digital.ni.com/public.nsf/allkb/F622E3B3B9CC34B6862579D500705272?OpenDocument

Libby B.
Applications Engineering Specialist - RF Wireless
National Instruments
0 Kudos
Message 2 of 3
(4,281 Views)
Solution
Accepted by topic author atafa

Hi Libby,

About the firmware and FPGA, I always make sure that both of them are update. Thank you for your suggestion.

 

Finally, I found the answer of "why that problem (1074118626 local oscillator did not lock within the alloted time) occured" It was because unsynchronous LO between the two USRP. I had solved the problem after connected both USRP using MIMO cable without any change in the LabVIEW code.

 

I don't know yet why the old USRP didn't need that synch thing.. anyway.. I'm glad that my problem was solved.

0 Kudos
Message 3 of 3
(4,213 Views)