Stats

  • Locked Locked
  • Replies 2
  • Subscribers 148
  • Views 14386
  • 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

Starting analog environment and schematic editor

archive

I am writing few SKILL/OCEAN scripts that perform the analysis of simple circuits.
From those scripts, I would like to be able to start the Analog Design Environment interface and the Schematic Editor, so that extra data extraction could be done with the UI.

How can I do that such that the design, the design variables, the result directory, etc... is all set up, without inserting it manually in the UI forms?

How can I annotate the schematic from the script (e.g. Results->Annotate->DC operating options)?

Thanks in advance for your answer to this questions.
Marco Ballini


Originally posted in cdnusers.org by mballini
Parents
  • archive

    Thank you for your kind answer. I found I can start ADE from an OCEAN script, as you suggested. The problem is that I also need then to load all design variables which were set in the script into the ADE. I had a look at sev* functions, and they generally allow you to open forms to insert values which are stored in the current ADE sessions.

    E.g. I can start a session with:
    sevSession = sevStartSession()
    Choose the design
    sevDesignForm = sevChooseDesign(sevSession)
    then in the ADE click on "Results->Select..." (the design _has_ to be chosen first otherwise that won't work).

    I would like to do all those operations from the script.
    Also, the design variables are not set in this way, while I would like to load them in the ADE from the script without having to enter them manually in a form each time (many variables).
    Is this possible?

    At this point I also would like to open and annotate a schematic, ALL from the script with no manual operations in the form (that is the reason why I am using scripts, to avoid to do the same point-and-click operations each time).

    I saw many SKILL functions (sev* and asi*), which allow you to open a form, so I thought that it could be also be possible to set the values from the script need of opening the forms at all, to do things such as open and annotate a schematic automatically.
    Is this the case?

    Thanks again.
    Kind regards,
    mb



    Originally posted in cdnusers.org by mballini
Reply
  • archive

    Thank you for your kind answer. I found I can start ADE from an OCEAN script, as you suggested. The problem is that I also need then to load all design variables which were set in the script into the ADE. I had a look at sev* functions, and they generally allow you to open forms to insert values which are stored in the current ADE sessions.

    E.g. I can start a session with:
    sevSession = sevStartSession()
    Choose the design
    sevDesignForm = sevChooseDesign(sevSession)
    then in the ADE click on "Results->Select..." (the design _has_ to be chosen first otherwise that won't work).

    I would like to do all those operations from the script.
    Also, the design variables are not set in this way, while I would like to load them in the ADE from the script without having to enter them manually in a form each time (many variables).
    Is this possible?

    At this point I also would like to open and annotate a schematic, ALL from the script with no manual operations in the form (that is the reason why I am using scripts, to avoid to do the same point-and-click operations each time).

    I saw many SKILL functions (sev* and asi*), which allow you to open a form, so I thought that it could be also be possible to set the values from the script need of opening the forms at all, to do things such as open and annotate a schematic automatically.
    Is this the case?

    Thanks again.
    Kind regards,
    mb



    Originally posted in cdnusers.org by mballini
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.