Constraint Manager User's Manual

Release X-ENTP VX.2.8

Document Revision 6
Unpublished work. © Siemens 2020

This document contains information that is confidential and proprietary to Mentor Graphics Corporation, Siemens
Industry Software Inc., or their affiliates (collectively, "Siemens"). 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 confidential and proprietary information.

This document is for information and instruction purposes. Siemens 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 Siemens to determine whether any changes have been made.

The terms and conditions governing the sale and licensing of Siemens products are set forth in written agreements
between Siemens and its customers. End User License Agreement — You can print a copy of the End User
License Agreement from: mentor.com/eula.

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 Siemens whatsoever.

SIEMENS MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE,
AND NON-INFRINGEMENT OF INTELLECTUAL PROPERTY.

SIEMENS SHALL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL OR
PUNITIVE DAMAGES, LOST DATA OR PROFITS, EVEN IF SUCH DAMAGES WERE FORESEEABLE, ARISING
OUT OF OR RELATED TO THIS PUBLICATION OR THE INFORMATION CONTAINED IN IT, EVEN IF SIEMENS
HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

LICENSE RIGHTS APPLICABLE TO THE U.S. GOVERNMENT: This document explains the capabilities of
commercial products that were developed exclusively at private expense. If the products are acquired directly or
indirectly for use by the U.S. Government, then the parties agree that the products and this document are
considered "Commercial Items" and "Commercial Computer Software" or "Computer Software Documentation," as
defined in 48 C.F.R. §2.101 and 48 C.F.R. §252.227-7014(a)(1) and (a)(5), as applicable. Software and this
document may only be used under the terms and conditions of the End User License Agreement referenced above
as required by 48 C.F.R. §12.212 and 48 C.F.R §227.7202. The U.S. Government will only have the rights set forth
in the End User License Agreement, which supersedes any conflicting terms or conditions in any government order
document, 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 Siemens or
other parties. No one is permitted to use these Marks without the prior written consent of Siemens or the owner of
the Marks, as applicable. The use herein of third party Marks is not an attempt to indicate Siemens as a source of a
product, but is intended to indicate a product from, or associated with, a particular third party. A list of Siemens'
trademarks may be viewed at: www.plm.automation.siemens.com/global/en/legal/trademarks.html and
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.

Support Center: support.sw.siemens.com

Send Feedback on Documentation: support.sw.siemens.com/doc_feedback_form
 Revision History ISO-26262

Revision Changes Status/Date

6 Modifications to title page to reflect the latest product version Released
supported. Approved by Regis Krug. November
All technical enhancements, changes, and fixes listed in the 2020
Xpedition Enterprise Flow Release Notes for this product are
reflected in this document. Approved by Mike Bare.
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
Xpedition Enterprise Flow Release Notes for this product are
reflected in this document. Approved by Mike Bare.
4 Modifications to title page to reflect the latest product version Released
supported. Approved by Regis Krug. September
All technical enhancements, changes, and fixes listed in the 2019
Xpedition Enterprise Flow Release Notes for this product are
reflected in this document. Approved by Mike Bare.
3 Modifications to title page to reflect the latest product version Released
supported. Approved by Regis Krug. February
All technical enhancements, changes, and fixes listed in the 2019
Xpedition Enterprise Flow Release Notes for this product are
reflected in this document. Approved by Mike Bare.

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, X-ENTP VX.2.8

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, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Table of Contents

Revision History ISO-26262

Chapter 1
Getting Started Videos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Front-End Getting Started Videos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Starting and Exiting From Constraint Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Cross Probing Between Design Systems and Constraint Manager . . . . . . . . . . . . . . . . . . 19
Specifying General Clearance Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Creating Rule-Area Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Creating Clearance Rule Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Creating Net Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Assigning Nets to Net Classes Using Constraint Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Defining Differential Pairs Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Creating Constraint Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Manually Defining Netline Ordering (From-Tos) for a Specific Net. . . . . . . . . . . . . . . . . 32
Creating Placement Clusters in a Schematic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Back-End Getting Started Videos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Starting and Exiting From Constraint Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Cross Probing Between Design Systems and Constraint Manager . . . . . . . . . . . . . . . . . . 36
Specifying Power-Supply Nets Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Specifying Trace Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Creating a Rule Area in Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Updating Clearance Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Assigning Class-To-Class Clearance Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Creating and Deleting Net Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Defining Differential Pairs Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Creating Constraint Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Creating a Constraint Class to Assign Nets and Tolerances. . . . . . . . . . . . . . . . . . . . . . . . 51
Ordering Nets With Netline Manipulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Other Videos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Importing HyperLynx Stackups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Importing Polar Speedstacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Defining Parallelism Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Assigning Parallelism Rules to Nets and Constraint Classes . . . . . . . . . . . . . . . . . . . . . . . 58

Chapter 2
Quick References and Work Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Quick Reference - Constraint Manager Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Quick Reference - Constraint Manager GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Edit Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Constraint Manager User's Manual, X-ENTP VX.2.8 5

 Table of Contents

Setup Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Filters Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Tools Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Data Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Output Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Constraint Manager Work Flows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Schematic-Design Work Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
PCB-Layout Work Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Chapter 3
Overview and Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Constraint-Driven Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Before You Begin Using Constraint Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Xpedition Enterprise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Keyin Netlist-Xpedition Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Differential Pairs Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Static Team Layout and Xpedition Team Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Overview of Electrical Nets and Physical Nets in Constraint Manager . . . . . . . . . . . . . . . 89
Automatically Recognized Topologies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Electrical Nets Defined Through a Package With More Than Two Pins . . . . . . . . . . . . . . 91
Importing a Layout Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Importing a 2005.x Ces.prefs File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Starting and Exiting From Constraint Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Starting Constraint Manager in Standalone Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Viewing Constraint Database Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Folder Structure and Location of Constraint Manager Log Files . . . . . . . . . . . . . . . . . . . . . 94
Cross Probing Between Design Systems and Constraint Manager . . . . . . . . . . . . . . . . . . . . 95
Constraint Manager Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Specifying Design Configuration Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Specifying Electrical Net Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Specifying Discrete Component Prefixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Using a Configuration File to Specify Design Preferences . . . . . . . . . . . . . . . . . . . . . . . . 100
Setting Display Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Setting General Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Setting Fonts and Colors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Setting Spreadsheet Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Setting Unit Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Specifying Other Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Reusing Settings in External Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Display Customization of Constraint Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Toggling the Display of Windows and Toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Changing the Position of Windows and Toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Folder Location of the ces.ini Configuration File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Toolbar Customization of Constraint Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Toggling Toolbar Buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Modifying Toolbars to Create Custom Sets of Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Modifying Individual Toolbar Buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Creating New Toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

6 Constraint Manager User's Manual, X-ENTP VX.2.8

Table of Contents

Renaming and Deleting Custom Toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Resetting a Toolbar to the Default Grouping of Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Customize Dialog Box - Options Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Constraint Set Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Creating or Modifying Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Deleting User-Created Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Constraint Set Propagation to a Team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Associating user.cns Files With a Mentor Graphics Software Release . . . . . . . . . . . . . . . 126
Adding Custom Menu Selections to the Tools Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Customizing Command Shortcut Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Default Keyboard Shortcuts Provided With Constraint Manager . . . . . . . . . . . . . . . . . . . . . 129
Selecting or Creating Valor NPI Design Centers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Sharing Valor NPI Design Centers Among Team Members. . . . . . . . . . . . . . . . . . . . . . . . . 131

Chapter 4
Constraint Spreadsheet Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Constraint Definition Through Spreadsheet Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Overview of Constraint Hierarchy and Overrides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Choosing From Among Change Impact Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Required Propagation Rules That Constraint Manager Maintains . . . . . . . . . . . . . . . . . . . 138
Organization of Constraints Into Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Spreadsheet Page Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Selecting a Spreadsheet Page Using the Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Selecting a Spreadsheet Page Using the Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Displaying Only Specific Constraint Types on a Spreadsheet Page . . . . . . . . . . . . . . . . 142
Displaying All Constraint Types on a Spreadsheet Page . . . . . . . . . . . . . . . . . . . . . . . . . 142
Spreadsheet Icons Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Resizing Spreadsheet Columns and Rows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Zooming the Display of Spreadsheet Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Expanding and Collapsing Spreadsheet Rows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Sorting Spreadsheet Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Deletion of Constraint Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Deleting Constraint Values at the Constraint Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Deleting Constraint Values at the Object Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Deleting Constraint Values at the Design Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Constraint Value Copy-and-Paste Between Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Removing Unused Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Searching for Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Filtering Spreadsheet Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Filtering the Spreadsheet by Row Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Resetting a Spreadsheet to its Default View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Constraint Group Creation and Modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Creating Constraint Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Modifying a Constraint Group From Directly Within the Spreadsheet . . . . . . . . . . . . . . . 158
Modifying a Constraint Group From Within the Constraint Groups Dialog Box . . . . . . . 158
Deleting One or More Constraint Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Restoring the Content of a Default Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Concurrent Constraint Entry With Other Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Constraint Manager User's Manual, X-ENTP VX.2.8 7

 Table of Contents

Overview of Constraint Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Showing Indication of Remotely Changed Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Constraint Value Commenting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Adding Comments to Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Editing Constraint Comments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Deleting Constraint Comments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Viewing Constraint Comments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Viewing Constraint Reference Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Viewing Design Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Checking Constraints Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Constraint Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Checking Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Correcting Constraint Manager Diagnostics Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Listing of Constraint Manager Diagnostics Tests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
PCB Actuals Comparison With Constraint Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Validating PCB Actuals Against Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Updating Actuals Displayed in Constraint Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Clearing Actuals From the Spreadsheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Sharing PCB Actuals With Front-End Constraint Manager Sessions . . . . . . . . . . . . . . . . 176
Viewing All Constraint Violations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Constraint Violation Revision Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Update of Electrical Net Data and Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Painting Rules to Reuse Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Constraint Change Undo and Redo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Rolling Back and Undoing All Constraint Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Rolling Back or Redoing Specific Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Supported Undo/Redo Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Viewing and Reverting to Parent Cell Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Saving Constraint Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Chapter 5
Net Class Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Creating Net Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Adding Nets to a Net Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Creating a Net Class From an Existing Net Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Deleting Net Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Chapter 6
Constraint Class Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Creating Constraint Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Creating Constraint Class Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Adding Nets to a Constraint Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Defining Bus Constraint Classes Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Types of Net Matching for Bus Constraint Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Creating a Constraint Class From an Existing Constraint Class . . . . . . . . . . . . . . . . . . . . . . 198
Deleting Constraint Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

8 Constraint Manager User's Manual, X-ENTP VX.2.8

Table of Contents

Chapter 7
Physical Rule Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Specifying General Clearance Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Rule-Area Scheme Creation and Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Creating Rule-Area Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Copying Rule-Area Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Renaming Rule-Area Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Deleting Rule-Area Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Resetting Clearance Rules to the Master Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
(Minimum) Scheme Clearances and Widths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Specifying Trace Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Trace Width Rule Propagation Through Layers for Hierarchical Net Classes . . . . . . . . . . . 212
Defining Via Assignments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Clearance Rule Set Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Creating Clearance Rule Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Defining Clearance Rules for a Rule Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Creating Z-Axis Clearance Rule Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Defining Z-Axis Clearance Rules for a Rule Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Defining Embedded Resistor Clearance Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Defining SMD Clearance Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Defining Bond Finger Clearance Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Clearance Rule Set Assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Assigning Class-To-Class Clearance Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Deleting Class-To-Class Clearance Rule Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Assigning Z-Axis Class-To-Class Clearance Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Deleting Z-Axis Class-To-Class Clearance Rule Assignments . . . . . . . . . . . . . . . . . . . . . 231
Package Clearance Rule Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Assigning Package Clearance Type Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Deleting Package Clearance Type Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Assigning Package-Type-to-Package-Type Clearance Rules. . . . . . . . . . . . . . . . . . . . . . . 233
Deleting Package-Type-to-Package-Type Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Package Side and End Determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
3D Clearance Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Defining 3D Clearances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
3D Clearance Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Chapter 8
Net Constraint Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Specifying General Net Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Topology Specification for Nets and Constraint Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Topology Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Specifying Topology Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Manually Defining Netline Ordering (From-Tos) for a Specific Net. . . . . . . . . . . . . . . . . 247
Changing Topology Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Overriding Trace Width Constraints for From-Tos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Advanced Topology Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Creating Pin Sets to Construct Advanced Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Changing the Order of Pin-Set Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254

Constraint Manager User's Manual, X-ENTP VX.2.8 9

 Table of Contents

Deleting Pin Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

Net Pin Pair Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Internal Component-Pin Delay Inclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Creating All Pin Pairs Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Creating Only Source-Load Pin Pairs Automatically. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Creating Pin Pairs Semi-Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Creating Pin Pairs Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Deleting One or More Pin Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Defining Discrete Component Pin Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Length and Delay Rule Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Specifying Length or Delay Rules for Nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Net Length and Delay Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Tolerance Routing of Nets Within a Constraint Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Specifying Maximum Length as a Percentage Above Manhattan Length . . . . . . . . . . . . . 266
Matching Delay or Length Rules Among Nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Matching Length or Delay Tolerance at the Constraint Class Level . . . . . . . . . . . . . . . . . 268
Formula Creation and Error Checking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Defining Formulas to Create Net Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Including Formula Tolerance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Tolerance Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Multiple Formula Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Solving Formulas to Check for Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Complex Formula Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Constant and Variable Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Creating Constants and Variables for Delay Rules and Formulas . . . . . . . . . . . . . . . . . . . 277
Deleting Specific Constants or Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Finding Variable References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Simulated Delay Specification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Specifying Simulated Delay Rules for Nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Signal Edge Rates and Crosstalk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Matching Simulated Delay Rules Among Nets or Constraint Classes . . . . . . . . . . . . . . . . 281
Defining Overshoot and Ringback Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Power-Supply Net and Constraint Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Net Names Constraint Manager Automatically Recognizes as Power-Supply Nets . . . . . 287
Specifying Power-Supply Nets Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Specifying Power-Supply Nets Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Defining Constraints for Power-Supply Nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Changing Power-Supply Nets Back Into Nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
Modifying Xpedition I/O Designer FPGA Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Defining Constraints for Single-Pin Nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Display Pattern Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Defining Net Display Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Applying Display Patterns in Host Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

Chapter 9
Differential Pair Creation and Pair Rule Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Defining Differential Pairs Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Defining Differential Pairs Automatically. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

10 Constraint Manager User's Manual, X-ENTP VX.2.8

Table of Contents

Assigning Rules to Differential Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

IBIS Model [Diff_Pin] Section Declarations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308

Chapter 10
Parallelism and Crosstalk Rule Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Overview of Parallelism and Crosstalk Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Defining Parallelism Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Assigning Parallelism Rules to Nets and Constraint Classes . . . . . . . . . . . . . . . . . . . . . . . . 313
Importing Parallelism Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
ParallelRules.txt File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
Navigating to Assigned Parallelism Rules From the Nets Page . . . . . . . . . . . . . . . . . . . . . . 321
Defining Crosstalk Rules for Nets and Constraint Classes . . . . . . . . . . . . . . . . . . . . . . . . . . 322

Chapter 11
Constraint Template Creation and Reuse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Creating Constraint Templates to Capture Net Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . 325
Constraints and Values Stored With Each Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Constraint Template Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Guidelines for Applying Constraint Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Applying a Constraint Template to Multiple Nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Applying Constraint Templates From the Constraint Templates Page . . . . . . . . . . . . . . . 330
Applying a Constraint Template to a Single Net . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Device Pattern Matching With Constraint Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Modifying Pin Matching for an Applied Constraint Template. . . . . . . . . . . . . . . . . . . . . . 332
Updating Nets With Constraint Template Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
Reusing Constraint Templates in External Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

Chapter 12
Constraint Export and Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Export of Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Constraint Export in Encrypted XML Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Choosing From the Entire Set of Constraint Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Exporting Only Selected Nets or Spreadsheet Rows . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
Exporting Constraints in CSV Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
Exporting Constraints in Encrypted ASCII Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Decrypting and Encrypting Exported Constraint Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Import of Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
Importing Constraints in Encrypted XML Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
Importing Constraints in CSV Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
CSV Importer Error and Warning Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
CSV Format Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
Example CSV Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
Guidelines for CSV Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351

Chapter 13
Stackup Display and Modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
Viewing or Modifying Stackup Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
Stackup File Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361

Constraint Manager User's Manual, X-ENTP VX.2.8 11

 Table of Contents

Importing HyperLynx Stackups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361

Importing Polar Speedstacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Layer Name Correlation Among Design Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
Stackup Editing Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364

Chapter 14
Part-Model Assignment Verification and Part Constraints Definition . . . . . . . . . . . . . . . 365
Automatic Assignment of IBIS Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
IBIS Models or Technology Models? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
IBIS Models Delivered With Constraint Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Part Model Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Specifying Model Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Specifying Individual Model Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
Reloading Model Directories and Individual Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
Verifying Default Model Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Assigning Models to Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
Editing Model Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Updating Part Model Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Overriding IBIS Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Defining Thermal Constraints for Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
Importing Pin Package Delay or Length Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
PinPkgDelays.txt File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
PinPkgLengths.txt File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378

Chapter 15
Signal Integrity Exploration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Sending Nets to HyperLynx LineSim . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Exporting Constraint Enhancements From HyperLynx LineSim . . . . . . . . . . . . . . . . . . . . . 382
Updating Constraint Manager With Constraint Enhancements. . . . . . . . . . . . . . . . . . . . . . . 383

Chapter 16
Design Tool Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
Constraint and Design Change Management Between Tools . . . . . . . . . . . . . . . . . . . . . . . . 385
Synchronization of Constraint Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Sending Schematic Data to Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
Sending Layout Data to Schematics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
Schematic Constraints Conflict Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Resolving Schematic Constraint Conflicts Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Viewing Constraint Resolution Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390

Appendix A
Constraint Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Constraint Reference Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Trace and Via Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
Display Pattern (Trace and Via Properties) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Via Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400

12 Constraint Manager User's Manual, X-ENTP VX.2.8

Table of Contents

Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Trace Width Minimum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
Trace Width Typical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Trace Width Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
Typical Impedance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
Differential Typical Impedance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Differential Spacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
Differential Via Spacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
Clearances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
Trace To Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
Trace To Pad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
Trace To Via . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Trace To Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
Trace To SMD Pad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
Pad To Pad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
Pad To Via . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Pad To Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Via To Via . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
Via To Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Via To SMD Pad. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
Plane To Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
Embedded Resistor To Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
Embedded Resistor To Pad. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Embedded Resistor To Via . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
Embedded Resistor To Resistor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
EP Mask To Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
EP Mask To Pad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
EP Mask To Via . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
EP Mask To Resistor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Bond Finger To Bond Finger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
Bond Finger To Trace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
Bond Finger To Pad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
Bond Finger To Via . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
Bond Finger To Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
Bond Finger To SMD Pad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
Z-Axis Clearances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
Trace To Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
Trace To Pad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
Trace To Via . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
Trace To Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
Trace To SMD Pad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
Nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
Hierarchical Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
# Pins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
Power Net . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
Analog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462

Constraint Manager User's Manual, X-ENTP VX.2.8 13

 Table of Contents

Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
Net Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
Display Pattern (Nets). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
Template Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
Template Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
Topology Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
Topology Ordered. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
Stub Length Max . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
# Vias Max . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
# Test Points Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
Backdrill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
Restricted Layer Length Max External. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
Restricted Layer Length Max Internal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
From To Constraints Layer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
From To Constraints Trace Width . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
From To Constraints Z0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
Length or TOF Delay Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
Length or TOF Delay Min . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
Length or TOF Delay Max . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
Length or TOF Delay Manhattan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
Length or TOF Delay Min Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Length or TOF Delay Match . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
Length or TOF Delay Tol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
Length or TOF Delay Delta . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
Length or TOF Delay Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
Formulas Formula. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
Formulas Violation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
Static Low Overshoot Max . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
Static High Overshoot Max . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
Dynamic Low Overshoot Max . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
Dynamic High Overshoot Max. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
Ringback Margin High Min . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
Ringback Margin Low Min . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
Non-Monotonic Edge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502
Single Ended Characteristic Impedance Value. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
Single Ended Characteristic Impedance Tol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
Simulated Delay Edge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
Simulated Delay Min . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
Simulated Delay Max . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
Simulated Delay Max Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
Simulated Delay Match To . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
Simulated Delay Match . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
Simulated Delay Offset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
Simulated Delay Tol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
Differential Pair Tol Max . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
Differential Pair Phase Tol Max . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
Differential Pair Phase Tol Distance Max . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
Differential Pair Phase Tol Actual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
Convergence Tolerance Max . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519

14 Constraint Manager User's Manual, X-ENTP VX.2.8

Table of Contents

Distance to Convergence Max . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520

Separation Distance Max . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
Differential Spacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
Differential Impedance Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523
Differential Impedance Tolerance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
I/O Standard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
Power Net Constraints Supply Voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
Power Net Constraints Max Voltage Drop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
Power Net Constraints Max Current Density . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
Power Net Constraints Max Via Current . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
Hierarchical Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
Part Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
Qty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
Part Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
Series. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
IBIS Component Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
IBIS Pin Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
Schematic Pin Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Topology Pin Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
Pin Package Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
Pin Package Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
Thermal Power Dissipation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
Thermal Power Scaling Factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
Thermal Theta-jc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
Thermal Casing Temperature Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
Thermal Junction Temperature Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
I/O Standard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
Noise Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
Noise Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
Constraint Class or Electrical Net Name Victim . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
Constraint Class or Electrical Net Name Aggressor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
Parallelism Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
Crosstalk Max . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
Crosstalk Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
Constraint Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558

Appendix B
Command-Line Tools Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
ceschk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
CesSyncCheck . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
cons2ascii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
cons2csv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
cons2xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
csv2dat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571
ImportPinPackageDelays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572

Constraint Manager User's Manual, X-ENTP VX.2.8 15

 Table of Contents

ImportPinPackageLengths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
ImportStk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
sandboxfile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
Index
End-User License Agreement
with EDA Software Supplemental Terms

16 Constraint Manager User's Manual, X-ENTP VX.2.8

 Chapter 1
Getting Started Videos

Learn to use Constraint Manager by watching how-to videos that show common tasks in action
for a schematic engineer or layout designer. You can also watch a selection of other videos.

Front-End Getting Started Videos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Back-End Getting Started Videos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Other Videos. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Constraint Manager User's Manual, X-ENTP VX.2.8 17

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Getting Started Videos
Front-End Getting Started Videos

Front-End Getting Started Videos

These topics are ordered to reflect the typical Constraint Manager workflow for schematic
engineers.
Starting and Exiting From Constraint Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Cross Probing Between Design Systems and Constraint Manager. . . . . . . . . . . . . . . . . 19
Specifying General Clearance Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Creating Rule-Area Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Creating Clearance Rule Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Creating Net Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Assigning Nets to Net Classes Using Constraint Editor . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Defining Differential Pairs Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Creating Constraint Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Manually Defining Netline Ordering (From-Tos) for a Specific Net . . . . . . . . . . . . . . . 32
Creating Placement Clusters in a Schematic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

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 or layout tool.

• Launch Constraint Manager.

18 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Getting Started Videos
Cross Probing Between Design Systems and Constraint Manager

Schematic Tool Layout Tool

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
Xpedition Designer Tools > Constraint
Manager
Xpedition Layout 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.

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 97.

Constraint Manager User's Manual, X-ENTP VX.2.8 19

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Getting Started Videos
Cross Probing Between Design Systems and Constraint Manager

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
Watch the video to learn how to:

• Enable cross probing mode.

• Highlight an object in your schematic or layout tool and view the result in Constraint
Manager.
• Highlight an object in Constraint Manager and view the result in your schematic or
layout tool.
Schematic Tool Layout 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.

20 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Getting Started Videos
Specifying General Clearance Rules

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

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.
For example, the minimum distance between testpoint centers is a general clearance rule that
you set globally and do not define between net classes. For a complete listing of general
clearance rules, refer to Table 1-2 on page 22.

Video
Watch the video to learn how to:

• Choose the Clearances tab.

• Display the Clearances toolbar.

Constraint Manager User's Manual, X-ENTP VX.2.8 21

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Getting Started Videos
Specifying General Clearance Rules

• View general clearance rules and values.

Procedure
1. On the Clearances toolbar, click ; or, from the Edit menu, click Clearances, then
click General Clearances.
2. In the General Clearance Rules dialog box, modify rules that have an editable value. The
tool sets editable rule values against a white background. Refer to the table for
explanations of each general clearance rule.
3. After you finish, click OK.

Table 1-2. General Clearance Rules

Rule Defines the... Minimum Maximum Default
Value Value Value
Cavity Inside Edge Minimum acceptable distance 0 1 in 10 th
to Parts between the inside edge of a
cavity and all parts.
Cavity Outside Edge Smallest acceptable distance 0 1 in 10 th
to Non-Plane between the outside edge of a
Conductor cavity and all non-plane
conductors.
Cavity Outside Edge Minimum acceptable distance 0 1 in 10 th
to Plane Conductor between the outside edge of a
cavity and all plane conductors.
Cavity Edge to Smallest acceptable distance 0 1 in 10 th
Cavity Edge between a cavity edge and all
other cavity edges.
Contour, Cavity & Minimum acceptable distance 0 1 in 10 th
Mounting Hole to between a mounting hole
Mounting Hole (including contour and cavity) and
all other mounting holes.

22 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Getting Started Videos
Specifying General Clearance Rules

Table 1-2. General Clearance Rules (cont.)

Rule Defines the... Minimum Maximum Default
Value Value Value
Contour & Smallest acceptable distance 0 1 in 10 th
Mounting Hole to between a mounting hole and all
Non-Plane non-plane conductors.
Conductor
Placement Outline to Minimum acceptable distance 0 1 in 10 th
Placement Outline between a placement outline and
all other placement outlines.
Placement Outline to Smallest acceptable distance 0 1 in 10 th
Placement Obstruct between a placement outline and
all placement obstructs.
Placement Outline to Minimum acceptable distance 0 1 in 10 th
Design Edge between a placement outline and
all design edges.
Trace to Resistor Smallest acceptable distance 1 nm 1 in 10 th
between a trace segment and all
resistors.
Pad to Resistor Minimum acceptable distance 1 nm 1 in 10 th
between a pad and all resistors.
Testpoint Center to Smallest acceptable distance 1 nm 1 in 10 th
Testpoint Center between the center of a testpoint
and all other testpoint centers.
Additional Hole Minimum acceptable additional 0 1 in 0
Conductor clearance between specific pin
Clearances: and via holes within pads and
• Drill Hole conductors (traces and planes).
• Laser Hole These clearance values must not
exceed the size of the annular ring
• Punched Hole
for the associated pads.
• Photo Hole
Note: The router also adds the
Drill Hole clearance to
mounting holes.

Note
All Additional Hole Conductor Clearances are valid whether contact pads exist or
not.

Constraint Manager User's Manual, X-ENTP VX.2.8 23

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Getting Started Videos
Creating Rule-Area Schemes

Figure 1-2. Additional Hole Conductor Clearances Example

Creating Rule-Area Schemes

You can create additional schemes (aside from the (Master) scheme) that correspond to rules
areas created in the PCB (or that you expect to create in the PCB). After you create a scheme,
you can define trace and via rules and clearance rule sets to which only nets crossing or within
that board area must adhere.
Note
To understand how the layout software applies rules in overlapping rule areas, see “Batch
DRC for Overlapping Rule Areas” in Layout Verification Guide.

Video
Watch the video to learn how to:

• Learn the difference between (Master) and (Minimum) schemes.

• View trace constraints.

24 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Getting Started Videos
Creating Clearance Rule Sets

• View default clearance values.

Procedure
1. In the Navigator, right-click Schemes, then click New Scheme.
2. Replace the default name “<user>_New” with a unique name for the scheme, keeping
the following in mind:
• You can use spaces.
• You cannot use these characters: ! \ “ and /
3. Press Enter.

Creating Clearance Rule Sets

After you create a scheme to represent a rule area on a PCB, you can specify clearance rules to
which net objects within the rule area must adhere. You can define clearance rules such as Trace
to Pad, SMD Pad to Trace, Resistor to Via, and Via to Plane.
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
Watch the video to learn how to:

• Observe a Trace Width Typical value.

• Create a clearance rule.
• Define a Trace to Trace value for the rule.

Constraint Manager User's Manual, X-ENTP VX.2.8 25

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Getting Started Videos
Creating Net Classes

• Assign a clearance rule between net classes.

Procedure
1. Do one of the following.
• In the Navigator, expand Schemes, right-click a specific scheme, then click New
Clearance Rule.
• On the Clearances spreadsheet page, right-click a scheme, then click New
Clearance Rule.
2. Replace the default name “<user>_New” with a unique name for the clearance rule set.
You can use spaces in clearance rule set names.
Results
The rule set now exists for constraint definition and assignment between net classes.

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.

26 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Getting Started Videos
Creating Net Classes

Figure 1-3. 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
Watch the video to learn how to:

• Make a net class.

• Search for and add nets to it.

Constraint Manager User's Manual, X-ENTP VX.2.8 27

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Getting Started Videos
Creating Net Classes

• Make an additional net class.

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. Although you are not limited to the levels of net-class
hierarchy you can create, 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: ! \ “ /
• 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.

28 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Getting Started Videos
Assigning Nets to Net Classes Using Constraint Editor

Assigning Nets to Net Classes Using Constraint

Editor
Use Constraint Editor to view or edit constraint data directly within your schematic tool or
layout tool.
Video
Watch the video to learn how to:

• Select nets in the schematic tool.

• Invoke Constraint Editor.
• Change constraint values.

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 46.

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.
Video
Watch the video to learn how to:

• Locate the nets on the schematic.

Constraint Manager User's Manual, X-ENTP VX.2.8 29

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Getting Started Videos
Defining Differential Pairs Manually

• Create a net class for the differential pair.

• Create the differential pair.

Procedure
1. Do one of the following:
• 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.
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 1-4. Differential Pair

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. To select multiple rows for simultaneous deletion, use
Ctrl-click and Shift-click.

30 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Getting Started Videos
Creating Constraint Classes

Creating Constraint Classes

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
Watch the video to learn how to:

• Create a constraint class.

• Add a differential pair to the constraint class.
• View constraint class assignments.

Procedure
1. Do one of the following:
• 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:
• You cannot use these characters: ! \ “ /
• 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.

Constraint Manager User's Manual, X-ENTP VX.2.8 31

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Getting Started Videos
Manually Defining Netline Ordering (From-Tos) for a Specific Net

• 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.

Manually Defining Netline Ordering (From-Tos) for

a Specific Net
After you set the Topology Type constraint for a net to “Custom” or “Complex,” you must order
the net.
Video
Watch the video to learn how to:

• Enable the Topology toolbar.

• Display the Netline Order dialog box.
• Create from-to connections.
• Observe changes to the Ordered column.

Procedure
1. Do one of the following:
• On the Nets spreadsheet page, click the row of the net for which you want to
manually define netline ordering, then on the Topology toolbar, click .

• After you click a net row, from the Edit menu, click Netline Order.
2. In the list of available pins, click a row to select the From pin.

Note
If defining from-tos between pin sets, select pin sets instead of pins in both the From
and To fields. Also, you can select both types of objects.

3. In the list of available pins, click a row to select the To pin.

32 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Getting Started Videos
Creating Placement Clusters in a Schematic

4. Verify the From pin and To pin fields, then click . If the From pin and To pin fields do
not contain the correct pins, click to clear the designation.

Note
As you create from-tos, you may find that not enough source (S) pins or load (L)
pins exist, and you cannot create a valid topology. If this occurs, you must exit the
dialog box and switch to the Parts spreadsheet page. From there, you can change the
Topology Pin Type constraint of one or more relevant component pins, and then start
this procedure over again.

5. Repeat steps 2 through 4 for each from-to you want to create. After you finish, click
OK.

Tip
To automatically create pin pairs from each from-to, select the “Automatically
create pin pairs from from-tos” check box. In the example, five pin pairs were
created, each matching a from-to.

Figure 1-5. Automatically Created Pin Pairs

Creating Placement Clusters in a Schematic

Create placement clusters by adding certain properties to groups of symbols in your schematic
tool. You can use the clusters later for placement activities in your layout tool.

Constraint Manager User's Manual, X-ENTP VX.2.8 33

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Getting Started Videos
Creating Placement Clusters in a Schematic

Video
Watch the video to learn how to:

• Add a cluster property to multiple symbols on two sheets.

• Add a cluster property and a room property to block symbols.
• Add and edit sheet text.

34 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Getting Started Videos
Back-End Getting Started Videos

Back-End Getting Started Videos

These topics are ordered to reflect the typical Constraint Manager workflow for layout
designers.
Starting and Exiting From Constraint Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Cross Probing Between Design Systems and Constraint Manager. . . . . . . . . . . . . . . . . 36
Specifying Power-Supply Nets Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Specifying Trace Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Creating a Rule Area in Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Updating Clearance Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Assigning Class-To-Class Clearance Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Creating and Deleting Net Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Defining Differential Pairs Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Creating Constraint Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Creating a Constraint Class to Assign Nets and Tolerances . . . . . . . . . . . . . . . . . . . . . . 51
Ordering Nets With Netline Manipulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

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 or layout tool.

• Launch Constraint Manager.

Constraint Manager User's Manual, X-ENTP VX.2.8 35

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Getting Started Videos
Cross Probing Between Design Systems and Constraint Manager

Schematic Tool Layout Tool

Procedure
1. Launch your design tool.
2. From your design tool, click the Constraint Manager icon ( ) or use its menu path.

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

Design Tool Menu Path
Xpedition Designer Tools > Constraint
Manager
Xpedition Layout 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.

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 97.

36 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Getting Started Videos
Cross Probing Between Design Systems and Constraint Manager

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
Watch the video to learn how to:

• Enable cross probing mode.

• Highlight an object in your schematic or layout tool and view the result in Constraint
Manager.
• Highlight an object in Constraint Manager and view the result in your schematic or
layout tool.
Schematic Tool Layout 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.

Constraint Manager User's Manual, X-ENTP VX.2.8 37

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Getting Started Videos
Specifying Power-Supply Nets Manually

Figure 1-6. 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

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.

38 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Getting Started Videos
Specifying Power-Supply Nets Manually

Video
Watch the video to learn how to:

• Select the Power Net constraint.

• Define the Supply Voltage constraint.
• View the total set of power and ground nets in a certain net class.

Procedure
1. Select the Nets spreadsheet page.
2. Do any of the following:
• 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.
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

Constraint Manager User's Manual, X-ENTP VX.2.8 39

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Getting Started Videos
Specifying Trace Constraints

Specifying Trace Constraints

After you create a scheme to represent a rule area on a PCB, you can specify trace constraints to
which nets within the rule area must adhere. You can simultaneously define trace rules for all
board layers for nets in a net class, or do so individually for each board layer.
When specifying trace constraints, you can define values such as minimal, typical, and
expansion trace widths, typical impedance, and differential pair spacing. You can also override
these values for from-tos that must route on specific board layers.

Note
If you change the value for typical trace width, the field solver uses the existing board
stackup to calculate typical impedance. Likewise, if you change the value for typical
impedance, the tool uses the field solver to calculate typical width.

Video
Watch the video to learn how to:

• Change Trace Width constraints.

• Modify Differential Spacing.
• Verify constraint propagation to layers.

Procedure
1. Do one of the following:
• On the Trace & Via Properties spreadsheet page, expand a scheme.
• In the Navigator, expand Schemes, expand a specific scheme, then click Trace &
Via Properties.
2. Expand the (Default) net class, or a unique net class you created previously, then define
trace constraints in one of the following ways:
• To simultaneously define trace rules for all board layers, in the net class name row
(for example, (Default)), specify each value.

40 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Getting Started Videos
Creating a Rule Area in Layout

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
press Enter. Constraint Manager updates each board layer to include this Minimum
Trace Width value.
Figure 1-7. Trace Width Constraints

• To individually define constraints for each board layer, in the appropriate board
layer row (for example, SIGNAL_1), specify each value.

Note
When specifying layers to route, you must do so in the (Master) scheme. When
working on a net class in the Master scheme and you change a net class via to
(None), the tool automatically changes all user-defined schemes to (None) for that
net class.

For example, to specify a Trace Width Expansion value of 12 th for board layers one
and two of the (Default) net class, in the SIGNAL_1 and SIGNAL_2 rows, type 12
in the Expansion cell.
Figure 1-8. Trace Width Constraints at the Layer Level

Creating a Rule Area in Layout

Create a new rule scheme with specific constraints. Add a rule area based on that scheme to
override the default board level constraints in a specific region. Rule areas are useful in areas
where device pin pitch patterns make routing difficult.

Constraint Manager User's Manual, X-ENTP VX.2.8 41

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Getting Started Videos
Updating Clearance Constraints

Video
Watch the video to learn how to:

• Define a rule scheme.

• Add a rule area based on the scheme.

Related Topics
Overview of Rule Areas [Layout Operations and Reference Guide]
Adding Rule Areas for Fine Pitch Devices [Cell Editor User's Guide]
Batch DRC for Overlapping Rule Areas [Layout Verification Guide]
Creating Rule Areas [Layout Routing Solutions Guide]

Updating Clearance Constraints

Update clearance constraints to specify required minimum distances between objects such as
traces and pads.
Video
Watch the video to learn how to:

• View Trace To values.

• Modify a few values.
• Override hierarchy warnings.

42 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Getting Started Videos
Assigning Class-To-Class Clearance Rules

Assigning Class-To-Class Clearance Rules

After you create clearance rule sets for a rule-area scheme, 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, a common concern is high voltage nets in a design that need certain
spacing around them based on the voltage level of each net.

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

• The tool obeys class-to-class clearance rules 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) use (Default Rule). This assignment
in the matrix is hardcoded into the top-left cell as (All) to (All).
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 25.
Video
Watch the video to learn how to:

• Display the Class to Class Clearances dialog box.

• Ensure that the dialog box shows the correct scheme.
• Assign a rule between two net classes.

Constraint Manager User's Manual, X-ENTP VX.2.8 43

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Getting Started Videos
Assigning Class-To-Class Clearance Rules

Procedure
1. On the Clearances toolbar, click ; or, from the Edit menu, click Clearances, then click
Class to Class Clearance Rule.
2. In the Class to Class Clearances dialog box, in the “Net Class to Class Clearance Rules
for Scheme” pulldown, select a scheme.

Tip
Many schemes use the same rule assignments and you can save time by
prepopulating a scheme with the assignments of another scheme. To do so, click .
In the Select source scheme dialog box, select a scheme, then click OK.

3. Populate cells in any of 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.
• Clone certain cell assignments of another scheme — Select one or more cells,
right-click, click Clone rules from scheme, then click a scheme.
• Copy and paste — Select one or more continuous 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-9. Highlighting Shows Cell Changes

4. Continue making rule assignments between net classes.

Tip
Optionally, to revert all changes, click . To undo a single change, right-click a cell,
then click Restore initial rule.

5. To assign class-to-class clearance rules for a different scheme, return to step 2.

44 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Getting Started Videos
Assigning Class-To-Class Clearance Rules

6. After you finish, click Apply or OK.

Examples
Example of Clearance Rule Assignments
In this example, there are four net classes (10th, 20th, 30th, and 40th), and the (Default) net
class. There are also four clearance rules of the same name. Each of the clearance rules defines
all clearance constraints to the same value as the name of the clearance rule set. The clearance
constraints defined for (Default Rule) are all set to 5 th.

Figure 1-10. Clearance Rule Assignments by Net Class

The usage of common names for net classes and clearance rule sets is only for the illustrative
purposes of this example, but you may find it useful to group nets into classes based on this
style of naming.

Here is a listing of all clearance rule assignments based on the dialog box example:

• (Default Rule) is the hardcoded assignment between all net classes, (All) and (All). If all
other cells in this picture where empty, (Default) would be the only rule assigned
between every possible pairing of net classes. The middle callout in the picture is an
example of this. If it is blank, it uses (Default Rule).
• The clearance rule 10th is assigned between the net class 10th and all other net classes.
• The clearance rule 20th is assigned between the net class 20th and all other net classes.
• The clearance rule 30th is assigned between the net class 30th and all other net classes.

Constraint Manager User's Manual, X-ENTP VX.2.8 45

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Getting Started Videos
Creating and Deleting Net Classes

• The clearance rule 40th is assigned between the net class 40th and all other net classes.
• The clearance rule 10th is assigned between the net class 20th and itself. This means that
nets within this class can use smaller clearances (based on the definitions in the rule set).
• The clearance rule 20th is assigned between the net class 30th and itself. This means that
nets within this class can use smaller clearances (based on the definitions in the rule set).
• The clearance rule 30th is assigned between the net class 40th and itself. This means that
nets within this class can use smaller clearances (based on the definitions in the rule set).
Related Topics
Creating Clearance Rule Sets

Creating and Deleting Net Classes

Create net classes to group nets for the purpose of assigning the same physical constraint values
to them. You can delete them as needed.
Video
Watch the video to learn how to:

• Create two net classes.

• Move nets into each class.
• Delete a net class.

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.

46 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Getting Started Videos
Defining Differential Pairs Automatically

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
Watch the video to learn how to:

• Determine the differential pair naming suffix.

• Search the net list for signals matching the search criteria.
• Select the nets to join into differential pairs.
• Assign a net class to the differential pair signals.

Procedure
1. Do one of the following:
• 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.
• IBIS Models — Group nets into differential pairs based on differential pin
definitions in available IBIS models.

Note
After selecting this method, click , then proceed to step 5.

Constraint Manager User's Manual, X-ENTP VX.2.8 47

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Getting Started Videos
Defining Differential Pairs Automatically

• 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-11. Automatic Assignment of Differential Pairs

48 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Getting Started Videos
Creating Constraint Groups

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.

Creating Constraint Groups

You can create groups that include just a subset of the constraints displayed on a spreadsheet
page. For example, if your constraint modifications are limited to a common subset of Nets
spreadsheet constraints, you can create a group that includes just those constraints.

Constraint Manager User's Manual, X-ENTP VX.2.8 49

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Getting Started Videos
Creating Constraint Groups

Doing so gives you the ability to increase the efficiency with which you modify constraints. If
managing other co-workers, creating unique groups can help to ensure that their focus remains
on the appropriate constraint subsets.

Note
Because constraint groups are a subset of all constraints located on a spreadsheet page,
modifying a spreadsheet constraint while in a group view results in the change appearing in
all views.

In the illustration, a user has created two constraint groups that serve as custom subsets of the
Nets spreadsheet page.

Figure 1-12. Constraint Groups

The My Delays Group is a subset containing all delay constraints, both simulated and time of
flight. The other group, My Actuals Group, contains all actual values that are available on the
Nets spreadsheet page.

You can modify constraint groups that you create, and also those that are included with
Constraint Manager by default. The only group that you cannot modify is All. To provide you
with greater flexibility, the tool supports two ways of populating and modifying the contents of
a constraint group. The recommended approach is from directly within the spreadsheet.

Video
Watch the video to learn how to:

• Select a group.
• Add constraints to the group.

50 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Getting Started Videos
Creating a Constraint Class to Assign Nets and Tolerances

• Save changes to the group.

Procedure
1. Do one of the following:
• With the spreadsheet page of interest active, click the Filters - Groups toolbar
dropdown, then click Edit Constraint Groups.
• From the Edit menu, click Constraint Groups.
2. In the Edit Constraint Groups dialog box, click .

3. In the Create New Constraint Group dialog box, type a name for the group, then click
OK.

Note
You cannot use the same name for groups on different spreadsheet pages. For
example, to create a group called “Critical” on both the Nets and Parts pages,
prepend the name with the page name (as in, “Nets_Critical” and “Parts_Critical”).

4. Click Apply.
5. Modify or populate the contents of the constraint group in one of these ways:
• “Modifying a Constraint Group From Directly Within the Spreadsheet” on page 158.
This is the recommended method. You can drag-and-drop columns and visually
review your progress while you make your changes.
• “Modifying a Constraint Group From Within the Constraint Groups Dialog Box” on
page 158.

Creating a Constraint Class to Assign Nets and

Tolerances
Create a constraint class and then assign nets and tolerances to the new class.

Constraint Manager User's Manual, X-ENTP VX.2.8 51

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Getting Started Videos
Ordering Nets With Netline Manipulation

Video
Watch the video to learn how to:

• Create a new class.

• Assign nets to the new class.
• Define net tolerances.
• Save the new class.

Ordering Nets With Netline Manipulation

Although you use Constraint Manager to define topologies, visualization of the actual
connections when components are placed can make it easier for you to determine net order.
Video
Watch the video to learn how to:

• Open display control in the layout tool.

• Change the display of netlines.
• Change the order of nets.
• View the custom ordering in Constraint Manager.

52 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Getting Started Videos
Other Videos

Other Videos
These topics are ordered alphabetically.
Importing HyperLynx Stackups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Importing Polar Speedstacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Defining Parallelism Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Assigning Parallelism Rules to Nets and Constraint Classes. . . . . . . . . . . . . . . . . . . . . . 58

Importing HyperLynx Stackups

Import a HyperLynx stackup into Constraint Manager to replace the current stackup for a
design.
Restrictions and Limitations
• You cannot import a different layer type into an existing layer.
• You cannot import stackups into Rigid Flex designs.
• You cannot import a stackup into a schematic invocation of Constraint Manager if the
PCB design exists. You must also import a layout template into Constraint Manager
before importing the stackup.
Video
Watch the video to learn how to:

• View the current stackup.

• Select a HyperLynx stackup to import.
• Map layers to preserve constraints.
• View the new stackup.

Constraint Manager User's Manual, X-ENTP VX.2.8 53

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Getting Started Videos
Importing Polar Speedstacks

Procedure
1. Import a HyperLynx stackup file in one of the following ways:

If you want to ... Do the following ...

Import through the GUI Refer to the video in this topic.
Import from the command Refer to “ImportStk” on page 576.
line

2. Load the stackup changes into the layout design by clicking the rightmost indicator light
in the layout tool (do not use the Project Integration dialog box to accomplish this). You
can also load the changes by instead closing and reopening Constraint Manager.

Note
You must back annotate to view the updated stackup in schematic invocations of
Constraint Manager.

Results
The Stackup Editor shows the updated stackup. You can now make additional modifications as
needed.

Importing Polar Speedstacks

Import a Polar Speedstack into Constraint Manager to replace the current stackup for a design.
You can also select impedance structures that define values for Trace Width and Differential
Spacing constraints.
Restrictions and Limitations
• You cannot import a different layer type into an existing layer.
• You cannot import stackups into Rigid Flex designs.
• You cannot import a stackup into a schematic invocation of Constraint Manager if the
PCB design exists. You must also import a layout template into Constraint Manager
before importing the stackup.
Video
Watch the video to learn how to:

• Select a Polar Speedstack to import.

• Select impedance structures.

54 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Getting Started Videos
Defining Parallelism Rules

• View updated Trace Width and Differential Spacing values.

Procedure
1. Import a Polar Speedstack file in one of the following ways:

If you want to ... Do the following ...

Import through the GUI Refer to the video in this topic.
Import from the command Refer to “ImportStk” on page 576.
line

2. Load the stackup changes into the layout design by clicking the rightmost indicator light
in the layout tool (do not use the Project Integration dialog box to accomplish this). You
can also load the changes by instead closing and reopening Constraint Manager.

Note
You must back annotate to view the updated stackup in schematic invocations of
Constraint Manager.

Results
The Stackup Editor shows the updated stackup. You can now make additional modifications as
needed.

Defining Parallelism Rules

You can create rules that define parallelism requirements for net segments that are on the same
layer, adjacent layers, or both. To accomplish this, you specify a combination of edge-to-edge
spacing between segments and the maximum length that segments can run in parallel without
violation.
By defining parallelism rules, you can help control the amount of crosstalk by restricting
excessive segment parallelism. You can create as many edge-to-edge and maximum length
combinations as you require. For example, a parallelism rule that contains three edge-to-edge

Constraint Manager User's Manual, X-ENTP VX.2.8 55

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Getting Started Videos
Defining Parallelism Rules

and maximum length combinations for net segments on the same layer could specify these
rules:

• Segments with an edge-to-edge spacing of 10 th can run parallel for no more than 100
th.
• Segments with an edge-to-edge spacing of 100 th can run parallel for no more than
1,000 th.
• Segments with an edge-to-edge spacing of 1,000 th can run parallel for no more than
10,000 th.
Figure 1-13. Example Parallelism Rule Definition

The example illustration shows what this looks like in the tool. Because the layout system
interpolates the available parallelism rules to account for undefined Edge / Edge values, you can
define rules as broadly or narrowly as you require.

Note
Interpolation of these rules means that the layout system mathematically determines an
appropriate Max Parallel Len value for an undefined Edge / Edge value that falls between
two defined Edge / Edge values. Using interpolation based on the example rules, an Edge / Edge
value of 50 th produces a Max Parallel Len requirement of 500 th.

Prerequisites
• You should have an understanding of whether to use parallelism or crosstalk rules. For
more information, refer to “Overview of Parallelism and Crosstalk Rules” on page 309.
Video
Watch the video to learn how to:

• Modify the assignment on the Noise Rules page.

56 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Getting Started Videos
Defining Parallelism Rules

• Define pairings of edge spacing values and run lengths.

Procedure
1. Do one of the following:
• On the Pairs toolbar, click .

• From the Edit menu, click Parallelism Rules, then click Define Parallelism Rules.
2. In the Define Parallelism Rules dialog box, next to the Parallelism rules heading, click
, then change the default name of the new rule (“New”) to a meaningful title.

Tip
Instead of creating a new rule, you can use an existing parallelism rule as a clone and
then modify it to meet the needs of the unique rule. To do so, in the list of existing
parallelism rules, click one, then click .

3. Define an edge-to-edge spacing and maximum length combination for each same layer
rule or adjacent layer segment rule you want this parallelism rule set to include by
performing one of these tasks:
• To define a same layer segment rule, next to the Same layer trace segments heading,
click , then type an Edge / Edge value and a Max Parallel Len value.

• To define an adjacent layer segment rule, next to the Adjacent layer trace segments
heading, click , then type an Edge / Edge value and a Max Parallel Len value.

Note
You can define a negative Edge / Edge value (for example, -2) to allow for
segment overlap between adjacent layers.

Tip
You can also create adjacent layer segment rules by cloning existing same layer
segment rules. To do so, next to the Adjacent layer trace segments heading, click
. If cloning, all rules are recreated. You can remove rules you do not need by
clicking a row, then clicking .

Constraint Manager User's Manual, X-ENTP VX.2.8 57

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Getting Started Videos
Assigning Parallelism Rules to Nets and Constraint Classes

4. After you finish typing edge-to-edge and maximum parallel length combinations, click
OK.

Note
The maximum length value associated with an edge-to-edge value cannot be greater
than the maximum length value associated with a larger edge-to-edge value. For
example, after you define an edge-to-edge and maximum length combination of 10 th
and 1200 th, an edge-to-edge value of 8 th must be accompanied by a maximum length
value that is less than the maximum length value of the previous set (that is, 1200 th). If
you type incorrect values, the tool changes the cell background to red and it does not
save the data in the cell until you correct the value.

Examples
The following parallelism rule allows for trace segment overlap between adjacent layers
through the definition of a negative Edge / Edge value. Segments overlapping by more than 2 th
can run in parallel for no more than 20 th.

Assigning Parallelism Rules to Nets and Constraint

Classes
After you define parallelism rules, you can apply them to specific pairs of nets and constraint
classes by creating net-to-net or class-to-class parallelism rule assignments. Each parallelism
rule assignment includes two specific nets or constraint classes and the parallelism rule to which
they must adhere.
In addition, you can apply all parallelism rules that you have created to the nets or constraint
classes that comprise a parallelism rule assignment. In the example illustration, the noise rule
Bus1 assigns parallelism rule PR1 between all nets in the Memory constraint class.

58 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Getting Started Videos
Assigning Parallelism Rules to Nets and Constraint Classes

Figure 1-14. Parallelism Rule Assignment

Video
Watch the video to learn how to:

• Enable the Noise Rules page.

• Assign a parallelism rule between two constraint classes.
• Modify the assignment on the Noise Rules page.

Procedure
1. Do one of the following:
• On the Pairs toolbar, click .

• From the Edit menu, click Parallelism Rules, then click Assign Parallelism Rules.

Tip
On the Noise Rules spreadsheet page, right-click, then click New. Modify the Noise
Type, Constraint Class or Electrical Net Name Victim and Aggressor, and
Parallelism Rule fields using the appropriate field selector. For example, because Class-
Class is the default parallelism type, if assigning a net-to-net parallelism rule, click to
change this field to Net-Net. When assigning parallelism rules using the Assign
Parallelism Rules dialog box, you can access it from the Edit menu by clicking
Parallelism Rules, then clicking Assign Parallelism Rules.

2. In the Assign Parallelism Rules dialog box, in the Noise rule type field, specify a net-to-
net or class-to-class assignment.
3. In the list of available electrical nets or constraint classes, select the nets or constraint
classes that will comprise the first half of the pairing (that is, reference nets or classes),
then next to the Victim constraint class(es) or Victim electrical net(s) box, click .

Constraint Manager User's Manual, X-ENTP VX.2.8 59

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Getting Started Videos
Assigning Parallelism Rules to Nets and Constraint Classes

Tip
To select multiple nets or constraint classes, use Ctrl-click, Shift-click, or click-drag.
To select nets or constraint classes by name, in the field below the list of source nets
or net classes, type a search string, then click .

4. In the list of nets or constraint classes, select the nets or constraint classes that will
comprise the second half of the pairing (that is, apply rules to nets or constraint classes),
then next to the Aggressor constraint class(es) or Aggressor electrical net(s) box, click .

Note
If assigning a parallelism rule to constraint classes, you can select all constraint
classes by using the (All Classes) selection. The selection (All) refers to the default
constraint class (All).

For example, to check for same net or same constraint class parallelism, select the nets
or constraint classes you chose in step 3.
5. In the Parallelism rule box, select a specific parallelism rule. To view detailed
information about each of the available rules, click . You can also create a parallelism
rule in the resulting dialog box.
6. (Optional) Define a maximum crosstalk value for these pairings of electrical nets or
constraint classes. To do so, in the Max crosstalk box, type the maximum amount of
crosstalk that the victim nets or constraint classes can receive from the aggressor nets or
constraint classes.
7. Make sure the lists of nets or constraint classes is accurate. To remove items from either
list, click to select them, then click the corresponding .

8. Click Apply or OK.

Examples
Example of Assigning a Parallelism Rule Between a Single Constraint Class and All Other
Constraint Classes
In this example, you want to assign a parallelism rule between nets in a single constraint class
with nets in all other constraint classes. The parallelism rule includes same-layer, adjacent-
layer, segment, edge-to-edge, and maximum parallelism rule lengths. The nets in the single
constraint class are critical nets with strict parallelism requirements.

1. In the Assign Parallelism Rules dialog box, in the Noise rule type field, make sure Class
to Class is selected.
2. In the list of Available constraint class(es), select the single constraint class to associate
with all other constraint classes, then next to the Victim constraint class(es) list, click .

3. In the list of Available constraint class(es), select the (All Classes) row, then next to the
Aggressor constraint class(es) list, click .

60 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Getting Started Videos
Assigning Parallelism Rules to Nets and Constraint Classes

4. In the Parallelism rule field, click the dropdown, select the parallelism rule to assign
between the single constraint class and all other constraint classes, then click OK.
In the illustration, the Noise Rules spreadsheet shows that parallelism rule G10L100/
G15L150 is assigned between constraint class HT_CONN_IN and all other constraint
classes.
Figure 1-15. Single Constraint Class and All Other Constraint Classes
Parallelism Rule Assignment

Related Topics
Navigating to Assigned Parallelism Rules From the Nets Page
Noise Rules

Constraint Manager User's Manual, X-ENTP VX.2.8 61

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Getting Started Videos
Assigning Parallelism Rules to Nets and Constraint Classes

62 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Chapter 2
Quick References and Work Flows

This section includes quick references and work flows that help you learn to use Constraint
Manager in a minimal amount of time.

Quick Reference - Constraint Manager Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Quick Reference - Constraint Manager GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Constraint Manager Work Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Constraint Manager User's Manual, X-ENTP VX.2.8 63

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Quick References and Work Flows
Quick Reference - Constraint Manager Commands

Quick Reference - Constraint Manager

Commands
Use this reference to quickly find specific Constraint Manager commands. The topic organizes
commands alphabetically by design object and then action. Click within the Topic column to
jump to the corresponding topic for one of the commands.

Table 2-1. Constraint Manager Commands

Design Action Command Topic
Object
3D clearances Define Edit menu > Clearances > 3D “Defining 3D Clearances”
Clearances on page 239
Bus Define (auto) Edit menu > Auto Bus “Defining Bus Constraint
constraint Classes Automatically” on
class page 196
Clearance Assign Edit menu > Clearances > Class to “Assigning Class-To-Class
rule set Class Clearance Rule Clearance Rules” on
page 43
Clearance Create Navigator > expand Schemes > “Creating Clearance Rule
rule set right-click a scheme > New Sets” on page 25
Clearance Rule
Constant Create Edit menu > Constants and “Creating Constants and
Variables > Edit Variables for Delay Rules
and Formulas” on page 277
Constraint Export File menu > Export > Constraints “Exporting Constraints in
Encrypted ASCII Format”
on page 341
Constraint Import File menu > Import > Constraints “Import of Constraints” on
page 343
Constraint Rollback File menu > Rollback Changes “Rolling Back and
Undoing All Constraint
Changes” on page 181
Constraint Search Edit menu > Find “Searching for
Constraints” on page 150
Constraint View Info Right-click a constraint cell > “Viewing Constraint
Constraint Help Reference Information” on
page 167
Constraint Add nets Nets tab > Edit menu > Assign “Adding Nets to a
class Nets to Classes Constraint Class” on
page 194

64 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Quick References and Work Flows
Quick Reference - Constraint Manager Commands

Table 2-1. Constraint Manager Commands (cont.)

Design Action Command Topic
Object
Constraint Copy Navigator > expand Constraint “Creating a Constraint
class constraints Classes > right-click a constraint Class From an Existing
class > Clone Constraint Class” on
page 198
Constraint Create Navigator > right-click Constraint “Creating Constraint
class Classes > New Constraint Class Classes” on page 31
Constraint Rename Navigator > expand Constraint “Creating Constraint
class Classes > right-click a constraint Classes” on page 31
class > Rename
Constraint Create Filters - Group toolbar dropdown > “Creating Constraint
group Edit Constraint Groups > Groups” on page 49
Constraint Apply Nets tab > Edit menu > Apply “Constraint Template
template Constraint Template Application” on page 328
Constraint Create Nets tab > right-click an electrical “Creating Constraint
template net ( ) > Create Constraint Templates to Capture Net
Template Constraints” on page 325
Constraint Reuse File menu > Export > Constraints “Reusing Constraint
template (external) Templates in External
Designs” on page 334
Default rules Revert Navigator > expand Schemes > “Resetting Clearance Rules
right-click a scheme > Reset to to the Master Scheme” on
(Master) page 208
Design Set up Setup menu > Settings “Specifying Design
configuration Configuration Preferences”
on page 97
Differential Create (auto) Edit menu > Differential Pairs > “Defining Differential
pair Auto Assign Differential Pairs Pairs Automatically” on
page 46
Differential Create Nets tab > select two nets > Edit “Defining Differential
pair (manual) menu > Differential Pairs > Pairs Manually” on
Differential Pair from Selected Net page 29
Discrete pin Define Parts tab > right-click a top-level “Defining Discrete
pair discrete > Create Component Pin Component Pin Pairs” on
Pairs page 259
Formula Define Nets tab > Formulas Formula cell “Defining Formulas to
Create Net Relationships”
on page 271

Constraint Manager User's Manual, X-ENTP VX.2.8 65

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Quick References and Work Flows
Quick Reference - Constraint Manager Commands

Table 2-1. Constraint Manager Commands (cont.)

Design Action Command Topic
Object
Formula Solve Data menu > Solve All Formulas “Solving Formulas to
Check for Errors” on
page 274
From-to Define Nets tab > set Topology Type cell “Manually Defining
to Custom > Edit menu > Netline Netline Ordering (From-
Order Tos) for a Specific Net” on
page 32
General Specify Edit > Clearances > General “Specifying General
clearance Clearances Clearance Rules” on
rules page 21
Net Analyze Nets tab > right-click an electrical “Sending Nets to
signal net ( ) > Display Net in HyperLynx LineSim” on
integrity HyperLynx LineSim page 381
Net Specify Nets tab > Filters - Group toolbar “Specifying Length or
length or dropdown > Delays and Delay Rules for Nets” on
delay rules Lengths page 263
Net class Add Nets Trace & Via Properties tab > Edit “Adding Nets to a Net
menu > Assign Nets to Classes Class” on page 188
Net class Copy Navigator > expand Net Classes > “Creating a Net Class
constraints right-click a net class > Clone From an Existing Net
Class” on page 189
Net class Create Navigator > right-click Net “Creating Net Classes” on
Classes > New Net Class page 26
Net class Rename Navigator > expand Net Classes > “Creating Net Classes” on
right-click a net class > Rename page 26
Package Assign Edit menu > Clearances > Assign “Assigning Package-Type-
clearance Package Type Clearances to-Package-Type
type rules Clearance Rules” on
page 233
Parallelism Assign Edit menu > Parallelism Rules > “Assigning Parallelism
rules Assign Parallelism Rules Rules to Nets and
Constraint Classes” on
page 58
Parallelism Define Edit menu > Parallelism Rules > “Defining Parallelism
rules Define Parallelism Rules Rules” on page 55
Parallelism Navigate Nets tab > right-click a net or “Navigating to Assigned
rules constraint class > Navigate to Parallelism Rules From the
Parallelism Rule Nets Page” on page 321

66 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Quick References and Work Flows
Quick Reference - Constraint Manager Commands

Table 2-1. Constraint Manager Commands (cont.)

Design Action Command Topic
Object
Part model Assign Parts tab > IBIS Component Name “Assigning Models to
and Technology cells > Parts” on page 371
Part model Verify Data menu > Model Audit Report “Verifying Default Model
Assignments Assignments” on page 370
Pin package Import File menu > Import > Package “Importing Pin Package
delays or Delays Delay or Length Values”
lengths on page 374
Pin pair Create (auto) Nets tab > right-click a net row > “Creating All Pin Pairs
Auto Pin Pair Generation Automatically” on
page 257
Pin pair Create Nets tab > click a net row > Edit “Creating Pin Pairs Semi-
(manual) menu > Pin Pairs > Add Pin Pairs Automatically” on
page 258
Pin pair Specify Nets tab > Filters - Group toolbar “Specifying Length or
length or dropdown > Delays and Delay Rules for Nets” on
delay rules Lengths page 263
Pin set Create Nets tab > click a net row > “Creating Pin Sets to
Topology toolbar > > > Construct Advanced
Netline Order dialog box > , , Topologies” on page 252
, , or > select pins > Finish
Rule-area Create Navigator > right-click Schemes > “Creating Rule-Area
scheme New Scheme Schemes” on page 24
Stackup Edit Edit menu > Stackup “Viewing or Modifying
Stackup Properties” on
page 359
Topology Specify Nets tab > click a net row > “Topology Specification
(custom) Topology toolbar > > for Nets and Constraint
Classes” on page 245
Topology Specify (pre- Nets tab > click a net row > “Topology Specification
defined) Topology toolbar > , , , , or for Nets and Constraint
Classes” on page 245

Trace & via Override Nets tab > From To Constraints “Overriding Trace Width
rules widths (from- Trace Width cell Constraints for From-Tos”
to) on page 250
Trace & via Specify Trace & Via Properties tab > “Specifying Trace
rules expand a scheme Constraints” on page 40

Constraint Manager User's Manual, X-ENTP VX.2.8 67

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Quick References and Work Flows
Quick Reference - Constraint Manager Commands

Table 2-1. Constraint Manager Commands (cont.)

Design Action Command Topic
Object
Units Set Setup menu > Settings > Display “Setting Spreadsheet
Units and Notation Units” on page 104
Variables Create Edit menu > Constants and “Creating Constants and
Variables > Edit Variables for Delay Rules
and Formulas” on page 277
Variables Find Edit menu > Constants and “Finding Variable
references Variables > Find Variables References” on page 279
Reference
Z-axis Assign Edit menu > Clearances > Z-Axis “Assigning Z-Axis Class-
clearance rule Class to Class Clearance Rule To-Class Clearance Rules”
set on page 229
Z-axis Create Z-Axis Clearances tab > right- “Creating Z-Axis
clearance rule click an existing rule set > New Clearance Rule Sets” on
set page 220

68 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Quick References and Work Flows
Quick Reference - Constraint Manager GUI

Quick Reference - Constraint Manager GUI

Use this reference to quickly determine the purpose of specific menu selections available
through the tool’s graphical user interface.
File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Edit Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Setup Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Filters Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Tools Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Data Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Output Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Constraint Manager User's Manual, X-ENTP VX.2.8 69

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Quick References and Work Flows
File Menu

File Menu
Read a command’s purpose or click within the Topic/Purpose column to view the
documentation associated with a specific File menu command.

Table 2-2. File Menu Selections

Menu Command Topic/Purpose
File > Rollback Changes “Rolling Back and Undoing All Constraint Changes” on
page 181
File > Open Project Open a .prj file if you launch Constraint Manager in
standalone mode.
File > Close Project Close a .prj file you opened in standalone Constraint
Manager.
File > Reload Project Reload a .prj file if you get disconnected from the iCDB
Server.
File > New Script Create a constraints automation script. For more
information, see Constraints Automation Manual.
File > Open Script Open a constraints automation script.
File > Page Setup Set up paper and orientation options for printing.
File > Print Setup Set up your printer.
File > Print Preview View preview of a print job.
File > Print Print spreadsheet content.
File > File Viewer “Viewing Constraint Database Log Files” on page 94
File > Import > Stackup “Stackup File Import” on page 361
File > Import > Layout Template “Importing a Layout Template” on page 91
File > Import > Constraints “Importing Constraints in Encrypted XML Format” on
page 343
File > Import > Constraints from “Importing Constraints in CSV Format” on page 344
encrypted CSV
File > Import > Constraint “Reusing Constraint Templates in External Designs” on
Template page 334
File > Import > Settings “Reusing Settings in External Designs” on page 108
File > Import > Preferences File “Importing a 2005.x Ces.prefs File” on page 92
File > Import > Package Delays “Importing Pin Package Delay or Length Values” on
page 374
File > Export > Constraints “Constraint Export in Encrypted XML Format” on page 339

70 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Quick References and Work Flows
File Menu

Table 2-2. File Menu Selections (cont.)

Menu Command Topic/Purpose
File > Export > Constraints to “Exporting Constraints in Encrypted ASCII Format” on
encrypted ASCII page 341
File > Export > Constraints to “Exporting Constraints in CSV Format” on page 340
CSV
File > Export > Constraint “Reusing Constraint Templates in External Designs” on
Template page 334
File > Export > Settings “Reusing Settings in External Designs” on page 108
File > Export > Actuals “Sharing PCB Actuals With Front-End Constraint Manager
Sessions” on page 176
File > Exit Exit Constraint Manager.

Constraint Manager User's Manual, X-ENTP VX.2.8 71

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Quick References and Work Flows
Edit Menu

Edit Menu
Read a command’s purpose or click within the Topic/Purpose column to view the
documentation associated with a specific Edit menu command.

Table 2-3. Edit Menu Selections

Menu Command Topic/Purpose
Edit > Undo Undo last operation.
Edit > Redo Redo last undo operation.
Edit > Cut Cut selection.
Edit > Copy Copy selection.
Edit > Paste Paste selection.
Edit > Delete Delete selection.
Edit > Rule Painter “Painting Rules to Reuse Constraints” on page 179
Edit > Find “Searching for Constraints” on page 150
Edit > Pin Pairs > Add Pin Pairs “Creating Pin Pairs Manually” on page 259
Edit > Pin Pairs > Auto Pin Pair “Creating All Pin Pairs Automatically” on page 257
Generation
Edit > Pin Pairs > Auto Source- “Creating Only Source-Load Pin Pairs Automatically” on
Load Pin Pair Generation page 258
Edit > Netline Order “Manually Defining Netline Ordering (From-Tos) for a
Specific Net” on page 32
Edit > Differential Pairs > “Defining Differential Pairs Manually” on page 29
Differential Pair from Selected
Nets
Edit > Differential Pairs > Auto “Defining Differential Pairs Automatically” on page 46
Assign Differential Pairs
Edit > Power Nets > Change “Specifying Power-Supply Nets Manually” on page 38
Nets to Power Nets
Edit > Power Nets > Auto Create “Specifying Power-Supply Nets Automatically” on
Power Nets page 288
Edit > Assign Nets to Classes “Adding Nets to a Net Class” on page 188
Edit > Auto Bus “Defining Bus Constraint Classes Automatically” on
page 196
Edit > Parallelism Rules > “Defining Parallelism Rules” on page 55
Define Parallelism Rules

72 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Quick References and Work Flows
Edit Menu

Table 2-3. Edit Menu Selections (cont.)

Menu Command Topic/Purpose
Edit > Parallelism Rules > “Assigning Parallelism Rules to Nets and Constraint
Assign Parallelism Rules Classes” on page 58
Edit > Clearances > Assign “Assigning Package-Type-to-Package-Type Clearance
Package Type Clearances Rules” on page 233
Edit > Clearances > Reset to “Resetting Clearance Rules to the Master Scheme” on
Master page 208
Edit > Clearances > General “Specifying General Clearance Rules” on page 21
Clearances
Edit > Clearances > Class to “Assigning Class-To-Class Clearance Rules” on page 43
Class Clearance Rule
Edit > Clearances > Z-Axis “Creating Z-Axis Clearance Rule Sets” on page 220
Clearances
Edit > Clearances > Z-Axis “Assigning Z-Axis Class-To-Class Clearance Rules” on
Class to Class Clearance Rule page 229
Edit > Clearances > 3D “Defining 3D Clearances” on page 239
Clearances
Edit > Constants and Variables > “Creating Constants and Variables for Delay Rules and
Edit Formulas” on page 277
Edit > Constants and Variables > “Finding Variable References” on page 279
Find Variables Reference
Edit > Via Assignments “Defining Via Assignments” on page 213
Edit > Apply Constraint “Constraint Template Application” on page 328
Template
Edit > Constraint Definitions “Creating or Modifying Constraints” on page 121
Edit > Constraint Groups “Creating Constraint Groups” on page 49
Edit > Stackup “Viewing or Modifying Stackup Properties” on page 359

Constraint Manager User's Manual, X-ENTP VX.2.8 73

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Quick References and Work Flows
View Menu

View Menu
Read a command’s purpose or click within the Topic/Purpose column to view the
documentation associated with a specific View menu command.

Table 2-4. View Menu Selections

Menu Command Topic/Purpose
View > Expand > Selected | All “Expanding and Collapsing Spreadsheet Rows” on
page 145
View > Collapse > Selected | All “Expanding and Collapsing Spreadsheet Rows” on
page 145
View > Reset Row Heights “Resizing Spreadsheet Columns and Rows” on page 143
View > Reset Column Widths “Resizing Spreadsheet Columns and Rows” on page 143
View > Reset View “Resetting a Spreadsheet to its Default View” on page 155
Views > Tabs “Toggling the Display of Windows and Toolbars” on
page 110
View > Navigator “Toggling the Display of Windows and Toolbars” on
page 110
View > Output “Toggling the Display of Windows and Toolbars” on
page 110
View > Status Bar “Toggling the Display of Windows and Toolbars” on
page 110
View > Remotely Modified Data “Showing Indication of Remotely Changed Constraints”
> Refresh on page 163
View > Remotely Modified Data “Showing Indication of Remotely Changed Constraints”
> Enable Indication on page 163
View > Toolbars “Toggling the Display of Windows and Toolbars” on
page 110
View > Toolbars > Customize “Toolbar Customization of Constraint Manager” on
page 115

74 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Quick References and Work Flows
Setup Menu

Setup Menu
Read a command’s purpose or click within the Topic/Purpose column to view the
documentation associated with a specific Setup menu command.

Table 2-5. Setup Menu Selections

Menu Command Topic/Purpose
Setup > Settings “Specifying Design Configuration Preferences” on page 97
and “Constraint Manager Setup” on page 97
Setup > Cross Probing “Cross Probing Between Design Systems and Constraint
Manager” on page 19
Setup > Shortcuts “Customizing Command Shortcut Keys” on page 128

Constraint Manager User's Manual, X-ENTP VX.2.8 75

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Quick References and Work Flows
Filters Menu

Filters Menu
Read a command’s purpose or click within the Topic/Purpose column to view the
documentation associated with a specific Filters menu command.

Table 2-6. Filters Menu Selections

Menu Command Topic/Purpose
Filters > Enabled “Filtering Spreadsheet Data” on page 152
Filters > Cumulative Mode “Filtering Spreadsheet Data” on page 152
Filters > Drill-down Filtering “Filtering Spreadsheet Data” on page 152
Filters > Levels “Filtering the Spreadsheet by Row Type” on page 154
Filters > Levels > Reset “Resetting a Spreadsheet to its Default View” on page 155

76 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Quick References and Work Flows
Tools Menu

Tools Menu
Read a command’s purpose or click within the Topic/Purpose column to view the
documentation associated with a specific Tools menu command.
Note
Some Tools menu selections are only available in standalone Constraint Manager sessions
that you launch on an Xpedition Enterprise Flow design.

Table 2-7. Tools Menu Selections

Menu Command Topic/Purpose
Tools > Dashboard Launch the Mentor Graphics Dashboard.
Tools > Xpedition Designer Launch Xpedition Designer.
Tools > Xpedition I/O Designer Launch Xpedition I/O Designer.
Tools > Constraint Template Launch Constraint Template Editor.
Editor
Tools > CES Diagnostics “Checking Constraints” on page 170
Tools > Constraint Resolution “Resolving Schematic Constraint Conflicts Manually” on
Manager page 389
Tools > iCDB Server Manager Launch Server Manager.
Tools > iCDB Project Backup Launch Auto Backup Utility.
Tools > Valor NPI “Selecting or Creating Valor NPI Design Centers” on
page 130
Tools > Customize “Adding Custom Menu Selections to the Tools Menu” on
page 127

Constraint Manager User's Manual, X-ENTP VX.2.8 77

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Quick References and Work Flows
Data Menu

Data Menu
Read a command’s purpose or click within the Topic/Purpose column to view the
documentation associated with a specific Data menu command.

Table 2-8. Data Menu Selections

Menu Command Topic/Purpose
Data > Constraint Violations “Viewing All Constraint Violations” on page 177
Data > Solve All Formulas “Solving Formulas to Check for Errors” on page 274
Data > Update IBIS Pin Type & “Updating Part Model Constraints” on page 373
Defaults
Data > Actuals > Import Layout “Sharing PCB Actuals With Front-End Constraint
Actuals Manager Sessions” on page 176
Data > Actuals > Import “Sharing PCB Actuals With Front-End Constraint
Thermal Actuals Manager Sessions” on page 176
Data > Actuals > Clear All Pages “Clearing Actuals From the Spreadsheet” on page 175
Data > Actuals > Clear This “Clearing Actuals From the Spreadsheet” on page 175
Page
Data > Actuals > Update All “Updating Actuals Displayed in Constraint Manager” on
page 175
Data > Actuals > Update “Updating Actuals Displayed in Constraint Manager” on
Selected page 175
Data > Clear > All Unused “Removing Unused Rules” on page 149
Constraints
Data > Clear > All Constraints “Deleting Constraint Values at the Design Level” on
page 148
Data > Clear > All Custom Delete any custom constraints you created.
Constraint Definitions
Data > Clear > All Custom Tabs Delete any custom spreadsheet pages you created.

78 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Quick References and Work Flows
Output Menu

Output Menu
Read a command’s purpose or click within the Topic/Purpose column to view the
documentation associated with a specific Output menu command.

Table 2-9. Output Menu Selections

Menu Command Topic/Purpose
Output > Model Audit Report “Verifying Default Model Assignments” on page 370
Output > Design Statistics “Viewing Design Statistics” on page 168
Output > Check Constraints “Checking Constraints Synchronization” on page 168
Synchronization
Output > Show iCDB Clients Provides a short report of clients and sub-clients who are
currently working on the same design.
Output > Report Comments “Viewing Constraint Comments” on page 167

Constraint Manager User's Manual, X-ENTP VX.2.8 79

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Quick References and Work Flows
Constraint Manager Work Flows

Constraint Manager Work Flows

The topics that follow illustrate the two main work flows for the tool. Although these work
flows indicate the typical order of constraint entry and modification for schematic and PCB
engineers, your order of operations may be different.
These work flows are included:

• Schematic-Design Work Flow — This work flow begins with creating and defining
constraint classes. These groupings hold electrical, signal integrity, and high-speed
signal integrity constraints. Along the way, you make a variety of constraint
assignments. Some of these include topology types, simulated delay rules, and
overshoot and ringback requirements. The final step is sending schematic constraint data
to your layout design representation through forward annotation.
• PCB-Layout Work Flow — This work flow starts with creating and defining both
rules-area schemes and net classes. These groupings hold physical constraints for board
layers and nets. Along the way, you make a variety of constraint assignments. Some of
these include trace and via rules, clearance rule sets, and package-type clearances. The
final step is to send layout constraint data to your schematic design representation
through back annotation.
Schematic-Design Work Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
PCB-Layout Work Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

80 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Quick References and Work Flows
Schematic-Design Work Flow

Schematic-Design Work Flow

Click within the illustration to view the topic for a specific step in the schematic work flow.
Figure 2-1. Schematic-Design Work Flow

Constraint Manager User's Manual, X-ENTP VX.2.8 81

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Quick References and Work Flows
PCB-Layout Work Flow

PCB-Layout Work Flow

Click within the illustration to view the topic for a specific step in the layout work flow.
Figure 2-2. PCB-Layout Work Flow

82 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Chapter 3
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 86. It includes important information for each PCB design flow that uses Constraint
Manager.

Constraint-Driven Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Before You Begin Using Constraint Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Starting and Exiting From Constraint Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Starting Constraint Manager in Standalone Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Viewing Constraint Database Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Folder Structure and Location of Constraint Manager Log Files . . . . . . . . . . . . . . . . . 94
Cross Probing Between Design Systems and Constraint Manager. . . . . . . . . . . . . . . . . 95
Constraint Manager Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Display Customization of Constraint Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Toolbar Customization of Constraint Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Constraint Set Customization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Adding Custom Menu Selections to the Tools Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Customizing Command Shortcut Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Default Keyboard Shortcuts Provided With Constraint Manager . . . . . . . . . . . . . . . . . 129
Selecting or Creating Valor NPI Design Centers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Sharing Valor NPI Design Centers Among Team Members . . . . . . . . . . . . . . . . . . . . . . 131

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.
For example, you can define constraints using HyperLynx LineSim, and then use that data to
drive automatic routing to ensure a correct-by-design circuit.

Constraint Manager User's Manual, X-ENTP VX.2.8 83

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Overview and Setup
Constraint-Driven Design

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.

Figure 3-1. Common Constraint Environment Resulting in Accurate Schematic

Design and PCB Layout Views

Click within the illustration to view specific documentation topics.

Constraint-Driven Design Flows

The tool is available in these integrated design flows:

• Xpedition® Enterprise
• PADS® Professional
• PADS Designer-PADS Layout (Integrated Workflow)
• Keyin netlist-Xpedition Layout

Concurrent Design Process

Constraint Manager supports concurrent design process, which is the ability to have multiple
engineers work on schematic-entry or PCB-layout design constraints simultaneously. This
means that users can modify a front-end or back-end constraint set at the same time. Each user
sees the constraint changes made by other users in real time. You still use forward and back
annotation to communicate changes between schematic and layout design representations.

For more information, see “Concurrent Constraint Entry With Other Users” on page 161.

84 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Overview and Setup
Constraint-Driven Design

PCB Rule-Area Creation Through Schemes

Beginning with the Master scheme, rule-area schemes give you the ability to segment areas of a
board into distinct regions and then apply different physical/manufacturing rules to each area.
For example, if a certain area of a board contains many critical connections between
components, you can define a board area that encompasses this region, and then apply tighter
trace and via rules that promote signal integrity within this critical board area.

For more information, see “Creating Rule-Area Schemes” on page 24.

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 26.

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 31.

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 174.

Automation of Constraint Tasks

Constraint Manager provides a COM automation interface in the Xpedition Enterprise and
PADS Professional flows.

For more information, see Constraints Automation Manual.

Constraint Manager User's Manual, X-ENTP VX.2.8 85

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
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 287.
• The default view of the tool is streamlined to present you with just the core set of
spreadsheet pages, toolbars, and navigator nodes. For information on displaying those
that are not displayed by default, refer to “Display Customization of Constraint
Manager” on page 110.
• 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 168.
• If your design includes them, the tool represents single-pin nets as a unified net called
“(Net0)-1:X”. You must access this special net if assigning Net0 nets to a constraint
class and net class, or if defining single-pin net constraints. For more information, refer
to “Defining Constraints for Single-Pin Nets” on page 294.
• 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.

86 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Overview and Setup
Before You Begin Using Constraint Manager

• 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
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.
• When working in Constraint Manager sessions launched from Xpedition Layout, you
cannot change reference designator prefixes through Constraint Manager’s settings
dialog box. To update these prefixes in your back-end constraint set, modify them in a
constraint session launched from the front-end, and then forward annotate.
• 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 106.
• When exporting constraints, the tool uses the native concurrent unit type. If reimporting
constraints, you must set the unit type afterward.
• The tool does not apply Z-axis clearances between segments of the same net.
• 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.
Xpedition Enterprise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Keyin Netlist-Xpedition Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Differential Pairs Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Static Team Layout and Xpedition Team Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Overview of Electrical Nets and Physical Nets in Constraint Manager . . . . . . . . . . . . . 89
Automatically Recognized Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Electrical Nets Defined Through a Package With More Than Two Pins. . . . . . . . . . . . 91
Importing a Layout Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Importing a 2005.x Ces.prefs File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Constraint Manager User's Manual, X-ENTP VX.2.8 87

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Overview and Setup
Xpedition Enterprise

Xpedition Enterprise
If using this flow, you should be aware of these additional requirements, limitations, and tool
behaviors.
They are:

• You must have an Xpedition Designer tool concurrency license (dxconcurrent) to use
multiple copies of schematic invocations of Constraint Manager, or standalone
Constraint Manager, on the same design.
• If you use the Copy Sheet command in the Xpedition Designer tool, the tool only copies
constraint values if you enable the “Copy Constraints on Copy Sheet” option in the
Xpedition Designer tool’s Advanced settings. The tool does not copy values if you use
the Copy Block command.

Keyin Netlist-Xpedition Layout

If using this flow, you should be aware of these additional requirements, limitations, and tool
behaviors.
They are:

• If you use a keyin netlist to represent design connectivity instead of traditional

schematic capture data, forward annotate before you begin use Constraint Manager to
modify constraint data. Aside from the standard communication of design changes, you
only have to perform this step once. You can do so before or after you enable Constraint
Manager in a keyin netlist flow.

Differential Pairs Conversion

When Constraint Manager converts differential pairs between database formats, some
differential pairs may not convert successfully; however, the tool preserves them in the old
format and they are still valid.
In the event that this occurs, the tool provides a dialog box indicating that it could not convert
some differential pairs and has marked them with a pin icon. To redefine one or more of these
differential pairs, you must delete them.

Note
You are not required to redefine differential pairs that the tool could not convert to the 2007
(or later) Constraint Manager database format. The tool preserves these differential pairs in
the previous format, and they are still applicable to your updated design.

88 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Overview and Setup
Static Team Layout and Xpedition Team Layout

Example 3-1. Differential Pair That was not Converted

If you delete a differential pair marked with a pin icon, another dialog box is displayed. It
indicates that each net that comprises the differential pair may be merged into another electrical
net. This can remove the ability for you to recreate the current differential pair.

Static Team Layout and Xpedition Team Layout

Static Team Layout (used for concurrent PCB design) and Xpedition Team Layout (used for
dynamic/interactive group PCB design) are integrated with Constraint Manager. However, the
tool has limited support for Static Team Layout. Constraints you define are carried forward to
the split designs.
If you are editing a split design, you can change constraints on the Trace & Via Properties page
and Clearance page inside Constraint Manager. However, the changes apply only to the current
split design. The changes are not joined with the main design. You cannot edit constraints on
any other spreadsheet pages in the tool if inside a split partition.

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.

Constraint Manager User's Manual, X-ENTP VX.2.8 89

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Overview and Setup
Automatically Recognized Topologies

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
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 3-2. Differential Pair Topologies Automatically Recognized by
Constraint Manager

In both of these cases, the tool determines the receiving component to be a differential receiver
if the component has an IBIS model that contains a diff pin statement for the pin; or, the
component has no IBIS model but two inputs exist on the same symbol or part instance, and a
single resistor, or a pair of resistors in parallel, connect the inputs.

90 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Overview and Setup
Electrical Nets Defined Through a Package With More Than Two Pins

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).
• You defined pin pairs across the entire part. For example, if the part has four pins, you
must define two pin pairs. Doing so maps the pins so the tool can correctly route through
the resistor pack. For more information, refer to “Defining Discrete Component Pin
Pairs” on page 259.
When the tool does this, it sets the Parts page Series constraint to enabled/on for the part.

Importing a Layout Template

If your design data is limited to just schematic data, you can import a layout template into
Constraint Manager sessions launched from your front-end design system. Doing so is useful if
a schematic engineer wants to define physical constraints based on an accurate board-layer
configuration before the first forward annotation has occurred.
Procedure
1. From the File menu, click Import, then click Layout Template.
2. In the Import Layout Template dialog box, next to Select layout template, click the
dropdown, then choose the template you want to use.
3. After you are sure of your selection, click OK.

Caution
After you associate a layout template with your design, whether through this
procedure or in your PCB layout design system, when you load the design in
Constraint Manager, the Output window displays information about the layout template.
This information includes the number of layers in the template. It is important to
understand that this information does not necessarily reflect the actual number of layers,
or other stackup information for the actual design. You get the same report even if you
make changes to the stackup.

Constraint Manager User's Manual, X-ENTP VX.2.8 91

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Overview and Setup
Importing a 2005.x Ces.prefs File

Importing a 2005.x Ces.prefs File

Versions of Constraint Manager before VX.0 stored some settings in a preferences file called
Ces.prefs that it wrote to the top level of your WDIR location. To make the transition between a
2005.x release and a VX.x release easier, you can import your preferences file into Constraint
Manager VX.x.
Note
The tool no longer writes this preferences file. Importing a Ces.prefs file is intended to be an
optional, one-time transitional step between releases.

Procedure
1. From the File menu, click Import, then click Preferences File.
2. In the Open dialog box, navigate to the Ces.prefs file you want to load, then click Open.

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 or layout tool.

• Launch Constraint Manager.
Schematic Tool Layout Tool

92 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Overview and Setup
Starting Constraint Manager in Standalone Mode

Procedure
1. Launch your design tool.
2. From your design tool, click the Constraint Manager icon ( ) or use its menu path.

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

Design Tool Menu Path
Xpedition Designer Tools > Constraint
Manager
Xpedition Layout 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.

Starting Constraint Manager in Standalone

Mode
Start Constraint Manager in standalone mode if you want to view the constraint set associated
with a design without opening your schematic or PCB layout software. To view a back-end
constraint set, you must open a keyin netlist .prj file in Constraint Manager.
Procedure
1. Start the tool in any of the following ways:

Operating System Instruction

Windows 7 Start menu Choose Xpedition Enterprise VX.x > Constraint
Entry > Constraint Manager.
Windows 8.1 Start menu and Choose All apps > Xpedition Enterprise
newer VX.x > Constraint Manager.
Linux Applications menu Choose Xpedition Enterprise VX.x > Constraint
Entry > Constraint Manager.
Dashboard In the Mentor Graphics Dashboard, with a project actively
selected, expand Board-Level (PCB) Design Toolbox,
then double-click Constraint Manager.

2. From the File menu, click Open Project.

Constraint Manager User's Manual, X-ENTP VX.2.8 93

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Overview and Setup
Viewing Constraint Database Log Files

3. In the Open Project dialog box, select a .prj file.

4. (Optional) If the front-end design contains multiple boards, click the Board dropdown to
select one.
5. Click Open.

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.

For Xpedition Designer only, in the event that you can not copy from-tos and/or pin pairs while
copying or updating a reuse block, or if copying sheets, the tool writes one or both of these log
files to capture the missing objects:

• MissingFromtos_<time/date stamp>.log
• MissingPinpairs_<time/date stamp>.log

Layout Log Files Folder Structure

<design_folder>\CES\LogFiles\<snapshot_name>\<block_name>\<machine_name>\
<user_name>

94 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Overview and Setup
Cross Probing Between Design Systems and Constraint Manager

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.

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 97.

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
Watch the video to learn how to:

• Enable cross probing mode.

• Highlight an object in your schematic or layout tool and view the result in Constraint
Manager.
• Highlight an object in Constraint Manager and view the result in your schematic or
layout tool.

Constraint Manager User's Manual, X-ENTP VX.2.8 95

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Overview and Setup
Cross Probing Between Design Systems and Constraint Manager

Schematic Tool Layout 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.
Figure 3-3. 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

96 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Specifying Electrical Net Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Specifying Discrete Component Prefixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Using a Configuration File to Specify Design Preferences. . . . . . . . . . . . . . . . . . . . . . . . 100
Setting Display Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Setting General Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Setting Fonts and Colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Setting Spreadsheet Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Setting Unit Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Specifying Other Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Reusing Settings in External Designs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Specifying Design Configuration Preferences

Design configuration preferences are settings that affect an entire design rather than specific
design objects (for example, layers or nets).
Tip
As an alternative, you can use a configuration file to specify some preferences. For more
information, refer to “Using a Configuration File to Specify Design Preferences” on
page 100.

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.

Constraint Manager User's Manual, X-ENTP VX.2.8 97

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Overview and Setup
Specifying Electrical Net Preferences

• Time — A default electrical tolerance for delay values. This is the allowable default
deviation for any match group delay constraints you define in Constraint Manager.
4. Under Parallelism mode, specify whether the router should report parallelism hazards
cumulatively, or separately for each segment. When in cumulative mode, the router
reports a hazard for each segment that comprises a group. For example, if the parallel
run length needs to be less than 400 th, and each of the three segments in a group are 134
th, the router shows a violation for each segment although they are each 266 th shorter
than required. The router reports violations because the sum of 134 th + 134 th + 134 th
is 402 th, which is greater than 400 th.

Note
For cumulative calculations, the router ignores segments smaller than 100 th. Using
the example in the step, five 98 th segments result in a total of 490 th, but because
each segment is less than 100 th, the router ignores all of them and reports no hazard.

5. Under Pin Package, in the Propagation Delay field, modify the velocity value as needed
to reflect an accurate signal speed through pin package connections. The tool uses this
value in conjunction with the Pin Package constraints of the Parts page to calculate
either Pin Package Length or Pin Package Delay, if requested. (The default value is
0.000165 ns/th.)
6. 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.
7. Click OK.

Specifying Electrical Net Preferences

You can specify electrical net preferences such as the maximum number of physical nets that
can comprise an electrical net and whether the tool can use IBIS part models to help
characterize electrical nets.
Prerequisites
• You must be using a Constraint Manager session launched from the front-end or a
standalone session of the tool.
Procedure
1. From the Setup menu, click Settings; or, on the General toolbar, click .

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

98 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Overview and Setup
Specifying Discrete Component Prefixes

which contains many physical nets. For more information, refer to “Overview of
Electrical Nets and Physical Nets in Constraint Manager” on page 89.
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. Specify whether the tool should use IBIS part models for electrical nets.
6. For component names, specify whether the tool should use IBIS names (for example,
icx_part_model) for mapping purposes. By default, the tool uses the part model name.
7. 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. If you
are using the Xpedition Enterprise Flow, the tool identifies any combination of 2-pin or full-
pack symbols as series devices. In the other flows, you must use 2-pin schematic symbols to
ensure Constraint Manager recognition.

Prerequisites
• You must be using a Constraint Manager session launched from the front-end or a
standalone session of the tool.
Procedure
1. From the Setup menu, click Settings; or, on the General toolbar, click .

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

Constraint Manager User's Manual, X-ENTP VX.2.8 99

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Overview and Setup
Using a Configuration File to Specify Design Preferences

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.

Using a Configuration File to Specify Design

Preferences
As an alternative approach to specifying design preferences through the Constraint Manager
GUI, you can use a preferences file (.prefs) to define some of these design characteristics.
For example, you can specify the numerical pin threshold the tool uses to determine whether a
net is a signal net or a power net. The tool uses this setting to create a list of valid reference
designator prefixes.

Procedure
1. Exit Constraint Manager.
2. In an ASCII text editor, create a file named ces.prefs.

100 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Overview and Setup
Setting Display Options

3. Copy and paste the content of the example preferences file into your ASCII text editor.
4. Modify the example content in your ASCII text editor to specify appropriate values.
5. Save ces.prefs to the appropriate WDIR location.
6. Restart Constraint Manager.
Results
Constraint Manager reads the preferences from this file and replaces any GUI definitions you
had specified previously.
Figure 3-4. Example ces.prefs File

(preferences
(section CES
(pref DSN_POWERS "+12V=12.0" "+5V=5.0" "-12V=-12.0" "-5V=-5.0"
"GND=0.0" "VCC=5.0" "VDD=5.0" "VEE=-5.2" "VSS=0.0" )
(pref DSN_MAXENETS 10)
(pref DSN_BIGNETPINCOUNT 50)
(pref DSN_DEF_DISTANCE_TOL 254000)
(pref DSN_DEF_TIME_TOL 0.015)
(pref DSN_DISCRETES "RESISTOR=R,RN,RP" "CAPACITOR=C"
"INDUCTOR=L,FB" "DIODE=CR,D" "CONNECTOR=J,P")))

Setting Display Options

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.
Procedure
1. From the Setup menu, click Settings; or, on the General toolbar, click .

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.

Constraint Manager User's Manual, X-ENTP VX.2.8 101

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Overview and Setup
Setting General Options

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
1. From the Setup menu, click Settings; or, on the General toolbar, click .

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.
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

102 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Overview and Setup
Setting Fonts and Colors

constraint value. If an actual value exceeds the constraint value, the tool highlights
the field in red.
• Acceptable threshold Constraint Manager uses when applying constraint templates
to nets. In the Template match threshold field, type a percentage value. For less
similarity, reduce this value; for more similarity, increase this value.
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 136.

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
1. From the Setup menu, click Settings; or, on the General toolbar, click .

2. In the Settings dialog box, under Display, click Fonts and Colors.
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.

Constraint Manager User's Manual, X-ENTP VX.2.8 103

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Overview and Setup
Setting Spreadsheet Units

• 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.

Setting Spreadsheet Units

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
1. From the Setup menu, click Settings; or, on the General toolbar, click .

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.
4. Click OK.

Table 3-2. Available Display Units

Field Description Default Values
Angle You can choose from the following deg; 3
units:
• deg – degree
• rad – radian
• ' – minutes
• " – seconds

104 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Overview and Setup
Setting Spreadsheet Units

Table 3-2. Available Display Units (cont.)

Field Description Default Values
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
Power You can choose from the following W; 3
units:
• kW – kilowatts
• W – watts
• mW – milliwatts
• uW – microwatts
• nW – nanowatts

Constraint Manager User's Manual, X-ENTP VX.2.8 105

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Overview and Setup
Setting Unit Notation

Table 3-2. Available Display Units (cont.)

Field Description Default Values
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
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.

106 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Overview and Setup
Specifying Other Preferences

Procedure
1. From the Setup menu, click Settings; or, on the General toolbar, click .

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.

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
1. From the Setup menu, click Settings; or, on the General toolbar, click .

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.)

Constraint Manager User's Manual, X-ENTP VX.2.8 107

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Overview and Setup
Reusing Settings in External Designs

Note
To do the same for thermal actuals, click to enable Thermal Dynamic update.

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.

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.

108 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Overview and Setup
Reusing Settings in External Designs

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.

Constraint Manager User's Manual, X-ENTP VX.2.8 109

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Changing the Position of Windows and Toolbars. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Folder Location of the ces.ini Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

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 Nodes.
o To show only the default nodes, click Default Nodes.

110 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Overview and Setup
Changing the Position of Windows and Toolbars

Tip
Clicking the right mouse button on Navigator items often displays context-
sensitive menus so you can perform operations directly from within it.

o To display the number of objects in each group (for example, a constraint class),
enable Show Object Counters.
• 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.
• 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.

Constraint Manager User's Manual, X-ENTP VX.2.8 111

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Overview and Setup
Changing the Position of Windows and Toolbars

Figure 3-5. 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.
Figure 3-6. 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.
For example, you could have the Output window and the 3D Clearances window
share the same screen position.

112 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Overview and Setup
Folder Location of the ces.ini Configuration File

Figure 3-7. Windows Sharing the Same Space are Tab Accessible

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
Folder Location of the ces.ini Configuration File

Folder Location of the ces.ini Configuration File

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.

Constraint Manager User's Manual, X-ENTP VX.2.8 113

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Overview and Setup
Folder Location of the ces.ini Configuration File

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\EEVX.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\
EEVX.1\ces.ini

Linux Location
The tool stores the GUI customization file (ces.ini) at the following location:

$HOME/.config/MentorGraphics/<software version>/ces.ini

For example, $HOME/.config/MentorGraphics/EEVX.1/ces.ini

114 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Overview and Setup
Toolbar Customization of Constraint Manager

Toolbar Customization of Constraint Manager

You can customize Constraint Manager toolbars to change the order and groupings of buttons
on standard toolbars and create new toolbars. Or, quickly toggle the visibility of specific buttons
on a toolbar.
Doing this can help to increase your efficiency with the tool by making it easier to access just
the toolbar buttons you use. If you do not want to keep your modifications to a standard toolbar,
you can reset it to its default group of buttons.

Toggling Toolbar Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Modifying Toolbars to Create Custom Sets of Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Modifying Individual Toolbar Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Creating New Toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Renaming and Deleting Custom Toolbars. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Resetting a Toolbar to the Default Grouping of Buttons . . . . . . . . . . . . . . . . . . . . . . . . . 118
Customize Dialog Box - Options Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Toggling Toolbar Buttons

Toggle one or more buttons on a standard toolbar to quickly customize it without saving formal
changes to a toolbar or creating a custom toolbar. For example, you might toggle the display of
certain topology type buttons while working on nets in a specific constraint class that all use just
one or two of the available types.
Prerequisites
• The toolbar you want to modify is visible.
Procedure
1. On any standard toolbar, click the down arrow icon to the right.

2. Choose Add or Remove Buttons.

3. Click the name of one of the visible standard toolbars.
4. Click to toggle specific toolbar buttons. As you do so, the tool hides or shows buttons on
the toolbar in real time.

Note
To quickly revert all visibility changes for the toolbar, choose Reset Toolbar.

Constraint Manager User's Manual, X-ENTP VX.2.8 115

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Overview and Setup
Modifying Toolbars to Create Custom Sets of Buttons

Modifying Toolbars to Create Custom Sets of

Buttons
You can modify Constraint Manager toolbars to change the order of buttons displayed on a
toolbar, add buttons, and remove buttons.
For example, if you typically use only half the buttons on a specific toolbar, you can reorder the
buttons on it so that those buttons display in the leftmost position of the toolbar instead of being
spread out among the entire width of the toolbar.

Procedure
1. Do one of the following:
• Choose View > Toolbars > Customize.
• Right-click any Constraint Manager toolbar, then click Customize.
2. In the Customize dialog box, click the Commands tab, then do any of the following:
• To add a button to a toolbar, click the appropriate group selection within the
Categories list box, then in the list of buttons, click and drag a button to a specific
toolbar at the top of the tool.

Tip
Visually group similar toolbar buttons if you intend to include a large number of
buttons on a single toolbar. To add a bar separator to the left of a toolbar button,
right-click the button, then click Start Group.

• To remove a button from a toolbar, at the top of the tool, click a toolbar button, then
drag it to any area below the collection of toolbars. You can also right-click a button,
then click Delete.
• To move a button within a toolbar, or from one toolbar to another, at the top of the
tool, click a toolbar button, then drag it to another location. The tool uses
highlighting to assist you.
Figure 3-8. Moving a Toolbar Button to Another Position

3. After you finish making changes to one or more toolbars, click Close.

116 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Overview and Setup
Modifying Individual Toolbar Buttons

Modifying Individual Toolbar Buttons

You can modify the appearance of individual toolbar buttons to specify whether they should
display an image, text, or both. You can also modify text or reset a button to its default display.
Toolbar button customizations you make are local to just the toolbar you are modifying. If you
make changes to a toolbar button that appears on multiple toolbars, those changes do not show
up on all toolbars.

Procedure
1. Do one of the following:
• Choose View > Toolbars > Customize.
• Right-click any Constraint Manager toolbar, then click Customize.
2. Right-click the toolbar button you want to modify, then do any of the following:
• To control whether the toolbar button shows textual information, an icon, or both,
click Image, Text, or Image and Text.
• To modify the text displayed by a toolbar button, click Button Appearance. In the
Button text field, type the text to show, then click OK.

Note
Although the Button Appearance dialog box includes functionality to change the
image for a toolbar button, it is not enabled in the tool.

• To revert a button to its default display, click Reset to Default.

Here is an example of modifications to buttons on the Pairs toolbar. It now shows both
images and text for the three differential pair buttons and also has text modifications for
each of them.
Figure 3-9. Modifications to the Pairs Toolbar

Creating New Toolbars

You can create new toolbars to group buttons from multiple toolbars. A common usage is to
create a user-based toolbar that includes all of the buttons you use most frequently. Constraint
Manager provides a large number of buttons, so making your custom set can help you be more
efficient with the tool if you use a specific subset of its functionality.

Constraint Manager User's Manual, X-ENTP VX.2.8 117

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Overview and Setup
Renaming and Deleting Custom Toolbars

Procedure
1. Do one of the following:
• Choose View > Toolbars > Customize.
• Right-click any Constraint Manager toolbar, then click Customize.
2. In the Customize dialog box, click the Toolbars tab, then click New.
3. In the New Toolbar dialog box, in the text field, type a name for the new toolbar (for
example, “pats_toolbar”), then click Close.
Results
You can now modify the new toolbar. To learn how to add buttons to it or change its contents,
refer to “Modifying Toolbars to Create Custom Sets of Buttons” on page 116.

Renaming and Deleting Custom Toolbars

After you create one or more toolbars, you can rename them and delete them as needed.
Procedure
1. Do one of the following:
• Choose View > Toolbars > Customize.
• Right-click any Constraint Manager toolbar, then click Customize.
2. In the Customize dialog box, click the Toolbars tab.
3. Click the name of a toolbar that you created, then click Delete or Rename.
4. If renaming a toolbar, in the Toolbar name text box, type a different name for the custom
toolbar, then click OK.
5. Click Close.

Resetting a Toolbar to the Default Grouping of

Buttons
You can reset a toolbar to display its default listing and order of buttons. Doing so is especially
useful if you make changes to a toolbar that are too extensive and you want to start over. In
some cases, you may have temporarily modified a toolbar and want to reset it.
Prerequisites
• The toolbar is a standard toolbar (you did not create it).

118 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Overview and Setup
Resetting a Toolbar to the Default Grouping of Buttons

Procedure
1. Do one of the following:
• Choose View > Toolbars > Customize.
• Right-click any Constraint Manager toolbar, then click Customize.
2. In the Customize dialog box, click the Toolbars tab.
3. In the listing of toolbars, click the appropriate toolbar, then click Reset. To instead reset
all toolbars, click Reset All.
4. Click Close.
Results
The toolbar now displays all default buttons, and in the default order.

Constraint Manager User's Manual, X-ENTP VX.2.8 119

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Overview and Setup
Customize Dialog Box - Options Tab

Customize Dialog Box - Options Tab

To access: View > Toolbars > Customize > Options
Control the visibility of screen tips and the system size for all toolbar icons. For 4K displays,
increasing the size of toolbar buttons can greatly enhance readability.
Fields

Field Description
Show Screen Tips on toolbars Show a tip when you hover
the mouse over a toolbar
button.
Show shortcut keys in Screen If you show screen tips, you
Tips can also choose to have each
tip include a keyboard
shortcut.
Large Icons Display larger toolbar icons.

120 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Overview and Setup
Constraint Set Customization

Constraint Set Customization

You can customize the constraint set by changing access to constraints and adding constraints
that are unique to the needs of your engineering organization. Often times, the goal of constraint
customization is to share modifications and additions with a set of users. As such, constraint
customization is many times the responsibility of an administrative user on the design team.
Creating or Modifying Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Deleting User-Created Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Constraint Set Propagation to a Team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Associating user.cns Files With a Mentor Graphics Software Release . . . . . . . . . . . . . 126

Creating or Modifying Constraints

You can customize the constraint set displayed through the spreadsheet to fit your needs and
that of your design team. If making customizations, you can add new constraints (user
constraints) and specify all of their properties.
You can only modify existing constraints (base constraints) to control whether they are read-
only or hidden. The tool stores all changes to the constraint in the user.cns file in the WDIR
location specific to your software installation.

Be aware of these important guidelines:

• There are two types of constraints: base constraints and user constraints. Base
constraints are defined by Mentor Graphics and supplied with the software. User
constraints are created by users.
• If your WDIR variable includes multiple locations, the tool only updates user.cns at the
first writable path.
• Because a user.cns file must exist at all locations specified in your WDIR variable,
Constraint Manager initially places one at each location if one does not already exist.
After that, it only writes changes to the first writable path.
• The tool does not support the use of user.cns files between releases. All user.cns files
need to be specific to a certain release (for example, EE 7.9.5). For more information,
refer to “Associating user.cns Files With a Mentor Graphics Software Release” on
page 126.

Constraint Manager User's Manual, X-ENTP VX.2.8 121

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Overview and Setup
Creating or Modifying Constraints

Caution
Customizations to the constraint set are something that a design team should only do
before starting design development. After you put a custom user.cns in place, you
should not modify it or make a different user.cns available. Custom constraint sets are
tied to each specific user.cns file. Changing the available user.cns file during the course
of design development causes the loss of custom constraints and data that you cannot
regain. Therefore, it is critical that the machines of all team members use the same
corporate or design-specific user.cns file.
For more information, refer to “Constraint Set Propagation to a Team” on page 124. In
the event that you move the design to a different machine, ensure that it has access to the
necessary user.cns file for the design before you load the design. If working with a
design backup that you restore at a later point in time, you must ensure that the correct
user.cns file is available to the design before you load the design.

Prerequisites
• There must be one or more writable folder locations specified in your WDIR variable. If
a user.cns file exists at each of the folder locations, at least one of those files must be
writable.
• If the user.cns file you are updating is in a shared WDIR folder location, you are the
only user who is modifying the constraint set. The tool does not support concurrency
while customizing the constraint set.
Procedure
1. Do one of the following:
• From the Edit menu, click Constraint Definitions.
• On the spreadsheet, right-click a constraint column, then click Constraint
Definitions. Now that you are in the context of a specific constraint, proceed to step
4.
2. In the Constraint Definitions dialog box, use the Page dropdown to select the
spreadsheet page for which you want to modify an existing constraint or a new
constraint.

Tip
To differentiate between base constraints and user constraints, you can use the Filter
dropdown to select the constraint types to display.

3. At this point, you can do any of the following:

• To modify a base constraint and control whether it is read-only or hidden, in the
Constraint dropdown, select a base constraint.

122 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Overview and Setup
Deleting User-Created Constraints

• To create a user constraint, click , type a name for the new constraint, then click
OK.
4. For user constraints only, you can now specify Header, Title, Data type, Default value,
and other attributes of the constraint. The Data type field controls whether the constraint
has an associated Unit type, Min value, and Max value.

Note
To display the unit type in a constraint heading, append “(%U)” to the heading text
(for example, “Crosstalk (%U)”).

5. For user constraints only, if applicable, you can use Min value and Max value to set the
acceptable boundaries for a constraint. If you input a constraint value that is outside of
this boundary, Constraint Manager uses its backlighting mechanism to visually indicate
the range breach.
6. If creating a user constraint, use the Levels selection to specify the spreadsheet-page
levels for which the constraint should be associated.
7. For both user constraints and base constraints, click the associated check box to make
the constraint read only and/or hidden.
8. For user constraints only, in the Constraint description text field, type or modify the
description for the constraint.
9. To make more adjustments to the constraint set, return to step 2. After you finish
changing the constraint set, click Apply.

Deleting User-Created Constraints

You can delete custom constraints that you added to Constraint Manager. You can do so
constraint-by-constraint or delete all custom constraint definitions at the same time.
Note
To delete all custom constraint definitions, from the Data menu, click Clear All Custom
Constraint Definitions.

Prerequisites
• You created one or more custom constraints as described in “Creating or Modifying
Constraints” on page 121.
Procedure
1. From the Edit menu, click Constraint Definitions.
2. In the Constraint Definitions dialog box, use the Page dropdown to select the
spreadsheet page for which you want to delete a user constraint.

Constraint Manager User's Manual, X-ENTP VX.2.8 123

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Overview and Setup
Constraint Set Propagation to a Team

3. Using the Constraint dropdown, select the constraint, then click .

Constraint Set Propagation to a Team

If working with a team of engineers who need to use the same custom constraint set, you can
share your <WDIR>/user.cns file (for example c:\WDIR\EEVX.1\user.cns) with other members
of the team.
How you deploy this file depends on the infrastructure of your organization and the goals you
want to accomplish. This topic provides a few different deployment methodologies. Generally,
the only users who would deploy a user.cns are either a design lead or administrator.

user.cns Requirements for Remote Server Usage and Project Concurrency

Be aware of these user.cns requirements if using RSCM:

• Each user machine and the RSCM server machine must have their own writable local
WDIR folder, and the WDIR environment variable for each user machine must include
all corporate WDIR folders listed by the RSCM server machine. The illustration depicts
these requirements being met in first two environments, but not in the third.
Example 3-2. WDIR Locations

Corporate WDIR folders are shown in blue text, while local WDIR folders are shown in
black text.
• If a user’s machine has the environment variable RSCM_ENV_CONFIG defined, it is
important to understand that the WDIR definition in the file rscm.env.cfg takes
precedence over their WDIR environment variable. In this case, users must ensure that
the WDIR variable in rscm.env.cfg is the same as the WDIR definition used by the team.

124 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Overview and Setup
Constraint Set Propagation to a Team

• The administrative user who runs the RSCM service for a design must have write access
to at least one directory specified in the WDIR definition.

Enterprise Methodology
The most efficient way to use the same custom constraint set within a design team relies upon
having a corporate WDIR location to which each user machine points. By placing user.cns in
the corporate WDIR location, each user machine can read from the same custom constraint set.

Caution
Before copying an updated user.cns file into a corporate WDIR folder shared by a design
team, ensure that none of the users have Constraint Manager open or are currently accessing
the file.

To use this approach, the WDIR environment variable on each user machine must include these
three paths, and in this order:

• Writable local WDIR folder (for example, C:\WDIR\EEVX.1).

• Read-only Corporate WDIR folder (for example, \\common\corp_WDIR_EEVX.1).
• Read-only pointer to <Mentor Graphics install location>\<version>\SDD_HOME\
standard.

Caution
The tool does not support deployment ofuser.cns files between releases. All user.cns
files need to be specific to a certain release (for example, EE 7.9.5). For more
information, refer to “Associating user.cns Files With a Mentor Graphics Software
Release” on page 126.

Based on the unique folder paths, the WDIR variable would be the following: C:\WDIR\
EEVX.1;\\common\corp_WDIR_EEVX.1;C:\MentorGraphics\EEVX.1\SDD_HOME\standard

Note
On Windows, if including network paths in your WDIR environment variable, you must list
them as full network paths (UNC). You cannot list them as mapped drives.

Using this approach provides the benefits of a corporate environment where various Constraint
Manager users are able to:

• Edit constraint values for base constraints and user constraints concurrently.
• Add their own user-defined constraints while not changing the corporate constraint set.
(Refer to the cautionary statement in “Creating or Modifying Constraints” on page 121
for important information about maintaining access to custom constraints and their
values.)

Constraint Manager User's Manual, X-ENTP VX.2.8 125

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Overview and Setup
Associating user.cns Files With a Mentor Graphics Software Release

Caution
Do not define user constraints in a local WDIR folder if using concurrency. The tool
does not support user constraints defined in a writable local WDIR folder (for
example, C:\WDIR\EEVX.1) if working in concurrent mode. The tool immediately
removes these constraints and their values from the database if you access the design in
concurrent mode.

• Maintain separate interface settings and constraint groups for each user.
• Efficiently and accurately benefit from a custom, corporate constraint set.

Small-Group Methodology
Although it is not recommended, if you do not have a corporate WDIR location, you can place
user.cns in a public location and then provide instructions for other team members to copy it
into the WDIR directory on their respective machines.

Manually managing deployment and updates to your team’s user.cns file is not an efficient
approach, and it can easily result in inconsistent constraint sets among your user base. If you are
not yet using a shared WDIR location, now is a great time to include one in your design
environment.

Constraint Sets Based on User Roles

In some cases, you might want to have custom constraint sets for specific user roles. For
example, if you are the constraint administrator for a design project or team, you might want to
grant access to specific constraints to just certain members of the team while hiding them from
the rest of the team, or making them read-only.

By default, all Constraint Manager users have access to all constraints, so reducing accessibility
to some key constraints can help to ensure constraint integrity. In an example case, a constraint
administrator could create different user.cns files and then provide the appropriate user.cns file
to each team member based on their role within the design team.

Associating user.cns Files With a Mentor Graphics

Software Release
Because Constraint Manager does not support deployment of common user.cns files between
releases, you need to ensure that each Mentor Graphics software release that you use has access
to its own unique user.cns file or file set for that release.
In the event that your WDIR variable definition includes multiple folder locations, the user.cns
file in each location must be specific to a single Mentor Graphics software release. You must
use different WDIR folders for each software release.

126 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Overview and Setup
Adding Custom Menu Selections to the Tools Menu

An Example Scenario
Here is an example WDIR variable definition that includes three folder locations and is based
on an enterprise methodology: C:\WDIR\EEVX.1;\\common\corp_WDIR_EEVX.1;C:\
MentorGraphics\EEVX.1\SDD_HOME\standard

As you can see, each of the three folders is unique to the EEVX.1 release. The user.cns file at
each location is specific to the EEVX.1 release.

Note
For additional information, refer to “Automating the License and WDIR Configurator
Settings” in the Installation and Administration Manual for your release.

Adding Custom Menu Selections to the Tools

Menu
You can add menu selections to customize the Tools menu. Doing so makes it easier to access
external programs that you use in conjunction with Constraint Manager or as part of your
constraint-driven design flow.
The tool appends menu selections that you add to the bottom of the Tools menu. You cannot
delete default Tools menu selections or change their order.

Procedure
1. From the Tools menu, click Customize.
2. In the Customize dialog box, click New, then complete these fields:
• Menu Text — The display name you want to associate with the custom menu
selection.
• Command — The executable file to run when you click the custom menu selection.
To specify the command, click the browse button, navigate to the appropriate folder
and filename, then click Open.
• Arguments — (Optional) An argument string to append to the command. Your
argument string can also include these variables:
o {CESDir} — Constraint Manager directory of the active project.
o {ProjectDir} — Top-level directory of the active project.
o {ProjectFile} — Filename of the .prj for the active project.
• Initial Directory — (Optional) A directory to use other than the current working
directory. This is useful if the command generates run-time files that it should store

Constraint Manager User's Manual, X-ENTP VX.2.8 127

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Overview and Setup
Customizing Command Shortcut Keys

in a different location. To specify an initial directory, click the browse button,

navigate to the appropriate folder, then click OK.
3. (Optional) You can do any of the following:
• To edit an existing custom menu selection, in the Menu Contents list box, click the
appropriate row, then modify any of the fields described in step 2 of this procedure.
• To change the order of a custom menu selection, in the Menu Contents list box, click
the appropriate row, then click Move Up or Move Down.
• To delete a custom menu selection, in the Menu Contents list box, click the
appropriate row, then click Delete.
4. After you finish adding or modifying existing custom menu selections, click OK.
Results
The bottom of the Tools menu is updated to reflect your changes.

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).

128 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 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 3-3. Constraint Manager Keyboard Shortcuts

Menu Command/Command Default Shortcut(s)
File > Open Project Ctrl+O
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

Constraint Manager User's Manual, X-ENTP VX.2.8 129

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Overview and Setup
Selecting or Creating Valor NPI Design Centers

Selecting or Creating Valor NPI Design

Centers
You can select from available Valor NPI design centers to choose the one that your layout tool
uses if you launch Valor NPI to perform analysis. A design center is a Valor NPI feature that
defines the rule set used during design for manufacturing analysis. If you need to make a new
design center, you can create one.
In addition to selecting a design center, you can also specify a checklist. You can do this
whether you choose a design center or not. Each design center provides you with the ability to
choose from unique checklists for that specific design center. The default checklists are
available if you do not specify a design center.

Note
It is important to understand that, by default, you cannot share design centers that you or
other team members create. In order to share them, you must configure your Valor NPI
environment in a specific way to support this usage. For more information, refer to “Sharing
Valor NPI Design Centers Among Team Members” on page 131.

Prerequisites
• Valor NPI is installed and part of your design environment.
• If selecting a design center, at least one must already be available.
Procedure
1. From the Tools menu, click Valor NPI.
2. Click one of these menu selections:
• Select Design Center — In the dialog box, use the dropdown to select the design
center or checklist you want to use (or both), then click OK.

Tip
To clear the active design center or checklist, choose the blank row for either
field.

• Create Design Center — In the dialog box, type a name for the new design center,
then click OK. Complete the steps in the Design Process Wizard.

Note
If you choose to create a new design center, you may first be presented with the
Valor License Configuration dialog box. From here, you can verify the selection
and ordering of licenses. To keep this dialog box from showing again, activate the
appropriate check box.

130 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Overview and Setup
Sharing Valor NPI Design Centers Among Team Members

Results
Depending on how you chose to use the procedure, you either created a new design center or
selected an existing design center, checklist, or both. If you chose a design center or checklist,
the Constraint Manager status bar updates to indicate that you are using Valor NPI.

Sharing Valor NPI Design Centers Among

Team Members
By default, users create their own design centers. If using Valor NPI as part of a team
environment, you may want to share a set of design centers among a group of team members.
Doing so ensures that everyone is using the same set of design centers if this is preferable.
Prerequisites
• Your team uses Valor NPI as part of their design flow.
Procedure
1. The team needs to decide upon a network location for the shared design centers (for
example, Z:\shared_design_centers). Refer to the Valor NPI documentation for details
about how to choose a location for your design centers.
2. All users who want to be part of the share must ensure that their VALOR_ENV_FILE
environment variable points to the proper folder that contains the env file. Constraint
Manager reads the VALOR_DIR variable in that env file to find the folder that contains
the design centers.
Results
The design team now uses a shared network location for all design centers. Any team member
who is configured this way can create, modify, and select from the shared set of design centers.

Constraint Manager User's Manual, X-ENTP VX.2.8 131

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Overview and Setup
Sharing Valor NPI Design Centers Among Team Members

132 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Chapter 4
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Removing Unused Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Searching for Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Filtering Spreadsheet Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Filtering the Spreadsheet by Row Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Resetting a Spreadsheet to its Default View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Constraint Group Creation and Modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Concurrent Constraint Entry With Other Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Constraint Value Commenting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Viewing Constraint Reference Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Viewing Design Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Checking Constraints Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Constraint Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
PCB Actuals Comparison With Constraint Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Update of Electrical Net Data and Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Painting Rules to Reuse Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Constraint Change Undo and Redo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Viewing and Reverting to Parent Cell Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Saving Constraint Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Constraint Manager User's Manual, X-ENTP VX.2.8 133

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Spreadsheet Usage
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.
Note
As you work with constraints on each spreadsheet page, you will notice that the tool lists a
small amount of constraints on multiple pages. If you change one of these constraint values,
any page that includes the constraint shows the change.

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Choosing From Among Change Impact Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Required Propagation Rules That Constraint Manager Maintains . . . . . . . . . . . . . . . . 138
Organization of Constraints Into Pages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Spreadsheet Page Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Spreadsheet Icons Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Resizing Spreadsheet Columns and Rows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Zooming the Display of Spreadsheet Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Expanding and Collapsing Spreadsheet Rows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Sorting Spreadsheet Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Deletion of Constraint Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Constraint Value Copy-and-Paste Between Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

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

134 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Spreadsheet Usage
Overview of Constraint Hierarchy and Overrides

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))
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 101. 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 4-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 103. 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.

Constraint Manager User's Manual, X-ENTP VX.2.8 135

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Spreadsheet Usage
Choosing From Among Change Impact Actions

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.

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.

Choosing From Among Change Impact Actions

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 134, 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 138.

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.

136 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Spreadsheet Usage
Choosing From Among Change Impact Actions

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 102.

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 4-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.

In the example illustration, an electrical net has an override at the physical net level for Length
or TOF Delay Min.

Figure 4-2. Electrical Net Constraint Override at Physical Net Level

If you change the electrical net value for this constraint, the tool reacts based on the Change
Impact Dialog setting. Depending on how you have Constraint Manager configured, the tool
would either keep the override value for physical net DCONN24, replace it, or prompt you for
the action to take.

Constraint Manager User's Manual, X-ENTP VX.2.8 137

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Spreadsheet Usage
Required Propagation Rules That Constraint Manager Maintains

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 102.
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
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 and Constraint
Templates 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.

138 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Spreadsheet Usage
Organization of Constraints Into Pages

• Template value for differential pairs — The constraint template assigned to a

differential pair is also assigned at the electrical net level.
Constraint Manager maintains this relationship on the Nets page.
• 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.
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 Topology Type value from the electrical
net and differential pair.
• Length or TOF Delay 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.
Constraint Manager maintains this relationship on the Nets page and Constraint
Templates page.
• Length or TOF Delay 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.
Constraint Manager maintains this relationship on the Nets page and Constraint
Templates page.
• 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.
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.
• Z-Axis Clearances — Adjacent-layer clearance constraints like Trace to Trace, Trace
to Pad, Trace to Via, Trace to Plane, and Trace to SMD Pad.

Constraint Manager User's Manual, X-ENTP VX.2.8 139

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Spreadsheet Usage
Organization of Constraints Into Pages

• Nets — This spreadsheet page contains the largest number of constraints, which fall into
these categories:
o Delays and Lengths — Time of flight (TOF) delay or length constraints like Type,
Minimum, Maximum, Match, Tolerance, and Formulas.
o Differential Pair Properties — Differential pair constraints like Convergence
Distance Tolerance, Distance to Convergence, and Separation Distance.
o I/O — FPGA constraints like I/O Standard.
o Net Properties — General net constraints like Analog, Bus, Net Class, Number of
Pins, and Topology Type.
o Overshoot/Ringback — Signal reflection constraints like Simulation Class, Static
and Dynamic Low and High Overshoot, High and Low Ringback, and Monotonic
Edge.
o Power Nets — Power-supply net constraints like Supply Voltage.
o Simulated Delays — Edge-rate delay constraints like Simulated Delay Type,
Minimum, Maximum, and Maximum Range.
o Template — Net template constraints like Name and Status.
• Parts — Component constraints are grouped into these categories:
o Delays and Lengths — Package constraints like Pin Package Length and Pin
Package Delay.
o I/O — FPGA constraints like I/O Standard.
o Pin Types — Pin constraints like IBIS Pin Type and Topology Pin Type.
o Thermal — HyperLynx Thermal constraints like Thermal Power Dissipation and
Thermal Junction Temperature.
• Noise Rules — Neighboring-net constraints like Noise Type, Constraint Class or
Electrical Net Name From and To, Parallelism Rule, and Crosstalk Max.
• 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 325.

140 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Spreadsheet Usage
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Selecting a Spreadsheet Page Using the Navigator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Displaying Only Specific Constraint Types on a Spreadsheet Page . . . . . . . . . . . . . . . . 142
Displaying All Constraint Types on a Spreadsheet Page . . . . . . . . . . . . . . . . . . . . . . . . . 142

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 4-3. Selected Spreadsheet Page: Z-Axis Clearances

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 displays just that constraint class and its nets. This type of row limiting occurs for
each object type.

Constraint Manager User's Manual, X-ENTP VX.2.8 141

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Spreadsheet Usage
Spreadsheet Icons Overview

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. Do one of the following:
• At the top of the spreadsheet page, click the Filters - Groups toolbar dropdown (also
known as “Constraint Groups”) and then select a constraint type.
• Right-click within the spreadsheet page, click Group, then click the 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
1. Select the page of interest.
2. Do one of the following:
• Click the Filters - Groups toolbar dropdown, then click All.

• Right-click within the spreadsheet page, click Group, 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.

142 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Spreadsheet Usage
Resizing Spreadsheet Columns and Rows

Table 4-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
From-to
Net class
Physical net
Pin
Pin pair
Power net
Rule-area scheme
Z-axis clearance rule

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).

Constraint Manager User's Manual, X-ENTP VX.2.8 143

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Spreadsheet Usage
Zooming the Display of Spreadsheet Pages

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.
Figure 4-4. 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.

144 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Spreadsheet Usage
Expanding and Collapsing Spreadsheet Rows

Procedure
1. Select the page of interest.
2. Do any of the following:
• To increase magnification, press F7.
• 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
1. Select the page of interest.
2. Do any of the following:
• 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

Constraint Manager User's Manual, X-ENTP VX.2.8 145

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Spreadsheet Usage
Sorting Spreadsheet Pages

rows, or just the parent rows. For example, sorting the Clearances page does not affect the order
of board layers.
Procedure
1. Select the page of interest.
2. Do one of the following:
• 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.

146 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Spreadsheet Usage
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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Deleting Constraint Values at the Object Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Deleting Constraint Values at the Design Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

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 Manager User's Manual, X-ENTP VX.2.8 147

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Spreadsheet Usage
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
• You must be using a Constraint Manager session launched from the front-end or a
standalone session of the tool.
• 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.

148 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Spreadsheet Usage
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 (standard and z-axis)
• Constants and variables
• Noise rules
• Package-type rules (layout only)
• Package-type-to-package-type rules (layout only)
• Parallelism rules
• Schemes (layout only)
• Templates
Restrictions and Limitations
• Constraint Manager needs the layout tool to determine if some rules are not used. For
this reason, you cannot remove some rules from schematic invocations of Constraint
Manager.
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.
2. Do any of the following:
• To learn why the tool considers a rule to be unused, hover over it to view tooltip text.

Constraint Manager User's Manual, X-ENTP VX.2.8 149

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Spreadsheet Usage
Searching for Constraints

• 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.
• 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.

150 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Spreadsheet Usage
Searching for Constraints

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.
• 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.

Constraint Manager User's Manual, X-ENTP VX.2.8 151

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Spreadsheet Usage
Filtering Spreadsheet Data

Filtering Spreadsheet Data

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
1. Do one of the following:
• 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).

152 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Spreadsheet Usage
Filtering Spreadsheet Data

• 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.

Constraint Manager User's Manual, X-ENTP VX.2.8 153

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Spreadsheet Usage
Filtering the Spreadsheet by Row Type

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

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 4-5. 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
1. Select the page of interest.
2. Do any of the following:
• 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.

154 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Spreadsheet Usage
Resetting a Spreadsheet to its Default View

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

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.

Constraint Manager User's Manual, X-ENTP VX.2.8 155

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Spreadsheet Usage
Constraint Group Creation and Modification

Constraint Group Creation and Modification

Constraint Manager comes with several pre-defined constraint groups that you can modify as
needed and restore to their default contents. You can also create new constraint groups, modify
them, and delete those that you create.
Creating Constraint Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Modifying a Constraint Group From Directly Within the Spreadsheet . . . . . . . . . . . . 158
Modifying a Constraint Group From Within the Constraint Groups Dialog Box . . . . 158
Deleting One or More Constraint Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Restoring the Content of a Default Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Creating Constraint Groups

You can create groups that include just a subset of the constraints displayed on a spreadsheet
page. For example, if your constraint modifications are limited to a common subset of Nets
spreadsheet constraints, you can create a group that includes just those constraints.
Doing so gives you the ability to increase the efficiency with which you modify constraints. If
managing other co-workers, creating unique groups can help to ensure that their focus remains
on the appropriate constraint subsets.

Note
Because constraint groups are a subset of all constraints located on a spreadsheet page,
modifying a spreadsheet constraint while in a group view results in the change appearing in
all views.

In the illustration, a user has created two constraint groups that serve as custom subsets of the
Nets spreadsheet page.

Figure 4-6. Constraint Groups

156 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Spreadsheet Usage
Creating Constraint Groups

The My Delays Group is a subset containing all delay constraints, both simulated and time of
flight. The other group, My Actuals Group, contains all actual values that are available on the
Nets spreadsheet page.

You can modify constraint groups that you create, and also those that are included with
Constraint Manager by default. The only group that you cannot modify is All. To provide you
with greater flexibility, the tool supports two ways of populating and modifying the contents of
a constraint group. The recommended approach is from directly within the spreadsheet.

Video
Watch the video to learn how to:

• Select a group.
• Add constraints to the group.
• Save changes to the group.

Procedure
1. Do one of the following:
• With the spreadsheet page of interest active, click the Filters - Groups toolbar
dropdown, then click Edit Constraint Groups.
• From the Edit menu, click Constraint Groups.
2. In the Edit Constraint Groups dialog box, click .

3. In the Create New Constraint Group dialog box, type a name for the group, then click
OK.

Note
You cannot use the same name for groups on different spreadsheet pages. For
example, to create a group called “Critical” on both the Nets and Parts pages,
prepend the name with the page name (as in, “Nets_Critical” and “Parts_Critical”).

4. Click Apply.

Constraint Manager User's Manual, X-ENTP VX.2.8 157

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Spreadsheet Usage
Modifying a Constraint Group From Directly Within the Spreadsheet

5. Modify or populate the contents of the constraint group in one of these ways:
• “Modifying a Constraint Group From Directly Within the Spreadsheet” on page 158.
This is the recommended method. You can drag-and-drop columns and visually
review your progress while you make your changes.
• “Modifying a Constraint Group From Within the Constraint Groups Dialog Box” on
page 158.

Modifying a Constraint Group From Directly Within

the Spreadsheet
You can modify a constraint group through the spreadsheet to see exactly how the selection of
constraints appears when you activate the group.
Procedure
1. With the spreadsheet page of interest active, click the Filters - Groups toolbar dropdown,
then select the group you want to modify.
2. Do any of the following:
• To show specific, hidden constraint columns, right-click the column heading after
which you want to insert columns, then click Unhide Column(s). In the Add
Column(s) to Group dialog box, select one or more constraints, then click OK.

Note
If you are working with a new constraint group that you created previously but
did not populate, all available columns are hidden.

• To move a column, use click-drag to move it to a different position within the

spreadsheet.
• To hide specific columns, use click or Ctrl-click to select the column headings, right-
click one of the column headings, then click Hide Column(s).
• To hide all columns, right-click any column heading, then click Hide All Columns.

Modifying a Constraint Group From Within the

Constraint Groups Dialog Box
Although this is not the recommended approach for constraint group modification, you may
find it to be more useful than modifying a group directly in the spreadsheet due to the amount or
type of changes you need to make.

158 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Spreadsheet Usage
Deleting One or More Constraint Groups

Procedure
1. With the spreadsheet page of interest active, click the Filters - Groups toolbar dropdown,
then click Edit Constraint Groups.
2. In the Edit Constraint Groups dialog box, click the Select constraint group dropdown,
then click the constraint group you want to modify.
3. In the Constraints assigned to group list, do any of the following:
• To remove one or more constraints, use click or Ctrl-click, then click .

• To remove all constraints, click .

• To add constraints, in the All constraints list, select the constraints that you want to
appear in the group by doing any of the following:
o To add one or more constraints, use click, Ctrl-click, or Shift-click, then click .

o To add all constraints, click .

• To move one or more constraints up or down in the list order, use click or Ctrl-click,
then click or .

• To move one or more constraints to the top or bottom of the list, use click or Ctrl-
click, then click or .

Tip
If moving constraints, it can be helpful to keep constraints and their actuals
together.

4. If needed, you can rename a user-created group. To do so, click , type a new name,
then click OK.
5. After you finish modifying a constraint group, click Apply or Close.

Deleting One or More Constraint Groups

You can delete constraint groups you created. You cannot delete default constraint groups.
Prerequisites
• You must have created one or more constraint groups.
Procedure
1. With the spreadsheet page of interest active, click the Filters - Groups toolbar dropdown,
then click Edit Constraint Groups.

Constraint Manager User's Manual, X-ENTP VX.2.8 159

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Spreadsheet Usage
Restoring the Content of a Default Group

2. In the Edit Constraint Groups dialog box, do any of the following:

• To delete one constraint group, click the Select constraint group dropdown, click the
constraint group you want to delete, then click .

• To delete all constraint groups, click .

Restoring the Content of a Default Group

Because you can modify the constraint content of the default constraint groups, Constraint
Manager provides a way for you to restore the content of a default group.
Procedure
1. With the spreadsheet page of interest active, click the Filters - Groups toolbar dropdown,
then click Edit Constraint Groups.
2. In the Edit Constraint Groups dialog box, click the Select constraint group dropdown,
click the default group you want to restore, then click .

160 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Spreadsheet Usage
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 164.

Overview of Constraint Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Showing Indication of Remotely Changed Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . 163

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, Xpedition Designer). For example, two designers
can be working on the same design, though one has front-end Constraint Manager open and the
other Xpedition Designer. Actions taken in Xpedition Designer can cause cells in Constraint
Manager to become locked. Conversely, actions taken in Constraint Manager can cause the
same behavior to occur in Xpedition Designer.

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.

Constraint Manager User's Manual, X-ENTP VX.2.8 161

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Spreadsheet Usage
Overview of Constraint Locks

Example 4-2. Locked Constraint Cell

Here is another example of locking, but instead at the object level. The scheme “Ground” is
currently locked by another user who is editing its name. The lock icon indicates this condition.

Example 4-3. Locked Object

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 97.
• All clients are disconnected.
• The server is down.

162 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Spreadsheet Usage
Showing Indication of Remotely Changed Constraints

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.
Figure 4-7. 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 103.

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 161.

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 Manager User's Manual, X-ENTP VX.2.8 163

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Spreadsheet Usage
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.

If using a layout invocation of Constraint Manager, comments you make directly against
physical nets in the “Constraint Class/Net” column of the Nets spreadsheet display in the Net
Explorer (and Design Tips) of the layout tool after you synchronize the constraint set within the
layout tool.

In the figure, physical nets ( ) ADDRESS3 and ADDRESS5 have comments against them in
Constraint Manager, so the Net Explorer in the layout tool displays the comments. The
comment against ADDRESS4 is on the electrical net ( ), so the layout tool does not show the
comment.

Note
Physical net comments work in the opposite direction, too. Comments you make against
nets in the Net Explorer are displayed by Constraint Manager the next time you launch the
tool.

Adding Comments to Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Editing Constraint Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Deleting Constraint Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Viewing Constraint Comments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

164 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Spreadsheet Usage
Adding Comments to Constraints

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
1. Do one of the following:
• 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.
Figure 4-8. 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).

Constraint Manager User's Manual, X-ENTP VX.2.8 165

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Spreadsheet Usage
Editing Constraint Comments

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.
• 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
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

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
• 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
1. Select the page of interest.
2. Do one of the following:
• 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 .

166 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Spreadsheet Usage
Viewing Constraint Comments

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
1. Select the page of interest.
2. Do any of the following:
• 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.

• 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 4-9. Constraint Reference Illustration for Differential Spacing

Constraint Manager User's Manual, X-ENTP VX.2.8 167

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Spreadsheet Usage
Viewing Design Statistics

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.
Note
The number of “Technology Parts” provided in this report provides a count of those used in
the back-end design system. These technology parts are editable only in the back-end design
system, but they are also stored in Constraint Manager and available in this report. This number
does not refer to the number of technology models available to the tool.

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.
Prerequisites
• You are not using a remote development flow.
Procedure
From the Output menu, click Check Constraints Synchronization.

Note
Use the CesSyncCheck command to check constraints synchronization between
different projects.

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.

168 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Spreadsheet Usage
Checking Constraints Synchronization

Related Topics
CesSyncCheck

Constraint Manager User's Manual, X-ENTP VX.2.8 169

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Spreadsheet Usage
Constraint Diagnostics

Constraint Diagnostics
You can both check and correct constraint values using CES Diagnostics.
Checking Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Correcting Constraint Manager Diagnostics Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Listing of Constraint Manager Diagnostics Tests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

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

170 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Spreadsheet Usage
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.
2. Do any of the following:
• 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.

Listing of Constraint Manager Diagnostics Tests

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 4-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.
Scheme and clearance rule Checks if scheme names and clearance rule names are
name unique unique.
Clearance rule in all schemes Checks if clearance rule exists in all schemes.
Net class in all schemes Checks if all rule-area schemes include all defined net
classes.

Constraint Manager User's Manual, X-ENTP VX.2.8 171

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Spreadsheet Usage
Listing of Constraint Manager Diagnostics Tests

Table 4-2. Constraint Manager Diagnostics Tests (cont.)

Test Purpose
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.
Layer in all z-axis clearance Checks if layer exists in all z-axis clearance rules.
rules
Victims and aggressors valid Checks if victims and aggressors in noise rules exist.
Component valid Checks if all components are valid in terms of references to
pins.
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.
Pin sets consistency Checks if pins in pin sets belong to physical net.
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.
Electrical net unique Checks if electrical net name is unique.
Electrical net consistency Checks if all electrical nets contain correct physical nets.
Physical nets consistency Checks if each electrical net consists of only one 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
Connection pin pairs in Checks if valid connection pin pairs exist in electrical nets
electrical net that contain multiple physical nets.
Power net topology Checks if power net has the proper topology.
Unique from-tos in physical Checks if all from-tos in physical net are unique.
net

172 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Spreadsheet Usage
Listing of Constraint Manager Diagnostics Tests

Table 4-2. Constraint Manager Diagnostics Tests (cont.)

Test Purpose
From-to in only one net Checks if pin referenced by from-to belongs to the same
physical net as the from-to.
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.
Schemes and rules in all class Checks if all schemes exist for class to class clearance
to class clearance rules rules.
Unique template names Checks if template names are unique in the design.
Valid template Checks if content of constraint templates are valid.
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.
Nets constraint values Checks the integrity of constraints defined on nets.
consistency

Constraint Manager User's Manual, X-ENTP VX.2.8 173

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Spreadsheet Usage
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Updating Actuals Displayed in Constraint Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Clearing Actuals From the Spreadsheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Sharing PCB Actuals With Front-End Constraint Manager Sessions . . . . . . . . . . . . . . 176
Viewing All Constraint Violations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Constraint Violation Revision Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

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
1. From the Data menu, click Connect to Expedition.

Note
Typically, when you launch Constraint Manager it is automatically connected to
Xpedition Layout. This menu option is not present when you are already connected.

2. 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.

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 107.

174 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Spreadsheet Usage
Updating Actuals Displayed in Constraint Manager

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
being out of range. During the process of setting up the tool, you can specify the backlight
colors used by the tool.
Figure 4-10. 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
1. Select the page of interest.
2. Do any of the following:
• 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
1. Select the page of interest.
2. Do any of the following:
• Clear actuals from the current spreadsheet page — From the Data menu, click
Actuals, then click Clear This Page.

Constraint Manager User's Manual, X-ENTP VX.2.8 175

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Spreadsheet Usage
Sharing PCB Actuals With Front-End Constraint Manager Sessions

• Clear actuals from all spreadsheet pages — From the Data menu, click Actuals,
then click Clear All Pages.

Sharing PCB Actuals With Front-End Constraint

Manager Sessions
Although the layout software generates actuals as part of back-end constraint calculations, you
can also share those values with front-end Constraint Manager sessions. This is especially
useful for logic engineers on your design team who are interested in the actual values for critical
nets.
The team member who performs which of the actions in the procedure varies depending on your
design process. For a small design team, one person might perform the procedure in its entirety.
For large design teams working on very complex designs, a schematic designer would typically
make a call or send an email to request that a PCB layout engineer perform step 1 to export
actuals. An alternative to that approach is to adopt a process where actuals are exported at
multiple, scheduled times each day, or automatically each time they are updated.

Tip
There are several settings you can enable to make the display of actuals a nearly automatic
part of your front-end Constraint Manager session. To do this, you must enable unique
settings in both front-end and back-end invocations of the tool. Refer to “Specifying Other
Preferences” on page 107. The procedure points out each setting as it relates to streamlining the
manual process.

Procedure
1. In a back-end invocation of Constraint Manager, from the File menu, click Export, then
click Actuals.

Tip
You can have the tool do this automatically each time you update actuals by
enabling a setting in your back-end invocation. From the Setup menu, click
Settings. In the Settings dialog box, click Other, then under Actuals, enable the option
“Export actuals to front-end”.

2. In the Output log window, verify that the tool successfully exported actuals.
For example: “Xpedition actuals side file was exported on Thu Mar 08 16:22:22 2012.”
3. In a front-end invocation of Constraint Manager, from the Data menu, click Actuals,
then click Import Layout Actuals. To include thermal values, click Import Thermal
Actuals as a second selection.

176 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Spreadsheet Usage
Viewing All Constraint Violations

Tip
You can configure your front-end invocation of Constraint Manager such that you
are notified when updated actuals are available for import. To do this, from the
Setup menu, click Settings. In the Settings dialog box, click Other, then under Actuals,
enable the option “Show alert that new actuals can be imported.”
To further facilitate the sharing of actuals, you can enable an additional setting to
automatically update actuals upon start up. If used together with the settings mentioned
in the procedure, back-end Constraint Manager automatically updates actual values
when you load it, which in turn causes the tool to export them to front-end Constraint
Manager. The next time you open front-end Constraint Manager, it automatically pulls
in the updated actual values. You enable this setting separately in each invocation of the
tool. To do this, from the Setup menu, click Settings. In the Settings dialog box, click
Other, then under Actuals, enable the option “Auto update on start up.”

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 178.)

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 Manager User's Manual, X-ENTP VX.2.8 177

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Spreadsheet Usage
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 (aggressor, constraint class, net class, parallelism rule, and victim)
• Hierarchical paths
• Layer indices
• Object types (parallelism rules and power nets)
• Pin counts
• Rule names
Related Topics
# Pins
Constraint Class or Electrical Net Name Aggressor
Constraint Class or Electrical Net Name Victim
Hierarchical Path
Index
Net Class
Parallelism Rule
Power Net

Update of Electrical Net Data and Results

After you assign IBIS models to parts, the tool automatically updates electrical nets to include
changes based on the technology information in your IBIS models. If a new IBIS model
requires the tool to join two or more existing electrical nets, Constraint Manager resolves
existing constraint values.

178 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Spreadsheet Usage
Painting Rules to Reuse Constraints

Resolution of Existing Constraint Values

If the tool joins two or more existing electrical nets into a larger electrical net due to new IBIS
model assignments, Constraint Manager resolves the unique constraint values in each
constituent net based on these rules:

• The minimum Simulated Delay Min constraint value is used; the maximum Simulated
Delay Max constraint value is applied.
• The minimum Ringback Low Max constraint value is used; the maximum Ringback
High Max constraint value is applied.
• The minimum Static Low Overshoot Max constraint value is used; the maximum Static
High Overshoot Max constraint value is applied.
• The tool removes Dynamic Low Overshoot Max and Dynamic High Overshoot Max
constraint values from the new electrical net.

Painting Rules to Reuse Constraints

You can quickly copy all constraint values that you define in a spreadsheet row into the rows of
other design objects that can benefit from those values.
If painting rules to copy constraint values, it is important to remember that the design object
from which you copy must be the same as the design object to which you copy. For example, if
reusing the constraint values of a specific net row, make sure that you apply them to another net
row (it is the same type of design object).

Prerequisites
• You enabled display of the leftmost column (Setup > Cross Probing).
Procedure
1. On the spreadsheet, click the leftmost cell of a scheme, net class, constraint class, layer,
or net row.
2. Now that the row is highlighted, from the Edit menu, click Rule Painter.

3. Click the leftmost cell in the spreadsheet row for which you want to apply the copied
constraint values.

Note
The Rule Painter shuts off automatically if you try to paste into a different row type.

4. Continue clicking additional rows to paint these rules where appropriate.

5. To turn off the Rule Painter, from the Edit menu, click Rule Painter.

Constraint Manager User's Manual, X-ENTP VX.2.8 179

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Spreadsheet Usage
Painting Rules to Reuse Constraints

Examples
Example of Copying Board Layer Constraint Values to Another Board Layer
Use these steps:

1. On the spreadsheet Trace & Via Properties page, expand a scheme, expand a net class,
then click the leftmost cell of the layer that holds the constraint values you want to
duplicate.
2. From the Edit menu, click Rule Painter.

3. On the spreadsheet, click the leftmost cell of the layer row to which you want to apply
the duplicate constraint values.
4. To apply these values to another layer, click its leftmost cell. When you finish, from the
Edit menu, click Rule Painter to disable rule painting.

180 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Spreadsheet Usage
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Rolling Back or Redoing Specific Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Supported Undo/Redo Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

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 4-3 on page 182. 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.

Constraint Manager User's Manual, X-ENTP VX.2.8 181

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Spreadsheet Usage
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 4-11. 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 4-3. Supported Undo/Redo Actions
Design Object Actions
Clearance rule Add, remove, and rename.
Constraint Add, change, propagate, rule
painter, copy, and paste.

182 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Spreadsheet Usage
Viewing and Reverting to Parent Cell Values

Table 4-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.
Noise rule Add and remove.
Pin pair Auto pin-pair, manual pin-
pair, and remove.
Rule-area scheme Add, remove, and rename.
Template Rename.
Z-axis clearance rule Add, remove, and rename.

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.
2. Do any of the following:
• 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.

Constraint Manager User's Manual, X-ENTP VX.2.8 183

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Spreadsheet Usage
Saving Constraint Changes

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).
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.
2. Do any of the following:
• 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.

184 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Chapter 5
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
Initially, the tool assigns all nets to the (Default) net class.

Creating Net Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Adding Nets to a Net Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Creating a Net Class From an Existing Net Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Deleting Net Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

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.

Constraint Manager User's Manual, X-ENTP VX.2.8 185

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Net Class Creation
Creating Net Classes

Figure 5-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
Watch the video to learn how to:

• Make a net class.

• Search for and add nets to it.

186 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Net Class Creation
Creating Net Classes

• Make an additional net class.

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. Although you are not limited to the levels of net-class
hierarchy you can create, 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: ! \ “ /
• 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.

Constraint Manager User's Manual, X-ENTP VX.2.8 187

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Net Class Creation
Adding Nets to a Net Class

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.

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 .

188 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Net Class Creation
Creating a Net Class From an Existing Net Class

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:

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.

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.

Constraint Manager User's Manual, X-ENTP VX.2.8 189

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Net Class Creation
Deleting Net Classes

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.
2. Do one of the following:
• 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.

190 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Chapter 6
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.
After you create a constraint class, you can create more constraint classes below it to create
hierarchy among nets within a constraint class. By doing so, you can apply general constraints
to all nets within the constraint class hierarchy, and then apply more specific electrical, signal
integrity, and high-speed constraints to the nets that make up the further groupings of constraint
classes.

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
Initially, the tool assigns all nets to the (All) constraint class.

Creating Constraint Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Creating Constraint Class Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Adding Nets to a Constraint Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Defining Bus Constraint Classes Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Types of Net Matching for Bus Constraint Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Creating a Constraint Class From an Existing Constraint Class . . . . . . . . . . . . . . . . . . 198
Deleting Constraint Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Creating Constraint Classes

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
Watch the video to learn how to:

• Create a constraint class.

Constraint Manager User's Manual, X-ENTP VX.2.8 191

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Class Creation
Creating Constraint Class Hierarchy

• Add a differential pair to the constraint class.

• View constraint class assignments.

Procedure
1. Do one of the following:
• 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:
• You cannot use these characters: ! \ “ /
• 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.

Creating Constraint Class Hierarchy

After you create a constraint class, you can create more constraint classes that are hierarchically
arranged below it. Constraint class hierarchy is very useful for certain types of high speed nets
(for example, DDR2 and DDR3) that require constraint values (for example, lengths) that must
match to each other in a mathematically-defined way.

192 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Class Creation
Creating Constraint Class Hierarchy

For example, after creating a top-level class for all bus nets (for example, “Bus Nets”) in a
design that should share many of the same electrical rules, you could add hierarchy to the
constraint class by creating additional classes that sit below “Bus Nets” to further group the
collection of nets that comprise this constraint class. In the example, the Bus Nets constraint
class contains two additional classes, which are “16-bit” and “32-bit.”

Figure 6-1. Navigator Showing Bus Nets Constraint Class With Two Additional
Hierarchical Classes

Tip
In the Constraint Manager Navigator, you can drag and drop constraint classes into other
constraint classes to create or redefine hierarchy. If your goal is to drag multiple constraint
classes at the same time, after you use Ctrl-click to select them, you must continue to hold the
Ctrl key while you drag them.

Although you are not limited to the levels of hierarchy you can create under a constraint class, it
is important to understand that creating hierarchy is not always the best approach. In most cases
it is a best practice to create a new top-level constraint class or simply modify some constraint
values manually for certain nets in a constraint class.

Procedure
1. Do one of the following:
• In the Navigator, expand Constraint Classes. Right-click a constraint class, then
click New.
• On the Nets spreadsheet page, right-click a constraint class, then click New.
2. Replace the default name “<user>_New” with a unique name for the hierarchical
constraint class.

Note
You can create multiple levels of hierarchy, but you should only do so if necessary.

Constraint Manager User's Manual, X-ENTP VX.2.8 193

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Class Creation
Adding Nets to a Constraint Class

Results
The new constraint class is now available for selection and assignment throughout Constraint
Manager. If needed, you can rename it. To do so, in the Navigator, expand Constraint Classes.
Right-click a constraint class, click Rename, type a new name, then press Enter.

Adding Nets to a Constraint Class

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
1. Do one of the following:
• 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
On the Nets spreadsheet page, select one or more nets, right-click a selected net,
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.

194 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Class Creation
Adding Nets to a Constraint 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.

6. 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 constraint 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 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.
2. Click , then click OK.
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.

2. Click , then click OK.

Constraint Manager User's Manual, X-ENTP VX.2.8 195

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Class Creation
Defining Bus Constraint Classes Automatically

Defining Bus Constraint Classes

Automatically
You can automate the process of creating and adding nets to unique constraint classes to group
the nets that comprise a bus. Automate this task to save time and reduce the instance of error.
Afterward, the tool enables the Bus constraint for each resultant constraint class.
Note
The tool uses the Bus constraint to indicate that your PCB layout software should enable bus
planning and routing capabilities for a specific constraint class.

Procedure
1. Choose Edit > Auto Bus.
2. In the Auto Assign Bus dialog box, in the Electrical Net Match String dropdown, specify
the match type you want to use, then click . For more information, refer to “Types of
Net Matching for Bus Constraint Classes” on page 197.
Under Proposed busses, Constraint Manager creates a row for each suggested bus. The
Suggested Bus Name column shows the name of each proposed constraint class.
3. (Optional) To have Constraint Manager group bus nets into constraint classes that
contain no fewer than a specific number of nets, type a value into the Minimum bus
width field.
4. Verify the suggested nets for each proposed bus constraint class. To do so, next to each
Suggested Bus Name, click .

5. In the Assign Nets to New Bus Constraint Class dialog box, under “Nets in new bus
constraint class”, verify that the list of nets is appropriate (or make adjustments), then
click OK. You can do the following:
• To move a suggested net out of the list, keeping it in its current constraint class, click
.

• To move a net from an existing constraint class into the list of nets that will comprise
the new bus constraint class, use the Existing Constraint Classes dropdown and the
Nets in existing constraint class list to select the appropriate nets, then click .

6. In the Auto Assign Bus dialog box, select the proposed bus constraint classes you want
to create by placing a checkmark beside each appropriate Suggested Bus Name. You can
also do the following:
• By default, the tool marks all proposed bus constraint classes for creation. To
quickly de-select all rows, click . To quickly select all rows, click .

• The Net Classes cell for each proposed bus constraint class lists all net classes to
which the proposed list of nets are currently assigned. After the tool creates a bus

196 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Class Creation
Types of Net Matching for Bus Constraint Classes

constraint class, it moves each net into the first net class listed in the Net Classes
cell. To choose another net class in the list, click .

• By default, the tool will create each bus constraint class as a child of the original
constraint class. To choose a different class, in the Constraint Classes cell, click .
You can also create the bus constraint class as a parent class by selecting Top Level
Class.
7. For the proposed constraint classes you select, resolve any naming errors, which the tool
indicates by shading the background color of a Suggested Bus Name cell. In the
example, you need to remove the backslash character from the Suggested Bus Name to
satisfy syntax requirements.
Figure 6-2. Suggested Bus Name With a Syntax Problem

8. Verify that your selections are correct, then click OK.

Results
Constraint Manager creates a new constraint class for each proposed bus that you selected and
moves the appropriate nets into the new constraint classes. The tool moves the nets that
comprise each bus into a single net class per your selection.
Related Topics
Types of Net Matching for Bus Constraint Classes
Bus

Types of Net Matching for Bus Constraint

Classes
Constraint Manager provides three methods you can pick from to determine which nets it
should suggest for grouping into a new constraint class.
Refer to the following type information:

• Digit suffix — (Default) Constraint Manager suggests constraint classes using nets that
include numeric characters at the end of a net name (for example, MicroNet0 and
MicroNet1). The resultant constraint class name is the common part of the net name (for
example, MicroNet).
• Bus nets — Constraint Manager suggests constraint classes based on busses defined in
the schematic tool. The name of the resultant constraint class includes a digit range at

Constraint Manager User's Manual, X-ENTP VX.2.8 197

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Class Creation
Creating a Constraint Class From an Existing Constraint Class

the end that indicates the number of nets in this class. For example, Primary_Bus[3:0]
means that this bus constraint class includes four nets: net three, net two, net one, and
net zero.
• Custom net match string — Type a custom search string using letters, numbers and
wildcard characters like “*” and “?”. This method is especially useful if you cannot use
one of the other methods due to an uncommon naming convention for nets.

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.
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.

Deleting Constraint Classes

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.

198 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Class Creation
Deleting Constraint Classes

2. Do one of the following:

• 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.

Constraint Manager User's Manual, X-ENTP VX.2.8 199

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Class Creation
Deleting Constraint Classes

200 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Chapter 7
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, but there is also a set of
general clearances you use to define required distances between board objects like testpoints.

Specifying General Clearance Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Rule-Area Scheme Creation and Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Specifying Trace Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Trace Width Rule Propagation Through Layers for Hierarchical Net Classes . . . . . . 212
Defining Via Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Clearance Rule Set Creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Clearance Rule Set Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Package Clearance Rule Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
3D Clearance Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

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.
For example, the minimum distance between testpoint centers is a general clearance rule that
you set globally and do not define between net classes. For a complete listing of general
clearance rules, refer to Table 1-2 on page 22.

Video
Watch the video to learn how to:

• Choose the Clearances tab.

• Display the Clearances toolbar.

Constraint Manager User's Manual, X-ENTP VX.2.8 201

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Physical Rule Definition
Specifying General Clearance Rules

• View general clearance rules and values.

Procedure
1. On the Clearances toolbar, click ; or, from the Edit menu, click Clearances, then
click General Clearances.
2. In the General Clearance Rules dialog box, modify rules that have an editable value. The
tool sets editable rule values against a white background. Refer to the table for
explanations of each general clearance rule.
3. After you finish, click OK.

Table 7-1. General Clearance Rules

Rule Defines the... Minimum Maximum Default
Value Value Value
Cavity Inside Edge Minimum acceptable distance 0 1 in 10 th
to Parts between the inside edge of a
cavity and all parts.
Cavity Outside Edge Smallest acceptable distance 0 1 in 10 th
to Non-Plane between the outside edge of a
Conductor cavity and all non-plane
conductors.
Cavity Outside Edge Minimum acceptable distance 0 1 in 10 th
to Plane Conductor between the outside edge of a
cavity and all plane conductors.
Cavity Edge to Smallest acceptable distance 0 1 in 10 th
Cavity Edge between a cavity edge and all
other cavity edges.
Contour, Cavity & Minimum acceptable distance 0 1 in 10 th
Mounting Hole to between a mounting hole
Mounting Hole (including contour and cavity) and
all other mounting holes.

202 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Physical Rule Definition
Specifying General Clearance Rules

Table 7-1. General Clearance Rules (cont.)

Rule Defines the... Minimum Maximum Default
Value Value Value
Contour & Smallest acceptable distance 0 1 in 10 th
Mounting Hole to between a mounting hole and all
Non-Plane non-plane conductors.
Conductor
Placement Outline to Minimum acceptable distance 0 1 in 10 th
Placement Outline between a placement outline and
all other placement outlines.
Placement Outline to Smallest acceptable distance 0 1 in 10 th
Placement Obstruct between a placement outline and
all placement obstructs.
Placement Outline to Minimum acceptable distance 0 1 in 10 th
Design Edge between a placement outline and
all design edges.
Trace to Resistor Smallest acceptable distance 1 nm 1 in 10 th
between a trace segment and all
resistors.
Pad to Resistor Minimum acceptable distance 1 nm 1 in 10 th
between a pad and all resistors.
Testpoint Center to Smallest acceptable distance 1 nm 1 in 10 th
Testpoint Center between the center of a testpoint
and all other testpoint centers.
Additional Hole Minimum acceptable additional 0 1 in 0
Conductor clearance between specific pin
Clearances: and via holes within pads and
• Drill Hole conductors (traces and planes).
• Laser Hole These clearance values must not
exceed the size of the annular ring
• Punched Hole
for the associated pads.
• Photo Hole
Note: The router also adds the
Drill Hole clearance to
mounting holes.

Note
All Additional Hole Conductor Clearances are valid whether contact pads exist or
not.

Constraint Manager User's Manual, X-ENTP VX.2.8 203

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Physical Rule Definition
Specifying General Clearance Rules

Figure 7-1. Additional Hole Conductor Clearances Example

204 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Physical Rule Definition
Rule-Area Scheme Creation and Management

Rule-Area Scheme Creation and Management

You use schemes to represent defined rule areas on a PCB. The (Master) scheme represents the
entire PCB area. Create additional schemes to separate areas of a board and then manage
constraint requirements for each board area independently from the global rule set.
The global rules for a design can be heavily constrained due to the requirements of relatively
small collections of critical nets that cross through concentrated board areas. For this reason,
you generally need additional schemes.

Creating Rule-Area Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Copying Rule-Area Schemes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Renaming Rule-Area Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Deleting Rule-Area Schemes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Resetting Clearance Rules to the Master Scheme. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
(Minimum) Scheme Clearances and Widths. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Creating Rule-Area Schemes

You can create additional schemes (aside from the (Master) scheme) that correspond to rules
areas created in the PCB (or that you expect to create in the PCB). After you create a scheme,
you can define trace and via rules and clearance rule sets to which only nets crossing or within
that board area must adhere.
Note
To understand how the layout software applies rules in overlapping rule areas, see “Batch
DRC for Overlapping Rule Areas” in Layout Verification Guide.

Video
Watch the video to learn how to:

• Learn the difference between (Master) and (Minimum) schemes.

• View trace constraints.

Constraint Manager User's Manual, X-ENTP VX.2.8 205

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Physical Rule Definition
Copying Rule-Area Schemes

• View default clearance values.

Procedure
1. In the Navigator, right-click Schemes, then click New Scheme.
2. Replace the default name “<user>_New” with a unique name for the scheme, keeping
the following in mind:
• You can use spaces.
• You cannot use these characters: ! \ “ and /
3. Press Enter.

Copying Rule-Area Schemes

By copying a rule-area scheme for which you have defined trace and via rules and clearance
rule sets, you can rename the copy, and then make modifications to that rule-area scheme to
reuse the majority of its constraint definitions on another area of the board.
Tip
In addition to copying an entire rule-area scheme, you can copy specific clearance rule sets
contained within a scheme. This is useful if you want to duplicate only a subset of a scheme
instead of an entire PCB rule area.

Procedure
1. Do one of the following:
• In the Navigator, expand Schemes.
• Locate a scheme using the Trace & Via Properties or Clearances spreadsheet
pages.
2. Right-click a scheme name, then click Clone.
As a result, the tool copies the scheme and gives it the default name:
“<user>_<scheme>_clone”
3. Hover over the clone, then click once.

206 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Physical Rule Definition
Renaming Rule-Area Schemes

4. Modify the name of the scheme, keeping the following in mind:

• You can use spaces.
• You cannot use these characters: ! \ “ and /
5. Press Enter.

Renaming Rule-Area Schemes

You can rename rule-area schemes as needed.
Caution
If you rename a scheme, the tool automatically resets all rule areas within that scheme to
those of the (Master) scheme. You must go into the PCB system and reset the rule areas to
use the new scheme created as a result of renaming the scheme.

Procedure
1. In the Navigator, expand Schemes.
2. Do one of the following:
• Right-click a scheme name, then click Rename.
• Click the name of a scheme, then wait for it to become editable.
3. Modify the name of the scheme, keeping the following in mind:
• You can use spaces.
• You cannot use these characters: ! \ “ and /
4. Press Enter.

Deleting Rule-Area Schemes

You can delete rule-area schemes you create as needed. You cannot delete the (Master) and
(Minimum) schemes.
Procedure
1. In the Navigator, expand Schemes.
2. Right-click a scheme name, then click Delete.

Constraint Manager User's Manual, X-ENTP VX.2.8 207

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Physical Rule Definition
Resetting Clearance Rules to the Master Scheme

Resetting Clearance Rules to the Master Scheme

For rule-area schemes you created, you can reset trace and via properties and clearances to
match the (Master) scheme.
The (Master) scheme, which is also known as the default rule set, typically represents the
majority of the clearance and width values for a board. The tool uses these values by default for
board areas that do not have unique schemes and rule areas assigned to them.

Tip
Reset all or a subset of the constraints stored in a scheme to the (Master) scheme to
effectively “start over” by replacing values of a user-created scheme with the default rules
and use them as a starting point.

Procedure
1. In the Navigator, expand Schemes, right-click a scheme, then click Reset to (Master).
2. In the Reset to (Master) dialog box, verify that the Area Scheme field lists the
appropriate scheme.
3. By default, the tool preselects all constraint types. Clear constraint types you do not
want to reset to the (Master) scheme, then click OK.
For example, to not reset Minimum Widths and Typical Widths, clear those sets of
constraint values.
Figure 7-2. Reset to (Master) Selections

208 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Physical Rule Definition
(Minimum) Scheme Clearances and Widths

Examples
Example of Resetting Class-To-Class Clearances and Expansion Widths to Those of the
(Master) Scheme
In this example, you want to reset just the class-to-class clearance rules and expansion widths of
user-created scheme “SchemeA” to those of the (Master) scheme.

Use these steps:

1. In the Navigator, expand Schemes, right-click SchemeA, then click Reset to (Master).
2. In the Reset to (Master) dialog box, click Unselect all, then click to select these
constraint types:
o Class to Class clearances
o Expansion Widths
3. Verify that the Area Scheme field lists the scheme that you want to reset to the constraint
values of the (Master) scheme, then click OK.

(Minimum) Scheme Clearances and Widths

The constraints within the (Minimum) scheme reflect the minimum clearances and widths
defined across all net classes within each scheme. Because the tool generates these values
dynamically, you cannot edit any values in the (Minimum) scheme.
Because each rule area can have a different net class scheme, and because each net class scheme
can have a full set of widths and clearances, it may be difficult to tell if some of the rules have
been set below the minimum acceptable rules for manufacturing. By referring to the values in
the (Minimum) scheme, you can verify that the clearance constraints in a design do not violate
any manufacturing minimums within any of the schemes you created.

Note
Typically, you do not assign the (Minimum) net class scheme to a rule area on the board.

Due to the nature of the (Minimum) scheme, it does not always include all class-to-class
clearance rules, but instead the clearance rule with the minimum constraint value among
duplicates. For example, if you have a clearance rule between net class A and net class B in the
(Master) scheme, and an additional scheme you created defines the same relationship between
net class A and net class B, the (Minimum) scheme shows the clearance rule with the lowest
constraint value.

Constraint Manager User's Manual, X-ENTP VX.2.8 209

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Physical Rule Definition
Specifying Trace Constraints

Specifying Trace Constraints

After you create a scheme to represent a rule area on a PCB, you can specify trace constraints to
which nets within the rule area must adhere. You can simultaneously define trace rules for all
board layers for nets in a net class, or do so individually for each board layer.
When specifying trace constraints, you can define values such as minimal, typical, and
expansion trace widths, typical impedance, and differential pair spacing. You can also override
these values for from-tos that must route on specific board layers.

Note
If you change the value for typical trace width, the field solver uses the existing board
stackup to calculate typical impedance. Likewise, if you change the value for typical
impedance, the tool uses the field solver to calculate typical width.

Video
Watch the video to learn how to:

• Change Trace Width constraints.

• Modify Differential Spacing.
• Verify constraint propagation to layers.

Procedure
1. Do one of the following:
• On the Trace & Via Properties spreadsheet page, expand a scheme.
• In the Navigator, expand Schemes, expand a specific scheme, then click Trace &
Via Properties.
2. Expand the (Default) net class, or a unique net class you created previously, then define
trace constraints in one of the following ways:
• To simultaneously define trace rules for all board layers, in the net class name row
(for example, (Default)), specify each value.

210 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Physical Rule Definition
Specifying Trace Constraints

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
press Enter. Constraint Manager updates each board layer to include this Minimum
Trace Width value.
Figure 7-3. Trace Width Constraints

• To individually define constraints for each board layer, in the appropriate board
layer row (for example, SIGNAL_1), specify each value.

Note
When specifying layers to route, you must do so in the (Master) scheme. When
working on a net class in the Master scheme and you change a net class via to
(None), the tool automatically changes all user-defined schemes to (None) for that
net class.

For example, to specify a Trace Width Expansion value of 12 th for board layers one
and two of the (Default) net class, in the SIGNAL_1 and SIGNAL_2 rows, type 12
in the Expansion cell.
Figure 7-4. Trace Width Constraints at the Layer Level

Constraint Manager User's Manual, X-ENTP VX.2.8 211

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Physical Rule Definition
Trace Width Rule Propagation Through Layers for Hierarchical Net Classes

Trace Width Rule Propagation Through Layers

for Hierarchical Net Classes
If your constraint and object data for a design includes hierarchical net classes, you can quickly
assign unique trace width constraints to each instance of a signal or plane layer as it appears in
all child net classes. Doing so makes it easy to allow for deviations from net class hierarchy if
you need to allow for larger or smaller trace widths when traces are on a certain board layer.
In the example illustration, you can see that trace width constraints become more tightly
constrained at deeper levels of net class hierarchy; however, the Trace Width Minimum
constraint for layer SIGNAL_3 is even more tightly constrained through the entire hierarchy.
One reason for the usage you see is for trace congestion on this layer. With a smaller minimum
value, it is easier to ensure that no traces will be routed any larger than needed.

212 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Physical Rule Definition
Defining Via Assignments

Example 7-1. Defining a Trace Width Rule for all Lower Levels of Net Class
Hierarchy

To replicate this, you would simply type “0.02” within the Parent_Class row of SIGNAL_3.
After you press Enter, Constraint Manager gives you the option to apply the same value to each
instance of layer SIGNAL_3 within the lower levels of net-class hierarchy. This approach
becomes even more beneficial if you have many child-level net classes and need to quickly and
accurately define a constraint deviation without having to type it multiple times.

Defining Via Assignments

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.

Constraint Manager User's Manual, X-ENTP VX.2.8 213

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Physical Rule Definition
Defining Via Assignments

Tip
The vias that are available for assignment are only those in your local library. To make
additional vias available, you must use Xpedition Library Manager to export them from
your central library to the local library. For more information, refer to “Library Services” in
Common Library Editors User’s Guide.

Procedure
1. On the Trace & Via Properties spreadsheet page, expand a scheme.
2. Do one of the following:
• 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. For information on how to define them, refer to Setup Parameters Dialog
Box - Via Definitions Tab in PCB Operations and Reference Guide.
3. In the Via Assignments dialog box, in the Net Class Via column, click the pulldown to
specify a different via assignment.

Tip
If defining multiple via assignments simultaneously, to set all to the default
assignment, click Set to Default.

(Optional) Use the dropdown buttons to change the Scheme and Net Class you want to
modify.
4. Repeat step 3 as needed. When you are finished, click OK or Apply.
Examples
Example of Net Class Via Assignments
In the example of the Via Assignment dialog box, two of three rows have a Net Class Via set to
a value other than the default via. This custom via assignment is for the (Master) scheme. The
net class “DiffPair” is a sub-class of the (Default) net class.

214 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Physical Rule Definition
Defining Via Assignments

Figure 7-5. Via Assignments per Via Span

Related Topics
Overriding Trace Width Constraints for From-Tos

Constraint Manager User's Manual, X-ENTP VX.2.8 215

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Physical Rule Definition
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.
Use standard clearance rule sets to specify spacing constraints for objects on the same board
layer. For objects on adjacent board layers, use z-axis clearance rule sets. Adjacent-layer
constraints are located on the Z-Axis Clearances spreadsheet page.

Note
The (Default Rule) and (Default Z-Axis Rule) clearance rule sets contain the default
clearances for a design. When assigning clearance rule sets between net classes, the tool
uses values in (Default Rule) by default; however, it does not use values in (Default Z-Axis
Rule) by default. You must explicitly assign them, or the rules of a different z-axis clearance
rule set, between net classes.

Creating Clearance Rule Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Defining Clearance Rules for a Rule Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Creating Z-Axis Clearance Rule Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Defining Z-Axis Clearance Rules for a Rule Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Defining Embedded Resistor Clearance Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Defining SMD Clearance Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Defining Bond Finger Clearance Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

Creating Clearance Rule Sets

After you create a scheme to represent a rule area on a PCB, you can specify clearance rules to
which net objects within the rule area must adhere. You can define clearance rules such as Trace
to Pad, SMD Pad to Trace, Resistor to Via, and Via to Plane.
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
Watch the video to learn how to:

• Observe a Trace Width Typical value.

• Create a clearance rule.
• Define a Trace to Trace value for the rule.

216 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Physical Rule Definition
Defining Clearance Rules for a Rule Set

• Assign a clearance rule between net classes.

Procedure
1. Do one of the following.
• In the Navigator, expand Schemes, right-click a specific scheme, then click New
Clearance Rule.
• On the Clearances spreadsheet page, right-click a scheme, then click New
Clearance Rule.
2. Replace the default name “<user>_New” with a unique name for the clearance rule set.
You can use spaces in clearance rule set names.
Results
The rule set now exists for constraint definition and assignment between net classes.

Defining Clearance Rules for a Rule Set

You define clearance rules of a rule set to specify the minimum amount of spacing you need
between objects on the same board layer.
Procedure
1. On the Clearances spreadsheet page, expand the (Master) scheme, or a previously
defined scheme.
2. Expand the clearance rule set for which you want to define clearance rules, then make
your definitions in one 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
cell of the Trace To heading, then press Enter. Constraint Manager updates each
board layer to include this Trace to Trace value.

Constraint Manager User's Manual, X-ENTP VX.2.8 217

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Physical Rule Definition
Defining Clearance Rules for a Rule Set

Figure 7-6. Trace To Clearances

• 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, to specify a Trace To Trace separation of 12 for board layer two, in
that row, type 12 in the Trace cell of the Trace To heading.
Figure 7-7. Trace To Clearances Per Layer

Note
The tool does not apply clearance rules you make unless you create associations
between specific net classes. To do so, refer to “Assigning Class-To-Class
Clearance Rules” on page 43.

218 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Physical Rule Definition
Defining Clearance Rules for a Rule Set

Examples
Example of Defining Differential Pair Spacing Between Channels and Ports
In this example, you have two ports, each of which consist of four differential pairs (eight
channels). You want to define unique constraint values to control spacing between differential
pairs (a), spacing between differential-pair traces (b), and spacing between traces of each port
(c). The illustration depicts these spacing requirements.

Figure 7-8. Three Trace-Spacing Requirements for Differential Pairs

Use these steps:

1. On the Trace & Via Properties spreadsheet page, define Differential Spacing as (a) in
each net class that includes one of these differential pairs.
2. Create separate net classes for each port, then assign each set of respective differential
pairs into these new net classes (for example, Port_1 and Port_2).
3. Create two clearances rule sets. One for nets within a port (b), and another for nets
between ports (c).
4. On the Clearances spreadsheet page, perform these tasks:
o For the nets within a port clearance rule set (for example, Within_Port), define Trace
to Trace as (b).
o For the nets between ports clearance rule set (for example, Across_Ports), define
Trace to Trace as (c).
5. Assign these class-to-class clearances rules:
o Within_Port between net class Port_1 and net class Port_1.
o Within_Port between net class Port_2 and net class Port_2.
o Across_Ports between net class Port_1 and net class Port_2.

Constraint Manager User's Manual, X-ENTP VX.2.8 219

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Physical Rule Definition
Creating Z-Axis Clearance Rule Sets

Figure 7-9. Class to Class Clearances

Creating Z-Axis Clearance Rule Sets

You can define z-axis clearance rules like Trace to Trace and SMD Pad to Trace. Unlike
standard clearance rules, which control spacing between design objects on the same signal
layer, z-axis clearance rules control spacing between design objects on different signal layers.
Z-axis clearance rules are especially important for high-speed designs where net density is very
tight.
It is important to note that z-axis clearance rules are absolutes based on just clearance. The tool
makes no exceptions as a result of layer-direction bias. For example, if dielectric thickness is
smaller than a z-axis clearance constraint, no applicable trace is allowed to run over or under
another trace. This is still the case if the traces cross at right angles.

Note
The tool does not apply z-axis clearances between segments of the same net.

Procedure
1. Do one of the following:
• On the Z-Axis Clearances spreadsheet page, right-click an existing clearance rule
set, then click New.
• In the Navigator, right-click Z-Axis Clearances, then click New Z-Axis Clearance
Rule.
2. Replace the default name “<user>_New” with a unique name for the clearance rule set.
You can use spaces in z-axis clearance rule set names.
Results
The rule set now exists for constraint definition and assignment between net classes.

220 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Physical Rule Definition
Defining Z-Axis Clearance Rules for a Rule Set

Defining Z-Axis Clearance Rules for a Rule Set

You define z-axis clearance rules of a rule set to specify the minimum amount of spacing you
need between objects on adjacent board layers.
Procedure
1. On the Z-Axis Clearances spreadsheet page, expand the clearance rule set for which
you want to define clearance rules.
2. Make your definitions in one of two ways:
• Define clearance rules for all board layers — In the clearance rule set name row,
specify any appropriate clearance rules. Refer to the example.
Figure 7-10. Z-Axis Clearances

• Individually define clearance rules for each board layer — In the appropriate
board layer row, specify any appropriate clearance rules. Refer to the example.
Figure 7-11. Z-Axis Clearances per Layer

Note
The tool does not apply z-axis clearance rules to your design until you create
associations between specific net classes. To do so, refer to “Assigning Z-Axis
Class-To-Class Clearance Rules” on page 229.

Defining Embedded Resistor Clearance Rules

If a design includes embedded resistive components like thick-film and thin-film resistors, you
can define spacing requirements between these parts and conductive board elements (for
example, traces, pads, and vias), and other resistors. Embedded resistors are typically located on
internal board layers but can also be placed on external board layers.
The difference between thick-film resistors and thin-film resistors is the production process
used to create each type of resistor. Thin-film resistors are typically “subtractive” because they

Constraint Manager User's Manual, X-ENTP VX.2.8 221

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Physical Rule Definition
Defining Embedded Resistor Clearance Rules

are created through an etching process. Thick-film resistors are typically “additive” because
they are instead printed on metal electrodes.

The clearance area that you define with each Resistor to <object> and EP Mask to <object>
constraint is depicted in the illustration. As you can see, thick-film resistor clearance is based on
protective-mask/overglaze adjacency. Clearance of thin-film resistors is based on production-
mask adjacency.

Figure 7-12. Embedded Resistor Clearances Defined by These Constraints

Note
Unlike embedded resistors, you do not need to define unique clearance rules for embedded
capacitive components. Standard pad clearance constraints (for example, Trace to Pad, Pad
to Pad, and Pad to Plane) handle their clearance requirements. Examples of embedded
capacitive components are mezzanine, screen-printed, and interdigitated capacitors.

Procedure
1. Select the Clearances spreadsheet page.

222 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Physical Rule Definition
Defining SMD Clearance Rules

2. Define any of these constraints for an entire clearance rule set, or individually for each
board layer of a rule set:
• Thick-film resistor clearance rules:
o “Embedded Resistor To Trace” on page 426
o “Embedded Resistor To Pad” on page 427
o “Embedded Resistor To Via” on page 428
o “Embedded Resistor To Resistor” on page 429
• Thin-film resistor clearance rules:
o “EP Mask To Trace” on page 430
o “EP Mask To Pad” on page 431
o “EP Mask To Via” on page 432
o “EP Mask To Resistor” on page 433

Note
“Mask” refers to the production mask of a thin-film resistor. It does not mean
solder mask.

Defining SMD Clearance Rules

If a design includes surface mount devices (SMD), you can define spacing requirements
between the pads of these devices and other board objects (for example, traces and vias). SMDs
are also commonly referred to as surface mount technologies (SMT).
Procedure
1. Select the Clearances spreadsheet page.
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 418
• “Via To SMD Pad” on page 424
3. Select the Z-Axis Clearances spreadsheet page.
4. Define “Trace To SMD Pad” on page 451 for an entire clearance rule set, or individually
for each board layer of a rule set.

Constraint Manager User's Manual, X-ENTP VX.2.8 223

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Physical Rule Definition
Defining Bond Finger Clearance Rules

Defining Bond Finger Clearance Rules

You can define spacing requirements between bonding fingers and objects like pads, planes,
and other bonding fingers.
A bonding finger is the connection point for a wire that comes off of a die. Bonding fingers can
be located on both substrate material and directly on a PCB. You use these constraints to define
spacing for both chip-on-board (COB) and package applications. If you define these constraints
for a package, the rules you use are generally much smaller than those for COB.

Procedure
1. Select the Clearances spreadsheet page.
2. Define these constraints for an entire clearance rule set, or individually for each board
layer of a rule set:
• “Bond Finger To Bond Finger” on page 434
• “Bond Finger To Trace” on page 436
• “Bond Finger To Pad” on page 438
• “Bond Finger To Via” on page 440
• “Bond Finger To Plane” on page 442
• “Bond Finger To SMD Pad” on page 444

224 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Physical Rule Definition
Clearance Rule Set Assignment

Clearance Rule Set Assignment

After you create class-to-class clearance rule sets, you must assign them between pairs of net
classes to make use of the constraint values you defined as part of a rule set.
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:

• Net class to net class

• Net class to (All)
• (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).

Assigning Class-To-Class Clearance Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Deleting Class-To-Class Clearance Rule Assignments. . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Assigning Z-Axis Class-To-Class Clearance Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Deleting Z-Axis Class-To-Class Clearance Rule Assignments . . . . . . . . . . . . . . . . . . . . 231

Assigning Class-To-Class Clearance Rules

After you create clearance rule sets for a rule-area scheme, 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, a common concern is high voltage nets in a design that need certain
spacing around them based on the voltage level of each net.

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

• The tool obeys class-to-class clearance rules 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) use (Default Rule). This assignment
in the matrix is hardcoded into the top-left cell as (All) to (All).

Constraint Manager User's Manual, X-ENTP VX.2.8 225

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Physical Rule Definition
Assigning Class-To-Class Clearance Rules

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 25.
Video
Watch the video to learn how to:

• Display the Class to Class Clearances dialog box.

• Ensure that the dialog box shows the correct scheme.
• Assign a rule between two net classes.

Procedure
1. On the Clearances toolbar, click ; or, from the Edit menu, click Clearances, then click
Class to Class Clearance Rule.
2. In the Class to Class Clearances dialog box, in the “Net Class to Class Clearance Rules
for Scheme” pulldown, select a scheme.

Tip
Many schemes use the same rule assignments and you can save time by
prepopulating a scheme with the assignments of another scheme. To do so, click .
In the Select source scheme dialog box, select a scheme, then click OK.

3. Populate cells in any of 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.
• Clone certain cell assignments of another scheme — Select one or more cells,
right-click, click Clone rules from scheme, then click a scheme.

226 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Physical Rule Definition
Assigning Class-To-Class Clearance Rules

• Copy and paste — Select one or more continuous 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 7-13. Highlighting Shows Cell Changes

4. Continue making rule assignments between net classes.

Tip
Optionally, to revert all changes, click . To undo a single change, right-click a cell,
then click Restore initial rule.

5. To assign class-to-class clearance rules for a different scheme, return to step 2.

6. After you finish, click Apply or OK.
Examples
Example of Clearance Rule Assignments
In this example, there are four net classes (10th, 20th, 30th, and 40th), and the (Default) net
class. There are also four clearance rules of the same name. Each of the clearance rules defines
all clearance constraints to the same value as the name of the clearance rule set. The clearance
constraints defined for (Default Rule) are all set to 5 th.

Constraint Manager User's Manual, X-ENTP VX.2.8 227

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Physical Rule Definition
Assigning Class-To-Class Clearance Rules

Figure 7-14. Clearance Rule Assignments by Net Class

The usage of common names for net classes and clearance rule sets is only for the illustrative
purposes of this example, but you may find it useful to group nets into classes based on this
style of naming.

Here is a listing of all clearance rule assignments based on the dialog box example:

• (Default Rule) is the hardcoded assignment between all net classes, (All) and (All). If all
other cells in this picture where empty, (Default) would be the only rule assigned
between every possible pairing of net classes. The middle callout in the picture is an
example of this. If it is blank, it uses (Default Rule).
• The clearance rule 10th is assigned between the net class 10th and all other net classes.
• The clearance rule 20th is assigned between the net class 20th and all other net classes.
• The clearance rule 30th is assigned between the net class 30th and all other net classes.
• The clearance rule 40th is assigned between the net class 40th and all other net classes.
• The clearance rule 10th is assigned between the net class 20th and itself. This means that
nets within this class can use smaller clearances (based on the definitions in the rule set).
• The clearance rule 20th is assigned between the net class 30th and itself. This means that
nets within this class can use smaller clearances (based on the definitions in the rule set).
• The clearance rule 30th is assigned between the net class 40th and itself. This means that
nets within this class can use smaller clearances (based on the definitions in the rule set).

228 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Physical Rule Definition
Deleting Class-To-Class Clearance Rule Assignments

Related Topics
Creating Clearance Rule Sets

Deleting Class-To-Class Clearance Rule

Assignments
You can delete class-to-class clearance rule assignments as needed. If doing so, you can delete
single rules, multiple rules, or all rules.
Procedure
1. On the Clearances toolbar, click ; or, from the Edit menu, click Clearances, then click
Class to Class Clearance Rule.
2. In the Class to Class Clearances dialog box, in the “Net Class to Class Clearance Rules
for Scheme” pulldown, select a scheme.
3. Do any of the following:
• Delete a single rule assignment — Click a cell, 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
Optionally, to revert your changes to the scheme, click .

4. After you finish deleting rule assignments, click Apply or OK.

Assigning Z-Axis Class-To-Class Clearance Rules

After you create z-axis clearance rule sets, you use the same spreadsheet page to assign rule sets
between one or more pairs of net classes. If selecting net classes to associate with a clearance
rule, you can quickly specify all net classes by using the (All) row.
If assigning these clearance rules between net classes, you can only create relationships for the
(Master) scheme; however, your layout system uses them for all rule areas (rule-area schemes).
For example, if your design includes ten user-created rule-area schemes, assigning a z-axis
clearance rule set between net class A and net class B results in those ten schemes and the
(Master) scheme using the assignment.

The illustration shows z-axis trace to trace relationships for two net classes. Because the net
classes contain mostly high-speed nets, that by nature are driving fast edge rates, it is important
to specify adjacent layer clearances between their net objects.

Constraint Manager User's Manual, X-ENTP VX.2.8 229

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Physical Rule Definition
Assigning Z-Axis Class-To-Class Clearance Rules

Figure 7-15. Z-Axis Trace to Trace Minimums

Depending on the number of adjacent layers that separate two design objects, z-axis clearance
rules may not be necessary. For this purpose, you can disable these rules when the number of
layers between design objects exceeds a certain amount. For example, after applying a z-axis
clearance rule set named “Fast_Clocks” to net class A and net class B, you specify that the
maximum depth is 5 layers. As a result, the tool will not obey Trace to Trace distances between
nets in class A and B when validating z-axis distances between layers one and seven, two and
nine, and so on.

Note
The tool obeys class-to-class clearance rules 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.

Procedure
1. On the Clearances toolbar, click ; or, from the Edit menu, click Clearances, then click
Z-Axis Class to Class Clearance Rule.
2. In the grid display under Source Net Class(es), click within an editable cell to select the
rule to use between two specific net classes.

Tip
To simultaneously assign the same rule to multiple cells, use Ctrl-click and Shift-
click to select a group of cells. After you select the last cell, you must continue
holding Ctrl or Shift while you make the rule selection.

3. (Optional) To specify a maximum layer depth between design objects:

a. In the cell you just edited, click .

b. In the Setup Z-Axis Clearance dialog box, click the Max layer depth dropdown,
select a maximum value, then click OK.
To specify a maximum layer depth that includes all layers, in the Max layer depth
dropdown, select 0. It is important to understand, though, that because of the shielding

230 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Physical Rule Definition
Deleting Z-Axis Class-To-Class Clearance Rule Assignments

effects of plane layers, as soon as the tool encounters a plane layer, it ignores all layers
after the plane layer.

Note
If you change the number of stackup layers, the tool changes all “Max layer depth”
values that were equal to or are now greater than the previous signal layer count. In
each case, it changes “Max layer depth” to match the new amount.

4. Continue making rule assignments between net classes.

Note
Those that you do not explicitly define (empty cells) do not use (Default Z-Axis
Rule).

5. After you finish, click OK.

Related Topics
Creating Z-Axis Clearance Rule Sets

Deleting Z-Axis Class-To-Class Clearance Rule

Assignments
You can delete z-axis class-to-class clearance rule assignments as needed.
Procedure
1. On the Clearances toolbar, click .

2. Click the row of an existing class-to-class clearance rule assignment, then press Delete,
or click the empty selection (which is the first in the list).
3. After you finish removing assignments, click OK.

Constraint Manager User's Manual, X-ENTP VX.2.8 231

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Physical Rule Definition
Package Clearance Rule Assignment

Package Clearance Rule Assignment

You use package clearances rules to specify required clearance distances between specific
packages types and other objects on a board. When doing so, you define package clearance type
rules to create general clearance rules for a certain package, and package-type-to-package-type
clearance rules to create more specific clearance rules for pairings of certain packages.
Assigning Package Clearance Type Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Deleting Package Clearance Type Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Assigning Package-Type-to-Package-Type Clearance Rules . . . . . . . . . . . . . . . . . . . . . 233
Deleting Package-Type-to-Package-Type Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Package Side and End Determination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

Assigning Package Clearance Type Rules

You can assign clearance rules to each package type to specify the required amount of clearance
distance between a package type and all other design components that come close to it on a
board layer.
Each package type clearance rule you define can be followed for the top of the board, its
bottom, or both the top and bottom sides. This gives you the ability to create more spacing or
less spacing between components depending on the assembly technique used when placing
components on the board, the soldering techniques used, or both. For example, you can define a
package type clearance rule for integrated circuit flip chips that requires a bottom-side clearance
of 200 th between this component type and all other design objects.

Note
If using the Xpedition Layout tool as part of your design flow, unique package types you
create in the Cell Editor of that PCB layout tool show up in Constraint Manager as part of
the drop-down list of selectable package types. To create a unique package type in Xpedition
Layout, you must use the Clearance Type field of the Cell Editor. For more information, refer to
the documentation for the Xpedition Layout tool.

Procedure
1. On the Clearances toolbar, click ; or, from the Edit menu, click Clearances, then
click Assign Package Type Clearances.
2. In the Package Clearance Type Rules dialog box, to the right of Package type clearance
override rules, click to create a new rule.

3. In the Package Clearance Type cell, click .

4. In the Select Package Type dialog box, select a package type (for example, IC - BGA),
then click OK.

232 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Physical Rule Definition
Deleting Package Clearance Type Rules

5. In the Side cell, click to specify a board layer side of top, bottom, or both sides.
6. In the Clearance cell, specify the required clearance distance for this package type.

Note
Note the following:
• This clearance defines the required distance between this package type and all other
design objects.
• The minimum value is 0 and the maximum value is 1 in.

7. After you finish, click Apply or OK.

Deleting Package Clearance Type Rules

You can delete package clearance type rules as needed.
Procedure
1. On the Clearances toolbar, click .

2. In the Package Clearance Type Rules dialog box, under Package type clearance override
rules, click a row, then click .

Tip
To select multiple rules, use Ctrl-click.

3. After you finish, click Apply or OK.

Assigning Package-Type-to-Package-Type
Clearance Rules
In addition to defining package clearance type rules, you can define package-type-to-package-
type rules. These rules give you the ability to specify directional component clearances between
specific package types for packages on the top, bottom, or both board layers.
Prerequisites
• You know how each package you want to select defines side and end. For more
information, refer to “Package Side and End Determination” on page 235.
Procedure
1. On the Clearances toolbar, click .

Constraint Manager User's Manual, X-ENTP VX.2.8 233

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Physical Rule Definition
Assigning Package-Type-to-Package-Type Clearance Rules

2. If you have not done so already, create two package clearance type rules to associate
before you continue to step 3. For more information, refer to “Assigning Package
Clearance Type Rules” on page 232.
3. In the Package Clearance Type Rules dialog box, next to “Package type to package type
clearance override rules”, click to create a new rule.

4. In the Pkg Clr Type cell of the new row, click to select the first Package clearance type
override rule you created.
5. In the second Pkg Clr Type cell, click to select the second Package clearance type
override rule you created.
6. In the Side, Direction, and Clearance cells, specify the side, direction, and clearance
distance between package types, then click OK. (The minimum clearance value is 0 and
the maximum clearance value is 1 in.)
Here are definitions for each direction you can choose:
• All — Top, bottom, left, and right sides of one component type to the top, bottom,
left, and right sides of another component type.
• Side to Side — Left and right sides of one component type to the left and right sides
of another component type.
• End to End — Top and bottom ends of one component type to the top and bottom
ends of another component type.
• Side to End — Left and right sides of one component type to the top and bottom
ends of another component type.
• End to Side — Top and bottom ends of one component type to the left and right
sides of another component type.

Caution
The direction types “Side to End” and “End to Side” are unique only if you
define values for both pairings. If you define a value for one but not the other,
the undefined pairing uses the value you specified for the defined pairing. For
example, if you define a value for “Side to End” but not “End to Side,” “End to
Side” uses the “Side to End” value, too.

7. After you finish, click Apply or OK.

Examples
Example of Assigning a Package-Type-to-Package-Type Rule for Both Layer Sides and All
Directions
In this example, you want to assign a package-type-to-package-type rule between Discrete -
Chip components and IC - Flip Chip parts. Each of these package types already has a package
clearance type rule that requires a clearance distance of 50 th between instances of these

234 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Physical Rule Definition
Deleting Package-Type-to-Package-Type Rules

components and all other board objects. However, if these components are in the same vicinity
on a board layer, you require a clearance distance of 500 th between them, and for all directions.

Use these steps:

1. With the Clearances spreadsheet page active, on the Clearances toolbar, click .

2. In the Package Clearance Type Rules dialog box, next to Package type to package type
clearance override rules, click .

3. In the first Pkg Clr Type cell of the new row, select Discrete - Chip.
4. In the second Pkg Clr Type cell, select IC - Flip Chip.
5. In the Side cell, select Both, then in the Direction cell, select All.
6. In the Clearance cell, type 500. After you finish, the bottom portion of the Package
Clearance Type Rule dialog box should look like the illustration.
Figure 7-16. Discrete - Chip to IC - Flip Chip Clearance Rule

Deleting Package-Type-to-Package-Type Rules

You can delete package-type-to-package-type rules as needed.
Procedure
1. With the Clearances spreadsheet page active, on the Clearances toolbar, click .

2. In the Package Clearance Type Rules dialog box, under Package type to package type
clearance override rules, click a row, then click .

Tip
To select multiple package type to package type clearance rules, use Ctrl-click.

3. After you finish, click Apply or OK.

Package Side and End Determination

To define the appropriate directional clearance rules between packages, you need to know
which parallel “sides” of a package are defined in your layout system as the sides, and which are
defined as the ends.

Constraint Manager User's Manual, X-ENTP VX.2.8 235

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Physical Rule Definition
Package Side and End Determination

The illustration depicts the difference between side-to-side, end-to-end, side-to-end, and end-to-
side clearances between directional package type clearance rules based on package orientation
within Cell Editor.

Figure 7-17. Package-Type-to-Package-Type Directional Clearances

How a package cell is oriented in Cell Editor controls what the sides and ends are. The sides are
always on the left and right, and the ends are always top and bottom. Therefore, if you change
the orientation of a cell, the definition changes accordingly. In Figure 7-17, the long sides are
left and right (sides), and the short sides are top and bottom (ends). In Figure 7-2, the orientation
on the right would correspond to the directional clearances in the figure.

Example 7-2. Cell Editor Showing Different Orientations for the Same Package
Cell

You might be wondering why side-to-end and end-to-side are not the same. Although you can
define them as if they are, having the ability to define clearances based on “which side” and
“which end” give you greater flexibility. For example, if the end of an IC-BGA is next to the
side of an IC-SIC, you might want more clearance than if the side of an IC-BGA is next to the
end of an IC-SIC. Commonly, you use a distinction like this to provide a greater or lesser
amount of room depending on adjacency of component pins. Some components have the same
number of pins on sides and ends, while others have pins on just sides or ends. How you define

236 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Physical Rule Definition
Package Side and End Determination

these clearances can vary greatly based on the unique footprint of each component, and the
clearance relationships you want to create between them.

If defining end-to-side and side-to-end rules, it is important not to define redundant rules. For
each pairing of package types, you only need a single end-to-side rule and one side-to-end rule
for the purpose of defining all clearance requirements. For two example packages A and B, you
would define just one of each set of these rules, but not both:

• End A to side B, side A to end B

• Side B to end A, end B to side A

Note
If you assign a package-type-to-package-type rule, the tool overrides the package
top and bottom clearances you defined in each package with the clearances defined
in the package adjacency rule.

Constraint Manager User's Manual, X-ENTP VX.2.8 237

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Physical Rule Definition
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.
Note
For information on how your layout system uses and checks these 3D clearances, refer to
“Setting Online Checking for Placement” in PCB Verification Guide.

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 7-18. Relationship Between Minimum and Optimal 3D Clearance Values

Figure 7-18 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.

238 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Physical Rule Definition
Defining 3D Clearances

Defining 3D Clearances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

3D Clearance Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

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, on the General tab, in the From Any and 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. On the General or Package tabs, click Add Clearance or Add Package, then select
the appropriate pairing (for example, from Bond Wire to Assembly).
b. (Optional) When adding a 3D package clearance, click the Side dropdown menu to
change the default selection of Both sides to just Top or Bottom.
c. 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 on the
General tab). You must define values for both of the Optimal cells (or leave both
blank).
d. 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).

Constraint Manager User's Manual, X-ENTP VX.2.8 239

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Physical Rule Definition
3D Clearance Descriptions

Note
To reset a 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.

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.
Figure 7-19. 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.

3D Clearance Descriptions
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:

• 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 7-2. 3D Objects
Object Description
Active Board The current PCB project open in Constraint Manager.

240 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Physical Rule Definition
3D Clearance Descriptions

Table 7-2. 3D Objects (cont.)

Object Description
Assembly The physical packaging (enclosure) in which the Active
Board (PCB) resides.
Bond Wire A conductive wire that forms a connection in one of these
ways:
• By leaving the surface of the Active Board and returning
to another point on the Active Board.
• By leaving the Active Board and connecting to a die pad
on top of a die.
Board Edge Cavity wall or edge in the current Active Board.
Component Physical package placed within the layout system.
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.

Usage Notes
• To make a certain 3D clearance available for definition, click Add Clearance, then
choose a pairing of objects.
• 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.

Constraint Manager User's Manual, X-ENTP VX.2.8 241

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Physical Rule Definition
3D Clearance Descriptions

242 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Chapter 8
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

Topology Specification for Nets and Constraint Classes . . . . . . . . . . . . . . . . . . . . . . . . . 245
Net Pin Pair Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Defining Discrete Component Pin Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Length and Delay Rule Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Formula Creation and Error Checking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Constant and Variable Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Simulated Delay Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Defining Overshoot and Ringback Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Power-Supply Net and Constraint Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Modifying Xpedition I/O Designer FPGA Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Defining Constraints for Single-Pin Nets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Display Pattern Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

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.

Constraint Manager User's Manual, X-ENTP VX.2.8 243

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Net Constraint Definition
Specifying General Net Constraints

Procedure
1. With the Nets spreadsheet page active, in the Filters - Groups toolbar dropdown, click
Net Properties.

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 if 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.

244 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Net Constraint Definition
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.

Constraint Manager provides router instruction in the form of from-tos, each of which is
composed of two design or component pins that respectively designate the router to etch from
one pin to another pin.

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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Specifying Topology Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Manually Defining Netline Ordering (From-Tos) for a Specific Net . . . . . . . . . . . . . . . 247
Changing Topology Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Overriding Trace Width Constraints for From-Tos . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Advanced Topology Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

Topology Considerations
You should be aware of certain things before specifying topologies.

Difference Between From-Tos and Pin Pairs

Often times, from-to relationships can be confused with pin pair designations. To better
understand these separate design attributes, refer to these definitions:

• Net line ordering/from-tos — Ordered, physical pairings of component pins that

instruct the router where to etch from and to when creating physical transmission lines
(traces).
• Pin pairs — Unordered pairings of component pins that are created for the purpose of
defining relationships between pins in the form of constraints.

Constraint Manager User's Manual, X-ENTP VX.2.8 245

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Net Constraint Definition
Specifying Topology Type

Multiple Load Handling

When there are at least two loads, the layout tool creates a virtual pin to join all of the sources.
The layout tool then balances the loads from the joining virtual pin. It follows this procedure for
TShape, Star, and HTree topology types.

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.

When you manually define netline ordering, both nets result with the same ordering definition.
Whether in whole or as a starting point, it depends on net similarity:

• In the case of symmetrical nets, after you manually define netline ordering for one net,
the tool automatically applies it to the other net.
• If you have a differential pair that is comprised of asymmetrical nets, first manually
define netline ordering for the net with the most pins. After you complete that process,
the tool stores the ordering as a temporary constraint template and it presents you with
the Constraint Template Matching dialog box. Through it, you can modify the ordering
as needed for the other net that makes up the differential pair.
Constraint Manager applies this approach with the goal of making the netline ordering process
as efficient as possible. Due to the relative, common characteristics of nets used to create most
differential pairs, a strategy that leverages re-use of manual netline ordering is a natural
solution.

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 , Chained , TShape , Star , and
HTree . When a pre-defined topology type is not appropriate for a specific net, you can
manually define netline ordering.

246 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Net Constraint Definition
Manually Defining Netline Ordering (From-Tos) for a Specific Net

When creating a custom topology type for a net, you do so through the process of manual
netline order. For all pre-defined topology types, your layout system performs automatic netline
ordering during routing.

Procedure
1. With the Nets spreadsheet page active, in the Filters - Groups toolbar dropdown, click
Net Properties.

The tool also displays topology constraints as part of the All group, but you may find
it easier to work with topology constraints if the Nets spreadsheet page displays only
them.

Caution
If you change a topology type from Custom or Complex to a pre-defined topology
type, the tool deletes all pin pairs, from-tos, and virtual pins. When changing
between Custom and Complex topology types, you have the option of preserving pin
pairs.

2. Do one of the following:

• In the spreadsheet row of the net or constraint class to which you want to assign a
topology type, click the Topology Type field, then select a pre-defined topology type
(MST, Chained, TShape, HTree, or Star), Custom, or Complex.
• 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.

Results
If you chose Custom or Complex, the next step is to perform netline ordering to define the
custom topology type. If you include pin sets as part of a Custom topology, the tool
automatically changes it to Complex to indicate the usage of pin sets.
Related Topics
Topology Type

Manually Defining Netline Ordering (From-Tos) for

a Specific Net
After you set the Topology Type constraint for a net to “Custom” or “Complex,” you must order
the net.

Constraint Manager User's Manual, X-ENTP VX.2.8 247

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Net Constraint Definition
Manually Defining Netline Ordering (From-Tos) for a Specific Net

Video
Watch the video to learn how to:

• Enable the Topology toolbar.

• Display the Netline Order dialog box.
• Create from-to connections.
• Observe changes to the Ordered column.

Procedure
1. Do one of the following:
• On the Nets spreadsheet page, click the row of the net for which you want to
manually define netline ordering, then on the Topology toolbar, click .

• After you click a net row, from the Edit menu, click Netline Order.
2. In the list of available pins, click a row to select the From pin.

Note
If defining from-tos between pin sets, select pin sets instead of pins in both the From
and To fields. Also, you can select both types of objects.

3. In the list of available pins, click a row to select the To pin.

4. Verify the From pin and To pin fields, then click . If the From pin and To pin fields do
not contain the correct pins, click to clear the designation.

Note
As you create from-tos, you may find that not enough source (S) pins or load (L)
pins exist, and you cannot create a valid topology. If this occurs, you must exit the
dialog box and switch to the Parts spreadsheet page. From there, you can change the
Topology Pin Type constraint of one or more relevant component pins, and then start
this procedure over again.

248 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Net Constraint Definition
Changing Topology Type

5. Repeat steps 2 through 4 for each from-to you want to create. After you finish, click
OK.

Tip
To automatically create pin pairs from each from-to, select the “Automatically
create pin pairs from from-tos” check box. In the example, five pin pairs were
created, each matching a from-to.

Figure 8-1. Automatically Created Pin Pairs

Changing Topology Type

Whenever you change the Topology Type constraint for a net or constraint class, any pin pairs,
from-tos, and virtual pins defined for the net, or individual nets in the constraint class, can be
lost.
In the case of switching from Custom to Complex (or vice-versa), you can preserve pin pairs
that are not associated with virtual pins.

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.

Constraint Manager User's Manual, X-ENTP VX.2.8 249

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Net Constraint Definition
Overriding Trace Width Constraints for From-Tos

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.
(Optional) If changing from Custom to Complex, or Complex to Custom, you can
preserve pin pairs. To do so, select the check box “Preserve pin pairs not associated with
virtual pins.”
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

Overriding Trace Width Constraints for From-Tos

You can optionally override the trace width constraints (for example, Trace Width Typical or
Trace Width Minimum) defined for a net as part of its trace and via rules. Doing so gives you
the ability to specify trace width on a pin-to-pin basis, in effect, overriding the net class trace
width for certain pin pairs.
Prerequisites
• The net's Topology Type must be Custom.
• The net must have gone through netline ordering.
• The net cannot be part of a differential pair.
• Filters > Levels > From-To must be enabled in order to view spreadsheet rows for
from-tos.
Procedure
1. On the Nets spreadsheet page, in the From To Constraints Layer cell, ensure that you
have selected the appropriate board layer.

250 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Net Constraint Definition
Overriding Trace Width Constraints for From-Tos

2. In the From To Constraints Trace Width cell, type the override value.
Results
Based on the trace width override you typed, the tool updates the From To Constraints Z0 value
to display the calculated impedance.
Related Topics
From To Constraints Layer
From To Constraints Trace Width

Constraint Manager User's Manual, X-ENTP VX.2.8 251

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Net Constraint Definition
Advanced Topology Creation

Advanced Topology Creation

You can use pin sets to construct advanced topologies for nets that require the characteristics of
multiple topology types.
Creating Pin Sets to Construct Advanced Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Changing the Order of Pin-Set Pins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Deleting Pin Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

Creating Pin Sets to Construct Advanced Topologies

When a net contains a large number of pins, sometimes the best approach to constructing an
advanced topology is to group pins into subsets called pin sets.
For example, a 16-pin net that requires characteristics of both T-shape and chained topology
types is a good candidate for pin sets. This would result in three pin sets, consisting of two 3-pin
T-shape topologies and one 10-pin chained topology. After you create pin sets, you can define
from-to relationships between pin sets, and pin sets and pins. You can also create higher-level
pin sets by grouping existing pin sets into new pin sets.

Procedure
1. On the Nets spreadsheet page, click the row of the net for which you want to create a pin
set, then on the Topology toolbar, click .

2. In the Netline Order dialog box, click one of these topology types:
• — T-shape, which automatically balances load branches, though the trunk branch
may not match. T-shape is used exclusively for constructs that include three objects
(pins or pin sets).
• — Chained, which chains all selected pins between the first and last pins you
select. The tool does not create virtual pins for this type of pin set.
• — Minimum spanning tree, which connects selected pins in the best way possible
based on physical location. The tool does not create virtual pins for this type of pin
set.
• — Balanced, which requires the distance between the virtual pin and all pins in
the pin set to be equal.
• — Unbalanced, which performs no automatic balancing. This is especially useful
if you want to specify unequal constraints on branches of the pin set.
3. In the listing of available pins and pin sets, click each pin that should comprise the pin
set, then click Finish.

252 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Net Constraint Definition
Advanced Topology Creation

Note
If defining a T-shape pin set, you can select no more than three pins. For chained pin
sets, make sure you click the start pin first and the end pin last.

4. When you finish, click Apply or OK.

Results
The tool adds the pin set to the listing of Available pins / pin sets. The Pin/Set and Type
columns indicate that a row is a pin set by including the topology type in their text (for example,
CH 1 or Chained). Also, the Set Contents column includes a button.

Examples
Example of a Complex Net Topology
In the example, a complex net topology is constructed for a net that has nine pins. This net
topology is considered complex because it uses both pin sets and from-tos. This complex net
topology includes a T-shaped pin set, a chained pin set, and an MST pin set. It connects each of
the three pin sets, all of which include just three pins, with two from-tos.

First, here is a visual of the complex net topology that you are going to create. It is important to
note that the standard pins are shown as blue. The virtual pins created for the T-shaped pin set
are shown as green to distinguish them from the preexisting, or standard pins.

Figure 8-2. Visual of a Complex Net Topology

Figure 8-3 on page 254 shows what the Netline Ordering dialog box would look like for the
purpose of defining this complex net topology. The steps you would use to create it are listed
after the picture of the dialog box.

Constraint Manager User's Manual, X-ENTP VX.2.8 253

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Net Constraint Definition
Advanced Topology Creation

Figure 8-3. Netline Ordering of a Complex Net Topology

To create the netline ordering in the figure, or one that is similar, use these steps:

1. Create a T-shaped pin set (T_1) using pins R3-2, RT1-2, and U1-14.
2. Create a chained pin set (CH_1) using pins U2-14, U3-14, and U4-20.
3. Create an MST pin set (MST_1) using pins U5-14, U6-1, and U7-8.
4. Connect pin sets T_1 and CH_1 by creating a from-to between pins RT1-2 and U2-14.
5. Connect pin sets T_1 and MST_1 by creating a from-to between pins U1-14 and U5-14.

Changing the Order of Pin-Set Pins

You can change the order of pins in a pin set as needed.
Procedure
1. On the Nets spreadsheet page, click the row of the net for which you want to do this.
2. On the Topology toolbar, click .

3. In the Netline Order dialog box, in the row of a pin set, click .

254 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Net Constraint Definition
Advanced Topology Creation

4. In the Pin Set Order dialog box, click a pin to move, then click or .

5. Repeat step 4 for each pin for which you want to change the order.
6. Click Apply.
7. When you finish, click Apply or OK.

Deleting Pin Sets

You can delete pin sets as needed.
Procedure
1. On the Nets spreadsheet page, click the row of the net for which you want to do this.
2. On the Topology toolbar, click .

3. In the Netline Order dialog box, you can do this in one of these ways:
• Click the row of an individual pin set, then click .

• To delete all pin sets, click .

4. When you finish, click Apply or OK.

Constraint Manager User's Manual, X-ENTP VX.2.8 255

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Net Constraint Definition
Net Pin Pair Creation

Net Pin Pair Creation

You create pin pairs so that you can define constraints for specific connections that result from
the linking of the two pins.
For example, you can define a pin pair between an output pin of a microprocessor and an input
pin of another microprocessor that are part of the same net. You can then constrain the signal
delay or length between these pins such that it stays within a specific threshold, or minimum
and maximum. Here is an example of this.

Example 8-1. Pin Pair Constraints Definition

Note
You can define pin pairs for nets that are of topology type TShape , HTree , Star ,
Custom , or Complex. You cannot define pin pairs for nets that are of topology type Chained
or MST .

After you define specific pairs of pins, the tool precedes the spreadsheet column referring to a
pin pair designation with the icon. Be careful not to confuse this icon with the resultant icon
of non-graphical netline ordering ( ), which you use to create from-to relationships.

You can define pin pairs manually, semi-automatically, and automatically for each net. If
automating the pin pair definition process for one or more nets, you should always verify the
accuracy of the pin pair definitions that Constraint Manager produces. If a specific pin pair
definition is not appropriate, you can instead manually define a pin pair.

Internal Component-Pin Delay Inclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

Creating All Pin Pairs Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Creating Only Source-Load Pin Pairs Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Creating Pin Pairs Semi-Automatically. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Creating Pin Pairs Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Deleting One or More Pin Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

256 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Net Constraint Definition
Internal Component-Pin Delay Inclusion

Internal Component-Pin Delay Inclusion

If you want to constrain signal delay such that it includes internal component-pin delays, you
can construct pin pairs using electrical board description (EBD) pins.
If using EBD pins, both pins of the pin pair must be of this pin type. Depending on your design
methodology, you might begin the constraint process for some pin pairs by including EBD pins
at the start, or instead, later change some standard pin pairs to EBD pin pairs to solve design
challenges.

The illustration depicts the physical difference between an external (that is, standard) pin pair
and an internal EBD pin pair.

Figure 8-4. Standard and EBD Pin Pairs

As you can see, the physical length of the connection between pin pairs is longer for EBD pin
pairs because internal component connections are included in addition to the trace segment
between external pins. After you create an EBD pin pair, you can specify delay and simulated
delay (signal edge rate) constraints.

Creating All Pin Pairs Automatically

In addition to creating pin pairs manually and semi-automatically, you can have Constraint
Manager automatically create all pin pairs for a net.
Prerequisites
• The net’s Topology Type constraint must be TShape, HTree, Star, Custom, or Complex.
Procedure
1. On the Nets spreadsheet page, click a net row.
2. Do one of the following:
• On the Pairs toolbar, click .

• From the Edit menu, click Pin Pairs, then click Auto Pin Pair Generation.

Constraint Manager User's Manual, X-ENTP VX.2.8 257

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Net Constraint Definition
Creating Only Source-Load Pin Pairs Automatically

Creating Only Source-Load Pin Pairs Automatically

In addition to the other methods of pin pair creation, you can have Constraint Manager
automatically create all source-load pin pairs for a net.
Prerequisites
• The net’s Topology Type constraint must be TShape, HTree, Star, Custom, or Complex.
Procedure
1. Select the Nets spreadsheet page.
2. Do one of the following:
• Right-click a net row, then click Auto Source-Load Pin Pair Generation.
• Click a net row, then choose Edit > Pin Pairs > Auto Source-Load Pin Pair
Generation.

Creating Pin Pairs Semi-Automatically

In addition to creating pin pairs automatically or manually for a net, you can create them semi-
automatically. If you use this method, you define the start pin of a pin pair and then let
Constraint Manager determine the appropriate end pin.
Prerequisites
• The net’s Topology Type constraint must be TShape, HTree, Star, Custom, or Complex.
Procedure
1. On the Nets spreadsheet page, click a net row.
2. From the Edit menu, click Pin Pairs, then click Add Pin Pairs.
3. In the Define Pin Pairs dialog box, click to create a new pin pair relationship.

4. Click the Start Pin field, then select a pin.

5. Click .

Constraint Manager fills the End Pin field.

6. Repeat steps 3 through 5 for each pin pair you want to define in this way.
7. After you finish defining pin pairs, click OK.

258 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Net Constraint Definition
Creating Pin Pairs Manually

Creating Pin Pairs Manually

In addition to creating pin pairs automatically or semi-automatically for a net, you can create
them manually. You generally do this if the other methods of pin pair creation do not work for
certain pin pairs you need to be available in a design.
Prerequisites
• The net’s Topology Type constraint must be TShape, HTree, Star, Custom, or Complex.
Procedure
1. On the Nets spreadsheet page, click a net row. From the Edit menu, click Pin Pairs,
then click Add Pin Pairs.
2. In the Define Pin Pairs dialog box, click to create a new pin pair relationship.

To make any internal EBD pins available for pin-pair definition, click .

3. Click the Start Pin field, then select a pin.

4. Click the End Pin field, then select a pin.

Tip
To automatically create a pin pair, click instead of selecting the End Pin.

5. Repeat steps 2 through 4 for each pin pair you want to define in this way.
6. After you finish defining pin pairs, click OK.

Deleting One or More Pin Pairs

You can delete pin pairs as needed.
Procedure
1. On the Nets spreadsheet page, click a net row.
2. From the Edit menu, click Pin Pairs, then click Add Pin Pairs.
3. In the Define Pin Pairs dialog box, click to select one or more pin pairs, then click .

4. After you finish deleting pin pairs, click OK.

Defining Discrete Component Pin Pairs

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

Constraint Manager User's Manual, X-ENTP VX.2.8 259

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Net Constraint Definition
Defining Discrete Component Pin Pairs

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 8-7 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 .

260 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Net Constraint Definition
Defining Discrete Component Pin Pairs

• 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 8-5. 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 8-6. 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).

Constraint Manager User's Manual, X-ENTP VX.2.8 261

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Net Constraint Definition
Defining Discrete Component Pin Pairs

Figure 8-7. 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.

262 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Net Constraint Definition
Length and Delay Rule Definition

Length and Delay Rule Definition

You use length and delay rules to specify acceptable run lengths or signal transmission times 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 or delay rules among certain nets and specify a tolerance to provide room for
accommodating routing obstructions.

Specifying Length or Delay Rules for Nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Net Length and Delay Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Tolerance Routing of Nets Within a Constraint Class . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Specifying Maximum Length as a Percentage Above Manhattan Length . . . . . . . . . . . 266
Matching Delay or Length Rules Among Nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Matching Length or Delay Tolerance at the Constraint Class Level . . . . . . . . . . . . . . . 268

Specifying Length or Delay Rules for Nets

You can specify length or delay rules for nets, differential pairs, and pin pairs. When specifying
these rules, you can do so based on physical or electrical properties. For example, to specify
them from an electrical perspective, use time of flight instead of length. Time of flight is an
electrical observance that is defined by the duration of time for signal propagation between two
pins.
Conversely, to specify these rules from a physical perspective, use length instead of time of
flight. Length is a physical rule that defines the minimum and maximum trace distance between
pins. When a rule of this type is put in place, the router uses these minimum and maximum
values to determine an acceptable trace distance between the minimum and maximum range.
For example, setting Length or TOF Delay Min to 100 th and Length or TOF Delay Max to 300
th would give the router a range of 200 th between these minimum and maximum values.

Note
The tool does not support the use of constants in Length or TOF Delay Min and Length of
TOF Delay Max.

Procedure
1. With the Nets spreadsheet page active, in the Filters - Groups toolbar dropdown, click
Delays and Lengths.

Constraint Manager User's Manual, X-ENTP VX.2.8 263

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Net Constraint Definition
Specifying Length or Delay Rules for Nets

Note
These constraints are also displayed as part of the All group, but you may find it
easier to work with delay constraints if the Nets spreadsheet page displays only them.

2. In the row of the net for which you want to specify rules, use the available constraint
fields to define values based on length or time of flight. Here is a length example.
Figure 8-8. Length Rule

Note
If you want to include the length or time of flight 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 or time. Based on the example, you might
instead use 150 for Min and 350 for Max.

Examples
Example of Specifying a Length Rule for a Net Pin Pair
1. In the Type field of the pin pair for which you want to specify a length rule, click, then
select Length.
2. In the Min field, type a value for the minimum acceptable trace length between pins.
3. In the Max field, type a value for the maximum acceptable trace length between pins.
In the example illustration, the user chose a minimum value of 1000 th and a maximum
value of 1500 th. Notice that this pin pair delay rule is a single instance that does not
have a match relationship or match tolerance associated with it.
Figure 8-9. Net Pin Pair With a Length Rule

264 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Net Constraint Definition
Net Length and Delay Calculations

Related Topics
Length or TOF Delay Type
Length or TOF Delay Min
Length or TOF Delay Max

Net Length and Delay Calculations

When you define a time of flight delay or length constraint for an entire net instead of just a pin
pair, length is calculated by combining the trace segment lengths between each pin in the net.
When you use the delay method, each trace segment length is converted to corresponding delay
values based on trace length and the propagation velocity associated with the board layer on
which a trace segment is located. If the calculated length or time of flight delay is less than the
minimum constraint for the net, one of the trace segments is increased to satisfy the specified
minimum delay.

Note
For electrical nets, the physical length of any devices that join physical nets is included in
the length calculation, if available.

In order for delay to be calculated, these requirements must be met:

• The layer stackup must have at least one plane layer (ground or voltage).
• The dielectric layers must have a valid thickness (greater than 0) and a valid dielectric
constant (greater than or equal to 1).
• The signal and plane layers must have a valid thickness (greater than 0).

Delay Value Default

If one or more of the requirements is not met, a delay value based on the default propagation
velocity is used. This default value is 170 ps/inch (2.04 ns/ft).

Tolerance Routing of Nets Within a Constraint

Class
Aside from defining general minimum and maximum delay or length constraints for nets within
a constraint class, you can also assign a tolerance to an entire constraint class through use of the
Length or TOF Delay tolerance (“Tol”) constraint. Doing so constrains the router to match the
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

Constraint Manager User's Manual, X-ENTP VX.2.8 265

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Net Constraint Definition
Specifying Maximum Length as a Percentage Above Manhattan Length

at the constraint-class level, but it is used by default for all lower-level objects (for example,
sub-level constraint classes and electrical nets).

Child-level constraint classes within a parent constraint class use the defined tolerance of the
parent constraint class by default; however, you can define a tighter tolerance at the child-class
level. In the event that you want to specify a tighter tolerance at the net level, you can do so by
defining a match relationship and then specifying a tolerance for the matched group of nets. To
do so, refer to “Matching Delay or Length Rules Among Nets” on page 266.

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 or TOF Delay 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 or TOF Delay 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%. This is shown in the figure.

Figure 8-10. Maximum Length as Manhattan Length

Matching Delay or Length Rules Among Nets

By creating match groups, you can use the delay rules you define for a single net or pin pair as
the delay rule for multiple nets or pin pairs. You can also create match groups that do not
include minimum or maximum delay rules, but instead are matched only within a range.

266 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Net Constraint Definition
Matching Delay or Length Rules Among Nets

You accomplish delay matching by setting up a match relationship, and optionally, a match
tolerance. The match feature of Constraint Manager delay rule specification is especially useful
when you want to use the same time-of-flight delay or length range for bus nets. If using match
groups, all nets or pin pairs with the same group identifier are routed to the same length or delay
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.
• A single match group can contain any combination of electrical nets, physical nets, and
pin pairs.
• 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 97.
Procedure
1. In the Match field of an electrical net, 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 or delay
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 delay 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 Specifying a Matched Time of Flight Delay for Several Pin Pairs
Use these steps:

1. In the Type field of the pin pair for which you want to specify a time of flight delay rule,
click, then select TOF.
2. In the Min field, type a value for the minimum acceptable time of flight between pins.
3. In the Max field, type a value for the maximum acceptable time of flight between pins.
4. In the Match field, type an alphanumeric identifier for this time of flight delay rule.
Optionally, type a tolerance value.
5. In the Match field of the net pin pairs for which you want to use this time of flight delay
rule, type the match identifier you chose in step 4.

Constraint Manager User's Manual, X-ENTP VX.2.8 267

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Net Constraint Definition
Matching Length or Delay Tolerance at the Constraint Class Level

In the example illustration, the user chose a minimum acceptable value of 40 ns and a
maximum acceptable value of 80 ns. The match identifier is set_a and has a tolerance
value of 5 ns. The user assigned this time of flight delay rule to the three net pin pairs
below it by typing set_a in each Match field. This match relationship means that each of
the four pin pairs must have a time of flight between 40 ns and 80 ns. Their respective
values must be within 5 ns of each other (for example, 60 ns, 61 ns, 63 ns, and 64 ns).
Figure 8-11. Net Pin Pair With a Time-Of-Flight Delay Rule

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.

Figure 8-12. Matching Length by Just Tolerance

Related Topics
Net Pin Pair Creation

Matching Length or Delay Tolerance at the

Constraint Class Level
In addition to matching these rules among nets, you can also match to a tolerance based on
constraint classes and their hierarchy. Doing so gives you the ability to easily ensure that all nets

268 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Net Constraint Definition
Matching Length or Delay Tolerance at the Constraint Class Level

within a constraint class end up with length or delay values that do not exceed a specific
tolerance.
Furthermore, if you have constraint classes that include child constraint classes, or even more
extensive hierarchy, you can define a tolerance at each level. For example, at the parent
constraint class level, you might define a tolerance of 50 th, while at a child constraint class
level a tolerance of 25 th.

Matching length or delay 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 delay 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. On the Nets spreadsheet page, in the Length or TOF Delay tolerance (“Tol”) cell of the
constraint class of interest, type a tolerance value.

Note
You can always edit Length or TOF Delay tolerance (“Tol”) cells for constraint
classes. Unlike net rows, you do not need to define a value in a Match cell to make a
tolerance (“Tol”) cell accessible.

2. (Optional) If there are child constraint classes for which you want to define tighter
tolerances, type a value in the associated Length or TOF Delay tolerance (“Tol”) cell.
The tolerance value for a child constraint class must be smaller than that of the
constraint class above it.
Examples
Simple Example of Matching Length Tolerance by Constraint Class
In this example, all nets within a constraint class are specified to be matched to within 100 th of
each other. To provide tighter tolerance for a subset of nets, two match groups are created. One
requires ADDRESS0 and ADDRESS1 to be matched to within 75 th. The other requires PCS0
and PCS1 to be matched to within 50 th. The four other nets in the class respect the matching
requirement defined at the constraint class level.

Constraint Manager User's Manual, X-ENTP VX.2.8 269

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Net Constraint Definition
Matching Length or Delay Tolerance at the Constraint Class Level

Figure 8-13. Simple Tolerance Matching by Constraint Class

Complex Example of Matching Length Tolerance by Constraint Class

In this example, a more complex usage of tolerance matching is shown. The parent constraint
class High_Speed_Nets has a tolerance requirement of 100 th. The child constraint class
High_Speed_Bus_Nets has a tighter tolerance of 50 th. To allow for even tighter tolerances
within the child constraint class, two match groups are created. The first requires that two nets
are matched within a tolerance of 30 th. The other requires that four nets are matched within a
tolerance of 15 th. All other nets in the parent or child class respect the matching requirement
defined at the relevant constraint class level.

Figure 8-14. Complex Tolerance Matching by Constraint Class

270 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Net Constraint Definition
Formula Creation and Error Checking

Formula Creation and Error Checking

You can create formulas to constrain delay or length relationships between net objects if you
require complex relationships that go beyond minimum and maximum values. By checking
formulas you create, you can ensure that no errors exist in the syntax you use.
Defining Formulas to Create Net Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Including Formula Tolerance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Tolerance Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Multiple Formula Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Solving Formulas to Check for Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Complex Formula Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

Defining Formulas to Create Net Relationships

You can define formulas to create delay or length relationships between nets, pin pairs, or
differential pairs. By doing so, you can set up delay relationships among similar design objects
that would benefit from such associations.
For example, you can set one pin pair delay to equal the delay of another (=), specify that the
delay of one net must be greater than or less than the delay of another (> or <), and add or
subtract the delay of one pin pair to or from the delay of another. You can also include constants
and variables to define net and pin pair delay with even more detail.

You should be aware of the following:

• Constraint Manager distinguishes between electrical and physical nets that you include
in formulas by encasing them with bracket symbols or pipe symbols:
o {\<electrical net name>\}
o |\<physical net name>\|
• If including virtual pins, they must appear in the form \VP#\-\VP#\. For example, to
include virtual pin number 12, type: \VP12\-\VP12\
Procedure
1. On the Nets spreadsheet page, in the Formulas Formula cell of the net, pin pair, or
differential pair for which you want to define a formula, construct a formula using
available constants, variables, and accepted operators (=, >, <, +, -).

Note
All formulas must begin with one of these operators: =, <, or >. If an operator is
missing, Constraint Manager assumes the = operator when it solves the formula.

Constraint Manager User's Manual, X-ENTP VX.2.8 271

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Net Constraint Definition
Including Formula Tolerance

Refer to these examples, which show common formula applications:

• A+3 — Length or delay equals constant A plus 3 units.
• B-2 — Length or delay equals constant B minus 2 units.
• >{\NET1\} — Length or delay must be greater than that of NET1.
• <{\NET1\} — Length or delay must be less than that of NET1.
• ={\NET1\} — Length or delay must be equal to that of NET1.

Note
Formulas assume ns unit of measure. If you are working with a different unit of
measure (for example, th), you must include it after the hardcoded value (for
example, 1000 th).

2. After you type an operator that requires a reference object (=, >, <), click the name cell
of the electrical net, physical net, differential pair, or other object that you want to use as
the reference. You can also type the object name, but clicking is recommended because
it is far more accurate and efficient if you have the option to do so.

Note
The reference object must be same type as the object for which you are defining the
formula. For example, if you define a formula for a net, the reference object must
also be a net.

Including Formula Tolerance

You can include tolerance in your formulas to introduce a range around a formula value.
For example, if you require the length of several nets to be larger than 3000 th, but a tolerance of
100 th is acceptable (that is, minimum value can be 2900 th), you can include the tolerance in
your formula.

Note
If you do not include a tolerance, 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 97.

Procedure
At the end of the formula, type +/-, the tolerance, then the unit of measure.

Examples
=2000th+/-100th specifies that the length can be between 1900 th and 2100 th.

272 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Net Constraint Definition
Tolerance Limitations

Tolerance Limitations
There are some limitations to using tolerances with formulas. In these cases, the tool reports
“Error in Formula.” Use the information in this topic to adjust formulas that include tolerance, if
needed.

Small Tolerances
If you specify very small tolerances, it is important for these values to be no smaller than 0.012
th or 0.002 ps. Using tolerance values below these limitations can cause errors to occur while
Constraint Manager solves a formula. Tolerance limitations are a general rule, but there are
exceptions.

For example, in a net that is part of a match group, the tolerance limitation may need to be
divided by the number of netlines, effectively making the smallest possible tolerance much
larger (for example, 0.048 th).

Note
Formula errors associated with tolerances below the limitations do not affect tuning. The
layout system always tunes based on the provided tolerance. For example, providing a
tolerance of 0.01 th will cause Constraint Manager to report a formula error, but layout tuning
will use the tolerance.

Greater Than and Less Than

You cannot use tolerances with formulas that include > or <. For example:

• Instead of <100+/-10 use <110

• Instead of >50+/-5 use >45

Constants
You cannot use a constant to specify tolerance. You must type a numerical value when you
want a formula to include tolerance.

Multiple Formula Entry

If you want to define two or more formulas for a net or pin pair, you must separate formulas
with the # character and include the net, pin pair, or differential pair name in each formula that
appears after the initial formula.
For example, if you want to set the delay constraint of a pin pair (for example, \U1\-\3\@\U2\-\
3\) to be equal to a pre-defined constant (for example, A) and less then a specific value (for
example, 800 th), the correct cell notation is =A#\U1\-\3\@\U2\-\3\<800th. The # symbol

Constraint Manager User's Manual, X-ENTP VX.2.8 273

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Net Constraint Definition
Solving Formulas to Check for Errors

defines an AND relationship between formula one (=A) and formula two (\U1\-\3\@\U2\-\3\
<800th).

Example 8-2. Multiple Formulas in Cell

Note
If typing multiple formulas, the net, pin pair, or differential pair name must immediately
follow the # symbol. If you type the # symbol, Constraint Manager automatically adds the
name. In the event that it does not, to quickly and accurately add an object name to a formula,
click its name cell.

Solving Formulas to Check for Errors

After you define formulas in Formulas Formula cells, you can check them for errors by solving
all formulas in your design.
During the checking process, Constraint Manager attempts to compute net and pin pair delay
values for each formula. When it is finished, you are notified of any formulas that contain errors
through a log file. In addition, the tool highlights Formulas Violation cells that contain
erroneous results to make them easier to find.

Note
Variables that you do not explicitly define in the Constants and Variables List dialog box do
not generate errors during this process. For this reason, it is important to ensure that your
formulas include the variables that you intend to use.

Procedure
On the Pairs toolbar, click ; or, from the Data menu, click Solve All Formulas.

Related Topics
Formulas Formula
Formulas Violation

Complex Formula Examples

Refer to the example formulas that show instances of complex usage.

274 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Net Constraint Definition
Complex Formula Examples

Example of a Formula Matching Length Within a Bus and Between Busses

In this example, you want to match the length for eight pin pairs that comprise a bus within a
tolerance of +/- 1.27 mm. In addition, you want to match the length of this bus between specific
external bus pin pairs within a tolerance of +/- 12.7 mm.

Use these steps:

1. Create two variables. One for within bus (for example, withinbus) matching and the
other for between bus (for example, betweenbusses) matching.
2. In the Formulas Formula cell of the first pin pair, type =withinbus+/-1.27mm#<pin pair
name>=betweenbusses+/-12.7mm

Note
Constraint Manager automatically adds the pin pair name after you press #.

For example, if the pair name is C1\-\1\@\C1\-\5\, the formula would be =withinbus+/-
1.27mm#C1\-\1\@\C1\-\5\=betweenbusses+/-12.7mm
3. For the seven remaining pin pairs, type or copy this formula in the Formulas Formula
cell.
4. For each external pin pair that you want to match between the pin pairs of this bus,
include =betweenbusses+/-12.7mm in the Formulas Formula cell.
For example, if a pin pair already includes its own length formula (for example,
>50mm), append it to the end (>50mm#<pin pair name>=betweenbusses+/-12.7mm).
This formula requires that the pin pair length be greater than 50 millimeters AND match
the betweenbusses value calculated during routing. The tolerance of the final value can
be +/- 12.7 millimeters. Here is a depiction of this formula in the cell.
Example 8-3. Complex Formula

Example of a Formula Where the Sum of Two Net Lengths Must be Less Than a Certain
Distance
In this example, you need the cumulative length of two nets to be less than 5000 th. The two
nets are B1 and B2.

Use these steps:

1. In Formulas Formula cell for net B1, type: < 5000th -

Constraint Manager User's Manual, X-ENTP VX.2.8 275

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Net Constraint Definition
Complex Formula Examples

2. Click net B2. Doing so adds this net to the Formulas Formula cell for net B1, resulting
with the completed definition: < 5000th -{\B2\}

276 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Net Constraint Definition
Constant and Variable Creation

Constant and Variable Creation

You can create constants and variables and then include them in length or delay formulas to
constrain these values with even greater control, or flexibility, depending on the requirements of
the circuit.
Creating Constants and Variables for Delay Rules and Formulas . . . . . . . . . . . . . . . . . 277
Deleting Specific Constants or Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Finding Variable References. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Creating Constants and Variables for Delay Rules

and Formulas
You can create constants and variables to use if defining length and delay formulas within the
Nets spreadsheet in the Formulas Formula field. Creation and application of constants and
variables is a way to provide delay rule consistency across multiple nets or pin pairs within a
design.
Unlike constants, you never associate a pre-defined value with a variable, nor do you set a
variable to a specific value within the Formulas Formula cell of a net, pin pair, or differential
pair row. Variables, also known as “free variables,” give you the ability to constrain delay of
several objects by group, with no regard for the delay value that is produced automatically or
manually during routing.

For example, if you want the length of 16 nets that comprise a bus to route to the same length,
but you do not care what the length is, you can set each net equal to this free variable (for
example, =samelength) and allow the router to determine the length to which to match each net.

Procedure
1. From the Edit menu, click Constants and Variables, then click Edit.
2. In the Constants and Variables List dialog box, make sure the tab that corresponds to the
data type you want to create is selected (Constants or Variables), then click .

3. In the Name field, type a name for the new constant or variable.

Note
Constant and variable names must start with a letter and may contain only letters,
numbers, and underscores.

4. If defining a constant, in the Value field, type a value for the new constant.
In the example, three variables have been created. As you can see, variables do not have
assigned values.

Constraint Manager User's Manual, X-ENTP VX.2.8 277

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Net Constraint Definition
Deleting Specific Constants or Variables

Figure 8-15. Constants and Variables

5. After you finish creating constants and variables, click OK.

Deleting Specific Constants or Variables

After you create one or more constants or variables, you can delete those you no longer need.
Procedure
1. From the Edit menu, click Constants and Variables, then click Edit.
2. In the Constants and Variables List dialog box, use the tabs at the bottom to view
available constants or variables.
3. Click the constant or variable row you want to delete, then click .

Tip
To select multiple constants or variables, use Ctrl-Click.

In the example, const_a and const_c are selected for deletion.

278 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Net Constraint Definition
Finding Variable References

Figure 8-16. Certain Constants Selected for Deletion

4. After you finish deleting constants and variables, click OK.

Finding Variable References

You can find variable references to view net and pin pair formulas that include variables.
Procedure
1. From the Edit menu, click Constants and Variables, then click Find Variables
Reference.
2. In the Variables Reference dialog box, do one of the following:
• To expand or collapse the listing of nets or pin pairs for a variable, click the +/-
button.
• To select a net or pin pair within the spreadsheet, double-click a specific net or pin
pair.
• To search for a specific variable, in the Find variable field, type a search string, then
click .

3. After you finish, click OK.

Constraint Manager User's Manual, X-ENTP VX.2.8 279

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Net Constraint Definition
Simulated Delay Specification

Simulated Delay Specification

You specify simulated delay rules to constrain the edge rates of individual electrical nets or
constraint classes by time. Unlike the constraints in the Delays and Lengths group of the Nets
spreadsheet page, which you use to define the total delay for a net, simulated delay constraints
control the switching times between signal states.
Specifying Simulated Delay Rules for Nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Signal Edge Rates and Crosstalk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Matching Simulated Delay Rules Among Nets or Constraint Classes . . . . . . . . . . . . . . 281

Specifying Simulated Delay Rules for Nets

If constraining delay through simulation, you can choose to constrain one or more signal-edge
properties with unique or identical minimum and maximum delay values. You can also specify
the maximum acceptable range between these minimums and maximums.
If you are constraining based on range, use Simulated Delay Max Range (without defining
minimum and maximum simulated delay values) to design source-synchronous busses where
the absolute delay is not important, but limiting the skew between bus nets is critical.

The signal states you define with these rules are formally referred to as the edge rates of a
signal, which are these types:

• Rising edge — The amount of time it takes the signal to switch between low and high
signal states (off to on).
• Falling edge — The amount of time it takes the signal to switch between high and low
signal states (on to off).
Procedure
1. With the Nets spreadsheet page active, from the Filters - Groups toolbar dropdown,
click Simulated Delays.

Note
The tool also displays these constraints as part of the All group, but you may find
it easier to work with simulated delay constraints if the Nets spreadsheet page displays
only them.

2. In the row of the net or constraint class for which you want to specify simulated delay
rules, click within the Simulated Delay Edge cell and select the signal edge to constrain.
3. In the Simulated Delay Min and Simulated Delay Max cells, type the target minimum
and maximum delays.

280 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Net Constraint Definition
Signal Edge Rates and Crosstalk

Note
If Simulated Delay Edge is set to Rise:Fall, separate values with a colon (for
example, 20:30). In the example, unique rise and fall values are being used.

Figure 8-17. Unique Rise and Fall Values for Simulated Delay Constraints

4. (Optional) To specify a maximum range between Simulated Delay Min and Simulated
Delay Max, in the Simulated Delay Max Range cell, type a value.
Related Topics
Simulated Delay Edge
Simulated Delay Min
Simulated Delay Max
Simulated Delay Max Range

Signal Edge Rates and Crosstalk

Constraining edge rates is a crucial component of signal integrity. It is directly related to
crosstalk. The speed of transition as a signal switches between its low and high states can cause
a spike in interference energy from the switching net (aggressor) to others net in its vicinity
(victims).
The faster a signal switches, the more interference energy it produces. Although you can space
parallel trace segments to account for strong electromagnetic fields generated by fast edge rates,
slowing down edge rates is the best solution if adding extra trace length is not an option.

Matching Simulated Delay Rules Among Nets or

Constraint Classes
You can match the simulated delay constraints of a net or constraint class to use the same values
for another net or constraint class. If matching simulated delay values between a constraint class
and a net, the mean of the delay range for nets in the constraint class is used as the matching
simulated delay.
If matching simulated delay rules, the electrical net or constraint class to which you are
matching does not need to include defined constraints for Simulated Delay Min, Simulated
Delay Max, or Simulated Delay Max Range. By keeping these constraints undefined, you can

Constraint Manager User's Manual, X-ENTP VX.2.8 281

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Net Constraint Definition
Matching Simulated Delay Rules Among Nets or Constraint Classes

specify edge rate commonality between multiple nets without constraining the common edge
rate to a specific value.

Procedure
1. On the Nets spreadsheet page, in the row of the net, differential pair, pin pair, or
constraint class for which you want to match simulated delay values, in its Simulated
Delay Match To cell, click to select the hierarchical level to which to match.
2. In the Simulated Delay Match cell, click .

3. In the Simulated Delay Match dialog box, click an appropriate hierarchical object, then
click OK.
The Simulated Delay Match cell now displays this design object, and the Simulated
Delay Offset and tolerance (“Tol”) constraints are accessible.
4. (Optional) Specify an offset and/or tolerance.
Examples
Example of Matching Simulated Delay Between Two Nets Without Defining Specific Delay
Values
In this example, you want to match both the rising and falling edges of two electrical nets, but
you are not interested in specifying appropriate minimum and maximum delay values, or the
maximum range between these values. Your concern is that the signal edges of these nets match
within a certain tolerance. The specific delay values are not of concern.

Use these steps:

1. On the Nets spreadsheet page, in the row of the electrical net you want the other net to
match, click within the Simulated Delay Edge cell, then click Both.
2. Make sure that the Simulated Delay Min, Max, and Max Range cells are empty.
3. In the row of the electrical net you want to match to another net, in the Simulated Delay
Match To cell, click to select Net.
4. In the Simulated Delay Match cell, click .

5. In the Simulated Delay Match dialog box, click the electrical net you used in step 1, then
click OK.
6. In the Simulated Delay tolerance (“Tol”) cell that is now accessible, type a tolerance.
In the example illustration, electrical nets ADDRESS1 and ADDRESS2 are matched.
ADDRESS2 includes a tolerance of +/-10.

282 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Net Constraint Definition
Defining Overshoot and Ringback Constraints

Figure 8-18. Simulated Delay Matching Between Two Electrical Nets

Related Topics
Simulated Delay Match
Simulated Delay Match To
Simulated Delay Offset
Simulated Delay Tol

Defining Overshoot and Ringback Constraints

You can define overshoot and ringback constraints to specify voltage requirements that
maintain component operability and signal integrity. Static and dynamic overshoot are two
distinct types of overshoot that are often times confused with each other.
Static overshoot is unidimensional. The high and low values you use maintain component
operability for an infinite duration. Dynamic overshoot is bidimensional. Each extended high or
low value is accompanied by a precise duration. Specification of this duration is what makes
dynamic overshoot possible. Although these durations are usually extremely short, sometimes
they are the key to solving design problems.

The four overshoot constraints define the high point, low point, extreme high point, and extreme
low point voltage thresholds that the specific logic components (for example, microprocessors)
of a net can handle. Unlike logic thresholds, which dictate the voltage levels needed to switch a
component between logic states, voltage thresholds are maximums and minimums that must be
adhered to in order to maintain operability. Because of the small size and delicate nature of
electronic components, too little or too much voltage can cause irreversible damage, rendering
them useless.

In the illustration, you can see that logic thresholds are between the overshoot thresholds, with
dynamic thresholds encapsulating both logic and static thresholds.

Constraint Manager User's Manual, X-ENTP VX.2.8 283

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Net Constraint Definition
Defining Overshoot and Ringback Constraints

Figure 8-19. Static and Dynamic Overshoot in Relation to Logic Thresholds

Ringback constraints, which are not depicted in the illustration, give you the ability to define the
amount of ringback voltage a net can sustain while in its logic high or logic low state. Too much
ringback, also called feedback, can cause a component to haphazardly switch between logic
states. This is why it is important to define the maximum acceptable amount of ringback energy
individually for each logic state.

Note
Overshoot constraints must be rail-relative (rr) where rr = VLmin – abs for low and rr = abs
– VHmax for high.

Procedure
1. With the Nets spreadsheet page active, in the Filters - Groups toolbar dropdown, click
Overshoot/Ringback.

Note
The tool also displays these constraints as part of the All group, but you may find
it easier to work with simulated delay constraints if the Nets spreadsheet page displays
only them.

2. Navigate to the row of the net or constraint class for which you want to specify
overshoot and ringback constraints.
3. In the Static Low Overshoot Max and Static High Overshoot Max cells, type minimum
and maximum operating voltages.
4. (Optional) In the Dynamic Low Overshoot Max and Dynamic High Overshoot Max
cells, type a lower minimum and higher maximum operating voltage (from the static
values you provided in the previous step), followed by a : character and the duration of
time each voltage can be sustained before Constraint Manager should report an error.
For example, to define a Dynamic High Overshoot Max constraint of 6 volts for 3
nanoseconds, type 6:3.
5. In the Ringback High Min and Ringback Low Min cells, type the maximum amount of
ringback voltage that is acceptable for high and low signal states.
6. In the Non-Monotonic Edge cell, use the dropdown to specify whether transitions
between signal states must be non-monotonic for the rising edge, falling edge, or both
edges.

284 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Net Constraint Definition
Defining Overshoot and Ringback Constraints

7. In the example, ringback values have been defined, and both the rising and falling edges
must be non-monotonic.
Figure 8-20. Ringback Constraint Values

Examples
Example of Defining Dynamic Overshoot Constraints With a 5 ns Limit
In this example, you have already assigned static overshoot constraints to a net. Static Low
Overshoot Max is set to 0.5, and Static High Overshoot Max is set to 5. Now, you want to
define the net's dynamic overshoot constraints and apply a duration of 5 nanoseconds to both
Dynamic Low Overshoot Max and Dynamic High Overshoot Max. The 5 ns value means that
Constraint Manager will not report an error as long as the overshoot value is not met or
exceeded for a continuous time-period greater than 5 ns. The dynamic overshoot constraints you
will define here are 1 and 5.5.

Use these steps:

1. In the Dynamic Low Overshoot Max cell, type 1:5, then press Enter.
2. In the Dynamic High Overshoot Max cell, type 5.5:5, then press Enter.
The net now has a fully-defined set of static and dynamic overshoot constraints. In the
illustration, you can see that both dynamic overshoot constraints are applicable for a
duration of no more than 5 ns.
Figure 8-21. Dynamic Overshoots With a 5 ns Duration Limit

Related Topics
Static Low Overshoot Max
Static High Overshoot Max
Dynamic Low Overshoot Max
Dynamic High Overshoot Max

Constraint Manager User's Manual, X-ENTP VX.2.8 285

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Net Constraint Definition
Defining Overshoot and Ringback Constraints

Ringback Margin Low Min

Ringback Margin High Min
Non-Monotonic Edge

286 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Net Constraint Definition
Power-Supply Net and Constraint Definition

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 287 for a full list of net names).

Example 8-4. 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 . . . 287

Specifying Power-Supply Nets Automatically. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Specifying Power-Supply Nets Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Defining Constraints for Power-Supply Nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Changing Power-Supply Nets Back Into Nets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292

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

Constraint Manager User's Manual, X-ENTP VX.2.8 287

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Net Constraint Definition
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.

Specifying Power-Supply Nets Automatically

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.

288 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Net Constraint Definition
Specifying Power-Supply Nets Automatically

Figure 8-22. 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 8-23. Finding Additional Power Nets

Constraint Manager User's Manual, X-ENTP VX.2.8 289

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Net Constraint Definition
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.

Video
Watch the video to learn how to:

• Select the Power Net constraint.

• Define the Supply Voltage constraint.

290 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Net Constraint Definition
Defining Constraints for Power-Supply Nets

• View the total set of power and ground nets in a certain net class.

Procedure
1. Select the Nets spreadsheet page.
2. Do any of the following:
• 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.
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.

Constraint Manager User's Manual, X-ENTP VX.2.8 291

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Net Constraint Definition
Changing Power-Supply Nets Back Into Nets

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 461.
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 526
• “Power Net Constraints Max Voltage Drop” on page 527
• “Power Net Constraints Max Current Density” on page 528
• “Power Net Constraints Max Via Current” on page 529
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

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
1. Select the Nets spreadsheet page.
2. Do any of the following:
• 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.

292 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Net Constraint Definition
Modifying Xpedition I/O Designer FPGA Constraints

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

Modifying Xpedition I/O Designer FPGA

Constraints
You can modify Xpedition I/O Designer field-programmable gate array (FPGA) constraints to
define technology standards. Because FPGA constraints are synchronized between front-end
Constraint Manager and Xpedition I/O Designer, modifications in either tool result in an update
across your schematic-capture design flow.
If you want to update these constraints across your entire design flow, you can do so with
standard forward-annotation processes. For more information about these constraints, refer to
these constraint reference topics:

• “I/O Standard” on page 525

Procedure
1. With the Nets spreadsheet page active, in the Filters - Groups toolbar dropdown, click
I/O.

Note
Because most Xpedition I/O Designer constraints are defined by pin or pin pairs,
make sure that Filters > Levels > Pins and Pin Pairs are enabled.

2. In the row of the net, constraint class, pin, or pin pair for which you want to modify an
Xpedition I/O Designer constraint, select or type a value.
In the example, the I/O Standard constraint has been set to SMBUS for net OUTPUT1.
Figure 8-24. I/O Standard Constraint Definition

Constraint Manager User's Manual, X-ENTP VX.2.8 293

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Net Constraint Definition
Defining Constraints for Single-Pin Nets

Defining Constraints for Single-Pin Nets

You can define a subset of constraint values for single-pin nets, which are referred to as “Net0”
nets. The constraints you can define are located on the Nets spreadsheet page. Constraint cells
that you cannot define are unavailable and not editable.
In addition to defining constraint values for Net0 nets, you can also assign this grouping of nets
to a constraint class and net class. Including them in a specific net class gives you the ability to
define clearances.

Within Constraint Manager, all single-pin nets have one entry. Therefore, you define rules for
all Net0 nets as a group. Incidentally, all single-pin nets will be part of the same constraint class
and net class. Whether you have 200 single-pin nets, or just two, the tool refers to them as
“(Net0)-1:X”.

Prerequisites
• To give your layout system the ability to produce single-pin nets, in its Project
Integration dialog box, click to enable the check box: “Assign single pin nets to unused
pins, enabling fanout”

Note
After you enable this check box, you must run forward annotation before the net
“(Net0)-1:X” will be visible in any Constraint Manager sessions, those launched
from your front-end or back-end design system.

• Your design must contain at least one single-pin net.

Procedure
1. On the Nets spreadsheet page, locate the net row: (Net0)-1:X
2. Modify the subset of constraint cells that are available to (Net0)-1:X for definition.
Available constraints are modifiable, and not displayed as blank or read-only.
In the example illustration, the “(Net0)-1:X” row has been enabled. It is part of the (All)
constraint class.
Figure 8-25. Single-Pin Nets Spreadsheet Row

Results
The constraint changes you made to (Net0)-1:X now apply to the entire grouping of single-pin
nets.

294 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Net Constraint Definition
Display Pattern Definition

Display Pattern Definition

Display patterns enable you to make certain nets more recognizable in your host tools by
showing nets using unique combinations of colors and hatching patterns. After you create and
assign display patterns in Constraint Manager, you can modify Display Control settings in the
schematic and layout tools to apply the patterns to the view of nets to which they are assigned.
It is possible to assign a unique display pattern to a net, its net class, and its constraint class. If
you enable the display of patterns for all relevant types in the host tool, the host tool shows one
pattern based on this hierarchy:

1. Net
2. Net class
3. Constraint class
For example, if a net has a pattern definition on the net level that differs from that of the net-
class level, the host tool shows the net-level pattern when the patterns for both types are visible.

Defining Net Display Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

Applying Display Patterns in Host Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

Defining Net Display Patterns

Create net display patterns and then assign them to nets and classes so you can apply the unique
combination of a color and hatching pattern to nets in the schematic or layout tool. You can also
modify, rename, and delete display patterns as needed.
Prerequisites
• You enabled the view of the Display Patterns node in the Navigator.
Procedure
1. Do one of the following:
• In the Navigator, right-click Display Patterns, then click New Display Pattern.
• On the Nets spreadsheet or the Trace & Via Properties spreadsheet, in a Display
Pattern cell, click the dropdown list, then click New.
2. In the New dialog box, choose a color.
3. (Optional) Choose a hatching pattern. The tool enables the availability of options like
Outline and Transparent for most patterns.
4. As you define the display pattern, the “New” preview updates to show how the pattern
appears. When satisfied, click OK.

Constraint Manager User's Manual, X-ENTP VX.2.8 295

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Net Constraint Definition
Applying Display Patterns in Host Tools

Results
The tool adds the pattern to the list of those under the Display Patterns node of the Navigator.
The pattern is now selectable under the Display Pattern cell dropdown list on both the Trace &
Via Properties spreadsheet and the Nets spreadsheet.
Note
After you create a display pattern, you might need to modify, rename, or delete it. To do so,
in the Navigator, under the Display Patterns node, right-click a pattern, then choose Edit,
Rename, or Delete.

Examples
Deleting a Display Pattern
Use these steps to delete a display pattern named “test_nets”:

1. In the Navigator, expand the Display Patterns node.

2. Right-click the “test_nets” display pattern, then click Delete.
Editing a Display Pattern
Use these steps to modify a display pattern named “critical_nets”:

1. In the Navigator, expand the Display Patterns node.

2. Right-click the “critical_nets” display pattern, then click Edit.
3. In the Edit dialog box, change the display pattern as needed, then click OK.
Related Topics
Display Pattern (Trace and Via Properties)
Display Pattern (Nets)

Applying Display Patterns in Host Tools

After you assign a display pattern to a net, differential pair, net class, or constraint class, you
must configure your host tool to apply them to your design representation. Like many other
display options in your host tool, you use the Display Control add-in to toggle the visibility of
display patterns you created and assigned in Constraint Manager.
Prerequisites
• You created one or more display patterns in Constraint Manager and assigned them to
nets through the Display Pattern constraint on the Trace & Via Properties spreadsheet or
Nets spreadsheet.
• If applying display patterns in the layout tool, you synchronized the constraint set within
that tool.

296 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Net Constraint Definition
Applying Display Patterns in Host Tools

Procedure
1. In your host tool, bring up the Display Control add-in using the View menu in each tool.
2. Use the instructions for your host tool:
• Schematic Capture — In the Display Control add-in, on the Objects tab, under
“Color by Net or Class,” select the “Use colors from Constraint Manager” option
and at least one of its secondary options. (In the figure, all secondary options are
selected.)

• PCB Layout — In the Display Control add-in, on the Graphic tab, under “Color By
Net or Class,” select the “Use Colors from Constraint Manager” option and at least
one “Apply To” option. (In the figure, all “Apply To” options are selected.)

Related Topics
Display Pattern (Trace and Via Properties)
Display Pattern (Nets)

Constraint Manager User's Manual, X-ENTP VX.2.8 297

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Net Constraint Definition
Applying Display Patterns in Host Tools

298 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Chapter 9
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.
Note
If any previously defined differential pairs now include a “push pin” icon next to them, refer
to “Differential Pairs Conversion” on page 88.

Defining Differential Pairs Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299

Defining Differential Pairs Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Assigning Rules to Differential Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
IBIS Model [Diff_Pin] Section Declarations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308

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 46.

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.
Video
Watch the video to learn how to:

• Locate the nets on the schematic.

• Create a net class for the differential pair.

Constraint Manager User's Manual, X-ENTP VX.2.8 299

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Differential Pair Creation and Pair Rule Definition
Defining Differential Pairs Manually

• Create the differential pair.

Procedure
1. Do one of the following:
• 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.
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 9-1. Differential Pair

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. To select multiple rows for simultaneous deletion, use
Ctrl-click and Shift-click.

300 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Differential Pair Creation and Pair Rule Definition
Defining Differential Pairs Automatically

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
Watch the video to learn how to:

• Determine the differential pair naming suffix.

• Search the net list for signals matching the search criteria.
• Select the nets to join into differential pairs.
• Assign a net class to the differential pair signals.

Procedure
1. Do one of the following:
• 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.

Constraint Manager User's Manual, X-ENTP VX.2.8 301

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Differential Pair Creation and Pair Rule Definition
Defining Differential Pairs Automatically

• IBIS Models — Group nets into differential pairs based on differential pin
definitions in available IBIS models.

Note
After selecting this method, click , then proceed to step 5.

• 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.

302 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Differential Pair Creation and Pair Rule Definition
Defining Differential Pairs Automatically

Figure 9-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.

Tip
To select all proposed differential pairs, click . To unselect all differential pairs,
click .

Constraint Manager User's Manual, X-ENTP VX.2.8 303

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Differential Pair Creation and Pair Rule Definition
Assigning Rules to Differential Pairs

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.

Assigning Rules to Differential Pairs

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.
Results
The new rules are assigned to the differential pair nets and are saved when you exit Constraint
Manager.
Updating Routed Differential Pairs with Changed Rules:
If you change the clearance spacing or trace width values in Constraint Manager for a specific
Net Class for routed differential pairs, you can automatically update and rebuild the geometry of
the existing differential pair traces with the new spacing and trace width values. In this case, a

304 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Differential Pair Creation and Pair Rule Definition
Assigning Rules to Differential Pairs

prompt dialog box opens after you exit Constraint Manager (or when you close the Net Classes
and Clearances dialog box if you make the changes there).
• Click "Yes" to automatically rebuild the differential pair traces.
• Click "No" if you do not want to modify the existing differential pair traces. If you do
not update the traces automatically, DRC reports constraint violations because of the
changed values, and you must modify the differential pair routing manually.
This update feature also works during Forward Annotation from the schematic if you change the
clearance spacing or trace width values there. (The prompt dialog box appears during the
Forward Annotation process in Layout.)
The following limitations and warnings apply:
• Fixed or locked traces are not changed.
• Changes are not made if there is an active Sandbox on the board.
• If you decrease the clearance spacing or trace width values, snake tuning patterns are not
flattened. You can still modify the snake patterns as snakes after the update.
• If you increase the clearance spacing or trace width values, snake tuning patterns are
flattened during the update.
• Sawtooth tuning patterns are always flattened during the update.
• Proximity violations may result after the update, depending on the new values.
• First corner rule violations on pad entries may result after the update.
Examples
Example of Defining a Matched Group Tolerance and Pair Tolerance
By defining both a matched group tolerance and differential pair tolerance, you can specify
tolerances for differential pairs at the individual net and pair level. For example, for three
differential pairs consisting of six total nets, you first define a matched group tolerance of 100 th
to give the router the ability to route each of these nets such that the difference between the
longest and shortest net is less than or equal to 100 th.

Because these six nets comprise three differential pairs, you are also concerned about the
difference in length between each pair of nets that makes up a differential pair. To account for
this, you define a pair tolerance of 20 th to ensure that the maximum difference between net
lengths at the differential pair level is no greater than 20 th.

Constraint Manager User's Manual, X-ENTP VX.2.8 305

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Differential Pair Creation and Pair Rule Definition
Assigning Rules to Differential Pairs

Figure 9-3. Differential Pairs With Two Types of Tolerances Defined

To Define a Matched Group Tolerance and Pair Tolerance:

1. On the Nets spreadsheet page, specify a Match and Tol for one net of the intended
matched group.
2. For the nets that will use this matched group tolerance, type the match number you
choose in step 1 into the Match field of each appropriate net row.
In the example, specify the match and tolerance in the spreadsheet row of one of the
nets, and then type the match number into the Match field of the remaining nets.
3. On the Nets spreadsheet page, specify an acceptable Pair Tol for each differential pair
that is comprised of the nets for which you defined a matched group tolerance in step 2.
In the example, you would define a pair tolerance of 20 th for the three differential pairs
that are based upon the nets for which you defined a matched group tolerance.
Example of Matching Physical Nets in a Differential Pair
You can use the Length or TOF Delay Match constraint to create matching relationships among
physical nets that are part of complex electrical nets (^^^) that make up a differential pair. You
can do this for any electrical net that contains multiple physical nets. By doing so, you ensure
that the lengths of physical nets that run parallel are the same, or within a certain tolerance. This
keeps the physical nets from being out of balance between series elements.

306 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Differential Pair Creation and Pair Rule Definition
Assigning Rules to Differential Pairs

Figure 9-4. Differential Pair Matched at the Physical Net Level

In the illustration, $1N111 and $1N110 are the first physical nets in each electrical net. ADDR2
and ADDR3 are the second physical nets in each electrical net. Each of the two match groups
matches each parallel physical net to within 50 th of the other. Although it is not pictured, the
differential pair itself has a defined tolerance for the overall electrical nets through the
Differential Pair Tol constraint.

Note
Matching at the physical net level is just one way to implement greater control over the nets
that comprise a differential pair. When you need to enforce exact lengths, you can define
minimum and maximum values, use formulas, variables, or a combination of various
constraints. You can do this at the physical net level or electrical net level.

Related Topics
Differential Pair Tol Max
Differential Pair Phase Tol Max
Differential Pair Phase Tol Distance Max
Differential Pair Phase Tol Actual
Convergence Tolerance Max
Distance to Convergence Max
Separation Distance Max
Differential Spacing
Differential Impedance Target
Differential Impedance Tolerance

Constraint Manager User's Manual, X-ENTP VX.2.8 307

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Differential Pair Creation and Pair Rule Definition
IBIS Model [Diff_Pin] Section Declarations

IBIS Model [Diff_Pin] Section Declarations

The tool always simulates nets connected to a receiver or bidirectional pin in the [Diff_Pin]
section of an IBIS model as differential pairs. This is true regardless of whether you define the
nets as differential pairs within Constraint Manager. However, the router you use with
Constraint Manager only enables differential pair routing/constraints if you have defined a
pairing in Constraint Manager.

308 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Chapter 10
Parallelism and Crosstalk Rule Creation

This section provides information about creating parallelism rules and crosstalk rules. Although
you can use both in a design, you might decide that one type of rule is more appropriate. Density
and complexity are two factors that can affect whether you need to use one or both types of
rules.

Overview of Parallelism and Crosstalk Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

Defining Parallelism Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Assigning Parallelism Rules to Nets and Constraint Classes. . . . . . . . . . . . . . . . . . . . . . 313
Importing Parallelism Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
ParallelRules.txt File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
Navigating to Assigned Parallelism Rules From the Nets Page. . . . . . . . . . . . . . . . . . . . 321
Defining Crosstalk Rules for Nets and Constraint Classes . . . . . . . . . . . . . . . . . . . . . . . 322

Overview of Parallelism and Crosstalk Rules

Before you define crosstalk rules for nets or constraint classes, or parallelism rules and then
assign them to nets or constraint classes, you should have an understanding of how parallelism
and crosstalk rules differ to determine which rule type you want to use with your design.
Here are definitions for each of these types of rules:

• Crosstalk rules — Give you the ability to specify the maximum amount of acceptable
interference energy (mV) for specific nets and constraint classes. Accordingly, the
hazard system displays violations that it encounters. Each crosstalk rule that you create
consists of two nets or constraint classes. The first object is the victim, and the second
object is the aggressor.
• Parallelism rules — Give you the ability to define pairings of net properties that
specify acceptable distances and parallelism run lengths between specific nets and
constraint classes. If Hazards identifies a distance/length pairing that has been breached,
you can have it resolve such violations through use of the Resolve button for the set of
hazards. For same layer parallelism rules, the router uses these rules to avoid creating
violations when running a Tune Crosstalk pass. The router does not use parallelism rules
for the Route pass or No Via Bias pass.

Constraint Manager User's Manual, X-ENTP VX.2.8 309

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Parallelism and Crosstalk Rule Creation
Defining Parallelism Rules

Note
If both are defined for a net, parallelism rules take precedence over crosstalk values.

Parallelism Rules Hierarchy

If you assign multiple parallelism rules between nets, Constraint Manager uses the rule with the
lowest level of hierarchy. For example, you assign parallelism rule PR1 to Net A and Net B.
These nets are grouped into separate constraint classes. If you assign a different parallelism rule
(for example, PR2) between these two constraint classes, Net A and Net B use the net-to-net
parallelism rule instead of the class-to-class rule.

Constraint Manager obeys parallelism rules between nets and classes based on the following
hierarchy:

1. Net to net
2. Net to (All Nets)
3. Class to class
4. Class to (All Classes)

Parallelism Rule Definition Methodologies

Depending on your design practices, you might define parallelism rules all at once, in groups,
individually, or as a mixture of these methodologies as you work with the nets in a design. Note
the following:

• If defining multiple rules, the method of parallelism rule creation explained in “Defining
Parallelism Rules” on page 55 gives you the ability to quickly define multiple rules,
making it best suited for this purpose.
• If defining or refining individual rules, you can use the Noise Rules spreadsheet page
(refer to “Assigning Parallelism Rules to Nets and Constraint Classes” on page 58).

Defining Parallelism Rules

You can create rules that define parallelism requirements for net segments that are on the same
layer, adjacent layers, or both. To accomplish this, you specify a combination of edge-to-edge
spacing between segments and the maximum length that segments can run in parallel without
violation.
By defining parallelism rules, you can help control the amount of crosstalk by restricting
excessive segment parallelism. You can create as many edge-to-edge and maximum length
combinations as you require. For example, a parallelism rule that contains three edge-to-edge

310 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Parallelism and Crosstalk Rule Creation
Defining Parallelism Rules

and maximum length combinations for net segments on the same layer could specify these
rules:

• Segments with an edge-to-edge spacing of 10 th can run parallel for no more than 100
th.
• Segments with an edge-to-edge spacing of 100 th can run parallel for no more than
1,000 th.
• Segments with an edge-to-edge spacing of 1,000 th can run parallel for no more than
10,000 th.
Figure 10-1. Example Parallelism Rule Definition

The example illustration shows what this looks like in the tool. Because the layout system
interpolates the available parallelism rules to account for undefined Edge / Edge values, you can
define rules as broadly or narrowly as you require.

Note
Interpolation of these rules means that the layout system mathematically determines an
appropriate Max Parallel Len value for an undefined Edge / Edge value that falls between
two defined Edge / Edge values. Using interpolation based on the example rules, an Edge / Edge
value of 50 th produces a Max Parallel Len requirement of 500 th.

Prerequisites
• You should have an understanding of whether to use parallelism or crosstalk rules. For
more information, refer to “Overview of Parallelism and Crosstalk Rules” on page 309.
Video
Watch the video to learn how to:

• Modify the assignment on the Noise Rules page.

Constraint Manager User's Manual, X-ENTP VX.2.8 311

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Parallelism and Crosstalk Rule Creation
Defining Parallelism Rules

• Define pairings of edge spacing values and run lengths.

Procedure
1. Do one of the following:
• On the Pairs toolbar, click .

• From the Edit menu, click Parallelism Rules, then click Define Parallelism Rules.
2. In the Define Parallelism Rules dialog box, next to the Parallelism rules heading, click
, then change the default name of the new rule (“New”) to a meaningful title.

Tip
Instead of creating a new rule, you can use an existing parallelism rule as a clone and
then modify it to meet the needs of the unique rule. To do so, in the list of existing
parallelism rules, click one, then click .

3. Define an edge-to-edge spacing and maximum length combination for each same layer
rule or adjacent layer segment rule you want this parallelism rule set to include by
performing one of these tasks:
• To define a same layer segment rule, next to the Same layer trace segments heading,
click , then type an Edge / Edge value and a Max Parallel Len value.

• To define an adjacent layer segment rule, next to the Adjacent layer trace segments
heading, click , then type an Edge / Edge value and a Max Parallel Len value.

Note
You can define a negative Edge / Edge value (for example, -2) to allow for
segment overlap between adjacent layers.

Tip
You can also create adjacent layer segment rules by cloning existing same layer
segment rules. To do so, next to the Adjacent layer trace segments heading, click
. If cloning, all rules are recreated. You can remove rules you do not need by
clicking a row, then clicking .

312 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Parallelism and Crosstalk Rule Creation
Assigning Parallelism Rules to Nets and Constraint Classes

4. After you finish typing edge-to-edge and maximum parallel length combinations, click
OK.

Note
The maximum length value associated with an edge-to-edge value cannot be greater
than the maximum length value associated with a larger edge-to-edge value. For
example, after you define an edge-to-edge and maximum length combination of 10 th
and 1200 th, an edge-to-edge value of 8 th must be accompanied by a maximum length
value that is less than the maximum length value of the previous set (that is, 1200 th). If
you type incorrect values, the tool changes the cell background to red and it does not
save the data in the cell until you correct the value.

Examples
The following parallelism rule allows for trace segment overlap between adjacent layers
through the definition of a negative Edge / Edge value. Segments overlapping by more than 2 th
can run in parallel for no more than 20 th.

Assigning Parallelism Rules to Nets and

Constraint Classes
After you define parallelism rules, you can apply them to specific pairs of nets and constraint
classes by creating net-to-net or class-to-class parallelism rule assignments. Each parallelism
rule assignment includes two specific nets or constraint classes and the parallelism rule to which
they must adhere.
In addition, you can apply all parallelism rules that you have created to the nets or constraint
classes that comprise a parallelism rule assignment. In the example illustration, the noise rule
Bus1 assigns parallelism rule PR1 between all nets in the Memory constraint class.

Constraint Manager User's Manual, X-ENTP VX.2.8 313

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Parallelism and Crosstalk Rule Creation
Assigning Parallelism Rules to Nets and Constraint Classes

Figure 10-2. Parallelism Rule Assignment

Video
Watch the video to learn how to:

• Enable the Noise Rules page.

• Assign a parallelism rule between two constraint classes.
• Modify the assignment on the Noise Rules page.

Procedure
1. Do one of the following:
• On the Pairs toolbar, click .

• From the Edit menu, click Parallelism Rules, then click Assign Parallelism Rules.

Tip
On the Noise Rules spreadsheet page, right-click, then click New. Modify the Noise
Type, Constraint Class or Electrical Net Name Victim and Aggressor, and
Parallelism Rule fields using the appropriate field selector. For example, because Class-
Class is the default parallelism type, if assigning a net-to-net parallelism rule, click to
change this field to Net-Net. When assigning parallelism rules using the Assign
Parallelism Rules dialog box, you can access it from the Edit menu by clicking
Parallelism Rules, then clicking Assign Parallelism Rules.

2. In the Assign Parallelism Rules dialog box, in the Noise rule type field, specify a net-to-
net or class-to-class assignment.
3. In the list of available electrical nets or constraint classes, select the nets or constraint
classes that will comprise the first half of the pairing (that is, reference nets or classes),
then next to the Victim constraint class(es) or Victim electrical net(s) box, click .

314 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Parallelism and Crosstalk Rule Creation
Assigning Parallelism Rules to Nets and Constraint Classes

Tip
To select multiple nets or constraint classes, use Ctrl-click, Shift-click, or click-drag.
To select nets or constraint classes by name, in the field below the list of source nets
or net classes, type a search string, then click .

4. In the list of nets or constraint classes, select the nets or constraint classes that will
comprise the second half of the pairing (that is, apply rules to nets or constraint classes),
then next to the Aggressor constraint class(es) or Aggressor electrical net(s) box, click .

Note
If assigning a parallelism rule to constraint classes, you can select all constraint
classes by using the (All Classes) selection. The selection (All) refers to the default
constraint class (All).

For example, to check for same net or same constraint class parallelism, select the nets
or constraint classes you chose in step 3.
5. In the Parallelism rule box, select a specific parallelism rule. To view detailed
information about each of the available rules, click . You can also create a parallelism
rule in the resulting dialog box.
6. (Optional) Define a maximum crosstalk value for these pairings of electrical nets or
constraint classes. To do so, in the Max crosstalk box, type the maximum amount of
crosstalk that the victim nets or constraint classes can receive from the aggressor nets or
constraint classes.
7. Make sure the lists of nets or constraint classes is accurate. To remove items from either
list, click to select them, then click the corresponding .

8. Click Apply or OK.

Examples
Example of Assigning a Parallelism Rule Between a Single Constraint Class and All Other
Constraint Classes
In this example, you want to assign a parallelism rule between nets in a single constraint class
with nets in all other constraint classes. The parallelism rule includes same-layer, adjacent-
layer, segment, edge-to-edge, and maximum parallelism rule lengths. The nets in the single
constraint class are critical nets with strict parallelism requirements.

1. In the Assign Parallelism Rules dialog box, in the Noise rule type field, make sure Class
to Class is selected.
2. In the list of Available constraint class(es), select the single constraint class to associate
with all other constraint classes, then next to the Victim constraint class(es) list, click .

3. In the list of Available constraint class(es), select the (All Classes) row, then next to the
Aggressor constraint class(es) list, click .

Constraint Manager User's Manual, X-ENTP VX.2.8 315

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Parallelism and Crosstalk Rule Creation
Importing Parallelism Rules

4. In the Parallelism rule field, click the dropdown, select the parallelism rule to assign
between the single constraint class and all other constraint classes, then click OK.
In the illustration, the Noise Rules spreadsheet shows that parallelism rule G10L100/
G15L150 is assigned between constraint class HT_CONN_IN and all other constraint
classes.
Figure 10-3. Single Constraint Class and All Other Constraint Classes
Parallelism Rule Assignment

Related Topics
Navigating to Assigned Parallelism Rules From the Nets Page
Noise Rules

Importing Parallelism Rules

You can populate Constraint Manager with parallelism rule definitions and assignments through
an import process. This is in addition to creating and assigning them manually from directly
within the tool.
Procedure
1. Determine the snapshot and top block name by choosing Output > Design Statistics.
The report shows this information at the top.
2. Run the sandboxfile command with the appropriate arguments.
Results
The tool updates the Noise Rules spreadsheet page to show the new rules and assignments.
Because you cannot define names for noise rules and parallelism rules in the ParallelRules.txt
file, the tool names noise rules as PR_# and parallelism rules as PRD_# (for example, PR_1,
PR_2, PRD_1, and PRD_2).
Note
The tool creates a unique parallelism rule for every net pairing or class pairing, except in the
case where a SAMELAYER definition and an ADJACENYLATER definition contain the
same object and clearance values.

Examples
The tool creates five rows after the user imports rules into a design that did not include any
rules.

316 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Parallelism and Crosstalk Rule Creation
Importing Parallelism Rules

Figure 10-4. Imported Rules and Assignments

Related Topics
sandboxfile

Constraint Manager User's Manual, X-ENTP VX.2.8 317

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Parallelism and Crosstalk Rule Creation
ParallelRules.txt File Format

ParallelRules.txt File Format

Input for: Constraint Manager parallelism rules
Use a ParallelRules.txt file to both define these rules and assign them between nets or net
classes. After you import the file, the tool populates the Noise Rules spreadsheet page with
rows for each new assignment.
Format
.FILETYPE PARALLELISM_RULES
.UNITS <unit>
.MODE <type>

.NET2NET_RULES <layer_relationship>
..CLEARANCE_LENGTH <edge> <max_parallel_len>
...NETCLASS_NETCLASS "<class_one>" "<class_two>"
...NET_NET "<net_one>" "<net_two>"

Note
You can use .CLASS2CLASS_RULES instead of .NET2NET_RULES because the tool
interprets them as the same.

Parameters
• .UNITS <unit>
A required keyword at the top of the file specifying the units of the file. Valid values for
units: thousandths (TH), microns (UM), millimeters (MM), and inches (IN).
• .MODE <type>
An optional keyword you use to change the parallelism mode for a design. Valid values are
CUMULATIVE and NONCUMULATIVE. You can also change this mode in the Settings
dialog box under Design Configuration.
• .NET2NET_RULES <layer_relationship>
A required keyword that defines a class-class rule as SAMELAYER or
ADJACENTLAYER.
• ..CLEARANCE_LENGTH <edge> <max_parallel_len>
A required pair of keywords that defines Edge / Edge and Max Parallel Len. You can
provide this line multiple times per rule.
• ...NETCLASS_NETCLASS "<class_one>" "<class_two>"
A required pair of keywords that defines the names of the two net classes for rule
assignment. You can provide this line multiple times per rule.
• ...NET_NET "<net_one>" "<net_two>"
A required pair of keywords that defines the names of the two nets for rule assignment. You
can provide this line multiple times per rule.

318 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Parallelism and Crosstalk Rule Creation
ParallelRules.txt File Format

Note
For backward compatibility, the tool treats “(ALL)” and “(All)” differently. It interprets
“(ALL)” as (All Classes) or (All Nets). It interprets “(All)” as the constraint class (All).

Examples
The following example shows five definitions. The first three include both SAMELAYER and
ADJACENTLAYER sections. The final two definitions include one of each. Although each
definition in the example assigns rules between pairs of net classes and pairs of nets, the tool
does not require you to include both types of assignments in a single definition.

Constraint Manager User's Manual, X-ENTP VX.2.8 319

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Parallelism and Crosstalk Rule Creation
ParallelRules.txt File Format

.FILETYPE PARALLELISM_RULES
.UNITS MM
.MODE NONCUMULATIVE

'first definition
.NET2NET_RULES SAMELAYER
..CLEARANCE_LENGTH 6 7
..CLEARANCE_LENGTH 4 5
..CLEARANCE_LENGTH 2 3
..CLEARANCE_LENGTH 1 2
...NET_NET "(All Nets)" "(All Nets)"
...NET_NET "A" "B"
...NET_NET "C" "D"
...NET_NET "E" "F"
...NETCLASS_NETCLASS "(All Classes)" "(All Classes)"
...NETCLASS_NETCLASS "CLASSA" "CLASSB"
...NETCLASS_NETCLASS "CLASSA" "CLASSB/CLASSC"
...NETCLASS_NETCLASS "CLASSA/CLASSC" "CLASSB/CLASSC"

.NET2NET_RULES ADJACENTLAYER
..CLEARANCE_LENGTH 6 7
..CLEARANCE_LENGTH 4 5
..CLEARANCE_LENGTH 2 3
..CLEARANCE_LENGTH 1 2
...NET_NET "(All Nets)" "(All Nets)"
...NET_NET "A" "B"
...NET_NET "C" "D"
...NET_NET "E" "F"
...NETCLASS_NETCLASS "(All Classes)" "(All Classes)"
...NETCLASS_NETCLASS "CLASSA" "CLASSB"
...NETCLASS_NETCLASS "CLASSA" "CLASSB/CLASSC"
...NETCLASS_NETCLASS "CLASSA/CLASSC" "CLASSB/CLASSC"

'second definition
.NET2NET_RULES SAMELAYER
..CLEARANCE_LENGTH 60 70
..CLEARANCE_LENGTH 40 50
..CLEARANCE_LENGTH 20 30
..CLEARANCE_LENGTH 10 20
...NET_NET "G" "H"
...NET_NET "I" "J"
...NETCLASS_NETCLASS "CLASSG" "CLASSH"
...NETCLASS_NETCLASS "CLASSI" "CLASSJ"

.NET2NET_RULES ADJACENTLAYER
..CLEARANCE_LENGTH 60 70
..CLEARANCE_LENGTH 40 50
..CLEARANCE_LENGTH 20 30
..CLEARANCE_LENGTH 10 20
...NET_NET "G" "H"
...NET_NET "I" "J"
...NETCLASS_NETCLASS "CLASSG" "CLASSH"
...NETCLASS_NETCLASS "CLASSI" "CLASSJ"

'third definition
.NET2NET_RULES SAMELAYER
..CLEARANCE_LENGTH 61 71
..CLEARANCE_LENGTH 41 51

320 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Parallelism and Crosstalk Rule Creation
Navigating to Assigned Parallelism Rules From the Nets Page

..CLEARANCE_LENGTH 21 31
..CLEARANCE_LENGTH 11 21
...NET_NET "K" "L"
...NETCLASS_NETCLASS "CLASSK" "CLASSL"

.NET2NET_RULES ADJACENTLAYER
..CLEARANCE_LENGTH 61 71
..CLEARANCE_LENGTH 41 51
..CLEARANCE_LENGTH 21 31
..CLEARANCE_LENGTH 11 21
...NET_NET "K" "L"
...NETCLASS_NETCLASS "CLASSK" "CLASSL"

'4th definition
.NET2NET_RULES SAMELAYER
..CLEARANCE_LENGTH 62 72
..CLEARANCE_LENGTH 42 52
..CLEARANCE_LENGTH 22 32
..CLEARANCE_LENGTH 12 22
...NET_NET "M" "N"
...NETCLASS_NETCLASS "CLASSM" "CLASSN"

'5th definition
.NET2NET_RULES ADJACENTLAYER
..CLEARANCE_LENGTH 63 73
..CLEARANCE_LENGTH 43 53
..CLEARANCE_LENGTH 23 33
..CLEARANCE_LENGTH 13 23
...NET_NET "O" "P"
...NETCLASS_NETCLASS "CLASSO" "CLASSP"

Related Topics
sandboxfile

Navigating to Assigned Parallelism Rules

From the Nets Page
As you work with the Nets spreadsheet page to define constraints for individual nets and
constraint classes, you can quickly navigate to the parallelism rules assigned to a net or
constraint class. By doing so, you can easily and accurately determine any parallelism-rule
assignments for a design object.
Procedure
On the Nets spreadsheet page, right-click a net or constraint class, then click Navigate to
Parallelism Rule.

Results
If one or more assignments exist, the tool makes the Noise Rules page active and highlights any
parallelism rules assigned to the design object.

Constraint Manager User's Manual, X-ENTP VX.2.8 321

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Parallelism and Crosstalk Rule Creation
Defining Crosstalk Rules for Nets and Constraint Classes

Defining Crosstalk Rules for Nets and

Constraint Classes
You can define crosstalk rules for pairs of nets and constraint classes to specify the maximum
crosstalk value for these pairs as part of an aggressor-victim relationship. These values define
the maximum acceptable amount of crosstalk a victim net can receive from an aggressor net.
If you define a maximum crosstalk value, you can also specify the victim net's signal state (for
example, Low or High) that is most susceptible to crosstalk. Because crosstalk presents unique
challenges based upon signal state, you can define multiple crosstalk rules to specify constraints
for aggressor-victim net and constraint class pairs. For example, if Net B is in a low state, you
can restrict the maximum crosstalk from Net A to 10 mV. However, if Net B is in a high state,
you can require that the maximum crosstalk from Net A is no more than 5 mV.

Prerequisites
• You should have an understanding of whether to use parallelism and crosstalk rules. For
more information, refer to “Overview of Parallelism and Crosstalk Rules” on page 309.
Procedure
1. With the Noise Rules spreadsheet page active, right-click within the spreadsheet, then
click New Rule.
2. In the Noise Type cell, click to specify whether the aggressor-victim relationship is Net-
to-Net or Class-to-Class (constraint class).
3. In the Constraint Class Or Electrical Net Name Victim field, click the browse button,
select the victim net or constraint class, then click OK.
4. In the Constraint Class or Electrical Net Name Aggressor field, click the browse button,
select the aggressor net or constraint class, then click OK.
5. In the Crosstalk Max cell, type the maximum amount of crosstalk the victim net or
constraint class can receive from the aggressor.
6. (Optional) In the Crosstalk Level cell, click to select the signal state or states of the
victim net or constraint class using these guidelines:
• High — The victim net is on (in its high state). The voltage level is at or above the
high threshold (for example, 5.1 V).
• Low — The victim net is off (in its low state). The voltage level is at or below the
low threshold (for example, 0.9 V).
• Tristate — The victim net is off, but a small voltage still flows from the receiver to
ground (for example, 0.5 V).

322 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Parallelism and Crosstalk Rule Creation
Defining Crosstalk Rules for Nets and Constraint Classes

Results
The Crosstalk Max value is now the constraint for a specific net-to-net relationship, or for all
victim nets in a constraint class if receiving crosstalk from the aggressor nets in another
constraint class.
Examples
Example of Defining Two Nets as Both Aggressors and Victims
In this example, you want to define two net-to-net crosstalk relationships to specify how Net A
and Net B should be constrained if each net is an aggressor or victim of the other. In this case, if
Net A is the aggressor of victim Net B, the maximum crosstalk value Net B can receive from
Net A is 5 mV. Conversely, if Net B is the aggressor of victim Net A, the maximum crosstalk
value Net A can receive from Net B is 10 mV. In addition, both victim nets must meet this
constraint during all signal states.

1. On the Noise Rules spreadsheet page, click , then in the Noise Type cell, click Net-to-
Net.
2. In the Constraint Class Or Electrical Net Name Victim field, click the browse button,
select Net A, then click OK.
3. In the Constraint Class or Electrical Net Name Aggressor field, click the browse button,
select Net B, then click OK.
4. In the Crosstalk Max cell, type 10. In the Level cell, click to select All.
5. Repeat steps 1 through 4, and this time specify Net B as the victim net, Net A as the
aggressor net, and a Crosstalk Max value of 5.
In the example illustration, net $1N2 can be susceptible to 10 mV of crosstalk from net
$1N5. Conversely, if the aggressor-victim role is reversed, net $1N5 can receive no
more than 5 mV of crosstalk from net $1N2.
Figure 10-5. Two Nets Defined As Both Aggressor and Victim Nets

Related Topics
Noise Type
Constraint Class or Electrical Net Name Victim

Constraint Manager User's Manual, X-ENTP VX.2.8 323

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Parallelism and Crosstalk Rule Creation
Defining Crosstalk Rules for Nets and Constraint Classes

Constraint Class or Electrical Net Name Aggressor

Crosstalk Max
Crosstalk Level

324 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Chapter 11
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 and also externally in other designs.
Because constraint templates capture all constraints defined for a specific net, constraint
templates are an extremely powerful and efficient way to reuse constraint specifications. At any
time during or after the design creation process, you can export constraint templates to a
common location. In doing so, you can build a library of proven design constraints to streamline
the design creation process for future designs that contain many of the same connection
requirements between parts.

Tip
If developing a library of constraint templates, consider making it accessible to all designers
within your group as appropriate. By doing so, you can leverage common constraint values
and promote consistency.

Creating Constraint Templates to Capture Net Constraints. . . . . . . . . . . . . . . . . . . . . . 325

Constraints and Values Stored With Each Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Constraint Template Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Updating Nets With Constraint Template Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
Reusing Constraint Templates in External Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

Creating Constraint Templates to Capture Net

Constraints
Create constraint templates to capture net constraints for reuse on similar nets within your
current design and external designs. Creating a constraint template for a single bus net is a
common application that could promote both design-internal and external constraint template
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. By exporting this constraint
template, you can then import it into designs that have a common bus structure, and reuse the
constraint template to duplicate characteristics that promote signal integrity for similar nets.

Constraint Manager User's Manual, X-ENTP VX.2.8 325

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Template Creation and Reuse
Creating Constraint Templates to Capture Net Constraints

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.

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 558.
• 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.

326 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Template Creation and Reuse
Constraints and Values Stored With Each Template

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 558 for a description of each template cell.

Constraint Manager User's Manual, X-ENTP VX.2.8 327

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Template Creation and Reuse
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

Applying a Constraint Template to Multiple Nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Applying Constraint Templates From the Constraint Templates Page . . . . . . . . . . . . . 330
Applying a Constraint Template to a Single Net . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Device Pattern Matching With Constraint Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Modifying Pin Matching for an Applied Constraint Template . . . . . . . . . . . . . . . . . . . . 332

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.

328 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Template Creation and Reuse
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 330.

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 .

Constraint Manager User's Manual, X-ENTP VX.2.8 329

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Template Creation and Reuse
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 tested and 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 332.

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).
2. Do one of the following:
• 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
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 332.

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.

330 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Template Creation and Reuse
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
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 332.

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*.

Constraint Manager User's Manual, X-ENTP VX.2.8 331

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Template Creation and Reuse
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.

332 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Template Creation and Reuse
Updating Nets With Constraint Template Changes

Figure 11-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,

Constraint Manager User's Manual, X-ENTP VX.2.8 333

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Template Creation and Reuse
Reusing Constraint Templates in External Designs

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 11-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.

Reusing Constraint Templates in External

Designs
After you create one or more constraint templates, you can reuse them by exporting them to a
file, and then importing that file into other designs. Each .cts file (encrypted XML format) you
export includes all constraint template definitions associated with a constraint set.
For example, after defining the physical, electrical, and signal integrity constraints for a net that
serves as the critical connection between two common components for a product line, you can
make the constraint template available for reuse by storing it in a common or collaborative
network directory. You and the other designers in your group gain the ability to reuse the
constraint template in similar designs by applying it to specific nets that benefit from the
constraint set.

Procedure
1. Export Constraint Manager constraint templates (File > Export > Constraint
Templates) to a .cts file.

Note
To export a single template, on the Constraint Templates page, right-click the
template row, then click Export Selection.

2. Launch Constraint Manager on the design for which you want to reuse these constraint
templates.
3. From the File menu, click Import, then click Constraint Templates.

334 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Template Creation and Reuse
Reusing Constraint Templates in External Designs

4. In the Import Constraint Template dialog box, select a file of the type you want to
import (based on these guidelines), then click Open:
• .cts files — Constraint templates you exported from Constraint Manager.
• .ctm files — Constraint templates you saved from within CTE, the constraint
template editor.
Results
You can now apply the imported constraint templates to nets as needed.
Related Topics
Constraint Template Application
Exporting Constraints in Encrypted ASCII Format
Import of Constraints

Constraint Manager User's Manual, X-ENTP VX.2.8 335

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Template Creation and Reuse
Reusing Constraint Templates in External Designs

336 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Chapter 12
Constraint Export and Import

This section covers the export and import of constraints, which give you the ability to reuse and
modify constraint information. It includes several topics, each of which provides procedures
you use to accomplish these tasks.

Export of Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338

Import of Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343

Constraint Manager User's Manual, X-ENTP VX.2.8 337

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Export and Import
Export of Constraints

Export of Constraints
You can export constraint values for one or more purposes.
Export constraints to capture constraints to a data file for the purpose of importing them into
Constraint Manager at a later time or decrypting and viewing the constraint data in an external
program. You can export constraints in the proprietary encrypted XML format (.cts), CSV
format (.csv), and proprietary encrypted ASCII format (.cs_).

Constraint Export in Encrypted XML Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339

Exporting Constraints in CSV Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
Exporting Constraints in Encrypted ASCII Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Decrypting and Encrypting Exported Constraint Data . . . . . . . . . . . . . . . . . . . . . . . . . . 342

338 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Export and Import
Constraint Export in Encrypted XML Format

Constraint Export in Encrypted XML Format

You can export constraints in encrypted XML format (.cts) for the purpose of later importing
the constraint set that you chose to export. Because you cannot decrypt this format, you would
use this method if you do not need to edit the data, but simply want to import it into the same
design or another design.
Typically, you would export data in this format for the purpose of creating constraint backups or
making constraint templates available for reuse. Depending on the amount of data you want to
capture, one of the two tasks is more appropriate for your purpose.

Note
You can also export constraints into proprietary encrypted XML format (.cts) using a
command-line tool. For more information, refer to “cons2xml” on page 569.

Choosing From the Entire Set of Constraint Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339

Exporting Only Selected Nets or Spreadsheet Rows . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340

Choosing From the Entire Set of Constraint Data

If exporting in encrypted XML format, you can start with the entire constraint set and then
reduce the total amount of constraint data. Do this if it is faster to exclude certain data rather
than manually select a data set.
Procedure
1. From the File menu, click Export, then choose Constraints.
2. In the Export Constraints dialog box, specify the following:
• A data scope of all data or just specific pages. To select the pages to export, click to
activate the Selected pages radio button, then click to highlight one or more
spreadsheet pages.

Note
If exporting just specific pages, the tool does not include referenced objects
between the Nets page and the Constraint Templates page unless you select both
pages or select the Include referenced objects check box.

• Whether you want to include the following:

o Default constraints — Standard constraints provided with the tool.
o User constraints — Non-standard constraints added to the tool by users.
o Objects hierarchy — Categorization of objects into classes and hierarchy.

Constraint Manager User's Manual, X-ENTP VX.2.8 339

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Export and Import
Exporting Constraints in CSV Format

o Attributes (comments) — Constraint mark-ups provided as comments against

specific cells.
o Referenced objects — For constraint values that reference objects like constraint
templates, the available data set for the referenced object.
• (Optional) In the Description field, modify the textual description for the exported
data set. To do so, click to activate the Edit description check box, then modify the
description.
3. Verify your selections, then click Export.
4. Specify a filename and location for the constraint data file you want to export, then click
Save.

Exporting Only Selected Nets or Spreadsheet Rows

You can select just the nets and spreadsheet rows you want to export. Do this if it is faster to
manually select a data set rather than exclude specific items.
Procedure
1. On the spreadsheet, use click or Ctrl-click to select the row or rows you want to export.
2. After you finish making your selections, right-click, then click Export Selection.
3. In the Export Selected Constraints dialog box, specify these options:
• Whether you want to include Default constraints (standard, out of the box
constraints), User constraints (non-standard, user-added constraints), Objects
hierarchy, and Attributes (comments).
• If applicable, referenced objects between the Nets page and the Constraint
Templates page.
• (Optional) In the Description field, modify the textual description for the exported
data set. To do so, click to activate the Edit description check box, then modify the
description.
4. Verify your selections, then click Export:
5. Specify a filename and location for the constraint data file you want to export, then click
Save.

Exporting Constraints in CSV Format

You can export constraints in CSV format (.csv) for the purpose of producing constraint data
files that are similar to the encrypted ASCII format, but simplified with regard to the reading
and sorting of data.

340 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Export and Import
Exporting Constraints in Encrypted ASCII Format

The CSV format is more explicit and easier for external programs to read and write. It is
important to note that over time the encrypted ASCII format will become obsolete. CSV is the
recommended format.

Tip
You can also export constraints in the CSV format using a command-line tool. For more
information, refer to “cons2csv” on page 566.

Prerequisites
• CES Diagnostics must report no issues in order for export to run.
Procedure
1. From the File menu, choose Export > Constraints to CSV.
2. In the Export Constraints to CSV dialog box, specify a filename and location for the
constraint data file you want to export, then click Save.
Results
• The .csv file always contains actuals if they are available in the Constraint Manager
session from which you export constraints. The tool never exports actuals if you use the
command-line utility (cons2csv).
• After the export finishes processing, a log file for the export is written to the following
location:
<design_folder>\CES\LogFiles\<snapshot_name>\<block_name>\<machine_name>\
<user_name>\csv_export_<date_time>.log
For example, C:\Tablet_design_1\CES\LogFiles\DxD\screen\psmith-lt\psmith\
csv_export_20121016_114536.log
In the event that the log file contains errors or warning, and is not clean, the File Viewer
automatically displays it for you to review.
Related Topics
Decrypting and Encrypting Exported Constraint Data
Importing Constraints in CSV Format

Exporting Constraints in Encrypted ASCII Format

You can export constraints in encrypted ASCII format (.cs_) for the purpose of producing
constraint data files that you can then decrypt and view in an external application. You cannot
re-import the encrypted ASCII format.

Constraint Manager User's Manual, X-ENTP VX.2.8 341

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Export and Import
Decrypting and Encrypting Exported Constraint Data

Note
You can also export constraints into the encrypted ASCII format (.cs_) using a command-
line tool. For more information, refer to “cons2ascii” on page 565.

Procedure
1. From the File menu, click Export, then click Constraints to encrypted ASCII.
2. In the Export Constraints to ASCII dialog box, specify a filename and location for the
constraint data files you want to export, then click Save.
Results
The tool produces a set of separate encrypted ASCII files: one for each spreadsheet page and
one for the board stackup. Now that you have exported the file set, you can decrypt it as needed.
Related Topics
Decrypting and Encrypting Exported Constraint Data

Decrypting and Encrypting Exported Constraint

Data
After you export encrypted constraint data, you can decrypt the data files. You would
commonly use the decrypted data to generate reports of your design, prepare design reviews, or
perform automated verification of constraint data with external programs.
The purpose of working with decrypted CSV data is to view or modify it in an external
spreadsheet application that supports the CSV format. In the event that you do modify the CSV
data, or create CSV files from scratch for import, you do not need to encrypt the data files
before importing them into Constraint Manager.

Prerequisites
• You have the following license: cesencryption
• You have exported encrypted ASCII constraint data or have decrypted or encrypted
CSV data.
Procedure
1. Verify that you have met all prerequisites.
2. Run the following command with the appropriate arguments: “csv2dat” on page 571

342 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Export and Import
Import of Constraints

Import of Constraints
You can import constraints for the purpose of reusing constraints and templates between
designs, if applicable, or to load a large number of constraints instead of providing them by
hand. If using import for the second purpose, you must be working in the CSV format. You can
import the following types of data files: .cts, .csv, and .ecsv
Importing Constraints in Encrypted XML Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
Importing Constraints in CSV Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
CSV Importer Error and Warning Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
CSV Format Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348

Importing Constraints in Encrypted XML Format

You can import constraints and templates that you exported in encrypted XML format (.cts)
during an earlier Constraint Manager session. By importing constraints that are stored in a data
file, you can easily work with constraint data that you or another engineer saved at a previous
time.
For example, if you are having trouble developing constraints for a specific net, you can export
your best-guess constraint data to a file, send it to another engineer (for example, a signal
integrity expert), and then that person can import your constraints in their Constraint Manager
environment to help create the appropriate constraint solution.

Note
You can also import constraints in the proprietary encrypted XML format (.cts) using a
command-line tool. For more information, refer to “cons2xml” on page 569.

Notes on import:

• The tool does not update via definitions and settings during the import process.
• If name changes have occurred after you export constraints, constraint values may not
be properly imported.
• After you import, you may want to set the display units for the constraint set. For more
information, refer to “Setting Spreadsheet Units” on page 104.
If you import constraints from one design to another, it is important to understand that these
requirements and implications exist:

• In order for a net to become updated with the constraints stored in the exported file, the
net name must be an exact match between constraint sets. For example, if the constraint
set into which you are importing constraints contains net A1 but the exported constraints
file does not, no updates are made to net A1 as a result of the import.

Constraint Manager User's Manual, X-ENTP VX.2.8 343

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Export and Import
Importing Constraints in CSV Format

• For nets that have matching names between the constraint set and the exported
constraints file, the tool will overwrite all constraint values for those nets.
Procedure
1. From the File menu, click Import, then click Constraints.
2. In the Import Constraints dialog box, select the constraints file (.cts) you want to load,
then click Open.
3. (Optional) Set the display units for the constraint set. For more information, refer to
“Setting Spreadsheet Units” on page 104.
Related Topics
Constraint Export in Encrypted XML Format

Importing Constraints in CSV Format

You can import constraints in CSV format (.csv) for the purpose of loading a large number of
constraints instead of providing them by hand. You can also import encrypted CSV (.ecsv) files.
Typically, an import includes physical constraints such as clearances, trace widths, and similar
values. For example, you could import a large number of package type clearance rules and
overrides.
CSV files you import can include just a single constraint table or multiple tables. For example,
one file you might choose to import could include just general clearances and clearances, while
another could include all constraint tables that you can import.

Caution
You cannot undo the results of a CSV import. You should create a backup or copy of the
project before you import. Doing so makes it easier to recover your data if you import
incorrect constraints. To create a backup, use the iCDB Project Backup utility.

Notes on import:

• During this process, Constraint Manager checks the syntax of the CSV file to validate its
components. This includes the CSV header, table names, display units, columns
(whether any are missing, redundant, or unknown), required values (whether any are
missing), unknown levels, and values.
• The tool examines integers and real numbers (“doubles”) to determine if they fall within
a required range.
• If a file includes net constraint data or constraint template data, Constraint Manager
checks the content during import.

344 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Export and Import
Importing Constraints in CSV Format

Restrictions and Limitations

• CSV import is not supported in an Xpedition EDM Design flow.
• Concurrent import is not supported.
• Via definitions are not updated during the import process.
• Although you can create many data objects directly in Constraint Manager, just a subset
of them are supported for creation through CSV import. The currently supported objects
are the following:
o Class-to-class clearance rules
o Clearance rules
o Net classes
o Package type clearance rules
o Package type to package type clearance override rules
o Schemes
o Z-axis class-to-class clearances rules
o Z-axis clearance rules
Prerequisites
• To use CSV import, you must set an environment variable called
CESENG_IMPORTCSV_ENABLE to 1.
• CES Diagnostics must report no issues in order for import to run.
• The stackup must already be defined for the project. Stackup definition or updates are
not supported.
• The file does not contain any duplicate object definitions. You can define each
constraint just once in the file. If a constraint has multiple definitions, import does not
run.
Procedure
1. Verify that you have met all prerequisites.
2. From the File menu, choose Import > Constraints from CSV.
3. In the Import constraints from CSV dialog box, select the .csv file or .ecsv file you want
to import, then click Open.

Note
To import from the command line, run the command “cons2csv” on page 566 with
the appropriate arguments.

Constraint Manager User's Manual, X-ENTP VX.2.8 345

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Export and Import
CSV Importer Error and Warning Codes

Results
After the import finishes processing, a log file for the import is written to the following location:
<design_folder>\CES\LogFiles\<snapshot_name>\<block_name>\<machine_name>\
<user_name>\csv_import_<date_time>.log
For example, C:\Tablet_design_1\CES\LogFiles\DxD\screen\psmith-lt\psmith\
csv_import_20121017_122937.log
At this point, you may want to set the display units for the constraint set. For more information,
refer to “Setting Spreadsheet Units” on page 104.
Related Topics
Decrypting and Encrypting Exported Constraint Data
Exporting Constraints in CSV Format
CSV Importer Error and Warning Codes
Example CSV Files
Guidelines for CSV Files

CSV Importer Error and Warning Codes

Refer to the table for the full listing of CSV importer code numbers and their corresponding
code names. You may find this information useful in the event that an import operation does not
complete, or even run at all, for a certain file.

Table 12-1. CSV Importer Codes

Code Number Code Name
0 EIC_ResOk
1 EIC_ResOkWithErrors
2 EIC_ResOkWithWarnings
3 EIC_ResCmdSyntaxError
4 EIC_ResIOFileError
5 EIC_ResError
6 EIC_ResLicError
7 EIC_ResCesChkWarnings
8 EIC_ResCesChkErrors
10 EIC_ResCESPIError
11 EIC_DatabaseCannotOpen

346 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Export and Import
CSV Importer Error and Warning Codes

Table 12-1. CSV Importer Codes (cont.)

Code Number Code Name
12 EIC_DatabaseCannotLoad
13 EIC_DatabaseCannotLock
14 EIC_DatabaseCannotBeginTrans
15 EIC_DatabaseCannotCommitTrans
16 EIC_DatabaseCannotBackup
40 EIC_ResSyntaxValError
41 EIC_SyntaxQuoteMissing
42 EIC_SyntaxColumnMissing
43 EIC_SyntaxColumnRedundant
44 EIC_SyntaxColumnUnknown
45 EIC_SyntaxRequiredValueMissing
46 EIC_SyntaxLevelUnknown
47 EIC_SyntaxLevelNotAllowed
48 EIC_SyntaxValueInvalid
49 EIC_SyntaxValueRedundant
100 EIC_ContentError
101 EIC_ResContentNAWarning
102 EIC_ContentObjectMissing
150 EIC_ImportError

Constraint Manager User's Manual, X-ENTP VX.2.8 347

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Export and Import
CSV Format Overview

CSV Format Overview

Although you can work with CSV files in an ASCII text editor, the best way to do so is with a
spreadsheet application that supports the CSV format. This method is recommended because
the display of constraint data looks more familiar through a spreadsheet display. In addition,
there is the chance that you could accidentally remove one or more delimiters if using an ASCII
text editor.
Note
The value separator/delimiter you must use in these CSV files is a semicolon (;).

Example CSV Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348

Guidelines for CSV Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351

Example CSV Files

Refer to the example CSV files, each of which represent what a CSV file looks like in a
spreadsheet application that supports the CSV format.
The first example is a CSV file that includes these two constraint tables:

• Class to class clearances

• General clearances
Notice that the first of the two constraint tables does not specify a value for “Display Units.”
Instead, the unit type of th is defined individually in the rightmost cells, where appropriate. For
the second constraint table, “Display Units” is set to th. For this reason, it is not defined in each
of the rightmost cells.

In the event that the tool does not use the same unit type for these constraints, it converts them
from th to the active Constraint Manager unit type upon import. For example, a value of 35 th is
converted to 0.035 inches if the unit type for linear is instead inches.
Table Class to class clearances
Display Units
Date 2012-03-21 13:52
Description cons2csv - Export/Import constraints to CSV.
Copyright Copyright 2013 Mentor Graphics Corporation. All Rights Reserved.

Scheme From Net Class To Net Class Clearance rule

(Master) (All) (All) (Default Rule)
BGA_RULE1 (All) (All) (Default Rule)

348 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Export and Import
CSV Format Overview

(Master) (Default) (Default) 10th

(Master) CLOCKS (All) 10th
(Master) CLOCKS CLOCKS 5th
(Master) DIFF_PR (All) 5th
(Master) DIFF_PR DIFF_PR 20th
(Master) POWER (All) 20th
(Master) POWER POWER 35th

Table General clearances

Display Units th
Date 2012-03-21 13:51
Description cons2csv - Export/Import constraints to CSV.
Copyright Copyright 2013 Mentor Graphics Corporation. All Rights Reserved.

Contour Cavity & Mounting Hole to Mounting Hole 10

Any to Any Optimal XY 10
Any to Any Optimal Z 5
Contour & Mounting Hole to Non-Plane Conductor 20
Placement Outline to Placement Outline 10
Placement Outline to Placement Obstruct 20
Placement Outline to Design Edge 20
Trace to Resistor 6
Pad to Resistor 6
Testpoint Center to Testpoint Center 50
Cavity Inside Edge to Parts 10
Cavity Outside Edge to non-Plane Conductor 10
Cavity Outside Edge to Plane Conductor 10
Cavity Edge to Cavity Edge 10
The next example is a CSV file that includes just one constraint table, General clearances.
Notice that this table does specify a value for “Display Units.”
Table General clearances

Constraint Manager User's Manual, X-ENTP VX.2.8 349

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Export and Import
CSV Format Overview

Display Units th
Date 2012-03-21 13:51
Description cons2csv - Export/Import constraints to CSV.
Copyright Copyright 2013 Mentor Graphics Corporation. All Rights Reserved.

Contour Cavity & Mounting Hole to Mounting Hole 10

Any to Any Optimal XY 10
Any to Any Optimal Z 5
Contour & Mounting Hole to Non-Plane Conductor 20
Placement Outline to Placement Outline 10
Placement Outline to Placement Obstruct 20
Placement Outline to Design Edge 20
Trace to Resistor 6
Pad to Resistor 6
Testpoint Center to Testpoint Center 50
Cavity Inside Edge to Parts 10
Cavity Outside Edge to non-Plane Conductor 10
Cavity Outside Edge to Plane Conductor 10
Cavity Edge to Cavity Edge 10

Simple CSV File Shown in an ASCII Text Editor

Here is a CSV file consisting of just the Clearance rules tables shown as it would appear in an
ASCII text editor. Notice that the value separator/delimiter used is a semicolon (;) and not a
comma.

350 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Export and Import
CSV Format Overview

Example 12-1. Simple CSV File

Table;Clearance rules;Display Units;th;Date;2013-09-16T11:22:26;

Description;cons2csv - Export/Import constraints to encrypted CSV.
Version: 2013-09-10 12:07:35 (574839);Copyright;Copyright 2013 Mentor
Graphics Corporation. All Rights Reserved.;
Name;Level;Scheme;Clearance rule;Index;Type;Trace To Trace;Trace To
Pad;Trace To Via;Trace To Plane;Trace To SMD Pad;Pad To Pad;Pad To Via;Pad
To Plane;Via To Via;Via To Plane;Via To SMD Pad;Plane To Plane;
(Master);Scheme;;;;;;;;;;;;;;;;;
(Default Rule);ClearRule;(Master);;;;10;10;10;10;10;8;8;8;8;8;8;10;
SIGNAL_1;Layer;(Master);(Default Rule);1;Signal;5;5;5;8;5;8;8;8;8;8;8;10;
SIGNAL_2;Layer;(Master);(Default Rule);2;Signal;5;5;5;8;5;8;8;8;8;8;8;10;
PLANE_3;Layer;(Master);(Default Rule);3;Plane;5;5;5;8;5;8;8;8;8;8;8;10;
PLANE_4;Layer;(Master);(Default Rule);4;Plane;5;5;5;8;5;8;8;8;8;8;8;10;
SIGNAL_5;Layer;(Master);(Default Rule);5;Signal;5;5;5;8;5;8;8;8;8;8;8;10;
SIGNAL_6;Layer;(Master);(Default Rule);6;Signal;5;5;5;8;5;8;8;8;8;8;8;10;
HS_3W;ClearRule;(Master);;;;12;8;8;8;8;8;8;8;8;8;8;10;
SIGNAL_1;Layer;(Master);HS_3W;1;Signal;12;8;8;8;8;8;8;8;8;8;8;10;
SIGNAL_2;Layer;(Master);HS_3W;2;Signal;12;8;8;8;8;8;8;8;8;8;8;10;
PLANE_3;Layer;(Master);HS_3W;3;Plane;12;8;8;8;8;8;8;8;8;8;8;10;
PLANE_4;Layer;(Master);HS_3W;4;Plane;12;8;8;8;8;8;8;8;8;8;8;10;
SIGNAL_5;Layer;(Master);HS_3W;5;Signal;12;8;8;8;8;8;8;8;8;8;8;10;
SIGNAL_6;Layer;(Master);HS_3W;6;Signal;12;8;8;8;8;8;8;8;8;8;8;10;

Related Topics
Importing Constraints in CSV Format
Guidelines for CSV Files

Guidelines for CSV Files

In order to import a CSV file, it must follow certain guidelines. This includes ensuring that all
required fields are available for each constraint table in the file, the proper separation between
constraint tables is present, and more.
Before familiarizing yourself with the information provided in this topic, it is recommended that
you look at some “Example CSV Files” on page 348.

Note
The value separator/delimiter you must use in these CSV files is a semicolon (;).

CSV Files Contain Constraint Tables That Consist of Sections

The illustration shows you the sections that are required for each constraint table in a CSV file.
The CSV file represented by this illustration consists of a single constraint table.

Constraint Manager User's Manual, X-ENTP VX.2.8 351

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Export and Import
CSV Format Overview

Figure 12-1. Structure of a CSV File Containing One Constraint Table

Here is a description of each section:

• CSV Information Section — Identifies the type of constraints supplied in the

constraints section, the display units used, the date, and a description.

Note
“Table” and “Display Units” are the only required values in this section, though you
can leave “Display Units” blank if you do not want to specify a unit type or are not
required to. For examples of this usage, refer to “Example CSV Files” on page 348.

• CSV Separator (one or more new lines) — A visual separation in the file that is used
to separate the information section from the constraints section or the constraints section
from the next information section.
• CSV Constraints Section — Contains the constraint values that you want to import.
You can also include multiple constraint tables in a single CSV file. The illustration
depicts a CSV file that contains two constraint tables. Notice that a CSV separator is
used between the two constraint tables.

352 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Export and Import
CSV Format Overview

Figure 12-2. Structure of a CSV File Containing Two Constraint Tables

Table Name Field in CSV Information Section

One of the two required fields in the CSV Information Section is the type of constraint table.
This field is not only required but must match precisely to one of the names in the reference
table (for example, “Z-Axis class to class clearances”).

Note that currently not all constraint tables are supported for import at this time. Non-supported
constraint tables are indicated with an * in the listing of table names.
Table 12-2. Constraint Tables
Valid Table Names
Class to class clearances
Clearance rules
Constraint templates *
Constants & variables *
General clearances
Nets * (Although import of most constraints in this table is
not yet supported at this time, you can import Net Class
assignments through it.)

Constraint Manager User's Manual, X-ENTP VX.2.8 353

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Export and Import
CSV Format Overview

Table 12-2. Constraint Tables (cont.)

Valid Table Names
Noise rules *
Package type clearance rules
Package type to package type clearance rules
Parallelism rules *
Parts *
Power & ground *
Stackup *
Traces
Via assignments
Z-Axis class to class clearances
Z-Axis clearance rules
Although the “Table” in a CSV Information section must be one of the accepted names, this
does not include case-sensitivity. For example, you could use either “Clearance rules” or
“CLEARANCE RULES”. Both would work.

Display Units Field in CSV Information Section

The second of the two required fields in the CSV Information Section is the “Display Units”
field. Although this field is required, you do not need to supply a value for some tables. If you
do want to provide a value, or are required to, you must use one (or more) of the display units in
the reference table. For more information, refer to “Constraint Tables and Required Unit Type
Declarations” on page 355.

It is important to note that these values are case sensitive. Note that currently most unit types are
not supported for import. Non-supported unit types are indicated with an * in the table.
Table 12-3. Valid Display Units
Unit Type Display Units (Case Sensitive)
Linear in th mm um nm
Angle * deg Rad ‘ “
Capacitance * F mF uF nF
Voltage * V mV uV nV
Inductance * H mH uH nH
Power * W mW uW nW
Velocity * in/ns m/s %c

354 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Export and Import
CSV Format Overview

Table 12-3. Valid Display Units (cont.)

Unit Type Display Units (Case Sensitive)
Resistance MOhm kOhm Ohm mOhm uOhm
Time * s ms us ns ps
Current * A mA uA nA pA
Temperature * degC
Theta * degC/W
If a constraint table includes constraints of multiple unit types, you can list them all by
separating them with a | character (for example, th|ns).

The table shows you which constraint tables require you to declare one or more unit types
through the “Display Units;” statement. After the table, you can find a short list of guidelines
you must follow if making these declarations.
Table 12-4. Constraint Tables and Required Unit Type Declarations
Table Name Required Unit Types
Clearance rules <linear>
Example: Display Units; th;
Constraint templates <linear>|<resistance>|<voltage>|<time>
Example: Display Units; th|Ohm|mV|ps;
General clearances <linear>
Example: Display Units; in;
Nets <linear>|<resistance>|<voltage>|<time>
Example: Display Units; in|mOhm|V|ns
Noise rules <voltage>
Example: Display Units; mV;
Package type clearance <linear>
rules Example: Display Units; th;
Package type to package <linear>
type clearance rules Example: Display Units; in;
Parallelism rules <linear>
Example: Display Units; th;
Parts <time>|<temperature>|<power>|<theta>|<linear>
Example: Display Units; ns|degC|W|degC/W|in;

Constraint Manager User's Manual, X-ENTP VX.2.8 355

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Export and Import
CSV Format Overview

Table 12-4. Constraint Tables and Required Unit Type Declarations (cont.)
Table Name Required Unit Types
Stackup <linear>|<resistance>
Example: Display Units; th|Ohm;
Traces <resistance>|<linear>
Example: Display Units; Ohm|th;
Via assignments None.
Z-Axis clearance rules <linear>
Example: Display Units; in;
If specifying required unit type declarations, you must follow these rules:

• You can use whichever order you like for the unit types, but each required type must be
part of the declaration.
• You must only define a unit type once. Multiple declarations for the same unit type will
cause the import to fail.

CSV Constraints Section

The CSV Constraints Section is the largest section in a constraint table. This is because it
specifies the constraint values that you want to import. If modifying the data in one or more of
these sections, be aware of the following:

• You have the option of using engineering/scientific notation for constraint values (for
example, 1.25E+6).
• For boolean values, you have the option of using “true” for 1/on and “false” for 0/off.
• You can assign a different display unit to any constraint value simply by putting it after
the value. For example, if the constraint table specifies “Display Units” of th, you can
put a value like 0.1mm in one or more cells.
• Constraint Manager does not create a data object (for example, scheme, net class, or
clearance rule) just because you reference it in the file. It either must already exist in the
tool or be something that you define for creation in the file. For example, if working
with net classes, any net class that you reference must already exist in Constraint
Manager or be defined in the CSV file.
• The order of columns is not important, but all column headings must be present. You
cannot import a table with any missing column headings.
• The order of rows is not important, but each row must contain all values. You cannot
import a table with any missing values; however, you can import empty values
(semicolon only) to preserve the current data.

356 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Export and Import
CSV Format Overview

• You can enclose data in double quotes if it makes sense to do so. For example:
Description;“Net Class Template for ““10-layer stackup”””;

Related Topics
Importing Constraints in CSV Format
Example CSV Files

Constraint Manager User's Manual, X-ENTP VX.2.8 357

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Export and Import
CSV Format Overview

358 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Chapter 13
Stackup Display and Modification

In Constraint Manager, you can view the characteristics of the board stackup used in a printed
circuit board design. Depending on your design flow, you may also be able to modify the
stackup.

Viewing or Modifying Stackup Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359

Stackup File Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Layer Name Correlation Among Design Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
Stackup Editing Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364

Viewing or Modifying Stackup Properties

You can view or modify the properties of the stackup associated with a Constraint Manager
design to visualize a cross section of the PCB and evaluate the effects of changing parameters of
the materials used in the board construction.
A stackup is the layering of conductive and dielectric materials that make up a printed circuit
board. The characteristics of these materials (for example, thickness, dielectric constants, and
conductivity) and how they are ordered determine the electrical characteristics (for example,
nominal impedance) of the PCB's traces.

Caution
Because the Stackup Editor is designed to give you the ability to analyze the effects of
changing parameters on the electrical characteristics of traces, it allows for the entry of any
value for the material properties. There are a limited number of materials available for the actual
construction of a PCB. The list of materials and their actual characteristics should be available
from the PCB manufacturer. This list of materials limits the material parameters available and
also constrains the order in which you can stack them. For a useful stackup analysis, the
material properties used should come from the manufacturer’s supplied information.

Prerequisites
• Read and understand the information in “Layer Name Correlation Among Design
Tools” on page 364.
• Read and understand the information in “Stackup Editing Limitations” on page 364.

Constraint Manager User's Manual, X-ENTP VX.2.8 359

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Stackup Display and Modification
Viewing or Modifying Stackup Properties

Procedure
On the General toolbar, click , or, from the Edit menu, click Stackup.

Results
Stackup changes affect only the front-end design or back-end design until you forward annotate
or back annotate. At that time, the changes are synchronized between the schematic and layout
design representations based on the constraint synchronization process. For more information,
refer to “Synchronization of Constraint Sets” on page 386.
Related Topics
Layer Name Correlation Among Design Tools

360 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Stackup Display and Modification
Stackup File Import

Stackup File Import

Import stackup files into Constraint Manager to replace the current stackup for a design. The
tool supports import of HyperLynx stackup files (.stk) and Polar Speedstack stackup files
(.stkx).
You can optionally import impedance structures stored in Polar .stkx files, and Frontline .stk
files if a .fsi file of the same name exists (for example, 8_layer.stk and 8_layer.fsi) and is stored
in the same location. For Polar files, all impedance structure information is included in the .stkx
file.

Note
V12 Polar files can also include net class definitions. If they exist, the wizard makes them
available for selection in the Target Net Class column if you choose to import impedance
structures. The tool creates the selected net classes as part of the stackup import process.

Importing HyperLynx Stackups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361

Importing Polar Speedstacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362

Importing HyperLynx Stackups

Import a HyperLynx stackup into Constraint Manager to replace the current stackup for a
design.
Restrictions and Limitations
• You cannot import a different layer type into an existing layer.
• You cannot import stackups into Rigid Flex designs.
• You cannot import a stackup into a schematic invocation of Constraint Manager if the
PCB design exists. You must also import a layout template into Constraint Manager
before importing the stackup.
Video
Watch the video to learn how to:

• View the current stackup.

• Select a HyperLynx stackup to import.
• Map layers to preserve constraints.

Constraint Manager User's Manual, X-ENTP VX.2.8 361

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Stackup Display and Modification
Importing Polar Speedstacks

• View the new stackup.

Procedure
1. Import a HyperLynx stackup file in one of the following ways:

If you want to ... Do the following ...

Import through the GUI Refer to the video in this topic.
Import from the command Refer to “ImportStk” on page 576.
line

2. Load the stackup changes into the layout design by clicking the rightmost indicator light
in the layout tool (do not use the Project Integration dialog box to accomplish this). You
can also load the changes by instead closing and reopening Constraint Manager.

Note
You must back annotate to view the updated stackup in schematic invocations of
Constraint Manager.

Results
The Stackup Editor shows the updated stackup. You can now make additional modifications as
needed.

Importing Polar Speedstacks

Import a Polar Speedstack into Constraint Manager to replace the current stackup for a design.
You can also select impedance structures that define values for Trace Width and Differential
Spacing constraints.
Restrictions and Limitations
• You cannot import a different layer type into an existing layer.
• You cannot import stackups into Rigid Flex designs.

362 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Stackup Display and Modification
Importing Polar Speedstacks

• You cannot import a stackup into a schematic invocation of Constraint Manager if the
PCB design exists. You must also import a layout template into Constraint Manager
before importing the stackup.
Video
Watch the video to learn how to:

• Select a Polar Speedstack to import.

• Select impedance structures.
• View updated Trace Width and Differential Spacing values.

Procedure
1. Import a Polar Speedstack file in one of the following ways:

If you want to ... Do the following ...

Import through the GUI Refer to the video in this topic.
Import from the command Refer to “ImportStk” on page 576.
line

2. Load the stackup changes into the layout design by clicking the rightmost indicator light
in the layout tool (do not use the Project Integration dialog box to accomplish this). You
can also load the changes by instead closing and reopening Constraint Manager.

Note
You must back annotate to view the updated stackup in schematic invocations of
Constraint Manager.

Results
The Stackup Editor shows the updated stackup. You can now make additional modifications as
needed.

Constraint Manager User's Manual, X-ENTP VX.2.8 363

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Stackup Display and Modification
Layer Name Correlation Among Design Tools

Layer Name Correlation Among Design Tools

The spreadsheet, Stackup Editor, and your PCB layout system all use slightly different
nomenclature when referring to unique board-layer types. Refer to the table for an
understanding of how these names correlate among design tools.

Table 13-1. Board-Layer Name Correlation

Constraint Manager Stackup Editor PCB Layout System
Spreadsheet
Signal Signal Signal
Solid Plane Solid Plane Plane
Mixed Split/Mixed Signal
Flood Signal Flooded Signal Flooded

Constraint Manager only shows signal layers. As such, dielectric layers displayed in the
Stackup Editor do not appear in the constraint spreadsheets.

Stackup Editing Limitations

The layout tool you are using determines the level of functionality available in the Stackup
Editor. In the Xpedition Enterprise and PADS Professional flows, stackup changes are
propagated to the layout tool.
If changing the stackup in Constraint Manager after the board has already gone through routing
in the PCB tool, there can be serious consequences to the work done in the layout tool. For
example, removing a layer from the stackup could easily result in lost routing if there were
traces on the removed layer.

364 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Chapter 14
Part-Model Assignment Verification and Part
Constraints Definition

This section provides information about how to make models and libraries of models available
to Constraint Manager for the purposes of satisfying existing model assignments and also
making new assignments.
Automatic Assignment of IBIS Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
IBIS Models or Technology Models? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
IBIS Models Delivered With Constraint Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Part Model Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Verifying Default Model Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Assigning Models to Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
Editing Model Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Updating Part Model Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Overriding IBIS Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Defining Thermal Constraints for Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
Importing Pin Package Delay or Length Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
PinPkgDelays.txt File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
PinPkgLengths.txt File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378

Automatic Assignment of IBIS Models

Constraint Manager automatically assigns IBIS models you select from within your design tool
if certain conditions are met.
The conditions are the following:

• The model matches the pinout of the part.

• The model parses without error.
• The PART_NO property for the part matches an IBIS Component name in an (.ibs) file
that resides in one of the SI Library search paths. For more information, refer to “Part
Model Availability” on page 368.

Constraint Manager User's Manual, X-ENTP VX.2.8 365

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Part-Model Assignment Verification and Part Constraints Definition
Automatic Assignment of IBIS Models

Hierarchical Assignment Process

Constraint Manager uses this assignment hierarchy to set the default IBIS Component Name
value for each part:

1. If you provide the IBIS component attribute on a symbol that is contained in a part
instance, it is used as the default IBIS component name. If this attribute is set on more
than one symbol that maps to a particular part instance, Constraint Manager decides
which wins based on its established rules.
2. User provided IBIS component name for the entry in the PDB corresponding to the part
instance.
3. Constraint Manager searches the IBIS library for a component with the same name as
the PCB part name. If it finds a case insensitive match, it uses this value.
4. Constraint Manager searches the IBIS library for a component with the same name as
the symbol name for the part instance in the PDB. If it finds a case insensitive match, it
uses this value.
5. If the part instance has a Technology value, Constraint Manager searches for an IBIS
component that matches the technology. If it finds a match, it uses this value.
6. If the part instance is a simple passive component that is included in the list, it sets the
IBIS component name to one of these values:
o R_by_value (resistor)
o C_by_value (capacitor)
o L_by_value (inductor)
o RC_by_value (RC terminator)
o RThev_by_value (thevenin terminator)
7. If the part instance is not a simple passive component, diode, or connector, it sets the
default IBIS component name to “generic”. The IBIS library provided with the release
always contains a supporting IBIS component named “generic” to support this type of
assignment.

Note
The only case where Constraint Manager sets IBIS Component Name to reference a
component that does not exist is if you explicitly set a name in the schematic or
PDB, and it does not exist.

366 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Part-Model Assignment Verification and Part Constraints Definition
IBIS Models or Technology Models?

IBIS Models or Technology Models?

Although you can assign an IBIS model and a technology model to a single part, if both are
present, the tool uses the IBIS Component Name model. IBIS models provide greater detail than
technology models, which model pins based only on pin type.
IBIS models include dedicated pin models for each component pin. For example, an IBIS model
for a sixteen pin component will include sixteen individual pin models. A technology model
used for the same component may include three or four pin models (that is, one for each type of
pin for the sixteen pin set).

IBIS Models Delivered With Constraint

Manager
Constraint Manager comes with a set of IBIS models that you can use to model an array of
component technologies.
There are IBIS models available at this location:

<Mentor Graphics install location>\EEVX.x\SDD_HOME\hssd\models\ibis\tech

You can also search your Mentor Graphics software installation for other .ibs files.

Constraint Manager User's Manual, X-ENTP VX.2.8 367

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Part-Model Assignment Verification and Part Constraints Definition
Part Model Availability

Part Model Availability

You must make part models available within Constraint Manager for part assignment. If doing,
so you can add entire directories of models or just single models. You can choose from folders
and files throughout your network.
Constraint Manager supports IBIS (I/O Buffer Information Specification) component models.
In addition to the standard IBIS model file format (.ibs), you can also use IBIS EBD (electrical
board definition) model files (.ebd).

Note
After you invoke the IBIS Model Browser dialog box, the tool automatically adds the
directories in the ..\Models\IBIS folder of your central library. This includes all sub-folders
that contain IBIS models. To access the dialog box, on the Parts spreadsheet page, click the
browse button in any IBIS Component Name cell or Technology cell.

Specifying Model Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368

Specifying Individual Model Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
Reloading Model Directories and Individual Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . 369

Specifying Model Libraries

You can add directories, remove existing directory entries, and change the order of directories
searched and displayed within the IBIS Model Browser. It is important to understand that
Constraint Manager treats each file system directory containing IBIS models as a library.
If you type a relative path, the tool makes an attempt to fully resolve the path. On Windows®,
this includes pre-pending the current drive letter from which you launched Constraint Manager.
If the path does not exist, the tool prompts you with a dialog box asking whether you want to
keep the path as-is or reject it. If you keep it, the tool uses the unresolved path.

Procedure
1. You specify model libraries through the IBIS Model Browser. To access it, on the Parts
spreadsheet page, click the browse button in any IBIS Component Name cell or
Technology cell.
2. In the IBIS Model Browser, at its top right, click , then do any of the following:

• Add a directory to the model search path — In the SI Library Search Paths dialog
box, click . In the new row that appears in the IBIS Libraries listing, type the
directory path, or click the browse button to navigate to the path, then select it.
• Remove a directory from the model search path — In the SI Library Search
Paths dialog box, in the listing of IBIS Libraries, click the directory you want to
remove, then click .

368 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Part-Model Assignment Verification and Part Constraints Definition
Specifying Individual Model Files

• Change the search order of model directories — In the SI Library Search Paths
dialog box, in the listing of IBIS Libraries, click the directory for which you want
you to change its order, then click or to move the directory up or down within
the list.
3. When finished, click OK.
Related Topics
IBIS Component Name
Technology

Specifying Individual Model Files

If you want to make one or more single model files available to Constraint Manager, you can
add individual IBIS and EBD files to the group of available models.
You can use both methods of model specification interchangeably. For example, after
specifying one or more model file directories (libraries), you can add a dozen individual model
files to complete the overall selection of available models.

Procedure
1. With the Parts spreadsheet page active, in any IBIS Component Name or Technology
cell, click .

2. In the IBIS Model Browser, click .

3. In the Open dialog box, browse to a model file (.ibs or .ebd), select it, then click Open.
Results
All models included in the model file are now available within Constraint Manager for
assignment.
Related Topics
IBIS Component Name
Technology

Reloading Model Directories and Individual Models

If one or more of your model directories or individual models are located in a network folder, it
is best practice to occasionally reload those model directories or individual models. By doing
so, you can make sure the model data available to Constraint Manager is the most current.

Constraint Manager User's Manual, X-ENTP VX.2.8 369

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Part-Model Assignment Verification and Part Constraints Definition
Verifying Default Model Assignments

You should also reload model information if you make changes to any model directories or
individual models on your local machine. Reloading a model directory refreshes all individual
models contained within it.

Procedure
1. With the Parts spreadsheet page active, in any IBIS Component Name or Technology
cell, click .

2. Do any of the following:

• Reload model directories — Complete these steps:
i. In the IBIS Model Browser, under Directories / Components, select one or more
model directories:
• Select all model directories by clicking the All row.
• Select two or more model directories by using Ctrl-click and Shift-click to
highlight the appropriate rows.
• Select just a single model directory by clicking it.
ii. Click .

• Reload an individual model — In the IBIS Model Browser, in the list of available
models, click a row, then next to the Search component field search button, click .

Tip
To adjust the list of available models, use the directory selections under
“Directories / Components.” For example, to list all available models, click All.

3. When finished, click OK.

Related Topics
Update of Electrical Net Data and Results
IBIS Component Name
Technology

Verifying Default Model Assignments

The first time you launch Constraint Manager on a design, it automatically assigns models to
parts by matching design components with part models located in model directories available to
the tool.
To ensure that the default assignments are correct, you should verify them using the content
generated by the Model Audit Report. If one or more assignments are incorrect or unavailable,
you must manually assign the correct model.

370 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Part-Model Assignment Verification and Part Constraints Definition
Assigning Models to Parts

Procedure
1. From the Output menu, click Model Audit Report.
2. In the Model Audit Report that Constraint Manager produced, scroll its content to locate
instances of ERROR and WARNING lines.

Tip
Copy the content of the report and paste it into a local ASCII file to make it easier to
fix a long list of issues.

3. Click OK to exit the report.

4. For each instance, locate its row on the Parts spreadsheet page, and do one of the
following:
• Assign the correct model to the part.
• Specify additional available part models, then assign the correct model to the part.
5. Return to step 1 to produce a new report.

Assigning Models to Parts

You can assign models to parts to specify the component technology they should represent. In
most cases, each part will already include a model assignment. If an assignment is incorrect,
you can change the model associated with a part.
Because pin information is stored in each part model, these designations are also used by
Constraint Manager to construct accurate nets.

Procedure
1. On the Parts spreadsheet page, in the row of the component to which you want to assign
a model, in its IBIS Component Name or Technology cells, click .

2. In the IBIS Model Browser, under Directories / Components, click a specific directory,
or click All to display models in all directories that are available to Constraint Manager.

Tip
To select multiple directories but not all directories, use Ctrl-click and Shift-click.
To search for a directory, in the Search directory field, type a search string, then
click .

3. In the Component list, click the model you want to assign to the component.

Constraint Manager User's Manual, X-ENTP VX.2.8 371

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Part-Model Assignment Verification and Part Constraints Definition
Editing Model Files

Tip
You may need to search for a model if the Component list includes a large number of
models. To do so, in the Search component field, type a search string, then click .

4. The previous three steps define the IBIS model for the part. Many parts are configurable,
and the pin characteristics change depending upon how they are configured. To
accommodate this, the IBIS model may contain multiple pin models for a given pin. To
ensure accurate simulations, it is important that the correct pin model be selected for
these pins. The IBIS Model Browser indicates pins for which multiple models are
available by coloring the Pin cell yellow in the Pin Model Types table. To change a pin
model:
a. In the Pin Model Types field, click the dropdown, then click a specific pin type you
want to view or change (for example, Output) or All to display all pins of the part.
b. In the table below the Pin Model Types field, click in the Model cell of the pin you
want to change, then select the pin model in the drop down list.

Tip
To change the display of this table, use the Select by Pin and Select by Model
radio buttons.

5. Click OK to apply the model assignment.

Related Topics
IBIS Component Name
Technology

Editing Model Files

You can edit model files using the HyperLynx Visual IBIS Editor or the Quick Model Wizard.
Procedure
1. With the Parts spreadsheet page active, in any IBIS Component Name or Technology
cell, click .

2. In the IBIS Model Browser, select a model file in the Component list.
3. Do one of the following based on the editor you want to use:
• To use the HyperLynx Visual IBIS Editor, click .

• To use the Quick Model Wizard, click .

372 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Part-Model Assignment Verification and Part Constraints Definition
Updating Part Model Constraints

Updating Part Model Constraints

You can update the IBIS Pin Type part model constraint to reflect accurate pin designations.
Doing so also updates default values.
Procedure
1. Select the Parts spreadsheet page.
2. From the Data menu, click Update IBIS Pin Type & Defaults.

Overriding IBIS Values

For discrete components, Thevenin terminators, and AC terminators that reference IBIS
models, you can override the discrete values stored in them by typing values directly into
Constraint Manager.
For example, although the IBIS model for a resistor specifies resistance as 50 ohms, you want to
temporarily change the value to 60 ohms.

Procedure
1. On the Parts spreadsheet page, in an appropriate IBIS Component Name cell, type one
of these override types:
• C_by_value — Capacitance by value.
• L_by_value — Inductance by value.
• R_by_value — Resistance by value.
• RC_by_value — AC terminator by value.
• RThev_by_value — Thevenin terminator by value.
2. In the Value cell, type one or more override values based on these guidelines:
• For C_by_value, L_by_value, and R_by_value, type a single override value.
• For RC_by_value, type a resistance and a capacitance value, and separate them with
a colon (for example, 75:5).
• For RThev_by_value, type two resistance values, and separate them with a colon
(for example, 75:75).
In the illustration, a resistor model has been changed to a Thevenin terminator with
resistance values of 75 ohms and 50 ohms.

Constraint Manager User's Manual, X-ENTP VX.2.8 373

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Part-Model Assignment Verification and Part Constraints Definition
Defining Thermal Constraints for Parts

Figure 14-1. Thevenin Terminator by Value

Defining Thermal Constraints for Parts

You can define thermal constraints within Constraint Manager for the purpose of specifying
constraint values that must be adhered to within your HyperLynx Thermal testing environment.
Presently, these constraints are only supported by that simulation tool.
Prerequisites
• To make use of any values you define for these constraints, you must be using
HyperLynx Thermal as part of your design flow.
Procedure
1. Select the Parts spreadsheet page.
2. Define values for any of these thermal constraints:
• “Thermal Power Dissipation” on page 545
• “Thermal Power Scaling Factor” on page 546
• “Thermal Theta-jc” on page 547
• “Thermal Casing Temperature Limit” on page 548
• “Thermal Junction Temperature Limit” on page 549
Results
Any thermal constraints you define for the design are included as requirements in your
HyperLynx Thermal simulation environment.

Importing Pin Package Delay or Length Values

You can import pin package delay or length values from side files instead of manually typing
values for one or more Pin Package Delay or Pin Package Length constraints.
This task shows you how to use the Constraint Manager GUI to import a side file, but you can
also use command-line utilities to do so. For more information, refer to
“ImportPinPackageDelays” on page 572 and “ImportPinPackageLengths” on page 574.

374 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Part-Model Assignment Verification and Part Constraints Definition
Importing Pin Package Delay or Length Values

Note
In some cases, an IC vendor provides a ready-to-use side file for one or more ICs. In any
event, pin package data always come from an IC vendor.

Prerequisites
• You must have an appropriate side file: PinPkgDelays.txt, *.ppd, PinPkgLengths.txt, or
*.ppl
Procedure
1. Choose File > Import > Package Delays.
2. In the Import Package Delays dialog box, navigate to and select a package delays or a
package lengths file.
3. (Optional) click to enable the check box “Set 0 when package delays are not specified.”
This check box sets values to 0 for any pin delays or lengths that the side file does not
specify. This only applies to pins of part numbers defined in the side file. Otherwise, the
tool keeps the existing values.
4. Review your selections, then click Import.
Results
The tool updates the Parts spreadsheet page to display the imported values.
Related Topics
PinPkgDelays.txt File Format
PinPkgLengths.txt File Format
Pin Package Delay
Pin Package Length

Constraint Manager User's Manual, X-ENTP VX.2.8 375

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Part-Model Assignment Verification and Part Constraints Definition
PinPkgDelays.txt File Format

PinPkgDelays.txt File Format

Input for: Constraint Manager “Pin Package Delay” constraint values.
Use a PinPkgDelays.txt file or *.ppd file to define pin package delays on a per-pin basis for
specific parts. The sum of a pin package delay value and the associated trace delay determines if
the trace delay meets the delay rule defined in Constraint Manager.
Format
A PinPkgDelays.txt or *.ppd file must use this format:

UNITS <unit>
PART_NUMBER <part_name>
<pin_number> <value>

Parameters
• UNITS <unit>
A required keyword at the top of the file specifying the units of the map file. Valid values
for units: seconds (s), milliseconds (ms), microseconds (us), nanoseconds (ns), and
picoseconds (ps). This value is case-insensitive.
• PART_NUMBER <part_name>
A required keyword that specifies the name of the part.
Note
If a <part_name> contains a space, the tool considers all characters after <part
name> part of the part name until the next PART_NUMBER keyword.

• <pin_number> <value>
A single line for each pin number and its associated delay value.
Caution
The tool does not support comma symbols, even if you have Constraint Manager
configured to use commas instead of periods for decimal points.

Examples
This example shows a file that contains definitions for two part numbers. Units are in
nanoseconds.

376 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Part-Model Assignment Verification and Part Constraints Definition
PinPkgDelays.txt File Format

UNITS ns

PART_NUMBER 4610-0054
A1 0.10
A2 0.11
A3 0.12
A4 0.13
A5 0.14
A6 0.15
R1 0.20
R2 0.20
R3 0.20
R4 0.20
R5 0.20
R6 0.20

PART_NUMBER 1120-0008
1 0.05
2 0.06
3 0.05
4 0.06
5 0.05
6 0.06
7 0.05
8 0.06
9 0.05
11 0.15
12 0.15
13 0.15
14 0.15
15 0.15
16 0.15

Related Topics
Importing Pin Package Delay or Length Values
ImportPinPackageDelays
Pin Package Delay

Constraint Manager User's Manual, X-ENTP VX.2.8 377

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Part-Model Assignment Verification and Part Constraints Definition
PinPkgLengths.txt File Format

PinPkgLengths.txt File Format

Input for: Constraint Manager “Pin Package Length” constraint values.
Use a PinPkgLengths.txt file or *.ppl file to define pin package lengths on a per-pin basis for
specific parts. The sum of a pin package length value and the associated trace length determines
if the trace length meets the length rule defined in Constraint Manager.
Format
A PinPkgLengths.txt or *.ppl file must use this format:

UNITS <unit>
PART_NUMBER <part_name>
<pin_number> <value>

Parameters
• UNITS <unit>
A required keyword at the top of the file specifying the units of the map file. Valid values
for units: thousandths (th), microns (um), millimeters (mm), and inches (in). This value is
case-insensitive.
• PART_NUMBER <part_name>
A required keyword that specifies the name of the part.
Note
If a <part_name> contains a space, the tool considers all characters after <part
name> part of the part name until the next PART_NUMBER keyword.

• <pin_number> <value>
A single line for each pin number and its associated length value.
Caution
The tool does not support comma symbols, even if you have Constraint Manager
configured to use commas instead of periods for decimal points.

Examples
This example shows a file that contains definitions for two part numbers. Units are in
thousandths of an inch. As you can see, you do not need to order the pin package length
definitions numerically. The first part number lists them out of order while the second part
number lists them in numerical order.

378 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Part-Model Assignment Verification and Part Constraints Definition
PinPkgLengths.txt File Format

UNITS TH

PART_NUMBER ASIC_AS_0_SOIC_28P_25_394X236_I
5 100
8 200
1 100
7 200
3 200
4 100
2 100
6 200

PART_NUMBER AT25HP512_SOIC_8P_50_197X236_IC
1 100
2 100
3 100
4 100
5 150
6 150
7 150
8 150

Related Topics
Importing Pin Package Delay or Length Values
ImportPinPackageLengths
Pin Package Length

Constraint Manager User's Manual, X-ENTP VX.2.8 379

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Part-Model Assignment Verification and Part Constraints Definition
PinPkgLengths.txt File Format

380 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Chapter 15
Signal Integrity Exploration

This section covers signal integrity exploration and enhancement with HyperLynx® LineSim®.
It presents the entire process of sending nets to HyperLynx LineSim for analysis and
enhancement, and then bringing changes back into Constraint Manager.
Sending Nets to HyperLynx LineSim. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Exporting Constraint Enhancements From HyperLynx LineSim . . . . . . . . . . . . . . . . . 382
Updating Constraint Manager With Constraint Enhancements . . . . . . . . . . . . . . . . . . 383

Sending Nets to HyperLynx LineSim

You can export one or more electrical nets from the Nets spreadsheet page to a LineSim free-
form schematic. In LineSim, you can run “what if” experiments to find physical and electrical
net properties that satisfy signal integrity and other performance requirements.
When you send a net from Constraint Manager to HyperLynx LineSim, the board stackup for
the design is included to ensure simulation accuracy. From LineSim, you can dynamically
update Constraint Manager with LineSim constraint templates; or, export a constraint template
file that you can import back into the tool at a later time.

It is important to note that some information can be lost when transitioning your net data from a
free-form schematic to a constraint template file. For instructions regarding exporting a
constraint template file from LineSim, refer to HyperLynx LineSim documentation or search
the InfoHub to locate this information.

Figure 15-1. Constraint Manager-HyperLynx LineSim Design Flow

Passive component model support when sending nets to HyperLynx LineSim:

• Resistor and capacitor packages modeled as IBIS models in Constraint Manager.

• Series elements described in IBIS/EBD files for IC components. This means that
Constraint Manager exports resistors and capacitors with three or more pins, and
assigned IBIS/EBD models, to the free-form schematic as IC components with assigned
models. It only exports the signal pins of passive network packages that are connected
inside it (that is, belonging to the same electrical net).

Constraint Manager User's Manual, X-ENTP VX.2.8 381

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Signal Integrity Exploration
Exporting Constraint Enhancements From HyperLynx LineSim

Restrictions and Limitations

• Unconnected pins on the net have no topology information. These pins are connected in
a “chained” routing topology that you can verify and edit in the free-form schematic.
• The free-form schematic models exported connectors as ICs with no model assignment.
Prerequisites
• You installed HyperLynx 8.0 or newer on the same computer as Constraint Manager.
• You configured HyperLynx to include the IBIS search paths defined in Constraint
Manager.
• The front-end and back-end design representations are synchronized. This ensures that
the nets you want to export are complete and not missing information (for example,
from-tos automatically generated in layout that do not show up in front-end Constraint
Manager until you back annotate).
Procedure
On the Nets spreadsheet page, right-click a single electrical net ( ) or multiple highlighted
electrical nets (ten maximum), then click Display Net in HyperLynx LineSim.

Results
HyperLynx LineSim automatically opens and displays the net in the free-form schematic editor.
The tool writes the exported free-form schematic (FFS) and HyperLynx project (PJH) files to \
<projects_folder>\<project_name>\HighSpeed\HyperLynx\PreLayoutLineSim<net_name>.
For example, C:\mentor_projects\test_project\HighSpeed\HyperLynx\PreLayoutLineSim\
data1.ffs.
Related Topics
Exporting Constraint Enhancements From HyperLynx LineSim

Exporting Constraint Enhancements From

HyperLynx LineSim
After you enhance a net in HyperLynx LineSim, you have to export those enhancements to
make them available for import into Constraint Manager. You also have the option of updating
the tool dynamically as part of the export process. Doing so makes the changes available to
Constraint Manager immediately but you still need to manually apply the changes to nets.
Prerequisites
• You must be using HyperLynx version 8.2 or newer.
• The Constraint Manager session from which you exported one or more nets is active.

382 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Signal Integrity Exploration
Updating Constraint Manager With Constraint Enhancements

Procedure
1. From the HyperLynx LineSim Export menu, click Constraint Template.
2. (Optional) Activate the “Update CES with generated template” check box to update
Constraint Manager dynamically with the constraint template.
3. Click OK.
Related Topics
Updating Constraint Manager With Constraint Enhancements

Updating Constraint Manager With Constraint

Enhancements
After you make a constraint template available to Constraint Manager, you can apply it to one
or more nets. You make a template available to the tool by importing it manually or updating
Constraint Manager dynamically.
After applying a constraint template to one or more nets, you complete the signal integrity and
enhancement process by updating the tool with the work that you performed in HyperLynx
LineSim.

Procedure
1. If you used the “Update CES with generated template” check box as part of the
procedure in “Exporting Constraint Enhancements From HyperLynx LineSim” on
page 382, skip to step 3.
2. From the Constraint Manager File menu, click Import, then click Constraint
Templates.
3. In the Import Constraint Template dialog box, select the path and filename of the
constraint template file (.ctm) that includes your net topology enhancements, then click
Open.
4. On the Nets spreadsheet page, select one or more electrical nets ( ) to update, right-
click, then click Apply Constraint Template.
5. In the Select Constraint Template dialog box, click the constraint template of the net you
enhanced in HyperLynx LineSim, then click OK.

Constraint Manager User's Manual, X-ENTP VX.2.8 383

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Signal Integrity Exploration
Updating Constraint Manager With Constraint Enhancements

384 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Chapter 16
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 . . . . . . . . . . . . . . . . . . . . . 385

Synchronization of Constraint Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Sending Schematic Data to Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
Sending Layout Data to Schematics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
Schematic Constraints Conflict Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389

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 386.

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

Constraint Manager User's Manual, X-ENTP VX.2.8 385

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Design Tool Update
Synchronization of Constraint Sets

schematic and layout using the forward and back-annotation commands provided by your
design systems.

Xpedition Enterprise Constraint-Driven Design-Flow Manual

For proper usage of these design annotation commands within this constraint-driven design
flow, refer to "Constraint Manager User’s Manual for Xpedition Enterprise Flow".

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 16-1. Constraint Manager Synchronization Process Runs During Design

Annotation

How you set the winner for design annotation depends on the flow you are using. Refer to the
Constraint Manager flow manual for your design flow for more information. For the listing of
flow manuals, refer to “Xpedition Enterprise Constraint-Driven Design-Flow Manual” on
page 386.

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

386 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Design Tool Update
Sending Schematic Data to Layout

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.

Xpedition Team Layout

This tool gives multiple designers the ability to simultaneously work on a single layout project.
Because of this, Constraint Manager synchronization is also used as a back-end only process to
manage changes to layer and net constraints within your PCB design. The result is that all
constraint work performed by multiple designers is accurately stored in the back-end constraint
set.

During forward annotation and back annotation, the front-end and back-end constraint sets are
synchronized as explained in this topic.

Note
If you run XDS Save from Xpedition Team Layout, it back annotates as necessary. As
expected, this back-annotation process includes full Constraint Manager synchronization
between back-end and front-end constraint sets.

Static Team Layout

This tool gives you the ability to partition your layout design, but it does not incorporate
constraint changes made to a partition. For this reason, you should use Static Team Layout to
perform layout operations to partitions–not constraint modifications. After a partition is
rejoined to the main layout design, you can modify constraints in Constraint Manager.

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 constraint-driven design-flow
manual for your flow or the documentation for your schematic-capture software.

Prerequisites
• When sending constraint changes you made in Xpedition Designer to Xpedition Layout,
you must first create a front-end Constraint Manager database by launching Constraint
Manager from Xpedition Designer. You must only do this once in order for the database
to be created. For example, after using only the Xpedition Designer Attributes add-in to
input or modify Xpedition Layout style constraints, you do not yet have a front-end

Constraint Manager User's Manual, X-ENTP VX.2.8 387

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Design Tool Update
Sending Layout Data to Schematics

Constraint Manager database. To create it, from the Xpedition Designer Tools menu,
click Setup Constraints.
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 constraint-driven design-flow manual
for your flow or 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.

388 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Design Tool Update
Schematic Constraints Conflict Resolution

Schematic Constraints Conflict Resolution

You must resolve constraint conflicts between sheets in a schematic design. Conflicts can occur
if you copy sheets between designs.
Resolving Schematic Constraint Conflicts Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Viewing Constraint Resolution Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390

Resolving Schematic Constraint Conflicts Manually

You can use the Constraint Resolution Manager (CRM) mode of Constraint Manager to
manually resolve constraint conflicts that arise between sheets that you copy from a source
schematic design to a target schematic design.
Providing manual constraint resolution during this type of copy gives you the ability to specify
the aspects of net design reuse you want to apply, while keeping important constraint values that
are unique to your design. In some cases, you might want to use most of the constraint values in
the source sheet and keep only a few of the values of the sheet in the target design. In other
cases, you might specify that more constraint values in the target sheet be used than those in the
source sheet.

Prerequisites
• Optional, but recommended, set up your schematic tool to launch CRM automatically as
needed. Refer to your schematic documentation to determine how to set up the
application to launch the Constraint Resolution Manager automatically for conflict
resolution if copying a sheet between two designs.
• You must have copied a schematic sheet from a source design to a target design.
Procedure
1. If Constraint Manager does not automatically display CRM, from Constraint Manager,
with the CRM toolbar enabled, select the most recent item in the dropdown list.
2. Constraint Manager is now in CRM mode. It has the appearance of Constraint Manager,
but provides a limited subset of functions related to manual resolution of constraint
conflicts. At any time, to switch from CRM mode back to Constraint Manager, from the
CRM Tools menu, click Constraint Manager.
If there are conflicting constraint values between source and target objects, the Nets and/
or Trace & Via Properties spreadsheet page highlights each net and/or layer row that has
conflicting constraint values. Cells that do not conflict remain white.
3. For each conflicting cell, you can do the following:
• To view the list of available values from which you can choose, click the dropdown.
“S” refers to the source value, “T” refers to the target value, and “C” refers to a
concurrent value that is being provided in real time.

Constraint Manager User's Manual, X-ENTP VX.2.8 389

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Design Tool Update
Viewing Constraint Resolution Statistics

• To change the default conflict resolution by choosing a different constraint value,

right-click a cell, then click the appropriate Restore to selection. For example, to use
the value already in a sheet which you are pasting, click Restore to Target.
4. Change appropriate constraint values as often as you like until the correct set of source,
target, and concurrent values are present.
5. After you finish, close the CRM or switch to Constraint Manager mode. To do so, from
the CRM Tools menu, click Constraint Manager.
Results
The set of appropriate constraint values is chosen. There are no longer any conflicting
constraints in the target sheet.

Viewing Constraint Resolution Statistics

While you are using the Constraint Resolution Manager, you may find it helpful to get a top-
level view of the source wins, target wins, or all constraint selections you have made to resolve
each set of conflicting values.
Doing so is especially helpful if you want to quickly verify that the selections you made are
correct. The alternative is to scroll through each affected page of the spreadsheet. In
comparison, using that method can be error-prone and time-consuming.

Prerequisites
• Constraint Manager must be in CRM mode.
Procedure
1. From the CRM Data menu, click Constraint Resolution.
2. In the Constraint Resolution dialog box, review the table of Source and target wins and
the summary of win statistics located at the top of the dialog box.
3. (Optional) You can do any of the following:
• To display just target wins, click to enable the Show only target wins check box.
• To display only source wins, click to enable the Show only source wins check box.
• To update the table to show the latest wins after you make changes within the CRM,
click Refresh.
• To cross probe to the spreadsheet row to which a win refers, click a list row. To
move up or down one row in the wins list while cross probing, click or .

4. After you finish reviewing statistics, click Close.

390 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Design Tool Update
Viewing Constraint Resolution Statistics

Results
The dialog box is no longer displayed on screen, leaving the CRM at the forefront of the screen.

Constraint Manager User's Manual, X-ENTP VX.2.8 391

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Design Tool Update
Viewing Constraint Resolution Statistics

392 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Appendix A
Constraint Reference

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393

Trace and Via Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
Clearances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
Z-Axis Clearances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
Nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
Noise Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
Constraint Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558

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, Z-Axis Clearances, Nets, Parts, and
Noise Rules 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.

Constraint Manager User's Manual, X-ENTP VX.2.8 393

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Constraint Reference Overview

Example A-1. Constraint Reference Illustration

Note
For illustrative purposes, components and other board elements may appear
disproportionately large relative to PCB size.

Supported Design Components

Some constraints within this reference indicate that they are supported by design components
that may be included in your constraint-driven design flow. Refer to these definitions for an
understanding of each design component:

• AutoActive® — Integrated place and route environment of Xpedition Layout.

• Hazards — Dynamically updated design rule checking for placement and routing
constraint information. This component is available in Xpedition Layout.
• High-speed routing (HSR) — Routing using estimation to determine how to adjust
routing to meet high-speed constraints (for example, time of flight delay or length). This
component is available in Xpedition Layout.
Related Topics
Constraint Definition Through Spreadsheet Pages
Creating Constraint Groups

394 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
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.
Display Pattern (Trace and Defines the display pattern for a net class. “(None)” is the
Via Properties) default value. Each pattern is a unique combination of a color
and hatching style that you can then apply to the appearance
of nets in the schematic or layout tool to make them more
easily recognizable.
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.
Typical Impedance Defines signal impedance for the Trace Width Typical
constraint. If you type a value into the Trace Width Typical
cell, the tool calculates impedance at this width and places
the result into the Typical Impedance cell.
Differential Typical Defines signal impedance for trace segments that are part of a
Impedance differential pair. The tool automatically calculates and
updates this value if you modify Trace Width Typical,
Typical Impedance, or Differential Spacing.

Constraint Manager User's Manual, X-ENTP VX.2.8 395

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Trace and Via Properties

Table A-1. Trace and Via Property Constraints Summary (cont.)

Constraint Description
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.
Differential Via Spacing Defines the required parallel distance between vias that
comprise a differential pair. You can define this value for
individual board layers and net classes.

396 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Index

Index
Displays the layer number for a board layer.
The tool also displays this constraint on the Clearances page and Z-Axis Clearances page.

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
Specifying Trace Constraints

Constraint Manager User's Manual, X-ENTP VX.2.8 397

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
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.
Note
If Type is Flooded Signal, the Typical Impedance constraint is calculated based on the test
width and the Trace to Plane constraint for that layer in the (Master) scheme's (Default
Rule).

Constraint Type
Reference

Example
Signal

Related Topics
Specifying Trace Constraints

398 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Display Pattern (Trace and Via Properties)

Display Pattern (Trace and Via Properties)

Defines the display pattern for a net class. “(None)” is the default value. Each pattern is a unique
combination of a color and hatching style that you can then apply to the appearance of nets in
the schematic or layout tool to make them more easily recognizable.
Figure A-1. Display Pattern

Note
You can create and assign display patterns on both the Trace & Via Properties page and the
Nets page. Patterns you create on one page are assignable on either page.

Constraint Type
Modifiable

Related Topics
Display Pattern Definition

Constraint Manager User's Manual, X-ENTP VX.2.8 399

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
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.

Supported Design Components

The layout system supports usage of this constraint during high-speed routing (HSR) and
through Hazards in the AutoActive environment. For more information, see “Supported Design
Components” on page 394.

Constraint Type
Modifiable

Example
(default)

Related Topics
Specifying Trace Constraints

400 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
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.
Note
You can only set this constraint in the (Master) scheme. All other schemes display the Route
values you define in the (Master) scheme.

Supported Design Components

The layout system supports usage of this constraint during high-speed routing (HSR) and
through Hazards in the AutoActive environment. For more information, see “Supported Design
Components” on page 394.

Constraint Type
Modifiable

Related Topics
Specifying Trace Constraints

Constraint Manager User's Manual, X-ENTP VX.2.8 401

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
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-2. Trace Width Minimum

Supported Design Components

The layout system supports usage of this constraint during high-speed routing (HSR) and
through Hazards in the AutoActive environment. For more information, see “Supported Design
Components” on page 394.

Constraint Type
Modifiable

Limits and Defaults

Minimum Maximum Default

Value Value Value
0.01 th 1000 th 10 th

Example
8 mil

Related Topics
Specifying Trace Constraints
Trace Width Expansion
Trace Width Typical

402 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
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-3. Trace Width Typical

Supported Design Components

The layout system supports usage of this constraint during high-speed routing (HSR) and
through Hazards in the AutoActive environment. For more information, see “Supported Design
Components” on page 394.

Constraint Type
Modifiable

Limits and Defaults

Minimum Maximum Default

Value Value Value
0.01 th 1000 th 10 th

Example
9 mil

Related Topics
Specifying Trace Constraints
Trace Width Expansion
Trace Width Minimum

Constraint Manager User's Manual, X-ENTP VX.2.8 403

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Trace Width Expansion

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.
Figure A-4. Trace Width Expansion

Supported Design Components

The layout system supports usage of this constraint during high-speed routing (HSR) and
through Hazards in the AutoActive environment. For more information, see “Supported Design
Components” on page 394.

Constraint Type
Modifiable

Limits and Defaults

Minimum Maximum Default

Value Value Value
0.01 th 1000 th 10 th

Example
10 mil

Related Topics
Specifying Trace Constraints
Trace Width Minimum
Trace Width Typical

404 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Typical Impedance

Typical Impedance
Defines signal impedance for the Trace Width Typical constraint. If you type a value into the
Trace Width Typical cell, the tool calculates impedance at this width and places the result into
the Typical Impedance cell.
Note
You cannot input or calculate Typical Impedance for traces that are on plane layers. To
indicate this, Constraint Manager grays out the cell and leaves it empty. And, in order for
the tool to calculate this constraint, your board stackup must include at least one plane layer.

If you adjust this constraint, the tool always updates Trace Width Typical unless the design does
not have a valid stackup or the trace is on a plane layer.

When calculating impedance, the tool includes these stackup properties as necessary:

• Layer thickness
• Dielectric constants
• Position of plane layers
• Copper thickness for metal layers

Supported Design Components

The layout system supports usage of this constraint during high-speed routing (HSR) and
through Hazards. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

Related Topics
Specifying Trace Constraints
Trace Width Typical

Constraint Manager User's Manual, X-ENTP VX.2.8 405

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Differential Typical Impedance

Differential Typical Impedance

Defines signal impedance for trace segments that are part of a differential pair. The tool
automatically calculates and updates this value if you modify Trace Width Typical, Typical
Impedance, or Differential Spacing.
Note
You cannot input or calculate Differential Typical Impedance for traces that are on plane
layers. To indicate this, Constraint Manager grays out the cell and leaves it empty. And, in
order for the tool to calculate this constraint, your board stackup must include at least one plane
layer.

If you modify Differential Typical Impedance, the tool updates Differential Spacing.

When calculating impedance, the tool includes these stackup properties as necessary:

• Layer thickness
• Dielectric constants
• Position of plane layers
• Copper thickness for metal layers

Supported Design Components

The layout system supports usage of this constraint during high-speed routing (HSR) and
through Hazards. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

Related Topics
Specifying Trace Constraints
Trace Width Typical
Typical Impedance
Differential Spacing

406 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Differential Spacing

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.
Figure A-5. 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.

Supported Design Components

The layout system supports usage of this constraint during high-speed routing (HSR) and
through Hazards. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

Limits and Defaults

Minimum Maximum Default

Value Value Value
1 nm 1 in 10 th

Example
0.5 mm

Related Topics
Specifying Trace Constraints
Trace Width Minimum
Differential Via Spacing

Constraint Manager User's Manual, X-ENTP VX.2.8 407

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Differential Via Spacing

Differential Via Spacing

Defines the required parallel distance between vias that comprise a differential pair. You can
define this value for individual board layers and net classes.
Figure A-6. Differential Via Spacing

Supported Design Components

The layout system supports usage of this constraint during high-speed routing (HSR) and
through Hazards. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

Limits and Defaults

Minimum Maximum Default

Value Value Value
1 nm 1 in N/A

Example
100 th

Related Topics
Differential Spacing

408 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
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

Constraint Description
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 Plane Defines the minimum clearance distance between traces and
planes. 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
and clearance rules.

Constraint Manager User's Manual, X-ENTP VX.2.8 409

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Clearances

Table A-2. Clearance Constraints Summary (cont.)

Constraint Description
Pad To Plane Defines the minimum clearance distance between pads and
planes. You can define this value for board layers and
clearance rules. This constraint definition includes through-
hole pads and SMD pads.
Via To Via Defines the minimum clearance distance between vias. You
can define this value for board layers and clearance rules.
Via To Plane Defines the minimum clearance distance between vias and
planes. You can define this value for board layers and
clearance rules.
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.
Plane To Plane Defines the minimum clearance distance between planes.
You can define this value for board layers and clearance
rules.
Embedded Resistor To Defines the minimum clearance distance between the
Trace resistive material of embedded thick-film resistors and
traces. You can define this value for board layers and
clearance rules.
Embedded Resistor To Pad Defines the minimum clearance distance between the
resistive material of embedded thick-film resistors and pads.
You can define this value for board layers and clearance
rules.
Embedded Resistor To Via Defines the minimum clearance distance between the
resistive material of embedded thick-film resistors and vias.
You can define this value for board layers and clearance
rules.
Embedded Resistor To Defines the minimum clearance distance between the
Resistor resistive material of embedded thick-film resistors. You can
define this value for board layers and clearance rules.
EP Mask To Trace Defines the minimum clearance distance between the
production mask of embedded thin-film resistors and traces.
You can define this value for board layers and clearance
rules.
EP Mask To Pad Defines the minimum clearance distance between the
production mask of embedded thin-film resistors and pads.
You can define this value for board layers and clearance
rules.

410 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Clearances

Table A-2. Clearance Constraints Summary (cont.)

Constraint Description
EP Mask To Via Defines the minimum clearance distance between the
production mask of embedded thin-film resistors and vias.
You can define this value for board layers and clearance
rules.
EP Mask To Resistor Defines the minimum clearance distance between the
production mask of embedded thin-film resistors and the
resistive material of embedded thick-film resistors. You can
define this value for board layers and clearance rules.
Bond Finger To Bond Defines the minimum clearance distance between bonding
Finger fingers. You can define this value for board layers and
clearance rules.
Bond Finger To Trace Defines the minimum clearance distance between bonding
fingers and traces. You can define this value for board layers
and clearance rules.
Bond Finger To Pad Defines the minimum clearance distance between bonding
fingers and through-hole pads. You can define this value for
board layers and clearance rules.
Bond Finger To Via Defines the minimum clearance distance between bonding
fingers and vias. You can define this value for board layers
and clearance rules.
Bond Finger To Plane Defines the minimum clearance distance between bonding
fingers and planes. You can define this value for board layers
and clearance rules.
Bond Finger To SMD Pad Defines the minimum clearance distance between bonding
fingers and the pads of surface mount devices. You can
define this value for board layers and clearance rules.

Constraint Manager User's Manual, X-ENTP VX.2.8 411

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Index

Index
Displays the layer number for a board layer.
The tool also displays this constraint on the Trace & Via Properties page and Z-Axis Clearances
page.

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
Creating Clearance Rule Sets
Assigning Class-To-Class Clearance Rules

412 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
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
Creating Clearance Rule Sets
Assigning Class-To-Class Clearance Rules

Constraint Manager User's Manual, X-ENTP VX.2.8 413

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Trace To Trace

Trace To Trace
Defines the minimum clearance distance between trace segments. You can define this value for
board layers and clearance rules.
Figure A-7. Trace To Trace

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

Limits and Defaults

Minimum Maximum Default

Value Value Value
1 nm 1 in 10 th

Example
20 th

Related Topics
Creating Clearance Rule Sets
Assigning Class-To-Class Clearance Rules

414 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
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-8. Trace To Pad

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

Limits and Defaults

Minimum Maximum Default

Value Value Value
1 nm 1 in 10 th

Example
12 th

Related Topics
Creating Clearance Rule Sets
Assigning Class-To-Class Clearance Rules

Constraint Manager User's Manual, X-ENTP VX.2.8 415

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Trace To Via

Trace To Via
Defines the minimum clearance distance between traces and vias. You can define this value for
board layers and clearance rules.
Figure A-9. Trace To Via

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

Limits and Defaults

Minimum Maximum Default

Value Value Value
1 nm 1 in 10 th

Example
8 th

Related Topics
Creating Clearance Rule Sets
Assigning Class-To-Class Clearance Rules

416 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Trace To Plane

Trace To Plane
Defines the minimum clearance distance between traces and planes. You can define this value
for board layers and clearance rules.
Figure A-10. Trace To Plane

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

Limits and Defaults

Minimum Maximum Default

Value Value Value
1 nm 1 in 10 th

Example
20 th

Related Topics
Creating Clearance Rule Sets
Assigning Class-To-Class Clearance Rules

Constraint Manager User's Manual, X-ENTP VX.2.8 417

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
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-11. Trace To SMD Pad

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

Limits and Defaults

Minimum Maximum Default

Value Value Value
1 nm 1 in 10 th

Example
15 th

Related Topics
Defining SMD Clearance Rules
Assigning Class-To-Class Clearance Rules

418 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
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-12. Pad To Pad

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

Limits and Defaults

Minimum Maximum Default

Value Value Value
1 nm 1 in 10 th

Example
15 th

Related Topics
Creating Clearance Rule Sets
Assigning Class-To-Class Clearance Rules

Constraint Manager User's Manual, X-ENTP VX.2.8 419

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Pad To Via

Pad To Via
Defines the minimum clearance distance between through-hole pads and vias. You can define
this value for board layers and clearance rules.
Figure A-13. Pad To Via

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

Limits and Defaults

Minimum Maximum Default

Value Value Value
1 nm 1 in 10 th

Example
8 th

Related Topics
Creating Clearance Rule Sets
Assigning Class-To-Class Clearance Rules

420 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Pad To Plane

Pad To Plane
Defines the minimum clearance distance between pads and planes. You can define this value for
board layers and clearance rules. This constraint definition includes through-hole pads and
SMD pads.
Figure A-14. Pad To Plane

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

Limits and Defaults

Minimum Maximum Default

Value Value Value
1 nm 1 in 10 th

Example
20 th

Related Topics
Creating Clearance Rule Sets
Assigning Class-To-Class Clearance Rules

Constraint Manager User's Manual, X-ENTP VX.2.8 421

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
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-15. Via To Via

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

Limits and Defaults

Minimum Maximum Default

Value Value Value
1 nm 1 in 10 th

Example
15 th

Related Topics
Creating Clearance Rule Sets
Assigning Class-To-Class Clearance Rules

422 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Via To Plane

Via To Plane
Defines the minimum clearance distance between vias and planes. You can define this value for
board layers and clearance rules.
Figure A-16. Via To Plane

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

Limits and Defaults

Minimum Maximum Default

Value Value Value
1 nm 1 in 10 th

Example
20 th

Related Topics
Creating Clearance Rule Sets
Assigning Class-To-Class Clearance Rules

Constraint Manager User's Manual, X-ENTP VX.2.8 423

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Via To SMD Pad

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.
Figure A-17. Via To SMD Pad

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

Limits and Defaults

Minimum Maximum Default

Value Value Value
1 nm 1 in 10 th

Example
15 th

Related Topics
Defining SMD Clearance Rules
Assigning Class-To-Class Clearance Rules

424 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Plane To Plane

Plane To Plane
Defines the minimum clearance distance between planes. You can define this value for board
layers and clearance rules.
Note
In order to accurately check this rule using Batch DRC in your layout software, you must set
any “Static” planes to “Dynamic” in that tool. Because the layout software regards static
planes as archived, it uses Plane To Plane values assigned at the time a plane was put into static
mode instead of the values of the assigned scheme.

Figure A-18. Plane To Plane

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

Limits and Defaults

Minimum Maximum Default

Value Value Value
1 nm 1 in 10 th

Example
20 th

Related Topics
Creating Clearance Rule Sets
Assigning Class-To-Class Clearance Rules

Constraint Manager User's Manual, X-ENTP VX.2.8 425

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Embedded Resistor To Trace

Embedded Resistor To Trace

Defines the minimum clearance distance between the resistive material of embedded thick-film
resistors and traces. You can define this value for board layers and clearance rules.
Figure A-19. Embedded Resistor To Trace

Prerequisites
• You acquired an Xpedition Embedded Passive license in Xpedition Layout.

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

Limits and Defaults

Minimum Maximum Default

Value Value Value
1 nm 1 in 10 th

Example
15 th

Related Topics
Defining Embedded Resistor Clearance Rules
Assigning Class-To-Class Clearance Rules

426 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Embedded Resistor To Pad

Embedded Resistor To Pad

Defines the minimum clearance distance between the resistive material of embedded thick-film
resistors and pads. You can define this value for board layers and clearance rules.
Figure A-20. Embedded Resistor To Pad

Prerequisites
• You acquired an Xpedition Embedded Passive license in Xpedition Layout.

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

Limits and Defaults

Minimum Maximum Default

Value Value Value
1 nm 1 in 10 th

Example
15 th

Related Topics
Defining Embedded Resistor Clearance Rules
Assigning Class-To-Class Clearance Rules

Constraint Manager User's Manual, X-ENTP VX.2.8 427

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Embedded Resistor To Via

Embedded Resistor To Via

Defines the minimum clearance distance between the resistive material of embedded thick-film
resistors and vias. You can define this value for board layers and clearance rules.
Figure A-21. Embedded Resistor To Via

Prerequisites
• You acquired an Xpedition Embedded Passive license in Xpedition Layout.

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

Limits and Defaults

Minimum Maximum Default

Value Value Value
1 nm 1 in 10 th

Example
15 th

Related Topics
Defining Embedded Resistor Clearance Rules
Assigning Class-To-Class Clearance Rules

428 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Embedded Resistor To Resistor

Embedded Resistor To Resistor

Defines the minimum clearance distance between the resistive material of embedded thick-film
resistors. You can define this value for board layers and clearance rules.
Figure A-22. Embedded Resistor To Resistor

Prerequisites
• You acquired an Xpedition Embedded Passive license in Xpedition Layout.

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

Limits and Defaults

Minimum Maximum Default

Value Value Value
1 nm 1 in 10 th

Example
15 th

Related Topics
Defining Embedded Resistor Clearance Rules
Assigning Class-To-Class Clearance Rules

Constraint Manager User's Manual, X-ENTP VX.2.8 429

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
EP Mask To Trace

EP Mask To Trace
Defines the minimum clearance distance between the production mask of embedded thin-film
resistors and traces. You can define this value for board layers and clearance rules.
Figure A-23. EP Mask To Trace

Prerequisites
• You acquired an Xpedition Embedded Passive license in Xpedition Layout.

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

Limits and Defaults

Minimum Maximum Default

Value Value Value
1 nm 1 in 10 th

Example
15 th

Related Topics
Defining Embedded Resistor Clearance Rules
Assigning Class-To-Class Clearance Rules

430 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
EP Mask To Pad

EP Mask To Pad
Defines the minimum clearance distance between the production mask of embedded thin-film
resistors and pads. You can define this value for board layers and clearance rules.
Figure A-24. EP Mask To Pad

Prerequisites
• You acquired an Xpedition Embedded Passive license in Xpedition Layout.

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

Limits and Defaults

Minimum Maximum Default

Value Value Value
1 nm 1 in 10 th

Example
15 th

Related Topics
Defining Embedded Resistor Clearance Rules
Assigning Class-To-Class Clearance Rules

Constraint Manager User's Manual, X-ENTP VX.2.8 431

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
EP Mask To Via

EP Mask To Via
Defines the minimum clearance distance between the production mask of embedded thin-film
resistors and vias. You can define this value for board layers and clearance rules.
Figure A-25. EP Mask To Via

Prerequisites
• You have acquired an Xpedition Embedded Passive license in Xpedition Layout.

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

Limits and Defaults

Minimum Maximum Default

Value Value Value
1 nm 1 in 10 th

Example
15 th

Related Topics
Defining Embedded Resistor Clearance Rules
Assigning Class-To-Class Clearance Rules

432 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
EP Mask To Resistor

EP Mask To Resistor
Defines the minimum clearance distance between the production mask of embedded thin-film
resistors and the resistive material of embedded thick-film resistors. You can define this value
for board layers and clearance rules.
Figure A-26. EP Mask To Resistor

Prerequisites
• You acquired an Xpedition Embedded Passive license in Xpedition Layout.

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

Limits and Defaults

Minimum Maximum Default

Value Value Value
1 nm 1 in 10 th

Example
15 th

Related Topics
Defining Embedded Resistor Clearance Rules
Assigning Class-To-Class Clearance Rules

Constraint Manager User's Manual, X-ENTP VX.2.8 433

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Bond Finger To Bond Finger

Bond Finger To Bond Finger

Defines the minimum clearance distance between bonding fingers. You can define this value for
board layers and clearance rules.
Figure A-27. Bond Finger To Bond Finger

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

434 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Bond Finger To Bond Finger

Limits and Defaults

Minimum Maximum Default

Value Value Value
1 nm 1 in 10 th

Example
10 th

Related Topics
Defining Bond Finger Clearance Rules

Constraint Manager User's Manual, X-ENTP VX.2.8 435

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Bond Finger To Trace

Bond Finger To Trace

Defines the minimum clearance distance between bonding fingers and traces. You can define
this value for board layers and clearance rules.
Figure A-28. Bond Finger To Trace

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

436 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Bond Finger To Trace

Limits and Defaults

Minimum Maximum Default

Value Value Value
1 nm 1 in 10 th

Example
30 th

Related Topics
Defining Bond Finger Clearance Rules

Constraint Manager User's Manual, X-ENTP VX.2.8 437

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Bond Finger To Pad

Bond Finger To Pad

Defines the minimum clearance distance between bonding fingers and through-hole pads. You
can define this value for board layers and clearance rules.
Figure A-29. Bond Finger To Pad

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

438 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Bond Finger To Pad

Limits and Defaults

Minimum Maximum Default

Value Value Value
1 nm 1 in 10 th

Example
40 th

Related Topics
Defining Bond Finger Clearance Rules

Constraint Manager User's Manual, X-ENTP VX.2.8 439

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Bond Finger To Via

Bond Finger To Via

Defines the minimum clearance distance between bonding fingers and vias. You can define this
value for board layers and clearance rules.
Figure A-30. Bond Finger To Via

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

440 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Bond Finger To Via

Limits and Defaults

Minimum Maximum Default

Value Value Value
1 nm 1 in 10 th

Example
30 th

Related Topics
Defining Bond Finger Clearance Rules

Constraint Manager User's Manual, X-ENTP VX.2.8 441

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Bond Finger To Plane

Bond Finger To Plane

Defines the minimum clearance distance between bonding fingers and planes. You can define
this value for board layers and clearance rules.
Figure A-31. Bond Finger To Plane

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

442 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Bond Finger To Plane

Limits and Defaults

Minimum Maximum Default

Value Value Value
1 nm 1 in 10 th

Example
12 th

Related Topics
Defining Bond Finger Clearance Rules

Constraint Manager User's Manual, X-ENTP VX.2.8 443

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Bond Finger To SMD Pad

Bond Finger To SMD Pad

Defines the minimum clearance distance between bonding fingers and the pads of surface
mount devices. You can define this value for board layers and clearance rules.

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

Limits and Defaults

Minimum Maximum Default

Value Value Value
1 nm 1 in 10 th

Example
30 th

Related Topics
Defining Bond Finger Clearance Rules

444 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Z-Axis Clearances

Z-Axis Clearances
Refer to the z-axis clearance constraint reference topics that follow. You access these
constraints through the Z-Axis Clearances spreadsheet page.
Note
By default, the router does not use z-axis clearance constraints, even those defined in the
(Defaut Z-Axis Rule), between any net classes. In order to use your values for these
constraints, you must assign z-axis clearance rule sets between specific net classes.

Table A-3. Z-Axis Clearance Constraints Summary

Constraint Description
Index Displays the layer number for a board layer. The tool also
displays this constraint on the Trace & Via Properties page
and Clearances page.
Trace To Trace Defines the minimum clearance distance between trace
segments located on different signal layers. 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 located on different signal layers. You can
define this value for board layers and clearance rules.
Trace To Via Defines the minimum clearance distance between traces and
vias located on different signal layers. You can define this
value for board layers and clearance rules.
Trace To Plane Defines the minimum clearance distance between traces and
planes located on different signal layers. You can define this
value for board layers and clearance rules.
Trace To SMD Pad Defines the minimum clearance distance between the pads of
surface mount devices and traces located on different signal
layers. You can define this value for board layers and
clearance rules.

Constraint Manager User's Manual, X-ENTP VX.2.8 445

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Index

Index
Displays the layer number for a board layer. The tool also displays this constraint on the Trace
& Via Properties page and Clearances page.
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
Creating Z-Axis Clearance Rule Sets
Assigning Z-Axis Class-To-Class Clearance Rules

446 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Trace To Trace

Trace To Trace
Defines the minimum clearance distance between trace segments located on different signal
layers. You can define this value for board layers and clearance rules.
Figure A-32. Trace To Trace

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

Limits

Minimum Maximum
Value Value
1 nm 1 in

Example
10 th

Related Topics
Creating Z-Axis Clearance Rule Sets
Assigning Z-Axis Class-To-Class Clearance Rules

Constraint Manager User's Manual, X-ENTP VX.2.8 447

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Trace To Pad

Trace To Pad
Defines the minimum clearance distance between traces and through-hole pads located on
different signal layers. You can define this value for board layers and clearance rules.
Figure A-33. Trace To Pad

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

Limits

Minimum Maximum
Value Value
1 nm 1 in

Example
12 th

Related Topics
Creating Z-Axis Clearance Rule Sets
Assigning Z-Axis Class-To-Class Clearance Rules

448 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Trace To Via

Trace To Via
Defines the minimum clearance distance between traces and vias located on different signal
layers. You can define this value for board layers and clearance rules.
Figure A-34. Trace To Via

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

Limits

Minimum Maximum
Value Value
1 nm 1 in

Example
8 th

Related Topics
Creating Z-Axis Clearance Rule Sets
Assigning Z-Axis Class-To-Class Clearance Rules

Constraint Manager User's Manual, X-ENTP VX.2.8 449

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Trace To Plane

Trace To Plane
Defines the minimum clearance distance between traces and planes located on different signal
layers. You can define this value for board layers and clearance rules.
Figure A-35. Trace To Plane

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

Limits

Minimum Maximum
Value Value
1 nm 1 in

Example
20 th

Related Topics
Creating Z-Axis Clearance Rule Sets
Assigning Z-Axis Class-To-Class Clearance Rules

450 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Trace To SMD Pad

Trace To SMD Pad

Defines the minimum clearance distance between the pads of surface mount devices and traces
located on different signal layers. You can define this value for board layers and clearance rules.
Figure A-36. Trace To SMD Pad

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Constraint Type
Modifiable

Limits

Minimum Maximum
Value Value
1 nm 1 in

Example
15 th

Related Topics
Defining SMD Clearance Rules
Assigning Z-Axis Class-To-Class Clearance Rules

Constraint Manager User's Manual, X-ENTP VX.2.8 451

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Nets

Nets
Refer to the net constraint reference topics that follow. You access these constraints through the
Nets spreadsheet page.

Table A-4. Net Constraints Summary

Constraint Description
Hierarchical Path Displays the hierarchical path to the object within the design.
# Pins Displays the number of pins that comprise the 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.
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.
Bus Defines the constraint class as a bus. You should limit nets
within the constraint class to only the nets that comprise the
bus.
Net Class Defines the name of the net class to which the net should
belong.
Display Pattern (Nets) Defines the display pattern for a net or group of nets.
“(None)” is the default value. You can define this value for
individual nets, differential pairs, and constraint classes.
Template Name Optionally, defines the constraint template to which the net is
assigned. You can define this value for individual nets and
constraint classes.
Template Status Displays the synchronization status of the net with regard to
the current values stored in the constraint template.
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.
Topology Ordered For Topology Type Custom or Complex, displays whether
the custom topology type has undergone netline ordering,
which is required for each user-specific topology type.
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.

452 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Nets

Table A-4. Net Constraints Summary (cont.)

Constraint Description
# 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.
# Test Points Required Defines the number of test points a net must have, if any are
required. You can define this value for individual nets and
constraint classes.
Backdrill Defines whether a net’s vias are suitable for backdrilling,
which is a process to remove the unused portion of a plated-
through hole via. You can define this value for individual
nets, differential pairs, and constraint classes.
Restricted Layer Length Defines the maximum trace length that the layout tool can
Max External route a net on an external restricted board layer. You can
define this value for individual nets and constraint classes.
Restricted Layer Length Defines the maximum trace length that the layout tool can
Max Internal route a net on an internal restricted board layer. You can
define this value for individual nets and constraint classes.
From To Constraints Layer Defines the board layer on which to route a from-to for a
non-differential net that uses Topology Type Custom. You
can define this value for each from-to that is part of a non-
differential net.
From To Constraints Trace Optionally defines the trace width to which to route a from-
Width to. You can only define this value for non-differential nets
that use a custom Topology Type. You also must define
From To Constraints Layer before you can type a value for
this constraint. You can define this value for each from-to.
From To Constraints Z0 Displays an impedance calculation based on the trace width
override value defined in From To Constraints Trace Width.
Length or TOF Delay Type Defines the type for a net, which you can constrain
electrically (TOF) or physically (Length). You can define
this value for individual nets, pin pairs, differential pairs, and
constraint classes.
Length or TOF Delay Min Defines the minimum acceptable physical routing length or
signal propagation delay between design connections. You
can define this value for individual nets, pin pairs,
differential pairs, and constraint classes.
Length or TOF Delay Max Defines the maximum acceptable physical routing length or
signal propagation delay between design connections. You
can define this value for individual nets, pin pairs,
differential pairs, and constraint classes.

Constraint Manager User's Manual, X-ENTP VX.2.8 453

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Nets

Table A-4. Net Constraints Summary (cont.)

Constraint Description
Length or TOF Delay Displays the Manhattan net length. The tool shows the actual
Manhattan length in the Length or TOF Delay Actual cell if the net is
routed.
Length or TOF Delay Min Displays the straight-line length between two pin pairs if
Length both components are placed. The tool replaces this length
with Length or TOF Delay Actual if the net is routed.
Length or TOF Delay Defines a match character or string (for example, a) you can
Match use to group nets for similar length or time of flight delay
routing. You can define this value for individual nets, pin
pairs, and differential pairs.
Length or TOF Delay Tol Introduces a tolerance range around the length or delay
requirements for nets that duplicate a Length or TOF Delay
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 or TOF Delay 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 or TOF Delay Tol values when it calculates
this delta value.
Length or TOF Delay Displays the range of length or time of flight actuals for all
Range nets and/or constraint classes that are part of the same match
group.
Formulas Formula Defines a formula that you can use to create length or delay
relationships between nets and pin pairs. You can define this
value for individual nets and pin pairs.
Formulas Violation Displays formula violation information based on the
requirements of the Formulas Formula constraint.
Static Low Overshoot Max Defines the maximum low DC voltage (minimum) that a
buffer can withstand without permanent damage to the
buffer. You can define this value for individual nets,
differential pairs, and constraint classes. An IBIS model
defines this value through the S_overshoot_low keyword.
Static High Overshoot Max Defines the maximum high DC voltage that a buffer can
withstand without permanent damage to the buffer. You can
define this value for individual nets, differential pairs, and
constraint classes. An IBIS model defines this value through
the S_overshoot_high keyword.

454 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Nets

Table A-4. Net Constraints Summary (cont.)

Constraint Description
Dynamic Low Overshoot Defines an available, smaller low operating voltage (below
Max minimum) limit for the signal that is to not exceed a specific
duration. This voltage limit should not be met or exceeded,
but allow for the signal to go lower than Static Low
Overshoot Max, while never equaling Dynamic Low
Overshoot Max.
Dynamic High Overshoot Defines an available, larger high operating voltage (above
Max maximum) limit for the signal that is to not exceed a specific
duration. This voltage limit should not be met or exceeded,
but allow for the signal to go higher than Static High
Overshoot Max, while never equaling Dynamic High
Overshoot Max.
Ringback Margin High Min Defines the minimum allowed difference between the high
switching threshold (Vinh) and a ringback wave. You can
define this value for individual nets, differential pairs, and
constraint classes.
Ringback Margin Low Min Defines the minimum allowed difference between the low
switching threshold (Vinl) and a ringback wave. You can
define this value for individual nets, differential pairs, and
constraint classes.
Non-Monotonic Edge Defines a non-monotonicity requirement for the rising edge,
falling edge, or both signal edges. You can define this value
for individual nets, differential pairs, and constraint classes.
Single Ended Characteristic Defines the single-ended characteristic impedance for a net’s
Impedance Value traces. You can define this value for individual nets,
differential pairs, and constraint classes.
Single Ended Characteristic Introduces a tolerance around Single Ended Characteristic
Impedance Tol Impedance Value. You can define this value for individual
nets, differential pairs, and constraint classes.
Simulated Delay Edge Defines the simulated delay edge or edges to constrain. You
can define this value for individual nets, differential pairs,
pin pairs, and constraint classes.
Simulated Delay Min Defines the minimum acceptable simulated delay time for the
Simulated Delay Edge value (for example, Rise or Fall). You
can define this value for individual nets, differential pairs,
pin pairs, and constraint classes.
Simulated Delay Max Defines the maximum acceptable simulated delay time for
the Simulated Delay Edge value (for example, Rise:Fall or
Both). You can define this value for individual nets,
differential pairs, pin pairs, and constraint classes.

Constraint Manager User's Manual, X-ENTP VX.2.8 455

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Nets

Table A-4. Net Constraints Summary (cont.)

Constraint Description
Simulated Delay Max Defines a maximum acceptable range of difference between
Range Simulated Delay Actual Min and Simulated Delay Actual
Max for the Simulated Delay Edge value (for example, Fall
or Both). You can define this value for individual nets,
differential pairs, pin pairs, and constraint classes.
Simulated Delay Match To Defines the hierarchical level of matching for the Simulated
Delay Match constraint. You can match to the constraint
class, net, or pin-pair level. You can define this value for
individual nets, differential pairs, pin pairs, and constraint
classes.
Simulated Delay Match Defines the electrical net, pin pair, or constraint class to
which to match Simulated Delay constraints (for example,
Simulated Delay Edge and Simulated Delay Min). You can
define this value for individual nets, differential pairs, pin
pairs, and constraint classes.
Simulated Delay Offset Introduces a positive or negative offset (for example, 50 ns or
-50 ns) from Simulated Delay Min and Simulated Delay Max
if matching the simulated delay of an electrical net or
constraint class (Simulated Delay Match). You can define
this value for individual nets, differential pairs, pin pairs, and
constraint classes.
Simulated Delay Tol Introduces a tolerance range (for example, 5 ns) around
Simulated Delay Min and Simulated Delay Max if matching
the simulated delay of an electrical net or constraint class
(Simulated Delay Match). You can define this value for
individual nets, differential pairs, pin pairs, and constraint
classes.
Differential Pair Tol Max Defines the maximum allowed difference between nets in a
differential pair.
Differential Pair Phase Tol Defines how far out of phase the signals of the differential
Max pair are allowed to get. You can define this value for
differential pairs and constraint classes.
Differential Pair Phase Tol Defines how much further the two signals can continue
Distance Max running out of phase after exceeding the Differential Pair
Phase Tol Max constraint. You can define this value for
differential pairs and constraint classes.
Differential Pair Phase Tol Indicates whether both Differential Pair Phase Tol Max and
Actual Differential Pair Phase Tol Distance Max constraints are
being exceeded. This actual only shows the word “Violation”
if both constraints are exceeded. It reports “No Violation”
otherwise.

456 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Nets

Table A-4. Net Constraints Summary (cont.)

Constraint Description
Convergence Tolerance Defines the maximum allowed difference in trace length
Max from pads to the point where traces start routing differentially
at the Differential Spacing constraint. You can define this
value for each differential pair.
Distance to Convergence Defines the maximum distance that differential traces are
Max allowed to route before they converge as a differential pair.
The distance value is the combination of segment lengths.
Convergence is met when traces start routing at the
Differential Spacing constraint. You can define this value for
differential pairs and constraint classes.
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.
Differential Impedance Defines the target differential impedance. You can define
Target this value for each differential pair. If the layout tool can not
meet this value, it uses Differential Spacing. The router does
not obey Differential Impedance Target.
Differential Impedance Introduces a tolerance range around Differential Impedance
Tolerance Target. You can define this value for each differential pair.
I/O Standard Defines the technology standard for an FPGA signal net. You
can define this value for individual nets and constraint
classes.
Power Net Constraints Defines the operating voltage for a power-supply net. You
Supply Voltage can define this value for each power-supply net.
Power Net Constraints Max Defines the maximum acceptable decrease in voltage from
Voltage Drop Power Net Constraints Supply Voltage. You can define this
value for individual power-supply nets and constraint
classes.
Power Net Constraints Max Defines the maximum acceptable current that can flow across
Current Density a power-supply net structure (such as an area fill or trace).
You can define this value for individual power-supply nets
and constraint classes.

Constraint Manager User's Manual, X-ENTP VX.2.8 457

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Nets

Table A-4. Net Constraints Summary (cont.)

Constraint Description
Power Net Constraints Max Defines the maximum acceptable current for vias connected
Via Current to power-supply nets. You can define this value for
individual power-supply nets and constraint classes.

458 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Hierarchical Path

Hierarchical Path
Displays the hierarchical path to the object within the design.

Nets Spreadsheet Group

All

Constraint Type
Reference

Example
sheet1

Related Topics
Net Constraint Definition

Constraint Manager User's Manual, X-ENTP VX.2.8 459

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
# Pins

# Pins
Displays the number of pins that comprise the net.

Nets Spreadsheet Group

Net Properties, Power Nets, and All

Constraint Type
Reference

Example
2

Related Topics
Net Constraint Definition

460 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
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.

Nets Spreadsheet Group

Power Nets and All

Constraint Type
Modifiable

Related Topics
Power-Supply Net and Constraint Definition
Analog
Power Net Constraints Supply Voltage
Power Net Constraints Max Voltage Drop
Power Net Constraints Max Current Density
Power Net Constraints Max Via Current

Constraint Manager User's Manual, X-ENTP VX.2.8 461

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
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.

Nets Spreadsheet Group

Net Properties, Power Nets, and All

Constraint Type
Modifiable

Related Topics
Overview of Electrical Nets and Physical Nets in Constraint Manager
Specifying General Net Constraints

462 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Bus

Bus
Defines the constraint class as a bus. You should limit nets within the constraint class to only
the nets that comprise the bus.
The layout tool uses the Bus constraint to identify which constraint classes it should consider for
bus planning and routing capabilities.

Nets Spreadsheet Group

Net Properties and All

Constraint Type
Modifiable

Related Topics
Specifying General Net Constraints

Constraint Manager User's Manual, X-ENTP VX.2.8 463

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
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.

Nets Spreadsheet Group

Delays and Lengths, Differential Pair Properties, Net Properties, Power Nets, and
All

Constraint Type
Modifiable

Related Topics
Creating Net Classes

464 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Display Pattern (Nets)

Display Pattern (Nets)

Defines the display pattern for a net or group of nets. “(None)” is the default value. You can
define this value for individual nets, differential pairs, and constraint classes.
Each pattern is a unique combination of a color and hatching style that you can then apply to the
appearance of nets in the schematic or layout tool to make them more easily recognizable.

Figure A-37. Display Pattern

Note
You can create and assign display patterns on both the Nets page and the Trace & Via
Properties page. Patterns you create on one page are assignable on either page.

Nets Spreadsheet Group

Differential Pair Properties, Net Properties, Power Nets, and All

Constraint Type
Modifiable

Related Topics
Display Pattern Definition

Constraint Manager User's Manual, X-ENTP VX.2.8 465

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Template Name

Template Name
Optionally, defines the constraint template to which the net is assigned. You can define this
value for individual nets and constraint classes.

Nets Spreadsheet Group

Template and All

Constraint Type
Modifiable

Related Topics
Creating Constraint Templates to Capture Net Constraints

466 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Template Status

Template Status
Displays the synchronization status of the net with regard to the current values stored in the
constraint template.
If one or more constraints values of a constraint template are modified after it was assigned to
one or more nets, the Template Status cell indicates that the net no longer includes the latest
template values.

Nets Spreadsheet Group

Template and All

Constraint Type
Reference

Related Topics
Updating Nets With Constraint Template Changes

Constraint Manager User's Manual, X-ENTP VX.2.8 467

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
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.
• TShape — Tells the router to connect pins based upon a T-shaped physical model.

• Star — Instructs the router to connect pins based upon a star-shaped physical model.

• HTree — Tells the router to connect pins based upon a hierarchical tree model.

• Custom/Complex — If creating a custom topology type, you can define Topology

Type as either Custom or Complex. Custom is used for netline ordering that does not
include pin sets. Complex is used for netline ordering that does include pin sets. When
you begin the process of netline ordering a Custom topology, if you add a pin set, its
type is changed to Complex.
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.

If you create a constraint template, the tool includes this constraint.

Supported Design Components

The layout system supports usage of this constraint during high-speed routing (HSR) and
through Hazards in the AutoActive environment. For more information, see “Supported Design
Components” on page 394.

Nets Spreadsheet Group

Net Properties and All

468 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Topology Type

Constraint Type
Modifiable

Related Topics
Topology Specification for Nets and Constraint Classes
Topology Ordered

Constraint Manager User's Manual, X-ENTP VX.2.8 469

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Topology Ordered

Topology Ordered
For Topology Type Custom or Complex, displays whether the custom topology type has
undergone netline ordering, which is required for each user-specific topology type.
If defining netline ordering for a Complex topology, the Topology Ordered cell does not update
to state “Yes” until the next time you launch Constraint Manager from the PCB layout system.
This is because the PCB layout system needs to analyze your usage of pin sets and from-tos to
ensure that the Complex topology is fully ordered.

Tip
Defining the order for all Custom or Complex nets, even those that contains just two pins, is
a good idea. After you define the order, any changes in connectivity cause this constraint to
be set back to “No.” For example, if another engineer adds a pin to a net, Topology Ordered
would be changed from “Yes” to “No,” alerting you to the change in connectivity.

If you create a constraint template, the tool includes this constraint.

Nets Spreadsheet Group

Net Properties and All

Constraint Type
Reference

Related Topics
Manually Defining Netline Ordering (From-Tos) for a Specific Net
Topology Type

470 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
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-38. Stub Length Max

If available, the tool displays the actual value for this constraint in the Actual cell to its right.

If you create a constraint template, the tool includes this constraint.

Supported Design Components

The layout system supports usage of this constraint during high-speed routing (HSR) and
through Hazards in the AutoActive environment. For more information, see “Supported Design
Components” on page 394.

Nets Spreadsheet Group

Net Properties and All

Constraint Type
Modifiable

Constraint Manager User's Manual, X-ENTP VX.2.8 471

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Stub Length Max

Limits and Defaults

Minimum Maximum Default

Value Value
0 1 in 300 th

Related Topics
Topology Specification for Nets and Constraint Classes

472 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
# 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.
If available, the tool displays the actual value for this constraint in the Actual cell to its right.

If you create a constraint template, the tool includes this constraint.

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Nets Spreadsheet Group

Net Properties and All

Constraint Type
Modifiable

Related Topics
Specifying General Net Constraints

Constraint Manager User's Manual, X-ENTP VX.2.8 473

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
# Test Points Required

# Test Points Required

Defines the number of test points a net must have, if any are required. You can define this value
for individual nets and constraint classes.
If available, the tool displays the actual value for this constraint in the Actual cell to its right.

If you create a constraint template, the tool includes this constraint.

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Nets Spreadsheet Group

Net Properties and All

Constraint Type
Modifiable

Related Topics
Specifying General Net Constraints

474 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Backdrill

Backdrill
Defines whether a net’s vias are suitable for backdrilling, which is a process to remove the
unused portion of a plated-through hole via. You can define this value for individual nets,
differential pairs, and constraint classes.
If you create a constraint template, the tool includes this constraint.

Nets Spreadsheet Group

Net Properties and All

Constraint Type
Modifiable

Related Topics
Specifying General Net Constraints

Constraint Manager User's Manual, X-ENTP VX.2.8 475

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Restricted Layer Length Max External

Restricted Layer Length Max External

Defines the maximum trace length that the layout tool can route a net on an external restricted
board layer. You can define this value for individual nets and constraint classes.
If available, the tool displays the actual value for this constraint in the Actual cell to its right.
The actual shows the total wire length.

Restricted layers are those that do not have routing enabled through the Route constraint, which
is located on the Trace & Via Properties spreadsheet page.

Figure A-39. Cross Section of a 6-Layer PCB (External)

An external layer is a surface layer, either the top or bottom layer of the board. In the example,
the PCB has two external layers and four internal layers.

If you create a constraint template, the tool includes this constraint.

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Nets Spreadsheet Group

Net Properties and All

Constraint Type
Modifiable

Related Topics
Specifying General Net Constraints
Restricted Layer Length Max Internal

476 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Restricted Layer Length Max Internal

Restricted Layer Length Max Internal

Defines the maximum trace length that the layout tool can route a net on an internal restricted
board layer. You can define this value for individual nets and constraint classes.
If available, the tool displays the actual value for this constraint in the Actual cell to its right.
The actual shows the total wire length.

Restricted layers are those that do not have routing enabled through the Route constraint, which
is located on the Trace & Via Properties spreadsheet page.

Figure A-40. Cross Section of a 6-Layer PCB (Internal)

An internal layer is a non-surface layer, sandwiched somewhere between the top and bottom
board layers. In the example, the PCB has four internal layers.

If you create a constraint template, the tool includes this constraint.

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Nets Spreadsheet Group

Net Properties and All

Constraint Type
Modifiable

Related Topics
Specifying General Net Constraints
Restricted Layer Length Max External

Constraint Manager User's Manual, X-ENTP VX.2.8 477

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
From To Constraints Layer

From To Constraints Layer

Defines the board layer on which to route a from-to for a non-differential net that uses Topology
Type Custom. You can define this value for each from-to that is part of a non-differential net.
If you create a constraint template, the tool includes this constraint.

Note
In order to apply this constraint, you must enable from-to rows on the spreadsheet. To do so,
from the Filters menu, click Levels, then click to enable FromTo.

Supported Design Components

The layout system supports usage of this constraint during high-speed routing (HSR) and
through Hazards in the AutoActive environment. For more information, see “Supported Design
Components” on page 394.

Nets Spreadsheet Group

Net Properties and All

Constraint Type
Modifiable

Related Topics
Overriding Trace Width Constraints for From-Tos
From To Constraints Trace Width

478 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
From To Constraints Trace Width

From To Constraints Trace Width

Optionally defines the trace width to which to route a from-to. You can only define this value
for non-differential nets that use a custom Topology Type. You also must define From To
Constraints Layer before you can type a value for this constraint. You can define this value for
each from-to.
From To Constraints Trace Width overrides any trace width constraints defined for a net on the
Trace & Via Properties page (for example, Trace Width Typical). If you define From To
Constraints Layer without defining an override width, the tool uses the trace width constraints
of the net class.

If you create a constraint template, the tool includes this constraint.

Note
In order to apply this constraint, you must enable from-to rows on the spreadsheet. To do so,
from the Filters menu, click Levels, then click to enable FromTo.

Supported Design Components

The layout system supports usage of this constraint during high-speed routing (HSR) and
through Hazards in the AutoActive environment. For more information, see “Supported Design
Components” on page 394.

Nets Spreadsheet Group

Net Properties and All

Constraint Type
Modifiable

Limits

Minimum Maximum
Value Value
0.01 th 250 th

Related Topics
Overriding Trace Width Constraints for From-Tos
From To Constraints Z0

Constraint Manager User's Manual, X-ENTP VX.2.8 479

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
From To Constraints Z0

From To Constraints Z0
Displays an impedance calculation based on the trace width override value defined in From To
Constraints Trace Width.
Note
In order to view this constraint, you must enable from-to rows on the spreadsheet. To do so,
from the Filters menu, click Levels, then click to enable FromTo.

Supported Design Components

The layout system supports usage of this constraint during high-speed routing (HSR) and
through Hazards in the AutoActive environment. For more information, see “Supported Design
Components” on page 394.

Nets Spreadsheet Group

Net Properties and All

Constraint Type
Reference

Related Topics
Overriding Trace Width Constraints for From-Tos
From To Constraints Trace Width

480 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Length or TOF Delay Type

Length or TOF Delay Type

Defines the type for a net, which you can constrain electrically (TOF) or physically (Length).
You can define this value for individual nets, pin pairs, differential pairs, and constraint classes.
TOF delay gives you the ability to specify time of flight based upon how long it takes the signal
to propagate through the net. Length gives you the ability to set physical constraints that instruct
the router to keep the net length within a specific range.

If you create a constraint template, the tool includes this constraint.

Supported Design Components

The layout system supports usage of this constraint during high-speed routing (HSR) and
through Hazards in the AutoActive environment. For more information, see “Supported Design
Components” on page 394.

Nets Spreadsheet Group

Delays and Lengths, Differential Pair Properties, and All

Constraint Type
Modifiable

Related Topics
Specifying Length or Delay Rules for Nets
Length or TOF Delay Delta
Length or TOF Delay Max
Length or TOF Delay Min

Constraint Manager User's Manual, X-ENTP VX.2.8 481

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Length or TOF Delay Min

Length or TOF Delay Min

Defines the minimum acceptable physical routing length or signal propagation delay between
design connections. You can define this value for individual nets, pin pairs, differential pairs,
and constraint classes.
The tool does not support the use of constants in this constraint.

Note
Length tuning in the layout tool does not work if the length value exceeds 55 inches. In
board configurations with extremely long traces, ensure that this constraint does not exceed
55 inches.

Figure A-41. Length or TOF Delay Min

If you create a constraint template, the tool includes this constraint.

Length or TOF Delay Actual Calculations

The tool displays the actual value for length or TOF delay in the Actual cell to the right. The
tool gets this value from the layout system and additionally includes pin package length actuals
and via delay actuals, if available. To include via delay actuals, you do so through the Setup
Parameters dialog box of the layout tool. On the Via Definitions tab, define via delays using the
cells of the Delay row.

Supported Design Components

The layout system supports usage of this constraint during high-speed routing (HSR) and
through Hazards in the AutoActive environment. For more information, see “Supported Design
Components” on page 394.

Nets Spreadsheet Group

Delays and Lengths, Differential Pair Properties, and All

Constraint Type
Modifiable

482 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Length or TOF Delay Min

Related Topics
Specifying Length or Delay Rules for Nets
Length or TOF Delay Delta
Length or TOF Delay Max
Length or TOF Delay Type

Constraint Manager User's Manual, X-ENTP VX.2.8 483

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Length or TOF Delay Max

Length or TOF Delay Max

Defines the maximum acceptable physical routing length or signal propagation delay between
design connections. You can define this value for individual nets, pin pairs, differential pairs,
and constraint classes.
The tool does not support the use of constants in this constraint.

Note
Length tuning in the layout tool does not work if the length value exceeds 55 inches. In
board configurations with extremely long traces, ensure that this constraint does not exceed
55 inches.

Figure A-42. Length or TOF Delay Max

If you create a constraint template, the tool includes this constraint.

Length or TOF Delay Actual Calculations

The tool displays the actual value for length or TOF delay in the Actual cell to the right. The
tool gets this value from the layout system and additionally includes pin package length actuals
and via delay actuals, if available. To include via delay actuals, you do so through the Setup
Parameters dialog box of the layout tool. On the Via Definitions tab, define via delays using the
cells of the Delay row.

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%.

Supported Design Components

The layout system supports usage of this constraint during high-speed routing (HSR) and
through Hazards in the AutoActive environment. For more information, see “Supported Design
Components” on page 394.

Nets Spreadsheet Group

Delays and Lengths, Differential Pair Properties, and All

484 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Length or TOF Delay Max

Constraint Type
Modifiable

Related Topics
Specifying Length or Delay Rules for Nets
Length or TOF Delay Delta
Length or TOF Delay Min
Length or TOF Delay Type

Constraint Manager User's Manual, X-ENTP VX.2.8 485

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Length or TOF Delay Manhattan

Length or TOF Delay Manhattan

Displays the Manhattan net length. The tool shows the actual length in the Length or TOF Delay
Actual cell if the net is routed.

Nets Spreadsheet Group

Delays and Lengths and All

Constraint Type
Reference

Related Topics
Specifying Length or Delay Rules for Nets

486 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Length or TOF Delay Min Length

Length or TOF Delay Min Length

Displays the straight-line length between two pin pairs if both components are placed. The tool
replaces this length with Length or TOF Delay Actual if the net is routed.

Nets Spreadsheet Group

Delays and Lengths and All

Constraint Type
Reference

Related Topics
Specifying Length or Delay Rules for Nets

Constraint Manager User's Manual, X-ENTP VX.2.8 487

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Length or TOF Delay Match

Length or TOF Delay Match

Defines a match character or string (for example, a) you can use to group nets for similar length
or time of flight delay routing. You can define this value for individual nets, pin pairs, and
differential pairs.
To duplicate the length or delay of a net row that has a defined match character, type the match
character into the Length or TOF Delay Match cell of the net for which you have not defined
delay.

If you create a constraint template, the tool includes this constraint.

Supported Design Components

The layout system supports usage of this constraint during high-speed routing (HSR) and
through Hazards in the AutoActive environment. For more information, see “Supported Design
Components” on page 394.

Nets Spreadsheet Group

Delays and Lengths and All

Constraint Type
Modifiable

Related Topics
Matching Delay or Length Rules Among Nets
Formulas Formula

488 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Length or TOF Delay Tol

Length or TOF Delay Tol

Introduces a tolerance range around the length or delay requirements for nets that duplicate a
Length or TOF Delay 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.
If you create a constraint template, the tool includes this constraint.

Supported Design Components

The layout system supports usage of this constraint during high-speed routing (HSR) and
through Hazards in the AutoActive environment. For more information, see “Supported Design
Components” on page 394.

Nets Spreadsheet Group

Delays and Lengths and All

Constraint Type
Modifiable

Example
100 th

Related Topics
Matching Delay or Length Rules Among Nets
Matching Length or Delay Tolerance at the Constraint Class Level

Constraint Manager User's Manual, X-ENTP VX.2.8 489

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Length or TOF Delay Delta

Length or TOF Delay 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 or TOF Delay Tol values when it calculates this delta value.

Nets Spreadsheet Group

Delays and Lengths and All

Constraint Type
Reference

Related Topics
Specifying Length or Delay Rules for Nets

490 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Length or TOF Delay Range

Length or TOF Delay Range

Displays the range of length or time of flight 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.

Nets Spreadsheet Group

Delays and Lengths and All

Constraint Type
Reference

Related Topics
Matching Delay or Length Rules Among Nets
Length or TOF Delay Match

Constraint Manager User's Manual, X-ENTP VX.2.8 491

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Formulas Formula

Formulas Formula
Defines a formula that you can use to create length or delay relationships between nets and pin
pairs. You can define this value for individual nets and pin pairs.
Note
All formulas must begin with one of these operators: =, <, or >. If an operator is missing,
Constraint Manager precedes the formula with the “=” operator when it solves the formula.
The tool does not visibly add the “=” operator to the content of the Formulas Formula cell.

If you create a constraint template, the tool includes this constraint.

Supported Design Components

The layout system supports usage of this constraint during high-speed routing (HSR) and
through Hazards in the AutoActive environment. For more information, see “Supported Design
Components” on page 394.

Nets Spreadsheet Group

Delays and Lengths and All

Constraint Type
Modifiable

Related Topics
Defining Formulas to Create Net Relationships
Length or TOF Delay Match

492 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Formulas Violation

Formulas Violation
Displays formula violation information based on the requirements of the Formulas Formula
constraint.
The tool highlights Formulas Violation cells if a length or delay value does not adhere to the
associated Formulas Formula string. A violation cell always contains data regardless of whether
it meets the requirements of a formula. Only the highlighted cells are those you need to fix.

A highlighted Formulas Violation cell can show one of these issues:

• Actual>formula — The actual is too small (for example, 0th>100th).

• Actual<formula — The actual is too large (for example 150th<100th).
• Actual=miminum:maximum — The actual does not fall between the acceptable low
and high values defined by the formula (for example, 40th=80:100th).

Note
This cell uses the most recent actuals data to determine if there is a violation. For this
reason, you must make sure that you synchronize your Constraint Manager changes
with layout using the rightmost indicator light in layout (it is amber when there are
changes), and then update actuals in Constraint Manager. Otherwise, there may be
violations that the tool does not displayed until the next time you launch it. Conversely,
the tool may still display old violations that are no longer relevant if the actuals data is
not up to date.

Supported Design Components

The layout system supports usage of this constraint through Hazards in the AutoActive
environment. For more information, see “Supported Design Components” on page 394.

Nets Spreadsheet Group

Delays and Lengths and All

Constraint Type
Reference

Related Topics
Solving Formulas to Check for Errors

Constraint Manager User's Manual, X-ENTP VX.2.8 493

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Static Low Overshoot Max

Static Low Overshoot Max

Defines the maximum low DC voltage (minimum) that a buffer can withstand without
permanent damage to the buffer. You can define this value for individual nets, differential pairs,
and constraint classes. An IBIS model defines this value through the S_overshoot_low
keyword.
You must type rail-relative (rr) values, where:

• rr = VLmin – abs for low

• rr = abs – VHmax for high
By defining Dynamic Low Overshoot Max, you can specify an operating voltage limit below
this value.

Figure A-43. Static Low Overshoot Max

If you create a constraint template, the tool includes this constraint.

Supported Design Components

The layout system supports usage of this constraint through Hazards. For more information, see
“Supported Design Components” on page 394.

Nets Spreadsheet Group

Overshoot/Ringback and All

Constraint Type
Modifiable

Example
0.3 V

Related Topics
Defining Overshoot and Ringback Constraints
Dynamic High Overshoot Max
Dynamic Low Overshoot Max
Static High Overshoot Max

494 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Static High Overshoot Max

Static High Overshoot Max

Defines the maximum high DC voltage that a buffer can withstand without permanent damage
to the buffer. You can define this value for individual nets, differential pairs, and constraint
classes. An IBIS model defines this value through the S_overshoot_high keyword.
You must type rail-relative (rr) values, where:

• rr = VLmin – abs for low

• rr = abs – VHmax for high
By defining Dynamic High Overshoot Max, you can specify an operating voltage limit above
this value.

Figure A-44. Static High Overshoot Max

If you create a constraint template, the tool includes this constraint.

Supported Design Components

The layout system supports usage of this constraint through Hazards. For more information, see
“Supported Design Components” on page 394.

Nets Spreadsheet Group

Overshoot/Ringback and All

Constraint Type
Modifiable

Example
0.2 V

Related Topics
Defining Overshoot and Ringback Constraints
Dynamic High Overshoot Max
Dynamic Low Overshoot Max
Static Low Overshoot Max

Constraint Manager User's Manual, X-ENTP VX.2.8 495

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Dynamic Low Overshoot Max

Dynamic Low Overshoot Max

Defines an available, smaller low operating voltage (below minimum) limit for the signal that is
to not exceed a specific duration. This voltage limit should not be met or exceeded, but allow for
the signal to go lower than Static Low Overshoot Max, while never equaling Dynamic Low
Overshoot Max.
You can define these values for individual nets, differential pairs, and constraint classes. An
IBIS model defines these values through the D_overshoot_low and D_overshoot_time
keywords.

You must type rail-relative (rr) values, where:

• rr = VLmin – abs for low

• rr = abs – VHmax for high
Static Low Overshoot Max defines the standard low operating voltage. Dynamic Low
Overshoot Max gives you the ability to define an exception-based low overshoot. This
constraint requires both a time and voltage value, which you separate with a : character.

Figure A-45. Dynamic Low Overshoot Max

If you create a constraint template, the tool includes this constraint.

Supported Design Components

The layout system supports usage of this constraint through Hazards. For more information, see
“Supported Design Components” on page 394.

Nets Spreadsheet Group

Overshoot/Ringback and All

Constraint Type
Modifiable

Example
0.6:5 (0.6 V for 5 ns)

496 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Dynamic Low Overshoot Max

Related Topics
Defining Overshoot and Ringback Constraints
Dynamic High Overshoot Max
Static High Overshoot Max
Static Low Overshoot Max

Constraint Manager User's Manual, X-ENTP VX.2.8 497

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Dynamic High Overshoot Max

Dynamic High Overshoot Max

Defines an available, larger high operating voltage (above maximum) limit for the signal that is
to not exceed a specific duration. This voltage limit should not be met or exceeded, but allow for
the signal to go higher than Static High Overshoot Max, while never equaling Dynamic High
Overshoot Max.
You can define these values for individual nets, differential pairs, and constraint classes. An
IBIS model defines these values through the D_overshoot_high and D_overshoot_time
keywords.

You must type rail-relative (rr) values, where:

• rr = VLmin – abs for low

• rr = abs – VHmax for high
Static High Overshoot Max defines the standard high operating voltage. Dynamic High
Overshoot Max give you the ability to define an exception-based high overshoot. This
constraint requires both a time and voltage value, which you separate with a : character.

Figure A-46. Dynamic High Overshoot Max

If you create a constraint template, the tool includes this constraint.

Supported Design Components

The layout system supports usage of this constraint through Hazards. For more information, see
“Supported Design Components” on page 394.

Nets Spreadsheet Group

Overshoot/Ringback and All

Constraint Type
Modifiable

Example
0.4:5 (0.4 V for 5 ns)

498 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Dynamic High Overshoot Max

Related Topics
Defining Overshoot and Ringback Constraints
Dynamic Low Overshoot Max
Static High Overshoot Max
Static Low Overshoot Max

Constraint Manager User's Manual, X-ENTP VX.2.8 499

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Ringback Margin High Min

Ringback Margin High Min

Defines the minimum allowed difference between the high switching threshold (Vinh) and a
ringback wave. You can define this value for individual nets, differential pairs, and constraint
classes.
Excessive ringback voltage can cause a device to momentarily switch out of the intended logic
state.

If you create a constraint template, the tool includes this constraint.

Supported Design Components

The layout system supports usage of this constraint through Hazards. For more information, see
“Supported Design Components” on page 394.

Nets Spreadsheet Group

Overshoot/Ringback and All

Constraint Type
Modifiable

Related Topics
Defining Overshoot and Ringback Constraints

500 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Ringback Margin Low Min

Ringback Margin Low Min

Defines the minimum allowed difference between the low switching threshold (Vinl) and a
ringback wave. You can define this value for individual nets, differential pairs, and constraint
classes.
Excessive ringback voltage can cause a device to momentarily switch out of the intended logic
state.

If you create a constraint template, the tool includes this constraint.

Supported Design Components

The layout system supports usage of this constraint through Hazards. For more information, see
“Supported Design Components” on page 394.

Nets Spreadsheet Group

Overshoot/Ringback and All

Constraint Type
Modifiable

Related Topics
Defining Overshoot and Ringback Constraints

Constraint Manager User's Manual, X-ENTP VX.2.8 501

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Non-Monotonic Edge

Non-Monotonic Edge
Defines a non-monotonicity requirement for the rising edge, falling edge, or both signal edges.
You can define this value for individual nets, differential pairs, and constraint classes.
A monotonic signal edge progresses toward the opposite signal state without any digression
back to the original signal state. For example, if you set Non-Monotonic Edge to Rising, the tool
reports an error only if the rising signal edge is non-monotonic.

Figure A-47. Non-Monotonic Edge

If you create a constraint template, the tool includes this constraint.

Supported Design Components

The layout system supports usage of this constraint through Hazards. For more information, see
“Supported Design Components” on page 394.

Nets Spreadsheet Group

Overshoot/Ringback and All

Constraint Type
Modifiable

Related Topics
Defining Overshoot and Ringback Constraints

502 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Single Ended Characteristic Impedance Value

Single Ended Characteristic Impedance Value

Defines the single-ended characteristic impedance for a net’s traces. You can define this value
for individual nets, differential pairs, and constraint classes.
If available, the tool displays the minimum and maximum actual values in the Actual cells to its
right.

If you define this constraint at the differential pair level and the individual net level for nets that
comprise a differential pair, in the case of a conflict, the tool uses the value at the differential
pair level.

If you create a constraint template, the tool includes this constraint.

Nets Spreadsheet Group

Net Properties and All

Constraint Type
Modifiable

Related Topics
Specifying General Net Constraints

Constraint Manager User's Manual, X-ENTP VX.2.8 503

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Single Ended Characteristic Impedance Tol

Single Ended Characteristic Impedance Tol

Introduces a tolerance around Single Ended Characteristic Impedance Value. You can define
this value for individual nets, differential pairs, and constraint classes.
For example, a tolerance of 5 ohms allows a Single Ended Characteristic Impedance Value of
40 ohms to tolerate a value between 35 ohms and 45 ohms.

If you create a constraint template, the tool includes this constraint.

Nets Spreadsheet Group

Net Properties and All

Constraint Type
Modifiable

Related Topics
Specifying General Net Constraints

504 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Simulated Delay Edge

Simulated Delay Edge

Defines the simulated delay edge or edges to constrain. You can define this value for individual
nets, differential pairs, pin pairs, and constraint classes.
Figure A-48. Simulated Delay Edge

You can choose from the following:

• Rise — Constrain the rising time between low and high signal states.
• Fall — Constrain the falling time between high and low signal states.
• Rise:Fall — Constrain both rising and falling times between signal states with unique
minimum and maximum values.
For example, a value of 100:120 in the Simulated Delay Min field constrains the
minimum rising delay to 100, and the minimum falling delay to 120.
• Both — Constrain both rising and falling times, between signal states, with the same
minimum and maximum values.
If you create a constraint template, the tool includes this constraint.

Nets Spreadsheet Group

Simulated Delays and All

Constraint Type
Modifiable

Related Topics
Specifying Simulated Delay Rules for Nets

Constraint Manager User's Manual, X-ENTP VX.2.8 505

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Simulated Delay Min

Simulated Delay Min

Defines the minimum acceptable simulated delay time for the Simulated Delay Edge value (for
example, Rise or Fall). You can define this value for individual nets, differential pairs, pin pairs,
and constraint classes.
If Simulated Delay Edge is set to Rise:Fall, separate the rising and falling minimums with a :
character. To use the same minimum value for each switching delay, type a single value. After
you press Enter, Constraint Manager completes the constraint value by duplicating the value
you typed and inserting a colon between them.

If you create a constraint template, the tool includes this constraint.

Nets Spreadsheet Group

Simulated Delays and All

Constraint Type
Modifiable

Related Topics
Specifying Simulated Delay Rules for Nets
Simulated Delay Edge

506 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Simulated Delay Max

Simulated Delay Max

Defines the maximum acceptable simulated delay time for the Simulated Delay Edge value (for
example, Rise:Fall or Both). You can define this value for individual nets, differential pairs, pin
pairs, and constraint classes.
If Simulated Delay Edge is set to Rise:Fall, separate the rising and falling maximums with a :
character. To use the same maximum value for each switching delay, type a single value. After
you press Enter, Constraint Manager completes the constraint value by duplicating the value
you typed and inserting a colon between them.

If you create a constraint template, the tool includes this constraint.

Nets Spreadsheet Group

Simulated Delays and All

Constraint Type
Modifiable

Related Topics
Specifying Simulated Delay Rules for Nets
Simulated Delay Edge

Constraint Manager User's Manual, X-ENTP VX.2.8 507

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Simulated Delay Max Range

Simulated Delay Max Range

Defines a maximum acceptable range of difference between Simulated Delay Actual Min and
Simulated Delay Actual Max for the Simulated Delay Edge value (for example, Fall or Both).
You can define this value for individual nets, differential pairs, pin pairs, and constraint classes.
You can define this constraint with or without defined Simulated Delay Min and Simulated
Delay Max constraints. If Simulated Delay Edge is set to Rise:Fall, separate the rising and
falling maximum ranges with a : character.

If you create a constraint template, the tool includes this constraint.

Nets Spreadsheet Group

Simulated Delays and All

Constraint Type
Modifiable

Related Topics
Specifying Simulated Delay Rules for Nets
Simulated Delay Edge

508 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Simulated Delay Match To

Simulated Delay Match To

Defines the hierarchical level of matching for the Simulated Delay Match constraint. You can
match to the constraint class, net, or pin-pair level. You can define this value for individual nets,
differential pairs, pin pairs, and constraint classes.
If you create a constraint template, the tool includes this constraint.

Nets Spreadsheet Group

Simulated Delays and All

Constraint Type
Modifiable

Related Topics
Matching Simulated Delay Rules Among Nets or Constraint Classes
Simulated Delay Match

Constraint Manager User's Manual, X-ENTP VX.2.8 509

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Simulated Delay Match

Simulated Delay Match

Defines the electrical net, pin pair, or constraint class to which to match Simulated Delay
constraints (for example, Simulated Delay Edge and Simulated Delay Min). You can define this
value for individual nets, differential pairs, pin pairs, and constraint classes.
If matching a net to a constraint class that has unique Simulated Delay constraints for each net,
the tool uses the mean of the delay range for nets in the constraint class as the matching
simulated delay. For example, a constraint class contains three nets with unique Simulated
Delay Min constraints of 100, 115, and 145. If assigning this constraint class to a net, the tool
uses the average value of 120 for minimum delay.

If you create a constraint template, the tool includes this constraint.

Nets Spreadsheet Group

Simulated Delays and All

Constraint Type
Modifiable

Related Topics
Matching Simulated Delay Rules Among Nets or Constraint Classes
Simulated Delay Match To
Simulated Delay Offset
Simulated Delay Tol

510 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Simulated Delay Offset

Simulated Delay Offset

Introduces a positive or negative offset (for example, 50 ns or -50 ns) from Simulated Delay
Min and Simulated Delay Max if matching the simulated delay of an electrical net or constraint
class (Simulated Delay Match). You can define this value for individual nets, differential pairs,
pin pairs, and constraint classes.
The tool uses this offset for all edge rates constrained through the Simulated Delay Edge value
of the matched net or constraint class.

If you create a constraint template, the tool includes this constraint.

Nets Spreadsheet Group

Simulated Delays and All

Constraint Type
Modifiable

Related Topics
Matching Simulated Delay Rules Among Nets or Constraint Classes
Simulated Delay Match
Simulated Delay Max
Simulated Delay Min
Simulated Delay Tol

Constraint Manager User's Manual, X-ENTP VX.2.8 511

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Simulated Delay Tol

Simulated Delay Tol

Introduces a tolerance range (for example, 5 ns) around Simulated Delay Min and Simulated
Delay Max if matching the simulated delay of an electrical net or constraint class (Simulated
Delay Match). You can define this value for individual nets, differential pairs, pin pairs, and
constraint classes.
The tool uses this tolerance for all edge rates constrained through the Simulated Delay Edge
value of the matched net or constraint class.

If you create a constraint template, the tool includes this constraint.

Nets Spreadsheet Group

Simulated Delays and All

Constraint Type
Modifiable

Related Topics
Matching Simulated Delay Rules Among Nets or Constraint Classes
Simulated Delay Match
Simulated Delay Max
Simulated Delay Min
Simulated Delay Offset

512 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Differential Pair Tol Max

Differential Pair Tol Max

Defines the maximum allowed difference between nets in a differential pair.
Specify the maximum as time of flight delay or length between electrical nets in a differential
pair. You can define this value for each pair.

If available, the tool displays the actual value for this constraint in the Actual cell to its right.

If you create a constraint template, the tool includes this constraint.

Supported Design Components

The layout system supports usage of this constraint during high-speed routing and through
Hazards in the AutoActive environment. For more information, see “Supported Design
Components” on page 394.

Nets Spreadsheet Group

Differential Pair Properties and All

Constraint Type
Modifiable

Example
5 ns

Related Topics
Assigning Rules to Differential Pairs

Constraint Manager User's Manual, X-ENTP VX.2.8 513

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Differential Pair Phase Tol Max

Differential Pair Phase Tol Max

Defines how far out of phase the signals of the differential pair are allowed to get. You can
define this value for differential pairs and constraint classes.
Figure A-49. Differential Pair Phase Tol Max

In the illustration, the legs of the differential pair start out in phase. One leg then becomes
longer for an allowed amount (defined through this constraint). Eventually that amount is
exceeded, as indicated in red after point A, resulting with a hazard. It is important to note that
although the legs of the differential pair are in phase from beginning to end, the coupled
segments of the pair are not.

If you create a constraint template, the tool includes this constraint.

Supported Design Components

The layout system supports usage of this constraint during high-speed routing and through
Hazards in the AutoActive environment. For more information, see “Supported Design
Components” on page 394.

Nets Spreadsheet Group

Differential Pair Properties and All

Constraint Type
Modifiable

Example
50 th

Related Topics
Assigning Rules to Differential Pairs
Differential Pair Phase Tol Distance Max

514 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Differential Pair Phase Tol Max

Differential Pair Phase Tol Actual

Constraint Manager User's Manual, X-ENTP VX.2.8 515

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Differential Pair Phase Tol Distance Max

Differential Pair Phase Tol Distance Max

Defines how much further the two signals can continue running out of phase after exceeding the
Differential Pair Phase Tol Max constraint. You can define this value for differential pairs and
constraint classes.
Figure A-50. Differential Pair Phase Tol Distance Max

In the illustration, this constraint allows for the legs of the differential pair to be out of phase for
an extended length. Eventually, the length is exceeded, as indicated in red after point A,
resulting with a hazard. It is important to note that although the legs of the differential pair are in
phase from beginning to end, the coupled segments of the pair are not.

If you create a constraint template, the tool includes this constraint.

Supported Design Components

The layout system supports usage of this constraint during high-speed routing and through
Hazards in the AutoActive environment. For more information, see “Supported Design
Components” on page 394.

Nets Spreadsheet Group

Differential Pair Properties and All

Constraint Type
Modifiable

Example
500 th

Related Topics
Assigning Rules to Differential Pairs
Differential Pair Phase Tol Max

516 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Differential Pair Phase Tol Distance Max

Differential Pair Phase Tol Actual

Constraint Manager User's Manual, X-ENTP VX.2.8 517

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Differential Pair Phase Tol Actual

Differential Pair Phase Tol Actual

Indicates whether both Differential Pair Phase Tol Max and Differential Pair Phase Tol
Distance Max constraints are being exceeded. This actual only shows the word “Violation” if
both constraints are exceeded. It reports “No Violation” otherwise.
Note the following:

• Constraint Manager does not provide this actual unless you define both Differential Pair
Phase Tol Max and Differential Pair Phase Tol Distance Max. Likewise, your layout
software does not report violations against these constraints unless you define them
both.
• This cell uses the most recent actuals data to determine if there is a violation. For this
reason, you must make sure you synchronize your Constraint Manager changes with
layout using the rightmost indicator light in layout (it is amber when there are changes),
and then update actuals in Constraint Manager. Otherwise, there may be violations the
tool does not display until the next time you launch it. Conversely, the tool may display
old violations that are no longer relevant if the actuals data is not up to date.
• For information about precisely where along the differential pair it is exceeding the
constraints, refer to the Hazards system of your layout software.

Supported Design Components

The layout system supports usage of this constraint during high-speed routing and through
Hazards in the AutoActive environment. For more information, see “Supported Design
Components” on page 394.

Nets Spreadsheet Group

Differential Pair Properties and All

Example
No Violation

Related Topics
Assigning Rules to Differential Pairs
Differential Pair Phase Tol Max
Differential Pair Phase Tol Distance Max

518 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Convergence Tolerance Max

Convergence Tolerance Max

Defines the maximum allowed difference in trace length from pads to the point where traces
start routing differentially at the Differential Spacing constraint. You can define this value for
each differential pair.
Note
Do not define this constraint to include pin package lengths. The actual values generated by
your layout tool do not include them.

If available, the tool displays the actual value for this constraint in the Actual cell to its right.

Figure A-51. Convergence Tolerance Max

If you create a constraint template, the tool includes this constraint.

Supported Design Components

The layout system supports usage of this constraint during high-speed routing and through
Hazards in the AutoActive environment. For more information, see “Supported Design
Components” on page 394.

Nets Spreadsheet Group

Differential Pair Properties and All

Constraint Type
Modifiable

Example
500 mil

Related Topics
Assigning Rules to Differential Pairs

Constraint Manager User's Manual, X-ENTP VX.2.8 519

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Distance to Convergence Max

Distance to Convergence Max

Defines the maximum distance that differential traces are allowed to route before they converge
as a differential pair. The distance value is the combination of segment lengths. Convergence is
met when traces start routing at the Differential Spacing constraint. You can define this value
for differential pairs and constraint classes.
Note
Do not define this constraint to include pin package lengths. The actual values generated by
your layout tool do not include them.

If available, the tool displays the actual value for this constraint in the Actual cell to its right.

Figure A-52. Distance to Convergence Max

If you create a constraint template, the tool includes this constraint.

Supported Design Components

The layout system supports usage of this constraint during high-speed routing and through
Hazards in the AutoActive environment. For more information, see “Supported Design
Components” on page 394.

Nets Spreadsheet Group

Differential Pair Properties and All

Constraint Type
Modifiable

Example
5000 mil

Related Topics
Assigning Rules to Differential Pairs

520 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Separation Distance Max

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.
If available, the tool displays the actual value for this constraint in the Actual cell to its right.

Figure A-53. Separation Distance Max

If you create a constraint template, the tool includes this constraint.

Supported Design Components

The layout system supports usage of this constraint during high-speed routing and through
Hazards in the AutoActive environment. For more information, see “Supported Design
Components” on page 394.

Nets Spreadsheet Group

Differential Pair Properties and All

Constraint Type
Modifiable

Example
200 mil

Related Topics
Assigning Rules to Differential Pairs

Constraint Manager User's Manual, X-ENTP VX.2.8 521

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Differential Spacing

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.
Figure A-54. Differential Spacing

Supported Design Components

The layout system supports usage of this constraint during high-speed routing and through
Hazards in the AutoActive environment. For more information, see “Supported Design
Components” on page 394.

Nets Spreadsheet Group

Differential Pair Properties and All

Constraint Type
Reference

Example
30 mil

Related Topics
Assigning Rules to Differential Pairs
Differential Spacing

522 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Differential Impedance Target

Differential Impedance Target

Defines the target differential impedance. You can define this value for each differential pair. If
the layout tool can not meet this value, it uses Differential Spacing. The router does not obey
Differential Impedance Target.
If available, the tool displays the minimum and maximum actual values for this constraint in the
Actual cells to its right.

If you create a constraint template, the tool includes this constraint.

Supported Design Components

The layout system supports usage of this constraint through Hazards. For more information, see
“Supported Design Components” on page 394.

Nets Spreadsheet Group

Differential Pair Properties and All

Constraint Type
Modifiable

Related Topics
Assigning Rules to Differential Pairs
Differential Impedance Tolerance
Differential Spacing

Constraint Manager User's Manual, X-ENTP VX.2.8 523

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Differential Impedance Tolerance

Differential Impedance Tolerance

Introduces a tolerance range around Differential Impedance Target. You can define this value
for each differential pair.
If the layout tool can not meet this value, it uses Differential Spacing. For example, to allow a 5
ohm tolerance range against a Differential Impedance Target value of 25 ohms, type 5. This
tolerance value specifies an acceptable impedance range of 20 to 30 ohms.

If you create a constraint template, the tool includes this constraint.

Nets Spreadsheet Group

Differential Pair Properties and All

Constraint Type
Modifiable

Related Topics
Assigning Rules to Differential Pairs
Differential Impedance Target
Differential Spacing

524 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
I/O Standard

I/O Standard
Defines the technology standard for an FPGA signal net. You can define this value for
individual nets and constraint classes.
In Xpedition I/O Designer, you can set this constraint through the Signals List or Pins List by
modifying the I/O Standard attribute.

If you create a constraint template, the tool includes this constraint.

Nets Spreadsheet Group

I/O and All

Constraint Type
Modifiable

Example
PCI

Related Topics
Modifying Xpedition I/O Designer FPGA Constraints

Constraint Manager User's Manual, X-ENTP VX.2.8 525

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Power Net Constraints Supply Voltage

Power Net Constraints Supply Voltage

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.

Nets Spreadsheet Group

Power Nets and All

Constraint Type
Modifiable

Example
5V

Related Topics
Power-Supply Net and Constraint Definition
Power Net
Analog

526 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Power Net Constraints Max Voltage Drop

Power Net Constraints Max Voltage Drop

Defines the maximum acceptable decrease in voltage from Power Net Constraints Supply
Voltage. You can define this value for individual power-supply nets and constraint classes.

Nets Spreadsheet Group

Power Nets and All

Constraint Type
Modifiable

Example
0.05 V

Related Topics
Power-Supply Net and Constraint Definition
Power Net Constraints Supply Voltage
Power Net
Analog

Constraint Manager User's Manual, X-ENTP VX.2.8 527

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Power Net Constraints Max Current Density

Power Net Constraints Max Current Density

Defines the maximum acceptable current that can flow across a power-supply net structure
(such as an area fill or trace). You can define this value for individual power-supply nets and
constraint classes.

Nets Spreadsheet Group

Power Nets and All

Constraint Type
Modifiable

Example
10 mA/th^2

Related Topics
Power-Supply Net and Constraint Definition
Power Net
Analog

528 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Power Net Constraints Max Via Current

Power Net Constraints Max Via Current

Defines the maximum acceptable current for vias connected to power-supply nets. You can
define this value for individual power-supply nets and constraint classes.

Nets Spreadsheet Group

Power Nets and All

Constraint Type
Modifiable

Example
1A

Related Topics
Power-Supply Net and Constraint Definition
Power Net
Analog

Constraint Manager User's Manual, X-ENTP VX.2.8 529

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Parts

Parts
Refer to the part constraint reference topics that follow. You access these constraints through
the Parts spreadsheet page.

Table A-5. Part Constraints Summary

Constraint Description
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.
IBIS Component Name Defines the IBIS model used for a part. You can define this
value for individual parts and all part instances.
Technology Defines the technology model used for a part. You can define
this value for individual parts and all part instances.
Value Defines the electrical value associated with a discrete part,
which can be resistance, inductance, or capacitance. You can
define this value for individual parts and all part instances.
IBIS Pin Type Displays the IBIS pin type for a pin instance.
Schematic Pin Type Displays the schematic pin type for a pin instance.
Topology Pin Type Defines the chaining pin type for a pin instance. Chaining pin
types are source, load, or terminator (S, L, or T).
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 Delay Defines a pin's internal package delay between the substrate
and dielectric layers of the component. You commonly use
this constraint to define the delay for wire bonding.
Thermal Power Dissipation Defines a part’s power dissipation as a subset of the total
amount of power needed to run the component.
Thermal Power Scaling Defines a part instance’s scaling factor with regard to power
Factor dissipation.

530 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Parts

Table A-5. Part Constraints Summary (cont.)

Constraint Description
Thermal Theta-jc Defines a part’s junction-to-casing thermal resistance. This is
also commonly referred to as die-to-package heat resistance.
Thermal Casing Defines a part’s maximum allowable temperature for the
Temperature Limit component casing or package.
Thermal Junction Defines a part’s maximum allowable temperature for
Temperature Limit component junctions. A component junction is also
commonly referred to as a die.
I/O Standard Displays the defined technology standard for an FPGA signal
net. When on the Nets spreadsheet page, you can define this
value for individual nets and constraint classes.

Constraint Manager User's Manual, X-ENTP VX.2.8 531

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Hierarchical Path

Hierarchical Path
Displays the hierarchical component path, if applicable.

Constraint Type
Reference

Example
XCMP107/E1

Related Topics
Part-Model Assignment Verification and Part Constraints Definition

532 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Part Number

Part Number
Displays the part number for a design component.
If you create a constraint template, the tool includes this constraint.

Constraint Type
Reference

Example
74LS82

Related Topics
Part-Model Assignment Verification and Part Constraints Definition

Constraint Manager User's Manual, X-ENTP VX.2.8 533

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Qty

Qty
Displays the number of times a part is used in the design.

Constraint Type
Reference

Example
4

Related Topics
Part-Model Assignment Verification and Part Constraints Definition

534 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Part Type

Part Type
Displays the part-type value associated with a design component.

Constraint Type
Reference

Example
IC

Related Topics
Part-Model Assignment Verification and Part Constraints Definition

Constraint Manager User's Manual, X-ENTP VX.2.8 535

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
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

Related Topics
Part-Model Assignment Verification and Part Constraints Definition

536 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
IBIS Component Name

IBIS Component Name

Defines the IBIS model used for a part. You can define this value for individual parts and all
part instances.
IBIS models contain the greatest amount of part detail, including package information for each
pin, and represent parts most accurately. Constraint Manager uses your design information to
assign a default value to this cell. In most cases it will be correct, though, it is important to
understand the process that the tool uses to make the assignment. For more information, refer to
“Automatic Assignment of IBIS Models” on page 365.

Note
If both IBIS Component Name and Technology constraints are defined for a part, the tool
uses IBIS Component Name.

Constraint Type
Modifiable

Example
ibis_f_24

Related Topics
Assigning Models to Parts
Overriding IBIS Values
Technology

Constraint Manager User's Manual, X-ENTP VX.2.8 537

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Technology

Technology
Defines the technology model used for a part. You can define this value for individual parts and
all part instances.
Because industry models parts broadly by technological classification, technology models do
not provide as much detail as IBIS models. A common difference between technology models
and IBIS models is that technology models include information for each pin type, while IBIS
models include information for each pin.

Note
If both IBIS Component Name and Technology constraints are defined for a part, the tool
uses IBIS Component Name.

Constraint Type
Modifiable

Example
tech_bicmos

Related Topics
Assigning Models to Parts
IBIS Component Name

538 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Value

Value
Defines the electrical value associated with a discrete part, which can be resistance, inductance,
or capacitance. You can define this value for individual parts and all part instances.
You can use the Value constraint for two-pin resistors, capacitors, inductors, Thevenin and AC
terminators, and passive modules that contain multiple two-pin slots/gates.

Note
If assigning a Value constraint to a discrete part row, its reference designator (for example,
R, L, or C), must be defined. For more information, refer to “Specifying Discrete
Component Prefixes” on page 99.

Constraint Type
Modifiable

Related Topics
Overriding IBIS Values

Constraint Manager User's Manual, X-ENTP VX.2.8 539

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
IBIS Pin Type

IBIS Pin Type

Displays the IBIS pin type for a pin instance.
IBIS Pin Type comes from library information in IBIS Component Name.

Constraint Type
Reference

Related Topics
Part-Model Assignment Verification and Part Constraints Definition
IBIS Component Name

540 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Schematic Pin Type

Schematic Pin Type

Displays the schematic pin type for a pin instance.

Constraint Type
Reference

Related Topics
Part-Model Assignment Verification and Part Constraints Definition

Constraint Manager User's Manual, X-ENTP VX.2.8 541

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Topology Pin Type

Topology Pin Type

Defines the chaining pin type for a pin instance. Chaining pin types are source, load, or
terminator (S, L, or T).
Note
You can define this constraint for component pins, but not part pins.

Figure A-55. Topology Pin Type

If you create a constraint template, the tool includes this constraint.

Supported Design Components

The layout system supports usage of this constraint during high-speed routing and in the
AutoActive environment. For more information, see “Supported Design Components” on
page 394.

Constraint Type
Modifiable

Related Topics
Part-Model Assignment Verification and Part Constraints Definition

542 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
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. There is no default value for this
constraint. If you do not define it, pin package length is 0.

Having Constraint Manager Automatically Calculate Pin Package Length

If used in conjunction with Pin Package Delay, you can have Constraint Manager automatically
calculate Pin Package Length based on the pin package propagation delay (ns/th) that is defined
in your Constraint Manager settings. To do so, after you have defined Pin Package Delay, right-
click within the Pin Package Length cell, then click Calculate Length.

Supported Design Components

The layout system supports usage of this constraint during high-speed routing and in the
AutoActive environment. For more information, see “Supported Design Components” on
page 394.

Constraint Type
Modifiable

Limits

Maximum Value
6 in

Related Topics
Importing Pin Package Delay or Length Values
ImportPinPackageLengths
Pin Package Delay

Constraint Manager User's Manual, X-ENTP VX.2.8 543

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Pin Package Delay

Pin Package Delay

Defines a pin's internal package delay between the substrate and dielectric layers of the
component. You commonly use this constraint to define the delay for wire bonding.
Pin package delay constraints only affect net delay values. There is no default value for this
constraint. If you do not define it, pin package delay is 0.

Having Constraint Manager Automatically Calculate Pin Package Delay

If used in conjunction with Pin Package Length, you can have Constraint Manager
automatically calculate Pin Package Delay based on the pin package propagation delay (ns/th)
that is defined in your Constraint Manager settings. To do so, after you have defined Pin
Package Length, right-click within the Pin Package Delay cell, then click Calculate Delay.

Supported Design Components

The layout system supports usage of this constraint during high-speed routing and in the
AutoActive environment. For more information, see “Supported Design Components” on
page 394.

Constraint Type
Modifiable

Limits

Maximum Value
1000 ps

Related Topics
Importing Pin Package Delay or Length Values
ImportPinPackageDelays
Specifying Design Configuration Preferences
Pin Package Length

544 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Thermal Power Dissipation

Thermal Power Dissipation

Defines a part’s power dissipation as a subset of the total amount of power needed to run the
component.

Constraint Type
Modifiable

Example
1W

Related Topics
Defining Thermal Constraints for Parts

Constraint Manager User's Manual, X-ENTP VX.2.8 545

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Thermal Power Scaling Factor

Thermal Power Scaling Factor

Defines a part instance’s scaling factor with regard to power dissipation.

Constraint Type
Modifiable

Example
1

Related Topics
Defining Thermal Constraints for Parts

546 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Thermal Theta-jc

Thermal Theta-jc
Defines a part’s junction-to-casing thermal resistance. This is also commonly referred to as die-
to-package heat resistance.

Constraint Type
Modifiable

Example
7 degC/watt

Related Topics
Defining Thermal Constraints for Parts

Constraint Manager User's Manual, X-ENTP VX.2.8 547

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Thermal Casing Temperature Limit

Thermal Casing Temperature Limit

Defines a part’s maximum allowable temperature for the component casing or package.
If available, the tool displays the actual value for this constraint in the Actual cell to its right.

Constraint Type
Modifiable

Example
60 degC

Related Topics
Defining Thermal Constraints for Parts

548 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Thermal Junction Temperature Limit

Thermal Junction Temperature Limit

Defines a part’s maximum allowable temperature for component junctions. A component
junction is also commonly referred to as a die.
If available, the tool displays the actual value for this constraint in the Actual cell to its right.

Constraint Type
Modifiable

Example
70 degC

Related Topics
Defining Thermal Constraints for Parts

Constraint Manager User's Manual, X-ENTP VX.2.8 549

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
I/O Standard

I/O Standard
Displays the defined technology standard for an FPGA signal net. When on the Nets
spreadsheet page, you can define this value for individual nets and constraint classes.
In Xpedition I/O Designer, you can set this constraint through the Signals List or Pins List by
modifying the I/O Standard attribute.

Constraint Type
Reference

Example
PCI

Related Topics
Modifying Xpedition I/O Designer FPGA Constraints

550 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Noise Rules

Noise Rules
Refer to the noise rule constraint reference topics that follow. You access these constraints
through the Noise Rules spreadsheet page.

Table A-6. Noise Rule Constraints Summary

Constraint Description
Noise Type Defines the noise type for a specific parallelism rule and/or
Crosstalk Max constraint and Crosstalk Level. You can set
this value to net-to-net or class-to-class.
Constraint Class or Defines the victim constraint class or electrical net of the
Electrical Net Name Victim aggressor-victim relationship. You can use these
relationships to define both crosstalk and parallelism rules.
Constraint Class or Defines the aggressor constraint class or electrical net of the
Electrical Net Name aggressor-victim relationship. You can use these
Aggressor relationships to define both crosstalk and parallelism rules.
Parallelism Rule Defines the parallelism rule for a class-to-class or net-to-net
parallelism relationship.
Crosstalk Max Defines the maximum acceptable crosstalk that a net or all
nets within a constraint class can be subjected to as victim
nets. You can define this value for individual nets and
constraint classes.
Crosstalk Level Defines the signal state of the victim net in a crosstalk
relationship. Supported simulators like HyperLynx use this
constraint. Layout systems do not use this constraint.

Constraint Manager User's Manual, X-ENTP VX.2.8 551

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Noise Type

Noise Type
Defines the noise type for a specific parallelism rule and/or Crosstalk Max constraint and
Crosstalk Level. You can set this value to net-to-net or class-to-class.

Supported Design Components

The layout system supports usage of this constraint during high-speed routing and through
Hazards in the AutoActive environment. For more information, see “Supported Design
Components” on page 394.

Constraint Type
Modifiable

Related Topics
Defining Crosstalk Rules for Nets and Constraint Classes
Assigning Parallelism Rules to Nets and Constraint Classes
Differential Spacing

552 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Constraint Class or Electrical Net Name Victim

Constraint Class or Electrical Net Name Victim

Defines the victim constraint class or electrical net of the aggressor-victim relationship. You
can use these relationships to define both crosstalk and parallelism rules.

Supported Design Components

The layout system supports usage of this constraint during high-speed routing and through
Hazards in the AutoActive environment. For more information, see “Supported Design
Components” on page 394.

Constraint Type
Modifiable

Related Topics
Defining Crosstalk Rules for Nets and Constraint Classes
Assigning Parallelism Rules to Nets and Constraint Classes
Crosstalk Level
Crosstalk Max
Parallelism Rule

Constraint Manager User's Manual, X-ENTP VX.2.8 553

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Constraint Class or Electrical Net Name Aggressor

Constraint Class or Electrical Net Name Aggressor

Defines the aggressor constraint class or electrical net of the aggressor-victim relationship. You
can use these relationships to define both crosstalk and parallelism rules.

Supported Design Components

The layout system supports usage of this constraint during high-speed routing and through
Hazards in the AutoActive environment. For more information, see “Supported Design
Components” on page 394.

Constraint Type
Modifiable

Related Topics
Defining Crosstalk Rules for Nets and Constraint Classes
Assigning Parallelism Rules to Nets and Constraint Classes
Crosstalk Level
Crosstalk Max
Parallelism Rule

554 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Parallelism Rule

Parallelism Rule
Defines the parallelism rule for a class-to-class or net-to-net parallelism relationship.
The Parallelism Rule constraint can be one of the parallelism rules you defined previously. You
can also create a new parallelism rule by selecting New in the cell for this constraint.

Supported Design Components

The layout system supports usage of this constraint during high-speed routing and through
Hazards in the AutoActive environment. For more information, see “Supported Design
Components” on page 394.

Constraint Type
Modifiable

Related Topics
Assigning Parallelism Rules to Nets and Constraint Classes

Constraint Manager User's Manual, X-ENTP VX.2.8 555

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Crosstalk Max

Crosstalk Max
Defines the maximum acceptable crosstalk that a net or all nets within a constraint class can be
subjected to as victim nets. You can define this value for individual nets and constraint classes.
Crosstalk results if another net (aggressor) causes electromagnetic interference on a victim net.
In the illustration, the electromagnetic field produced by net A is strong enough to interfere with
net B.

Figure A-56. Crosstalk Max

In the spreadsheet, you define aggressor nets using Constraint Class or Electrical Net Name
Aggressor. You define victim nets using Constraint Class or Electrical Net Name Victim.

If you create a constraint template, the tool includes this constraint.

Supported Design Components

The layout system supports usage of this constraint during high-speed routing and through
Hazards in the AutoActive environment. For more information, see “Supported Design
Components” on page 394.

Constraint Type
Modifiable

Related Topics
Defining Crosstalk Rules for Nets and Constraint Classes
Constraint Class or Electrical Net Name Aggressor
Constraint Class or Electrical Net Name Victim
Crosstalk Level

556 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Crosstalk Level

Crosstalk Level
Defines the signal state of the victim net in a crosstalk relationship. Supported simulators like
HyperLynx use this constraint. Layout systems do not use this constraint.
You can define Crosstalk Level using one of these choices:

• High & Low — Require Crosstalk Max to be met for both high and low signal states.
• High — The victim net is on (in its high state). The voltage level is at or above the high
threshold (for example, 5.1 V).
• Low — The victim net is off (in its low state). The voltage level is at or below the low
threshold (for example, 0.9 V).
• Tristate — Require Crosstalk Max to be met for just tristate signal states. During
tristate, the victim net is off, but a small voltage still flows from the receiver to ground
(for example, 0.5 V).
• High & Tristate — Require Crosstalk Max to be met for both high and tristate signal
states. During tristate, the victim net is off, but a small voltage still flows from the
receiver to ground (for example, 0.5 V).
• Low & Tristate — Require Crosstalk Max to be met for both low and tristate signal
states. During tristate, the victim net is off, but a small voltage still flows from the
receiver to ground (for example, 0.5 V).
• All — Require Crosstalk Max to be met for all signal states.
If you create a constraint template, the tool includes this constraint.

Constraint Type
Modifiable

Related Topics
Defining Crosstalk Rules for Nets and Constraint Classes
Constraint Class or Electrical Net Name Aggressor
Constraint Class or Electrical Net Name Victim
Crosstalk Max

Constraint Manager User's Manual, X-ENTP VX.2.8 557

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Constraint Templates

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 464.
Crosstalk Max See “Crosstalk Max” on page 556.
Crosstalk Level See “Crosstalk Level” on page 557.
Topology Type See “Topology Type” on page 468.

558 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Constraint Reference
Constraint Templates

Constraint Description/Topic
Topology Ordered See “Topology Ordered” on page 470.
Stub Length Max See “Stub Length Max” on page 471.
# Vias Max See “# Vias Max” on page 473.
# Test Points Required See “# Test Points Required” on page 474.
Backdrill See “Backdrill” on page 475.
Restricted Layer Length See:
• “Restricted Layer Length Max External” on page 476
• “Restricted Layer Length Max Internal” on page 477
From To Constraints See:
• “From To Constraints Layer” on page 478
• “From To Constraints Trace Width” on page 479
Length or TOF Delay See:
• “Length or TOF Delay Type” on page 481
• “Length or TOF Delay Min” on page 482
• “Length or TOF Delay Max” on page 484
• “Length or TOF Delay Match” on page 488
• “Length or TOF Delay Tol” on page 489
Formulas Formula See “Formulas Formula” on page 492.
Static and Dynamic See:
Overshoot • “Static Low Overshoot Max” on page 494
• “Static High Overshoot Max” on page 495
• “Dynamic Low Overshoot Max” on page 496
• “Dynamic High Overshoot Max” on page 498
Ringback Margin See:
• “Ringback Margin High Min” on page 500
• “Ringback Margin Low Min” on page 501
Non-Monotonic Edge See “Non-Monotonic Edge” on page 502.
Single Ended Characteristic See:
Impedance • “Single Ended Characteristic Impedance Value” on
page 503
• “Single Ended Characteristic Impedance Tol” on
page 504

Constraint Manager User's Manual, X-ENTP VX.2.8 559

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Constraint Reference
Constraint Templates

Constraint Description/Topic
Simulated Delay See:
• “Simulated Delay Edge” on page 505
• “Simulated Delay Min” on page 506
• “Simulated Delay Max” on page 507
• “Simulated Delay Max Range” on page 508
• “Simulated Delay Match To” on page 509
• “Simulated Delay Match” on page 510
• “Simulated Delay Offset” on page 511
• “Simulated Delay Tol” on page 512
Differential Pair Tol Max See “Differential Pair Tol Max” on page 513.
Differential Pair Phase Tol See:
• “Differential Pair Phase Tol Max” on page 514
• “Differential Pair Phase Tol Distance Max” on
page 516
Convergence Tolerance Max See “Convergence Tolerance Max” on page 519.
Distance to Convergence See “Distance to Convergence Max” on page 520.
Max
Separation Distance Max See “Separation Distance Max” on page 521.
Differential Impedance See:
• “Differential Impedance Target” on page 523
• “Differential Impedance Tolerance” on page 524
I/O Standard See “I/O Standard” on page 525.

560 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Appendix B
Command-Line Tools Reference

This section provides reference documentation for command-line tools that are available with
Constraint Manager. You use these tools to export, import, encrypt, and decrypt constraint data.

Table B-1. Conventions for Command-Line Syntax

Convention Example Usage
Bold csv2dat -input path Bold font indicates a required
argument.
Normal cons2csv -export Normal font indicates an optional
argument.
Italic csv2dat -input path Italic font indicates a user-supplied
argument.
{} csv2dat -input path {-decrypt | Brace enclose arguments to indicate
-encrypt} -output path grouping. Do not type braces.
| csv2dat -input path {-decrypt | The vertical bar indicates an either/
-encrypt} -output path or choice between items. Do not
include the bar in the command.

ceschk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
CesSyncCheck . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
cons2ascii . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
cons2csv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
cons2xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
csv2dat. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571
ImportPinPackageDelays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572
ImportPinPackageLengths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
ImportStk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
sandboxfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578

Constraint Manager User's Manual, X-ENTP VX.2.8 561

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Command-Line Tools Reference
ceschk

ceschk
Use ceschk with certain arguments to run CES Diagnostics.
Usage
..\SDD_HOME\common\<OS>\bin\ceschk -prj .prj file -sn name -topblock name -l -log path
-v -fix
Arguments
• -prj .prj file
.prj file for the design.
• -sn name
Snapshot name.
• -topblock name
Topblock name.
• -l
Display the list of diagnostic tests.
• -log path
Create a log file at the specified path.
• -v
Increase the amount of information the tool displays.
• -fix
Automatically fix errors.
Description
Use this command to run Tools > CES Diagnostics from your system prompt.

Tip
To determine the path to the .prj file, snapshot name, and other similar information, you can
use iCDB Server Manager. Choose Tools > iCDB Server Manager.

Examples
Run diagnostics without fixing errors:

ceschk -prj c:\design\design.prj -sn DxD -topblock top

-log c:\design\ceschk1.log

Related Topics
Constraint Diagnostics

562 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Command-Line Tools Reference
CesSyncCheck

CesSyncCheck
Use CesSyncCheck to compare snapshots of the same project, or different projects.
Note
When you run this command on an EDM-managed project, the tool compares the open
design against the last checked-in version of the complimentary design.

Usage
Compare Snapshots of the Same Project
..\SDD_HOME\common\<OS>\bin\CesSyncCheck -prj path -fs name -bs name -tb name -
compare -output path -log name
Compare Snapshots of Different Projects
..\SDD_HOME\common\<OS>\bin\CesSyncCheck -src_prj path -src_sn name -src_tb name
-trg_prj name -trg_sn name -trg_tb name -compare -output path -log name
Arguments
• -prj path
.prj file for the design (same project compare).
• -fs name
Front-end snapshot name (same project compare).
• -bs name
Back-end snapshot name (same project compare).
• -tb name
Topblock name (same project compare).
• -src_prj path
.prj file for the source project (different project compare).
• -src_sn name
Source project snapshot name (different project compare).
• -src_tb name
Source project topblock name (different project compare).
• -trg_prj path
.prj file for the target project (different project compare).
• -trg_sn name
Target project snapshot name (different project compare).

Constraint Manager User's Manual, X-ENTP VX.2.8 563

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Command-Line Tools Reference
CesSyncCheck

• -trg_tb name
Target project topblock name (different project compare).
• -compare
Compare argument.
• -output path
Create a log file at the specified path.
• -log name
Define the name for the log file.
Description
Use this command to run Output > Check Constraints Synchronization from your system
prompt. Most of the arguments are restricted to one of the types of comparison (for example,
same project compare).

Tip
To determine the path to the .prj file, snapshot name, and other similar information, you can
use iCDB Server Manager. Choose Tools > iCDB Server Manager.

Examples
Compare the front-end and back-end snapshots of the same project:

CesSyncCheck -prj c:\design\design.prj -fs DXD -bs EXP -tb top -compare -
output c:\design\logs -log sync.log

Compare snapshots from different projects:

CesSyncCheck -src_prj c:\design1\design1.prj -src_sn DXD -src_tb top -

trg_prj c:\design2\design2.prj -trg_sn DXD -trg_tb top -compare -output
c:\design\logs -log sync.log

Related Topics
Checking Constraints Synchronization

564 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Command-Line Tools Reference
cons2ascii

cons2ascii
Use cons2ascii to export Constraint Manager data in the encrypted ASCII format (.cs_).
Usage
..\SDD_HOME\common\<OS>\bin\cons2ascii -export -outputdir path -cns .cns file
-prj .prj file -snapshot name -topblock name
Arguments
• -export
Export argument.
• -outputdir path
Directory in which to place the exported constraint file.
• -cns .cns file
.cns file to use.
• -prj .prj file
.prj file for the design.
• -snapshot name
Snapshot name.
• -topblock name
Topblock name.
Description
This command exports the entire constraint set in encrypted ASCII format (.cs_). This
command requires you to supply all arguments.

Tip
To determine the path to the iCDB database, snapshot name, and other similar information,
you can use iCDB Server Manager. To access it, from the Tools menu, click iCDB Server
Manager.

Examples
cons2ascii -export -outputdir c:\OutDir
-cns c:\ee7.9.5\7.9.5EE\SDD_HOME\standard\ce_ee.cn
-prj c:\design\design.prj -snapshot DxD -topblock top

Related Topics
Exporting Constraints in Encrypted ASCII Format
Decrypting and Encrypting Exported Constraint Data

Constraint Manager User's Manual, X-ENTP VX.2.8 565

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Command-Line Tools Reference
cons2csv

cons2csv
Prerequisite: For this command to run, the design must show no problems in CES Diagnostics.
Use cons2csv to export and import Constraint Manager data in CSV format (.csv). You can also
import .ecsv files. The command only supports import into the front-end snapshot. Use the
menu selection in a layout invocation of Constraint Manager if you want to import into the
back-end constraint set.
Note
To use CSV import, you must set an environment variable called
CESENG_IMPORTCSV_ENABLE to 1. Import is only supported in the Xpedition
Enterprise flow.

Usage
Export
..\SDD_HOME\common\<OS>\bin\cons2csv -export -prj .prj file -board name
-snapshot name -topblock name -frontend -output path -log path -pages -expact
Import
..\SDD_HOME\common\<OS>\bin\cons2csv -import -input file -prj .prj file
-snapshot name -topblock name -log path
Arguments
• -export
Export constraints argument. Export is the default mode for the command. As such, it is
does not require this argument for export.
• -import
Import constraints argument.
• -output path
Use only with the export argument. Directory and filename of exported constraint file(s). If
using the pages argument, this argument defines the suffix to use for each file. If you do not
use the pages argument, you should type this argument as the full filename (for example, c:\
output\alltables.csv).
• -input file
Use only with the import argument. Directory and filename of the .csv file or .ecsv file to
import or process.
• -prj .prj file
Directory and filename of .prj file.
• -board name
Export argument that is required if the design includes multiple boards.

566 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Command-Line Tools Reference
cons2csv

• -snapshot name
Snapshot name. The command does not require this argument for export.
• -topblock name
Top block name. The command does not require this argument for export.
• -frontend
Export argument you use to export the front-end snapshot. By default, the command exports
the back-end snapshot.
• -log path
Use to create a log file at the path you specify.
• -pages
Use with the export argument to create a separate .csv file for each table.
• -expact
Use to export the current set of actuals data (if available). Availability of actuals data
depends on whether you are exporting constraint data from the back-end snapshot, or if the
front-end snapshot includes an actuals side file.
Description
This command exports and imports constraint data in the CSV file format (.csv). You can also
import .ecsv files. If exporting, you can choose to export all constraint data to a single file or
multiple files.

The tool creates a single .csv file for all Constraint Manager data. The file uses the units settings
defined in the tool. The order of constraints is based on the default column order in Constraint
Manager for each page. If the file already exists, a new one is created with an incremental
suffix. For example, <filename>_1.csv, <filename>_2.csv, etc.

Tip
To determine the path to the .prj file, snapshot name, and other similar information, you can
use iCDB Server Manager. To access it, from the Tools menu, click iCDB Server
Manager.

Examples
Export
cons2csv -prj .\design.prj

Import
cons2csv -import -input c:\data\tables_Class2ClassClear.csv
-prj .\design.prj -snapshot DXD -topblock Schematic1

Constraint Manager User's Manual, X-ENTP VX.2.8 567

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Command-Line Tools Reference
cons2csv

Related Topics
Exporting Constraints in CSV Format
Importing Constraints in CSV Format
Decrypting and Encrypting Exported Constraint Data
Example CSV Files
Guidelines for CSV Files

568 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Command-Line Tools Reference
cons2xml

cons2xml
Use cons2xml to export and import Constraint Manager data in the proprietary encrypted XML
format (.cts). You can also list detailed information about an iCDB database using this
command.
Usage
Export
..\SDD_HOME\common\<OS>\bin\cons2xml -export -output path -icdb path -sn snapshot
-tb topblock -log path {-constempl | -pages list}
Import
..\SDD_HOME\common\<OS>\bin\cons2xml -import -input path -icdb path -sn snapshot
-tb topblock -log path
List
..\SDD_HOME\common\<OS>\bin\cons2xml -list -icdb path
Arguments
• -export
Export argument.
• -import
Import argument.
• -list
List argument. Provides detailed information about the iCDB database (for example,
snapshot names and block names).
• -output path
Use only with the export argument. Directory in which to place the exported constraint file.
• -input path
Use only with the import argument. Directory and filename of the .cts file to import.
• -icdb path
Path to the iCDB database.
• -sn snapshot
Snapshot name.
• -tb topblock
Top block name.
• -log path
Path to optional log file that can be created during import or export.

Constraint Manager User's Manual, X-ENTP VX.2.8 569

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Command-Line Tools Reference
cons2xml

• {-constempl | -pages list}

Use with the export argument. Optionally, output just constraint template information or just
certain constraint information based on the following list of all available pages/constraint
data: CLASS_CLASS_RULE, ENET, LAYER, PACKAGE_CLEARANCE,
PARALLEL_RULE, PART, SCHEME_CLASS_LAYER, SCHEME_RULE_LAYER,
TOPOTMPL, ZAXIS_CLASS_CLASS_RULE, and ZAXIS_CLEARRULE.
Description
This command exports and imports constraint data in the proprietary encrypted XML (.cts)
format. You can also use it to list detailed information about an iCDB database (that you could
then use with the import or export functions of this command). If exporting, you can choose
which constraints/pages to include in the output file. If importing, all constraint data that you
exported to the file is imported back into Constraint Manager.

Tip
To determine the path to the iCDB database, snapshot name, and other similar information,
you can use iCDB Server Manager. To access it, from the Tools menu, click iCDB Server
Manager.

Examples
Export
cons2xml -export -output c:\output\file.cts -icdb c:\mydesign\database
-sn Snapshot1 -tb Microtop -log c:\output\file_log.txt -pages ENET,PART

Import
cons2xml -import -input c:\files\file.cts -icdb c:\mydesign\database
-sn Snapshot1 -tb Microtop -log c:\files\file_log.txt

List
cons2xml -list -icdb c:\mydesign\database

Related Topics
Constraint Export in Encrypted XML Format
Import of Constraints

570 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Command-Line Tools Reference
csv2dat

csv2dat
Prerequisite: You must have a Constraint Encryption license. You can request this license free
of charge from the PCB Community: http://communities.mentor.com/mgcx/docs/DOC-
2533
Use csv2dat to decrypt and encrypt data files exported from Constraint Manager. You can
decrypt files in encrypted ASCII (.cs_) format and encrypted CSV (.ecsv) format. You also use
this command to encrypt CSV files into encrypted CSV (.ecsv) format.
Usage
..\SDD_HOME\common\<OS>\bin\csv2dat -input path {-decrypt | -encrypt}
-output path
Arguments
• -input path
The path and filename of the file you want to process.
• {-decrypt | -encrypt}
Specifies whether you are decrypting or encrypting data. This argument is optional because
the command determines whether you want to encrypt or decrypt based on the extension of
the input file.
• -output path
The path and filename of the output file (.ecsv) you want to produce. If you do not specify
this argument, the command creates the file in the location of the input file.
Description
This command encrypts or decrypts a single file at a time. Upon completion, the command
outputs the location of the file it creates. The output file type is the opposite type of the input
file. For example, if you run csv2dat on an .ecsv file, the tool produces a .csv file.

Examples
Decrypt
csv2dat -input C:\files\design1_nets.ecsv

Encrypt CSV File

csv2dat -input C:\files\data.csv

Encrypt Text File

csv2dat -input C:\Files\design1_nets.txt

Related Topics
Decrypting and Encrypting Exported Constraint Data

Constraint Manager User's Manual, X-ENTP VX.2.8 571

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Command-Line Tools Reference
ImportPinPackageDelays

ImportPinPackageDelays
Use ImportPinPackageDelays to import values from a PinPkgDelays.txt or *.ppd side file.
Usage
..\SDD_HOME\common\<OS>\bin\ImportPinPackageDelays -prj path -sn name
-tb name
-ppd path -offline -zero_ppl -log path
Arguments
• -prj path
.prj file for the design.
• -sn name
Snapshot name.
• -tb name
Topblock name.
• -ppd path
Path to a PinPkgDelays.txt or *.ppd side file.
• -offline
Runs import without an iCDB server.
• -zero_ppl
Sets values to 0 for any pin package delays that are not specified in the side file. This only
applies to pins of part numbers defined in the side file. Otherwise, the tool keeps the existing
values, if defined.
• -log path
Creates a log file at the specified path.
Description
This command imports Constraint Manager Parts page Pin Package Delay constraint values
from a side file that you previously created or acquired. If a part number included in a side file is
missing definitions for one or more pins, you can use the zero_ppl argument to set Pin Package
Delay to zero for those pins.

Tip
To determine the snapshot name and other similar information, you can use iCDB Server
Manager. To access it, from the Tools menu, choose iCDB Server Manager.

572 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Command-Line Tools Reference
ImportPinPackageDelays

Examples
ImportPinPackageDelays -prj c:\micro_design\micro.prj -sn micro -tb top
-ppd c:\data\PinPkgDelays.txt

ImportPinPackageDelays -prj c:\design\design.prj -sn design -tb top

-ppd c:\mypackagedelays.ppd

Related Topics
Importing Pin Package Delay or Length Values
PinPkgDelays.txt File Format
Pin Package Delay

Constraint Manager User's Manual, X-ENTP VX.2.8 573

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Command-Line Tools Reference
ImportPinPackageLengths

ImportPinPackageLengths
Use ImportPinPackageLengths to import values from a PinPkgLengths.txt or *.ppl side file.
Usage
..\SDD_HOME\common\<OS>\bin\ImportPinPackageLengths -prj path -sn name
-tb name
-ppl path -offline -zero_ppl -log path
Arguments
• -prj path
.prj file for the design.
• -sn name
Snapshot name.
• -tb name
Topblock name.
• -ppl path
Path to a PinPkgLengths.txt or *.ppl side file.
• -offline
Run import without an iCDB server.
• -zero_ppl
Sets values to 0 for any pin package lengths that are not specified in the side file. This only
applies to pins of part numbers defined in the side file. Otherwise, the tool keeps the existing
values, if defined.
• -log path
Create a log file at the specified path.
Description
This command imports Constraint Manager Parts page Pin Package Length constraint values
from a side file that you previously created or acquired. If a part number included in a side file is
missing definitions for one or more pins, you can use the zero_ppl argument to set Pin Package
Length to zero for those pins.

Tip
To determine the path to the snapshot name and other similar information, you can use
iCDB Server Manager. To access it, from the Tools menu, choose iCDB Server Manager.

574 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Command-Line Tools Reference
ImportPinPackageLengths

Examples
ImportPinPackageLengths -prj c:\micro_design\micro.prj -sn micro -tb top
-ppl c:\data\PinPkgLengths.txt

ImportPinPackageLengths -prj c:\design\design.prj -sn design -tb top

-ppl c:\mypackagelengths.ppl

Related Topics
Importing Pin Package Delay or Length Values
PinPkgLengths.txt File Format
Pin Package Length

Constraint Manager User's Manual, X-ENTP VX.2.8 575

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Command-Line Tools Reference
ImportStk

ImportStk
Use ImportStk to import parameters of a board stackup into a front-end design or back-end
design. You can import HyperLynx (.stk) and Polar Speedstack (.stkx) stackups.
Usage
..\SDD_HOME\common\<OS>\bin\ImportStk -input path -prj path -board name -frontend
-log path -map_layers mapping -remove_electrical_layer -stackup_only
Arguments
• -input path
Location and filename of the .stk file or .stkx file.
• -prj path
Location and filename of the .prj file.
• -board name
Board name. This argument is required if multiple boards exist in the design.
• -frontend
Imports the stackup file into the front-end design. By default, the import affects the back-
end design.
• -log path
Creates a log file at the specified location.
• -map_layers mapping
Specifies how to preserve existing internal metallic layers data so the tool does not clear
trace widths and clearances values. The command requires this argument if there is a
difference in the number of layers.
Examples:
o -map_layers 1,3,4 — The stackup file has three metallic layers and layer 4 is the last
metallic layer in the design’s stackup. Because the stackup file does not include
information for all four layers, after import, the tool will reset the current layer
constraints for layer 2 to default values.
o -map_layers 1,,,2 — The stackup file has four metallic layers (1,s1,s2,2) and layer 2
is the last metallic layer in the design’s stackup. After import, the design will contain
four metallic layers and the tool will preserve the constraints for layers 1 and 2 of the
original stackup.
• -remove_electrical_layer
Required if the import will cause removal of one more layers that contain electrical data.

576 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Command-Line Tools Reference
ImportStk

• -stackup_only
For .stkx files and .stk .fsi file-pairs only, specifies that import should include just basic
stackup information (for example, layer thickness and the dielectric constant) without
controlled impedance structures.
Caution
You must use this argument to import stackups that include controlled impedance
structures (and ignore them). Otherwise, import will fail. To import these structures,
you must use the Import Stackup dialog box.

Description
You can import stackup parameters into a front-end or back-end design through the Constraint
Manager ImportStk command. To use this command, the design must already have a stackup.
If you import a stackup that includes less metallic layers than the design stackup, the tool keeps
the extra layers but resets layer constraint values to defaults.

During an import, the command uses at least the following definitions:

• Basic — Er, layer name, thermal conductivity, thickness, and usage

• Dielectric — Loss tangent and technology
• Metal — Bulk resistivity and temperature coefficient

Note
After you import into the back-end, load the stackup changes into the layout design by
clicking the rightmost indicator light in the layout tool (do not use the Project Integration
dialog box to accomplish this). You can also load the changes by instead closing and reopening
Constraint Manager.

Examples
Import a 10-Layer HyperLynx Stackup Into a Design With a 10-Layer Stackup
ImportStk -input c:\stackups\10_layer.stk
-prj c:\my_designs\design1\design1.prj

Import a 4-Layer Polar Speedstack Stackup Into a Design With a 6-Layer Stackup
ImportStk -input c:\stackups\3metal_layer.stkx
-prj c:\my_designs\design1\design1.prj -map_layers 1,2,5,6

Related Topics
Stackup File Import

Constraint Manager User's Manual, X-ENTP VX.2.8 577

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Command-Line Tools Reference
sandboxfile

sandboxfile
Use sandboxfile to both create and assign parallelism rules defined in a ParallelRules.txt file.
Usage
..\SDD_HOME\common\<OS>\bin\sandboxfile -pr ParallelRules.txt file
-prj .prj file -sn name -tb name -log path
Arguments
• -pr ParallelRules.txt file
ParallelRules.txt file that contains the rule set.
• -prj .prj file
.prj file for the design.
• -sn name
Snapshot name.
• -tb name
Topblock name.
• -log path
Create a log file at the specified path.
Description
This commands creates unique noise rules as needed based on the assignment of new
parallelism rules between nets or net classes.

Tip
To determine the path to the .prj file, snapshot name, and other similar information, you can
use iCDB Server Manager. Choose Tools > iCDB Server Manager.

Examples
sandboxfile -pr c:\data\ParallelRules.txt
-prj c:\my_designs\design1\design1.prj -sn DXD -tb top

Related Topics
Importing Parallelism Rules
ParallelRules.txt File Format

578 Constraint Manager User's Manual, X-ENTP VX.2.8

Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
 Index

Constraint Class or Electrical Net Name

Index

— Symbols — Aggressor, 554

(Minimum) scheme, 209 Constraint Class or Electrical Net Name
# Pins, 460, 461, 526, 527, 528, 529 Victim, 553
# Vias Max, 473 Constraint Manager, 83
— Numerics — Constraint Reference, 393
2-pin, 99 Constraint template
Apply, 328
—A— Convergence Tolerance Max, 519
Analog, 462 Cross probing, 19, 36, 95
Auto bus, 196 Cross select, 19, 36, 95
Crosstalk Level, 557
—B— Crosstalk Max, 556
Back-end, 385 Crosstalk rules, 322
Before you begin, 86 Customization, 110
Bus, 463
Bus constraint classes, 196 —D—
Default
—C— Rules, 208
Capture net constraints, 325 Delay
Clearance rule sets Calculations, 265
Assign, 43, 225
Default value, 265
Create, 216 Delete
Clearances, 409 Constraint class, 198
Colors, 103 Net class, 190
Command quick-reference, 64 Design
Commands, 64 Preferences, 97
Component pin pairs, 256 Reuse, 334
Concurrent design, 84 Setup, 97
Constraint Design-flow manuals, 385
Classes, 31, 191 Differential Impedance Target, 523
Groups, 49, 156 Differential Impedance Tolerance, 524
Templates, 326 Differential pair
Constraint class Assign rules, 304
Add nets, 194 Define automatically, 46, 301
Auto bus, 196 Define manually, 29, 299
Copy, 198 Diff_Pin, 308
Create, 31, 191 Differential Spacing, 407, 522
Delete, 198 Discrete component prefixes, 99
Hierarchy, 192 Display

Constraint Manager User's Manual, X-ENTP VX.2.8 579

 Settings, 97 —I—
Units, 104 I/O Designer I/O Standard, 525, 550
Distance to Convergence Max, 520 IBIS Component Name, 537
Dynamic High Overshoot Max, 498 IBIS Pin Type, 540
Dynamic Low Overshoot Max, 496 Import constraints, 343
Improve design accuracy, 83
—E— Index (Clearances), 412
EBD pin pairs, 259 Index (Trace and Via Properties), 397
Electrical Index (Z-Axis Clearances), 446
Preferences, 98 Intellectual property, 83
Rules, 31, 191 Interdigitated capacitors, 222
Units, 106 Interface quick-reference, 69
Embedded Resistor to Pad, 427
Embedded Resistor to Resistor, 429 —L—
Embedded Resistor to Trace, 426 Layout, 385
Embedded Resistor to Via, 428 Length or TOF Delay Delta, 490
Embedded resistors, 221 Length or TOF Delay Manhattan, 486
Engineering format, 107 Length or TOF Delay Match, 488
EP Mask to Pad, 431 Length or TOF Delay Max, 484
EP Mask to Resistor, 433 Length or TOF Delay Min, 482
EP Mask to Trace, 430 Length or TOF Delay Min Length, 487
EP Mask to Via, 432 Length or TOF Delay Range, 491
Export Length or TOF Delay Tol, 489
Constraint Templates, 334 Length or TOF Delay Type, 481
Constraints, 339, 341
—M—
—F— Manhattan length, 266
Filters, 152, 155 Mask, 223
Find, 150 Matching delay, 266
Fonts, 103 Max Restricted Layer Length External, 476
Formulas, 271 Max Restricted Layer Length Internal, 477
Formulas Formula, 492 Mezzanine capacitors, 222
Formulas Violation, 493 Monotonic Edge, 502
FPGA constraints, 293
From To Constraints Layer, 478 —N—
From To Constraints Trace Width, 479 Navigator, 110
From To Constraints Z0, 480 Net Class, 464, 466, 467
From-tos, 245 Net class
Front-end, 84 Add nets, 188
Copy, 189
—G— Create, 28, 187
General Delete, 190
Options, 97 Net line ordering, 245
Preferences, 97 Nets, 452
Global rules, 24, 205 Noise Rules, 551
GUI quick-reference, 69 Noise Type, 552

580 Constraint Manager User's Manual, X-ENTP VX.2.8

—O— Signal edge rates, 280
Options, 97 Simulated Delay Edge, 505
Output, 110, 111 Simulated Delay Match, 510
Overshoot, 283 Simulated Delay Match To, 509
Simulated Delay Max, 507
—P— Simulated Delay Max Range, 508
Pad to Plane, 421 Simulated Delay Min, 506
Pad to Via, 420 Simulated Delay Offset, 511
Pair Tol Max, 513 Simulated delay rules, 280
Parallelism, 310 Simulated Delay Tol, 512
Parallelism mode, 98 Single Ended Characteristic Impedance Tol,
Parallelism Rule, 555 504
Parallelism rules, 55, 310 Single Ended Characteristic Impedance Value,
Assign, 58, 313 503
Parallelism rules hierarchy, 310 SMD Pad to Trace, 418, 451
Part Number, 533 SMD Pad to Via, 424
Part Type, 535 Spreadsheet pages, 139
Parts, 530 Stackup, 359
Pin Package Length, 543 Stackup layers, 55, 310
Pin pairs, 246 Static High Overshoot Max, 495
Plane to Plane, 425 Static Low Overshoot Max, 494
Production mask, 223 Static overshoot, 283
—Q— Status Bar, 111
Qty, 534 Stub Length Max, 471

—R— —T—
Reuse, 334 Technology, 538
Ringback, 283 Thermal Casing Temperature Limit, 548
Ringback Margin High Min, 500 Thermal Junction Temperature Limit, 549
Ringback Margin Low Min, 501 Thermal Power Dissipation, 545
Roll back, 181 Thermal Power Scaling Factor, 546
Route, 401 Thermal Theta-jc, 547
Rules, 309 Thick-film resistors, 221
Thin-film resistors, 221
—S— Toolbars, 111
Same constraints Topology Ordered, 470
Electrical rules, 198 Topology Pin Type, 542
Physical rules, 189 Topology Type, 468
Save, 184 Trace and Via Properties, 395
Schematic, 385 Trace and via rules, 40, 210
Schematic Pin Type, 541 Trace to Plane, 417, 450
Screen-printed capacitors, 222 Trace to Trace, 414, 447
Search, 150 Trace to Via, 416, 449
Separation Distance Max, 521 Trace Width Expansion, 404
Series, 536 Trace Width Minimum, 402
Settings, 97 Trace Width Typical, 403

Constraint Manager User's Manual, X-ENTP VX.2.8 581

Type, 398, 413
Typical Impedance, 405
—U—
User interface quick reference, 69
—V—
Validate constraints, 174
Value, 539
Via Assignments, 400
Via rules, 40, 210
Via to Plane, 423
Via to Via, 422
—W—
Window customization, 110
—Z—
Z-axis clearance rule sets
Assign, 229
Z-Axis Clearances, 445

582 Constraint Manager User's Manual, X-ENTP VX.2.8

 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