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

Add MAV_RESULT_COMMAND_UNSUPPORTED_MAV_FRAME #2001

Merged
merged 1 commit into from
Jun 7, 2023

Conversation

hamishwillee
Copy link
Collaborator

If MAV_CMD has a location where the frame is not explicitly specified this is taken from the COMMAND_INT.frame field. There is no way to query what frames are supported for a particular command by a particular flight stack. Many flight stacks just ignore the frame, using whatever arbitrary frame they support.

This adds a MAV_RESULT_COMMAND_UNSUPPORTED_MAV_FRAME to tell a user that the command may be valid, but not with the supported frame. If implemented a user could use this to determine what frames are supported.

Note that if autopilots continue to do the very bad thing of silently just accepting any frame this will make no difference. But this is still "the right design" by any measure.

@hamishwillee hamishwillee merged commit 7f666a4 into master Jun 7, 2023
11 checks passed
@hamishwillee hamishwillee deleted the hamishwillee-patch-6 branch June 7, 2023 23:58
@hamishwillee
Copy link
Collaborator Author

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