Skip to main content

What is UDS on CAN or Diagnostic on CAN ?

OSI Model and Diagnostics :
OSI model has 7 layers and each layer has defined functionality. To understand this you can refer
this excellent IEEE  publication. It explains OSI Model for CAN , Ethernet, flexray and MOST. 

External reference :

So let us understand,  what is this UDS on CAN  ?

When a Diagnostic Message formatted  as per ISO 14229 -1 i.e UDS Standard is sent over Controller Network we say Diagnostics Communication is happening as per UDS on CAN.

So as per this :

Below layers participate in Diagnostic Communication Over CAN :

 1. Application Layer :

 ISO 14229-1:2013 ROAD VEHICLES — UNIFIED DIAGNOSTIC SERVICES (UDS) — PART 1: SPECIFICATION AND REQUIREMENTS 

ISO 14229-3:2012 ROAD VEHICLES — UNIFIED DIAGNOSTIC SERVICES (UDS) — PART 3: UNIFIED DIAGNOSTIC SERVICES ON CAN IMPLEMENTATION (UDSONCAN)

 2. Session layer :

 ISO 14229-2 : Road vehicles — Unified diagnostic services (UDS) — Part 2: Session layer services

 3. Transport Layer :

ISO 15765-2:2016 ROAD VEHICLES — DIAGNOSTIC COMMUNICATION OVER CONTROLLER AREA NETWORK (DOCAN) — PART 2: TRANSPORT PROTOCOL AND NETWORK LAYER SERVICES

 4. Data Link Layer :

 ISO 11898-1:2015 ROAD VEHICLES — CONTROLLER AREA NETWORK (CAN) — PART 1: DATA LINK LAYER AND PHYSICAL SIGNALLING

 5. Physical Layer :

ISO 11898-1:2015 ROAD VEHICLES — CONTROLLER AREA NETWORK (CAN) — PART 1: DATA LINK LAYER AND PHYSICAL SIGNALLING   

External reference : https://www.iso.org


So the use of these standards for Diagnostics Communication is said to be a UDS On CAN overall.

We shall study all these standards to know the UDS On CAN in depth.




    

  
  

Comments

Popular posts from this blog

What is a Diagnostic Communication

Diagnostic Communication : Diagnostic Communication is base of Automotive Diagnostics . It is an  exchange of Diagnostic messages between an two entities. Those could be two , ECUs or ECU and  Tester Application.or it could be a group of ECUs and a tester application    The basic components of the diagnostic communication are : A Diagnostic Message :   It could be of these types -  1. A Request 2. A Response  3. A Negative Response Code Diagnostic Address :  1. Functional 2. Physical  Diagnostic Protocol : 1. UDS 2. J1939 3. KWP 2000 etc. Supporting Protocols :  1. CAN 2. Ethernet 3. K-line ,etc What is  Diagnostic Protocols ans supporting Protocols   ?  ECUs and tester communication are connected to each other by physical or wireless media. They exchange messages (requests and responses) over that physical or wireless channel. It is same as we connect to each other over internet or phone...

Diagnostic Session : Function 5 - Session Oriented Access to Services

  There are multiple users those need to use UDS protocol for various purposes like Garage person for fault detection, ECU manufacture for Testing activities and development purpose. Also  OEM needs  access to ECU memory for flashing purposes.   UDS services can be categorized in different groups like few services will just read some Data from memory,a few will write or update the data to memory, some will erase/update ECU sw itself , some will control Inputs outs of ECU directly.  So there are chances that any improper usage of UDS service may result in safety issues , security breaches or damage to ECU resources. Hence, it doesn't make sense to give access to all services to everyone. To achieve this UDS has designed some mechanisms like Sessions, Security Authentication, Preconditions. I hope you are aware about what a Diagnostic Session is. Please visit :  https://thevehiclediagnostics.blogspot.com/2020/01/what-is-diagnostic-session.html   if you ...

A 2nd Pebble : What is Endianness ?

Endiness is characteristic of a Digital link or an Electronic System. For a System, Endiness refers to the order in which the data is stored by the system in its memory. The order could be LSB to a lower memory address or MSB to lower memory address. For example : A Data coming to system is  - 0x 00 FF  - '00' : MSB and 'FF' : LSB in the received data.  - System use 2 bytes to store data in its memory. Suppose address bytes 0x0001 and 0x0002 are to be used for storing these 2 data bytes. - Strange thing is , System can utilize these two bytes in two ways to store the data. Method 1  : Little Endian Address  | 0x0001          |   0x0002     | Data        |   LSB - FF    |    MSB - 00 | Method 2 : Big Endian Address  | 0x0001          |   0x0002     | Data        |  ...