CAN RX Callback with Identifiers #190
Open
+15
−10
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
dchansen06
requested changes
Jan 27, 2026
Contributor
dchansen06
left a comment
dchansen06
left a comment
There was a problem hiding this comment.
Please provide both the message ID GR_OLD_MSG_ID and the sending node ID GR_OLD_NODE_ID (both are held in the underlying identifier, see CANutils.c)
dchansen06
added
Enhancement
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.
CAN RX Callback with Identifiers
Problem and Scope
The current CAN RX Callback does not pass in the message ID.
Description
The RX callback typedef now passes in the message ID as an additional parameter
GR_OLD_MSG_ID id.Gotchas and Limitations
Testing
Testing Details
Larger Impact
Additional Context and Ticket