When comparing GNSS array-based protection, separate two functions: reducing reception towards an interferer and forming increased response towards wanted satellite signals. A system may combine them, but a generic CRPA or anti-jamming label does not establish that both are included. Buy against the function your requirement actually needs, rather than treating every adaptive reception pattern as the same feature.
This matters to integrators comparing a documented interference-suppression solution with a configuration that also explicitly provides satellite-directed beamforming. The additional function can change the shortlist; it is not established by the number of elements or a suppression figure alone.
A null and a wanted-direction beam have different jobs
Null steering reduces the receiving response in a selected direction so that an interfering signal contributes less to the combined signal. Satellite-directed beamforming instead shapes the response towards wanted GNSS signals. These descriptions concern reception, not transmitting a counter-jamming signal.
Keysight's CRPA technical discussion, originally published by Spirent, describes both rejecting an interference direction and directing beams towards genuine signals. They are different objectives within adaptive antenna processing, not proof that every commercial implementation delivers the same combination.
Terminology needs care. A supplier may use “beamforming” broadly for spatial processing, including the creation of nulls. In this comparison, satellite-directed beamforming means the specifically stated wanted-signal function. If an offer says only “beamforming,” its description must reveal which objective is actually included before you treat it as the additional feature.
The CRPA category does not settle the function
Helix Geospace's CRPA buyer's guide describes interference rejection and qualifies satellite-directed beamforming as a feature in some cases. Keep these two requirements separate when reading a supplier's configuration description.
The same caution applies to the item being quoted. Antcom's CRPA product category describes its antennas working with compatible antenna electronics and with null-forming and beamforming systems. An antenna's suitability for use with such a system is not, by itself, a quotation for the electronics, processing configuration and complete working function.
Compare what the complete offered configuration does. A compatible array statement can help identify an integration component. It cannot be substituted for a system-level statement that the selected configuration supplies the function you intend to buy.
Compare functions using the same scope
Keep a suppression result attached to the configuration and conditions that produced it. It describes a rejection result, not a substitute measurement of wanted-direction gain. Conversely, a stated wanted-direction feature does not remove the need for a matching interference-protection requirement.
Element counts answer another question: the spatial constraints a design may support. The element and channel count guide explains that capacity screen. Use it separately: a larger count is not evidence that the quotation includes a particular satellite-directed function.
Two hypothetical offers, two different decisions
Suppose an integrator is retaining a receiver and has defined a reception-protection requirement. Offer A documents adaptive interference rejection in its quoted configuration. Offer B documents that function and separately describes satellite-directed beamforming. Both still need to match the receiving path and the rest of the buyer's requirements.
If the requirement is interference rejection, the additional function in B is not automatically mandatory. A should not be rejected solely for lacking an extra feature that the application has not required. This does not rank A and B by price or performance; it prevents a broader feature label from silently changing the order.
Now suppose the system requirement explicitly calls for satellite-directed beams. A's rejection documentation no longer answers that requirement. Keep configurations that document the wanted-direction function, or treat an offer with unspecified functionality as incomplete for that requirement. Do not assume the missing feature can be added after purchase unless the supplier actually documents an available configuration.
The examples are hypothetical. No particular ResiNav or third-party model is assigned to A or B. The change in selection comes from the required function, not an invented test result, satellite count or operating threshold.
Make the function an orderable configuration, not a slogan
For a complete-system offer, the meaningful line is the selected configuration with its stated reception function and included processing. For an antenna-component offer, the meaningful line is the named compatible electronics configuration and which items are actually included. These are different quotation scopes, even when both carry the same CRPA category label.
A useful functional statement might be “adaptive rejection in the offered configuration; no separately documented satellite-directed function in this offer.” That records the evidence available without claiming that the underlying product cannot provide another function. If the offer expressly includes both, keep the functions separately described so that a later configuration change does not obscure what was purchased.
For buyers retaining a receiver, the receiver interface guide addresses the separate RF and data-path questions. A correctly understood adaptive function does not prove receiver compatibility, nor does a connector settle the algorithm supplied.
Where the ResiNav catalogue fits
Use this distinction to interpret the function in a supplier's offer, then compare the published reception-protection products in the ResiNav catalogue. Continue through the relevant model page when its recorded signals, output and product scope match the protection portion you are buying.
ResiNav is an own-brand supplier. For a ResiNav feature or delivery scope, use the particular model's approved record, not the Antcom or Helix category examples above. A generic CRPA description does not establish an orderable ResiNav component or a satellite-directed feature.
The decision is practical: do you need documented interference rejection, a documented wanted-direction function as well, or an integration component for a separately specified processing system? Keep those purchase requirements distinct before comparing quotations under a common anti-jamming label.
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.