-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VW PQ: Message updates, checksum and counter support #633
Merged
Merged
Changes from all commits
Commits
Show all changes
20 commits
Select commit
Hold shift + click to select a range
fd82dcb
refactor MQB checksum/counter to prep for PQ
jyoung8607 cb6d980
first pass at PQ checksums and counters
jyoung8607 0d30ee9
remove checksum and counter alignment checks
jyoung8607 bbb67a9
forgot HCA_1
jyoung8607 1701440
Revert "remove checksum and counter alignment checks"
jyoung8607 579f317
don't check counter offset
jyoung8607 c987ed0
tweak comment
jyoung8607 eef6620
handle checksum not starting at zero
jyoung8607 06f8c58
remove unused argument
jyoung8607 fac85f7
add LDW_Textbits to LDW_1
jyoung8607 838fa4e
Update can/common.cc
jyoung8607 944a024
Merge branch 'master' of https://github.com/commaai/opendbc into pq-c…
jyoung8607 02571d4
fix counter again; minimize diff
jyoung8607 7342679
additional door-open signals
jyoung8607 629169a
add trunk lid state
jyoung8607 a712a5b
update LDW_Status message and signals
jyoung8607 a78c458
typo
jyoung8607 6eecf6c
Merge branch 'master' into pq-checksum
jyoung8607 433ea88
Merge branch 'master' into pq-checksum
jyoung8607 2aae662
make XOR checksum generic
jyoung8607 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
think it would be nice to keep these names. how do you feel about using the unit field for this instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This has come up in discussion before; my first cut at MQB back in the day kept the signal names intact. I'm amenable to any good solution that lets us tag an existing canonically-named signal as "the checksum signal" or "the counter signal". I think last time I looked at it, there was some other means within the DBC file spec I wanted to use, but (ab)using units is possible too. I will dig up my old conversations and think about it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For DBCs where we want to keep the canonical signal names, I think the best thing is a DBC attribute that maps those signal names to their special usage. For DBCs that were created by hand and use the conventional CHECKSUM and COUNTER naming, we could fall through to using the name when the signal type attribute is entirely absent.
We could also get rid of the filename-based magic for selecting the checksum algorithm, even tweaking the algorithm per-message if we need to for situations like GM. I've seen MQB DBCs with our annoying pad byte lookup tables stored in the DBC in a similar way, which is something we could consider.
Something like this is a worthy goal, and I'm even willing to work on it at some point, but I'd rather not add a complex blocker for Volkswagen PQ dashcam upstream if that's okay. If you agree with the approach, I'd want to go back and unwind the signal names we changed years ago for MQB, and I can fix PQ at the same time.