• 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. Capturing all operating point info in a text file

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 14836
  • 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

Capturing all operating point info in a text file

swdesigner
swdesigner over 15 years ago

Does anyone know how to do this? The only way I have for accessing device OP info is to print the operating point info device by device into the Results Display Window. I'd like to capture all the OP info for all devices into a text file because I need to compare operating points for two corners to find the device causing my circuit to fail.

Thanks

---- 

By the way, if anyone is interested in setting up a bindkay (say '1') to go into "print device OP info in Results Display Window" mode, here's how :

hiSetBindkey("Schematics" "<Key>1" "load\"/~/skill/op_info.il\")")

where that file contains :

sevPrintResults('sevSession1 'dcOpPoints)

If you want to setup <Key>2 to Update this Results Display Window so that you only see the last device you clicked on  

load this procedure into your session :

procedure( CCSkey()

   wins = hiGetWindowList()

   win = setof( y wins y~>hiForm && rexMatchp("awviPrintWindowForm" y~>hiForm))

   hiSetCurrentWindow(car(win))

)

Then, you setup the bindkey as :

 hiSetBindKey("Schematics" "<Key>2" "CCSkey() awviUpdateMenuCB()")

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 15 years ago

    Look at the OCEAN report() function (either in the documentation, or by typing ocnHelp('report) in the CIW).

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • swdesigner
    swdesigner over 15 years ago

     Is there an example I can refer to? If I just do

     report()

    cadence first tells me I need to run openResults, then selectResults

    the doc says selectResults( dcOp) which is a typo, it needs to be selectResults( "dcOp") or I get  "*Error* eval: unbound variable - dcOp"

    Then, I get openResults() to go through fine, but, after selectresults( "dcOp"), I get 

    stdobj@0x12d0e27c

    If I then do

    report(), I get

    *Info* no design parameters available for data type 'V' and another similar line with 'I'.

    report(?output "file") also doesn't do anything for me.

    Any help would be great.

    Thanks

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

    There's a typo in the documentation (in fact more than one). I'll file a CCR to get that fixed. The "dcOp" results give the node voltages and currents. What you need is the "dcOpInfo" results. So if you do:

    selectResult('dcOpInfo)
    report()

    And then you can experiment with other report() arguments as covered in the documentation. For example:

    report(?type "bjt" ?param "vce")

    Regards,

    Andrew.

    • 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