Official Standard Name

Title
and Short Description

Version

Download 

ASAM MCD-1

The MCD-1 standard ‘family’ defines several standards for the connection of an ECU to a computer or a measurement or data logging device. This connection can be established via different transport layers.

ASAM MCD-1.XCP

The Universal Measurement and Calibration Protocol Family
Based on the practical experience with the predecessor protocol CCP, which was limited to the CAN bus, the new protocol family XCP was developed. CAN, Ethernet, SxI, USB and FlexRay transport layer specifications exist.

Important for the success of the XCP standard are also the functional enhancements in comparison to CCP, such as features for bypassing ECU internal functions in Rapid Control Prototyping.

ASAM MCD-1.XCP

The Universal Measurement and Calibration Protocol Family
See ASAM MCD-1 XCP V1.0.0

1.1.0

ASAM MCD-1.CCP

CAN Calibration Protocol
CCP defines the communication of controllers with a master device using CAN for data acquisition and memory transfers to and control functions in the controllers for calibration.

ASAM MCD-2

ASAM MCD-2 D
(market name: ODX)

Data Model for ECU Diagnostics
(also: Open Diagnostic Data Exchange Format)
ODX defines a unique and open XML exchange format for transferring ECU diagnostic and programming data between system supplier, vehicle manufacturer and service dealerships and diagnostic tools of different vendors. 

ASAM MCD-2 D
(market name: ODX)

NEW! Authoring Guidelines
A recommended practice paper for the ODX based data exchange between companies and represents a collection of best practice authoring rules.

1.0.0

ASAM MCD-2 NET
(market name: FIBEX)

NEW! Data Model for ECU Network Systems
(also: Field Bus Data Exchange Format
FIBEX describes an XML exchange format for data exchange between tools that deal with bus communication systems (tools for bus configuration, parameterization, design, monitoring, simulation, ...). 

Flease find the What’s New presentation V3.1.1 here.

  3.1.1

ASAM MCD-2 NET
(market name: FIBEX)

Data Model for ECU Network Systems
(also: Field Bus Data Exchange Format
FIBEX describes an XML exchange format for data exchange between tools that deal with bus communication systems (tools for bus configuration, parameterization, design, monitoring, simulation, ...). 

Flease find the What’s New presentation V3.1.0 here.

ASAM MCD-2 MC (market name: ASAP2)

ECU Measurement and Calibration Data Exchange Format
ASAP2 is a description format for calibration values and signals of an Electronic Control Unit (ECU), its communication methods and interfaces.
In contrast to ODX which is service-based, ASAP2 contains address-based information of the ECU code. Therefore it might be necessary to update an ASAP2 file with the compile and link run during ECU software development process.

  1.6.1

ASAM MCD-2 MC (market name: ASAP2)

ECU Measurement and Calibration Data Exchange Format
ASAP2 is a description format for calibration values and signals of an Electronic Control Unit (ECU), its communication methods and interfaces.
In contrast to ODX which is service-based, ASAP2 contains address-based information of the ECU code. Therefore it might be necessary to update an ASAP2 file with the compile and link run during ECU software development process. 

1.6.0

 ASAM MCD-3

The MCD-3 standard ‘family’ defines an object-oriented API between a so-called MCD-system. MCD systems might provide M(easurement)-, C(alibration)- or D(iagnostics)- functionality or any combination of these functionalities. The MCD-3 API is used by test automation client systems typically. 

ASAM MCD-3

Application Programming Interface Specification
MCD-3 defines the interface between an application (e.g. Diagnosis- or Calibration System) and a Kernel / MCD System in form of an object oriented API.

ASAM ASAP3

Automation/Optimisation Interface for ECU Calibration System
This standards defines a command protocol to be used via RS232 or TCP/IP transport layer to remote control an ECU calibration system by a client system, e.g. an Automation or Optimisation system.

ASAM AE HIL

AE Hardware-in-the-Loop API
AE HIL introduction to come later

Flease find the What’s New presentation V1.0.0 here .

ASAM AE Expression (Draft version - June 23, 2009) here .

1.0.0

ASAM AE ISSUE

ISSUE Exchange Format
AE ISSUE describes an electronic exchange for change requests and problem reports.

3.0.0

ASAM AE CC 

Container Catalog
CC describes the meta information of engineering data (e.g. configuration management info) at exchange between repositories or tools.

ASAM AE CDF

Calibration Data Format
CDF stands for Calibration Data Format and describes a format for the exchange of ECU calibration data.

2.0.0

ASAM AE FSX

Functional Specification Exchange Format
FSX describes functional specification data of ECU Software functions.

ASAM AE MBFS

Model Based Function Specification
MBFS is a tool and technology independent standard library of blocks for ECU software applications. A Matlab/Simulink reference implementation is part of the delivery of this standard.

ASAM AE MDX

Meta Data Exchange Format
MDX describes a multi-purpose format for data specifications of ECU software which allows the exchange of data between vendor independent calibration, simulation, documentation, spreadsheet and data acquisition tools.

1.0.0

ASAM AE Common CRC

Seed&Key and Checksum Calculation API
The document contains definitions of Win32 APIs for Seed&Key calculation and for checksum calculation.  These definitions were formerly contained in the ASAM  MCD-2MC specification document

ASAM Adopted Standards (AAS)

The following standards have been developed as MSR standards. They haven’t been updated since then and are made available here for convenience.

ASAM AAS MSRSW

MSR Description for Software of ECUs

  2.3.0

ASAM AAS MSRSYS 

ECU Control System Description

  1.2.0

ASAM AAS MSRDCI

Document Control Information

  2.1.0

ASAM AAS MSRFMEA

Failure Mode and Effects Analysis

ASAM AAS MSRMEPRO

Methodology for Engineering Process-Synchronization

  1.0.0