Add 'relative' property for COB-ID vars relative to the node-ID #281
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
|
@christiansandberg Any objections to adding this? I would like to use Python canopen to auto-generate C-code from EDS files for use in a native CANopen stack for the Zephyr RTOS, but I need to be able to determine if a given object entry contains a COB-ID relative to the node-ID. We are already using Python canopen in Zephyr for performing program download (CiA302-3) and all the Zephyr CANopen examples contain Python canopen snippets for testing device functionality. |
|
Sorry for the late feedback. I guess it wouldn't hurt to add another property if it will helpful. |
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.
Add 'relative' property for COB-ID vars relative to the node-ID.
I have used the term "relative" only since I could not come up with something better (and CiA306-1 doesn't really help here). Other suggestions are most welcome.