Re: PLL convergence problem



On 16 Oct 2005 10:38:08 -0700, allanherriman@xxxxxxxxxxx wrote:

>This reminds me of a "learning experience" I had with a tracking
>receiver design about 13 years ago. We could control the L.O.
>frequency in a downconverter to produce a constant I.F. output
>frequency, even though the carrier could vary by about 1/2 MHz (due to
>doppler, etc.).
>A narrowband 455kHz I.F. filter with a group delay of some ms was in
>the feedback loop. The system would sometimes lock several kHz (?)
>away from where it was supposed to be.
>
>I eventually found a paper that described the problem. I don't
>remember all the details, but "As long that the loop bandwidth is
>larger then
>the frequency offset, the loop should converge to the right frequency"
>is definitely false in the general case.
>
>A combination of high gain and delay caused the problem. Perhaps this
>is why the leaky integrator helped - it reduced the gain at low
>frequencies.

Depending on what signals you were locking it probably just found a
convenient false-lock point. Another way to prevent this sort of
thing is to try to design the loop to have only one stable operating
point, and that point being the desired lock frequency. Sometimes
even just a dip in the overal tracking response can create essentially
the same condition as an equalizer that has found a local minimum in
the convergence space. It'll sit there and not move unless something
perturbs it to find a better lock point.

The leaky integrator is sometimes enough to make these local minima or
false lock points just unstable enough to make it move on to the next
(hopefully correct) stable operating point.

Anyway, that's just another way to look at it.


Eric Jacobsen
Minister of Algorithms, Intel Corp.
My opinions may not be Intel's opinions.
http://www.ericjacobsen.org
.



Relevant Pages

  • Re: Independent thread fireing events in ATL Service synchronization requirements?
    ... and hence the loop will not execute, ... m_vec itself is not a pointer, so it cannot be NULL for sure. ... >> Did you lock while adding and removing your objects to the list? ... >>> and made my client list a class with synchronization inside ...
    (microsoft.public.vc.atl)
  • Re: 2Khz clock signal from 50Hz main frequency with ADPLL
    ... and the tracking speed becomes the PLL-LPF. ... Each new cycle uses the last cycles period, to get a best fit of 40 '2Khz' clocks. ... These lock frequecy, or cycles, but do not lock phase. ...
    (comp.arch.fpga)
  • Re: PLL convergence problem
    ... >>the feedback loop. ... and that point being the desired lock frequency. ... - multiplier type phase detector. ... which is influenced by the delay in the loop filter. ...
    (comp.dsp)
  • Re: Crystal drift
    ... >>Sideband locking is a possible strategy here. ... but it will try to lock up at the wrong null--which in a PFD ... loop bandwidth in this condition. ... All it takes is a twin-T or a phase shift oscillator network. ...
    (sci.electronics.design)
  • Re: DataTable weirdness
    ... > If I iterate through all the elements of a table in thread A, ... > correct assuming that the lock in thread B will block until the ... the collection will now have a gap between ... This causes problems for any loop that started with the assumption ...
    (microsoft.public.dotnet.languages.csharp)