Experienced Learning Path
Skip basic onboarding and move through the validated v1 architecture, configuration, control behavior, tuning and customization references.
# Fast route
- 1
Lock the validated baseline
Confirm Downloads & Versions: Firmware v1.0.0, Hardware v1.0, Application v1.0.0, Protocol 2.
Checkpoint: you know which known-good versions you can return to after experiments.
- 2
Understand the system architecture
Read How ESPFlight Works and System Architecture, then dive into Stabilization & Control Loop and Safety Model as needed.
Checkpoint: you can separate hardware, real-time control, networking, application state and safety responsibilities.
- 3
Map the reference hardware
Use Pinout, Power System, Sensors and Motor Outputs.
Checkpoint: your real board, pin mapping, sensor orientation and power path are understood before code-level changes.
- 4
Reproduce and configure firmware
Use Download & Flash, Configuration and Firmware Reference.
Checkpoint: you can reproduce the baseline build and identify which values are project-specific versus release constants.
- 5
Understand communication and reported state
Review Networking, Telemetry and, if integrating directly, the Protocol 2 reference.
Checkpoint: you understand the trusted local network boundary and treat telemetry as controller-reported state.
- 6
Understand flight behavior
Review Flight Modes, PID Basics and Safety & Failsafe.
Checkpoint: you can distinguish mode behavior, tuning symptoms and safety-state behavior before changing values.
- 7
Validate and tune deliberately
Use Bench Test, PID Tuning and Basic Tuning.
Checkpoint: hardware faults are ruled out, one variable is changed at a time, and results are observable.
- 8
Move into customization
Continue to Compatibility, Configuration Protocol or the Advanced / Developer Path.
Checkpoint: you know whether the next change belongs to configuration, firmware, hardware or integration work.
# Configure and tune quickly
# When to use the Developer Path
Switch to the Advanced / Developer Path when you need to change firmware architecture, create custom hardware, implement a Protocol 2 client, or build an independently branded product around ESPFlight technology.