How to Choose a Counter-UAS System

Technical Guide / Counter-UAS System Selection

How to Choose a Counter-UAS System: RF, Radar, EO, TDOA and Integrated Response

This guide explains how to choose a counter-UAS system by comparing detection technologies, deployment models and authorized response architectures without reducing a site-specific security requirement to one headline range figure.

Published by JIGGS Technologies Last reviewed: August 2026 Professional and authorized-use context

Executive Summary

Start with the protected environment, not the longest published range.

No single sensor solves every detection and identification problem.
RF, radar and EO provide different types of evidence.
TDOA is a multi-node RF localization method, not a substitute for every sensor.
Detection does not determine intent or automatically authorize a response.
Portable, fixed-site and mobile systems require different infrastructure.
Final architecture should follow a site, target and authorization assessment.

01 / Operational Logic

What does a counter-UAS system actually need to do?

A counter-UAS system is better understood as a sequence of decisions than as a single device. The sequence normally begins with sensing, but useful protection also requires classification, localization, verification, operator assessment and a legally authorized response plan.

01

Detect

Recognize a physical target, RF emission or other indicator of possible UAV activity.

02

Classify

Separate likely UAV activity from birds, aircraft, Wi-Fi sources and environmental clutter.

03

Locate

Estimate bearing, position, altitude or track according to the available sensor outputs.

04

Verify

Use visual, protocol-level or correlated sensor data to improve target confidence.

05

Assess

Evaluate behavior, protected-zone rules, authorization and possible effects on nearby systems.

06

Respond

Apply an authorized operational response and continue monitoring the target and site.

Important distinction: Detection confirms that the system has observed an indicator or target. It does not, by itself, determine hostile intent or create legal authority to interfere with an aircraft, radio link or navigation signal.

02 / Detection and Localization Technologies

RF, radar, EO and TDOA solve different parts of the problem.

The correct question is not which technology is universally best. The useful question is which evidence the operator needs, which targets matter, what the environment allows and where one technology must be supported by another.

RF

Radio-frequency detection

RF systems listen for control, telemetry, image-transmission or broadcast signals associated with UAV activity. Depending on protocol support and system design, they may provide an alert, frequency information, signal classification, model identification, electronic fingerprint, bearing or decoded position data.

Where RF is strong

  • Passive monitoring without transmitting detection energy.
  • Early warning when control or data links become active.
  • Protocol, model or fingerprint information when supported.
  • Direction finding or multi-node localization in suitable configurations.

Important limitations

  • Requires detectable RF activity within the monitored spectrum.
  • Unknown protocols or missing library references may reduce identification.
  • Autonomous, radio-silent or alternative-link targets may require radar or EO support.
  • Background RF noise, antenna placement and terrain affect performance.
Portfolio examples

AS207 supports portable RF detection and direction finding. AS201-PC and AS410 represent fixed or wider-band RF monitoring and identification roles.

Explore RF detection systems
RDR

Low-altitude surveillance radar

Radar illuminates the airspace and processes returned energy to detect and track physical targets. A suitable counter-UAS radar can provide range, azimuth, elevation, altitude and speed even when a drone is not transmitting a recognizable control signal.

Where radar is strong

  • Wide-area surveillance and continuous track generation.
  • Detection independent of recognized UAV communication protocols.
  • Useful cueing data for EO, command platforms or response assets.
  • Coverage of autonomous or non-cooperative physical targets.

Important limitations

  • Small UAVs may have a low radar cross section.
  • Birds, ground clutter, buildings and terrain complicate classification.
  • Blind zones, installation height and radar horizon require site planning.
  • A radar track does not by itself establish identity or intent.
Portfolio examples

AS50 and AS120 Radar Detection Equipment support short-range low-altitude surveillance and multi-target tracking roles within an integrated counter-UAS architecture.

Review radar detection equipment
EO

Electro-optical and thermal imaging

EO and infrared systems convert a sensor cue or search sector into visible or thermal imagery. Their central value is confirmation: helping the operator determine whether a detected object is a drone, observe its configuration or payload, track its movement and retain visual evidence.

Where EO and IR are strong

  • Visual confirmation and operator-supported identification.
  • Evidence capture for incident review and reporting.
  • Precision tracking when cued by radar or RF localization.
  • Day and night operation when visible and thermal channels are combined.

Important limitations

  • Range depends on lens, resolution, target size and background contrast.
  • Fog, rain, haze, lighting and thermal conditions affect imagery.
  • Field of view is narrower than broad-area RF or radar surveillance.
  • Often most effective as a confirmation and tracking layer.
Portfolio examples

AS260U/Q combines visible-light and thermal-imaging channels with servo positioning and radar-cued automatic tracking options.

Explore EO and thermal systems
TDOA

Time Difference of Arrival localization

TDOA is not a separate physical sensor in the same sense as radar or EO. It is a localization method that compares when the same RF signal reaches multiple synchronized receiving nodes. From those time differences, the system estimates the position of the transmitting source.

Where TDOA is strong

  • Converts distributed RF reception into a position estimate.
  • Supports passive fixed-area localization without active radar emission.
  • Can complement protocol identification and direction finding.
  • Useful where multiple networked nodes can surround or flank the site.

Important limitations

  • Requires multiple synchronized and networked receiving nodes.
  • Node geometry has a direct effect on localization quality.
  • Multipath, obstruction and RF interference can introduce error.
  • The target must emit a signal that the receiving network can observe.
Portfolio example

AS290 uses four front-end RF positioning detectors and a back-end control platform to support distributed detection, identification, alarm and localization workflows.

Review TDOA and RF localization

03 / Technology Comparison

Compare the information each technology provides.

A useful comparison should focus on output, target dependence and operational role rather than range alone. The table below describes typical roles; final performance remains system- and site-dependent.

Technology Primary output Main strength Main limitation Typical system role
RF Signal alert, identity, fingerprint or bearing Passive and potentially information-rich Depends on detectable and supported RF activity Early warning, identification and direction finding
Radar Range, bearing, altitude, speed and track Observes physical targets without protocol dependence Clutter, small target signature and classification Wide-area surveillance and sensor cueing
EO / IR Visible or thermal imagery and precision track Confirmation, evidence and threat assessment support Weather, visibility, contrast and field of view Identification and target confirmation
TDOA RF emitter position estimate Passive distributed localization Requires synchronized nodes, useful geometry and RF emission Fixed-area localization and tracking support

This comparison describes typical technology behavior and is not a substitute for product-specific testing, site surveys or applicable regulatory review.

04 / Deployment Models

Portable, fixed-site and mobile systems answer different mission needs.

Deployment format changes more than the enclosure. It affects coverage persistence, sensor geometry, network requirements, power, operator workload and how quickly the protected boundary can move.

01 / PORTABLE

Rapid deployment

Handheld, case-based or backpack equipment can support temporary events, checkpoints, patrol teams and rapid on-site screening.

Best when:

Infrastructure is limited and deployment speed matters more than persistent multi-sensor coverage.

02 / FIXED-SITE

Persistent protection

Permanent RF, TDOA, radar and EO nodes can support continuous monitoring, stable sensor geometry and command-platform integration.

Best when:

The protected boundary is known and power, network, mounting and site survey work can be planned.

03 / MOBILE

Changing boundaries

Vehicle-supported or on-the-move architectures can combine sensing, command and response around a mobile asset or field mission.

Best when:

The route, protected asset or operational boundary changes during the task.

05 / Integrated Response

Combine detection, tracking and response around the decision process.

Integration is valuable when it reduces gaps between sensor outputs, improves operator understanding and keeps response activation tied to verified conditions. Integration should not remove the required authorization or operator controls simply because the equipment can exchange data.

01

Portable screening pattern

Portable RF detection provides an alert and direction indication. The operator confirms the context and applies the approved reporting or response procedure.

02

Fixed multi-sensor pattern

RF or TDOA and radar establish early warning and location. EO provides confirmation. A command platform correlates the outputs before an authorized response decision.

03

Integrated detection-response pattern

Detection generates an alarm, software applies identification or whitelist logic, and the operator selects a permitted manual or configured response while monitoring the result.

Portfolio context: AS120 Integrated UAV Detection & Jamming Equipment represents an integrated detection-and-jamming workflow; AS130 combines detection with navigation-response control; AS809W-360 can be configured with radar and spectrum detection plus optional EO and navigation modules; AS333 is positioned as a specialized response layer that benefits from upstream detection and cueing.

06 / Selection by Protected Area

Use the environment to define the starting architecture.

The following examples are starting points, not universal configurations. Each project should be refined against local terrain, surrounding RF use, target profile, infrastructure, rules of engagement and applicable law.

Protected environment Suggested starting point Why Questions to resolve
Temporary event or checkpoint Portable RF detection with operator-led verification Fast setup and limited infrastructure Expected protocols, crowd environment, response authority
Large open perimeter Radar plus RF and EO confirmation Physical target coverage with signal and visual context Radar horizon, mounting height, EO cueing and power
Urban or RF-congested site Radar-led detection with EO and carefully assessed RF support Reduces dependence on a clean RF environment Clutter, multipath, line of sight and false-alarm management
Fixed critical site RF or TDOA, radar, EO and command integration Layered coverage and persistent sensor geometry Site survey, network, redundancy and authorized response plan
Mobile patrol or convoy Vehicle-integrated sensing, command and response Protection boundary changes with the mission Antenna masking, power, vibration and moving-sensor performance
High identification requirement RF protocol information plus EO confirmation Combines identity data with visual evidence Supported models, library maintenance and visibility conditions

07 / Continue the Evaluation

Move from selection logic to the relevant JIGGS system layer.

Use the guide to identify the functions you need, then review the relevant product family or solution architecture. Avoid choosing a response device before defining the detection and operator decision workflow that will support it.

08 / Pre-Purchase Review

Questions to ask before buying a counter-UAS system

A credible proposal should explain not only what the equipment can do, but also the conditions, evidence, maintenance and integration work behind the claim. Use these questions during technical and commercial evaluation.

Which target models and flight modes were tested? Confirm the target type, firmware, protocol and operating behavior used for published results.
Under what environment was range measured? Ask for line-of-sight, antenna height, RF conditions, terrain and target-altitude assumptions.
What are the probability of detection and false-alarm rate? Range alone does not describe detection consistency or operator workload.
How are RF and image libraries maintained? Clarify supported models, update frequency, subscriptions and responsibility for new protocols.
How many targets can be detected and tracked? Confirm simultaneous-target capacity and how performance changes in dense environments.
How are sensor outputs correlated? Review timestamps, track association, map display, operator confirmation and command-platform interfaces.
Which interfaces and integration documents are available? Ask about network architecture, protocols, APIs, data formats and third-party system compatibility.
What does the site need to provide? Confirm power, network, mounting, grounding, weather protection, operator positions and maintenance access.
Which features are standard and which are optional? Separate published base configuration from optional bands, sensors, software and response modules.
Which local permissions apply? Confirm spectrum, aviation, interception, privacy and mitigation authority before active deployment.

09 / Frequently Asked Questions

Counter-UAS system selection questions

What is the best counter-UAS detection technology?
There is no universal best technology. RF can provide passive signal and identity information, radar can detect physical targets independently of recognized control links, EO supports visual confirmation, and TDOA can localize an RF emitter through multiple synchronized nodes. The best choice depends on the target, site and required output.
Can an RF detector find every drone?
No. RF detection depends on observable signals, monitored frequency coverage and supported protocols or signal characteristics. Autonomous, radio-silent, unknown-protocol or alternative-link targets may require radar, EO or other sensing support.
Is TDOA different from RF direction finding?
Yes. Direction finding estimates the bearing of a signal from a receiving location. TDOA compares signal arrival times across multiple synchronized receivers to estimate the transmitter position. They may complement each other, but they require different deployment geometry and infrastructure.
Why combine radar with EO or RF?
Radar can establish a physical track, while EO can provide visual confirmation and RF can add signal or identity context. Correlating independent evidence can improve operator understanding and reduce dependence on the limitations of one sensor type.
Should I choose a portable or fixed-site system?
Portable systems suit temporary protection and rapid deployment. Fixed-site systems suit persistent coverage, stable sensor geometry and deeper command integration. Vehicle-integrated systems are appropriate when the protected asset or boundary moves.
Does detection automatically allow jamming or navigation response?
No. Detection and mitigation are separate technical and legal questions. RF interference, navigation-related response and other mitigation methods may require specific statutory authority, spectrum permission, licensing and operating procedures in the deployment jurisdiction.

10 / Review Basis

Sources and editorial method

Product roles and portfolio examples are based on JIGGS Technologies technical materials. General technology characteristics and legal cautions are cross-checked against public government guidance. Product-specific ranges are intentionally kept on the relevant product pages with their stated conditions.

Build the architecture around the mission.

Share the protected-area type, approximate coverage requirement, deployment model and relevant target profile. JIGGS Technologies can help organize the sensing, localization, confirmation and authorized response questions for a structured technical evaluation.