• 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. RF Design
  3. Finding DC operating points at certain timepoints during...

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 64
  • Views 25721
  • Members are here 0
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

Finding DC operating points at certain timepoints during TRANSIENT analysis

RFStuff
RFStuff over 12 years ago

Dear All,

I need to run transient analysis of a circuit.

However, I also want to find the dc operating points of some components at certain instants ( time points) during  the transient analysis on the FLY. The operating points may be logged to a file for analysing the data after the transient simulatuion is OVER.

Could anybody please tell, is there any way of achieving this. I use IC5141 & MMSIM12

Kind Regards,

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    Two approaches:

    1. On the transient options form, there's a field called "infotimes" - specify the times at which you want it to output the dc operating point data. You can then annotate the "transient operating points" from any of these times after the simulation, or access them via the results browser.
    2. Or you could get the operating point data to be continuously saved during the transient for selected devices - if so, create a file called (say) "save.scs" (make sure it has a ".scs" suffix), and put:
        save M1:oppoint
      or
        save M*:oppoint sigtype=dev
      in this file, and then reference the file via Setup->Model Libraries or as a "definition file" on Setup->Simulation Files.
      With this approach you can then find the operating point data for the selected devices in the results browser and plot it versus time (be cautious of saving too much though because this can generate a lot of data if you're not careful)

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RFStuff
    RFStuff over 12 years ago

     Dear Andrew,

    Thanks a lot.

    The approach 1 looks suitable to me for large circuit blocks.

     Actually I want to write a ocean script, which intially calculate the desired timppoint and enter into the transient alnalysis before run. This can be doen.

    But, how the dc op points of certain components at the timepoints can be dumped into a log file. Basically how the OP( ) command can be used for giving DC operating point at multiple time points.Could you please throw some light into it.

    Kind Regards,

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    For completeness, this question is dealt with in your other thread - /forums/p/25743/1322126.aspx#1322126

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RWTH
    RWTH over 9 years ago

    Hi Andrew,

    Maybe this is hashing up the old stuff, but like the previous question, I would like to calculate the DCOP at certain transien time. Basically, all the capacitors should be removed and the inductors are open at the specified time.

    I tried this on a very simple RC circuit, in which the resistor and the capacitor are parallel. I placed an initial condition on top of the resistor and capacitor. I performed a transient analysis first. Let's say I see at 50uS simulation some voltage level on top of the RC, let's assume 100mV.

    Once I do infotime at 50uS and back annote the results then I should see 0V, right? Because, the cap should be discharged completely? Is my expactation from the infotime correct?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    No, that doesn't make sense. The infotimes parameter does not cause spectre to compute a DC operating point at each of the specific time; instead it reports the operating point parameters for each device at that time. Essentially an operating point is the set of voltages and currents (for the nodes and branches) in the circuit, used as a starting point for many other analyses. In that context, removing the capacitors and inductors (setting them to 0) makes sense because you are trying to find the DC steady state solution. Then once the DC operating point has been found, we typically save the information about the operating point parameters for each device (often the parameters that are used in the small-signal models, like gm, gds etc).

    With infotimes, this is during a transient. So all it is doing is saving the parameters for the devices at the bias point at that time. Removing the capacitors and inductors would be an odd thing to do, because then you'd essentially throw away all the storage elements in the circuit, and the operating point would be the same as the initial DC operating point (because it would have to find a consistent operating point in the absence of those devices - essentially finding the settled steady state again). So that's not what you'd want (I believe).

    So unless the capacitor is discharged at that time anyway, I would expect the voltage across the capacitor to reflect what it actually is at that time in the transient. Anything else would be of little use, I think. Remember there are capacitors inside all the devices too - it's not just the physical capacitors that get set to 0 when a DC operating point is computed.

    Hope that helps (and that I've not just rambled around in circles).

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RWTH
    RWTH over 9 years ago
    Hi Andrew,

    I am getting lost here a little bit. I think, I use the Cadence nomenclature wrong as well. If I say operating point, then I always thought DC operating point. I think, I have to distinguish between DCOP and operating point. For me the DCOP is the steady state current and voltage calculations, as you put nicely into the words. This is not what infotimes is doing, right?

    Let me give you a real case, where I would like to use such analysis (running first transient analysis and at certain transient time running a DCOP). We have a top level simulation and after certain normal operation, we would like to go to the power down mode and make sure we don't have any DC current consumption. If I were to run transient time simulation after PD signal asserted, then I will need to wait pretty long time, in order to measure the steady-state current and voltages. How can I solve this issue?

    Basically, after I go into the PD mode let's say at time tzero, I would like to have a DCOP analyis with the initial conditions at that time tzero. This way I would be able run the simulation very fast, instead of running a long transient simulaton on a big circuitry.

    Regards
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    Essentially each point in the transient is a solved "operating point" - and what infotimes is doing is just writing out the data at the already solved bias conditions.

    To do what you want, I think the only possible option is to run a transient simulation to the time you want, and use writefinal to write out a nodeset file which contains the voltages and currents. You could then run a dc with this as an initial condition file (readforce) and also to enable the force=all option to allow initial conditions to be used in a DC. However, I doubt this really is what  you want - because that would hold the initial conditions from the file during the DC and so the resulting DC would essentially be the same as what was in the file. If instead you used readns on the dc analysis, I'm not sure this proves very much, because all the voltages would move away from the original values to reach a settled steady-state condition.

    There used to be an option in transient to "checkpoint" the operating point voltage/currents at times during the simulation, which was used in the past as a means of recovering from a previous time. However, it wasn't very robust so that was dropped in favour of the save/recover options which write a much more complete representation of the state at a timepoint.

    So I don't think you can really do what you are trying to do here. You're expecting selected capacitors to discharge, but not others...

    The transient is not necessarily going to take a long time to simulate if there's no signal activity when you've gone into power down mode - although if you've got clocks switching, those will cause the simulator to still take timesteps, so maybe it's not so easy).

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RWTH
    RWTH over 9 years ago

    Hi Andrew,

    Thanks a lot for your inputs. They are very helpful. On the ohter hand, it is clear to me, what Cadence is doing with infotime.

    Regards,

    RWTH

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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