Constraint Manager User's Manual: Release PADS VX.2.7

Constraint Manager User's Manual
Release PADS VX.2.7
Document Revision 5
© 2004-2020 Mentor Graphics Corporation

All rights reserved.
This document contains information that is proprietary to Mentor Graphics Corporation. The original recipient of this
document may duplicate this document in whole or in part for internal business purposes only, provided that this entire
notice appears in all copies. In duplicating any part of this document, the recipient agrees to make every reasonable
effort to prevent the unauthorized use and distribution of the proprietary information.
Note - Viewing PDF files within a web browser causes some links not to function (see MG595892).
Use HTML for full navigation.
This document is for information and instruction purposes. Mentor Graphics reserves the right to make
changes in specifications and other information contained in this publication without prior notice, and the
reader should, in all cases, consult Mentor Graphics to determine whether any changes have been
made.
The terms and conditions governing the sale and licensing of Mentor Graphics products are set forth in
written agreements between Mentor Graphics and its customers. No representation or other affirmation
of fact contained in this publication shall be deemed to be a warranty or give rise to any liability of Mentor
Graphics whatsoever.
MENTOR GRAPHICS MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE.
MENTOR GRAPHICS SHALL NOT BE LIABLE FOR ANY INCIDENTAL, INDIRECT, SPECIAL, OR
CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING BUT NOT LIMITED TO LOST PROFITS)
ARISING OUT OF OR RELATED TO THIS PUBLICATION OR THE INFORMATION CONTAINED IN IT,
EVEN IF MENTOR GRAPHICS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
U.S. GOVERNMENT LICENSE RIGHTS: The software and documentation were developed entirely at
private expense and are commercial computer software and commercial computer software
documentation within the meaning of the applicable acquisition regulations. Accordingly, pursuant to
FAR 48 CFR 12.212 and DFARS 48 CFR 227.7202, use, duplication and disclosure by or for the U.S.
Government or a U.S. Government subcontractor is subject solely to the terms and conditions set forth in
the license agreement provided with the software, except for provisions which are contrary to applicable
mandatory federal laws.
TRADEMARKS: The trademarks, logos and service marks ("Marks") used herein are the property of
Mentor Graphics Corporation or other parties. No one is permitted to use these Marks without the prior
written consent of Mentor Graphics or the owner of the Mark, as applicable. The use herein of a third-
party Mark is not an attempt to indicate Mentor Graphics as a source of a product, but is intended to
indicate a product from, or associated with, a particular third party. A current list of Mentor Graphics’
trademarks may be viewed at: mentor.com/trademarks.
The registered trademark Linux® is used pursuant to a sublicense from LMI, the exclusive licensee of
Linus Torvalds, owner of the mark on a world-wide basis.
End-User License Agreement: You can print a copy of the End-User License Agreement from:
mentor.com/eula.
Mentor Graphics Corporation

8005 S.W. Boeckman Road, Wilsonville, Oregon 97070-7777
Telephone: 503.685.7000
Toll-Free Telephone: 800.592.2210
Website: mentor.com
Support Center: support.mentor.com
Send Feedback on Documentation: support.mentor.com/doc_feedback_form

Revision History ISO-26262
Revision Changes Status/Date

5 Modifications to title page to reflect the latest product version Released
supported. Approved by Regis Krug. March 2020
All technical enhancements, changes, and fixes listed in the
Personal Automated Design System Release Notes for this product
are reflected in this document. Approved by Mike Bare.
supported. Approved by Regis Krug. September
All technical enhancements, changes, and fixes listed in the 2019
supported. Approved by Regis Krug. March 2019
All technical enhancements, changes, and fixes listed in the
supported. Approved by Regis Krug. September
All technical enhancements, changes, and fixes listed in the 2018
Author: In-house procedures and working practices require multiple authors for documents. All
associated authors for each topic within this document are tracked within the Mentor Graphics
Technical Publication’s source. For specific topic authors, contact Mentor Graphics Technical
Publication department.
Revision History: Released documents include a revision history of up to four revisions. For
earlier revision history, refer to earlier releases of documentation on Support Center.
Constraint Manager User's Manual, PADS VX.2.7
Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
4 Constraint Manager User's Manual, PADS VX.2.7
Table of Contents
Revision History ISO-26262
Chapter 1
Getting Started Videos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Starting and Exiting From Constraint Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Cross Probing Between Design Systems and Constraint Manager . . . . . . . . . . . . . . . . . . . . 12
Viewing Clearance and Trace Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Creating Net Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Adding Nets to a Net Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Defining Differential Pairs Automatically. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Creating Clearance Rule Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Assigning Class-To-Class Clearance Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Creating Constraint Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Chapter 2
Overview and Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Constraint-Driven Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Before You Begin Using Constraint Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
PADS Designer-PADS Layout (Integrated Workflow) . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Overview of Electrical Nets and Physical Nets in Constraint Manager . . . . . . . . . . . . . . . 31
Automatically Recognized Topologies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Electrical Nets Defined Through a Package With More Than Two Pins . . . . . . . . . . . . . . 32
Starting and Exiting From Constraint Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Viewing Constraint Database Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Folder Structure and Location of Constraint Manager Log Files . . . . . . . . . . . . . . . . . . . . . 34
Cross Probing Between Design Systems and Constraint Manager . . . . . . . . . . . . . . . . . . . . 34
Constraint Manager Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Specifying Design Configuration Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Specifying Electrical Net Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Specifying Discrete Component Prefixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Setting Display Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Setting General Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Setting Fonts and Colors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Setting Spreadsheet Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Setting Unit Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Specifying Other Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Reusing Settings in External Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Display Customization of Constraint Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Toggling the Display of Windows and Toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Changing the Position of Windows and Toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Folder Location of the ces.ini Configuration File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Customizing Command Shortcut Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Constraint Manager User's Manual, PADS VX.2.7 5

Table of Contents
Default Keyboard Shortcuts Provided With Constraint Manager . . . . . . . . . . . . . . . . . . . . . 52
Chapter 3
Constraint Spreadsheet Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Constraint Definition Through Spreadsheet Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Overview of Constraint Hierarchy and Overrides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Choosing From Among Change Impact Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Required Propagation Rules That Constraint Manager Maintains . . . . . . . . . . . . . . . . . . . 58
Organization of Constraints Into Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Spreadsheet Page Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Selecting a Spreadsheet Page Using the Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Selecting a Spreadsheet Page Using the Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Displaying Only Specific Constraint Types on a Spreadsheet Page . . . . . . . . . . . . . . . . 61
Displaying All Constraint Types on a Spreadsheet Page . . . . . . . . . . . . . . . . . . . . . . . . . 61
Spreadsheet Icons Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Resizing Spreadsheet Columns and Rows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Zooming the Display of Spreadsheet Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Expanding and Collapsing Spreadsheet Rows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Sorting Spreadsheet Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Deletion of Constraint Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Deleting Constraint Values at the Constraint Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Deleting Constraint Values at the Object Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Deleting Constraint Values at the Design Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Constraint Value Copy-and-Paste Between Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Removing Unused Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Searching for Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Filtering Spreadsheet Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Filtering the Spreadsheet by Row Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Resetting a Spreadsheet to its Default View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Concurrent Constraint Entry With Other Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Overview of Constraint Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Showing Indication of Remotely Changed Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Constraint Value Commenting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Adding Comments to Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Editing Constraint Comments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Deleting Constraint Comments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Viewing Constraint Comments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Viewing Constraint Reference Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Viewing Design Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Checking Constraints Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Constraint Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Checking Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Correcting Constraint Manager Diagnostics Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Listing of Constraint Manager Diagnostics Tests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
PCB Actuals Comparison With Constraint Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Validating PCB Actuals Against Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Updating Actuals Displayed in Constraint Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Clearing Actuals From the Spreadsheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Table of Contents
Viewing All Constraint Violations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Constraint Violation Revision Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Constraint Change Undo and Redo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Rolling Back and Undoing All Constraint Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Rolling Back or Redoing Specific Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Supported Undo/Redo Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Viewing and Reverting to Parent Cell Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Saving Constraint Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Chapter 4
Net Class Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Creating Net Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Adding Nets to a Net Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Creating a Net Class From an Existing Net Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Deleting Net Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Chapter 5
Constraint Class Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Creating Constraint Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Adding Nets to a Constraint Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Creating a Constraint Class From an Existing Constraint Class . . . . . . . . . . . . . . . . . . . . . . 104
Deleting Constraint Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Chapter 6
Physical Rule Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Viewing Clearance and Trace Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Specifying General Clearance Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Specifying Trace Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Defining Via Assignments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Clearance Rule Set Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Creating Clearance Rule Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Defining Clearances for a Rule Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Defining SMD Clearance Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Defining Board Edge Clearances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Defining Copper Clearances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Assigning Class-To-Class Clearance Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Deleting Class-To-Class Clearance Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
3D Clearance Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Defining 3D Clearances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
3D Clearance Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Chapter 7
Net Constraint Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Specifying General Net Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Topology Specification for Nets and Constraint Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Topology Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Specifying Topology Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Changing Topology Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Table of Contents
Defining Discrete Component Pin Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Length Rule Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Specifying Length Rules for Nets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Tolerance Routing of Nets Within a Constraint Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Specifying Maximum Length as a Percentage Above Manhattan Length . . . . . . . . . . . . . 132
Matching Length Rules Among Nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Matching Length Tolerance at the Constraint Class Level. . . . . . . . . . . . . . . . . . . . . . . . . 134
Power-Supply Net and Constraint Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Net Names Constraint Manager Automatically Recognizes as Power-Supply Nets . . . . . 135
Specifying Power-Supply Nets Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Specifying Power-Supply Nets Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Defining Constraints for Power-Supply Nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Changing Power-Supply Nets Back Into Nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Chapter 8
Differential Pair Creation and Pair Rule Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Defining Differential Pairs Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Defining Differential Pairs Automatically. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Assigning Rules to Differential Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Chapter 9
Constraint Template Creation and Reuse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Creating Constraint Templates to Capture Net Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . 147
Constraints and Values Stored With Each Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Constraint Template Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Guidelines for Applying Constraint Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Applying a Constraint Template to Multiple Nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Applying Constraint Templates From the Constraint Templates Page . . . . . . . . . . . . . . . 151
Applying a Constraint Template to a Single Net . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Device Pattern Matching With Constraint Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Modifying Pin Matching for an Applied Constraint Template. . . . . . . . . . . . . . . . . . . . . . 153
Updating Nets With Constraint Template Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Chapter 10
Design Tool Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Constraint and Design Change Management Between Tools . . . . . . . . . . . . . . . . . . . . . . . . 157
Synchronization of Constraint Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Sending Schematic Data to Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Sending Layout Data to Schematics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Appendix A
Constraint Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Constraint Reference Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Trace and Via Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Via Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Table of Contents
Trace Width Minimum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Trace Width Typical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Trace Width Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Differential Spacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Clearances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Trace To Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Trace To Pad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Trace To Via . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Trace To SMD Pad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Pad To Pad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Pad To Via . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Via To Via . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Via To SMD Pad. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Board Edge To Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Board Edge To Pad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Board Edge To Via . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Board Edge To Copper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Board Edge To SMD Pad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Copper To Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Copper To Pad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Copper To Via . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Copper To Copper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Copper To SMD Pad. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Hierarchical Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
# Pins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Net Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Topology Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Power Net . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Analog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Stub Length Max . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
# Vias Max . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Length Min . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Length Max. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Length Manhattan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Length Min Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Length Match . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Length Tol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Length Delta . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Length Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Separation Distance Max . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Differential Spacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Power Net Constraints Supply Voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Hierarchical Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Part Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Qty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

Table of Contents
Part Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

Series. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Pin Package Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Constraint Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Index
End-User License Agreement
with EDA Software Supplemental Terms

Chapter 1
Getting Started Videos
Learn to use Constraint Manager by watching how-to videos that show common tasks in action.
Starting and Exiting From Constraint Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Cross Probing Between Design Systems and Constraint Manager. . . . . . . . . . . . . . . . . 12
Viewing Clearance and Trace Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Creating Net Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Adding Nets to a Net Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Defining Differential Pairs Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Assigning Class-To-Class Clearance Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Creating Constraint Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Starting and Exiting From Constraint Manager

You can launch Constraint Manager from many Mentor Graphics applications. Refer to the
procedure in this topic to determine the command you use to launch it from a specific design
tool in your flow.
Prerequisites
• You properly configured your WDIR environment variable. Refer to your installation
and administration documentation for more information.
Video
Watch the video to learn how to:
• Load a design in your schematic tool.
Cross Probing Between Design Systems and Constraint Manager
• Launch Constraint Manager.
Procedure
1. Launch your design tool.
2. From your design tool, click the Constraint Manager icon ( ) or use its menu path.
Table 1-1. Starting Constraint Manager Through the Menu Path

Design Tool Menu Path
PADS Designer Tools > Constraint
Manager
PADS Layout Setup > Constraint
Manager
PADS Router Setup > Constraint
Manager
Results
Constraint Manager opens and displays the constraint set for the front-end or back-end design.
If the .prj file for the design is read-only, the tool opens in read-only mode. Eventually, to exit
from the tool, in the main window, click x, or from the File menu, click Exit.
Caution
You should not work in Constraint Manager while your host tool is closed. Always exit
Constraint Manager before closing the host tool from which you invoked it.
Cross Probing Between Design Systems and

Constraint Manager
You can enable cross probing between Constraint Manager and the design system from which
you launched the tool. Cross probing, also known as cross select, works in a bi-directional
fashion.
For example, when you select a design object in your PCB layout design system, Constraint
Manager selects the object in its interface. When you select a design object in Constraint
Manager, the host tool selects the design object in its view.
Tip
You can set up Constraint Manager to enable cross probing by default. To learn how to do
this, refer to “Constraint Manager Setup” on page 37.
Prerequisites
• You accessed both data sets using the same file-system method. You cannot mix
methods. For example, cross probing does not work if you access the schematic design
through a mapped drive but the front-end constraint set in standalone mode through a
UNC path.
• You enabled cross probing in the tool from which you launched Constraint Manager.
Video
• Enable cross probing mode in both tools.

• Select an object in your schematic tool and view the result in Constraint Manager.
• Select an object in Constraint Manager and view the result in your schematic tool.
Procedure
1. From the Setup menu, click to enable Cross Probing; or, on the General toolbar, click
.
2. You can cross probe in these ways:

• From your design system to Constraint Manager — In your schematic capture or
PCB layout software, click a design object (for example, a net or component).
• From Constraint Manager to your design system — On the spreadsheet, click the
leftmost column of a design object, or press Ctrl+J to select the current row.
In the example illustration, the user selected net ADDRESS1 for cross probing.
Viewing Clearance and Trace Constraints
Figure 1-1. Cross Probing From Constraint Manager
Tip
You can also cross probe from the Navigator to select all nets that are part of a
hierarchical object like a constraint class or net class. If you do so, your
invocation tool selects all associated nets from within your logic or layout
environment.
Related Topics
Setting Display Options

View clearance and trace constraints to see the minimum distances that must be maintained
between objects, allowable widths for traces, layers enabled for routing, and more.
Video
• View clearance constraints defined as part of the “(Default Rule)” clearance rule.
• Observe trace width constraints defined as part of the “(Default)” net class.
• Identify system-default constraint values.
Creating Net Classes

You create net classes to group specific types of nets for the purposes of defining board-level
physical/manufacturing constraints and assigning clearance rules between nets in the classes.
Net class constraints are located on the Trace & Via Properties spreadsheet page. Although you
create clearance rules on the Clearances spreadsheet, you assign them elsewhere.
Figure 1-2. Net Classes Created for a Design
In the example, the ddr3_group* classes (ddr3_group0, ddr3_group1, ddr3_group2, and

ddr3_group3) all contain nets that are of the same technology type and function, but they have
slightly different current-carrying needs or sensitivity to crosstalk. For this reason, unique net
classes are being used instead of a single ddr3_group net class. Each of the net classes accounts
for the differences in width and spacing.
Video
• Make a net class.

• Clone a net class.
• Rename a net class.
• Modify physical constraints.
Procedure
1. In the Navigator, right-click Net Classes, then click New Net Class.
Note
To create a net class under an existing net class, in the Navigator, right-click a net
class, then click New. You are limited to two levels of hierarchy. The
recommendation is to use hierarchy sparingly. Doing so helps to reduce complexity.
2. Replace the default name “<user>_New” with a name for the net class, keeping the
following in mind:
• You cannot use these characters: ! \ “ /
• Net class names must be 127 characters or less.
• You can use spaces in net class names.
• It is a best practice to use a name that reflects the purpose of the class. For example,
if creating a net class that will contain only signal nets, replace “New” with “Signal
Nets”.
Results
• You can now move nets into the net class.
• The new net class initially takes on the constraint values of the (Default) net class if it is
a top-level net class. If it is a child net class, it takes on the constraint values of its parent
net class.
• You can rename the net class if needed. To do so, in the Navigator, expand Net Classes.
Right-click the net class, click Rename, type a new name, then press Enter.
• You can create child classes under a top-level net class as you need to, but use hierarchy
sparingly.
Adding Nets to a Net Class

After you create a net class, you must define the group of nets that should comprise the net
class. By default, each net class that you create contains no nets.
Note
Each net can belong to one net class.
Video
• Filter the spreadsheet.

• Select filtered nets and move them to a different net class.
• Make net class changes from the Navigator.
• Enable the display of physical nets in the Navigator to easily see the nets in a net class.
Procedure
1. Do one of the following:
• With the Trace & Via Properties spreadsheet page active, from the Edit menu,
click Assign Nets to Classes.
• In the Navigator, expand Net Classes, right-click a net class, then click Assign Nets.
Tip
On the Nets spreadsheet page, select one or more nets, right-click a selected net,
then click Assign Net(s) to Net Class. In the Select Net Class dialog box, select
a net class, then click OK. If using this option, you do not need to finish this
procedure.
2. In the Assign Physical Nets to Net Class dialog box, specify the net class from which
you want to select nets by clicking the Source Net Class dropdown, then clicking a net
class.
For example, if you are adding nets to your first custom class you can select from all
nets in the design by specifying the (Default) class as the source.
3. Specify the net class to which you want to add nets by clicking the Target Net Class
dropdown, then clicking a net class.
4. Under the nets in source net class listing, specify the nets that you want to add to the
target class.
Tip
To select multiple nets, you can use Ctrl-click and Shift-click. To select nets by
name, in the field below the list of source nets, type a search string, then click .
The tool automatically highlights the matching nets. You can also move nets
individually by double-clicking a specific net.
5. Click , then click Apply or OK.
Tip
Before clicking OK, make sure that the list of target nets is accurate. To remove any
nets from the list of target nets, click to select them, then click .
Results
The tool moves the nets to the target the net class; these nets are no longer part of the source
class from which they originated.
Examples
Example of Adding All Available Nets in a Source Net Class to a Target Net Class
Use these steps:
1. In the Assign Physical Nets to Net Class dialog box, specify a source net class, then
specify a target net class.
2. Click , then click OK.
Example of Swapping All Nets in One Net Class With All Nets in Another Net Class
Use these steps:
Defining Differential Pairs Automatically

You can automatically define differential pairs to quickly construct them from specific nets.
After you have the tool automatically construct differential pairs based on a net name criterion,
you select from the proposed list of differential pairs to choose those you want to create. After
you create specific differential pairs, the tool updates the Nets spreadsheet page to include them.
The process of automatically creating differential pairs is not always a viable method. It
depends on whether your nets have naming characteristics that allow for identification of
complimentary nets.
Prerequisites
• Nets that should comprise a differential pair must be part of the same net class and
constraint class.
Video
• Find net pairs that match a search criteria.

• Select the nets to join into differential pairs.
• Assign the new differential pairs to the same net class.
Procedure
• On the Pairs toolbar, click .
• From the Edit menu, click Differential Pairs, then click Auto Assign Differential
Pairs.
2. In the Auto Assign Differential Pairs dialog box, In the Assign by field, select one of
these assignment methods:
• Net Name — Group nets into differential pairs based on net naming conventions.
• Regular Expression — Group nets into differential pairs based on regular-
expression search criteria. If using this assignment method, the tool does not display
search results for the Pair net name field (step 4) when there are no search results for
the Net name field (step 3), even if they do exist.
The advantage of regular expressions is that you can use them to create more precise
net matching searches. In the event that the Net Name assignment method would not
work, you could create a regular expression that would identify certain pairs of
differential nets.
3. In the Net name field, type a search criterion. For example, if assigning by net name, you
could use a search criterion of *_P if you know that each net with this suffix should be
paired with a net of the same name that uses a different suffix.
Tip
To view the list of electrical nets in your design, click Preview Nets. Doing so can
be helpful when you are typing criteria in the Net name field and Pair net name field.
After you finish reviewing the content of the Electrical Nets dialog box, click OK.
4. In the Pair net name field, type an appropriate search criterion based on the Net name
search criterion you provided in step 3, then click .
For example, if assigning by net name, a complimentary suffix to the example in step 3
(*_P) might be *_N. In the illustration, you can see how the tool used the Net name and
Pair net name fields to discover five pairs of nets that may be candidates for differential
pair creation.
Figure 1-3. Automatic Assignment of Differential Pairs
Creating Clearance Rule Sets
Note
It is important to understand that the Net name field takes precedence over the Pair
net name field. This comes in to effect if the net name string or regular expression
string you type results in the same net showing up in both the Electrical Net column and
Pair Net column. In these cases, the nets show up in the Electrical Net column only.
5. Unless you chose to assign by regular expressions, skip to the next step. In this case, the
Match Differential Pairs dialog box appears. For each pair row the tool proposed based
on your regular expressions, you can click within the Pair Net column to select an
alternate pair net, if appropriate. After you finish making adjustments, click Accept.
Note
If two electrical nets on the same row do not match, the tool highlights the Pair Net
cell in red. You can hover over a red cell or refer to the Output window to determine
the cause of the conflict (for example, the two nets do not belong to the same net class).
6. In the list of proposed differential pairs, click to select the differential pairs you want to
use, then click Apply.
Tip
To select all proposed differential pairs, click . To unselect all differential pairs,
click .
7. (Optional) To give one or more differential pairs unique names instead of their system-
defined names, on the spreadsheet, right-click a differential-pair cell, then click
Rename. Now that the cell is editable, type a new name (but exclude these characters: !
\ “ and /), then press Enter.
Results
• The tool sets the Topology Type constraint to Custom for the differential pair and the
nets that comprise it.
• After you create a differential pair, delay cells at the pair level could be highlighted to
indicate errors. This happens if each of the nets you used to create the differential pair
had different delay values defined previously. To remove the error highlighting, you
need to define delay values at the differential-pair level.
• If you need to delete a differential pair, on the Nets spreadsheet page, click a
differential-pair row ( ), then press Delete.

You can specify clearance rules to which net objects must adhere. You can define clearance
rules such as Trace to Pad, Pad to Pad, and Via to SMD Pad.
Assigning Class-To-Class Clearance Rules
Different net classes often require unique design rules in order for nets within a class to
maintain integrity during signal transmission. By creating clearance rule sets, you can address
the unique requirements of the different technology types in a design.
Video
• Create clearance rules.

• Modify the constraints in a clearance rule.
Procedure
1. In the Navigator, right-click Clearances, then click New Clearance Rule.
2. Replace the default name “<user>_New” with a unique name for the clearance rule set.

After you create clearance rule sets, you can assign class-to-class clearance rules that maintain
certain clearances between specific net classes. By doing so, you can apply the rules you
defined in a clearance rule set to one or more pairs of net classes.
You use class-to-class rules to maintain very precise clearance requirements between specific
net objects. These requirements usually relate to electrical, safety, or manufacturability
concerns. For example, high voltage nets in a design that need certain spacing based on the
voltage level of each net.
Also, as you make these assignments, it is important to be aware of the following:
• Class-to-class clearance rules are obeyed between net classes to which you explicitly
assign them. Assignments do not include sub-level net classes. Any child net classes
under a parent net class do not obey the clearance rules of the parent net class.
• When selecting net classes to associate with a clearance rule, you can quickly specify all
other net classes by using the (All) column. Although this can be useful, the (All)
column does not provide for granular rule assignment between a net class and other net
classes.
• Cells that you do not explicitly define (empty cells) do not use (Default Rule).
• The tool makes it possible to assign more than one clearance rule between two net
classes. In these cases, the tool uses the following priority to pick one:
o Net class to net class
o Net class to (All)
o (All) to (All)
For example, if you assign a rule between (All) and (Default), and a different rule
between (Default) and (Default), based on the priority, the tool uses the clearance rule
you assigned between (Default) and (Default).
Prerequisites
• You created the clearance rule sets you want to assign between net classes. For more
information, refer to “Creating Clearance Rule Sets” on page 21.
Video
• Enable the Clearances toolbar.

• Assign a clearance rule between a net class and (All) net classes.
• Assign a clearance rule between two specific net classes.
Procedure
1. On the Clearances toolbar, click ; or, from the Edit menu, click Clearances, then click
Class to Class Clearance Rule.
2. Populate cells in these ways:
• One cell at a time — Click within an editable cell to select the rule to use between
two specific net classes (for example, (Default) and (Default)).
• Assign the same rule to multiple cells — Use Ctrl-click and Shift-click to select a
group of cells. After selecting the last cell, continue holding Ctrl or Shift while you
use the dropdown to make the rule selection.
Creating Constraint Classes
• Copy and paste — Select one or more cells, press Ctrl-C, click a single cell, then
press Ctrl-V. For example, you could select all of the cells in the (All) column and
then quickly copy them into the (Default) column.
As you make changes, the dialog box updates to show them by highlighting the
background of these cells. This makes it easy for you to keep track of all your
changes.
Figure 1-4. Highlighting Shows Cell Changes
3. Continue making rule assignments between net classes.
Tip
Optionally, to revert your changes, click .
4. After you finish, click Apply or OK.

You create constraint classes to group specific nets and then define electrical and signal
integrity constraints such as topology types and stub lengths.
Constraint class constraints are located on the Nets spreadsheet page and Noise Rules page.
Video
• Create a constraint class.

• Add a differential pair to the constraint class.
• Change some length constraints for the differential pair.
Procedure
• In the Navigator, right-click Constraint Classes, then click New Constraint Class.
• On the Nets spreadsheet page, right-click a constraint class, then click New Top
Level Class.
2. Replace the default name “<user>_New” with a name for the constraint class. Keep the
following in mind:
• Constraint class names must be 256 characters or less.
• You can use spaces in constraint class names.
• A best practice is to use a name that reflects the purpose of the constraint class. For
example, if creating a constraint class that will contain only signal nets, replace
“New” with “Signal Nets”.
Results
• You can now move nets into the constraint class.
• The new constraint class initially takes on the constraint values of the (All) constraint
class. This includes both top-level net classes and child net classes.
• You can rename the constraint class if needed. To do so, in the Navigator, expand
Constraint Classes. Right-click a constraint class, click Rename, type a new name,
then press Enter.
Chapter 2
Overview and Setup
This section is an introduction to the tool that provides an overview of it and constraint-driven
design flows. It also includes information about invocation, setup, and application
customization.
Note
At a minimum, make sure to read “Before You Begin Using Constraint Manager” on
page 29. It includes important information for each PCB design flow that uses Constraint
Manager.
Constraint-Driven Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Before You Begin Using Constraint Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Starting and Exiting From Constraint Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Viewing Constraint Database Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Folder Structure and Location of Constraint Manager Log Files . . . . . . . . . . . . . . . . . 34
Cross Probing Between Design Systems and Constraint Manager. . . . . . . . . . . . . . . . . 34
Constraint Manager Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Display Customization of Constraint Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Customizing Command Shortcut Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Default Keyboard Shortcuts Provided With Constraint Manager . . . . . . . . . . . . . . . . . 52
Constraint-Driven Design
Constraint Manager gives you the ability to manage design constraints in a common
environment. By using it, you can view, edit, and specify access to constraints in a single tool
that is tightly integrated into your PCB design flow.
The ultimate result is that the tool helps to reduce costly research and development expenses
that are associated with multiple design revisions for a single product release.
Constraint-Driven Design Flows

The tool is available in these integrated design flows:
• Xpedition® Enterprise
• PADS® Professional
Overview and Setup
Constraint-Driven Design
• PADS Designer-PADS Layout (Integrated Workflow)

• Keyin netlist-Xpedition Layout
• Design Capture®/DesignView®-Xpedition Layout
Organization of Physical Design Rules Through Net Class Creation

A net class is a set of physical constraints defined for each board layer. By assigning individual
nets to net classes, you can require them to use certain physical rules during placement, routing,
and DRC. In addition, you can define clearance constraints between net classes, making the
clearance between two objects depend on the net class each object is in.
For more information, see “Creating Net Classes” on page 15.
Time Saving and Error Reduction Through Constraint Class Creation

You use constraint classes to group and define electrical constraints. Constraint classes give you
the ability to specify net constraint values once for all nets in a class. Nets you put into the class
later inherit those constraints, too.
For more information, see “Creating Constraint Classes” on page 24.
Design Constraint Verification

If you view physical routing results in Constraint Manager, you can use easily see if those
results meet your constraint values. These results are called actuals. If Constraint Manager is
connected in this way, the spreadsheet updates to include not only routing results but also a
visual indication of adherence.
For example, if the routed length of a net is too close to either its minimum or maximum
constraint, or exceeding either value, the cell that displays the actual is backlighted in red or
yellow to indicate that the actual exceeds, or comes close to exceeding, the constraint values.
For more information, see “Validating PCB Actuals Against Constraints” on page 87.
Overview and Setup
Before You Begin Using Constraint Manager
Before You Begin Using Constraint Manager

In preparation for using Constraint Manager, you should be aware of certain requirements,
limitations, and tool behavior.
They are:
• The tool supports entry of English characters only. Although you can view GUI text in
languages other than English, you must type English characters into the tool.
• Memory requirements are design dependent and based on the relative size of a design.
Operating systems that use a 32-bit architecture have a process-size limitation of 2 GB.
This means that regardless of how much memory is available, no single process is
allowed to use more than 2 GB of memory. A large number of net classes and layers are
examples of objects that may exceed memory limits in the tool. As a result, you may not
be able to open large designs.
• Constraint Manager automatically recognizes some net names as power-supply nets. As
such, it enables the Power Net constraint for them. For more information, refer to “Net
Names Constraint Manager Automatically Recognizes as Power-Supply Nets” on
page 135.
• Ensure that you properly configured your WDIR variable. Refer to the Installation and
Administration Manual for your release for more information.
• If you launch the tool on a read-only .prj file, it opens in read-only mode. If Constraint
Manager unexpectedly opens in read-only mode, you should check to ensure that you
have write access permissions for the .prj file.
• In the event that the tool reports an error message that includes a UID number (for
example, “507,692,52”), you should run CES Diagnostics to check constraints and
attempt to fix the error. For more information, refer to “Checking Constraints
Synchronization” on page 81.
• When rolling back constraint changes made in Constraint Manager, the forward and
back annotation indicator lights for your design flow do not reflect these undo actions.
For example, after you make a single change in back-end Constraint Manager and then
rollback that change, your back-end system will still indicate that you need to perform
back annotation.
• Depending on the design flow you are using, the invocation tool from which you
launched Constraint Manager may or may not save your changes by default. In order to
keep from losing data, ensure that you understand the unique save process of your
design system, and use it appropriately to save constraint changes within each applicable
session. For example, the schematic tools automatically save data and constraints, but
PCB layout tools require an explicit save before they write PCB layout changes and
Overview and Setup
PADS Designer-PADS Layout (Integrated Workflow)
constraint changes to disk. When making a Constraint Manager change in a session

launched from a PCB layout tool, it is important to understand the following:
o All changes you make in Constraint Manager are reflected in the layout invocation
tool after you exit Constraint Manager.
o You can send pending Constraint Manager changes to the layout tool during the
active Constraint Manager session. To do so, at the bottom-right corner of your PCB
layout tool, click the rightmost status indicator to load the changes into the back-end
design system.
• A constraint cell shows ‘#’ if the precision is too low for it to display a meaningful
value. For example, 0.000435 V would show ‘#’ if the precision is set to 3. With
precision set to 4, it shows ‘0.0004’. To set precision, refer to “Setting Unit Notation” on
page 45.
• The tool does not create an electrical net if both ends of a series component (for
example, resistor) are connected to the same instance of a device.
PADS Designer-PADS Layout (Integrated Workflow) . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Overview of Electrical Nets and Physical Nets in Constraint Manager . . . . . . . . . . . . . 31
Automatically Recognized Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Electrical Nets Defined Through a Package With More Than Two Pins. . . . . . . . . . . . 32
PADS Designer-PADS Layout (Integrated Workflow)

If using this flow, you should be aware of these additional requirements, limitations, and tool
behaviors.
They are:
• You should not work in Constraint Manager while your host tool is closed. Always exit
Constraint Manager before closing the host tool from which you invoked it. For
example, exit Constraint Manager, then close the PADS Designer tool.
• The version of Constraint Manager in this flow includes less functionality than versions
of the tool provided with other flows. If you are familiar with Constraint Manager
because you have used it in another flow, you should carefully review this version of the
tool and its documentation prior to using it. Here are some of the key differences:
o Absence of rule-area schemes.
o Hierarchical constraint classes are not available.
o Just two levels of net class hierarchy are supported.
o Trace constraints only support physical length and not time of flight delay.
o Only MST, Chained, and Custom topology types are available.
Overview and Setup
Overview of Electrical Nets and Physical Nets in Constraint Manager
o Many of the Nets and Parts spreadsheet constraints are not supported.
• If you use the Copy Sheet command in the PADS Designer tool, the tool only copies
constraint values if you enable the “Copy Constraints on Copy Sheet” option in the
tool’s Advanced settings. The tool does not copy values if you use the Copy Block
command.
• The PADS Router tool ignores electrical net constraints if you do not have a High-speed
Routing license.
Overview of Electrical Nets and Physical Nets in

Constraint Manager
The tool automatically populates the Nets spreadsheet with electrical nets and physical nets
based on definitions that are unique to Constraint Manager. Definitions for other objects like
differential pairs, components, and terminators are not unique to Constraint Manager.
They are:
• Physical net (pNet) — A physical net ( ) is a net where all pins of the net are
connected by a trace, via, or plane segment.
• Electrical net (eNet) — An electrical net ( ) is made up of one or more physical nets
that are connected together logically or electrically through (usually passive)
components. Electrical nets are generated by Constraint Manager. A common example
of an electrical net containing two physical nets is one where Net A and Net B are
connected through a series resistor. Electrically, the signal on Net A goes through the
resistor and continues on through Net B as if it were all one net. Note the following:
o There must be an electrical net for every physical net. Because of this, the simplest
example of an electrical net is a single physical net that is not connected to any other
physical nets through passive components. In this case, the electrical net is the same
as the physical net below it.
o The tool denotes electrical nets that include two or more physical nets on the Nets
page of the spreadsheet. It adds a ^^^ suffix to the end of the net name as it appears
in the first column (Constraint Class/Net/*).
Note
Constraint Manager does not create an electrical net if both ends of a series
component (for example, resistor) are connected to the same instance of a device.
Automatically Recognized Topologies

Constraint Manager automatically recognizes two termination strategies when it recommends
differential pairs within the context of electrical nets. In these cases, the tool ignores some
Overview and Setup
Electrical Nets Defined Through a Package With More Than Two Pins
connections, which can result in orphaned physical nets. The tool ignores connections so the
two poles of the differential pair can remain separate, allowing for the pair to be recognized.
They are:
• Standard parallel termination — If the two poles of a differential pair are joined
through a resistor, the tool ignores the resistor connection. Doing so keeps the two poles
of the pair from being joined into a single electrical net.
• Alternative parallel termination — If the two poles of a differential pair are joined
through two resistors (with a capacitor taking the net to ground), the tool ignores the
connection through the resistors.
Figure 2-1. Differential Pair Topologies Automatically Recognized by
Constraint Manager
Electrical Nets Defined Through a Package With

More Than Two Pins
Constraint Manager creates electrical nets through parts with more than two pins if you
correctly configure both the tool and the part. For example, you could set up a 4-pin resistor
pack for this usage.
In order for Constraint Manager to do this, you must meet these requirements:
• You defined the reference designator prefix for the part as an available discrete
component prefix (for example, RN).
When the tool does this, it sets the Parts page Series constraint to enabled/on for the part.

You can launch Constraint Manager from many Mentor Graphics applications. Refer to the
procedure in this topic to determine the command you use to launch it from a specific design
tool in your flow.
Overview and Setup
Prerequisites
• You properly configured your WDIR environment variable. Refer to your installation
and administration documentation for more information.
Video
• Load a design in your schematic tool.

• Launch Constraint Manager.
Procedure
1. Launch your design tool.
2. From your design tool, click the Constraint Manager icon ( ) or use its menu path.
Table 2-1. Starting Constraint Manager Through the Menu Path

Design Tool Menu Path
PADS Designer Tools > Constraint
Manager
PADS Layout Setup > Constraint
Manager
PADS Router Setup > Constraint
Manager
Results
Constraint Manager opens and displays the constraint set for the front-end or back-end design.
If the .prj file for the design is read-only, the tool opens in read-only mode. Eventually, to exit
from the tool, in the main window, click x, or from the File menu, click Exit.
Caution
You should not work in Constraint Manager while your host tool is closed. Always exit
Constraint Manager before closing the host tool from which you invoked it.
Overview and Setup
Viewing Constraint Database Log Files
Viewing Constraint Database Log Files

Constraint Manager generates log files for various situations during the course of a design
project.
Procedure
From the File menu, click File Viewer.
Folder Structure and Location of Constraint

Manager Log Files
Constraint Manager writes log files (.log) within each design folder, using subfolders to
distinguish between the snapshot name, block name, machine name, and user name. Within
each log file folder, the tool names log files based on the date and time you started a session.
Each time you close and reopen the tool, it adds a new set of log files. This topic shows the
individual directory structures that exist for front-end and back-end Constraint Manager
sessions.
Schematic Log Files Folder Structure

<design_folder>\CES\LogFiles\<snapshot_name>\<block_name>\<machine_name>\
<user_name>
For example, C:\Phone_design_1\CES\LogFiles\DxD\keypad\psmith-lt\psmith.
Layout Log Files Folder Structure

<design_folder>\CES\LogFiles\<snapshot_name>\<block_name>\<machine_name>\
<user_name>
For example, C:\Phone_design_1\CES\LogFiles\keypad_Layout_Temp\keypad\psmith-lt\

psmith.
Cross Probing Between Design Systems and

Constraint Manager
You can enable cross probing between Constraint Manager and the design system from which
you launched the tool. Cross probing, also known as cross select, works in a bi-directional
fashion.
For example, when you select a design object in your PCB layout design system, Constraint
Manager selects the object in its interface. When you select a design object in Constraint
Manager, the host tool selects the design object in its view.
Overview and Setup
Tip
You can set up Constraint Manager to enable cross probing by default. To learn how to do
this, refer to “Constraint Manager Setup” on page 37.
Prerequisites
• You accessed both data sets using the same file-system method. You cannot mix
methods. For example, cross probing does not work if you access the schematic design
through a mapped drive but the front-end constraint set in standalone mode through a
UNC path.
• You enabled cross probing in the tool from which you launched Constraint Manager.
Video
• Enable cross probing mode in both tools.

• Select an object in your schematic tool and view the result in Constraint Manager.
• Select an object in Constraint Manager and view the result in your schematic tool.
Procedure
1. From the Setup menu, click to enable Cross Probing; or, on the General toolbar, click
.
2. You can cross probe in these ways:

• From your design system to Constraint Manager — In your schematic capture or
PCB layout software, click a design object (for example, a net or component).
• From Constraint Manager to your design system — On the spreadsheet, click the
leftmost column of a design object, or press Ctrl+J to select the current row.
In the example illustration, the user selected net ADDRESS1 for cross probing.
Overview and Setup
Figure 2-2. Cross Probing From Constraint Manager
Tip
You can also cross probe from the Navigator to select all nets that are part of a
hierarchical object like a constraint class or net class. If you do so, your
invocation tool selects all associated nets from within your logic or layout
environment.
Related Topics
Overview and Setup
Constraint Manager Setup
Constraint Manager Setup

You can specify options to customize the most appropriate Constraint Manager environment.
The tool uses these settings, and the settings associated with units displayed in the spreadsheet
editor, for all designs you work on.
Settings are unique for each copy of Constraint Manager installed as part of a specific flow.
Although most settings are machine and flow specific, there is a small number of settings
unique to each design.
Specifying Design Configuration Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Specifying Electrical Net Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Specifying Discrete Component Prefixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Setting Display Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Setting General Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Setting Fonts and Colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Setting Spreadsheet Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Setting Unit Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Specifying Other Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Reusing Settings in External Designs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Specifying Design Configuration Preferences

Design configuration preferences are settings that affect an entire design rather than specific
design objects (for example, layers or nets).
Procedure
1. From the Setup menu, click Settings; or, on the General toolbar, click .
2. In the Settings dialog box, click Design Configuration.
3. Under Default tolerances, specify the following:
• Distance — A default physical tolerance for length constraints. This is the allowable
default deviation for any match group length constraints you define in Constraint
Manager.
4. To change the number of seconds a user can reserve a constraint cell for editing while
working concurrently, in the Maximum locking timeout field, type a different value.
5. Click OK.
Overview and Setup
Specifying Electrical Net Preferences
Specifying Electrical Net Preferences

You can specify electrical net preferences such as the maximum number of physical nets that
can comprise an electrical net.
Prerequisites
• You must be using a Constraint Manager session launched from the front-end or a
standalone session of the tool.
Procedure
2. In the Settings dialog box, under Design Configuration, click Electrical Nets.
3. Specify the maximum number of physical nets that may comprise an electrical net.
Using too low of a setting may cause Constraint Manager to create too many electrical
nets. Too high of a setting could cause the tool to create too few electrical nets, each of
which contains many physical nets. For more information, refer to “Overview of
Electrical Nets and Physical Nets in Constraint Manager” on page 31.
4. Specify the net pin count threshold to use to determine whether a net is potentially a
signal net.
Tip
Identify the signal net in your design with the smallest number of pins, and then set
this value to that number minus one. For example, if the smallest signal net in a
design contains 15 pins, set this value to 14.
5. Click OK.
Specifying Discrete Component Prefixes

You must specify discrete component prefixes in order for Constraint Manager to identify the
parts that are of this type.
Note
The tool identifies resistor packs with 2-pin schematic symbols as series connections. You
must use 2-pin schematic symbols to ensure Constraint Manager recognition.
Prerequisites
Procedure
Overview and Setup
2. In the Settings dialog box, under Design Configuration, click Discrete Component
Prefixes.
3. Specify all possible reference designator prefixes for the parts in your design. Keep the
following in mind:
• If your design flow includes reuse blocks, you must include special reference
designator prefixes that support reuse blocks. They are of the format #_<type>. For
example, #_R supports resistors in reuse blocks and #_C supports capacitors in reuse
blocks. To be safe, for each prefix that you define, you should include an additional
prefix in this format.
• If your design uses reference designators that are of the format YYYRNN
(schematic sheet, reference designator prefix, unique instance), append a # to each
discrete component prefix that you define. For example, instead of using just C to
define the discrete component prefix for capacitors, use #C.
• If a part type has instances with multiple reference designators, Constraint Manager
determines that a part is a discrete if you specify at least one of the refdes prefixes.
For example, part type RES has instances R1 -> R10 and X1 -> X10. If either R or X
are in the list, the tool considers the part and its instances to be resistors.
In the example illustration, each discrete component has at least two defined prefixes.
Connectors have three prefixes: P, J, and PJ. Resistors have four prefixes: R, RR, RN,
and RP.
4. Click OK.
Results
After you finish modifying discrete component prefixes, Constraint Manager automatically re-
generates electrical nets. In order to update layout, you must package the design and forward
annotate.

You can set display options such as cross probing settings, whether the tool should display row
numbers in the spreadsheet, and the availability of scrolling buttons for the listing of
spreadsheet tabs.
Overview and Setup
Setting General Options
Procedure
2. In the Settings dialog box, click Display.

3. Under Window Settings, specify whether Constraint Manager should cross probe
between itself and the host tool, by default.
Note
If setting display options for CTE, “Set the default cross probing mode to ON” is
intentionally grayed out and not available.
4. To turn on cross probing from the Navigator, click to enable its check box.
5. Click to enable row, column, or header highlighting and indication of remotely modified
cells. Both are useful if working concurrently.
6. To show row numbers, click to enable the associated check box.
7. Enable or disable “Show scrolling buttons for tabs” to include the left and right arrow
buttons next to the tabs you use to select specific spreadsheet pages.
8. To highlight constraint changes made by concurrent users, enable “Show indication of
remotely modified cells.”
9. To automatically show differences between parent and child objects, click to enable the
associated check box.
10. Click OK.
Setting General Options

You can set general options such as the initial magnification level of the tool, default tolerances
for constraint values, and what should happen when you press the Enter key if a cell is active.
Procedure
2. In the Settings dialog box, under Display, click General.

3. Under Initial Zoom Level, specify the default size of spreadsheet fonts and rows by
typing a percentage value. As you increase this value, the size of spreadsheet fonts
increase.
4. Under Inactive Draw Combobox Buttons, specify when Constraint Manager should
display comboboxes within a spreadsheet field. If you enable this option, any cell that
can display a dropdown list will always display the down arrow box. If disabled, the tool
displays the dropdown box for a cell after you click within the cell.
Overview and Setup
Setting Fonts and Colors
5. Under Spin Edit Control, specify whether integer value spreadsheet fields should
display up and down arrows beside them when clicked. You use these arrows to increase
or decrease the integer value within a cell without using the keyboard.
6. Choose the preferred action of the LMB when you double-click it. You can choose
expand cell, rename cell, or no action.
7. Choose the preferred action that occurs after you press the Enter key within a cell. You
can choose to move to up, down, left, or right from the current cell.
8. Under Tolerances, specify these values:
• Design tolerance of constraints compared against actual back-annotated design
values. In the Constraint violation warning field, type a percentage value.
For example, if the Constraint violation warning field contains 90%, the tool
highlights actual values in yellow that are ninety percent, or a greater, of the
associated constraint value to indicate an actual that is close to the acceptable
constraint value. If an actual value exceeds the constraint value, the tool highlights
the field in red.
9. Under Change Impact Dialog, specify what should happen if you attempt to change a
child constraint override at the parent constraint level:
• Change all affected values — Replace all child values with the value provided at
the parent constraint level. Does not show the Change Impact Prompt dialog box.
• Keep all overrides but change others — Replace only the child values that match
the old parent value. Does not show the Change Impact Prompt dialog box.
• Always prompt user for all values — Prompt for all values using the Change
Impact Prompt dialog box, whether the current value is an override or not.
Note
For more information on how these settings affect your constraint editing
environment, refer to “Choosing From Among Change Impact Actions” on page 56.
10. Click OK.
Setting Fonts and Colors

You can set font and color options to control the appearance of header and constraint cells, the
background colors the tool uses to indicate violations, and the colors the tool uses to display
information in the Output window.
Procedure
2. In the Settings dialog box, under Display, click Fonts and Colors.
Overview and Setup
Setting Spreadsheet Units
3. Modify any of these options:

• Specify the header font and cell font appearances for defaults, constraints, and
properties.
• Specify the header font, cell font, and background color appearance settings for
actuals, read-only values, static values, and disabled cells.
• To help you identify changes made by concurrent Constraint Manager users, specify
background colors and cell fonts for edited cells, locked cells, and modified cells.
• Specify the background cell color the tool uses to indicate violations of type caution
or error.
• Specify the background color for other/hierarchical items like Different, Default
Value, and Override Value.
• Specify the colors the tool uses to indicate the presence of comment marks and
propagation marks.
• Specify the color and font the tool uses to display content in the Output window.
Note
Although the heading for this column of the dialog box states that all colors are
background colors, you use Font, Error, Warning, and Path rows to set textual
colors.
4. Click OK.

You can specify the units Constraint Manager displays for the different types of constraint data.
The tool uses your preferences to format the display and entry of values. These settings do not
affect the units you use in a host design system.
Procedure
2. In the Settings dialog box, under Display, click Display Units.

3. On the Display Units page, for each unit type, specify the unit and precision you want to
use. Refer to the table if you need help determining the meaning of a specific unit.
Overview and Setup
4. Click OK.
Table 2-2. Available Display Units

Field Description Default Values
Angle You can choose from the following deg; 3
units:
• deg – degree
• rad – radian
• ' – minutes
• " – seconds
Capacitance You can choose from the following F; 3
units:
• F – farad
• mF – millifarad
• uF – microfarad
• nF – nanofarad
Current You can choose from the following A; 3
units:
• A – ampere
• mA – milliampere
• uA – microampere
• pA – picoampere
Current Density The tool expresses this unit type in mA/th^2; 3
milliamperes over thousandths of an
inch squared (mA/th^2).
Inductance You can choose from the following H; 3
units:
• H – henry
• mH – millihenry
• uH – microhenry
• nH – nanohenry
Linear You can choose from the following th; 3
units:
• in – inch
• th – thousandth of an inch
• mm – millimeter
• um – micrometer
• nm – nanometer
Overview and Setup
Table 2-2. Available Display Units (cont.)

Power You can choose from the following W; 3
units:
• kW – kilowatts
• W – watts
• mW – milliwatts
• uW – microwatts
• nW – nanowatts
Resistance You can choose from the following Ohm; 3
units:
• MOhm – mega-ohm
• KOhm – kilo-ohm
• Ohm – ohm
• mOhm – milli-ohm
• uOhm – micro-ohm
Temperature This unit type is expressed in degree degC; 3
Celsius (degC).
Theta This unit type is expressed in degree degC/W; 3
Celsius per watt (degC/W).
Time You can choose from the following ns; 3
units:
• s – second
• ms – millisecond
• us – microsecond
• ns – nanosecond
• ps – picosecond
Velocity You can choose from the following in/ns; 3
units:
• in/ns – inch per nanosecond
• m/s – meter per second
• %c – percentage of the speed of light
Overview and Setup
Setting Unit Notation
Table 2-2. Available Display Units (cont.)

Voltage You can choose from the following V; 3
units:
• kV – kilovolt
• V – volt
• mV – millivolt
• uV – microvolt
• nV – nanovolt
Setting Unit Notation

You can specify the precision and format of electrical units displayed by Constraint Manager.
For example, you can use engineering notation with a precision of three digits after the decimal
point, scientific notation with two digit post-decimal point precision, or choose not to format
electrical units and always display full precision.
Procedure
2. In the Settings dialog box, under Display, click Notation.

3. On the Notation page, under Electrical units, specify the format and precision you want
to use for electrical units.
For example, to use SPICE format with a precision of 5, click the radio button next to
SPICE, and in its associated Precision field, type 5.
Note
If you do not want to format electrical units and want to use full precision, click the
“Do not format electrical units and use full precision” check box. If the precision is
too low to display a meaningful value, a constraint cell will display ‘#’ instead of a
number.
4. Under Regional settings, specify the decimal point symbol to use, the number of digits
to display after the decimal point, and other similar properties.
5. To suppress the display of trailing zeros, click to activate the “Suppress trailing zeros”
check box.
For example, if using engineering format with a precision of 5, the tool displays a
spreadsheet value of 8.12300 as 8.123. If you do not suppress trailing zeros, the tool
displays all five post-decimal values.
6. Click OK.
Overview and Setup
Specifying Other Preferences
Specifying Other Preferences

You can specify additional preferences for things such as actuals, constraint diagnostics, and log
file storage.
Prerequisites
• You can only modify certain actuals preferences if you are in a Constraint Manager
session launched from the back-end. You must modify the remaining preferences from a
front-end session.
Procedure
2. In the Settings dialog box, click Other.

3. To have Constraint Manager automatically display updated actuals produced by your
layout tool during interactive routing, under Actuals, activate the Layout Dynamic
update check box. (The tools grays out this option if it is not available.)
4. To automatically update actuals upon Constraint Manager invocation, under Actuals,
activate the “Auto update on start up” check box.
5. To automatically export actuals to schematic capture for display in Constraint Manager,
under Actuals, click to enable Export actuals to front-end. The tool exports actuals each
time they are updated, whether manually or automatically.
6. To show alerts in Constraint Manager front-end sessions that updated actuals can be
imported, under Actuals, click to activate the appropriate check box. If this option is
enabled, a small message appears above the spreadsheet each time new actuals become
available.
7. To automatically run CES Diagnostics upon exit, activate the associated check box.
8. To automatically update nets that use a constraint template when any of the constraint
template values are updated, click to activate “Automatically apply templates”. If
activated, you never need to re-apply constraint templates to individual nets to which
they are assigned.
9. To cross probe from the host tool to the parent electrical net of a physical net instead of
the physical net, select the “Cross Probe to Electrical Net” check box.
10. To store log files generated during your Constraint Manager session locally at your
WDIR location, ensure that you enable the appropriate check box.
Note
By default, the tool enables this check box. If you disable it, the tool stores log files
in the project directory for the design.
Overview and Setup
Reusing Settings in External Designs
11. When cross probing from Constraint Manager, to have your design tool select no more
than a maximum number of nets, type a value in the “Maximum number of selected
nets” field.
12. Specify how old a log file needs to be before archiving it.
13. Click OK.
Reusing Settings in External Designs

You can reuse your Constraint Manager environment settings in other designs. You do so by
exporting to a file, and then importing that file in any other Constraint Manager session. This is
useful for maintaining the workgroup standards of a large design team, or reusing your own
design settings on different machines.
Procedure
1. From the File menu, click Export, then click Settings.
2. In the Export Settings dialog box, specify a path and filename, then click Save.
3. (Optional) Provide this settings file (.ini) to other engineers.
4. In any external Constraint Manager design, from the File menu, click Import, then click
Settings.
5. In the Import Settings dialog box, select the settings file saved previously (for example,
workgroup.ini), then click Open.
Overview and Setup
Display Customization of Constraint Manager
Display Customization of Constraint Manager

You can customize the display of Constraint Manager to design the most efficient work
environment for the completion of your constraint tasks. You can toggle the display of specific
windows, toolbars, and spreadsheet pages, and change the positions of windows and toolbars.
Display customizations you make are unique to your machine. They are available in all designs
you work with in Constraint Manager.
Note
The initial view of Constraint Manager is streamlined to present you with just the core set of
spreadsheet pages and toolbars.
Toggling the Display of Windows and Toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Changing the Position of Windows and Toolbars. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Folder Location of the ces.ini Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Toggling the Display of Windows and Toolbars

You can toggle the display of specific spreadsheet pages, toolbars, and windows. For many of
these items, you can quickly display a group of default objects, or all objects.
Procedure
1. Choose the View menu.
2. Click to toggle the display of specific GUI objects:
• Tabs — Toggle this set of selections to display or exclude specific pages of the
Spreadsheet (for example, Parts). To show all tabs, click All. To show only the
default tabs, click Default.
Tip
You can also toggle spreadsheet pages by right-clicking any of the tabs at the
bottom of the application.
• Navigator — This also known as the browser. Toggle this set of selections to
display or exclude items in this listing of Constraint Manager nodes (such as net
classes and constraint classes). You can also hide the navigator.
o To show all nodes, click All.
• Output — Toggle this setting to display or exclude the log/output window.
• Status Bar — Toggle this setting to display or exclude the status bar that appears at
the bottom of the application.
Overview and Setup
Changing the Position of Windows and Toolbars
• Remotely Modified Data — Toggle Enable Indication to highlight cells modified

concurrently by other users. You can also click to Refresh the display of this type of
change.
• Toolbars — Toggle this set of selections to display or exclude specific toolbars. To
show all toolbars, click All. To show only the default toolbars, click Default.
Results
Your display changes are available now and in future Constraint Manager sessions. The
changes are written to your ces.ini file.
Related Topics
Folder Location of the ces.ini Configuration File
Changing the Position of Windows and Toolbars

You can move Constraint Manager windows and toolbars to different areas of the application or
choose to leave them undocked. You can also set specific windows to hide automatically when
you are not using them.
Procedure
1. Click and hold the window handle or toolbar handle of the interface element you want to
move.
Figure 2-3. GUI Object Handles
2. Move the interface element to position it within Constraint Manager, keeping the
following in mind:
• You can change the position of toolbars at the top of Constraint Manager or leave a
toolbar undocked by moving it out of the toolbar area at the top of the application.
• If you move a window, the display of the tool changes to show you where you can
quickly dock the window.
Overview and Setup
Figure 2-4. GUI Position Indicators
Drag the window and mouse over one of the icons and release. The tool highlights
the new location for the window when you select its positioning icon. (These
positioning icons also appear at the borders of the application.)
You can instead undock a window by not moving it into one of the preset positions,
or move a window into a preset position that is already occupied and have it share
the space with one or more windows.
Tip
Sometimes windows seem to get in the way no matter where you put them. You
can set a Constraint Manager window to automatically hide until you hover the
mouse over the window label. To do so, click the pin icon to the right of the window
handle; or, right-click the window handle, then click Auto Hide.
Results
Your display changes are available now and in future Constraint Manager sessions. The
changes are written to your ces.ini file.
Related Topics

The tool stores application customizations, which exclude design settings and preferences,
locally for each user at one of the operating system-specific folder locations. This file includes
user customizations for windows, toolbars, and other GUI customizations you can make to
Constraint Manager.
There are some customizations that are not stored in the referenced file:
• Command shortcut keys — Stored in the WDIR location specific to your software
installation in the file ces_shortcuts.ini.
• User-created constraint groups — Stored in the WDIR location specific to your
software installation in the file user.cns.
Overview and Setup
Customizing Command Shortcut Keys
Caution
If you intend to remove or replace a ces.ini file, you must do so while Constraint
Manager is not running.
Windows Locations
The tools stores the GUI customization file (ces.ini) at one of these locations:
• c:\Users\<user>\AppData\Local\MentorGraphics\<software version>\ces.ini
(Windows 7 and 8)
For example, c:\Users\psmith\AppData\Local\MentorGraphics\PADSVX.1\ces.ini
• c:\Documents and Settings\<user>\Application Data\MentorGraphics\<software
version>\ces.ini (Windows XP and earlier)
For example, c:\Documents and Settings\psmith\Application Data\MentorGraphics\
PADSVX.1\ces.ini
Customizing Command Shortcut Keys

You can customize command shortcut keys to associate key combinations with commands that
do not already have them, change existing key combinations, and assign multiple shortcut
combinations to a single command.
For example, if Constraint Manager does not include what you consider to be an intuitive
shortcut combination for a command, you can remove the existing command, and then define
your own shortcut combination. As an alternative, you can add an additional shortcut
combination.
Prerequisites
• To execute and test the accessibility of some Constraint Manager commands through
shortcut combinations, you must have a design loaded in order to access all
functionality.
Procedure
1. From the Constraint Manager Setup menu, click Shortcuts.
2. In the Customize dialog box, in the list box of Commands, click to select a command,
then do any of the following:
• Create a shortcut — Click New, then do the following:
i. When the New Shortcut dialog box appears, key-in the combination you want to
use. It can consist of Ctrl, Shift, Alt, and then a letter key, number key, or F# key
(for example, Ctrl+Shift+Alt+F8).
Overview and Setup
Default Keyboard Shortcuts Provided With Constraint Manager
ii. After you finish pressing the appropriate shortcut key combination, visually
verify that it is correct, then click OK.
• Delete a shortcut — In the Current shortcuts list box, click a shortcut, then click
Remove.
3. (Optional) To remove all user-defined shortcuts and reset the list of shortcuts to just the
defaults, click Remove All.
4. After you finish adding, modifying, or deleting shortcut combinations, click OK. In the
event that you made changes that you do not want to keep, click Cancel.
Default Keyboard Shortcuts Provided With

Constraint Manager
The table provides a list of all keyboard shortcuts available in Constraint Manager. The table is
ordered with respect to the layout of the tool’s menu system. Commands that do not have menu
selections are listed at the end of the table.
Table 2-3. Constraint Manager Keyboard Shortcuts

Menu Command/Command Default Shortcut(s)
File > Print Ctrl+P
Edit > Undo Ctrl+Z
Alt+Backspace
Edit > Redo Ctrl+Y
Edit > Cut Ctrl+X
Shift+Delete
Edit > Copy Ctrl+C
Ctrl+Insert
Edit > Paste Ctrl+V
Shift+Insert
Edit > Find Ctrl+F
Help F1
Display constraint help Shift+F1
Zoom full F6
Zoom in F7
Zoom out F8
Chapter 3
Constraint Spreadsheet Usage
In Constraint Manager, spreadsheets are the primary interface for entry and modification of
constraint values. This section provides information on displaying and navigating spreadsheets
pages, filtering and searching for constraints, working concurrently with other users on the same
constraint set, and much more.
Constraint Definition Through Spreadsheet Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Removing Unused Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Searching for Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Filtering Spreadsheet Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Filtering the Spreadsheet by Row Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Resetting a Spreadsheet to its Default View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Concurrent Constraint Entry With Other Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Constraint Value Commenting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Viewing Constraint Reference Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Viewing Design Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Checking Constraints Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Constraint Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
PCB Actuals Comparison With Constraint Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Constraint Change Undo and Redo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Viewing and Reverting to Parent Cell Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Saving Constraint Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Constraint Definition Through Spreadsheet Pages
Constraint Definition Through Spreadsheet

Pages
The Constraint Manager interface for entry and modification of data is a spreadsheet that is
separated into pages. Each page corresponds to specific types of constraint data. The constraints
located on some spreadsheet pages are further groupable by listing only a pre-defined subset of
a constraint set. This makes it easier to isolate the set of constraints you want to modify.
While providing or modifying the data on each of these pages, you can search for net and
constraint data, filter data, sort data, and validate constraints against actuals that the layout
software produced during routing.
Overview of Constraint Hierarchy and Overrides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Choosing From Among Change Impact Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Required Propagation Rules That Constraint Manager Maintains . . . . . . . . . . . . . . . . 58
Organization of Constraints Into Pages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Spreadsheet Page Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Spreadsheet Icons Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Resizing Spreadsheet Columns and Rows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Zooming the Display of Spreadsheet Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Expanding and Collapsing Spreadsheet Rows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Sorting Spreadsheet Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Deletion of Constraint Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Constraint Value Copy-and-Paste Between Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Overview of Constraint Hierarchy and Overrides

Constraint Manager uses hierarchy extensively for two main purposes. The first is to organize
and maintain relationships between different types of objects. For example, pins on a part, or
nets in a differential pair. The tool attempts to maintain the important relationships between
constraint objects and values, especially those used by other tools (such as your layout
software).
The other purpose is to provide a convenient way to group objects (nets, for example) into
classes that share the same constraints. This grouping gives you the ability to define constraints
once for an entire group. Another example usage of classes is to group nets that are the same
type. Overall, hierarchical grouping gives you the ability to organize your design data and make
your job easier.
For example, by grouping 32 bus nets into the same constraint class, you can quickly assign a
single constraint value to the class (for example, # Vias Max (maximum number of vias))
Overview of Constraint Hierarchy and Overrides
instead of manually assigning the same value to each of the 32 nets. If you need to deviate from
a constraint class value, you can type an override value into one or more net rows.
To help make it clear that constraint values under a hierarchical object have overrides,
Constraint Manager can highlight the background of parent-level cells. To turn on this type of
highlighting, refer to “Setting Display Options” on page 39. In the illustration, you can see that
although the constraint class row defines # Vias Max as 10 for each net row, DCON3 and
DCON4 have overrides that replace the parent value. The tool uses cell highlighting at the
parent level to indicate that one or more overrides exist at the child level.
Example 3-1. Overrides at the Net Level
In the illustration, the tool uses yellow to highlight parent overrides. To set the background
color, refer to “Setting Fonts and Colors” on page 41. In addition to choosing this highlighting
color, you can review and modify the overall color scheme Constraint Manager uses to
highlight constraint violations like errors and cautions. These are just a couple examples of how
the tool uses cell highlighting to indicate data conditions.
Moving Nets Between Constraint Classes

When moving a net to another constraint class, the tool might identify constraint differences
between the two objects. This is because the tool considers each constraint value for the net to
be an override if the net value is not the same as the value in the new constraint class.
A net that has no overrides in its current constraint class can easily have many overrides in its
new constraint class. Depending on how you have configured the tool, it either keeps all
differences, changes them all, or asks you to make a choice for each difference.
Blank Cells at the Constraint Class Level are not Considered When
Determining Overrides
An override is defined as a value that is different from a value at a higher level of hierarchy.
When moving a net into a different constraint class, Constraint Manager does not consider an
empty or blank constraint class level cell as a value when determining if there is an override in
its hierarchy.
Choosing From Among Change Impact Actions
For example, you have a net that defines # Vias Max at the net level. You then move the net into
a constraint class that has a blank entry for this constraint. Doing so preserves # Vias Max at the
net level if you instruct the tool to change the old value. This is because the tool does not
interpret the blank entry as a value. Therefore, the net level value is not an override.

Constraint Manager should not change your data without you being warned about it. For this
reason, the tool either prompts you or presents you with a warning dialog box. Depending on
how you have the tool configured, you can disable the warning dialog box.
The purpose of the warning dialog box is to alert you to the hierarchical impact of changing a
parent constraint value. As explained in “Overview of Constraint Hierarchy and Overrides” on
page 54, parent and child objects are linked for the purpose of quickly and accurately defining
constraints and values for groups of nets through constraint classes, net classes, and other
parent/child object relationships.
Whether you have a parent object expanded or collapsed in the spreadsheet, the tool always
identifies overrides in a child object if you attempt to change a value at the parent-constraint
level. Constraint Manager propagates the new value (or not) based on how you have it
configured. In some cases, the tool does not propagate the new value due to the requirement of a
specific rule. For a list of these, refer to “Required Propagation Rules That Constraint Manager
Maintains” on page 58.
Constraint Manager brings up this warning dialog box if all of these conditions are met:
• Your setting for the Change Impact Dialog is not set to “Always prompt user for all
values.”
• You have not already enabled the “Don’t ask me again in this session” check box in the
warning dialog box.
• You are changing more data than what you typed in.
If you are presented with this warning dialog box, to go ahead with the change based on your
settings, click OK. To instead not make the change, click Cancel.
Caution
The primary purpose of this warning dialog box is to make you aware that a value you are
changing has hierarchical impact. The secondary purpose is to let you know that a
Constraint Manager setting controls how the tool handles overrides. To modify the Change
Impact Dialog setting, refer to “Setting General Options” on page 40.
For example, you have a constraint class that defines # Vias Max as 3. Out of the five nets in the
constraint class, you define this constraint as 5 for two of them. A change to the value at the
constraint-class level would cause the tool to use this setting to determine whether you still want
to keep the override value of 5 for the two nets that use the value.
Figure 3-1. Constraint Class With Two Constraint Overrides
Choices regarding hierarchical propagation are not limited to net classes and constraint classes.
Any parent/child relationships that include overrides at the child level causes Constraint
Manager to use the Change Impact Dialog setting if you attempt to change a parent value.
Prerequisites
• The procedure is only valid if the tool automatically displays the Change Impact Prompt
dialog box. The tool does this if you have it configured to ask you to choose which child
values will take on a new parent value. To modify this setting, refer to “Setting General
Options” on page 40.
Procedure
1. In the Change Impact Prompt dialog box, for each child object, select one of the
following:
• Change to new value — Replace the child value with the new parent value.
• Keep current value — Retain the child value.
2. Click OK.
Note
You can also do the following:
• To use the selected action for all child objects that are left, click to activate the check
box: “Do this for all remaining constraints”
• As you use the Change Impact Prompt dialog box, you can stop reviewing or
changing values by clicking Exit at any time. Doing so retains any changes that you
have made thus far, but skips any child objects that remain.
Required Propagation Rules That Constraint Manager Maintains
Required Propagation Rules That Constraint

Manager Maintains
There are some cases where the Change Impact dialog box setting is irrelevant. This is due to
object and constraint relationships that Constraint Manager must maintain in order for certain
aspects of the constraint set to be valid.
Refer to the list of required rules and their explanations:
• Net Class value for differential pairs and electrical nets — This value must be the
same for physical nets that are part of an electrical net, electrical nets that are part of a
differential pair, and the differential pair.
Constraint Manager maintains this relationship on the Nets page.
There is an exception to this rule if an electrical net contains multiple physical nets. In
this case, each physical net can have a different Net Class value from the electrical net
and differential pair.
• Topology Type value for differential pairs and electrical nets — This value must be
the same for physical nets that are part of an electrical net, electrical nets that are part of
a differential pair, and the differential pair.
There is an exception to this rule if an electrical net contains multiple physical nets. In
this case, each physical net can have a different Topology Type value from the electrical
net and differential pair.
• Length value for differential pairs and electrical nets — This value must be the same
for physical nets that are part of an electrical net, electrical nets that are part of a
differential pair, and the differential pair.
• Length Match value for differential pairs — This value must be the same for
electrical nets that are part of a differential pair, and at the differential pair level.
• Trace Width Minimum, Typical, and Expansion values — Constraint Manager
enforces mathematical relationships among these constraints. For example, Minimum
cannot be greater than Typical, and Expansion cannot be less than Typical.
Organization of Constraints Into Pages

The tool organizes constraint data into spreadsheet pages to group constraints by type.
Organization of Constraints Into Pages
Here is a description of each spreadsheet page:
• Trace and Via Properties — Board-layer transmission constraints like Via

Assignments, Routing, and Trace Width.
• Clearances — Same-layer clearance constraints like Trace to Trace, Trace to Pad, and
Pad to Via.
• Nets — This spreadsheet page contains the largest number of constraints, which fall into
these categories:
o Lengths — Length constraints like Minimum, Maximum, Match, and Tolerance.
o Differential Pairs — Differential pair constraints like Separation Distance and
Differential Spacing.
o Main — The most commonly modified constraints like Net Class and Topology
Type.
o Power Nets — Power-supply net constraints like Supply Voltage.
o Routing — Routing constraints like the Maximum Stub Length and # Vias Max.
o Template — Net template constraints like Name and Status.
• Parts — Component constraints.
• Constraint Templates — Superset of constraints that includes many of those from each
spreadsheet page for reuse as intellectual property for other nets and designs. For more
information, refer to “Constraint Template Creation and Reuse” on page 147.
Spreadsheet Page Selection
Spreadsheet Page Selection

You can select the active spreadsheet page in a variety of ways. In addition, you can use the
Filters - Groups toolbar to filter a spreadsheet to display just a certain group of constraints. For
example, display just differential pair constraints on the Nets page. By doing so, you can more
easily focus on the constraints related to differential pairs.
Selecting a Spreadsheet Page Using the Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Selecting a Spreadsheet Page Using the Navigator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Displaying Only Specific Constraint Types on a Spreadsheet Page . . . . . . . . . . . . . . . . 61
Displaying All Constraint Types on a Spreadsheet Page . . . . . . . . . . . . . . . . . . . . . . . . . 61
Selecting a Spreadsheet Page Using the Tabs

Constraint Manager shows a tab for each spreadsheet page. The documentation refers to each
spreadsheet page by its tab name.
Here are some tips for customizing and using the display of spreadsheet tabs, which in turn give
you access to individual spreadsheet pages:
• Constraint Manager gives you the ability to display just certain tabs so that you can
show and hide tabs as needed. To do so, right-click the listing of tabs, then click to show
or hide specific tabs. You can also click to show All Tabs, or click to show just Default
Tabs.
• If you can not see all spreadsheet tabs, use the arrow buttons to scroll through the tabs (if
this setting is enabled). You can also resize the right edge of the tab listing to increase or
decrease the amount of space the tool uses to display tabs.
Figure 3-2. Selected Spreadsheet Page: Nets
Procedure
At the bottom of the spreadsheet pane, click a spreadsheet tab.
Selecting a Spreadsheet Page Using the Navigator

You can click within the Navigator to select among the different spreadsheet pages that are
available in Constraint Manager. For example, after clicking Constraint Classes, the Nets page
becomes active.
Clicking further into the hierarchy in the Navigator limits the display to a specific object in the
relevant spreadsheet. For example, if you click a constraint class in the Navigator, the Nets
Spreadsheet Icons Overview
spreadsheet displays just that constraint class and its nets. This type of row limiting occurs for
each object type.
Tip
Constraint Manager gives you the ability to display just certain nodes of the Navigator so
that you can show and hide nodes as needed. To do so, right-click within the whitespace of
the Navigator, then in the listing of nodes, click to show or hide specific nodes. You can also
click to show All Nodes, or click to show just Default Nodes.
Procedure
Click within the hierarchy of the Navigator to view the relevant spreadsheet page.
Displaying Only Specific Constraint Types on a

Spreadsheet Page
Use this procedure if you want to focus on a specific subset of constraints on a spreadsheet
page.
Procedure
1. Select the page of interest.
2. At the top of the spreadsheet page, click the Filters - Groups toolbar dropdown (also
known as “Constraint Groups”) and then select a constraint type.
Displaying All Constraint Types on a Spreadsheet Page

After you restrict a spreadsheet page to show a certain subset of the total constraints, you can
return the view to its default display, which is all constraints.
Procedure
2. Click the Filters - Groups toolbar dropdown, then click All.
Spreadsheet Icons Overview

As you work with the spreadsheet, you will notice that each row includes an icon. Each icon
indicates a different type of design object. The tool provides icons to make design-object
identification clear and efficient.
Resizing Spreadsheet Columns and Rows
Table 3-1. Design Object and Spreadsheet Icon Correlation

Design Object Spreadsheet Icon
Board layer
Clearance rule
Component
Component instance
Constraint class
Constraint template
Differential pair
Electrical net
Net class
Physical net
Pin
Pin pair
Power net
Note
The tool adds ^^^ to the end of net names on the Nets page to indicate electrical nets that
include two or more physical nets.
Resizing Spreadsheet Columns and Rows

As you work with constraint data, you may find it useful to resize specific columns or rows. For
example, you can reduce the size of a column to provide more display room for other columns
on the same page.
Prerequisites
• To resize rows, you must display the leftmost column of the spreadsheet The tool shows
it automatically if you enable cross probing (Setup > Cross Probing), or if you have
row numbering turned on (Setup > Settings > Display).
Procedure
1. In the columns heading of a spreadsheet, or the leftmost cell of a spreadsheet row, hover
your mouse over the vertical or horizontal separation between cells until the mouse icon
changes to the resize icon.
Zooming the Display of Spreadsheet Pages
Figure 3-3. Row and Column Resizing
2. Click and hold and then drag to increase or reduce the size of the column or row.
3. After resizing the column or row, release the mouse button.
Note
To reset the columns or rows on a spreadsheet page to their default widths or
heights, from the View menu, click Reset Column Widths or Reset Row Heights.
Zooming the Display of Spreadsheet Pages

You can increase and decrease the magnification level of spreadsheet pages. Because each
spreadsheet page stores its own zoom level, you can customize the magnification level of
specific pages.
Tip
To quickly set the same magnification level for all spreadsheet pages, use the Setup >
Settings menu selection. Using the Initial Zoom Level option, you can globally control the
initial magnification level.
Procedure
2. Do any of the following:
• To increase magnification, press F7.
Expanding and Collapsing Spreadsheet Rows
• To decrease magnification, press F8.

• To set magnification to 100%, press F6.
Expanding and Collapsing Spreadsheet Rows

You can expand and collapse the rows on a spreadsheet page. You can expand or collapse just
the selected rows, all rows, or a single row.
Procedure
• Expand or collapse a single spreadsheet row — Click the + or - symbol to the left
of the row.
• Expand multiple spreadsheet rows — Use these steps:
i. If you want to expand only specific rows, use Ctrl-click to select each row the
tools precedes with a + symbol.
ii. From the View menu, do one of the following:
• To expand selected rows, click Expand, then click Selected.
• To expand all rows, click Expand, then click All.
• Collapse multiple spreadsheet rows — Use these steps:
i. If you want to collapse only specific rows, use Ctrl-click to select each row the
tool precedes with a - symbol.
ii. From the View menu, do one of the following:
• To collapse selected rows, click Collapse, then click Selected.
• To collapse all rows, click Collapse, then click All.
Sorting Spreadsheet Pages

You can sort nets and objects listed on a spreadsheet page in both ascending and descending
order. Because this function is based on spreadsheet context, a sort includes all or most child
rows, or just the parent rows. For example, sorting the Clearances page does not affect the order
of board layers.
Procedure
Sorting Spreadsheet Pages

• To sort in ascending order, on the Sort toolbar, click .
• To sort in descending order, on the Sort toolbar, click .
Tip
You can also right-click within the spreadsheet, click Sort, then click Ascending
or Descending.
Deletion of Constraint Values
Deletion of Constraint Values

You can delete constraint values at the constraint level, object level, and design level. When
deleting values at the constraint level, you select individual constraint cells that you previously
defined but want to clear. When deleting values at the object level, you delete the entire set of
constraints for a given object and all child objects that are part of the parent object.
Deleting Constraint Values at the Constraint Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Deleting Constraint Values at the Object Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Deleting Constraint Values at the Design Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Deleting Constraint Values at the Constraint Level

When you want to delete one or more constraint values at the cell level, Constraint Manager
gives you the ability to do so through both the keyboard and the mouse.
Procedure
1. On the spreadsheet, click a constraint cell to select the value for deletion.
Tip
To select multiple constraint values, use Ctrl-click and Shift-click.
2. Press the Delete key; or, right-click, then click Delete.

Results
One or more constraint cells are now empty or reset to their default value (if one exists).
Deleting Constraint Values at the Object Level

You can delete constraint values at the object level to quickly empty the set of defined
constraints for a net, constraint class, or net class. For example, after making many erroneous
constraint modifications to a net, you can quickly clear the new constraint values.
If deleting constraint values at the object level, it is important to understand that the tool clears
all removable constraints within an object’s hierarchy. For instance, clearing a constraint class
results in deleting all constraint values for each net within the constraint class. This is in
addition to any constraints defined at the constraint-class level.
If you delete constraint values at the object level, the tool does not clear any default values. This
method of deletion is often times thought of as a way to easily “reset” a net or other object.
Procedure
1. In the first column of the spreadsheet, right-click a design object, then click Clear
Constraints.
Constraint Value Copy-and-Paste Between Sessions
2. In the message box that appears, optionally activate one or more check boxes, if
appropriate, then click Yes.
Results
The tool deletes all non-default constraint values for an object (and its child objects).
Deleting Constraint Values at the Design Level

You can delete constraint values at the design level to quickly empty the set of defined
constraints for the entire design. If you delete all constraint values, the tool does not clear
default constraint values.
Prerequisites
• Your invocation of Constraint Manager must be the only session.
Procedure
1. Choose Data > Clear > All Constraints.
2. In the confirmation dialog box that appears, note the location of the design backup that
the tool will create, then click Yes only if you are sure you want to clear all user-defined
constraints from the design.
Results
• The tool deletes all non-default constraint values for the design.
• You can restore all constraint values to their previous state. To do so, from the Tools
menu, click iCDB Project Backup.
Constraint Value Copy-and-Paste Between

Sessions
If you have multiple invocations of Constraint Manager loaded, you can copy and paste
spreadsheet values between the same spreadsheet of the other invocation.
Because the tool does not restrict the cells between which you can copy and paste, it is
important to make sure you select identical cells of the appropriate spreadsheet page. You can
use the copy and paste on all spreadsheet pages, but you cannot use it within tables and cells of
dialog boxes.
Removing Unused Rules
Removing Unused Rules

You can have the tool identify unused rules throughout a design and then remove some or all of
them. If you remove an unused rule, the tool deletes all constraint values that are part of the rule.
In this context, rules are objects like net classes, clearances, and package type rules. You
typically remove unused rules if using a finished design as the starting point for a new design.
Note
You cannot use undo to restore unused rules. To restore them, from the Tools menu, click
iCDB Project Backup.
Rules and objects you can remove in this way:
• Classes (constraint and net)

• Clearance rules
• Templates
Procedure
1. Choose Data > Clear > All Unused Constraints.
By default, the tool selects all unused rules for removal. In addition, the Unused Rules
add-in indicates if the design is not synchronized. Although you are not required to
synchronize the design, the add-in reports more accurate results if you synchronize the
front-end and back-end constraint sets. To do so, forward annotate or back annotate.
• To learn why the tool considers a rule to be unused, hover over it to view tooltip text.
• To cross probe to a rule, click it. If this is not possible, the tool updates the Output
window to tell you how to access the rule.
• Toggle the check box for a rule.
• Toggle the check boxes for all rules by clicking the check box in the column
heading.
3. When you are ready to remove all checked rules, click Clear.
Results
• The tool updates the row of each unused rule to show the result of the removal. The
Result column indicates whether the tool was able to remove a rule. Optionally, to clear
removed rules from the add-in, click Refresh.
Searching for Constraints
• The Output window provides a link to a log file containing details about the removals. If
the tool was unable to remove one or more rules, you can refer to the log file for more
information.
Searching for Constraints

You can search for data within spreadsheet pages to locate specific nets or select multiple nets
for the purpose of performing group operations. By doing so, you can quickly find or select
certain nets within large, complex design structures. You can also search spreadsheets for
precise constraint data.
When searching for nets, you can step through the list of all nets based upon the search criteria
you provide. If selecting multiple nets, you can filter the display of Constraint Manager data
based upon a net-name or constraint-value criterion.
Tip
To quickly search for the first occurrence of any text string, on the Find toolbar, type the text
string into the text box, then click the button to the left. To find the next occurrence, click
the search button again.
Procedure
1. From the Edit menu, click Find; or, on the Find toolbar, click .
2. In the Find dialog box in the “Find what” field, type the text you want to find.
For example, to find and step through all nets of the form /N$2050 - /N$2059, use /
N$205? as your search string. To find and step through all nets that begin with /N$2,
type /N$2*. Note that this is not a regular-expression search example.
3. Specify the direction in which you want to search by selecting Forward or Backward.
4. To view additional search preferences, click More, then use these options:
• To search a page other than the current page, click the Page dropdown, then click to
specify your search scope.
• To search sequentially by row or column, click the Search dropdown, then click to
specify the direction.
• To search constraint values, or constraint comments, click the Look In dropdown,
then click to specify the appropriate criterion.
• To match the exact capitalization or case sensitivity of the search string, click to
enable Match Case.
• To find only full matches and not partial ones (for example, you do not want
searches for “100” to find “1000” and “10000”), click to enable Match entire cell.
Filtering Spreadsheet Data
• To enable searching of spreadsheet rows that are not expanded, click to enable Drill-
down searching.
• To search using wildcard characters, select Use wildcards.
• To search using regular expressions, click to enable Use regular expressions, but
keep the following in mind:
o Standard wildcard characters (for example, * and ?) behave much differently in
that they include matching—or not—to the preceding character. For example, a
regular expression search for “n*t” would match “at”, “nt”, “net”, “about”, and
many other words that begin with any character and end with “t”. Conversely, a
regular expression search for “n?t” would only match “at”, “nt” and “net” of the
results of the asterisk example.
o * matches 0 or more of the preceding character, not just any character unless you
precede it with the period character (“.”).
o ? matches 0 or 1 of the preceding expression.
o There are additional wildcard characters that you can use.
o You can search using ranges of characters.
5. After you finish configuring your search, click Find Next or Find All.
• When you search with Find Next, the tool highlights the first relevant cell. To find
the next cell that matches your criteria, click Find Next again.
• When you search with Find All, Constraint Manager augments the dialog box to
show a table of all matching cells. You can cross probe between the table of search
results and the spreadsheet by clicking a cell in the results table.
6. When finished, click Close.

You can filter a spreadsheet page to restrict the display of data rows to just those that match a
string criteria. After you perform an initial filter, you can further restrict the display of rows by
cumulatively filtering the remaining rows. After you finish working with a subset of nets, you
can reset the spreadsheet page to display all data rows.
Filtering is useful if you want to focus on a specific group of data rows without worrying about
modifying constraint data on rows that do not apply to a specific subset. It is common to use
filtering as a precursor to assigning nets to classes. By restricting the spreadsheet to only the
nets that match a filter string, you can quickly select a group of nets without having to select
around other nets.
Note
Constraint Manager filters just spreadsheet rows that are expanded. To filter all rows of a
spreadsheet page, from the Filters menu, click to enable Drill-down Filtering.
Procedure
• From the Filters menu, click Enabled.
• With the Filters - Main toolbar enabled (View > Toolbars > Filters - Main), from it,
click .
Note
Make sure that Filter mode is now on. If it is, the spreadsheet is augmented to
include an additional row at the top for typing filter strings.
2. In the column for which you want to filter spreadsheet data, click the dropdown in the
filter cell, then do one of the following:
• Use a default filter — Select from among Sort Ascending, Sort Descending, (All),
(All Non Empty), and (All Non Default).
• Create a custom filter — Click (Custom...), then perform these steps:
i. In the Custom Autofilter dialog box, click the dropdown in the box to the left,
then click to specify how the custom filter will apply to the filter string you use.
ii. In the box to the right, type the filter string you want to use.
iii. For additional filtering options, click the More button, then specify any of these
options:
• To match case sensitivity, click to enable Match case.
• To toggle cumulative mode filtering, click the appropriate check box.
• To toggle filtering of non-expanded spreadsheet rows, click Drill-down filter-

ing.
• To instead use a regular expression, click to enable the appropriate check box,
then type a regular expression.
iv. After you finish configuring your filter, click Apply.
3. To reduce the display of spreadsheet data (rows) by adding another column criterion,
return to step 2. You can also filter a column more. For example, after filtering the Nets
spreadsheet Constraint Class/Net/* column to display a subset of rows based upon net
name, you can cumulatively filter the subset by net name again.
You must enable cumulative mode before you can filter using additional criteria. To do
so, from the Filters menu, click Cumulative Mode. As a result, the Cumulative Mode
menu item includes a check mark.
Tip
If you filter out the parent row of an object, but need to re-enable it, you can do so by
right-clicking the child row, then clicking Show Parent.
4. To exit filtering mode when finished, on the Filters - Main toolbar, click .
Examples
Example of Filtering the Nets Page to Display Only Electrical Nets (^^^)
In this example, you are interested in displaying only true electrical nets on the Nets
spreadsheet. Net names can often times be quite long. Because the true electrical net identifier is
appended to the end of a net name (^^^), filtering to display just these nets ensures that you are
working on only electrical nets.
Use these steps:
1. With the Nets spreadsheet page active, expand the constraint class that you want to work
in.
2. With filtering enabled, in the filter row of the Constraint Class/Net/* column, click the
filtering dropdown, then click (Custom...).
3. In the Custom Autofilter dialog box, set the filter to equals, then in the box to the right,
type: *^^^
4. After you finish setting the custom filter, click Apply.
The spreadsheet reduces to display just electrical nets that are part of the (All) constraint
class.
Filtering the Spreadsheet by Row Type
Filtering the Spreadsheet by Row Type

When working on spreadsheet pages, you can specify the row types that Constraint Manager
displays. For example, if the active spreadsheet page is Parts, you can choose to display only a
subset of data rows based on what you want to see (part pins, components, and/or components
pins).
It is important to note that each spreadsheet page has one or more default row types that the tool
always displays (for example, the constraint classes row of the Nets page is always displayed).
Figure 3-4. Filters - Levels Toolbar Showing Parts Page Selections
The illustration shows the Filters - Levels toolbar from the perspective of the Parts spreadsheet
page being active. The toolbar changes the display of active buttons depending on the
spreadsheet page you are on. As you can see, all four of the parts selections (on the right) are
enabled. A blue box around each active row type indicates this state.
Procedure
• From the Filters menu, click Levels, then click to choose the row types you want to
display.
• With the Filters - Levels toolbar enabled (View > Toolbars > Filters - Levels), from
it, click a button to toggle the display of a specific row type. The tool displays an
outline around those that are active.
• With the Filters - Main toolbar enabled (View > Toolbars > Filters - Main), from it,
click . In the Filter Levels dialog box, click to toggle the levels that you want to
display, then click Apply.
Results
The spreadsheet shows only certain rows (this includes rows that you cannot toggle).
Eventually, you may want to change the display back to a more common view, which is one of
the following:
• All Row Types — From the Filters menu, click Levels, then click All.
• Only Default Row Types — From the Filters menu, click Levels, then click Reset.
• Only Row Types That You Cannot Toggle — From the Filters menu, click Levels, then
click None.
Resetting a Spreadsheet to its Default View
Resetting a Spreadsheet to its Default View

After you work on a spreadsheet page for one or more sessions, you may find it necessary to
return it to its default view.
Resetting a spreadsheet page results with the following:
• Only default levels are shown (Filters > Levels > Reset).
• Filtering is turned off (Filters > Enabled).
• Filters - Groups toolbar dropdown is set to All.
• All expanded rows are collapsed.

Procedure
1. Make the spreadsheet page you want to reset the active one by clicking its tab.
2. From the View menu, click Reset View.
Results
Just the active spreadsheet page is reset.
Concurrent Constraint Entry With Other Users
Concurrent Constraint Entry With Other Users

Constraint Manager gives you the ability to work effectively with other users who are editing
the same constraint set, whether on the front-end or back-end. It does this by making it easy for
you to see which constraint values other users have changed, or are in the process of changing.
It also provides a way for you to communicate the rationale for your constraint changes by
giving you the ability to create constraint cell comments that all other users can read. For more
information, refer to “Constraint Value Commenting” on page 78.
Overview of Constraint Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Showing Indication of Remotely Changed Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Overview of Constraint Locks

If working in any concurrent design environment, the spreadsheet automatically locks
constraint values or objects that are being changed by another user in a separate instance of the
tool. After the user finishes making their change, the lock is removed, and the value is once
again editable by other users.
Cells in Constraint Manager can also become locked due to actions performed within a tool
from which you can launch it (for example, PADS Designer). For example, two designers can
be working on the same design, though one has front-end Constraint Manager open and the
other PADS Designer. Actions taken in schematic tool can cause cells in Constraint Manager to
become locked. Conversely, actions taken in Constraint Manager can cause the same behavior
to occur in the schematic tool.
In the example, two designers are modifying constraints from within Constraint Manager
sessions launched from their layout tool. Because both users are working on the same back-end
constraint set, the tool displays an indication of locks in the other user’s environment as each
applicable constraint or object is in the process of modification. In this case, there is a single
locked cell.
Showing Indication of Remotely Changed Constraints
Example 3-2. Locked Constraint Cell
Tip
To determine which user has a constraint or object locked, hover your mouse cursor over the
locked constraint or object in the spreadsheet. The tooltip that is displayed shows the user
account that currently has the constraint or object locked for editing.
Automatic Removal of Constraint Locks

A constraint or object lock is always removed if any of the following occur:
• The user who initiated the change finishes their modification(s).

• The maximum locking time is exceeded. To learn how to modify this setting in your
environment, refer to “Specifying Design Configuration Preferences” on page 37.
• All clients are disconnected.
• The server is down.
Showing Indication of Remotely Changed

Constraints
If multiple users are working on the same constraint set, you can have your Constraint Manager
session update in real time to highlight the changes of other users. You do so by enabling
indication of remotely modified cells. This causes the tool to highlight the background color of
such cells. The example illustrates this using the default highlight color.
Showing Indication of Remotely Changed Constraints
Figure 3-5. Indication of a Concurrently Modified Constraint Value
Tip
You can change the background color Constraint Manager uses to indicate remote
modifications. For more information, refer to “Setting Fonts and Colors” on page 41.
Another way that Constraint Manager helps ensure effective concurrent design is by
temporarily locking a constraint or object if it is being modified in a parallel session. For more
information, refer to “Overview of Constraint Locks” on page 75.
Prerequisites
• Concurrent design is enabled through availability of the appropriate license.
Procedure
1. From the View menu, click Remotely Modified Data.
2. Click to activate Enable Indication.
Results
Your Constraint Manager session is now updating in real time to show you all constraint
changes being made in any concurrent sessions.
(Optional) To clear all of the current cell highlighting, from the View menu, click Remotely
Modified Data, then click Refresh. At this point, only new modifications will show.
Constraint Value Commenting
Constraint Value Commenting

You can comment on constraint values for multiple reasons. You might do so to help yourself
remember why you made certain changes to a constraint, or to make the rationale for a change
clear to other designers. In addition, you could use commenting to provide feedback on
constraint changes made by other designers. This could be the function of a supervisory role.
After you create a constraint comment, you can refine it or delete it. You can also view the
constraint comments of other users. To view all constraint comments against a constraint set,
you can run a report that lists them.
Adding Comments to Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Editing Constraint Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Deleting Constraint Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Viewing Constraint Comments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Adding Comments to Constraints

You can add comments to individual cells on any page of the spreadsheet. Doing so is
especially useful if you want to help ensure that another user does not change a constraint value
that is important to your individual goals as a designer.
Prerequisites
• The Comment toolbar must be visible if you want to use Comment toolbar buttons
instead of right-click actions. Ensure that View > Toolbars > Comment is enabled.
Procedure
• On the spreadsheet, right-click a cell, then click Insert Comment.
• On the Comment toolbar, click .
2. In the Comment dialog box, type your comment in the text field.
3. Click Apply or OK.
Results
The cell is updated to include a red marker in its upper-right corner to indicate that you have
added a comment to it. The illustration shows an example of this marker.
Editing Constraint Comments
Figure 3-6. Constraint Cell With Comment Marker
In this case, the user could have provided an explanation for why they set the minimum length
value to 1400 th instead of 1000 th (like the other values).
Editing Constraint Comments

You can edit existing constraint comments as needed for the purpose of updating them. Instead
of editing one, in some cases it may make more sense to delete the comment and create a new
one.
Prerequisites
• You must have created the constraint comment you want to modify.
Procedure
1. On the spreadsheet, do one of the following:
• Right-click a cell that includes a comment, then click Edit Comment.
• Click a cell that includes a comment, then on the Comment toolbar, click .
2. In the Comment dialog box, modify the comment in the text field.
3. Click Apply or OK.
Results
The content of the comment is updated.
Deleting Constraint Comments
Deleting Constraint Comments

You can delete constraint comments that you created, as well as those of other designers. If
deleting constraint comments that you did not create, it is important that you have an agreement
in place for such practice.
It is not recommended that any user delete the comments of another user without there being an
understanding, process, or guideline for if doing so would be acceptable.
Prerequisites
Procedure
• Right-click a cell that includes a comment, then click Delete Comment.
• Click a cell that includes a comment, then on the Comment toolbar, click .
Results
The constraint comment is erased.
Viewing Constraint Comments

You can view constraint comments to see constraint “notes” that you and other users have
provided. Constraint Manager gives you a few ways to view comments. Each method is mostly
relevant to the number of constraint comments you want to view, whether one comment,
several, or all of them.
Prerequisites
• The Comment toolbar must be visible if you want to use Comment toolbar buttons.
Ensure that View > Toolbars > Comment is enabled.
Procedure
• To see a single comment, hover the mouse cursor over a cell that includes a
comment.
• To cycle from one comment to the next, on the Comment toolbar, click (next) or
(previous), then hover the mouse cursor over the cell to see the comment.
Viewing Constraint Reference Information
• To generate a report that lists all comments, from the Output menu, click Report
Comments.
Viewing Constraint Reference Information

This manual includes a full constraint reference. You can access it directly from the constraint
spreadsheet using a right-click command.
As an example, the constraint reference graphic for the differential pair constraint Differential
Spacing is shown.
Figure 3-7. Constraint Reference Illustration for Differential Spacing
Procedure
On the constraint spreadsheet, right-click a constraint cell, then click Constraint Help.
Related Topics
Constraint Reference
Viewing Design Statistics

You can generate a detailed report of design statistics that includes object, connectivity, and
constraint information. The report includes totals for each data point (for example, total
constraints) and top-level information like snapshot, block, and software installation.
Procedure
From the Output menu, click Design Statistics.
Checking Constraints Synchronization

You can check synchronization between the front-end constraint set and the back-end constraint
set. Doing so gives you the ability to see differences between constraint values for specific
objects. The report only shows objects with values that do not match between the constraint
sets.
Checking Constraints Synchronization
Prerequisites
• You are not using a remote development flow.
Procedure
From the Output menu, click Check Constraints Synchronization.
Results
In the event that synchronization checking fails, ensure that you are properly connected to
appropriate client systems. You can also view the report for more information.
Constraint Diagnostics
Constraint Diagnostics
You can both check and correct constraint values using CES Diagnostics.
Checking Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Correcting Constraint Manager Diagnostics Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Listing of Constraint Manager Diagnostics Tests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Checking Constraints
You can check constraints to verify the data integrity of your local constraint set. This is
especially useful if starting with a migrated design. Constraints checking provides information
and errors for multiple aspects of design-object relation and net assignment.
Procedure
1. From the Tools menu, click CES Diagnostics.
2. To view the report that was created, refer to the Output window, CES Diagnostics tab.
Results
The report shows the results of many diagnostics tests. Each test indicates whether the data has
passed or failed. In the event that a test has failed, and the error is automatically fixable by
Constraint Manager, the report shows a link at the bottom that gives you the ability to
automatically fix all errors that fall into this category.
Tip
You can cross probe from the report to problematic design objects by clicking a link on any
available error rows.
Correcting Constraint Manager Diagnostics Errors

After you check constraints integrity, the status bar of the tool displays one of two types of
exclamation points if your constraint set has integrity problems.
They are:
• Red exclamation point — Contact customer support to get help fixing these problems.
You will need their assistance.
• Yellow exclamation point — Attempt to fix these problems yourself by using Constraint
Manager documentation to make changes based on the reported errors.
When your constraint set does not have any integrity problems, the status bar does not display
an indicator. It only displays an indicator in the event that there is problematic data. It is
important to understand that Constraint Manager may display some errors that are not fixable
Listing of Constraint Manager Diagnostics Tests
through the tool. Instead, you would have to do so through your host tool, or another piece of
software. In these cases, the error report tries to make it clear that the error must be fixed outside
of Constraint Manager.
Procedure
1. Familiarize yourself with the errors.
• Fix all automatically fixable errors — In the event that you have errors that can be
fixed automatically by Constraint Manager, you can click a link at the bottom of
error report to do so.
Note
After you have Constraint Manager fix errors, it will reload if necessary. This is
to ensure that the tool shows the correct constraint data based on changes that
occurred during the process of making automatic fixes.
• Fix errors that you must fix manually — In the event that you have Constraint
Manager errors that can only be fixed manually in the tool, you should use
Constraint Manager documentation to make the appropriate fixes. In some cases, the
error will provide a link to the exact documentation you must use to fix the error.

Each of the diagnostics tests Constraint Manager performs is described in the table. This
information is in the tooltip the tool displays if you hover the mouse over a specific test in the
report.
Table 3-2. Constraint Manager Diagnostics Tests

Test Purpose
CES database initialization Checks if Constraint Manager database is correctly
initialized.
Net class name unique Checks if net class name is unique on given level of
hierarchy.
Constraint class name unique Checks if constraint class name is unique on given level of
hierarchy.
Layer consistency Checks if layers contain all required and valid data.
Layer in all net classes Checks if all net classes include the full listing of board
layers.
Component valid Checks if all components are valid in terms of references to
pins.
Table 3-2. Constraint Manager Diagnostics Tests (cont.)

Test Purpose
Pin in net and component Checks if pin belonging to net also belongs to component.
Component name unique Checks if all component names are unique within the
design.
Physical net unique Checks if physical net name is unique.
Pin reference to net valid Checks if pin has a proper reference to physical net.
All used constraint classes Checks if all constraint classes used by nets and differential
valid pairs exist in the design.
All used net classes valid Checks if all net classes used by nets and differential pairs
exist in the design.
Differential pair with two Checks if all differential pairs have two existing and
electrical nets different electrical nets.
Electrical nets belonging to Checks if electrical nets belonging to differential pair have
differential pair assigned to the same net class.
the same net class
Unique pin pairs in electrical Checks if pin pairs in electrical net are unique.
net
Power net topology Checks if power net has the proper topology.
Constraints consistency Checks consistency of constraints. This test also reports
empty constraints.
Default objects Checks if standard and default objects exist for schemes,
clearance rules and net classes.
Mapping of schematic and Checks if all schematic nets and physical nets are mapped
physical nets correctly.
Reference designator vs. Checks if attribute 'Ref Designator' is the same as
component name Constraint Manager component name.
Attributes vs. constraints When component attributes are defined on the schematic,
checks if the corresponding constraints (Technology,
Value, and Series) exist in the database.
Via span valid Checks if the via span is valid.
Unique virtual pin names Checks if virtual pin names are unique in the design.
All used package clearance Checks if each package clearance-type rule is fully defined.
type rules valid
Physical net topology Checks if physical net topologies are consistent. This test
also checks for virtual pins in complex topologies.
Table 3-2. Constraint Manager Diagnostics Tests (cont.)

Test Purpose
Nets constraint values Checks the integrity of constraints defined on nets.
consistency
PCB Actuals Comparison With Constraint Values
PCB Actuals Comparison With Constraint

Values
Your layout system generates actuals data as a result of routing. By comparing actuals for nets
and objects against constraint values for those same nets and objects, you can determine how
well a design meets the guidelines of its constraint set.
Validating PCB Actuals Against Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Updating Actuals Displayed in Constraint Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Clearing Actuals From the Spreadsheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Viewing All Constraint Violations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Constraint Violation Revision Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Validating PCB Actuals Against Constraints

You validate PCB actuals (generated through AutoActive) against constraint data to determine
whether the router is obeying specific constraint values. For example, you can see whether the
routed length of a net is within its minimum and maximum length constraints.
Note
The Constraint Manager actuals menu selections referenced in this section are only
available in sessions launched from a back-end design system.
Procedure
If you do not have Constraint Manager configured to automatically update actuals on start-up,
from the Data menu, click Actuals, then click Update All to show actuals on the spreadsheet.
(If you do not have automatic display of actuals enabled, you must perform this step
each time you launch Constraint Manager.)
Tip
To make the display of actuals a seamless part of your back-end or front-end
Constraint Manager session, there are several settings you can enable. For more
information, refer to “Specifying Other Preferences” on page 46.
Results
When constraint validation is available, you can easily see which constraints are resulting in
actuals that are approaching or exceeding a constraint threshold, or moving beyond a minimum
and maximum constraint range.
To make such distinctions clear, Constraint Manager backlights actual spreadsheet fields with
one of two colors, which respectively indicate whether an actual is out of range, or close to
Updating Actuals Displayed in Constraint Manager
being out of range. During the process of setting up the tool, you can specify the backlight
colors used by the tool.
Figure 3-8. Constraint Manager Color-Codes Actuals to Indicate Violations
Updating Actuals Displayed in Constraint Manager

If users are performing engineering efforts simultaneously in both Constraint Manager and the
router to which Constraint Manager is connected, you may want to periodically update/refresh
the actuals that are in Constraint Manager to reflect changes to actuals produced by the router.
Procedure
• Update selected actuals — Use these steps:
i. On a spreadsheet page, click, Ctrl-click, or Shift-click to select one or more nets.
ii. From the Data menu, click Actuals, then click Update Selected.
• Update all actuals — From the Data menu, click Actuals, then click Update All.
Clearing Actuals From the Spreadsheet

You may want to clear actual values the tool displays on one or more spreadsheet pages.
Procedure
• Clear actuals from the current spreadsheet page — From the Data menu, click
Actuals, then click Clear This Page.
• Clear actuals from all spreadsheet pages — From the Data menu, click Actuals,
then click Clear All Pages.
Viewing All Constraint Violations
Viewing All Constraint Violations

Aside from locating constraint violations within specific pages of the spreadsheet, you can
quickly generate a list of all actuals that are producing constraint violations.
The Constraint Violations dialog box is modeless, so you can conveniently keep it on screen for
prolonged periods of time. To update its display, click Refresh.
Procedure
1. From the Data menu, click Constraint Violations.
2. In the list of Constraint cautions and violations, refer to the Constraint and Object
columns to determine problematic constraints.
3. (Optional) Do any of the following:
• To display just violations, click to enable the “Show only violations” check box.
• To hide any revised constraint rows, click to enable the “Show only unrevised”
check box.
• To mark a constraint as revised, click to enable its Revised check box. (You cannot
mark all data types as revised. For a list of restrictions, refer to “Constraint Violation
Revision Restrictions” on page 90.)
Tip
To do this in the spreadsheet, right-click a constraint cell, click Mark As, then
click Revised.
• To cross probe to the spreadsheet row to which a constraint caution or violation

refers, click a list row. To move up or down one row in the violations list while cross
probing, click or .
Constraint Violation Revision Restrictions
Constraint Violation Revision Restrictions

The Constraint Violations dialog box gives you the ability to mark specific caution or violation
rows as “Revised” so you can keep track of problems you correct in the spreadsheet. It is not
possible to mark every row in this way, though.
You cannot mark these data types as “Revised”:
• Actuals and other read-only values

• Assignments (constraint class and net class)
• Hierarchical paths
• Layer indices
• Object types (parallelism rules and power nets)
• Pin counts
• Rule names
Related Topics
# Pins
Hierarchical Path
Index
Net Class
Power Net
Constraint Change Undo and Redo
Constraint Change Undo and Redo

Constraint Manager supports sequential undo and redo, both for single and multiple changes,
and undo of all constraint changes you make in a session.
Rolling Back and Undoing All Constraint Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Rolling Back or Redoing Specific Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Supported Undo/Redo Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Rolling Back and Undoing All Constraint Changes

You can revert all constraint changes made at any time during your current Constraint Manager
session. This includes all commands for which undo/redo is supported. For example, modifying
constraint classes and net classes, adding clearance rules, and creating differential pairs.
For a full listing of supported actions, refer to Table 3-3 on page 92. The procedure in this topic
affects all changes that you can revert. For reverting just specific changes, refer to the
appropriate topic in this section.
Note
When rolling back constraint changes, the forward and back annotation indicator lights for
your design flow do not reflect these undo actions. For example, after you make a single
change in back-end Constraint Manager and then rollback that change, your back-end system
still indicates that you need to perform back annotation (though you do not).
Procedure
1. From the File menu, click Rollback Changes.
2. (Optional) To also rollback user interface changes, clear the check box.
3. In the Rollback Changes dialog box, click Rollback.
4. Use the dialog box to confirm the action.
Results
The Status column displays “Pending,” “In Progress,” “Conflict,” or “Restored” for each row.
Each entry starts out as pending. When the tool successfully rolls back a change, the field
displays “restored.” For undo actions that take longer to process you see “in progress” displayed
before the tool moves them to a resolved state. If the tool cannot undo a change due to conflicts,
the Status field indicates this condition.
Rolling Back or Redoing Specific Changes
Rolling Back or Redoing Specific Changes

In addition to rolling back all changes, the tool also supports an enhanced interface for undoing
or redoing multiple changes, beginning with the most recent supported action.
For example, after making three consecutive constraint changes, you can quickly use the
standard Constraint Manager GUI to undo all three changes without pressing Ctrl-Z multiple
times. This approach also gives you a visual indication of the most recent changes that you can
undo.
When undoing or redoing changes, the tool also reverts all actions following the selected action.
For example, if you create three net classes, beginning with net class A and ending with net
class C, undoing the creation of net class B results in the deletion of net class C as well.
Procedure
1. On the General toolbar, click the dropdown next to (undo) or (redo).
2. In the list of changes you can undo or redo, hover over one or more changes, then click.
Figure 3-9. Last Three Actions Selected for Undo
Supported Undo/Redo Actions

You can roll back, undo, and redo certain Constraint Manager changes.
Refer to the table for a complete list.
Table 3-3. Supported Undo/Redo Actions
Design Object Actions
Clearance rule Add, remove, and rename.
Constraint Add, change, propagate,
copy, and paste.
Viewing and Reverting to Parent Cell Values
Table 3-3. Supported Undo/Redo Actions (cont.)

Design Object Actions
Constraint class Net assignment to class, add,
remove, and rename.
Differential pair Add, remove, and auto-
assign.
Net class Net assignment to class, add,
remove, and rename.
Pin pair Auto pin-pair, manual pin-
pair, and remove.
Viewing and Reverting to Parent Cell Values

You can view the parent value of a constraint cell to determine the assigned value at the next,
upper level of hierarchy.
For example, if you have a constraint class that includes a large number of nets, and many of the
values for a specific constraint differ from the value at the constraint class level, you can view
the value at that level without having to change your place on the spreadsheet.
In addition to viewing parent values, you can also revert an overridden value to its parent value
if it is appropriate to do so. In the event that you have filtered the listing of spreadsheet rows,
you can also show a parent row if it is hidden from view.
Procedure
1. Right-click the spreadsheet cell of interest.
• To see what the cell value is at the next, upper level of hierarchy, click Show Parent
Value. As a result, the tool updates the Output log window to include a new line of
text that displays this value.
• To revert the cell value to the value of the parent cell, click Reset to Parent Value.
• In the event that you are using row filtering and the row for a parent cell is hidden,
you can click Show Parent to enable display of the hidden parent row.
Saving Constraint Changes

After you make constraint changes through the spreadsheet and other constraint-entry
mechanisms of Constraint Manager, the tool saves them automatically in your front-end or
back-end constraint set; however, the changes may not persist unless you perform a save in the
tool from which you launched Constraint Manager (for example, your layout software).
Saving Constraint Changes
Note
Some design tools automatically save your design data (for example, the schematic tool).
Depending on the tool from which you launched Constraint Manager, you may not have to
explicitly save. Refer to the documentation for your design tool for information about saving
design changes in your invocation tool.
Procedure
1. Finish making constraint changes for the session.
• After you exit Constraint Manager, in the invocation tool, save your design (if
required).
• When working in a Constraint Manager session launched from the back-end, at the
bottom-right corner of your PCB layout tool, click the rightmost status indicator to
load the changes into the back-end, then save your design in the PCB layout
software.
Chapter 4
Net Class Creation
You use net classes to group nets and objects for the purpose of efficiently defining similar
physical requirements in Constraint Manager. Like constraint classes, the number of net classes
you create for a design typically depends on design complexity, which can include the number
of board layers, technology types, and other factors.
When grouping nets into classes, you can group based on function, level of importance within a
design, and more. If grouping nets based on function, you might classify them to differentiate
power and ground nets from signal nets. If grouping nets based on their level of design
importance, you could classify them to differentiate critical nets in a design from non-critical
nets.
If you want to create a net class that includes the constraint definitions of an existing net class,
you do so by creating a net class from an existing class instead of creating a new net class.
Note
Be aware of the following:
• Initially, the tool assigns all nets to the (Default) net class.
• You are limited to two levels of net class hierarchy (a parent net class can have child net
classes, but no additional net class hierarchy below the child net classes).
Creating Net Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Adding Nets to a Net Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Creating a Net Class From an Existing Net Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Deleting Net Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

You create net classes to group specific types of nets for the purposes of defining board-level
physical/manufacturing constraints and assigning clearance rules between nets in the classes.
Net class constraints are located on the Trace & Via Properties spreadsheet page. Although you
create clearance rules on the Clearances spreadsheet, you assign them elsewhere.
Net Class Creation
Figure 4-1. Net Classes Created for a Design
In the example, the ddr3_group* classes (ddr3_group0, ddr3_group1, ddr3_group2, and

ddr3_group3) all contain nets that are of the same technology type and function, but they have
slightly different current-carrying needs or sensitivity to crosstalk. For this reason, unique net
classes are being used instead of a single ddr3_group net class. Each of the net classes accounts
for the differences in width and spacing.
Video
• Make a net class.

• Clone a net class.
• Rename a net class.
Net Class Creation
• Modify physical constraints.
Procedure
1. In the Navigator, right-click Net Classes, then click New Net Class.
Note
To create a net class under an existing net class, in the Navigator, right-click a net
class, then click New. You are limited to two levels of hierarchy. The
recommendation is to use hierarchy sparingly. Doing so helps to reduce complexity.
2. Replace the default name “<user>_New” with a name for the net class, keeping the
following in mind:
• Net class names must be 127 characters or less.
• You can use spaces in net class names.
• It is a best practice to use a name that reflects the purpose of the class. For example,
if creating a net class that will contain only signal nets, replace “New” with “Signal
Nets”.
Results
• You can now move nets into the net class.
• The new net class initially takes on the constraint values of the (Default) net class if it is
a top-level net class. If it is a child net class, it takes on the constraint values of its parent
net class.
• You can rename the net class if needed. To do so, in the Navigator, expand Net Classes.
Right-click the net class, click Rename, type a new name, then press Enter.
• You can create child classes under a top-level net class as you need to, but use hierarchy
sparingly.
Net Class Creation

After you create a net class, you must define the group of nets that should comprise the net
class. By default, each net class that you create contains no nets.
Note
Each net can belong to one net class.
Video
• Filter the spreadsheet.

• Select filtered nets and move them to a different net class.
• Make net class changes from the Navigator.
• Enable the display of physical nets in the Navigator to easily see the nets in a net class.
Procedure
• With the Trace & Via Properties spreadsheet page active, from the Edit menu,
click Assign Nets to Classes.
• In the Navigator, expand Net Classes, right-click a net class, then click Assign Nets.
Tip
then click Assign Net(s) to Net Class. In the Select Net Class dialog box, select
a net class, then click OK. If using this option, you do not need to finish this
procedure.
2. In the Assign Physical Nets to Net Class dialog box, specify the net class from which
you want to select nets by clicking the Source Net Class dropdown, then clicking a net
class.
Net Class Creation
For example, if you are adding nets to your first custom class you can select from all
nets in the design by specifying the (Default) class as the source.
3. Specify the net class to which you want to add nets by clicking the Target Net Class
dropdown, then clicking a net class.
4. Under the nets in source net class listing, specify the nets that you want to add to the
target class.
Tip
Tip
Results
The tool moves the nets to the target the net class; these nets are no longer part of the source
Examples
Example of Adding All Available Nets in a Source Net Class to a Target Net Class
Use these steps:
Example of Swapping All Nets in One Net Class With All Nets in Another Net Class
Use these steps:
Net Class Creation
Creating a Net Class From an Existing Net Class
Creating a Net Class From an Existing Net

Class
You can create a new net class from an existing class to quickly create one that includes the
same constraint definitions as the source net class. For example, after creating a base net class
for most signal nets in your design, you can duplicate it, and then modify the constraint
definitions in the new class.
Tip
It is important to remember that creating a net class from an existing net class copies
constraints and not nets. After you create a copy, make sure you assign the appropriate nets.
Procedure
1. In the Navigator, expand Net Classes, right-click a net class, then click Clone.
2. Right-click the name of the clone, click Rename, then type a different name.
3. Specify the group of nets that comprise the new class by moving nets to this net class.
4. Modify the physical constraint values defined in this class such that they are appropriate
for the nets you added to this class in the previous step.
Deleting Net Classes

If you delete a net class, the tool removes the class object and constraint values, but not the
contents of the class itself (such as nets and differential pairs). Before deleting a net class,
Constraint Manager prompts you to verify that you selected the appropriate class.
Procedure
1. In the Navigator, expand Net Classes.
• Right-click a net class, then click Delete.
• Click a net class, then press Delete.
Results
After you delete a net class, the tool moves any nets that were assigned to it to the (Default) net
class. This includes child net classes. The nets return to the (Default) net class instead of moving
up one level of hierarchy to the parent net class.
Chapter 5
Constraint Class Creation
You use constraint classes to group nets for the purpose of efficiently defining similar electrical
requirements in Constraint Manager. The number of constraint classes you create for a design
typically depends on design complexity, which can include the number of nets, technology
types, and other factors.
If you want to create a constraint class that includes the constraint definitions of an existing
constraint class, you do so by creating a constraint class from an existing class instead of
creating a new constraint class.
Note
You cannot create constraint class hierarchy beyond a single level (parent constraint classes
cannot have child constraint classes).
Creating Constraint Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Adding Nets to a Constraint Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Creating a Constraint Class From an Existing Constraint Class . . . . . . . . . . . . . . . . . . 104
Deleting Constraint Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

You create constraint classes to group specific nets and then define electrical and signal
integrity constraints such as topology types and stub lengths.
Constraint class constraints are located on the Nets spreadsheet page and Noise Rules page.
Video
• Create a constraint class.

• Add a differential pair to the constraint class.
Adding Nets to a Constraint Class
• Change some length constraints for the differential pair.
Procedure
• In the Navigator, right-click Constraint Classes, then click New Constraint Class.
• On the Nets spreadsheet page, right-click a constraint class, then click New Top
Level Class.
2. Replace the default name “<user>_New” with a name for the constraint class. Keep the
following in mind:
• Constraint class names must be 256 characters or less.
• You can use spaces in constraint class names.
• A best practice is to use a name that reflects the purpose of the constraint class. For
example, if creating a constraint class that will contain only signal nets, replace
“New” with “Signal Nets”.
Results
• You can now move nets into the constraint class.
• The new constraint class initially takes on the constraint values of the (All) constraint
class. This includes both top-level net classes and child net classes.
• You can rename the constraint class if needed. To do so, in the Navigator, expand
Constraint Classes. Right-click a constraint class, click Rename, type a new name,
then press Enter.

After you create a constraint class, you can assign nets to it. By default, each constraint class
you create contains no nets.
Note
Each net can belong to one constraint class.
Procedure
• With the Nets spreadsheet page active, from the Edit menu, click Assign Nets to
Classes.
• In the Navigator, expand Constraint Classes, right-click a constraint class, then
click Assign Nets.
Tip
then click Assign Net(s) to Constraint Class. In the Select Constraint Class
dialog box, select a constraint class, then click OK. If using this option, you do not
need to finish this procedure.
2. In the Assign Nets to Constraint Class dialog box, specify the constraint class from
which you want to select nets by clicking the Source Constraint Class dropdown, then
clicking a constraint class.
For example, if you are adding nets to your first custom constraint class you can select
from all nets in the design by specifying the (All) constraint class as the source.
3. Specify the constraint class to which you want to add nets by clicking the Target
Constraint Class dropdown, then clicking a constraint class.
4. (Optional) Limit the source and target net listings to show just physical nets. To do so,
click to enable Use physical nets.
5. Under the nets in source constraint class listing, specify the nets you want to add to the
target class.
Tip
Tip
Creating a Constraint Class From an Existing Constraint Class
Results
The tool moves the nets to the target constraint class; these nets are no longer part of the source
Examples
Example of Adding All Available Nets in a Source Constraint Class to a Target Constraint
Class
Use these steps:
1. In the Assign Nets to Constraint Class dialog box, specify a source constraint class, then
specify a target constraint class.
Example of Swapping All Nets in One Constraint Class With All Nets in Another Constraint
Class
Use these steps:
1. In the Assign Nets to Constraint Class dialog box, specify a source constraint class, then
specify a target constraint class.
Note
If you create a new constraint class while the Assign Nets to Constraint Class dialog
box is displayed, the drop down lists are updated appropriately.
Creating a Constraint Class From an Existing

Constraint Class
You can create a constraint class from an existing one to quickly duplicate the same electrical
and physical rules and use them as the starting point for a new constraint class.
For example, after creating a constraint class that defines many rules for signal nets, you can
duplicate it, add specific nets to it, and then modify the rules that were copied over from the
original constraint class to make them appropriate for another group of nets.
Note
If creating a constraint class from an existing constraint class, the nets in the existing
constraint class remain in that constraint class.
Procedure
1. In the Navigator, expand Constraint Classes, right-click a constraint class, then click
Clone.
Deleting Constraint Classes
2. Right-click the name of the clone, click Rename, then type a different name.
3. Specify the group of nets that comprise the new class by moving nets to this constraint
class.
4. Modify the constraint values defined in this class such that they are appropriate for the
nets you moved to this class in the previous step.

If you delete a constraint class, the tool removes the class object and constraint values, but not
the contents of the class (such as nets and differential pairs). Before you delete a constraint
class, Constraint Manager prompts you to verify that you selected the appropriate class.
Procedure
1. In the Navigator, expand Constraint Classes.
• Right-click a constraint class, then click Delete.
• Click a constraint class, then press Delete.
Results
After you delete a constraint class, the tool moves any nets that were assigned to it to the (All)
constraint class.
Chapter 6
Physical Rule Definition
You define physical rules to constrain spacing between objects on a board. You can do so at the
net class level and the layer level. You define most physical rules through the Clearances
spreadsheet page and the Trace & Via Properties spreadsheet page.
Viewing Clearance and Trace Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Specifying General Clearance Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Specifying Trace Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Defining Via Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Clearance Rule Set Creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Assigning Class-To-Class Clearance Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Deleting Class-To-Class Clearance Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
3D Clearance Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

View clearance and trace constraints to see the minimum distances that must be maintained
between objects, allowable widths for traces, layers enabled for routing, and more.
Video
• View clearance constraints defined as part of the “(Default Rule)” clearance rule.
• Observe trace width constraints defined as part of the “(Default)” net class.
• Identify system-default constraint values.
Specifying General Clearance Rules
Specifying General Clearance Rules

You specify general clearance rules to define clearance values between design objects that you
do not specify through the Clearances spreadsheet page. Unlike spreadsheet clearance
constraints, you specify general clearance rules irrespective of net class relationships.
In this flow, you can define a single general clearance rule (Placement Outline to Placement
Outline). It allows a minimum value of 0 and a maximum value of 1 in. It provides a default
value of 10 th.
Procedure
1. Do one of the following.
• On the Clearances toolbar, click .
• From the Edit menu, click Clearances, then click General Clearances.
2. In the General Clearance Rules dialog box, modify the value for Placement Outline to
Placement Outline.
3. After you finish, click OK.
Specifying Trace Constraints

You can specify trace constraints to which nets must adhere. You can simultaneously define
trace rules for all board layers for nets in a net class, or you can do so individually for each
board layer. You can define values such as minimal, typical, and expansion trace widths.
Procedure
1. On the Trace & Via Properties spreadsheet page, expand the (Default) net class, or a
unique net class that you created previously.
2. Define trace constraints in any of the following ways:
• To simultaneously define trace rules for all board layers, in the net class name row
(for example, (Default)), specify Route, Trace Width, and Differential Spacing rules.
For example, to specify a Trace Width Minimum value of 8 th for all board layers
for nets that are a part of the (Default) net class, type 8 in the Minimum field, then
Defining Via Assignments
press Enter. Constraint Manager updates each board layer to include this Minimum
Trace Width value.
• To individually define trace constraints for each board layer, in the appropriate
board layer row (for example, SIGNAL_1), specify Route, Trace Width, and
Differential Spacing rules.
For example, to specify a Trace Width Expansion value of 12 th for board layers 1
and 2 of the (Default) net class, in the SIGNAL_1 and SIGNAL_2 rows, type 12 in
the Expansion field.

You can assign a specific via to a net class when the default via is not suitable. When defining
via assignments, you can choose from the default, none, or any available vias. For all via
assignments other than the default, the spreadsheet indicates the specification with "Custom" in
the Via Assignments cell.
Procedure
1. Select the Trace & Via Properties spreadsheet page.
• In the Via Assignments cell of the net class for which you want to define or modify a
via assignment, click .
• Click a net class spreadsheet row, then from the Edit menu, click Via Assignments.
The Via Assignments dialog box displays. It shows a row for each via span defined in
the layout tool.
3. In the Via Assignments dialog box, in the Net Class Via column, click the pulldown to
specify a different via assignment, then click Apply or OK.
Note
You can do any of the following:
• If defining multiple via assignments simultaneously, to set all to the default
assignment, click Set to Default.
• Use the dropdown button to change the Net Class you want to modify.
Clearance Rule Set Creation
Clearance Rule Set Creation

You can create clearance rule sets and then define their constraints to specify spacing
requirements between objects on a board. These constraints are located on the Clearances
spreadsheet page.
Note
The (Default Rule) clearance rule set contains the default clearances for a design. When
assigning clearance rule sets between net classes, the values in (Default Rule) are used by
default.

Defining Clearances for a Rule Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Defining SMD Clearance Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Defining Board Edge Clearances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Defining Copper Clearances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

You can specify clearance rules to which net objects must adhere. You can define clearance
rules such as Trace to Pad, Pad to Pad, and Via to SMD Pad.
Different net classes often require unique design rules in order for nets within a class to
maintain integrity during signal transmission. By creating clearance rule sets, you can address
the unique requirements of the different technology types in a design.
Video
• Create clearance rules.

• Modify the constraints in a clearance rule.
Procedure
1. In the Navigator, right-click Clearances, then click New Clearance Rule.
Defining Clearances for a Rule Set
2. Replace the default name “<user>_New” with a unique name for the clearance rule set.
Defining Clearances for a Rule Set

You define clearances for a rule set to specify the amount of spacing you need between objects
on the same board layer.
Prerequisites
• You enabled the Clearances spreadsheet page by choosing View > Tabs > Clearances.
Procedure
1. Click the Clearances spreadsheet tab.
2. Make your definitions in any of the following ways:
• To simultaneously define clearance rules for all board layers, in the clearance rule
set name row (for example, (Default Rule)), specify any appropriate clearance rules.
For example, if your distance unit is thousandths, to specify a Trace To Trace
separation of 15 for all board layers, in the (Default Rule) row, type 15 into the Trace
field of the Trace To heading, then press Enter. Constraint Manager updates each
board layer to include this Trace to Trace value.
• To individually define clearance rules for each board layer, in the appropriate board
layer row (for example, PHYSICAL_2), specify any appropriate clearance rules.
For example, if your distance unit is centimeters, to specify a Pad To Trace
separation of 10 for board layer 1, in the (Default Rule) row, type 10 into the Pad
field of the Pad To heading, then press Enter.
Note
Clearance rules are not applied to your design until you create associations
between specific net classes. To do so, refer to “Assigning Class-To-Class
Clearance Rules” on page 22.
Defining SMD Clearance Rules

If your design includes surface mount devices (SMD), you can define spacing requirements
between the pads of these devices and conductive board elements (for example, traces and vias).
SMDs are also commonly referred to as surface mount technologies (SMT).
Prerequisites
Defining Board Edge Clearances
Procedure
2. Define these constraints for an entire clearance rule set, or individually for each board
layer of a rule set:
• “Trace To SMD Pad” on page 179
• “Via To SMD Pad” on page 183

You can define clearance constraints that specify the minimum required distance between the
edge of a printed circuit board and other objects like traces, pads, and vias.
Prerequisites
Procedure
2. (Optional) To more easily focus on just these constraints, in the Filters - Groups toolbar
dropdown, select Board Edge.
3. Define these constraints for an entire clearance rule set or individually for each board
• “Board Edge To Trace” on page 184
• “Board Edge To Pad” on page 185
• “Board Edge To Via” on page 186
• “Board Edge To Copper” on page 187
• “Board Edge To SMD Pad” on page 188
Defining Copper Clearances

You can define clearance constraints that specify the minimum required distance between
copper objects (copper, copper pours, and plane areas) and other objects like traces, pads, and
vias.
Prerequisites
Procedure
2. (Optional) To more easily focus on just these constraints, in the Filters - Groups toolbar
dropdown, select Copper.
3. Define these constraints for an entire clearance rule set or individually for each board
• “Copper To Trace” on page 189
• “Copper To Pad” on page 190
• “Copper To Via” on page 191
• “Copper To Copper” on page 192
• “Copper To SMD Pad” on page 193

After you create clearance rule sets, you can assign class-to-class clearance rules that maintain
certain clearances between specific net classes. By doing so, you can apply the rules you
defined in a clearance rule set to one or more pairs of net classes.
You use class-to-class rules to maintain very precise clearance requirements between specific
net objects. These requirements usually relate to electrical, safety, or manufacturability
concerns. For example, high voltage nets in a design that need certain spacing based on the
voltage level of each net.
Also, as you make these assignments, it is important to be aware of the following:
• Class-to-class clearance rules are obeyed between net classes to which you explicitly
assign them. Assignments do not include sub-level net classes. Any child net classes
under a parent net class do not obey the clearance rules of the parent net class.
• When selecting net classes to associate with a clearance rule, you can quickly specify all
other net classes by using the (All) column. Although this can be useful, the (All)
column does not provide for granular rule assignment between a net class and other net
classes.
• Cells that you do not explicitly define (empty cells) do not use (Default Rule).
• The tool makes it possible to assign more than one clearance rule between two net
classes. In these cases, the tool uses the following priority to pick one:
o Net class to net class
o Net class to (All)
o (All) to (All)
For example, if you assign a rule between (All) and (Default), and a different rule
between (Default) and (Default), based on the priority, the tool uses the clearance rule
you assigned between (Default) and (Default).
Prerequisites
• You created the clearance rule sets you want to assign between net classes. For more
information, refer to “Creating Clearance Rule Sets” on page 21.
Video
• Enable the Clearances toolbar.

• Assign a clearance rule between a net class and (All) net classes.
• Assign a clearance rule between two specific net classes.
Procedure
2. Populate cells in these ways:
• One cell at a time — Click within an editable cell to select the rule to use between
two specific net classes (for example, (Default) and (Default)).
• Assign the same rule to multiple cells — Use Ctrl-click and Shift-click to select a
group of cells. After selecting the last cell, continue holding Ctrl or Shift while you
use the dropdown to make the rule selection.
• Copy and paste — Select one or more cells, press Ctrl-C, click a single cell, then
press Ctrl-V. For example, you could select all of the cells in the (All) column and
then quickly copy them into the (Default) column.
As you make changes, the dialog box updates to show them by highlighting the
background of these cells. This makes it easy for you to keep track of all your
changes.
Deleting Class-To-Class Clearance Rules
Figure 6-1. Highlighting Shows Cell Changes
3. Continue making rule assignments between net classes.
Tip
4. After you finish, click Apply or OK.
Deleting Class-To-Class Clearance Rules

You can delete class-to-class clearance rule assignments as needed. If doing so, you can delete a
single rule, multiple rules, or all rules.
Procedure
• Delete a single rule assignment — Click a row, then press Delete.
• Delete multiple rule assignments — Use Ctrl-click or Shift-click to select multiple
cells, then press Delete.
• Delete all rule assignments — Click .
Tip
3. After you finish deleting assignments, click Apply or OK.
3D Clearance Specification
3D Clearance Specification
3D clearances are generally the XY axis and Z axis distance requirements of the mechanical
designer. By defining them in Constraint Manager, you can check 3D clearances in your layout
system to ensure that no hazards are identified due to insufficient spacing between mechanical
and assembly objects.
By default, 3D clearances have a general definition that is used for all mechanical and assembly
objects. These default values are an Optimal XY of 10 th and an Optimal Z of 5 th. Minimum
XY and Minimum Z values are not defined by default.
You can define unique definitions for Optimal XY, Optimal Z, Minimum XY, and Minimum Z
to specify smaller or larger clearances between certain pairings of mechanical and assembly
objects. Before defining unique 3D clearances or changing the general definitions, it is
important to understand the difference between the two sets of values:
• Minimum — Lowest clearance value that does not produce an error.

• Optimal — Lowest clearance value that does not significantly affect production yield.
Figure 6-2. Relationship Between Minimum and Optimal 3D Clearance Values
Figure 6-2 depicts the difference between minimum and optimal values. Based on example
values of 5 th and 10 th, checking in the layout system would result with the following:
• Any clearance of 10 th or above would pass.

• Any clearance between 5 th and 9 th would issue a warning.
• Any clearance below 4 th would produce an error.
You define mechanical and assembly clearances through the “3D Clearances” add-in. It is
important to understand that clearances you define to control mechanical and assembly
constraints do not overlap the definitions of any other clearances that you can define in
Constraint Manager.
Defining 3D Clearances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

3D Clearance Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Defining 3D Clearances
Defining 3D Clearances
You can define 3D clearances to specify the XY and Z constraints that should be checked by
your layout system to ensure that there is sufficient spacing between certain pairings of
mechanical and assembly objects.
Note
Minimum XY and Z clearances cannot be larger than Optimal XY and Z clearances. The
same is true in reverse. If you type a minimum clearance that is greater than the optimal
clearance, or an optimal clearance that is less then the minimum clearance, both clearances
change to the new value. Constraint Manager does this automatically to keep you from creating
conflicts in the constraint set.
Prerequisites
• You are using an invocation of Constraint Manager launched from your layout system.
Procedure
1. From the Edit menu, click Clearances, then click 3D Clearances.
2. In the 3D Clearances add-in, in the Any to Any row, do the following:
• Modify the values for Optimal XY and Optimal Z (if needed).
• Specify values for Minimum XY and Minimum Z (if needed).
3. To define unique clearances for a specific 3D object relationship, do the following:
a. Click Add Clearance, then select the appropriate pairing (for example, Bond Wire
to Assembly).
b. In the row of the 3D clearance, change the values for both Optimal XY and Optimal
Z. (These values start out as the current definitions in the Any to Any row). You
must define values for both of the Optimal cells (or leave both blank).
c. If needed, specify values for Minimum XY and Minimum Z. (If defined, these
values start out as the current definitions in the Any to Any row). You must define
values for both of the Minimum cells (or leave both blank).
Note
To reset a 3D clearance to the “Any to Any” values, click it, then click Delete
Clearances. Also, you can use Ctrl-click to highlight multiple rows.
4. Repeat step 3 to define unique 3D clearances as needed.

In the example illustration, most 3D objects use the default clearances, but there are
several that have unique definitions.
3D Clearance Descriptions
Figure 6-3. General and Unique 3D Clearance Definitions
Results
The 3D clearances for the design are available for checking in your layout system after you
bring any pending changes into that system.
To access: Edit > Clearances > 3D Clearances
Each 3D clearance defines a distance constraint between two 3D objects. To understand the
relationships that you define with a specific 3D clearance, it is important to have a clear
understanding of each of the 3D objects that are part of a pairing.
Note
Note the following:
• You must be using an invocation of Constraint Manager launched from your layout
system.
• The minimum value for all 3D clearances is 1 nm.
• The maximum value for all 3D clearances is 1 in.
Refer to the objects and clearances tables.

Table 6-1. 3D Objects
Object Description
Active Board The current PCB project open in Constraint Manager.
Assembly The physical packaging (enclosure) in which the Active
Board (PCB) resides.
Board Edge Cavity wall or edge in the current Active Board.
Component Physical package placed within the layout system.
Table 6-1. 3D Objects (cont.)

Object Description
Mechanical One of the following:
• A layout system mechanical cell.
• An imported mechanical cell from an MCAD system.
PCB Assembly A PCB design exported from the layout system used for
multi-board validation.
Table 6-2. 3D Clearances

Clearance Description
Any to Any Default clearances between any 3D object to any other 3D
object:
• Optimal XY clearance of 10 th
• Optimal Z clearance of 5 th
Minimum clearance values are not defined by default.
Active Board to Assembly Clearances between the board and imported assemblies.
Component to Assembly Clearances between package cells and imported assemblies.
Component to Board Edge Clearances between package cells and cavity walls/edges.
Component to Component Clearances between package cells and other package cells.
Component to Mechanical Clearances between package cells and mechanical cells/
models.
Component to PCB Clearances between package cells and imported PCB
Assembly assembly designs.
Mechanical to Assembly Clearances between mechanical cells/models and imported
assemblies.
Mechanical to Mechanical Clearances between mechanical cells/models and other
mechanical cells/models.
Mechanical to PCB Clearances between mechanical cells/models and imported
Assembly PCB assembly designs.
PCB Assembly to Clearances between imported PCB assembly designs and
Assembly imported assemblies.
PCB Assembly to PCB Clearances between imported PCB assembly designs and
Assembly other imported PCB assembly designs.
Usage Notes
• To make a certain 3D clearance available for definition, click Add Clearance, then
select the clearance.
• To reset a certain 3D clearance to the “Any to Any” values, right-click it, then click
Delete Clearances. Also, you can use Ctrl-click to highlight multiple rows.
Chapter 7
Net Constraint Definition
You define net constraints to characterize electrical and physical requirements for specific nets
that are in a design. You can do so at the net and constraint class level. You define all net
constraints through the Nets spreadsheet page. Some examples of these types of rules are
topology constraints, length rules, and power-supply constraints.
Specifying General Net Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Topology Specification for Nets and Constraint Classes . . . . . . . . . . . . . . . . . . . . . . . . . 125
Defining Discrete Component Pin Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Length Rule Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Power-Supply Net and Constraint Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Specifying General Net Constraints

You can use Constraint Manager to specify general net constraints such as topology type and
the maximum number of vias that can be applied to a net. You can specify these constraints
individually for each net, or simultaneously by assigning a value to a constraint class.
When specifying a single constraint value for multiple nets through constraint class assignment,
each net in the constraint class is updated to include the single constraint value.
Tip
To view all constraints instead of only those that are of a specific type, in the Filters -
Groups toolbar dropdown, select All.
Procedure
1. With the Nets spreadsheet page active, from the Filters - Groups toolbar dropdown,
click Main.
Note
The tool also displays these constraints as part of the All group, but you may find
it easier to work with general net constraints when the Nets spreadsheet page displays
only them.
2. You can specify these constraints in one of two ways:

• To simultaneously define a constraint for all nets in a constraint class, in the
constraint class name row, change the cell value (for example, Net Class or
Topology Type).
The tool updates each net in the constraint class with the value.
• To individually define a constraint for a specific net, in the net row, change the cell
value.
Topology Specification for Nets and Constraint Classes
Topology Specification for Nets and

Constraint Classes
You can assign pre-defined and custom topology types to specific nets and constraint classes.
When you assign a topology type to a constraint class, all nets within the class take on the
topology type designation.
When you assign a topology type to a net or constraint class, or manually create a unique
topology ordering, you are defining the order in which the router etches transmission lines and
other physical mechanisms that aid in the propagation of electrical signals.
Note
MST topology type disregards the Stub Length Max constraint. You do not need to define
this constraint if the topology type is MST (Minimum Spanning Tree).
Topology Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Specifying Topology Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Changing Topology Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Topology Considerations
You should be aware of certain things before specifying topologies.
Differential-Pair Topology Definition

When specifying topologies for differential pairs, both nets that make up the pairing ultimately
take on the same topology definition. This is whether you define topology type for one net in the
pair, or at the differential-pair level. After you make your selection, the tool automatically
applies it at each level.
Note
Differential pairs are typically used for high-speed signals, so you will want to order and
constrain them as such. The layout system will not order a net that has been defined as MST
or Chained. It can route these types of topologies in anyway it needs to complete the route. For
this reason, you cannot select MST or Chained for differential pairs. The only valid topology
types are the remaining ones that force the layout system to order the route. This is a layout
limitation that Constraint Manager enforces.
Specifying Topology Type

You can assign pre-defined and custom topology types to specific nets and constraint classes.
The available pre-defined topology types are MST and Chained .
Changing Topology Type
Procedure
1. With the Nets spreadsheet page active, from the Filters - Groups toolbar dropdown,
click Main.
The tool also displays topology constraints as part of the All group, but you may find
it easier to work with topology constraints when the Nets spreadsheet page displays only
them.
Caution
If you change a topology type from Custom to a pre-defined topology type, the tool
deletes all pin pairs and virtual pins.

• In the spreadsheet row of the net or constraint class to which you want to assign a
topology type, click the Topology Type field, and then select a pre-defined topology
type (MST or Chained), or Custom.
• On the Topology toolbar, click a topology type button to specify a pre-defined
topology type ( or ), or a custom topology ( ).
Tip
To simultaneously specify a pre-defined topology type for multiple nets, use Ctrl-
click, then on the Topology toolbar, click a topology type button.
Related Topics
Topology Type
Changing Topology Type

Whenever you change the Topology Type constraint for a net or constraint class, any pin pairs
and virtual pins defined for the net, or individual nets in the constraint class, can be lost.
Changing topology type is not a concern if a net does not have unique definitions associated
with the topology type. In many cases, changing topology type is a simple action of just going
from one topology type to another.
In the event that changing the topology type will result with losses, Constraint Manager notifies
you of this fact, and gives you the ability to choose which Topology Type values to change to
the new value, and which to keep with their current value, therefore preserving the additional
definitions that are part of the present topology type. The procedure explains the options you
have in this case.
Defining Discrete Component Pin Pairs
Procedure
1. In the event that changing topology type will result with losses, the tool presents the Net
Topology Change dialog box. From it, select one of these options:
• Prompt before changing the topology for each net — Prompt individually for
each net to specify whether to keep the current topology type or change to the new
one. As a result, the tool displays a Yes/No dialog box for each affected net.
• Change the topology type for all nets without prompting — Change the
topology type for all affected nets.
• Disregard the topology change for all nets without prompting — Cancel out of
the change, preserving the existing topology type for all affected nets.
2. Verify your selection, then click OK.
Results
The tool changes or preserves the existing Topology Type value for one or more nets depending
on your choices.
Related Topics
Topology Type

If your design includes complex discrete components like resistor packs, you can define pin
pairs for such components. You can define these pin pairs manually, or instead automatically
based on dual-inline (DIP) and single-inline (SIP) pin pairing. Constraint Manager uses discrete
component pin pairs when it generates electrical nets.
Standard dual-inline components have pins on two sides of the component. Standard single-
inline components have pins on just one side of the component. The buttons you use for
automatic pin pair generation show the general appearance of standard DIP and SIP
components.
Note
If using automatic SIP pin pair generation for components with an odd number of pins (for
example, 9 or 15), the tool uses “1” as the start pin for each pin pair. Refer to Figure 7-3 for
an example.
Restrictions and Limitations

• The tool only supports automatic DIP pin-pairing for components that have an even
number of pins. For components with an odd number of pins, you must use automatic
SIP pin-pairing.
Prerequisites
• You must add the reference designator prefix your design uses for resistor packs (for
example, RP, RN, or both) to your settings for discrete component prefixes. To do so:
a. From the Setup menu, click Settings.
b. In the Settings dialog box, under Design Preferences, click Discrete Component
Prefixes.
c. In the Resistor cell, add your additional reference designators, then click OK.
For example, if both RP and RN are used as reference designators for resistor packs,
and R is the one used for resistors, this cell will now contain all three (for example:
R, RN, RP).
• The component must have more than two pins.
Procedure
1. On the Parts spreadsheet page, right-click a top-level discrete part that begins with the
reference designator prefix you added for resistor packs (for example, RN), then click
Create Component Pin Pairs.
2. In the Define Discrete Pin Pairs dialog box, do one of the following:
• To define pin pairs manually, click , then click within the Start Pin and End Pin
cells to select each pin. Repeat this step until you create all pin pairs.
Tip
To delete a pin pair, click its row, then click .
• To define pin pairs automatically, click or to create dual-inline (DIP) or single-

inline (SIP) pin pairings.
3. After you finish defining discrete pin pairs, click OK.
Examples
Example of Automatic DIP Pin Pair Generation
In this example, pin pairing for a dual-inline component is shown. In this case, automatic
generation results with low and high pins being paired (1 and 16, 2 and 15, and so on).
Figure 7-1. Automatic DIP Pin Pair Generation
Example of Automatic SIP Pin Pair Generation for Components With an Even Number of Pins
In this example, pin pairing for a single-inline component with an even number of pins is
shown. In this case, automatic generation results with pins being paired in sequence (1 and 2, 3
and 4, and so on).
Figure 7-2. Automatic SIP Pin Pair Generation (Even Pin Number)
Example of Automatic SIP Pin Pair Generation for Components With an Odd Number of Pins
In this example, pin pairing for a single-inline component with an odd number of pins is shown.
In this case, automatic generation results with all pins being paired with the first pin (1 and 2, 1
and 3, and so on).
Figure 7-3. Automatic SIP Pin Pair Generation (Odd Pin Number)
As you can see, the automatic DIP pin-pairing button ( ) is unavailable because the component
has an odd number of pins.
Length Rule Definition
Length Rule Definition

You use length rules to specify acceptable run lengths for traces that comprise a net. You can do
this in both basic and complex ways.
The common approach to defining these values for nets is to do so explicitly by providing
acceptable minimum and maximum values for a net. Design complexity and included
technology can dictate the need for more complicated approaches, though. For example, you
can match length rules among certain nets and specify a tolerance to provide room for
accommodating routing obstructions.
Specifying Length Rules for Nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Tolerance Routing of Nets Within a Constraint Class . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Specifying Maximum Length as a Percentage Above Manhattan Length . . . . . . . . . . . 132
Matching Length Rules Among Nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Matching Length Tolerance at the Constraint Class Level . . . . . . . . . . . . . . . . . . . . . . . 134
Specifying Length Rules for Nets

You can specify length rules for nets and differential pairs. Length is a physical rule that defines
the minimum and maximum trace distance between pins.
Note
The tool does not support the use of constants in Length Min and Length Max.
The router uses these minimum and maximum values to determine an acceptable trace distance
between the minimum and maximum range. For example, setting Length Min to 100 th and
Length Max to 300 th would give the router a range of 200 th between these minimum and
maximum values.
Procedure
1. With the Nets spreadsheet page active, in the Filters - Groups toolbar dropdown, click
Lengths.
Note
The tool also displays these constraints as part of the All group, but you may find
it easier to work with length constraints if the Nets spreadsheet page displays only them.
2. In the row of the net for which you want to specify length rules, use the available
constraint fields to define these values.
Tolerance Routing of Nets Within a Constraint Class
Note
If you want to include the length of vias that are part of a net, you can express those
inclusions by providing larger values that approximate the appropriate increases to
the overall length.
Related Topics
Length Min
Length Max
Tolerance Routing of Nets Within a Constraint

Class
Aside from defining general minimum and maximum length constraints for nets within a
constraint class, you can also assign a tolerance to an entire constraint class through use of the
Length tolerance (“Tol”) constraint.
Doing so constrains the router to match the lengths of all nets in the constraint class to within
the tolerance. This means the router has greater room to increase or decrease the length of trace
connections during routing operations. It is important to understand that the tool only displays
the tolerance at the constraint-class level, but uses it by default for all lower-level objects.
Specifying Maximum Length as a Percentage

Above Manhattan Length
You can use a net's Manhattan length plus a fixed percentage to specify the value used for the
maximum length constraint (Length Max). Manhattan length is calculated in your associated
PCB layout tool. You can specify a length of Manhattan plus 1% or greater (for example, 1%,
200%, 400%, or larger).
Note
Manhattan length values used in Constraint Manager are not validated. Manhattan actual
values depend on component positions on the PCB so it is not possible to constrain them.
Procedure
In the Length Max field, type a value of 1 or more, and follow it with a percentage symbol (%).
Examples
To use a length that is 120% of the Manhattan length, type 20%. To use a length that is 500% of
Manhattan length, type 400%. To specify a length as close as possible to the Manhattan length,
type 1%.
Matching Length Rules Among Nets

By creating match groups, you can use the length rules you define for a single net as the length
rules for multiple nets. You can also create match groups that do not include minimum or
maximum length rules, but instead are matched only within a range.
You accomplish length matching by setting up a match relationship, and optionally, a match
tolerance. The match feature of Constraint Manager length rule specification is especially useful
when you want to use the same length range for bus nets. If using match groups, all nets with the
same group identifier will be routed to the same length within the tolerance.
Be aware of these rules:
• Match group identifiers that include multiple characters must begin with an alphabetical
character. After which, you can use any combination of alphabetical characters,
numerical characters, and underscores.
• If you do not set a tolerance for the matched group, the tool uses the default tolerances
for the design. For information about how to review or set these values, refer to
“Specifying Design Configuration Preferences” on page 37.
Procedure
1. In the Match field of a physical net or pin pair row, type a match identifier (for example,
ADDR_line1).
2. (Optional) In the tolerance (“Tol”) field, specify a tolerance (that is, length range that
design objects must be within).
For example, to specify a tolerance of 100 th, type 100, then press Enter. All design
objects that use this match relationship must be within 100 th of each other.
3. For each net for which you want to match this length rule, in the Match field of each
row, type the match identifier (for example, ADDR_line1) you specified in step 1, then
press Enter.
Examples
Example of Matching Length Only by Tolerance
In this example, you are not concerned with the minimum and maximum length values to which
several nets will be matched, just the tolerance of the match group. As you can see in the
illustration, the length of each net must be within 50 th of each other.
Matching Length Tolerance at the Constraint Class Level
Figure 7-4. Matching Length by Just Tolerance
Matching Length Tolerance at the Constraint Class

Level
In addition to matching length rules among nets, you can also match length tolerance based on
constraint classes. Doing so gives you the ability to easily ensure that all nets within a constraint
class end up with length values that do not exceed a specific tolerance.
Matching length tolerance at the constraint class level does not limit you from creating tolerance
matches among specific nets. This is regardless of whether the nets are part of the same
constraint class. For example, after matching length tolerance within a constraint class to 100 th,
you can then create a match group with a tighter tolerance (for example, 50 th) and associate a
subset of nets within the constraint class with the match group. You can also associate nets that
do not belong to the constraint class with the match group.
Prerequisites
• You must have one or more constraint classes and nets assigned to constraint classes.
Procedure
1. Select the Nets spreadsheet page.
2. In the Length tolerance (“Tol”) cell of the constraint class of interest, type a tolerance
value.
Note
Length tolerance (“Tol”) cells are always editable for constraint classes. Unlike net
rows, you do not need to define a value in a Match cell in order to make a tolerance
(“Tol”) cell accessible.
Power-Supply Net and Constraint Definition

You can specify power-supply nets both manually and automatically to tell Constraint Manager
which nets in your design are power nets or ground nets. After you do so, you can define power-
supply constraints to characterize those nets. If you export nets from your layout system,
HyperLynx PI includes these constraints as part of the simulation.
Constraint Manager marks power-supply nets with the symbol . In the illustration, nets VCC
and GND are power-supply nets. They were automatically flagged by the tool as power-supply
nets because of their names (see “Net Names Constraint Manager Automatically Recognizes as
Power-Supply Nets” on page 135 for a full list of net names).
Example 7-1. Nets Marked as Power-Supply Nets
Note
If you mistakenly specify that a net is a power-supply net, you can easily set it back to be a
net.
Net Names Constraint Manager Automatically Recognizes as Power-Supply Nets . . . 135

Specifying Power-Supply Nets Automatically. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Specifying Power-Supply Nets Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Defining Constraints for Power-Supply Nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Changing Power-Supply Nets Back Into Nets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Net Names Constraint Manager Automatically

Recognizes as Power-Supply Nets
Constraint Manager recognizes these net names as power-supply nets by default:
• 0.9V
• +5V
• -5V
• +12V
• -12V
Specifying Power-Supply Nets Automatically
• GND
• GROUND
• VCC
• VDD
• VEE
• VSS
As such, it automatically enables the Power Net constraint for any nets that match these names.
In addition, the tool does the same thing for any nets that you defined as power-supply nets in a
previous version of the software. To set any other nets to power nets in the tool, you must do so
explicitly.

You can specify power-supply nets in your design automatically. Doing so can save you time if
your design includes many nets of this type. Through this approach you input search criteria to
match net names with a minimum pin count. If you are interested in only matching against net
names or pin count, you can set up your search to disregard the other criterion.
For example, your design could contain a large number of nets but just a few power-supply nets.
By searching on pin count only, you could isolate all nets that have a certain number of pins or
greater. Because power-supply nets usually contain a large number of pins, using a high number
would provide you with a list of nets that should include power-supply nets and a minimum of
extra nets (for example, complex nets with many pins).
Restrictions and Limitations

• Only nets with a Topology Type constraint value of MST can become power-supply
nets.
Procedure
1. From the Edit menu, click Power Nets, then click Auto Create Power Nets.
2. In the Auto Create Power Nets dialog box, in the Net Name field, type a search string to
use to find similar net names (for example, ENABLE?).
3. In the # Pins Threshold field, specify the minimum number of pins the nets must contain
(for example, 7).
4. Click . If any nets match your criteria, the Proposed power nets list displays them, and
they are automatically selected. In the example, the tool found two nets.
Figure 7-5. Proposed Power Nets
Note
This dialog box works in an additive manner, which means that you can type a new
search criteria, click , and any new matches are added to the existing list of results.
You can do this as many times as needed. In the example, the Net Name field was
changed to “ADDR*”.
Figure 7-6. Finding Additional Power Nets
Specifying Power-Supply Nets Manually
Tip
To start over and clear the entire list of Proposed power nets, click .
5. Of the nets in the list of Proposed power nets, make sure that only the check boxes of the
nets that you want to become power nets are selected. To select all proposed power nets,
click . To unselect them all, click .
6. Verify that your selections are correct, then click OK.

Results
The tool enables the Power Net constraint for each affected net. You can now define power-
supply constraints for these nets.
Related Topics
Power Net
Specifying Power-Supply Nets Manually

You can manually specify the power-supply nets in your design. Use this method instead of
automatic specification if your design includes only a few nets that you want to classify as
power-supply nets, or if automatic creation is not plausible.
Another approach is to first use the automatic method of specification for power-supply nets
that can be found that way, and then specify the remaining power-supply nets manually.
Prerequisites
• The nets you want to change to power-supply nets must have a Topology Type
constraint value of MST.
• When you intend to do this from the Navigator, electrical nets must be visible. (Right-
click Constraint Classes, then enable Show > Electrical Nets.)
Note
If using the Navigator to change a net to a power-supply net, it is recommended that
you have the display of power nets enabled in the Navigator. Otherwise, nets will
seem to disappear from the Navigator when you change them to power nets.
Procedure
• To change a single net into a power-supply net:
o Right-click the name of a net, then click Change Net to Power Net.
Defining Constraints for Power-Supply Nets
o Click to enable its Power Net constraint.

o In the Navigator, right-click a net, then click Change Net to Power Net.
• To change multiple nets into power-supply nets:
i. Select multiple net rows.
ii. From the Edit menu, click Power Nets, then click Change Nets to Power Nets.
Results
The tool enables the Power Net constraint for each affected net. You can now define power-
supply constraints for these nets.
Related Topics
Power Net
Defining Constraints for Power-Supply Nets

You can define power-supply constraints for nets marked in Constraint Manager as power-
supply nets. By defining these constraints, you can characterize your nets for power-integrity
analysis in HyperLynx PI.
If multiple power-supply nets in a constraint class need the same values for these constraints,
you can define them at that level instead of the net level. The only constraint of this type that
you cannot define at the constraint-class level is Power Net Constraints Supply Voltage. You
must define this constraint individually for each power-supply net.
Prerequisites
• The Power Net constraint of the nets for which you want to define these constraints must
be enabled. For more information, refer to “Power Net” on page 200.
Procedure
1. With the Nets spreadsheet page active, click the Filters - Groups toolbar dropdown, then
click Power Nets to reduce the display to just these constraints.
2. In the row of the power-supply net for which you want to define these constraints, type
or modify values for the following constraints:
• “Power Net Constraints Supply Voltage” on page 214
Results
When you use HyperLynx PI to analyze these nets, their power-supply constraints are included
in the analysis.
Changing Power-Supply Nets Back Into Nets
Changing Power-Supply Nets Back Into Nets

You can change power-supply nets back into nets as needed.
Prerequisites
• If you intend to do this in the Navigator, power-supply nets must be visible. (Right-click
Constraint Classes, then enable Show > Power Nets.)
Note
If using the Navigator to change a power-supply net back into a net, it is
recommended that you have the display of electrical nets enabled in the Navigator.
Otherwise, nets will seem to disappear from the Navigator when you change them back
into nets.
Procedure
• Right-click the name of a net, then click Change Power Net to Net.
• Clear a net’s Power Net constraint.
• In the Navigator, right-click a net, then click Change Power Net to Net.
Results
The power-supply net is now a regular net. The tool removes any power-supply constraints that
were defined for the net.
Related Topics
Power Net
Chapter 8
Differential Pair Creation and Pair Rule
Definition
You can designate two nets as a unique differential pair for the purpose of defining constraints
that are only applicable to this type of net pairing. When creating differential pairs, you can do
so manually and automatically.
Defining Differential Pairs Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Defining Differential Pairs Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Assigning Rules to Differential Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Defining Differential Pairs Manually

You can manually define differential pairs by selecting the two electrical nets to define as the
differential pair. After you define a differential pair, the tool updates the Nets spreadsheet page
to include the designation.
When you can match differential pairs by net name, you should consider creating differential
pairs automatically. By doing so, you can create differential pairs more efficiently. For more
information, refer to “Defining Differential Pairs Automatically” on page 19.
Prerequisites
• Nets that you define as differential pairs must be part of the same constraint class and net
class.
• The nets must be electrical nets.
• The nets must not be power nets.
Procedure
• On the Nets spreadsheet page, use Ctrl-click to select two electrical nets ( ), then on
the Pairs toolbar, click .
• After you select two electrical nets, right-click either net, then click Create
Differential Pair; or, from the Edit menu, click Differential Pairs, then click
Differential Pair from Selected Nets.
Differential Pair Creation and Pair Rule Definition
2. (Optional) To give the differential pair a unique name instead of its system-defined
name, right-click the differential-pair cell, then click Rename. Now that the cell is
editable, type a new name (but exclude these characters: ! \ “ and /), then press Enter.
Figure 8-1. Differential Pair
Results
• If you need to delete a differential pair, on the Nets spreadsheet page, click a differential
pair row ( ), then press Delete. To select multiple rows for simultaneous deletion, use
Ctrl-click and Shift-click.

You can automatically define differential pairs to quickly construct them from specific nets.
After you have the tool automatically construct differential pairs based on a net name criterion,
you select from the proposed list of differential pairs to choose those you want to create. After
you create specific differential pairs, the tool updates the Nets spreadsheet page to include them.
The process of automatically creating differential pairs is not always a viable method. It
depends on whether your nets have naming characteristics that allow for identification of
complimentary nets.
Prerequisites
• Nets that should comprise a differential pair must be part of the same net class and
constraint class.
Video
• Find net pairs that match a search criteria.

• Select the nets to join into differential pairs.
• Assign the new differential pairs to the same net class.
Procedure
• On the Pairs toolbar, click .
• From the Edit menu, click Differential Pairs, then click Auto Assign Differential
Pairs.
2. In the Auto Assign Differential Pairs dialog box, In the Assign by field, select one of
these assignment methods:
• Net Name — Group nets into differential pairs based on net naming conventions.
• Regular Expression — Group nets into differential pairs based on regular-
expression search criteria. If using this assignment method, the tool does not display
search results for the Pair net name field (step 4) when there are no search results for
the Net name field (step 3), even if they do exist.
The advantage of regular expressions is that you can use them to create more precise
net matching searches. In the event that the Net Name assignment method would not
work, you could create a regular expression that would identify certain pairs of
differential nets.
3. In the Net name field, type a search criterion. For example, if assigning by net name, you
could use a search criterion of *_P if you know that each net with this suffix should be
paired with a net of the same name that uses a different suffix.
Tip
To view the list of electrical nets in your design, click Preview Nets. Doing so can
be helpful when you are typing criteria in the Net name field and Pair net name field.
After you finish reviewing the content of the Electrical Nets dialog box, click OK.
4. In the Pair net name field, type an appropriate search criterion based on the Net name
search criterion you provided in step 3, then click .
For example, if assigning by net name, a complimentary suffix to the example in step 3
(*_P) might be *_N. In the illustration, you can see how the tool used the Net name and
Pair net name fields to discover five pairs of nets that may be candidates for differential
pair creation.
Figure 8-2. Automatic Assignment of Differential Pairs
Note
It is important to understand that the Net name field takes precedence over the Pair
net name field. This comes in to effect if the net name string or regular expression
string you type results in the same net showing up in both the Electrical Net column and
Pair Net column. In these cases, the nets show up in the Electrical Net column only.
5. Unless you chose to assign by regular expressions, skip to the next step. In this case, the
Match Differential Pairs dialog box appears. For each pair row the tool proposed based
on your regular expressions, you can click within the Pair Net column to select an
alternate pair net, if appropriate. After you finish making adjustments, click Accept.
Note
If two electrical nets on the same row do not match, the tool highlights the Pair Net
cell in red. You can hover over a red cell or refer to the Output window to determine
the cause of the conflict (for example, the two nets do not belong to the same net class).
6. In the list of proposed differential pairs, click to select the differential pairs you want to
use, then click Apply.
Assigning Rules to Differential Pairs
Tip
To select all proposed differential pairs, click . To unselect all differential pairs,
click .
7. (Optional) To give one or more differential pairs unique names instead of their system-
defined names, on the spreadsheet, right-click a differential-pair cell, then click
Rename. Now that the cell is editable, type a new name (but exclude these characters: !
\ “ and /), then press Enter.
Results
• If you need to delete a differential pair, on the Nets spreadsheet page, click a
differential-pair row ( ), then press Delete.

After you manually or automatically define differential pairs, you can assign rules (constraint
values) to each pair. Although most rules you can define are at the pair level, there are a few
differential pair constraints you can define at the constraint class level.
Procedure
1. On the Nets spreadsheet page, locate the row of the differential pair ( ) to which you
want to assign rules.
Tip
To limit the Nets spreadsheet to a subset of constraints that includes only differential
pair constraints, in the Filters - Groups toolbar dropdown, click Differential Pairs.
2. Click a specific constraint cell (for example, Separation Distance), then type an
appropriate value.
3. Repeat step 2 to define more rules.
Related Topics
Separation Distance Max
Differential Spacing
Chapter 9
Constraint Template Creation and Reuse
You create constraint templates to capture the constraints you define for a single net in a form
that gives you the ability to quickly apply those values to other nets. You can reuse constraint
templates in the design in which you create them.
Creating Constraint Templates to Capture Net Constraints. . . . . . . . . . . . . . . . . . . . . . 147
Constraints and Values Stored With Each Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Constraint Template Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Updating Nets With Constraint Template Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Creating Constraint Templates to Capture Net

Constraints
Create constraint templates to capture net constraints for reuse on similar nets within your
current design. Creating a constraint template for a single bus net is a common application for
reuse.
For example, after specifying the constraints that promote signal integrity for one bus net within
a 64-bit bus, you can quickly create a constraint template based upon that net, and then apply the
template to the other sixty-three nets that comprise the bus.
Note
When you modify constraint values on the Constraint Templates spreadsheet page, the tool
only changes the values in the template. The originating values, which come from other
spreadsheet pages, are not modified.
Prerequisites
• The Constraint Templates spreadsheet page is visible. To display it, right-click any
available spreadsheet tab, then select Constraint Templates.
Procedure
1. On the Nets spreadsheet page, right-click an electrical net ( ), then click Create
Constraint Template.
Constraints and Values Stored With Each Template
Tip
Instead of creating a new template, you can clone an existing template to use its
constraint values as the starting point for another template. To do so, on the
Constraint Templates spreadsheet page, right-click a template, then click Clone.
2. In the Create Constraint Template dialog box, in the name field and optional description
field, type suitable identifiers for this constraint template, then click OK.
Tip
Type a name and description that promotes the highest potential for proper reuse
among other designers and yourself.
3. If needed, modify specific constraint values defined in the constraint template.

Results
The constraint template is now available on the Constraint Templates spreadsheet page for
review or modification. At this point, you can do the following:
• Define the Device Matching Pattern cell — You can do this for one or more devices in
the constraint template (for example, QU988*). It is a regular expression. By doing so,
you can create name matching requirements that are used when the constraint template
is applied to a net. For more information about this cell, and when you might use it, refer
to its description in “Constraint Templates” on page 222.
• Rename the constraint template — On the Constraint Templates spreadsheet page,
right-click the name of the constraint template, then click Rename. Type a new name,
then press Enter.
• Delete the constraint template — On the Constraint Templates spreadsheet page, click
the name of the constraint template you want to delete, then press Delete.
Constraints and Values Stored With Each

Template
The tool combines various net values and constraints to produce each constraint template. It
does so by using internal Constraint Manager database information, constraint definitions you
have made on the Nets, Parts, and Noise Rules spreadsheet pages, and appropriate selections
from specific Constraint Manager dialog boxes.
Refer to “Constraint Templates” on page 222 for a description of each template cell.
Constraint Template Application
Constraint Template Application

After you create a constraint template to capture net constraints, you can apply it to one or more
nets. It is important to understand that the tool overwrites all net constraints that can be defined
within a template during the application process. This includes constraint values within a
template that are “blank” or undefined.
If you apply a constraint template to a net, make sure that the net to which you are applying it is
an appropriate candidate for the constraint set defined in the template. During the application
process, which includes the process of elaboration, Constraint Manager performs an analysis to
determine whether constraint template is suitable for the target net. Depending on the required
level of similarity you defined while setting up the tool, the potential for net application will
vary. By modifying the Constraint Manager setting that dictates this similarity requirement, you
can specify how similar candidate nets must be to the net from which a constraint template
originated.
Tip
To modify the similarity requirement between constraint templates and net candidates, from
the Setup menu, click Settings, then under Display, click General. Now, change the
Template match threshold. For example, to specify a lesser similarity requirement, type a
smaller percentage value.
Guidelines for Applying Constraint Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Applying a Constraint Template to Multiple Nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Applying Constraint Templates From the Constraint Templates Page . . . . . . . . . . . . . 151
Applying a Constraint Template to a Single Net . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Device Pattern Matching With Constraint Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Modifying Pin Matching for an Applied Constraint Template . . . . . . . . . . . . . . . . . . . . 153
Guidelines for Applying Constraint Templates

You should be aware of certain guidelines for differential pairs and virtual pins.
Differential Pairs
If applying a constraint template to a differential pair, the constraint template must have been
created from a differential pair. For example, if you only have constraint templates based off of
single nets, trying to apply a constraint template to a differential pair results in there being no
available constraint templates for selection. In some cases, though, you might want to apply a
single-net constraint template to each net that will comprise a differential pair before you create
the actual differential pair.
Applying a Constraint Template to Multiple Nets
Virtual Pins
If you apply a template that contains virtual pins, the tool only applies it correctly to nets if these
conditions are met:
• They are of the same topology type.

• They contain the same number of virtual pins.
For example, you create a template from a net that is topology type star and has two virtual pins.
You then try to apply the template to a net that is topology type TShape and also includes two
virtual pins. Because both the topology type and the number of virtual pins do not match, the
template is applied incorrectly. In fact, the net’s two virtual pins and from-tos are deleted.
Applying a Constraint Template to Multiple Nets

Use this procedure if you want to apply a constraint template to a selection of nets and not just a
single net. This procedure provides application instructions that originate from the Nets page of
the spreadsheet. You should already know which template you want to apply to nets.
You can also use a slightly different interface that originates from the Constraint Templates
page of the spreadsheet. It is useful if you do not know which template you want to apply to a
net and need to refer to the list of available templates to make a decision. For more information,
refer to “Applying Constraint Templates From the Constraint Templates Page” on page 151.
Procedure
1. With the Nets spreadsheet page active, from the Edit menu, click Apply Constraint
Template.
2. In the Select Nets for Constraint Template Application dialog box, type a Net Name
Filter to select the appropriate nets to which to apply the constraint template, then click
.
3. In the Constraint Template field, use the pull down to select a constraint template.
Note
By default, the tool moves the nets into the classes defined in the template. To
preserve their classes, clear the check boxes for Apply Constraint Class and Apply
Net Class.
4. Under the list of Proposed nets, use the check box next to each net to uncheck the nets to
which you do not want to apply the constraint template. While you are working with the
list of proposed nets, you can do any of the following:
• To apply the constraint template to all checked nets without exiting this dialog box,
to the right of the Proposed nets heading, click .
• To select all Proposed nets, click .
Applying Constraint Templates From the Constraint Templates Page
• To deselect all Proposed nets, click .
• To clear the list of Proposed nets and start over, click .
5. After you have selected the nets to which you want to apply the constraint template,
click OK.
Results
After you finish, the tool displays the Constraint Template Matching dialog box. It lets you
modify pin matching. For more information, refer to “Modifying Pin Matching for an Applied
Constraint Template” on page 153.
Applying Constraint Templates From the Constraint

Templates Page
You can use this procedure to assign a constraint template to one or more nets. This approach is
most useful if you do not know which template you want to apply and need to refer to the list of
available templates in order to make a decision.
Procedure
1. With the Constraint Templates spreadsheet page active, right-click a template name
row, then click Apply Constraint Template to Net(s).
• In the Assign nets to template dialog box, use click and Ctrl-click to select one or
more nets.
• Use the search box, and optionally wildcard characters, to quickly select a group of
nets that match a name criteria.
3. After you finish highlighting the appropriate nets, click OK.
Results
Applying a Constraint Template to a Single Net

Constraint Manager provides multiple methods of applying constraint templates to nets. Most
procedures are generally more suitable for working with large numbers of nets. The method
described in the procedure is useful if you want to work with a finite number of nets by selecting
individual nets on the Nets spreadsheet page.
Device Pattern Matching With Constraint Templates
Procedure
1. On the Nets spreadsheet page, right-click an electrical net ( ), then click Apply
Constraint Template. (You can also select multiple nets by using Ctrl-click or Shift-
click.)
Tip
You can also apply a constraint template at the constraint-class level, but doing so is
only for propagation to nets inside the constraint class. For this reason, the tool does
not apply the constraint template directly to the constraint class. The tool only applies
constraint templates directly to nets and not object hierarchy.
2. In the Select Constraint Template dialog box, select the constraint template to apply to
one or more nets.
3. If applying constraint templates to nets, specify whether the tool should also move the
nets into the constraint (electrical and signal integrity) and/or net (physical) classes
defined in the template. To make these specifications, click the check boxes associated
with Apply Constraint Class and Apply Net Class, then click OK.
For example, to move nets into just the net class defined in the constraint template, make
sure that only Apply Net Class is checked.
The Constraint Template Application Report dialog box shows the compatibility
between a constraint template and the selected nets. The tool applies the constraint
template to the selected nets.
Results
Device Pattern Matching With Constraint Templates

If automatic pin matching does not work as precisely as needed, you can define the Device
Matching Pattern value for one or more components in a constraint template. You can also
define this template value if you expect this to be the case.
Here is a detailed example of when you would use this value:
1. There is a set of nets that contain these identical components: QU9881, QU9882, and
QU9883. These components have pins that are part of a netline topology.
2. You create a constraint template from the first net in the set. In the template, component
QU9881 is now defined as Dev1.
3. In the template, you define the Device Matching Pattern value for component Dev1 as
QU988*.
Modifying Pin Matching for an Applied Constraint Template
4. Now, if you apply the constraint template to the nets containing QU9882 and QU9883,
the tool matches the Dev1 component to these components. In essence, the pins create
the same netline topology.
Modifying Pin Matching for an Applied Constraint

Template
You can modify pin matching for each net associated with a constraint template. After you
apply a constraint template to a net, the tool automatically displays the Constraint Template
Matching dialog box. You can also display this dialog box manually if you need to update pin
matching.
The Constraint Template Matching dialog box uses both color coding and numbering to show
how well a constraint template matches the net to which it is applied. The following are
important fields of the dialog box:
• Pins Template — Displays the number of pins in the template.

• Pins Net — Displays the number of pins in the net.
• Pins Matched — Displays the number of net pins the tool has matched to template pins.
The tool indicates good matching through green color coding of the Pins Net and Pins Matched
fields. Red color coding indicates that there is not sufficient matching. The tool uses yellow to
show that the matching is not good, but it may still be suitable. In the example illustration, green
coloring indicates that all 5 of the pins in the constraint template have been matched. The
matching table at the bottom shows the objects that are matched to the template objects.
Updating Nets With Constraint Template Changes
Figure 9-1. Pin Matching Between Template and Net
Procedure
1. On the Nets spreadsheet page, right-click the row of a net that is associated with a
constraint template, then click Update Pin Matching.
2. In the Constraint Template Matching dialog box, in the table at the bottom, click the
right column of a pin row to change the associated net pin with one of the available
template pins.
Note
You can associate each template pin with a single net pin.
3. After you finish making changes, click OK or Apply.
Updating Nets With Constraint Template

Changes
After you modify the constraint definitions in a template, the tool may not automatically update
nets associated with the template to include the template changes. If they remain static, they
reflect the constraint values in the template at the time it was applied to the net. In these cases,
you must update nets associated with the template if you want to use the current constraint
template values with each net.
Constraint Manager will only automatically update a net to actively reflect the template values
if you have it configured to do so. To modify this setting, from the Setup menu, click Settings,
then in the Settings dialog box, click Other. Under Constraint Templates, activate or clear the
Automatically apply templates check box.
Tip
To make it easier to determine if changes have occurred and a net does not reflect the
current constraint values stored in the associated template, refer to the Nets spreadsheet
page, Template Status constraint.
Figure 9-2. Status Cell Indicates Differences Between Net and Template
Procedure
On the Nets spreadsheet page, right-click the row of a net that is associated with a constraint
template, then click Reapply Constraint Template.
Chapter 10
Design Tool Update
This section helps you understand how and when constraints are synchronized between a tool
and the Constraint Manager invocation you launched from that tool. It also provides instructions
for sending constraint and design changes from a front-end design representation to a back-end
design representation.
Constraint and Design Change Management Between Tools . . . . . . . . . . . . . . . . . . . . . 157

Synchronization of Constraint Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Sending Schematic Data to Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Sending Layout Data to Schematics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Constraint and Design Change Management

Between Tools
When Constraint Manager and the tool from which you launched it become synchronized
depends on whether you are using a front-end tool or a back-end tool.
Refer to these synchronization rules:
• Front-end — Synchronization occurs automatically as you make changes in Constraint

Manager or a schematic capture tool.
• Back-end — Synchronization occurs after you exit Constraint Manager or use the
rightmost light in the layout tool to send pending constraint changes to layout.
When you want to update changes between the front-end and back-end tools that comprise your
flow, you can perform forward annotation by sending schematic data to layout, or back
annotation by updating the schematic design with changes from layout. During these processes,
constraint synchronization occurs, resulting in full updates of both the front-end and back-end
constraint sets. For more information, refer to “Synchronization of Constraint Sets” on
page 158.
Communication of Design Changes Between Schematic and Layout

Constraint Manager provides several constraint-driven design flows that bring together front-
end design systems (schematic) with back-end design systems (layout). Depending on the
design systems that make up your design flow, you communicate design changes between
Design Tool Update
Synchronization of Constraint Sets
schematic and layout using the forward and back-annotation commands provided by your
design systems.
Synchronization of Constraint Sets

The Constraint Manager synchronization process runs during forward annotation and back
annotation. This process is used to synchronize the separate constraint sets associated with your
front-end and back-end design representations.
When you forward annotate, both constraint sets are completely synchronized. Front-end
constraint changes are sent to the back-end constraint set and back-end constraint changes are
sent to the front-end constraint set. Conversely, when you back annotate, only back-end
constraint changes are sent to the front-end constraint set.
Figure 10-1. Constraint Manager Synchronization Process Runs During Design

Annotation
Constraint Manager synchronization works in this manner to provide more opportunities for
constraint alignment in all of its flows. Because both forward annotation and back annotation
result in constraint synchronization, overall design state is less of an issue for update purposes.
For example, if your schematic data is changing less frequently as you move toward
manufacturing start, forward annotating to layout gives you more opportunities to acquire
constraint changes made in a layout invocation of Constraint Manager. Due to the large volume
of design changes that can occur in the back-end at the end of the PCB creation cycle, forward
annotating to get back-end constraint changes saves time because there are few or no schematic
changes to communicate to your layout design.
Design Tool Update
Sending Schematic Data to Layout
Sending Schematic Data to Layout

You can send schematic data to layout to update the layout design to reflect applicable changes
driven by the schematic. You do this through the process of forward annotation.
Note
For specific forward-annotation commands, refer to the documentation for your schematic-
capture software.
Procedure
From your front-end design tool, or in some cases your back-end design tool, forward annotate.
Sending Layout Data to Schematics

You can send layout data to your schematic design to update it to reflect applicable changes
driven by layout. You do this through the process of back annotation.
Note
For specific back-annotation commands, refer to the documentation for your layout
software.
Prerequisites
• You synchronized constraint data between layout and Constraint Manager by exiting
Constraint Manager or using the rightmost light in the layout tool to send it pending
constraint changes.
Procedure
From your back-end design tool, back annotate.
Design Tool Update
Sending Layout Data to Schematics
Appendix A
This section provides a full constraint reference for each constraint available in Constraint
Manager. This reference is organized to reflect the default ordering of constraints on each
spreadsheet page.
Constraint Reference Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Trace and Via Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Clearances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Constraint Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Constraint Reference Overview

The constraint reference includes information about each design constraint that appears on the
Constraint Manager spreadsheet.
This includes the Trace & Via Properties, Clearances, Nets, and Parts pages of the spreadsheet.
Constraints in each category are listed by their default arrangement on a spreadsheet page.
Click within the section “Constraint Reference” of the table of contents to view the reference
topic associated with a constraint. In the illustration below, the graphic available in the
constraint topic Trace Width Minimum is shown.
Example A-1. Constraint Reference Illustration
Note
For illustrative purposes, components and other board elements may appear
disproportionately large relative to PCB size.
Constraint Reference Overview
Related Topics
Constraint Definition Through Spreadsheet Pages
Trace and Via Properties
Trace and Via Properties

Refer to the trace and via property constraint reference topics that follow. You access these
constraints through the Trace & Via Properties spreadsheet page.
Table A-1. Trace and Via Property Constraints Summary

Constraint Description
Index Displays the layer number for a board layer.
Type Displays the type of printed circuit board layer (for example,
signal or plane). The tool also displays this constraint on the
Clearances page.
Via Assignments Defines the via assignment for a net class.
Route Defines whether the layout tool can use a board layer for
routing. You can define this value for individual board layers
and net classes.
Trace Width Minimum Defines the minimum acceptable trace width. You can define
this value for individual board layers and net classes. The
router uses Trace Width Minimum whenever it can route at
this trace width and a minimum width is needed.
Trace Width Typical Defines the typical acceptable trace width. You can define
this value for individual board layers and net classes. The
routers uses this trace width whenever possible.
Trace Width Expansion Defines the expansion, or maximum acceptable trace width.
You can define this value for individual board layers and net
classes. The router uses this trace width if it needs to increase
trace width to satisfy routing requirements.
Differential Spacing Defines the required parallel distance between trace
segments that comprise a differential pair. You can define
this value for individual board layers and net classes.
Index
Index
Displays the layer number for a board layer.
Tip
In the event that the stackup layer sequence is shown out of order in the spreadsheet, you
can click to sort by the Index heading to return the layer listing to its sequential order.
Constraint Type
Reference
Example
1
Related Topics
Type
Type
Displays the type of printed circuit board layer (for example, signal or plane). The tool also
displays this constraint on the Clearances page.
Constraint Type
Reference
Example
Signal
Related Topics
Via Assignments
Via Assignments
Defines the via assignment for a net class.
The value “(default)” means that the net class is using the via assignment defaults defined in the
layout tool, which are general via settings for a design. “Custom” indicates that the net class is
instead using selections in the Via Assignments dialog box.
Constraint Type
Modifiable
Example
(default)
Related Topics
Route
Route
Defines whether the layout tool can use a board layer for routing. You can define this value for
individual board layers and net classes.
Constraint Type
Modifiable
Related Topics
Trace Width Minimum
Trace Width Minimum

Defines the minimum acceptable trace width. You can define this value for individual board
layers and net classes. The router uses Trace Width Minimum whenever it can route at this trace
width and a minimum width is needed.
Figure A-1. Trace Width Minimum
Constraint Type
Modifiable
Limits and Defaults
Minimum Maximum Default

Value Value Value
0.01 th 1000 th 10 th
Example
8 mil
Related Topics
Trace Width Expansion
Trace Width Typical
Trace Width Typical
Trace Width Typical

Defines the typical acceptable trace width. You can define this value for individual board layers
and net classes. The routers uses this trace width whenever possible.
Figure A-2. Trace Width Typical
Constraint Type
Modifiable
Limits and Defaults

Value Value Value
0.01 th 1000 th 10 th
Example
9 mil
Related Topics
Trace Width Minimum

Defines the expansion, or maximum acceptable trace width. You can define this value for
individual board layers and net classes. The router uses this trace width if it needs to increase
trace width to satisfy routing requirements.
Figure A-3. Trace Width Expansion
Constraint Type
Modifiable
Limits and Defaults

Value Value Value
0.01 th 1000 th 10 th
Example
10 mil
Related Topics
Trace Width Minimum
Trace Width Typical
Defines the required parallel distance between trace segments that comprise a differential pair.
You can define this value for individual board layers and net classes.
Figure A-4. Differential Spacing
Tip
If applied in conjunction with Differential Spacing, Trace Width Minimum gives you the
ability to define a smaller Differential Spacing constraint. As trace width decreases,
potential aggressor net interference between differential pairs reduces as the total conductive
surface area decreases.
Constraint Type
Modifiable
Limits and Defaults

Value Value Value
1 nm 1 in 10 th
Example
0.5 mm
Related Topics
Trace Width Minimum
Clearances
Clearances
Refer to the clearance constraint reference topics that follow. You access these constraints
through the Clearances spreadsheet page.
Note
By default, the router uses clearance constraints defined in the (Defaut Rule) between all net
classes unless you create additional clearance rule sets and then assign them between
specific net classes.
Table A-2. Clearance Constraints Summary

Index Displays the layer number for a board layer.
Type Displays the type of printed circuit board layer (for example,
plane). The tool also displays this constraint on the Trace &
Via Properties page.
Trace To Trace Defines the minimum clearance distance between trace
segments. You can define this value for board layers and
clearance rules.
Trace To Pad Defines the minimum clearance distance between traces and
through-hole pads. You can define this value for board layers
and clearance rules.
Trace To Via Defines the minimum clearance distance between traces and
vias. You can define this value for board layers and clearance
rules.
Trace To SMD Pad Defines the minimum clearance distance between traces and
the pads of surface mount devices. You can define this value
for board layers and clearance rules.
Pad To Pad Defines the minimum clearance distance between pads. You
can define this value for board layers and clearance rules.
This constraint definition includes through-hole pads and
SMD pads.
Pad To Via Defines the minimum clearance distance between through-
hole pads and vias. You can define this value for board layers
Via To Via Defines the minimum clearance distance between vias. You
Via To SMD Pad Defines the minimum clearance distance between the pads of
surface mount devices and vias. You can define this value for
board layers and clearance rules.
Clearances
Table A-2. Clearance Constraints Summary (cont.)

Board Edge To Trace Defines the minimum clearance distance between the edge of
a board and trace segments. You can define this value for
Board Edge To Pad Defines the minimum clearance distance between the edge of
a board and through-hole pads. You can define this value for
Board Edge To Via Defines the minimum clearance distance between the edge of
a board and vias. You can define this value for board layers
Board Edge To Copper Defines the minimum clearance distance between the edge of
a board and copper objects (copper, copper pours, and plane
areas). You can define this value for board layers and
clearance rules.
Board Edge To SMD Pad Defines the minimum clearance distance between the edge of
a board and the pads of surface mount devices. You can
define this value for board layers and clearance rules.
Copper To Trace Defines the minimum clearance distance between copper
objects (copper, copper pours, and plane areas) and trace
segments. You can define this value for board layers and
clearance rules.
Copper To Pad Defines the minimum clearance distance between copper
objects (copper, copper pours, and plane areas) and through-
hole pads. You can define this value for board layers and
clearance rules.
Copper To Via Defines the minimum clearance distance between copper
objects (copper, copper pours, and plane areas) and vias. You
Copper To Copper Defines the minimum clearance distance between copper
objects (copper, copper pours, and plane areas). You can
define this value for board layers and clearance rules.
Copper To SMD Pad Defines the minimum clearance distance between copper
objects (copper, copper pours, and plane areas) and the pads
of surface mount devices. You can define this value for board
layers and clearance rules.
Index
Index
Displays the layer number for a board layer.
Tip
In the event that the stackup layer sequence is shown out of order in the spreadsheet, you
can click to sort by the Index heading to return the layer listing to its sequential order.
Constraint Type
Reference
Example
1
Related Topics
Type
Type
Displays the type of printed circuit board layer (for example, plane). The tool also displays this
constraint on the Trace & Via Properties page.
Constraint Type
Reference
Example
Signal
Related Topics
Trace To Trace
Trace To Trace
Defines the minimum clearance distance between trace segments. You can define this value for
Figure A-5. Trace To Trace
Constraint Type
Modifiable
Limits and Defaults

Value Value Value
1 nm 1 in 10 th
Example
20 th
Related Topics
Trace To Pad
Trace To Pad
Defines the minimum clearance distance between traces and through-hole pads. You can define
this value for board layers and clearance rules.
Figure A-6. Trace To Pad
Constraint Type
Modifiable
Limits and Defaults

Value Value Value
1 nm 1 in 10 th
Example
12 th
Related Topics
Trace To Via
Trace To Via
Defines the minimum clearance distance between traces and vias. You can define this value for
Figure A-7. Trace To Via
Constraint Type
Modifiable
Limits and Defaults

Value Value Value
1 nm 1 in 10 th
Example
8 th
Related Topics
Trace To SMD Pad
Trace To SMD Pad

Defines the minimum clearance distance between traces and the pads of surface mount devices.
You can define this value for board layers and clearance rules.
Figure A-8. Trace To SMD Pad
Constraint Type
Modifiable
Limits and Defaults

Value Value Value
1 nm 1 in 10 th
Example
15 th
Related Topics
Pad To Pad
Pad To Pad
Defines the minimum clearance distance between pads. You can define this value for board
layers and clearance rules. This constraint definition includes through-hole pads and SMD pads.
Figure A-9. Pad To Pad
Constraint Type
Modifiable
Limits and Defaults

Value Value Value
1 nm 1 in 10 th
Example
15 th
Related Topics
Pad To Via
Pad To Via
Defines the minimum clearance distance between through-hole pads and vias. You can define
Figure A-10. Pad To Via
Constraint Type
Modifiable
Limits and Defaults

Value Value Value
1 nm 1 in 10 th
Example
8 th
Related Topics
Via To Via
Via To Via
Defines the minimum clearance distance between vias. You can define this value for board
layers and clearance rules.
Figure A-11. Via To Via
Constraint Type
Modifiable
Limits and Defaults

Value Value Value
1 nm 1 in 10 th
Example
15 th
Related Topics
Via To SMD Pad
Via To SMD Pad

Defines the minimum clearance distance between the pads of surface mount devices and vias.
Figure A-12. Via To SMD Pad
Constraint Type
Modifiable
Limits and Defaults

Value Value Value
1 nm 1 in 10 th
Example
15 th
Related Topics
Board Edge To Trace
Board Edge To Trace

Defines the minimum clearance distance between the edge of a board and trace segments. You
Constraint Type
Modifiable
Limits and Defaults

Value Value Value
1 nm 1 in 10 th
Example
200 th
Related Topics
Board Edge To Pad
Board Edge To Pad

Defines the minimum clearance distance between the edge of a board and through-hole pads.
Constraint Type
Modifiable
Limits and Defaults

Value Value Value
1 nm 1 in 10 th
Example
200 th
Related Topics
Board Edge To Via
Board Edge To Via

Defines the minimum clearance distance between the edge of a board and vias. You can define
Constraint Type
Modifiable
Limits and Defaults

Value Value Value
1 nm 1 in 10 th
Example
200 th
Related Topics
Board Edge To Copper
Board Edge To Copper

Defines the minimum clearance distance between the edge of a board and copper objects
(copper, copper pours, and plane areas). You can define this value for board layers and
clearance rules.
Constraint Type
Modifiable
Limits and Defaults

Value Value Value
1 nm 1 in 10 th
Example
200 th
Related Topics
Board Edge To SMD Pad
Board Edge To SMD Pad

Defines the minimum clearance distance between the edge of a board and the pads of surface
mount devices. You can define this value for board layers and clearance rules.
Constraint Type
Modifiable
Limits and Defaults

Value Value Value
1 nm 1 in 10 th
Example
200 th
Related Topics
Copper To Trace
Copper To Trace
Defines the minimum clearance distance between copper objects (copper, copper pours, and
plane areas) and trace segments. You can define this value for board layers and clearance rules.
Constraint Type
Modifiable
Limits and Defaults

Value Value Value
1 nm 1 in 10 th
Example
20 th
Related Topics
Copper To Pad
Copper To Pad
plane areas) and through-hole pads. You can define this value for board layers and clearance
rules.
Constraint Type
Modifiable
Limits and Defaults

Value Value Value
1 nm 1 in 10 th
Example
20 th
Related Topics
Copper To Via
Copper To Via
plane areas) and vias. You can define this value for board layers and clearance rules.
Constraint Type
Modifiable
Limits and Defaults

Value Value Value
1 nm 1 in 10 th
Example
20 th
Related Topics
Copper To Copper
Copper To Copper
plane areas). You can define this value for board layers and clearance rules.
Constraint Type
Modifiable
Limits and Defaults

Value Value Value
1 nm 1 in 10 th
Example
20 th
Related Topics
Copper To SMD Pad
Copper To SMD Pad

plane areas) and the pads of surface mount devices. You can define this value for board layers
Constraint Type
Modifiable
Limits and Defaults

Value Value Value
1 nm 1 in 10 th
Example
20 th
Related Topics
Nets
Nets
Refer to the net constraint reference topics that follow. You access these constraints through the
Nets spreadsheet page.
Table A-3. Net Constraints Summary

Hierarchical Path Displays the hierarchical path to the object within the design.
# Pins Displays the number of pins that comprise the net.
Net Class Defines the name of the net class to which the net should
belong.
Topology Type Defines the topology type used for routing, which can be an
automatic routing pattern, or a custom routing pattern that
you define. You can define this value for individual nets and
constraint classes.
Power Net Defines the net as a power-supply net. You can define this
value for individual nets. You cannot define differential pair
nets as power-supply nets.
Analog Defines the net as analog and prevents the tool from merging
physical nets that comprise an electrical net into another
electrical net, or a differential pair. You cannot define
differential pair nets as Analog. You can define this value for
individual nets and constraint classes.
Stub Length Max Defines the maximum length of shared copper allowed
between two branches of a net if routing it as a custom,
complex, or chained Topology Type. You can define this
value for individual nets and constraint classes.
# Vias Max Defines the maximum number of vias the router can create
when routing a net. If specified, this constraint value must be
between 1 and 1000. You can define this value for individual
nets and constraint classes.
Length Min Defines the minimum acceptable physical routing length
between design connections.You can define this value for
individual nets, pin pairs, differential pairs, and constraint
classes.
Length Max Defines the maximum acceptable physical routing length
between design connections.You can define this value for
individual nets, pin pairs, differential pairs, and constraint
classes.
Length Manhattan Displays the Manhattan net length. The tool shows the actual
length in the Length Actual cell if the net is routed.
Nets
Table A-3. Net Constraints Summary (cont.)

Length Min Length Displays the straight-line length between two pin pairs if
both components are placed. The tool replaces this length
with Length Actual if the net is routed.
Length Match Defines a match character or string (for example, a) you can
use to group nets for similar length routing. You can define
this value for individual nets, pin pairs, and differential pairs.
Length Tol Introduces a tolerance range around the net routing length
requirements for nets that duplicate a Length Match (for
example, a). You can also define this constraint at the
constraint class level without the pre-requirement of defining
a match character or string.
Length Delta Displays the difference between the actual value for the net
and the net with the largest actual value in the match group.
If there is no difference, this cell displays 0. The tool does not
includes Length Tol values when it calculates this delta
value.
Length Range Displays the range of length actuals for all nets and/or
constraint classes that are part of the same match group.
Separation Distance Max Defines the maximum allowed distance that differential
traces are allowed to route at a spacing greater or less than
the Differential Spacing constraint. You can define this value
for each differential pair.
Differential Spacing Displays the required parallel distance between trace
segments that comprise a differential pair. If you define
separate spacing values for each board layer, Constraint
Manager displays the range of values as a colon-separated
list. For example, "5:10" indicates a range of values where 5
is the smallest value and 10 is the largest value.
Power Net Constraints Defines the operating voltage for a power-supply net. You
Supply Voltage can define this value for each power-supply net.
Hierarchical Path
Hierarchical Path
Displays the hierarchical path to the object within the design.
Constraint Type
Reference
Example
sheet1
Related Topics
# Pins
# Pins
Displays the number of pins that comprise the net.
Constraint Type
Reference
Example
2
Related Topics
Net Class
Net Class
Defines the name of the net class to which the net should belong.
If you create a constraint template, the tool includes this constraint.
Constraint Type
Modifiable
Related Topics
Topology Type
Topology Type
Defines the topology type used for routing, which can be an automatic routing pattern, or a
custom routing pattern that you define. You can define this value for individual nets and
constraint classes.
You can choose from these automatic topology types, each of which has a corresponding
Topology toolbar button:
• MST — Minimum Spanning Tree tells the router to connect the pins in any way
possible.
• Chained — Instructs the router to connect nets from pin to pin beginning with all
sources, all loads, and then all terminators.
• Custom — For creating custom topologies.
When you define Topology Type for a differential pair, it is applied to both nets that comprise
the differential pair. The same is true when you define it for a net that comprises a differential
pair. After you do so, the other net and the differential pair level all show the updated selection.
Note
Only a subset of the available topology types are available to differential pairs and the nets
that comprise them.
Constraint Type
Modifiable
Related Topics
Power Net
Power Net
Defines the net as a power-supply net. You can define this value for individual nets. You cannot
define differential pair nets as power-supply nets.
Constraint Type
Modifiable
Related Topics
Analog
Power Net Constraints Supply Voltage
Analog
Analog
Defines the net as analog and prevents the tool from merging physical nets that comprise an
electrical net into another electrical net, or a differential pair. You cannot define differential pair
nets as Analog. You can define this value for individual nets and constraint classes.
Note
To change a net from an electrical net to a physical net, you can enable Analog for the net
row. When the tool automatically updates electrical nets, the net will now show as a
physical net. To reverse the process, disable the Analog cell.
Constraint Type
Modifiable
Related Topics
Overview of Electrical Nets and Physical Nets in Constraint Manager
Stub Length Max
Stub Length Max

Defines the maximum length of shared copper allowed between two branches of a net if routing
it as a custom, complex, or chained Topology Type. You can define this value for individual
nets and constraint classes.
Figure A-13. Stub Length Max
If available, the tool displays the actual value for this constraint in the Actual cell to its right.
Constraint Type
Modifiable
Limits and Defaults

Value Value
0 1 in 300 th
Related Topics
# Vias Max
# Vias Max
Defines the maximum number of vias the router can create when routing a net. If specified, this
constraint value must be between 1 and 1000. You can define this value for individual nets and
constraint classes.
Constraint Type
Modifiable
Related Topics
Length Min
Length Min
Defines the minimum acceptable physical routing length between design connections.You can
define this value for individual nets, pin pairs, differential pairs, and constraint classes.
Note
The tool does not support the use of constants in this constraint.
Figure A-14. Length Min
Constraint Type
Modifiable
Related Topics
Length Delta
Length Max
Length Max
Length Max
Defines the maximum acceptable physical routing length between design connections.You can
define this value for individual nets, pin pairs, differential pairs, and constraint classes.
Note
The tool does not support the use of constants in this constraint.
Figure A-15. Length Max
Manhattan Length
To derive maximum length from the Manhattan length computed during routing, type a value
between 1 and 100, and follow it with a percentage sign (%). For example, to use 110% of
Manhattan length, type 10%.
Constraint Type
Modifiable
Related Topics
Length Delta
Length Min
Length Manhattan
Length Manhattan
Displays the Manhattan net length. The tool shows the actual length in the Length Actual cell if
the net is routed.
Constraint Type
Reference
Related Topics
Length Min Length
Length Min Length

Displays the straight-line length between two pin pairs if both components are placed. The tool
replaces this length with Length Actual if the net is routed.
Constraint Type
Reference
Related Topics
Length Match
Length Match
Defines a match character or string (for example, a) you can use to group nets for similar length
routing. You can define this value for individual nets, pin pairs, and differential pairs.
To duplicate the length of a net row that has a defined match character, type the match character
into the Length Match cell of the net for which you have not defined length.
Constraint Type
Modifiable
Related Topics
Length Tol
Length Tol
Introduces a tolerance range around the net routing length requirements for nets that duplicate a
Length Match (for example, a). You can also define this constraint at the constraint class level
without the pre-requirement of defining a match character or string.
Constraint Type
Modifiable
Example
100 th
Related Topics
Length Delta
Length Delta
Displays the difference between the actual value for the net and the net with the largest actual
value in the match group. If there is no difference, this cell displays 0. The tool does not
includes Length Tol values when it calculates this delta value.
Constraint Type
Reference
Related Topics
Length Range
Length Range
Displays the range of length actuals for all nets and/or constraint classes that are part of the
same match group.
For example, a value of 3000:5000 indicates that the smallest actual among matched design
objects is 3000; the largest actual is 5000.
Constraint Type
Reference
Related Topics
Length Match

Defines the maximum allowed distance that differential traces are allowed to route at a spacing
greater or less than the Differential Spacing constraint. You can define this value for each
differential pair.
Figure A-16. Separation Distance Max
Constraint Type
Modifiable
Example
200 mil
Related Topics
Displays the required parallel distance between trace segments that comprise a differential pair.
If you define separate spacing values for each board layer, Constraint Manager displays the
range of values as a colon-separated list. For example, "5:10" indicates a range of values where
5 is the smallest value and 10 is the largest value.
Figure A-17. Differential Spacing
Constraint Type
Reference
Example
30 mil
Related Topics

Defines the operating voltage for a power-supply net. You can define this value for each power-
supply net.
Note
To define this constraint, you must enable the Power Net constraint for the net.
Constraint Type
Modifiable
Example
5V
Related Topics
Power Net
Analog
Parts
Parts
Refer to the part constraint reference topics that follow. You access these constraints through
the Parts spreadsheet page.
Table A-4. Part Constraints Summary

Hierarchical Path Displays the hierarchical component path, if applicable.
Part Number Displays the part number for a design component.
Qty Displays the number of times a part is used in the design.
Part Type Displays the part-type value associated with a design
component.
Series Defines whether the tool should consider a series-class
component (for example, resistor) a series element
(“connected in series”), and therefore not used for electrical
net generation. You can define this value for parts and part
instances.
Pin Package Length Defines a pin's internal package length between the substrate
and dielectric layers of the component. You commonly use
this constraint to define wire bonding length.
Hierarchical Path
Hierarchical Path
Displays the hierarchical component path, if applicable.
Constraint Type
Reference
Example
XCMP107/E1
Part Number
Part Number
Displays the part number for a design component.
Constraint Type
Reference
Example
74LS82
Qty
Qty
Displays the number of times a part is used in the design.
Constraint Type
Reference
Example
4
Part Type
Part Type
Displays the part-type value associated with a design component.
Constraint Type
Reference
Example
IC
Series
Series
Defines whether the tool should consider a series-class component (for example, resistor) a
series element (“connected in series”), and therefore not used for electrical net generation. You
can define this value for parts and part instances.
Tip
You can also modify the series specification for a part instance on the Nets page of the
spreadsheet. To do so, expand a physical net, right-click a pin instance (for example, R1-1),
then click Make series or Make non-series. This change affects only the part instance.
If an extensive electrical net includes other electrical nets that should not stay grouped into the
top-level, extensive electrical net, you can disable the Series check box of any connecting/
shared components to separate the electrical nets of interest. A common reason to do this is if
you need to define two electrical nets as a differential pair for the purpose of constraint
definition, but they do not show up as independent electrical nets (or a pre-defined differential
pair) because of their association with the comprehensive electrical net (for example, power
net).
For example, if there is a missing differential pair, Constraint Manager might not recognize a
differential pair that shares a series discrete component. Instead, the tool interprets the design
methodology of the net as an electrical net("^^^"). To change this recognition, uncheck the
Series check box, then automatically or manually define the differential pair.
Constraint Type
Modifiable
Pin Package Length
Pin Package Length

Defines a pin's internal package length between the substrate and dielectric layers of the
component. You commonly use this constraint to define wire bonding length.
Pin package length constraints only affect net length values. The value you type into this cell
must be less than 1968.5 th (5 cm). There is no default value for this constraint. If you do not
define it, pin package length is 0.
Constraint Type
Modifiable
Limits
Maximum Value
6 in
Constraint Templates
Refer to the constraint template reference information that follows. You access these constraints
through the Constraint Templates spreadsheet page.
Constraint Description/Topic
Template Name Name of the constraint template.
Description Description of the constraint template, if provided.
Device Orig Name Name of the source object.
Device Matching Pattern Defines a regular-expression device name matching pattern
(for example, QU988*) that becomes a requirement when
you apply the constraint template to a net. This is an
optional value. Here are some examples of when you might
use it:
• If automatic pin matching does not work precisely or
produce the needed outcome.
• If a group of nets includes one or more of the same
component.
Note: You generally do not need to define this value if
all components in a net are unique. This is because the
automatic pin matching process has no issues during
application of the constraint template.
Device Type Part number of the source component.
Device Model IBIS model of the source object.
Device Value Discrete value of the source object, if available.
Pin Type Pin type of the source pin.
Pin Number Pin number of the source pin.
Pin Net Template net for the pin.
Pin Model Pin model of the source object.
Pin Topology Pin Type Pin type of the topology.
Pin Set Type Type of pin set (for example, balanced or unbalanced).
Pin Set Pins Pins included in the pin set.
Net Constraint Class Constraint class of the template.
Net Net Class See “Net Class” on page 198.
Topology Type See “Topology Type” on page 199.
Stub Length Max See “Stub Length Max” on page 202.
# Vias Max See “# Vias Max” on page 203.
Constraint Description/Topic
Length See:
• “Length Min” on page 204
• “Length Max” on page 205
• “Length Match” on page 208
• “Length Tol” on page 209
Separation Distance Max See “Separation Distance Max” on page 212.
Index
Constraint class, 105

Index
— Symbols — Net class, 100

# Pins, 197, 200, 214 Design
# Vias Max, 203 Preferences, 37
— Numerics — Setup, 37
2-pin, 38 Design-flow manuals, 157
Differential pair
—A— Assign rules, 145
Analog, 201 Define automatically, 19, 142
Define manually, 141
—B— Differential Spacing, 171, 213
Back-end, 157 Discrete component prefixes, 38
Before you begin, 29 Display
—C— Settings, 37
Capture net constraints, 147 Units, 42
Clearance rule sets
—E—
Assign, 22, 114
EBD pin pairs, 127
Create, 21, 111
Electrical
Clearances, 172 Preferences, 38
Colors, 41
Rules, 24, 101
Concurrent design, 27
Units, 45
Constraint Engineering format, 45
Classes, 24, 101
Templates, 148 —F—
Constraint class Filters, 70, 74
Add nets, 102 Find, 69
Copy, 104 Fonts, 41
Create, 24, 101 Front-end, 27
Delete, 105
Constraint Reference, 161 —G—
Constraint template General
Apply, 149 Clearance rules, 108
Cross probing, 12, 34 Options, 37
Cross select, 12, 34 Preferences, 37
Customization, 48 —I—
—D— Index (Clearances), 174
Delay Index (Trace and Via Properties), 164
Rules, 131
Delete

—L— Search, 69
Layout, 157 Separation Distance Max, 212
Length Delta, 210 Series, 220
Length Manhattan, 206 Settings, 37
Length Match, 208 SMD Pad to Trace, 179
Length Max, 205 SMD Pad to Via, 183
Length Min, 204 Spreadsheet pages, 59
Length Min Length, 207 Status Bar, 48
Length Range, 211 Stub Length Max, 202
Length Tol, 209
—T—
—M— Toolbars, 49
Manhattan length, 132 Topology Type, 199
Matching delay, 133 Trace and Via Properties, 163
Trace and via rules, 108
—N— Trace to Trace, 176
Navigator, 48 Trace to Via, 178
Net Class, 198 Trace Width Expansion, 170
Net class Trace Width Minimum, 168
Add nets, 17, 98 Trace Width Typical, 169
Copy, 100 Type, 165, 175
Delete, 100
Nets, 194 —V—
Validate constraints, 87
—O— Via Assignments, 166
Options, 37 Via rules, 108
Output, 48 Via to Via, 182
—P— —W—
Pad to Via, 181 Window customization, 48
Part Number, 217
Part Type, 219
Parts, 215
Pin Package Length, 221
—Q—
Qty, 218
—R—
Roll back, 91
Route, 167
—S—
Same constraints
Electrical rules, 104
Physical rules, 100
Save, 93
Schematic, 157

End-User License Agreement
with EDA Software Supplemental Terms
Use of software (including any updates) and/or hardware is subject to the End-User License Agreement together with the
Mentor Graphics EDA Software Supplement Terms. You can view and print a copy of this agreement at:
mentor.com/eula

Constraint Manager User's Manual: Release PADS VX.2.7

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Constraint Manager User's Manual: Release PADS VX.2.7

Uploaded by

Copyright:

Available Formats

Constraint Manager User's Manual

Release PADS VX.2.7

© 2004-2020 Mentor Graphics Corporation

Mentor Graphics Corporation

Send Feedback on Documentation: support.mentor.com/doc_feedback_form

Revision Changes Status/Date

Constraint Manager User's Manual, PADS VX.2.7

Revision History ISO-26262

Constraint Manager User's Manual, PADS VX.2.7 5

Default Keyboard Shortcuts Provided With Constraint Manager . . . . . . . . . . . . . . . . . . . . . 52

6 Constraint Manager User's Manual, PADS VX.2.7

Viewing All Constraint Violations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Constraint Manager User's Manual, PADS VX.2.7 7

Defining Discrete Component Pin Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

8 Constraint Manager User's Manual, PADS VX.2.7

Trace Width Minimum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Constraint Manager User's Manual, PADS VX.2.7 9

Part Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

10 Constraint Manager User's Manual, PADS VX.2.7

Starting and Exiting From Constraint Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Starting and Exiting From Constraint Manager

• Load a design in your schematic tool.

Constraint Manager User's Manual, PADS VX.2.7 11

• Launch Constraint Manager.

Table 1-1. Starting Constraint Manager Through the Menu Path

Cross Probing Between Design Systems and

12 Constraint Manager User's Manual, PADS VX.2.7

• Enable cross probing mode in both tools.

2. You can cross probe in these ways:

Constraint Manager User's Manual, PADS VX.2.7 13

Figure 1-1. Cross Probing From Constraint Manager

Viewing Clearance and Trace Constraints

14 Constraint Manager User's Manual, PADS VX.2.7

Creating Net Classes

In the example, the ddr3_group* classes (ddr3_group0, ddr3_group1, ddr3_group2, and

• Make a net class.

Constraint Manager User's Manual, PADS VX.2.7 15

• Modify physical constraints.

16 Constraint Manager User's Manual, PADS VX.2.7

Adding Nets to a Net Class

• Filter the spreadsheet.

Constraint Manager User's Manual, PADS VX.2.7 17

5. Click , then click Apply or OK.

18 Constraint Manager User's Manual, PADS VX.2.7

Defining Differential Pairs Automatically

• Find net pairs that match a search criteria.

Constraint Manager User's Manual, PADS VX.2.7 19

20 Constraint Manager User's Manual, PADS VX.2.7

Creating Clearance Rule Sets

Constraint Manager User's Manual, PADS VX.2.7 21

• Create clearance rules.

Assigning Class-To-Class Clearance Rules

Also, as you make these assignments, it is important to be aware of the following:

22 Constraint Manager User's Manual, PADS VX.2.7

• Enable the Clearances toolbar.

Constraint Manager User's Manual, PADS VX.2.7 23

3. Continue making rule assignments between net classes.

4. After you finish, click Apply or OK.

Creating Constraint Classes

• Create a constraint class.

24 Constraint Manager User's Manual, PADS VX.2.7

• Change some length constraints for the differential pair.

Constraint Manager User's Manual, PADS VX.2.7 25