Stats

  • Locked Locked
  • Replies 4
  • Subscribers 143
  • Views 13322
  • 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

STIMULI control via ocean script

Genas

I have an ocean script where I’m running a simulation and I want to set a value for one of the input stimuli (“trm_db”) but for some reason its not letting me do that, I am using this command to set the variable but when I check the maestro view stimuli GUI after running the simulation, I do not see this variable set to this value.

 ocnxlStimuliData(?inputs '(((name "trm_db") (nodes ("trm_db" "/gnd!")) (enabled t) (tranType "dc") (srcType "Voltage") (instParameters (dc("3v") type("dc"))))))

I guess I'm missing something

  • Andrew Beckett

    The ocnxl function will only affect the OCEAN script. It will not update the settings in the Maestro view.

    Andrew.

  • Genas
    in reply to Andrew Beckett

    Thanks for this information. Do you know of any method or option to update the settings in the Maestro view. I saw a solution on the cadence support but it requires opening the GUI to get the current form. I want any solution that doesnt involve opening the GUI, just updating the settings via skill.

       formId = hiGetCurrentForm()

        foreach(choice formId~>artStmBox~>choices

           formId->artStmBox->value = list(choice)

           formId->artStmEnabled->value = t

           formId->artStmTranType->value = "sin"

           formId->dc->value = "2"

           artStmChangeCB(formId)

        );foreach

    Also, (leveraging on this solution), is it possible to get the form ID without using hiGetCurrentForm()

  • Andrew Beckett
    in reply to Genas

    I'm not sure there's a public way at the moment. You should contact customer support, as there ought to be a "mae" function to do this.

    Andrew.

  • Genas
    in reply to Andrew Beckett

    Thanks, I have contacted customer support

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.