feat: inject MAVLink diagnostic overlay and volatile render bypass#86
Open
feat: inject MAVLink diagnostic overlay and volatile render bypass#86
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Implemented a live diagnostics overlay for anomaly detection.
Receiver Hook: Included handling for MAVLINK_MSG_ID_NAMED_VALUE_FLOAT to provide visual feedback through edge compute payloads.
Memory Safety: Defined the trigger as volatile to ensure that the Render Thread sees the changes in the trigger made by the MAVLink thread instantly (no CPU register caching).
Visual Indicator: The model flashes in RED if there is a 'resonance' anomaly.
See the attached Shot demo of the system in action using a 10Hz Python-based MAVLink stream.
