Continue #1218: Added Mavlink command reception support #1236
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
…nkCommandSender and a MavlinkCommandReceiver class
julianoes
requested changes
Oct 22, 2020
TSC21
force-pushed
the
add-mav-cmd-reception
branch
2 times, most recently
from
58931e0
to
c35d2c9
Compare
…re in MavlinkCommandReceiver
TSC21
force-pushed
the
add-mav-cmd-reception
branch
from
c35d2c9
to
b1ab361
Compare
julianoes
approved these changes
Oct 22, 2020
JonasVautherin
approved these changes
Oct 22, 2020
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 continues the work of @yhabib29 and splits the Mavlink command send and receive functions between two different classes.