democratize access to car decoder rings
Switch branches/tags
Nothing to show
Clone or download
energee and rbiasini Adds Chinese Odyssey DBC (#110)
* Adds Chinese Odyssey DBC

* Fixed some steering-related things

* Update honda_odyssey_extreme_edition_2018_china_can.dbc

* Flip steer signal
Latest commit 42f8c12 Sep 17, 2018
Permalink
Failed to load latest commit information.
generator Syntax and encoding fixes (#111) Sep 17, 2018
.gitignore make opendbc import work, and ignore junk Jun 5, 2017
README.md Updated README with a recommended overview May 19, 2018
__init__.py make opendbc import work, and ignore junk Jun 5, 2017
acura_ilx_2016_can_generated.dbc Honda: forgot to generate dbc files Aug 16, 2018
acura_ilx_2016_nidec.dbc Honda Nidec: added wrong config radar value Jul 23, 2018
acura_rdx_2018_can_generated.dbc Honda: forgot to generate dbc files Aug 16, 2018
cadillac_ct6_chassis.dbc Cadillac: typo Jun 13, 2018
cadillac_ct6_object.dbc Cadillac: add object bus dbc May 24, 2018
cadillac_ct6_powertrain.dbc Syntax and encoding fixes (#111) Sep 17, 2018
chrysler_pacifica_2017_hybrid.dbc 🚐 more chrysler pacifica signals (#84) Jul 27, 2018
chrysler_pacifica_2017_hybrid_private_fusion.dbc 🚐 more chrysler pacifica signals (#84) Jul 27, 2018
ford_cgea1_2_bodycan_2011.dbc ford cgea 1.2 2011 (#32) Oct 5, 2017
ford_cgea1_2_ptcan_2011.dbc ford cgea 1.2 2011 (#32) Oct 5, 2017
ford_fusion_2018_adas.dbc Ford Fusion: added radar dbc file Apr 25, 2018
ford_fusion_2018_pt.dbc Ford Fusion: added brake and doors info May 3, 2018
gm_global_a_chassis.dbc GM: typo Jun 13, 2018
gm_global_a_lowspeed.dbc Volt: switch to parsing ACC buttons from powertrain CAN (#74) Feb 20, 2018
gm_global_a_lowspeed_1818125.dbc Update gm_global_a_lowspeed_1818125.dbc (#34) Oct 10, 2017
gm_global_a_object.dbc convert all line endings to unix style Feb 12, 2018
gm_global_a_powertrain.dbc Syntax and encoding fixes (#111) Sep 17, 2018
honda_accord_lx15t_2018_can_generated.dbc Honda: forgot to generate dbc files Aug 16, 2018
honda_accord_s2t_2018_can_generated.dbc Honda: forgot to generate dbc files Aug 16, 2018
honda_accord_touring_2016_can.dbc convert all line endings to unix style Feb 12, 2018
honda_civic_hatchback_ex_2017_can_generated.dbc Honda: forgot to generate dbc files Aug 16, 2018
honda_civic_touring_2016_can_generated.dbc Syntax and encoding fixes (#111) Sep 17, 2018
honda_clarity_hybrid_2018_can.dbc fix bugs in some counter/checksum definitions Jan 29, 2018
honda_crv_ex_2017_can_generated.dbc Honda: forgot to generate dbc files Aug 16, 2018
honda_crv_touring_2016_can_generated.dbc Honda: forgot to generate dbc files Aug 16, 2018
honda_fit_ex_2018_can_generated.dbc Honda: forgot to generate dbc files Aug 16, 2018
honda_odyssey_exl_2018_generated.dbc Honda: forgot to generate dbc files Aug 16, 2018
honda_odyssey_extreme_edition_2018_china_can.dbc Adds Chinese Odyssey DBC (#110) Sep 17, 2018
honda_pilot_touring_2017_can_generated.dbc Honda: forgot to generate dbc files Aug 16, 2018
honda_ridgeline_black_edition_2017_can_generated.dbc Honda: forgot to generate dbc files Aug 16, 2018
hyundai_2015_ccan.dbc Hyundai: not sure why steer angle was unigned... seems a bug Aug 30, 2018
hyundai_2015_mcan.dbc add hyundai 2015 (#63) Dec 28, 2017
hyundai_i30_2014.dbc add hyundai_i30_2014.dbc Sep 10, 2017
hyundai_santa_fe_2019_ccan.dbc Santa Fe: dealing with steer torque integer is easier for now Aug 25, 2018
kia_sorento_2018.dbc This adds support for 8 Speed Auto Tranismission (#104) Jul 28, 2018
lexus_rx_hybrid_2017_pt_generated.dbc Toyota Pedal Support (#108) Aug 24, 2018
mercedes_benz_e350_2010.dbc Update mercedes e350 dbc (#112) Sep 17, 2018
subaru_outback_2016_eyesight.dbc Add chffr metrics for cars Sep 10, 2017
tesla_can.dbc Tesla: Add missing line break after VAL_ 69 WprSw6Posn (#109) Sep 2, 2018
toyota_avalon_2017_pt_generated.dbc Toyota Pedal Support (#108) Aug 24, 2018
toyota_camry_hybrid_2018_pt_generated.dbc Toyota Pedal Support (#108) Aug 24, 2018
toyota_chr_2018_pt_generated.dbc Toyota Pedal Support (#108) Aug 24, 2018
toyota_chr_hybrid_2018_pt_generated.dbc Toyota Pedal Support (#108) Aug 24, 2018
toyota_corolla_2017_pt_generated.dbc Toyota Pedal Support (#108) Aug 24, 2018
toyota_highlander_2017_pt_generated.dbc Toyota Pedal Support (#108) Aug 24, 2018
toyota_highlander_hybrid_2018_pt_generated.dbc Toyota Highlander: fixed dbc file name Sep 3, 2018
toyota_iQ_2009_can.dbc Created toyota iQ base plus reversed some signals (#48) Nov 5, 2017
toyota_prius_2017_adas.dbc Toyota: changed dbc names Oct 10, 2017
toyota_prius_2017_pt_generated.dbc Toyota Pedal Support (#108) Aug 24, 2018
toyota_rav4_2017_pt_generated.dbc Toyota Pedal Support (#108) Aug 24, 2018
toyota_rav4_hybrid_2017_pt_generated.dbc Toyota Pedal Support (#108) Aug 24, 2018
vw_golf_mk4.dbc Create vw_golf_mk4.dbc Sep 22, 2017
vw_mqb_2010.dbc Create vw_mqb_2010.dbc Oct 1, 2017

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 message 490. 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 read 0x64 0x00 0x00: clearly, the gas pedal position is within the first byte of the message and I might be tempted to define the signal GAS_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.