Tools: autotest: add HEXA X configuration #26125
Merged
Conversation
This file contains 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
|
Looks like tridge got in ahead of you with the copter-x fix. Your hexa-x changes look like they might stil be applicable - did you want to pursue those? |
tatsuy
changed the title
|
@peterbarker Thanks for the feedback. I tested hexax in SITL, and confirmed no oscillation. |
tatsuy
force-pushed
the
pr-frame-type-x
branch
2 times, most recently
from
b64e59c
to
d0bd78b
Compare
tridge
approved these changes
Apr 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR introduces the following changes:
1. Fixing the ability to correctly set FRAME_TYPE to 1 when specifying --frame=X.2. Adding support for the --frame=hexax option.
I tested these frame types in SITL