Professional Documents
Culture Documents
Setting Up Libraries For ELDO Simulation With HyperLynx Analog
Setting Up Libraries For ELDO Simulation With HyperLynx Analog
Setting Up Libraries For ELDO Simulation With HyperLynx Analog
S SM
Table of contents________________________________________________________________ 1
Introduction ____________________________________________________________________ 1
Terms and Definitions ____________________________________________________________ 2
Library Data Organization _________________________________________________________ 2
Property and Simulation Attribute Categories __________________________________________ 3
DxDesigner Symbol Properties Directly Used by HyperLynx Analog ________________________ 4
Common ELDO Simulation Attributes ________________________________________________ 6
Element Type Specific Property Information ___________________________________________ 8
Subcircuit Instances (Macromodels) ________________________________________________ 15
Conclusion ___________________________________________________________________ 16
Appendix - Considerations for Defining Properties for Use in Simulation ____________________ 17
Introduction
This document describes how to set up libraries for simulation with HyperLynx Analog. It describes the
requirements for integrating schematic design information with simulation, and also explains optional
information that may be used for more advanced analyses.
HyperLynx Analog provides a great deal of flexibility for defining the simulation information, so in many
cases there may be more than one way to set up the library elements. This document describes the
options, and outlines the considerations in choosing one option over another.
This document addresses the property information relevant to the Eldo simulation engine. The information
for the HyperLynx Analog Simulation Engine is comparable, but differs in the details.
The information in this document is applicable to HyperLynx Analog and DxDesigner through the
EE2007.5 and PADS 9.0 releases. Future releases may change the requirements for setting up the
libraries as HyperLynx Analog evolves.
Page 1 of 18
Copyright 2009 Mentor Graphics Corporation
Trademarks that appear in Mentor Graphics product publications that are not owned by Mentor Graphics are
trademarks of their respective owners.
Definition
Simulation
Attributes
These are attributes attached to simulation element instances. They represent the
information in the simulation netlist, after it has been derived from the Properties.
There may or may not be a one-to-one correspondence of properties to simulation
attributes. For a more detailed description of this, please see the Property and
Simulation Attribute Categories section and the Appendix - Considerations for
Defining Properties for Use in Simulation.
Properties
These are the properties as attached to the schematic symbols. This represents the
information that is placed on the design by the user (either explicitly or as part of
placing the symbol).
Some properties are used by simulation, others are not (for example, they may be
used for PCB layout).
The properties that are used by simulation will likely map to one or more simulation
attributes as discussed below.
The choice of where to place the simulation information depends on several factors, and the following
bullets can be used to help determine where the best location in a particular environment is:
If using DxDataBook, and placing symbols from the parts there, then putting all of the
parametric information in DxDataBook will enable more sophisticated searches.
If not using DxDataBook, then putting the information in a PDB entry will facilitate sharing
symbols among similar parts (for example all NPN BJTs can use the same symbol) and thus
reducing maintenance.
If users place by symbol, then putting the information on the symbol definition will enable the
users to place fully populated symbols. This approach has the drawbacks that it requires
creation and maintenance of a significantly larger symbol library. Also, the symbol definitions
cannot be shared.
Placing simulation property information on specific symbol instances can be used with any of
the above approaches and is typically done by the analog design engineer who wishes to
extend or modify some of the simulation characteristics for this specific design or analysis.
Page 2 of 18
Required These must appear on the symbol in order for the symbol to be processed
properly by HyperLynx Analog.
Optional These are optional properties that are relevant for PCB design, and can be
placed on the symbol to provide additional simulation information, or to control the behavior
of this element for particular analyses (for example for statistical or noise analysis).
Advanced These are optional properties that can be relevant for PCB design that probably
wouldnt be used by most users, but can provide sophisticated simulation behavior.
Similarly to the IC specific attributes, the simulators support a number of element types that dont
necessarily map to physical parts (such as the controlled sources). These types wouldnt be used directly
in a PCB design, but can be used when creating schematics for building macromodels.
The document below will enumerate the properties and simulation attributes for the various element
types, and indicate the category to which each belongs.
Page 3 of 18
Required/
Optional
Comments
Prefix
Required
This property is used to tell HyperLynx Analog the type of this element.
The value of this property determines the other properties that HyperLynx
Analog will use for this symbol.
ID
Required
(Generated)
This is the unique identifier for this particular element. It is not a separate
property; the identifier is generated by HyperLynx Analog when creating
the simulation netlist.
HyperLynx Analog uses:
1. The Name property of the symbol.
2. The block value of the Reference Designator if the Name is blank
3. The instance name of the symbol if the previous values are
blank.
The 2007.3 and 2007.5 versions of HyperLynx Analog ignore the instance
value of the reference designator as placed by the packaging or REFDES
utilities.
Pin Order
Required
This property defines the order in which the Pins should be written to the
netlist.
The contents of this property are the names of the Pins in the order in
which they should be written to the netlist.
The netlister then writes the nets connected to each of the pins in order in
the netlist.
Order
Required
Page 4 of 18
Required/
Optional
Comments
Value
Required
based on
Type
This is the value for the element. It is used with passive elements (such as
resistors, capacitors, inductors) that generally dont have models
associated with them.
It is required for those elements.
Model
Required
based on
Type
This is the name of the SPICE simulation model to use for this element. It
must match the name of the model contained in the library referenced
using the Spice Lib Name and Spice Lib Path properties.
It is required for elements that require models, optional if the model is
optional, and should not be used if the element doesnt have a model.
Spice
Subckt
Required
based on
Type
This is also the name of the SPICE simulation model. It must match the
value of the Model property. It is used for certain functions in HyperLynx
Analog (such as the Simulation Properties feature).
It is required for subcircuit macromodels.
Spice Lib
Name
Required
based on
Type
This is the name of the file containing the SPICE model. This is just the
name without any filesystem path.
It is specified as a .lib or a .mod filename.
It is required for all elements that require models.
Spice Lib
Path
Required
based on
Type
This is the path to the directory containing the library that holds the SPICE
model. It should not contain the file name.
Spice Lib Path and Spice Lib Name are concatenated together to form
the fully qualified path to the SPICE library that contains the referenced
model.
It is required for all elements that require models.
No Pins
Optional
If defined, and not set to 0 or false (case-insensitive), the netlister will not
write the nets out using the Pin Order information.
This is typically used when the Order property is used to define the pin
information.
Simulation
Model
Required
VHDL
VHDL_AMS
VERILOG
VERILOGA
Page 5 of 18
Required/
Optional
Comments
Exclude
Optional
Yes The element is excluded from the simulation, and its pins
are not connected in any way. It behaves as an OPEN circuit.
Shunt The element is excluded from the simulation, and the pins
are connected together as a SHORT circuit.
Allowed
Values
Real
Values
Notes
Page 6 of 18
Allowed
Values
Real
Values
Notes
Used to define a temperature delta for this device from the rest of
the circuit. Thus the temperature used for this device will track the
circuit temperature and is another way to model heating effects.
TEMP and DTEMP are mutually exclusive. If both are specified, the
last one is utilized.
TC1, TC2,
TC3
Real
Values
Allowed
Values
0 or 1
Notes
Nonoise
No value
Noise
1 (or
sometimes 0)
Fmin
Real Values
Fmax
Real Values
Nbf
Real Values
Page 7 of 18
Property Value
Prefix
Pin Order
Order
Recommended:
Model= Value$ TC1= TC2= TC3= TEMP= DTEMP= ELDO_PARAMS$
Minimum:
Value$
Value
Property
Name
Notes
Model
A model to use for this capacitor. For example for capacitors in Eldo, statistical
information is defined in the model.
IC
Sets the initial guess for the voltage across the capacitor prior to a transient
analysis. To use this option, the UIC parameter must also be present in the .TRAN
statement.
TC1, TC2,
TC3
Page 8 of 18
Notes
TEMP,
DTEMP
Notes
ELDO_PARAMS
Entered as needed.
e.g.
STATISTICAL=1 NOISE=1
STATISTICAL
There are other advanced properties that could be added, please refer to the Eldo reference manual
for more information. This description is intended to provide guidance, and should provide examples
to allow advanced users to harness the descriptive capabilities that Eldo provides.
Table 6 INDUCTOR Minimum Required Properties:
INDUCTOR Minimum Required Properties
Property
Name
Property Value
Prefix
Pin Order
Order
Recommended:
Model= Value$ IC= TC1= TC2= TC3= R= TEMP= DTEMP= ELDO_PARAMS$
Minimum:
Value$
Value
Property
Name
Notes
Model
A model to use for this capacitor. For example for capacitors in Eldo, statistical
information is defined in the model.
IC
Sets the initial guess for the current through the inductor prior to a transient
analysis. To use this option the UIC parameter must also be present in the .TRAN
statement.
Page 9 of 18
Notes
TC1, TC2,
TC3
TEMP,
DTEMP
Notes
ELDO_PARAMS
Entered as needed.
e.g.
STATISTICAL=1
STATISTICAL
There are other advanced properties that could be added, please refer to the Eldo reference manual
for more information. This description is intended to provide guidance, and should provide examples
to allow advanced users to harness the descriptive capabilities that Eldo provides.
Table 9 RESISTOR Minimum Required Properties:
RESISTOR Minimum Required Properties
Property
Name
Property Value
Prefix
Pin Order
Order
Recommended:
Model= Value$ TC1= TC2= TC3= TEMP= DTEMP= ELDO_PARAMS$
Minimum:
Value$
Value
Property
Name
Notes
Model
A model to use for this resistor. For resistors in Eldo, statistical information is
defined in the model.
Page 10 of 18
TC1, TC2,
TC3
TEMP,
DTEMP
Notes
ELDO_PARAMS
Entered as needed.
e.g.
STATISTICAL=1 NOISE=1
STATISTICAL
NONOISE
NOISE
FMIN
FMAX
NBF
KF
AF
WEEXP
LEEXP
FEXP
There are other advanced properties that could be added, please refer to the Eldo reference manual
for more information. This description is intended to provide guidance, and should provide examples
to allow advanced users to harness the descriptive capabilities that Eldo provides.
Table 12 DIODE Minimum Required Properties:
DIODE Minimum Required Properties
Property Name
Property Value
Prefix
Pin Order
Order
Recommended:
Model$ Off= TEMP= DTEMP= ELDO_PARAMS$
Minimum:
Model$
Model
Page 11 of 18
Notes
OFF
TEMP,
DTEMP
Notes
ELDO_PARAMS
Entered as needed.
e.g.
STATISTICAL=1
STATISTICAL
NONOISE
NOISE
Set to 1 or 0
There are other advanced properties that could be added, please refer to the Eldo reference manual
for more information. This description is intended to provide guidance, and should provide examples
to allow advanced users to harness the descriptive capabilities that Eldo provides.
Table 15 BJT Minimum Required Properties:
BJT Minimum Required Properties
Property Name
Property Value
Prefix
Pin Order
Ordered List of Pin Names for the netlist. (Collector Base Emitter)
Order
Recommended:
Model$ Off= TEMP= DTEMP= ELDO_PARAMS$
Minimum:
Model$
Model
Page 12 of 18
Notes
OFF
When set to 1, causes no initial operating point to be calculated for the device
during DC analysis, i.e. the device is off. When set to 0, the option is ignored.
TEMP,
DTEMP
Notes
ELDO_PARAMS
Entered as needed.
e.g.
STATISTICAL=1
STATISTICAL
NONOISE
NOISE
Set to 1 or 0
FMIN
FMAX
NBF
There are other advanced properties that could be added, please refer to the Eldo reference manual
for more information. This description is intended to provide guidance, and should provide examples
to allow advanced users to harness the descriptive capabilities that Eldo provides.
Table 18 JFET and MESFET Minimum Required Properties
In Eldo, JFET and MESFET differ by the model level used. So, the symbols are set up the same for
both devices.
JFET and MESFET Minimum Required Properties
Property Name
Property Value
Prefix
Pin Order
Ordered List of Pin Names for the netlist. (Drain Gate Source)
Order
Recommended:
Model$ Off= TEMP= DTEMP= ELDO_PARAMS$
Minimum:
Model$
Model
Page 13 of 18
Notes
OFF
When set to 1, causes no initial operating point to be calculated for the device
during DC analysis, i.e. the device is off. When set to 0, the option is ignored.
TEMP,
DTEMP
Notes
ELDO_PARAMS
Entered as needed.
e.g.
STATISTICAL=1
STATISTICAL
NONOISE
NOISE
Set to 1 or 0
FMIN
FMAX
NBF
There are other advanced properties that could be added, please refer to the Eldo reference manual
for more information. This description is intended to provide guidance, and should provide examples
to allow advanced users to harness the descriptive capabilities that Eldo provides.
Table 21 MOSFET Minimum Required Properties:
MOSFET Minimum Required Properties
Property Name
Property Value
Prefix
Pin Order
Ordered List of Pin Names for the netlist. (Drain Gate Source [Bulk])
Order
Recommended:
Model$ TEMP= DTEMP= ELDO_PARAMS$
Minimum:
Model$
Model
Page 14 of 18
Notes
TEMP, DTEMP
Property Name
Notes
ELDO_PARAMS
Entered as needed.
e.g.
STATISTICAL=1
STATISTICAL
NONOISE
NOISE
FMIN
FMAX
NBF
There are other advanced properties that could be added, please refer to the Eldo reference manual
for more information. This description is intended to provide guidance, and should provide examples
to allow advanced users to harness the descriptive capabilities that Eldo provides.
Property Value
Prefix
Pin Order
Order
Recommended:
Model$ TEMP= ELDO_PARAMS$
Minimum:
Model$
Page 15 of 18
Model
Spice Subckt
Spice Lib
Name
Notes
TEMP
Property Name
Notes
ELDO_PARAMS
Entered as needed.
e.g.
STATISTICAL=1
STATISTICAL
NONOISE
NOISE
<xxx>
There are other advanced properties that could be added, please refer to the Eldo reference manual
for more information. This description is intended to provide guidance, and should provide examples
to allow advanced users to harness the descriptive capabilities that Eldo provides.
Conclusion
This document outlines the recommended information to place on symbols or parts when creating your
libraries. Some advanced properties are also noted to guide those users who wish to use those advanced
capabilities.
Page 16 of 18
Page 17 of 18
Page 18 of 18
Copyright 2009 Mentor Graphics Corporation
Trademarks that appear in Mentor Graphics product publications that are not owned by Mentor Graphics are trademarks
of their respective owners.