Align the integration configuration
Review controller capabilities, nominal and data bit rates, bit-rate switching, accepted frame types, and gateway mappings. Define changes with the team responsible for the target configuration.
Vehicle Networks & Communication
Integrate CAN FD communication
CAN FD integration brings controller configuration, frame definitions, and network participants into agreement. I review arbitration and data-phase settings, frame compatibility, DBC coverage, and gateway mappings, then define and verify the configuration changes supported by your project inputs.
Discuss CAN-FD IntegrationProblems I can investigate
Find the behavior behind the symptom
- 01
CAN-FD communication issue
Investigate CAN-FD frames that fail because of configuration, timing, compatibility, or decoding conditions. Findings are tied to observed traffic and available message definitions.
- 02
CAN message missing
Trace an expected CAN frame through live traffic or a recording to determine whether it is absent, filtered, incorrectly decoded, or affected by surrounding network behavior.
- 03
CAN bus errors
Analyze error frames, bus-off events, and controller error counters to characterize unstable CAN or CAN-FD communication without assuming a root cause before reviewing the evidence.
- 04
CAN gateway issue
Examine messages that are missing, modified incorrectly, or routed to the wrong CAN network, using available traffic and DBC information to compare expected and observed behavior.
What I can help with
Focused engineering work in Vehicle Networks & Communication
CAN-FD traffic analysis
Review CAN-FD and CAN recordings for frame presence, timing, payload changes, and communication patterns. Analysis can use BLF, ASC, or CAN dump data with CANalyzer or CANoe where available.
Message and signal decoding
Decode CAN and CAN-FD messages from DBC definitions, checking identifiers, signals, scaling, nodes, and interpretation notes with cantools where appropriate.
Bus error investigation
Correlate error frames, bus-off events, and controller error counters with recorded communication to isolate conditions requiring further integration or configuration review.
Gateway behavior review
Compare traffic across CAN and CAN-FD networks to identify missing, changed, or incorrectly routed messages. CANoe, CAPL, and DBC data can support focused simulation or test work when supplied.
Repeatable CAN analysis
Create focused analysis or decoding workflows with python-can and cantools for repeatable review of CAN data, message definitions, and recorded traffic.
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.
How the analysis works
From recorded data to engineering findings
- 01
Map the participating interfaces
Review supplied CAN and CAN FD traffic, message definitions, available controller configuration, and intended gateway behavior.
- 02
Identify incompatible settings
Check frame format, nominal and data-phase settings, supported payloads, and message mappings against each participant and the network design.
- 03
Apply agreed configuration changes
Update in-scope message definitions or integration settings where the project provides access. Hand over documented changes for components owned by other teams.
- 04
Verify the updated communication
Repeat representative exchanges and compare traffic with expected mappings, values, and timing. Record remaining limits and any hardware checks still needed.
What you receive
Deliverables matched to the investigation
Engineering analysis
A documented technical analysis with evidence, findings, limitations, and focused follow-up checks.
CAN decoding results
Decoded CAN frames, signals, and interpretation notes based on the supplied CAN data and DBC definitions.
DBC file
A CAN database describing messages, signals, scaling, and nodes when the available information supports creating or updating one.
Technologies & formats
Automotive data and analysis environments
- CAN-FD
CAN Flexible Data-rate
An extension of CAN with larger payloads and a faster data phase.
- 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.
- CANoe
Vector CANoe
A development, simulation, test, and analysis environment for vehicle networks.
- 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.
- 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.
- cantools
cantools
A Python package for parsing CAN databases and encoding or decoding messages.
- UDS
Unified Diagnostic Services
ISO 14229 diagnostic services for communicating with vehicle ECUs.
- CAPL
Communication Access Programming Language
Vector event-driven language for network simulation, testing, and automation.
FAQ
Practical questions before an investigation
- Can a Classical CAN node receive CAN FD frames?
- A Classical CAN-only node cannot decode CAN FD frames. Coexistence depends on the devices and network design; it is not established by matching a nominal bit rate. Integration must account for controller and transceiver capabilities, FD settings, and the traffic permitted on each segment.
- What can I provide to start a CAN-FD investigation?
- A BLF recording, ASC recording, CAN dump, or DBC can provide a useful starting point. The most relevant combination depends on whether the need is decoding, missing-message analysis, bus-error investigation, or gateway review.
- Can you work with CAN and CAN-FD traffic together?
- Yes. The analysis can compare CAN and CAN-FD frames, message definitions, payloads, and observed communication where the supplied data contains both.
- Can you determine why a CAN message is missing?
- The analysis can identify evidence consistent with filtering, decoding, configuration, timing, compatibility, or gateway behavior. A definitive cause depends on the completeness and quality of the supplied traffic and definitions.
- Can you create a DBC file?
- A DBC file can be created or updated when the available CAN data and signal information are sufficient to describe messages, signals, scaling, and nodes.
Discuss the evidence
Discuss CAN-FD Integration
Share a BLF, ASC, CAN dump, or DBC and describe the CAN-FD behavior you need investigated. I can scope the analysis from the evidence available.