Simulink Editor
Use the simulinkScreenshot function to take a screenshot of a Simulink® model or subsystem and display it in a figure window.
For example, this code loads the sf_car model and takes a screenshot of
it.
load_system("sf_car"); simulinkScreenshot("sf_car");
Starting in R2026b, Simulink settings are integrated into MATLAB® settings. Instead of appearing in a separate dialog box, Simulink settings are now located on panes in the MATLAB Settings dialog box.
You can still access Simulink settings from the Simulink Toolstrip. On the Modeling tab, select Environment > Simulink Settings. The MATLAB Settings dialog box opens to the Simulink pane, where you can specify general Simulink settings. To view editor or model file settings, in the navigation pane, expand Simulink and select Editor or Model File.
Using this command to open the Simulink settings is no longer supported.
slprivate('showprefs')Instead, use this command to open the MATLAB Settings dialog box, and then select Simulink.
preferences
Starting in R2026b, you can provide suggestions for improving Simulink and Stateflow® from the Simulink Editor. In the Simulink quick access bar located in the upper right corner of the editor, click the Feedback button.
Use Quick Mode in the Finder to search for model elements of the current system without loading referenced models or libraries. By searching without loading references, Quick Mode reduces search time for large model hierarchies.
In Quick Mode, the Finder displays matches from unloaded references as grayed-out results. Double-click a result to load references and view additional matches. Starting in R2026b, Quick Mode is the default search mode in Finder.
For more information, see Search Using Quick Mode.
Simulation Analysis and Performance
You can now organize your visualizations in the Simulation Data Inspector using up to eight independent tabs, each with its own subplot layout and settings. You can:
Add tabs with the New Tab button
. Reorder tabs by dragging.
Rename, close, or change tab color by right-clicking.
To manage tabs programmatically, use the Simulink.sdi.TabGroup object. This object is a container for Simulink.sdi.Tab
objects, each representing an open tab in the Simulation Data Inspector. To create, access,
and manage tabs, use these functions with the Simulink.sdi.TabGroup
object:
addTab— Add a new tab to the Simulation Data Inspector.getActiveTab— Get the active tab.getAllTabs— Get all tabs in the Simulation Data Inspector.getTabByIndex— Get a tab by index.getTabByName— Get a tab by name.
To manage individual tabs, use these functions with the Simulink.sdi.Tab
object corresponding to the tab of interest:
setActiveTab— Make a tab the active tab.closeTab— Close a tab.closeOtherTabs— Close all tabs except the specified tab.
Techniques to Speed Up Simulink Simulations is a new course that teaches you to:
Analyze models for configuration parameter settings that impact simulation performance using the Performance Advisor.
Analyze solver behavior that impacts simulation performance using the Solver Profiler.
Identify blocks and subsystems that contribute most to the overall compilation and execution time using the Simulink Profiler.
Choose appropriate simulation modes to accelerate the simulation of model reference hierarchies.
Avoid recompilation in batch and iterative simulations by using fast restart.
For more information, see Techniques to Speed Up Simulink Simulations.
Component-Based Modeling
Starting in R2026b, you can use In Bus Element and Out Bus Element blocks as input and output ports on Variant Subsystem or Variant Assembly Subsystem blocks, alongside existing port types Inport, Outport, Connection Port (Simscape), and control ports Enable, Trigger, and Reset.
For example, consider a Variant Subsystem block
Controller. The first input port of the Controller
block is an In Bus Element block named sensorInputs that
groups related signals speed, position, and
temperature. The second input port is also an In Bus
Element block named operationMode that groups related signals
type and status. The Controller
block has two variant choices, Linear Controller and Nonlinear
Controller. Each variant choice contains corresponding input ports for
sensorInputs and operationMode.
When you simulate the model, Simulink maps the In Bus Element blocks between
Controller and its variant choices by matching the port names
sensorInputs and operationMode so that the correct
signals route to each variant choice.
When using bus element ports in a Variant Subsystem or Variant Assembly Subsystem block, these restrictions apply:
Bus element block port names at the Variant Subsystem interface must be unique.
Routing individual bus elements to each variant choice is not supported. In Bus Element and Out Bus Element blocks must specify the bus port.
Unlike Outport blocks, the Specify output when source is unconnected and Output function call parameters are not available for Out Bus Element blocks in a Variant Subsystem block.
In a child Variant Subsystem block, when neither the Built-in empty choice nor the Built-in passthrough choice parameter is selected, the block requires at least one active variant choice during simulation.
Starting in R2026b, for child Variant Subsystem blocks where neither parameter is selected, Simulink evaluates the variant control expressions of the parent block and the child Variant Subsystem block before reporting a diagnostic. If the child Variant Subsystem block is inactive because its parent block is inactive, Simulink suppresses the diagnostic, as the inactive state is inherited and does not require resolution. Diagnostics are reported only when the variant control expressions of the parent and child blocks indicate a configuration that requires action. For example, when the variant control expressions do not overlap and the child Variant Subsystem block can never become active under any parent condition.
Previously, Simulink reported a diagnostic for every inactive child Variant Subsystem block that had no active variant choice, regardless of whether the parent block was also inactive. This behavior produced diagnostics in cases where the child block inherited its inactive state from the parent block and no resolution was needed.
The table demonstrates how the relationship between variant control expressions of the parent block and child Variant Subsystem block determines whether diagnostics for inactive child blocks are reported or suppressed.
| Relationship | Parent Variant Control Expression | Child Variant Control Expression | Diagnostic Behavior |
|---|---|---|---|
| Variant control expressions of child block are equal to those of the active variant choice of the parent. |
|
| Diagnostic is suppressed. |
| Variant control expressions of child block are mutually exclusive from those of the active variant choice of the parent. |
|
| Diagnostic is reported. |
| Variant control expressions of child block are a subset of the active variant choice of the parent. |
|
| Diagnostic is reported only when the variant choice of the parent is active. |
| Variant control expressions of child block are a superset of those of the active variant choice of the parent. |
|
| Diagnostic is suppressed. |
Consider the Nonlinear Controller block, which is a variant choice
within the Variant Subsystem block Controller, and which has
a variant control expression V == 2 || V == 3. Inside this block, there is
a child Variant Subsystem block saturationLogic with the
variant control expression V == 2 || V == 4.
If you set the variant control variable
Vto1, both the parentNonlinear Controllerblock and childsaturationLogicblock are inactive. Simulink suppresses diagnostics for the child block because its inactivity is inherited from the inactive parent.If you set
Vto2, both the parent and child blocks are active. No diagnostic is reported.If you set
Vto3, the parent blockNonlinear Controlleris active. The child blocksaturationLogicremains inactive sinceV == 3does not satisfy the variant control expression of the child block. Simulink reports a diagnostic for the child block because it is expected to be active when the parent is active, but no valid variant choice is selected.
Starting in R2026b, you can use symbolic dimensions to specify array sizes for variant
parameters (Simulink.VariantVariable) in models configured for AUTOSAR code generation. In the
generated C code, the code generator uses the symbolic dimension as a system constant to size
the variant parameter arrays.
To define a symbolic dimension, add a system constant in the Architecture
Data section of a Simulink data dictionary linked to the AUTOSAR component. Set the
Specification property of the variant parameter to an
AUTOSAR.Parameter object, and set the dimensions of this object to
reference the system constant name. Define the variant control as a
Simulink.VariantControl object. Set the value of the object to an
AUTOSAR.Parameter object mapped to a system constant, and set the
activation time to code compile. Code generation exports the
symbolic dimension and the variant control as system constants and the variant choices as
variation point proxy entries in the generated ARXML. For more information, see Configure Variant Parameter Values for AUTOSAR Elements (AUTOSAR Blockset).
In this example, the model uses a variant parameter K, defined as a
Simulink.VariantVariable with two choices. The conditions for the choices
are defined as Simulink.VariantExpression objects
VExpr_Cond1 and VExpr_Cond2, which represent the
variant control expressions V == 1 and V == 2,
respectively. The Specification property of K is set
to an AUTOSAR.Parameter object KSpec with its dimensions
set to [1,P], where P is a system constant from the
architecture data that specifies the symbolic dimension.
The model defines the variant parameter K and its associated objects in
the Design Data section of a Simulink data dictionary. The data dictionary defines the system constant
P in the Architecture Data section. For more
information on defining system constants in the Architecture Data
section, see Manage AUTOSAR Architectural Data With Data Dictionaries (AUTOSAR Blockset).
When you generate code for this model, the stub file Rte_Cfg.h defines
the system constants for the symbolic dimension P, the variant control
V, and the variation
points.
/* File: Rte_Cfg.h */
/* Variation points */
#define Rte_SysCon_VExpr_Cond1 (V == 1)
#define Rte_SysCon_VExpr_Cond2 (V == 2)
#define P 3
#define Rte_SysCon_P P
#define V 2
#define Rte_SysCon_V VThe header file mArchDataAsDim.h uses the system constant
Rte_SysCon_P as the symbolic dimension for the variant parameter array
K. The #if preprocessor conditionals guard the
variant parameter definition based on the variant
control.
/* File: mArchDataAsDim.h */
/* PublicStructure Variables for Internal Data, for system '<Root>' */
typedef struct {
float64 Output1[Rte_SysCon_P]; /* '<Root>/Gain2' */
} ARID_DEF_mArchDataAsDim_T;
/* Parameters (default storage) */
struct P_mArchDataAsDim_T_ {
#if Rte_SysCon_VExpr_Cond1 || Rte_SysCon_VExpr_Cond2
sint16 K[Rte_SysCon_P]; /* Variable: K
* Referenced by: '<Root>/Gain2'
*/
#endif
};The source file mArchDataAsDim.c assigns the values for each choice of
the variant parameter. The code conditionally compiles the values based on the variant control
V.
/* File: mArchDataAsDim.c */
/* Block parameters (default storage) */
P_mArchDataAsDim_T mArchDataAsDim_P = {
#if Rte_SysCon_VExpr_Cond1 || Rte_SysCon_VExpr_Cond2
/* Variable: K
* Referenced by: '<Root>/Gain2'
*/
#if Rte_SysCon_VExpr_Cond1
{ 2, 3 }
#elif Rte_SysCon_VExpr_Cond2
{ 4, 5, 6 }
#endif
#endif
};Rte_SysCon_P to iterate over the variant parameter
array./* File: mArchDataAsDim.c */
/* Model step function */
void mArchDataAsDim_Step(void)
{
...
for (i = 0; i < Rte_SysCon_P; i++) {
mArchDataAsDim_ARID_DEF.Output1[i] = (float64)mArchDataAsDim_P.K[i] *
tmpIRead[i];
}
...
}Project and File Management
Data Management
Starting in R2026b, the Root Inport Mapper tool supports mapping signal data by port name for bus element ports. To select this map mode, in the Map Mode section of the Root Inport Mapper tool, select Port Name.
Corresponding to this change, the mapDataToInport and getSlRootInportMap functions now support the
new mapping mode option "PortName".
Block Enhancements
Display measurements data using engineering notation
The Scope, Floating Scope and Scope Viewer display the cursor measurements, peaks, statistics, and bilevel measurements using engineering notation.
Note
The Signal Statistics panel, Peaks panel, and the bilevel measurements panel require a DSP System Toolbox™ or Simscape™ license.
Access style settings from context menu
You can now also access the style settings of the Scope, Floating Scope and Scope Viewer by right-clicking the scope display and selecting Style.
Support for calendar date and time
You can now visualize the simulation data and the measurements data in Scope, Floating Scope and Scope Viewer using the real-world calendar date and time. For more information on how to enable this support, see the Enable DateTime on T-Axis parameter description in the scope reference page.
The Display block from the Customizable Blocks library can now display multidimensional signals. Previously, the block could only display scalar signals.
By default, the block displays multidimensional signals in a grid. To set the color of the grid lines, select the block. In the Property Inspector, on the Design tab, in the Text component, select a new color for Grid Color. To turn the grid off, in the same location, toggle the Show grid for non-scalar signals button off.
![A Display block displays the value of the signal line connected to a Constant block. The Constant block value is the matrix [5 8; 9 4]. The Display block displays the element values in a grid with green lines.](display-block-connected-to-multidimensional-signal.png)
When you enable the Evaluate attribute for a
combobox mask parameter, Simulink evaluates both predefined and user‑defined values as MATLAB expressions.
Starting in R2026b, you can set a combobox mask parameter to
evaluate only the custom values you enter.
You can enable the Evaluate only custom values option of a
combobox parameter in the Behavior section
of the Property Editor pane in the Mask Editor.
To enable the Evaluate only custom values option from the command
line, see Simulink.MaskParameter.Behavior
Starting in R2026b, you can set the column type in a custom table parameter to
combobox from the Mask Editor or programmatically. To set the
column type in the Mask Editor, in the Property Editor pane, click
Columns, and then set Type to
combobox.
To add a combo box column from the command line, see Control Custom Table Parameter Programmatically.
Starting in R2026b, Icon Editor has these enhancements:
Add dynamic text — Add expression text on a masked block icon by using the Expression Text element from the Tools pane. To edit an expression, double-click the Expression Text element on the canvas and write a JavaScript® expression such as
"Gain value is " + parameterName. To customize expression behavior, use the options in Expression Text section in the Element Properties pane.For more information, see Display Text Dynamically on Block Icon Based on Parameter Values.
Position an icon element relative to another element — The updated Relative Position section in the Element Properties pane now makes it easier to position an element relative to another element or the canvas.
For more information, see Position Elements Relatively Using Relative Positioning.
Inherit domain styles for Simscape block icons — You can now make Simscape block icons inherit port domain styles by using the Inherit Styles option in the Format section. For example, to inherit a style based on a right-side port and the electrical domain for a Variable Resistor block, you would set Inherit Styles to
R0: Electrical. Previously, domain styles could be inherited only by using the Port Binding option in the toolstrip.Display port labels on masked block icons — You can now display port labels from the blocks inside the mask directly on masked block icons by selecting the Show port labels from block check box in the Icon Settings section.