Central Data Container
- Central container for managing all data required for designing a model and implementing it on an ECU
- Convenient administration of parameters, constants, signals, variables, structures, variable classes, typedefs, scaling formulas, etc.
- Full access to code specifics
- Various import and export formats
- Full access to all TargetLink Data Dictionary objects via powerful MATLAB® API
The TargetLink Data Dictionary is a data container that centrally holds the relevant information for a model’s design, code generation, and implementation on an ECU. Data dictionary objects can be referenced from TargetLink models. You can define and manage variables and corresponding properties, and you can specify structured data types and use them for variable declarations. Scaling formulas can be entered and used to uniformly scale fixed-point signals and parameters in the model. You can import and export standardized or proprietary data and share the data with the calibration system.
The TargetLink Data Dictionary is the perfect tool for defining and handling project-related code specifics, even for workgroups. It provides access to a wealth of additional information, for example, specifics on C modules, function calls, tasks, variable classes, data variants and so forth. The data is well structured in a hierarchical tree and can also be accessed via an application programming interface (API). It also supports common import and export formats, which means that existing and proven definitions, for example, an existing calibration file, can be used as templates.
Import and Export
The TargetLink Data Dictionary supports various import/export formats, including
- Variables and Simulink data objects from/to MATLAB workspace and files
- XML (Extensible Markup Language)
- ASAM-MCD 2MC (Standardized Description Data, formerly ASAP2)
- AUTOSAR software component descriptions
- OIL (OSEK Implementation Language)
Code Generation Straight from the Data Dictionary
The Data Dictionary supports the generation of both code and A2L files for Data Dictionary variables independently of their use in TargetLink models. Variables with global relevance that are shared between different models, subsystems and referenced models should be specified in the Data Dictionary and implemented from there. Generating code files with definitions and declarations, and also A2L files for variables from the Data Dictionary, makes software integration and software integration testing easy. Moreover, it is possible to create all the calibration parameters for an entire ECU project in one file, no matter whether they are from legacy code or used in TargetLink models.