The release of R2014b brought a time-honored Stateflow feature up to the model level: Simulink Functions. These blocks, analogous to stand-alone MATLAB functions, promote modularity and reuse by... 더 읽어보기 >>

Yesterday, I was giving a training to new hires at MathWorks and one of the attendees asked me how to hold a value in Simulink. Of course, my answer was that there are many ways to hold a value... 더 읽어보기 >>

Did you know that with Stateflow, it is possible to monitor which state is currently active, and use that information in the rest of the Simulink model? This feature is named Active State Output. The screenshot below shows how to do this for one of the charts in the example Temporal Logic Using the AT Function.... 더 읽어보기 >>

Have you noticed a new block in the Stateflow Library since R2012b? The MATLAB Chart block uses MATLAB as the action language for states and transitions in Stateflow. This means that you... 더 읽어보기 >>

This week I have been experimenting with a feature released in R2010b that I have not used before: Stateflow Atomic Subcharts The Problem I am currently working on a model architecture where... 더 읽어보기 >>

As we all know, in Simulink there are always multiple ways to implement a functionality. One situation where I often hesitate when choosing an implementation is conditional execution. I will share... 더 읽어보기 >>

Today Guy Rouleau is back to introduce the code generated from the For Each Subsystem. I created an example model implementing the same functionality as in my previous post, but using... 더 읽어보기 >>

This week I asked Michael Carone to introduce a relatively new Stateflow capability, Simulink Functions. Did you ever want to put a Simulink block inside of a Stateflow chart?  Well, if you... 더 읽어보기 >>