ADOS SWARM
Fleet coordination, from the radio up to the hive mind
Two layers make a swarm work. A radio layer lets every drone hear every other drone. On-board logic turns what each drone hears into its own flight, so the fleet acts as one. Swarm is in development.
24
Drones per fleet2
Layers: radio and logicOn-board
Distributed intelligence
A wedge formation, each drone flying off the neighbours it hears.
The two halves
A shared bus and a smart fleet
The radio is the plumbing: every drone broadcasts where it is and where it is heading, and every node hears it. The logic is the intelligence: each drone turns those beacons into its own setpoint. Neither needs a ground station in the loop.
Every node hears every node
Each drone broadcasts a 20-byte beacon twice a second, and every node, drone and ground station alike, hears every other. Power the ground station off and each drone's neighbour table is unchanged.
In the agent
The swarm bus, by the numbers
The swarm bus shares the long-range video radio, so a fleet needs no second adapter. The logic that flies the fleet ships switched off and is turned on in the agent config.
Swarm bus and swarm logic
- Fleet size
- Up to 24 drones
- Beacon
- 20 bytes, twice a second
- Airtime at 24 drones
- 0.84% of one channel
- Seal
- Fleet-keyed authenticated encryption
- Behaviours
- Hold, flocking, formation
- Formations
- Line, column, wedge, grid, circle
- Swarm flight control
- Off by default
One ecosystem, many drones
The swarm bus and the on-board swarm logic live in the open-source drone agent, and the logic that flies the fleet ships switched off. Follow the design as it comes together.
Read the docs