Capital Analysis User PDF

Capital® Analysis™ for Capital®
User Guide
Release 2015.1
February 2016
© 2016 Mentor Graphics Corporation

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

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

Table of Contents
Chapter 1
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Overview of Capital Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Model Construction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Capital SimCertify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Capital SimProve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Capital SimStress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Capital SimScript . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Model Construction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Capturing the Circuit Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Describing the System's Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Linking Function to Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Introduction to Capital SimCertify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Introduction to Interactive FMEA Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Introduction to Capital SimProve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Introduction to Capital SimScript . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Introduction to Capital SimStress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Introduction to Transient Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Frozen Shared Objects in Capital . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Using Different Numeric Simulators with Capital Analysis . . . . . . . . . . . . . . . . . . . . . . . . . 22
Enabling Transient Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Disabling Transient Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Switching to Berkeley SPICE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Switching to SystemVision Transient and VHDL Support . . . . . . . . . . . . . . . . . . . . . . . . 24
Switching to SimTransient VHDL Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Chapter 2
The Object Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Object Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Object Manager Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Navigating the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Reuse and Editing of Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Locking Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Object Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Object Finder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Searching for an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Save Printable File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Delete Lock Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Bulk Import/Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Exporting a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Importing a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Rename Object Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Capital Analysis for Capital User Guide, 2015.1 3

February 2016
Table of Contents
Audit Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Viewing an Audit Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Chapter 3
Simulator Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Overview of Simulator Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Robust Netlisting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Activating Robust Netlisting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Choose Log File Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Component Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Setting a Component Parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Local Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Expression Editor Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Overrides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Overriding Numeric Simulator Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Power Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Setting the Power Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Recording a Sequence of Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Recording a Sequence of Events as a Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Deleting an Event from a Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Opening an Existing Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Pausing a Recording Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Running a Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Simulating With Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Simulation Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Digital Multimeter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Watches (Simulator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Simulation Feedback Coloring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Simulator Tool Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Viewing Transient Graphs of Property Watches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
The Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Common Watch Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
The Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Chapter 4
Dynamic Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Starting Dynamic Simulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
On-Demand Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Starting On-demand Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Watches (Dynamic Simulation). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Adding Watches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Feedback on Watch Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Watch Persistence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Viewing Device Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Viewing Embedded Component Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Setting a Failure Against a Device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Output Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Analysis Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
4 Capital Analysis for Capital User Guide, 2015.1

February 2016
Table of Contents
Audit Report Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Chapter 5
FMEA Editor (Capital SimCertify) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Overview of FMEA Editor (Capital SimCertify) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
FMEA Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Editing and Appending an FMEA Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Header of FMEA Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Viewing the FMEA Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Filtering the Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Ordering the Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Printing an FMEA Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Exporting an FMEA Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Simulating a Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Menu Bar Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Edit Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Order Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Chapter 6
Capital SimCertify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Overview of Capital SimCertify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Capital SimCertify Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Edit Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Creating FMEA Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Defining Initial Circuit State. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Defining Circuit State Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Selecting Failures to Analyze . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Unresolved Scenario Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Confirm Event Delete Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Edit Description Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
FMEA Scenario Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Insert Combination Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Insert Component Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Run Scenario Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Simulate FMEA Record Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Chapter 7
Capital SimProject . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Overview of Capital SimProject . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Output Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Child Output Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Child Output Function Operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Copy, Cut and Paste . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

February 2016
Table of Contents
Control Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Creating a Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Adding Project Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Adding Output Functions to Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Adding Control Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Adding Excluded Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Saving the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Menus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Chapter 8
Capital SimScript . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Overview of Capital SimScript . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Performing a Script Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Capital SimScript Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Filter the Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
ECAD Device & Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Functions Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Simulation Properties & Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Error and Console Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Creating a Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Script File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Scenario Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Using a Script File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Override File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Error Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Overrides File format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Chapter 9
Capital SimProve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Overview of Capital SimProve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Performing an SCA Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Creating an SCA Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Advanced Functionality (Capital SimProve) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Exporting an SCA Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Prune an SCA Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
SCA Report View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Concern View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Function View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Type View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Simulation Displays Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
SCA Tool Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Chapter 10
Capital SimStress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Overview of Capital SimStress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Running Stress Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Stress Analysis Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Wire Sizing and Back Propagation of Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

February 2016
Table of Contents
Concerns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Defining Applied Current, Voltage and Power Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . 146
Defining Stress Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Custom Styles Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Creating a New Stress Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Editing a Stress Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Deleting a Stress Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Import and Export of Stress Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Chapter 11
Capital SimBridge. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Introduction to Capital SimBridge. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Chapter 12
The Component Builder Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Overview of Component Builder Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Component Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Creating a new component model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Selecting a Component Category. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
The Behavior Modeling Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Defining a Component Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Overriding Interface Property Promotion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Defining Component Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Moving Objects in the Structure Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Deleting Objects in the Structure Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Pin Naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Defining Component Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Defining Failure Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Overriding Failure Mode Promotion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Quantization Bands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Shared Object Component Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Attaching a Model to a Shared Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Embedding Hierarchical Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
To Embed a Hierarchical Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Reference an Embedded Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Set Failure Modes for an Embedded Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Embedding VHDL-AMS Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
To embed a VHDL-AMS model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Component Model Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
To create a Component Model template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
To create a Template from an existing Component Model . . . . . . . . . . . . . . . . . . . . . . . . 190
To delete a Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
To associate a Template with a Component Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
To delete the association between a Template and a Component Model . . . . . . . . . . . . . . 193
Component Builder Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

February 2016
Table of Contents
Basic Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Structural Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Failure Modes (Component Builder Tool) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Properties (component inputs/outputs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Completing the Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Component Library - Component Models Provided . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Attaching Component Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Generate Model in Capital Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Associate Symbol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Attaching Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Attaching Output Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Attaching Control Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Specifying Power Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Overriding Interface Property or Failure Mode Promotion . . . . . . . . . . . . . . . . . . . . . . . . 204
Component Builder Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Associate Symbol Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Associate Symbol Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Edit Comment Dialog Box (Component Builder) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Failure Mode Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Fuse Rating Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
New Component Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Description Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Component Builder Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Component Builder Related Menus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Structure Editor Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Dependency Editor Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Chapter 13
State Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Overview of State Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
State Builder Menus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Adding a New State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Defining State Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Moving and Resizing States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Hiding States. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Pushing and Popping States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Adding an Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Event Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Defining Event Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Moving Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Adding a Concurrency Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Import and Export State Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Importing a State Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Exporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Choose Grid Settings Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Edit Comment Dialog (State Builder). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Edit Event Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Edit State Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

February 2016
Table of Contents
Structure Error Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Chapter 14
QScheme Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Overview of QScheme Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Checking the QScheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Defining QScheme Bands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Numerical QSchemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
String QSchemes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Editing QSchemes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Ordering QSchemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Opening an Existing QScheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
QScheme Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
QScheme Warning Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
QScheme Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Creating a New QScheme. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Saving QSchemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Saving New QSchemes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Saving Existing QSchemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Chapter 15
Analysis Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Assigning a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Chapter 16
Scoping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Setting the Scope. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Chapter 17
The Design Inspector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Accessing the Design Inspector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Using the Design Inspector with Capital Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Object Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Object Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Extending the Design Inspector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Chapter 18
Component Model Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Overview of Component Model Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Exporting Encrypted Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
To export a component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
To export a folder of components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Importing Encrypted Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
To import a component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Encrypting VHDL-dependent components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

February 2016
Table of Contents
Chapter 19
Menus and Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Export Netlist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Exporting to XML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Exporting to Saber (Export Netlist) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Edit Stress Report Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
General Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
About Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Error Report Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Filter Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Find And Replace Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Input Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Object Properties Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Open/Save Object Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Progress Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Database Dependency Check Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Chapter 20
Editing Global and User Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Edit Options Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
General Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Syntax Highlighting Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Changing Color Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Changing Font Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Automation Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
RPN Default Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Report Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Simulation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Simulation Highlighting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Adding a New Highlight. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Editing an Existing Highlight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Deleting a Highlight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Model Search Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Adding a Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Deleting a path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Component Categories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Adding a Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Edit a Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Delete a Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Error Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Qualitative Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Modeling Language Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Simulation Engine Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Numeric Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Spice Simulator Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
External Model Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

February 2016
Table of Contents
To create an external model object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

To compile an external model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
To manage the external model list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
To edit an external model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
To delete an external model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
To unlock all external models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
To export external models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Structure Editor Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
State Builder Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Chapter 21
Configuration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Configuration Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Encryption Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Optional Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Configuration Tool - dsAdmin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Datasource Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Change Administrator Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Encryption Key Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
To create a key file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
To create a key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
To delete a key file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
To delete a key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Appendix A
Company Preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Generic Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
RunTime.properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
FmeaText.properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
ScaText.properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
SimulationText.properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
EcadBridge.properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
EcadDefault.properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Script Analysis Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
SaberNetlister.Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Appendix B
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Internal "Duplication Entry" exceptions are being raised . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Internal "java.lang.RuntimeException" exceptions are being raised. . . . . . . . . . . . . . . . . . . 318
Sometimes the component model attacher does not attach the component model . . . . . . . . 318
Error message "Failed to connect to component 'X' . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
Error message "Failed to initialise viewbase routines" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Composite Components seem Disconnected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
The error report window appears, however no messages are displayed . . . . . . . . . . . . . . . . 319

February 2016
Table of Contents
Your workstation slows down after a few months. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320

For TransCable users, multiple alert messages are being displayed . . . . . . . . . . . . . . . . . . . 320
When using the Simulator, functions seem to be achieved when the schematic colouring indicates
that they should not be . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
The following message appears "Sorry: dependency expressions caused oscillation" . . . . . 321
The following message appears "Sorry: current flow across diode(s) could not be determined"
321
The following message appears "Failure: warning - uncontrolled thermal activity detected" 322
The following message appears "Sorry: event conflict detected in state machine(s)" . . . . . 322
The following message appears "Sorry: race condition detected". . . . . . . . . . . . . . . . . . . . . 322
Exporting an FMEA report to some formats results in failure . . . . . . . . . . . . . . . . . . . . . . . 322
FMEA Editor (Capital SimCertify) hangs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
For TransCable users, after simulating a schematic, the colours of the schematic have not
reverted back to there original state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Importing an .f2f file, exported by Capital Analysis, into FMEA+ fails. . . . . . . . . . . . . . . . 324
Appendix C
Administration of Capital Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Administrator Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Appendix D
System Import/Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Import and Export Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Appendix E
Supply Rails, Batteries and Multiple Battery Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Single Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Explicit Batteries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Multiple Batteries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Appendix F
Self Modeling Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Creating a self modifying model map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Specifying component type information META_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Identifying the supported device types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
Specifying Adaptive Component Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
Identifying Component Model Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
Managing Terminal Mapping Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Appendix G
Dynamically Generated Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Dynamic Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Setting Resistance on Dynamically Generated Arcs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
To view a dynamically generated model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
To override default behavioral code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342

February 2016
Table of Contents
Appendix H
Saber Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Saber Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Saber Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Netlist Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
Mast Model Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
Ignore Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
Identifier Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
Parameters Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
Property Value Substitution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Exclusion Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
Exporting to Saber (Saber Integration) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Saber Model Template Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Appendix I
SystemVision Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
SystemVision Integration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
SystemVision Integration Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
SystemVision Project Attachment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
SystemVision VHDL Model Attachment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
SystemVision Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Appendix J
Error Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Could not connect to the database:Could not load library 'libmysqlclient'.. . . . . . . . . . . . . . 365
Analysis error message: "both supply rail and batter components are present..." . . . . . . . . . 365
Can not run Background Simulation and no simcore.exe is listed in task manager.. . . . . . . 366
Capital Web Naming Service does not invoke due to the lack of port number as a parameter.
367
Error message: Destination component DEV_1{DEV**P1} does not exist in the component list.
367
Error: Unable to obtain a license for feature CHManufact, License request for feature NULL
failed [mgls_errno 203] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Error when trying to run casconfig -dsAdmin in DOS Shell. . . . . . . . . . . . . . . . . . . . . . . . . 369
Cap Analysis - error message: no 'Quantization Bands' have been specified.. . . . . . . . . . . . 370
OCI.dll The specified module could not be found. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
The DataSource Admin tab does not appear when launching the Configuration Tool with
casconfig -dsadmin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Unable to connect to the AutoSteve Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Unable to import a database dump of Capital; "the objects were exported by SYS, not by you"
372
Index
Third-Party Information
End-User License Agreement

February 2016
List of Figures
Figure 3-1. Simulation Feedback Coloring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Figure 4-1. Watch Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Figure 4-2. Embedded Component Properties Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Figure 10-1. Capital SimStress Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Figure 12-1. Component Interface Property Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Figure 12-2. Interface Property States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Figure 12-3. Failure Mode Definition Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Figure 12-4. Failure Modes States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Figure G-1. Dynamically Generated Connector Structure . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Figure G-2. Dynamic Connector Example Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
Figure G-3. Dynamically Generated Single-pin Splice Structure . . . . . . . . . . . . . . . . . . . . . 340
Figure I-1. Outline of the Analysis Flow with SystemVision Integration. . . . . . . . . . . . . . . 357
Figure I-2. Choosing SystemVision Simulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
Figure I-3. Example DRCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Figure I-4. Model Attachment Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Figure I-5. SystemVision Simulation Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Figure I-6. Simulation Parameter Specification in SystemVision . . . . . . . . . . . . . . . . . . . . . 363
Figure I-7. Analysis Operations in SystemVision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364

February 2016
List of Tables
Table 2-1. Delete Lock Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Table 2-2. Rename Object Dialog Contents Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . 35
Table 3-1. Choose Log File Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Table 3-2. Expression Editor Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Table 3-3. Simulation Feedback Colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Table 4-1. Analysis Tab Toolbar Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Table 6-1. Confirm Event Delete Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Table 6-2. Edit Description Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Table 6-3. FMEA Scenario Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Table 6-4. Insert Combination Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Table 6-5. Insert Combination Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Table 10-1. Custom Styles Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Table 12-1. Associate Symbol Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Table 12-2. Edit Comment Dialog Box(Component Builder) Contents . . . . . . . . . . . . . . . . 208
Table 12-3. Failure Mode Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Table 12-4. Fuse Rating Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Table 12-5. Description Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

February 2016
List of Tables

February 2016
Chapter 1
Introduction
This chapter contains high-level, introductory information about Capital Analysis and aspects
of its functionality.
Overview of Capital Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Model Construction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Introduction to Capital SimCertify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Introduction to Interactive FMEA Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Introduction to Capital SimProve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Introduction to Capital SimScript . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Introduction to Capital SimStress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Introduction to Transient Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Frozen Shared Objects in Capital . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Using Different Numeric Simulators with Capital Analysis . . . . . . . . . . . . . . . . . . . . . . 22
Overview of Capital Analysis

The Capital Analysis tool set can provide several major design analysis tasks:
• Model Construction
• Automated FMEA (Failure Mode and Effects Analysis) Assistant
• Sneak Circuit Analysis
• Stress Analysis
• Design Verification Scripting
Model Construction
Capital Analysis is used for creating component models:
• Model Construction - The engineer gathers and inputs the information needed by the
Capital Analysis system by creating structural and behavioral models of circuit
components.

February 2016
Introduction
Model Construction
Capital SimCertify
The use of Capital Analysis for this task can be broken down into two stages:
• FMEA Generation - This stage is mostly automated, and it is at this point that Capital
Analysis generates the failure effects and RPN values.
• Introduction to Interactive FMEA Verification - During this stage, the engineer uses
Capital Analysis to examine the results of the automated FMEA generation.
Capital SimProve
The use of Capital Analysis for this task can be split into two stages:
• SCA Generation - This stage is automated, and it is at this point that Capital Analysis
detects possible sneaks.
• Interactive SCA Verification - During this stage, the engineer uses Capital Analysis to
examine the results of the automated SCA generation.
Capital SimStress
Capital SimStress is used for analyzing the maximum stresses (current, voltage and power)
detected on each component. This data can be used to generate wire and fuse sizing
information, which can then be back-propagated to your designs.
• Stress Analysis - This stage is automated and will explore all the switch changes for a
schematic and report the maximum current, voltage and power detected on each
component. See “Capital SimStress” on page 135.
Capital SimScript
Capital Analysis allows you to use design verification scripts to testing circuits:
• Design Verification Scripting - This facility is part of the Simulator tool and allows you
to run scripts that test the operation of circuits.
Model Construction
During the model construction stage, the engineer collects all the information required to
describe how the circuit works. There are three main aspects of the model:
• Capturing the circuit design
• Describing the system's functionality

February 2016
Introduction
Model Construction
• Linking function to structure
Capturing the Circuit Design

The model construction phase of using Capital Analysis has been streamlined to use existing
information as much as possible. If the circuit has already been drawn using the ECAD tool,
then this phase only involves checking that the circuit behaves correctly within Capital
Analysis. Capital Analysis's component library contains descriptions of the operation and
failure modes for common components such as wires and relays. If the circuit contains a
component that does not have predefined operation within Capital Analysis (such as an ECU),
then the Component Builder provides facilities for defining the operation of such a component.
A later section describes the operation of the Component Builder. Once the circuit description
within Capital Analysis is complete, it is possible to simulate the operation of the circuit under
different conditions by opening and closing switches in the circuit simulator. The simulator will
show which paths are active by changing the color of components. This facility should be used
to ensure that the circuit has the correct behavior when all components are working properly. A
later section describes the features of the Overview of Simulator Tool.
Describing the System's Functionality

Knowledge of the intended functions of the system must be added to the circuit design
information in order to interpret the state of the circuit in ways that are meaningful in an FMEA
report. For each circuit, Capital Analysis uses a set of functional labels that describe what the
system is intended to do (e.g. all doors locking in the central door locking system). These labels
are held in a library, along with numbers that describe the significance and detection values for
absence of the function when it is expected, and presence of the function when it is not expected
(these values are used in RPN generation). These functional labels are highly reusable provided
that the designers decompose the electrical system into subsystems in the same manner for each
project.
Functions are created as part of project models in Capital SimProject.
Linking Function to Structure

In order for Capital Analysis to be able to interpret the state of the circuit at any point, the
engineer must link the functional labels to the state of significant components in the circuit. This
is done by describing the state of all significant components when a function is being achieved.
For example, the "all doors locking" function might be achieved when each door lock motor is
activated in the "FORWARD" direction or the corresponding door switch indicates that the door
is already locked. The linking of the functions to a subsystem is performed using the Analysis
Settings dialog.

February 2016
Introduction
Introduction to Capital SimCertify
Introduction to Capital SimCertify

Once the engineer has verified that all necessary information for model construction has been
entered into the Capital Analysis system, then the automated phase of Capital Analysis can be
started.
This involves the Capital Analysis system deciding each fault that could happen on each of the
components in the circuit, and trying simulation of the circuit with that fault through a standard
set of simulation steps, in order to see what the consequences of the fault are. The simulation
steps must be set up by the engineer before the automated phase is started, and should test all of
the functionality of the circuit. This is done by describing initial conditions of the circuit, and a
set of switch changes to exercise the circuit. Capital Analysis then simulates the correct circuit,
and notes which functions are active after each change in switch state. When the circuit is
simulated again for each possible component fault, Capital Analysis compares the functions that
are expected to be active after each switch change with the functions that are actually achieved.
The difference is determined as the failure mode and a failure effect is generated from this.
Capital Analysis assigns RPN values (severity, occurrence, detection) to the effects of each
failure. The output of this procedure is the contents of the FMEA report. After the report has
been generated it can be examined and printed out, as the next section describes in more detail.
A later section of this document describes the options for setting up and running an FMEA
generation using the FMEA Tool (see “Overview of Capital SimCertify” on page 79).
Introduction to Interactive FMEA Verification

Interactive FMEA (Failure Mode and Effects Analysis) verification presents the results of the
automated analysis to the engineer for examination and amendment. The results can be viewed
on the screen in a similar format to the paper-based FMEA form, but with the benefit of being
able to arrange the results in several different ways.
The engineer can ask for more details on the failure effects, or invoke the simulator to perform a
simulation of the circuit with a particular fault present, in order to gain more information about
what happened. The engineer can also edit the RPN values or the text before printing the report
to a laser printer or exporting it to FMEAplus. See “FMEA Editor (Capital SimCertify)” on
page 69 to find out more about the FMEA Editor.
Introduction to Capital SimProve

Capital SimProve builds on the work done by the engineer in producing an FMEA Report. To
do an FMEA, expressions have to be constructed that detects when a particular function is
achieved.
Function expressions consider the outputs of the circuit (are the lamps illuminated). To do an
SCA, for each function, a sneak expression must be constructed that detects when the function
should be achieved. Sneak expressions consider the inputs to the circuit (is the switch closed).
These sneak expressions can be viewed as model of the correct operation of the circuit.

February 2016
Introduction
Introduction to Capital SimScript
Capital SimProve then compares this model with the observed behavior of the circuit (see
“Overview of Capital SimProve” on page 123). This could result in a number of concerns being
detected. In situations where a function has been achieved, when the model indicates that it
should not have been, this is highlighted as a possible sneak. In situations where a function has
not been achieved, but the model indicates that it should have been achieved, this is highlighted
as a possible failure of the circuit to met its specification.
After a report has been generated, the engineer can view the state of the circuit for each concern
of interest.
Introduction to Capital SimScript

This facility allows scripts to be constructed and run that test the operation of circuit.
It is an extension of the Overview of Simulator Tool. The scripts can be saved and run on
different versions of the circuit. These scripts can change switch settings and set failure modes
to components. The effects such changes have on the circuit can be observed and saved to a file.
See “Capital SimScript” on page 103 and “Script File Format” on page 108 to find out more
about scripting.
Introduction to Capital SimStress

Capital SimStress performs a numerical analysis of your design, exercising all input
combinations and generates a results table that contains results defined by a 'stress style'.
The supplied stress styles allows the traditional formatting of stress results. This style displays
the maximum voltage, current and power values for each component, and suggested wire CSA.
This data can be back propagated to the ECAD tool.
In addition to the above information, any concerns found during the analysis will be displayed
in the concerns tab of Capital SimStress. The concerns could be related to fuses blowing, or
short circuit conditions. See “Overview of Capital SimStress” on page 135 to find out more
about Capital SimStress.
Introduction to Transient Analysis

Transient analysis is available as part of Capital Analysis suite. This extension (licence
dependant) allows the majority of the analysis tools to be run in a transient mode. This will
allow the engineer to closely analyze those areas of the design that time plays a critical part in.
This may be how long a fuse takes to blow, or how long the battery takes to discharge. To run
in transient mode it is a case of checking a transient check box in the majority of the tools.
Some extra setup information is usually needed for the transient run:
• Start Time - The point in time that the analysis should start, this defaults to zero.

February 2016
Introduction
Frozen Shared Objects in Capital
• Stop Time - The point in time when the simulation should finish.
• Sample Rate - How often the state of the simulated system should be sampled and
recorded.
• Variable Time Steps - This is a mode of operation of the numeric transient simulator,
where the simulation engine automatically determines the sample rate of the results.
Note
Some models will need to have been associated with the correct transient mode in order
to simulate. Please see the language reference guide for more detail.
Related Topics
Overview of Simulator Tool Overview of Capital SimProve
Overview of Capital SimStress Capital SimScript
Overview of Capital SimCertify
Frozen Shared Objects in Capital

If shared objects have been frozen in Capital, this limits the actions that Capital Analysis can
perform on them in the following ways:
• You cannot attach component model information.
• You cannot propagate properties back to the shared object in Capital when performing
operations in Capital Analysis tools.
Using Different Numeric Simulators with

Capital Analysis
At present, Berkeley SPICE 3f5, SystemVision and SimTransient are supported. Contact our
technical support team if you need to use a different version.
Note that the SimAPI based simulators are the only ones that support the following:
1. VHDL models
2. Transient Simulation
This section contains details on how to switch and enable numeric simulators.
Enabling Transient Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Disabling Transient Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Switching to Berkeley SPICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

February 2016
Introduction
Using Different Numeric Simulators with Capital Analysis
Switching to SystemVision Transient and VHDL Support . . . . . . . . . . . . . . . . . . . . . . . 24

Switching to SimTransient VHDL Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Enabling Transient Support

You can enable transient support.
Procedure
1. Ensure that you have either SystemVision or SimTransient installed.
2. Open the ConfigurationTool.
3. Select the Optional Components tab.
4. Check the Capital SimTransient check-box.
5. Click OK.
Disabling Transient Support

You can disable transient support.
Procedure
1. Open the ConfigurationTool.
2. Select the Optional Components tab.
3. Uncheck the Capital SimTransient check-box.
4. Click OK.
Switching to Berkeley SPICE

You can switch to Berkeley SPICE.
Procedure
1. Open the <CAPITAL_installation_directory>/resources/resources directory.
2. Edit the RunTime.properties file.
In this file, you might find a line similar to the following:
netsim.spice.program.override = ...
To switch to using Berkeley SPICE, change this line to (or add the line if it is not
present)

February 2016
Introduction
Using Different Numeric Simulators with Capital Analysis
netsim.spice.program.override = berkeley
3. Save the file.
4. You need to ensure that ${PATH} includes the PSpice executable.
Switching to SystemVision Transient and VHDL

Support
You can switch to SystemVision Transient and VHDL Support.
Procedure
1. Open the <Capital_installation_directory>/resources/resources directory.
To switch to using SystemVision, change this line to (or add the line if it is not present)
netsim.spice.program.override = simapi
3. Save the file.
Switching to SimTransient VHDL Support

Contact Mentor Graphics support to obtain the latest SimTransient distribution before following
these steps.
Procedure
1. Open the <Capital_installation_directory>/resources/resources directory.
To switch to using SimTransient, change this line to (or add the line if it is not present)
netsim.spice.program.override = simapi
and ensure the following line is set
simcore.simapi.tengine=true
3. Save the file.

February 2016
Chapter 2
The Object Manager
This chapter contains information about the Object Manager and its functionality.
Object Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Navigating the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Reuse and Editing of Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Locking Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Object Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Object Finder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Save Printable File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Delete Lock Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Bulk Import/Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Rename Object Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Audit Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Object Manager
Capital Analysis requires the creation of analysis component models and audit reports. Once
these objects have been created, they are stored in a database structure allowing engineers
access to modify or reuse them in future projects.
The Object Manager supplied as part of the Capital Analysis system is the tool that provides
engineers with access to this database. The Object Manager window is invoked by pressing
Space Bar and entering Object Manager.
The Object Manager window is divided into 2 sections. The section on the left displays the
directory structure of the database and the section on the right displays the objects located in the
highlighted directory.
The directory structure within the database should be arranged to suit the user. Each engineer
might wish to have their own directory or it might be appropriate for work to be stored in
project directories. The Object Manager gives users the flexibility to choose the set up that best
suits them.
Related Topics
Navigating the Database Reuse and Editing of Objects

February 2016
The Object Manager
Object Manager Menus
Object Finder Locking Objects

Object Properties Object Manager Menus

This topic describes the various menus that area available.
File Menu
New: This menu option invokes an additional menu. It gives the user the option of creating a
new Folder (directory), or one of the following objects:
• Component Model
• FMEA Report
• State Machine
• Component Mapping
• QScheme
• Script
Import Folder: This menu option does a bulk import of a folder (see “Bulk Import/Export” on
page 34). The input of the import is a Zip file that has been exported from another database.
Export Folder: This menu option does a bulk export of a folder (see “Bulk Import/Export” on
page 34). The output of the export is a Zip file that can be imported to another database.
Print: Prints a report of the contents of a selected folder
Print Preview: Displays an image that represents the printer output of the selected object.
Exit: Exits the Object Manager window.
Edit Menu
Open Selected: Opens the selected object in the relevant tool (i.e. opens a component model in
the Component Builder tool)
Rename...: Allows the user to rename the selected object (see “Rename Object Dialog Box” on
page 35).
Cut: Removes the selected object from the database and places it on the clip board. This option
is also available as a tool button .
Copy: Copies the selected object to the clip board. This option is also available as a tool button
.

February 2016
The Object Manager
Paste: Pastes an object from the clip board into the database at the location of the highlighted
directory. This option is also available as a tool button .
Delete: Deletes the selected objects from the database . A dependency checking operation is
performed before any object is deleted (see “Database Dependency Check Dialog” on
page 267).
Select All: Highlights all the objects in the selected directory or folder.
Find: Opens the Object Finder, to allow the user to search for objects in the database.
System Preferences: Gives the user access to the Capital Analysis user definable options. See
“Edit Options Dialog” on page 269 for more details.
View Menu
Refresh Display: Refreshes the contents of the database in the Object Manager window.
Display Properties: Invokes a dialog displaying the properties of the selected object (see
“Object Properties” on page 31).
Tools Menu
Admin mode: Enables Administrator level privileges on the database.
Lock: Applies a database lock to the selected object .
Unlock: Removes the lock applied to the selected object (see “Delete Lock Dialog Box” on
page 34).
Export Encrypted: Allows the export of component object models in an encrypted format. See
“Exporting Encrypted Components” on page 254.
Import Encrypted: Allows the import of encrypted component object models. See “Importing
Encrypted Components” on page 256.
Listing: Saves a list of the objects in the current folder to a file (see “Save Printable File” on
page 33).
Netlist Scope Management: Allows the unlocking of a design’s scope.
Unlock VHDL Models: Forces the unlocking of any persistent locks on external VHDL
models. See “To unlock all external models” on page 285.
Related Topics
Object Manager Navigating the Database

February 2016
The Object Manager
Navigating the Database
Reuse and Editing of Objects Locking Objects

Object Properties
Navigating the Database

To navigate around the database, use the left-hand section of the window. The top-level entry in
the navigation menu will display the type and name of the database host, as well as the port
number in use and the name of the database.
Highlighting a directory by clicking on it will display its contents in the right hand section.
A symbol indicates the directory has at least one sub-directory associated with it. By clicking on
this symbol the sub-directories will be displayed. The user can also move up to the next
directory by clicking on the up arrow located on the Object Manager tool bar.
In the right hand section of the window each object has an icon preceding its name.
The different icons represent the different types of object.
Representing a component model (see “Component Builder” on page 160) or

component model template (see “Component Model Templates” on page 189)
Representing an encrypted component model (see “Component Model Encryption”
on page 253).
Representing a state machine (see “State Builder” on page 217).
Representing a design description.
Representing a FMEA report (see “FMEA Editor (Capital SimCertify)” on page 69).
Representing a component mapping.
Representing a qscheme (see “Overview of QScheme Builder” on page 233).
Representing a script object.
Representing an audit report (see “Audit Reports” on page 35).
Related Topics
Object Manager Object Manager Menus
Reuse and Editing of Objects Locking Objects
Object Properties

February 2016
The Object Manager
Reuse and Editing of Objects
Reuse and Editing of Objects

Once an object has been created and stored in the database it can be reused or edited for use
elsewhere saving considerable effort for the engineer concerned.
To reuse an object, the engineer can copy and paste it using the copy button and paste
button both located on the Object Manager tool bar or alternatively select these options
from the Object Manager Edit menu. To avoid confusion, the engineer might wish to rename
the object once it has been copied. This can be done by selecting the "Rename" option also
located on the Object Manager Edit menu.
If an object is required that is similar to an already existing one, the engineer might choose to
edit a copy of the existing model. Once the object to be edited has been copied to a new location
the engineer can open the selected object by either selecting the "Open Selected" option from
the Object Manager Edit menu or by double clicking on the object itself. In both cases the
relevant tool will be invoked with the object loaded. For example, if it is a component the
engineer wishes to edit, the Component Builder tool will be invoked with the component
already loaded.
Related Topics
Navigating the Database Locking Objects
Object Properties
Locking Objects
The Capital Analysis system is designed as a multi-user system and so more than one user may
wish to access the same object simultaneously. Therefore Capital Analysis uses a system of
object locking in order to maintain the integrity of the database and its objects.
For example if an object is in the process of being edited by one user, the software will have
automatically applied a lock to the object in the database, its icon will be grayed out in the
Object Manager window and it will be unavailable to other users whilst the lock is in force.
When the user saves the edited version to the database the lock is automatically removed and
once again the object is available to other users.
Locks can be applied and removed manually or automatically when a tool edits an object. A
user can only remove a lock that was created for or by that user. However, the administrator can
remove any lock. Great care should be taken when doing this not to compromise the integrity of
the database. Here are the setups involved in applying a manual lock as administrator.

February 2016
The Object Manager
Locking Objects
Procedure
1. You must first enter the admin mode if you have not already done so. Select "Admin
Mode" from the Tools > Admin menu option in the Object Manager. A dialog will
appear asking the administrator for a password.
2. After entering the password and clicking the "OK" button, the title bar of the Object
Manager window will change to "Administration" and the lock buttons on the tool bar
will now be available for use.
3. To apply the lock, ensure the correct object is highlighted and then
4. Either click the lock button located on the object manager window tool bar or select
the "Lock" option from the Administration window Tools menu.
Here are the setups involved in applying a manual lock as a normal user:
1. Ensure the correct object is highlighted in the right hand area of the object manager.
2. Either click the lock button located on the object manager window tool bar or select
the "Lock" option from the Administration window Tools menu.
To manually remove a lock from an object as Administrator:
1. You must first enter the admin mode if you have not already done so.
2. Ensure the relevant object is highlighted in the right hand area of the object manager
3. Select the "Unlock" option from the object manager window Tools menu or clicking the
Delete Lock button on the window tool bar (see “Delete Lock Dialog Box” on
page 34 for more information).
To manually remove a lock from an object as a normal user:
1. Ensure the relevant object is highlighted in the right hand area of the object manager
2. Select the "Unlock" option from the object manager window Tools menu or clicking the
Delete Lock button on the window tool bar (see “Delete Lock Dialog Box” on
page 34 for more information).
Related Topics
Object Properties

February 2016
The Object Manager
Object Properties
Object Properties
An engineer can view the properties of a particular object. This is done by highlighting the
desired object by clicking on it and then selecting the Properties option from the Object
Manager View menu.
An object's properties will consist of the following:
• Name
• Id number
• Type of object (i.e. component, design etc.)
• Location of the object in the database
• When it was Created and by whom
• When it was Last modified and by whom
• Any locks that are applied to the object
In particular the text frame displaying the locks that apply to the object can be very useful. For
example, if an engineer wishes to edit an object but finds it is locked in the database, by looking
at the properties they can find out who applied the lock and when it was applied.
Related Topics
Locking Objects
Object Finder
This tool allows the user to search the database to find an object or folder in the database.
It can be opened from the Object Manager.
Searching for an Object

The upper half of the window has several input boxes to enter details about the object(s) that the
engineer is trying to find. The Name & Location tab has the details:
• Named - the name or part name of the object the engineer is looking for, there is a
button on the right of this text bar indicating a pick list to allow access to previous
entries.

February 2016
The Object Manager
Object Finder
• Of Type - this is a pick list of the types of object that are supported by Capital Analysis
in the Object Manager. This also has options to search for all types of object or a folder.
• Look In - the default for this is Whole Database; by using the Browse button a single
directory can be searched, which makes the search run faster.
The Date Modified tab has these options:
• All Files - all the files will be searched

• Find all files created or modified - one of the following three options must then be
chosen and only objects created or modified within the given time period are displayed
as search results.
o between DD/MM/YYYY and DD/MM/YYYY - the dates must be chosen using
the picklists
o during the previous [ ] month(s)
o during the previous [ ] day(s)

February 2016
The Object Manager
Save Printable File
There are also three buttons to perform the search. Start Search will start looking for the
object(s) as has been specified. Stop Search will abort the search and output the object already
found to the table. New Search will clear all the details and the table of objects found in the last
search.
Once a search has finished (or been stopped) the list of objects found will be displayed in the
table along with their locations and dates. An object will be opened in its editor by double-
clicking on it.
The Object Finder only has the File menu with an Exit option to close the window and the usual
Help menu.
Related Topics
Object Manager
Save Printable File

The Save Printable File function is part of the Object Manager. Under the Tools menu select
Listing to save the selected directory's information to a text file. The file's extension will be
".dls".

February 2016
The Object Manager
Delete Lock Dialog Box
Related Topics
Delete Lock Dialog Box

To access: select Tools>Unlock
This dialog shows all the locks on a selected object.
Fields
Table 2-1. Delete Lock Dialog Box Contents
Field Description
Information For each lock the following information is displayed.
Panel • The lock type (Read/Write)
• The person who locked the object
• The date and time the object was locked
To delete the locks click OK. To keep the locks click Cancel.
Related Topics
Object Manager
Bulk Import/Export
These topics detail the process of exporting and importing folders.
Exporting a Folder
Select the folder you wish to export.
1. Click the File > Export folder menu, the Save window appears.
Note
If you have selected the root folder in the Object Manager, the You have selected the
root folder dialog gives you the option Include Settings. Select this option if you want
to export Analysis settings (equivalent to system data) alongside Analysis objects (such
as models). If you do not select this option, only Analysis objects are exported.
2. Use this file chooser to select the name and location of the export file to be created.
Clicking the Save button will open the Bulk export status window.
3. On completion of the export operation, click OK to close the window.

February 2016
The Object Manager
Rename Object Dialog Box
Importing a Folder
It is recommended that you create a new folder to import into. When the import is complete the
folders can be renamed as necessary.
1. To start the import, select the new folder (within which the exported folder will be
created) and clicking the File > Import folder menu, the Open window appears.
2. Use this file chooser to select the name and location of the export file to load. The
Include Settings option allows you to specify whether you want to include Analysis
settings in the import (selected) or not (unselected). Clicking the Open button will open
the Bulk import status window. Note: This option is only available if importing from
the root folder.
3. On completion of the import operation, click OK to close the window.
4. If you selected to import settings, restart the application.
Related Topics
Object Manager
Rename Object Dialog Box

This dialog allows the user to edit the name and description of an object in the database.
Click OK to accept the changes or Cancel to keep the existing name & description.
Fields
Table 2-2. Rename Object Dialog Contents Box Contents
Field Description
Name Edit the name of the object.
Description Edit the description of the object.
Related Topics
Object Manager
Audit Reports
Audit reports can be created by selecting the Create Audit Report option when running
Capital SimCertify or Capital SimStress actions using the FMEA Wizard.

February 2016
The Object Manager
Viewing an Audit Report
For further information see Capital SimCertify - Run Scenario Wizard and Capital SimStress -
Stress Analysis Wizard.
Once created, they can be accessed in the Object Manager by highlighting the Audit directory
( ). Clicking on this icon will display its contents in the right hand section.
The right hand section display the details of the available audit reports including name, a
description of the action performed to generate it. the date of its creation and its last
modification date. Right clicking on a report opens a context menu containing some of the
actions available in the Object Manager Menus.
Related Topics
FMEA Wizard (Run Scenario Wizard) Stress Analysis Wizard
Object Manager Menus Viewing an Audit Report

This topic describes how to open and view the contents of an Audit report and how the report is
structured in terms of environment and analysis setup.
Procedure
1. There are a number of ways an Audit Report can be viewed. Do one of the following:
• Highlight the required report and select Edit > Open Selected from the menu
or
• Double click the required report
or
• Right click and choose Open Selected from the context menu
2. The report opens in the Audit Report Viewer. It contains the following:
• Report Name: name of the audit report object
• Generated: date and time the audit was created
• User: username of the creator of the audit
• Software Version: major version, service pack and hotfix (if applicable)
• Database: unique identifier information for the database the audit was run on. This
may differ from the database the audit is currently in.
• Project: the name of the project within which the audit was created.

February 2016
The Object Manager
• Analysis Type: type of analysis (such as Capital SimStress or Capital SimCertify).

• Simulation Type: Qualitative, Numeric, Transient.
• Scope: list all designs, their revisions and short descriptions that were in scope. If
more than one, each is listed on its own row.
• Global Expressions: list all global expressions (if any) used during the run. If more
than one, each is listed on its own row.
• Numeric Settings: list all numeric settings (if any) used during the run. If more than
one, each is listed on its own row.
• Transient Conditions: list all transient conditions (if any) used during the run. If
more than one, each is listed on its own row.
• Input Settings: list all input settings (if any) used during the run. If more than one,
each is listed on its own row.
• Applied Failure Modes: list all failure modes the user applied (if any) during the run.
If more than one, each is listed on its own row.
• Scenario: Description of scenario (if applicable).
3. Click Open Report to view full results from the running of the analysis scenario. Note,
the report is opened in read-only mode based on the type of report.
Related Topics
FMEA Wizard (Run Scenario Wizard) Stress Analysis Wizard

February 2016
The Object Manager

February 2016
Chapter 3
Simulator Tool
Capital Analysis can simulate the behavior of a circuit when the states of switches in the circuit
are changed. This can be shown graphically on the schematic of the ECAD tool and helps to
verify the correct behavior of the circuit and to understand its faulty behavior. Active wires in
the circuit are colored green and possess an arrow indicating the direction of the current.
Inactive wires are colored blue.
Overview of Simulator Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Robust Netlisting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Choose Log File Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Component Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Local Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Overrides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Power Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Recording a Sequence of Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Running a Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Simulating With Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Simulation Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Digital Multimeter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Watches (Simulator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Simulation Feedback Coloring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Simulator Tool Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Viewing Transient Graphs of Property Watches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Overview of Simulator Tool

The simulation tool allows you to perform various tasks.
• Test that the circuit you have drawn works correctly.
• Simulate individual failure modes within the circuit.
• Debug the behavior of component models.
• Run automated test scripts.
• Record a scenario consisting of a sequence of events

February 2016
Simulator Tool
Overview of the Simulator

The Simulator dialog box is split into the following secions.
• The top section contains the following buttons:

• Run simulation with current settings - Performs a simulation given the
selected switch states and failure modes.
• Qualitative/Numeric/External
Allows you to switch between a Qualitative (LC) or Numeric (DC) simulation, as

well as offering access to an external simulator if one has been configured using
Capital SimBridge (see “Capital SimBridge” on page 155 for more information).
The simulation types are only available if the appropriate simulation modules are
installed. Position the mouse cursor over the button and hold the mouse button down
to display a drop-down list of the available simulations.
• Perform transient simulation - Runs the selected simulators in transient mode.
• Reset simulation settings - Resets the failure modes, results tables, coloring
and simulation engine (but does not change the switch positions).
• Reset all - Resets the same as Reset simulation settings and also the switch
positions.
• Show diagram labels - Turns the display of the label names in the ECAD tool
on or off.
• Color components on diagram - Turns the coloring of components in the
ECAD tool on or off. See “Simulation Feedback Coloring” on page 54 for more
information.
• Show simulation watches - Displays a list of current watches in the Watched
Properties dialog box.
• Open the sequence recorder and start recording - Opens the sequence
recorder that you use to record a scenario consisting of a sequence of events.
• The middle section contains the following tabs:
• Events - Allows the switches (or other components with input properties) to be set.
See “Running a Simulation” on page 49.

February 2016
Simulator Tool
Robust Netlisting
• Failure Modes - Allows failure modes to be applied to components. See

“Simulating With Failures” on page 50.
• Simulation Displays - Allows additional simulation information to be displayed in
other windows. See “Simulation Displays” on page 51.
• Scripted Test - Allows a script to be constructed and run that tests the schematic.
See “Capital SimScript” on page 103.
• The bottom section contains a table that shows the results of the simulation. The table
has the following columns:
• Step - Displays the step number of the simulation. If a qualitative simulation has
been run, there may be a number of steps, each representing a moment it time.
• Description - Displays additional information about the step (the time stamp; which
components, if any, failed).
• Results - Displays which functions have been achieved (only if the functions
expressions for the design description have been defined).
Related Topics
Running a Simulation Simulating With Failures
Simulation Displays Simulation Feedback Coloring
Capital SimScript Simulator Tool Menus
Recording a Sequence of Events
Robust Netlisting
Typically, attempting to run a simulation on a scope containing errors (such as incomplete nets,
isolated content, missing attachments, etc.) will result in an error, in which case the simulation
will be aborted and the errors reported. In most cases, this functionality offers an opportunity to
rectify the errors before re-running the simulation, but that does not satisfy the needs of users
wanting to run simulations on incomplete complex electrical systems developed within Capital.
The Robust Netlisting option allows more issues with an incomplete/incorrect diagram to pass
without generating an error. Without Robust Netlisting turned on, dynamic simulation will
generate errors and the diagram must be fixed before running. See “Dynamic Simulation” on
page 59 for more information.
Note
Robust Netlisting is supported in all of the Capital Analysis simulation and high-level
analysis tools.
The following scenarios will be allowed when simulating with Robust Netlisting enabled:

February 2016
Simulator Tool
Robust Netlisting
• Incomplete Attachment - components missing an attachment will receive a “null”

attachment, allowing the simulation to run but will generate a warning. The resulting
simulation will take into account the missing attachment, generating appropriate results
and coloring the diagram accordingly.
Note
An incomplete attachment is not the same as a component having an attachment to a
component that can no longer be found in the database. An attachment to a missing
component will still result in an error that will not allow a simulation to run. The same is
true of attachments to encrypted components where no decryption key can be located;
refer to “Component Model Encryption” on page 253 for more information.
• Template Attachments - component model templates have no internal structure, and

hence cannot be simulated. Components with templates attached will be treated the
same way as if the attachment was missing: the simulation will run, the component will
be ignored for netlist generation and a warning will be raised.
• Missing power source - a scope with a missing power source (a scope without a positive
and/or negative node) will still result in an error; it will not be possible to run a
simulation. However, when using Capital SimBridge to pass a netlist to an external
simulator, it must be possible to pass a netlist with no component attachments. In this
scenario, any errors resulting from a missing power source will be reduced to warnings,
allowing the netlist to be passed for external simulation, however it will still not be
possible to run a qualitative or numeric simulation on the same scope.
• Floating Content - floating content includes any nets or components without a complete
connection to a circuit. This includes:
o Connectors connected solely to their mates - this will result in a disconnected island
of connectivity, all of which will be ignored when the netlist is generated, but a
warning will be raised instead of an error.
o A component with no connections - this component will be ignored when the netlist
is generated, and a warning will be raised.
o Disconnected islands of connectivity - the disconnected components and nets/wires
will be ignored when generating the netlist, and a warning will be raised.
This situation may arise when simulating a build list containing multiple designs.
One of the designs may be completely disconnected from all others, possibly
because another design has not been included in the build list, yet it will still be
possible to successfully simulate the remaining designs in the build list.
o A net or wire with only one connection - the wire or net will be ignored when the
netlist is generated, and a warning will be raised.

February 2016
Simulator Tool
Activating Robust Netlisting
This situation may occur when the wire is present on a design in a build list and
connects to another design that is not present in the build list. It will still be possible
to simulate the remaining designs.
Note
As most of these scenarios will result in the generation of warnings instead of errors, it
will be possible to deselect the Show warnings option on the Error Report Dialog and
remove them from the display. However, as operating in Robust Netlisting mode will
downgrade almost all common errors to warnings, it will not be possible to re-open the
error dialog to disable this option. If you wish to do this, either disable Robust Netlisting
temporarily, or close and re-open the current design to reset the option to the default
(warnings are displayed).
Related Topics

The option to toggle the Robust Netlisting option is available within your ECAD tool within the
Capital Analysis-specific icons on the ribbon:
• Click on the Enable Robust Netlisting ( ) icon to enable the Robust Netlisting
validation.
• Once the Robust Netlisting is enabled, the icon will switch to the Disable Robust
Netlisting ( ) icon. Click this to return to normal netlisting validation.
Related Topics
Robust Netlisting
Choose Log File Dialog Box

To access: Click the (Open) button to select the results output file. An existing file can
be appended to, or replaced by a new set of results. Click the OK button to begin the log,
otherwise click the Cancel button.
Used to create a log file of the results obtained from the Simulator. All of the simulation
information will be recorded in the selected log file.
Fields
Table 3-1. Choose Log File Dialog Box Contents
Field Description
OK Click to begin the log.

February 2016
Simulator Tool
Component Parameters
Table 3-1. Choose Log File Dialog Box Contents

Field Description
Cancel Click to cancel the log.
Related Topics
Component parameters are properties on component models that are of the type parameter. If
you are using the Simulator, you can change the parameters in the Component Parameter
dialog box.
Related Topics
Setting a Component Parameter
Setting a Component Parameter

You can set and modify the parameters prior to, or during the analysis to affect the behavior of
the model (for example, battery voltage, wire CSA or the voltage that a relay pulls in (VPull)).
Procedure
1. Select Edit > Component Parameters from the Simulator menu.
2. In the resulting dialog box, double-click the component that possesses the parameter you
wish to override.
3. Select the parameter in the list, the type and default value will be displayed to the right.
4. Type a new value into the Current Value box.
Note
Click the Reset button in the Parameter Values panel to reset the parameter to its default
value as specified in the component model.
Related Topics

February 2016
Simulator Tool
Local Expressions
Local Expressions
Local expressions provide a way of defining constants that are available to all of the component
models in the scope of the simulation. A component model can refer to this constant. An
example of this may be constants that are defined for address locations for devices connected to
a data bus.
Related Topics
Expression Editor Dialog Box
Expression Editor Dialog Box

To access: Expressions can be entered using the Edit > Local Expressions facility on the
Simulation Tool menu.
To enter an expression, type directly into the dialog box or use the point-and-click accelerators
on the right of the dialog.
Fields
Table 3-2. Expression Editor Dialog Box Contents
Field Description
Edit Box Enter the required expression
An example constant definition is:
const int CAN_BUS_MESSAGE_ID1 := 1001
Related Topics
Local Expressions
Overrides
The Numeric overrides facility is used to override the global numeric simulator settings for a
simulation.
The settings that can be overridden are:
• Active Current Threshold - the level of current that the simulator interprets as 'active'
and is used for coloring and when methods such as isActive are used in a component
models behavior.
• Short Circuit Current Threshold - the level of current, if this level is exceeded during
analysis, will flag overload or short circuit conditions.
• Open Circuit Resistance - the level of resistance the simulator will use to represent
open circuit conditions in the context of component models and failure conditions.

February 2016
Simulator Tool
Overriding Numeric Simulator Settings
• Short Circuit Resistance - the level of resistance the simulator will use to represent
short circuit conditions in the context of component models and failure conditions.
Related Topics

You can override the Numeric Simulator settings.
Procedure
1. Select the Edit > Overrides option from the Simulator menu.
2. Check the box of the field that you would like to override.
3. Enter the new value for the overridden value.
Related Topics
Overrides
Power Node
The Power nodes for failure application dialog is used to select the power node that short to
battery failures use.
There are several options available:
• Use any available battery - essentially an 'I don't care which battery is used' option,
uses the first battery the simulator finds and shorts to its positive terminal.
• Use the highest rated battery - shorts to the positive terminal of the battery that has the
highest voltage.
• Use the lowest rated battery - shorts to the positive terminal of the battery that has the
lowest voltage.
Related Topics
Setting the Power Node
Setting the Power Node

You can set the Power Node.

February 2016
Simulator Tool
Procedure
1. Select the Edit > Power Node option from the Simulator menu.
2. Select the desired battery.
Related Topics
Power Node

The Scenario Sequencer dialog box enables you to record a scenario consisting of a sequence
of events. This scenario is saved as an object in the database and Capital Stress Analyzer can
reference this scenario as a basis for a stress analysis.
The access the Scenario Sequencer by clicking the Open the sequence recorder and start
recording button at the top of the Simulator.
Recording a Sequence of Events as a Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Deleting an Event from a Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Opening an Existing Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Pausing a Recording Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Recording a Sequence of Events as a Scenario

The sequence of events in an open scenario is updated automatically as you simulate events in
the Simulator. If required, you can leave the Scenario Sequencer open but pause the recording
while simulating events.
Procedure
1. Click the Open the sequence recorder and start recording button at the top of the
Simulator to display the Scenario Sequencer dialog box.
2. The switch settings from the Simulator are displayed in the Sequence window. If you
want to change these settings for the start of the scenario, you can change them in the
Sequence window.
3. You can insert events into the sequence in the following ways:
• Make a change in the Event pane of the Simulator and click either the Run
simulation with current settings button or the Open the sequence recorder and
start recording button at the top of the Simulator. The event is added at the end of
the sequence.

February 2016
Simulator Tool
• Click an event in the sequence and click the Insert Event button on the Scenario
Sequencer to add an event below the selected event. Ensure that the new event is
selected in the Scenario Sequencer and make a change in the Event pane of the
Simulator. Click either the Run simulation with current settings button or the
Add event without doing another simulation button at the top of the Simulator.
The new event is updated with the change from the Simulator.
4. Select each event in turn and specify whether you want the event to occur after the
previous event has stabilized or after a certain period of time after the previous event. If
you uncheck the upon Stabilization box, the After box is enabled and you can specify a
period of time and select a unit of time from the drop-down list.
5. Select either the File > Save or File > Save As menu option.
6. The Select location dialog box is displayed. In the tree, select the folder location where
you want to save the scenario file. Note that you can select a folder and click the Create
sub-folder button to create a sub-folder below it. In the Object field, specify the name
of the scenario and click the Save button.
Note
You can use the Object Manager tool to view a scenario in read-only mode.
Deleting an Event from a Scenario

Events can be deleted from scenarios
Procedure
1. Click on the event in the Scenario Sequencer and click the Delete Event button.
2. The event is deleted from the scenario.
Opening an Existing Scenario

You can open saved scenarios.
Procedure
1. Click the File - Open menu option.
2. The Select sequence dialog box is displayed. In the tree, click on the scenario that you
want to open and click the Open button. You can check the Read-Only box if you want
to open the scenario in read-only mode.
3. If you are editing the scenario, insert or delete the events as required.

February 2016
Simulator Tool
Running a Simulation
Pausing a Recording Sequence

You can pause a recording while Running the Simulator.
Procedure
1. Click the Stop recording data to the sequence button on the Scenario Sequencer.
2. The recording of the scenario is paused. To restart the recording, click the Start
recording data to the open sequence button.
Running a Simulation
This topic gives detailed steps on runnnig a simulation.
Procedure
1. Set the analysis scope.
2. Press Space Bar and enter Simulator.
3. Click the Event tab.
4. Select the switch positions. You open a switch by clicking open and close a switch by
clicking closed.
5. Click the Simulate button. A progress dialog is displayed, titled with the name of the
selected scope, and with a progress bar indicating that the simulation is underway.
Note
You can cancel the current simulation by clicking the button to the right of the
progress bar.
After a moment the ECAD tool schematic will be colored and any open Simulation
Displays will change to reflect the new state of the circuit.
Note
If the analysis scope is a Capital Integrator plane and wiring synthesis has been
performed, then an additional dialog will appear when starting the Simulator requesting
the configuration to analyze. Select one from the list.
The simulation mode options are selected in the centre panel, (they are license dependant):
• Qualitative - the simulation will be based on the LC or Logical Current simulator.

• Numeric - the simulation will be based in the DC simulator, a dc simulation.

February 2016
Simulator Tool
Simulating With Failures
• External - the simulation will use an external simulation technology supported via the
Capital SimBridge. See “Capital SimBridge” on page 155 on configuring an external
simulator.
Checking the Use Transient box will run the simulators in transient mode. When this is mode
selected, extra information is required for the transient run - click the Simulate button to open
the Transient settings... dialog box.
You must specify the following temporal information:
• Start time - the time that the transient run should start at (defaults to zero).
• Stop time - the time that the transient analysis should run to.
• Sample time - the sample rate at which the results will recorded.
• Variable Time Steps - the mode of operation of the numeric transient simulator, where
the simulation engine automatically determines the sample rate of the results.
Enter the settings by typing into the boxes. You can specify the temporal magnitude using the
drop-down lists to the right of each box.
Related Topics
Simulating With Failures Simulation Displays
Capital SimScript Local Expressions
Component Parameters Overrides
Power Node Simulation Feedback Coloring
Simulator Tool Menus Scoping

To simulate a circuit with a failure mode present, you must select one or more failure modes by
clicking the Failure Modes tab at the top of the simulator window. The Components list
displays the folders containing components. Click a folder to view its components and click the
component icons to view their possible failure modes on the right. Select the required failure
mode for each component by clicking its box in the Setting column of the Current Settings
list.
To run a simulation with the selected failure mode, click the Event tab and select the switch
states you wish to simulate with the failure mode present. Click the Simulate button to see what
happens when the circuit is simulated with the failure present.

February 2016
Simulator Tool
Simulation Displays
Related Topics
Overview of Simulator Tool Simulation Displays
Capital SimScript Running a Simulation
Component Parameters Overrides
Power Node Simulation Feedback Coloring
Simulator Tool Menus Scoping
Simulation Displays
The Simulation Displays tab enables additional information to be displayed for selected
components in the design description.
Note
If a component involved in the simulation is encrypted, the option to view the
component’s structure and behavior will be disabled, only external component interfaces
will be displayed and only external node information will be displayed. See “Component
Model Encryption” on page 253 for more information on working with encrypted
components.
Several types of information can be displayed:
• Show structure - displays information about the activity in-terms of the component’s
structure.
• Show behavior - for those components whose behavior is implemented using state
machines, the current active states can be displayed.
• Show properties - for those components with input or output properties, the values of
those properties can be displayed. In addition, the current values of nodes and arcs used
in the evaluation of the components behavior are also shown. As are the values of
variables used in State Machines.
• Show multimeter - displays a Digital Multimeter window showing arc and node
currents and voltages.
• Show buffers - displays the contents of any data buses buffers.
• Show activity - displays the data bus activity.
• Show watches - displays a list of watched component properties.
• Show graphs - displays a graph of the values for watched component properties plotted
against simulation time. See “Viewing Transient Graphs of Property Watches” on
page 56 for more information about the graphs. This is enabled only if you are running a
transient simulation.

February 2016
Simulator Tool
Digital Multimeter
These facilities are extremely useful for debugging the component models. Not that some of
these options are license dependant.
An example of the Show properties window and the other available options is displayed
below:
If required, you can have several simulation displays open simultaneously.

If you select a component with a state based behavior, the Show behavior button will become
available. When this button is clicked, the NORMAL_OPERATION state machine will be
displayed for that component. This will display the current active state for the simulation step.
Individual simulation displays can be closed at any time. Note that when the Simulator is
closed, all simulation displays will be closed.
Digital Multimeter
This display enables you to view the results of the Numeric simulation for the component you
selected in the Simulator.

February 2016
Simulator Tool
Watches (Simulator)
The display shows the result either with the usual suffixes, or in scientific notation. Use the
drop-down list at the bottom of the dialog box to display the component's electrical property.
Related Topics
Watches (Simulator)
It is possible to watch individual component properties by adding them to a watch list. This
facility enables you to monitor the important electrical conditions of devices in one list.
Watches are set in the Property Viewer window.
To set a watch, double-click on the component's property, a watch icon will appear to the left of
it (as shown above for CONTACT.R).
To view all current watches, click on the Show simulation watches button at the top of the
Simulator. The list of watches will appear in the Watched Properties dialog box.
The Watched Properties dialog box contains a table with the following columns:
• Property - the component and the property being watched.

• Value - displays the value of the property.
• Change - describes the range of change, if the property type is a number.
Red highlighting indicates a change has occurred in the property value since the previous
simulation step.

February 2016
Simulator Tool
Simulation Feedback Coloring
Related Topics
Overview of Simulator Tool Simulating With Failures
Capital SimScript Simulator Tool Menus
Simulation Feedback Coloring

During a simulation, conductors and devices (in Capital Logic) and bundles and slots (in Capital
Integrator) are displayed in varying colors to indicate the state of the object. Colors are assigned
a priority, meaning that electrical objects to which multiple states apply are colored according to
the state with the highest priority.
For example, a bundle containing wires, one of which is active while another is inactive, is
colored blue (indicating the presence of the active wire).
The following example shows an active simulation of a Capital Integrator plane:
Figure 3-1. Simulation Feedback Coloring
Refer to the following table for a list of colors and their meanings:

February 2016
Simulator Tool
Simulator Tool Menus
Table 3-3. Simulation Feedback Colors

Priority Color Meaning
1 Red The object contains a short.
2 Yellow The object contains a failure.
3= User-defined User-defined colors can be configured to display information
beyond the core simulation feedback. Refer to “Simulation
Highlighting” on page 275 for more information. Note that
user-defined colors are prioritized according to the order in
which they are created; where a priority clash occurs, a
warning is displayed in the output window.
4 Green The object is electrically active.
5 Blue (Cyan) The object is electrically inactive.
Simulator Tool Menus

This topic describes the available tools menus.
File Menu
• Log Results - the log entry is only displayed if Capital SimScript is installed.
• Print Preview - opens a window which displays the page format and allows you to
change the printer settings.
• Print - prints all of the simulation information.
• Exit - exits the Simulator tool. Will also close any simulation displays still open.
Edit Menu
• Local expressions - specifies expressions (such as constants), that will be in the scope
of the design being simulated. See “Local Expressions” on page 45 for more details.
• Component parameters - overrides the component model parameters. See
“Component Parameters” on page 44 for more details.
• Transient Settings - specifies the transient settings for a transient simulation. See
“Running a Simulation” on page 49 for more details.
• Overrides - overrides the global settings for numeric simulation. See “Overrides” on
page 45 for more details.
• Power Node - used to select the power node for simulation (for short to power failures).
See “Power Node” on page 46 for more details.

February 2016
Simulator Tool
Viewing Transient Graphs of Property Watches
• Evaluate Rules - check this box if you want to evaluate rules when running the
Simulator. Any print statements from rules will be displayed in the Console when you
run a simulation.
• Evaluate Actions - check this box if you want to evaluate actions when running the
simulation. Any print statements from actions triggered by rules will be displayed in the
Console when you run a simulation.
• Options - opens the Options dialog box. See “Edit Options Dialog” on page 269 for
more details.
Utils Menu
• Reset - resets the simulation (but does not change the switch settings or applied failure
modes).
• Reset All - resets the simulation (will reset switch settings to their defaults and unset
any failures applied).
View Menu
• Console - displays the Console where all the print messages in component models
appear.
• Netlist - produces a netlist for the design description being simulated.
• Functional Expressions - displays a summary of any functional or sneak expressions
that have been set.
• Netlist Errors - displays any errors produced when creating a netlist. If you are denied
the ability to run a simulation, this option will help to explain why.
• Generated Models - displays any dynamically generated models, such as connectors,
that have nothing attached by the user.
Related Topics
Overview of Simulator Tool Simulating With Failures
Running a Simulation Simulation Displays
Viewing Transient Graphs of Property

Watches
If you are running a qualitative or quantitative simulation in transient mode and you have set
watches for component properties, the Show graphs button on the Simulation Displays of the
Simulator is enabled. Clicking this button displays a Component Property Watches facility
with a graph of the values for the watched properties plotted against simulation time.

February 2016
Simulator Tool
If you keep the graph open and run the simulation again, the graph updates accordingly. If you
exit the Simulator, the Component Property Watches facility also closes.
The graph facility is resizable and is divided into two parts:
• Key - this lists the component property watches from the simulation and indicates the
color that is used for that watch on the graph. The name of each simulation consists of
the component name and the name of the property that is being watched.
• Graph - The Y-axis of the graph shows the property values and the X-axis shows the
simulation time.
The Key
The key can be hidden or shown by clicking the arrows at the top right corner of it.
Although all watches from the simulation are listed, only 9 can be displayed on the graph at any
one time. Those not currently displayed on the graph have a gray square.
Note
The key cannot display watches with voltage values alongside watches with current
values.
If watches of both types have been set before you display a graph and the first watch set
has voltage values, watches with current values are not displayed in the key, and vice
versa. In this scenario, watches with current values will only be displayed after all
watches with voltage values have been stopped.
If the graph key is displaying watches with current values and you start watches with
voltage values, the watches with voltage values will not be displayed in the graph key
until all watches with current values have been stopped.
Common Watch Actions

Removing a Watch from the Graph
Right-click on the watch name and select the Remove from graph option from the pop-up
menu.
Right-click on the watch name and select the Edit Plot Style option from the pop-up menu to
display the Plot Style dialog. Check the Do not render this plot box.
Adding a Watch to the Graph

Right-click on the watch name and select the Add to graph option from the pop-up menu.

February 2016
Simulator Tool
Editing the Plot Color for a Watch

Right-click on the watch name and select the Edit Plot Style option from the pop-up menu to
display the Plot Style dialog. Alternatively, double-click the color block to display the Plot
Style dialog where you can specify the color that you want to use.
The Graph
Data-capture points (points at which data was sampled in the simulation) are displayed as small
squares along the lines on the graph. If you position the mouse cursor over a data-capture point,
the exact property value and the simulation time are displayed. If the key for the graph is
hidden, the name of the watch is also displayed. When multiple watches have the same value at
the same simulation time, all of the watch names are displayed.
The View menu enables you to use zoom controls to view different part of the graph (these
controls are also available by right-clicking on the graph window):
• Zoom In and Zoom Out change the scale of the diagram incrementally. You can also
do this by rolling the mouse wheel.
• Zoom All re-scales the graph window to show the entire graph. When the entire graph is
not visible in the graph window, scroll bars along the sides enable you to move around
the graph.
Note that there is a gap between the axes and the start of the graph. This is to help distinguish
between the axes and the lines plotted on the graph.
Related Topics

February 2016
Chapter 4
Dynamic Simulation
The dynamic simulation capabilities of Capital Analysis offer you numerous benefits in terms
of analysis when working on electrical designs. Dynamic simulation offers some of the
simulator tool's capabilities but presented in a way to aid workflow.
It is embedded within the Capital Logic application so that it can run in the background as you
work with the design. When you add devices and connectivity, the design is simulated
automatically. By placing the mouse cursor over the design, you can directly change input
conditions and view output conditions of the devices and connectivity. Dynamic Simulation has
the advantage that serious design errors, such as short circuits, are picked up immediately if
they are introduced in the design.
Further feedback about the operational state of the design is displayed as achieved functions (as
in the Simulator) in the Output Window in the Capital Logic application.
Starting Dynamic Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

On-Demand Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Watches (Dynamic Simulation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Viewing Device Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Viewing Embedded Component Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Setting a Failure Against a Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Output Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Analysis Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Audit Report Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Starting Dynamic Simulation

This topic details how to enable dynamic simulation for a design.
Procedure
1. With the design to simulate open, click the Analysis Tab.
2. Click the Set Scope icon ( ) and select the design name from the dropdown list.
3. Specify either Qualitative or Numeric Simulation from the simulation type icon ( )
dropdown list. If you have an external simulator configured, that option is also
available; see “Capital SimBridge” on page 155 for more information.
4. Click the Background Simulation icon ( ).

February 2016
Dynamic Simulation
On-Demand Operation
Note
The simulation feedback provided during dynamic simulation is the same as that offered
within the Simulator Tool; see “Simulation Feedback Coloring” on page 54 for more
information.
Results
• The simulation engine starts.
• To disable dynamic simulation, simply click the Disable Simulation icon ( ). The
simulation engine shuts down.
• You can cancel the current simulation by clicking the button to the right of the
progress bar. If you do cancel a simulation while running dynamic simulation, you will
be switched into On-Demand Operation.
Related Topics
On-Demand Operation Watches (Dynamic Simulation)
Viewing Device Properties
On-Demand Operation
Another way to run simulation on a design while working on it is on-demand simulation.
Similar to background simulation, setting this mode of operation starts the simulation engine in
the background, but in this case, the simulation is not run until you click the button. This
mode may be preferable when working with exceptionally large designs, where waiting for the
simulation to update after a design change may not be acceptable.
Note
The button is not enabled until design changes have been made that require
simulation.
Related Topics
Starting On-demand Operation
Starting On-demand Operation

This topic details how to enable on-demand simulation for a design.

February 2016
Dynamic Simulation
Watches (Dynamic Simulation)
Procedure
1. With the design to simulate open, click the Analysis Tab.
2. Click the Set Scope icon ( ) and select the design name from the dropdown list.
3. Specify either Qualitative or Numeric Simulation from the simulation type icon ( )
dropdown list. If you have an external simulator configured, that option is also
available; see “Capital SimBridge” on page 155 for more information.
4. Click the On Demand icon ( ).
Results
• The simulation engine starts.
• Once on-demand operation has been started, you can trigger the simulation of the
selected scope by clicking the button at the bottom of the Analysis Tab.
• You can cancel the simulation at any time by clicking the button to the right of the
progress bar.
Related Topics
On-Demand Operation Watches (Dynamic Simulation)

A watch allows you to monitor a particular property of a component (as defined by its
simulation model) without having to hover over that component.
A watch will also highlight when the property it is monitoring changes. The following topics
explain how to set, delete and inspect watches.
Adding Watches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Feedback on Watch Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Watch Persistence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Adding Watches
This topic details how to set a watch on a component property.
Prerequisites
Before you can set a watch on a property, simulation output must be available. This means that
either:

February 2016
Dynamic Simulation
• Background simulation must be enabled, or

• On-demand simulation must be enabled, and a simulation triggered
Procedure
1. Position the mouse pointer over the component for which you want to set a watch. A
tooltip is displayed.
2. Click the Properties button. The Properties For... dialog is displayed, with its title
appended with the name of the selected component. All properties for the component are
displayed.
3. Select the property for which you want to set a watch.
4. Click the Watch Selected button.
Results
• The property is added to the watches table in the Output Window.
• To remove a watch, highlight the row in the watches table of the Output Window that
you wish to remove, and then press the Delete key or press the Stop Watching button.
Related Topics
Starting Dynamic Simulation Viewing Device Properties
Feedback on Watch Changes

During a simulation, the values of the properties will change. This will be highlighted in the
watch table by coloring the changed properties red.
Figure 4-1. Watch Information
When a simulation is running in numeric mode, the amount of the change will also be shown in
the column.
Watch Persistence
Capital Analysis remembers the properties you have chosen to watch for the duration of your
session in the authoring tool. For example, you can stop a simulation, alter a model, and restart

February 2016
Dynamic Simulation
a simulation without losing your specified watches. However, if Capital Logic were to be
closed, then the watches will be lost.
Related Topics
Adding Watches

All simulatable components, devices and conductors in a design can be inspected to view their
properties.
Prerequisites
Before you can view device properties, simulation output must be available. This means that
either:

Procedure
1. Hover your mouse pointer over the entity you want to inspect. A tooltip is displayed.
Note
If you are performing a numeric simulation, the tooltip can be used to display component
variables, if the behavior of the attached model has been scripted to do so.
2. Click the Properties button. The Properties For... dialog is displayed, with its title
displayed.
Related Topics
Starting Dynamic Simulation On-Demand Operation
Viewing Embedded Component Properties

Embedded components can be inspected to view their built-in and interface properties.
Prerequisites
Before you can view component properties, simulation output must be available. This means
that either:

February 2016
Dynamic Simulation

Procedure
1. Hover your mouse pointer over the entity you want to inspect. A tooltip is displayed.
Note
If you are performing a numeric simulation, the tooltip can be used to display component
variables, if the behavior of the attached model has been scripted to do so.
2. Click the Properties button. The Property View dialog is displayed, with its title
displayed as shown in Figure 4-2.
3. If required, you can set a watch on a property by clicking the Watch Selected button. To
remove a watch, highlight the row in the table and press the Stop Watching button.
Figure 4-2. Embedded Component Properties Report
Related Topics
Defining a Component Interface On-Demand Operation

February 2016
Dynamic Simulation
Setting a Failure Against a Device
Setting a Failure Against a Device

While running a dynamic simulation, you can trigger device failures, immediately viewing the
system response to the change.
Prerequisites
Before you can set a failure against a device, simulation output must be available. This means
that either:

Procedure
1. Hover your mouse pointer over the entity in which you want to trigger a failure. A
tooltip is displayed.
2. The Failures section of the tooltip offers all failures available. Select the failure to
apply; the results are displayed immediately, both in the Messages tab of the output
window, and in the design coloring.
A failure can be removed by deselecting the option against the device.
Related Topics
Output Window
If you have selected the Capital Analysis tab in the output window, you can select one of the
following tabs to view information.
• Messages
Displays information about achieved functions, failed functions, failed components and
watched properties.
• Console
Displays information, such as messages from the analysis models, in a similar way to
the Simulator's console.
• Errors
Displays any errors that have been generated by a simulation.

February 2016
Dynamic Simulation
Analysis Tab
Additionally, on the right of the output window, all active watches are displayed. See “Watches
(Dynamic Simulation)” on page 61 for more information.
Related Topics
Analysis Tab
This set of functions, located on the Analysis tab of the Capital Logic design browser, acts as a
control center for all dynamic simulation functions, as well as providing a number of shortcuts
to the other simulation tools.
Tip: The Analysis tab can be detached from the design browser and used as a separate
window. To do this, click on the tab and drag it away from the browser; once detached,
you can position it anywhere. To restore the tab, click the close button to close the
window.
Analysis Tab Toolbar

The following options are available:
Table 4-1. Analysis Tab Toolbar Icons

Icon Function Description
Set Scope Allows you to set the simulation scope to any design or
build list in the project.
Set Qualitative/Transient Allows you to run the simulation in Qualitative or
Simulation Type Transient mode. If you have an external simulator
configured, that option is also available; see “Capital
SimBridge” on page 155 for more information.
Background Simulation Begins the simulation action, resulting in simulation
feedback being displayed continually as edits are made
to the design.
On Demand Prepares the simulator to run upon pressing the
Simulate button.
Disable Simulation Turns off all simulation actions currently running.
Record Macro Displays the Scenario Sequencer dialog, allowing you
to record a sequence of simulation steps for reuse. See
“Recording a Sequence of Events” on page 47 for more
information.

February 2016
Dynamic Simulation
Analysis Tab
Table 4-1. Analysis Tab Toolbar Icons

Icon Function Description
Display Console Displays the Console view within the Capital Analysis
tab of the Output Window.
Display Watches If the Capital Analysis tab of the Output Window is
not visible, clicking this button displays it.
Toggle Robust Nelisting Enables the Robust Netlisting actions, allowing
partially complete designs to be simulated successfully.
Simulation Type Shortcuts Offers a quick link to the following simulation tools:
Simulator, Capital SimCertify, CapitalSimProve,
Capital SimStress and Export Netlist.
Simulation Controls
The grid in the middle of the Analysis tab displays all of the input interfaces available on the
analysis models attached to components in the design. By setting the state of these inputs, you
can control the flow of current within the system during simulation. The grid displays all
devices and components with attachments; the following icons are used to identify the
attachment types:
• A red dot on a device icon indicates that it has a manual analysis model attachment.
• A blue dot on a device icon indicates that it has an automatically generated analysis
model attachment.
To set the state of an input, select one of the available states from the dropdown list to the right
of the device/component name.
Functions Browser
If a project has a project model assigned, this field offers a tree menu displaying all configured
functions and outputs.
See “Capital SimProject” on page 91 for more information on configuring and associating an
analysis project.
The three icons beneath the browser allow you to filter the displayed content against the
following categories:
• Function inputs/outputs
• Active functions/sneak functions/failures
• All functions/scoped functions

February 2016
Dynamic Simulation
Audit Report Tab
Related Topics
Audit Report Tab

The Audit Report tab appears once a scope is set, or the Analysis tab is clicked. It will be blank
until an audit report has been generated in one of the Analysis tools.
The report shows all the audit reports generated for designs and build list under that project. It
also creates a verification snapshot of the design, which you can use to study the design impact
between each subsequent snapshot to improve the quality of the design. It also provides a
convenient method of release approval, as well as traceability of the audit trail.
Generated reports are accessible both from the tab, and in the Object Manager - where you can
view report information on the analysis operation, the scope of its analysis and detailed scenario
information.
Double-click on a report within the tab to view its contents. For further information see “Audit
Reports” on page 35.

February 2016
Chapter 5
FMEA Editor (Capital SimCertify)
The FMEA editor is provided as part of the Capital Analysis system giving the engineer the
facility to view, edit and annotate the results of different FMEAs. When the results of an FMEA
are loaded into the FMEA Editor each entry can be examined on screen and amended if
necessary.
Overview of FMEA Editor (Capital SimCertify) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Editing and Appending an FMEA Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Header of FMEA Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Viewing the FMEA Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Printing an FMEA Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Exporting an FMEA Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Simulating a Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Menu Bar Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Overview of FMEA Editor (Capital SimCertify)

The FMEA editor has a number of useful features:
• it can show the FMEA results in different formats.
• it can invoke and run the circuit simulator to show the state of the failed circuit.
• it can print out the FMEA results.
• it can export the FMEA results to FmeaPlus, PostScript, HTML and other formats.
The FMEA editor can be invoked automatically following the generation of results for a
particular scenario. Before the FMEA scenario is run, a box can be selected that is located in the
bottom left hand corner of the Run Scenario Wizard dialog, the box is selected by default. By
ticking the box, the FMEA editor will be automatically invoked with the results loaded when
the generation is complete.
If an engineer wishes to review an FMEA report some time, later there are 2 ways in which
the FMEA editor can be invoked. The easiest way is to press Space Bar and enter FMEA Editor.
This will invoke an empty FMEA editor window into which the engineer can load the desired
results. This is done by selecting "Open" from the File menu or clicking the button on the tool
bar and selecting the relevant file from the dialog.

February 2016
FMEA Reports
Alternatively, it can be activated from the Capital Analysis FMEA tool window by highlighting
the desired FMEA and then clicking the "Edit" button located on the tool bar.
FMEA Reports
There are a number of ways an FMEA report can be viewed and edited:
• Editing and appending the report (see “Editing and Appending an FMEA Report” on
page 70).
• Viewing and editing the header of the report (see “Header of FMEA Report” on
page 71).
• Viewing the report (see “Viewing the FMEA Report” on page 72).
• Printing the report (see “Printing an FMEA Report” on page 73).
• Exporting the report (see “Exporting an FMEA Report” on page 73).
• Simulating a record in the report (see “Simulating a Record” on page 75).
Related Topics
Menu Bar Contents
Editing and Appending an FMEA Report

The FMEA editor has capabilities to edit the entries in a record, add new records and to delete
old records.
Procedure
1. Entries in the Report can be edited by selecting them and entering the new contents of
that cell. Some cells must however have specific entries; sev, occ, det (severity,
occurrence and detection) must be specified as integers from 1 to10. The rpn column is
also not editable as it is defined as the product of the three sev, occ and det values.
2. New records can be added by selecting Edit > Add row, this will add a row below the
selected line. Rows can be removed by selecting Edit > Delete row, this will confirm
whether the selected result should be deleted before deleting it. Rows can also be edited
using the Cut, Copy and Paste buttons. They work in the usual way and are found in the
edit menu and in the tool bar.
Related Topics
FMEA Editor (Capital SimCertify) Header of FMEA Report
Viewing the FMEA Report Printing an FMEA Report

February 2016
Header of FMEA Report
Exporting an FMEA Report Simulating a Record

Menu Bar Contents
Header of FMEA Report

The FMEA header contains general details about the report. It can be viewed and edited by
selecting Edit > Edit Header. The dialog is shown below.
The details in the header are as follows:
• FMEA number - the number of the FMEA report.

• FMEA date - the date the report was created.
• Key date
• System - The electrical system the FMEA is based on.
• Product
• Prepared by
• Responsibility
• Core team
• Extra information

February 2016
Viewing the FMEA Report
If the FMEA report was created by Capital Analysis then the FMEA date and System boxes
will have been completed automatically.
The dialog can be closed by pressing Cancel which discards the changes or by pressing OK to
save any changes that have been made.
Related Topics
Viewing the FMEA Report

The FMEA editor provides two methods for sorting and viewing the report. It is possible to
apply filters to only view a selection of the results and it is also possible to sort the results
according to their properties.
Filtering the Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Ordering the Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Filtering the Results

To filter the records select View > Filter results..., this will open the FMEA Report Filters
dialog.
This dialog allows you to add and remove your own filters to and from the FMEA report. The
filters that are applied to the report are displayed in box at the top of the window.
Firstly select Add Filter to create a filter. Next define the filter by selecting from the two pick
lists and typing appropriate filter text in the text box. The first pick list selects the category to be
filtered and the second pick list selects the operator. Depending on the category you have
chosen the operator pick list will change appropriately to suit the category.
When the Invert Results check box is checked, the opposite of the filtered results will be
displayed.
To remove a filter highlight it in the box at the top of the window and click Remove Filter.
All the filters can be removed by selecting View > Remove All Filters from the menu. This
will return the FMEA Editor to showing all of the results.
Ordering the Results

The FMEA editor can order the FMEA results in a number of different ways. Select the Order
menu and one of the following options:
• Default Order - shows the rows in the order they were created.

February 2016
Printing an FMEA Report
• Order by Name - orders the rows alphabetically according to the name column (e.g.
MOTOR_1 before RELAY_3 before WIRE2).
• Order by Failure - orders the rows alphabetically according to the failure column (e.g.
short circuit before short to ground).
• Order by Occurrence - orders the rows according to the occurrence column.
• Order by Rpn - orders the rows according to the RPN values.
• Order by Severity - orders the rows according to the severity values.
• Order by Detection - orders the rows according to the detection values.
Related Topics
FMEA Editor (Capital SimCertify) Editing and Appending an FMEA Report
Header of FMEA Report Printing an FMEA Report
Menu Bar Contents
Printing an FMEA Report

The Print and Print Setup options on the File menu are not currently implemented. Therefore to
print a FMEA report it must be first be exported to PostScript format and sent to a laser printer.
To transform the results of an FMEA into PostScript select File > Export..., this will invoke the
Export dialog from which Fmea to PostScript should be selected (see “Exporting an FMEA
Report” on page 73).
Related Topics
Header of FMEA Report “Viewing the FMEA Report” on page 72
Menu Bar Contents
Exporting an FMEA Report

The FMEA report can be exported to a number of different formats:
• FMEAplus Import Format (.f2f)
• PostScript (.ps) - for printing to a PostScript printer.

February 2016
Exporting an FMEA Report
• HTML (.html) - for publishing on a web page.

• XML (.xml) - for doing any post processing.
• Rich Text Format (.rtf) - for editing using a word processor.
• Data Interchange Format (.dif) - for inclusion into a spreadsheet program or database.
• Comma Separated Variables (.csv) - for inclusion into a spreadsheet program or
database.
• Plain Text (.txt) - for other reasons.
• SQL Export (.xsql) - for moving object to other databases.
Procedure
1. Select File > Export from the menu of the FMEA Editor. This will invoke the Export
FMEA dialog where the desired selection can be made.
2. After selecting the export you require and clicking the Next button, you can select the
orientation of the export:
o Function: all the failures which cause each function to fail or be archived
unexpectedly are grouped together. Within each function, the failures will be
ordered in the specified sort order.
o Failure: list the failures in the specified sort order.
o Effect: all the failures which have the same effect are grouped together. Within each
function, the failures will be ordered in the specified sort order.
o Symptom: all the failures which have the same symptom are grouped together. This
is useful for diagnositics.
3. The sort order for the export must also be selected:
o rpn (highest rpn number first - descending)
o severity (highest rpn number first - descending)
o name (component name in alphabetical order - ascending)
o failure (component failure in alphabetical order - ascending)
4. After selecting the orientation and the sort order, clicking the Next button allows the
engineer to select the where the exported file will be placed.
5. Using the Browse button, the name and location of the exported file can be specified.
6. Clicking the Next button will now export the file.
7. Click Close to finish.

February 2016
Simulating a Record
Note
The FMEAplus export will only work on FMEA reports opened from the FMEA Tool
(see “Overview of Capital SimCertify” on page 79). This is because additional
information is required (like the FunctionModel attached to the Subsystem) that is only
available there. Other exports will work on FMEA reports saved outside the FMEA Tool
but some information may be missing (like the event sequence information). It is,
therefore, recommended that all exports of FMEA reports generated by Capital Analysis
be done via the FMEA Tool.
For FMEA reports generated by hand, the FMEAplus export will also fail. All other
exports will work, however.
In failure orientation, all the failures will appear in the exported file even if they have no
effect on the schematic (they do not result in an functions being achieved unexpectedly or
spontaneously). Such failures will have an RPN of 1 (as the occurrence, severity and
detectability values will be set to one). Ordering by RPN will therefore place these
failures at the end of the FMEA.
In function orientation, those the failures that do not have an effect on the schematic will
not appear in the exported file.
Related Topics
Header of FMEA Report Viewing the FMEA Report
Printing an FMEA Report Simulating a Record
Menu Bar Contents
Simulating a Record
It is quite possible that engineers analyzing a FMEA report will find it useful to have a facility
where a specific record in the report can be simulated.
Procedure
1. Select the FMEA report record by clicking on it.
2. Select the View > Simulate Record.... The Simulate FMEA Record window is
displayed.
The window presents the information summarized in the record in a more detailed way.
The top section of the window has the toolbar and the potential failure cause together
with the RPN information.

February 2016
Menu Bar Contents
The text frame in the center of the window shows the individual steps of the scenario,
together with the expected functions and the actual functions that were achieved at each
step.
3. The engineer can then:
o Select one of the event lines.
o Select to view the expected or actual simulation.
o Click the button to view the colored simulation in the Ecad tool.
Note
The results of the analysis will vary according to whether the original simulation was run
with Robust Netlisting enabled. Refer to “Robust Netlisting” on page 41 for more
information.
Related Topics
Printing an FMEA Report Exporting an FMEA Report
Menu Bar Contents
Menu Bar Contents

The following section describes the menu bar contents of the FMEA Editor.
File Menu
• New - creates a new report.
• Open... - opens a chooser to load a saved report (see “Open/Save Object Dialog” on
page 265).
• Save - saves the current report.
• Save As... - opens a chooser to save the report as another object (see “Open/Save Object
Dialog” on page 265).
• Import... - imports a report from a file (.xsql file)
• Export... - exports the report to a file (see “Exporting an FMEA Report” on page 73).
• Close - closes the current report.
• Exit - exits the FMEA editor.

February 2016
Menu Bar Contents
Edit Menu
• Cut - cuts the selected row.
• Copy - copies the selected row.
• Paste - pastes the selected row.
• Add row - adds a new row below the selected line. See “Editing and Appending an
FMEA Report” on page 70 for more information.
• Delete row - deletes selected row from the report. See “Editing and Appending an
FMEA Report” on page 70 for more information.
• Edit Header... - allows the engineer to edit the header file of the report (see “Header of
FMEA Report” on page 71).
• Options... - opens the edit options dialog. See“Edit Options Dialog” on page 269 for
more information.
View Menu
• Reload FMEA - reloads the FMEA report discarding the changes that have been made.
• Filter results - opens a dialog allowing the engineer to filter the results (see “Filtering
the Results” on page 72).
• Remove filter - removes any filter that is currently on the results.
• Simulate Record... - simulates the selected record (see “Simulating a Record” on
page 75).
Order Menu
• Default Order - shows the rows in the order they were created.
• Order by Name - orders the rows alphabetically according to the name column.
• Order by Failure - orders the rows alphabetically according to the failure column.
• Order by Occurrence - orders the rows according to the Occurrence values.
• Order by Rpn - orders the rows according to the RPN values.
• Order by Severity - orders the rows according to the severity values.
• Order by Detection - orders the rows according to the detection values.
See “Ordering the Results” on page 72 for more information about ordering the report.

February 2016
Menu Bar Contents
Related Topics
Printing an FMEA Report Exporting an FMEA Report
Simulating a Record

February 2016
Chapter 6
Capital SimCertify
This chapter details Capital SimCertify and the FMEA Scenario Tool, which are used when
running an FMEA using the Capital Analysis system.
Overview of Capital SimCertify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Capital SimCertify Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Creating FMEA Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Unresolved Scenario Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Confirm Event Delete Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Edit Description Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
FMEA Scenario Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Insert Combination Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Insert Component Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Run Scenario Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Simulate FMEA Record Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Capital SimCertify gives you access to all the previous FMEA that has been carried out on the
relevant circuit. As you can see from the figure above, the cargo_bay_door circuit has several
reports already generate for it.
In order to generate an FMEA report the following steps should be followed:
1. Define and associate the analysis project.

2. Set the analysis scope.
3. Open Capital SimCertify from the main Analysis menu.
Note
If you have Robust Netlisting enabled, a message will be displayed to inform you that the
results displayed may differ from those expected. Refer to “Robust Netlisting” on
4. Create a new scenario (this step is only required if you have not created a scenario
already or do not wish to use an existing scenario.
5. Run the selected scenario.

February 2016
Capital SimCertify
Capital SimCertify Menus
6. View the resultant FMEA report (this step can be done at any time after the creation of
the report).
Note
If the analysis scope is a topology and wiring synthesis has been performed, then a
additional dialog will appear when starting the FMEA tool requesting the configuration to
analyze. Select one from the list.
The toolbar has the following buttons:
runs the selected scenario (see “FMEA Scenario Dialog Box” on page 85).
creates a new scenario (see “FMEA Scenario Dialog Box” on page 85).
edits the selected scenario (see “FMEA Scenario Dialog Box” on page 85) or FMEA
report (see “FMEA Editor (Capital SimCertify)” on page 69).
deletes the selected scenario (see “FMEA Scenario Dialog Box” on page 85) or
FMEA report (see “FMEA Editor (Capital SimCertify)” on page 69).
creates a new scenario (see “FMEA Scenario Dialog Box” on page 85) based on
those failures that could not be done in the selected FMEA report (see “FMEA Editor
(Capital SimCertify)” on page 69).
Related Topics
Scoping Creating FMEA Scenarios
Run Scenario Wizard Unresolved Scenario Builder
Capital SimCertify Menus Viewing the FMEA Report
Capital SimCertify Menus

The following menus are available
File Menu
New Scenario: Invokes the FMEA Scenario tool to allow a new scenario to be defined. This
option is also available as a tool button .
Run Scenario: Runs automated analysis on the highlighted scenario. This option is also
available as a tool button .
Exit: Exit Capital SimCertify.

February 2016
Capital SimCertify
Creating FMEA Scenarios
Edit Menu
Edit: Edits the selected object. In the case of an FMEA scenario it invokes the FMEA Scenario
tool with the scenario loaded, and in the case of an FMEA report it invokes the FMEA editor
with the report loaded. This option is also available as a tool button .
Delete: Delete the selected object. This option is also available as a tool button .
Edit Description: Invokes a dialog to allow the description of the selected object to be edited.
Unlock FMEA: Unlocks an FMEA that is locked for access.
Incremental FMEA: Compares two selected FMEA reports putting the differences in a third
FMEA report.
Resume FMEA: If an FMEA report generation operation fails or is cancelled, this menu entry
will attempt to restart the generation of the FMEA report. By selecting a failed/cancelled FMEA
report and click this menu entry, the failures that were not done will be applied.
View Menu
Netlist Errors: This window will view the errors produced in creating a netlist. If you are
denied the ability to create a Qualitative or Spice FMEA report, this option will explain why.
Functional Expressions: Displays the functional expressions used in the design
Related Topics
Overview of Capital SimCertify Creating FMEA Scenarios
Run Scenario Wizard

In order to generate an FMEA report when using the Capital Analysis system, an FMEA
scenario must first be defined.
There are three stages involved in defining an FMEA scenario:
• The initial state the circuit should be in.

• The events that the circuit will undergo (switch and sensor changes).
• The failures to be investigated.
Open the scenario tool from the FMEA tool by pressing to create a new one or to edit a
selected scenario.

February 2016
Capital SimCertify
Each of these are specified using the "FMEA Scenario Tool".
The FMEA Scenario Tool can be invoked in several ways once a scenario has been defined and
run. At present the headlamp circuit has not had any analysis carried out so the FMEA Scenario
tool has to be invoked by clicking the "New Scenario" button on the tool bar of the Capital
SimCertify window.
Defining Initial Circuit State

The first stage in defining an FMEA scenario is to decide on the initial state of each switch and
sensor in the circuit. If the engineer wishes to investigate the results of circuit failures in
different operating states, this can be achieved by defining different initial states in a number of
different scenarios, all of which can be easily tracked by the Capital SimCertify tool.
When the FMEA Scenario Tool window is first invoked, it displays all the switch and sensor
components set to their default positions. To change the initial state of a switch or sensor, click
on the text to highlight it. Not only will the text become highlighted but a gray box containing a
triangle will appear, indicating a pick list is available. Clicking on the triangle will display all
the available starting positions for that specific switch or sensor enabling the engineer to select
the desired starting position.
Defining Circuit State Changes

Capital Analysis performs FMEA by simulating a faulty circuit through a set of switch and
sensor changes, so the results can be compared with those of the working circuit. The engineer
has to define the set of changes that will exercise the circuit fully.
This is done by defining a series of events, with each event consisting of one or more changes.
The example scenario used here specifies the following events:
• Turn the dipped lights on

• Turn the dipped lights off & turn the main lights on
• Turn the main lights off & turn the dipped lights on
• Turn the dipped lights off
For an engineer to recreate this scenario they must first introduce a new event. This is achieved
by clicking the "Insert Event" button on the right hand side of the FMEA Scenario Tool
window.
Now a new event has been created, it is possible to specify when it occurs. It is possible to allow
the event to occur when the simulation has settled by checking upon Stabilization, or force the
event to occur at a specified time by entering a value in the After field.

February 2016
Capital SimCertify
Now components can be added to the event, click the "Insert Component" button to invoke the
Insert component dialog. This allows the engineer to choose a component.
Components are selected by clicking on the text to highlight them and then clicking "Insert" to
add them to the scenario. Components are added in their default state under the highlighted
event. It is possible to use the Shift and Ctrl keys to select a number of components to be
inserted at once.
To change the position of a switch, click on the triangle in the gray box and make a selection
from the pick list that appears.
There is no limit to the number of events that a scenario can contain. The only limit is the
number of switches that can be changed in each event.
The Insert Combination button can be used to insert a number of events automatically. If you
click "Insert Combination" the Insert component window will open allowing you to select the
components to be inserted by clicking on the ticks and crosses. Once you have selected the
components you want, click "Insert" and Capital Analysis will insert all the possible
combinations for the components inputs (switches).
Selecting Failures to Analyze

The engineer can decide which failures to try out on the circuit by clicking on the "Failure
modes" tab at the top of the FMEA Scenario Dialog Box. The window will change and be split
into two parts as shown below. The left hand side of the window shows the directory structure
containing all the components in the circuit, and the right hand side of the window shows the
possible failure modes for the highlighted component, plus a tick box to allow selection. By
default all failure modes for all components are selected.
When the Components level is highlighted, pressing the "Select All" of the "Deselect All"
buttons will select all the failures or deselect all the failures.
It is also possible to select or deselect all failure modes for all components within a particular
folder. This is achieved by highlighting the relevant folder on the left by clicking on it and then
clicking the "Select All" or "Deselect All" buttons located below the failure modes on the right.
Moreover, it is possible to select individual failures of individual components.
When the scenario is complete, clicking the "OK" button will add the scenario to the Capital
SimCertify window.
The description of the scenario can be edited by highlighting the scenario and then selecting
"Edit Description" from the Edit menu. A Edit description dialog will appear allowing the user
to edit the scenario's description.

February 2016
Capital SimCertify
Unresolved Scenario Builder
Related Topics
“Overview of Capital SimCertify” on page 79
“Run Scenario Wizard” on page 87
Unresolved Scenario Builder

When an FMEA report is generated, it is possible that some of the records could not be
simulated. Such records are referred to as unresolved.
It is possible that these unresolved records can be simulated successfully using an external
simulation engine through Capital SimBridge. That being the case, this tool can, from a selected
FMEA report, extract those failures that are unresolved and create a new scenario from them.
In the FMEA Tool, select an FMEA report and press the button. The Sub scenario
generator for scenario window will then open:
The first tab of this window will list all the failures that were unresolved. You can select these
failures in the same way you select failure modes of a scenario.
The second tab of this window allows other failures to be applied. You can select these failures
in the same way you select failure modes of a scenario. When the OK button is pressed you will
be asked for the name of the new scenario.
Enter the name and click the OK button.
Related Topics
Confirm Event Delete Dialog Box

To access: This dialog opens when an attempt is made to delete an event in the event sequence
for a Scenario.
Ensure that the event number shown in the title of the window is the number of the event that
you wish to delete. It this is the case, click OK to delete the event. Click CANCEL to keep the
event.
Fields
Table 6-1. Confirm Event Delete Dialog Box Contents
Field Description
OK Click to delete the event.

February 2016
Capital SimCertify
Edit Description Dialog Box
Table 6-1. Confirm Event Delete Dialog Box Contents

Field Description
Cancel Click to keep the event.
Related Topics
Edit Description Dialog Box

The Edit Description dialog is used to change the name of scenarios and FMEA reports in the
FMEA Editor (Capital SimCertify).
Used to edit the description of the object. Click OK to change the name. Click CANCEL to
keep the existing name.
Fields
Table 6-2. Edit Description Dialog Box Contents
Field Description
Edit Box Enter the new text for the object.
Related Topics
FMEA Scenario Dialog Box

To access: Run a scenario; Capital Analysis generates an FMEA report.
The Event Sequence Tab is used to test the operation of the circuit. The Failure Modes Tab
(Capital SimCertify) is used to select the failure modes to be applied to the circuit.
Fields
Table 6-3. FMEA Scenario Dialog Box Contents
Field Description
Event Sequence The event sequence tabs allow a sequence of switch changes
Tab to be applied in order to test the circuit.
Insert Event Use to add a number of events. Each such event should apply
one or more switch changes (changes to the input properties
of components). To achieve this, merely select the event you
wish to add a component change to and click the Insert
Component button.

February 2016
Capital SimCertify
Insert Combination Dialog Box
Table 6-3. FMEA Scenario Dialog Box Contents

Field Description
Insert Component This button allows you to choose the component to change
(see “Insert Component Dialog” on page 87).
Insert Use to insert a number of events based on a selection of
Combination components (see “Insert Combination Dialog Box” on
page 86).
Delete Component If a component is no longer required in an event, select the
component and click this button. If a whole event is no longer
required, select the event and click the Delete Event button
(see “Confirm Event Delete Dialog Box” on page 84).
Failure Modes Tab In the failure modes tabs, there are several ways of selecting
(Capital and deselecting failures.
SimCertify)
All Failures To select all failures, select the root node of the tree called
Components and click the SELECT ALL button. To deselect
all failures, select the root node of the tree called
Components and click the DESELECT ALL button.
All Failures in a To select all failures for a category, select the category node
Category of the tree and click the SELECT ALL button. To deselect all
failures for a category, select the category node of the tree
and click the DESELECT ALL button. The category of a
component is the category of the component model that
implements that component model.
Individual Failures To select (or deselect) an individual failure on a specific
component, select the component and check (or uncheck) the
failure mode check box.
Related Topics
Insert Combination Dialog Box

The Insert Combination dialog inserts the combination of input properties of the selected
components into an event in the Event Sequence Tab. The main window lists those
component & input properties that a combination can be constructed from.
Select all the components that you wish to create a combination from, click INSERT to insert
the combination into the event sequence. Click CANCEL to make no changes.

February 2016
Capital SimCertify
Insert Component Dialog
Fields
Table 6-4. Insert Combination Dialog Box Contents
Field Description
Insert Click to to insert the combination into the event sequence.
Cancel Click to make no changes.
Related Topics
Insert Component Dialog

The Insert Component dialog inserts a selected component into an event in the Event
Sequence Tab. The main window lists those component & input properties that can be
added to the currently selected event. If a component & input property has already been
added to the selected event, it will not be listed in this window.
When one or more components have been selected, click INSERT to insert the component &
input property into the event. Click CANCEL to make no changes.
Fields
Table 6-5. Insert Combination Dialog Box Contents
Field Description
Insert Click to insert the component & input property into the event.
Cancel Click to make no changes.
Related Topics
Run Scenario Wizard

Pressing the Run button in Capital SimCertify, opens the FMEA Wizard dialog.
The FMEA wizard leads you though the steps required to run an FMEA. Use the Next and Back
buttons to navigate your way through the wizard dialogs.
1. The first step summarizes the stages followed by the wizard. It also allows you to add
additional analysis steps by ticking the Enable Advanced Functionality (Capital
SimCertify) checkbox. These include selecting power nodes for failure application,
adding numeric simulation overrides and specifying component parameter

February 2016
Capital SimCertify
Run Scenario Wizard
modifications. If Enable advanced functionality is not selected, clicking Next brings

up the Create Audit Report screen.
2. This step offers the option to create an audit report which allows you to preserve the
configuration details and results of your FMEA run. Click the Create Audit Report
checkbox to enable the functionality. On selection the Name field is enabled, allowing
you to specify a report name, or accept the default entry offered. Click Next to move to
the next screen.
The generated Audit Reports are available for viewing in the Audit folder in the Object
Manager.
3. Select the simulation type; select from Qualitative, Numeric or an external simulator (if
you have configured an external simulator using Capital SimBridge, see “Capital
SimBridge” on page 155 for more information). Also, specify whether transient mode
will be used.
4. If transient was selected, you must supply the transient run information above, in the
additional pane. This consists of:
o Start Time - The point in time that the analysis should start, this defaults to zero.
o Stop Time - The point in time when the simulation should finish.
o Sample Rate - How often the state of the simulated system should be sampled and
recorded.
o Failure Time - The time into the scenario that the failure is applied.
o Variable Time Steps - This is a mode of operation of the numeric transient
simulator, where the simulation engine automatically determines the sample rate of
the results.
5. Next select the number of failure modes to be analyzed. Failure Modes can be dealt with
in three ways:
o Single failures - each of the selected failures will be applied to the circuit one at a
time.
o Double failures - each of the selected failures will be combined with each of the
other selected failures to create double failures.
o Multiple failures - each of the selected failures will be combined as long as the
combined failure likelihood does not exceed the given threshold.
6. Next specify whether to have the FMEA Editor (Capital SimCertify)opened when the
report is completed. Also for double and multiple FMEA generation (failure modes), the
results can be pruned to remove all those multiple failures whose effect on the circuit is
no different than applying a single failure mode.
This step also allows you to select if the FMEA scenario is to be run via either the
FMEA Wizard or when FMEA is set to run in the background (via FEM). Background

February 2016
Capital SimCertify
Simulate FMEA Record Dialog
FMEA runs are noted as “queued” in the Capital SimCertify until the FEM processing
has finished. During this time no actions are permitted on the design or parent scenario.
Once the FMEA run completes
7. Finally enter a description of the FMEA report you wish to create.
8. Click Run to initiate the action. This opens a progress dialog box.
9. Clicking Stop will stop the FMEA running but not delete what it has already processed.
The results that have been processed will be opened in the FMEA Editor. To continue a
FMEA that has been stopped, highlight it in Capital SimCertify window and select
Resume FMEA from the Edit menu.
Advanced Functionality (Capital SimCertify)
Checking the 'Enable advanced functionality' checkbox on the first page of the wizard adds a
number of pages to the wizard.
With this checked the following options are available:
• Power nodes for failure application, see “Power Node” on page 46 for more detail on
power nodes.
• Numeric simulation overrides, see “Overrides” on page 45 for more detail on numeric
simulation overrides.
• Component Parameters modification, see “Component Parameters” on page 44 for more
detail on component parameters.
Related Topics
Capital SimCertify Menus Object Manager

To access: highlight the record by clicking on it and then select the "Simulate Record" option
from the FMEA Editor View menu. This will invoke the Simulate FMEA Record window.
It is quite possible that engineers analyzing an FMEA report will find it useful to have a facility
where a specific record in the report can be simulated.
The window presents the information summarized in the record in a more detailed way.
The top section is the tool bar for the simulator:
• an event can be viewed by pressing the button

• Console messages can be displayed by pressing the button

February 2016
Capital SimCertify
The next section of the window displays the potential failure cause together with the RPN
information.
The text frame in the center of the window shows the individual steps of the scenario, together
with the expected functions and the actual functions that were achieved at each step.
To view an event
1. Select the row you wish to view.

2. Choose whether you want the expected (no failure applied) or actual (failure applied).
3. Choose whether you want the components colored and the labels shown.
4. Press icon.
5. The schematic will now be colored.
Note
The results of the simulation may vary according to whether the original simulation was
run with Robust Netlisting enabled. Refer to “Robust Netlisting” on page 41 for more
information.
The close button will stop the simulation of this record.
Related Topics

February 2016
Chapter 7
Capital SimProject
In order for Capital Analysis to be able to generate meaningful SCA and FMEA reports for an
electrical system, it needs to know what the functions of the system are, when they are active,
and the legal input conditions for an output condition. Capital SimProject and analysis projects
help us achieve this.This chapter details Capital SimCertify and the FMEA Scenario Tool,
which are used when running an FMEA using the Capital Analysis system.
Overview of Capital SimProject . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Output Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Control Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Creating a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Overview of Capital SimProject

Capital SimProject allows to define an analysis project or platform specification. The analysis
project describes in part or complete the electrical system being developed.
This is in terms of
• Features - Groupings of related functions, denoted by the icon.

• Output Functions - Key output conditions, denoted by the icon.
• Control Functions - Key input conditions, denoted by the icon.
An example of a 'Feature' in an automotive context might be a 'window system', it's output
conditions might be 'window opening' and 'window closing'. For these output conditions or
functions, there are usually input conditions such as 'window switch up', 'window switch down',
these are control functions.
There are three key steps to setting up the analysis project:
1. Creating the analysis project - Using Capital SimProject to build the analysis project
structure (see “Creating a Project” on page 98).
2. Assigning the analysis project to a Capital project - Assigning the analysis project to the
Capital ECAD environment (see “Assigning a Project” on page 245).

February 2016
Capital SimProject
Features
3. Attaching functions - Define the relationship between project functions and the devices
in the ECAD environment (see “Attaching Component Models” on page 199).
Related Topics
Creating a Project Assigning a Project
Attaching Component Models Features
Output Functions Control Functions
Features
A feature in an automotive context may be a window system. In the platform builder it appears
under the 'Product' root folder.
A product can have one or more features, and a feature can be made up of a number of sub-
features.
Each feature has some optional information.

• Description - A textual description of the feature for information purposes
• URI (Uniform Resource Location) - A text field that points a document on a file system
or URL perhaps, again used for information purposes.
Related Topics
Attaching Component Models Control Functions
Output Functions
Output Functions
An output function a high level condition of a system or sub-system. It used for reporting on the
state of a system during analysis. It makes testing and generation of functional analysis possible
by simulation. It is the output functions that are reported in the Simulator, FMEA reports, SCA
reports and script reports.

February 2016
Capital SimProject
Output Functions
The output function text or label will be reported by the analysis tool indicating it's state. For
each output function there are further fields that are used for FMEA reporting.
For each output function, severity and detection values need to be assigned. There will be 2
severity values and 2 detection values for each output function. These are for when the output
function fails to happen (failure), and for when the output function is achieved when it should
not have been (spontaneous). A short explanation of the effects for each case is also required.
This information should be entered in the bottom section of the SimProject window. To assist
the entry of the severity and detection values a pick list is provided for each entry required.
These are accessed by clicking on the small triangles next to the default values. There is also a
text frame provided for the explanation of the effects. Remember this information must be
entered for each output function and in each case will only apply to the output function that is
highlighted.
Child Output Functions

Child output functions are output functions that are created as sub folders of other (parent)
output functions to which they have some degree of influence over. They are created in exactly
the same way except that the user highlights a output function other than a feature.
When the create output function button is clicked a new output function is created as a sub
folder of the highlighted function, but this time the highlighted output function (the parent
output function) has a gray box next to it highlighting the word "And". This is the default
logical operator. Clicking on the gray box will display a pick list of all the available operators.
The parent function's icon will also change to , denoting that it has child objects.
The figure below shows a output functions of a headlamp circuit with the pick list of available
operators displayed.
In the figure above, the main_beam output function has two child output functions.
Left_main_beam and right_main_beam with the "And" logical operator selected. This means
that if the main_beam function is to be achieved, the left_main_beam function and the
right_main_beam function both have to be achieved.

February 2016
Capital SimProject
Output Functions
Child Output Function Operators

When defining child output functions there are several different operators available, they are as
follows:
• And (logical AND) All child output functions must be achieved for the parent function
to be achieved.
• Or (logical OR) The parent output function is determined as being achieved regardless
of the number of child output functions achieved, as long as there is at least one.
• Xor (Exclusive Or) Any single child output function must be achieved for the parent
output function to be achieved, but not more than one.
• Equivalent (Temporal Or) if any of this functions children are achieved at any time
during a simulation, then this parent output function is achieved.
• Strict Sequence For the parent output function to be achieved, the child output
functions must be achieved in the order defined.
• Loose Sequence The parent output function is determined as being achieved as long as
all child output functions are achieved, regardless of order.
It should be noted that the Equivalent operator can only be present at the top level (it cannot be
a child of another function label). This restriction may be lifted in a future version of Capital
Analysis. An example use for this operator is a wash_wipe function that has two children
fast_wipe and slow_wipe. By using the Equivalent operator, as long as a fast_wipe or a
slow_wipe appears at any time in the Event Sequence Tab, the wash_wipe function will be
achieved.
Copy, Cut and Paste

It is possible to use the cut, copy and paste commands in the SimProject's Edit menu to create
output functions. This can be a big advantage as it will save you time and effort when creating
lots of similar output functions. You can use the Copy, Cut and Paste commands in the usual
way.
If you copy an output function and then paste it as a child output function the following dialog
will open asking you if you want to create a Copy or a Clone of the output function. A copied
output function will be a new individual output function with the same data in it as in the
original and it will be given a new label. A cloned output function will not be a new output
function but an imitating copy of the original with the same label as the original.

February 2016
Capital SimProject
Control Functions
Related Topics
Attaching Component Models Control Functions
Features Capital SimProject
Control Functions
As mentioned, a control function is usually associated with a switch condition in a particular
state or position, 'window switch up', for example. Control functions are required so that SCA
can be performed. When running SCA, Capital Analysis will be looking at output conditions
(output functions) of the system and checking against inputs conditions (control functions). If
an illegal set of input conditions results in an output then this will be reported in the SCA report.

February 2016
Capital SimProject
Control Functions
So this means we need to represent the input conditions (control functions) and the relationships
with the outputs (output functions).
This is done by selecting output functions in SimProject, and selecting Edit > Create Control
to add a control function. A controlled by folder is automatically inserted, containing control
functions. The output functions icon will also change to denoting that it has some contents.
A given output condition may require several input conditions to be present at once, so further
control functions can be added.

February 2016
Capital SimProject
Control Functions
The 'Controlled by folder' allows the logical relationship to be set between an output function
and it's valid input conditions. In the image above, we can see the 'And' operator. By double
clicking on the 'Controlled by' folder you can set this operator from the drop-down that appears.
The options available are:
• AND - All inputs must be present when the output is achieved.

• OR - One or more of the inputs must be present when the output is achieved.
• XOR - Only one of the inputs must be present when the output is achieved.
It is possible to make the control functions hierarchical. Child control functions can make up the
parent control function. This is done by selecting the parent control function, and selecting Edit
> Create Control. The parents icon will change to . As it is likely that more that one child is
to be added, then the logical association between the parent and children can be set. This is done
by double-clicking on the parent and selecting the logical operator from the drop-down list. The
logical operators are as described above.
There are also cases where you would like to say, not this input state. To achieve this logical
condition, control functions can be added to an 'Excluding' group, this is done by selecting the
'Controlled by' folder and selecting Edit > Create Not Group.
Control functions can now be added to the 'Excluding' group. Do this by selecting the
'Excluding' folder and then adding control functions in the usual way. If more that one control
function has been added to the Exclude group then the same logical relationship between the
control functions in the group can be set by double clicking on the 'Excluding' group and
selecting the logical operator. The available operators are as described above.
Related Topics
Attaching Component Models Output Functions

February 2016
Capital SimProject
Creating a Project
Creating a Project
In order to create or edit an analysis project, start Capital SimProject. The project is built using
this tool. Do this by pressing Space Bar and entering SimProject.
Once SimProject is open, you can configure the following:
Adding Project Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Adding Output Functions to Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Adding Control Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Adding Excluded Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Saving the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Adding Project Features

Project features are added either to the project root, or as children to a parent feature. Follow the
steps below to below to add a feature.
Procedure
1. Select the root folder in SimProject.
2. Select Edit > Create Feature from SimProject's menubar.
3. Edit the feature name by double-clicking on it.
4. Fill in the 'Feature description' field (optional step)
5. Fill in 'URI' field (optional step).
To create child feature, select an existing feature, instead of the root folder at step 1.
Adding Output Functions to Features

Output functions are added to features, or added to parent output functions. Follow the steps
below to do this.
Procedure
1. Select the feature that you would like to add output functions to.
2. Select Edit > Create Function, to add an output function.
3. Edit the function name by double-clicking on it.
4. Set the 'Failure' 'Sev.', 'Det' and 'Potential Failure Effect' fields.
5. Repeat the above step for 'Spontaneous' and the respective fields.

February 2016
Capital SimProject
Creating a Project
You can also create child functions, do this by selecting an output function in step 1 instead of a
feature.
If you are adding further child functions to a single parent, the relationship between the parent
being achieved as a result of child functions occurring should be defined. To do this, double
click on the parent output function, and select an operator from the drop down list on the right-
hand-side.
Adding Control Functions

Control functions are associated with output functions. Follow the steps below to add control
functions.
Procedure
1. Select an output function.
2. Select Edit > Create Control to add a control function.
3. Edit the function name by double-clicking on it.
If you add further control functions to an output function, then you must define the a
relationship between the control functions and the output function. To do this double click on
the 'Controlled by' level that has been added as a result of adding control functions, select from
the logical operators available.
You can also add child control functions, to do this select a control function, instead of a output
function at step 1 above.

February 2016
Capital SimProject
Creating a Project
Adding Excluded Functions

Excluding functions are groups of controls functions that effectively have a logical NOT
operator applied to them. This negation is represented by an Exclude folder added to the
'Controlled by' folder of the output function. To add an 'Excluding' group of functions follow
the steps below.
Procedure
1. Select the output function, or Controlled by group to add the 'Exclude' group to.
2. Select Edit > Create Not Group.
3. Select the 'Excluding' folder.
Add control functions as described above, except step 1 is ignored
If several control functions are added to the 'Excluding' group, the logical relationship between
them can be set by double clicking on the 'Excluding folder', and selecting the operator from the
drop-down.
Saving the Project

The analysis project is saved to the analysis database. In order to do this:
Procedure
1. Select File > Save from the menubar in Capital SimProject.
2. Enter the location and name for the analysis project.
3. Click 'Save'.

February 2016
Capital SimProject
Menus
Related Topics
Control Functions Output Functions
Menus
The SimProject window has 4 menus available to the user: File, Edit, Tools and Help.
File Menu
• New: Create a new analysis project. This option is also available as a tool button .
• Open: Open an existing analysis project. This option is also available as a tool button
. This will invoke a chooser dialog (see “Open/Save Object Dialog” on page 265).
• Save: Save the analysis project under the same name. If it is a new analysis project and
has not been saved before, selecting this option will cause the “Save As” option to be
invoked. This option is also available as a tool button .
• Save As...: Save the analysis project under a different name. This will invoke a chooser
dialog (see “Open/Save Object Dialog” on page 265).
• Merge: This option allows you to merge the functions of another selected analysis
project into the current analysis project.
• Print: Prints all the project information.
• Print Preview: Opens a window that displays the page format and allows you to change
the printer settings.
• Import...: This option allows analysis project to be imported from the file system. See
“System Import/Export” on page 327.
• Export...: This option allows the analysis project to be exported to the file system. See
“System Import/Export” on page 327.
• Exit: Exit the SimProject tool.
Edit Menu
• Edit Function Name: Allows the user to edit the name of the highlighted function.
• Create Function: Creates a new output function . This option is also available as a tool
button .
• Create Control: Creates a new control function. This option is also available as a tool
button .

February 2016
Capital SimProject
Menus
• Create Feature: Creates a new feature. This option is also available as a tool button
.
• Create Not Group: Creates an excluding group for control functions. This option is
also available as a tool button .
• Move Up: Moves the selected function up in the list. This option is also available as a
tool button .
• Move Down: Moves the selected function down in the list. This option is also available
as a tool button .
• Cut: Removes the selected object and places it on the clipboard. This option is also
available on a tool button .
• Copy: Copy the selected object to the clipboard. This option is also available on a tool
button .
• Paste: Paste the contents of the clip board. This option is also available on a tool button
.
• Delete: Delete the selected function. This option is also available on a tool button .
• Options: Gives the user access to the Capital Analysis user definable options. See “Edit
Options Dialog” on page 269 for more details.
Tools Menu
• Check Integrity: Checks the object for correctness in terms of syntax, required fields
and reports this.
Related Topics
“Capital SimProject” on page 91
“Creating a Project” on page 98

February 2016
Chapter 8
Capital SimScript
This facility is an optional module for Capital Analysis. Its user interface appears in the
Overview of Simulator Tool and allows scripts to be constructed and run that test the operation
of the circuit. These scripts can be saved and run on different versions of the circuit. These
scripts can change switch settings and set failure modes to components. Test points can be
monitored and timing information can be included in the script. The results of running a script
are written to a file in xml format.
Overview of Capital SimScript . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Capital SimScript Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Creating a Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Script File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Using a Script File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Override File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Overview of Capital SimScript

This tool allows scripts to the constructed that test the behaviour of an electrical design.
This tool appears as a fourth tab on the Overview of Simulator Tool. If it is not present, and you
require this facility, please contact us. There are three areas in the pane:
• Input Script - This is the file that contains the script which you wish to execute, for
details on the format and language constructs available, see “Script File Format” on
page 108.
• Output Results - As well as the generation of interactively explore-able scripts (see
“Capital SimScript Reports” on page 104), the scripting tool generates an XML file
which can be parsed by an external application to translate the results into those required
by your process. The file format is defined in an XML dtd.
• Run Area - This area allows you to specify the simulation parameters for the script.
You can set three key parameters. The first is the Start time, this is the point in time at
which script results should start to be recorded. The second parameter specifies an
absolute Stop time for the script. This is only used if the script has not already reached
its final state by this time. Finally, the Sample time parameter controls how frequently
the simulation state is recorded to the XML file (in simulation time).

February 2016
Capital SimScript
Performing a Script Analysis
Note
The Variable Time Steps option, available when running a numeric simulation, allows
the Simulator to “decide” when samples should be taken. This will result in the Sample
time parameter being ignored; instead, the system will detect changes in the result set and
increase the sample rate to capture the information needed.
Related Topics
Creating a Script Using a Script File
Script File Format Overview of Simulator Tool
Capital SimScript Reports Performing a Script Analysis
Performing a Script Analysis

There are three main steps to performing a script analysis:
Procedure
1. Create script file. See “Creating a Script” on page 107.
2. Set up and run the analysis. “Using a Script File” on page 118.
3. Explore and examine the results. “Capital SimScript Reports” on page 104.
Note
Simulate and Reset buttons do not apply to the Scripted test pane of the Simulator.
Related Topics
Creating a Script Using a Script File
Capital SimScript Reports

After a script has been completed, you can view the generated report in the report viewer.
The report viewer’s window is composed of two areas. On the left-hand side, the components of
the report are shown in a tree. Every script report will include the following sections:
• Header – A high-level summary of the report contents.

February 2016
Capital SimScript
• Ecad Devices & Properties – A complete list of all components in the simulation, and
the properties that were passed to the simulation model from the ECAD tool at the start
of the simulation.
• Result Set – One or more result sets (depending on how many analyses were executed
within the script). Result sets are broken down into Functions, Component Variables
and Component Properties. See “Filter the Results” on page 105 for information on
working with the report output.
• Console output – The console output generated while running the script.
• Error – Any error messages generated by the Capital SimScript during simulation.
The right-hand pane displays the results for the user selection.
The following topics offer contain full details:
Filter the Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

ECAD Device & Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Functions Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Simulation Properties & Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Error and Console Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Filter the Results

When viewing a result set, a number of options are available to refine the data displayed.
• Enter a regular expression into the search field (indicated by the magnifying glass icon)
to search on the contents of the Name column. The following wildcards are supported:
o * - matches 0 or more of any characters
o ? - matches exactly 1 character
o [...] - matches a single character from the list in the brackets
o [^...] - matches a single character except those from the list in the brackets
o (...|...) - matches the first or second character group in the parentheses
o {N} - matches exactly N of the preceding character or group
o {M,N} matches M to N of the preceding character or group
o ^... matches the start of the cell value
o ...? - matches the end of the cell value

February 2016
Capital SimScript
Note
If no wildcards are used, the search string is case-insensitive and will match any string
that contains the expression. If any wildcards are used, the search string is case-sensitive,
and will match any string that starts with the expression.
• Columns can be repositioned within the report. To move a column, click on the column
name and drag it to the new position.
• When viewing Component Variables or Component Properties, click the button
to toggle the display of components within the data.
• When viewing Component Variables or Component Properties, toggle the display of
internal and external nodes by clicking the 3-way button; the following modes are
available:
o - all nodes are displayed
o - no nodes are displayed
o - only external nodes are displayed
• When viewing Component Variables, click the button to toggle the display of arcs
within the data.
• The report data can be sorted on a single column.
o Click a column header once to sort on that column in ascending order (indicated by
an up-arrow icon).
o Click the column header again to sort in descending order (indicated by a down-
arrow).
o Click a third time to remove the sorting.
Sorting is applied according to the type of data displayed in the column:
o Integer and Real data types are sorted numerically.
o String data is sorted using a true alphanumeric sort, so any number groups within a
string are considered a single integer. For example, in an ascending sort, 1.3 is
placed before 1.22.
ECAD Device & Properties

This section contains an exhaustive list of all of the components captured in the netlist used for
the script. In addition, the name and value of each property passed from the ECAD tool to the
simulation model is reported.

February 2016
Capital SimScript
Creating a Script
Functions Area
The functions achieved by the system being simulated are recorded at each sample step during
script execution. All functions are shown in the table on the right hand side, with its achieved
state (true if the function was being achieved, false if it was not) reported at each sample step.
Simulation Properties & Variables

In addition to the design functionality achieved, Capital SimScript also records all properties
and variable of each simulation model at each step, as defined by the monitor command in the
script. A sample is taken at each defined sample step, and displayed in the table on the right.
Component Variables are defined as being the internal variables within the component model,
and Component Properties as the properties defined in the interface section of the component
model.
As the variables section can become extremely large, it is recommended that any value that is
intended to be checked by a human reader is assigned to a property rather than an internal
variable.
Error and Console Area

Some simulation models output information during simulation using the SAINT print
command. This output is captured during the execution of a script, and stored in the Console
output section of the report. Clicking on this icon in the tree will show all of the captured
console output during the complete execution of the script.
Finally, the Errors section contains a list of any errors or warnings generated during script
execution. As shown in the screen shot, errors and warnings may not stop the script from
completing. However, this section should be checked for any errors that may invalidate the
results of the script analysis.
Creating a Script
After selecting the 'Create new script' button, from the Simulator, the script editor will be
displayed.
There are several operations available on the toolbar:
• The button will create a new script.

• The button will open an existing script in for filestore.
• The button will save the script being edited.
• The button will cut the selected text into the clipboard.
• The button will copy the selected text into the clipboard.

February 2016
Capital SimScript
Script File Format
• The button will paste the text in the clipboard into the editor.
• The button will check the script you have entered for syntax errors.
Script files usually have the following sections:
• Scenarios - this section defines the initial states of the switches in the schematic.
• Monitoring - this section indicates which components of the schematic you wish to
monitor the changes of.
• Multiple runs of defined scenarios.
For a worked example for the radio_sneak example schematic, see“Script File Format” on
page 108.
Note
When the script is complete, use the button to check it.
Related Topics
Capital SimScript Using a Script File
Script File Format

Consider an example of a script file. This can be used directly on the supplied Analysis
Examples Project on the radio_sneak design.
// This is a Script for 'radio_sneak_capital'
scenario "radio_sneak_capital"
do
at 10ms
do
design.setProperty("DRV_DOOR_SWTCH", "position", "open");
design.setProperty("IGN_SWTCH", "position", "open");
design.setProperty("INT_LAMP_OVRDE", "position", "open");
design.setProperty("PAS_DOOR_SWTCH", "position", "open");
design.setProperty("RADIO", "radio_function", "on");
done;
at 20ms
do
design.setProperty("RADIO", "radio_function", "off");
done;
at 30ms
do
design.setProperty("PAS_DOOR_SWTCH", "position", "closed");

February 2016
Capital SimScript
Script File Format

design.setFailure("BATTERY", "flat");
done;
at 40ms
do
done;
at 50ms
do
design.setProperty("INT_LAMP_OVRDE", "position", "closed");
done;
at 60ms
do
design.unsetFailure("BATTERY");
done;
at 70ms
do
done;
at 80ms
do
done;
at 90ms
do
design.setProperty("IGN_SWTCH", "position", "closed");
design.setFailure("DRV_DOOR_SWTCH", "Switch stuck open");
done;
at 100ms
do
done;
at 110ms
do
done;
at 120ms
do
design.unsetFailure("DRV_DOOR_SWTCH");
done;

February 2016
Capital SimScript
Script File Format
at 130ms
do
done;
at 140ms
do
done;
at 150ms
do
design.setFailure("DRV_DOOR_SWTCH", "Switch stuck closed");
done;
at 160ms
do
done;
at 170ms
do
design.setProperty("DRV_DOOR_SWTCH", "position", "closed");
done;
at 180ms
do
done;
at 190ms
do
done;
at 200ms
do
done;
at 210ms
do
design.setFailure("DRV_INT_LAMP", "open circuit");

February 2016
Capital SimScript
Script File Format
done;
at 220ms
do
done;
at 230ms
do
done;
at 240ms
do
design.unsetFailure("DRV_INT_LAMP");
done;
at 250ms
do
done;
at 260ms
do
done;
at 270ms
do
design.setFailure("IGN_RELAY", "Coil burnt out");
done;
at 280ms
do
done;
at 290ms
do
done;
at 300ms
do
design.unsetFailure("IGN_RELAY");
done;
at 310ms
do

February 2016
Capital SimScript
Script File Format

done;
at 320ms
do
done;
done;
design.monitor("connections","WIRE.*");
design.monitor("fuses","DASH_FUSE");
design.monitor("fuses","SUPPLY_FUSE");
design.analyze("radio_sneak_capital");
Any characters '//' are ignored by the Script object when it reads the file, and are treated as
comments. In this case, maybe the user wishes to log results to a different file (set manually
before running the script) so the first line is commented out. No provision for is made for
commenting out part of a line, only whole lines can be comments. Blank lines are also ignored,
so can be used to separate steps in the script, as here.
There are three main groups of scripting commands:
• Scenario Definitions - These define sequences of actions to be performed on the design.

In the example, a single scenario is defined named "radio_sneak_capital". This can be
re-used any number of times during the scripts execution. The command relevant to this
group are described in detail below.
• Monitoring Specifications - During the execution of a script there are many things that
you may wish to record. This group of commands allows you to specify which
properties of which components you can monitor.
• Simulation Inception - Use the command design.analyze("scenario name")
which will run through a previously defined scenario. This behavior can be exploited to
significantly improve script execution performance where large scenarios or complex designs
are in use.
Scripts use a sub-set of the SAINT modeling language, for further information on the syntax
and object available for use in a script, please consult the SAINT: Behavior Modeling Language
guide.
Scenario Commands
• scenario
This command is used to identify a sequence of actions as being part of a scenario. The
basic structure is:
scenario "name" do ... done;

February 2016
Capital SimScript
Script File Format
The "name" portion should be replaced by a string that meaningfully captures the
purpose of the scenario. All event commands between the do and done form the
sequence of actions that make up the scenario.
• at
This command is used to specify a set of actions to occur at a specific point in time
during the execution of a scenario. The basic structure is:
at time unit do ... done;
The at command specifies an set of actions (design.setProperty, design.setFailure,

design.unsetFailure, design.reset) to occur at a particular time. Like the scenario
command, all actions to occur at the specified time are enclosed in do...done; the
allowable units are:
o us
o ns
o ms
o sec
o Seconds (legacy use)
o min
o Minutes (legacy use)
o hr
o Hours (legacy use)
• after
This specifies that actions in the do block that should be performed after a given period
from any previous action group, the basic form is:
after <time>
do
...
done;
• if ... then ... elseif ... then ... else ... endif;
'if then else' program control constructs, form:
if <conditional>
then
....
elseif <conditional>
then
...
else
....

February 2016
Capital SimScript
Script File Format
endif;
• for ... do ... done

For loop programming construct:
for <counter> %= <start> to <finish> step <step rate>
do
...
done;
• while ... do ... done

While loop construct, form:
while <condition is true>
do
...
done;
• function ... do ... done

Functions can be defined to analyze a design. They can be passed parameters and return
values. Form:
function <return type> <function name> (<type> <parameter name>,...)
do
...
done;
• break
'break' is used to break out of a loop
break;
• continue
continue is used to stop in a for loop and return back to the top of the for loop.
continue;
• return
'return' is used to exit out of a function, and return a value specified by the function type.
Its form is:
return;
• print
Print is used to print messages to the console Its form is:
print "...";
• renames

February 2016
Capital SimScript
Script File Format
renames is used to rename variables:

...renames...;
• design.analyze
By calling design.analyze(); a scenario will be executed on the local machine. The
format of the command is:
design.analyze("scenario_name");
The analyze() method has now been extended to do an exploration of selected switch
positions & all the failures being considered. The switch positions that will be explored
are selected inversely by the user (the user indicates those switches that will be held at
given values - see the hold() method). The form in this case is:
design.analyze();
• design.setProperty
This command allows you to (within an at do...done block) to change the value of an
input property on a component, the format of the command is:his command allows you
to (within an at do...done block) to change the value of an input property on a
component, the format of the command is:
design.setProperty("component_name", "property", "value");
It should be noted that errors will be generated if the components, properties, or values
do not exist.
• design.setFailure
setFailure changes the current failure mode of the component. The format of the
command is:
design.setFailure("component_name", "failure mode ");
Setting a failure will override any current failure that is set on that component.
• design.unsetFailure
unsetFailure unsets the current failure mode of the component, restoring it to its default
behavior. The format of the command is:
• design.open
This will open a new design to analyze.
Note that this will also clear all the considered failures.
design.open("databasepath/subsystem", "simulation mode");
• design.setOutput

February 2016
Capital SimScript
Script File Format
The setOutput method will override the output filename to write to.
Note that this will also clear all the monitored properties.
design.setOutput("output file name");
• design.isOutputAlreadyPresent
This method can be used to test if an output file exists and act accordingly. It's use is in a
conditional statement and will return true of false. Its form is:
design.isOutputAlreadyPresent()
• design.setStartTime
This method can be used to override the transient setting for start time:
design.setStartTime("time");
• design.setSampleTime
This method can be used to override the transient setting for sample time:
design.setSampleTime("time");
• design.setStopTime
This method can be used to override the transient setting for stop time:
design.setStopTime("time");
• design.consider
This method is used in conjunction with the analyze() method. It creates a list of failures
to be considered during the analysis.
design.consider("<category>", "<component>", "<failure>");
design.consider("<category>", "<component>");
design.consider("<category>");
where any of the above parameters can include regular expressions.

• design.reset
design.reset takes no parameters, and resets the designs failure modes and state but does
not effect the properties. The format of the command is:
design.reset();
• design.resetAll
design.resetAllesign.resetAll takes no parameters, and resets the designs failure modes,
state and resets all component properties to default settings. The format of the command
is:
design.resetAll();

February 2016
Capital SimScript
Script File Format
• design.monitor
This command allows you to specify one or more components whose properties you
wish to record into the results output file.
design.monitor("category", "component", "property");
design.monitor("category", "component");
design.monitor("category");
where any of the above parameters can include regular expressions. The monitoring will
not be applied until the next invocation of design.analyze().
• design.getComponent
This command allows you to access a component within a design.
component aFuse := design.getComponent("FUSE1");
if (aFuse.isValid())
then
print "Found a fuse";
endif;
For further information on methods available in SAINT for component objects please
see the SAINT: Behavior Modeling Language guide.
• design.getComponents
This command allows you to get an array of all components in a design:
component allComponents[] := design.getComponents();
• design.getNumberOfComponents
This command allow you to get a count of all components in a design:his command
allow you to get a count of all components in a design:
int compCount := design.getNumberOfComponents();
• design.override
This command allows you to link to an external override file as the script is run,
overwriting default component properties values:his command allows you to link to an
external override file as the script is run, overwriting default component properties
values:
design.override ("<path\filename>.xml");
For further information on the use of override files, see “Override File” on page 119.

February 2016
Capital SimScript
Using a Script File
Related Topics
Capital SimScript Using a Script File
Creating a Script Overview of Simulator Tool
Capital SimScript Reports Override File
Using a Script File

To use a script, follow this steps:
Procedure
1. In the Input Script area, you can either specify the script you have created using the
button, or create a new script using the button and follow the instructions under
“Creating a Script” on page 107.
2. In the Output Results area, specify a location for the results to be stored to.
3. In the Run area, set the start time (in simulation time) for the start of results recording.
Please note that this is not the time that simulation will begin, but the first instant that
results will be recorded.
4. In the 'Run' panel set the resolution. This specifies how frequently (in simulation time)
the results are recorded to file.
5. In the 'Run' panel, set the stop time. This specifies the point at which results recording
should stop (in simulation time). Note that the simulation itself may continue beyond
this point, but no further results will be captured in the output XML file.
6. Set the simulation technology to be used (Qualitative or Numeric), and transient if
required.
7. In the 'Run' panel, check the 'Variable step' check box if variable time steps are required
for transient simulation.
8. In the 'Run' panel click on the Run button to execute the selected script with the
specified parameters.
After the script has been run the schematic will be colored, and a several steps will be
shown in the bottom half of the Overview of Simulator Tool, each of these steps will
correspond to a design.analyze() call in the script.

February 2016
Capital SimScript
Override File
Tip: You can run the analysis action as a background operation by checking the Run in
background option on the dialog box, see the Creating Audit Reports when Capital
Analysis Operations are in the Background topic in the Capital Design Tools -
Common Functions User Guide for further information. Running the analysis operation
in the background allows you to continue working on other analysis tasks knowing you
can open and interrogate the audit report at a convenient time.
Note
The script derived from loading a file will start from the current settings of the Overview
of Simulator Tool, so it is worthwhile ensuring that the initial state of the system is fully
defined. If no failures have been set or cancelled before the first RUN and the user was to
set a failure before running the file, the initial design.analyze() will include that
failure. Settings can also be changed in the Overview of Simulator Tool between running
parts of the file, including the running of additional steps. Note that any changes set in
this way will affect the state of the subsystem when running from the script, so if the user
cancels the failure after running the second step in the file above, it'll stay cancelled
unless it is reset before returning to the script.
Related Topics
Capital SimScript “Script File Format” on page 108
Capital SimScript Reports Override File
Override File
Capital SimScript allows you to import an XML file containing a number of component
property definitions, overriding property values assigned to components in the simCore
database as the script is run. The override is performed within the script, using the following
syntax:
design.override(“<path\filename>.xml”);
Note
A restricted number of characters are not supported by SAINT, hence the use of non-
alphanumeric characters should be avoided where possible. If a filename cannot be found
and contains invalid xml characters, when reported, the invalid characters will be
transformed to ? to prevent the xml parser reporting an error.
Note also that if you need to use ^ anywhere in a SAINT expression, including a
filename, it should be preceded by another ^. So, for example, "my^File.xml" must
become "my^^File.xml" when referenced in SAINT.

February 2016
Capital SimScript
Override File
The file, which must be correctly formatted, as detailed below, contains details of component
property overrides and will, in effect, behave like a set of setProperty(<component>,
<property>, <value>) commands.
For example:
<overrideList>
<overrideComponent name="lamp_1">
<override property="lit" value="TRUE"/>
</overrideComponent>
</overrideList>
In this example, a component model for a lamp "lamp_1" has a property of "lit" - a Boolean
value - and this is set to TRUE by the override property command.
Error Handling
While running a script:
• if the specified file cannot be found, the Simulator shall continue running the script, and
no overrides shall be performed. A warning will be logged in the error section of the
results dialog.
• if the file exists but it isn't a valid overrides file, the Simulator will continue running the
script and no overrides shall be performed. A warning will be logged in the error section
of the results dialog.
• if the file exists and is valid but some of the components and properties aren't valid, the
Simulator will continue running the script and any valid overrides shall be done. A
warning will be logged in the error section of the results dialog; this will detail the
missing/incorrect component, property and value for file debugging purposes.
If, in the overrides file, more than one value is given for the same component and property, the
second value will be used. A warning, detailing the component, property, both values, and
which one will be used, will be logged in the errors section of the results dialog.
Overrides File format

The following samples show possible, valid formats for the overrides file:
Sample1
<overrideList>
<overrideComponent name="myComponent1">
<override property="firstProperty" value="1234.5"/>
<override property="secondProperty" value="ABCdef"/>

February 2016
Capital SimScript
Override File
<override property="thirdProperty" value="TRUE"/>
<override property="fourthProperty" value="FALSE"/>
</overrideList>
The override script above features four override property commands, each one overriding the
value of a different property (for example, the property "firstProperty" has its value set to
"1234.5"). The component "myComponent1" is referenced each time one of its properties is
overridden.
Sample2
<overrideList>
<override property="firstProperty" value="6789"/>
<override property="secondProperty" value="GHIjkl"/>
<override property="thirdProperty" value="FALSE"/>
<override property="secondProperty" value="TRUE"/>
</overrideList>
The override script above first references a component "myComponent1" before invoking three
override property commands, overriding the three properties belonging to it. Next, a second
component is referenced ("myComponent2"), which also has three properties overridden.
Finally, a third component ("myComponent3") is referenced and its two properties are
overridden.
Sample3
<overrideList>
<override property="firstProperty" value="5432"/>
<override property="secondProperty" value="GHIjkl"/>
<override property="fourthProperty" value="FALSE"/>
<override property="fifthProperty" value="6789"/>

February 2016
Capital SimScript
Override File
</overrideList>
The above script is similar to Sample 2, above, but demonstrates that you can have properties
for a single component defined in separate <overrideComponent> tags. The component
"myComponent1" has three property values overridden, then the component "myComponent2"
has three property values overridden. Finally, the script references the component
"myComponent1" a second time, then overrides two further properties.
Note
All these XML files are valid, however the second one, having least repetition, is
preferred.
Related Topics
Capital SimScript Script File Format
Capital SimScript Reports Using a Script File

February 2016
Chapter 9
Capital SimProve
The Capital Analysis sneak circuit analysis tool builds on the work done by the engineer in
producing an FMEA Report. Based on the 'Analysis Project', assigned to the Capital project, the
tool looks for unexpected output conditions (output functions) as a result of a set of input
conditions (control functions).
Overview of Capital SimProve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Creating an SCA Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Exporting an SCA Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Prune an SCA Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
SCA Report View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
SCA Tool Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Overview of Capital SimProve

Capital SimProve then compares this model with the observed behaviour of the circuit. This
could result in a number of concerns being detected. In situations where a function has been
achieved, when the model indicates that it should not have been, this is highlighted as a possible
sneak. In situations where a function has not been achieved, but the model indicates that it
should have been achieved, this is highlighted as a possible failure of the circuit to meet its
specification.
After a report has been generated, the engineer can view the state of the circuit for each concern
of interest.
Related Topics
Creating an SCA Report SCA Report View
Exporting an SCA Report SCA Tool Menus
Scoping Performing an SCA Operation
Performing an SCA Operation

Based on the analysis project that has been defined to the Capital project, it is possible to run
SCA. The steps below identify the main steps to preform SCA.

February 2016
Capital SimProve
Procedure
1. Create the analysis project / platform specification.
2. Associate the analysis project with the Capital project and devices.
3. Set the Analysis Scope.
4. Open Capital SimProve from the main menu. The following window will open. It will
be blank if no SCA report has been generated before.
See “Creating an SCA Report” on page 126 for instructions on creating an SCA report.
Note
additional dialog will appear when starting Capital SimProve requesting the
configuration to analyze. Select one from the list.
When a SCA operation is run, the function and sneak expressions are evaluated for all the input
combinations and a number of concerns are identified.
• Sneaked functions are those functions that have been achieved according to the function
expression, but should not have been achieved according to the sneak expressions.

February 2016
Capital SimProve
• Failed functions are those function that have not been achieved according to the function
expression, but should have been achieved according to the sneak expressions.
Below is an example of a sneaked function.
To run an SCA operation click the button.

To simulate the situation (display all electrical activity in the ECAD tool) when a concern was
detected, select the concern and click the button.
To show the predicted sneak path (highlight path in yellow in the ECAD tool) click on the
button.
To delete a concern that is no longer required, select the concern and click the button.
Note
The predicted sneak path functionality will only display on connectivity that is wiring.
Nets will be colored as normal, displaying electrical activity.
Related Topics
Creating an SCA Report SCA Report View

February 2016
Capital SimProve
Creating an SCA Report

Scoping

To run an SCA operation from Capital SimProve:
Procedure
1. Click the button and the SCA Wizard will open.
2. Read the instructions and select Next.
3. If you wish to capture details of the SimProve run, check the Create audit report
checkbox. This enables you to create an audit report preserving the configuration details
and results. The system offers a default name for the report which can change if
required.
The report can be used to study the design impact between SimProve run sessions to
improve design quality and provide traceability of the audit trail. The results of the audit
report can viewed on the Audit Report Tab, and also viewed and managed using the
Object Manager.
You can run the analysis action as a background operation by checking the Run in
Common Functions User Guide for further information. Running the analysis
operation in the background allows you to continue working on other analysis tasks
knowing you can open and interrogate the audit report at a convenient time.
Note
Audit report generation is automatically selected whenever the Run in background
option is checked.
Once you have decided on your report and background run requirements, click Next.
4. Select the type of simulation radio button and click Next. The simulation technologies
that are enabled on this page will depend on what simulator modules are licensed and
whether you have configured an external simulator using Capital SimBridge (see
“Capital SimBridge” on page 155 for more information).
Check Use transient if transient mode should be used with the selected simulation type.
5. If Use transient is selected, an additional pane above will be displayed. You can specify
transient information:
• Start Time - The point in time that the analysis should start, this defaults to zero.

February 2016
Capital SimProve
Advanced Functionality (Capital SimProve)
recorded.
• Variable Time Steps - This is a mode of operation of the numeric transient
the results.
6. Select the input components you wish to exercise during the simulation. By default all
the input components will be used. Uncheck those that you wish to ignore and click
Next.
7. If you choose to ignore some components then the next step in the wizard will ask you
what settings you want to leave these input components with. If you select all the
components then you will not see this window.
8. If you would like to apply failure modes during the analysis, click on the Edit Failure
Modes button. In the dialog, use the Components tree to select the failure modes you
wish to analyze. By default none of the failures are selected.
9. Tick the tick box if you want to prune the results and then click Close to close the
wizard and start the SCA Analysis.
Use the Back and Next buttons to move backwards and forwards through the SCA
Wizard and the Cancel button to exit it at any point.
Related Topics
Prune an SCA Report SCA Report View
Scoping Overview of Capital SimProve
Advanced Functionality (Capital SimProve)

Checking the 'Enable advanced functionality' checkbox on the first page of the wizard adds a
number of pages to the wizard.
With this checked the following options are available:
• Power nodes for failure application. See “Power Node” on page 46 for more detail on
power nodes.
• Numeric simulation overrides. See “Overrides” on page 45 for more detail on numeric
simulation overrides.
• Component Parameters modification. See “Component Parameters” on page 44 for
more detail on component parameters.

February 2016
Capital SimProve
Exporting an SCA Report
Related Topics
Exporting an SCA Report

To export an SCA report from Capital SimProve:
Procedure
1. Click the File > Export menu entry, the Export SneakReport window will now open.
2. Select the type of export file you which to create and press the Next button.
3. Select the ordering you require in the exported SCA report and click the Next button.
4. Select the filename and location where you want the exported file to be placed by using
the Browse button. The click the Next button.
5. After a few moments the SCA report will be exported.
Related Topics
Creating an SCA Report SCA Tool Menus
Prune an SCA Report

On the 7th step of the SCA wizard you get the choice of wether or not you want the results of
the SCA report pruned or not. The pruning wizard step is shown below:

February 2016
Capital SimProve
Prune an SCA Report
Pruning will remove duplicate and redundant entries in a SCA report.
A report without pruning may have 2000 concerns in it which can be reduced to 85 real
concerns by using the pruning function. It is normal for pruning to reduce the number of
concerns by one or two orders of magnitude.
For example, consider a schematic which has 10 switches on it and has a sneak circuit which
only exists when 2 of the switches are in a certain combination regardless of the other 8 switch
positions. With pruning switched off the SCA report will generate a concern for every switch
combination which creates a sneak circuit, most of these concerns will be caused by the 8
switches' positions going through their various combinations when the 2 switches are in their
certain combination. If pruning is switched on then the results will analyzed by the pruning
function and all the concerns which are cause by the 2 switches being in a certain combination
will be reduced to one concern which just shows the 2 switches being in their certain
combination and the other 8 switches' positions not mattering.
Related Topics
Exporting an SCA Report SCA Report View

February 2016
Capital SimProve
SCA Report View

SCA Report View

The SCA report is written to the Concerns tab. The are three viewing modes of an SCA report.
The View menu is used to select between them. The arrow buttons can be used to move back
and forth if the SCA report is large.
Concern View
In this view, the detected issues are ordered based on the switch setting that caused them. This
view is useful for deleting those concerns that no longer of interest to you. See the example
shown below

February 2016
Capital SimProve
SCA Report View
Function View
In this view, the concerns are ordered based on the functions the concern has effected. This
view is useful for determining which functions the concerns actually effect. There may be many
concerns but only one or two functions the concern effects. See the example shown below.
Type View
In this view, the concerns are ordered based on their type (sneak or failure). This view is useful
in determining the type of concerns detected. Are they all sneaks? See the example shown
below.

February 2016
Capital SimProve
SCA Tool Menus
Simulation Displays Tab

The Simulation Displays tab allows the engineer to view the electrical properties and state when
the sneak occurred. It's functionality similar to that of the Simulator's Simulation Displays tab.
Related Topics
SCA Tool Menus

This topic details the SCA Tools menus.
File menu
• Run SCA: run/rerun the SCA operation .

February 2016
Capital SimProve
SCA Tool Menus
• Simulate Concern: simulate the selected concern in the ECAD tool .

• Highlight Sneak Path: highlights the sneak path in the ECAD tool .
• Print: Print the report.
• Page Setup: Page settings for printing.
• Export...: export the SCA report.
• Exit: Exit Capital SimProve.
Edit menu
• Delete Concern: Delete the selected concern .
• Delete All Concerns: Delete all the concerns in the report.
View menu
• Concern view: view the results by the concern.
• Function view: view the results by function name.
• Type view: view the results by sneak failed functions.
• Goto page: opens a dialog to go to another page of concerns.
• Netlist Errors: opens the Error Report Dialog which shows messages produced during
the netlist.
• Color Components: if checked the components will be colored when the concern is
shown.
• Show Labels: if checked the labels will be shown when the circuit is colored.
Related Topics

February 2016
Capital SimProve
SCA Tool Menus

February 2016
Chapter 10
Capital SimStress
The Capital SimStress performs a numerical analysis of your design and generates a results
table that contains results defined by a 'stress style'.
Overview of Capital SimStress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Defining Applied Current, Voltage and Power Algorithms. . . . . . . . . . . . . . . . . . . . . . . 146
Defining Stress Styles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Overview of Capital SimStress

The Capital SimStress performs a numerical analysis of your design and generates a results
table that contains results defined by a 'stress style'. The supplied stress styles allows the
traditional formatting of stress results. This style displays the voltage, current and power values
for each component, and suggested wire CSA. This data can be back propagated to the ECAD
tool.
In addition to the above information, any concerns found during the analysis will be displayed
in the concerns tab of Capital SimStress. The concerns could be related to fuses blowing, or
short circuit conditions.
The tool performs a simulation for each combination of inputs in the schematic, simulation
results are generated and the report populated in accordance to the stress style. For all reporting,
some special internal values (automatic properties) are available from the components and
wiring, namely max. 'applied current', max. 'applied voltage' and 'applied power' developed.
These values are generated by calculating the current and voltage power for each arc in the
component and then taking the arc's value that is highest. Power is calculated by summing the
power developed in each arc.
The 'automatic properties' are displayed in the basic stress style format supplied. The automatic
properties for voltage, current and power can also be overridden, see “Defining Applied
Current, Voltage and Power Algorithms” on page 146.
It is possible to define your own stress styles and report on any component output property, or
ECAD property. This enables the report to be specific, for example, wire sizing information
only. See “Defining Stress Styles” on page 147 for more information.
For wire sizing, the analysis is run using wire size information in the design (or system defaults
if unavailable). If the load on the wire exceeds its rating, then a suggested wire gauge is
displayed in the results.

February 2016
Capital SimStress
It is also possible to perform sizing of other devices. Please check available tech-notes on sizing
specific devices.
Note
Upon launching Capital SimStress, if you have Robust Netlisting enabled, a message will
be displayed to inform you that the results displayed may differ from those expected.
Refer to “Robust Netlisting” on page 41 for more information.
Running Stress Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Stress Analysis Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Wire Sizing and Back Propagation of Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Running Stress Analysis

The results are displayed on the screen and are also saved to a file. The results form the basis of
the information to perform a full Stress Analysis. The file results can be used within other tools
that apply rules to detect components that are operating outside of specified tolerances.
In your Capital design application, select the analysis scope, press Space Bar and enter Capital
SimStress.
Note
If you have Robust Netlisting enabled, a message will be displayed to inform you that the
results displayed may differ from those expected. Refer to “Robust Netlisting” on
The dialog below is displayed:

February 2016
Capital SimStress
Figure 10-1. Capital SimStress Interface
Capital SimStress can now be used to open and display previous reports or create new reports
using the Stress Analysis Wizard.
Note
additional dialog will appear when starting the FMEA tool requesting the configuration to
analyze. Select one from the list.
Related Topics
Stress Analysis Wizard
Stress Analysis Wizard

This topic details the Stress Analysis Wizard.

February 2016
Capital SimStress
Procedure
1. To start the wizard select File > Run Stress Analysis... from Capital SimStress.
2. In the first dialog, you can select a previously generated stress report to use the settings
from that to generate a new stress report. Click Next to continue. If you have selected a
previously generated stress report, skip to step 13. Otherwise, continue with step 4.
3. This step offers the option to create an audit report which allows you to preserve the
configuration details and results of your Stress Analysis run. Click the Create Audit
Report checkbox to enable the functionality. On selection the Name field is enabled,
allowing you to specify a report name, or accept the default entry offered.
The generated Audit Reports are available for viewing in the Audit folder in the Object
Manager.
You can run the analysis action as a background operation by checking the Run in
Common Functions User Guide for further information. Running the analysis
operation in the background allows you to continue working on other analysis tasks
knowing you can open and interrogate the audit report at a convenient time.
Note
Audit report generation is automatically selected whenever the Run in background
option is checked.
Once you have decided on your report and background run requirements, click Next.
4. You must select the simulation type that the stress analysis will use to create its report.
There may be different options depending on the version you are running, and whether
you have configured an external simulator using Capital SimBridge (see “Capital
SimBridge” on page 155 for more information).
• Check the Use transient box to run the analysis under transient mode if required.
• Check the Enable advanced functionality box if you want to use advanced settings
to run the report.
Click the Next button to continue.
5. If you did not check the Use transient box, skip to step 6. If you did check the Use
transient box, you must specify the following transient simulation settings:
• Start Time - The point in time that the analysis should start.
recorded.

February 2016
Capital SimStress
• Variable Time Steps - This is a mode of operation of the numeric transient

the results.
Click the Next button.
6. If you did not check the Enable advanced functionality box, skip to step 9. If you did
check, the Enable advanced functionality box, you must specify the power node that
short to battery failures use. See “Power Node” on page 46 for more information on
power nodes. Click the Next button.
7. If required, you can override the global numeric simulation settings for a simulation. See
“Overrides” on page 45 for more information on numeric simulation overrides. Click the
Next button.
8. If required, you can modify the values of component parameters that are user-definable
to change the behavior of the model. See “Component Parameters” on page 44 for more
detail on component parameters.
If you have overridden parameter values when running a stress analysis previously, you
can reference the stress report xml file to use the override values from that analysis run
in the current analysis. To do this, click the Select a File button in the Override File
section of the dialog to browse to the stress report file that contains the override values
that you want to use. Click the Open button to select the file.
After you have selected the stress report file, the values in the Component Parameters
box are overridden. You can still modify these values further.
Click the Next button to continue.
Only the override values information from the <overrideList> section of the stress report
is used when you reference a stress report file.
As an alternative to referencing a stress report file, you can create your own override file
by copying the <override section> from a stress report file to another xml file in the
following format:
<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<stressReport>
<overrideList>
<overrideComponent name="DEV1">
<override property="Internal_Input_Integer" value="3334"/>
</overrideList>
</stressReport>
This example contains only one property override value.
9. You must specify whether you want to evaluate rules and actions in your stress report.
Select one of the following:

February 2016
Capital SimStress
• No rules or actions should be evaluated - no rules or actions triggered by rules are

evaluated. No information regarding rules is displayed on the Rules tab of Capital
SimStress.
• Evaluate Rules only - rules are evaluated. The components that triggered the rules
and any messages resulting from issue statements in the rules are displayed on the
Rules tab of Capital SimStress. Action statements from rules are not evaluated.
• Evaluate Rules and Actions - rules and actions are evaluated. The components that
triggered the rules, the actions triggered by the rules and any messages resulting
from issue statements in the rules and actions are displayed on the Rules tab of
Capital SimStress.
10. You must select which of the schematics input components you want to exercise during
the generation of the report. Double-click on the name of an input component to select
and de-select each one.
Alternatively, you can select a scenario sequence file that has been created using the
Simulator Tool. To do this, click the Select a new object button at the bottom of the
dialog to browse to the scenario sequence file that you want to use. Click the Open
button to select the file. Note that you can cancel the association by clicking the Forget
this object button.
Note
If you select a scenario sequence file, the stress report will contain a section called
<scenario> that lists the events in the order that they took place.
11. If you did not select all the schematic's input components to be exercised, the next step
in the wizard will ask you to define the settings for the de-selected components. Specify
the appropriate values and click the Next button.
12. If you selected all the schematics input components for stress analysis, the wizard skips
straight on to the next step. This is used to select how the stress report is displayed. You
can select an existing style from the Stress Styles list or create a new stress style. Click
the Next button.
13. You must give the file name and the directory for the report to be saved in. You can use
the Browse button to navigate to a directory. Click the Next button.
14. The Summary dialog displays a list of the options selected in the wizard. Read the list
carefully and click the Back button to make any changes, or click the Run button to start
the stress analysis.
15. A status bar indicates the progress of the stress analysis.
16. The report will be displayed in Capital SimStress as shown below:

February 2016
Capital SimStress
The report shows the maximum applied voltages, currents and powers for each
component, node and pin in the schematic.
The following options are available to filter the returned data:
• Enter a regular expression into the search field (indicated by the magnifying glass
icon) to search on the contents of the topmost column configured in the report style
(displayed on the left of the grid by default). The following wildcards are supported:
o * - matches 0 or more of any characters
o ? - matches exactly 1 character
o [...] - matches a single character from the list in the brackets
o [^...] - matches a single character except those from the list in the brackets
o (...|...) - matches the first or second character group in the parantheses
o {N} - matches exactly N of the preceding character or group
o {M,N} matches M to N of the preceding character or group

February 2016
Capital SimStress
o ^... matches the start of the cell value

o ...? - matches the end of the cell value
Note
If no wildcards are used, the search string is case-insensitive and will match any string
that contains the expression. If any wildcards are used, the search string is case-sensitive,
and will match any string that starts with the expression.
• Columns can be repositioned within the report. To move a column, click on the
column name and drag it to the new position.
• Click the button to toggle the display of components within the data.
• Toggle the display of internal and external nodes by clicking the 3-way button; the
following modes are available:
o - all nodes are displayed
o - no nodes are displayed
o - only external nodes are displayed
• The report data can be sorted on a single column.
o Click a column header once to sort on that column in ascending order (indicated
by an up-arrow icon).
o Click the column header again to sort in descending order (indicated by a down-
arrow).
o Click a third time to remove the sorting.
Sorting is applied according to the Type of data specified for the column in the
report style (see “Custom Styles Dialog Box” on page 147 for more information).
o Integer and Real data types are sorted numerically.
o String data is sorted using a true alphanumeric sort, so any number groups
within a string are considered a single integer. For example, in an ascending sort,
1.3 is placed before 1.22.
Related Topics
Running Stress Analysis Wire Sizing and Back Propagation of
Properties

February 2016
Capital SimStress
Wire Sizing and Back Propagation of Properties

It is possible to propagate back wire sizing information and other generated column data to the
ECAD tool. Capital SimStress will generate the suggested wire sizing information and populate
the results table with it.
Running the Analysis

To perform wire sizing analysis in your Capital application, press Space Bar and enter Capital
SimStress. In Capital Integrator, press Space Bar and enter Component Sizing.
In Capital Integrator, in the Component Sizing dialog that appears, there are options to apply
the results to all configurations or a particular configuration. Either check the Use all
configurations box or select the specific configurations that should be analyzed.
In the Stress Analysis Wizard, follow the steps described for “Running Stress Analysis” on
page 136.
When the analysis is complete, Capital SimStress will show the results table. The columns
Wire CSA (max), Wire CSA (mean) and Wire CSA (min) columns contain suggested wire
sizes.

February 2016
Capital SimStress
The Wire CSA (max) column displays the gauge that should be used to allow the maximum
current to flow safely after performing the analysis. Wire CSA (mean) contains the mean gauge
found from the analysis.
Property Back Propagation

To propagate column data back such as the wire sizing information:
1. Click the Propagate Back button . A dialog is displayed from which you can select
the column of data to use:
2. Select the column of data you want to back propagate from the Column Heading
dropdown list, then click OK.
• In Capital Logic the Back Propagate dialog is displayed:
Enter the name of the property in the Property name field as you would like it to
appear on the component, wire or net, choose the item to which the property is to be
applied from the Apply to radio group, then click OK. If an attribute is found for the

February 2016
Capital SimStress
selected component type with a name matching the entered Property name, the
value will be entered into the attribute. If no matching value can be found, the value
will be entered into either a property with a matching name, or if one does not exist,
a new property.
• In Capital Integrator, the Back Propagate Wire Size dialog is displayed:
Enter the property name in the Property field and click the OK button. If a wire
attribute is found with a name matching the entered Property name, the value will
be entered into the attribute. If no matching value can be found, the value will be
entered into either a property with a matching name, or if one does not exist, a new
property.
The following fields are also available to support the reselection of wires from the
library based on the back-propagated values:
o Use Library to lookup material specification
Select this option to force the selection of a new wire specification based on the
WireCSA supplied and the material of the currently assigned wire.
o Use default material
Select this option, then select a material from the dropdown list to force the
selection of a new wire specification based on the WireCSA supplied and the
specified material.
• In LCable, the property pushback dialog below is displayed:

February 2016
Capital SimStress
Defining Applied Current, Voltage and Power Algorithms
Enter the name of the property that will appear on LCable wires or components.
Click on the OK button to exit the dialog and pushback the property.
Concerns
The concerns tab displays any concerns found during the analysis run and the input conditions
under which they were found. Examples of concerns are fuses that have blown or short circuit
conditions that have been found.
Rules
The rules tab displays any rules that have been evaluated during the analysis run. For each rule,
the tab also displays the component that triggered the rule, any actions triggered by the rule and
any messages resulting from issue statements in the rules or actions.
Related Topics
Scoping
Defining Applied Current, Voltage and Power Algorithms
Defining Applied Current, Voltage and Power

Algorithms
You can define your own algorithms to calculate the applied Current, applied Voltage and
applied Power for a component by defining them within the components behavior. To do this
follow the instructions below:
Procedure
1. Create a new component interface property in the Component Builder (see “Defining a
Component Interface” on page 164).

February 2016
Capital SimStress
Defining Stress Styles
2. Ensure that the property has the following settings:

• The property's Name must be either appliedCurrent, appliedVoltage or
appliedPower.
• The property's Scope must be Internal.
• The property's Direction must be Output.
• The property's Type must be Floating-point.
3. Describe your algorithm in the components behavior using the Dependency Editor or
State Builder.
Capital SimStress will automatically pick up the property names and use them for the stress
analysis simulation. Of course, they must be defined in the stress style to appear in final report.
Applied Power will always be worked out by summing the power of a component's individual
arcs unless it is overridden by a property called appliedPower.
The results are displayed on the screen and are also saved to a file. The file results can be used
within other tools that apply rules to detect components that are operating outside of specified
tolerances.
Related Topics
Component Builder Overview of Capital SimStress
Defining a Component Interface

Stress reports can tailored to the engineer’s needs. This is done on the Custom Styles window
when you perform a stress analysis from the Stress Analysis Wizard.
A new style can be defined using the Custom Styles Dialog.
Custom Styles Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Creating a New Stress Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Editing a Stress Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Deleting a Stress Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Import and Export of Stress Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Custom Styles Dialog Box

The Custom Styles dialog, accessed by selecting Edit > Report Styles from the Stress
Analysis Tool.

February 2016
Capital SimStress
It is used to create a new style, shown below.

Fields
Table 10-1. Custom Styles Dialog Box Contents
Field Description
Style Name The name of the stress style being created.
Style A textual description of the stress style being created.
Description
Columns in Available - A list of columns that can be displayed in the
Style stress report. Aside from the default columns, you can add a
new column by clicking the button and entering a new
name in the Column Title field (see below). You can delete
any columns created in this way by first selecting it in the list,
then clicking the button (default columns cannot be
deleted). To display a column in the stress report, it must be
moved into the Used list. The following options are available
to move columns between lists:
• Click the button to move a selected column from the
Available list into the Used list.
• Click the button to move all columns from the
Available list into the Used list.
• Click the button to move a selected column from the
Used list into the Available list.
• Click the button to move all columns from the Used
list into the Available list.
Used - A list of all columns selected for display in the stress

report. The order in which columns are displayed in the stress
report is determined by the order of the columns in the list:
the column at the top of the list will be displayed on the left
of the report; the column at the bottom of the list will be
displayed on the right. The following options are available to
order the columns within the list:
• Click the button to move a selected column one
position higher in the list.
• Click the button to move a selected column one
position lower in the list.
Details Tab The following options are available to configure the column
name and the source of the data displayed.
Column The title of the column as it exists in the database.
Title
Column The title of the column as it is displayed in the report.
Heading

February 2016
Capital SimStress

Field Description
Source This is sthe ource of the column data.
• modelProperty - Data source is an interface property
from an analysis component model (see “Defining a
Component Interface” on page 164).
• nodeProperty - Data source is a property from a node of
an analysis component model.
• ecadProperty - Data source is a property from an ecad
component / wire / net.
• internal - Data source is an internal name or uid of the
component / wire / net.
Property This is name of the property that the column data will come
Name from. This can be entered by the user, or chosen from the
drop-down list (Source-dependant). Available options are as
follows:
• appliedCurrent (model property)
• appliedVoltage (model property)
• appliedPower (model property)
• blowTime (model property)
• blowCurrent (model property)
• V (node property)
• RToPwr (node property)
• RToGnd (node property)
• uid (internal property)
• name (internal property)
Type This specifies the data type of the property being recorded.
This is required for further processing of the xml results file
(source dependant).
• integer - a whole number

• real - a floating-point (decimal) number
• string - one or more alphanumeric characters

February 2016
Capital SimStress

Field Description
Obtain The behavior of this option varies according to the Type
specified above.
• With a Type of integer or real selected, this specifies any
mathematical operation to be performed on the data in the
field:
• maximum - records the maximum value that the
property reached during the analysis.
• minimum - records the minimum value that the
property reached during the analysis.
• average - records the average value of the property
during the analysis.
• With a Type of string selected, this specifies any string
operation to be performed on the data in the field:
• last - records the final value the analysis encounters.
• first - records the first value the analysis encounters.
• mode - records the most frequently occuring value the
analysis encounters.
• With a Type of string selected, this specifies any string
operation to be performed on the data in the field:
• last - records the final value the analysis encounters.
• first - records the first value the analysis encounters.
• mode - records the most frequently occuring value the
analysis encounters.

February 2016
Capital SimStress

Field Description
Format Tab These options are available to format the data displayed in
columns with a Type of Real specified. Select one from the
following:
• Precision - This option allows you to specify the

rounding that is applied to the numerical data. Enter a
value into the field, then specify whether the entered
value indicates the number of Decimal Places or
Significant Digits to which to round the number.
• Pattern - This option allows you to control the display of

numerical data by creating a format for the column. The
following formatting characters are supported:
• # - specifies that a numeric character in this position
should be displayed. For example, 12.345 formatted
using ##.## is displayed as 12.35 (5s are rounded up).
• 0 - specifies that a character in this position should be
displayed, but if no character is present, display a zero.
For example, 12.345 formatted using 0##.###0 is
displayed as 012.3450.
• . the placeholder for the decimal point. All formatting
is applied relative to this position.
• SPACE - adds a leading or trailing space to the
number.
• E - defines the beginning of an exponent when
formatting exponential data. For example, 12.345
formatted using ##.#E## is displayed as 12.3e45.
Related Topics
Creating a New Stress Style Editing a Stress Style
Deleting a Stress Style Import and Export of Stress Styles
Creating a New Stress Style

To create a new style, do the following:
Procedure
1. Click the Create new Style button in the Stress Styles page of the Stress Analysis
Wizard, or by first selecting Edit > Report Styles from the Stress Analysis Tool.
2. Enter the new style name in the Style Name field.

February 2016
Capital SimStress
3. Give the new style a description in the Description field.

4. The Used field offers a default selection of columns; add or remove columns from the
list until the required column set is defined (see “Custom Styles Dialog Box” on
page 147 for information on column selection).
5. If required, add new columns by clicking the button, then configuring the Column
Details. Again, see “Custom Styles Dialog Box” on page 147 for more information.
6. Configure each column:
• Select the source from the Source dropdown list.
• Enter the property name of the source value in the Property Name field, or select
from the list.
• Specify the Type of data in the column by selecting one of the options from the
dropdown list.
• For any columns with a Type of Real specified, configure the formatting options
(available on the Format tab - see “Custom Styles Dialog Box” on page 147 for a full
description of the options available).
• In the Obtain dropdown list, select any mathematical field processing (if
applicable).
7. Specify the order in which columns should appear in the report using the move up and
move down buttons above the User field. See “Custom Styles Dialog Box” on page 147
for more information of ordering columns).
8. Click OK to save the style and close the dialog.
Related Topics
Editing a Stress Style Import and Export of Stress Styles
Deleting a Stress Style
Editing a Stress Style

You can Edit a stress style.
Procedure
1. Select a stress style from the Stress Styles list in the Stress Analysis Wizard.
2. Click on the Edit Selected Style button .
3. Modify information in the Custom Styles Dialog Box where appropriate. If modifying
column data, select the column from the Used list first.

February 2016
Capital SimStress
4. Click Apply to save the changes.
Related Topics
Creating a New Stress Style Import and Export of Stress Styles

You can Delete a stress style.
Procedure
1. Select a stress style from the Stress Styles list in the Stress Analysis Wizard.
2. Click on the Delete selected style button .
Related Topics
Creating a New Stress Style Import and Export of Stress Styles
Editing a Stress Style
Import and Export of Stress Styles

It is possible to import and export stress styles for sharing the styles with other instances of
SimCore. This can be done in two places.
• Stress Analysis Tool - From the Edit menu.
• Stress Analysis Wizard - By selecting the Advanced tab in the Stress Styles panel, of
the Wizard.
Procedure
1. Select Edit > Edit report styles from Capital SimStress, or select the Advanced tab in
the Stress Styles panel, of the Wizard.
2. In the Advanced tab of the Stress Styles panel, select the import button, .
3. Select Report Style XML Import, from the import wizard, click Next.
4. Select the file to import by clicking Browse, in the import wizard, open the file from the
dialog.
5. Click Close, to close the wizard.
To export a stress style follow the steps below:

February 2016
Capital SimStress
1. Select Edit > Edit report styles from Capital SimStress, or select the Advanced tab in
the Stress Styles panel, of the Wizard.
2. In the Advanced tab of the Stress Styles panel, select the export button, .
3. Select Report Style XML Export, from the export wizard, click Next.
4. Select the location of the export file by clicking Browse, in the export wizard, enter the
file name and location in the Save dialog, close the dialog, click Next in the wizard.
5. Click Close, to close the wizard.
Related Topics
Overview of Capital SimStress Defining a Component Interface
Component Builder

February 2016
Chapter 11
Capital SimBridge
Capital SimBridge adds external simulation functionality to the following scope-level

simulation tools:
Introduction to Capital SimBridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Simulator Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Capital SimScript. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103)
Capital SimCertify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Capital SimProve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Capital SimStress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Introduction to Capital SimBridge

Capital SimBridge allows the invocation of external simulation technology when performing
any scope-level simulation, allowing users to integrate their own technologies into Capital
Analysis. Once configured, the external simulator will be available as a new simulation type;
running the simulation will result in the generation of a netlist and job description, which will be
passed to the external simulator, the simulation performed, and the results collected for further
simulation, report generation or simply user feedback.
Once an external bridge has been configured, it will be available for selection as an alternative
simulation type within the simulation tools.
The degree of functionality available to the external simulation will be dictated by its design.
For example, the coloring of schematics according to the results returned is one option available
to developers when creating the external simulator. A document has been created to provide
developers with all the information they need to develop an external simulator, and it is
included as part of the Capital Analysis installation. It can be found in the /docs/simbridge sub-
directory of your Capital Analysis home folder, and is named:
Guide to interfacing with external simulators using Capital SimBridge.
Before you can access the external simulator in any of the scope-level simulation tools, you
must first configure your Capital Analysis installation to find and run the simulator.

February 2016
Capital SimBridge
Configuration
Configuration
Capital SimBridge is configured within a properties file that gives Capital Analysis all of the
information it needs to integrate the external simulation technology.
Procedure
1. From your Capital Analysis home directory, navigate to the /resources/resources sub-
directory, and open the file named SimBridge.properties.
2. Modify the following lines within the file:
SimBridge.supported=<name of bridge>
Replace <name of bridge> with the name of the external bridge component
<name of bridge>.visibleName=<visible bridge name>
Replace <visible bridge name> with the name of the external bridge as it should be
displayed in the Capital Analysis user interface
<name of bridge>.commandLineInvocation=<Command Line>
Replace <Command Line> with the command line used to launch the external
simulator, and add the following optional parameters:
o the path to the location in which the file containing the generated netlist is to be
created
o the path to the location in which the job file is to be created
o the path to the location in which the results file is to be created
If any of these parameters are missing, Capital SimBridge will create ALL files in
the directory specified by the TEMP variable used by your Capital installation.
<name of bridge>.interfaceVersion=1.0
This line identifies the version of the netlist and results formats that the simulator
understands, and hence should not be changed.

February 2016
Capital SimBridge
Configuration
Note
Although it is possible to enter multiple bridges into the SimBridge.supported line,
specifying all configuration settings for each bridge, at this release, support is only
available for a single bridge. If more than one bridge is configured, when Capital
Analysis is launched, a message will be displayed to inform you that only the first bridge
in the list will be available for use in simulation.
For example, both of the following formats are allowed:
SimBridge.supported=Bridge1 Bridge2
and
SimBridge.supported=Bridge1
SimBridge.suppoirted=Bridge2

February 2016
Capital SimBridge
Configuration

February 2016
Chapter 12
The Component Builder Tool
Capital Analysis simulates the behavior of a circuit for each of the failure modes for each
component in the design. To achieve this, a model of each class of component needs to be
defined. This model describes the structure and behavior of a component under both normal
operation and under any failure modes.
A set of models for common components is supplied with Capital Analysis. You will typically
need to define a number of additional models that are particular to your work. This section
describes the Component Builder tool that is used to create these models.
Overview of Component Builder Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Component Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Creating a new component model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Selecting a Component Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
The Behavior Modeling Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Defining a Component Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Defining Component Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Moving Objects in the Structure Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Deleting Objects in the Structure Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Pin Naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Defining Component Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Defining Failure Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Quantization Bands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Shared Object Component Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Embedding Hierarchical Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Embedding VHDL-AMS Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Component Model Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Component Builder Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Component Library - Component Models Provided . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Attaching Component Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Component Builder Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Description Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Component Builder Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Component Builder Related Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

February 2016
Overview of Component Builder Tool
Structure Editor Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

Overview of Component Builder Tool

The structure of a component is defined as a network of resistive nodes. The nodes take one of
three values: ZERO, LOAD, INFINITE. These values are used during simulation to determine
if current can flow through the various sections in the component. There are additional types of
resistance nodes for use in modeling source and sink connections, such as required in an ECU.
The terminal pins correspond to the pins on the actual ECAD component drawing.
The behavior describes how the resistance values change as a result of the changing inputs to
the component. There are two ways to provide this description:
• Expressions - define the state of the resistances under certain conditions. Expressions
are written as if-then-else statements.
• State Charts - more complex component behaviors should be modeled as state charts.
These can include concurrent states and timing information.
In addition to describing the normal operation of the component, it is necessary to define the
different component failure modes to be explored in the FMEA. For each failure mode, you
describe the way in which the failure mode affects the component. This may be a structural
change, a behavioral change or a combination of the two.
Tools
Component Builder- This tool is started from the ribbon on the Capital applications. It is used to
create new components, define the structure, failure modes and behavior expressions.
Related Topics
“Attaching Component Models” on page 199
“Creating a new component model” on page 162
“Component Library - Component Models Provided” on page 198
Component Builder
Every component in Capital Analysis is defined as a set of terminals, resistances, and the
relationships between the two.
Standard components such as wires, lamps, motors, relays and switches are provided as part of
the Capital Analysis Component Library - Component Models Provided. The Component
Builder provides the facilities to construct component models.

February 2016
Component Builder
Note
A Language Reference Guide is included on your Capital Analysis installation CDs for
further information on creating component model behaviors.
There are six main stages in defining an Capital Analysis component, They are as follows:
• Selecting a component category (see “Selecting a Component Category” on page 163)

• Behavior modelling types (see “The Behavior Modeling Type” on page 164)
• Defining a components interface (see “Defining a Component Interface” on page 164)
• Defining a components structure (see “Defining Component Structure” on page 167)
• Defining the components behavior (see “Defining Component Behavior” on
page 172)
• Defining failure modes (see “Defining Failure Modes” on page 174)
When the component model is complete, use the button to check that the syntax of the
expressions is correct.
Note
Clicking the Promotion icon ( ) allows you to filter the list of interface properties or
failure modes based on their ownership (from the current model or from the hierarchy)
and promotion status. Note - the icon changes according to the setting selected. For
further information see “Overriding Interface Property or Failure Mode Promotion” on
page 204.
There are 3 different windows with menus used when creating an Capital Analysis component
model. They are the Component Builder window, the Structure Editor window and the
Dependency Editor window. The menus for these 3 windows are covered in these sections:
• “Component Builder Menus” on page 212

• “Dependency Editor Menus” on page 215
• “Structure Editor Menus” on page 214
Related Topics
“Quantization Bands” on page 176

February 2016
Creating a new component model
“Component Model Templates” on page 189
Creating a new component model

Do one of the following to create a new component model.
Procedure
1. Start a new ComponentBuilder from the ECAD tools main analysis menu
a. Press Space Bar and enter Model Builder.
Or
2. Create a new component from within the ComponentBuilder
a. Choose File > New.
3. The Create New Component dialog is displayed:
4. Select the component type. The default option is Other.

5. Select the behavior modelling type. The default option is to create Expressions to
describe behavior.
6. Press OK to create the new component model. The main Component Builder window is
shown.
If the component that you were previously working on has changed since it was loaded,
you are asked whether you wish to save any changes.
Related Topics
Attaching Component Models Component Library - Component Models
Provided

February 2016
Selecting a Component Category
Selecting a Component Category

There are 8 different categories for Capital Analysis component models by default.
They are:
• other (default type)

• positive
• negative
• connections
• fuses (a fuse rating can be set; see “Fuse Rating Dialog Box” on page 210)
• diodes
• chassis
• template (a template is a special type of component that allows the re-use of
Dependency-based behaviors and component interfaces; see “Component Model
Templates” on page 189 for more information)
Categories can be added to via the Options dialog.
The selection is made from the Create New Component window:
Located in the top section of the window is a button with the default category (other) selected
and a small triangle indicating a picklist. Clicking on the button will make the picklist appear
allowing the user to select the desired category.
Related Topics
Component Builder

February 2016
The Behavior Modeling Type
The Behavior Modeling Type

There are two ways of modelling the behavior of Capital Analysis component models.
• Dependency expressions (see “Defining Component Behavior” on page 172)
• State machines (see “State Builder” on page 217)
The selection is made from the Create New Component window (see “Creating a new
component model” on page 162) by clicking the corresponding radio button for the desired
method. Once the component category and the behavior modelling type have been selected,
click the "OK" button and start creating your component model.
It is possible to change the behavior modelling model by selecting Tools->Change Behavior
Type. You will be prompted to confirm that you wish to change the behavior type. This is
important because the existing dependency expression or state-chart will be lost when the
model is converted. Please note that the model is automatically saved after the behavior type is
changed, and this operation cannot be undone.
Related Topics
Component Builder

A component interface is created to facilitate data sharing beyond the scope of this component,
and data sharing between normal operation and failure mode. The interface property is needed
for:
1. data sharing between components
2. data sharing with the analysis engine to change or pass a value to the component (input
interface property)
3. data sharing with SimStress report
Also, the interface properties can be fully accessed by SimScript. For example, you can create
an input interface to allow the analysis engine to turn on or off a light and an output property to
allow the analysis engine to indicate the emitting status of the light.
To define a new component interface, first click the 'New' button in the 'Component Interfaces'
section of the Component Builder. This will introduce a new blank interface.

February 2016
Figure 12-1. Component Interface Property Dialog
The following information must be entered to define the interface:
• Name - Give a name to the property or interface (i.e. A lamp would emit light).
• Promote - This flag adds additional visibility to a scoped (External) interface property.
Note
A promoted external property will be visible to the analysis engine to perform analysis on
interactive analysis (via a tool tip), SimStress, SimProve and SimCertify.
1) When used as an embedded model, the promoted interface property can be directly
accessible through the parent model.
2) When used as an embedded model, it is recommended that this interface property

value should not be changed within the scoping of the parent component.
(Note when in an application, the assignment or value change of a promoted input

interface property will prompt a warning during integrity checks, but is acceptable.
However altering the value of promoted output property prompts an integrity check error
and is not acceptable.)
An un-promoted external property will not be visible to the analysis engine to be

manipulated, except the SimScript. SimScript will ignore the promotion flag.
See Viewing Embedded Component Properties for details on how to inspect the
embedded models built-in and interface properties.

February 2016
Overriding Interface Property Promotion
• Scope -
o External - means the property will be visible in the simulation tool, for example: a
switch input or lamp output.
o Internal - means the property will only be available within component models
behavior, for example: used in passing values between a temperature sensor and a
controller.
o Parameter- means the property will be available in the Constants tab of The
Design Descriptor, for example: used as a global setting to change components
behavior depending on the simulation engine being used.
• Direction - Is it an input or output property (In the case of the lamp, light is an output
property).
• Type - Boolean, Enumeration etc. (the lamp will be of type Boolean).
• Default - Is it Active or Inactive by default (light will be FALSE).
Note
You can override the interface property promotion status by double clicking on the row in
which it is implemented. This opens the Component Interface Property Dialog where you
can change the promotion status as required.
The following icons detail the status of the interface property within the Component Interface
and Operating Modes dialog.
Figure 12-2. Interface Property States
Overriding Interface Property Promotion

The Promotion tab is used to override either interface property promotion or failure mode
promotion on a per-model basis. This functionality is available from both the Attacher dialog,
and when setting a model’s promotion status during its creation in Capital Symbol.
When an embedded model or composite symbol is instantiated on a design as a device instance,
its interface property promotion and/or failure mode promotion setting is also instantiated from
the original default promotion status. Clicking on the icon allows you to add individual
promotion behavior to a model. The available settings revolve cyclically on each click of the
icon. These are detailed below.

February 2016
Defining Component Structure
Procedure
To override a promotion setting:
1. Select whether you wish to override the Interface Properties or the Failure Modes by
clicking the relevant radio button.
2. Set the promotion behavior by clicking the icon until the required status is reached.
Available settings are:
• - displays all the available interfaces or failure modes.
• - displays all the interfaces or failure modes owned by this model.
• - displays all the interfaces or failure modes promoted from the embedded model.
• - displays all the interfaces or failure modes blocked for promotion from the
embedded model.
3. Click OK.
Related Topics
Component Builder Attaching Component Models

There are 3 distinct stages in defining a component's structure although not all components
require all 3 stages to be completed.
The 3 stages are:
1. Specifying the terminals

2. Adding resistances
3. Defining inputs and outputs
Before invoking the Structure Editor to carry out these tasks, it is important to ensure that
"Normal Operation" is highlighted in the Operating Modes section of the Component Builder
window. Every component needs to have a structure for the Normal Operation mode. The user
can now invoke the Structure Editor window by clicking the "Edit Mode's Structure" button
located on the lower right hand side of the window.
An empty Structure Editor window is shown in below:

February 2016
The yellow grid shown is a user definable preference and can be turned on or off via the View
menu.
Specifying Terminals
The first step in defining a component's structure is to specify the terminals.
To specify a terminal, the user must select the Terminal button from the speed bar down
the left hand side of the Structure Editor window. When the cursor is then moved onto the
canvas it automatically changes to a cross-hair. Clicking the left mouse button will place the
node on the canvas and a dialog will appear like the one shown in figure below asking for an
appropriate name for the terminal. By default the first node will be called NODE1, the second
NODE2 and so on. The text that the user enters will automatically be converted to upper case.
See “Pin Naming” on page 172 for more details.
You can also specify if a node is external (used to represent the parts of the component that
interface with the outside world) or internal (used purely to connect different resistances within
the component). Click OK to add the node with the specified settings. Click Cancel to cancel
the addition and remove the node from the drawing canvas.

February 2016
To define further terminals there is no need to select the Terminal button again as the cursor
continues to perform the same operation until another speed bar item is selected.
Defining Resistances
The functionality of the component is determined in terms of links between terminals. These
links can contain resistances which can change depending on the state of other parts of the
component.
To enter a resistance as part of a component's structure select the Resistance button from
the speed bar, and move the cross-hair over a circle representing a terminal. Click and hold
down the left mouse button and drag the cursor until the line being drawn joins with a circle
representing another terminal, and release the mouse button. When the line joins with a
terminal, the terminal will change to a red color.
This time a dialog like the one shown in the figure below will appear, not just asking for an
appropriate name (the default will be ARC1, ARC2 etc) but also for the type of resistance to be
selected. The resistance defined with this dialog is the default value. The value may change
during simulation as a result of the effects of normal or failure behavior.
In addition to simple resistance arcs, it is also possible to change the arc's type to fuse or diode.

February 2016
Diode Arcs
Diode arcs only allow current to flow in one direction through them. In addition it is not
possible to specify an infinite resistance for a diode, they must either have Zero or Load. The
allowed direction of current flow is indicated in the structure editor by arrows drawn over the
arc as shown in the image below:
Fuse Arcs
The final arc type is the fuse arc. Fuse arcs are considered require the specification of their
rating, as shown in the dialog below. Please note that units must also be specified.

February 2016
Moving Objects in the Structure Editor
The rating indicates at what level of current the fuse will blow.
Moving Objects in the Structure Editor

At any time whilst building a component's structure, it is possible to move individual nodes
around the canvas by simply clicking and dragging them. Multiple nodes or indeed the whole
structure can be moved by clicking and holding the left mouse button on the canvas outside the
component structure and dragging the cursor so the box outline covers the desired nodes. Once
highlighted, the nodes can be moved by clicking and dragging.
It is also possible to zoom in and out to view the structure in more detail. This can be done in 2
ways. By selecting the Zoom In/Zoom Out options from the Structure Editor View menu or by
clicking the Zoom In and Zoom Out buttons located on the Structure Editor tool bar.
Related Topics
Component Builder
Deleting Objects in the Structure Editor

There are 2 ways to delete objects in the Structure Editor window. In both cases the user must
first select the object or objects to be deleted. The object can then be deleted by selecting the
"Delete" option from the Structure Editor Edit menu or click on the delete button located on the
Structure Editor tool bar.
Related Topics
Component Builder

February 2016
Pin Naming
Pin Naming
When naming external nodes it is worth considering the rules below which the Attacher's
automated Terminal Mapping program uses to match the pins of the ECAD component with the
external nodes of the Capital Analysis component model.
The pins will be automapped if:
• The pins have the same name

• The ECAD pin is a <number> it will map it to the NODE<number> (i.e. 1 goes to
NODE1, 2 goes to NODE2)
• The ECAD pin is a <number> it will map it to the _<number> (i.e. 1 goes to _1, 2 goes
to _2)
• The ECAD pin is a <number>-<number> it will map it to the <number>_<number> (i.e.
J1-3 goes to J1_3, J1-4 goes to J1_4)
• There is only one pin on the ECAD component and on the component model.
When entering a name in the Node/Arc Details dialog the text will automatically be converted
to upper case and any space characters will be converted to underscore ('_') characters. By
default the first node will be called NODE1, the second NODE2 and so on.
Mapping also recognizes and accommodates space characters used in device pin names,
especially when the model port name is created using the automatic model builder. For
example, the mapper can detect that “AUDIO IN” and “AUDIO_IN” are actually the same and
map them accordingly.
Related Topics
Attaching Component Models
Defining Component Behavior

In Capital Analysis there are 2 different methods of defining component behavior. The first is to
use a series of dependency expressions, but for complex components Capital Analysis provides
the State Builder tool to allow engineers to model component behavior by using state charts.
Dependency Expressions
The Dependency Editor is where the behavior of a component is defined when the engineer
chooses to use dependency expressions. It will only be linked to a component if the Dependency
Expressions option was selected when the component was initially created. If the State Builder
tool is invoked instead of the dependency editor then the engineer must create a new component
this time selecting the dependency expressions option.

February 2016
Defining Component Behavior
It is very important to ensure that "Normal Operation" is highlighted on the Operating Modes
canvas of the Component Builder main window, before invoking the Dependency Editor. The
Dependency Editor is invoked by clicking on the "Edit Mode's Behavior" button located in the
lower right section of the window.
This will open a Dependency Editor window. The window is divided into two sections. By
default the left side is a blank text frame where the dependency expressions are written. The
right side of the window is also blank apart from the title "Commands" with a small triangle
next to it indicating that a pick list is available.
Clicking on the triangle will display the contents of the pick list. The pick list headings will
always be:
• Commands
• Operators
• Constants
• Structure
• Interface
These are directories containing everything required to build the dependency expressions for a
components behavior. However, although the directories will always be the same, the contents
of the directories will depend directly on the structure of the component whose behavior is
being modelled.
The practical part of constructing dependency expressions is very easy. The difficult part is
making sure the syntax is correct so that the component behaves in the way it was intended to.
To construct a dependency expression an engineer must find their way through the pick list of
directories for the syntax they require and select it by clicking on it. Once the correct syntax is
highlighted it can be entered onto the text frame by clicking on the arrow located to the left
of the pick list of directories.
It is better to use the pick list directories rather than typing the expression in directly as this
helps to cut down on errors.
Related Topics
State Builder Component Builder
Embedding VHDL-AMS Models

February 2016
Defining Failure Modes

The failure modes of a component enable you to define and analyze the failure behavior for the
component. In a failure mode, you can alter the behavior of a structure model and create its own
analysis behavior, or reuse the analysis behavior of the normal operation.
To define a new failure mode, click the New Failure Mode button to the right of the
Component Model Builder window. Under the Failure Modes directory a new mode will be
created after you have completed the Failure Mode dialog.
Figure 12-3. Failure Mode Definition Dialog
The dialog will ask for the following information:
• The name of the new failure mode.

• An occurrence value for the failure mode. The occurrence value indicates how often this
failure is likely to happen and is used in the calculation of Risk Priority Numbers
(RPNs). The lower the number, the lower the chance of the failure occurring. The
occurrence values are located on a pick list accessed by clicking on the small triangle
located in the top right hand corner of the dialog.
• The promotion flag allows users to block the failure mode from being visible by the
Analysis engine, making it unavailable for interactive analysis, SimProve and
SimCertify. If used as embedded model and with the promotion flag set as true, the
failure mode of the embedded model will be directly visible by the analysis engine.
Click the check box to enable the promotion of the failure mode, leave unchecked to
prevent its promotion. The flag indicates the default setting whenever the model is used.
• Whether or not the failure mode has its own behavior or uses the normal operation
behavior.

February 2016
When a failure mode is introduced, the structure of the component under the failure mode status
can be edited to show what effect the failure mode will impose on the physical behavior of the
component. To do this, first ensure that the correct failure mode is highlighted and then click the
Edit Mode's Structure button.
The Structure Editor will open and its title bar will display which failure mode has been
accessed. Even though the structure definition defined in the normal operation model cannot be
modified you can change the behavior of the existing model structure to mimic the physical
effect of the defined failure mode. Double clicking on a Arc allows you to alter the Arc behavior
for the failure mode. Double clicking on a Node allows you to alter the behavior of the node or
impose a new behavior for the node to mimic target failure mode behavior.
In the Node/Arc Details window there are various settings that can be used to simulate failures.
For example nodes can be shorted to other nodes and arc's resistances can be forced to set
values.
Selecting File > Exit will close the Structure Editor and allow you to go back to the Component
Model Builder where you can save your work by selecting File > Save.
If you have chosen to create a failure mode which has its own behavior then the Edit Mode's
Behavior will button will be active. Use this button to start either the StateBuilder or
DependencyEditor and describe the failure mode's behavior on the normal way. At this point,
all variable and functions will not be accessible, but the normal mode and failure modes will
share some interface properties for the component. Additionally all promoted interface
properties can also be accessed in the failure mode.
Note
You can override the failure mode promotion status by double clicking on the row in
which it is implemented. This opens the Component Interface Property Dialog where you
can change the promotion status as required.
The following icons detail the status of the failure mode within the Component Interface and
Operating Modes dialog.
Figure 12-4. Failure Modes States

February 2016
Overriding Failure Mode Promotion
Overriding Failure Mode Promotion

The Promotion tab is used to override failure mode promotion on a per-model basis. This
functionality is available from both the Attacher dialog, and when setting a model’s promotion
status during its creation in Capital Symbol.
Procedure
embedded model.
3. Click OK.
Related Topics
Component Builder Attaching Component Models
Quantization Bands
For Spice simulations each component model must have a Quantization Scheme attached to it
for Voltage, Current and Resistance. This is done by selecting Edit > Quantization Bands...
from the Component Model Builder menus. The Quantization Bands dialog will open allowing
you to choose appropriate QSchemes for the component model.
Below is an example of a current QScheme.

February 2016
Shared Object Component Models
The table below shows you the labels of the Quantization Bands each type of Quantization
Scheme must have in it for mixed mode simulations to work.
Resistance QScheme Current QScheme Voltage QScheme

INFINITE INFINITE INFINITE
MEDIUM NOMINAL NOMINAL
ZERO ZERO ZERO
Related Topics
Component Builder Overview of QScheme Builder

Shared objects in Capital Logic and Capital Integrator can reside on multiple designs and can be
modified by multiple users concurrently, including the specification of any attached simulation
models. To ensure the consistency of attached models within a project, restrictions apply as to
where, and by who, model attachments can be created or modified.

February 2016
Attaching a Model to a Shared Object
Related Topics

Models can be attached to shared objects within the Capital suite of applications:
Procedure
1. Models can be attached to shared objects within the Capital suite of applications:
• In Capital Project:
With the project open, select Shared Objects > Shared Devices from the tree menu,
then right-click on the shared device to which you wish to attach a model and select
"Edit". The Edit Shared Pin List dialog will open.
In the section labeled Analysis, either click the "Attach" button to open the Attacher
(see “Attaching Component Models” on page 199) and select the pre-built model to
attach, or click the "Build" button to launch the Component Builder Wizard and
create a new model to attach. Once a model has been attached, the Simulation
Model field will display its name and location.
Alternatively the Associate button in the Analysis panel allows you to specify a
symbol with associated model can also be added to the device. Once associated, the
behavior of the model can be used in any simulations. See “Generate Model in
Capital Symbol” on page 201 and “Associate Symbol” on page 202 for full details.
See the Capital Project help system for more information on creating and editing
shared objects in Capital Project.
• In Capital Logic:
In the Shared Objects browser window, right-click on the shared object to which you
wish to attach a model and select Edit Shared Device. The Edit shared Device
dialog will open. On the Analysis tab, either click the "Attach" button to open the
the Attacher (see “Attaching Component Models” on page 199) and select the pre-
built model to attach, or click the "Build" button to launch the Component Builder
Wizard and create a new model to attach. Once a model has been attached, the
Simulation Model field will display its name and location.
Alternatively the Associate button in the Analysis tab allows you to specify a
symbol with associated model can also be added to the device. Once associated, the
behavior of the model can be used in any simulations. See “Generate Model in
Capital Symbol” on page 201 and “Associate Symbol” on page 202 for full details.

February 2016
See the Capital Logic help system for more information on creating and editing
shared objects in Capital Logic.
2. Right-clicking on an instance of a shared object in a Capital Logic diagram, or in the
Diagram browser window, and selecting Analysis > Attach will open the Attacher in
read-only mode as models cannot be attached directly to instances; you will be able to
view the name and location of any attached model, but you will not be able to make any
changes to the attachment. The Analysis > Build option will be disabled for the same
reason: you cannot build a model for attachment to an instance of a shared object. It is,
however, possible to edit the model attached to an instance by right-clicking on the
instance and selecting Analysis > Edit Model. This will open the attached model in the
Component Model Builder, allowing users with sufficient privileges to edit the model's
structure and behavior.
Note
If right-clicking on an instance of a shared device in a Capital Logic diagram, or in the
Design browser window, the Analysis > Associate Symbol menu item will not be
enabled, as symbols cannot be attached directly to instances. See step 1 above for details.
3. Upon pressing Space Bar and entering Refresh Shared in Capital Logic, any updated
model attachments will be applied to all instances of a shared object within a design,
overwriting any legacy attachments.
Note
If you are working with an old diagram (pre-2006.2) and attempt to run a simulation
without refreshing the shared objects, you may encounter the following message:
Shared Device: "Device Name" has multiple different attachments. Please refresh shared
objects.
This will occur because it was previously possible to attach component models to
instances of shared objects, and without refreshing the shared objects on the design, the
models attached to the shared objects at project level will not have cascaded down to each
instance on the design. This can be rectified by pressing Space Bar and entering ‘Refresh
Shared’ in Capital Logic before running the simulation again.
Related Topics

February 2016
Embedding Hierarchical Components
Embedding Hierarchical Components

Instead of creating the structure for every model employed in a design - often creating identical
structures for duplicated components - it is possible to embed existing models into the model
structure you are creating.
For example, if you are creating a model for a fuse box containing a number of identical fuses,
the component model can be created for a fuse component, which can then be embedded a
number of times - the same model being re-used in each case - until all fuses in the fuse box
component have been modeled.
These hierarchical models - embedded along with all attendant behaviors - can be connected to
the parent structure through connections to parent nodes by regular resistance arcs, and the
properties of the embedded model can be accessed through the behavior of the parent model.
Note
Note that although it is possible to embed a model that contains its own embedded
models, each model can only access the properties and structure of the model embedded
directly within it, that is, access is only available to the next level down in the hierarchy.
Restrictions on Use
Although the implementation of embedded hierarchical component models is highly flexible, a
number of limitations apply when embedding a model with a component model structure:
• The component model to be embedded must contain one or more external nodes.
• A component model cannot be embedded within itself.
• Although it is possible to create a Dependency expression model with an embedded
State machine model, simulations involving the Dependency expression model may take
an excessive amount of time, and the results may feature a greater number of steps than
expected.
Related Topics
Reference an Embedded Object Set Failure Modes for an Embedded Object
To Embed a Hierarchical Model Defining Component Structure
Moving Objects in the Structure Editor Deleting Objects in the Structure Editor
Pin Naming
To Embed a Hierarchical Model

This topic details how to embed hierarchical models.

February 2016
Procedure
1. Create a new component model, see “Creating a new component model” on page 162.
2. With the "Normal Operation" mode selected, the user can now invoke the Structure
Editor window by clicking the "Edit Mode's Structure" button located on the lower-
right-hand side of the window.
An empty Structure Editor window is shown below:
Note
The yellow grid shown is a user definable preference and can be turned on or off via the
View menu.
3. Click the "Insert an embedded component model" button ( ) then move the mouse
pointer over the canvas. The cursor changes to a cross-hair. Left-click at the point at
which you wish to place the embedded model. A file selection dialog is displayed:

February 2016
Note
In the above image, a Connector model has been selected, as this best shows the nature of
the folder structure, but later steps in this process detail the use of a simple lamp model
for simplicity.
Select the model to be embedded by clicking on it (noting that only component models
can be selected). The selected model is displayed in the Location field, and its
properties can be examined by clicking the "Properties..." button. Once the correct
model is selected, click the "Open" button.
Note
If the model you have selected to embed has no external nodes, a warning message will
be displayed, and you will be prevented from embedding the model.
4. A dialog is displayed asking you to provide a name for the model to be embedded:

February 2016
The dialog shows the name of the selected model by default, but this can be overwritten
as required. Once you are satisfied with the name entered for the model, click OK to
proceed.
Note
Entering a new name for the model only overrides the model name for this instance of its
use; the model stored in the database will not be renamed. Note also that all instances of
the same model embedded in a parent model must have unique names.
5. The model is displayed on the canvas as a circle, with the model's name in the center and
all external nodes displayed on the perimeter of the circle:
The embedded model can be repositioned as required. The circular representation of the
model can be rotated by first selecting it, then by scrolling the mouse wheel while
holding down the Ctrl key. If you wish to replace the embedded model with another
model, double-click in the model representation and the file selection dialog will open,
allowing you to select a different model to use; once you have selected a new model to
use and clicked on the "Open" button, the new model will be displayed on the canvas.
6. Once the model has been placed on the canvas, it can be connected to the parent
component model's structure, using arcs to connect the embedded model's external
nodes to terminal nodes (both internal and external) within the structure:

February 2016
7. Multiple instances of the same model can be embedded within a structure as long as
each is given a unique name as it is selected. Multiple types of model can also be
embedded in the same structure:

February 2016
8. Once all required models have been embedded and connected to the parent structure,
close the Structure Editor dialog and save the changes to the model.
It is possible to remove a component model from the Analysis datasource that is
embedded in a parent model. If this occurs, the following errors/warnings will be
encountered:
• If you open the model in the Component Model Builder, a warning will be displayed
to inform you as to which embedded model can no longer be located in the database.
The associated embedded object will be colored red in the Structure Editor and can
only be deleted.

February 2016
Reference an Embedded Object
• If you check the integrity of the model (by selecting Tools > Check Integrity from
the Component Model Builder main menu) the missing model will be noted as a
problem.
• Any attempt to simulate the model will raise an error detailing the missing model.
Related Topics
Reference an Embedded Object Set Failure Modes for an Embedded Object
Embedding Hierarchical Components Defining Component Structure
Pin Naming
Reference an Embedded Object

All properties and behaviours of embedded models can be set/read within the parent model's
behavior using the "embedded" construct. For example:
embedded.myEmbeddedObject
allows you to target all of the functionality available to the model called
"myEmbeddedObject".
This means that the command:
embedded.myEmbeddedObject.arc_1.setResistance(INFINITE);
sets the resistance of the arc named "arc_1" in the embedded object
"myEmbeddedObject" to "Infinite".
Related Topics
To Embed a Hierarchical Model Set Failure Modes for an Embedded Object
Pin Naming
Set Failure Modes for an Embedded Object

Failure modes may not be directly set for an embedded model via the structure. Instead, they
can be applied using one of the following two methods:
• The embedded object can have its failure mode set by referencing it from within the
behavior of the parent object. For example:

February 2016
embedded.myEmbeddedObject.setFailureMode("myFailureMode","<Failure
Text>");
sets the failure mode "myFailureMode" for the embedded object
"myEmbeddedObject". The parameter "<Failure Text>" is used to pass the text to be
displayed in FMEA reports; this parameter must be included, otherwise an error will
be encountered when you attempt to save or run an integrity check on the model.
An example of use for this method would be the modeling of a fuse box, where a
number of fuse models have been embedded within the parent "fuse box" object. The
fuse box would be constructed with a number of failure modes, one each for every
possible combination of embedded fuse failure. Upon setting the failure mode for the
parent object, the behavior entered against the selected failure mode sets the failure
mode for the embedded fuse object or objects required.
• A failure mode can be applied to the arcs connecting the external nodes of the embedded
object to the structure of the parent object.
Related Topics
To Embed a Hierarchical Model Reference an Embedded Object
Pin Naming

Removing the need to maintain complex source code within the body of a component's
behavior, Capital Analysis allows you to create a library of pre-compiled VHDL-AMS models,
which can be referenced within behavior scripts.
To embed a VHDL-AMS model

Note
Ensure that the model you wish to reference has been created and compiled in the
database, and make a note of the model's name. See the section detailing “External Model
Management” on page 281 for more information.
It is possible to reference a model before it has been created, but although the component
model's behavior will be syntactically correct, an error will be generated when you save
the model or perform an integrity check, stating that the referenced model is missing.

February 2016
1. Open the Component Model Builder, either bypressing Space Bar and entering Model
Builder in your Capital Logic application, or right-click on a device within an open
diagram and select Analysis > Build. Create a new component model with an
appropriate structure (see “Creating a new component model” on page 162).
2. Click the "Edit Mode's Behavior" button to open the Dependency Editor.
Note
It is possible to embed VHDL-AMS models within a State Machine, but this section will
use a Dependency Expression model for illustration.
3. In the Dependency Editor window, enter the following statement, or select the statement
from the Commands list on the right of the screen, under Model Objects > self >
Methods:
self.usurp("VHDL","<vhdl model>");
replacing <vhdl model> with the name of the model you wish to reference. For example:
self.usurp("VHDL","myModel");
Note
The name you enter must match that entered against the model in the database, otherwise
a missing model error will be generated when you save the model or perform an integrity
check.
Two other statements can be used to reference the model. These are:
self.usurp("VHDL","<vhdl model name>","<vhdl library>");
and
self.usurp("VHDL", "<vhdl model name>","<vhdl
library>","<architecture>");
Currently, only the "WORK" model library can be referenced, so passing these extra
arguments is unnecessary.
4. Close the Dependency Editor and save the component. If an error is encountered
informing you that the named model is missing, check that the model exists in the
library and that you have entered the model's name in the behavior correctly.
Related Topics
“External Model Management” on page 281
“Defining Component Behavior” on page 172

February 2016
Component Model Templates

Component Model Templates are a type of component model that allows the storage of
behavioral expressions and component properties in a reusable form in the database. Once
created, templates can be associated with component models - the models inheriting the
template’s behavior and properties as the basis for the new model’s construction.
Component Model Templates can only be created as Dependency Expressions; the option to
create a template as a State Machine is not available. It is, however, possible to associate a
template with component models of either type. Any behavior entered against a component
model template will be interpreted before any behavior belonging to a dependent component.
A component model associated to a template has access to the template component’s interfaces
as well as its behavior, although not its structure. Any interfaces created for the template will be
displayed in the Component Interface list along with any interfaces created for the component.
The template interfaces will be positioned at the top of the list and will be grayed-out as they
cannot be edited; if you want to edit any of the template interfaces, you must edit them within
the template model.
When a component with an associated template is exported, it will be handled in the same way
as a component with a QScheme attached or with an Embedded Model: the additional content
will be embedded within the exported component model. The export of such component models
is supported in both encrypted and unencrypted formats (see “Component Model Encryption”
on page 253 for more information.
Note
Any changes made to a template will be inherited by the associated component models. If
you open a component model with an associated template that has been edited since the
model was last opened, a message will be displayed to inform you that the template has
changed; simply click OK to confirm and clear the message.
To create a Component Model template

1. Open the Component Model Builder dialog, either from the Capital Launcher by
selecting Analysis Solutions then Capital SimModel, or by pressing Space Bar and
entering ‘Model Builder’ in your Capital Logic application.
2. Select File > New from the menu. The Create New Component dialog will be displayed.
3. From the Component category drop-down list, select Template, then click OK.
Note
Component Model Templates can only be created as Dependency Expressions; upon
specifying the component model as a template, the State Machines Behavior Modeling
Type option will be disabled.

February 2016
4. The Component Model Builder dialog will change in appearance to offer only those
options applicable to templates:
• The Operating Modes and Component Information areas will be removed from
the dialog.
• A new button will be added to the toolbar allowing you to view or edit the
behavior of the template.
• The Edit > Select Template menu option will be disabled. It is not possible to
associate a template with another template.
• The Tools > Change Behavior Type menu option will be disabled. As discussed
above, it is not possible to create a template with a Behavior Modeling Type of
State Machine.
5. Click on the button to open the Dependency Editor (see “Dependency Expressions”
on page 172)and create a behavior for the template.
6. To add a component interface, click the New button; the Component Interface Property
dialog will be displayed. Refer to “Defining a Component Interface” on page 164 for
more information on how to create an interface.
7. Once the template is complete, select File > Save from the menu. The Save a
Component Model dialog will open, allowing you to specify a name for the new
template and a location within the component database in which to save it.
To create a Template from an existing Component

Model
Caution
It is possible to change the category of an existing component model to Template, but this
will result in the deletion of the following areas of the model’s content: Structures, State
Machines and Failure Modes.
1. With the Component Model Builder dialog displayed, select File > Open from the
menu.
2. The Open a component model dialog will be displayed. Browse to the component model
you wish to use as a template, click once to select it, then click Open. The model will be
displayed in the Component Model Builder.
3. Select Tools > Change Category from the menu. A message will be displayed asking
you to confirm the change; click on Yes to proceed.
4. The Change category dialog will be displayed. From the Component category drop-
down list, select Template.

February 2016
5. A message will be displayed informing you that the component model’s structure, state
machines and failure modes will be deleted (if any have been created). Click on OK to
confirm the message and continue.
Note
It is possible to change a template’s component category to one of the other options,
converting the template into a standard component model. If you do this, and the template
is already associated with one or more component models, a message will be displayed to
inform you of any dependencies, and you will be given the option to cancel or proceed
with the change.
6. To create, view or edit the template’s behavior, click the button to open the
Dependency Editor.
7. To add a component interface, click the New button; the Component Interface Property
dialog will be displayed. Refer to “Defining a Component Interface” on page 164 for
more information on how to create an interface. Existing component interfaces can be
edited or deleted by first clicking on the interface to select it, then clicking the Edit or
Delete buttons as appropriate.
8. Once the template is complete, select File > Save from the menu. The Save a
Component Model dialog will open, allowing you to specify a name for the new
template and a location within the component database in which to save it.
To delete a Template
1. Launch the Object Manager by pressing Space Bar and entering Object Manager in your
Capital Logic application.
2. Navigate to the component model template you wish to delete, then either:
• Right-click on the model and select Delete
or
• Select Edit > Delete from the menu
or
• Press the Delete key on your keyboard
3. A message will be displayed asking you to confirm the deletion; click Yes to proceed or
No to abort the process.

February 2016
Note
If the template you have chosen to delete is associated with any component models, a
warning will be displayed to inform you, giving you the option to proceed or cancel the
deletion. If you open a component model that was previously associated with a template
that has since been deleted, a message will be displayed to inform you, but you won’t be
prevented from proceeding; once you have confirmed the message, the component model
will open, but without any Dependency behavior or component interfaces previously
inherited from the template. If you perform an integrity check on the model, a message
will be displayed to inform you that the template can no longer be found. If you attempt
to run a simulation using the component model, an appropriate error message will be
displayed.
To associate a Template with a Component Model

Note
It is not possible to associate more than one template with a component model.
1. With the Component Model Builder dialog displayed, and the component model with
which you wish to associate a template open, select Edit > Select Template from the
menu.
2. The Template dialog will be displayed.
3. Click on the button. The Select Template dialog will open; browse to the template
you wish to use, select it, then click the Open button.
Note
The Select Template dialog will only display component models with a Component
category of Template to aid in selecting the correct template.
4. The Template dialog will now display the path to the selected template.
Note
Clicking the button allows you to launch the Component Model Builder and edit the
selected template before associating it. Clicking the button will clear the path from the
field; see To delete the association between a Template and a Component Model, below,
for more information.
5. Click the OK button; you will be returned to the Component Model Builder. Any
component interfaces entered in the template will be displayed, grayed-out, at the top of
the Component Interface list; any behavior entered in the template will be available to
view by first clicking the Edit Mode’s Behavior button, then in either the Dependency

February 2016
Editor or the State Builder, clicking on the Show the template behavior button ( ) to
launch the Template Behavior dialog.
Any behavior defined for the template will be interpreted before the behavior entered
belonging to the dependent component model.
6. With the template associated, select File > Save to save the component model to the
component database.
Note
If you perform an integrity check on the component and a SAINT function is found to be
missing in either the template or component model behavior, a message will be displayed
to inform you of the problem. If you save and close the component model without
performing the integrity check, the same message will be displayed the next time you
open the model in the Component Model Builder. The same check will be performed if
you attempt to run a simulation using the model, in which case an appropriate error
message will be displayed.
The Template Behavior Dialog

This dialog, launched from with the Dependency Editor or State Builder by clicking on the
Show template behavior button ( ), displays any behavior assigned to a template associated
with a component model. The behavior cannot be edited in any way: it is displayed only for
reference.
Refer to “Component Model Templates” on page 189 for more information on how template
behaviors are created and interpreted.
To delete the association between a Template and a

Component Model
1. With the Component Model Builder dialog displayed, and the component model from
which you wish to delete a template association open, select Edit > Select Template
from the menu.
2. The Template dialog will be displayed, with the path to the currently selected template
displayed in the field.
3. Click the button; the path to the template will be removed from the field.
4. Click OK to confirm the deletion and close the Template dialog.
5. You will be returned to the Component Model Builder dialog; any component interfaces
or behaviors previously inherited from the deleted template will now no longer be
available.

February 2016
Component Builder Wizard
Related Topics
“Component Builder” on page 160
“Selecting a Component Category” on page 163
“Defining a Component Interface” on page 164
“Defining Component Behavior” on page 172

The Component Builder Wizard will help you create component models quickly and efficiently.
It will automatically pick up information from an ECAD tool symbol, thus saving you time and
effort typing it in.
Note
After you create a model using the Component Builder Wizard, it is automatically
attached to the device (in the Attaching Component Models dialog) and your pins will be
mapped.
The description of the Component Builder Wizard assumes that you are familiar with the
Component Model Builder tool.
The Component Builder Wizard is started by selecting the schematic symbol for which you
want to build a model, pressing Space Bar and entering Buld.
The first screen is an introduction screen describing the main stages involved in completing the
wizard. It also has a tick box on it which allows you to choose wether you want information
panes to be shown as you go through the wizard. In this description of the wizard the
information panes will not be shown. If you are a new user we recommend that you leave the
information panes switched on. Click the Next buttons to proceed to the next step in the wizard
and Back buttons to return to a previous step.
The main wizard stages are:
• Basic Information - Here you define the components category and behavior modeling
type.
• Structural Information - Where you must define the component's nodes and arcs, and
their layout.
• Failure Modes - Where you select the standard or user-defined failure modes for the
component.

February 2016
• Properties (component inputs/outputs) - Where you define the components interface

properties.
Basic Information
In the second step of the Component Builder Wizard you must select the component model's
Category and Behavior Modeling Type. This is step is the same as if you had just selected File
> New from within the Component Model Builder tool.
Structural Information
Next you must start to describe the model's structure by defining your model's nodes. The
wizard will automatically pick up the ECAD pin names and create external nodes with the same
names. Depending on what you want to do you can change the node's names and create other
internal and external nodes as you wish.
The first column in the table shows the ECAD pin names that the wizard has picked up. The
second column shows the names of the nodes that will be created for the model. You can
rename and create new nodes by typing in the second column. The External column has tick
boxes to allow you to make a component model's node internal or external. Note that ECAD
pins have to be external nodes. The Map pins -> nodes button will map the ECAD pin names to
the node names.
It is also possible to group sets of nodes. For example, you could group all the input and output
pins of you model together, this would make it easy to describe the structure's layout and the
connectivity of the nodes further on in the wizard. To group some nodes first highlight a set of
nodes and then click the Group button. The wizard will ask you to name the group of nodes.
Once you have defined the nodes in your component model, you must then describe their
physical layout or formation.
The next step allows you to choose the shape of the node's structure to be laid out in the
structure editor.
• Star - This layout lets you select one node to be the center node and then puts the
remaining nodes around the center node in the shape of a star.
• Column - This layout lines up the nodes in columns. You may have one or two columns
which may be set out vertical or horizontal.
• Rectangle - This layout will line up the nodes in a rectangular shape.
• User - This layout option will allow you to place the nodes anywhere you want using the
mouse.
Depending on the option you choose for the structure's formation will change the screen you
will see next. If you choose Star, Column or User then the next screen you see will allow you to
organize the chosen structure shape.

February 2016
You can also choose to have the layout organized according to groups of nodes. This option is
only available if you have assigned some of the pins to groups.
The next step depends on the shape of the node’s structure. If you chose the star formation, you
must choose which node is to be at the center of the star. If you chose the Column structure
formation then you will have decide how many columns you want and whether you want them
laid out vertically or horizontally. The Rectangle formation does not have any extra settings and
the User layout option will take you to a formation editor window where you can move the
nodes to the positions you want by using the mouse.
You must describe the models connectivity. Depending on which options you select will change
the next wizard screen you will see. The Connectivity options are:
• No Connectivity - this will leave you model with no internal connections (arcs).
• As defined by formation rule - this will create connections according to the layout of
the nodes.
• All nodes are connected to all other nodes - this will create a connection from every
node to every other node.
• All nodes are connected to a specified node - this will create a connection from one
particular node to every other node.
• User defined - this option will allow you to define the connections yourself.
You must specify an arc default resistance for some of the connectivity options. Depending on
which option you chose, you may have to specify various connectivity settings in the next step
of the wizard. You can also have the nodes connected in accordance with their groups. This
option is only available if you have assigned some of the pins to groups.
If you used the As defined by formation rule connectivity option then the connections will be
made according to the node's layout you have selected previously. If you have chosen:
• Star - then the central node will be connected to each node surrounding it.
• Column - then each node in the first column will be connected to the adjacent node in
the next column.
• Rectangle - then every node will be connected to every other node.
• User - then you will have to define the connections yourself.
Failure Modes (Component Builder Tool)

In the Standard Failure Modes window, you can create failure modes for your component
model. You can select to use particular standard failure modes by using the tick boxes, each
standard failure mode will be applied to all the nodes in the model. The standard failure modes
are:

February 2016
• Short to battery - this will directly connect a node to the battery's positive terminal as
specified in the subsystem editor.
• Short to ground - this will directly connect a node to the battery's ground terminal as
specified in the subsystem editor.
• Open Circuit - this will allow you to make one or more of the model's arcs fail open
circuit.
• Bent Pin - this failure will short every node to every other individual node in the models
structure.
• Foreign Object Detection - this failure will short every node to every other
combination of nodes.
• Pin lifted - this failure will remove a node, effectively disconnecting it from any arcs.
If you tick the Create User Defined failure modes... tick box you will see another step in the
wizard which will allow you to create your own failure modes for this component model.
Properties (component inputs/outputs)

In the Component Interface window, you create the component model's interface. You can
add all the normal internal, external, subsystem, input and output properties by clicking the New
button. You can also edit and delete Component Interface properties by highlighting a property
and then clicking the appropriate button.
If you tick the I don't want to add any more detail, skip to end. tick box the wizard will take
you straight to the Summary step when you click next.
Completing the Wizard

The Quantization schemes window allows you to define the Resistance, Voltage and Current
QSchemes which will allow Spice simulations of the model. Use the Select a new Object
buttons to select previously created QSchemes and the Create a new Object buttons to create
new QSchemes.
In the Model description window, you may enter a description of the model.
This Summary window shows you a summary of the model you have created. Select the tabs to
view the different parts of the model. If any of the details of the model are incorrect click the
Back buttons until you reach the appropriate screen and change the settings.
The Save Object window of the wizard asks you to save it. Click the Browse button to choose a
directory and name for the component model.

February 2016
Component Library - Component Models Provided
Once your model is saved you will be asked if you would like to open it in the Component
Model Builder. Select Yes to use the Component Model Builder to describe the models
behavior.
Related Topics
“Component Builder” on page 160
Component Library - Component Models

Provided
The Analysis standard library includes various component models.
• Connectors: splices and connector devices.
• ECUs: electronic control units, microcontrollers and similar devices.
• ElectroHydraulic: contains electrohydraulic devices.
• ElectroMechanical: contains components like relays and solenoids.
• ElectroPneumatic: contains electropneumatic devices.
• Loads: motors, lamps, speakers and other devices are held here.
• Logic: digital logic devices, for example, and gates.
• Modules: contains various modules (components that are made from other
components), for example, a radio.
• Protection: fuses and circuit breakers are stored here.
• Semiconductors: discrete semiconductor devices are stored here.
• Sensors: contains various sensor components.
• Supply: contains batteries, chassis components, supply and ground rails.
• Switches: various types of switches are stored here.
• Wires: wire component models are stored here.
Important Recommendations
1. It is recommended that you do not modify any objects in the /Capital folder. This folder
is distributed with an Administrator lock already present.
2. It is recommended that you create a folder for shared objects. This folder should start
with your company name. See “Shared Object Component Models” on page 177 for
more information on attaching component models to shared objects.
3. Projects that more than one user is working on should have their own folders.

February 2016
4. Individual users should have their own folders.
Related Topics
Attaching Component Models Creating a new component model

This topic explains how to attach component models.
Procedure
1. In the design tool, select (or highlight) the component in the schematic to which you
want to attach the component model. In Capital Symbol, you can skip this step but you
must ensure that the symbol is open in Capital Symbol.
2. Press Space Bar and enter Attach. This opens the Attacher dialog. This dialog
comprises a number of tabs that control differing options
3. The top of the Attacher dialog allows you to select whether you attach your model at the
Symbol or Instance level. If you attach at the Symbol level, all the components in the
schematic with the same symbol will have the same model attached to them. If you
attach at the Instance level, the model is attached to only the component that you
highlighted before selecting to attach the model.
4. The model section in this window displays the component model that the simulation
engine will use for the selected component in the design tool.
Note
If you created a model using the Component Builder Wizard, it is automatically attached
to the device and your pins will be mapped.
5. Select whether you want to attach the component model to the instance or to the symbol
of the component. If a component model is already attached to the instance or the
symbol of the selected component, the model (or mapping) section of the window will
show the path to the attached component model (or mapping).
6. Select the component model that you want to attach by clicking the Select a new Object
button in the Model section. This will open the Select a new Object chooser.
Alternatively, you may also press Make a new Object button to create a new
component model from scratch. This will open the Component Builder.
7. When you have selected the component model you want, press the OPEN button. The
Attacher dialog will now show the selected component model. A process will have run
to automatically map the pins on the selected model with the pins on the schematic

February 2016
object according to the mapping rules, (see “Pin Naming” on page 172). Message text
on the Models Panel will display the results of the automatic mapping as follows:
• All ECAD terminals have been successfully mapped - this displays is when
every ECAD terminal maps, either uniquely or as a duplicate to the component
model.
• Only partial mapping of ECAD terminals possible, please check Terminal
Mapping panel - this displays is when some ECAD terminals are not mapped to
anything on the component model.
• No ECAD terminals can be automatically mapped, please check Terminal
Mapping panel - this displays when no ECAD terminals can be mapped to the
selected model.
8. To view the mappings and investigate any un-successful mappings, click the Terminal
Mapping tab. Mappings will be displayed, in the Qualitative Terminal column, as
follows:
• Automatic in black text - denotes a successful mapping between the ECAD and
the model pin.
• Automatic in red text - denotes an un-successful mapping between the ECAD
and the model pin.
• No Terminal - denotes that there is no pin on the ECAD device.
• Actual pin names - will display where previous manual mapping has been
performed.
Note
Hovering the mouse over any of the mapping entries in the Qualitative Terminal column,
as above, will display a tooltip with the mapping details.
Mapping entries can be changed by clicking in the required cell in the Qualitative
Terminal column, and selecting a different value from the combo box that displays.
An ECAD component pin can remain unattached only if that pin is not connected to
another component i.e. it is floating. See “Pin Naming” on page 172 for more
information.
9. To remove an attached model, click the Forget this Object button in the model
section of the attacher window. To remove an attached mapping, click the Forget this
Object in the mapping section of the attacher window.
To view the component model that is attached, click the Show this Object button
in the model section of the Component Model tab. To view the component
mapping that is attached, click the Show this Object in the mapping section of the
Component Model tab.

February 2016
Generate Model in Capital Symbol
10. The Promotion tab can be used to override either interface property promotion or
failure mode promotion on a per-model basis. Click the Promotion icon ( ) to assign
individual promotion behavior to a model. Note - the icon changes according to the
setting selected. For further information see “Overriding Interface Property or Failure
Mode Promotion” on page 204.
11. Click the OK button to apply the attachment.
Related Topics
Generate Model in Capital Symbol Associate Symbol
Generate Model in Capital Symbol

Composite Symbols, within Capital Symbol, can dynamically generate analysis models based
on the internal blocks and internal connectivity.
These dynamic models can be saved directly into the Analysis Object Manager for later reuse
and association to devices. Alternatively, the Composite Symbol itself can be associated to
devices within the schematic (thus maintaining a link to the dynamic model via the composite
symbol). This topic describes how the dynamic model can be saved into the Analysis Object
Manager, from within Capital Symbol.
Note
These symbols can be associated with devices in Capital and the inherited Analysis
model used in dynamic simulations.
Prerequisites
• Composite symbol with internal connectivity.
Procedure
1. Open the composite symbol in Capital Symbol.
2. Press Space Bar and enter Attach.
Results
• The Attacher dialog displays.
• The Model Panel displays the name of the Model that has been generated.
• Select the Show this Object button to display the Component Model Builder dialog
from where the Structure and Behavior of the model can be checked and defined

February 2016
Associate Symbol
Related Topics
Attaching Component Models Associate Symbol
Internal blocks and internal connectivity
Associate Symbol
Analysis models can be defined against a symbol. This topic describes how such symbols can
be associated with devices in Capital Logic and how the inherited Analysis model used in
dynamic simulations.
Using models in this way removes the need for you to manually generate models.
Prerequisites
• Composite symbol with internal connectivity and simulation model attached exists, see
“Generate Model in Capital Symbol” on page 201.
Procedure
1. Right-click on the device in question and select the Analysis > Associate Symbol menu
item.
2. The Associate Symbol dialog displays. Select symbol required and press OK.
Results
• The symbol and its model are now associated with the device.
Note
The association can be checked by checking the device property Analysis Symbol which
displays the name of the currently associated symbol.
• The model that is attached to the associated symbol will be used in any simulations that
are run.
Related Topics
Attaching Component Models Generate Model in Capital Symbol
Attaching Functions
There are three other active tabs in the component model attacher. One of these is for attaching
Functions. Output functions are attached to output devices, control functions are attached to
input devices.

February 2016
Attaching Functions
Attaching Output Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

Attaching Control Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Attaching Output Functions

To attach an output function, follow the steps below.
Procedure
1. Select an output device, on the schematic
2. Open the attacher as described above.
3. Select the 'Functions' tab.
4. Navigate the project in the left-hand panel, to find the desired output function.
5. In the right-hand panel, select the output condition that is valid for this output function.
(This will depend on the component model attached).
Note
When attaching an encrypted component model, only External and Parameter type
properties will be available for selection. See “Component Model Encryption” on
page 253 for more information on working with encrypted models.
6. Click 'OK'.
Attaching Control Functions

To attach a control function, follow the steps below.
Procedure
1. Select an input device, on the schematic
2. Open the attacher as described above.
3. Select the 'Functions' tab.
4. Navigate the project in the left-hand panel, to find the desired control function.
5. In the right-hand panel, select the input condition that is valid for this control function.
(This will depend on the component model attached).
Note
When attaching an encrypted component model, only External and Parameter type
properties will be available for selection. See “Component Model Encryption” on
page 253 for more information on working with encrypted models.

February 2016
Attaching Functions
6. Click 'OK'.
Specifying Power Pins

The tab labelled Power in the attacher is used for setting power and ground pins. These are used
for determining what nodes are to used when short to power and short to ground failures are
applied. Also the ground node is used as a reference for voltage calculation. To set the pins
follow the steps below:
Short to Battery
Set a short to battery component.
1. Select the component that will be used for such failures, this will normally be the power
supply.
2. Open the attacher, select the power tab.
3. Check the 'Use a node on this component', in the short to battery failures group.
4. Select the node from the drop-down list that will now be active.
Short to Ground
Set a short to ground component.
1. Select the component that will be used for such failures, this will normally be the power
supply.
2. Open the attacher, select the power tab.
3. Check the 'Use a node on this component', in the short to ground failures group.
4. Select the node from the drop-down list that will now be active.
Click on OK in the attacher when power pins have been set up.
Related Topics
Component Builder
Overriding Interface Property or Failure Mode

Promotion
The Promotion tab is used to override either interface property promotion or failure mode
promotion on a per-model basis. This functionality is available from both the Attacher dialog,
and when setting a model’s promotion status during its creation in Capital Symbol.

February 2016
Component Builder Dialogs

Procedure
embedded model.
3. Click OK.
Related Topics
Component Builder

The following topic details the component builder dialogs.
Associate Symbol Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Edit Comment Dialog Box (Component Builder) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Failure Mode Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Fuse Rating Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
New Component Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Description Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Associate Symbol Help

What do you need help with?
• The Associate Symbol Dialog Box fields

February 2016
• Associate Symbol

February 2016
Associate Symbol Dialog Box
Associate Symbol Dialog Box

To access: Press Space Bar and enter Associate Symbol in Capital Logic.
Also accessd from the Associate button on the Capital Project > Edit Shared Pinlist dialog
Use this dialog box to directly map symbols with attached models to devices.
See “Associate Symbol” on page 202..
Fields
Table 12-1. Associate Symbol Dialog Box Contents
Field Description
Treeview Displays all the symbols available for selection
Panel
Preview Displays a preview of the symbol that is currently selected in
Panel the treeview
Related Topics
Associate Symbol

February 2016
Edit Comment Dialog Box (Component Builder)
Edit Comment Dialog Box (Component Builder)

To access: Accessed when using the Component Builder.
This dialog is used to create and edit a comment in the structure editor.
Fields
Table 12-2. Edit Comment Dialog Box(Component Builder) Contents
Field Description
OK Select to accept the text entered
Cancel Select to reject the text entered
Related Topics
Defining Component Structure Component Builder

February 2016
Failure Mode Dialog Box
Failure Mode Dialog Box

This dialog allows a failure mode on a component model to the created or modified.
Enter the name of the failure mode in the text box. Each failure mode should be assigned an
occurrence rating indicating the likelihood of the failure occurring. The two radio buttons can
be used it indicate how the behavior of the failure mode is implemented.
Fields
Table 12-3. Failure Mode Dialog Box Contents
Field Description
Has no Select to indicate that the failure mode does not have any
behavior behavior at all.
Has own Select to indicate that a new behavior for the failure mode
behavior will be implemented later.
Uses normal Select to indicate that the behavior used for normal operation
operation will be used.
behavior
Related Topics
Component Builder Defining Failure Modes

February 2016
Fuse Rating Dialog Box
Fuse Rating Dialog Box

This dialog allows the fuse rating of a component to be set and changed. This dialog is only
available for those component models whose category is fuse.
Fields
Table 12-4. Fuse Rating Dialog Box Contents
Field Description
Fuse Rating Enter the fuse rating value in the box on the left.
Related Topics
Component Builder

February 2016
New Component Dialog
New Component Dialog

This dialog is used to define the specification of a new component model.
Characteristics
There are 8 different categories for Capital Analysis component models by default. They are:
• other (default) - most components will be in this category.

• positive - a single node positive component (structure will be created automatically).
• negative - a single node negative component (structure will be created automatically).
• connections - for wire components (structure will be created automatically).
• fuses - create a fuse component with a fuse rating (structure will be created
automatically).
• diodes - create a diode component (structure will be created automatically).
• chassis - a single node chassis component (structure will be created automatically).
• template - a special type of component that allows the re-use of Dependency-based
behaviors and component interfaces; see “Component Model Templates” on page 189
for more information.
Further categories can be defined from the Options dialog, (Edit > Options).
Related Topics
Component Builder

February 2016
Description Editor
Description Editor
The Description Editor tool allows a more detailed description of the component model to be
stored.
You can apply cut, copy and paste operations using Edit menu. You can insert the current time
stamp from the Tools menu.
Fields
Table 12-5. Description Editor
Field Description
Text Panel Enter the text into the white text area and click the File > Exit
menu when finished.
Related Topics
Component Builder
Component Builder Menus

The Component Builder window has 4 menus on its menu bar: File, Edit, Tools and Help.
File Menu
There are 9 options on the Component Builder File menu. They are as follows:
• New: Open a blank Component Builder window to allowing a new component model to
be defined.
• Open...: Open an existing Capital Analysis component model, this will invoke the
Open/Save Object Dialog.
• Save: Save an edited Capital Analysis component model to the database using the same
name.
• Save As...: Save an Capital Analysis component model to the database under a different
name. This will invoke the Open/Save Object Dialog.
• Print: Prints all the information about the component model e.g. General Component
Information and Operating Modes.
• Print Preview...: Opens the Print Preview... window which shows you what the printer
will print and allows you to change the page format and printer settings.
• Import...: Import a component model to the database from an external source (see
“System Import/Export” on page 327).

February 2016
Component Builder Related Menus
• Export...: Export an Capital Analysis component model from the database (see “System
Import/Export” on page 327).
• Exit: Exit the Component Builder tool.
Edit Menu
The Component Builder Edit menu has 7 options which are:
• Fuse Values: Allows the use rating to be set. Available only for component models of
type fuse.
• Quantization Bands: Opens the dialog which allows you to select the Quantization
Bands for Spice simulation of the component model.
• Unlock Behavior: This option is not available with this version of Capital Analysis.
• Delete Behavior: Deletes the behavior of the highlighted operating mode.
• Select Template: Opens the Template dialog, allowing you to specify a template model
to associate with the component model.
• Description: Edits the detailed descriptions of the component model.
• Options...: Gives the user access to the Capital Analysis user definable options. See
Tool Menu
• Check Integrity: This checks that the expression and state machines used to build the
component are valid.
Related Topics
Component Builder

There are several different windows with menus used when creating an Capital Analysis
component model. They are the Component Builder window, the Structure Editor window and
the Dependency Editor window. The menus for these 3 windows are covered in these sections:
Component Builder Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Structure Editor Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

February 2016
Structure Editor Menus

The menu bar of the Structure Editor window has 5 menus, which are: File, Edit, View, Draw
and Help.
File Menu
The File menu for the Structure Editor window only has 3 options listed:
• Print: Prints the component models structure information.

• Print Preview...: Allows you to view the page before it is printed and change page
layout and printer settings.
• Export Image: Allows the image of the structure to be exported and saved to the file
system
• Exit: Closes the Structure Editor window and returns to the Component Builder
window.
Edit Menu
The Edit menu of the Structure Editor window has 5 options. They are:
• Undo: Undoes the last edit.

• Redo: Redoes the last edit after it has been undone.
• Edit Object: Invokes a dialog allowing the name of a node or resistance to be changed.
In the case of a resistance the type of resistance can also be changed.
• Delete: Deletes selected objects from the structure.
• Cut / Copy / Paste:For cutting, copying and pasting elements of the structure.
• Options...: Gives the user access to the Capital Analysis user definable options. See
View Menu
The view menu of the Structure Editor window has 9 menu options, which are:
• Show Names: Should names of nodes and arcs be displayed or hidden.

• Show Comments: Should comments be displayed or hidden.
• Show Grid: Should the grid onto which a structure can be drawn be on or off.
• Grid Settings...: Opens an option dialog to adjust the grid size.
• Zoom In: Zooms in on the structure. This option is also available as a tool button.

February 2016
• Zoom Out: Zooms out from the structure. This option is also available as a tool button.
• Zoom To Fit: Sets the zoom to fit everything on the screen.
• Reset Zoom: Reset the zoom to its default.
• Refresh Display: Refresh the display area.
Draw Menu
The Draw menu of the Structure Editor window consists of 9 options all of which are available
from the speed bar located on the left hand side of the Structure Editor window. The options are:
• Select Objects: Changes the cursor to a pointer to allow selection of object .

• Draw Node: Changes the cursor to crosshair and allows the user to draw a node .
• Draw Resistance: Changes the cursor to crosshair and allows the user to draw a
resistance .
• Draw Input: Changes the cursor to crosshair and allows the user to draw an Input node
.
• Draw Output: Changes the cursor to crosshair and allows the user to draw an Output
node .
• Draw Positive Node: Changes the cursor to crosshair and allows the user to draw a
Positive node .
• Draw Negative Node: Changes the cursor to crosshair and allows the user to draw a
Negative node .
• Draw Chassis Node: Changes the cursor to crosshair and allows the user to draw a
Chassis node .
• Draw Comment: Draw a comment text area.
Related Topics
Component Builder Defining Component Structure
Dependency Editor Menus

The Dependency Editor window has only 2 menus on the menu bar, which are: File and Help
File Menu
• Print: Prints the dependency expression information.
• Print Preview: Displays the Print Preview... window, which shows you what will be
sent to the printer, and allows you to change the page format and printer settings.

February 2016
• Close: Exit the Dependency Editor window and return to the Component Builder
window.
Related Topics
Component Builder

February 2016
Chapter 13
State Builder
When a new Capital Analysis component model is created by using the Component Builder
tool, the engineer has to decide which method will be used to model the components behavior.
If the option to use "State Machines" is selected, when the engineer clicks the "Edit Mode's
Behavior" button the State Builder tool will be invoked allowing the engineer to draw state
charts to implement the behavior of components.
Overview of State Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
State Builder Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Adding a New State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Adding an Event. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Adding a Concurrency Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Import and Export State Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Choose Grid Settings Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Edit Comment Dialog (State Builder) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Edit Event Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Structure Error Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Overview of State Builder

The State Builder has two tool bars.
The main toolbar has the following buttons:
- creates a new state machine. This option is not required when state machines are
embedded with component models.
- opens a new state machine. This option is not required when state machines are
embedded with component models.
- this button saves the state machine.
- this cuts the selected item
- this copies the selected item
- this pastes the selected item
- this deletes the selected item

February 2016
State Builder
State Builder Menus
- this button undoes the last operation.

- this button redoes the last operation.
- this button will zoom into the state machine.
- this button will zoom out of the state machine.
- the button will check the integrity of the state machine. Errors will be raised if
there are issues with the structure of the state machine or syntax errors in the language.
The drawing toolbar has the following options:
- this button will change the drawing mode to selection. This allows objects to be
selected, edited and resized.
- this button will change the drawing mode to states. This allows new states to be
drawn in the state machine.
- this button will change the drawing mode to groups. This allows new concurrency
groups to be drawn in the state machine.
- this button will change the drawing mode to events. This allows new events to be
drawn in the state machine.
- this button will change the drawing mode to loop events. This allows new loop
events to be drawn in the state machine.
- this button will change the drawing mode to default events. This allows new default
- this button will change the drawing mode to exit events. This allows new exit
- this button will change the drawing mode to comments. This allows comment
objects to be drawn in the state machine.
Related Topics
Overview of Simulator Tool Adding a New State
Adding an Event Adding a Concurrency Group
Import and Export State Machines State Builder Menus
State Builder Menus

The State Builder window has 6 menus: File, Edit, View, Draw, Tools and Help.

February 2016
State Builder
State Builder Menus
File Menu
• New Window: This option opens a new state builder window allowing the user to view
or develop more than one state machine at the same time.
• New: Open a new (blank) State chart. The State Builder tool can be used independently
from the rest of Capital Analysis if desired. This option is also available on a tool button
.
• Open...: Open an existing State chart. This option is also available on a tool button .
This will invoke a chooser dialog (see “Open/Save Object Dialog” on page 265).
• Close: Close the current state chart leaving the State Builder tool open.
• Save: Save the changed version of a state chart. This option is also available on a tool
button .
• Save As...: Save the changed version of a state chart with a new name. This will invoke
a chooser dialog (see “Open/Save Object Dialog” on page 265).
• Print: Prints the statemachine information.
• Print Preview...: Opens the Print Preview... window which
• Import...: Import a state chart into the State Builder tool from either SQL export (from
another Capital Analysis database) format or from StateMate. See “Import and Export
State Machines” on page 226.
• Export...: Export a state chart from the State Builder tool to either SQL Export or EPS
format (for printing). See “Import and Export State Machines” on page 226.
• Exit: Exit the State Builder tool.
Edit Menu
The State Builder edit menu is designed to allow the easy editing of state charts within the State
Builder tool. The most common used edit features are available as tool buttons on the State
Builder tool bar.
• Undo: Undo last edit of the state chart. This option is also available on a tool button .
• Redo: Redo the previous edit to the state chart following the undo action. This option is
also available on a tool button .
• Cut: Remove selected object from the state chart and place it on the clipboard. This
option is also available on a tool button .
• Copy: Copy the selected object to the clipboard. This option is also available on a tool
button .
• Paste: Paste the contents of the clip board to the state chart. This option is also available
on a tool button .

February 2016
State Builder
State Builder Menus
• Select all: Select the entire state chart.

• Edit Object...: Invoke the edit dialog for the selected object to either rename the object
or change its properties.
• Delete: Delete the selected object from the state chart. This option is also available on a
tool button .
• Options: Access the Capital Analysis user definable option. See “Edit Options Dialog”
on page 269 for more details.
View Menu
The view menu allows the user to set what information will be displayed on the state chart and
how it will be presented. The same information is still required if the state chart is to be used in
the Capital Analysis system, but some complex state charts might become difficult to read with
all the information visible. By using this menu the user can select which information to display
and which to keep hidden.
• State Attributes: This menu option gives access to 2 options each with a tick box.
o Show Names - should the state names be displayed?
o Show Actions - should the state actions be displayed?
• Event Attributes: This menu option gives access to 3 options each with a tick box.
o Show Names - should the event names be displayed?
o Show Conditions - should the event conditions be displayed?
o Show Actions - should the event actions be displayed?
Tick the box to display the corresponding attribute
• Concurrency Attributes, show names - should the concurrency names be displayed?
• Show Comments: Select the tick box to display any comments entered on the state
chart.
• Show Grid: Select the tick box to display a grid on which the state chart can be drawn.
This enables the user to draw state charts that are easier to read.
• Grid Settings...: Selecting this menu option invokes the Choose Grid Settings Dialog,
allowing the user to set the width and height of the grid lines used in the State Builder
tool.
• Zoom In: Zooms in on the state chart. This option is also available on a tool button .
• Zoom Out: Zooms out showing more of the state chart. This option is also available on
a tool button .

February 2016
State Builder
State Builder Menus
• Reset Zoom: Resets the state chart to the original size before the zoom in/zoom out
features were used.
• Zoom To Fit: Resizes the state chart to the maximum size possible within the size of the
window. This option should be used when the window itself has been resized.
• Refresh Display: Re-draws the state chart.
Draw Menu
Each of the options listed on the Draw menu are also available as tool buttons on the speed bar
located down the left hand side of the State Builder window.
• Select Objects: Allows user to click on objects to select and edit them.
• Draw State: Allows user to draw a new state (see “Adding a New State” on
page 222)
• Draw Concurrency: Allows user to define concurrency groups (see “Adding a
Concurrency Group” on page 225).
• Draw Normal Event: Add a normal event to the state chart (see “Adding an Event”
on page 223).
• Draw Event Loop: Add a loop event to the state chart. (see “Adding an Event” on
page 223).
• Draw Default Event: Add a default event to the state chart (see “Adding an Event”
on page 223).
• Draw Exit Event: Add an exit event to the state chart (see “Adding an Event” on
page 223).
• Draw Comment: Add a comment to the state chart (see “Edit Comment Dialog
(State Builder)” on page 229).
Tools Menu
The State Builder Tools menu gives access to 3 tools used when creating state charts.
• Orthogonalize Events: Lines up all events used in the state chart both vertically and
horizontally resulting in the state chart being easier to read.
• Check Integrity: Checks the integrity of the state chart including all events being
connected at both ends, all events having different firing conditions and ensuring that all
states can be reached.
• Export Image: Exports and image of the state chart to the file system as a .png.

February 2016
State Builder
Adding a New State
Related Topics
Overview of Simulator Tool Adding a New State
Import and Export State Machines
Adding a New State

When a new state chart is created, by default it contains a single state called "State1". Each
additional state that is introduced is assigned the next available number. For example State 2,
State 3, etc.
To add a new state first select the "Add State" button from the speed bar located on the left
hand side of the State Builder window. Now move the cursor onto the canvas, notice that the
cursor changes to a crosshair. Move the cursor to the location where you want to draw the new
state, then hold down the left mouse button and drag the mouse. When you are happy with the
size of the box release the mouse button to create the new state. If the new state is drawn so that
it is on top of another state it will appear in a lighter shade. This indicates to the engineer that
the new state is lower down in the hierarchy.
Defining State Properties

When a new state is drawn with autoedit turned on, the Edit State Dialog will appear. This
allows the engineer to rename the state and define its properties straight away. If the engineer
chooses to perform this task later, clicking the "OK" button will accept the default name and
allow the engineer to continue.
If autoedit is turned off or the engineer wishes to return later to edit the state properties, the
same dialog can be invoked by double clicking on the relevant state.
Moving and Resizing States

To move a state, first select it by clicking on it. The selected state will be highlighted with a
series of handles located around the edges. Position the cursor over the selected state, click and
hold down the left mouse button and drag the mouse to move it. When it is in the desired
location release the mouse button. To resize a state, again highlight it by clicking on it. The
same handles will appear around its edges. Move the cursor over one of the handles then click
and hold down the left mouse button. Drag the mouse to resize the state and then release the
button. Which handle is selected will determine how the state can be resized. By selecting a
corner handle both the height and width of the state can be resized at the same time.

February 2016
State Builder
Adding an Event
Hiding States
It is possible to hide the details of any internal states and events that a parent state contains. This
can make the state chart clearer and easier to understand if detail is removed. In order to do this
right click in the state that you wish to hide the details of. Un-check the Show states check box.
The state internals will now be hidden. The state will now display a 'H' graphic, that denotes
hidden content. Checking Show states will return the view to normal.
Pushing and Popping States

You can push into and pop out of states that have hidden content. Pushing into the state will
open it as the main state in the State Builder, and the internal details shown. To do this right
click in the state with hidden content, select push. To return to the original view, right click in
the outer state and select pop.
Related Topics
Overview of Simulator Tool State Builder Menus
Adding an Event
The Capital Analysis State Builder uses events to allow component models to move from one
state to another. There are four different types of event used by the State Builder all of which are
drawn in the same way.
To draw an event the engineer must first select one of the event buttons from the speed bar on
the left hand side of the State Builder window. The event type section provides a list of the
different events, their corresponding buttons and a short explanation as to their use. Now move
the cursor onto the canvas, notice that the cursor changes to a crosshair. The crosshair must then
be moved over the state from which the event will fire, hold down the left mouse button and
drag the mouse so that the line that appears connects to the desired state. When you are happy
that the event is in the right place release the button. If the line appears gray in color, one or both
ends of the event are disconnected. See “Moving Events” on page 224 for how to reconnect
them.
Event Types
• Normal Event. The Normal event is the most common and is used to move from
one state to another when a condition or conditions are satisfied.

February 2016
State Builder
Adding an Event
• Loop Event. The Loop event should be used when a component model must
exercise a delay before changing state. A counter can be used with the value of the
counter as part of a condition to model the delay. (e.g. fire if count < 5).
• Default Event. The default event is used to define the initial state of the state chart
or component model.
• Exit Event. This event is used when a state chart moves to another state which
requires an additional state in another concurrency group then to exit its current state.
Defining Event Conditions

When a new event is drawn with autoedit turned on, the Edit Event Dialog will appear. This
allows the engineer to rename the event and define its conditions for firing. If the engineer
chooses to perform this task later, clicking the "OK" button will accept the default name and
allow the engineer to continue.
If autoedit is turned off or the engineer wishes to return later to edit the event conditions, the
same dialog can be invoked by double clicking on the relevant event.
Moving Events
To move an event or reposition either of its ends, the event must first be selected by clicking on
it. The selected event will be highlighted with three handles. The handles at each end are used to
reposition the event where it connects to the different states. The middle handle allows the
engineer to move the name and conditions of the event to a location where it is more readable.
To reposition the end of an event, move the cursor over the relevant handle then press and hold
down the left mouse button. Drag the mouse so that the handle moves to the desired location
and release the button. To move the name and conditions of an event to a more readable location
follow the same procedure but select the middle handle. If it is the entire event that is to be
moved, first highlight the event by clicking on it and then follow the same procedure once again
but this time select part of the line that represents the event rather than one of the handles. In
most cases when drawing an event an engineer will probably be required to use a combination
of these procedures to make the state chart easier to read.
Related Topics
Adding a New State Adding a Concurrency Group

February 2016
State Builder
Adding a Concurrency Group
Adding a Concurrency Group

If a complex component like an ECU is to be modelled using a state chart, it is likely that the
chart will need to use concurrency groups. A concurrency group contains a number of possible
states grouped in such a way that only one state within the group can be active at any one time.
A state chart that uses concurrency will have more than one concurrency group. For example
the model of an ECU in the figure below might be part of a headlamps circuit with one
concurrency group defining the state of the DIPPED_BEAM and the other defining the state of
the MAIN_BEAM.
The concurrency groups are depicted by the yellow lines when viewed on a color screen.
To create a concurrency group click on the concurrency button located on the speed bar to the
left hand side of the State Builder window. Now move the cursor onto the canvas, notice that
the cursor changes to a crosshair. Identify which states are to be included in the group and move
the cursor to a location outside of the outermost state in the group, then click and hold down the
left mouse button and drag the mouse. When you are happy that all the desired states are located
within the group, release the mouse button to create the new group.

February 2016
State Builder
Related Topics
Adding a New State Adding an Event

This topic details importing and exporting state machines.
Importing a State Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Exporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Choose Grid Settings Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Edit Comment Dialog (State Builder) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Edit Event Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Structure Error Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Importing a State Machine

State Machines can be imported from various format. The result of an import is always a new
state machine. This means that it is not possible to import an state machine into a component
model object. To invoke the import dialog, click the File->Import menu. This will open the
Import StateMachine window.
Select the type of object you want to import from and click NEXT. Follow the instructions until
the object is imported.
Two types of imports are currently supported:
• SQL Export - this format is used to exchange a single Capital Analysis object between
databases.
• StateMate - state charts can also be imported from StateMate.
Exporting
State Machine can be exported from various format. The state machine should be saved before
the export is invoked. To invoke the export dialog, click the File->Export menu. This will open
the Export StateMachine window.
Select the type of object you want to export to and click NEXT. Follow the instructions until the
object is exported.

February 2016
State Builder
Two types of exports are currently supported:
• SQL Export - this format is used to exchange a single Capital Analysis object between
databases.
• EPS (encapsulated postscript) - this format can be used to include state machine
diagrams into word processor documents.
Related Topics
State Builder

February 2016
State Builder
Choose Grid Settings Dialog
Choose Grid Settings Dialog

To access: Accessed when using the State Builder.
The Choose Grid Settings dialog allows the grid settings for the State Builder to be changes.
Using this dialog you can vary both the width and the height of the grid.
The OK button will accept the new grid settings. The CANCEL button will reject them.
Related Topics
State Builder

February 2016
State Builder
Edit Comment Dialog (State Builder)
Edit Comment Dialog (State Builder)

The Edit Comment dialog allows graphical comments to be added to State Machines. These
comments provide line pointer that can be dragged to point to the aspect of the state machine the
comment is for.
The OK button will accept the text entered. The CANCEL button will reject the text entered.
Related Topics
State Builder

February 2016
State Builder
Edit Event Dialog
Edit Event Dialog

The Edit Event dialog edits an event in the state machine. Three aspects of an event that can be
edited: the name of the event, he condition that must be satisfied to fire the event and the action
that is executed when the event fires.
Characteristics
To change the name of the event, click the name text box. delete the existing name and type in
the new name. The combo boxes can be used to create conditions and actions for the event.
See the language reference guide for more information about conditions and actions.
Related Topics
State Builder

February 2016
State Builder
Edit State Dialog
Edit State Dialog

The Edit State dialog edits a state in the state machine.
Characteristics
Two aspects of a state that can be edited:
• The name of the state.

• The actions executed when the state is activated for the first time.
To change the name of the state, click the name text box. delete the existing name and type in
the new name. The combo boxes can be used to create the actions for the state.
See the language reference guide for more information about conditions and actions.
Related Topics
State Builder

February 2016
State Builder
Structure Error Dialog
Structure Error Dialog

To carry out some basic checks on a state machine select Tools > Check Integrity from within
the State Builder window. If there are no errors then a dialog will open informing you that your
state machine in OK.
Characteristics
If there are errors, a dialog listing the errors in your state machine is displayed. Double click on
each error in turn to bring up a Fix Structural Error dialog. This dialog allows you to select
one of a number of options to fix the error.
Related Topics
“Overview of Simulator Tool” on page 39 Adding a New State
Import and Export State Machines State Builder Menus

February 2016
Chapter 14
QScheme Builder
Under Capital Analysis electrical circuits can be simulated using three different types of
simulator, depending on the simulation type chosen by the engineer. In order to perform Spice
(Numeric) simulations and extract results, QSchemes must be defined.
Overview of QScheme Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Checking the QScheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Defining QScheme Bands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Opening an Existing QScheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Opening an Existing QScheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
QScheme Menus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
QScheme Warning Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
QScheme Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Saving QSchemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Overview of QScheme Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Overview of QScheme Builder

A QScheme has a unique name and a list of one or more bands. Each band has a label to identify
it, minimum and maximum values.
The output from the simulator is tested against the minimum and maximum values in each band
and if in the range then the band is valid for the simulator output. The bands must not overlap
and there should be no missing bands (See “Checking the QScheme” on page 234). This
QScheme is described as a numerical QScheme as it covers a numerical range. In certain cases,
that are dependent on the models used for the simulation, the simulators output may be an
enumerated type, string QSchemes cater for these cases and they consist a name and a list of
bands as in numerical QSchemes. The bands differ as they consist of a label to describe the band
and another string that is a valid simulator output (this is model dependent).
Building QSchemes
The QScheme Builder is used to create and edit QSchemes, shown below:

February 2016
QScheme Builder
Checking the QScheme
There are a number steps involved in building/modifying a QScheme these are as listed below:
1. Creating a QSchemee using the QScheme Builder Wizard (see “Creating a New
QScheme” on page 242).
2. Opening QSchemes (see “Opening an Existing QScheme” on page 238).
3. Defining bands (see “Defining QScheme Bands” on page 236).
4. Checking the QScheme (see “Checking the QScheme” on page 234).
5. Saving QSchemes (see “Saving QSchemes” on page 243).
Related Topics
QScheme Menus QScheme Wizard

After a QScheme has been defined it must pass a number of checks before it can be saved.
The QScheme has to comply with the following rules:
• No two numerical bands range can overlap.

• No dead bands can exist - The bands in the QScheme must cover the entire numerical
range from minus infinity to plus infinity.

February 2016
QScheme Builder
• No bands can have empty labels or values.No duplicate string values are allowed.
The above rules can be checked automatically.
Running a Check
If a QScheme is not already open, open one.
Select Tools > Check Integrity or alternatively select the check integrity tool button, .
Any errors that will affect the use of the QScheme will be reported.
Errors
The errors found in the QScheme are reported in the following way:
• Overlapping Bands
An error dialog will appear that contains a list of bands that overlap with other bands, as
shown:
It must be noted that you cannot save a QScheme that contains overlapping bands.
• Dead Bands
An error dialog will appear that contains a list of all the dead band in the scheme. This
comprises of a band for each of the range of numbers not covered by the QScheme, as
shown:

February 2016
QScheme Builder
Defining QScheme Bands
To add the dead bands to the QScheme click OK, to ignore click Cancel. However you
cannot save a QScheme that contains dead bands.
• Missing Entries
If empty labels or values exist then the following dialog appears:
• Duplicate String Values

If duplicate string values exist then the following dialog appears:

A QScheme can consist of one or more bands. Numerical QSchemes must cover all numbers
from minus to plus infinity. String QSchemes must cover all possible results for a model that
generates an enumerated output after a simulation.

February 2016
QScheme Builder
Numerical QSchemes
These contain bands with three fields, the label, the minimum value and the maximum value.
The following steps create a new band.
1. To add a band, click on Edit > Add Band, from the menubar, or on the add band button,
, in the toolbar. If bands are present, the new band will be inserted at the high-lighted
position, otherwise it will be added to the end of the table.
2. Default values will be automatically inserted into the band. The label can be changed by
entering the label cell of the band by double clicking on it as shown below:
3. Change the label by entering new text.

4. Set the minimum value of the band by double clicking on the minimum value, >=, cell of
the band as shown below:
5. Change the value by entering a number. This can be an integer or floating point format
number.
6. The minimum value may be minus infinity, this can be entered by clicking once in the
cell and selecting the -INFINITY from the list.
7. Set the maximum value for the band by double clicking on the maximum value cell of
the band:
8. Change the default value by entering a number.

9. Again this number may be positive infinity, this can set by a single click in the
maximum value cell and selecting +INFINITY from the list:

February 2016
QScheme Builder
Opening an Existing QScheme
String QSchemes
These contain bands with two fields, the label and the string value. The following steps create a
new band:
1. To add a band, click on Edit > Add Band, from the menubar, or on the button in the
toolbar. If bands are present, the new band will be inserted at the high-lighted position,
otherwise it will be added to the end of the table.
2. Default values will be automatically inserted into the band. The label can be changed by
entering the label cell of the band by double clicking on it:
3. Set the string value of the band by clicking on the string value cell:
4. Change the default value by entering the text.
Editing QSchemes
A QScheme may need to be edited. To change the value in a text field (e.g. the bands label)
click on the cell and enter the new text. To change the value in a numeric field (e.g. minimum
value) double click on the cell and enter the new value, if the value is to change to infinity then
select it from the drop down list that appears in the cell. Further bands can be added at a later by
selecting Edit > Add Band, from the menubar, or clicking on the button in the toolbar.
Deleting bands is achieved by selecting the band and selecting Edit > Delete Band, from the
menubar, or clicking on the button in the toolbar.
Ordering QSchemes
The QScheme may be sorted. Depending on the QScheme type affects the way sorting is
performed. Numerical QSchemes are sorted by the minimum value, string QSchemes are sorted
alphabetically by the label field. To sort the QScheme select Tools > Sort Bands, from the
menubar, or click on the sort tool button , from the toolbar.
Opening an Existing QScheme

To open an existing QScheme the following steps should be taken.

February 2016
QScheme Builder
QScheme Menus
Procedure
1. If the QScheme builder is not already open then it should be started. This can be done by
pressing Space Bar and entering QScheme Builder.
2. To open an existing QScheme either select File > Open from the menubar or click on
the Open button in the toolbar, .
3. Navigate and select the QScheme you wish to open in the open dialog and click Open.
QScheme Menus
The following section describes the contents of the menubar in the QScheme Builder.
File Menu
The File menu option are shown below:
• New - Creates a new QScheme.

• Open... - Opens and existing QScheme.
• Save - Saves a QScheme to the database.
• Save As... - Saves a QScheme with a given name.
• Print - Prints the QScheme information.
• Print Preview... - Sets the printer settings and displays the pages that will be sent to the
printer.
• Import... - Imports a QScheme from file (.xsql file).
• Export... - Exports a QScheme to SQL (.xsql file).
• Close - Closes the current QScheme.
• Exit - Exits the QScheme editor.
Edit Menu
• Cut - Cuts the selected band from the QScheme and places it on the clipboard.
• Copy - Copies the selected band from the QScheme to the clipboard.
• Paste - Pastes a band from the clipboard into the QScheme.
• Add Band - Adds a band at the selected location in the QScheme.
• Delete Band - Deletes the selected band from the QScheme.

February 2016
QScheme Builder
QScheme Warning Dialog
Tools Menu
• Check Integrity - Runs checks on the QScheme to ensure it is valid.
• Sort Bands - Sorts the QScheme bands.
Help Menu
• Current - Displays help regarding the current context.
• Contents - Displays help contents.
• Index - Displays the help index.
• Search - Searches the help system for a given topic.
• About - Displays version details regarding Capital Analysis.

This dialog contains errors and warnings that are associated with the Quantization Scheme. This
dialog is shown when the user demands an integrity check, or when a save is performed. The
dialog consists of either a list of overlapping bands, missing bands or other warning messages.
These are explained in greater detail below.
Errors and Warnings

The errors found in the QScheme are reported in the following way:
• Overlapping Bands
An error dialog will appear that contains a list of bands that overlap with other bands, as
shown:

February 2016
QScheme Builder
Note
You cannot save a QScheme that contains overlapping bands.
• Dead Bands
An error dialog will appear that contains a list of all the dead band in the scheme. This
comprises of a band for each of the range of numbers not covered by the QScheme, as
shown:
To add the dead bands to the QScheme click OK, to ignore click Cancel. However you
cannot save a QScheme that contains dead bands.
• Missing Entries
If empty labels or values exist then the following dialog appears:
• Duplicate String Values

If duplicate string values exist then the following dialog appears:

February 2016
QScheme Builder
QScheme Wizard
Related Topics
QScheme Wizard
Selecting File > New in the Quantization Scheme Builder window will start the QScheme
Wizard which will help you create a new QScheme. The first wizard screen describes the steps
involved in the wizard.
Creating a New QScheme

Selecting File > New in the Quantization Scheme Builder window will start the QScheme
Wizard which will help you create a new QScheme. The first wizard screen describes the steps
involved in the wizard.
In the second wizard step you must select the QScheme type. String QSchemes are used for
interpreting Saber simulation results when the Saber simulation engine returns string values. If
you choose to create a String QScheme the wizard will finish at this step. Numeric QSchemes
are used for matching numeric values with text labels.
If you have chosen to create a Numeric QScheme then the third step of the wizard will ask you
to select the type of Numeric QScheme you wish to create. Voltage, Resistance and Current
QSchemes are used in component models to enable Spice simulations. The Other option is used
for creating QSchemes used in component mappings.
If you chose to create a Voltage QScheme then a forth step of the wizard will ask you to select
between creating a Normal or Logic Voltage QScheme. The Logic option is used for QSchemes
which are going to be used with digital component models e.g. that use high and low signal
levels. The Normal option is best used for all other component models such as motors or lamps.
When you have selected all the appropriate options in the wizard click Run to close the wizard
and open you new QScheme in the Quantization Scheme Builder. Use the Quantization Scheme
Builder to complete your QScheme.

February 2016
QScheme Builder
Saving QSchemes
Related Topics
QScheme Menus Opening an Existing QScheme
Defining QScheme Bands Checking the QScheme
Saving QSchemes
Saving QSchemes
The following describe saving QSchemes. In order to save a QScheme it must first pass the
integrity checks.
The integrity checks are run upon saving and any errors will prevent the save operation (see
“Checking the QScheme” on page 234).
Saving New QSchemes

The following steps apply to save a QScheme that has not previously been saved.
1. Select File >Save from the menubar, or the save button in the toolbar, .
2. If the QScheme fails the integrity checks then the errors need to be removed before
continuing.
3. In the save dialog that has appeared navigate to the location where the QScheme is to be
saved, the save dialog is shown below:

February 2016
QScheme Builder
Saving QSchemes
4. Enter the QSchemes name in the object text field.

5. Click Save.
Saving Existing QSchemes

To save an existing QScheme select File >Save from the menubar, or the save button in the
toolbar, . Note that it may fail integrity checks and the QScheme will not be saved. If the
QScheme requires renaming then follow the steps below:
1. Select File >Save As... from the menubar.

2. If the QScheme fails the integrity checks then the errors need to be removed before
continuing.
3. In the save dialog that appears navigate to the location that the QScheme should be
saved to and enter the new name.
4. Click on Save.

February 2016
Chapter 15
Analysis Settings
The Analysis Settings dialog is for setting the analysis project model to be used with the
Capital Integrator project.
It's also used for setting any global expressions. See “Assigning a Project” on page 245 to find
out how to set the project. Examples of global expressions are battery voltage or temperature of
a zone, such as:
const int ENGINE_TEMP := 110;

Component models can read this and use these parameters. Use the accelerator on the right of
the 'Global Expressions' panel to help build them, or type directly into the box.
Capital SimProject. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Assigning a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Assigning a Project
After creating an analysis project, the next step is to assign it to a Capital project. To do this
follow the steps below.
Procedure
1. Open a Capital project in Capital Project.
2. Open the 'Projects' folder , and ensure that you can see all the folders in the Capital
project you loaded in step 1.
3. Right-click on the 'Analysis' folder, click on 'Edit' in the pop-up.
4. Click on the file open button , in the 'Analysis Settings' dialog.
5. In the file chooser, select the analysis project model, click 'Open'.
6. Click 'OK' in the 'Analysis Settings' dialog.

February 2016
Analysis Settings
Assigning a Project

February 2016
Chapter 16
Scoping
In Capital Logic, analysis scoping provides a way to set the scope or perimeter of the
simulation, and thus the analysis. Every conductor, device and logical connection in the scope
will be simulated. A scope can be a design or a build list.
To find out more about more about designs and build lists, please consult the Capital Logic and
Capital Project user guides.
Setting the Scope

Either:
• Click the Set Scope button ( ) on the Analysis Tab and select any design, Logic build
list or Analysis build list.
• Open a project in Capital Logic, right-click on the design revision to analyze and select
Analysis > Set Scope.
Procedure
Alternatively:
1. Create an Analysis build list containing designs that you want to analyze in Capital
Logic or Capital Project.
2. Open a project in Capital Logic.
3. Set the Analysis build list as active in Capital Logic by pressing Space Bar and entering
Set Active.
4. Open a diagram from the analysis build list.
5. To run an analysis, select one of the analysis options by pressing Space Bar, entering
Analysis and selecting one of the analysis options.
Note
Setting an active Logic build list within a Capital Logic desig does not set the analysis
scope to that build list. If you run an analysis when a Logic build list is active, the
analysis runs on either the last scope that was set or, if no scope has been set, on the
currently active design.

February 2016
Scoping
Related Topics
“Overview of Simulator Tool” on page 39
“Overview of Capital SimCertify” on page 79
“Overview of Capital SimProve” on page 123
“Overview of Capital SimStress” on page 135
“Capital SimScript” on page 103

February 2016
Chapter 17
The Design Inspector
Only available from within the Capital Integrator application, this dialog offers a method for
investigating the simulation feedback and variables of design objects during simulation, drilling
down to data that cannot be displayed using visual feedback on the Capital Integrator plane.
The following topics detail the use of the Design Inspector:
“Accessing the Design Inspector” on page 249
“Using the Design Inspector with Capital Analysis” on page 250
“Extending the Design Inspector” on page 251
Accessing the Design Inspector

The Design Inspector is available in Capital Integrator regardless of whether a simulation is
running, but no simulation feedback will be provided unless a simulation has been started.
The only reason to launch the Design Inspector without a simulation running is if you have
extended the inspector’s functionality by creating and implementing an extensibility plugin. See
“Extending the Design Inspector” on page 251 for more information.
Procedure
1. Set the analysis scope to the open plane by right-clicking on the plane name in the
design browser, then selecting Analysis > Set Scope.
2. Either:
• Right-click on the plane in the design browser and select Analysis > Simulator
• Press Space Bar and enter Simulator
The Simulator Tool is displayed.
3. Begin the simulation. See “Running a Simulation” on page 49 for more information.
4. Press Space Bar and enter Show Design Inspector. The Design Inspector is displayed.
Related Topics
“Using the Design Inspector with Capital Analysis” on page 250

February 2016
Using the Design Inspector with Capital Analysis
Using the Design Inspector with Capital

Analysis
By default, the Design Inspector offers a single Analysis tab, displaying all of the simulation
feedback from the active simulation of a Capital Integrator plane.
Note
See “Extending the Design Inspector” on page 251 for information on adding tabs to the
Design Inspector.
The Analysis tab is divided into two areas:
Object Browser
With no objects selected on the Capital Integrator plane, this tree menu displays all objects on
the plane - namely bundles, slots, connectors and nodes. Selecting an object on the plane
restricts the display to the selected object.
The object browser is broken down into the following columns:
• Parent
Displays object names and relationships. Clicking on the plus [+] symbol to the left of
an object in the menu expands the tree to show the child objects of the selected parent.
For example, expand a bundle to view the wires routed through it; expand a connector to
view its pins; expand a slot to view the devices placed within it.
• From/To
Displays the points at which conductors and connectors are electrically connected. For
example, for conductors, the terminating pins are displayed; for connectors, directly
connected devices and/or bundles are displayed.
• Activity
All conductors and objects with analysis models attached have an entry in this column,
where they are listed as either active or inactive. Additionally, a block of color indicates
the object’s state, following the same coloring rules as applied when displaying
simulation feedback on the Capital Integrator plane; for wires, the direction of current
flow is indicated by an arrow.
Clicking on an electrical object (a conductor or an object with an analysis model attached)
enables the second area of the Design Inspector: the object data display.

February 2016
Extending the Design Inspector
Object Data
Only enabled when an electrical object is selected in the object browser, these two tabs display
the simulation data and the state of all variables applicable to the object:
Tooltip
This tab, only applicable when running a numeric or supported external simulation type,
displays all of the information that would be available in a tooltip when running a dynamic
simulation. The tooltip data for a selected device or conductor varies according to the behavior
and structure of the attached model.
Variables
This tab displays all electrical simulation results available for the selected object, as would
otherwise be displayed in the Simulator’s Property Viewer. The list of results includes any
component interfaces configured for the model, as well as properties and scripted variables.

The Design Inspector is available as an interface to expose the functionality of custom plugins
that you may want to create to extend the Capital applications. Once a plugin has been loaded, a
new tab will be added to the inspector, from where all of the plugin’s functions can be accessed.
The creation and application of plugins is detailed in a separate document called
CustomInspectorDevelopment.pdf, which can be found in the \doc\plugin folder of your Capital
home directory.
Once the plugin has been placed in the correct location, check it has been loaded and refresh the
installed plugins list if necessary. Open Capital Integrator, press Space Bar and enter Plugins. If
the custom plugin is not displayed in the Available Plugins list, click the Reload All button to
refresh the list. Once you have verified that the plugin is present, close the dialog.

February 2016

February 2016
Chapter 18
Component Model Encryption
Capital Analysis supports the encryption of component models as encrypted XML (.exml) files,
allowing you to share your library models with your customers or other third-parties without
exposing your intellectual property (IP). Although it will be possible for third-parties to
simulate designs using your encrypted models, as well as being able to view all component
interfaces, it will not be possible to view the structure or behavior of a model, or edit the model
in any way. Additionally, only external model properties (of Direction: Input) and pin
attributes will be available for reporting purposes.
Overview of Component Model Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Exporting Encrypted Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Importing Encrypted Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Overview of Component Model Encryption

Capital Analysis’ component model encryption is based on the provision of
encryption/decryption keys along with the encrypted models; only installations of Capital
Analysis with access to the key(s) used to encrypt the models will be able to use them. These
keys are created on the originating system by a system administrator and stored in key files,
which can be emailed or distributed on a disk. Key files can store multiple encryption keys,
allowing you to maintain one or more files per customer and ship all of the keys needed for
simulation of a set of components in a single file.
Note
Component Model Encryption is only supported when operating Capital Analysis within
the Capital Harness System suite of products.
Key files can be stored in two locations:
• In the \resources\keys sub-directory of the Capital Analysis home folder.

• In a single alternate location: either a local directory or a location on a remote machine.
The use of another location requires the creation of an environment variable -
$AS_KEYS. This option allows key files to be stored in a centralized location, with
added security protocols as available.
Capital Analysis will check both of these locations for valid key files whenever any of the
following processes are performed:
• Simulating a design

February 2016
Exporting Encrypted Components
• Attaching a component model

• Importing an encrypted model
It is possible to export encrypted component models that have dependencies to other entities
within the database. For example, Component Model templates and VHDL dependencies.
• When exporting a component model with a template attached, the necessary template
information will be included within the encrypted model, allowing it to operate correctly
on a system that does not have access to the template.
• When exporting a component model with a VHDL dependency, a message will be
displayed to warn that a VHDL dependency exists. It will be necessary to export any
referenced VHDL models from the External Model Manager and supply these to the
third party before the encrypted components will be usable. See “External Model
Management” on page 281 for more information on exporting VHDL models, and see
“Encrypting VHDL-dependent components” on page 256 for information on how to
import and use VHDL-dependent models.
Related Topics
“Exporting Encrypted Components” on page 254
“Importing Encrypted Components” on page 256
“Encryption Key Management” on page 302

When exporting a design for use by a third-party, all attached component models must also be
made available if simulation of the design is to be possible, and these components should be
encrypted to protect your IP contained within each one.
Note
Before you can export an encrypted component, your system administrator must have
created at least one encryption key and key file. See “Encryption Key Management” on
page 302 for more information on creating and managing keys and key files.
To export a component
1. Open the Object Manager and navigate to the component model you wish to export.
2. With the model highlighted, select Tools > Export Encrypted... from the menu.

February 2016
Note
You can select multiple components for export by holding down the CTRL or SHIFT
keys while selecting subsequent models; CTRL will allow the selection of multiple, non-
adjacent components, SHIFT will allow the selection of two components along with all
components in-between.
3. The Choose Encryption Key dialog will be displayed. The key flagged as the default
on the Encryption tab of the Configuration Tool will be offered, but you can select a
different key from the list if required. Once the correct key is selected, click OK.
4. A Save dialog will be displayed. Navigate to the location in which you wish to place the
encrypted component file (.exml) before clicking the Save button. If you selected
multiple components for export, a Save dialog will be displayed for each one, allowing
you to modify the file name and location in which to save the component each time.
5. Once the encrypted model has been successfully saved, a message will be displayed to
inform you; click OK to confirm and clear the message. If you chose to export multiple
components, the message will display the number exported.
To export a folder of components

1. Open the Object Manager and navigate to the folder of component models you wish to
export. Ensure that the folder is visible in the right-hand pane of the object manager so
that it can be selected.
2. With the folder highlighted in the right-hand pane, select Tools > Export Encrypted...
from the menu.
3. The Choose Encryption Key dialog will be displayed. The key flagged as the default
on the Encryption tab of the Configuration Tool will be offered, but you can select a
different key from the list if required. Once the correct key is selected, click OK.
4. A Save dialog will be displayed. Navigate to the location in which you wish to place the
encrypted component files (.exml) before clicking the Save button.
Note
Note that the Files of type field displays “(Folders)” instead of listing the file type of the
encrypted models. The models will, however, be saved as individual encrypted
component models (.exml files) within the selected location.
5. Once the encrypted model has been successfully saved, a message will be displayed to
inform you of the number of models that have been exported; click OK to confirm and
clear the message.

February 2016
Importing Encrypted Components

Encrypted components can only imported if the key used to encrypt them is present. Ensure that
the relevant key file(s) have been made available and placed in the correct location before
attempting an import, otherwise you will encounter an error and be unable to continue.
See the “Overview of Component Model Encryption” on page 253 for more information on
supported key file locations.
To import a component
1. Open the Object Manager and select Tools > Import Encrypted... from the menu.
2. An Open dialog will be displayed. Navigate to the location in which the encrypted
component file (.exml) is stored, select it, then click the Open button.
Note
You can select multiple components for import by holding down the CTRL or SHIFT
keys while selecting subsequent models; CTRL will allow the selection of multiple, non-
adjacent components, SHIFT will allow the selection of two components along with all
components in-between.
Note
If the key used to encrypt a model cannot be found, a message will be displayed to inform
you that the import has failed. The message will be display the name of the missing key
file, allowing you to take steps to remedy the problem before attempting the import again.
Click OK to clear the message and cancel the import.
3. A dialog will be displayed prompting you to select the location in Capital SimCore in
which you wish to place the imported component. Navigate to the desired location, enter
a name for the component model in the Object field, then click the Save button. If you
have selected multiple components to import, the dialog will be displayed once for each
component.
4. Once the encrypted model has been successfully added to Capital SimCore, a message
will be displayed to inform you; click OK to confirm and clear the message. If you
selected multiple components to import, the message will display the number of
components imported.
Encrypting VHDL-dependent components

Although it is possible to export encrypted component models with associated VHDL models,
the contents of the VHDL model will not be included in the exported component. However, the
component will retain its reference to the VHDL model, so re-establishing this link on the third-
party system is possible.

February 2016
1. In the External Model Management screen, select the VHDL models required by the
encrypted component models and export them to a new export library. See “External
Model Management” on page 281 for more information on exporting VHDL models
libraries.
2. The VHDL library will be compressed to a .zip file. Transfer this to the third-party
system and unzip it into <install_location>\tools\adms\[library_name], replacing
[library_name] with the name given to the new VHDL library during export, creating
this directory if necessary.
3. Navigate to <install_location>\resources\resources and edit the RunTime.properties
file.
The new library needs to be identified to the system, and this is achieved by modifying
the following section:
#Capital Transient properties

netsim.simapi.library.attach=WORK_LIBRARY
netsim.simapi.library.attach.WORK_LIBRARY.path=L:/Example/Project/s
im_adms/netlist/WORK_LIBRARY
These two lines hold the name and location of the work library (the WORK_LIBRARY
references will hold the name of the actual work library). To add the new library in
addition to the work library, add a carriage return, then add the following lines:
netsim.simapi.library.attach=LIBRARY_NAME
netsim.simapi.library.attach.LIBRARY_ABC.path=L:/Example/Project/si
m_adms/netlist/LIBRARY_NAME
substituting the real library name and the location of the library directory.
Once Capital Analysis has been restarted, the new library will be available to the
system.
1. Before the VHDL-dependent models can be exported, they must be edited to reference
the new library. Refer to “Embedding VHDL-AMS Models” on page 187 for
information on how to edit the library reference.
2. Export the encrypted, VHDL-dependent component(s) and transfer them to the third-
party system, ensuring that the relevant encryption keys are also transferred.
3. Import the encrypted models into the Component Database. See “Importing Encrypted
Components” on page 256 for more information.

February 2016

February 2016
Chapter 19
Menus and Dialogs
This chapter details the various menus and dialogs available in Capital Analysis.
Export Netlist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Edit Stress Report Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
General Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
About Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Filter Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Input Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Progress Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Export Netlist
This option allows you to export the netlist to XML or Saber format.
Exporting to XML
To export to xml, follow the steps below:
1. Press Space Bar and enter Export Netlist.

2. Select 'Capital Analysis Netlist' from the export filter list, click Next.
3. Click Browse, and choose a location and file name for the export file.
4. Click Save, from the save dialog.
5. Click Next, to complete the export, click Close.

February 2016
Menus and Dialogs
Edit Stress Report Styles
Exporting to Saber (Export Netlist)

Note
If you are exporting a design as a Saber Model Template Definition, there are a number
of prerequisites required to ensure that the netlist is exported correctly. See “Saber
Integration” on page 345 for more information.
To export to Saber, follow the steps below:

2. Select 'Saber Design Netlist', click Next.
3. Check 'Invoke Saber on netlist', if you want to invoke the Saber application with the
netlist.
4. Click Browse, and choose a location and file name for the export file.
5. Click Save, from the save dialog.
6. Click Next, to complete the export, click Close.
If the checkbox was selected at step 3, then Saber will be launched on completion of step 6.
Edit Stress Report Styles

Accessed by selecting Edit > Edit Report Styles in the Capital SimStress main dialog.
This dialog allows you to manage default and custom report styles outside of the Stress
Analysis Wizard. The following actions can be performed:
• On the Basic tab:

o To create a new stress style, click on the button to launch the Custom Styles
Dialog Box, from where you can create and configure a new report style.
o To edit a stress style, first select it in the Stress Styles list, then click the button to
launch Custom Styles Dialog Box from where you can edit the selected style.
o To delete a stress style, first select it in the Stress Styles list, then click the
button.
Caution
Deleting a stress style cannot be undone.
• On the Advanced tab:

February 2016
Menus and Dialogs
General Dialogs
o To export a stress style (other than the defaults), first select it in the Stress Styles
list, then click the button to launch the Export Report Style dialog. See Import and
Export of Stress Styles for more information.
o To import a stress style, click the button to launch the Import Report Style dialog.
See Import and Export of Stress Styles for more information.
o To copy an existing stress style, first select it in the Stress Styles list, then click the
button. In the New Name dialog, enter a name to identify the new style before
clicking OK. The style is added to the Stress Style list, from where you can select
and edit it.
o To rename a stress style, first select it in the Stress Styles list, then click the
button. In the New Name dialog, enter the new name for the style before clicking
OK.
General Dialogs
The following dialogs can be accessed from a number of points within Capital Analysis.
About Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Filter Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Input Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Progress Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
About Dialog
This dialog shows information about the build of Capital Analysis installed on your system,
specifically the Release Number and Release Date. This information will be necessary if you
ever need to log a support call against your software.
Error Report Dialog

This dialog shows any errors raised whilst simulating a subsystem. Three levels of error
message can be raised:
WARNING: These messages indicate problems that will not stop a simulation from
running. The Show warnings check box on this dialog can turn these messages on or off.
ERROR: These messages indicate problems that will stop a simulation from running

February 2016
Menus and Dialogs
General Dialogs
SERIOUS ERROR: These messages indicate serious problems that will stop a
simulation from running. Such messages are usually raised as a result of external
problems (lack of memory, no room on the hard disk)
For more general information, see the sections on the language reference guide supplied in the
install CD and “Troubleshooting” on page 317.
Filter Wizard
The filter wizard is used to import or export an object in Capital Analysis to/from an external
format. Merely select the required import/export operation, click the NEXT button and follow
the instructions.
Above is an example of an import operation for a component model.

February 2016
Menus and Dialogs
General Dialogs
Above is an example of an export operation.
Find And Replace Dialog

The Find and Replace dialog is used to search for and optionally replace a text string in a file.
To find a string
1. Enter the text string into the Find text field.
2. Click the Find next button start the search.
3. The string should now be highlighted in the text editor.
4. Press the Find next button again to find the next string.
5. Continue pressing the Find next button for each text string you wish to find.
6. To quit, click the windows exit button.
To find and then replace a string

1. Enter the text string you want to find into the Find text field.
2. Enter the text string you want to replace into the Replace with text field.
3. Press the Find next button start the search.
4. The string should now be highlighted in the text editor.

February 2016
Menus and Dialogs
General Dialogs
5. Press the Replace button to replace the current string.

6. To quit, click the windows exit button.
Input Dialog
The input dialog allows a text string to be entered into Capital Analysis.
An example of its use is the Go To dialog:
Enter the line number you which to go to and press the [OK] button. Press the [Cancel] button to
return without entering the text.
Object Properties Dialog

In the Object Manager, by selecting an object and clicking the View > Properities menu entry,
this dialog will be displayed.
The Name field indicates the name of the selected object. The Id field indicates its unique
database id. The Type field indicates the type of the object. The Location indicates the folder
the object resides within. The Created at section give a date stamp and user on creation. The

February 2016
Menus and Dialogs
General Dialogs
Last modified at gives a date stamp and user when last modified. The Lock section shows all
the locks on the object. In the above example there are no locks. Click OK to close the dialog.
Related Topics
Object Manager
Open/Save Object Dialog

This dialog is used to open and save objects in the database.
The main area of the chooser shows the folder structure of the database. Within these folders,
only those objects with the same type as the one you wish to load/save are shown. The location
box indicates the currently selected folder. The object box shows the currently selected object or
the name of the object you wish to create. This dialog can be used to create sub folders by
clicking the CREATE SUB FOLDER button. For a selected object, properties about the object
can be shown by clicking the PROPERTIES button. To cancel the operation click the CANCEL
button. Click the OPEN/SAVE button to complete the load/save operation.
It should be noted that when you are opening an object, you cannot enter the name in "Object:"
box. The required object must be selected.
Related Topics
Object Manager
Printing
In many of the Capital Analysis family windows you will be able to select Print and Print
Preview... from the File menu. The Print option will send the appropriate pages straight to your
default printer. The Print Preview option will open the Print Preview window so you can see
all the pages laid out.
If you select File > Page Setup within the Print Preview window, then the Page Setup dialog
will be displayed.
The Page Setup window allows you to set the page size, source, orientation and margins.
Related Topics
Component Builder Related Menus Simulator Tool Menus

February 2016
Menus and Dialogs
General Dialogs
Progress Dialog
The progress dialog appears whenever an operation could take a significant length of time. The
name of the operation is shown in the title. The progress of the operation is indicated by the
progress bar and the estimated time remaining.
The operation can be stopped by clicking the Stop button.
Related Topics
Run Scenario Wizard Capital SimCertify Menus
Console
If there are any print statements in the behavior of any component, these messages will be
displayed in this window. Furthermore, if the Spice module is installed, important information
about the Spice simulation may appear here.
This facility is available in the Overview of Simulator Tool. An example window is shown
below.
It should be noted that print statements may be displayed more times than there are steps in a
simulation. This is because some statements may be evaluated multiple times within a
simulation step. Also, this window is not cleared unless this is specified in the Edit Options

February 2016
Menus and Dialogs
General Dialogs
Dialog. As a result, print statements will be added to the console when further simulations are
done. This window will be closed when the Overview of Simulator Tool is closed.
Menubar
This window has the following menu entries:
File > Exit: Exits the console viewer.
Edit > Options: This menu entry opens the options dialog. See “Edit Options Dialog” on
page 269 for more details.
View > Clear Console: This clears all the messages in the console.
Related Topics
Database Dependency Check Dialog

When deleting an object from the database (using the Object Manager), a dependency checking
operation is performed. This operation search the database for other objects that depend on the
existence of the object that you are about to delete.
If there are any dependencies, a warning window will be opened.
To continue with the delete operation click Yes. Any affected subsystems will no longer work
unless a new component model is used to replace the deleted one. The component model
attacher (see “Attaching Component Models” on page 199) can be used to replace the deleted
Component Model with a new one. If, however, you do not want to affect the other objects or
are unsure for any reason, click CANCEL and the object will not be deleted.
Related Topics
Object Manager

February 2016
Menus and Dialogs
General Dialogs

February 2016
Chapter 20
Editing Global and User Options
This chapter details the various global and user option settings available in Capital Analysis.
Edit Options Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
General Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Syntax Highlighting Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Automation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
RPN Default Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Report Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Simulation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Simulation Highlighting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Model Search Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Component Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Error Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Qualitative Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Modeling Language Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Simulation Engine Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Numeric Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Spice Simulator Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
External Model Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Structure Editor Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
State Builder Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Edit Options Dialog

This dialog configures various global and user options.
When the window is first displayed it will look like the screenshot below.

February 2016
Edit Options Dialog
Fields
The left-hand pane contains a tree of options that can be changed.
The right-hand pane changes based on the selection made on the left-hand pane. If you select a
color option in the left-hand pane, for example, the right-hand pane will change to the color
selection options (see “Changing Color Options” on page 272). Similarly, if you select a font
options in the left hand pane, the right-hand pane will change to contain the font selection
options (see “Changing Font Options” on page 273).
The left-hand pane has several sections:
• General contains options like the look and feel of the GUI.
• Qualitative contains options for the qualitative simulation engine module.
• Numeric contains options for the Spice simulation engine module and the VHDL-AMS
external model manager.
• State Builder contains options for the qualitative simulation engine module. This
section will only be present if the edit option dialog is opened from the State Builder.

February 2016
General Options
• Structure Editor contains options for the qualitative simulation engine module. This
section will only be present if the edit option dialog is opened from the Structure Editor
(see “Defining Component Structure” on page 167).
Related Topics
General Options Qualitative Options
Numeric Options Structure Editor Options
State Builder Options
General Options
See the following topics for details of the options that can be changed in this section.
• “Syntax Highlighting Options” on page 271
• “Automation Options” on page 274
• “RPN Default Options” on page 274
• “Report Options” on page 275
• “Simulation Options” on page 275
• “Simulation Highlighting” on page 275
• “Model Search Path” on page 278
• “Component Categories” on page 279
• “Error Reporting” on page 279
Related Topics
Qualitative Options Numeric Options
Structure Editor Options State Builder Options
Syntax Highlighting Options

This section allows the colors for syntax highlighting to be changed.
• Comments: changes the color of comments used in the Saint modeling language.
• Strings: changes the color of strings used in the Saint modeling language.
• Keywords: changes the color of keywords used in the Saint modeling language.
• Methods: changes the color of methods used in the Saint modeling language.

February 2016
• Operators: changes the color of operators used in the Saint modeling language.
• Constants: changes the color of constants used in the Saint modeling language.
See “Changing Color Options” on page 272 for details on changing these options. You should
try to avoid using the same colors for more than one of these options.
To turn off syntax highlighting, select Syntax highlighting in the left-hand pane and uncheck the
Syntax highlighting enabled box.
Changing Color Options

For all color options, there are three tabs available, each allowing you to select the color
required in different ways:
• Swatches: select from standard colors.

• HSB: select color using the Hue, Saturation, Black mechanism.
• RGB: select color by setting the Red, Green, Blue intensity of the color.
In either case, the preview section below will display the color you have selected.
Note
It should be noted that the color may look slightly different if viewed on different
computers or monitors.
Swatches tab
To select a color using this tab, follow these steps:
1. Click on the color you wish to use.
2. Look at the preview section to ensure that this is the color you want to use.
3. Click on a different color if it is not to your liking.
4. Click on the color in the recent box to go back to a color you have recently clicked on.
5. Click OK to accept the color change and Cancel to reject it.
HSB
1. Select the H (Hue) radio button.

2. Move the slider up or down to select the color you want. You could also move the
circle in the color area with the mouse.

February 2016
3. Select the S (Saturation) radio button.

4. Move the slider up or down to select the brightness of the color you want. You could
also move the circle in the color area with the mouse.
5. Select the B (Blackness) radio button.
6. Move the slider up or down to select the blackness of the color you want. You could
also move the circle in the color area with the mouse.
7. Look as the preview section to ensure that this is the color you want to use. Repeat the
previous steps if it is not the color you want.
8. Click OK to accept the color change or Cancel to reject it.
RGB
1. Move the slider to set the red to select the red intensity value for the required color.
2. Move the slider to set the green to select the green intensity value for the required
color.
3. Move the slider to set the blue to select the blue intensity value for the required color.
4. Look as the preview section to ensure that this is the color you want to use. Repeat the
previous steps if it is not.
5. Click OK to accept the color change, Cancel to reject it or select another option to
change from the list in the left-hand pane.
Changing Font Options

Font options can be edited for specific objects listed in the Edit Options facility.
Follow these steps to change the fonts:
1. In the browser tree on the left of the facility, select the object font that you want to edit
(for example, the name font for states).
2. Select the font you require using the first combo-box:

February 2016
Automation Options
3. Select the type of font you require using the second combo-box:
4. Select the size of the font you require using the third combo-box:
5. Look as the preview section to ensure that this is the font you want to use. Repeat the
previous steps if it is not.
6. Click OK to accept the color change, Cancel to reject it or select another option to
change from the list in the left-hand pane.
Automation Options
This section allows you to turn on/off various automation options.
• Map values - should pins be automatically mapped in the component attacher (see
“Attaching Component Models” on page 199).
• Console refresh - should the console be refreshed automatically.
• Integrity check - should the integrity of objects be checked when those objects are
saved.
RPN Default Options

The RPN Defaults section of the Edit Options facility allows RPN related options to be set:
• Default severity - should the severity be overridden if uncontrolled thermal activity is
detected? For FMEA report generation, when an issue with a function is detected (it fails
or is achieved unexpectedly), the severity value of the function used to calculate the
RPN value. This options allows you use a different severity value if the failure results
uncontrolled thermal activity.

February 2016
Report Options
• Occurrence ratios - Each occurrence number is associated with a likelihood of failure

ratio. These ratios can be entered here. It is important to enter this information correctly
as it is used in the generation multiple FMEA reports.
Report Options
The Report section of the Edit Options facility sets various options for report generation:
• Encapsulate all function labels in double quotes - should they be encapsulated in
double quotes in the reports generated by Capital Analysis.
• Generate all text for a report in - this combo-box allows you to select the language
used in the reports generated by Capital Analysis.
Simulation Options
In the Simulation section of the Edit Options facility, various qualitative simulation options
can be changed.
• Automatic Reset of Catastrophic Failures in Interactive Simulation - if this option is
set the catastrophic failures, such as short circuits and blown fuses, are reset prior to re-
simulation being run in interactive simulations.
• Enable caching of component information across a session - if set, this option caches
information on all components until the session is closed.
• Enable logging of debugging info during component information reading - this
option allow detailed debugging information to be recorded in a log file during
component information reading.
• Ensure netlist is present before reading simulation information - option for
checking that the netlist is present before simulations start.
Simulation Highlighting
The Simulation Highlighting option in the Edit Options facility allows the user to define
labels that map to colors. These are then used to colour components and wiring in diagrams
during simulation. Once defined, the user can modify the color of the component or wire by
using the label within the component behavior, acting on some condition of the device, over-
current for instance.
The left panel contains a list of defined highlighting labels.

February 2016
The right panel contains a name field of the label, and the color setup itself. This panel has
tabbed options if the ECAD tool is using white or classical black backgrounds. This will allow
alternative colors if the background is toggled. There are some sub-tabs to set the color. Please
see “Changing Color Options” on page 272 for details about the use of the color selector.

February 2016
Add/Update and Remove buttons are below this section for adding a newly defined highlight,
updating an existing one or deleting an entry from the list.
Adding a New Highlight

To add a new highlight entry do the following:
1. Click in the Name field and enter a unique name

2. Specify the color for this label on white backgrounds by selecting the White
background tab
3. Select the color from Swatches/HSB/RGB tabs
4. If you would like to specify the alternative for black backgrounds, then select the Black
background tab and repeat the last step.
5. The Update button will now have changed to Add. Click this to add the label to the list.
Editing an Existing Highlight

To edit a highlight entry do the following:

February 2016
Model Search Path
1. Select the highlight from the Defined Colors list

2. Modify the color for this label on white backgrounds by selecting the White
background tab
3. Select the color from Swatches/HSB/RGB tabs
4. If you would like to modify the alternative for black backgrounds then select the Black
background tab and repeat the last step.
5. The Add button will now have changed to Update. Click this to update the changes.
Deleting a Highlight
1. Select the highlight from the Defined Colors list
2. Click on Remove
Model Search Path

The Model Search Path option in the Edit Options facility is to set the database directory
paths that Capital Analysis uses to search for component models that are used in a design.
It consists of a list of paths, and to the right of this, arrow buttons to move the selected entry up
or down in the list. Below this Add path... and Remove path ... buttons, to add and remove
paths.
Adding a Path
To add a path:
1. Click on the Add path ... button

2. In the Add folder dialog that appears, enter the path
3. Click OK in the dialog
Deleting a path
To delete a path:
1. Select the path from the list

2. Click on the Remove path... button

February 2016
Component Categories
Component Categories
This option in the Edit Options facility is to specify the categories that components are
organised under when using Capital Analysis. This allows more productive use of the tool as
components can be listed, selected and manipulated by category, for example.
There are number of reserved categories also that are listed. These cannot be removed or
modified. Once categories are specified, they will be available in the Component Builder.
Adding a Category
1. Click on the Add button
2. Enter a name in the Category Name dialog
3. Click OK
Edit a Category
1. Select the Category, click on the Edit button
2. Edit the name in the Category Name dialog
3. Click OK
Delete a Category
1. Select the Category
2. Click the Remove button
Error Reporting
In the Error Reporting section of the Edit Options facility, various qualitative simulation
options can be changed.
• Enable the display of additional warning messages - this option will show extra
warning messages in the console and integrity checking dialogs.
• Enable full debugging information to be logged- this option allows detailed
debugging information to be recorded in a log file.
Qualitative Options
See the following topics for the options that can be changed in this section of the Edit Options
facility:

February 2016
Modeling Language Options
• “Modeling Language Options” on page 280

• “Simulation Engine Options” on page 280
Related Topics
General Options Numeric Options
Modeling Language Options

In the Modelling Language section of the Edit Options facility, various qualitative simulation
options can be changed.
• Strong type checking - allows you to switch strong type checking on or off.
• Loop events - allows you to set loop events so they execute state actions.
• While loop iterations - allows you to set the maximum number of while loop iterations
that are allowed.
Simulation Engine Options

Various options can be changed in the Simulation Engine section of the Edit Options facility.
• Enable multiple battery support - see “Multiple Batteries” on page 332.
• Display only those variables used in expressions.
• Simulation considered unresolved if the same state is seen this many times.
Numeric Options
Various options can be changed in this section of the Edit Options facility.
• “Spice Simulator Options” on page 281
• “External Model Management” on page 281
Related Topics

February 2016
Spice Simulator Options
Spice Simulator Options

In the Simulator Settings section of the Edit Properties facility, the Spice Simulator Settings
can be changed.
• Active Current - If a wire or component's current is above this value then it will be
considered active (colored active).
• Short Resistance - This is the resistance value that will be used for short circuit failures.
• Short Current - If a wire or component's current is above this value then it will be
considered shorted (colored shorted).
• Zero Resistance - This is the value of resistance that will be used for ZERO as specified
by a component model's structure (when an arc drawn is set to ZERO)
• Infinite Resistance - This is the value of resistance that will be used for INFINITE as
specified by a component model's structure (when an arc drawn is set to INFINITE)
• Load Resistance - This is the value of resistance that will be used for LOAD as
specified by a component model's structure (when an arc drawn is set to LOAD)
External Model Management

When running numeric transient simulations with usurped VHDL-AMS models, considerable
processing overhead is incurred due to the need to compile the embedded models at runtime,
and model dependencies can result in the need to run a simulation multiple times until all
models have been successfully compiled. By creating a library of VHDL-AMS object models,
you can pre-compile all models, specifying a compilation order to satisfy model dependencies.
Once all models have been compiled, they will be available to all users of this Capital Analysis
installation.
To create an external model object

1. Open the Edit Options dialog by selecting Edit > Options from the main menu
available in the Object Manager, Overview of Simulator Tool, and Component Builder.
2. From the menu on the left of the dialog, browse to Numeric > External Models. The
External Model Management screen will be displayed on the right of the dialog.
3. Click on the "Add a new external model" ( ) button. The Edit VHDL dialog will be
displayed.

February 2016
4. Enter a unique name for the model in the Name field. This name must be unique, as it
will be used to identify the model when selecting/ordering it within the External Models
list; the "OK" button will be unavailable until the name in the field is unique.
5. Enter the code for the model into the Source field. Typically, you will open your VHDL
"*.vhd" file in a standard text editor (Windows Notepad, for instance) and copy the
contents before pasting it into the Source field. Standard Cut, Copy and Paste
functionality is available within the dialog:
• To cut, either click on the button, or press Ctrl+X.
• To copy, either click on the button, or press Ctrl+C.
• To paste, either click on the button, or press Ctrl+V.
6. Click the "OK" button to close the dialog. The model will be created and added to the
External Models list.

February 2016
Note
You must compile the new model you have created before you will be able to use it. Any
attempt to reference an uncompiled external model from within a script will result in an
error during simulation.
To compile an external model

1. Open the Edit Options dialog by selecting Edit > Options from the main menu available
in the Object Manager, Overview of Simulator Tool, and Component Builder.
2. From the menu on the left of the dialog, browse to Numeric > External Models. The
External Model Management screen will be displayed on the right of the dialog.
3. Click on a model name in the list to select it. You can select multiple models by shift-
clicking a number of adjacent models, or by Ctrl-clicking a number of non-adjacent
models.
Note
When compiling more than one model, or using the "Rebuild the model library from
scratch" option, as detailed below, the order in which the models will be compiled is
determined by their position within the External Models list. If one model references
another, the referenced model must be compiled first to avoid generating an error. Refer
to the section on managing the external model list, below, for more information.
Note also that while a model is being compiled it will not be possible for another user on
the system to amend or delete that model. During a rebuild (see below) no models can be
amended or deleted.
4. Click the "Compile the selected models" ( ) button. The status pane of the Edit
Options dialog will display a message to confirm the success or failure of the
compilation. Following a successful compilation, the compiled model will be added to
the database, where it will be available for use during simulation.
Note
Compiled models are stored in the database for reasons of performance during simulation
only; they cannot be viewed or accessed from within the Object Manager.
5. You can delete all compiled models from the database and recompile all models in the
list by clicking the "Rebuild the model library from scratch" ( ) button, which will
ensure that all models are compiled using the most up-to-date code available. Models
will be compiled in list order so, again, ensure that the list is ordered correctly to ensure
that models referenced by other models are compiled first. See the section on managing
the external model list, below, for more information.

February 2016
To manage the external model list

The order in which models appear in the External Model list is important, as it dictates the order
in which the models will be compiled when compiling multiple models or refreshing the model
list from the database. If one model is dependant upon another, the referenced model must be
compiled first to avoid errors.
To change a model's position within the list, you must first select it by clicking on it. You can
select multiple models by Shift-clicking a number of adjacent models, or by Ctrl-clicking a
number of non-adjacent models. Once you have selected one or more models to move, the
following options are available:
• Move to top ( ) - the selected model(s) will be moved to the top of the list. If you have
selected more than one model, the model order within the selection will be maintained.
• Move up ( ) - all selected models will be moved one position higher in the list.
• Move down ( ) - all selected models will be moved one position lower in the list.
• Move to bottom ( ) - the selected model(s) will be moved to the bottom of the list. If
you have selected more than one model, the model order within the selection will be
maintained.
To edit an external model

Note
If another user is working in the Edit Options dialog, all models will be "locked" for that
user, and all options on the Numeric > External Models screen will be disabled apart from
the "Edit the selected model" button. However, clicking this button, or double-clicking on
a model in the list while a model is locked will open the Edit VHDL dialog in read-only
mode: you will be able to view the contents of the model, but you will not be able to make
any changes. While a model is open in read-only mode, it will not be possible for another
user to make any changes to that model.
Clicking the "Refresh the selected models" ( ) button will update the External Model
list to reflect any changes that other users may have made since you have been viewing
the list, including the creation and deletion of models.
1. Select the model you wish to edit and click the "Edit the selected model" ( ) button.
Alternatively, double-click on the model you wish to edit.
2. The Edit VHDL dialog will be displayed.
3. You can rename the model by overwriting the contents of the Name field, but the name
must still be unique; if you attempt to change the name to that of an existing model, the
"OK" button will be disabled, forcing you to change the name back before you can save
the model.

February 2016
4. You can amend the contents of the Source field as required. The option to search for
specific terms within the source code, and to find and replace terms, is available by
clicking on the "Find text in expression" button ( ) to access the Find And Replace
Dialog.
5. Once you have finished editing the model, click on "OK" to save the changes to the
database and close the Edit VHDL dialog.
To delete an external model

1. Select the model(s) you wish to delete. You can select multiple models by shift-clicking
a number of adjacent models, or by Ctrl-clicking a number of non-adjacent models.
2. Click the "Delete" button ( ). A message will be displayed asking you to confirm the
deletion; click "OK" to proceed and remove the model from the database, or click on
"Cancel" to abort the deletion.
To unlock all external models

If, for any reason, one or more external models remain locked once all users have exited the
External Model Management screen, it is possible for a system administrator to remove any
persistent locks.
1. In the Object Manager dialog, select Tools > Admin Mode from the main menu.
2. An Enter Password dialog will be displayed. Enter your administrator password and
click the "OK" button.
3. The Object Manager dialog will be renamed "Administrator" to indicate that you are
now operating in Administration Mode. Also, the Tools > Admin Mode menu option
will be ticked.
4. Select Tools > Unlock VHDL Models from the main menu.
5. A message will be displayed to confirm that all external models have been unlocked
successfully.
Note
The Unlock VHDL Models option will remove the locks on ALL models; you cannot
choose which models to unlock.
To export external models

This option allows you to export one or more VHDL models as a compiled library, allowing
them to be transferred to another installation of Capital Analysis. When exporting encrypted
component models with VHDL dependencies, this is a necessary step in making sure that the

February 2016
required VHDL models are available in the destination Capital Analysis installation when the
encrypted models are imported.
Caution
In order for the VHDL dependancies to be maintained in the destination Capital Analysis
installation, the VHDL models must be exported first, then the VHDL-dependent models
must be edited to reference the new VHDL library before exporting them. Refer to
“Embedding VHDL-AMS Models” on page 187 for more information on editing the
library references within the component models.
1. Select the models you wish to export. Click on a single model to select it, Shift-click on
non-adjacent models to select those models and all in-between, or CTRL-click to select
multiple, non-adjacent models.
2. Click on the Export Selected Models icon. The Library Name dialog will be displayed.
3. When you export the VHDL models, they will be compiled into a temporary library,
which will then be compressed into the archive file. Enter a name for the library in the
field. The Delete temporary library when finished? option allows you to specify
whether this library should be deleted once the archive file has been created; this is
selected by default, and should be deselected if you want to use the temporary library for
testing your edited VHDL-dependent component models.
4. Click the OK button. If the library name you entered in step 3 matches one already in
use, you will be prompted to enter a new name, otherwise a Save dialog will be
displayed. Navigate to the location in which you wish to save the archive (.zip) file and
enter a File name before clicking the Save button.
5. The compressed archive file will be created and saved in the specified location. This file
can then be copied to the target Capital Analysis installation and unzipped, recreating
the library structure. Before this library can be accessed on the target system, its location
must be added to the RunTime.properties file located in the /resources/resources/ sub-
directory of the Capital Analysis home folder. Within the section beginning:
# Capital Transient properties
add the following lines:
netsim.simapi.library.attach=LIBRARY_ABC
netsim.simapi.library.attach.LIBRARY_ABC.path=L:/Example/sim_adms/n
etlist/LIBRARY_ABC
replacing LIBRARY _ABC with the name of the compiled library, and
“L:/Example/sim_adms/netlist/LIBRARY_ABC with the full path to the library file.

February 2016
Structure Editor Options
Note
You can define multiple compiled libraries in this way by adding subsequent library
names to the definition, separated by a space. For example:
netsim.simapi.library.attach=LIBRARY_ABC LIBRARY_DEF. Once the libraries have
been defined, each will need a separate line specifying the path to the library file.
Related Topics
“Embedding VHDL-AMS Models” on page 187
Structure Editor Options

The following options can be changed in the Structure Editor section of the Edit Options
facility.
See “Changing Color Options” on page 272 for details about changing color options and
“Changing Font Options” on page 273 for details about changing font options.
• Editing
o Automatic edit - determine if nodes, arcs and comments should be edited
automatically when they are first created.
o Grid Preferences - should the grid be on when you first open the structure editor?
• Drawing Objects
o Text Options
• Name font - changes the font used for the names of nodes and arcs.
• Name color - changes the color used for the names of nodes and arcs.
• Link Options
o Link color - changes the color used for the links between nodes and arcs.
• Node Options
o Node color - changes the color used for nodes.
o Node failure color - changes the color used nodes when a failure is applied.
• Arc Options
o Arc color - changes the color used for arcs.
o Arc Failure color - changes the color used arcs when a failure is applied.
o Display arrow on arcs? - should arrows that indicate FORWARD current flow be
shown on the arcs?

February 2016
• Comments
o Background color - changes the background color used for comments.
o Foreground color - changes the foreground color used for comments.
o Border color - changes the border color used for comments.
o Font - changes the font used for comments.
Related Topics
Numeric Options State Builder Options

The following options can be changed in the State Builder section of the Edit Options facility.
See “Changing Color Options” on page 272 for details about changing color options and
“Changing Font Options” on page 273 for details about changing font options:
• File Operations
o Automatic integrity check - determine if an integrity check should be performed
when the state machine is saved.
• Editing
o Automatic edit - when a state or event is first created, should the edit for that object
be opened.
• Drawing objects
o States
• Inactive color - changes the colors used when states are inactive whilst being
simulated.
• Active color - changes the colors used when states are active whilst being
simulated.
• Foreground color - changes the color used for a state whilst being viewed or
edited.
• Name font - changes the font used for the name of the state.
• Action font - changes the font used for the actions within the state.
• Concurrency groups

February 2016
o Foreground color - changes the color used for a group whilst being simulated,
viewed or edited.
• Events
o Inactive color - changes the color used when an event is inactive whilst being
simulated.
o Active color - changes the color used when an event is active whilst being
simulated.
o Unlinked color - changes the color used for an event that is not connected to a state.
o Foreground color - changes the color used for an event whilst being viewed or
edited.
o Name font - changes the font used for the name of the event.
o Condition font - changes the font used for the conditions for the event.
o Action font - changes the font used for the actions for the event.
• Comments
o Background color - changes the background color used for comments.
o Foreground color - changes the foreground color used for comments.
o Border color - changes the border color used for comments.
o Font - changes the background font used for comments.
Related Topics
Numeric Options Structure Editor Options

February 2016

February 2016
Chapter 21
Configuration Tool
This tool configures various global options. It should only be used by your support team and/or
the Capital Analysis Administrator.
Caution
None of the operations available in this tool should be carried out while other people are
using Capital Analysis.
Configuration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Encryption Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Optional Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Configuration Tool - dsAdmin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Change Administrator Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Encryption Key Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Configuration Tool
This tool configures various global options. It should only be used by your support team and/or
the Capital Analysis Administrator.
Version
This tab displays the overall version number of Capital Analysis. In addition, a list of the
installed modules is given. It is important to check this tab if you have just installed an
additional module to Capital Analysis.

February 2016
Configuration Tool
Configuration Tool
Diagnostics
This tab allow various diagnostic operations to be performed on Capital Analysis. Two
diagnostic checks are available:
• Installation - checks the Capital Analysis installation (this operation is not supported in
the current release).
• Database- checks the integrity of the Capital Analysis database, fixing all the errors that
it can.
This tab can also be used to tidy the database. This operation removes any temporary
information held in the database. Such information can remain in the database if Capital
Analysis crashes for any reason.

February 2016
Configuration Tool
Configuration Tool
Data Sources
This tab allows the database that Capital Analysis uses to be configured. Once configured it is
not recommended that this information be changed. Capital SimCore can support multiple
different database configurations, these are all managed from this tab.

February 2016
Configuration Tool
Configuration Tool
The current (active) configuration is shown in red. This can be changed by double clicking on
any of the entires. To Test a connection to ensure that the database server can be contacted, and
that the login details supplied are valid, highlight one of the entries in the list and select Test.
After a short delay you will be informed as to whether a connection could be made to the
database.
If you wish to make a copy of an existing data source, click on the copy button.
If you wish to delete an entry, highlight the entry in the list, before clicking on the Delete
button. Before the entry is deleted you will be prompted to confirm that you wish to perform
this action. If you do accidentally delete a connection, it will have to be re-created.
To add a new connection, click on the Add button. You will be presented with the connection
configuration wizard. In the first panel you must specify the RDBMS that you intend to use. A
list dropdown will contain all the supported types.

February 2016
Configuration Tool
Configuration Tool
The options are:
• MySQL - for connecting to a MySQL RDBMS.

• Oracle - for connecting to an Oracle RDBMS.
• Remote - for connecting to an Oracle database via the Capital Analysis Data Relay.
Note
The Oracle integration requires that a version of the Oracle client software is installed on
the client machine.
The next pane captures information on the location and access details for the specified RDBMS.

February 2016
Configuration Tool
Configuration Tool
Your system administrator will have these details. Tick the Enable debugging button for
additional debugging information during the use of the tool. This can be useful if you are having
some problems with your connection.
Encryption Keys
This tab displays the details of the encryption keys that are available for use when exporting or
importing encrypted component models. See “Component Model Encryption” on page 253 for
more information.
The pane on the left of the tab shows all available keys, nested in any key files that have been
created. Clicking on a key to select it will result in its details being displayed in the fields on the
right of the tab, although the contents of the Key Code field will be replaced with asterisks for
security (in normal user mode).
In normal user mode, the only action that can be performed on this tab is the nomination of a
key as the default to be used when exporting an encrypted component model. This is achieved
by first selecting a key in the left-hand pane, then clicking the Use As default Key option. The
icon of the key will change from to to indicate that it is now the default.
Note
To create or delete keys, or to create a new key file, the Configuration Tool must be run
in Administration mode. See “Encryption Key Management” on page 302 for more
information.

February 2016
Configuration Tool
Configuration Tool
Optional Components
The 'Optional Components' tab allows you to enable or disable optional components, so as to
prevent licensing warnings. Checking the boxes enables the components.

February 2016
Configuration Tool
Configuration Tool - dsAdmin

The configuration tool can be run standalone in a special mode that allows the administration of
data sources and the creation and maintenance of encryption keys.
Datasource Administration
The Configuration Tool has as additional tab called Data Source Admin.

February 2016
Configuration Tool
This tab performs the following actions:
• Populate - Populates the selected data source

• Update - Updates the selected data source to a version specified by an external .sql file
• Transfer - Transfers all data from a populated data source to an unpopulated data
source
• Backup - Makes a backup of the selected data source
• Save Log - Saves the transcript to file
• Utility Update - This updates a v3.2 export file to the current version
• Set datasource administration password - Allows you to change the password used to
log into Admin Mode. See “Change Administrator Password” on page 302 for more
information.
In order to start the configuration tool in this way, open a command window or terminal and
type:
CapitalAnalysisConfiguration -dsAdmin

February 2016
Configuration Tool
Populating a data source

Caution
If you are connecting to a database that has been configured and populated for use with
Capital Analysis already, you must not perform this step.
1. Select the data source you wish to populate from the Selected datasource drop-down
list. Click the Populate button.
2. The Populate datasource window is displayed. Check the Configure database box and
the Populate database box. Click the OK button.
3. The Tablespace file window is displaced. Specify the full path to the location of the
tablespace file that will be created for the database that you are using. You must create
the file in the same folder as the other tablespace files for the database that you are
using.
If the database is on the same computer as the Capital Analysis application, the path
looks something like this:
C:\ORACLE\ORADATA\CAPITAL
If the database is on a separate computer, you must ensure that the folder containing the
tablespace files is shared and that read/write permissions are set on it. You specify the
path to this folder as follows:
\\[name of server]\[shared folder name]
For example:
\\123.123.123.12\CAPITAL
Click the OK button.
4. A dialog requesting a username is displayed. You must enter the database administrator
username.
5. A second dialog requesting a user password is displayed. You must enter the database
administrator password.
6. The main window on the DataSource Admin tab shows the progress of the configuration
and population processes. The configuration process creates the CANALYSIS user and
the Capital Analysis tablespace. The population process creates the Capital Analysis
database schema (the databases and indexes used by the application). When the
processes are complete, the following is displayed in the output window:
Done POPULATE : Success = true
7. When the database is configured and populated, test the connection by clicking on it on
the Data Sources tab and clicking the Test button.

February 2016
Configuration Tool
Updating a data source

1. Select the database that you would like to upgrade from the Selected datasource drop-
down list.
2. Click the Update button.
3. The Update datasource dialog is displayed. Click the Choose file button to navigate to
one the following location:
<install_location>\data\sql\Oracle
then open the sub-directory named with the number of the version to which you are
upgrading.
Select the upgrade_database.sql script.
4. On the Update datasource dialog, click the OK button to upgrade the database.
5. The progress of the upgrade is displayed in the Configuration Tool dialog. Once the
update has completed, the output window will display:
Done UPDATE : Success = true
Transferring a data source

Once you have populated a data source, you have the option to transfer all of the Capital
Analysis data from that datasource to another, unpopulated datasource.:
1. Select the populated data source from which you wish to transfer the data from the
Selected datasource drop down.
2. Click Transfer.
3. The Transfer data dialog is displayed. Select the target, unpopulated data source for the
transfer, from the Select target drop down.
4. Click OK.
5. The output window will display the progress of the transfer.
Backing up a data source

You can save a backup version of a populated data source by doing the following:
1. Select the data source you wish to backup from the Selected datasource drop down.
2. Click Backup.
3. The Backup datasource dialog is displayed. Click Choose file

February 2016
Configuration Tool
Change Administrator Password
4. A Save dialog is displayed. Navigate to the location in which you wish to save the
backup file and enter a file name before clicking on Save.
Change Administrator Password

This window allows the Administrator password for Capital Analysis to be changed. This tool
should only be used by your support people and/or the Capital Analysis Administrator. To
change the password:
1. Enter the current password in the first text box.
2. Enter the new password in the middle text box.
3. Confirm the new password in the last text box.
4. Click OK to change to the new password, CANCEL to leave the password unchanged.
Related Topics
“Configuration Tool” on page 291
Encryption Key Management

This tab is used to create and maintain encryption keys for use when exporting and importing
encrypted component models.
See “Component Model Encryption” on page 253 for more information.
Note
Although this tab is available when operating the configuration tool in normal user mode,
the contents (with the exception of the Use As Default Key option) are uneditable. You
must be running the tool in -dsAdmin mode to make any other changes on this tab.

February 2016
Configuration Tool
To create a key file

1. Click the New Key File... button.
2. A Save dialog will be displayed, with the <install_location>\resources\keys directory
selected by default. Unless you have created a $AS_KEYS environment variable
pointing to a different location, leave this default location selected.
3. Enter a File name for the key file. then click the Save button.
4. A key file must contain at least one key, so you will be prompted to create a new key
immediately. The New Key dialog will be displayed, allowing you to enter a Key Name
(mandatory) and a Description (optional )for the new key. Once you have entered this
information, click OK.
5. The new key file will be visible in the pane on the left-hand side of the tab, with the full
path and filename displayed. The new key you created will be visible immediately
beneath the key file. Click on the key to highlight it (if it is not already) and the fields on
the right of the tab will displayed the following details:
• Key Name - this is the name that will be displayed whenever you are prompted to
select a key; for example, when exporting an encrypted component model.
• Description - an optional field available to store more information about this key.

February 2016
Configuration Tool
• Capability - a Capital Analysis capability code for component model simulation.

• Key Code - this is the encryption key in its unencrypted format. Note that this is
only visible when running the Configuration Tool in -dsAdmin mode; in normal
mode the contents of this field will be replaced with asterisks.
To create a key
1. In the pane on the left-hand side of the tab, click on a key file to highlight it. This is the
key file within which the key will be created.
2. Click the New Key... button. The New Key dialog will be displayed, allowing you to
enter a Key Name (mandatory) and a Description (optional) for the new key. Once you
have entered this information, click OK.
3. The key will be added to the selected key file. Selecting the key wil result in the fields
on the right of the tab displaying the key’s properties, as detailed in To create a key file,
above.
To delete a key file

Caution
It is not recommended to delete a key file unless a secure backup has been taken. It is not
possible to recreate the keys stored within it once it has been deleted. Key codes are
generated by the system when keys are created and cannot be manually entered. If you
delete a key that is still required for an existing component model, it will no longer be
possible to import that model or run a simulation with it attached.
It is not possible to delete a key file from within the Configuration Tool. If you wish to delete a
key file, remove or delete the relevant .keys file from within <install_location>\resources\keys
(or from your custom location if you have created one); the next time you run the Configuration
Tool, the key file will have been removed from the tree menu.
To delete a key
Caution
It is not possible to recreate a key once it has been deleted. Key codes are generated by
the system when keys are created and cannot be manually entered. If you delete a key that
is still required for an existing component model, it will no longer be possible to import
that model or run a simulation with it attached.
1. Click on the key you wish to delete to highlight it.

2. Click the Delete Key... button.

February 2016
Configuration Tool
3. A message will be displayed asking you to confirm the deletion: click Yes to proceed or
No to abort.

February 2016
Configuration Tool

February 2016
Appendix A
Company Preferences
This section describes how various properties can be changed to adapt Capital Analysis to your
companies needs.
Changing these properties involves editing files in
<install_location>/resources/resources/ on UNIX or
<install_location>\resources\resources on Win32 platforms.
Generic Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307

RunTime.properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
FmeaText.properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
ScaText.properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
SimulationText.properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
EcadBridge.properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
EcadDefault.properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Script Analysis Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
SaberNetlister.Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Generic Preferences
These files are called properties files. It is recommended that you backup these files before
making any changes. If more than one site in your company is using Capital Analysis, these
properties files can be modified at one site and then copied to the others.
Capital Analysis must be shutdown and restarted before changes to theses files will take effect.
Changing the properties used to generate and export reports will not change text in any existing
reports. Only the reports generated or exported subsequent to that change will be effected.
RunTime.properties
This file contains various runtime settings
Simulation Engine Properties

This property indicates the number of seconds taken between the updates of the progress bar.
netsim.progress.poll = 1

February 2016
Company Preferences
Generic Preferences
Resetting of Input Properties

This property controls the resetting of input properties if you use a reset statement or
design.consider when running a script. If it is set to true, input property values for component
models are preserved rather than reset to their default values.
netsim.maintaining.properties.between.mode.changes = true
Maths Language Support

The maths language constants can be extended via the RunTime.properties file. To extend the
language, the following needs to be done:
• Enable the support.

• Define the names of the constants.
• Specify the constants.
Examples of this follow:
This property is a switch to activate user defined math constants.
netsim.language.maths=true
This property is used to specify names of user defined constants (this must be done).
netsim.language.maths.list=PI E NEWCONSTANT1
The following properties implement the user defined list, note they are just examples.
Define PI.
netsim.language.maths.value.PI=3.141592654
Define E.
netsim.language.maths.value.E=2.718281828
Define NEWCONSTANT1.
netsim.language.maths.value.NEWCONSTANT1=1202.0309
Default QSchemes
Global default QSchemes can now be defined.
Define a current QScheme
netsim.qscheme.default.current =
/CAPITAL/QSchemes/Enumeration/Current/switch_0A001_15A0

February 2016
Company Preferences
Generic Preferences
netsim.qscheme.default.resistance =
/CAPITAL/QSchemes/Enumeration/Resistance/switch_0R0_10M0
netsim.qscheme.default.voltage =
/CAPITAL/QSchemes/Enumeration/Voltage/battery_12V0
FmeaText.properties
The simulation engine uses the information in this file to generate text for FMEA reports (see
“FMEA Editor (Capital SimCertify)” on page 69.
The FmeaText<LANGUAGE>.properties files have the same format but are for a specific
<LANGUAGE> like French, German etc...
Function Comparison Properties

The properties below determine how the expected and actual results are compared.
fmea.compare.hierarchically = true
fmea.compare.acrossEvents = true
fmea.consider.subsequent = true
FMEA Text Generation Properties

• The text for this property is used when the expected & actual results are the same.
fmea.text.same = All functions were achieved as expected.
• The text for this property is used when an unresolved simulation is detected.
fmea.text.err.unresolved = Sorry: unresolved simulation was
detected.
• The text for this property is used when a short circuit is not dealt with by a fuse.
fmea.text.err.short = A short circuit possibly caused uncontrolled
thermal activity.
• The text for this property is also used when a short circuit is not dealt with by a fuse.
fmea.text.err.short.also = However, uncontrolled thermal activity
still resulted in parts of the subsystem.
FMEA Conversion Properties

• The text for this property is used when an unresolved simulation is detected.

February 2016
Company Preferences
Generic Preferences
fmea.conv.record.unres=(SORRY: the effect of this failure could not

be determined due to oscillation).
• The text for this property is used when a short circuit is not dealt with by a fuse.
fmea.conv.record.short=(resulting in uncontrolled thermal
activity).
• This property is used to form the title for the converted FMEA report.
fmea.conv.header.title=FMEA report for
• This property is used as the title for the FMEA number field of the header.
fmea.conv.header.fnum=FMEA Number
• This property is used as the title for the product field of the header.
fmea.conv.header.product=Product
• This property is used as the title for the system field of the header.
fmea.conv.header.system=System
• This property is used as the title for the FMEA date field of the header.
fmea.conv.header.fdate=FMEA Date
• This property is used as the title for the key date field of the header.
fmea.conv.header.kdate=Key Date
• This property is used as the title for the design responsibility field of the header.
fmea.conv.header.design=Design Responsibility
• This property is used as the title for the prepared by field of the header.
fmea.conv.header.prepared=Prepared By
• This property is used as the title for the core team field of the header.
fmea.conv.header.core=Core Team
• This property is used as the title for the extra info field of the header.
fmea.conv.header.extra=Extra Info
• This property is used as the title for the initial states field of the header.
fmea.conv.header.init=Initial States
• This property is used as the title for the event sequence field of the header.
fmea.conv.header.seq=Event Sequence
• This property is used as the title for the header section of the converted FMEA report.

February 2016
Company Preferences
Generic Preferences
fmea.conv.header.head=Header Information
• This property is used as the title for the record section of the converted FMEA report.
fmea.conv.header.record=Record Information
• This property is used as the title for the item/function field of the record.
fmea.conv.title.func=Item/Function
• This property is used as the title for the failure mode field of the record.
fmea.conv.title.mode=Potential Failure Mode
• This property is used as the title for the failure effect field of the record.
fmea.conv.title.effect=Potential Effect(s) of Failure
• This property is used as the title for the severity field of the record.
fmea.conv.title.sev=S
• This property is used as the title for the class field of the record.
fmea.conv.title.class=Cl
• This property is used as the title for the failure cause field of the record.
fmea.conv.title.cause=Potential Cause(s) of Failure
• This property is used as the title for the occurrence field of the record.
fmea.conv.title.occ=O
• This property is used as the title for the design controls field of the record.
fmea.conv.title.control=Current Design Controls
• This property is used as the title for the detectability field of the record.
fmea.conv.title.det=D
• This property is used as the title for the RPN field of the record.
fmea.conv.title.rpn=RPN
• This property is used as the title for the recommended action field of the record.
fmea.conv.title.ract=Recommended Action(s)
• This property is used as the title for the responsibility field of the record.
fmea.conv.title.resp=Responsibility/Completion Date
• This property is used as the title for the actions taken field of the record.
fmea.conv.title.act=Actions Taken

February 2016
Company Preferences
Generic Preferences
• This property is used as the title for the action severity field of the record.
fmea.conv.title.asev=R S
• This property is used as the title for the action occurrence field of the record.
fmea.conv.title.aocc=R O
• This property is used as the title for the action detectability field of the record.
fmea.conv.title.adet=R D
• This property is used as the title for the action RPN field of the record.
fmea.conv.title.arpn=R RPN
ScaText.properties
The simulation engine uses the information in this file to generate text for SCA reports (see
“Overview of Capital SimProve” on page 123). The ScaText<LANGUAGE>.properties files
have the same format but are for a specific <LANGUAGE> like French, German etc...
Set this property to true if you want to allow state machine behavior when generating SCA
reports.
generation.allowComplexBehaviour = false
The title of the SCA report.
header.title = SCA report for
The schematic title.
header.schematic = Schematic
SimulationText.properties
• The error message raised when current direction over diodes could not be determined.
electrical.qual.error.diode.unresolved = Sorry: the following diode
component(s) could not be simulated:
• The error message raised when diodes could not be simulated due to oscillation.
electrical.qual.error.diode.oscillation = Sorry: diode components
caused oscillation.
• The error message raised when a short circuit has not dealt with be a fuse.
electrical.qual.error.catastrophic.short = Failure: warning -
uncontrolled thermal activity detected.

February 2016
Company Preferences
Generic Preferences
• The error message raised when dependency expressions based component models are
causing oscillation.
electrical.qual.error.depend.oscillation = Sorry: dependency
expressions caused oscillation.
• The error message raised when state machine based component models are causing
oscillation.
electrical.qual.error.state.oscillation = Sorry: state machines
caused oscillation.
• The error message raised when state machine based component models are causing
oscillation.
electrical.qual.error.state.conflict = Sorry: event conflict
detected in state machine(s).
• The error message raised when a state-machine-based component model is attempting to

modify a variable in several places at the same time.
electrical.qual.error.variable.race = Sorry: race condition
detected.
• The error message raised when a component model has become unresolved.
electrical.qual.error.component.unresolved = Sorry: the following
component(s) have become unresolved:
EcadBridge.properties
• The property below can be used to turn subsystem registration on or off. By default,
subsystem registration is on (this property only has an effect if subsystem registration is
supported by the ECAD tool).
schematic.subsystem.registration = TRUE
• The property below indicates the length of time (in milliseconds) the Capital Analysis
splash screen is displayed.
splash.delay=9000
EcadDefault.properties
This file is used specify the default value for any properties that a component model tries to
reference from the ECAD tool.
• The property below specifies defaults for a property called 'WireLength'.
WireLength = 1.0
• It is possible to specify the defaults for exact component names.

February 2016
Company Preferences
Generic Preferences
The property below specifies the default for 'gauge' on 'Wire1'.

Wire1.gauge = 10
• It is also possible to use naming prefixes.

The property below specifies defaults for 'gauge' for component names starting with
'Wire'.
Wire*.gauge = 10
Script Analysis Properties

ScriptAnalysis.properties
The following properties affect the script analyzer.
• Should we write the header element in the XML output file?

ignore.header = false
• Should we write the structure element in the XML output file?

ignore.structure = false
• Should we write the properties element in the XML output file?

ignore.properties = false
• Should we write the state machine behaviour element in the XML output file?
ignore.behaviour = false
• Should we write the variables element in the XML output file?

ignore.variables = false
• Should we write the quantitative element in the XML output file?

ignore.quantitative = false
• Should we write the components element in the XML output file?

ignore.components = false
• Should we write the buses element in the XML output file?

ignore.buses = false
• Should we write the functions element in the XML output file?

ignore.functions = false
• Should we write the uncontrolledThermalActivity element in the XML output file?

February 2016
Company Preferences
Generic Preferences
ignore.uncontrolledThermalActivity = false
• Should we write the catastrophicFailure element in the XML output file?

ignore.catastrophicFailure = false
• Should we write the unresolvedSimulation element in the XML output file?

ignore.unresolvedSimulation = false
• Should we write the color element in the XML output file?

ignore.color = false
• Should we write the ecad element in the XML output file?

ignore.ecad = false
• Should we write the failure element in the XML output file?

ignore.failure = false
• List of categories to ignore (supports wildcards/regex)

ignored.category.list =
• List of components to ignore (supports wildcards/regex)

ignored.component.list =
• List of properties to ignore (supports wildcards/regex)

ignored.property.list =
• Should we use the simple pattern matcher (?*) or full regex?

useSimplePatternMatcher = true
• Automatically reset() the simulator after each failure is applied & analyze()d?
resetSimulatorAfterEachFailure = true
• Automatically reset() the simulator after each analyze()?

resetSimulatorAfterEachAnalyze = false
• Should we clear the list of monitor()ed properties after each analyze()?

clearPatternMatchersAfterEachAnalyze = false
SaberNetlister.Properties
This file controls the structure of the netlist generated for export to Saber, and is covered in
“Saber Configuration” on page 345.

February 2016
Company Preferences
Generic Preferences

February 2016
Appendix B
Troubleshooting
This is a list of legacy problems and solutions. Please check out the Mentor graphics supportNet
site for current FAQ's and trouble shooting.
Internal "Duplication Entry" exceptions are being raised . . . . . . . . . . . . . . . . . . . . . . . 317
Internal "java.lang.RuntimeException" exceptions are being raised . . . . . . . . . . . . . . 318
Sometimes the component model attacher does not attach the component model . . . . 318
Error message "Failed to connect to component 'X' . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
Error message "Failed to initialise viewbase routines" . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Composite Components seem Disconnected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
The error report window appears, however no messages are displayed . . . . . . . . . . . . 319
Your workstation slows down after a few months . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
For TransCable users, multiple alert messages are being displayed . . . . . . . . . . . . . . . 320
When using the Simulator, functions seem to be achieved when the schematic colouring
indicates that they should not be . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
The following message appears "Sorry: dependency expressions caused oscillation" . 321
The following message appears "Sorry: current flow across diode(s) could not be
determined" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
The following message appears "Failure: warning - uncontrolled thermal activity
detected" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
The following message appears "Sorry: event conflict detected in state machine(s)" . 322
Exporting an FMEA report to some formats results in failure . . . . . . . . . . . . . . . . . . . . 322
FMEA Editor (Capital SimCertify) hangs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
reverted back to there original state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Importing an .f2f file, exported by Capital Analysis, into FMEA+ fails . . . . . . . . . . . . 324
Internal "Duplication Entry" exceptions are

being raised
Internal "Duplication Entry" exceptions are being raised.

February 2016
Troubleshooting
Internal "java.lang.RuntimeException" exceptions are being raised
Solution
• All users should close all Capital Analysis windows.
• All users should then shutdown Capital Analysis.
• One user should open the Configuration Tool on the "Capital Analysis->Utilities" menu.
• Click the "Diagnostic" tab.
• Press the "Database Check" button.
• All users can now start using Capital Analysis again.
Internal "java.lang.RuntimeException"
exceptions are being raised
Internal "java.lang.RuntimeException" exceptions are being raised.
Solution
If users are using the shell "csh", ensure that all Capital Analysis executables have world
execute permissions.
Sometimes the component model attacher

does not attach the component model
Sometimes the component model attacher does not attach the component model.
Solution
• Ensure only one component model attacher window is open at a time.
Error message "Failed to connect to

component 'X'
Error messages are being raised along the lines of "Failed to connect to component 'X'.
Solution
• Use the component model attacher to reattach the model to component 'X'.

February 2016
Troubleshooting
Error message "Failed to initialise viewbase routines"
Error message "Failed to initialise viewbase

routines"
Error message along the lines of "Failed to initialise viewbase routines." is displayed.
Solution
• Ensure that all the library directories specified in your "viewdraw.ini" file actually exist.
• Remove all those libraries that do not exist.
• Correct all those libraries that have moved to a new location in your file store.
• Check that all composite (BLOCK_TYPE = COMPOSITE) components/symbols
have an underlying schematic.
• If such a component is found and it is not meant to have an underlying schematic,
change the BLOCK_TYPE to MODULE.
• If such a component is found and it is meant to have an underlying schematic, create the
underlying schematic for it.
Composite Components seem Disconnected

When simulating a schematic, composite components within the schematic seem to behave as if
they are completely disconnected from the other parts of the schematic, where the composite
component has component directly connected to its pins.
Solution
• Always use pin blocks to connect high & low-level schematics (this is the recommended
solution).
• Ensure that the net (which is automatically created between the connector & composite
component) at the high level has the same name as the net at the lower level.
The error report window appears, however no

messages are displayed
The error report window appears, however no messages are displayed.
or
The last message in the "firstearth.errors" file is "ERROR -> could not write subsystem ..."

February 2016
Troubleshooting
Your workstation slows down after a few months
Solution
• Ensure that all composite components have an underlying schematic with components
connected to pins.
• Ensure that all objects that are not electrical components (bounding boxes, text) have a
block type of annotation.
Your workstation slows down after a few

months
Your workstation slows down after a few months.
• Several "tcBridge" or "netsim" processes are running on your system when Capital
Analysis is not running.
• Unexpectedly running out of licenses for Capital Analysis.
Solution
• Ensure both Capital Analysis and ECAD Tool is not running then kill the rogue
processes/threads (short term solution).
• Ensure that all Capital Analysis windows have been closed and then shutdown Capital
Analysis before closing ECAD Tool.
For TransCable users, multiple alert messages

are being displayed
For TransCable users, multiple alert messages are being displayed of the form: "vscript-E-
4307: vdraw2.vs: Unbound variable - 'update_cmd'"
Solution
• Never click "OK" on the Alert window, simply drag the window out of the way (short
term solution).
• Tell your Systems Administrator to edit the following file
$TRANSROOT/tdt/exec/transcable/standard/tcable01.vs and uncomment the /*
load("tcupdate.vs"); */ so it should look like load("tcupdate.vs");
• If you are unsure or this causes other problems, contact your TransCable support person
for the solution to this TransCable specific problem.

February 2016
Troubleshooting
When using the Simulator, functions seem to be achieved when the schematic colouring indicates
When using the Simulator, functions seem to

be achieved when the schematic colouring
indicates that they should not be
When using the Simulator, functions seem to be achieved when the schematic colouring
indicates that they should not be.
or
When simulating a record in an FMEA report, functions are achieved when the schematic
colouring indicates that they should not be.
Solution
• If the function expressions use the output properties of components, ensure that the
Component Models behaviour sets the output property in all situations.
The following message appears "Sorry:

dependency expressions caused oscillation"
The following message appears "Sorry: dependency expressions caused oscillation."
or
The following message appears "Sorry: state machines caused oscillation."
Solution
• Check that the state machine (or dependency expression) based components are not
continuously looping.
• Use the simulation display facility of the Overview of Simulator Tool to debug the
dependency expressions and/or state machines.
The following message appears "Sorry:

current flow across diode(s) could not be
determined"
The following message appears "Sorry: current flow across diode(s) could not be determined."
Solution
• No solution. This is due to the use qualitative simulation engine. Contact us for more
information.

February 2016
Troubleshooting
The following message appears "Failure: warning - uncontrolled thermal activity detected"
The following message appears "Failure:

warning - uncontrolled thermal activity
detected"
The following message appears "Failure: warning - uncontrolled thermal activity detected."
Solution
• In the Simulator, press the reset button to remove the short circuit.
The following message appears "Sorry: event

conflict detected in state machine(s)"
The following message appears "Sorry: event conflict detected in state machine(s)."
Solution
• Check the conditions on events in your state machines. Ensure that there is no way more
than one event can fire from each state.
• Use the simulation display facility of the Overview of Simulator Tool to debug the state
machines.
The following message appears "Sorry: race

condition detected"
The following message appears "Sorry: race condition detected."
Solution
• Check the actions in events/states in your state machines. Ensure that there is no way
more than one change can be applied to the same variable.
Exporting an FMEA report to some formats

results in failure
Exporting an FMEA report to some formats results in failure.
Solution
• Exporting FMEAs to some formats can only be done from those FMEA reports held in
the FMEA Editor (Capital SimCertify), see “Exporting an FMEA Report” on page 73.

February 2016
Troubleshooting
FMEA Editor (Capital SimCertify) hangs
Saving the FMEA report in the folder structure results in information, required by the
export filter, being lost.
FMEA Editor (Capital SimCertify) hangs

FMEA Editor (Capital SimCertify) hangs.
Solution
• The FMEA Editor (Capital SimCertify) does not work on Solaris with OpenWindows.
Please use the Common Desktop Environment (CDE).
For TransCable users, after simulating a

schematic, the colours of the schematic have
not reverted back to there original state
reverted back to there original state.
Solution
• From the TransCable menu: Select - Name - $1w* (for a sheet 1 change. Use $2w* for
sheet 2 changes, etc). This will select all wires in the schematic. Note that it also selects
displayed wire attributes, but that is fixed in step 3 of this solution.
• From the TransCable menu: Edit - Style - Colour - Red (or whatever default colour you
want to return the wires to). This will change the wire colours as desired, but also change
the attribute colours as well. See next step for fixing this.
• If you have deselected the wires after step 2, reselect them as described in step 1. Then:
Select - Attr - * - Selected (note - it is important that the "Selected" button is pressed).
• From the TransCable menu: Edit - Style - Colour - White (or whatever default colour
you want to return the attributes to).
• Alternatively, TransCable keeps a backup copy of your schematic in the sch/bak
directory. If after colouring, the colours remain blue, you can copy the backup over the
original copy of the schematic, thus restoring the colours. However, if you have done
any changes after this problem occurred, then the backup may also now have those
colours.

February 2016
Troubleshooting
Importing an .f2f file, exported by Capital Analysis, into FMEA+ fails
Importing an .f2f file, exported by Capital

Analysis, into FMEA+ fails
Importing an .f2f file, exported by Capital Analysis, into FMEA+ fails.
Solution
• This problem occurs when the size of the file is greater than 1Mbytes. This seems to be a
restriction of the FMEA+ application itself. You can reduce the size of the FMEA+
export by reducing the number of functions used to generate the FMEA report (see
“FMEA Editor (Capital SimCertify)” on page 69).

February 2016
Appendix C
Administration of Capital Analysis
It is recommended that one of the users of Capital Analysis be nominated as the Administrator.
This person should be the only one with the Administrator password.
Administrator Information
The Administrator should be aware of the following:
• The administrator password should be changed after Capital Analysis has been installed,
the initial password is password.
• You can change the Administrator password using the Configuration Tool.
• There are two types of user in Capital Analysis, the Administrator and Users (everyone
else).
• Administrator locks on objects can only be unlocked by the Administrator.
• User locks on objects can be unlocked by only that user and the Administrator.
• Objects can be locked and unlocked from the Object Manager.
• To become the Administrator, enter the Administrator password from the Object
Manager menu.
• Locking folders will lock all the objects within that folder (including objects in the sub-
folders all the way down the folder hierarchy).
• The Bulk Import/Export can be used to exchange objects between different sites.
• Take note of the recommendations concerning component libraries (see “Component
Library - Component Models Provided” on page 198).
• Using the Edit Options Dialog, ensure that the occurrence ratios that Capital Analysis
uses match those specified in your companies FMEA report standards. See “RPN
Default Options” on page 274.
• You should ensure that your companies preferences for Capital Analysis have been
setup. See “Company Preferences” on page 307.

February 2016
Administration of Capital Analysis
Administrator Information

February 2016
Appendix D
System Import/Export
There are several types of object that can exist in the database.
Import and Export Information

Almost all objects in the database can be exported and imported from the SQL export format.
This format can be used to exchange individual objects between different sites with their own
databases.
Each of these objects can be imported or exported using a Filter Wizard. For state machines, see
“Import and Export State Machines” on page 226. For FMEA reports, see“Exporting an FMEA
Report” on page 73.
Objects can also be exported and imported in bulk between sites via the Object Manager. For
information on bulk import/export, see “Bulk Import/Export” on page 34.

February 2016
System Import/Export
Import and Export Information

February 2016
Appendix E
Supply Rails, Batteries and Multiple Battery
Support
There are two types of supply that can be present in a schematic:

• Single Supplies.
• Explicit Batteries.
Single Supplies
The screenshot below shows a simple lamp circuit that uses supply rails:

February 2016
Supply Rails, Batteries and Multiple Battery Support
Single Supplies
Each supply rail is an individual symbol with an individual component model attached to it. The
positive rail has a "positive" category component model attached to it and the ground rail has a
"negative" category component model attached to it. When you create a new component model,
the first decision you make is to choose the component model's category (see “Selecting a
Component Category” on page 163). The simulation engine collects together all the positive
and negative supply rail components and connects them to a default battery.

February 2016
Single Supplies
Explicit Batteries
The picture below shows a simple lamp circuit which uses a battery:
The battery is a single symbol with a single component model attached to it. The component
model is of category type "other" and contains one positive node and one negative node (see
“Selecting a Component Category” on page 163). Such components cannot have more than one
positive or negative node, if a component is given more than one positive or negative node then
the simulation engine will connect all the positive and all the negative nodes together within
that component.
Chassis
The picture below shows a simple lamp circuit which uses a battery and chassis components:

February 2016
Single Supplies
A chassis component must not be confused with a ground rail component. They often have very
similar symbols but they are inherently different. A chassis component has a category type
"chassis". The simulation engine will connect all the chassis components together during an
analysis.
Multiple Batteries
The following multiple battery information is only relevant to Qualitative analysis.

February 2016
Single Supplies
The screenshot above shows the Enable multiple battery support checkbox which is located
in the Launcher menu Edit > Options under Qualitative > Simulation Engine. Multiple
battery support is enabled by default.
If the multiple battery support is disabled (unchecked), then the simulation engine will connect
all the positive battery terminals and positive power rails together, and it will connect all the
negative battery terminals and negative power rails together. Effectively all the batteries will be
connected together.
If the multiple battery support is enabled (checked), then the simulation engine considers each
battery by connecting its default battery to each of them in turn. While one battery is being
considered, any others within the schematic have their terminals connected together.
Multiple battery support is designed to allow large schematics with several batteries on them to
work but not for having individual circuits which contain several batteries.
It is not recommended that you connect batteries directly together in series or parallel.
It is not recommended that you mix the supply rails and explicit batteries.

February 2016
Single Supplies

February 2016
Appendix F
Self Modeling Components
Self Modeling Components comprise of a series of technologies being developed in the Capital
environment that aim to reduce the amount of work required for design engineers to simulate a
design.
By default on Capital, a user does not have to build a component model for grounds, shields,
connectors, or splices. This can be extended by a system administrator by making changes to
the 'netlister.properties' file described below.
Note
This functionality is only available to users operating Capital Analysis within a Capital-
based flow.
Creating a self modifying model map

Included below is a section of the 'netlister.properties' file that controls model mapping. Each
section is described in detail.
Specifying component type information

META_TYPE
# component.automapped.property
#
# this property identifies the property on a component that is to be used
# to identify which type of analysis model may be used when no attachment
has been
# made.
#
# i.e. component.automapped.property=META_TYPE identifies the META_TYPE
property
# on a component to contain the type of analysis model to be
automapped
component.automapped.property=META_TYPE
In order for Capital Analysis to identify a device type to associate with a suitable adaptive
component model that is not recognized as a distinct device type by Capital, the netlister must
be told where to look for the device type.

February 2016
This is achieved by looking up the value of a defined property on the device. By default this is
set to META_TYPE (case sensitive), but can be changed to any user value that does not use any
of the following characters
. <space> “ ‘
Identifying the supported device types

# component.automapped.types
#
# this space delimeted list of properties identifies the types of
component that
# may be automapped only the values listed here will be deemed valid
values for
# the component.automapped.property value.
#
# i.e. component.automapped.types=fuse battery specifies that there
are fuse
# and battery types valid for the component.automapped.property.
component.automapped.types=fuse battery motor
When the netlister detects a component with a value specified in the META_TYPE property, it
then checks the value of the property against the space delimited list of identified types. This
type is then used as an index to look up the appropriate adaptive model stored in Capital
SimCore.
Specifying Adaptive Component Models

# component.type.<typename>.model
#
# each of the types defined in the component.automapped.types field should
# have an analysis model associated here
#
component.type.fuse.model=/CAPITAL/ComponentModels/Protection/fuse_dc
component.type.battery.model=/CAPITAL/ComponentModels/Supply/battery_dc
component.type.motor.model=/CAPITAL/ComponentModels/Loads/motor_dir
For each type defined in the section above, an adaptive model must be specified to be used for
the simulation. These models are normal component models that can robustly manage situations
where perhaps not all pins are connected, or where internal connectivity is changed as a result of
pin properties.
There must be a specific entry for each type of supported device list in the previous section.
Identifying Component Model Pins

# component.type.<typeName>.pins
#

February 2016
# defines the model pins, i.e. the names of the external nodes on
# the analysis model, as a space separated list
component.type.motor.pins=NODE1 NODE2
component.type.battery.pins=POS NEG
Each pin on the simulation model that can acquire a mapping to an ECAD pin must be
enumerated here in a space delimited list. This is then used in the next section to identify a list
of match ECAD terminals that can be associated with that simulation model node or pin.
Managing Terminal Mapping Associations

# component.type.<typeName>.pin.<pinName>
#
# defines the list of ecad pins that are to be recognised as a match
# for the model pin as a comma delimited list
component.type.motor.pin.NODE1=PIN1,1,P1
component.type.motor.pin.NODE2=PIN2,2,P2
component.type.battery.pin.POS=+,POS,+ve,p,pow,pwr,sup
component.type.battery.pin.NEG=-,NEG,-ve,m,neg,gnd,erth
For each simulation model node listed in the previous section, a space delimited list of valid
ECAD terminal names that can be automatically mapped to each node.
It is the specified model’s responsibility to ensure it can manage situations where pins are not
attached.

February 2016

February 2016
Appendix G
Dynamically Generated Components
When you simulate a Capital Logic or Capital Integrator design, models are automatically
synthesized for any connector or splice (in Capital Logic) found without an attached Analysis
model. These models are created dynamically: the models are constructed with an appropriate
structure, and default behavioral code is inserted to enable the setting of resistance between
contacts.
Note
The code inserted into a dynamic model's behavior can be overridden by adding your
own code to be used in the netlister.properties file. See “To override default behavioral
code” on page 342 for more information.
Dynamic Generation
Dynamically generated connector model structures contain an additional node for each pin
(external node) on the connector, given the same name as the pin but suffixed with `.
Connecting each external node (pin) and its corresponding internal node is a resistance arc,
allowing resistances within the connector to be set.
Figure G-1. Dynamically Generated Connector Structure
The above structure is generated for each pin within a multi-pin connector. Inline connectors
feature two external pins and resistance arcs, but share the internal node (M` in the above
example) to model the connection.
As voltages can be measured at the internal and external nodes, and hence the potential
difference across the resistance arc can be calculated, it is possible to return a value for the
current travelling through the connector.
The following example shows how this structure applies (theoretically) to a connector in
Capital Logic:

February 2016
Dynamic Generation
Figure G-2. Dynamic Connector Example Structure
Dynamically generated single-pin splice structures contain three external nodes (pins)
connected to internal nodes via resistance arcs. As with connectors, the external nodes are
named according to the pins with which they are associated, and the internal nodes are given the
same name, suffixed with `.
Figure G-3. Dynamically Generated Single-pin Splice Structure

February 2016
Dynamic Generation
Note
The ` character used to identify dynamically generated internal nodes can be overridden,
and an alternative used, by adding the following argument to the
java.bridge.properties= line in the RunTime.properties file (located in
<install_location>\resources\resources):
node.associate.marking= and insert the character to use.
Setting Resistance on Dynamically Generated Arcs

If a property called "resistance" is set on the connector or splice, this will automatically be
propagated and set for each resistance arc, thus setting the component’s dc resistance. If a
connector pin has its own property called "resistance", this will be used instead.
To view a dynamically generated model

1. Right-click on the design in the project browser window, press Space Bar and enter Set
Scope. Then right-click on the design again and select Analysis > Simulator.
2. The Overview of Simulator Tool will open. Select View > View generated models
from the main menu.
3. The Dynamically generated models dialog will open:
All models generated for the simulation will be listed.

To view a model in the Component Builder, first click on the model name to highlight it
before clicking the "View" button. The Component Model Builder will open with the
component's details displayed, allowing you to amend the component's structure or
behavior if required.

February 2016
Dynamic Generation
Note
Dynamically generated models are only persisted for the purpose of simulating the
design; changes saved against the model in the Component Model Builder will be taken
into account when running the simulation, but the model itself will not be saved unless
you select File > Save As from the main menu, or return to the Dynamically generated
models dialog, select the model and click the "Save" button. In both cases, a browser
dialog will be displayed, allowing you specify a database location in which to save the
model. In order to then use this saved model, it should be attached in the normal way to a
connector or splice, as appropriate; any attempt to attach the model to another component
type will result in an error being generated.
Once you have finished viewing the model, click the "OK" button to close the dialog.
To override default behavioral code

Prior to generating the script for insertion into a dynamically generated model's behavior,
Analysis will check the netlister.properties file for any overrides. This means that you can
create blocks of code to be inserted into each model, overriding one or more of the behavior
code sections described below.
Note
The netlister.properties file can be found in the resources\resources subdirectory of your
Capital Analysis installation directory. For example:
C:\MentorGraphics\Capital\Analysis\Capital
Analysis_2006.2\resources\resources\netlister.properties
The overrides use the form GeneratedConnector.expression.[element] where [element] should

be substituted with the name of the section you wish to override: either head, pin or tail.
• head - you can enter a block of initialization statements to be executed when the
components behavior is first accessed. For example:
GeneratedConnector.expression.head=\n\
//HEAD START - MODEL MODIFIED FROM NETLISTER PROPERTIES FILES\n\
only once\n\
do\n\
if ( simulator.getSimulationType( ) = SIMULATION_TYPE_SPICE ) then\n\
float componentResistance;\n\
float pinResistance;\n\
string propertyCapture;\n\

February 2016
Dynamic Generation
propertyCapture := ecad.resistance;\n\
componentResistance := propertyCapture.toFloat( ) ;\n\
endif;\n\
done;\n\
• pin - you can enter a block of statements to be applied to EACH pin in the model. For
example:
GeneratedConnector.expression.pin=\n\
//PIN START - MODEL MODIFIED FROM NETLISTER PROPERTIES FILES\n\
propertyCapture := PINNAME.getEcadProperty( \"PROPNAME\" );\n\
if ( propertyCapture != \"\" ) then\n\
pinResistance := propertyCapture.toFloat( );\n\
PINNAME.setContactResistance( pinResistance );\n\
else\n\
PINNAME.setContactResistance( componentResistance );\n\
endif;\n\
Note
References to PINNAME and PROPNAME identify substitutions that will be made in the
model.
• tail - you can enter a block of statements to be executed as the script completes. For
example:
GeneratedConnector.expression.tail=\n\
//TAIL START - MODEL MODIFIED FROM NETLISTER PROPERTIES FILES\n\
do only once\n\
do\n\
print "The behavior of model " + self.getName() + "has been successfully
overridden.";\n\
done;\n\
The default connector resistance property name (examined as an ecad property) is "resistance"
but may be overridden using GeneratedConnector.resistance.property. For example:
GeneratedConnector.resistance.property=NewName

February 2016
Dynamic Generation

February 2016
Appendix H
Saber Integration
This section details the integration between Capital Analysis and Saber, including the
configuration of the Saber netlist, the export of the netlist, and the use of Saber Model Template
Definitions. The following topics are available:
Saber Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Exporting to Saber (Saber Integration). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Saber Model Template Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Saber Configuration
The structure of the generated Saber netlist is controlled by editing the SaberNetlister.properties
file, which is found in:
• <install_location>/resources/resources/ on UNIX
• <install_location>\resources\resources on Win32 platforms.
Note
It is recommended that you backup this file before making any changes.
The SaberNetlister.properties contents is broken down into the following sections:
Saber Properties
Saber.command.line
This is the command line that is to be used to execute Saber following the export of a
Saber netlist. <filename> will be substituted for the name of the exported netlist, i.e.
Saber.command.line=saber <filename> will execute Saber on the exported netlist.
Saber.command.line=saber <filename>
Saber Frameway Integration

An additional alternative configuration setting, saber.invoke.keepinstance, in
sabernetlist.properties allows the activation of the Saber Frameway integration. This uses the
current command line configuration to launch Saber but then establishes a persistent connection

February 2016
Saber Integration
Saber Configuration
to Saber Frameway. This and all future netlists are sent as commands over this interface. Output
from Saber Frameway is echoed to your design tool log file.
If the new key saber.invoke.keepinstance is set to “true” it causes Saber Frameway to

invoke SaberGuide. The new key is set to “true” by default. This also causes the value of the
saber.command.line to be ignored as Saber Frameway is invoked rather than the Saber Binary
specified in the command line.
If the key is not found or is manually set to “false” then the existing command line driven
method will be used running the Saber executable file with the netlist file path for every netlist
export.
Note
This functionality requires a Saber Frameway license in addition to the usual Saber
licenses.
Netlist Properties
Saber.netlist.filename
This property allows the specification of a fixed filename and file location for the
exported netlist. If this property has a value, the option to specify a filename and
location when exporting a Saber netlist will be displayed, but not available for editing.
Saber.netlist.filename=C:\Temp\Data\MyNetlist.sin
Two variables can be used with the value:

• $Scope - this variable will be replaced with the name of the Analysis scope when the
netlist file is created.
• $Model - this variable will be replaced with the name of the MAST_MODEL
property attached to the selected design.
Note
The location supplied must be a valid location to which the client machine has access; if
the location cannot be found, an error will be generated and the export terminated.
Mast Model Properties

Mast.model.property
The name of the property on the component that indicates the MAST MODEL to be
used in the netlist. This may be a space separated list of properties with precedence
given to the foremost in the list.
Mast.model.property=MAST_MODEL

February 2016
Saber Integration
Saber Configuration
Mast.wireModel.name
If there is no model property specified on a wire the model named here will be used
instead.
Mast.wireModel.name=WIRE_V1
Mast.wireModel.pins
The name of the pins on the wire model to be used with the exported netlist.
Failure to specify to distinct pins will cause an invalid netlist to be formed.
Mast.wireModel.pins=p m
Mast.pin.property
The name of the property on the pin that indicates the MAST PIN to be used in the
netlist. This may be a space separated list of properties with precedence given to the
foremost in the list.
Mast.pin.property=PN
Ignore Properties
Ignore.component.with.model
This allows any component with the given mast model to be ignored during netlisting (It
will be replaced by a splice in the netlist ). This may be a space separated list.
e.g. Ignore.component.with.model=wire will ignore any components with the mast
model set to be 'wire'
Ignore.component.with.model=
Ignore.component.with.property
This allows any component with the given ECAD property to be ignored during
netlisting ( It will be replaced by a splice in the netlist ). This may be a space separated
list.
e.g. Ignore.component.with.property=ignore will ignore any components with a
property named 'ignore' regardless of its value.
Ignore.component.with.property=
Identifier Properties
Identifier.max.size=

February 2016
Saber Integration
Saber Configuration
This allows the maximum length of any identifiers in the netlist to be set. This must be a
positive integer value. Recommended setting is 32, smaller settings may prevent the
netlister generated unique identifiers.
Identifier.max.size=32
Identifier.translation.hints
This allows ECAD identifiers that require translation to have translations indicated.
Identifiers are translated when the netlister encounters a character in the ECAD name
that the Saber simulator would not permit. Hints must be space separated pairs
specifying the translatable character or sequence of characters and the transation that
should occur.
e.g. Identifier.translation.hints=+ plus would hint that the + character in
an ecad name should be substituted for the word plus in the netlist.
Note
Hints may take the form of regular expressions and will be used as possible within the
Identifier.max.size constraint. Default translations for space, + and - are present in the
exporter but may be overridden here.
Identifier.translation.hints=
Parameters Properties
Parameters.obtain.all
If this is set to true all properties on all components will be exported as Saber
parameters.
Parameters.obtain.all=false
Parameters.obtain.component.all
If this is set all the properties of a component with any of these property names will be
exported as Saber parameters, including the named properties. If the named properties
are not to be exported then they should be prefixed with a *. This may be a space
separated list.
e.g. Parameters.obtain.component.all=MAST_MODEL *SABER_ALL would indicate
that any component with a MAST_MODEL property or SABER_ALL property should
export all of its properties as Saber parameters excluding the SABER_ALL property.
Parameters.obtain.component.all=

February 2016
Saber Integration
Saber Configuration
Parameters.obtain.component.prefix
If a component's ECAD property has one of the given prefixes it will be exported in the
Saber netlist as a parameter. May be a space-separated list.
Parameters.obtain.component.prefix=SABER_
Parameters.obtain.component.suffix
If a component's ECAD property has one of the given suffixes it will be exported in the
Saber netlist as a parameter. May be a space-separated list.
Parameters.obtain.component.suffix=_SABER
Property Value Substitution

Mapping Enumerations
Mapping enumerations map the values of properties on the ECAD component to new values
suitable for Saber interpretations. For example, using a mapping enumeration it is possible to
map a wire gauge code such as 000 to a value the Saber model will understand such as g000.
Mapping.enumerations
This is a space separated list of all the enumerations available to the netlister.
i.e. Mapping.enumerations=enum1 enum2 specifies to enumerations enum1 and enum2
that are available to the netlister
Mapping.enumerations=
Enumeration.<enumerationName>.properties
This is a comma delimited list of the properties to which an enumeration may be

applied. Property names may make use of regular expressions to easily encompass
multiple properties i.e. Enumeration.enum1.properties=GAUGE states that
enumeration enum1 may be applied to any instance of the GAUGE property.
Enumeration.enum1.properties=.*GAUGE.* states that enumeration enum1 may be
applied to any property that contains GAUGE in its name ( so WIRE_GAUGE,
GAUGE_CODE and AGAUGEPROPERTY would all match )
Enumeration.<enumerationName>.properties=
Enumeration.<enumerationName>.models

February 2016
Saber Integration
Saber Configuration
This is a space-delimited list of the Saber models for which this enumeration is valid.
Model names may make use of regular expressions to easily encompass multiple
models.
i.e. Enumeration.enum1.models=WIRE_V1 WIRE_V2 WIRE_V3 states that the
enumeration is valid for wire models v1, v2 and v3.
Enumeration.enum1.models=WIRE_V.? states that enumeration enum1 may be applied
to any wire_v<char> model.
Enumeration.<enumerationName>.models=
Enumeration.<enumerationName>.keys
This is a space delimeted list of the initial values of the property on the ecad component
that indicate a substitution should take place.
i.e. Enumeration.enum1.keys=000 00 0 1 2 3 4 5 6 7 states that if any of the listed values
are found on a property substitution should be attempted.
Enumeration.<enumerationName>.keys=
Enumeration.<enumerationName>.<enumerationKey>.value
This specifies the value that should be substituted for the key defined above i.e.
Enumeration.enum1.000.value=g000 states that 000 should be substituted with g000
whenever the substitution attempt is made.
Enumeration.<enumerationName>.<enumerationKey>.value=
Mapping String
Mapping strings map the names and values of properties on the ECAD component to new
values suitable for Saber interpretations.
For example, using a mapping string it is possible to map a property such as GAUGE=01 to
WIRE_GAUGE="001" when exported in the Saber netlist. These mappings are identified by
mast model and property name.
Mapping.String.models
A space delimeted list of the models for which mapping strings exist which may not be
regular expressions.
Mapping.string.models=
Mapping.string.<modelName>.mappings=

February 2016
Saber Integration
Saber Configuration
A space delimeted list of the mappings that are applicable to this model i.e.
Mapping.string.wire_v1.mappings=lengthMapping wireSizeMapping
wireSpecMapping
Mapping.string.<modelName>.mappings=
Mapping.string.<mappingName>.property=
The name of the property this mapping string acts upon

Mapping.string.<mappingName>.property=
Transform examples
For example "valueTransform=test" would replace the identified value with
test
"valueTransform=.*,"\0"" would quote the whole value.
Mapping.string.<mappingName>.propertyTransform=
Either a regular expression + replace string to be executed upon the property name or a
fixed string that is substituted. i.e propertyTransform=text would be interpreted as a
fixed string substitution.
propertyTransform=regexp,replace would attempt to map interpret the value as a
regular expression using regex and then replace the value using the replace regex string.
Mapping.string.<mappingName>.propertyTransform=
Mapping.string.<mappingName>.valueTransform=
Either a regular expression + replace string to be executed upon the property value or a
fixed string that is substituted. i.e valueTransform=text would be interpreted as a fixed
string substitution valueTransform=regex,replace would attempt to map interpret the
value as a regular expression using regex and then replace the value using the replace
regex string.
Mapping.string.<mappingName>.valueTransform=
Exclusion Properties
remove.property.with.name=
A space-separated list or properties to be removed from the netlist.

remove.property.with.name=MY_FIRST_PROP MY_SECOND_PROP
This example would remove all instances of the properties MY_FIRST_PROP and
MY_SECOND_PROP from the netlist.

February 2016
Saber Integration
Exporting to Saber (Saber Integration)
remove.property.with.value=
A space-separated list of property-value pairs. Properties with the specified values will
be removed from the netlist.
remove.property.with.value=MY_PROP a MY_PROP b
This example would remove all instances of the MY_PROP property with a value of
a or b.
remove.properties.with.value=
A space-separated list of values. All properties with a value appearing in the list will be
removed from the netlist.
remove.properties.with.value=OPT1 OPT2
This example would remove all instances of any property with a value of OPT1 or
OPT2.
Exporting to Saber (Saber Integration)

To export to Saber, follow the steps below:
If you are exporting a design as a Saber Model Template Definition, there are a number of
prerequisites required to ensure that the netlist is exported correctly.
See “Saber Model Template Definitions” on page 353 for more information. Note also that this
option is only available to users operating Capital Analysis as part of a Capital-based flow.
Procedure
2. Select Saber Design Netlist, then click Next.
3. Check Invoke Saber on netlist if you want to launch the Saber application upon
generation of the netlist.
4. Click Browse and choose a location and file name for the export file.
5. Click Save from the save dialog.
6. Click Next to complete the export, then click Close.
If the Invoke Saber on netlist option was selected at step 3, Saber will be launched
following the generation of the netlist.

February 2016
Saber Integration
Saber Model Template Definitions

Capital Analysis supports the export of a design as a Saber Model Template Definition,
generating the exported netlist in the appropriate format for Saber Models, and passing
properties assigned to the design or its components as parameters of the exported model.
The export of the design is performed in the same way as exporting a Saber Netlist (see
“Exporting to Saber (Export Netlist)” on page 260 for more information), but a number of
prerequisites must be satisfied before a design can be successfully exported as a Saber model.
Note
This functionality is only available to users operating Capital Analysis within a Capital-
based flow.
• A design must have a MAST_MODEL property assigned to identify it as a Saber Model

Definition.
Note
The name of the MAST_MODEL property can be overriden within the
SaberNetlister.properties file (located in the %Analysis%\Resources\Resources
directory. Locate the line that reads: Mast.model.property=MAST_MODEL and replace
MAST_MODEL with a new value of your choice.
The property is assigned within your ECAD tool using the following method:
a. Navigate to the appropriate scope within the project tree, and expand the scope until
the relevant design is visible.
b. Right-click on the design and select Edit...
c. The Edit Diagram dialog is displayed; click the New... button beneath the
Properties list.
d. In the Property Name field, enter MAST_MODEL, then click OK. Back on the Edit
Diagram dialog, the Property list will display the newly created property and will
offer the option to enter a value for the property; leave the Value field blank and
click OK.
• Any nets that will be exposed as ports in the exported Saber model must be assigned a
SABER_PORT property. This, again, is performed within your ECAD tool:
a. Right-click on the appropriate component and select Properties...

b. The Edit Properties dialog will be displayed. Click the New... button beneath the
Properties list.
c. The New Property dialog is displayed; enter SABER_PORT in the Property Name
field, then click OK.

February 2016
Saber Integration
d. Back on the Edit Properties dialog, the new property will have been added to the
Properties list. When the Saber Netlist is generated, the value for this property will
be taken as the name for the pin on the Saber model, so enter the correct name into
the Value field.
e. Leave the other settings for the property at their defaults and click OK.
• Saber Model Template parameters are defined by assigning properties to either the
diagram or components, which will then be converted to model parameters when the
netlist is exported. All properties attached in this way must include a SABER_PROPERTY
prefix, followed by the name of the parameter.
Note
The value used for the prefix can be overridden within the SaberNetlister.properties file
(located in the %Analysis%\Resources\Resources directory. Locate the line that reads:
Parameters.obtain.component.prefix=SABER_PROPERTY_ and replace
SABER_PROPERTY_ with a value of your choice.
The option to use a suffix as well as/instead of a prefix is also supported; locate the line
reading Parameters.obtain.component.suffix=_SABER_PROPERTY and substitute
_SABER_PROPERTY with a value of your choice. In both cases, prefixing the configured
value with an asterisk will result in the prefix and/or suffix being removed from the
parameters as the netlist is exported. For example: *_SABER_PROPERTY will be removed.
For example:
SABER_PROPERTY_MY_PROPERTY=
defines a Mast/Saber parameter named MY_PROPERTY.

Property values can be assigned in two ways:
o A value can be assigned to a property directly, whether the property is attached to a
design or component. For example:
SABER_PROPERTY_RES_1=1.5
defines a property named RES_1 and assigns a value of 1.5.

o A value can be assigned to a property attached to a design, then referenced as a
default by properties attached to components. For example:
The following property is attached to a design:
SABER_PROPERTY_DEFAULT_RES=1.5
and the following properties are attached to a component:

SABER_PROPERTY_RES_1=2
SABER_PROPERTY_RES_2=DEFAULT_RES

February 2016
Saber Integration
In this case, both properties will be exported as parameters of the Saber Model
Template; parameter RES_1 will have a value of 2, while parameter RES_2 will take
the value of the property DEFAULT_RES, 2 in this case.
Note
If you specify the name of a design-level property as a value, that property has to exist on
the design to ensure that the correct value is referenced. If the property does not exist, the
property name entered as a value will be taken literally. In the above example, if the
property SABER_PROPERTY_DEFAULT_RES did not exist on the design, the property
SABER_PROPERTY_RES_2 will be exported as a parameter called RES_2 with a value of
DEFAULT_RES.

February 2016
Saber Integration

February 2016
Appendix I
SystemVision Integration
This section details the integration between Capital Analysis and SystemVision, including the
configuration of SystemVision, project and model attachment and SystemVision Simulation.
The following topics are available:
SystemVision Integration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
SystemVision Integration Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
SystemVision Project Attachment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
SystemVision VHDL Model Attachment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
SystemVision Simulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
SystemVision Integration Overview

Using the standard Capital Analysis Simulator, users are able to pick SystemVision as the target
simulation engine and perform analysis operations inside the SystemVision environment.
Such analysis operations include Parametric Sweep, Monte-Carlo, and Worst-case Analyses
which help the designer filter permutations of system states to get to the real/common problems
that the electrical system can run into. Robust operation can be verified against variations in
input levels, which is very common in noisy areas of the system. Startup/shut-down,
charge/discharge cycles, and network signal integrity are types of analyses that are necessary to
ensure a reliable and safe operation of the system.
The diagram below shows an outline of the analysis flow with SystemVision Integration.
Figure I-1. Outline of the Analysis Flow with SystemVision Integration

February 2016
SystemVision Integration Configuration
A SystemVision model attacher is available for objects in Capital Logic through which VHDL
models can be attached to devices. A design rule check (DRC) verifies model attachments
making sure all needed models have been attached.
Once all models are attached, using the Simulator Tool, SystemVision can be picked from the
simulation type drop down. Different analysis operations can then be performed inside the
SystemVision environment as shown below:
Figure I-2. Choosing SystemVision Simulator
SystemVision Integration Configuration

Following installation, Capital Analysis is configured to run with SystemVision through the
following steps. This configuration needs to be done only once.
Procedure
1. Make sure that SystemVision is installed and that the "Capital SimBridge" component is
enabled in the Analysis Configuration Tool as seen in the screenshot below. Note that

February 2016
SystemVision Project Attachment
enabling this component will not take effect until Capital Logic is restarted.
Note
The configuration tool can be opened by pressing Space Bar and entering Configure.
2. Add the SystemVision Attacher plugin to the plugin home directory

(%Capital_Home%\plugins). The SystemVision Attacher can be found at this location:
https://communities.mentor.com/mgcx/docs/DOC-2387
SystemVision Project Attachment

A project in Capital Logic is mapped to one in SystemVision so that all simulations done in the
same project are collated and mapped to corresponding results in SystemVision. This is
achieved by using the SystemVision attacher as follows:
• Make sure the target project has been created in SystemVision
• In Capital Logic, press Space Bar, enter Custom, and choose Set SystemVision Project.
Use the browser to pick a SystemVision Project of choice (.dproj file)

February 2016
SystemVision VHDL Model Attachment

VHDL models should be attached to objects on the diagram to define their behavior. Not all
objects need a model to be attached. The following classification indicates different types of
objects and their respective need for a VHDL model.
Model required (mandatory):

• Device
• Backshell
Caution
If there is no model attached to one of the objects above, then this will cause netlisting
(simulation) errors in SystemVision.
Model optional:
• Connector: a model can optionally be attached. A contact resistance of 50.0 will be
added for mated pins (mated to device, or to other connector pins). This value can be
overridden by adding a property "contact_resistance" and giving it a value on the
connector.
• Wire: a model can optionally be attached. By default the SystemVision model
EDULIB.WIRE is used on wires unless overridden by an attachment.
Model not needed:

• Ground: considered a ground in SystemVision. If a model is attached it will be ignored.
• Splice: considered a junction point in SystemVision. If a model is attached it will be
ignored.
• Net: considered a net in SystemVision. If a model is attached it will be ignored.
To identify objects missing attachments, the user can run the DRC "SystemVision" (under
'Custom' category). Objects will be listed in the DRC results window.
Note
This DRC can be configured to run in background mode.

February 2016
Figure I-3. Example DRCs
To attach a model to an object, right click on it and choose Custom > SystemVision Properties
Figure I-4. Model Attachment Example
The attacher enables you to perform the following actions:
1. Choose a model from a precompiled SystemVision library or an uncompiled VHDL file

on the disk.
2. Choose the VHDL model Entity and Architecture.
3. Configure mapping of VHDL ports to Capital Logic pins.
• A tooltip over the VHDL port shows its properties.
4. Add parameters to be used on the object in conjunction with its VHDL behavior.
• Default parameters from the VHDL model are automatically added along with any
default values, which can be overridden in the attacher. A tooltip over a parameter
indicates its type.

February 2016
SystemVision Simulation
The SystemVision attacher will add the following properties on the device, indicating the
attachment settings:
1. VHDL_File
• For example, C:\MentorGraphics\VHDL Files\MyVHDLFile.vhd (only if an
uncompiled model was selected in the attacher).
2. VHDL_Model
• <Library_Name><Model_Name>(<Architecture_Name>) for a compiled model.
• <ModelName>(<Architecture_Name>) for an uncompiled model.
3. VHDL_Property_<Property_Name>
• For each VHDL parameter added or overridden in the attacher, a property with the
above name is created. The property value indicates the parameter value used. Note
that for default parameters, which have not been overwritten by the user, no
properties are created.
4. SVPinOrder
• Property added on each pin to indicate which VHDL model terminal this pin is
mapped to.
• If this property is removed off all pins, a property "VHDL_PinOrder" can be used on
the device itself to indicate the mapping. The value for this property is an ordered list
of the device pins that would match the ordered list of terminals in the VHDL file.
So in the Model Attachment Example the terminals in the VHDL file are listed in the
order 'p1 p2' so the VHDL_PinOrder property would have the value 'X Y'.
Once all models are attached and the DRC passes without any errors, scope can be set on the
required design or build list so simulation would be performed on it.
In the Simulator, select SystemVision from the Simulation Type drop down and tap the Play
button.

February 2016
Figure I-5. SystemVision Simulation Example
This will automatically launch SystemVision on the set project and run the simulation. You can
then specify the end time and other parameters needed for simulation.
Figure I-6. Simulation Parameter Specification in SystemVision
Different analysis operations can be chosen from the Multi-Run tab.

February 2016
Figure I-7. Analysis Operations in SystemVision
Results are then shown in SystemVision and propagated back into Capital to change the color of
different components according to their activity and failure conditions.

February 2016
Appendix J
Error Resolution
Please check out the Mentor graphics supportNet site for current FAQ's and trouble shooting.
Could not connect to the database:Could not

load library 'libmysqlclient'.
Product: Capital AQQA: Analysis/AnalysisCommandLineApplicationABC.cpp 181 => could
not connect to the database: Could not load library 'libmysqlclient'.
Solution
The error above, from the Capital AQQA errors file, means that the library libmysqlclient.so
cannot be found or loaded. You need to build this library on your system if you have not done
so.
Here are the instructions:
Please download the MySQL distribution (4.0.20) and configure it with:
configure --without-server --enable-shared
Then type make to build the shared library.
After make is done the library will appear in libmysql/.libs/libmysqlclient.so.
If this library has been built, then you need to ensure that the LD_LIBRARY_PATH includes
the directory where you have placed libmysqlclient.so. If you are still have problems, type the
following command on libmysqlclient.so.
ldd libmysqlclient.so
This will tell you the libraries libmysqlclient.so is dependent on. Please ensure that the location
of these libraries are in the LD_LIBRARY_PATH environment variable also.
Analysis error message: "both supply rail and

batter components are present..."
Product: Capital Analysis, Capital Logic.

February 2016
Error Resolution
Can not run Background Simulation and no simcore.exe is listed in task manager.
Analysis error message: "both supply rail and batter components are present..."
• When Simulator is selected the following messages are displayed:

o ERROR -> no connection to default battery source node. Please add positive
category component or remove all negative category components.
o WARNING -> both supply rail and battery components are present in the schematic.
Recommend using one or other approach.
o WARNING -> please ensure multiple batteries in the schematic are isolated to
ensure correct simulation.
o SERIOUS ERROR -> could not create a valid simulator for schematic 'Design1' of
type 'electrical.qualitative'.
o SERIOUS ERROR -> simulation failure: not running a simulation.
Cause: This may be caused by using a wrong combination of models in the diagram. For
example:
• Battery device is attached to "battery"

• Ground device is attached to "ground_rail"
Solution
Change the device attachments appropriately. For example:
• Battery device to "battery"

• Ground device to "chassis"
Can not run Background Simulation and no

simcore.exe is listed in task manager.
Product: Capital Stress/Analyzer with Japanese OS
Symptoms
• Can not run Background Simulation and no simcore.exe is listed in task manager.
• Schematic diagram is not highlighted in usual background simulation colors of red,
green and blue.
• Capital Analysis tab shows only "Please wait..." and does not change.
Cause: An equivalent Japanese character appears to be used as a delimiter between component
name and pin name. If this delimiter is not consistent between generated design and the netlister
then the problem arises.

February 2016
Error Resolution
Capital Web Naming Service does not invoke due to the lack of port number as a parameter.
Solution
This may be resolved by changing the delimiter to be used and then running Generate Wiring
Diagram again.
Capital Web Naming Service does not invoke

due to the lack of port number as a parameter.
Product: Capital
Symptoms Capital Web Naming Service does not invoke due to the lack of port number as a
parameter. This only occurs on brand new installs on clean machines.
Solution
As a workaround to this issue you should create a shortcut icon of the original
CapitalWebNamingServer.exe. Then add a the port number you wish to use as Capital Web
Naming Service. This can be done by:
1. Right-click on the new short cut that has been created.

2. Select Properties.
3. Select the Shortcut tab.
4. Add the port number to the end of the target line. For example,
was C:\MentorGraphics\Capital\bin\CapitalWebNamingServer.exe,
now C:\MentorGraphics\Capital\bin\CapitalWebNamingServer.exe 11178
5. Use this Shortcut to start the Web Naming Service.
Error message: Destination component

DEV_1{DEV**P1} does not exist in the
component list.
Product: Capital Stress/Analyzer
Product: Japanese OS
Symptoms Generate Wiring Diagram: receiving the following error: Destination component
DEV_1{DEV**P1} does not exist in the component list. Note that in place of the ** there may
be a doublebyte "overline".
Cause: Device "DEV_1" and the Pin "P1" are not correctly associated. This occurs because an
equivalent Japanese character appears to be used as a delimiter between component name and

February 2016
Error Resolution
Error: Unable to obtain a license for feature CHManufact, License request for feature NULL failed
pin name. If this delimiter is not consistent between generated design and the netlister then the
problem arises.
Solution
Resolve by changing the delimiter to be used as follows:
1. Shut down Capital.

2. Open RunTime.properties in the following directory (or the equivalent for your
installation):
C:\MentorGraphics\Capital\Analysis\Capital Analysis_2005.2\resources\resources
(Make a backup copy of this file before opening and modifying it.)
3. Find the following line (or similar) which should be near the top of the file:
# Capital only bridge properties.
java.capital.properties=netsim.bridge.single=false,
analysis.netlist.enableConductorEquiv=true, analysis.AttachProperties.all=true
4. Add the following to the end of that line (be sure to add the leading comma):
, wdg.analysisProperty.separator=<delimiterCharacter>
5. In place of the <delimiterCharacter> use a character that would not be used in the
component nor pin names. For example try using $, ! or \\. An example result of that line
would be:
java.capital.properties=netsim.bridge.single=false,
analysis.netlist.enableConductorEquiv=true, analysis.AttachProperties.all=true,
wdg.analysisProperty.separator=$
6. Save the above file and start Capital again.
7. You MUST now run Generate Wiring Diagrams again so that the new delimiter
(example $) is used.
Error: Unable to obtain a license for feature

CHManufact, License request for feature NULL
failed [mgls_errno 203]
Product: Capital Bridges
Symptoms
• Error: Unable to obtain a license for feature CHManufact, License request for feature
NULL failed [mgls_errno 203]

February 2016
Error Resolution
Error when trying to run casconfig -dsAdmin in DOS Shell.
• Error: Unable to obtain a license for feature CHDesigner, License request for feature
NULL failed [mgls_errno 203]
• MGLS_PKGINFO_FILE is not set
• C:\Mentor\2006.1\mglsclnt does not exist
Cause: The client-side licensing is missing. The licensing exists in <install_dir>\mglsclnt and
this directory does not exist.
Solution
Reinstall WG2006.1. Verify that the mglsclnt directory is created and that the environment
variables MGLS_PKGINFO_FILE and MGLS_DLL are set.
Error when trying to run casconfig -dsAdmin

in DOS Shell.
Product: Capital Analysis, Capital SimCore, Capital Logic
Symptoms Connections.propertiesError when trying to run casconfig -dsAdmin in DOS Shell.
Full error message as follows:
ERROR [PropertiesFile-167] =>

ifstream not open
ERROR [AnalysisProperties-203] =>
could not read the properties file
Exception in thread "main" java.lang.NoClassDefFoundError: uk/co/firstearth/auto
steve/configuration/ConfigurationTool
ERROR [SimCoreApplication-919] =>
could not start the virtual machine
NOTE:
(I) Please check that the class
uk.co.firstearth.autosteve.configuration.ConfigurationToolexists.
(II) Please check that the class method mainexists.
(III) Please check the classpath is correct:
(IV) Please check the <install_location> environment variable is set.
Press any key to continue . . .

February 2016
Error Resolution
Cap Analysis - error message: no 'Quantization Bands' have been specified.
Cause:
The Connections.properties file in the following directory is empty:
C:\MentorGraphics\Capital\Analysis\Capital Analysis_2006.1\resources\resources
Solution
Open the Connections.properties file, enter the following, save the file and the casconfig
program will run.
default=
(Note in the above line to be entered there is nothing after the "=" sign.)
Cap Analysis - error message: no

'Quantization Bands' have been specified.
Product: Capital Analysis, Capital Sim Model
Symptoms When Analysis>Simulator is selected the following message is displayed:
ERROR -> in component P_MY_SW, mode Normal_Operation - no 'Quantization

Bands' have been specified.
Method 'CONTACT11.setResistance()' cannot be used without one.
Please add a QScheme to the component model. This has caused the next error.
ERROR -> in component PW_MAIN_SW, mode Normal_Operation - extra terminator
';' found.
Could be due to missing actions or previous error(s).
Cause: This may be caused by either of:
• The path setting for the model in question not being correct.
For this reason the command Resistance referred to has not been assigned from the
model.
Please see method (A) below.
• An incorrect model has been assigned to the device or the model has been moved.
Please see method (B) below.
Solution
(A) The path for the component model can be confirmed and saved as follows:

February 2016
Error Resolution
OCI.dll The specified module could not be found
1. Select Analysis>Tools>Component Model Builder...

2. Open the model indicated in the Log file (P_MY_SW in this example).
3. Edit>Quantization Bands...
4. Select the item with the problem (resistance in this case). This will list the assumed path
and model (example /Mentor/Switch_0A_15M).
5. Using the folder icon, open and select the model from the path as above or another path
and model if not available.
6. Select Open followed by OK and then Save this setting.
Repeat the above for all other components in the Log file.
Then return to Analysis>Simulator and the program should open and run.
Note that it may take several seconds or up to a minute for the Simulator to open depending
upon your machine environment.
(B) To assign a model to the Device:
1. With the diagram open, select the Device from the Diagram Browser.
2. From the Popup menu select Analysis>Attach...
3. Select the Model, confirm that Terminal Mappings are correct then select OK.
OCI.dll The specified module could not be

found
Product: Capital SimCore, Capital Analysis
Symptoms
• OCI.dll The specified module could not be found.

• Cannot Start the Simulator.
Solution
The PATH variable should include the path to the Oracle bin directory.

February 2016
Error Resolution
The DataSource Admin tab does not appear when launching the Configuration Tool with casconfig
The DataSource Admin tab does not appear

when launching the Configuration Tool with
casconfig -dsadmin
Product: Capital SimCore
Symptoms The DataSource Admin tab does not appear when launching the Configuration Tool
with casconfig -dsadmin.
Solution
The command is case-sensitive. Typing casconfig -dsAdmin will make the DataSource Admin
tab available.
Unable to connect to the AutoSteve Database

Product: Capital AutoSteve, Capital Bridges
Symptoms
• Unable to connect to the AutoSteve Database.

• Settings appear to be correct.
• SQL is running on the right server.
Solution
Ensure that the mysql daemon is up and running. If not, re-start the mysql daemon.
Unable to import a database dump of Capital;

"the objects were exported by SYS, not by
you"
Product: Capital
Symptoms
• Unable to import a database dump of Capital
• Warning: the objects were exported by SYS, not by you
Solution
If you are using the following script for importing the data then you may need to change the
script.

February 2016
Error Resolution
Standard import script from a DOS prompt:

imp file=*****.dmp
fromuser=hse,matprice,labour,dessysti,projeng,q527,q539,jobctrl,custom,capital
touser=hse,matprice,labour,dessysti,projeng,q527,q539,jobctrl,custom,capital rows=y
indexes=y grants=y constraints=y
New Modified import script from a DOS prompt:
imp file=*****.dmp
fromuser=sys,hse,matprice,labour,dessysti,projeng,q527,q539,jobctrl,custom,capital
touser=sys,hse,matprice,labour,dessysti,projeng,q527,q539,jobctrl,custom,capital rows=y
indexes=y grants=y constraints=y

February 2016
Error Resolution

February 2016
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Index
Capital SimProject
Index
—A— menus, 101

Activity, 250 Capital SimProve
Add menus, 132
concurrency groups, 225 overview, 20, 123
control functions, 99 Capital SimScript
events, 223 overview, 21
excluded functions, 100 reports, 104
output functions to features, 98 Capital SimStress
project features, 98 overview, 21, 135
states, 222 Capture
watches, 61 circuit designs, 19
Analysis Change
transient, 21 administrator password, 302
Analyze password, 302
script analysis, 104 Check
stress analysis, 136 QSchemes, 234
Append, 70 Checking, 267
Assign Child output functions, 93
projects, 245 Circuits
Attach capturing design, 19
component models, 199 Color options, 272
control functions, 203 Combinations
output functions, 203 inserting, 86
Automation options, 274 Comments
—B— editing, 229
Back propagation, 143 Company preferences, 307
Batteries, 329 Component behavior
Behavior modelling type, 164 defining, 172
Build Component Builder
QSchemes, 233 menus, 212, 213
overview, 160
—C— wizard, 194
Capital Analysis Component categories, 279
overview, 17 selecting, 163
Capital SimBridge, 40, 88, 126, 138 Component interfaces
Capital SimCertify defining, 164
menus, 76, 80 Component library, 198
Overview, 79 Component models
overview, 20 attaching, 199

February 2016
creating, 162 QScheme bands, 236

shared objects, 177 resistancies, 169
Component structures state properties, 222
defining, 167 stress styles, 147
Components voltage algorithms, 146
inserting, 87 Delete
parameters, 44 events from scenario, 48
Concurrency groups locks, 34
adding, 225 objects in Structure Editor, 171
Configure stress styles, 153
data sources, 293 Dependency Editor
Console, 266 menus, 215
Construct Describe
models, 18 system functionality, 19
Control functions, 95 Description Editor, 212
adding, 99 Design description import wizard, 259
attaching, 203 Digital multimeter, 52
Create Diode arcs, 170
component model, 162 Dynamic simulation
FMEA scenarios, 81 information windows, 63
projects, 98 starting, 60
SCA reports, 126 Dynamically generated components, 339, 345
scripts, 107
stress styles, 151 —E—
Current Edit
defining algorithms, 146 comments, 229
events, 230
—D— FMEA reports, 70
Data sources objects, 29
backing up, 301 preferences, 307
configuring, 293 QSchemes, 238
populating, 300 states, 231
transferring, 301 stress styles, 152
updating, 301 Embed
database dependency, 267 hierarchical components, 180
Databases hierarchical model, 180
dependency check, 267 VHDL-AMS models, 187
navigating, 28 Errors
Define reports, 261
component behavior, 172 structure errors, 232
component interfaces, 164 Events
component structure, 167 adding, 223
current algorithms, 146 defining conditions, 224
event conditions, 224 deleting from scenario, 48
failure modes, 174 editing, 230
power algorithms, 146 moving, 224

February 2016
recording a sequence, 47 pausing, 89

sequence, 85 running, 87
types, 223 Unresolved Scenario Builder, 84
Excluded functions FMEA verification, 20
adding, 100 Folders
Export exporting, 34
FMEA reports, 73 importing, 35
folders, 34 Font options, 273
netlists, 259 Formats
overview, 327 script files, 108
SCA reports, 128 Frozen shared objects, 22
state machines, 226 Fuse arcs, 170
stress styles, 153
External model management, 281 —G—
Grid settings, 228
—F—
Failure, 55 —H—
Failure modes Header
defining, 174 FMEA reports, 71
setting, 186 Hide
Failures states, 223
modes, 85 Hierarchical components
simulating, 50 embedding, 180
Features —I—
adding output functions, 98 Import
Features (Capital SimProject), 92 folders, 35
Feedback Coloring, 54 overview, 327
Filter state machines, 226
results, 72 stress styles, 153
Find Input dialog, 264
objectsSearch Insert
objects, 31 combinations, 86
text in file, 263 components, 87
FMEA Editor, 76
menus, 76 —L—
FMEA reports, 70 Local expressions, 45
appending, 70 Locks
editing, 70 deleting, 34
exporting, 73
header, 71 —M—
Manage
printing, 73
external models, 281
simulating records, 89
objects, 25
viewing, 70, 72
Menus, 76
FMEA scenarios
Capital SimCertify, 76, 80
creating, 81
Capital SimProject, 101
dialog, 85

February 2016
Capital SimProve, 132 Options

Component Builder, 212, 213 automation, 274
Dependency Editor, 215 color, 272
Object Manager, 26 external model management, 281
QScheme Builder, 239 font, 273
SCA Tool, 132 model search path, 278
Simulation Tool, 55 modeling language, 280
State Builder, 218 netlist, 281
Structure Editor, 214 other, 279
Model search path options, 278 qualitative, 279, 280
Modeling language options, 280 report, 275
Models RPN defaults, 274
constructing, 18 Saber, 280
Modes simulation, 275
failures, 85 simulation engine, 280
Move simulation highlighting, 275
events, 224 simulator settings, 281
objects in Structure Editor, 171 state builder, 288
states, 222 structure editor, 287
syntax highlighting, 271
—N— Order
Name QSchemes
pins, 172 QSchemes
Navigate ordering, 238
databases, 28 results, 72
Netlist options, 281 Other options, 279
Netlists Output conditions
exporting, 259 viewing, 63
—O— Output functions, 92
Object Manager, 25 adding features, 98
menus, 26 attaching, 203
saving printable files, 33 Override
Objects numeric settings, 46
editing, 29 Override files, 119
finding, 31 Overrides (numeric), 45
managing, 25 Overview
properties, 31 Capital Analysis, 17
renaming, 35 Capital SimCertify, 20, 79
reusing, 29 Capital SimProve, 20, 123
searching, 31 Capital SimScript, 21
Open Capital SimStress, 21, 135
objects, 265 Component Builder, 160
QSchemes Simulation Tool, 39
QSchemes State Builder, 217
opening, 238

February 2016
—P— defining bands, 236

Parameters editing, 238
components, 44 overview, 233
Parent, 250 saving, 243
Passwords Qualitative options, 279, 280
changing, 302 Quantization bands, 176
Pause Quantization schemes
FMEA scenarios, 89 overview, 233
recording sequence, 49
Pins —R—
Record
naming, 172
sequence of events, 47
Plane, 250
Reference
Plugin, 251
embedded objects, 186
Pop
Regular expressions, 105, 141
states, 223
Rename
Power
objects, 35
defining algorithms, 146
Replace
Power nodes
text in file, 263
setting, 46
Report options, 275
Power pins, 204
Reports
Preferences, 307
Capital SimScript, 104
Print, 265
Resistances
FMEA reports, 73
defining, 169
Progress dialog, 266
Resize
Projects
states, 222
adding features, 98
Results
assigning, 245
filtering, 72
creating, 98
ordering, 72
saving, 100
Reuse
Properties
objects, 29
dialog, 264
Robust netlisting, 76, 79, 90, 136
viewing, 31
RPN default options, 274
Property watches, 56
Run
Prune
FMEA scenarios, 87
SCA reports, 128
simulations, 49
Push
stress analysis, 136
states, 223
—Q— —S—
Saber
QScheme Builder
options, 280
menus, 239
Save
wizard, 242
objects, 265
QSchemes
printable files, 33
building, 233
projects, 100
checking, 234
QSchemes, 243

February 2016
SCA reports running, 49

creating, 126 Simulations highlighting options, 275
exporting, 128 Simulations options, 275
pruning, 128 Simulator settings, 281
viewing, 130 Size
SCA Tool wires, 143
menus, 132 Specify
Scenarios power pins, 204
builder for unresolved scenarios, 84 terminals, 168
creating, 81 Start
pausing, 89 dynamic simulation, 60
running, 87 State Builder
Script analysis, 104 menus, 218
Scripts options, 288
creating, 107 overview, 217
file format, 108 State machines
override files, 119 exporting, 226
using files, 118 importing, 226
Select States
component categories, 163 adding, 222
Self modeling components, 335 defining properties, 222
Sequence editing, 231
events, 85 hiding, 223
Set moving, 222
component parameters, 44 popping, 223
failure modes for embedded objects, 186 pushing, 223
power nodes, 46 resizing, 222
Shared objects Stress analysis
component models, 177 running, 136
frozen, 22 Stress styles
Short, 55 creating, 151
Short to battery, 204 defining, 147
Short to ground, 204 deleting, 153
Simulate editing, 152
displays, 51 exporting, 153
FMEA record, 89 importing, 153
with failures, 50 Structure Editor
Simulation, 249 deleting objects, 171
Simulation engine options, 280 menus, 214
Simulation Tool, 249 moving objects, 171
menus, 55 options, 287
overview, 39 Supply rails, 329
Simulation type, 88, 126, 138 Syntax highlighting options, 271
Simulation types, 40 Systems
Simulations describing functionality, 19

February 2016
—T—
Terminals
specifying, 168
Tooltip, 251
Transfer
data sources, 301
Transient analyis, 21
Transient graphs, 56
Troubleshooting, 317
—U—
Unresolved Scenario Builder, 84
Update
data sources, 301
—V—
Variables, 251
Verification
FMEA interactive, 20
VHDL-AMS models, 187
View
FMEA reports, 70, 72
object properties, 31
output conditions, 63
property watches, 56
SCA reports, 130
transient graphs, 56
Viewing Embedded Component Properties, 63
Voltage
defining algorithms, 146
—W—
Watches
adding, 61
Wires
sizing, 143
Wndows
simulation information, 63

February 2016

February 2016
Third-Party Information
For full information on open source and third-party software that may be included in Capital products see the 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.
END-USER LICENSE AGREEMENT (“Agreement”)

This is a legal agreement concerning the use of Software (as defined in Section 2) and hardware (collectively “Products”)
between the company acquiring the Products (“Customer”), and the Mentor Graphics entity that issued the corresponding
quotation or, if no quotation was issued, the applicable local Mentor Graphics entity (“Mentor Graphics”). Except for license
agreements related to the subject matter of this license agreement which are physically signed by Customer and an authorized
representative of Mentor Graphics, this Agreement and the applicable quotation contain the parties’ entire understanding
relating to the subject matter and supersede all prior or contemporaneous agreements. If Customer does not agree to these
terms and conditions, promptly return or, in the case of Software received electronically, certify destruction of Software and all
accompanying items within five days after receipt of Software and receive a full refund of any license fee paid.
1. ORDERS, FEES AND PAYMENT.

1.1. To the extent Customer (or if agreed by Mentor Graphics, 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. THIRD PARTY CLAIMS.

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. TERMINATION AND EFFECT OF TERMINATION.
11.1. If a Software license was provided for limited term use, such license will automatically terminate at the end of the authorized
term. Mentor Graphics may terminate this Agreement and/or any license granted under this Agreement immediately upon
written notice if Customer: (a) exceeds the scope of the license or otherwise fails to comply with the licensing or confidentiality
provisions of this Agreement, or (b) becomes insolvent, files a bankruptcy petition, institutes proceedings for liquidation or
winding up or enters into an agreement to assign its assets for the benefit of creditors. For any other material breach of any
provision of this Agreement, Mentor Graphics may terminate this Agreement and/or any license granted under this Agreement
upon 30 days written notice if Customer fails to cure the breach within the 30 day notice period. Termination of this Agreement
or any license granted hereunder will not affect 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.
Rev. 151102, Part No. 265968

Capital Analysis User PDF

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Capital Analysis User PDF

Transféré par

Droits d'auteur :

Formats disponibles

Capital® Analysis™ for Capital®

© 2016 Mentor Graphics Corporation

Mentor Graphics Corporation

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

Capital Analysis for Capital User Guide, 2015.1 3

4 Capital Analysis for Capital User Guide, 2015.1

Audit Report Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Capital Analysis for Capital User Guide, 2015.1 5

6 Capital Analysis for Capital User Guide, 2015.1

Capital Analysis for Capital User Guide, 2015.1 7

Basic Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

8 Capital Analysis for Capital User Guide, 2015.1

Structure Error Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

Capital Analysis for Capital User Guide, 2015.1 9

10 Capital Analysis for Capital User Guide, 2015.1

To create an external model object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

Capital Analysis for Capital User Guide, 2015.1 11

Your workstation slows down after a few months. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320

12 Capital Analysis for Capital User Guide, 2015.1

Capital Analysis for Capital User Guide, 2015.1 13

Figure 3-1. Simulation Feedback Coloring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Capital Analysis for Capital User Guide, 2015.1 14

Table 2-1. Delete Lock Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

15 Capital Analysis for Capital User Guide, 2015.1

16 Capital Analysis for Capital User Guide, 2015.1

Overview of Capital Analysis

Capital Analysis for Capital User Guide, 2015.1 17

18 Capital Analysis for Capital User Guide, 2015.1

• Linking function to structure

Capturing the Circuit Design

Describing the System's Functionality

Functions are created as part of project models in Capital SimProject.

Linking Function to Structure

Capital Analysis for Capital User Guide, 2015.1 19

Introduction to Capital SimCertify

Introduction to Interactive FMEA Verification

Introduction to Capital SimProve

20 Capital Analysis for Capital User Guide, 2015.1

Introduction to Capital SimScript

Introduction to Capital SimStress

Introduction to Transient Analysis

Capital Analysis for Capital User Guide, 2015.1 21

Frozen Shared Objects in Capital

Using Different Numeric Simulators with

Enabling Transient Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

22 Capital Analysis for Capital User Guide, 2015.1

Switching to SystemVision Transient and VHDL Support . . . . . . . . . . . . . . . . . . . . . . . 24

Enabling Transient Support

Disabling Transient Support

Switching to Berkeley SPICE

Capital Analysis for Capital User Guide, 2015.1 23

Switching to SystemVision Transient and VHDL

Switching to SimTransient VHDL Support

24 Capital Analysis for Capital User Guide, 2015.1

Capital Analysis for Capital User Guide, 2015.1 25

Object Finder Locking Objects

Object Manager Menus

26 Capital Analysis for Capital User Guide, 2015.1

Lock: Applies a database lock to the selected object .

Netlist Scope Management: Allows the unlocking of a design’s scope.

Capital Analysis for Capital User Guide, 2015.1 27

Reuse and Editing of Objects Locking Objects

Navigating the Database