Connection Problems
Diagnose Wi-Fi, discovery, Protocol 2 and live telemetry from the controller outward, in a fixed order.
# App cannot discover the Drone
Swipe horizontally to see all columns.
| Check | Expected result | If not |
|---|---|---|
| Firmware boot | Serial Monitor reaches Setup completed.. | Fix MPU/setup or power problems before network troubleshooting. |
| Compiled Wi-Fi credentials | Controller reports Connected! IP: ... or retries safely after timeout. | Re-check config.h SSID/password and re-flash. |
| Phone network | Phone is on the same local network as the controller. | Join the same trusted Wi-Fi; avoid cellular-only/guest isolation. |
| Local peer traffic | Network allows devices to reach one another. | Disable guest/client isolation or use another private network. |
| Versions | App 1.0.0 + Firmware 1.0.0 + Protocol 2. | Install the documented baseline before diagnosing custom combinations. |
# Discovered but not ready / no live telemetry
- 1
Confirm the intended controller
Do not control a device only because it appears in discovery.
- 2
Watch the flight-link state
The v1 app should report the flight link ready/connected rather than stale/disconnected.
- 3
Watch multiple telemetry values
Signal/system state should update repeatedly. A static old screen is not proof of a healthy control path.
- 4
Reconnect from DISARMED
Close/reopen the connection from a propeller-off safe state.
- 5
Check for another active controller client
Protocol 2 permits one active control owner; another client can prevent control ownership even if telemetry is visible.
# Network boundary
Protocol 2 v1 uses UDP discovery on port 4210 and WebSocket on port 81. Router/firewall/client-isolation rules can block either path. The transport is intended for a trusted private local network.