Transport-layer test design
Define repeatable tests for segmented messages over CAN, including addressing, flow-control behavior, message length, and timing observations.
Vehicle Diagnostics · ISO-TP Testing
Test and diagnose ISO-TP communication
I test segmented diagnostic transport over CAN, examine failures in addressing, flow control, and timing, and build focused diagnostic or automated testing support around the available ECU and evidence.
Discuss a ISO-TP ProjectProblems I can investigate
Find the behavior behind the symptom
- 01
ISO-TP communication failure
Investigate segmented diagnostic transport that fails during addressing, flow-control exchange, or timing, using recordings and repeatable test conditions where available.
- 02
UDS request fails
Trace diagnostic requests that do not complete with the expected positive response, separating transport behavior from the surrounding UDS exchange.
- 03
ECU not responding
Analyze cases where an ECU does not answer diagnostic or network requests, checking the available communication evidence before drawing conclusions about the cause.
What I can help with
Focused engineering work in Vehicle Diagnostics
Diagnostic exchange analysis
Examine ISO-TP behavior around UDS requests and responses to identify where an exchange stops or deviates from expected behavior.
CanTp integration checks
Review and exercise AUTOSAR CanTp behavior in the surrounding diagnostic communication path, with findings tied to observed evidence rather than assumptions.
CAN and CAN-FD transport coverage
Assess transport tests across the supplied CAN environment, including CAN-FD cases when the ECU and test setup support them.
What to send
Start with the evidence you already have
BLF recording
Timestamped bus communication for examining transport frames, responses, and timing.
ASC recording
A text-based bus recording for reviewing the same communication evidence in a readable form.
DBC
CAN message and signal definitions that help relate recorded traffic to the intended network setup.
ECU
The available electronic control unit for communication, testing, or reproduction of the observed behavior.
Problem description
Observed symptoms, reproduction steps, context, and expected behavior for the test or investigation.
How the analysis works
From recorded data to engineering findings
- 01
Scope the exchange
Review the problem description, available ECU access, recordings, and DBC to identify the diagnostic exchange and the expected observation.
- 02
Reproduce the behavior
Create focused ISO-TP tests around addressing, flow control, message segmentation, and timing, using the available communication setup.
- 03
Analyze evidence
Compare observed frames and ECU responses with the intended exchange, recording where transport or UDS communication diverges.
- 04
Implement support
When useful, develop a diagnostic application or automated test suite that makes the exchange repeatable and its results easier to inspect.
- 05
Document findings
Summarize evidence, test conditions, limitations, and practical next steps without overstating a root cause that the available data cannot establish.
What you receive
Deliverables matched to the investigation
Engineering analysis
A documented technical analysis with evidence, reproduction details, transport observations, and findings.
Diagnostic application
Software for executing and interpreting ECU diagnostic services in the agreed testing context.
Automated test suite
Executable tests with setup, assertions, repeatable results, and coverage of the agreed ISO-TP scenarios.
Technologies & formats
Automotive data and analysis environments
- ISO-TP
ISO 15765-2 Transport Protocol
A segmented transport protocol for messages carried over CAN.
- CAN
Controller Area Network
A priority-based broadcast bus used for in-vehicle control communication.
- UDS
Unified Diagnostic Services
ISO 14229 diagnostic services for communicating with vehicle ECUs.
- CanTp
CAN Transport Protocol
The AUTOSAR transport-protocol module for segmented communication over CAN.
- CAN-FD
CAN Flexible Data-rate
An extension of CAN with larger payloads and a faster data phase.
- DBC
CAN Database
A text format describing CAN messages, signals, nodes, scaling, and metadata.
- J1939
SAE J1939
A higher-layer vehicle network protocol suite using CAN, common in heavy vehicles.
- 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.
- DoIP
Diagnostics over Internet Protocol
Diagnostic transport over IP networks as defined by ISO 13400.
- DTC
Diagnostic Trouble Code
A coded diagnostic record identifying a detected fault condition.
FAQ
Practical questions before an investigation
- What is needed to start ISO-TP testing?
- A BLF recording, ASC recording, DBC, ECU, or problem description can provide a starting point. The useful combination depends on whether the work is analysis, reproduction, or implementation.
- Can you investigate an ECU that is not responding?
- Yes. I can examine available recordings and test the communication path with the ECU, while keeping conclusions proportional to the evidence and access available.
- Can the work include UDS requests?
- Yes. The scope can include UDS request and response exchanges where they are part of the ISO-TP communication being tested.
- Will the result identify the root cause?
- The work is structured to isolate transport and diagnostic behavior, but a definitive root cause depends on the available ECU, recordings, setup, and reproducibility of the failure.
Discuss the evidence
Discuss a ISO-TP Project
Share a recording, ECU access detail, or a short problem description to scope the ISO-TP test or analysis.