User Tools

Site Tools


tutorials:vec:system_schematic_basics

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
tutorials:vec:system_schematic_basics [2019/07/15 10:39]
4soft.becker
tutorials:vec:system_schematic_basics [2019/08/01 16:11]
4soft.becker
Line 8: Line 8:
 <​imgcaption simple_example |Simple System Schematic Example>​{{:​tutorials:​vec:​basic_schematic.png?​|}}</​imgcaption> ​ <​imgcaption simple_example |Simple System Schematic Example>​{{:​tutorials:​vec:​basic_schematic.png?​|}}</​imgcaption> ​
  
-To represent a system schematic in the VEC the [[:​models:​vec_v1_1_3:​classes:​connectionspecification|ConnectionSpecification]] and its subelements are used. E/​E-Components (in some ECAD Systems called Block) are represented by [[:​models:​vec_v1_1_3:​classes:​componentnode|ComponentNodes]]. A [[:​models:​vec_v1_1_3:​classes:​componentnode|ComponentNode]] is a node where an electrological component is located. It is a representative for an element in the electric system, e.g. an actuator, a sensor, an ECU. In <imgref simple_example_diagram>​ contains the representation as VEC classes of the system schematic shown in <imgref simple_example>​. The [[:​models:​vec_v1_1_3:​classes:​componentport|ComponentPort (Pins)]] of a[[:​models:​vec_v1_1_3:​classes:​componentnode|ComponentNodes]] are grouped into Connectors / Slots with the help of [[:​models:​vec_v1_1_3:​classes:​componentconnector|ComponentConnectors]]. In the <imgref simple_example>​ the connectors are only represented implicitly by the prefix "​A"​ to the Pin-Number.+To represent a system schematic in the VEC the [[:​models:​vec_v1_1_3:​classes:​connectionspecification|ConnectionSpecification]] and its subelements are used. E/​E-Components (in some ECAD Systems called Block) are represented by [[:​models:​vec_v1_1_3:​classes:​componentnode|ComponentNodes]]. A [[:​models:​vec_v1_1_3:​classes:​componentnode|ComponentNode]] is a node where an electrological component is located. It is a representative for an element in the electric system, e.g. an actuator, a sensor, an ECU. <imgref simple_example_diagram>​ contains the representation as VEC classes of the system schematic shown in <imgref simple_example>​. The [[:​models:​vec_v1_1_3:​classes:​componentport|ComponentPort (Pins)]] of a [[:​models:​vec_v1_1_3:​classes:​componentnode|ComponentNode]] are grouped into Connectors / Slots with the help of [[:​models:​vec_v1_1_3:​classes:​componentconnector|ComponentConnectors]]. In <imgref simple_example>​ the connectors are only represented implicitly by the prefix "​A"​ to the Pin-Number. \\ 
 +Even if the system schematic in this example only shows pins which are connected to other pins (of other components),​ the VEC representation of the component ([[:​models:​vec_v1_1_3:​classes:​componentnode|ComponentNode]]) is explicitly allowed to contain [[:​models:​vec_v1_1_3:​classes:​componentport|ComponentPorts]] for unused pins. For example a component with 5 pins where just pin no. 1 and 5 are connected in some way __may__ contain ComponentPorts for the pins 2 - 4 (but is not required to). This underlines that these pins do physicaly exists. There is no need of a reference from a [[:​models:​vec_v1_1_3:​classes:​connection|Connection]] to one of the [[:​models:​vec_v1_1_3:​classes:​componentport|ComponentPorts]] via a [[:​models:​vec_v1_1_3:​classes:​connectionend|ConnectionEnd]].
  
 <​imgcaption simple_example_diagram |System Schematic Class Diagram>​{{ :​tutorials:​vec:​simpleschematicconnectionsbasic.png |}}</​imgcaption>​ <​imgcaption simple_example_diagram |System Schematic Class Diagram>​{{ :​tutorials:​vec:​simpleschematicconnectionsbasic.png |}}</​imgcaption>​
  
-The following XML listing ​shows the same as xml snippet.+The following XML listing ​contains ​the component nodes and connection from the example above.
 <​Code:​xml linenums|>​ <​Code:​xml linenums|>​
-<​Specification ​xmlns:​xsi="​http://​www.w3.org/​2001/​XMLSchema-instance" ​xsi:​type="​ns2:​ConnectionSpecification"​ id="​id_connect_spec_2506">​+<​Specification xsi:​type="​vec:​ConnectionSpecification"​ id="​id_connect_spec_2506">​
             <​Identification>​ConSpec_V..58L..</​Identification>​             <​Identification>​ConSpec_V..58L..</​Identification>​
             <​ComponentNode id="​id_comp_node_2507">​             <​ComponentNode id="​id_comp_node_2507">​
Line 74: Line 75:
 <WRAP group> <WRAP group>
 <WRAP half column> <WRAP half column>
-The black dots (circled in red) in the graphical example <imgref nodes> have only a layouting purpose and do not represent a technical design decision (e.g. to place a splice on this spot). The expressed engineering intention is only that the connected pins (all “A1”) have the same potential (are connected in some way). The decision about a technical realization (e.g. splice, multicrimp, single wires) is normally ​at this point impossible to make, because a technical realization depends on concrete variant combinations and might be even different for different variants (see section Wiring) or is still unnecessary,​ because in a reduced 100% scope there would be just one of the components. As the VEC does not represent graphical layout of documents, but only product describing content of those, ​these nodes have no representation in VEC.+As mentioned before, the level of abstraction of the system schematic in the VEC (represented by the [[:​models:​vec_v1_1_3:​classes:​connectionspecification|ConnectionSpecification]]) contains only the electrological design and no physical design of the wiring harness. Therefore, the black dots (circled in red) in the graphical example <imgref nodes> have only a layouting purpose and do not represent a technical design decision (e.g. to place a splice on this spot). ​ 
 + 
 +The expressed engineering intention is only that the connected pins (all “A1”) have the same potential (are connected in some way). The decision about a technical realization (e.g. splice, multicrimp, single wires) ​can not be made is most cases at the stage of a system schematic, because a technical realization depends on concrete variant combinations and might be even different for different variants (see section Wiring) or is can be unnecessary,​ because in a reduced 100% variant, ​there might be just two of the three components ​and a realization with a single wire would be possible. As the VEC does not represent ​the graphical layout of documents these nodes have no representation in VEC. 
 + 
 +If the system schematic should explicitly contain the engineering intention of a star like connection topology (e.g. with a splice or a potential distributor) the center of this "​star"​ must be explicitly represented with an individual [[:​models:​vec_v1_1_3:​classes:​connectionspecification|ComponentNode]]
 </​WRAP>​ </​WRAP>​
  
Line 84: Line 89:
  
 ===== Partial Systems ===== ===== Partial Systems =====
 +During the development of individual systems or sub systems for a vehicle the corresponding system schematic is often incomplete (partial). This situation arises from the fact, that most systems depend on some kind of infrastructure of the integrated overall vehicle system (e.g. power, ground or bus connections). ​  
 +-----
 Sometimes there is the situation that concrete target components are unknown (or not yet defined) or different (topic specific) parts of a system schematic are developed independently as partial systems (e.g. vehicle infrastructure like power, ground or bus systems). In these cases more than one schematic plan exists as you can see in <imgref simple_example>​. There is a reference to a second sheet suggested by the arrow on the very bottom of the illustration. In <imgref advanced_example>​ the same system schematic from above is shown (now displayed in a blue section) and is extended by the red section containing the new component "​M.31" ​ with its pin "​A1"​. Sometimes there is the situation that concrete target components are unknown (or not yet defined) or different (topic specific) parts of a system schematic are developed independently as partial systems (e.g. vehicle infrastructure like power, ground or bus systems). In these cases more than one schematic plan exists as you can see in <imgref simple_example>​. There is a reference to a second sheet suggested by the arrow on the very bottom of the illustration. In <imgref advanced_example>​ the same system schematic from above is shown (now displayed in a blue section) and is extended by the red section containing the new component "​M.31" ​ with its pin "​A1"​.