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
tutorials:vec:system_schematic_basics [2019/07/18 11:34]
4soft.becker
tutorials:vec:system_schematic_basics [2019/08/02 12:24]
4soft.becker removed
Line 9: Line 9:
  
 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. \\ 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 ​illustration ​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]].+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>​
Line 75: Line 75:
 <WRAP group> <WRAP group>
 <WRAP half column> <WRAP half column>
-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, ​have the black dots (circled in red) in the graphical example <imgref nodes> only a layouting purpose and do not represent a technical design decision (e.g. to place a splice on this spot). ​\\ +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) 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 two of the three 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.+ 
 +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 86: 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),​ which is only a available in the context of the complete vehicle. In <imgref simple_example>​ such a link to an unspecified infrastructure is represented by the down arrow, in the following sections this is called an **open link**. ​
  
-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_examplethe same system schematic ​from above is shown (now displayed in blue section) ​and is extended by the red section containing the new component "​M.31" ​ with its pin "​A1"​.+To create ​fully functional ​system, a partial system must be merged / combined with other partial systems. In this process matching open links are connected ​(and thus removedin order to create complete overall system. In <​imgref ​advanced_examplethis is illustrated by adding ​second partial system schematic (framed in red) to the original example from <​imgref ​simple_example>. The resulting overall ​system schematic ​of such merge process would just contain a simple connection between //​E.1.1// ​and //M31//
  
 <​imgcaption advanced_example |System Schematic Example with two parts>​{{:​tutorials:​vec:​simple_schematic_connections_plan2.png?​|}}</​imgcaption>​ <​imgcaption advanced_example |System Schematic Example with two parts>​{{:​tutorials:​vec:​simple_schematic_connections_plan2.png?​|}}</​imgcaption>​
Line 93: Line 97:
 <​imgcaption types |Open Enumeration with OpenLink>​{{ :​tutorials:​vec:​componentnode_types.png?​200|}}</​imgcaption>​ <​imgcaption types |Open Enumeration with OpenLink>​{{ :​tutorials:​vec:​componentnode_types.png?​200|}}</​imgcaption>​
  
-To transfer the changes in this advanced schematic example into the VEC context it is neccessary to know some more background information. To bracket ​each content of a partial plan in a logical context, more than one [[:​models:​vec_v1_1_3:​classes:​documentversion|DocumentVersion]] with a [[:​models:​vec_v1_1_3:​classes:​connectionspecification|ConnectionSpecification]] ​each can be used in the same [[:​models:​vec_v1_1_3:​classes:​veccontent|VecContent]]. ​In this case the [[:​models:​vec_v1_1_3:​classes:​componentnode|ComponentNode]] ​for "M.31" can be placed ​in a second [[:​models:​vec_v1_1_3:​classes:​connectionspecification|ConnectionSpecification]] and can be referenced by a [[:​models:​vec_v1_1_3:​classes:connectionend|ConnectionEnd]] of a Connection from our first example even if it is not in the same specification\\ +The mapping of this advanced schematic example into the VEC context it is the following (see <imgref advanced_example_diagram>​) 
-In case of not having ​the second specification at all though ​the VEC provides a possibility to model the system schematic. The [[:​models:​vec_v1_1_3:​classes:​componentnode|ComponentNode]] ​with its sub elements ​can easily be placed in the same ConnectionSpecification. To mark it as a not included node the enumeration ​[[:​models:​vec_v1_1_3:​enums:componentnodetype|ComponentNodeType]] contains ​the specific value “OpenLink” (see <imgref types> on the right).+  - To maintain the logical grouping of each partial system schematic, the content of each is contained ​in its own [[:​models:​vec_v1_1_3:​classes:​documentversion|DocumentVersion]] with a single ​[[:​models:​vec_v1_1_3:​classes:​connectionspecification|ConnectionSpecification]] in the same [[:​models:​vec_v1_1_3:​classes:​veccontent|VecContent]]. 
 +  -  The open link is represented by a "​virtual" ​[[:​models:​vec_v1_1_3:​classes:​componentnode|ComponentNode]]. ​Its naming is arbitrary and shall be choosen ​in a way, that a merge algorithm has the required information. For the clarity of the example it is here named //GROUND//. Depending on the used merge algorithm the name can be irrelevant if the merge algorithm for example only requires signal information. 
 +  - The "​virtual"​ component node shall be marked with the [[:​models:​vec_v1_1_3:​enums:componentnodetype|ComponentNodeType]] literal //​OpenLink//​ (see <imgref types> on the right)
 + 
 +<imgref advanced_example_diagram>​ shows the extended diagram with the [[:​models:​vec_v1_1_3:​classes:​componentnode|ComponentNode]] ​"​GROUND"​. As you can see the [[:​models:​vec_v1_1_3:​classes:componentnode|ComponentNode]] is marked with the node type “OpenLink” (red markto clarify that this component is NOT part of the system schematic but components from the plan DO HAVE a connection to it
  
-<imgref advanced_example_diagram>​ shows the extended diagram with the [[:​models:​vec_v1_1_3:​classes:​componentnode|ComponentNode]] ​"​M.31"​. As you can see the [[:​models:​vec_v1_1_3:​classes:​componentnode|ComponentNode]] is marked ​with the node type “OpenLink” (red mark) to clarify that this component ​is NOT part of the system schematic but components from the plan DO HAVE a connection ​to it+**//​__Caution:​__//​** The strategy and algorithm to merge partial systems if individual for the different ECAD systems and development processes. The VEC does not define an algorithm or requires a specific strategy. The VEC only the means to store and exchange the information that is required by those algorithms. When merging the definition of these partial systems together into one vehicle system, it is mandatory to resolve these open links and replace them by determined ​[[:​models:​vec_v1_1_3:​classes:​componentnode|ComponentNode]] ​elements or [[:​models:​vec_v1_1_3:​classes:​connectionspecification|Connection]]
 +  - **Case 1:** The open link component node is replaced by a real component ​with the required connectivity. 
 +  - **Case 2:** If multiple real component nodes have connections ​to different open link component ​nodes, ​the open link nodes can be merged to single ​connection ​among the real component nodes.
  
-**//__Caution:​__//​** ​When merging the definition of these partial systems together into one vehicle system, it is mandatory to resolve these open links and replace them by determined [[:​models:​vec_v1_1_3:​classes:​componentnode|ComponentNode]] elements. ​It is also possible to reference ​the concerning ​[[:​models:​vec_v1_1_3:​classes:​componentport|ComponentPort]] ​by a Connection/​ConnectionEnd even though it is not part of the same [[:​models:​vec_v1_1_3:​classes:​documentversion|DocumentVersion]]+**//__Note:__//** It is possible to reference ​[[:​models:​vec_v1_1_3:​classes:​componentport|ComponentPort]] ​from a Connection/​ConnectionEnd even if they are contained in different ​[[:​models:​vec_v1_1_3:​classes:​documentversion|DocumentVersion]].
  
 <​imgcaption advanced_example_diagram |Advanced System Schematic Example>​{{ :​tutorials:​vec:​simple_schematic_connections3.png?​900 |}}</​imgcaption>​ <​imgcaption advanced_example_diagram |Advanced System Schematic Example>​{{ :​tutorials:​vec:​simple_schematic_connections3.png?​900 |}}</​imgcaption>​
Line 117: Line 127:
             </​ComponentNode>​             </​ComponentNode>​
             <​ComponentNode id="​id_comp_node_2634">​             <​ComponentNode id="​id_comp_node_2634">​
-                <​Identification>​M.31</​Identification>​+                <​Identification>​GROUND</​Identification>​
                 <​ComponentNodeType>​OpenLink</​ComponentNodeType>​                 <​ComponentNodeType>​OpenLink</​ComponentNodeType>​
                 <​ComponentConnector id="​id_component_connector_2636">​                 <​ComponentConnector id="​id_component_connector_2636">​
Line 128: Line 138:
             [...]             [...]
             <​Connection id="​id_connection_2885">​             <​Connection id="​id_connection_2885">​
-                <​Identification>​M.31..SYS_055A</​Identification>​+                <​Identification>​GROUND..SYS_055A</​Identification>​
                 <​ConnectionEnd id="​id_conn_end_2886">​                 <​ConnectionEnd id="​id_conn_end_2886">​
                     <​Identification>​E1.1-A1</​Identification>​                     <​Identification>​E1.1-A1</​Identification>​
Line 134: Line 144:
                 </​ConnectionEnd>​                 </​ConnectionEnd>​
                 <​ConnectionEnd id="​id_conn_end_2887">​                 <​ConnectionEnd id="​id_conn_end_2887">​
-                    <​Identification>​M.31-A1</​Identification>​+                    <​Identification>​GROUND-A1</​Identification>​
                     <​ConnectedComponentPort>​id_comp_port_2639</​ConnectedComponentPort>​                     <​ConnectedComponentPort>​id_comp_port_2639</​ConnectedComponentPort>​
                 </​ConnectionEnd>​                 </​ConnectionEnd>​