Skip to content

Gimbal: help tell multiple gimbal managers apart - #14793

Merged
DonLakeFlyer merged 2 commits into
masterfrom
pr-multiple-gimbal-managers
Aug 11, 2026
Merged

Gimbal: help tell multiple gimbal managers apart#14793
DonLakeFlyer merged 2 commits into
masterfrom
pr-multiple-gimbal-managers

Conversation

@julianoes

@julianoes julianoes commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

Description

When we have more than one gimbal manager in the system, it is not clear which gimbal is which.

For example:

  • Autopilot with internal gimbal (compid 1, gimbal device 1)
  • External Mavlink gimbal manager (compid 154, gimbal device 1)

Previously, both of these gimbals would show as "Gimbal 1".

With this change, they show up as "Gimbal 1-1" and "Gimbal 154-1".

Type of Change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update
  • Refactoring (no functional changes)
  • CI/Build changes
  • Other

Testing

  • Tested locally
  • Added/updated unit tests
  • Tested with simulator (SITL)
  • Tested with hardware

Platforms Tested

  • Linux
  • Windows
  • macOS
  • Android
  • iOS

Flight Stacks Tested

  • PX4
  • ArduPilot

Screenshots

Checklist

  • I have read the Contribution Guidelines
  • I have read the Code of Conduct
  • My code follows the project's coding standards
  • I have added tests that prove my fix/feature works
  • New and existing unit tests pass locally

Related Issues


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).

@github-actions

github-actions Bot commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

Build Results

Platform Status

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

Some builds failed.

Pre-commit

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

Pre-commit hooks: 0 passed, 0 failed, 0 skipped.


Updated: 2026-08-11 20:47:09 UTC • Commit: 9b81700 • Triggered by: Linux

@DonLakeFlyer DonLakeFlyer added this to the Release V5.2 milestone Aug 9, 2026
@julianoes

Copy link
Copy Markdown
Contributor Author

@DonLakeFlyer what about adding this to v5.1 and #14794 to v5.2?

@DonLakeFlyer

Copy link
Copy Markdown
Contributor

what about adding this to v5.1 and #14794 to v5.2?

I can live with that.

Can you change this such that you build gimbal names using a common function? You basically have the gimbal name building in two different places, done two different ways (sort of).

@julianoes

Copy link
Copy Markdown
Contributor Author

Can you change this such that you build gimbal names using a common function? You basically have the gimbal name building in two different places, done two different ways (sort of).

Good idea.

@julianoes

Copy link
Copy Markdown
Contributor Author

Done.

When we have more than one gimbal manager in the system, it is not clear
which gimbal is which.

For example:
- Autopilot with internal gimbal (compid 1, gimbal device 1)
- External Mavlink gimbal manager (compid 154, gimbal device 1)

Previously, both of these gimbals would show as "Gimbal 1".

With this change, they show up as "Gimbal 1-1" and "Gimbal 154-1".
@DonLakeFlyer
DonLakeFlyer force-pushed the pr-multiple-gimbal-managers branch from 9b81700 to 4f57380 Compare August 11, 2026 20:45
@DonLakeFlyer
DonLakeFlyer merged commit 87356be into master Aug 11, 2026
46 checks passed
@DonLakeFlyer
DonLakeFlyer deleted the pr-multiple-gimbal-managers branch August 11, 2026 20:49
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.

2 participants