EHANDBOOK Container-Build in General

EHB-CB is a framework, which can be extended by multiple converters and generator plug-ins. It has an overall automatic sequence control system for the integrated converters and generators and administrate the meta database and data intelligence. The database is basis for label pop-up, search proposal and function overview feature in EHB-NAV.

To allow these functionalities, EHB-CB interprets further information (metadata like imported/exported/local, compu-method, data-type, …) about parameters, variables and system constants. This content is parsed out of the AUTOSAR-Classic arxml-files or MDX-files (ASAM based EHB-CB) or out of the XLSX-files (directory based EHB-CB).

The EHB-CB generates a special database with this data and puts it into the EHB container. Also per ECU function the standard chapter “Systemconstant-Parameter-Variable-Structure“ with the corresponding tables is created. EHB-CB tags all labels in the textual content (FSX-, adoc- or RTF-files).

The mapping procedure for the function overview is purely named based, which means the name of a parameter or variable that is exported by one function has to be the same for the function that is importing it. This implies also, that every label name has to be unique. That is the same paradigm as in the existing a2l specification.

The EHB-CB provides an own vector graphics generator, to generate images in SVG format out of interactive model hierarchies for ASCET and Simulink and creates links between them.

The framework can be used via a small GUI or headless via command line parameters to allow automated integration into documentation build processes.

Further build process steps:

  • Auto tagging for textual content

  • construct of meta database for variables and parameters (If model interface description is provided as MDX, XLSX or ARXML)

  • Processing of text styling

  • Creation of search index out of textual and interactive model contents

  • Packaging and zipping of all content into EHB container format

Types and Components of the EHB-CB Framework

The entire data sources, like models, texts, graphics and interface data have to be structured in a given way. EHB-CB allows two different types of input structures: file directory or ASAM based. Only one type can be used per EHB-CB framework.

Directory Based EHB-CB

This framework is capable to generate EHB containers out of a given file directory input.

  • The table of contents is created from the directory structure

  • The optional RTF or ADOC file converters parse the textual content for every ECU function and creates references to images and models

  • The optional XLS-file converter or arxml-AUTOSAR-Classic converter parses the model interface data and its parameters and variables

  • The optional PDF file converter can generate documentation with PDF as source. For further, refer Support for PDF files in Directory Based EHB-CB

For the required file format details, please refer to the ADOC/RTF/XLS Specification for EHB-CB documents. These documents are located in the sub folder ../documentation of your EHB-CB installation folder.

ASAM Based EHB-CB

This framework is capable to generate EHB containers out of the ASAM Exchange files standard. For each type of the standard, an adequate converter is provided:

  • The CCX-converter for parsing the container catalog file, which contains the table of content and all references to FSX/MDX and models & graphics

  • The FSX-converter for parsing the function specification files, which contain the textual descriptions and structure and references to images and models

  • The MDX- or arxml-AUTOSAR-Classic-converter for parsing the model data files, which contain the function interface descriptions

  • The optional PDF file converter can generate documentation with PDF as source. For further, refer Support for PDF files in ASAM-based EHB-CB

For the required ASAM file format details, please refer to the ASAM Specification for EHB-CB document, which is located in the sub folder ../documentation of your EHB-CB installation folder.

Unified Graphics Generator

The Unified Graphics Generator tool (UGG) is capable to pre-generate interactive models, SVG images and map files out of Simulink or ASCET models. These artifacts are then read in by the EHB-CB and will speed-up the container generation process dramatically. The UGG can be ordered as a separate SW package.

EHB-CB Toolboxes

ETAS offers the following toolboxes as separate SW packages:

  • Toolbox for Simulink: allows container generation for one model directly out of Simulink

  • Toolbox for ASCET: allows container generation directly out of ASCET V6/V7

Possible Add-on Combinations in EHB-CB

Multiple converters, generator plug-ins and functionalities can extend each EHB-CB framework. The following combinations are possible:

Optional Add-on/ Functionality Dir based CB ASAM based CB UGG ASCET-Toolbox Simulink-Toolbox

ASAM-Ex files importer

No

Yes

No

No

No

AsciiDoc file importer

Yes

No

No

No

Yes

RTF file importer

Yes

No

No

Yes

Yes

XLS file importer

Yes

No

No

No

Yes

Simulink model converter

Yes

Yes

Yes

No

Yes

ASCET model converter

Yes

Yes

Yes

Yes

No

C-code converter

Yes

Yes

Yes

No

No

AUTOSAR Classic arxml

Yes

Yes

No

No

No

Container encryption

Yes

Yes

No

Yes

No

Fetch artifacts from UGG

Yes

Yes

No

No

No

GUI mode

Yes

Yes

No

Yes

Yes

Cmd-line mode

Yes

Yes

Yes

No

No