An “anti-jamming antenna” and an “anti-jamming terminal” are not interchangeable procurement descriptions. Before comparing products, identify where interference mitigation sits, what signal leaves that boundary, and which receiver and platform interfaces remain your responsibility. Separate the physical integration boundary from the suppression method: a fixed reception pattern and an adaptive null-forming system are different functions.
Is a GNSS smart antenna the same purchase as an anti-jamming terminal?
Not necessarily: “smart antenna” describes an integrated product form in the commercial ranges cited here; “anti-jamming” describes a protection function. Establish whether the offered item includes a GNSS receiver, then compare the protection function separately. These are two selection conditions, not mutually exclusive product categories.
NovAtel’s SMART antenna range combines a GNSS receiver and antenna in one enclosure. Septentrio’s smart-antenna range likewise offers receiver-and-antenna units, with GNSS-only and GNSS/INS options. By contrast, an antenna feeding a separate GNSS receiver supplies received radio signals rather than computing the position solution. An active amplifier does not, by itself, make that antenna a receiver.
- Replacing the antenna while keeping the receiver: compare antenna products for the existing receiver’s signal and RF-input requirements. A smart-antenna offer containing another receiver changes the equipment scope; it is not automatically an antenna-input replacement.
- Buying a unit that supplies navigation data: shortlist receiver-inclusive products with the required data output. Compare any GNSS/INS option as an additional function, not as something included in every smart antenna. Do not add a separate receiver merely because the product name contains “antenna”.
- Adding protection to an installed receiver: shortlist the documented protection function and RF path. A receiver-inclusive product is relevant only if its documented output meets that purchase requirement; a PVT statement alone does not establish the RF connection.
Check the exact item, not only the category heading: Septentrio also links AntaRx-AUX, an auxiliary antenna, from its smart-antenna range. That accessory is a different purchase from the receiver-inclusive unit.
For navigation data with a published combined anti-jamming and anti-spoofing configuration, review RN2501-AJS-4CH-DPA: its current configuration provides PVT through HDMI without a separate GNSS receiver for those outputs, and its public signal record lists BDS B1 and GPS L1. ResiNav identifies it as a terminal, not as a renamed smart antenna or an equivalent to the cited products. For an existing receiver’s protection path, continue with the architecture comparison below and the published model records.
Draw the signal path before comparing enclosures
Start with the existing receiver and navigation chain: sky view, antenna or array, any external RF electronics, receiver, platform controller, and the status or navigation output consumed by the application. Mark which components are already fixed and which may change. A buyer replacing only an antenna has a different integration problem from a buyer defining a new receiver-and-terminal chain.
“Anti-jamming” covers different architectures. For example, NovAtel documents a separate electronics-and-CRPA arrangement, while Septentrio documents receiver-side interference monitoring and mitigation. An in-line device and an integrated terminal create different boundaries again. These are industry examples, not ResiNav capabilities; use each ResiNav model’s own record to establish its role.
Compare the integration boundary, not the label
| Architecture under review | What the buyer must locate | Question before a shortlist |
|---|---|---|
| Antenna-focused path | Antenna output, cable, receiver input and any required external electronics. | Does the exact antenna record describe a stand-alone function, or does it require another module for mitigation? |
| Array plus separate electronics | Array-to-electronics interface, electronics-to-receiver output, power and mounting split. | Are the array and electronics approved as one specified configuration for the intended receiver? |
| In-line RF device | Its position in the existing RF chain, input/output requirements, supply and status path. | Can the current receiver path be retained under documented conditions, or is that still unverified? |
| Integrated terminal | The functions inside the offered unit and the exact RF, power, data and control outputs. | Which platform interfaces remain to be designed even if the terminal is supplied as one item? |
| Receiver-side mitigation | Receiver model, firmware, monitoring outputs and the upstream antenna path. | Which functions are actually part of the receiver, and what external protection is still required? |
These are architecture categories, not a performance ranking. Check actual ResiNav model availability in the product catalogue.
Not by itself. Digital processing inside an anti-jamming unit does not tell you whether its connection to the receiver is RF or digital data. Nor does an RF connection establish that every advertised operating mode is available with that receiver.
NovAtel’s GAJT-710ML product page describes digital beamforming algorithms and a standard RF output for legacy and modern GPS receivers. This is a concrete example of digital processing with an RF receiver boundary—not proof that a ResiNav configuration fits the same receivers.
A different dependency appears in BAE Systems’ DIGAR announcement: it describes software that enabled beamforming with Trimble receivers in addition to BAE Systems’ own receivers. That named integration should not be read as approval for every receiver. These examples also do not mean that all beamforming requires receiver cooperation; compare the function and interface documented for the particular offer.
| Your purchase requirement | Keep on the shortlist | An incomplete answer |
|---|---|---|
| Retain the installed receiver and add a documented GNSS RF-protection path. | An offer that identifies the protected RF output and its applicable receiver-input conditions. Do not require receiver replacement solely because the processing is described as digital. | A “digital anti-jam” label without a defined output or installation boundary. |
| Obtain a feature that the supplier documents for a particular receiver/electronics combination. | The identified equipment pairing, supported configuration and any required integration software included in the scope. If the installed receiver is outside that documented combination, keep the feature unconfirmed or compare a supported alternative. | A generic RF-output statement presented as evidence that the named cooperative feature will work. |
The decision is about preserving the required function, not ranking RF and digital connections. An RF-only offer can address an RF-feed requirement yet leave a receiver-dependent feature unanswered. Conversely, buying a replacement receiver is unnecessary merely to satisfy a processing label when the documented function uses the existing RF input.
For ResiNav, start with the exact model record and its published output rather than assigning it either manufacturer’s architecture. For example, the RN2501-AJS-4CH-DPA product page identifies its confirmed PVT configuration; that statement does not establish a DIGAR-style receiver collaboration interface. For an existing receiver’s RF path, use the receiver compatibility guide to compare the selected model’s documented boundary. Missing information is unconfirmed, not proof of non-support. You can start an enquiry with the receiver and required function already known.
Shortlist the suppression method as well as the enclosure
A fixed low-elevation reception pattern and an adaptive null-forming system are not the same purchase. The first reduces sensitivity in a designed angular region. The second changes its reception pattern in response to interference. An enclosure labelled “anti-jamming antenna” does not tell you which function is included.
Calian’s AJ977XF white paper describes a low-elevation null zone and distinguishes that design from dynamically nulling CRPAs. Helix Geospace’s Horizon Nulling Antenna is another published example of a designed low-elevation pattern. By contrast, NovAtel describes GAJT adaptive digital nulling as changing the pattern to reduce gain toward interference. These examples establish different product approaches, not equivalent performance or features of a ResiNav model.
- Consider a fixed-pattern candidate when the required angular coverage is defined. A documented low-elevation attenuation region can be relevant to an installation whose interference exposure falls in that region. Compare the installed orientation and the useful satellite view with the published pattern. Do not treat a horizon-specific claim as protection from every arrival direction. “Fixed pattern” also does not mean “needs no power”: the offered antenna may contain an active amplifier.
- Require an adaptive configuration when changing the rejection pattern is part of the purchase requirement. If the requirement explicitly calls for nulls that respond to changing interference directions, a fixed-pattern statement alone is not a match. The shortlist must identify the array and processing electronics together, whether supplied in one enclosure or separately. Buying an array without the required processing does not buy the complete adaptive function.
- Keep an unclassified offer unresolved rather than ranking it. An element count, enclosure photograph or suppression figure does not establish how a pattern changes. If this distinction determines the purchase, the offer needs to identify the implemented method; otherwise it cannot yet be compared on that requirement. Missing information is not proof that the capability is absent.
Check the satellite-view cost of a fixed horizon-rejection pattern
A fixed pattern that attenuates signals near the horizon can attenuate wanted satellites in that same angular region. Safran says its own horizon-rejecting timing antenna reduces the number of satellites the receiver sees. That is a tradeoff documented for Safran’s design, not a measured pattern or performance claim for a ResiNav model.
Fixed-site timing: Keep a horizon-rejection candidate on the shortlist only if the actual receiver can acquire and maintain the required timing reference with the remaining sky view, and the interference direction matches the documented rejection region. Safran’s SecureSync manual illustrates different initial-survey and subsequent tracking requirements; do not assume that receiver’s operating mode applies to another.
Positioning, RTK or a moving platform: Do not select a horizon-rejection pattern solely because it has an anti-jam label. Position solutions depend on usable satellites and their geometry; NovAtel’s RTK documentation explains that fewer or poorly distributed satellites raise DOP. If the installed pattern removes directions needed by the intended receiver and route, exclude that fixed-pattern offer from the configuration shortlist and compare a different documented approach. This does not make an adaptive array automatically compatible or superior.
Purchase gate: Compare the candidate’s published angular pattern with the receiver’s satellites actually used, geometry and solution continuity at the intended mounting location. Check both the ordinary sky view and the relevant interference condition. A suppression figure by itself cannot show whether useful reception has been sacrificed. If the pattern or receiver evidence is unavailable, suitability remains unconfirmed rather than proven absent.
For ResiNav, use the model records below and the public English datasheets to establish documented configuration facts. Do not assign a model the adaptive behavior, pattern shape, power arrangement or receiver compatibility of these industry examples.
Four questions that eliminate a false match
1. Which signals must reach the receiver?
List the required constellations and bands precisely, then compare them with the exact product record. “GNSS” alone does not establish band coverage, and a frequency shown for an RF output should not be read as proof of every desired received signal. Check whether your receiver expects an RF feed, processed navigation data, status messages, or a combination. If the connector and cable details are not published for the exact configuration, mark them open.
2. What can the platform supply and accommodate?
Record mounting area, sky view, cable run, service access, power budget, bonding approach and nearby radios or switching electronics. Then define whether the weight allowance applies to the complete GNSS installation or only the hardware being added. Those are different comparison boundaries when an existing receiver is retained.
Compare the selected assembly, not its lightest box. A separate-electronics offer needs the selected antenna or array in the mass and space comparison as well as the processing unit. Include the added mounting parts and cables; include a new receiver if that is part of the selected installation. A processor-only figure is not the weight of this assembly.
A manufacturer example makes the difference explicit: NovAtel’s GAJT-AE3 page lists 714 g for its rail-mount electronics variant and 964 g for the paired Antcom 8NF array. Adding those two published entries gives 1,678 g before any other installation items. This is a calculation from that manufacturer’s records, not a measured installed total or a comparison of anti-jamming performance. The 714 g entry alone cannot represent that two-component choice.
Check the antenna layout as well as the enclosure dimensions. infiniDome’s GPSdome2 datasheet, page 1 describes two to four external antennas and an optimal arrangement with more than 10 cm separation. The processing-box dimensions on page 2 do not describe that distributed footprint. This is a recommendation for its product, not a universal minimum spacing or a ResiNav installation rule. Compare the selected antenna locations, cable routes and access with the platform drawing.
Use the same boundary to accept or exclude an offer. If the applicable documented masses of the required components already exceed the allowance, that configuration does not pass the documented mass screen. If installation items have no stated mass, do not count them as zero or declare the assembly compliant. Conversely, a published upper weight limit above the allowance does not prove that actual mass exceeds it; the upper bound alone leaves the required fit unestablished.
For a compact GPS L1/BDS B1 product-body screen, RN-S65-4CH-SNB publishes 65 × 65 × 21 mm and weight ≤130 g. Those entries can keep its product body on a shortlist; they do not approve an installed mass, mounting kit or receiver match. Use the catalogue if the signal set or product role differs, then the chosen model’s enquiry route with the budget boundary stated. A compact body and a complete installation are separate decisions, not interchangeable quotations.
3. Where does status become a system decision?
Receiving GNSS signals is not the same as having active anti-jamming protection. When an offer includes a bypass mode, distinguish ordinary RF passage, active mitigation and operation after loss of device power. A standby bypass description does not, by itself, establish a power-off path or uninterrupted navigation.
A concrete manufacturer example is infiniDome’s Aura Integration Manual v1.0.3, printed page 19 (PDF page 21). It describes a quiet-condition bypass from ANT1 to OUT without processing, and a separate active mode using the antennas for null steering. Antenna-power routing changes between those modes. The manual also states that a disconnected or faulty ANT2 detection path leaves protection inactive in bypass. These are Aura-specific behaviors, not ResiNav features or instructions for another product.
| What the offer establishes | What the buyer can decide | What remains a different deliverable |
|---|---|---|
| A documented bypass mode while the unit is operating | Whether its ordinary RF route and antenna-power arrangement suit the intended receiver path. | Active mitigation in that mode, or RF continuity when the unit loses power. |
| A documented active-protection mode | Which mitigation function and operating conditions the quoted configuration addresses. | A power-off bypass, an independent navigation backup or a platform fallback function. |
| An explicit power-off RF-path specification | Whether the specified RF route remains available under the stated power condition. | Valid receiver navigation under interference, and the controller’s decision to use that output. |
Hypothetical quotation comparison: a buyer requires an existing receiver to retain an RF feed when the added protection unit is switched off. Offer A says only “automatic bypass when no interference is detected.” Offer B explicitly documents the unpowered RF route, its antenna supply and its applicable receiver-input conditions. A leaves the power-off requirement unanswered; B addresses that part of the order scope. B is not automatically a compatible installation or proof of navigation continuity. If the buyer instead needs only quiet-condition bypass while powered, the extra requirement in B may not be needed.
For a ResiNav configuration, an RF output, PVT output or element count does not establish either bypass behavior or power-loss operation. Keep those functions unconfirmed unless the selected configuration is explicitly documented. The vehicle application guide covers the separate controller and fallback decision. You can begin an enquiry with the output and operating condition already known; detailed confirmation can follow during quotation.
4. What is the evidence for this exact configuration?
Ask for the identified model, document revision, interface drawing and test conditions. Evidence from a different device or receiver does not validate this proposal. Specify anti-spoofing separately; a jamming claim does not establish spoofing protection.
Use the published ResiNav family for model screening
ResiNav currently publishes anti-jamming terminals and separate anti-jamming-and-anti-spoofing product versions. For example, the RN2501-AJS-4CH-DPA record identifies a 4-element, 4-channel version for BDS B1 and GPS L1; the RN2512-AJS-16CH-DPA record identifies a different 16-element, 16-channel version for those published bands. Those figures describe catalogue records only. More elements do not automatically mean a better choice for your receiver, installation or interference environment.
If your project instead asks for an unlisted form factor or a different interface boundary, describe the requirement through the Custom OEM integration guide. Do not assume the published model can be modified or retrofitted without a separate engineering response.
Turn the architecture question into a supplier conversation
Send a short system diagram or description showing the antenna location, current receiver model, required bands, available power and space, expected output and the purchasing stage. State whether you seek a published configuration, an evaluation unit or an OEM feasibility discussion. Ask the supplier to answer with the proposed configuration identity, the included components, the remaining platform interfaces and a list of unresolved items. The RFQ project brief provides a copyable format; this page answers the earlier question of which architecture belongs in that brief.
Frequently asked questions
Is one category always better than the other?
No. The right architecture depends on verified product information, receiver compatibility, platform interfaces, installation conditions and project requirements.
Can a terminal be treated as a complete project solution?
No. Platform interfaces, installation, receiver integration and the overall navigation workflow still need engineering confirmation.
What should be shared before comparing options?
Share the platform role, existing receiver information, requested bands, interfaces, mounting conditions, quantity and timing.
NEXT STEP
Turn available platform information into an engineering review.
Use the Technology centre to frame the discussion, review relevant application scenarios, then send the available platform and receiver details for confirmation.