-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Chrysler: Parse LKAS button from steering wheel #1963
base: master
Are you sure you want to change the base?
Conversation
|
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.
I don't think I love the approach of adding a bunch of flags and conditionals.
All three cases are using reverse-engineered message/signal definitions, and are already pre-processed by the DBC generator. This means we're free to come up with a single message/signal naming scheme that opendbc can use with zero flags and conditionals, and I think we should do that.
Also, the pacifica_2017_hybrid
and ram_dt
cases may be redundant. They're named entirely differently, but they're the same CAN arb ID, message length, and signal bit offset for the LKAS button.
Lastly, if RAM_DT and RAM_HD don't share 816
and 650
(as this PR implies) then they shouldn't both be present in both generated DBCs, so we shouldn't add them both to HD in this PR and we should probably cleanup RAM_DT.
TL;DR: Tackle #1977 first, then this PR gets dramatically smaller.
Center_Stack_1
forRAM_HD
platformsRAM_CARS
platformsChryslerFlags
int flags to identify which button configuration a car uses