Hello,
I have run into some unexpected behavior with the PLL1 DLD on the LMK04610. It appears that the device indicated PLL1 lock shortly after startup as expected, but then indicates unlock periodically for up to a couple minutes. When observed on an oscilloscope the lock signal can bee seen to start with an unlock period of around 600Hz and then slowly decrease in frequency. This increase in time between unlock events eventually leads to a stable PLL1 lock detect output indicating the PLL is locked. I have not seen it unlock again after the lock detect signal goes stable. I have included an example scope screen shot below in Figure1.
I have attempted to adjust to the PLL1 tuning thinking it was ringing, but adjustment of the PPL1 proportional gain has little to no effect until the extremes where it causes the PLL to become unstable. Adjusting PLL1 integrator gain does reduce the time to a stable lock signal, but maxing out the PLL1_INTG parameter only reduces the stable lock time to around 5 seconds.
Figure1: Unlock signal shortly after startup (Pink) and correspond VCXO voltage (Orange)
In another effort I adjusted the DLD lock count. Lowering the lock count did not effect the stable lock time, but increasing the lock count to above 0x080000 had a substantial impact on the lock detect signal. I made a table showing the tested values and rough time to a stable lock detect signal below. This seems counter intuitive and makes me believe there is something about the DLD that I am mis-understanding or have incorrectly configured.
Lock Cycle Count | Approximate Lock Stable Time |
0x000400 | 10 seconds |
0x004000 | 10 seconds |
0x020000 | 10 seconds |
0x040000 | 10 seconds |
0x080000 | 2 seconds |
0x200000 | < 1 second |
As a starting point I have included the TICS Pro file used as the base configuration for my testing and here are my system specs
VCXO: Crystek CVHD-950
Ref Oscillator: Abracon AOCJY2
Ref Frequency: 100MHz
VCXO Frequency: 125MHz
VCXO Gain: +3.125kHz/V
If anyone else has seen this lock detect signal behavior or can provide some advice on how to fix, or further trouble shoot, this behavior It would be extremely helpful.