User Tools

Site Tools


tutorials:vec:system_schematic
 Next

System Schematic

Coupling Devices

Basics

8_2_1_basics.jpg

The figure above illustrates the model of the smallest appearance of a coupling device (e.g. an inliner) with just one connector with only one pin on each side. The coupling device is represented in the VEC by a ComponentNode with the componentNodeType ‘CouplingDevice’ and contains for each side of the coupling device a ComponentConnector. These connectors include the ComponentPorts, which represent the pins of the connector.
To display the connectivity between the two sides connectors and their pins, the VEC also contains a Connection with two ConnectionEnds, which reference the connected ComponentPorts. The flag isExternalEnd of the Ends is set to false, because the connection represent the internal mapping of the coupling device. The connection to other ComponentNodes is represented by different Connections with ConnectionEnds where isExternal=true.

Variance

8_2_2_variance.jpg

A more complex situation is displayed in this diagram. A coupling device can consist of one or more connectors for each side. Because of variance it is possible, that more than one connector from a side are mapping onto one connector of the other side.

If there is a second connector placed on one of the sides, this connector gets its own ComponentConnector with the underneath ComponentPorts.

Variant Management For ECUs

8_3_variant_management_for_ecus.jpg

This example demonstrates how the variant management can be handled in the systems schematic on different levels of abstraction.

The top most element is the usage node. It defines an abstract position / function in the vehicle. In the example it is the back light on the left hand side (named “MX3”). This function can be realized by two different electrological variants (interfaces). These variants are represented by ComponentNodes. In the example there is one variant with two pins (MX3.1) and one variant with three pins (MX3.2). On a more concrete level these interfaces can be satisfied by one or more EE-components (alternatives). These EE-Components are defined by PartVersion with a EEComponentSpecification. In order to define restrictions a corresponding PartOccurrence with a VariantConfiguration can be defined.

The PartUsages in the example are needed for to reasons:

  1. They serve as a container to group the different possible alternatives (“realizedPartUsage”).
  2. It is necessary to declare one of the EEComponents as the representative of all alternatives of a variant. This is done by the reference between the PartUsage and the corresponding EEComponentSpecification.
tutorials/vec/system_schematic.txt · Last modified: 2019/03/07 17:33 by 4soft.becker