Buy interference protection for the part of the route where usable satellite signals are being disrupted. Buy an appropriate navigation-aiding solution for the part where satellite observations are unavailable. An anti-jamming array and an inertial navigation system (INS) can address different parts of the same requirement; neither label, by itself, promises continuous positioning within your equipment’s error limit.
This guide is for vehicle OEMs and integrators deciding whether a quotation needs RF mitigation, GNSS/INS integration, or both. It separates the purchase scopes before a model shortlist is made. It does not describe an installed ResiNav/INS combination or a tested outage performance.
Choose the function from the operating segment
A receiver losing its fix is an observation, not a diagnosis of jamming. Start with the known operating condition. When the cause is still uncertain, the interference-environment guide helps separate observations without assigning a cause from a single status flag.
| Operating segment | What belongs in the shortlist | What the purchase does not establish |
|---|---|---|
| Open-sky operation with a confirmed interference problem | A mitigation configuration covering the receiver’s required GNSS signals and RF boundary. | An array alone does not specify how the vehicle estimates motion once satellite observations disappear. |
| A bounded passage with little or no usable sky view | A navigation solution designed to bridge the required outage, such as an appropriately configured GNSS/INS system and any required aiding sensors. | More anti-jamming elements do not create satellite observations through an obstruction. |
| A route containing both interference exposure and covered sections | Separate mitigation and outage-navigation requirements in the system purchase. They may be supplied as separate components or an integrated solution. | Two individually described products are not automatically an interoperable or accepted system. |
| Long or unbounded operation without GNSS | Reconsider the navigation concept and external references available for that environment. | A short-outage INS specification is not a guarantee of indefinite accurate dead reckoning. |
NovAtel’s interference overview describes both anti-jam antenna systems and additional navigation sensors for short outages. These are complementary approaches to different problems, not interchangeable descriptions of one component.
An IMU is not the same purchase as a working GNSS/INS solution
An inertial measurement unit (IMU) supplies motion measurements. An INS uses inertial measurements to calculate navigation quantities; a GNSS/INS solution combines that navigation process with GNSS. NovAtel’s GNSS/INS explanation describes computing position, velocity and attitude from motion measurements and bridging periods of degraded or unavailable GNSS.
For a buyer, this creates a practical scope distinction: an IMU line item does not tell you who supplies the navigation computation, how it is initialized or which output reaches the controller. A receiver with an optional inertial feature is also not the same as a quote that includes the required sensor, enabled software and integration work. Compare the delivered configuration, not just the presence of the letters “IMU” or “INS.”
If navigation is required before the platform can move, compare GNSS/INS initial alignment against the actual restart condition, not only an already-running outage result.
Outage error depends on the system and its aiding conditions. For a concrete vendor example, NovAtel’s DMI documentation explains how wheel-distance input can constrain INS error growth during GNSS outages. That is a documented option for the specified NovAtel systems, not a claim that any wheel signal works with any INS or that a ResiNav product provides that input.
Size the outage interval before comparing a duration claim
Illustrative covered-passage example — not a ResiNav test. Assume usable GNSS is lost exactly at the entrance to a 48 m covered passage. The vehicle travels at a constant 2 m/s while moving, stops inside for 10 seconds, then takes another 2 seconds after exiting before the system accepts the recovered GNSS solution.
Travel without the stop: 48 m ÷ 2 m/s = 24 s.
Navigation interval to cover: 24 s travel + 10 s stop + 2 s recovery = 36 s.
The drawing-free example specifies a duration only. It says nothing about the position error, heading error or safety of a particular navigation system.
A purchasing requirement based on the 24-second travel time alone would omit 12 seconds. If a proposed configuration is only characterized for a 30-second outage, that statement does not cover this 36-second example. A longer-duration statement is still insufficient unless its error limits, initialization, motion and aiding conditions match the intended use.
The actionable decision is whether the system can meet the required output limits over the full interval or whether operation must change. If coverage cannot be established, options include changing the route, introducing another suitable positioning reference, or having the equipment enter a defined non-GNSS operating state. Merely slowing the vehicle can lengthen time without GNSS; it is not automatically a cure for drift. The equipment owner must determine the permissible behavior—this example is not a safety approval.
Where a ResiNav product fits in that purchase
Use the ResiNav product catalogue to screen the mitigation part of the requirement. For example, the public RN2501-AJS-4CH-DPA record describes an independent anti-jamming and anti-spoofing version with 4 elements, 4 channels, BDS B1 and GPS L1. Those facts support an initial signal/configuration screen; they do not specify an IMU, an inertial navigation solution, a 36-second outage accuracy or compatibility with the systems cited above.
If the covered passage is the only unmet condition and there is no established interference requirement, an anti-jamming product is not, by itself, the missing outage-navigation function. If the route also has interference exposure, keep the mitigation requirement alongside the outage requirement rather than deleting one because the other is present.
For the proposed combination, identify who delivers the navigation output to the controller and which part of the offer covers each operating segment. A missing public field remains unknown, not proof that a feature is unsupported. The vehicle-platform guide covers the existing receiver and installation screen; the receiver-compatibility guide covers the interface boundary. Neither replaces evidence for the combined solution.
Make the scope clear in the enquiry
State whether you need interference mitigation, navigation through a bounded GNSS outage, or both. If an INS is already installed, identify it as an existing system—not as a capability you assume is included in an antenna quotation. This helps the supplier distinguish the ResiNav product request from additional navigation-system work.
Compare mitigation products Discuss the ResiNav product scope