Skip to content

New option for Gimbal control, and update gimbal indicator docs - #14000

Open
Davidsastresas wants to merge 3 commits into
masterfrom
gimbal-features-and-docs-update
Open

New option for Gimbal control, and update gimbal indicator docs#14000
Davidsastresas wants to merge 3 commits into
masterfrom
gimbal-features-and-docs-update

Conversation

@Davidsastresas

Copy link
Copy Markdown
Member

Folowing #13955 (comment)

For Center and tilt 90 gimbal commands, we were sending setting also the gimbal to follow mode, as that is usually the expected behaviour. We added a new setting now to instead preserve the previous gimbal lock status:
Screenshot from 2026-02-18 15-09-08

When this is set, center and tilt 90 will just preserve current gimbal lock/follow status.

Additionally, the top toolbar indicator docs were extended to include some info from this gimbal indicator.

For awareness @DonLakeFlyer.

Copilot AI review requested due to automatic review settings February 18, 2026 14:10

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds a new setting to control gimbal yaw lock behavior during position commands and updates the documentation for the gimbal indicator. The change allows users to preserve the current yaw lock state instead of forcing yaw follow mode when centering or tilting the gimbal to 90 degrees.

Changes:

  • Added preserveYawLockOnPositionCommands setting to preserve yaw lock status during gimbal positioning
  • Refactored gimbal control to use dedicated tilt90Gimbal() method instead of direct pitch/yaw commands
  • Updated gripper action enum mappings to use correct MAVLink constants
  • Extended gimbal indicator documentation with detailed operation guide

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 2 comments.

Show a summary per file
File Description
src/UI/toolbar/GimbalIndicator.qml Added UI checkbox for new yaw lock preservation setting and updated Tilt 90 button to use new method
src/Settings/GimbalControllerSettings.h Added setting declaration for preserving yaw lock on position commands
src/Settings/GimbalControllerSettings.cc Added implementation declaration for new setting
src/Settings/GimbalController.SettingsGroup.json Added JSON configuration for new yaw lock preservation setting
src/MAVLink/QGCMAVLink.h Updated gripper action enum values to match correct MAVLink constants
src/Gimbal/GimbalController.h Added tilt90Gimbal() method declaration
src/Gimbal/GimbalController.cc Implemented logic for preserving yaw lock state in centerGimbal() and new tilt90Gimbal() methods
docs/en/qgc-user-guide/fly_view/fly_view_toolbar.md Added comprehensive gimbal indicator documentation section


#### Gimbal Control Acquisition

If the option "Show Acquire/Release control button is set, a new **Acquire/Release Control**button will appear

Copilot AI Feb 18, 2026

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing closing quote after 'button'. Should be 'If the option "Show Acquire/Release control button" is set'.

Suggested change
If the option "Show Acquire/Release control button is set, a new **Acquire/Release Control**button will appear
If the option "Show Acquire/Release control button" is set, a new **Acquire/Release Control** button will appear

Copilot uses AI. Check for mistakes.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed


#### Gimbal Control Acquisition

If the option "Show Acquire/Release control button is set, a new **Acquire/Release Control**button will appear

Copilot AI Feb 18, 2026

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing space before 'button'. Should be 'Acquire/Release Control button' with a space between the bold text and the word.

Copilot uses AI. Check for mistakes.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

@github-actions

github-actions Bot commented Feb 18, 2026

Copy link
Copy Markdown
Contributor

Build Results

Platform Status

Platform Status Details
Linux Failed View
Windows Passed View
MacOS Passed View
Android Passed View

Some builds failed.

Pre-commit

Check Status Details
pre-commit Failed (non-blocking) View

Pre-commit hooks: 4 passed, 32 failed, 7 skipped.

Artifact Sizes

Artifact Size
QGroundControl 320.17 MB
QGroundControl 330.15 MB
QGroundControl-installer-AMD64 151.16 MB
QGroundControl-installer-AMD64-ARM64 77.37 MB
QGroundControl-installer-ARM64 78.34 MB
QGroundControl-mac 184.38 MB
QGroundControl-windows 184.41 MB
No baseline available for comparison---
Updated: 2026-03-25 15:53:46 UTC • Triggered by: Android

@Davidsastresas
Davidsastresas force-pushed the gimbal-features-and-docs-update branch from c9edb07 to 6783187 Compare February 18, 2026 14:15
@DonLakeFlyer

Copy link
Copy Markdown
Contributor

@Davidsastresas Don't worry about screen shots for now. We'll do that when we get closer to stable. Dont want to capture now and have things still move around and have to redo.

Comment thread src/MAVLink/QGCMAVLink.h Outdated
GripperActionRelease = GRIPPER_ACTION_RELEASE,
GripperActionGrab = GRIPPER_ACTION_GRAB,
GripperActionHold = GRIPPER_ACTION_HOLD,
GripperActionRelease = GRIPPER_ACTION_OPEN,

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this a mistake? Seems unrelated?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If I recall correctly I got compilation errors and it was because of it. It is in a separate commit 38871ff

Maybe it was already fixed in master.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Usually means you CPM cache is out of date with respect to latest mavlink headers.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh I am sorry, I wasn't aware about it. Please let me take a look at this again in the next few days. The user that reported the issue added some more comments and maybe that changes the current PR. I will remove this mavlink thing and test, and also work on those possible new requests.

Thanks!

@Davidsastresas
Davidsastresas force-pushed the gimbal-features-and-docs-update branch from 6783187 to 752f53b Compare March 25, 2026 14:53
@github-actions github-actions Bot removed the MAVLink label Mar 25, 2026
@Davidsastresas

Davidsastresas commented Mar 25, 2026

Copy link
Copy Markdown
Member Author

@DonLakeFlyer you were totally right. I removed the mavlink commit and rebased to master, force pushed. #13955 was closed recently so I don't have nothing to add to this PR.

@Davidsastresas
Davidsastresas force-pushed the gimbal-features-and-docs-update branch from 752f53b to da7b7c4 Compare March 25, 2026 14:56
@DonLakeFlyer

Copy link
Copy Markdown
Contributor

@Davidsastresas Sorry lost track of this. I'll pick it back up when I get back in town first week in July...

@Davidsastresas

Copy link
Copy Markdown
Member Author

@DonLakeFlyer no problem at all. This was done exclusively because that user complained, but he doesn't seem to be interested anymore, so there is really no hurry.

You can ping me anytime about this and I will rebase it to master at the moment, and double check again.

@DonLakeFlyer DonLakeFlyer added this to the Release V5.2 milestone Jul 6, 2026
@DonLakeFlyer

Copy link
Copy Markdown
Contributor

but he doesn't seem to be interested anymore, so there is really no hurry.

I'm gonna move this to 5.2 then so it has some bake time after it goes in

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants