Start learning
EN
English فارسی
ESPFlight Docs v1
Browse documentation
Docs / Flight / Bench Test

Bench Test

Run one complete propeller-off validation from firmware boot through ARM/DISARM and a safe link-loss check before installing propellers.

ESPFlight Docs · v1 • Validated v1 documentation path
BEGINNER PATH · STEP 10 OF 13

This is the propeller-off validation gate. Every listed check must pass before preflight.

Back to the 13-step path · Next checkpoint: Preflight Check

# Starting state

All propellers removed.
Frame secured so motor vibration cannot move it off the bench.
Firmware v1.0.0 flashed and Serial Monitor available.
Application v1.0.0 installed.
Battery/power wiring inspected and polarity verified.

# 1 — First power-up and gyro calibration

  1. 1

    Power the controller

    Keep the Drone completely still on a stable surface.

  2. 2

    Watch Serial Monitor at 115200

    Confirm MPU6050 detection and configuration succeed.

  3. 3

    Keep the frame still through calibration

    After “MPU6050 configuration verified”, do not move the board until “Setup completed.” appears; the 2000-sample calibration takes about eight seconds plus processing time.

  4. 4

    Stop on boot failure

    Do not continue if the MPU is not detected/configured or setup never completes.

# 2 — Connection and telemetry

  1. 1

    Open the app on the same trusted Wi-Fi

    Discover and select the intended controller.

  2. 2

    Confirm live telemetry

    Connection, battery/supply proxy, signal and state information should update. Firmware/Protocol identity must match the v1 baseline.

  3. 3

    Move the frame by hand only after setup is complete

    Roll/Pitch indication must follow the real physical motion rather than moving opposite to it. If it is reversed or implausible, stop and check IMU orientation/wiring.

# 3 — Motor mapping, direction, ARM and throttle

Use the Motors & Propellers table as the mapping authority. The public v1 beginner path does not assume a dedicated single-motor test UI.

  1. 1

    Verify M1–M4 wiring with power off

    Confirm each documented output reaches the intended physical corner.

  2. 2

    Set throttle minimum and ARM

    Telemetry must show ARMED-ready while all motors remain off.

  3. 3

    Raise throttle only enough to start normal output

    Above the low-throttle boundary, confirm all four motors respond and rotate M1/M3 CCW and M2/M4 CW.

  4. 4

    Return throttle to minimum

    Normal motor output should return to zero while the firmware may still report ARMED.

  5. 5

    DISARM explicitly

    Confirm telemetry reports DISARMED and motors remain off before approaching the frame.

# 4 — Safe link-loss check

  1. 1

    Reconnect and ARM at minimum throttle

    Do not enter powered flight for the first failsafe check.

  2. 2

    Confirm ARMED-ready / motors off

    This establishes the validated motor-off starting state.

  3. 3

    Break the control link

    Background/close the app or disable phone Wi-Fi.

  4. 4

    Observe

    Failsafe may be reported, but a session that never entered powered flight must not start the motors.

  5. 5

    Restore a safe state

    Reconnect, return to DISARMED, and do not proceed if the behavior was unexpected.

# Pass / fail gate

PASS ONLY IF

Boot/calibration completes, live telemetry is trustworthy, attitude direction is correct, M1–M4 wiring/direction is correct, ARM-ready keeps motors off, throttle start/stop is predictable, DISARM works, and the propeller-off link-loss check is safe. Only then continue to Preflight Check.