Convert CAN database data
Map the supplied database into the agreed target format and tool version. Check which attributes and multiplexing features can be preserved, and report unsupported fields before accepting the converted database.
Vehicle Networks & Communication
DBC conversion for reliable CAN data
Transform supplied CAN database definitions into an agreed DBC or supported target representation. Verify identifiers, bit layout, byte order, signedness, scaling, and multiplexing, and document information the target cannot represent. Recordings provide validation samples rather than a complete database definition.
Discuss a DBC ProjectProblems I can investigate
Find the behavior behind the symptom
- 01
DBC mismatch
A CAN database does not match the observed message layout, scaling, or software version. The mismatch can be reviewed against available recordings and CAN data.
- 02
CAN message missing
An expected CAN frame is absent from live traffic or a recording. The available data can be examined to distinguish missing definitions from missing communication.
- 03
Unknown CAN signal
The meaning or encoding of a CAN payload field is not documented. Recorded frames and existing DBC information can be compared to document supported interpretations.
- 04
Incorrect CAN signal value
A decoded signal is implausible or differs from the system state. Signal definitions, scaling, and observed CAN communication can be reviewed for inconsistencies.
What I can help with
Focused engineering work in Vehicle Networks & Communication
Decode recorded CAN communication
Process BLF recordings, ASC recordings, or CAN dumps to produce decoded frames and signals using the available database information.
Review CAN-FD and J1939 definitions
Examine DBC content associated with CAN, CAN-FD, or J1939 communication and identify inconsistencies in the available message and signal definitions.
Build repeatable conversion utilities
Develop a focused converter in Python using cantools or python-can where repeatable transformation and decoding are required.
What to send
Start with the evidence you already have
DBC
The current CAN database defining messages and signals, including any available scaling, nodes, and metadata.
BLF recording
A Vector binary log containing timestamped bus communication for comparison and decoding.
ASC recording
A text-based Vector bus recording used as an additional source of CAN communication data.
CAN dump
Raw or text-exported CAN frames for regression checks of the converted definitions; frames alone do not supply complete signal names, units, or semantics.
How the analysis works
From recorded data to engineering findings
- 01
Assess the available data
Review the DBC, recordings, and CAN dumps to establish what message definitions and observed communication are available.
- 02
Compare definitions with communication
Compare message layout, signal encoding, scaling, and observed frames to identify mismatches, absent messages, or unclear signal values.
- 03
Implement the conversion
Convert the source database using a parser or explicit mapping for the agreed formats. Record changes to attributes, comments, value tables, or multiplexing that the target representation cannot retain.
- 04
Check decoded results
Decode the same representative payloads with source and converted definitions, compare physical values, and check identifiers, bit positions, byte order, and scaling. Report every intended difference and unsupported feature.
What you receive
Deliverables matched to the investigation
DBC file
A CAN database describing messages, signals, scaling, and nodes.
CAN decoding results
Decoded CAN frames, signals, and interpretation notes based on the supplied data.
Engineering analysis
A documented technical analysis with evidence, findings, and identified data inconsistencies.
Data converter
A repeatable utility that transforms automotive data formats.
Technologies & formats
Automotive data and analysis environments
- DBC
CAN Database
A text format describing CAN messages, signals, nodes, scaling, and metadata.
- CAN
Controller Area Network
A priority-based broadcast bus used for in-vehicle control communication.
- CAN-FD
CAN Flexible Data-rate
An extension of CAN with larger payloads and a faster data phase.
- cantools
cantools
A Python package for parsing CAN databases and encoding or decoding messages.
- J1939
SAE J1939
A higher-layer vehicle network protocol suite using CAN, common in heavy vehicles.
- ISO-TP
ISO 15765-2 Transport Protocol
A segmented transport protocol for messages carried over CAN.
- CANoe
Vector CANoe
A development, simulation, test, and analysis environment for vehicle networks.
- CANalyzer
Vector CANalyzer
A Vector environment for recording and analyzing vehicle-network communication.
- python-can
python-can
A Python library providing a common API for CAN interfaces and messages.
- BLF
Binary Logging Format
A Vector binary container for timestamped bus communication.
- Python
Python
A general-purpose language widely used for automotive analysis, tooling, and automation.
FAQ
Practical questions before an investigation
- Can the conversion use an existing DBC?
- Yes. An existing DBC can be reviewed against a BLF recording, ASC recording, or CAN dump and updated or converted where the supplied data supports it.
- Can you work with CAN-FD data?
- CAN-FD data can be considered when it is represented in the supplied DBC or communication records. The available message and signal definitions determine the scope of decoding.
- Can you investigate an incorrect decoded signal value?
- Yes. The signal definition, scaling, observed CAN frames, and available system-state evidence can be compared to document likely inconsistencies without assuming a root cause.
- What is needed to start a DBC conversion?
- Provide the available DBC, BLF recording, ASC recording, or CAN dump, along with the intended conversion or review outcome.
Discuss the evidence
Discuss a DBC Project
Send the DBC or CAN recording you need reviewed, and I will confirm the useful inputs and a focused conversion scope.