Configuration · Integrations
What this deployment speaks
One protocol per section: what it carries in, what it can be told, and what you have to configure before it will listen.
An integration is a protocol, not a device and not a connection. The list is fixed we ship it, and what you do with one is enable it, configure it, and decide whether it may be commanded. Nothing is created here; a device joins a protocol when you add the device.
Receiving and commanding are separate switches, and deliberately so. A live feed on a test bench is reasonable; letting that bench task an effector is not. Turning an integration on decides what may arrive; allowing commanding decides what may leave.
Availability follows the environment. A simulated environment carries the in-process link and nothing that reaches real hardware; a live one is the reverse. A protocol the current environment cannot carry is shown, disabled, with the reason, you will never be offered a switch that comes back as no.
| Protocol | What it is | What it carries in | What it can be told |
|---|---|---|---|
| MAVLink | autopilots talk to a port we bind | position, attitude, battery, mode | 8 commands |
| MQTT | sensors publish to a broker we run | detections | reports only |
| DJI Cloud API | a Dock or Pilot 2 connects to us | OSD and state | 3 commands |
| SAPIENT | C-UAS sensors and effectors, BSI Flex 335 | registration, status, detections, alerts | 5 commands |
| ASTERIX | radar plots and tracks | CAT 048 and CAT 034 | reports only |
| MISB ST 0601 | EO/IR video metadata | pointing and slant range | reports only |
| ADS-B | cooperative aircraft, from a receiver | position and identity | reports only |
| DJI telemetry | a Dock or Pilot 2 that only reports | OSD | reports only |
| Inturai | sensing pods, from their cloud or ours | detections | reports only |
| Simulated | carried by the attached environment | everything the world reports | yes, verbs not yet listed |
Each row links to that protocol's own page: what arrives, how devices get onto it, the verbs it accepts, and what it needs configured.
Three objects, three questions
A protocol is not a device and not a connection, and the three get confused because the word "link" was doing all three jobs.
| Answers | How many | |
|---|---|---|
| Integration | how do bytes reach us at all | one per protocol, shipped with the build |
| Link | which of the things on it is this one | made for you, mostly invisible |
| Asset | what is it, where is it, what can it do | what you manage |
A link is not always one per device. On MQTT the credential is the identity, so there is one link per sensor. On MAVLink the system id inside the message is the identity, so twelve aircraft share one socket and one link. That asymmetry is why this page counts assets and never links.