Vehicle Diagnostics Presentation

VEHICLE DIAGNOSTICS
Introduction
• Helps to determine, check, classify symptoms of a system for overall

picture
(Directed Communication)
Request
Tester ECU
Response
• Offboard Communication:- Access to tester; Reads data
• Onboard Communication:- During driving; Taking data
• Mainly used wherever direct access to ECU is not possible or
difficult
2
Confidential & Proprietary Information – Exempt from Public Disclosure by Applicable Law
Introduction
• Vehicle diagnostic is a method which allows

– Reading and sometimes writing access
– In the entire life cycle of an ECU
– To selected ECU information or memory areas
– And allows usage of selected ECU functions
• Standardized diagnostic protocols: UDS, KWP
3
Further possibilities of vehicle diagnostics
• Read/write identification values

• Calibration
• I/O Control
• Start of routines
• Fault Memory
– Faults are stored as Diagnostic Trouble codes (DTC)
– Talks about malfunction or repair instruction
4
Vehicle Diagnostic Architecture
Vehicle Vehicle
EDC ECU EDC ECU
Gearbox ECU Gearbox ECU

Tester Tester Gateway
ABS ECU ABS ECU
Airbag ECU Airbag ECU
5
Diagnostics over CAN
Advantages
Vehicle
Faster communication
EDC ECU
CAN interface available on most ECU’s
More reliable Gearbox ECU

Tester CAN
Preference of car manufacturers
ABS ECU
Disadvantages
Can send only 8bytes in one CAN Airbag ECU

frame, but can send blocks of data up to
4095 bytes using segmentation system
for which sequence and timing are
defined
6
UDS – Unified Diagnostic Services
• ISO 14229
5-7 Diagnostic Application with UDS
3-4 Transport Layer
1-2 Physical Bussystem
• Physical layer can be CAN, K-Line, LIN, FlexRay, Ethernet
7
Composition of Frames
Structure
Byte 1 Byte n Byte 8
NPCI Useful data
NPCI (Network Protocol Control Information)

Four different types of messages
8
SINGLE_FRAME
4 bits4 bits 7 bytes
SF DL Useful data
NPCI
 Max of 7 bytes of useful data.
 SF-SINGLE_FRAME, value set at 0.
 DL-no. of useful data contained in the frame.
9
Single frames
Sender Receiver
Single frame
Tool ECU
Request 02 10 C0 xx xx xx xx xx
P2
02 50 C0 xx xx xx xx xx Response
10
FIRST_FRAME
4 bits 12bits 6 bytes
FF DL Useful data
NPCI
 Used for a block of over 7 bytes of useful data.

 FF-FIRST_FRAME, value set at 1.
 DL-no. of useful data contained in the frame and
takes account of the 6 bytes and all of the bytes to be
issued within CONSECUTIVE_FRAME.
11
CONSECUTIVE_FRAME
4 bits 4bits 7 bytes
CF SN Useful data
NPCI
 Used when a block of over 7 bytes of useful data.
 CF, value set at 2.
 SN - no. of the segments sent (0-15).
12
Segmented Frames
Transmitter Bus Receiver
Size of data
package sent
First Frame
Ack_transmission
Sending of: STmin

BS=0
Clear_To_Send.
Flow Control Frame
Ack_transmission
First segment
(SN=1) of first
block sent
Consecutive Frame
Ack_transmission
STmin
Second segment
Block (SN=2) of first
Size block sent
Consecutive Frame
Ack_transmission
Thirds egment STmin

(SN=3) of first
block sent
Consecutive Frame
Ack_transmission
13
Principle of Communication
Service Identifier SID
Positive Response SID + 40 Data
Negative Response 7F SID NRC
There are 4 types of UDS Services

SID Service supports service identifier
SID SF Service supports Subfunction. Eg:- 10 SF
SID ID Service supports Identifier Eg:- 22 ID

Service supports Subfunction and Identifier Eg:-
SID SF ID 31 SF ID
14
Physical and Functional Addressing
E1 E2 E3 E4 E5
FG1 FG1 FG2 FG2 FG1
Tester
Physical Addressing
E1 E2 E3 E4 E5
FG1 FG1 FG2 FG2 FG1
Tester
Functional Addressing
15
Data Identifier
Service Usage of DID
Read Service 22 Read DID
Write Service 2E Write DID
Stream Service (Periodic Reading) 2A Stream DID
Control Service 2F Control DID
Communication Control 28 Switches on and off the transmission of certain ECU messages
Clear Diagnostic Information 14 Used by the external diagnostic tool to clear diagnostic
information in one or multiple ECU’s memory.
Control DTC Settings 85 Used by diagnostics tool to stop or resume the setting of DTCs
in ECU.
Diagnostic Session Control 10 Used to enable different diagnostic sessions in one ECU or a
group of ECUs.
ECU Reset 11 Used by the external diagnostic tool to request an ECU reset
based on content of the reset type parameter included in the
ECU Reset request message.
Read DTC Information 19 Allows a diagnostic tool to read the status of ECU resident
Diagnostic Trouble Code (DTC) information from any ECU,
or group of ECU’s within a vehicle.
Tester Present 3E Used to indicate to an ECU or a group of ECU’s that a
diagnostic tool is still connected to the vehicle.
16
Read and Write Service
Service Identifier 22 ID
Positive Response 62 ID Data
Request for Active Diagnostic Session 22 F1 86

Response Received: Programming Session 62 F1 86 02
17
Read and Write Service
Service Identifier 2E ID Data
Positive Response 6E ID
Request for PROXI Write 2E 20 23 Data

Response Received: Positive Response 6E 20 23
18
IO Controls
Service Identifier 2F ID SF Data
Positive Response 6F ID SF
SF Description
00 Return Control to ECU
01 Reset to Default (as stored in ECU)
02 Freeze Current State
03 Short Term Adjustment (with timeout)
19
Routines
Service Identifier 31 SF ID
Positive Response 71 SF ID Data
SF Description
01 Start Routine
02 Stop Routine
03 Request Routine Results
20
Diagnostic Session
• Depending on who uses or works on the ECU the amount of diagnostic

services is different. After restart the ECU is in default session.
– SF=03: Extended Session: Development, Manufacturing, After sales
– SF=02: Programming Session: Development, Manufacturing
– SF=01: Default Session: Normal car operations after sales
• Tester Present 3E or another gets session active
10 SF
Change
Default Timeout Non Default to same
Session S3 Time Session or other
session
Power On 10 01
21
ECU Reset
• After restart ECU is in default session

SF Description Meaning
01 Hard Reset Same as disconnecting/reconnecting power to ECU
02 Key Off On Reset Same as cycling ignition key off and on
03 Soft Reset Jumps back to beginning of application program
Service Identifier 11 SF
Positive Response 51 SF Optional Data
22
Response Timeout Time P2
Tester ECU
Parameter Tester ECU
P2EC Time between tester and ECU 150 50
U response
Timeout wait after receiving 5000 2000
P2EC negative response with NRC 78
U
23
Response Timeout Time P2
Tester ECU
S3Client
S3Server
Parameter ECU
Session timeout (Return to 5000
default session)
Time for transmitting next (keep 4000
non default session)
24
Suppressed Positive Answer (with MSB of the sub function)
Service Identifier 11 01
51 01
Response
Parameter MSB
Positive Answer - suppressed 0
Positive Answer – not suppressed 1
Service Identifier 11 81
Suppressed Response
25
Negative Response Code Handling
Service Identifier SID • If ECU cannot work with a

service it will send a
Negative Response 7F SID NRC Negative Response with
NCR statement
12 - Sub Function Not Supported

13 - Incorrect Message Length Or Invalid Format
22 - Conditions Not Correct
• If unsupported service is 24 - Request Sequence Error
loaded in unsupported 31 - Request Out Of Range
33 - Security Access Denied
session, then expected NRC 35 - Invalid Key
is 7F (Service not supported 36 - Exceed Number Of Attempts
in active session) 37 - Required Time Delay Not Expired
70 - Upload Download Not Accepted
71 - Transfer Data Suspended
72 - General Programming Failure
73 - Wrong Block Sequence Counter
92 - Voltage Too High
93 - Voltage Too Low
26
Fault Memory
• Report DTC by Status Mask 19 02 Mask
• Clear DTCs 14 (DTC/Group Mask)
• Extended Data Records 19 06 DTC Num
• Snapshot Record 19 04 DTC Num Records
27
ODX (Open Diagnostic Data Exchange)
• Standardized diagnostic data format for test devices and for ECUs.
Data reuse in development, production, service
• Vehicle diagnostic in machine readable format
– ODX-C/CS – Communication Parameters
– ODX-D – Diagnostic Services
– ODX-V – Vehicle Info (Access for entire network/ECUs with different ODX
files)
– ODX-FD – Vehicle Functions documentation data
– ODX-E – ECU Configuration data
– ODX-F – Flash/reprogramming data
• PDX contains several ODX files – Represents entire ECU
28
Terminology (using ODX)
ID SID SF Data Control
Diag-Service Param
• PARAM’s are represented by byte-bit positions

• Data will be in hexadecimal form.
• Data types are Identical, Linear, Text table etc
• Value linked by Short names
29
Q&A
THANK YOU
•May 11°,2015 •Network Management 30


Vehicle Diagnostics Presentation

Uploaded by

Copyright:

Available Formats

Vehicle Diagnostics Presentation

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Vehicle Diagnostics Presentation

Uploaded by

Copyright:

Available Formats

VEHICLE DIAGNOSTICS

• Helps to determine, check, classify symptoms of a system for overall

• Vehicle diagnostic is a method which allows

• Read/write identification values

EDC ECU EDC ECU

Gearbox ECU Gearbox ECU

ABS ECU ABS ECU

Airbag ECU Airbag ECU

More reliable Gearbox ECU

Can send only 8bytes in one CAN Airbag ECU

5-7 Diagnostic Application with UDS

3-4 Transport Layer

1-2 Physical Bussystem

• Physical layer can be CAN, K-Line, LIN, FlexRay, Ethernet

NPCI Useful data

NPCI (Network Protocol Control Information)

4 bits4 bits 7 bytes

4 bits 12bits 6 bytes

 Used for a block of over 7 bytes of useful data.

4 bits 4bits 7 bytes

Sending of: STmin

Thirds egment STmin

Service Identifier SID

Positive Response SID + 40 Data

Negative Response 7F SID NRC

There are 4 types of UDS Services

SID SF Service supports Subfunction. Eg:- 10 SF

SID ID Service supports Identifier Eg:- 22 ID

Service Usage of DID

Read Service 22 Read DID

Write Service 2E Write DID

Stream Service (Periodic Reading) 2A Stream DID

Control Service 2F Control DID

Positive Response 62 ID Data

Request for Active Diagnostic Session 22 F1 86

Service Identifier 2E ID Data

Request for PROXI Write 2E 20 23 Data

Service Identifier 2F ID SF Data

Positive Response 71 SF ID Data

• Depending on who uses or works on the ECU the amount of diagnostic

• After restart ECU is in default session

Positive Response 51 SF Optional Data

Service Identifier SID • If ECU cannot work with a

12 - Sub Function Not Supported

• Report DTC by Status Mask 19 02 Mask

• Clear DTCs 14 (DTC/Group Mask)

• Extended Data Records 19 06 DTC Num

• Snapshot Record 19 04 DTC Num Records

ID SID SF Data Control

• PARAM’s are represented by byte-bit positions

•May 11°,2015 •Network Management 30

You might also like