GCS_MAVLink: Common: Allow scripting to receive messages which fail CRC check #28248
+93
−15
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
IamPete1
commented
Sep 27, 2024
| // This may be a valid message that we don't know the crc extra for, pass it to scripting which might | ||
| AP_Scripting *scripting = AP_Scripting::get_singleton(); | ||
| if (scripting != nullptr) { | ||
| scripting->handle_message(msg, chan); |
There was a problem hiding this comment.
Note that this ignores our usual routing rules from the check_and_forward function. We can't call it because we don't want to learn routes based on messages that failed the crc.
There was a problem hiding this comment.
Maybe allow the subscribe function to pass CRC Extra value in mavlink:register_rx_msgid(msg_id)
tridge
approved these changes
Oct 1, 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 allows scripting to receive messages which the flight controller does not understand. Note that more work is needed to allow sending. This uses ArduPilot/pymavlink#983.
Tested new CRC check with MAVLink 1 and 2. Tested unknown messages by changing the CRC extra of command long in ArduPilot so it would fail its CRC check, it still works as normal in the script.