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 & Positioning RF Hardware

Application engineering for GNSS and BeiDou antenna paths, low-noise receiver front ends, stable references and precision timing distribution, bounded by signal coverage, interference, cable delay, holdover, output interfaces and verification evidence.

Navigation, Timing & Positioning RF application visual

Start with the installed signal and timing boundary

Navigation, Timing & Positioning RF Hardware: Application engineering for GNSS and BeiDou antenna paths, low-noise receiver front ends, stable references and precision timing distribution, bounded by signal coverage, interference, cable delay, holdover, output interfaces and verification evidence.

This application connects the antenna installation, weak-signal receiver path, disciplined local reference and timing outputs. The public taxonomy is broader than the two inherited product records, so every model, performance limit and compliance claim requires project-specific confirmation.

Treat reception and timing as one evidence chain

RF hardware for Navigation, Timing & Positioning
Define the service, operating environment and loss-of-signal behavior
Navigation, Timing & Positioning RF requirements
Freeze the antenna-to-receiver reference plane
Navigation, Timing & Positioning RF architecture
Allocate weak-signal margin and blocker tolerance together
Navigation, Timing & Positioning RF hardware selection
Separate acquisition, discipline, holdover and recovery
Navigation, Timing & Positioning RF testing and verification
Specify PPS, frequency and time-code distribution at the load

How to Specify a GNSS Receiver Front End and Precision Timing Chain

A practical method for defining GNSS and BeiDou antenna paths, filtering, low-noise gain, receiver interference tolerance, disciplined references, holdover and PPS or 10 MHz distribution with measurable acceptance evidence.

GNSS RF Front-End & Precision Timing Specification

Articles

FAQ

How should GNSS receiver blocker and interference tolerance be specified?

Define the interferer waveform, frequency, bandwidth, duty cycle, coupling plane, wanted-signal state, exposure and measurable degradation or recovery metric instead of relying on an anti-jam label.

What belongs in a GNSS antenna, LNA, filter and cable RF budget?

Budget antenna gain, pre-LNA loss, LNA noise and gain, filtering, cable loss, active-antenna power, return loss, linearity, receiver range and blocker headroom in physical path order.

How should PPS and 10 MHz timing-distribution delay and skew be verified?

Verify every delivered timing channel at its real load by separating fixed calibrated delay, channel skew, environmental drift, output level, edge or phase behavior and path-dependent uncertainty.

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.

Does sharing a frequency reference make multiple RF sources phase coherent?

A shared reference aligns average frequency, but deterministic relative phase also depends on trigger timing, divider state, path delay, retune behavior, relock and restart conditions.

How should frequency accuracy, temperature stability, aging and holdover be specified?

Specify accuracy, temperature, aging and holdover as separate error terms with their own interval, environment, warm-up and reference history instead of one unexplained ppm value.

When should an RF source use phase-noise spot limits versus integrated jitter?

Use phase-noise spot or mask limits when offset regions drive RF behavior; use integrated jitter only when the project defines the integration band and a time-domain error budget.

What does PLL settling time mean, and why is lock detect not enough?

PLL settling time is the time from a defined disturbance until the RF output enters and remains inside specified frequency, phase, amplitude and spectral limits; lock detect is only an internal status signal.

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