DBC file

CAN databaseCAN DBC.dbcCAN message definition file

A DBC file is a text database that describes how to decode CAN bus messages into physical values. For each message ID it lists the signals inside, with their start bit, length, byte order, signedness, scale, offset and unit. Loggers, dashboards and engine controllers use it to share data consistently.Medium123

How it works

A CAN frame carries an identifier and up to 8 data bytes in classical CAN, or up to 64 in CAN FD, but the bytes have no meaning on their own. The DBC file is the agreed map. It names each message, its ID and length, which node sends it, and where each signal sits in the payload.Medium41

Each signal is converted with a linear rule: physical value = offset + scale × raw value. A coolant temperature signal might use scale 1 and offset -40, so raw 130 means 90 °C. Byte order is either little-endian (Intel) or big-endian (Motorola), and getting it wrong produces nonsense values.Medium1

Inside the file, a BO_ line defines a message by its ID in decimal, name, length and sending node. SG_ lines define each signal with start bit, length, byte order, sign, scale, offset, range and unit. VAL_ lines map raw numbers to text states, such as gear positions or switch states.1

Extended 29-bit IDs are stored with bit 31 of a 32-bit number set, so extended ID 0x123 appears as 2147483939. Multiplexed signals, marked M and m, let one ID carry different signal sets chosen by a multiplexor value, which is how OBD-II responses are usually described.1

The format was created by Vector Informatik and has become a de facto standard across CAN tools, although Vector has not published a formal specification. Most syntax guides come from third-party tool makers.Medium1

Typical values

Classical CAN payload0-8 bytes (up to 64 bits) per frameSourced24
CAN FD payloadUp to 64 bytes per frameSourced2
Byte order codes
  • @1 = Intellittle-endian
  • @0 = Motorolabig-endian
Sourced1
Sign codes
  • + = unsigned
  • - = signed
Sourced1
Extended ID encodingCAN ID with bit 31 setID + 0x80000000Keeps 29-bit IDs distinct from 11-bit IDsSourced1
Scaling rulephysical = offset + scale × rawSourced1
J1939 engine speed (EEC1, SPN 190)16 bits, 0.125 rpm per bit, offset 0Published SAE J1939 definitionSourced17

How an ECU uses it

An ECU does not read a DBC at run time.

Its firmware has the message layout built in, and the DBC documents that layout for other devices. Configurable controllers, dashes and loggers import a DBC to build their receive and transmit tables.Medium1

When an ECU receives data, such as wheel speeds from an ABS module, it must use the same definition as the sender. A scale or byte-order mismatch passes straight into traction or launch strategies as a wrong number, and no CAN error frame warns you, because the frame itself is valid.Medium16

How to test it

5 checks, in order.

  1. Capture a raw log with a USB CAN interface in listen-only mode at the bus bit rate. Note the conditions while logging: key-on engine off, idle, and a slow throttle sweep.5
  2. Load the DBC and the log into a decoding tool. Confirm every expected ID appears; an ID defined in the DBC but absent from the log suggests the wrong DBC version or an 11-bit versus 29-bit mismatch.Medium1
  3. Check each signal against a known value: rpm zero at key-on, manifold pressure equal to barometric pressure, coolant equal to ambient on a cold engine. A wrong factor points to scale; scrambled values point to byte order or start bit.Medium1
  4. Sweep a signal through its range, such as throttle from closed to wide open, and look for jumps. A jump halfway through the raw range suggests a signed or unsigned mix-up; jumps every 256 counts suggest the wrong byte order.Medium1
  5. Open the file in an editor with consistency checks, such as Vector CANdb++ or the Kvaser Database Editor, to catch overlapping signals and lengths that exceed the message.Medium1

Symptoms and causes

A signal reads huge numbers or jumps wildly.

Likely causes Wrong byte order or wrong start bit.

Check Swap Intel and Motorola for that signal and recheck at a known state.

1

The shape is right but the magnitude is wrong.

Likely causes Wrong scale, unit or offset, such as a missing -40 offset on a temperature.

Check Compare against a known condition, like ambient temperature on a cold engine.

1

Negative values show as large positive numbers.

Likely causes Signal defined as unsigned but sent as signed.

Check Change + to - and recheck at a known negative condition.

1

A message never decodes.

Likely causes ID entered in hex instead of decimal, extended flag missing, or wrong multiplexor value.

Check Compare the raw IDs in the log with the decimal BO_ IDs in the file.

1

Values correct on one car, wrong on another.

Likely causes Different model year, platform or software version.

Check Verify each car against known values before trusting the file.

Low13

In tuning

When connecting an engine controller to a dash, power module or logger, export the transmitting device's message definitions as a DBC and import them on the receiving side. This avoids hand-typed scaling errors and keeps both ends in step after changes.Medium12

For third-party vehicles, use message definitions the manufacturer or device vendor publishes. Reverse-engineered definitions from the internet are unverified and may be wrong for your model year.Low13

Formula and worked example

physical = offset + scale × raw
physical
decoded engineering value
raw
unsigned or signed integer extracted from the signal's bits
scale
factor from the DBC signal definition
offset
offset from the DBC signal definition
Medium1

Common mistakes

Mistake Entering a message ID in hex where the DBC expects decimal.

Do instead BO_ IDs are decimal, so 0x100 is written 256. Use a DBC editor instead of hand-editing.1

Mistake Forgetting the extended flag on 29-bit messages.

Do instead Set bit 31 (add 2147483648) or use the editor's extended-frame option.1

Mistake Using a DBC found online for a different car or model year.

Do instead Use definitions the maker publishes and confirm each signal against known values.Low13

Myths vs facts

Myth A DBC file lets you change what a car's modules do.

Fact It only describes how to interpret messages. It does not alter any module's behavior; it is a decoding dictionary for reading or, when sending is authorized, for formatting messages.Medium12

Myth Any DBC for a model works on every year of that model.

Fact Message IDs and signal layouts change between platforms and software versions. A file that decodes one car correctly can be wrong for another, so check decoded values against known conditions.Low13

Myth DBC is an ISO standard format.

Fact It is a Vector Informatik format that became a de facto standard. Vector has not published a formal specification, so tools occasionally differ on rarely used features.Medium1

Frequently asked

What is a DBC file?

A DBC file is a text database that tells software how to turn raw CAN frames into named values with units. For each message ID it lists the signals, their bit positions, byte order, scale and offset. Loggers, dashes and controllers use it so both ends of a link agree.Medium12

How do you decode CAN data with a DBC file?

Load the DBC into a CAN tool or logger along with the raw log. The tool matches each frame's ID to a message in the DBC, extracts each signal's bits using its start bit, length and byte order, then applies physical = offset + scale × raw to give values with units.Medium1

What is byte order in a DBC file?

It tells the decoder how multi-byte signals are arranged. Little-endian, called Intel, stores the least significant byte first; big-endian, called Motorola, stores the most significant byte first. Using the wrong one scrambles the value, which is a common cause of nonsense readings when building a DBC by hand.Medium1

Where do I get a DBC file for my car?

Device makers often publish DBCs for their own products, such as dashes, sensors and controllers. Vehicle manufacturers generally do not publish their internal CAN definitions. Community files exist but are unverified, so treat them with caution and confirm values against known readings before relying on them.Low13

What program opens a DBC file?

Any text editor can open a DBC because it is plain text, but a DBC editor is safer. Options include Vector CANdb++, the Kvaser Database Editor, CSS Electronics' online editor and the open-source canmatrix Python module. Editors check for overlapping signals and length errors.Medium1

Sources

Numbered as cited above. Hover or tap a citation chip to preview it.

  1. CAN DBC File Explained: A Simple Intro · CSS Electronics · vendor-doc · retrieved 2026-10-27
  2. CAN bus · Wikipedia · reference · retrieved 2026-10-27
  3. Controller Area Network (CAN BUS) Protocol tutorial · Kvaser · vendor-doc · retrieved 2026-10-27
  4. ISO 11898-1:2024 Road vehicles, Controller area network (CAN), Part 1: Data link layer and physical coding sublayer · International Organization for Standardization · standard · retrieved 2026-10-27
  5. CAN Bus Explained: A Simple Intro · CSS Electronics · vendor-doc · retrieved 2026-10-27
  6. CAN Bus Errors Explained: A Simple Intro · CSS Electronics · vendor-doc · retrieved 2026-10-27
  7. SAE J1939: Serial Control and Communications Heavy Duty Vehicle Network, top level document · SAE International · standard · retrieved 2026-10-27