It is now maintained at https://github.com/cariad-tech
- FEP SDK Metamodel as XSD
- Data Model and Parser for C++ to use it in further developments (see /include and /lib directory)
The valid Metamodel 2.0 version is a bundle of:
- xsd/common/2.0
- xsd/element/2.0
- xsd/system/2.0
- xsd/ddl/4.0
- xsd/mapping/1.0
The Metamodel 1.0 and 1.1 version is currently delivered, but not yet verified!
| COMMON | ||
| Common Type Defintions |
xsd/common/2.0/conan_types.xsd xsd/common/2.0/fep_types.xsd xsd/common/2.0/timing_interface_types.xsd |
Type definitions to be used element and system relevant XSDs |
| ELEMENT RELEVANT | ||
| FEP Element Type Description | xsd/element/2.0/fep_element_type.xsd xsd/element/2.0/timing_interface_types.xsd |
FEP Element Type Description to describe the default behaviour and interfaces of a FEP Element Type. (Within C++ it is a type like a class type!) Such a type can be instanciated more than once and will commonly describe the functionality of a concrete FEP Element. |
| FEP Element Timing Configuration | xsd/element/2.0/fep_element_timing.xsd xsd/element/2.0/timing_interface_types.xsd |
Configuration File to change the timing behaviour of a instanciated element.
This file is only necessary if you want to change the default behaviour of the timing interface defined within FEP Element Type Description. REMARK: A instance of this file can be used within the FEP System SDK Description (see below under SYSTEM RELEVANT) |
| FEP Element Mapping Configuration | xsd/mapping/1.0/mapping_configuration.xsd | Configuration File for the data input and output configuration while connecting to the simulation data bus. This file is only necessary if you want to change the default data input and output names or remap some content of the data to other data inputs or data outputs. REMARK: A instance of this file can be used within the FEP System SDK Description (see below under SYSTEM RELEVANT) |
| Data Defintion Language Description | xsd/ddl/4.0/ddl4.0.xsd | Description File to describe the layout of inputs and outputs of an element type. REMARK: A instance of this file is used within the FEP Element Type Description. |
| SYSTEM RELEVANT | ||
| FEP System SDK Description | xsd/system/2.0/fep_system_sdk.xsd |
Description File to describe and configure one concrete FEP SDK System.
The FEP SDK System is a bundle of participants with concrete loaded element instances. These instances may be reconfigured with a data mapping. Otherwise the instances will use the default data mapping defined within the FEP Element Type Description. To configure a data mapping per element instance the FEP Element Mapping Configuration can be used. The element instances may have a reconfigured scheduling and timing behaviour where the FEP Element Timing Configuration can be used. If the timing is not reconfigured, the default timing behaviour will be used described in the FEP Element Type Description. |
| FEP System Properties Configuration | xsd/system/2.0/fep_system_properties.xsd |
Description File to describe a concrete parameter set of a concrete launched FEP System.
A instance of this file contains the properties of the element instances (described in the FEP Element Type Description) that have to be changed after the system was launched.
Additionally, the file will contain System Properties which will be distributed to all element instances. Since FEP Participaants and its Elements are (runtime-) configurable via properties, and also a timing behaviour is configurable via properties, the file will also contain pre-defined property sets that take care of system timing behaviour. |
- For any software changes have a look at changelog
- This software is published under Modzilla Public Lisense 2.0
- To join the project see Contribution rules