• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. PCB Design
  3. Problem running PSpice simulation from OrCAD Capture

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 165
  • Views 31228
  • Members are here 0
More Content
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Problem running PSpice simulation from OrCAD Capture

RaggMopp
RaggMopp over 13 years ago

The first simulation example in the PSpice User's Guide is made up of 2 voltage sources, 2 diodes, 4 resistors and 1 capacitor. When I  run the simulation from OrCAD Capture, it fails with: "ERROR(ORPSIM-15090): DC device Vin is undefined".

 I found that I can edit the PSpice netlist file to get the simulation to run in SPice A/D primarily by changing the second voltage source name from V_V2 to V2. 

 Anyone know why that is? And, what I can do in OrCAD to "correct" the PSpice output.

 
**** 09/17/12 14:20:40 ****** PSpice 16.5.0 (April 2011) ****** ID# 0 ********

 ** Profile: "SCHEMATIC1-DC Sweep"  [ C:\SI\PSPICE\UserGuide\clipper-pspicefiles\schematic1\dc sweep.sim ]


 ****     CIRCUIT DESCRIPTION


******************************************************************************




** Creating circuit file "DC Sweep.cir"
** WARNING: THIS AUTOMATICALLY GENERATED FILE MAY BE OVERWRITTEN BY SUBSEQUENT SIMULATIONS

*Libraries:
* Profile Libraries :
* Local Libraries :
.LIB "C:/Cadence/SPB_16.5/tools/pspice/library/spice_elem.lib"
* From [PSPICE NETLIST] section of C:\Cadence\SPB_16.5\tools\PSpice\PSpice.ini file:
.lib "nom.lib"

*Analysis directives:
.DC LIN Vin -10 15 1
.PROBE V(alias(*)) I(alias(*)) W(alias(*)) D(alias(*)) NOISE(alias(*))
.INC "..\SCHEMATIC1.net"



**** INCLUDING SCHEMATIC1.net ****
* source CLIPPER
V_V1         VCC 0 5V
V_V2         VIN 0 0V
D_D1         MID VCC D1N3940
D_D2         0 MID D1N3940
R_R1         VIN MID R_R1 1k TC=0,0
.model        R_R1 RES R=1 DEV=5% TC1=0 TC2=0
R_R2         MID VCC R_R2 3.3k TC=0,0
.model        R_R2 RES R=1 DEV=5% TC1=0 TC2=0
R_R3         0 MID R_R3 3.3k TC=0,0
.model        R_R3 RES R=1 DEV=5% TC1=0 TC2=0
R_R4         0 OUT R_R4 5.6k TC=0,0
.model        R_R4 RES R=1 DEV=5% TC1=0 TC2=0
C_C1         MID OUT  0.47uF  TC=0,0

**** RESUMING "DC Sweep.cir" ****
.END


ERROR(ORPSIM-15090): DC device Vin is undefined

  • Cancel
  • oldmouldy
    oldmouldy over 13 years ago
    Your simulation profile is trying to run a DC Sweep of device Vin, you have no device Vin, in your netlist Vin is a net, V2 is the device to sweep the voltage at net Vin, change the Voltage Source in the Sweep to V2 and the simulation will run correctly.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RaggMopp
    RaggMopp over 13 years ago

    Thanks, that was helpful in that it guided me to the answer to my original question.

    So, to sum up, the information in Chapter 2 - Figure 6 - DC sweep analysis settings in the PSpice User's Guide, Second Edition 31 May 2000, is incorrect in one regard. When setting up the Simulation Profile, replace Voltage Source Name: "Vin" with the source name generated by OrCAD which, in the case of the example, becomes "V_V2". The simulation will then run correctly from OrCAD Capture.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • oldmouldy
    oldmouldy over 13 years ago

    I don't have access to a version of the Users Guide that is so old BUT, I suspect that you missed the Steps to name the IN net and change the RefDes of the swept source to Vin (from the likely default of V2) along the way. Things would then work correctly.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RaggMopp
    RaggMopp over 13 years ago

     If "Vin" had worked, we wouldn't be having this conversation. Naming the IN net has no effect.

    So then, since I am annoyed, I will critique what appears to be an incomplete attempt to edit a correction to the problem in the PSpice User's Guide.

    In the latest online PSpice User's Guide a new figure is added: Figure 2-5. The difference being that the two sources are hardwired into the schematic diode clipper. At least, I assume that is the change, since the figure called "Diode clipper design" is still labeled 1-1 and the "Figure 2-5" links don't actually link to anything.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • zaied
    zaied over 11 years ago

    my problem is like this.....

    **** 01/12/14 11:42:05 ********* PSpice 9.2 (Mar 2000) ******** ID# 0 ********

     

     ** Profile: "SCHEMATIC1-maxipower"  [ F:\112454\maxipower-SCHEMATIC1-maxipower.sim ] 

     

     

     ****     CIRCUIT DESCRIPTION

     

     

    ******************************************************************************

     

     

     

     

    ** Creating circuit file "maxipower-SCHEMATIC1-maxipower.sim.cir" 

    ** WARNING: THIS AUTOMATICALLY GENERATED FILE MAY BE OVERWRITTEN BY SUBSEQUENT SIMULATIONS

     

    *Libraries: 

    * Local Libraries :

    * From [PSPICE NETLIST] section of C:\Program Files\Orcad\PSpice\PSpice.ini file:

    .lib "nom.lib" 

     

    *Analysis directives: 

    .DC LIN PARAM RVAL 1 10k 10 

    .PROBE V(*) I(*) W(*) D(*) NOISE(*) 

    .INC ".\maxipower-SCHEMATIC1.net" 

     

     

     

    **** INCLUDING maxipower-SCHEMATIC1.net ****

    * source MAXIPOWER

    V_V1         VIN 0 10vdc

    R_R1         VIN VOUT  1k  

    R_R2         0 VOUT  {RVAL}  

    .PARAM  {RVAL}=1k RVAL=1k

    --------$

    ERROR -- Param name

     

    **** RESUMING maxipower-SCHEMATIC1-maxipower.sim.cir ****

    .END

     

    please...give me a solution...

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
>
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information