PSpice Release 9
Release Notes

November, 1998

Most of the information contained in these release notes is not included in the PSpice manuals or online help. Please read the notes carefully to see if any apply to your designs.

These release notes are divided into the following sections:


Installation notes

There are no known installation problems specific to PSpice Release 9.


What's new

This section gives you information concerning:

 

PSpice now fully integrated with OrCAD Capture

OrCAD PSpice Release 9 connects two of today's most popular EDA products, Capture and PSpice.

With OrCAD PSpice Release 9, you can:

  • Enjoy a full-featured design entry environment with easy-to-use editing features and numerous advanced capabilities.
  • Find support for more than 30 netlist formats, and import and export EDIF graphical schematics for interchanging designs with other schematic packages.
  • Manage hierarchical designs and multi-page designs in a single file, and browse the hierarchy tree with the Project Manager.
  • Use a property editor spreadsheet to simultaneously edit multiple parts.
  • Import designs created with any version of MicroSim Schematics.
  • Simulate with a single button click.
  • Specify stimulus and simulation analysis directly from the schematic.
  • Create and edit simulation models from a schematic.
  • Manage, view, and run a list of simulations.
  • Create, open, and edit simulation profiles to simulate a design. A simulation profile contains analysis settings, library settings, stimulus settings, etc.
  • View waveforms during or after a simulation.
  • View output files.
  • Use trace markers to examine waveforms at various nodes in the circuit. Trace markers are color coded with the same colors as their corresponding traces.

User interface with presentation quality graphics

  • The new PSpice user interface integrates the Probe waveform analyzer with the PSpice simulator into a single application.
  • The new simulation setup dialog box has tabbed windows with access to a very organized, self-documenting analysis setup procedure.
  • An editable simulation queue shows you how many files are currently in line to be simulated; this allows you to re-order the list.
  • The new Probe interface supports presentation quality graphics, adding significantly to the display and printing options to improve reporting and documentation.
  • Graphical presentation quality has been improved with user-controlled grid settings, and grid and trace properties (style, thickness, and color), including support for scalable clipboard output to support copying and pasting into documentation packages.

Simulation Profiles

  • The new Simulation Profiles feature allows you to specify unlimited named simulation setups that are stored with the project.
  • You can specify and store multiple simulations for the same schematic, and run one or more of them at any time. Each simulation profile refers to one root schematic in a design.
  • A profile includes one analysis type (AC, DC, or transient) with any or all of the applicable additions (noise, sensitivity, temperature, parametric, Monte Carlo, etc.), specific option settings, and settings for automatically restoring plots after simulation.

Enhancements for simulating large circuits:

  • Improved simulation of large circuits
  • Improved GMIN stepping algorithm
  • New matrix pre-ordering algorithm to speed up simulation of large circuits (.OPTIONS PREORDER)

Enhancements to device models

  • Enhanced BSIM3v3.1 MOSFET model
  • New EKV MOSFET model
  • Bipolar model enhancements
    • New Temperature dependencies for the quasi-saturation model parameters GAMMA, RCO, and VO with QUASIMOD=1.0
    • New model parameter, XCJS, to allow fraction of CJS to be connected internally to RC

Enhancements to Model Editor (formerly Parts)

  • The new Model Editor provides a unified application for editing models either in text form, or by modifying their specifications.
  • Darlington Modeling is now supported.

Enhancements to model libraries

  • Over 1,000 new simulation models have been added, bringing the total to over 13,000. New libraries include :
    • Data Converter (Capture is required for this library - dataconv.olb)
    • Transceiver (linedriv.lib)
    • Darlington (darlngtn.lib)

The following table lists new and enhanced libraries for R9:

Model Developer

Library Name

Device Type

New Models

AMP

amp.lib

Connectors

474

Analog Devices

anlg_dev.lib

Op-Amps

57

Burr-Brown

burr_brn.lib

Op-Amps

20

Elantec

elantec.lib

Op-Amps

9

Maxim

maxim.lib

Op-Amps

13

OrCAD

jpipolar.lib

Japanese Bipolar Transistors

107

OrCAD

jpwrmos.lib

Japanese Power MOS Transistors

111

OrCAD

opto.lib

Optocouplers

22

LED (Light Emitting Diodes)

2

Photo-detector Diodes

2

OrCAD

linedriv.lib (new ) Transceivers

14

Receivers

4

OrCAD

jpwrbjt.lib

Power Bipolar Transistors

77

OrCAD

darlngtn.lib (new)

Darlington Transistors

60

OrCAD

dataconv.lib (new)

Digital to Analog Converters (DAC)

32

Analog to Digital Converters (ADC)

30

Zetex

zetex.lib

Transistors and Diodes

56


Known problems

This section gives you information concerning:

 

Documentation errata

The "Simulation Examples" chapter is not clear with regard to which ground symbol to use. Use the '0' symbol in <orcad_dir>\capture\library\pspice\source.olb. You can access this symbol after configuring this library in the Place Ground dialog box.

 

Reported PSpice problems that have not been fixed for this release

These problems have been reported and are not yet fixed for this release of PSpice. This list is intended to cite the most serious problems and is not an exhaustive list of all known problems. Many of these problems have workarounds. Please consult the OrCAD Knowledge Base for updated information.

Id

Title

5304

Request to allow parameters for temperature coefficients on resistor statement.

6115

Extraction of Darlingtons in the Model Editor is slow.

6255

Output variables don't translate correctly if they contain 2 nodes and character names.

6526

Request for the ability to copy from a simulation profile summary.

6560

Marching waveforms displays only one section of a multiple section simulation after completion.

6608

Scaling problems when copying a metafile to the clipboard.

6701

Request to allow cursors to work on single data point analysis.

6805

Request for user defined icons and commands in Customize menu.

6882

Copy to Clipboard does not include cursor info.

6888

Request to automatically display the .out file when a simulation error occurs.

7069

Model Editor: Vbe(sat) curve is discontinuous for BU508 library model.

7156

The time shown in the PSpice status bar is not always in sync with the time in the Analysis tab.

7231

Hysteresis curve is incorrect after File, Open of a CORE model.

7334

 When simulating, Probe window comes up restored even if previously maximized.

7563

Request for View, Zoom, Fit.

7564

Request for View, Zoom, Previous.

7706

No way to suppress "CURRENT MODEL PARAMETERS..." with .MC analysis.

7735

Request for support of multiple views.

7806

Request for property to link a text file to a symbol (support for FILENAME in Schematics).

7808

Make BROWSE dialog box wider in project wizard to show complete paths.

7810

Request for DRC function in PSpice menu.

7812

Request for ability to save and load a configuration of libraries.

7840

Printing fails when error "Can't begin another Print or Print Preview" occurs.

7949

Cannot change entries in the Library, Include or Stimulus tabs of the Simulation Settings dialog box.

8172

Shot noise (NSID) for diode is incorrect unless .noise output variable is used.

8244

PSpice New Simulation does not inherit markers.

8253

Zoom Area command does not work unless a plot is selected.

8328

The Trace, Undelete command in PSpice does not refresh the marker colors in Capture.

8648

Marching waveforms does not work if multiple Probe windows are open for the .dat file.

8778

Capture overwrites any part library changes done by the Model Editor.

8792

Closing a page will sometimes remove markers on other open pages.

8803

Double-click does not work on the negative differential marker.

 

 

 

 


General notes

This section gives you information concerning:

 

Frequently Asked Questions

Q: Can I run Release 9 under Windows 3.1/3.11?

A: No. Release 9 will not run under Windows 3.1/3.11. Release 9 will run under Windows 95, Windows 98, or Windows NT.

 

Q. Why can't I see the PSpice menu in Capture?

A. To access the PSpice menu, you must be working on an "Analog or Mixed-Signal Design" project. Every design is associated with a project whose type determines the commands available for it (PCB, Analog, etc.). If the design is separated from its project file, Capture cannot tell the project type and creates a default PCB project for the design. If you create a new design by using the File menu and choosing New, Design, you will get a default PCB project. If you want to create an Analog or Mixed-Signal Design project you should use the Project creation wizard. (From the File menu, point to New and choose Project.)


Q: How do I specify trace colors in PSpice that correspond to Markers in Schematics?

A: Right-click on the desired trace in PSpice. Choose Properties to access the Colors pull-down. The corresponding marker in Capture will reflect this setting.

 
Q: Why do I get a blue screen after updating to Windows NT Service Pack 4?

A: NT4.0 Service Pack 4 requires Aladdin hinstall v3.74. Call OrCAD Tech Support for the latest information on this problem.

 

Q: Where is the .ini file for PSpice Release 9?

A: <windows_dir>\pspice.ini

 

Q: Why do I get missing PSPICETEMPLATE DRCs when I create a netlist?

A: Check that the problem part was obtained from a library from the PSpice folder (under the Library folder). For example there are resistor symbols in <orcad_dir>\capture\library\device.olb and in <orcad_dir>\capture\library\pspice\analog.olb. For PSpice simulation, the resistor in analog.olb should be used, since it has a PSPICETEMPLATE property.

 

Q: How can I keep my model and part libraries configured from project to project?

A: These libraries may be added to the <orcad_dir>\capture\capture.ini file:

[Part Selector Configured Libraries]

Number of Configured Libraries=2

Library0=E:\ORCAD2\CAPTURE\LIBRARY\PSPICE\ANALOG.OLB

Library1=E:\ORCAD2\CAPTURE\LIBRARY\PSPICE\ANL_MISC.OLB

 

Q: How to set a command line option for PSpice (for example -p, -i)?

A: Options are now read from the PSPICE.INI file, PSPICE section, PSPICECMDLINE key. PSpice.ini has an entry PSPICECMDLINE that can be changed (using a text editor) to specify what command line options should be used when starting up PSpice.

[PSPICE]

PSPICECMDLINE= -i <user_dir>\<ini_file>

 

Q: Why doesn't PSpice run the simulation when started with a command line pspice <circuit_file>?

A: Use pspice -r <circuit_file>. -r is a new option meaning run/simulate file(s); if not specified, the file will just be opened, and PSpice will wait for he next command.

 

Q: Where can I find tips for getting started in Capture?

A: See Chapter 2 in the on-line Schematics-to-Capture Quick Start manual.

 

Q: How can I create a subcircuit for my schematic design?

A: Go to Project Manager and select the .dsn file. From the Tools menu, choose Create Netlist. Check Create Subckt format netlist.

 

Q: How can I define my own set of properties to display in the spreadsheet?

A: The file "prefprop.txt" can be edited to allow custom "filters".

 

Q: Why does my library list change in Capture when I use both Place Part and Place Power/Place Ground?

A: Place Part and Place Power/Ground keep different library lists (thus you have to add source.olb for each one). The libraries source, sourcstm, special, and analog are configured for all PSpice projects created with the project wizard. 

 

Q: Why don't ground symbols from CAPSYM.OLB netlist as node '0'?

A: The standard power and ground symbols in capsym.olb must be renamed to the global PSpice node name. Nearly always this should be node 0 for grounds in PSpice. Thus, the need for the '0' symbol. You can, of course, double-click any ground and rename the part to 0.

 

Q: Why do my markers appear gray sometimes and are colored at other times?

A. Markers inherit their color from Probe traces. Also, markers are specific to a simulation profile. If the active simulation profile is open in PSpice and the traces corresponding to the markers are shown in the active Probe Waveform window then the markers are colored in the schematic pages. Otherwise, the markers show up gray. The colors allow you to identify traces in the Probe window by the colored markers in the schematic pages.

Q: Why do my markers disappear after changing simulation profiles?

A: Markers are specific to a simulation profile. Only markers that were created for the currently active simulation profile are displayed.

 

Q: Why is the Darlington extraction in the Model Editor slow?

A: Darlingtons are complex models with characteristics that require many calculations to evaluate. We recommend that the auto-update option be disabled while entering specifications, or when tweaking model parameters by hand.

 

Q: Why is Edit/Model or Edit/Stimulus grayed out in Capture?

A: The menu items to edit a PSpice model or PSpice stimulus are disabled when the selected part is not associated with the root schematic.

 

Q: Why can't I simulate when I specify the Output Variable with two nodes?

A: This problem has not yet been corrected for Release 9. As a workaround, enter any alphanumeric names with square brackets enclosing them in the Simulation Settings dialog box.

Example: v([N0009],[N00010]) 

 

Q: Why have .cir, .net, .als, and .out file names become longer than in Release 8?

A: These PSpice filenames in Release 9 have the format:

<project>-<schem>-<profile>.ext

This makes it easy to identify the analysis and the schematic to which these files apply.

 

Q: Why does the Model Editor sometimes display a text editor and other times use the extractor dialog box?

A: The Model Editor will use specification based entry for new models, or models that have previously been extracted and have not been modified. Note that the model libraries supplied by OrCAD do not contain datasheet specification data. For intrinsic models, from the View menu, choose Normal to load the parameter data only into the extractor. Doing this may modify the original model and is not recommended, except to enter datasheet specifications and perform new extractions.

 

Q: Why do I get "Skipping section 1. Section 1 has less than 2 rows of data." from PSpice when attempting to load the .dat file after a simulation?

A: If a simulation is aborted very early, or if there are fatal errors it is possible for the data file to be corrupt. The simulation must be run longer. Contact Tech Support if the simulation can not be run longer due to non-convergence or a fatal error.

 

Q: Why does the percent complete reported by PSpice sometimes read 100%, incorrectly?

A: PSpice percent complete shows 100% whenever the simulation ends whether terminated or completed. PSpice shows percent complete 100% even when the simulation is aborted at mid analysis.

 

Q: Why are there obsolete Schematics symbols in some libraries?

A: Libraries with hierarchical symbols can contain symbols translated from Schematics in their Design Cache (such as INTERFACE in anl_misc.olb). We do not recommend using symbols from the Design Cache of these libraries.

 

Q: Why does the Schematics-to-Capture translator attempt to write libraries to the old MSim_8 library directory?

A: The only way that you would write files to the standard MicroSim directory is if you don't have the Consolidate option checked. If you aren't translating custom symbol libraries/hierarchical schematics (designs to be re-used), then always use Consolidate.

 

Q: In PSpice, when I right-click on a trace to edit the Properties, why does Show Symbol have no effect?

A: From the Tools menu, choose Options and check Attributes in the Use Symbols frame.

 

Q: Why can't I add Model Libraries, Stimulus Libraries, or Include Files folders from the Project Manager window?

A: You cannot add files to the Model Libraries, Stimulus Libraries, or Include Files folders from the Project Manager window. Use the simulation settings dialog box, and add the desired files using the appropriate tabs. This dialog box can be accessed from Capture using the following command sequence:

From the PSpice menu, choose Edit Simulation Settings or New Simulation Profile.

 

Q: What is the .OPTIONS PREORDER enhancement and how do I use it?

A: .OPTIONS PREORDER causes the circuit to be ordered in a fixed way prior to performing any analysis. The matrix diagonal is sorted in ascending order of Markowitz count (a criterion which tends to minimize the number of "fillins" that can appear in the matrix during LU decomposition). Ties are broken by taking the lowest row element count first and then taking the lowest column element count.
If you use a circuit file to simulate, just add the following line to the file.

.OPTIONS PREORDER

(This feature is not currently available for use with Simulation Profiles, but can be specified in an include file.)

Q: I have setup my simulation to collect data only at markers. I simulated once, went back to the schematic, added more markers, and re-simulated. However, these markers do not show up in my Probe waveform window. What is wrong?

A. When collecting data at markers, close the Probe windows before re-simulating after adding more markers.

 

Q: How do I assign a default net name to power type pin in Capture?

A: To do this:

  1. Double-click symbol to bring up the property editor spreadsheet.
  2. Select the Pins tab.
  3. For the Power pin, enter the default net name under the PSpiceDefaultNet property.
  4. Click Apply.
The PSpice netlist will contain this net name if the pin is listed in the PSpiceTemplate.

 

Q: How do I assign the PWR_NODE and GND_NODE for DIGIFPWR in SPECIAL.OLB?

A: To do this:

  1. Double-click symbol to bring up the property editor spreadsheet.
  2. Select the Pins tab.
  3. For the PWR pin, enter a net name under the PSpiceDefaultNet property.
  4. Click Apply.
  5. For the GND pin, enter a net name under the PSpiceDefaultNet property.
  6. Click Apply.
  7. To use the power supply, change the PSpiceDefaultNet properties on the 74xx device to use the same net names.

 

Q: How do I use the DATACONV and FILTSUB libraries?

A: To change a design to a non-primitive state: In the Project Manager, right-click the .DSN file, choose Design Properties, then click the Schematic Design tab. Click the Design Properties button, click the Hierarchy tab, and select Non-primitive.

To change the global default to non-primitive: From the Options menu, choose Design Template. Click the Hierarchy tab and select Non-primitive in the Parts frame.

In order to use the hierarchical symbols in the DATACONV.OLB and FILTSUB.OLB libraries, the Primitive attribute needs to be set to No after placement. All parts in these libraries currently have the Primitive attribute set to Default. You will not be able to Descend Hierarchy or Netlist without errors if this setting isn't changed to No for hierarchical symbols.

 

 

Tips for PSpice Release 8 users

Translating MicroSim Schematics to OrCAD Capture projects

MicroSim Schematics to OrCAD Capture Project Translation can be very easily done through the import utility in Capture. In Capture, from the File menu, choose Import and in the PSpice tab select the source schematic, the destination project, and the MicroSim msim.ini file for existing settings. Then click OK to start the automated translation utility.

For last minute information about the Schematics to Capture Translator, see the OrCAD Capture 9 Release Notes.

Translated designs with unconnected pin error

Translated schematics, when netlisted for PSpice, may get "unconnected pin" errors in Release 9 if there are voltage sources or ABM parts with outputs connected to ports where the ports have no corresponding port with the same name. These designs will need their design cache changed to Unique Net to work correctly. To do this:

  1. In Capture, select the part.
  2. From the Edit menu, choose Part.
  3. Double-click the pin.
  4. Add a User Property FLOAT=UniqueNet.
  5. From the File menu, choose Save.
  6. Select Update All.

Descending hierarchical parts in a translated .SLB library

If you use a part in a translated library and the library is not in the same directory as your design, you will not be able to descend. As a workaround, you can edit the part in the library and clear the name of the library from the implementation cell so that it is blank.

Creating new PSpice projects In Capture

Please see NewPSpiceProject

PSpice libraries

The PSpice part libraries (.olb files) and simulation model libraries (.lib files) are located under the Capture\ Library\PSpice directory under your installation directory. If you wish to add more PSpice part libraries to your design, you can do so using the Place Part dialog box (From the Place menu, choose Part or use the Place Part toolbar button) and adding a library from the above mentioned subdirectory.

Placing Ground Symbols

To place a ground symbol for PSpice simulations, you must use the '0' symbol. To select the '0' symbol:

  1. From the Place menu, choose Ground (or use the Place Ground toolbar button).
  2. Select the Source part library from the Libraries list. (If not already there, add it to the library list using the Add Library button; SOURCE.OLB is located in the Capture\Library\PSpice subdirectory under your installation directory.)
  3. Select the '0' symbol.
  4. Click OK to place the ground symbol.

Save As and Archive commands

Please see Save As and Archive

Global parameters in Capture

The new PARAM part works differently in Release 9. You simply add new properties and assign them values in the spreadsheet. They should display on the schematic and netlist as in Release 8. For example, you can add a property named VAL with value 10K with the following steps:

  1. From the Place menu, choose Part.
  2. Place an instance of PARAM from SPECIAL.OLB.
  3. Double-click it to start the spreadsheet editor.
  4. Click New.
  5. Type Name=<param name>.
  6. Click on the cell below <param name>. Type in the value.
  7. Click Display. Click Name=Value.
  8. Click Apply.

Unlike the PARAM symbol in Schematics, you can add more than three parameters for a single part instance.

 HI and LO symbols

The HI and LO symbols for digital inputs have been renamed and moved. These can be used by choosing Place Power in Capture. $D_HI and $D_LO are now in the library Capture\Library\PSpice\special.olb under your installation directory.

Simulating without Displaying Waveforms

The settings for Probe Window in the Simulation Settings dialog box have no direct equivalent to choosing None at Probe startup from the Probe Startup menu in Schematics.

As a workaround, you can uncheck both "Display Probe window when profile is opened" and "Display Probe window" in the Simulation Settings dialog box, under the Probe Window tab.

NRD and NRS default for MOSFETs

Prior to Release 9 the default values for NRD and NRS in PSpice were 1. Starting with Release 9 the defaults values are 0. This change will not affect device instances with NRD and NRS specified in the netlist.

MEMUSE has been removed from the .OPTIONS ACCT report

Due to lack of accuracy with current dynamic memory allocation methods, MEMUSE will no longer appear when you simulate with .OPTIONS ACCT in the netlist. The memory used can be obtained from Windows.

Command line switches for PSpice

Command line options, such as "-i" to load a user defined initialization file (.ini), can be specified by adding the following line to the <windows_dir>\pspice.ini file:

[PSPICE]

PSPICECMDLINE= -i <user_dir>\<ini_file>

A custom .ini file can contain a configuration of PSpice library, include and stimulus files. For other command line options, see the on-line PSpice A/D Reference Manual.

Change of function of PRINT STEP

Print Step no longer needs to be specified for a transient analysis. When left at the new default value of 0, the following is used in its place: maximum step size if defined, otherwise Final Time/100.

PSpice uses TSTEP for the following things in addition to setting print and plot intervals for the text output file:

  1. It's the maximum time step for circuits that have no charge storage devices or maximum step size.
  2. It's used to limit the maximum frequency for impulse response calculations in ABM Laplace devices and lossy transmission lines.
  3. It becomes the default for various parameters associated with independent source stimuli (i.e., rise time, fall time, 1/frequency, etc.) if these values are set to zero by the user.
  4. .FOUR uses it to specify time resolution for the old Fourier analysis, whose results are printed to the text output file. This does not affect the FFT plots in Probe.

PSpiceDefaultNet

IPIN(<pin>) attributes present for hidden pins in Schematics are replaced by the PSpiceDefaultNet property on Power type pins in Capture. When creating a part with a Power type pin, create the pin property:

PSpiceDefaultNet=<net_name>

The PSpiceDefaultNet pin property cannot be displayed on the schematic.

 

Miscellaneous

Creating new PSpice projects

Use the Project Wizard to create a new PSpice project.

  1. From Capture's File menu, point to New and choose Project.
  2. In the New Project dialog box, select Analog or Mixed-Signal Circuit Wizard.
  3. Select the part libraries you wish to use to create the design.
  4. Select Finish to complete the project creation.

PSpice libraries

The PSpice part libraries (.olb files) and simulation model libraries (.lib files) are located under the Capture\Library\PSpice directory under your installation directory. If you wish to add more PSpice part libraries to your design, you can do so using the Place Part dialog box (from the Place menu, choose Part or use the Place Part toolbar button) and adding a library from the above mentioned subdirectory.

Placing ground symbols

To place a ground symbol for PSpice simulations, you must use the '0' symbol. To select the '0' symbol:

  1. From the Place menu, choose Ground (or use the Place Ground toolbar button).
  2. Select the Source part library from the Libraries list. (If not already there, add it to the library list using the Add Library button; source.olb is located in the Capture\Library\PSpice subdirectory under your installation directory.)
  3. Select the '0' symbol.
  4. Click OK to place the ground symbol.

Using Save As from Capture

In Capture a design file (.DSN) is always accompanied by a project file (.OPJ). Each time you do a Save As function to save a design file to another name or directory, it is recommended that you also Save As the project file. To do this:

  1. In the Project Manager highlight the name of the design file (i.e. .\<filename>.DSN).
  2. From the File menu, choose Save As.
  3. Change the filename of the design in the File Name text box and/or change the directory.
  4. Press Save.
  5. Highlight the Design Resources folder.
  6. From the File menu, choose Save As.
  7. Change the filename of the project (.OPJ) and/or change the directory to the same directory where you just saved the design file.
  8. Press Save.

This process saves a .DSN file and a .OPJ file into the same directory and allows you to continue editing the current project without altering the original files.

Using the Archive menu command in Capture

You can use the Archive menu command to save your project and associated files to a different directory. The Archive menu command is accessible if the Project Manager window in Capture is active.

  1. From the File menu, choose Archive Project.
  2. In the Archive Project dialog box, specify the directory to which the files need to be saved.
  3. Also specify what optional files need to be saved by checking the appropriate check boxes. (The library files option saves part library files and other related files (.olb, .sml, etc.) from the Library directory; the output files option saves files generated by Capture's tools (.xrf, .edn, etc.); the referenced projects option recursively saves any projects referenced from within the current project.)

Note: For PSpice projects, the simulation profiles and the local files (.lib, .stl, .inc) will all be archived along with the project. The output files option currently does not archive simulation output files (.dat, .out, etc.).

Library parts with hierarchy

OrCAD PSpice A/D Release 9 ships with two libraries which contain hierarchical symbols with underlying sub-schematics: dataconv.olb and filtsub.olb. To use a hierarchical part in a design you must use the Edit Properties command, then set PRIMITIVE=NO using the pull-down in the property spreadsheet.

PSpice .OPTIONS to improve simulation of large circuits (STEPGMIN, PREORDER)

  • STEPGMIN - Use .OPTIONS STEPGMIN to instruct PSpice to use a newly enhanced GMIN stepping algorithm to help DC convergence for large circuits.
  • PREORDER - Use .OPTIONS PREORDER to instruct PSpice to reduce simulation sensitivity to he netlist order and to also reduce the likelihood of "fill-in avalanches". This can speed up the simulation of large circuits. This option is not available in the Simulation Settings dialog box but can be specified in an include file. 

PSpice A/D Basics

In the libraries provided with PSpice A/D Basics, there are a number of parts that use delay line models that are not supported by the simulation. The use of these models may produce erroneous simulation results. The names of these parts and their libraries are as follows:

  • 74121, 74122, 74123 in 7400.LIB
  • CD4098B, CD4538B in CD4000.LIB
  • 74LS122,74LS123 in 74LS.LIB
  • 54L121, 54L122, 54L123 in 74L.LIB
  • 555D (Mixed A/D model for the CMOS version of the 555 Timer) in DIG_MISC.LIB
  • Subckt DELAY (a generic delay line model in DIG_MISC.LIB)

Additionally, the following libraries are not supported by the Basics package, therefore you should not place parts from these:

  • 1_SHOT.OLB
  • DATACONV.OLB
  • IGBT.OLB
  • MAGNETIC.OLB
  • SOURCSTM.OLB
  • SWIT_REG.OLB
  • THYRISTR.OLB
  • TLINE.OLB

Optimizer specification file

The .OPT file is not archived automatically. You must drag and drop this file manually into the Outputs folder after working in Optimizer in order to archive it. You can also use the copy command to do this.