b - ASAM

eports from the workgroups
activity report from
ASAM AE MCD-3
Description
MCD-3 is an object-oriented API to MC, D,
MD or even integrated MCD-server tools. It
contains domain specific functionalities on
the one hand. On the other hand it defines
common functionalities (e.g. project and
database handling) in an unique form.
As the API is modeled in UML there is the
need for concrete implementation references,
which exist for COM, Java and C++.
The ECU diagnostics part of MCD-3 is also
known as ISO 22900-3.
Standard and current version
ASAM MCD-3 V2.0.2
Solutions Guide 2007 SECTION TWO
Active workgroup members and speaker
Dr. Jobst Richert, dSPACE (Workgroup
Speaker)
Dr. Andre Marburger, DSA (Coordinator for 3D,
Core Team Leader ISO 22900-3)
Stefan Schukat, dSPACE (Coordinator for 3MC)
Core Team MCD-3D:
Berner&Mattner, DaimlerChrysler, DSA,
dSPACE, ETAS, GM Europe, In2Soft, M&K,
Porsche, Samtec, Siemens, Softing,
Teradyne, T-Systems, Vector Informatik,
Volkswagen
Core Team MCD-3MC:
BMW, dSPACE, ETAS, M&K, Vector
Informatik, Visu-IT!
MCD-3 Plenary (only additional
companies mentioned):
IAV, Johnson Controls, RA Consulting
Current activities
Development of V2.1 of the MCD-3 standard
to be released in March/April 2007
Major MCD-3 global topics:
• Multi-client support
Major 3D topics:
• ECU configuration (variant coding)
• Improvement functional addressing
• Audiences
• Functional diagnostics
• Monitoring
• Integration and Alignment of PDU API V2.1
• Alignment with MCD-2D (ODX) V2.1
• Bug fixing and improvement
Major 3MC topics:
• Unattended measurement (recorder operation)
• Triggered measurement (watcher)
ASAM MCD-3 in the market
The MCD-3 standard has successfully hit the
market. An increasing number of MCD-3D
compliant products – MCD-3D servers as well
as corresponding client applications – is
available. These products span the whole lifecycle
of ECU and vehicle diagnostics. ECU
suppliers, engineering departments,
development departments and after-sales
departments are provided with modern
diagnostic equipment based on the standards
MCD-3D, MCD-2D (ODX) and ISO 22900-2
(D-PDU API) by an increasing number of tool
suppliers.
All market leading MC tools, e.g. ECU
calibration tools and test automation tools
have successfully implemented MCD-3MC
server and clients. MCD-3MC is used
predominantly in new project environments,
such as auto-calibration scenarios or COMbased
test automation applications, e. g.
Hardware-in-the-loop simulation. Step-bystep
3MC substitutes or amends ASAP3
solutions also in conventional test bench
applications.
Quality assurance
The MCD-3D workgroup regularly reviews the
standard’s documents. Implementation
feedback from companies developing
products on the basis of the standard
provides real-world input and helps to
improve the standard. Regular joint technical
meetings with related standards like MCD-2D
(ODX) and ISO 22900-2 (D-PDU API) have
been successfully established to provide a
consistent basis for diagnostic products.
Because MCD-3MC had been implemented
already since 2003 there is a lot of market
feedback available. This feedback has been
considered for the future version development
of V2.1. Meanwhile several cross tests took
place hosted by an OEM beside several
bilateral compatibility tests on customer
project level.
11