* fix(navigator): keep RTL using the checked mission after a Home update Since25a903f403(#27804), RTL uses the mission only while the mission check result carries the current Home update counter. Mission reruns the check only for a new mission or fence, or when Mission mode activates, but Commander also updates Home at arming, at takeoff outside a mission, when the disarmed vehicle is moved, on the GNSS altitude correction in the first 120 s after takeoff and on DO_SET_HOME. After any of these, and until the check ran again, RTL_TYPE 2 and 4 returned directly instead of along the mission, types 1 and 3 ignored the mission landing and the remaining time estimate used the direct path. Type 1 is the FW and VTOL default, so every FW or VTOL that armed outside Mission ignored its mission landing. Match only the mission and fence IDs, so a Home update leaves the verdict in place as it did before25a903f403. Rechecking on every Home update instead would recheck in flight: the RTL mission modes inherit MissionBase::on_inactive() and run every cycle, so even the inactive Return mode would rerun the check, and a check that now fails makes Commander fail over out of Mission. Assisted-by: Claude:claude-opus-5-5 * fix(navigator): let Return's mission modes keep Mission's verdict RTL creates a new mission-based Return mode whenever the return type changes, for example when RTL_TYPE 4 switches from the reverse to the forward mission. The new mode starts with its mission check unchecked, so its first cycle reruns the check if Home was updated since Mission checked the mission. Before the previous commit RTL used the mission only while the result carried the current Home counter; now it also creates these modes after a Home update, in flight too. There a recheck with the new Home can reject the mission being flown: an absolute takeoff altitude now below Home, GF_MAX_HOR_DIST or GF_MAX_VER_DIST measured from the new Home over items already flown, or a landing relative to Home now above its absolute approach. The result is shared, so Commander would fail over out of Mission, and a Return that creates the mode at activation would loiter instead of following the mission. RTL creates these modes only for a mission and fence that Mission has already checked, so start them with the check complete. A new mission or fence still triggers a check through the existing path, and in flight a Home update keeps the verdict, as it does for Mission. A mode created at Return activation, or in the last inactive cycle before it, also no longer reloads its items in its first active cycle. On the ground that reload started the mission that on_activation() had just declined because the vehicle is landed (for RtlDirectMissionLand, its landing). Assisted-by: Claude:claude-opus-5-5 * fix(navigator): recheck the mission when armed on the ground Mission checks the mission when the mission or fence changes and when Mission mode starts, not when Home is updated, and RTL now keeps that verdict after a Home update. Home follows the disarmed vehicle and is set again at arming and on DO_SET_HOME, so a verdict from an older Home can be wrong for the Home the vehicle takes off from. For example a fixed-wing landing relative to Home ends up above its absolute approach when Home moves up, which FeasibilityChecker::checkFixedWingLandApproach() rejects, yet Return with RTL_TYPE 1 (the fixed-wing and VTOL default) would fly it. Mission, which owns the check, now asks for a recheck when it is armed on the ground before takeoff and the verdict was computed with an older Home. The existing path reruns the check and, if Mission is active, reloads its items. While disarmed the verdict is kept, so moving the vehicle around does not recheck on every Home update. No state is needed: Commander clears takeoff_time only at disarm, and the land detector reports the takeoff before Commander sets Home for it, so a Home update in flight or after a landing keeps the verdict. So on the ground the check reruns once armed; in flight a Home update keeps the verdict, and relative altitudes (also Return's mission landing) follow the current Home, as for an active Mission. Assisted-by: Claude:claude-opus-5-5 * docs(navigator): correct why RTL does not compare Home The comment said a Home update never re-runs the mission check, but since the previous commit Mission rechecks once armed on the ground. Assisted-by: Claude:claude-opus-5-5 * refactor(navigator): clarify intent behind check --------- Co-authored-by: jonas <jonas.perolini@rigi.tech>
4.8 KiB
Missions
A mission is a predefined flight plan, which can be planned in QGroundControl and uploaded to the flight controller, and then executed autonomously in Mission mode.
Missions typically include items for controlling taking off, flying a sequence of waypoints, capturing images and/or video, deploying cargo, and landing. QGroundControl allows you to plan missions using a fully manual approach, or you can use its more advanced features to plan ground area surveys, corridor surveys, or structure surveys.
This topic provides an overview of how to plan and fly missions.
Planning Missions
Manually planning missions is straightforward:
- Switch to the mission view
- Select the Add Waypoint ("plus") icon in the top left.
- Click on the map to add waypoints.
- Use the waypoint list on the right to modify the waypoint parameters/type The altitude indicator on the bottom provides a sense of the relative altitude of each waypoint.
- Once finished, click on the Upload button (top right) to send the mission to the vehicle.
You can also use the Pattern tool to automate creation of survey grids.
:::tip For more information see the QGroundControl User Guide. :::
Mission Feasibility Checks
PX4 runs some basic sanity checks to determine if a mission is feasible. For example, whether the mission is close enough to the vehicle, if the mission will conflict with a geofence, or if a mission landing pattern is required but is not present.
The checks are run when the mission is uploaded and immediately before it is run. They are run again after arming, before takeoff, if the Home position was set since the last check. If any of the checks fail, the user is notified and it is not possible to start the mission.
For more detail on the checks and possible actions, see: Mission Mode (FW) > Mission Feasibility Checks and Mission Mode (MC) > Mission Feasibility Checks.
Setting Vehicle Yaw
If set, a multi-rotor vehicle will yaw to face the Heading value specified in the target waypoint (corresponding to MAV_CMD_NAV_WAYPOINT.param4).
If Heading has not been explicitly set for the target waypoint (param4=NaN) then the vehicle will yaw towards a location specified in the parameter MPC_YAW_MODE.
By default this is the next waypoint.
Vehicle types that cannot independently control yaw and direction of travel will ignore yaw settings (e.g. Fixed-wing).
Setting Acceptance/Turning Radius
The acceptance radius defines the circle around a waypoint within which a vehicle considers it has reached the waypoint, and will immediately switch to (and start turning towards) the next waypoint.
For a multi-rotor drones, the acceptance radius is tuned using the parameter NAV_ACC_RAD. By default, the radius is small to ensure that multirotors pass above the waypoints, but it can be increased to create a smoother path such that the drone starts to turn before reaching the waypoint.
The image below shows the same mission flown with different acceptance radius parameters:
The speed in the turn is automatically computed based on the acceptance radius (= turning radius) and the maximum allowed acceleration and jerk (see Jerk-limited Type Trajectory for Multicopters).
:::tip For more information about the impact of the acceptance radius around the waypoint see: Mission Mode > Inter-waypoint Trajectory. :::
Package Delivery (Cargo) Missions
PX4 supports cargo delivery in missions using a gripper.
This kind of mission is planned in much the same as any other waypoint mission, with mission start, takeoff waypoint, various path waypoints, and possibly a return waypoint. The only difference is that a package delivery mission must include a mission items to indicate how the package is released and the deployment mechanism. For more information see: Package Delivery Mission.
Flying Missions
Once the mission is uploaded, switch to the flight view. The mission is displayed in a way that makes it easy to track progress (it cannot be modified in this view).


