209d968b75
* Create V40.dbc Added V40 dbc * OpenDBC updates * OpenDBC updates * OpenDBC updates * OpenDBC updates * Cruise control buttons added * CC buttons update * OpenDBC updates * Deciphered most important part of LKA message * OpenDBC updates * Steering angle from DBC scaling update * OpenDBC updates * OpenDBC updates * Update V40.dbc * OpenDBC updates * OpenDBC updates * OpenDBC updates * Added volvo v40 * Deleted V40.dbc * OpenDBC updates gear mode * OpenDBC updates * OpenDBC updates * OpenDBC updates * OpenDBC updates * OpenDBC updates * OpenDBC updates * OpenDBC updates * Firstupdate * OpenDBC updates * Accelerator Pedal * Brake pedal * OpenDBC updates * OpenDBC updates * OpenDBC updates * OpenDBC updates * OpenDBC updates * Added messages from camera * OpenDBC updates * OpenDBC updates * OpenDBC updates * OpenDBC updates * Fix typo in volvo v40 dbc * Renamed v60 dbc * OpenDBC updates * Updated fromFSM messages from new input * Added CCButtons V60 * OpenDBC updates * OpenDBC updates * Finetuned dbc files volvo v60 fromServo1 SteeringAngle scaling update Wheelspeeds OpenDBC updates OpenDBC updates OpenDBC updates OpenDBC updates OpenDBC updates OpenDBC updates OpenDBC updates OpenDBC updates OpenDBC updates OpenDBC updates OpenDBC updates OpenDBC updates OpenDBC updates OpenDBC updates * OpenDBC updates * Harmonize volvo dbc * Update naming on FSM V40 OpenDBC updates diagmsgadded Added diagnostic addresses for v60 Add diag v40 v60 Tested and working diagnostic request. Flowcontrol not tested. * V40 updated with information by sender. V40 & V60 diagnostic ids fixexd * Create V40.dbc Added V40 dbc * OpenDBC updates * OpenDBC updates * OpenDBC updates * OpenDBC updates * Cruise control buttons added * CC buttons update * OpenDBC updates * Deciphered most important part of LKA message * OpenDBC updates * Steering angle from DBC scaling update * OpenDBC updates * Update V40.dbc * OpenDBC updates * OpenDBC updates * OpenDBC updates * Added volvo v40 * Deleted V40.dbc * OpenDBC updates gear mode * OpenDBC updates * OpenDBC updates * OpenDBC updates * OpenDBC updates * OpenDBC updates * OpenDBC updates * Firstupdate * OpenDBC updates * Brake pedal * OpenDBC updates * OpenDBC updates * OpenDBC updates * OpenDBC updates * OpenDBC updates * Added messages from camera * OpenDBC updates * OpenDBC updates * OpenDBC updates * Fix typo in volvo v40 dbc * Renamed v60 dbc * OpenDBC updates * Updated fromFSM messages from new input * Added CCButtons V60 * OpenDBC updates * OpenDBC updates * Finetuned dbc files volvo v60 fromServo1 SteeringAngle scaling update Wheelspeeds OpenDBC updates OpenDBC updates OpenDBC updates OpenDBC updates OpenDBC updates OpenDBC updates OpenDBC updates OpenDBC updates OpenDBC updates OpenDBC updates OpenDBC updates OpenDBC updates OpenDBC updates OpenDBC updates * OpenDBC updates * Harmonize volvo dbc * Update naming on FSM V40 OpenDBC updates diagmsgadded Added diagnostic addresses for v60 Add diag v40 v60 Tested and working diagnostic request. Flowcontrol not tested. * V40 updated with information by sender. V40 & V60 diagnostic ids fixexd * Corrected diag byte response * CEM and PSCM diag request had mixed up addresses. * Add static fields to lka steering request v60. * FsmSteerRequest update * Updated scaling on SteeringAngle signals for v40 after new test. * OpenDBC updates * Update V40 to support fix in dtc set on FSM * PSCM Servo1 v60 update * OpenDBC updates * Updated Volvo DBCs, renaming some signals * Updated volvo v40 * Updated volvo v40 with CVM message * diagCVM and v60 PSCM messages * Rename lka signal, add global request for diagnostic. * Renamed and updated steeringwheelangle * Fix scaling bug v40 * Add readback signals of CCbuttons from ECM * OpenDBC updates * OpenDBC updates * OpenDBC updates * Seatbelt Driver * OpenDBC updates * Seatbelt updates * Sorted in numerical order Co-authored-by: Comma Device <device@comma.ai> |
||
---|---|---|
.github/workflows | ||
can | ||
generator | ||
.gitignore | ||
.pre-commit-config.yaml | ||
Dockerfile | ||
ESR.dbc | ||
README.md | ||
SConstruct | ||
__init__.py | ||
acura_ilx_2016_can_generated.dbc | ||
acura_ilx_2016_nidec.dbc | ||
acura_rdx_2018_can_generated.dbc | ||
bmw_e9x_e8x.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 | ||
ford_lincoln_base_pt.dbc | ||
gm_global_a_chassis.dbc | ||
gm_global_a_high_voltage_management.dbc | ||
gm_global_a_lowspeed.dbc | ||
gm_global_a_lowspeed_1818125.dbc | ||
gm_global_a_object.dbc | ||
gm_global_a_powertrain.dbc | ||
gm_global_a_powertrain_expansion.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_sedan_16_diesel_2019_can_generated.dbc | ||
honda_civic_touring_2016_can_generated.dbc | ||
honda_clarity_hybrid_2018_can_generated.dbc | ||
honda_crv_ex_2017_body_generated.dbc | ||
honda_crv_ex_2017_can_generated.dbc | ||
honda_crv_executive_2016_can_generated.dbc | ||
honda_crv_hybrid_2019_can_generated.dbc | ||
honda_crv_touring_2016_can_generated.dbc | ||
honda_fit_ex_2018_can_generated.dbc | ||
honda_fit_hybrid_2018_can_generated.dbc | ||
honda_hrv_touring_2019_can_generated.dbc | ||
honda_insight_ex_2019_can_generated.dbc | ||
honda_odyssey_exl_2018_generated.dbc | ||
honda_odyssey_extreme_edition_2018_china_can_generated.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_kia_generic.dbc | ||
lexus_ct200h_2018_pt_generated.dbc | ||
lexus_gs300h_2017_pt_generated.dbc | ||
lexus_is_2018_pt_generated.dbc | ||
lexus_nx300h_2018_pt_generated.dbc | ||
lexus_rx_350_2016_pt_generated.dbc | ||
lexus_rx_hybrid_2017_pt_generated.dbc | ||
luxgen_s5_2015.dbc | ||
mazda_3_2019.dbc | ||
mazda_2017.dbc | ||
mercedes_benz_e350_2010.dbc | ||
nissan_leaf_2018.dbc | ||
nissan_x_trail_2017.dbc | ||
requirements.txt | ||
subaru_forester_2017_generated.dbc | ||
subaru_global_2017_generated.dbc | ||
subaru_global_2020_hybrid_generated.dbc | ||
subaru_outback_2015_generated.dbc | ||
subaru_outback_2019_generated.dbc | ||
tesla_can.dbc | ||
tesla_radar.dbc | ||
toyota_2017_ref_pt.dbc | ||
toyota_adas.dbc | ||
toyota_avalon_2017_pt_generated.dbc | ||
toyota_camry_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_nodsu_hybrid_pt_generated.dbc | ||
toyota_nodsu_pt_generated.dbc | ||
toyota_prius_2010_pt.dbc | ||
toyota_prius_2017_pt_generated.dbc | ||
toyota_rav4_2017_pt_generated.dbc | ||
toyota_rav4_hybrid_2017_pt_generated.dbc | ||
toyota_sienna_xle_2018_pt_generated.dbc | ||
toyota_tss2_adas.dbc | ||
volvo_v40_2017_pt.dbc | ||
volvo_v60_2015_pt.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.
How to use reverse engineered DBC
To create custom CAN simulations or send reverse engineered signals back to the car you can use CANdevStudio project.
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 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.