Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 3406
  • 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

Tools needed for Analog simulation & MATLAB interface

Kabal

 Hello, we are using MMSIM10, IC6.14.

 

Right now for example, i can save waveforms from my simulation as table, and then open them in MATLAB.

 What im looking at now is, how to make a co-simulation with matlab.

I looked already at several tutorials, one of them for example about spectre RF engine. Another about SimCoupler.

 

Here are my questions:

1) Am i correct that SimCoupler and SpectreRF Engine are basically doing the same job, except that the SpectreRF Engine is oriented more towards RF related applications? So, basically for general analog stuff its preferred to use SimCoupler?

2) To import the SpectreRF Engine in MATLAB simulink, i basically open the spectrerf.mdl located in .../MMSIM10/tools/spectre/simulink,   now where is the .mdl file for SimCoupler located? I cant find it within IC614 install folder, do i need to install some another tool?  I see the AMS Designer product talking about same stuff... is that what i need to install? If yes, then what is its short name in the install directory list?

Parents
  • Andrew Beckett

    There are two interfaces to Simulink. One from AMS Designer (that's the "SimCoupler" you are referring to; this is provided in the INCISIV stream these days), and one from Spectre. 

    The AMS Designer interface is for mixed-signal simulation - although that could be entirely analog.

    The spectre interface was provided by the SpectreRF team and may be used with transient or envelope simulation.

    So in practice the spectre interface would be the one to use for normal Analog simulation.

    For the AMS simulink interface, look at <ICinstDir>/doc/amsdMatSim/amsdMatSim.pdf which talks through the tutorial; the database is at <ICinstDir>/tools/dfII/samples/tutorials/AMS/MATLABCosimulation.tar.gz

    For the spectre simulink interface, look at  <MMSIMinstDir>/spectreRF/spectreRF.pdf (there's a chapter on it - chapter 10 in MMSIM10.1). For the tutorial, look in <MMSIMinstDir>/tools/spectre/examples/SpectreRF_workshop and there's SpectreRF_simulink_example.pdf and SpectreRF_simulink_example.tar.Z - a pdf and the database to try it out.

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    There are two interfaces to Simulink. One from AMS Designer (that's the "SimCoupler" you are referring to; this is provided in the INCISIV stream these days), and one from Spectre. 

    The AMS Designer interface is for mixed-signal simulation - although that could be entirely analog.

    The spectre interface was provided by the SpectreRF team and may be used with transient or envelope simulation.

    So in practice the spectre interface would be the one to use for normal Analog simulation.

    For the AMS simulink interface, look at <ICinstDir>/doc/amsdMatSim/amsdMatSim.pdf which talks through the tutorial; the database is at <ICinstDir>/tools/dfII/samples/tutorials/AMS/MATLABCosimulation.tar.gz

    For the spectre simulink interface, look at  <MMSIMinstDir>/spectreRF/spectreRF.pdf (there's a chapter on it - chapter 10 in MMSIM10.1). For the tutorial, look in <MMSIMinstDir>/tools/spectre/examples/SpectreRF_workshop and there's SpectreRF_simulink_example.pdf and SpectreRF_simulink_example.tar.Z - a pdf and the database to try it out.

    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.