Converting a DBC file to Excel — what to export and what to watch out for

"Send me the DBC as an Excel" is a weekly request in automotive projects: review meetings, supplier discussions and test-spec writing all happen in spreadsheets. But a naive conversion loses exactly the information that makes a DBC useful. Here is what a good DBC-to-Excel export contains.

The columns that matter

A signal is only fully defined by all of its properties together. Your export should include, per signal:

• Message: name, CAN ID (flag extended frames), DLC, cycle time
• Signal: name, start bit, length, byte order (Intel/Motorola), signedness
• Scaling: factor and offset — this is where raw counts become engineering units
• Range: minimum and maximum physical values
• Metadata: unit, value descriptions (VAL_ tables), and the comment from CM_ lines

Pitfall 1: exporting raw values instead of physical values

A signal with factor 0.001 and offset -40 does not carry 0.001 and -40 as data — it defines a mapping. Your spreadsheet must show the physical range (min/max after scaling), not the raw bit range. Reviewers think in degC and rpm, not in counts.

Pitfall 2: losing multiplexed signals

Multiplexed signals (mux selectors and multiplexed children) are only valid for certain values of the selector. A flat table hides that relationship. Either flag multiplexed signals in a dedicated column, or note the mux value they belong to.

Pitfall 3: encoding damage

DBC comments often contain German umlauts, French accents or Chinese characters. A conversion path that forces ASCII turns every comment into question marks. Export as UTF-8 (Excel opens UTF-8 CSV correctly when a BOM is present, or use XLSX which stores text natively).

Doing it without a script

CANpeek's DBC viewer lets you inspect the full database in the browser and export a preview sample — parsing and export both run locally, so confidential databases never leave your PC. Everything available today is free to use; there is currently no paid product. The current preview exports the first 20 rows. Full export and batch conversion will be available when Pro launches.

Message,MessageID,Extended,DLC,CycleMs,Signal,StartBit,Length,ByteOrder,Signed,Factor,Offset,Min,Max,Unit,Comment
EngineData,0x100,No,8,10,EngineSpeed,0,16,Intel,No,0.25,0,0,8000,rpm,Raw engine speed feedback
EngineData,0x100,No,8,10,CoolantTemp,16,8,Intel,Yes,1,-40,-40,215,degC,PT1-filtered sensor value

One row per signal, one header — that structure survives pivot tables, VLOOKUPs and supplier review cycles.