GNSS anti-jamming and RTK are not substitutes. Anti-jamming addresses interference affecting satellite reception. RTK is a positioning method that uses carrier measurements and correction data to improve the position solution. A system may need both, but purchasing one does not automatically provide the other.
For a buyer, the useful first question is which missing function the purchase must add: better positioning accuracy under suitable reception conditions, more resilient satellite reception, or both. A correction subscription cannot replace an interference-mitigation device, and an anti-jamming terminal is not automatically an RTK receiver or correction service.
Two paths meet inside the positioning system
Satellite-signal path
GNSS antenna and any compatible RF mitigation equipment → receiver measurements
Correction-data path
Local base or network service → supported communication link → RTK-capable receiver processing
Result
The receiver produces position and status outputs for the application.
Conceptual separation of functions, not a wiring diagram or a confirmed ResiNav configuration. Receiver-integrated mitigation is another possible implementation.
ESA’s RTK overview describes the base, rover and real-time communication channel. NovAtel’s correction guide explains how a rover combines its observations with reference information. Neither description makes a particular anti-jamming product RTK-capable.
What belongs in each purchase
| Purchase category | Function being bought | Items to distinguish in the offer | What it does not establish |
|---|---|---|---|
| Anti-jamming antenna, terminal or receiver feature | Mitigation of specified interference within a documented signal and system boundary. | Exact hardware or enabled receiver feature; supported signal path; any separately supplied receiver. | RTK processing, correction access, centimetre-level accuracy or an uninterrupted position under all conditions. |
| RTK-capable GNSS receiver | Processing of suitable GNSS observations and supported correction data into an RTK solution. | Receiver configuration, enabled positioning modes, supported correction input and required antenna system. | An included local base, network subscription, communication service or a particular anti-jamming capability. |
| Local reference station or correction-service access | A source of applicable reference information for the rover. | Base hardware and setup, or service coverage and access terms; correction delivery equipment or connectivity. | Restoration of satellite signals blocked at the rover, or compatibility with every receiver. |
These are functional categories, not necessarily three boxes. One supplier may bundle several functions, while another may quote them separately. Compare what is included before comparing totals. For the specific E6-B versus Internet correction-delivery purchase, see whether Galileo HAS needs an E6 antenna. The supplier proposal comparison guide helps separate hardware and service costs without assuming a price or subscription term.
Choose the category from the requirement, not the symptom alone
If the receiver works but the required position accuracy is not available: first establish the required positioning mode and correction arrangement. An anti-jamming purchase alone does not add RTK processing. Also check that the antenna and RF path support the signals the intended receiver configuration uses.
If usable satellite observations are being lost to interference: evaluate the reception and mitigation path. RTK still depends on usable measurements; correction delivery is not a replacement for them. Septentrio’s AIM+ explanation is an example of receiver-integrated mitigation supporting RTK when sufficient satellite signals remain. That manufacturer’s implementation is not a ResiNav capability or compatibility claim.
If correction delivery has stopped while satellite reception remains usable: address the correction source, delivery path or receiver configuration. Buying a GNSS anti-jamming terminal is not a direct substitute for the missing correction stream. A communications link can have its own problems; keep that question separate from interference at the satellite-signal input.
If a receiver and correction service both list RTCM, compare the correction stream the receiver can actually use before replacing hardware.
A lost RTK fix alone does not diagnose interference. Obstruction, correction availability and other receiver or system conditions can affect the result, and problems can coexist. Use the existing surveying guide or agricultural application guide for context-specific troubleshooting.
For an accepted integer solution, see why RTK Fixed still needs position verification and how reference settings and independent checks change the conclusion.
A purchase example: keep three lines separate
Illustrative case, not a ResiNav quotation: an integrator already owns an RTK-enabled receiver and has access to a correction network. The new requirement is to evaluate interference mitigation at the GNSS input. The initial purchase list is a candidate mitigation configuration plus any confirmed connection and installation items—not automatically another receiver and another correction subscription.
If the integrator instead owns a receiver without the required RTK capability, the list must also address receiver processing. If no suitable correction source is available, it must address that source and delivery path too. Do not mark these items “included” merely because the offer uses the phrase “GNSS system.” This functional split avoids buying the same service twice or omitting a required one.
Where a ResiNav product can enter the comparison
The ResiNav catalogue is a starting point for the interference-mitigation portion of a system. For example, the RN2501-AJS-4CH-DPA record lists BDS B1 and GPS L1 for its published configuration. That fact supports a signal-path screen; it does not establish an RTK mode, a correction subscription or support for other required signals.
If the intended receiver configuration depends on a signal not listed for the candidate, the public record is insufficient to approve that path. Missing information is not proof of non-support, but neither an array count nor an anti-spoofing label fills the gap. Use the model’s public data sheet for the documented configuration and obtain a specific answer for the missing requirement.
Buy the missing function
Shortlist anti-jamming equipment for a defined reception problem; select RTK processing and correction delivery for a defined positioning requirement. Where both are needed, keep their deliverables separate and evaluate the combined system.
Compare anti-jamming productsDiscuss the mitigation part of your system
For a construction site with a shared correction base and several machines, see where to evaluate GNSS RF mitigation and how to count candidate paths.