{"id":17021,"date":"2024-09-12T14:39:31","date_gmt":"2024-09-12T18:39:31","guid":{"rendered":"https:\/\/blogs.mathworks.com\/simulink\/?p=17021"},"modified":"2024-09-12T14:39:31","modified_gmt":"2024-09-12T18:39:31","slug":"whats-new-in-simulink-in-r2024b","status":"publish","type":"post","link":"https:\/\/blogs.mathworks.com\/simulink\/2024\/09\/12\/whats-new-in-simulink-in-r2024b\/","title":{"rendered":"What’s New in Simulink in R2024b?"},"content":{"rendered":"
\"\"<\/img><\/a><\/div>
Looking at the <\/span>Release Notes<\/span><\/a> for Simulink in R2024b, what stands out the most to me is that we have improved a lot of already existing features. <\/span><\/div>
Let's look at my favorites of those enhancements.<\/span><\/div>

New Details panel for Quick Insert<\/span><\/h2>
When it was introduced many releases ago, the <\/span>Quick Insert menu<\/span><\/a> was a huge game changer. It completely changed the way to add blocks to a Simulink model. Instead of navigating the Library Browser and dragging the block into the model, Quick Insert allows you to just type the name of the block in the canvas and hit Enter.<\/span><\/div>
In R2024b, we are adding a Details panel to this menu. It provides a description of the block and hyperlinks to documentation and examples:<\/span><\/div>
\"\"<\/img><\/div>

Starting a Simulation in Debug mode<\/span><\/h2>
In R2023b, we introduced a new way to debug Simulink models, with the <\/span>in-canvas debugger<\/span><\/a>. Since then, the way to launch the block-by-block debugger was to add breakpoints on signal lines so the debugger would break as soon as the condition is met.<\/span><\/div>
In R2024b, we decided to enable the Step Over button in the toolstrip when the simulation is stopped. Starting the simulation with this button will pause the simulation just before the first block executes, ready to debug from t=0. This is especially useful when the problem you are investigating is not obvious to capture with a change in value of a signal. Here is an example:<\/span><\/div>
\"StepOver2.gif\"<\/img><\/div>

Connecting blocks across model hierarchy<\/span><\/h2>
The ability to programmatically create Simulink models is a major power of MATLAB + Simulink. For those using the <\/span>add_block<\/span><\/a> and <\/span>add_line<\/span><\/a> functions, you will love the new <\/span>Simulink.connectBlocks<\/span><\/a>.<\/span><\/div>
Let's take this model:<\/span><\/div>
\"\"<\/img><\/div>
I can connect the Gain block inside Subsystem A to the Bias block inside Subsystem B using this code:<\/span><\/div>
blk1 = <\/span>'testConnect\/A\/Gain'<\/span>;<\/span><\/span><\/div><\/div>
blk2 = <\/span>'testConnect\/B\/Bias'<\/span>;<\/span><\/span><\/div><\/div>
Simulink.connectBlocks(blk1,blk2);<\/span><\/span><\/div><\/div><\/div>
This will automatically add the Inport and Outport blocks required and connect all those blocks together. <\/span><\/div>
\"\"<\/img><\/div>
In this case the result is one line of code instead of two calls to <\/span>add_blocks<\/span> and three calls to <\/span>add_line<\/span>. For more complex cases across deep hierarchies, the benefit is more significant. Look at the <\/span>documentation for <\/span>Simulink.connectBlocks<\/span><\/a> to see all the possibilities.<\/span><\/div>

Improved Bus handling in Model Reference Conversion Advisor<\/span><\/h2>
Let's say I have a simple model with a bus signal entering a Subsystem:<\/span><\/div>
\"\"<\/img><\/div>
I can now <\/span>convert<\/span><\/a> it to a Referenced Model and the resulting model will look exactly like the original, and the bus element ports will include the entire bus definition, so no need for bus objects.<\/span><\/div>
\"\"<\/img><\/div>

Customize Sample Time Colors<\/span><\/h2>
Since the beginning of time, <\/span>sample time colors<\/span><\/a> in Simulink have always been the same: D1 is red, D2 is green, D3 is blue, etc. In R2024b, we finally implemented the long-standing request of allowing users to customize sample time colors.<\/span><\/div>
It's quite simple. Create a <\/span>simulink.sampletimecolors.Palette<\/span><\/a> object, define your colors in RGB or <\/span>Hexadecimal color code<\/span><\/a> and apply it:<\/span><\/div>
h = simulink.sampletimecolors.Palette(<\/span>\"myColors\"<\/span>);<\/span><\/span><\/div><\/div>
h.DiscreteSampleTimeColors = [<\/span>\"#aed6f1\"<\/span>; <\/span>\"#85c1e9\"<\/span>;<\/span>\"#3498db\"<\/span>;<\/span>\"#2874a6\"<\/span>];<\/span><\/span><\/div><\/div>
simulink.sampletimecolors.applyPalette(h);<\/span><\/span><\/div><\/div><\/div>
Here the resulting sample time legend for my \"50 shades of blue\" palette:<\/span><\/div>
\"\"<\/img><\/div>

Adding Model blocks and Referenced Subsystems made easier<\/span><\/h2>
This one is very straightforward: Drag a Simulink file from the Current Folder Browser into a Simulink model, and we automatically insert a Model or Subsystem block referencing it.<\/span><\/div>
\"AddModel.gif\"<\/img><\/div>

Now it's your turn<\/span><\/h2>
Look at the <\/span>Release Notes<\/span><\/a> and let us know what your favorite feature in Simulink R2024b is, or if there are other features you would like me to cover on the blog.<\/span><\/div>\n
\n<\/div>