Repository navigation
Bench Procedures
Open the inspector's Bench tab, or Run bench check under the preflight list, and choose a procedure:
| Procedure | When |
|---|---|
full_bench |
A new, modified or repaired aircraft |
preflight_quick |
Before each session |
motor_check |
After a motor or ESC change |
vibration_check |
After a propeller or motor change |
hover_tune |
While tuning |
Steps run in order: link and firmware, battery at rest, parameter baseline, sensor calibration, stick directions, motor order and direction with the propellers removed (drawn from the reported frame), ground vibration, propellers fitted, a hover test at 0.6 m, roll, pitch and yaw step responses, and hover learning.
Each step shows live measurements and a verdict against a stated limit. Suggested parameter changes name the parameter and the direction, and are applied only when the operator agrees. Confirm words (CALIBRATE, MOTOR, ARM) and limits apply on a real aircraft.
The report is saved under Records → Bench reports and exports as JSON or a bilingual Markdown table. Agents run the same procedures through the API and the device MCP server; on a real aircraft only the operator answers the propeller and motor questions.
Get started
Simulation
- Simulator and Physics
- Collisions and Rings
- Firmware Twins and HITL
- PX4 and ArduPilot SITL
- Simulators Compared
Arena
Programs and agents
Tools
Help