This document defines the Open Test sequence eXchange (OTX) additional extension requirements and data model specifications. The requirements are derived from the use cases described in ISO 13209-1. They are listed in Clause 4. The data model specification aims at an exhaustive definition of all features of the OTX extensions which have been implemented to satisfy the requirements. This document establishes rules for the syntactical entities of each extension. Each of these syntactical entitie...view more

    • sale 15% off
    • Standard
      379 pages
      English language
    • sale 15% off
    • Draft
      379 pages
      English language

ISO 22901-3:2018 specifies machine-readable descriptions of all fault symptom algorithms which are implemented as diagnostic software in an electronic control unit (ECU). The main use case is the standardized data exchange from a function & software supplier to a vehicle manufacturer (VM) in order to enable a tool-based information processing. Based on the FXD content and associated calibration values, several end user documents can be generated such as the "summary sheet" needed as part of the ...view more

    • sale 15% off
    • Standard
      198 pages
      English language

ISO 22900-2:2017 specifies the diagnostic protocol data unit application programming interface (D-PDU API) as a modular vehicle communication interface (MVCI) protocol module software interface and common basis for diagnostic and reprogramming software applications. ISO 22900-2:2017 covers the descriptions of the application programming interface (API) functions and the abstraction of diagnostic protocols, as well as the handling and description of MVCI protocol module features. Sample MVCI modu...view more

    • sale 15% off
    • Standard
      362 pages
      English language

ISO 22900-3:2012 focuses on the description of an object-oriented programming interface. The objective is the ability to implement server applications, used during the design, production and maintenance phase of a vehicle communication system, compatible to each other and thus exchangeable. From a user's perspective, access and integration of on-board control units is provided by a corresponding application, the communication server and a VCI module for diagnostics. The user is granted access fo...view more

    • sale 15% off
    • Standard
      281 pages
      English language

The Open Test sequence eXchange (OTX) Core, defined in ISO 13209-2, describes the basic structure underlying every OTX document. ISO 13209-3:2012 extends the Core by a set of additional features, using the extension mechanism rules described in ISO 13209-2. The extensions defined in ISO 13209-3:2012 comprise features which allow diagnostic communication to a vehicle's diagnostic interface, flashing, executing diagnostic jobs, controlling measurement equipment, internationalization, working with ...view more

    • sale 15% off
    • Standard
      278 pages
      English language

ISO 13209-2:2012 defines the OTX Core requirements and data model specifications. The requirements are derived from the use cases described in ISO 13209-1. They are listed in the requirements section that composes the first major part of ISO 13209-2:2012. The data model specification aims at an exhaustive definition of all OTX Core features implemented to satisfy the Core requirements. Since OTX is designed for describing test sequences, which themselves represent a kind of program, the Core dat...view more

    • sale 15% off
    • Standard
      205 pages
      English language
    • sale 15% off
    • Standard
      205 pages
      English language

1 Scope This part of ISO 13209 specifies a standardized, tester-independent, XML-based data exchange format for the documentation and formal description of diagnostic test sequences. The format serves to support the requirements of transferring diagnostic-test-sequence logic between electronic system suppliers, vehicle manufacturers and service dealerships/repair shops. This part of ISO 13209 provides an introduction to the rationale behind ISO 13209. It gives an overview of the document set and...view more

    • sale 15% off
    • Standard
      19 pages
      English language

ISO 22901-2:2011 is intended to ensure that diagnostic data stream information is available to diagnostic tool application manufacturers to simplify the support of the aftermarket automotive service industry. The ODX modelled diagnostic data are compatible with the software requirements of the Modular Vehicle Communication Interface (ISO 22900-2 and ISO 22900-3). The ODX modelled diagnostic data can enable an MVCI device to communicate with the vehicle [ECU(s)] and interpret the diagnostic data ...view more

    • sale 15% off
    • Standard
      72 pages
      English language

ISO 22901-1:2008 specifies the concept of using a new industry standard diagnostic format to make diagnostic data stream information available to diagnostic tool application manufacturers, in order to simplify the support of the aftermarket automotive service industry. The Open Diagnostic Data Exchange (ODX) modelled diagnostic data are compatible with the software requirements of the Modular Vehicle Communication Interface (MVCI), as specified in ISO 22900-2 and ISO 22900-3. The ODX modelled di...view more

    • sale 15% off
    • Standard
      486 pages
      English language
    • sale 15% off
    • Standard
      486 pages
      English language

ISO 22900-1:2008 provides the framework to allow diagnostic and reprogramming software applications from all vehicle manufacturers the flexibility to work with multiple vehicle communication interfaces (VCI) from multiple tool suppliers. This system enables each vehicle manufacturer to support all vehicle communication interfaces to perform diagnostics and to control the programming sequence for electronic control units (ECUs) in their vehicles. ISO 22900-1:2008 describes the applicable use case...view more

    • sale 15% off
    • Standard
      29 pages
      English language

ISO 17356-6:2006 describes the OSEK Implementation Language (OIL) concept for the description for ISO 17356 real-time systems, capable of multitasking and communications, which can be used for motor vehicles. It is not a product description that relates to a specific implementation.

    • sale 15% off
    • Standard
      49 pages
      English language

ISO 17356-5:2006 defines a set of services for node monitoring (NM). NM consists of the following: interface to interact with the Application Programming Interface(API); algorithm for node monitoring; internal interfaces (NM COM, etc.); algorithm for transition into sleep mode; and NM protocol data unit (NMPDU).

    • sale 15% off
    • Standard
      117 pages
      English language

ISO 17356-3:2005 describes the concept of a real-time operating system, capable of multitasking, which can be used for motor vehicles. It is not a product description which relates to a specific implementation. It also specifies the operating system Application Program Interface (API). General conventions, explanations of terms and abbreviations have been compiled in ISO 17356-1. ISO 17356-6 discusses implementation and system generation aspects. The specification of the OS represents a uniform ...view more

    • sale 15% off
    • Standard
      61 pages
      English language

ISO 17356-4:2005 (COM) specifies a uniform communication environment for automotive control unit (ECU) application software. In ISO 17356-4:2005 , the specification increases the portability of application software modules by defining common software communication interfaces and behaviours for internal communication (communication within an ECU) and external communication (communication between networked vehicle nodes), which is independent of the used communication protocol.

    • sale 15% off
    • Standard
      55 pages
      English language

ISO 17356-2:2005 gives the OSEK/VDX specifications for binding the OS (operating system), COM (communications) and NM (network management) of the open interface for embedded automotive applications. It specifies the variables (error codes, status types, etc.) programmable by the user to ensure that implementation of OS, COM and NM are coherent between each other.

    • sale 15% off
    • Standard
      3 pages
      English language

ISO 17356-1:2005 outlines the general structure of, and defines terms and abbreviations used in relation to, the specification of the software open interface for embedded automotive applications given by the other parts of ISO 17356.

    • sale 15% off
    • Standard
      21 pages
      English language

ISO 22900-2:2009 specifies the diagnostic protocol data unit application programming interface (D-PDU API) as a modular vehicle communication interface (MVCI) protocol module software interface and common basis for diagnostic and reprogramming software applications. ISO 22900-2:2009 covers the descriptions of the application programming interface (API) functions and the abstraction of diagnostic protocols, as well as the handling and description of MVCI protocol module features. Sample MVCI modu...view more

    • sale 15% off
    • Standard
      325 pages
      English language

Defines diagnostic provisions applicable to electronic systems in road vehicles. Applies to electronic systems including electronic modules, associated input sensors, output actuators and indicators. The measurement ranges specified exclude certain devices for which specific test equipment is required. Does not apply to those systems which have built-in diagnostic capabilities and do not require compatibility with off-board equipment.

    • sale 15% off
    • Standard
      3 pages
      English language
    • sale 15% off
    • Standard
      3 pages
      French language
    • sale 15% off
    • Standard
      3 pages
      French language