Logic
Logic
Release 2015.1
February 2016
This document contains information that is proprietary to Mentor Graphics Corporation. The original recipient of this
document may duplicate this document in whole or in part for internal business purposes only, provided that this entire
notice appears in all copies. In duplicating any part of this document, the recipient agrees to make every reasonable
effort to prevent the unauthorized use and distribution of the proprietary information.
This document is for information and instruction purposes. Mentor Graphics reserves the right to make
changes in specifications and other information contained in this publication without prior notice, and the
reader should, in all cases, consult Mentor Graphics to determine whether any changes have been
made.
The terms and conditions governing the sale and licensing of Mentor Graphics products are set forth in
written agreements between Mentor Graphics and its customers. No representation or other affirmation
of fact contained in this publication shall be deemed to be a warranty or give rise to any liability of Mentor
Graphics whatsoever.
MENTOR GRAPHICS MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE.
MENTOR GRAPHICS SHALL NOT BE LIABLE FOR ANY INCIDENTAL, INDIRECT, SPECIAL, OR
CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING BUT NOT LIMITED TO LOST PROFITS)
ARISING OUT OF OR RELATED TO THIS PUBLICATION OR THE INFORMATION CONTAINED IN IT,
EVEN IF MENTOR GRAPHICS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
U.S. GOVERNMENT LICENSE RIGHTS: The software and documentation were developed entirely at
private expense and are commercial computer software and commercial computer software
documentation within the meaning of the applicable acquisition regulations. Accordingly, pursuant to
FAR 48 CFR 12.212 and DFARS 48 CFR 227.7202, use, duplication and disclosure by or for the U.S.
Government or a U.S. Government subcontractor is subject solely to the terms and conditions set forth in
the license agreement provided with the software, except for provisions which are contrary to applicable
mandatory federal laws.
TRADEMARKS: The trademarks, logos and service marks ("Marks") used herein are the property of
Mentor Graphics Corporation or other parties. No one is permitted to use these Marks without the prior
written consent of Mentor Graphics or the owner of the Mark, as applicable. The use herein of a third-
party Mark is not an attempt to indicate Mentor Graphics as a source of a product, but is intended to
indicate a product from, or associated with, a particular third party. A current list of Mentor Graphics’
trademarks may be viewed at: www.mentor.com/trademarks.
The registered trademark Linux® is used pursuant to a sublicense from LMI, the exclusive licensee of
Linus Torvalds, owner of the mark on a world-wide basis.
Chapter 1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Reporting on a Project's Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
User Access Rights in Capital Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Object Model Integrity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Launching Capital Library from this Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Launching Capital Symbol from this Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Video Live Drive - Interactive Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Video Test Drive - Aerospace and Toplogy Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Diagram Language Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Engineering Change Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Chapter 2
Projects and Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Project Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Opening a Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Creating a Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Editing the Attributes and Properties of a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Deleting a Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Importing a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Exporting a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Closing a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Applying Scopes to a Project or Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Project-Related Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Edit Project Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Edit Properties Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
New Project Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Open Project Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Project Folders Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Build Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Editing the Information for a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Deleting a Design. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Importing a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Adding a Property to a Design. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Editing a Property for a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Deleting a Property for a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Properties Dialog Box and Field References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Edit Design Properties Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
New Property Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Saving the Designs in a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Setting an Active Build List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Chapter 3
Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Creating a New Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Editing the Properties of a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Editing the Name of a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Adding a Property to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Deleting a Property From a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Deleting a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Filtering the Objects Displayed in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Effects of Filtering on Object Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Moving Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Moving Objects from a Diagram to Another Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Adding a Diagram List Table to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Adding a Device List Table to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Changing the Background Color of a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Closing a Diagram Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Deleting an Object from a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Selecting Objects in a Diagram Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Specifying the Highlight Color of Selected Objects in a Diagram. . . . . . . . . . . . . . . . . . . 128
Slice Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Copying Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Editing Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Multiple Selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Undoing an Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Chapter 4
Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Adding Pins to an Object Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Usage Example - Preventing Pin Duplication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Adding Pins to an Instance of a Shared Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Moving a Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Disconnecting a Conductor from a Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Overview of Reference Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Cross-reference Rules for Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Converting a Non-reference Instance of a Pin to a Reference Instance . . . . . . . . . . . . . . . 153
Converting a Reference Instance of a Pin to a Non-reference Instance . . . . . . . . . . . . . . . 153
Connecting Selected Overlapping Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Connecting Selected Pins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Stacked Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Creating a Stack of Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Adding a Pin to a Pin Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Removing a Pin from a Pin Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Viewing the Pins in a Pin Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Deleting a Stack of Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Viewing the Highway Conductors that Terminate at Stacked Pins . . . . . . . . . . . . . . . . . . 164
Edit Stack Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Usages Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Usage Examples - Stacked Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Chapter 5
Devices and Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Creating a Device in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Adding a Device from Capital Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Preserving Connectivity and Assisting Object Placement. . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Preserving Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Preserving Imported Connectivity and Using Assisted Placement . . . . . . . . . . . . . . . . . . 184
Adding a Shared Device/Connector/Splice to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Adding a Shared Device, Plug, Receptacle, Ring Terminal, or Inline Connector to a Diagram
187
Adding a Shared Splice to a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Editing Shared Devices and Shared Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Joining Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Associating a Symbol with a Shared Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Removing the Association Between a Symbol and a Shared Object . . . . . . . . . . . . . . . . . 194
Adding a Pin to a Shared Pin List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Removing a Pin from a Shared Pin List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Renaming a Pin in a Shared Pin List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Converting a Reserved Pin to an Unrestricted Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Converting an Unrestricted Pin to an Automatic Reservation Pin . . . . . . . . . . . . . . . . . . . 196
Creating a New Revision of a Shared Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Creating a Revision of a Shared Object in Capital Logic. . . . . . . . . . . . . . . . . . . . . . . . . . 197
Swapping Out Shared Objects for a Compatible Revision . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Cross-References on Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Cross-References and Composite Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Setting up Project Preferences for Cross-references. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Viewing Another Instance of an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Changing the Home Instances of an Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Changing an Instance of an Object to a Home Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Changing a Home Instance of an Object to a Normal Instance . . . . . . . . . . . . . . . . . . . . . 204
Promoting a Device/Connector/Modular Connector/Ring Terminal/Splice to a Shared Object
206
Promoting a Device/Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Promoting a Splice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Creating a Shared Device Based on a Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Deleting Multiple Unused Shared Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Deleting a Single Unused Shared Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Implementing Ground Wiring in the Generative Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Resizing a Device or Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Resizing a Device or Connector Using the Resize Option . . . . . . . . . . . . . . . . . . . . . . . . . 213
Chapter 6
Design Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Design Hierarchy Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Adding a Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Associating a Block with a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Removing an Association Between a Block and a Design . . . . . . . . . . . . . . . . . . . . . . . . . 248
Creating New Instances of a Block. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Viewing Items Related to the Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Adding Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Viewing the Connectivity that Terminates at Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Merging Block Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Adding Pins to a Block Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Chapter 7
Wires, Conductors and Nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Creating a Conductor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Creating/Moving/Deleting a Wire Conductor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Creating a Wire Conductor in a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Moving a Wire Conductor in a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Merging Wire Conductors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Deleting a Wire Conductor from a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Creating/Moving/Deleting a Net Conductor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Creating a Net Conductor in a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Modifying a Net Conductor in a Design. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Merging Net Conductors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Adding Multiple Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Deleting a Net Conductor from a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Creating a Notch to Move a Subsegment of a Conductor . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Disconnecting and Moving a Conductor End from a Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Poke Home Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Specifying a Poke Home Wire in Capital Logic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Routing Conductors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Using Orthogonal Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Auto-routing of Nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Auto-routing of Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Promoting a Conductor to a Shared Conductor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Creating a Splice in Capital Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Creating a Single Pin Splice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Adding a Splice with a Library Part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Converting a Butt Splice to a Center Strip Splice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Converting a Center Strip Splice to a Butt Splice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Automatic Splice Creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Overview of Multicores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Overview of Overbraids. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Creating a Multicore or Overbraid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Creating a Multicore or Overbraid Without a Library Part in a Diagram . . . . . . . . . . . . . 282
Creating a Multicore with a Library Part in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Splitting Multicore Indicators and Overbraid Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Associating a Comment Symbol with a Multicore or Overbraid Indicator . . . . . . . . . . . . . . 288
Replacing a Multicore or Overbraid Indicator with a Comment Symbol . . . . . . . . . . . . . . . 289
Using Add Wire to Terminate a Wire at a Multicore or Overbraid. . . . . . . . . . . . . . . . . . . . 290
Promoting a Multicore or Overbraid to a Shared Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Adding a Shared Conductor to a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Overview of Shared Net Conductor Equivalence Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
Creating a Shared Multicore or Overbraid in Capital Logic . . . . . . . . . . . . . . . . . . . . . . . . . 293
Adding a Shared Multicore to a Design. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Creating a Shield Terminator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Chapter 8
Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Adding a Symbol to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Adding a Symbol to a Diagram as a Non-Intelligent Graphical Shape . . . . . . . . . . . . . . . . . 336
Updating Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Composite Symbol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Updating a Symbol Block in a Composite Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Replacing Composite Symbols for Shared Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Replacing a Symbol with a Compatible Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Saving Diagram Objects as a Device Symbol (Bookshelf Circuit) . . . . . . . . . . . . . . . . . . . . 341
Help Button Landing Pages for Symbols Dialog Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Chapter 9
Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
Available Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
Chapter 10
Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Generating Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Reporting on Single Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Reporting on a Build List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Saving a Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
Printing a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
Available Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Assembly BOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Component BOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Custom Logic Wire List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
Multicore List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
Net List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
Shared Object Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
Wire List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Configured Wire List Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Using the Report Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Custom Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Chapter 11
Graphics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Borders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Adding a Border to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Replacing a Border on a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Removing a Border from a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Graphic Drawing Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
Drawing a Line in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
Drawing a Rectangle in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Drawing a Polygon in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Drawing a Circle in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
Drawing an Arc in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
Drawing a Curved Line in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
Adding Text Frames to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Adding a Picture to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Changing the Picture in an Image Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Adding a Comment Symbol to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
Resizing a Comment Symbol in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
Adding Properties to a Graphical Shape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
Editing a Property Value of Graphical Shape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
Chapter 12
Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Grouping Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Aligning Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Distributing Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
Flipping Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
Rotating Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
Defining Rotation Increments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
Free Rotation of an Object or Comment Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
Pivoting Text about its Axis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Setting Snap To Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Setting Grid Defaults for a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Manual Table Splitting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Using Japanese Text on a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
Usage Example - Displaying Wire Color Information in Diagrams . . . . . . . . . . . . . . . . . . . 400
Chapter 13
Modifying Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Editing the Properties of Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Editing an Object's General Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Chapter 14
Rules and Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
Rules and Constraints Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
Defining a Constraint for a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
Defining Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
Referencing another Rule in a Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
Adding Rules to a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
Using a Constraint to Set Properties and Attributes on Objects . . . . . . . . . . . . . . . . . . . . . . 475
Chapter 15
Interface Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
Extending a Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
The Application Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
Ribbon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
Project Browser Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
Design Browser Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
Symbol Browser Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
Parts Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
Shared Objects Browser Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
ICD Browser Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
Placing ICDs in Capital Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
Placing ICDs Containing Shared Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
Refreshing ICDs in Capital Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Viewing ICD Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Diagram Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
Output Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
Chapter 16
Capital AutoView Assist for Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
Overview of Capital AutoView Assist for Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
Generating Diagrams for a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
Generating Filtered Diagrams for a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
Importing a Project and Generating Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
Generating a Design and Diagrams for Filtered Connectivity from Multiple Designs . . . . . 503
Specifying Layout Styling when Generating Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
Capital AutoView Assist for Logic Dialog Boxes and Field References . . . . . . . . . . . . . . . 515
AutoView Diagram Generator - Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
AutoView Diagram Generator Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
New Generated Diagrams - Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
New Generated Diagrams Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
New Diagram - Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
New Diagram Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
Edit Diagram - Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
Edit Diagram Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
Selection Preview - Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
Selection Preview Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
Import Project and Generate Diagrams - Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
Import Project and Generate Diagrams Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
AutoView Style Editor Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
AutoView: Query and Generate Design Dialog - Help . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
AutoView: Query and Generate Design Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
Parent Folder Selection Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Parent Folder Selection Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
Chapter 17
Capital Topology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
Capital Topology Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
Enabling Capital Topology Functionality in Capital Logic. . . . . . . . . . . . . . . . . . . . . . . . . . 550
Video Test Drive - Aerospace and Topology Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
High-Level Flow for Using Capital Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
Styling Objects (Capital Topology) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
Harness Concurrency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
Topology Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558
Creating a Capital Topology Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558
Editing a Capital Topology Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
Deleting a Capital Topology Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
Logical Design Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
Build List Association (Managed Mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
Associating Logical Designs with the Topological Design . . . . . . . . . . . . . . . . . . . . . . . . 561
Replacing a Logical Design Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
Wires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
Constraining the Routing of Wires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
Using the Routing Assistant to Identify the Possible Routes for an Unrouted Wire . . . . . 604
Using the Routing Assistant to Identify all Unrouted Wires that Need to Pass Through a
Selected Inline Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
Reporting on All Unrouted Wires that Could Pass Through an Inline Connector . . . . . . . 607
Viewing the Attributes and Properties of a Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
Updating Wire Lengths. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
Annotating Topology Wire Lengths and Harness Attributes Back to Logical Wires and Splices
608
Multicores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
Viewing the Attributes and Properties of a Multicore . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
Splices in Capital Topology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611
Specifying the Harness Attribute for a Splice in Capital Topology . . . . . . . . . . . . . . . . . . 611
Inline Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613
Adding an Unassociated Inline Pair to a Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613
Adding a Specific Logical Inline Pair to a Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614
Editing an Inline Plug Connector or an Inline Receptacle Connector . . . . . . . . . . . . . . . . 615
Specifying a Route Code for an Inline Plug Connector or an Inline Receptacle Connector 616
Moving an Inline Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
Deleting an Inline Pair from a Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
Toggling the Inline Plug Connector and Inline Receptacle Connector on an Inline Pair. . 618
Constraining the Automatic Association of Inline Halves . . . . . . . . . . . . . . . . . . . . . . . . . 618
Viewing the Signal Map for an Inline Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
Virtual Harnesses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621
Editing a Virtual Harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621
Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
Grouping Wires into Signals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
Usage Example for Grouping Wires into Signals in Capital Topology . . . . . . . . . . . . . . . 623
Holes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
Adding a Hole to a Slot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
Editing a Hole . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
Constraining the Mapping of Wires to a Hole on a Slot. . . . . . . . . . . . . . . . . . . . . . . . . . . 626
Assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628
Viewing the Attributes and Properties for an Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . 628
Constraints (Capital Topology) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629
Standard Constraints for Capital Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629
Setting Constraints for an Entire Topology Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
Using a Constraint to Set an Attribute or Property on an Object . . . . . . . . . . . . . . . . . . . . 632
Applying the Set Topology Attribute/Property on Object Constraint . . . . . . . . . . . . . . . . 633
Reports (Capital Topology) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634
Harness Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634
Creating a Harness Report for a Topology Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634
Material Statistics Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
Creating a Material Statistic Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
Bundle Wires Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
Creating a Bundle Wires Report for a Bundle Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636
Copying the Bundle Wires Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636
Clearing the Bundle Wires Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
Chapter 18
Bridges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
Bridges Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
Chapter 19
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
Troubleshooting Shared Multicores. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
Index
Third-Party Information
End-User License Agreement
This following sections provide an introduction and overview to using Capital Logic.
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Reporting on a Project's Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
User Access Rights in Capital Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Object Model Integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Launching Capital Library from this Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Launching Capital Symbol from this Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Video Live Drive - Interactive Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Video Test Drive - Aerospace and Toplogy Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Diagram Language Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Engineering Change Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Introduction
Capital Logic is the application that is used to create electrical schematic diagrams for a
project's designs.
A project is usually an automotive or aerospace product line. Projects are top-level 'containers'
for all of the harness designs and data that comprise a specific product line.
Once created, a project can have data added from many of the Capital applications.
The information that is contained within a project is arranged into distinct 'sub-containers'
called Designs. Designs are versional data containers that can have their contents copied as
required. A design is usually created for each sub-system of a product line and contains the
schematic diagrams created in Capital Logic. Designs can be created for a project using Capital
Project.
The following diagram displays the hierarchical relationship between projects, designs and
diagrams.
Once created in Capital Project, a project can be opened into Capital Logic and the required
schematic diagrams created for the designs within that project. The Open Project facility in
Capital Logic, displays the same project list as that in Capital Project (unless project access
restrictions have been imposed on the user using the Capital User application).
Only one user can access a design at a time. If another user needs to access a diagram in the
same design, the first user must close the design.
When a logical design is complete, it can be imported into Capital Harness & Factory where the
data can be used to manufacture harnesses. See the Capital Engineer help system for more
information on accessing Capital Logic designs from Capital Engineer.
The electrical symbols used on the Capital Logic schematic diagrams can be created as required
using the Capital Symbol application.
Note
Capital Logic can be accessed from the Capital Launcher by selecting Capital Logic.
Alternatively, you can select the Capital Design option from the Capital Launcher. The Capital
Design application allows the user to access both Capital Logic designs and Capital Integrator
designs from the same window.
Opening Capital Design will check out a Capital Logic and a Capital Integrator license.
When using Capital Design, you must open a Capital Logic diagram to access the menu options
and functionality for Capital Logic. You must open a Capital Integrator diagram to access the
menu options and functionality for Capital Integrator.
The level of validation is specified in the clientprops.xml file, located in the config sub-directory
of your Capital install directory.
<validation level=”VALUE”/>
• failureStopsValidation
o false - if a validation failure has been detected, validation will continue to be
performed.
o true - if a validation failure has been detected, validation will no longer be
performed.
• failureStopsExportValidation
o false - if a validation failure has been detected, validation will not be performed on
export operations, thus allowing customers to export projects with invalid data to us.
o true - if a validation failure has been detected, validation will be performed on export
operations.
• exceptionIncreasesLevel
o false - if an exception has been raised anywhere in the code, the validation level will
remain the same.
o true - if an exception has been raised anywhere in the code, the validation level will
be increased once (from LOW to MEDIUM, or MEDIUM to HIGH).
• exceptionTriggersValidation
o false - when the validation is set to LOW, any exceptions will not force a validation.
o true - when the validation level is set to LOW, any exception encountered will
trigger a validation at level HIGH.
Note
None, any or all of the optional attributes can be added to the validation level
statement, with each attribute being separated by a space.
One way to access the Mentor Learning Center is clicking the On Demand Training symbol on
the launch pane visible in a Capital application when no diagram is open.
This following sections explain how to open, create, edit and delete projects from within the
application.
Project Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Opening a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Creating a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Editing the Attributes and Properties of a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Deleting a Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Importing a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Exporting a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Closing a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Applying Scopes to a Project or Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Project-Related Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Edit Project Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Edit Properties Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
New Project Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Open Project Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Project Folders Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Build Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Editing the Information for a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Deleting a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Importing a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Adding a Property to a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Editing a Property for a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Deleting a Property for a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Properties Dialog Box and Field References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Edit Design Properties Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
New Property Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Saving the Designs in a Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Setting an Active Build List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Setting an Active Build List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Selecting an Alternative Build List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Creating a New Capital Logic Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Copying a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Creating a Revision of a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Specifying the Applicable Options for a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Comparing Objects and Their Properties in Design Revisions or Build Lists. . . . . . . . 61
Mapping Equivalent Devices During Design Comparison . . . . . . . . . . . . . . . . . . . . . . . 63
Running Design Rule Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Design Rule Checks Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Design Rule Checks Output Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Design Rule Check Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Styling Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Project Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Refreshing External Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Managing Design Changes When Synchronizing Designs . . . . . . . . . . . . . . . . . . . . . . . . 70
Extensibility Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Releasing a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Functional Module Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Definition and Management of Module Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Assignation of Module Codes to Capital Logic Designs . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Assignation of Module Codes to Capital Logic Components . . . . . . . . . . . . . . . . . . . . . . 72
Purge Functional Module Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Options and Option Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Creating an Option Folder at Project Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Creating an Option at Project Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Defining Inclusive and Exclusive Relationships for an Option . . . . . . . . . . . . . . . . . . . . . 75
Creating an Option Combination at Project Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Adding a Valid Selection to an Option Combination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Deleting a Valid Selection from an Option Combination. . . . . . . . . . . . . . . . . . . . . . . . . . 78
Deleting an Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Options Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Choose Options Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Design Wide Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Deleting Design Wide Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Merging of Design Wide Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Example Flow for Using Design Wide Objects to Create a Contactor Configuration . . . . 87
Adding an Instance of a Design Wide Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Place Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Merging Instances of Design Wide Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Merge Into Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Finding Which Designs Use a Shared Object Revision . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Shared Object Usages Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Reporting on Shared Object Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Help Button Landing Pages for Project and Designs Dialog Boxes . . . . . . . . . . . . . . . . 95
Edit Project Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Edit Project Properties Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
New Project Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Open Project Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Project Folders Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Edit Design Properties Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
New Property Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Edit Effectivity Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Edit Effectivity Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Copy Design Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Copy Design Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Create New Design Revision Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Create New Design Revision Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Applicable Options Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Applicable Options Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Edit Option Expression Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Edit Option Expression Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Design Revision/Build List Selection Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Design Revision/Build List Selection Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Compare Designs Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Compare Designs Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Design Rules Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Options Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Choose Options Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Place Design Wide Object Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Merge Into Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Shared Object Usages Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Project Browser
The Project Browser is located on the upper left side of the application window. It contains the
following:
• Close Project ( ) button
In the field next to the Enter Filter String icon ( ), enter a series of characters. A filter
is applied to the Project browser tree so that only designs with names containing that
series of characters are listed. If you want to use a regular expression character, such as a
bracket, in the filter, you must prefix it with \. For example, \(P.
Click the Clear Filter String icon ( ) to clear the filter and view all designs in the
project.
• Design Filter ( )
Click the dropdown list to filter the designs displayed in the Project browser tree
window to those of a particular type, all designs in the project or all designs in the
currently active build list.
Related Topics
Opening a Project
Creating a Project
Deleting a Project
Importing a Project
Exporting a Project
Closing a Project
Opening a Project
This topic explains how to open an existing project.
Procedure
1. Press Space Bar and enter Open.
The Open Project Dialog is displayed.
2. Click the project that you want to open and click OK.
The project is added to the Project Browser.
Related Topics
Creating a Project
Deleting a Project
Importing a Project
Exporting a Project
Closing a Project
Creating a Project
This topic details how to create a project from within the application. Once a project has been
created, all project-level data can be managed within Capital Project. Refer to the Capital
Project User Guide for more information.
Procedure
1. Press Space Bar and enter New Project. The New Project Dialogis displayed.
2. Enter a Name for the project.
3. Click OK. The project is created and added to the Project Browser.
Note
Once a project has been created, it can only be edited in Capital Project.
Related Topics
Opening a Project
Editing the Attributes and Properties of a Project
Deleting a Project
Importing a Project
Exporting a Project
Closing a Project
Deleting a Project
This topic details how to delete a project from the database.
Caution
The deletion of a project cannot be undone without recourse to a database backup, which
may not be up-to-date.
Procedure
1. Open the project you want to delete.
2. Press Space Bar and enter Delete Project.
3. A message is displayed asking you to confirm the deletion. Click Yes to proceed and
delete the project. The project is removed from the database.
Related Topics
Opening a Project
Creating a Project
Editing the Attributes and Properties of a Project
Importing a Project
Exporting a Project
Closing a Project
Importing a Project
This topic details how to import an existing project (as a Project XML file) that has been
exported from another installation of Capital.
Procedure
1. Press Space Bar and enter Import Project. A generic file browser is displayed.
2. Navigate to the Project XML (*.xml) file that you want to import.
3. Click Import Project. A progress bar monitors the status of the import and disappears
once complete.
Note
An imported project is not opened by default and must be opened manually.
Related Topics
Opening a Project
Creating a Project
Deleting a Project
Exporting a Project
Closing a Project
Exporting a Project
Projects may be exported from, and imported into, the Capital Design databases (as XML files).
The use of XML files as the data-transfer medium enables the exchange of project data between
other data systems and also increases the portability of Capital project data. The data stored in
XML files is readily manipulated manually.
An exported project's XML file contains all of the information (options, object names, designs,
diagrams etc.) that are contained in its original database record.
Note
Even if you do not have Capital Analysis installed, you must have the Analysis permission
assigned to your user account in Capital User if you want to import and export projects that
have Analysis project models attached to them.
Procedure
1. If you want to export the currently open project, press Space Bar and enter Export
Current Project, or right-click on the project and select Export.
If you want to export a project that is not open, press Space Bar and enter Select Project
to Export; the Select Project dialog box is displayed. Select the project to export and
click OK.
The Export Project dialog box is displayed.
2. Specify the folder location and file name for the project's exported XML file.
3. Select the following as required:
• As Copy
Select this if you want the project to be exported with anonymous unique identifiers
(UIDs). This option replaces all of the exported project's database UIDs (within the
exported XML file) with anonymous UIDs so that the project can be imported back
into Capital in the future. A project exported with anonymous UIDs are
automatically assigned new UIDs when it is imported back into Capital.
Note
When a project is exported from Capital, its original record remains in the
database with its original UIDs. Therefore, if the project is exported without
anonymous UIDs, it cannot be imported back into Capital unless its UIDs have been
changed, as its original UIDs are already present in the original project in the
database and are not allowed to be overwritten.
4. Click Export Project; the selected project is exported from the database.
Related Topics
Opening a Project
Creating a Project
Deleting a Project
Importing a Project
Closing a Project
Closing a Project
This topic explains how to close a project in the application.
Procedure
1. Click the project in the Project Browser and either:
• Press Space Bar and enter Close Project
• Click Close Project ( ) at the top of the Project Browser.
If scopes are defined both at project and design level, the design-level scopes are used within a
design.
Only one customer or manufacturing site scope code is allowed per design or project.
Note
You can use extensibility (a plugin) to manage component scoping. If a plugin is available
then it will override the default rules, and will determine part suitability based on project,
design and library scoping but using the business logic defined within the plugin. For more
information about developing and using extensibility plugins, see the PluginDevelopment.pdf
file that is located in the doc\plugin folder of your Capital installation.
Prerequisites
• The required scopes must have been created in Capital Library.
Procedure
1. Right-click on the project name or design in the Project Browser Tree and select Edit;
the Edit Project Information dialog or Edit Design dialog is displayed.
2. Click Properties; an Edit Properties dialog is displayed.
3. Click the Scopes tab; the scope codes that have been created in Capital Library are
displayed in the Available window.
4. Select the scopes that you want to apply to the project or design and click Add; the
selected scopes are added to the Selected window.
5. Click OK.
Results
• The selected scopes are applied to the project or design.
• If a library component has had scopes applied to it, these dictate whether it is available
for selection within the project or design.
• For a design, if you hold your mouse cursor over the design name in the Project Browser
Tree, the applied scopes are displayed.
Project-Related Dialogs
This section offers a description of all dialogs used to open and create projects. For each dialog,
all fields are listed, along with a full description of the field’s function.
“Edit Project Dialog” on page 43
Moves the selected scopes in the Selected window to the Available window.
• Remove All
Moves all scopes in the Selected window to the Available window.
• Selected
Displays the names of the scopes applied to the project.
Objects
• The following fields and objects are available:
o Create New Project
Select this if you want to create a new project. Optional, displayed only when
starting application for the first time.
o Create
Select this if want to create a design in the new project. In the drop-down list, select
the type of design. If you select this, a New Design dialog is displayed when you
click OK. Optional, enabled only if Create New Project is selected.
o Open Existing Project
Select this if you want to open an existing project. Select the project in the window.
Optional.
o On Startup
Specifies whether a project opens by default the next time that you start the
application. Mandatory.
You can select the following:
• Always open last project
The last project that you opened in the application opens automatically.
• Display Open Dialog dialog
The Open Project dialog is opened automatically.
• Do nothing
No project opens and the Open Project dialog is not opened automatically.
Build Lists
A build list is a container for designs, representing a sub-set of a vehicle’s connectivity and
topology at a single point in the design life-cycle. Any number and configuration of build lists
may be created for a project.
See Build List in the Capital Project User Guide for full details of this concept and links to
related tasks.
Procedure
1. Right-click on the name of the design in the Project Browser Window on the upper left
of the application window and select Edit from the pop-up menu that is displayed.
2. The Edit facility is displayed. You can edit the following properties for the design:
• Name - the name of the design. If valid names for the object type have been created
in Capital Project, you can select a name by clicking the ellipsis button (...) to
display the Name Selection dialog.
• Part Number (Capital HarnessXC design only) - a unique part number for the
design.
• Revision - the revision for the design.
Note
You can click the Properties button to display the Edit Design Properties Dialog
that allows you to add or remove properties for the design.
Note
The Applicable Options field will only display if the project has been configured
to use Options. See Module Codes, Options preference settings in the Capital
Design Tools - Common Functions User Guide for details of how to configure the
project.
• Applicable Modules - Functional Module Codes that are available to objects in the
design, can be assigned, amended or removed by clicking the ellipsis button, (...),
next to the Applicable Modules field. This will display the Applicable Modules
dialog where you can select the required Functional Module code(s).
Note
The Applicable Modules field will only display if the project has been
configured to use module codes. See Module Codes, Options preference
settings in the Capital Design Tools - Common Functions User Guide for details of
how to configure the project.
• Option - the option or option expression that you want to apply to the whole design.
You must enter this in the Option Expression field by clicking the ellipsis (...)
button to display the Edit Option Expression dialog.
Note
The Option field will only display if the project has been configured to use
Options. See Module Codes, Options preference settings in the Capital Design
Tools - Common Functions User Guide for details of how to configure the project.
• Effectivity - if using effectivity, click the ellipsis (...) button to the right of the field
to launch the Edit Effectivity Dialog, from where you can specify the effectivity
ranges that apply to the design. See Managing Effectivity in the Capital Project
User Guide for an overview of using effectivity.
3. Click the OK button to confirm the changes and to exit the dialog.
Note
If you move a design to release level with Frozen Shared Objects behavior, all
shared objects in a design must be frozen. If any shared objects are not frozen, the
Freeze/Unfreeze Shared Objects facility is displayed automatically when you click the
OK button so that you can freeze them.
Deleting a Design
This topic details how to delete one or more designs from a project.
Note
The ability to delete a design may depend on its release level, and the allowable behaviors
assigned to that release level in Capital Project. Also, when working in a design application,
you can delete only designs that can be authored in that application.
Procedure
1. In the Project Browser Window, select one or more of the following:
• a design
The action will delete all revisions listed below the design.
• a design revision
The action will delete just the design revision.
• a design folder
The action will delete all designs, design revisions and folders contained within the
selected folder.
2. Right-click on a selected object and select Delete; a message asks you to confirm that
you want to delete the objects. When you delete a composite design, you have the option
of deleting both the composite and its derivatives or just the composite.
3. Click Yes.
Note
If a design cannot be deleted, an error message provides details of why it cannot be
deleted.
Importing a Design
Full details of how to import designs from XML files into a project, can be found by using the
following link:
Importing Designs into a Project topic in the Capital Design Tools - Common Functions User
Guide.
Procedure
1. On the Edit Design dialog or dialog for creating a design, click Properties to display
the Edit Design Properties Dialog.
2. Click New to display the New Property Dialog. Enter a name for the property and click
OK.
The property is added to the Edit Design Properties dialog box.
3. Specify the Value and Type for the property and click OK.
• Add All
Moves all scopes in the Available window to the Selected window.
• Remove
Moves the selected scopes in the Selected window to the Available window.
• Remove All
Moves all scopes in the Selected window to the Available window.
• Selected
Displays the names of the scopes applied to the design.
ECO Tab
Lists the Engineering Change Orders that impact the design.
• The following fields and objects are available:
o Category
Displays the category of the engineering change order. Read-only.
o Name
Displays the name of the engineering change order. Read-only.
o Short Description
Displays the short description for the engineering change order. Read-only.
o Date Created
Displays the date on which the engineering change order was created. Read-only.
o Date Updated
Displays the date on which the engineering change order was last updated. Read-
only.
o Release Level
Displays the release level for the engineering change order. Read-only.
o Design Status
Specify the status of the change required by the engineering change order: Not
Started, In Progress or Completed. This value dictates the Completion value of
the ECO on the Engineering Change Orders dialog where they are created.
If an ECO is associated with multiple designs, the Completion value of the ECO
only changes to Completed when the Design Status of all associated designs has
been changed to Completed. Mandatory.
Whenever you attempt to close a diagram that has been amended since it was last saved in the
current session, you will be asked if you wish to save the changes.
When a build list is active and you open a diagram that is not on that build list, the system asks
you to set an alternative build list as active. See “Selecting an Alternative Build List” on
page 57 for more information.
Note
Setting an active build list within a Capital Logic design does not set the analysis scope to
that build list. See the Scoping topic in the Capital Analysis User Guide for more
information.
2. Select the build list that you want to set as active. If it has a description, it is displayed in
the Description box. The designs in the build list are displayed in the Contents box.
Click the OK button.
3. In the Project Browser Window, the designs from the active build list have an orange
indicator next to them.
Note
You can click the Properties button to display the Edit Design Properties
dialog that allows you to add or remove properties for the design.
• Domain - The domain of the design. See the Capital Project for more information
about domains.
• Applicable Options - the options that can be assigned to the design. Click the
ellipsis (...) button by the Applicable Options field to display the Applicable
Options dialog.
Note
The Applicable Options field will only display if the project has been configured
to use Options. See Module Codes, Options preference settings in the Capital
Design Tools - Common Functions User Guide for details of how to configure the
project.
• Applicable Modules - Functional Module Codes that are available to objects in the
design, can be assigned, amended or removed by clicking the ellipsis button, (...),
next to the Applicable Modules field. This will display the Applicable Modules
dialog where you can select the required Functional Module code(s).
Note
The Applicable Modules field will only display if the project has been
configured to use module codes. See Module Codes, Options preference
settings in the Capital Design Tools - Common Functions User Guide for details of
how to configure the project.
• Option - the option or option expression that you want to apply to the whole design.
You must enter this in the Option Expression field by clicking the ellipsis (...)
button to display the Edit Option Expression dialog.
Note
The Option field will only display if the project has been configured to use
Options. See Module Codes, Options preference settings in the Capital Design
Tools - Common Functions User Guide for details of how to configure the project.
• Effectivity - if using effectivity, click the ellipsis (...) button to the right of the field
to launch the Edit Effectivity Dialog, from where you can specify the effectivity
ranges that apply to the design. See Managing Effectivity in the Capital Project
User Guide for an overview of using effectivity.
• Create Diagram - Check this box if you want to create a diagram for the design
automatically. If you create a diagram, it is automatically displayed in the diagram
window.
• Name - If you have specified that you want a diagram to be created automatically,
specify the name of the diagram.
Note
You can click the Properties button to display the Edit Diagram Properties
dialog that allows you to add or remove properties for the design. See “Editing
the Properties of a Diagram” on page 119 for more information.
• Style Set - the style set that you want to apply to the diagram. See the Diagram
Styling User Guide for more information about style sets and how to edit them.
3. Click the OK button.
4. A folder for the design is added to the Project Browser Window tree. Under the folder
for the design, the design revision is displayed. If the system has created a diagram
automatically, the diagram is displayed under the design revision in the Project Browser
Window tree and is opened in the diagram window.
Note
If the system has not created a diagram automatically. See “Creating a New
Diagram” on page 118 for information on how to create a diagram manually.
Related Topics
Project Browser Window
Creating a New Diagram
Copying a Design
This topic explains how to copy a design within a project.
Procedure
1. Open the project in which you want to copy the design. See “Opening a Project” on
page 36.
2. Right-click on the design in the Project Browser Window and select Copy. The Copy
Design Dialog is displayed.
3. Enter a Name and click OK. The new design is added to the Project Browser Window.
2. Right-click on the design in the Project Browser Window and select Create Revision.
The Create New Design Revision Dialog is displayed.
3. Enter a Revision and click OK. The design revision is added to the Project Browser
Window.
Note
The options that can be allocated to a design are created for the project as a whole, and not
for each individual design.
If the Edit Applicable Options dialog box contains no options in the Available or Selected
lists, it is likely that no options have yet been created for the project. This is done in Capital
Project. See the Capital Project help system for more information.
To allocate an option to the selected project, click the required option in the Available list and
click the Add button to move the option to the Selected list. If required, all of the options in the
Available list may be allocated simultaneously to the design by clicking the Add All button.
If required, you may remove a mistaken, or previously allocated, option from the design by
clicking the option in the Selected list and clicking the Remove button to move the option to the
Available list.
Click the Apply button to save the allocated options to the design and keep the dialog box open,
or click the OK button to save the allocated options and close the dialog box.
The specified applicable options can now be applied to the various design objects on the
project's schematic diagrams in Capital Logic.
what properties and attributes are on those objects. The results can be exported and saved as an
HTML file.
For example, you can compare a junction box wiring design that has been generated from a slot
in Capital Integrator or Capital Topology against a reusable junction box design.
When you compare two build lists, design revisions are compared individually by mapping each
design revision from the first build list to one in the second build list based on BaseUID or
Name.
Procedure
1. Open the diagram for one of the design revisions that you want to compare, press Space
Bar and enter Compare.
The Design Revision/Build List Selection Dialog is displayed.
2. Select the project that contains the build lists or design that you want to compare from
the Projects window.
3. Either:
• Select the two build lists that you want to compare from the Build Lists window.
• Select the other design revision that you want to compare from the Design Revisions
window.
4. Click OK.
The Compare Designs Dialog is displayed.
5. Specify the following:
• If you are comparing Capital Logic designs, whether you want to ignore Connectors
and Splices in the comparison. If you compare a Capital Logic design with a Capital
Integrator or Capital Topology design, this applies only to the Capital Logic design.
• Whether you want to compare Attributes and Properties on objects.
• If you are comparing Capital Logic and/or Capital Integrator or Capital Topology
designs, the Comparison Type that you want to perform. Select from:
o Topology Only
Only topological data is considered. None of the connectivity items on the
selected designs appear in the comparison results. Enabled only when comparing
two Capital Integrator or Capital Topology designs.
o Exact
Nets and wires are treated as different types of object, and all objects are treated
as equivalent if they have the same base UID (when comparing revisions of the
same design) or if they have the same name (when comparing designs that are
unrelated).
o Conductor Equivalent
Nets and wires are treated as the same type of object. Devices are treated as
equivalent if they have the same name. Enabled only when comparing a Capital
Logic design.
Note
If there is a net between two pins on one design revision and two wires
separated by a splice between the same pins on a second design revision,
these are treated as the same.
Note
You can export and save the comparison results in an HTML file by clicking
Export. You can display the differences between the design revisions graphically in
the diagram windows by clicking Show Differences.
The Map Equivalent Devices dialog lists the devices from the two designs in separate tables
that list the names, pin counts and part numbers of the devices. You can click on the title of any
column to sort the table according to the contents of that column.
The second design must contain equivalent devices for all of the devices in the first design for
mapping to occur. The second design can contain devices that do not have equivalents in the
first design but not vice versa.
You can select a device in either table and click the Associate button to map them. To unmap
devices, select them in the tables and click the Disassociate button.
If you click the Assist button, the system attempts to map devices automatically. It may be the
case that it cannot map all devices and you may need to map some manually. When you click
the Assist button, the Suggestions box displays any suggested mappings that the system has
identified.
When you are satisfied with the mappings, you can click the OK button to return to the
Compare Designs facility.
Related Topics
Comparing Objects and Their Properties in Design Revisions or Build Lists
• See Running Design Rule Checks in the Capital Design Tools - Common Functions
User Guide.
• See Running Design Rule Checks in Background in the Capital Design Tools - Common
Functions User Guide.
• For a full list of the design rule checks available for use in Capital HarnessXC and
Capital ModularXC, see Design Rule Checks Applicable to Capital HarnessXC/Capital
ModularXC Designs in the Capital Design Tools - Common Functions User Guide.
The table includes columns in which you can filter the contents by selecting an item from the
dropdown list at the top. You can sort the contents of a column by clicking the column header.
The columns are:
• Severity
Whether the result is an error ( ), a warning ( ) or an information message ( ).
• Category
The category of design rule check to which the particular design rule check belongs (for
example, Connectivity, Naming, and so on).
• DRC
The specific design rule check that has identified something in the design.
• Design
The design in which the check has identified something/
• Object
The specific object for which the check has identified something.
• Message
Detailed message about what the check has identified. You can click an object in the
message to jump to that object in the diagram window.
If you are using Web Services with your Capital applications, you can release a Capital Logic or
Capital Integrator design and send an automatic notification to the Web Services component.
When you release a design this way, it is automatically checked for design errors using the
Design Rule Checks functionality.
If you are using Capital Topology, see “Design Rule Checks (Capital Topology)” on page 641
for descriptions of the available checks.
For a full list of the design rule checks available for use in Capital Logic, see Design Rule
Checks Applicable to Capital Logic Designs in the Capital Design Tools - Common
Functions User Guide.
Styling Objects
You specify the way in which you want to style objects in diagrams by using a style set. Style
sets are maintained at the system level but are applied to individual diagrams. By default,
Capital Logic uses a Default style set.
The creation of style sets beyond the default offered is a licensed operation; if you do not have
the license required, the option to create new style sets is unavailable.
See the Diagram Styling User Guide for more information about style sets and how to edit
them.
Project Preferences
Project preferences are default settings that you specify for the designs and diagrams in a
project.
You specify them in the Project Preference Dialog Box, accessed in the design applications by
pressing Space Bar and entering Project Preferences.
You can also edit them in Capital Project by opening a project, expanding the Project Browser
Tree for that project and double-clicking the Preferences node.
Note
Some preferences work alongside Capital styling to control the appearance of designs. See
the Capital Diagram Styling User Guide for more information about all aspects of Capital
styling.
If a preference (for example, bundle thickness) is specified for an object type, whenever a new
instance of that object type is inserted into a design, it will automatically assume this pre-set
preference setting.
All new and existing designs within a project automatically inherit their project's preferences.
Note
Preferences can also be specified at the system level.
Related Topics
Project Preferences for Capital Logic
Project Preferences for Capital Topology
Project Preferences for Design Rule Checks
General Project Preferences Applicable to all Applications
These preferences can be set by using the Design Change Policy Manager functionality in
Capital Project. See the Capital Project help system for more information.
Extensibility Plugins
Extensibility Plugins allow you to create custom actions and functions that are exposed in the
Capital user interface (XC & Logic).
For full details see the Extensibility Plugins section of the Capital Design Tools - Common
Functions Guide.
Releasing a Design
You can release designs and enforce the running of particular design rule checks when doing so.
This action is available for designs created in Capital Logic, Capital Topology, Capital
Integrator, Capital HarnessXC and Capital ModularXC.
See Releasing Designs with Enforced Design Rule Checks in the Capital Design Tools -
Common Functions User Guide.
Assigning module codes to a design, makes the codes available to be assigned to components on
any diagram in such a design.
Please see the Applicable Functional Module Codes Dialog section in the Capital ModularXC
guide for full details.
The Harness Synchronization process will pass the module codes, assigned to any components,
from Capital Logic to Capital ModularXC, allowing them to be used in the Capital Modular XC
Modular Processing.
See the Applicable Functional Module Codes Dialog section in the Capital ModularXC guide
for full details.
There are three ways in which you can define relationships between options at project level:
Deleting an Option
4. Specify the Name and Description for the option and whether it is a Variant option.
5. Define any Inclusive or Exclusive relationships for the option.
6. Click OK.
Related Topics
Creating an Option Folder at Project Level
Defining Inclusive and Exclusive Relationships for an Option
Creating an Option Combination at Project Level
Adding a Valid Selection to an Option Combination
Deleting a Valid Selection from an Option Combination
Deleting an Option
2. Select the option in the Options Browser on the left of the dialog.
The fields on the right of the dialog display the values for that option.
3. Add any Inclusive or Exclusive relationships for the option.
4. Repeat steps 2 to 3 for each option that you want to add to edit.
5. Click OK.
Related Topics
Creating an Option Folder at Project Level
Creating an Option Combination at Project Level
Adding a Valid Selection to an Option Combination
Deleting a Valid Selection from an Option Combination
Deleting an Option
A new option combination is added to the Options Browser on the left of the dialog.
3. Specify the Name for the option combination.
4. Drag and drop an option to be included in the option combination from its location in the
Options Browser tree to the option combination node in the tree.
The option is listed under the option combination as well as in its original location in the
tree.
5. Repeat step 4 for each option that you want to add to the option combination.
6. Select the option combination in the Options Browser.
The options are displayed as columns in the Valid Selections table.
7. Click to add a valid selection row to the table.
9. In the row, select the options that are included in the valid selection.
10. Repeat steps 7 to 9 for each valid selection in the option combination.
11. Repeat steps 2 to 10 for each option combination that you want to create.
12. Click OK.
Related Topics
Creating an Option Folder at Project Level
Defining Inclusive and Exclusive Relationships for an Option
Adding a Valid Selection to an Option Combination
Deleting a Valid Selection from an Option Combination
Deleting an Option
The row is deleted from the table and the valid selection is deleted from the option
combination.
5. Repeat steps 3 to 5 for each valid selection that you want to add.
6. Click OK.
Related Topics
Creating an Option Folder at Project Level
Defining Inclusive and Exclusive Relationships for an Option
Creating an Option Combination at Project Level
Adding a Valid Selection to an Option Combination
Deleting an Option
Deleting an Option
This topic explains how to delete an option from the Options Dialog.
Select the option in the Options Browser and click Delete selected objects ( ).
• If the option is used in a combination, an error message is displayed and the option is not
deleted.
• If the option has been specified as an applicable option for a design, an error message is
displayed and the option is not deleted.
• If the option is not used in a combination, it is removed from the Options Browser.
Related Topics
Creating an Option Folder at Project Level
Creating an Option at Project Level
Defining Inclusive and Exclusive Relationships for an Option
Creating an Option Combination at Project Level
Adding a Valid Selection to an Option Combination
Deleting a Valid Selection from an Option Combination
Options Dialog
To access: Press Space Bar and enter Options with the project open.
Used to define option relationships within a project.
Objects
• The following fields and objects are available:
o Options Browser
Located at the left of the dialog. Blank when no options exist.
Displays a tree of options ( ) and variant options ( ) grouped within option folders
( ). When you edit options at project level, option combinations ( ) are listed too.
When you select an option folder, option combination or option in the tree, details
for the selected item are displayed in fields on the right of the dialog.
You can drag and drop items in the tree to:
• Change their order. Dragging an option or folder to a space between two other
items moves it there. Dropping an option or folder over another folder adds it as
the last child node of that folder. This order of option folders and options
controls the order of options when they are listed in other dialogs in Capital
applications.
• Add an option to an option combination. In this case, the option is copied in the
tree.
o Delete selected objects
o Exclusive
Lists the options that cannot be used with the option selected in the Options
Browser. Optional, displayed only for options at project level.
Click to display the Choose Options Dialog where you select the exclusive
options.
To remove an option from the Exclusive window, select it and click .
o Valid Selections
Lists the options in the option combination selected in the Options Browser; each
option is a column in the table. A row represents a valid selection of the options.
Click to add a row to the table. Click to delete a row from the table. Within a
row select the options that you want to be included in that valid selection. The Name
column specifies unique identifiers for the valid selections. Available only for option
combinations at project level.
Related Topics
Creating an Option Folder at Project Level
Creating an Option at Project Level
Defining Inclusive and Exclusive Relationships for an Option
• select it and delete is as normal; the object no longer exists in the design data.
• select it and press Ctrl + Delete on your keyboard; the object is removed from the
diagram but still exists as a connectivity object in the design. It is moved to an Unplaced
folder for that object type in the Design Browser Window. You can then place that
object in a diagram again. However, when you next save the design, all Unplaced
objects may be deleted from the design data depending on the Purge unplaced objects
on Save setting listed under General Preferences in the Project Preferences. For a short
video illustrating this task see “Deleting a Stack of Pins” on page 163.
When you delete any instance apart from the final instance of an object from a diagram, then the
connectivity is retained. Its pins become unplaced and remain connected to the wires -
following the existing unplace functionality.
In this example, P100 has pins 1, 2 and 3 and P101 has pins 4. Merging P101 into P100 creates
a single object (named P100) that has pins 1, 2, 3 and 4.
Any objects to be merged must be the same type of object (connectors must be the same type of
connector).
A device represented by a symbol can be merged with a parameterized device so that one
instance is a symbol and one is not. Devices represented by different symbols can be merged so
that one device uses different symbols for instances.
This action does not break library part associations so it is not possible to:
When you merge two devices with different analysis models, the resultant device maintains the
behavior of both blocks. However, you can override this by specifying a new behavior using the
attach analysis model action (right-click on the device and select Analysis > Attach, see
Attaching Component Models in the Capital Analysis for Capital User Guide).
1. Double-click the top node for that object in the Design Browser Window.
2. If the object does not have pins, skip to step 4.
If the object has pins, the Place Dialog is displayed; specify whether you want to create
the object instance as a symbol (Symbol Selection) or to create the object instance as a
parameterized shape (Pin Selection).
3. Either select the symbol to be used (Symbols) or the pins to be included on the
parameterized shape (Available Pins) and click OK.
4. Place the object on the diagram as you would when using menu options.
Note
A wire conductor can be placed on a diagram only if it creates a connection between
two or fewer pins.
5. A new instance of the object is listed below the top node for it in the Design Browser
Window. The instance lists the pins included on it.
Related Topics
Design Wide Object
Place Dialog
To access: Double-click an object with pins in the Design Browser Window.
Use this dialog to select which pins are included on the new instance of an object in the diagram
or which symbol is used when placing a Design Wide Object.
Objects
Related Topics
Adding an Instance of a Design Wide Object
Procedure
1. In the diagram window or the Design Browser Window, right-click on the source design
wide object that you want to merge into another target design wide object and select
Merge Into; the Merge Into Dialog is displayed.
2. Select the target design wide object into which the selected object will be merged and
click OK.
Results
• Any pins with the same name in the source object and target object are merged on the
merged object. Any pins with unique names on the source or target object appear on the
merged object.
Note
If the project preference Disallow pin duplication within a design is set, objects
with duplicate pin names can not be merged. Such object names will not be
selectable in the Merge dialog. A tooltip message displays an explanation of this on
hovering over such a row in the Merge dialog.
• When you merge two devices with different analysis models, the resultant device
maintains the behavior of both blocks. However, you can override this by specifying a
new behavior using the attach analysis model action (right-click on the device and select
Analysis > Attach, see Attaching Component Models in the Capital Analysis for
Capital User Guide).
Related Topics
Design Wide Object
Adding an Instance of a Design Wide Object
Related Topics
Merging Instances of Design Wide Objects
A report is generated detailing design name, revision, option expression, part number, type,
abstraction and a description of the shared object including individual pins usage, if connected.
Related Topics
Finding Which Designs Use a Shared Object Revision
Objects
Delete selected effectivity Deletes the selected row in the Effectivity Table.
range
Revisions Lists the existing revisions of the design and the
effectivity ranges that have been specified for those
revisions. Read-only.
For example: if 1[1..10] is listed, this means that the
range 1 to 10 has been specified for revision 1 of this
design.
Related Topics
Creating a New Capital Logic Design
Editing the Information for a Design
Creating a Revision of a Design
Note
The Applicable Options field will only display if the project has been
configured to use Options. See Module Codes, Options preference settings
in the Capital Design Tools - Common Functions User Guide for details of how
to configure the project.
• Applicable Modules
Functional Module Codes that are available to objects in the design, can be
assigned, amended or removed by clicking the ellipsis button, (...), next to the
Applicable Modules field. This will display the Applicable Modules dialog
where you can select the required Functional Module code(s).
Note
The Applicable Modules field will only display if the project has been
configured to use module codes. See Module Codes, Options preference
settings in the Capital Design Tools - Common Functions User Guide for details
of how to configure the project.
• Option
The option or option expression that you want to apply to the whole design.
Click the ellipsis (...) button to display the Edit Option Expression Dialog where
you can select a single option or create an option expression. Optional.
Note
The Option field will only display if the project has been configured to use
Options. See Module Codes, Options preference settings in the Capital
Design Tools - Common Functions User Guide for details of how to configure
the project.
• Effectivity
If using effectivity, click the ellipsis (...) button to the right of the field to launch
the Edit Effectivity Dialog, from where you can specify the effectivity ranges
that apply to the design. See Managing Effectivity in the Capital Project User
Guide for an overview of using effectivity.
o Copy Options
• Retain Generated Names
Specifies whether object names that have been generated using advanced naming
are retained in the copy (selected) or whether object names return to default
naming in the copy (unselected). Mandatory.
Note
The Applicable Options field will only display if the project has been
configured to use Options. See Module Codes, Options preference settings
in the Capital Design Tools - Common Functions User Guide for details of how
to configure the project.
• Applicable Modules
Functional Module Codes that are available to objects in the design, can be
assigned, amended or removed by clicking the ellipsis button, (...), next to the
Applicable Modules field. This will display the Applicable Modules dialog
where you can select the required Functional Module code(s).
Note
The Applicable Modules field will only display if the project has been
configured to use module codes. See Module Codes, Options preference
settings in the Capital Design Tools - Common Functions User Guide for details
of how to configure the project.
• Option
The option or option expression that you want to apply to the whole design.
Click the ellipsis (...) button to display the Edit Option Expression Dialog where
you can select a single option or create an option expression. Optional.
Note
The Option field will only display if the project has been configured to use
Options. See Module Codes, Options preference settings in the Capital
Design Tools - Common Functions User Guide for details of how to configure
the project.
• Effectivity
If using effectivity, click the ellipsis (...) button to the right of the field to launch
the Edit Effectivity Dialog, from where you can specify the effectivity ranges
that apply to the design. See Managing Effectivity in the Capital Project User
Guide for an overview of using effectivity.
Contains the complete expression constructed from the Options and Operators
available. You also have the option to type an expression into this field instead of
selecting from the lists above. Mandatory.
In the field next to the Enter Filter String icon ( ), enter a series of characters. A
filter is applied to the Design Revisions window so that only designs with names
containing that series of characters are listed.
Click the Clear Filter String icon ( ) to clear the filter and view all designs in the
project.
o Design Filter ( )
Click the dropdown list to filter the designs displayed in the Design Revisions
window to those of a particular type, all designs in the project or all designs in the
currently active build list.
Note
If there is a net between two pins on one design revision and two wires
separated by a splice between the same pins on a second design revision,
these are treated as the same.
Runs the comparison. The result for which are displayed in Differences window.
Mandatory.
o Export
Enables you to export and save the comparison results in an HTML file. Click this to
display the Design Compare Report Dialog where you select a location to save the
file and specify the file name. Optional.
o Differences
Lists the results of the design comparison in a tree. The tree displays each design
revision and the objects being compared in each design. If an object appears on a
design revision or build list, the field in the column for that design revision or build
list is selected.
If you are comparing properties and option expressions on objects, these are listed
under the appropriate objects. If the property or option expression is set for the
object in a design revision or build list, the field in the column for that design
revision or build list is selected.
If filtering has been applied to the diagram windows for the designs, (Filter Active)
is displayed in the head for the Differences column.
Note
If you click on an object in the Differences window, the diagram containing that
object is opened and the object is highlighted.
o Show Differences
Displays the differences between the design revisions graphically by fading
(filtering out) objects that are common in the diagram windows. You move the slider
control up and down to control how much the common objects are faded. Objects
that are different between the design revisions are displayed normally. When clicked
this button changes to Hide Differences. Optional, not available when comparing
build lists.
Note
If filtering has been applied to the diagram windows for the design revisions,
(Filter Active) is displayed in the head for the Differences column. This means,
some objects may have been faded in the diagram window as a result of the filtering
and not as a result of showing differences.
o Hide Differences
Displays all objects in the diagram windows normally, regardless of whether they
are common to the design revisions or not. When clicked this button changes to
Show Differences. Optional, not available when comparing build lists.
o Slider Control
Move the slider up and down to control how much common objects are faded out
(filtered) when Show Differences has been clicked. Optional, not available when
comparing build lists.
Options Help
What do you need help with?
• Options and Option Relationships
• The Options Dialog fields
• Creating an Option Folder at Project Level
• Creating an Option at Project Level
• Defining Inclusive and Exclusive Relationships for an Option
• Creating an Option Combination at Project Level
• Adding a Valid Selection to an Option Combination
• Deleting a Valid Selection from an Option Combination
• Deleting an Option
This following sections explain how to open, create, filter and manage diagrams, including the
objects portrayed on them.
Creating a New Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Editing the Properties of a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Editing the Name of a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Adding a Property to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Deleting a Property From a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Deleting a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Filtering the Objects Displayed in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Effects of Filtering on Object Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Moving Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Moving Objects from a Diagram to Another Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Adding a Diagram List Table to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Adding a Device List Table to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Changing the Background Color of a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Closing a Diagram Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Deleting an Object from a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Selecting Objects in a Diagram Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Specifying the Highlight Color of Selected Objects in a Diagram. . . . . . . . . . . . . . . . . . . 128
Slice Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Copying Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Editing Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Multiple Selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Undoing an Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Redoing an Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Repeating an Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Cutting and Pasting an Object in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Copying and Pasting an Object in a Diagram to Create a New Instance of the Same Object
132
Copying and Pasting an Object in a Diagram to Create a New, Non-Shared Object . . . . . 133
Moving Diagram Objects to the Grid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Deleting an Object in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Selecting All Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Finding and Selecting Objects by Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Procedure
1. Either:
• select a logical design in the Project Browser Window, press Space Bar and enter
New Logical Diagram
• right-click on a logical design in the Project Browser Window and select New
Logical Diagram
The New Logical Diagram Dialog is displayed.
2. Specify the name of the diagram and click OK; the diagram is created and placed
beneath the design to which it belongs in the Project Browser Window.
4. In the Value column for that property, enter the value that you want the property to have
and click the OK button.
Deleting a Diagram
You can delete a diagram but keep the connectivity that is displayed graphically in it.
Procedure
1. Right-click on the diagram name in the Project Browser Window and select the Delete
option from the pop-up menu.
2. The Delete facility is displayed.
If you want to delete the connectivity that is represented in the diagram, check the
Delete connectivity? box.
If you want to keep the connectivity, ensure that the Delete connectivity? box is
unchecked.
3. Click the Yes button to delete the diagram.
4. The diagram is removed from the Project Browser Window. If you selected not to delete
the connectivity, the connectivity set is still displayed under the design in the Project
Browser Window.
Filtering does not change design data. The effect of filtering an object out of the diagram is
limited to the following:
• Cross-references to invisible objects are still displayed and following the cross-reference
opens the other diagram but the invisible object is not selected.
Note
See “Effects of Filtering on Object Types” on page 122 for more information per
object type.
Procedure
1. Open the diagram.
2. Press Space Bar and enter Filter design.
The Design Filter facility is displayed.
3. Select one of the following Filter options:
• No Filtering
Display all objects for every possible configuration of the vehicle.
• By Configuration
Display only objects from one configuration. Ensure that you are showing the filter
options (Show Filter Options) and add the configuration to the Selected window.
To select the configuration whose objects you want to display, click on it in the
Available window and click the Add button to move it to the Selected window. If a
configuration is displayed in the Selected window already, it is moved back to the
Available window automatically.
If you wish to remove the configuration from the Selected window, click Remove to
move it to the Available window.
• Graphics by Option / Custom Filter
Display only objects that have been assigned particular options.
Ensure that you are showing the filter options (Show Filter Options) and add the
options to the Selected window.
Caution
When you select an option here, the diagram will still include objects that are not
explicitly set to not be included with that option. For example, when an option A
is selected, then this includes all objects that are not set to !A (for example, B, C,
blank, and so on). You cannot use this filter to display only objects that have option
A. However, you can use the Find and Replace facility to locate only objects with
option A. See “Finding and Replacing Property Values, Attribute Values and
Symbols” on page 450.
If you want to display objects with no assigned option expressions, select Show
Non-Optioned Objects. Inlines and interface connectors not connected to a bundle
are filtered (hidden). Otherwise, their visibility depends on the visibility of the
attached bundle. The visibility of slot portals depends on the visibility of the slot.
Note
If no options are in the Included column, only objects with no option expression
are displayed in the diagram.
4. Click the OK button; the filtering is applied and the filtering icon on the Status Bar at
the bottom of the application window displays the icon for the filtering that you have
selected.
Assembly
An assembly has no visible representation in a diagram window but it is filtered out of the
Design Browser Window. When an assembly is filtered out, the objects within the assembly
remain visible in the diagram window.
Note
An object in an assembly has two entries in the Design Browser Window; one under the
assembly and one under the node for its object type. Only the entry under the assembly is
filtered out.
Daisy Chain
If either multicore associated with a daisy chain is filtered out so is the daisy chain.
Device Connector
If a device is filtered out so are any device connectors on it. If a device is visible, the option
expressions on the device connectors dictate whether they are visible or not.
Inline Connector
Each half has its own option expression that dictates whether that half is filtered out or not.
Multicore
When a multicore is filtered out, its indicators are invisible. The visibility of the inner cores
depends on their own option expressions. When an inner core is filtered out but the multicore
has no option expression, the indicators retain their original size. A multicore is visible in the
Design Browser Window if at least one inner core is visible in the diagram or if it has an
implicit shield termination.
The Add Multicores Dialog displays only multicores associated with visible conductors in the
diagram.
Net Conductor
A net conductor can be filtered out based on its own option expression. It is also filtered out if
the objects to which it connects are filtered out. If the option expression on a pin is currently
filtered out, the pin remains visible but it is disconnected from any net conductor so the net
conductor becomes invisible.
Overbraid
Behaves in the same way as a multicore.
Pin
The visibility of a pin is dictated by the visibility of the pinlist to which it belongs, regardless of
the option expression on the pin. Dialogs that list pins continue to list all pins regardless of
filtering.
Shield Termination
Follows similar rules to a wire conductor. However, a multicore can gain an implicit shield
termination when it is daisy chained to a multicore that has an explicit termination. The implicit
terminations are not visible in the diagram window but are visible in the Design Browser
Window. If the multicore with the implicit shield termination is not filtered out, the implicit
shield termination remains visible even when the explicit shield termination is filtered out.
Splice
Splices are filtered out based only on their own option expressions. Unconnected splices are not
automatically filtered out.
Wire Conductor
Follows similar rules to a net conductor.
Moving Objects
This topic explains how to move objects within a diagram.
Procedure
1. Select one or more objects.
2. Either:
• Drag the objects using the mouse
• Hold Shift and use the arrow keys on your keyboard to move the objects by:
o One pin grid point if one or more selected objects have pins
o One Drawing Point if no selected objects have pins
• Hold Ctrl and use the arrow keys on your keyboard to move the objects by:
o One Major Grid Interval if one or more selected objects have pins
o Approximately half of a pin grid point if no selected objects have pins. Note that
when there are less than two Drawing Grid points per pin grid point, objects with
no pins will move a great distance.
The table contains one column Diagram that lists the diagrams in the design.
Note
The background color change only affects on-screen viewing; printing a diagram is always
executed with a white background.
If other diagram windows are open for the design, the diagram is closed but any modifications
in that diagram are not saved until you either:
For example:
To select only the name text in the design, you click on one instance of name text and then hold
down the SHIFT key on your keyboard and drag the mouse cursor to form a box around the
design.
When you click to place the opposite corner of the box, the box disappears and the name text in
the diagram is selected:
Note
The color that you have selected will be used in other sessions of Capital design
tools when you start them.
Slice Objects
Certain objects on diagrams can be sliced, simplifying diagram modifications and making
diagrams easier to understand.
The Slice functionality allows you to draw an intersection line across an applicable object, to
create a new instance of that object, retaining connectivity and preserving style. You can use
this to quickly partition diagram content then move it to a new diagrams, or to trim oversized
devices and connectors.
Copying Objects
You can copy objects both within a diagram and from one diagram to another.
Procedure
1. Select the objects that you want to copy in the diagram window, press Space Bar and
enter Copy, or right-click on the selection and select Copy from the pop-up menu.
Alternatively, you can use the key combination CTRL + C.
2. Open the other diagram and either right-click on the diagram window and select the
Paste menu option from the pop-up menu or click on the diagram window, press Space
Bar and enter Paste. Alternatively, you can use the key combination CTRL + V. If you
do any of these, the copies of the objects are given unique names.
In addition, you can use the key combination CTRL + SHIFT + V. If you do this, the
copies of the objects retain the same names as the original objects.
Editing Actions
The following topics explain how to perform various generic editing actions.
Multiple Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Undoing an Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Redoing an Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Repeating an Action. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Cutting and Pasting an Object in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Copying and Pasting an Object in a Diagram to Create a New Instance of the Same Object
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Copying and Pasting an Object in a Diagram to Create a New, Non-Shared Object . . 133
Moving Diagram Objects to the Grid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Deleting an Object in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Selecting All Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Finding and Selecting Objects by Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Finding and Selecting Objects by Attribute or Property . . . . . . . . . . . . . . . . . . . . . . . . . 135
Select By Name Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Select by Attribute/Property Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Using the Stroke Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Multiple Selection
A number of the grids and lists in the dialogs support the selection of multiple items. There are
two ways to select multiple items:
• Hold down the Ctrl key on your keyboard while clicking subsequent, non-adjacent
items. For example, you could select the first, third and fifth items in a list. While
holding the Ctrl key, you can deselect items in the same way, removing them from the
selection.
• Hold down the Shift key on your keyboard while clicking the first and last items of a
subset you want to select. For example, with the first item in a list selected, clicking the
fifth item with the Shift key held down results in items one to five all being selected.
Undoing an Action
This topic explains how to use the undo facility to reverse up to the last 20 actions that have
been performed.
Procedure
1. Press Space Bar and enter Undo.
2. The previous action is undone and is added to the stored list of undone actions.
Note
If you perform a new action after you have undone one or more actions, this empties
the stored list of undone actions.
Redoing an Action
This topic explains how to use the redo facility to re-perform the last actions that were reversed
using the undo facility.
Note
If there are no more actions to redo, the Redo option changes to Repeat... .
Procedure
1. Press Space Bar and enter Redo.
2. The previously undone action is redone.
Repeating an Action
This topic explains how to repeat an action. If there are no undone actions that can be redone,
the menu includes an option to repeat the last action that was performed.
Procedure
1. Press Space Bar and enter Repeat.
2. The application is put in the correct mode to repeat the last action performed.
Note
If Disallow pin duplication within a design is selected in your Project Preferences,
then you will not be able to copy and paste shared pins or paste where duplicate pin
instances will be created. In this case, a message is displayed.
If you attempt to paste an object within another design, then the paste will create a new,
non shared object with a new name.
4. Drag the copy to the location where you want to place it.
Note
If you attempt to undo this action, you will clear the clipboard only.
Related Topics
Copying and Pasting an Object in a Diagram to Create a New, Non-Shared Object
Note
If you attempt to undo this action, you will clear the clipboard only.
Related Topics
Copying and Pasting an Object in a Diagram to Create a New Instance of the Same Object
Prerequisites
• In the clientprops.xml in the config directory of your installation, edit the value of
<allowmigrationflow value="no"> to be yes and restart Capital Logic. If you do not do
this, the Move To Grid action will not be visible.
Procedure
In the diagram, select the objects that you want to move to the grid, press Space Bar and enter
Move To Grid.
Results
• For each selected object:
o Pins snap to the grid.
o Object boundaries snap to the grid. Note that device boundaries only snap to the grid
if the device has attached connectors or if any of the attached connectors are inside
the device.
o Device pins and attached connectors move to device boundaries (attached segments
to connectors move as well).
• For each selected conductor:
o The start and end points of each segment snap to the grid.
Each stroke action maps to a pattern on the following nine part grid:
A stroke is identified by the path of the mouse through the grid. For example, the following
stroke that is a counter-clockwise C pattern is named 3214789 because of the grid squares that it
passes through.
Window Controls
The following topics explain how to arrange open diagram windows and browser windows for
viewing and how to use the zoom and pan controls to change what you are viewing in a
window.
Arranging Diagram Windows for Viewing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Moving Browser Windows Around the Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Zooming In and Out of Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Panning Across a Diagram Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Procedure
1. Click on the tab of the browser window and drag it to the location where you want to
display it.
2. Resize the browser window as required.
Note
To return the browser window to the bottom left of the main application window,
close the separate window. It returns to its original position automatically.
o Type
The data type of the value. Mandatory. If you enter a Value that is not supported by
the selected Type, the Value is displayed in red text and the OK button is disabled.
The following types are available:
• String - a mix of letters, number or special characters
• Integer - a whole number
• Float - a number including a decimal (floating) point
To delete a property from the list, select it and click the Delete button, then click OK to
confirm the deletion.
The following sections describe how to add and edit pins on objects in designs.
Adding Pins to an Object Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Usage Example - Preventing Pin Duplication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Adding Pins to an Instance of a Shared Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Moving a Pin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Disconnecting a Conductor from a Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Overview of Reference Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Cross-reference Rules for Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Converting a Non-reference Instance of a Pin to a Reference Instance . . . . . . . . . . . . . . . 153
Converting a Reference Instance of a Pin to a Non-reference Instance . . . . . . . . . . . . . . . 153
Connecting Selected Overlapping Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Connecting Selected Pins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Stacked Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Creating a Stack of Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Adding a Pin to a Pin Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Removing a Pin from a Pin Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Viewing the Pins in a Pin Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Deleting a Stack of Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Viewing the Highway Conductors that Terminate at Stacked Pins . . . . . . . . . . . . . . . . . . 164
Edit Stack Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Usages Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Usage Examples - Stacked Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Help Button Landing Pages for Pins Dialog Boxes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Place Pins For Share Object Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Place Pins Dialog for Shared Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Place Pins for Non-shared Object Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Place Pins Dialog for Non-shared Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Edit Stack Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Stack Usages Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Procedure
1. Select the object in the Diagram Window or in the Design Browser Window and either:
• Right-click on it and select Add Pin; the Place Pins Dialog for Non-shared Object is
displayed where you select whether you want to add existing pins or create a new
one. You can select multiple existing pins.
Press SHIFT when selecting Add Pin to add multiple new pins.
• Press Space Bar and enter Add External; the Place Pins dialog (for non-shared
object) is displayed where you select whether you want to add existing pins or create
a new one. You can select multiple existing pins.
Note
If the project preference Disallow pin duplication within a design is set,
existing pins will not be displayed in the Place Pins dialog (for non-shared
object), as creation of duplicate pin instances will be prohibited. You will only be
able to add duplicate pin instances as reference pins, see Overview of Reference
Pins. To allow the placement of duplicate pins the project preference Disallow pin
duplication within a design should be unset.
Press SHIFT when selecting the Add External action to add multiple new pins.
• Press P (to add one new pin).
2. In the Diagram Window, click on the points of the object where you want to add pins.
As you move the cursor over the object, it changes appearance.
In the case of devices, you can add a pin at a grid point on an edge of the device. You
can also add a pin outside of the graphical representation of the device, the device
stretches to include the new pin. For connectors, a broken line indicates the side on
which you can add a pin. If you add a pin at a point on the broken line outside of the
connector symbol, the symbol stretches to include the new pin. For shared objects, a
dialog box appears showing the pins available to add to the object.
3. If adding multiple new pins, press the Esc key on your keyboard to stop.
Note
If you are using a generative flow where you will use Capital Integrator to generate
wiring for the design, you may want to consider the values specified for the
following pin attributes:
Connector Group - specifies the name of the virtual connector to which the pin maps
when it is placed in a slot in a Capital Integrator design.
Connector Cavity - specifies the name of the connector cavity to which the pin maps
when it is placed in a slot in a Capital Integrator design. Normally, the pin will map to a
cavity with a name equivalent to the value of this attribute. However, a connector part
may restrict the matching of the name.
Related Topics
Moving a Pin
Disconnecting a Conductor from a Pin
Procedure
1. Within Capital Project or Capital Logic, press Space Bar and enter Project Preferences,
select General from the left hand pane and select the Disallow pin duplication within a
design preference.
2. When the project preference is enabled the Place Pins dialog will only show the
following;
a. Non-shared pins that have not been used elsewhere in the design.
b. Shared pins that have not been used by any other design within the active build list.
3. Clicking "Add as Reference Pins" will list all pins and allow the user to place a pin as a
reference instance.
Note
Reference pins appear on the diagram with a cross, conductors cannot be terminated
onto reference pins.
Should you wish to create a duplicate instance of a pin, this is only possible if the pin
duplication preference is disabled or the pin is shared with an unrestricted reservation
status.
4. In Figure 4-1 pin "ACC" has been made "Unrestricted", therefore you can place multiple
instances of the pin within the current or any design within the project.
5. The Design Rule Check "Multiple instances of a pin within the design" will report any
duplicate placed pins (unless the pins are shared as "unrestricted"). Additionally a
custom Design Rule Check can be deployed which report multiple occurrences of any
pin within a design.
Results
The project preference controls pin usage for shared or non-shared objects.
If pin duplication is needed for selective pins then they should be shared with the "unrestricted"
status.
Design Rule Checks can be used to identify pin duplication within existing designs.
Procedure
1. Select the shared object in the Diagram Window or in the Design Browser Window and
either:
• right-click on it and select Add Pin
• press Space Bar and enter Add External
• press P
The Place Pins Dialog for Shared Object is displayed where you select which existing
pins to add to the instance.
2. Select the pins that you want to add to the instance and click OK.
3. In the Diagram Window, click on the points of the object where you want to add pins.
As you move the cursor over the object, it changes appearance.
In the case of devices, you can add a pin at a grid point on an edge of the device. You
can also add a pin outside of the graphical representation of the device, the device
stretches to include the new pin. For connectors, a broken line indicates the side on
which you can add a pin. If you add a pin at a point on the broken line outside of the
connector symbol, the symbol stretches to include the new pin. For shared objects, a
dialog box appears showing the pins available to add to the object.
4. Press the Esc key on your keyboard to stop adding pins.
Related Topics
Moving a Pin
Disconnecting a Conductor from a Pin
Moving a Pin
This topic explains how to move a pin to a new position on its device or connector and how to
swap the positions of two pins on an object. Note that if an object has multiple instances in a
diagram, you can move the pin to another instance of that object.
Note
If a device pin on a parameterized device and a connector pin are connected (mated), they
move together. If you do not want to move them together, you must disconnect them before
moving one. If a wire is attached to the pin being moved, it will move with the pin.
Procedure
1. In the Diagram Window or Design Browser Window either:
• Click on the pin, hold down the mouse button and drag it.
• Right-click the pin and select Move Pin(s)
• Click on the pin, press Space Bar and enter Move Pin(s)
A circle is displayed around the selected pin and any connected pin. Any valid positions
for the pin are highlighted in green and a broken line indicates any positions outside of
the parent object where you could place it. In this case, the parent object will stretch to
include that position.
Figure 4-2. Diagram Highlighting when Moving a Pin
2. Move the cursor to the position where you want to place the pin.
Note
If another pin is connected to the pin that you are moving, a circle indicates the
position the connected pin would take if you moved the pin to the current position of
the cursor.
If you clicked and dragged the pin, release the mouse button.
If you used a menu option to start the action, click once to place the pin.
3. The pin and any connected pin/wire are moved to the new position.
If you are swapping a pin with another pin, the pins swap positions.
If there is connectivity between a pin and a conductor, there is no diamond shape around the pin
in the Diagram Window.
Procedure
1. In the Diagram Window or Design Browser Window, right-click the pin from which you
want to disconnect a conductor.
2. A pop-up menu is displayed. Select Disconnect Selected from the pop-up menu.
Note
Alternatively, you can click on the pin to select it and select the Actions >
Disconnect Selected menu option. When a pin is selected a blue circle is displayed
around it.
3. A diamond is displayed around the pin to show that there is no longer any connectivity
between the pin and the conductor. The conductor and pin do not move within the
Diagram Window but the pin is no longer displayed under the conductor's folder in the
Design Browser Window.
If cross-references have been enabled for pins in the applied style set, then cross-references are
created between the normal pin and their reference pins and other pin instances (It is possible to
have multiple instances).
Non-referenced pins or pin-instances behave differently to referenced pins. See “Adding Pins to
an Object Instance” on page 145.
Note
If the project preference Disallow pin duplication within a design is set, the Make
Non-Reference Pin menu option will not be available for selected Reference Pins
where there is already a non Reference Pin of the same object, as creation of duplicate
pins will be prohibited. To allow the conversion of such Reference Pins the project
preference Disallow pin duplication within a design should be unset.
2. The pin changes to a non-reference instance of the pin. If cross-references have been
enabled on pins, any cross-references next to the instance disappear.
Procedure
1. For example:
You have devices DEV213 and DEV214:
You keep DEV214 as a whole selected, specify that you want to connect the devices
with net conductors and drag DEV214 so that it no longer overlaps DEV213:
The pins that were overlapping are now connected by net conductors.
2. Instead of selecting entire objects, you can select specific instances of overlapping pins.
3. For example:
4. In the above example, the red circles indicate which instances of overlapping pins have
been selected. Any other overlapping pins are ignored when creating connections.
5. You must consider the following when using this functionality:
• If more than two pins (that is, on more than two objects) are overlapping at one point
in the diagram, connections are created from each pin to every other overlapping pin
at that point.
If a pin already has a connection to a second pin and you overlap it with a third pin,
any connection between the first and third pins must use the same type of conductor
as used between the first and second pins.
For example:
DEV213 and DEV214 are connected by a wire conductor. DEV216 has no connection
to anything.
DEV214 is dragged to overlap DEV213 and DEV216 is dragged so that two pins are
overlapping pins on the other devices.
You keep DEV216 selected as a whole, specify that you want to create connections
using net conductors and drag the devices apart.
No new connections are created for the pins connected by the wire conductor.
Connections with net conductors are created between the other overlapping pins.
• If an instance of overlapping pins on the selected objects already has a connection,
this connection remains unchanged when using the functionality to create new
connections between other overlapping pins on the selected objects.
For example:
DEV213 and DEV214 are connected by two net conductors.
You specify that you want to create connections with wire conductors between the
overlapping pins and drag DEV214 so that it no longer overlaps DEV213.
The net conductors remain unchanged but wire conductors are added between the other
pins that were overlapping.
Stacked Pins
You can stack (or group) pins within a single grid location. Such stacked pins support the
creation of single-line block diagrams (also known as interconnect diagrams). You can create
these block diagrams as alternative, or companion views/representations of connectivity
diagrams (wiring or system diagrams).
Note
You cannot stack the pins on a symbol and you cannot use the Update Symbol action for
any pinlists with stacked pins. This applies when any actions attempt to Update Symbol
(that is, assigning a library part, bulk update of library parts, or Find and Replace).
Interaction with these stacked pins support the routing of conductors within highways. Any pin
that is removed from the stack will maintain its connectivity and the conductor is drawn
automatically. Therefore, you can define the connectivity of your block diagrams directly
within the wiring or system view, or by making connectivity edits to an unstacked pin prior to
its insertion into a stack.
Stacked pins can be used on shared and non-shared pinlists (devices and connectors). No single
device pin can be mated to more than one connector object and restricted-usage pins can only be
placed in stacks on diagrams where the pin can be used. Within the stacked pin, or block
diagram, a highway can be used to represent an interconnect (these represent a grouping of
wires or nets). You can manually terminate a highway at a stack of pins. Alternatively, a
highway is created automatically if a pin with a conductor is added to a stack or if you manually
connect a conductor to a stack.
If you draw a conductor between two stacks of pins that are already connected by a highway:
• the conductor is added to the highway and the first un-terminated pin from each stack is
selected
• if there is no un-terminated pin at one end, the conductor is still added to the highway
but standard design rule checks will indicate that conductors are unterminated
• if both stacks have no un-terminated pins, you will not be allowed to complete the action
You can select multiple pins and add them to a single stack or select multiple pins from a stack
for placement outside of it. A stack of pins can contain only one instance of a normal pin. For
example, if a connector has four pins, with multiple instances of PIN4, only four pins are listed
when they are all added to a stack. You cannot add a reference pin to a stack.
Note
When using Capital AutoView Assist for Logic or Capital AutoView Assist for Integrator,
stacked pins are not rendered and you cannot paginate existing designs (using AutoView
Generate Diagrams) if the source diagrams have stacked pin representations. Also, it is not
possible to use a design with stacked pins as a template/prototype for any generated designs or
diagrams.
Within the Design Browser, the stack of pins is named using the number of pins in the stack and
the total number of pins on the object. For example, if two pins are in the stack and there are six
pins in total on the object, the stacked pin is named 2 of 6. In the Design Browser Window,
stacked pins are represented as a collection of pins listed under the device. For example:
In this example, DEV304 has three pins. Two of the three pins (1 and 2) are stacked. Pin 3 is not
stacked.
The appearance of stacked pins can be styled. See the Diagram Styling User Guide for more
information about style sets and how to edit them. There are three default attributes for a stack
of pins that you can use in styling:
• Name
The name of the stack of pins.
• Num Pins
The number of pins in the stack.
• Total Num Pins
The total number of pins on the device/connector.
Procedure
1. Select the pins to be included and either:
• Right-click on a selected pin and select Create Stack.
• Press Space Bar and enter Create Stack.
The mouse cursor changes and possible locations for the stack of pins are indicated by
circles.
2. Click the location where you want to position the stack of pins.
Results
• The selected pins are no longer displayed on the diagram.
• If no conductors are connected to the selected pins, the stack of pins is displayed as a
diamond shape .
• If conductors are connected to the selected pins, they maintain their connectivity and are
placed in a new highway that interfaces with the stack of pins.
• If a pin with a shield termination is added to the stack, the shield termination disappears
from the diagram but the pin retains the connectivity to the shield termination.
• The stack of pins is named using the number of pins in the stack and the total number of
pins on the object. For example, if two pins are in the stack and there are six pins in total
on the object, the stacked pin is named 2 of 6.
Related Topics
Stacked Pins
Adding a Pin to a Pin Stack
Removing a Pin from a Pin Stack
Viewing the Pins in a Pin Stack
Deleting a Stack of Pins
Viewing the Highway Conductors that Terminate at Stacked Pins
Prerequisites
• The pins to be added to the stack must be visible on the object instance.
• The stack of pins must exist. See “Creating a Stack of Pins” on page 159.
Procedure
1. Select the pins to be added and either:
• Right-click on a selected pin and select Add to Stack.
• Press Space Bar and enter Add to Stack.
The mouse cursor changes and the available stacks of pins are indicated by circles.
2. Click the stack of pins to which you are adding the selected pins.
Results
• The selected pins are no longer displayed on the diagram.
• If conductors are connected to the selected pins, they maintain their connectivity. If a
highway already interfaces with the stack, they are added to that highway. If there was
no existing highway, the conductors are placed in a new highway that interfaces with the
stack of pins.
• If a pin with a shield termination is added to the stack, the shield termination disappears
from the diagram but the pin retains the connectivity to the shield termination.
Related Topics
Stacked Pins
Creating a Stack of Pins
Removing a Pin from a Pin Stack
Viewing the Pins in a Pin Stack
Deleting a Stack of Pins
Viewing the Highway Conductors that Terminate at Stacked Pins
Procedure
1. Select the stack of pins in the diagram window or Design Browser Window and either:
• Right-click on it and select Edit Stack.
• Press Space Bar and enter Edit Stack.
Related Topics
Stacked Pins
Creating a Stack of Pins
Adding a Pin to a Pin Stack
Removing a Pin from a Pin Stack
Deleting a Stack of Pins
Viewing the Highway Conductors that Terminate at Stacked Pins
Procedure
Select the stack of pins in the diagram window or Design Browser Window.
• To delete both the stack and individual pins, click the Delete button on your
keyboard.
• To delete only the stack and to retain the pins in the design, click CTRL + Delete on
your keyboard.
Results
• If you deleted both the stack and pins, the stack is removed from the diagram and the
pins are removed from the Design Browser Window.
• If you deleted only the stack, it is removed from the diagram. The pins remain listed as
Unplaced Pins under the device in the Design Browser Window.
Related Topics
Stacked Pins
Creating a Stack of Pins
Adding a Pin to a Pin Stack
Removing a Pin from a Pin Stack
Viewing the Pins in a Pin Stack
Viewing the Highway Conductors that Terminate at Stacked Pins
Related Topics
Viewing the Pins in a Pin Stack
Usages Dialog
To access: Select a stack of pins or highway in the diagram window or Design Browser Window
and either: Right-click on it and select View Usage, or press Space Bar and enter View
Usage.
Used to view which conductors from a highway terminate at which pins in a stack.
Related Topics
Viewing the Highway Conductors that Terminate at Stacked Pins
Video
Creating and Styling Stacked Pins— This video illustrates how to perform the usage
example. Click to view it.
Prerequisites
Project Quick Start - Aerospace Interactive has been imported and design Logical 2, diagram
Diagram1 is open in Capital Logic
The following Usage Examples are available below- note that each example builds on the
previous one.
Procedure
1. In the following steps you will create a stacked pin using Pins +28V DC and GND on
device DEV10.
2. Right-click on Pin +28V DC and select Create Stack from the popup menu.
3. The available pin positions to create the stacked pin display in green. Click the desired
position to place the stacked pin.
Place the stacked pin at the available space below pin +28 DC.
Pin +28 DC is added to newly created stacked pin 1/5 (the name denoting that this
stacked pin contains one of the five pins on this device) and is no longer displayed.
Conductor COND100 has been placed in the automatically created Highway HW202.
Add Pin GND to the stacked pin 1/5 by selecting it and then right-clicking Add to Stack
from the popup menu.
.
Viewing the Composition of a Stacked Pin
This section of the usage example runs through the steps for viewing the composition of a
stacked pin.
Procedure
1. To view the composition of the stacked pin: right-click on the stacked pin 2/5 and select
Edit Stack.
The Edit Stack dialog displays as below. Pin Names +28 DC and GND display in the
Pin Name
column.
Procedure
1. To view the conductors in the highway: right-click on the highway HW202 and select
View Usage. Note the Usages dialog displays the conductors COND100 & COND101
present in the
Highway
Procedure
1. In the following steps you will change the displayed name of the stacked pin 2/5 via
Styling. This is done via Composite Text.This will change the naming format on all
stacked pins
2. Highlight stacked pin 2/5 and select Shift +E (this command opens the styling dialog of
the currently selected object type, in this case Stacked Pin
3. Expand the tree view to the Composite Texts level as below and click NumPins + “/” +
TotalNumPins
5. The Edit Composite Text dialog displays. This dialog is used to configure the
displayed name format of the styled stacked pin (2/5) you have been working with. The
format is built up in the Entries panel and is defined from the Attributes and free
text
6. In the Text field add the word StackedPin and click the Add button
7. The Text is added to the Entries panel. Select the text and move it to the top of the list
with the Up button and Press OK
8. The basic tab displays with the revised name updated in the Composite Text panel. Press
OK
The diagram is updated, the name of the stacked pin displays in the new format
StackedPin 2/5. Note this new name format will only be applied to any other stacked
applied
The following sections describe how to create, add and manage devices and connectors,
including shared devices and connectors in designs.
Creating a Device in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Adding a Device from Capital Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Preserving Connectivity and Assisting Object Placement . . . . . . . . . . . . . . . . . . . . . . . . 184
Preserving Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Preserving Imported Connectivity and Using Assisted Placement . . . . . . . . . . . . . . . . . . 184
Adding a Shared Device/Connector/Splice to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . 186
Adding a Shared Device, Plug, Receptacle, Ring Terminal, or Inline Connector to a Diagram
187
Adding a Shared Splice to a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Editing Shared Devices and Shared Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Joining Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Associating a Symbol with a Shared Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Removing the Association Between a Symbol and a Shared Object . . . . . . . . . . . . . . . . . 194
Adding a Pin to a Shared Pin List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Removing a Pin from a Shared Pin List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Renaming a Pin in a Shared Pin List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Converting a Reserved Pin to an Unrestricted Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Converting an Unrestricted Pin to an Automatic Reservation Pin . . . . . . . . . . . . . . . . . . . 196
Creating a New Revision of a Shared Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Creating a Revision of a Shared Object in Capital Logic. . . . . . . . . . . . . . . . . . . . . . . . . . 197
Swapping Out Shared Objects for a Compatible Revision . . . . . . . . . . . . . . . . . . . . . . . 198
Cross-References on Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Cross-References and Composite Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Setting up Project Preferences for Cross-references. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Viewing Another Instance of an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Changing the Home Instances of an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Changing an Instance of an Object to a Home Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Changing a Home Instance of an Object to a Normal Instance . . . . . . . . . . . . . . . . . . . . . 204
Promoting a Device/Connector/Modular Connector/Ring Terminal/Splice to a Shared
Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Promoting a Device/Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Promoting a Splice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Creating a Shared Device Based on a Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
4.
Note
If you place a device across the path of a conductor, pins are automatically created
where the conductor enters and exits the device. The conductor is broken and a new
conductor with the same properties is created on one side of the device. The two
conductors are attached to the pins.
This also applies to multicores and overbraids. They are split and retain their structure
on both sides of the new device. If there are shields and daisy chains attached, they
remain connected to the same pins but may belong to the newly created multicore or
overbraid. If the existing multicore or overbraid belongs to an assembly, the newly
created multicore or overbraid also belongs to that assembly.
Tip
If you wish to create a horizontal connector (top/bottom pin location) instead of the
vertical (left/right pin location) then, after the first click of the mouse which places
the first corner of the connector, press R on the keyboard to rotate the direction of the
connector, before performing a second click of the mouse to set the opposite corner and
place the horizontal connector. This command can also be used to rotate the drawing of
ring terminals, inline connectors and devices.
Related Topics
Editing the Properties of Objects
Resizing a Device or Connector
Note
When placing a symbol in a diagram, you can rotate the symbol by pressing the R
key on your keyboard and you can flip it by pressing the F key on your keyboard.
If the device does not have a symbol, the mouse cursor has a little device symbol next to
it. Click once to place the first corner of the device and then move the cursor to where
you want to place the opposite corner of the device and click once.
If you are auto-generating the pin placement, the pins are added to the device
automatically. If you are placing the pins manually, the cursor changes so that it has a
little pin symbol next to it.
As you move the cursor over the device, it changes appearance. Where a pin can be
added, it looks like this: .
Where a pin cannot be added it looks like this: .
You can add a pin at a grid point on an edge of the device. You can also add a pin
outside of the graphical representation of the device, the device stretches to include the
new pin.
Click once to place each pin.
7. The device is added to the diagram and to the Design Browser Window. In the Design
Browser Window, a normal device is indicated by the icon and a symbol for a ground
device is indicated by the icon . Any device that has a part number from Capital
Library assigned to it also has a red tick by the symbol.
Preserving Connectivity
The system allows you to import connectivity from other MCAD designs and retain the
connectivity for the objects, including devices, connectors and so on, as it was originally
specified. This methodology automates the connectivity process and enables an accurate
representation of the imported design.
Further functionality assists the optimal layout of the design when you place the imported
connectivity objects onto the diagram. Shadow graphics display the proposed connectivity
between options enabling you to easily view the originally defined routing and tweak this where
required. This assisted placement is also available when unplacing objects.
Tip
User CTRL-DEL to remove (unplace) object from the diagram into the Unplaced folder
then use the process to optimally place them back on the diagram.
Capital User Guide for further information. Note: Do not select the Autoview Diagram
Generation option.
2. Once the Import process completes, imported components are added to the “Unplaced”
folder of the relevant object.
3. Place objects from these folders on to your diagram using the Place Dialog. If the object
already has a symbol defined in the Capital Symbol library then click Symbol Selection
on the Place dialog to use it on the diagram.
4. Continue adding objects to the diagram. As more objects are added ghost connection
graphics (including any multicore connectivity) are added between connected objects
reflecting the original imported design definition and to assist in optimizing diagram
layout.
Results
Once all imported objects have been placed and the connectivity rendered save the design.
Tip
It is possible to reuse connectivity by selecting the required objects and pressing CTRL-
DEL to remove them from the diagram back into the Unplaced folder. You can then
optimally place them back on the diagram using the method described above.
Under certain circumstances, an object (a net, wire, multicore, device, connector, inline, ring
terminal, overbraid or splice) on a design's schematic diagram must share its connectivity across
more than one design in a project.
For example:
It may be necessary for two separate harnesses (from separate designs in a project) to connect to
one device. You would therefore create the device as a shared device.
Shared devices and connectors (including shared ring terminals) behave differently than
standard devices and connectors; in addition to placing the component, the pins to be reserved
for that instance of the device or connector must be specified. Because the device / connector is
shared, any instances of it in any other diagram may only choose from the remaining available
pins, unless the pins in the shared object are specifically designated as Reusable Pins. You can
also add reference pins to an instance of a shared object. See “Overview of Reference Pins” on
page 152 for more information about reference pins.
If a shared object has symbols associated with it, you can add a symbol as an instance of the
object. In any case, you can select pins from the pin list for the shared object and add those to an
instance of the shared object as a parameterized object. See “Adding a Shared Device, Plug,
Receptacle, Ring Terminal, or Inline Connector to a Diagram” on page 187 for information
about adding those shared objects to a diagram.
Shared splices can be created in Capital Project either with or without a plugmap. A shared
splice without a plug map is a shared pin list that has a single unrestricted pin. You cannot
reserve the pin for a design. A shared splice with a plug map can have multiple unrestricted
pins. See “Adding a Shared Splice to a Diagram” on page 189.
When shared pin lists, conductors and multicores are created in Capital Project, they can be
assigned an abstraction level. The Shared Objects Browser Window displays all shared
objects in all abstractions.
Note
If a shared object is frozen, a blue snowflake is displayed on the icon for the shared object.
See “Freezing and Unfreezing Shared Objects” on page 447 for more information about
frozen shared objects.
Video
A short example detailing how to add ring terminals and assign library parts to them
is contained within the video link in “Generating Harness Connectors on a Device”
on page 218.
2. The Add Shared Object facility is displayed. If you have used the menu options to
access the facility, you must select the shared object that you want to add from the
Current Shared Object box.
3. You must select whether you want to add particular pins to the instance of the object or
whether you want to add an instance as a symbol (if a symbol is associated with the
shared object).
If you want to add the instance as a symbol, skip to step 4. If you want to add particular
pins and not use a symbol, continue with this step.
Select the Pin Selection option. The plug map for the shared object is displayed in the
Plug Map window. The pins currently available for that device / connector (if any)
appear in the Available Pins box.
Note
If you want to add a shared device with reference pins, check the Reference box. All
pins for that device are then displayed in the Available Pins window. You can only
add reference instances of pins or non-reference instances of pins to the object when you
first add it to a diagram. You can, however, convert non-reference instances to reference
instances and vice versa later. See “Overview of Reference Pins” on page 152.
Hold down the CTRL key on your keyboard and select pins in the Available Pins
window to allocate them to this instance of the shared object.
Tip
If you want to place all the selected pins on the object as a stack, check the Place as
Stack box instead of having to hold down the CTRL key. The placed, stacked pins
can be styled using the Styling dialog.
If you want the pins to be sized and placed automatically on the instance in the diagram,
check the Auto-Generate box. If you want to place the pins manually, do not check the
Auto-Generate box.
Go to step 5.
4. If you want to add the instance using a symbol, select the Symbol Selection option. Any
associated symbols are displayed in the Symbols window. The Symbol Selection option
is grayed out if there are no symbols associated with the shared device.
If the shared object has been created using a composite symbol, the available symbol
blocks are listed in the Symbols window. See Overview of Composite Symbols in the
Capital Symbol User Guide for more information about composite symbols.
Select the symbol or symbol blocks that you want to use for the instance of the diagram.
If a symbol is not available it is grayed out.
Note
A symbol or symbol block can contain more than one pin. When you select a symbol
or symbol block, you automatically select all of the pins on it.
If you want to add a shared device with reference pins, check the Reference box. When
you add the symbol or symbol blocks to the diagram, all of the pins will be reference
pins. You can, however, convert non-reference instances to reference instances and vice
versa later. See “Overview of Reference Pins” on page 152 for more information.
5. After you have finished making your selections, click the OK button to close the dialog
box.
6. You are adding the instance with a symbol, click on the position where you want the
symbol to be placed. If you have selected multiple symbol blocks, you place each block
separately.
Otherwise, draw the shared component on the diagram in the desired location by
clicking once to place one corner, then dragging the mouse to define the object's shape.
If you did not check the Auto-Generate box, Capital Logic will prompt you to place
each of the pins (in numerical order that you selected for this instance of the shared
object. You can place a pin on any side of a shared object, but not a corner or inside the
object. The shared object will be set when the last pin is placed.
Examples
When you create more than one instance of a shared object, cross-references are displayed next
to the instances in the diagram. See “Cross-References on Objects” on page 199 for more
information about cross-references.
If you abort placement of a shared object during pin placement, all the pins placed thus far are
added to the object, but the remaining pins are not placed (and are also unreserved for that
object instance). You can use the Pin action to add pins to a shared device. Any properties
created on the shared object and its pins are also transferred to each instance of the shared object
in the diagram(s).
See “Overview of Reference Pins” on page 152 for more information about reference
pins.
2. Position the mouse cursor over the position where you want to place the splice and click
once to place it. If the shared splice has been created with a plug map, the grayed-out
symbol is displayed to help placement.
3. The shared splice is added to the diagram and to the browser tree in the Design Browser
Window.
Note
When you create more than one instance of a shared object, cross-references are
displayed next to the instances in the diagram. See “Cross-References on Objects”
on page 199 for more information about cross-references. If you copy a shared splice,
the instance that you then paste is not shared. However, you can promote it to a shared
splice.
Related Topics
Cross-References on Objects
Modular connectors are displayed as a separate node in the Shared Objects Browser window
containing all modular connectors and associated sub-connectors. The modular tab is available
by right-clicking on the modular connector and selecting Edit Shared Plug. See “Assigning
Connector Positions Using the Modular Tab” on page 443.
You can edit a shared device or connector/modular connector/ring terminal in the following
ways:
• Associate a symbol with the shared object and associate the pins from the symbol with
the pins on the shared pin list. See “Associating a Symbol with a Shared Object” on
page 192.
• Remove the association between a symbol and a shared object. You can do this only if
none of the pins mapped to that symbol have been used. See “Removing the Association
Between a Symbol and a Shared Object” on page 194.
• Add or remove pins from the shared pin list for the shared object. See “Adding a Pin to a
Shared Pin List” on page 194 or “Removing a Pin from a Shared Pin List” on page 195.
• Convert reserved pins (automatic reservation or manually reserved) to unrestricted pins
and vice versa. See “Converting a Reserved Pin to an Unrestricted Pin” on page 195 or
“Converting an Unrestricted Pin to an Automatic Reservation Pin” on page 196.
Joining Objects
This topic describes how to select and join together pin lists of the same name and object type,
thereby speeding up design modification and clean up.
It is used to rejoin in-line connector, device and connector pin lists which have either been
manually split, or after a CAVAI or CAVAL operation.
• The first object selected becomes the anchor point for the unified object.
• If any graphical properties are assigned to object instances and that instance is the first
selected then, the properties will be ascribed to the newly unified object.
• The action works on both normal oriented and rotated objects.
• To select multiple objects, draw a square around the objects on the diagram that you
wish to join together.
Procedure
Right-click on the instance or instances of the object that you wish to join together and select the
Join option from the pop-up menu. Alternatively select the objects use the keyboard shortcut J.
Results
The selected pin lists are joined together.
Note
There are a number of reasons why the Join action could fail:
Note
For shared devices, the symbol is added to the symbols associated with the shared
device. For shared connectors, the symbol becomes the single symbol associated
with the shared connector and replaces the existing associated symbol if there is one.
For shared connectors, the symbol must have at least as many pins as the shared
connector. For shared devices with library parts, the symbol must have exactly the same
number of pins as the shared device.
A symbol can be associated multiple times with a shared object for the purpose of
mapping multiple sets of pins to the same symbol.
If there are no symbols that can be added to the shared device or connector, the Symbols
tab is not displayed.
3. On the Associate Pins tab, you must associate pins from the symbol with pins on the
shared pin list. Note that if you have not selected a symbol on the Symbols tab, the Pins
tab is displayed instead of the Associate Pins tab.
The Symbol window lists the pins on the symbol. The Shared window lists the pins in
the shared pin list.
You can either associate all of the pins from the symbol with pins on the shared object
by clicking the Associate All button or you can associate one pin at a time. To do this,
select the pin in the Symbol window, select the shared pin in the Shared window and
click the Associate button.
All pin from the object instance must be associated with pins on the shared pin list if you
want to continue with promoting the object.
You can disassociate all of the pins for the current instance by clicking the Disassociate
All button or you can disassociate one pin by clicking on the shared pin in the Shared
window and clicking the Disassociate button.
You can remove a pin from the shared pin list by clicking on it in the Shared window
and clicking the Delete button.
You can rename a pin in the shared pin list by clicking on it in the Shared window and
clicking the Rename button.
You can add pins to the shared pin list by clicking the New button. This displays the
Add Shared Pins facility. You must specify the following:
• Pin Name Prefix - a prefix that will be displayed at the start of the pin names on the
new pins.
• Start Index - the number that you want the first new pin to have in its name after the
prefix. The other new pins will follow on from this number.
• No of Pins - the number of new pins that you want to add.
Click the OK button to add the pins and to return to the Shared Object facility.
4. Click the OK button to save your changes and to exit the Shared Object facility.
Procedure
1. Right-click on the shared object and select the Edit Shared Object option from the pop-
up menu or select the shared object and click the Edit Shared Object ( ) toolbar icon
in the Shared Objects Browser Window.
2. The Edit Shared Object facility is displayed. Click the Symbols tab. In the browser
tree, click on the symbol that you want to remove. Click the Remove button.
3. The symbol is removed from the tree. Click the OK button to exit the facility.
Procedure
1. In the Shared Object facility, click the Pins tab or Associate Pins tab, click on the pin
and click the Delete button.
2. The pin is removed from the shared pin list. Click the OK button to exit the Shared
Object facility.
Reservations tab is not available if the shared object has a library part and if all of its
pins are already unrestricted.
If you want to convert multiple pins, you can hold down the Control key on your
keyboard and click them to select them.
Note
If you want to convert all of the pins in the shared pin list to unrestricted pins, you
can click the Add All button without selecting any pins.
3. The pin is added to the Unrestricted Pins window. Click the OK button to exit the
Shared Object facility.
Note
If you want to convert multiple pins, you can hold down the Control key on your
keyboard and click them to select them. If you want to convert all of the unrestricted
pins in the shared pin list to reserved pins, you can click the Remove All button without
selecting any pins.
3. The pin is added to the Automatic Reservations window. Click the OK button to exit
the Shared Object facility.
See the Capital Project help system for more information about creating a revision in that
application.
Note
If you have a shared device with shared harness connectors, you can create revisions for the
device and the connectors separately.
Special conditions apply for editing shared modular connectors, see “Sharing a Modular
Connector” on page 226 for further information.
2. The Create Revision facility is displayed. You must enter a unique name and revision
combination. You can either keep the previously used name, enter a new name or click
the ellipsis (...) button to select a name that has been defined in Capital Project.
If you enter a combination that is already in use, the text changes to red. You cannot edit
the Short Description field.
If you want to swap out the original shared object revision for the new revision in
designs, select Swap Out Revision.
3. Click the OK button to exit the facility. The new revision is listed under the original
shared object revision in the Shared Objects Browser Window. If you selected Swap
Out Revision, the Swap Out Revision Dialog [2] is displayed where you select the
design revisions in which you want to swap out the shared object revisions. See
“Swapping Out Shared Objects for a Compatible Revision” on page 198 for more
details.
Related Topics
Swapping Out Shared Objects for a Compatible Revision
Cross-References on Objects
When you create more than one instance of a shared object or design wide object, cross-
references are displayed next to the instances in the diagram by default. Cross-references can
also be displayed for re-usable pins on a pin list but they are not by default. The display and
styling of cross-references is controlled using style sets, see the Capital Diagram Styling User
Guide for further information.
You can also use Project Preferences to control whether cross-references are displayed for pin
lists, conductors and pins, however this is to support legacy user-flow cases and the
recommended best practice is that the style set control method should be used. See “Setting up
Project Preferences for Cross-references” on page 201 for more information.
Note
If you release a design, then close the project in Capital Logic and then re-open the project
and design, the cross-reference text becomes invisible.
If you want to override the Project Preferences related to the display of cross-reference text, you
can edit the cross-reference properties for an instance of an object. To do this, right-click on the
instance of the object in the diagram and select the Properties option from the pop-up menu.
See “Editing the Graphical Properties of Cross-References” on page 441 for more information
about the properties on the Cross-references tab of the Edit Properties facility.
The first instance of an object that you created is the home instance by default. The locations of
all other instances of the object are displayed next to the home instance.
The location of the home instance is displayed next to all other instances of the device. You can
have more than one home instance and change which instances are home instances. See
“Changing the Home Instances of an Object” on page 204 for more information.
By default, each cross-reference both for the home instance or other instances are in the format:
/{DESIGN.NAME}:{DIAGRAM.NAME} {ZONE}
For example:
/Audio:Audio_1 3-D
In this example, the cross-reference indicates that there is an instance of the device in the
diagram Audio_1 of the design Audio. In the diagram Audio_1, the instance is in the zone 3-D.
A zone is only displayed if the diagram has a border that uses zones. See Adding Zone Areas
to a Border in the Capital Symbol User Guide for more information.
When a build list is active, any cross-references in the designs in the build list will list only
those instances in designs on the active build list. Cross-references in designs not in the active
build list show all instances. If there is no active build list, cross-references show all instances.
If a net conductor is part of an equivalence set, the cross-reference text lists the designs and
diagrams names in which any of the other shared net conductors in the same equivalence set
have been placed. Therefore, the cross-reference text also includes the name of the other net
conductor.
For example:
/Audio:Audio_1 3-D:Net-2
In this example, the net conductor Net-2 is in the same equivalence set as the net conductor by
which the cross-reference is displayed. The cross-reference indicates that there is an instance of
the net conductor Net-2 in the diagram Audio_1 of the design Audio. In the diagram Audio_1,
the instance of Net-2 is in the zone 3-D.
See “Overview of Shared Net Conductor Equivalence Sets” on page 292 for more information
about equivalence sets.
See “Cross-reference Rules for Pins” on page 152 for further information on the rues that apply
for pins.
If you are viewing an instance of an object, you can jump to another diagram where another
instance of an object is. See “Viewing Another Instance of an Object” on page 203.
Note
When you create, move or delete instances of the shared object, the cross-references refresh
automatically. However, if somebody is working on the project in a separate session of
Capital Logic, any changes to instances of the shared object that they make will not be refreshed
automatically in your session. You can manually update cross-references by pressing Space Bar
and entering Refresh Shared Objects.
• By default, any instance of a block from a composite symbol is not set as a home
instance.
• If a connectivity object has been placed on the diagram using instances of the complete
composite symbol, instances of blocks from the composite symbol, and instances of
parameterized devices (that is, instances drawn without using a symbol), all of these
instances reference each other.
• A composite symbol can have additional cross-reference placeholders on the symbol
blocks in it. If such placeholders exist, the references pointing to other instances of the
same block are grouped together and listed at those placeholder locations. If no such
placeholders are available, these references appear at the location of the cross-reference
placeholder for the composite symbol.
• If a composite symbol or block does not have cross-reference placeholders defined in
Capital Symbol, the cross-reference is created based on either Project Preferences or the
applied style set (depending on the Project Preference setting: Project Preferences >
Capital Logic > Diagram node > Use Style-Set Cross-reference).
• If a block within the composite symbol does not have a cross-reference placeholder
defined in Capital Symbol, no new placeholder for that block is created when the block
is placed in a diagram (irrespective of the Project Preferences or the applied style set).
Check the box to enable the field. Specify the maximum number of lines that can be
in a block of cross-references in a diagram. If the number of cross-references for an
instance of a shared object is greater than this value, the cross-references are
displayed in multiple blocks. If you move a cross-reference in a block to another
location in a diagram, all of the cross-references in that block move with it. Cross-
references in other blocks for that instance do not move.
• Template - specify the format of the cross-references. The format is specified as a
string that combines text with references to variables. The system interprets text
encased by curly brackets as a variable. This will be replaced by the appropriate
value in a cross-reference. Valid variables are as follows:
o DESIGN.* where * is the name of a design attribute
o DIAGRAM.* where * is the name of a diagram attribute
o ZONE - the x, y coordinates of the zone where the other instance is located
o ZONE.X - the x coordinate of the zone where the other instance is located
o ZONE.Y - the y coordinate of the zone where the other instance is located
o EQUIVALENTNET - if a net conductor is part of an equivalence set and you
specify this variable in the format, the cross-reference text will also include the
name of the other net conductor from the equivalence set.
For example, you could have the format:
/{DESIGN.NAME}:{DIAGRAM.NAME} {ZONE.X}:{EQUIVALENTNET}
If a net conductor Net-2 is in the same equivalence set as the net conductor by which
the cross-reference is displayed and if Net-2 is in the zone with an X coordinate of 3
in the diagram Audio_1 of the design Audio, the cross-reference would be:
/Audio:Audio_1 3:Net-2
Note
The Preview box displays how the text will appear but not to scale.
The first instance that you created is the home instance by default. The locations of all other
instances of the object are displayed next to the home instance. The location of the home
instance is displayed next to all other instances of the device.
You can have more than one home instance and change which instances are home instances. If
you have more than one home instance, the locations of all other instances (both home instances
and other instances) are displayed next to a home instance. All home instances are displayed
next to other instances.
If you are viewing an instance of an object, you can jump to another instance in another
diagram. See “Cross-References on Objects” on page 199 for more information about how to do
this.
2. The instance changes to a normal instance and the locations of all home instances are
displayed next to it.
Related Topics
Adding a Shared Device/Connector/Splice to a Diagram
Cross-reference Rules for Pins
Cross-References on Objects
Promoting a Device/Connector/Modular
Connector/Ring Terminal/Splice to a Shared
Object
Capital Logic supports the promotion of an existing, non-shared device, connector, modular
connector, ring terminal or splice to be defined as shared. The shared objects, once promoted,
can be shared with other diagrams in the same design (but not across designs). The properties of
the instance will also be migrated onto the shared object, as well as the symbol if an existing
symbol map is used.
When you promote an object, you can either create a new shared object or promote the object
into an existing shared pin list.
You can promote a device that has been added to a diagram using a symbol into an existing
shared pin list. When you promote it, the symbol is added to the shared device's set of symbols.
• If the number of pins on the shared pin list is greater than the number of pins on the
library part, the library part association is removed.
• If both the shared pin list and the object instance have valid library part descriptions, the
library part description on the object instance is removed.
You can also create a shared device based on a symbol. See “Creating a Shared Device Based
on a Symbol” on page 209
Promoting a Device/Connector
This topic describes how to promote a device or connector.
Procedure
1. First create a device or connector (including modular connector or ring terminal) as
normal. See “Creating a Device in a Diagram” on page 181, “Adding a Modular
Connector” on page 224 or “Creating a Harness Connector In a Diagram” on page 219.
2. Select the new device or connector, then press Space Bar and enter Share. Alternatively,
right-click on the object and select the Share option from the pop-up menu.
3. The Share dialog box appears, which is a multi-tabbed dialog. On the Shared Device
tab, you must specify the following:
• Create New - Select this if you want to create a new shared object. You must also
specify a name and revision for the object. If you want the name to be fixed check
the Fixed box.
• Share Into - Select this if you want to promote the object into an existing shared
object. You must select the existing shared object by clicking on it in the window
below the Share Into option.
Note
The Share Into action is not available when sharing modular connectors.
4. On the Associate Pins tab, you must associate pins from the object instance that is being
promoted with pins on the shared pin list.
The Instance window lists the pins on the object instance that is being promoted. If you
are creating a new shared object with a new shared pin list, the Shared window lists the
same pins as on the instance that is being promoted. If you are promoting the instance
into an existing shared pin list, the pins from the existing shared pin list are listed in the
Shared window.
Pins that are reserved to this design or are not reserved to any design are displayed in
bold and can be associated with a pin on the diagram. Once a pin (that is not
unrestricted) is associated with a pin on an instance, it becomes reserved to this design
and it is grayed out. Unrestricted pins are displayed in bold and in italics.
You can either associate all of the pins from the instance with pins on the shared object
by clicking the Associate All button or you can associate one pin at a time. To do this,
select the pin in the Instance window, select the shared pin in the Shared window and
click the Associate button.
All pin from the object instance must be associated with pins on the shared pin list if you
want to continue with promoting the object.
You can disassociate all of the pins for the current instance by clicking the Disassociate
All button or you can disassociate one pin by clicking on the shared pin in the Shared
window and clicking the Disassociate button.
You can remove a pin from the shared pin list by clicking on it in the Shared window
and clicking the Remove button.
You can add pins to the shared pin list by clicking the Add button. This displays the
Add Shared Pins facility. You must specify the following:
• Pin Name Prefix - a prefix that will be displayed at the start of the pin names on the
new pins.
• Start Index - the number that you want the first new pin to have in its name after the
prefix. The other new pins will follow on from this number.
• No of Pins - the number of new pins that you want to add.
Click the OK button to add the pins.
5. Optionally, you can use the Pin Reservations tab to set one or more of the pins to be
unrestricted. The automatic reservation pins from the shared pin list are displayed in the
Automatic Reservations window. Click on the pin that you want to make unrestricted
and click the Add button. If you want to make all of the pins unrestricted, click the Add
All button.
The new unrestricted pins are displayed in the Unrestricted Pins window.
6. Press OK to promote the instance and save it as a shared object / connector. The shared
object / connector can now be selected with the appropriate Add Shared ribbon actions.
Note
When you create more than one instance of a shared object, cross-references are
displayed next to the instances in the diagram. See “Cross-References on Objects”
on page 199 for more information about cross-references.
Promoting a Splice
This topic describes how to promote a splice.
Note
An instance of a splice symbol on a diagram can be promoted to a shared splice. A splice
using a symbol can only be promoted into a shared splice if it has the same symbol as the
shared splice. A shared splice cannot have pins or a symbol added to it after it has been
promoted.
Procedure
1. First create a splice as normal. See “Creating a Splice in Capital Logic” on page 277.
2. Click on the splice in the Design Browser Window or in the diagram window, press
Space Bar and enter Share. Alternatively, you can right-click on the splice and select the
Share Splice option from the pop-up menu.
3. The Share Splice dialog box is displayed.
If you are creating a new shared splice, select the Create New option and enter a name
for the shared splice in the Name box and click the OK button. Note that you can check
the Fixed box if you want the name to be fixed.
If you want to promote the splice instance into an existing shared splice, select the
Share Into option and select the shared splice in the window below the option.
4. The splice is promoted to a shared splice. If you have created a new splice, it is added to
the Shared Objects Browser Window.
Note
When you create more than one instance of a shared object, cross-references are
displayed next to the instances in the diagram. See “Cross-References on Objects”
on page 199 for more information about cross-references.
You can disassociate all of the pins for the current instance by clicking the Disassociate
All button or you can disassociate one pin by clicking on the shared pin in the Shared
window and clicking the Disassociate button.
You can remove a pin from the shared pin list by clicking on it in the Shared window
and clicking the Remove button.
You can add pins to the shared pin list by clicking the Add button. This displays the
Add Shared Pins facility. You must specify the following:
• Pin Name Prefix - a prefix that will be displayed at the start of the pin names on the
new pins.
• Start Index - the number that you want the first new pin to have in its name after the
prefix. The other new pins will follow on from this number.
• No of Pins - the number of new pins that you want to add.
Click the OK button to add the pins.
4. Optionally, you can use the Pin Reservations tab to set one or more of the pins to be
reusable. The automatic reservation pins from the shared pin list are displayed in the
Automatic Reservations window. Click on the pin that you want to make unrestricted
and click the Add button. If you want to make all of the pins unrestricted, click the Add
All button.
The new unrestricted pins are displayed in the Unrestricted Pins window.
5. Press OK to create the shared device and place the symbol on the diagram to create the
first instance of it.
Related Topics
Adding a Shared Device/Connector/Splice to a Diagram
Cross-References on Objects
points and normal device positions may change. Therefore, you would have to change
all of the ground connections in your system schematics.
Related Topics
Ground Wiring Flow Using Ground Design Functionality
Ground Wiring Flow Using Shared Objects
• By adding a device with a footprint and a symbol directly to a Capital Logic diagram.
See “Adding a Device from Capital Library” on page 182 for more information on how
to do this.
• By assigning a library description to a device that has been created in the diagram. See
“Editing an Object's General Properties” on page 406 for more information on how to do
this.
Harness Connectors
In addition to adding a device with a harness connector footprint to a Capital Logic diagram,
you can add a harness connector directly to a Capital Logic diagram.
See “Creating a Harness Connector In a Diagram” on page 219 for more information about
doing this. If you do this, you are able to see the harness connector in the diagram.
If you add a device with a harness connector footprint to a Capital Logic diagram, whether
harness connectors are generated automatically or not depends on a setting for the design
abstraction of the design.
If the design has an abstraction for which the Allow auto-creation of harness connectors
option has been selected in Capital Project, harness connectors are created automatically
according to device library definitions. If this option has not been selected for the design’s
abstraction, no harness connectors are generated automatically.
If they are not generated automatically, you can generate the harness connectors manually for
any unmated pins after you have added pins to the device. See “Adding Pins to an Object
Instance” on page 145 for more information about adding pins to an object and see “Generating
Harness Connectors in Capital Logic” on page 217 for more information about generating
graphical representations of the harness connectors on a device with a footprint.
Device Connectors
You can add a device connector to a Capital Logic diagram by:
• Adding a device with a device connector footprint directly to the diagram (see “Adding
a Device from Capital Library” on page 182).
• Assigning a library description to a device that has been created in the diagram (see
“Editing an Object's General Properties” on page 406.
When you add a device with a device connector footprint to a Capital Logic diagram, the device
connectors are graphically represented inside the symbol for the device and are listed under the
device in the Design Browser Window.
The placement of the graphical representation of the device connectors in a device follow these
rules:
• Pins on the same side of the device symbol are separated into groups based on the device
connector of which they are part.
• If there are multiple groups per side, there are multiple device connectors on that side.
• If a device connector is split into multiple groups, all connectors that are part of the
larger group are drawn 'broken'.
Capital Logic will always create the correct set of device connectors for a footprint. The
appearance depends on the symbol that is used for the device. You can set Project Preferences
in Capital Project to limit the width of the device connectors in the diagram window.
The names of the device connectors do not have to be unique in a diagram. For example, a
connector J1 on a device DEV1 is different to a connector J1 on a device DEV2.
The pin types for each pin on the connector are taken from the library part definition for the
device and not from the connector.
Conductors connect to the device pin and therefore keep the internal mapping separate to the
external mapping.
You can move pins and swap their positions on the device symbol in the Capital Logic diagram.
See “Moving a Pin” on page 149 for more information on how to do this.
You can select a device connector and move it but the device moves with it. You cannot move
the device connector itself within a device.
You can add properties to a device connector (and to device connector pins) but there are
restrictions because there is no graphical representation of the device connector pin:
• Any properties that have come from the Capital Library definition of the device are
fixed.
If the footprint for the device is changed in Capital Library, the instance in Capital Logic is
updated only if you right-click on the instance in the Capital Logic diagram and select the
Update Instances option from the pop-up menu.
If the library part for the device connector or the footprint is changed in Capital Library, an
update in Capital Logic is possible only if the symbol for the devices library part is the same.
Devices that currently have a library part with a symbol will restrict the selection of a new
library part to only those library parts that use the same symbol.
There is a project preference to define whether the device pin names or the device connector pin
names are displayed graphically in Capital Logic. This cannot be defined individually for each
device instance. See “Project Preferences” on page 68 for more information on defining project
preferences.
Note
The system will only generate harness connectors on designs that have the same abstraction
and are within the same build list.
If the Allow auto-creation of harness connectors option has not been selected for the design’s
abstraction, no harness connectors are generated automatically.
If they are not generated automatically, you can generate the harness connectors manually after
you have added pins to the device. See “Adding Pins to an Object Instance” on page 145 for
more information about adding pins to an object.
Note
Automatically generated harness connectors cannot be edited manually (for example, pin
changes and plug deletion). Only manually generated connectors can be edited.
When you generate them manually, the harness connector graphics are generated around the
pins that have been added to the device and are labelled with the harness connector name.
For example:
Pins 1 and 2 on the device should be mated with harness connector conn01 of the device
footprint, pins a, b and c should be mated with harness connector conn02 of the device
footprint.
Where possible, the system generates one harness connector graphic for multiple pins from one
harness connector (as in the case of pins 1 and 2 or pins b and c in this example).
Note
If conductors have been connected to pins on the device, they will connect automatically to
the harness connectors after they have been generated. If you have two devices with the
same library part and generate harness connectors, then this can result in two shared connectors
with the same name.
Note
If you generate harness connectors for a device, then add more pins to the device and
generate harness connectors again, any existing harness connector graphics remain
the same. They do not extend to include new pins. Instead, the new pins have their own
separate harness connector graphics. If you want groupings of previously existing and
new pins to share the same harness connector graphic, you must delete any existing
harness connector graphic for those pins before generating harness connectors again.
If you are using Generate Harness Connectors to automatically mate ring terminals to a
stud pin the system selects the desired ring terminal based on the device’s housing
definition information, as well as considering the connected wire(s) (gauge and multi-
termination), whilst honoring scope and material drivers and factor - a priority number
specifying selection order where more than one ring terminal is available. For further
information see Ring Terminal Groups in the Capital Library User Guide.
Video
Ring Terminals — This video details how to use the Generate Harness Connectors
action to assign the correct ring terminal for wire and stud specifications, as well as
how to add symbols and ring terminals, assign library parts to ring terminals and convert
pins to studs. Click to view it.
Related Topics
Overview of Device Connectors and Harness Connectors in Capital Logic
Procedure
1. Press Space Bar and enter Add Plug, Add Ring Terminal, or Add Receptacle.
Note
You can only mate a plug or ring terminal with a device.
2. Position the mouse cursor over a grid point where you want to place one corner of the
device.
3. Drag the mouse away to place the opposite corner of the device. A gray rectangle is
displayed, along with the dimensions of the device and the number of pins that can fit on
the device. Drag the mouse until the rectangle is the size that you want the device to be
and click the grid point where you want to place the opposite corner.
Note
If you hold CTRL during the second click, pins are automatically added to the
connector. If the connector touches a device, matching pins are added to the device
as required and the connector is plugged in. If you place a plug connector so it attaches
to a device, any conductors previously attached to that device covered by the plug
connector are broken and reconnected to the plug connector if they can be attached to
parallel pins on the plug connector.
4. If you are creating an inline connector, drag the mouse again to place the final corner of
the second inline half.
Note
If you place an inline connector across the path of a straight conductor, pins are
automatically created where the conductor enters and exits the inline pair. The
conductor is broken and a new conductor with the same properties is created on one side
of the inline pair. The two conductors are attached to the pins. If you hold CTRL during
the third click, the inline pair is fully populated with pins.
This also applies to multicores and overbraids. They are split and retain their structure
on both sides of the new inline. If there are shields and daisy chains attached, they
remain connected to the same pins but may belong to the newly created multicore or
overbraid. If the existing multicore or overbraid belongs to an assembly, the newly
created multicore or overbraid also belongs to that assembly.
If you place an inline connector such that it lies across a shared/ported conductor,
multicore or overbraid, one half of the split becomes a completely new shared/ported
conductor, multicore or overbraid.
Functionality has been introduced to enable the mating of more than one plug to any
given receptacle connector, or vice versa. This allows the representation of complex
mating configurations within wiring designs and can also be used with modular
connectors. The can also be represented in downstream tools such as Capital Topology
and Capital HarnessXC.
Related Topics
Editing the Properties of Objects
Resizing a Device or Connector
Overview of Device Connectors and Harness Connectors in Capital Logic
Note
Stud pins are specifically excluded from the Disallow pin duplication within a design design
rule check, as they can be placed a number of times to facilitate the mating of multiple ring
terminals.
Defining pins in Capital Library allows for assistance via automated ring terminal selection,
based on library housing definition and connected wires. The stud pin is rendered differently
from a normal pin in the Design Browser and Place Pins dialog and is represented by the
icon to assist correct assignation.
When assigning a library part to a device during the design process, the Part Selection Dialog
(PSD) guides the selection of and, also automatically matches the number of stud pins and
checks ring terminal suitability, then when the Generate Harness Connectors is run the action
selects the correct ring terminal based on the connected wires. For further information see
“Generating Harness Connectors in Capital Logic” on page 217.
For further information on defining stud pins, ring terminals and managing associated Ring
Terminal Groups in Capital Library see Stud Pins Ring Terminals and Ring Terminal Groups in
the Capital Library User Guide.
When a device with a stud pin is placed in a slot in Capital Integrator, you can see it in the signal
map. For information on mating multiple ring terminals to the same stud pin using Signal
Mapping see Stud Pins and Ring Terminals in the Capital Integrator User Guide.
Video
A short example detailing how to convert pins to studs is contained within the video link in
“Generating Harness Connectors on a Device” on page 218.
Procedure
1. With a single pin connector selected on the design, right click and select Convert To
Stud Pin from the context menu.
2. The process:
• Converts a single device pin to stud pin. This allows the mating of multiple ring
terminals to a single stud pin. The stud pin is rendered differently from a normal pin
in the Design Browser and Place Pins dialog and is represented by the icon.
Additionally, on the design diagram, the pin style changes from a diamond ( )to a
circle ( ) to indicate the type of pin connected.
Note
For shared stud pins, the Convert To Stud Pin action remains disabled if there
are other designs with these pins and:
- they are opened elsewhere
- they are released
- if the shared device is frozen.
Note
The Convert To Normal Pin action is disabled if there is more than one ring
terminal still connected to the selected stud pin. A tooltip provides information
on the number of ring terminals still connected. You must remove all these before
proceeding with the conversion.
The Convert To Normal Pin action is also disabled if the project preference
Disallow duplicate pins on diagram is ON and the selected stud pin has multiple
representations in the design as this can result in multiple normal pin instances
violating the preference.
For shared stud pins, the Convert To Normal Pin action remains disabled if there
are other designs with these pins and:
Procedure
1. Press Space Bar and enter Plug or Receptacle.
2. Position the mouse cursor over a grid point where you want to place one corner of the
device.
3. Drag the mouse away to place the opposite corner of the device. A gray rectangle is
displayed, along with the dimensions of the device and the number of pins that can fit on
the device. Drag the mouse until the rectangle is the size that you want the device to be
and click the grid point where you want to place the opposite corner.
Note
If you hold CTRL during the second click, pins are automatically added to the
connector. If the connector touches a device, matching pins are added to the device
as required and the connector is plugged in. If you place a plug connector so it attaches
to a device, any conductors previously attached to that device covered by the plug
connector are broken and reconnected to the plug connector if they can be attached to
parallel pins on the plug connector.
2. Either:
• Press Space Bar and enter Delete
• Right-click on the selected entity and select Delete
• Press the Delete key
3. The connector is removed from the design and from the Design Browser Window.
Note
If you delete a modular connector (housing) the associated sub-connectors remain in
the design browser in an Unplaced Connectors folder.
Related Topics
Adding a Modular Connector
Note
The Share Into action is not available when sharing modular connectors.
When modular connectors are shared, the modular tab becomes read-only in the Design
Browser. Modular connectors are displayed as a separate node in the Shared Objects Browser
window. The modular tab can still be accessed for editing purposes by right-clicking on a
modular connector and selecting Edit Shared Plug. See “Assigning Connector Positions Using
the Modular Tab” on page 443 and “Editing Shared Devices and Shared Connectors” on
page 191.
2. Expand the modular connector with which the selected sub-connector is to be associated
by clicking the plus (+) symbol to the left.
3. Click to select the position into which the sub-connector should be inserted.
4. Click OK. A message is displayed asking you to confirm that the sub-connector should
be moved to a new position on the bundle configuration.
5. Click Yes to confirm. The sub-connector is repositioned according to the settings
configured for the currently applied style set (see the Diagram Styling User Guide for
more information).
Related Topics
Adding a Modular Connector
Disassociating a Modular Insert
Related Topics
Adding a Modular Connector
Associating a Modular Insert
Overview of Backshells
You can add one backshell to a connector in Capital Logic. You can specify terminations on the
backshell to which wires or shield conductors can connect.
When you share the connector, you also automatically share the backshell. However, the
backshell is only shared across instances of that connector. You cannot share a backshell across
connectors. There is no specific functionality for adding a shared instance of a backshell
termination because you can add multiple instances of a termination and this implies that the
termination is shared.
Procedure
1. A typical workflow for using a backshell is as follows:
2. Create a backshell symbol in Capital Symbol.
When you add a backshell termination with the name BS1 to a conductor and use that
The symbol relates to one backshell termination so you can add only one pin to it. If you
add a library part to an instance of a backshell, the library part can have an infinite
number of backshell termination connections.
If you add a pin, the pin is used as the insertion point marker when the symbol is added
to a Capital Logic diagram. If you do not add a pin to the symbol, the normal insertion
point marker is used.
See Creating a New Symbol in the Capital Symbol User Guide for more information
about how to create a symbol.
3. Add a backshell to a connector in Capital Logic and define backshell terminations on the
connector. See “Adding a Backshell to a Connector” on page 228 for more information.
4. Associate a library part description with the backshell in the diagram. See “Editing an
Object's General Properties” on page 406 for more information about this. The library
part description must have been defined in Capital Library first. See the Capital Library
help system for more information about defining library parts.
Procedure
1. Right-click on the connector and select the Add Backshell menu option. Alternatively,
click on the connector, press Space Bar and enter Add Backshell.
2. The Backshell facility is displayed. Specify the following for the backshell:
• Name - Enter the name of the backshell in the Name field.
• Library - From the drop-down list, select the symbol library that contains the
backshell symbol that you want to use.
• Symbol - From the drop-down list, select the backshell symbol that you want to use
for the backshell terminations. The selected symbol is displayed in the window
below the Symbol field.
3. Specify the backshell terminations on the connector by typing the name of the
termination in the Name field of the Terminations section and clicking the Add button.
The termination is listed in the window below the Name field.
4. Click the OK button to add the backshell to the connector. In the Design Browser
Window, the backshell is listed below the conductor and has the backshell indicator
next to it.
If you have defined terminations, a broken line indicates where you can add the
termination to the connector in the diagram window. Click on the point on the broken
line where you want to add a termination. The line extends beyond the connector
drawing. If you add the termination at a point outside of the connector, the connector
drawing extends accordingly. If you have defined multiple terminations, you must place
each termination. The backshell symbol is displayed at each termination and the
terminations are listed under the backshell in the Design Browser Window.
If you have not defined any terminations, the backshell is not visible in the diagram
window.
Note
A backshell termination can appear at multiple locations on the connector. This is
because the backshell symbol represents an available termination location but does
not define the physical location of that termination. Therefore, if a termination name is
displayed multiple times, it represents the same physical termination.
To add a termination symbol for a termination multiple times, right-click on the
connector and select the Edit Backshell menu option. In the Backshell facility, click on
the termination and click the OK button. You can then add the termination as described
above. To delete a backshell termination, right-click on it in the diagram window or in
the Design Browser Window and select Delete from the pop-up menu.
Capital Library
A direct to device connection must be modeled as part of a device footprint.
Procedure
1. Create a connector for which the Include on BOM option on the Base tab of the
Component Maintenance Dialog is unselected.
2. Add the connector to a device connector footprint for the device for which you want to
create the direct to device connection. See Update/Edit Device Footprint in the
Capital Library User Guide.
Note
If a footprint connector is defined as included on BOM, it is ignored during the
synchronization and all of the connected wiring is ignored too. If a footprint
connector is defined as not included on BOM, it is included in the synchronization and
so is any connected wiring.
Capital Harness XC
When you synchronize a logical design with a harness design, Capital HarnessXC detects the
device connector that is set as not included on BOM, selects the relevant part from the library
and places it on the harness diagram.
When you synchronize a topological design with a harness design, Capital HarnessXC detects
where a hole has been used for a device connector that is set as not included on BOM, selects
the relevant part from the library and places it on the harness diagram.
In this case, you can set attributes directly on device pins in Capital Logic to define a footprint.
When you synchronize the logical design with a Capital Integrator design in the generative
flow, this footprint data is passed on to the Capital Integrator design (just like library footprint
data).
Note
The system treats footprints created using attributes as harness connector footprints. When
you define a harness connector footprint in Capital Library, you can assign part numbers to
the footprint connectors. When you define a harness connector footprint directly on a device in
Capital Logic, you cannot assign part numbers to the footprint connectors. In the latter case, you
should assign part numbers to the slot connectors in Capital Integrator.
Procedure
1. Create the device and add the required pins to it. See “Creating a Device in a Diagram”
on page 181 and “Adding Pins to an Object Instance” on page 145.
2. Edit the attributes of each pin as follows:
a. Right-click on the pin in the diagram window and select Properties; the Edit
Properties dialog for the pin is displayed.
b. On the General tab, specify the following attributes for the pin:
o Connector Group
Specify a footprint connector to which the pin should map. You can use
placeholder names for connectors, such as C1 and C2. Capital Integrator gives
you the option of renaming them later.
o Connector Cavity
Specify a footprint connector cavity (such as 1, 2 and so on) to which the pin
maps.
Note
Mapping the Pin to a Hole rather than a ConnectorIf you want the pin to
map to a hole in Capital Integrator, do not use the Connector Group and
Connector Cavity attributes. Instead, use the Pin Group attribute for the pin to
specify a placeholder hole name, such as H1. You can specify different holes for
different pins on the device, but typically you have only one.
Design hierarchy can be represented using blocks that provide an instant portrayal of objects
and devices that eventually will comprise multiple inter-related systems. It is possible to use
these blocks to create hierarchical documentation of how system designs within a platform
(such as a complete vehicle or aircraft) are interconnected. This is achieved by associating
designs to blocks which are connected together using highways. Navigation allows you to go
from a block to a design and back again. Reporting on highways lists all the shared connectivity
between the connected designs.
Design Hierarchy Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Adding a Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Associating a Block with a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Removing an Association Between a Block and a Design . . . . . . . . . . . . . . . . . . . . . . . . . 248
Creating New Instances of a Block. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Viewing Items Related to the Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Adding Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Viewing the Connectivity that Terminates at Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Merging Block Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Adding Pins to a Block Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Edit Properties: Blocks Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Block Conductors Usages Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Place Pins Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Design rule checks identify any connections between blocks that do not have a valid highway.
Additional checks identify where a block is not associated with a design or the design is not part
of an active build list. The integrity of the connectivity is also automatically subject to design
rule checks, see “Design Rule Check Descriptions” on page 67.
It is possible to navigate from a block to its associated design, and back again. While reporting
on the highway lists all the shared connectivity between the connected blocks and designs, See
“Viewing Another Instance of an Object” on page 203.
Figure 6-1 shows a design comprising three blocks, connected via two highways, referencing
three designs. You can use the View Related Items functionality to view the design that the
block is associated with (see “Viewing Another Instance of an Object” on page 203).
A block appears both graphically in a diagram and also under a Blocks node in the Design
Browser Window. Any highways that connect with the block are also listed under the same
node.
Blocks on diagrams can be sliced, simplifying diagram modifications and making diagrams
easier to understand. See “Slice Objects” on page 128.
Copy and pasting a block creates a new block. Using the key combination CTRL + SHIFT + V
creates a new instance of the block. This method results in the copies of the block retaining the
same name as the original block. See “Copying Objects” on page 129.
Reporting on highways lists all the shared connectivity between the connected blocks and
designs. For further information see “Reports” on page 349.
The appearance of blocks can be styled. See the Diagram Styling User Guide for more
information about style sets and how to edit them. There are two default attributes for block
styling:
• Name
The name of the block.
• Associated Design
The design which the block has been associated with.
Note
From 2013.1 the defaultStyle.xml includes new shape parameters to support
hierarchical blocks in Capital Logic. If you copy your pre-v2013.1 defaultStyle.xml
file to the new installation, you must manually add the sections needed to represent
blocks in your designs to ensure that blocks are styled correctly.
Adding a Block
This topic details how to add (create) a new block in a diagram.
Video
Adding a Block — This video illustrates how to perform this task. Click to view it.
Procedure
1. Press Space Bar and enter Block.
2. Position the mouse cursor over a grid point where you want to place one corner of
the block.
3. Drag the mouse away to place the opposite corner of the block. A gray rectangle is
displayed. Drag the mouse until the rectangle is the size that you want the block to be
and click the grid point where you want to place the opposite corner.
Results
• A new block is added to the Design Browser Window.
Related Topics
Design Hierarchy
Associating a Block with a Design
Creating New Instances of a Block
Viewing Items Related to the Block
Edit Properties: Blocks Dialog Box
Video
Associating a Block — This video illustrates how to perform this task. Click to view it.
Prerequisites
• A build list must be active in order to view a list of available designs (see “Setting an
Active Build List” on page 57). Only designs in the active build list can be selected.
Procedure
1. Do one of the following:
• Select the block, press Space Bar and enter Properties
• Right-click on the selected block and select Properties
• Double click on the selected block
• Select the block and press ALT + Enter
The Edit Properties: Blocks Dialog Box is displayed.
2. Specify a name for the block, or accept the default.
3. Click the ellipsis (...) button in the Associated Design field to select from a list of
available target designs to which you wish to associate the block. You can also type in
the first few characters of the required design and the system will auto-complete the rest.
Alternatively you can use wildcards, for example .* lists all available target designs. For
further information see “Design Revision/Build List Selection Help” on page 108.
Note
The Select Design dialog box only displays designs available within the active build
list.
4. Make any other changes required to the block attributes and/or properties.
5. Click OK.
Results
• Once a block is associated to a target child design its icon changes to show the block/
design association ( ). The difference between associated and unassociated block icons
is shown in Figure 6-2. Additionally positioning the mouse cursor over the block in the
Design Browser Window displays a tool tip with details of the design to which it is
associated.
Figure 6-2. Block and Design Associations
Related Topics
Design Hierarchy
Design Rules Help
Removing an Association Between a Block and a Design
Creating New Instances of a Block
Viewing Items Related to the Block
3. Click OK.
Results
• The block and design association is removed and the Block icon reverts to ( ) in the
Design Browser Window.
Related Topics
Design Hierarchy
Associating a Block with a Design
Creating New Instances of a Block
Viewing Items Related to the Block
Edit Properties: Blocks Dialog Box
Procedure
Do one of the following:
• Associate the new instance of the block to a design that is already associated to
another block, within the current design.
• Double click on a block in the Design Browser and specify a target design that is
already associated to another block within the current design.
• Copy the block and press CTRL + SHIFT + V to create a new instance of the block.
If you do this, the copies of the block retain the same name as the original block.
Note
If you copy and paste a block on its own, you will create a new block, not
another instance of the same block. See “Copying Objects” on page 129.
Results
• A new instance of the selected block is displayed on the design. It has a broken glyph
graphic to indicate that more than one instance of this block exists, as shown in
Figure 6-3.
Figure 6-3. Multiple Instances of Block Indicator
Related Topics
Design Hierarchy
Associating a Block with a Design
Viewing Items Related to the Block
Edit Properties: Blocks Dialog Box
2. If there is only one cross-reference listed for the block that you have been viewing, the
diagram in the cross-reference opens automatically.
If there is more than one cross-reference listed for the instance, the Related Items
dialog box is displayed. Click on the cross-reference for the design that you want to
view and click the OK button.
Results
• The diagram for the design that you have selected opens in the diagram window. If the
design is locked, a read-only version is displayed.
Related Topics
Design Hierarchy
Associating a Block with a Design
Creating New Instances of a Block
Edit Properties: Blocks Dialog Box
Adding Connectivity
This topic details how to add (create) connectivity between blocks in a diagram by using
highways.
For full information on creating and using Highways, see “Highways” on page 316.
Note
When a highway is connected to a block it is added as an “empty stack” of pins in order to
provide a representation of the connectivity of the block. If you connect a highway to an
empty stack and subsequently delete the highway, the stack is also deleted. It is possible to hide
the Stacked Pins decoration through styling if required. For further information see “Stacked
Pins” on page 158.
Procedure
1. Press Space Bar and enter Highway.
2. Position the mouse cursor over the point on the block where you want to place the first
end of the new highway.
3. Click and drag the mouse cursor to define highway segments.
4. Double click on the destination block or highway to complete the connection.
Results
• If the highway is not attached to an existing highway, a new highway is added to the
Design Browser Window.
• If the new highways segments are attached to an existing highway, they become part of
the existing highway. No new highway is created.
Note
To view the conductors in the highway: either right-click on the highway and select
View Usage, or press Space Bar and enter View Usage. See “Viewing the
Connectivity that Terminates at Blocks” on page 251.
Tip
For further information on adding connectivity between block see “Wires,
Conductors and Nets” on page 261.
Related Topics
Design Hierarchy
Associating a Block with a Design
Adding a Highway
Deleting an Entire Highway
Stacked Pins
Creating New Instances of a Block
Viewing Items Related to the Block
Viewing the Connectivity that Terminates at Blocks
Edit Properties: Blocks Dialog Box
Procedure
1. Select the highway in the diagram window and either:
• Right-click on it and select View Usage.
• Press Space Bar and enter View Usage.
2. The Block Conductors Usages Dialog Box is displayed; the dialog lists the conductors
and any connected blocks.
Design rule checks identify unassociated pins and invalid associations on the block, navigation
to which is then provided in order to correct any issues. See “Design Rule Check Descriptions”
on page 67.
Prerequisites
• Child designs have been created and associated with the top-level design.
• Unmated receptacle pins or unconnected device pins must have been created on the
associated child design.
Procedure
1. Select the block in the Diagram Window or in the Design Browser Window and either:
• right-click on it and select Add Pin
• press Space Bar and enter Add External
• press P
In all cases, the Place Pins Dialog Box is displayed.
2. In the Diagram Window, click on the points of the block where you want to add pins.
As you move the cursor over the block, it changes appearance. Where a pin can be
added, it looks like this: .
3. You can add multiple pins from the Place Pins dialog box by pressing SHIFT and
selecting the required pins.
4. Click OK.
Results
• The requisite pins are added to the selected hierarchical block.
Related Topics
Place Pins Dialog Box
Related Topics
Design Hierarchy
Adding a Block
Associating a Block with a Design
Creating New Instances of a Block
Viewing Items Related to the Block
Design Rule Check Descriptions
Slice Objects
Copying Objects
Editing Objects Parameters
Related Topics
Viewing the Connectivity that Terminates at Blocks
Related Topics
Adding Pins to a Block Instance
The following sections describe how to add, edit and manage wires, conductors and nets in
designs.
Creating a Conductor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Creating/Moving/Deleting a Wire Conductor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Creating a Wire Conductor in a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Moving a Wire Conductor in a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Merging Wire Conductors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Deleting a Wire Conductor from a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Creating/Moving/Deleting a Net Conductor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Creating a Net Conductor in a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Modifying a Net Conductor in a Design. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Merging Net Conductors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Adding Multiple Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Deleting a Net Conductor from a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Creating a Notch to Move a Subsegment of a Conductor . . . . . . . . . . . . . . . . . . . . . . . . 270
Disconnecting and Moving a Conductor End from a Pin . . . . . . . . . . . . . . . . . . . . . . . . 270
Poke Home Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Specifying a Poke Home Wire in Capital Logic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Routing Conductors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Using Orthogonal Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Auto-routing of Nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Auto-routing of Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Promoting a Conductor to a Shared Conductor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Creating a Splice in Capital Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Creating a Single Pin Splice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Adding a Splice with a Library Part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Converting a Butt Splice to a Center Strip Splice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Converting a Center Strip Splice to a Butt Splice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Automatic Splice Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Overview of Multicores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Overview of Overbraids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Creating a Multicore or Overbraid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Creating a Multicore or Overbraid Without a Library Part in a Diagram . . . . . . . . . . . . . 282
Creating a Multicore with a Library Part in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Creating a Conductor
You can add the following types of conductors to a design:
• Net Conductors
This is a logical object that you use to represent a connection between objects. A net
conductor can be a shared object.
See “Creating/Moving/Deleting a Net Conductor” on page 267.
• Wire Conductors
This is a physical object that is a wire creating connectivity between objects. A wire can
be a shared object.
See “Creating/Moving/Deleting a Wire Conductor” on page 264.
• Shield Termination Conductors
This is a logical object that you use to represent a connection between a shield and other
objects.
See “Creating a Shield Terminator” on page 296.
Note
By default, Auto Routing is enabled in the application. Auto Routing means that the
Route Selected action is performed automatically on a conductor when it is created
between two points (pins or empty space) without clicking to create segments between
those two points. See “Routing Conductors” on page 274.
3. To place the end-point of the conductor, double-click on the location where you want
the conductor to end. Alternatively, left-click once with the mouse on the location and
then right-click to display a pop-up menu and select Commit. The line changes to
purple and the conductor is added to the list in the Design Browser Window.
You can create connectivity between a wire conductor and the following objects:
• Device
• Splice
• Connector
A circle is displayed around a pin when you drag the end-point of a wire conductor over
it. This indicates that placing the wire conductor there creates connectivity. After you
place the end-point, the diamond around the pin disappears. This indicates that the wire
conductor is connected.
Note
You can indicate a wire is a poke home using an attribute in the Properties dialog
box.
Related Topics
Automatic Splice Creation
Note
If you move or stretch a conductor end to a pin, it will connect to it. If you move or
stretch it to a point on a pinlist where there is no pin, a pin is created.
Note
You cannot merge a wire conductor with another wire conductor by placing the end-point of
one on a mid-point of another.
Note
By default, Auto Routing is enabled in the application. Auto Routing means that the
Route Selected action is performed automatically on a conductor when it is created
between two points (pins or empty space) without clicking to create segments between
those two points. See “Routing Conductors” on page 274.
A net junction is at the end of a segment that is connected to another segment. Any net
junction where three or more net sections meet is displayed as a solid square.
3. To place the end-point of the conductor, double-click on the location where you want
the conductor to end. Alternatively, left-click once with the mouse on the location and
then right-click to display a pop-up menu and select Commit. The line changes to teal
and the conductor is added to the list in the Design Browser Window.
You can create connectivity between a net conductor and the following objects:
• Device
• Connector
• Another net conductor
In the case of devices and connectors, a circle is displayed around a pin when you drag
the end-point of a net conductor over it. This indicates that placing the net conductor
there creates connectivity. After you place the end-point, the diamond around the pin
disappears. This indicates that the net conductor is connected.
You can connect more than one net conductor to a pin. The net conductors are treated as
different design objects.
In the case of shield conductors and other net conductors, a larger square is displayed
around the square of the end-point when you drag it over a point on the other conductor.
This indicates that placing the end-point there creates connectivity.
A net junction is created whenever you end a net conductor at a segment of another net
conductor. The net junction is displayed as a solid square placed at the junction point.
You cannot create connectivity between a net conductor and a wire conductor.
Note
If you move or stretch a conductor end to a pin, it will connect to it. If you move or
stretch it to a point on a pinlist where there is no pin, a pin is created.
Procedure
1. Press either CTRL + SHIFT + W to add multiple wires or CTRL + SHIFT + N to add
multiple nets.
2. Select the pins for which you wish to create multiple connections. Colored (red and
green) numbers are displayed against pins in the sequence they are selected so it is
possible to quickly match the source and target pins. Additionally shadow connections
are depicted by dashed lines indicating the proposed connectivity.
3. Double click on the target pins, or press the Enter key to commit the action
Incorrect selections on source pins can be amended if the CTRL key remains pressed
and you reselect previously selected pins. Incorrect selections of target pins can be
amended by either pressing Backspace or right-clicking and selecting Backspace from
the context menu. Pressing the Esc key cancels the operation.
Results
Once connections have been committed, the dashed lines change to solid. The adding of
multiple wires onto a stacked pin is supported as is multi-pin terminations. If there is not a target
pin on your selected object, the system adds a pin as required. Selecting on free space adds
dangling connections which can be joined to pins in future operations.
2. Click on the pin or free space where you want to place the conductor end.
Results
• The conductor end is disconnected from the original pin.
• If you place the conductor end on a new pin, it is connected.
• If you use the Auto Routing action, the conductor is re-routed.
This means that wires 001 and 002 are poke homes where they terminate at connector P02.
When this design is synchronized with Capital HarnessXC designs for a harness H1 and harness
H2:
• Only H1 objects are synchronized with the H1 design, although the connector P02 also
appears in it but is treated as “not on BOM”.
• Only H2 objects are synchronized with the H2 design.
• The system recognizes the wires 001 and 002 in the H1 design as poke home wires.
Caution
The Treat Wires Terminating On A Different Harness As Poke Home project
preference for Capital Logic must be selected for this to work. See “Project
Preferences” on page 68.
Caution
Although it is possible to enter multiple harnesses as a comma-separated list, you
should not do so when working with poke homes. This is because a poke home wire
only ever belongs to one harness.
2. Right-click on objects in the diagram window or Design Browser Window and select
Edit Harness Attribute; the Edit Harness Attribute dialog is displayed.
Note
If you use Capital Topology, you can specify a bundle as a poke home in that. See
“Specifying a Bundle (Harness) as a Poke Home” on page 598 of the Capital
Topology chapter.
3. Enter the name of the harness or the harness group that the object is to be synchronized
to. If harness names or harness groups have been created in Capital Project, you can
select one from the drop-down list in the Harness field.
Results
When the design is synchronized with Capital HarnessXC designs:
• The Capital Logic objects are synchronized with the appropriate harness designs in
Capital HarnessXC.
• The system recognizes wires that are poke homes (that is, they terminate on a different
harness design). When you generate reports for the Capital HarnessXC designs, the
specified Poke Home Prefix is added to those wire names.
Note
The wires in Capital HarnessXC all need to terminate, so connectors not belonging
to that harness still get created with “Poke Home” set against the connector. It is also
set as “not on BOM”.
Related Topics
Poke Home Wire
Routing Conductors
If conductors are following complicated paths in the Diagram Window, you can re-route the
conductors to more direct paths.
Procedure
Select one or more conductors to be routed and either:
Auto-routing of Nets
Auto-routing means that the Route Selected action is performed automatically on connected
conductors when:
• devices / symbols / connectors are moved
• pins are repositioned on devices / connectors
• devices / symbols / connectors are rotated
• devices / symbols / connectors are flipped
• a symbol is selected for a parameterized device
• a symbol is reselected for a device
• a symbol is updated for a device
• a wire / net / shield is created between two points (pins or empty space) without clicking
to create segments between those two points
Auto-routing can be enabled or disabled by pressing Space Bar and entering Auto-route Net, or
by pressing Ctrl+Shift+R on your keyboard. The Auto-route: ON/OFF Indicator on the
Status Bar indicates whether it is enabled or disabled, and which mode is currently active.
Auto-routing of Signals
When the Auto-route Signal mode is enabled, conductors and in-line connectors placed along
the signal path are re-routed and relocated in the case of the in-lines. The in-lines are placed in
an optimal position for their connections and may rotate through 90 degrees to provide an
optimized diagram.
Note
The Auto-route Signal functionality routes from end to end, including in-line connectors
and splices. In-line connectors must have one pin pair, and each pin must be connected to a
single wire. Splices must also have at least two wires connected.
Auto-route Signal can be enabled or disabled either by pressing Space Bar and entering Auto-
route Signal, or by clicking the Auto Route icon on the Status Bar. The icon changes to
indicate whether it is enabled or disabled, and which Auto Route mode is active:
• - Auto-routing is off.
There are a number of ways in which you can create a multiple pin splice but it must use a splice
symbol created in Capital Symbol. See the Capital Symbol help system for more information
about creating a splice symbol.
If splice symbols have been created, you can either add a shared splice with a plug map (see
“Adding a Splice with a Library Part” on page 278), add a symbol (see “Adding a Symbol to a
Diagram” on page 335), or add a splice with a library part that has an associated symbol (see
“Adding a Splice with a Library Part” on page 278).
You can add a splice from the component library even if it does not have an associated symbol
(see “Adding a Splice with a Library Part” on page 278).
On a normal conductor, the splice style is a butt splice by default. On a conductor that has been
converted to a port, the splice style is a center strip splice (the wire's insulation is stripped at a
midpoint and passed through a splice) by default.
If a butt splice does not use a symbol, it can be converted to a center strip splice (see
“Converting a Butt Splice to a Center Strip Splice” on page 278). A center strip splice can be
converted to a butt splice (see “Converting a Center Strip Splice to a Butt Splice” on page 278).
Stretching a wire so that its end touches a midpoint of a shared wire results in a center strip
splice on the shared wire, and a butt splice on the stretched wire.
Note
Splices are automatically created if you insert a wire that attaches its terminating end to the
middle of another wire.
If you connect a conductor to a conductor that has been converted to a port, a center strip splice
is created automatically.
Procedure
1. Press Space Bar and enter Splice, and click on the conductor at the point that you wish to
insert the splice.
2. The splice appears in the browser tree as a child of the conductor in addition to being
listed in the Devices list.
Splices are represented in the diagram by a filled circle. There are two splice styles:
• Butt Splices - The default splice style is a butt splice (one end of the wire connected to
the splice pin). Butt splices appear in the browser tree as a child of the conductor in
addition to being listed in the Devices list.
• Center Strip Splices - A butt splice can be converted to a center strip splice (the wire's
insulation is stripped at a midpoint and passed through a splice). Wires attached to
center stripped splices appear in the browser tree as a child of the splice in addition to
being listed in the Devices list.
Related Topics
Creating a Splice in Capital Logic
Creating/Moving/Deleting a Wire Conductor
Overview of Multicores
A multicore cable is a single cable comprised of multiple wires. If it is a coax or oval multicore
it has a shield that can be grounded with a shield terminator.
On a Capital Logic diagram, the graphical representation is similar to an overbraid but an
overbraid is not the same as a multicore.
An overbraid can contain other overbraids and multicores but a multicore cannot contain an
overbraid.
There are the following ways of adding a multicore to a design in Capital Logic:
• Create a multicore in Capital Logic (this can be promoted to a shared multicore later).
See “Creating a Multicore or Overbraid” on page 282.
• Create a shared multicore in Capital Logic. See “Creating a Shared Multicore or
Overbraid in Capital Logic” on page 293.
• Add a shared multicore that has been created in Capital Project. “Adding a Shared
Multicore to a Design” on page 295.
• Add a multicore that has been created with a part number in Capital Library. See
“Adding a Multicore from Capital Library” on page 301.
Shared multicores can be added to multiple diagrams across a project.
If you want to display the name of a multicore on the diagram. You can either:
• Select to make the name visible when creating a multicore or shared multicore in Capital
Logic. This displays the name next to every indicator on the multicore.
• Edit the general properties for an indicator on an existing multicore and make the name
visible. See “Editing an Object's General Properties” on page 406 for more information.
This displays the multicore name next to that indicator only.
Note
If a multicore or a conductor has a Capital Library part number assigned to it, a tick
is displayed next to its symbol in the Browser Windows.
Note
If the conductors in a multicore connect to different pin lists you can specify whether the
individual indicators on the multicore stretch across all of the conductors or whether they
are split so that there is part of the indicator on each of the conductors. See “Splitting Multicore
Indicators and Overbraid Indicators” on page 285 for more information.
Overview of Overbraids
An overbraid is a sheath that is applied to the outside of a harness primarily to address electrical
noise concerns. On a Capital Logic diagram, the graphical representation is similar to a
multicore but an overbraid is not the same as a multicore.
An overbraid can be applied over another overbraid but a multicore cannot contain an
overbraid.
There are the following ways of adding an overbraid to a design in Capital Logic:
• Create an overbraid in Capital Logic (this can be promoted to a shared overbraid later).
See “Creating a Multicore or Overbraid” on page 282.
• Create a shared overbraid in Capital Logic (you cannot create a shared overbraid in
Capital Project). See “Creating a Shared Multicore or Overbraid in Capital Logic” on
page 293.
Shared overbraids can be added to multiple designs across a project.
You can add a library part to an overbraid. When you do this, the color, material and wire spec
attributes are applied to the overbraid.
If you want to display the name of an overbraid on the diagram. You can either:
• Select to make the name visible when creating an overbraid or shared overbraid in
Capital Logic. This displays the name next to every indicator on the overbraid.
• Edit the general properties for an indicator on an existing overbraid and make the name
visible. See “Editing an Object's General Properties” on page 406 for more information.
This displays the name next to that indicator only.
Note
If an overbraid has a Capital Library part number assigned to it, a tick is displayed
next to its symbol in the Browser Windows.
If the conductors in an overbraid connect to different pin lists you can specify whether
the individual indicators on the overbraid stretch across all of the conductors or whether
they are split so that there is part of the indicator on each of the conductors. See
“Splitting Multicore Indicators and Overbraid Indicators” on page 285 for more
information.
Note
You cannot add shared conductors to a multicore or overbraid that has been created in
Capital Logic but has not been promoted to a shared multicore and placed in the diagram.
The Generic Multicore dialog allows you to create a multicore either with or without a library
part:
Note
A multicore or overbraid that has been created in Capital Logic and has not been
shared cannot contain a shared conductor or overbraid.
5. Click OK to accept your changes. An indicator symbol of the type you have selected
appears near each end of the multicore or overbraid. If a multicore or overbraid is
between more than two connectors and/or devices, one indicator appears near each
connected end. Each indicator can be moved independently of the others, but changes to
one affect the whole set.
The multicore or overbraid is also added to the Multicore folder or Overbraid folder in
the Design Browser Window.
Note
A wire, multicore or overbraid can belong to only one multicore or overbraid at a
time (it is removed from the Available Conductors column). However, any time
you create a new multicore or overbraid, that object is added to the Available
Conductors column.
If an indicator cannot be drawn across two parallel wires, the indicator will be drawn on
the single wire.
You can add a shield termination to coax and oval multicores and to overbraids. See
“Creating a Shield Terminator” on page 296 for more information.
You can also assign a part number from Capital Library to a multicore or overbraid. See
“Editing an Object's General Properties” on page 406.
If the conductors in a multicore or overbraid connect to different pin lists you can
specify whether the individual indicators on the multicore or overbraid stretch across all
of the conductors or whether they are split so that there is part of the indicator on each of
the conductors. See “Splitting Multicore Indicators and Overbraid Indicators” on
page 285 for more information.
Procedure
1. Press Space Bar and enter Multicore. The Generic Multicore facility is displayed.
2. In the Available Conductors window, select the diagram conductors to be included as
inner cores in the multicore and click the Add From Library ( ) button on the right part
of the dialog box, the Part Selection Dialog is displayed.
3. Click the Search parts using criteria specified ( ) button; multicore library parts
with an equal or greater number of inner core wires are displayed.
4. Select a multicore library part and click Insert; the library multicore structure is added
to the Multicores window in the Generic Multicore facility.
Note
You can change the name of the multicore by clicking the Edit () button.
5. Associate the diagram conductors to be included in the multicore with library inner
cores:
a. In the Available Conductors window, select a conductor to be included.
b. In the Multicores window, select the library inner core.
c. Click Assign ( ); the library inner core changes name to the diagram conductor and
an association is created.
6. Click OK; the multicore is added to the Multicore folder in the Design Browser
Window and, where appropriate, multicore indicators are added to the diagram window.
Note
You can add a shield termination to coax and oval multicores. See “Creating a
Shield Terminator” on page 296 for more information.
If the conductors in a multicore connect to different pin lists you can specify whether the
individual indicators on the multicore stretch across all of the conductors or whether
they are split so that there is part of the indicator on each of the conductors. See
“Splitting Multicore Indicators and Overbraid Indicators” on page 285 for more
information.
Related Topics
Overview of Multicores
Overview of Overbraids
Creating a Shield Terminator
Promoting a Multicore or Overbraid to a Shared Object
The two wires are put in a multicore. By default the indicator at the right end of the wires is split
as shown (Note that for overbraids, the indicator would not be split by default. These default
settings can be changed in the Project Preferences in Capital Project or Capital Logic):
You can right-click on one of the split indicators and select the Toggle Indicator option from
the pop-up menu. The indicator changes as follows:
If you want to split an indicator again, right-click on it and select the Toggle Indicator option
from the pop-up menu. The indicator reverts to its original form.
However, if the combined length of both the indicators from the left end of the segment (where
they are connected to a single pinlist) is less than the combined distance of the indicators from
the right end of segment (where they are connected to multiple pinlists), the system considers
these closer to a single pinlist and they are NOT split, as in the following example.
There may be cases where individual indicators on a multicore overlap with conductors that are
not part of the same multicore. This can happen when an additional “foreign” segment is
connected to a device, appearing to join with an existing multicore. To avoid creating confusion
the multicore indicator will not stretch across all the conductors, instead two separate indicators
are generated on the diagram.
This can be seen in the example below, where WIRE30 is marked as one group, and WIRE31
and WIRE32 as another. WIRE33 and WIRE34 are not part of the multicore and are not tagged
with an indicator.
If a group of multicore wires are split by drawing a foreign segment, removing this foreign
segment would automatically stretch the indicator back, as shown below.
If you have explicitly toggled an indicator (as shown in number 1) so it has stretched (as shown
in number 2), adding a foreign segment (as in number 3) would not split the explicitly stretched
indicator.
By default, the 'Split indicators' project preference setting is off for overbraids. Therefore if an
overbraid is created with this default option, the adding a foreign segment would not split the
overbraid indicators.
The systems stores this setting when the indicators are created and continues to honor them, as
shown below.
For further information see the Split Indicator Project Preferences setting.
Note
In addition to associating a comment symbol from a symbol library with an indicator, you
can associate graphical objects created in the diagram. You do this by clicking the indicator
before drawing a graphic. See the individual task flows under “Graphic Drawing Tools” on
page 369.
Prerequisites
• The comment symbol must exist in the symbol library.
Procedure
1. Right-click on the indicator in the diagram and select Add Comment Symbol; the
Symbol Selection Dialog is displayed.
2. Select the comment symbol and click OK; the comment symbol is displayed next to the
cursor.
3. Move the cursor to position the symbol and click to place it.
Results
The symbol is associated with the indicator. This association will be lost if the indicator is
regenerated and if you stretch, split or individualize the indicator.
Note
By default, Auto Routing is enabled in the application. Auto Routing means that the
Route Selected action is performed automatically on a conductor when it is created
between two points (pins or empty space) without clicking to create segments between
those two points. See “Routing Conductors” on page 274.
3. To place the end-point of the conductor, double-click on the multicore indicator hookup
where you want the conductor to end.
Results
• The wire is added to the diagram and the Design Browser Window.
• The system creates a splice and a zero-length shield termination at the hookup.
See “Creating a Shared Multicore or Overbraid in Capital Logic” on page 293 for more
information about creating a new shared multicore.
Note
If a Shield Termination is required on the Multicore then it should be defined before the
Multicore is shared. See “Creating a Shield Terminator” on page 296 for more information.
Procedure
1. Click on the multicore or overbraid in the Design Browser Window, press Space Bar
and enter Share.
Alternatively, right-click on the multicore or overbraid and select the Share Multicore/
Overbraid option from the pop-up menu.
2. The multicore or overbraid becomes a shared object and is added to the list of shared
multicores on the Shared Objects Browser Window.
Note
If a multicore has a daisy chain attached, the shared object replicates the local
connectivity. For example, if the multicore has a daisy chain attached but this does
not result in a shield (because the attached multicore does not have a shield, or the shield
does not end at a pin), then the shared object will not have a shield. In addition, the
redundant daisy chain is removed.
Related Topics
Overview of Multicores
Overview of Overbraids
Creating a Shared Multicore or Overbraid in Capital Logic
Adding a Shared Multicore to a Design
Note
A shared net conductor can be part of an equivalence set. See “Overview of Shared Net
Conductor Equivalence Sets” on page 292 for information about equivalence sets.
If a shared object is frozen, a blue snowflake is displayed on the icon for the shared object .
See “Freezing and Unfreezing Shared Objects” on page 447 for more information about frozen
shared objects.
Procedure
1. Double-click on the conductor in the Shared Objects Browser Window or right-click on
it and select the Add Shared Net or Add Shared Wire option from the pop-up menu.
2. Click on the location in the design where you want the conductor to start and use the
mouse to drag the line.
You can define sections in the conductor by clicking once to place a segment end-point
and then continuing to drag the line.
3. To place the end-point of the conductor, double-click on the location where you want
the conductor to end. Alternatively, left-click once with the mouse on the location and
then right-click to display a pop-up menu and select Commit.
Note
When you create more than one instance of a shared object, cross-references are
displayed next to the instances in the diagram. See “Cross-References on Objects”
on page 199 for more information about cross-references.
Equivalence sets enable the shared net conductors present in existing (re-usable) designs, to be
included in further projects.
When creating an equivalence set in Capital Project, one of its net conductors must be selected
as the Representative net conductor for that equivalence set. Once selected, the name of the
representative net conductor is automatically used as the equivalence set's name. See the
Capital Project help system for more information about creating equivalence sets.
In Capital Logic, you can insert shared net conductor into a design diagram. See “Adding a
Shared Conductor to a Diagram” on page 291 for more information.
When a shared net conductor (that is part of an equivalence set) is place onto a design diagram
in Capital Logic, it is automatically annotated with cross-reference text that lists the design and
diagram names in which any of the other net conductors in the same equivalence set have been
placed. If a net conductor is part of the same equivalence set, but has not been placed on a
design, it will not appear listed in the cross-reference text. See “Cross-References on Objects”
on page 199 for further information about cross-references.
Note
Equivalence sets can only contain shared net conductors, they cannot contain shared wire
conductors.
A shared net conductor can only be included in one equivalence set, once a net conductor has
been included in one equivalence set, it is not available for inclusion in further equivalence sets.
A shared net conductor must first be removed from one equivalence set before it can be
included in another equivalence set.
A Capital Logic design containing shared net conductors (that are part of an equivalence set)
can still be associated with a Capital Integrator design in order to synthesize wiring. Signal
names in Capital Integrator will use the name of the representative shared conductor whenever a
shared conductor that is in an equivalence set is used. This means that all shared net conductors
in the same equivalence set are shorted together in Capital Integrator.
If you have already created a multicore or overbraid that is not shared, you can promote it to a
shared object. See “Promoting a Multicore or Overbraid to a Shared Object” on page 290 for
more information about promoting an existing multicore or overbraid.
Note
You can add both shared conductors and other conductors to a shared multicore or overbraid
that you are creating in Capital Logic. Any conductors that are not already shared are
converted to shared conductors when the shared object is created.
Procedure
1. Press Space Bar and enter Shared Multicore or Shared Overbraid.
2. In the Create Shared Multicore or Create Shared Overbraid dialog box, click the
New button on the right part of the dialog box.
3. In the Edit Shared Multicore or Edit Shared Overbraid dialog box, name the new
multicore or overbraid and click the indicator type that applies to the object. Twist-
commercial, twist-military and twist-z are not shielded. Coax and oval multicores can be
shielded. An overbraid can have only a dashed-oval indicator type.
Note
When you are editing shared multicores or shared overbraids, only shared
multicores/overbraids that are used in the current design are displayed. If you want
to view shared multicores/overbraids that are used in other designs, then you must open
diagrams from those other designs.
If you do not want to use the name that the system uses by default, uncheck the Default
Name box and enter a new name in the Name box. If you want to display the name next
to each indicator for that object on the Capital Logic diagram, check the Visible box.
If you want to deselect an indicator, hold down the CTRL key on your keyboard and
click the indicator.
Click OK to close the New Multicore or New Overbraid dialog box.
4. On the Create Shared Multicore/Overbraid facility, the object is added to the
Selected box. It has the appropriate indicators listed below it. Click on the object in the
Selected column to make it active, and a wire, multicore or overbraid in the Available
column to select it. Click Add to put the wire, overbraid or multicore into the new
multicore or overbraid.
5. Click OK to accept your changes. An indicator symbol of the type you have selected
appears near each end of the object. If a multicore or overbraid is between more than
two connectors and/or devices, one indicator appears near each connected end. Each
indicator can be moved independently of the others, but changes to one affect the whole
set.
Note
A wire, overbraid or multicore can belong to only one multicore or overbraid at a
time (it is removed from the Available column). However, any time you create a
new multicore or overbraid, that object is added to the Available column.
If an indicator cannot be drawn across two parallel wires, the indicator will be drawn on
the single wire.
You can add a shield termination to coax and oval multicores and to overbraids. See
“Creating a Shield Terminator” on page 296 for more information.
You can also assign a part number from Capital Library to a multicore or overbraid. See
“Editing an Object's General Properties” on page 406.
Related Topics
Overview of Multicores
Overview of Overbraids
Creating a Shield Terminator
Promoting a Multicore or Overbraid to a Shared Object
Adding a Shared Multicore to a Design
Note
If you are adding a shared net or wire conductor to a design, see “Adding a Shared
Conductor to a Diagram” on page 291.
In Capital Logic, you can add these existing shared multicores to designs. If any shared
multicores exist for the project that is open in Capital Logic, they are displayed in the Shared
Objects Browser Window.
If a shared multicore was created in Capital Project, you cannot edit the content of it in Capital
Logic. This must be done in Capital Project. If a shared object is frozen, a blue snowflake is
displayed on the icon for the shared object . See “Freezing and Unfreezing Shared Objects” on
page 447 for more information about frozen shared objects.
Procedure
1. You must add each conductor in the shared multicore individually. Double-click on the
conductor in the Shared Objects Browser Window or right-click on it and select the Add
Shared Net or Add Shared Wire option from the pop-up menu.
2. Click on the location in the design where you want the conductor to start and use the
mouse to drag the line.
You can define sections in the conductor by clicking once to place a segment end-point
and then continuing to drag the line.
3. To place the end-point of the conductor, double-click on the location where you want
the conductor to end. Alternatively, left-click once with the mouse on the location and
then right-click to display a pop-up menu and select Commit.
4. Repeat the previous steps for each of the conductors in the multicore. When you have
added more than one conductor from the multicore to the design, an indicator is
displayed across the wires to show that they belong to a multicore.
Note
If the shared multicore is coax or oval, you must define a shield termination for it
when you create it. This shield termination is listed in the Shared Objects Browser
Window with the conductors for the multicore. See “Creating a Shield Terminator” on
page 296 for more information on how to add the shield termination to the design.
If a shared multicore does not have a library part number assigned to it already, you can
assign a part number from Capital Library. See “Editing an Object's General Properties”
on page 406.
Related Topics
Overview of Multicores
Overview of Overbraids
Creating a Shield Terminator
Promoting a Multicore or Overbraid to a Shared Object
Creating a Shared Multicore or Overbraid in Capital Logic
You can add daisy chains to connect together shield conductors so that they terminate at one
shield termination. See “Chaining Shield Conductors” on page 298 for more information.
Procedure
1. Press Space Bar and enter Shield.
2. Position the mouse cursor over the connector pin where you want to place one end of the
wire.
3. Drag the mouse to draw the circuit line, clicking to leave a right-angle turn for the circuit
line. When you have drawn the line to the cable shield, double-click to place the line.
Note
By default, Auto Routing is enabled in the application. Auto Routing means that the
Route Selected action is performed automatically on a conductor when it is created
between two points (pins or empty space) without clicking to create segments between
those two points. See “Routing Conductors” on page 274.
4. The shield termination is added to the list of conductors in the Design Browser Window.
Note
If you are adding a shield termination to a shared multicore, the shield termination
must have already been defined as part of the multicore in Capital Project.
Related Topics
Overview of Multicores
If there is no shield termination on any of the shield conductors, adding a chain does not affect
connectivity. If a shield termination is added to one of the chained indicators, connections are
added to the termination point. You must not have more than one shield termination connected
to the chain of shield indicators.
Note
Daisy chains can be added to a shared multicore only if it has a shield already. The
shield does not have to be in the current connectivity (that is, not currently
represented in the design) but it must exist on the shared object.
2. RMB and then select action “Connect indicators with Daisy Chain”
Results
• All selected multicore indicators are now connected with Daisy Chains
• The multi terminated shields have been consolidated into a single shield termination,
with the shortest shield termination being preserved.
Procedure
1. Press Space Bar and enter Add Library Multicore.
2. The Part Selection Dialog is displayed. Click the Search button to display a list of
multicores in Capital Library, click on the multicore that you want to add and click the
Insert button.
3. The multicore is added under the Multicores section of the Design Browser Window.
The conductors in the multicore are listed as grayed out under the multicore in the tree.
4. Add each conductor to the diagram by right-clicking on the conductor and selecting
either Add as Wire or Add as Net.
a. Click on the location in the design where you want the conductor to start and use the
mouse to drag the line.
b. You can define sections in the conductor by clicking once to place a segment end-
point and then continuing to drag the line.
c. To place the end-point of the conductor, double-click on the location where you
want the conductor to end. Alternatively, left-click once with the mouse on the
location and then right-click to display a pop-up menu and select Commit.
d. Multicore indicators are added to the wire in the diagram. In the Design Browser
Window, the conductor changes to the name assigned to it in the diagram and is no
longer grayed out.
e. Repeat the previous steps for each of the conductors in the multicore. When you
have added more than one conductor from the multicore to the design, the indicators
are displayed across the wires to show that they belong to the same multicore.
Note
If the multicore is coax or oval and the library part does not have a shield
termination defined, one of its conductors must be defined as a shield
termination once it is added into the design. To do this, right-click on the conductor
that you want to be the shield termination under the multicore in the Design Browser
Window and select the Designate Shield menu option.
Related Topics
Overview of Multicores
Creating a Shield Terminator
Creating a Multicore or Overbraid
Promoting a Multicore or Overbraid to a Shared Object
Creating a Shared Multicore or Overbraid in Capital Logic
Adding a Shared Multicore to a Design
In Capital Logic, it is possible that several pins with an Equipotential attribute are connected.
In Capital Integrator, all connected and equipotential nets will be combined into a single signal
that uses the name of one of the equipotential nets.
In Capital Integrator, the Design Browser Window displays the signal and lists all of the nets
below it.
In the case of shared pins, the Equipotential attribute is stored on each instance of the pin. This
provides a way of varying its value in different designs or different revisions of the same design.
It also allows separate groups of nets to be merged resulting in multiple signals on the pin.
However, this mechanism means that it is necessary to connect all the shared nets that are to be
merged onto the same instance of the device pin. In some cases, this is not desirable. For such
cases, you can use the Equipotential Global attribute on a shared pin. This results in all nets to
any instance of that pin being merged.
When a signal in Capital Integrator includes nets which have been merged using more than one
mechanism, the signal name is determined using the following precedence (that is, 1 overrides 2
and 3, and 2 overrides 3):
The Equipotential attribute is defined on an instance of a device pin. that means that it is stored
within a design and can therefore be revised with that design. In other words, you can have
multiple revisions of a system design and the definition of equipotential signals can be different
in each.
Use of the Equipotential Global attribute is very similar to the use of the Equipotential
attribute. The main difference is that Equipotential requires you to connect all the nets you
want to combine to a single instance of a device pin. However, Equipotential Global allows
you to combine all nets connected to any instance of the device pin.
Related Topics
Setting the Equipotential Attribute for a Pin
Setting the Equipotential Global Attribute for a Shared Pin
Procedure
1. Right-click on the device pin and select the Properties option from the pop-up menu.
2. The Edit Properties facility is displayed. Go to the Attributes section of the General
tab.
3. For the Equipotential attribute, click in the Value field and select a net name from the
drop-down list. The listed nets are those that connect to the pin. The name that you select
is the name that will be used for the single signal in Capital Integrator.
If you select the blank value for the Equipotential attribute, the nets will not be treated
as equipotential.
Note
If the selected net is later deleted, the attribute changes to reference another net
connected to the pin.
If the deletion leaves just one net connected to the pin, the attribute remains set so that
the equipotential behavior is preserved in case another net is later multitermed at the pin.
Note
When wiring is synthesized in Capital Integrator, the system recognizes the
equipotential attribute and creates a single signal containing the connectivity of all
the nets attached to this device pin. This signal is synthesized as a single entity.
Related Topics
Setting the Equipotential Global Attribute for a Shared Pin
Procedure
1. Right-click on an instance of the shared device pin in Capital Logic and select the
Properties option from the pop-up menu.
2. The Edit Properties facility is displayed. Go to the Attributes section of the General
tab.
3. For the Equipotential Global attribute, enter a string in the Value field; this value is
used as the name of the combined signal in Capital Integrator.
Note
When the Equipotential Global attribute is set, the Equipotential attribute is
disabled but is not cleared. The Equipotential Global value overrides the
Equipotential value when the combined signal is named in Capital Integrator.
Related Topics
Equipotential Nets at a Pin
Setting the Equipotential Attribute for a Pin
• Full-length stow - this wire runs the full length of the bundle
• Mid-bundle stow - this wire runs from a connector cavity to a splice stow point
Procedure
1. In Capital Library, create a new splice part and name it STOW. Ensure that the splice’s
Include on BOM option is not selected.
2. In Capital Logic, to create a full-length stow wire, place two splices following the
method for “Adding a Splice with a Library Part” on page 278. Give the splices a name
that identifies them as stow points, such as STOW1 and STOW2 and set the Harness
attribute for both splices (see “Specifying the Harness Attribute for an Object” on
page 438).
Note
To create a mid-bundle stow to increase the strength of a connector join, only a
single splice needs to be added. Terminate the other end of the stow wire at a
connector pin.
4. Create additional stow wires as required, but in each case, add subsequent splices at
which to terminate the wire, otherwise the stow wires will be considered electrically
connected.
Note
The stow wires can be synchronized into a harness design in Capital HarnessXC. If
the splices exist in Capital HarnessXC already, they are matched by name and the
stow wire is placed. If the splices do not exist, they are added to the bottom of the
harness diagram and you must use the Move Splice functionality to place them.
Prerequisites
• A diagram containing nets is open.
Procedure
1. Press Space Bar and enter Nets to Wires.
The Confirm Convert Nets to Wires Dialog is displayed.
2. Select whether you want to convert net conductors only in the currently open design or
in all designs in a build list. If build lists are available, select the build list from the
dropdown list. See also Abstraction Filtering below.
3. Click OK.
Results
The process:
• Converts net conductors to wire conductors.
• Converts net multicores to wire multicores, fully preserving the multicore structure and
graphical layout.
• Creates splices at wire junctions where a net or shared net has more than two ends in the
design or build list (depending on which is selected as the scope).
• Creates or modifies shared wires and multicores.
• Adds a Convert Nets to Wires tab to the Output Window summarizing the creation and
modification of objects. Where a component is listed by name, clicking on the name
highlights the component on the diagram.
Multicore Behavior
There are various considerations to take into account when running Convert Nets To Wires on
Multicores.
• Abstraction Filtering
• Shield Termination Conversion
Abstraction Filtering
To allow you to run the process against a build list, but for just one single abstraction, the
following rules apply:
• When running “Convert Nets to Wires” on a build list, convert all nets to wires on all
designs in the build list whose abstraction matches the abstraction of the currently open
design, if the currently open design has an abstraction.
• When running “Convert Nets to Wires” on a build list, if the design has no abstraction,
then all designs in the build list will be processed.
Procedure
On running Convert Nets to Wires, the result as in Figure 7-5 shows that separate shields,
SHIELD25 and SHIELD26 have been created for the newly created multicores MC214 and
MC215
Daisy Chains
On running Convert Nets to Wires, daisy chains are removed and a new shield is added in their
place, between the new indicator and original pin.
Procedure
1. In the examples below, the daisy chain from MC400 to MC399 in Figure 7-6.
Figure 7-6. Daisy Chain - Pre
3. Multiple multicore indicators can be selected and daisy chained together in one action.
See “Connect Indicators with Daisy Chain” on page 299, for full details.
Procedure
1. After running Convert Nets to Wires the indicator that SHIELD302 on DEV1599, was
connected to, MC499, now spans different multicores and no shield is placed. See
Figure 7-8below.
Figure 7-8. Shield Not Created- Pre
2. Instead, a warning is displayed in the console advising this fact. The shield has to be
placed manually.
Related Topics
Excluding Net Conductors from the Conversion to Wire Conductors
Rules and Constraints
Procedure
Caution
When running the Convert Nets to Wires action on a build list, it is strongly
recommended that all designs participating in the build list have the same constraints
applied to them. Otherwise, this could lead to unpredictable results, especially regarding
the conversion of shared objects.
1. Right-click on the design in the Project Browser Window; the Edit Design Dialog is
displayed.
2. Click Properties; the Edit Design Properties Dialog is displayed.
3. Click the Rules tab and click the Add Constraint button; the Constraint Selection
dialog is displayed.
4. Select “Exclude Nets or Multicores from the Nets to Wires conversion” and click OK;
the constraint is added to the Edit Design Properties dialog.
5. Edit the constraint as required and click OK.
Note
If you want to exclude both nets and multicores from the action, you must apply at
least two constraints.
Results
• When you run the Nets to Wires action on the design or a build list containing the
design, the nets or multicores that match any of these constraints are excluded from the
action in this design.
Note
If Net to Wires constraints apply to multicores and a matching multicore is an inner
multicore (within a nested multicore), that multicore is not excluded from the
conversion. If a root multicore matches a constraint, all of the multicores and nets nested
inside it are excluded from the conversion.
Related Topics
Converting Net Conductors to Wire Conductors
Rules and Constraints
Highways
A highway represents multiple conductors (wires and/or nets) in a single graphical
representation.
Note
Highways are also known as tramways and raceways.
A highway appears both graphically in a diagram and under a Highways node in the Design
Browser Window, under which the conductor interfaces interfacing with it are listed.
When filtering is applied to a diagram, a highway is filtered out if all conductors interfacing
with it are filtered out.
When highway functionality is described in this document, the word termination is used to
describe a conductor termination with an object other than the highway. The word interface is
used to describe the connection point between the highway and a conductor instance.
A highway can have multiple instances within a design or in another design (making the
highway a Design Wide Object). If you want to create a highway connection between designs,
then you can share a highway to achieve this. In either case, cross-references are supported as
on other diagram objects (see “Cross-References on Objects” on page 199) and you can use the
View Related Items functionality to view other instances (see “Viewing Another Instance of an
Object” on page 203).
If you copy and paste a highway on its own, you will create a new highway (not another
instance of the same highway) and no interfacing conductors are copied with it. See “Copying
Objects” on page 129. Similarly, if you move a highway on its own, no interfacing conductors
are moved with it.
Highway/Conductor Interfaces
Conductors interface (connect) with a highway.
When doing this, conductors are used as a Design Wide Object (that is, they are non-shared but
have multiple instances).
A single conductor instance can interface with one highway at one end and with another
highway at the other end and multiple instances of a conductor can interface with different
highways.
A shared conductor can interface with a non-shared highway (without the highway becoming
shared) and a non-shared conductor can interface with a shared highway.
A conductor can have also have multiple interface points with a highway. For example:
After a highway/connector interface has been created, you can drag it along the highway
segment to adjust its position.
Related Topics
Adding a Highway
Adding a New Branch to a Highway
Moving a Highway Section
Editing a Highway
Deleting a Highway Section
Deleting an Entire Highway
Interfacing a Conductor with a Highway
Routing Existing Conductors into a Highway
Removing a Conductor from a Highway
Unrouting Selected Conductors from a Highway
Unrouting all Conductors from a Highway
Sharing a Highway
Unsharing a Highway Instance
Adding a Highway
This topic details how to add (create) a new highway in a diagram.
Procedure
1. Press Space Bar and enter Highway.
2. Position the mouse cursor over the grid point where you want to place the first end of the
highway. Note that if you place it on an existing highway, a connection is made
automatically and the added segments become part of the existing highway.
3. Click and drag the mouse cursor to define highway segments.
Note
You can define segments in a highway by dragging the line, clicking once, and
dragging the line in a new direction.
4. Position the mouse cursor over the grid point where you want to place the other end of
the highway and double-click. Note again that if you place it on an existing highway, a
connection is made automatically and the added segments become part of the existing
highway.
Results
• If the highway is not attached to an existing highway, a new highway is added to the
Design Browser Window.
• If the new highways segments are attached to an existing highway, they become part of
the existing highway. No new highway is created.
Related Topics
Highways
Note
You can define segments in a highway by dragging the line, clicking once, and
dragging the line in a new direction.
4. Position the mouse cursor over the grid point where you want to place the other end of
the highway branch and double-click. Note again that if you place it on an existing
highway, a connection is made automatically and all connected segments become part of
the other highway.
Results
• If the highway is not attached to an existing highway, a new highway is added to the
Design Browser Window.
• If the new branch connects the highway to another highway, all connected segments
become part of the other highway.
Related Topics
Highways
Adding a Highway
Moving a Highway Section
Editing a Highway
Deleting a Highway Section
Deleting an Entire Highway
Interfacing a Conductor with a Highway
Routing Existing Conductors into a Highway
Removing a Conductor from a Highway
Unrouting Selected Conductors from a Highway
Unrouting all Conductors from a Highway
Sharing a Highway
Procedure
In the diagram, either:
• Click a highway section, hold down the mouse button and drag the highway section
• Click the end of a highway section, hold down the mouse button and drag the end of
the highway section
Results
• If you have dragged a whole highway section, the selected highway section moves to the
new location.
• If you have dragged the end of a highway section, the section moves or changes length
as required.
• Any other highway sections connected to the highway section move or change length as
required to maintain the connection.
• If you have dragged an end of a highway section over another highway section, a
connection is created.
• If you have dragged an end of a highway section over a highway section from a separate
highway, the highway being moved merges into the other highway. In the Design
Browser Window, the highway being moved is no longer displayed and its conductors
are displayed under the other highway.
Related Topics
Highways
Adding a Highway
Adding a New Branch to a Highway
Editing a Highway
Deleting a Highway Section
Deleting an Entire Highway
Interfacing a Conductor with a Highway
Routing Existing Conductors into a Highway
Removing a Conductor from a Highway
Unrouting Selected Conductors from a Highway
Unrouting all Conductors from a Highway
Sharing a Highway
Editing a Highway
This topic details how to edit the attributes and properties of a highway on a topology design.
Procedure
1. Select the highway to be edited.
2. Either:
• Press Space Bar and enter Properties
• Right-click on the selected entity and select Properties
• Double-click on the bundle
The Edit Properties: Highway Dialog is displayed.
3. Make any changes required to the highway attributes and/or properties.
4. Click OK.
Related Topics
Highways
Adding a Highway
Adding a New Branch to a Highway
Moving a Highway Section
Deleting a Highway Section
Deleting an Entire Highway
Interfacing a Conductor with a Highway
Routing Existing Conductors into a Highway
Removing a Conductor from a Highway
Unrouting Selected Conductors from a Highway
Unrouting all Conductors from a Highway
Sharing a Highway
Prerequisites
• The highway must exist. See “Adding a Highway” on page 318.
Procedure
1. Create the first interface (entrance/exit point) between the conductor and the highway.
To do this, use the normal functionality for adding the relevant type of conductor to
initiate the add action (for example, press Space Bar and enter Add Wire). While adding
the conductor place one end on the highway; an instance of the conductor is created in
the diagram and is listed under the highway and under Conductors in the Design
Browser Window.
2. If required, create a second interface (entrance/exit point) between the conductor and the
highway.
To do this, double-click the conductor in the Design Browser Window and add the
second instance to the diagram, placing one end at the appropriate point on the highway.
Note
You can also move or stretch the end of a conductor to a point on the highway; this
will create an interface between them.
Results
• The conductor is listed under the highway in the Design Browser Window.
Related Topics
Highways
Routing Existing Conductors into a Highway
Removing a Conductor from a Highway
Unrouting Selected Conductors from a Highway
Unrouting all Conductors from a Highway
When doing this, you create Highway/Conductor Interfaces and conductors are used as a
Design Wide Object (that is, they are non-shared but have multiple instances).
Prerequisites
• The conductors must exist.
• The highway must exist. See “Adding a Highway” on page 318.
Procedure
In the diagram window, select the conductors (or conductor segments) and the highway into
which you want to route them and either:
Related Topics
Highways
Unrouting all Conductors from a Highway
Interfacing a Conductor with a Highway
Routing Existing Conductors into a Highway
Sharing a Highway
This topic explains how to share a highway.
See “Adding a Shared Device/Connector/Splice to a Diagram” on page 186 for further
information about how shared objects are used.
Procedure
1. Either:
• Right-click on the highway in the Design Browser Window or diagram and select
Share
• Select the highway, press Space Bar and enter Share
2. If the highway has the same name as an existing shared highway, a message asks to
decide whether you want to create a new shared highway with that same name, whether
you want to use the existing shared highway or whether you want to cancel the action.
Results
• After you share an object, it is added to the Shared Objects Browser Window and can be
used elsewhere.
• Conductors interfacing with the highway are not shared automatically. You must share
them manually.
• Shared conductors that interface with the shared highway are listed below it in the
Shared Objects Browser Window. Non-shared conductors that interface with it will not
be listed in that window but will still be listed below it in the Design Browser Window.
Related Topics
Highways
Adding a Highway
Adding a New Branch to a Highway
Moving a Highway Section
Editing a Highway
Routing Existing Conductors into a Highway
Deleting a Highway Section
Deleting an Entire Highway
Unrouting Selected Conductors from a Highway
Unrouting all Conductors from a Highway
Unsharing a Highway Instance
Procedure
1. Either:
• Right-click on the highway in the Design Browser Window or diagram and select
Unshare
• Press Space Bar and enter Unshare
The Name Local Highway dialog is displayed.
2. Specify a name for the unshared highway. You can click the ellipsis (...) button to select
a pre-configured name (if any exist).
3. Click OK.
Results
• The highway is unshared.
• Any shared conductors in the highway remain shared.
Related Topics
Highways
Adding a Highway
Adding a New Branch to a Highway
Moving a Highway Section
Editing a Highway
Routing Existing Conductors into a Highway
Deleting a Highway Section
Deleting an Entire Highway
Unrouting Selected Conductors from a Highway
Unrouting all Conductors from a Highway
Sharing a Highway
Related Topics
Editing a Highway
This section details how to add, update and manage symbols that are available for use on design
diagrams.
Adding a Symbol to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Adding a Symbol to a Diagram as a Non-Intelligent Graphical Shape . . . . . . . . . . . . . 336
Updating Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Composite Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Updating a Symbol Block in a Composite Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Replacing Composite Symbols for Shared Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Replacing a Symbol with a Compatible Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Saving Diagram Objects as a Device Symbol (Bookshelf Circuit) . . . . . . . . . . . . . . . . . 341
Help Button Landing Pages for Symbols Dialog Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Update Symbol - Options Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Update Symbol - Options Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Map Pins (for Symbol) Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Map Pins Dialog (for Symbol) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Note
When placing a symbol in a diagram, you can rotate the symbol by pressing the R
key on your keyboard and you can flip it by pressing the F key on your keyboard.
3. Click the location to add the symbol graphic. If you place it directly on a pin, connector
or device, the symbol is automatically associated with that object (that means, if the
object is moved, the symbol moves with it).
Note
You can only modify the General and Graphical properties of a symbol graphic in
Capital Logic. See “Editing the Properties of Objects” on page 403. You cannot
scale a symbol from within Capital Logic. If you want to modify the symbol graphic
further, you must use Symbol Editor and then update the symbol graphics in the
diagram. See “Updating Symbols” on page 337.
Related Topics
Adding a Symbol to a Diagram as a Non-Intelligent Graphical Shape
Symbol Browser Window
Note
When placing a symbol in a diagram, you can rotate the symbol by pressing the R
key on your keyboard and you can flip it by pressing the F key on your keyboard.
Results
• The symbol is added to the diagram as grouped graphical objects.
Updating Symbols
If a symbol has been updated in a symbol library, you may want to update that symbol where it
has been used in diagrams already. This update not only updates the graphic but also the fixed
properties of the symbol.
If a symbol in a diagram is controlled by a library part, you must update the library part on that
object instance in the diagram in order to update the symbol.
Procedure
1. Right-click the symbol instance in the Diagram Window or in the Design Browser
Window.
Note
If you want to update multiple symbol instances, hold down the Shift key on your
keyboard and click the symbol instances to select them. Once you have selected the
symbol instances, right-click one of the selected instances. If a symbol has been used
more than once in a diagram, you must select every instance that you want to update. If
you select only one instance of the symbol, only that instance is updated.
2. A pop-up menu is displayed. Select Update Symbol from the pop-up menu.
Alternatively, you can click the symbol, press Space Bar and enter Update Symbol.
The Update Symbol - Options Dialog is displayed.
3. Select the options as required and click OK; the symbol instances are updated to the
latest version.
Composite Symbol
A composite symbol represents an electrical device containing one or more blocks. The blocks
are represented by nested device symbols that also exist within Capital Symbol as individually-
selectable symbols. The complete composite may also contain optional internal connectivity
and cross-reference placeholders.
When placing a composite symbol in Capital Logic, you have the choice of placing the
complete composite or any of the sub-blocks. If you place the complete composite, the placed
graphics will match the composite symbol. If you place one of the sub-blocks, the placed
graphic will match the original sub-block symbol. If you then want to place a second instance
(or nth instance) of the device, you can again choose to place either the complete composite or
one of the sub-blocks.
Note
If the project preference Disallow pin duplication within a design is set, you cannot place
the composite and a sub block together as this would create duplicate instances of the same
pin. To allow such placement, the project preference Disallow pin duplication within a design
should be unset.
The composite symbol can be used as a plug map that you use to create a shared pin list for a
device in Capital Project. See the Capital Project help system for more information. Note that
when you set whether pins are reserved or reusable, the pins on an individual block must all be
reusable or all reserved for the same designs.
When you add the shared device to a diagram in Capital Logic, the blocks can be used to refine
the selection of pins and to enable you to place a more specific symbol representing the pins in
that instance on the diagram. See“Adding a Shared Device/Connector/Splice to a Diagram” on
page 186 for more information.
See “Cross-References on Objects” on page 199 for more information about how cross-
references work with composite symbols.
From Capital Logic, you can change the composite symbol that is used for a shared device.
Procedure
1. After the changes to the symbol block have been saved, open the diagram window for
the composite symbol in Capital Symbol or the diagram window containing the instance
of the composite symbol in Capital Logic. Right-click on the instance of the symbol
block and select the Update Instances option from the pop-up menu. If more than one
symbol block has been changed, you can select all of the symbol blocks at the same
time.
Alternatively, you can select the symbol blocks to be updated, press Space Bar and enter
Update Symbol.
2. The symbol block is updated in the composite symbol. If the number of pins on the
symbol used as the symbol block has changed, the instance is not updated.
Properties on the shared pin list for the shared device will be preserved after replacing the
symbol.
There are a number of pre-requisites that must be met before you can perform this action:
Procedure
1. Right-click on the device in the Shared Objects Browser Window and select the Replace
Shared Composite option from the pop-up menu. Alternatively, click on the device,
press Space Bar and enter Replace Shared Composite.
2. The Replace Shared Composite facility is displayed.
The Source Composite area shows the name of the shared device, the symbol library
where the current symbol is stored and the name of the symbol that is currently used.
The current symbol is displayed below those details.
The Target Symbol Selection enables you to navigate to the composite symbol that you
now want to use. When you select a symbol, it is displayed in the window below the
symbol libraries tree.
Select the composite symbol that you want to use by clicking on it in the tree.
3. On the Resulting Action tab, the actions that will result from replacing the composite
symbol are displayed.
4. On the Mapping tab, the symbol blocks from the previously used symbol are displayed
in the Source window, the symbol blocks from the new symbol are displayed in the
Target window. If you hold the mouse cursor over the name of a symbol block, the
names of the pins on the block are displayed.
You must associate the blocks from the previously used symbol with the blocks on the
new symbol. Associated blocks are displayed in bold. Blocks in italics must be mapped
for the action to continue (these are blocks that have instances).
When you select a new symbol, similar blocks are associated automatically. You can
disassociate all blocks by clicking the Disassociate All button. To disassociate one
target symbol block, click on it in the Target window and click the Disassociate button.
To associate all of the previously used symbol blocks click the Associate All button. To
associate one previously used symbol block, click on it in the Source window, click on
the target block in the Target window and click the Associate button.
5. Click the OK button to replace the symbol. The symbol blocks and composite symbols
on the diagrams are updated accordingly.
Related Topics
Map Pins Dialog (for Symbol)
Updating Symbols
Update Symbol - Options Dialog
Replacing a Symbol with a Compatible Symbol
Procedure
1. Right-click on the object represented by the current symbol either in the diagram or in
the Design Browser Window and select the Replace Symbol option from the pop-up
menu. Alternatively, click on the object represented by the symbol, press Space Bar and
enter Replace Symbol.
2. The Select Symbol dialog is displayed. In the browser tree, select the symbol that you
want to use as the replacement symbol and click the OK button. When you select a
symbol, it is displayed in a preview window. The OK button is enabled only if the
symbol is compatible with the current symbol.
The Map Pins Dialog (for Symbol) is displayed.
3. Map the pins from the replacement symbol to pins on the symbol instance and specify
what data on the symbol instance you want to preserve.
4. The new symbol replaces the old symbol.
Results
• The new symbol library contains device symbols and a composite device symbol. The
names of these are inherited from the names of the selected devices.
• The composite includes the selected devices with internal connectivity (links) that
represents the selected wires/nets/splices.
• The graphics of the composite symbol include any comment graphics, text and comment
symbols from the selected objects.
• The blocks within the composite symbol retain their attached analysis models.
Note
This is only applicable if normal symbols are used in the original selection. If a
composite symbol has been included in the original selection, then any analysis
model associated with that symbol will not be propagated to the new composite symbol.
• If more than one instance of a single conductor is selected, a separate internal link is
created for each instance.
Select this if you want to maintain any pin names that have been changed manually on
the diagram. If you do not select this, they will be replaced with pin names from the
symbol library. Optional.
Creates an automatic mapping for each of the Symbol pins or Library part pins to the
Instance pins. This is not available if some pins have been mapped already.
• Disassociate
Unmaps a pin on the replacement symbol from a pin on the symbol instance. Select one
of the mapped pins from either Instance pins, Symbol pins or Library part and click this
to unmap them.
• Disassociate All
Unmaps all of the Symbol pins or Library part pins and Instance pins.
• Changes
Lists the changes that will be made to the symbol instance when you click OK.
• Preserve Diagram Pin Position
Select this if you want the pins on the symbol instance to remain where they are in the
diagram already.
• Remove Properties not on Symbol
Select this if you want to remove any properties from the symbol instance that are not on
the symbol in the symbol library. Displayed when using the Replace Symbol action.
• Copy Attribute/Property Values from Symbol
Select this if you want to copy any properties and attributes that are on the symbol in the
symbol library to the symbol instance. Displayed when using the Replace Symbol action.
• Preserve Attribute Text
Select this if you want to maintain the visibility of the object attributes on the diagram. If
you do not select this, they will no longer be displayed. Displayed when using the
Replace Symbol action.
• Preserve Pin Names
Select this if you want to maintain any pin names that have been changed manually on
the diagram. If you do not select this, they will be replaced with pin names from the
symbol library. Displayed when using the Replace Symbol action.
The Capital Design Tools - Common Functions User Guide contains full details of the
options available for configuring Projects, Designs, Print Regions and Diagrams for Printing
and Printing to a File.
Available Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
Available Topics
The following topics are available:
Printing
These topics detail how to select one or more diagrams to be sent to a printer or plotter, either
installed on the local machine or available on the network.
Printing to a File
These topics detail how Print to File can export the design data from one or more diagrams to
either PDF, DXF, CGM or SVG format.
These topics detail how to add print regions to a design, with additional topics on resizing,
moving and editing print regions once created:
Printing Dialogs
This section offers a description of all dialogs related to printing functions. For each dialog, all
fields are listed, along with a full description of the field’s function.
This section details the reports available, and explains the options available to configure and
style your own reports.
Generating Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Reporting on Single Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Reporting on a Build List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Saving a Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
Printing a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
Available Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Using the Report Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Custom Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Generating Reports
The following topics detail how to select one or more designs as the basis for a report, then to
generate a report using one of the default types before saving or printing the results:
Reporting on Single Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Reporting on a Build List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Saving a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
Printing a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
Available Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
3. Select the build list(s) upon which you want to base the report. The list supports the
Multiple Selection of build lists.
4. Select the report type to generate (see “Available Reports” on page 353 for a full list of
the available types).
5. Click View Report. The report is displayed in a new window.
Related Topics
Reporting on Single Designs
Saving a Report
Printing a Report
Saving a Report
This topic details how to save the results from a report as an html file, which can be viewed in
any internet browser.
Procedure
1. Generate the report, following the steps detailed in “Reporting on Single Designs” on
page 350 or “Reporting on a Build List” on page 350.
2. Click Save Report. A generic Save dialog is displayed.
3. Enter a File name for the report, and specify the location in which to save it before
clicking Save.
Related Topics
Reporting on Single Designs
Reporting on a Build List
Printing a Report
Printing a Report
This topic details how to send the results from a report to a printer, either installed on the local
machine or available on the network.
Procedure
1. Generate the report, following the steps detailed in “Reporting on Single Designs” on
page 350 or “Reporting on a Build List” on page 350.
2. Click Print. A generic Print dialog is displayed.
3. Configure the printout as required before clicking OK. The report is sent to the specified
printer.
Related Topics
Reporting on Single Designs
Reporting on a Build List
Saving a Report
Available Reports
The following reports are available by default:
For information on adding your own reports and styling the appearance of the default report
types, see “Custom Reports” on page 363.
Assembly BOM
This report lists all assemblies used on the selected design(s), along with a breakdown of each
assembly’s contents. For each assembly, the following information is displayed:
• Part Number
The unique number identifying the assembly.
• Quantity
The number of times the assembly is used on the design.
• Assembly Contents
The constituent parts of each assembly are listed individually.
o Part Number
The unique number identifying the component.
o Quantity
The number of times the component is used within the assembly.
Component BOM
This report lists all library components used on the selected design(s), along with the number of
each component used. For each component, the following information is displayed:
• Part Number
• Default Name
The default name of the wire within the selected design.
• Design
The name of the design.
• Design Abstraction
The abstraction(s) assigned to the design.
• Generated Name
The generated name of the wire on the diagram.
• Harness
The name of the harness in which the wires exist.
• Included On BOM
Indicates if the wire is included on the bill of materials.
• Included On Cut Chart
Indicates if the wire is included on the cut chart.
• Length Change Type
Specifies the Length Change Type is applied to the wire: Neither; Absolute or Offset.
• Length Change Value
Specifies a value used to override the calculated wire length, based on the Length
Change Type.
• MCAD ID
If the harness was bridged in from an MCAD application, this field displays the
component's unique identifier as derived from the external data.
• Modified Length
The modified length of the wire.
• Multicore
The name of any multicore to which the wire belongs.
• Name Overridden
The previous name of the wire if it has been overridden.
• Option Expression
The options applied to the wire.
• Outside Diameter
Specifies the outside diameter of the wire.
• Part Number
The part number of any library part associated with the wire.
• Poke Home
Indicates if the wire is poke home wire, connected during installation.
• Revision
The design revision.
• Status
The release status of the design.
• Supplier Name
The name of the supplier from which the component is sourced.
• Supplier Part Number
The number used by your supplier to identify the component.
• Terminal Material Code
The terminal material code applied to the end of the wire.
• Type Code
The component type, as defined within the library.
• Unmodified Length
The unmodified length of the wire.
• Wire Color
The color of the wire.
• Weight
The total weight of the harness.
• Wire Material
The material from which the wire is manufactured.
• Wire Note
Any additional information recorded against this wire.
• Attributes
Lists the attributes of the wire applicable for the Capital Logic design, together with a
text box to specify your required attribute. You can enter more than one attribute using a
semi-colon separated list.
• Properties
Lists the properties of the wire applicable for the Capital Logic design, together with a
text box to specify your required property. You can enter more than one property using a
semi-colon separated list.
• Reset
Resets all attributes and properties to their previous state prior to starting modifications.
• Clear
Clears all attributes and properties
Lists the mated pin properties as entered in the text box for the start of a wire in Capital
Logic Designs.
Multicore List
This report lists all multicores on the selected design(s). For each multicore, the following
information is displayed:
• Name
The unique identifier for the multicore within the selected design.
• Design
The design upon which the multicore appears.
• Part Number
The part number of any library part associated with the multicore.
• Multicore Contents
A listing of the wires and child multicores assigned to the multicore.
• Multicore Parent
Net List
This report lists all nets on the selected design(s). For each net, the following information is
displayed:
• Net ID
The unique identifier for the net within the selected design.
• Component (Device/Connector) : Pin
The components and pins between which the net is connected.
Note
The default comment symbol for the connector assigned to the library part will also be
displayed, if defined.
• Pin
The name of the pin at which a wire is terminated.
• Design Revision
The Design Revision where conductors are present.
• Diagram
The name of the diagram.
• Zone
The zone in which the shared object appears on the diagram.
• Conductor
The conductors connected to the pin lists.
• PinMated / PinBackshell
The mated or backshell pin name details applicable in Capital Logic Designs.
Wire List
This report lists all wires on the selected design(s), along with the pins at which they are
terminated. For each wire, the following information is displayed:
• Name
The unique identifier for the wire within the selected design.
• Component 1
The name of the component at which end 1 of the wire is terminated.
• Connector 1
If the wire is terminated at the component identified in the Component 1 field, above,
via a connector, the connector is identified here.
• Pin 1
The name of the pin at which end 1 of the wire is terminated.
• Component 2
The name of the component at which end 2 of the wire is terminated.
• Connector 2
If the wire is terminated at the component identified in the Component 2 field, above,
via a connector, the connector is identified here.
• Pin 2
The name of the pin at which end 2 of the wire is terminated.
• Color
The color of the wire insulation.
• Length
The length value assigned to the wire, either by manually entering a wire length, or via
the bridging in of wire lengths from an MCAD application.
• Gauge
The cross-sectional area of the wire core.
• Type
The type of report being generated. For Capital Logic this is specified as “Logic”.
• Attribute
This element displays the attribute value in the column title, for example “Name” -
listing the name attributes of the wire.
• Property
The property element displays the property value in the column title. for example
“Signal” - listing the signal properties of the wire.
• Wireendexpressions
This element contains all expressions listed below, that are applicable in a wire reports,
as well as the start and end fields of the wire.
• Component
For further information see Using the Report Builder in the Capital Design Tools - Common
Functions User Guide.
Custom Reports
The option is available to deploy custom reports using the Capital extensibility architecture,
adding reports of your own design as compiled plugins, which can then be accessed from within
the Reports dialog.
Note
The use of custom reports does not consume an extensibility license.
Custom report plugins are managed in the same way as all extensibility plugins; see
“Extensibility Plugins” on page 70 for more information.
For detailed information on the creation of custom report plugins, see the
CustomReportDevelopment.pdf document, located in the doc\plugin sub-directory of your
Capital installation directory.
The following sections explain how to add and edit graphical shapes and graphical objects in a
diagram.
Borders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Adding a Border to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Replacing a Border on a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Removing a Border from a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Graphic Drawing Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
Drawing a Line in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
Drawing a Rectangle in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Drawing a Polygon in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Drawing a Circle in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
Drawing an Arc in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
Drawing a Curved Line in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
Adding Text Frames to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Adding a Picture to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Changing the Picture in an Image Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Adding a Comment Symbol to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
Resizing a Comment Symbol in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
Adding Properties to a Graphical Shape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
Editing a Property Value of Graphical Shape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
Editing the Graphical Properties of a Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
Stretching a Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
Moving a Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
Deleting a Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
Grouping Graphical Shapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
Ungrouping Graphical Shapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
Controlling the Layering Order (Z-Order) of Graphical Shapes and Objects . . . . . . . . . . 378
Graphics Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
Adding a Graphics Point to a Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
Deleting a Graphics Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
Grip Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Adding a Grip Point to an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Deleting a Grip Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Graphics Related Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
Edit Border Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
Add Text Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Image Selection Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
Borders
The following topics explain how to add and edit the border in a diagram.
“Adding a Border to a Diagram” on page 367
3. To insert a waypoint into the line, click once again on the diagram, otherwise, place the
second end of the line by double-clicking or by pressing the Enter key.
Note
In Capital Logic, if you click once on a pin, connector or device before clicking to
start drawing the graphic, the graphic is automatically associated with the object
(that means, if the object is moved, the graphic moves with it).
Note
In Capital Logic, if you click once on a pin, connector or device before clicking to
start drawing the graphic, the graphic is automatically associated with the object
(that means, if the object is moved, the graphic moves with it).
3. Click once on the diagram to place further corners and double-click on the diagram or
press the Enter key to place the last corner.
Note
In Capital Logic, if you click once on a pin, connector or device before clicking to
start drawing the graphic, the graphic is automatically associated with the object
(that means, if the object is moved, the graphic moves with it).
3. Drag the cursor away from the center and click once on the diagram to place the edge of
the circle.
Note
In Capital Logic, if you click once on a pin, connector or device before clicking to
start drawing the graphic, the graphic is automatically associated with the object
(that means, if the object is moved, the graphic moves with it).
Note
In Capital Logic, if you click once on a pin, connector or device before clicking to
start drawing the graphic, the graphic is automatically associated with the object
(that means, if the object is moved, the graphic moves with it).
Procedure
1. Press Space Bar and enter Curve. The cursor changes to .
2. Click on the diagram to place the first end of the curved line.
3. Click once on the diagram to place further points along the curve and double-click on
the diagram or press the Enter key to place the second end of the curved line.
Note
In Capital Logic, if you click once on a pin, connector or device before clicking to
start drawing the graphic, the graphic is automatically associated with the object
(that means, if the object is moved, the graphic moves with it).
2. Click on the diagram to place the first corner of the text frame.
3. Click on the diagram to place the opposite corner of the text frame. The Add Text
Dialog is displayed.
4. Enter the text that you want to display in the box at the bottom of the Add Text dialog.
5. Click OK..
Note
If the text is not displayed, the text frame is not large enough for the text. To increase
the size of the text frame, place the mouse cursor over a corner of the frame so that
the stretch icon is displayed, hold down the left mouse key and drag the corner.
Results
The text frame and text is added to the diagram.
Note
In Capital Logic, if you click once on a pin, connector or device before clicking to start
drawing the graphic, the graphic is automatically associated with the object (that means, if
the object is moved, the graphic moves with it).
Procedure
1. Press Space Bar and enter Image. The cursor changes to .
2. Click on the diagram to place the first corner of the image frame that will contain the
image.
3. Click on the diagram to place the opposite corner of the image frame. The Image
Selection Dialog is displayed.
4. In the window listing files, select the image file containing the picture that you want to
add.
5. Click Select. The image frame and picture is added to the diagram. The picture is scaled
to fit the image frame.
Note
In Capital Logic, if you click once on a pin, connector or device before clicking to
start drawing the graphic, the graphic is automatically associated with the object
(that means, if the object is moved, the graphic moves with it).
Related Topics
Changing the Picture in an Image Frame
2. Either:
• Press Space Bar and enter Properties.
• Right-click on the selected entity and select Properties
• Double-click on the graphical shape.
3. The Edit Properties: Propertied Graphic Dialog is displayed.
4. On the General tab, click the ellipsis (...) button next to the Image File field.
The Image Selection Dialog is displayed.
5. In the window listing files, select the image file containing the picture that you want to
add.
6. Click Select. The new picture is displayed in the image frame.
Related Topics
Adding a Picture to a Diagram
Procedure
1. Press Space Bar and enter Comment Symbol.
The Symbol Selection Dialog is displayed.
2. In the Symbol Selection tree, select the comment symbol.
1. Move the mouse cursor over the symbol; a bounding box is displayed.
2. Move the mouse cursor over a corner of the bounding box so that the stretch icon ( ) is
displayed, hold down the mouse button and drag the corner to resize the symbol. The
symbol is scaled proportionally along both the X-axis and Y-axis.
Related Topics
Adding a Comment Symbol to a Diagram
Procedure
1. Select the graphical shape.
2. Move the cursor over a graphics point ( ) on the graphical shape so that the stretch icon
( ) is displayed next to it.
3. Hold down the left mouse button and drag the graphics point to stretch the shape.
2. Either:
• Press Space Bar and enter Group
• Right-click on one of the selected shapes and select Group
3. A frame is displayed around the shapes and you can edit them as one object.
Related Topics
Ungrouping Graphical Shapes
Sends the selected shapes one layer backward in the overlapping shapes.
Caution
Z-order settings for an object are lost if styling is applied to it, either manually or
automatically. If using z-order settings with conductors and symbols, ensure that you
apply the z-order to the symbol (for example, Bring To Front) and not to the conductor.
Prerequisites
• The graphical shapes must have been added to the diagram.
Procedure
In the diagram window, select one or more graphical shapes and either:
• right-click on a selected object and select Order > Bring To Front / Send To Back
/ Bring Forward / Send Backward
• press Space Bar and enter Bring To Front, Sent To Back, Bring Forward, or Send
Backward
Results
The selected shapes and objects change layer accordingly.
Graphics Points
The following topics explain how to add graphics points to graphical shapes in a diagram and
how to delete them.
A graphics point is a point at which you can stretch a graphical shape to resize or reshape it.
Procedure
1. Select the graphical shape on which the graphics point is located.
2. Press Space Bar and enter Delete graphics.
The cursor changes to .
Grip Points
A grip point is point that you add to a conductor or highway in Capital Logic, a bundle in
Capital Integrator and a bundle in Capital Harness XC. It divides the object into graphical
sections that can be resized and reshaped.
The following topics explain how to add a grip point to an object and how to delete it.
Procedure
1. Select the object on which the grip point is located.
2. Either:
• Press Space Bar and enter Delete grip point
• Right-click on the selected entity and select Grip Point > Delete.
The cursor changes to .
Note
If a placeholder was used as the value for a property in Capital Symbol, you
cannot edit it here. See Adding Information Placeholders to a Border in the
Capital Symbol User Guide for more information.
o Preview
Displays a preview of the current Layout selection.
Objects
• Symbol Selection
In the tree, navigate to a symbol in a symbol library and select it. The selected symbol is
displayed in the window to the right of the tree.
Select the color from the dropdown list; it is previewed in the window to the right of
the field. As well as color names, the list contains the following options:
• Default
The default color used for the object by the system.
• background
The same color used for the background of the diagram. The color changes when
the background color is toggled.
• automatic
If the diagram background is white, the object is black, and vice versa.
• Choose Color
The Choose Object Color dialog is displayed, where you can select a color.
o Thickness
Specify the thickness of the lines of the graphical shape. Mandatory. To use the
default thickness, select Default from the dropdown list.
To use a different thickness, select Override from the first dropdown list and select
the type of thickness from the final dropdown list:
• Logical
These thicknesses do not have a physical unit of measurement. They provide a
logical progression of thickness with a default of 1. A line with thickness 2 is
displayed twice as thick as a line with thickness 1, and so on. When you zoom in
or out of a diagram, the line thickness does not appear any different.
You select the thickness from the middle dropdown list.
• Physical (unit of measurement)
The physical unit of measurement that has been specified as the Unit in the style
set applied to the diagram. The line thickness is displayed in relation to the grid
size of a diagram. When you zoom in or out of a diagram, the line grows or
shrinks to stay in scale with the grid.
When you select a unit, the middle dropdown list changes to a free text field
where you specify the thickness. The value can be any floating-point number up
to three decimal places.
See Physical Line Thickness in the Capital Design Tools - Common Functions
User Guide for a definition and links to related task flows.
o Line Style
Specify the style of the lines of the graphical shape. Mandatory. To use the default
style, select Default from the dropdown list.
To use a different style, select Override from the dropdown list and select the style
from the second dropdown list that is displayed.
o Fill Pattern Selection
Specify the fill pattern of the graphical shape. Mandatory. Displayed only for a
graphical shape that encloses space. To use the default fill pattern, select Default
from the dropdown list.
To use a different fill pattern, select Override from the dropdown list and click
Change to display the Fill Pattern Selection Dialog where you select a fill pattern.
Grouping Objects
You can group and ungroup graphical objects so that they can be selected, and moved, aligned
or distributed, as a single entity.
Procedure
See Grouping Objects in a Diagram in the Capital Design Tools - Common Functions User
Guide.
Aligning Objects
You can align objects in a diagram.
Procedure
See Aligning Objects in a Diagram in the Capital Design Tools - Common Functions User
Guide.
Distributing Objects
You can distribute objects in a diagram so that there is an equal distance between them.
You can distribute all objects apart from pins and indicators in a diagram window.
Procedure
See Distributing Objects in a Diagram in the Capital Design Tools - Common Functions User
Guide.
Flipping Objects
You can flip objects horizontally or vertically about their centers in a diagram.
Procedure
See Flipping Objects in a Diagram in the Capital Design Tools - Common Functions User
Guide.
Rotating Objects
You can rotate objects about a specified point in a diagram and also freely rotate primitive
graphical objects and comment symbols around their center point.
Procedure
See Rotating Objects in a Diagram in the Capital Design Tools - Common Functions User
Guide.
Procedure
See Free Rotation of an Object or Comment Symbol in the Capital Design Tools - Common
Functions User Guide.
Procedure
See Setting Snap To Object in the Capital Design Tools - Common Functions User Guide.
If you select multiple objects of different object types, the selection of tabs displayed on the
Edit Properties facility may be limited. In addition, the properties and attributes that you can
edit may be limited. This is because not all properties and attributes can be applied to all object
types.
For example:
If you select a wire and a device, a Wire Color attribute is listed but you cannot change it
because it cannot be applied to all of the selected objects.
Even if a property is not editable because it does not apply to all selected objects, you can still
change whether it is visible or not.
If any of the selected objects are frozen, you can edit only graphical properties.
In Capital Logic:
Edit Properties facilities for all objects (excluding object name text) contain the
following tabs (if you have selected multiple objects, any changes to the parameters on
these tabs apply to all selected objects):
o General (see “Editing an Object's General Properties” on page 406)
o Graphical (see “Editing an Object's Graphical Properties” on page 425)
o Properties (see “Adding a Property to an Object” on page 411)
The Edit Properties facilities for devices, connectors and splices includes the following
tab:
o Parameters (see “Editing Objects Parameters” on page 444)
The Edit Properties facilities for modular connectors includes the following tab:
o Modular (see “Assigning Connector Positions Using the Modular Tab” on
page 443)
The Edit Properties facilities for conductors include the following tab:
o Text (see “Editing Text Attributes for an Object” on page 439)
The Edit Properties facility for a shared object and cross-reference text displays the
following tab:
o Cross-references (see “Editing the Graphical Properties of Cross-References” on
page 441)
In Capital Integrator:
Edit Properties facilities for all objects (including symbol graphics) contain the
following tabs (if you have selected multiple objects, any changes to the parameters on
these tabs apply to all selected objects):
o General (see “Editing an Object's General Properties” on page 406)
o Graphical (see “Editing an Object's Graphical Properties” on page 425)
o Rules
o Properties (see “Adding a Property to an Object” on page 411)
The Edit Properties facility for a signal displays the following tab:
o Variance (see “Specifying Option-Specific Values for Net Attributes and
Properties” on page 422)
Note
The Variance tab will not be displayed for an object if there are no options
defined in a project or if the project preference for Mandate applicable options
has been set and the design does not have any applicable options.
In Capital Symbol:
The Edit Properties facility for symbol graphics and borders include the following tab:
o Graphical (see “Editing an Object's Graphical Properties” on page 425)
o Properties (see “Adding a Property to an Object” on page 411)
The Edit Properties facility for a border includes the following tabs:
o General (see “Editing an Object's General Properties” on page 406) - note that the
General tab for a border in Capital Symbol allows you to specify placeholders for
design information that is then displayed automatically when you add the border to a
diagram. See Adding Information Placeholders to a Border in the Capital
Symbol User Guide for more information about doing this.
o Paper Layout (see Editing the Paper Layout Properties of a Border in the
Capital Symbol User Guide) - This provides information about the paper size and
usable area within the border.
See “Viewing the Library Part Details for an Object” on page 416.
• To specify the specification attributes for a conductor.
See “Defining Specification Attributes for a Conductor” on page 416.
• Specify the Slot Type.
This indicates whether the slot will be an equipment slot (contains normal devices), a
ground slot (contains ground devices) or a junction box slot (you can route signals
through a junction box slot). See “Implementing Ground Wiring in the Generative
Flow” on page 211 for more information about ground devices.
See “Specifying the Slot Type” on page 417.
• Assign variant Options to an object.
Specifies the variant harness options that are applicable to this design object (set for the
diagram's design using the Capital Project application). The options specified for a
design object in Capital Logic or Capital Integrator are used to distinguish the
individual variant harness designs when applying the Evaluated Designs facility in the
Capital Project application. See the Capital Project help system for more information
on Evaluated Designs. Options are not applicable to Capital Symbol.
See “Assigning or Editing an Object's Options” on page 417.
o Modules - In Capital Logic only, allows Functional Module Codes that are available
to a design, to be assigned to, amended or removed by clicking the ellipsis button,
(...), next to the Modules field. This will display the Modules dialog where you can
edit the required Functional Module code(s). Applies to connectors, multicores,
overbraids, ring terminals, shields, splices and wires only.
See “Assignation of Module Codes to Capital Logic Components” on page 72
Note
The Modules field will only display if the project has been configured to use module
codes. See Module Codes, Options preference settings in the Capital Design Tools
- Common Functions User Guide for details of how to configure the project.
Note
With the exception of pins, you can rename an object to have the same name of
another object in the same diagram. If you do this, the name is displayed in red and
a warning is displayed when you click the OK button.
If you are editing the properties of a multicore indicator, the multicore name is displayed
in the Name field.
If you are editing the properties of a signal, you can edit the name only if the signal is
not associated with a functional source net conductor from the associated Capital Logic
design.
If a shared object has been frozen, you cannot change its name.
If you have assigned a library part to the object and usage definitions have been created
for the library part in Capital Project, the Name Selection dialog lists only the names
that are used in the usage definitions by default. You can display all available names for
the object type by unchecking the Filter on Usage box at the top of the dialog. See the
Capital Project help system for more information about usage definitions.
If you are editing the general properties for a net conductor and it connects to a device
that has a usage definition in Capital Project, the Name Selection dialog lists only the
names that have been added for the corresponding pin in the usage definition.
If a net conductor is connected to more than one device with a usage definition, the list
of net names displayed depends on the pin types to which it is connected. The pin types
can be IN, OUT, IxO, IxO Terminated, NC, PWR and GND. These are defined in
Capital Library. See the Capital Library help system for more information about
defining pin types.
In Capital Symbol, you can specify the pin type U that means that no pin type is
specified.
3. Check the Visible box if you want the specified name to be displayed with the object in
the diagram.
The name is displayed once for each object. However, in the case of conductors, you can
display the name next to more than one segment of the conductor. See “Displaying a
Conductor Name For Multiple Segments of a Conductor” on page 454 for more
information. If name text has been added to segments previously and has not been
deleted, checking the Visible box will display the name text for each instance of name
text that has been added.
4. Click the Edit Attributes button to display the Edit Name Text Attributes facility
where you can set the following attributes for the name that is displayed on the diagram:
• Justification - where you want the text to be displayed in relation to the object.
• Clip
If selected, specifies that the text is clipped at the edge of its bounding box.
• Shrink to fit
If selected, specifies that the font of the text reduces as necessary so that the text fits
in its bounding box.
• Overflow
If selected, specifies that the text ignores the edge of its bounding box and flows out
of it.
• Wrap text
Specifies whether the text wraps onto multiple lines when it reaches the edge of the
text bounding box (selected) or whether the text ignores the bounding box and
continues on one line (unselected). When this is selected, if a word is too long to fit
on a single line, it is wrapped by character. Mandatory.
• Rotation - rotates the text to change the angle at which it is displayed. By default
this is 0 which displays the text running left to right following the horizontal axis:
. Enter a different value manually or select a value from the dropdown list, for
example, 270 .
• Auto flip - if selected, the text flips automatically so that it is never displayed upside
down when it is rotated or flipped. If not selected, a flip or rotation can result in the
text being displayed upside down.
• Color - the color of the text. To change the default color, select Over-ride from the
drop-down list on the left. This enables the box on the right that you can click to
display the Choose Text Color facility.
• Opacity - select one of the following from the drop-down list:
o Transparent - object lines are visible behind the text.
o Opaque - object lines are not visible behind the text.
• Font - select the font used for the text from the drop-down list.
• Height - the height of the text. You select the unit of measurement from the drop-
down list.
Click the OK button to exit the Edit Name Text Attributes dialog.
. Enter a different value manually or select a value from the dropdown list, for
example, 270 .
• Auto flip - if selected, the text flips automatically so that it is never displayed upside
down when it is rotated or flipped. If not selected, a flip or rotation can result in the
text being displayed upside down.
• Color - the color of the text. To change the default color, select Over-ride from the
drop-down list on the left. This enables the box on the right that you can click to
display the Choose Text Color facility.
• Opacity - select one of the following from the drop-down list:
o Transparent - object lines are visible behind the text.
o Opaque - object lines are not visible behind the text.
• Font - select the font used for the text from the drop-down list.
• Height - the height of the text. You select the unit of measurement from the drop-
down list.
Click the OK button to exit the Edit Name Text Attributes dialog.
Note
The property names in the drop-down list are predefined for object types in a project
in Capital Project. See the Capital Project help system for more information on
creating them. When a project is defined in Capital Project, the valid values for a the
property can be specified. If you enter a property value that is not valid in Capital Logic
or Capital Integrator, a warning is generated.
3. The property is added to the properties box. In the property's row, click the following
columns to change their values:
• Name - the name of the property. This box cannot be edited.
• Value - the value of the property. This is the value that is displayed with the object
in the design if you tick the Visible box.
• Type - the type of value that the property can have. The following options are
available:
o String - a mixture of letters, numbers and special symbols.
o Integer - a whole number.
o Float - a decimal number.
• Editable (only in Capital Symbol) - check the box if you want the Value and Type
fields to be editable in other applications.
• Visible - check the box if you want the specified Value to be displayed with the
object on the design. If style set options have been defined for the property, those
options are used to define the appearance of the value. Otherwise, the Attributes
defined in this table define the appearance.
• Attributes - click Edit to display the Edit Text Attributes facility where you can
set the following attributes for the Value text that is displayed for this property on
the diagram:
o Justification - where you want the text to be displayed in relation to the object.
o Clip
If selected, specifies that the text is clipped at the edge of its bounding box.
o Shrink to fit
If selected, specifies that the font of the text reduces as necessary so that the text
fits in its bounding box.
o Overflow
If selected, specifies that the text ignores the edge of its bounding box and flows
out of it.
o Wrap text
Specifies whether the text wraps onto multiple lines when it reaches the edge of
the text bounding box (selected) or whether the text ignores the bounding box
and continues on one line (unselected). When this is selected, if a word is too
long to fit on a single line, it is wrapped by character. Mandatory.
o Rotation - rotates the text to change the angle at which it is displayed. By default
this is 0 which displays the text running left to right following the horizontal
axis: . Enter a different value manually or select a value from the dropdown
o Auto flip - if selected, the text flips automatically so that it is never displayed
upside down when it is rotated or flipped. If not selected, a flip or rotation can
result in the text being displayed upside down.
o Color - the color of the text. To change the default color, select Over-ride from
the drop-down list on the left. This enables the box on the right that you can click
to display the Choose Text Color facility.
o Opacity - select one of the following from the drop-down list:
Transparent - object lines are visible behind the text.
Opaque - object lines are not visible behind the text.
4. Click OK to apply the specified property values and exit the facility.
• Font - select the font used for the text from the drop-down list.
• Height - enter the height of the text in the box and select the unit of measurement
from the drop-down list.
If a property does apply to all of the selected objects but the objects have different values for it,
Multiple Values is displayed in the Value field with a drop-down list of the different values.
You can select one of these values and check the box at the start of the Value field to apply it to
all selected objects or you can leave the field as Multiple Values so that the objects retain their
different values. Alternatively, you can enter an entirely new value that will apply to all of the
selected objects.
If there is a list of possible values defined for a property, these are listed in the drop-down list
with the used values in the Value field. Any values that are already used on the selected objects
are displayed in bold.
If a property has a different Type value (string, integer or float) on different objects, then you
cannot edit it and Different Types is displayed in the Value field
The bundle length is used when calculating the cost of any synthesized wiring. Overriding the
length can therefore change the result of routing logical signals because the system selects the
cheapest route.
If the library part has device connectors, device connectors are added to the device in Capital
Logic. In the case of a shared device, the device connectors are added to the shared instances.
See “Overview of Device Connectors and Harness Connectors in Capital Logic” on page 214
for more information about device connectors.
If a library part has a symbol associated with it, the graphical representation of the device in
Capital Logic does not change to the symbol when you assign that library part to it.
Note
Library Part Usage on Shared Objects in Capital Logic
When a library part is assigned to a shared pin list, if the number of pins/cavities on the library
part is greater than the number of pins on the pin list, the number of pins necessary to account
for difference is added to the shared pin list.
When a library part is assigned to a shared device, if you have selected a symbol for the library
part, that symbol is added to the shared device and you are presented with a dialog to map
shared pins to the symbol pins.
Procedure
1. Right-click on the object and select Properties; the Edit Properties dialog is displayed.
2. Click the Add (...) button in the Library Part section of the General tab; the Part
Selection Dialog is displayed.
3. Search for the library part, select it and click Insert.
4. If you are assigning a library part to a device, connector or backshell, the Associate
Pins with Cavities dialog is displayed. You must associate the cavities from the library
part with the pins on the object. See “Associating Library Cavities with Pins” on
page 439 for more information about this dialog. When you have associated the cavities
with the pins, click the OK button.
If you are assigning a library description to a multicore, the Assign Library Multicore
dialog prompts you to assign the innercores from the library multicore to the multicore
wires in the design. See “Assigning Wires from Library Multicores to Wires in a
Design” on page 303 for more information about this dialog. When you have associated
the multicore wires, click the OK button.
5. The library part number is displayed at the top of the Library Part section of the
General tab.
Note
If the details for a library description are changed in Capital Library, they are not
updated automatically in Capital Logic or Capital Integrator, you must update them
manually. See the To update an object's library part section below.
Procedure
1. Right-click on the object and select Properties; the Edit Properties dialog is displayed.
2. Click the Update ( ) button in the Library Part section of the General tab.
3. The details for the library description are updated in the Edit Properties facility. Click
the OK button.
3. The details for the library description are removed from the Edit Properties facility.
Click the OK button.
3. The View Component facility is displayed. This is like the Part Selection facility but is
read-only. Click the Close button to exit the facility.
Procedure
1. Right-click on the object and select Properties; the Edit Properties dialog is displayed.
2. In the Specification section of the General tab, specify the Color, Material, Spec and
CSA as required. If you want to display any of these attribute values next to the
conductor in the diagram, select the box next to the field and click the button to
display the Edit Graphical Attributes dialog where you specify how it is displayed.
3. Click OK to apply the specified values and exit the facility.
• Equipment - this indicates that the slot will contain normal devices
• Ground - this indicates that the slot will contain ground devices.
• Junction Box - this indicates that signals can be routed through this slot.
Note
The options that are available for assignment to the object in the Edit Option
Expression dialog box are initially created for the object's project and then assigned
to the object's design using the Applicable Options facility in the Capital Project
application. See the Capital Project help system for more information on creating and
assigning options and evaluated designs.
If no options have been assigned specifically to the design, the system displays all of the
options that have been created for the project.
If you attempt to enter an invalid option expression in the Expression box, the text is
If you attempt to enter an invalid expression in the Edit Option Expression dialog, an
error message is displayed.
3. Check the Visible box if you want the option expression to be displayed next to the
object on the diagram. You can set the attributes for the text that is displayed by clicking
the Edit Attributes button and specifying the following:
• Justification - where you want the text to be displayed in relation to the object.
• Clip
If selected, specifies that the text is clipped at the edge of its bounding box.
• Shrink to fit
If selected, specifies that the font of the text reduces as necessary so that the text fits
in its bounding box.
• Overflow
If selected, specifies that the text ignores the edge of its bounding box and flows out
of it.
• Wrap text
Specifies whether the text wraps onto multiple lines when it reaches the edge of the
text bounding box (selected) or whether the text ignores the bounding box and
continues on one line (unselected). When this is selected, if a word is too long to fit
on a single line, it is wrapped by character. Mandatory.
• Rotation - rotates the text to change the angle at which it is displayed. By default
this is 0 which displays the text running left to right following the horizontal axis:
. Enter a different value manually or select a value from the dropdown list, for
example, 270 .
• Auto flip - if selected, the text flips automatically so that it is never displayed upside
down when it is rotated or flipped. If not selected, a flip or rotation can result in the
text being displayed upside down.
• Color - the color of the text. To change the default color, select Over-ride from the
drop-down list on the left. This enables the box on the right that you can click to
display the Choose Text Color facility.
• Opacity - select one of the following from the drop-down list:
o Transparent - object lines are visible behind the text.
o Opaque - object lines are not visible behind the text.
• Font - select the font used for the text from the drop-down list.
• Height - enter the height of the text in the box and select the unit of measurement
from the drop-down list.
Click the OK button to exit the Edit Attributes dialog.
4. Click the OK button to exit the Edit Properties facility.
Procedure
1. Open the Edit Properties facility for the harness level. To do this, right-click on the
harness level in the Configuration Setting Browser Window and select the
Properties option from the pop-up menu. Alternatively, select the harness level in the
Harness Levels facility (see Defining a Harness Level in the Capital Integrator User
Guide) and click the Properties button.
2. Enter the part number in the Part Number field and click the OK button to close the
facility.
Procedure
1. In the Configuration section of the Edit Properties facility, click the ellipsis (...) button
next to the Level field.
2. The Edit Levels facility is displayed. The Available window displays the available
harness levels to which the wire has not been assigned. The Selected window displays
the harness levels to which the wire has been assigned. You can assign a wire to a
harness level by clicking on it in the Available window and clicking the Add button.
You can remove a wire from a harness level by clicking on it in the Selected window
and clicking the Remove button.
3. Click the OK button to confirm the changes and to exit the Edit Levels facility.
nodes.
For example:
A region has the following offset
values:
The following image indicates the sections of the bundle to which the offset distances
correspond:
3. In the diagram, red squares indicate the new locations of the region nodes. If you have
entered conflicting offsets, the offset values are displayed in red. Click OK to accept
your changes to the offsets.
4. The bundle region changes accordingly in the diagram window.
Related Topics
Editing the Properties of Objects
Note
The Variance tab will not be displayed for an object if there are no options defined in a
project or if the project preference for Mandate applicable options has been set and the
design does not have any applicable options.
Any properties specific to the individual net conductor or to the net conductor object type can
have option-specific values.
• WireColor
• WireCSA
• WireMaterial
• WireSpecification
In order for these attributes or net-specific properties to be available on the Variance tab, they
must have a valid value set on the Properties tab or General tab of the Edit Properties facility.
Procedure
1. Right-click on the net conductor in the diagram or Logical Design Browser Window and
select the Properties option from the popup menu.
2. Ensure that the attribute or property has a valid value set on the Properties tab or
General tab of the Edit Properties facility. This value is used as the default value when
no option expression has been applied to the net.
3. Click on the Variance tab and click the New button in the Option Variable Attributes
or Option Variable Properties section as appropriate.
4. The Option Selection dialog is displayed. From the dropdown list, select the attribute or
property and click the OK button.
5. A row for that attribute or property is added to the appropriate table. In the Options
column, specify the option expression to which the value applies. You can click on the
ellipsis (...) button to display the Edit Option Expressions facility that helps you to
define the expression. In the Value field, specify the option-specific value.
You repeat steps 2 to 5 for each option-specific value for that attribute or property.
6. Click the OK button to exit the Edit Properties facility.
Note
There are two design rule checks that can be run in Capital Integrator that are
relevant to these option-specific values, Wires violating specification rules and
Option-based variance inconsistency. See Checks applicable to Capital Integrator
designs in the Capital Design User - Common Functions User Guide.
An attribute is a quality or characteristic of an object within Capital. Object attributes are built-
in to Capital and particular tool behavior is inferred by their presence and value.
The attributes that are displayed in the Attributes section vary depending on the type of object.
If an attribute is editable for the object, its name and value are displayed in black in the Name
and Value column, otherwise they are grayed out. If you enter an invalid value, it changes to
red.
The Show All Attributes option is selected by default. Unselect this option to display only the
editable attributes on this tab.
When you have edited the attributes, you must click the OK button to exit the Edit Properties
facility and to commit your changes.
Note
If harness names have been created in Capital Project, you can click the ellipsis (...) button
by the Harness attribute value to select one.
In Capital Logic, you can specify the Harness attribute for an object either on the General tab
of the Edit Properties facility or using the Edit Harness Attribute facility. See “Specifying
the Harness Attribute for an Object” on page 438 for more information.
Related Topics
Using Quick Editing for Object Attribute Displayed on Diagram
Note
If pre-defined values are available for selection, an ellipsis (...) button is displayed
next to the field. Click that button to select a value.
You can expand the window to display the full Edit Properties dialog for the object by
clicking or by pressing ALT + Up Arrow.
You can hit the Esc button on your keyboard to cancel the action at any time.
If you want to edit the graphical display of the text, select it on the diagram and press
ALT + Enter on your keyboard to display the Attribute Text dialog box.
Related Topics
Editing an Object's Attributes
• Color - the color of the object as it is displayed in the diagram. See “Changing an
Object's Primary or Secondary Graphical Color Property” on page 425.
• Thickness - the thickness of the lines of the object in the diagram. See “Changing an
Object's Graphical Thickness Property” on page 426.
• Line Style - the style of the lines of the object in the design. See “Changing an Object's
Graphical Line Style Property” on page 426.
• Fill Pattern - whether a fill pattern is used in a polygon or closed object. See “Changing
the Fill Color Attribute for an Object” on page 427.
• Line Style (for lines and conductors in Capital Logic only) - the style of arrow at the end
of a line. See “Changing the Line End Style of a Conductor” on page 427.
Procedure
1. Select the color from the dropdown list; it is previewed in the window to the right of the
field. As well as color names, the list contains the following options:
• Default
The default color used for the object by the system.
• Background
The same color used for the background of the diagram. The color changes when the
background color is toggled.
• Foreground
If the diagram background is white, the object is black, and vice versa.
• Manual
The Choose Object Color dialog is displayed, where you can select a color.
2. Click OK to apply it.
Procedure
1. Select the Override option from the drop-down list box to the right of the Line Style
label.
2. Select the required line style from the drop-down list box.
3. Click the OK button to apply the selected Property to the Object.
4. The line style will display with the color currently selected in the Primary Color
setting.
Note
If the object is a highway or conductor in Capital Logic, or a bundle in Capital
Integrator, and the line style selected is broken, then the color of the gaps in the
broken line style can be set with the Secondary Color option
Procedure
1. Select the Over-ride option from the drop-down list box to the right of the Fill Pattern
label.
2. The Fill Pattern dialog is displayed. Click on the fill pattern that you want to use.
3. Specify the foreground color and background color that you want to use for the fill
pattern by clicking on the corresponding color box. The Foreground Color dialog box
is displayed in which you can select the color. Click the OK button to exit the color
dialog box.
4. Click the OK button to exit the Fill Pattern dialog.
When you select an arrow style, it is previewed in the window below the drop-down list.
If you do not want an arrow at the end of the conductor, select the blank line from the
drop-down list.
2. Click on the Right drop-down list and select the style of arrow that you want to display
at the right end of the conductor.
3. Click the OK button to apply the selected end line styles to the object.
Note
The style is applied to every end-segment of the conductor. An end-segment is a
segment where at least one end point is not connected to another segment from the
same conductor.
Assembly (Overview)
An assembly is a collection of objects that you can use as a single entity. It is treated as a design
wide object. It can contain wires, shields, nets, devices, connectors, conductor groups, inline
plugs and inline jacks, and other assemblies. Commercially Off the Shelf (COTS) cables are
also treated as assemblies. COTS cables are purchased in their made-up form containing multi-
conductors with one or more pre-connected connectors. For further information on COTS
cables see the Capital Library User Guide.
Adding assemblies from Capital Library automatically populates the design browser with the
correct child parts, improving quality and reducing design time. The part selection dialog assists
in assigning the correct assembly and sub-assembly parts. In addition, if the assembly contains
connectivity information then once the assembly is placed on the diagram the system auto-
routes the conductors defined in the assembly.
You can add comment graphics and comment symbols to a diagram so that those graphics and
symbols are associated with the assembly and form a graphical boundary around it.
Note
An assembly cannot contain shared objects.
This functionality can be used, for example, to create the graphical representation of a panel, a
line replaceable unit (LRU) or Commercially Off the Shelf (COTS) cables.
Creating an Assembly
This topic details how to create an assembly and specify the design objects that are included in
the assembly.
Procedure
1. Press Space Bar and enter Assemblies.
2. The Edit Assemblies facility is displayed. Click the Create button ( ); the New
Assembly dialog is displayed.
3. If you do want to use a default name for the assembly, leave the Default Name box
checked. Otherwise, uncheck the Default Name box and enter the assembly name in the
Assembly Name box. Click the OK button.
4. Click on the assembly in the Selected box. The Available box contains the objects that
can be added to the assembly. Select the objects that you want the assembly to contain
and click the Add ( ) button. You can leave the assembly empty for later use.
5. Any selected objects are added to the Selected box under the assembly. You can double-
click the assembly name to show or hide the objects in it. Click the OK button.
6. The assembly is added to the Assemblies folder in the Design Browser Window.
Note
You can right-click on the assembly in the Design Browser Window and select the
Extend Selection option from the pop-up menu to highlight all of the objects in the
assembly in the diagram window.
Related Topics
Assembly (Overview)
Removing an Object from an Assembly
Renaming an Assembly
Deleting an Assembly
Adding Associated Comment Graphics or Comment Symbols to an Assembly
Adding Objects Within the Associated Comment Graphic Boundary to an Assembly
Removing Objects No Longer Within the Associated Comment Graphic Boundary from an
Assembly
Extending the Selection of Objects for an Assembly Comment Graphic or Symbol
Results
The pre-validated assembly is placed on the diagram, system constraints having ensured that
only valid child parts have been used in the construction of the assembly.
• If the assembly has a part number but it's children do not then the Part Selection Dialog
on the children checks the structure of the assembly and only allows valid children.
• If the assembly does not have a part number but its children do then the Part select
Dialog on the assembly only allows assemblies which contain the children.
Renaming an Assembly
This topic details how to rename an assembly.
Procedure
1. Press Space Bar and enter Assemblies; the Edit Assemblies dialog is displayed.
2. Right-click on the assembly name in the Selected box and select Rename from the pop-
up menu; the Edit Assembly dialog is displayed.
3. Ensure that the Default Name box is unchecked and enter the new name in the
Assembly Name box. Click the OK button.
Related Topics
Assembly (Overview)
Creating an Assembly
Removing an Object from an Assembly
Deleting an Assembly
Adding Associated Comment Graphics or Comment Symbols to an Assembly
Adding Objects Within the Associated Comment Graphic Boundary to an Assembly
Removing Objects No Longer Within the Associated Comment Graphic Boundary from an
Assembly
Extending the Selection of Objects for an Assembly Comment Graphic or Symbol
Deleting an Assembly
This topic details how to delete an assembly.
Procedure
1. Press Space Bar and enter Assemblies; the Edit Assemblies dialog is displayed.
2. Click on the assembly in the Selected box and click the Delete ( ) button.
3. The assembly name is deleted and any objects under the assembly move from the
Selected box to the Available box. Any comment graphics or comment symbols
associated with the assembly are deleted.
Related Topics
Assembly (Overview)
Creating an Assembly
Removing an Object from an Assembly
Renaming an Assembly
Adding Associated Comment Graphics or Comment Symbols to an Assembly
Adding Objects Within the Associated Comment Graphic Boundary to an Assembly
Removing Objects No Longer Within the Associated Comment Graphic Boundary from an
Assembly
Prerequisites
• The assembly must exist in Capital Library
Procedure
1. Create an assembly following the process detailed in ***UNRESOLVED***. This
populates the design browser with all defined connectivity objects such as devices,
connectors, splices and so on.
Note
If you have read-write domain access permission you can save the design assembly
changes back into the library assembly by selecting Save Design into Assembly on
the ribbon.
2. Once the assembly is added to the diagram its pre-defined connectivity, including any
highway information is shown by ghosted lines. This enables the optimal placing of
objects and connectivity prior to saving the design. For further information see
“Preserving Connectivity” on page 184.
3. Save your design.
In this example, the box surrounding the diagram objects and the text ASSEMBLY1 are
comment graphics associated with an assembly called ASSEMBLY1. WIRE3 and WIRE5
pass out of the box to connect with other design objects not in the assembly. The inline jack J1
is part of the assembly whereas the inline plug P1 is not.
The visible graphical boundary can be any shape but the system creates an invisible rectangle
around the extents of the visible shape. This invisible rectangle represents the boundary for any
actions related to the assembly (such as Reset Assembly and Update Assembly).
Prerequisites
• The assembly must exist.
Procedure
1. In the Design Browser Window, select the assembly in the Assemblies folder and either:
• right-click on it and select Associate Graphics followed by the graphic drawing tool
that you want to use.
Prerequisites
• The assembly must exist with the associated comment graphic boundary. See “Creating
an Assembly” on page 429 and “Adding Associated Comment Graphics or Comment
Symbols to an Assembly” on page 433.
• The objects to be added to the assembly must have been added to the diagram within the
invisible boundary.
Procedure
In the Design Browser Window, select the assembly in the Assemblies folder or select the
visible graphical boundary in the diagram window and either:
Results
Any diagram objects wholly contained within the invisible boundary are added to the assembly
and appear under it in the Design Browser Window.
Related Topics
Assembly (Overview)
Creating an Assembly
Removing an Object from an Assembly
Renaming an Assembly
Deleting an Assembly
Adding Associated Comment Graphics or Comment Symbols to an Assembly
Removing Objects No Longer Within the Associated Comment Graphic Boundary from an
Assembly
Extending the Selection of Objects for an Assembly Comment Graphic or Symbol
Prerequisites
• The assembly must exist with the associated comment graphic boundary. See “Creating
an Assembly” on page 429 and “Adding Associated Comment Graphics or Comment
Symbols to an Assembly” on page 433.
• The objects to be removed from the assembly must not be wholly contained within the
invisible boundary.
Procedure
In the Design Browser Window, select the assembly in the Assemblies folder or select the
visible graphical boundary in the diagram window and either:
Results
Any diagram objects no longer wholly contained within the invisible boundary are removed
from the assembly and are no longer displayed under it in the Design Browser Window.
Related Topics
Assembly (Overview)
Creating an Assembly
Removing an Object from an Assembly
Renaming an Assembly
Deleting an Assembly
Adding Associated Comment Graphics or Comment Symbols to an Assembly
Adding Objects Within the Associated Comment Graphic Boundary to an Assembly
Extending the Selection of Objects for an Assembly Comment Graphic or Symbol
Renaming an Assembly
Deleting an Assembly
Adding Associated Comment Graphics or Comment Symbols to an Assembly
Adding Objects Within the Associated Comment Graphic Boundary to an Assembly
Removing Objects No Longer Within the Associated Comment Graphic Boundary from an
Assembly
You can specify the Harness attribute for an object either on the Attribute tab of the Edit
Properties facility (see “Editing an Object's Attributes” on page 423) or using the Edit
Harness Attribute facility as described in this topic.
There are cases were one object attribute may be in multiple harnesses. To eliminate the need to
run numerous synchronizations multiple harness attributes can be stored as comma (,) separated
values and may also be specified by entering a relevant Harness Group tag. These names are
created and maintained in Capital Project and can be edited by following the directions below.
Caution
Although it is possible to enter multiple harnesses as a comma-separated list, you should not
do so when working with Poke Home Wires. This is because a poke home wire only ever
belongs to one harness.
Procedure
1. Do one of the following:
• Right-click on the object either in the diagram window or in a browser tab at the
bottom left of the application window and select Edit Harness Attribute.
• Click the object, press Space Bar and enter Set Harness Attribute.
2. The Edit Harness Attribute dialog box is displayed. Enter the name of the harness or the
harness group that the object is to be synchronized to. If harness names or harness
groups have been created in Capital Project, you can select one from the drop-down list
in the Harness field.
For shared objects, if there are more cavities than shared pins, additional pins will be generated
and named according to the remaining unassociated cavities.
Procedure
1. In the Associate Pins with Cavities dialog, click on the cavity in the Cavities window
and click on the pin in the Pins window. Any pins that are not yet associated are
displayed in bold in the Pins window.
Note
You can associate all of the cavities automatically at once by clicking the Associate
All button. You can also disassociate a pin from a cavity by clicking on the pin in the
Pins window and clicking the Disassociate button. You can disassociate all pins by
clicking the Disassociate All button.
2. The associated pin is no longer displayed in bold. Click the OK button to exit the dialog.
Procedure
1. In the Edit Properties dialog, click the button.
Note
You cannot rename an object to have the same name of another object in the same
diagram. The application will automatically change the name to a unique name.
3. If displayed, check the Visible box if you want the specified name to be displayed with
the object in the diagram.
4. Set the following attributes for the text that is displayed on the diagram:
• Justification - where you want the text to be displayed in relation to the object.
• Clip
If selected, specifies that the text is clipped at the edge of its bounding box.
• Shrink to fit
If selected, specifies that the font of the text reduces as necessary so that the text fits
in its bounding box.
• Overflow
If selected, specifies that the text ignores the edge of its bounding box and flows out
of it.
• Wrap text
Specifies whether the text wraps onto multiple lines when it reaches the edge of the
text bounding box (selected) or whether the text ignores the bounding box and
continues on one line (unselected). When this is selected, if a word is too long to fit
on a single line, it is wrapped by character. Mandatory.
• Rotation - rotates the text to change the angle at which it is displayed. By default
this is 0 which displays the text running left to right following the horizontal axis:
. Enter a different value manually or select a value from the dropdown list, for
example, 270 .
• Auto flip - if selected, the text flips automatically so that it is never displayed upside
down when it is rotated or flipped. If not selected, a flip or rotation can result in the
text being displayed upside down.
• Color - the color of the text. To change the default color, select Over-ride from the
drop-down list on the left. This enables the box on the right that you can click to
display the Choose Text Color facility.
• Opacity - select one of the following from the drop-down list:
o Transparent - object lines are visible behind the text.
o Opaque - object lines are not visible behind the text.
• Font - select the font used for the text from the drop-down list.
• Height - the height of the text. You select the unit of measure from the drop-down
list.
5. Click the OK button to exit the facility.
You can use the Project Preferences facility in Capital Project or Capital Logic to control
whether cross-references are displayed for pin lists, conductors and pins. If you want to override
the project preferences related to the display of cross-reference text, you can edit the cross-
reference properties for an instance of a object. To do this, right-click on the instance of the
object in the diagram and select the Properties option from the pop-up menu. The graphical
properties for cross-references are on the Cross-references tab of the Edit Properties facility
that is displayed.
• Justification - where you want the cross-reference text to be displayed in relation to the
object.
• Clip
If selected, specifies that the text is clipped at the edge of its bounding box.
• Shrink to fit
If selected, specifies that the font of the text reduces as necessary so that the text fits in
its bounding box.
• Overflow
If selected, specifies that the text ignores the edge of its bounding box and flows out of
it.
• Wrap text
Specifies whether the text wraps onto multiple lines when it reaches the edge of the text
bounding box (selected) or whether the text ignores the bounding box and continues on
one line (unselected). When this is selected, if a word is too long to fit on a single line, it
is wrapped by character. Mandatory.
• Rotation - rotates the text to change the angle at which it is displayed. By default this is
0 which displays the text running left to right following the horizontal axis: . Enter
a different value manually or select a value from the dropdown list, for example, 270 .
• Auto flip - if selected, the text flips automatically so that it is never displayed upside
down when it is rotated or flipped. If not selected, a flip or rotation can result in the text
being displayed upside down.
• Color - the color of the text. To change the default color, select Over-ride from the
drop-down list on the left. This enables the box on the right that you can click to display
the Choose Text Color facility.
• Opacity - select one of the following from the drop-down list:
o Transparent - object lines are visible behind the text.
o Opaque - object lines are not visible behind the text.
• Font - select the font used for the text from the drop-down list.
• Height - the height of the text. You select the unit of measure from the drop-down list.
• Value - the cross-reference values. These cannot be edited.
• Limit references per line - the maximum number of cross-references that can be
displayed on one line when there are multiple cross-references for an object. To override
the value set either in the project preferences or in the applied style set. To set a limit,
you must check the Set Limit box (if you check the Override box and leave the Set
Limit box unchecked, the references per line will be unlimited for the object).
• Limit Lines per block - the maximum number of lines that can be in a block of cross-
references for the instance. If the number of cross-references for the instance is greater
than this value, the cross-references are displayed in multiple blocks. If you move a
cross-reference in a block to another location in the diagram, all of the cross-references
in that block move with it. Cross-references in other blocks for the instance do not move.
To override the value set in the project preferences or in the applied style set, you must
check the Override box. To set a limit, you must check the Set Limit box (if you check
the Override box and leave the Set Limit box unchecked, the references per line will be
unlimited for the object).
• Visible - check this box if you want cross-reference text for the instance to be displayed
on the diagram. Uncheck this box if you do not want cross-reference text to be
displayed.
• Position List
This tree menu shows every position configured against a modular connector. To assign
a sub-connector to a position, first select the position, then specify a name (if required)
and select a library part. Positions can be empty, filled or blocked, as indicated by the
following icons:
o - the position is empty. You can select this position and assign a sub-connector.
Related Topics
Adding a Modular Connector
Parameters at the top level can only be renamed (by changing the value in the Type field),
whereas sub-parameters can have their type and name changed.
The Parameters tab on the Edit Properties facility enables you to add or edit parameters for
connectors, cables, splices, blocks and devices in Capital Logic. It is not available for other
objects. See “Editing the Properties of Objects” on page 403 topic for more information on the
Edit Properties facility.
Note
Each object type has its own set of parameters. For example, the "bottom-broken" (broken
line glyph) is only available for shared components.
Related Topics
Editing Objects Parameters
Adding a Glyph to a Parameter
Editing Object Parameters
Removing a Parameter or Glyph from an Object
3. The item's current values will be displayed in the Type and Name boxes below the
browser tree. Edit a parameter's value or a glyph's value by clicking it in the tree
structure and selecting the required values from the drop-down lists.
4. Click the OK button to save the amended parameters and view the subsequent changes
to the object.
Related Topics
Editing Objects Parameters
Adding a Parameter to an Object
Adding a Glyph to a Parameter
Removing a Parameter or Glyph from an Object
You can manually freeze shared objects at any time. In Capital Project, you can also add a
Frozen Shared Objects behavior to a release level so that all shared objects in a design must be
frozen before you can move the design to that release level. The release level would generally
be of type Released. See the Capital Project help system topic for more information. After a
design has been moved to this release level, unfrozen shared objects cannot be added to it.
When you use the Edit Design facility to move a design to a release level with this behavior and
you click the OK button, the Freeze/Unfreeze Shared Objects facility is displayed
automatically.
Note
You cannot work with unfrozen shared objects in a Capital Logic design with a release level
that has the Frozen Shared Objects behavior. For example, promoting an unshared object
results in the freezing of that object.
If you have the necessary permission set in Capital User, you can unfreeze a shared object after
it has been frozen. The unfreezing of a shared object is an administrative operation and can be
done on any frozen shared objects. This might not be possible in Capital Logic if a design is
read-only (generally the case for a released design).
When a shared object is frozen, you can only view the information for it. You cannot edit it
apart from changing its appearance in a design. If the object has pins, you can also:
If your user account has the Frozen Shared Object Pin Attributes/Properties permission, you
can edit the attributes/properties for frozen shared object pins that have not been used on a
released design. If you do not have this permission, you cannot edit a frozen shared object pin
under any circumstances.
Any unrestricted or reserved pins that are not present on an instance of a shared object that you
demote will not be available on the object after you demote it.
Note
When you unshare an instance of a multicore or overbraid, all instances of it in the design
become unshared.
Procedure
1. Right-click on one instance of a shared object in the Design Browser or in the diagram
and select Unshare from the popup menu. Alternatively, click the object, press Space
Bar and enter Unshare.
2. The Name Local [object type] dialog is displayed. Specify a name (can be new or used
already) for the demoted object. If valid names have been specified in Capital Project,
you can click the ellipsis (...) button to open the Name Selection dialog where you can
select a valid name.
After specifying a name, click the OK button. You cannot undo this action.
3. If you have specified a name that is already used, a message asks whether you want to
use that name again or not.
After you demote the object, the Design Browser Window is updated accordingly.
Note
If the project preference Disallow pin duplication within a design is set, the
Unshare menu option will not be available for selection where the unsharing of the
object will create duplicate instances of pins. A tooltip message displays an explanation
of this on hovering over the Unshare menu item.
Depending on the object and any changes that have been made to the library part in Capital
Library, the Map Pins dialog may be displayed. This allows you to edit the associations
between the cavities on the library part and the pins on the object in the diagram. The Changes
window at the bottom of the dialog describes what will happen as a result of the new
associations.
If you attempt to perform an invalid action for the object (for example, removing a pin from a
shared object), a message is displayed in the Changes window and you cannot proceed.
Note
There is a design rule check called Invalid library pin mapping that checks for invalid
library pin mappings. See “Running Design Rule Checks” on page 65.
If the symbol associated to the library part has been modified, the symbol in the diagram is
updated or replaced when you update the library part information. When a symbol has been
replaced, the Map Pins Dialog (for Symbol) is displayed where you map the library part symbol
pins to the pins on the instance.
3. The filter symbol in the Scope section indicates whether a filter has been set or
not .
If a filter has been set and you do not want to use a filter, click the Clear Filter button.
If you want to set a filter for the search, click the Set Filter button to display the Find
and Replace Filters dialog. In that dialog, specify the following;
• Object Types - select the object types that you want to be included in the search.
You can clear the selection at any point by clicking the Clear Selection button.
Note
If you search for pins, the search results include backshell terminations, if you
search for devices, the search results also include ground devices.
• Revision - specify the design revision in which you want to search. You can check
the Latest Revision Only box to only ever search across the latest revision.
• Release Level - from the dropdown list, select either no release level (blank) or a
release level across which you want to search.
• Abstraction - from the dropdown list, select either no abstraction level (blank) or an
abstraction level across which you want to search.
• Domain - from the dropdown list, select either no domain (blank) or a domain
across which you want to search.
• Effectivity (only visible if effectivity functionality has been enabled for the project
in Capital Project) - specify the effectivity range within which you want to search.
Click the OK button to exit the Find and Replace Filters dialog.
4. In the Find section, you specify for what you are searching and potentially want to
replace.
The behavior of the search depends on whether you select Exact Match and/or Match
Case for the fields in this section:
• Neither are selected
The search finds appropriate objects/attributes/values that contain the string entered
in the box, regardless of whether any characters are uppercase or lowercase.
For example, you search for an Attribute/Property of model.
The search will find any object with an attribute or property whose name contains
the string model. As this is not case-sensitive, it will find the string regardless of
whether any characters are uppercase of lowercase in it (for example, Analysis
Model would be found).
• Exact Match IS NOT selected and Match Case IS selected
The search finds appropriate objects/attributes/values that contain the string entered
in the box with the same uppercase and lowercase characters.
For example, you search for an Attribute/Property of model.
The search will find any object with an attribute or property whose name contains
the string model. As this is case-sensitive, it will not find the string if any of the
characters are in a different case (for example, Analysis Model would not be found
but Vehicle model would be found).
• Exact Match IS selected and Match Case IS NOT selected
The search finds appropriate objects/attributes/values that match the exact string
entered in the box, regardless of whether any characters are uppercase or lowercase.
For example, you search for an Attribute/Property of model.
The search will find any object with an attribute or property whose name exactly
matches the string model. As this is not case-sensitive, it will find the string
regardless of whether any characters are uppercase of lowercase in it (for example,
Model and model would be found but Analysis Model would not be found).
• Exact Match and Match Case are both selected
The search finds appropriate objects/attributes/values that match the exact string
entered in the box with the same uppercase and lowercase characters.
For example, you search for an Attribute/Property of model.
The search will find any object with an attribute or property whose name exactly
matches the string model. As this is case-sensitive, it will not find the string if any of
the characters are in a different case (for example, model would be found but Model
and Analysis Model would not be found).
You can specify the following:
Note
In the following fields, if you want to search for a special character such as $, ensure
that you type a delimiter (\) before it. For example, \$.
• Object Name - if you want to limit the search to objects with particular names, you
can enter a full name or part of a name using wildcards.
• Attribute/Property - specify the attribute or property name. You can either enter
the name manually or select it from the drop-down list in the field.
• Matches - specify the value of the attribute or property.
If Exact Match is selected, every value string found will be fully replaced by the
content in the replace section.
If Exact Match is not selected, each and every occurrence of the string entered will
be replaced by the content in the replace section. For example, find “AB” and
replace with “C”, results in the renaming of Property=ABDAB with
Property=CDC.
If nothing is specified here, the entire value strings of the attribute/property
occurrences found will be replaced by the content in the replace section. For
example, find “AB“ and replace with “C”, results in the renaming of
Property=ABDAB with Property=C.
• Symbol - if you want to search on objects that use a particular symbol only, you can
click the ellipsis (...) button to display the Symbol Selection dialog that enables you
to browse the available symbol libraries to select the symbol. If you select a symbol,
it is displayed in a preview window.
You can click the Clear button to clear the symbol selection.
• Update Symbol Only - select this if you want to replace only the symbols used for
the found objects and not their attributes or properties. You cannot replace comment
symbols or symbols associated to library parts.
• Preserve Pin Positions
Select this if you want the pins on the symbol instances to remain where they are in
the diagram already.
• Remove Properties not on Symbol
Select this if you want to remove any properties from the symbol instances that are
not on the symbol in the symbol library.
• Copy Attribute/Property Values from Symbol
Select this if you want to copy any properties and attributes that are on the symbol in
the symbol library to the symbol instances.
• Preserve Attribute Text
The attribute visibility settings on a diagram instance of a symbol may be different to
the attribute visibility settings on that symbol in the symbol library. If this is
selected, the attribute visibility settings on the symbol instance in the diagram are
retained. If this is not selected, the attribute visibility settings on the diagram
instance are overwritten by those on the symbol in the library.
• Preserve Diagram Pin Name
In a diagram, you can rename a pin name on a symbol instance. If this is selected, the
pin names in the diagram are retained. If this is not selected, the pin names in the
diagram are replaced by the pin names from the symbol in the symbol library.
You can display the name more than once along the course of a conductor.
Procedure
1. Ensure that the name of the conductor has been set as visible in the conductor's general
properties.
2. Select one or more segments of the conductor next to which you want to display the
conductor name and right-click one of the selected segments. Select the Add Name
Text menu option from the pop-up menu. Alternatively, select one or more segments of
the conductor, press Space Bar and enter Name Text.
3. The name of the conductor is displayed next to each selected segment and follows the
property style preferences that have been specified in Capital Project.
Note
All shared devices have fixed names, regardless of whether they were named
manually or automatically.
If the name for an object has been modified from the default in the Name field of the
Edit Properties dialog, it is set as fixed by default.
• Generated names - these are based on the naming compositions set up in the advanced
naming functionality in Capital Project. Each name composition has a condition that
determines the objects for which can be used to generated names. When a name is being
generated, each name composition is tested against the named object in the order the
compositions are defined. The first name composition to match the object is used to
generate a name.
Different types of condition entries are used to test the named object. Property and attribute
value conditions can be used to match their value to a fixed string. For example, the condition
"color"="Blue" matches all objects with the property set to "Blue".
It may be the case that some objects will not be renamed when you apply advanced naming to
them because they do not match any conditions for the naming compositions.
Design properties can also be included in naming compositions so the values that you have
specified for design properties influence the names that are generated. See “Editing the
Information for a Design” on page 48 for more information about specifying design properties.
Note
Device connectors whose names are constrained by a footprint or library part cannot be
renamed using advanced naming.
• Use the Generate Advanced Names dialog to generate them for specific selected
objects. See “To generate names for selected objects using advanced naming” below.
• Use the Generate Advanced Names dialog to generate them for all objects in a design
or a diagram. See “To generate a batch of names using advanced naming” below.
Note
If you want to replace names on shared objects, you must select Fixed Names
because shared object names are considered as fixed by the system.
Note
If you check both the Replace Object Indices box and the Reset Counters box,
the indices on the objects will start from 1.
If the Reset Counters box is checked and the Replace Object Indices box is not
checked, the indices on the selected objects do not change but the counter will start
from 1 again when you create new objects. For example: If you have three objects
with the indices 4, 5 and 6, those indices will remain 4, 5 and 6. However, when you
create a new object that uses that counter, it will have the index value 1. The next
new object created after that will have the index value 2, and so on.
4. Click the OK button to generate new names for the selected objects.
To generate a batch of names using advanced naming
1. With the appropriate project open, press Space Bar and enter Batch Update.
2. The Generate Names facility is displayed. In the browser tree in the Select Scope
window, select the design or diagram within which you want to generate names.
The objects in these containers already have names and you must select which types of
names you want to replace with newly generated names. Check the box next to each
type of name that you want to replace (Default Names, Generated Names and Fixed
Names).
Note
If you want to replace names on shared objects, you must select Fixed Names
because shared object names are considered as fixed by the system.
Note
If you check both the Replace Object Indices box and the Reset Counters box,
the indices on the objects will start from 1.
If the Reset Counters box is checked and the Replace Object Indices box is not
checked, the indices on the selected objects do not change but the counter will start
from 1 again when you create new objects. For example: If you have three objects
with the indices 4, 5 and 6, those indices will remain 4, 5 and 6. However, when you
create a new object that uses that counter, it will have the index value 1. The next
new object created after that will have the index value 2, and so on.
4. Click the OK button to generate new names for the objects in the container that you
have selected.
Objects
• The following fields and objects are available:
o Search By (Internal/Customer/Supplier)
Use the dropdown list to specify whether you want to search for an internal,
customer or supplier part number and enter a partial or full part number in the field
next to that dropdown list. When you start to type a part number, a dropdown list
suggests full part numbers that you may want to select. Mandatory.
As you type a part number, a dropdown list suggests part numbers that match the
entered string. If ... is displayed at the bottom of the list, this indicates that more
matching part numbers are available. When the entry ... is selected, a component
search with the currently entered part number string combined with other defined
search criteria is performed.
You can use the following characters to restrict the part numbers returned in the
search results:
• * (star symbol)
Represents any number of characters when used in a string. For example,
entering C-00*E represents values that start C-00, followed at any position by an
E. Example results are C-002-BLUE, C-003-GREEN, C-004-GREY, C-005-
RED.
• ? (question mark character)
Represents any single character when used in a string. For example, entering
A??X (an A, two question marks and an X) into a field represents only 4-
character values that have an A as their first character and an X as their fourth
character. Example results are ABCX, A11X, ABCXAB.
• Single letter
Entering a single letter into the field, returns only part numbers that begin with
that letter. For example, typing the character C into a box will list only that box's
records that begin with C - regardless of their length.
o Search parts using criteria specified
you select the details that you want to apply. When using the Parts tab, you can
right-click the part and select Select Details.
When using the Parts tab, you can right-click on part numbers for certain
component types and add a component to a harness with that part number. See “Parts
Browser” on page 482.
Insert
Click this to assign the part number that is selected in the Parts Table to the object
that you are editing.
Details Dialog
To access: Select a component in the Part Selection Dialog and clicking View part details ( ).
Used to display the component details tabs for a component.
Objects
See Component Details in the Capital Library User Guide for more information about the
fields on the tabs.
Procedure
1. Press Space Bar and enter Batch Update Library Parts; the Confirm Batch Update Of
Library Parts dialog is displayed.
2. If given the choice, select whether you want to update library parts in the currently
active design or in a build list to which that design belongs and click Update; a status
bar indicates that the update is taking place.
3. Once the update is complete:
• The Output Window displays information regarding which objects have been
updated on a Update Library Parts tab. This tab also displays messages regarding
any objects that could not be updated. You can click on an object’s name to jump to
that object in the diagram window.
• If an object has a value specified for its Part Number attribute but does not have a
library part associated, this action creates an association to a library part for that
object.
• If an object already has an associated library part, the associated part is not changed
but the library part information is updated for that object where appropriate.
In Capital Logic, you can use constraints to set properties and attributes on objects and to
exclude specific nets from conversion to wires.
Rules and Constraints Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
Defining a Constraint for a Design. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
Defining Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
Referencing another Rule in a Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
Adding Rules to a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
Using a Constraint to Set Properties and Attributes on Objects . . . . . . . . . . . . . . . . . . 475
If you are using Capital Topology, see “Constraints (Capital Topology)” on page 629 for details
of the constraints that are available. Otherwise, use the information in this chapter on how to use
rules and constraints in general.
You use constraint templates in Capital Logic and Capital Integrator to define a constraint.
You can write your own custom constraints in Java and load them into Capital Integrator or
Capital Logic. For more information about writing and loading custom constraints, see the
PluginDevelopment.pdf document that is located in the doc\plugin folder of your Capital
installation. Once custom constraints are loaded, you use them in the same way as standard
constraints. An object can have both standard and custom constraints defined for it.
The design rule check Missing Custom Constraint Check can be run to report on any custom
constraints that have been defined for an object but are not loaded any longer in Capital
Integrator or Capital Logic. See “Running Design Rule Checks” on page 65 for more
information about running design rule checks.
Rules
In Capital Logic, a rule is a group of constraints that can be applied to a whole design. You can
define rules from within Capital Logic or from within Capital Project. In Capital Project, you
can define rules either at a project level or you can define rule libraries at a system level. A rule
library can be added to a project. See the Capital Project help system for more information
about defining rule libraries.
Related Topics
Defining Rules
Adding Rules to a Design
Procedure
1. Right-click over the appropriate design in the Project Browser Window and select the
Edit option.
The Edit Design Dialog is displayed.
2. Click Properties.
The Edit Design Properties Dialog is displayed.
3. Click the Rules tab.
4. Click Add Constraint and select the type of constraint that you want to define. Click
the OK button to add it to the Rules tab. Click on the constraint and click on the green
and red text in the constraint to edit it.
You can select whether you want to use the standard version or a custom version of this
constraint by clicking the icon at the start of the constraint. This displays a drop down
list containing the standard version of this constraint and any custom versions of this
constraint. Select the required version from the list and click the OK button. If the icon
is white, it indicates a standard constraint. A yellow icon indicates a custom constraint.
An icon indicates a rule. See “Adding Rules to a Design” on page 474 for more
information about rules.
The following text may be displayed as editable (red or green) in a constraint:
• Value
This is used typically when you want to use rules to add properties and attributes to
conductors, splices and multicores. Select one of the following:
o Literal
This means it is a literal value. Enter the value string in the box. You can use
wildcards in this string. Click the OK button to exit the dialog.
o Attribute
This means the value is derived from the value of an attribute on the functional
signal or multicore. Select the attribute from the drop-down list in the box. Click
the OK button to exit the dialog.
In the defined constraint, ValueOf is placed in front of the bracketed attribute
name. For example,
o Property
This means the value is derived from the value of a property on the functional
signal or multicore. Enter the property name in the box. Click the OK button to
exit the dialog.
• Object Type
Select an object type from the list that is displayed when you click on this.
• AttrOrProp
Select either Attribute or Property. For an attribute, select the attribute name from
the drop-down list. For a property, enter the property name in the box or select from
the list of pre-defined property names in the drop-down list. Click the OK button to
exit the dialog.
If a constraint contains a clause for matching it to particular objects (for example, Object
Name = PropValue), you can also edit the match operator that is = by default. The
available operators are:
= Equal to
!= Not equal to
< Less than
> Greater than
<= Less than or equal to
>= Greater than or equal to
For example:
Only route signals with property matching Object Name != Signal01
In this example, only signals that do not have a value of Signal01 for the Object Name
property will be routed.
Do place devices with property matching Rating >= 7.5 here
In this example, only devices that have a value greater than or equal to 7.5 for the
Rating property will be placed.
When specifying a property value string in a constraint, you can use wildcards.
For example:
.* is all possible strings
si.* is any string starting with si.
Related Topics
Rules and Constraints
Defining Rules
Adding Rules to a Design
Defining Rules
In Capital Logic, rules are groups of associated constraints that can be applied to a whole
design. A rule can contain (reference) other rules and therefore include their constraints.
Procedure
1. Open the project for which you want to define rules, press Space Bar and enter Rules. If
rules or rule libraries have been defined before, they are displayed in the Rules window.
2. Click the New button, enter a new rule name and click the OK button.
3. Click the Add Constraint button and select a constraint template from the Constraint
Selection dialog. Click the OK button to exit the Constraint Selection dialog.
4. The constraint is displayed in the Rules Contents window. See “Rules and Constraints”
on page 469 for information about editing constraints.
You can select whether you want to use the standard version or a custom version of this
constraint by clicking the icon at the start of the constraint. This displays a drop down
list containing the standard version of this constraint and any custom versions of this
constraint. Select the required version from the list and click the OK button. If the icon
is white, it indicates a standard constraint. A yellow icon indicates a custom constraint.
5. Click the OK button when you have added and edited all of the constraints that you want
the rule to have.
Related Topics
Referencing another Rule in a Rule
custom constraint. See “Defining a Constraint for a Design” on page 471 for more
information about constraints. You can click on the rule to display the constraints from it
in a read-only window.
Related Topics
Rules and Constraints
Defining Rules
Defining a Constraint for a Design
Extending a Selection
When you select particular objects in the Design Browser Window or diagram window, you can
extend the selection to include associated objects.
You can use this function on the following objects:
Note
If a window is not large enough for everything to be visible, scroll bars are added to it
automatically and you can move these to display different areas of the window.
Ribbon
The ribbon at the top of an application contains tabs with menu items and buttons for various
actions.
You can use a Ribbon Helper to find a particular action.
See Searching for an Action on the Ribbon in the Capital Design Tools - Common Functions
User Guide.
To expand all sub-folders under a folder, right-click on the folder and select the Expand
Completely option from the pop-up menu.
The project folder contains folders for designs. Design folders contain the design revision and
diagrams for the design
revision.
You can collapse a section of the browser tree by clicking a downward-pointing flipper .
Alternatively, you can double-click the name of the project or the name of a design.
To display an open project in the Project Browser Window and open a Diagram Window
1. Click the Open Project Selector that is located at the top right of the Project Browser
Window.
2. A drop-down list displays the names of open projects. Click the name of the project that
you want to display in the Diagram Window.
3. The existing designs and diagrams for the project are displayed in the Project Browser
Window and any open diagrams for the project are displayed in Diagram Windows on
the right-hand side of the application window.
To filter the listed designs
Use the following controls:
In the Enter Filter String ( ) field, enter a series of characters, for example, Engine. A
filter is applied to the Project browser tree so that only designs with names containing
that series of characters are listed.
Click the Clear Filter String icon ( ) to clear the filter and view all designs in the
project.
• Design Filter ( )
Click the dropdown list to filter the designs displayed in the Project browser tree
window to those of a particular type, all designs in the project or all designs in the
currently active build list.
o Show All Designs ( )
To close a project
Click the Close Project button at the top left of the Project Browser Window.
Note
You can hide the various browser windows by selecting the View menu option and
unchecking the Browser Area box. To display the browser windows again, select the View
menu option and check the Browse Window box.
• Browser tree
Lists the objects used in the active diagram or in the design. Also lists any design wide
object that is not currently used in the design in Unplaced folders.
If an object has child objects, such as pins, these are displayed as sub-nodes of that
object. You can expand a folder or node by clicking the + symbol. To collapse a folder
or node, click the - symbol.
When you click on an object in the browser tree, it is highlighted in the currently active
diagram window. If you click a pin, a circle is displayed around it in the diagram
window.
If you move your cursor over an instance of a design wide object, a tooltip indicates the
diagram where that instance is located. Double-click an instance to jump to it in the
diagram window.
• Enter Filter String ( )
Enter a series of characters. A filter is applied to the Design Browser Window so that
only objects with names containing that series of characters are listed. If you want to use
a regular expression character, such as a bracket, in the filter, you must prefix it with \.
For example, \(P.
• Showing all objects in the design ( )/ Only showing objects in the active diagram
( )
Controls what is displayed in the browser tree. Click this to switch between showing all
objects in the design and only objects used in the active diagram.
To launch Capital Symbol, right-click on a symbol library name or a symbol name and select
Edit Symbol. Capital Symbol is launched in a separate window with the appropriate library and
symbol open.
Note
You can hide the various browser windows by selecting the View menu option and un-
checking the Browser Area box. To display the browser windows again, select the View
menu option and check the Browse Window box.
To expand all sub-folders under a folder, right-click on the folder and select the Expand
Completely option from the pop-up menu.
Related Topics
Adding a Symbol to a Diagram
Parts Browser
The Parts tab, located on the lower-left side of the application window, allows you to use Part
Selection dialog functionality to search for library parts and view their details. This tab can be
dragged from its location to display it as a separate floating dialog. Close the dialog to return it
to the original tab location.
In addition to that functionality, you can right-click on part numbers for certain component
types and add a component to a harness with that part number. This action creates a component
in the same way as using a menu option but Library Part fields will be pre-populated. You can
do this for the following components:
• Connectors
• Devices
• Wires
• Nets
• Shields
• Multicores
• Splices
You can hide the various browser windows by selecting the View menu option and un-checking
the Browser Area box. To display the browser windows again, select the View menu option
and check the Browse Window box.
When you insert a shared conductor (that was created in Capital Project) into a design, you
will be asked (immediately), if you wish to save the design. If you do not choose save the
design, the conductor will not be inserted. You can choose to have the design automatically save
after the insertion of shared conductors, by checking the Don't show me this message again
box in the Confirm Save Design dialog box.
The toolbar in the Shared Objects Browser Window contains the following:
• Edit Shared Object - allows you to edit a shared object. See “Editing Shared
Devices and Shared Connectors” on page 191.
• Create Revision - allows you to create a revision of a shared object. See “Creating a
New Revision of a Shared Object” on page 197.
• Freeze/Unfreeze Shared Objects - allows you to freeze and unfreeze shared objects.
See “Freezing and Unfreezing Shared Objects” on page 447.
• Delete Unused Shared Objects - allows you to delete multiple unused shared
objects in a project. See “Deleting Multiple Unused Shared Objects” on page 210.
• Delete Shared Object - allows you to delete a single unused shared object from a
project. See “Deleting a Single Unused Shared Object” on page 211.
• Refresh Shared Device, Connectors, and Conductors - allows you to refresh the
shared objects displayed in the Shared Objects Browser Window so that changes made
by other users to the available shared objects can be seen.
The tree contains the following nodes:
You can right-click on a shared object revision and select Swap Out Revision to swap instances
of that shared object revision for another compatible revision in designs. See “Swapping Out
Shared Objects for a Compatible Revision” on page 198.
To expand all sub-folders under a folder, right-click on the folder and select the Expand All
option from the pop-up menu.
Once ICD information is received in Capital Logic it can be utilized to quickly and accurately
place devices into designs, generate connectivity using auto-route functionality and be easily
verified using design rule checks that validate the connectivity and device information against
the original ICD definition. See “Running Design Rule Checks” on page 65. Any subsequent
updates to an ICD can be dynamically synchronized using a context menu command. ICD
details and descriptions can be viewed from within Capital Logic in a popup browser window,
again by utilizing a context menu command.
Furthermore visual feedback in the form of changed icons is provided in the design browser
immediately indicating if any ICD shares connectivity with other ICDs in the active design or
build list.
Note
Capital Devices requires a valid license in order to access its functionality. Contact Mentor
Graphics Customer Support to obtain this license.
There are also a number of settings that must be enabled in the Capital configuration files before
using ICDs and accessing the ICD tab. See the Capital Configuration Files User Guide for
further information on these settings.
On accessing the ICD tab four folders are available containing device information. These are:
• Unplaced
Lists any ICDs that are allocated to the current, active design, but that have not yet been
placed on the diagram.
• Placed
When ICDs are added to the diagram they are moved into the Placed folder.
• Placed in other designs
Lists ICDs that have been placed in other designs in the build list and that share
connectivity.
• Unallocated
Lists devices that have been made applicable for the current project but not (as yet) to an
active design.
Note
The conductor and footprint behavior is determined by the design abstraction.
- If the abstraction is set to “Auto create harness connectors” then wires and footprints
are used.
- If “Auto create harness connectors” is not set then Nets are used and no footprints
added.
See the Edit Design Abstractions in the Capital Project User Guide for further
information.
Procedure
1. Select a device from the Unallocated/Unplaced folder and place it on to the diagram.
2. The ICD icons in the design browser change ( )to denote any ICDs that share
connectivity with ICDs already placed on designs in the same build list. These ICDs are
listed in the Placed in other designs folder and in other designs of the build list.
3. Select the ICD containing common connectivity in the relevant design, right-click on it
and select Share from the context menu. Its icon changes to indicate it is now shared
( ). For further information see “Adding a Shared Device, Plug, Receptacle, Ring
Terminal, or Inline Connector to a Diagram” on page 187.
4. Once you place and share an ICD in the active design its connectivity is automatically
displayed. See “Placing ICDs in Capital Logic” on page 486 for further information.
information on these settings see icdviewer in the Capital Configuration Files Reference
Guide.
Procedure
1. Select the ICD which you wish to interrogate from the ICD tab in the design browser.
2. Right-click on the ICD and select View ICD Details from the context menu.
Results
A popup browser window opens allowing you to view the ICD information and description as
defined in Capital Devices.
Diagram Window
Diagram Windows are displayed on the right-hand side of the Application Window. This is
where diagrams are edited.
More than one Diagram Window can be open in the Application Window.
When no diagram is open, a launch pane is visible. See Launch Pane in the Capital Design
Tools - Common Functions User Guide.
An active diagram has a purple title bar and an inactive diagram has a gray title bar. The title bar
displays the name of the diagram and the design to which it belongs. The title bar also has the
following buttons:
Minimize
Minimizes the size of the Diagram Window so that it is displayed as a small gray bar:
Note
To restore the Diagram Window to the size it was before, double-click the left end of the
gray bar or click the name of the design and diagram on the gray bar.
Maximize
Maximizes the size of the Diagram Window so that it fills all available space in the Application
Window.
When a Diagram Window is maximized, the Maximize button becomes a Restore button.
Click the Restore button to restore the Diagram Window to the size it was before.
Close
Note
If a Diagram Window is not large enough for everything to be visible, scroll bars are added
to it automatically and you can move these to display different areas of the Diagram
Window.
Alternatively, you can change the size of a Diagram Window by holding down the right mouse
button over an edge of the Diagram Window (the cursor changes to a two-way arrow ) and
dragging the edge.
Output Window
The Output Window is located at the bottom of the Capital Logic window. It displays the tool
output during operation, and includes various tabs.
• Capital Logic shows the output of the commands.
• Logic shows the status of any logic calculations performed in the diagrams.
• Update displays the status of diagram windows.
Each pane also has a pop-up menu, accessible with a right mouse button click, that contains text
manipulation commands (Select All, Copy, and Clear).
Status Bar
The Status Bar is located at the bottom of the Application Window and contains various
elements.
• Auto-route: ON/OFF Indicator
When running, the toggle button changes to a square (stop icon) that you can click to
stop the checks running:
The symbol next to the toggle button (start / stop icon) indicates whether the checks
have currently found failures or not.
• Filtering Icon
Indicates whether any filtering is applied to the open diagram. You can click this icon to
open the Design Filter dialog that allows you to apply filtering. See “Filtering the
Objects Displayed in a Diagram” on page 120.
• Selected object counter
Displays the number of objects (including text) that are selected on a diagram.
• Cursor co-ordinate box
Displays the co-ordinates of the position of the mouse cursor in a Diagram Window.
• Active Language
Indicates which diagram translation language is active. By default, this is EN.
Note
You can hide the Status Bar by selecting the View menu option and unchecking the
Status Bar box. To display the Status Bar again, select the View menu option and
check the Status Bar box.
Bridge Filter
When bridging out data from Capital Logic, filtering may be applied to selectively output data.
This is useful when your design contains several configurations and/or harnesses and you are
attempting to bridge out to a single MCAD harness.
To access the Bridge Filter dialog, select Filter from the Bridge menu. This dialog contains
two list boxes:
• Configuration Filter
This box displays a list of the available configurations within the design. These can be
selected individually by clicking on the name of the configuration. Use the SHIFT and
CTRL keys to make multiple selections within the list.
• Harness Filter
This box displays a list of the available harnesses within the design. These can be
selected individually by clicking on the name of the harness. Use the SHIFT and CTRL
keys to make multiple selections within the list.
For each list box you can also use the Select All and Clear All buttons to select (or de-select) all
the items in the list. Once the desired items have been selected, press OK to return to the main
Capital Logic window.
Once filter selections have been made, subsequent Bridge Out operations will export data only
for those items. If no filters are specified, the whole connectivity of the design is exported.
A hand under an object icon indicates that the object is shared. If a blue snowflake is
displayed at the top of the icon, it indicates that the shared object is frozen.
An orange circle on an object icon indicates that it has an Analysis model attached to it.
An orange tick on an object indicates that is has a library part assigned to it.
When option descriptions are displayed, they are followed by the option name in brackets.
For example:
V6 3.0L Engine [ENG_3.0] where V6 3.0L Engine is the option description and ENG_3.0 is
the option name.
If option descriptions have been selected but no description has been given for an option, the
option name is displayed in brackets, such as [ENG_3.0].
Note
Options displayed in the diagram window and options displayed in option expressions will
be displayed as the option name regardless of the setting.
Hot Keys
Hot Keys permit the execution of commands by pressing a single key on your keyboard. For
reference, the equivalent TransDesign commands are also listed for the Capital Logic
commands. The Hot Keys are not case sensitive.
The Capital AutoView Assist for Logic (CAVAL) facility allows a user to create functional or
wiring diagrams based on an existing set of connectivity using specified constraints, instead of
manually placing components.
Overview of Capital AutoView Assist for Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
Generating Diagrams for a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
Generating Filtered Diagrams for a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
Importing a Project and Generating Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
Generating a Design and Diagrams for Filtered Connectivity from Multiple Designs. 503
Specifying Layout Styling when Generating Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . 504
Capital AutoView Assist for Logic Dialog Boxes and Field References . . . . . . . . . . . . . 515
AutoView Diagram Generator - Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
AutoView Diagram Generator Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
New Generated Diagrams - Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
New Generated Diagrams Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
New Diagram - Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
New Diagram Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
Edit Diagram - Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
Edit Diagram Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
Selection Preview - Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
Selection Preview Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
Import Project and Generate Diagrams - Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
Import Project and Generate Diagrams Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
AutoView Style Editor Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
AutoView: Query and Generate Design Dialog - Help . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
AutoView: Query and Generate Design Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
Parent Folder Selection Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Parent Folder Selection Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
a design (for which diagrams have to be generated) and the template are revisions of the same
design, connectivity objects (devices, conductors, and so on) are matched by revisions.
Otherwise, connectivity objects are matched by name.
• As a single action directly from Capital Logic or Capital Design to import a project
XML file and bulk generate a diagram for each design. In this case, the user can select
the border and style preferences to be applied to all diagrams to be generated (one per
design). If a design has a diagram already, no new diagram will be generated. See
“Importing a Project and Generating Diagrams” on page 500 for more information.
• Directly against an existing Capital Logic design, regardless of whether diagrams exist
already or not. In this case, the user can select the layout and style preferences to be
applied to all diagrams to be generated. See “Generating Filtered Diagrams for a
Design” on page 499 for more information.
• For a specific Capital Logic design, regardless of whether diagrams exist already or not.
In this case, a filtering option is available to interactively paginate a set of design
connectivity into multiple diagrams and apply a project based style preference set
against each. See “Generating Diagrams for a Project” on page 497 for more
information.
• For a project or build list so that it can generate a single design and its diagrams for
filtered logical connectivity from multiple Capital Logic, Capital Integrator or Capital
HarnessXC designs in a project. See “Generating a Design and Diagrams for Filtered
Connectivity from Multiple Designs” on page 503.
When a device has a tree type connection (logical or physical) to another device that has
no other connectivity relationships, the path between the devices is the shortest path
available that minimizes the crossing over of conductors, maximizes the balancing of
white space, and reduces net jogs. Additionally, two new layout style settings optimize
the way that the tree connectivity is displayed.
When complex loops occur within the design connectivity, Capital AutoView Assist for
Logic will ensure: 1) minimum conductor cross over, 2) no device collisions, 3) even
device distribution in both the horizontal and vertical planes.
Caution
On the Component Styling tab, you can edit the default style set or selected style set
but note that the changes will apply to any designs using the style set and will be
visible if this style set is viewed in Capital Project.
See the Diagram Styling User Guide for more information about style sets and how to
edit them.
5. On the Layout Styling tab, specify the preferences that you want to use for the layout of
the diagrams. See “Specifying Layout Styling when Generating Diagrams” on page 504
for more information about layout styling preferences.
6. If you want to use template diagrams from another project for the generation of
diagrams, click the Prototype tab. Any connectivity in the current project that matches
connectivity in the selected template designs will take the layout from the template. Any
unmatched connectivity in the current project will be laid out automatically.
Note
If a path in the current project is more complex than the reference path in a template
path, Capital AutoView Assist for Logic uses its own improved algorithm to
determine the layout of the path.
Note
If a design (for which diagrams have to be generated) and the template are
revisions of the same design, connectivity objects (devices, conductors, and
so on) are matched by revisions. Otherwise, connectivity objects are matched by
name. This matching rule applies in all cases. For example, even if you select to
match designs by name, the connectivity objects are matched by revisions if the
design and its template are revisions of the same design.
• From Project - select the project from which the template designs should be
selected.
7. Click the OK button to generate the diagrams.
Note
If a design has a diagram, it is ignored by Capital AutoView Assist for Logic and a
message is displayed on the Import/Generate tab of the Output Window at the
bottom of the application.
Related Topics
Overview of Capital AutoView Assist for Logic
Caution
On the New Generated Diagrams - Component Styling Tab, you can edit the default
style set or selected style set but note that the changes will apply to any designs
using the style set and will be visible if this style set is viewed in Capital Project.
See the Diagram Styling User Guide for more information about style sets and how to
edit them.
4. On the New Generated Diagrams - Layout Styling Tab, specify the preferences that you
want to use for the layout of the diagrams. See “Specifying Layout Styling when
Generating Diagrams” on page 504 for more information about layout styling
preferences.
5. On the New Generated Diagrams - Prototype Tab, specify whether you want to use an
existing design as a template for the generated diagram. Any connectivity in the current
design that matches connectivity in the selected template design will take the layout
from the template. Any unmatched connectivity in the current design will be laid out
automatically.
Note
If a path in the current project is more complex than the reference path in a template
path, Capital AutoView Assist for Logic uses its own improved algorithm to
determine the layout of the path.
In the From Project window, select the project that contains the template diagram. In
the Select Design Prototype window, select the template diagram from the browser
tree.
Note
If a design (for which diagrams have to be generated) and the template are revisions
of the same design, connectivity objects (devices, conductors, and so on) are
matched by revisions. Otherwise, connectivity objects are matched by name.
2. The Import Project & Generate Diagrams dialog is displayed. Specify the following:
• Look In - select a folder location from the drop-down list and browse to the project
file that you want to import in the window below the Look In field.
• Border Selection - select [No Border] if you do not want the diagrams in the project
to have a border. If you do want to use a border on the diagrams, select the border
name in the browser tree.
• Horizontal - specify whether you want the border to align with the left, right or
center of the connectivity on the diagram.
• Vertical - specify whether you want the border to align with the top, bottom or
center of the connectivity on the diagram.
• Regenerate Existing Diagrams - check this box to regenerate any existing
diagrams based on the currently specified settings.
• Run Segment Overlay DRC - check this box if you want to run a design rule check
that checks for overlaying conductor segments. See “Running Design Rule Checks”
on page 65 for more information about design rule check functionality.
• Show AutoView Style Editor - Check this box if you want to open a style editor
when you import the project. The style editor enables you to specify component
styling, diagram layout styling and the selection of template (prototype) diagrams.
• File Name - if you have not browsed to the file in the window above, enter the full
path to the project XML file that you want to import.
• Files of Type - from the drop-down list, select the type of files for which you want
to browse.
3. Click the OK button.
4. A dialog indicates the progress of the process. If you did not check the Show AutoView
Style Editor box, skip to step 8.
If you did check the Show AutoView Style Editor box, the style editor is displayed. On
the Component Styling tab, you specify the styling that you want to use for objects on
the generated diagrams. By default, Capital AutoView Assist for Logic uses the Default
style set for Capital Logic.
If you have a license to use Capital Styling, you can use the Style Set dropdown list at
the top of the tab to select a different style set if they are available. You can click the
ellipsis (...) to open the Style Sets Dialog where you can edit an existing style set or
create a new style set.
Caution
On the Component Styling tab, you can edit the default style set or selected style set
but note that the changes will apply to any designs using the style set and will be
visible if this style set is viewed in Capital Project.
See the Diagram Styling User Guide for more information about style sets and how to
edit them.
5. On the Layout Styling tab, specify the preferences that you want to use for the layout of
the diagrams. See “Specifying Layout Styling when Generating Diagrams” on page 504
for more information about layout styling preferences.
6. If you want to use template diagrams for the generation of diagrams, click the Prototype
tab. Any connectivity in the current project that matches connectivity in the selected
template designs will take the layout from the template. Any unmatched connectivity in
the current project will be laid out automatically.
Note
If a path in the current project is more complex than the reference path in a template
path, Capital AutoView Assist for Logic uses its own improved algorithm to
determine the layout of the path.
Note
If a design (for which diagrams have to be generated) and the template are
revisions of the same design, connectivity objects (devices, conductors, and
so on) are matched by revisions. Otherwise, connectivity objects are matched by
name. This matching rule applies in all cases. For example, even if you select to
match designs by name, the connectivity objects are matched by revisions if the
design and its template are revisions of the same design.
• From Project - select the project from which the template designs should be
selected.
7. Click the OK button to generate the diagrams.
8. When the project is imported, existing diagrams are imported with it and diagrams are
generated for connectivity that does not have diagrams.
Related Topics
Overview of Capital AutoView Assist for Logic
If you have a license to use Capital Styling, you can use the Style Set dropdown list at
the top of the tab to select a different style set if they are available. You can click the
ellipsis (...) to open the Style Sets Dialog where you can edit an existing style set or
create a new style set.
Caution
On the Component Styling tab, you can edit the default style set or selected style set
but note that the changes will apply to any designs using the style set and will be
visible if this style set is viewed in Capital Project.
See the Diagram Styling User Guide for more information about style sets and how to
edit them.
7. On the Layout Styling tab, specify the preferences that you want to use for the layout of
the diagrams. See “Specifying Layout Styling when Generating Diagrams” on page 504
for more information about layout styling preferences.
8. On the Prototype tab, specify whether you want to use an existing design as a template
for the generated diagram. Any connectivity in the current design that matches
connectivity in the selected template design will take the layout from the template. Any
unmatched connectivity in the current design will be laid out automatically.
Note
If a path in the current project is more complex than the reference path in a template
path, Capital AutoView Assist for Logic uses its own improved algorithm to
determine the layout of the path.
In the From Project window, select the project that contains the template diagram. In
the Select Design Prototype window, select the template diagram from the browser
tree.
Note
If a design (for which diagrams have to be generated) and the template are revisions
of the same design, connectivity objects (devices, conductors, and so on) are
matched by revisions. Otherwise, connectivity objects are matched by name.
Diagram flow — Specify whether you want the layout of the components, pins and conductors
in the diagram to flow horizontally (left to right), or vertically (bottom to top).
Enable connector flow — Check this box if you want devices and connectors to have their pins
only on the sides that follow the direction of the Diagram flow. That is, on the top and bottom
sides in a vertical flow, and on the left and right sides in a horizontal flow. This restricts the
connector placement to the sides of devices following the flow.
Do not check this box if you want devices and connectors to have pins on all sides, and
therefore do not want to restrict connector placement on devices.
Note that harness-side connectors become shared if they have multiple instances in the
generated diagram as a result of the flow.
Enable Tree Layout — When you check this box, diagrams are created using a tree layout that
reflects the specified Diagram flow direction. When you do not check this box, diagrams are
created using a graph representation that reduces the overlapping of connectivity and bends in
conductors. The following considerations are relevant to this type of layout:
Enable device stretching — Check this box if you want devices to stretch in the generated
diagram to reduce net jogs, and the crossover of conductors. The device height and width
exceeds nominal pin grid spacing. Otherwise, do not check this box.
Optimize parallel placements of tree devices — Many devices can directly associate to a
single device. Check this box if you want such associations to be graphically represented by
aligning the devices either vertically, or horizontally. This is considered a one-to-many
connection. An example is an ABS module, and its sensors.
Enable connector splitting by proximity — Check this box if you want the graphical
representation of harness connectors to be split around the devices to which they belong, if it
reduces net jogs, and conductor crossover. Otherwise, do not check this box.
Hide unconnected pins — This specifies whether unconnected pins are hidden (selected) or
displayed (unselected), in the generated diagrams.
Minimum segment length — Specify the minimum distance in grid spaces that can exist
between any two devices, connectors, or splices that are connected by a conductor. If a greater
length is specified, more white space will appear between objects in the diagram.
Related Topics
Overview of Capital AutoView Assist for Logic
Table 16-3. Auto View Diagram Generator - Layout Styling Tab (cont.)
Field Description
Enable Tree When you check this box, diagrams are created using a tree layout that
Layout reflects the specified Diagram flow direction. When you do not check
this box, diagrams are created using a graph representation that reduces
the overlapping of connectivity and bends in conductors. The following
considerations are relevant to this type of layout:
• Generated diagrams do not have a flow.
• Pins are not always evenly distributed.
• Conductors may have 90 degree bends.
Enable Device Check this box if you want devices to stretch in the generated diagram
Stretching to reduce net jogs, and the crossover of conductors. The device height
and width exceeds nominal pin grid spacing. Otherwise, do not check
this box.
Optimize Parallel Many devices can directly associate to a single device. Check this box
placements of Tree if you want such associations to be graphically represented by aligning
Devices the devices either vertically, or horizontally. This is considered a one-
to-many connection. An example is an ABS module, and its sensors.
Enable Connector Check this box if you want the graphical representation of harness
Splitting by connectors to be split around the devices to which they belong, if it
Proximity reduces net jogs, and conductor crossover. Otherwise, do not check this
box.
Enable Inline Check this box to enable the creation of individual inline pin pairs. For
Splitting example, if an inline has ten pins then ten instances of that inline are
created. Note: Enabling Inline Splitting normally creates a better layout
when compared with a single instance of the inline, however this
should be validated on your data.
Auto select Border Check this box to automatically select a suitable border to fit the
to Fit design.
Minimum Segment Specify the minimum distance in grid spaces that can exist between any
Length two devices, connectors, or splices that are connected by a conductor. If
a greater length is specified, more white space will appear between
objects in the diagram.
Minimum Device Specify the minimum width in grid spaces for Device display.
Width
Related Topics
Generating Diagrams for a Project
Specifying Layout Styling when Generating Diagrams
Related Topics
Generating Filtered Diagrams for a Design
Specifying Layout Styling when Generating Diagrams
Objects
Usage Notes
• A property consists of the following fields:
o Name — A unique identifier for the property. Read-only.
o Value — The value assigned to the property. Optional.
o Type — This is the data type of the value. Mandatory. If you enter a Value that is
not supported by the selected Type, the Value appears in red text, and the OK
button is disabled.
The following types are available:
o String — A mix of letters, number or special characters.
o Integer — A whole number.
o Float — A number including a decimal (floating) point.
Related Topics
Generating Filtered Diagrams for a Design
Objects
Usage Notes
• A property consists of the following fields:
o Name — A unique identifier for the property. Read-only.
o Value — The value assigned to the property. Optional.
o Type — This is the data type of the value. Mandatory. If you enter a Value that is
not supported by the selected Type, the Value appears in red text, and the OK
button is disabled.
The following types are available:
o String — A mix of letters, number or special characters.
o Integer — A whole number.
o Float — A number including a decimal (floating) point.
Related Topics
Generating Filtered Diagrams for a Design
Objects
Usage Notes
• Connectivity objects selected in the Available Connectivity tree are highlighted in the
diagram.
Related Topics
Generating Filtered Diagrams for a Design
Specifying Layout Styling when Generating Diagrams
New Generated Diagrams Dialog
Usage Notes
• If ‘Show AutoView Style Editor’ is selected, the AutoView Style Editor Dialog is
displayed as the project is imported. This dialog enables you to specify component
styling, diagram layout styling and to select a template (prototype) to be applied to the
diagrams that are being imported.
Related Topics
Importing a Project and Generating Diagrams
AutoView Style Editor Dialog
Objects
• The dialog has three tabs:
o Component Styling Tab
o Layout Styling Tab
o Prototype Tab Contents
Table 16-15. Auto View Style Editor - Layout Styling Tab (cont.)
Field Description
Auto select Check this box to automatically select a suitable border to fit the design
Border to Fit
Minimum Specify the minimum distance in grid spaces that can exist between
Segment any two devices, connectors, or splices that are connected by a
Length conductor. If a greater length is specified, more white space will appear
between objects in the diagram.
Minimum Specify the minimum width in grid spaces for Device display.
Device Width
Related Topics
Importing a Project and Generating Diagrams
Specifying Layout Styling when Generating Diagrams
Import Project and Generate Diagrams Dialog
Table 16-17. AutoView: Query and Generate Design Dialog - Scope Tab
Field Description
Scope Tab Use this dialog box to specify the designs and build lists from which
you want to take the connectivity that will be included in the generated
design and diagrams.
Design Type Select the type of designs from which you want to take connectivity.
The available designs for that type are displayed in the Available
window. Mandatory.
Available Window Lists the available designs and build lists (of the type selected for
Design Window ). Select the build lists and designs from which you
want to take connectivity and click Add to move them to the Selected
window. Click Add All to move all build lists and designs to the
Selected window.
Selected Window Lists the designs and build lists that have been selected. These are the
designs whose connectivity will be included in the generated design
and diagrams. To move a design to the Available window, select it and
click Remove. To move all designs to the Available window, click
Remove All.
Effectivity
Table 16-18. AutoView: Query and Generate Design Dialog - Design Tab
Contents
Field Description
Design Tab Used to specify the base details for the generated design.
Table 16-18. AutoView: Query and Generate Design Dialog - Design Tab
Contents (cont.)
Field Description
Name A unique label to identify the design. Mandatory.
Properties Click this button to access the Edit Design Properties Dialog, from
where you can create properties to associate with the design.
Optional.
Revision Specifies the version of the design, allowing multiple updated
versions of the same design to exist in the database. Mandatory.
Short Description Enter a line of descriptive text to provide more information about the
design revision. This information is displayed alongside the design
Filter Tab and Revision in the Project Browser Window. Optional.
Description This is a free-text field into which you can enter additional
comments or notes relevant to this design. Optional.
Release Level This field is used to record the design’s progress through the stages
of the design lifecycle. A number of system-defined release levels
are available, but it is possible to create custom levels in Capital
Project (see the Creating a Release Level for a Projecttopic in the
Capital Project User Guide for more information). Regardless of the
number of custom levels available, they must correspond to one of
the system-defined release levels:
If no custom levels are configured, the only option available is
Draft, which is selected by default.
Any custom levels configured must correspond to the Draft system-
defined level, so select the custom level required as dictated by your
internal procedures.
In either case, this is field is mandatory.
Abstraction If you are using design abstractions, select the abstraction to which
this design belongs, from the dropdown list. Maintained in Capital
Project, abstractions allow you to group related harnesses together
for reporting purposes, providing a “view” of a subset of a vehicle’s
wiring. See the Create a Project’s Design Abstractions topic in the
Capital Project User Guide for more information. Optional.
Domain If you are using domains to restrict user access to designs, select the
domain to which this design belongs from the dropdown list. Only
users with access rights to the selected domain are able to access this
design. Domains are created and associated with user accounts in
Capital User. See the Domains topic in the Capital User User Guide
for more information. Optional.
Table 16-18. AutoView: Query and Generate Design Dialog - Design Tab
Contents (cont.)
Field Description
Applicable The options that apply to this design revision. Click the ellipsis (...)
Options button to the right of the field to launch the Applicable Options
Dialog, from where you can select the option codes available. Once
selected, the available options are displayed in the field.
These options - created and maintained in Capital Project - can then
be applied to the components on the design. Optional.
Option The option or option expression that you want to apply to the whole
design revision. Click the ellipsis (...) button to display the Edit
Option Expression Dialog where you can select a single option or
create an option expression. Optional.
Parent Folder The folder in the Project design tree under which the design will be
added. Click the ellipsis (...) to display the Scope Tab where you can
select the folder.
Table 16-19. AutoView: Query and Generate Design Dialog - Filter Tab
Field Description
Filter Tab Used to specify attribute filters against components or devices to
restrict the connectivity that is included in the generated design and
diagrams.
Filter Table Lists the filters that have been set in a tree. The tree consists of entity
type (component or device) nodes and sub-nodes for specific attributes
used to filter those types of entities.
Attribute Lists entity types and the attribute filters set for them.
Name To add an entity type, select Entities at the top of the tree and click
Add New Attribute (x) A node is added to the tree. Click on that node
(in the column) to select the entity type from a dropdown list. A sub-
node for an attribute is added below the entity node, click on the sub-
node to select an attribute name from a dropdown list.
To add additional attribute sub-nodes below an entity type, click that
entity node in the tree and click Add New Attribute (x). A new sub-
node is added below the entity type.
To remove a node and its sub-nodes, select that node and click
Remove Attribute (x).
To remove all nodes, click Reload Criteria (x).
Table 16-19. AutoView: Query and Generate Design Dialog - Filter Tab (cont.)
Field Description
Operator Offers a list of standard query comparators that you can use in the filter
for the corresponding, as defined in table: Table 16-20 below.
Select the condition to use, then enter the number or string to compare
the attribute or property to in the Related Topics column.
Value Specifies the value used in the filter for the corresponding.
Connectivity Specifies the different ways in which electrically connected entities
processor can be discovered for the purposes of filtering data. Mandatory.
The options are:
Connectivity Between Pin ListsDiscovers all connectors connected
between the pin lists returned by the filter. This discovery will pass
through any splices and inlines. Additionally, if used with a Pin
Processor the discovery of conductors can traverse devices that have
internal connectivity.Directly ConnectedDiscovers all conductors
connected to the pin lists returned by the filter. If the pin list is a
device, then the harness connector and any device connector pins are
included.IdentityDoes not search the connectivity for any other
entities than those specified by the filters in the Filter Table.Signal
TracerIdentifies each item in the filter and discovers all their
connected conductors and terminations. It can traverse all splices and
inlines. Additionally, if the Pin Processor filter is selected here it
allows traversal between pins connected with internal connectivity and
symbols having internal links, for example a fuse symbol with a “fuse”
link.
Configuration Specifies that you want to filter the connectivity to only that belonging
to a particular vehicle configuration. Optional.
Pin Processor Used in conjunction with the Connectivity Between Pin Lists or Signal
Tracer Connectivity Processor to discover additional objects for
inclusion in the target design. One processor is provided: Traverse
Internal Links.
This processor enables the system to traverse internal links created
within Capital Symbol.
Additional processors can be developed and loaded as plugins. For
more information see the PluginDevelopment.pdf document that is
located in the doc\plugin folder of your Capital installation.
Table 16-19. AutoView: Query and Generate Design Dialog - Filter Tab (cont.)
Field Description
Reuse shared Specifies whether shared objects are copied to the new design as new
objects in objects (unselected) or if they are created in the new design with
design stitching references to the shared object (selected). Mandatory, displayed only
for Capital Logic designs.
For example:
If you select this option and there is a shared device DEV1 in the scope
designs, the generated design contains a device DEV1 that is an
instance of the same shared device.If you do not select this option and
there is a shared device DEV1 in the scope designs, the generated
design contains a device DEV1 but it is not an instance of the shared
device DEV1 in the scope designs. It is a new device DEV1.
Usage Notes
Related Topics
Generating a Design and Diagrams for Filtered Connectivity from Multiple Designs
Capital Topology enables you to create topological designs and diagrams from within Capital
Logic.
Capital Topology Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
Enabling Capital Topology Functionality in Capital Logic. . . . . . . . . . . . . . . . . . . . . . . 550
Video Test Drive - Aerospace and Topology Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
High-Level Flow for Using Capital Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
Styling Objects (Capital Topology) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
Harness Concurrency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
Topology Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558
Creating a Capital Topology Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558
Editing a Capital Topology Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
Deleting a Capital Topology Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
Logical Design Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
Build List Association (Managed Mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
Associating Logical Designs with the Topological Design . . . . . . . . . . . . . . . . . . . . . . . . 561
Replacing a Logical Design Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
Synchronizing Wiring Changes with a Capital Topology Design . . . . . . . . . . . . . . . . . . . 565
Locating a Source Physical Object in a Capital Logic Design . . . . . . . . . . . . . . . . . . . . . . 566
Comparing Capital Topology Design Revisions with Other Design Revisions . . . . . . . . . 567
Topology Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
Working with Multiple Diagrams Overview Video . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
Creating a Capital Topology Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
Editing a Capital Topology Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
Deleting a Capital Topology Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
Opening a Topology Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
Closing a Topology Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
Flipping Objects in a Topology Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571
Rotating Objects in a Topology Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572
Defining Rotation Increments in a Topology Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 572
Free Rotation of an Object or Comment Symbol in a Topology Diagram. . . . . . . . . . . . . 573
Physical Scale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575
Specifying the Physical Scale of a Capital Topology Diagram . . . . . . . . . . . . . . . . . . . . . 575
Skeletons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
Adding a Skeleton to a Topology Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
Removing a Skeleton from a Topology Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577
Adding an Empty Slot to a Topology Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577
Adding a Slot with a Device to a Topology Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
Editing a Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
Constraining the Placement of Devices in a Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
Manually Placing a Device in a Slot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
Manually Unplacing a Device from a Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
Viewing the Signal Map for a Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
Creating Multiple Slot Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
Slot Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
Adding an Unassociated Slot Connector to a Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
Adding a Specific Harness Connector as a Slot Connector to a Slot . . . . . . . . . . . . . . . . . 585
Editing a Slot Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586
Specifying a Route Code for a Slot Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586
Moving a Slot Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
Constraining the Association of Logical Harness Connectors to Slot Connectors. . . . . . . 588
Device Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590
Viewing the Attributes and Properties for a Device Connector . . . . . . . . . . . . . . . . . . . . . 590
Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
Adding a Bundle to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
Editing a Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
Creating Multiple Bundle Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
Specifying the Physical Length of a Bundle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594
Specifying Variant Physical Lengths for a Bundle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594
Moving a Bundle Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
Deleting a Bundle Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597
Deleting an Entire Bundle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597
Specifying a Bundle (Harness) as a Poke Home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598
Constraining the Placement of Splices on a Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
Multiple Harnesses at Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600
Wires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
Constraining the Routing of Wires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
Using the Routing Assistant to Identify the Possible Routes for an Unrouted Wire . . . . . 604
Using the Routing Assistant to Identify all Unrouted Wires that Need to Pass Through a
Selected Inline Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
Reporting on All Unrouted Wires that Could Pass Through an Inline Connector . . . . . . . 607
Viewing the Attributes and Properties of a Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
Updating Wire Lengths. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
Annotating Topology Wire Lengths and Harness Attributes Back to Logical Wires and Splices
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608
Multicores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
Viewing the Attributes and Properties of a Multicore . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
Splices in Capital Topology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611
Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
Design Rule Checks (Capital Topology) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
Running Design Rule Checks in the Design Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
Capital Topology Dialog and Field Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642
Add Selected Logical Design Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643
Add Selected Logical Design Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
Associate Signals By Attribute or Property Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
Associate Signals By Attribute or Property Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
Associate Wiring Designs Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
Associate Wiring Designs Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646
Concurrency Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
Connector Details Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
Connector Details Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
Design Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
Edit Design (Capital Topology) Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
Edit Design Dialog (Capital Topology) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
Edit Physical Scale (Capital Topology) Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
Edit Physical Scale Dialog (Capital Topology) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653
Edit Diagram Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653
Edit Diagram Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
Edit Properties: Assembly Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655
Edit Properties: Assembly Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656
Edit Properties: Bundle Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
Edit Properties: Bundle Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
Edit Properties: Device Connector Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664
Edit Properties: Device Connector Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665
Edit Properties: Hole Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666
Edit Properties: Hole Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668
Edit Properties: Inline Plug Connector Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672
Edit Properties: Inline Plug Connector Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674
Edit Properties: Inline Receptacle Connector Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
Edit Properties: Inline Receptacle Connector Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681
Edit Properties: Multicore Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686
Edit Properties: Multicore Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687
Edit Properties: Diagram Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688
Edit Properties: Diagram Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690
Edit Properties: Slot Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690
Edit Properties: Slot Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
Edit Properties: Slot Connector Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696
Edit Properties: Slot Connector Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 698
Edit Properties: Virtual Harness Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703
Edit Properties: Virtual Harness Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704
Edit Properties: Wire Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 708
Edit Properties: Wire Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710
Edit Skeleton Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711
The Capital Topology functionality is available within Capital Logic only when a Capital
Topology diagram is active.
Capital Topology designs can be synchronized with Capital HarnessXC, or exchanged with
MCAD tools via one of the Capital MCAD topology bridges. For further details, see the
Bridging Data In and Out of Capital User Guide.
You can report on topological data using either the embedded reporting capability or Capital
Enterprise Reporter. For further details, see the Capital Enterprise Reporter User Guide.
Capital Insight
Capital Insight is an additional product that provides functionality for conducting physical
architectural trade studies on designs created in Capital Integrator, Capital Topology, Capital
HarnessXC and Capital ModularXC. These studies use metrics to compare design data, for
example, using cost and weight.
See the Capital Insight chapter in the Capital Design Tools - Common Functions User Guide
for more details.
Related Topics
Enabling Capital Topology Functionality in Capital Logic
Video Test Drive - Aerospace and Topology Flows
High-Level Flow for Using Capital Topology
Note
Alternatively, you can enable Capital Topology by editing the clientprops.xml file in
the config directory of your Capital installation. Find the <packages> section in that
file and ensure that the line for topology reads: <feature check="YES"
name="topology"></feature>
Related Topics
Capital Topology
Video Test Drive - Aerospace and Topology Flows
High-Level Flow for Using Capital Topology
1. In Capital Logic, create a topology design. See “Topology Designs” on page 558. Note
that Capital Topology uses a style set to style objects in diagrams. See “Styling Objects
(Capital Topology)” on page 553.
2. Specify the physical scale of the diagram. See “Physical Scale” on page 575. This must
be done prior to creating the topology (for example, bundles) because the graphical
length of bundle graphics (relative to the skeleton) will change if you change the scale.
This means the bundles would no longer fit correctly with the skeleton.
Note
You can run design rule checks on the diagram (see “Design Rule Checks (Capital
Topology)” on page 641), use Capital Enterprise Reporter to report on the design
data (see the Capital Enterprise Reporter User Guide), and compare the topology design
with wiring designs (see “Comparing Objects and Their Properties in Design Revisions
or Build Lists” on page 61).
10. If you want to locate and/or edit a particular object on the source Capital Logic designs,
use the Show Physical Source function to open the relevant diagram and make the edit.
See “Locating a Source Physical Object in a Capital Logic Design” on page 566.
11. Select the topology design to open it in the Diagram Window again; the edits from the
Capital Logic design are reflected in the topology design.
12. You can annotate wire lengths from the Capital Topology design back to the wires in the
Capital Logic designs. See “Annotating Topology Wire Lengths and Harness Attributes
Back to Logical Wires and Splices” on page 608.
Related Topics
Capital Topology
Enabling Capital Topology Functionality in Capital Logic
Video Test Drive - Aerospace and Topology Flows
See the Diagram Styling User Guide for more information about style sets and how to edit
them.
Harness Concurrency
Harness concurrency is functionality that allows you to run Capital Topology in multi user
mode or single user mode. Multi user mode enables multiple users to open the same Capital
Topology diagram for simultaneous editing and allows each user to work on a different portion
of the diagram. This is achieved primarily by the ability to lock individual harnesses and slots.
If you do not run Capital Topology in multi user mode, you run it in single user mode. In this
mode, if a user opens a design, other users can open the same design in read-only mode only.
If a lock is held on a diagram in Capital Topology, the design for that design cannot be edited or
deleted in Capital Project. If you hold a lock on a slot or harness in Capital Topology, other
users cannot perform editing actions that operate directly on that locked object and connected
objects. Connected objects can be bundles, nodes, bundle regions, inline connectors, slot
connectors, device connectors, cavities and wiring objects. Any actions that they cannot
perform are disabled for the locked objects.
Note
To run Capital Topology in single user mode, your user account must have the Manage
Design permission set in Capital User. You can still edit a diagram in multi user mode even
if you do not have this permission set. See the Capital User help system for more information
about setting permissions for user accounts.
When you are editing a diagram in multi user mode, you can dim (gray out) objects that are
unlocked and objects that are locked by other users. This means that you only see objects that
you have locked and can edit. See “Dimming (Graying out) Slots and Harnesses that Are
Locked by Other Users or that Are Unlocked” below.
After you have finished editing an object, you should unlock it so that other users can edit it if
required (see “Unlocking a Harness or Slot when Running in Multi User Mode” below).
If you create a new harness or slot in multi user mode, no other user will see the new object on
their Concurrency tab until you save it. When you save the object, you have a lock on it
automatically.
Concurrency tab
The Concurrency tab is displayed at the bottom left of the application window and enables you
to view the lock state for the diagram, each harness and each slot.
• Mode field - enables you to select whether you are running in multi user or single user
mode. See “Selecting to Run in Multi User or Single User Mode” below.
• Table of harnesses and slots - enables you to view a list of slots, harnesses and their lock
states (see “Selecting which Lockable Objects to View on the Concurrency Tab”
below). The table contains the following columns:
o Lock - shows whether the object is unlocked , locked by you or locked by
another user .
o Modified - shows whether the object has been modified since the last save in
the current session. The column is blank for unmodified objects.
o Object Type - shows whether an object is a slot or a harness.
Or
o Click on the harness or slot in the diagram or Design Browser, press Space Bar and
enter Lock.
o Ensure that the object you want to lock is listed on the Concurrency tab and click
the unlocked padlock symbol at the start of the table row for it.
2. If the object is listed on the Concurrency tab, the padlock symbol for the object changes
to a locked padlock to indicate that the object is locked. The name of the user holding
the lock is also displayed in the Locked By column for that object. Any other users
viewing the object on the Concurrency tab in another session will see a locked padlock
with an extra mark .
If you have locked a harness, the action also refreshes and locks all single-harness slots
on the harness.
If you have locked a slot connected to a single harness, the action also refreshes and
locks the harness attached to the slot.
If you have locked a slot connected to more than one harness, the action also refreshes
any harnesses directly connected to it.
Unlocking a Harness or Slot when Running in Multi User Mode
Note
You can unlock an object only if it is has been saved since it was last modified.
2. If the object is listed on the Concurrency tab, the padlock symbol for the object changes
to an unlocked padlock to indicate that the object is unlocked.
Dimming (Graying out) Slots and Harnesses that Are Locked by Other Users or that Are
Unlocked
You can dim (gray out) slots and harnesses in the diagram if they are locked by other users or
are unlocked. This helps you to see which objects are locked by you and are therefore editable
in the diagram. If you print out a diagram, any dimmed objects are printed normally.
1. Ensure that the dimming functionality is enabled by clicking the Dim By Harness Lock
Status button at the bottom of the application window so that it has no red stop sign
displayed. If a red stop sign is displayed , no objects are dimmed in the diagram.
Alternatively, you can right-click on the Dim By Harness Lock Status button to
display two sliders and a Dim checkbox. Check the box to enable the dimming of
objects.
2. Display the sliders by right-clicking on the button. One slider is for unlocked objects
and the other is for objects locked by other users . Move the sliders down to dim out
objects and move the slider up to make objects clearer.
3. Click in the main application window to hide the sliders.
Refreshing Harness Information with Changes from Other Users and Synchronize the Wiring
Select an unlocked object on the Concurrency tab and click the Refresh Harnesses and Slots
button next to the Mode field. You can select multiple objects. This refreshes only the
selected objects.
Or
Do no select anything and click the Refresh Harnesses and Slots button next to the Mode
field. This refreshes the entire diagram.
Or
Select an unlocked object in the diagram, press Space Bar and enter Refresh to refresh the
harness on which the object is located and any adjacent modified harnesses.
Topology Designs
A topology design is the container for your engineered data representing a topological layout for
a harness.
Multiple topology designs can be grouped together in a build list. See “Build Lists” on page 48
for more information.
The following topics detail how to create, edit and delete topology designs:
Results
The design is added to the Project Browser Window. The diagram is opened in the Diagram
Window.
If you selected a template design with multiple diagrams, the system creates diagrams matching
those and with the same names.
Related Topics
Topology Designs
Creating a Capital Topology Diagram
Editing a Capital Topology Design
Deleting a Capital Topology Design
Procedure
1. Navigate to the design you want to delete in the Project Browser, right-click and select
Delete.
2. A message is displayed asking you to confirm the deletion; click Yes to proceed. The
following design entities are deleted:
• Design folder
• Design
• Diagrams (if present)
Related Topics
Topology Designs
Deleting a Capital Topology Diagram
You can replace a logical design association with a newer revision of that design. When you do
this, the topological design retains the device placement and wiring for common devices and
nets from those logical design revisions.
Related Topics
Associating Logical Designs with the Topological Design
Replacing a Logical Design Association
Procedure
Either:
The Associate Wiring Designs Dialog Box is displayed and the Associated Designs
window displays any logical designs that are associated already.
Note
When associating individual designs, you can remove the association with a logical
design by selecting it in the Associated Designs window and clicking the Remove
associated designs () button. An icon () indicates that you are going to remove the
association when you click OK.
Results
• The Wiring Browser lists the devices, connectors, multicores, splices and wires from the
associated Capital Logic designs. If a logical device has the same name as a topology
slot, the device is placed in the slot (unless constraints dictate otherwise).
• If a harness connector has the same name as a slot connector on the Capital Topology
diagram, an association is created between them. If a device connector is attached to a
harness connector in the Capital Logic design, a device connector is created as a
separate object that is connected to the slot connector. The device connector is added to
the Design Browser.
• If an inline plug connector or an inline receptacle connector from the Capital Logic
designs has the same name as one in the topology diagram, an association is created
between them.
• Wires associated with bundles in the topology diagram are added to the Design Browser,
either under the Unassigned node or, if grouped into Signals, under the Signals node.
• Any items that have not been placed or routed are grayed out in the Wiring Browser.
Notes relating to option expressions on devices and nets:
• When associating logical designs, any nets that are tagged with an option expression that
evaluates to FALSE because of obsolete options are not added to the design. Similarly, a
net connection will not be added if that connection’s pins are tagged with an option
expression that evaluates to FALSE because of obsolete options.
• Devices tagged with an option expression that evaluates to FALSE because of obsolete
options are not added to the design. Similarly, a device is not added even if one of its
pins is tagged with an option expression that evaluates to FALSE because of obsolete
options.
• In the case of a net connected to multiple pins, the net will be considered even if at least
one of its pins has an option expression that is TRUE. However, the net is ignored if its
pins all have option expressions that are FALSE.
• If a logic design is tagged with an option expression that evaluates to FALSE, you will
not be allowed to add this design to the set of associated designs. It is displayed on the
right-hand side of the dialog in italics, which indicates that it will not be considered.
• If an already associated design is tagged with an obsolete option expression, it will be
un-associated whenever the associations are updated.
Related Topics
Logical Design Association
Replacing a Logical Design Association
Synchronizing Wiring Changes with a Capital Topology Design
When you do this, the topological design retains the device placement and wiring for common
devices and nets from those logical design revisions.
Prerequisites
• The new design revision must have been created in Capital Logic or Capital Project.
• If you are working in managed mode (where a build list association is used), the new
design revision must be added to the associated build list and the old one must be
removed.
Procedure
Follow the appropriate procedure from the table.
Results
• The topological design retains the device placement and wiring for common parts of
those logical designs or design revisions.
Prerequisites
• The Capital Logic designs must be associated with the topology design. See “Logical
Design Association” on page 561.
Procedure
Either:
Results
• If logical objects have changed names, been created or been deleted, the associations
with objects in the topology diagram change accordingly.
• The Design Assistant displays any messages or errors related to this action.
• If the synchronization finds a change to a net or device that means the object is now
obsolete, the device/signal or its wiring is not removed from the Capital Integrator
design but the Sync tab indicates that it cannot remove the signal/device:
o If the system finds a change to a net that now has wiring, the signal is not removed
from the design.
o If the system finds a change to a net that has not yet got wiring generated, the signal
is removed from the design and a message is displayed on the Sync tab.
o If the systems finds a change to a device that is now placed, the device is not
removed from the design.
o If the system finds a change to a device that is not placed, the device is removed
from the design and a message is displayed on the Sync tab.
Related Topics
Logical Design Association
Note
If there is more than one diagram containing the physical source, the Show Physical
Source dialog is displayed where you select the diagram to be opened.
Results
• The Capital Logic diagram containing the source physical object is opened in the
Diagram Window.
• The source physical object is highlighted in the Capital Logic diagram.
Topology Diagrams
A topology diagram is the drawing canvas upon which the topological layout for a design is
created. Each design can have one or more diagrams.
• “Creating a Capital Topology Diagram” on page 568
• “Editing a Capital Topology Diagram” on page 569
• “Deleting a Capital Topology Diagram” on page 569
• “Opening a Topology Diagram” on page 570
• “Closing a Topology Diagram” on page 570
Results
The diagram is added under the design in the Project Browser Window and is opened in the
Diagram Window.
Related Topics
Topology Diagrams
Creating a Capital Topology Design
Specifying the Physical Scale of a Capital Topology Diagram
Procedure
1. Navigate to the diagram that you want to delete in the Project Browser Window, right-
click and select Delete.
2. A message is displayed asking you to confirm the deletion; click Yes to proceed. The
diagram is deleted.
Related Topics
Topology Diagrams
Deleting a Capital Topology Design
Note
Bundles cannot rotate.
Procedure
1. Press Space Bar and enter Set Rotation Degrees.
2. Set the Minor Rotation Increment used for finer grained rotational control. Default value
is 1 degree.
3. Set the Major Rotation Increment used for coarser grained rotational control. Default
value is 5 degrees.
4. Click on the OK to confirm your settings.
Related Topics
Free Rotation of an Object or Comment Symbol in a Topology Diagram
Procedure
1. Select one object that you want to rotate.
2. Either:
• Press CTRL+> to rotate the object clockwise by a major increment. Press Ctrl+< to
rotate counter-clockwise. For finer grained control press CTRL+Shift+> to rotate
the object clockwise by a minor increment. Press Ctrl+Shift+< to rotate counter-
clockwise.
• Press CTRL and move the clickable scroll wheel on your mouse forwards or
backwards to rotate the object clockwise or counter-clockwise by a major increment.
For finer grained control press CTRL+Shift and move the clickable scroll wheel on
your mouse forwards or backwards to rotate the object clockwise or counter-
clockwise by a minor increment.
3. The object rotates at a pre-defined degree increment around their center point.
Related Topics
Rotating Objects in a Topology Diagram
Defining Rotation Increments in a Topology Diagram
Physical Scale
In a topology diagram, this is the scale used for the distance between grid points that indicates
how long that distance is for real-world, physical wires.
It is used to calculate the real-world length of bundles and wires in the diagram.
The physical scale does not effect the size of the diagram when it is printed.
The size of a skeleton graphic on a diagram does not change if the physical scale is changed,
only the number of grid points that fit within the skeleton changes.
This scale must be specified prior to creating the topology (for example, bundles) because the
graphical length of bundle graphics (relative to the skeleton) will change if you change the
scale. This means the bundles would no longer fit correctly with the skeleton.
Skeletons
A skeleton graphic is created and saved as a border in Capital Symbol.
It uses the Physical Scale that has been set for the diagram.
Note that you can also add a border to the diagram. See “Borders” on page 367.
Slots
Slots represent the location of electrical equipment within the electrical wiring system. At the
most basic level, a slot is a connection point to the harness system. A slot is also referred to as a
component. Electrical devices, as defined in the associated Capital Logic diagrams, are placed
into slots in the topology diagram to define connectivity.
Slots are connected together by bundles and there must be a slot connector or a hole wherever a
bundle connects to a slot.
• Create an empty slot prior to associating a Capital Logic design with the topology design
and place a device in it after the association. Note that when you associate a Capital
Logic design with the topology design, any logical device with a name matching a
topology slot name is placed in that slot automatically.
• Create a slot for a specific device after a Capital Logic design has been associated with
the topology design. This action creates the slot and places the device in one step.
If you want to place multiple devices in one slot, you can use the Place by Attribute/Property
constraint to force the placement. See “Constraining the Placement of Devices in a Slot” on
page 579. If there is a direct connection (wire) between two devices placed in one slot, the wire
connecting them is listed below the slot in the Design Browser.
Once devices have been placed in a slot, you can view a read-only signal map to see which
signals and wires are entering the slot at which connector cavities or holes.
Related Topics
Slots
Adding a Slot with a Device to a Topology Diagram
Editing a Slot
Viewing the Signal Map for a Slot
Related Topics
Slots
Adding an Empty Slot to a Topology Diagram
Editing a Slot
Viewing the Signal Map for a Slot
Editing a Slot
This topic details how to edit the attributes and properties of a slot on a topology diagram.
Procedure
1. Select the slot to be edited.
2. Either:
• Press Space Bar and enter Properties
• Right-click on the selected entity and select Properties
• Double-click on the slot in the Diagram Window
The Edit Properties: Slot Dialog is displayed.
3. Make any changes required to the slot attributes and/or properties.
4. Click OK.
Related Topics
Slots
Adding an Empty Slot to a Topology Diagram
Adding a Slot with a Device to a Topology Diagram
Viewing the Signal Map for a Slot
Note
Constraints can be bundled into rules that can be set on objects. See “Rules and Constraints”
on page 469 for further information about creating rules.
Rules and constraints adhere to hierarchies. That means, if they are set on an object, child
objects inherit them. For example, constraints can be set for a diagram so that they are inherited
by all objects on that diagram (in this case, all slots and connectors). See “Setting Constraints
for an Entire Topology Diagram” on page 631.
Procedure
1. Select a slot.
2. Either:
• Press Space Bar and enter Properties
• Right-click on the selected entity and select Properties
• Double-click on the slot
The Edit Properties dialog for the object is displayed.
3. Click the Rules tab and click the Add Constraint button; the Constraint Selection
dialog is displayed.
4. Select ‘Place by Attribute/Property’ and click OK; the constraint is added to the Edit
Properties dialog.
5. Edit the constraint as required and click OK.
Results
• The constraint is applied when Capital Logic designs are associated with the topology
diagram and when updated data from the Capital Logic design is synchronized with the
topology design.
Related Topics
Setting Constraints for an Entire Topology Diagram
Constraints (Capital Topology)
Slots
Procedure
1. Select one or more unplaced devices in the Wiring Browser and either:
• right-click on one of the selected devices and select Place Device
• press Space Bar and enter Place Device
The Place Device Dialog is displayed.
2. Select the slot into which you want to place the devices and click OK.
Results
• The devices are placed in the slot.
• For each device, a ‘Place by Attribute/Property’ constraint is added to the slot specifying
that the device is to be placed in that slot. For example, for a device called DEV1, the
constraint would be Do place devices with attribute/property matching Name =
DEV1.
Related Topics
Slots
Manually Unplacing a Device from a Slot
Related Topics
Slots
Adding an Empty Slot to a Topology Diagram
Adding a Slot with a Device to a Topology Diagram
Editing a Slot
Prerequisites
• At lease one instance of the slot must exist.
Procedure
Perform one of the following procedures:
Results
The new instance is created in the diagram.
In the Design Browser (Design tab), an Instances folder displays under the slot and lists the
instances of the slot with the name of the diagram containing that instance. The connectors on
an instance are listed below it.
You can use styling to control whether and how cross-reference text is displayed at a slot with
multiple instances. You apply this styling to the slot object in your style set. See Adding a
Cross-Reference Text Decoration in the Capital Diagram Styling User Guide.
Slot Connectors
In a topology diagram, a slot connector connects devices in a slot to a bundle. You cannot
connect a bundle to a slot without either a slot connector or holes. Bundles from different
harnesses can connect to the same slot connector without the harnesses merging.
A slot connector in a Capital Topology design represents a harness connector on the associated
Capital Logic designs. Any device connector attached to the harness connector is created as a
separate object that is connected to the slot connector.
• Create an empty slot prior to associating a Capital Logic design with the topology design
and place a device in it after the association (see “Adding an Empty Slot to a Topology
Diagram” on page 577). When you associate a Capital Logic design with the topology
design, any logical device with a name matching a topology slot name is placed in that
slot automatically. Any harness connectors on the logical device are automatically
added as slot connectors to the slot.
• Create a slot for a specific device after a Capital Logic design has been associated with
the Capital Topology design. This action creates the slot and places the device in one
step. Any harness connectors on the logical device are automatically added as slot
connectors to the slot. See “Adding a Slot with a Device to a Topology Diagram” on
page 578.
• Add an unplaced logical harness connector to the slot containing its device. See “Adding
a Specific Harness Connector as a Slot Connector to a Slot” on page 585.
• Add an unassociated slot connector manually to a slot. See “Adding an Unassociated
Slot Connector to a Slot” on page 584.
Results
• The slot connector is added to the slot in the Diagram Window.
• The slot connector is added below the slot in the Design Browser.
Related Topics
Slot Connectors
Adding a Specific Harness Connector as a Slot Connector to a Slot
Editing a Slot Connector
Specifying a Route Code for a Slot Connector
Moving a Slot Connector
Related Topics
Slot Connectors
Adding an Unassociated Slot Connector to a Slot
Editing a Slot Connector
Specifying a Route Code for a Slot Connector
Moving a Slot Connector
Procedure
1. Select the slot connector to be edited.
2. Either:
• Press Space Bar and enter Properties
• Right-click on the selected entity and select Properties
• Double-click on the slot connector in the Diagram Window
The Edit Properties: Slot Connector Dialog is displayed.
3. Click the Routes tab, specify the Route Code and click OK.
Related Topics
Slot Connectors
Adding a Specific Harness Connector as a Slot Connector to a Slot
Adding an Unassociated Slot Connector to a Slot
Moving a Slot Connector
Procedure
Do one of the following:
• Right-click the slot connector that you want to move and select the Move slot
connector option from the pop-up menu. Click on the new location.
• Click on the slot connector to select it, press Space Bar and enter Move. Click on the
new location.
• Click on the slot connector, hold the mouse button down and drag the slot connector
to the new location.
Note
During the action, circles denote the valid grid points.
Results
The slot connector moves to the new location and is re-styled appropriately (for example, to
move related text).
Related Topics
Slot Connectors
Adding a Specific Harness Connector as a Slot Connector to a Slot
Adding an Unassociated Slot Connector to a Slot
Editing a Slot Connector
Specifying a Route Code for a Slot Connector
Note
Constraints can be bundled into rules that can be set on objects. See “Rules and Constraints”
on page 469 for further information about creating rules.
Rules and constraints adhere to hierarchies. That means, if they are set on an object, child
objects inherit them.
For example, constraints can be set for a diagram so that they are inherited by all objects on that
diagram (in this case, all slots and connectors). See “Setting Constraints for an Entire Topology
Diagram” on page 631.
This constraint can also be set on a slot so that all slot connectors on that slot inherit it.
Procedure
1. Select a slot. If you want to set this constraint for the entire diagram, see Setting
Constraints for an Entire Topology Diagram.
2. Either:
• Press Space Bar and enter Properties
• Right-click on the selected entity and select Properties
Device Connectors
In a topology diagram, slot connectors represent an associated harness connector. Any device
connector attached to the harness connector is created as a separate object that is attached to the
slot connector.The device connector and harness connector are treated as separate graphical
objects.
However, the device connectors are listed below the slot connectors in the Design Browser.
Bundles
A bundle is used to join together slots and inline pairs. It represents an available wire-routing
path within the electrical system. A collection of bundles represents a harness. There must be a
slot connector or a hole wherever a bundle connects to a slot. After you have associated Capital
Logic designs with the topology design and synchronized logical changes, wires are routed
along these bundles.
Bundles from different harnesses can connect to one connector without the harnesses merging
(see “Multiple Harnesses at Connectors” on page 600).
Note
You can define segments in a bundle by dragging the line, clicking once, and
dragging the line in a new direction.
4. Position the mouse cursor over the grid point where you want to place the other end of
the bundle and double-click. Note again that if you place it on a slot connector or
another bundle, a connection is made automatically. If you place it on a slot, a slot
connector is created automatically.
Results
• If the bundle is not attached to an existing harness, a new harness is added to the Design
Browser.
• If the bundle is attached to an existing harness, new bundles are listed under the harness
in the Design Browser as appropriate.
• If the bundle is attached to a slot connector, a connection is made.
• If the bundle is attached to a slot, a slot connector is created automatically and a
connection is made. The slot connector is added under both the harness and the slot in
the Design Browser.
Related Topics
Bundles
Editing a Bundle
Moving a Bundle Section
Deleting a Bundle Section
Deleting an Entire Bundle
Specifying a Bundle (Harness) as a Poke Home
Editing a Bundle
This topic details how to edit the attributes and properties of a bundle on a topology diagram.
Procedure
1. Select the bundle to be edited.
2. Either:
• Press Space Bar and enter Properties
• Right-click on the selected entity and select Properties
• Double-click on the bundle in the Diagram Window
The Edit Properties: Bundle Dialog is displayed.
3. Make any changes required to the bundle attributes and/or properties.
4. Click OK.
Related Topics
Bundles
Adding a Bundle to a Diagram
Moving a Bundle Section
Deleting a Bundle Section
Deleting an Entire Bundle
Specifying a Bundle (Harness) as a Poke Home
Video
For an overview of working with multiple diagrams, including creating multiple bundle
instances, see the video Multiple Diagrams Overview.
Procedure
Perform one of the following procedures:
Results
The new instance is created in the diagram.
The Design Browser (Design tab) displays an Instances folder under the harness for the bundle.
It lists the instances of that harness. You can also expand the node for that particular bundle to
view the different instances of it
The sliced end of the bundles have an arrowed glyph to indicate that these are sliced
bundles.
You can drag a sliced end to stretch and move a bundle.
You can also extend an instance by adding a bundle at a sliced end. This results in a longer
instance and not a new bundle.
If a harness has multiple instances, you cannot merge it with another harness by dragging a
sliced end. You must drag a non-sliced end. However, you can merge instances of the same
harness to form one instance by dragging a sliced end to any place on the other instance.
You can use styling to control whether and how cross-reference text is displayed at a sliced end
for a bundle. You apply this styling to the bundle object in your style set. See Adding a Cross-
Reference Text Decoration in the Capital Diagram Styling User Guide.
There are various ways you can navigate between object instances, see Navigating Between
Sliced Object Instances in the Capital Design Tools - Common Functions User Guide.
The bundle length is used when calculating the cost of any synthesized wiring. Overriding the
length can therefore change the result of routing logical signals because the system selects the
cheapest route.
Procedure
1. Right-click on the bundle in the Diagram Window or Design Browser and select
Properties; the Edit Properties: Bundle Dialog is displayed.
2. On the General tab, select Override next to the Length field and change the value in the
field.
3. Click OK to exit the Edit Properties facility and to commit your changes.
Related Topics
Adding a Bundle to a Diagram
Editing a Bundle
Specifying Variant Physical Lengths for a Bundle
The physical length is initially determined by the length of the bundle in the diagram. This
length is displayed on the General tab of the Edit Properties: Bundle Dialog for the bundle and
can be overridden (see “Specifying the Physical Length of a Bundle” on page 594). This is the
physical length used by default. However, the bundle length may vary for different variants of
the built vehicle.
The lengths are passed from Capital Topology to Capital HarnessXC when designs are
synchronized between the two. Capital HarnessXC uses the variant lengths when performing
composite breakdown.
Procedure
1. Right-click on the bundle in the Diagram Window or Design Browser and select
Properties; the Edit Properties: Bundle Dialog is displayed.
2. Click the Variant Tab (Edit Properties Dialog).
3. In the Option Expression column of the currently empty row, enter the option expression
for which you want to specify a variant length; a new empty row is added to the table.
4. In the Variant Length column for the option expression that you have entered, specify
the variant length.
5. Repeat steps 3 and 4 for each variant physical length that you want to enter.
6. Click OK to exit the Edit Properties facility and to commit your changes.
Results
• Wiring import and export does not support variant bundle information.
• When the Capital Topology design is synchronized with a Capital HarnessXC design,
the variant lengths are displayed on the Variant tab of the Edit Bundle dialog for the
appropriate bundle in Capital HarnessXC.
• There is no support for linking variant bundles through bridges or Change Manager. The
MCAD bridge is used to set the nominal length.
• When bundles are merged:
o The bundles retain variants and merge where required.
o When merging a variant bundle with a non-variant bundle, the resulting bundle
retains the variant information. The lengths for each variant will be modified by
adding the default length of the non-variant bundle.
o When merging two variant bundles, the variances are merged. Where option
expressions match, the variant lengths are added together.
o When a variant length is unique on one of the bundles, it is not modified on the
merged bundle.
• When splitting a variant bundle, the resulting bundles both have the variant lengths
applied. The lengths are adjusted according to the proportional nominal position where
the bundle is split.
Related Topics
Adding a Bundle to a Diagram
Editing a Bundle
Specifying the Physical Length of a Bundle
• Click a bundle section, hold down the mouse button and drag the bundle section
• Click the end of a bundle section, hold down the mouse button and drag the end of
the bundle
Results
• If you have dragged a whole bundle section, the selected bundle section moves to the
new location.
• If you have dragged the end of a bundle section, the section moves or changes length as
required.
• Any other bundle sections connected to the bundle section move or change length as
required to maintain the connection.
• If you have dragged an end of a bundle section over another bundle section, a
connection is created.
• If you have dragged an end of a bundle section over a bundle section from a separate
harness, the harness being moved merges into the other harness. In the Design Browser,
the harness being moved is no longer displayed and its bundles are displayed under the
other harness.
Related Topics
Bundles
Adding a Bundle to a Diagram
Editing a Bundle
Deleting a Bundle Section
Deleting an Entire Bundle
Specifying a Bundle (Harness) as a Poke Home
Related Topics
Bundles
Adding a Bundle to a Diagram
Editing a Bundle
Moving a Bundle Section
Deleting a Bundle Section
Specifying a Bundle (Harness) as a Poke Home
Procedure
1. Select the slot connector, inline plug connector or inline receptacle connector at which
the bundle is poked home.
2. Either:
• Press Space Bar and enter Properties
• Right-click on the selected entity and select Properties
• Double-click on the slot connector in the Diagram Window
The Edit Properties: Slot Connector Dialog is displayed.
3. Click the Routes tab, click the Poke Home column for the bundle (harness) and click
OK.
Related Topics
Adding a Bundle to a Diagram
Editing a Bundle
Moving a Bundle Section
Deleting a Bundle Section
Deleting an Entire Bundle
Constraining the Placement of Splices on a Bundle
Multiple Harnesses at Connectors
Rules and constraints adhere to hierarchies. That means, if they are set on an object, child
objects inherit them. For example, constraints can be set for a diagram so that they are inherited
by all objects on that diagram (in this case, all slots and connectors). See “Setting Constraints
for an Entire Topology Diagram” on page 631.
Procedure
1. Select a bundle or a parent object of bundles (a harness). If you want to set this
constraint for all objects in the diagram, see Setting Constraints for an Entire Topology
Diagram.
2. Either:
• Press Space Bar and enter Properties
• Right-click on the selected entity and select Properties
• Double-click on the bundle in the Diagram Window
The Edit Properties dialog for the object is displayed.
3. Click the Rules tab.
4. Click the Add Constraint button; the Constraint Selection dialog is displayed.
5. Select ‘Minimum Splice Separation’ or ‘Place Splice/s on Bundle by Attribute/Property’
and click OK; the constraint is added to the Edit Properties dialog.
6. Edit the constraint as required.
7. If you want to use both constraints on the bundle, repeat steps 4 to 6 for the other
constraint.
8. Click OK.
Results
• The constraint is applied when Capital Logic designs are associated with the topology
diagram and when updated data from the Capital Logic design is synchronized with the
topology design.
Related Topics
Setting Constraints for an Entire Topology Diagram
Constraints (Capital Topology)
Bundles
The primary scenario for multiple harnesses at a connector is at an inline connector, for
instance, where wires terminating at the inline belong to different harness part numbers.
However, there are some cases where you may want to have multiple harnesses at a connector
on a slot, for example, if the H1 and H2 harnesses connect to the same connector. In this case,
you may not want to duplicate the connectors on the slot.
Both the H1 and H2 harnesses are connected to the single door harness via
a single inline connector.
page 603).
1. Add a new bundle that either starts of finishes at a connector that is already connected to
another bundle; the system treats this as a new connection to a complex connector
junction.
2. Add option expressions to the bundles to identify their applicability.
3. Specify bundles at the connector that contain poke home wires.
4. Synchronize the data with a design in Capital Harness Classic or Capital HarnessXC; the
system treats the complex junction as if there is a connector applicable to each harness.
Note
All other tools that access the data (including reports, design rule checks and Capital
Enterprise Reporter) treat the complex junction as if multiple bundles are connected
to a single connector.
Related Topics
Specifying a Route Code for an Inline Plug Connector or an Inline Receptacle Connector
Specifying a Route Code for a Slot Connector
Specifying a Bundle (Harness) as a Poke Home
Wires
The source wires from associated Capital Logic designs are listed on the Wiring Browser. After
these wires have been routed along the bundles in the topology diagram, they are displayed
under the Unassigned node in the Design Browser or, if grouped into signals, under the Signals
node.
The wires from the associated Capital Logic designs are automatically routed along the bundles
in the topology design when the devices that they connect have been placed in slots.
The real-world length of the wires is calculated using the Physical Scale of the topology
diagram and is specified as the value of the Wire Length attribute on the Edit Properties: Wire
Dialog. This length can be back annotated to the source wires in the Capital Logic designs. If
you have performed actions that changed bundle lengths, you may need to update the wire
lengths before back annotating them (see “Updating Wire Lengths” on page 607).
Rules and constraints adhere to hierarchies. That means, if they are set on an object, child
objects inherit them. For example, constraints can be set for a diagram so that they are inherited
by all objects on that diagram (in this case, all slots and connectors). See “Setting Constraints
for an Entire Topology Diagram” on page 631.
Procedure
1. Select the object on which you are setting the constraint.
2. Either:
• Press Space Bar and enter Properties
• Right-click on the selected entity and select Properties
• Double-click on the object in the Diagram Window
The Edit Properties dialog for the object is displayed.
3. Click the Rules tab and click the Add Constraint button; the Constraint Selection
dialog is displayed.
4. Select ‘Route by Attribute/Property’ and click OK; the constraint is added to the Edit
Properties dialog.
5. Edit the constraint as required and click OK.
Results
• The constraint is applied when Capital Logic designs are associated with the topology
diagram and when updated data from the Capital Logic design is synchronized with the
topology design.
Related Topics
Wires
Constraints (Capital Topology)
Setting Constraints for an Entire Topology Diagram
Note
You select a route in the ‘Alternative Routes Table / Route to Implement Table /
Routes to Implement Table’ in order to view details of the stages of that route in the
To-Do List Table (See Routing Assistant.
Note
If you click a wire cell or connector cell in the table, a tooltip displays additional
information about it, including links to any instances of that object in either the
Capital Topology diagram or in the associated Capital Logic diagrams. Click the link to
jump to the Capital Logic diagram where the instance of the inline connector needs to be
added.
5. After an inline connector instance is added, you must rename it to the same name as the
inline connector named in the To-Do List Table row for that stage of the route.
Results
• When a stage of a route is completed for a wire in the Capital Logic diagrams, the wire
name in that To-Do List Table row changes from red to black.
• When a stage is complete for all wires, the status column for it displays a tick ( ).
• When all stages are complete for all selected wires, the status column for the route in the
‘Alternative Routes Table / Route to Implement Table / Routes to Implement Table’
displays a tick ( ).
Related Topics
Using the Routing Assistant to Identify all Unrouted Wires that Need to Pass Through a
Selected Inline Connector
Splices in Capital Topology
Procedure
1. In the Design Browser or diagram window, right-click on the inline connector and select
Routing Assistant or click Show Routing Assistant ( ) on the Design Browser or
Wiring Browser; a progress bar indicates that the system is identifying the routes and it
displays the routes for the wires in a Routing Assistant tab in the Output Window. All of
these routes need to be completed.
2. In the ‘Alternative Routes Table / Route to Implement Table / Routes to Implement
Table’, select a route; the To-Do List Table displays the details for the stages of the
selected route. See Routing Assistantfor a detailed description of the information in this
table.
3. For each stage of the route where a wire is displayed in red, you need to add an instance
of the inline connector to an associated Capital Logic design so that the wire passes
through it.
Note
If you click a wire cell in the table, a tooltip displays additional information about it,
including links to any instances of that object in either the Capital Topology diagram
or in the associated Capital Logic diagrams. Click the link to jump to the Capital Logic
diagram where the instance of the inline connector needs to be added.
4. After an inline connector instance is added, you must rename it to the same name as the
inline connector named in the To-Do List Table row for that stage of the route.
Results
• When a stage of a route is completed for a wire in the Capital Logic diagrams, the wire
name in that To-Do List Table row changes from red to black.
• When a stage is complete for all wires following that route, the status column for it
displays a tick ( ).
• When all stages are complete for all wires following that route, the status column for the
route in the ‘Alternative Routes Table / Route to Implement Table / Routes to
Implement Table’ displays a tick ( ).
Related Topics
Using the Routing Assistant to Identify the Possible Routes for an Unrouted Wire
Reporting on All Unrouted Wires that Could Pass Through an Inline Connector
Related Topics
Using the Routing Assistant to Identify all Unrouted Wires that Need to Pass Through a
Selected Inline Connector
Procedure
Press Space Bar and enter Update All Lengths; the wire lengths are updated.
If you are working in multi user mode (see “Harness Concurrency” on page 553 for an
explanation of what this means), this action updates wiring only from locked harnesses and
refreshes the unlocked harnesses before running. It also opens and locks any Capital Logic
designs that need to be updated.
Procedure
With the topology diagram open, press Space Bar and enter Back Annotate.
Results
• The Length value from the topology wires are copied to the attributes of the source wires
in the Capital Logic designs.
• Harness attributes are back-annotated to wires and splices in the Capital Logic designs
with the name of the harness in which the object (wire or splice) is routed in Capital
Topology.
Related Topics
Wires
Edit Properties: Wire Dialog
Splices in Capital Topology
Constraining the Routing of Wires
Viewing the Attributes and Properties of a Wire
Multicores
The multicores from associated Capital Logic designs are listed with their innercore wires on
the Wiring Browser.
After these wires have been routed along the bundles in the topology diagram, the routed
innercore wires are displayed under the Unassigned node in the Design Browser or, if grouped
into Signals, under the Signals node.
The innercore wires from the associated Capital Logic designs are automatically routed along
the bundles in the topology design when the devices that they connect have been placed in slots.
The real-world length of the innercore wires is calculated using the Physical Scale of the
topology diagram and is specified as the value of the Wire Length attribute on the Edit
Properties: Wire Dialog. This length can be back annotated to the source wires in the Capital
Logic designs.
• Splices connecting wires whose paths are mainly on one harness are placed on a bundle
on that harness.
• If the connected wires have paths that are equally distributed across multiple harnesses,
the splice is placed on the first harness from the alphanumerically sorted list of potential
harnesses. It is connected to any appropriate conductors in that harness.
• If none of the connected wires have any paths on the available harnesses, the splice is
left unplaced. This means the connected wires are also not routed.
• If the splice is center-stripped, the path of the center-stripped wire(s) is used to select the
harness.
If Capital Topology has not identified the correct harness for a splice, you can override the
default harness by specifying a Harness attribute for it. When you refresh wiring (or re-
synchronize), the splices will be re-positioned in the specified harness. (see “Specifying the
Harness Attribute for a Splice in Capital Topology” on page 611 and “Synchronizing Wiring
Changes with a Capital Topology Design” on page 565).
You can then run the Design Assistant to identify routing paths for the unrouted wires
connected to these splices. See “Using the Routing Assistant to Identify the Possible Routes for
an Unrouted Wire” on page 604.
You can back-annotate the Harness attribute to the splices in the associated Capital Logic
designs. See “Annotating Topology Wire Lengths and Harness Attributes Back to Logical
Wires and Splices” on page 608.
Procedure
1. Do one of the following:
• Right-click on the object either in the diagram window or in a browser tab at the
bottom left of the application window and select Edit Harness Attribute.
• Click the object, press Space Bar and enter Set Harness Attribute.
2. The Edit Harness Attribute dialog box is displayed. Enter the name of the harness or the
harness group that the object is to be synchronized to. If harness names or harness
groups have been created in Capital Project, you can select one from the drop-down list
in the Harness field.
Results
• When you refresh wiring (or re-synchronize), the splice will be re-positioned in the
specified harness.
• You can then run the Design Assistant to identify routing paths for the unrouted wires
connected to these splices.
Related Topics
Synchronizing Wiring Changes with a Capital Topology Design
Using the Routing Assistant to Identify the Possible Routes for an Unrouted Wire
Annotating Topology Wire Lengths and Harness Attributes Back to Logical Wires and Splices
Inline Pairs
Inline pairs consist of an inline plug connector and an inline receptacle connector (also known
as inline halves).
When placed on a bundle, an inline pair splits the bundle into separate Virtual Harnesses.
There are several factors that are considered when placing inline pairs, the following highlights
some of the possible factors:
• The inline plug connector and inline receptacle connector are listed below the Inlines
node of the Design Browser.
• The inline plug connector and inline receptacle connector are displayed below the
harnesses to which they connect in the Design Browser.
Related Topics
Inline Pairs
Adding a Specific Logical Inline Pair to a Bundle
Editing an Inline Plug Connector or an Inline Receptacle Connector
Specifying a Route Code for an Inline Plug Connector or an Inline Receptacle Connector
Moving an Inline Pair
Deleting an Inline Pair from a Bundle
Toggling the Inline Plug Connector and Inline Receptacle Connector on an Inline Pair
Constraining the Automatic Association of Inline Halves
• The inline plug connector and inline receptacle connector are displayed below the
harnesses to which they connect in the Design Browser.
• An association is created between the logical inline pair and the topology inline pair.
Related Topics
Inline Pairs
Adding an Unassociated Inline Pair to a Bundle
Editing an Inline Plug Connector or an Inline Receptacle Connector
Specifying a Route Code for an Inline Plug Connector or an Inline Receptacle Connector
Moving an Inline Pair
Deleting an Inline Pair from a Bundle
Toggling the Inline Plug Connector and Inline Receptacle Connector on an Inline Pair
Constraining the Automatic Association of Inline Halves
Procedure
1. Select the inline plug connector or an inline receptacle connector to be edited.
2. Either:
• Press Space Bar and enter Properties
• Right-click on the selected entity and select Properties
• Double-click on the inline plug connector or inline receptacle connector in the
Diagram Window
The Edit Properties: Inline Plug Connector Dialog or Edit Properties: Inline Receptacle
Connector Dialog is displayed.
3. Click the Routes tab, specify the Route Code and click OK.
Related Topics
Inline Pairs
Adding an Unassociated Inline Pair to a Bundle
Adding a Specific Logical Inline Pair to a Bundle
Moving an Inline Pair
Deleting an Inline Pair from a Bundle
Toggling the Inline Plug Connector and Inline Receptacle Connector on an Inline Pair
Constraining the Automatic Association of Inline Halves
Related Topics
Inline Pairs
Adding an Unassociated Inline Pair to a Bundle
Adding a Specific Logical Inline Pair to a Bundle
Editing an Inline Plug Connector or an Inline Receptacle Connector
Specifying a Route Code for an Inline Plug Connector or an Inline Receptacle Connector
Deleting an Inline Pair from a Bundle
Toggling the Inline Plug Connector and Inline Receptacle Connector on an Inline Pair
Constraining the Automatic Association of Inline Halves
Results
• The inline pair is deleted from the diagram.
• If there is more than one bundle connected to either side of the inline, it is replaced with
a structure node.
Related Topics
Inline Pairs
Adding an Unassociated Inline Pair to a Bundle
Adding a Specific Logical Inline Pair to a Bundle
Editing an Inline Plug Connector or an Inline Receptacle Connector
Specifying a Route Code for an Inline Plug Connector or an Inline Receptacle Connector
Moving an Inline Pair
Toggling the Inline Plug Connector and Inline Receptacle Connector on an Inline Pair
Constraining the Automatic Association of Inline Halves
should not be associated with particular inline halves in Capital Topology. This constraint can
be applied to inline connectors and harnesses in a topology diagram.
This constraint is not normally required as the default behavior is to associate inline halves with
the same name. This constraint would only be used if you wanted inline halves in Capital Logic
to have different names from inline halves in Capital Topology.
Note
Constraints can be bundled into rules that can be set on objects. See “Rules and Constraints”
on page 469 for further information about creating rules.
Rules and constraints adhere to hierarchies. That means, if they are set on an object, child
objects inherit them. For example, constraints can be set for a diagram so that they are inherited
by all objects on that diagram (in this case, all slots and connectors). See “Setting Constraints
for an Entire Topology Diagram” on page 631.
Procedure
1. Select the object on which you are setting the constraint.
2. Either:
• Press Space Bar and enter Properties
• Right-click on the selected entity and select Properties
• Double-click on the object in the Diagram Window
The Edit Properties dialog for the object is displayed.
3. Click the Rules tab and click the Add Constraint button; the Constraint Selection
dialog is displayed.
4. Select ‘Place Inline Half by Attribute/Property’ and click OK; the constraint is added to
the Edit Properties dialog.
5. Edit the constraint as required and click OK.
Results
• The constraint is applied when Capital Logic designs are associated with the topology
diagram and when updated data from the Capital Logic design is synchronized with the
topology design.
Related Topics
Constraints (Capital Topology)
Setting Constraints for an Entire Topology Diagram
Inline Pairs
• The Signal Mappings tab displays the mapping of signals and wires between the
cavities of connectors on each inline half.
Each row represents a signal and wire mapping between connector cavities on both
halves of the inline.
The table is divided into two sections by the middle column. The fields on either side
of this apply to the connector cavities on either side of the inline.
• The Wire Info tab displays details of the wires connecting to the connectors. Each
row represents a wire.
Related Topics
Inline Pairs
Virtual Harnesses
Virtual harnesses are displayed in the Design Browser. Each virtual harness lists the connectors
and bundles included on it.
Signals
In Capital Topology, you can group wires into a signal based on attribute or property values.
You can constrain the routing of wires in the topology diagram based on the signals that they
carry in the associated Capital Logic designs.
• The slot, slot connectors and inline pairs have the same names as the corresponding
objects on the logical design so that associations will be created automatically.
Prerequisites
• Create a new project to work in for the duration of the example.
• Create a new logical design and diagram, and add the devices, connectors, inline pairs
and wires as shown in Figure 17-1.
• Create a new topology diagram, and add the slots, slot connectors, inline pairs and
bundles as shown in Figure 17-2.
Procedure
1. With the topology diagram open in Capital Logic, press Space Bar and enter Associate
Signals By; the Associate Signals By Attribute or Property Dialog is displayed.
2. Select Property and enter Topo_Signal in the drop-down list box. Click OK.
3. Press Space Bar and enter Associate Logical Designs. The Associate Wiring Designs
Dialog Box is displayed.
4. Select the logical design you created from the Available list, then click Add to move it
into the Associated list. Click OK; the designs are associated. The topology objects are
associated with the logical objects of the same name and the wires are displayed in the
Design Browser, grouped as follows:
Figure 17-3. Wire Grouping Example - Grouped Wires
• Wire -199- is placed under the signal Sig01, which was the value of the
Topo_Signal property on it in the Capital Logic design.
• Wires -200- and -201- are grouped under the signal Sig02, which was the value of
the Topo_Signal property on them in the Capital Logic design.
Related Topics
Grouping Wires into Signals
Signals
Holes
A hole is used to create a direct-to-device connection in Capital Topology.
In a Capital Logic design, this would be modeled by a wire connecting directly to a device pin
(no connector in between). When the device is placed in a slot in a topology diagram, no
connector is created and the system does not know where a connecting signal or wire enters the
slot. In this scenario, you must use a ‘Route by Attribute/Property’ constraint on the connecting
bundle or an ‘Assign Conductor/s to Hole by Attribute/Property’ constraint on the hole itself.
A hole can house one or several different wires and, unlike a connector, does not have cavities.
Editing a Hole
This topic details how to edit the attributes and properties of a hole on a topology diagram.
Procedure
1. Select the hole to be edited.
2. Either:
• Press Space Bar and enter Properties
• Right-click on the selected entity and select Properties
• Double-click on the hole in the Diagram Window
The Edit Properties: Hole Dialog is displayed.
3. Make any changes required to the hole attributes and/or properties.
4. Click OK.
Related Topics
Holes
Adding a Hole to a Slot
Constraining the Mapping of Wires to a Hole on a Slot
Rules and constraints adhere to hierarchies. That means, if they are set on an object, child
objects inherit them. For example, constraints can be set for a diagram so that they are inherited
by all objects on that diagram (in this case, all slots and connectors). See “Setting Constraints
for an Entire Topology Diagram” on page 631.
Procedure
1. Select the hole.
2. Either:
• Press Space Bar and enter Properties
• Right-click on the selected entity and select Properties
• Double-click on the slot in the Diagram Window
The Edit Properties dialog for the object is displayed.
Assemblies
An assembly is a collection of objects that you can use as a single entity in a design. It can
contain wires, shields, nets, devices, connectors, conductor groups and other assemblies.
Although you cannot add an assembly specifically to a Capital Topology design, an associated
Capital Logic design can contain assemblies.
If an object from an assembly is placed in the Capital Topology design, the assembly is listed
under the Assemblies node in the Design Browser.
If no objects from an assembly have been placed, it will not be listed in the Design Browser.
Allows you to specify that a property or attribute must be set to a particular value on objects of
a particular type when they have another property or attribute with a particular value. The
property/attribute and value are assigned to the object when you select the Set Attribute/
Property action from the ribbon in Capital Topology. The Object that breaks attribute/
property rule design rule check can be run to check for objects that violate this constraint.
For further information, see “Using a Constraint to Set an Attribute or Property on an Object”
on page 632 and “Applying the Set Topology Attribute/Property on Object Constraint” on
page 633.
Placement
Various Placement constraints are available.
This is applied when you place devices attached to harness connectors in slots. It allows you to
control whether a harness connector with a particular value for an attribute or property is
mapped to a slot connector with an attribute or property that has the same value.
This constraint is not normally required as the default behavior is to associate connectors with
the same name. This constraint would only be used if you wanted harness connectors in Capital
Logic to have different names from slot connectors in Capital Topology.
For further information on using this constraint, see “Constraining the Association of Logical
Harness Connectors to Slot Connectors” on page 588.
Place by Attribute/Property
Default: Do place devices with attribute/property matching Name = Slot Name
Allows you to specify whether objects with a particular property or attribute should or cannot be
placed in a slot. The system obeys this rule when automatically placing objects.
By default, the Place by Attribute/Property constraint is set for a topology diagram and is
inherited by any slots. The default setting forces devices to be placed in slots with the same
name. This default setting can be edited or removed.
For further information on using this constraint, see “Constraining the Placement of Devices in
a Slot” on page 579 and “Manually Placing a Device in a Slot” on page 580.
Allows you to specify whether inline halves with a particular property or attribute (from Capital
Logic) should or should not be associated with particular inline halves in Capital Topology. The
system obeys this rule when automatically placing objects. This constraint can apply to inline
connectors, harnesses and diagrams.
This constraint is not normally required as the default behavior is to associate inline halves with
the same name. This constraint would only be used if you wanted inline halves in Capital Logic
to have different names from inline halves in Capital Topology.
For further information on using this constraint, see “Constraining the Automatic Association of
Inline Halves” on page 618.
Routing
Various Routing constraints are available.
Allows you to specify whether conductors with a particular property or attribute are or are not
mapped to a particular hole on a slot. This constraint can apply to a hole.
For further information on using this constraint, see “Holes” on page 625 and “Constraining the
Mapping of Wires to a Hole on a Slot” on page 626.
Allows you to specify the minimum distance that there must be between a splice and a
connector, splice or takeout. This can be set so that it only applies if a splice has an attribute or
property with a particular value. This can be set on an entire diagram, on a bundle or on a
harness.
For further information on using this constraint, see “Constraining the Placement of Splices on a
Bundle” on page 599.
Allows you to specify whether splices with a particular property or attribute should or cannot be
placed on a bundle. The system obeys this rule when automatically placing objects. This
constraint can apply to bundles, harnesses and diagrams.
For further information on using this constraint, see “Constraining the Placement of Splices on a
Bundle” on page 599.
Route by Attribute/Property
Default: Don’t route conductors with attribute/property matching Name = Value here
Allows you to specify whether conductors with a particular property or attribute can or cannot
be routed along a bundle, along a harness or through an inline pair. This constraint can apply to
bundles, inline connectors, harnesses and diagrams.
For further information on using this constraint, see “Constraining the Routing of Wires” on
page 603.
Related Topics
Setting Constraints for an Entire Topology Diagram
Procedure
1. On the Design Browser, click the Set Rules and Constraints ( ) button; the Edit
Properties: Diagram Dialog is displayed.
2. Add any rules and Constraints (Capital Topology) to the ‘Object Rule Rule Contents:’
window and click OK.
Results
• The constraints are inherited by objects on the diagram.
• The constraints are applied when actions are performed on the topology diagram.
Related Topics
Constraints (Capital Topology)
Procedure
1. Select the object.
2. Either:
• Press Space Bar and enter Properties
• Right-click on the selected entity and select Properties
• Double-click on the object
The Edit Properties dialog for the object is displayed.
3. Click the Rules tab and click the Add Constraint button; the Constraint Selection
dialog is displayed.
4. Select ‘Set Integrator/Topology Attribute/Property on Object’ and click OK; the
constraint is added to the Edit Properties dialog.
5. Edit the constraint as required and click OK.
Results
• When you use the Set Attribute/Property action, the attribute or property value is set on
the object.
Related Topics
Constraints (Capital Topology)
Setting Constraints for an Entire Topology Diagram
Applying the Set Topology Attribute/Property on Object Constraint
Results
• The attribute and property values on objects on the topology diagram are updated based
on the constraints.
Related Topics
Constraints (Capital Topology)
Setting Constraints for an Entire Topology Diagram
Using a Constraint to Set an Attribute or Property on an Object
Harness Report
This creates a summary report in HTML format detailing all of the design objects (and their
measurements) that are located on the currently active topology diagram.
Related Topics
Creating a Harness Report for a Topology Diagram
Note
Select the Open in Browser option if you want the report to be opened
automatically in a browser window.
Related Topics
Harness Report
You can save the report in comma separated variable (CSV) format. The enables the report to be
opened into applications such as MS Excel.
Related Topics
Creating a Material Statistic Report
Related Topics
Creating a Bundle Wires Report for a Bundle Section
Copying the Bundle Wires Report
Clearing the Bundle Wires Report
Note
You can also copy sub-sections of the report by highlighting the appropriate sections
with your mouse and selecting Copy before pasting into the other application.
Related Topics
Bundle Wires Report
Results
• The Bundle tab is cleared.
Related Topics
Bundle Wires Report
Creating a Bundle Wires Report for a Bundle Section
Copying the Bundle Wires Report
• Harness
Specifies the name of the harness to which the object belongs if appropriate.
• Object Name
Specifies the name of the object.
• Object Type
Specifies the type of object.
• Constraint Type
Specifies whether the constraint is standard (STANDARD) or customized (CUSTOM).
• Constraint
The constraint that has been applied to the object. If multiple constraints have been
applied to an object, the object is listed multiple times. If a constraint was applied via a
rule (that is, the rule was referenced rather than adding a constraint directly, then the
entry in this column starts with the rule name and a colon.
Related Topics
Creating an Applied Constraints Report for a Topology Diagram
Note
Select Open in Browser or Spreadsheet if you want the report to open
automatically when it is generated.
Related Topics
Applied Constraints Report
• Part Number
The part number of the library component.
• Quantity
The number of times the library part is used on the selected design(s).
Related Topics
Creating a Component BOM Report for a Topology Diagram
Note
To save the report in HTML format, click Save Report. To print the report, click
Print.
Related Topics
Component BOM Report
• Name
The unique identifier for the multicore within the diagram.
• Design
The design upon which the multicore appears.
• Part Number
The part number of any library part associated with the multicore.
• Multicore Contents
A listing of the wires and child multicores assigned to the multicore.
• Multicore Parent
If a multicore is nested as a child of another multicore, the parent “containing” multicore
is listed here.
Related Topics
Creating a Multicore List Report for a Topology Diagram
Note
To save the report in HTML format, click Save Report. To print the report, click
Print.
Related Topics
Multicore List Report
For further information see Using the Report Builder in the Capital Design Tools - Common
Functions User Guide for full details.
Metrics
The Metrics or Insight tab at the bottom left of the application window supplies metrics that can
be run against the open design.
For a full description of this functionality, see Capital Insight in the Capital Design Tools -
Common Functions User Guide.
For a full list of the design rule checks available for use in Capital Topology, see Design Rule
Checks Applicable to Capital Topology Designs in the Capital Design Tools - Common
Functions User Guide.
Related Topics
Design Rule Checks (Capital Topology)
Design Assistant
Related Topics
Associating Logical Designs with the Topological Design
Related Topics
Grouping Wires into Signals
Related Topics
Associating Logical Designs with the Topological Design
Replacing a Logical Design Association
Logical Design Association
Concurrency Tab
The Concurrency tab to the left of the application window is used with harness concurrency
functionality. The tab shows information on the design, harnesses, slots and their lock state and
allows you to lock and unlock objects.
See “Harness Concurrency” on page 553 for more information about this functionality.
Related Topics
Reporting on All Unrouted Wires that Could Pass Through an Inline Connector
Design Assistant
Accessed by pressing Space Bar and entering Design Assistant.
Also displayed when you click the Refresh Wiring ( ) button on the Concurrency Tab,
Design Browser or Wiring Browser.
The Design Assistant is displayed as a tab in the Output Window. It can be used to run selected
design rule checks or to view or wiring synchronization messages.
• Save to CSV
Saves the content of the Design Assistant Output Table as a comma separated variable
(CSV) file. A dialog is displayed where you specify the file name and where you want to
save it.
• Run Checks
Runs the design rule checks that are set to run in the Design Assistant. The results of the
checks are displayed in the Design Assistant Output Table. You can specify which
checks are run by clicking Configure Checks ( ).
• Configure Checks
Opens the Project Preferences dialog where you specify which design rule checks are
run by the Design Assistant. See Project Preferences.
• Design Assistant Output Table
The table includes columns in which you can filter the contents by selecting an item
from the dropdown list at the top. It can be cleared by right-clicking on the tab and
selecting Clear. You can also filter some columns by typing a string into the box in the
column header. This allows you to filter on partial words, and so on.
You can sort the contents of a column by clicking the column header. The columns are:
o Severity
Whether the result is an error ( ), a warning ( ), an information message ( ), or a
summary.
o Message
Detailed message about what the check or wiring synchronization action has
identified. You can click an object in the message to jump to that object in the
diagram window.
o Category
The category of design rule check to which the particular design rule check belongs
(for example, Connectivity, Naming, and so on). If the wiring synchronization
action has been performed, Sync is displayed.
o Check
The specific design rule check or wiring synchronization action that has identified
something in the design.
o Design
The design in which the check or wiring synchronization action has identified
something/
o Object
The specific object for which the check or wiring synchronization action has
identified something.
Related Topics
Running Design Rule Checks in the Design Assistant
Related Topics
Editing a Capital Topology Design
Related Topics
Specifying the Physical Scale of a Capital Topology Diagram
Related Topics
Editing a Capital Topology Diagram
Related Topics
Viewing the Attributes and Properties for an Assembly
• Editing a Bundle
• Adding a Bundle to a Diagram
• Moving a Bundle Section
• Deleting a Bundle Section
• Deleting an Entire Bundle
Related Topics
Editing a Bundle
Specifying the Physical Length of a Bundle
Specifying Variant Physical Lengths for a Bundle
Related Topics
Viewing the Attributes and Properties for a Device Connector
Related Topics
Editing a Hole
Table 17-14. Edit Properties: Inline Plug Connector Dialog Contents (cont.)
Field Description
Properties To add a property to the inline plug connector, click the New
button, enter a Property Name in the New Property Dialog,
then click OK. The new property is added to the list. A property
consists of the following fields:
• Name
A unique identifier for the property. Read-only.
• Value
The value assigned to the property. Optional.
• Type
The data type of the value. Mandatory. If you enter a Value
that is not supported by the selected Type, the Value is
displayed in red text and the OK button is disabled. The
following types are available:
• String
A mix of letters, number or special characters.
• Integer
A whole number.
• Float
A number including a decimal (floating) point.
To delete a property from the list, select it and click the Delete
button, then click OK to confirm the deletion. Optional.
Attributes Specify the values for inline plug connector attributes in the
Value column. Select the Visible option to display the attribute
value next to the slot on the topology diagram. Click to
display the Edit Graphical Attributes dialog where you can
specify how the value is displayed on the diagram (see “Editing
Text Attributes for an Object” on page 439). Mandatory.
Library Part Specifies whether a library part is associated with the inline
plug connector. Click Add to associate a library part using the
Part Selection Dialog. Click Update to update the library part
information if changes have been to the part in Capital Library.
Click Remove to cancel the association of the library part.
Click View to display the Details Dialog for the library part.
Optional.
Graphical Tab Specify how you want the inline plug connector graphic to
appear on the topology diagram.
Table 17-14. Edit Properties: Inline Plug Connector Dialog Contents (cont.)
Field Description
Primary Color Specify the color of the lines of the inline plug connector.
Select the color from the dropdown list; it is previewed in the
window to the right of the field. As well as color names, the list
contains the following options:
• Default
The default color used for the object by the system.
• Background
The same color used for the background of the diagram. The
color changes when the background color is toggled.
• Foreground
If the diagram background is white, the object is black, and
vice versa.
• Manual
The Choose Object Color dialog is displayed, where you
can select a color.
Mandatory.
Table 17-14. Edit Properties: Inline Plug Connector Dialog Contents (cont.)
Field Description
Thickness Specify the thickness of the lines of the graphical shape.
Mandatory. To use the default thickness, select Default from
the dropdown list.
To use a different thickness, select Override from the first
dropdown list and select the type of thickness from the final
dropdown list:
• Logical
These thicknesses do not have a physical unit of
measurement. They provide a logical progression of
thickness with a default of 1. A line with thickness 2 is
displayed twice as thick as a line with thickness 1, and so
on. When you zoom in or out of a diagram, the line
thickness does not appear any different.
You select the thickness from the middle dropdown list.
• Physical (unit of measurement)
The physical unit of measurement that has been specified as
the Unit in the style set applied to the diagram. The line
thickness is displayed in relation to the grid size of a
diagram. When you zoom in or out of a diagram, the line
grows or shrinks to stay in scale with the grid.
When you select a unit, the middle dropdown list changes to
a free text field where you specify the thickness. The value
can be any floating-point number up to three decimal
places.
See Physical Line Thickness in the Capital Design Tools -
Common Functions User Guide for a definition and links to
related task flows.
Line Style Specify the style of the lines of the inline plug connector. To
use the default style, select Default from the dropdown list; to
use a different style, select Override from the dropdown list
and select the style from the second dropdown list that is
displayed. Mandatory.
Rules Tab
Table 17-14. Edit Properties: Inline Plug Connector Dialog Contents (cont.)
Field Description
Show Inherited Specifies what is displayed in the ‘Object Rule Rule Contents:
window’.
Select this if you want to display all constraints that apply to the
inline plug connector, including constraints that have been set
for the whole diagram and constraints included in rules that
have been added to the slot. Note that you cannot edit the
constraints when this option is selected.
Do not select this if you want to display only the rules added to
the slot and constraints that have been set specifically for the
slot. Mandatory.
Object Rule Rule Contents: Displays the Constraints (Capital Topology) that apply to the
Window inline plug connector. Optional.
If Show Inherited is selected, you cannot edit any of the
constraints.
If Show Inherited is not selected, you can edit the individual
constraints added to the inline plug connector but not the rules.
A rule is indicated by and you can click to display the
constraints in that rule (in read-only mode).
A constraint is indicated by . Red text indicates a value that
either must be edited or is invalid. Green text indicates editable
text.
Add Rule Ref Displays the Rule Selection dialog from which you can select a
rule that you want to apply to the inline plug connector. The
selected rule is added to the ‘Object Rule Rule Contents:
window’. Optional.
Add Constraint Displays the Constraint Selection dialog from which you can
select a constraint that you want to add to the inline plug
connector. The selected constraint is added to the ‘Object Rule
Rule Contents: window’ where you can edit it. Optional.
Routes Tab Used to specify:
• the route code for the connector. If there are multiple
harnesses entering the connector, you can specify a different
route code for the connector on each harness.
• whether bundles entering the connector are poke home
bundles.
Harness The name of the harness entering the connector. Read-only.
Connector The name of the connector. Read-only.
Bundle The name of the harness bundle entering the connector. Read-
only.
Table 17-14. Edit Properties: Inline Plug Connector Dialog Contents (cont.)
Field Description
Route Code The route code used to distinguish between connectors, for
example, when there is more than one slot connector combined
with a slot. It is not used in Capital Topology but it is used in
Capital HarnessXC.
If no route codes have been defined for the library part or no
library part is assigned, you can manually specify a route code
for the connector when on the harness specified in this row.
Optional.
If route codes have been defined for the library part used for the
connector, this field is not editable and displays the appropriate
code from the library part. Read-only.
Poke Home Whether the bundle specified in this row is a poke home bundle
(selected) or not (unselected). Mandatory.
Related Topics
Editing an Inline Plug Connector or an Inline Receptacle Connector
Specifying a Route Code for an Inline Plug Connector or an Inline Receptacle Connector
Specifying a Bundle (Harness) as a Poke Home
Related Topics
Editing an Inline Plug Connector or an Inline Receptacle Connector
Specifying a Route Code for an Inline Plug Connector or an Inline Receptacle Connector
Specifying a Bundle (Harness) as a Poke Home
Related Topics
Viewing the Attributes and Properties of a Multicore
Related Topics
Setting Constraints for an Entire Topology Diagram
Constraints (Capital Topology)
Related Topics
Editing a Slot
Related Topics
Editing a Slot Connector
Specifying a Route Code for a Slot Connector
Specifying a Bundle (Harness) as a Poke Home
Related Topics
Editing a Virtual Harness
Related Topics
Viewing the Attributes and Properties of a Wire
Related Topics
Adding a Skeleton to a Topology Diagram
Removing a Skeleton from a Topology Diagram
In this example:
• The Totals row shows the total number of objects in the diagram as a
whole. That is, 56 connectors, 12 inlines, 11 splices, and so on.
• The top BODY row shows the total number of objects on the BODY
base harness regardless of harness levels. That is, 12 connectors, 1
inline, 1 splice, and so on.
• The other BODY rows show the total number of objects on particular
harness levels for the BODY base harness. For the _US-SP1 level,
there are 6 non-inline connectors. In other words, there are 6 slot slot
connectors or interface connectors populated for this harness level.
• By Option
In addition to the totals for the whole diagram, the report contains
lines for each base harness and is further divided by option.
In this example, you can see that 1 wire with the WireColor value U/P is
used in total and that 3 wires with the WireColor value G are used in the
BODY LH base harness.
Generate Generates the report table.
Save Report File Displays the Material Statistics Report dialog that allows you to save
the report as a CSV file.
Related Topics
Creating a Material Statistic Report
Related Topics
Creating a Capital Topology Design
Related Topics
Creating a Capital Topology Diagram
Related Topics
Manually Placing a Device in a Slot
Design Browser
This tab, labelled Design and located on the lower-left side of the application window, is
displayed when a topology diagram is active in the diagram window. It lists all topological and
harness objects present on the topology diagram, grouped into folders by object type.
Note
You can hide the Design Browser (and the Project Browser Window) by pressing Space Bar
and entering Toggle Browser Area. You can return it in the same way.
Table 17-28. Signal Map Dialog Box for Inline Pair Contents
Field Description
Connector Mating Table Displays each half of the inline pair. The table is split into
two sections by the middle column. The fields on either side
of this represent the two halves of the inline pair.
To select which columns you want displayed in the table,
right-click on a column header and select/unselect the
column names as required.
Connector A unique identifier for the inline half.
Part Number The library part of the inline half (if a library part has been
selected).
No. of Cavities Specifies the number of cavities on the inline half.
Signal Mappings tab Displays the mapping of signals and wires between the
cavities of connectors on each inline half.
Each row represents a signal and wire mapping between
connector cavities on both halves of the inline.
The table is divided into two sections by the middle column.
The fields on either side of this apply to the connector
cavities on either side of the inline.
Status Column (blank column Displays an error or warning symbol if there is an issue with
header) the mapping. Move your mouse over the symbol to view a
brief description of the issue.
Connector Displays the name of a connector used for the inline half.
Cavity Displays the name of a cavity or backshell termination ( )
on the connector in the Connector column.
Harness Displays the name of the harness owning the connector in
the Connector column.
Signal Specifies the signal travelling between the connector
cavities from the Cavity columns.
Wire Displays the wire that is carrying the signal and is mapped
to the connector cavity in the Cavity column.
Table 17-28. Signal Map Dialog Box for Inline Pair Contents (cont.)
Field Description
Wire Info tab Displays details of the wires connecting to the connectors
from the Connector Mating Table. Each row represents a
wire.
If no connector is selected in the Connector Mating Table,
all wires connecting to all of the connectors are displayed.
If a connector is selected in one half of the Connector
Mating table, wires connecting to only that connector are
displayed.
If you click the Select both halves ( ) symbol in the
middle of the Connector Mating table, both connectors are
selected and all wires connecting to both of them are
displayed.
You can right-click on a row for a wire and select
Properties to view the properties for the wire, including its
library part.
To sort the table rows based on the contents of a column,
click on the column header.
To select which columns you want displayed in the table,
right-click on a column header and select/unselect the
column names as required.
Status Column Displays an error or warning symbol if there is an issue with
the wire. Move your mouse over the symbol to view a brief
description of the issue.
Harness The harness to which the wire belongs.
Connector/Hole The connector to which the wire is connected.
Cavity/Backshell The connector cavity or backshell through which the wire
passes.
Signal The signal carried by the wire.
Wire The name of the wire.
Part The library part assigned to the wire.
Spec The specification of the wire.
Material The material of the wire.
Color The color of the wire.
Variant The variant option expression for a variant wire.
Option Expression The option expression on the wire.
Module Code The module code of the wire.
Table 17-28. Signal Map Dialog Box for Inline Pair Contents (cont.)
Field Description
To The object and pin to which the wire connects at the other
end.
Related Topics
Viewing the Signal Map for an Inline Pair
Related Topics
Viewing the Signal Map for a Slot
Routing Assistant
The Routing Assistant is displayed as a tab in the Output Window. It identifies possible routes
for selected/identified unrouted wires. These routes may or may not be complete.
If they are incomplete, the To-Do List Table identifies where an inline connector instance is
required in the associated Capital Logic diagrams to complete the route.
• selecting one or more unrouted wires, for which you want to identify possible routes,
right-clicking on a selected wire, and selecting Routing Assistant or clicking Show
Routing Assistant ( ) on the Design Browser or Wiring Browser.
• right-clicking on an inline connector, for which you want to identify the currently
unrouted wires whose routes could be completed by adding instances of this inline
connector to the Capital Logic designs, and selecting Routing Assistant or clicking
Show Routing Assistant ( ) on the Design Browser or Wiring Browser.
o Status
Indicates whether a route is completely implemented ( ) or not ( ).
o Length
The total length of the route (calculated as the sum of all bundle lengths along the
route).
o Inlines
The number of inline connectors along the route.
o Harnesses
The harnesses through which the route passes.
o Wires
The number of currently unrouted wires that are consumed by this route.
• To-Do List Table
Displays details for each stage of the possible route selected in the ‘Alternative Routes
Table / Route to Implement Table / Routes to Implement Table’.
The From cell in the top row indicates the connector where the wire starts and the To
cell in the bottom row indicates the connector where the wire ends. Both of these
connectors already exist in the associated Capital Logic designs and the wire already
starts and terminates at those points.
Any connectors in the other From and To cells do not currently exist for the selected/
identified wires in the associated Capital Logic designs. That means, instances of the
connector may or may not exist in those designs but the wires do not currently pass
through any of them.
You can reverse the order in which the stages of this route are displayed in this table by
clicking Reverse Route.
To complete the route, you must add an inline instance through which the wire passes.
o Status
Indicates whether this stage of the route is complete ( ) or not ( ).
o From
Displays the name of the connector at the start of this stage of the route. If the
connector is mated to a device, the device name is also displayed.
Red text indicates that an action is required. Either:
• The connector does not exist (is missing) and must be added to an associated
Capital Logic design.
• There is at least one wire in this row of the table that does not terminate at the
connector yet.
If you click a connector cell in the table, a tooltip displays additional information
about it, including:
• links to any instances of that object in either the Capital Topology diagram or in
the associated Capital Logic diagrams. Click the link to jump to that instance in
the diagram window
• A Spec. table lists the gauges of the unrouted wires that could pass through this
connector. You can use the report to identify whether the selected connector is
big enough to house all of the wires.
Spec.
The different gauges of the unrouted wires.
Cavities
The number of available cavities on the connector that support the gauge.
Wires
The number of unrouted wires with this gauge that could pass through the inline.
o Available Cavities
Displays the number of available cavities on the From connector. If the connector
does not currently exist, Missing is displayed.
o To
Displays the name of the connector at the end of this stage of the route. If the
connector is mated to a device, the device name is also displayed.
Red text indicates that an action is required. Either:
• The connector does not exist (is missing) and must be added to an associated
Capital Logic design.
• There is at least one wire in this row of the table that does not terminate at the
connector yet.
If you click a connector cell in the table, a tooltip displays additional information
about it, including:
• links to any instances of that object in either the Capital Topology diagram or in
the associated Capital Logic diagrams. Click the link to jump to that instance in
the diagram window
• A Spec. table lists the gauges of the unrouted wires that could pass through this
connector. You can use the report to identify whether the selected connector is
big enough to house all of the wires.
Spec.
The different gauges of the unrouted wires.
Cavities
The number of available cavities on the connector that support the gauge.
Wires
The number of unrouted wires with this gauge that could pass through the inline.
o Available Cavities
Displays the number of available cavities on the To connector. If the connector does
not currently exist, Missing is displayed.
o Wires to be Routed
A column is displayed for each selected or identified wire following the route. If the
wire has been assigned to a signal in the Capital Topology design, the signal name is
displayed as the column name. Otherwise, the wire name is displayed as the column
name.
The formatting of the cells in these columns offer guidance on what you need to do:
• No text and a white background indicates that, for a signal, no wire belonging to
that signal is connected to either connector in that stage of the route.
• Black text on a white background indicates that the wire is fully routed and
connected in that stage of the route.
• Red text indicates that only one end of the wire is connected in that stage of the
route. A colored background indicates that connecting this wire in this stage is a
suggested next step. A white background indicates that connecting this wire is
not a suggested next step, although it must be done at some point.
It is suggested that you work down and then across the columns when connecting the
wires.
When connectors and wires are created in Capital Logic, this table updates to reflect
the changes.
If you click a wire or connector cell in the table, a tooltip displays additional
information about it, including links to any instances of that object in either the
Capital Topology diagram or in the associated Capital Logic diagrams. Click the
link to jump to that instance in the diagram window.
Related Topics
Using the Routing Assistant to Identify the Possible Routes for an Unrouted Wire
Using the Routing Assistant to Identify all Unrouted Wires that Need to Pass Through a
Selected Inline Connector
Indicates that the splices are not visible in the diagram and will not be visible if you
print or output to PDF/DXF/CGM. Click this to make them visible.
Indicates that the splices are visible in the diagram. You can use style sets to
determine how their appearance is styled. See “Styling Objects” on page 68.
If you print to PDF, DXF or CGM with the diagram open, the splices are printed
exactly as seen on the diagram. If the diagram is closed when you print, the splices
are not printed.
Click this to hide them in the diagram.
Note
The toggle splice visibility state is not persisted.
Objects
Related Topics
Specifying Variant Physical Lengths for a Bundle
Wiring Browser
This tab, labelled Wiring and located on the lower-left side of the application window, is
displayed when a topology diagram is active in the diagram window.
Each object entry in the design browser offers all of the right-
click options available to the object on the diagram.
Hovering your mouse over a device displays a tooltip that
indicates the Capital Logic design from which it comes.
Enter Filter String box Enter a series of characters. A filter is applied to the Wiring
Browser so that only objects with names containing that
series of characters are listed.
Show all objects / Show Show all objects
remaining objects / Show All harness objects present on the associated Capital Logic
completed objects designs are displayed in the Wiring Browser.
Show remaining objects
Only harness objects that are not yet associated with a an
object on the topology diagram are displayed in the Wiring
Browser.
Show completed objects
Only harness objects that are associated with a an object on
the topology diagram are displayed in the Wiring Browser.
Note
You can hide the Wiring Browser (and the Project Browser Window) by pressing Space Bar
and entering Toggle Browser Area. You can return it in the same way.
Full details on how to bridge data in and out of Capital and use the bridges and their
functionality is contained within the Bridging Data In and Out of Capital User Guide.
Bridges are applications that permit the exchange of design data between Capital and other
enterprise design systems using either intermediate file transfer or by direct connection.
Bridges Overview
The Bridges provide two generic functions:
• Bridge Out - the exportation of Capital design or build list data in a format acceptable to
third party design systems.
• Bridge In - the re-importation of design or build list data, that was previously authored
and bridged out from Capital and since modified, using a third-party design system.
File translators, known as the Bridges (that are specific to each third-party design system),
automatically re-format the outgoing and incoming design data to the specific format required
by each system.
During the bridge out procedures, design data is initially extracted from Capital as an X2ML
formatted file. X2ML is the Capital 3D Wiring proprietary XML-based format that is used by
the bridges to create a suitably formatted design file for the various third-party design systems.
For example, when using the CATIA V5 Electrical Adaptor, the Capital design data is initially
(and invisibly) exported using the X2ML format before being automatically re-formatted to a
Dassault Systèmes iXF formatted XML file.
Conversely, whenever a third-party design system's design file is bridged into Capital, the
Bridges automatically convert the file to the X2ML format prior to importing the design data
into Capital.
Note
Before you can use Bridges the bridge types that you wish to utilize, and hence wish to
appear in the Files of Type list in the Bridge Data In/Bridge Data Out dialogs, must be
un-commented in the 1- Adaptors declarations section of the adaptors.xml file. Once un-
commented, the same adaptors will appear in all applicable Capital product bridge lists. For
guidance see the Usage Example - Modifying the Adaptors.xml File.
For further information, see the Bridging Data In and Out of Capital User Guide.
Associate
Index
Third-Party Information Section in the Capital Design Tools - Common Functions User Guide. For last minute additions to
this information refer to the latest Capital Release Highlights document.
End-User License Agreement
The latest version of the End-User License Agreement is available on-line at:
www.mentor.com/eula
IMPORTANT INFORMATION
USE OF ALL SOFTWARE IS SUBJECT TO LICENSE RESTRICTIONS. CAREFULLY READ THIS LICENSE
AGREEMENT BEFORE USING THE PRODUCTS. USE OF SOFTWARE INDICATES CUSTOMER’S 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.
This is a legal agreement concerning the use of Software (as defined in Section 2) and hardware (collectively “Products”)
between the company acquiring the Products (“Customer”), and the Mentor Graphics entity that issued the corresponding
quotation or, if no quotation was issued, the applicable local Mentor Graphics entity (“Mentor Graphics”). Except for license
agreements related to the subject matter of this license agreement which are physically signed by Customer and an authorized
representative of Mentor Graphics, this Agreement and the applicable quotation contain the parties’ entire understanding
relating to the subject matter and supersede all prior or contemporaneous agreements. If Customer does not agree to these
terms and conditions, promptly return or, in the case of Software received electronically, certify destruction of Software and all
accompanying items within five days after receipt of Software and receive a full refund of any license fee paid.
1.1. To the extent Customer (or if agreed by Mentor Graphics, Customer’s appointed third party buying agent) places and Mentor
Graphics accepts purchase orders pursuant to this Agreement (each an “Order”), each Order will constitute a contract between
Customer and Mentor Graphics, which shall be governed solely and exclusively by the terms and conditions of this Agreement,
any applicable addenda and the applicable quotation, whether or not those documents are referenced on the Order. Any
additional or conflicting terms and conditions appearing on an Order or presented in any electronic portal or automated order
management system, whether or not required to be electronically accepted, will not be effective unless agreed in writing and
physically signed by an authorized representative of Customer and Mentor Graphics.
1.2. Amounts invoiced will be paid, in the currency specified on the applicable invoice, within 30 days from the date of such invoice.
Any past due invoices will be subject to the imposition of interest charges in the amount of one and one-half percent per month
or the applicable legal rate currently in effect, whichever is lower. Prices do not include freight, insurance, customs duties, taxes
or other similar charges, which Mentor Graphics will state separately in the applicable invoice. Unless timely provided with a
valid certificate of exemption or other evidence that items are not taxable, Mentor Graphics will invoice Customer for all
applicable taxes including, but not limited to, VAT, GST, sales tax, consumption tax and service tax. Customer will make all
payments free and clear of, and without reduction for, any withholding or other taxes; any such taxes imposed on payments by
Customer hereunder will be Customer’s sole responsibility. If Customer appoints a third party to place purchase orders and/or
make payments on Customer’s behalf, Customer shall be liable for payment under Orders placed by such third party in the event
of default.
1.3. All Products are delivered FCA factory (Incoterms 2010), freight prepaid and invoiced to Customer, except Software delivered
electronically, which shall be deemed delivered when made available to Customer for download. Mentor Graphics retains a
security interest in all Products delivered under this Agreement, to secure payment of the purchase price of such Products, and
Customer agrees to sign any documents that Mentor Graphics determines to be necessary or convenient for use in filing or
perfecting such security interest. Mentor Graphics’ delivery of Software by electronic means is subject to Customer’s provision
of both a primary and an alternate e-mail address.
2. GRANT OF LICENSE. The software installed, downloaded, or otherwise acquired by Customer under this Agreement, including any
updates, modifications, revisions, copies, documentation, setup files and design data (“Software”) are copyrighted, trade secret and
confidential information of Mentor Graphics or its licensors, who maintain exclusive title to all Software and retain all rights not
expressly granted by this Agreement. Except for Software that is embeddable (“Embedded Software”), which is licensed pursuant to
separate embedded software terms or an embedded software supplement, Mentor Graphics grants to Customer, subject to payment of
applicable license fees, a nontransferable, nonexclusive license to use Software solely: (a) in machine-readable, object-code form
(except as provided in Subsection 4.2); (b) for Customer’s internal business purposes; (c) for the term of the license; and (d) on the
computer hardware and at the site authorized by Mentor Graphics. A site is restricted to a one-half mile (800 meter) radius. Customer
may have Software temporarily used by an employee for telecommuting purposes from locations other than a Customer office, such as
the employee’s residence, an airport or hotel, provided that such employee’s primary place of employment is the site where the
Software is authorized for use. Mentor Graphics’ standard policies and programs, which vary depending on Software, license fees paid
or services purchased, apply to the following: (a) relocation of Software; (b) use of Software, which may be limited, for example, to
execution of a single session by a single user on the authorized hardware or for a restricted period of time (such limitations may be
technically implemented through the use of authorization codes or similar devices); and (c) support services provided, including
eligibility to receive telephone support, updates, modifications, and revisions. For the avoidance of doubt, if Customer provides any
feedback or requests any change or enhancement to Products, whether in the course of receiving support or consulting services,
evaluating Products, performing beta testing or otherwise, any inventions, product improvements, modifications or developments made
by Mentor Graphics (at Mentor Graphics’ sole discretion) will be the exclusive property of Mentor Graphics.
3. BETA CODE.
3.1. Portions or all of certain Software may contain code for experimental testing and evaluation (which may be either alpha or beta,
collectively “Beta Code”), which may not be used without Mentor Graphics’ explicit authorization. Upon Mentor Graphics’
authorization, Mentor Graphics grants to Customer a temporary, nontransferable, nonexclusive license for experimental use to
test and evaluate the Beta Code without charge for a limited period of time specified by Mentor Graphics. Mentor Graphics may
choose, at its sole discretion, not to release Beta Code commercially in any form.
3.2. If Mentor Graphics authorizes Customer to use the Beta Code, Customer agrees to evaluate and test the Beta Code under normal
conditions as directed by Mentor Graphics. Customer will contact Mentor Graphics periodically during Customer’s use of the
Beta Code to discuss any malfunctions or suggested improvements. Upon completion of Customer’s evaluation and testing,
Customer will send to Mentor Graphics a written evaluation of the Beta Code, including its strengths, weaknesses and
recommended improvements.
3.3. Customer agrees to maintain Beta Code in confidence and shall restrict access to the Beta Code, including the methods and
concepts utilized therein, solely to those employees and Customer location(s) authorized by Mentor Graphics to perform beta
testing. Customer agrees that any written evaluations and all inventions, product improvements, modifications or developments
that Mentor Graphics conceived or made during or subsequent to this Agreement, including those based partly or wholly on
Customer’s feedback, will be the exclusive property of Mentor Graphics. Mentor Graphics will have exclusive rights, title and
interest in all such property. The provisions of this Subsection 3.3 shall survive termination of this Agreement.
4. RESTRICTIONS ON USE.
4.1. Customer may copy Software only as reasonably necessary to support the authorized use. Each copy must include all notices
and legends embedded in Software and affixed to its medium and container as received from Mentor Graphics. All copies shall
remain the property of Mentor Graphics or its licensors. Except for Embedded Software that has been embedded in executable
code form in Customer’s product(s), Customer shall maintain a record of the number and primary location of all copies of
Software, including copies merged with other software, and shall make those records available to Mentor Graphics upon
request. Customer shall not make Products available in any form to any person other than Customer’s employees and on-site
contractors, excluding Mentor Graphics competitors, whose job performance requires access and who are under obligations of
confidentiality. Customer shall take appropriate action to protect the confidentiality of Products and ensure that any person
permitted access does not disclose or use Products except as permitted by this Agreement. Customer shall give Mentor Graphics
written notice of any unauthorized disclosure or use of the Products as soon as Customer becomes aware of such unauthorized
disclosure or use. Customer acknowledges that Software provided hereunder may contain source code which is proprietary and
its confidentiality is of the highest importance and value to Mentor Graphics. Customer acknowledges that Mentor Graphics
may be seriously harmed if such source code is disclosed in violation of this Agreement. Except as otherwise permitted for
purposes of interoperability as specified by applicable and mandatory local law, Customer shall not reverse-assemble,
disassemble, reverse-compile, or reverse-engineer any Product, or in any way derive any source code from Software that is not
provided to Customer in source code form. Log files, data files, rule files and script files generated by or for the Software
(collectively “Files”), including without limitation files containing Standard Verification Rule Format (“SVRF”) and Tcl
Verification Format (“TVF”) which are Mentor Graphics’ trade secret and proprietary syntaxes for expressing process rules,
constitute or include confidential information of Mentor Graphics. Customer may share Files with third parties, excluding
Mentor Graphics competitors, provided that the confidentiality of such Files is protected by written agreement at least as well as
Customer protects other information of a similar nature or importance, but in any case with at least reasonable care. Customer
may use Files containing SVRF or TVF only with Mentor Graphics products. Under no circumstances shall Customer use
Products or Files or allow their use for the purpose of developing, enhancing or marketing any product that is in any way
competitive with Products, or disclose to any third party the results of, or information pertaining to, any benchmark.
4.2. If any Software or portions thereof are provided in source code form, Customer will use the source code only to correct software
errors and enhance or modify the Software for the authorized use, or as permitted for Embedded Software under separate
embedded software terms or an embedded software supplement. Customer shall not disclose or permit disclosure of source
code, in whole or in part, including any of its methods or concepts, to anyone except Customer’s employees or on-site
contractors, excluding Mentor Graphics competitors, with a need to know. Customer shall not copy or compile source code in
any manner except to support this authorized use.
4.3. Customer agrees that it will not subject any Product to any open source software (“OSS”) license that conflicts with this
Agreement or that does not otherwise apply to such Product.
4.4. Customer may not assign this Agreement or the rights and duties under it, or relocate, sublicense, or otherwise transfer the
Products, whether by operation of law or otherwise (“Attempted Transfer”), without Mentor Graphics’ prior written consent and
payment of Mentor Graphics’ then-current applicable relocation and/or transfer fees. Any Attempted Transfer without Mentor
Graphics’ prior written consent shall be a material breach of this Agreement and may, at Mentor Graphics’ option, result in the
immediate termination of the Agreement and/or the licenses granted under this Agreement. The terms of this Agreement,
including without limitation the licensing and assignment provisions, shall be binding upon Customer’s permitted successors in
interest and assigns.
4.5. The provisions of this Section 4 shall survive the termination of this Agreement.
5. SUPPORT SERVICES. To the extent Customer purchases support services, Mentor Graphics will provide Customer with updates and
technical support for the Products, at the Customer site(s) for which support is purchased, in accordance with Mentor Graphics’ then
current End-User Support Terms located at http://supportnet.mentor.com/supportterms.
6. OPEN SOURCE SOFTWARE. Products may contain OSS or code distributed under a proprietary third party license agreement, to
which additional rights or obligations (“Third Party Terms”) may apply. Please see the applicable Product documentation (including
license files, header files, read-me files or source code) for details. In the event of conflict between the terms of this Agreement
(including any addenda) and the Third Party Terms, the Third Party Terms will control solely with respect to the OSS or third party
code. The provisions of this Section 6 shall survive the termination of this Agreement.
7. LIMITED WARRANTY.
7.1. Mentor Graphics warrants that during the warranty period its standard, generally supported Products, when properly installed,
will substantially conform to the functional specifications set forth in the applicable user manual. Mentor Graphics does not
warrant that Products will meet Customer’s requirements or that operation of Products will be uninterrupted or error free. The
warranty period is 90 days starting on the 15th day after delivery or upon installation, whichever first occurs. Customer must
notify Mentor Graphics in writing of any nonconformity within the warranty period. For the avoidance of doubt, this warranty
applies only to the initial shipment of Software under an Order and does not renew or reset, for example, with the delivery of (a)
Software updates or (b) authorization codes or alternate Software under a transaction involving Software re-mix. This warranty
shall not be valid if Products have been subject to misuse, unauthorized modification, improper installation or Customer is not in
compliance with this Agreement. MENTOR GRAPHICS’ ENTIRE LIABILITY AND CUSTOMER’S EXCLUSIVE
REMEDY SHALL BE, AT MENTOR GRAPHICS’ OPTION, EITHER (A) REFUND OF THE PRICE PAID UPON
RETURN OF THE PRODUCTS TO MENTOR GRAPHICS OR (B) MODIFICATION OR REPLACEMENT OF THE
PRODUCTS THAT DO NOT MEET THIS LIMITED WARRANTY. MENTOR GRAPHICS MAKES NO WARRANTIES
WITH RESPECT TO: (A) SERVICES; (B) PRODUCTS PROVIDED AT NO CHARGE; OR (C) BETA CODE; ALL OF
WHICH ARE PROVIDED “AS IS.”
7.2. THE WARRANTIES SET FORTH IN THIS SECTION 7 ARE EXCLUSIVE. NEITHER MENTOR GRAPHICS NOR ITS
LICENSORS MAKE ANY OTHER WARRANTIES EXPRESS, IMPLIED OR STATUTORY, WITH RESPECT TO
PRODUCTS PROVIDED UNDER THIS AGREEMENT. MENTOR GRAPHICS AND ITS LICENSORS SPECIFICALLY
DISCLAIM ALL IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NON-INFRINGEMENT OF INTELLECTUAL PROPERTY.
8. LIMITATION OF LIABILITY. TO THE EXTENT PERMITTED UNDER APPLICABLE LAW, IN NO EVENT SHALL
MENTOR GRAPHICS OR ITS LICENSORS BE LIABLE FOR INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL
DAMAGES (INCLUDING LOST PROFITS OR SAVINGS) WHETHER BASED ON CONTRACT, TORT OR ANY OTHER
LEGAL THEORY, EVEN IF MENTOR GRAPHICS OR ITS LICENSORS HAVE BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES. IN NO EVENT SHALL MENTOR GRAPHICS’ OR ITS LICENSORS’ LIABILITY UNDER THIS
AGREEMENT EXCEED THE AMOUNT RECEIVED FROM CUSTOMER FOR THE HARDWARE, SOFTWARE LICENSE OR
SERVICE GIVING RISE TO THE CLAIM. IN THE CASE WHERE NO AMOUNT WAS PAID, MENTOR GRAPHICS AND ITS
LICENSORS SHALL HAVE NO LIABILITY FOR ANY DAMAGES WHATSOEVER. THE PROVISIONS OF THIS SECTION 8
SHALL SURVIVE THE TERMINATION OF THIS AGREEMENT.
9.1. Customer acknowledges that Mentor Graphics has no control over the testing of Customer’s products, or the specific
applications and use of Products. Mentor Graphics and its licensors shall not be liable for any claim or demand made against
Customer by any third party, except to the extent such claim is covered under Section 10.
9.2. In the event that a third party makes a claim against Mentor Graphics arising out of the use of Customer’s products, Mentor
Graphics will give Customer prompt notice of such claim. At Customer’s option and expense, Customer may take sole control
of the defense and any settlement of such claim. Customer WILL reimburse and hold harmless Mentor Graphics for any
LIABILITY, damages, settlement amounts, costs and expenses, including reasonable attorney’s fees, incurred by or awarded
against Mentor Graphics or its licensors in connection with such claims.
9.3. The provisions of this Section 9 shall survive any expiration or termination of this Agreement.
10. INFRINGEMENT.
10.1. Mentor Graphics will defend or settle, at its option and expense, any action brought against Customer in the United States,
Canada, Japan, or member state of the European Union which alleges that any standard, generally supported Product acquired
by Customer hereunder infringes a patent or copyright or misappropriates a trade secret in such jurisdiction. Mentor Graphics
will pay costs and damages finally awarded against Customer that are attributable to such action. Customer understands and
agrees that as conditions to Mentor Graphics’ obligations under this section Customer must: (a) notify Mentor Graphics
promptly in writing of the action; (b) provide Mentor Graphics all reasonable information and assistance to settle or defend the
action; and (c) grant Mentor Graphics sole authority and control of the defense or settlement of the action.
10.2. If a claim is made under Subsection 10.1 Mentor Graphics may, at its option and expense: (a) replace or modify the Product so
that it becomes noninfringing; (b) procure for Customer the right to continue using the Product; or (c) require the return of the
Product and refund to Customer any purchase price or license fee paid, less a reasonable allowance for use.
10.3. Mentor Graphics has no liability to Customer if the action is based upon: (a) the combination of Software or hardware with any
product not furnished by Mentor Graphics; (b) the modification of the Product other than by Mentor Graphics; (c) the use of
other than a current unaltered release of Software; (d) the use of the Product as part of an infringing process; (e) a product that
Customer makes, uses, or sells; (f) any Beta Code or Product provided at no charge; (g) any software provided by Mentor
Graphics’ licensors who do not provide such indemnification to Mentor Graphics’ customers; (h) OSS, except to the extent that
the infringement is directly caused by Mentor Graphics’ modifications to such OSS; or (i) infringement by Customer that is
deemed willful. In the case of (i), Customer shall reimburse Mentor Graphics for its reasonable attorney fees and other costs
related to the action.
10.4. THIS SECTION 10 IS SUBJECT TO SECTION 8 ABOVE AND STATES THE ENTIRE LIABILITY OF MENTOR
GRAPHICS AND ITS LICENSORS, AND CUSTOMER’S SOLE AND EXCLUSIVE REMEDY, FOR DEFENSE,
SETTLEMENT AND DAMAGES, WITH RESPECT TO ANY ALLEGED PATENT OR COPYRIGHT INFRINGEMENT
OR TRADE SECRET MISAPPROPRIATION BY ANY PRODUCT PROVIDED UNDER THIS AGREEMENT.
11.1. If a Software license was provided for limited term use, such license will automatically terminate at the end of the authorized
term. Mentor Graphics may terminate this Agreement and/or any license granted under this Agreement immediately upon
written notice if Customer: (a) exceeds the scope of the license or otherwise fails to comply with the licensing or confidentiality
provisions of this Agreement, or (b) becomes insolvent, files a bankruptcy petition, institutes proceedings for liquidation or
winding up or enters into an agreement to assign its assets for the benefit of creditors. For any other material breach of any
provision of this Agreement, Mentor Graphics may terminate this Agreement and/or any license granted under this Agreement
upon 30 days written notice if Customer fails to cure the breach within the 30 day notice period. Termination of this Agreement
or any license granted hereunder will not affect Customer’s obligation to pay for Products shipped or licenses granted prior to
the termination, which amounts shall be payable immediately upon the date of termination.
11.2. Upon termination of this Agreement, the rights and obligations of the parties shall cease except as expressly set forth in this
Agreement. Upon termination of this Agreement and/or any license granted under this Agreement, Customer shall ensure that
all use of the affected Products ceases, and shall return hardware and either return to Mentor Graphics or destroy Software in
Customer’s possession, including all copies and documentation, and certify in writing to Mentor Graphics within ten business
days of the termination date that Customer no longer possesses any of the affected Products or copies of Software in any form.
12. EXPORT. The Products provided hereunder are subject to regulation by local laws and European Union (“E.U.”) and United States
(“U.S.”) government agencies, which prohibit export, re-export or diversion of certain products, information about the products, and
direct or indirect products thereof, to certain countries and certain persons. Customer agrees that it will not export or re-export Products
in any manner without first obtaining all necessary approval from appropriate local, E.U. and U.S. government agencies. If Customer
wishes to disclose any information to Mentor Graphics that is subject to any E.U., U.S. or other applicable export restrictions, including
without limitation the U.S. International Traffic in Arms Regulations (ITAR) or special controls under the Export Administration
Regulations (EAR), Customer will notify Mentor Graphics personnel, in advance of each instance of disclosure, that such information
is subject to such export restrictions.
13. U.S. GOVERNMENT LICENSE RIGHTS. Software was developed entirely at private expense. The parties agree that all Software is
commercial computer software within the meaning of the applicable acquisition regulations. Accordingly, pursuant to U.S. FAR 48
CFR 12.212 and DFAR 48 CFR 227.7202, use, duplication and disclosure of the Software by or for the U.S. government or a U.S.
government subcontractor is subject solely to the terms and conditions set forth in this Agreement, which shall supersede any
conflicting terms or conditions in any government order document, except for provisions which are contrary to applicable mandatory
federal laws.
14. THIRD PARTY BENEFICIARY. Mentor Graphics Corporation, Mentor Graphics (Ireland) Limited, Microsoft Corporation and
other licensors may be third party beneficiaries of this Agreement with the right to enforce the obligations set forth herein.
15. REVIEW OF LICENSE USAGE. Customer will monitor the access to and use of Software. With prior written notice and during
Customer’s normal business hours, Mentor Graphics may engage an internationally recognized accounting firm to review Customer’s
software monitoring system and records deemed relevant by the internationally recognized accounting firm to confirm Customer’s
compliance with the terms of this Agreement or U.S. or other local export laws. Such review may include FlexNet (or successor
product) report log files that Customer shall capture and provide at Mentor Graphics’ request. Customer shall make records available in
electronic format and shall fully cooperate with data gathering to support the license review. Mentor Graphics shall bear the expense of
any such review unless a material non-compliance is revealed. Mentor Graphics shall treat as confidential information all information
gained as a result of any request or review and shall only use or disclose such information as required by law or to enforce its rights
under this Agreement. The provisions of this Section 15 shall survive the termination of this Agreement.
16. CONTROLLING LAW, JURISDICTION AND DISPUTE RESOLUTION. The owners of certain Mentor Graphics intellectual
property licensed under this Agreement are located in Ireland and the U.S. To promote consistency around the world, disputes shall be
resolved as follows: excluding conflict of laws rules, this Agreement shall be governed by and construed under the laws of the State of
Oregon, U.S., if Customer is located in North or South America, and the laws of Ireland if Customer is located outside of North or
South America or Japan, and the laws of Japan if Customer is located in Japan. All disputes arising out of or in relation to this
Agreement shall be submitted to the exclusive jurisdiction of the courts of Portland, Oregon when the laws of Oregon apply, or Dublin,
Ireland when the laws of Ireland apply, or the Tokyo District Court when the laws of Japan apply. Notwithstanding the foregoing, all
disputes in Asia (excluding Japan) arising out of or in relation to this Agreement shall be resolved by arbitration in Singapore before a
single arbitrator to be appointed by the chairman of the Singapore International Arbitration Centre (“SIAC”) to be conducted in the
English language, in accordance with the Arbitration Rules of the SIAC in effect at the time of the dispute, which rules are deemed to be
incorporated by reference in this section. Nothing in this section shall restrict Mentor Graphics’ right to bring an action (including for
example a motion for injunctive relief) against Customer in the jurisdiction where Customer’s place of business is located. The United
Nations Convention on Contracts for the International Sale of Goods does not apply to this Agreement.
17. SEVERABILITY. If any provision of this Agreement is held by a court of competent jurisdiction to be void, invalid, unenforceable or
illegal, such provision shall be severed from this Agreement and the remaining provisions will remain in full force and effect.
18. MISCELLANEOUS. This Agreement contains the parties’ entire understanding relating to its subject matter and supersedes all prior
or contemporaneous agreements. Any translation of this Agreement is provided to comply with local legal requirements only. In the
event of a dispute between the English and any non-English versions, the English version of this Agreement shall govern to the extent
not prohibited by local law in the applicable jurisdiction. This Agreement may only be modified in writing, signed by an authorized
representative of each party. Waiver of terms or excuse of breach must be in writing and shall not constitute subsequent consent, waiver
or excuse.