User Tools

Site Tools


tutorials:vec:coupling_devices

Work on following article or section is in progress

Coupling Devices

Basics

Fig. 1: Coupling Device Example

Coupling devices are used for several reasons. For example to connect two or more seperate harnesses to a vehicle electrical system. But sometimes in a harness itself, too, when there is a space problem in the transposition and the harness has to be devided until it is located in the vehicle.
The VEC contains a hand full of posibilities to define coupling devices on different design levels which this article will descibe using a continuous example which can be found in figure 1 above.

Coupling Devices in System Schematics

Fig. 2: Coupling Device in System Schematic 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. It is a snippet from the shown example from figure 1. 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 ConnectionEndswhere isExternal=true.

Variance

8_2_2_variance.jpg Fig. 3: Variance handling in VEC 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.

VEC Structure and Part Master Data

Fig. 4: Basic idea of coupling devices in VEC

The basic idea of modelling coupling devices in the VEC is to consider each of these devices in a vehicle electrical system as a single virtual construction object. Taking a look to the physical components of a coupling device only, we can just see two or more connectors which are plugged together (or connected in some way). With the introduction of an additional virtual component as a placeholder it is possible to mark and place a connector as a part of the defined coupling device. This also allows the coupling device to exist even if the counter part of one connector is still missing AND the virtual device can be used as an interface contract, too.

Fig. 5: Part Master Definition of virtual Coupling Component

In figure 5 you can find the VEC diagram of the part master definition of such a virtual ee component and Listing 1 shows this example as xml snippet.
It all starts with an EEComponentSpecification and a HousingComponent for each slot on each side of the coupling device. Underneath them the pins are located, each represented by a PinComponent. For clarity reasons the ConnectorHousingSpecifications are not displayed in the examples but they are necessary for a complete vec model.
To illustrate that there is a conductive connection between one side and the other side, an InternalComponetConnection is placed in the EEComponentSpecification for each “pair” of pins (A1 and A2) and references the corresponding PinComponent.

Listing 1:

<DocumentVersion id="id_docu_ver_16475">
    <Description xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:type="ns2:LocalizedString" id="id_16476">
        <LanguageCode>De</LanguageCode>
        <Value>TQVL</Value>
    </Description>
    <DocumentNumber>VWK_TQVL</DocumentNumber>
    <DocumentType>PartMaster</DocumentType>
    <Specification xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:type="ns2:ConnectorHousingSpecification" id="id_connect_hous_spec_16505">
        <Identification>CHS_TQVL.1A</Identification>
        <Description xsi:type="ns2:LocalizedString" id="id_16506">
            <LanguageCode>De</LanguageCode>
            <Value>ConnectorHousingSpecification for id: '1A' of 'TQVL'</Value>
        </Description>
        <Slot xsi:type="ns2:Slot" id="id_slot_16509">
            <Cavity id="id_cavity_16510">
                <CavityNumber>1</CavityNumber>
            </Cavity>
            <Cavity id="id_cavity_16511">
                <CavityNumber>2</CavityNumber>
            </Cavity>
        </Slot>
    </Specification>
    <Specification xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:type="ns2:ConnectorHousingSpecification" id="id_connect_hous_spec_16507">
        <Identification>CHS_TQVL.2A</Identification>
        <Description xsi:type="ns2:LocalizedString" id="id_16508">
            <LanguageCode>De</LanguageCode>
            <Value>ConnectorHousingSpecification for id: '2A' of 'TQVL'</Value>
        </Description>
        <Slot xsi:type="ns2:Slot" id="id_slot_16514">
            <Cavity id="id_cavity_16515">
                <CavityNumber>1</CavityNumber>
            </Cavity>
            <Cavity id="id_cavity_16516">
                <CavityNumber>2</CavityNumber>
            </Cavity>
        </Slot>
    </Specification>
    <Specification xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:type="ns2:EEComponentSpecification" id="id_ecomponent_spec_16519">
        <Identification>EECS_TQVL</Identification>
        <Description xsi:type="ns2:LocalizedString" id="id_localizedString_16520">
            <LanguageCode>De</LanguageCode>
            <Value>EEComponentSpecification for TQVL</Value>
        </Description>
        <SpecialPartType>CouplingDevice</SpecialPartType>
        <Connections id="id_intern_comp_conn_16551">
            <Identification>ICC_A_female-1*A_male-1</Identification>
            <Pins>id_pin_comp_16543 id_pin_comp_16547</Pins>
        </Connections>
        <Connections id="id_intern_comp_conn_16552">
            <Identification>ICC_A_female-2*A_male-2</Identification>
            <Pins>id_pin_comp_16544 id_pin_comp_16548</Pins>
        </Connections>
        <HousingComponent id="id_housing_comp_16541">
            <Identification>A_female</Identification>
            <HousingSpecification>id_connect_hous_spec_16505</HousingSpecification>
            <PinComponent id="id_pin_comp_16543">
                <Identification>1</Identification>
                <ReferencedCavity>id_cavity_16510</ReferencedCavity>
            </PinComponent>
            <PinComponent id="id_pin_comp_16544">
                <Identification>2</Identification>
                <ReferencedCavity>id_cavity_16511</ReferencedCavity>
            </PinComponent>
        </HousingComponent>
        <HousingComponent id="id_housing_comp_16542">
            <Identification>A_male</Identification>
            <HousingSpecification>id_connect_hous_spec_16505</HousingSpecification>
            <PinComponent id="id_pin_comp_16547">
                <Identification>1</Identification>
                <ReferencedCavity>id_cavity_16510</ReferencedCavity>
            </PinComponent>
            <PinComponent id="id_pin_comp_16548">
                <Identification>2</Identification>
                <ReferencedCavity>id_cavity_16511</ReferencedCavity>
            </PinComponent>
        </HousingComponent>
    </Specification>
</DocumentVersion>

Instantiation and Usage

After defining the part master data of the coupling device it is mandatory to create an instance for each appearance in the modelled context. This procedure is like instantiating any other (physical) part, too. On each level of detail a class from the part master data gets its representation with a corresponding class for intantiation. A EEComponentRole is created for the Specification, there are two HousingComponentReferences for the slots and underneath them the PinComponentReferences are located.

The following code shows the xml representation of the instantiation of the virtual ee component from listing 1. In figure 6 the instance model can be found. It is part of the whole coupling example, the matching elements are colored in orange.

Listing 2:

<Specification xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:type="ns2:PartUsageSpecification" id="id_part_usage_spec_16577">
        <Identification>CouplingDeviceList</Identification>
        <Description xsi:type="ns2:LocalizedString" id="id_localizedString_16578">
            <LanguageCode>De</LanguageCode>
            <Value>Coupling Device Instance</Value>
        </Description>
        <PartUsage id="id_part_usage_16579">
            <Identification>TQVL</Identification>
            [...]
            <Role xsi:type="ns2:EEComponentRole" id="id_ee_role_16580">
                <Identification>TQVL</Identification>
                <EEComponentSpecification>id_ecomponent_spec_16519</EEComponentSpecification>
<HousingComponentRef id="id_housing_comp_ref_16617">
                    <Identification>A_female</Identification>
                    <HousingComponent>id_housing_comp_16541</HousingComponent>
                    <ConnectorHousingRole id="id_conHousingRole_16618">
                        <ConnectorHousingSpecification>id_connect_hous_spec_16505</ConnectorHousingSpecification>
                        <SlotReference xsi:type="ns2:SlotReference" id="id_slotRef_16619">
                            <ReferencedSlot>id_slot_16509</ReferencedSlot>
                            <CavityReference id="id_cavityRef_16620">
                                <Identification>1</Identification>
                                <ReferencedCavity>id_cavity_16510</ReferencedCavity>
                            </CavityReference>
                            <CavityReference id="id_cavityRef_16621">
                                <Identification>2</Identification>
                                <ReferencedCavity>id_cavity_16511</ReferencedCavity>
                            </CavityReference>
                        </SlotReference>
                    </ConnectorHousingRole>
                    <PinComponentRef id="id_pin_comp_ref_16624">
                        <PinComponent>id_pin_comp_16543</PinComponent>
                    </PinComponentRef>
                    <PinComponentRef id="id_pin_comp_ref_16625">
                        <PinComponent>id_pin_comp_16544</PinComponent>
                    </PinComponentRef> 
                </HousingComponentRef>
                <HousingComponentRef id="id_housing_comp_ref_16628">
                    <Identification>A_male</Identification>
                    <HousingComponent>id_housing_comp_16542</HousingComponent>
                    <ConnectorHousingRole id="id_conHousingRole_16629">
                        <ConnectorHousingSpecification>id_connect_hous_spec_16505</ConnectorHousingSpecification>
                        <SlotReference xsi:type="ns2:SlotReference" id="id_slotRef_16630">
                            <ReferencedSlot>id_slot_16509</ReferencedSlot>
                            <CavityReference id="id_cavityRef_16631">
                                <Identification>1</Identification>
                                <ReferencedCavity>id_cavity_16510</ReferencedCavity>
                            </CavityReference>
                            <CavityReference id="id_cavityRef_16632">
                                <Identification>2</Identification>
                                <ReferencedCavity>id_cavity_16511</ReferencedCavity>
                            </CavityReference>   
                        </SlotReference>
                    </ConnectorHousingRole>
                    <PinComponentRef id="id_pin_comp_ref_16635">
                        <PinComponent>id_pin_comp_16547</PinComponent>
                    </PinComponentRef>
                    <PinComponentRef id="id_pin_comp_ref_16636">
                        <PinComponent>id_pin_comp_16548</PinComponent>
                    </PinComponentRef>
                </HousingComponentRef>
            </Role>
            <PrimaryPartUsageType>EEComponent</PrimaryPartUsageType>
            <PartOrUsageRelatedSpecification>id_ecomponent_spec_16519</PartOrUsageRelatedSpecification>
        </PartUsage>
    </Specification>

Asign components to the coupling device

In a last step the information about the concrete coupling between the connectors and the coupling device is completed. To do so a CouplingSpecification is needed. For each coupling of two connectors (1A1 ↔ 2A1 in the example) are two CouplingPoints needed. In figure 6 these are colored in blue. The first one is to describe the coupling of 1A1 (green) to the instance of the virtual device (orange) and the second one for 2A1 (red). Each CouplingPoint gets its full description on every level. The instance of the connector from the harness and the slot from the coupling device, represented by a ConnectorHousingRole, are referenced as first and second connector. Underneath the CouplingPoint a SlotCoupling is located where the SlotReferences from the roles are referenced. One step deeper the CavityCoupling with its first and second cavity defines the connection at pin level for each CavityReference.

figure 6 shows the diagram of the instances of the example, listing 3 the corresponding xml code.

Fig. 6

Listing 3:

<Specification xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:type="ns2:CouplingSpecification" id="id_coupling_spec_16667">
        <Identification>TQVL</Identification>
        <CouplingPoint id="id_coupling_point_16685">
            <Identification>TQVL.1A1</Identification>
            <FirstConnector>id_conHousingRole_16618</FirstConnector>
            <SecondConnector>id_conHousingRole_10227</SecondConnector>
            <SlotCoupling id="id_slotCoupling_16686">
                <FirstSlot>id_slotRef_16619</FirstSlot>
                <SecondSlot>id_slotRef_10228</SecondSlot>
                <CavityCoupling id="id_cavity_coupling_16687">
                    <Identification>1</Identification>
                    <FirstCavity>id_cavityRef_16620</FirstCavity>
                    <SecondCavity>id_cavityRef_10229</SecondCavity>
                </CavityCoupling>
                <CavityCoupling id="id_cavity_coupling_16688">
                    <Identification>2</Identification>
                    <FirstCavity>id_cavityRef_16621</FirstCavity>
                    <SecondCavity>id_cavityRef_10230</SecondCavity>
                </CavityCoupling>
            </SlotCoupling>
        </CouplingPoint>
        <CouplingPoint id="id_coupling_point_16703">
            <Identification>TQVL.2A1</Identification>
            <FirstConnector>id_conHousingRole_16629</FirstConnector>
            <SecondConnector>id_conHousingRole_10500</SecondConnector>
            <SlotCoupling id="id_slotCoupling_16704">
                <FirstSlot>id_slotRef_16630</FirstSlot>
                <SecondSlot>id_slotRef_10501</SecondSlot>
                <CavityCoupling id="id_cavity_coupling_16705">
                    <Identification>1</Identification>
                    <FirstCavity>id_cavityRef_16631</FirstCavity>
                    <SecondCavity>id_cavityRef_10502</SecondCavity>
                </CavityCoupling>
                <CavityCoupling id="id_cavity_coupling_16706">
                    <Identification>2</Identification>
                    <FirstCavity>id_cavityRef_16632</FirstCavity>
                    <SecondCavity>id_cavityRef_10503</SecondCavity>
                </CavityCoupling>
            </SlotCoupling>
        </CouplingPoint>
    </Specification>
    <Specification xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns2:CompositionSpecification" id="id_composition_spec_8590">
        <Identification>COMPONENTS</Identification>
    <Component id="id_partOccurrence_10223"> 
        <Identification>1A1</Identification>
        <Role xsi:type="ns2:ConnectorHousingRole" id="id_conHousingRole_10227">
            <Identification>1A1</Identification>
            <ConnectorHousingSpecification>id_connect_hous_spec_6878</ConnectorHousingSpecification>
            <SlotReference xsi:type="ns2:SlotReference" id="id_slotRef_10228">
                <Identification>default</Identification>
                <ReferencedSlot>id_slot_6880</ReferencedSlot>
                <CavityReference id="id_cavityRef_10229">
                    <Identification>1</Identification>
                    <ReferencedCavity>id_cavity_6881</ReferencedCavity>
                </CavityReference>
                <CavityReference id="id_cavityRef_10230">
                    <Identification>2</Identification>
                    <ReferencedCavity>id_cavity_6882</ReferencedCavity>
                </CavityReference>
            </SlotReference>
        </Role>
    </Component>
        <Component id="id_partOccurrence_10495">
            <Identification>2A1</Identification>
            <Role xsi:type="ns2:ConnectorHousingRole" id="id_conHousingRole_10500">
                <Identification>2A1</Identification>
                <ConnectorHousingSpecification>id_connect_hous_spec_7126</ConnectorHousingSpecification>
                <SlotReference xsi:type="ns2:SlotReference" id="id_slotRef_10501">
                    <Identification>default</Identification>
                    <ReferencedSlot>id_slot_7128</ReferencedSlot>
                    <CavityReference id="id_cavityRef_10502">
                        <Identification>1</Identification>
                        <ReferencedCavity>id_cavity_7129</ReferencedCavity>
                    </CavityReference>
                    <CavityReference id="id_cavityRef_10503">
                        <Identification>2</Identification>
                        <ReferencedCavity>id_cavity_7130</ReferencedCavity>
                    </CavityReference>
                </SlotReference>
            </Role>   
        </Component>
    </Specification>
tutorials/vec/coupling_devices.txt · Last modified: 2019/08/02 12:08 by 4soft.fehlmann