Diagnostic communication with ASAM-MCD, ODX and UDS on CAN

Softing Automotive Electronics GmbH 

<strong>Diagnostic</strong> <strong>communication</strong> <strong>with</strong> <strong>ASAM</strong>- 

<strong>MCD</strong>, <strong>ODX</strong> <strong>and</strong> <strong>UDS</strong> on CAN 

Peter Subke - October 25, 2011 – Open Technology 

Forum @ Testing Expo North America

Agenda 

• Terms & Definitions 

• <strong>UDS</strong> on CAN 

• <strong>ASAM</strong> <strong>MCD</strong> D-Server 

• <strong>ODX</strong> 

The title of my presentation should read: 

<strong>Diagnostic</strong> <strong>communication</strong> <strong>with</strong> 

<strong>ODX</strong> 2.2.0 (ISO 22901-1) driven D-Server Applications on the D-Server API (ISO 22900-3) 

<strong>with</strong> D-PDU API (ISO 22900-2) compatible VCIs implementing <strong>UDS</strong> (ISO 14229-1) on CAN 

(ISO 15765-3) as diagnostic protocol. 

© 2011 Softing AE / Seite 2

ECUs: Functional View 

ECU # 1 

ECU # 2 

Input Info 

Output Info 

Input Info 

Output Info 

Important reasons for the assignment of electronic systems in vehicles 

include: 

• Increase of miles per gallon 

• Increase of comfort <strong>and</strong> safety 

• Reduction of emissions 


On-Board Communication 

ECU # 1 

ECU # 2 

Input Info 

Output Info 

Input Info 

Output Info 

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

on-board <strong>communication</strong> 

ECUs convert input information to output information. 

ECUs send information to other ECUs <strong>and</strong> receive information from other ECUs (they 

virtually talk to each other = on-board <strong>communication</strong>). 

For on-board <strong>communication</strong>, ECUs are interconnected via in-vehicle networks, e.g. 

CAN. 


Gateway ECU, Data Link Connector (DLC) <strong>and</strong> TST 

ECU # 1 

ECU # 2 

Input Info 

Output Info 

Input Info 

Output Info 

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

DLC 

<strong>Diagnostic</strong> <strong>communication</strong> 

CAN 

TST 

A gateway ECU supports the 

connection of external test equipment 

= Tester (TST) 

Gateway ECU 


Unified <strong>Diagnostic</strong> Services (<strong>UDS</strong>) 

• For any diagnostic <strong>communication</strong>, both the tester <strong>and</strong> the ECUs must support 

the same diagnostic protocol 

• Examples for diagnostic protocols include KWP2000 <strong>and</strong> <strong>UDS</strong> on CAN. 

• <strong>UDS</strong> is specified in ISO 14229-1 <strong>and</strong> its implementation on CAN in ISO 15765-3 

• ISO 14229-1 contains 25 diagnostic services. Examples include 

• ECU reset 

• Response on event 

• Read DTC information 

• Read memory by address 

• Routine control 

• Transfer data 


PC-Software 

Tester Software 

Editor 

Tester Application 

Data 

D-Server 

VCI 


PC-Software 

St<strong>and</strong>ardized Tester Software 

Editor 

Tester Application 

D-Server API (ISO 22900-3) 

<strong>ODX</strong> 

MVCI D-Server 

ISO 22901 

<strong>ODX</strong> 2.2 

D-PDU API (ISO 22900-2) 

VCI 


D-Server API 



MVCI D-Server 

• The D-Server is an object-oriented 

programming interface for applications 


written in C/C++ or Java 

• ISO 22900-3:2009 has been <strong>with</strong>drawn in April 2010. 

• The current stage date of the new committee draft (ISO/CD) is Sept 30, 2011 

• As ISO/CD are not available for the public, there is no valid ISO st<strong>and</strong>ard for the 

D-Server API 


D-PDU API 



MVCI D-Server 


• Objective: Any application (incl. D-Server) that utilizes the D-PDU API can be 

executed on any D-PDU API compliant VCI 

• ISO 22900-2 (D-PDU API) provides the description of API functions <strong>and</strong> the 

abstraction of diagnostic protocols, e.g. „ISO_14229_1_on_ISO_15765_3“ 


ISO MVCI <strong>and</strong> <strong>ODX</strong>- Summary 

ISO 22900: Road vehicles – Modular vehicle <strong>communication</strong> interface (MVCI) 

Part 1(2008): Hardware design requirements 

Part 2 (2009): <strong>Diagnostic</strong> protocol data unit application programmer interface (D-PDU API) 

Part 3 (CD): <strong>Diagnostic</strong> server application programmer interface (D-Server API) 

ISO 22901: Road vehicles – Open diagnostic data exchange (<strong>ODX</strong>) 

Part 1 (2008): Data model specification 

Part 2 (2011): Emissions-related diagnostic data 


PC-Software 

DTS 8 

VENICE 

MONACO 



MVCI D-Server 

COS 

ISO 22901 

<strong>ODX</strong> 2.2 


VCI (EDIC or 3rd party)* 

*VCIs <strong>with</strong> D-PDU API 

or SAE J2534 PassThru API 

• VENICE 

• MONACO 

• COS 

• EDIC 


EDICblue 

VCIs <strong>with</strong> D-PDU API 

EDICwlan 

ETAS ES6520 

SAMTEC 

HSX 


Summary 


<strong>ASAM</strong>-<strong>MCD</strong>, <strong>ODX</strong> <strong>and</strong> <strong>UDS</strong> on CAN 

Means 


<strong>ODX</strong> 2.2.0 (ISO 22901-1) driven D-Server Applications on the D-Server API (ISO 

22900-3) <strong>with</strong> D-PDU API (ISO 22900-2) compatible VCIs implementing <strong>UDS</strong> (ISO 

14229-1) on CAN (ISO 15765-3) as diagnostic protocol. 


Literature 

Christoph Marscholik & Peter Subke 

Road vehicles – <strong>Diagnostic</strong> <strong>communication</strong> 

Technology & Applications 

2008, 336 pages, soft cover 

ISBN 978-3-7785-4048-0 

http://www.vde-verlag.de/engl/books.html

Diagnostic communication with ASAM-MCD, ODX and UDS on CAN

Create successful ePaper yourself

Delete template?

Save as template?