Configuration
Understand which v1.0.0 values identify the release baseline and which values are project-specific.
ESPFlight Docs · v1 • Validated v1 documentation path
# Release identity
#define ESPFLIGHT_FIRMWARE_VERSION "1.0.0"
#define ESPFLIGHT_PROTOCOL_VERSION 2UKeep these values unchanged when producing the reference v1.0.0 build. A changed implementation should be treated as a separately tested variant.
# Tested timing
| Setting | Baseline |
|---|---|
| CPU | 160 MHz |
| Control loop | 4000 µs / 250 Hz |
| Motor PWM range | 0..1023 |
| Motor PWM frequency | 4000 Hz |
# What to change carefully
Wi-Fi credentials are expected to change for your network. Hardware pin assignments, timing, PID gains, MPU configuration, PWM frequency, and failsafe thresholds should not be changed casually in a release-equivalent build.
TEST AFTER CHANGES
If you change hardware-facing or control-loop values, treat the result as a new variant and repeat propeller-off plus controlled-flight validation.