This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

LMX2595: Lock Detect Pin when Frequency Hopping

Part Number: LMX2595

Hello E2E community,

I am troubleshooting the lock detect functionality on the MUXOut pin. Specifically, I am switching between frequencies in full assist mode at a very fast rate. If I slow down this rate, I see the lock detect pin go high on my oscilloscope. However, when I run at the rate I wish to run at, say, 75 MHz serial clock, I can see the frequency switching on my real-time spectrum analyzer. But when I examine the lock detect pin, when I expect it to go high, it just shows up as a noisy signal centered around DC, and when I expect it go low, there is almost no signal (obviously a bit of noise, but what one might expect for no signal. The noise level is still higher when I expect the lock detect to go high).

Does anyone have insights on why I'm not able to see lock detect when switching frequencies very quickly?

  • Hi Jonathan,

    the best guess is the lock detector response time is longer than the frequency hopping time. MUXout determines lock by reading the Vtune voltage (indirectly), if you are hopping the VCO too fast, MUXout may not be able to track Vtune seamlessly and therefore its output is not deterministic.