Skip to main content

Configuration · Supported hardware

What you can plug in

Every sensor and vehicle this build knows, straight from the build itself, so the list cannot quietly fall behind what the product actually offers.

DomeCommand defends with your inventory. Everything below is a type the system already knows how to talk to: pick one when you add a thing, and it arrives with its reach, its field of view and its protocol already filled in. Nothing here has to be typed by hand.

Something you field that is not on this list is usually one integration away rather than one product away. See Integrations for the protocols we speak, and Onboarding an asset for how a device that speaks one of them gets connected.

Sensors

What a sensor measures matters as much as how far it reaches. A sensor that reports a bearing or a zone localises nothing on its own, it needs a second source before anything can be tracked from it. That is not a shortcoming; it is what makes two cheap nodes worth more than one expensive one.

SensorModalityMeasuresReachField of viewConnects by
L3Harris WESCAM MX-10ira bearing6.0 km25° sectorMISB ST 0601 (KLV), Turret control
MISB ST 0601 feedeoa bearing4.0 km12° sectorKLV over UDP, KLV over TCP
Batear Acoustic nodeacoustica zone300 momniPublishes to us
Inturai Sensing podPublishes to us, Inturai cloud
ASTERIX radarradara position5.0 kmomniASTERIX multicast
SAPIENT nodeSAPIENT
ADS-B receiverBeast / SBS

Vehicles

VehicleWhat it isConnects by
DJI Mavic 3 EnterpriseQuadrotor · 45 min · 21 m/sDJI Cloud API, DJI telemetry only, MAVLink bridge
MAVLink airframeAny autopilot · PX4 or ArduPilotMAVLink
Where these figures come from

Every row is read out of the build you are running, not maintained by hand. If a model you field is missing, it is a catalog entry away, and a vehicle whose exact model is not named inherits nothing, so its endurance reads as a battery percentage rather than as minutes of flight left.