Back to all solutions
Detector & Tracker
ATR
Automatic Target Recognition for carts, tablets and airborne platforms
A single detection and tracking engine that runs identically on the ground control cart, the operator's rugged tablet and the aircraft itself. Operators keep the same target picture whether processing happens at the station or onboard, so hand-off between ground and air never resets the track.
Detection
- ▸Multi-class ATR for personnel, light and heavy vehicles, vessels and static structures
- ▸EO/IR and multispectral input with per-sensor model profiles
- ▸Small-object detection tuned for high-altitude and long-standoff imagery
- ▸Confidence gating and operator-adjustable classification thresholds
Tracking
- ▸Persistent multi-object tracking with re-acquisition after occlusion
- ▸Operator click-to-track and auto-lock on highest-priority classification
- ▸Track continuity across zoom, gimbal slew and platform manoeuvre
- ▸Geo-registered track output for fusion into the common operating picture
Deployment surfaces
- ▸Ground control carts — rack or box compute driving multi-feed operator displays
- ▸Rugged tablets — dismounted operation with the same track pipeline at reduced power
- ▸Onboard drone integration — direct feed from payload to mission computer, no downlink required
Integration & interoperability
- ▸ROS2, MAVLink, I2C, UART and custom protocol bridges
- ▸STANAG 4609 motion imagery with KLV metadata, and STANAG 4818 interoperable control
- ▸ATAK / TAK CoT track publishing into the common operating picture
- ▸C-UAS workflows: hostile drone detection, classification and hand-off to effectors
- ▸Swarm and hybrid-swarm operation with shared tracks across manned and unmanned nodes
- ▸Deterministic behavior with full audit trail of detections and operator actions
- ▸Runs disconnected — no cloud dependency in contested comms
At a glance
- Compute
- NVIDIA Jetson (Orin family), Qualcomm
- Sensors
- EO, IR, multispectral
- Form factors
- Cart, tablet, airborne payload
- Interfaces
- ROS2, MAVLink, I2C, UART, custom
- Standards
- STANAG 4609, STANAG 4818, ATAK / CoT
- Missions
- ISR, C-UAS, swarm and hybrid-swarm
- Connectivity
- Fully offline capable
- Origin
- Designed and supported in Israel
NVIDIA JetsonQualcommiMX8Hailo
Integration FAQ
- Which compute platforms does the ATR detector and tracker run on?
- It runs on NVIDIA Jetson Orin modules and Qualcomm compute, with additional builds for iMX8 and Hailo accelerators. The same model pipeline is used across ground control carts, rugged tablets and onboard drone computers, so behavior stays consistent when a mission moves between form factors.
- How is ATR integrated into an existing ground control station or airframe?
- Integration is through ROS2, MAVLink or a custom protocol bridge. Detections and tracks are published over standard video and telemetry channels, so an existing operator display can overlay them without replacing the ground control software.
- Does ATR require a network or cloud connection?
- No. All detection and tracking runs at the edge on the host compute. The system is fully offline capable and continues to operate in contested or comms-denied environments with no cloud dependency.
- Which sensors are supported?
- EO, IR and multispectral payloads are supported, with per-sensor model profiles. Small-object detection is tuned for high-altitude and long-standoff imagery, and tracks persist across zoom, gimbal slew and platform manoeuvre.
- How long does a typical integration take?
- Timelines depend on compute, sensor set and platform interfaces. Share those three details with our team and we will scope the integration, including any model tuning needed for your imagery.
- Does the ATR detector-tracker support STANAG 4609 and STANAG 4818?
- Yes. Motion imagery is consumed and produced as STANAG 4609 streams with KLV metadata, and platform control interoperability follows STANAG 4818, so the detector-tracker drops into NATO-aligned ISR and C2 architectures without a bespoke video pipeline.
- Can tracks be pushed to ATAK?
- Yes. Detections and tracks are published as Cursor-on-Target messages to ATAK / TAK clients, so dismounted operators and the ground control station share one target picture alongside the STANAG 4609 video feed.
- Is the ATR suitable for C-UAS missions?
- Yes. Small-object detection is tuned for hostile drone and loitering-munition signatures at long standoff, with persistent tracking and classification hand-off to C-UAS effectors and command systems.
- Does it support swarm and hybrid-swarm operations?
- Tracks are shared across nodes so a drone swarm, or a hybrid-swarm mixing UAVs, UGVs and manned assets, keeps a single fused target list. Low-level sensor and payload boards are addressed over I2C and UART on the host compute.
Integrate ATR into your platform
Tell us your compute, sensors and platform, and we will scope the integration.