CAN-FD traffic testing
Build a test matrix covering supported payload lengths, bit-rate-switch settings, message periods, and recovery scenarios. Agree timing tolerances and required hardware before execution; record unsupported cases explicitly.
Vehicle Networks & Communication
CAN-FD Testing for Communication and Timing Issues
Define and execute repeatable CAN-FD acceptance checks for message presence, periods, payload interpretation, and communication recovery. Each result links the test condition and expected behavior to captured evidence and a pass, fail, or unresolved outcome.
Discuss a CAN-FD ProjectProblems 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.
- 02
Network timing issue
Examine message periods, latency, ordering, and timeouts against the expected network behavior.
- 03
CAN message missing
Trace an expected CAN frame through live traffic or a recording to determine where its absence can be observed.
- 04
CAN bus errors
Check captured error events and controller diagnostics where available. Bus-off state and error counters require suitable interface or ECU reporting and cannot be assumed to exist in an ordinary traffic log.
What I can help with
Focused engineering work in Vehicle Networks & Communication
Recording analysis and decoding
Inspect timestamped traffic, decode messages and signals from a DBC, and document interpretation limits or inconsistencies.
Automated CAN analysis
Build focused analysis or test routines using python-can and cantools for repeatable handling of CAN messages and CAN databases.
CANoe and CAPL test support
Review or extend network testing, simulation, and automation work in CANoe using CAPL where that environment is part of the workflow.
J1939 and ISO-TP traffic review
Analyze CAN traffic involving J1939 or segmented messages carried through ISO-TP when those protocols are present in the supplied data.
What to send
Start with the evidence you already have
BLF recording
A timestamped bus communication recording for traffic, timing, and error review.
ASC recording
A text-based bus recording for message presence, ordering, and timing analysis.
DBC
The CAN database used to interpret messages, signals, scaling, nodes, and related metadata.
CAN dump
Raw or text-exported CAN frames for focused decoding and communication checks.
How the analysis works
From recorded data to engineering findings
- 01
Define the expected behavior
Confirm the CAN-FD communication, message, timing, decoding, or bus-error question to be examined.
- 02
Review the available evidence
Inspect the supplied BLF recording, ASC recording, CAN dump, and DBC in relation to the reported problem.
- 03
Analyze and test
Run agreed stimuli on the available bench, capture traffic, and apply explicit assertions to frames, signal values, and periods. For recording-only work, report the checks that can be evaluated and which scenarios need a live setup.
- 04
Document findings
Separate direct observations from interpretation, identify relevant evidence, and note areas that require additional data.
What you receive
Deliverables matched to the investigation
Engineering analysis
A test-results analysis with scenario identifiers, setup conditions, expected values or tolerances, observed evidence, and pass, fail, or unresolved outcomes for regression comparison.
CAN decoding results
Decoded CAN frames and signals with interpretation notes based on the supplied CAN database and recordings.
DBC file
A CAN database describing messages, signals, scaling, and nodes when a DBC output is part of the agreed work.
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
- What can I provide to start CAN-FD testing?
- A BLF recording, ASC recording, DBC, or CAN dump can provide a starting point. The most useful input depends on whether the focus is communication, timing, missing messages, decoding, or bus errors.
- Can you investigate a missing CAN message?
- Yes. The analysis can examine recordings or CAN dumps for the expected frame, its timing, surrounding traffic, and available decoding information. The evidence may identify likely conditions without guaranteeing a root cause.
- Can you work with CANoe or CANalyzer data?
- Yes. CANoe and CANalyzer recordings and analysis context can be considered when they are included in the supplied material or agreed engineering environment.
- Can you create or update a DBC file?
- A DBC file can be produced when the available message, signal, scaling, and node information is sufficient. Unknown definitions are recorded as limitations rather than invented.
Discuss the evidence
Discuss a CAN-FD Project
Send a BLF recording, ASC recording, DBC, or CAN dump with the communication question you need answered.