LCRF

Privacy preferences

Choose optional purposes independently. You can change or withdraw your choice at any time from the footer.

Strictly necessary

Required for security, session functions and storing your privacy choice.

Always active
Preferences

Remembers optional display or language settings when these features are enabled.

Analytics

Uses first-party visitor and session identifiers to measure pages, referrals and inquiry interactions.

Marketing

Allows marketing measurement or third-party advertising technologies if they are introduced in the future.

Navigation, Timing and Positioning Engineering

What does holdover mean in a GNSS-disciplined timing system?

Holdover is the bounded time or frequency performance after GNSS reference loss, defined by the starting state, outage duration, environment, local oscillator, steering history, maximum time error and recovery rule.

Holdover begins when the timing unit can no longer discipline its local oscillator from an accepted GNSS reference. A usable requirement names the pre-outage lock and warm-up state, outage duration, temperature and supply profile, oscillator type and history, allowed frequency behavior and maximum accumulated time or phase error at the delivered output.

Do not reduce holdover to the oscillator data-sheet accuracy. The steering loop estimates and corrects oscillator behavior while GNSS is available; environmental change, aging, prior learning interval and the algorithm used after reference loss all influence the result. State the stability statistic and averaging interval for frequency outputs and the time-error mask for timing outputs.

Also define loss detection, alarm latency, output-valid flag, behavior during degraded or intermittent reception, reacquisition and any permitted phase correction after recovery. Test from controlled initial states at relevant temperatures and retain the complete time-error record; a single end-point value can hide steps or excursions that downstream equipment cannot accept.

Engineering inquiry

Share your RF requirement

Share the product, operating requirements and project context. Our engineering team will route your request to the right specialist.

AttachmentsAttach drawings, BOMs, specifications or test files. Up to 5 files, 10 MB each and 25 MB total.
or drag and dropPDF, DOCX, XLSX, CSV, TXT, JPG, PNG, S1P and S2P
Typically reviewed within one business dayProject information is handled confidentially