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

mavlink-manual-control: Skip button remapping logic if vehicle has no button parameters #1175

Merged

Conversation

rafaellehmkuhl
Copy link
Member

This commit updates the button filtering logic in the MavlinkManualControlManager class. The code now filters buttons based on their names and includes only those that contain 'BTN' and 'FUNCTION'. This change ensures that only the button function parameters are used.

The commit also adds a check to skip the buttons system if the vehicle has no button parameters.

Fix #1168

… button parameters

This commit updates the button filtering logic in the MavlinkManualControlManager class. The code now filters buttons based on their names and includes only those that contain 'BTN' and 'FUNCTION'. This change ensures that only the button function parameters are used.

The commit also adds a check to skip the buttons system if the vehicle has no button parameters.
@ArturoManzoli ArturoManzoli merged commit 7e0fbf3 into bluerobotics:master Aug 2, 2024
9 checks passed
@rafaellehmkuhl rafaellehmkuhl deleted the fix-rover-joystick-throw branch August 2, 2024 12:14
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.

Joystick does not work if BTN0_FUNCTION does not exist in the vehicle
2 participants