Capital Wiring Integrator > Constraints (Capital Wiring Integrator)

Standard Constraints for

Capital Wiring Integrator

Various constraints are available for use in Capital Wiring Integrator.

Attributes

and Properties

One Attributes and Properties constraint is available.

Set Topology Attribute/Property on Object

Default: Set Bundle AttrOrProp to Value where AttrOrProp = Value

Used to specify that a property or attribute must be set to a particular value on objects of a particular type when they have another property or attribute with a particular value. The property / attribute and value are assigned to the object when you select the Set Attribute/Property action from the ribbon in Capital Wiring Integrator. The “Object that breaks attribute/property rule” design rule check can be run to check for objects that violate this constraint.

See also Using a Constraint to Set an Attribute or Property on an Object and Applying the Set Topology Attribute/Property on Object Constraint.

Placement

Various Placement constraints are available.

Assign Connector by Attribute/Property

Default: Do assign connector to slot connector where Device connector Name = VC Name

Applied when you place devices attached to harness connectors in slots. Used to control whether a harness connector with a particular value for an attribute or property is mapped to a slot connector with an attribute or property that has the same value.

This constraint is not normally required as the default behavior is to associate connectors with the same name. This constraint would only be used if you wanted harness connectors in Capital Logic Designer to have different names from slot connectors in Capital Wiring Integrator.

See also Constraining the Association of Logical Harness Connectors to Slot Connectors.

Place by Attribute/Property

Default: Do place devices with attribute / property matching Name = Slot Name

Used to specify whether objects with a particular property or attribute should or cannot be placed in a slot. The system obeys this rule when automatically placing objects.

By default, the Place by Attribute/Property constraint is set for a topology diagram and is inherited by any slots. The default setting forces devices to be placed in slots with the same name. This default setting can be edited or removed.

See also Constraining the Placement of Devices in a Slot and Manually Placing a Device in a Slot.

Place bundle device by Attribute/Property

Default: Place bundle devices matching Name = .* at offset Value on bundle matching Name = .*

You can set this constraint on a bundle, a harness, or a design. Used to specify that the association process places particular devices on particular bundles at a particular position (offset from bundle start in same unit of measurement as you use for bundle length).

For example:

Place bundle device matching Name = DEV301 at offset 1.5 on bundle matching Name = BUN200

In this example, the association process places the device DEV301 as a bundle device on bundle BUN200. It places the bundle device 1.5 units from the start of the bundle.

See also Constraining the Placement of Bundle Devices on Bundles.

Place Inline Half by Attribute/Property

Default: Do place inline half with attribute / property matching Name = .Inline Half Name

Used to specify whether inline halves with a particular property or attribute (from Capital Logic Designer) should or should not be associated with particular inline halves in Capital Wiring Integrator. The system obeys this rule when automatically placing objects. This constraint can apply to inline connectors, harnesses and designs.

This constraint is not normally required as the default behavior is to associate inline halves with the same name. This constraint would only be used if you wanted inline halves in Capital Logic Designer to have different names from inline halves in Capital Wiring Integrator.

See also Constraining the Automatic Association of Inline Halves.

Routing

Various Routing constraints are available.

Assign Conductor/s to Hole by Attribute/Property

Default: Do assign conductor/s with attribute / property matching Name = .* to hole

Used to specify whether conductors with a particular property or attribute are or are not mapped to a particular hole on a slot. This constraint can apply to a hole.

See also Holes and Constraining the Mapping of Wires to a Hole on a Slot.

Minimum Splice Separation

Default: Minimum separation from splice to object = num where splice matches Name = .*

Used to specify the minimum distance that there must be between a splice and a connector, bundle device, takeout, or another splice. This can be set so that it only applies if a splice has an attribute or property with a particular value. This can be set on an entire diagram, on a bundle or on a harness.

See also Constraining the Placement of Splices on a Bundle.

Place Splice/s on Bundle by Attribute/Property

Default: Do place splice/s with attribute / property matching Name = .* on bundle

Used to specify whether splices with a particular property or attribute should or cannot be placed on a bundle. The system obeys this rule when automatically placing objects. This constraint can apply to bundles, harnesses and diagrams.

See also Constraining the Placement of Splices on a Bundle.

Route by Attribute/Property

Default: Don’t route conductors with attribute / property matching Name = Value here

Used to specify whether conductors with a particular property or attribute can or cannot be routed along a bundle, along a harness or through an inline pair. This constraint can apply to bundles, inline connectors, harnesses and diagrams.

The system evaluates the Route by Attribute/Property constraint in the following way for multicores and overbraids.

Multicore behavior

      Multicores (including innercores and shields) are treated as a complete unit.

      Routing requires all components to meet these requirements:

          
              The multicore's attributes/properties satisfy the constraints.

              All innercore attributes/properties satisfy the constraints.

              Shield attributes/properties satisfy the constraints.

              All constraints are met for both inlines and bundles.

Overbraid behavior

          Non-multicore wires in overbraid:

          
              The system evaluates each wire independently.

              The system routes wires only when their attributes/properties satisfy the constraints for inlines and bundles.

          

      

      
          Overbraid shields:

          
              The system evaluates shields independently.

              The system routes shields only when their attributes/properties satisfy the constraints within the overbraid harness.

          

      

      
          Multicores within overbraid:

          
              The system applies standard multicore behavior to each multicore independently
                                      (as in the *Multicore behavior* section
                                      above).

See also Constraining the Routing of Wires.

Routing Assistant

The following constraint applies when you use the Place Inline action from the Routing Assistant.

Pigtail usage by attribute/property

Default: Don't use pigtail for termination when shield Signal matches Name = .*

When placing inline connectors, the Routing Assistant uses pigtail wires to terminate shielded multicores at inline connectors if there is no applicable 'Pigtail usage by attribute/property' constraint. You can set this constraint on the topology design or on an inline half to control whether the Routing Assistant uses a pigtail, shield, or no termination for multicore shields for a shield signal with a particular attribute or property when placing an instance of an inline half.

If the constraint is set at design level, it applies to all inlines in the design. If it is set on an inline half, it applies when the Routing Assistant places instances of that particular inline half. A constraint on an inline half overrides a constraint on the design.

Note

Place Inline splits a multicore into two only if you perform the action on all conductors in the multicore, and all of them are located in the same diagram.

Constraint Usage	Result in Inline Placement for a Shielded Multicore
Not defined	Shield termination with pigtail
Do use pigtail	Shield termination with pigtail
Don't use pigtail	Shield termination
Do use shield	Shield termination
Don't use shield	No termination

Note

You can also define a custom constraint in Java that you add to a topology design or inline half to control shield termination type. For more information about writing and loading custom constraints, see the PluginDevelopment.pdf document that is located in the doc/plugin folder of your installation.

See Using the Routing Assistant to Identify the Possible Routes for One or More Unrouted Wires and Using the Routing Assistant to Identify Unrouted Wires for details of when the Place Inline action is used.

Note

You can run a design rule check 'Multicore that breaks Pigtail Usage constraint' to check that shield terminations for shielded multicores have not been edited in such a way to contradict 'Pigtail usage by attribute/property' constraints. See Design Rule Checks (Capital Wiring Integrator).

Parent Topic:

Constraints (Capital Wiring Integrator)