ISO-TP and CAN integration
Connect ISO-TP handling with CAN communication and diagnostic application logic, including segmented messages and transport state transitions.
Vehicle Diagnostics
Integrate ISO-TP transport for UDS
ISO-TP carries diagnostic payloads over CAN by handling segmentation and reassembly when needed. I connect the transport to your diagnostic application, configure addressing and flow-control behavior, and check timeout recovery against the supplied ECU requirements.
Discuss ISO-TP IntegrationProblems I can investigate
Find the behavior behind the symptom
- 01
ECU not responding
Investigate cases where an ECU does not answer diagnostic or network requests, using available recordings, CAN definitions, and reproduction details to narrow the communication path involved.
- 02
UDS request fails
Trace diagnostic requests that do not complete with the expected positive response, separating transport behavior from diagnostic application handling and observed ECU behavior.
- 03
ISO-TP communication failure
Analyze segmented transport failures involving addressing, flow-control, or timing behavior across ISO-TP and CAN communication.
What I can help with
Focused engineering work in Vehicle Diagnostics
UDS diagnostic communication
Develop and troubleshoot communication paths for UDS requests over ISO-TP, with attention to diagnostic sessions, responses, and failure evidence.
CAN and CAN-FD transport analysis
Examine transport behavior across CAN and CAN-FD using bus recordings, CAN definitions, and repeatable request scenarios.
Trace-based debugging and simulation
Use available analysis environments and Python-based CAN interfaces to reproduce communication behavior, inspect traces, and support focused tests.
What to send
Start with the evidence you already have
BLF recording
Vector binary log containing timestamped bus communication.
ASC recording
Text-based Vector bus recording.
DBC
CAN database defining messages and signals.
ECU
Electronic control unit available for communication or testing.
Problem description
Observed symptoms, context, reproduction steps, and expected behavior.
How the analysis works
From recorded data to engineering findings
- 01
Review the communication context
Examine the problem description, available ECU access, recordings, and DBC information to establish the expected communication path and reproduction conditions.
- 02
Trace transport behavior
Inspect CAN or CAN-FD traffic for addressing, segmentation, flow-control, timing, and response behavior relevant to the reported failure.
- 03
Reproduce and isolate
Recreate the communication scenario with the available ECU or a focused simulation setup, separating transport handling from UDS request processing where evidence allows.
- 04
Implement and test the change
Integrate or correct the ISO-TP capability, then exercise the relevant request paths with repeatable checks and recorded results.
- 05
Document findings
Summarize the evidence, implemented behavior, remaining uncertainty, and practical next steps for the surrounding diagnostic system.
What you receive
Deliverables matched to the investigation
Engineering analysis
A documented technical analysis with evidence and findings.
Diagnostic application
Software for executing and interpreting ECU diagnostic services.
Automated test suite
Executable tests with assertions, setup, and repeatable results.
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 must match at both ends of an ISO-TP connection?
- The endpoints need compatible CAN identifiers, addressing mode, frame format, and transport settings. Multi-frame transfers also depend on flow-control block size, separation timing, and timeout handling. A DBC may describe surrounding CAN traffic, but it does not replace the diagnostic transport configuration.
- What communication scope does this service cover?
- The service covers ISO-TP communication over CAN, including its interaction with UDS and, where relevant, CAN-FD transport behavior.
- Can existing recordings be used for the investigation?
- Yes. BLF and ASC recordings can provide evidence of message ordering, segmentation, flow-control, timing, and ECU responses when the captured traffic contains the relevant scenario.
- Do I need to provide an ECU?
- An ECU is useful for communication or testing, but the available problem description, recordings, and DBC can also support an initial analysis.
- Can the result include executable software?
- Depending on the scope, the work can produce a diagnostic application or an automated test suite in addition to the engineering analysis.
Discuss the evidence
Discuss ISO-TP Integration
Share the communication symptoms, available recordings, DBC, and ECU access to define a focused ISO-TP integration or debugging task.