Capital Knowledge Base | Siemens Capital Documentation

Rules and Constraints

	Overview

In Capital Logic Designer, you can use constraints to set properties and attributes on objects and to exclude specific nets from conversion to wires.

In Capital Systems Integrator, you can set rules and constraints to control how the system places devices in slots, synthesizes wiring, and sets properties / attributes for objects. See “Overview of Rules and Constraints” in the Capital Systems Integrator User Guide for all the available constraints.

If you are using Capital Wiring Integrator, see Constraints (Capital Wiring Integrator) for details of the available constraints. Otherwise, use the information in this chapter to use the rules and constraints in general.

Standard Constraints for Capital Logic

				Designer

In Capital Logic Designer, a constraint is a statement that you can set for a whole design only.

You use constraint templates in Capital Logic Designer and Capital Systems Integrator to define a constraint.

You can write your own custom constraints in Java and load them into Capital Systems Integrator or Capital Logic Designer. For more information about writing and loading custom constraints, see the PluginDevelopment.pdf document that is located in the doc\plugin folder of your Capital installation. Once custom constraints are loaded, you use them in the same way as standard constraints. An object can have both standard and custom constraints defined for it.

The design rule check Missing Custom Constraint Check can be run to report on any custom constraints that have been defined for an object but are not loaded any longer in Capital Systems Integrator or Capital Logic Designer. See also Design Rule Checks.

The constraint templates available in Capital Logic Designer:

Attributes and Properties

Set Logic Attribute/Property on Object

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 specified property / attribute and value are assigned to the object when you run the Apply Constraints action in Capital Logic Designer. The “Objects that break attribute/property rule” design rule check can be run to check for objects that violate this constraint. You can only set this constraint for a whole design. Used in Capital Logic Designer only. See Using a Constraint to Set Properties and Attributes on Objects.

Nets to Wires

Exclude Nets or Multicores from the Nets to Wires conversion

Default: Do not convert Net to wire where AttrOrProp = Value Used to specify that a net or multicore is excluded from the Nets to Wires action. You can only set this constraint for a whole design. Used in Capital Logic Designer only. To exclude both nets and multicores from the action, you must apply at least two of these constraints to a design. When set for nets, a constraint is applied as follows: Nets that meet the constraint and are not in a multicore are excluded from the action

Nets in a multicore (even if they meet the constraint) are not excluded from the action

When set for multicores, the constraint is applied as follows: Multicores that meet the constraint and are not nested within another multicore are excluded from the action and so are any nets or multicores nested within those multicores

Multicores that meet the constraint but are nested within a parent (top-level) multicore that does not meet the constraint are not excluded from the action

See Excluding Nets From the Conversion to Wires.

Rules

In Capital Logic Designer, a rule is a group of constraints that can be applied to a whole design. You can define rules from within Capital Logic Designer or Capital Project Manager. In Capital Project Manager, you can define rules at a project level or define rule libraries at a system level. A rule library can be added to a project. See the Capital Project Manager User Guide to define rule libraries.

Parent Topic:

Rules and Constraints