Start learning
EN
English فارسی
ESPFlight Docs v1
Browse documentation
Docs / Espflight App / Connect to Drone

Connect to Drone

Connect the phone and Firmware v1.0.0 controller on the same trusted local network and confirm live Protocol 2 telemetry before control.

ESPFlight Docs · v1 • Validated v1 documentation path
BEGINNER PATH · STEP 9 OF 13

Do not continue to motor checks until the intended controller is connected and telemetry is live.

Back to the 13-step path · Next checkpoint: Bench Test

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.

# Before connecting

Firmware v1.0.0 has completed boot and gyro calibration.
Phone and controller use the same trusted local Wi-Fi network.
Propellers remain removed for initial connection and control checks.
Application v1.0.0 is installed.

# Connection sequence

  1. 1

    Power the controller and wait for setup

    Do not open a motor test while firmware is still calibrating. Wait for the controller to finish startup.

  2. 2

    Confirm controller Wi-Fi

    Serial Monitor should report a successful local IP or, if Wi-Fi timed out, the controller will remain safe and retry in the background.

  3. 3

    Connect the phone to the same Wi-Fi

    Avoid guest/client-isolated networks that block local peer traffic.

  4. 4

    Open ESPFlight Application

    Allow automatic discovery to find a compatible Protocol 2 controller.

  5. 5

    Select/verify the intended Drone

    Confirm the physical test setup matches the controller you intend to use.

  6. 6

    Confirm live state

    The v1 UI should show a ready/connected flight link and live telemetry. Check that signal/battery/system information updates rather than remaining stale.

# Success criteria

The intended controller is discovered.
The flight link reports ready/connected.
Telemetry updates repeatedly.
Firmware identity is v1.0.0 and protocol identity is 2 for this documented baseline.
ARM state shown in the app follows firmware telemetry; do not infer ARM only from a button appearance.

# If discovery or connection fails

Work through Connection Problems in order: controller boot → compiled Wi-Fi credentials → same local network → client isolation/firewall → firmware/application versions → clean reconnect.

TRUSTED NETWORK ONLY

Protocol 2 v1 is intended for a trusted private local network; the control/telemetry transport is not a hostile-network authentication or encryption boundary.