Software Reference Status
Availability and safety boundaries for Asimov control, telemetry, media, and protocol documentation.
The manual documents first-time board flashing, setup-dashboard access, Motor ID assignment, installed-motor discovery, zeroing, and firmware activation. The Asimov API reference also documents the low-level LiveKit connection, robot-control messages, telemetry, media, protocol fields, and firmware joint order.
Public image downloads and several release, commissioning, and safety dependencies remain TBC. The API reference is available to users with a supported robot software release, but it does not replace those prerequisites or the unavailable end-to-end Connect and Operate procedure.
Reference is not commissioning
Use API fields and examples only with version-matched generated bindings on a commissioned robot. A software DAMP state is not an emergency stop. Powered commissioning requires independent hardware safety controls, validated support and restraint, and approved startup, shutdown, disconnect, and recovery procedures.
Published API Scope
Requirements for Physical Operation
Before using the API for physical operation, confirm:
- a supported robot hardware, board, firmware, and edge-software version matrix
- generated protobuf bindings from the matching supported Asimov software release
- validated authentication, enrollment, network, and media setup
- authoritative model-joint, Motor ID, and firmware-array crosswalks
- command limits, watchdog behavior, fault semantics, and independent emergency-stop boundaries
- witnessed commissioning, restrained motion, disconnect, shutdown, and recovery tests
The Platform wire-format reference documents the platform transport contract. The Asimov API pages provide the robot-specific mappings and examples users need on top of that contract.
How is this guide?