EHANDBOOK Container Build

EHANDBOOK Container Build can be used by OEMs and tier-1 suppliers to share their software documentation in the form of EHANDBOOK containers. This system of multi-container support permits the provision, delivery, and use of complementary parts of the ECU software documentation by the OEM and tier-1 suppliers. The EHANDBOOK-NAVIGATOR tool can integrate multiple EHANDBOOK containers to form one unit. Using the INCA interface, the calibration engineer can access measurement and characteristic variables from the experiment in the documentation and vice-versa.

EHANDBOOK containers support the structured management of ECU documentation. They contain the various com-ponents of documentation in the form of tables, descriptive texts, interactive models for ASCET, MATLAB®/Simulink®, and C code, and a search index in compressed form. The search index allows users to make rapid, targeted searches for specific details of the description of software functions.

Container Build tool and service

EHANDBOOK Container Build enables software developers to reliably and automatically generate the entire docu-mentation for ECU software “at the push of a button.” In order to make it easier for customers to change over to EHANDBOOK, ETAS offers to integrate Container Build into a specific software development environment as an engineering service.

Integration of documentation from different sources

EHANDBOOK-NAVIGATOR can integrate EHANDBOOK containers from different sources, giving users a general, joined-up view of the whole system.

Intelligent data preparation

EHANDBOOK Container Build merges information from different sources relevant to the documentation of ECU software, such as ASCET or MATLAB®/Simulink® models and descriptive texts. The information is intelligently cross-linked, supplemented, and indexed. The Container Build process collects metadata on functions as well as meas-urement and characteristic variables from different sources and stores them in a central database. This metadata makes it possible to map the connections between functions and to display detailed information about individual elements directly in the text or in the model.

Interactive, graphical models for C code, too

To be able to relate data saved in separate development steps in different formats, the Container Build tool con-tains various converters. In this way, it is possible to process image and text contents in RTF format and descriptions of model interfaces in XLS format in addition to the ASAM formats FSX, MDX, and CCX, which were developed for the exchange of ECU documentation in XML format. In particular, the Container Build tool converts function models from ETAS ASCET and MATLAB®/Simulink® as well as C code into graphical, interactive models.

Know-how protection included

To protect copyright interests, implementation-specific information is removed from the source data during conver-sions. This makes EHANDBOOK particularly well suited to the documentation of software that is developed by auto manufacturers and suppliers in joint projects. This form of cooperation requires the protection of each party’s source code as proprietary intellectual property.
EHANDBOOK containers do not contain any native models from software and function development tools, only graphical representations of these models, which are neither suitable for code generation nor can be processed with software development tools. For this reason, no licenses for products such as ASCET or MATLAB®/Simulink® are required to use EHANDBOOK documentation.


  • Integration of documentation from different sources
  • Interactive, graphical models also for C code
  • Automatic generation of documentation
  • Integration into customer-specific development environment
  • Intelligent preparation and linking of input data
  • Know-how protection