Adding hardware to DroneCommand™ is an integration task, not a migration.
New airframe types built on open-autopilot platforms typically integrate in two to four weeks. The work is confined to the hardware abstraction layer.
Four steps from assessment to handover.
- 01
Assessment
We review the platform's autopilot, interfaces and telemetry model, and confirm whether it can be addressed through open standards.
- 02
Adapter development
A vehicle adapter is written against the hardware abstraction layer. No change is required in the command layer or the operator interface.
- 03
Bench and field validation
Capability mapping, tasking, telemetry fidelity and degraded-mode behaviour are validated on the bench and then in flight or on the ground.
- 04
Documentation and handover
The integration is documented, versioned and added to your compatibility matrix with its supported task set.
Bench and field validation before any platform enters the supported matrix.
Supported asset categories.
Categories rather than model numbers. The full compatibility matrix, including specific supported configurations, is shared with qualified customers on request.
| Asset category | Integration status |
|---|---|
| Multirotor · open autopilot | Supported |
| Fixed-wing · open autopilot | Supported |
| VTOL · open autopilot | Supported |
| Unmanned ground vehicles | Supported |
| Static sensor nodes | Supported |
| Docking and housing infrastructure | Integration on request |
| Proprietary manufacturer stacks | Assessed case by case |
DroneCommand™ is licensed per connected agent regardless of manufacturer. Existing platforms stay in service; supported types connect immediately and unsupported types enter the integration process above.
Manufacturers and system integrators can have their platforms assessed for adapter support. We select, integrate and validate airframes; we do not manufacture them.