What is ISO 15765-4 about?
ISO 15765-4 is the fourth part of multiple series that specifies requirements for CAN-based communication systems between the in-vehicle network and the diagnostic link connector of the vehicle. This document specifies the requirements to enable the in-vehicle CAN-based communication systems to establish, maintain, and terminate communication with the devices connected to the diagnostic link connector.
NOTE-
ISO 15765-4 does not specify any requirements related to the in-vehicle CAN network architecture.
Who is ISO 15765-4 for?
ISO 15765-4 on diagnostic communication over Controller Area Network (DoCAN) is useful for:
- Network provider of DoCAN
- Vehicle regulatory authority
- Service provider
- Vehicle repair shop
- Manufacturer and supplier of vehicle
Why should you use ISO 15765-4?
ISO 15765-4 has been established in order to define common requirements for vehicle diagnostic systems implemented on a controller area network (CAN) communication link. It is intended for diagnostic systems. It also meets requirements from other CAN-based systems needing a network layer protocol. It is very useful for the diagnostic communication over Controller Area Network (DoCAN).
ISO 15765-4 provides the application of vehicle that is useful for CAN-based communication systems between the in-vehicle network and application layer to diagnostic link connector of the vehicle.
What’s changed since the last update?
BS ISO 15765-4:2021 supersedes BS ISO 157654:2016, which is withdrawn.
This fourth edition replaces the third edition (ISO 157654:2016), which has been technically revised.
The main changes compared to the previous edition are as follows:
- Changed all time-related parameters to t Parameter_Name
- Corrected all occurrences of ⊣⫤ P2 CAN_max and changed to Δt P2_CAN_Client_Max
- Clause 6 title has been changed to application
- Subclause 6.1 title has been changed to vehicle communication initialisation sequence
- Subclause 6.2 title has been changed to external test equipment communication initialisation sequence
- Changed N_As to t N_As and changed timeout value to 33 ms
- Changed N_Ar to t N_Ar and changed timeout value to 33 ms
- Added clarification in 10.3.3 regarding the acceptance of physically addressed request messages