• 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. Custom IC Design
  3. Use of DC operating point parameters in calculations and...

Stats

  • Locked Locked
  • Replies 13
  • Subscribers 126
  • Views 24970
  • 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

Use of DC operating point parameters in calculations and plots

archive
archive over 18 years ago

Hi all,

I run a DC sweep simulation on ADE and I would like to plot some of the DC operating point parameters of my schematic (such as vdsat of the transistors, ...)
Moreover, I would like to use these parameters in the calculator in order to make calculations (e.g.: use of vdsat in some calculations).

Does anyone have any idea?

Thks for considering my request.

AXP


Originally posted in cdnusers.org by axp
  • Cancel
Parents
  • archive
    archive over 18 years ago

    It's not in spectreMDL syntax - it's just straight spectre syntax. See "spectre -h save" for more details (as I mentioned before). It's also covered in the spectre documentation in cdsdoc/cdnshelp (depending on the version of MMSIM you're using).

    For hierarchy, you need to use netlist names, and spectre's hierarchy delimiter. So if the transistor is called "M5" and is in an instance called I2, you'd do:

    save I2.M5:all

    Note that if M5 is modelled using a (non-inline) subckt model, you would need the name of the instance within the subckt model. The simplest way of finding out (rather than diving through all the model files) is to do a single DC operating point, and then look at the operating point results in the results browser, and see what the instance name there is called.

    If you want to model something with a subckt model, you can reference that .scs file from the Setup->Model Libraries form in ADE. Then for the component, you can set up the CDF to have the following in the spectre simInfo:

    componentName: theNameOfTheSubckt
    termOrder: the order of the terminals in the subckt model, using the names on the symbol
    instParameters: any parameters you need to pass (need corresponding CDF parameters).

    You'll also need a stopping view, to tell the netlister to stop expanding the hierarchy at that point. The easiest way to do this is to copy the symbol view to a view called "spectre".

    Note there are numerous sourcelink.cadence.com solutions on how to do the above, so it's worth looking there if you can.

    Regards,

    Andrew.


    Originally posted in cdnusers.org by adbeckett
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 18 years ago

    It's not in spectreMDL syntax - it's just straight spectre syntax. See "spectre -h save" for more details (as I mentioned before). It's also covered in the spectre documentation in cdsdoc/cdnshelp (depending on the version of MMSIM you're using).

    For hierarchy, you need to use netlist names, and spectre's hierarchy delimiter. So if the transistor is called "M5" and is in an instance called I2, you'd do:

    save I2.M5:all

    Note that if M5 is modelled using a (non-inline) subckt model, you would need the name of the instance within the subckt model. The simplest way of finding out (rather than diving through all the model files) is to do a single DC operating point, and then look at the operating point results in the results browser, and see what the instance name there is called.

    If you want to model something with a subckt model, you can reference that .scs file from the Setup->Model Libraries form in ADE. Then for the component, you can set up the CDF to have the following in the spectre simInfo:

    componentName: theNameOfTheSubckt
    termOrder: the order of the terminals in the subckt model, using the names on the symbol
    instParameters: any parameters you need to pass (need corresponding CDF parameters).

    You'll also need a stopping view, to tell the netlister to stop expanding the hierarchy at that point. The easiest way to do this is to copy the symbol view to a view called "spectre".

    Note there are numerous sourcelink.cadence.com solutions on how to do the above, so it's worth looking there if you can.

    Regards,

    Andrew.


    Originally posted in cdnusers.org by adbeckett
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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