Does NOMAD require a cloud connection?

No. NOMAD is designed for on-premises, disconnected deployment on tactical tablets, rugged laptops and edge computers.

Can NOMAD work with the C2 system we already use?

Yes. NOMAD interoperates with ATAK through CoT messaging and STANAG 4609 video, and can integrate with customer command systems.

How many assets can one operator manage?

NOMAD is designed so one operator can supervise multiple heterogeneous air and ground assets from a single interface.

Does it require cloud connectivity?

No. NOMAD deploys on-premises and in disconnected environments; no cloud dependency is required.

Can it work with ATAK?

Yes. NOMAD shares tracks, video and the common operational picture with ATAK and other customer C2 systems through CoT messaging.

Does NOMAD replace the fielded C2I?

No. NOMAD sits under ATAK, TAK, another CoT-based C2I, a vendor station or a customer interface. New platforms are integrated through adapters while the operator picture stays in place.

Which robot and video protocols does NOMAD support?

The supplied interfaces include MAVLink for air vehicles, STANAG 4818 for UGV interoperability, ROS 2 for quadrupeds, CoT for C2I events, and STANAG 4609 or RTSP for motion video, plus vendor APIs.

Which networks are supported?

Adaptive video and prioritised control run over RF radios, MANET mesh, LTE/5G and wired backhaul.

What do operators use to view and control?

Operator clients run on Android tactical tablets, Windows and Linux, and several platforms can stream at once.

What radios are supported?

RF radios, MANET mesh, LTE/5G, wired backhaul and hybrid links. The system is bearer-agnostic and adapts to measured link conditions.

How does it handle a sudden bandwidth drop?

Resolution and bitrate are reduced smoothly while control traffic is protected, so the operator stays in command instead of losing the platform.

Can multiple operators watch the same feed?

Yes. Video and telemetry can be shared through NOMAD so several operators and command stations see the same picture.

Do we need to modify the aircraft?

No. Translation happens in an edge gateway alongside the existing autonomy and video pipeline, so the autopilot and the receiving system stay unchanged.

Can the metadata schema be adapted to our coalition requirements?

Yes. The gateway output is customisable to specific coalition or customer schemas and can feed NOMAD or ATAK.

STANAG 4619 is a NATO standardisation agreement that defines metadata and interfaces for sharing ISR sensor data, including video and target information, across coalition systems.

How is STANAG 4619 different from STANAG 4609?

STANAG 4609 is the NATO digital motion imagery standard that carries video and KLV metadata. STANAG 4619 addresses broader ISR metadata exchange for command and intelligence systems. A bridge maps MAVLink data into the appropriate fields for each.

Do I need to replace my autopilot?

No. The bridge sits between the existing MAVLink autopilot and the downstream C2/ISR system, so the aircraft and ground control station can stay as they are.

Is the integration bidirectional?

Yes. Tracks, targets, video links and telemetry are published to ATAK, and tasking can be sent from ATAK back to the robotic asset.

Can it be deployed without internet access?

Yes. The integration runs on-premises and supports disconnected operation, and works with MAVLink and ROS platforms.

What is Cursor on Target?

Cursor on Target, or CoT, is the XML-based messaging protocol used by ATAK and the TAK ecosystem to share positions, tracks, points and tasking across tactical networks.

Do the robots need to run ATAK themselves?

No. The robots run Neuronic autonomy, video and C2 software, which translates between robot protocols and CoT so ATAK sees standard tracks and tasking.

Can video from the robot appear in ATAK?

Yes. Video, telemetry and target metadata can be shared into ATAK alongside the CoT track picture.

Tactical Hybrid Swarm Control & Connectivity

One C4I gateway to operate and coordinate drones, UGVs and USVs over tactical networks.

NOMAD tactical robotic command and control operational picture

Neuronic Tactical Hybrid Swarm Control connects mixed robotic platforms to your existing C4I through the NOMAD gateway, with resilient video, teleoperation, MAVLink-to-STANAG 4619 bridging and ATAK integration.

Products

Tactical Video & Teleoperation Suite NOMAD Tactical Robotic C2

Command & control

NOMAD Tactical C2I Autonomy Gateway

A tactical C2I autonomy gateway connects robots that use different control, video and metadata protocols without replacing the operator's existing interface. NOMAD translates MAVLink, STANAG 4818, ROS 2, CoT, STANAG 4609 and vendor APIs into one operational picture while maintaining one control owner per platform.

Step 1

Connect assets and sensors

MAVLink UAVs, STANAG 4818 UGVs, ROS 2 quadrupeds and vendor platforms connect through adapters.

Step 2

Build a shared picture

NOMAD converts each platform's video, telemetry and metadata into a common operational representation beneath the existing C2I.

Step 3

Task by intent

The operator assigns intent while NOMAD maintains one named control owner for each platform in the mixed fleet.

Step 4

Cross-cue automatically

A common target can be handed from a UAV to a UGV or robotic dog, translated into the receiving platform's protocol.

Every new robot adds operator load

Mixed robotic fleets arrive with different vendor stations, protocols, radios and video paths. Replacing the fielded C2I creates another integration problem. NOMAD puts an adapter layer underneath it, so a new platform or modem can be added without changing the operator picture.

Why it matters

Lets one operator supervise multiple heterogeneous assets.
Speeds up detect-to-engage cycles with automatic cross-cueing.
Shares a common picture with ATAK and existing command systems.
Runs disconnected; no cloud dependency required.
Keeps video off the command path and supports RF, SATCOM and cellular transports.

Resilient links

Tactical Video & Teleoperation

Tactical video and teleoperation means controlling a robot you cannot see over a network that keeps changing. Neuronic encodes video at the edge and adapts bitrate, resolution and frame rate to measured link conditions while prioritising control traffic, so latency stays low and the operator retains control across RF, mesh, cellular and satellite-backed links.

Step 1

Capture video and telemetry

The suite ingests video, MAVLink and ROS telemetry from the platform at the edge.

Step 2

Measure and adapt

Available bandwidth is measured continuously and bitrate, resolution and frame rate are adjusted to match.

Step 3

Prioritise control

Control traffic is protected over video so the operator keeps command even when the link is heavily degraded.

Step 4

Share the picture

Video, telemetry and target data feed into NOMAD and ATAK so the whole team sees the same mission picture.

Fixed-bitrate video fails on tactical networks

Standard video streams freeze or drop when bandwidth changes. In tactical operations that costs situational awareness and can leave the operator without control of the platform. The link must adapt instead of breaking.

Why it matters

Maintains situational awareness beyond line of sight.
Keeps control responsive during bandwidth drops.
Supports multiple simultaneous streams from mixed assets.
Works over the radios and mesh networks already fielded.

Interoperability

MAVLink to STANAG 4619 Bridge

A MAVLink to STANAG 4619 bridge translates autopilot telemetry and target data from tactical drones into NATO-compliant metadata that coalition command and intelligence systems can consume. Neuronic runs the gateway at the edge, alongside the video pipeline, so tracks and platform state reach higher command without changing the aircraft or the receiving system.

Step 1

Ingest MAVLink telemetry

The gateway receives position, attitude, sensor and target messages from the MAVLink autopilot or companion computer.

Step 2

Map to STANAG 4619 semantics

Telemetry and target information are translated into the correct metadata fields and timing for the STANAG 4619 stream.

Step 3

Package and stream metadata

The resulting metadata stream is multiplexed with video or sent alongside it over standard tactical bearers.

Step 4

Feed C2 and ISR systems

Coalition command, intelligence and ATAK-based systems consume the STANAG 4619 stream as if it came from a NATO-standard platform.

Tactical UAS do not speak NATO ISR natively

Most small and tactical drones use MAVLink for autopilot command and telemetry, while coalition ISR systems expect STANAG 4619 metadata. Without a bridge, valuable tactical video and tracks cannot be consumed by higher command or shared across allies.

Why it matters

Integrates tactical UAS into coalition ISR workflows without replacing the autopilot.
Preserves the low cost and flexibility of MAVLink-based platforms.
Lets command systems consume video, position and target metadata from the same source.
Runs at the edge so translation happens before the datalink.

Interoperability

ATAK Integration for Robotic Systems

ATAK integration connects drones, UGVs and robotic dogs to the Android Team Awareness Kit using Cursor on Target (CoT) messaging. Platform positions, detected targets and video links appear as CoT entities in the same common operational picture the team already uses, and tasking can be sent back to the robot from ATAK.

Step 1

Generate CoT messages

Robot positions, detected targets and sensor footprints are translated into Cursor on Target messages at the edge.

Step 2

Receive ATAK tasking

ATAK points, routes and areas of interest are converted into missions the robot's autonomy stack can execute.

Step 3

Share video and telemetry

Live video, telemetry and target metadata flow into ATAK alongside the CoT track picture.

Step 4

Keep a bidirectional sync

Updates from the robot and commands from ATAK stay synchronised across the mission so the picture is always current.

Robots produce data ATAK cannot see

Drones and ground robots generate position, video and target information, but without CoT translation that data does not appear in ATAK. Operators end up with one screen for the robot and another for the rest of the mission.

Why it matters

Uses the ATAK ecosystem teams already train on.
Puts robotic tracks on the same map as crewed and other digital assets.
Lets command task robots through a familiar interface.
Avoids replacing existing command systems.

Demos

See it working

Tactical Video & Teleoperation Under Degraded Links

An operator holds live video, telemetry and control of a robotic platform while available bandwidth drops and the link degrades.

Neuronic Capability Overview

A short overview of the Neuronic stack: edge perception, platform autonomy, tactical video and multi-robot command and control.

NOMAD Tactical Autonomy Gateway

See NOMAD connect heterogeneous UAV, UGV and robotic-dog feeds, normalize their video and metadata, and hand a shared target between platforms.

All demos

Quick answers

Questions about Tactical Hybrid Swarm Control

Does NOMAD require a cloud connection?: No. NOMAD is designed for on-premises, disconnected deployment on tactical tablets, rugged laptops and edge computers.
Can NOMAD work with the C2 system we already use?: Yes. NOMAD interoperates with ATAK through CoT messaging and STANAG 4609 video, and can integrate with customer command systems.
How many assets can one operator manage?: NOMAD is designed so one operator can supervise multiple heterogeneous air and ground assets from a single interface.
Does it require cloud connectivity?: No. NOMAD deploys on-premises and in disconnected environments; no cloud dependency is required.
Can it work with ATAK?: Yes. NOMAD shares tracks, video and the common operational picture with ATAK and other customer C2 systems through CoT messaging.
Does NOMAD replace the fielded C2I?: No. NOMAD sits under ATAK, TAK, another CoT-based C2I, a vendor station or a customer interface. New platforms are integrated through adapters while the operator picture stays in place.
Which robot and video protocols does NOMAD support?: The supplied interfaces include MAVLink for air vehicles, STANAG 4818 for UGV interoperability, ROS 2 for quadrupeds, CoT for C2I events, and STANAG 4609 or RTSP for motion video, plus vendor APIs.
Which networks are supported?: Adaptive video and prioritised control run over RF radios, MANET mesh, LTE/5G and wired backhaul.
What do operators use to view and control?: Operator clients run on Android tactical tablets, Windows and Linux, and several platforms can stream at once.
What radios are supported?: RF radios, MANET mesh, LTE/5G, wired backhaul and hybrid links. The system is bearer-agnostic and adapts to measured link conditions.
How does it handle a sudden bandwidth drop?: Resolution and bitrate are reduced smoothly while control traffic is protected, so the operator stays in command instead of losing the platform.
Can multiple operators watch the same feed?: Yes. Video and telemetry can be shared through NOMAD so several operators and command stations see the same picture.
Do we need to modify the aircraft?: No. Translation happens in an edge gateway alongside the existing autonomy and video pipeline, so the autopilot and the receiving system stay unchanged.
Can the metadata schema be adapted to our coalition requirements?: Yes. The gateway output is customisable to specific coalition or customer schemas and can feed NOMAD or ATAK.
What is STANAG 4619?: STANAG 4619 is a NATO standardisation agreement that defines metadata and interfaces for sharing ISR sensor data, including video and target information, across coalition systems.
How is STANAG 4619 different from STANAG 4609?: STANAG 4609 is the NATO digital motion imagery standard that carries video and KLV metadata. STANAG 4619 addresses broader ISR metadata exchange for command and intelligence systems. A bridge maps MAVLink data into the appropriate fields for each.
Do I need to replace my autopilot?: No. The bridge sits between the existing MAVLink autopilot and the downstream C2/ISR system, so the aircraft and ground control station can stay as they are.
Is the integration bidirectional?: Yes. Tracks, targets, video links and telemetry are published to ATAK, and tasking can be sent from ATAK back to the robotic asset.
Can it be deployed without internet access?: Yes. The integration runs on-premises and supports disconnected operation, and works with MAVLink and ROS platforms.
What is Cursor on Target?: Cursor on Target, or CoT, is the XML-based messaging protocol used by ATAK and the TAK ecosystem to share positions, tracks, points and tasking across tactical networks.
Do the robots need to run ATAK themselves?: No. The robots run Neuronic autonomy, video and C2 software, which translates between robot protocols and CoT so ATAK sees standard tracks and tasking.
Can video from the robot appear in ATAK?: Yes. Video, telemetry and target metadata can be shared into ATAK alongside the CoT track picture.

Other technologies

Perception Monitored Autonomy

Discuss your platform and mission

Tell us the platform, sensor and mission. We will walk you through integration options and arrange a technical demonstration.