File Exchange Pick of the Week

February 27th, 2008

Advanced MATLAB: Calling Simulink from MATLAB

I normally only have two posts a week, but I needed to throw in this extra post to announce a new blog by my buddy Seth. Seth will be discussing Simulink every week. This week, he is discussing batch simulations of Simulink from MATLAB [Click here]. He goes much deeper into the topic than I do in today’s video.

Please check out his blog [Click here] and be sure to let him know who sent you!

Video Content

iconFiles.jpgiconPod.jpglazy.jpg

4 Responses to “Advanced MATLAB: Calling Simulink from MATLAB”

  1. Ray Goldsworthy replied on :

    Hi, enjoyed the blog. Can you call compiled simulink models in a similar manner? I would like to compile simulink models using real-time workshop, but call those models from Matlab GUI….thanks, Ray

  2. Seth Popinchalk replied on :

    @Ray – Try using the Real-Time Workshop Rapid Simulation Target. You can set parameters, provide inputs and record outputs from your simulation. The interface is through the system command prompt, so your MATLAB code will not use the SIM command. Instead, you call the generated executable directly from your MATLAB GUI. Check out the documentation for running batch mode simulations:

    http://www.mathworks.com/access/helpdesk/help/toolbox/rtw/ug/f6817.html

    Good luck!

  3. Ram replied on :

    How can I simulate a model opened in a second MATLAB session from the current session?

    In my current session I will have a GUI to open a simulink model in a separate MATLAB session

    Thanks

  4. Doug replied on :

    @Ram,

    Why would you want to use two MATLAB sessions??

Leave a Reply

Wrap code fragments inside <pre> tags, like this:

<pre class="code">
a = magic(3);
sum(a)
</pre>

If you have a "<" character in your code, either follow it with a space or replace it with "&lt;" (including the semicolon).


MathWorks

Brett & Jiro share their favorite user-contributed submissions from the File Exchange.

These postings are the author's and don't necessarily represent the opinions of The MathWorks.