Documentation
Quickstart Guide
Connect your first aircraft and run a mission in under 20 minutes.
Prerequisites
- A UAVsynq account (Ops, Fleet, or Enterprise tier)
- A supported aircraft (DJI Enterprise, Autel EVO II, Skydio X2E/X10, or senseFly eBee)
- A ground station (Windows 10/11 or macOS 12+) with the UAVsynq Operator Agent installed
- Network connectivity for the ground station during the mission
Step 1 — Install the Operator Agent
The UAVsynq Operator Agent handles the hardware communication layer between your aircraft's SDK and the UAVsynq platform.
Terminal
# Download and install the Operator Agent
$ curl -fsSL https://uavsynq.com/install.sh | bash
✓ Operator Agent installed at /usr/local/bin/uavsynq-agent
✓ Service registered: com.uavsynq.agent
Step 2 — Authenticate
Terminal
$ uavsynq-agent auth login
your-org-slug
[paste from Account → API Keys]
✓ Authenticated as yourorg — fleet: BETA-FLEET-01
Step 3 — Register your first aircraft
Connect the aircraft via USB or the hardware's companion Wi-Fi link, then register it with the fleet.
Terminal
$ uavsynq-agent fleet add --model dji-m300 --serial SN-42A80BX2
✓ Aircraft registered: UAV-01 [SN-42A80BX2]
✓ Telemetry stream active — 2 Hz polling
✓ Visible in Fleet Operations dashboard
Step 4 — Create your first mission
Open the UAVsynq web dashboard, navigate to Mission Planning, and click New Mission. Upload a KMZ boundary or draw a site polygon directly on the map.
- Set the mission name and target date/time
- Upload your KMZ/KML or draw the survey boundary
- Select aircraft assignments from your registered fleet
- Review generated flight paths — terrain-aware routing applies automatically
- Click Launch Mission to push waypoints to assigned aircraft
Step 5 — Monitor in Fleet Operations
Switch to the Fleet Operations view. All assigned aircraft should appear with live position, battery percentage, and mission progress.
First-mission tip: Start with a single aircraft in a small, open area to verify telemetry connectivity before running a multi-aircraft coordinated mission. The deconfliction engine requires telemetry from all aircraft to compute separation — partial connectivity will trigger a pre-flight warning.
Next Steps
- Fleet Configuration — Add multiple aircraft, configure roles, and set deconfliction parameters
- API Reference — Integrate UAVsynq mission control into your existing operations workflow
- Contact Support — Get help from the UAVsynq team if you hit any issues