ESPFlight Docs v1
Browse documentation
Docs / Start Here / Quick Start

Quick Start

Build and validate an ESPFlight v1 drone from hardware review to first controlled flight.

ESPFlight Docs · v1 Validated v1 documentation path

# Before you begin

BEFORE YOU START

Use Firmware v1.0.0, Hardware Reference v1.0, Application v1.0.0, and Protocol 2 together. Keep propellers removed until the preflight stage.

# Build path

  1. 1

    Review the hardware

    Open the Hardware Reference, schematic, BOM, assembly notes, module requirements, power connections, and pin assignments.

    Open Hardware Reference
  2. 2

    Assemble and inspect

    Build the reference hardware or your compatible variant. Check soldering, shorts, polarity, installed modules, motor wiring, and mechanical security.

    Open Assembly guide
  3. 3

    Prepare firmware

    Install the pinned ESP8266 build environment, set Wi-Fi credentials in config.h, and keep the v1.0.0 release identity and tested timing values unchanged.

    Prepare build environment
  4. 4

    Flash the controller

    Select LOLIN(WEMOS) D1 R2 & mini / ESP8266, use the 160 MHz baseline, compile, upload, and confirm the controller starts without a build or boot fault.

    Open flashing guide
  5. 5

    Install the application

    Install the official v1.0.0 Android APK from the ESPFlight release channel.

    Install the app
  6. 6

    Connect on trusted Wi-Fi

    Put the phone and controller on the same private local network and confirm discovery plus live connection state.

    Open connection guide
  7. 7

    Bench-test without propellers

    Verify IMU direction, motor order, motor direction, ARM/DISARM, telemetry, low-throttle motor-off behavior, and link-loss behavior.

    Open bench-test checklist
  8. 8

    Complete preflight

    Only after bench validation passes, install the correct propellers and repeat the mechanical and control checklist.

    Open preflight checklist
  9. 9

    First controlled flight

    Move to an open low-risk area, start conservatively, keep the first hover brief, and land immediately if behavior is unexpected.

    Open first-flight guide
  10. 10

    Review and continue

    Inspect the build after the first flight, then continue to flight modes, tuning, concepts, or developer documentation.

    Choose your next path

# Expected result

EXPECTED RESULT

At the end of this guide the Drone should have a validated hardware build, Firmware v1.0.0 running, Application v1.0.0 connected, propeller-off checks passed, and a controlled first-flight baseline.

Protocol 2 v1 security boundary Keep the controller and phone on a private trusted local Wi-Fi network. Protocol 2 v1 does not provide encrypted transport or cryptographic client authentication against a hostile client on the same network; an untrusted public/shared network is not appropriate for flight control.