Capital Wiring Integrator

Multiple Harnesses at

Connectors

You can create multiple harnesses at connectors to manage the installation of different harnesses to one connector.

Graphically, this is displayed as multiple bundles connected to the same connector cavity. You can add option expressions to the bundles to enable them to be filtered. See Filtering the Objects Displayed on a Diagram.

The primary scenario for multiple harnesses at a connector is at an inline connector, for example, where wires terminating at the inline belong to different harness part numbers. However, you can also have multiple harnesses at a connector on a slot, for example, if the H1 and H2 harnesses connect to the same connector. In this case, you might not want to duplicate the connectors on the slot.

Example 1: Example of Multiple Harnesses at a Connector

Copy

 
Both the H1 and H2 harnesses are connected to the single door harness by a single inline connector.

Scenarios Modeled Using Multiple Harnesses at

a Connector

The use of multiple harnesses at a connector enables you to model:

Mutually exclusive harnesses and connectors (including many-to-many mating) In this case, the cavities on the connector are connected to wires from multiple harnesses. You apply option expressions to the harnesses to ensure that only one is active at a time. A cavity can be connected to wires from different harnesses only if the signals on these wires are the same.
Poke home wires (wire from one harness plugged into the connector of another harness) This is where a wire is to be connected to a connector at harness installation time rather than harness manufacture time. This setting is not reflected graphically in the topology design but is passed on to Capital Harness Designer during synchronization. When this information is transferred to Capital Harness Classic or Capital Harness Designer, the connector is marked as “Not on BOM”. If any wire in a bundle is poked home, all wires in that bundle will be poked home. A simple case being where a harness has only poked home wires at a connector; all bundles at that connector for that harness contain only poke home wires.
EWIS scenario of multiple harnesses/bundles connected to a single connector Routing constraints are used to route wires down particular paths based upon a Separation Code property. For example, here are three differently colored bundles. The wires have been assigned a Separation Code property and the ‘Route by Attribute/Property’ constraint has been set on the different bundles to control the routing of the wires down the different harnesses (see Constraining the Routing

of Wires).

Synchronization with Capital Harness Designer

If you synchronize a design containing multiple harnesses at a connector with a harness design, Capital Harness Designer will recognize that not all the nodes at a connector belong to the harness being edited. In addition, it recognizes that just because a cavity has no wire in this harness, it does not mean a plug should be inserted into the cavity. The cavity might be required for a wire on another harness.

Example High-Level Flow Using Multiple Harnesses at Connectors

The following example gives high-level details of how multiple harnesses at connectors may be used. This is not the only flow that could be used.

Add a new bundle that starts or finishes at a connector that is already connected to another bundle; the system treats this as a new connection to a complex connector junction.
Add option expressions to the bundles to identify their applicability.
Specify bundles at the connector that contain poke home wires.
Synchronize the data with a design in Capital Harness Classic or Capital Harness Designer; the system treats the complex junction as if there is a connector applicable to each harness. Note All other tools that access the data (including reports, design rule checks and Capital E/E Reporter) treat the complex junction as if multiple bundles are connected to a single connector.

Parent Topic:

Capital Wiring Integrator