Remove DBName From DBC Files#498
Merged
Merged
Conversation
DBName From DBC Files
2c84250 to
5542332
Compare
dchansen06
approved these changes
May 29, 2026
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
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.
Make DBC work in CANoe
Problem and Scope
DBName was generated as a field but left empty in DBC, which CANdb++ is okay with but CANoe doesnt like.
Description
Removed the two lines in DBCparser that generate the blank DBName field.
Gotchas and Limitations
Testing
Testing Details
plugged into my local CANoe, which doesnt always behave the same as testing device.
Larger Impact
Additional Context and Ticket