Configuration Protocol
Keep runtime configuration bounded by firmware validation and version compatibility.
ESPFlight Docs · v1•Validated v1 documentation path
#Design principles
Validate inputs
Reject malformed, unsupported, or unsafe configuration values at the controller boundary.
Keep ownership clear
Only the active control path should be able to make state-changing requests.
Acknowledge changes
The application should know whether a requested change was accepted.
Version semantics
If configuration meaning changes, document it as a compatibility change rather than relying on guesswork.
#PID configuration
The v1 platform supports PID configuration through the application. A runtime tuning interface does not remove the need for safe bounds, known-good defaults, and revalidation after meaningful changes.