Automotive Test Exchange Format
Definition of an XML-based format for describing tests. Allows the reuse of test descriptions in different test automation systems. Covers activities such as test specification, test planning, test execution and test evaluation. Test specifications includes test cases, sequences, steps, actions and corresponding meta data. Format allows to store test values for inputs (stimuli values), outputs (expectation values) and execution conditions. Frequently used in conjunction with ASAM HIL.
Definition of an XML-based format for describing engineering objects such as source code, compiled objects or documentation files, and associated meta information about the objects, such as creator, name or version. Primarily used for exchanging information between OEM and supplier.
Calibration Data Format
Definition of an XML-based format for storing calibration values and associated meta data on acquisition and quality. Complements ASAM MCD-2 MC such that it provides the values of the calibration parameters described by ASAM MCD-2 MC.
|ASAM CPX||Calibration Process Exchange Format|
Definition of an XML- and ISO 13029 (OTX)-based format for describing ECU calibration tests, i.e. to determine and validate the parameters of ECU software. Standard provides a programmatic access API to calibration and measurement data on the ECU, access to meta information about this data (from A2L files), functions for controlling the execution of measurement tests and simulation models, and specific mathematical functions.
Functional Specification Exchange Format
Definition of an XML-based format for describing the functional specification of software, primarily for the purpose of generating technical documentation. The format allows documentation via prose text in multiple languages, cross-referencing, linking and mentioning of requirements. Variations of the specification can be expressed. Is complementary to ASAM MDX, which contains the interface definitions of functions.
Definition of an API between test automation systems and ASAM HIL test-bench components. Provides access to the simulation model, ECU internal measurement and calibration data, diagnostics data and the electrical error simulation unit. API is described as a technology-independent UML model. Includes code examples for implementing the API in C# and Python.
ISSUE Exchange Format
Definition of an XML-based format for information exchange between different parties of a distributed development process. Covers change requests, clarification requests, problem reports and further use-cases. Furthermore, definition of a workflow for handling the requests.
Model Based Functions Specification
Definition of a block library for model-based design that contains typical functions needed in automotive control algorithm specifications. Includes the definition for 70 blocks with icons, pseudo code and test vectors. Also includes a description of a reference implementation in MATLAB/Simulink.
CAN Calibration Protocol
Definition of a communication protocol between master and slave controllers on a CAN 2.0B network. Includes transfer of calibration data to slave devices, continuous data acquisition from slave devices and carrying out of generic control functions. Standard is also known as "ASAP1". Standard has been replaced by ASAM MCD-1 XCP, but is still widely used in the industry.
The Universal Measurement and Calibration Protocol Family
Definition of a bus-independent communication protocol between master and slave controllers. Includes synchronous data acquisition and stimulation, read/write access on calibration data, memory page management, flash programming and further optional features. Transport layer specifications are defined for CAN, Ethernet (TCP/IP & UDP/IP), FlexRay, USB and SPI/SCI. Establishes an improved and generalized version of ASAM MCD-1 CCP.
|ASAM MCD-2 CERP||Calibration Expert System Rule and Product Model Format||Definition of an XML- and ISO 13029 (OTX)-based format for describing ECU calibration parameter dependencies. Current version covers the use-case of calibration parameter checking. Standard has functions for access to database information (according to ASAM MCD-2 MC), calibration runtime data (values, units) and the product model exchange file. Product model describes properties and features of the system. Check functions and procedures are defined to compare and validate data.|
Data Model Specification for ECU Diagnostics
Definition of an XML-based format for describing ECU diagnostic, programming and related vehicle interface data for data exchange between the ECU and external test equipment. If compliant to this standard, such equipment does not require special programming to process diagnostic data from an ECU. Standard is also known as "ODX".
ECU Measurement and Calibration Data Exchange Format
Definition of calibration parameters (CHARACTERISTIC) and measureable variables (MEASUREMENT) via a non-XML format. Such data resides inside the memory of the ECU. The definition format makes the data accessible through application systems. Furthermore, describes the HW interface of the ECU for device driver configuration of the application system. Standard is also known as "ASAP2".
Data Model for ECU Network Systems
Definition of an XML-based format for describing messages and their timing of automotive communication busses. Is the preferred description format for FlexRay and MOST, but also supports CAN, TTCAN, LIN and Ethernet. Is used for design, configuration, monitoring and simulation of communication on the bus. Standard is also known as "FIBEX" (Field Bus Exchange Format). Content is harmonized with the AUTOSAR System Template.
Automation / Optimization and ECU Calibration System Interface
Definition of an RS232 protocol between a test automation system and a measurement & calibration system connected to an ECU. Standard describes an obsolete technology. Standard has been replaced by ASAM MCD-3 MC and ASAM MCD-3 D.
Application Programming Interface for MVCI Diagnostic Server
Definition of an object-oriented API for a diagnostics server, which provides bus- and protocol-independent services for communication between client applications and ECUs. Includes a mapping of the OO API to C++, Java and COM-IDL with example code. Is complemented by ASAM MCD-2 D, which contains the actual diagnostic configuration for ECUs and vehicle networks.
Application Programming Interface for Measurement and Calibration server
Definition of an object-oriented API for a measurement and calibration server, which provides bus- and protocol-independent services for communication between client applications and ECUs. Includes a mapping of the OO API to COM-IDL with example code. Is complemented by ASAM MCD-2 MC, which contains the actual measurement and calibration data description for ECUs. Standard is also known as "MVCI D-Server API".
Model Data Exchange Format
Definition of an XML-based format for describing interfaces of functions, their data (variables and calibration parameters) and scheduling in ECU software. This allows the integration of such functions as object code into the overall ECU software without having access to the source code. Standard is complementary to FSX, which contains the functional description of functions. MDX is the predecessor of the AUTOSAR Software Component Template.
|ASAM OTX||Open Test Sequence eXchange Format||Definition of an extension of ISO 13029 "Open Test Sequence Exchange" (OTX) with added functionality. Includes new data types, change monitoring and triggering of events, general read and write access to files, general processing of XML files, flow charts and state machines. Includes document that clarifies specification gaps, limitations and some known errors of ISO 13029. Shall be transferred to ISO in the future and become part 4 and 5 of ISO 13029.|
|ASAM XIL||Generic Simulator Interface||Definition of an API between test automation systems and test-benches such as HIL-systems (hardware-in-the-loop) or SIL-systems (software-in-the-loop). Provides access to the simulation model, ECU internal measurement and calibration data, diagnostics data, the electrical error simulation unit and the ECU network. API is described as a technology-independent UML model. Includes open-source code in C#, which implements a significant part of the standard's API. Former name of the standard was "ASAM HIL".|
ASAM CAT standards (Computer Aided Testing) are primarily applied during the verification & validation phases of ECU software development (right side of the V-Model), and during automated calibration and system testing on engine and vehicle test beds. They focus on: