Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BACKPORT v1.15] gimbal: fix auto RC and MAVLink mode #23249

Merged
merged 2 commits into from
Jun 11, 2024

Conversation

julianoes
Copy link
Contributor

Backport of #23236

This fixes various edge cases when input is set to both: RC and
MAVLink gimbal protocol v2.

Specifically:
- We no longer immediately reset primary control if there is no update,
  otherwise this will reset immediately after an commands.
- Talking of commands: GIMBAL_MANAGER_CONFIGURE no longer switches
  control to MAVLink but only an actual incoming setpoint command does.
- And incoming setpoint command only triggers UpdatedActiveOnce which
  means we will check RC again afterwards and if there is big movement
  switch back to RC. That's the intuitive thing to do until we have
  better reporting about who/what is in control.
- Also, with RC we no longer always set us to be in control but only on
  major movement.
@julianoes
Copy link
Contributor Author

Tested using Pixhawk 6C, Herelink and QGC v4.4.0, works!

@julianoes julianoes merged commit e255804 into release/1.15 Jun 11, 2024
5 checks passed
@julianoes julianoes deleted the pr-release/1.15-gimbal-backport branch June 11, 2024 03:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant