gazebo_mavlink_interface: remove support for MAVLink v1 #1076
Conversation
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
|
@MaEtUgR Are we at the point where I can say "PX4 supports only MAVLink 2 and will ignore MAVLink 1 packets on the network"? |
|
@hamishwillee For simulation I think it doesn't support mavlink 1 for sure |
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.
I thought I'd remove some clutter by only using MAVLink v2. It was default already before and I couldn't find any model that still uses MAVLink v1.
I can't test this pr with my Ubuntu 25.04 setup, sorry for that.
Mildly related to PX4/PX4-Autopilot#25583 but for the simulation use case I don't have any concerns.