Reverse engineered Hyundai Kona Electric DBC file(s), work in progress.
pcan.dbcapplies to PCAN (Powertrain) CAN Bus. This is where most of the effort has been put in. Some messages have comments indicating if the same message is forwarded unmodified to multiple buses.bcan.dbcapplies to BCAN (Body) CAN Bus.comp_can.dbcapplies to the "COMP CAN" bus that links the A/C controller (FATC), A/C compressor and the PTC heater modules only.
- Diagnostics.md contains a partial list of diagnostic CAN IDs.
Messages copied from other sources may not follow these conventions (yet!)
- Currently the message naming follows convention
SourceModule_HEXID, i.e.VCU_333is ID 0x333 sent by VCU (Vehicle Control Unit). - To make it quicker to find some messages, some are named
SourceModule_HEXID_Name, i.e.VCU_523_TEMPis temperature information sent on ID 0x523 by VCU. UNKstands for unknown, i.e.UNK_471is ID 0x471 sent by an unknown module.
This file includes information pieced together from the following sources. Massive gratitude to everyone who has worked on decoding Hyundai/Kia CAN messages, and/or who has posted CAN logs from vehicles online!
- Large body of CAN logs hosted at https://github.com/projectgus/hyundai-kona-ev-can-logs/
- comma.ai opendbc repo hyundai_kia_generic.dbc.
- uhi22's Ioniq DBC file.
- Eric Router's spreadsheet of PCAN messages, see also this comment. Eric also did a bunch of VESS hacking (code, video).
- "vin" on openinverter's CAN log for 2020 Ioniq BMU with nothing else connected.
- "powertop" on openinverter has a spreadsheet with CAN message content summaries here (see also post).
- Kia Soul EV Message spreadsheet (dates from ~2016 or so, I believe the author to be Elmil and other users from the My Kia Soul EV forum.)
Where possible the git log for the DBC file includes some comments on what the source for a particular addition or change is.
To any extent applicable, these DBC files are licensed under the MIT License as described in the file LICENSE.
Please note very carefully the disclaimer of warranty in the MIT License. These DBC files are the product of reverse engineering and should be regarded as completely untrustworthy!
Note: For Copyright purposes, I don't consider this DBC file to be a "derived work" of any of the linked information resources. DBC file content is mostly simple facts, which are generally not copyrightable on their own. The information we're collecting here is an aggregation of simple facts - i.e. message X field Y means Z. In the same spirit, if you take information from this DBC and apply it somewhere else - that isn't copying the entire file - then I don't believe you need to worry about the source copyright or DBC file license information. Of course, I'm very grateful if you re-share your work and credit the sources you got it from - that's the decent thing to do, regardless!