A dual-antenna GNSS heading system and an anti-jamming array solve different problems. The first uses measurements from spatially separated antennas to determine orientation. The second uses an array and associated processing to mitigate interference. A published count of four, eight or sixteen array elements does not establish a heading output.
If a stationary machine must know which way it is pointing, start with a documented heading solution. If its satellite reception must remain usable in a specified interference environment, evaluate a mitigation solution. If both are required, neither category label is enough to buy the complete system.
Heading, direction of travel and interference resistance are different outputs
Course over ground describes travel direction, not necessarily the direction the platform faces. A vehicle reversing or moving sideways is a simple reason to keep those concepts separate. A stationary platform also cannot obtain a useful direction of travel merely by comparing its unchanged positions.
A suitable dual-antenna heading solution uses the relative antenna locations rather than relying on forward motion. Septentrio’s mosaic-H page is a concrete example: it describes heading in static and dynamic operation and specifies results against antenna separation. These are features of that receiver, not evidence that a ResiNav array provides them.
NovAtel’s ALIGN documentation separately identifies heading and the baseline between two antennas; its configuration guidance relates the antenna baseline to the vehicle through an offset. The procurement implication is to buy a defined orientation output, not just two antenna connectors.
Compare the system you need, not the number of antenna elements
| Decision | Dual-antenna heading solution | Anti-jamming array or terminal |
|---|---|---|
| Primary purpose | Determine orientation from a documented antenna baseline and receiver processing. | Mitigate interference affecting the supported GNSS reception path. |
| Meaningful purchase evidence | Heading output and status, conditions of operation, antenna arrangement and baseline-dependent specification. | Exact signal configuration, product boundary and applicable interference-mitigation specification. |
| Physical layout | Two identified antenna locations with a defined relationship to the platform. | The published array assembly and installation requirements for the selected configuration. |
| What antenna count does not prove | Two arbitrary antennas or receivers do not automatically form a supported heading system. | Multiple elements do not automatically expose separate receiver inputs or supply a heading message. |
| Combined requirement | The heading function and both required observation paths must remain supported. | The proposed mitigation arrangement must be assessed for that heading architecture, not assumed interchangeable. |
Some commercial receivers combine heading and receiver-level interference mitigation. Others use separate equipment. NovAtel’s mitigation overview distinguishes receiver algorithms from an antenna-and-electronics mitigation layer. The availability of either approach elsewhere does not establish a named receiver’s compatibility with a ResiNav product.
Example: a stationary vehicle needs heading before it moves
Hypothetical buying scenario: a vehicle controller requires body heading while stationary. The buyer has found an anti-jamming unit with eight array elements and assumes those elements replace a dual-antenna heading installation.
That assumption is not supported by the element count. The purchase needs a documented heading-capable receiver or navigation assembly, its specified antenna arrangement, and an output the controller can use. If interference mitigation is also required, it is a separate function to include in the architecture and offer.
The buyer should therefore reject an offer as incomplete for the stated heading requirement if it identifies only an array and gives no heading solution. This does not declare the array defective or incapable of mitigation. It identifies the missing deliverable. Likewise, a heading receiver without a documented mitigation scope is not automatically a complete anti-jamming solution.
Make the purchase list reflect the heading geometry
For a dual-antenna heading purchase, distinguish the receiver or processing assembly, the two specified antenna installations, their RF paths, and the means of delivering heading and validity to the controller. Confirm which of these are included in the offer. A receiver module and a ready-to-install assembly are different purchase scopes.
Keep the antenna baseline and the platform’s forward direction distinct. Antennas mounted across a vehicle rather than along it do not define the same axis; the applicable receiver setup must account for the installation. Follow the selected receiver’s documented configuration, not a universal offset or minimum spacing invented for every product.
Do not use a single antenna split into two RF inputs as evidence of a spatial baseline. Both feeds originate at the same antenna location. A splitter may serve other distribution purposes, but it does not create the separated observations described by a dual-antenna heading architecture.
Use ResiNav records for the mitigation portion
Start with the published anti-jamming product catalogue when comparing the mitigation function. The RN2511-16A-SNB and RN-8AT-FULL-KGR-34V records identify different published array configurations. Their element counts are not heading specifications, port maps or a ranking of orientation accuracy.
The public record must explicitly establish a required function before it can be treated as supplied. If heading behavior or the handling of two receiver paths is not stated for a proposed configuration, leave that question open. Do not convert missing information into either a compatibility promise or a claim of non-support.
For a broader distinction between antenna assemblies, electronics and terminals, use the architecture comparison. The element and channel guide explains the separate counting terms; neither count replaces a documented heading output.
Specify orientation and mitigation separately
Ask for a quote that names the heading solution and the mitigation configuration as distinct functions, even when proposed in one assembly. That makes a missing receiver, second antenna installation or unsupported output visible before ordering.
Explore mitigation configurationsAsk about the proposed GNSS arrangement