Stats

  • Locked Locked
  • Replies 5
  • Subscribers 125
  • Views 1959
  • 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

Spectre and Simulink cosimulation - Problem on defining cosimulation inputs

Milad M

Dear All,

     I have done a successful Spectre/Simulink cosimulation. Then, I used Optimization Toolbox of MATLAB to find the best value of the cosimulation input in order to minimize the cosimulation output. I will explain the MATLAB codes if someone is interested.

     Now, I want to use this method to optimize the parameters of a sample circuit. I'd like to define cosimulation inputs some different things such as the value of a resistor or a capacitor or even the pulse width of a pulse voltage source in the circuit. But, looking at the tutorials, it is only possible to define cosimulation inputs the instance sources such as Vin:wave.

    How can I define cosimulation inputs something different? 

Sincerely Yours,

Milad

Parents

  • Hi Milad,

    I don't think this is really possible. You could of course use some kind of voltage-controlled resistor or capacitor (a vccr can be a voltage-controlled resistor, for example) and do it that way.

    If you only want to optimise the component values once for each simulation, you'd be better off having Matlab create some include file with parameter values that the main netlist could reference. Something like that.

    Regards,

    Andrew.

Reply

  • Hi Milad,

    I don't think this is really possible. You could of course use some kind of voltage-controlled resistor or capacitor (a vccr can be a voltage-controlled resistor, for example) and do it that way.

    If you only want to optimise the component values once for each simulation, you'd be better off having Matlab create some include file with parameter values that the main netlist could reference. Something like that.

    Regards,

    Andrew.

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.