Anti-Jamming

How to Choose CRPA Element Count for Drones

Stan Zhu·May 10, 2026Updated Oct 27, 2026·4 min read
Conceptual civilian inspection drone carrying a circular multi-element GNSS array; not a product drawing.

Choosing CRPA element count for a civilian mapping or inspection drone requires more than counting potential interferers. Element count describes part of an adaptive reception system. It does not specify its supported bands, suppression performance, processor compatibility or ability to preserve a valid RTK solution.

The useful purchasing question is: which complete array-and-processing configuration meets the aircraft’s measured operating problem and acceptance criteria? Establish that evidence before choosing a larger array.

Start the CRPA element-count decision with a problem record

Record where positioning fails, the receiver and firmware involved, the correction source, tracked signals and aircraft operating state. Separate blocked sky, stale corrections and onboard electromagnetic noise from evidence of external RF interference.

If the problem coincides with a camera, telemetry radio or power converter turning on, investigate that coupling first. A larger array is not a substitute for a clean RF installation. If the evidence instead shows recurring external interference, define the affected signals, observed duration and operational consequences without guessing the source count from a map or a single receiver alarm.

The high-precision GNSS antenna buyer’s guide establishes the signal and measurement requirements behind a shortlist. This article addresses a more specific decision: comparing candidate configurations after an adaptive architecture is justified.

Why there is no universal element-to-interferer table

Array processing combines channel signals using amplitude and phase relationships. Additional channels can provide more freedom to shape a response, but some of that freedom is needed to preserve desired signals or meet other constraints. Source direction, waveform, bandwidth and channel quality also affect the outcome.

Simple expressions such as N minus one describe particular idealized processing assumptions. They are not a guaranteed count of sources rejected by any installed N-element GNSS product. Several signals may share a direction; one broadband source may create a more difficult processing problem than several well-separated narrowband sources.

Nor does adding elements guarantee a particular carrier-to-noise gain or recovery time. A GNSS receiver tracks satellites over many directions, while an array’s response depends on its geometry and processing mode. Ask for measured performance with the desired satellite signals present, rather than applying a coherent gain formula as an RTK prediction.

Compare complete candidate systems

Request a configuration-specific answer to each row below. If the supplier changes processor, firmware, cable set or supported bands between options, record that change instead of attributing every difference to element count.

Procurement question Evidence needed
Which signals pass through the system? Supported bands and processing modes for the quoted hardware
How does it connect to the RTK receiver? RF output or multichannel interface specification and compatibility statement
What does the aircraft carry? Complete mass, power, dimensions, harness and thermal requirements
How is adaptation maintained? Calibration procedure, channel monitoring and revalidation conditions
What performance has been demonstrated? Scenario, source geometry, waveform, power definitions and position/tracking results

A higher-count array can still be the wrong purchase if it does not support a required signal or the receiver cannot accept its output. Confirm those interfaces before discussing suppression margins.

Aperture and installation constrain the choice

Element spacing and array diameter belong to a specific design. A generic half-wavelength rule is not a universal mounting template. Use the manufacturer’s drawings, keep-outs and installation requirements; include nearby carbon structures, radios, landing gear and payload movement in the review.

The RF paths also form part of the design. Preserve channel mapping and the specified cable set. Equal cable lengths alone do not establish phase and delay matching across bands and temperature. Ask which parts are calibrated together and whether a field replacement invalidates that calibration.

On the aircraft, check center of gravity, structural stiffness, vibration, heat and power transitions. More processing channels can affect these budgets, but the relationship is product-specific. Avoid choosing a count from aircraft takeoff mass alone: two aircraft with similar mass can have very different mounting and electrical capacity.

Require tests that can distinguish the candidates

Spirent’s CRPA testing overview distinguishes conducted testing from over-the-air testing. The former can exercise the electronics with controlled channel inputs; the latter can include the physical array response. State which evidence each candidate supplies.

For a fair comparison, define a quiet baseline and contained laboratory scenarios representing the measured problem. Keep receiver settings, corrections and evaluation metrics consistent. Vary source geometry and relevant operating conditions instead of testing only a favorable direction.

Evaluate tracking continuity, cycle slips, fixed/float states, recovery behavior, processor alarms and position errors against an independent reference. A system that reports “fixed” more often but produces unacceptable errors has not met the goal.

Set pass criteria from the survey or inspection task. Do not copy an arbitrary fixed percentage or re-lock time from another airframe. If both candidates pass, compare the complete installation and maintenance cost. If neither passes, a higher count is only one possible next investigation; calibration, processing and front-end overload may be the limiting factors.

Keep spoofing and calibration questions separate

Spatial processing can contribute to certain false-signal checks or mitigation, but count alone does not establish anti-spoofing capability. Ask what the exact receiver and processor detect, what they report and how the aircraft responds. Authentication and independent sensor comparisons have their own scope and requirements.

The calibration file also needs a purpose. A phase-center model for survey observations is different from channel or array-response data used by adaptive processing. Our GNSS antenna calibration guide explains the former; request the latter from the array-system supplier with the quoted configuration.

When requesting options, give GNSource your receiver interfaces, measured interference evidence and aircraft constraints. Ask for a compatible configuration and its verification plan before committing to an element count.

Need help choosing the right antenna?

Tell us your platform, bands, environment, and accuracy target — our engineers respond within 24 hours.

Talk to our engineers