feat(PlanView): choose PX4 VTOL takeoff mode - #14986
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## master #14986 +/- ##
==========================================
+ Coverage 25.47% 34.61% +9.14%
==========================================
Files 769 945 +176
Lines 65912 85662 +19750
Branches 30495 39480 +8985
==========================================
+ Hits 16788 29653 +12865
+ Misses 37285 36332 -953
- Partials 11839 19677 +7838
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 656 files with indirect coverage changes Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
Build ResultsPlatform Status
All builds passed. Pre-commit
Pre-commit hooks: 2 passed, 76 failed, 7 skipped. Test Resultslinux-coverage-integration: 52 passed, 0 skipped Code CoverageCoverage: 70.7% No baseline available for comparison Artifact Sizes
Updated: 2026-09-03 04:34:33 UTC • Commit: 9391baf • Triggered by: Linux |
b0c90ae to
808b949
Compare
Offer VTOL takeoff and multicopter takeoff choices for PX4 VTOL missions while keeping VTOL takeoff as the default. Use the existing MAVLink commands and preserve the current behavior for ArduPilot and non-VTOL vehicles. Update mission-state calculations, PX4 command metadata, the Plan View guide, and focused tests for insertion, persistence, path state, compatibility, and the offline planning UI.
808b949 to
9391baf
Compare
Feature Description
QGroundControl currently inserts
MAV_CMD_NAV_VTOL_TAKEOFFwhenever the planvehicle is a VTOL. PX4 also supports an ordinary
MAV_CMD_NAV_TAKEOFFfor aVTOL that should start and continue the mission in multicopter mode.
For PX4 VTOL plans, the Takeoff tool now offers two choices:
MAV_CMD_NAV_VTOL_TAKEOFF. It remains the first anddefault choice, so the existing workflow does not change.
MAV_CMD_NAV_TAKEOFFand keeps the mission inmulticopter mode until an explicit transition item is reached.
ArduPilot and non-VTOL vehicles keep the existing single-action Takeoff tool.
This PR is limited to QGroundControl mission planning. It does not add a
MAVLink command, change the mission format, require a PX4 change, or include
any video/networking work.
Implementation Details
does not contain a firmware-name check.
persistent takeoff-mode setting.
actually stored in the plan.
multicopter-mode takeoff after insertion or reload.
MAV_CMD_DO_VTOL_TRANSITIONis unchanged. Its existing target-state selectorremains the way to transition later in the mission.
Testing
Manual check:
inserts a takeoff mission item.
Automated coverage includes:
The full feasible suite is run by the QGroundControl GitHub Actions matrix for
this commit. No SITL or hardware evidence is claimed here.
Platforms Tested
Flight Stacks Tested
Screenshots / Demo
Compatibility
choice.
Checklist
The full QGC build/test toolchain was not available in the local checkout; the
local validation was limited to static checks and the manual Linux UI flow.
By submitting this pull request, I confirm that my contribution is made under
the terms of the project's dual license (Apache 2.0 and GPL v3).