Testing Expo North America 2008

Introduction to Standardized Diagnostic

Communication: UDS on CAN (ISO 15765)
with MVCI (ISO 22900) and ODX (ISO 22901)

Dipl.-Ing. Peter Subke

Key Account Manager
Automotive Electronics
Softing AG, Germany
sub@softing.com
 2

Onboard Communication

ECU # 1 ECU # 2

Input Info Output Info Input Info Output Info

in-vehicle network (e.g. CAN bus)

onboard communication

ECUs convert input information from sensors to output information

for actuators.
ECUs send information to other ECUs and receice information from
other ECUs (onboard communication).
For onboard communication, ECUs are interconnected via an in-vehicle
network (e.g. CAN)
 3

Diagnostic Communication

ECU # 1 ECU # 2

Input Info Output Info Input Info Output Info

For diagnostic communication, a TESTER is

connected to the in-vehicle network. TESTER

The TESTER (client) sends a request to

a specific ECU (e.g. #1) and the ECU
(server) answers the request with a response.
 4

Diagnostic Services

Diagnostic communication requires a diagnostic protocol.

A diagnostic protocol contains a set of communication parameters and

diagnostic services (request / response).

Typical examples for diagnostic protocols include KWP2000 and UDS.

ISO 14229-1(2006) : Road vehicles –Unified diagnostic services

(UDS) specifies a diagnostic protocol on layer 7 of the OSI model.

Examples for diagnostic services of ISO 14229 include:

11hex = ECU reset

86hex = response on event
19hex = read DTC information
23hex = read memory by address
31hex = routine control
36hex = transfer data
 5

UDS on CAN

Today, diagnostic communication uses the existing in-vehicle network

to transport requests and responses.

The transport protocol for UDS on CAN is specified in

ISO 15765-3 (2004): Road vehicles –

Diagnostics on controller area network (CAN) –
Part 3: Implementation of unified diagnostic services (UDS on CAN)

ISO 14229-1:2006 (UDS) and ISO 15765-3:2004 (Diagnostics on CAN)

are complementary standards that together specify the diagnostic
protocol “UDS on CAN”.
 6

Communication system

Tester
Applications (e.g. MONACO, INCA, LabView, AD
Databases (EDF, ODX, FBX,CANdb, A2L)
D-Server (EDIABAS, ETESTER, COS, MVCI)

PC-to-ECU interface software

e.g. EIDBSS, Vecom, D-PDU API

PC-to-ECU interface hardware

e.g. ETK, EDIC, DCDI, VCI
Onboard communication
CAN, LIN, FlexRay, MOST

Diagnostic communication
Diagnostic protocols
KWP 2000, UDS on CAN
UDS on FlexRay

ECU software (e.g. AUTOSAR)

 7

Components of a PC-based Tester

Editor Application

PC software
Basesystem
Database

PC hardware

PC-to-ECU-Interface

in-vehicle network (e.g. CAN)

ECU
 8

OEM-specific PC-based Tester (examples)

Editor TST

E-TESTER 6
CBF Basesystem

DCDI

BEST/2 VAS 5163

EDF EDIABAS

EDIC
 9

Problem & Solution...

Too much energy is spent on the development of proprietary

communication protocols and networking technologies.

Incompatible tester technologies cause high costs at the vehicle

manufacturer and their suppliers.

Proprietary technologies make the vehicle manufacturer dependent of

the selected tool supplier (single source).

Standardization is an advantage for vehicle manufacturers as well as

for their suppliers.

Standardization serves the price, the quality, and the maintainability

of the end product via scale and training curve effects.
 10

ASAM LLC

ASAM is short for

Association for the Standardisation of Automation & Measuring systems

The vision of ASAM is that standards enable products that can be

freely interconnected with seamless data interchange.
The mission of ASAM is to develop platform independent extensible
standards, and to enable products that use and are compliant with
those standards

ASAM MCD = Working group for Measurement, Calibration and

Diagnostics
ASAM AE = ASAM Automotive Electronics
 11

The ASAM MCD system

Editor/Viewer
Application
Checker

PC software
ASAM MCD-3D

ASAM
MCD-2D (MC) D BaseSystem
(ODX)
No ASAM standard for Diagnostics

PC-to-ECU-Interface
 12

History of ASAM-MCD 2D (ODX)

ASAM MCD-2D 2.2

ASAM MCD-2D 2.0

ASAM MCD-2D 1.2.2

ASAM MCD-2D 1.0

1998 2000 2002 2004 2006 2008

 13

Combination of ODX and MCD-3D versions

MCD-3 MCD-3 MCD-3 MCD-3 MCD-3D

1.0.1 2.0.1 2.0.2 2.1.0 2.2.0
ODX
1.2.2
ü
ODX
2.0.0

ODX
2.0.1
ü ü
ODX
2.1.0
(ü)
ODX
2.2.0
(ü)
ü = commonly used combinations (ü) = to be used in future
 14

PC based TESTER: ASAM goes ISO (MVCI & ODX)

Editor/Viewer
Application
Checker

PC software
D-Server API (ISO 22900-3)

D-Server

ISO 22901 D-PDU API (ISO 22900-2)

PC-to-ECU-Interface
 15

ISO 22900 and ISO 22901

ISO 22900: Road vehicles –Modular vehicle communication

interface (MVCI)
Part 1(2008): Hardware design requirements
Part 2 (FDIS): Diagnostic protocol data unit application programmer
interface (D-PDU API)
Part 3 (DIS): Diagnostic server application programmer interface
(D-Server API)
Part 4 (AWI): Conformance test

ISO 22901: Road vehicles –Open diagnostic data exchange (ODX)

Part 1 (PRF): Data model specification
Part 2 (CD): Emissions-related diagnpostic data in ODX format

(F)DIS = Final draft International standard - WD = Working draft - .AWI = Approved work item –PRF = proof
 16

PC-based tester by Softing: DTS V7

Venice Monaco HMI Controls

PC software
D-Server API (ISO 22900-3)

D-Server (COS)

D-PDU API (ISO 22900-2)

ISO 22901
EDIC
 17

Summary

Editor/Viewer
Diagnostic Application
Checker

D-Server API (ISO 22900-3)

PC software
UDS on CAN D-Server
ISO 14229-1
ISO 15765-3
D-PDU API (ISO 22900-2)
ISO 22901
PC-to-ECU-Interface (ISO 22900-1)

ISO 11898 (CAN)

 18

Screenshot: ODX database with UDS on CAN

 19

Screenshot: ODX cats and UDS on CAN comparams

 20

Thank you for your attention.

www.softing.com
 10

ASAM LLC

ASAM is short for

Association for the Standardisation of Automation & Measuring systems

The vision of ASAM is that standards enable products that can be

freely interconnected with seamless data interchange.
The mission of ASAM is to develop platform independent extensible
standards, and to enable products that use and are compliant with
those standards

ASAM MCD = Working group for Measurement, Calibration and

Diagnostics
ASAM AE = ASAM Automotive Electronics
 11

The ASAM MCD system

Editor/Viewer
Application
Checker

PC software
ASAM MCD-3D

ASAM
MCD-2D (MC) D BaseSystem
(ODX)
No ASAM standard for Diagnostics

PC-to-ECU-Interface
 12

History of ASAM-MCD 2D (ODX)

ASAM MCD-2D 2.2

ASAM MCD-2D 2.0

ASAM MCD-2D 1.2.2

ASAM MCD-2D 1.0

1998 2000 2002 2004 2006 2008

 13

Combination of ODX and MCD-3D versions

MCD-3 MCD-3 MCD-3 MCD-3 MCD-3D

1.0.1 2.0.1 2.0.2 2.1.0 2.2.0
ODX
1.2.2
ü
ODX
2.0.0

ODX
2.0.1
ü ü
ODX
2.1.0
(ü)
ODX
2.2.0
(ü)
ü = commonly used combinations (ü) = to be used in future
 14

PC based TESTER: ASAM goes ISO (MVCI & ODX)

Editor/Viewer
Application
Checker

PC software
D-Server API (ISO 22900-3)

D-Server

ISO 22901 D-PDU API (ISO 22900-2)

PC-to-ECU-Interface
 15

ISO 22900 and ISO 22901

ISO 22900: Road vehicles –Modular vehicle communication

interface (MVCI)
Part 1(2008): Hardware design requirements
Part 2 (FDIS): Diagnostic protocol data unit application programmer
interface (D-PDU API)
Part 3 (DIS): Diagnostic server application programmer interface
(D-Server API)
Part 4 (AWI): Conformance test

ISO 22901: Road vehicles –Open diagnostic data exchange (ODX)

Part 1 (PRF): Data model specification
Part 2 (CD): Emissions-related diagnpostic data in ODX format

(F)DIS = Final draft International standard - WD = Working draft - .AWI = Approved work item –PRF = proof
 16

PC-based tester by Softing: DTS V7

Venice Monaco HMI Controls

PC software
D-Server API (ISO 22900-3)

D-Server (COS)

D-PDU API (ISO 22900-2)

ISO 22901
EDIC
 17

Summary

Editor/Viewer
Diagnostic Application
Checker

D-Server API (ISO 22900-3)

PC software
UDS on CAN D-Server
ISO 14229-1
ISO 15765-3
D-PDU API (ISO 22900-2)
ISO 22901
PC-to-ECU-Interface (ISO 22900-1)

ISO 11898 (CAN)

 18

Screenshot: ODX database with UDS on CAN

 19

Screenshot: ODX cats and UDS on CAN comparams

 20

Thank you for your attention.

www.softing.com