Alpha stage. This guide is based on bench-level testing only. Some steps may change as we validate on real hardware. Check back once we ship a stable release.
What You Will Do
This guide walks you through planning an automated survey mission in ADOS Mission Control. You will define an area, generate a survey grid pattern, set flight parameters, upload the mission to your flight controller, execute it in Auto mode, and download logs afterward. By the end, your drone will have flown a complete survey pattern autonomously.Prerequisites
- Mission Control running and connected to your FC (see Quickstart)
- A drone with GPS lock (3D Fix, 8+ satellites)
- An ArduPilot or PX4 flight controller (mission planning requires MAVLink, not MSP)
- A battery with at least 80% charge
- An open outdoor area for the flight
You can plan missions without a connected FC. The planner works offline. Upload the mission when you are ready to fly.
Planning the Mission
Open the Plan tab
Click the Plan tab in the main navigation. You will see a map view with your current GPS position (if connected to a FC with GPS) or a default location.The left panel shows the mission tools: waypoint list, pattern generators, settings, and import/export.

Define the survey area
You have two options:Option A: Draw on the map
- Click the Draw Polygon tool in the toolbar
- Click on the map to place polygon vertices around the area you want to survey
- Close the polygon by clicking the first vertex or double-clicking
- Click Import in the tools panel
- Load a KML, GeoJSON, or CSV file with your survey boundary
- The polygon appears on the map
Generate the survey pattern
With the polygon selected, open the Pattern Generator panel and choose Survey Grid.The survey grid generator creates a lawnmower pattern that covers the entire polygon. Configure these settings:
Click Generate. The pattern appears on the map as a series of parallel waypoints.
| Setting | What It Controls | Recommended Start |
|---|---|---|
| Altitude | Flight height above ground | 50m for general mapping, 30m for detail |
| Speed | Ground speed during survey legs | 5-8 m/s |
| Overlap (front) | Image overlap along the flight direction | 75% |
| Overlap (side) | Image overlap between adjacent legs | 65% |
| Angle | Grid rotation angle | 0° (north-south legs) or auto-optimize |
| Camera trigger | How the camera fires | Distance-based or time-based |

Review the mission details
After generating the pattern, the tools panel shows:
- Total waypoints: Number of mission items
- Total distance: Flight path length in meters
- Estimated time: Based on your speed setting
- Leg count: Number of parallel survey legs
- Photo count: Estimated images based on overlap and altitude
- Sequence number
- Latitude/longitude
- Altitude (relative to home or terrain)
- Command type (NAV_WAYPOINT, DO_SET_CAM_TRIGG_DIST, etc.)
Add takeoff and return-to-launch
A mission needs a takeoff command at the beginning and a return-to-launch (RTL) at the end.
- Click Add Takeoff at the top of the waypoint list. Set the takeoff altitude (typically the same as your survey altitude).
- Click Add RTL at the bottom of the list.
Set geofence (optional but recommended)
A geofence defines a boundary the drone cannot cross. If the drone reaches the fence, the FC triggers a failsafe action (RTL, land, or brake).
- Click the Geofence tool
- Draw a polygon larger than your survey area (give 50-100m buffer)
- Set the maximum altitude (100m is a common default)
- Set the breach action (RTL recommended)
FENCE_ENABLE, FENCE_TYPE, and FENCE_ACTION parameters. Mission Control handles the parameter mapping automatically.Set rally points (optional)
Rally points are alternate landing locations. If the drone triggers RTL and cannot reach home (wind, obstacles), it goes to the nearest rally point instead.
- Click the Rally Points tool
- Click on the map to place rally points at safe landing spots
- Set the altitude for each point (the drone approaches at this altitude before descending)
Validate the mission
Click Validate in the tools panel. The validator checks for:
- Missing takeoff command
- Missing RTL or land command
- Waypoints outside the geofence
- Altitude violations (too low, too high)
- Speed violations
- Duplicate waypoints
- Distance between waypoints (too close or too far)
Uploading the Mission
Connect to the FC
Make sure your flight controller is connected (green status indicator in the top bar). The FC must be online for mission upload.
Upload
Click Upload Mission in the tools panel.Mission Control sends the mission items to the FC using the MAVLink mission protocol:
- Sends
MISSION_COUNTwith the total number of items - FC requests each item with
MISSION_REQUEST_INT - GCS sends each
MISSION_ITEM_INT - FC sends
MISSION_ACKwhen all items are received
Mission Control uses
MISSION_ITEM_INT (message 73) for all mission uploads. This is the modern format with integer latitude/longitude (1e7 scaling) for higher precision. Older MISSION_ITEM (message 39) is supported for downloads but not used for uploads.Executing the Mission
Pre-flight checks
Run the same pre-flight checks from the Your First Flight guide:
- GPS 3D Fix, 8+ satellites
- Battery above 80%
- Pre-arm messages clear
- Geofence parameters set if you defined a geofence
- Wind conditions acceptable for your drone
Arm in Stabilize or Loiter
Arm the drone in Stabilize or Loiter mode first. Do not arm directly in Auto mode for your first mission. This gives you a chance to take off manually and verify flight behavior before handing over to autonomy.Click Arm and confirm.
Take off manually
Take off to a safe hover altitude (3-5 meters). Verify the drone is stable and responsive.
Switch to Auto
Click the mode selector and choose Auto. The drone will immediately start flying toward the first waypoint.What happens:
- The drone climbs to the mission’s first waypoint altitude
- It flies to waypoint 1 (the takeoff point, already at altitude)
- It begins the survey pattern, flying leg by leg
- Camera triggers fire at the configured interval
- At the last waypoint, it executes the RTL command
- It flies back to the launch point and lands

Monitor the flight
While the mission runs, watch:
- Progress: The active waypoint is highlighted on the map. Completed legs change color.
- Altitude: Verify the drone is holding the target altitude.
- Battery: Watch voltage sag under load. If you see voltage dropping faster than expected, be ready to abort.
- Ground speed: Should be close to your configured speed.
- Camera triggers: The mission item count increments as camera commands execute.
Other Pattern Types
The survey grid is one of seven pattern generators in Mission Control. Here are the others:| Pattern | Use Case | How It Works |
|---|---|---|
| Survey Grid | Area mapping, photogrammetry | Parallel legs covering a polygon |
| Circular Survey | Point-of-interest coverage | Concentric circles around a center point |
| Corridor Scan | Road, pipeline, or river mapping | Parallel legs along a line/path |
| Search Pattern | SAR, lost object search | Expanding square or sector search |
| Spiral | Area search from center outward | Outward spiral from a center point |
| Crosshatch | High-overlap photogrammetry | Two perpendicular survey grids overlaid |
| Perimeter | Fence-line or boundary survey | Follows polygon edges at a set offset |
Saving and Loading Missions
Save to File
Click Export to save your mission as:- QGC WPL 110: Standard MAVLink waypoint format. Compatible with QGroundControl, Mission Planner, and other GCS tools.
- KML: Google Earth format. Good for sharing with non-drone people.
- CSV: Spreadsheet format. One row per waypoint.
Load from File
Click Import to load a mission from any of the above formats. You can also import boundaries from KML or GeoJSON for the polygon tools.Mission Library
If you have cloud features enabled (Convex backend), missions are saved to the mission library in the cloud. You can browse, duplicate, and re-use past missions. This is useful for recurring survey jobs where you fly the same pattern regularly.Simulation
Before flying a real mission, you can simulate it.- Go to the Simulate tab
- Select your uploaded mission
- Click Play
- 3D visualization of the flight path on terrain
- Camera trigger points marked on the map
- Estimated timing for each leg
- Altitude profile along the route
- Terrain clearance warnings if the flight path gets too close to the ground
Tips for Better Surveys
Altitude matters. Lower altitude = higher resolution photos but more flight legs and longer mission time. 50m is a good balance for general mapping. 25-30m for detailed inspection. 80-100m for large area overview. Overlap is important. 75% front overlap and 65% side overlap is the starting point for photogrammetry. If your processing software struggles to stitch images, increase side overlap to 70-75%. Wind check. Survey missions fly at constant speed. Headwind legs are slower (use more battery). Tailwind legs are faster. Plan the grid angle perpendicular to the wind direction when possible, so wind is a crosswind on the survey legs. Battery budget. Plan for 70% of your battery capacity, not 100%. Keep 30% as margin for wind, unexpected maneuvers, and RTL. Check your estimated flight time against your battery’s known endurance.Next Steps
Pattern Generators
Deep dive into all 7 pattern types with configuration guides.
Geofences and Rally
Set up safety boundaries and alternate landing points.
Simulation
Run 3D mission simulations before flying.
File Formats
Import and export missions in multiple formats.