Chrysler: Parse LKAS button from steering wheel#1963
Chrysler: Parse LKAS button from steering wheel#1963sunnyhaibin wants to merge 1 commit intocommaai:masterfrom
Conversation
|
There was a problem hiding this comment.
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_1forRAM_HDplatformsRAM_CARSplatformsChryslerFlagsint flags to identify which button configuration a car uses