User Tools

Site Tools



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/05/21 12:29]
— (current)
Line 1: Line 1:
-====== System Schematic Basics ====== 
-KBLFRM-599 ​ \\ 
-<​imgcaption plan| System Schematic>​{{ ​   :​tutorials:​vec:​simple_schematic_connections_plan2.png?​600|}}</​imgcaption>​ 
-<imgref plan> on the right shows examples of two system schematics, the blue and the red one. In the blue system schematic, a switch (E1.1) is connected to a left tail light (MX1.1) and, because of the 150% scope, to the two versions of a left headlight (MX3.1 und MX3.2). 
-The headlight is linked to the usage node MX1 to which exactly one template MX1.1 exists. There are two different headlights (B and D) which are connection compatible and therefore connected to the same template. 
-The tail light has the usage node MX3. And there are two different versions (G and A) as well. This time they are not connection compatible and are therefore connected via the two different templates MX3.1 and MX3.2. 
-The EEcomponents on the plan are connected to each other via the potentials M.31S, V.58 and V.58L. The switch is connected to the ground via the potential M.31, which is linked through several partial system schematics. A1, A2 and A3 are the pins of the components. 
-In the VEC the system schematic is mapped in a DocumentVersion below the VecContent element. \\ 
- \\ 
-<​imgcaption diagram| System Schematic>​{{ ​   :​tutorials:​vec:​simple_schematic_connections3.png?​600 |}}</​imgcaption>​ 
-The diagram in <imgref diagram> illustrates a simple scenario of a system schematic. Each component is represented by a ComponentNode with ComponentConnectors and ComponentPorts. The ComponentPorts represent the Pins of a component, the ComponentConnector is a grouping of the ComponentPorts. In the graphical example, the ComponentConnector is not represented explicitly, but implicitly. In the pin numbering (e.g. A1) the "​A"​ means connector "​A"​. 
-The connections between the pins are represented by a Connection with ConnectionEnds. In case of partial systems or early development states some pins may not have been connected yet. As you can see there is still a link from the ConnectionSpecification to the right ComponentNode "​MX4.1"​ but their pin is not referenced by any ConnectionEnd. Whether non-connected nodes are referenced by the specification or not is in the free decision of the implementation. 
-=== Potential Nodes === 
-The black dots (circled in red) in the graphical example <imgref potential>​ 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 three 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 there will be just one of two representative electrical components in the final scope of a specific vehicle (100% scope). 
-As the VEC does not represent graphical layout of documents, but only product describing content of those, these nodes have no representation in VEC. 
-<​imgcaption potential| System Schematic>​{{ :​tutorials:​vec:​simple_schematic_connections_plan.png?​400 |}}</​imgcaption>​ 
-{{tag>​tutorials:​vec:​v113 unpublished}} 
tutorials/vec/system_schematic_basics.1558434577.txt.gz · Last modified: 2019/05/21 12:29 by 4soft.fehlmann