Decode CAN and CAN-FD traffic
Parse CAN and CAN-FD messages from supplied recordings or CAN dumps, then translate available signal definitions into engineering values.
Vehicle Networks & Communication
CAN signal decoding with DBC
CAN signal decoding converts message payloads into engineering values using signal definitions. I check bit layout, byte order, signedness, scaling, and multiplexing against your recordings and DBC, then deliver decoded results with the assumptions needed to interpret them.
Discuss CAN Signal DecodingProblems I can investigate
Find the behavior behind the symptom
- 01
ISO-TP communication failure
Trace segmented diagnostic transport behavior across CAN records to examine addressing, flow-control, and timing evidence associated with the failure.
- 02
CAN message missing
Compare expected communication with live traffic or recordings to identify where an expected CAN frame is absent and document the available evidence.
- 03
Unknown CAN signal
Examine payload fields across recordings and related DBC information to develop a cautious interpretation of signal meaning and encoding.
- 04
Incorrect CAN signal value
Check decoded values against the supplied system context and communication evidence to isolate discrepancies without assuming a single root cause.
What I can help with
Focused engineering work in Vehicle Networks & Communication
Analyze DBC-defined signals
Review message, signal, node, scaling, and metadata definitions in a DBC, identifying gaps or inconsistencies that affect interpretation.
Investigate recorded communication
Work from BLF or ASC recordings and use CANoe or CANalyzer exports and analysis context where available to examine message presence, timing, and signal behavior.
Build repeatable Python analysis
Create a maintainable workflow for parsing CAN data, applying available definitions, and producing consistent analysis results with Python, python-can, or cantools.
Examine transport and higher-layer context
Account for ISO-TP segmentation and J1939 communication context when those protocols are present in the supplied data.
What to send
Start with the evidence you already have
BLF recording
A Vector binary log containing timestamped bus communication.
ASC recording
A text-based Vector bus recording.
DBC
A CAN database defining messages and signals.
CAN dump
Raw or text-exported CAN frames.
Problem description
Observed symptoms, context, reproduction steps, and expected behavior.
How the analysis works
From recorded data to engineering findings
- 01
Review the supplied evidence
Confirm the available recordings, CAN dumps, DBC definitions, and problem description, then identify the communication scope and expected behavior.
- 02
Establish the decoding basis
Map available messages and signals from the DBC or other supplied definitions, while clearly separating documented values from interpretation.
- 03
Analyze communication behavior
Examine message presence, decoded values, and relevant ISO-TP or J1939 context across the supplied data.
- 04
Test candidate interpretations
Compare observations with reproduction steps and expected behavior, using focused scripts or analysis workflows where they improve repeatability.
- 05
Document findings and limits
Record the evidence, findings, unresolved questions, and assumptions so the result can be reviewed or reused by the engineering team.
What you receive
Deliverables matched to the investigation
CAN decoding results
Decoded CAN frames, signals, and interpretation notes.
Engineering analysis
A documented technical analysis with evidence and findings.
DBC file
A CAN database describing messages, signals, scaling, and nodes.
Python analysis script
A maintainable Python workflow for engineering-data analysis.
Restbus simulation
A simulation of missing network nodes and their communication.
Technologies & formats
Automotive data and analysis environments
- CAN
Controller Area Network
A priority-based broadcast bus used for in-vehicle control communication.
- DBC
CAN Database
A text format describing CAN messages, signals, nodes, scaling, and metadata.
- cantools
cantools
A Python package for parsing CAN databases and encoding or decoding messages.
- CAN-FD
CAN Flexible Data-rate
An extension of CAN with larger payloads and a faster data phase.
- 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
- Why can a decoded CAN signal have the wrong value?
- A wrong byte order, signedness, scale, offset, or multiplexor selection can change the decoded value even when the raw frame is correct. I compare the payload and DBC definition with a known operating condition before treating an unexpected value as a vehicle fault.
- What data is needed to start CAN signal decoding?
- A BLF recording, ASC recording, CAN dump, DBC, or problem description can provide a starting point. The most useful combination depends on whether the task is decoding, comparison, or investigation.
- Can you work without a DBC?
- Yes. A CAN dump or recording can still be examined for message presence and payload behavior, but signal interpretation may remain provisional where definitions are unavailable.
- Can you investigate a missing CAN message?
- Yes. I can compare the expected communication with the supplied live traffic or recording and document what is present, absent, and still uncertain.
- Do you handle ISO-TP communication failures?
- Yes. I can examine supplied CAN evidence for addressing, flow-control, and timing behavior associated with segmented transport, without assuming undocumented ECU behavior.
- What can the final output include?
- Depending on the evidence and scope, the work can produce CAN decoding results, engineering analysis, a DBC file, a Python analysis script, or a restbus simulation.
Discuss the evidence
Discuss CAN Signal Decoding
Send a recording, CAN dump, DBC, and short problem description. I will assess the available evidence and propose a focused decoding or analysis scope.