ENGINEERING REFERENCE / SURVEYING AND MOBILE MAPPING
A survey receiver can lose usable positioning for more than one reason. Before choosing an anti-jamming product, identify whether the project is seeing interference at the satellite-signal input, blocked sky, a correction-service interruption, or a timing and georeferencing problem elsewhere in the capture chain. Each calls for a different engineering response.
First locate the failure in the positioning chain
Surveying and mobile mapping depend on more than the antenna assembly. The receiver’s observables and solution status, correction delivery, platform time synchronisation, sensor alignment and post-processing procedure all affect whether collected data can be used. A GNSS anti-jamming device addresses only a defined part of that chain: interference affecting supported satellite signals at the RF front end. It does not create satellite visibility, supply missing corrections or establish survey accuracy by itself.
| Evidence from the actual workflow | Review first | Product decision |
|---|---|---|
| Satellite-signal degradation coincides with a measured or suspected RF interferer. | Receiver logs, affected constellation and band, spectrum evidence where available, antenna placement and RF path. | Shortlist only a configuration whose published signal coverage matches the receiver requirement; request interface and test evidence for the exact build. |
| The receiver passes beneath trees, structures or inside a tunnel. | Sky visibility, route transitions, inertial/odometry inputs and the required fallback behaviour. | Do not treat an anti-jamming element count as a remedy for blocked sky. Review the complete navigation architecture. |
| RTK or other corrections stop while satellite tracking remains available. | Correction source, cellular or radio link, age of corrections, receiver status and fallback rules. | Resolve the correction path before attributing the incident to satellite-signal interference. |
| Positions exist, but the mapped features or point cloud do not align. | Time stamps, lever arms, antenna reference point and calibration, sensor alignment and processing records. | Validate the capture and georeferencing chain; anti-jamming alone cannot establish the cause. |
These are triage paths, not automatic diagnoses. A replacement antenna can change the measurement reference even when reception remains available.
When the required output is a camera, vehicle or work point rather than the antenna reference, see how lever-arm compensation combines geometry, attitude and event timing.
Can you retain the calibration profile after an antenna or radome change?
Match the documented combination, not just the antenna’s commercial name. The NGS calibration catalogue identifies antenna types by antenna code plus radome code. A radome is the antenna cover; NONE denotes no radome, not an arbitrary cover. Compare the installed pair with the calibration entry and the signals it covers. Also keep the calibration reference system consistent with the orbits and reference-station coordinates used in processing. A familiar model name or an unchanged connector is not enough to select the old profile.
Height and phase corrections answer different questions. The antenna reference point (ARP) is a defined physical point on the antenna, identified in its documentation. The NGS explanation of phase-centre calibration distinguishes that point from the electrical phase centre: the phase-centre offset (PCO) locates the average reception reference relative to the ARP, while phase-centre variations (PCV) describe directional changes. Calibration corrections are not a substitute for the measured relationship between the survey mark and the antenna.
Check the software’s height convention before entering a value. NovAtel Waypoint, for example, supports heights measured to the ARP or phase centre, or calculated from a slant measurement. Its antenna model reduces the phase-centre position to the ARP. Do not add the same offset again by hand when that reduction is already applied. This is a Waypoint processing example, not a universal instruction for every receiver or survey package.
A changed radome needs a new identity check. The NGS antenna-calibration FAQ explains that the installed cover can change phase-centre offsets and variations. It recommends the exact antenna-plus-radome calibration. If the exact pair is absent, NGS describes the same antenna with NONE as a fallback—not as proof that the fitted cover has no effect or that a project’s tolerance is met. For a precision-critical purchase, availability of the matching pair can therefore change the shortlist.
In Waypoint, a base-station RINEX header can supply antenna and radome names for automatic profile selection; inspect the loaded profile rather than assuming the header is correct. Its Generic profile applies no antenna corrections and references the result to the L1 phase centre as best estimated. Generic is not a calibrated substitute for an unknown combination. Other software must be checked against its own documented behavior.
Illustrative replacement decision: option A retains the documented antenna and radome pair but changes the mount height. The matching calibration record may remain relevant, while the height and sensor-geometry record must be updated. Option B retains the antenna but substitutes another radome: compare the new pair with the available calibration entry, or explicitly qualify a fallback rather than declaring equivalence from fit alone. Changing the antenna, covered signals or processing reference system likewise calls for a fresh model check.
A calibration entry is not acceptance of the complete mapping system. Retain checks of the installed receiver, processing, timing and sensor alignment against the project’s criteria. Use the configuration-change guide to separate reusable evidence from affected checks, and the multipath-versus-RF-interference guide when deciding which reception problem to address. This auxiliary survey guidance does not establish a ResiNav calibration file or service; an ordinary survey-antenna record is not evidence for an anti-jamming array or processing terminal.
Where a documented anti-jamming configuration might fit
Start with the survey receiver’s required constellations and bands, then compare them with the published record for the exact ResiNav model. For example, the public RN2501-AJS-4CH-DPA record lists BDS B1 and GPS L1 for its four-element, four-channel anti-jamming and anti-spoofing version. This is a reason to ask whether that published configuration fits a B1/L1 receiver path; it is not a claim that RN2501 provides every signal, correction method or observable a particular survey workflow needs. A model’s element or channel count is not a ranking of positioning accuracy or interference resilience.
If the intended workflow requires bands or observables not stated in the product record, keep the answer unconfirmed until the supplier confirms the exact configuration. A missing public statement does not establish support and does not establish confirmed non-support. This distinction matters for workflows with specific requirements: for instance, NOAA’s OPUS guidance specifies dual-frequency L1/L2 observables for that particular static-processing service. Such a requirement should be checked directly, not assumed from an anti-jamming label. NGS OPUS requirements.
The related vehicle integration guide addresses platform-level interfaces and fallback. For a wider comparison of published models, use the product catalogue rather than extrapolating from a single product.
Evidence to carry into an engineering review
A useful supplier discussion starts with one real capture sequence, not a request for a generic accuracy promise. Record the route or site, receiver model and firmware, required signals and observables, antenna and RF installation, correction source, relevant receiver status logs, sensor and time interfaces, and the failure transition the team wants to test. Separate measured behaviour from an expectation or a suspected cause.
| Bring this evidence | Question it helps answer |
|---|---|
| Receiver’s required bands and observable outputs | Can the exact published product configuration be considered without removing a required receiver input? |
| Antenna location, cable and RF-chain drawing | What mechanical, power, connector and RF constraints must be checked for installation? |
| Tracking, solution and correction-status logs from the same event | Did satellite reception, correction delivery or both fail, and when? |
| Time synchronisation, sensor offsets and quality criteria | How will the integrated system decide whether mapped output is valid after a disturbance? |
Ask the supplier which interface, installation and acceptance evidence can be supplied for that configuration. The receiver evaluation guide can help frame recovery testing; the engineering RFQ guide covers the broader purchase brief. Neither replaces a project-specific survey validation plan.
Frequently asked questions
Does this page promise survey accuracy?
No. It describes the information required for engineering review and does not make an accuracy or performance guarantee.
Why include the data-capture workflow?
It helps clarify receiver outputs, interfaces and documentation needs across the complete integration boundary.
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.