Fix Vertiq IO yaml bitmask definition#23802
Merged
Conversation
Contributor
|
Looks good to me |
dagar
approved these changes
Oct 11, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Solved Problem
@DonLakeFlyer was getting errors in his QGC builds as referenced in #23800 due to the VTQ_TELEM_IDS_2 bitmask starting at 32 instead of 0.
Solution
We changed the VTQ_TELEM_IDS_2 bitmask to start at 0 and end at 30
Changelog Entry
For release notes:
Alternatives
We could also change the way the generate_params.py works so that it finds the largest and smallest bitmask values and builds the param from there.