Vendor Integrations
UTMOS Open Platform provides a unified API experience across vendors. Integrators call Open Platform APIs, while the platform translates requests into vendor-specific capabilities and normalizes device responses into consistent API results.Supported Vendors
| Vendor | Cloud Commands | Command Status | Device Requests | Device Request Replies |
|---|---|---|---|---|
| PX4 | Partial | Partial | Unsupported | Unsupported |
| DJI | Supported | Supported | Supported | Supported |
Where to Go
- To understand the PX4 vendor model, uplink events, and downlink safety boundary: open PX4 → PX4 Overview.
- To inspect the 178 exposed PX4 MAV_CMD flows, 1 parameter read, and 1873 named parameter set commands: open PX4 → PX4 Command Catalog.
- To prepare a PX4 bench, HITL firmware, and QGroundControl: open PX4 → Gazebo Classic HITL.
- To send control commands from cloud to device: open DJI → Cloud → Device → DJI Downlink Command Methods.
- To inspect business requests initiated by the device: open DJI → Device → Cloud → DJI Requests.
- To write a business reply for a device request: open DJI → Device → Cloud → DJI Requests Reply.
Capability Types
| Capability | Description |
|---|---|
| Cloud commands | Integrators call Open Platform APIs to initiate control, task, configuration, or other device operations. |
| Command status | Integrators use command_id to query acceptance, delivery, success, failure, or timeout status. |
| Device requests | Devices initiate business requests; integrators query those requests through Open Platform APIs. |
| Device request replies | Integrators make a business decision and write the result back through Open Platform APIs. |