Telemetry
Use telemetry to confirm what the controller believes is happening before and during tests.
ESPFlight Docs · v1 • Validated v1 documentation path
# What to watch
Connection state
Confirm the controller remains connected and responsive.
Attitude
Use Roll/Pitch movement to detect an orientation or axis problem before flight.
ARM state
Treat firmware telemetry as authoritative for whether ARM/DISARM succeeded.
Flight time
In v1.0.0 this represents accumulated powered-flight time, not total time spent ARMED.
# Use telemetry as a validation tool
Unexpected telemetry is a reason to stop and diagnose. Do not continue to a powered flight test when attitude, ARM state, connection state, battery information, or other critical feedback is inconsistent with the real build.