Signal regex#6
Closed
Murmele wants to merge 2 commits into
Closed
Conversation
…0) [0|204] "Km/h" DEVICE1,DEVICE2,DEVICE3 - multiple whitespaces at the end: SG_ TEMPERATURE : 48|16@1+ (0.01,-40) [-40|125] "C" DEVICE1,DEVICE2,DEVICE3
Contributor
Author
|
I did not find any documentation about the dbc which describes which characters are allowed and which not |
Owner
|
I think this was my original reference used (http://mcu.so/Microcontroller/Automotive/dbc-file-format-documentation_compress.pdf). The standard isn't really well defined and sort of custom sometimes I have found. I did / still do use the https://pypi.org/project/cantools/ as a reference for how they parse DBC files. |
Contributor
Author
|
Ah cool I searched for something like this, but indeed there is nothing which characters are allowed and which not. |
Contributor
Author
|
merged into #9 |
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
2 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.
It seems to be that the second case will be also parsed without the +, but I don't understand why, maybe you have an idea