Troubleshooting
Choose the observed symptom, run the smallest relevant checks, and return to a known-good safe state before changing another layer.
ESPFlight Docs · v1 • Validated v1 documentation path
# Start safe
PROPELLERS OFF FOR BENCH DIAGNOSIS
If the problem involves firmware, connection, IMU, motors, ARM/DISARM, failsafe or unexpected control behavior, return to a propeller-off bench state first.
# Choose the symptom
Swipe horizontally to see all columns.
| Symptom | Start here |
|---|---|
| Firmware does not compile / upload / board not visible | Hardware Problems — toolchain, USB/port and MPU boot checks. |
| App cannot find or keep the Drone connected | Connection Problems — Wi-Fi, discovery, Protocol 2, live telemetry and session state. |
| No power, resets, MPU problem, motor wrong/not running | Hardware Problems — physical evidence and measurements before PID changes. |
| Flip, drift, vibration, oscillation, failsafe/battery/landing issue | Flight Problems — return to safe baseline and isolate mechanics/control/state. |
| Unfamiliar term | Glossary. |
# Troubleshooting method
- 1
Write down the exact symptom
Include firmware/app version, whether propellers are removed, and what changed since the last known-good test.
- 2
Return to the last known-good state
Undo unrelated changes before adding another variable.
- 3
Check one layer
Power/hardware → firmware boot → network → app/telemetry → controls → flight/tuning.
- 4
Compare with an expected result
Do not accept “it seems better” when the page gives a concrete state/message/value.
- 5
Apply one fix and re-test
Avoid simultaneous hardware, network and PID changes.