Dxdesigner Ref

PADS Schematic Design Reference
Manual
Release PADS VX.2.1
2007-2016 Mentor Graphics Corporation

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

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

Table of Contents
Chapter 1
Design Entry Tool Interface and Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
User Interface - Design Entry Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
File Viewer Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Chapter 2
Support Files and Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Files Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Support File Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Borders Initialization File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Bus Contents File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Databook Tool Configuration File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
VerifyDefaults.ini (DRC Defaults). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
VerifyDefaults.ini (DRC Defaults) File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
DRC Defines Section - VerifyDefaults.ini File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
DRC Settings Section - VerifyDefaults.ini File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
DRC Checks Section - VerifyDefaults.ini File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
DRC Rules Section - VerifyDefaults.ini File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
DxDesigner.xml File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Part Lister Initialization File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
project.prj File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
xDX PDF Initialization File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
The Design Entry Tool Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Chapter 3
Dialog Boxes and Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Add Block Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Add Nets With Ports Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Add Pin Array Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Add Properties Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Array Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Cadence Allegro Netlister Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
CCZ Exporter Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Customize Tools Menu Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Customize Dialog Box - Toolbars Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Customize Dialog Box - Commands Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Customize Dialog Box - Options Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Databook Tool Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Databook Tool - CL View Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Databook Tool - CL View - Part View Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Databook Tool - CL View - Symbol View Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Databook Tool - CL View - Reuse Blocks Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
PADS Schematic Design Reference Manual, PADS VX.2.1 3

Table of Contents
Databook Tool - Configure Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

Databook Tool - Configure Dialog Box - Properties Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Databook Tool - Properties Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Databook Tool - Query Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
xDX Archiver Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
xDX PDF Dialog Box - General Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
xDX PDF Dialog Box - Advanced Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
xDX PDF Dialog Box - Fonts Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Find and Replace Text Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Font Mapping Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Generate Symbol Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Insert Object Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Keyin Netlister Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
LineSimLink Dialog Box - Options Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
LineSimLink Dialog Box - Schematic Topology Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Merge Differences Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
New Library Symbol Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
New Project Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Open Block Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Packager Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Select Parts to Update Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Part Lister Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Part Lister Dialog Box - General Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Part Lister Dialog Box - Advanced Pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Part Lister Dialog Box - Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Part Lister Dialog Box - Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Paste Special Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Properties Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Property Definition Editor Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Quick Connection View Dialog Box - General Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Quick Connection View Dialog Box - Display Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Quick Connection View Dialog Box - Advanced Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Replace Part Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Replace Symbol/Part Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
RINF Netlister Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Scale Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Settings Dialog Box - Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
Settings Dialog Box - Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Settings Dialog Box - Symbol Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Settings Dialog Box - Special Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Settings Dialog Box - Bus Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
Settings Dialog Box - Borders and Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Settings Dialog Box - Cross Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Settings Dialog Box - Net Name Delimiter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
Settings Dialog Box - Databook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Settings Dialog Box - Sheet Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Settings Dialog Box - Export HDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Settings Dialog Box - VHDL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Settings Dialog Box - Export HDL - External Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
4 PADS Schematic Design Reference Manual, PADS VX.2.1

Table of Contents
Settings Dialog Box - Export HDL - Port Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

Settings Dialog Box - Verilog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
Settings Dialog Box - Schematic Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Settings Dialog Box - Strokes, Pan and Zoom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Settings Dialog Box - New Sheets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
Settings Dialog Box - Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Settings Dialog Box - Nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Settings Dialog Box - Selection Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Settings Dialog Box - Symbol Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
Settings Dialog Box - Symbol Editor - Symbol Default Properties . . . . . . . . . . . . . . . . . . . 335
Settings Dialog Box - Symbol Editor - Pin Default Properties . . . . . . . . . . . . . . . . . . . . . . . 337
Settings Dialog Box - Symbol Editor - Symbol HLA Properties . . . . . . . . . . . . . . . . . . . . . 339
Settings Dialog Box - Graphical Rules Checker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
Settings Dialog Box - Interconnectivity Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Settings Dialog Box - ICT - Slice and Dice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
Settings Dialog Box - ICT - Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Settings Dialog Box - Navigator - Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
Settings Dialog Box - Navigator - Sheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
Settings Dialog Box - Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Settings Dialog Box - Navigator - Nets and Buses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Settings Dialog Box - Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
Settings Dialog Box - Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
Settings Dialog Box - Font Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
Settings Dialog Box - xDX Designer Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
Settings Dialog Box - Cross Probing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Settings Dialog Box - Sheet/ICT Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Settings Dialog Box - Project Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
Settings Dialog Box - Integrated Simulator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Settings Dialog Box - FPGA Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Settings Dialog Box - Run on Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
Settings Dialog Box - xDX Databook Data Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Settings Dialog Box - Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
Settings Dialog Box - Advanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
Simulation Setup Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
Update Other Objects Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
Verify Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
Verilog Netlister Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
VHDL Netlister Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
Chapter 4
Design Entry Tool Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Shell-Level Design Entry Tool Command Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Shell-Level Design Entry Tool Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
icdbPartsLister . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
DxArchiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
sch2pdf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
vdrc (Design Rule Checker) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405

Table of Contents
Design Entry Tool Command Line Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Chapter 5
Property Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Visibility Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Property Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
Property Name and Value Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
Netlist Interpretation of Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
User-Defined Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
Multiple and Duplicate Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
Multiple Property Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
Property Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
Chapter 6
Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
Illegal Characters in Name Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
Unnamed Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
Name Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
Compound Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
Unique Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
Pin Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Bus Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Chapter 7
Key Bindings and Strokes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Key Bindings - Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Key Bindings - xPCB Layout Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
Key Bindings - PADS Style. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
Chapter 8
Design Entry Tool Diagnostics Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
Diagnostics Tool Tests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
DRC Rule Notes and Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
DRC Property and Label Syntax Using Regular Expression Syntax . . . . . . . . . . . . . . . . . . 453
DRC Regular Expression Ambiguity Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
DRC Verify Tool Defaults File Search Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
Prerequisites for DRC Electrical Checks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
Appendix A
Supplemental Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
Design Entry Tool COLORS Element. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
LineSimLink - Passives Prefixes - Models Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
Pin (Port) Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
Property Editing Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
Verilog HDL Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
Verilog HDL Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
Verilog HDL Parameters as User-Defined Name/Value Pairs . . . . . . . . . . . . . . . . . . . . . . . 470

Table of Contents
Verilog HDL Parameters Used as Physical Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472

Using Parameters in Verilog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
How the VHDL Netlist is Processed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
Example VHDL Netlist Output File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
The QCV Netlist Output Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
Search Query Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
Regular Expression Syntax in Text Searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
Numeric Operators for Databook Tool Search Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . 482
Wildcard Characters for Databook Tool Search Conditions . . . . . . . . . . . . . . . . . . . . . . . . . 483
Index
Third-Party Information
End-User License Agreement

Table of Contents

Chapter 1
Design Entry Tool Interface and Utilities
The following describes some of the windows and utilities associated with the
PADS DX Designer interface as follows:
User Interface - Design Entry Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
File Viewer Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
User Interface - Design Entry Tool

This topic identifies PADS DX Designer windows in various configurations.
Video
PADS DX Designer UI Introduction Click to view a video demonstrating the basic user
interface capabilities.
Note
The Design Entry Tool Start Page Click to view a short video demonstrating the Start
page capabilities.
Video
Toolbar Tooltips Click to view a short video demonstrating the toolbar button tooltips.

User Interface - Design Entry Tool
Figure 1-1. PADS Schematic Design Interface With Various Uitility Windows
Displayed

File Viewer Utility
Figure 1-2. Design Entry Tool with Project Integration Window Displayed
Related Topics
User Interface Customization - xDX Designer
File Viewer Utility

The File Viewer utility allows you to view the contents of log files generated by the design entry
tool. These files are located in the project's ./LogFiles folder. Options are provided from the
pulldown menus to delete, rename, print, send, copy, find, list with or without details, and
arrange by Name, Size or Date.
The File Viewer utility is available from the File > File Viewer pulldown menu or from the
toolbar button.
Note
You cannot copy and paste sections of one File Viewer file into another File Viewer file.

File Viewer Utility
The Workspace is divided into two areas: the left hand side lists the files, the right hand side
displays the text of the selected file. Figure 1-3 shows the File Viewer window with the buttons
identified with their associated menu path. The List button (see figure inset) provides a simple
list of files, whereas the Details button provides additional file information.
Figure 1-3. File Viewer Window
Many of the commands are also available from popup menus when you right-click the mouse
button.
If the right mouse button is clicked in the list of files, the popup menu displays View and
Arrange commands as shown below on the left. If a file is highlighted in the list of text files
during the right-click, the popup menu displays Print, Delete and Rename commands as shown
below on the right.

File Viewer Utility
You can print only relevant information by highlighting the portion of text you want before
using the File > Print command. If text is not highlighted within the file, the whole file is
printed.
If you exit the application without exiting File Viewer, you will have to manually close File
Viewer.
Related Topics

File Viewer Utility

Chapter 2
Support Files and Variables
The following topics provide information on some of the PADS DX Designer design entry
tools support files and variables:
Files Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Support File Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Borders Initialization File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Databook Tool Configuration File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
VerifyDefaults.ini (DRC Defaults). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
DxDesigner.xml File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Part Lister Initialization File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
xDX PDF Initialization File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
The Design Entry Tool Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Files Summary
The following table describes some of the files that the design entry tools use to control their
behavior and appearance. You can customize many of the settings stored in these files from the
design entry tool user interface, or in the files themselves.
Table 2-1. Design Entry Tool Support Files Listing

Filename Description
addins.ini Supports the configuration of custom Add-ins.
borders.ini Stores schematic border assignment settings specified from Setup >
Settings, Project (category), Borders and Zones (subcategory). You
specify the location of this .ini file from Setup > Settings, Project
(category), Border Symbols (field).
Related Topics:
Borders Initialization File Format on page 22
Controlling Sheet Borders - xDX Designer
busconts.ini Replaces the conts.bc file from releases prior to 2007.
Related Topic:
Bus Contents File Format on page 27

Files Summary
Table 2-1. Design Entry Tool Support Files Listing (cont.)

<layout_system>.cfg Defines the attributes that are passed to the layout system. The
files configuration files also perform error checking. You can control the
level of error checking (ERROR, WARNING, or NOTE). You can
also define rules for self-correction (for example, to replace illegal
characters with legal characters).

Client.cfg This Client-Server Configuration Manager client file is located at
%WDIR%\iCDB\Client\Client.cfg.
Related Topic:
Client.cfg Configuration File in the Concurrent Design
Administrators Guide.
commontools.ini The design entry tool stores customized common menu commands
(Tools > Customize) in this file in the
\<mentor_home>\<release>\SDD_HOME\standard directory.
Related Topic:
Customize Tools Menu Dialog Box on page 187
dashtools.ini Controls custom toolbox on the Dashboard.
.dxc files Contains color definition schemes that you can load or save from
Setup > Settings, Display (category), Objects (subcategory)
.dbb file Controls which .dbc file is loaded into DataBook.
Related Topic:
Creating a Databook Configuration File
.dbc file Connects the Databook tool to an ODBC database.
Related Topic:
Databook Tool Configuration File Format on page 29
dxpdf.ini Stores default DxPDF settings in
\<mentor_home>\<release>\SDD_HOME\standard\dxpdf.ini. Any
setting changes you make are stored in a dxpdf.ini file in your
project directory. DxPDF reads your WDIR variable and chooses
the settings in first dxpdf.ini file it finds in the path during
execution.
Related Topics:
Exporting Design Documentation in PDF Format - xDX
Designer
xDX PDF Dialog Box - General Tab on page 217

Files Summary

DxArchiver.xml Contains the settings you use when you run Tools > Archiver. The
tool also creates the file manifest.xml.
Related Topic:
Project Archive
DxDesigner.xml The primary Setup configuration file that replaced the viewdraw.ini
and draw.ini files that were used prior to Release EE2007. Contains
user preferences set from the Setup > Settings (dialog box).
Related Topic:
DxDesigner.xml File Format on page 53
DxDesigner.wsp Stored in your WDIR to record your design entry tool window
placement from your last session. There are multiple versions of this
file for each project type, such asDxDesignerNL.wsp,
DxDesignerPADS.wsp,.
To restore your session to the default window placement, delete
these files. A new file is created the next time you invoke the design
entry tool.
See also:
Saving and Restoring the Window Configuration - xDX Designer
hdlutils.ini Created from running the Tools > Simulation Setup utility or File
> Export > VHDL Netlist or File > Export Verilog Netlist. All
netlister settings are stored in this hdlutils.ini file that is created in
the project directory during creation of the VHDL or Verilog netlist.
Related Topics:
Verilog Netlister Dialog Box on page 391
VHDL Netlister Dialog Box on page 392
Launcher.cfg This Client-Server Configuration Manager file is located only on
machines that run the service/daemon in
%WDIR%\iCDB\Launcher\Launcher.cfg.
Related Topic:
Launcher.cfg Configuration File in the Concurrent Design
Administrators Guide
locmap.cfg Contains variable definitions that define soft pathnames found in
your WDIR path.
<project_dir>/ When certain tools are run from the design entry tool, resulting log
LogFiles/ <tool>.log files are stored in <project>\LogFiles\<tool>.log

Files Summary

manifest.xml Lists the fileset used when you run Tools > Archiver. The file
DxArchiver.xml is also created.
Related Topic:
Project Archive
map.cfg Maps pre-v2007 design entry tool attributes to the current
equivalent property names. The tool searches for a map.cfg file in
the following locations in the following order:
1. Current project folder.
2. Each folder specified by the WDIR environment variable,
reading left-to-right.
Related Topic:
WDIR Variable Search Order
NetlistVerify.ini The Design Rule Checker (DRC) utility uses this .ini file (for Netlist
project designs) to store your projects DRC configuration settings,
such as which checks you chose to run, default values that are used,
and the message level specified (ERROR, WARNING or NOTE).
Related Topics:
VerifyDefaults.ini (DRC Defaults) File Format on page 40
Verify Dialog Box on page 387
Set Up the Verify Tool to Find Rule Violations - xDX Designer
NetlistVerifyDefaults.in The Design Rule Checker utility uses this .ini file (for Netlist
i project designs) to store initial default settings. It is stored in
\<mgc_home>\<release>\SDD_HOME\standard\ or %WDIR%.
Also see the description for NetlistVerify.ini.
Related Topics:
PathsMap.cfg This Client-Server Configuration Manager file is located at
%WDIR%\iCDB\PathsMap.cfg.


Files Summary

<project>.prj Contains the project-specific settings and configurations that are set
from the Setup > Settings (dialog). This file is stored under your
project directory. Templates are also created as .prj files and located
in specific locations.
Related Topics:
DxDesigner.xml File Format on page 53
Project Template File
scripts.ini Lists which scripts are loaded when the design entry tool starts.
scout.ini Contains Scout configuration settings. Scout is a cross reference
utility that supports hierarchy.
Related Topic:
Sample Scout.ini File in the Cross Referencing a Design
Server.cfg This Client-Server Configuration Manager server file is located at
%WDIR%\iCDB\Server\Server.cfg.
Related Topic:
Server.cfg Configuration File in the Concurrent Design
usertools.ini The design entry tool stores customized user-specific menu
commands (Tools > Customize) in this file in either the %WDIR%
location or the project location.
Related Topic:
Customize Tools Menu Dialog Box on page 187
Verify.ini The Design Rule Checker (DRC) utility uses this .ini file to store
your projects DRC configuration settings, such as which checks
you chose to run, default values that are used, and the message level
specified (ERROR, WARNING or NOTE).
Related Topics:

Files Summary

VerifyDefaults.ini The Design Rule Checker utility uses this .ini file to store initial
default settings. It is stored in
\<mgc_home>\<release>\SDD_HOME\standard or %WDIR%.
Also see the description for Verify.ini.
Related Topics:
Related Topics
Read-only User-Preference Settings

Support File Reference
Support File Reference

The support file reference topics describe the content of each file, and what you may or may not
edit in each file.
Borders Initialization File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Databook Tool Configuration File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
VerifyDefaults.ini (DRC Defaults) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
DxDesigner.xml File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Part Lister Initialization File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
xDX PDF Initialization File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Borders Initialization File Format

Input for: PADS DX Designer design entry tools schematic border settings
The design entry tool reads the specified ASCII borders.ini file to configure the schematic
border settings. You specify the location of this .ini file from Setup > Settings, Project
(category), Border Symbols (field).
The borders.ini file stores schematic border assignment settings specified from Setup >
Settings, Project (category), Borders and Zones (subcategory).
Format
The file is composed of five sections as shown in bold below:
Figure 2-1. borders.ini File Content Overview
[SYMBOLS]
This section defines a border symbol for specified sheet sizes and
orientation.
Syntax Example:
Sheet=symbol_name
In the syntax example, Sheet specifies the size and orientation of the
sheet, symbol_name is name of the border symbol
Example:
A0SHEETL=Borders:a0sheet.1 (Defines the symbol for landscape oreientation)
A0SHEETP=Borders:a0sheet.2 (Defines the symbol for portrait orientation)
. . .
[ZONE A0SHEETL] (A zone exists for each configured sheet.

A0SHEETL is used as an example to match the sheets defined above.)
(See VerticalZones and HorizontalZones descriptions for content of this
section)
[ZONE A0SHEETP]
. . .
[ATTRIBUTES]
This section defines a set of properties that are attached to each border
symbol instance when a border is added or changed.
Syntax Example:
property_name1=property_value1
property_name2=property_value2
Example:
DEVELOPER=Thomas
COMPANY=ACME

[ANNOTATIONS]
This section describes the annotation format for links (from Setup >
Settings, Project (category), Cross Reference (subcategory). The
definition is stored here if it differs from the default form of the
following
Example:
FORMAT=$(sheet)-$(vzone)$(hzone)
[DEFAULTS]
This section defines default values for border properties.
Syntax Example:
property1=value1
property2=value2;value3;value4
Parameters
The following tables list the setting names and describe the editable parameter values in each
section of the borders.ini file.
Table 2-2. borders.ini - ZONE <SHEET_TYPE> Section
Setting Name Setting Description
HORZLABELING Specifies whether numbers or letters are used to denote the horizontal
zones, and whether the numbers or letters are ascending or descending
as shown in the following:
GUI access:
Setup > Settings,
Project (category), Borders and Zones (subcategory), Horizontal Zones
(section), Letters, Numbers, and Descending (options)
HORZNUMBER Specifies the number of horizontal zones on the schematic, such as in the
following example:
HORZNUMBER=8
GUI access:
Setup > Settings, Project (category)
Borders and Zones (subcategory), Horizontal Zones (section), Number
of Zones (option)

Table 2-2. borders.ini - ZONE <SHEET_TYPE> Section (cont.)

OFFSETBOTTOM Specifies the bottom offset in the specified units for the horizontal zones
on the schematic such as in the following example:
OFFSETBOTTOM=1270000
You need to enter a value as: (value in millimeters) * 100,000.

A value of 1.27e+006 sets the offset to 12.7mm, or .5in.
GUI access:
Setup > Settings, Project (category), Borders and Zones (subcategory),
Horizontal Zones (section), Bottom Offset (option)
OFFSETTOP Specifies the top offset in the specified units for the horizontal zones on
the schematic such as in the following example:
OFFSETTOP=1270000

GUI access:
Horizontal Zones (section), Top Offset (option)
VERTLABELING Specifies whether numbers or letters are used to denote the vertical
zones, and whether the numbers or letters are ascending or descending
as shown in the following:
GUI access:
Vertical Zones (section), Letters, Numbers, and Descending (options)
VERTNUMBER Specifies the number of vertical zones on the schematic, such as in the
following example:
VERTNUMBER=10
GUI access:
Vertical Zones (section), Number of Zones (option)

Table 2-2. borders.ini - ZONE <SHEET_TYPE> Section (cont.)

OFFSETLEFT Specifies the left offset in the specified units for the vertical zones on the
schematic such as in the following example:
OFFSETLEFT=2540000

A value of 2.54e+006 sets the offset to 25.4mm, or 1.0in.
GUI access:
Vertical Zones (section), Left Offset (option)
OFFSETRIGHT Specifies the right offset in the specified units for the vertical zones on
the schematic such as in the following example:
OFFSETRIGHT=2540000

A value of 2.54e+006 sets the offset to 25.4mm, or 1.0in.
GUI access:
Setup > Settings, Project (subcategory), Borders and Zones
(subcategory), Vertical Zones (section), Right Offset (option)

Table 2-3. borders.ini - ANNOTATIONS Section

FORMAT Specifies the appearance of cross reference links by using the cross-ref
variable as shown in the following default example:
FORMAT=$(sheet)-$(vzone)$(hzone)-$(block)
You can also insert text in the FORMAT specification.

GUI access:
Setup > Settings, Project (category), Cross Reference (subcategory),
Annotation Format for Links (option)
Related Topics
Settings Dialog Box - Borders and Zones
Sheet Borders

Bus Contents File Format

Input for: PADS DX Designer bus bundle information
PADS DX Designer reads pre-defined bus information from an ASCII busconts.ini file. You
specify the location of this .ini file from Setup > Settings, Project (category).
Format
The default busconts.ini filename replaces the conts.bc filename used in releases prior to 2007.
When PADS DX Designer loads a project, if a bus contents file for that project is specified in
the <design_name>.prj file such as the following:
SECTION DesignInfo
. . .
KEY Bus_Contents busconts.ini
. . .
ENDSECTION
the bus information contained in that file is loaded into PADS DX Designer.
Parameters
The contents of the 2007 and beyond busconts.ini file and the older conts.bc bus contents
file use similar formatting as follows:
$FORMAT_CAR Define header in pre-2007 conts.bc files.

D$ (Not used with the busconts.ini file)
nA mC (Not used with the busconts.ini file)
$END$ Terminate header in conts.bc.
(Not used with the busconts.ini file)
bus_net_name signal_name1,signal_name2,
signal_name1,signa signal_name3,signal_name4,
l_name2,
Field Description
nA The maximum size of the bus net name field.
(Not used with busconts.ini)
mC The size of the bus contents field. m is less than 64K.
(Not used with busconts.ini)
bus_net_name The value of the Net Name text property you assign to the bus.
signal_name The signal names you assign, separated by a comma. The signal
names must be separated with a comma.

o Each line of the contents file can have up to 10,000 characters.

o Use an ampersand (&) at the end of a line to continue a bus definition on another
line.
Note, the continuation (second) line must also have the bus_net_name at the
beginning. See the following example:
Bus1 net1,net2,&
Bus1 net3,net4
o When using signal names that contain spaces, all of the signal names must be
enclosed in double-quotes ( ). Although this is allowed, it is not a recommended
practice.
o Nested buses are not supported.
Examples
The following is an example of a busconts.ini bus contents file:
CPU_BUS ADR[0:15],DATA[0:8],CTL[0:3],&
CPU_BUS INAP[0:25],ADV[0:7]
MEM_BUS "ADR[0:10],CONTROL[10:20],NETNAME WITH SPACE"
Related Topics
Creating and Editing Pre-Defined Buses - xDX Designer
Connectivity With Buses - xDX Designer

Databook Tool Configuration File Format

Input for: The design entry tools Databook tool.
The configuration (.dbc) file is an ASCII file that uses standard XML formatting. Use the .dbc
file to connect the Databook tool to an ODBC database.
You can edit the file elements and subelements with a text or XML editor.
Note
Editing the .dbc file may require deleting component libraries associated with the Data
Source Name (DSN) and adding libraries back to the file.
Format
A .dbc file must conform to the following formatting restrictions:
File sections appear in a specific order (see Table 2-4 on page 30):
1. Declaration Statement
2. dbc Element
3. CObject
4. CConfigSym
5. CConfigLib
6. CConfigLibEntry
7. CConfigAtt
8. CConfigTable
9. CConfigPref
10. CConfigScripting
11. End Statement
File content is case-sensitive.
Standard XML file syntax is:
<element attribute1="value1" ... > elements' contents </element>
The XML file elements can be nested and are called subelements.
For example:
<element>
<subelement1> ... </subelement1>

<subelement2> ... </subelement2>
</element>
If an element statement does not contain information, it appears in shorthand notation:
<element attribute1="value1" ... />
All XML file elements need to be numbered in order of appearance in the file.
For example,
<element1><element2><element3><element3><element4><element4><element1>
<element5><element5><element1>
See the subsection in this topic for a sample of an XML file containing nested and numbered
elements.
Table 2-4. XML File Structure
File Section Example Value Description
Declaration <?xml version="1.0" The file begins with a standard
Statement encoding="UTF-8"?> XML declaration which includes a
UTF-8 encoding statement.
dbc Element <dbc version="1.0"> The dbc element is the top-level or
main element of the XML file with
version number as its attribute
(this element contains all of the
other file elements/subelements).
CObject <CObject0 overallSchema="21" CObject contains the Databook
flag="DX Databook Overlay main configuration (CConfig
Configuration File" element) and internal window data
BaseConfigurationURL=""> (CObList element).
<CConfig1>
... Note: Do not modify the
CObList element or its
</CConfig1> attributes.
<CObList128 CPersistList="0"/>
</CObject0>
CConfigSym <CConfigSym2> CConfigSym contains the list of
<CObArray3 symbols and it is a subelement of
CXMLTypedPtrArraySize="0"/> CConfig.
</CConfigSym2>
Note: CConfigSym cannot be
used to store symbols.

Table 2-4. XML File Structure (cont.)

CConfigLib <CConfigLib4> CConfigLib contains the list of
<CObArray5 libraries, and it is a subelement of
CXMLTypedPtrArraySize="8"> CConfig with the following
subelements:
<CConfigLibEntry6 > ... </
CConfigLibEntry6> CObArray which has the
following subelements:
... CConfigLibEntry
</CObArray5> CConfigTableEntry
</CConfigLib4> Contains subelement
CStringList which lists all
table fields.
CConfigAtt
CConfigTable Contains the
list of tables
CConfigLibEntry <CConfigLibEntry6> CConfigLibEntry is a subelement
<CConfigAtt7 ... > ... </ of CObArray and it contains the
CConfigAtt7> DataBook library configuration.
<CConfigTable32> ... </
CConfigTable32>
</CConfigLibEntry6>
CConfigAtt <CConfigAtt7 CConfigAtt contains the list of
UseCentralLibrarySymbols="0"> properties and it is a subelement of
<CObArray8 CConfigLib (CConfigAtt has
CXMLTypedPtrArraySize="2"> subelement CConfigAttEntry).
<CConfigAttEntry9> ... </
CConfigAttEntry> Note: CConfigAttEntry is also
a subelement of CObArray.
<CConfigAttEntry9> ... </
CConfigAttEntry>
</CObArray8>
<CConfigAtt7>
CConfigTable <CConfigTable32> CConfigTable contains the list of
<CObArray33 tables and it is a subelement of
CXMLTypedPtrArraySize="1"> CConfigLib (CConfigTable has
subelement CObArray).
<CConfigTableEntry34> ... </
CConfigTableEntry34>
</CObArray33>
</CconfigTable32>

Table 2-4. XML File Structure (cont.)

CConfigPref <CConfigPref125 CConfigPref contains the
LoadIntoNewWindow="0" configuration file preferences and
SymbolAttributesGet-Loaded="0" it is a subelement of CConfig.
ComponentTracking="1"
AnnotateUndefinedAttributes="0"
Chan-geCompEnabled="0"
ComponentTrackingZoom="0"
MaintainAttVisibility="0"
LibraryAttEnabled="1"
LibraryAttName="DXDB_LIBNA
ME" AnnotateUndefine-
dAttributesValue=""
UseLoadTabAttribute="0"
LoadTabAttributeName="" An-
notateSelected="0"
AnnotateSelectedPrefix="ALT_*"
AnnotateRemoveAttri-butes="1"
ExcludedAttList="REFDES"/>
CConfigScripting <CConfigScripting126 CConfigScripting is a subelement
OnAddComponentEnabled="1" of CConfig and it contains
OnAnnoComponentEnabled="1" Databook scripting (automation
OnLoadComponentEnabled="1" control) information.
OnSelectComponentEnabled="1" CConfigScripting has subelement
On-ViewDocumentEnabled="1" CConfigScriptLanguage.
OnAfterAddComponentEnabled="1
" OnAfterAnnoCom-
ponentEnabled="1">
<CConfigScriptLanguage127
Filename="" type="0" pro-
gID="VBScript"/>
</CConfigScripting126>
End Statement </dbc> The file ends with the XML end
statement.
Parameters
Table 2-5. Element/Subelement Attributes
Element/Subelement Attribute Description
CConfigAtt UseCentralLibraryS Symbol data from Central Library is used.
ymbols="0" Values are 0 (disabled) and 1 (enabled).

Table 2-5. Element/Subelement Attributes (cont.)

CConfigAttEntry Fieldname="ID" Name of column in ODBC data source
table.
AttName="ID" Name of property as it appears in Databook
and the design entry tool.
DefaultValue="" Value used if property not present (value
dependent on property).
ExcludeWhenAnnot Properties to exclude when back-
ating="0" annotating to PADS DX Designer. Values
are 0 (disabled) and 1 (enabled).
ExcludeWhenLoadi Properties to exclude when loading into
ng="0" Databook. Values are 0 (disabled) and 1
(enabled).
m_bNameVisible=" Property names are visible in the design
0" entry tool schematic after back-annotating.
Values are 0 (disabled) and 1 (enabled).
m_bValueVisible=" Property values are visible in the design
0" entry tool schematic after back-annotating.
Values are 0 (disabled) and 1 (enabled).
AttType="0" Field type. Values are 0 (Normal), 1
(Symbol), 2 (Document), 3 (Unused), 4
(Unique ID).
ValueType="0" Type of value. Values are 0 (Undefined), 1
(String), 2 (Numeric), 3 (Numeric_Int), 4
(Numeric_Float), 5 (Numeric_Double).
MagType="0" Numeric property values displayed in
Databook. Values are 0 (Unknown), 1
(Atto), 2 (Femto), 3 (Pico), 4 (Nano), 5
(Micro), 6 (Milli), 7 (Unity), 8 (Kilo), 9
(Mega), 10 (Giga), 11 (Tera), 12 (Auto), 13
(Percent).
UnitsString="" Unit suffix annotated to symbols. Values
are expressed as a string (for example,
mm or in).
AddAsOat="0" For internal use only.
Required="0" Properties that are required. Values are 0
and 1 (property is required and included).


ValidMag="2047" Valid magnitude for selected property.
Value is the number, which is interpreted
as a binary mask that enables values
described in MagType (each MagType
value is interpreted as one bit).
ValidMagDir="63" For internal use only.
FutureUseBool1="0 For internal use only.
",
FutureUseBool2="0
",
FutureUseStr1="",
FutureUseStr2=""
MatchCondition="- SQL database language relation used for
" matching.
=: exact match. For example, entering a
value of 50, only results in a match of 50.
Like: matches a character pattern using
wildcards. For example, entering a value of
*50, results in matches of ALS150, DP50,
and so on. Entering a value of *50*, results
in matches of ALS0500, ALS0505_sp, and
so on.
Note: Only applicable if Databook is
used by Variant Manager.
AttrUnplace="0" Property placement. Values are 0 (Name),
1 (Value), 2 (NameAndValue), 3 (Hide), 4
(Delete), 5 (None).
SerialKey="0" For internal use only.
CConfigLibEntry LibraryName="nam Library name.
e"
JoinTable="false" Tables linked to provide access to
component properties that reside in
multiple tables. Values are true or
false.
Locked="0" For internal use only.
SymbolExpression= Symbol expression used to find a valid
"" symbol.


JoinType="0" Tables linked vertically or horizontally.
Values are 0 (vertical join) or 1 (horizontal
join).
HorizJoinType="0" Records from tables combined if values of
joined fields meet specified criteria (inner
join) or records included even if related
records are not in joined tables (left outer).
Values are 0 (inner) or 1 (left outer).
CConfigPref LoadIntoNewWind New window is created when components
ow="0" loaded. Values are 0 (window not created)
or 1.
SymbolAttributesG Symbol properties loaded along with
etLoaded="0" component properties. Values are 0
(properties not loaded) or 1.
ComponentTrackin Automatic selection of component in the
g="0" design entry tool when selected in Search/
Verify windows. Values are 0 (component
not selected) or 1.
AnnotateUndefined Values matching undefined value are
Attributes="0" annotated. Values are 0 (values not
annotated) or 1.
ChangeCompEnabl New symbol can be overwritten when
ed="0" annotating to a component. Values are 0
(symbol not overwritten) or 1.
ComponentTrackin Zoom To Fit is performed on selection.
gZoom="0" Values are 0 (Zoom To Fit not performed)
or 1.
MaintainAttVisibilit Properties change their visibility when
y="0" annotated. Values are 0 (visibility not
changed) or 1.
LibraryAttEnabled= Special library property is annotated.
"0" Values are 0 (property not annotated) or 1.
LibraryAttName=" Name of the property which holds the
DXDB_LIBNAME library name (for example,
" DXDB_LIBNAME).
AnnotateUndefined String to match values (if a value matches,
AttributesValue="" it is not annotated).


UseLoadTabAttribu Load tabs in the Databook Search window
te="0" use LoadTabAttributeName. Values are
0 or 1 (load tabs use
LoadTabAttributeName).
AnnotateSelected=" Annotate properties to selected
0" components. Values are 0 (not enabled) or
1.
AnnotateSelectedPr AnnotateSelectedPrefix used in
efix="ALT_*" conjunction with AnnotateSelected
attribute.
AnnotateRemoveAt Properties without values are removed
tributes="0" during annotation. Values are 0 (properties
not removed) or 1.
ExcludedAttList="R Comma-separated list of properties to be
EFDES" excluded when loading (for example, Ref
Designator).
CConfigScripting OnAddComponentE OnAddComponentEnabled automation
nabled="1" callback is enabled. Values are 0 or 1
(enabled).
OnAnnoComponent OnAnnoComponentEnabled automation
Enabled="1" callback is enabled. Values are 0 or 1
(enabled).
OnLoadComponent OnLoadComponentEnabled automation
Enabled="1" callback is enabled. Values are 0 or 1
(enabled).
OnSelectComponen OnSelectComponentEnabled automation
tEnabled="1" callback is enabled. Values are 0 or 1
(enabled).
OnViewDocumentE OnViewDocumentEnabled automation
nabled="1" callback is enabled. Values are 0 or 1
(enabled).
OnAfterAddCompo OnAfterAddComponentEnabled
nentEnabled="1" automation callback is enabled. Values are
0 or 1 (enabled).
OnAfterAnnoComp OnAfterAnnoComponentEnabled
onentEnabled="1" automation callback is enabled. Values are
0 or 1 (enabled).
CConfigScriptLanguage Filename="" Script filename.


type="0" Script programming language. Values are
0 (VBScript), 1 (JScript), 2 (User-
Defined).
progID="VBScript" User-defined programming language
name.
CConfigTableEntry Assembly="ODBC; Data source configuration file.
ALIAS=SampleLib;
CNS={ODBC;DSN
=SampleLib};DDS
={Microsoft Access
Driver (*.mdb)};"
TableName="Capac Database table name (for example,
itors" Capacitors).
CObArray CXMLTypedPtrArr Value is number of libraries listed in
aySize CObArrayElement.
CStringList ListSize="1" Number of fields stored in properties.
Value is number of fields (decimal format).
ListItem0="ID" Lists of different types in .dbc file format.
Values are dependent on list type used.
dbc overallSchema="21 Internal version number.
"
flag="xDX File type with
Databook Base
Configuration File" "xDX Databook Overlay Configuration
File"
or
"xDX Databook Overlay Configuration

File" BaseConfigurationURL="">
values.
Note: For flag="xDX Databook Base

Configuration File", the value is the
.dbb file (see Databook to Data Sources
Connections for more information).

Examples
<?xml version="1.0" encoding="UTF-8"?>
<dbc version="1.0">
<CObject0>
<CConfig1>
<CConfigSym2>
<CObArray3/>
</CConfigSym2>
</CConfig1>
<CObList4/>
</CObject0>
</dbc>
Related Topics
Databook Configuration File Overview

VerifyDefaults.ini (DRC Defaults)

The design entry tool Design Rule Checker (DRC) Verify tool uses the VerifyDefaults.ini file to
configure the checker.
The file description is broken into the following topics:
VerifyDefaults.ini (DRC Defaults) File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

DRC Defines Section - VerifyDefaults.ini File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
DRC Settings Section - VerifyDefaults.ini File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
DRC Checks Section - VerifyDefaults.ini File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
DRC Rules Section - VerifyDefaults.ini File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

VerifyDefaults.ini (DRC Defaults) File Format

Input for: PADS DX Designer design entry tools Design Rule Checker (DRC) Verify tool
The design entry tool reads one or more ASCII VerifyDefaults.ini files along your WDIR path
to configure the design entry tools Verify tool settings. A Verify.ini file located in the project
folder stores your local settings. The settings stored in the local Verifiy.ini file take precedence
over those stored in the VerifyDefaults.ini file.
For more information on why the design entry tool uses more than one copy of this file and how
the design entry tool accesses them, see DRC Verify Tool Defaults File Search Order on
page 455.
You can modify a .ini file to set up your own DRC Verify tool default settings to do the
following:
Change the default settings on the Settings pane

Do the following on any of the Rules panes:
o Change the default value for a particular Rule check
o Change the rule check visibility
o Add your own groups and assign certain Rule checks to them
o Choose which check(s) you want to appear under each group
Format
The VerifyDefaults.ini file is an ASCII file that uses standard XML formatting. The content is
divided into major sections as shown in Figure 2-2.
Figure 2-2. VerifyDefaults.ini File Section Structure
<?xml version="1.0"?>
<VDRC>
<FlowType Name="<name>" />

<Checks>

</Checks>
<Defines>

</GUI>
</VDRC>

The following topics describe the sections of code in a VerifyDefaults.ini file to help you relate
the file contents to the DRC dialog box panes:
DRC Defines Section - VerifyDefaults.ini File on page 42

DRC Settings Section - VerifyDefaults.ini File on page 46
DRC Checks Section - VerifyDefaults.ini File on page 48
DRC Rules Section - VerifyDefaults.ini File on page 50
Note
The NetlistVerifyDefaults.ini and VerifyDefaults.ini are similar. Values may vary
slightly for some checks.
Warning
Incorrect XML syntax in a VerifyDefaults.ini file could cause the design entry tool to
hang when starting Tools > Verify.
Parameters
None.

DRC Defines Section - VerifyDefaults.ini File

Input for: PADS DX Designer design entry tools Design Rule Checker (DRC)
The <Defines> section of the VerifyDefaults.ini file defines Option Names and corresponding
Values that the DRC uses for certain rules checks.
Format
Figure 2-3 shows the VerifyDefaults.ini file <Defines> section with added comments to indicate
which DRC checks use each option:
Figure 2-3. DRC VerifyDefaults.ini File - Defines Section Listing
<Defines>
<Option Name="ground_nets" Value="AGND CGND GND +0V* E FG AG E0V* G0V*
A0V*"/>

<Option Name="power_nets"
Value="VCC +5V +18V +2.5V* -2.5V* +3.3V"/>


<Option Name="units"

Value="Atto:a Femto:f Pico:p Nano:n Micro:u

Milli:m Kilo:k Mega:M Giga:G Tera:T" />

<Option Name="supply_pin" Value="DRC Supply Pin" />

<Option Name="drc_power" Value="DRC Power" />

<Option Name="drc_tolerance" Value="DRC Tolerance" />

<Option Name="drc_negative" Value="DRC Negative" />


<Option Name="drc_positive" Value="DRC Positive" />

<Option Name="drc_ic" Value="DRC IC" />
 <Option Name="drc_power_factor"
Value="DRC Power" /> 
<Option Name="drc_vrrm" Value="DRC VRRM />

<Option Name="vhdl_file" Value="VHDL File" />

<Option Name="verilog_file" Value="Verilog File" />

<Option Name="verilog_type" Value="Verilog Type" />

<Option Name="vhdl_model" Value="VHDL Model" />

<Option Name="supply_net" Value="Power Supply Net" />

<Option Name="ground" Value="GROUND" />

<Option Name="part_number" Value="Part Number" />

<Option Name="resistors" Value="*res*.*" />

<Option Name="net_class" Value="DRC_NCLS" />


<Option Name="net_check" Value="DRC_NCHK" />

<Option Name="net_class_default" Value="5V_TECH" />

</Defines>
Parameters
For example, OutputDirectlyPG (drc-116) passes the Values specified in the following
ground_nets and power_nets definition in the .ini file <Defines> section to the DRC:
<Option Name="ground_nets" Value="GND +0V* E FG AG E0V* G0V*
A0V*"/>
<Option Name="power_nets" Value="VCC +2.5V* -2.5V*"/>
You can use other Option Name definitions to indicate to certain rules checks which
schematic objects the DRC should evaluate. This type of option specifies a user-defined
value that corresponds to a property name on a schematic object. For example, the following
supply_pin definition specifies a value of DRC Supply Pin.
<Option Name="supply_pin" Value="DRC Supply Pin" />
If you define a DRC Supply Pin property in your design and place the property on a net,
the checks SupNegConnected (drc-505), SupNotConnected (drc-506), and
SupWrongConnected (drc-507), if selected, evaluate that net.
Note
You or an administrator can modify the Values in the .ini <Defines> section to suit
each site. For example, you can change the Value in the supply_pin definition from
DRC Supply Pin to Supply Pin Check. You can then create a property named
Supply Pin Check and place it on a schematic object(s). However, you must not
modify the Option Name supply_pin.
Related Topics
Verify Dialog Box
DRC Rule Notes and Examples
DRC Property and Label Syntax Using Regular Expression Syntax
DRC Regular Expression Ambiguity Resolution

DRC Settings Section - VerifyDefaults.ini File

The <Settings> section of the .ini file relates to the various settings on the Verify tool Settings
pane, which specifies the scope of the DRC operation.
Format
Figure 2-4 uses numbered designators to cross-reference the .ini file code to the Settings pane.
Figure 2-4. DRC Verify Tool Settings Pane - Settings Section as it Relates to UI

Parameters
None.
Related Topics
Verify Dialog Box

DRC Checks Section - VerifyDefaults.ini File

The <Checks> section of the .ini file contains the definition of each numbered check.
Format
Figure 2-5 uses the following numbered designators to cross-reference the .ini file code to the
Rules pane.
1. ID Specifies an ID number.
2. State Presets the checkbox as either Enabled (checked) or Disabled (unchecked).
3. Severity Presets the Severity level as either Note, Warning, or Error.
4. GUI Defines the Rule title that appears on the GUI.
5. Description Text defined here appears at the bottom of the dialog box when a check
is selected.
6. Option text Defines the Option title that appears on the GUI.
7. Option Value Preset the value(s) in the Values column, or leave this out of the Check
Name definition if there are no values.
8. Option GuiObject (edit) If set to edit, an edit box appears when you click on the
value.
9. Option Value In Figure 2-5, this option value is the default setting for one of the
choices provided.
10. Option GuiObject (combobox) If set to combobox, a pulldown list is available to
set the value.

Figure 2-5. Verify Tool Rules Pane - Defaults File Checks Section as it Relates
to UI
Parameters
None.
Related Topics
Verify Dialog Box

DRC Rules Section - VerifyDefaults.ini File

Input for: PADS DX Designer design entry tools Design Rule Checker (DRC)
The <Rules> section specifies which groups appear in the Rules list, and which checks are
associated with each group.
Format
Figure 2-6 shows the <Rules> section of the .ini file. Figure 2-6 also shows a portion of the
Checks section so you can see how the <Rules> section references a Check Name. In this
example, the PropertyUnsupported Check Name is the first entry in Migration. The
description that follows the figure uses the numbered designators as reference.

Figure 2-6. DRC Rules Pane - Defaults File Rules Section as it Relates to UI
The following items explain the .ini file sections shown in Figure 2-6:
1. The <Rules> section of the .ini file define the group name(s). This example defines the
first group as Migration.
2. Migration group checks reference Check Names, as defined in the <Checks> section.

3. If you include the string State=Enabled in the Rules section, it overrides the State
declaration in the Checks section of the .ini file for a given check. This example shows
the PropertyUnsupported check disabled in the Checks section, yet it is enabled in the
Rules section. As seen in the UI (Figure 2-6), this check is enabled.
4. The second group specified in the Rules section is titled Connectivity.
Parameters
None.
Related Topics

DxDesigner.xml File Format

Input for: PADS DX Designer design entry tools user interface configuration settings
The design entry tool reads one or more ASCII DxDesigner.xml files along your WDIR path to
configure the design entry tool session settings.
For more information on how design entry tool accesses multiple DxDesigner.xml files along
your WDIR path, see DxDesigner.xml File Precedence Order.
Format
The DxDesigner.xml file is an ASCII file that uses standard XML formatting. The file content is
divided into major sections as shown in Figure 2-7.
Figure 2-7. DxDesigner.xml File Section Structure
<?xml version="1.0" ?>

<DxDesigner_Configuration_file version="1.2" name="DxDesigner.xml">
<DxDesigner>
<OBJECTS>  </OBJECTS>
<LAYERS>  </LAYERS>
<ICTOBJECTS>  </ICTOBJECTS>
<SETTINGS>  </SETTINGS>
<SIZES> </SIZES>
<COLORS>  </
COLORS>
. . .
</DxDesigner>
<DxDatabook>
<SETTINGS>  </SETTINGS>
</DxDatabook>
</DxDesigner_Configuration_file>
The lines that define configuration settings in the DxDesigner.xml file have the following
format:
<key name="setting_name" value="setting" />
Note
You should only change the setting value.
If the readonly=1 option has been applied to an object or key name in the DxDesigner.xml
file, such as <object name=NET readonly=1/> or
<key name=VISIBLE value=1 readonly=1/>, the associated setting cannot be changed
in the Setup > Settings dialog box. All objects allow the readonly=1 option. Not all key
names allow the readonly=1 setting. Read-only compatibility is indicated in the key name
descriptions in this topic. For more information, see Read-only User-Preference Settings.

Parameters
The following tables list the setting names and describes the editable parameter values in
each section of the DxDesigner.xml file:
o DxDesigner.xml DxDesigner OBJECTS Section Table 2-6 on page 54
o DxDesigner.xml DxDesigner LAYERS Section Table 2-7 on page 57
o DxDesigner.xml DxDesigner ICTOBJECTS Section Table 2-8 on page 59
o DxDesigner.xml DxDesigner SETTINGS Section Table 2-9 on page 60
o DxDesigner.xml DxDesigner SIZES Section Table 2-10 on page 136
o DxDesigner.xml DxDatabook SETTINGS Section Table 2-11 on page 139
Table 2-6. DxDesigner.xml DxDesigner OBJECTS Section

Setting Name Setting Description and Setting Values
The OBJECTS section defines the following: (Note: Names in parentheses indicate UI labels.)
NET, COMPONENT, ATTRIBUTE (Property), LABEL (Name), PIN, BOX, LINE,
CIRCLE, ARC, TEXT, WIRE, BUS, WIRE_BUS, FRAME, POLYGON, and
DOCUMENT_CONTAINER
COLOR Sets the color of each object using an RGB hex value. The
default values for each defined object are set as follows:
0xffff00 ATTRIBUTE (Property), BUS, LABEL (Name),
WIRE, WIRE_BUS
0x00ffff ARC, BOX, CIRCLE, COMPONENT, LINE,
PIN, POLYGON, TEXT
0x9eb8cf DOCUMENT_CONTAINER
0xff6820 FRAME
0x00ff00 NET
Can be set to Read-only? Yes.
GUI access:
Setup > Settings, Display (category), Objects

Table 2-6. DxDesigner.xml DxDesigner OBJECTS Section (cont.)

FILL_STYLE Sets the fill style of each object using the following values:
0 Hollow (Default for BOX, CIRCLE, COMPONENT,
DOCUMENT_CONTAINER, LINE, PIN, POLYGON, and
WIRE)
1 Solid (Default for BUS, NET, and WIRE_BUS)
2 Diagdn1
3 Diagdn2
4 Grey08
5 Diagdn2
6 Diagup1
7 Horiz
8 Vert
9 Grid2
10 Grid1
11 X2
12 X1
13 Grey50
14 Grey92
15 Grey04
Fill style settings are not applicable (set to -1 by the design entry
tool) to the following objects:
ARC, ATTRIBUTE (Property), FRAME, LABEL (Name),
WIRE, and TEXT
GUI access:
Setup > Settings, Display (category), Objects (subcategory),
Schematic button selected.


LINE_STYLE Sets the line style of each object using the following values:
0 Solid (Default)
1 Dash
2 Center
3 Phantom
4 Big dash
5 Dot
6 Dash-Dot
7 Medium Dash
Line style settings are not applicable to the following objects:
ATTRIBUTE (Property), LABEL (Name), TEXT
GUI access:
Schematic button selected.
SELECTABLE Defines selection filter behavior as follows:
0 The object is filtered from the selection and cannot be
selected. (Default - all objects.)
1 The object is selectable.
GUI access:
View > Other Windows > Selection Filter
VISIBLE Sets object visibility state as follows:
0 Not visible.
1 Visible (Default - all objects.)
GUI access:
View > Other Windows > Selection Filter
For ATTRIBUTE (Property) objects Setup > Settings,
Display (category), Common Properties (option)
For TEXT objects Setup > Settings, Display (category),
Graphical Text (option)
For LABEL (Name) objects Setup > Settings, Display
(category), Name (option)


LINE_THICKNESS Sets line thickness using a value between 1 (thinnest - default)
and 10 (thickest). Line thickness settings are not applicable to
the following objects:
ATTRIBUTE (Property), BUS, COMPONENT,
DOCUMENT_CONTAINER, LABEL (Name), PIN, and TEXT
GUI access:
Setup > Settings, Display (category), Objects (subcategory)
Table 2-7. DxDesigner.xml DxDesigner LAYERS Section

The LAYERS section defines the following: (Note: Names in parentheses indicate UI labels.)
SELECTION_LAYER, DYNAMIC_SELECTION_LAYER, BORDER_LAYER,
VALUE_LAYER, ANNOTATION_LAYER, HIGHLIGHT_LAYER,
BACKGROUND_LAYER, GRID_LAYER, DRAG_LAYER (Selection),
UNPLACEDCOMPONENT_LAYER, ZONES_LAYER (Border/Grid Zones),
ZONING_LAYER (Sheet Zoning Grid), CROSS_REFERENCE_LAYER
COLOR Sets the color of each layer using an RGB hex value. The default
values for each defined layer are set as follows:
0xffffff SELECTION_LAYER, ZONES_LAYER
(Border/Grid Zones), ZONING_LAYER (Sheet Zoning
Grid)
0x00ffff BORDER_LAYER
0xc0c0c0 VALUE_LAYER,
UNPLACEDCOMPONENT_LAYER
0xffff00 ANNOTATION_LAYER,
CROSS_REFERENCE_LAYER
0xff00ff HIGHLIGHT_LAYER
0x000000 BACKGROUND_LAYER
0x3a3a3a GRID_LAYER
xffaaaa DYNAMIC_SELECTION_LAYER
0x00ff00 DRAG_LAYER (Selection)
GUI access:
Schematic button selected

Table 2-7. DxDesigner.xml DxDesigner LAYERS Section (cont.)

FILL_STYLE Sets the fill style of each layer using the following values:
0 Hollow
1 Solid (Default for HIGHLIGHT_LAYER)
2 Diagdn1
3 Diagdn2
4 Grey08
5 Diagdn2
6 Diagup1
7 Horiz
8 Vert
9 Grid2
10 Grid1
11 X2
12 X1
13 Grey50
14 Grey92
15 Grey04
Fill style settings are not applicable for any layers except the
HIGHLIGHT_LAYER.
GUI access:

Table 2-7. DxDesigner.xml DxDesigner LAYERS Section (cont.)

LINE_STYLE Sets the line style of each layer using the following values:
0 Solid (Default for HIGHLIGHT_LAYER)
1 Dash
2 Center
3 Phantom
4 Big dash
5 Dot
6 Dash-Dot
7 Medium Dash
Line style settings are not applicable for any layers except the
HIGHLIGHT_LAYER.
GUI access:
Table 2-8. DxDesigner.xml DxDesigner ICTOBJECTS Section

The ICTOBJECTS section defines the following: (Note: Names in parentheses indicate UI
labels.)
ICTBLOCK (View), ICTBUS, ICTCOMPONENT (Block), ICTDIFFPAIR, ICTEDITCELL,
ICTFPGA, ICTFUB (Editable Block), ICTGROUP, ICTHIGHLIGHT_LAYER,
ICTINVALIDCELL, ICTNET, ICTNETS (Global Net), ICTPIN, ICTPORT, ICTSYMBOL.
COLOR Sets the color of each ICT object using an RGB hex value. The
default value for each ICT object is set as follows:
0xfffbf0 (Default for ICTBLOCK (View), ICTBUS,
ICTCOMPONENT (Block), ICTDIFFPAIR,
ICTEDITCELL, ICTFPGA, ICTFUB (Editable Block),
ICTNET, ICTNETS (Global Net), ICTPIN, ICTPORT,
ICTSYMBOL)
0xa6caf0 (Default for ICTGROUP)
0xffffce (Default for ICTHIGHLIGHT_LAYER)
0xb0b0b0 (Default for ICTINVALIDCELL)
GUI access:
ICT button selected

Table 2-8. DxDesigner.xml DxDesigner ICTOBJECTS Section (cont.)

TEXTCOLOR Sets the text color of each ICT object using an RGB hex value.
The default value for all ICT objects is set as follows:
0x000000
GUI access:
ICT button selected
Table 2-9. DxDesigner.xml DxDesigner SETTINGS Section

ABSOLUTE_OATS Internal Use Only. Do not modify.
ADD_PROPERTIES_ Internal Use Only. Do not modify.
HINT_TAG
ADD_PROPERTIES_ Internal Use Only. Do not modify.
HINT_TAG_TIMER
ADISTANCE Obsolete. Use ADISTANCE_HR.
ADISTANCE_HR Avoidance distance - high resolution. (Available only when
Avoidance Routing is active: =2.) Sets the minimum distance
between nets and components or other nets.
The default value of 5.08mm or 0.20in appears in the file as
508000 (5.08mm * 100,000).
GUI access:
Setup > Settings, Schematic Editor (category), Nets
(subcategory), Avoidance Distance (option)
ADVANCED_BOARD_ xSD Systems Designer. Controls connectivity when you move
MANAGEMENT system level Blocks between boards:
0 Do not update connectivity. Default.
1 Update connectivity. xSD Systems Designer adds
connector pairs, nets and wires to preserve connectivity.
Can be set to Read-only? No.
GUI access:
Setup > Settings, Advanced (category), System Designer
Automatic Connectivity Update (option)

Table 2-9. DxDesigner.xml DxDesigner SETTINGS Section (cont.)

ANALOG_ Internal Use Only. Do not modify.
SIMULATION_MODE
ANNO_LOC_OFFSET_X Sets cross reference annotation text X-offset placement based
on the annotation origin point in the specified units. Default is
0. A positive number offsets the text to the right, a negative
number offsets the text to the left.
GUI access:
Setup > Settings, Project (category), Cross Reference
(subcategory), X-Offset (option)
ANNO_LOC_OFFSET_Y Sets cross reference annotation text Y-offset placement based
on the annotation origin point in the specified units. Default is
0. A positive number offsets the text vertically up, a negative
number offsets the text vertically down.
A value of 762000 sets the offset to 7.62mm, or .3in.
GUI access:
(subcategory), Y-Offset (option)
ANNO_LOC_SPACING Internal Use Only. Do not modify.


ANNO_ORIGIN Sets the cross reference annotation text origin point (or none)
for the as one of the following:
0 None (Default)
1 Upper left
2 Middle left
3 Lower left
4 Upper center
5 Middle center
6 Lower center
7 Upper right
8 Middle right
9 Lower right
GUI access:
(subcategory), Annotation Origin (option)
ANNO_SIZE Internal Use Only. Do not modify.
ANNO_SIZE_HR Internal Use Only. Do not modify.
CROSS_REFERENCE_ Sets the size of cross reference text. Default is 381000.
SIZE_HR You need to enter a value as: (value in millimeters) * 100,000.
The default value of 381000 sets the offset to 3.81mm, or .15in.
GUI access:
(subcategory), Text Size (option)
ANNO_MAX_LENGTH Sets the maximum length (in characters) of the cross reference
annotation. Default is 20.
GUI access:
(subcategory), Max Line Length (option)


ANNO_SEP Specifies a separator that appears between multiple cross
reference link designators when a link goes to more than one
destination such as 2-B7;3-G4;3-D10;3-GS. Default = ;
(semicolon).
GUI access:
(subcategory), Separator (option)
ANNO_CONDENSED_ If the ANNO_USE_CONDENSED option is on (value=1),
SEP then you can specify the separator (default = /) used between
multiple link designators when a link goes to more than one
destination such as: 3-G4/D10/G9.
GUI access:
(subcategory), Condensed Separator (option)
ANNO_USE_ Sets the cross reference annotation text to use either condensed
CONDENSED format (default) or non-condensed format when a link points to
multiple destinations:
0 Display verbose, non-condensed cross reference links
to a given sheet.
1 Condense cross reference links to a given sheet.
Default.
For example, given the following destinations from a link:
2-B7;3-G4;3-D10;3-GS. Turning on this option (value=1)
condenses the three entries that all go to page 3 as follows: 2-
B7;3-G4/D10/G9. Note that the condensed separator is set in
the ANNO_CONDENSED_SEP setting, which in this example
is set to / (the default).
GUI access:
(subcategory), Allow Condensed Annotations (option)


AREA_SELECTION_ 0 The selection area must totally enclose an object to be
OVERLAP included in a selection. Default.
1 The selection area need only enclose a portion of an
object for it to be included in a selection.
GUI access:
Setup > Settings, Advanced (category), Area Select by
Overlap (option)
See also:
Selecting Schematic Objects - xDX Designer
ATTR_ON_SPLIT Internal Use Only. Do not modify.
ATTRON Internal Use Only. Do not modify.
AUTOHIDE_SCHEMATIC Internal Use Only. Do not modify.
_PANANDZOOM
AUTOLABELING_NETS Controls whether the design entry tool names new nets
automatically as follows:
0 The design entry tool does not name nets
automatically. Default.
1 The design entry tool names nets automatically based
on the rules described in the topic:
Naming Connectivity Objects Such as Nets and Buses - xDX
Designer
GUI access:
(subcategory), Name New Nets Automatically (option)


AUTOLABELING_ Controls whether the design entry tool names new buses
BUSES automatically as follows:
0 The design entry tool does not name buses
automatically. Default.
1 The design entry tool names buses automatically based
on the rules described in the topic:
Naming Connectivity Objects Such as Nets and Buses - xDX
Designer
GUI access:
(subcategory), Name New Buses Automatically (option)
AUTO_CONNECT_NEW_ Sets the ICT power supply tap autoconnect behavior as follows:
TAP 0 Turn off power supply tap autoconnect.
1 If set prior to placing a tap in an Interconnectivity
Table (Add > Power or Add > Ground), creates the
connection to the corresponding global net (given by the
value of the tap symbol property Global Signal Name).
The global net is eventually added if it does not already
exist. Default.
GUI access:
Setup > Settings, Interconnectivity Table (category), Power
supply tap autoconnect (option)
AUTO_RIPPER_BUS_ Internal Use Only. Do not modify.
SEGMENT
AUTO_RIPPER_BUS_ Internal Use Only. Do not modify.
SEGMENT_LENGTH_
HR
AUTO_TEXT_ORIEN Internal Use Only. Do not modify.
AUTOLOG Internal Use Only. Do not modify.


AUTOMATICALLY_ Controls the behavior of connector pin naming when
PROPAGATE_NET_ connecting a net to a connector as follows:
NAMES 0 You can use different names between nets and
associated connectors. Default.
1 The design entry tool automatically synchronizes the
net name with the connector pin name no matter which
name changes.
GUI access:
Setup > Settings, Advanced (category), Automatically
synchronize on-sheet/off-links and net names (option)
AUTOPAN Controls schematic panning as follows:
0 Does not automatically pan screen when dragging a
component to an edge of the schematic.
1 Automatically pans the screen when dragging a
component. This eliminates the need for using F6 to pan
each time you move an object. Default.
GUI access:
Setup > Settings, Advanced (category), Auto Pan (option)
BEGIN_NETS_IN_ Controls how nets are places on the schematic as follows:
SPACE 0 Nets can only start at a component pin or at a junction
with another net.
1 Allows nets to start anywhere. Default.
BELL Obsolete.
BIGCROSS Obsolete.
BITNUMBERS Control the display of bit numbers on a ripped bus as follows:
0 Do not show bit numbers on a ripped bus. Default.
1 Show bit numbers on a ripped bus.
GUI access:
Setup > Settings, Advanced (category), Show Ripper
Indexes (option)
BLOCKTYPE Internal Use Only. Do not modify.


BORDERON Controls the visibility of the schematic border shown in the
figure, Border, Border Symbol and Zoning Grid. This is not
referring to a border symbol.
0 Hides the schematic border.
1 Displays the schematic border. Default.
GUI access:
Setup > Settings, Display (category), Border (option)
BORDERZONES Controls the visibility of the schematic zoning grid border label
shown in the figure, Border, Border Symbol and Zoning Grid.
0 Hides the zoning grid border label. Default.
1 Displays the zoning grid border label.
GUI access:
Setup > Settings, Display (category), Zone Labels (section),
Border (option)
BOXSIZE Obsolete. Use BOX_SIZE_HR.
BOXSIZE_HR Sets the drawing size (radius) of all boxes on dangling joints.
The default value of 127000 sets the size to 1.27mm, or
0.050in.
GUI access:
Setup > Settings, Advanced (category), Box Size [<Units>]
(option)
BUBBLESIZE Obsolete. Use .
BUBBLESIZE_HR Sets the size of the bubble on inverted pins.
0.050in.
GUI access:
Setup > Settings, Advanced (category), Inverted Pin Bubble
Size [<Units>] (option)
BUS Obsolete.


BUS_DOTSIZE Obsolete. Use BUS_DOTSIZE_HR.
BUS_DOTSIZE_HR Sets the drawing size (radius) of all net solder dots.
0.120in.
GUI access:
Setup > Settings, Advanced (category), Bus Dot Size
[<Units>] (option)
BUS_MODE Internal Use Only. Do not modify.
BUSWIDTH Obsolete. Use the LINE_THICKNESS option in the BUS
object in the OBJECTS section.
BUSWIDTH_HR Obsolete. Use the LINE_THICKNESS option in the BUS
object in the OBJECTS section.
CHANGE_TO_ALLOW_ Internal Use Only. Do not modify.
MULTIPLE_TYPES
CHECK_COMP_DATES Controls the design entry tool behavior with out-of-date
symbols as follows:
0 The design entry tool does not flag out-of-date
symbols.
1 Enables checking and highlighting of out-of-date
symbols. The software compares the symbol in the host
design and central library to ensure they are the same. If the
time/date stamp of the symbol is different than that in the
host design, The design entry tool places a magenta box
around the out-of-date symbol. Default.
GUI access:
Setup > Settings, Advanced (category), Flag out-of-date
symbols (option)


CHECK_REUSEBLOCK_ Controls the design entry tool behavior with out-of-date
DATES reusable blocks as follows:
0 The design entry tool does not flag out-of-date
reusable blocks. Default.
1 Enables checking and highlighting of out-of-date
reusable blocks. The software compares the reusable block
in the host design and central library to ensure they are the
same. If the time/date stamp of the reusable block symbol is
different than that in the host design, the design entry tool
places a magenta box around the out-of-date reusable block.
GUI access:
Setup > Settings, Advanced (category), Flag out-of-date
Reusable Blocks (option)
COARSE_GRID Internal Use Only. Do not modify.
COMPONENT_ Controls the visibility of component tooltips (labels and
TOOLTIPS properties) on schematics as follows:
0 Hide component tooltips.
1 Display component tooltips. Default.
GUI access:
Setup > Settings, Display (category), Show tooltips
(section), Components (option)
COMPTEXTON Sets symbol text visibility on schematics as one of the
following:
0 Hide symbol text.
1 Display symbol text on schematics. Default.
GUI access:
Setup > Settings, Display (category), Symbol Text (option)
CONSTRAINT Internal Use Only. Do not modify.
CONTEXT_WINDOW Obsolete.
CONTINUE_ROLLBACK_ Internal Use Only. Do not modify.
DECISION


CONTINUE_REMOVE_ Controls whether to provide a warning before deleting all sheet
ALL_BACKUPS_ backups in the current project.
DECISION 0 Provide a warning before deleting all sheet backups in
the current project. Default.
4 Do not provide warning.
GUI access:
Setup > Settings, Sheet/ICT Backup (category)
CONTINUE_REMOVE_ Controls whether to provide a warning before deleting all sheet
BOARD_BACKUPS_ backups in the current board.
DECISION 0 Provide a warning before deleting all sheet backups in
the current board. Default.
GUI access:
CONTINUE_REMOVE_ Controls whether to provide a warning before deleting all
SHEET_BACKUPS_ current sheet backups.
DECISION 0 Provide a warning before deleting all current sheet
backups. Default.
GUI access:
COPY_CONSTRAINTS_ Controls how constraints are copied along with schematic data
ON_COPY_BLOCK as follows:
0 Only schematic data is copied.
1 The design entry tool copies constraints data during
Copy Block and Copy Sheet operations. Default.
GUI access:
Setup > Settings, Advanced (category), Sheet/ICT Backup,
Copy Constraints on Copy Sheet (option)


COPY_CONSTRAINTS_ Controls whether constraints overwrite existing values during
OVERWRITES_VALUES Copy Block and Copy Sheet operations, as follows:
0 Constraints do not overwrite existing constraints
values in the project to which a block or sheet is copied.
1 Constraints overwrite existing constraint values in the
project to which a block or sheet is copied. Default.
GUI access:
Setup > Settings, Advanced (category), Copy Constraints
Overwrites All Values (option)
COPY_CONSTRAINTS_ Controls Constraint Manager invocation method when you
USING_CRM paste a sheet in the design entry tool, as follows:
0 The Constraint Manager tool does not open
automatically in Conflict Resolution Manager (CRM) when
you paste a sheet in the design entry tool. Default.
1 The Constraint Manager tool opens automatically in
Conflict Resolution Manager (CRM) when you paste a
sheet in the design entry tool.
GUI access:
Setup > Settings, Advanced (category), Copy and Paste
Sheet using Conflict Resolution (option)


CUSTOM_SELECTION_ Stores the schematic editor selection filters Custom Filter
FILTER_NAMES names.
This key name consists of multiple <value> lines, one
corresponding to each custom filter <value> line listed in the
CUSTOM_SELECTION_FILTER_OBJECTS. The first
<value> line corresponds to the first line listed in the Custom
Selection Filter Objects list, the second <value> line
corresponds to the second item listed in the Custom Selection
Filter Objects list, and so on.

GUI access:
Setup > Settings, Schematic Editor (category), Selection
Filters (subcategory)
Also see: CUSTOM_SELECTION_FILTER_OBJECTS


CUSTOM_SELECTION_ Controls the custom selection filter settings represented by the
FILTER_OBJECTS following values:
This key name consists of multiple <value> lines; one line per
custom filter listed in the
CUSTOM_SELECTION_FILTER_NAMES (Custom Filters)
list. The first <value> line corresponds to the first item listed in
the Custom Filter list, the second <value> line corresponds to
the second item listed in the Custom Filter list, and so on.
For each <value> line, activate the objects you want in that
particular filter by adding the appropriate values, separated by
spaces (see the following default custom filter definitions).
Default Custom Filter Definitions:
<value>0 1 3 4</value> (Graphics)
<value>5 7 9 26 27</value> (Objects)
<value>2 6 8</value> (Text)
GUI access:
Setup > Settings, Schematic Editor (category), Selection
Filters (subcategory)
Also see: CUSTOM_SELECTION_FILTER_NAMES


PRESERVE_ Controls what the design entry tool does with packaging
PACKAGING_INFO_ information when you copy a schematic, sheet, block, or design
ON_COPY as follows:
0 Packaging information resets to default or empty
values (depending on the information type). Default.
1 The design entry tool preserves packaging information
such as reference designators, instance values, pin numbers,
and pin slots.
GUI access:
Setup > Settings, Advanced (category), Preserve
packaging info on copy (option)
CROSSCURSOR Set the appearance of the schematic crosshair cursor as one of
the following:
0 None. Default.
1 Small.
2 Full Extent.
GUI access:
Setup > Settings, Advanced (category), Crosshair Cursor
(option)
DATETIME_FORMAT Set the @DATETIME property format using the following
variables and separator characters (most common are / and : ):
%d day
%m month
%Y year as four digits
%y year as two digits
%H hour
%M minutes
%S seconds
Default: %d/%m/%Y:%H:%M
GUI access:
Setup > Settings, Display (category), Date Format -
pulldown menu


DB_AUTO_BACKUP Controls whether sheets and ICTs are backed up each time you
open them.
0 Do not backup sheets and ICTs. Default
1 Backup sheets and ICTs each time you open them.
GUI access:
See also: DB_BACKUPS_LIMIT
DB_BACKUPS_LIMIT Set the number of sheet/ICT backups to save before
overwriting them. This is used if DB_AUTO_BACKUP is set
to 1 (on). Set the value to between 4 and 20. If you keep the
default of 0, the design entry tool saves all backups without
overwriting older ones.
GUI access:
See also: DB_AUTO_BACKUP
DB_ERR_VERBOSE Sets the SCH/SYM parser database validation to display one of
the following in the design entry tool:
0 Tallies the number of messages when done reading the
design.
1 Generates all error/warning messages. Default.
DBOXON Internal use only. Do not modify.
DEFAULT_VALUE_ Internal use only. Do not modify.
UPPER


DEFAULT_ZOOM Sets the Pan and Zoom behavior to the PADS DX Designer
configuration:
0 Turns off the PADS DX Designer style pan and zoom.
1 Turns on the PADS DX Designer style pan and zoom.
Default.
Note: This setting is used in conjunction with
EXPEDITION_ZOOM and PADS_ZOOM. Only one of
these should be set to 1 (on) at a time.
GUI access:
Setup > Settings, Schematic Editor (category), Strokes, Pan,
and Zoom (subcategory)
See also:
Panning and Zooming Default-Style - xDX Designer
DEFMETHOD Sets the behavior of border symbol placement on new

schematic sheets as one of the following:
0 Does not place user-configured border symbol on new
schematic sheets.
1 Places a user-configured border symbol on to new
schematics. This symbol can be from any location in the
search order. Default.
GUI access:
Setup > Settings, Schematic Editor (category), New Sheets
(subcategory), Enable user-configurable border symbols
(option)
DEFSHEET Sets the following Border Sheet option as one of the following:
0 Do not automatically add a border to new schematic
sheets. Default.
1 Automatically add a hardwired border schematic from
a required location on to new schematics.
GUI access:
(subcategory), Automatically add border to new schematic
sheets (option)


DEF_USESHEET1 If DEFMETHOD=1, this setting lets you choose to use either
the same user-configurable border for all sheets, or a different
border for the first sheet in a design, as follows:
0 Do not use the sheet 1 border for new sheets. Default.
1 Use the sheet 1 border for new sheets.
Rules:
This setting has no effect on a top level schematic. You use
this setting to specify which border to use on the first sheet
of a new schematic when you push into a composite
component.
If you select this setting, the border specified in Border for
Sheet 1 is used on the first sheet of the underlying
schematic.
If you clear this setting (value=0), the border specified in
Border for Sheet 2-N is used for all sheets, including sheet
1.
GUI access:
(subcategory), Use sheet 1 border for underlying schematics
(option)
DETAIL Controls how the design capture tool displays objects during
object manipulation operations as one of the following:
0 The design capture tool displays a bounding box,
which represents the object until the operation is complete.
1 The design capture tool continually displays objects
while you are performing operations, such as: adding,
pasting, moving, copying, or rotating. Default.
Tip: Leaving this option on (value=1) slows down object
movement. If you find the speed of object operations slow,
change this option setting.


DISPLAY_FULL_ Controls how the design entry tool displays net names when
SIGNAL_NAME_ON_ you rip nets from a bus as follows:
RIPPER 0 Displays only the ripper index value (default) as shown
below:
1 Displays the full net name of the ripped net as shown
below:
Prerequisite:
=1 must be set before you can display the ripped net name.
See also:

GUI access:
Setup > Settings, Advanced (category), Use Full Bus Name
on Ripper (option)
DISPLAY_ Obsolete.
REUSEBLOCK_WORK
DOTSIZE Obsolete. Use DOTSIZE_HR.


DOTSIZE_HR Sets the drawing size (radius) of all net connection dots. The
design entry tool determines the connection dot size from the
radius setting and the net linewidth.
You need to enter a radius value as: (value in millimeters) *
100,000. The default value of 63500 sets the increment to
0.635mm, or 0.025in.
If the net has a linewidth=1, the design entry tool displays the
connection dot using the radius value (0.025 in the second
example in the following figure.)
If the net has a linewidth>1, the design entry tool increases the
connection dot size according to the net size. The design entry
tool adds the radius value to the net line edge as shown in the
first example in the following
figure:

GUI access:
Setup > Settings, Advanced (category), Dot Size [<Units>]
(option)
DOTSIZE_THREE_ Obsolete.
SEGMENTS
DOTSIZE_THREE_ Obsolete.
SEGMENTS_HR
DXD_ALTERA_ Enter the path to the Altera folder that contains the executable.
EXECUTABLE_PATH Default: null string .
GUI access:
Setup > Settings, HDL/FPGA Integration (category), FPGA
Tools (subcategory), Altera Executable Path (option)


DXD_CLEAR_LIBRARY_ Controls what actions need to happen before simulation
BEFORE_INIT initialization as follows:
True You do not need to manually run the Simulation >
Clean command before running Simulation > Initialize
Simulation .
False Before running Simulation > Initialize
Simulation you need to manually run the Simulation >
Clean command. Default.
GUI access:
Setup > Settings, HDL/FPGA Integration (category),
Integrated Simulator (subcategory), Delete Design Units
from HDL Design (option)
DXD_COMPILE_ Controls what actions need to happen before simulation
BEFORE_INIT initialization as follows:
Compile command before running Simulation >
Initialize Simulation .
Simulation you need to manually run the Simulation >
Compile command. Default.
GUI access:
Integrated Simulator (subcategory), Compile Files (option)
DXD_CURRENT_FPGA_ Specify which FPGA tool you want to execute (Xilinx or
TOOL Altera).
Default: null string .
GUI access:
Tools (subcategory), Current Tool (option)


DXD_DIAGNOSTICS_ Sets the design entry tool to run the automatic Diagnostics tool
RUN_ON_CLOSE when the session exits.
0 Does not run the Diagnostics tool. Default.
1 Runs the Diagnostics tool when the design entry tool
closes.
GUI access:
Setup > Settings, DxDesigner Diagnostics (category),
Execute PADS DX Designer Diagnostics on exit (option)
DXD_ENABLE_ Controls the design entry tool edit mode if the proj_name.prj
EXTERNAL_EDITOR file has specified a valid DedicatedServerName as follows:
False Sets the session so that the first designer to open a
sheet does not get read-write access to the sheet. The sheet
is opened in read-only mode. The first designer who clicks
the Click to Edit button gets read-write access to the
sheet.
True Sets the session so that the first designer to open a
sheet gets read-write access. Any subsequent designer
opening the same sheet gets read-only access.
GUI access:
Setup > Settings, Project (category), Enable edit mode for
opened sheets (option)
or
Integrated Simulator, Use External Text Editor (option)
Also see: The Multi-User Environment
DXD_ENABLE_ Controls whether the PADS DX Designer Start Page displays
START_PAGE when you invoke the tool as follows:
0 Does not display the Start Page.
1 Displays the Start Page. Default.


DXD_EXPORT_BEFORE_ Controls what actions need to happen before simulation
INIT initialization as follows:
Export HDL Files command before running
Simulation > Initialize Simulation .
Simulation you must run Simulation > Export HDL Files.
Default.
GUI access:
Integrated Simulator (subcategory), Export HDL Files
(option)
DXD_EXPORT_BEFORE_ Controls whether to export HDL files when you run the Launch
TOOL_LAUNCH FPGA tool as follows:
True Exports HDL files when you run the Launch
FPGA Tool the Launch FPGA tool.
False Does not export HDL files when you run the
Launch FPGA tool. Default.
GUI access:
Tools (subcategory), Export Before Launch (option)


DXD_EXTERNAL_ If the DXD_ENABLE_EXTERNAL_EDITOR setting is set to
EDITOR_EXECUTABLE True, use this setting to provide a path to your own text editor
instead of using the one the design entry tool provides. The
default = null string .
In addition to the path to the executable, include the parameter
$(File) as in the following example to enable the design entry
tool to start the editor on the correct HDL file:
C:\Program Files\TextPad.exe $(File)
If your text editor invocation supports a second argument to

invoke on a specific line number, you can add the argument
$(Line) as in the following example:
C:\Program Files\TextPad.exe $(File) $(Line)

GUI access:
Integrated Simulator (subcategory), Executable File and
Parameters (option)
DXD_HDL_EXPORT_ Sets the name of the export folder (default = Exported):
FOLDER Can be set to Read-only? No.
GUI access:
Setup > Settings, Project (category), Export HDL
(subcategory), Export Folder
DXD_HDL_EXPORT_ Sets the default export language as one of the following:
LANGUAGE 0 VHDL (default)
1 Verilog
GUI access:
Setup > Settings, Project (category), Export HDL
(subcategory), Default Export Language (option)


DXD_ML_OBJECT_ This setting works with a project.
REFERENCES Use this setting to compute values of Function or Location or
Product ID properties in different formats as follows:
0 PADS DX Designer computes values in single-level
format.
1 PADS DX Designer computes values in multi-level
format. Default.
GUI access:
Setup > Settings, Advanced (category), Multi-Level Object
References (option)
DXD_ML_OBJECT_ This setting works with a project.
REFERENCES_SHORT_ If DXD_ML_OBJECT_REFERENCES is set to value=1, this
NOT option controls the following:
0 The design entry tool does not use shorthand notation.
1 The design entry tool uses shorthand notation. Default.
GUI access:
Setup > Settings, Advanced (category), Multi-Level Object
References Use Shorthand Notation (option)
DXD_MODELSIM_ Internal use only. Do not modify.
EXECUTABLE_PATH
DXD_OVERWRITE_ Controls whether to overwrite the tool files list before running
TOOL_FILES_LIST the Launch FPGA tool as follows:
True Prepares the project file in the FPGA tool with the
HDL file list when you run the Launch FPGA tool.
False Does not overwrite tools HDL file list when you
run the Launch FPGA tool. Default.
GUI access:
Tools (subcategory), Overwrite Tool Files List (option)


DXD_SIMULATOR_ Sets the path to the ModelSimfolder that contains the
EXECUTABLE executable. Default = null string
GUI access:
Integrated Simulator (subcategory), ModelSim Executable
Path (field)
DXD_SIMULATOR_USE_ Controls what actions need to happen before simulation
EXTERNAL initialization as follows:
True Use the ModelSim User Interface (UI) to set up
and run the simulation instead of the PADS DX Designer
UI.
False PADS DX Designer provides a dialog to set up
and run the simulation. Default.
GUI access:
Integrated Simulator (subcategory), Use External ModelSim
(option)
DXD_XILINX_ Enter the path to the Altera folder that contains the executable.
EXECUTABLE_PATH Default = null string
GUI access:
Tools (subcategory), Xilinx Executable Path (option)
DXDB_HIDE_CL_VIEW Controls whether the Central Library view is visible in
DataBook when a .dbc configuration file is loaded:
0 The Central Library view is visible in xSD Databook.
Default.
1 The Central Library view is not visible in DataBook.
Can be set to Read-only? No
DXDLITE_SHOW_ Internal use only. Do not modify.
EXPIRATION_WARNING
_LEVEL


DXDIAG_ON_DB_ Controls the design entry tool behavior before opening a
UPGRADE project that was created with an earlier version of
PADS DX Designer as follows:
0 Do not run Tools > DxDesigner Diagnostics before
opening an updated project. Default.
1 Before opening a project that was created with an
earlier version of PADS DX Designer, PADS DX Designer
automatically runs Tools > DxDesigner Diagnostics after
successfully updating the project to the current version of
PADS DX Designer.
GUI access:
Setup > Settings, Advanced (category), Run Diagnostics
after update (option)
DYNAMIC_PANNING Controls dynamic panning as follows:
0 Do not use middle mouse button to pan the schematic.
1 Use middle mouse button to pan the schematic.
Default.
DYNAMIC_PLOTSIZE Obsolete.
DYNAMIC_XY Controls component coordinate updating as follows:
0 Does not dynamically update component coordinates
on the status bar during a component move. This setting
may improve performance slightly.
1 Dynamically updates component coordinates on the
status bar when moving a component. Default.
EDM_GENERATE_BAsd_ xSD Systems Designer. Controls xDM Design Client check-in
SYNCDATA_ON_CLOSE behavior regarding back annotation as follows:
0 Hide the Generate SD BA dialog box on check-in
request. Default.
1 Show the Generate SD BA dialog box on check-in
request.
GUI access:
Setup > Settings, Advanced (category), Hide 'Generate SD
BA dialog' on Check-In request (option)


EURO_ARROWS This option is used in conjunction with option
PINTYPE_ARROWS to set the appearance of pintype arrows
between full arrow and half arrow (European) style as follows:
None .........(PINTYPE_ARROWS, value = 0,
...................EURO_ARROWS, not applicable)
Full Size....(PINTYPE_ARROWS, value = 1,
...................EURO_ARROWS, value = 0)
Half Size...(PINTYPE_ARROWS, value = 1,
The default setting for EURO_ARROWS is 0.
Notes:
The design entry tool only displays pintype arrows for
symbols that have block types of Module and Composite.
The design entry tool does not display pintype arrows for a
block type of Pin.
If a pintype does not exist on the symbol pin, the design
entry tool does not display Pintype Arrows.
Different pin types are represented by different arrows. A list of
these are shown in the PINTYPE/Arrow Type Examples table
in the Settings Dialog Box - Advanced topic.
GUI access:
Setup > Settings, Advanced (category), Pintype Arrows
(option)
EURO_DATE Obsolete. Use DATETIME_FORMAT


EXPEDITION_ZOOM Sets the Pan and Zoom behavior to the layout tool
configuration:
0 Turns off xPCB Layout tool style pan and zoom.
1 Turns on the xPCB Layout style pan and zoom.
Default.
DEFAULT_ZOOM and PADS_ZOOM. Only one of these
should be set to 1 (on) at a time.
GUI access:
and Zoom (subcategory)
See also:
Panning and Zooming xPCB Layout-Style - xDX Designer


FIXED_TEXT_ Controls the design entry tool text rotation behavior as follows:
ROTATION 0 (Off) The design entry tool handles text rotation as
shown in the following example (on the left). Rotating the
text 180 degrees maintains the original orientation. Rotating
the Text string either 90 or 270 degrees produces the
results shown in the example on the left.
1 (On) The design entry tool handles text rotation as
shown in the following example (on the right). For each
rotation of the text (90, 180, and 270 degrees), the
orientation is changed as shown. Default.
Note: If you change the setting from On to Off after you

have added text, any text appearing in the 180 degree state
or the 270 degree state (as shown on the right in the example
above) changes to the equivalent state as shown at the left in the
example when you apply the new setting.
GUI access:
Setup > Settings, Advanced (category), Fixed Text Rotation
(option)
FUBPINTYPEON Internal Use. Do not modify.
GRC_DESIGN_SCOPE Sets the Graphical Rule Checker scope as one of the following:
Project - Default
Board
Schematic
Sheet
GUI access:
GRC button pulldown


GRC_ISSUE_SCOPE Configures the Graphical Rules Checker rule defaults that
appear in Setup > Settings, Graphical Rules Checker
(category). Each line is constructed of:
<value> 0 (checked) or 1 (unchecked):
{rule_name}:{severity}:{value} </value>
The following shows the default settings:
<key name="GRC_ISSUE_SCOPE">
<value>1:Net overlap:Note</value>
<value>0:Object overlap:Note</value>
<value>1:Net off grid:Note</value>
<value>1:Pin off grid:Note</value>
<value>1:Text owner:Note:1.2in</value>
<value>1:Text alignment:Note</value>
</key>

GUI access:
Setup > Settings, Graphical Rules Checker (category)
GRID_HIGHLIGHT_ Internal Use. Do not modify.
INTERVAL
GRID_HIGHLIGHT_ Internal use. Do not modify.
MARKS
GRID_HIGHLIGHT_ If = 1 and = 1, this sets a grid highlight interval (default = 10,
MARKS_INTERVAL meaning that for every ten grid units, a highlight mark is
displayed).
GRID_HR Sets the grid display space increment for the active schematic
or symbol window.
The default value of 254000 sets the increment to 2.54mm, or
0.1in.
GUI access:
Setup > Settings, Schematic Editor (category), Grid Spacing
(option)


GRIDON Sets the schematic grid display as follows:
0 Grid is off. Objects that are placed or moved on a
schematic do not snap to the grid.
1 Grid is on. Objects that are placed or moved on a
schematic snap to the grid. Default.
If the grid is on, the LINE_GRID (Grid Type) setting
determines how the grid appears (dotted or lined).
GUI access:
Setup > Settings, Schematic Editor (category), Display Grid
(option)
GRIDZONES Turns on or off the schematic zone labels as shown in the
figure, Border, Border Symbol and Zoning Grid as follows:
0 Turns off zone labels. Default.
1 Turns on zone labels.
GUI access:
Setup > Settings, Display (category), Zone Labels (section),
Left-Top Corner of Each Zone (option)
HATS Internal use. Do not modify.
HIDE_EDM_GENERATE_ xSD Systems Designer. Controls xDM Design Client check-in
BAsd_SYNCDATA_ON_ behavior regarding back annotation as follows:
CLOSE_DIALOG 0 Hide Generate SD BA dialog box on check-in request.
Default.
1 Show the Generate SD BA dialog box on check-in
request.
GUI access:
Setup > Settings, Advanced (category), Hide 'Generate SD
BA dialog' on Check-In request (option)
HIDE_EDM_GENERATE_ xSD Systems Designer. Controls xDM Design Client check-in
FA_SYNCDATA_ON_ behavior regarding forward annotation as follows:
CLOSE_DIALOG 0 Hide Generate FA dialog box on check-in request.
Default.
1 Show the Generate FA dialog box on check-in request.
GUI access:
Setup > Settings, Advanced (category), xDM Design: Hide
'Generate FA dialog' on Check-In request (option)


ICE_AUTOFIT Sets ICT autofit on or off as follows:
0 Turn autofit off
1 Turn autofit on (default)
GUI access:
Setup > Settings, Interconnectivity Table (category), Autofit
Automatically (option)
ICE_CELLS_SHOW_ Sets the ICT cell display characteristics for direction as
DIRECTION follows:
0 Do not display direction. Default.
1 Display direction.
GUI access:
Setup > Settings, Interconnectivity Table (category), Cells
display, Direction (option)
ICE_CELLS_SHOW_ Obsolete.
NAME
ICE_CELLS_SHOW_ Sets the ICT cell display characteristics for pin numbers as
PIN_NUMBER follows:
0 Do not display pin numbers. Default.
1 Display pin numbers.
GUI access:
Setup > Settings, Interconnectivity Table (category), Cells
display (section), Pin number (option)
ICE_COMPONENTS_ Sets the ICT components to display in one of the following
IN_COLUMNS configurations:
0 Show components in rows, nets in columns
1 Show components in columns, nets in rows (default)
GUI access:
Setup > Settings, Interconnectivity Table (category), Show
components in (option)


ICE_PINSDROPDOWN Sets the ICT pin drop-down list to display pin direction as
LIST_SHOW_DIRECTION follows:
0 Do not display pin numbers.
1 Display pin numbers. Default.
GUI access:
Setup > Settings, Interconnectivity Table (category), Pins
drop-down list display (section), Direction (option)
ICE_PINSDROPDOWN Obsolete.
LIST_SHOW_NAME
ICE_PINSDROPDOWN Sets the ICT pin drop-down list to display pin numbers as
LIST_SHOW_PIN_ follows:
NUMBER 0 Do not display pin numbers. Default.
1 Display pin numbers.
GUI access:
Setup > Settings, Interconnectivity Table (category), Pins
drop-down list display (section), Pin number (option)
ICE_SLICEANDDICE_ Sets the ICT Slice and Dice nets choices as one of the
NETS_SHOW_MODE following:
0 Show only nets connected between the components of
Slice and Dice. Default.
1 Show nets connected between and to the components
of Slice and Dice.
2 Show all nets.
GUI access:
Setup > Settings, Interconnectivity Table (category), Slice
and Dice (subcategory)


ICE_SYMBOL_FORMAT Select how Symbol label(s) appear in the Interconnectivity
Table using any combination of the following variables:
$(Name)
$(Symbol)
$(Ref Designator)
You can include formatting characters between the variables
such as space, semicolon, colon and so on.
Default: $(Name)$(Symbol)
GUI access:
Setup > Settings, Interconnectivity Table (category),
Symbol label format (option)
ICT_HIDE_ Show only common properties in ICT viewer.
NOTCOMMON_PRP 0 Shows all properties. Default.
1 Shows only common properties.
GUI access:
Setup > Settings, Interconnectivity Table (category),
Properties (subcategory), Show Common Properties Only
(checkbox)
IMPORT_PADSPE_CL_ Internal use only. Do not modify.
PATH
KEYBINDINGS Control the design entry tool keybindings as follows:
0 The design entry tool uses default keybindings.
1 The design entry tool uses xPCB Layout-style Key
Bindings. Default.
See also:
Key Bindings - xPCB Layout Style on page 437
Key Bindings - Default on page 433
GUI access:
Setup > Settings, Advanced (category), Xpedition Style
Keybindings (option)
LABELBRACKETS Internal use only. Do not modify.
LABELON Obsolete


LABELTHRESHOLD Internal use only. Do not modify.
LABEL_ON_SPLIT Internal use only. Do not modify.
LANGUAGE Set the User Interface language to one of the following:
Default
ENG English
JPN Japanese
PTB Portuguese
CHN Chinese
GUI access:
Setup > Settings, Advanced (category), Language (option)
LINE_GRID If GRIDON is set to 1, LINE_GRID sets the active schematic
or symbol window grid display as follows:
Dotted Grid is displayed as dotted lines.
Lined Grid is displayed as solid lines. Default.
The grid lines or dots display as one line per grid interval
defined by GRID_HR (Grid Spacing).
GUI access:
Setup > Settings, Schematic Editor (category), Grid Type
(option)
LONG_LINE_ERRORS Set the maximum number of characters allowed in an error/
warning message.
Default: 127
MIDSTROKE If STROKES is on (value=1), this setting determines which
mouse button you use to draw predefined patterns in the
schematic window to execute commands or functions as
follows:
0 You draw strokes with the right mouse button. Default.
1 You draw strokes with the middle mouse button.
GUI access:
Setup > Settings, Schematic Editor (category), Strokes,
Pan, and Zoom (subcategory)


MRU_SCHEMA Points to the last-saved user color scheme. The project reopens
to this scheme.
GUI access:
Save (option)
MRU_SETTINGS The design entry tool stores the last-viewed Setup > Settings
dialog box pane as follows:
<key name=MRU_SETTINGS value=<pane_name>/>
The next time you open the Setup > Settings dialog box, this
pane is selected.
Default: Designs
MRU_SIZE Sets the maximum number of Most Recently Used items
displayed in the list.
Default: 6
NAMESON Obsolete.
NAV_BLOCK_FILTER_ Controls filtering for blocks and schematics in the Navigator as
USE_REGEXP follows:
0 Display all blocks or schematics (Wildcard).
1 Use regular expressions in filters to constrain the
displayed list. Default.
GUI access:
Navigator window > right-click block or schematic > Filter


NAV_BLOCK_INFOTIP_ Sets the block info tip format in the Navigator window using
FORMAT any combination of the following variables:
$(Name)
$(View)
Default: $(View): $(Name)
GUI access:
Setup > Settings, Navigator (category), Blocks
(subcategory), Info Tip format (option)
NAV_BLOCK_LABEL_ Sets the block label format in the Navigator window using any
FORMAT combination of the following variables:
$(Name)
$(View)
Default: $(Name)
GUI access:
(subcategory), Label format (option)
NAV_BLOCK_SHEET_ Controls whether or not the sheet range of each block is shown
RANGE_DISPLAY in the Navigator window as follows:
0 Does not display the sheet range of each block in the
Navigator window. Default.
1 Display the sheet range of each block in the Navigator
window.
GUI access:
(subcategory), Display sheet range (option)


NAV_BLOCK_SORT_ Controls the way blocks or schematics are sorted in the
DESCENDING Navigation window according to the chosen property as one of
the following choices:
0 Ascending. Default.
1 Descending.
GUI access:
Right-click schematic node and choose Sort > Ascending or
Descending
NAV_BLOCK_SORT_ Controls the way blocks or schematics are sorted in the
ORDER_BY Navigator window as follows:
0 Name. Default.
1 View.
GUI access:
Right-click schematic node and choose Sort > Name or
View.
NAV_BOARD_FILTER_ Internal use only. Do not modify.
USE_REGEXP
NAV_BOARD_INFOTIP_ Internal use only. Do not modify.
FORMAT
NAV_BOARD_LABEL_ Internal use only. Do not modify.
FORMAT
NAV_BOARD_SORT_ xSD Systems Designer. Sets the board sorting order as follows:
DESCENDING 0 Ascending. Default.
1 Descending.
GUI access:
In the Navigator window, right click a board and choose
Sort > Descending
NAV_BOARD_SORT_ Internal use only. Do not modify.
ORDER_BY


NAV_BUS_INFOTIP_ Sets the format of the info-tip for bus objects in the Navigator
FORMAT window.
Values: $(Name), $(Type), $(Path)
Default: Bus: $(Name)
GUI access:
Setup > Settings, Navigator (category), Nets and Buses
(subcategory), Bus info Tip format (option)
NAV_BUS_LABEL_ Sets the bus label format in the Navigator window using any
FORMAT combination of the following variables:
$(Name)
$(Path)
$(Type)
Default: $(Name)
GUI access:
(subcategory), Bus label format (option)
NAV_CABLE_FILTER_ Internal use only. Do not modify.
USE_REGEXP
NAV_CABLE_INFOTIP_ xSD Systems Designer. Configures the cable info-tip in the
FORMAT Navigator using predefined variables and formatting characters
between the variables such as space, semicolon, colon and so
on.
Variable: $(Name)
Default: Cable: $(Name)
GUI access:
Setup > Settings, Navigator (category), Signals
(subcategory), Cables (group), Info Tip format (option)


NAV_CABLE_LABEL_ xSD Systems Designer. Configures the cable label in the
FORMAT Navigator using predefined variables and formatting characters
between the variables such as space, semicolon, colon and so
on.
Variable: $(Name)
Default: $(Name)
GUI access:
(subcategory), Cables (group), Label format (option)
NAV_CABLE_SORT_ xSD Systems Designer. Controls the way the design entry tool
DESCENDING sorts cable nodes by names as follows:
1 Descending.
GUI access:
Right click on the cable node on the Cables tab and choose
Sort > Ascending or Descending.
NAV_CABLE_SORT_ Internal use only. Do not modify.
ORDER_BY
NAV_COMP_DISPLAY_ Sets how the Navigator displays component symbols as
MODE follows:
0 Display all component symbols. Default.
1 Display hierarchical only.
2 Dont display component symbols.
GUI access:
Setup > Settings, Navigator (category), Symbols
(subcategory), Display all components, Display hierarchical
only, or Dont display components (options)


NAV_COMP_FILTER_ Controls filtering for symbol nodes in the Navigator window as
USE_REGEXP follows:
0 Display all symbols (Wildcard). Default.
displayed list.
GUI access:
Navigator window > right-click a symbol > Filter
NAV_COMP_INFOTIP_ Configures the symbol info-tip in the Navigator using
FORMAT predefined variables and formatting characters between the
variables such as space, semicolon, colon and so on.
Variables: $(Custom), $(Name), $(Symbol), $(Type), $(Path),
$(Ref Designator)
Default: $(Name) $(Symbol)
GUI access:
NAV_COMP_LABEL_ Configures symbol label in the Navigator window using
Variables: $(Custom), $(Name), $(Symbol), $(Type), $(Path)
Default: $(Name)
GUI access:
NAV_COMP_SORT_ Controls the symbols sort order (either descending or
DESCENDING ascending) in the Navigator window as follows:
1 Descending.
GUI access:
In the Navigator window Project tree, right-click a
component, and select Sort > Descending


NAV_COMP_SORT_ Controls the way symbol/component nodes are sorted in the
ORDER_BY Navigator window using one of the following values:
0 Custom.
1 Name. Default.
2 Symbol.
3 Type.
4 Path.
5 Ref Designator.
GUI access:
Right-click on a symbol node > Sort > (option)
NAV_CONNECTOR_ xSD Systems Designer. Specify the use of regular expressions
FILTER_USE_REGEXP in filters for connector nodes as follows:
0 Wildcard. Default.
1 Regular expression.
GUI access:
In the Navigator window Connectors tab, right-click a
connector > Filter. In the Filter connector dialog box, select
Reg. exp.
NAV_CONNECTOR_ xSD Systems Designer. Configures the connector info-tip in
INFOTIP_FORMAT the Navigator using predefined variables and formatting
characters between the variables such as space, semicolon,
colon and so on.
Variables: $(Board), $(Connector Gender), $(Connector Id),
$(Connector Mating Part), $(Name), $(Part Number)
$(Ref Designator), $(Symbol Alias)
Default: $(Connector Id)
GUI access:
Setup > Settings, Navigator (category), Connectors


NAV_CONNECTOR_ xSD Systems Designer. Configures the connector label in the
LABEL_FORMAT Navigator window using predefined variables and formatting
colon and so on.
Variables: $(Board), $(Connector Gender), $(Connector Id),
$(Connector Mating Part), $(Name), $(Part Number)
$(Ref Designator), $(Symbol Alias)
Default: $(Name):$(Part Number)
GUI access:
Setup > Settings, Navigator (category), Connectors
NAV_CONNECTOR_ xSD Systems Designer. Controls the connectors sort order
SORT_DESCENDING (either descending or ascending) in the Navigator window as
follows:
1 Descending.
GUI access:
In the Navigator window Project tree, right-click a
connector, and choose Sort > Ascending or Descending
NAV_CONNECTOR_ xSD Systems Designer. Controls connector nodes sort order in
SORT_ORDER_BY the Navigator window, the Connectors tab, using one of the
following values:
0 Board. Default.
1 Connector Gender.
2 Connector Id.
3 Connector Mating Part.
4 Name.
5 Part Number.
6 Ref Designator.
7 Symbol Alias.
GUI access:
Right-click on a connector node > Sort > (option).


NAV_DISPLAY_SHEETS Depending on which selection you choose, this option displays
icons (shown in the following figure) for each sheet and
composite node within a design in the Navigator tree as
follows:
0 Always
1 Only if there is more than one
2 Never
GUI access:
Setup > Settings, Navigator (category), Sheets
(subcategory), Display sheets (option)
NAV_FLAT_VIEW Controls how the design entry tool displays blocks in the
Navigator window as one of the following:
0 Hierarchical view format as shown in the following
example (default):
1 Flat view format as shown in the following example:

GUI access:
(subcategory), Hierarchical view or Flatten view (options)
NAV_ Obsolete.
FUNCTIONBLOCK_
FILTER_USE_REGEXP
NAV_ Obsolete.
FUNCTIONBLOCK_
INFOTIP_FORMAT


NAV_ Obsolete.
FUNCTIONBLOCK_
LABEL_FORMAT
NAV_ Obsolete.
FUNCTIONBLOCK_
SORT_DESCENDING
NAV_ Obsolete.
FUNCTIONBLOCK_
SORT_ORDER_BY
NAV_ Internal use only. Do not modify.
DOCUMENTBLOCK_
FILTER_USE_REGEXP
DOCUMENTBLOCK_
INFOTIP_FORMAT
DOCUMENTBLOCK_
LABEL_FORMAT
DOCUMENTBLOCK_
SORT_DESCENDING
DOCUMENTBLOCK_
SORT_ORDER_BY
NAV_NET_DISPLAY Controls Navigator window display of nets and buses as
follows:
0 Does not display nets and buses.
1 Does display nets and buses. Default.
GUI access:
(subcategory), Display nets and buses (option)


NAV_NET_FILTER_USE_ Controls filtering for nets in the Navigator window as follows:
REGEXP 0 Display all symbols (Wildcard). Default.
displayed list.
GUI access:
In the Navigator window, right-click Net, click Filter,
NAV_NET_INFOTIP_ Configures the nets info-tip format in the Navigator window
FORMAT using predefined variables and formatting characters between
the variables such as space, semicolon, colon and so on.
Variables: $(Name), $(Type), $(Path)
Default: Net: $(Name)
GUI access:
(subcategory), Net info tip format (option)
NAV_NET_LABEL_ Configures the nets label format in the Navigator window using
Variables: $(Name), $(Type), $(Path)
Default: $(Name)
GUI access:
(subcategory), Net label format (option)
NAV_NET_SORT_ Sets the nets and buses sorting order in the Navigator window
DESCENDING as follows:
1 Descending.
GUI access:
In the Navigator window Project tree, right-click a net, and
select Sort > (option)


NAV_NET_SORT_ Sets the nets and buses sorting order in the Navigator window
ORDER_BY based on one of the following values:
0 Name. Default.
1 Type.
2 Path.
GUI access:
In the Navigator window Project tree, right-click a net, and
select Sort > Name, Type or Path
NAV_SHEET_INFOTIP_ Sets the sheet info tip format in the Navigator window using
Variables: $(Name), $(Number)
Default: $(Number): $(Name)
GUI access:
NAV_SHEET_LABEL_ Sets the sheet label format in the Navigator window using
Variables: $(Name), $(Number)
Default: $(Name)
GUI access:


NAV_SHOW_REPLACE_ Controls whether the design entry tool displays a warning
SHEET_WARNING before replacing selected sheets during a copy in the Navigator
as follows:
0 Do not provide Warning before replacing selected
sheets.
1 Provide Warning before replacing selected sheets.
Default.
GUI access:
(subcategory), Warn before replacing selected sheets during
copy (option)
NAV_SPLICE_INFOTIP_ xSD Systems Designer. Configures the splice info-tip format in
FORMAT the Navigator window using predefined variables and
formatting characters between the variables such as space,
semicolon, colon and so on.
Variable: $(Name)
Default: Splice: $(Name)
GUI access:
Setup > Settings, Navigator (category), Signals (category),
Splices (group), Info Tip format (option)
NAV_SPLICE_LABEL_ xSD Systems Designer. Configures the splice label format in
Variable: $(Name)
Default: Net: $(Name)
GUI access:
(subcategory), Splices (group), Label format (option)


NAV_SPLICE_SORT_ xSD Systems Designer. Controls the way splice nodes are
DESCENDING sorted by their name in the Navigator window.
1 Descending.
GUI access:
Right-click on the splice node and choose Sort > Ascending
or Descending
NAV_SPLICE_SORT_ Internal use only. Do not modify.
ORDER_BY
NAV_SUBSYSTEM_ Obsolete.
FILTER_USE_REGEXP
INFOTIP_FORMAT
LABEL_FORMAT
SORT_DESCENDING
SORT_ORDER_BY
NAV_SYSTEMDESIGN xSD Systems Designer. Specify the use of regular expressions
BLOCK_FILTER_USE_ in filters for block nodes on the Navigator window Blocks tab
REGEXP as follows:
0 Wildcard. Default.
1 Regular expression.
GUI access:
In the Navigator window, right-click a block > Filter. In the
Filter sdblocks dialog box, select Reg. exp.


NAV_SYSTEMDESIGN xSD Systems Designer. Sets the block info tip format in the
BLOCK_INFOTIP_ Navigator window using any combination of the following
FORMAT variables:
$(Board)
$(Name)
$(Symbol)
Default: $(Name): $(Symbol)
GUI access:
NAV_SYSTEMDESIGN xSD Systems Designer. Sets the block label format in the
BLOCK_LABEL_ Navigator window using any combination of the following
FORMAT variables:
$(Board)
$(Name)
$(Symbol)
Default: $(Board)$(Name)
GUI access:
NAV_SYSTEMDESIGN xSD Systems Designer. Controls the way blocks are sorted by
BLOCK_SORT_ their name in the Navigator window.
DESCENDING 0 Ascending. Default.
1 Descending.
GUI access:
In the Navigator window, right-click on the block node and
choose Sort > Ascending or Descending


NAV_SYSTEMDESIGN xSD Systems Designer. Controls block sort order by property
BLOCK_SORT_ORDER_ in the Navigator window Blocks tab as follows:
BY 0 Board. Default.
1 Name.
2 Symbol.
GUI access:
In the Navigator window Project tree, right-click a System
Designer block and choose Sort > Board, Name, Symbol
NAV_WIRE_DISPLAY Internal use. Do not modify.
NAV_WIRE_FILTER_ xSD Systems Designer. Controls filtering for wire nodes in the
USE_REGEXP Navigator window as follows:
0 Display all wires (Wildcard). Default.
displayed list.
GUI access:
In the Navigator window, right-click Wire, click Filter,
NAV_WIRE_INFOTIP_ xSD Systems Designer. Sets the wire info tip format in the
FORMAT Navigator window using predefined variables and formatting
colon and so on.
Variables: $(Name), $(Cable)
Default: Wire:$(Name)
GUI access:
(subcategory), Wire (group), Info Tip format (option)


NAV_WIRE_LABEL_ xSD Systems Designer. Configures the wire label format in the
FORMAT Navigator window using predefined variables and formatting
colon and so on.
Variables: $(Name), $(Cable)
Default: $(Name)
GUI access:
(subcategory), Wires (group), Label format (option)
NAV_WIRE_SORT_ xSD Systems Designer. Sets the wire sorting order in the
DESCENDING Navigator window as follows:
1 Descending.
GUI access:
In the Navigator window Project tree, Right-click a wire, and
choose Sort > (option)
NAV_WIRE_SORT_ xSD Systems Designer. Sets the wire sorting order in the
ORDER_BY Navigator window based on one of the following values:
0 Cable. Default.
1 Name.
GUI access:
In the Navigator window Project tree, Right-click a wire,
and select Sort > Cable or Name
NAV_WIREBUS_INFOTIP xSD Systems Designer. Sets the wire bus info tip format in the
_FORMAT Navigator window using predefined variables and formatting
colon and so on.
Variable: $(Name)
Default: Wire Bus: $(Name)
GUI access:
(subcategory), Wire Buses (group), Info Tip format (option)


NAV_WIREBUS_LABEL_ xSD Systems Designer. Configures the wire bus label format in
Variable: $(Name)
Default: $(Name)
(subcategory), Wire Buses (group), Label format (option)
NAV_WIREBUS_SORT_ xSD Systems Designer. Sets the wire bus sorting order in the
DESCENDING Navigator window as follows:
1 Descending.
GUI access:
and select Sort > (option)
NAV_WIREBUS_SORT_ xSD Systems Designer. Sets the wire bus sorting order in the
ORDER_BY Navigator window based on one of the following values:
0 Cable. Default.
1 Name.
GUI access:
and select Sort > Cable or Name
NET_LENGTH Obsolete.
NET_LENGTH_HR Specifies the length of the stub automatically placed on symbol
pins at instantiation if you select the Add Components with
Nets Stubs option in DataBook.
Default: 1.016e+006
GUI access:
(subcategory), Net Length (option)
NET_SPACING Obsolete.
NET_SPACING_HR Obsolete.


NET_TOOLTIPS Controls the visibility of net tooltips (labels and properties) on
schematics as follows:
0 Hide net tooltips. Default.
1 Display net tooltips.
GUI access:
(section), Nets (option)
NEW_ATTR_VIS Internal use only. Do not modify.
NEW_PROJECT_CL Stores the path to the last central library location entered in the
File > New > Project dialog box.
NEW_PROJECT_ Sets a path to a default central library location that populates
DEFAULT_CL the File > New > Project dialog box. The File > New >
Project dialog box uses this value if NEW_PROJECT_CL is
empty.
Default:
${SDD_HOME}/standard/examples/SampleLib2007/
SampleLib.lmc
Note: The ${SDD_HOME} variable is set for the internal
tool environment when the design entry tool is started.
NEW_PROJECT_ Sets a default location for new projects. The design entry tool
DEFAULT_LOCATION uses this path when NEW_PROJECT_LOCATION is empty. If
empty, the design entry tool uses ${WDIR}/DxProjects.
NEW_PROJECT_ Stores the path to the newest project (File > New > Project)
LOCATION location.
NEW_PROJECT_NAME Sets a default name for new projects. The design entry tool
adds a number suffix when needed.
Default: Project
NON_UNDOABLE_ Internal use only. Do not modify.
MOVE
NO_UNDO_CBA_MOVE Internal use only. Do not modify.


OATCHECK Obsolete.
OATS Obsolete.
OATSTOOLS_FILE_ Obsolete.
BYPASS
ORIENTATION Sets the sheet orientation as one of the following:
0 Landscape (default)
1 Portrait
GUI access:
(subcategory), Sheet Orientation (section), Portrait or
Landscape (option)
PADS_ZOOM Sets the Pan and Zoom behavior to the PADSlayout tool
configuration:
0 Turns off the PADS style pan and zoom. Default.
1 Turns on the PADS style pan and zoom.
DEFAULT_ZOOM and EXPEDITION_ZOOM. Only one
of these should be set to 1 (on) at a time.
GUI access:
and Zoom (subcategory), PADS Pan and Zoom (option)
See also: Panning and Zooming PADS-Style - xDX Designer
PARTIAL_UNLIMITED_ Obsolete.
TEXT_LENGTH
PARTSLISTER_ Sets the name for the Part Lister tool configuration file.
DEFAULTS Default: PartsListerDefaults.ipl
See also:The Part Lister Configuration File
PE_FLOW_MODE Internal use only. Do not modify.


PIN_TOOLTIPS Controls the visibility of pin tooltips (labels and properties) on
schematics as follows:
0 Hide pin tooltips. Default.
1 Display pin tooltips.
GUI access:
(section), Pins (option)
PINTYPE_ARROWS This option is used in conjunction with option
EURO_ARROWS to set the appearance of pintype arrows
between full arrow and half arrow (European) style as follows:
Notes:
The design entry tool only displays pintype arrows for
symbols that have block types of Module and Composite.
The design entry tool does not display pintype arrows for a
block type of Pin.
If a pintype does not exist on the symbol pin, the design
entry tool does not display Pintype Arrows.
Different pin types are represented by different arrows. A list of
these are shown in Settings Dialog Box - Advanced topic.
GUI access:
Setup > Settings, Advanced (category), Pintype Arrows
(option)
PLACEHOLDER Internal use only. Do not modify.


PNUMSON Sets Pin number visibility on schematics as one of the
following:
0 The design entry tool hides Pin numbers. Default.
1 The design entry tool displays Pin numbers.
Note: This setting is used in conjunction with the
OBJECTS > ATTRIBUTE element > VISIBLE setting.
GUI access:
Setup > Settings, Display (category), Common Properties
(option checked), Pin Numbers (option)
PRINTDEVICENAME Stores the last printer used from File > Print.
GUI access:
File > Print, select a printer from the Name dropdown in the
Print dialog box
PRINTFORCEBLACK Controls the black and white print mode setting as follows:
0 Print output contains colors, depending on printer
settings.
1 Print output converts all output to black and white
colors only. Default.
GUI access:
File > Print, check Map Colors to Black in the Print dialog
box
PRINTHIERARCHY Obsolete.
PRINTING Internal use only. Do not modify.
PRINTLINETHICKNESS Sets a minimum line thickness that the design entry tool uses
when printing.
Default: 1
GUI access:
File > Print, enter a Minimum line width in the Print dialog
box


PRINTORIENTATION Internal use only. Do not modify. This entry stores the last-used
Portrait or Landscape setting as follows:
1 Portrait. Default.
2 Landscape.
GUI access:
File > Print, click Properties in the Print dialog box, click
the Printing Shortcuts tab, select Orientation
PRINTPAPERSIZE Internal use only. Do not modify. This entry stores the last-used
paper size.
PRINTSCALE Obsolete.
PRINTSCALEFACTOR Sets a scale factor for the print output. Use a factor of 1 to scale
the print output to 100% of normal. A factor of .9 scales the
output to 90%.
Default: 1
GUI access:
File > Print, choose Scale factor in the Print dialog box
Zoom section, use the up and down arrows to choose a scale
factor
PRINTSCALETYPE Obsolete.
PRINTXMARGIN Obsolete.
PRINTYMARGIN Obsolete.
PROJECT_PLOT_ON_PC Obsolete.


PROPAGATE_PORTS_ Control how the design entry tool handles missing ports to a
TO_SCH lower-level schematic as follows:
0 You must manually add missing ports to a lower-level
schematic from a block using Add > Missing Ports.
1 Any pins that you add to a block automatically causes
corresponding ports to be added to the lower-level
schematic when you execute (right-click) > Push
Schematic from the block. In addition, when you place
parts containing multiple part database slots (multiple parts
in one package), the placed part automatically assigns a slot
number and corresponding pin values.
See also:Connecting Hierarchical Levels in a Top-Down
Design
GUI access:
Setup > Settings, Advanced (category), Propagate Ports to
Schematic (option)
PROPERTIES_TOOLTIP Obsolete.
RB_USE_HOST_DESIGN_ Sets the following Constraint Manager actions with reuse
RULES blocks:
0 The Constraint Manager tool merges clearances and
widths design rules with the reuse block design. Default.
1 The Constraint Manager tool uses the host design rules
for clearances and widths instead of merging them with the
reuse block design.
GUI access:
Setup > Settings, Advanced (category), Reuse Blocks Use
Host Design Rules (option)


REMOVE_ Sets the design entry tool action for mismatched Symbol/Pin
MISMATCHED_PORTS port connectors as one of the following:
Ask You are given a choice at the time the mismatch is
found. Default.
Yes Delete the found mismatched port connectors.
No Do not delete the found mismatched port connectors.
GUI access:
Setup > Settings, Advanced (category), Delete mismatched
Symbol/Pin port connectors (option)


RESET_SCALE_ON_ Controls the way the design entry tool handles a scaled symbol
SYM_UPDATE as follows:
0 When you execute Tools > Update Symbols, the
design entry tool maintains the original local scale factor of
any updated symbols, and also applies any changed scale
factor from the library. Default. For example:
a. Set the scale factor on a symbol to 0.8 in the design entry
tool.
b. Change the scale factor in the Symbol Editor for that
symbol to 0.8.
c. Update the symbol in the design entry tool.
Results: The design entry tool applies both the local scale
factor and the Symbol Editor scale factor to the updated
symbol. The design entry tool rescales the symbol to
0.64.
1 When you execute Tools > Update Symbols, the
design entry tool sets the local symbol scale factor to 1 for
any updated symbols. Using the same scenario in the
previous example:
a. Set the scale factor on a symbol to 0.8 in the design entry
tool.
b. Change the scale factor in the Symbol Editor for that
symbol to 0.8.
c. Update the symbol in the design entry tool.
Results: The design entry tool resets the local scale factor
to 1 on all symbols requiring an update. For this example,
the updated symbol in the design entry tool reflects only
the 0.8 scale factor set in the Symbol Editor.
GUI access:
Setup > Settings, Advanced (category), Reset Component
Scale on Symbol Update (option)
See also:
Scale Symbol Dialog Box (PADS DX Designer Symbol
Editor)
Updating Sheets With Changed Library Symbols


RNUMSON Sets reference designator visibility on schematics as one of the
following:
0 The design entry tool hides reference designators.
1 The design entry tool displays reference designators.
Default.
Note: This setting is used in conjunction with the
OBJECTS > ATTRIBUTE element > VISIBLE setting.
GUI access:
Setup > Settings, Display (category), Common Properties
(option checked), Reference Designators (option)
XREF_ANNOTATION_ Sets Pin number visibility on schematics as one of the
ON following:
0 Do not display cross reference annotations in the entire
design. Default.
1 Display cross reference annotations in the entire
design.
GUI access:
Setup > Settings, Display (category), Xref Annotation
(option)
ROUTE Specifies the routing mode for new connections. Valid settings
are as follows:
0 Straight
1 Orthogonal
2 Avoidance (default)
GUI access:
(subcategory), Route Mode (option)
See also:
Setting Net and Bus Preferences - xDX Designer


RULERS_VISIBLE xSD Systems Designer. Controls the Local Symbol Editor
rulers as follows:
0 Do not display Local Symbol Editor rulers. Default.
1 Display Local Symbol Editor rulers.
GUI access:
Setup > Settings, Symbol Editor (category), Display
(subcategory), Rulers (option)
SCALEFACTOR Provides a scale factor for the selected Font Style that is applied
to the Size property value that appears on all text objects.
Default: 1.0 (100%)
GUI access:
Setup > Settings, Display (category), Font Styles
(subcategory), Scale factor (option)
SCHEMATIC_TABS Controls schematic sheet tabs as follows:
0 The design entry tool displays each schematic sheet as
a separate window.
1 The design entry tool displays each schematic sheet as
a tabbed window. Default.
Can be set to Read-only? No
GUI access:
Window > Schematic Tabs
SCOPE Internal use only. Do not modify.
SD_AUTOMATIC_ xSD Systems Designer. Controls how the tool updates
CONNECTIVITY_ connectivity when you move a System Level Block from one
UPDATE board to another as follows:
0 Requires you to manually update connectivity.
1 Automatically updates connectivity. Default.
GUI access:
Setup > Settings, Advanced (category), System Designer
Automatic Connectivity Update (option)
SD_CONNECTOR_PIN_ Internal use only. Do not modify.
SPACING
SDISTANCE Obsolete. See SDISTANCE_HR.


SDISTANCE_HR Specify a positive integer to set the number of pixels that
determine the selection distance boundary during object
selection on a schematic.
The default value of 254000 sets the increment to 2.54mm, or
0.1in.
GUI access:
Setup > Settings, Advanced (category), Selection Distance
[<Units>] (option)
SE_PIN_LENGTH xSD Systems Designer. Controls the Local Symbol Editor
default pin length in grid points units.
Default: 2 (grid points)
GUI access:
Setup > Settings, Symbol Editor (category), Pins (section),
Default length (option)
SE_PIN_SPACING xSD Systems Designer. Controls the Local Symbol Editor
default pin spacing in grid points units.
Default: 1 (grid point)
GUI access:
Setup > Settings, Symbol Editor (category), Pins (section),
Default spacing (option)
SE_AUTOMATIC_PIN_ xSD Systems Designer. Controls the Local Symbol Editor
SIDE automatic pin side recognition as follows:
0 You must manually rotate the pin if it is not oriented
correctly to the symbol border.
1 Enables the automatic pin side recognition so that
when you place a pin on a symbol border, the pin rotates
itself based on which side you choose. Default.


SE_PIN_PROPERTY_ xSD Systems Designer. Controls the Local Symbol Editor pin
POSITION property position.
Default: Below pin
GUI access:
Setup > Settings, Symbol Editor (category), Properties
(subcategory), Pin property position
SE_SYMBOL_ xSD Systems Designer. Controls the Local Symbol Editor
PROPERTY_POSITION property position.
Default: Below symbol
GUI access:
Setup > Settings, Symbol Editor (category), Properties
(subcategory), Symbol property position
SELBORDERS Controls whether borders are selected as follows:
0 During an area selection, the design entry tool does not
select borders.
1 During an area selection, the design entry tool includes
borders in the selection. Default.
GUI access:
View > Other Windows > Selection Filter, Borders option
SELNAMEON Internal use only. Do not modify.
SELRIPPERS Controls whether rippers are selected as follows:
0 During an area selection, the design entry tool does not
select rippers.
1 During an area selection, the design entry tool includes
rippers in the selection. Default.
GUI access:
View > Other Windows > Selection Filter, Rippers option


SEPARATE_FLIP_ Controls the Flip or Mirror operation when more than one
MIRROR object is selected as follows:
0 The design entry tool flips/mirrors the selected group
of objects against the symmetry axis of the entire selected
group. Default.
1 The design entry tool flips/mirrors the selected group
of objects against each objects symmetry axis.
GUI access:
Setup > Settings, Advanced (category), Flip/Mirror objects
separately (option)
SHEETSIZE Sets the default sheet size for all new schematics and symbols.
Specify one of the following sizes:
(Note: The following values correspond to the SIZES
definitions in Table 2-10 on page 136:)
0 A ()
1 B (, default)
2 C ()
3 D ()
4 E ()
5 A4 ()
6 A3 ()
7 A2 ()
8 A1 ()
9 A0 ()
10 Custom - user-definable width and height using , the
HEIGHT and WIDTH values you specify.
11 F ()
See also:
GUI access:
(subcategory), Size (option)


SHEETZONINGGRID Sets the visibility of schematic zoning grid shown in the figure,
Border, Border Symbol and Zoning Grid as one of the
following:
0 Hide the schematic zoning grid. Default.
1 Show the schematic zoning grid.
See also:
Partitioning a Sheet into Zones - xDX Designer

GUI access:
Setup > Settings, Display (category), Zoning Grid (option)
SHOW_ALIGNMENT_ Controls dynamic alignment marker visibility when moving
MARKS symbols:
0 Do not show the dynamic alignment markers. Default.
1 Show the dynamic alignment markers.
See also:
Dynamically Aligning Components - PADS DX Designer
GUI access: Grid toolbar, Show Alignment Markers
button
SNAPTOPIN Sets net route snapping to the nearest pin of a specified
component as follows:
0 Snap net to pin is off.
1 Snap net to pin is on. Default.
GUI access:
(subcategory), Snap Nets to Pin (option)
SORTON Obsolete.


STAGGER_DISTANCE_ Sets the distance the design entry tool uses when staggering
HR nets. If the value is too small, overlapping nets could result as
shown in the following
figure:
Enter a value as: (value in millimeters) * 100,000. The default

value of 9.08mm or 0.3575in appears in the file as 908000
(9.08mm * 100,000).
STROKE_DELAY Specifies how much time the design entry tool allows for the
user to complete a stroke.
Default: 200 (milliseconds)
STROKES Turns on or off the ability for you to draw predefined patterns
in the schematic window using the mouse, which map to
commands or functions as follows:
0 Turns off strokes.
1 Turns on strokes. Default.
See also:
MIDSTROKE control which mouse button draws the
strokes.
Key Bindings and Strokes on page 433
GUI access:
and Zoom (subcategory), Strokes off (option)
SG_PROPERTIES Internal use only. Do not modify.
SG_PINS_IN Internal use only. Do not modify.
SG_PINS_OUT Internal use only. Do not modify.
SG_PIN_LABEL_SIZE Internal use only. Do not modify.


SG_PIN_LENGTH Internal use only. Do not modify.
SG_PIN_SPACING Internal use only. Do not modify.
SG_SYM_ATTR_SIZE Internal use only. Do not modify.
SG_PINTYPE_ANALOG Internal use only. Do not modify.
SG_PINTYPE_IN Internal use only. Do not modify.
SG_PINTYPE_BI Internal use only. Do not modify.
SG_PINTYPE_OCM Internal use only. Do not modify.
SG_PINTYPE_OEL Internal use only. Do not modify.
SG_PINTYPE_OUT Internal use only. Do not modify.
SG_PINTYPE_TRI Internal use only. Do not modify.
TABSSHEET_NAMES_ Controls what information the design entry tool displays in the
ONLY schematic tabs as follows:
0 The design entry tool displays the schematic name
followed by the sheet name on schematic tabs as shown
below:
Default.
1 The design entry tool displays only the schematic sheet

name on schematic tabs as shown below:

GUI access:
Setup > Settings, Advanced (category), Display Only Sheet
Names in Tabs (option)
TEXTON Obsolete.


TEXTORIGIN Sets the default origin point for all new text, labels, and
properties you create. Valid values (options) are:
0 Lower center
1 Lower left
2 Lower right
3 Middle center (default)
4 Middle left
5 Middle right
6 Upper center
7 Upper left
8 Upper right
Setup > Settings, Schematic Editor (category), Text
(subcategory), Default Text Origin (option)
TEXTSIZE Obsolete. Use TEXTSIZE_HR.
TEXTSIZE_HR Sets text size for all new text, labels, and properties you create.
Enter a value as: (value in millimeters) * 100,000. The default
value of 2.54mm or 0.10in appears in the file as 254000
(2.54mm * 100,000).
Setup > Settings, Schematic Editor (category), Text
(subcategory), Default Text Size (option)
TEXT_THRESHOLD Internal use only. Do not modify.
TIPOFTHEDAY Controls how the Tip of the Day is displayed as follows:
0 Do not display the tip of the day when you start the
design entry tool.
1 Display the tip of the day when you start the design
entry tool. Default.
Help > Tip of the Day
TIPOFTHEDAYFILEPOS Internal use only. Do not modify.
TIPOFTHEDAY Internal use only. Do not modify.
TIMESTAMP
UNDO Internal use only. Do not modify.
UNDO_LEVEL Internal use only. Do not modify.


UNIQUE_LABEL Controls the design entry tool labeling behavior when you copy
nets, components, or pins as follows:
0 Do not automatically create a unique label during a
copy operation. Default.
1 The design entry tool automatically creates a unique
label during a copy operation.
GUI access:
Setup > Settings, Advanced (category), Unique names on
copy (option)
UNIT Sets the design entry tool unit of measurement as one of the
following:
mm millimeters
cm centimeters
in inches (default)
Once set, the design entry tool uses the unit of measurement
you have chosen for measurements such as SHEETSIZE
(Default Sheet Size) and GRID_HR (Grid Spacing).
GUI access:
Setup > Settings, Schematic Editor (category), Unit (option)
UNLIMITED_TEXT Internal use only. Do not modify.
UPDATE_OBJECTS_ Internal use only. Do not modify. Stores settings for Tools >
PAGENUMBERS Update Other Objects.
ANNOTATIONS Update Other Objects.
BUS_RIPPERS Update Other Objects.
BUS_SIGNALS Update Other Objects.
PROPERTIES Update Other Objects.
RANGE Update Other Objects.
UPDATE_OBJECTS_SD_ Internal use only. Do not modify. Stores settings for Tools >
RANGE Update Other Objects.


USEEXCLUDEINFO Controls which sheets (if any) to exclude from printing or PDF
generation as follows:
0 Do not exclude designated sheets from printout.
1 Exclude designated sheets from printout. Default.
See also:
Excluding Sheets from Printing - xDX Designer -
GUI access:
File > Print, Print dialog box, Use exclusion info checkbox
USERNAME xSD Systems Designer (only).
Specify the owner name you want to apply to an objects
Owner property. By default, an objects owner property is the
operating system user name (value="$osusername"). This key
only appears in the local DxDesigner.xml file if the User name
is not the operating system user name.
Setup > Settings, User Information (category),
Use operating system user name and User name
VALUESON Obsolete.
VERIFY_EXPEDITION_ Obsolete.
CONFIG_FILE
VERIFY_NETLIST_ Obsolete.
CONFIG_FILE
VERIFY_ Obsolete.
SYSTEMDESIGN_
CONFIG_FILE
WHITEBACKGROUND_ Internal use only. Do not modify.
MODE
WIREON Internal use only. Do not modify.
WIR_CONT_CHAR Obsolete.
WIR_FILE_ Obsolete.
CONTINUATION
WRITE_HIRES_ Obsolete.
SYMBOL_FILES


XPROB_HLU_ENABLE Controls cross probing to highlight unplaced components as
follows:
0 Do not highlight unplaced components during cross
probing.
1 Highlight unplaced components during cross probing.
Default.
GUI access:
Setup > Settings, Cross Probing (category), Highlight
unplaced components (section), Enable (option)
XPROB_HLU_ Controls cross probing to highlight unplaced components only
LIMITOPEN on open schematics or ICTs as follows:
0 Do not limit the highlight of unplaced components
during cross probing to only open schematics or ICTs.
1 Limit the highlight of unplaced components during
cross probing to only open schematics or ICTs. Default.
GUI access:
Setup > Settings, Cross Probing (category), Highlight
unplaced components (section), Limit to already open
documents (option)
XPROB_SEL_ Use this setting to limit cross probing between the design entry
LIMITOPEN tool and other applications, such as xPCB Layout as follows:
0 Allow cross probing with other applications to any
applicable the design entry tool schematic or ICT.
1 Limits cross probing with other applications to just
open the design entry tool schematics or ICTs. Default.
GUI access:
Setup > Settings, Cross Probing (category), Limit selection
to already open documents (option)


XPROB_SEL_ (This setting is not applicable unless
LIMITOPEN_COMP XPROB_SEL_LIMITOPEN=1.)
Use this setting to further specify limits for cross probing
between the design entry tool and other applications, such as
xPCB Layout as follows:
0 Do not allow cross probing components on already
open documents. Default.
1 Allows cross probing with components on already
open documents.
GUI access:
to already open documents (option checked), for
Components (option)
LIMITOPEN_NET XPROB_SEL_LIMITOPEN=1.)
0 Do not allow cross probing with signal nets on already
1 Allows cross probing with signal nets on already open
documents.
GUI access:
to already open documents (option checked), for Signal Nets
(options)


LIMITOPEN_ XPROB_SEL_LIMITOPEN=1.)
GLOBALNET Use this setting to further specify limits for cross probing
0 Do not allow cross probing with global nets on already
1 Allows cross probing with global nets on already open
documents.
GUI access:
to already open documents (option checked), for Global Nets
(option)
LIMITOPEN_PIN XPROB_SEL_LIMITOPEN=1.)
0 Do not allow cross probing with global nets on already
1 Allows cross probing with global nets on already open
documents.
GUI access:
to already open documents (option checked), for Pins
(option)
XPROB_SEL_ZOOMFIT This setting controls whether the design entry tool zooms in on
the selected, cross-probed object. This setting also works with
dynamic links, to zoom in on the target object when a link is
traversed.
0 Do not zoom in to selected objects during cross
probing. Default.
1 Zoom in to selected objects during cross probing.
GUI access:
Setup > Settings, Cross Probing (category), Zoom Fit to
Selected objects (option)


XTRAERRS Control the design capture tool Check utility as follows:
0 Do not provide additional Check utility testing.
1 Provide additional Check utility testing and error
reporting operations. Default.
Table 2-10. DxDesigner.xml DxDesigner SIZES Section

A_SIZE_HR Predefines the A sheet default size used by = 0 as the following:
21590000 HEIGHT (215.90mm or 8.5in)
27940000 WIDTH (297.4mm or 11.0in)
The value is set as: (value in millimeters) * 100,000.
GUI access:
(subcategory), Size = A (option)
B_SIZE_HR Predefines the B sheet default size used by = 1 as the following:
27940000 HEIGHT (279.4mm or 11.0in)
43180000 WIDTH (431.8mm or 17.0in)
GUI access:
(subcategory), Size = B (option)
C_SIZE_HR Predefines the C sheet default size used by = 2 as the following:
43180000 HEIGHT (431.8mm or 17.0in)
55880000 WIDTH (558.8mm or 22.0in)
GUI access:
(subcategory), Size = C (option)

Table 2-10. DxDesigner.xml DxDesigner SIZES Section (cont.)

D_SIZE_HR Predefines the D sheet default size used by = 3 as the following:
55880000 HEIGHT (558.8mm or 22.0in)
86360000 WIDTH (863.6mm or 34.0in)
GUI access:
(subcategory), Size = D (option)
E_SIZE_HR Predefines the E sheet default size used by = 4 as the following:
86360000 HEIGHT (863.6mm or 34.0in)
111760000 WIDTH (1,117.6mm or 44.0in)
GUI access:
(subcategory), Size = E (option)
A4_SIZE_HR Predefines the A4 sheet default size used by = 5 as the
following:
20999999.91 HEIGHT (210.0mm or 8.268in)
29699999.02 WIDTH (297.0mm or 11.693in)
GUI access:
(subcategory), Size = A4 (option)
following:
29699999.02 HEIGHT (297.0mm or 11.693in)
41999999.82 WIDTH (420.0mm or 16.535in)
GUI access:


following:
41999999.82 HEIGHT (420.0mm or 16.535in)
59400000.58 WIDTH (594.0mm or 23.386in)
GUI access:
following:
59400000.58 HEIGHT (594.0mm or 23.386in)
84099999.44 DxDesigner.xml Miscellaneous DxDesigner
Settings Section WIDTH (841.0mm or 33.110in)
GUI access:
following:
84099999.44 HEIGHT (841.0mm or 33.110in)
118900000.96 WIDTH (1189.0mm or 46.811in)
GUI access:


Z_SIZE_HR Sets a custom sheet size for new schematics. If value="10", then
the design entry tool uses the following the HEIGHT and
WIDTH settings you define in the SIZES section:
<size name="Z_SIZE_HR">
<key name="HEIGHT" value="your_value"/>
<key name="WIDTH" value="your_value"/>
</size>

The default HEIGHT and WIDTH value of 2540000 sets the
sheetsize to 254mm or 10in square.
GUI access:
(subcategory), Size = Custom (option)
Table 2-11. DxDesigner.xml Databook SETTINGS Section

DXDB_AUTO_ 1 Default.
QUERY_LIBRARIES
DXDB_AUTO_SIZE_ 0 Default.
RESULTS_COLUMNS
DXDB_COLLAPSE_ 0 Default.
SYMBOLS
DXDB_CONNECT_ 0 Default.
TABLES_WHEN_
LOADING
DXDB_DETECT_BAD_ 1 Default.
CRITERIA
DXDB_DISPLAY_ 1 Default.
NUMERICS_WITH_
MAGNITUDE
DXDB_ENABLE_COLUMN 0 Default.
_TOOTIPS
DXDB_ENABLE_DMS_ 1001 Default.
CONNECTOR
DXDB_IGNORE_ 0 Default.
COMPOSITES

Table 2-11. DxDesigner.xml Databook SETTINGS Section (cont.)

DXDB_POSITION_ALL_ 0 Default.
LIBRARIES_FIRST
DXDB_QUERY_RESULTS_ 400 Default.
LIMIT
DXDB_QUERY_TIMEOUT 60 Default.
DXDB_SEARCH_DISPLAY 0 Default.
_PROPERTIY_NAMES
DXDB_STRIP_FROM_ PWD Default.
CONNECT_STRING
DXDB_UPDATE_TABLES_ 0 Default.
WHEN_LOADING
DXDB_USE_CACHE 0 Default.
DXDB_COLOR_SEARCH_ 0x000000 Default.
TEXT
LINK_TEXT
DXDB_COLOR_SEARCH_ 0x0000ff Default.
HIGHLIGHT
DXDB_COLOR_SEARCH_ 0xf5f5e1 Default.
EVEN_BCKGND
DXDB_COLOR_SEARCH_ 0xfffff5 Default.
ODD_BCKGND
CRITERIA_TEXT
DXDB_COLOR_SEARCH_ 0xe9e9e9 Default.
CRITERIA_BCKGND
DXDB_COLOR_VERIFY_ 0x000000 Default.
TEXT
DXDB_COLOR_VERIFY_ 0xebebe1 Default.
EVEN_BCKGND
DXDB_COLOR_VERIFY_ 0xf5f5eb Default.
ODD_BCKGND
DXDB_DO_NOT_STORE_ 0 Default.
USER_CREDENTIALS
DXDB_DROPBOX_ Null Default.
LOCATION

Related Topics
The Design Entry Tool Environment Variables
Read-only User-Preference Settings

Part Lister Initialization File Format

Input for: PADS DX Designer Part Lister
A Part Lister initialization file (<name>.ipl) stores Tools > Part Lister settings. The Part Lister
both reads from, and writes to a <name>.ipl file.
Format
A Partlister.ipl file has the following structure:
<?xml version="1.0"?>
<PartListerConfiguration version="3">

<Entry name="name" value="CORPORATE"/>
<Entry name="outputFormat" value="PLAIN"/>
<Entry name="outputFileExt" value="txt"/>
<Entry name="pagination" value="YES"/>
<Entry name="pagelength" value="150"/>
<Entry name="delimiter" value=" "/>
<Entry name="delimiterbefore" value="NO"/>
<Entry name="delimiterafter" value="NO"/>
<Entry name="addTitleRow" value="YES"/>
<Entry name="ignoreColumnWidths" value="NO"/>
<Entry name="open" value="YES"/>
<Header>

</Header>
<Columns>

</Columns>
<Preprocessor> 

 <Rule attribute="Part Number">
<Logic regexp="(.*)\|(.*)" value="\1"/>
</Rule>

<Rule attribute="CLASS" name="Part List Exclude">
<Logic regexp="EMB" value="True"/>
</Rule>
</Preprocessor>
</PartListerConfiguration>
The lines that define miscellaneous configuration settings in the Partlister.ipl file have the
following format:
<Entry name="setting_name" value="setting" />

Note
You should only change the setting value.
If the readonly=1 option has been applied to an entry name in the Partlister.ipl file, such as:
<Entry name="outputFormat" value="PLAIN" readonly=1/>, the associated setting cannot
be changed in the Tools > Part Lister dialog box.
Parameters
The following tables list the setting names and describes the editable parameter values in
each section of the <name>.ipl file:
o Part Lister Initialization File Miscellaneous Settings Section
o Part Lister Initialization File Header Section
o Part Lister Initialization File Columns Section
Table 2-12. Part Lister Initialization File Miscellaneous Settings Section

outputVersion Defines the output version. Do not change.
1 Default
outputFormat Set the Part Lister report output format as one of the following:
Text File Produces a text file. Default
HTML Produces an HTML file.
EXCEL Produces an Excel spreadsheet.
See also: Part Lister output format description
GUI access:
Tools > Part Lister > General (tab), (report) Output format
(option)
pagination Set the Part Lister output to paginate into separate pages as follows:
NO Do not split into pages. Default.
YES Separate into separate pages, with a length determined by
the pagelength setting.
GUI access:
Tools > Part Lister > Advanced (tab), (Text Output) Split into
pages (option)


pagelength If pagination=YES, set the number of lines per page for the Part Lister
output.
65535 lines per page. Default.
GUI access:
Tools > Part Lister > Advanced (tab), (Text Output) Split into
pages, ____lines each (option)
delimiter Specifies a delimiter character (such as pipe | ) between columns.
Example:
<Entry name="delimiter" value=" |"/>
GUI access:
Tools > Part Lister > Advanced (tab), Delimiter (option)
See also: Delimiter - Examples
delimiterbefore Controls the column delimiter placement in front of the first column
as one of the following:
NO Do not add the column delimiter in front of the first
column. Default.
YES Add the column delimiter in front of the first column.
GUI access:
Tools > Part Lister > Advanced (tab) > (Delimiter) > Before first
column
delimiterafter Controls the column delimiter placement after the last column as one
of the following:
NO Do not add the column delimiter after the last column.
Default,
YES Add the column delimiter in front of the first column.
GUI access:
Tools > Part Lister > Advanced (tab) > (Delimiter) > After last
column (option)
addTitleRow Controls the Titles row that appears at the top of each column in the
Part Lister output as follows:
NO Do not add the Titles row at the top of each column.
YES Add the Titles row at the top of each column. Default,
GUI access:
Tools > Part Lister > Advanced (tab), (Header) Add Title Rows
(option)
See also: (Header) Add Title Rows - Examples


ignoreColumnWidths Controls the Part Lister use of column width settings in Text Output
as follows:
NO Do not use the column width settings.
YES Use the column width settings. Default,
GUI access:
Tools > Part Lister > Advanced (tab), (Text Output) Ignore
Column Widths (option)
See also: The examples in the Ignore Column Widths description
Table 2-13. Part Lister Initialization File Header Section

(Lines in Header Specify a Part Lister table header by adding lines in this Header
section) section such as the following:
text <Line text="Part Lister output for $(NAME)"/>
<Line text="Generated on $(DATE)"/>
The Part Lister provides the following fields to help you customize
the header:
$(NAME) - Name of the Project, Board or Block (see example
below)
$(DATE) - As shown in the example below
$(TIME) - such as 14:45:28 (hh:mm:ss)
$(VARIANT) - If PADS DX Designer is in the Variant mode (it
means that the variant view was created in the Variant
Managerwindow), this field displays the data specified in the
current variant.
Tip: If you want to add a blank line between the Part Lister output
Header and the first row, use the following blank line as the final
header line:
<Line text=" "/>
GUI access:
Tools > Part Lister > Advanced (tab), Header (text box)

Table 2-14. Part Lister Initialization File Columns Section

Setting Setting Description and Setting Values
Name
dec If type = PROPERTY, use the dec (decimal) argument to define the number of
decimal places (digits after decimal point). If the value displayed in the column
is not a real number, this setting is ignored.
If you specify 0 as dec value, all numbers in the column are rounded to the
nearest integer value.
Example:
<Column type="PROPERTY" property="Cost" label="Cost"
width="8" sum="YES" dec="2" key="SECONDARY"
display="Compress"/>
GI access:
Tools > Part Lister > Columns (tab), Display (section), Decimal (option)
delimiter If type = PROPERTY and display = Full or display = Compressed, this setting
defines the delimiter used if a list of values is displayed in a column. May be
any string of characters. The default is the space character.
Example:
<Column type="PROPERTY" property="Id" label="test"
width="10" justification="RIGHT" sum="NO" display="Full"
delimiter=", "/>
GUI access:
Tools > Part Lister > Columns (tab), Display (section), List Delimiter
(option)

Table 2-14. Part Lister Initialization File Columns Section (cont.)

Name
display If Column type = PROPERTY, use the display setting to configure the column
display mode as one of the following:
Full Values for all objects are displayed as a list. The values are sorted
alphanumerically. If there is more than one object with the same value, the
value is repeated the appropriate number of times.
Slots Values for all objects are displayed as a list. The values are sorted
value is repeated the appropriate number of times. The slot values are
appended after a slash character (such as: U1/1, U1/2, U2/1).
Compress All values are sorted alphanumerically. Repeated values are
removed. Then ranges such as A1, A2, A3 are shortened to A1-A3. Slots are
never appended.
Unique All values are sorted alphanumerically. Repeated values are
removed. A list such as IC1, IC1, IC2, IC3, IC3, IC5 is shortened to IC1,
IC2, IC3, IC5.
Total The column displays the total of all numeric values for all objects.
Non-numeric values are ignored.
Default: Compress
Example:
<Column type="PROPERTY" property="Part Number" label="Part
Number" width="15" justification="RIGHT" sort="ASCENDING"
key="PRIMARY" display="Compress"/>
GUI access:
Tools > Part Lister > Columns (tab), Display (section), Mode (pulldown)
justification Use this argument to set the alignment of the column as one of the following:
CENTER
LEFT
RIGHT
Example:
GUI access:
Tools > Part Lister > Columns (tab), Display (section), Align (pulldown)


Name
key If type = PROPERTY, set key to one of the following:
PRIMARY (Required) This sort key must be applied to at least one
column of type PROPERTY, such as the default column Part Number as
shown in the following Example 1. If a Primary Key is not present on one of
the columns, the Part Lister output will be blank.
The purpose of this key is to define which column is used as the primary
sort.
Secondary Key This secondary sort key can be applied to at least one
column of type Property, such as the default column Ref Designator as
shown in the following Example 2.
The purpose of this key is to determine which column to sort on if there are
identical values listed in the Primary Key row.
Example:
1. <Column type="PROPERTY" property="Part Number"
label="Part Number" width="15" sort="ASCENDING"
priority="2" key="PRIMARY" display="Compress"/>
2. <Column type="PROPERTY" property="Ref Designator"
label="Ref Designator" width="15" key="SECONDARY"
--------EXAMPLE REPORT OUTPUT USING ABOVE SETTINGS-------
|# |QTY |Part Number |Ref Designator |Cost |
-----------------------------------------------------------
| 1 | 1 |74LS08-SMD |U2 |1.32 |
...
| 6 | 3 |R47-2512 |R1-R3 |0.50, |
| | | | |0.50,0.50 |
| | | | |--------- |
| | | | |8.14 |


Name
priority If Column type = PROPERTY and key=PRIMARY, and in addition, if
sort=ASCENDING or sort=DESCENDING, the priority argument determines
the sorting priority when more than one column has sort = ASCENDING or sort
= DESCENDING.
The priority value is set as an integer in the range 0-9. The value 9 means the
highest priority. The Part Lister first sorts the column with the highest priority.
If duplicate values occur in the first column, the Part Lister continues the sort
using lower priority columns. If there is more than one column with the same
priority, the order of column definitions (from top to bottom in the file)
determines the priority.
Example:
<Column type="PROPERTY" property="Part Number"
label="Part Number" width="14" justification="LEFT"
sort="ASCENDING" key="PRIMARY" priority="5"
<Column type="PROPERTY" property="Value" label="Value"
width="5" justification="LEFT" sort="ASCENDING"
key="PRIMARY" priority="4" display="Compress"/>
See also: BOM Output Example: Sorting Rows With One or More Columns
Designated as Primary
GUI access:
Tools > Part Lister > Columns (tab), Sort (section), Priority (field)


Name
property If the Column type = PROPERTY, use this property argument to specify one
of the Common Properties (.prp), which represents the row values for this
column. Additionally, this field supports the following properties not in the list
of Common Properties:
Name
Id
Partition
Symbol Name
Sheet
Sheet Number
Block
Architecture (applicable to Systems Design projects only)
Function (applicable to Systems Design projects only)
Example:
GUI access:
Tools > Part Lister > Columns (tab), Property (pulldown)
sum Sets the column to total the numerical value of all data in the column as follows:
NO Does not total the numerical value of all data in the column. This is
the same behavior as leaving the sum setting out of the Column definition.
YES Totals the numerical value of all data in the column.
If the result of the summing produces more than the maximum number of
digits allowed for a particular field (specified by width), the sum total is
truncated on the right side. To indicate that a truncation has occurred, the
Part Lister places a hyphen ( -) on the right side of the total.
Example:
<Column type="PROPERTY" property="Cost" label="Cost"
width="9" justification="LEFT" sum="YES" dec="2"
display="Full"/>


Name
sort If type = PROPERTY and key=PRIMARY
Set whether the output is sorted by the contents of the column as one of the
following:
None If you leave the sort setting out of the column specification, the
column does not determine the sorting order.
ASCENDING The column contents sorts in ascending order
DESCENDING The column contents sorts in descending order
The sort is alphanumeric (meaning that A2 goes before A11) and case-
insensitive.
Example:
Number" width="15" sort="ASCENDING" priority="2"
See also:
BOM Output Example: Sorting Rows With One or More Columns Designated
as Primary
GUI access:
Tools > Part Lister > Columns (tab), Sort (section)
text If the Column type = TEXT, use this text argument to specify a text value that
is displayed in the column rows.
Example:
<Column type="TEXT" label="test" width="10"
justification="RIGHT" text="test
text"/>
GUI access:
Tools > Part Lister > Columns (tab), Text (field)


Name
type Choose a column type as one of the following:
NUMBER The column represents sequential row numbers.
QUANTITY The column represents quantities.
PROPERTY The column represents the value of a pre-defined property,
as selected in the Property pull-down list.
TEXT The column represents text. Use the setting text= to add the
text.
Examples:
<Column type="NUMBER" label="#" width="3" visible="NO"/>
<Column type="QUANTITY" label="QTY" width="5"/>
<Column type="TEXT" label="test" width="10"
justification="RIGHT" text="test text"/>
GUI access:
Tools > Part Lister > Columns (tab), Type (pulldown)
visible Set the column visibility in the output as follows:
NO Hide the column in Part Lister output.
YES Make the column visible in the Part Lister output.
Note that even if a column is hidden, it still may be used for sort order.
Example:
<Column type="NUMBER" label="#" width="3" visible="NO"/>
GUI access:
Tools > Part Lister > Columns (tab) > Display (section), Hidden (option)
width Use this argument to specify the column width in characters. The value is an
integer in the range 1-1000. Any text longer than the specified width is right-
justified, and the last character is replaced with a hyphen (-).
Example:
GUI access:
Tools > Part Lister > Columns (tab) > Display (section), Width (option)
Related Topics
Part Lister Dialog Box - General Pane

Part Lister Dialog Box - Columns

Part Lister Dialog Box - Advanced Pane
Creating a Part Lister Configuration File

project.prj File Format

Input for: PADS DX Designer
The design entry tool creates a <project>.prj file under each project folder when you open a
new project to hold the project-specific settings and configurations.
Format
A <project>.prj is divided into major sections as shown in Figure 2-8. (Indentation is provided
in the example for readability.)
Figure 2-8. Project File Section Structure
SECTION DesignInfo

<TargetDirectory Path="C:\gary_archives"/> 
<Compression Type="Zip"/> 
<PDF Type="1"/> 
<AdditionalFiles>
<File Path="C:\project_archives\Archiver_test"/>
</AdditionalFiles>
</DxArchiverProject>
Related Topics
xDX Archiver Wizard

sch2pdf
sch2pdf
In addition to using the DxPDF interface, you can also generate PDF files for schematics from
the DOS or UNIX command line. The command line program is named sch2pdf.exe.
Usage
sch2pdf -project <project_file> [-eevm <filename>] [-a <output_filename>]
[-c <colorCode>] [-g* global_override] [-i <hyperlink>] [-l <level>]
[-o <order>] [-s] [-p] [-f] [-v] [-u <font_name>]
[-schematic <name>]
Parameters
Command line options are described in the following tables.
Table 4-2. Command Line Options for Generating a PDF File
Option Description
-a Overrides the default output filename of <design>.pdf
-c Refer to Color Code in the following table for a list of colorCode options.
-eevm Switches on generation PDF in eevm mode
-f Displays a PDF file in Adobe Acrobat with a list of fonts supported on your
system
-i Interprets component attribute values as potential URLs
-p Adds a pop-up menu on components
-project Path to the .prj project file
-s Starts the Adobe Acrobat viewer and displays the output file
-schematic Specify the name of only one particular schematic to be generated.
-u Disable font mapping for a particular named font.
-v Makes all hyperlinks visible in a PDF document
Command line color codes are described in the following table:
Table 4-3. Command Line Color Codes For Generating a PDF File
Color Code Description
0 Black on white, suppresses black text
1 Color on white
2 Color on black
3 Black on white, prints text in black

sch2pdf
Other command line options are described in the following table:

Table 4-4. Additional Command Line Options for Generating a PDF File
Option Description
global override Overrides memory allocation defaults. Use only on very large designs that
do not otherwise complete.
hyperlink Component property names whose values are checked as legal URLs
level Property to stop descending composite symbols (specifies multiple levels
separately)
order Component property names whose values override sheet order (use with
Scout)
Advanced options for use on very large designs are shown in the following table:
Table 4-5. Advanced Command Line Options for Generating a PDF File
Option Description
ga Maximum number of annotations
go Maximum number of objects
gp Maximum number of pages
Related Topics
DxPDF interface - xDX Designer

vdrc (Design Rule Checker)
vdrc (Design Rule Checker)

In addition to using the Verify dialog box, you can also run the DRC from the DOS or UNIX
command line. The command line program is named vdrc.
Usage
vdrc -proj <project_file.prj> -block <block_name> -def <definition_filename>
[-dxd_std] [-group <group_name>] [-hier] [-page <sheet_name>]
-set <settings_filename> [-ssc] [-usage]
Arguments
Table 4-6. Command Line Options for vdrc Command
Option Description
-proj (Required) Specify a path to the project_file.prj file. The vdrc command uses
the .prj file contents to determine settings such as the Bus Contents and others,
which will override any duplicate settings that might appear on the command
line.
-block (Required) Specify the block that vdrc will check.
-def (Required) Specify the path to the default Verify configuration file. This file
contains settings usually specified by an administrator for multiple users or to
determine standardized checks. If you do not specify this file, vdrc uses the
default file stored with the installation for your type of project, such as
C:\...\standard\VerifyDefaults.ini or C:\...\standard\VerifyDefaultsSD.ini .
-dxd_std If specified, the vdrc output is formatted for , with HTML tags with links to the
objects.
-group Specify the Verify group_name in order to execute all checks within the
specified group such as Connectivity, Electrical, and so on.
-hier If specified, vdrc checks the specified block and all hierarchy below the block.
-page If you specify a page sheet_name, only that sheet will be verified.
-set (Required) Specify the path to the user settings stored in a Verify.ini
configuration file. If you do not specify this path, the settings defined in the
Default Verify configuration file will be used. See the -def option above.
-ssc Applicable only if you have xSD Systems Designer installed. Checks the
architectural view in a xSD Systems Designer design.
-usage Displays the vdrc command usage information.
Related Topics
Verify Dialog Box

Design Entry Tool Command Line Commands

The design entry tool commands are grouped alphabetically. Online viewers can click on a
letter below to access each alphabetic group:
Table 4-7. A - Command Line Commands

Command Description
A
ansize n = 0 through 4
Changes the schematic or symbol sheet size of the active window to an.
When you execute this command, the sheet size automatically changes to an.
(Executing this command does not change the project settings for sheet
size.)
adistance Sets the avoidance distance between components. The routing distance can
be specified with the aroute command. A connection is automatically
staggered by the avoidance distance as the route hugs to the components or
other connections.
ainvis Makes the specified attribute invisible in the active schematic or symbol
window. If you enter the ainvis command on the command line and execute
the command, the Make Attribute Invisible dialog box appears. You can
either enter an attribute name in the Name field to make a specific invisible,
or you can leave the wildcard (*) symbol in the Name field to make all
properties invisible.
align Aligns the selected components to a side of the window.
Syntax: align side
where side equals one of: left, right, top, or bottom.
anvis Makes the name portion of the specified properties visible in the active
schematic or symbol window. The Make Attributes Name Visible dialog
box appears. Enter the attribute name in the Name field and click OK. You
can use the wildcard characters when entering the attribute name.
aoff Changes the attributes settings to off.
aon Changes the attributes settings to on.
arc Adds an arc in the schematic or symbol drawing. Arcs are dynamically
created by specifying the endpoints and stretching the segment to specify the
arc.
Also see:
Creating and Editing Graphical Objects on a Sheet - xDX Designer

Table 4-7. A - Command Line Commands (cont.)

Command Description
aroute Changes the routing mode to full avoidance routing. Executing this
command changes the routing mode specified in the DxDesigner.xml file
(key name=ROUTE value=2) to avoidance routing.
array Creates an array for one or more selected objects. Arrays are created by
selecting the command and defining the relative or absolute spacing.
Using positive values for the spacing settings creates the array to the right
and/or upward in the window.
Also see:
Creating a Graphical Component Array - xDX Designer
arrowson Turns on Pintype Arrows
arrowsoff Turns off Pintype Arrows
asize Changes the schematic or symbol sheet size of the active window to a. When
you execute this command, the sheet size automatically changes to a.
(Executing this command does not change the project settings for sheet
size.)
avis Makes the specified attributes visible in the active schematic or symbol
window.
To make an attribute visible, enter the avis command from the command
line. The Make Attributes Visible dialog box appears. Enter the attribute
name in the Name field and click OK. You can use the wildcard characters
when entering the attribute name
avvis Makes the value portion of the specified attributes visible in the active
schematic or symbol window.
To make a value visible, enter the avvis command from the command line.
The Make Attribute Value Visible dialog box appears. Enter the attribute
name in the Name field and click OK. You can use the wildcard characters
when entering the attribute name.
Table 4-8. B - Command Line Commands

Command Description
B
bb This command brings up the Change Bounding Box dialog that allows you to
modify the bounding box of your current drawing.
L1X: Lower left x-coordinate (should typically be 0)
L1Y: Lower left y-coordinate (should typically be 0)
UrX: Upper right x-coordinate (should typically be width of drawing)
UrY: Upper right y-coordinate (should typically be height of drawing)

Table 4-8. B - Command Line Commands (cont.)

Command Description
bcast Turn broadcasting on or off.
bcomposite Set blocktype composite.
bcopy Copies the selected objects or areas of the drawing into the clipboard,
overwriting the previous contents of the clipboard.
Also see:
Duplicating and Moving Selected Objects - xDX Designer
bcut Removes the selected objects or areas from the window into the buffer,
overwriting the previous buffer contents.
Also see:
boff Turns the border for the active window off.

bon Turns the border for the active window on.
box Adds a box to the schematic or symbol drawing. The box is dynamically
created when you drag the mouse.
Also see:
bpaste Copies the contents of the buffer to an indicated location in the active
window.
Also see:
bsize Changes the schematic or symbol sheet size of the active window to b. When
you execute this command, the sheet size automatically changes to b.
(Executing this command does not change the project settings for sheet size.)
bus Adds a bus in the active schematic window.
A bus is a collection of nets that can operate as a group or as individual nets
within the bus. A bus is created between components, from a single
component, or between nets.
Also see: Connectivity With Buses

Table 4-9. C - Command Line Commands

Command Description
C
cattribute Displays the Properties window (if not already open) for the selected schematic,
component, net, symbol or pin.
cb Lets you change the border on the open schematic. When you execute the
command, a Change Border dialog box appears. Fill in or browse to the path to
the border you want to use.
ccomp Changes the symbol that the selected component represents.
Syntax: ccomp new_component_name
If you do not enter new_component_name, the Change Component dialog box
appears to prompt you to enter the component name and whether you want to
preserve REFDES. Preserve REFDES defaults to no.
chgattr The Change Attribute dialog box appears so you can change only the selected
property.
chglabel The Change Label dialog box appears so you can change only the selected label
(name).
chgtext The Change Text dialog box appears so you can change only the selected text.
cinst Updates the pin numbers of all selected components. This command does not
updated the REFDES attribute information.
circle Adds a circle to the active schematic or symbol window.
Also see:
color Changes the color or selected objects in the active window to the color you
specify.
Example: color blue
If you enter only the command color, the Change Color dialog box appears to
prompt you to enter the color.
component Adds a component to the schematic drawing.
If you dont specify the component name, the Add Component dialog box
appears so you can enter the component name.
copy Copies the selected object or group of objects.
Also see:
bpaste

Table 4-9. C - Command Line Commands (cont.)

Command Description
csize Changes the schematic or symbol sheet size of the active window to c When
you execute this command, the sheet size automatically changes to c (Executing
this command does not change the project settings for sheet size.)
ctoff Toggles the display of all text, labels, and properties associated with all
component symbols to off. Text, labels, or properties you add on the component
level are unaffected.
cton Toggles the display of all text, labels, and properties associated with all
component symbols to on. Text, labels, or properties you add on the component
level are unaffected.
cuapply Update components to match symbols, mark as compliant, and clear optional
highlight. When you execute the command, the Apply Symbol Updates to
Components dialog box appears. Select whether to apply the command to All or
Selected, then select the desired slot.
cucheck Check components for compliance with their symbols. When compliant, the
component on the design matches the symbol in the library. Highlight & select
all out-of-date components.
cycle Automatically changes a specialized pin to the next component of the same type
of a user-configured list.
PADS DX Designer
Table 4-10. D - Command Line Commands

Command Description
D
db Delete border.
dbevoff Turns the database validation of read verbosity of the SCH/SYM parser off.
Off - tallies the number of messages when done reading the design.
On - generates all error/warning messages.
dbevon Turns the database validation of read verbosity of the SCH/SYM parser on.
On - generates all error/warning messages.
Off - tallies the number of messages when done reading the design.
defshoff Toggles off default border functionality. New schematics will not have a
default border applied to them.
defshon Toggles on default border functionality. New schematics will have a default
border applied to them.

Table 4-10. D - Command Line Commands (cont.)

Command Description
defsh1off Toggles off use of different border for underlying schematics. They will have
the same border as sheets 2 N.
defsh1on Toggles on use of different border for underlying schematics. They will use
the sheet 1 border.
defshcfg Use borders from user-configurable file and location.
defshfix Use borders from fixed file and location.
delete Deletes the selected objects in the active document. The delete command can
be reversed using the undo command.
If you delete a component, net segment, or bus segment from a schematic, all
connections become dangling connections.
If the object you delete has dangling connections, by default these wires
(including attached labels and properties) are also deleted. If you want to
preserve net labels and properties from deletion in this case, use CTRL+ Del.
directory Lists all the schematics and the symbols used on the schematics (in memory)
and identifies from which library the schematics and symbols were accessed.
dirsym Lists all the symbol files in project directories as specified in the name.prj
file.
Enter the dirsym command in the command line field and execute the
command.
Restriction: dirsym truncates file names to the first 16 characters.
doff Toggles the display of objects during object manipulation operations to off.
The default value for detail is the current value set in your DxDesigner.xml
file.
When you use this command, a bounding box is displayed to represent the
object until the operation is complete. If you use the don command, the
objects are continually displayed while you are performing object operations,
such as: adding, pasting, moving, copying, or rotating.
don Toggles the display of objects during object manipulation operations to on.
The default value for detail is the current value set in your DxDesigner.xml
file.
When you use this command, the objects are continually displayed while you
are performing object operations, such as: adding, pasting, moving, copying,
or rotating. If you use the doff command, a bounding box is displayed to
represent the object until the operation is complete.
Tip: Using this command slows down object movement. If you find the speed
of object operations slow, change this option setting. Click the right mouse
button or the spacebar while dragging an object to toggle detail settings on the
fly.

Table 4-10. D - Command Line Commands (cont.)

Command Description
dsize Changes the schematic or symbol sheet size of the active window to d. When
you execute this command, the sheet size automatically changes to d.
Table 4-11. E - Command Line Command

Command Description
E
egoff Exclude globals fm unique labels off.
egon Exclude globals fm unique labels on.
esize Changes the schematic or symbol sheet size of the active window to e. When
you execute this command, the sheet size automatically changes to e.
execute Execute a command ID.
commandid
exit Exit the design entry tool session
Table 4-12. F - Command Line Commands

Command Description
F
fcloseall Saves all open symbol and schematic windows.
If a file has been modified, a dialog opens asking if you want to save it.
form Run a form.
full Shows the full view of the schematic or symbol displayed in the active
window.
Table 4-13. G - Command Line Commands

Command Description
G
gmove Fast move.
goff Turns off the grid display for the current schematic or symbol window. The
grid will not display if the spacing number specifies too many dots to be
drawn.
Also see: Display Grid

Table 4-13. G - Command Line Commands (cont.)

Command Description
gon Turns on the grid display for the current schematic or symbol window.
grid Toggles the grid display on and off.
ground Add ground pin to schematic
gspace Changes the grid display space increment for the current schematic or symbol
window. Grid increments are 0.01 inch.
Table 4-14. I - Command Line Commands

Command Description
I
ib Insert a border on the open schematic. When you execute the command, the
default border for the sheet size and orientation (portrait or landscape) of the
schematic is inserted.
in Zooms in on the design.
io Select pins that exist on a symbol corresponding to the open schematic for
which you want to instantiate hierarchical I/O pins
Table 4-15. L - Command Line Commands

Command Description
L
label Adds a label to the selected object. Using the label command, you can add a
label and specify the name, expand, visibility, scope, and sense values for the
label.
PADS DX Designer
line Adds a line between two points or a series of line segments in the schematic
or symbol window.
Also see:

Table 4-15. L - Command Line Commands (cont.)

Command Description
linvis Makes the display of the specified labels invisible in the active schematic or
symbol window.
If you do not select a label before or during the execution of the command,
the Make Label Invisible dialog box appears to let you specify the label. You
can use wildcard characters to specify a group of labels.
PADS DX Designer
loff Turns off the display of the labels associated with nets, components, and pins
for the active schematic or symbol window.
logmemory Log memory.
lon Turns on the display of the labels associated with nets, components, and pins
for the active schematic or symbol window.
longstrings Searches the schematic sheet and reports labels, properties, text, or OATs that
are longer than 127 characters.
lsense Changes a label to signify a logical inversion by drawing an inverted bar over
the label in the active schematic or symbol window. If a selected label already
has the overbar, this command removes the overbar from the label.
PADS DX Designer
lvis Makes the display of the specified labels visible in the active schematic or
symbol window.
If you do not select a label before or during the execution of the command,
the Make Label Visible dialog box appears to let you specify the label. You
can use wildcard characters to specify a group of labels.
PADS DX Designer
Table 4-16. M - Command Line Command

Command Description
M
move Attaches selected objects to the cursor for movement. Also allows use of the
arrow keys for fine placement.
To complete the move after executing the command, click the left mouse
button.
Table 4-17. N - Command Line Commands

Command Description
N

Table 4-17. N - Command Line Commands (cont.)

Command Description
name Changes the name of the selected attribute.
Example: name NEW_ATT_NAME
If you do not enter NEW_ATT_NAME, the Change Attribute Name dialog box
appears for you to enter the new attribute name in.
PADS DX Designer
narray Automatically completes adding nets to a bus when any one net has been
placed and labeled. Execute this command after you have selected the net.
Syntax:
narray direction
Where direction is one of the following:
righttoleft
lefttoright
toptobottom
bottomtotop
naspace Auto net array space.
net Adds a net that connects two component pins and/or nets in the schematic
window. You also use this command to connect or continue a dangling net.
Also see:
Connecting Components with Nets - xDX Designer
noff Turns off the display of the internal names associated with objects in all
schematic or symbol windows. If a net or component is labeled, the internal
name is not displayed.
non Turns on the display of the internal names associated with objects in all
schematic or symbol windows. If a net or component is labeled, the internal
name is not displayed.
nsym New local symbol.
Also see: Creating and Editing Local Symbols
Table 4-18. O - Command Line Commands

Command Description
O

Table 4-18. O - Command Line Commands (cont.)

Command Description
o1 through o9 Sets the default origin point for all new text, labels, and properties that you
create. The origin number represents the positions shown:
1-------------------4--------------------7
| | |
| | |
2-------------------5--------------------8
| | |
| | |
3-------------------6--------------------9
odetail Lists a detailed description of each object or selected objects for the active
schematic or symbol. If you do not select any objects, the list contains all the
objects in the active window.
PADS DX Designer
offsheet Add offsheet connector.
onsheet Add onsheet connector.
oroute Changes the routing mode to full orthogonal routing. Executing this
command changes the routing mode specified in the DxDesigner.xml file to
orthogonal routing.
out Zooms out on the design.
Table 4-19. P - Command Line Commands

Command Description
P
pdbslot Applicable in integrated project types only:
A dialog appears to allow you to changes or update the slot of the selected
component or group of components to a specified slot of the package in the
Parts Database. The Slot pulldown list provides a list of available slots with
pin numbers.
placedetail Report on placeholders.

poff Turns off the display of pin numbers.
pon Turns on the display of pin numbers.

Table 4-19. P - Command Line Commands (cont.)

Command Description
pop Returns back through the stack of previously issued psch, psym and psheet
commands. The pop command will take a numerical argument specifying the
number of levels to pop. If no argument is specified, the value of 1 is
assumed. There is no need to select an object prior to issuing a pop command,
as it will use the stack to determine the results.
Special Condition:
When you open a sheet from a sheet node in the Navigator Tree, executing a
Pop command will always return you to sheet 1. This is true for all sheets,
including sheet 1.
Why:
Navigator opens the design root, and then pushes to the desired sheet
Workaround:
Open the schematic from the File > Open menu, or from a design root in the
Navigator Tree.
Also see:
Navigating With the Toolbar and Right-Click Menus - xDX Designer
power Add power connection.

psch Pushes through the hierarchy into a schematic block.
You must select the component before selecting the command to push down
to the corresponding schematic.
Also see:
psheet Pushes through sheets of a schematic or symbol set in sequential order, or

pushes to a specified sheet.
To push through the sheets in sequential order, enter the psheet command
in the command line field and execute the command.
To push to a specified sheet, enter the psheet command with the sheet number
in the command line field and execute the command. For example, psheet 12.
Also see:
psym Pushes through the hierarchy into a symbol block.

You must select the component before selecting the command to push down
to the corresponding symbol.

Table 4-20. Q - Command Line Commands

Command Description
Q
quit Quit PADS DX Designer.
Table 4-21. R - Command Line Commands

Command Description
R
read Refreshes memory with the active block. This affects only the open schematic
or symbol.
reflect Reflects the selected object(s) as a mirror image across a designated
horizontal or vertical line. You use the mouse to designate the line you want
the object reflected around.
The reflection line is snapped to the nearest orthogonal line and objects are
reflected about the line 180 degrees.
Also see:
refresh Updates the data in the active window. Use this command if the visual display
of the data has been disrupted.
RenameNet Rename net.
roff Turns off the display of reference designators.
ron Turns on the display of reference designators.
rotate Rotates the selected object(s) to the left in 90-degree increments.
Also see:
run Runs a script from the command line. Enter the run command followed by the
name of the script.
Table 4-22. S - Command Line Commands

Command Description
S

Table 4-22. S - Command Line Commands (cont.)

Command Description
scale Scales the size of a selected object or group of objects up or down by the scale
factor you specify in the Scale dialog box.
Toolbar:
Menu: Format > Scale
Also see:
Resizing Sheet Objects - xDX Designer
schematic Opens a new or existing schematic window for the creation and editing of
schematics and symbols.
PADS DX Designer
scomp Selects the component by a specified symbol name.
PADS DX Designer
sdistance Selects the distance, in screen pixels, surrounding an object that the cursor
must be placed within to select an object in a schematic or symbol window.
setenv Set environment variable.
sicdb Select ICDB index.
seticdbstore Set ICDB store retries.
retries
size Changes text, properties, or labels to a specified size in the schematic or
symbol window.
PADS DX Designer
slabel Selects the specified labels in a schematic or symbol window.
PADS DX Designer
slot Applicable in Netlist project type only:
Changes or updates the slot of the selected component or group of
components to a specified slot of the package.
sname Selects objects (such as components, nets, pins, and buses) in a schematic or
symbol window by specifying either the Internal name(s) or label(s).
PADS DX Designer


Command Description
snap Snaps objects in the open schematic to the grid you have enabled and defined
in the Setup > Settings (dialog) > Grid (section) (see Settings Dialog Box -
Strokes, Pan and Zoom on page 322.)
The Snap command takes one parameter, which you specify as all or
selected, to indicate the scope of the command. For this command to be
active, grid must be selected, and a grid spacing must be defined.
Example:
snap selected
snaps selected objects to the grid you have defined.

soff Turns off the Snap to Pin option.
son Turns on the Snap to Pin option.
sroute Changes the routing mode to straight routing.
stext Selects the specified text string in a schematic or symbol window.
You can use wildcard characters when specifying the text string.
PADS DX Designer
stretch Stretches the selected object in any direction. Stretchable objects are: Lines,
Boxes, Circles, Arcs, and Pins.
Also see:
Resizing Schematic Objects - xDX Designer
string Changes the name of selected string. This command will change the name of
any selected label, attribute, name, or text string.
PADS DX Designer
stub Add net stubs and optional labels to selected components.
Syntax:
stub Parameter
Where:
Parameter = No - if you do not want to label the stubs.
Parameter = Label - if you want to add labels to the stubs. These labels
take the names of the associated symbol pins.
svalue Selects the objects associated with the specified attribute value(s), as well as
the associated objects (such as, components, nets, pins, or buses) in a
schematic or symbol window.
PADS DX Designer


Command Description
system Open a system window.
Table 4-23. T - Command Line Commands

Command Description
T
text Adds text in the active schematic or symbol window.
Annotations can be inserted anywhere in a symbol or schematic drawing.
Text within a schematic or symbol drawing has no association with the
graphical or connectivity data.
Also see:
toff Turns off the visibility of text in a schematic. The default for this setting is on.
ton Turns on the visibility of text in a schematic. The default for this setting is on.
Table 4-24. U - Command Line Commands

Command Description
U
ubat Update the default values for properties assigned to the border for the open
schematic.
undo Reverses changes you make in a symbol or schematic drawing, such as
stretching or moving an object.
uoff Turns off the creation of unique labels from internal names when
components, nets, buses, or pins are copied, arrayed, or pasted from the
buffer.
uon Turns on the creation of unique labels from internal names when components,
nets, buses, or pins are copied, arrayed, or pasted from the buffer.
Table 4-25. V - Command Line Commands

Command Description
V
value Changes the value portion of the selected attribute(s) to the specified value.
PADS DX Designer
voff Turns off the display of simulation values.

Table 4-25. V - Command Line Commands (cont.)

Command Description
von Turns on the display of simulation values.
Table 4-26. W - Command Line Commands

Command Description
W
wclose Closes the active symbol or schematic drawing. If you made changes to the
document since it was last saved, you are asked if you want to save the
changes. If you close a document without saving, you lose all unsaved
changes.
If you have several windows open on the same document, this command
closes all windows viewing the same document. To close one of several
windows viewing the same document, use the Close command on the
Document Control menu.
wtext Open text file.
Table 4-27. Z - Command Line Commands

Command Description
Z
zoom Zoomed in on a specified area of the window.
Also see:Panning and Zooming Default-Style
zselect Zooms in on the selected area of the window.
Tip: If you want to zoom in more tightly than the default, you set the
VL_FULL_ZOOM environment variable, using the syntax
VL_FuLL_ZOOM=1. If you do not set this environment variable, you will
zoom in at a medium distance from the selected area.
Also see:Panning and Zooming Default-Style
zsize Changes the schematic or symbol sheet size of the active window to a custom
size. When you execute this command, you specify the custom sheet size.
(Executing this command does not change the project settings for sheet size.
Rule: Execute the zsize command in one of the following ways:
Press the Tab key immediately after entering each of the Width and Height
values and then press Enter.
When you have entered the values, do not press Enter. Instead, click OK.
Use the following syntax in the Command Line box:
zsize width height

Chapter 5
Property Characteristics
You use properties to create symbol definitions for interpretation when wirelisting, verification,
or passing to layout.
You can add properties to:
Symbols (unattached) Component pins
Symbol pins Net Segments
Schematics (unattached) Bus segments
Components
Note
You cannot place custom properties on boxes, lines, arcs or circles.
The following topics describe the characteristics of properties:
For information on specific properties, refer to the Properties Glossary.
Visibility Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423

Property Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
Property Name and Value Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
Netlist Interpretation of Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
User-Defined Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
Multiple and Duplicate Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
Multiple Property Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
Property Ranges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
Visibility Options
Visibility options for properties are controlled by check boxes in the Properties window.
You can make properties visible or invisible at the symbol and/or schematic level. If you are in
a symbol window and properties are visible, they are also visible on the schematic window. If
you specify properties visible on the symbol, you cannot make them invisible on the schematic.
Having the properties set as visible while you are placing them on the symbol is helpful.
However, as a general rule you should change the display of the property to invisible after you
have placed them on the schematic so they do not clutter the schematic drawing.

Property Format
Note
Making a property invisible does not delete the property. It only helps to reduce the clutter
from the schematic display.
If you want the Ref Designator (REFDES) property to be invisible on the schematic, deselect
the Ref Designator check box (one for the property name and one for the property value) in the
Properties window.
Related Topics
Property Format
The format for properties is: NAME = VALUE You must specify the property name exactly as
you want the netlist to interpret it. For example, to associate reference designator information
with a symbol, add an property, such as REFDES=U?. REFDES is the property name and U? is
the property value.
There are several ways to define an property value:
Explicit value - the value is constant (exactly as you enter it)

Multiple value - the value represents multiple properties
Variable value - the value changes
Expression value - the value is dependent on characteristics of the design
Related Topics
Property Name and Value Restrictions

Do not create property names beginning with $ or *, since the design entry tool reserves names
beginning with $, and since * is the wildcard character. Also avoid using % and ? in property
values.
Do not use mathematical characters such as /, *, -, or +, in property values (except when
specifying variable definitions for parameterized properties). You must enter the property
NAME in upper case. Under certain conditions, you can enter the property value in upper, lower
or mixed case. However, you must remember that third party tools which use the
PADS DX Designer netlists do not all support mixed case property values. These tools may
require upper case values. Check with your tool provider to confirm whether you can use mixed
case with the tool.

Netlist Interpretation of Properties
Related Topics
Netlist Interpretation of Properties

The design entry tool has a flexible scheme that allows an unrestricted number of properties.
Netlisting interprets almost all properties, with each layout tool looking for a particular set of
properties.
Either flattened or hierarchical, netlists interpret explicit and multiple property values. Only
flattened netlists interpret variable and expression property values.
Related Topics
User-Defined Properties
You can create any property to define unique information about your design such as optional
labels or part numbers used in the design.
The PADS DX Designer tool cannot interpret user-defined properties. The netlist process lists
the properties in the netlist file if you add them before the netlist is executed. You can interpret
user-defined properties for application specific functions using scripting or the
PADS DX Designer utilities.
Related Topics
Multiple and Duplicate Properties

Most objects can have multiple properties (properties with different names) associated with
them. Duplicate properties on a single object, properties with the same name, usually have
different values.
The design entry tool allows the following objects to have multiple properties (properties with
the different names) on a single object. Duplicate properties (properties with identical names)
on a single object usually have different values.

Multiple Property Values
The design entry tool allows duplicate properties as outlined below:

Table 5-1. Legal Duplicate Properties
Object Duplicate
Symbol Unrestricted duplicates (if you name symbols, every named symbol must
have a unique name)
Schematics No duplicates
Components No duplicates (except SIGNAL, PROBE, EQUATE, and PINSWAP
properties)*
Pins No duplicates
Net/bus segments No duplicates (except PROBE property)*
* Duplicate properties must be enabled in the configuration file if you wish to run the PCB
Integration program. Refer to the PCB Integration Help for more information.
Most symbol properties are not accessible from the component level. You can add identical
properties to the component and change the property value on the component to override the
property value on the symbol. See Multiple Property Values on page 426.
Related Topics
Multiple Property Values

The format for multiple property values is: name = value,value,value
Separate multiple property values with commas or colons. For example, #=[a,b,c,d] or
TPHL=10:17:25.
Related Topics
Multiple and Duplicate Properties
Property Ranges
A property value can express a numerical range for a bus or a pin by specifying beginning,
ending, and incremental integer values. The design entry tool expands an property value with a
range to create a series of properties.
The format for property value ranges is:
NAME[F:L:I]

Property Ranges
where F is the first number, L is the last number, and I is the interval between the numbers in the
range. If no interval is specified, the interval is 1.
Separate the numbers with colons. You must enclose the range in brackets, and you can only
express the range in numeric characteristics.
Given the values shown in the following table:

Table 5-2. Property Ranges Example
This Range... Becomes Properties...
#=[1:4] #=1, #=2, #=3, and #=4
#=[1:20:2] #=1, #=3, #=5, #=7, #=9, #=11, #=13, #=15, #=17, #=19
#=A[1:3],#=B[1:3],#=C[1:3] #=A1, #=A2, #=A3, #=B1, #=B2, #=B3,
#=C1, #=C2, and #=C3
In PCB design, multiple values of the property #=1,4,8,12, when attached to a symbol pin and
used in conjunction with a PARTS=4 property, indicate that this pin represents:
pin 1 of the first part of the package

pin 4 of the second part of the package
pin 8 of the third part of the package
pin 12 of the fourth part of the package
Related Topics

Property Ranges

Chapter 6
Names
A name is a string of characters you apply to sheet objects.

You can apply the same name to more than one net. Using the same name for more than one net
establishes connectivity between those nets.
You can apply the same name to more than one bus.
You must name all pins on a block and you must name the ports of the underlying schematic to
correspond to the pins. The design entry tool uses these name matches to maintain connectivity
between a symbol and the underlying schematic.
You do not have to name symbols, but if you do, the name for each symbol must be unique to
avoid packager errors. You should not name module symbols, although naming composite
symbols (blocks) can make the design easier to read. You will receive packager errors if more
than one symbol has the same name. For more information on local symbols and their types,
refer to Creating and Editing Local Symbols - xDX Designer.
The following topics describe name characteristics:
Illegal Characters in Name Identifiers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429

Unnamed Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
Name Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
Compound Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
Unique Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
Pin Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Bus Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Illegal Characters in Name Identifiers

This topic identifies illegal characters in block names and net names.
Block Names
For blocks appearing in the Navigator, it is recommended that you only use name strings that
include numerals (0-9), lowercase letters (a-z), uppercase letters (A-Z) and underscore (_).

Names
Unnamed Objects
Illegal characters in a block name include the following:
* , @ # $ % ^ & < > ' ( ) = ? . <space>
Net Names
Name strings used for net names can consist of any characters (including spaces).
Illegal characters in a net name include the following:
@ $ ' \ " ; \\ < > { } *
Related Topics
Names
Unnamed Objects
Unnamed Objects are nets, buses, or symbols to which you have not applied a name. Whether or
not you name them, the design entry tool automatically assigns a unique internal ID to each
object. All internal IDs begin with $ (for example, $1N12). If you name an object and set the
name to visible, the design entry tool displays the name.
If you copy a net, bus, or symbol, the name you applied to the original is also assigned to the
copy, but the design entry tool automatically changes the internal ID to keep it unique.
Pin names are defined by the Central Library symbol and you cannot change them in the design
entry tool.
Related Topics
Names
Name Ranges
Names can express a numerical range for a bus or a pin by specifying beginning, ending, and
incremental integer values. The design entry tool expands names with a range to create a series
of names.
The format for name ranges is:
NAME[F:L:I]
where F is the first number, L is the last number, and I is the interval between the
numbers in the range. If no interval is specified, the interval is 1.

Names
Compound Names
The following shows legal range formats:
out.[1:5] - creates out.1, out.2, out.3, out.4, and out.5

a[10:3:2] - creates a10, a8, a6, a4
a[1:2]b[2:1] - creates a1b2, a1b1, a2b2, a2b1
A radix qualifier may follow the range specification to indicate a binary, hexadecimal, or octal
specification. Separate the qualifier from the range specification with a slash.
The name identifier A[8:C/H] is equivalent to A8, A9, AA, AB, and AC.
You can specify a bus range only with numeric characters. For example, data[b7:b0] is not a
valid format. If the bus range you want to label is decimal (for example, 7:0), use the format
data[7:0].
Related Topics
Names
Compound Names
Use compound names or bundles to label busses or pins that are not expressible as a single
range. You form a compound name with several name identifiers (with or without ranges). You
separate the names using commas. The system expands compound name identifiers separately
from left to right.
To enter a compound name, use the following format:
NAME[F:L:I], NAME,NAME[F:L],...
where F is the first number, L is the last number, and I is the interval between the
numbers in the range. If no interval is specified, the interval is 1.
o A[0:3],B,D[1:4] - is equivalent to A0,A1,A2,A3,B,D1,D2,D3,D4
o A[2:1],B[3:0],C - is equivalent to A2,A1,B3,B2,B1,B0,C
Related Topics
Names
Unique Names
The design entry tool creates different types of names when components, nets, busses, or pins
are copied, arrayed, or pasted from the buffer.

Names
Pin Names
Related Topics
Names
Pin Names
You specify pin names and ranges (width) with name identifiers. Pin names establish and
maintain connectivity between components. The pin range of a multi-bit pin must be identical to
the range of a connecting bus.
The exception to this is when the component has the $ARRAY property. All pins on a symbol
must have a label for identification during any netlisting process. For symbols that do not
normally have labels, such as resistors and capacitors, make the labels invisible.
Related Topics
Names
Bus Names
Bus names specify the nets contained in the bus. The names of the nets connected to the bus can
either correspond to the bus name or the nets can be aliased to different names.
Note
The Setup > Settings, Project (category), Net Name Delimiter (subcategory) allows you to
control how net names are resolved into elements of buses. See Settings Dialog Box - Net
Name Delimiter on page 308.
Related Topics
Naming Connectivity Objects Such as Nets and Buses - xSD Systems Designer
Names

Chapter 7
Key Bindings and Strokes
The following topics describe the predefined keybindings that are available in the
PADS DX Designer design entry tool:
Refer to the Key Binding definition description for your design capture tool session setup to see
how the strokes are mapped to specific commands. Also see the following:
Executing Commands Using Key Bindings and Strokes - xDX Designer

Key Bindings - Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Key Bindings - xPCB Layout Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
Key Bindings - PADS Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
Key Bindings - Default

Default PADS DX Designer design entry tool default key bindings are stored in various .vbs
files.
Table 7-1 on page 433 shows the default PADS DX Designerdesign entry tool key bindings that
are loaded from \<mgc_home>\<release>\SDD_HOME\standard\vdbindings.vbs. These
bindings are in effect if you set the following: Setup > Settings, Schematic Editor (category),
Strokes, Pan and Zoom (category), Default Pan and Zoom.
(Equivalent DxDesigner.xml entry: <key name="KEYBINDINGS" value="0"/>)
Table 7-2 on page 436 shows the default PADS DX Designer ICT Viewer key bindings stored
in the vdbindings.vbs file.
Table 7-3 on page 436 shows the default PADS DX Designerdesign entry tool Stroke
definitions stored in the vdbindings.vbs file.
Table 7-1. List of vdbindings.vbs Key Bindings
Action Key Binding Action Key Binding
Working with files
New Project CTRL+N Save File CTRL+S
Open Block CTRL+O Close File CTRL+F4
Print File CTRL+P Close design entry tool ALT+F4

Table 7-1. List of vdbindings.vbs Key Bindings (cont.)

Opening dialogs and menus
Add menu ALT+A Setup menu ALT+S
Edit menu ALT+E Settings dialog CTRL+ALT+G
File menu ALT+F Tools menu ALT+T
Find and Replace Text CTRL+H View menu ALT+V
dialog
Format menu ALT+O Window menu ALT+W
Help menu ALT+H
Opening windows
Open DataBook window CTRL+ALT+D Open Properties ALT+Enter
window
Open Xpedition Cell CTRL+ALT+K Open Command Line Space
Preview window window
Adding objects to schematics
Add arc A Add line L
Add block f Add off page pin CTRL+Alt+Space
Add box B Add on page pin CTRL+Alt+Shift+
Space
Add bus b Add net n
Add circle C Add power pin Shift+Space
Add ground pin CTRL+Space Add text T
Add Hierarchical I/O Pin CTRL+Shift+
Space
Editing
Copy CTRL+C or Move now CTRL+E or m
CTRL+Insert
Cut CTRL+X or Paste CTRL+V or
Shift+Delete Shift+Insert
Delete Delete or d or Reattach net CTRL+R
Backspace
Flip Vertical CTRL+Shift+F Redo CTRL+A or
CTRL+Backspace or r

Table 7-1. List of vdbindings.vbs Key Bindings (cont.)

Flip Horizontal (Mirror) CTRL+F Rotate 90 degrees CTRL+Shift+R
Undo Alt+Backspace or
CTRL+Z or u
Selecting objects
Select mode s or ESC
Navigating in the design - Schematic window
Move to next schematic Page Down or Push into schematic h
sheet in sequence Page Up
Cycle between open CTRL+Tab Push into symbol with y
Schematic window tabs Symbol Editor
Cycles a specialized pin CTRL+Y
to the next component of
the same type of a user-
configured list
Viewing the design
Pan (to cursor) F6 or Insert Zoom area CTRL+W or F9 or z
Zoom in F7 Zoom full Home or F4
Refresh F5 or CTRL+D Zoom out F8
or END
Restore Zoom Shift+F10 Zoom on selected Z
Save Zoom Shift+F9
Getting help (For current help, use Help > Documentation in InfoHub instead of the
following)
Launch DxDesigner help CTRL+F1 Next Help Shift+F5
Help on features F1 Next error message Shift+F4
Help on, context Shift+F1
Miscellaneous
Left mouse button CTRL+Shift+F2 Scroll around Arrow buttons (up,
or CTRL+F2 or schematic down, left, right)
F2
Middle mouse button F3

Table 7-2. List of PADS DX Designer ICT Viewer vdbindings.vbs Key Bindings

Adding objects
Add net CTRL+I Add block CTRL+G
Editing
Delete Delete Expand pins CTRL+Page Down
Edit start Insert or F2 Redo CTRL+Y
Collapse pins CTRL+Page Up Undo CTRL+Z
Selecting objects
Select all CTRL+A
Table 7-3. List of vdbindings.vbs Stroke Definitions

Command Graphic Numerical Sequence
Add Line 852
Delete Selected 74123698

or
741236987
Help (Use Help > 123658

Documentation in InfoHub for or
up-to-date information.)
12368
Last Command Recall 12369
Flip Horizontal (Mirror) 9632147
Refresh 74123
Rotate 90 3698741
Undo 7412369

Key Bindings - xPCB Layout Style
Table 7-3. List of vdbindings.vbs Stroke Definitions (cont.)

View Full 951
Zoom In 357
Zoom Out 753
Related Topics
Key Bindings - PADS Style

The xPCB Layout key bindings described in this section are stored and loaded from
\<mgc_home>\<release>\SDD_HOME\standard\exped_wvo.vbs on Windows and /
<mgc_home>/<release>/SDD_HOME/standard/exped_pv.vbs on Linux. These bindings are in
effect if you select the following: Setup > Settings, Schematic Editor (category), Strokes, Pan
and Zoom (subcategory), Xpedition Pan and Zoom.
The bindings are described in the following tables:
exped_wvo.vbs (Windows) file:
Table 7-4 on page 437 - Key bindings

Table 7-5 on page 440 - PADS DX Designer ICT Viewer key bindings
Table 7-6 on page 440 - Stroke definitions
exped_pv.vbs (Linux) file:
Table 7-7 on page 441 - Key bindings

Table 7-8 on page 443 - PADS DX Designer ICT Viewer key bindings
Table 7-9 on page 443 - Stroke definitions
Table 7-4. List of Windows exped_wvo.vbs Key Bindings
Working with files

Table 7-4. List of Windows exped_wvo.vbs Key Bindings (cont.)

New Project CTRL+N Save File CTRL+S
File menu ALT+F Tools menu ALT+T
Find and Replace Text CTRL+F or View menu ALT+V
dialog CTRL+H
Help menu ALT+H
Opening windows
window
Add arc A Add line L
Add block f Add off page pin CTRL+Alt+Space
Add box B Add on page pin CTRL+Alt+Shift+
Space
Add bus b Add net n
Add circle C Add power pin Shift+Space
Add ground pin CTRL+Space Add text T
Add Hierarchical I/O Pin CTRL+Shift+
Space
Editing
CTRL+Insert

Table 7-4. List of Windows exped_wvo.vbs Key Bindings (cont.)

Delete CTRL+Delete Reattach net CTRL+R
or Delete or d
or Backspace
Edit String S Redo F7 or
CTRL+Backspace or r
Flip Vertical F5 Rotate 90 degrees CTRL+Shift+R or F3
Flip Horizontal (Mirror) F4 Undo Alt+Backspace or
CTRL+Z or F6 or u
Selecting objects
Select mode s or ESC Select all CTRL+A
configured list
Viewing the design
Pan (to cursor) Insert Zoom full Home
Restore Zoom Shift+F10 Zoom out F8
Save Zoom Shift+F9 Zoom on selected Z
Zoom area CTRL+W or F9
or z
Getting help (For current information, use Help > Documentation in InfoHub instead of the
following)
Miscellaneous
F2

Table 7-5. List of Windows PADS DX Designer ICT Viewer exped_wvo.vbs Key
Definitions
Adding objects
Editing
Selecting objects
Select all CTRL+A
Table 7-6. List of Windows exped_wvo.vbs Stroke Definitions

Command Graphic Numerical
Sequence
Add Line 852

or
741236987
Help (For up-to-date information, use 123658

Help > Documentation in InfoHub or
instead)
12368
Refresh 74123
Rotate 90 3698741

Table 7-6. List of Windows exped_wvo.vbs Stroke Definitions (cont.)

Command Graphic Numerical
Sequence
Undo 7412369
View Full 951
Zoom In 357
Zoom Out 753
Table 7-7. List of Linux exped_pv.vbs Key Bindings

Working with files
New Project CTRL+N Save File CTRL+S or
Find and Replace Text CTRL+F or Tools menu ALT+T
dialog CTRL+H
File menu ALT+F View menu ALT+V
Help menu ALT+H
Opening windows
window
Add arc A Add label l
Add block F Add line L

Table 7-7. List of Linux exped_pv.vbs Key Bindings (cont.)

Add box B Add off page pin CTRL+Alt+Space
Add bus b Add on page pin CTRL+Alt+Shift+
Space
Add circle C Add net n
Add ground pin CTRL+Space Add power pin Shift+Space
Add Hierarchical I/O Pin CTRL+Shift+ Add text t
Space
Editing
CTRL+Insert or
c (copy now)
Delete Delete or d or Reattach net CTRL+R
Backspace
Flip Vertical CTRL+Shift+F Redo CTRL+Backspace or
or F5 F7 or r
Flip Horizontal (Mirror) F4 Rotate 90 degrees CTRL+Shift+R or F3
Undo Alt+Backspace or
CTRL+Z or u or F6
Selecting objects
Select mode ESC Select All CTRL+A
configured list
Viewing the design
Pan (to cursor) Insert Zoom area CTRL+W
Zoom in (define area) z or F9 Zoom full Home or F10

Table 7-7. List of Linux exped_pv.vbs Key Bindings (cont.)

Refresh F5 or CTRL+D Zoom out F8
or END
Restore Zoom Shift+F10 Zoom on selected Z
Save Zoom Shift+F9
Getting help (For current help, use Help > Documentation in InfoHub instead of the
following)
Miscellaneous
F2
Middle mouse button CTRL+Shift+F3
or CTRL+F3
Table 7-8. List of Linux PADS DX Designer ICT Viewer exped_pv.vbs Key
Bindings
Adding objects
Editing
Selecting objects
Select all CTRL+A
Table 7-9. List of Linux exped_pv.vbs Stroke Definitions

Add Line 852

Table 7-9. List of Linux exped_pv.vbs Stroke Definitions (cont.)

or
741236987
Help (Use Help > 123658

Documentation in InfoHub or
instead)
12368
Refresh 74123
Rotate 90 3698741
Undo 7412369
View Full 951
Zoom In 357
Zoom Out 753
Related Topics


The following table lists the PADS keybindings you enable with the Key Bindings property of
the PADS Design Configuration. These bindings are in effect if you select the following: Setup
> Settings, Schematic Editor (category), Strokes, Pan and Zoom (subcategory), PADS Pan and
Zoom.
Table 7-10. PADS Keybindings in PADS DX Designer

Key Binding Description
Ctrl+N File > New
Ctrl+S File > Save
Ctrl+Z Edit > Undo
Ctrl+Y Edit > Redo
Ctrl+X Edit > Cut
Ctrl+C Edit > Copy
Ctrl+V Edit > Paste
Ctrl+E Edit > Move
Del Edit > Delete
Ctrl+W View > Zoom
Home View > Board
Shift+Z View > Selected
Ctrl+D View > Redraw
End View > Refresh
F4 View > Full
F5 View > Refresh
F6 Pan (centers screen on
cursor)
F9 Zoom selected area
Related Topics


Chapter 8
Design Entry Tool Diagnostics Reference
The topics in this section provide reference information for some of the design entry tool
diagnostic tools.
Diagnostics Tool Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
DRC Rule Notes and Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
DRC Property and Label Syntax Using Regular Expression Syntax . . . . . . . . . . . . . . . 453
DRC Regular Expression Ambiguity Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
DRC Verify Tool Defaults File Search Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
Prerequisites for DRC Electrical Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
Diagnostics Tool Tests

You can run Tools > PADS DX Designer Diagnostics to check for basic errors in your design.
Table 8-1 on page 447 shows the tests that the Diagnostics Tool executes.
Table 8-1. Diagnostics Tool Tests
Checks for Description
Symbol types Verifies that symbols are either of type pin or type port, but not
both.
Message:
Invalid symbol definition type <name>.
Invalid nets Verifies that each sheet-level net is part of a logical net.
(Logical nets constitute the connectivity and the design entry
tool displays them in Navigator).
Messages:
Invalid unconnected net found
Invalid net found
Invalid buses Verifies that all buses in the project include graphical data.
Message:
Invalid bus found

Table 8-1. Diagnostics Tool Tests (cont.)

Sheet order data Verifies that custom sheet order values, if specified, are not
corrupt. Corrupt sheet order values could result in incorrect
xDX PDF output.
Message:
Inconsistent sheet ordering data for <name> schematic.
Sheet internal identifiers Validates internal properties that store sheet IDs.
Message:
Sheet <name> has a missing identifier which is needed to
generate object IDs.
Component graphical data Verifies that all components have graphical data. You can create
logical-only components that do not contain graphical data in
Constraint Manager or xPCB Layout, but these logical-only
components must not exist on the schematic.
Message:
Components <name> without graphical data found on
schematic <name> and need to be deleted.
Net connections Verifies that the project does not include nets connected to non-
existent pins.
Message:
Net <name> connected to a non-existent pin.
Rippers Verifies bus ripper data consistency.
For example, the signals listed on an internal property as being
connected with a bus may be inconsistent with actual signals
present in the bus.
Messages:
Ripper refers to non-existent bus, and should be deleted.
Ripper refers to a signal which is not a member of the bus, the
signal reference should be deleted from the ripper.
Reuse blocks Verifies that the reuse blocks instantiated in the design are
marked as read-only.
Message:
Missing read-only flag for block <name>.


Empty blocks Checks if there are any empty blocks present. If a block (such as
a schematic or an ICT) present in the Integrated Common
Database (iCDB) does not have any data, you cannot open the
block from the Navigator. You can safely delete the empty
blocks, because they do not impact connectivity in any way and
do not contain any data.
Message:
Empty invalid block <name> found and needs to be deleted.
Top level name consistency Verifies that the name of the top level block stored in the project
file uses the same case as the name in the database.
Message:
Block names differ: <name1> in database, <name2> in project
file.
Duplicate internal IDs Verifies that xDX Designersymbols pins have unique IDs.
Message:
Symbol <name> has pins with duplicate IDs needed for
Backup/Rollback.
Bus signal connections Verifies that no shorts exist due to incorrect naming of rippers.
Message:
Invalid connection of <net_name1> to <net_name2> on
schematic <sch_name>.
Component names Verifies that no component name contains the invalid '$'
character. The fix removes '$' characters from names.
Message:
Invalid Component Name(s) <name1>, <name2>, on
schematic <sch_name>.
Pass-through pins Verifies connectivity of component pass-through pins:
Pins correctly connect to one logic net.
Connections to the master pin (with flag ForwardPCB) do
not repeat.
Message:
Incorrect connection of pass-through pin to net on
schematic


Connectivity Verifies that schematic sheet graphical data is synchronized
with logical data. The fix recompiles schematic graphical data
to synchronize with the logical data.
Message:
Connectivity not up to date with schematic sheet.
Related Topics
Checking Data Integrity with the Diagnostics Tools, and Correcting Reported Errors

The following table provides supplemental Design Rule Checker (DRC) information for the
design entry tool.
Table 8-2. DRC Rule Notes and Examples

Rule Group Rule ID Rule Notes/Examples
Connectivity drc-107 Unconnected pin(s)
You configure drc-107 with the provided options to report
unconnected pins. The options include:
Two pin components You set drc-107 to either Include two
pin components, Exclude two pin components, or Only check
two pin components.
Input, Output, Bi-directional, Tri-state If Enabled, any
unconnected component pin of one of these types generates a
report.
Others If Enabled, any unconnected component pin not of
type Input, Output, Bi-directional, or Tri-state generates a
report.
All inputs If Enabled, components found with all inputs
disconnected generate a report.
All outputs If Enabled, components found with all outputs
All pins If Enabled, components found with all pins
Also see:

Table 8-2. DRC Rule Notes and Examples (cont.)

Connectivity drc-108 Hanging/Dangling net
This check applies to nets with a connection on only one end (net
stubs).
Also see:
Connectivity drc-121 Net Connectivity Consistency
Use a different symbol for each type of check. If you use the same
symbol for all checks, and then run all checks at one time, you may
see unexpected interactions and associated erroneous messages.
Connectivity drc-126 Bus/Bus Content versus wide pin width match
Examples:
Assume a Bus Content MYBUS=A,B,C[3:0],D, which contains a
total of seven signals.
A mismatch occurs if MYBUS connects to DD[2:0], which only
has three signals
A mismatch occurs if ADDR[4:0] (five signals) connects to
ADDRESS[5:0] (six signals)
Option: Bit to bit match
Examples:
If this option is enabled:
A mismatch occurs if ADD[4:0] <==> ADDRESS[5:1] Same
number of signals but shift in the bit numbers
A mismatch occurs if ADD[4:0] <==> ADDRESS[0:4] Same
number of signals but reverted range


Electrical drc-201 Open collector pin not pulled up
drc-202 Open emitter pin not pulled down
Checks that an Open Collector or Emitter pin is connected to either
power or ground through a pull-up or pull-down component
(resistor defined in VerifyDefaults.ini).
By default, these checks look for a resistor symbol name that
includes the string res based on the following definition in the
Defines section in the VerifyDefaults.ini file:
<Defines>
<Option Name="resistors" Value=*res*.*" />
</Defines>
In the resistors definition, the wildcard characters (*) preceding and

following "res", causes a match to occur for symbol names such as
res.1, vres.1, hres.1, resistor.1 or anything similar.
If your pull-up or pull-down resistor does not have the string res
in the symbol name, you need to add a similar definition line (as
shown in the previous example) in the Defines section of your local
Verify.ini file to include your symbol name.
drc-201 has an option to allow you to specify the Pull-up net(s),
such as: VCC VDD (one or more strings separated by a space).
drc-202 has an option to allow you to specify the Pull-down net(s),
such as: GND VSS VEE (one or more strings separated by a space).
Electrical drc-203 Component Polarity Check
This check applies to incorrectly named polarized nets connected to
a power supply.
Examples:


Electrical drc-204 Voltage Drop Tolerance Check
The nets connected to the pins carrying the DRC Positive and DRC
Negative properties must:
Be defined in the power_nets/ground_nets section of the
VerifyDefault.ini file that is in the standard folder of the
installation tree.
Use the following naming convention to identify positive or
negative voltage as well as a voltage reference (ground) of 0
volt:
The nets must start with a + or sign followed by numbers with
eventually appropriate units.
An error occurs when the calculated power is less than the Min
Value or greater than the Max value.
Note that the DRC Positive and DRC Negative properties can be
renamed provided the VerifyDefault.ini file defines them
accordingly.
Also see: Prerequisites for DRC Electrical Checks on page 460
Electrical drc-205 Power Tolerance Check
This check applies to resistors and requires that the resistor symbol
is polarized using the DRC Positive and DRC Negative common
properties.
The DRC calculates the voltage drop the same way as drc-203 and
drc-204. The DRC calculates power as (Voltage drop) X (Voltage
drop) / resistor_value. It means that the DRC expects the Value
property to have a value. The DRC compares the calculated power
to the Min/Max values you specify (for example, Min Value; Max
Value = 200mW/500mW).
The DRC reports an error when the calculated power is less than the
Min Value or greater than the Max value.
Also see: Prerequisites for DRC Electrical Checks on page 460
DRC Property and Label Syntax Using Regular

Expression Syntax
The property and label syntax use the following regular expression syntax for pattern matching:
A regular expression is zero or more branches, separated by |. If any one of the branches
contains a pattern match, the regular expression is a match.

A branch is zero or more pieces, concatenated. The DRC regular expression interpreter
searches for a match for the first piece of the branch, followed by a match for the second
piece, until the regular expression interpreter reaches the end of the branch.
A piece is an atom followed by one of the following quantifiers:
o * the interpreter looks for a sequence of 0 or more matches of the atom.
o + the interpreter looks for a sequence of 1 or more matches of the atom.
o ? the interpreter looks for a match of the atom, or the null string.
An atom is a regular expression in parentheses, which can contain any of the following:
o a range
o . (causes the interpreter to match any single character)
o ^ (causes the interpreter to match the null string at the beginning of the input string)
o $ (causes the interpreter to match the null string at the end of the input string)
o a \ followed by a single character (causes the interpreter to match that character)
o or a single character with no other significance (causes the interpreter to match that
character)
A range is a sequence of characters enclosed in brackets ([]). The interpreter normally
matches any single character from the sequence. If the sequence begins with ^, the
interpreter matches any single character not from the rest of the sequence. A hyphen (-)
separating two characters in the sequence is shorthand for the full list of ASCII
characters between them (for example, [0-9] matches any decimal digit). To include a
literal ] in the sequence, make it the first character (following a possible ^). To include a
literal - in the sequence, make it the first or last character.
Related Topics
DRC Regular Expression Ambiguity

Resolution
Regular expression ambiguity resolutions include:
If a regular expression matches two different parts of the input string, the DRC regular
expression interpreter matches the part that begins earliest. If both matching parts of the
input string begin in the same place, but match different lengths, or match the same
length in different ways, the following occurs:
o The interpreter evaluates the possibilities in a list of branches, in order, from left-to-
right.

o The interpreter evaluates the possibilities for *, +, and ? by looking at the longest
first.
o The interpreter considers nested constructs from the outermost in, and the interpreter
considers concatenated constructs from the leftmost-first.
o The interpreter chooses the match in the earliest part of the input string, in the first
chosen part.
o If there is more than one choice, the interpreter makes the next choice in the same
manner by looking at the earliest possibility, subject to the decision on the first
choice.
For example, (ab|a)b*c could match abc in one of two ways. The first choice is between ab and
a. Since ab is earlier, and does lead to a successful overall match, the interpreter chooses ab.
Since the b is already spoken for, the b* must match its last possibility-the empty string-since it
must respect the earlier choice.
In the particular case where no |'s are present and there is only one *, +, or ?, the result is that the
interpreter chooses the longest possible match. So ab*' presented with an input string xabbbby,
matches abbbb. Note that if ab* is tried against xabyabbbz, it matches ab just after x, due to the
begins-earliest rule. (In effect, the decision on where to start the match is the first choice made
by the interpreter, hence subsequent choices must respect the decision even if this leads the
interpreter to less-preferred alternatives.)
Related Topics

When you invoke the Design Rules Checker (DRC) Verify tool (Tools > Verify), the Verify
dialog box opens. The Verify tool uses one or more .ini configuration files found along the
search path to configure the Verify dialog box (both the Settings and Rules tab).
The Verify tool uses the settings from the first defaults file found along the search path, and
then overwrites duplicate settings with any differences found in subsequently found .ini files.
You can view which defaults file(s) the Verify tool uses on the Verify dialog box Settings pane.
These .ini files use XML formatting. If you or an administrator has the proper file permissions,
you can modify the \<mgc_home>\<release>\SDD_HOME\standard\VerifyDefaults.ini file to
reconfigure the initial Verify defaults for anyone invoking the tool from
\<mgc_home>\<release>\SDD_HOME\...
You can modify writable %WDIR%\<path>\VerifyDefaults.ini defaults file to affect multiple

Verify tool users in multiple projects.

The search order is a little different with an integrated project type that uses concurrent design
in comparison to a design that is not a concurrent design. In a concurrent design, it is not
desirable for each users local Verify settings to be saved to the same Verify.ini file located in
the concurrent design project directory. To prevent users from overwriting each others local
Verify settings, the tool saves each users Verify settings in a unique location in the first
writeable WDIR found along the search path, designated as the following:
\<1st_writeable_WDIR_path>\<release>\config\<unique_id>\Verify.ini
Verify Tool Search Order for a Netlist Project

The Verify tool checks the following netlist project type files in the order listed:
1. \<mgc_home>\<release>\SDD_HOME\standard\NetlistVerifyDefaults.ini
2. %WDIR%\<path1>;%WDIR%\<path2>;%WDIR%\<path3> (The Verify tool loads
and merges .ini file content and compares, key by key, whether a new value is found.
Then the tool overwrites the existing one.)
3. \<project_dir>\NetlistVerifyDefaults.ini (Netlist project)
4. \<project_dir>\NetlistVerify.ini (Netlist project - Locally saved settings)
Note: Only settings that differ from the VerifyDefaults.ini or NetlistVerifyDefaults.ini
settings appear in your local NetlistVerify.ini file.
Verify Tool Search Order for an Integrated Project (No Current Design)
For an Integrated project type that does not use the Remote Server Configuration Manager
(RSCM), the Verify tool checks the following files in the order listed:
1. \<mgc_home>\<release>\SDD_HOME\standard\VerifyDefaults.ini
2. %WDIR%\<path1>;%WDIR%\<path2>;%WDIR%\<path3> (The Verify tool uses the
first VerifyDefaults.ini file found in this path)
3. \<project_dir>\VerifyDefaults.ini
4. \<project_dir>\Verify.ini - Locally saved settings
Note
Only settings that differ from the VerifyDefaults.ini settings appear in your local
Verify.ini file.
Verify Tool Search Order for an Integrated Project (Concurrent Design)

The following list presents the files in the order that the Verify tool checks for them in an
integrated project that uses a Remote Server Configuration Manager (RSCM) for concurrent
design.

1. \<mgc_home>\<release>\SDD_HOME\standard\VerifyDefaults.ini (Integrated
project)
\<mgc_home>\<release>\SDD_HOME\standard\VerifyDefaultsSD.ini (xSD Systems
Designer project)
2. %WDIR%\<path1>;%WDIR%\<path2>;%WDIR%\<path3> (Integrated project
The Verify tool uses the first VerifyDefaults.ini file found in this path)
(xSD Systems Designer project The Verify tool uses the first VerifyDefaultsSD.ini
file found in this path)
3. \<first_writeableWDIR>\config\<unique_id>\Verify.ini (Integrated project - Locally
saved settings) \<first_writeableWDIR>\config\<unique_id>\
Note
Only settings that differ from the VerifyDefaults.ini settings appear in your local
Verify.ini file.
Example 1 - Concurrent Project

Figure 8-1 shows an example of a search order for a concurrent Integratedproject type.

Example 8-1. DRC Verify Tool File Precedence Order (Concurrent Design)
Example 2 - Non-Concurrent Project

Figure 8-2 shows an example search order for a project type that does not use the Remote
Server Configuration Manager (RSCM).

Example 8-2. DRC Verify Tool File Precedence Order (Non-Concurrent Project)
Related Topics
Verify Dialog Box

Prerequisites for DRC Electrical Checks

For electrical checks drc-203, drc-204, and drc-205, the Tools > Verify utility calculates
numerical values for the voltage drop or the power across components and identifies pin
polarity.
You must meet the following conditions in order to enable the voltage drop or the power
calculation:
o Net names must follow a convention: names of nets connected to a power supply
must start with a + (for positive voltage) and with a (for negative voltage)
followed by a numerical value (for example, using the string +5V*, the extracted
value used for calculation is +5).
o Names of nets connected to a ground must be listed as ground_nets in the <Defines>
section of the VerifyDefaults.ini file. The value used for calculation is 0.
o Verify that the <Defines> section of the VerifyDefaults.ini file defines power_nets
values for every power supply value you might use in the design, such as those
shown in the following example:
<Option Name="power_nets" Value="VCC +2.5V* -2.5V* +3.3V"/>
The Verify utility identifies pin polarity through drc_positive and drc_negative options
in the <Defines> section of the VerifyDefaults.ini file, which default to properties,
respectively, DRC Positive and DRC Negative.
You must check that the properties associated with drc_positive and drc_negative exist
as Pin properties in the Central Library .prp file. The Central Library .prp file is editable
with Tools > Properties Definition Editor. For more information on how to add the pin
properties, see Creating a User-Defined Property.
For drc-204 and drc-205, if you want to specify a Min Value;Max Value setting
exception to the value specified in the Verify dialog box setting (shown below) for
certain components:
a. You must first define a user symbol property in the Central Library .prp file called
DRC Voltage (drc-204) or DRC Power (drc-205). The property names are
determined in the following drc_voltage and drc_power options of the <Defines>
section of the VerifyDefaults.ini file:
<Option Name="drc_voltage" Value="DRC Voltage" />
<Option Name="drc_power" Value="DRC Power" />

b. Place the DRC Voltage or DRC Power property on a component(s) with a value
(such as 50mV;5.0V) that specifies the exception to the initial drc-204 or drc-205
Min Value;Max Value setting.
Related Topics
Verify Dialog Box
Creating a User-Defined Property


Appendix A
Supplemental Information
The following topics provide supplemental reference information:

Design Entry Tool COLORS Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
LineSimLink - Passives Prefixes - Models Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
Pin (Port) Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
Property Editing Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
Verilog HDL Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
Verilog HDL Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
Verilog HDL Parameters as User-Defined Name/Value Pairs . . . . . . . . . . . . . . . . . . . . 470
Verilog HDL Parameters Used as Physical Properties . . . . . . . . . . . . . . . . . . . . . . . . . . 472
Using Parameters in Verilog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
How the VHDL Netlist is Processed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
Example VHDL Netlist Output File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
The QCV Netlist Output Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
Search Query Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
Regular Expression Syntax in Text Searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
Numeric Operators for Databook Tool Search Conditions . . . . . . . . . . . . . . . . . . . . . . . 482
Wildcard Characters for Databook Tool Search Conditions . . . . . . . . . . . . . . . . . . . . . 483
Design Entry Tool COLORS Element

Each object and layer defined in the design entry tool and stored in the DxDesigner.xml file
contains a COLOR definition line similar to the bolded line in the following example:
<NET>
<key name="VISIBLE" value="1" />
<key name="SELECTABLE" value="1" />
<key name="COLOR" value="0x00ff00" />
<key name="FILL_STYLE" value="1" />
<key name="LINE_STYLE" value="0" />
</NET>
Figure A-1 shows the default colors you can choose to assign to an object.

Figure A-1. Default Colors Choices for Objects and Layers
Note
Each object type uses the color defined in Setup > Settings, Display (category), Objects
(subcategory), and the DxDesigner.xml file if the Color property (on that object) is set to
Automatic as shown in Figure A-2. Otherwise, each selected object color can be set individually
in the Properties window.
Figure A-2. Choosing Automatic Color Property Value in the Properties Window
The color choices are translated to a hex value in the DxDesigner.xml file. The hex value
defines the Red, Green, and Blue intensities to make up each unique color value. The following
example defines a value of black. The first two numbers following the 0x are the intensity
setting for Red (00, meaning no Red color), the next two are for green, the final two are for blue.


<value>0x000000</value>
To help with converting colors from pre-Release 2007 PADS DX Designer designs, the
COLORS element definition section of the DxDesigner.xml file is divided into two sections,
one for SCREEN and one for PRINTER to correspond with pre-Release 2007 color settings as
shown in Figure A-3. When converting a pre-Release design to the current Release, this
DxDesigner.xml section helps to map the old settings to a new value set (or maintain the
original defaults).

In addition to the default colors, you can define your own custom colors by clicking the Other
button from the color palette to bring up the Color dialog box.
Figure A-3. Pre-Release-2007 Color Settings Mapped in Current

DxDesigner.xml
Related Topics

LineSimLink - Passives Prefixes - Models Usage
LineSimLink - Passives Prefixes - Models

Usage
Passive components are exported to LineSim as a package/connector symbol. For information
about assigning models to the symbol, refer to the topic Selecting Package and Connector
Models in the LineSim User Guide.
The property SIM_MODEL_FILE is used to connect a simulation model file with the symbol in
the design capture tool. The property SIM_MODEL names the model in a simulation model
file. If these two properties are not present, LineSimLink uses the Part Name property to
identify the model file with .sp at the end of the filename.
For example, you might use the SIM_MODEL_FILE property to identify a SPICE or
Touchstone model file for a connector component.
When the models are changed in HyperLynx, importing from HyperLynx using LineSimLink,
the SIM_MODEL_FILE and SIM_MODEL properties are changed to the new value.
Related Topics
Pin (Port) Types

Scope: Symbol Editor
Pins define the electrical connection between the symbol and wiring in a schematic design.
Each pin in a symbol object must have a type definition to enable placement and wiring in a
schematic design.
Description
Pins can represent either a single electrical connection point, multiple electrical connection
points, or a bus pin. The following table defines the available pin type definitions and direction
that appear in the Symbol Editor Pins window.
Table A-1. Pin (Port) Types Used in the Symbol Editor
Pin (Port) Type Description
IN (Input) Digital input pins.
OUT (Output) Digital output pins that are not TRI (Tristate), OEM (Open emitter), or
OCL (Open collector).

Table A-1. Pin (Port) Types Used in the Symbol Editor (cont.)
Pin (Port) Type Description
BI (Bidirectional or Digital pins that are both input and output (process input and output
Bidir) signals).
TRI (Tristate) Digital three-state output pin.
OCL (Open Open collector output pin.
collector)
OEM (Open emitter) Emitter coupled logic (ECL) output pin.
POWER Supply pin, typically used for power pins on symbols (positive and
negative rails). Apply this pin type to positive and negative tap
symbols.
GROUND Ground pin, typically used for ground pins on symbols. Apply this pin
type to ground tap symbols.
ANALOG Pin used for analog devices and for analog pins on digital devices (for
example, DAC output pins and ADC input pins).
TERMINAL Terminal pin for VHDL-AMS (Analog Mixed Signal).
Unknown symbol pin Pin that requires a pin (port) type association.
type

You create new properties with the Property Definition Editor in xDM Library tools.
In an integrated design, for more information see Defining Properties for Use in Schematic and
Layout Designs in the xDM Library Tools Process Guide.
In a Netlist project, you can create and edit properties with the Property Definition Editor from
the Tools > Property Definition Editor menu. For more information see Property Definitions
in the Netlist Project.
When you place a symbol on your design, you can select which of the symbol properties to use,
then add or edit them.
You control property and value visibility with the following order of precedence, with 1
having the highest precedence and 3 the lowest:
1. Component level settings (when placed on the schematic)

2. Symbol level settings (assigned by the librarian)
3. Property Definition Editor level settings

For editing purposes, there are three types of properties. The rules for editing them appear in
Table A-2 on page 468.
Table A-2. Property Editing Rules
Property Type Example Editing Actions Allowed
Symbol Property Partition Change Values
Added by the librarian to the symbol
Component Property Description Change values
Added by the user to the placed Delete
component
System Property Id None
Added by the tool
Related Topics
Properties Window

In order to make lower-level blocks reusable, parameters are often used within them (for
example, as length and width values for a MOSFET). By passing named parameters to a lower-
level block and assigning them different values for each instance, the resulting properties of the
lower-level block can be changed without changing its definition.
The Verilog Netlister supports parameter passing by attaching a Parameter Value text property
to a lower-level block instance (that is, a block symbol or symbol with a Block Name text
property in the schematic). Any parameters defined in the Parameter value are passed to the
lower-level block and visible to all components in the lower-level block. The text of the
Parameter value might look like this:
MY_L=10
MY_W=20
If you specify more than one parameter on the same line, enclose each parameter in quotes. For
example:
"MY_L=10","MY_W=20"

For SPICE, numbers can be suffixed with one of the following letters, using upper-case or
lower-case, to provide magnitude scaling:
f - 1E-15
p - 1E-12
n - 1E-9
u - 1E-6
mil - 25.4E-6
m - 1E-3
k - 1E+3
meg - 1E+6
g - 1E+9
t - 1E+12
More complex expressions can be defined for parameters, including simple mathematical
operators (+,-,*,/) parenthetic grouping, and references to other parameters. For example, the
following is a valid parameter definition:
MY_PARM=(10.5p+@MY_OTHER_PARM)*2
References to other parameters must include a @ prefix before the parameter name. Note that
parameters can be passed down multiple levels of hierarchy by explicitly including a reference
to the upper-level parameter in a Parameter Value text property attached to an instance of a
lower-level circuit. For example:
MY_PARM_2=@MY_PARM
In this case, @MY_PARM refers to the parameter passed in to the circuit containing an instance
of the lower-level circuit, and MY_PARM_2 defines a new parameter for the lower-level circuit
using the value of MY_PARM passed from above. If desired, the same name can be used for
both.
When defining parameters, additional white space can be inserted into the expression to
improve readability. Parameter names are case-insensitive.
Related Topics
Verilog HDL Objects
Verilog HDL Parameters as User-Defined Name/Value Pairs
Verilog HDL Parameters Used as Physical Properties
Using Parameters in Verilog

Verilog HDL Objects
Verilog HDL Objects

Verilog HDL parameters are valid for component instances and nets, and are defined by
attaching Parameter Value text properties to symbol instances and nets. When attached to a
symbol instance which represents either a block defined in the design or a model defined
outside the design (for example, in a library), the HDL parameters will act as user-defined
name/value pairs which are passed to the block definition or library model.
When HDL parameters are attached to a symbol which represents a primitive device or to a net,
the parameters are interpreted as physical properties of the device or net. The Verilog HDL
Parameters Used as Physical Properties on page 472 topic discusses this special case in more
detail.
Related Topics
Verilog HDL Parameters as User-Defined

Name/Value Pairs
The following figure illustrates a simple use of HDL parameters as user-defined name/value
pairs and the corresponding results in the netlist.

Figure A-4. Verilog HDL Parameters as User-Defined Name/Value Pairs
The schematic in Figure A-4 contains a single instance of a block named lower and has a
Parameter Value text property attached which defines three parameters: RISE, FALL, and OFF.
Assume that the pins of the instance are connected to nets of the same names as the pins. When
this instance is netlisted, the following results:
SPICE:
Xlower1 In1 In2 Out1 Out2 lower RISE=5 FALL=6 OFF=7
Verilog:
lower lower1 (.In1(In1), .In2(In2), .Out1(Out1), .Out2(Out2));
defparam lower1.RISE=5;
defparam lower1.FALL=6;
defparam lower1.OFF=7;
Related Topics
Verilog HDL Objects

Verilog HDL Parameters Used as Physical

Properties
The following figure illustrates a simple use of Verilog HDL parameters for defining physical
properties and the corresponding results in the netlist.
Figure A-5. Verilog HDL Parameters for Defining Physical Properties
The schematic shown in Figure A-5 is the block definition for the lower block instance used in
the previous figure. It contains two Verilog primitive gates, a buffer 'buf' and an inverter 'not.'
The buffer 'buf' has a Parameter value which specifies a propagation delay for the gate. The
inverter 'not' has a Parameter value which specifies the drive strength for the gate. Finally, the
wire connected to port Out2 has a Parameter value which specifies rising, falling, and turn-off
propagation delay for the wire.
The following results would be obtained from the Verilog netlister for this schematic block:
module lower (In1, In2, Out1, Out2);

input In1, In2;
output Out1, Out2;
parameter RISE=0;
parameter FALL=0;
parameter OFF=0;
wire In1, In2, Out1;
wire #(RISE, FALL, OFF) Out2;
buf #(5) (Out1, In1);
not (strong1, strong0) (Out2, In2);
endmodule

Note
Parameters used in a schematic block will be defined in the corresponding Verilog module
with a default value of zero. In order to prevent potential simulation errors, always override
the default values with specific values attached to each instance of the schematic block.
Related Topics
Verilog HDL Objects

The following table defines the keywords recognized in Verilog, on which objects they can be
used, and what values the keyword can assume.
Table A-3. Verilog-Recognized Keywords

Keyword Objects Supported Values
DELAY= ComponentsWires single delay value or min:typ:max
RISEDELAY= ComponentsWires single delay value or min:typ:max
FALLDELAY= ComponentsWires single delay value or min:typ:max
OFFDELAY= ComponentsWires single delay value or min:typ:max
DECAY= Wires (trireg only) single delay value
STRENGTH= Components small medium large
STRENGTH1= Components supply1 strong1 pull1 weak1 highz1
STRENGTH0= Components supply0 strong0 pull0 weak0 highz0
WIRETYPE Wires trireg
Related Topics
Verilog HDL Objects


All settings, such as mapping of names, external packages, etc. are stored in a hdlutils.ini file
that is created in the project directory during creation of the VHDL netlist.
Processing begins at the lowest-level block and proceeds to the highest-level block. Each block
is written as an entity, with a port map that lists all of its external pins.
The architecture is then written, declaring signals that are only visible within the block, any
needed temporary signals, and any needed component declarations. Then a component
instantiation is written for each instance of each component using the port mapping from the
component pin name to the block net name.
Temporary signals are sometimes necessary because VHDL does not allow the direct
connection of certain pin types to other pin types. The temporary signals provide a layer of
indirection that satisfies the VHDL semantics.
VHDL requires that the Hier Pin Name of a hierarchical bidirectional pin match the Net Name
of the net connected to the pin.
A project file that contains the location of the Remote Server Configuration Manager and
needed configuration files is required.
Related Topics

The following is an example output file.

-- File : E:\scott\1405test\vhdltest1\genhdl\sbk\sample.vhd
-- CDB : E:\scott\1405test\vhdltest1\sample.cdb
-- By : CDB2VHDL Netlister version 15.0.0.0
-- Time : Mon January 27 11 14:46:27 2014
-- Entity/architecture declarations
use work.all;
library IEEE;
use IEEE.std_logic_1164.all;
entity bottom is
port(
P1 : out BIT;
P2 : out BIT;
X : in BIT;
Y : in BIT;
Z : in BIT
);
end bottom;
architecture bottom of bottom is
-- Component declarations
component INV
port(
A : in BIT;
O : out BIT
);
end component;
-- Signal declarations
signal cdb2vhdl_tmp_1 : BIT;
begin
-- Signal assignments
cdb2vhdl_tmp_1 <= Y after 0 ns;
-- Component instances
XCMP1 : INV
port map(
A => X,
O => P1
);
XCMP3 : INV
port map(
A => cdb2vhdl_tmp_1,
O => P2
);
XCMP6 : INV
port map(
A => Z,
O => cdb2vhdl_tmp_1
);
end bottom;
use work.all;
library IEEE;
use IEEE.std_logic_1164.all;
entity top is
port(
A : in std_ulogic;
B : in std_ulogic;
C : in std_ulogic;
D : in std_ulogic;
ZZZ : out std_ulogic
);

end top;
architecture top of top is
-- Component declarations
component bottom
port(
P1 : out BIT;
P2 : out BIT;
X : in BIT;
Y : in BIT;
Z : in BIT
);
end component;
component TRISTA
port(
O : out BIT;
E : in BIT;
A : in BIT
);
end component;
component AND3
port(
A : in BIT;
B : in BIT;
C : in BIT;
O : out BIT
);
end component;
component INV
port(
A : in BIT;
O : out BIT
);
end component;
component AND2
port(
O : out BIT;
A : in BIT;
B : in BIT
);
end component;
-- Signal declarations
signal AAA : std_ulogic;
signal ABC : BIT;
signal cdb2vhdl_tmp_1 : BIT;
signal XSIG010010 : BIT;
signal XYZ0 : BIT;
begin
-- Signal assignments
AAA <= A after 0 ns;
cdb2vhdl_tmp_1 <= '0';
-- Component instances
lower : bottom
port map(
P1 => ABC,
P2 => XSIG010010,
X => XYZ0,

Y => XSIG010013,
Z => cdb2vhdl_tmp_1
);
XCMP4 : TRISTA
port map(
To_stdulogic(O) => ZZZ,
E => XSIG010013,
A => XSIG010017
);
XCMP2 : AND3
port map(
A => ABC,
B => XSIG010010,
C => To_bit(D),
O => XSIG010017
);
XCMP3 : INV
port map(
A => To_bit(C),
O => XSIG010013
);
XYZ0_1 : AND2
port map(
O => XYZ0,
A => To_bit(AAA),
B => To_bit(B)
);
end top;
Related Topics

The Quick Connection View (QCV) netlist is divided into fields that are separated with a
separator (a space in these examples) as follows:
FIELD1[separator]FIELD2[separator]FIELD3[separator]FIELD4[separator]
Also see Figure A-6.
FIELD1 - Is a keyword to identify the type of net as either:
NET
PIN
FIELD2 - Is the colon character (:)
FIELD3 - Shows the hierarchical net name in between single quotes

Search Query Syntax
FIELD4 - Shows the net connections to all pins
Figure A-6. Quick Connection View Netlist Example 1
Related Topics
Connectivity Checks With a Quick Connection View Netlist
Search Query Syntax

In addition to plain text, you can use operator and wildcard characters to search the design or
database in the Edit > Find and Replace > Search window to narrow the list of found parts.
In the search field at the top of the window, you can use any of the characters shown in the
following table to narrow the search for parts.
The following list describes some search considerations:
Regarding wildcards (* or ?):

o They can be used in stand-alone values such as CAP* and 10*k.
o They can be used with the Like (=) operator.

Search Query Syntax
o They do not work with the Equal (==) operator.

Searches are case-insensitive.
In the case of a search that uses a property name on the left-side of an operator such as
<property> <operator> <text>, you do not need to double quote a property name
string that contains spaces.
You must enclose the following special characters in double-quotes if you want to
search for a text string that contains any of them:
&=></@
Some examples of text strings that require double-quotes are:
Search for Enter
strings with spaces strings with spaces
words with quotes words with quotes
logic@chip logic@chip
The - (not) character is only considered a special character if it is used as the first
character of a text string.
Table A-4. Search Query Syntax Examples

Search String Examples Result of Search
<text> CAP Displays all lines containing CAP.
?<text> ?n In the first example, using the any single
<text>? character wildcard (?), displays lines
containing in, on, Pn, and so on.
<text>* CAP* Using the zero or more characters wildcard
*<text> (*), displays lines containing CAP,
CAPACITOR, CAPACITY, and so on.
<text1> & <text2> CAP&10uF Using the AND (&) operator, displays lines
<text1>&<text2> CAP 10uF containing both CAP and 10uF. Because the &
<text1> <text2> operator is implied between multiple strings,
you do not need to use it, as shown in the
second example.
<property>==<text> Value==1 Using the Equal (==) operator, displays lines
with the Value property equal to 1.

Search Query Syntax
Table A-4. Search Query Syntax Examples (cont.)

<property><compar Cost > .1 Using one of the comparison operators,
_operator><text> Cost >= .1 displays lines that satisfy the mathematical
operation. These comparisons also work on
Cost < .1 strings, not just numbers.
Cost <= .1
Cost <>.1
<property>=<text> Value=1 Using the Like (=) operator, displays lines with
the Value property containing 1, such as 10, 1,
1ohm.
<text> Part Label Using quotes ( ) to treat the text as a string of
characters, displays lines that contain the string
Part Label. Use quotes to escape special
characters used within a string such as 1/2, or
start->stop.
@<database_type> @Parametric Data Using the Scope (@) operator, the first
or @Parts.Capacitor example displays all lines within the
Parametric Data database type.
@<database_type>. @Capacitor
<partition> The second example displays all lines within
the Parts database type, in the Capacitor library
or partition.
@<partition> Assuming that the third example has a
Capacitor partition in more than one database
type, the search displays all lines from all
databases types containing the Capacitor
partition.
Note: The following conditions apply to
using the Scope operator:
When a search does not include the
Scope operator, the search uses the
scope from the Property Chooser
window.
When you use the Scope operator, the
search ignores the Property Chooser
window scope settings.
<property> / Value /Symbol =1 Using the Level character (/), displays lines
<property_level> that have a Value property value equal to 1 on
=<value> the Symbol property level.

Table A-4. Search Query Syntax Examples (cont.)

-<text> -CAP Using the NOT (-) operator, the first example
or -@Parametric Data displays all lines except those containing CAP.
-@<database_type> The second example displays all lines except
those in the Parametric Data database type.
Related Topics
Databook Tool Overview
Searching for Objects in a Design or Components in a Database Library

Property and label syntax preferences use the following regular expression syntax:
A regular expression is zero or more branches, separated by |. It matches anything that
matches one of the branches.
A branch is zero or more pieces, concatenated. It matches a match for the first, followed
by a match for the second, until it reaches the end of a branch.
A piece is an atom possibly followed by *, +, or ?. An atom followed by * matches a
sequence of 0 or more matches of the atom. An atom followed by + matches a sequence
of 1 or more matches of the atom. An atom followed by ? matches a match of the atom,
or the null string.
An atom is a regular expression in parentheses (matching a match for the regular
expression), a range, . (matching any single character), ^ (matching the null string at the
beginning of the input string), $ (matching the null string at the end of the input string),
a \ followed by a single character (matching that character), or a single character with no
other significance (matching that character).
A range is a sequence of characters enclosed in []. It normally matches any single
character from the sequence. If the sequence begins with ^, it matches any single
character not from the rest of the sequence. If two characters in the sequence are
separated by -, this is shorthand for the full list of ASCII characters between them (e.g.
[0-9] matches any decimal digit). To include a literal ] in the sequence, make it the first
character (following a possible ^). To include a literal -, make it the first or last
character.
Related Topics

Numeric Operators for Databook Tool Search

Conditions
You can add numeric operators to your Databook database library search conditions.
Table A-5. Numeric Comparison Operators

Operator Function Example
= Represents values equal to the specified The = 20 operator returns a list
numeric value. of components for which the
numeric value of the specified
property equals 20.
> Represents values greater than the The > 20 operator matches all
specified numeric value. numeric values of the specified
property greater than 20.
< Represents values less than the specified The < 1.25 operator matches all
numeric value. numeric values of the specified
property less than 1.25.
>= Represents values greater than or equal to The >= 32 operator matches all
the specified numeric value. numeric values of the specified
property greater than or equal to
32.
<= Represents values less than or equal to the The <= 0.05 operator matches
specified numeric value. all numeric values of the
specified property less than or
equal to 0.05.
!= Represents values not equal to the The != 34 operator matches all
specified value. numeric values of the specified
property except those that equal
34.
Related Topics

Wildcard Characters for Databook Tool Search

Conditions
The Databook tool supports using wildcards in your database library search conditions. By
default, the Databook tool uses the standard SQL percent (%) wildcard to match multiple string
characters and underscore (_) wildcard to match an individual character.
Note
To search for components using wildcards, the database is required to contain string data
and the like operator must be used.
The following wildcard characters are supported:
Percent sign (%) which represents any of zero or more (multiple) characters.
For example:
o string% Matches any value beginning with string.
o %string Matches any value ending with string.
Underscore (_) which represents any individual character.
For example:
o string_ Matches string followed by one character.
o _string Matches any two characters followed by string.
Use the question mark (?) wildcard symbol to match a single character and the asterisk (*)
wildcard symbol to match multiple characters in your database library search.
Note
xDX Databook does not support question mark (?) and asterisk (*) wildcard symbols when
connected to xDM Library Tools through xDM Connector.
For example, using RESISTO? as a search string only yields RESISTOR whereas RESISTO*
yields a list of all parts in the database that include the RESISTO string (such as RESISTOR and
RESISTOR123).
Related Topics


Index
bpaste, 408
Index
A bsize, 408
Advanced settings, 375 bus, 408
B cattribute, 409
Bus cb, 409
names, 432 ccomp, 409
Bus bundles chgattr, 409
bus contents file, 27 chglabel, 409
busconts.ini file, 27 chgtext, 409
cinst, 409
C circle, 409
CCZ Exporter, 185 color, 409
Characters component, 409
illegal in name identifiers, 429 copy, 409
Command line comman ds csize, 410
system, 421 ctoff, 410
Command line commands cton, 410
adistance, 406 cuapply, 410
ainvis, 406 cucheck, 410
align, 406 cycle, 410
ansize, 406 db, 410
anvis, 406 dbevoff, 410
aoff, 406 dbevon, 410
aon, 406 defsh1off, 411
arc, 406 defsh1on, 411
aroute, 407 defshcfg, 411
array, 407 defshfix, 411
arrowsoff, 407 defshoff, 410
arrowson, 407 defshon, 410
asize, 407 delete, 411
avis, 407 directory, 411
avvis, 407 dirsym, 411
bb, 407 doff, 411
bcast, 408 don, 411
bcomposite, 408 dsize, 412
bcopy, 408 egoff, 412
bcut, 408 egon, 412
boff, 408 esize, 412
bon, 408 exit, 412
box, 408 fcloseall, 412

form, 412 refresh, 418
full, 412 roff, 418
goff, 412 ron, 418
gon, 413 rotate, 418
grid, 413 run, 418
ground, 413 scale, 419
gspace, 413 schematic, 419
ib, 413 scomp, 419
in, 413 sdistance, 419
io, 413 setenv, 419
label, 413 sicdb, 419
line, 413 size, 419
linvis, 414 slabel, 419
loff, 414 slot, 419
logmemory, 414 sname, 419
lon, 414 snap, 420
longstrings, 414 soff, 420
lsense, 414 son, 420
lvis, 414 sroute, 420
move, 414 stext, 420
name, 415 stretch, 420
narray, 415 string, 420
naspace, 415 stub, 420
net, 415 svalue, 420
noff, 415 text, 421
non, 415 toff, 421
nsym, 415 ton, 421
o1 through o9, 416 ubat, 421
odetail, 416 undo, 421
offsheet, 416 uoff, 421
onsheet, 416 uon, 421
oroute, 416 value, 421
out, 416 voff, 421
pdbslot, 416 von, 422
placedetail, 416 wclose, 422
poff, 416 zoom, 422
pon, 416 zselect, 422
pop, 417 zsize, 422
power, 417 Configuration and initialization file summary,
psch, 417 15
psheet, 417 contents.bc, bus contents file, 27
psym, 417 example, 28
quit, 418 Cross Probing settings, 361
read, 418
reflect, 418 D
Dialog Boxes

Add Block, 174 Font Mappings settings, 358
Add Properties, 179 Objects settings, 356
Apply Symbol Updates to Components, Display characteristics, 356
410 DRC
Archiver Wizard, 215 vdrc command line, 405
Change Attribute, 409 DxDe signer.xml ICTOBJECTS
Change Border, 409 ICTEDITCELL elements, 59
Change Bounding Box, 407 DxDesigner.x ml ICTOBJECTS
Change Label, 409 ICTGROUP elements, 59
Change Text, 409 DxDesigner.xml, 342, 343
Color, 466 DxDesigner.xml ICTOBJECTS
Customize (Toolbars), 189, 190, 191 ICTBLOCK elements, 59
Customize Tools Menu, 187 ICTBUS elements, 59
DRCschematic_name, 387 ICTCOMPONENT elements, 59
Find and Replace Text, 224 ICTDIFFPAIR elements, 59
Generate Symbol, 229 ICTFPGA elements, 59
Advanced Options, 230 ICTFUB elements, 59
Insert Object, 231 ICTHIGHLIGHT_LAYER elements, 59
LineSimLink ICTINVALIDCELL elements, 59
Options tab, 233 ICTNET elements, 59
Schematic Topology tab, 236 ICTNETS elements, 59
Load Properties Scheme, 344 ICTPIN elements, 59
Make Attributes Visible, 407 ICTPORT elements, 59
Merge Differences, 238 ICTSYMBOL elements, 59
New Library Symbol, 240 DxDesigner.xml LAYERS
New Project, 241 ANNOTATION_LAYER elements, 57
Open Block, 243 BACKGROUND_LAYER elements, 57
Packager, 244 BORDER_LAYER elements, 57
Part Lister, 249 CROSS_REFERENCE_LAYER elements,
Advanced Tab, 252 57
Columns Tab, 257 DRAG_LAYER elements, 57
General Tab, 250 GRID_LAYER elements, 57
Header Tab, 264 HIGHLIGHT_LAYER elements, 57
Paste Special, 266 SELECTION_LAYER elements, 57, 59
Property Definition Editor, 270 UNPLACEDCOMPONENT_LAYER
Quick Connection View, 275, 278 elements, 57
Save Properties Scheme, 344 VALUE_LAYER elements, 57
Scale, 291 ZONES_LAYER elements, 57
Simulation Setup, 384 ZONING_LAYER elements, 57
Verilog Netlister, 391 DxDesigner.xml OBJECTS
VHDL Netlister, 392 ARC elements, 54
xDX PDF ATTRIBUTE elements, 54
Advanced Tab, 220 BUS elements, 54
General Tab, 217 CIRCLE elements, 54
Display COMPONENT elements, 54

FRAME elements, 54 ICTOBJECTS elements, DxDesig ner.xml
LINE elements, 54 ICTHIGHLI GHT_LAYER, 59
PIN elements, 54 ICTOBJECTS elements, DxDesigner.xml
TEXT elements, 54 ICTBLOCK, 59
WIRE elements, 54 ICTBUS, 59
DxDesigner.xml SETTINGS elements ICTDIFFPAIR, 59
DYNAMIC_PANNING, 322 ICTFPGA, 59
DxPDF ICTFUB, 59
initialization file, 160 ICTGROUP, 59
DYNAMIC_PANNING, DxDesigner.xml key ICTINVALIDCELL, 59
name, 322 ICTNET, 59
ICTNETS, 59
E ICTPIN, 59
Environment variables, 164 ICTSYMBOL, 59
Export ICTOBJECTSelements, DxDesigner.xml
CCX, 185 ICTEDITCELL, 59
F Info Tip box, Navigator, 352
File Viewer, 11 Interconnectivity Table settings, 341
G K
Grid settings, 320 Key bindings
Grid, snap to, 321 PADS, 445
PC, 433, 437
H
HDL Simulation settings, 368 L
HPGL_HEIGHT_SCALE variable Label
overview, 164 objects not labeled, 430
HPGL_WIDTH_SCALE variable LAYERS element s, DxDesigner.xml
overview, 164 ZONING_LAYER, 57
LAYERS elements, DxDesigner.xml
I ANNOTATION_LAYER, 57
ICE_CELLS SHOW_NETS, DxDesigner.xml BACKGROUND_LAYER, 57
key name, 342 BORDER_LAYER, 57
ICE_CELLS SHOW_WIDTH, CROSS_REFERENCE_LAYER, 57
DxDesigner.xml key name, 342 DRAG_LAYER, 57
ICE_PINSDROPDOWNLIST_SHOW_GLO GRID_LAYER, 57
BAL_NETS, DxDesigner.xml key HIGHLIGHT_LAYER, 57
name, 343 SELECTION_LAYER, 57, 59
ICE_PINSDROPDOWNLIST_SHOW_NETS UNPLACEDCOMPONENT_LAYER, 57
, DxDesigner.xml key name, 342 VALUE_LAYER, 57
ICE_PINSDROPDOWNLIST_SHOW_WIDT ZONES_LAYER, 57
H, DxDesigner.xml key name, 342 LineSimLink - Merge Differences, 238
ICTOBJE CTS elements, DxDesigner.xml LM_LICENSE_FILE variable
ICTPORT, 59 overview, 164
ICTOBJECTS elements, D xDesigner.xml
ICTCOMPONENT, 59

M format, 424
Merge Differences dialog, 238 multiple and duplicate, 425
MGC_EPD_INVISIBLE_ ADDIN_LIST multiple values, 426
variable name and value restrictions, 424
overview, 165 netlist interpretation, 425
MGLS_LICENSE_FILE variable ranges, 426
overview, 164 used by Design Rule Checker, 45
user-defined, 425
N
Name R
adding and editing, introduction, 429 Ranges
bus, 432 properties, 426
compound, 431 Regular expression syntax, 453, 481
illegal characters in, 429 Run on Startup settings, 371
pin, 432
ranges, 430 S
sch2pdf, pdf generation command, 403
unique, 431
Navigator Info Tip box, 352 Settings dialog
Advanced, 375
Nets settings, schematics, 328
Cross Probing, 361
New Sheets settings, 324
Display, 354
O Font Mappings, 358
Objects Objects, 356
unlabeled, 430 HDL Simulation, 368
OBJECTS elements, DxDesigner.xml Interconnectivity Table, 341
ARC, 54 Run on Startup, 371
ATTRIBUTE, 54 Schematic Editor
BUS, 54 Grid, 320
CIRCLE, 54 Nets, 328
COMPONENT, 54 New Sheets, 324
FRAME, 54 Strokes, Pan and Zoom, 322
LINE, 54 Text, 327
PIN, 54 Units, 320
TEXT, 54 xDX Designer Diagnostics, 360
WIRE, 54 SETTINGS elements, DxDesigner.xml
DYNAMIC_PANNING, 322
P ICE_CELLS_SHOW_NETS, 342
Part Lister ICE_CELLS_SHOW_WIDTH, 342
icdbpartslister.exe usage, 396 ICE_PINSDROPDOWNLIST_GLOBAL_
initialization file, 142 NETS, 343
PATH variable ICE_PINSDROPDOWNLIST_SHOW_N
overview, 165 ETS, 342
Pin ICE_PINSDROPDOWNLIST_SHOW_W
names, 432 IDTH, 342
Property Shell commands
characteristics, 423 AllegroNetlist, 393

DxArchiver, 393
edifExporter, 393
icdbpartslister, 394
KeyinNetlist, 394
package, 394
QuickConnectionView, 394
RinfNetlist, 394
sch2pdf, 394
Strokes, Pan and Zoom settings, 322
Syntax
regular expression, 453
T
Text settings, 327
U
Units settings, 320
V
vdrc, Design Rule Checker command, 405
ViewDRC
ambiguity, 454
regular expression syntax, 453
Visibility
options, 423
W
WDIR variable
overview, 165
Windows
File Viewer, 11
X
xDX Designer
display characteristics, 356
xDX Designer Diagnostics settings, 360

Third-Party Information
Open source and third-party software may be included in the Systems Design products.
For third-party information, refer to the Third-Party Software document.

End-User License Agreement
The latest version of the End-User License Agreement is available on-line at:
www.mentor.com/eula
IMPORTANT INFORMATION
USE OF ALL SOFTWARE IS SUBJECT TO LICENSE RESTRICTIONS. CAREFULLY READ THIS LICENSE
AGREEMENT BEFORE USING THE PRODUCTS. USE OF SOFTWARE INDICATES CUSTOMERS COMPLETE
AND UNCONDITIONAL ACCEPTANCE OF THE TERMS AND CONDITIONS SET FORTH IN THIS AGREEMENT.
ANY ADDITIONAL OR DIFFERENT PURCHASE ORDER TERMS AND CONDITIONS SHALL NOT APPLY.
END-USER LICENSE AGREEMENT (Agreement)
This is a legal agreement concerning the use of Software (as defined in Section 2) and hardware (collectively Products)
between the company acquiring the Products (Customer), and the Mentor Graphics entity that issued the corresponding
quotation or, if no quotation was issued, the applicable local Mentor Graphics entity (Mentor Graphics). Except for license
agreements related to the subject matter of this license agreement which are physically signed by Customer and an authorized
representative of Mentor Graphics, this Agreement and the applicable quotation contain the parties entire understanding
relating to the subject matter and supersede all prior or contemporaneous agreements. If Customer does not agree to these
terms and conditions, promptly return or, in the case of Software received electronically, certify destruction of Software and all
accompanying items within five days after receipt of Software and receive a full refund of any license fee paid.
1. ORDERS, FEES AND PAYMENT.
1.1. To the extent Customer (or if agreed by Mentor Graphics, Customers appointed third party buying agent) places and Mentor
Graphics accepts purchase orders pursuant to this Agreement (each an Order), each Order will constitute a contract between
Customer and Mentor Graphics, which shall be governed solely and exclusively by the terms and conditions of this Agreement,
any applicable addenda and the applicable quotation, whether or not those documents are referenced on the Order. Any
additional or conflicting terms and conditions appearing on an Order or presented in any electronic portal or automated order
management system, whether or not required to be electronically accepted, will not be effective unless agreed in writing and
physically signed by an authorized representative of Customer and Mentor Graphics.
1.2. Amounts invoiced will be paid, in the currency specified on the applicable invoice, within 30 days from the date of such invoice.
Any past due invoices will be subject to the imposition of interest charges in the amount of one and one-half percent per month
or the applicable legal rate currently in effect, whichever is lower. Prices do not include freight, insurance, customs duties, taxes
or other similar charges, which Mentor Graphics will state separately in the applicable invoice. Unless timely provided with a
valid certificate of exemption or other evidence that items are not taxable, Mentor Graphics will invoice Customer for all
applicable taxes including, but not limited to, VAT, GST, sales tax, consumption tax and service tax. Customer will make all
payments free and clear of, and without reduction for, any withholding or other taxes; any such taxes imposed on payments by
Customer hereunder will be Customers sole responsibility. If Customer appoints a third party to place purchase orders and/or
make payments on Customers behalf, Customer shall be liable for payment under Orders placed by such third party in the event
of default.
1.3. All Products are delivered FCA factory (Incoterms 2010), freight prepaid and invoiced to Customer, except Software delivered
electronically, which shall be deemed delivered when made available to Customer for download. Mentor Graphics retains a
security interest in all Products delivered under this Agreement, to secure payment of the purchase price of such Products, and
Customer agrees to sign any documents that Mentor Graphics determines to be necessary or convenient for use in filing or
perfecting such security interest. Mentor Graphics delivery of Software by electronic means is subject to Customers provision
of both a primary and an alternate e-mail address.
2. GRANT OF LICENSE. The software installed, downloaded, or otherwise acquired by Customer under this Agreement, including any
updates, modifications, revisions, copies, documentation, setup files and design data (Software) are copyrighted, trade secret and
confidential information of Mentor Graphics or its licensors, who maintain exclusive title to all Software and retain all rights not
expressly granted by this Agreement. Except for Software that is embeddable (Embedded Software), which is licensed pursuant to
separate embedded software terms or an embedded software supplement, Mentor Graphics grants to Customer, subject to payment of
applicable license fees, a nontransferable, nonexclusive license to use Software solely: (a) in machine-readable, object-code form
(except as provided in Subsection 4.2); (b) for Customers internal business purposes; (c) for the term of the license; and (d) on the
computer hardware and at the site authorized by Mentor Graphics. A site is restricted to a one-half mile (800 meter) radius. Customer
may have Software temporarily used by an employee for telecommuting purposes from locations other than a Customer office, such as
the employees residence, an airport or hotel, provided that such employees primary place of employment is the site where the
Software is authorized for use. Mentor Graphics standard policies and programs, which vary depending on Software, license fees paid
or services purchased, apply to the following: (a) relocation of Software; (b) use of Software, which may be limited, for example, to
execution of a single session by a single user on the authorized hardware or for a restricted period of time (such limitations may be
technically implemented through the use of authorization codes or similar devices); and (c) support services provided, including
eligibility to receive telephone support, updates, modifications, and revisions. For the avoidance of doubt, if Customer provides any
feedback or requests any change or enhancement to Products, whether in the course of receiving support or consulting services,
evaluating Products, performing beta testing or otherwise, any inventions, product improvements, modifications or developments made
by Mentor Graphics (at Mentor Graphics sole discretion) will be the exclusive property of Mentor Graphics.
3. BETA CODE.
3.1. Portions or all of certain Software may contain code for experimental testing and evaluation (which may be either alpha or beta,
collectively Beta Code), which may not be used without Mentor Graphics explicit authorization. Upon Mentor Graphics
authorization, Mentor Graphics grants to Customer a temporary, nontransferable, nonexclusive license for experimental use to
test and evaluate the Beta Code without charge for a limited period of time specified by Mentor Graphics. Mentor Graphics may
choose, at its sole discretion, not to release Beta Code commercially in any form.
3.2. If Mentor Graphics authorizes Customer to use the Beta Code, Customer agrees to evaluate and test the Beta Code under normal
conditions as directed by Mentor Graphics. Customer will contact Mentor Graphics periodically during Customers use of the
Beta Code to discuss any malfunctions or suggested improvements. Upon completion of Customers evaluation and testing,
Customer will send to Mentor Graphics a written evaluation of the Beta Code, including its strengths, weaknesses and
recommended improvements.
3.3. Customer agrees to maintain Beta Code in confidence and shall restrict access to the Beta Code, including the methods and
concepts utilized therein, solely to those employees and Customer location(s) authorized by Mentor Graphics to perform beta
testing. Customer agrees that any written evaluations and all inventions, product improvements, modifications or developments
that Mentor Graphics conceived or made during or subsequent to this Agreement, including those based partly or wholly on
Customers feedback, will be the exclusive property of Mentor Graphics. Mentor Graphics will have exclusive rights, title and
interest in all such property. The provisions of this Subsection 3.3 shall survive termination of this Agreement.
4. RESTRICTIONS ON USE.
4.1. Customer may copy Software only as reasonably necessary to support the authorized use. Each copy must include all notices
and legends embedded in Software and affixed to its medium and container as received from Mentor Graphics. All copies shall
remain the property of Mentor Graphics or its licensors. Except for Embedded Software that has been embedded in executable
code form in Customers product(s), Customer shall maintain a record of the number and primary location of all copies of
Software, including copies merged with other software, and shall make those records available to Mentor Graphics upon
request. Customer shall not make Products available in any form to any person other than Customers employees and on-site
contractors, excluding Mentor Graphics competitors, whose job performance requires access and who are under obligations of
confidentiality. Customer shall take appropriate action to protect the confidentiality of Products and ensure that any person
permitted access does not disclose or use Products except as permitted by this Agreement. Customer shall give Mentor Graphics
written notice of any unauthorized disclosure or use of the Products as soon as Customer becomes aware of such unauthorized
disclosure or use. Customer acknowledges that Software provided hereunder may contain source code which is proprietary and
its confidentiality is of the highest importance and value to Mentor Graphics. Customer acknowledges that Mentor Graphics
may be seriously harmed if such source code is disclosed in violation of this Agreement. Except as otherwise permitted for
purposes of interoperability as specified by applicable and mandatory local law, Customer shall not reverse-assemble,
disassemble, reverse-compile, or reverse-engineer any Product, or in any way derive any source code from Software that is not
provided to Customer in source code form. Log files, data files, rule files and script files generated by or for the Software
(collectively Files), including without limitation files containing Standard Verification Rule Format (SVRF) and Tcl
Verification Format (TVF) which are Mentor Graphics trade secret and proprietary syntaxes for expressing process rules,
constitute or include confidential information of Mentor Graphics. Customer may share Files with third parties, excluding
Mentor Graphics competitors, provided that the confidentiality of such Files is protected by written agreement at least as well as
Customer protects other information of a similar nature or importance, but in any case with at least reasonable care. Customer
may use Files containing SVRF or TVF only with Mentor Graphics products. Under no circumstances shall Customer use
Products or Files or allow their use for the purpose of developing, enhancing or marketing any product that is in any way
competitive with Products, or disclose to any third party the results of, or information pertaining to, any benchmark.
4.2. If any Software or portions thereof are provided in source code form, Customer will use the source code only to correct software
errors and enhance or modify the Software for the authorized use, or as permitted for Embedded Software under separate
embedded software terms or an embedded software supplement. Customer shall not disclose or permit disclosure of source
code, in whole or in part, including any of its methods or concepts, to anyone except Customers employees or on-site
contractors, excluding Mentor Graphics competitors, with a need to know. Customer shall not copy or compile source code in
any manner except to support this authorized use.
4.3. Customer agrees that it will not subject any Product to any open source software (OSS) license that conflicts with this
Agreement or that does not otherwise apply to such Product.
4.4. Customer may not assign this Agreement or the rights and duties under it, or relocate, sublicense, or otherwise transfer the
Products, whether by operation of law or otherwise (Attempted Transfer), without Mentor Graphics prior written consent and
payment of Mentor Graphics then-current applicable relocation and/or transfer fees. Any Attempted Transfer without Mentor
Graphics prior written consent shall be a material breach of this Agreement and may, at Mentor Graphics option, result in the
immediate termination of the Agreement and/or the licenses granted under this Agreement. The terms of this Agreement,
including without limitation the licensing and assignment provisions, shall be binding upon Customers permitted successors in
interest and assigns.
4.5. The provisions of this Section 4 shall survive the termination of this Agreement.
5. SUPPORT SERVICES. To the extent Customer purchases support services, Mentor Graphics will provide Customer with updates and
technical support for the Products, at the Customer site(s) for which support is purchased, in accordance with Mentor Graphics then
current End-User Support Terms located at http://supportnet.mentor.com/supportterms.
6. OPEN SOURCE SOFTWARE. Products may contain OSS or code distributed under a proprietary third party license agreement, to
which additional rights or obligations (Third Party Terms) may apply. Please see the applicable Product documentation (including
license files, header files, read-me files or source code) for details. In the event of conflict between the terms of this Agreement
(including any addenda) and the Third Party Terms, the Third Party Terms will control solely with respect to the OSS or third party
code. The provisions of this Section 6 shall survive the termination of this Agreement.
7. LIMITED WARRANTY.
7.1. Mentor Graphics warrants that during the warranty period its standard, generally supported Products, when properly installed,
will substantially conform to the functional specifications set forth in the applicable user manual. Mentor Graphics does not
warrant that Products will meet Customers requirements or that operation of Products will be uninterrupted or error free. The
warranty period is 90 days starting on the 15th day after delivery or upon installation, whichever first occurs. Customer must
notify Mentor Graphics in writing of any nonconformity within the warranty period. For the avoidance of doubt, this warranty
applies only to the initial shipment of Software under an Order and does not renew or reset, for example, with the delivery of (a)
Software updates or (b) authorization codes or alternate Software under a transaction involving Software re-mix. This warranty
shall not be valid if Products have been subject to misuse, unauthorized modification, improper installation or Customer is not in
compliance with this Agreement. MENTOR GRAPHICS ENTIRE LIABILITY AND CUSTOMERS EXCLUSIVE
REMEDY SHALL BE, AT MENTOR GRAPHICS OPTION, EITHER (A) REFUND OF THE PRICE PAID UPON
RETURN OF THE PRODUCTS TO MENTOR GRAPHICS OR (B) MODIFICATION OR REPLACEMENT OF THE
PRODUCTS THAT DO NOT MEET THIS LIMITED WARRANTY. MENTOR GRAPHICS MAKES NO WARRANTIES
WITH RESPECT TO: (A) SERVICES; (B) PRODUCTS PROVIDED AT NO CHARGE; OR (C) BETA CODE; ALL OF
WHICH ARE PROVIDED AS IS.
7.2. THE WARRANTIES SET FORTH IN THIS SECTION 7 ARE EXCLUSIVE. NEITHER MENTOR GRAPHICS NOR ITS
LICENSORS MAKE ANY OTHER WARRANTIES EXPRESS, IMPLIED OR STATUTORY, WITH RESPECT TO
PRODUCTS PROVIDED UNDER THIS AGREEMENT. MENTOR GRAPHICS AND ITS LICENSORS SPECIFICALLY
DISCLAIM ALL IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NON-INFRINGEMENT OF INTELLECTUAL PROPERTY.
8. LIMITATION OF LIABILITY. TO THE EXTENT PERMITTED UNDER APPLICABLE LAW, IN NO EVENT SHALL
MENTOR GRAPHICS OR ITS LICENSORS BE LIABLE FOR INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL
DAMAGES (INCLUDING LOST PROFITS OR SAVINGS) WHETHER BASED ON CONTRACT, TORT OR ANY OTHER
LEGAL THEORY, EVEN IF MENTOR GRAPHICS OR ITS LICENSORS HAVE BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES. IN NO EVENT SHALL MENTOR GRAPHICS OR ITS LICENSORS LIABILITY UNDER THIS
AGREEMENT EXCEED THE AMOUNT RECEIVED FROM CUSTOMER FOR THE HARDWARE, SOFTWARE LICENSE OR
SERVICE GIVING RISE TO THE CLAIM. IN THE CASE WHERE NO AMOUNT WAS PAID, MENTOR GRAPHICS AND ITS
LICENSORS SHALL HAVE NO LIABILITY FOR ANY DAMAGES WHATSOEVER. THE PROVISIONS OF THIS SECTION 8
SHALL SURVIVE THE TERMINATION OF THIS AGREEMENT.
9. THIRD PARTY CLAIMS.
9.1. Customer acknowledges that Mentor Graphics has no control over the testing of Customers products, or the specific
applications and use of Products. Mentor Graphics and its licensors shall not be liable for any claim or demand made against
Customer by any third party, except to the extent such claim is covered under Section 10.
9.2. In the event that a third party makes a claim against Mentor Graphics arising out of the use of Customers products, Mentor
Graphics will give Customer prompt notice of such claim. At Customers option and expense, Customer may take sole control
of the defense and any settlement of such claim. Customer WILL reimburse and hold harmless Mentor Graphics for any
LIABILITY, damages, settlement amounts, costs and expenses, including reasonable attorneys fees, incurred by or awarded
against Mentor Graphics or its licensors in connection with such claims.
9.3. The provisions of this Section 9 shall survive any expiration or termination of this Agreement.
10. INFRINGEMENT.
10.1. Mentor Graphics will defend or settle, at its option and expense, any action brought against Customer in the United States,
Canada, Japan, or member state of the European Union which alleges that any standard, generally supported Product acquired
by Customer hereunder infringes a patent or copyright or misappropriates a trade secret in such jurisdiction. Mentor Graphics
will pay costs and damages finally awarded against Customer that are attributable to such action. Customer understands and
agrees that as conditions to Mentor Graphics obligations under this section Customer must: (a) notify Mentor Graphics
promptly in writing of the action; (b) provide Mentor Graphics all reasonable information and assistance to settle or defend the
action; and (c) grant Mentor Graphics sole authority and control of the defense or settlement of the action.
10.2. If a claim is made under Subsection 10.1 Mentor Graphics may, at its option and expense: (a) replace or modify the Product so
that it becomes noninfringing; (b) procure for Customer the right to continue using the Product; or (c) require the return of the
Product and refund to Customer any purchase price or license fee paid, less a reasonable allowance for use.
10.3. Mentor Graphics has no liability to Customer if the action is based upon: (a) the combination of Software or hardware with any
product not furnished by Mentor Graphics; (b) the modification of the Product other than by Mentor Graphics; (c) the use of
other than a current unaltered release of Software; (d) the use of the Product as part of an infringing process; (e) a product that
Customer makes, uses, or sells; (f) any Beta Code or Product provided at no charge; (g) any software provided by Mentor
Graphics licensors who do not provide such indemnification to Mentor Graphics customers; (h) OSS, except to the extent that
the infringement is directly caused by Mentor Graphics modifications to such OSS; or (i) infringement by Customer that is
deemed willful. In the case of (i), Customer shall reimburse Mentor Graphics for its reasonable attorney fees and other costs
related to the action.
10.4. THIS SECTION 10 IS SUBJECT TO SECTION 8 ABOVE AND STATES THE ENTIRE LIABILITY OF MENTOR
GRAPHICS AND ITS LICENSORS, AND CUSTOMERS SOLE AND EXCLUSIVE REMEDY, FOR DEFENSE,
SETTLEMENT AND DAMAGES, WITH RESPECT TO ANY ALLEGED PATENT OR COPYRIGHT INFRINGEMENT
OR TRADE SECRET MISAPPROPRIATION BY ANY PRODUCT PROVIDED UNDER THIS AGREEMENT.
11. TERMINATION AND EFFECT OF TERMINATION.
11.1. If a Software license was provided for limited term use, such license will automatically terminate at the end of the authorized
term. Mentor Graphics may terminate this Agreement and/or any license granted under this Agreement immediately upon
written notice if Customer: (a) exceeds the scope of the license or otherwise fails to comply with the licensing or confidentiality
provisions of this Agreement, or (b) becomes insolvent, files a bankruptcy petition, institutes proceedings for liquidation or
winding up or enters into an agreement to assign its assets for the benefit of creditors. For any other material breach of any
provision of this Agreement, Mentor Graphics may terminate this Agreement and/or any license granted under this Agreement
upon 30 days written notice if Customer fails to cure the breach within the 30 day notice period. Termination of this Agreement
or any license granted hereunder will not affect Customers obligation to pay for Products shipped or licenses granted prior to
the termination, which amounts shall be payable immediately upon the date of termination.
11.2. Upon termination of this Agreement, the rights and obligations of the parties shall cease except as expressly set forth in this
Agreement. Upon termination of this Agreement and/or any license granted under this Agreement, Customer shall ensure that
all use of the affected Products ceases, and shall return hardware and either return to Mentor Graphics or destroy Software in
Customers possession, including all copies and documentation, and certify in writing to Mentor Graphics within ten business
days of the termination date that Customer no longer possesses any of the affected Products or copies of Software in any form.
12. EXPORT. The Products provided hereunder are subject to regulation by local laws and European Union (E.U.) and United States
(U.S.) government agencies, which prohibit export, re-export or diversion of certain products, information about the products, and
direct or indirect products thereof, to certain countries and certain persons. Customer agrees that it will not export or re-export Products
in any manner without first obtaining all necessary approval from appropriate local, E.U. and U.S. government agencies. If Customer
wishes to disclose any information to Mentor Graphics that is subject to any E.U., U.S. or other applicable export restrictions, including
without limitation the U.S. International Traffic in Arms Regulations (ITAR) or special controls under the Export Administration
Regulations (EAR), Customer will notify Mentor Graphics personnel, in advance of each instance of disclosure, that such information
is subject to such export restrictions.
13. U.S. GOVERNMENT LICENSE RIGHTS. Software was developed entirely at private expense. The parties agree that all Software is
commercial computer software within the meaning of the applicable acquisition regulations. Accordingly, pursuant to U.S. FAR 48
CFR 12.212 and DFAR 48 CFR 227.7202, use, duplication and disclosure of the Software by or for the U.S. government or a U.S.
government subcontractor is subject solely to the terms and conditions set forth in this Agreement, which shall supersede any
conflicting terms or conditions in any government order document, except for provisions which are contrary to applicable mandatory
federal laws.
14. THIRD PARTY BENEFICIARY. Mentor Graphics Corporation, Mentor Graphics (Ireland) Limited, Microsoft Corporation and
other licensors may be third party beneficiaries of this Agreement with the right to enforce the obligations set forth herein.
15. REVIEW OF LICENSE USAGE. Customer will monitor the access to and use of Software. With prior written notice and during
Customers normal business hours, Mentor Graphics may engage an internationally recognized accounting firm to review Customers
software monitoring system and records deemed relevant by the internationally recognized accounting firm to confirm Customers
compliance with the terms of this Agreement or U.S. or other local export laws. Such review may include FlexNet (or successor
product) report log files that Customer shall capture and provide at Mentor Graphics request. Customer shall make records available in
electronic format and shall fully cooperate with data gathering to support the license review. Mentor Graphics shall bear the expense of
any such review unless a material non-compliance is revealed. Mentor Graphics shall treat as confidential information all information
gained as a result of any request or review and shall only use or disclose such information as required by law or to enforce its rights
under this Agreement. The provisions of this Section 15 shall survive the termination of this Agreement.
16. CONTROLLING LAW, JURISDICTION AND DISPUTE RESOLUTION. The owners of certain Mentor Graphics intellectual
property licensed under this Agreement are located in Ireland and the U.S. To promote consistency around the world, disputes shall be
resolved as follows: excluding conflict of laws rules, this Agreement shall be governed by and construed under the laws of the State of
Oregon, U.S., if Customer is located in North or South America, and the laws of Ireland if Customer is located outside of North or
South America or Japan, and the laws of Japan if Customer is located in Japan. All disputes arising out of or in relation to this
Agreement shall be submitted to the exclusive jurisdiction of the courts of Portland, Oregon when the laws of Oregon apply, or Dublin,
Ireland when the laws of Ireland apply, or the Tokyo District Court when the laws of Japan apply. Notwithstanding the foregoing, all
disputes in Asia (excluding Japan) arising out of or in relation to this Agreement shall be resolved by arbitration in Singapore before a
single arbitrator to be appointed by the chairman of the Singapore International Arbitration Centre (SIAC) to be conducted in the
English language, in accordance with the Arbitration Rules of the SIAC in effect at the time of the dispute, which rules are deemed to be
incorporated by reference in this section. Nothing in this section shall restrict Mentor Graphics right to bring an action (including for
example a motion for injunctive relief) against Customer in the jurisdiction where Customers place of business is located. The United
Nations Convention on Contracts for the International Sale of Goods does not apply to this Agreement.
17. SEVERABILITY. If any provision of this Agreement is held by a court of competent jurisdiction to be void, invalid, unenforceable or
illegal, such provision shall be severed from this Agreement and the remaining provisions will remain in full force and effect.
18. MISCELLANEOUS. This Agreement contains the parties entire understanding relating to its subject matter and supersedes all prior
or contemporaneous agreements. Any translation of this Agreement is provided to comply with local legal requirements only. In the
event of a dispute between the English and any non-English versions, the English version of this Agreement shall govern to the extent
not prohibited by local law in the applicable jurisdiction. This Agreement may only be modified in writing, signed by an authorized
representative of each party. Waiver of terms or excuse of breach must be in writing and shall not constitute subsequent consent, waiver
or excuse.
Rev. 151102, Part No. 265968

Dxdesigner Ref

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Dxdesigner Ref

Caricato da

Copyright:

Formati disponibili

PADS Schematic Design Reference

Release PADS VX.2.1

2007-2016 Mentor Graphics Corporation

Mentor Graphics Corporation

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

PADS Schematic Design Reference Manual, PADS VX.2.1 3

Databook Tool - Configure Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

4 PADS Schematic Design Reference Manual, PADS VX.2.1

Settings Dialog Box - Export HDL - Port Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

PADS Schematic Design Reference Manual, PADS VX.2.1 5

Design Entry Tool Command Line Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406

6 PADS Schematic Design Reference Manual, PADS VX.2.1

Verilog HDL Parameters Used as Physical Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472

PADS Schematic Design Reference Manual, PADS VX.2.1 7

8 PADS Schematic Design Reference Manual, PADS VX.2.1

User Interface - Design Entry Tool

PADS Schematic Design Reference Manual, PADS VX.2.1 9

10 PADS Schematic Design Reference Manual, PADS VX.2.1

File Viewer Utility

PADS Schematic Design Reference Manual, PADS VX.2.1 11

Figure 1-3. File Viewer Window

12 PADS Schematic Design Reference Manual, PADS VX.2.1

PADS Schematic Design Reference Manual, PADS VX.2.1 13

14 PADS Schematic Design Reference Manual, PADS VX.2.1

Table 2-1. Design Entry Tool Support Files Listing

PADS Schematic Design Reference Manual, PADS VX.2.1 15

Table 2-1. Design Entry Tool Support Files Listing (cont.)

16 PADS Schematic Design Reference Manual, PADS VX.2.1

Table 2-1. Design Entry Tool Support Files Listing (cont.)

PADS Schematic Design Reference Manual, PADS VX.2.1 17

Table 2-1. Design Entry Tool Support Files Listing (cont.)

18 PADS Schematic Design Reference Manual, PADS VX.2.1

Table 2-1. Design Entry Tool Support Files Listing (cont.)

PADS Schematic Design Reference Manual, PADS VX.2.1 19

Table 2-1. Design Entry Tool Support Files Listing (cont.)

20 PADS Schematic Design Reference Manual, PADS VX.2.1

Support File Reference

PADS Schematic Design Reference Manual, PADS VX.2.1 21

Borders Initialization File Format

Figure 2-1. borders.ini File Content Overview

[ZONE A0SHEETL] (A zone exists for each configured sheet.

22 PADS Schematic Design Reference Manual, PADS VX.2.1

PADS Schematic Design Reference Manual, PADS VX.2.1 23

Table 2-2. borders.ini - ZONE <SHEET_TYPE> Section (cont.)

You need to enter a value as: (value in millimeters) * 100,000.

You need to enter a value as: (value in millimeters) * 100,000.

24 PADS Schematic Design Reference Manual, PADS VX.2.1

Table 2-2. borders.ini - ZONE <SHEET_TYPE> Section (cont.)

You need to enter a value as: (value in millimeters) * 100,000.

You need to enter a value as: (value in millimeters) * 100,000.

PADS Schematic Design Reference Manual, PADS VX.2.1 25

Table 2-3. borders.ini - ANNOTATIONS Section

You can also insert text in the FORMAT specification.

26 PADS Schematic Design Reference Manual, PADS VX.2.1

Bus Contents File Format

$FORMAT_CAR Define header in pre-2007 conts.bc files.

PADS Schematic Design Reference Manual, PADS VX.2.1 27

o Each line of the contents file can have up to 10,000 characters.

28 PADS Schematic Design Reference Manual, PADS VX.2.1

Databook Tool Configuration File Format

<element attribute1="value1" ... > elements' contents </element>

<subelement1> ... </subelement1>

PADS Schematic Design Reference Manual, PADS VX.2.1 29

<subelement2> ... </subelement2>