Stats

More Content

problems with smoke simulation

digital1

I have a simple resistive circuit R1 and R2, R2 comes from the menu Place / PSpice Part/ Resistor and R1 comes from my CIS Cip database.

I have all the smoke parameters set up the same but for the R1 I have
the following non fatal errors

Voltage Data not found for smoke test RV

Please verify save data and data collections options in the simulation profile

R2 gives me the voltage data expressed as RV but R1 from my cip database does not

Has anybody else found this error and if so how do I correct it

Parents
  • 0

    Hi,

    This error can come due to one of the following reasons:

    1. Data collection for voltage, current and power not set correctly.

    In order to resolve this go to PSpice > Edit Simulation Profile > Data Collection and ensure that for Voltages , Current and Power ALL is selected.

    If not then change from the drop down to ALL.

    2. This error can also come due to incorrect test node mapping.
    Port names defined in test node mapping should be same as the pin name of component which is defined in PSpiceTemplate.

    If there is a mismatch here, then this error will be reported.

    To resolve this, edit the model and check Test Node Mapping. Make sure that port names are same as defined in PSpiceTemplate.

    Can you please check, hopefully the above solution shall help.

    Do share your input, how it goes.

Reply
  • 0

    Hi,

    This error can come due to one of the following reasons:

    1. Data collection for voltage, current and power not set correctly.

    In order to resolve this go to PSpice > Edit Simulation Profile > Data Collection and ensure that for Voltages , Current and Power ALL is selected.

    If not then change from the drop down to ALL.

    2. This error can also come due to incorrect test node mapping.
    Port names defined in test node mapping should be same as the pin name of component which is defined in PSpiceTemplate.

    If there is a mismatch here, then this error will be reported.

    To resolve this, edit the model and check Test Node Mapping. Make sure that port names are same as defined in PSpiceTemplate.

    Can you please check, hopefully the above solution shall help.

    Do share your input, how it goes.

Children
  • 0 in reply to IshaS

    Hi  

    Thank you for your reply. I can say that Data collection for voltage current and power is set correctly otherwise surely i wouldnt have voltage data for R2 
    For statement 2  I have not used port names just 2 resistors and 1 dc voltage source and a pspice ground.here is the pspice netlist

    V_V3 N00133 0 35Vdc
    R_R1 N00133 N00145 R_R1 10k TC=0.00005,0
    .model R_R1 RES R=1 DEV=1% TC1=0.00005 TC2=0
    R_R2 N00145 0 1k TC=0,0

    The main difference is R1 gives me a model statement and R2 doesn't  but if i give R2 a tolereance then R2 has a model statement but it still gives me the voltage simulated or RV as it is called in smoke

    R2 gives me the voltage data but R1 doesn't here is the smoke window from this simulation

    AAs you can see I am using the latest version of Orcad 

    II really need this to work for 1 other thing all my smoke parameters come from CIS CIP and taken from manufacturers datasheets. As you can see all the other smoke parameters for R1 is working correctly

  • +1 in reply to IshaS

    Hi  I found a workround my capture symbol was called resistor  and the pspice symbol was called R when I renamed my capture symbol to R the problem went away sounds like one of those silly bugs 

  • 0 in reply to digital1

    Hi Digital1, 

    There seemed to be symbol name and pin-mismatch.

    Great issue is resolved.

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.