P-Cad 2006 Pcs User's Guide
P-Cad 2006 Pcs User's Guide
P-Cad 2006 Pcs User's Guide
Altium Limited
Copyrights
This software product is copyrighted and all rights are reserved. The distribution and sale of this product
are intended for the use of the original purchaser only per the terms of the License Agreement.
This document may not, in whole or part, be copied, photocopied, reproduced, translated, reduced or
transferred to any electronic medium or machine-readable form without prior consent in writing from
Altium Limited.
U.S. Government use, duplication or disclosure is subject to RESTRICTED RIGHTS under applicable
government regulations pertaining to trade secret, commercial computer software developed at private
expense, including FAR 227-14 subparagraph (g)(3)(i), Alternative III and DFAR 252.227-7013 subparagraph
(c)(1)(ii).
P-CAD is a registered trademark and P-CAD Schematic, P-CAD Relay, P-CAD PCB, P-CAD ProRoute, P-CAD
QuickRoute, P-CAD InterRoute, P-CAD InterRoute Gold, P-CAD Library Manager, P-CAD Library Executive,
P-CAD Document Toolbox, P-CAD InterPlace, P-CAD Parametric Constraint Solver, P-CAD Signal Integrity,
P-CAD Shape-Based Autorouter, P-CAD DesignFlow, P-CAD ViewCenter, Master Designer and Associate
Designer are trademarks of Altium Limited. Other brand names are trademarks of their respective
companies.
Altium Limited
www.altium.com
Table of Contents
Index .......................................................................................................................................... 87
Congratulations on your purchase of the P-CAD Parametric Constraint Solver. P-CAD’s Parametric
Constraint Solver (PCS) is a productivity-enhancing tool that enables true rules based design.
With PCS, designers can comprehensively view and manipulate Schematic and PCB design rules in
rule-precedence order. Most importantly, design rules can be defined as constant values or
mathematical expressions, and may also be defined in terms of other design rules, providing a
parametric, precedence-based, rules-driven system.
The Parametric Constraint Solver provides a vehicle in which a design’s constraint values can be
defined in a variety of ways: as a constant, formula, vector, or as the result of a mathematical
expression which can be based on one or more other design constraints.
The updates made to a design in PCS are saved to the PCB or Schematic design file. PCB routing,
copper pour, online DRC, and placement tools honor PCS width and clearance restrictions. In
addition, DRC validates the completed design against the constraints defined in PCS, including
widths, clearance, and room constraints such as room inclusion and height restrictions.
With PCS, a circuit board designer has easy access to the PCB and Schematic design rules. You can
view the hierarchical order of the design constraints from an individual component rule up to the
global design rules and quickly determine the order of precedence in which these rules will be
applied to and affect your design. Constraints are easily added to and removed from any level of
the rules hierarchy and can also be added to and removed from multiple items with just one
operation.
P-CAD Parametric Constraint Solver is an advanced constraint management tool for the Microsoft®
Windows 95™, Windows 98™, Windows 2000™, or Windows NT™ operating systems. The
Parametric Constraint Solver contains a combination of features designed to significantly reduce
the number of design iterations needed to produce a successful board layout.
lowest: component, room, class-to-class, net, net class, layer and design. From this hierarchy
you can easily add constraints to and remove constraints from any of the levels.
• Constraints as expressions. PCS provides the ability to use expressions to define your design
rules. An expression can use constants, formulas or vectors and may include references to
other constraints.
• Constraints based on other constraints. A constraint expression can be based on and/or
reference other constraints from any precedence level in the design. When the value of one
constraint is modified, the result is applied to any expressions that referenced it, and their
values are changed as well.
• Math and Trig Functions. A comprehensive suite of mathematical and trigonometric functions
are supported by the PCS Constraint Editor.
• Constraint validation. Constraints are evaluated at the time they are defined and whenever a
design is loaded into PCS. Synchronizing the updates between the applications helps
eliminate errors that may occur due to changes made in PCB or Schematic.
• Unit selection. You can choose a constraint’s unit. For instance, a clearance constraint can be
a length unit such as an inch, mil, millimeter or centimeter. User-defined constraints provide
the opportunity to assign any of the available units.
• Assignment to multiple design objects at one time. With PCS it’s easy to assign a constraint to
many items at once, instead of many times to individual items.
• Constraint data saved in originating design. Updates made to the design in PCS are saved to
the originating design file, eliminating any need to repeat the process in multiple applications.
• Organizing the design objects. You can use the Design Manager in PCS to organize the
various objects in the design so that assigning constraints becomes quick and easy. The
contents of the design data (i.e., components and nets) can be defined in terms of partitions,
rooms, net classes and class-to-class rules.
• Application integration. P-CAD PCB, P-CAD Relay and P-CAD Schematic software is tightly
integrated with P-CAD Parametric Constraint Solver assuring the synchronization of design file
updates between the applications.
• Using InterPlace and PCS: Chapter 8 provides information on the additional placement
functionality available when both P-CAD Parametric Constraint Solver and P-CAD InterPlace
are used together.
• The Parametric Constraint Solver Reference: Chapters 9 through 11 and Appendices A and B
include an extensive reference on the PCS commands and covers all of the variables the
Parametric Constraint Solver allows when assigning values to the constraints.
This chapter lists the required hardware and software settings you need to install the P-CAD Suite.
System Requirements
Make sure that your PC and its software conform to the following P-CAD requirements and
recommendations.
Recommended System
• Windows NT 4/2000 Professional
• PC with Pentium III Processor
• 128MB RAM (256MB for high component/net count)
• 400MB Hard Disk Space
• Desktop area 1024x768 pixels
• 32-bit Color Palette
• CD-ROM Drive
• Mouse or compatible pointing device.
Minimum System
• Windows 95/98/2000Me
• PC with Pentium 166MHz
• 64MB RAM
• 200MB Hard Disk Space (without ISO libraries)
• Desktop area 800x600 pixels
• 256 Color Palette
• CD-ROM Drive
• Mouse.
This chapter introduces many of the basic features you need to know when using the P-CAD
Parametric Constraint Solver. It includes general information on such topics as:
• Using PCS from PCB, Relay, or Schematic
• PCS user interface.
• Loading, saving, and closing a design.
• Right mouse commands.
What is presented here is a high level look at Parametric Constraint Solver capabilities. These
capabilities are detailed in later chapters.
To keep with the easy-to-use tradition of P-CAD applications, much of the basic functionality of P-
CAD Parametric Constraint Solver is similar to P-CAD PCB. As a Windows user, you will also be
familiar with the basic manipulations employed in managing constraints in PCS.
Unless specified, all references to the Parametric Constraint Solver features, relevant when a PCB
design is loaded, are also applicable when a Relay design is loaded.
When you access PCS from PCB you have access to the Design Manager and the Constraint Editor
in which to organize your design objects and define the desired constraints. Each of these aspects
of the Parametric Constraint Solver interface is discussed in About the User Interface below.
When you load a design file from a P-CAD application, the design information is displayed in the
appropriate viewing area. The Parametric Constraint Solver workspace views include:
• The Constraint Editor View
• The Design Manager View
Designs loaded from P-CAD PCB, Relay or Schematic provide the design information as it pertains
to the individual views. The Design Manager View shows the design objects in each of its pages,
while the Constraint Editor View provides access to the constraints.
Each of the Parametric Constraint Solver views is summarized in the Parametric Constraint Solver
Views section.
Menu Bar
The menu bar allows you easy access to Parametric Constraint Solver commands and functions.
Before you load a design, the PCS menu bar contains only the File and Help menu items. From the
File menu you can choose to load a PCB or Schematic design.
When you load a design from PCB or Schematic, the menu bar of PCS appears as follows:
To activate a menu, click the menu title or press the Alt key in combination with the underlined
letter of the menu title (e.g., Alt+F to open the File menu). When the menu appears, click a menu
item, or press the underlined key, to enable a command.
• A command followed by three dots (e.g., Open...) opens a dialog when you choose it.
• The menu bar wraps if you reduce the width of the window. In contrast, other areas of the
screen truncate with screen reduction.
Command Toolbar
The Command Toolbar provides shortcuts to menu commands and other system functions.
The Command Toolbar attached to the Parametric Constraint Solver contains only one shortcut
command and appears as follows:
Update PCB/Schematic
For more information about using the Design Manager, refer to The Design Manager View, (page
15).
The Constraint Editor spreadsheet provides the ability to establish constraint values using simple or
complex methods. Formulas can be as simple as a mathematical operation or as complex as
referencing other constraint values to define relationships between constraints.
For more information about using the Constraint Editor, refer to The Constraint Editor View, (page
31).
Loading a Design
To load a design into the P-CAD Parametric Constraint Solver, the design must first be opened in P-
CAD PCB, P-CAD Relay, or P-CAD Schematic.
Once the design is open and active in the originating P-CAD application, choose the Utils » P-CAD
Design Constraint Manager command to launch the Parametric Constraint Solver. You can also
launch PCS from your desktop.
The Design Constraint Manager command in the PCB and Schematic Utils menus provides access
to both PCS and P-CAD InterPlace. P-CAD searches your license files and, depending on which
license(s) are found, launches the appropriate application(s).
From the Parametric Constraint Solver File menu choose the Load PCB Design or the Load
Schematic Design command to begin the design loading process.
The design is loaded automatically and the Parametric Constraint Solver workspace displays the
Design Manager and Constraint Editor Views.
While a design is loaded, the originating P-CAD application is locked so that conflicting changes to
the design or the design constraints cannot be made. Refer to P-CAD Application Lock for details.
Cancel terminates the DBX (P-CAD Database Exchange programmer's interface) connection
between the applications. If this connection is broken any changes made in PCS are not saved to
the design file.
Design information is communicated between the originating application and the Parametric
Constraint Solver via DBX. If you wish to update the design with changes made in the Parametric
Constraint Solver, do not click Cancel. To update the design, use either the File » Update PCB or
File » Update Schematic command to save the changes to the original design. Then, close the
design or exit the Parametric Constraint Solver.
See Working with the Constraint Editor View, (page 41), for more information on maintaining the
update link between PCS and the originating application.
When you exit PCS and return to the originating application, make sure you do a File » Save in PCB
or Schematic to apply the PCS updates to the design. Updates made in PCS are saved in the
memory of the originating application only until you choose the File Save command or confirm that
you want the updates saved on exiting the originating application.
The P-CAD Parametric Constraint Solver provides the Design Manager View to help in organizing
the design components into logical partitions and physical regions called rooms. The Design
Manager View also gives access to information about the nets, net classes and class-to-classes in
your design in an easy-to-use interface.
In this chapter, each method of organizing components, nets and net classes is discussed, as well as
how you can use them to expedite the design and production of an efficient and cost effective
circuit board. You will also learn how organizing design objects can facilitate the assignment of
constraints.
Before a design is loaded, the Design Manager View is empty. Once a design is loaded using the
File » Load PCB or Schematic Design commands, the Design Manager View displays the design data
in the relevant pages.
You can choose to view or hide the Design Manager View using the View Design Manager
command. The view can also be resized and rearranged in the workspace. See Parametric
Constraint Solver Basics, (page 7), for details on changing the way the workspace is organized.
The Design Manager View is displayed in the right half of the Parametric Constraint Solver
workspace when PCS is launched for the first time, as shown below:
Components Page
Nets Page
Partitions Page
Class-to-Class Page
On each page, except the Components Page, is a tree structure or hierarchy, containing all of the
information pertinent to that page. You can view the page’s contents at various levels of detail by
expanding or collapsing the branches of the tree.
Groupings containing collapsed levels are shown with a sign. To expand the grouping, simply
click the . Expanded groupings are shown with a sign. To collapse the grouping, simply click
the sign. You can also use the and keys on a selected group to collapse or expand
groupings, respectively.
Component Information
For each component in the design, the following information is displayed:
• Reference Designator or component identifier.
• Type of component.
• Value assigned to the component.
• Placed indicates whether the component is or isn’t located within the board outline.
• Partition displays the name of the partition the component is assigned to, if any.
Net Information
The Nets page displays a list of the nets resident in the loaded design. Nodes associated with each
net are listed for designs loaded from PCB.
A Schematic design loaded into Parametric Constraint Solver displays only the list of nets in the
design.
Partition names can be used to describe the way the components are organized for easy
identification. For instance, you may have a partition containing the analog components and name
it AnalogPart, or for components located on a Schematic Sheet number one you can create a
partition called Sheet1Part.
The Partitions Page is displayed in the workspace as follows:
Organizing Components, (page 25), has more information on using partitions to help organize
designs.
Rooms must be placed on the board in PCB before the design is loaded into the Parametric
Constraint Solver. A Room cannot be created in the Parametric Constraint Solver. See your PCB
User’s Guide for instructions on creating rooms.
Refer to Organizing Components, (page 25), for more information on the use of Rooms.
Class-to-Class Information
The Class-to-Class page of the Design Manager View groups the design’s net classes in the list of
Available Net Classes and does not display them until you click the button.
The Class-to-Class Page appears as follows:
Creating a Class-to-Class
A new Class-to-Class is created by selecting one or two net classes and then choosing the New
Class-to-Class command from the right mouse menu.
To Create a Class-to-Class
1. Expand the Available Net Classes folder, if it is not expanded, to display the available net
classes, by clicking the button or pressing the key.
2. Select one or two of the Net Classes in the list of available net classes. The new Class-to-Class
name is the name of the first net class, followed by a space, then the name of the second net
class appended to it. If you only select one net class, the new Class-to-Class name is the net
class name repeated.
Deleting a Class-to-Class
You can delete any Class-to-Class you have created.
To Delete A Class-to-Class
1. Select an existing class-to-class.
2. From the right mouse menu, choose Delete or press the Delete key.
C N P R NC CC Command
Organizing Components
Whether you are working on a PCB or a Schematic design, the P-CAD Parametric Constraint Solver
will help you organize the many objects in your design. The Parametric Constraint Solver
specializes in two of the basic areas of board design: object organization and constraint
assignment. A well organized board is essential to minimizing constraint violations resulting in
more efficiently designed and manufactured circuit boards.
The Design Manager View in the Parametric Constraint Solver provides easy access to information
on the components and nets in your design. In the Design Manager View you can define logical
blocks or partitions and assign components to them. For a PCB design, you can even group
components into a room, providing an additional organizational tool to help place them in a
specific physical location on the board.
This chapter explains in detail how to use the organizational tools in the Partitions and Rooms
pages for your PCB or Schematic design objects. The other pages of the Design Manager View are
described in The Design Manager View (page 15).
Once the design objects are organized, you will be better prepared to assign constraints to
individual objects or the groups of objects you have created.
When you first enter the Partitions page of the Design Manager View, and no partitions have been
created, the components are grouped in the Unpartitioned Components list and are not visible.
Click the button next to Unpartitioned Components to display the list of components.
The Partitions Page is shown below:
Creating Partitions
Components in a design with no partitions are, by default, unpartitioned. A new partition is
created using the New Partition command in the right mouse menu. The partition name can be
changed at any time.
To Create a Partition
1. Select the Unpartitioned Components folder or an existing partition.
2. Choose the New Partition command from the right mouse menu. The partition is given a
default name of PartitionX, where X is a number incremented with each added partition.
Deleting Partitions
Any partition you create can be deleted. If a deleted partition has components assigned to it, those
components are placed back into the Unpartitioned Components list and the associated Partition
name is deleted from the Components Page.
To Delete A Partition
1. Select an existing partition.
2. From the right mouse menu, choose Delete or press the Delete key. If the partition has
assigned components, the components are placed back in the Unpartitioned Components list
and the partition is deleted.
Renaming Partitions
The partition can be renamed at any time. Partition name changes are also reflected in the Partition
column of the Components Page.
To Rename a Partition
1. Select an existing partition.
2. From the right mouse menu choose the Rename command. You may also double click on the
partition name to put the field in edit mode.
3. Enter the new partition name and press Enter.
Components can be assigned to more than one Room, therefore, the list of Available Components
does not change even after a component has been assigned to a room. All components remain
available for room assignment at all times.
In addition to the Available Components folder, there is a Top, Bottom and Top or Bottom
folder. Existing Rooms are displayed in their appropriate folder, depending on the layer placement.
The Rooms Page appears as follows:
Creating a Room
Physically drawing the boundaries of a room must be completed in PCB before the design is loaded
into Parametric Constraint Solver. The location of the room, Top, Bottom or Top or Bottom, is
determined at the time the room is placed in the design. See your PCB User’s Guide for more
information on placing a room.
Design constraints are an integral part of P-CAD PCS. The Parametric Constraint Solver provides an
easy-to-use interface in which you can organize, prioritize and define constraints or design rules.
In one convenient location you can access all the constraints for a design and easily manipulate
those constraints to satisfy your design requirements. You can even define constraint formulas,
which are based on other constraints values.
Design constraints and any constraint expressions are automatically loaded from an open design in
P-CAD PCB or Schematic to the Parametric Constraint Solver. The constraints are consolidated in
the Constraint Editor where you can view, add, copy, modify, or remove constraint definitions.
Constraints defined or modified in PCS can be saved back to the original PCB or Schematic design.
This chapter summarizes the constraint management power of the Constraint Editor. You will learn
what a constraint is and how constraints are applied to printed circuit board and Schematic
designs. The Constraint Editor’s functions are detailed along with instructions on building formulas
based on other constraints.
What is a Constraint?
A design constraint may be more familiar to you from P-CAD PCB or P-CAD Schematic as a design
rule or attribute. Rules or attributes specify requirements that must be met to successfully design,
route and manufacture a printed circuit board.
For example, with PCS you can assign components to a physical, predefined area of the board
called a room, and then, using the Constraint Editor View, apply a maximum height constraint to all
the components located in that area.
In the above example, PCB Design Rules Checking can automatically verify that components placed
in a room satisfy design rules or constraints.
The Constraint Editor View may be enabled or disabled using the View » Constraint Editor
command. When visible, the view can be disabled by clicking the appropriate button at the top
right corner. The Constraint Editor can also be resized by positioning the cursor on the edge of the
line you want to move, then dragging it to the right or left and releasing the button at the desired
location. Additionally, if you double-click on the gray lines at the left of the view, the view is
undocked and floats in the middle of your display. You can then use your mouse to drag it to a
new position.
The windows can be rearranged and, along with the columns, resized. PCS stores the visibility,
position and size of the Constraint Editor View from your last session in the .ini file and
reconstructs those settings in the workspace for the new session.
Within each constraint category in the Precedence View tree are constraint items. For example, the
Layer category will have the item Top, which contains all of the constraints defined for the Top
layer of the design. When a category has a large number of items, such as a Net or a Component,
the items in the category are divided into two lists. The first list displays the items that have
constraints, while the remaining items are grouped into the No Constraints folder.
Constraint Categories
There are seven constraint categories organized hierarchically, whose order precedence is applied
to the design. For example, a Design Width constraint can be overridden for a particular net by
specifying a Net Width constraint.
The constraint categories of PCS are listed, and displayed in the Constraint Editor View, in their
precedence order as shown below:
• Design: Design constraints are constraints that apply to any object when no other constraint
has been set.
• Layer: Layer constraints are constraints that apply to any object on a particular layer.
• Net Class: Net Class constraints apply to all nets that have been assigned to the specified net
class.
• Net: Net constraints apply to a specific net.
• Class-to-Class: Class-to-Class constraints specify constraints between two net classes.
• Room: Room constraints apply to the components included in a room. Note that the
Placement Side Attribute on the Rooms dialog in PCB is used for Design Rules Checking. If the
attribute is added in PCS, it will not override the value on the dialog.
• Component: Component constraints apply to a specific component.
Constraint categories are used when evaluating and enforcing design rules.
Certain constraints assigned to items in the Layer category are predefined in the PCB design and
they cannot be deleted. Those constraints are: PadToPad, PadToLine, PadToVia, LineToVia,
LineToLine and ViaToVia. The display units for these predefined constraints are fixed and cannot
be changed, but the constraint values can be modified.
Add Constraint: This command is used to add a constraint to the selected item(s) and can be
accessed from both the Precedence View and the Constraint View.
Remove Constraints: This command is used to remove all constraints from the selected item(s) in
the Precedence View or individually selected constraints in the Constraint View.
The Constraint View displays the constraints within the selected item and includes the information
in these columns:
• Name: This is the name of the constraint or attribute, for example, LineToLineClearance or
PadToLineClearance.
• Value: The value assigned to the constraint. The value displayed here can be entered directly
into the field, or will automatically appear based on the evaluation of an expression in the
Expression field.
• Unit: The unit is the method of presentation for the quantity entered in the Expression field.
For instance, a width measurement can be presented as a unit of inch, millimeter, mil, etc. The
unit is assigned when the constraint is added.
If you add a user-defined constraint and do not choose a unit, you will be required to enter the
unit along with the value each time you change the constraint’s value. For instance, if you have
a constraint whose value should always be mil, by assigning that unit to the constraint you
need not enter “mil” each time the numeric measurement changes, you will only need to enter
the appropriate figure.
• Expression: This field displays a formula, which can use numeric values, expressions,
functions, or other constraint values to mathematically calculate the value applied to a
constraint.
• Comment: Notes about the constraint.
The columns in the Constraint View can be resized by clicking the left mouse button on the
dividing line and dragging it to the right or left, then releasing the button at the desired location.
For more information about constraint types, see Constraint Data Types below. Additional
information on building expressions can be found in Evaluating Expressions, (page 44).
• String: A constraint of type String includes a series of alphanumeric characters. For example,
the constraint PartNumber may have the String value 76-8BEH98-42.
• Layer: A constraint of type Layer indicates the layer on which the constraint applies (e.g., Top,
Bottom, etc.).
• ViaStyle: The ViaStyle type is specific to the ViaStyle constraint. It indicates the style of the via
for a particular design, net class or net.
Constraint types described as having a base unit all provide additional units of milli-, micro-, nano-,
and pico- in addition to the base unit. The one exception is the Frequency type where the
additional units are kilo- and mega- hertz.
Constraint types are particularly important when defining a constraint expression based on other
constraints. See Evaluating Expressions, (page 44), for more information
Expression Syntax
When building an expression to determine a constraint’s value, the syntax, or structure, of the
expression must follow the format supported by the Constraint Editor. PCS grammar defines
where spaces, quotes, brackets, periods and other special characters are allowed and the format
required to successfully utilize expressions and operators in your formulas.
In its simplest form, using the expression field, you can derive the constraint value from a sequence
of numbers, constraint, vector or an expression where an expression is a combination of
constraints, operators and integers.
A very simple example is the one shown below which defines a RiseTime constraint by using a
numeric value (number) in the Expression field.
The next example uses an expression referencing the RiseTime constraint shown above to compute
the MaxNetLength.
Moving on to a sample expression that is a bit more complicated, the next example uses two other
constraints and a trigonometric function in its expression to determine the ComponentSpacing
value. Note that one of the referenced constraints, ComponentHeight, resides in the same
precedence level while the InspectionAngle constraint comes from the Design level.
In the last example, an expression is used to produce the value of the Capacitance constraint.
This expression includes the Diel_Const, BoardThickness, Cu_width and cu_thickness constraints
and incorporates their values into a formula to determine capacitance. Whenever the value of any
of the referenced constraints changes, the value of the capacitance constraint is re-evaluated and
changed automatically.
For more information on expressions, see Working With Constraints, (page 41). Additional
information on valid units, data types, function, operators and other PCS definitions and grammar
can be found in Appendix B, PCS References, (page 69).
Knowing how to organize and assign constraints to the various objects in your design is just the
beginning of putting the power of the Parametric Constraint Solver to work for you. Building an
expression to represent a constraint value is an advanced, intelligent way to produce the desired
value when one constraint’s change affects others down the line.
In this chapter you will learn how to add the constraints you need to the items in the precedence
levels of the design. You will also put the Constraint View to use in providing the proper values in
the constraints used in your design.
There is also a section, which explains how the updates you make in the Parametric Constraint
Solver affect the design file in PCB and Schematic.
For constraints requiring a data type of Length, use units of mil, mm, cm or inch in order to
correspond with the units used in a PCB design.
If the constraint being added is user-defined, the unit can be chosen from the complete list of
allowable units. If you do not specify a unit for a user-defined constraint, PCS makes the unit
Unitless.
Adding Constraints
A new constraint may be added to one or more selected items in the Precedence View using the
Add Constraint command in the right mouse menu. For instance, in a PCB design with a room, you
can organize the components that reside in the room in the Design Manager View’s Rooms Page,
and then add constraints to that entire group of components in the Precedence View.
A unit is assigned to every predefined constraint in the design. Constraints that are automatically
assigned to the design (such as the clearance constraints in the Layer level) are given the unit
chosen as your default in the Options Configure dialog of the originating application.
When you choose the Add Constraint command, the Add Constraint dialog appears as follows:
For each constraint category, you can select the constraint and its unit. Units are unique to the type
of constraint chosen. For example, when adding a clearance type constraint the unit selection is
Length, while for a component rotation constraint type the unit is Angular.
Removing Constraints
Any selected constraint that you have added to the design can be removed by using the Remove
Constraints command in the right mouse menu.
The predefined Layer constraints: PadToPad, PadToLine, PadToVia, LineToVia, LineToLine and
ViaToVia cannot be removed.
If you have selected one or more items in the Precedence View, and then choose the Remove
Constraints command, all the constraints for that item are removed.
In the Constraint View, only the constraints attached to the selected items are removed with the
Remove Constraints command.
Constraint Reports
The PCS provides reports that sort your design constraints in a variety of ways: by constraint
domain, precedence level, net class, class-to-class and partitions.
File Commands, (page 57), has instructions on producing the reports, along with an explanation of
the information each contains.
Evaluating Expressions
With the Constraint Editor you can define a constraint’s value in a number of ways:
• By entering a value in the Value field.
• By entering a value in the Expression field.
• By entering a formula in the Expression field that uses constant values, functions or references
to other constraints’ values. For example, you can assign a single clearance constraint at the
design level. Then, a constraint added to a different precedence level (e.g., a single
component) can reference the design level constraint in the expression field. Whenever the
design level constraint’s value is changed, the component’s constraint is evaluated and reflects
the resulting value.
The Constraint Editor checks each constraint’s expression for proper syntax and correct usage of
assigned units. It also converts units and displays error messages where necessary.
A correctly assigned data type is important when the Constraint Editor is evaluating expressions
and converting units to produce a constraint value. You cannot mix data types in an expression.
For instance, if your expression is a simple addition of a data type of Length, both sides of the
operand must be numeric and contain one of the measurements in the data type such as mil and
inch (e.g., 10mil + 0.5in). PCS displays an error if, for instance, you attempt to add a Length data
type and a Resistance data type.
The complete list of data types, the units supported in each, and their unit conversions can be
found in Appendix B, PCS References, (page 69).
Unit Conversions
When there is a difference between the assigned unit and a unit resulting from an expression, the
Constraint Editor attempts to convert the expression’s resulting unit to an equivalent value in the
assigned unit. For example, you may have a clearance constraint whose assigned unit is inch. If
you type a value of 2mm in the expression field and press Enter, the value field displays the
equivalent measurement of 0.0787402inch.
Appendix B, PCS References, (page 69), contains a table of unit conversions provided in the
Constraint Editor.
Unitless Expressions
You can assign a unit of Unitless to a user-defined constraint. With a Unitless constraint it is
possible to allocate a simple number without a unit in the value field, and it will not be subject to a
conversion.
Expression Errors
PCS checks expression formulas for correct application of functions, operators, units and
constraint references. When the Constraint Editor evaluates an expression and encounters an
illegal situation, an error message appears in the Value field.
The errors you may encounter include:
• Syntax Error.
• Divide by Zero.
• Operands type mismatch.
• <Operator> units mismatch
• Function <function> math error.
• Not a number.
• Unknown identifier <name>.
• Undefined identifier <name>.
• Array index <index> out of bounds.
The complete description of each of the PCS error messages can be found in Appendix B, PCS
References, (page 69), along with examples and possible solutions.
The message at the top of the dialog includes the name of the design constraint in conflict, in
this case the Design Level Clearance constraint. The following information is displayed as well:
• Formula: This is the expression defined for the constraint.
• Formula Result: This is the result of the expression (i.e., Value field entry) in the
Constraint Editor.
• Current Value: This is the value currently assigned to the constraint in PCB.
Based on the information supplied in the Constraint Mismatch dialog, you may choose one
of the following actions:
• Change the current value to the formula result: This option changes the value of the
constraint in PCB to match the value of the evaluated constraint in PCS.
• Change the formula to the current value. This option assigns the value of the constraint in
PCB to the expression and value in the PCS constraint, and drops the original expression.
4. Once you have chosen the desired change option, you can apply that option to all of the
detected mismatches by enabling the Apply to all box. If this option is not checked, a
Constraint Mismatch dialog is presented for each error and you can choose an individual,
appropriate action for each mismatch.
When you exit PCS and return to the originating application, make sure you do a File » Save in PCB
or Schematic to apply the PCS updates to the design. Updates made in PCS are saved in the
memory of the originating application only until you choose the File » Save command or confirm
that you want the updates saved on exiting the originating application.
Design update options are described in Parametric Constraint Solver Basics, (page 7).
Make sure to turn on the ECO recorder before launching PCS and loading the design.
If you should forget to turn on the ECO recorder, you can still record the changes by following
these steps:
1. Return to the originating application.
2. Terminate the link between the applications by Cancel button on the P-CAD DBX dialog,
shown below:
3. Turn on the ECO recorder using the Utils » Record ECOs command or by clicking the
button.
4. Return to PCS and update the design using the File » Update PCB/Schematic Design
command.
5. The error message dialog informs you that the connection has been terminated. Click the OK
button to continue.
6. In the next DBX Error dialog you must choose whether to re-establish the connection and
continue the update process or cancel it.
7. If you wish to continue the update, click the OK button. P-CAD DBX is automatically re-
activated and the link between the applications re-established. The changes saved to the file
in PCS are also saved to the ECO recorder and can then be exported to PCB or Schematic.
If you chose either the File » Close or File » Exit commands in step 4, and you click the Cancel
button in the DBX Error dialog, your design is erased from the PCS workspace and the changes you
made are not recorded in the design file.
Accessing a DTP
To access a Design Technology Parameters file, choose the File » Design Technology Parameters
command. The Design Technology Parameters dialog, shown on the next page, appears:
DTP Operations
The following list shows which operations are available in PCS from the Design Technology
Parameters dialog:
• Update From Design
• Copy To Design
• Properties
• New Section or Item
• Rename
• Delete
• Statistics
For each of the categories in the file, a particular set of operations is allowed. In all cases, you can
Update From Design and Copy To Design, as well as Delete items in each category. In addition to
those basic functions, the following additional operations are available in each of the categories:
• Class-to-Class Rules: In this category you can add a New Section or item.
• Global Rules (Layers): For the entire category you can add a New Section or item. For an
individual layer in this category you can access the Properties and Statistics, as well as Rename
an item.
• Net Class Definitions: In this category a New Section or item can be added.
• Net Class Rules: In this category a New Section or item can be added.
• Net Rules: A New Section or item can be added to the category. The Properties and Statistics
are accessible for individual nets, which can also be Renamed.
The Attribute Handling On Copy section of the Design Technology Parameters dialog is enabled for
the Copy to Design function for selected Class-to-Class Rules, Net Class Rules, Net Rules or
individual nets. You may choose to Merge Attributes in the design with those in the DTP file, or
Replace Design Attributes with those in the DTP file by clicking the appropriate radio button.
Refer to the File Commands chapter of the PCB User’s Guide for more information on how the
Merge Attributes function behaves in each of the relevant categories.
The P-CAD Parametric Constraint Solver permits you to attach comments to the constraints in your
design and assign expressions to determine constraint values. PCB and Schematic do not display
the comments or expressions, but they are easily accessible in the Parametric Constraint Solver
Reports. For more information on reports, see File Commands, (page 57).
While you can use the P-CAD Parametric Constraint Solver as a stand alone application, its power is
dramatically increased when the P-CAD InterPlace (IPL) application is running along side it. In
addition to being able to organize the design objects and constraints in PCS, you can use the
placement features in IPL to increase the effectiveness of the design.
The Layout View in P-CAD InterPlace provides the graphic representation of the circuit board for a
PCB design. Manipulation of the design objects, including controlling design layers, using rooms,
moving components, and viewing connections are just a small part of the productivity enhancing
tools that are available with InterPlace. InterPlace also provides a Visible Placement Area tool
which shows an area on the board, based on constraints, where a component can be placed
without incurring errors.
If you have purchased InterPlace, refer to the InterPlace User’s Guide to learn about its basic
functionality, which includes all of the functions described in this chapter.
Highlighting Objects
The Layout View provides the means to highlight a number of objects using the right mouse
commands from the Parametric Constraint Solver’s Precedence View.
When net connections are visible, you can highlight individual nets, the nets assigned to a net class
or class-to-class, or the nets attached to selected components. You can also highlight a room and
its components, when a room exists in the design.
Highlighting options are described in the following sections.
Net Highlighting
There are several methods you can use to highlight the nets in your design. Each highlighting
method is described below:
You must enable the visibility of the net connections before they can be highlighted. See The
Layout View in the InterPlace User’s Guide for more information on showing net connections.
To highlight a single net: Select a net item in the Net category of the precedence tree. Choose the
Highlight command in the right mouse menu.
To highlight the nets in a net class: Select the desired net class in the net class category of the
precedence tree. Choose the Highlight command in the right mouse menu.
To highlight the nets attached to components: Select the desired components from the
Component category list in the precedence tree. Choose the Highlight Attached Nets command in
the right mouse menu.
To highlight the net classes in a class-to-class: Select the desired class-to-class from the Class-to-
Class category in the precedence tree. Choose the Highlight command in the right mouse menu.
To highlight a group of nets: Select the desired Nets, Net Class or Class-to-Class items in their
respective pages and choose Highlight from the right mouse menu. For instance, in the Net Class
page you can select the Net Class instead of having to select the nets in the Net Class and then
highlight them.
To remove highlights: To remove highlighting from any highlighted object, select the object and
from the right mouse menu choose the appropriate Unhighlight command.
Room Highlighting
When rooms exist in a PCB design, and components have been assigned to and placed in them,
you can highlight the room and its components.
To highlight rooms and assigned components: Select the desired room(s) in the Rooms Page of the
Design Manager View and choose the Highlight Room and Assigned Components command from
the right mouse menu.
To remove highlights: To remove highlighting from any highlighted object, select the object and
from the right mouse menu choose the appropriate Unhighlight command.
Component Highlighting
Components and their attached nets can be highlighted in the Layout View from the Parametric
Constraint Solver’s Precedence View.
To highlight one or more components: Select the desired components in the PCS Precedence
View component category. From the right mouse menu choose the Highlight Component
command.
To highlight the nets attached to a component: First make sure that the display of the net
connections is enabled, then select the desired components in the PCS Precedence View
component category. From the right mouse menu, choose the Highlight Attached Nets command.
To remove highlights: To remove highlighting from any highlighted object, select the object and
from the right mouse menu choose the appropriate Unhighlight command.
Component Selection
In addition to being able to highlight components and nets, the components in the design can be
selected from the Precedence View in PCS. Once selected, you can perform any of the functions
available to selected objects such as moving, fixing, rotating, clustering, etc. All of these functions
are explained in detail in The Layout View, in your InterPlace User’s Guide.
To place component(s) in select mode: Select the desired component(s) from the list of
components in the Precedence View tree and choose the Select Component command from the
right mouse menu.
To place components in a net in select mode: Select the desired net from the list of Nets in the
Precedence View tree and choose the Select Net Components command from the right mouse
menu.
Clustering Components
Locating one or more specific components in a design with a large quantity of components can be
almost effortless when you use the Cluster By command. The Cluster tool finds designated
components and lets you place them in a chosen location arranged by the property of your choice,
such as type, pin count, package size, etc. Once clustered they can easily be placed on the board.
The Cluster By command is available on every menu in the Layout View and the Design Manager
View. In addition, the Cluster By command appears in the right mouse menu of the PCS
Precedence View when one or more items in the Net, Net Class, Room or Component categories
are selected.
The InterPlace User’s Guide provides detailed information on how to use the clustering tool in
Organizing and Placing Components.
File Commands
The File commands allow you to load, close, and update designs with their
design constraints into P-CAD Parametric Constraint Solver. From the File
menu, you can also exit the application.
The File menu displayed in the margin, containing the File » Load PCB Design
and File » Load Schematic Design commands, is available when a design is yet
to be loaded. An expanded File menu is available once the PCB or Schematic design has been
loaded into the Parametric Constraint Solver. See the following pages for details.
File Close
Closes all views for the design in the Parametric Constraint Solver. The design is unlocked in the
originating application, permitting changes again in the PCB or Schematic design editor.
If the design has been changed but not yet saved, you are asked whether or not you want to save
your changes before closing.
File Reports
Allows you to generate reports with specific output options. The selected Style Format dictates the
options available for each of the styles: Comma Separated and Report. With the Report style, in
addition to the Report Options, Lines per Page and Report Destination, you may select the page
format and define the Header and Footer. These options are saved when you exit the program.
Filename
You may specify the report or reports you wish to generate from the list of report types listed in the
Report Options area. Each report type has its own, unique file extension; the filename defaults to
the name of the current design.
Report Options
The reports are described below:
Constraint Domain: The Constraint Domain report lists the three domains pertinent to placement
constraint management: Physical, Electrical, and Room. Within each domain, in their precedence
order, are each item’s constraint names, values, expressions and comments.
Precedence Level: The Precedence Level report shows, for each precedence level and item, the
constraint names, values, expressions and comments.
Net Class: The Net Class report shows the nets that are assigned to each net class in the design.
Class-to-Class: The Class-to-Class report shows the net classes assigned to each class-to-class and
the class-to-class constraints.
Partitions: The Partitions report lists the components assigned to each Partition.
Page Format
These Page Format options are enabled when the Report format is selected:
• Use Header and Use Footer include the information you specified in the header and footer
dialog fields.
• Date/Page includes the current date and the page number.
• Pagination allows you to create your own pagination (lines per page). When this option is
enabled print from the DOS Print command, not the Notepad.
Style Format
Comma Separated puts all data in comma-separated format. This format can be imported into
other spreadsheet and database programs.
Report produces a report format with columns and spaces, etc.
Report Destination
Screen sends the output to a file and opens the file using the Notepad Utility.
File sends the output to a file.
Printer sends output directly to the printer without creating files.
Generate
Generates all selected reports using the options selected.
Design constraints, or rules, can be transferred using a design technology parameter file between
the Parametric Constraint Solver and any PCB or Schematic design.
In the P-CAD Parametric Constraint Solver, Design Technology Parameters can be used in a variety
of ways, including:
• Applying company-standard design rules to your board layout.
• Storing design rules created or organized in Parametric Constraint Solver for later use in other
PCB or Schematic designs. You can create or change design rules pertaining to Class-to-Class
Rules, Layer Rules, Net Class Definitions, Net Class Rules and Net Rules in Parametric
Constraint Solver.
For more information, see Using a Design Technology Parameters File, (page 49).
File Exit
Exits the Parametric Constraint Solver program.
If the design has been modified since the last save, you are prompted whether you want to save the
changes.
The design file is unlocked in the originating application, permitting changes again in the PCB or
Schematic design editor.
The program writes information to the .ini file when you choose Exit. This information, which
will apply to subsequent PCS sessions, consists of parameters and settings such as values set in
Options Configure, etc.
View Commands
View commands allow you to temporarily alter your view of the workspace.
You can enable or disable the display of the Design Manager View or the
Constraint Editor View.
The View menu of Parametric Constraint Solver, for a design loaded from
either PCB or Schematic, is shown in the left margin.
Help Commands
Keyboard Reference
This chapter is a reference of commands and functions accessed through P-CAD shortcut keys and
standard Windows accelerators.
Standard Windows key combinations are functional for all of the menu commands; use the normal
combination Alt,x,y, where x equals the underlined menu character, and y equals the underlined
command character.
The Parametric Constraint Solver Keyboard Reference section includes general keystrokes and
those specific to P-CAD Parametric Constraint Solver.
Alt+F4 (File Exit) Shortcut for File Exit, which exits the P-CAD program. If the
current design has been modified since the last save, you will be
prompted (YES or NO) as to whether you want to save the
changes to the file. The program will write information to the
.ini file when you exit.
arrow keys A directional arrow key moves the cursor in the Constraint Editor
to the constraint above or below, or to the field to the left or
right of the starting position. In the Design Manager View only
the up and down arrows are operational.
Ctrl+S (File Update PCB) Saves changes to the current design without closing it.
F1 (Help) Displays context-sensitive help. If you put focus on a command
or dialog and press F1, the Help window appears containing
information specific to the focus item.
Shift + End Selects all items in a list on the Design Manager pages from the
first one selected to the end of the list.
PCS References
This appendix contains references pertaining to the Parametric Constraint Solver field entries,
primarily the Expression field.
Included are tables:
• Grammar
• Data Types
• Postfix mode
• Functions
• Operators
• Units
• Constants
• Constraint Referencing
• Sample formulas
• Error Messages
• Limitations.
The Constraint Editor View, (page 31), provides detailed information on how these references are
utilized in the Constraint View.
PCS Grammar
The Parametric Constraint Solver understands specific use of variables, operators, special
characters and phrases when evaluating an expression. The notations shown below will help you
understand the PCS grammatical rules.
Notations
The following notations are used to describe the PCS grammar.
Notations Definition
Grammar
The following table shows the list of allowable syntax usage. Any entry in the second column can
be used.
Term Allowable syntax
expression expr
booleanExpr
vector
expr ‘postfix’ exprpf
‘-‘ expr
expr ‘+’ expr
expr ‘*’ expr
expr ‘/’ expr
expr ‘%’ expr
expr ‘!’
‘(‘ expr ‘)’
number
constraint
constraint ‘[‘ expr ‘]’
‘size’ ‘(‘ constraint ‘)’
‘if’ booleanExpr ‘then’ expr
‘else’ expr
‘abs’ ‘(‘ expr ‘)’
‘acos’ ‘(‘ expr ‘)’
‘asin’ ‘(‘ expr ‘)’
‘atan’ ‘(‘ expr ‘)’
‘cos’ ‘(‘ expr ‘)’
‘cosh’ ‘(‘ expr ‘)’
‘exp’ ‘(‘ expr ‘)’
‘int’ ‘(‘ expr ‘)’
‘in’ ‘(‘ expr ‘)’
‘log’ ‘(‘ expr ‘)’
‘max’ ‘(‘ expr[,expr]* ‘)’
‘min’ ‘(‘ expr[,expr]* ‘)’
‘sin’ ‘(‘ expr ‘)’
‘sinh’ ‘(‘ expr ‘)’
‘sqrt’ ‘(‘ expr ‘)’
‘sum’ ‘(‘ xpr[,expr]* ‘)’
‘tan’ ‘(‘ expr ‘)’
‘tanh’ ‘(‘ expr ‘)’
booleanExpr ‘yes’ | ‘no’ | ‘true’ | ‘false’
expr ‘and’ expr
expr ‘or’ expr
‘not’ expr
booleanExpr ‘and’
booleanExpr
booleanExpr ‘or’
booleanExpr
‘not’ booleanExpr
‘(‘ booleanExpr ‘)’
expr ‘<’ expr
expr ‘>’ expr
expr ‘<=’ expr
expr ‘>=’ expr
expr ‘=’ expr
expr ‘=’ booleanExpr
expr ‘!=’ expr
expr ‘!=’ booleanExpr
constraint name
precedenceMember ‘.’ name
precedenceMember ‘Design’
precedenceLevel ‘{‘ member
‘}’
precedenceLevel ‘Layer’
‘Net’
‘NetClass’
‘Room’
‘Component’
‘ClassToClass’
member name
vector [–] ?number[,[–]number]+
exprfp number
constraint
exprpf exprpf ‘+’
exprpf exprpf ‘–’
exprpf exprpf ‘*’
exprpf exprpf ‘/’
exprpf exprpf ‘%’
Data Types
The following data types are supported as a field entry or when used in an expression:
Type Definition
AutoRouteWide Boolean
BoardEdgeClearance Length
Clearance Length
ComponentHeight Length
ComponentRotation Angular
ComponentSpacing Length
Description String
HoleToHoleClearance Length
InsertionGripLength Length
InsertionGripWidth Length
InspectionAngle Angular
LineToLineClearance Length
Postfix Mode
The keyword postfix starts a postfix expression. The postfix expression stack runs left to right (e.g.,
“postfix 2 3 + 5 /” is the same as “(2 + 3) / 5”. A negative number must be noted using the reserved
keyword neg. Do not use the minus sign. In the above example, if the number 3 is negative, the
expression would read postfix 2 3neg + 5 / which is the same as “(2 + 3neg) / 5”.
Functions
The following table describes which functions are supported in the Parametric Constraint Solver,
along with the legal arguments and the expected results. Each function’s legal argument contains
an expression, which is any number, constant, function result, or known identifier. Unless
otherwise stated, and expression may include any unit.
Operators
The following table of operators are those supported in PCS. Binary means the operator takes both
a left and a right hand side. Unary means the operator only has a left hand side. Unit restrictions
list how the units on the left and right hand side must be used. Unit category is the “type” of unit,
such as length, current, time, power, etc. typically, linear combinations of units must have the same
category.
Supported Units
The following table shows the units supported in PCS along with applicable conversions.
Constants
The following are predefined constants:
Constant Unit
e Unitless
pi Unitless
True Boolean
False Boolean
Yes Boolean
No Boolean
Constraint Referencing
Referencing other constraints is done in two ways: 1) if the constraint is in the same precedence
member (e.g. a net), then use the name of the constraint (e.g., “Width”), 2) if the constraint is in
another precedence level, use one of the fully qualified constraint name formulas:
• Design.constraint-name
• Layer{layer-name}.constraint-name
• NetClass{net-class-name}.constraint-name
• Net{net-name}.constraint-name
• ClassToClass{“net-class-name net-class-name”}.constraint name
• Room{room-name}.constraint-name
• Component{component-name}.constraint-name
Spaces are optional except for ClassToClass where quotes around and a space between the net
class names are required. Constraint referencing formulas are not case sensitive.
Reserved Keywords
The following keywords are reserved and cannot be used as constraint names:
Limits
The limits supported by PCS are:
Integer (64 bit internal storage) -9223372936854775807 to +9223372036854775807
Integer (32 bit internal storage and only when the unit is quantity) 2147483647
Floating Point (IEEE standard)
Minimum value: 2.2250738585072014E – 308
Maximum value: 1.7976931348623158E + 308
Syntax Examples
The following table shows sample expressions for different types of constraints and the expected
results. Notice that, for each section of the table, there are constraint expressions based on the
values of other constraints, some at different levels of the precedence hierarchy.
For each example the targeted constraint value is displayed in bold letters. Those constraints that
are not bold are those that supply values to the target constraint’s expression.
EXAMPLE #1
In this example the value of the constraint Dist is the sum of the values of the thickness constraints
from the Top Layer and the INT1 Layer.
EXAMPLE #2
In this example the value of the constraint width in the –5v net is the value of the width constraint
in the mux1 net multiplied by 2.
EXAMPLE #3
In this example the value of the constraint width in the Top Layer is determined by using the Dist
and Cu_Height constraints in the Top Layer and the B constraint in the Design level. In addition, as
you can see, each expression references another constraint at a different level in the precedence
hierarchy.
EXAMPLE #4
In this example the value of the constraint MaxNetLength for the A80 net is determined using the
RiseTime constraint’s value from the Design level of the hierarchy.
EXAMPLE #5
In this example the value for the VDdiff constraint is obtained using various constraints from the
design level.
Constraint Precedence Level Expression Results
EXAMPLE #6
In this example, to determine the ComponentSpacing value at the component level, the
expressions use values of constraints at the design level and the component level.
Constraint Precedence Level Expression Results
Divide By 0
Cause: An attempt was made to divide by zero.
Solution: Evaluate the expression for the existence of a divisor with a value of zero.
Not a Number
Cause: An internal floating point conversion was unsuccessful or an integer was too large.
Solution: Check the expression for evaluations, which may result in an integer outside the limits.
-L- operators
reference..................................................... 77
launching organizing
PCS................................................................12 class to class ............................................... 30
layer in Components Page ................................ 26
constraints...................................................35 in Nets Page................................................ 26
Layout View in Partitions Page....................................... 26
clustering components ............................55 net classes................................................... 30
highlighting objects ..................................53 organizing objects........................................ 25
jumping to a component .........................55
selecting components ..............................55 -P-
using IPL with PCS .....................................53 partitions
limits adding components ................................. 28
floating point ..............................................81 adding new ................................................. 27
integer ..........................................................81 deleting ....................................................... 27
integer for quantity unit...........................81 in partitions page ...................................... 19
reference .....................................................81 removing components ............................ 28
Load PCB Design, File command...............57 renaming..................................................... 27
Load Schematic Design, File command ...58 report ........................................................... 60
loading P-CAD
a design........................................................12 PCB icon........................................................ 3
a PCB design ...............................................57 PCS Help Topics ........................................ 65
a Schematic design....................................58 PCB
lock icon................................................................. 3
application using PCS from ............................................ 7
terminating ..............................................48 PCS
on P-CAD applications .............................13 basics ............................................................. 7
-M- exit ................................................................ 14
features.......................................................... 1
menu bar...........................................................9 interface .................................................... 3, 8
-N- references................................................... 69
using from PCB............................................ 8
net
using from Relay.......................................... 8
adding nets..................................................22
using from Schematic ................................ 8
class constraints .........................................35
PCS features
class report..................................................59
viewing in PCB ........................................... 51
constraints...................................................35
viewing in Schematic ............................... 51
creating nets ...............................................21
PCS reference
deleting net classes ...................................23
constants..................................................... 80
deleting nets ...............................................21
constraint referencing ............................. 80
renaming nets.............................................22
data dypes................................................... 74
using net class page ..................................20
data dypes by constraint.......................... 74
using the nets page ...................................18
definitions................................................... 69
nets
expression error messages ..................... 84
removing nets.............................................22
functions ..................................................... 76
-O- grammar ...................................................... 69
opening ......................................... see loading limits............................................................. 81
highlighting -V-
components.............................................54
nets ............................................................53 validating expressions................................. 46
objects.......................................................53 value field
removing ..................................................54 modifying directly..................................... 42
rooms ........................................................54 View Commands .......................................... 63
jumping to components...........................55 Constraint Editor ....................................... 63
selecting components ..............................55 Design Manager .................................. 10, 63
unhighlighting objects .............................53 viewing
using the ECO recorder...............................48 constraint editor........................................ 32
Utils -W-
Record ECO ................................................48
WAS file .......................................................... 48