Before you power on
Use the system image for your board, a suitable power supply and a verified SD card. Connect only the equipment needed for your first setup. The browser interface runs on the companion computer itself; it is not downloaded from a server at every boot.
Open the local interface
- Start the board. Allow the system and dashboard to finish starting. Boot time varies with the board, card and attached devices.
- Join the local network. On Wi-Fi-equipped images using the standard hotspot, join
Uas_Ltewith the supplied hotspot password. The standard image password is12345abcde. - Open the dashboard. While connected to that hotspot, enter
http://192.168.77.1:3000/uaslte/in your browser. - Using a router instead? Find the board’s assigned address in the router’s client list, then open
http://BOARD_IP:3000/uaslte/. Use the board’s address, not the router’s address.
First boot: identify, try or activate
Raspberry Pi & Radxa — same sequence.
1 → 2 → 3: send your Device ID privately to Julliano, paste your matching UAS license, then activate and allow the board to restart. T is optional: start the included one-use 15-minute trial when you are ready. Opening the dashboard does not start it. A board restart ends the trial. Permanent activation remains available before or after the trial. Illustrated activation example. The bundle includes lifetime UAS, DJI Pocket 1 and DJI Pocket 2 licenses, with separate activation codes.
Choose trial or permanent activation
The activation screen offers two routes: try the included trial, or activate the program with a purchased license. A trial starts only when you press its button. Simply powering the board on does not consume it.
For permanent activation, send the displayed Device ID privately to EasyDrone, enter the matching license in Enter License, then press the activation button. Activation restarts the board; reconnect to the same local or VPN address after it returns.
Check the system before adding equipment
In Dashboard, check the detected board, system load and network status. Then configure one camera and one flight controller at a time. A waiting video frame or missing telemetry is normal when the corresponding device is not connected.
Bring the first picture and heartbeat online
- Open the appropriate camera tab. Detect or select the source and confirm the action display.
- Set resolution and bitrate, apply the local receiver IP/port and start one stream. General Cockpit video uses 127.0.0.1:8020; Pocket uses its dedicated tab/receiver.
- Connect the flight controller, confirm the heartbeat and check live HUD/map values in Cockpit.
- Only after this local check, configure the modem/VPN and external receivers. Test after unplugging and reconnecting the intended equipment.