Phase-locked loop range
parameter of phase-locked loop engineering
The terms hold-in range, pull-in range (acquisition range), and lock-in range are widely used by engineers for the concepts of frequency deviation ranges within which phase-locked loop-based circuits can achieve lock under various additional conditions.
History
In the classic books on phase-locked loops, published in 1966, such concepts as hold-in, pull-in, lock-in, and other frequency ranges for which PLL can achieve lock, were introduced. They are widely used nowadays (see, e.g. contemporary engineering literature and other publications). Usually in engineering literature only non-strict definitions are given for these concepts.
Many years of using definitions based on the above concepts has led to the advice given in a handbook on synchronization and communications, namely to check the definitions carefully before using them. Later some rigorous mathematical definitions were given in.
Gardner problem on the lock-in range definition
In the 1st edition of his well-known work, Phaselock Techniques, Floyd M. Gardner introduced a lock-in concept: If, for some reason, the frequency difference between input and VCO is less than the loop bandwidth, the loop will lock up almost instantaneously without slipping cycles. The maximum frequency difference for which this fast acquisition is possible is called the lock-in frequency. His notion of the lock-in frequency and corresponding definition of the lock-in range have become popular and nowadays are given in various engineering publications.
“Phase-locked loop range” enters the record as parameter of phase-locked loop engineering. Crown Archives preserves that source wording while asking what Phase-locked, loop and range can confirm, complicate or overturn.
Why this record matters
“Phase-locked loop range” is worth following because a concise public description often conceals a longer documentary argument. Here, Phase-locked, loop and range provides the most credible route into that argument.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Jun 22, 2026. The linked authority identifier is Q25304097. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1966.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Phase-locked loop range”, its source revision and the description used here.
- Expand the search: follow Phase-locked loop range primary sources, Phase-locked loop range archive and Phase-locked research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Phase-locked loop range”?
- Which institution is responsible for the underlying evidence?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “Phase-locked loop range” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.