General Information about DDS
The Visu-IT! Data Declaration System (DDS) is an intuitive database application for defining and managing calibration and measurement items to be used in embedded controllers. DDS manages the calibration and measurement object attributes required for configuring calibration systems, as well as code representation information. To ensure consistency of the DDS data pool and the actual ECU software, ANSI-C code is generated out of the DDS data definitions.
This ANSI-C code is compiled and linked with the ECU software. The generated locator file is used by DDS to:
Perform validity checks
Capture the address information required for creating an ASAM MCD 2MC file
Basic Functions
ANSI-C source code export of the data definitions in the database
Locator address import (IEEE-695 file or ELF/DWARF file)
Creation of description files for calibration tools reading ASAM MCD 2MC files
Several other import and export filters
Compare&Merge functionality
Remote Access via COM API
etc.
Arrays and structured data are mapped to the calibration data object model (curve/map, axis, parameter, online data).
The modular DDS database itself consists of so-called configuration units in the form of (ASCII format) GRL files, which can be managed, together with the ECU source code, by the use of a configuration management system.
The DDS Scripting Host provides basic search and modification operations on the command-line. The DDS COM-API provides access to the internal data structures of the DDS database.
Application
DDS runs on Windows XP, Windows 2000 and NT 4.0 and
supports command line controlled filters. File imports or exports can be
invoked either from the DDS Editor graphical user interface or via a
command line, allowing the DDS functionality to be integrated with
script, batch and make processes. Severity level control mechanisms
support the fine-tuning of error management policies to specific
customer requirements.
Documentation
A comprehensive online help system provides context-sensitive user
information and step-by-step guidance for all input fields, system
messages and command line tool options.
Workflow
The user enters calibration data by defining those
manually via the DDS Editor, by importing ASAP2 (ASAM MCD 2 MC) files,
by running customer specific import scripts using the DDS COM API or by re-using
existing data pool files.
The Source Export filter is used to generate ANSI C declaration and
definition files. Together with the ECU algorithms, these *.c and *.h
files will be used for ECU software development.
The DDS generated C source files as well as the ECU algorithm
software are compiled by one of the sup-ported compilers (see list below).
The locator file generated by this step provides the address information
for the calibration data definitions.
DDS provides a filter for importing the locator file into the
database. The address information will be merged with the existing
description data.
An ASAP2 (ASAM MCD 2 MC) description file (*.a2l) is generated. Alternatively, a
description file (*.des) for the SAM calibration system can be generated.
Calibration data provided as CVX files can be imported to define
initialization values.
Interfaces
ASAM-MCD-2MC export: versions 1.4.1, 1.3.1, 1.2.1 (or 1.2.0 for Softing EDICmobil)
ASAM-MCD-2MC import: versions 1.4.1, 1.3.1 and 1.2.1
ASAM-MCD-2D export: version 1.2.2 (prototype)
ASAM-MCD-2D export: version 2.0 (ODX) -> ODX-FLASH export (prototype)
MSRSW export: version 2.2.2 (prototype)
IEEE-695 import: Tasking C166, etc.
ELF/DWARF import: DIAB DATA (Motorola MPC555 series), Hitachi (SH7055), etc.
DDS supports the TASKING VX-toolset for TriCore
DDS supports the TASKING VX-toolset for TriCore
Calibration Value import: CVX version 1.0
System Requirements
Operating System Windows XP, Windows Vista
Processor Pentium or equivalent, 166 MHz or higher, 400 MHz recommended
Hard disk 100 MB (minimum) of free hard disk space, depending on database size