Identify the failed step
| What you see | Check next | Illustrated guide |
|---|---|---|
| No dashboard | Network address and port 3000; board startup | First connection |
| Camera detected, no picture | PLAY state, codec, receiving destination and active camera license | Video routing |
| Pocket phone mode, no detected stream | Correct Pocket model, its valid module license and the dedicated panel | Pocket controls |
| Telemetry ON, heartbeat offline | Controller detection, USB/UART and controller configuration | Heartbeat and endpoints |
| Modem detected, no internet | Registration, SIM/data plan, APN and route | Modem checks |
| VPN logged in, board unreachable | Device approval, assigned IP and access rules | Tailscale · ZeroTier |
| Update file uploaded, version unchanged | Installation result, correct package and board internet | Update result |
The dashboard does not open
- Check that the board has booted and that your computer is connected to the correct local network or VPN.
- Use the board’s current address and port 3000 with the
/uaslte/path. - If you switched from hotspot to Wi-Fi client mode, use the new router-assigned address.
- If remote access fails but local access works, investigate the VPN route and permissions before changing the program.
The current dashboard does not require a cloud download at boot. A missing internet connection alone is not an explanation for a missing local interface.
Camera detected, no video
- In Cockpit, confirm the selected source: Rspi Cam, CSI to HDMI Cam or the supported USB source. The visible controls must belong to the camera you want to use.
- Open the matching camera tab and check its destination. A stream directed to a ground station is not automatically also sent to Cockpit.
- For a shared Cockpit camera, select it and use Play for local viewing, or configure 127.0.0.1:8020 in its dedicated tab.
- For Pocket, use the Pocket tab and its displayed browser endpoint; confirm the detected model and matching camera license.
- Check receiver address, port and codec, and stop another independent source if it is feeding the same endpoint.
- Try H.264 to isolate a browser or receiver H.265 compatibility issue.
Video gets progressively delayed
Compare the beginning of the stream with playback after it has been running. Growing delay suggests a processing or buffering bottleneck. Check the selected resolution, concurrent streams, system load and receiver buffering before increasing bitrate.
For Pi 5 Pocket H.265, the configured maximum is 540p at 24 fps. A larger requested workload is not a quality improvement if the stream cannot keep up.
No telemetry or incomplete values
- Confirm controller detection and heartbeat.
- Check that the controller is configured to send the relevant MAVLink messages.
- For a remote receiver, match the target IP and listening UDP port.
- A missing GPS, current sensor or airspeed sensor can explain a missing reading.
- Read the action console before repeating parameter or aircraft commands.
Modem is present but there is no internet
Separate USB detection from cellular registration, data connection and routing. Check the SIM, APN, modem mode and actual route. Test internet access before trying to fix a VPN session. LED colours are model-specific.
Trial or activation issues
An expired trial returns to activation and remains used after a restart. A valid permanent main license activates the program independently of trial availability. Pocket 1 and Pocket 2 require their respective camera licenses.
Check the Device ID, copied license text and any camera-license validity date. Send license details only privately.
Update did not complete
Keep the exact installation message, filename, current version and board model. Check that the package belongs to the platform, that the required internet connection is available and that you followed the release order. Do not treat a failed attempt as a successful version change.
Send a useful support report
- Board model and image/release name.
- Camera or modem model, plus firmware where relevant.
- The selected codec, resolution, bitrate and destination type.
- Exact action/status message and whether the issue follows boot or reconnection.
- A screenshot with private license strings and account details hidden.