Beginner Learning Path
Build your first ESPFlight Drone without needing to understand the whole platform in advance. Complete each checkpoint before moving on.
# Before you start
ESPFlight controls real motors and flying hardware. Keep propellers off during assembly, first power-up, connection checks and the bench-test stages unless a referenced guide explicitly moves you beyond that boundary.
This path uses the validated v1 baseline: Firmware v1.0.0, Hardware Reference v1.0, Application v1.0.0 and Protocol 2.
# Essential terms before you start
| Term | Practical meaning in this path |
|---|---|
| Firmware | Software running on the ESP8266 that handles sensors, flight control, motor outputs, safety, and communication. |
| IMU / MPU-6050 | The reference motion sensor that gives Firmware the motion/rotation data used for stabilization. |
| ARM | The Firmware's flight-ready state after safety checks; ARM alone does not mean motors must spin. |
| DISARM | The safe state that stops motor output and resets control/assist state. |
| Failsafe | The Firmware's safety response when a required condition such as communication or health is lost. |
| BOM / Gerber | The BOM lists PCB parts; Gerbers are PCB fabrication files. Neither is the complete Drone parts list. |
Use the Glossary when you need a fuller definition.
# 13 guided checkpoints
- 1
Understand what ESPFlight is
Read the Introduction. Learn the roles of Firmware, Hardware Reference, Application and Documentation.
Done when: you can explain how those four parts work together and know that ESPFlight is a platform, not a required finished kit.
- 2
Prepare what you need
Use What You Need, Downloads & Versions, and Airframe & Power Selection.
Done when: required parts, tools, computer/Android device and the correct v1 software sources are identified before ordering or flashing.
- 3
Understand the basic system
Read How ESPFlight Works. Focus on the sensor → firmware → motor path and the app → network → firmware path.
Done when: you know what the ESP controller, MPU-6050, motor outputs, power system and Application each contribute without needing deep electronics theory.
- 4
Build and inspect the hardware
Follow Build Overview, then use Components, Airframe & Power Selection, Assembly, Wiring & Orientation and Hardware Verification.
Done when: assembly, polarity, orientation and electrical inspection pass and propellers are still off.
- 5
Prepare the firmware environment
Open Download & Flash. Install Arduino IDE, the required ESP8266 board support and the pinned libraries described there.
Done when: the documented build environment is installed and the Firmware v1.0.0 source is ready to compile.
- 6
Configure only what your build requires
Use Firmware Configuration. Treat
config.has the project-specific settings file: review Wi-Fi and hardware-related settings against your real build instead of changing unrelated values.Done when: the configuration matches your hardware and network and you have not changed advanced values without a reason.
- 7
Compile, upload and verify startup
Return to Download & Flash and complete the documented configure → compile → upload flow.
Done when: upload completes successfully and the controller reaches the expected startup/gyro-calibration behavior described in the guide.
- 8
Install the official Application
Follow Install the App. Use the official ESPFlight Application v1.0.0 package and verify the APK when appropriate.
Done when: the official app is installed and opens normally on Android.
- 9
Connect on trusted local Wi-Fi
Use Connect to Drone. The phone and controller must meet the v1 trusted-network requirements.
Done when: the intended Drone is discovered/connected and live telemetry confirms an active link.
- 10
Pass the propeller-off bench test
Follow Bench Test. Verify IMU response, motor mapping/direction, ARM / DISARM, throttle behavior and failsafe as documented.
Done when: every propeller-off validation gate passes. Do not compensate for a failed hardware or direction check with PID tuning.
- 11
Complete preflight
Use Preflight Check immediately before moving to powered flight.
Done when: physical, system and environment checks all pass with no unresolved stop condition.
- 12
Perform the first controlled flight
Read Controls and follow First Flight. Use the conservative beginner baseline described there.
Done when: you complete a short, controlled manual hover/flight, land or disarm safely, and observe no unresolved abnormal behavior.
- 13
Choose what to learn next
Continue with Next Steps or move to the Experienced Path.
Done when: you choose one next goal—tuning, modes, concepts, hardware changes or development—while keeping one known-good v1 baseline.
# If something does not pass
Use Hardware Problems and return to the failed checkpoint before continuing.
Use Connection Problems and verify the trusted-network boundary first.
Stop the flight test, return to propeller-off checks, and diagnose the likely layer before tuning.
# For educators and structured learning
This Beginner Path can be used as a practical lab sequence: platform overview → hardware build → firmware setup → connection → propeller-off validation → first controlled flight. Instructors can deepen selected topics using Concepts without creating a separate parallel curriculum.