-
-
Notifications
You must be signed in to change notification settings - Fork 510
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
Switch to new REQUEST_MESSAGE but fall back to deprecated request message commands if required #2381
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I think this logic makes sense 👍
This is a first step towards consistently using the new REQUEST_MESSAGE commands everywhere while still being able to fall back to the deprecated commands on retries.
bf73ee8
to
06f485d
Compare
Just to name this consistently with other MAVLink helpers like this.
The home position is now requested until valid, for both PX4 and ArduPilot. Presumably, I had broken this in a previous cleanup.
We no longer support gimbal v1 (MOUNT) commands with the next MAVSDK major release.
This allows to register and unregister mavlink messages in any context, even if the the mavlink message handler lock is already taken.
@JonasVautherin do you mind double checking the last commit please, thanks! Better to get that one right... |
Quality Gate passedIssues Measures |
It looks good to me! Though I haven't tested it, I only read the commit (carefully, though). Let me know if you need me to test something. |
Thanks @JonasVautherin! It fixes the system_test failure, so that's enough testing for me :) |
This implements the logic of requesting messages using the new command as well as the deprecated commands consolidated in the RequestMessage class.
Currently WIP implementing the functionality in REQUEST_MESSAGE. The next step is to use this class consistently everywhere.
Closes #1605, closes #2013.