Multipath and external RF interference can both make GNSS look unreliable, but they do not create the same purchase. If reflected satellite signals dominate, review antenna location and multipath-oriented reception. If a separate radio signal is degrading reception, evaluate an interference-mitigation path. A blocked view of the sky is a third problem: neither category can recover satellites that the antenna cannot see.
This guide is for a buyer or integrator deciding whether a precision GNSS antenna or an anti-jamming configuration belongs on the shortlist. An unstable position alone does not identify the cause. Receiver status, antenna surroundings and time-aligned equipment activity matter more than the product label on a proposed replacement.
Separate reflected GNSS signals from an interfering transmitter
Multipath means a satellite signal reaches the antenna directly and again after reflecting from a surface such as a building, metal roof, ground or water. The delayed copy can distort a receiver measurement even while satellites remain tracked. NovAtel’s multipath explanation describes this mechanism. For a fixed reference site, antenna placement, the surrounding reflective surfaces and phase-centre requirements can therefore matter to the purchase.
For the measurement-level distinction, compare GNSS multipath and NLOS reception before treating a reflected-signal mitigation claim as correction of a blocked direct path.
RF interference comes from another radio-energy source competing with or disrupting GNSS reception. An anti-jamming system can reduce specified interference within its documented design boundary; it is not a generic correction for reflected satellite paths. NovAtel’s interference guide explains the distinct role of anti-jam antenna electronics. These are industry principles, not a claim about the performance of a ResiNav model.
The categories can overlap in a real installation, and one product may document more than one function. Calian’s antenna selector nevertheless separates anti-jam/CRPA options from multipath-oriented precision antenna categories. Do not infer either function from the words “GNSS antenna” alone, or from an element count.
When the purchase is an antenna replacement, compare RHCP and linear polarization, including the installed viewing angles, before treating two GNSS antenna offers as equivalent.
Choose the next purchase path from the evidence
| Observed pattern to investigate | Useful distinction | Purchase path to evaluate |
|---|---|---|
| Position quality varies near reflective roofs, walls, vehicles or water while satellite tracking continues. | Compare site geometry, receiver measurements and repeat observations. A visual symptom alone does not prove multipath. | Review relocation or a suitable multipath-oriented antenna and, where relevant, phase-centre documentation. Do not add an anti-jamming unit solely because the position is unstable. |
| Tracking degrades when a nearby transmitter or switching device is active, with time-aligned RF and receiver evidence. | Confirm the affected signals and RF path rather than assigning cause from coincidence alone. | Review coexistence measures and a documented interference-mitigation configuration. A choke-ring or precision label alone does not establish jammer rejection. |
| Satellites disappear below a roof, inside a tunnel or behind structures. | Determine whether usable sky view is physically absent during the transition. | Review antenna placement and system fallback. Do not specify either antenna category as a substitute for missing satellite visibility. |
| Reflections and an RF source are both plausible. | Keep site/antenna effects and transmitter/receiver effects as separate observations. | Scope the precision-antenna/site decision and the RF-mitigation decision separately; combine them only when the exact offered configuration documents both functions. |
These are conditional buying routes, not remote diagnoses. Trimble’s geodetic antenna comparison illustrates a multipath-oriented choice for its own reference-station products; its specifications and results do not transfer to a ResiNav product. Use the RF coexistence guide for a suspected on-platform emitter and the receiver evaluation guide when receiver behavior under controlled interference is the open question.
What changes the equipment order?
Illustrative reference-site case: an antenna sits beside a reflective parapet, the receiver continues tracking, and coordinate quality varies with satellite geometry. The first purchase decision is whether the site or antenna system needs changing. A multipath-oriented geodetic antenna may belong in the comparison, but its signal coverage, calibration and installation still need to fit the project. Ordering an anti-jamming unit from the symptom alone would skip the more relevant mechanism.
Illustrative machine case: tracking degrades during operation of a nearby radio, with supporting receiver and RF observations under comparable sky conditions. The first equipment decision is whether the RF source can be separated or managed, and whether a documented mitigation configuration is needed at the affected GNSS input. A precision or choke-ring antenna is not, by its name, an equivalent replacement for that protection path.
Both cases are decision examples, not ResiNav field results. If the receiver is losing a correction stream rather than satellite observations, use the anti-jamming versus RTK buying guide instead. If the platform output or controller rejects otherwise available GNSS data, compare receiver and controller records before purchasing antenna hardware.
Where a ResiNav product enters the shortlist
Use the published ResiNav product catalogue and English product data sheets when the purchase concerns interference mitigation for specified GNSS signals. They provide model-specific configuration facts for an initial screen. They do not, without separate evidence, establish multipath suppression, geodetic phase-centre behavior, compatibility with a named receiver, or a field outcome. A missing public field is unconfirmed, not proof that a feature is unsupported.
For an equipment order, keep the two potential scopes distinct: a multipath-oriented site/antenna package may require mounting and calibration records, while an RF-mitigation path may require the specified antenna or array, any necessary electronics, receiver interface and power arrangement. The exact included items depend on the documented offer. If the project needs both functions, ask for each to be identified explicitly rather than assuming a single label covers both.
Keep a short record before committing to either category
Retain the receiver’s satellite and solution status, antenna location and nearby reflectors, equipment or transmitter state, and the time of the observed change. Compare runs only when their conditions are sufficiently alike. This small record supports the right purchase conversation; it is not a demand to complete a generic engineering dossier before making any shortlist. The monitoring-versus-protection guide helps if the actual requirement is an alert rather than mitigation hardware.
Frequently asked questions
Does this guide identify a final configuration?
No. It identifies the inputs needed to begin a review. Final suitability remains subject to verified product documentation and engineering confirmation.
Should a project wait until every detail is known?
No. Start with the available platform and receiver information, but clearly label unknown items so they can be resolved during the review.
Can this process be used for more than one type of platform?
Yes. The information structure applies across commercial and industrial integration projects; the specific installation constraints must still be assessed for each platform.