STANAG 4609 / MISB ST0601
Process video, timestamps and positions together. External MISB ST0601 streams connect through UDP ingest to the situational picture and track.
Video and metadata processing in detailDanubis connects aircraft, cameras, sensors and other systems.
- aircraft: MAVLink
- autopilots: ArduPilot · PX4
- ground control stations: QGroundControl
- video feeds: STANAG 4609
- video metadata: MISB ST0601 · KLV
- video streams: UDP ingest
- thermal cameras: Thermal payloads
- camera payloads: Camera control
- geodata: Custom map layers
- telemetry: Real time via API
- control room software: Programming interface
- archive systems: Recordings · POIs
- detection models: Managed locally
- field teams: Mobile view
Cameras, sensors and operational assets from different manufacturers work together in the Operator Console. Existing systems become part of a shared operational workflow.
Discuss an integrationThe right level of integration for your system.
From a video feed to mission planning: the scope of an integration depends on device capabilities, available interfaces and the approvals required for its intended use.
Operational assetOperator Console
Video & telemetry
Payload
Control
Missions
Receive data
Bring video, position and telemetry into the shared situational picture. Observations remain linked to their source.
Operate payloads
Control cameras and their orientation from the Operator Console where the connected system provides these functions.
Control assets
Send control commands through the integration. Approvals and logging form part of the operational workflow.
Transfer missions
Transfer planned routes, zones and waypoints to a device and follow mission progress in the Operator Console.
Established standards, custom adapters.
We use established standards for video, metadata and aircraft. Adapters support device-specific functions. We assess compatibility with your source and its intended use.
MAVLink
Connect telemetry, mission transfer and flight commands to the Operator Console. The command chain has been tested with ArduPilot SITL and QGroundControl.
MAVLink integration in detailAdapters
Device-specific behaviour is handled by the integration. Its available capabilities for video, position and control are made accessible to the platform.
Bring Danubis into your environment.
Programming interfaces connect data and events to existing control rooms and applications. Technical interface documentation is available to integration partners on request.
- Query state
- Make information about devices, missions, detections and recordings available to existing applications.
- Subscribe to events
- Use telemetry, detections and state changes in connected workflows in real time.
- Connect geodata
- Use your own map layers, infrastructure and area data for situational awareness and mission planning.
- Export data
- Export recordings, metadata, detections and POIs for analysis and archiving outside the platform.
- Deployment with the operator
- Danubis is designed to run in the operator’s infrastructure. Data, maps and models can be managed locally.
- Controlled access
- Devices are enrolled with access management and revocation. Control functions and approvals are agreed for the intended workflow.
Let’s discuss your integration.
For operators, system integrators, and hardware and sensor manufacturers. Together, we establish how your system can become part of the operational workflow.
Review the starting point
Discuss existing systems, protocols and the intended workflow.
Evaluate the integration
Check data flow, control functions and approvals with a test source or device.
Agree a pilot deployment
Define scope, deployment environment and next steps for joint operations.
Responsibilities during integration
- Manufacturer
- Hardware, sensors and radio link, including certification and maintenance.
- Danubis
- Situational picture, mission planning, coordination, processing and recording in the Operator Console.
- Together
- The interface, available functions and technical evaluation.