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

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.

Write each interference case as a test vector: interferer frequency or sweep, modulation, occupied bandwidth, continuous or pulsed state, duty cycle, level, exposure time and the connector, antenna field or coupling path where it is applied. Define the wanted GNSS signal, constellation, band, level and tracking state at the same time. A dBm value without these conditions cannot be reproduced.

Choose a pass metric that follows the application. It may be acquisition time, tracked satellites, C/N0 degradation, data validity, timing error, loss-of-lock threshold, AGC state, false output suppression or recovery time. Include out-of-band transmitters that can compress the antenna LNA or receiver even when their energy is outside the GNSS passband.

Test both degradation and return to service. Record preselector, LNA, cable and receiver configuration, temperature, RF-level uncertainty and alarm behavior. Published ITU protection criteria are application- and band-specific analysis inputs; they do not replace an installed receiver coexistence test or justify a universal anti-jam claim.

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