LM Proc GD

Library ManagerTM Process Guide
DxDesigner to Expedition Flow; Design Capture/DesignView to Expedition Flow Release EXP2005 SPac1
Copyright Mentor Graphics Corporation 2005 - 2006 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 CORPORATION HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. RESTRICTED RIGHTS LEGEND 03/97 U.S. Government Restricted Rights. The SOFTWARE and documentation have been developed entirely at private expense and are commercial computer software provided with restricted rights. Use, duplication or disclosure by the U.S. Government or a U.S. Government subcontractor is subject to the restrictions set forth in the license agreement provided with the software pursuant to DFARS 227.72023(a) or as set forth in subparagraph (c)(1) and (2) of the Commercial Computer Software - Restricted Rights clause at FAR 52.227-19, as applicable. Contractor/manufacturer is: 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: www.mentor.com/supportnet Contact Your Technical Writer: www.mentor.com/supportnet/documentation/reply_form.cfm
TRADEMARKS: The trademarks, logos and service marks ("Marks") used herein are the property of Mentor Graphics Corporation or other third parties. No one is permitted to use these Marks without the prior written consent of Mentor Graphics or the respective third-party owner. The use herein of a thirdparty 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/terms_conditions/trademarks.cfm. This product includes software developed by the Apache Software Foundation (http://www.apache.org/). This product includes software licensed under the Sun Public License. Covered code available upon request. This product includes software developed by the University of California, Berkeley, and its contributors.
Table of Contents
Chapter 1 Library Manager Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Production Flows Supported by Library Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . What is a Central Library?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing a Central Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the WDIR Variable on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adjusting Central Libraries for Use on Linux and UNIX . . . . . . . . . . . . . . . . . . . . Supported Operating Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supporting Mixed Operating System Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Linux and UNIX Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Central Library Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DC/DV to Expedition PCB Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DxDesigner to Expedition Library Manager Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . Process Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Library Manager Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Project Workspace Tree Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Libraries Tab (Project Workspace Tree) . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Object Associations in a Central Library . . . . . . . . . . . . . . . . . . . . . . . . . . Searching/Finding Objects in the Project Workspace Tree . . . . . . . . . . . . . . . . . . . . . Chapter 2 Using Library Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a New Central Library and Selecting a Production Flow . . . . . . . . . . . . . . . Invoking Library Manager, Creating a New Central Library, and Selecting a Flow Type Opening an Existing Central Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Central Library Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subdirectories and Files Created by Library Manager . . . . . . . . . . . . . . . . . . . . . . . Packaging Parts Using a Central Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mapping Expedition Device Data to DxDesigner Device Data . . . . . . . . . . . . . . . . Invoking Library Manager on an Existing Central Library (pre-EXP2005) . . . . . . . . Establishing Common Properties in a Central Library . . . . . . . . . . . . . . . . . . . . . . . . Checking Property Verification Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Central Library Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Symbol Partition from the Menubar . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Cell Partitions from the Project Workspace Tree . . . . . . . . . . . . . . . . . . . Creating a Part Partition from the Project Workspace Tree . . . . . . . . . . . . . . . . . . . Creating Partition Search Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unreserving Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Units Display Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 1-1 1-2 1-3 1-3 1-3 1-4 1-4 1-5 1-5 1-5 1-6 1-6 1-7 1-8 1-11 1-12 1-13 1-15 1-17 2-1 2-1 2-1 2-2 2-4 2-5 2-6 2-8 2-9 2-10 2-11 2-12 2-14 2-14 2-15 2-16 2-17 2-19 2-20
Library Manager Process Guide, EXP2005 SPac1
iii
Table of Contents
Setting Up Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Library Services to Import DC/DV-Expedition Flow Symbols . . . . . . . . . . . . What if a Partition is in Use? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manipulating Objects in the Workspace Tree that are Reserved . . . . . . . . . . . . . . . Deleting Parts, Symbols, Cells, Padstacks and Model Data . . . . . . . . . . . . . . . . . . . Using Library Services to Import DC/DV-Expedition Flow Symbols. . . . . . . . . . . Importing DxD Symbols into a Central Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Symbol Using DC Symbol Editor (DC/DV-Expedition Flow) . . . . . . . . . Creating the 74F244_Half Symbol (DC/DV-Expedition Flow Symbol Editor) . . . Drawing the Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Naming Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding Pin Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding Symbol Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a DxDesigner Symbol Using Symbol Editor (DxD-Expedition Flow). . . . . Creating a 74f244_half Symbol in Dx Symbol Editor . . . . . . . . . . . . . . . . . . . . . . . Setting Symbol Editor Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adjusting Fill Color, Rectangle, Outline Area, and Type . . . . . . . . . . . . . . . . . . . . Adding Pins and Defining Pin Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assigning Pin Numbers and Properties to Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding Device, Package Type and Other Attributes (Dx Symbol Editor). . . . . . . . Renaming a Dx Symbol in the Project Workspace Tree . . . . . . . . . . . . . . . . . . . . . Deleting a Symbol from the Workspace Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Pads, Holes, and Padstacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Surface Mount Padstack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Building a Surface Mount Padstack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Building a Through-Hole Padstack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Associated Pads and Holes in the Workspace Tree . . . . . . . . . . . . . . . . . . Editing Pad and Holes Via the Workspace Tree Viewer . . . . . . . . . . . . . . . . . . . . . Finding Padstack Elements in the Workspace Tree . . . . . . . . . . . . . . . . . . . . . . . . . Creating Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Placing the Pins and Cell Graphics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Cells in the SOIC Partition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Completing the Drawing in Cell Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Parts (Using Part Editor) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining a 74F244 Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assigning Pin Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assigning Alternate Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assigning Pin Names to the Half Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing and Assigning Pin Names to the Full Package . . . . . . . . . . . . . . . . . . . . Assigning Pin Names to the Full Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Model Data (DxD-Expedition Flow) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Model Types in the Workspace Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a New Model File Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing a Model File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a New Model File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing and Editing a Model File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copying a Model File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a Model File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv
2-22 2-23 2-24 2-25 2-25 2-25 2-27 2-29 2-30 2-31 2-32 2-34 2-35 2-36 2-37 2-39 2-42 2-44 2-47 2-50 2-52 2-54 2-55 2-55 2-57 2-58 2-62 2-62 2-63 2-65 2-65 2-67 2-70 2-72 2-74 2-74 2-81 2-83 2-85 2-86 2-88 2-90 2-90 2-91 2-92 2-94 2-95 2-96 2-96
Table of Contents
Using the Modify Pins Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copying Objects in the Workspace Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copying a Padstack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Moving Objects in the Workspace Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Objects and Partitions from the Workspace Tree . . . . . . . . . . . . . . . . . . . . . Using File Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 3 Using PM Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Invoking and Configuring Parts Manager Administrator . . . . . . . . . . . . . . . . . . . . . . Creating a Parametric Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding Parameters to a Parametric Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mapping Properties to Parameters in Parts Manager . . . . . . . . . . . . . . . . . . . . . . . . Adding Properties to Parts Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mapping Properties to Parameters in Parts Manager . . . . . . . . . . . . . . . . . . . . . . . . Applying Parameters from One Parametric Table to Another Table . . . . . . . . . . . . Renaming Parametric Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Parametric Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inserting Parametric Tables from ASCII . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding Part Numbers to the PM Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Part Numbers from the PM Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inserting PPS Data into the PM Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying the Central Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Symbol Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Cell Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Parts Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Library Services to Import Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Library Services to Import Padstacks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Library Services to Import Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Library Services to Import Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Library Services to Import Data from Another Central Library File . . . . . . . Adding Parametric Data to Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing a Parametric Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting Parametric Data to an ASCII File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing Parametric Data from the PM Database . . . . . . . . . . . . . . . . . . . . . . . . . Adding a Parameter to the Parametric Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing Parametric Data into the Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating the Part Number in the PM Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Parts Manager Validation Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Invoking the Parts Manager Validation Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Correcting Problems Detected by the Parts Manager Validation Utility . . . . . . . . . Using the Property Definition Editor to Correct Tolerance Property Problems. . . . Using the Property Definition Editor to Correct Cell Name Property Problems . . . Using the Property Definition Editor to Add Properties. . . . . . . . . . . . . . . . . . . . . . Using PM Administrator to Correct Property Problems. . . . . . . . . . . . . . . . . . . . . . Re-invoking the Parts Manager Validation Utility . . . . . . . . . . . . . . . . . . . . . . . . . .
2-97 2-99 2-101 2-101 2-102 2-103 2-104 3-1 3-1 3-4 3-5 3-8 3-12 3-14 3-15 3-17 3-17 3-21 3-24 3-29 3-33 3-34 3-39 3-41 3-41 3-42 3-43 3-45 3-47 3-49 3-52 3-55 3-55 3-55 3-57 3-62 3-64 3-68 3-70 3-71 3-72 3-72 3-73 3-74 3-77 3-79
Table of Contents
Moving Data Between the PM Database and Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . Using PM Administrator to Create Part Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . Applying Part Number Information to the Parts Database Editor . . . . . . . . . . . . . . Using the Part Editor to Verify Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the PM/PDB Synchronization Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Parts Manager Batch Update Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding Attachment Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding Attachment Data to a Part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Attachment Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding a Description to Attachment Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing PPS Data With Attachment Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exiting / Logging Out of PMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 4 Implementing a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Design Project in Design Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the New Project Wizard to Create a Project. . . . . . . . . . . . . . . . . . . . . . . . . . Creating a New DC/DV Schematic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Linking a Central Library With a Project File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Placing DC/DV Symbols and Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Placing Devices in a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Refreshing the Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connecting Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Compiling and Packaging the DC/DV Schematic . . . . . . . . . . . . . . . . . . . . . . . . . . . . Compiling and Packaging the DC/DV Schematic . . . . . . . . . . . . . . . . . . . . . . . . . . Reviewing Packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Design in DxDesigner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a DxDesigner Project/Linking to Central Library. . . . . . . . . . . . . . . . . . . . . Creating a New DxD Project and Linking to a Central Library . . . . . . . . . . . . . . . . Attaching a Symbol Library to a DxD Project Search Path . . . . . . . . . . . . . . . . . . . . Creating a Schematic Workspace in DxDesigner. . . . . . . . . . . . . . . . . . . . . . . . . . . Adding Symbols to a DxD Schematic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connecting Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Compiling and Packaging the DxD Schematic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Expedition PCB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Invoking Expedition PCB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening a New PCB Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Swapping Gates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pushing from Top Cell to Bottom Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Replacing a Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Reusable Blocks (DC/DV-Expedition Flow) . . . . . . . . . . . . . . . . . . . . . . . Invoking Reusable Block Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Logical/Physical Reusable Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Reusable Block Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing a Reusable Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copying a Reusable Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-79 3-79 3-84 3-88 3-89 3-91 3-97 3-98 3-99 3-100 3-101 3-103 4-1 4-1 4-2 4-3 4-4 4-5 4-6 4-8 4-8 4-9 4-10 4-11 4-11 4-13 4-14 4-14 4-17 4-19 4-20 4-22 4-23 4-24 4-24 4-25 4-27 4-32 4-33 4-34 4-35 4-35 4-36 4-39 4-42 4-42
vi
Table of Contents
Renaming a Reusable Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a Reusable Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 5 Using Other Tools and Library Manager Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Layout Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using IBIS Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Invoking IBIS Librarian . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Invoking Visual IBIS Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using IBIS Functionality in Part Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using IBIS Functionality in Library Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Symbol Editor for DC/DV Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Symbol Editor for DxD Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Padstack Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Library PDF Documenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a User-defined Script or Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening an Existing User-defined Script or Dialog Box . . . . . . . . . . . . . . . . . . . . . . Using DxDatabook Data Editor (DxD-Expedition Flow) . . . . . . . . . . . . . . . . . . . . . . Using the Material / Process Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Appendix A DxD to Expedition Flow Wizards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DxDesigner to Library Manager Migration Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . Invoking the Migration Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specifying a Target Central Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selecting a Migration Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specifying a List of Symbol Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Searching for Symbol Libraries in a Specified Directory. . . . . . . . . . . . . . . . . . . . . Searching DxD Projects for Symbol Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Confirming Migration Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Moving Migrated Symbols to a Different Central Library Partition . . . . . . . . . . . . DxDesigner Project Translation Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Invoking the DxD Project Translation Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selecting DxD Projects to Translate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selecting a Central Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Local Libraries in DxD Projects (Not Translated to a Central Library) . . Appendix B Using Design Architect with Expedition Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Translating a DA Schematic to Expedition PCB. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-44 4-45 5-1 5-1 5-1 5-3 5-4 5-4 5-5 5-6 5-6 5-7 5-7 5-8 5-9 5-11 5-11 5-12 5-12 5-13 5-14 A-1 A-1 A-1 A-1 A-2 A-3 A-5 A-7 A-10 A-13 A-13 A-14 A-14 A-14 A-16 A-18 B-1 B-1 B-1 B-1
vii
Table of Contents
Appendix C Upgrading Central Libraries for Linux and UNIX Use . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Appendix D Using DxDatabook Data Editor in Library Manager . . . . . . . . . . . . . . . . . . . . . . . . What is a DxDatabook User Configuration (*.dbc) File? . . . . . . . . . . . . . . . . . . . . . . Setting Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Parametric Databases on Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . Connecting to Parametric Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating an ODBC Data Source on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using a Configuration (*.dbc) File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a DxDatabook (*.dbc) File (Edit Databook Configuration Command) . . . . Creating a New, Empty DxDatabook Configuration . . . . . . . . . . . . . . . . . . . . . . . . Creating a New DxDatabook Configuration from an Existing Configuration . . . . . Adding Component Libraries to the Configuration (*.dbc) File . . . . . . . . . . . . . . . Adding a Table to a Library Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding Tables to a Library Configuration Using WWW. . . . . . . . . . . . . . . . . . . . . Saving DxDatabook User Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Other Library Configuration Dialog Box Controls . . . . . . . . . . . . . . . . . . . . Viewing Central Library Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing DxDatabook Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Table Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assigning Properties to New Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Database Table Layouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing Database Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing Parametric Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Simple Searches (Search Command) . . . . . . . . . . . . . . . . . . . . . . . . . . Appendix E Library Manager (DxD-Expedition Flow) Limitations. . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Heterogeneous Symbol Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DxDesigner-driven and Part-driven Generic and Non-generic Hetero Devices Supported in the DxD-Expedition Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supporting DxD-Driven Non-generic Hetero Type 3 Symbols . . . . . . . . . . . . . . . . . Export the Part Entry (or Entries) to ASCII . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modify the Part Entry in an ASCII Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing the Modified Part Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supporting DxD-Driven Non-generic Hetero Type 4 Symbols . . . . . . . . . . . . . . . . . Using DxD Symbols (Non-generic Hetero Type 4) . . . . . . . . . . . . . . . . . . . . . . . . . Central Library Parts Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Constraint Editor System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Expedition PCB Pin Swapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Swappable Sub-Gates / PinSets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pin Swap Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
viii
C-1 C-1 C-2 D-1 D-1 D-2 D-2 D-3 D-3 D-8 D-9 D-9 D-11 D-12 D-15 D-25 D-26 D-26 D-27 D-28 D-30 D-30 D-33 D-33 D-35 D-37 D-39 E-1 E-1 E-1 E-2 E-3 E-5 E-6 E-23 E-25 E-25 E-26 E-29 E-30 E-32 E-33
Table of Contents
Part Writer (Hetero Type 2 and/or 4). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unsupported DxD-Expedition Library Manager Flow Scenarios . . . . . . . . . . . . . . . . Appendix F Using DxDesigner for Symbols and Netlist Generation . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the DxDesigner Symbol Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Guidelines for Creating Symbols with DxDesigner (DxD-Expedition Flow). . . . . . . Creating 74f244_half Symbol Using DxDesigner. . . . . . . . . . . . . . . . . . . . . . . . . . . . Naming Pins and Assigning Pin Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding Device, Package Type and Other Attributes . . . . . . . . . . . . . . . . . . . . . . . . Packaging a DxD Schematic Using the Netlist-based Flow . . . . . . . . . . . . . . . . . . . . Appendix G Library Manager Automation Scripting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Custom Scripts and Dialog Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard Automation Interfaces in Library Manager . . . . . . . . . . . . . . . . . . . . . . . . . Glossary Index End-User License Agreement
E-33 E-33 F-1 F-1 F-1 F-2 F-3 F-4 F-9 F-14 G-1 G-1 G-1 G-2
ix
List of Figures
Figure 1-1. DC/DV to Expedition Library Manager Design Flow . . . . . . . . . . . . . . . Figure 1-2. DxDesigner to Expedition Library Manager Flow . . . . . . . . . . . . . . . . . . Figure 1-3. DC/DV-Expedition Flow Using Library Manager . . . . . . . . . . . . . . . . . . Figure 1-4. DxD-Expedition Flow Using Library Manager . . . . . . . . . . . . . . . . . . . . Figure 1-5. Library Manager Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 1-6. Viewing Associated Objects in the Library Navigator Tree. . . . . . . . . . . Figure 1-7. Find Dialog Box (Libraries Tab) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 1-8. Example of Include Associated Object Nodes option (Find Command) . Figure 2-1. Library Manager Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-2. Select a New Central Library Directory Dialog Box . . . . . . . . . . . . . . . . Figure 2-3. Library Navigation Tree with Central Library Defined . . . . . . . . . . . . . . Figure 2-4. Viewing Central Library Properties Using the Popup Menu . . . . . . . . . . Figure 2-5. Property Definition Editor Dialog Box (Cost Property Selected). . . . . . . Figure 2-6. Property Verification Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-7. Partition Editor Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-8. New Cell Partition Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-9. Viewing New Cell Partitions in the Project Workspace Tree. . . . . . . . . . Figure 2-10. New Part Partition Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-11. Viewing a New Part Partition in the Project Workspace Tree . . . . . . . . Figure 2-12. Partition Search Paths Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-13. Unreserve Partitions Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-14. Units Display Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-15. Setup Parameters Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-16. Select a Symbol Library File Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . Figure 2-17. Importing a Symbol Library Using Library Services . . . . . . . . . . . . . . . Figure 2-18. Library Services Dialog Box (Symbols Tab) . . . . . . . . . . . . . . . . . . . . . Figure 2-19. Import Symbols Command in the Project Workspace Tree . . . . . . . . . . Figure 2-20. DxD Symbols Displayed in the Workspace Tree . . . . . . . . . . . . . . . . . . Figure 2-21. Partition Open Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-22. Symbol Editor Interface with 74f244_Half Displayed . . . . . . . . . . . . . . Figure 2-23. Properties Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-24. Naming a Pin on a Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-25. Symbol 74f244_Half With Pins Named . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-26. Symbol Wizard Command from the Workspace Tree . . . . . . . . . . . . . . Figure 2-27. New Symbol Command from the Workspace Tree . . . . . . . . . . . . . . . . Figure 2-28. Properties Section of Dx Symbol Editor. . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-29. Preferences Dialog Box - General (Dx Symbol Editor) . . . . . . . . . . . . . Figure 2-30. Preferences Dialog Box - Appearance (Dx Symbol Editor) . . . . . . . . . . Figure 2-31. Preferences Dialog Box - Save (Dx Symbol Editor) . . . . . . . . . . . . . . .
x
1-7 1-8 1-9 1-10 1-12 1-16 1-18 1-19 2-2 2-3 2-4 2-5 2-12 2-13 2-15 2-16 2-16 2-17 2-17 2-18 2-20 2-21 2-22 2-26 2-26 2-27 2-28 2-29 2-30 2-32 2-33 2-34 2-36 2-37 2-38 2-38 2-39 2-40 2-41
List of Figures
Figure 2-32. Adjusting Fill Color and Background Attributes (Dx Symbol Editor). . Figure 2-33. Corrected Dimensions for 74f244_half Symbol . . . . . . . . . . . . . . . . . . . Figure 2-34. Specifying a Symbol Type Property (Dx Symbol Editor) . . . . . . . . . . . Figure 2-35. Symbol 74f244_half (Left Side Pins) in Dx Symbol Editor . . . . . . . . . . Figure 2-36. Add Pins Dialog Box (Dx Symbol Editor) . . . . . . . . . . . . . . . . . . . . . . . Figure 2-37. Symbol 74f244_half (Left and Right Side Pins) in Dx Symbol Editor . Figure 2-38. Assigning Pin Attributes (Dx Symbol Editor) . . . . . . . . . . . . . . . . . . . . Figure 2-39. Displaying Symbol Attributes (Dx Symbol Editor) . . . . . . . . . . . . . . . . Figure 2-40. Adding Symbol Attributes (Dx Symbol Editor) . . . . . . . . . . . . . . . . . . . Figure 2-41. Symbol 74f244_Half with Pins Defined (Dx Symbol Editor) . . . . . . . . Figure 2-42. Rename Dx Symbol Command from the Workspace Tree. . . . . . . . . . . Figure 2-43. Rename Symbol (Dx) Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-44. Renamed Dx Symbol in Workspace Tree. . . . . . . . . . . . . . . . . . . . . . . . Figure 2-45. Delete Symbol Command from the Workspace Tree . . . . . . . . . . . . . . . Figure 2-46. Padstack Editor Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-47. Padstack Editor Interface (for Surface Mount Padstack) . . . . . . . . . . . . Figure 2-48. Padstack Editor (Holes Tab) With Drill Symbol Graphic . . . . . . . . . . . Figure 2-49. Padstack Editor (Padstacks Tab) With Fields Populated . . . . . . . . . . . . Figure 2-50. Viewing Padstacks in the Workspace Tree. . . . . . . . . . . . . . . . . . . . . . . Figure 2-51. Edit Padstack Popup Menu Command in Workspace Tree . . . . . . . . . . Figure 2-52. Displaying Associated Pads and Holes in the Workspace Tree . . . . . . . Figure 2-53. Editing Pads and Holes from the Workspace Tree . . . . . . . . . . . . . . . . . Figure 2-54. Viewing Padstack Elements in the Workspace Tree. . . . . . . . . . . . . . . . Figure 2-55. Finding a Padstack Element in the Workspace Tree. . . . . . . . . . . . . . . . Figure 2-56. Finding 58 Round Padstack in the Workspace Tree . . . . . . . . . . . . . . . . Figure 2-57. Create Package Cell Dialog Box (Cell Editor) . . . . . . . . . . . . . . . . . . . . Figure 2-58. Pattern Place Tab (Place Pins Dialog Box). . . . . . . . . . . . . . . . . . . . . . . Figure 2-59. Cell Editor Interface (With Ref Des Displayed) . . . . . . . . . . . . . . . . . Figure 2-60. New Cell Command from the Workspace Tree . . . . . . . . . . . . . . . . . . . Figure 2-61. New Cell Dialog Box from the Workspace Tree . . . . . . . . . . . . . . . . . . Figure 2-62. Create Package Cell Dialog Box (Cell Editor) . . . . . . . . . . . . . . . . . . . . Figure 2-63. Place Pins Dialog Box (Cell Editor) . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-64. Cell Editor Interface (With Cell Created) . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-65. Part Editor Dialog Box (With Values Displayed). . . . . . . . . . . . . . . . . . Figure 2-66. Import Dialog Box (Part Editor) With Symbols Tab (DC/DV-Expedition flow) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-67. Import Dialog Box (Part Editor) With Symbols Tab (DxD-Expedition flow) Figure 2-68. Import Dialog Box (Part Editor) With Cells Tab . . . . . . . . . . . . . . . . . . Figure 2-69. Import Dialog Box (Part Editor) With Cells Tab Updated . . . . . . . . . . . Figure 2-70. Pin Names Assigned to Slot #1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-71. Pin Numbers Assigned to Slots. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-72. Assigning Power, Ground, and NC Pins. . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-73. Import Dialog Box (Part Editor) With 74F244_Half Package Displayed Figure 2-74. Import Dialog Box (Part Editor) With 74F244_Half Package Displayed (DxD-Expedition flow). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-42 2-43 2-44 2-45 2-46 2-47 2-48 2-50 2-51 2-52 2-53 2-53 2-54 2-54 2-56 2-58 2-59 2-61 2-61 2-62 2-62 2-63 2-64 2-64 2-64 2-66 2-68 2-69 2-70 2-70 2-71 2-72 2-73 2-76 2-77 2-78 2-79 2-80 2-81 2-81 2-82 2-84 2-85
xi
List of Figures
Figure 2-75. Assigning Pin Names to 74F244_Half Package . . . . . . . . . . . . . . . . . . . Figure 2-76. Import Dialog Box (Part Editor) With 74F244_Full Package Displayed Figure 2-77. Import Dialog Box (Part Editor) With 74F244_Full Package Displayed (DxD-Expedition flow). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-78. Assigning Pin Names to 74F244_Full Package . . . . . . . . . . . . . . . . . . . Figure 2-79. Assigning Default Symbol in the Part Editor . . . . . . . . . . . . . . . . . . . . . Figure 2-80. Part With Associated Symbols and Cells in the Workspace Tree . . . . . Figure 2-81. Models Node in the Workspace Tree (DxD-Expedition Flow) . . . . . . . Figure 2-82. Creating a New Models Partition in the Workspace Tree. . . . . . . . . . . . Figure 2-83. Partitions in the Models Node of the Workspace Tree . . . . . . . . . . . . . . Figure 2-84. Importing a Model File to a Models Partition. . . . . . . . . . . . . . . . . . . . . Figure 2-85. Imported Model File in the Workspace Tree . . . . . . . . . . . . . . . . . . . . . Figure 2-86. New Model File Command in the Workspace Tree . . . . . . . . . . . . . . . . Figure 2-87. View and Edit Model File Commands in the Workspace Tree . . . . . . . Figure 2-88. Copy Model File Command in the Workspace Tree . . . . . . . . . . . . . . . Figure 2-89. Delete Model File Command in the Workspace Tree. . . . . . . . . . . . . . . Figure 2-90. Modify Pins Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-91. Using the Copy Popup Menu Command (Parts in Library Manager) . . Figure 2-92. Copy Padstack Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-93. Move Part Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-94. Delete Popup Menu Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-1. Parts Manager Administrator Software Process Flow . . . . . . . . . . . . . . . Figure 3-2. Parts Manager Administrator Window . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-3. Parts Manager Configuration Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-4. Parametric Tables Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-5. PM Classification Tree With One Undefined Table . . . . . . . . . . . . . . . . . Figure 3-6. PM Classification Tree With Two Undefined Tables. . . . . . . . . . . . . . . . Figure 3-7. Adding a Parameter to a Parametric Table . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-8. Specifying a Parameter in a Parametric Table . . . . . . . . . . . . . . . . . . . . . Figure 3-9. Mapping a Parameter to a Property in a Parametric Table . . . . . . . . . . . . Figure 3-10. Populating a Parametric Table With Parameters . . . . . . . . . . . . . . . . . . Figure 3-11. Property Definition Editor Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-12. Modifying a Property in the Property Definition Editor. . . . . . . . . . . . . Figure 3-13. Mapping a Parameter to a New Property in a Parametric Table. . . . . . . Figure 3-14. Parts Manager Administrator Information Dialog Box . . . . . . . . . . . . . Figure 3-15. Changing a Parametric Table Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-16. Renaming a Parametric Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-17. Renamed Parametric Table in the PM Classification Tree . . . . . . . . . . . Figure 3-18. Renamed Parametric Table in the PM Classification Tree With Message Displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-19. Creating a New Parametric Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-20. Deleting the Test Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-21. Deleting the Memory IC Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-22. Insert Parametric Tables Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-86 2-87 2-88 2-89 2-89 2-90 2-91 2-91 2-92 2-93 2-93 2-94 2-95 2-96 2-97 2-98 2-100 2-101 2-102 2-103 3-3 3-4 3-5 3-6 3-7 3-8 3-9 3-10 3-11 3-12 3-13 3-14 3-16 3-17 3-18 3-19 3-20 3-21 3-22 3-23 3-24 3-25
xii
List of Figures
Figure 3-23. Inserting Parametric Tables into an ASCII File . . . . . . . . . . . . . . . . . . . Figure 3-24. Displaying Successful Parametric Table Insertion into an ASCII File. . Figure 3-25. Displaying Successful Parametric Table Insertion into an ASCII File. . Figure 3-26. Using Create/Update Parametric Data Dialog Box to Manually Add Part Numbers to the PM Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-27. Adding a Parameter and Value to a Parametric Table . . . . . . . . . . . . . . Figure 3-28. Updating Part Number Information in the PM Database . . . . . . . . . . . . Figure 3-29. Deleting a Part Number from the Create/Update Parametric Data Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-30. Selecting Part Number Data for Insertion into the PM Database . . . . . . Figure 3-31. Inserting Part Number Data into the PM Database. . . . . . . . . . . . . . . . . Figure 3-32. Successful Insertion of Part Number Data into the PM Database . . . . . Figure 3-33. Property Definition Editor Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-34. Expanded Property Definition Editor Dialog Box With Cell Name Property Attributes Selected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-35. Partition Editor Dialog Box (Symbols Tab) . . . . . . . . . . . . . . . . . . . . . . Figure 3-36. Partition Editor Dialog Box (Cells Tab) . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-37. Partition Editor Dialog Box (Parts Tab) . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-38. Selecting a Symbol and Associated Data Using Library Services . . . . . Figure 3-39. Importing a Symbol and Associated Data Using Library Services. . . . . Figure 3-40. Selecting Padstacks and Associated Data Using Library Services . . . . . Figure 3-41. Importing Padstacks and Associated Data Using Library Services . . . . Figure 3-42. Selecting Cells and Associated Data Using Library Services. . . . . . . . . Figure 3-43. Importing Cells and Associated Data Using Library Services . . . . . . . . Figure 3-44. Selecting Parts and Associated Part Data Using Library Services . . . . . Figure 3-45. Importing Parts and Associated Part Data Using Library Services . . . . Figure 3-46. Selecting Parts Data to Import from Another Central Library . . . . . . . . Figure 3-47. Importing Parts Data from One Central Library to the Active Central Library Figure 3-48. Selecting a Part Number to Extract from the Database. . . . . . . . . . . . . . Figure 3-49. Extracting a Part Number from the Database to an ASCII File . . . . . . . Figure 3-50. Delete Parametric Tables Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-51. Displaying all Part Numbers in the PM Database. . . . . . . . . . . . . . . . . . Figure 3-52. Selecting a Part Number to Delete from the Logic IC Table . . . . . . . . . Figure 3-53. Deleting a Part Number from the Logic IC Table. . . . . . . . . . . . . . . . . . Figure 3-54. Logic IC Table With Part Number Deleted . . . . . . . . . . . . . . . . . . . . . . Figure 3-55. Adding a Parameter to a Parametric Table . . . . . . . . . . . . . . . . . . . . . . . Figure 3-56. Selecting a Table to Receive Parametric Data . . . . . . . . . . . . . . . . . . . . Figure 3-57. Selecting Part Number Data to Import from an ASCII File . . . . . . . . . . Figure 3-58. Inserting a Part Number into the Logic IC Table . . . . . . . . . . . . . . . . . . Figure 3-59. Successful Part Number Insertion into the Logic IC Table . . . . . . . . . . Figure 3-60. Parameters Associated With a Part Number . . . . . . . . . . . . . . . . . . . . . . Figure 3-61. Part Number With a New Parameter Added to the PM Database. . . . . . Figure 3-62. Tools Menu Showing Parts Manager Validation Command . . . . . . . . . Figure 3-63. Correcting Tolerance Property Problems Using the Property Definition Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-26 3-27 3-28 3-30 3-31 3-32 3-34 3-36 3-37 3-38 3-39 3-40 3-41 3-42 3-43 3-44 3-45 3-46 3-47 3-48 3-49 3-50 3-51 3-53 3-54 3-56 3-57 3-58 3-59 3-60 3-61 3-62 3-64 3-65 3-66 3-67 3-68 3-69 3-70 3-71 3-73
xiii
List of Figures
Figure 3-64. Correcting Cell Name Property Problems Using the Property Definition Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-65. Adding a New Property Using the Property Definition Editor . . . . . . . . Figure 3-66. Enabling the Parts Manager Option in the Property Definition Editor. . Figure 3-67. Setting Up a New Property in the Property Definition Editor . . . . . . . . Figure 3-68. Parametric Tables With Table Changes Saved . . . . . . . . . . . . . . . . . . . . Figure 3-69. Create Parts Numbers from PDB Dialog Box . . . . . . . . . . . . . . . . . . . . Figure 3-70. Part Numbers Associated With the Resistor Partition . . . . . . . . . . . . . . Figure 3-71. Selecting Part Numbers in the Create Part Numbers from PDB Dialog Box Figure 3-72. Creating Part Numbers from PDB Data . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-73. Viewing PPS Data With Part 800-3000000-001. . . . . . . . . . . . . . . . . . . Figure 3-74. Viewing PPS Data With Part 100-1000000-001. . . . . . . . . . . . . . . . . . . Figure 3-75. Error Condition When Updating Part Numbers in the PDB . . . . . . . . . . Figure 3-76. Updating Part Numbers in the PDB from the Create/Update Parametric Data Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-77. Parts Database Editor Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-78. Open Dialog Box (PM/PDB Synchronization Utility) . . . . . . . . . . . . . . Figure 3-79. Parts Manager PM/PDB Synchronization Dialog Box . . . . . . . . . . . . . . Figure 3-80. Verifying Parameters Associated With Part Number 100-1000000-001 Figure 3-81. Reverifying Parameters Associated With Part Number 100-1000000-001 Figure 3-82. Parameters Associated With Part Number 100-1000000-001 After Running PM Batch Update Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-83. Attachment Data Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-84. Attachment Data Dialog Box With Description Field Highlighted . . . . Figure 3-85. Attachment Data Dialog Box With Valid Path Entry . . . . . . . . . . . . . . . Figure 3-86. Attachment Data Dialog Box With Description Field Displayed. . . . . . Figure 3-87. Part Number With Associated Attachment Data . . . . . . . . . . . . . . . . . . Figure 3-88. Importing Part Numbers With Attachment Data . . . . . . . . . . . . . . . . . . Figure 3-89. Part Numbers With Associated Attachment Data (in Blue) . . . . . . . . . . Figure 4-1. Software Tools Process Flow (DC/DV-Expedition Flow) . . . . . . . . . . . . Figure 4-2. Selecting a Schematic Design With the New Dialog Box . . . . . . . . . . . . Figure 4-3. Project Setting Dialog Box (Design Capture). . . . . . . . . . . . . . . . . . . . . . Figure 4-4. Parts Database Dialog Box (Place Device Command) . . . . . . . . . . . . . . . Figure 4-5. Schematic Design in Design Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 4-6. Schematic Design With Wires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 4-7. Selecting a Schematic File in Design Capture . . . . . . . . . . . . . . . . . . . . . Figure 4-8. Completed Schematic Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 4-9. Software Tools Process Flow (DxDesigner-Expedition Library Manager) Figure 4-10. Specifying a DxDesigner Project Name . . . . . . . . . . . . . . . . . . . . . . . . . Figure 4-11. Specifying Central Library Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 4-12. Enabling Expedition Style Zoom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 4-13. Design Configuration Pulldown Menu . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 4-14. Selecting Invoke Project Editor Command (DxDesigner) . . . . . . . . . . . Figure 4-15. Project Editor Search Order Scheme. . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-74 3-75 3-76 3-77 3-78 3-80 3-81 3-81 3-82 3-83 3-85 3-86 3-87 3-88 3-89 3-90 3-92 3-94 3-97 3-98 3-99 3-99 3-100 3-101 3-102 3-103 4-2 4-4 4-5 4-7 4-9 4-10 4-11 4-12 4-14 4-15 4-15 4-16 4-17 4-18 4-18
xiv
List of Figures
Figure 4-16. Changing the Search Order Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 4-17. Project Editor With Symbol Library Search Order Defined. . . . . . . . . . Figure 4-18. Creating a Schematic in DxDesigner . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 4-19. Place Device Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 4-20. Positioning Components in the DxD Schematic. . . . . . . . . . . . . . . . . . . Figure 4-21. DxD Schematic Design With Nets Included. . . . . . . . . . . . . . . . . . . . . . Figure 4-22. PCB Design With Cells U1 and U2 Displayed. . . . . . . . . . . . . . . . . . . . Figure 4-23. Cells With Selected Pins Highlighted . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 4-24. Cells With Pins Selected for Gate Swapping . . . . . . . . . . . . . . . . . . . . . Figure 4-25. Board With All Gates Swapped . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 4-26. ViewPCB Dialog Box (DxDesigner) Running Back Annotation . . . . . . Figure 4-27. ViewPCB Dialog Box (Results tab) with Back Annotation Results . . . Figure 4-28. Board Design With Replaced Cell Defined . . . . . . . . . . . . . . . . . . . . . . Figure 4-29. Reusable Blocks Node in Workspace Tree. . . . . . . . . . . . . . . . . . . . . . . Figure 4-30. Accessing Reusable Blocks (Logical/Physical) Commands from the Workspace Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 4-31. Reusable Blocks Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 4-32. New Reusable Block Dialog Box (Logical/Physical). . . . . . . . . . . . . . . Figure 4-33. Reusable Blocks Dialog Box with Block Name Displayed . . . . . . . . . . Figure 4-34. Logical/Physical Reuse Block in the Workspace Tree . . . . . . . . . . . . . . Figure 4-35. Reusable Block Properties Dialog Box (Invoked from Workspace Tree) Figure 4-36. Edit Reusable Block Command in the Workspace Tree. . . . . . . . . . . . . Figure 4-37. Copying a Reusable Block in the Workspace Tree. . . . . . . . . . . . . . . . . Figure 4-38. Copying a Reusable Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 4-39. Results of Copying a Reusable Block in the Workspace Tree . . . . . . . . Figure 4-40. Renaming a Reusable Block in the Workspace Tree . . . . . . . . . . . . . . . Figure 4-41. Renamed Reusable Block in the Workspace Tree . . . . . . . . . . . . . . . . . Figure 4-42. Deleting a Reusable Block in the Workspace Tree. . . . . . . . . . . . . . . . . Figure 4-43. Reusable Block Removed from the Workspace Tree . . . . . . . . . . . . . . . Figure 5-1. Layout Templates Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 5-2. Library PDF Documenter Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 5-3. Select Script Language Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 5-4. Material / Process Editor (Processes Node) . . . . . . . . . . . . . . . . . . . . . . . Figure 5-5. Material / Process Editor (Materials Node) . . . . . . . . . . . . . . . . . . . . . . . Figure A-1. Selecting or Creating a Target Central Library . . . . . . . . . . . . . . . . . . . . Figure A-2. Selecting a Migration Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure A-3. Specifying a List of Symbol Libraries to Migrate . . . . . . . . . . . . . . . . . . Figure A-4. Confirming Symbol Libraries to Migrate . . . . . . . . . . . . . . . . . . . . . . . . Figure A-5. Searching for Symbol Libraries in a Directory . . . . . . . . . . . . . . . . . . . . Figure A-6. Confirming Directories with Symbol Libraries to Migrate . . . . . . . . . . . Figure A-7. Searching DxD Projects for Symbol Libraries. . . . . . . . . . . . . . . . . . . . . Figure A-8. Confirming DxD Projects to Migrate. . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure A-9. Select DxDesigner Projects to Translate . . . . . . . . . . . . . . . . . . . . . . . . .
4-18 4-19 4-19 4-20 4-21 4-22 4-26 4-28 4-29 4-30 4-31 4-32 4-34 4-35 4-36 4-37 4-37 4-38 4-38 4-40 4-42 4-43 4-43 4-43 4-44 4-45 4-45 4-46 5-2 5-8 5-10 5-12 5-13 A-2 A-4 A-5 A-6 A-8 A-9 A-11 A-12 A-15
xv
List of Figures
Figure A-10. Specifying a Central Library Destination for Translated DxD Projects Figure D-1. ODBC Data Source Administrator Dialog Box . . . . . . . . . . . . . . . . . . . . Figure D-2. Create New Source Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure D-3. ODBC Microsoft Access Setup Dialog Box . . . . . . . . . . . . . . . . . . . . . . Figure D-4. ODBC Microsoft Access Setup Dialog Box with Name and Description Figure D-5. Create New Database Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure D-6. ODBC Data Source Administrator Dialog Box . . . . . . . . . . . . . . . . . . . . Figure D-7. Accessing Edit Databook Configuration Command in Library Manager Figure D-8. New DxDatabook Configuration Dialog Box (Create an Empty Configuration) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure D-9. Central Library Properties Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . Figure D-10. Configure DxDatabook Database Dialog Box . . . . . . . . . . . . . . . . . . . . Figure D-11. New DxDatabook Configuration Dialog Box (Copy an Existing Configuration) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure D-12. Add Library Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure D-13. Library Added to Component Libraries List . . . . . . . . . . . . . . . . . . . . . Figure D-14. Add Table Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure D-15. Data Source Manager Dialog Box (Spawned from Add Table) . . . . . . Figure D-16. Data Source Manager Dialog Box (WWW Option Enabled) . . . . . . . . Figure D-17. Data Source Manager Dialog Box (WWW Data Source Enabled) . . . . Figure D-18. Data Source Manager Dialog Box (Oracle Data Source Enabled) . . . . Figure D-19. Data Source Manager Dialog Box (Oracle Data Source Defined). . . . . Figure D-20. Data Source Manager Dialog Box (ODBC Data Source Enabled) . . . . Figure D-21. Data Source Manager Dialog Box (ODBC Data Source Defined) . . . . Figure D-22. Editing Data Source Names (Data Source Manager Dialog Box) . . . . . Figure D-23. New Table Dialog Box with Data Source (DSN) Populated . . . . . . . . . Figure D-24. Configure Dialog Box With Library Data Displayed . . . . . . . . . . . . . . Figure D-25. Central Library Popup Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure D-26. Company Library Properties Dialog Box . . . . . . . . . . . . . . . . . . . . . . . Figure D-27. DxDatabook Properties Popup Menu Command . . . . . . . . . . . . . . . . . . Figure D-28. DxDatabook Properties (Table) Dialog Box . . . . . . . . . . . . . . . . . . . . . Figure D-29. Parametric Table Properties Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure D-30. New Table Properties Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure D-31. New Table Properties Dialog Box with New Table Name . . . . . . . . . . Figure D-32. Properties Dialog Box with New Table Displayed . . . . . . . . . . . . . . . . Figure D-33. Symbol Library Tab (Properties Dialog Box) . . . . . . . . . . . . . . . . . . . . Figure D-34. Database Layout Tab - Tables Joined Vertically (Properties Dialog Box) Figure D-35. Database Layout Tab - Tables Joined Horizontally (Properties Dialog Box Figure D-36. Accessing Edit Database Tables Command from the Popup Menu. . . . Figure D-37. Viewing Parametric Table Entries in DxDatabook . . . . . . . . . . . . . . . . Figure D-38. Accessing Edit Parametric Data Command from the Popup Menu . . . . Figure D-39. Parametric Data Associated With a Part . . . . . . . . . . . . . . . . . . . . . . . . Figure D-40. Editing Parametric Data in a Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure D-41. Using the Toggle Query Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-17 D-4 D-5 D-6 D-6 D-7 D-8 D-9 D-10 D-10 D-11 D-12 D-13 D-14 D-15 D-16 D-17 D-18 D-19 D-20 D-21 D-22 D-23 D-23 D-24 D-28 D-28 D-29 D-29 D-30 D-31 D-32 D-32 D-33 D-34 D-34 D-36 D-36 D-37 D-38 D-38 D-40
xvi
List of Figures
Figure E-1. IC_OK_1 Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure E-2. IC_OK_2 Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure E-3. IC_OK_3 Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure E-4. Selecting Export ASCII Command in Part Editor . . . . . . . . . . . . . . . . . . Figure E-5. Export ASCII Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure E-6. Part Editor Copy Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure E-7. Import ASCII Dialog Box (Part Editor) . . . . . . . . . . . . . . . . . . . . . . . . . . Figure E-8. Hetero_3 Entry in Part Editor (After ASCII Import) . . . . . . . . . . . . . . . . Figure E-9. DxDesigner Symbol for Full Resistor Package . . . . . . . . . . . . . . . . . . . . Figure E-10. DxDesigner Symbol for Gated Resistor Package. . . . . . . . . . . . . . . . . . Figure E-11. Parts Database Editor Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure E-12. Pin Mapping Dialog Box With Swap Definitions for 2 Pin Symbol . . . Figure E-13. Pin Mapping Dialog Box With Swap Definitions for 8 Pin Symbol . . . Figure E-14. DxDesigner Schematic Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure E-15. Electrical Nets in CES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure E-16. Pin Swapping in Expedition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure E-17. Gate Swapping in Expedition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure E-18. Symbol Group Swapping in Expedition. . . . . . . . . . . . . . . . . . . . . . . . . Figure E-19. Automatic Group/Gate/Pin Swapping in Expedition . . . . . . . . . . . . . . . Figure F-1. DxDesigner Symbol Creation Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure F-2. Symbol 74f244_Half Displayed in DxDesigner . . . . . . . . . . . . . . . . . . . . Figure F-3. Pin Properties Dialog Box (DxDesigner) . . . . . . . . . . . . . . . . . . . . . . . . . Figure F-4. Assigning Pin Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure F-5. Assigning a Second Pin Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure F-6. Symbol 74f244_Half in DxDesigner with First Pin Defined . . . . . . . . . . Figure F-7. 74f244_Half Device in DxDesigner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure F-8. Symbol Properties Dialog Box (DxDesigner) . . . . . . . . . . . . . . . . . . . . . Figure F-9. Symbol Properties Dialog Box (DxDesigner) - One Attribute Assigned . Figure F-10. Symbol Properties Dialog Box (DxDesigner) - Two Attributes Assigned Figure F-11. Symbol Properties Dialog Box (DxDesigner) - All Attributes Assigned Figure F-12. Symbol 74f244_Half with Pins Defined. . . . . . . . . . . . . . . . . . . . . . . . . Figure F-13. ViewPCB Dialog Box (DxDesigner) Running Forward Annotation . . . Figure F-14. Results Tab (ViewPCB Dialog Box) . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure F-15. DxDesigner to Expedition PCB Dialog Box . . . . . . . . . . . . . . . . . . . . . Figure F-16. Expedition PCB Forward Annotation Choice Box. . . . . . . . . . . . . . . . .
E-4 E-4 E-5 E-6 E-6 E-23 E-24 E-24 E-25 E-26 E-27 E-28 E-28 E-29 E-29 E-30 E-31 E-31 E-32 F-2 F-4 F-5 F-5 F-6 F-7 F-9 F-10 F-11 F-12 F-13 F-13 F-15 F-16 F-17 F-17
xvii
List of Tables
Table 1-1. Project Workspace Tree Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 1-2. Search Methods Using Wildcard Characters . . . . . . . . . . . . . . . . . . . . . . . Table 2-1. Mapping Expedition Device Data to DxDesigner Device Data . . . . . . . . Table 2-2. Left Side Pin Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 2-3. Right Side Pin Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 2-4. Assigning Properties to 74f244_half Symbol (Dx Symbol Editor) . . . . . Table 2-5. Valid Model File Name Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-1. Entering Parameters and Values for a Part Number . . . . . . . . . . . . . . . . . Table 4-1. Establishing Project File Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 4-2. Reusable Block Properties Dialog Box Fields and Options . . . . . . . . . . . Table D-1. Database Types Configurable via the Library Wizard . . . . . . . . . . . . . . . Table D-2. ODBC Data Sources and Operating Systems Supported by DxDatabook Data Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table D-3. Library Configuration Dialog Box Controls . . . . . . . . . . . . . . . . . . . . . . Table D-4. Operators and Corresponding Data Types . . . . . . . . . . . . . . . . . . . . . . . . Table D-5. Numeric Comparison Operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table E-1. Supported Hetero Type Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table F-1. Attributes Required for Processing Generic and Non-generic DxD Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table F-2. Left Side Pin Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table F-3. Right Side Pin Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table F-4. Assigning Properties to 74f244_half Symbol . . . . . . . . . . . . . . . . . . . . . . Table G-1. ActiveLibrary Property Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table G-2. Name Property Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table G-3. Version Property Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table G-4. FullName Property Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table G-5. Visible Property Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table G-6. PreviewCell Property Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table G-7. PreviewSymbol Property Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table G-8. OnLMCModify Method Property Status . . . . . . . . . . . . . . . . . . . . . . . . . 1-13 1-18 2-9 2-49 2-49 2-51 2-92 3-32 4-16 4-40 D-2 D-3 D-27 D-40 D-41 E-2
F-2 F-7 F-8 F-12 G-2 G-3 G-3 G-4 G-4 G-5 G-6 G-7
xviii
Chapter 1 Library Manager Overview

Introduction
Library Manager software maintains relationships between data in different libraries by establishing library object associations. A library created by the Library Manager is called a central library and integrates symbols, cells, padstacks, part data, parametric data (DC/DVExpedition flow uses Parts Manager, DxD-Expedition flow uses DxDatabook Data Editor), IBIS models, and layout templates under a single directory structure. The databases controlled by Library Manager are integrated to help control and ensure data reliability throughout the library development process. Library entities, as well as a "common properties" definition file, are integrated to control data reliability throughout the library development process. When a library object is updated, Library Manager software automatically updates related objects within that central library. For example, if you modify a padstack, the software updates all cells that contain that padstack. Since Library Manager integrates this data in a central library scheme, the software also provides the required library editors, utilities, and symbol, cell (footprint), and padstack editors into a single, centralized environment, which can be accessed from a graphical user interface or from within various design tools. Use Library Manager software to perform the following tasks: Launch software tools (editors) to create symbols, cells, padstacks, part data, IBIS models, and layout templates from the Library Manager interface. Define and manage library partitions, which allows grouping of like parts (for example, resistors in one partition, capacitors in a second partition, and so forth). Create custom search path schemes for partitions in the central library. This increases the speed and efficiency of searches and controls the use of non-qualified partitions. For example, assigning a frequently used partition at the top of a search path scheme ensures that the software searches that partition first. Likewise, assigning a user partition at the bottom ensures it will be searched last. Import/export parts, cells, symbols, padstacks, and IBIS models between partitions, libraries, to or from PCB jobs, or to or from ASCII. Create and store standard layout templates with board shape, routing layers, userdefined layers, via size, routing clearances, and so forth for use in subsequent designs.
1-1
Library Manager Overview Production Flows Supported by Library Manager
Create reusable blocks (DC/DV-Expedition flow only) to create circuit blocks and store it in the central library. This allows you to store and utilize verified circuitry with the ease of placing a single element in a design. Define and modify properties that may be common to various library entities (Property Definition Editor dialog box) and control the display and precision of units (Units Display dialog box). The relationship between the data in the different libraries is maintained providing the capability to update associated library objects. For example, modify a padstack and all footprints that contain that padstack are updated to reflect the change.
Production Flows Supported by Library Manager

Library Manager features three product flows that include all the software tools needed to create symbols, cells, and parts. These distinct design flows are based on the type of central library you use: Design Capture/DesignView - Expedition PCB: Using Design Capture or DesignView to create and manage parts, cells, symbols, and padstacks (Windows only), Parts Manager to manage parametric data (Windows only), and IBIS Librarian. Use Expedition PCB to link to a schematic project, compiling a PCB design, placing cells, performing gate swapping, pushing a cell, and replacing a cell. DxDesigner - Expedition PCB: Using Dx Symbol Editor to create and manage symbols (or import symbols from DxDesigner), DxDatabook Data Editor to manage parametric data, and IBIS Librarian or Visual IBIS Editor. Use Expedition PCB to link to a schematic project, compiling a PCB design, placing cells, performing gate swapping, pushing a cell, and replacing a cell. Note If using the DxDesigner to Expedition PCB flow in Library Manager, be sure to read Library Manager (DxD-Expedition Flow) Limitations on page E-1 for important information. See Importing DxD Symbols into a Central Library on page 2-27 for information on importing Dx symbols. Expedition only flow - using Design Architect to create symbols.
See Using Design Architect with Expedition Tools on page B-1 for information on the Design Architect to Expedition PCB flow using Library Manager.
1-2
Library Manager Overview What is a Central Library?
What is a Central Library?

A central library is a collection of interrelated libraries with an improved level of data integrity and consistency checking. A central library contains a library management and control file (.lmc) that maintains an inventory of the contents in the central library. An individual library (one of the sub-folders in the central library) is a collection of partitions. Libraries are the storage locations for parts, cells, symbols, IBIS model software, padstacks, and parametric data (from Parts Manager in the DC/DV-Expedition flow and DxDatabook Data Editor in the DxD-Expedition flow). A partition is a user-defined grouping of data objects. For example, the Cell (footprint) library might be separated into partitions for SMD Cells, Through Cells, Mechanical Cells, and Drafting Cells. The Library Manager interface controls central library creation, partition editing, and invocation of library editors. Designs then reference a central library as a whole rather than inter-mixing library files from various locations.
Accessing a Central Library

More than one user can access a single central library (.lmc) file at a time with different machines. When multiple users access a central library, the partition opened first by a user for editing is write-protected. Other users can access information in that central library partition in read only mode. Once the user editing an entity in a partition has written information to disk and closed that partition, then Library Manager software grants access to another user. Multiple users can edit different partitions in the same central library simultaneously. While not recommended, Library Manager allows multiple central libraries. A central library cannot be created in a directory that contains a central library file (.lmc), a project file (.prj) for the DC/DV-Expedition flow, a design project file (.dproj) for DxD-Expedition flow, or an Expedition PCB file (.pcb). Only one central library is associated with one design. Designs reference one central library as a whole.
Prerequisites
Before using Library Manager, understand your companys library management concept and objectives, be familiar with the software tools (such as Design Capture and DesignView for the DC/DV to Expedition flow on Windows only) and DxDesigner (for the DxD-Expedition Library Manager flow) and Expedition PCB. You must successfully install Library Manager from the appropriate software CD. Installation instructions are included with the software CD. Also, see Configuring the WDIR Variable on Windows for important information.
1-3
Library Manager Overview Prerequisites
Note If using the DxDesigner to Expedition PCB flow in Library Manager, be sure to read Library Manager (DxD-Expedition Flow) Limitations on page E-1 for important information.
Configuring the WDIR Variable on Windows

When you install Library Manager on Windows, the installation prompts you for the location of the WDIR variable. The location you specify during installation is combined with a default location to automatically create the WDIR variable. For example:
E:\wdir;C:\Mentor_EXP2005\2005EXP\SDD_HOME\standard
Caution Do not remove the %SDD_HOME%\standard portion of the WDIR variable on Windows operating systems. Doing so causes problems with the Parts Database Symbol Import, Symbol Preview, and Modify Pins functionality, resulting in a software crash in some cases. Note On UNIX and Linux, the %SDD_HOME%\standard portion of the WDIR is defined and transparent at installation. If you set a WDIR variable manually, the %SDD_HOME%\standard path is automatically appended to the WDIR used by Library Manager and DxDesigner.
Adjusting Central Libraries for Use on Linux and UNIX

The lmcwin2unix script, delivered with Library Manager, adjusts central libraries that were created on the Windows operating system prior to SDD2004 SPac1 for use on the Linux operating system. Therefore, this script is used with the DxDesigner-Expedition PCB flow only. The lmcwin2unix script traverses the directories of a specified central library and adjusts directory names to eliminate case-sensitivity problems that might occur on Linux. For example, the lmcwin2unix script changes a directory named either Sym or SYM to sym (all lowercase text) to ensure operability on Linux. After running this script, the selected central library can be accessed on either Linux, UNIX, or Windows. Linux If you do not run the lmcwin2unix script prior to opening a central library originally created on Windows, the software may generate errors.
1-4
Library Manager Overview Prerequisites
The lmcwin2unix script is located in the following directory and must be invoked from a command prompt:
$<SDD_HOME>/common/linux/bin
See Upgrading Central Libraries for Linux and UNIX Use on page C-1 for complete information on this script.
Supported Operating Systems

Library Manager has been certified to run on the following operating systems for this release: Windows 2000, Service Pack 4 Windows XP Pro, Service Pack 2 Linux WorkStation 3.0 and 4.0 HP-UX 11.0, 11.i (DxD-Expedition flow only) Solaris 8, 9, 10 (DxD-Expedition flow only) Note DC/DV-Expedition Library Manager and DA/BA-Expedition Library Manager is not available on the Linux or UNIX operating systems.
Supporting Mixed Operating System Usage

Central libraries created on the Windows operating system prior to SDD2004 SPac1 must be adjusted for use on both the Linux, UNIX, and Windows operating systems. See Upgrading Central Libraries for Linux and UNIX Use on page C-1 for information on the lmcwin2unix script, which adjusts central libraries that were created on the Windows operating system prior to SDD2004 SPac1 for use on the Linux or UNIX operating system.
Configuring Linux and UNIX Workstations

Configuration information for Linux and UNIX workstations is included in the Release Information document. Consult that document for complete configuration information. Set the following environment variables for Linux and/or UNIX workstations:
SDD_HOME=<install_dir>/2005EXP/SDD_HOME PATH=$SDD_HOME/common/<operating_system>/bin:$PATH
If using the k-shell (ksh) environment on HP-UX 11.0, set the following variable:
export SHLIB_PATH=$SDD_HOME/common/ux11/lib
1-5
Library Manager Overview DC/DV to Expedition PCB Flow
Also, ensure that the LM_LICENSE_FILE points to the license file (Linux and UNIX).
Recommended Central Library Permissions

The company librarian controls access to partitions in a central library and sets the access privileges for numerous purposes. For example, symbols or cells (footprints) which have not been checked and certified for use may be placed into a partition that is inaccessible to designers, and production partitions may be read-only to designers. To disallow individuals from making changes to a central library but still allow Read access for viewing library data, the central library must be loaded on a Windows NTFS, Linux, or UNIX operating system disk. All files, whether they are on Windows, UNIX, or Linux, should have Write permission except for individual library files, which can be write-protected as desired to control access. Note Windows users can use the Properties/Security dialog box and Linux and UNIX users can use the chmod command to adjust central library permissions to corporate guidelines. Files that can be permission-controlled are: Common property (centlib.prp) file Padstack library (padstackDB.psk) file Layout template files Files in the CellDBLibs, IBISModels, PartDBLibs, and SymbolLibs subdirectories. Parts Manager database (partsmanager.mdb) file (DC/DV-Expedition flow only) All other files in the central library should remain Everyone = Change (read-write) to ensure proper operation of the library. The Windows share that allows access to the central library directory from remote machines must have permissions set to Everyone = Full Control. The share permissions are superseded by the individual file permissions.
DC/DV to Expedition PCB Flow

Figure 1-1 on page 1-7 illustrates the DC/DV to Expedition PCB design flow using the central library architecture in Library Manager.
1-6
Library Manager Overview DxDesigner to Expedition Library Manager Flow
Figure 1-1. DC/DV to Expedition Library Manager Design Flow
DxDesigner to Expedition Library Manager Flow

Figure 1-2 on page 1-8 illustrates the DxDesigner to Expedition Library Manager design flow using the central library architecture:
1-7
Library Manager Overview Process Flows
Figure 1-2. DxDesigner to Expedition Library Manager Flow
Process Flows
This process guide describes how to use the Library Manager for both DC/DV to Expedition and DxDesigner to Expedition process flows. Differences in the Library Manager user interfaces and symbol editing processes are explicitly specified within the text. This process guide outlines how to use Library Manager software in an integrated process to create a central library, populate the central library with symbol, cell, and padstack data, and create a simple board layout. The procedures in this process guide illustrate the basics of how to use Library Manager and all related data creation and management tools in an integrated flow. Note See Using Design Architect with Expedition Tools on page B-1 for information on the Design Architect to Expedition PCB flow using Library Manager.
1-8
Figure 1-3 on page 1-9 illustrates the DC/DV-Expedition Library Manager usage flow: Figure 1-3. DC/DV-Expedition Flow Using Library Manager
Figure 1-4 illustrates the DxD-Expedition Library Manager usage flow:
1-9
Figure 1-4. DxD-Expedition Flow Using Library Manager
1-10
Library Manager Overview Using the Library Manager Interface
Using the Library Manager Interface

The Library Manager interface delivers a library-centric environment that illustrates the entire library contents and data. Users access interactive library management tools and data (design) editing software from the menu bar, tool bar, and Library Navigation tree from the Library Manager user interface. The Library Navigation tree identifies the active central library and the contents within partitions (symbols, cells, parts, padstacks) associated with a selected central library. On Windows, for the DxD-Expedition flow, select Start > Programs > Mentor Graphics SDD > DxDesigner-Expedition Flow > Data and Library Management > Library Manager to invoke the Library Manager interface (see Figure 1-5 on page 1-12). For the DC/DVExpedition flow, select Start > Programs > Mentor Graphics SDD > Design Capture DesignView-Expedition Flow > Data and Library Management > Library Manager to invoke the Library Manager interface (see Figure 1-5 on page 1-12). On Linux and UNIX, open a terminal window and type LibraryManager to invoke the Library Manager interface. See Configuring Linux and UNIX Workstations on page 1-5 for information on configuring your Linux workstation. See Invoking Library Manager, Creating a New Central Library, and Selecting a Flow Type on page 2-2 for information on creating a central library and Opening an Existing Central Library on page 2-4 for information on opening an existing central library. Tip: You can also start Library Manager by invoking the LibraryManager.exe executable in the Mentor Graphics software tree. The Library Manager interface can be reduced to an application icon on your desktop which allows you to make more space on your desktop without exiting the software. Note There are also two workflow wizards associated with Library Manager: DxDesigner to Library Manager Migration Wizard on page A-1 DxDesigner Project Translation Wizard on page A-14 See DxD to Expedition Flow Wizards on page A-1 for complete information on invoking and using the DxD to Expedition flow wizards. Library Manager is a launching area for library/project management and design management and editing tools.
1-11
Library Manager Overview Project Workspace Tree Viewer
Tip: Icons on the Library Manager toolbar may vary slightly according to the design flow you are using. For example, the DxD-Expedition flow uses Visual IBIS Editor and the icon appears slightly different in the toolbar. See Using IBIS Software on page 5-3 for more information. The Models node appears in the project workspace tree for the DxDExpedition flow only (see Managing Model Data (DxD-Expedition Flow) on page 2-90). The Reusable Blocks node appears in Library Manager for the DC/DVExpedition flow only (see Managing Reusable Blocks (DC/DV-Expedition Flow) on page 4-35). Figure 1-5. Library Manager Interface
Project Workspace Tree Viewer

The Project Workspace Tree is located by default to the left of the design space. This displays the active central library and all contents within the Parts, Cells, Symbols, and Padstack partitions within that central library. This allows you to view associations between entities within the central library without opening several different editors in the workspace.
1-12
Library Manager Overview Using the Libraries Tab (Project Workspace Tree)
Note Models (SPICE and Verilog) are only supported in DxD-Expedition flow central libraries. Reusable Blocks are supported in the DC/DV-Expedition flow. Therefore, the nodes that appear in the project workspace tree (Figure 1-5) varies depending upon the flow.
Viewing Central Library Properties

Use the Properties command in the Project Workspace Tree to view the directory path to the active central library and confirm the workflow supported by the central library. You will use this functionality later in this document (see Viewing Central Library Properties on page 2-5).
Using the Libraries Tab (Project Workspace Tree)

Use the Libraries tab to create, open, view, edit, and save symbols, cells, parts, padstacks, models (DxD-Expedition flow), and reusable blocks (DC/DV-Expedition flow) within partitions in the selected central library (*.lmc). When you select an entity (cells and symbols) in the tree, the software displays a preview window in the display area. However, if you double click an entity or right click and select Edit from the popup menu, the software opens the appropriate editor for the entity you select. For example, if you double click a symbol, the symbol editor software opens with the selected symbol displayed. Popup menu commands in the Libraries tab allow you to perform object creation and editing tasks without using the toolbar or menubar to access the appropriate editor. For example, highlight a part and right click the Edit popup menu command. The software invokes Part Editor and displays the part you selected in the tool. Files are recognizable by the associated icon and file extension (Table 1-1). Table 1-1. Project Workspace Tree Entities Icon File Extension and Type Parts: *.pdb Process
Double-click a part in the Parts partition. Part Editor software invokes and displays part information for the part you selected from the project workspace tree. See Creating Parts (Using Part Editor) on page 2-74 for more information on Part Editor.
1-13
Table 1-1. Project Workspace Tree Entities Icon File Extension and Type Cells: *.cel Process
Single click a cell in a cell partition and the object displays in a non-editable viewer. Double-click a cell in a cell partition to invoke the Cell Editor software and display the cell you selected from the project workspace tree. This allows you to edit the cell. See Creating Cells on page 2-65 for more information on Cell Editor. Single click a symbol in a symbol partition and the object displays in a non-editable viewer. Double-click on a symbol in a symbol partition to invoke the symbol editor software and display the symbol you selected in the project workspace tree. This allows you to edit the symbol. See Creating a Symbol Using DC Symbol Editor (DC/DV-Expedition Flow) on page 2-29 and Creating a DxDesigner Symbol Using Symbol Editor (DxD-Expedition Flow) on page 2-36 for more information. Double-click a padstack in the Padstacks partition. The Padstack Editor displays with the object you selected from the project workspace tree. See Creating Pads, Holes, and Padstacks on page 2-55 for more information. Select a model file in the Models partition in Library Manager (and DMS Librarian). The Models node displays analog simulation models in Verilog-A and SPICE. While IBIS models are supported with Visual IBIS Editor and IBIS Librarian, these models do not appear in the project workspace tree like other library objects (like symbols, cells, padstacks, and so forth). Supported Model Types: Verilog-A (.va) Compiled Verilog-A (.cml) SPICE (.cir, .ckt, .mod, .spi) Model Types Not Supported: VHDL (.vhd) Encrypted SPICE See Managing Model Data (DxD-Expedition Flow) on page 2-90 for more information.
DxD symbols: <name.#> DC/DV symbols: <name.slb>
Padstacks: *.psk
Models (DxDExpedition flow only) *.va, *.cml, *.cir, *.ckt, *.mod, *.spi Note: Verilog-A and SPICE models with other file name extensions can be imported to the central library.
1-14
Table 1-1. Project Workspace Tree Entities Icon File Extension and Type Reusable Blocks (DC/DVExpedition flow only) Process
Select a Logical/Physical reusable block (DC/DVExpedition flow) associated with the central library. The Reusable Blocks dialog box displays and allows you to create reusable blocks and associate them with projects linked to the active central library (*.lmc) file. See Managing Reusable Blocks (DC/DV-Expedition Flow) on page 4-35 for more information.
Note Partition nodes within part, symbol, cell, padstack, reusable blocks (DC/DV-Expedition flow only), and model partitions (DxD-Expedition flow only) in the project workspace tree are sorted alphabetically by name (case-insensitive). Partition names are compared lexicographically.
Viewing Object Associations in a Central Library

Use the library navigator tree to view associations between entities in a central library instead of invoking the individual point tools to determine associations. This provides a convenient method to view all object associations within a central library (see Figure 1-6). If needed, select Edit from the popup menu to invoke the appropriate editor.
1-15
Figure 1-6. Viewing Associated Objects in the Library Navigator Tree
Pulldown Menu Bar

Library Manager commands are listed on pulldowns available from the menu bar (Figure 1-5 on page 1-12). Click the topic to display a cascading list of library management, design creation
1-16
Library Manager Overview Searching/Finding Objects in the Project Workspace Tree
and manipulation, and user interface control tools. Many of these same commands are accessible via the toolbar.
Toolbar
The toolbar provides one click access to most tools and utilities associated with Library Manager (Figure 1-5 on page 1-12). To determine what tool or utility is associated with a toolbar icon, position your cursor over an icon and a tooltip (label associated with the icon) appears and identifies the associated tool or utility. The status bar (bottom of the Library Manager interface) also displays the tool or utility associated with an icon. Toolbars can be repositioned in the Library Manager interface by dragging the toolbar to the desired location on the interface (called docking).
Searching/Finding Objects in the Project Workspace Tree

Use the Find popup menu command in the project workspace tree to quickly find objects, such as symbols, cells, parts, padstacks, reusable blocks, and models (Verilog and SPICE) within the selected central library (*.lmc) file. Tools on the Find dialog box allow you the option to customize your search by entering object associations related to the object you are searching for in the tree. For example, to find a padstack that is associated to a specific cell, hole, or pad in the tree, use the Object Association options on the Find dialog box.
Invoking and Using the Find Command

1. Highlight a node in the tree, right click the mouse, and select Find from the popup menu. The Find dialog box appears (Figure 1-7). 2. Select the type of object you want to search for in the dropdown box. The dropdown list contains a list of all objects in the active workspace tree (parts, symbols, cells, padstacks, reusable blocks, and models by type). To search for any object in the central library, select Any type of object.
1-17
Figure 1-7. Find Dialog Box (Libraries Tab)
3. Key in the object name in the Name text entry box. You can search on any alphanumeric text string. You can use the asterisk (*) or question mark (?) as a wildcard character to aid in searches by expanding search criteria. Possible search methods using the wildcard characters appear in Table 1-2. Table 1-2. Search Methods Using Wildcard Characters Wildcard Character String ? character? ?character ?character? * character* Description Match one character. Select a single entity that begins with a specified character(s). Select a single entity that ends with a specified character(s). Select a single entity that conforms to a specified character or string. Selects all available entities (zero or match one or more characters). Selects all entities that begin with a specified character (for example, 10* specifies all objects that begin with 10).
1-18
Table 1-2. Search Methods Using Wildcard Characters Wildcard Character String *character Description Selects all entities that end with a specified character (for example, *H specifies all objects that end with H). Selects all entities that conform to a specified character string (for example, *r* returns all objects that have "r" in the string).
*character*
4. Select the Include Associated Object Nodes option to view the object and associations to other objects in the workspace tree. Deselect this option to view only the object (no associations display in the Libraries tab). Figure 1-8 illustrates how using this option to find a symbol in the Libraries tab also displays the associations defined in the central library for the selected symbol object. Figure 1-8. Example of Include Associated Object Nodes option (Find Command)
5. Click OK to execute the search in the Libraries tab.

1-19
6. Click Find Next to find the next matching object in the project workspace tree. Tip: Place the cursor over the highlighted item in the project workspace tree before using the Find Next popup menu command. This ensures the software finds the next object in the library navigator tree that meets the search criteria. Otherwise, the software may not advance to the next applicable object. 7. Click Close to dismiss the dialog box.
Using Find Command to Perform a More Exacting Search

Use the Object Association pulldown to perform a more exacting search for objects in the Libraries tab. Use this option to limit the search to pre-defined object classes. For example, to find a part that uses a specific type of object (for example, a cell or symbol), select an option from the Object Association pulldown, key in the object name, and click OK. This option is disabled if Any Type of Object appears in the Search For dropdown list. Note This procedure assumes you selected a specific type and name of an object to search for in the Find dialog box. 1. Select an object association criteria in the dropdown box and key in the name or number of an object type associated with the displayed object (in the Name field). The list of possible object association criteria is determined by the type of object you selected in the Search For dropdown list. 2. Click OK; the software matches the value you entered against objects in the navigator tree beginning at the node that the Find command was invoked and displays the first object that meets the criteria specified in the Object Association/Name fields. 3. Click Find Next to find the next matching object in the navigator tree. Tip: Place the cursor over the highlighted item in the workspace tree before using the Find Next popup menu command. This ensures the software finds the next object in the library navigator tree that meets the search criteria. Otherwise, the software may not advance to the next applicable object. 4. Click Close to dismiss the dialog box.
1-20
Chapter 2 Using Library Manager

Introduction
This chapter discusses the Library Manager interface and how to use Library Manager and the tools and utilities available from the interface to create a new central library for a DC/DVExpedition or DxDesigner-Expedition flow design, set up parameters for the central library, create a symbol with cell, padstack, and part data. Note See Using Design Architect with Expedition Tools on page B-1 for information on the Design Architect to Expedition PCB flow using Library Manager.
Creating a New Central Library and Selecting a Production Flow

A central library is a collection of interrelated libraries with an improved level of integrity and consistency checking. A central library contains a library control (.lmc) file which maintains and records the contents of the central library. The central library file stores all library data in a single directory structure and consists of one or more libraries depending on the software tools you use (for example, schematic symbol libraries, PCB cells, padstack libraries, and parts). The central library architecture maintains relationships between the data in the different libraries. This provides the capability to verify dependencies across library objects (such as updating all cells that contain a particular padstack after it has been modified). It also allows approval of a design against a central library by verifying that the library objects in a design file match those in the active central library. Note While not recommended, Library Manager allows multiple central libraries. A central library cannot be created in a directory that contains a central library file (.lmc), a project file (.prj) or an Expedition PCB file (.pcb). Only one central library is associated with one design. Designs reference one central library as a whole.
2-1
Using Library Manager Creating a New Central Library and Selecting a Production Flow
Invoking Library Manager, Creating a New Central Library, and Selecting a Flow Type
Use the following steps to invoke Library Manager, select a production flow type, and create a central library: 1. On Windows, for the DxD-Expedition flow, select Start > Programs > Mentor Graphics SDD > DxDesigner-Expedition Flow > Data and Library Management > Library Manager to invoke the Library Manager interface (see Figure 1-5 on page 1-12). For the DC/DV-Expedition flow, select Start > Programs > Mentor Graphics SDD > Design Capture DesignView-Expedition Flow > Data and Library Management > Library Manager to invoke the Library Manager interface (see Figure 1-5 on page 1-12). On Linux and UNIX, open a terminal window and type LibraryManager. See Configuring Linux and UNIX Workstations on page 1-5 for information on configuring your Linux or UNIX workstation. The Library Manager interface displays. Figure 2-1. Library Manager Interface
2. Click File > New to create a central library (.lmc) file. The Select a New Central Library Directory dialog box displays (Figure 2-2).
2-2
Figure 2-2. Select a New Central Library Directory Dialog Box
3. Select the production flow from the Flow Type list in the dialog box (see Figure 2-2). This ensures that Library Manager software creates the appropriate subdirectories and supporting files required to continue processing within the selected flow. The exercises in this document allow you to create a new central library for either the DxDesigner/Expedition flow or the Design Capture/Expedition flow only. Select either one of these options when creating a central library using the procedures in this process guide. Do not select the Design Architect/Expedition flow type. For information on using the Design Architect/Expedition flow, see Using Design Architect with Expedition Tools on page B-1. For additional information on supported production flow types, see Production Flows Supported by Library Manager on page 1-2,
2-3
Note Use the Up One Level icon to navigate to the appropriate directory on your machine. We recommend that, for the exercises presented in this book, you do not create a central library within the Mentor Graphics software tree. 4. Click the Create New Folder icon. The software displays a new folder entry in the directory you specify and prompts you for a new name. 5. Key in the new name for the central library (for this exercise, Company_Library), press the ENTER key, then click OK. The Library Manager Library Navigation tree displays the name of the central library (.lmc) file in the top level (Figure 2-3). Caution For DxDesigner/Expedition flow central libraries, no directory in the path to the central library file can contain more than 32 characters. Figure 2-3. Library Navigation Tree with Central Library Defined
Note Reusable Blocks functionality is only available in the Design Capture/Design ViewExpedition flow central libraries in this release (see Managing Reusable Blocks (DC/DV-Expedition Flow) on page 4-35). Models functionality is only available in the DxDesigner-Expedition flow in this release (see Managing Model Data (DxDExpedition Flow) on page 2-90).
Opening an Existing Central Library

When opening a pre-existing central library file, Library Manager reads the central library and automatically determines which flow it supports (either DC/DV-Expedition or DxDExpedition). If Library Manager cannot automatically determine the flow, the software prompts you to select the desired flow via a dialog box. For DxDesigner/Expedition flow central libraries, no directory in the path to the central library file can contain more than 32 characters.
2-4

Use the Properties popup menu command in the Project Workspace tree to view the directory path to the active central library and confirm the workflow supported by the central library. Use the following steps to view the properties of the active central library (.lmc) file using the Properties command from the popup menu the Project Workspace tree: 1. Right-click the central library name in the Project Workspace tab and select Properties from the popup menu; the central library properties dialog box displays (Figure 2-4). Figure 2-4. Viewing Central Library Properties Using the Popup Menu
The dialog box displays the path to the central library you are using and the workflow assigned to the central library.
2-5
Subdirectories and Files Created by Library Manager

Library Manager software creates the central library directory including the following subdirectories and files. Library Manager requires and utilizes the typical DxDesigner project folder structure and files within the central library to support symbols. The subdirectories created depends on if you are using Library Manager in the Design Capture/DesignView to Expedition flow or DxD-Expedition flow (noted as follows): CellDBLibs - directory that contains all cell (.cel) files managed by the Cell Editor (Creating Cells on page 2-65). Config (generated when using Library PDF Documenter) - directory that contains the libpdf.cfg configuration file which saves the options selected on the Library PDF Documenter dialog box of the job where the central library (.lmc) file is located. See Using Library PDF Documenter on page 5-8 for more information. IBISModels - directory that contains all IBIS Model (.ibs) files (DC/DV-Expedition flow on Windows only). IBIS modeling software supports IBIS Model specification Version 2.1 and, in some cases, Version 3.2. See Using IBIS Software on page 5-3 for more information on IBIS modeling software supported by Library Manager. Note Visual IBIS Editor (which supports both the DC/DV-Expedition and DxD-Expedition flow on all platforms) can store IBIS models anywhere on your machine (and are not controlled by Library Manager). Layout - directory that contains the padstack file PadstackDB.psk. LayoutTemplates - directory that contains all design templates for all jobs. LogFiles - directory that contains log files associated with the central library (.lmc) file processing. See Using File Viewer on page 2-103 for more information. MaterialDBLibs (generated when using Material / Process Editor) - subdirectory created when the Material / Process Editor opens from the Library Manager interface. See Using the Material / Process Editor on page 5-12 for more information. Models ((DxD-Expedition flow only) - subdirectory within a central library that stores Verilog (uncompiled and compiled Verilog A models) and SPICE model data. Models are separated into subdirectories with like type models. While stored as files on disk, some files may contain more than one model. Models display in the workspace tree. See Managing Model Data (DxD-Expedition Flow) on page 2-90. PanelTemplates - If you create a new panel template, this directory contains the <template_name>.pnl file, which is the control file for a Fablink XE job. When you create a new Panel template, the entire Fablink XE job folder is copied to this directory. For more information on Panel templates, consult online help from the Templates dialog box.
2-6
PartsDBLibs - directory that contains part (.pdb) files. See Creating Parts (Using Part Editor) on page 2-74 for more information. PartsManager - (Design Capture/DesignView-Expedition flow only) - directory that contains all parametric tables and data. See Using PM Administrator on page 3-1. pkt (DxD-Expedition flow only) - subdirectory associated with a DxDesigner project. ReusableBlocks - (created when using the Reusable Blocks functionality in the DC/DV-Expedition flow) directory that contains a completed project (.prj) file and schematic(s) (with CDB data) that reflects a given circuit block within a unique subdirectory. The associated Expedition PCB design(s) and all supporting data will also be included within a unique subdirectory. See Managing Reusable Blocks (DC/DVExpedition Flow) on page 4-35 for more information. sch (DxD-Expedition flow only) - subdirectory associated with a DxDesigner project. sym (DxD-Expedition flow only) - subdirectory associated with a DxDesigner project. Linux Appendix C: Upgrading Central Libraries for Linux and UNIX Use on page C-1 includes information on the lmcwin2unix script, which adjusts central libraries that were created on the Windows operating system prior to SDD2004 SPac1 for use on the Linux operating system.
SymbolLibs - directory that contains DC/DV-Expedition flow symbol files. See Creating a Symbol Using DC Symbol Editor (DC/DV-Expedition Flow) on page 2-29. wir (DxD-Expedition flow only) - subdirectory associated with a DxDesigner project. Work - an empty working directory. CentLib.prp file - a file that contains symbol property information. <central_library_name>.dbc - DxDatabook user configuration file. See Using DxDatabook Data Editor in Library Manager on page D-1 for more information. <central_library_name>.lmc - the central library (.lmc) file created earlier in this exercise. See What is a Central Library? on page 1-3 for general information on the central library file. <central_library_name>.dproj (DxD-Expedition flow only) - a central library-specific project used by DxDesigner. When you create a new central library, the *.dproj file inherits the same name as the *.lmc file. <central_library_name>.cfg - a configuration file that stores information on the flow type of the central library. sysindex.cbf - a binary file associated with the central library (.lmc) file.
2-7
viewdraw.ini (DxD-Expedition flow only) - a configuration file used by DxDesigner.
Editing a Central Library Name or Location

If you wish to modify an existing central library (*.lmc) file name or directory path when using Library Manager in the DxDesigner-Expedition flow, the upper-level directory name and the *.lmc file name must be the same. Also, you must manually rename the associated DxDesignerExpedition project (*.dproj) file when renaming the DxDesigner-Expedition flow central library. Settings in the *.dproj file are automatically updated when you reopen the newly renamed central library; however, you must manually rename the *.dproj filename to match accordingly.
Packaging Parts Using a Central Library

The central library uses the Parts Database to store the mapping information between the logical pins of the symbols and the physical pin numbers of the cells. This mapping information is used to: Annotate pin numbers to the components as you place them on the schematic. Refer to the schematic capture software online help to see how this is done in the tool you are using. Process the symbol and map the data to a logical symbol. Pass data forward to Expedition and back annotate changes to the schematic.
Before you assign pin numbers from a central library parts, you must: Import DxDesigner legacy libraries into the central library using the DxDesigner to Library Manager Library Migration Wizard (page A-1). Once the symbols are transferred to the central library, you can create part entries using the Part Editor. The resulting symbol graphics and a file containing pin number assignments can then be accessed from the central library. Specify the path to the central library in the projects design configuration.
2-8
Mapping Expedition Device Data to DxDesigner Device Data

Expedition device data is extracted from the part in DxDesigner. Table 2-1 maps DxDesigner device data to the part data. Table 2-1. Mapping Expedition Device Data to DxDesigner Device Data Expedition Device Data Device Name DxDesigner Data DEVICE/Symbol component attribute value P/D_NUM component attribute value (optional, defaults to DEVICE value) REFDES symbol attribute value Expedition PCB (ASCII Representation) Part Number Expedition Part Editor field Part Number
Part Number
Name
Part Name (optional, name of the part) Reference designator prefix (used as a character prefix for reference designators) Top Cell Name Bottom Cell Name (not used) Alternates
Reference Designator Prefix
RefPrefix
Default Footprint Name Bottom Footprint Name Alternate Footprint Name Symbol Names
PKG_TYPE component attribute value N/A ALT_PKG_LIST component attribute value All symbols in the design sharing a common DEVICE attribute value Symbol Pin Labels
TopCell BottomCell (not included in file) AltCell [one entry per alternate package] Symbol [one entry per device symbol]
Symbol Name
Symbol Pin Names
Symbol_SwapGroup [unique value per device symbol]... PinName [list of symbol pin labels, in symbol pin order]
Logical pins: Pin Name
2-9
Using Library Manager Invoking Library Manager on an Existing Central Library (pre-EXP2005)
Table 2-1. Mapping Expedition Device Data to DxDesigner Device Data Expedition Device Data Pin Swappability DxDesigner Data PINSWAP symbol attribute Expedition PCB (ASCII Representation) SwapGroup SwapID [unique SwapID value for each swappable pin group, in symbol pin order] Expedition Part Editor field Selection of the Swap icon
Device Pin Types Slot Swappability
PINTYPE Symbol pin attributes Determined by matching symbol names. Heterogeneous devices can have multiple symbol names per device
SwapGroupProperties. Pin Type Property ... Prop "Pin Type and Value Slots [one entry per device slot] Slot_SwapGroup [One Slot_Swapgroup per device slot, listing each pin number per slot in symbol pin order. Each swappable slot has a unique Slot_SwapGroup name]
Selection of the Swap icon
The DEVICE attribute is required for a DxDesigner symbol to be mapped into a part number in a part. It identifies the corresponding parts in the part data and associates the schematic symbols with the physical cells using the part number property. The part data enables you to map the same symbol to different parts. It also enables you to map different cells/symbols to a single part and enables you to map the same symbol/cell to different parts. See documentation for the DxDesigner PCB Interface for more information.
Invoking Library Manager on an Existing Central Library (pre-EXP2005)

Note This process guide assumes you are creating a new central library for the DxDesignerExpedition or DC/DV-Expedition flow. However, if you have an existing central library, Library Manager performs transparent operations to update your central library file and directory structure to EXP2005 standards. If you have an existing central library that was created before the EXP2005 release, Use the File > Open command and specify the central library (*.lmc) file in the dialog box. The software automatically determines what flow you are using (based on the symbols in the SymbolLibs
2-10
Using Library Manager Establishing Common Properties in a Central Library
partition) and updates the central library file structure to work within that flow. For example, the software reads the type of symbols that exist in the central library and automatically determines the flow you are using. If no symbols exist in the selected central library, the Select a New Central Library Directory dialog box displays (see Figure 2-2 on page 2-3) and prompts you to select a flow type. If the central library contains mixed symbol types (for example, both DC/DV symbols and DxDesigner symbols), the dialog box displays and prompts you to select the appropriate flow type. Caution For DxDesigner/Expedition flow central libraries, no directory in the path to the central library file can contain more than 32 characters.
Establishing Common Properties in a Central Library

Use the Property Definition Editor to define the available properties and their format in a central library. Use this editor to define new properties, define property types and their associated syntax, and change certain attributes of pre-defined system properties. The values of the properties are stored on the data objects and are not defined in the Property Definition Editor. Note The DxDesigner-Expedition flow does not utilize Common Properties or part dataspecified component properties when creating or placing symbols in DxDesigner. When you create a central library, the software automatically places a default property file (CentLib.prp) into the directory. Tip: Additional information on component type properties is included in Library Manager online help. Use the following steps to establish common properties in a central library using the Property Definition Editor: 1. Select Tools > Property Definition Editor or click the Property Definition Editor icon ; the Property Definition Editor dialog box displays (Figure 2-5). 2. Click the Name header to alphabetize the list of property names in the Property List. If you click the Name header again, the list of property names appears in reverse alphabetical order.
2-11
Using Library Manager Checking Property Verification Settings
Tip: Click any column header in the Property List to organize entries in the list. 3. Select (place a check next to) the Cost property. Figure 2-5. Property Definition Editor Dialog Box (Cost Property Selected)
4. Click OK to save the changes and dismiss the dialog box. This enables the software to place selected properties in a schematic during the packaging process.
Checking Property Verification Settings

Use the Property Verification dialog box to access the Property Verification dialog box. This dialog box displays a list of software products to use in a design process. Placing a check next to the appropriate software tools ensures that library entries meet design requirements and comply with other downstream software tools. For example, if you create a new part using the Part Editor, the Part Name/Number/Label displays in red text which indicates that certain properties required by downstream tools have yet to be added.
2-12
Using Library Manager Checking Property Verification Settings
All tools are selected by default. If your company does not use specific software products listed on this dialog box, then de-select those options. This reduces the amount of error checking performed by the software. If any of these software tools are purchased or used at a later date, select the appropriate options in the Property Verification Settings dialog box to ensure proper verification. Note The following procedure introduces the Property Verification dialog box and its function. For the purpose of this process guide, ensure that the Design Entry and PCB options are enabled. Use the following steps to check property verification settings in the central library: 1. Select Setup > Property Verification or click the Property Verification icon Property Verification dialog box displays (Figure 2-6). Figure 2-6. Property Verification Dialog Box ; the
2. Review the options on the dialog box (all options are selected by default). Select online help for the dialog box to learn more about the options on the dialog box. However, do not change the default settings. Note For DxD-Expedition flow central libraries, the Signal Analyzer / Signal Vision option is disabled. 3. Click Cancel to dismiss the dialog box.
2-13
Using Library Manager Creating Central Library Partitions
Creating Central Library Partitions

Use the Partition Editor to create new symbol, cell, part (formerly Parts Database), and IBIS Model partitions, rename partitions, and remove partitions from a central library. You must create partitions for symbols, cells, and parts using the Partition Editor dialog box before creating symbol, cell, part data, and IBIS model data (see Using IBIS Software on page 5-3 for more information on IBIS software). Partitions are library files that store data within a central library (.lmc) file. The software prohibits removal of a partition that is in use (reserved) by another user or that contains parts. See What if a Partition is in Use? on page 2-24 for more information. Tip: You can create central library partitions using commands from the menubar, icon in the toolbar, or from popup menu commands in the project workspace tab. These methods are illustrated in the following procedures. Information about the number of existing entries in the partition and if that partition is reserved (in use) displays in the Partition Editor dialog box (see Figure 2-7). If the library partition is reserved, other users can access the partition in Read Only mode (no changes are permitted) until it is unreserved (not in use). See Unreserving Partitions on page 2-19 for information on unreserving partitions. Note Data shown in dialog boxes in this document may be slightly different when you use Library Manager.
Creating a Symbol Partition from the Menubar

Use the following steps to create a symbol partition in your central library (.lmc) file using commands from the menubar or icon on the toolbar: 1. Select Setup > Partition Editor or click the Partition Editor icon Editor dialog box displays (Figure 2-7). ; the Partition
2-14
Figure 2-7. Partition Editor Dialog Box
2. Click the New Partition icon , key in Logic Gates (Logic_Gates if you are using the DxDesigner-Expedition flow) for the symbol partition name, and click Apply. The Logic Gates (or Logic_Gates for the DxDesigner-Expedition flow) partition appears in the list of symbol partitions. Tip: You can also create a symbol partition using popup commands from the Project Workspace tab. To create a symbol partition, right-click on the Symbols node in the project workspace and select the New Partition command from the popup menu. To learn more about creating partitions from the project workspace, see Creating Cell Partitions from the Project Workspace Tree on page 2-15.
Creating Cell Partitions from the Project Workspace Tree

Use the following steps to create two cell partitions in your central library (.lmc) file using the New Partition command from the popup menu the Project Workspace tab: 1. Right-click the Cells node in the Project Workspace tab and select New Partition from the popup menu; the New Cell Partition dialog box displays. 2. Key in Dip Thru (Dip_Thru if you are using the DxD-Expedition flow). See Figure 2-8.
2-15
Figure 2-8. New Cell Partition Dialog Box
3. Click OK; the Dip_Thru cell partition is added to the central library. 4. Right-click the Cells node in the Project Workspace tab and select New Partition from the popup menu; the New Cell Partition dialog box displays. 5. Key in SOIC and click OK; the SOIC cell partition is added to the central library. To see the two new cell partitions you added to the central library, expand the Cells node in the project workspace. The Dip_Thru and SOIC partitions associated with the Cells partition in the central library display in the Project Workspace tree (Figure 2-9). Figure 2-9. Viewing New Cell Partitions in the Project Workspace Tree
Creating a Part Partition from the Project Workspace Tree

Use the following steps to create a Part (formerly PDB) partition in your central library (.lmc) file using the New Partition command from the popup menu the Project Workspace tab: 1. Right-click the Parts node in the Project Workspace tab and select New Partition from the popup menu; the New Part Partition dialog box displays. 2. Key in Logic Gates (Logic_Gates if you are using the DxD-Expedition flow). See Figure 2-10.
2-16
Using Library Manager Creating Partition Search Paths
Figure 2-10. New Part Partition Dialog Box
3. Click OK; the Logic Gates (or Logic_Gates) Part partition is added to the central library. To see the new Part partition you added to the central library, expand the Parts node in the project workspace. The Logic Gates (or Logic_Gates) partitions associated with the Parts partition in the central library display in the workspace tree (Figure 2-11). Figure 2-11. Viewing a New Part Partition in the Project Workspace Tree
Creating Partition Search Paths

Each central library (.lmc) file contains the capability to create and manipulate search path schemes for symbol, cell, part data, and IBIS Model partitions (see Using IBIS Software on page 5-3 for more information on IBIS software). A default search path scheme capability, which contains all partitions within the library, is also provided. Select Setup > Partition Search Paths or click the Partition Search Paths icon Partition Search Paths dialog box appears (Figure 2-12). ; the
2-17
Using Library Manager Creating Partition Search Paths
Figure 2-12. Partition Search Paths Dialog Box
A library can have multiple search path schemes. Create custom search path schemes (by clicking the New Scheme icon ) to increase the speed and efficiency of searches. Once you create a search path scheme, enable or disable partitions to allow or disallow their use within point tools (such as design entry software or Expedition PCB). Use options on the Partition Search Paths dialog box to reorder the partitions for each search path scheme by placing a check in the appropriate box and moving them within the list using the arrow icons. For example, if a company has separate domestic and international facilities that use different parts, then create a customized search path scheme for each facility. By putting a frequently used partition at the top of the search path scheme, the software automatically searches that partition first during a part search. The company librarian can grant users permission to alter the search path scheme at the design level by selecting the check box in the Scheme List. Note If you create a new search path scheme for cells while using the Partition Search Paths dialog box in DMS Librarian, the scheme is saved to DMS when you exit the dialog box.
Partition Search Paths Within DC/DV-Expedition Flow Point Tools

Library Manager software applies the "default" search path scheme at the design level when you select a central library for use in a design.
2-18
Using Library Manager Unreserving Partitions
Within Design Capture and DesignView, you can select and alter partition search paths using the Project Settings dialog box (accessible from the Project > Settings command). Within Expedition PCB, you can select and alter partition search paths using the Project Editor dialog box (accessible from the Setup > Project Integration command) and clicking the Edit the Project File icon. Click Cancel to dismiss the Partition Search Paths dialog box.
Unreserving Partitions
Use the Unreserve Partitions dialog box to view partitions that are being edited within a central library (.lmc) file and remove READ/WRITE access to those partitions. Partitions in a central library, such as symbol, cell, part data, and IBIS Model partitions, are considered "reserved" when a user accesses and performs operations within that partition. Other users can connect to that partition with read only access. When the editing node disconnects from a partition, that partition becomes "unreserved" and another node can access and perform editing operations within that partition. If a network disruption, power outage, workstation crash, or similar unexpected anomaly occurs while users access partitions in the central library, the software may not automatically unreserve partitions being edited when the anomaly occurred. Use the Unreserve Partitions dialog box to view these partitions, ensure that no editing operations are in progress, and unreserve them. Upon completion, the software removes the partition from the list meaning that another user can perform editing operations within that partition. Note The following procedure introduces the Unreserve Partitions dialog box and its function. For the purpose of this process guide, do not use this dialog box for this exercise. Use the following steps to access and view the Unreserve Partitions dialog box: 1. Click Setup > Unreserve Partitions or click the icon on the Library Manager interface. The Unreserve Partitions dialog box displays (Figure 2-13).
2-19
Using Library Manager Defining Units Display Settings
Figure 2-13. Unreserve Partitions Dialog Box
Partitions in use would display in this dialog box. You would highlight a partition and click Apply to unreserve the selected partition. 2. Click Close and the Unreserve Partitions dialog box disappears. The Library Manager interface appears.
Defining Units Display Settings

Use the Units Display dialog box to set the precision for electrical and physical properties and time and percentages for all entities in the active central library. Use this dialog box to specify the active electrical units display format. The precision and the display format of the various types of numbers are considered global notation settings. Note The software restricts working units to English (IN and TH) or Metric (MM and UM). The default is English. The precision in all categories specifies the number of decimal places. An example displays at the right of the precision in the Units Display dialog box. The Regional Settings Properties dialog displays the Number tab by default. Options on the Number tab allow you to set several different parameters. Only the following five displayed settings are respected: Decimal Symbol - Allows you to choose which symbol indicates decimal values. No. (number) of digits after decimal - Any units of resolution (such as inches or millimeters) display at the resolution you specify in this drop-down box. Digit grouping symbol - Groups large numbers so they are easily read. For example, a comma digit grouping symbol makes 9,000,000 easier to read than 9000000.
2-20
Using Library Manager Defining Units Display Settings
No. (number) of digits in group - Allows you to adjust the number of digits between grouping symbols. The default is 3. Display leading zeros - Displays leading zeros based on the value entered. By default, this option is set so that leading zeros do not display. Note These settings apply to properties defined as REAL or INTEGER only.
This exercise uses the default units display settings delivered with the software. For additional information on the Units Display dialog box, click online help. Use the following steps to access and view the Units Display dialog box: 1. Click Setup > Units Display or click the Units Display icon dialog box appears (Figure 2-14). Figure 2-14. Units Display Dialog Box ; the Units Display
Do not change the default settings in this dialog box for this exercise. However, use this dialog box to modify notation settings used in a central library (.lmc) file based on your companys requirements.
2-21
Using Library Manager Setting Up Parameters
2. Click Cancel to dismiss the Units Display dialog box.
Setting Up Parameters
Note For the purpose of this process guide, DO NOT change the default settings on the Setup Parameters dialog box. Use the Setup > Setup Parameters command or click the Setup Parameters icon to define parameters for cells that you build using the Cell Editor software. Due to the significance of the settings in the Setup Parameters dialog box, define all cell parameters using this dialog box before using Cell Editor software to create cells. Use the Setup Parameters dialog box (Figure 2-15) to set the default design units, create new user-defined levels, and select a default via for fanouts. Figure 2-15. Setup Parameters Dialog Box
For additional information on the Setup Parameters dialog box, click online help for the Setup Parameters dialog box. Click Close to dismiss the Setup Parameters dialog box.
2-22
Using Library Manager Using Library Services to Import DC/DV-Expedition Flow Symbols
Using Library Services to Import DC/DVExpedition Flow Symbols

Note DxD-Expedition flow users should skip this section and proceed to Importing DxD Symbols into a Central Library on page 2-27. Use Library Services command to manipulate data within a central library (.lmc) file. You can copy, move, and delete parts, cells, symbols, padstacks, and model data: Between central library (.lmc) files. Between partitions in a central library file. Import parts, cells, or padstacks from a PCB design's local libraries into a specified partition in the central library. Import/export ASCII (.txt and .hkp) files. Import symbols from a standalone symbol library file (.slb) into a specified partition in the central library. Import and export processes and materials between central libraries that are developed using the Material / Process Editor (see Using the Material / Process Editor on page 5-12 for more information). Tip: When creating or modifying part data, cells, symbols, padstacks or IBIS Models, save all changes to enable the Library Services software to recognize the new parts. See Using IBIS Software on page 5-3 for more information on IBIS software. Use the Library Services dialog box to import and export parts, cells, symbols, padstacks, and IBIS Models between libraries, from PCB jobs, or to/from ASCII (.txt and .hkp) files and to delete parts, cells, symbols, padstacks and IBIS Models from partitions. Use this dialog box to copy, move, and delete parts, cells, symbols, padstacks, and IBIS Models from partitions in the central library. Note Library Services is accessible from either within the Library Manager environment or from the Setup > Library Services command in Expedition PCB. When importing parts and cells from a library, the software automatically imports all referenced objects. For example, when importing a part data, the software automatically imports the cells, symbols, and padstacks referenced by the part.
2-23
Note When importing parts data, the software copies the referenced symbols to the Temp_Symbol partition and cells to the Temp_Cell partition. When importing or exporting parts and cells from/to ASCII, the software only processes the selected part or cell. Referenced objects are not copied to or from ASCII. For example, when exporting cells to ASCII, the software exports only the cell data. Associated padstacks must be exported separately. When importing cells (or parts that contain cells), the padstacks contained in the cell are automatically imported to the Padstack library. A warning prompt displays for any imported pads, holes, and padstacks that already exist in the target central library. Operations from the attached central library are allowed when invoked from within a local design library. When invoked within a central library, local design databases and other central libraries can be used as the source library during operations. However, the software prohibits exporting library data to a local design's library. Use the Export feature only for exporting to central libraries or ASCII. Each tab in the Library Services dialog box displays the partitions and entries for part data, cells, symbols, padstacks and IBIS Models contained in the central library. Use the options on these tabs to perform various operations with these partitions. Tip: The Import/Export options do not carry over from tab to tab. If you selected an external central library in the Parts tab, then reselect the external library to import/export cells to the external library.
What if a Partition is in Use?

Partitions being accessed by other users display in red text in the Library Services dialog box. The company librarian (administrator for the central library) cannot manipulate partitions until all users have exited that partition. When all users exit a partition, click the Refresh icon to reset the Library Services dialog box. The partition that was in use now appears in the default color. Individual parts, cells, and symbols being accessed by other users also display in red text in the Library Services dialog box. The company librarian cannot move, copy, or delete these entities until all users have terminated access to them. When all users exit these entities, the company librarian clicks the Refresh icon to reset the Library Services dialog box.
2-24
Manipulating Objects in the Workspace Tree that are Reserved

Individual parts, cells, and symbols that appear in the workspace tree which are in a Reserved partition cannot be deleted using the Delete popup menu command. The Delete popup menu command will be disabled for objects that are reserved. To verify a partition is in use, invoke the Partition Editor (see Creating Central Library Partitions on page 2-14). Likewise, the Copy and Move popup menu commands in the workspace tree are also disabled for any object in the workspace tree that is Reserved. If you attempt to copy or move an object from a non-reserved partition to a target partition that is Reserved, the software generates a warning message and prompts you to select a non-reserved partition.
Deleting Parts, Symbols, Cells, Padstacks and Model Data

Use the Display Delete Dialog icon to display the Delete dialog box. Use this dialog box to remove entities in the specified Current Partition. Entities that appear in red text indicate that it is currently in use; therefore, the company librarian cannot delete that entity until other users terminate access to it. Once access is terminated, click the Refresh Library Status icon to reset the Delete dialog box. Note See Using IBIS Software on page 5-3 for more information on IBIS software.
Using Library Services to Import DC/DV-Expedition Flow Symbols

Use Library Services to import two symbols from a symbol library delivered in the software. These symbols will be used later in this process guide. Note The Import Symbols command is also available from the workspace tree viewer. Highlight a symbol partition, right click and select the Import Symbols popup command, and the Import Symbols dialog box displays and prompts you to enter a library, select symbols to import, and select a target partition in the receiving symbol partition. However, in this procedure, use Library Services to import the symbol library. 1. Click the Library Services icon ; the Library Services dialog box displays.
2. Click the Symbols tab to display the Symbols dialog box. 3. Click the Browse icon and the following dialog box displays (Figure 2-16).
2-25
Figure 2-16. Select a Symbol Library File Dialog Box
4. When using the DC/DV-Expedition flow, select Symbol Library files (*.slb) from the Files of Type dropdown box. 5. Browse to the following location and select the symbol library file:
<SDD_HOME>\wg\examples\LibMgrPG.slb
Note If you invoked Library Manager from within Design Capture (DC), browse to the following location and select the symbol library file: \<SDD_HOME>\wg\examples\LibMgrPG.slb 6. Click Open and the two symbols in the LibMgrPG symbol library file display in the Symbols in Import Partition list (Figure 2-17). Figure 2-17. Importing a Symbol Library Using Library Services
2-26
Using Library Manager Importing DxD Symbols into a Central Library
7. Click the Current Partition dropdown box and select Logic Gates. 8. Ensure that Copy displays in the Mode box. 9. Click the Include All icon to move the symbols to the Symbols to Import list (Figure 2-18). Figure 2-18. Library Services Dialog Box (Symbols Tab)
10. Click Apply to import the symbols into the Company_Library.lmc (central library) file. 11. Click Close to dismiss the Library Services dialog box. In summary, you used the Library Services dialog box to import two symbols from a remote symbol library into a symbol partition in the Company_Library.lmc file.
Importing DxD Symbols into a Central Library

DxD-Expedition Library Manager features two methods of importing DxD Symbols:
2-27
Using Library Manager Importing DxD Symbols into a Central Library
Library Migration Wizard (see DxDesigner to Library Manager Migration Wizard on page A-1 for more information) Import Symbols command (click File > Import Symbols or from the workspace tree popup menu for symbols in Library Manager as shown in Figure 2-19). Figure 2-19. Import Symbols Command in the Project Workspace Tree
For this exercise, use the Import Symbols command, available from the workspace tree popup menu, to import DxD symbols into a symbol partition in a central library (.lmc) file. Note Although it is not possible to directly import DxD symbols via Library Services, associated DxD symbols and associated cells are included when importing parts from another central library. The DxD symbols are imported to same-named partition as the source partition. For example, if the part being imported referenced a symbol in the "digital" symbol partition, then the symbol is created in an existing (or newly created) symbol partition in the target Central Library. Associated cells are imported into the "temp_cell" partition. Use the following procedure to import the g244a.1 and 74f244_full.1 symbols into the Logic_Gates partition. 1. Click Symbols in the Library Navigation tree to display the Logic_Gates symbol partition. 2. With the Logic_Gates symbol partition highlighted, right click the mouse and select Import Symbols from the pop-up menu (Figure 2-19). The Select Symbols to Import dialog box displays. Tip: The Import Symbols command is also available from the File pulldown menu.
2-28
Using Library Manager Creating a Symbol Using DC Symbol Editor (DC/DV-Expedition Flow)
3. Browse to the following directory on your machine: \<SDD_HOME>\wg\tutorial\LibMgr 4. Select the g244a.1 and 74f244_full.1 DxDesigner symbols from the dialog box and click Open. The software imports these two symbols into the Logic_Gates symbol partition (Figure 2-20). Figure 2-20. DxD Symbols Displayed in the Workspace Tree
Note These symbols may be read only when delivered to your computer. If you receive errors when importing these symbols, use the Properties dialog box on Windows to remove read only access (change the permissions to full control) for both symbols. On Linux and UNIX, change the permissions associated with these symbols appropriately using thc chmod command.
Creating a Symbol Using DC Symbol Editor (DC/DV-Expedition Flow)

Note If you are using the DxD-Expedition flow, go to Creating a DxDesigner Symbol Using Symbol Editor (DxD-Expedition Flow) on page 2-36. If you ar using the Design Capture/DesignView-Expedition flow, use the Design Capture (DC) Symbol Editor software as instructed in this section. Use the DC Symbol Editor, available from the Library Manager interface, to create a symbol in a specific partition in the central library. Symbols are stored in library files called partitions (that you created in the previous procedure) within the SymbolLibs directory. Use the DC Symbol Editor software to create and edit symbols, open multiple symbol libraries, and edit multiple symbols in a single work session. The file name extension of a symbol library is ".slb."
2-29
Within a central library file, symbols are identified by symbol name in a symbol partition. Each symbol contains an internal time stamp. The library can contain multiple versions of a symbol stored in separate partitions (for example, border.slb, capacitor.slb, and connector.slb). Select Tools > Symbol Editor or click the Symbol Editor icon interface to invoke the DC/DV-Expedition Flow Symbol Editor. in the Library Manager
Note When invoking Library Manager within a point tool (such as Design Capture (DC) or Expedition PCB), only editors that apply to the specific point tool are available. When invoking Library Manager from DC, all editors EXCEPT Cell Editor, IBIS Models, Padstacks, Layout Templates, and Parts Manager are accessible. When invoking Library Manager from Expedition PCB, all editors EXCEPT Symbol Editor and Parts Manager are accessible. Parts Manager is available only from the standalone Library Manager dialog box. Consult Using Symbol Editor for DC/DV Symbols on page 5-6 for additional information. In this procedure, create a 74F244_Half symbol in the symbol partition you created in the central library (.lmc) file.
Creating the 74F244_Half Symbol (DC/DV-Expedition Flow Symbol Editor)

Use the following steps to create a 74F244_Half symbol using the DC Symbol Editor: Tip: The newly created central library (.lmc) file must display in the Central Library text edit field. 1. Click the Symbols (Circuit & Logical) icon to display the Symbol Editor interface. 2. Click File > Open to display the Partition Open dialog box (Figure 2-21). Figure 2-21. Partition Open Dialog Box
3. Select Logic Gates and click OK. The two symbols that display (74F244_Full and g244a) are used later in this exercise.
2-30
Tip: When accessing a partition, that partition and all entities within that partition become "Read Only" to other users. This prevents multiple users from editing the same entity at the same time. After exiting the partition, another user can access and edit entities in that partition. Entries display in alphabetical order in the workspace tree. 4. Click the New Symbol icon ; the New Symbol dialog box displays.
5. Key in 74F244_Half, ensure that the Symbol Type is set to IC, and click OK. The software displays the work area. You create symbols in this work area. Tip: If needed, click the Maximize icon on the workspace window (not the Symbol Editor window) to expand the symbol design display.
Drawing the Symbol

Use the following steps to draw the 74f244_Half symbol in the DC Symbol Editor: 1. Use the commands on the Place toolbar to create the symbol. To place pins on the symbol, use the Place > Line command and add pins using the Place > Pin command. Note Before using the Place > Pin command, click the right mouse button to display the Properties dialog box. Click the Display tab and de-select the Pin Text option. This prevents default pin placement text from appearing in the design when you place pins. Upon completion, the symbol should appear as shown in Figure 2-22:
2-31
Figure 2-22. Symbol Editor Interface with 74f244_Half Displayed
2. Click the right mouse button and select Cancel to exit the Place > Line and Place > Pin commands.
Naming Pins
Use the following steps to name all pins in the schematic using the DC Symbol Editor: 1. Double click on the first pin; the Properties dialog box displays.
2-32
Tip: You can also access the Properties dialog box by double clicking on a pin, clicking on the right mouse button, and selecting the command from the pop-up menu. Or, press ALT + ENTER on the keyboard to access the command. Pin names cannot have a "\" character or an embedded space. 2. Click the Text tab and select Pin Name from the Type list, enter ~G (to type the tilde ("~"), hold the shift key and press the key to the left of the "1" key) in the Value field, and click OK. 3. Click in the workspace to deselect the pin. The Properties dialog box should appear as shown in Figure 2-23: Figure 2-23. Properties Dialog Box
The symbol appears as shown in Figure 2-24:
2-33
Figure 2-24. Naming a Pin on a Symbol
Tip: Use the Place > Text command to add text properties. This command is useful when placing incremental text.
Adding Pin Numbers

Follow these steps to add the remaining pin names, part name, part number, and cost to the symbol: 1. Hold the Shift key, select the four pins on the left side of the symbol, and select the Place Text icon. Pin Name appears in the Type list. If not, select Pin Name from the Type list. 2. Enter A in the Value field and select the Auto increment/decrement option. An increment value of 1 displays in the Value and Delta fields. 3. Click OK; the software automatically numbers all selected pins. Tip: If the text does not display, click the right mouse button and select Properties from the pop-up menu. Select the Display tab, click the Invisible text option, and click OK. 4. Click in the workspace to deselect the pins. 5. Hold the Shift key, select the four pins on the right side of the symbol, and select the Place Text icon.
2-34
6. Enter Y in the Value field and select the Auto increment/decrement option. An increment value of 1 displays in the Value and Delta fields. If not, change the increment Value and Delta to 1. 7. Click OK; the software automatically numbers all selected pins. 8. Click in the workspace to deselect the pins.
Adding Symbol Properties

Use the following steps to add properties to the symbol: Note The Place Text dialog will display data that was used in previous steps. You will need to delete any text in the Value field and deselect the Auto Position option. 1. Select the Place Text icon, select Part Name from the Type/Value list, and click OK. The text attaches to the cursor. Tip: If the text does not display, click the right mouse button and select Properties from the pop-up menu. Select the Display tab, select the Text Placeholders option, and click OK. 2. Place the text under the block. 3. Using the steps you just learned, place Part Number and Cost as shown in Figure 2-25. Click Cancel to dismiss the Place Text dialog box. 4. Move the pin names as shown in Figure 2-25.
2-35
Using Library Manager Creating a DxDesigner Symbol Using Symbol Editor (DxD-Expedition Flow)
Figure 2-25. Symbol 74f244_Half With Pins Named
5. Click on the screen to de-select any selected item and press 5 on the keypad (Num Lock must be off) to refresh the screen. 6. Click File > Save to save the symbol. You are not required to verify the symbol. 7. Click File > Exit to close the 74f224_Half symbol and exit the DC/DV-Expedition Library Manager Symbol Editor.
Creating a DxDesigner Symbol Using Symbol Editor (DxD-Expedition Flow)

Tip: If you are using the Design Capture/DesignView-Expedition flow, use the Design Capture (DC) Symbol Editor software (see Creating a Symbol Using DC Symbol Editor (DC/DV-Expedition Flow) on page 2-29. You can use DxDesigner to create a symbol. See Library Manager (DxD-Expedition Flow) Limitations on page E-1 for more information. However, you can access a Dx Symbol Editor from the Library Manager workspace tree (or toolbar).
2-36
Use the Dx Symbol Editor, available from the Library Manager workspace tree or toolbar, to create a symbol in a specific partition in the central library supporting the DxD-Expedition flow. This symbol is stored in a partition (that you created in the previous procedure) within the SymbolLibs\<partition_name>\sym directory. Use Dx Symbol Editor to create and edit a symbol in the DxD-Expedition flow. For supplemental information on creating symbols in Dx Symbol Editor, consult the online help associated with the software. For general information on Dx Symbol Editor, see Using Symbol Editor for DxD Symbols on page 5-7.
Using the Dx Symbol Creation Wizard

Library Manager features a Dx symbol creation wizard that walks you through the steps of creating a new symbol using the Dx Symbol Editor. However, to familiarize you with tools and options in the Dx Symbol Editor, the exercises in this process guide instruct you how to use the tools in the software application to create a new symbol. Use the following steps to access the Dx Symbol Creation Wizard: 1. Right-click an existing symbol partition in the project workspace tree and select Symbol Wizard from the popup menu (Figure 2-26). Figure 2-26. Symbol Wizard Command from the Workspace Tree
The first page of the Dx Symbol Creation Wizard appears. 2. Complete the required entries in the Symbol Creation Wizard dialog boxes. Upon completion, the software creates a Dx symbol to the specifications entered via the wizard. Consult online help associated with the Dx Symbol Creation Wizard for more information.
Creating a 74f244_half Symbol in Dx Symbol Editor

Use the following processes to create a 74f244_half symbol in the Dx Symbol Editor:
2-37
1. Select the Logic_Gates partition (Symbol Partition) in the workspace tree and select New Symbol from the popup menu (Figure 2-27). Figure 2-27. New Symbol Command from the Workspace Tree
The New Symbol dialog box appears. Tip: To invoke Dx Symbol Editor from the menubar, select the Logic_Gates partition in the Navigator Tree and click Tools > Symbol Editor (for DxDesigner symbols). You can also invoke DxDesigner Symbol Editor using the Symbol Editor icon on the toolbar. 2. Key in the following symbol name in the New Symbol dialog box. 74f244_half Tip: In the DxDesigner - Expedition flow, symbol names cannot contain spaces or special characters. Log files containing errors generated by the Dx Symbol Editor are written to the LogFiles directory for the active central library. 3. Click OK; the Dx Symbol Editor work area displays (Figure 2-28). Note that the symbol partition and name appears in the Properties section of the symbol editor interface. The symbol type is not set by default (but you will set it later in this chapter). Figure 2-28. Properties Section of Dx Symbol Editor
2-38
Setting Symbol Editor Preferences

When the Dx Symbol Editor workspace displays, use the Preferences dialog box to set default characteristics for the symbol editing environment before creating a symbol. For example, you can adjust grid spacing and pin length and spacing characteristics, enable an Autosave feature, and adjust the font size used for graphics and associated labels. 1. Click File > Preferences in the Dx Symbol Editor to view available settings. The Preferences dialog box appears (Figure 2-29). Figure 2-29. Preferences Dialog Box - General (Dx Symbol Editor)
2. Adjust the grid visibility, grid spacing, pin length, and pin spacing in the grid using controls in the dialog box. For the purposes of this process guide, use the settings in Figure 2-29. Click Apply to save the changes.
2-39
Tip: Click the Crosshair cursor visible to enable the crosshair cursor within Dx Symbol Editor. The crosshair position refreshes as you move the cursor. The status field in Dx Symbol Editor indicates the exact coordinates of the cursor as it moves. This allows more precise editing control when creating or editing a symbol. The Dx Symbol Editor can be set to use either English or Metric units of measure (Figure 2-29). 3. Click Appearance and the Preferences dialog box provides tools to adjust the display of elements in the console window and symbol window (Figure 2-30). For example, to adjust the font settings for pin labels that appear in the Symbol Window, select the Pin Label Font subcategory. Tools are available in the dialog box to adjust font size, color, and style. Figure 2-30. Preferences Dialog Box - Appearance (Dx Symbol Editor)
2-40
Tip: Click Default at any time to return settings in the Preferences dialog box to the default settings. 4. Click Save in the Preferences dialog box. This provides tools to customize automatic save intervals used by the Dx Symbol Editor (Figure 2-31). Figure 2-31. Preferences Dialog Box - Save (Dx Symbol Editor)
5. Use Enable autosave to save the active Dx symbol to disk at regular intervals defined in the Autosave delay in minutes selection box. Set this option to meet your requirements. Note Enable the Skip Graphics Attributes option to use default colors and fonts from the editing environment in which the symbol is opened. Enable the Save Default Graphics Attributes option to always use the default colors and fonts for the symbol assigned by the Dx Symbol Editor. For example: Settings in Dx Symbol Editor: Default Text Font = Kanji, Default Text Color = Red Settings in DxDesigner: Default Text Font = Roman, DefaultText Color = Yellow Symbol saved with Skip Graphics Attributes option enabled - In DxDesigner, the symbol text is yellow and uses Roman font. Symbol saved with Save Default Graphics Attributes option enabled - In DxDesigner, the symbol text is red and uses Kanji font. 6. Click OK to save all settings and dismiss the Preferences dialog box. Caution Before performing the next step, save symbol designs to the sym folder of your central library symbol partition. This ensures the symbol design is saved to the appropriate location in your central library directory structure. 7. Click File > Save to save your settings.
2-41
Adjusting Fill Color, Rectangle, Outline Area, and Type

By default, the Symbol Editor displays a template with a symbol outline area in the workspace area. The symbol origin is located at the bottom left of the symbol outline area by default. Adjust the fill (background) color and symbol rectangle areas before creating the 74f244_half symbol.
Setting Fill Color

By default, the symbol fill color is transparent when you invoke the Dx Symbol Editor. However, you can set this parameter using settings in the Properties table. For the purposes of this process guide, use the default Fill Color setting. 1. Click the edge of the symbol rectangle area. The symbol attributes update to display default settings. 2. Note the default settings for Fill Color and Outline Color symbol attributes in the Properties table (Figure 2-32). Figure 2-32. Adjusting Fill Color and Background Attributes (Dx Symbol Editor)
Adjusting Rectangle Size and Dimensions

Adjust the symbol rectangle size and dimensions using the following steps: 1. Click the symbol rectangle and ensure the rectangle highlights. 2. While holding the mouse button, adjust the dimensions of the symbol rectangle to match that shown in Figure 2-33. Tip: If needed, click Zoom In grid points. to improve visibility of the symbol rectangle and
The symbol rectangle should match Figure 2-33:
2-42
Figure 2-33. Corrected Dimensions for 74f244_half Symbol
Specifying Symbol Type Attribute

When creating a new symbol in the Dx Symbol Editor, the default symbol type is UNKNOWN until you specify otherwise. Use the following steps to assign a symbol type attribute for the 74f244_half symbol: Note If needed, click outside the symbol outline area to refresh the list of symbol properties (right pane of the Dx Symbol Editor). 1. Select the Symbol Type attribute and enable the dropdown list to view the list of valid symbol types (Figure 2-34).
2-43
Figure 2-34. Specifying a Symbol Type Property (Dx Symbol Editor)
2. Select MODULE from the dropdown list. Ensure that MODULE is the Value associated with the Symbol Type property (attribute). 3. Click File > Save to save all changes to the symbol. Tip: For some types of attributes, use the Symbol > Symbol Attributes command to add standard property type attributes.
Adding Pins and Defining Pin Attributes

Add pins to the symbol and define their attributes using the following steps: 1. Click Symbol > Add Pin command or Symbol > Add Pin and Edit pins on the left side of the symbol as shown in Figure 2-35. and insert
As you insert each pin, key in the text and press Return to place you back into Place Symbol with Label mode. For example, for the first pin, use the Add Pin and Edit command to place the pin, then key in ~G to name the pin, and press Return to place you back to Place Pin with Label mode. 2. Repeat Step 1 until the symbol resembles Figure 2-35. Tip: Click the Select Mode icon needed. to clear the Place Pin and Label command, if
2-44
Figure 2-35. Symbol 74f244_half (Left Side Pins) in Dx Symbol Editor
Next, place pins on the right side of the symbol using the Add Pins dialog box. The Add Pins dialog box lets you predefine pin attributes within a symbol before placement. 3. Click Symbol > Add Pin Array; the Add Pins Array dialog box displays with default settings. Use the dialog box to place pins on the right side of the symbol. Use settings that appear in Figure 2-36:
2-45
Figure 2-36. Add Pins Dialog Box (Dx Symbol Editor)
4. Click OK; the symbol editor places pins along the right side of the pin. 5. Using the mouse, click on and drag and drop the pins into the appropriate position on the symbol. Upon completion, the symbol should appear similar to Figure 2-37. Ensure the right side pins are aligned with the left side pins.
2-46
Figure 2-37. Symbol 74f244_half (Left and Right Side Pins) in Dx Symbol Editor
Tip: The Symbol Editor allows you to rotate and align one pin at a time. Click Symbol > Edit Selection to view the rotation and alignment commands that apply to pins in a Dx schematic.
Assigning Pin Numbers and Properties to Pins

Once you have placed the pins, use the Dx Symbol Editor to assign properties and attributes to the pins on the symbol. 1. Click the first pin ~G (upper left in the design); the Pin Property attributes update in the Property table within the Dx Symbol Editor.
2-47
Note Ensure that the Label value in the Property table is ~G. If you do not see the pin-list window on left side of Symbol Editor user interface, drag the separator down until it appears. 2. Click New attribute to enable the software to add a new property and assign it to the pin. 3. Type # in the Property column to assign a pin number property and enter 1,19 in the Value column. Tip: To delete an attribute, click the Delete icon in the associated Value column.
4. Click any field in the Properties table and click File > Save to save the pin number attributes you just entered. The Properties table should appear as shown in Figure 2-38. Figure 2-38. Assigning Pin Attributes (Dx Symbol Editor)
Note The checkboxes adjacent to the Pin and # properties and values control visibility within the symbol. To make a property and/or value visible within the symbol, select the checkboxes. For this exercise, do not enable visibility for these properties and values.
2-48
5. Repeat Steps 2 through 5 to add pin numbers to the remaining pins in the symbol. Use the pin names and attributes as instructed in Table 2-2 and Table 2-3: Table 2-2. Left Side Pin Attributes Pin Name A1 Property and Value Label = A1 # = 2,11 Port Type = IN Inverted = False Length = 20.000 Label = A2 # = 4,13 Port Type = IN Inverted = False Length = 20.000 Label = A3 # = 6,15 Port Type = IN Inverted = False Length = 20.000 Label = A4 # = 8,17 Port Type = IN Inverted = False Length = 20.000 Enable Visibility? Yes No
A2
Yes No
A3
Yes No
A4
Yes No
Table 2-3. Right Side Pin Attributes Pin Name Y1 Property and Value Label = Y1 #= 18,9 Port Type = OUT Inverted = False Length = 20.000 Label = Y2 # = 16,7 Port Type= OUT Inverted = False Length = 20.000 Enable Visibility? Yes No
Y2
Yes No
2-49
Table 2-3. Right Side Pin Attributes Pin Name Y3 Property and Value Label = Y3 # = 14,5 Port Type = OUT Inverted = False Length = 20.000 Label = Y4 # = 12,3 Port Type = OUT Inverted = False Length = 20.000 Enable Visibility? Yes No
Y4
Yes No
Adding Device, Package Type and Other Attributes (Dx Symbol Editor)
Use the following steps to add device, package type, and other required information to the symbol: 1. Press Esc (Escape) or click the Select Mode icon mode. to clear any active command
2. Click in the symbol design to refresh the Property editor (right side of the symbol editor). The Property editor should appear similar to Figure 2-39: Figure 2-39. Displaying Symbol Attributes (Dx Symbol Editor)
3. Click New attribute.....; the editor creates a new property entry field. 4. Type DEVICE in the Property field, key in 100-100000-001 in the Value field. Ensure the visibility check boxes are not selected (see Figure 2-40).
2-50
Figure 2-40. Adding Symbol Attributes (Dx Symbol Editor)
5. Click New attribute..... and then click File > Save to save the property and attribute you just entered. Note If a symbol is only intended for use in the DxDesigner-Expedition flow, only the DEVICE ane REFDES attributes are required. The PKG_TYPE attribute is optional but, if provided, is used by the cell previewer in Cell Editor. The HETERO and PARTS attributes are not required since they are part of the part (PDB) mapping. Pin numbers are not required. However, if you plan to use the symbol in DxDesigner to a third-party flow or from DxDesigner in the DxD-Expedition flow, then all attributes in Table 2-4 are required. 6. Using the process documented in Steps 3 through 5, enter the properties and attributes provided in Table 2-4 in the dialog box. The software adds these properties to the list in alphabetical order: Table 2-4. Assigning Properties to 74f244_half Symbol (Dx Symbol Editor) Property Value Enable Visibility? No No No No
PKG_TYPE 20_PIN_SOIC HETERO PARTS SIGNAL LOGIC:G244A, (LOGIC:74F244_FULL), (LOGIC:74F244_HALF) 2 GND;10, VCC;20
7. Click File > Save to save all changes. The Property editor should appear similar to Figure 2-41:
2-51
Figure 2-41. Symbol 74f244_Half with Pins Defined (Dx Symbol Editor)
8. Click File > Close to dismiss the 74f244_half symbol and File > Quit to exit the DxD Symbol Editor. The Library Manager interface continues to display. Tip: Three attributes that can be defined more than once in the DxD Symbol Editor: NC, SIGNAL, and PINSWAP.
Renaming a Dx Symbol in the Project Workspace Tree

Note Do not rename the 74f244_half, g244a, or 74f244_full symbols in the Logic_Gates partition. This discussion describes the functionality of renaming a Dx symbol in a central library. A Dx symbol that appears in the project workspace tree can be renamed and saved to the active central library using the Rename popup menu command. To rename a symbol: 1. Right-click the symbol you want to edit and select the Rename popup menu command (Figure 2-42).
2-52
Figure 2-42. Rename Dx Symbol Command from the Workspace Tree
The Rename Symbol dialog box appears with the current symbol name displayed in the text edit field (Figure 2-43). Figure 2-43. Rename Symbol (Dx) Dialog Box
2. Key in the new Dx symbol name (for example, ok_ic_working) and click OK. The symbol is renamed in the central library (Figure 2-44). The software automatically updates symbol name references of all Parts within the central library that reference the symbol to reflect the new name.
2-53
Figure 2-44. Renamed Dx Symbol in Workspace Tree
Deleting a Symbol from the Workspace Tree

A symbol that appears in the project workspace tree can be removed from the active central library using the Delete popup menu command. To delete a symbol: 1. Right-click the symbol you want to edit and select the Delete popup menu command (Figure 2-45). Figure 2-45. Delete Symbol Command from the Workspace Tree
The symbol you highlighted is removed from the workspace tree and from the central library.
2-54
Using Library Manager Creating Pads, Holes, and Padstacks
Copying and Moving Symbols in the Workspace Tree

Central library objects, such as symbols, can be copied and moved using popup menu commands in the workspace tree. See Copying Objects in the Workspace Tree on page 2-99 and Moving Objects in the Workspace Tree on page 2-101 for more information.
Creating Pads, Holes, and Padstacks

Use the Padstack Editor to create pads, holes, and padstacks in the appropriate partition of the central library (.lmc) file. Use the following procedures to create pads, holes, and padstacks for use in a cell that you will build later. See Using Padstack Editor on page 5-7 for general information.
Creating a Surface Mount Padstack

Use the following steps to create a surface mount padstack: 1. Click the Padstack Editor icon on the Library Manager interface or click Tools > Padstack Editor; the Padstack Editor dialog box displays. Tip: You can also invoke and use the Padstack Editor from the Padstacks node in the project workspace. Right-click on a Padstack type, select New Padstack from the popup menu, and key in the new padstack name.
The Padstack Editor dialog box appears with the new padstack name and the correct Padstack Type selected by default in the dialog box. Padstack names are ordered alphabetically in the workspace tree.
2-55
2. Click the Pads tab to create a new Surface Mount pad (Padstack Type is Pin - SMD). 3. Click the New Pad icon and click Rectangle from the Properties area. The Pad Parameters area displays text entry fields for width and length properties. 4. Key in 24 for width, 70 for length, and press Enter. The Preview window displays the surface mount pad according to these dimensions (Figure 2-46). Figure 2-46. Padstack Editor Interface
Note Ensure that Rectangle 70x24 appears in the Names field and is selected.
2-56
Building a Surface Mount Padstack

Use the following steps to build a surface mount padstack in the design: 1. Click the Padstacks tab, click the New Padstack icon name: 24x70 Rectangle Note Ensure that Pin - SMD displays in the Type field within the Properties section of the dialog box. 2. Highlight Rectangle 70x24 from the Available Pads list. 3. Highlight the Top Mount field from the Pads list and click the left arrow icon. Rectangle 70x24 displays in the Pads list (adjacent to Top Mount). 4. Highlight the Bottom Mount field from the Pads list and click the left arrow icon (Figure 2-47). Tip: You can highlight both fields by pressing the Ctrl key, clicking on the Top Mount and Bottom Mount fields, selecting a pad from the Available pads list, and then clicking the left arrow icon. The software populates both fields. and key in the following
2-57
Figure 2-47. Padstack Editor Interface (for Surface Mount Padstack)
5. Click File > Save to save the finished surface mount padstack.
Building a Through-Hole Padstack

Use the following steps to create a through-hole padstack: 1. Click the Holes tab and click the New Hole icon. 2. Key in 38 in the Diameter text entry field and press Enter. 3. Using the Assignment Method dropdown box, select the Use Drill Symbol from List option (in the Drill Symbol Assignment box). 4. Select the drill symbol as shown in Figure 2-48:
2-58
Figure 2-48. Padstack Editor (Holes Tab) With Drill Symbol Graphic
Note This drill symbol graphic appears in the PCB layout when using the Output > NC Drill command in Expedition PCB.
Building a Pad
Use the following steps to finish building the pad: 1. Click the Pads tab and click the New Pad icon. 2. Key in 58 for the diameter and press Enter. 3. Click the New Pad icon, select Square, key in 58, and press Enter.
Defining Padstacks
1. Select the Padstacks tab, click the New Padstack icon 2. Select Pin - Through in the Type field. , and key in 58 Round.
2-59
3. Highlight Round 58 in the Available Pads list and move it into the Mount Side, Internal, and Opposite Side fields in the Pads list. Tip: You can highlight Mount Side, Internal, and Opposite Side fields by holding and dragging the left mouse button to highlight the individual fields, then click the left arrow button to move Round 58 to the highlighted areas in the Pads list. 4. Highlight Rnd 38 in the Available Holes list. The Preview window updates with the new hole. 5. Click the New Padstack icon and key in 58 Square.
6. Select Pin - Through in the Type dropdown box. 7. Highlight Square 58 in the Available Pads list and move it into the Mount Side and Opposite Side entries of the Pads list. 8. Highlight Round 58 in the Available Pads list and move it into the Internal entry of the Pads list. 9. Highlight Rnd 38 in the Available Holes list. 10. Select Square 58 in the Mount Side field (Pads list). The Preview window displays the new padstack (Figure 2-49). Note Colors that appear in the Preview window may be slightly different depending upon color settings on the workstation.
2-60
Figure 2-49. Padstack Editor (Padstacks Tab) With Fields Populated
11. Click File > Save to save the design and create the padstacks. The padstacks appear in the appropriate Padstacks node in the project workspace viewer (Figure 2-50). Figure 2-50. Viewing Padstacks in the Workspace Tree
Tip: To invoke the Padstack Editor on any padstack in the workspace tree viewer, rightclick the padstack and select the Edit popup menu command (Figure 2-51).
2-61
Figure 2-51. Edit Padstack Popup Menu Command in Workspace Tree
12. Click File > Exit to dismiss the Padstack Editor.
Viewing Associated Pads and Holes in the Workspace Tree

Use the project workspace tree to view the associated pads and holes associated with the padstacks you just created. This provides a convenient way to view all pads and holes associated with a padstack without executing the Padstack Editor software within Library Manager. For more information, see Viewing Object Associations in a Central Library on page 1-15. Click 58 Square in the Pin - Through padstack element. The associated pads and holes display in the workspace tree (Figure 2-52). Figure 2-52. Displaying Associated Pads and Holes in the Workspace Tree
Note that the Associated Pads and Associated Holes match the settings in the Padstack Editor (see Figure 2-49 on page 2-61).
Editing Pad and Holes Via the Workspace Tree Viewer

While viewing pads and holes associated with a padstack in the workspace tree viewer, use the Edit popup menu command to view the pad or hole in the Padstack Editor. This opens the selected pad or hole in the Padstack Editor (Figure 2-53).
2-62
Figure 2-53. Editing Pads and Holes from the Workspace Tree
Finding Padstack Elements in the Workspace Tree

Use the project workspace tree to find padstack elements you entered using the Padstack Editor dialog box. Use the popup menu commands to query for any padstack names, pad names, and hole names associated with the central library. This provides a convenient way to find view all padstack elements without executing the Padstack Editor software within Library Manager. 1. Expand the Padstacks node in the project workspace; the list of padstacks in the central library display in the Project Workspace tab. 2. Highlight the Pin - Through padstack and click the right mouse button to display the Find command (Figure 2-54):
2-63
Figure 2-54. Viewing Padstack Elements in the Workspace Tree
3. Click Find and enter the following values in the dialog box (Figure 2-55): Figure 2-55. Finding a Padstack Element in the Workspace Tree
4. Click OK. The software queries the Pin-Through node and finds the 58 Round padstack element in the tree (Figure 2-56). Figure 2-56. Finding 58 Round Padstack in the Workspace Tree
2-64
Using Library Manager Creating Cells
Creating Cells
Given that you successfully created padstacks, use the Cell Editor to create cells for the design. Cell Editor software provides tools to create Package, Mechanical, Drawing, and Panel cells in the cell partitions within a central library (.lmc) file. Package cells are associated with a part in the Parts Database. Mechanical cells are objects (such as nuts, bolts, card ejectors, heatsinks, washers, plastic mounting devices, and so forth) and may or may not be referenced in the part data. Drawing cells are composed of drawing objects and text. Panel cells are elements that are added to a manufacturing panel to aid in the manufacturing process. For more information on Cell Editor (for example, creating Package, Mechanical, Drawing, and/or Panel cells), consult online help. Note Panel cells functionality is only available when Library Manager is invoked in standalone mode. Panel cells are not available when you invoke Library Manager from Expedition PCB. If large or complex cell designs take more than one editing session to complete, Cell Editor allows you to save an incomplete cell design and exit the software. The incomplete cell design is saved locally but not written to the central library and cannot be used until it is fully completed. When ready to finish work on an incomplete cell design, invoke Cell Editor and note that incomplete (or in progress) cell designs are denoted by colored text in the Cell Editor dialog box. Select the incomplete cell design and continue your work in Cell Editor. When the cell design is considered complete, save the cell design using commands in Cell Editor. The software saves the completed cell design to the central library. Note Cells (and parts) that are saved as complete, they cannot be saved as incomplete or in progress. In this exercise, you will use options on the Mechanical tab to create a cell using Cell Editor accessed from the toolbar (or menubar).
Creating Cells
Use the following procedure to create a cell using the Cell Editor software (accessed from the toolbar or menubar): Tip: You can also create cells by clicking the Cells node in the project workspace and selecting the New Cell command. You will use this method when creating a second cell (see Creating Cells in the SOIC Partition on page 2-70).
2-65
1. Click Tools > Cell Editor or click the Cell Editor icon.
The Cell Editor displays.
When using the DC/DV-Expedition flow, ensure that Dip Thru displays in the Partition pulldown. When using the DxD-Expedition flow, ensure the Dip_Thru partition displays. 2. Click the New Cell icon; the Create Package Cell dialog box appears.
3. Enter the following values in the Create Package Cell dialog box (see Figure 2-57). If you are using the DxD-Expedition flow, key in 20_PIN_DIP in the Cell Name text entry field: Figure 2-57. Create Package Cell Dialog Box (Cell Editor)
4. Click Next; the Place Pins dialog box appears.
2-66
Note In the following steps, select padstacks to build into the cell. 5. For Pin 1, click the center of the Padstack Name field. Click the dropdown list and then click 58 Square. 6. Click the center of the Padstack Name field for Pin 2. Scroll to the bottom of the list then press and hold the SHIFT key. Note Continue to press and hold the SHIFT key while performing steps 7 and 8 (until you assign all pins). If you do not press and hold the SHIFT key while performing these steps, information in the Place Pins dialog box disappears. 7. Hold the SHIFT key and select the center of the Padstack Name field for Pin 20. This highlights the remaining pads in the list. 8. Hold the SHIFT key, select 58 Round from the dropdown list, and release the SHIFT key. Padstack Names 2 through 20 now display 58 Round.
Placing the Pins and Cell Graphics

Perform the following steps to place pins and cell graphics: 1. Click the Pattern Place tab and select DIP from the Pattern Type dropdown box. 2. Key in the measurements displayed in Figure 2-58:
2-67
Figure 2-58. Pattern Place Tab (Place Pins Dialog Box)
3. Click Place to create the cell according to the specified measurements. 4. Click in the screen area to deselect the cell graphics. 5. Click the Maximize icon window. 6. Click the Fit All icon in the workspace window to enlarge the Cell Editor to adjust the display.
Tip: You can use the middle mouse button to Zoom and Pan. Click to zoom in. To zoom out, either hold the Shift key and click the middle mouse button or hold and drag to pan. Colors that appear in the workspace window may be slightly different depending upon color settings on the workstation. 7. Select the Draw Mode icon and move the Ref Des and Part No text objects into the positions as illustrated in Figure 2-59. Place both Ref Des in the same location.
2-68
Figure 2-59. Cell Editor Interface (With Ref Des Displayed)
Note If the Part No (part number) and origin do not appear for the 20 pin dip cell (or 20_PIN_DIP cell in DxD-Expedition Library Manager), click View > Display Control in Cell Editor. Click the Part tab in the Display Control dialog box and select Part Numbers and Origin check boxes. Adjust the Part No property to match Figure 2-59. 8. Click File > Save to save the design. 9. Click File > Exit Graphics to return to the Cell Editor environment. 10. Click Apply in Cell Editor to save changes to the Dip Thru partition (or the Dip_Thru partition in DxD-Expedition Library Manager).
2-69
Creating Cells in the SOIC Partition

In this procedure, you create cells in the SOIC partition using popup menu commands from the workspace tree. 1. In the workspace tree, select the SOIC partition, right-click the mouse button to display the popup menu commands, and select New Cell from the popup menu (Figure 2-60). Figure 2-60. New Cell Command from the Workspace Tree
2. Key in 20 pin SOIC (or 20_pin_SOIC if you are using the DxDesigner-Expedition flow) in the New Cell dialog box (Figure 2-61). Figure 2-61. New Cell Dialog Box from the Workspace Tree
3. Click OK. The Create Package Cell dialog box displays. 4. Enter the following values in the Create Package Cell dialog box (see Figure 2-62). If you are using DxD-Expedition Library Manager, ensure that 20_pin_SOIC appears in the Cell Name text entry field.
2-70
Figure 2-62. Create Package Cell Dialog Box (Cell Editor)
5. Click Next to enter the Cell Editor environment. 6. For Pin 1, click in the center of the Padstack Name field. Scroll to the bottom of the list, then press and hold the SHIFT key. 7. Hold the SHIFT key, select Pin 20, and click in the center of the Padstack Name field. This highlights the remaining pads in the list. A dropdown box displays in the right edge of the Padstack Name field for Pin 20. 8. Hold the SHIFT key and select 24x70 Rectangle from the dropdown list. Select 90 from the Rotation dropdown and release the SHIFT key. All Padstack Names 1 - 20 now display 24x70 rectangle with 90 degree rotation. 9. Click the Pattern Place tab and select SOIC from the Pattern Type dropdown box.
2-71
10. Key in the measurements displayed in Figure 2-63: Figure 2-63. Place Pins Dialog Box (Cell Editor)
11. Click Place; the software creates the cell according to the specified measurements. 12. Click in the screen area to deselect the cell graphics.
Completing the Drawing in Cell Editor

Use the following steps to adjust the display in the Cell Editor window and complete your work in the Cell Editor environment: 1. Maximize the Cell Editor window using the Maximize icon window. Click the Fit All icon to adjust the display. in the workspace
2. Select the Draw Mode icon and move the Ref Des and Part No text objects into the positions illustrated in Figure 2-64. Place both Ref Des objects in the same location. Note If the Part No (part number) and origin do not appear for the 20 pin SOIC cell (or 20_PIN_SOIC in DxD-Expedition Library Manager), click View > Display Control in Cell Editor. Click the Part tab in the Display Control dialog box and select Part Numbers and Origin boxes in the Assembly Items area of the list. Move the Part No text object to the correct position illustrated in Figure 2-64. 3. Click the down arrow next to the Snap Grid icon
2-72
and verify that 10 is selected.
4. Click in the design workspace to clear the current command. 5. Click the Properties icon; the Properties dialog box displays. 6. Select Assembly Outline from the top of the Type list dropdown box. 7. Click the Add Circle icon from the Draw toolbar, key in 40 for the diameter in the Properties dialog box, and press Enter. The circle attaches to the cursor. 8. Place the circle to left of Pin 1. Click in the screen area to deselect the cell graphics (Figure 2-64). Figure 2-64. Cell Editor Interface (With Cell Created)
9. Click File > Save to save the design. 10. Click File > Exit Graphics to exit the design and return to the Cell Editor environment.
2-73
Using Library Manager Creating Parts (Using Part Editor)
11. Click OK to save the cell and exit the Cell Editor software. Note that the new cell appears in the workspace tree. Now that you have created symbol and cell data, use the Part Editor to add parts database data to the central library.
Copying and Moving Cells in the Workspace Tree

Central library objects, such as cells, can be copied and moved using popup menu commands in the workspace tree. See Copying Objects in the Workspace Tree on page 2-99 and Moving Objects in the Workspace Tree on page 2-101 for more information.
Creating Parts (Using Part Editor)

The Part Editor provides tools to create and modify the part entries. Part data provides a link between the physical design cells and schematic symbols through packaging information, such as gate, pin, and device definitions. If large or complex parts take more than one editing session to complete, Part Editor allows you to save an incomplete design and exit the software. The incomplete part is saved locally but not written to the central library and cannot be used until it is fully completed. When ready to finish work on an incomplete part, invoke Part Editor and note that incomplete (or in progress) parts are denoted by colored text in the Part Editor dialog box. Select the incomplete part and continue your work in Part Editor. When the part is complete, save the design using commands in Part Editor. The software saves the completed design to the appropriate part partition in the central library.
Defining a 74F244 Device

The following procedure defines the pin mapping and specifies the default symbol and cell for a 74F244 device to be stored in the Parts partition defined earlier in this exercise. This procedure illustrates how to assign alternate symbols and cells for the device and define swapping between gates. 1. Click Tools > Part Editor or the Part Editor icon The Parts DB Editor dialog box appears. in the Library Manager interface.
2-74
Tip: You can also invoke and use the Part Editor from the Parts node in the project workspace. Right-click on the Parts node and select New Part from the popup menu. The Part Editor dialog box appears (see Figure 2-65 on page 2-76).
Ensure that the Logic Gates partition displays in the Partition field (or Logic_Gates for DxD-Expedition flow). Use Logic_Gates for the DxD-Expedition flow because spaces are not valid for symbol partition names. 2. Click the New icon and key in 100-100000-001 in the Part Listing Number field. The part number is typically the company recognized part number. 3. Click in the Part Listing Name field and key in 74F244. The part name is usually more recognizable than the part number. 4. Click in the Part Listing Label field and key in F244. The part label is even more general than the part name, but is still very recognizable. Tip: Use CTRL+C to copy and CTRL+V to paste from one field to another. 5. Key in the following text in the Description field: 74F244 Octal Buffer/Driver 6. In the Component Properties section of the Part Editor, click the New icon, click in the newly created Name field, and select the dropdown list to display a list of available properties. 7. Select Cost and key in 1.25 in the Value field (see Figure 2-65).
2-75
Figure 2-65. Part Editor Dialog Box (With Values Displayed)
8. Click Pin Mapping to display the Pin Mapping dialog box. 9. In the Assign Symbol section of the dialog box, click the Import icon. dialog box displays. The Import
Using the Import Dialog Box to Import Symbols and Cells to the Part Database
Use the Symbols and Cells tabs in the Import dialog box to import symbol and cell data into the part database:
2-76
1. Select Logic Gates from the Central Library Partition pulldown and highlight g244a. If you are using the DxD-Expedition flow, select Logic_Gates from the Central Library partition field and highlight Logic_Gates:g244a. Ensure other values and settings match Figure 2-66 for the DC/DV-Expedition flow (Figure 2-67 for the DxD-Expedition flow): Figure 2-66. Import Dialog Box (Part Editor) With Symbols Tab (DC/DVExpedition flow)
Ensure values and settings match for the DxD-Expedition flow (see Figure 2-67):
2-77
Figure 2-67. Import Dialog Box (Part Editor) With Symbols Tab (DxD-Expedition flow)
When selecting the Create New Gate Information option and entering a value in the Number of Slots in Component field, the software creates slots for mapping pin names with pin numbers. When selecting the Include Pin Properties option, the software imports the Property and Value information for the pins on the Logical tab. Tip: Though it is not used in this exercise, you can also use the Include pin number mapping option when importing DxDesigner symbols. The Part Editor will import and map the pin numbers accordingly. When this option is selected, the Part Editor searches the symbol pin numbers to determine the correct number of slots to create. For symbols with one assigned pin number per pin, a single slot will be created. If the symbol contains pins with multiple comma-separated pin numbers, the Part Editor will create an equivalent number of slots and map the pin numbers accordingly. 2. Click the Cells tab in the Import dialog box and set the values and settings as shown in Figure 2-68 (for both the DC/DV-Expedition and DxD-Expedition flows). Note that Cell Names in the DxD-Expedition flow are in uppercase with no spaces (20_PIN_DIP and 20_PIN_SOIC). Ensure that you select 20 pin SOIC (or 20_PIN_SOIC for the DxD-Expedition flow) as shown in Figure 2-68:
2-78
Figure 2-68. Import Dialog Box (Part Editor) With Cells Tab
3. Click OK; the software imports the symbol and cell name information. The software returns you to the Pin Mapping dialog box. 4. Click the Import icon in the Assign Package Cell section; the Import dialog box displays (the Cells tab displays by default). 5. Select 20 pin dip (20_PIN_DIP if you are using DxD-Expedition Library Manager) and set the Import Cell As option to Alternate (Figure 2-69).
2-79
Figure 2-69. Import Dialog Box (Part Editor) With Cells Tab Updated
6. Click OK. The software places this device as a surface mount device or a through-hole device.
2-80
Note The software automatically assigns the pin names to Slot #1 in the Logical tab (Figure 2-70). You do not need to enter pin names in the remaining slots since they are all the same. When using DxD-Expedition Library Manager, the order of the Value column and pin names in Slot #1 may vary in appearance. If this occurs, be careful when assigning pin numbers because they may not exactly match the graphics in this document. Figure 2-70. Pin Names Assigned to Slot #1
Assigning Pin Numbers

Use the following steps to assign pin numbers to the associated slots: 1. Click the Physical tab to assign the pin numbers to each slot. 2. Select a pin number from the Physical Pins list. For each slot, assign the pin number that corresponds to the pin name by clicking in the Pin # field. Select the Paste Across icon to move the physical pin number into the slot. You can also key in the pin numbers into the Pin # field for each slot. 3. Enter pin numbers for each slot as shown in Figure 2-71. Note that DxD-Expedition Library Manager may order gates in inverted order so the pin numbers may not exactly match those in this figure. Figure 2-71. Pin Numbers Assigned to Slots
2-81
Tip: Use CTRL+C to copy and CTRL+V to paste common pins from one field to another. 4. Click the Supply and NC tab. Use the options in this dialog box to assign the power, ground, and no connect pins. 5. Click in the Supply Name field (in the Supply and NC Assignments table) and enter gnd. If you are using DxD-Expedition Library Manager, enter GND. 6. Click Pin 10 in the Physical Pins list, select the Pin # field to the right of gnd, and select the Paste Across icon. 7. Click in the Supply Name field (in the Supply and NC Assignments box) below gnd and enter vcc. If you are using DxD-Expedition Library Manager, enter VCC. 8. Click on Pin 20 in the Physical Pins list, select the Pin # field to the right of vcc, and select the Paste Across icon. Figure 2-72. Assigning Power, Ground, and NC Pins
For the DxD-Expedition flow, ensure that Supply Name is GND and VCC (upper case text).
Note When importing the symbol using DxD-Expedition Library Manager, if the SIGNAL attribute and value are built into the symbol and the Include pin number mapping option is used, corresponding Supply Name entries and values are created and display on the Supply/NC tab. 9. Click OK in the Pin Mapping dialog box to return to the Part Editor environment. 10. Click File > Save in the Part Editor to save the design.
2-82
Assigning Alternate Symbols

Use the following steps to assign alternate symbols to the design: 1. Click the Pin Mapping command (bottom-right of the dialog box); the Pin Mapping dialog box displays. 2. Click the Import icon dialog box displays. in the Assign Symbol section of the dialog box; the Import
3. Select Logic Gates from the Central Library Partition pulldown and highlight 74F244_Half. If you are using the DxD-Expedition flow, select Logic_Gates from the Central Library Partition pulldown and highlight Logic_Gates:74F244_Half. Ensure other values and settings match Figure 2-73:
2-83
Figure 2-73. Import Dialog Box (Part Editor) With 74F244_Half Package Displayed
Ensure values and settings match for the DxD-Expedition flow Figure 2-74:
2-84
Figure 2-74. Import Dialog Box (Part Editor) With 74F244_Half Package Displayed (DxD-Expedition flow)
4. Click OK; the software incorporates the symbol information. The software automatically assigns the pin numbers to the slots in the Logical tab.
Assigning Pin Names to the Half Package

Use the following steps to assign the pin names to each slot in the 74F244_Half package using the Logical tab: 1. Select a pin name from the Logical Pins list. For each slot, assign the pin name that corresponds to the pin number by clicking in the Slot # field and selecting the Paste Across icon to move the logical pin name into the slot. You can also key the pin names into the Slot # field for each slot manually. 2. Enter pin names for each slot as shown in the following figure. Do not enter the pin names in the remaining slots since they are the same for each half of the device. Note that the DxD-Expedition flow may order pin in inverted order so the pin numbers may not exactly match those in Figure 2-75. Tip: Use CTRL+C to copy and CTRL+V to paste common pins from one field to another.
2-85
Figure 2-75. Assigning Pin Names to 74F244_Half Package
3. Click OK on the Pin Mapping dialog box to return to the Part Editor dialog box. 4. Click File > Save in the Part Editor to save your work.
Importing and Assigning Pin Names to the Full Package

Use the following steps to assign the pin names to each slot in the 74F244_Full package using the Logical tab: 1. Click the Pin Mapping command; the Pin Mapping dialog box displays. 2. Click the Import icon dialog box displays. in the Assign Symbol section of the dialog box; the Import
3. Select Logic Gates from the Central Library Partition pulldown and highlight 74F244_Full. If you are using DxD-Expedition Library Manager, select Logic_Gates from the Central Library Partition pulldown and highlight Logic_Gates:74F244_full. Ensure other values and settings match Figure 2-76:
2-86
Figure 2-76. Import Dialog Box (Part Editor) With 74F244_Full Package Displayed
Ensure values and settings match for the DxD-Expedition flow match Figure 2-77:
2-87
Figure 2-77. Import Dialog Box (Part Editor) With 74F244_Full Package Displayed (DxD-Expedition flow)
4. Click OK; the software incorporates the symbol information and automatically assigns pin numbers to the slots in the Logical tab.
Assigning Pin Names to the Full Package

Use the following steps to assign pin names to each slot in the 74F244_Full package using the options in the Logical tab: 1. Select a pin name from the Logical Pins list. For each slot, assign the pin name that corresponds to the pin number by clicking in the Slot # field and select the Paste Across icon to move the logical pin name into the slot. You can also key the pin names into the Slot # field for each slot manually. 2. Enter pin names for each slot as shown in Figure 2-78. Do not enter the pin names in the remaining slots since they are the same for each half of the device. Note that the DxDExpedition flow may order pins in inverted order; therefore, the pin numbers may not exactly match those in Figure 2-78. Tip: Use CTRL+C to copy and CTRL+V to paste common pins from one field to another.
2-88
Figure 2-78. Assigning Pin Names to 74F244_Full Package
3. Click the Supply and NC tab. Use the options in this dialog box to assign the power, ground, and no connect pins (gnd =10, vcc = 20 for the DC/DV-Expedition flow. For the DxD-Expedition flow, type uppercase text. For example, GND = 10 and VCC = 20. See Figure 2-72 on page 2-82 for additional information. 4. Select the 74F244_Full symbol (or Logic_Gates:74F244_Full if you are using the DxD-Expedition flow) in the Assign Symbol section. This is the default symbol that the software uses during Symbol Device Place within Design Capture (DC) or placing symbols in DxDesigner (Figure 2-79). Figure 2-79. Assigning Default Symbol in the Part Editor
5. Click OK in the Pin Mapping dialog box to display the Part Editor environment. 6. Click File > Save in the Part Editor to save the design. 7. Click File > Exit to exit the Part Editor environment. Note that the Parts entry in the workspace tree shows the relationships you assigned via the dialog box (Figure 2-80).
2-89
Using Library Manager Managing Model Data (DxD-Expedition Flow)
Figure 2-80. Part With Associated Symbols and Cells in the Workspace Tree
Copying and Moving Parts in the Workspace Tree

Central library objects, such as parts, can be copied and moved using popup menu commands in the workspace tree. See Copying Objects in the Workspace Tree on page 2-99 and Moving Objects in the Workspace Tree on page 2-101 for more information.
Managing Model Data (DxD-Expedition Flow)

Library Manager and DMS Librarian in the DxDesigner-Expedition flow provides tools to manage models (SPICE and Compiled Verilog-A only). Using commands in the workspace tree, you can create model data partitions and manage model data files (edit, view, copy, and delete) that you import to the central library. Model data files are stored in the Models subdirectory within the DxD-Expedition flow central library. Model data files are not managed in a DC/DV-Expedition flow central library. Note You cannot use Library Services to import or manage models.
Viewing Model Types in the Workspace Tree

Model files types and partitions are viewable in the Models node in the navigator tree. Subnodes within the Models node segregate the data by supported model type (Spice and Verilog) as shown in Figure 2-81.
2-90
Figure 2-81. Models Node in the Workspace Tree (DxD-Expedition Flow)
Creating a New Model File Partition

Use the popup menu commands in the workspace tree to create model file partitions in the central library. 1. To create a new model partition for either SPICE or Verilog, select the New Partition popup menu command and key in the partition name (Figure 2-82). Figure 2-82. Creating a New Models Partition in the Workspace Tree
2. Click OK to add a partition to the SPICE or Verilog model nodes (Figure 2-83). 3. Repeat Steps 1 and 2 as necessary to add as many partitions as you require.
2-91
Figure 2-83. Partitions in the Models Node of the Workspace Tree
Importing a Model File

Use the Import Model popup menu command to import a Verilog or SPICE model file into a select Model partition in a central library. When you invoke the command, the Select a Model File to Import dialog box appears and allows you to browse for or key in a model file based on the type of model (SPICE or Verilog) you are importing. The Files of Type dropdown box provides a filtered list of valid file name extension for both SPICE and Verilog (note that SPICE is used as an example in Figure 2-84). The valid file name extensions supporting in this release are outlined in Table 2-5: Table 2-5. Valid Model File Name Extensions File Type SPICE Verilog File name extensions .cir, .ckt, .mod, .spi .ai, .va
Tip: While the file type filters for the file name extensions (see previous table), the software allows you to import other valid SPICE and Verilog files with different extensions.
2-92
Figure 2-84. Importing a Model File to a Models Partition
1. Highlight a partition in the Models tree and select the Import Model popup menu command. The Select a Model File to Import dialog box appears which allows you to browse for and choose the appropriate model file for the type you selected 2. Browse for or enter a model file name and extension in the dialog box. Tip: Use the Files of Type dropdown box to limit the files that appear in the Select a Model File to Import dialog box to those that have the appropriate file name extensions (see Step 3 in Figure 2-84). 3. Click Open to dismiss the dialog box and copy the file into the model partition in the central library. The model file you selected appears in the appropriate model partition in the workspace tree (Figure 2-85). Figure 2-85. Imported Model File in the Workspace Tree
2-93
Tip: To import more than one model file (or bulk load) into a models partition, use file management tools to copy and paste multiple model files into select partitions. Ensure that you import the correct model type into the correct partition (in other words, SPICE models must appear in partitions in the SPICE node) or errors will occur. Click Refresh from the Library Manager toolbar to reset the workspace tree view and view the newly imported model files in their select partition(s).
Creating a New Model File

Use the New Model popup menu command in the workspace tree (from a Models partition) to create a Verilog or SPICE model file in a select Model partition in a central library. When invoked, the New Model File Editor environment appears and allows you to create a new model file. Upon completion, the model file you created appears in the selected Models partition in workspace tree and in the central library. 1. Highlight a Models partition in the workspace tree and select the New Model popup menu command. The New SPICE Model or New Verilog Model dialog box appears depending upon the type of model file you are creating (Figure 2-86). Figure 2-86. New Model File Command in the Workspace Tree
2. Enter the name of the new SPICE or Verilog Model file that you want to create. Use the appropriate file name extensions (Table 2-5 on page 2-92) when creating a new model file. 3. Click OK; the New Model dialog box dismisses and the software invokes the DxDesigner model file editor environment to create the new model.
2-94
4. Create the SPICE or Verilog model file in the editor using tools in the editing environment. 5. Upon completion, click File > Close and File > Exit in the DxDesigner model file editor environment. The appropriate Model file partition in the workspace tree updates to show the new model file you just created.
Viewing and Editing a Model File

Use the View and Edit popup menu commands in the workspace tree (from a Models partition) to view a Verilog or SPICE model file in a select Model partition within the DxD Model Editor environment. When invoked, the DxD Model Editor environment appears and allows you to view and make edits to an existing model file. If you edited the file, save changes and exit the DxD Model Editor. This automatically updates the model file you selected. If you select the View popup menu command, simply exit the DxD Model Editor. Note The Edit popup menu command is disabled if you select a compiled Verilog-A file or model files originating from a model library (a model file containing multiple models). Figure 2-87. View and Edit Model File Commands in the Workspace Tree
1. Highlight a SPICE or Verilog model file in the workspace tree and select the View or Edit popup menu commands (Figure 2-87). The software invokes the DxD Model Editor environment and displays the model file contents in the viewer. 2. Use commands in the DxD Model Editor to edit the file as needed. 3. To save edits, click File > Save in DxD Model Editor. The software saves the changes, dismisses the DxD Model Editor, and returns you to the model file you selected in the Library Manager workspace tree. To close the model file without saving changes, click File > Exit or File > Close in the DxD Model Editor. This dismisses the DxD Model Editor and returns you to the model file you selected in the Library Manager workspace tree.
2-95
Copying a Model File

Use the Copy popup menu command in the workspace tree (on a model file within a Models partition) to copy a model file from one partition in a central library to another (Figure 2-88). Note You cannot copy a model file to a SPICE model partition. The Copy command is disabled for compiled Verilog-A model files. Figure 2-88. Copy Model File Command in the Workspace Tree
Central library objects, such as a model file, can be copied and moved using the Copy command in the workspace tree. See Copying Objects in the Workspace Tree on page 2-99 and Moving Objects in the Workspace Tree on page 2-101 for more information.
Deleting a Model File

Use the Delete popup menu command in the workspace tree to remove a model file from a models partition in a central library (Figure 2-89). When deleting a model file, the software removes the model file from the central library and from the workspace tree.
2-96
Using Library Manager Using the Modify Pins Dialog Box
Figure 2-89. Delete Model File Command in the Workspace Tree
Deleting a model file is similar to deleting other objects (such as symbols, cell, and padstacks) from the central library. See Deleting Objects and Partitions from the Workspace Tree on page 2-102 for more information. Tip: To delete more than one model file, use file management tools to remove multiple model files from select partitions. Click Refresh from the Library Manager toolbar to reset the workspace tree view and remove deleted model files from the viewer.
Using the Modify Pins Dialog Box

The Modify Pins dialog box, available when you click Tools > Modify Cell & Symbol Pins, allows you to rename and renumber cell and symbol pins. There are three ways to modify the pins. Direct Edit - Click on the pin in the New Pin column and update the pin name/number. Swap Pins - When two entries are selected in the New Pin column, the entries can be swapped by clicking the Swap icon. This icon is only active when two pins are selected. Auto Number Pins - When more than one pin is selected, the Auto Generate Numbers icon enables you to automatically generate numbers. Tip: You can select the Auto Generate Numbers icon when at least one pin of a slot is selected. Use Auto Generate Numbers to create logical pin names or physical pin numbers. You can enter the prefix, starting number, increment (positive or negative) and the suffix to be used when the pin numbers or names are automatically generated. The only difference between this dialog and the one found in the Parts Editor is that the Numbering direction option is not available.
2-97
Using Library Manager Using the Modify Pins Dialog Box
Most symbol or cell changes will affect one or more Part Editor entries; therefore, when you click OK or Apply, the active central library (*.lmc) file is checked for affected cells or symbols and related Part Editor entries. Pin changes cannot be completed if any cell or symbol partitions are reserved. If any partitions are reserved, a message dialog box displays with information on which partitions are reserved. If none of the cell or symbol partitions are reserved, then a confirmation dialog box appears detailing all the part database entries that are affected by the change. To use the Modify Pins dialog box: 1. Click Tools > Modify Cell & Symbol Pins; the Modify Pins dialog box displays. 2. Change the Type field to Symbol and highlight the Logic_Gates;74f244_full symbol from the list. The pin names you just defined for the symbol appear in the adjacent list (Figure 2-90). Figure 2-90. Modify Pins Dialog Box
2-98
Using Library Manager Copying Objects in the Workspace Tree
3. Select a partition to filter the item list or choose (All) to see items from all partitions. 4. Use the Find option to enter a specific cell or symbol name; asterisks (*) can be used as wildcards. When a match is found, the Item list scrolls to that item and selects the item. Click Find to continue searching the list for the next match. Tip: To quickly find something in the list you can select a cell in the list and type the first few letters of the desired name or partition and the list will scroll to the first name or partition that matches those letters. The find function does not find partition names and is case-insensitive. The list contains cells or symbols, depending on the selected Type. When an item is selected in this list, the associated pins are displayed in the Modify Pins List on the right side of the dialog box. The columns can be sorted in ascending or descending order by pressing the column header. Note Do no modify the pin names. This exercise simply illustrates the tools used to modify pin names of cells and symbols in a central library without using the Part Editor dialog box. 5. Edit the pins in the second column in the Modify Pins List to reflect your requirements. The first column is Read Only and contains the existing pins. The columns can be sorted in ascending or descending order by pressing the column header. Note When the Type is set to Symbol, the column headers are labeled "Existing Pin Name" and "New Pin Name". When the Type is set to Cell, the column headers are labeled "Existing Pin Number" and "New Pin Number". 6. Click Close to dismiss the dialog box without changes.
Copying Objects in the Workspace Tree

Use the Copy popup menu command to copy and move objects (such as a symbol, cell, part, padstack, models, and reusable blocks) that appear in the workspace tree (and exist in the central library) between partitions within the selected central library. You can also copy an object and rename it within an existing central library partition. The Copy popup menu command allows you to conveniently manage central library objects within the workspace tree without invoking Library Services to copy and move objects in a central library.
2-99
Using Library Manager Copying Objects in the Workspace Tree
Tip: The Copy popup menu command moves only one object at a time. To move several objects in a central library or perform a bulk move or bulk copy, use Library Services. Right-click the object in the workspace tree and select Copy from the popup menu. The Copy dialog box appears. By default, the Target Partition dropdown displays the current name and partition (if applicable) of the selected object. Figure 2-91 shows the Copy Part dialog box (which is similar in use with the Copy Symbol, Copy Cell, Copy Spice Model, and Copy Verilog Model dialog boxes). Figure 2-91. Using the Copy Popup Menu Command (Parts in Library Manager)
To copy the object to another partition, select one from the Target Partition dropdown and click OK. The software copies the object to the selected partition in the central library. The copied object appears in the workspace tree. To rename the object, key in the new object name, select a Target Partition, and click OK. The object or empty partition is removed from the central library and no longer appears in the workspace tree. If the object name you key in matches an object that already exists in the
2-100
Using Library Manager Moving Objects in the Workspace Tree
selected partition, the software generates and error and prompts you for a unique object name and/or target partition.
Copying a Padstack
For padstacks, use the Copy popup menu command to copy an existing padstack and enter a new name. If you enter a padstack name that already exists, the software generates an error and prompts you to rename the padstack. Figure 2-92. Copy Padstack Dialog Box
Click OK and the new padstack name appears in the correct partition type in the workspace tree. Note For information on reusable blocks, see Managing Reusable Blocks (DC/DV-Expedition Flow) on page 4-35.
Moving Objects in the Workspace Tree

Use the Move popup menu command to move objects (such as a symbol, cell, part, model data, and reusable blocks) that appear in the workspace tree (and exist in the central library) between partitions within the selected central library. Unlike the Copy popup menu command Copying Objects in the Workspace Tree on page 2-99), you cannot move and rename the object. The Move popup menu command allows you to conveniently manage central library objects within the workspace tree without invoking Library Services to move objects in a central library. In Figure 2-93, a part is being moved from one partition to another within the central library.
2-101
Using Library Manager Deleting Objects and Partitions from the Workspace Tree
Figure 2-93. Move Part Dialog Box
To move the object to another partition, select one from the Target Partition dropdown and click OK. The software copies the object to the selected target partition in the central library. The copied object appears in the workspace tree.
Deleting Objects and Partitions from the Workspace Tree

Use the Delete popup menu command to remove objects (such as a symbol, cell, and parts) from the central library as long as they are not referenced by other parts in the central library. Empty symbol, cell, and parts data partitions (in other words, partitions that are void of objects in the workspace tree) can also be removed from the central library using the Delete popup menu command (Figure 2-94). Right-click the object or empty part, symbol, or cell partition in the workspace tree and select Delete from the popup menu. The object or empty partition is removed from the central library and no longer appears in the workspace tree.
2-102
Using Library Manager Using File Viewer
Note Dx Symbols can be renamed using popup menu commands in the project workspace tree. See Renaming a Dx Symbol in the Project Workspace Tree on page 2-52 for more information. Figure 2-94. Delete Popup Menu Command
Note If a central library partition is reserved or contains objects, the software disables the Delete popup menu command.
Using File Viewer

Library Manager features the File Viewer, a utility that allows you to view the contents of ASCII process log files generated by the software. These files are located in the job's LogFiles directory within the central library structure. The workspace is divided into two areas: the left side displays the names of the files generated by the software, and the right hand side displays the text of the selected file. When you rightclick the mouse on a file name, a popup menu appears with quick access to Print, Delete and Rename commands. If you click the right mouse button in the list of text files, the popup menu displays View and Arrange commands. Before printing a file, ensure that you have a printer installed. If you highlight some of the text within a file, only that selected text is printed. This enables you to define and print only relevant information. If text is not highlighted within the file, the entire file is printed. You can collapse File Viewer to an icon on the desktop by clicking on the minimize button in the top right-hand corner of the viewer. If you exit the application without exiting File Viewer, you must manually close it.
2-103
Using Library Manager Summary
Use the following steps to invoke the File Viewer and view a report file generated by Library Manager: 1. Select File > File Viewer or click the File Viewer icon in the toolbar ; the File Viewer utility displays. A list of ASCII text files generated by Library Manager displays in the workspace. 2. Highlight any text file displayed in the File Viewer workspace. The selected file appears in the viewer. 3. Select the text from the file displayed in File Viewer by highlighting the text with the left mouse button. 4. Use one of the following methods to define and copy text: Select Copy from the Edit pulldown in the File Viewer. Select the Copy icon in the File Viewer. Type Ctrl+C or Alt + E + C
5. After highlighting sections of the file, click the right mouse button and select Copy from the popup menu or after highlighting sections of the file, click the right mouse button and select Select All from the popup. 6. When the text is highlighted, click the right mouse button again and select Copy from the popup. 7. Open another application (Mail or Notepad or other text editor) and press Ctrl + V to paste the selected text. Note You can attach a selected file to a Microsoft Mail message using the File > Send command. Do not attempt to use this command unless you have a Microsoft Mail account set up on your system. Other options included in the File Viewer utility are documented in online help associated with the File Viewer software (Help > Contents command). Upon completion, delete the text file you just created in this section.
Summary
You have now successfully used Library Manager and the software tools necessary to continue to the next exercises. If Parts Manager Administrator software is unavailable (DC/DVExpedition Library Manager only), proceed directly to Using Library Manager on page 2-1. If Parts Manager Administrator software is available (DC/DV-Expedition Library Manager only), perform the optional exercises in Using PM Administrator on page 3-1.
2-104
Chapter 3 Using PM Administrator

Introduction
If you are using Library Manager in the DxDesigner-Expedition flow or the Design Architect to Expedition PCB flow, you cannot use Parts Manager Administrator. Proceed to Implementing a Design on page 4-1. If you are using the DC/DV flow, you are not required to perform the procedures in this chapter. Note If Parts Manager Administrator (PMA) software is not available, the Parts Manager icon on the Library Manager interface becomes non-selectable. If so, proceed to Implementing a Design on page 4-1. A copy of the finalized library (resulting from this exercise) is located in the following directory: <SDD_HOME>\wg\tutorial\LibMgr\final_library This exercise assumes that you have successfully completed the exercise in Implementing a Design on page 4-1 and the Library Manager interface displays on your workstation. Parts Manager (PM) is an electronic component management tool that provides access to parametric data and interfaces with parts data stored in a relational database. Users of electronic design applications, such as Design Capture (DC) and DesignView, can access this data from nodes on the network. PM stores and retrieves parametric data from a database. Parametric data in the PM database works in tandem with the Library Manager software which stores information on symbols, Parts data, and cells in partitions in the central library (*.lmc) file. Note This process guide uses Design Capture as the design entry software tool. You can also use DesignView for design entry tasks. However, command paths may be different when using DesignView. When using Parts Manager, perform the procedures in this chapter in the following order: Invoking and Configuring Parts Manager Administrator on page 3-4 Creating a Parametric Table on page 3-5 Adding Parameters to a Parametric Table on page 3-8 Renaming Parametric Tables on page 3-17
3-1
Using PM Administrator Introduction
Deleting Parametric Tables on page 3-21 Inserting Parametric Tables from ASCII on page 3-24 Adding Part Numbers to the PM Database on page 3-29 Deleting Part Numbers from the PM Database on page 3-33 Inserting PPS Data into the PM Database on page 3-34 Modifying the Central Library on page 3-39 Adding Parametric Data to Parts on page 3-55 Using the Parts Manager Validation Utility on page 3-70 Moving Data Between the PM Database and Parts on page 3-79 (using the Parts Manager Batch Update Utility) Using the PM/PDB Synchronization Utility on page 3-89 Using the Parts Manager Batch Update Utility on page 3-91 Adding Attachment Data on page 3-97 Importing PPS Data With Attachment Data on page 3-101 Exiting / Logging Out of PMA on page 3-103
The flowchart in Figure 3-1 illustrates the order of procedures in this chapter:
3-2
Using PM Administrator Introduction
Figure 3-1. Parts Manager Administrator Software Process Flow
3-3
Using PM Administrator Invoking and Configuring Parts Manager Administrator
Invoking and Configuring Parts Manager Administrator

In this procedure, click Tools > Parts Manager to invoke Parts Manager Administrator (PMA) from the Library Manager interface. You will configure the software for the remaining procedures in this chapter. Note that PMA is not available on Linux and UNIX. Use the following steps to configure Parts Manager Administrator software on your Windows machine: 1. Click the Parts Manager icon in the Library Manager interface and the Parts Manager Administrator window displays: Figure 3-2. Parts Manager Administrator Window
2. Click the Configure icon on the PMA toolbar or select File > Configure; the Parts Manager Configuration dialog box displays.
3-4
Using PM Administrator Creating a Parametric Table
Figure 3-3. Parts Manager Configuration Dialog Box
3. Set the Parts Manager (PM) Working Directory to the following directory: <drive>:\temp Tip: If PMA software does not detect a temp directory, a dialog box displays and prompts you to create this directory. Click Yes, and the software automatically creates the temp directory. Now that you have defined a PM working directory, you can create parametric tables. Note Refer to the Parts Manager Process Guide and Parts Manager Administrator online help for additional information on fields and options on the Parts Manager Configuration dialog box.
Creating a Parametric Table

Parametric tables consist of user-definable component parameters (such as thermal, electrical, cost, and other information). Consult the Parts Manager Process Guide for additional information on parametric tables.
3-5
Now that you configured the Parts Manager Administrator (PMA) software, use the following procedure to create a parametric table: 1. Click the PPS Tables icon on the icon bar or File > PPS Tables to invoke the Parametric Tables dialog boxes. Note The dialog boxes contain two sections. The top half contains the PM Classification Tree and the bottom half contains the Create/Update/Delete, Insert, and Extract Parametric Tables dialog boxes. Figure 3-4. Parametric Tables Dialog Box
2. Click the Create/Update/Delete tab in the lower half of the Parametric Tables dialog box. The Create/Update/Delete dialog box displays. 3. Click the PM Classification Tree text in the top half of the Create/Update/Delete Parametric Tables dialog box.
3-6
4. Key in Logic IC in the text field in the lower half of the Create/Update/Delete Parametric Tables dialog box and click the New Table icon or press the Enter key. This adds the Logic IC table to the Parts Manager (PM) database. The Create/Update/Delete Parametric Table dialog box appears as shown in the following figure. Figure 3-5. PM Classification Tree With One Undefined Table
5. Key in the name of a second table (Logic IX) and click the New Table icon. The Create/Update/Delete Parametric Tables dialog box updates as shown in the following figure.
3-7
Using PM Administrator Adding Parameters to a Parametric Table
Figure 3-6. PM Classification Tree With Two Undefined Tables
Note You delete the Logic IX table later in this exercise. You have now successfully created parametric tables in the PM database. However, these tables must be populated with parameter information.
Adding Parameters to a Parametric Table

Now that parametric tables have been created, add parameters to these tables and use the Property Definition Editor (available from the Library Manager interface) to make modifications to these individual parameters. Use the following steps to add parameters and define the parametric table: 1. Select the Logic IC table in the upper half of the Parametric Tables dialog box.
3-8
2. Click the New Parameter icon in the Parameters field in the lower half of the Create/Update/Delete Parametric Tables dialog box. The software adds a new parameter (called param name) to the table. 3. Click the New Parameter icon to add a second parameter to the table. Figure 3-7. Adding a Parameter to a Parametric Table
4. Click the name of the first new parameter (param name) to highlight the parameter and key in the following: Cost
3-9
Figure 3-8. Specifying a Parameter in a Parametric Table
5. Click in the Property column and a list of property names display. 6. Select the Cost property to map the Cost parameter to the Cost property (defined in the Property Definition Editor).
3-10
Figure 3-9. Mapping a Parameter to a Property in a Parametric Table
7. Click Apply to save the parameter-to-property mapping in the table. The following message displays in the message field: PPS table created successfully.
3-11
Figure 3-10. Populating a Parametric Table With Parameters
Note Properties and their corresponding attributes (visibility, color, and so forth) are defined in the CentLib.prp file. This file also controls property accessibility in other tools such as Design Capture (DC), DesignView, the Part Editor, and Parts Manager (PM). The CentLib.prp file can be modified using the Property Definition Editor dialog box in Library Manager.
Mapping Properties to Parameters in Parts Manager

Use the following steps to map parameters in Parts Manager to properties in the Property Definition Editor: 1. Click the Property Definition Editor icon on the Library Manager interface to invoke the Property Definition Editor dialog box. Click Advanced on the Property Definition Editor to enlarge the dialog box.
3-12
Figure 3-11. Property Definition Editor Dialog Box
2. Find the Property list field in the left half of the dialog box. This field lists all properties in the central library. The field consists of four columns: Checkboxes Property types Property names Property formats
3. Sort the list by any of the four columns by clicking on the columns title bar header. Clicking on it again sorts the list in the reverse order. Note Selecting a checkbox in the Place property in schematic when Packager or Place Device is used column enables the software to place that property on a schematic when using the Packager Utility or the Place > Device command in design entry software, such as Design Capture or DesignView. 4. Locate the Include selected property in property lists for field in the right half of the Property Definition Editor dialog box. If the PM option is enabled, that property appears in the Property dropdown list in the Parametric Tables dialog box in Parts Manager.
3-13
Adding Properties to Parts Manager

Using the Property Definition Editor dialog box, modify the Description property using the following steps: 1. Select the Description property in the Property List field within the Property Definition Editor dialog box. 2. Click the checkbox adjacent to the Description property. This enables the Description property for access by the Packager Utility or the Place > Device command in design entry software. 3. Click Advanced at the bottom of the Property Definition Editor dialog box to display additional property options and settings. The software applies all modifications made in this half of the dialog box to the Description property. 4. Select the Parts Manager checkbox in the Include Selected Property in Property Lists For field. This instructs the software to allow access to the Description property in Parts Manager. 5. Change the default property visibility from Visible to Hidden by changing the Visible field from Yes to No. The settings in the Property Definition Editor must match the following figure: Figure 3-12. Modifying a Property in the Property Definition Editor
3-14
6. Click OK in the Property Definition Editor to save all property changes and close the dialog box.
Mapping Properties to Parameters in Parts Manager

Use the following steps to map the Description property you activated using the Property Definition Editor to the Description parameter in Parts Manager: 1. Return to the Create/Update/Delete Parametric Tables dialog box in Parts Manager Administrator and click Apply to save the table. The software re-reads the changes you made in the Property Definition Editor dialog box (saved to the CentLib.prp file). The software adds the Description property to Property list in the Create/Update/Delete Parametric Tables dialog box. 2. Select the param name parameter. 3. Change the name of the parameter to Description. 4. Map the Description parameter to the Description property by choosing the Description property in the Property dropdown list. The parameter type changes from Integer to Char(64).
3-15
Figure 3-13. Mapping a Parameter to a New Property in a Parametric Table
Tip: When mapping a parameter to a property, the parameter type automatically changes to the type listed in the CentLib.prp file. With Text property types, the software sets the Type to Char (Character). The software sets the amount of characters specified in the Max Number of Characters field in the CentLib.prp file. When changing a property type in the CentLib.prp file, change the type of its corresponding parameter in Parts Manager by remapping the parameter to its corresponding property. 5. Click Apply to save all changes. The following informational dialog box appears.
3-16
Using PM Administrator Renaming Parametric Tables
Figure 3-14. Parts Manager Administrator Information Dialog Box
6. Click Yes and the new Logic IC table overwrites the existing Logic IC table.
Applying Parameters from One Parametric Table to Another Table

Use the following steps to apply the parameters you defined in the Logic IC table to the Logic IX table: 1. Select the Logic IX table in the PM Classification Tree. Note that all of the Logic IC parameters display in the Parameters field. If a table does not contain any parameters, the Parameters field displays the previous tables parameter list. This allows you to add parameters to a new table. 2. Click Apply and the software adds the Cost and Description parameters to the Logic IX table. The software did not display a message to replace an existing table definition. This message only appears when you save a table with existing parameters.
Renaming Parametric Tables

Tables in the PM Classification Tree can be renamed without changing the parameters within that table. Use the following procedure to change the name of a table in the PM Classification Tree: 1. Double-click on the Logic IX table in the top half of the Create/Update/Delete Parametric Tables dialog box. The table name field changes to an editable field.
3-17
Figure 3-15. Changing a Parametric Table Name
2. Rename the table by keying in the following new table name: Memory IX Tip: If you change the name of the table in the PM Classification Tree and click Apply, the software saves the new table name. However, the lower half of the Parametric Tables dialog box still displays Logic IX. Click Apply to save only the Logic IX table to disk. 3. Click the Logic IC table in the top half of the Create/Update/Delete Parametric Tables dialog box. The software automatically saves the Memory IX table name.
3-18
Figure 3-16. Renaming a Parametric Table
4. Select the Memory IX table in the top half of the Create/Update/Delete Parametric Tables dialog box. 5. Key in the following text in the text input field in the bottom half of the Parametric Tables dialog box: Memory IC
3-19
Figure 3-17. Renamed Parametric Table in the PM Classification Tree
6. Click Apply and then click Yes on the informational dialog box to save the new table name.
3-20
Using PM Administrator Deleting Parametric Tables
Figure 3-18. Renamed Parametric Table in the PM Classification Tree With Message Displayed
Deleting Parametric Tables

Parametric tables can be quickly deleted from the Parts Manager database. In this procedure, create a table and then delete it. Remember that a parametric table must be void of all part numbers before it can be deleted (removed) from the database. Use the following steps to remove an empty parametric table (named Test) from the Parts Manager (PM) Classification Tree. Note Ensure that you select the PM Classification Tree in the upper half of the Parametric Tables dialog box.
3-21
1. Key in Test in the lower half of the Create/Update/Delete Parametric Tables dialog box and click the Create Table icon. Figure 3-19. Creating a New Parametric Table
2. Select the Test table from the PM Classification Tree in the upper half of the Create/Update/Delete Parametric Tables dialog box. 3. Click the Delete Table icon message: to delete the table. A dialog box displays the following
Are you sure you want to delete this table? 4. Click Yes in the dialog box and the following message displays in the PM status bar: PPS table deleted successfully.
3-22
Figure 3-20. Deleting the Test Table
Tip: You do not have to click Apply to delete a table from the PM database. 5. Repeat the same steps to remove the Memory IC table. Upon completion, the Create/Update/Delete Parametric Tables dialog box resembles the following graphic:
3-23
Using PM Administrator Inserting Parametric Tables from ASCII
Figure 3-21. Deleting the Memory IC Table
Inserting Parametric Tables from ASCII

PMA software also allows insertion of an ASCII file that contains one or more tables with predefined parameters. In the following procedure, use the Parametric Tables dialog boxes to create the Capacitor and Resistor folders and tables by inserting ASCII files: 1. Click the Insert tab in the Parametric Tables window. The Insert Parametric Tables dialog box displays. Use this dialog box to add the Capacitors table and associated parameters to the PM database. 2. Click the File Browse icon and navigate to the following directory:
<drive>:\<SDD_HOME>\wg\tutorial\LibMgr\cap_tables.txt
3. Select the cap_tables.txt file.

3-24
4. Click Open on the dialog box and the bottom half of the Insert Parametric Tables dialog box displays a PM Classification Tree folder. Figure 3-22. Insert Parametric Tables Dialog Box
5. Open the PM Classification Tree and the Capacitors sub-folder by clicking the + to the left of the folder or double clicking on the folder name in the lower half of the Parametric Tables window. After opening all the folders, the following tables display: Axial Radial Surface Mount
3-25
Figure 3-23. Inserting Parametric Tables into an ASCII File
6. Select the Axial, Radial, and Surface Mount tables by holding down the shift key and clicking in each table name. 7. Click Apply in the Insert Parametric Tables dialog box. The software inserts these tables into the PM database and displays the following message in the status bar: Parametric tables inserted successfully. Note After inserting tables into the PM database, the associated icons change color from blue to red (indicating that these tables are already in the PM database). Only the tables were selected, not the Capacitors folder. The software inserted the Capacitors folder into the database with the tables.
3-26
Figure 3-24. Displaying Successful Parametric Table Insertion into an ASCII File
1. Click the File Browse icon in the lower half of the Parametric Tables window and navigate to the directory where the software is loaded. Note that the browser points to the same directory that contained the cap_tables.txt file. 2. Click the res_tables.txt file and click Open in the Open dialog box. When you click OK, the bottom half of the Parametric Tables window displays a PM Classification Tree folder. 3. Select the PM Classification Tree in the lower half of the Insert Parametric Tables dialog box. 4. Click Apply in the Parametric Tables window to insert the Resistor folder and associated tables into the PM database.
3-27
5. Open the PM Classification Tree folder and the Resistor folder to display the Axial, Radial, and Surface Mount tables.
Figure 3-25. Displaying Successful Parametric Table Insertion into an ASCII File
Tip: The blue star on the Capacitors and Resistors folder in the upper half of the Parametric Tables window indicates that all tables in the folder contain identical parameters. Since the parameters are identical, you can perform searches at the folder level and at the table level. 6. Click Cancel or the Quit icon in the upper right corner of the window to close the Parametric Tables dialog boxes and return to the PMA window.
3-28
Using PM Administrator Adding Part Numbers to the PM Database
Adding Part Numbers to the PM Database

Parts Manager Administrator (PMA) provides the ability to add part numbers to the PM database using the Create/Update Parametric Data dialog box. Use the following procedure to add part numbers to the PM database: 1. Click the PPS Data icon on the icon bar to invoke the Parametric Data window.
The Parametric Data window contains two halves. The upper half displays the PM Classification Tree and the lower half displays the Create/Update, Insert, Extract, and Delete tabs. 2. Click the Create/Update tab in the lower half of the Parametric Data window. The Create/Update Parametric Data dialog box displays. 3. Select the Logic IC table from the PM Classification Tree in the upper half of the Create/Update Parametric Data dialog box. The associated parameters display in the lower half of the dialog box.
3-29
Figure 3-26. Using Create/Update Parametric Data Dialog Box to Manually Add Part Numbers to the PM Database
4. Click in the Part Numbers field in the lower half of the Create/Update Parametric Data dialog box and key in the following: 9999 5. Click in the Value column on the Cost row in the Parameters field to select the Cost parameter. The entire row highlights (blue) and the column displays in white. 6. Key in the following for the cost (in the Value column): 1 7. Select the Description parameter and key in the following text in the Value column: Test description
3-30
Figure 3-27. Adding a Parameter and Value to a Parametric Table
8. Click Apply to save the part number and parametric information to the PM database. The status bar displays the following message: Part number inserted successfully.
3-31
Figure 3-28. Updating Part Number Information in the PM Database
9. Click in the Part Numbers field and key in the following: 100-1000000-001 All of the values for the parametric data from part number 9999 display in the lower half of the Create/Update Parametric Data dialog box. This provides a quick method to add parametric data to a new part number. 10. Enter the following data in the Parameters table: Table 3-1. Entering Parameters and Values for a Part Number Field Name Cost Description Key in 1.25 74F244 Octal Buffer/Driver
3-32
Using PM Administrator Deleting Part Numbers from the PM Database
11. Click Apply to save the part number and parametric information to the PM database. The status bar displays the following message: Part number inserted successfully. 12. Click Cancel or click the Quit icon to close the Create/Update Parametric Data dialog box.
Deleting Part Numbers from the PM Database

Use the Create/Update Parametric Data dialog box to remove a part number from the Parts Manager (PM) database. Note To remove multiple part numbers from the PM database, use the Delete Parametric Data dialog box. Use the following procedure to remove one of the part numbers you added in a previous procedure: 1. Click the PPS Data icon to display the Parametric Data window.
2. Click the Create/Update tab in the lower half of the Parametric Data window. The Create/Update Parametric Data dialog box displays. 3. Select the Logic IC table from the PM Classification Tree in the upper half of the Parametric Data window. Tip: The Logic IC table may be selected when you open the Parametric Data window because the software defaults to the last selection in this window. As long as the current PM session is active, the software selects the last selected item and the last tab that was active in the Parametric Data and Parametric Tables windows. 4. Select part number 9999 from the drop down list in the Part Numbers field. The software displays the PPS data associated with part number 9999. 5. Click the Delete Part Number icon to delete the part number from the PM database. The status bar displays the following message: Part number deleted successfully.
3-33
Using PM Administrator Inserting PPS Data into the PM Database
Figure 3-29. Deleting a Part Number from the Create/Update Parametric Data Dialog Box
Note Even though the part number was deleted from the PM database, its values display in the window. You can apply those values to another part number in the same table. If you close the Parametric Data window and reopen it, the values remain displayed. The values disappear when you refresh the display by selecting another table in the PM Classification Tree.
Inserting PPS Data into the PM Database

PMA software also allows "bulk loading" of parametric part selection (PPS) data to the Parts Manager (PM) database from an external source, such as a properly formatted ASCII file (in PM or tab-separated value format).
3-34
Use the following procedure to access an ASCII file and import three part numbers and corresponding PPS data into the PM database: 1. Click the Insert tab in the Parametric Data window and the Insert Parametric Data dialog box displays. Use this dialog box to insert part numbers and their associated parametric (PPS) data into the PM database. Note The dialog box contains two halves. However, the lower half allows you to specify a PPS file. Two other fields, Exclude and Include, also display. 2. Click the File Browse icon in the lower half of the dialog box (to invoke the Open dialog box) and navigate to the directory where you loaded the Mentor Graphics tools. 3. Browse to the following directory: <SDD_HOME>\wg\tutorial\LibMgr 4. Select the cap_pps.txt file. 5. Click Open in the Open dialog box; six part numbers display in the Exclude field.
3-35
Figure 3-30. Selecting Part Number Data for Insertion into the PM Database
6. Click the Move all items icon to transfer the part numbers from the Exclude field to the Include field.
3-36
Figure 3-31. Inserting Part Number Data into the PM Database
7. Click Apply; the software inserts the six part numbers into the PM database. The status bar displays the following message: Insertion successful. The part numbers no longer display in the Include field.
3-37
Figure 3-32. Successful Insertion of Part Number Data into the PM Database
Note Do not select a table to insert the data into because the PPS data is in PM format. If the PPS data is in tab-separated value (TSV) format, select a specific table that receives the parametric data. 8. Click Cancel or the Quit icon on the Insert Parametric Data dialog box to return to the Parts Manager Administrator window. 9. Click File > Exit or the Exit icon window. to close the Parts Manager Administrator
3-38
Using PM Administrator Modifying the Central Library
Modifying the Central Library

A central library that supports a manufacturing process is never stagnant because the manufacturing process is constantly enhanced and refined. For that reason, the central library must undergo modification from time to time. The modifications usually consist of adding additional properties or partitions. Use the following procedure to modify the existing central library (.lmc) file by creating extra properties and partitions. Once they are created, populate the new partitions with data. 1. Click the Property Definition Editor icon on the Library Manager interface to invoke the Property Definition Editor. The Property Definition Editor dialog box displays. 2. Click the New Property icon. The software creates a new user property called New Property1, scrolls the property list to the end, and automatically highlights the new property. Figure 3-33. Property Definition Editor Dialog Box
3. Click the check box in the Place property in schematic when Packager or Place Device is used column to enable this option.
3-39
4. Click the property name (New Property1) to enable editing in this field. 5. Rename the property from New Property1 to Cell Name. 6. Click Advanced to enlarge the Property Definition Editor dialog box. 7. Select the Parts Manager option in the Include selected property in property lists for field. Tip: Selecting the Parts Manager option ensures that this property appears in the Property dropdown list in the Parametric Tables dialog box in Parts Manager (PM). Verify that the Cell Name property attributes match Figure 3-34: Figure 3-34. Expanded Property Definition Editor Dialog Box With Cell Name Property Attributes Selected
8. Click OK to save the new property and close the Property Definition Editor dialog box.
3-40
Creating Symbol Partitions

Use the following steps to create new symbol partitions in the active central library using the Library Manager interface: 1. Click the Setup > Partition Editor command in the Library Manager interface. The Partition Editor dialog box displays. 2. Using the Symbols tab, click the New Partition icon from New to Capacitor. and change the partition name
3. Add another new symbol partition to the library named Resistor using the same methodology. 4. Click on the Library Partition Name column heading to sort the partitions. Verify that the partitions match Figure 3-35. Figure 3-35. Partition Editor Dialog Box (Symbols Tab)
5. Click Apply to save the Symbol partition changes. The software creates the new symbol partitions in the active central library file.
Creating a Cell Partition

Use the following steps to create a cell partition in the active central library:
3-41
Tip: You can also create a cell partition from the Project workspace tab in the Library Navigator Tree. See Creating Cell Partitions from the Project Workspace Tree on page 2-15 for more information. 1. Click on the Cells tab and add a new cell partition named SM. Figure 3-36. Partition Editor Dialog Box (Cells Tab)
2. Click Apply to save the partition changes. The software creates the new cell partition in the active central library file.
Creating a Parts Partition

Use the following steps to create a Parts (formerly PDB) partition in the active central library: You can also create a Parts partition from the Project workspace tab in the Library Navigator Tree. See Creating a Part Partition from the Project Workspace Tree on page 2-16 for more information. 1. Click the Parts tab in the Partition Editor dialog box and add two new part partitions called Capacitor and Resistor.
3-42
Figure 3-37. Partition Editor Dialog Box (Parts Tab)
2. Click OK to save the partition changes and close the Partition Editor dialog box. The software creates the new Part partitions in the active central library file. The Library Manager interface displays.
Using Library Services to Import Symbols

Use the Library Services dialog box to import symbols into the symbol partitions you just created. See Using Library Services to Import DC/DV-Expedition Flow Symbols on page 2-25 for more information. 1. Click the Library Services icon ; the Library Services dialog box displays.
2. Click the Symbols tab in the Library Services dialog box. The Symbols dialog box displays. 3. Set the Operation field to Import and the Import From field to ASCII file. 4. Click on the Browse icon in the Import From field and navigate to the directory where the Mentor Graphics tools are loaded. 5. Browse to the following folder: <SDD_HOME>\wg\tutorial\LibMgr 6. Select the cap_slb.txt file. 7. Click Open in the navigator dialog box; the Symbols in ASCII file field contains a symbol.
3-43
Figure 3-38. Selecting a Symbol and Associated Data Using Library Services
8. Click the Include All icon to move the symbol from the Symbols in ASCII File field to the Symbols to Import field. 9. Click Apply to import the symbols into the selected partition.
3-44
Figure 3-39. Importing a Symbol and Associated Data Using Library Services
Using Library Services to Import Padstacks

Use the Library Services dialog box to import padstacks as outlined in the following steps: 1. Click the Padstacks tab in the Library Services dialog box to display the Padstacks dialog box. 2. Set the Operation field to Import and the Import From field to ASCII file. 3. Click the Browse icon Graphics tools. and navigate to the directory where you loaded the Mentor
4. Browse to the following folder: <SDD_HOME>\wg\tutorial\LibMgr

3-45
5. Select the sm_pad.txt file. 6. Click Open in the navigator dialog box; the Parts in ASCII file field displays two padstack names. Figure 3-40. Selecting Padstacks and Associated Data Using Library Services
7. Click the Include All icon to move the two padstacks from the Padstacks in Import Partition field to the Padstacks to Import field. 8. Click Apply to import the padstacks into the specified partition in the active central library.
3-46
Figure 3-41. Importing Padstacks and Associated Data Using Library Services
Using Library Services to Import Cells

Use the Library Services dialog box to import cells into the cell partitions you just created: 1. Click the Cells tab in Library Services and the Cells dialog box displays. 2. Set the Operation field to Import and the Import from field to ASCII file. 3. Click the Browse icon Graphics tools. and navigate to the directory where you loaded the Mentor
4. Browse to the following folder: <SDD_HOME>\wg\tutorial\LibMgr
3-47
5. Select the sm_cell.txt file. 6. Click Open in the navigator dialog box; the Parts in ASCII file field displays two cell names. Figure 3-42. Selecting Cells and Associated Data Using Library Services
7. Set the Current Partition dropdown box to SM. 8. Click the Include All icon to move the two cells from the Cells in ASCII file field to the Cells to import field. 9. Click Apply to import the cells into the selected partition as shown in the following figure:
3-48
Figure 3-43. Importing Cells and Associated Data Using Library Services
Using Library Services to Import Parts

Use the Library Services dialog box to import part information into the partitions you just created: 1. Click the Parts tab in Library Services and the Parts dialog box displays. 2. Change the option on the Import From field from Library Database to ASCII File. 3. Click the Browse icon in the Import from field. Use the navigator dialog box to browse to the directory where the Mentor Graphics software tools reside on your machine.
3-49
4. Browse to the following directory: <SDD_HOME>\wg\tutorial\LibMgr 5. Select the cap_pdb.txt file. 6. Click Open in the navigator dialog box and the Parts in ASCII file field displays six part numbers. Verify that the Library Services dialog box matches the following figure: Figure 3-44. Selecting Parts and Associated Part Data Using Library Services
7. Change the Current Partition field from Logic Gates to Capacitor. 8. Click the Include All icon to transfer the six part numbers from the Parts in ASCII file field to the Parts to import field.
3-50
Figure 3-45. Importing Parts and Associated Part Data Using Library Services
9. Click Apply to import the part numbers into the active central library. After importing the part numbers, the software removes them from the Parts to import field and displays them in the Parts in ASCII file field. These part numbers now display in blue text (indicating that they already exist in the current library) instead of black. Note When importing part database entries into a central library from another central library, the software automatically imports the corresponding symbols, cells, and pads. When importing part data entries from an ASCII file, import all corresponding symbols, cells, and pads separately.
3-51
Using Library Services to Import Data from Another Central Library File
Use the Library Services dialog box to import part numbers and corresponding library data (symbols, cells, and padstacks) from an inactive central library file to the active central library: 1. Click the Parts tab in the Library Services dialog box (if it is not currently active). The Parts dialog box displays. 2. Set the Operation field to Import and the Import From field to Library database. 3. Click the Browse icon and navigate to the directory where you loaded the Mentor Graphics tools. 4. Browse to the following folder: <SDD_HOME>\wg\tutorial\LibMgr\small_library 5. Select the small_library.lmc central library file. 6. Click Open in the navigator dialog box; the Parts in Import Partition field displays six resistor part numbers.
3-52
Figure 3-46. Selecting Parts Data to Import from Another Central Library
7. Set the Current Partition field to Resistor using the drop down list to the right of the Current Partition field. 8. Click the Include All icon to move the six part numbers from the Parts in Import Partition field to the Parts to Import field. Ensure that you set the Mode to Copy. 9. Click Apply to import the part numbers and corresponding library data (symbols, cells, and padstacks) from the small_library.lmc file to the active central library file.
3-53
Figure 3-47. Importing Parts Data from One Central Library to the Active Central Library
Tip: The software automatically imports the corresponding symbols, cells, and pads when importing part data entries from one central library to another central library. 10. Click Close to dismiss the Library Services dialog box and return to the Library Manager interface.
3-54
Using PM Administrator Adding Parametric Data to Parts
Adding Parametric Data to Parts

A library that supports a manufacturing process is constantly enhanced and refined. Therefore, you must modify the Parts Manager (PM) database to reflect these changes. The most common database modifications include adding parameters and modifying existing parameters in the database. In this procedure, use Parts Manager Administrator software to modify the existing PM database by exporting PPS data, deleting PPS data, adding additional parameters, importing the deleted PPS data, and inserting PPS data to parts:
Viewing a Parametric Table

1. Click the Parts Manager icon on the Library Manager interface to invoke Parts Manager Administrator (PMA) software. The PMA window displays. 2. Click the PPS Tables icon on the icon bar and the Create/Update/Delete Parametric Tables dialog box displays by default. 3. Select the Logic IC table in the PM Classification Tree. The following message displays in the PMA status bar: Parts exist in table - you are not allowed to edit this table. Tip: Tables that contain PPS data cannot be edited using the Parametric Tables dialog box. Remove all PPS data from the table by exporting the data to a file and then deleting it.
Exporting Parametric Data to an ASCII File

Export parametric data in the Logic IC table to an ASCII file using the following steps: 1. Click the PPS Data icon on the icon bar in the PMA window; the Create/Update Parametric Data dialog box displays by default. Note The Parametric Data dialog box displays on top of the Parametric Tables window and becomes the active dialog box. 2. Click the Extract tab to display the Extract Parametric Data dialog box. The dialog box contains two halves. The lower half displays a field for a PPS file, some file formatting fields, and the Exclude and Include fields. 3. Select the Logic IC table in the PM Classification Tree. The single part number associated with this table displays in the Exclude field.
3-55
Figure 3-48. Selecting a Part Number to Extract from the Database
4. Type the following in the File field: logic_ic.txt 5. Click the Move All Items icon the Include field. to move the part number from the Exclude field to
Note If you do not type a path in the File field, the software creates the file in the default working directory defined in the Parts Manager Configuration dialog box in Figure 3-3 on page 3-5).
3-56
Figure 3-49. Extracting a Part Number from the Database to an ASCII File
6. Click Apply to transfer the part number and its corresponding PPS data to the logic_ic.txt file. After the software writes the data to the database, the following message appears in the Parts Manager Administrator status bar: Part numbers extracted successfully.
Removing Parametric Data from the PM Database

Now that you extracted (copied) the part number and corresponding parametric data associated with the Logic IC table to an ASCII file, use the Delete Parametric Data dialog box to remove the part number and parametric data from the Logic IC table using the following steps: 1. Click the Delete tab in the Parametric Data dialog box; the Delete Parametric Data dialog box displays. The dialog box contains two halves. The lower half contains the Exclude and Include fields.
3-57
Figure 3-50. Delete Parametric Tables Dialog Box
2. Select the PM Classification Tree; seven part numbers display in the Exclude field. They represent all part numbers that currently reside in the PM database.
3-58
Figure 3-51. Displaying all Part Numbers in the PM Database
3. Select the Logic IC table; only one part number displays in the Exclude field.
3-59
Figure 3-52. Selecting a Part Number to Delete from the Logic IC Table
4. Click the Move All Items icon the Include field.
to move the part number from the Exclude field to
3-60
Figure 3-53. Deleting a Part Number from the Logic IC Table
5. Click Apply to delete the part number and its corresponding PPS data from the Logic IC table. After the software deletes the data, the following message displays in the status bar: Delete successful. Notice that the part numbers no longer display in the Include field. However, the part number in the part database is not deleted.
3-61
Figure 3-54. Logic IC Table With Part Number Deleted
Adding a Parameter to the Parametric Table

Now that you have removed part number and parametric part selection (PPS) data from the parametric table, use the following steps to add a parameter to the parametric table: 1. Click the PPS Tables icon on the PMA toolbar. The Create/Update/Delete Parametric Tables dialog box becomes active and displays it in front of the Delete Parametric Data dialog box. Note Before performing the following step, select the PM Classification Tree and then select the Logic IC table. This enable the PMA software to read the changes you made to the database using the Delete Parametric Data dialog box.
3-62
2. Click and highlight the new parameter name (param name) and key in the following: Cell Type 3. Click in the Property column to enable the dropdown list and map the new Cell Type parameter to the Cell Name property. Click in the middle of the column or on the left side of the column; the dropdown list displays (or click on the right side of the column to display the dropdown list). 4. Highlight 221 - Cell Name from the list of properties in the pulldown. Note When mapping a parameter to a property, the horizontal scroll bar may move to the right. After mapping the parameter, the first column that appears is the Type column. Use the scroll bar to display the first column (Name). 5. Click the Move Down icon to move the Cell Type parameter to the bottom of the Parameters list. 6. Ensure that the list of Parameter names are in the following order: Cost Description Cell Type
Use the Move Up and Move Down icons to put the parameter names in the proper order. 7. Click Apply to save the table modifications. 8. Click Yes on the subsequent dialog box. The following message appears in the dialog box: PPS table created successfully.
3-63
Figure 3-55. Adding a Parameter to a Parametric Table
9. Click Cancel
to close the Create/Update/Delete Parametric Tables dialog box.
Importing Parametric Data into the Table

Use the following steps to import part number and PPS data you extracted to the logic_ic.txt file to the modified parametric table: 1. Click the Parametric Data dialog box to make it active and select the Insert tab. The Insert Parametric Data dialog box displays. 2. Select the Logic IC table in the PM Classification Tree.
3-64
Figure 3-56. Selecting a Table to Receive Parametric Data
3. Click the File browse icon;
the Open dialog box displays.
4. Select the logic_ic.txt file and click Open. The software loads the PPS data from the previously exported logic_ic.txt file into the Exclude field.
3-65
Figure 3-57. Selecting Part Number Data to Import from an ASCII File
5. Click the Move All Items icon the Include field.
to move the part number from the Exclude field to
3-66
Figure 3-58. Inserting a Part Number into the Logic IC Table
6. Click Apply; the software imports the part number and its corresponding PPS data into the Logic IC table. Upon completion, the following message displays in the Parts Manager Administrator status bar. Insertion successful. The part number no longer appears in the Include field.
3-67
Figure 3-59. Successful Part Number Insertion into the Logic IC Table
Updating the Part Number in the PM Database

Use the following procedure to update the part number you just inserted into the PM database: 1. Click the Create/Update tab to display the Create/Update Parametric Data dialog box and select the Logic IC table from the PM Classification tree in the upper half of the dialog box. 2. Select part number 100-1000000-001 from the dropdown list in the lower half of the Create/Update Parametric Data dialog box.
3-68
Figure 3-60. Parameters Associated With a Part Number
3. Select the Value column in the Cell Type row and key in SM. 4. Click Apply to save the PPS data modifications. The PMA status bar displays the following message: Part number updated successfully.
3-69
Using PM Administrator Using the Parts Manager Validation Utility
Figure 3-61. Part Number With a New Parameter Added to the PM Database
5. Click Cancel to close the Create/Update Parametric Data dialog box and exit out of PMA.
Using the Parts Manager Validation Utility

The Parts Manager Validation (PM Validate) Utility compares the parametric part selection (PPS) data in the PM database against the property settings in the Property Definition Editor (CentLib.prp file). The software records any discrepancies to the PMValidate.txt file. Use the following procedure to modify a property in the CentLib.prp file, execute the PM Validation Utility (to generate errors), correct the errors, and execute the PM Validation Utility again to verify that all discrepancies are resolved.
3-70
Invoking the Parts Manager Validation Utility

1. Click the Parts Manager icon on the Library Manager interface to invoke the Parts Manager Administrator software. 2. Select Tools > Parts Manager Validation from the Parts Manager Administrator menubar to invoke the PM Validation Utility. Figure 3-62. Tools Menu Showing Parts Manager Validation Command
The validation software starts after you select the command. The following message displays in the status bar when the utility completes the validation process: Parts Manager Validation complete. See PmValidate.txt in your working directory for results. 3. Click the View Log icon displays. to invoke the File Viewer. The File Viewer window
4. Select the PmValidate.txt file from the left half of the File Viewer window. The PmValidate.txt file opens in the right half of the window. The first line after the file headers indicate the table where the problem exists. Messages, such as Capacitors\Axial\, indicates that the PM Validation Utility validated against the Axial table in the Capacitors folder. The first warnings for this table are:
Parameter 'Tolerance' is not the same length as the property that it maps to Parameter length:10 Property length:127 Parameter 'Cell Type' is not the same length as the property that it maps to Parameter length:6 Property length:132
The next warnings appear separately in the table.

Property mapping for parameter 'Mfg' does not exist in the Central Library Property mapping for parameter 'Mfg Part No' does not exist in the Central Library
These warnings state that, for the given parameters, the property that they are mapped to do not exist in the CentLib.prp file. The first warning indicates the Mfg parameters corresponding property does not exist in the CentLib.prp file. The remaining warnings are the previous four warnings which occurred in subsequent tables.
3-71
5. Click the Quit icon
to dismiss the File Viewer window.
Correcting Problems Detected by the Parts Manager Validation Utility

Use the following steps to correct problems resulting from the PM Validation Utility: 1. Click the PPS Tables icon dialog box. to invoke the Create/Update/Delete Parametric Tables
2. Double-click on the Capacitors folder in the PM Classification Tree to open it. 3. Highlight the Axial table. Note The Tolerance parameter is mapped to the Tolerance property. View the Cell Type parameter and note that it is mapped to the Cell Name property.
Using the Property Definition Editor to Correct Tolerance Property Problems

To resolve the four warnings in the PmValidate.txt file, use the Property Definition Editor to modify the CentLib.prp file using the following steps: 1. Click the Property Definition Editor icon on the Library Manager interface to invoke the Property Definition Editor. The Property Definition Editor dialog box displays. 2. Click in the Name column header to sort the properties by name. Scroll down through the list until you find the Tolerance property. 3. Select the Tolerance property and click Advanced to expand the Property Definition Editor dialog box. 4. Change the Max Number of Characters from 127 to 10 by keying in the correct value in the Value field (to the right of the Option Attribute field).
3-72
Figure 3-63. Correcting Tolerance Property Problems Using the Property Definition Editor
5. Click Apply to save the Tolerance property changes in the Property Definition Editor dialog box.
Using the Property Definition Editor to Correct Cell Name Property Problems
Use the following steps to correct cell name property problems detected by the PM Validation Utility: 1. Double click on the Type column header to sort the properties by the type of property in reverse order. After the second click, the Cell Name user property displays at the top of the list. 2. Select the Cell Name property and change the Max Number of Characters value from 132 to 6 in the Value field (to the right of the Option Attribute field).
3-73
Figure 3-64. Correcting Cell Name Property Problems Using the Property Definition Editor
3. Click Apply to save the Cell Name property changes in the Property Definition Editor dialog box.
Using the Property Definition Editor to Add Properties

To correct the last two warnings detected by the PM Validation Utility, use the Property Definition Editor to add two additional properties (Mfg and Mfg Part No). 1. Click the New property icon properties. in the Property List two times to add two additional
3-74
Figure 3-65. Adding a New Property Using the Property Definition Editor
2. Change the name of NewProperty1 to Mfg and change the Max Number of Characters value from 132 to 50. 3. Click on the Parts Manager option in the Include Selected Property in Property Lists For field. This enables the property to be displayed in Parts Manager dialog boxes.
3-75
Figure 3-66. Enabling the Parts Manager Option in the Property Definition Editor
4. Change the name of NewProperty2 to Mfg Part No. Change the Max Number of Characters value from 132 to 30 and select the Parts Manager option.
3-76
Figure 3-67. Setting Up a New Property in the Property Definition Editor
5. Click OK in the Property Definition Editor dialog box to save property changes and close the dialog box.
Using PM Administrator to Correct Property Problems

Use the following procedure to correct property problems detected by the PM Validation Utility using the PMA dialog boxes: 1. Return to the Parts Manager Administrator window, invoke the PM Validation Utility, and open the PmValidate.txt file in the file viewer. Note The PM Validation Utility saves the last PmValidate.txt file by renaming it to PmValidate.bak. If a PMValidate.bak file already exists, the software overwrites the existing file. The PM Validation Utility generates a new error which appears in the Logic IC table: Parameter 'Cell Type' is not the same length as the property that it maps to Parameter length:132 Property length:6 Use Parts Manager Administrator software to remap the Cell Name property to the Cell Type parameter in the Logic IC table.
3-77
2. Select the Logic IC table on the PM Classification Tree in the upper half of the dialog box. The following message displays in the status bar: Parts exist in table table. you are not allowed to edit this
3. Export the PPS data from the Logic IC table into a file and delete the PPS data using appropriate steps in Adding Parametric Data to Parts on page 3-55. 4. Click the PPS Tables icon box displays. and the Create/Update/Delete Parametric Tables dialog
5. Click Apply to save the Logic IC table changes in the Create/Update/Delete Parametric Tables dialog box. 6. Click OK in the subsequent dialog box to confirm the save. Figure 3-68. Parametric Tables With Table Changes Saved
7. Click the PPS Data icon
to activate the Parametric Data dialog boxes.
3-78
Using PM Administrator Moving Data Between the PM Database and Parts
8. Re-import the PPS data into the Logic IC table using the appropriate steps of Adding Parametric Data to Parts on page 3-55.
Re-invoking the Parts Manager Validation Utility

Use the PM Validation Utility to verify that the parametric part selection (PPS) data in the PM database match the property settings in the Property Definition Editor (CentLib.prp file) based on the corrections you have made: 1. Select Tools > Parts Manager Validation from the Parts Manager Administrator menubar to invoke the PM Validation Utility. The validation software starts after you select the command. 2. Open the PMValidate.txt file in the File Viewer. The PMValidate.txt file displays the following message: No errors detected. 3. Close the File Viewer and the Parts Manager Administrator window.
Moving Data Between the PM Database and Parts

Because Parts Manager (PM) does not contain symbol or cell information, the software must work closely with the Parts files to ensure that each library part contains the correct parametric information. The parametric information can reside in a parts database file (in the active central library) in the form of properties, in the PM database as parametric part selection (PPS) data, or in both places. Use the Parts Manager (PM) Batch Update Utility software to transfer data between the parts database files and the PM database in either part by part or batch mode. Use the following procedure to create part numbers in the PM database using part data, transfer PPS data from the PM database to the part database files, and execute the PM Batch Update Utility:
Using PM Administrator to Create Part Numbers

Use the following steps to create part numbers in PMA: 1. Click the Parts Manager icon on the Library Manager interface to invoke the Parts Manager Administrator (PMA) software. The PMA window displays. 2. Click the PPS Data icon box displays. on the icon bar; the Create/Update Parametric Data dialog
3. Double-click the Resistors folder in the PM Classification Tree (in the upper half of the Create/Update Parametric Data dialog box) to open the Resistor folder.
3-79
4. Select the Surface Mount table on the PM Classification Tree (in the upper half of the Create/Update Parametric Data dialog box). 5. Click the Create Part Numbers from PDB icon in the Create/Update Parametric Data dialog box. The Create Part Numbers from PDB dialog box displays. Figure 3-69. Create Parts Numbers from PDB Dialog Box
6. Select Resistor from the drop down list in the PDB Partition field. Six part numbers display in the Exclude field.
3-80
Figure 3-70. Part Numbers Associated With the Resistor Partition
7. Click the Move all items icon to the Include field.
to move the six part numbers from the Exclude field
Figure 3-71. Selecting Part Numbers in the Create Part Numbers from PDB Dialog Box
3-81
8. Click OK; the software creates entries in the PM database based on the six part numbers. The Create Part Numbers from PDB dialog box disappears and the following message appears in the Parts Manager Administrator status bar: Create part numbers from PDB common properties successful. Figure 3-72. Creating Part Numbers from PDB Data
The software adds the six part numbers to the database in the selected table with values from the Part that are mapped through a common property (in the Property Definition Editor). When creating part numbers from the part, if any PPS parameters are mapped to properties that are in the part and these properties have values, then the PPS parameters also receive the same values.
3-82
Note The Create Part Number from PDB function can fail due to the following conditions: - If the part is missing some PDB component properties that are mapped to required parameters for the part in PM, or - The Part properties exist but are not toggled in the PM Configuration dialog box. This software will not copy the Part properties to the PM database and, if the parameter is required, the function fails. The Parts Manager Administrator log file (PmAdmLog.txt) contains information for each part number that could not be created. 9. Select 800-3000000-001 from the Part Numbers drop down field. Note that some PPS data displays in the dialog box. Figure 3-73. Viewing PPS Data With Part 800-3000000-001
3-83
Note When creating part numbers from the parts database data, if any PPS parameters are mapped to properties that are in the parts database and these properties have values, then the PPS parameters also receive the same values.
Applying Part Number Information to the Parts Database Editor

Use the Parts Database Editor in Library Manager to ensure that part number information from PM is correctly applied to parts database information in the active central library. 1. Click the Parts Database icon in the Library Manager interface to invoke the Parts Database Editor. 2. Select Logic Gates in the Partition field. 3. Return to the Parts Manager Administrator window and, in the Create/Update Parametric Data dialog box, select the Logic IC table in the PM Classification Tree. 4. Select part number 100-1000000-001 from the dropdown list in the Part Numbers field.
3-84
Figure 3-74. Viewing PPS Data With Part 100-1000000-001
5. Select the Update This Part Number in the PDB Upon Apply option and click Apply. The software modifies the part number in the Logic Gates PDB. The following message displays in the Parts Manager Administrator status bar: Updating Central Library When the cursor returns to its normal state, the following message displays in the status bar: Errors occurred during create/update operation, Consult log file.
3-85
Figure 3-75. Error Condition When Updating Part Numbers in the PDB
6. Click the View Log icon on the toolbar. The PmAdmLog.txt file displays in the File Viewer. The file contains header information (title, version, and date) and the following transcript.
Creating part numbers from PDB 800-3000000-001 800-3000000-002 800-3000000-003 800-3000000-004 800-3000000-005 800-3000000-006 Update part number 100-1000000-001 Unable to open PDB file for this part number Unable to update part number in PDB
3-86
Note The PmAdmLog.txt file lists the six part numbers that were created using the Creating Part Numbers from PDB procedure. The log then lists the step Update Part Number. This step is followed by the part number and a status of the operation. The log file states that the PDB file for the part number could not be opened. Since the Logic Gates PDB file was open in the Part Editor, PM software could not update the parts database entry. 7. Click the Quit icon 8. Exit the Part Editor. 9. Return to PMA and click Apply in the Create/Update Parametric Data dialog box. The PMA status bar displays the following message. Part number updated successfully. Figure 3-76. Updating Part Numbers in the PDB from the Create/Update Parametric Data Dialog Box in the upper right hand corner to dismiss the File Viewer.
3-87
Using the Part Editor to Verify Updates

Use the Part Editor dialog box to view the updates you just made in the Part using the following steps: 1. Invoke the Part Editor from the Library Manager interface. 2. Select part number 100-1000000-001 in the Logic Gates partition. Verify that the Part Editor matches Figure 3-77: Figure 3-77. Parts Database Editor Dialog Box
3-88
Using PM Administrator Using the PM/PDB Synchronization Utility
Using the PM/PDB Synchronization Utility

The Parts Manager PM to PDB Synchronization Utility synchronizes data stored in the PM database with PDB part number properties in the Parts partition of the central library. This utility transfers data from one location to the other for each part number that exists in the PM database, or in the Parts partitions in the active central library. You can execute the PM/PDB Synchronization Utility from a dialog box or by keying in command strings from an MS-DOS prompt. In this exercise, you will execute the PM/PDB Synchronization Utility using the dialog box. For information on executing this utility from the keyboard, consult the Parts Manager Process Guide. Use the PM/PDB Synchronization Utility to copy PPS data mapped to properties from the PM database to parts database files: 1. Exit Parts Manager Administrator software. The PM/PDB Synchronization Utility will not execute when PMA software is running. 2. Using file management software on your machine, browse to the following directory: <drive>:\<SDD_HOME>\wg\win32\bin 3. Double-click the PmPdbSync.exe to execute the PM/PDB Synchronization Utility. The Open dialog box displays. 4. Select the Company_Library.lmc file (the active central library file). Figure 3-78. Open Dialog Box (PM/PDB Synchronization Utility)
5. Click Open and the Parts Manager PM/PDB Synchronization dialog box displays:
3-89
Using PM Administrator Using the PM/PDB Synchronization Utility
Figure 3-79. Parts Manager PM/PDB Synchronization Dialog Box
6. Select the Update PDB with PM Data option. This instructs the software to synchronize PPS data in the PM database with parts database data in the Parts partition of the active central library. 7. Click OK; the software begins the synchronization process. The PM/PDB Synchronization Utility creates the PMPdbSync.txt log file in your working directory and writes results of the synchronization process to this file. Upon completion, the PmPdbSync.txt file displays in the File Viewer. The following text displays:
Processing classification path: Capacitors\Axial\ No part numbers in this classification. Processing classification path: Capacitors\Radial\ No part numbers in this classification. Processing classification path: Capacitors\Surface Mount\ 900-2000000-001 In partition Capacitor Changing property 'Value' from '0.0000000000049' to '4.9E-012' Added property 'Cell Name' value '0805' Added property 'Mfg' value 'Kemet' Added property 'Mfg Part No' value 'C0805C479K5G' Added property 'Cost' value '0.001' 900-2000000-002 In partition Capacitor Changing property 'Value' from '0.0000000000049' to '4.9E-012' Added property 'Cell Name' value '0805' Added property 'Mfg' value 'Kemet' Added property 'Mfg Part No' value 'C0805C479K1G' Added property 'Cost' value '0.001' 900-2000000-003 In partition Capacitor Changing property 'Value' from '0.0000000000049' to '4.9E-012' Added property 'Cell Name' value '0805' Added property 'Mfg' value 'Kemet' Added property 'Mfg Part No' value 'C0805C479K2G' Added property 'Cost' value '0.001' 900-2000000-004 In partition Capacitor Changing property 'Value' from '0.000000000068' to '6.8E-011' Added property 'Cell Name' value '0603'
3-90
Using PM Administrator Using the Parts Manager Batch Update Utility Added property 'Mfg' value 'Kemet' Added property 'Mfg Part No' value 'C0603C680K1G' Added property 'Cost' value '0.001' 900-2000000-005 In partition Capacitor Changing property 'Value' from '0.000000000068' to '6.8E-011' Added property 'Cell Name' value '0603' Added property 'Mfg' value 'Kemet' Added property 'Mfg Part No' value 'C0603C680K2G' Added property 'Cost' value '0.001' 900-2000000-006 In partition Capacitor Changing property 'Value' from '0.000000000068' to '6.8E-011' Added property 'Cell Name' value '0603' Added property 'Mfg' value 'Kemet' Added property 'Mfg Part No' value 'C0603C680K5G' Added property 'Cost' value '0.001' Processing classification path: Resistors\Axial\ No part numbers in this classification. Processing classification path: Resistors\Radial\ No part numbers in this classification. Processing classification path: Resistors\Surface Mount\ 800-3000000-001 In partition Resistor No changes to part number 800-3000000-002 In partition Resistor No changes to part number 800-3000000-003 In partition Resistor No changes to part number 800-3000000-004 In partition Resistor No changes to part number 800-3000000-005 In partition Resistor No changes to part number 800-3000000-006 In partition Resistor No changes to part number Processing classification path: Logic IC\ 100-1000000-001 In partition Logic Gates No changes to part number 6 part numbers updated
8. Close the PmPdbSync.txt file in File Viewer upon completion.
Using the Parts Manager Batch Update Utility

Parts Manager (PM) software features the Parts Manager Batch Update (PM Batch Update) Utility (PmBatch.exe) which allows edits of the Parts Manager database in batch mode. Also, use the PM Batch Update Utility to update or insert part numbers and/or parametric data in the PM database.
3-91
Using PM Administrator Using the Parts Manager Batch Update Utility
In this procedure, use the PM Batch Update Utility to update some existing parametric values and insert some new part numbers in the PM database using both text format options (ASCII and Tab-Separated Value, or TSV). 1. Invoke Parts Manager Administrator and click the PPS Data icon The Create/Update Parametric Data dialog box displays. 2. Select the Logic IC table in the PM Classification Tree. 3. Select 100-1000000-001 from the Part Numbers drop down list. Figure 3-80. Verifying Parameters Associated With Part Number 100-1000000001 on the toolbar.
4. Close the Parts Manager Administrator window after verifying that the parameters are correct.
3-92
5. Invoke an MS-DOS window and go to the directory where Parts Manager Administrator software is loaded. <drive>:\..\<SDD_HOME>\wg\win32\bin You execute the PM Batch Update Utility by keying in the appropriate usage statement. The following syntax illustrates how to execute the PM Batch Update Utility using the ASCII text format: pmbatch -pm=<pmppsfile> -centrallib=<librarypath> -mode=<insert|update> -pdb <pmppsfile> is the full path to the data file that the utility reads. The pmppsfile format is identical to the file format when exporting PPS data from the Parts Manager database. <librarypath> is the full path to the central library file. <insert|update> is the mode that the utility executes. Update modifies existing Parts Manager part numbers. Insert adds new part numbers. -pdb is an optional argument that instructs the utility to update any parameters that are mapped to properties to be updated in the parts database file. When omitted, the utility only modifies the PPS data. 6. Key in the following at the MS-DOS prompt to update the Cell Type field for part number 100-1000000-001 in the Logic IC table and add a Cell Name property to the Logic ICs Parts partition in the central library using the PM Batch Update Utility: pmbatch -pm=<Path>\2005EXP\wg\tutorial\ LibMgr logic_pps1.txt -centrallib= <Path>\2005\wg\tutorial\ LibMgr Company_library\Company_library.lmc -mode=update -pdb <Path> is the full path to the directory where the software is loaded. The PM Batch Update Utility outputs data to the PmBatch.txt log file. The software automatically generates this log file in the working directory specified earlier in this process guide. The PMBatch.txt file should contain text similar to the following example:
Parts Manager Batch Update Version: <NUMBER> <DATE and TIME> Using central library C:\<Path>\tutorial\LibMgr\Company_library\Company_library.lmc Using update mode Updating pdb Updating part numbers from file C:\<Path>\tutorial\LibMgr\logic_pps1.txt
3-93
Using PM Administrator Using the Parts Manager Batch Update Utility 100-1000000-001 Changing Cell Type from SM to SO20 Adding part property Cell Type value SO20
The parameters for part number 100-1000000-001 should match as shown in Figure 3-81 Figure 3-81. Reverifying Parameters Associated With Part Number 1001000000-001
While updating the Cell Type parameter in the Parts Manager database, the PM Batch Update Utility adds the property Cell Type to the Logic ICs PDB file in the active central library.
3-94
Note If the PM Batch Update Utility executes with the Parts Manager Administrator software active, the software displays a message stating that the database is in use. If this occurs, exit Parts Manager Administrator and re-execute the PM Batch Update Utility. The PMBatch.txt file that contains this message is provided as an example: Parts Manager Batch Update Version: <NUMBER> <DATE and TIME>
Using central library C:\<path>\tutorial\LibMgr\Company_library\ Company_library.lmc Using update mode Database is in use by <machine>:<user> for Parts Manager Administrator If this is incorrect, execute the Parts Manager Administrator from this node and by this user. Exiting the PMA software clears this status.
7. Use the following syntax to execute the PM Batch Update Utility using the TSV (tabseparated value) text format option: pmbatch -tsv=<TSV control file> -centrallib=<librarypath> -mode=<insert|update> -pdb <TSV control file> is the full path to the data file that the utility reads. Use the TSV control file to update parts in multiple tables in the Parts Manager database by pointing to a unique TSV file for each updated table. <librarypath> is the full path to the central library file. <insert|update> is the mode that the utility executes. Update mode modifies existing PM part numbers. Insert mode adds new part numbers. -pdb is an optional argument that instructs the utility to update any parameters that are mapped to properties for update in the parts data file. If this argument is omitted, the software modifies only the PPS data. 8. Key in the following at the MS-DOS prompt type to add a new part number (1001000000-002) to the Logic IC table:
pmbatch -tsv=<Path>\tutorial\LibMgr\logic_tsv_ctl.txt -centrallib=<Path>\tutorial\LibMgr\Company_library\Company_library.lmc -mode=insert
<Path> is the full path to where Parts Manager software is loaded. The TSV control file (logic_tsv_ctl.txt) contains the following:
.FILETYPE TSV_UPDATE_CONTROL .VERSION "1.0" .FILE "C:\\<Path>\\tutorial\\LibMgr\\logic_tsv.txt" ..CLASSIFICATION "Logic IC"
<Path> is the full path to where you have Parts Manager software loaded.
3-95
The .FILE keyword calls for the file name of the TSV file. The .CLASSIFICATION keyword specifies the file where the software places the PPS data. The TSV file, logic_tsv.txt contains the following:
Part Number 100-1000000-002 Cell Type DIP20 Description 74F244 Octal Buffer/Driver Cost 1.25
The PMBatch.txt file contains the following data:

Parts Manager Batch Update Version: <NUMBER> <DATE and TIME> Using central library C:\<Path>\tutorial\LibMgr\Company_library\Company_library.lmc Using insert mode Processing file C:\<Path>\tutorial\LibMgr\logic_tsv.txt for classification Logic IC Inserting part numbers from file C:\<Path>\tutorial\LibMgr\logic_tsv.txt 100-1000000-002 Part number added to database
The parameters for the new part number 100-1000000-002 should match Figure 3-82:
3-96
Using PM Administrator Adding Attachment Data
Figure 3-82. Parameters Associated With Part Number 100-1000000-001 After Running PM Batch Update Utility
Note When executing the PM Batch Update Utility in Insert mode using the -pdb option, the software ignores the -pdb option. The utility cannot create a new parts data entry without specific symbol or cell information.
Adding Attachment Data

Parts Manager Administrator (PMA) software allows the addition of one or more attachments to a part number in the Parts Manager (PM) database. The attachment is a pointer to data available on the network (either internal or external network). An attachment can be a URL to a web address, a text file, GIF image, and executable on your machine, or any other piece of data that your system can interpret.
3-97
Use the Attachment Data dialog box to assign attachments to part numbers. Invoke this dialog box from either the Parts Manager Administrator interface or from the Parts Manager Client interface.
Adding Attachment Data to a Part

The following procedure describes how to add an attachment manually, add attachments through PPS data inserted into the PM database, and how to view the attachments. Note Attachments used in this procedure are PDF files. Use Adobe Acrobat Reader to view these attachments. 1. Invoke the Parts Manager Administrator and click the Parametric Data icon to invoke the Create/Update Parametric Data dialog box. 2. Select the Logic IC table in the PM Classification Tree. 3. Select part number 100-1000000-001 and click the Edit Attachments icon Attachment Data dialog box displays: Figure 3-83. Attachment Data Dialog Box . The
4. Click the New Attachment icon to add an attachment to part number 100-1000000-001. The software adds a text entry field in the Path column. 5. Click in the Path text entry field and a Browse icon displays.
3-98
Figure 3-84. Attachment Data Dialog Box With Description Field Highlighted
6. Click the Browse icon and navigate to the directory where you loaded the Mentor Graphics tools. 7. Browse to the following folder: \..\2005EXP\SDD_HOME\wg\tutorial\LibMgr 8. Select the 74f244.pdf file. Figure 3-85. Attachment Data Dialog Box With Valid Path Entry
9. Click OK in the dialog box and the 74f244.pdf file and directory path displayed in the Path column is saved as an attachment to part number 100-1000000-001.
Viewing Attachment Data

Use the following steps to view the data file you saved as an attachment to part number 1001000000-001 using the Attachment Data dialog box: 1. Select part number 100-1000000-001 and click the Edit Attachments icon Attachment Data dialog box displays. . The
2. Click the View Attachment icon to view the 74f244.pdf file in Adobe Acrobat Reader. The file displays in the Adobe window.
3-99
3. Dismiss the 74f244.pdf file in Adobe Acrobat Reader by exiting the Adobe window. The Attachment Data dialog box displays.
Adding a Description to Attachment Data

Use the Description field in the Attachment Data dialog box to associate a name to the attachment data. For example, to reference a titled document, enter the proper name of the document. 1. Click in the Description field; the software automatically shifts the horizontal view to show only the Description field. 2. Click in the Description field. Note that the Path field disappears. 3. Type Vendor specification in the Description field. Figure 3-86. Attachment Data Dialog Box With Description Field Displayed
4. (Optional) Click the View Attachment icon Reader. 5. Dismiss Adobe Acrobat Reader.
to view the PDF file in Adobe Acrobat
6. Click OK in the Attachment Data dialog box to save the attachment and description text to part number 100-1000000-001 in the Logic IC table. The software displays the Create/Update Parametric Data dialog box. 7. Click in the Part Numbers dropdown list in the Create/Update Parametric Data dialog box. Note that the text of part number 100-1000000-001 is blue and the text of part number 100-1000000-002 is black. The blue text indicates that the part number has attachment data associated with it.
3-100
Using PM Administrator Importing PPS Data With Attachment Data
Figure 3-87. Part Number With Associated Attachment Data
Note Click OK in the Attachment Data dialog box to automatically update the PPS data in the Logic IC table. Do not click Apply in the Create/Update Parametric Data dialog box to save an attachment.
Importing PPS Data With Attachment Data

Attachment data is stored in the PM database as parametric part selection (PPS) data. When exporting PPS data, the software exports attachment information as well. Conversely, when importing PPS data with attachments, the imported data contains attachment information. Use the following procedure to import PPS data that contains attachment information: 1. Click the Insert tab to display the Insert Parametric Data dialog box.
3-101
Using PM Administrator Importing PPS Data With Attachment Data
2. Browse to the following directory: \..\2005EXP\SDD_HOME\wg\tutorial\LibMgr 3. Select the res_pps.txt file. 4. Select the Update existing parts in database option on the Insert Parametric Data dialog box. Figure 3-88. Importing Part Numbers With Attachment Data
5. Import the resistor PPS data into the PM database using the same procedure performed earlier in this process guide. 6. Click the Create/Update tab to display the Create/Update Parametric Data dialog box. 7. Double-click on the Resistors folder in the Create/Update Parametric Data dialog box and select the Surface Mount table.
3-102
Using PM Administrator Exiting / Logging Out of PMA
8. Click in the Parts Numbers field and note that the text of all part numbers are now blue (this indicates that these part numbers have attachment data). Figure 3-89. Part Numbers With Associated Attachment Data (in Blue)
9. Click Cancel to close the Create/Update Parametric Data dialog box.
Exiting / Logging Out of PMA

Use the File > Exit command or the Exit icon in the PMA toolbar to close all open PMA dialog boxes and exit the Parts Manager Administrator (PMA) software. You must complete all work before exiting the application.
3-103
Using PM Administrator Exiting / Logging Out of PMA
3-104
Chapter 4 Implementing a Design

Introduction
Now that you have created symbols, cells and parts, use the procedures in this chapter to define a project, create a design, and place device symbols in a schematic using design entry software. This chapter also includes procedures for using Expedition PCB to link to a schematic project, compiling a PCB design, placing cells, performing gate swapping, pushing a cell, and replacing a cell. Note You must successfully complete the exercise in Using Library Manager on page 2-1 before you begin the exercise in this chapter. DC/DV-Expedition flow users are not required to complete the optional exercises in Using PM Administrator on page 3-1. If you are using DxD-Expedition flow software, go to Creating a Design in DxDesigner on page 4-13. See Managing Reusable Blocks (DC/DV-Expedition Flow) on page 4-35 for information on the Reusable Blocks Editor. Perform the procedures in the following order for the DC/DV-Expedition flow: Creating a Design Project in Design Capture on page 4-2 Placing DC/DV Symbols and Devices on page 4-6 Compiling and Packaging the DC/DV Schematic on page 4-10 Using Expedition PCB on page 4-24
Use the following flowchart (Figure 4-1) to guide you through the procedures in this section.
4-1
Implementing a Design Creating a Design Project in Design Capture
Figure 4-1. Software Tools Process Flow (DC/DV-Expedition Flow)
Note For detailed information on dialog boxes displayed during these exercises, click the online help icon or press F1.
Creating a Design Project in Design Capture

Note If you are using the Design Capture/DesignView flow, you must have Design Capture software loaded onto your machine. If you are using the DxD-Expedition flow, go to Creating a Design in DxDesigner on page 4-13. A project (.prj) file is used by design entry software (Design Capture and DesignView) and other tools, such as Expedition PCB, to define various project settings and file paths for library, schematic, and configuration files.
4-2
Tip: This process guide uses Design Capture as the design entry software tool. You can also use DesignView for design entry tasks. However, command paths may be different when using DesignView. A typical project file contains the following information: Location of the root schematic in the design. Location of the central library. Location of other design source files (schematics, state diagrams, HDLs, and so forth). Location of the central database (CDB). Location of libraries used in the design (symbols and parts). Location of configuration files used in the design. Location of ASIC/FPGA toolkits in the design. Information to facilitate integration between PCB layout and design entry tools. Information to facilitate integration between VHDL and DC. Information to facilitate integration between FPGA Synthesis and DC. Information to facilitate integration between Analog and DC.
The directory where a project file is stored is called the project directory. Unless otherwise specified, the software writes all output files created during the design process in the project directory. Note Using design entry software without an active project file is not recommended. An active project file is required for design verification, design compilation, hierarchy browsing, inter-tool communication, and several other basic functions. If you edit a schematic when a project file is not open, the software uses default configuration information.
Using the New Project Wizard to Create a Project

The following steps illustrate how to use the New Project Wizard to name a project file, specify a location for the project directory on your machine, and identify design files for the new project: 1. Select Start > Programs > Mentor Graphics SDD > Design Capture Design ViewExpedition Flow > Design Entry > Design Capture to display the Design Capture software. 2. Click the Project > New command to display the New Project Wizard.
4-3
3. Key in gate_test in the Project Name text entry field. This is the name of the project file used in this exercise. Note The software automatically appends the project name you enter to the end of the default directory name in the Project Location field. You will add a design later in this exercise. 4. Browse to and select the following directory in the Project Location field. ..\company_library 5. Click Next to advance to the next page of the New Project Wizard. 6. Click Next to advance to the last page of the wizard. This page displays a summary of your selections. At this point, the project file selections are complete. The New Project Wizard displays the directory structure created for the project. 7. Click Finish to save all settings; the software automatically creates the project. The new project file name displays in the design entry software banner. Tip: New projects can also be created from existing, "seed" project using the Project > Copy command. This enables you to customize the project "seed" and start all new projects from your customized project file.
Creating a New DC/DV Schematic

Use the following steps to create a schematic workspace in Design Capture and associate it with the Company_Library.lmc central library file: Note You can use DesignView software to perform these steps. However, the command paths documented in this chapter assume you are using Design Capture software. 1. Click File > New to display the New dialog box (Figure 4-2). Figure 4-2. Selecting a Schematic Design With the New Dialog Box
4-4
2. Highlight Schematic and click OK. The software creates a workspace where you can create a schematic design.
Linking a Central Library With a Project File

Use commands in Design Capture to link the project (.prj) file with the active central library (.lmc) file as outlined in the following steps: Note This procedure assumes that the correct project file displays in the design entry software banner. 1. Click Project > Settings; the Central Library dialog box displays in the Project Settings interface. 2. Browse for and select the Company_Library.lmc file in the Central Library field. Click Open in the Open dialog box (Figure 4-3). Figure 4-3. Project Setting Dialog Box (Design Capture)
The Capacitor and Resistor entries do not appear if you skipped the exercises in Using PM Administrator on page 3-1. 3. Click OK in the Central Library dialog box to attach the Company_Library.lmc file to the project file.
4-5
Implementing a Design Placing DC/DV Symbols and Devices
Placing DC/DV Symbols and Devices

Now that you linked the project file and the Company_Library.lmc file, place the symbols you created into a Design Capture (DC) workspace using the following steps:
Assigning a Layout Template

1. Select Place > Device or click the Device icon Templates dialog box displays. from the toolbar. The Layout
2. Select the default Layout Template (4 Layer Template) for use during PCB layout of this design. 3. Click OK on the Layout Templates dialog box; the Place Device dialog box displays. Note If a PCB job has not yet been associated with the project, the Layout Template dialog box displays when you select the Place > Device command. When you select a Layout Template and click OK, the software copies various PCB configuration files to the project's Common Database directory (.cdb), and the selected Layout Template will be specified in the project file. 4. Click the Partition dropdown box and highlight Logic Gates. The part you created earlier displays in the Parts Found list box. 5. Highlight the part in the list (see Figure 4-4).
4-6
Figure 4-4. Parts Database Dialog Box (Place Device Command)
The Select Symbol field displays the symbols defined for the part. Use the Slot field to select individual slots for placement. For example, select the g244a (*.slb extension) symbol from the Select Symbol field and select the Slot dropdown box. This provides the option to individually place the eight slots of the device in the schematic. The symbol graphics display in the view window below the Slot field. The Preview Available Cells field lists the cells for placement within Expedition PCB. These are the top and alternate cells you defined with the Pin Mapping dialog box in the Part Editor. The cell graphics display in the view window below the Preview Available Cells field. Use the Include PDB Data option to add Part data to the symbol when placed in the schematic. The software only places the symbol data when you de-select this option.
4-7
The Include PPS Data option is only available if Parts Manager (PM) software resides on your machine. For more information, consult PM online help or the Parts Manager Process Guide. Note Before proceeding, ensure that 74F244_Full is highlighted in the Select Symbol field.
Placing Devices in a Design

Use commands in Design Capture to place the symbols you created earlier in this process guide in the schematic design: 1. Click Place; the Place Device dialog box dismisses and the 74F244_Full device attaches to the cursor. 2. Position the device in the workspace and single click the left mouse button to enter it into the design. 3. Click the right mouse button to display the popup menu. Highlight and click Cancel on the popup menu; the Place Device dialog box displays. 4. Select 74F244_Half from the Select Symbol field and place it to the right of the 74F244_Full device. 5. Click the right mouse button to display the popup menu. Highlight and click Cancel on the popup menu; the Place Device dialog box displays. 6. Select g244a from the Select Symbol field and place four symbols above the 74F244_Half device. Place the first symbol directly above the 74F244_Half symbol and stack the remaining three symbols above the first from bottom to top. 7. Click the right mouse button to display the popup menu. Highlight and click Cancel on the popup menu; the Place Device dialog box displays. 8. Click Close in the Place Device dialog box.
Refreshing the Display

Use the following steps to refresh and reorient the display of the symbols in the schematic design: 1. Click View > Refresh to update the display in Design Capture. The design should resemble Figure 4-5:
4-8
Figure 4-5. Schematic Design in Design Capture
2. Select View > Zoom Area (or click the Zoom commands from the toolbar) and place a zoom window around the symbols. Tip: You can also hold the SHIFT key, press the middle mouse button, and place a zoom window around the symbols. When the window updates, note that the software adds part name, part number, and cost place holders from information you specified in the part data. Note If the text does not display, select the Properties command, click the Display tab, and select the Invisible Text option.
Connecting Devices
Use the following steps to connect the devices you just placed in the schematic design: 1. Select the Place > Wire command (or click the Place Wire (connect) the devices as shown in Figure 4-6: icon) and wire
4-9
Implementing a Design Compiling and Packaging the DC/DV Schematic
Figure 4-6. Schematic Design With Wires
2. Click the right mouse button and select Cancel from the popup menu when completed. 3. Click File > Save to save the schematic design. 4. Key in gate_test.sbk in the File Name text box. 5. Click Save. A confirmation dialog box prompts you to add the schematic file to the current project. Click Yes to save the design in the current project file. 6. Click File > Close to dismiss the schematic design.
Compiling and Packaging the DC/DV Schematic

In this exercise, run the central database (CDB) compiler on the schematic you just created. The CDB Compiler Utility is a bidirectional interface that enables the interchange of structural netlist data between the software tools. Netlists are read into and saved in a neutral format in the Common Database (CDB). This format can then be transformed into the target format such as Verilog, EDIF, PCB, and so forth. The Common Database Compiler (CDBC) reads the schematics from the project file and writes the CDB into the location defined by the CDB entry in the project file.
4-10
The Tools > Compile CDB command in Design Capture (DC) invokes the CDB compiler in default mode (that is, it flattens and runs in incremental compile mode) on the active design. The software prompts you to save all changes you made to the design. As the CDBC executes, it writes various informational messages to the screen and displays any error messages and/or warning messages associated with incorrectly constructed schematics. Note Normally, you should verify your design (using the Tools > Verify command) and correct all errors before compiling the design. However, for this exercise, do not run Verify on the schematic.
Compiling and Packaging the DC/DV Schematic

Use the following steps to compile and package the schematic design in DC/DV: 1. Click Tools > Compile CDB to activate the CDB Compiler. The following message appears in the Command output window below the DC workspace. Compiler finished, no errors found. 2. Click Tools > Package Design to invoke Packager software on the schematic design. Upon completion, the following message appears in the Command output window: Packager finished successfully. !THE CDB IS UP-TO-DATE! Note You must scroll up in the Command output window to view this message.
Reviewing Packaging
Use the following steps to review work performed by the Packager software: 1. Double-click gate_test.sbk to open the schematic (Figure 4-7). Figure 4-7. Selecting a Schematic File in Design Capture
2. Select View > Zoom or click the Zoom command from the toolbar and place a zoom window around the symbols. The software adds the Reference Designator, properties, and pin numbers to the symbols from the part database.
4-11
Note You placed minimal information in your symbols when building them with Symbol Editor software. The Place > Device command places the selected symbol and also adds text properties from the part data to the symbol during placement. Properties, such as the Part Number, Part Name, and Part Label, are automatically added to the symbol. Other properties are added to the symbol if enabled in the Property Definition Editor dialog box. It is recommended that symbols contain minimal part-specific information. When compiled, the software combines all data and displays the following schematic (Figure 4-8). The schematic is now considered complete for this exercise. Tip: If the text does not display, select the Edit > Properties command, click the Display tab, and select the Invisible Text option to display the text. Figure 4-8. Completed Schematic Design
3. Click File > Exit to exit the design entry software.
4-12
Implementing a Design Creating a Design in DxDesigner
Creating a Design in DxDesigner

Use DxDesigner to create and define a new project, create a design, and place symbols in a schematic. Note You must successfully complete the exercises in Using Library Manager on page 2-1 before you begin the exercises in this chapter. Perform the procedures in this chapter in the following order: Creating a DxDesigner Project/Linking to Central Library on page 4-14 Attaching a Symbol Library to a DxD Project Search Path on page 4-17 Adding Symbols to a DxD Schematic on page 4-20 Compiling and Packaging the DxD Schematic on page 4-23 Using Expedition PCB on page 4-24 Note See Managing Reusable Blocks (DC/DV-Expedition Flow) on page 4-35 for information on the Reusable Blocks Editor.
4-13
Implementing a Design Creating a DxDesigner Project/Linking to Central Library
Use the flowchart in Figure 4-9 to guide you through the procedures in this section: Figure 4-9. Software Tools Process Flow (DxDesigner-Expedition Library Manager)
Creating a DxDesigner Project/Linking to Central Library

Before you create a schematic, create a project in which to store the schematic design files, symbols, and WIR files that result when you generate a netlist for a schematic. Then, link that project to the central library. You must also define a library search path that will indicate the order in which you want to search your part libraries for schematic symbols and other design elements that you will be using to create the schematic designs.
Creating a New DxD Project and Linking to a Central Library

Use the following steps to create a new DxD project file and establish a link to the Company_Library central library: 1. On Windows, click Start > Programs > Mentor Graphics SDD > DxDesignerExpedition Flow > Design Entry > DxDesigner to invoke DxDesigner.
4-14
On Linux and UNIX, open a terminal window and type viewdraw. See Configuring Linux and UNIX Workstations on page 1-5 for more information. 2. Click File > New and select the Project tab. 3. Select the category (General) and type of project (Default) you want to create. Note Currently, all projects are of a General category. A project type is like a template. It contains information relating to the type of project you want to create, such as what libraries to load in the library search order. The Default project type adds the built-in library to the project. This type is appropriate for most design types. 4. Browse to the \Company_Library directory in the Location field. 5. Key in gate_test in the (project) Name field. This instructs the software to create the DxD project file in the \Company_Library\gate_test directory (Figure 4-10). Figure 4-10. Specifying a DxDesigner Project Name
6. Click More to display the design configuration information. 7. Set the design configuration as shown in Figure 4-11. Figure 4-11. Specifying Central Library Path
4-15
8. When you click the Expedition PCB check box, expand the view and enable the Zoom Style property (Figure 4-12). Figure 4-12. Enabling Expedition Style Zoom
9. Select the appropriate layout template within the central library structure. For example: <drive>:\Company_Library\LayoutTemplates\4 Layer Template\template.pcb 10. Select the following DxD project file within the central library as follows: <drive>:\Company_Library\gate_test\pcb_dx\pcb_dx.prj Tip: If no DxD project file existed, you can specify a path and the software creates the project file and stores the settings in it as specified in the Design Configuration dialog box. In this exercise, use the pcb_dx.prj file. 11. Ensure the design has the following settings (in Table 4-1): Table 4-1. Establishing Project File Settings Setting Keybindings Configuration File Allow Forward Annotation Allow Back Annotation Constrain in CES Use CDB Flow Automatic Update of Schematic Files Value Disable expedition.cfg Enable Enable Enable Enable Disable
4-16
Implementing a Design Attaching a Symbol Library to a DxD Project Search Path
Tip: You cannot disable the Constrain in CES option. Also, when you enable the Use CDB Flow option, you cannot return to a non-CDB flow. To use a netlist-based flow, DO NOT ENABLE the Use CDB Flow option. See procedures in Library Manager (DxD-Expedition Flow) Limitations on page E-1 for information on using the netlist-based flow. 12. Click OK; the software creates a gate_test.dproj project file in the \Company_Library\gate_test directory. The DxDesigner interface appears. Note The central library you create and work with in this process guide should not be used or associated with any central library you currently have or will create when using Library Manager. 13. Ensure that Expedition PCB appears in the Design Configuration pulldown menu. If not, select Expedition PCB (Figure 4-13). Figure 4-13. Design Configuration Pulldown Menu
Attaching a Symbol Library to a DxD Project Search Path

Use the following steps to attach a symbol library to your DxD project: 1. Having set the active Design Configuration to Expedition PCB (performed in the previous procedure), go to the Navigator Project tree, highlight Design Roots, rightclick the mouse button to display the popup menu, and select the Invoke Project Editor command (Figure 4-14).
4-17
Figure 4-14. Selecting Invoke Project Editor Command (DxDesigner)
The Project Editor dialog box displays with a default search order scheme (Figure 4-15). Figure 4-15. Project Editor Search Order Scheme
2. Change the search order scheme to Central Library default (Figure 4-16): Figure 4-16. Changing the Search Order Scheme
Logic_Gates appears in the Library Search Order list (Figure 4-17).
4-18
Figure 4-17. Project Editor With Symbol Library Search Order Defined
3. Click OK; the Project Editor dialog disappears and the software attaches the symbol library to your DxD project. This library path and search order information is written to the project's viewdraw.ini file. If you re-invoke the Project Editor, you would see the Search order scheme field again set to {Local to Project} again. This is correct behavior as the active scheme is always saved locally to the project. Subsequent changes made to the search order scheme (if you click Apply or OK) will overwrite the current search order information in the viewdraw.ini file. Also, local library paths (libraries that do not exist in the central library) will be preserved in the project. These will appear in the Project Editor search order listing with full paths displayed. This allows you to distinguish between the central library libraries and local libraries.
Creating a Schematic Workspace in DxDesigner

Now that you have created a project and linked it to a valid central library, create a schematic in DxDesigner using the following steps: 1. Click File > New > File tab. 2. Click Schematic to create a new empty schematic file. 3. Key in gate_test in the Name field. Note that the location of the schematic file is automatically updated in the Location field (Figure 4-18). Figure 4-18. Creating a Schematic in DxDesigner
4-19
Implementing a Design Adding Symbols to a DxD Schematic
4. Click OK; the schematic is created in your active project directory. You can work on the schematic contents in the workspace.
Adding Symbols to a DxD Schematic

Now that you have created a project file and associated it with the central library, place the symbols you created (via DxDesigner) using the following steps. 1. Click Add > Device from PDB ; the Place Device dialog box appears.
2. Select the Logic_Gates partition. The symbols you manipulated earlier in this process guide display in the Select Symbol list. 3. Select the 74f244_full.1 symbol (Figure 4-19). Be sure the pin numbers that were previously built in to the symbols appear in the pin list dropdown box (below Select Symbol list). Figure 4-19. Place Device Dialog Box
4-20
4. Click Place; the component attaches to the cursor. 5. Place the 74f244_full component at the bottom left of design space. Click to place the component in the design. 6. Select the 74f244_half.1 symbol from list and click Place. The component attaches to the cursor. 7. Position the 74f244_half component to the right of the 74f244_full component. Click to place the component in the design. 8. Select the g244a.1 symbol from list and click Place. The component attaches to the cursor. 9. Place four g244a.1 components above the 74f244_half component. The schematic should resemble the design in Figure 4-20. 10. Close the Add Component dialog box when completed. The DxD project workspace should appear as shown in Figure 4-20: Figure 4-20. Positioning Components in the DxD Schematic
11. Use Zoom by Rectangle to improve resolution for wiring purposes. Zoom in close enough for the grid to display.
4-21
Connecting Components
Use the following procedure to wire (connect) the components in your schematic. Note that the appearance of symbols in the schematic may vary if you are using DxD-Expedition Library Manager. 1. Click Add > Net and wire (connect) the components as shown in Figure 4-21. 2. Click Select to exit the Add Net command. The schematic should resemble the following figure: Figure 4-21. DxD Schematic Design With Nets Included
3. Click File > Save to save your work.
4-22
Implementing a Design Compiling and Packaging the DxD Schematic
Compiling and Packaging the DxD Schematic

In this exercise, run the central database (CDB) compiler on the schematic you just saved. Note If you do not select the Use CDB Flow options in the Design Configurations dialog box, you can use the Tools > Create PCB Netlist (common) command to invoke the ViewPCB dialog box, which allows you to run forward annotation on a DxD design. The CDB Compiler is a bidirectional interface that enables the interchange of structural netlist data between the software tools. Netlists are read into and saved in a neutral format in the Common Database (DCB). This format can then be transformed into the target format, such as Expedition PCB. Perform the following steps to prepare the schematic design for export to a PCB layout system and package the schematic: 1. Click Tools > Compile CDB. The software runs the CDB Compiler on the design and the following message appears at the bottom of the DxDesigner window: CDB was generated successfully. 2. Click Tools > Package CDB; the CDB Packager dialog box appears. Ensure the correct project file appears at the top of the dialog box (Basic tab). Use the default settings in the Basic tab. 3. Click Run in the CDB Packager dialog box to run CDB Packager and generate a netlist. The Results tab displays the outcome of the netlist generation. While the software displays various notes and warnings, the following message should display in the Results tab: Packager finished successfully. !THE CDB IS UP-TO-DATE! Tip: You must scroll up the Results tab to view this message. 4. Click Tools > Launch Expedition to execute Expedition PCB. The project you are working on appears in the Expedition PCB viewer. Go to Step 4 in Opening a New PCB Job on page 4-25 to use Expedition PCB software to forward annotate the design.
4-23
Implementing a Design Using Expedition PCB
Using Expedition PCB

This section provides information on using Expedition PCB to build a PCB design with the entities created earlier in this process guide. Use Expedition PCB software to automate the design of printed circuit boards. PCB design functions, such as placement layout, placement optimization, routing, analysis, and output generation, are performed using Expedition PCB. Expedition PCB contains the Auto Router which is a shape-based router and interconnect editor, providing both interactive and batch routing capabilities. It can push aside routed traces and vias and work in a gridded or gridless environment. The routing process is controlled by the design rules and routing algorithms that you define. Use Expedition PCB software to open a new PCB job, perform gate swapping, push into a cell, and replace a cell in the PCB job. Note If you are using the DxD-Expedition Library Manager flow, go to Step 4 in Opening a New PCB Job on page 4-25 to forward annotate. This section contains the following topics: Invoking Expedition PCB Opening a New PCB Job on page 4-25 Swapping Gates on page 4-27 Pushing from Top Cell to Bottom Cell on page 4-32 Replacing a Cell on page 4-33 Managing Reusable Blocks (DC/DV-Expedition Flow) on page 4-35 Summary on page 4-34
Invoking Expedition PCB

Use the following steps to invoke Expedition PCB software and create a new PCB design file: 1. Select Start > Programs > Mentor Graphics SDD > <Design Capture DesignViewExpedition Flow> or <DxDesigner-Expedition Flow> > Layout > Expedition PCB to invoke Expedition PCB software (if not already invoked). The Expedition PCB window displays. 2. Click File > New; the Job Management Wizard displays.
4-24
3. Click the Browse icon on the Job Management Wizard and browse for the following source project filename: ..\company_library\gate_test\gate_test.prj 4. Click Open on the Select Project File dialog box. 5. Click Next; the software creates a new PCB source project filename (gate_test.pcb). 6. Select 4 Layer Template in the Job Management Wizard and click Next to advance to the next dialog box. 7. Click Finish to accept the default settings. 8. Click Close to dismiss the Job Management Wizard dialog box.
Opening a New PCB Job

Use the following steps to open a new PCB job in the PCB source project: 1. Click File > Open in Expedition PCB and browse to the following path: ..\company_library\gate_test\pcb_dx 2. Select gate_test.pcb and click the Open button. The software opens the PCB job. Note The layout template copied by the software is the template you designated in the Job Management Wizard. Information on creating and manipulating layout templates is included later in this process guide. 3. Click Setup > Project Integration; the Project Integration dialog box displays. 4. Select Forward Annotate. The software performs a database load and netload and brings the schematic data into the design. 5. Click OK in the Information dialog box when it displays. 6. Click Close on the Project Integration dialog box. 7. Click the Place Mode icon and select the Place Parts and Cells command (or click the Place Parts and Cells icon). The Place Parts and Cells dialog box displays. 8. Select the Unplaced option (from the list of Include options). 9. Click the Include All icon. 10. Click Apply. The Place Parts and Cells dialog box dismisses and the part U1 attaches to the cursor.
4-25
11. Position part U1 at the bottom (inside the board outline) and click the left mouse button to place it in the design. 12. Move the cursor up; part U2 attaches to the cursor. 13. Position part U2 at the top (inside the board outline) and click the left mouse button to place it in the design. Tip: U1 and U2 are the cells created earlier in this chapter. 14. Click Close to dismiss the Place Parts and Cells dialog box. 15. Click in the screen area to deselect the cell graphics (see Figure 4-22). Figure 4-22. PCB Design With Cells U1 and U2 Displayed
4-26
Swapping Gates
Use the following steps to swap gates between the U1 and U2 parts that are displayed in Expedition PCB: 1. Zoom in between parts U1 and U2 until the pin numbers are visible. 2. Select Route > Swap > Gates (or click the Swap Gates icon bottom of the window) displays the following message: "Select pin of first gate to swap." 3. Click Pin 2:L on U2. Pins 4:L, 6:L, and 8:L also highlight (Figure 4-23). The status bar displays the following message: "Select pin from second gate to swap." ). The status bar (at the
4-27
Figure 4-23. Cells With Selected Pins Highlighted
4. Click on Pin 8:L and the Expedition PCB status bar displays the following message: "Confirm swap."
4-28
Figure 4-24. Cells With Pins Selected for Gate Swapping
5. Click anywhere in the workspace to confirm your selection. Notice that net lines are no longer crossed. 6. Swap gates 4:L and 6:L using the process outlined in Steps 1-5. 7. Click the Fit Board icon. The board displays properly within the template. The board should appear as illustrated in Figure 4-25:
4-29
Figure 4-25. Board With All Gates Swapped
8. Click File > Save to save the design. 9. Select Setup > Project Integration to invoke the Project Integration dialog box. Click Back Annotation in Expedition PCB which annotates the swap information back to the schematic. The software swaps the pin numbers between the symbols according to the swapping performed in Expedition PCB. The Back Annotation indicator should change from red to green. 10. Close the Project Integration dialog box.
4-30
11. (DxD-Expedition Library Manager Flow only) To complete the Back Annotation process, return to ViewPCB dialog box. Change the process to run Back Annotate Information From Layout to Schematic (Figure 4-26). Use back annotation to bring layout information from your PCB place and route tool back to the schematic. This includes change information regarding pin swaps, gate swaps, and so forth. Be sure to deselect the Run command line before processing option. Figure 4-26. ViewPCB Dialog Box (DxDesigner) Running Back Annotation
12. Click Run. The Results tab displays without errors, notes, and warnings (Figure 4-27).
4-31
Figure 4-27. ViewPCB Dialog Box (Results tab) with Back Annotation Results
Pushing from Top Cell to Bottom Cell

Use the following steps to push from one cell to another in Expedition PCB: 1. Click the Place action key (below the PCB workspace) or press the F12 function key on the keyboard. 2. Select part U1; the part highlights. 3. Press the F5 function key on the keyboard or click the Push action key. The software pushes the cell to the opposite side of the board. The part number and reference designator text are now mirrored. Note When pushing a cell, the cell updates with the opposite side padstack that you specified earlier in the Padstack Editor. 4. Click in the workspace to deselect the component.
4-32
Replacing a Cell
Use the following steps to replace a cell in the design: 1. Click ECO > Replace Cell in Expedition PCB; the Replace Cell dialog box displays. 2. Select 100-100000-001 from the Parts with Multiple Cells list. The Reference Designator and Replacement Cell lists update. 3. Click (20 pin SOIC) in the Replacement Cell list for part U2; a dropdown arrow displays. For the DxD-Expedition Library Manager flow, click (20_PIN_SOIC). 4. Select the arrow, select 20 pin dip (or 20_PIN_DIP if you are using DxD-Expedition Library Manager) from the list, and click OK. The software automatically places the alternate cell on the original cells origin as shown in Figure 4-28. Tip: You defined the alternate cell earlier in this process guide using the Part Editor. You can also place the alternate cell in the design using the Place Cells dialog box.
4-33
Implementing a Design Summary
Figure 4-28. Board Design With Replaced Cell Defined
Summary
You have completed the exercises in this process guide using the central library you created. Be sure to read Using Other Tools and Library Manager Utilities on page 5-1 for more information on tools and utilities available from the Library Manager interface. See Managing Reusable Blocks (DC/DV-Expedition Flow) on page 4-35 to learn more about Reusable Blocks functionality in Library Manager for the DC/DV-Expedition flow.
4-34
Implementing a Design Managing Reusable Blocks (DC/DV-Expedition Flow)
Managing Reusable Blocks (DC/DV-Expedition Flow)

Use the Reusable Blocks function in Library Manager to create circuit blocks and store them in the central library for future use. You design the circuit block using design entry tools (such as Design Capture and DesignView in the DC/DV-Expedition flow) and layout tools (such as Expedition PCB), verify the circuit block, and store it in the central library. This allows you to utilize verified quality circuitry with the ease of placing a single element in a design. A reusable block can contain parts, interconnect, vias, shape fills, plane information, design rules, obstructs, contours, slots, mounting holes, user-defined graphics and rules by area. It cannot contain a board outline or route border. You can create a Logical/Physical reusable block design that contains the schematic, PCB layout, and related design information (see Creating a Logical/Physical Reusable Block on page 4-36). This reusable block type appears under the Reusable Blocks node in the workspace tree (Figure 4-29). Figure 4-29. Reusable Blocks Node in Workspace Tree
Invoking Reusable Block Software

Use any of the following methods to invoke the Reusable Blocks Editor: Click Tools > Reusable Blocks Editor to invoke the Reusable Blocks Editor dialog box or click the icon in the toolbar. You can also invoke the Reusable Blocks Editor using commands from the popup menu accessible from the Reusable Blocks node in the workspace tree (Figure 4-30).
4-35
Figure 4-30. Accessing Reusable Blocks (Logical/Physical) Commands from the Workspace Tree
The Reuse Blocks dialog box appears (Figure 4-31) and allows you to create reusable blocks based on the type you selected from the popup menu.
Creating a Logical/Physical Reusable Block

A Logical/Physical reusable block design contains the schematic, PCB layout, and related design information and is supported in the DC/DV-Expedition flow. In this procedure, use the Reusable Blocks software in Library Manager to create a reusable block from the gate_test project. 1. Select Tools > Reusable Blocks Editor or click the Reusable Blocks icon on the Library Manager interface or click the Reusable Blocks Dialog popup menu command from the Logical/Physical Reusable Blocks node in the workspace tree; the Reusable Blocks dialog box displays (Figure 4-31). Tip: To access the New Reusable Blocks dialog box without invoking the Reusable Blocks dialog box, select the New Logical/Physical Reuse Block popup menu command from the Logical/Physical Reusable Blocks node in the workspace tree. The New Reusable Blocks dialog box appears (Figure 4-32). Using this method allows you to skip Step 2 in this procedure.
4-36
Figure 4-31. Reusable Blocks Dialog Box
2. Click the New Reusable Block icon and the New Reusable Block dialog box displays (Figure 4-32). Or, if you click the New Logical/Physical Reuse Block popup menu command (Figure 4-30), the New Reusable Block dialog box appears. Figure 4-32. New Reusable Block Dialog Box (Logical/Physical)
3. Click the Browse icon and select the following source project file: <drive>:\Company_Library\gate_test The following appears by default in the Reusable Block Name field. If not, key in gate_test. 4. Click OK to dismiss the New Reusable Blocks dialog box. The Reusable Blocks dialog box now displays the gate_test circuit with a status of Unverified (Figure 4-33) and lists all properties associated with the new reusable block. See Table 4-2 on page 4-40 for a description of the properties associated with an reusable block.
4-37
Figure 4-33. Reusable Blocks Dialog Box with Block Name Displayed
The project workspace tree also adds the reusable block to the Logical/Physical Reusable Blocks node (Figure 4-34). Figure 4-34. Logical/Physical Reuse Block in the Workspace Tree
The software creates a new subdirectory (ReusableBlocks) in the active DC/DVExpedition flow central library file structure (see Subdirectories and Files Created by Library Manager on page 2-6). Within the ReusableBlocks subdirectory within the central library structure, the software creates a subdirectory using the name of the reusable blocks you create (for example, gate_test). Note that the software creates two subdirectories below the directory named for the reusable block: Work - contains the project file, schematic objects, and supporting entities needed for the reusable block to have logical and physical attributes. When entities reside in the Work subdirectory, the Status field in the Reusable Blocks dialog box shows Unverified for the specific reusable block. Cert - When the reusable block is successfully verified, the software moves the project file, schematic objects, and supporting entities from the Work subdirectory to this subdirectory. When entities reside in the Cert subdirectory, the Status field in the Reusable Blocks dialog box shows Verified for the specific reusable block. See Table 4-2 on page 4-40 for more information on reusable block properties.
4-38
Viewing Reusable Block Properties

Note The following sections illustrate how to use Reusable Block object commands in the workspace tree. Do not manipulate reusable block objects in the sample central library you created for use in this process guide. Use the Reuse Properties popup menu command in the workspace tree to view the object properties of any reusable block in the central library. When invoked, the Reusable Block Properties dialog box appears and displays properties of the selected object, such as name, status, modification time/date stamps, and description. Tip: This provides an easy method to view reusable block object properties without invoking the Reusable Blocks Editor (Figure 4-33 on page 4-38). To view reusable block properties: 1. Highlight the reusable block in the workspace tree. 2. Invoke the Reuse Properties popup menu command in the workspace tree; the Reusable Block Properties dialog box appears (Figure 4-35).
4-39
Figure 4-35. Reusable Block Properties Dialog Box (Invoked from Workspace Tree)
Table 4-2 describes the fields and options on the Reusable Block Properties dialog box. Table 4-2. Reusable Block Properties Dialog Box Fields and Options Dialog Box Field Block Name Block Layers Description By default, the reusable block name matches the project file (*.prj) name associated with the central library. Identifies the number of layers within the reusable block design.
4-40
Table 4-2. Reusable Block Properties Dialog Box Fields and Options Dialog Box Field Status (non-editable field) Description Verified - Indicates that the reusable block has been verified and can be placed in schematic designs or extracted into Expedition PCB designs. The project file, PCB job, and files supporting the reusable block object are stored in the Cert subdirectory in the central library (ReusableBlocks). Unverified - Indicates that a change has occurred that requires re-verification of the reusable block and a re-save of the reusable block cell. A reusable block that is unverified is not allowed to be placed within schematics or extracted into Expedition PCB designs until it is reverified. If there are newer cells or padstacks referenced by the reusable block, Forward Annotation does not bring them into the local design until the reusable block is reverified. This ensures that the local reusable block cell remains in synchronization with the central library. The project file, PCB job, and files supporting the reusable block object are stored in the Work subdirectory in the central library (ReusableBlocks). Displays when the reusable block was last updated. The time and date stamp and the username of the individual who processed the reusable block appears in this field. Displays the modification status of the physical cell (footprint) characteristics within the reusable block. Unmodified - Displays when the physical attributes of the reusable block has not been modified since the last successful verification. Modified - Displays when the physical attributes of the reusable block has been modified and successfully verified. This also indicates that other designs that include the same block may be impacted by the change.
Design Modified (non-editable field) Cell Modified (non-editable field)
Reusable Block Description Key in a verbose description of the reusable block. This (Optional) text is saved to the ReuseInfo.txt file located in the subdirectory associated with the reusable block (same level as the Work and Cert subdirectories). 3. Key in a reusable block description (if one is not specified already for the reusable block). 4. Click OK to save changes and dismiss the dialog box.
4-41
Note Once a reusable block has had its reusable block cell saved, any changes to padstacks, parts or cells within the central library, referenced by the reusable block, causes the reusable block to be marked as Unverified (see Table 4-2).
Editing a Reusable Block

Library Manager features two ways to select a reusable block of any type within a central library for editing; from the Reusable Blocks dialog box (Figure 4-33) or the Edit popup menu command in the Reusable Blocks node in the tree (Figure 4-36). Figure 4-36. Edit Reusable Block Command in the Workspace Tree
The software invokes Expedition PCB and provides the tools necessary to edit the reusable block objects. Upon completion, save your work in Expedition PCB and exit. When edits are made to a Verified reusable block object, the status changes to Unverified until the object is recompiled, packaged, and successfully completes all verification checks. Once all verification checks are completed, the reusable block status changes to Verified (see Table 4-2).
Copying a Reusable Block

There are two methods to copy a reusable block: Use the Copy popup menu command to copy an existing reusable block and create a new one. Highlight the reusable block in the workspace tree and use the Copy popup menu command (Figure 4-37).
4-42
Figure 4-37. Copying a Reusable Block in the Workspace Tree
Use the Copy icon in the Reusable Blocks dialog box. Highlight the Reusable Block you want to copy in the dialog box, click Copy , key in a unique name for the new reusable block, and press Enter (Figure 4-38). Figure 4-38. Copying a Reusable Block
The software creates a new reusable block with the same name but with _1 appended to the source reusable block. For example, if you copy the gate_test reusable block (Figure 4-38), the software creates a new reusable block named gate_test_1 (Figure 4-39). Figure 4-39. Results of Copying a Reusable Block in the Workspace Tree
4-43
Renaming a Reusable Block

Use the Rename popup menu command to edit any reusable block name. Any renamed reusable block name cannot be the same as another name within the reusable block type or the software generates errors. To change a reusable block name: 1. Highlight the reusable block in the workspace tree. 2. Invoke the Rename popup menu command. The Rename Reusable Block dialog box appears (Figure 4-40). 3. Key in the new name for the reusable block in the dialog box (Figure 4-40). Figure 4-40. Renaming a Reusable Block in the Workspace Tree
4. Click OK. The new reusable block name appears in the workspace tree (Figure 4-41). In this example, the sampletest_1 reusable block was renamed to SRAM15 and the revised name appears in the workspace tree. An error message appears if enter a reusable block name that is already defined (to avoid duplicate names).
4-44
Figure 4-41. Renamed Reusable Block in the Workspace Tree
Tip: The Reusable Blocks dialog box (Figure 4-33) also provides a user interface to perform this operation. Simply highlight the reusable block name in the Block Name field, type the new name, and click again in the field to save the changes.
Deleting a Reusable Block

Use the Delete popup menu command in the workspace tree to remove any reusable block from a reusable block type partition in a central library. 1. Highlight the reusable block in the workspace tree that you want to delete and select the Delete popup menu command (Figure 4-42). Figure 4-42. Deleting a Reusable Block in the Workspace Tree
The software displays a warning message and asks you to confirm the deletion. Caution Deleting a reusable block from a central library can have detrimental affects on designs that use that reusable block and cause the CDB Compiler, Packager, and Verification to fail. 2. Click OK in the message dialog box; the software removes the file from the central library the workspace tree refreshes (Figure 4-43). Click Cancel to exit the Delete command.
4-45
Figure 4-43. Reusable Block Removed from the Workspace Tree
Tip: The Reusable Blocks dialog box (Figure 4-33) also provides the Delete icon to perform this operation. Simply highlight the reusable block in the dialog box and click Delete. The software displays a warning message and asks you to confirm the deletion. Click OK.
4-46
Chapter 5 Using Other Tools and Library Manager Utilities

Introduction
Library Manager provides additional tools to manipulate central library data. This chapter discusses the following Library Manager utilities and administrative procedures that are part of central library file management: Using Layout Templates Using IBIS Software on page 5-3 Using Symbol Editor for DC/DV Symbols on page 5-6 Using Symbol Editor for DxD Symbols on page 5-7 Using Padstack Editor on page 5-7 Using Library PDF Documenter on page 5-8 Creating a User-defined Script or Dialog Box on page 5-9 Opening an Existing User-defined Script or Dialog Box on page 5-11 Using DxDatabook Data Editor (DxD-Expedition Flow) on page 5-11 Using the Material / Process Editor on page 5-12 Performing Backups on page 5-14 Using File Viewer on page 2-103.
See Appendix C: Upgrading Central Libraries for Linux and UNIX Use on page C-1 includes information on the lmcwin2unix script, which adjusts central libraries that were created on the Windows operating system prior to SDD2004 SPac1 for use on the Linux operating system.
Using Layout Templates

Use the Layout Templates dialog box to create and manage PCB layout or panel templates that can be used to start new PCB or panel designs. The dialog box displays all the available layout and panel templates in the central library.
5-1
Using Other Tools and Library Manager Utilities Using Layout Templates
Note The Layout Templates icon is disabled when Library Manager is invoked from within Design Capture. Select Tools > Layout Template Editor or click the Layout Templates icon Manager interface and the Layout Templates dialog box displays (Figure 5-1). Figure 5-1. Layout Templates Dialog Box in the Library
The software provides two design templates (4 Layer Template and 8 Layer Template) that contain predefined configuration settings such as layer stackup, default clearances, Gerber plot file definitions, and so forth. You can create new templates and copy, edit, and delete templates associated with the active central library. For additional information on managing layout templates, consult online help. Note Consult online help for more information on creating and using Panel layout templates in a Fablink XE job. The following exercises illustrate how to create a new user-defined design template from an existing design file and how to copy an existing design layout template that appears in the Layout Templates dialog box.
Creating a New Design Template from an Existing Design File

Creating a new design template from an existing design allows you to use the original board outline and job settings, such as layer stackup, trace spacings, net class information, Gerber plot setup file, and so forth, as a starting point for the new template.
5-2
Using Other Tools and Library Manager Utilities Using IBIS Software
Tip: For Design type, create a template from a design prior to running Forward Annotation in Expedition PCB. Otherwise, the net names and part data associated with the template will conflict with subsequent designs. 1. Click the New Template icon ; the software prompts you to browse for a source design file and define a new template name. 2. Click OK to copy the entire PCB layout directory structure into the following central library: ..\central_library\layout templates 3. Select the layout template and click the Edit Template icon to edit the file. Note The software prompts you for a project file which is not required. Click No or Cancel and proceed to Expedition PCB.
Copying an Existing Design Layout Template

You can copy an existing design layout template and use the existing board outline and job settings, such as layer stackup, trace spacings, net class information, Gerber plot setup file, and so forth, as a starting point for the copied template. 1. Select an existing Design layout template from the list and click the Copy Template icon. The software copies the template directory structure and appends _1 to the new name. 2. Rename the template _1 that you copied to a new template name.
Using IBIS Software

Note IBIS Librarian supports the Design Capture/DesignView-Expedition flow on Windows only. IBIS is an industry standard format used to describe the behavior of inputs and outputs of active devices. For DC/DV-Expedition flows that do not use Constraint Editor System (CES) software, Library Manager uses IBIS Librarian software which organizes and verifies device models for use in transmission line simulation by Signal Vision and Signal Analyzer software (available on Windows only). IBIS Librarian facilitates organization of models by device vendor, technology, function, and so forth. The models are then verified for compliance with the IBIS format prior to
5-3
simulation. IBIS Librarian software supports Version 2.1 of the IBIS Model specification. See Invoking IBIS Librarian on page 5-4 for more information. Note IBIS Librarian software operates on the Windows operating system. It is not available in Library Manager using Linux or UNIX and is only available when Signal Analyzer and Signal Vision are used in flows that do not use CES software. For all flows that use CES software, Library Manager uses Visual IBIS Editor software. Visual IBIS Editor software facilitates organization of models by device vendor, technology, function, and so forth. The models are then verified for compliance with the IBIS format prior to simulation. Visual IBIS Editor software supports Version 3.2 of the IBIS Model specification. See Invoking Visual IBIS Editor on page 5-4 for more information. Note Visual IBIS Editor software operates on Windows, UNIX, and Linux operating systems but only with Dx symbols. Since IBIS modeling software supports multiple product flows, there are some limitations and usage guidelines to consider when using the IBIS Models software. These limitations and rules apply when you use the Part Editor software (see Using IBIS Functionality in Part Editor on page 5-5) and Library Services (IBIS Models tab) in Library Manager (see Using IBIS Functionality in Library Services on page 5-6 for specific flow-based solutions).
Invoking IBIS Librarian

Select Tools > IBIS Librarian or click the icon in the Library Manager interface to access IBIS Librarian software. The IBIS Librarian interface displays and provides the tools necessary to create and edit models. A graphical viewer displays I/V curves for pulldown/pull up states and power/ground clamps as well as V/T curves for rising and falling edges. For additional information on the IBIS Librarian software, click online help within the applicable IBIS software interface.
Invoking Visual IBIS Editor

Note Visual IBIS Editor (which supports both the DC/DV-Expedition and DxD-Expedition flow on all platforms) can store IBIS models anywhere on your machine (and are not controlled by Library Manager). Select Tools > Visual IBIS Editor or click the icon access the software. in the Library Manager interface to
5-4
For additional information on the Visual IBIS Editor software, click online help within the application interface. Note If Library Manager is invoked within Expedition PCB, the software automatically enables the appropriate IBIS software tool. If Library Manager is invoked in standalone mode, both IBIS model editors will be operational in the Library Manager interface.
Using IBIS Functionality in Part Editor

Note Part Editor IBIS integration applies to the DC/DV-Expedition flow only IBIS software (IBIS Librarian). Use the Part Editor software to assign IBIS models to parts. If the Online Property Verification option is enabled in the Part Editor software, select Browse to find and display a list of IBIS models in the Available IBIS Models dialog box.
Standalone Mode
Note The Browse functionality in the Component Properties section is enabled for the DC/DVExpedition flow IBIS Librarian and becomes active if the Online Property Verification option is toggled On in the Verification pulldown menu. When invoking Library Manager in standalone mode, the Browse feature does not work properly unless you use Signal Analyzer or Signal Vision in a non-CES mode.
Expedition PCB in Non-CES Mode

When invoking Library Manager from Expedition PCB in a non-CES mode, the Browse feature is enabled if you use Signal Analyzer or Signal Vision software. This allows you to browse for/find IBIS models in the active central library. A list of IBIS models appears in the Available IBIS Models dialog box.
Expedition PCB in CES Mode

When invoking Library Manager from Expedition PCB in CES mode, the Browse feature is enabled and may display an empty list of IBIS models. If the central library has been used previously in a non-CES flow with Signal Analyzer or Signal Vision, the dialog box displays a valid list of IBIS models. However, these models may not be adequate for use in ICX Pro Verify. If IBIS models are not adequate, reassign the proper IBIS models from the CES Parts tab.
5-5
Using Other Tools and Library Manager Utilities Using Symbol Editor for DC/DV Symbols
Using IBIS Functionality in Library Services

Note Library Services only supports DC/DV-Expedition flow IBIS Librarian models. Since the DC/DV-Expedition flow is only supported on Windows, the IBIS Models tab in Library Services is disabled on UNIX/Linux. Use Library Services to move IBIS models within a central library from one partition to another or import IBIS models from other Expedition PCB jobs or other ASCII IBIS files.
Standalone Mode
When using Library Manager in standalone mode, the IBIS Models tab in Library Services is available but is only functional if you plan to use Signal Analyzer or Signal Vision in a nonCES flow.
Expedition PCB in Non-CES Mode

When using Library Manager invoked from Expedition PCB in non-CES mode, the IBIS Models tab in Library Services allows you to copy and move IBIS models in Version 2.1 from/to partitions in a central library or copy and move IBIS models from one central library to another. Library Services cannot process IBIS models that are later than Version 2.1.
Expedition PCB in CES Mode

When using Library Manager invoked from Expedition PCB in CES mode, the IBIS Models tab in Library Services is disabled.
Using Symbol Editor for DC/DV Symbols

Note Symbol editing environments are different for the DC/DV-Expedition flow and DxDesigner-Expedition flow. See online help for each symbol editor for information on that specific software application. Symbol editing software in the DC/DV-Expedition and DxD-Expedition flow is a separate editing environment used to create and edit symbols. Use symbol editing software to open multiple libraries and edit multiple symbols during a single session. Each symbol window contains tabs along the bottom which represent the composite view of the symbol and the eight available rotations to build for a symbol (0, 90, 180, 270 and the mirrors for each). Place all graphics, pins, and text in Composite view and (if desired) modify the position and rotation of text properties in the eight rotation views. If you make modifications in the rotation views (for example, views other than the Composite view), the Composite view reflects the text position and rotation in the 0 view.
5-6
Using Other Tools and Library Manager Utilities Using Symbol Editor for DxD Symbols
Symbols are stored in library files (also referred to as partitions). The file name extension of a symbol library is .slb. The library files are binary compatible across all supported hardware platforms and operating systems. Symbols are identified within a library by symbol name and internal time stamp. Each library can contain multiple versions of each symbol; however, only the latest version is editable in the Symbol Editor. The software creates a new version each time the symbol is saved. To create a new symbol, open an existing library or create a new one. To edit an existing symbol, simply browse for and open the existing library containing the symbol and then doubleclick on the symbol name to open the symbol for editing. All details of symbol creation also apply to modification. Consult online help within the symbol editing software you are using for more information.
Using Symbol Editor for DxD Symbols

Use Dx Symbol Editor, available from the Library Manager interface, to create and edit symbols for use in the DxD-Expedition flow. This symbol editor software eliminates the need for you to invoke and configure DxDesigner to create and edit DxD symbols. Dx Symbol Editor provides the tools you need to create a Dx symbol and edit an existing symbol. Tabs at the top of the symbol workspace area allow you to have multiple symbols open for editing at the same time. All DxD symbols created by the symbol editor have a <symbol name.1> extension. These symbols are saved within the central library directory structure (SymbolLibs directory). See Creating a DxDesigner Symbol Using Symbol Editor (DxD-Expedition Flow) on page 2-36 for procedures on using DxD Symbol Editor.
Using Padstack Editor

The Padstack Editor provides tools to create and edit padstacks. Each padstack is one of the following types: Fiducial Mounting Hole Pin-SMD Pin-Through Shearing hole Tooling hole Via
5-7
Using Other Tools and Library Manager Utilities Using Library PDF Documenter
Assign one of the padstack types to the padstack. Once defined and named, assign different pads to padstack layers, specify pad filters, define pads to use within stacks, define holes, and define any custom pads or drill symbols. Click the Padstack Editor icon on the Library Manager interface or click Tools > Padstack Editor; the Padstack Editor dialog box displays. See Creating a Surface Mount Padstack on page 2-55 for more information. Tip: You can also invoke and use the Padstack Editor from the Padstacks node in the project workspace. Right-click on the Padstacks node and select New Padstack from the popup menu. The Padstack Editor dialog box appears.
Using Library PDF Documenter

Use the Library PDF Documenter dialog box to generate a customized PDF document containing a listing of selected layers (system, user) with cell items, part and symbol information and graphics that are present within the central library partitions. Select File > Output PDF to invoke the Library PDF Documenter within Library Manager (Figure 5-2). Figure 5-2. Library PDF Documenter Dialog Box
5-8
Using Other Tools and Library Manager Utilities Creating a User-defined Script or Dialog Box
UNIX On UNIX systems, set the EPD_ACROREAD_BIN variable to the directory where the Acrobat Reader executable resides. This ensures that the Acrobat Reader invokes on the PDF file created by Library PDF Documenter. Linux On Linux systems, set the ACRO_HOME variable to the directory where the Acrobat Reader executable resides. This ensures that the Acrobat Reader invokes on the PDF file created by Library PDF Documenter. After you have loaded an existing central library, you can set custom parameters and save these to either a new or overwrite an existing PDF file. Use the Cell tab to select the system and user-defined layers on which you require information. Use the Other Options tab to enter header and footer information (created by and created for) to personalize the PDF document. The software writes the PDF file to the Output directory of the active job (design). The default file name is the <central_library_name>.pdf. You can edit the output directory and PDF file name to fit your needs. The options selected on the Library PDF Documenter dialog box are saved in the file libpdf.cfg in the Config directory of the job where the central library (.lmc) file is located. See Subdirectories and Files Created by Library Manager on page 2-6 for more information. The options from the libpdf.cfg file are automatically displayed on the dialog if the dialog box has been run at least once. Otherwise, default values display. Consult online help associated with the Library PDF Documenter for more information.
Creating a User-defined Script or Dialog Box

Select File > New Script Form to create your own customer scripts and dialog boxes and add them to the Library Management user interface. This command invokes the Select Script Language dialog box which allow you to choose what programming language to use (Java or VisualBasic). A script is a series of automation instructions that you group together as a single command to accomplish a task automatically. Use scripting to automate time-consuming, repetitive operations. Scripts can also provide new functionality, such as design navigation aids and web browsing add-ins. You can run scripts automatically when you start running application software or opening them within an application. Scripts can be self-contained, custom commands or you can write script
5-9
Using Other Tools and Library Manager Utilities Creating a User-defined Script or Dialog Box
code to be executed through forms (dialog boxes). Scripts can contain many subroutines or functions. Scripts by themselves run and then exit immediately. Scripts do not wait for events so event handlers only apply in the context of forms (dialog boxes). If you want a particular subroutine to run in response to an event, you must include the appropriate script code as part of the form. When invoked, forms remain open (and running) until you switch to Edit mode or close the form. Note See Library Manager Automation Scripting on page G-1 for specific information on automation scripting. To create a new form: 1. Click File > New Script Form; the Select Script Language dialog box appears (Figure 5-3). Figure 5-3. Select Script Language Dialog Box
2. Select either VBScript or JScript from the Form Language pulldown and click OK. The Form Editor appears. 3. Design your form by dragging objects from the toolbox and defining their properties as needed. 4. Switch to the Script View (click View Script in the Standard toolbar) and write the script code (event handlers) for each object. 5. Click File > Save to save the form and associated script.
5-10
Using Other Tools and Library Manager Utilities Opening an Existing User-defined Script or Dialog Box
Opening an Existing User-defined Script or Dialog Box

Select File > Open Script Form to open and edit your own customer scripts and dialog boxes associated with the Library Management software. You can open an existing form to run it and to edit it from within an application. Note These scripts and dialog boxes are created using the New Script Form dialog box and can be written in Java or VisualBasic (see Creating a User-defined Script or Dialog Box on page 5-9. To open an existing form: 1. Select File > Open Script Form. 2. Select, type, or browse to the .efm file you want to open and click Open. The form executes. To stop the form, click the Stop icon on the Standard toolbar. To edit the form, drag and drop objects from the Object bar or click the View Script icon on the Standard toolbar to edit the code.
Using DxDatabook Data Editor (DxD-Expedition Flow)

DxDatabook provides component search, selection, and verification capabilities from databases located anywhere on the Internet or on your company's intranet. It accelerates the design entry stage of PCB designs by adding parametric data to a DxD-Expedition flow schematic using an interactive library management system. Use DxDatabook Data Editor in the following ways: Search for parametric data entries in a database and receive a list of objects that meet the criteria you specify. Add, edit, and/or remove attributes to an existing object.
For more information on using DxDatabook in the DxD-Expedition flow, see Using DxDatabook Data Editor in Library Manager on page D-1 and the DxDataBook Users Guide.
5-11
Using Other Tools and Library Manager Utilities Using the Material / Process Editor
Using the Material / Process Editor

To design with embedded passives, a number of material properties must be defined. An embedded passive is built into the product and is a device that does not add energy to the signal it passes (for example: resistors, capacitors, and inductors). In addition, processes must be defined to use the available materials in a design flow Use the Material / Process Editor user interface to create and modify the process properties associated with the materials used in the central library. When materials and processes are created using the Material / Process Editor, the data is stored in the MaterialDBLibs directory within the active central library (see Subdirectories and Files Created by Library Manager on page 2-6). Tip: To limit the number of materials and processes within the Cell or Layout Editor, use Library Services to create and modify the local libraries and import material and process information from external sources.
Managing Processes
To effectively use the available materials in a design flow (for example, capacitors, conductors, insulators, and resistors), a process is defined via the Material / Process Editor. Each process has three subcategories: Additive Resistors Subtractive Resistors Capacitors
Subcategories in the tree view cannot be altered and are the same for all processes (Figure 5-4). Figure 5-4. Material / Process Editor (Processes Node)
5-12
Using Other Tools and Library Manager Utilities Using the Material / Process Editor
Use Library Services to copy processes between central libraries and designs. When invoking Library Services within Library Manager, you can copy processes from one central library to another central library and/or imported/exported to/from the central library via ASCII. Note When invoked from Library Services from within Expedition PCB, processes can be copied from the central library to the design and processes can be exported from the design to ASCII. When importing processes in ASCII via Library Services, all required parameters must be present or the process will fail. For more information, consult online help associated with the Material / Process Editor.
Materials
The Material properties are grouped for common properties and properties relevant to the following types of materials (Figure 5-5): Capacitors Conductors Inductors Resistors Figure 5-5. Material / Process Editor (Materials Node)
Use the right mouse button popup menu commands to add new materials to the materials / process data that is stored in your central library.
5-13
Using Other Tools and Library Manager Utilities Performing Backups
The name of the material must be unique within the library and is limited to a maximum of 80 characters. Use alphanumeric characters when creating materials. Do not use the following keyboard characters: \ (forward slash) ( (open parenthesis) ) (closed parenthesis) ! (exclamation or bang)
Performing Backups
Perform a nightly backup of your central library and all associated files and directories. This ensures that all data is preserved in the event of a disk drive failure or if the data becomes corrupted. Information should be stored on a designated backup system or another machine with sufficient disk space. Contact your system administrator for information on performing backups.
5-14
Appendix A DxD to Expedition Flow Wizards

Introduction
This appendix provides information and procedures for using two workflow wizards associated with Library Manager using the DxD-Expedition flow: DxDesigner to Library Manager Migration Wizard DxDesigner Project Translation Wizard on page A-14
If you are using Library Manager for the DC/DV-Expedition flow, ignore this appendix.
DxDesigner to Library Manager Migration Wizard

Library Manager software combines library editors and utilities used by Mentor Graphics into a single, centralized environment. The library created by the Library Manager is called a central library and integrates symbols, cells, padstacks, part data, IBIS models, and layout templates under a single directory structure. The software creates a <central_library_name>.lmc file. Use the DxDesigner/Library Manager Library Migration Wizard to add existing DxDesigner symbol libraries to a new or existing central library. Note The migration wizard is case-sensitive on Linux and UNIX and operates on directories with lowercase syntax. If you encounter problems, check the symbol library (sym) directory and rename the directory using lowercase syntax.
Invoking the Migration Wizard

On Windows, click Start > Programs > Mentor Graphics SDD > DxDesigner-Expedition Flow> Data and Library Management > DxD to Library Manager Migration Wizard to invoke the migration wizard software. On Linux and UNIX, open a terminal window, ensure the directory is set to $SDD_HOME/common/linux/bin, and type DxDLMCWizard. This displays the DxDesigner/Library Manager Library Migration Wizard dialog box which allows you to add DxD symbol libraries to an existing central library (*.lmc) file or create a new central library and add DxD symbol libraries.
A-1
DxD to Expedition Flow Wizards DxDesigner to Library Manager Migration Wizard
Specifying a Target Central Library

Before migrating DxD symbols, you must specify a central library that will receive the symbol libraries (Figure A-1). Figure A-1. Selecting or Creating a Target Central Library
Use this dialog box to perform one of the following actions: Create a New Central Library - the software creates a new central library file in the location you specify. The central library filename matches the directory name where it resides. Use an Existing Central Library - the software accesses an existing central library.
As you add DxD symbol libraries to a central library, Library Manager maintains information on what library paths were used to create each central library symbol partition. This information is stored in the DxDMigrationMap.txt file in the SymbolLibs subdirectory of the central library.
Creating a New Central Library

1. Click the Create a New Central Library radio button and either key in the full path of the directory where the new central library will reside or click Browse to select or create the destination folder for the central library. The Select a new Central Library directory dialog box displays.
A-2
2. Browse to a directory that will contain the new central library and click OK. The software creates a new central library (*.lmc) file using the name of the directory you selected. For example:
<drive>:\MyNewDxCL\MyNewDxCL.lmc
3. Click Next to display the next dialog box which provides tools to add DxD symbol libraries to the central library file.
Using an Existing Central Library

1. Click the Use an Existing Central Library radio button and either key in the full path of the directory where the central library resides or click Browse to select the central library (*.lmc) file. The Select a Central Library database file to open dialog box displays. 2. Browse to a directory where the central library resides, select the central library (*.lmc) file, and click OK. 3. Click Next to display the next dialog box which provides tools to add DxD symbol libraries to the central library file. The software provides three methods to add symbol libraries to the central library: Specifying a List of Symbol Libraries Searching for Symbol Libraries in a Specified Directory Searching DxD Projects for Symbol Libraries
Selecting a Migration Method

The software provides three methods to add symbol libraries to the central library (as shown in Figure A-2):
A-3
Figure A-2. Selecting a Migration Method
Specifying a List of Symbol Libraries - Use this option to specify a list of defined DxD symbol libraries that the wizard will migrate to the selected central library. The migration wizard verifies that the specified folder(s) are valid DxD symbol library folders and, if so, migrates the symbols in these directories to a symbol partition of the same name in the central library. Specifying a List of Directories to be Searched for Central Libraries - Use this option to specify a list of directories that the wizard queries for symbol libraries. The migration wizard reads the directories in the list, searches for valid DxD Symbol library folder, and migrates all symbol library files (including sym, sch, wir and pkt) in these directories to the corresponding symbol partition(s) in the central library. Specifying a List of Projects to be Searched for Symbol Libraries - Use this option to select DxDesigner projects that contain symbol libraries that you want to migrate to a central library. This dialog box reads the DxDesigner project.lst file and displays the names and paths to these projects.
Select the migration method from the dialog box and click Next to proceed with the migration wizard.
A-4
Specifying a List of Symbol Libraries

The dialog box in Figure A-3 appears when you select the Specifying a List of Symbol Libraries radio button in the migration wizard and click Next. Figure A-3. Specifying a List of Symbol Libraries to Migrate
Use this dialog box to specify a list of defined DxD symbol library directories that the wizard will migrate to the selected central library. The migration wizard reads the directories in the list, verifies that the specified folder(s) are valid DxD symbol library folders, and migrates all symbol library files (including sym, sch, wir and pkt) in these directories to the corresponding symbol partition(s) in the central library. These symbol library folder and files appear in the SymbolLibs directory in the central library structure. 1. Click Add/Create to enter the full directory path to directories that contain symbol libraries you want to migrate. You can also browse for the appropriate directory on your machine. 2. Repeat Step 1 to add additional symbol library directory paths. Use Delete to remove any directory path you specified earlier in the dialog box.
A-5
Tip: Use the Move Up and Move Down icons to reorder the list of directories in the dialog box. The order of symbol library directories you specify in the dialog box affects the partition search path scheme for symbol libraries in that partition. By putting a frequently used partition at the top of the Symbol Library Directories list, the software automatically searches that partition first during a search. This increases the speed and efficiency of searches. 3. Click Next; the dialog box (Figure A-4) displays the full directory path to all symbol libraries within the directory you queried. The partition name associated with each symbol library also displays. Note If you select a path that does not include DxD symbols, the software displays an error. Click OK and the software removes the errant entry from the list. Figure A-4. Confirming Symbol Libraries to Migrate
4. Use Add and/or Delete to edit the list of symbol libraries in the dialog box. Highlight any entry in the Symbol Library Directory list and browse for a different symbol library directory.
A-6
Tip: You can also edit the partition name in the dialog box to place the symbol and associated files in a user-specified partition in an existing central library. 5. Click Finish; the software migrates all symbol libraries in the directories you specified in the dialog box. The software creates the DxDMigrationMap.txt file in the SymbolLibs directory which records the symbol libraries that have been migrated. The software also creates a migration.log file in the newly created symbol partition folder to identify the symbols that have been successfully migrated. The following message appears: The Migration Wizard completed. Would you like to run it again? Note Problematic DxDesigner symbols are not migrated by the wizard and the software generates errors. However, the wizard continues to migrate valid DxD symbols and adds them to the selected central library. The migration.log file in each newly created symbol partition folder identifies the symbols migrated to a central library. Once these errant symbols are corrected, you can run the migration wizard again to migrate these symbols. 6. Click Yes to repeat the migration process. Click No to exit the migration wizard. Note Once you import DxD symbols into a central library using the Library Migration Wizard, the software records the transaction in the DxDMigrationMap.txt file. However, if you delete these symbol partitions from the central library (for example, using Library Services in Library Manager) and attempt to migrate the same DxD symbol libraries using the wizard, the software generates errors. The DxDMigrationMap.txt file assumes the symbol libraries remain in the referenced central library and does not track symbol libraries once they are migrated to the central library. To work around this problem, use the Import Symbol command from the popup menu to import these symbols. To invoke this command in DxD-Expedition Library Manager, highlight the symbol partition in the navigation tree, right click the mouse, select Import Symbol, and select the DxDesigner symbols to import.
Searching for Symbol Libraries in a Specified Directory

The dialog box in Figure A-5 appears when you select the Specifying a List of Directories to be searched for Symbol LIbraries radio button from the migration wizard and click Next.
A-7
Figure A-5. Searching for Symbol Libraries in a Directory
Use this option when you are unsure of the exact path of the DxD Symbol Libraries. You can specify a parent folder and the Wizard can then search for symbol libraries to any arbitrary subdirectory depth. The migration wizard reads the directories in the list and searches the specified folders for DxD symbol library folders. The DxD symbol library found in these folders are then listed on the next page of the wizard. However, if no DxD symbol libraries are found in the specified folder(s), then the software issues an error message. 1. Click Add/Create to enter the full path to a directory that you want to search for symbol libraries. You can also browse for the appropriate directory on your machine. 2. Repeat Step 1 to add additional directory paths. Use Delete to remove any directory path you specified earlier in the dialog box. 3. Click Next; the dialog box (see Figure A-6) displays the full directory path to all DxD symbol libraries within the directory you queried. The partition name associated with each symbol library also displays.
A-8
Tip: You can edit the Partition name for any partition in the list. This is useful when you want to have a different partition name than the one displayed. This can occur when library names collide. Figure A-6. Confirming Directories with Symbol Libraries to Migrate
4. Use the Add and Delete icons to edit the list of symbol libraries in the dialog box. Highlight any entry in the Symbol Library Directory list and browse for a different symbol library directory. 5. Click Finish; the software reads symbol libraries in the directories you specify and migrates them into partitions in the SymbolLibs directory within the central library. The software creates the DxDMigrationMap.txt file in the SymbolLibs directory which records the symbol libraries that have been migrated. The following message appears: The Migration Wizard completed. Would you like to run it again?
A-9
Problematic DxDesigner symbols are not migrated by the wizard and the software generates errors. However, the wizard continues to migrate valid DxD symbols and adds them to the selected central library. The migration.log file in each newly created symbol partition folder identifies the symbols migrated to a central library. Once these errant symbols are corrected, you can run the migration wizard again to migrate these symbols. 6. Click Yes to repeat the migration process. Click No to exit the migration wizard. Note Once you import DxD symbols into a central library using the Library Migration Wizard, the software records the transaction in the DxDMigrationMap.txt file. However, if you delete these symbol partitions from the central library (for example, using Library Services in Library Manager) and attempt to migrate the same DxD symbol libraries using the wizard, the software generates errors. The DxDMigrationMap.txt file assumes the symbol libraries remain in the referenced central library and does not track symbol libraries once they are migrated to the central library. To work around this problem, use the Import Symbol command from the popup menu to import these symbols. To invoke this command in DxD-Expedition Library Manager, highlight the symbol partition in the navigation tree, right click the mouse, select Import Symbol, and select the DxD symbols to import.
Searching DxD Projects for Symbol Libraries

The dialog box in Figure A-7 appears when you select the Specifying a List of Projects (*.dproj files) to be searched for Symbol Libraries radio button from the migration wizard.
A-10
Figure A-7. Searching DxD Projects for Symbol Libraries
Use this dialog box to select DxDesigner projects that contain symbol libraries that you want to migrate to a central library. This dialog box reads the DxDesigner project.lst file and displays the names and paths to these projects. The dialog box specifies the location of the projects that can be searched for symbol libraries to be added to the central library. 1. Select the appropriate projects from the Project list (using check boxes). 2. Click Next; the dialog box displays a list of symbol library directories, partitions, and aliases (Figure A-8). The software uses the name in the Partition column when migrating symbols to the central library data structure.
A-11
Figure A-8. Confirming DxD Projects to Migrate
3. Edit the Partition names as necessary before proceeding with the migration. These partition names will be written to the SymboLibs directory of the target central library. 4. Click Finish; the software reads symbol libraries associated with the DxD project files you specify and migrates them into partitions in the SymbolLibs directory within the central library. The software creates the DxDMigrationMap.txt file in the SymbolLibs directory which records the symbol libraries that have been migrated. The following message appears: The Migration Wizard completed. Would you like to run it again? Problematic DxD symbols are not migrated by the wizard and the software generates errors. However, the wizard continues to migrate valid DxD symbols and adds them to the selected central library. The migration.log file in each newly created symbol partition folder identifies the symbols migrated to a central library. Once these errant symbols are corrected, you can run the migration wizard again to migrate these symbols. 5. Click Yes to repeat the migration process. Click No to exit the migration wizard.
A-12
Note Once you import DxD symbols into a central library using the Library Migration Wizard, the software records the transaction in the DxDMigrationMap.txt file. However, if you delete these symbol partitions from the central library (for example, using Library Services in Library Manager) and attempt to migrate the same DxD symbol libraries using the wizard, the software generates errors. The DxDMigrationMap.txt file assumes the symbol libraries remain in the referenced central library and does not track symbol libraries once they are migrated to the central library. To work around this problem, use the Import Symbol command from the popup menu to import these symbols. To invoke this command in DxD-Expedition Library Manager, highlight the symbol partition in the navigation tree, right click the mouse, select Import Symbol, and select the DxD symbols to import.
Confirming Migration Libraries

Use this information only dialog box to view a list of symbol libraries, directories of symbol libraries, or DxDesigner projects with symbol libraries before the migration wizard invokes. If you find discrepancies or errors, click Back to return to the appropriate page in the migration wizard or make appropriate edits on this page. Click Finish; the software displays messages to inform you of the results of the wizard.
Moving Migrated Symbols to a Different Central Library Partition

If you move migrated DxDesigner symbols from one symbol partition to another in a central library, DxD schematics have missing components on the schematic (highlighted by a box in place of the symbols on the schematic). This also occurs using symbol libraries within DxD projects. Therefore, ePD2004 provides a procedure via the Altran command line utility to update the library aliases on their DxD schematic instances (after the symbols have been moved from one partition to other). Use the altran utility to change the alias in a design. You must provide the command line parameters for both the old and new alias before running altran because there is no feature to automatically find the new alias. Perform the following steps: 1. Open schematic and note ViewBase errors in Output Log Window and empty white boxes where the component should be. (note the old alias). 2. Use the comp command with the symbol name only to find and add the named symbol. 3. Open properties on the newly added component to determine the new alias. 4. Close the schematic without saving changes.
A-13
DxD to Expedition Flow Wizards DxDesigner Project Translation Wizard
5. Use altran with the correct old and new alias's to fix the design. For information on using the Altran utility in DxDesigner, see the DxDesigner online help and related documentation.
DxDesigner Project Translation Wizard

Library Manager software combines library editors and utilities used by Mentor Graphics CAD and CAE tools into a single, centralized environment. The library created by the Library Manager is called a central library and integrates symbols, cells, padstacks, part data, IBIS models, and layout templates under a single directory structure. The software creates a <central_library_name>.lmc file. See Using IBIS Software on page 5-3 for more information on IBIS software. Before invoking the DxDesigner Project Translation Wizard, use the DxD Library Migration Wizard on DxD projects to migrate symbol libraries in selected projects into a central library. See DxDesigner to Library Manager Migration Wizard on page A-1 for more information. Then, run this Wizard (the DxDesigner Project Translation Wizard) to point these migrated DxD projects and their symbol libraries to the central library created by the Project Translation Wizard.
Invoking the DxD Project Translation Wizard

On Windows, click Start > Programs > Mentor Graphics SDD > DxDesigner-Expedition Flow> Translators and 3rd Party Interfaces > Project Translation Wizard to invoke the DxD Project Translation Wizard. On Linux, open a terminal window, ensure the directory is set to $SDD_HOME/common/linux/bin, and type PFProjWizard. The Wizard displays the DxDesigner/Library Manager Project Translation Wizard dialog box which allows you to select DxDesigner projects to translate. Note The list of DxDesigner projects eligible to translate is generated from the project.lst file in the %WDIR%\vf directory. To add a project to this list, you must open the project in DxDesigner and translate it.
Selecting DxD Projects to Translate

Use the dialog box in Figure A-9 to select DxDesigner projects that will be upgraded to use the central library data model.
A-14
Figure A-9. Select DxDesigner Projects to Translate
As you add DxD symbol libraries to the central library using the Library Migration Wizard, the Migration Wizard creates/updates the DxDMigrationMap.txt file in the <Central_Library_Folder>/SymbolLibs directory. The DxDMigrationMap.txt file stores the directory path from where the library was copied and the directory path where it is stored in the central library. Note The original DxD Symbol Libraries remain in the current location and can be used until each project is translated. Any libraries that the DxD project uses that are not specified in the DxDMigrationMap.txt file remain in the project as local libraries. The DxD Project Translation Wizard displays these local libraries so you can confirm that you want them to remain as local libraries or determine if they need to be translated. The DxD Project Translation Wizard reads the DxDesigner project (*.dproj) file to determine if the project already references a central library. If the project already references a central library, the software generates an error message. Otherwise, the software displays the next Project Translation Wizard dialog box which allows you to browse for or select a central library. Upon completion, the Wizard updates the DxDesigner project (*.dproj) file to include information on central library references.
A-15
Specifying DxDesigner Projects to Translate

1. Review the list of projects (displayed with associated directory paths in Figure A-9 on page A-15). This list is generated from the project.lst file in the %WDIR%/vf directory. 2. Select the DxD projects to upgrade to use the central library data model. You can select multiple projects if you want all of them to use the same central library 3. Click Next to specify the central library that contains the symbol libraries you migrated using the DxD to Library Manager Migration Wizard (see Figure A-10 on page A-17). If the project (*.dproj) file already references a central library, an error message displays. The project translation wizard updates paths to the local DxD symbol libraries to point to the central library symbol partitions using the DxDMigrationMap.txt to compare the paths of the local libraries. The DxD Project Translation Wizard compares the library list in the DxDMigrationMap.txt file with the library paths in the ViewDraw.ini file. This instructs the software to leave path information to additional local libraries that don't exist in the central library. Note Libraries are not compared on a symbol-to-symbol basis (in other words, there may be symbols missing from the central library partition because some extra symbols were added to the local libraries after migration or some symbols were deleted by the librarian from the central library partitions). If some symbols are missing from the central library symbol partition and you are using (or want to use) those symbols in the design, use the Import Symbol popup command to import the missing symbols. Invoke the Import Symbol popup command by selecting a symbol partition in the Project Navigator Tree, click the right mouse button, and import symbols using the dialog box.
Selecting a Central Library

The dialog box in Figure A-10 appears after you select project(s) from the list to update them to use a central library. Browse for or select a central library that contains migrated symbol libraries using the DxD to Library Manager Migration Wizard. Note Do not select a DC/DV-Expedition central library. A DC/DV-Expedition central library also has a *.lmc filename extension.
A-16
Figure A-10. Specifying a Central Library Destination for Translated DxD Projects
Click Next. The software updates the DxD project (*.dproj) files for the projects selected to use the central library. The wizard adds the path of the central library to the project (.dproj) file. The wizard reads the DxDMigrationMap.txt file in the Central Library directory (in the <Central_Library_Folder>/SymbolLibs/ directory) and determines the corresponding partition in the selected central library by comparing the paths in the ViewDraw.ini for the project and the DxDMigrationMap.txt. If the paths match, the path in ViewDraw.ini is updated with the path of the symbol partition from the DxDMigrationMap.txt. The wizard dialog box disappears if no libraries are found in the projects that were not migrated. Otherwise, the DxD Project Translation Wizard displays a list of these libraries so that you can migrate them or continue to use them as local libraries. The order of libraries in the project will be maintained. Aliases will also be maintained but will be updated to point to the symbol library location in the central library. The software also updates the DxD project to include the path to the central library. Note Libraries are not compared on a symbol-to-symbol basis (in other words, there may be symbols missing from the central library partition because some extra symbols were added to the local libraries after migration or some symbols were deleted by the librarian from the central library partitions). If some symbols are missing from the central library symbol partition and you are using (or want to use) those symbols in the design, use the Import Symbol popup command to import the missing symbols. Invoke the Import Symbol popup command by selecting a symbol partition in the workspace tree, click the right mouse button, and import symbols using the dialog box.
A-17
Library paths can still be used in the DxD Project Editor. For example, if you set the Search Order Scheme field to "Local to Project", the software reads the ViewDraw.ini file and displays a list of all non-translated symbol libraries in the dialog box. If the Search Order Scheme filed is set to "Central Library Default", the software displays a list of translated symbol libraries.
Changing Symbol Library Permissions

Once DxD projects are translated via the DxD Project Translation Wizard, you can change the permission of the DxD symbol libraries used in the design according to the permission provided to you by the librarian for the corresponding symbol partitions. Note that you are making the DxD symbol library as read-only or writable for a specific design only. You are not changing the actual permissions of the symbol libraries. Symbol library permissions are managed by the librarian.
Viewing Local Libraries in DxD Projects (Not Translated to a Central Library)

This dialog box displays the libraries listed in the projects ViewDraw.ini file for which no corresponding entry was found in DxDMigrationMap.txt file (in other words, those libraries that were not migrated to a central library using the DxD to Library Manager Migration Wizard). These libraries remain as local libraries in the project. You can migrate them to a central library or continue to use them as local libraries. Note If you decide and add these missing libraries to the central library using the DxD Manager Migration Wizard, then you must update the library paths manually to the central library symbol partition by invoking the Library Settings dialog box and changing the path. Confirm that the libraries are included in the central library search path scheme and then invoke the Project Editor from the Project Navigation Tree - Design Roots entry. This resets the library paths for the project to include the central library symbol partitions as well as the project's local libraries. Click Finish to dismiss the dialog box and exit the DxD Project Translation Wizard.
A-18
Appendix B Using Design Architect with Expedition Tools

Introduction
This appendix provides information on the Expedition only flow (using Design Architect with Expedition tools, such as Expedition PCB and Library Manager). See Invoking Library Manager, Creating a New Central Library, and Selecting a Flow Type on page 2-2 for more information. The information in this appendix assumes you do not access design data via DMS. We strongly recommend that you use DMS when processing designs from Design Architect through Expedition tools.
Prerequisites
To minimize the disruption of the existing DA/BA process, a copy of Package is required. Also set the MGC_PKG_XINFO environment variable as follows: MGC_PKG_XINFO=1
This enables PACKAGE to provide additional information to Expedition regarding heterogeneous components.
Translating a DA Schematic to Expedition PCB

Use the following steps to translate a Design Architect schematic to Expedition PCB:
Using Design Architect

1. Invoke Design Architect software. 2. Set the PCB Design Viewpoint and save. 3. Exit Design Architect (DA) software.
Using Package
1. Execute Package software.
B-1
Using Design Architect with Expedition Tools Translating a DA Schematic to Expedition PCB
2. Select Check Build and ensure that no errors display. 3. Select Build and ensure no errors display. 4. Select Save (within Package) and exit Package software.
Using Library Manager

Note See Using Library Manager on page 2-1 for information on using Library Manager to create a new central library and to create entries for all the parts in your design. 1. Invoke Library Manager software. The Library Manager interface displays. 2. Create a new central library. Select the Expedition-only flow type from the dialog box. For more information on creating a new central library see Invoking Library Manager, Creating a New Central Library, and Selecting a Flow Type on page 2-2. 3. Create entries for all the parts in the design: Padstacks (via the Padstack Editor) - physical pads for footprints (see Creating Pads, Holes, and Padstacks on page 2-55 for more information). Cells (via the Cell Editor) - physical footprints (see Creating Cells on page 2-65 for more information) Parts via the Part Editor - part name pin mapping (see Creating Parts (Using Part Editor) on page 2-74 for more information)
Note When processing DA symbols using the Part Editor in Library Manager, the symbol names used in Part Editor must use the DA comp property value. For example: comp_<part number> where: comp = the value of the comp property on the DA symbol part number = part number you are creating. 4. Save your work in Library Manager and exit the software.
Using the Expedition PCB Job Management Wizard

1. Create a new PCB job. 2. Enter a new project file (for example; demo.prj). 3. Click No to the schematic message. 4. Click OK to the central library message. 5. Browse for and select the central library.
B-2
6. For Netlist, select Design Architect". 7. Browse for and select the Design Architect Component directory. 8. Select a PCB Layout Template. 9. Complete the job creation.

1. Open the new <project name>.pcb file. 2. Select Setup > Project Integration. 3. Run Forward Annotate and verify that the process was successful. 4. Select Place > Place Parts and Cells. 5. Place all unplaced parts within the board outline. 6. If necessary, select Route > Swap > Gates. 7. If necessary, select ECO > Renumber Ref Des. 8. Select Setup > Project Integration. 9. Run Back Annotate and verify that the process was successful. If the process is unsuccessful, error messages display and provide information needed to run a successful back annotation. 10. Save the PCB design.
Using DVE
Use the following steps in DVE if DA and Expedition PCB are not loaded on the same machine. For example, if you use Design Architect on a UNIX machine and Expedition PCB on a Windows machine, you must perform these steps. Otherwise, go to the next procedure. 1. Set the PCB Design viewpoint. 2. Run Import ASCII BA (Board Architect) and browse for the following: /<job_name>/expbackanno.txt 3. Verify that changes from Expedition PCB are present in the schematic. 4. Save the schematic and exit DVE.
B-3
Using Packager
To complete the synchronization between Design Architect and Expedition PCB (ensuring that the data is synchronized), perform the following steps in Packager and Expedition PCB: 1. Select Check Build and verify there are no errors. 2. Select Build and verify there were no errors. 3. Save the design and exit Packager.

1. Select Setup > Project Integration to display the dialog box. 2. Select Forward Annotate and verify that the process completed successfully. 3. Save the PCB design and exit Expedition PCB.
B-4
Appendix C Upgrading Central Libraries for Linux and UNIX Use

Introduction
Note Information in this appendix applies only to Linux and UNIX operating system users who want to access and use central libraries created on Windows operating systems prior to SDD2004 SPac1. Therefore, this information applies to DxDesigner-Expedition flow users only in this release. This appendix provides information on using the lmcwin2unix script, which adjusts central libraries that were created on the Windows operating system prior to SDD2004 SPac1 for use on the Linux and UNIX operating systems. The lmcwin2unix script traverses the directories of a specified central library and adjusts directory names to eliminate case-sensitivity problems that might occur on Linux and UNIX. For example, the lmcwin2unix script changes a directory named either Sym or SYM to sym (all lower-case text) to ensure operability on Linux and UNIX operating systems. After running this script, the selected central library can be accessed on either Linux, UNIX, or Windows. See Subdirectories and Files Created by Library Manager on page 2-6 for information on the sym subdirectory. Tip: If you do not run the lmcwin2unix script prior to opening a central library originally created on Windows, the software may generate errors on Linux or UNIX. The lmcwin2unix script is located in the following directory and must be invoked from a command prompt:
${SDD_HOME}/common/linux/bin/lmcwin2unix
Determine what Windows-based central libraries you want to access on Linux or UNIX before invoking the script. Be sure to note the directory where each central library resides. After running this script, the central library can be opened in either Linux and UNIX operating systems.
C-1
Upgrading Central Libraries for Linux and UNIX Use Using the Script
Using the Script

Use the following steps to invoke the lmcwin2unix script to eliminate case-sensitivity problems in a central library that might occur on Linux and UNIX: Note There is no dialog box or wizard associated with this script. 1. Open a terminal window on Linux or UNIX. 2. Key in the following at the prompt:
lmcwin2unix <Central Library Directory>
where lmcwin2unix is the script executable name and <Central Library Directory> is the directory where the selected central library (*.lmc) file resides. The software accepts either full or relative directory paths. Note You can only specify one central library directory at a time. Do not specify a central library (*.lmc) filename in the command line argument. Example:
$ lmcwin2unix /data/job1/centlibs/t1
3. Press Enter. The script adjusts the central library directories to resolve case-sensitivity issues. The software displays messages when a directory was renamed and how it was renamed. Example:
Renaming /data/job1/centlibs/t1/SymbolLibs/Logic/Sym to /data/job1/centlibs/t1/SymbolLibs/Logic/sym
Note Messages display only if the script resolved case-sensitivity issues within the selected central library directory. The central library is now ready for use on Linux, UNIX, and Windows.
C-2
Appendix D Using DxDatabook Data Editor in Library Manager

Library Management tools for the DxD-Expedition flow provides the capability to view and (on Windows) edit parametric data in a database. Use library management tools to create and edit a DxDatabook configuration file and perform simple edits to the underlying parametric data database using commands available from the workspace tree. Use DxDatabook to instantiate symbols on the schematic. The DxDatabook requires a configuration file which is created using library management tools (see What is a DxDatabook User Configuration (*.dbc) File?). Note DxDatabook software is delivered with DxDesigner. See DxDesigner online help and documentation for additional details on DxDatabook addin. Apart from the functionality of creating and editing the DxDatabook configuration file, library management software provides functionality to edit the underlying database containing the parametric data. See Adding a Table to a Library Configuration on page D-15. This functionality is similar to Library Studio software; however, you can perform simple edits and changes to the parametric data database instead of invoking Library Studio software to complete the changes.
What is a DxDatabook User Configuration (*.dbc) File?

The DxDatabook library structure is contained in the user configuration file (.dbc file). The DxDatabook user configuration file name is same as the central library name and is stored in the same directory. For example, if Company_Library.lmc is the central library, the software creates and uses the Company_Library.dbc file. To easily manage a .dbc file for multiple users, place this file on a network file server and share it. Tip: To safeguard the configuration on a network file server, set the .dbc file access permissions to read-only for all users. See Using a Configuration (*.dbc) File on page D-8 for more detailed information on the DxDatabook user configuration file.
D-1
Using DxDatabook Data Editor in Library Manager Setting Environment Variables
Setting Environment Variables

When using DxDatabook Data Editor software with a central library, you may have to add or specify certain environment variables depending upon the operating system and/or the type of ODBC or Oracle database you are using. For example, you may have to set Oracle databaserelated environment variables.
Using the tnsnames.ora File (Oracle Client)

If Oracle Client is not installed to your machine, the software automatically sets the appropriate Oracle environment variables. However, you must copy the tnsnames.ora file to the following directory:
${SDD_HOME}/common/${SDD_PLATFORM}/ORA_NLS
If Oracle Client is installed to your machine (and the ORACLE_HOME environment variable is set correctly), the software uses your Oracle Client software.
Using Parametric Databases on Supported Platforms

DxDatabook Data Editor in Library Manager is certified using the database types and versions defined in Table D-1. Other versions of Oracle may work; however, this version of software is certified based on the information in Table D-1. Table D-1. Database Types Configurable via the Library Wizard Supported Database Types Oracle V9.x World Wide Web server (WWW) ODBC Windows XP & 2000 Yes Yes* Yes HP11.00 & 11.i Yes Yes* No Solaris 8, 9 & Linux REL3.0 & 10 4.0 Yes Yes* No Yes Yes* No
* Supported as Read Only.
D-2
Using DxDatabook Data Editor in Library Manager Connecting to Parametric Databases
Table D-2 lists certified ODBC data sources and operating systems supported by DxDatabook Data Editor. Other data sources may work; however, this version of software is certified on the data sources and operating systems listed in Table D-2. Table D-2. ODBC Data Sources and Operating Systems Supported by DxDatabook Data Editor Supported Database Types MS SQL Server Excel MS Access Windows XP & 2000 Yes Yes* Yes HP11.0 & 11.i Yes** Yes** Yes** Yes** Solaris 8, 9 & Linux REL3.0 & 10 4.0 Yes** Yes** Yes** Yes** Yes** Yes** Yes** Yes**
Text, CSV delimited Yes* & Tab delimited * Supported as Read Only.
** Supported as Read Only but requires DxWebPack.
Connecting to Parametric Databases

You can integrate DxDatabook to a variety of databases formats, including Microsoft Access, Oracle, MS SQL Server, and so on (see Using Parametric Databases on Supported Platforms on page D-2 for more information). You can also import component information from a central library into a data source. Note If the database file is located on the network, make sure that all users can access it. For example, if you are using a Microsoft Access database, copy the .mdb file to a location that is accessible to all users. DxDatabook uses Open Database Connectivity (ODBC) and Oracle to connect to databases. While a database contains the actual component data, a data source contains information needed by DxDatabook to locate and access the database.
Creating an ODBC Data Source on Windows

Use the following steps to create an ODBC Data Source connection to a parametric database. Note In this exercise, you will create a Microsoft Access database on a Windows machine. 1. Click Start > Settings > Control Panel; utilities in the Control Panel window appear.
D-3
Using DxDatabook Data Editor in Library Manager Creating an ODBC Data Source on Windows
2. Double-click Administrative Tools. 3. Double-click Data Sources (ODBC) Administrator dialog box appears. and the ODBC Data Source
Figure D-1. ODBC Data Source Administrator Dialog Box
4. View the User DSN tab and verify that your Data Source Name (DSN) is not already used for a User DSN. Tip: If the DSN is already in use, either remove the User DSN or change the name of the DSN you are adding. 5. Click the System DSN tab and click Add; the Create New Data Source dialog box appears (Figure D-2).
D-4
Figure D-2. Create New Source Dialog Box
6. Select the type of database connection you want to create (see Table D-2 on page D-3). In this case, click Microsoft Access Driver (*.mdb) and click Finish. The ODBC Microsoft Access Setup dialog box appears (Figure D-3).
D-5
Figure D-3. ODBC Microsoft Access Setup Dialog Box
7. Key in the Data Source Name and the database description as shown in Figure D-4. Figure D-4. ODBC Microsoft Access Setup Dialog Box with Name and Description
D-6
8. To create a new .mdb file, click Create and key in DxDBook.mdb in the New Database dialog box. You can create this in a user-defined folder within an existing central library or another location on your machine. For example, in Figure D-5, the \company_library directory is specified in the dialog box. To select an existing database file, click Select in the ODBC Microsoft Access Setup dialog box (Figure D-4) and specify the .mdb file to use. Figure D-5. Create New Database Dialog Box
If the database is to be accessed over a network, type the Universal Naming Convention (UNC) path to the .mdb file in the Database Name field. Tip: Avoid using Browse when defining the UNC path to the .mdb file. Browse yields a path containing a network drive letter, which may be different with each user. Type the UNC path to avoid potential problems for users who use different drive letters. For example: \\server1\D\data\dxdb\DxDBook.mdb 9. Click OK; the software creates the DxDBook.mdb file in the directory you specify. If you selected an existing database (.mdb file), the software associates the selected database with the central library. The ODBC Data Source Administrator dialog box appears (see Figure D-6).
D-7
Using DxDatabook Data Editor in Library Manager Using a Configuration (*.dbc) File
Figure D-6. ODBC Data Source Administrator Dialog Box
Using a Configuration (*.dbc) File

The user configuration file maps DxDatabook libraries to the component libraries. The libraries store data about components that you use in your design. For more information, see What is a DxDatabook User Configuration (*.dbc) File? on page D-1.
Setting Up a Configuration (*.dbc) File for Multiple Users

A read-only .dbc file centrally-located operates correctly if others do not need to add their own libraries, or do any personal customization to the DxDatabook configuration. If others need to use a centrally-defined DxDatabook configuration with the ability to add their own libraries, use the DxDatabook Base Configuration file (.dbb file). When using a .dbb file, each user has a personal .dbc file, which acts as an overlay of the .dbb file. Each personal .dbc file contains a link to the centrally-located .dbb file. Tip: In this setup, you can store the .dbb file on a file server or an FTP site.
D-8
Using DxDatabook Data Editor in Library Manager Creating a DxDatabook (*.dbc) File (Edit Databook Configuration Command)
Implement the configuration scheme using a .dbb file independently of the DxWebPack. Think of the .dbb file as a way of centralizing the administration of the DxDatabook Configuration. DxWebPack is a way of centralizing the database functionality. When you create a new database or select an existing database and configure an ODBC data source on Windows, you are ready to edit parametric data using the new functionality available in DxDatabook.
Creating a DxDatabook (*.dbc) File (Edit Databook Configuration Command)

Use the Edit Databook Configuration command from the Navigator Tree popup menu in Library Manager to create a DxDatabook configuration (*.dbc) file (Figure D-7). Use the Edit Databook Configuration command to perform the following: Create a user configuration file with the same name as the central library (for example, Company_Library.dbc). See Creating a New, Empty DxDatabook Configuration on page D-9 for more information. Copy an existing configuration file and applies it to the active central library. See Creating a New DxDatabook Configuration from an Existing Configuration on page D-11 for more information.
Figure D-7. Accessing Edit Databook Configuration Command in Library Manager
Creating a New, Empty DxDatabook Configuration

The user configuration file maps DxDatabook libraries to the component libraries. The libraries store data about components that you use in your design. Use the following steps to create a new, empty DxDatabook configuration: 1. Highlight the active central library (*.lmc) file in the Library Navigator Tree, click the right mouse button, and select the Edit Databook Configuration command. The New DxDatabook Configuration dialog box appears (Figure D-8). Note If the configuration file already exists in the central library, the Configure dialog box displays (see Figure D-10 on page D-11).
D-9
Figure D-8. New DxDatabook Configuration Dialog Box (Create an Empty Configuration)
2. Ensure the Create an Empty Configuration option is selected and click OK; the Properties dialog box displays (see Figure D-9). Figure D-9. Central Library Properties Dialog Box
3. Enter a value in the Symbol Attribute for PDB Part Number field to define which DxDesigner attribute is equivalent to an Expedition part number. The software uses this information in the DxDatabook Configuration to determine what column in the DxDatabook table is equivalent to the Expedition part number. 4. Click OK; the Configure dialog box displays (see Figure D-10).
D-10
Figure D-10. Configure DxDatabook Database Dialog Box
The left pane displays the component libraries in a tree structure, and shows the tables contained in each library. The right pane shows detailed information about the selected library. 5. Once you add component libraries using the Configure dialog box, click OK. The software writes the new configuration file to the same location as the active central library and retains the same file name as the active central library.
Creating a New DxDatabook Configuration from an Existing Configuration

Use the Copy an Existing Configuration option to copy an existing DxDatabook configuration (*.dbc) file to the central library directory. The software automatically renames the DxDatabook configuration file to match the central library file name. 1. Highlight the active central library (*.lmc) file in the Library Navigator Tree, click the right mouse button, and select the Edit Databook Configuration command. The New DxDatabook Configuration dialog box appears (Figure D-11).
D-11
Figure D-11. New DxDatabook Configuration Dialog Box (Copy an Existing Configuration)
2. Ensure the Copy and Existing Configuration option is selected and click OK; the Open dialog box appears and prompts you to browse for a Databook configuration (*.dbc) file. 3. Select the applicable configuration (*.dbc) file and click Open. The Central Library Properties dialog box appears (see Figure D-9 on page D-10). 4. Enter a value in the Symbol Attribute for PDB Part Number field to define which DxDesigner attribute is equivalent to an Expedition part number. The software uses this information in the DxDatabook Configuration to determine what column in the DxDatabook table is equivalent to the Expedition part number. 5. Click OK. The Configure DxDatabook Database Dialog Box appears (see Figure D-10 on page D-11). 6. Once you add component libraries using the Configure dialog box, click OK. The software writes the new configuration file to the same location as the central library and retains the same name as the central library.
Adding Component Libraries to the Configuration (*.dbc) File

Note Using the Add Library command is NOT a required step if the Configure dialog box (Figure D-10) already added the Libraries based on the Library Manager Part partition names. Use the Add Library dialog box to: Add a component library to the current configuration (*.dbc) file Edit properties for a selected library
D-12
Component Libraries group together multiple tables containing the same types of parts. For example, all capacitors could share a component library. The tables within a component library may be from the same or different relational databases. 1. Click Add Library to display the Add Library box. As an example, type Capacitors in the Library Name field (Figure D-12). Since the software associates the component library with the part partition, the library you specify must be the same as the Part partition in the central library. The library name is case-insensitive. Figure D-12. Add Library Dialog Box
2. In the Symbol Expression text input field, type a symbol expression to specify the legal symbols for the entire library, if your database does not have a field that contains the symbol name.
D-13
For example, if you have a capacitor library, and there is no symbol field in the database that shares the same generic symbol, you may set this field to any of the following values: cap.1, cap*, caph*, capv*. If there is a symbol field in your database, and it is specified as Symbol in the configuration file, leave this field empty. 3. (Optional) Click Advanced to specify how you want to link tables in the library. Tip: Steps 4 and 5 are used primarily for databases that do not have join capabilities. 4. Select one of the two options: Tables Joined Vertically - This option links tables vertically and accesses components that span multiple tables, but use the attributes in one table. Vertically linked tables provide a single search interface for similar components stored in multiple tables. Tables Joined Horizontally - This option links tables horizontally and accesses one component with attributes that span multiple tables. Horizontally linked tables join disparate information about the same set of components so you have access to all the information you need.
When you select the Tables Joined Horizontally option, the Choose Link Table button and the Join Type options are enabled. 5. Click Choose Link Table to select the table to which you want to link. For more information, see Adding a Table to a Library Configuration on page D-15. The database name is displayed and the table name to which you have linked underneath Choose Link Table. 6. Click OK; the Capacitors library is added to the list of Component Libraries (Figure D-13). Figure D-13. Library Added to Component Libraries List
Note Settings in the Symbol and Preferences tabs affect how components are placed on the schematic using the configuration file. The settings in these tabs are stored in the configuration file. For more information, consult online help.
D-14
Adding a Table to a Library Configuration

Use the Add Table command (available from the dialog box or right-click a table entry in the dialog box and click Insert Table from the popup menu) to add parametric tables to the selected library. A table refers to an actual database table that stores parametric data. For example, in Microsoft Access, data is organized in different tables. Similarly, a library can contain several tables. Use database joins to link together tables of disparate information. Use a DxDatabook or an Access query to link these tables together. 1. From the Libraries tab (under Component Libraries), highlight the library (for example, Capacitors) to which you want to add data. 2. Click Add Table (or Insert Table from the popup menu); the dialog box appears (Figure D-14). Figure D-14. Add Table Dialog Box
3. If no entries appear in the Data Source (DSN) dropdown box, click New to invoke the Data Source Manager dialog box. This allows you to select data sources from the list to populate the Data Source (DSN) dropdown box in the Add Table dialog box (Figure D-15).
D-15
Figure D-15. Data Source Manager Dialog Box (Spawned from Add Table)
4. Select an existing Data Source name, or select a data source type to create a new Data Source. Note that there are constraints based on the data source type you select (see Table D-1 on page D-2). The Data Source Manager provides tools to specify data source names using the following database types (see Table D-2 and Figure D-1 on page D-2): WWW (World Wide Web) - allows connection to data sources via DxWebPack. Oracle (see page D-19) - allows a direct connection to an Oracle database. ODBC (see page D-20) - allows connection to various database types using Windows ODBC.
D-16
Note For UNIX and Linux operating systems, the ODBC radio button on the Data Source Manager dialog box is not available. If you select WWW or Oracle, the dialog box provides fields to specify the database connection name (that will appear in the Data Source Names list), server connection identification, location, and access (login and password). If you select ODBC, the dialog box lists current database drivers that are loaded to your Windows machine.
Specifying a Web-based Data Source

Select the WWW (World Wide Web) radio button to configure the Data Source Manager dialog box to define web-based data sources to include in the list of data sources in the Add Table dialog box (Figure D-15 on page D-16). Use the following steps to specify a web-based data source in the dialog box (see Figure D-16): Figure D-16. Data Source Manager Dialog Box (WWW Option Enabled)
D-17
1. Ensure the WWW radio button is selected. 2. Enter the connection name (identification) in the text entry field. The name you enter in this field eventually appears in the Data Source (DSN) dropdown box within the New Table dialog box (Figure D-14). 3. Enter the URL path in the URL String text entry field. This identifies the location of the data source located on the web. 4. Enter the Database name in the field. 5. Click Apply. The text in the Connection Name field now appears in the Data Source Names field of the dialog box (Figure D-17). Figure D-17. Data Source Manager Dialog Box (WWW Data Source Enabled)
6. Click Add to create another web-based data source connection and repeat steps 1 - 6. Note When you click Add, you can select any of the data source type radio buttons (Oracle and ODBC) to create data source types and corresponding names. 7. To remove a Data Source Name from the Data Source Manager dialog box, highlight the entry in the dialog box and click Remove. 8. Click Apply to save changes at any time in the dialog box. 9. Click OK to save changes and dismiss the dialog box. The software saves the list of entries in the Data Source Names list box and returns you to the Add Table dialog box.
D-18
Note If you use the WWW option in the Data Source Manager dialog box to add a table that you can access over a Web server, the contents of the parametric data table appear. See Adding Tables to a Library Configuration Using WWW on page D-25 for more information.
Specifying an Oracle Data Source

Select the Oracle radio button to configure the Data Source Manager dialog box to define an Oracle-based data source to include in the list of data sources in the Add Table dialog box Use the following steps to specify a Oracle data source in the dialog box (Figure D-18). Figure D-18. Data Source Manager Dialog Box (Oracle Data Source Enabled)
1. Ensure the Oracle radio button is selected. 2. Enter the connection name (user-assigned identification) in the text entry field. The name you enter in this field eventually appears in the Data Source (DSN) dropdown box within the New Table dialog box. 3. Enter the Oracle service name (database instance name). 4. Enter your Oracle user name (Oracle database login). 5. Enter your Oracle database password.
D-19
6. Click Apply. The text in the Connection Name field now appears in the Data Source Names field of the dialog box (Figure D-19). Figure D-19. Data Source Manager Dialog Box (Oracle Data Source Defined)
7. Click Add to create another Oracle data source connection and repeat steps 1 - 6. Note When you click Add, you can select any of the data source type radio buttons (Oracle and ODBC) to create data source types and corresponding names. 8. To remove a Data Source Name from the Data Source Manager dialog box, highlight the entry in the dialog box and click Remove. 9. Click Apply to save changes at any time in the dialog box. 10. Click OK to save changes and dismiss the dialog box. The software saves the list of entries in the Data Source Names list box and returns you to the Add Table dialog box.
Specifying an ODBC Data Source

Note The ODBC radio button is enabled on Windows operating systems. It is not available on UNIX and Linux operating systems. Select the ODBC radio button to configure the Data Source Manager dialog box to define an ODBC-based data source to include in the list of data sources in the Add Table dialog box. Use the following steps to specify a ODBC-based data source in the dialog box (see Figure D-20).
D-20
Figure D-20. Data Source Manager Dialog Box (ODBC Data Source Enabled)
1. Ensure the ODBC radio button is selected. 2. Select a ODBC connection from the list of selections in the dialog box. The ODBC connection you highlight eventually appears in the Data Source (DSN) dropdown box within the New Table dialog box. 3. Click Apply. The text in the Connection Name field now appears in the Data Source Names field of the dialog box. 4. Click Add to select another ODBC data source connection and repeat steps 1 - 3. Note When you click Add, you can select any of the data source type radio buttons (Oracle and ODBC) to create data source types and corresponding names.
D-21
Figure D-21. Data Source Manager Dialog Box (ODBC Data Source Defined)
5. To remove a Data Source Name from the Data Source Manager dialog box, highlight the entry in the dialog box and click Remove. 6. Click Apply to save changes at any time in the dialog box. 7. Click OK to save changes and dismiss the dialog box. The software saves the list of entries in the Data Source Names list box and returns you to the Add Table dialog box.
Editing and Saving Data Source Names (Data Source Manager Dialog Box)
Controls on the Data Source Manager dialog box (Figure D-22) allow you to manage the list of eligible data source names. Use Remove to exclude a data source from the Data Source Names list box. Use Add to create new connections and include them in the Data Source Names list box.
D-22
Figure D-22. Editing Data Source Names (Data Source Manager Dialog Box)
Click OK to save the list of data source names and connections and return to the New Table dialog box (Figure D-23). The Data Source (DSN) dropdown field is now populated with the data source names specified in the Data Source Manager dialog box (Figure D-22). Click Cancel to dismiss the Data Source Manager dialog box without saving changes. Figure D-23. New Table Dialog Box with Data Source (DSN) Populated
D-23
Selecting a Data Source and Table Name

Note This section assumes you have valid data sources in the Add Table dialog box. 1. Select a data source from the Data Source (DSN) dropdown list. The software reads the data source and compiles a list of valid parametric table names to populate the Table name dropdown list (see Figure D-23). Note You can create a DSN by clicking New on this dialog (see Viewing Table Properties on page D-30 for more information). 2. In the Table Name box, select a table from the dropdown list, and then click OK. The Configure dialog box displays the detailed information about the selected library (Figure D-24). Figure D-24. Configure Dialog Box With Library Data Displayed
D-24
Tip: The order of libraries affects how libraries appear and how parts are mapped to libraries when loaded from DxDesigner, if no DXDB_LIBNAME attribute exists on the part. See Using Other Library Configuration Dialog Box Controls on page D-26 for more information on additional dialog box controls.
Adding Tables to a Library Configuration Using WWW

Note To use the following functionality, you must install and configure DxWebPack software on Windows. For more information on DxWebPack, consult online help associated with DxWebPack. Using the Add Table dialog box, click the Use the Data Source (DSN) dropdown list and select from the list of data sources and the table from the list tables in the Table Name dropdown list. Library Manager retrieves data from the selected data source and displays data in the parametric table in the workspace (read only mode) when you invoke the Edit Parametric Data popup menu command (see Editing Parametric Data on page D-37) on the table. Note Prerequisite: Install and configure DxWebPack Server on Windows and then use DxDatabook to view parametric data in table from a web-based (WWW) data source (see Specifying a Web-based Data Source on page D-17). Parametric data is read only when using DxWebPack Server on Windows. 1. From the Libraries tab (under Component Libraries), highlight the library (for example, DEVICE) to which you want to add data. 2. Click Add Table; the Add Table dialog box appears (Figure D-14 on page D-15). 3. Select the option on the Add table dialog box. 4. Enter the full URL address of the web server where you installed DxWebPack. In the following example, <machine_name> is the Windows machine where you configured the DxWebPack server.
http://<machine_name>/dxscripts/dxdbweb.dll
Once you add a valid URL address to the web server, the software populates the Data Source (DSN) dropdown list with the full list of data sources accessible from the machine where DxWebPack is loaded. 5. Select a Data Source from the dropdown list that contains the table you want to add. When selected, the software populates the Table Name dropdown list with the associated parametric tables.
D-25
6. In the Table Name box, select a table to add (displayed in the drop-down list) and click OK. The Configure dialog box displays with the associated table and the parametric data associated with the table appears in the viewer in read only mode.
Saving DxDatabook User Configuration

Click OK in the Configure dialog box to save settings in the user configuration (*.dbc) file. The software creates the .dbc file in the same location as the central library (*.lmc) file. The configuration file you save opens each time you use DxDatabook. To change the configuration or open a different configuration file, right-click anywhere in the DxDatabook window and select a command from the popup menu. For additional information on DxDatabook user configuration information, see Viewing Central Library Properties on page D-27.
Using Other Library Configuration Dialog Box Controls

Removing Libraries and Tables
Use the Remove command to remove table or library from the Libraries list. To delete a library from the current configuration: 1. Under Component Libraries, select the library you want to remove, and then click Remove. 2. At the prompt, click Yes. The highlighted entity is removed and the configuration automatically updates.
Reordering Libraries
Use the Set (Library) Order command to change the order of the libraries or tables within component libraries in the tree hierarchy. To reorder libraries: Tip: The order of libraries affects how libraries appear and how parts are mapped to libraries when loaded from DxDesigner, if no DXDB_LIBNAME attribute exists on the part. 1. From the Libraries tab, click Set Order. The Reorder Libraries dialog box displays with a list of all the libraries in the current configuration. The libraries are listed in the order they appear in the tree hierarchy.
D-26
Using DxDatabook Data Editor in Library Manager Viewing Central Library Properties
2. Under Libraries, select a library and click one of the commands in Table D-3: Table D-3. Library Configuration Dialog Box Controls Button Move Up Move Down Alpha Order Purpose Move the selected library up one level in the tree hierarchy. Move the selected library down one level in the tree hierarchy. Restore the order in which the libraries were originally arranged (before saving).
3. Click OK. The configuration automatically updates.
Editing Library or Table Properties

Use the Add Library or Add Table dialog boxes to view or edit a library or table. You can change a library or table name or link tables using advanced features within the Add Library dialog box. For more information on linking tables, consult online help. 1. Under Component Libraries, select the library or table you want to view or edit, and then click Properties. The Add Library or Add Table dialog box appears depending upon the entity you highlight. 2. From the Add Library or Add Table dialog box, make the appropriate changes, and then click OK. The configuration automatically updates based on the changes you made.

Use the Properties command, available from the popup menu when you right click on a valid central library in the Library Navigator Tree, to view the location, supported workflow, and symbol attributes for the active central library. You can edit the Symbol Attribute for PDB Part Number field to define which DxDesigner attribute is equivalent to an Expedition part number. The software uses this information in the DxDatabook Configuration to determine what column in the DxDatabook table is equivalent to the Expedition part number. 1. In the Library Navigator Tree, right click the central library (*.lmc) file name to display the popup menu (Figure D-25).
D-27
Using DxDatabook Data Editor in Library Manager Editing DxDatabook Properties
Figure D-25. Central Library Popup Menu
2. Click Properties; the Central Library Properties dialog box appears (Figure D-26). Figure D-26. Company Library Properties Dialog Box
Editing DxDatabook Properties

Use the DxDatabook Properties popup command to add or remove parametric tables from the database and edit table properties that exist in the database. This data is associated with the Part partition in the active central library. Tip: You cannot edit the table layout in the database using this dialog box. 1. Within the Library Navigator Tree, right click the Part partition in the central library to display the popup menu commands. 2. Select DxDatabook Properties from the popup menu (Figure D-27).
D-28
Figure D-27. DxDatabook Properties Popup Menu Command
The Properties dialog box displays with the Tables tab displayed by default and lists the parametric table names associated with the central library. If no parametric tables exist, click Add to associate a table using the proper Data Source Name (DSN) as illustrated in Figure D-28. Figure D-28. DxDatabook Properties (Table) Dialog Box
D-29
Viewing Table Properties

Use the Properties command to view and potentially modify the parametric table properties of the highlighted table. The software provides the means to select an ODBC data source and table name. The ODBC data source includes both machine data source (DSN) or user DSN. The tables correspond to the selected DSN. Use the Tables tab to select and associate tables to a DxDatabook library. 1. Click Properties; the parametric table properties appears in the Table tab (Figure D-29). Figure D-29. Parametric Table Properties Tab
2. Select a Data Source Name from the dropdown menu, which lists all the data source on your machine. Tip: Click New DSN to create a data source connecting DxDatabook to an ODBC database located on the computer or network. Use this option to connect to databases supported by DxDatabook (see Using Parametric Databases on Supported Platforms on page D-2). 3. Click OK to save changes, dismiss the dialog box, and return to the Properties dialog box (see Figure D-28 on page D-29).
Assigning Properties to New Tables

Select New in the Properties dialog box and the New Table Properties dialog box appears. Use the Table tab to view all the ODBC tables on your system by data source name. You can also use the New DSN command to create a new Data Source name.
D-30
1. Click Add in the Properties dialog box; the New Table Properties dialog box appears. 2. Select the Data Source Name from the list of available sources (Figure D-30). Figure D-30. New Table Properties Dialog Box
Note To create a new data source name (DSN), click New DSN to invoke the Select Data Source dialog box. For more information on the Select Data Source dialog box, click Help on the dialog box. 3. Select the parametric table from the list of available parametric tables in the Table Name dropdown to add to the library. The new table appears in the Table Name dropdown list (Figure D-31).
D-31
Figure D-31. New Table Properties Dialog Box with New Table Name
4. Click OK on the New Table Properties dialog box. The Properties dialog box updates with the new database table displayed (Figure D-32). Figure D-32. Properties Dialog Box with New Table Displayed
D-32
Removing Tables
To remove a table so you do not have to include it in a library, select the Tables tab in the dialog box, select a table and click Remove. The highlighted table is removed from the list.
Displaying Symbols
Use the Symbol Library tab to display symbols based on a filtered setting or the actual data values associated with symbols. From the Properties dialog box, click the Symbol Library tab. The dialog box appears (see Figure D-33 on page D-33): Figure D-33. Symbol Library Tab (Properties Dialog Box)
If you have symbol expression in your table (see Figure D-12 on page D-13), select the Valid Data Values in Symbol Field radio button and click OK. Otherwise, select the Symbol Filter radio button, enter a symbol expression to specify the legal symbols for the entire library, and click OK.
Configuring Database Table Layouts

From the Properties dialog box, use the Database Layout tab to link multiple tables in a library either horizontally (Figure D-34) or vertically (Figure D-35).
D-33
Figure D-34. Database Layout Tab - Tables Joined Vertically (Properties Dialog Box)
Figure D-35. Database Layout Tab - Tables Joined Horizontally (Properties Dialog Box
D-34
Using DxDatabook Data Editor in Library Manager Editing Database Tables
Tables Joined Vertically - Vertically linked tables provide a single search interface for similar components stored in multiple tables. For example, you may want to search on capacitors, but the tables could be segmented into polarized and non-polarized fields for maintenance reasons. See Figure D-34 for an example. Tables Joined Horizontally - Horizontally linked tables join disparate information about the same set of components. See Figure D-35 for an example. Data Source - Displays all file DSNs associated with the selected library. Table Name - Displays all parametric tables associated with the selected library. Join Types are as follows: Inner Join - Combines records from two tables to a query's results only if the values of the joined fields meet certain specified criteria. The values of the joined fields must be equal. Left Outer Join - Includes records even if there are no related records in the joined tables.
Advantages of Linking Tables Horizontally

Linking tables horizontally allows each department full read-write access to each other's databases (or tables within the database). For example, if manufacturing information (cost, leadtime) is in one database table, and engineering (value, tolerance) is in another database, you can horizontally link these databases. Horizontally linked tables also reduce the duplication of data within a table. For example, manufacturer information (name, address, Web page) can be in a separate manufacturer table, and linked together by the manufacturer name. Tip: Use the database's built-in table linking mechanisms for simplicity and efficiency. For example, queries in Microsoft Access or Views in Oracle provide more efficient linking mechanisms. For more information, refer to the documentation for the appropriate database.
Editing Database Tables

Use the Edit Database Tables popup command to edit parametric table properties and values within the DxDatabook database associated with the active central library. For example, use commands in the DxDatabook viewer to add, remove, or modify parametric table properties and values stored in the database. Invoke the command from the workspace tree as shown in Figure D-36:
D-35
Using DxDatabook Data Editor in Library Manager Editing Database Tables
Figure D-36. Accessing Edit Database Tables Command from the Popup Menu
The tables that appear in the Library Manager workspace depend on the number of tables you specified in the Properties dialog box (Figure D-37). Figure D-37. Viewing Parametric Table Entries in DxDatabook
D-36
Using DxDatabook Data Editor in Library Manager Editing Parametric Data
Use commands available in the DxDatabook environment to add parametric table entries (or rows), modify existing table entries (or rows), or delete rows from the table. When editing database tables, remember that you are modifying the schema of your database by changing parametric table properties. For more information, consult DxDatabook online help (Working With Database Properties section).
Editing Parametric Data

Use the Edit Parametric Data popup command to edit the parametric data present in the database. This command allows you to add, delete, and/or modify the contents of the parametric database table. For more information on editing parametric data, see the DxDatabook Users Guide. Caution If you delete data from the parametric table, the software does not prompt you to either complete the deletion operation or cancel. The Undo command does not recover the deleted data. 1. Select Edit Parametric Data from the Library Navigator Tree (Figure D-38). Tip: You can access this command from the Part partition associated with the active central library or from an individual part within the Part partition (as shown in Figure D-38). Figure D-38. Accessing Edit Parametric Data Command from the Popup Menu
The parametric data associated with the selected part displays in the viewer (Figure D-39). Note the toolbar which provides functionality to search, query, and edit parametric data in the table. You can also highlight parametric data and manually edit
D-37
the data via the mouse and keyboard. If you make an errant edit, use the Undo icon to quickly correct the last edit you made to data in the table. Figure D-39. Parametric Data Associated With a Part
2. To edit the data within the table, highlight the appropriate entity within the table and edit it as required. Use the tools in the toolbar as necessary to perform these edits. When you change the data within a row, use the Edit icon (Figure D-40) to quickly isolate the row where the edit occurred. Note If a parametric table is read only in the database, the table window banner indicates that the table is not editable. If you attempt to create a new Databook entry corresponding to a new part and receive a warning message (Part <xxx> not found; Unable to create new record - database is read-only), the database you are attempting to update is read only. Figure D-40. Editing Parametric Data in a Table
D-38
3. To save edits to the parametric data, exit the table in the workspace. The software saves all edits.
Performing Simple Searches (Search Command)

Use the Search icon in the toolbar to perform simple queries for entries in the table. For example, to find a specific value in the PKG_TYPE, click the Search icon, key in the alphanumeric text string in the Find dialog box, and click OK. The software highlights the matching alphanumeric text in the table. Click Find Next to find the next duplicate entry. The software informs you if no matching string is found.
Using the Query Window for More Exacting Searches

For more exacting data query, click the Toggle Query Window icon to display the query toolbar and operator fields (Figure D-41). This enables you to query by specific conditions and make global changes and query using more than one criteria. Tip: To hide the query commands and fields, click the Toggle Query Window icon. Example: 1. Click the Toggle Query Window icon to display the toolbar and operator fields. 2. Select the field you want the software to query. In the example in Figure D-41, select tolerance in the Field pulldown.
D-39
Figure D-41. Using the Toggle Query Window
3. Select the Operator (Op). Operators can be used with the data types in Table D-4. Table D-4. Operators and Corresponding Data Types Operator = > >= < <= != like Corresponding Data Type Numerical or String Numerical only Numerical only Numerical only Numerical only Numerical or String String only
Note See Using Numeric Comparison Operators for more information. 4. In the Value dropdown list, use one of the following methods to specify a value: Choose an existing value from the dropdown list.
D-40
Type a value to match. Typing a value allows you to use wildcards when attempting to return a list of matches. For example, entering R12* updates the results list with components that start with R12 and end with any alphanumeric characters.
5. Click Add to place the query in the list. 6. Repeat Steps 2 through 5 for any additional query criteria. 7. Click Run to execute the Query. The Results table updates to display items in the table that match your search criteria. The Toggle Query Window also contains commands to navigate through a parametric table, view its contents, copy selections from the table to a buffer (for example, a clipboard or to an ASCII data editor), and refresh the table display. For more information on using the Query Window, consult the DxDatabook Users Guide and online help.
Using Numeric Comparison Operators

To use the numeric comparison characters in a search condition, select a Field value from the list of available dropdown choices and then select one of the operators in Table D-5. Table D-5. Numeric Comparison Operators Operator = Function Represents a value equal to the specified numeric value. Represents values that are grater than the specified numeric value. Example =20 returns a list of the components for which numeric value of the specified attribute equals 20. >20 matches all numeric values of the specified attribute greater than 20.
>
<
Represents values that are less than <1.25 matches all numeric values the specified numeric value. of the specified attribute less than 1.25. Represents values that are greater than or equal to the specified numeric value. >=32 matches all numeric values of the specified attribute greater than or equal to 32.
>=
<=
Represents values that are less than <=0.05 matches ll numeric values or equal to the specified numeric of the specified attribute less than or value. equal to 0.05. Represents values not equal to the specified value. !=34 matches all numeric values of the specified attribute except those that equal 34.
!=
Searching for a range from a smaller to larger value requires creating two search queries -- one search query for an attribute value greater than a certain number, and a second query for the same attribute value less than a large number. For example, the following query matches all
D-41
values from 10 to 20 inclusive by creating a search condition for values greater than 10 and less than 20:
>10AND<20
Searching with a local NOT function for numeric ranges also requires two search queries. For example, the following query matches the values less than 3m OR greater than 16m:
<3mOR>16m
Using String Wildcards

DxDatabook uses the standard SQL percent (%) wildcard to match multiple string characters and the underscore (_) to match an individual character. DxDatabook also supports the asterisk (*) wildcard for matching multiple characters, and the question mark (?) wildcard for matching a single character. When you use the asterisk in a search query, DxDatabook converts it into the multiple wildcard character(%). Likewise, when you use a question mark (?), DxDatabook converts it into the individual wildcard character (_). Note To search for a component using wildcards, two conditions must be satisfied. First, the data in the database must be of type string. Second, you must use the like operator. Wildcard matching is not available for numerical data, which should be searched using mathematical comparisons of numeric values. When you select the like operator, use any of the following wildcard characters: Multiple Wildcard Characters - A percent sign (%), which represents any of zero or more characters. For example: string% - matches any value beginning with string. %string - matches any value ending with string. Individual Wildcard Character - An underscore (_), which represents any one character. For example: string_ - matches string followed by one character. _string - Matches any character followed by string. For more information, consult the DxDatabook Users Guide.
D-42
Appendix E Library Manager (DxD-Expedition Flow) Limitations

Overview
Before using Library Manager in the DxD-Expedition flow, read and understand the software limitations documented in this appendix. Library Manager includes the DxDesigner to Expedition PCB design flow. There are some limitations and working methodologies regarding the DxD-Expedition flow within Library Manager which are discussed in this section. Most limitations are related to the integration and interaction of DxDesigner's packaging/netlisting utility and the Part Editor's pin mapping definition and are specific to heterogeneous symbol support. Read this section and study Table E-1 on page E-2 which describes the Hetero symbol types supported in this release. Also, refer to the Release Notes documentation for information on specific problems and workarounds.
Heterogeneous Symbol Support

A heterogeneous device is defined as a physical package which is represented by at least two non-equivalent symbols on a DxDesigner schematic. The HETERO attribute indicates which DxDesigner symbols are part of a heterogeneous device. These symbols may differ in logic function, pin count, pin labels, attributes, and number of slots. The different symbols collectively correspond to a single physical device type for layout, and sometimes correspond to a single model for simulation. The combination of identical DEVICE attribute values and HETERO attribute values on each of the non-equivalent symbols is used to implement heterogeneous device support for the PCB interfaces. The value of the HETERO attribute binds the different symbols together. There are four types of heterogeneous devices: HETERO Type 1 Different components with the same device HETERO Type 2 Different gates within the same device (No HETERO attribute needed) HETERO Type 3 Split ICs HETERO Type 4 Different representations of the same device
E-1
Library Manager (DxD-Expedition Flow) Limitations Heterogeneous Symbol Support
Consult DxDesigner Schematic Design online help for more information.
DxDesigner-driven and Part-driven Generic and Nongeneric Hetero Devices Supported in the DxD-Expedition Flow
A Hetero device is DxDesigner-driven when the Hetero attribute definition exists (specified by the user) on the symbol/component. A Hetero device is part-driven if the Hetero attribute definition is not present on the symbol/component. Packager will instead use the pin mapping definition to compose a value for the HETERO attribute. In the DxDesigner-Expedition flow, generic symbols are symbols without built-in pin numbers and other device-related attributes while non-generic symbols are those containing built-in pin numbers and other attributes. The DxD-Expedition flow supports specific part-driven and DxDesigner-driven generic and non-generic Hetero type symbols/devices in DxDesigner. Table E-1 illustrates the heterogeneous symbol types supported in this release: Table E-1. Supported Hetero Type Symbols Part-driven Hetero Symbol Type Type 1 Type 2 Type 3 Generic Symbols Yes No Yes * (see Part-driven Heteros on page E-3) No Non-generic Symbols Yes No Yes * (see Partdriven Heteros on page E-3) No DxDesigner-driven Generic Symbols No No No Non-generic Symbols Yes Yes Yes ** (see Supporting DxD-Driven Nongeneric Hetero Type 3 Symbols on page E-3) Yes (see Supporting DxD-Driven Nongeneric Hetero Type 4 Symbols on page E-25)
Type 4
No
DxDesigner-driven Heteros
DxDesigner-driven (DxD-driven) Heteros are devices where the Hetero definition resides on the DxDesigner symbol/component. The symbol value of the HETERO attribute can be overridden at the component level. For these devices/symbols, schematic packaging (PCB Netlisting) in DxDesigner is driven by the symbol/component HETERO attribute value and overrides a possibly different hetero attribute that can be created from the part. All non-generic
E-2
Library Manager (DxD-Expedition Flow) Limitations Supporting DxD-Driven Non-generic Hetero Type 3 Symbols
(symbols must have built in PIN numbers) Hetero types are supported when driven from DxDesigner (user-specified HETERO definition on the symbol). ** See Supporting DxD-Driven Non-generic Hetero Type 3 Symbols on page E-3 on creating a Part definition for DxDesigner driven Hetero Type 3 devices. See Supporting DxD-Driven Non-generic Hetero Type 4 Symbols on page E-25 on creating part definitions for DxDesigner driven hetero Type 4 devices.
Part-driven Heteros
Part-driven heteros are devices where the HETERO attribute definition is not present on the DxDesigner symbol/component. The Hetero device is driven from the part definition. The HETERO attribute is not needed on the DxDesigner symbol since Packager will create and add a custom HETERO attribute value to the DxDesigner schematic component (based on the part definition of the device). Using this methodology, Hetero Type 1 is supported. * For Hetero Type 3 (Generic and Non-generic), the HETERO attribute created by Packager software does not contain parentheses and does not function for simulation flows where the netlisters depend on the HETERO attribute to determine the Hetero type. Therefore, for Hetero Type 3, the HETERO attribute value created by Packager must be manually edited to add these parentheses. Part-driven Hetero Types 2 and 4 are not supported in this release.
Supporting DxD-Driven Non-generic Hetero Type 3 Symbols

Note This modification is only required for DxD-Driven Non-generic Hetero Type 3 symbols. Part-Driven Generic and Non-generic symbols do not require this modification. To support Hetero Type 3 symbols (Split ICs) in the DxD-Expedition flow for this release, you must manually modify the part entry to create a master/layout symbol definition. Use an ASCII editor of your choice to complete this task. To illustrate the process, refer to the "HETERO_3" device with three fracture symbols (with pin numbers visible for use in this process guide): IC_OK_1 (illustrated in Figure E-1 on page E-4) IC_OK_2 (illustrated in Figure E-2 on page E-4) IC_OK_3 (illustrated in Figure E-3 on page E-5)
E-3
All three fracture symbols are located in symbol partition "Hetero". Note that you do not have to create the master/layout symbol. Figure E-1. IC_OK_1 Symbol
Figure E-2. IC_OK_2 Symbol
E-4
Figure E-3. IC_OK_3 Symbol
In Modify the Part Entry in an ASCII Editor on page E-6, you will find an ASCII representation of the part entry before the master symbol is added and an updated ASCII representation that includes the master symbol in the pin mapping. Note that the new master symbol entry will use the existing gate definitions from the fracture symbols. Therefore, this is basically a cut-and-paste procedure using the following steps: 1. Export the Part Entry (or Entries) to ASCII on page E-5 2. Modify the Part Entry in an ASCII Editor on page E-6 3. Importing the Modified Part Entry on page E-23
Export the Part Entry (or Entries) to ASCII

Export the existing Part entry for the HETERO_3 device using the following steps: 1. Invoke the Part Editor from the Library Manager interface. 2. Select the HETERO_3 device and select File > Export ASCII from the Part Editor interface:
E-5
Figure E-4. Selecting Export ASCII Command in Part Editor
The Export ASCII dialog box displays. 3. Enter an output ASCII file name with a .txt or .hkp extension and select the Selected Parts Only or All Parts in Partition option depending upon on the number and organization of your hetero-3 devices. In this example, the Selected Parts Only is selected since only one entry is being exported/ Figure E-5. Export ASCII Dialog Box
Modify the Part Entry in an ASCII Editor

Open the output file in an ASCII editor and observe the structure of the Part entry before editing. You must be familiar with the format because you must edit it.
E-6
The following example describes the following major sections. Header section SwapGroup section Symbol section Slots section
Information in these sections correlate with each other. Specifically, the Symbol Pin Name is mapped to the Component/Device Pin Number via the SwapID contained in the SwapGroup section. This mapping is performed positionally within each section. See the example gold-highlighted SwapID "P0" and the corresponding entries in the Symbol and Slot sections (in this case, SwapID "P0" maps input pin "I0" to Pin Number 41). See Swap group for gate on page E-9, Symbol Mapping Section on page E-13, and Slot Definition Section on page E-14 for examples. To better illustrate how the data relates, portions within each section are enclosed in colorcoded rectangles to show the data that applies to each symbol of this Split IC device. Blue boxes represent symbol ic_ok_1 Red/maroon boxes represent symbol ic_ok_2 Green boxes represent symbol ic_ok_3 Purple (magenta) boxes illustrate the implicit Supply and No-Connect data that is stored in and processed from the part.
HETER0_3 - Part ASCII Representation (BEFORE EDITING)

File Header Information
File header information showing the File type, File version, Units (either th, in, mm or um) and Notation (either Engineering, European, Scientific, Si, Spice, None, or Regional).
Filetype ASCII_PDB .Version "02.00" .Units th .Notation Si
E-7
Definition Section (Part Number, Name, Label, RefDes Prefix, and PKG_TYPE)
Definition section containing Part Number, Name and Label information. Number refers to Part Number = HETERO_3; Name refers to Part Name = HETERO_3; Label refers to Part Label = FPGA. The Definition section contains the Reference Designator Prefix and the TopCell (PKG_TYPE).
.Number "HETERO_3" ..Name "HETERO_3" ...Default ..Label "FPGA" ...Default ..Desc "" ..RefPrefix "U" ..TopCell "52PLCC" ..BottomCell "" ..Modified1078852829 ! 3/9/04 11:20 AM ..Prop "Type", "", "Text"
The following lists SwapGroup Name and Definition containing the SwapIDs and properties. These are used to represent the logic pins on the symbols as well as the Supply (SIGNAL) and No-Connect (NC) pins. Note that there can be multiple SwapGroup definitions. This example entry has three SwapGroups: gate (page E-9), gate_1 (page E-10), and gate_2 (page E-11), corresponding to fracture symbols ic_ok_1, ic_ok_2 and ic_ok_3 respectively. SwapGroup definitions for the Supply and NC pins follow on page E-12.
E-8
Swap group for gate

..SwapGroup "gate" ...SwapID "P0" ...SwapID "P0" ...SwapID "P1" ...SwapID "P2" ...SwapID "P0" ...SwapID "P0" ...SwapID "P0" ...SwapID "P0" ...SwapID "P3" ...SwapID "P4" ...SwapID "P5" ...SwapID "P6" ...SwapID "P7" ...SwapID "P8" ...SwapID "P9" ...SwapID "P10" ...SwapID "P11" ...SwapIDProperties "P0" ....Prop "Pin Type", "Input", ...SwapIDProperties "P1" ....Prop "Pin Type", "Input", ...SwapIDProperties "P2" ....Prop "Pin Type", "Input", ...SwapIDProperties "P3" ....Prop "Pin Type", "Input", ...SwapIDProperties "P4" ....Prop "Pin Type", "Input", ...SwapIDProperties "P5" ....Prop "Pin Type", "Input", ...SwapIDProperties "P6" ....Prop "Pin Type", "Input", ...SwapIDProperties "P7" ....Prop "Pin Type", "Bidir", ...SwapIDProperties "P8" ....Prop "Pin Type", "Bidir", ...SwapIDProperties "P9" ....Prop "Pin Type", "Bidir", ...SwapIDProperties "P10" ....Prop "Pin Type", "Bidir", ...SwapIDProperties "P11" ....Prop "Pin Type", "Output",
"Text" "Text" "Text" "Text" "Text" "Text" "Text" "Text" "Text" "Text" Text" "Text"
Note: The blue box represents symbol ic_ok_1.
E-9
Swap group for gate_1

..SwapGroup" gate_1" ...SwapID "P0" ...SwapID "P1" ...SwapID "P2" ...SwapID" P3" ...SwapID "P4" ...SwapID "P5" ...SwapID "P6" ...SwapID "P6" ...SwapID "P6" ...SwapID "P6" ...SwapID " P6" ...SwapID "P6" ...SwapID "P7" ...SwapID "P8" ...SwapIDProperties "P0" ....Prop "Pin Type", "Input", "Text" ...SwapIDProperties "P1" ....Prop "Pin Type", "Input", "Text" ...SwapIDProperties "P2" ....Prop "Pin Type", "Input", "Text" ...SwapIDProperties "P3" ....Prop "Pin Type","Input", "Text" ...SwapIDProperties "P4" ....Prop "Pin Type","Input", "Text" ...SwapIDProperties "P5" ....Prop "Pin Type","Input", "Text" ...SwapIDProperties "P6" ....Prop "Pin Type","Output", "Text" ...SwapIDProperties "P7" ....Prop "Pin Type","Output", "Text" ...SwapIDProperties "P8" ....Prop "Pin Type","Output", "Text"
The red/maroon box represents symbol ic_ok_2.
E-10
SwapGroup for gate_2

..SwapGroup "gate_2" ...SwapID "P0" ...SwapID "P1" ...SwapID "P2" ...SwapID "P3" ...SwapID "P4" ...SwapID "P5" ...SwapID "P6" ...SwapID "P7" ...SwapID "P8" ...SwapID "P9" ...SwapID "P10" ...SwapID "P10" ...SwapID "P10" ...SwapID "P10" ...SwapID "P10" ...SwapID "P10" ...SwapIDProperties "P0" ....Prop "Pin Type", "Bidir", "Text" ...SwapIDProperties "P1" ....Prop "Pin Type", "Bidir", "Text" ...SwapIDProperties "P2" ....Prop "Pin Type", "Bidir", "Text" ...SwapIDProperties "P3" ....Prop "Pin Type", "Bidir", "Text" ...SwapIDProperties "P4" ....Prop "Pin Type", "Input", "Text" ...SwapIDProperties "P5" ....Prop "Pin Type", "Input", "Text" ...SwapIDProperties "P6" ....Prop "Pin Type", "Input", "Text" ...SwapIDProperties "P7" ....Prop "Pin Type", "Input", "Text" ...SwapIDProperties "P8" ....Prop "Pin Type", "Input", "Text" ...SwapIDProperties "P9" ....Prop "Pin Type", "Input", "Text" ...SwapIDProperties "P10" ....Prop "Pin Type", "Output", "Text"
The green box represents symbol ic_ok_3.
E-11
SwapGroup Definitions for Supply and NC Pins

..SwapGroup "VDD" ...SwapID "P1" ...SwapIDProperties "P1" ....Prop "Supply", "VDD", "Text" ..SwapGroup "VDD_1" ...SwapID "P1" ...SwapIDProperties "P1" ....Prop "Supply", "VDD", "Text" ..SwapGroup "GND" ...SwapID "P1" ...SwapIDProperties "P1" ....Prop "Supply", "GND", "Text" ..SwapGroup "GND_1" ...SwapID "P1" ...SwapIDProperties "P1" ....Prop "Supply", "GND", "Text" ..SwapGroup "No Connect" ...SwapID "P1" ...SwapIDProperties "P1" ....Prop "Pin Type", "No Connect",
"Text"
The purple (magenta) box illustrates the implicit Supply and No-Connect data that is stored in and processed from the Part.
E-12
Symbol Mapping Section

The Symbol Mapping section contains Symbol_SwapGroup definitions that positionally map Pin Names (LABELS) on the symbols to the SwapGroup SwapIDs and the Slot (Pin Number) information. Note There is no mapping of the Supply/NC pins in this section because they do not appear explicitly on the symbols.
..Symbol "Hetero:ok_ic_1" ...Symbol_SwapGroup "gate" ....PinName "IN0" ....PinName "IN1" ....PinName "IN10" ....PinName "IN11" ....PinName "IN2" ....PinName "IN3" ....PinName "IN4" ....PinName "IN5" ....PinName "IN6" ....PinName "IN7" ....PinName "IN8" ....PinName "IN9" ....PinName "~B0" ....PinName "~B1" ....PinName "~B2" ....PinName "~B3" ....PinName "~O7" ..Symbol "Hetero:ok_ic_2" ...Symbol_SwapGroup "gate_1" ....PinName "IN15" ....PinName "IN16" ....PinName "IN17" ....PinName "IN21" ....PinName "IN22" ....PinName "IN23" ....PinName "X0" ....PinName "X1" ....PinName "X2" ....PinName "X3" ....PinName "X4" ....PinName "X5" ....PinName "X6" ....PinName "X7"
E-13
Library Manager (DxD-Expedition Flow) Limitations Supporting DxD-Driven Non-generic Hetero Type 3 Symbols ..Symbol "Hetero:ok_ic_3" ...Symbol_SwapGroup "gate_2" ....PinName "B4" ....PinName "B5" ....PinName "B6" ....PinName "B7" ....PinName "IN12" ....PinName "IN13" ....PinName "IN14" ....PinName "IN18" ....PinName "IN19" ....PinName "IN20" ....PinName "O0" ....PinName "O1" ....PinName "O2" ....PinName "O3" ....PinName "O4" ....PinName "O5"
Slot Definition Section

The Slot Definition Section contains Slot_SwapGroup definitions which positionally map component Pin Numbers to both the Symbol_SwapGroup Pin Names and SwapGroup SwapIDs (shown previously).
..Slots ...Slot_SwapGroup "gate" ....PinNumber "41" ....PinNumber "42" ....PinNumber "52" ....PinNumber "1" ....PinNumber "43" ....PinNumber "44" ....PinNumber "45" ....PinNumber "47" ....PinNumber "48" ....PinNumber "49" ....PinNumber "50" ....PinNumber "51" ....PinNumber "37" ....PinNumber "38" ....PinNumber "39" ....PinNumber "40" ....PinNumber "27"
E-14
Library Manager (DxD-Expedition Flow) Limitations Supporting DxD-Driven Non-generic Hetero Type 3 Symbols ...Slot_SwapGroup "gate_1" ....PinNumber "5" ....PinNumber "6" ....PinNumber "7" ....PinNumber "12" ....PinNumber "13" ....PinNumber "14" ....PinNumber "28" ....PinNumber "29" ....PinNumber "30" ....PinNumber "31" ....PinNumber "32" ....PinNumber "33" ....PinNumber "35" ....PinNumber "36" ...Slot_SwapGroup "gate_2" ....PinNumber "15" ....PinNumber "16" ....PinNumber "17" ....PinNumber "18" ....PinNumber "2" ....PinNumber "3" ....PinNumber "4" ....PinNumber "9" ....PinNumber "10" ....PinNumber "11" ....PinNumber "19" ....PinNumber "21" ....PinNumber "22" ....PinNumber "23" ....PinNumber "24" ....PinNumber" 25"
Slot SwapGroup Definitions for Supply and NC Pins

Slot_SwapGroup definitions for the Supply and NC pins are as follows:
...Slot_SwapGroup "VDD" ....PinNumber "8" ...Slot_SwapGroup "VDD_1" ....PinNumber "46" ...Slot_SwapGroup "GND" ....PinNumber "20" ...Slot_SwapGroup "GND_1" ....PinNumber "34" ...Slot_SwapGroup "No Connect" ....PinNumber "26"
Specify the new symbol name entry in the Symbol section of the Part entry. Note that the symbol name must match the Part Number (for example, "Hetero_3"). Therefore, the new entry should appear as ..Symbol "Hetero_3".
E-15
You can insert this new entry after the last fractures symbol definition. Once you enter that line, copy and paste the existing Symbol_SwapGroup definitions of each of the fracture symbols (three in this example). See the text enclosed in a box in the ASCII dump of the Part after making the required modifications (next section in this chapter). Make sure to accurately copy and paste the Symbol_SwapGroup definitions so that the SwapGroup definition for the master symbol is complete.
HETER0_3 - Part ASCII Representation (AFTER EDITING)

The ASCII version of the same HETERO_3 entry is now modified to show the addition of the master/layout Symbol definition. Remember that the name of the master/layout symbol must match the Part Number (DEVICE) attribute. The modified symbol definition is indicated in Modified Symbol Definitions (HETERO_3) on page E-20.
.Filetype ASCII_PDB .Version "02.00" .Units th .Notation Si .Number "HETERO_3" ..Name "HETERO_3" ...Default ..Label "FPGA" ...Default ..Desc "" ..RefPrefix "U" ..TopCell "52PLCC" ..BottomCell "" ..Modified 1078852829 ! 3/9/04 11:20 AM ..Prop "Type", "", "Text" ..SwapGroup "gate" ...SwapID "P0" ...SwapID "P0" ...SwapID "P1" ...SwapID "P2" ...SwapID "P0" ...SwapID "P0" ...SwapID "P0" ...SwapID "P0" ...SwapID "P3" ...SwapID "P4" ...SwapID "P5" ...SwapID "P6" ...SwapID "P7" ...SwapID "P8" ...SwapID "P9" ...SwapID "P10" ...SwapID "P11" ...SwapIDProperties "P0" ....Prop "Pin Type", "Input", "Text" ...SwapIDProperties "P1" ....Prop "Pin Type", "Input", "Text" ...SwapIDProperties "P2" ....Prop "Pin Type", "Input", "Text"
E-16
Library Manager (DxD-Expedition Flow) Limitations Supporting DxD-Driven Non-generic Hetero Type 3 Symbols ...SwapIDProperties "P3" ....Prop "Pin Type", "Input", "Text" ...SwapIDProperties "P4" ....Prop "Pin Type", "Input", "Text" ...SwapIDProperties "P5" ....Prop "Pin Type", "Input", "Text" ...SwapIDProperties "P6" ....Prop "Pin Type", "Input", "Text" ...SwapIDProperties "P7" ....Prop "Pin Type", "Bidir", "Text" ...SwapIDProperties "P8" ....Prop "Pin Type", "Bidir", "Text" ...SwapIDProperties "P9" ....Prop "Pin Type", "Bidir", "Text" ...SwapIDProperties "P10" ....Prop "Pin Type", "Bidir", "Text" ...SwapIDProperties "P11" ....Prop "Pin Type", "Output", "Text" ..SwapGroup "gate_1" ...SwapID "P0" ...SwapID "P1" ...SwapID "P2" ...SwapID "P3" ...SwapID "P4" ...SwapID "P5" ...SwapID "P6" ...SwapID "P6" ...SwapID "P6" ...SwapID "P6" ...SwapID "P6" ...SwapID "P6" ...SwapID "P7" ...SwapID "P8" ...SwapIDProperties "P0" ....Prop "Pin Type", "Input", "Text" ...SwapIDProperties "P1" ....Prop "Pin Type", "Input", "Text" ...SwapIDProperties "P2" ....Prop "Pin Type", "Input", "Text" ...SwapIDProperties "P3" ....Prop "Pin Type", "Input", "Text" ...SwapIDProperties "P4" ....Prop "Pin Type", "Input", "Text" ...SwapIDProperties "P5" ....Prop "Pin Type", "Input", "Text" ...SwapIDProperties "P6" ....Prop "Pin Type", "Output", "Text" ...SwapIDProperties "P7" ....Prop "Pin Type", "Output", "Text" ...SwapIDProperties "P8" ....Prop "Pin Type", "Output", "Text" ..SwapGroup "gate_2" ...SwapID "P0" ...SwapID "P1" ...SwapID "P2" ...SwapID "P3" ...SwapID "P4" ...SwapID "P5"
E-17
Library Manager (DxD-Expedition Flow) Limitations Supporting DxD-Driven Non-generic Hetero Type 3 Symbols ...SwapID ...SwapID ...SwapID ...SwapID ...SwapID ...SwapID ...SwapID ...SwapID ...SwapID ...SwapID "P6" "P7" "P8" "P9" "P10" "P10" "P10" "P10" "P10" "P10"
...SwapIDProperties "P0" ....Prop "Pin Type", "Bidir", "Text" ...SwapIDProperties "P1" ....Prop "Pin Type", "Bidir", "Text" ...SwapIDProperties "P2" ....Prop "Pin Type", "Bidir", "Text" ...SwapIDProperties "P3" ....Prop "Pin Type", "Bidir", "Text" ...SwapIDProperties "P4" ....Prop "Pin Type", "Input", "Text" ...SwapIDProperties "P5" ....Prop "Pin Type", "Input", "Text" ...SwapIDProperties "P6" ....Prop "Pin Type", "Input", "Text" ...SwapIDProperties "P7" ....Prop "Pin Type", "Input", "Text" ...SwapIDProperties "P8" ....Prop "Pin Type", "Input", "Text" ...SwapIDProperties "P9" ....Prop "Pin Type", "Input", "Text" ...SwapIDProperties "P10" ....Prop "Pin Type", "Output", "Text" ..SwapGroup "VDD" ...SwapID "P1" ...SwapIDProperties "P1" ....Prop "Supply", "VDD", "Text" ..SwapGroup "VDD_1" ...SwapID "P1" ...SwapIDProperties "P1" ....Prop "Supply", "VDD", "Text" ..SwapGroup "GND" ...SwapID "P1" ...SwapIDProperties "P1" ....Prop "Supply", "GND", "Text" ..SwapGroup "GND_1" ...SwapID "P1" ...SwapIDProperties "P1" ....Prop "Supply", "GND", "Text" ..SwapGroup "No Connect" ...SwapID "P1" ...SwapIDProperties "P1" ....Prop "Pin Type", "No Connect", "Text"
Note: This ok_ic_1 symbol_swapgroup definition (not including the ..Symbol Hetero:ok_ic_1 line) should be copied into the new master/layout symbol entry in Modified Symbol Definitions (HETERO_3) on page E-20.
E-18
..Symbol "Hetero:ok_ic_1" ...Symbol_SwapGroup "gate" ....PinName "IN0" ....PinName "IN1" ....PinName "IN10" ....PinName "IN11" ....PinName "IN2" ....PinName "IN3" ....PinName "IN4" ....PinName "IN5" ....PinName "IN6" ....PinName "IN7" ....PinName "IN8" ....PinName "IN9" ....PinName "~B0" ....PinName "~B1" ....PinName "~B2" ....PinName "~B3" ....PinName "~O7"
Note: This ok_ic_2 symbol_swapgroup definition (not including the ..Symbol Hetero:ok_ic_2 line) should be copied into the new master/layout symbol entry on Modified Symbol Definitions (HETERO_3) on page E-20.
..Symbol "Hetero:ok_ic_2" ...Symbol_SwapGroup "gate_1" ....PinName "IN15" ....PinName "IN16" ....PinName "IN17" ....PinName "IN21" ....PinName "IN22" ....PinName "IN23" ....PinName "X0" ....PinName "X1" ....PinName "X2" ....PinName "X3" ....PinName "X4" ....PinName "X5" ....PinName "X6" ....PinName "X7"
E-19
Note: This ok_ic_3 symbol_swapgroup definition (not including the ..Symbol Hetero:ok_ic_3 line) should be copied into the new master/layout symbol entry (see Modified Symbol Definitions (HETERO_3).
..Symbol "Hetero:ok_ic_3" ...Symbol_SwapGroup "gate_2" ....PinName "B4" ....PinName "B5" ....PinName "B6" ....PinName "B7" ....PinName "IN12" ....PinName "IN13" ....PinName "IN14" ....PinName "IN18" ....PinName "IN19" ....PinName "IN20" ....PinName "O0" ....PinName "O1" ....PinName "O2" ....PinName "O3" ....PinName "O4" ....PinName "O5"
Modified Symbol Definitions (HETERO_3)

The following page shows the Symbol entry for the master/layout symbol. It is named "HETERO_3" to match the Part Number/Device attribute. Notice that the definition consists of the Symbol_SwapGroup definitions used for the three fracture symbols (shown on the next page): Hetero: ic_ok_1 Hetero: ic_ok_2 Hetero: ic_ok_3
E-20
Library Manager (DxD-Expedition Flow) Limitations Supporting DxD-Driven Non-generic Hetero Type 3 Symbols ..Symbol "Hetero_3" ...Symbol_SwapGroup "gate" ....PinName "IN0" ....PinName "IN1" ....PinName "IN10" ....PinName "IN11" ....PinName "IN2" ....PinName "IN3" ....PinName "IN4" ....PinName "IN5" ....PinName "IN6" ....PinName "IN7" ....PinName "IN8" ....PinName "IN9" ....PinName "~B0" ....PinName "~B1" ....PinName "~B2" ....PinName "~B3" ....PinName "~O7" ...Symbol_SwapGroup "gate_1" ....PinName "IN15" ....PinName "IN16" ....PinName "IN17" ....PinName "IN21" ....PinName "IN22" ....PinName "IN23" ....PinName "X0" ....PinName "X1" ....PinName "X2" ....PinName "X3" ....PinName "X4" ....PinName "X5" ....PinName "X6" ....PinName "X7" ...Symbol_SwapGroup "gate_2" ....PinName "B4" ....PinName "B5" ....PinName "B6" ....PinName "B7" ....PinName "IN12" ....PinName "IN13" ....PinName "IN14" ....PinName "IN18" ....PinName "IN19" ....PinName "IN20" ....PinName "O0" ....PinName "O1" ....PinName "O2" ....PinName "O3" ....PinName "O4" ....PinName "O5"
E-21
Library Manager (DxD-Expedition Flow) Limitations Supporting DxD-Driven Non-generic Hetero Type 3 Symbols ..Slots ...Slot_SwapGroup "gate" ....PinNumber "41" ....PinNumber "42" ....PinNumber "52" ....PinNumber "1" ....PinNumber "43" ....PinNumber "44" ....PinNumber "45" ....PinNumber "47" ....PinNumber "48" ....PinNumber "49" ....PinNumber "50" ....PinNumber "51" ....PinNumber "37" ....PinNumber "38" ....PinNumber "39" ....PinNumber "40" ....PinNumber "27" ...Slot_SwapGroup "gate_1" ....PinNumber "5" ....PinNumber "6" ....PinNumber "7" ....PinNumber "12" ....PinNumber "13" ....PinNumber "14" ....PinNumber "28" ....PinNumber "29" ....PinNumber "30" ....PinNumber "31" ....PinNumber "32" ....PinNumber "33" ....PinNumber "35" ....PinNumber "36" ...Slot_SwapGroup "gate_2" ....PinNumber "15" ....PinNumber "16" ....PinNumber "17" ....PinNumber "18" ....PinNumber "2" ....PinNumber "3" ....PinNumber "4" ....PinNumber "9" ....PinNumber "10" ....PinNumber "11" ....PinNumber "19" ....PinNumber "21" ....PinNumber "22" ....PinNumber "23" ....PinNumber "24" ....PinNumber "25"
E-22
Library Manager (DxD-Expedition Flow) Limitations Supporting DxD-Driven Non-generic Hetero Type 3 Symbols ...Slot_SwapGroup "VDD" ....PinNumber "8" ...Slot_SwapGroup "VDD_1" ....PinNumber "46" ...Slot_SwapGroup "GND" ....PinNumber "20" ...Slot_SwapGroup "GND_1" ....PinNumber "34" ...Slot_SwapGroup "No Connect" ....PinNumber "26"
When you complete the definition for the master Symbol, save the updated ASCII file. Save it as a different file name (if desired) so as not to overwrite the original exported version. In this example, the modified ASCII filename is Hetero_modified.txt.
Importing the Modified Part Entry

To finish the process, use the Part Editor (File > Import ASCII command) to import the modified ASCII Part entry back into the part data. 1. Before importing the modified entry, go to the Part Editor and rename the original HETERO_3 Part Number so that it is not overwritten when you import the modified file. In the following figure, the part was copied using the Copy command and the part was renamed to "HETERO_3_save" (Figure E-6). Figure E-6. Part Editor Copy Command
2. Click File > Import ASCII; the Import ASCII dialog box displays. 3. Browse to the modified ASCII text file and choose the Import options as desired (Figure E-7).
E-23
Figure E-7. Import ASCII Dialog Box (Part Editor)
4. Click OK; the software displays a message box informing you that the process was successful. If errors occur, open the file in an ASCII editor, troubleshoot the problem, save your changes, and reimport. 5. In the Part Editor dialog box, select the Hetero_3 entry, click Pin Mapping, and view the Symbol section to ensure the new master/layout Symbol appears (Figure E-8). Figure E-8. Hetero_3 Entry in Part Editor (After ASCII Import)
6. Review the pin mapping for the Hetero_3 symbol to make sure it is complete and accurate, then save and exit the Part Editor. The Part entry for the Hetero_3 device is now updated and is ready for the Create PCB Netlist operation.
E-24
Supporting DxD-Driven Non-generic Hetero Type 4 Symbols

This section discusses the support of DxD-driven non-generic hetero Type 4 symbols in this release of Library Manager. See Supported Hetero Type Symbols on page E-2 for more information. The methods used to define resistor packages has an impact on the functionality available in many downstream tools (such as Constraint Editing System software). This section describes a process for defining a resistor package that supports: Place either 2 pin or 8 pin schematic symbols in any combination Swap pins from one side of the resistor to the other Swap resistors within package Swap resistors across packages Enable recognition as series device in CES
Using DxD Symbols (Non-generic Hetero Type 4)

Heterogeneous symbols provide the ability to assign different symbols to the same package. In the following examples, a hetero Type 4 (different representations of the same device) is used to indicate that the two-pin gate information is available in layout, which enables gate swapping (see Figure E-9 and Figure E-10). Figure E-9. DxDesigner Symbol for Full Resistor Package
E-25
Figure E-10. DxDesigner Symbol for Gated Resistor Package
Central Library Parts Database

Pin and symbol group swapping is defined in the Central Library Parts Database. Select Tools > Part Editor to invoke the Part Editor from the DxDesigner - Expedition Library Manager interface. The Part Editor displays (Figure E-11 on page E-27).
E-26
Figure E-11. Parts Database Editor Interface
When you select a part from the list and click Pin Mapping, the Pin Mapping dialog box displays (see Figure E-12 and Figure E-13):
E-27
Figure E-12. Pin Mapping Dialog Box With Swap Definitions for 2 Pin Symbol
Figure E-13. Pin Mapping Dialog Box With Swap Definitions for 8 Pin Symbol
E-28
DxDesigner Schematic
Either the 2 pin or 8 pin symbol can be used on the schematic. The 2 pin symbols will be packaged together into the same physical package, as indicated by the identical reference designator (see Figure E-14.) Figure E-14. DxDesigner Schematic Instances
Constraint Editor System

Once the resistor gate information is defined, use the series device heuristics in the Constraint Editor System (CES) to identify the physical nets on either side of the resistor as part of the same electrical net (see Figure E-15). Figure E-15. Electrical Nets in CES
E-29
Constraints can be defined for the entire electrical net, and constraint templates can be applied to define delay formulas across physical nets.
Expedition PCB Pin Swapping

Once the design is forward annotated into Expedition PCB, several swap functions are now possible. Note CES must be closed for Swap commands to be enabled. After the Swap commands are completed, the next invocation of CES will load the swaps and update pin pair references accordingly in the design.
Pin Swapping
To swap pins from one side of the resistor to the other, click the Pin Swap icon click the pins to swap. See Figure E-16 for an example: Figure E-16. Pin Swapping in Expedition and then
Gate Swapping
To swap a resistor within a package, click the Gate Swap icon See Figure E-17 for an example. then click the pins to swap.
E-30
Figure E-17. Gate Swapping in Expedition
Symbol Group Swapping

To swap a resistor from one package to another package, you must first display the Gate Swap dialog box by pressing the F2 function key after clicking the Gate Swap icon . Selecting the "Symbol Gate Group" for the swap mode will highlight all swappable pins, including those in other packages of the same device (see Figure E-18). Figure E-18. Symbol Group Swapping in Expedition
E-31
Library Manager (DxD-Expedition Flow) Limitations Swappable Sub-Gates / PinSets
Automatic Swapping
In addition to the interactive swapping commands, automatic swapping functionality is available. Select Place > Automatic > Swap by Part Number; the Automatic Swap dialog box displays. Select the type of swap and click Apply (see Figure E-19). Figure E-19. Automatic Group/Gate/Pin Swapping in Expedition
Swappable Sub-Gates / PinSets

In the DxD-Expedition flow, mismatches can exist between pin definitions on DxD symbols and the part which generate errors during Packaging. Make sure the pin definitions in DxD symbols are represented in the Part data. This provides Packager enough information to know the context of the swappable subgates.
E-32
Library Manager (DxD-Expedition Flow) Limitations Pin Swap Verification
Swappable pin sets (in a part/symbol) are defined in Parts data by defining swappable sub-gates. In a symbol with multiple sub-gates, the software matches DxD symbol PINs against all pins in all sub-gates. These sub-gates are implicitly swappable and so the PINs assigned to these slots are defined as swappable sets in DxDesigner. The software must read all symbol swap group definitions, the pin names must be matched with a DxD symbol and the pin numbers must be assigned accordingly. Also, the Parts data slot processor requires modification to process all the symbol swap groups defined for a part in a Part data. The software must validate of pin names and numbers for all slots.
Pin Swap Verification

Pin swap verification allows the software to validate the pin swap attribute against the actual pin and pin set swap definitions of the Part data. In this release, pin swap verification is limited to non-gated, single-representation parts.
Part Writer (Hetero Type 2 and/or 4)

The DxD-Expedition flow creates a local part for non-matching parts (to a Central Library) on a design. This is limited to non-gate, single-representation parts in this release.
Unsupported DxD-Expedition Library Manager Flow Scenarios

The following are unsupported scenarios in the DxD-Expedition flow within Library Manager: Generic symbols and multiple swap groups (and/or symbol swap groups) Generic symbols with multiple representations
E-33
Library Manager (DxD-Expedition Flow) Limitations Unsupported DxD-Expedition Library Manager Flow Scenarios
E-34
Appendix F Using DxDesigner for Symbols and Netlist Generation

Overview
Note This appendix applies only if you are using Library Manager in the DxD-Expedition flow. You can use DxDesigner to create symbols and import them into the appropriate Symbols partition in a central library. If you have DxDesigner software loaded on your machine, create the symbol in DxDesigner and then use Library Manager to import the symbol into the appropriate Symbol partition. Note that the Dx Symbol Editor, delivered with Library Manager and available from the user interface, can also be used to create a symbol in a specific partition in the central library supporting the DxD-Expedition flow. For more information, see Creating a DxDesigner Symbol Using Symbol Editor (DxD-Expedition Flow) on page 2-36. Tip: If you are using the Design Capture/DesignView-Expedition flow, use the Design Capture (DC) Symbol Editor software (see Creating a Symbol Using DC Symbol Editor (DC/DV-Expedition Flow) on page 2-29. Symbols are stored in a partition within the SymbolLibs\<partition_name>\sym directory. Use Symbol Editor to create and edit a symbol. For supplemental information on creating symbols in DxDesigner, consult the online help and the DxDesigner documentation.
Using the DxDesigner Symbol Wizard

DxDesigner features a Symbol Creation Wizard which provides a step-by-step, interactive GUIbased methodology for symbol creation. For detailed information on using the Symbol Wizard, consult online help associated with the wizard.
F-1
Using DxDesigner for Symbols and Netlist Generation Guidelines for Creating Symbols with DxDesigner (DxD-Expedition Flow)
Guidelines for Creating Symbols with DxDesigner (DxD-Expedition Flow)

Before creating a DxD-Expedition flow symbol, you need to know the PCB-related attributes required for generic and non-generic symbols. Table F-1 shows the attributes required for processing generic and non-generic symbols. Table F-1. Attributes Required for Processing Generic and Non-generic DxD Symbols Non-generic (built-in attributes) DEVICE # (Pin Numbers) SIGNAL NC PKG_TYPE HETERO (if required) Generic Symbols DEVICE (placed at the component level) Note: Other attributes will be processed and annotated using data from the parts database. Whether an attribute's value is annotated depends on settings in the expedition.cfg file.
The REFDES attribute is not required to be built-in with a prefix value (for example, C?), but, if not specified in the symbol or on the component, will default to a prefix of "U". Also note that the Reference Designator prefix specified in the parts database will not be used. When using the Symbol Creation Wizard in DxDesigner to create a new symbol, the wizard defaults to a valid central library path but does not specify the symbol partition in the central library (Figure F-1). Figure F-1. DxDesigner Symbol Creation Wizard
Select a valid symbol library partition from the Library path or alias dropdown list. For example, a valid alias to specify in the dialog box is as follows: <drive>:\<central_library_name>\SymbolLibs\<partition_name> You can also use the File > New command to create a new symbol. This methodology is documented in the following procedure.
F-2
Using DxDesigner for Symbols and Netlist Generation Creating 74f244_half Symbol Using DxDesigner
Creating 74f244_half Symbol Using DxDesigner

Use the following processes to create a 74f244_half symbol in DxDesigner: 1. On Windows, click Start > Programs > Mentor Graphics SDD > DxDesignerExpedition Flow > Design Entry > DxDesigner to invoke DxDesigner. On UNIX or Linux, key in DxDesigner from your SDD_HOME directory.
2. Click File > New and click the Symbol type icon. 3. Key in the following partition name and symbol name in the Name field. You must type a colon between the partition name and symbol name. Logic_Gates:74f244_half Note When entering the new symbol name, you must precede the symbol name with a valid symbol partition name/alias that already exists in the central library. The partition alias and the symbol name must be separated with a colon (:). If the symbol name is not preceded with a valid partition name and a colon, the created symbol will not be saved to the proper location in the central library folder structure and will not be added to the central library. 4. Click OK; the work area displays. Note that the Symbol type is set by default. 5. Right click the mouse and select Properties from the popup menu. The Use Properties dialog box displays. 6. Adjust the bounding box width to 100 and the height to 100. 7. Set the Symbol Type to Module and click OK. Tip: Click View > Full to readjust the work area to include the new proportions of the bounding box. 8. Click Add > Box and draw the symbol body/rectangle to the dimension shown in Figure F-2 on page F-4. To escape the Add Box command, press Escape or click the select icon. 9. Click Add > Pin and insert pins as shown in Figure F-2.
F-3
Figure F-2. Symbol 74f244_Half Displayed in DxDesigner
Naming Pins and Assigning Pin Attributes

Use the following steps to name pins and assign pin attributes to the newly placed pins: 1. Double click the first pin (upper left in the design); the Pin Properties dialog box displays. 2. Type ~G in the Label field and ensure the Visible property is enabled (illustrated in Figure F-3). This is the name of the pin.
F-4
Figure F-3. Pin Properties Dialog Box (DxDesigner)
3. Click the Attributes tab and enter the following attribute name and value in the specified fields. Ensure the Visibility mode is set to Invisible (see Figure F-4): Figure F-4. Assigning Pin Attributes
F-5
Note If the software prompts you to display expanded attributes, click No. 4. Click Set to add the new attribute name and value to the Attributes list. 5. Add the PINTYPE attribute by entering the following in the specified fields (see Figure F-5): Figure F-5. Assigning a Second Pin Attribute
6. Click Set and click OK and the symbol appears as follows with the first pin defined. If the software prompts you to display expanded attributes, click No.
F-6
Figure F-6. Symbol 74f244_Half in DxDesigner with First Pin Defined
7. Double click the next pin (below the first pin you named); the Pin Properties dialog box displays. Ensure the Name tab displays. 8. Enter A1 in the Label field and click the Attributes tab. 9. Repeat Steps 3 through 7 to name the remaining pins in the symbol as shown in Figure F-7 on page F-9. Use the pin names and attributes in Table F-2 and Table F-3 (be sure to increment the pin values on the left side pins and use Y and incremental numbers for the right side pins): Table F-2. Left Side Pin Attributes Pin Name A1 Pin Attributes Label = A1 Name = # Value = 2,11 Name = PINTYPE Value = IN Label = A2 Name = # Value = 4,13 Name = PINTYPE Value = IN Label = A3 Name = # Value = 6,15 Name = PINTYPE Value = IN Visibility Mode Visible Invisible Invisible Visible Invisible Invisible Visible Invisible Invisible
A2
A3
F-7
Table F-2. Left Side Pin Attributes Pin Name A4 Pin Attributes Label = A4 Name = # Value = 8,17 Name = PINTYPE Value = IN Visibility Mode Visible Invisible Invisible
Note: If the software prompts you to display expanded attributes, click No.
Table F-3. Right Side Pin Attributes Pin Name Y1 Pin Attributes Label = Y1 Name = # Value = 18,9 Name = PINTYPE Value = OUT Label = Y2 Name = # Value = 16,7 Name = PINTYPE Value = OUT Label = Y3 Name = # Value = 14,5 Name = PINTYPE Value = OUT Label = Y4 Name = # Value = 12,3 Name = PINTYPE Value = OUT Visibility Mode Visible Invisible Invisible Visible Invisible Invisible Visible Invisible Invisible Visible Invisible Invisible
Y2
Y3
Y4
Ensure the pin names appear as shown in Figure F-7.
F-8
Figure F-7. 74f244_Half Device in DxDesigner
Adding Device, Package Type and Other Attributes

Use the following steps to add device, package type, and other required information to the symbol: 1. Press Escape or click the select icon to return to select mode.
2. Click in the design, right-click the mouse button, and select Properties from popup menu; the Symbol Properties dialog box displays (Figure F-8).
F-9
Figure F-8. Symbol Properties Dialog Box (DxDesigner)
3. Type DEVICE in the Name field, key in 100-100000-001 in the Value field, select Invisible from the Visibility pulldown, and click Set. DEVICE now appears in the Attribute list (see Figure F-9).
F-10
Figure F-9. Symbol Properties Dialog Box (DxDesigner) - One Attribute Assigned
4. Add PKG_TYPE to the Attribute list using the process in Step 3. Key in PKG_TYPE in the Name field, key in 20_PIN_SOIC in the Value field, select Invisible from the Visibility pulldown, and click Set. PKG_TYPE now appears in the Attribute list (Figure F-10).
F-11
Figure F-10. Symbol Properties Dialog Box (DxDesigner) - Two Attributes Assigned
5. Enter the attributes in Table F-4 in the dialog box. The software adds these attributes to the list in alphabetical order: Table F-4. Assigning Properties to 74f244_half Symbol Attribute Name HETERO PARTS SIGNAL SIGNAL Attribute Value LOGIC:G244A, (LOGIC:74F244_FULL), (LOGIC:74F244_HALF) 2 GND;10 VCC;20 Visibility Setting Invisible Invisible Invisible Invisible
The Symbol Properties dialog box appears as shown in Figure F-11:
F-12
Figure F-11. Symbol Properties Dialog Box (DxDesigner) - All Attributes Assigned
6. Click OK in the Symbol Properties dialog box to place properties in the design. 7. Move the text and pin properties to resemble the illustration in Figure F-12. Do not to move the pin, only the pin property. Figure F-12. Symbol 74f244_Half with Pins Defined
Tip: Click Refresh to clear bounding box display problems.
F-13
Using DxDesigner for Symbols and Netlist Generation Packaging a DxD Schematic Using the Netlist-based Flow
8. Click File > Save to save the 74f244_half symbol. 9. Click File > Exit to exit DxDesigner.
Packaging a DxD Schematic Using the Netlistbased Flow

Run the Create PCB Netlist (common) command on the schematic. The Create PCB Netlist utility is a bidirectional interface that enables the interchange of structural netlist data between the software tools. Netlists are read into and saved in a neutral format. Perform the following steps to prepare the schematic design for export to a PCB layout system and package the schematic: 1. Click File > Save + Check to save the schematic and check the connectivity of the nets and components within the schematic. If errors display in the message field, fix the problem based on information provided by the error message. Run Save + Check until all errors are resolved. 2. Click Tools > Create PCB Netlist (common); the ViewPCB dialog box displays. 3. Adjust settings in the ViewPCB dialog box as shown in Figure F-13. Ensure that the Netlist Format / Vendor setting is set to Expedition. Also, enable the Create Netlist for Layout / Assign Reference Designators and Run the command line after processing options to display the command line sequence in the dialog box.
F-14
Figure F-13. ViewPCB Dialog Box (DxDesigner) Running Forward Annotation
Note Selecting the Run command after processing option invokes the DxDesigner to Expedition PCB dialog box. 4. Click Run and the software generates the schematic design data within a netlist file based on the selected PCB layout system-specific PCB configuration file. The Results tab displays the outcome of the netlist generation. While the software displays various notes and warnings, ensure that no errors, failures, or fatal errors appear in the Results tab (see Figure F-14).
F-15
Figure F-14. Results Tab (ViewPCB Dialog Box)
If the design packages without errors, the DxDesigner to Expedition PCB dialog box displays (Figure F-15). 5. Complete the DxDesigner to Expedition PCB dialog box as shown in Figure F-15 to configure the data transfer from DxDesigner to Expedition PCB.
F-16
Figure F-15. DxDesigner to Expedition PCB Dialog Box
In the Select Central Library field, specify an existing Expedition Central Library. In the Select Template field, specify an existing PCB design to use as the template on which Expedition creates a new design. In the PCB Directory field, specify the output directory for the new design. The Options tab remains unchanged. 6. Click OK. If a warning box displays saying that Back annotation has been disabled, click OK. The following dialog box displays (Figure F-16): Figure F-16. Expedition PCB Forward Annotation Choice Box
7. Click Yes. The software invokes Expedition PCB and the Project Integration dialog box displays. Go to Step 4 on page 4-25 to use Expedition PCB software to forward annotate the design.
F-17
F-18
Appendix G Library Manager Automation Scripting

Overview
Automation scripting allows you to interact with the operation of the product using automation languages like Visual Basic, VBScript, JScript or C++. Functionality includes: Creating new design elements Modifying design elements Intercepting events allowing you to extend the functionality of the product Changing the settings of the product
Library Manager delivers specific automation scripting for use within the tool. Automation scripting allows you to customize select features in the application software for your use. This section describes the Library Manager-specific automation scripting. Library Manager shares three types of automation customization features with Expedition PCB: Shortcut Keys Command Bars Add-in Controls
Consult Expedition PCB Automation online help for more information.
Creating Custom Scripts and Dialog Boxes

Library Manager delivers software for customers to create custom scripts and dialog boxes and access them from the software application. Use the File > New Script Form command to create custom scripts and dialog boxes for use within Library Manager. Use the File > Open Script Form to open, access, and edit your own scripts and dialog boxes associated with the Library Management software. See Creating a User-defined Script or Dialog Box on page 5-9 and Opening an Existing User-defined Script or Dialog Box on page 5-11 for more information.
G-1
Library Manager Automation Scripting Standard Automation Interfaces in Library Manager
Standard Automation Interfaces in Library Manager

The following is a list of automation programming interfaces provided by Library Manager:
ActiveLibrary Property
Prerequisites
None.
Description
Identifies the active central library.
Access
Read-Only
Syntax
object.ActiveLibrary
The ActiveLibrary property syntax includes these parts: Table G-1. ActiveLibrary Property Syntax Part object <return_type> Description An object expression that evaluates to a Library Manager Application object. A string that identifies a Library Manger central library (*.lmc) file.
Name Property
Prerequisites
None.
Description
Returns the name of the application software.
Access
Read-Only
G-2
Syntax
object.Name
Table G-2. Name Property Syntax Part object <return_type> Description An object expression that evaluates to a LibraryManagerApp object. A string that identifies the name of the active application software.
Version Property
Prerequisites
None.
Description
Returns the version of the application software (for example, EXP2005 SPac1).
Access
Read-Only
Syntax
object.Version
Table G-3. Version Property Syntax Part object <return_type> Description An object expression that evaluates to a LibraryManagerApp object. A string that identifies the software version number.
FullName Property
Prerequisites
None.
G-3
Description
Returns the software application's full name (including directory path to the location of the executable).
Access
Read-Only
Syntax
object.FullName
Table G-4. FullName Property Syntax Part object <return_type> Description An object expression that evaluates to a LibraryManagerApp object. A string that identifies the directory path and name of the executable program.
Visible Property
Prerequisites
None.
Description
Sets or returns the application's visible property.
Access
Read/Write
Syntax
object.Visible = True | False
Table G-5. Visible Property Syntax Part object Description An object expression that evaluates to a LibraryManagerApp object.
G-4
Table G-5. Visible Property Syntax Part True False Description String that causes objects to be visible String that causes objects to not appear.
PreviewCell Method
Prerequisites
None.
Description
Enables the application to open a Preview window and display a specified cell object. For example, select a cell object and view the cell in a Preview window.
Syntax
object.PreviewCell (ByVal <centralLib> As String, ByVal <partition> As String, ByVal <cell> As String)
Table G-6. PreviewCell Property Syntax Part object centralLib partition cell Description An object expression that evaluates to a LibraryManagerApp object/ Identifies the central library that contains the cell object. Identifies the cell partition within the central library where the cell resides. Identifies the cell name to display in the Preview window.
PreviewSymbol Method
Prerequisites
None.
G-5
Description
Enables the application to open a Preview window and display a specified symbol object. For example, select a symbol object and view the symbol in a Preview window.
Syntax
object.PreviewSymbol (ByVal <centralLib> As String, ByVal <partition> As String, ByVal <symbol> As String, ByVal <type> As Long)
Table G-7. PreviewSymbol Property Status Part object centralLib partition symbol type Description An object expression that evaluates to a LibraryManagerApp object. Identifies the central library that contains the symbol object. Identifies the symbol partition within the central library when the symbol resides. Identifies the symbol name. Identifies the symbol type to display in the Preview window (for example, MODULE, COMPOSITE, and so forth).
CloseAllPreviewWindows Method
Prerequisites
None.
Description
Enables the application to close any Preview window used to view symbols and cells.
Syntax
object.CloseAllPreviewWindows ()
OpenURL Method
Prerequisites
None.
G-6
Description
Opens a specified Uniform Resource Locator (URL) in the default web browser in Library Manager. A URL provides the global address of documents and other resources on the World Wide Web (WWW). The first part of the address indicates what protocol to use (for example www or ftp), and the second part specifies the IP address or the domain name where the resource is located.
Syntax
object.OpenURL (ByVal <url> As String)
<url> = the Uniform Resource Locator (URL) used by the software to display information in the web browser in Library Manager.
OnLMCModify Method
Prerequisites
None.
Description
Notifies Library Manager that the central library has changed and the Library Navigator Tree (see Library Navigation Tree with Central Library Defined on page 2-4) should be refreshed. The software refreshes only the area of the navigator tree that was modified. For example, if symbol partitions in the central library were changed, only subnodes in the Symbols node of the Library Navigator Tree are refreshed.
Syntax
object.OnLMCModify (ByVal <centralLib> As String , ByVal <partition> As String , ByVal <object> As String , ByVal <type> As Long)
Table G-8. OnLMCModify Method Property Status Part object centralLib Description An object expression that evaluates to a LibraryManagerApp object. Identifies the central library that contains object modifications that require the Library Navigator Tree to be refreshed.
G-7
Table G-8. OnLMCModify Method Property Status Part partition Description Identifies the partition within the central library where edits occurred and require the navigator tree to be refreshed. Identifies the object(s) that changed in the central library and require the navigator tree to be refreshed. Identifies the object type that changed in the central library and require the navigator tree to be refreshed.
object type
OnReusableBlocksEditor Method
Prerequisites
None.
Description
Invokes the Reusable Blocks dialog box (see Managing Reusable Blocks (DC/DV-Expedition Flow) on page 4-35).
Syntax
object.OnReusableBlocksEditor();
OpenLibrary Method
Prerequisites
None.
Description
Provides the functionality to open a specific central library. You can request a pointer to an open (active) central library using ActiveLibrary Property. Also, you can determine the flow mode associated with the central library using FlowMode / FlowType Method).
Syntax
object.OpenLibrary (ByVal <FullName> As String) As IMGCLMLibrary
G-8
ActiveLibrary Property
Prerequisites
None.
Description
Provides the functionality to access a central library that is already open and in use (see ActiveLibrary Property). You can also determine the flow mode associated with the central library using FlowMode / FlowType Method).
Access
Read-only.
Syntax
object.ActiveLibrary MGCLMLibrary
FlowMode / FlowType Method

Prerequisites
None.
Description
If you have a pointer to a central library using ActiveLibrary Property and OpenLibrary Method, then use this method.
Access
Read-only.
Syntax
object.FlowType MGCLMLibrary
FullName Property
Prerequisites
None.
G-9
Description
Provides the full name of the active central library, including the directory path). You can also determine the flow mode associated with the central library using FlowMode / FlowType Method. See OpenLibrary Method and ActiveLibrary Property to display the central library name as well.
Access
Read-only.
Syntax
object.FullName MGCLMLibrary
G-10
Glossary
Administrator Individual(s) responsible for the manipulation and maintenance of the Parts Manager (PM) database using the Parts Manager Administrator (PMA) interface. American Standard Code for Information and Interchange (ASCII) A character format standard used by the Windows NT workstation for storing text. An ASCII file can be edited, printed, or typed. Cells (or Footprints) Data that includes the graphic and non-graphic information that are grouped together to represent various components in a circuit layout. Central Library A central library is a collection of interrelated libraries with an improved level of integrity and consistency checking. A Central Library contains a library control file (.lmc) which maintains the inventory of the contents in the Central Library. An individual library (one of the sub-folders in the Central Library) is a collection of partitions. Libraries are the storage locations for Parts, Cells, Symbols, IBIS Models (Windows only), and padstacks. The Library Manager interface controls Central Library creation, partition editing, and invocation of library editors. Designs then reference a Central Library as a whole, rather than inter-mixing library files from various locations. Client Users that access information in the PM database in read-only mode using other software products, such as Design Capture (DC). Collapse Hides tables and/or subfolders below a highlighted folder in the PM Classification Tree. Design Capture (DC) A design entry tool that allows you to create schematic designs which may be partitioned into various function blocks and represented with different levels of hierarchy. You can choose topdown, bottom-up and/or middle-out methodologies, which allow complex systems to be easily represented and traversed. Expand Allows you to display hidden tables and/or subfolders in the PM Classification Tree. Folders that can expand display a plus (+) sign when you click to expand.
Glossary-1
Glossary
Expedition PCB A point tool for the design, layout, analysis, and manufacture of printed circuit boards. Use Expedition PCB to create the board outline, build and place components, and route your design. Folder A user-defined category to which one or more parametric tables (possibly no tables) may belong. Folders partition parametric data at the highest level during parametric part selection (PPS) operations in the PM database. Footprints See Cells. IBIS Model Provides a complete behavioral description of the input and output elements of a component. Every active component that you intend to simulate must be described by an IBIS model before the signal integrity tool suite can be used to simulate the design. IBIS models are not available in Library Manager using Linux. Layout Templates Defines PCB design templates for use by Expedition PCB when starting a new PCB design. The Available Templates list displays all the available templates in the central library. Library Manager Library Manager provides the ability to manage your company library (Central Library) from a single seat without the need to purchase additional licenses for other software tools, such as design entry software (Design Capture and DesignView) and Expedition PCB. All software tools used to create symbols, cells, and parts are launched from within Library Manager. When Library Manager is invoked within a point tool (such as Design Capture, DesignView, or Expedition PCB), only editors that apply to the specific point tool are available. For example, if you invoke Library Manager through Design Capture, you can access all editors EXCEPT Cell Editor, IBIS Models, Padstacks, Layout Templates, and Parts Manager. If you invoke Library Manager through Expedition PCB, you can access all editors EXCEPT Symbol Editor and Parts Manager. Menubar A rectangular area at the top of the client area of a window that contains the titles of the standard pulldown menus for that application. Message box The generic name for any dialog box (window) that provides information, gives the current state of a work in progress, asks a question, issues a warning, or draws attention to an error. Mnemonics Mnemonics are single characters of a menu selection. The mnemonics are the letters underlined on the menu bar and pulldown menus. When the pulldown menu displays, press the <ALT> key, and type in the character string to invoke the command.
Glossary-2
Glossary
Padstacks A grouping of pads (SMD) and pads and holes (Through). Each padstack is one of five types: pin (SMD or Through), mounting hole, fiducial, test point or via. Pin types may or may not have a hole and are the origin of the padstack. A pin represents the trace tie point of the padstack and has an alphanumeric pin number assigned in the Cell Editor. Padstack Editor Allows you to create padstacks. Each padstack is one of five types: Fiducial, Mounting Hole, Pin-SMD, Pin-Through or Via. When defining a padstack, you first need to assign one of the above types. Parametric Data Parametric data is any user-definable data (tolerance, current, and so forth), that is tied to a part number. Part numbers are grouped into folders and tables in the PM Classification Tree. Parametric Part Selection (PPS) Data Data that is associated with internal processes such as design development (cell name, simulation model name, and so forth), manufacturing (surface mount, through hole, and so forth), or purchasing (purchase price, inventory, and so forth). PPS data can also be associated with external processes such as device parameters (voltage, current, power rating, and so forth), manufacturer information (manufacturer name, manufacturer part number, and so forth), or other external processes. Parametric Table Parametric tables are user-definable tables stored in the PM database. These tables hold userdefinable component parameters, such as thermal properties, electrical characteristics, cost, and other information. Every parametric table has a unique folder and table combination associated with it which can be used to locate the table in the PM Classification Tree during parametric part selection (PPS) operations. Partition A partition is a user-defined grouping of data objects. For example, the Cell Library might be broken up into partitions for SMD Cells, Through Cells, Mechanical Cells, and Drafting Cells. Part Label In the Part Editor software, the part label is more general than the part name or part number, but is still very recognizable. Part Name In the Part Editor software, the part name is usually more recognizable than the part number. Part Number The part number corresponds to a company (corporate) number. Many vendor parts have the same speed, packaging, and function, but different manufacturers. Part numbers can differentiate these vendor parts.
Glossary-3
Glossary
Parts Data Parts data includes gates, pins, and pin, gate, symbol and component properties. The mapping between parametric properties and their associated values are stored in the PM database. Parts Manager Parts Manager (PM) is an electronic component management tool that interfaces parametric data stored in a relational database and interfaces with parts data in the DC/DV-Expedition Library Manager flow. Users of electronics design applications, such as Design Capture (DC) and DesignView, can access this data from nodes on the network. Part Editor A tool that changes parts data entries, such as adding and deleting part numbers, or pin information. pin padstack A pin padstack is the graphical representation of the size and shape of a pad or a series of pads occurring, vertically aligned, on different board layers. A padstack can also include information on the finished hole size and the whether the hole is plated, to define the hole for inserting a component pin. The pin padstack geometry represents a component pin connection and consists of a geometry name, the pad graphics, and padstack attributes. There are three types of pin padstacks: blind - provides for a pin connection on one or more board layers from a surface layer to an internal layer. A blind pin padstack lets you define optional pin rules. surface - represents a pad for a surface-mount device and appears on either the top or bottom physical layer of the board, depending on the placement of a surface-mount device. through-pin - spans all physical layers of the board to provide connection to a component pin on all board layers. Reusable Blocks A feature in Library Manager used to create circuit blocks in both the layout and schematic files and store them in the central library. Users can design a circuit block in both areas (schematic and layout), verify the circuit, and store the circuit in the central library. This provides the ability to utilize known good circuitry with the simplicity of placing a single element in a design. Schematic A drawing that shows, by means of graphic symbols, the electrical connections, symbols and functions of a specific circuit arrangement. Symbols A function (gate) or group of functions on a schematic in design entry software, such as Design Capture or DesignView. Symbol Editor A editing environment in which symbols are built and edited. The Symbol Editor's editing environment allows you to open multiple libraries and edit multiple symbols during a single session.
Glossary-4
Glossary
Table A user-defined subcategory to a folder that contains the parametric table file. Tables partition parametric data on a secondary level (behind folder selection) during parametric part selection (PPS) operations. Wildcard Searches The following examples show the types of wildcard searches that you can make: # - Selects any single digit (0 through 9).
character# - Selects all entities that begin with a specified character and a single digit (but not a character).
? - Selects any single character.
Character? - Selects entities that begin with a specified character and has one character following it.
Character?? - Selects all entities that begin with a specified character and have two characters following it.
Note: The "?" wildcard character search performs properly on newly created tables and tables that were translated from Version 98.X to WG2004. However, "?" wildcard searches do not work properly on tables that were translated from Version 99.X to WG2004. To work around this problem, extract data in the table to an ASCII file, delete the table, and insert the ASCII file using the PM Batch Utility or the Insert Parametric Data dialog box.
* - Selects all available entities (zero or more characters)
Character* - Selects all entities that begin with a specified character (for example, 10* specifies all symbols that begin with 10).
*character - Selects all entities that end with a specified character (for example, *H specifies all files that end with H).
Glossary-5
Glossary
*character* - Selects all entities that conform to a specified character string (for example *r* returns all entities that have "r" in the string).
[character-character] - Selects all entities that start within the range you specify. For example, [ad] returns all entities that begin with the letters A, B, C, or D.
*[!character] - Selects all entities that do not end with the specified character. For example, *[!W] returns all entities that do not end with the character W.
character[!character-character]# - Selects all entities that begin with a specified character followed by any character that falls within a specified range of characters, followed by a digit (or digits).
Note: Searches for values in scientific notation cannot end with a wildcard. For example, 5e* or 5e? as a search criteria is invalid.
Glossary-6
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Index
A
Accessing a Central Library, 1-3 ACRO_HOME variable, 5-9 Activating All Partitions for Search, 2-17 Add Circle Command, 2-73 Add Component dialog box (DxDesigner), 4-20 Add Pins Range dialog box, 2-45 Adding Attachments to the Parts Manager Database, 3-97 Parameters to a Parametric Table, 3-8 Parametric Data to Parts, 3-55 Part Numbers Manually to the PM Database, 3-29 Pin Numbers to DC/DV symbol, 2-34 Pins to a DC/DV Design, 2-32 Properties to a DC/DV symbol, 2-35 Properties to Parts Manager, 3-14 Symbols to a DxD schematic, 4-20 Altering Search Path Schemes, 2-17, 2-18 altran utility, A-13 ASIC/FPGA Toolkits, 4-3 Assigning Alternate Symbols, 2-83 Central Library to a DxD Project, 4-13 Central Library to a Project, 4-2 Full Package, 2-86 Pin attributes in a DxD design, F-4 Pin Names to Full Package, 2-88 Pin Names to Half Package, 2-85 Pin Numbers, 2-81 Symbols as Default Symbols, 2-89 Attaching a Symbol Library to DxD Project Search Path, 4-17 Attachment Data, 3-97, 3-101 Auto Router, 4-24 Automatic Back Annotation, 4-30 Automatic Pin Numbering, 2-34 Automation interfaces in Library Manager, G-2
Automation scripting, G-1 ActiveLibrary property, G-2, G-9 CloseAllPreviewWindows method, G-6 FlowMode/FlowType method, G-9 FullName property, G-3, G-9 Name property, G-2 OnLMCModify Method, G-7 OnReusableBlocksEditor method, G-8 OpenLibrary method, G-8 OpenURL method, G-6 PreviewCell method, G-5 PreviewSymbol method, G-5 Version property, G-3 Visible property, G-4 Available Templates List, 5-1
B
Back Annotation, 4-30 Updates to a Schematic, 4-24 Backing Up Central Library Files, 5-14 Batch Update Utility, 3-79, 3-91 Bottom Mount, 2-57 Building a Pad, 2-59 a Surface Mount Pad, 2-57 a Through-Hole Padstack, 2-58 PCB Design, 4-24
C
CellDBLibs Subdirectory, 2-6 Cells Copying, 2-74 Creating, 2-65 Drawing, 2-65 Moving, 2-74 Package, 2-65 Patterns, 2-67 CentLib.prp File, 2-7, 2-11, 3-71
Index-1
Central Library Accessing, 1-3 Associating a flow type, 2-1, 2-5 Backups, 5-14 Creating a Central Library, 2-2 Defining a flow type, 2-3 Description and definition, 1-3 Determining flow type association, 2-5 Editing or modifying in the DxDExpedition flow, 2-8 Importing DxD Symbols, 2-27 Linking a DxD Project, 4-14 Managing model data files, 2-90 Opening a Central Library, 2-4 Opening a pre-EXP2005 central library, 2-10 Packaging Parts (Expedition), 2-8 Recommended permissions, 1-6 Setting up partitions, 2-14 Subdirectories and Files, 2-6 Upgrading for UNIX and Linux Use, C-1 Viewing object associations, 1-15 Viewing properties, 1-13 Central Library (.lmc) File, 4-6 Changing Central Library File, 3-39 Parametric Table Name, 3-17 Checking Property Verification Settings, 2-12 Closing a Design, 4-10 Commands Copy Model, 2-96 Delete Model, 2-96 DxDatabook Properties, D-28 Edit Model, 2-95 Find (Library Navigator Tree), 1-17 Import Model, 2-92 Modify Cell and Symbol Pins, 2-97 New Model, 2-94 New Script Form, 5-9 Open Script Form, 5-11 View Model, 2-95 Common Database (CDB) Compiler, 4-10 Common Database (CDB) Compiler (DC/DV), 4-10 Common Database directory (CDB), 4-6 Compiling a DxD schematic, 4-23 Compiling DC/DV Schematics, 4-10 Configuring Linux workstation, 1-5 Configuring Parts Manager Administrator, 3-4 Configuring UNIX workstation, 1-5 Configuring WDIR variable on Windows, 1-4 Connecting components in DxD, 4-22 Copying a reusable block, 4-42 Cells via the workspace tree, 2-74 Existing Layout Template, 5-3 Model files, 2-96 Objects in the workspace tree, 2-99 Padstacks via the workspace tree, 2-101 Parameters from One Parametric Table to Another, 3-17 Parts via the workspace tree, 2-90 Symbols via the workspace tree, 2-55 Using Keyboard Shortcuts, 2-75, 2-82, 2-85, 2-88 Create Package Cell Dialog Box, 2-65, 2-66, 2-70 Creating a Central Library, 2-2 a New Schematic, 4-4 Cell Partitions, 3-41 Cell partitions from the workspace tree, 2-15 Cells, 2-65 Central Library, 2-1 Central Library partitions, 2-14 Custom dialog boxes, G-1 Custom scripts, G-1 Design Project, 4-2 Dx Design Project, 4-13 DxD Project and link to a Central Library, 4-14 DxD Symbols, 2-36 DxD Symbols using the wizard, 2-37 Flattened Netlist (DC/DV), 4-10 Holes, 2-55, 2-58 Model file partition in the workspace tree, 2-91 Model files, 2-94 Multiple Search Path Schemes, 2-18
Index-2
New Gate Information, 2-78 New logical/physical reusable block, 4-36 New PCB Design, 4-25 New Template from an Existing Design File, 5-2 Pads, 2-55, 2-56 Padstacks, 2-55 Parametric Tables, 3-5 Part Entries, 2-74 Part partitions from the workspace tree, 2-16 Partition Search Paths, 2-17 Partitions in a Central Library, 2-14 Parts Partitions, 3-42 Reusable Blocks, 4-35 Schematic workspace in DxDesigner, 4-19 Surface Mount Pad, 2-55 Symbol Partitions, 3-41 Symbol partitions from the menubar, 2-14 Symbols, 2-29 Symbols in Dx Symbol Editor, 2-37 Template, 5-1 Custom Search Path Schemes, 2-18 Part Numbers from the PM Database, 3-33 Partitions from the workspace tree, 2-102 Parts, 2-25 Symbols, 2-25 Symbols via the workspace tree, 2-54 Design Architect and Expedition Tools, B-1 Design Capture Project, 4-2 Design Configurations dialog box, 4-15 Design project (dproj) file (DxD-Expedition Library Manager), 4-17 Device data mapping (DxD to Expedition), 2-9 Dialog Box, 2-15 Add Component (DxDesigner), 4-20 Add Pins Range, 2-45 Copy Padstack, 2-101 Create Package Cell, 2-66, 2-70 Design Configurations (DxD-Expedition Library Manager), 4-15 DxDesigner to Expedition PCB, F-16 Edit Properties, 2-32 Import (Part Editor), 2-78 Layout Templates, 4-6 Library Services, 2-27 Modify Pins, 2-97 New, 4-4 New Cell, 2-70 New Model Partition, 2-91 New Part Partition, 2-16 New Reusable Block, 4-37 New SPICE Model, 2-94 New Symbol, 2-31 New Verilog Model, 2-94 Partition Editor, 2-14 Partition Open, 2-30 Partition Search Paths, 2-17 Pin Mapping, 2-83, 2-86 Pin Properties (DxDesigner), F-4 Place Parts and Cells, 4-25 Place Pins, 2-66, 2-72 Preferences in Dx Symbol Editor, 2-39 Project Editor (DxDesigner), 4-18 Project Integration, 4-25 Project Settings, 4-5 Properties, 2-73 Property Definition Editor, 2-11
D
Default Symbol, 2-89 Defining Clearances, 2-22 Devices, 2-74 Graphic Levels, 2-22 Layers, 2-22 Pads, 2-60 Partition Search Path Scheme, 2-17 Parts data, 2-74 Pins Mappings, 2-74 Planes, 2-22 Units Display Settings, 2-20 Vias, 2-22 Deleting a reusable block, 4-45 Cells, 2-25 IBIS Models, 2-25 Model files, 2-96 Objects from the workspace tree, 2-102 Padstacks, 2-25 Parametric Tables, 3-21
Index-3
Property Verification, 2-13 Replace Cell, 4-33 Reusable Blocks, 4-36 Select Project File, 4-25 Setup Parameters, 2-22 Symbol Properties (DxDesigner), F-9 Units Display, 2-20 Unreserve Partitions, 2-19 ViewPCB (DxDesigner), F-14 Display Control Dialog Box, 4-24 Displaying I/V Curves, 5-4 Invisible Text, 4-6, 4-9 dproj file, 4-17 Draw Mode Command, 2-65, 2-68, 2-72 Drawing a Symbol, 2-31 Dx Symbol Editor Adding device and package type attributes, 2-50 Adding pins, 2-44 Adjusting symbol outline dimensions, 2-42 Adjusting symbol rectangle size, 2-42 Assigning pin numbers, 2-47 Assigning properties to pins, 2-47 Creating a Symbol, 2-37 Defining pin attributes, 2-44 Origin, 2-42 Overview, 2-36 Setting fill color, 2-42 Setting Preferences, 2-39 Specifying symbol type attribute, 2-43 Symbol origin, 2-42 DxD Symbol Creation Wizard, 2-37 DxD to Expedition flow wizards, A-1 DxDatabook Data Editor, 5-11 DxDatabook Data Editor in Library Manager, D-1 Adding a table to a configuration, D-12 Adding a table to a configuration (*.dbc) file, D-15 Adding component libraries to a configuration (*.dbc) file, D-12 Assigning properties to new tables, D-30 Connecting to parametric databases, D-3 Creating a configuration (*.dbc) file, D-9 Creating a configuration (*.dbc) file from existing configuration, D-11 Creating an ODBC data source on Windows, D-3 DxWebPack configuration, D-25 Editing database table properties, D-35 Editing parametric data, D-37 Editing properties, D-28 Parametric databases and supported platforms, D-2 Removing tables, D-33 Setting environment variables, D-2 Specifying a web-based data source, D-17 Using a configuration (*.dbc) file, D-8 Viewing table properties, D-30 DxDatabook Properties command, D-28 DxDesigner Adding symbols to a schematic, 4-20 Connecting components, 4-22 Creating a schematic workspace, 4-19 Heterogeneous symbols, E-2 DxDesigner Project, 4-13 DxDesigner Project Translation Wizard, A-14 DxDesigner to Expedition device data mapping, 2-9 DxDesigner to Expedition PCB dialog box, F-16 DxDesigner to Library Manager Migration Wizard, A-1 DxD-Expedition Library Manager limitations, E-1 DxWebPack, D-25
E
Editing a reusable block, 4-42 Central Library Name or Location (DxDExpedition flow), 2-8 Data source names in DxDatabook, D-22 DxD Symbols in Dx Symbol Editor, 2-36 Holes, 2-62 IBIS Models Within IBIS Librarian, 5-3 Model files, 2-95 Pads, 2-62 Partition Search Paths, 2-17 Property Verification, 2-12
Index-4
Symbols, 2-29 Electrical Units Display Format, 2-20 Environment variables for Linux, 1-5, 5-8 Environment variables for UNIX, 1-5, 5-8 EPD_ACROREAD_BIN variable, 5-9 Establishing Common Properties in a Central Library, 2-11 Exiting Parts Manager Administrator, 3-103 Expedition PCB, 4-24 Expedition style zoom (DxDesigner), 4-16 Expedition to DxDesigner device data mapping, 2-9 Exporting Cells, 2-23, 2-24 IBIS Models, 2-23 Padstacks, 2-23 Parts, 2-24 Symbols, 2-23
H
Heterogeneous and sub-gated parts, E-32 Heterogeneous symbols, E-1 Types, E-1 Holes Associations with pads, 2-62 Viewed in the workspace tree, 2-62
I
IBIS Librarian, 5-3 IBISModels Subdirectory, 2-6 Import Dialog Box (Part Editor), 2-78 Importing Cells, 2-23, 2-79 DxD symbols into a Central Library, 2-27 IBIS Models, 2-23 Model file, 2-92 Padstacks, 2-23 Parametric Data into a Table, 3-64 Pin names, 2-85 PPS Data With Attachment Data, 3-101 Referenced Objects, 2-23 Symbols, 2-23 Symbols and Cells to the Parts Database, 2-76 Inserting Parametric Tables from an ASCII File, 3-24 PPS Data into the PM Database, 3-34 Internal Time Stamp, 2-30, 5-7 Introduction Library Manager, 1-1 Using Other Software Tools and Library Manager Utilities, 5-1 Invisible Text, 4-9 Invoking Expedition PCB, 4-24 IBIS Librarian, 5-4 Library Manager, 2-2 Library PDF Documenter, 5-8 New Script Form command, 5-9 Open Script Form command, 5-11 Pre-existing EXP2005 central library, 2-10 Reusable Block software, 4-35
F
Fiducial, 5-7 File Viewer, 2-103 Files *.dbc, D-1 *.dproj (DxD-Expedition Library Manager), 4-17 CentLib.prp, 2-11, 3-71 viewdraw.ini, 2-8, 4-19 Find command (Library Navigator Tree), 1-17 Finding Objects in the Project Workspace Tree, 1-12 objects in the workspace tree, 1-17 Padstack elements in the workspace tree, 2-63 Fit All Command, 2-68, 2-72 Fit Board Command, 4-29 Forward Annotation, 4-24, 5-3 Forward Annotation (all Library Manager flows), 4-25
G
Generic heterogeneous symbols, E-2 Gerber Plot Setup File, 5-2
Index-5
Select Script Language dialog box, 5-9, 5-11 Linking Central Library and DxD Project, 4-13 Central Library and Project, 4-2 Central Library and Project File, 4-5 Physical Design Cells and Schematic Symbols, 2-74 Linux environment variable settings, 1-5 lmcwin2unix, C-1 LogFiles Subdirectory, 2-6, 2-103 Logging Out of Parts Manager Administrator, 3-103 Logical/Physical reusable block, 4-36
J
Job Management Wizard (Expedition PCB), 4-24
K
Keyboard Shortcuts, 2-75, 2-82, 2-85, 2-88
L
Layer Stackup, 5-2 Layout Subdirectory, 2-6 Layout Templates, 4-25, 5-1 Dialog Box, 4-6 LayoutTemplates Subdirectory, 2-6 Libraries tab, 1-13 Library Manager Automation scripting, G-1 Creating custom dialog boxes, G-1 Creating custom scripts, G-1 DxDatabook Data Editor, D-1 Editing a Central Library (DxD-Expedition flow, 2-8 Material / Process Editor, 5-12 Overview, 1-1 Prerequisites, 1-3 Product Description, 1-1 Standard automation interfaces, G-2 Subdirectories and files, 2-6 Library Navigator Tree viewer, 1-15 Library PDF Documenter, 5-8 Library Services, 2-23, 2-24 Accessible from Expedition PCB Environment, 2-23 Considerations When Using Library Services, 2-24 Dialog Box, 2-27 Using IBIS functionality, 5-6 Limitations of DxD-Expedition Library Manager, E-1
M
Managing Library Data, 2-23 SPICE files, 2-90 Templates, 5-1 Verilog A files, 2-90 Manipulating Data in a Central Library File, 2-23 Mapping DxDesigner device data to parts data, 2-9 Mapping Expedition to DxDesigner device data, 2-9 Mapping Properties to Parameters in Parts Manager, 3-12 Material / Process Editor, 5-12 Material Editor, 5-12 MGC_PKG_XINFO environment variable, B-1 Model data, 2-90 Copying a model file, 2-96 Creating a model file, 2-94 Creating a partition in a central library, 2-91 Deleting a model file, 2-96 Editing a model file, 2-95 Importing, 2-92 Viewing a model file, 2-95 Modifying Central Library, 3-39 Parametric Table Name, 3-17 Mounting Hole, 5-7
Index-6
Moving Cells via the workspace tree, 2-74 Objects in the workspace tree, 2-101 Parts via the workspace tree, 2-90 Symbols via the workspace tree, 2-55 Deleting partitions from the workspace tree, 2-102 DxD to Expedition flow wizards, A-1 DxDatabook Data Editor, 5-11, D-1 DxDatabook user configuration file (*.dbc), D-1 DxDesigner Project Translation Wizard, A-14 DxDesigner to Library Manager Migration Wizard, A-1 DxD-Expedition Library Manager, 1-9 DxD-Expedition Library Manager interface, 1-11 DxD-Expedition Library Manager limitations, E-1 Establishing Common Properties in a Central Library, 2-11 Generic and nongeneric heterogeneous symbols, E-2 Heterogeneous symbols, E-1 Heterogeneous symbols (generic and nongeneric), E-2 Library Manager, 1-1 Library Manager automation scripting, G-1 Library Manager Process Flows, 1-8 Library Navigator Tree viewer, 1-15 lmcwin2unix, C-1 Material / Process Editor, 5-12 Model data, 2-90 Model data (Verilog and SPICE), 2-90 Model data in Library Manager, 2-90 Modify Cell and Symbol Pins, 2-97 Moving objects in the workspace tree, 2-101 Padstack Editor, 5-7 Prerequisites, 1-3 Problems with Heterogeneous and subgated parts, E-32 Project Workspace Tree viewer, 1-12 Reusable Blocks, 4-35 Setting up Central Library partitions, 2-14 Supported Operating Systems, 1-5 Symbol Editor, 5-6 Types of Heterogeneous symbols, E-1
N
Naming DC/DV Pins in a Design, 2-32 Pins in a DxD design, F-4 Project Files, 4-3 Net Class Information, 5-2 New Cell Partition, 2-15 New Dialog Box, 4-4 New Project Command, 4-3 New Project Wizard, 4-2, 4-3 New Script Form command, 5-9 New Symbol Dialog Box, 2-31 Nongeneric heterogeneous symbols, E-2
O
Open Script Form command, 5-11 Opening a Central Library, 2-4 a New PCB Job, 4-24, 4-25 Operating Systems supported by Library Manager, 1-5 Oracle Client, D-2 Organizing Models by Device, 5-3 Origin (Dx Symbol Editor), 2-42 Overview Accessing a Central Library, 1-3 Associating a flow type to a central library, 2-1 Central Library, 1-3 Compiling and packaging a DxD schematic, 4-23 Copying objects in the workspace tree, 2-99 Creating a Central Library, 2-1 Creating Central Library partitions, 2-14 Creating custom scripts and dialog boxes, G-1 DC/DV-Expedition Library Manager, 1-9 Deleting objects from the workspace tree, 2-102
Index-7
Upgrading Central Libraries for Linux and UNIX Use, C-1 Using Design Architect with Expedition Tools, B-1 Using DxD Symbol Creation Wizard, 2-37 Using IBIS functionality in Library Services, 5-6 Using IBIS functionality in Part Editor, 5-5 Using the Libraries tab, 1-13 Visual IBIS Editor, 5-4 Workflow for DC/DV Library Manager, 1-6 Workflow for DxDesigner to Expedition Library Manager, 1-7 Partition Editor Altering Search Path Schemes, 2-18 Custom Search Path Schemes, 2-18 Multiple Search Path Schemes, 2-18 Partition Open Dialog Box, 2-30 Partition Search Paths, 2-17 Partitions, 2-14, 5-7 Accessed by Other Users, 2-24 Creating, 2-14 Creating a cell partition from the workspace tree, 2-15 Creating a part partition from the workspace tree, 2-16 Creating a symbol partition from the menubar, 2-14 Deleting via the workspace tree, 2-102 in Red Text, 2-24 Reserved, 2-14 Symbol, 2-29 Temp_Cell, 2-24 Temp_Symbol, 2-24 Parts Copying, 2-90 Moving, 2-90 Parts Manager Administrator Batch Update Utility, 3-79, 3-91 Configuring, 3-4 PM/PDB Synchronization Utility, 3-89 Validation Utility, 3-70 Parts Manager Database Adding Attachments, 3-97 Adding Parametric Data to Parts, 3-55 Adding Part Numbers Manually, 3-29 Deleting Part Numbers, 3-33 Inserting PPS Data, 3-34 Parts Manager Working Directory, 3-4 Parts Numbers in the PM Database, 3-33 PartsDBLibs Subdirectory, 2-7 PartsManager Subdirectory, 2-7 Paste Across Icon, 2-81 PDF Documenter, 5-8 Performing Backups, 5-14 Pin Mapping Dialog Box, 2-76, 2-83, 2-86 Pin Numbering, 2-34 Pin Numbers Assigned Automatically, 2-81
P
Packaging DC/DV Schematics, 4-10 DxDesigner schematics, F-14 Parts in Expedition Central Library, 2-8 Schematics, 4-11 Packaging a DxD schematic, 4-23 Pads, 2-59 Associations with holes, 2-62 Viewed in the workspace tree, 2-62 Padstack Editor Overview, 5-7 PanelTemplates Subdirectory, 2-6 Panning, 2-68 Parameter Setup, 2-22 Parametric database types supported by DxDatabook, D-2 Parametric Tables Adding Parameters, 3-8 Creating, 3-5 Deleting Tables, 3-21 Inserting from an ASCII File, 3-24 Renaming, 3-17 Part Editor, 2-74 Using IBIS functionality, 5-5 Part Label, 2-75 Part Name, 2-75 Part Numbers, 2-75 Adding to the PM Database Manually, 3-29
Index-8
Pin Properties dialog box (DxDesigner), F-4 Pin-SMD, 5-7 Pin-Through, 5-7 Place Device Command, 4-8 Dialog Box, 4-6 Place Line Command, 2-31 Place Parts and Cells Dialog Box, 4-25 Place Pins Command, 2-31 Dialog Box, 2-65, 2-66, 2-72 Place Text Command, 2-34 Place Wire Command, 4-6, 4-9 Placing Devices in a Design, 4-8 Parts and Cells (Expedition PCB), 4-24 Patterns, 2-65 Symbols and Devices, 4-6 Text, 2-35 PPS Data Insertion, 3-34 Prerequisite tasks Adjusting Central Libraries for Use on Linux, 1-4 Configuring Linux Workstations, 1-5 Configuring the WDIR variable (Windows), 1-4 Configuring UNIX Workstations, 1-5 Overview, 1-3 Setting Central Library Permissions, 1-6 Supporting Mixed Operating System Usage, 1-5 Preview Available Cells, 4-7 Procedure Adding a table to a library configuration (DxDatabook Data Editor), D-12 Adding a table to the configuration (*.dbc) file (DxDatabook Data Editor), D-15 Adding Attachment Data, 3-97 Adding DC/DV symbol properties, 2-35 Adding device and package type attributes (Dx Symbol Editor), 2-50 Adding Parameters to a Parametric Table, 3-8 Adding Parametric Data to Parts, 3-55 Adding Part Numbers to the PM Database, 3-29 Adding Pin Numbers to Pins (DC/DV), 2-34 Adding pins (Dx Symbol Editor), 2-44 Adding Properties to Parts Manager, 3-14 Adding symbols to a DxD schematic, 4-20 Adjusting symbol outline dimensions (Dx Symbol Editor), 2-42 Adjusting symbol rectangle size (Dx Symbol Editor), 2-42 Assigning a Layout Template, 4-6 Assigning Alternate Symbols, 2-83 Assigning pin attributes in DxD, F-4 Assigning Pin Numbers, 2-81 Assigning pin numbers (Dx Symbol Editor), 2-47 Assigning Pin Numbers (Part Editor), 2-81 Assigning properties to new tables (DxDatabook Data Editor), D-30 Assigning properties to pins (Dx Symbol Editor), 2-47 Associating a flow type to a central library, 2-1, 2-3 Attaching a Symbol Library to a DxD Project Search Path, 4-17 Building a Pad, 2-59 Building a Surface Mount Padstack, 2-57 Building a Through-Hole Padstack, 2-58 Checking Property Verification Settings, 2-12 Compiling a DxD schematic, 4-23 Compiling and Packaging a Schematic, 4-11 Configuring DxWebPack on Windows (DxDatabook Data Editor), D-25 Configuring Parts Manager Administrator, 3-4 Configuring WDIR variable on Windows, 1-4 Connecting components in DxDesigner, 4-22 Copying a cell, 2-74 Copying a model file, 2-96 Copying a padstack, 2-101
Index-9
Copying a part, 2-90 Copying a reusable block, 4-42 Copying a symbol, 2-55 Copying Existing Layout Template, 5-3 Copying objects in the workspace tree, 2-99 Copying Parameters from One Parametric Table to Another, 3-17 Creating a cell partition from the workspace tree, 2-15 Creating a Central Library, 2-1, 2-2 Creating a configuration (*.dbc) file (DxDatabook Data Editor), D-9 Creating a configuration (*.dbc) file (DxDatabook Data Editor) from existing configuration, D-11 Creating a DxD Project, 4-14 Creating a model file, 2-94 Creating a new logical/physical reusable block, 4-36 Creating a new model file partition via the workspace tree, 2-91 Creating a New Schematic, 4-4 Creating a Parametric Table, 3-5 Creating a part partition from the workspace tree, 2-16 Creating a Reusable Block, 4-35 Creating a schematic workspace in DxDesigner, 4-19 Creating a Surface Mount Padstack, 2-55 Creating a Symbol, 2-29 Creating a symbol in Dx Symbol Editor, 2-37 Creating a symbol partition from the menubar, 2-14 Creating a Symbol Using Dx Symbol Editor, 2-36 Creating an ODBC data source on Windows (DxDatabook Data Editor), D-3 Creating Cell Partitions, 3-41 Creating Cells, 2-65 Creating Cells in a Partition, 2-70 Creating Central Library partitions, 2-14 Creating New Template from an Existing Design File, 5-2 Creating Partition Search Paths, 2-17 Creating Parts, 2-74 Creating Parts Partitions, 3-42 Creating Symbol Partitions, 3-41 Defining Padstacks, 2-59 Defining pin attributes (Dx Symbol Editor), 2-44 Defining Units Display Settings, 2-20 Deleting a model file, 2-96 Deleting a reusable block, 4-45 Deleting a symbol, 2-54 Deleting objects from the workspace tree, 2-102 Deleting Parametric Tables, 3-21 Deleting Part Numbers from the PM Database, 3-33 Deleting partitions from the workspace tree, 2-102 Drawing a Symbol, 2-31 Editing a model file, 2-95 Editing a reusable block, 4-42 Editing data source names (Data Source Manager dialog box), D-22 Editing database table properties (DxDatabook Data Editor), D-35 Editing pads and holes from the workspace tree, 2-62 Editing parametric data (DxDatabook Data Editor), D-37 Editing properties (DxDatabook Data Editor), D-28 Establishing Common Properties, 2-11 Exiting Parts Manager Administrator, 3-103 Exporting Parametric Data to an ASCII File, 3-55 Finding objects in the tree, 1-12 Finding objects in the workspace tree, 1-17 Finding padstack elements, 2-63 Importing a model file, 2-92 Importing Cells Using Library Services, 3-47
Index-10
Importing Data from Another Central Library File, 3-52 Importing DxD symbols into a CL, 2-27 Importing Padstacks Using Library Services, 3-45 Importing Parametric Data into a Table, 3-64 Importing PDBs Using Library Services, 3-49 Importing pin names, 2-85 Importing PPS Data with Attachments, 3-101 Importing Symbols and Cells to the Parts Database, 2-76 Importing Symbols Using Library Services, 3-43 Inserting Parametric Tables from ASCII, 3-24 Inserting PPS Data into the PM Database, 3-34 Invoking a pre-EXP2005 central library, 2-10 Invoking Expedition PCB, 4-24 Invoking IBIS Librarian, 5-4 Invoking Library Manager, 2-2 Invoking reusable blocks, 4-35 Invoking the Find command, 1-17 Invoking Visual IBIS Editor, 5-4 Linking a Central Library With a Project File, 4-5 Linking a DxD Project to a Central Library, 4-14 Mapping Properties to Parameters in Parts Manager, 3-12 Modifying a Central Library File, 3-39 Moving a cell, 2-74 Moving a part, 2-90 Moving a symbol, 2-55 Moving Data Between PM Database and PDB, 3-79 Moving objects in the workspace tree, 2-101 Naming pins in DxD, F-4 Naming Pins on a DC/DV Symbol, 2-32 Opening a Central Library, 2-4 Opening a New PCB Job, 4-25 Packaging a DxD schematic, 4-23, F-14 Performing Gate Swapping, 4-27 Placing Devices in a Design, 4-8 Placing Pins and Cell Graphics, 2-67 Pushing Top Cell to Bottom Cell, 4-32 Refreshing a Display, 4-8 Removing Parametric Data from the PM Database, 3-57 Removing tables (DxDatabook Data Editor), D-33 Renaming a Dx symbol, 2-52 Renaming a reusable block, 4-44 Renaming Parametric Tables, 3-17 Replacing Cells (Expedition PCB), 4-33 Searching for objects in the workspace tree, 1-17 Searching for padstack elements, 2-63 Setting DxDatabook Data Manager environment variables, D-2 Setting environment variables on Linux, 1-5 Setting environment variables on UNIX, 1-5 Setting Expedition zoom style, 4-16 Setting fill color (Dx Symbol Editor), 2-42 Setting preferences in Dx Symbol Editor, 2-39 Setting up component libraries to the configuration (*.dbc) file (DxDatabook Data Editor), D-12 Setting Up Parameters, 2-22 Specifying symbol type attribute (Dx Symbol Editor), 2-43 Transferring data from DxD to Expedition PCB, F-16 Translating a DA schematic to Expedition PCB, B-1 Unreserving Library Partitions, 2-19 Unreserving Partitions, 2-19 Updating Part Numbers in the PM Database, 3-68 Upgrading Central Libraries for Linux and UNIX Use, C-1
Index-11
Using a configuration (*.dbc) file (DxDatabook Data Editor), D-8 Using Design Architect with Expedition, B-1 Using DxDatabook Data Editor in Library Manager, D-1 Using File Viewer, 2-103 Using Library Services to Import Symbols, 2-25 Using lmcwin2unix, C-1 Using Modify Pins dialog box, 2-97 Using New Project Wizard, 4-3 Using Part Editor, 2-74 Using PM Batch Update Utility, 3-91 Using PM Validation Utility, 3-70 Using PM/PDB Synchronization Utility, 3-89 Using Symbol Wizard to create DxD symbols, F-2 Using the Libraries tab, 1-13 Using wildcard characters for object searches, 1-18 Viewing a central library flow type, 2-5 Viewing a model file, 2-95 Viewing associated objects in the Library Navigator Tree, 1-15 Viewing Attachment Data, 3-99 Viewing central library properties, 2-5 Viewing pad and hole associations in the workspace tree, 2-62 Viewing reusable block properties, 4-39 Viewing table properties (DxDatabook Data Editor), D-30 Process Editor, 5-12 Process Flows DC/DV-Expedition Library Manager, 1-9 DxD-Expedition Library Manager, 1-9 Project Editor dialog box, 4-18 Project Integration Dialog Box, 4-25 Project Search Path (DxD-Expedition Library Manager), 4-17 Project Settings Dialog Box, 4-5 Project Workspace Tree (Libraries tab), 1-13 Project Workspace Tree viewer, 1-12 Properties Dialog Box, 2-32, 2-73 Property Definition Editor, 2-11 Property Verification Settings, 2-12 Pushing Top Cell to Bottom Cell, 4-24, 4-32
R
Reducing Error Checking, 2-12 Reference Designator, 4-11, 4-33 Refresh Library Status icon, 2-24, 2-25 Refreshing the Display, 4-8 Removing Part Numbers from the PM Database, 3-33 Renaming a reusable block, 4-44 Central Library directories for Linux, C-1 Central Library directories for UNIX, C-1 Symbols via the workspace tree (Dx only), 2-52 Renaming Parametric Tables, 3-17 Reordering Partition Search Path Scheme, 2-18 Replace Cell Dialog Box, 4-33 Replacing Cells (Expedition PCB), 4-24, 4-33 Reserved Partitions, 2-14 Reusable Blocks, 4-35 Copying, 4-42 Deleting, 4-45 Editing, 4-42 Invoking the editor, 4-35 Logical/Physical type, 4-35 Renaming, 4-44 Viewing properties, 4-39 Reuse Subdirectory, 2-7 Route Swap Gates, 4-24 Running CDB Compiler on a DC/DV Schematic, 4-10
S
Saving a Design, 4-10 Schematic Compilation and Packaging (DC/DV), 4-10 Schematic Compilation and Packaging (DxDExpedition LM), F-14 Schematic workspace in DxDesigner, 4-19 Search Path Schemes, 2-17
Index-12
Searching for objects in the Project Workspace Tree, 1-12 for objects in the tree, 1-15 for objects in the workspace tree, 1-17 Padstack elements in the workspace tree, 2-63 Using wildcard characters, 1-18 Select Project File Dialog Box, 4-25 Select Script Language dialog box, 5-9, 5-11 Selecting a flow type when creating a central library, 2-3 Setting Fill color in Dx Symbol Editor, 2-42 PM Working Directory, 3-4 Precision for Electrical/Physical Properties, 2-20 Setting up in a Central Library, 2-14 Setup Command Partition Search Paths, 2-17 Property Verification, 2-12 Setup Parameters, 2-22 Units Display, 2-20 Unreserve Partitions, 2-19 Signal Analyzer, 5-3 Signal Vision, 5-3 Snap Grid Command, 2-72 Specifying Active Electrical Units Display, 2-20 Component Properties, 2-74 PCB Layout Template, 4-24 Standard automation interfaces, G-2 Subdirectories and Files of a Central Library, 2-6 Sub-gated parts (DxDesigner), E-32 Supporting heterogeneous symbols, E-1 Supporting mixed operating system usage, 1-5 Swap Gates Command, 4-27 Swapping Gates, 4-24, 4-27 Symbol Creation Wizard (DxDesigner), F-2 Symbol Editor, 2-29 Overview, 5-6 Symbol Placement, 4-6 Symbol Properties dialog box (DxDesigner), F-9 SymbolLibs Subdirectory, 2-7 Symbols Copying, 2-55 Deleting, 2-54 Heterogeneous, E-1 Moving, 2-55 Renaming (Dx only), 2-52 Symbols in a DxD schematic, 4-20 Synchronization Utility, 3-89 sysindex.cbf File, 2-7
T
Tables Adding Parameters, 3-8 Creating, 3-5 Inserting from an ASCII File, 3-24 Renaming, 3-17 Temp_Cell Partition, 2-24 Temp_Symbol Partition, 2-24 Templates, 5-2 Templating a Design, 5-1 tnsnames.ora file, D-2 Top Mount, 2-57 Trace Spacings, 5-2 Transferring data from DxD to Expedition PCB, F-16 Troubleshooting Finding objects in a central library, 1-17 Partitions in use while using Library Services, 2-24 Unreserving partitions in a central library, 2-19
U
Units Display Settings, 2-20 UNIX environment variable settings, 1-5 Unreserving Partitions, 2-14, 2-19 Updating Part Numbers in the PM Database, 3-68 Using Batch Update Utility, 3-79, 3-91 Cell Editor, 2-65 DxDatabook Data Editor in Library Manager, D-1 Expedition PCB, 4-24
Index-13
Find command in Library Navigator Tree, 1-17 IBIS functionality in Library Services, 5-6 IBIS functionality in Part Editor, 5-5 IBIS Models, 5-3 Libraries tab, 1-13 Library PDF Documenter, 5-8 Library Services, 2-23 New Project Wizard, 4-2 New Script Form dialog box, 5-9 Open Script Form dialog box, 5-11 Padstack Editor, 2-55 Part Editor, 2-74 Parts Manager Validation Utility, 3-70 PMPDB Synchronization Utility, 3-89 Project Workspace Tree, 1-13 Properties Command, 2-65 Symbol Wizard to create DxD symbols, F-2 Templates, 5-1 Utilities Library PDF Documenter, 5-8 Parts Manager Batch Update, 3-79, 3-91 Parts Manager Validation, 3-70 PM/PDB Synchronization, 3-89
W
WDIR variable, 1-4 Wildcard character strings used for searches, 1-18 Wizards Dx Symbol Creation, 2-37 DxDesigner Project Translation Wizard, A-14 DxDesigner to Library Manager Migration Wizard, A-1 Overview, A-1 Work Subdirectory, 2-7 Workflow DC/DV to Expedition Library Manager, 1-6 DxDesigner to Expedition Library Manager, 1-7 Working Directory, 3-4 Working Units, 2-20 Workspace to Create Schematic Designs, 4-5
Z
Zoom style, 4-16 Zooming, 2-68, 4-9, 4-11
V
Validation Utility, 3-70 Verification Settings, 2-12 Via, 5-7 View Refresh Command, 4-6 viewdraw.ini File, 2-8, 4-19 Viewing Associated objects, 1-15 Attachment Data, 3-99 Central library flow type, 2-5 Central library properties, 2-5 Model files, 2-95 Model types in the workspace tree, 2-90 Pad and hole associations, 2-62 Reports generated by Library Manager, 2-103 Reusable block properties, 4-39 ViewPCB dialog box, F-14 Visual IBIS Editor, 5-4
Index-14
End-User License Agreement

The latest version of the End-User License Agreement is available on-line at: www.mentor.com/terms_conditions/enduser.cfm IMPORTANT INFORMATION USE OF THIS SOFTWARE IS SUBJECT TO LICENSE RESTRICTIONS. CAREFULLY READ THIS LICENSE AGREEMENT BEFORE USING THE SOFTWARE. USE OF SOFTWARE INDICATES YOUR 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 between you, the end user, as an authorized representative of the company acquiring the license, and Mentor Graphics Corporation and Mentor Graphics (Ireland) Limited acting directly or through their subsidiaries (collectively Mentor Graphics). Except for license agreements related to the subject matter of this license agreement which are physically signed by you 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 you do not agree to these terms and conditions, promptly return or, if 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. GRANT OF LICENSE. The software programs, including any updates, modifications, revisions, copies, documentation 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. Mentor Graphics grants to you, subject to payment of appropriate license fees, a nontransferable, nonexclusive license to use Software solely: (a) in machine-readable, object-code form; (b) for your internal business purposes; (c) for the license term; 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. 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. EMBEDDED SOFTWARE. If you purchased a license to use embedded software development (ESD) Software, if applicable, Mentor Graphics grants to you a nontransferable, nonexclusive license to reproduce and distribute executable files created using ESD compilers, including the ESD run-time libraries distributed with ESD C and C++ compiler Software that are linked into a composite program as an integral part of your compiled computer program, provided that you distribute these files only in conjunction with your compiled computer program. Mentor Graphics does NOT grant you any right to duplicate, incorporate or embed copies of Mentor Graphics' real-time operating systems or other embedded software products into your products or applications without first signing or otherwise agreeing to a separate agreement with Mentor Graphics for such purpose. BETA CODE. Software may contain code for experimental testing and evaluation (Beta Code), which may not be used without Mentor Graphics explicit authorization. Upon Mentor Graphics authorization, Mentor Graphics grants to you 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. This grant and your use of the Beta Code shall not be construed as marketing or offering to sell a license to the Beta Code, which Mentor Graphics may choose not to release commercially in any form. If Mentor Graphics authorizes you to use the Beta Code, you agree to evaluate and test the Beta Code under normal conditions as directed by Mentor Graphics. You will contact Mentor Graphics periodically during your use of the Beta Code to discuss any malfunctions or suggested improvements. Upon completion of your evaluation and testing, you will send to Mentor Graphics a written evaluation of the Beta Code, including its strengths, weaknesses and recommended improvements. You agree 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 your 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 section 3 shall survive the termination or expiration of this Agreement.
2.
3.
4.
RESTRICTIONS ON USE. You 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. You 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. You shall not make Software available in any form to any person other than employees and on-site contractors, excluding Mentor Graphics' competitors, whose job performance requires access and who are under obligations of confidentiality. You shall take appropriate action to protect the confidentiality of Software and ensure that any person permitted access to Software does not disclose it or use it except as permitted by this Agreement. Except as otherwise permitted for purposes of interoperability as specified by applicable and mandatory local law, you shall not reverse-assemble, reverse-compile, reverse-engineer or in any way derive from Software any source code. You may not sublicense, assign or otherwise transfer Software, this Agreement or the rights under it, whether by operation of law or otherwise (attempted transfer), without Mentor Graphics prior written consent and payment of Mentor Graphics then-current applicable transfer charges. 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 licenses granted under this Agreement. The terms of this Agreement, including without limitation, the licensing and assignment provisions shall be binding upon your successors in interest and assigns. The provisions of this section 4 shall survive the termination or expiration of this Agreement. LIMITED WARRANTY. 5.1. Mentor Graphics warrants that during the warranty period Software, when properly installed, will substantially conform to the functional specifications set forth in the applicable user manual. Mentor Graphics does not warrant that Software will meet your requirements or that operation of Software 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. You must notify Mentor Graphics in writing of any nonconformity within the warranty period. This warranty shall not be valid if Software has been subject to misuse, unauthorized modification or improper installation. MENTOR GRAPHICS' ENTIRE LIABILITY AND YOUR EXCLUSIVE REMEDY SHALL BE, AT MENTOR GRAPHICS' OPTION, EITHER (A) REFUND OF THE PRICE PAID UPON RETURN OF SOFTWARE TO MENTOR GRAPHICS OR (B) MODIFICATION OR REPLACEMENT OF SOFTWARE THAT DOES NOT MEET THIS LIMITED WARRANTY, PROVIDED YOU HAVE OTHERWISE COMPLIED WITH THIS AGREEMENT. MENTOR GRAPHICS MAKES NO WARRANTIES WITH RESPECT TO: (A) SERVICES; (B) SOFTWARE WHICH IS LICENSED TO YOU FOR A LIMITED TERM OR LICENSED AT NO COST; OR (C) EXPERIMENTAL BETA CODE; ALL OF WHICH ARE PROVIDED AS IS. 5.2. THE WARRANTIES SET FORTH IN THIS SECTION 5 ARE EXCLUSIVE. NEITHER MENTOR GRAPHICS NOR ITS LICENSORS MAKE ANY OTHER WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, WITH RESPECT TO SOFTWARE OR OTHER MATERIAL PROVIDED UNDER THIS AGREEMENT. MENTOR GRAPHICS AND ITS LICENSORS SPECIFICALLY DISCLAIM ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT OF INTELLECTUAL PROPERTY.
5.
6.
LIMITATION OF LIABILITY. EXCEPT WHERE THIS EXCLUSION OR RESTRICTION OF LIABILITY WOULD BE VOID OR INEFFECTIVE 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 PAID BY YOU FOR THE SOFTWARE 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 6 SHALL SURVIVE THE EXPIRATION OR TERMINATION OF THIS AGREEMENT. LIFE ENDANGERING ACTIVITIES. NEITHER MENTOR GRAPHICS NOR ITS LICENSORS SHALL BE LIABLE FOR ANY DAMAGES RESULTING FROM OR IN CONNECTION WITH THE USE OF SOFTWARE IN ANY APPLICATION WHERE THE FAILURE OR INACCURACY OF THE SOFTWARE MIGHT RESULT IN DEATH OR PERSONAL INJURY. THE PROVISIONS OF THIS SECTION 7 SHALL SURVIVE THE EXPIRATION OR TERMINATION OF THIS AGREEMENT. INDEMNIFICATION. YOU AGREE TO INDEMNIFY AND HOLD HARMLESS MENTOR GRAPHICS AND ITS LICENSORS FROM ANY CLAIMS, LOSS, COST, DAMAGE, EXPENSE, OR LIABILITY, INCLUDING ATTORNEYS' FEES, ARISING OUT OF OR IN CONNECTION WITH YOUR USE OF SOFTWARE AS
7.
8.
DESCRIBED IN SECTION 7. THE PROVISIONS OF THIS SECTION 8 SHALL SURVIVE THE EXPIRATION OR TERMINATION OF THIS AGREEMENT. 9. INFRINGEMENT. 9.1. Mentor Graphics will defend or settle, at its option and expense, any action brought against you alleging that Software infringes a patent or copyright or misappropriates a trade secret in the United States, Canada, Japan, or member state of the European Patent Office. Mentor Graphics will pay any costs and damages finally awarded against you that are attributable to the infringement action. You understand and agree that as conditions to Mentor Graphics' obligations under this section you must: (a) notify Mentor Graphics promptly in writing of the action; (b) provide Mentor Graphics all reasonable information and assistance to defend or settle the action; and (c) grant Mentor Graphics sole authority and control of the defense or settlement of the action. 9.2. If an infringement claim is made, Mentor Graphics may, at its option and expense: (a) replace or modify Software so that it becomes noninfringing; (b) procure for you the right to continue using Software; or (c) require the return of Software and refund to you any license fee paid, less a reasonable allowance for use. 9.3. Mentor Graphics has no liability to you if infringement is based upon: (a) the combination of Software with any product not furnished by Mentor Graphics; (b) the modification of Software other than by Mentor Graphics; (c) the use of other than a current unaltered release of Software; (d) the use of Software as part of an infringing process; (e) a product that you make, use or sell; (f) any Beta Code contained in Software; (g) any Software provided by Mentor Graphics licensors who do not provide such indemnification to Mentor Graphics customers; or (h) infringement by you that is deemed willful. In the case of (h) you shall reimburse Mentor Graphics for its attorney fees and other costs related to the action upon a final judgment. 9.4. THIS SECTION IS SUBJECT TO SECTION 6 ABOVE AND STATES THE ENTIRE LIABILITY OF MENTOR GRAPHICS AND ITS LICENSORS AND YOUR SOLE AND EXCLUSIVE REMEDY WITH RESPECT TO ANY ALLEGED PATENT OR COPYRIGHT INFRINGEMENT OR TRADE SECRET MISAPPROPRIATION BY ANY SOFTWARE LICENSED UNDER THIS AGREEMENT. 10. TERM. This Agreement remains effective until expiration or termination. This Agreement will immediately terminate upon notice if you exceed the scope of license granted or otherwise fail to comply with the provisions of Sections 1, 2, or 4. For any other material breach under this Agreement, Mentor Graphics may terminate this Agreement upon 30 days written notice if you are in material breach and fail to cure such breach within the 30 day notice period. If Software was provided for limited term use, this Agreement will automatically expire at the end of the authorized term. Upon any termination or expiration, you agree to cease all use of Software and return it to Mentor Graphics or certify deletion and destruction of Software, including all copies, to Mentor Graphics reasonable satisfaction. 11. EXPORT. Software is subject to regulation by local laws and United States government agencies, which prohibit export or diversion of certain products, information about the products, and direct products of the products to certain countries and certain persons. You agree that you will not export any Software or direct product of Software in any manner without first obtaining all necessary approval from appropriate local and United States government agencies. 12. RESTRICTED RIGHTS NOTICE. Software was developed entirely at private expense and is commercial computer software provided with RESTRICTED RIGHTS. Use, duplication or disclosure by the U.S. Government or a U.S. Government subcontractor is subject to the restrictions set forth in the license agreement under which Software was obtained pursuant to DFARS 227.7202-3(a) or as set forth in subparagraphs (c)(1) and (2) of the Commercial Computer Software - Restricted Rights clause at FAR 52.227-19, as applicable. Contractor/manufacturer is Mentor Graphics Corporation, 8005 SW Boeckman Road, Wilsonville, Oregon 97070-7777 USA. 13. THIRD PARTY BENEFICIARY. For any Software under this Agreement licensed by Mentor Graphics from Microsoft or other licensors, Microsoft or the applicable licensor is a third party beneficiary of this Agreement with the right to enforce the obligations set forth herein. 14. AUDIT RIGHTS. You will monitor access to, location and use of Software. With reasonable prior notice and during your normal business hours, Mentor Graphics shall have the right to review your software monitoring system and reasonably relevant records to confirm your compliance with the terms of this Agreement, an addendum to this Agreement or U.S. or other local export laws. Such review may include FLEXlm or FLEXnet report log files that you shall capture and provide at Mentor Graphics request. Mentor Graphics shall treat as confidential information all of your 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 or addendum to this Agreement. The provisions of this section 14 shall survive the expiration or termination of this Agreement.
15. CONTROLLING LAW, JURISDICTION AND DISPUTE RESOLUTION. THIS AGREEMENT SHALL BE GOVERNED BY AND CONSTRUED UNDER THE LAWS OF THE STATE OF OREGON, USA, IF YOU ARE LOCATED IN NORTH OR SOUTH AMERICA, AND THE LAWS OF IRELAND IF YOU ARE LOCATED OUTSIDE OF NORTH OR SOUTH AMERICA. All disputes arising out of or in relation to this Agreement shall be submitted to the exclusive jurisdiction of Portland, Oregon when the laws of Oregon apply, or Dublin, Ireland when the laws of Ireland apply. Notwithstanding the foregoing, all disputes in Asia (except for 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 15. This section shall not restrict Mentor Graphics right to bring an action against you in the jurisdiction where your place of business is located. The United Nations Convention on Contracts for the International Sale of Goods does not apply to this Agreement. 16. 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. 17. PAYMENT TERMS AND MISCELLANEOUS. You will pay amounts invoiced, 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. Some Software may contain code distributed under a third party license agreement that may provide additional rights to you. Please see the applicable Software documentation for details. This Agreement may only be modified in writing by authorized representatives of the parties. Waiver of terms or excuse of breach must be in writing and shall not constitute subsequent consent, waiver or excuse. Rev. 060210, Part No. 227900

LM Proc GD

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

LM Proc GD

Загружено:

Авторское право:

Доступные форматы

Library ManagerTM Process Guide

Copyright Mentor Graphics Corporation 2005 - 2006 All rights reserved.

Library Manager Process Guide, EXP2005 SPac1

Library Manager Process Guide, EXP2005 SPac1

Library Manager Process Guide, EXP2005 SPac1

Library Manager Process Guide, EXP2005 SPac1

Library Manager Process Guide, EXP2005 SPac1

Library Manager Process Guide, EXP2005 SPac1

Library Manager Process Guide, EXP2005 SPac1

Library Manager Process Guide, EXP2005 SPac1

Library Manager Process Guide, EXP2005 SPac1

Library Manager Process Guide, EXP2005 SPac1

Library Manager Process Guide, EXP2005 SPac1

Library Manager Process Guide, EXP2005 SPac1

Library Manager Process Guide, EXP2005 SPac1

Library Manager Process Guide, EXP2005 SPac1

Library Manager Process Guide, EXP2005 SPac1

Library Manager Process Guide, EXP2005 SPac1

Chapter 1 Library Manager Overview

Library Manager Process Guide, EXP2005 SPac1

Library Manager Overview Production Flows Supported by Library Manager

Production Flows Supported by Library Manager

Library Manager Process Guide, EXP2005 SPac1

Library Manager Overview What is a Central Library?

What is a Central Library?

Accessing a Central Library

Library Manager Process Guide, EXP2005 SPac1

Library Manager Overview Prerequisites

Configuring the WDIR Variable on Windows

Adjusting Central Libraries for Use on Linux and UNIX

Library Manager Process Guide, EXP2005 SPac1

Library Manager Overview Prerequisites

Supported Operating Systems

Supporting Mixed Operating System Usage

Configuring Linux and UNIX Workstations

Library Manager Process Guide, EXP2005 SPac1

Library Manager Overview DC/DV to Expedition PCB Flow

Recommended Central Library Permissions

DC/DV to Expedition PCB Flow

Library Manager Process Guide, EXP2005 SPac1

Library Manager Overview DxDesigner to Expedition Library Manager Flow

Figure 1-1. DC/DV to Expedition Library Manager Design Flow

DxDesigner to Expedition Library Manager Flow

Library Manager Process Guide, EXP2005 SPac1

Library Manager Overview Process Flows

Figure 1-2. DxDesigner to Expedition Library Manager Flow

Library Manager Process Guide, EXP2005 SPac1

Library Manager Overview Process Flows

Figure 1-4 illustrates the DxD-Expedition Library Manager usage flow:

Library Manager Process Guide, EXP2005 SPac1

Library Manager Overview Process Flows

Figure 1-4. DxD-Expedition Flow Using Library Manager

Library Manager Process Guide, EXP2005 SPac1

Library Manager Overview Using the Library Manager Interface

Using the Library Manager Interface

Library Manager Process Guide, EXP2005 SPac1

Library Manager Overview Project Workspace Tree Viewer

Project Workspace Tree Viewer

Library Manager Process Guide, EXP2005 SPac1

Viewing Central Library Properties

Using the Libraries Tab (Project Workspace Tree)

Library Manager Process Guide, EXP2005 SPac1