Route Wire Through Bundle by Attribute/Property Constraint

You can control the wire path of automatically routed wires by using a constraint which controls which wires can pass along bundles matching a query. This constraint is available at the system, project and design level.

Usage

Copy

Don't route wire matching Name = .* through bundle matching Name = .*

Arguments

Arguments	Description
CopyDon't	Use to specify whether to allow or prevent wires from passing through matching bundles. Values are: Don't — Matching wires must not be routed through the matching bundles. Non-matching wires can be routed through the matching bundles if appropriate. Only — Matching wires can be routed through the matching bundles if appropriate. Non-matching wires are not allowed to be routed through the matching bundles.
CopyName = .*	Use to specify an attribute or property condition to drive the selection of the associated matching object, either a wire or a bundle. Click Name to select the attribute or property to match. Click = to select the matching condition. Click .* to enter the value of the attribute or property to be matched.

Description

Any conflicts between the settings of the constraint and the paths of the existing wires in the design are reported by the design rule check "Wire that breaks routing rule." See Capital Harness Designer and Capital Harness Designer Modular - Harness Designer Rules DRCs.

When you perform Route Wires, the wire attribute Routed By Constraint is set to True for any wires affected by the constraint.

Routing success or failure is reported on the Wire Routing tab. Click the hyperlink in the message for more information.

Examples

In this example, the default path of the two wires is though bundles BUN1, BUN2 and BUN4, the shortest path between the two ends of the wires.

Figure 129: Shortest Route for Wires

WIRE1 is a high voltage wire, which is identified by a property "IsHV=True". High voltage wires cannot travel through BUN2, as it is in a high temperature area, identified by a property "HotZone=True".

We configure the following constraint on the design:

Figure 130: Example Wire Routing Constraint

When we perform Route Wires, WIRE1 is routed through BUN3 as the constraint prevents it from passing through BUN2.

Figure 131: Wire Routing Constraint Defines Path of WIRE1

Parent Topic:

Rule Based Wire Routing

Capital Harness Designer User Guide, 2512

Unpublished work. © 2025 Siemens