8ac852b7d4
* initial signals for chrysler pacifica 2017 hybrid * add gear status PRNDL * tighten up speed bits. brake pressue max comment. * value table for gear status * speed of right vs left side of car * units for speed_right * Set packet lengths, adding steering rate, adjusted speed * Speed, braking, and distance signals * turn signals * Revert "turn signals" This reverts commit 91f6507031a989f8e15ee8fcf67c3a730ee1909f. * turn signals This time without accidentally overwriting energee's signals. * turn signal lights (and thus hazard lights) * high beams for genericToggle * high beams also. likely dashboard message. * acceleration pedal for gasPressed * seatbelt unbuckle message * LKAS lane-keeping assist dashboard indicators * auto park disable button * auto park turning on button * auto park signal unknown * autopark has control * another signal for autopark having control * autopark parallel and perpendicular mode. maybe turning wheel. * another auto park perpendicular bit * another bit for if autopark or human has control * another steering angle signal, this is more noisy and lags the other one. * blind spot warning signal why isn't the left warning near the right warning? * parksense disabled signal * lkas steering torque maaaaybe * correct size and signed for lkas maaaybe steering torque * lkas incrementer and checksum * lkas checksum thanks to work by Charlie Miller and Chris Valasek! * gear checksum, message lengths, better names * more message lengths and checksum * more lengths * the rest of the normal message lengths * lots more signals * blind spot left alert * autopark checksum * one more bit for energy curve * more braking * fix speed factor * radar messages for pacifica from private fusion canbus * change to standard COUNTER and CHECKSUM * another speed signal * dashboard signals, perhaps acc * ACC steering wheel buttons * unknown signals * more unknown signals * new type of message on private fusion * private fusion unknown messages * autopark turning status * more auto park * fix wheel speed signal size * radar distance signal fix * radar LAT_DIST, LONG_DIST and guesses for REL_ACCEL and REL_SPEED * speeds that correspond with long dist messages * units for the d_* REL_SPEED * acc speed config units * ACC accel and decel * ACC braking messages * guesses for ACC * more acc * random signals * fix lkas signal, gas vs electric signals * steering angle units * switch PRNDL to big endian because I suspect cabana and OP CanParser do not work the same way for little endian. * switch the signals OP uses to big endian to work around little endian limitation * wheel speed factors and fix side speeds * ACC cancel button |
||
---|---|---|
generator | ||
.gitignore | ||
README.md | ||
__init__.py | ||
acura_ilx_2016_can_generated.dbc | ||
acura_ilx_2016_nidec.dbc | ||
acura_rdx_2018_can_generated.dbc | ||
cadillac_ct6_chassis.dbc | ||
cadillac_ct6_object.dbc | ||
cadillac_ct6_powertrain.dbc | ||
chrysler_pacifica_2017_hybrid.dbc | ||
chrysler_pacifica_2017_hybrid_private_fusion.dbc | ||
ford_cgea1_2_bodycan_2011.dbc | ||
ford_cgea1_2_ptcan_2011.dbc | ||
ford_fusion_2018_adas.dbc | ||
ford_fusion_2018_pt.dbc | ||
gm_global_a_chassis.dbc | ||
gm_global_a_lowspeed.dbc | ||
gm_global_a_lowspeed_1818125.dbc | ||
gm_global_a_object.dbc | ||
gm_global_a_powertrain.dbc | ||
honda_accord_lx15t_2018_can_generated.dbc | ||
honda_accord_s2t_2018_can_generated.dbc | ||
honda_accord_touring_2016_can.dbc | ||
honda_civic_hatchback_ex_2017_can_generated.dbc | ||
honda_civic_touring_2016_can_generated.dbc | ||
honda_clarity_hybrid_2018_can.dbc | ||
honda_crv_ex_2017_can_generated.dbc | ||
honda_crv_touring_2016_can_generated.dbc | ||
honda_fit_ex_2018_can_generated.dbc | ||
honda_insight_ex_2019_can_generated.dbc | ||
honda_odyssey_exl_2018_generated.dbc | ||
honda_odyssey_extreme_edition_2018_china_can.dbc | ||
honda_pilot_touring_2017_can_generated.dbc | ||
honda_ridgeline_black_edition_2017_can_generated.dbc | ||
hyundai_2015_ccan.dbc | ||
hyundai_2015_mcan.dbc | ||
hyundai_i30_2014.dbc | ||
hyundai_santa_fe_2019_ccan.dbc | ||
kia_sorento_2018.dbc | ||
lexus_is_2018_pt_generated.dbc | ||
lexus_rx_hybrid_2017_pt_generated.dbc | ||
mercedes_benz_e350_2010.dbc | ||
subaru_outback_2016_eyesight.dbc | ||
tesla_can.dbc | ||
toyota_avalon_2017_pt_generated.dbc | ||
toyota_camry_hybrid_2018_pt_generated.dbc | ||
toyota_chr_2018_pt_generated.dbc | ||
toyota_chr_hybrid_2018_pt_generated.dbc | ||
toyota_corolla_2017_pt_generated.dbc | ||
toyota_highlander_2017_pt_generated.dbc | ||
toyota_highlander_hybrid_2018_pt_generated.dbc | ||
toyota_iQ_2009_can.dbc | ||
toyota_prius_2010_pt.dbc | ||
toyota_prius_2017_adas.dbc | ||
toyota_prius_2017_pt_generated.dbc | ||
toyota_rav4_2017_pt_generated.dbc | ||
toyota_rav4_hybrid_2017_pt_generated.dbc | ||
vw_golf_mk4.dbc | ||
vw_mqb_2010.dbc |
README.md
opendbc
The project to democratize access to the decoder ring of your car.
DBC file basics
A DBC file encodes, in a humanly readable way, the information needed to understand a vehicle's CAN bus traffic. A vehicle might have multiple CAN buses and every CAN bus is represented by its own dbc file. Wondering what's the DBC file format? Here and Here a couple of good overviews.
How to start reverse engineering cars
opendbc is integrated with cabana.
Use panda to connect your car to a computer.
DBC file preprocessor
DBC files for different models of the same brand have a lot of overlap. Therefore, we wrote a preprocessor to create DBC files from a brand DBC file and a model specific DBC file. The source DBC files can be found in the generator folder. After changing one of the files run the generator.py script to regenerate the output files. These output files will be placed in the root of the opendbc repository and are suffixed by _generated.
Good practices for contributing to opendbc
-
Comments: the best way to store comments is to add them directly to the DBC files. For example:
CM_ SG_ 490 LONG_ACCEL "wheel speed derivative, noisy and zero snapping";
is a comment that refers to signal
LONG_ACCEL
in message490
. Using comments is highly recommended, especially for doubts and uncertainties. cabana can easily display/add/edit comments to signals and messages. -
Units: when applicable, it's recommended to convert signals into physical units, by using a proper signal factor. Using a SI unit is preferred, unless a non-SI unit rounds the signal factor much better. For example:
SG_ VEHICLE_SPEED : 7|15@0+ (0.00278,0) [0|70] "m/s" PCM
is better than:
SG_ VEHICLE_SPEED : 7|15@0+ (0.00620,0) [0|115] "mph" PCM
However, the cleanest option is really:
SG_ VEHICLE_SPEED : 7|15@0+ (0.01,0) [0|250] "kph" PCM
-
Signal's size: always use the smallest amount of bits possible. For example, let's say I'm reverse engineering the gas pedal position and I've determined that it's in a 3 bytes message. For 0% pedal position I read a message value of
0x00 0x00 0x00
, while for 100% of pedal position I read0x64 0x00 0x00
: clearly, the gas pedal position is within the first byte of the message and I might be tempted to define the signalGAS_POS
as:SG_ GAS_POS : 7|8@0+ (1,0) [0|100] "%" PCM
However, I can't be sure that the very first bit of the message is referred to the pedal position: I haven't seen it changing! Therefore, a safer way of defining the signal is:
SG_ GAS_POS : 6|7@0+ (1,0) [0|100] "%" PCM
which leaves the first bit unallocated. This prevents from very erroneous reading of the gas pedal position, in case the first bit is indeed used for something else.