Simulink Editor
In R2026a, the context menus that appear when you right-click the Simulink® model canvas or model elements such as blocks, signal lines, and annotations are changing. This image shows the differences between the context menu that opens when you right-click a Constant block in R2025b and the context menu that opens when you right-click the same block in R2026a.
In addition to conventional menu items, the R2026a context menu design includes interactive elements such as buttons, text boxes, radio buttons, check boxes, and drop-down lists. To view a tooltip that describes the action you can take by pressing a button, pause your pointer on the button icon.
This table lists some of the common buttons in the context menus of blocks.
| Button | Tooltip |
|---|---|
 | Model Data Editor |
 | Referenced Variables |
 | Open in Model Explorer |
 | Explain with Simulink Copilot |
 | Block Parameters |
 | Properties |
 | Comment out the block. |
 | Comment through the block. |
 | Uncomment the block. |
 | Cut |
 | Copy |
 | Paste |
For a tooltip showing a list of all the actions that you can take by pressing the buttons in a button row, click the name of the button row. For each button, the tooltip shows the button icon followed by a description of the button action. When there is only one button in a button row, clicking the name of the button row presses the button instead of opening a tooltip.
To open the help documentation, in the upper right corner of the context menu, click the
Open help documentation button 
.
You can find formatting options in the format bar, for example, options to change fonts
and colors, show or hide block names, show or hide the content preview of a subsystem, and
auto-arrange the model. You can also find clipboard options such as copy and paste there. To
expand or collapse the format bar, click the arrow button 
at the top of the context menu.
You can set the values of certain parameters and properties directly in the context menu using text boxes, radio buttons, check boxes, and drop-down lists. For example, to set the value of a Constant block, right-click the block, and in the Value box, enter the new value.
To add information overlays such as units or execution order to a model, right-click the model canvas and pause your pointer on Information Overlays. Then, select an overlay option.
In R2025b, you could access options that belong to an app such as the HDL Coder™ app or the Polyspace® Code Verifier app through menu items such as HDL Code or Polyspace. In R2026a, app-specific options are located in app sections. App sections are not shown by default. To access app-specific options, you must add the relevant app section to the context menu.
For example, this image highlights the options in the R2025b Constant block context menu that you can access in R2026a by adding app sections.
To add an app section to the context menu, pause your pointer on Select Apps, and then select the app. When you add an app section, the same app windows and toolstrip tabs open as when you click the app icon on the Apps tab in the Simulink Toolstrip. Alternatively, open the app from the Simulink Toolstrip. When you open an app, the corresponding app section appears in the context menu.
If you are unsure whether a menu option you use is part of an app, or you know the option is part of an app but are unsure of which app, check this table. The table lists the apps associated with some of the most common R2025b context menu items.
| R2025b Context Menu Item | App |
|---|---|
| C/C++ Code |  Embedded Coder |
 Simulink Coder | |
| Coverage |  Coverage Analyzer |
| Design Verifier |  Design Verifier |
| Fixed-Point Tool |  Fixed-Point Tool |
| HDL Code |
|
| Identify Modeling Clones |  Clone Detector |
| Linear Analysis Points |  Linearization Manager |
| Metrics Dashboard | The options for this app are no longer available in the context menu. |
| Model Advisor |  Model Advisor |
| Model Slicer |  Model Slicer |
| Model Transformer | The options for this app are no longer available in the context menu. |
| Observers |  Simulink Test |
| PLC Code |  PLC Coder |
| Polyspace |
|
| Requirements or Requirements at This Level |  Requirements Manager |
 Requirements Viewer | |
| Test Harness |
|
You can add multiple app sections. To add another app section, pause your pointer on Select Apps again, and select a different app.
In the model in which you add an app section, the app section appears in all context menus and persists across Simulink sessions. For example, if you right-click a block and add an app section, and then right-click a signal line in the same model, the signal line context menu also shows the app section you added. However, if you open a context menu in a different model, the context menu does not show the app section. If you open a context menu when none of the actions of an app section are available, the context menu might not show the app section.
To collapse an app section, click the down arrow button 
in the upper left of the app section. To expand the app
menu section, click the arrow again.
To remove an app section from the context menu, pause your pointer on the app icon at the left edge of the app-specific section and click Close App. Alternatively, pause your pointer on Select Apps, and then cancel the app selection. You can also collapse the app section and then click the X on the right.
In addition to adding and removing app sections, you can also customize the context menus with the new design by adding widgets or disabling widget actions. For information, see Customize Simulink Context Menu Using Extension Points.
For lookup tables showing how you can access R2025b context menu options in R2026a, see Find Simulink Context Menu Options. The tables cover the options in the context menus of Constant blocks, top level models, signal lines, and text annotations. For a list of options that are no longer available in the Simulink context menus going forward, see Options that have been removed from Simulink context menus.
Starting in R2026a, when you select multiple blocks on the Simulink canvas, you can use the Move In and Move Out buttons on the Simulink Toolstrip to move the blocks into or out of a subsystem. If the selected blocks are connected to a subsystem, use the Move In button to move the blocks into the subsystem. If the selected blocks are inside a subsystem, use the Move Out button to move the blocks up one level from the subsystem. This allows you to reorganize the model while preserving signal connections and block properties after refactoring. This feature eliminates the need to manually move blocks in or out of the subsystem when required.
The Move In and Move Out buttons appear in the Move section of the Multiple tab of the Simulink Toolstrip. Alternatively, you can use the context menu for move operations. Right-click the selected blocks and select Move > Move In to move blocks into a subsystem, or Move > Move Out to move blocks up one level. You can undo (Ctrl+Z) and redo (Ctrl+Y) the move operation to reverse or restore any changes.
For more information, see Move Blocks Into and Out of Subsystems.
Simulink Preferences has been renamed Simulink Settings. Use Simulink Settings to specify Simulink editing environment options and default behaviors. To open Simulink Settings, in the Simulink Toolstrip, on the Modeling tab, in the Evaluate and Manage section, select Environment > Simulink Settings.
Previously, to share a Model Finder database, you had to
share the database file with team members, who would then manually import it in their
settings folder using the Model Finder user interface (UI). Starting in R2026a, you can
directly share and reuse model databases by using a shared repository and customizing the
Model Finder UI with the MATLAB
sl_customization function. By registering the customizations
programmatically, you only need to do a one-time setup to access shared databases.
To set up a shared database, use Model Finder to create a database containing information of project related Simulink models. Store this database in a shared repository, such as a file server, cloud storage, or source code management (SCM) system.
To access the shared database, team members have to specify a customization to import the
database to their Model Finder in the sl_customization.m file. After
importing, the shared database appears in the Model Finder UI, and team members can search
for models in the database.
To import the shared database wireless_systems.db from a shared
repository and assign it the alias Shared Database, specify this
customization in the customization file. Use the ModelFinderCustomizer class
function on the customization manager object cm to specify the
customization.
function sl_customization(cm) dbPath = fullfile("simulink","modelfinderdatabases","wireless_systems.db"); cm.ModelFinderCustomizer.importDatabase(dbPath,“Shared Database”); end
For more information, see Configure, Share, and Search Databases.
In R2026a, the context menus that appear when you right-click the Simulink model canvas or model elements such as blocks, signal lines, and annotations are changing. To maximize the compactness of the new context menus and the convenience of accessing frequently used options, some options have been removed from the context menus. The tables list some of these options and alternative ways to take the associated actions.
Block Context Menu
| R2025b Context Menu Action | Action in R2026a |
|---|---|
| Right-click the block and select Find Referenced Variables. | Navigate into the model or component whose referenced variables you
want to find. Right-click the canvas, and then click the Referenced
Variables button |
| Right-click the block and select Format > Flip Block Name. | Select the block. In the Simulink Toolstrip, on the Format tab, click Flip Name. |
| Right-click the block and select Format > Fit to Content. | Select the block. In the Simulink Toolstrip, on the Format tab, click Fit to Content. |
Right-click any type of block representing a subsystem, for example an If Action Subsystem block, and select one of these options:
| Select any type of block representing a subsystem, for example an If Action Subsystem block. In the Simulink Toolstrip, on the Format tab, in the Ports section, click the Port Labels button and select one of these options:
|
| Right-click the block and select Format > Bring to Front. | Select the block. In the Simulink Toolstrip, on the Format tab, click the
Bring to front button  . |
| Right-click the block and select Format > Send to Back. | Select the block. In the Simulink Toolstrip, on the Format tab, click the
Send to back button  . |
Top Model Canvas Context Menu
| R2025b Context Menu Action | Action in R2026a |
|---|---|
| Right-click the model canvas and select Sample Time > All. | Right-click the model canvas and select Information Overlays. Then, select all overlays under Sample Time. |
| Right-click the model canvas and select Sample Time > Off. | Right-click the model canvas and select Information Overlays. Then, clear all overlays under Sample Time |
Right-click the model canvas and set Animation
Speed to Fast,
Medium, Slow, or
None. | In the Simulink Toolstrip, on the Debug tab, set
Animation speed to Fast,
Medium, Slow, or
None. |
Annotation Context Menu
| R2025b Context Menu Action | Action in R2026a |
|---|---|
| Right-click the annotation and select Format > Bring to Front. | Select the annotation. In the Simulink Toolstrip, on the Format tab, click the
Bring to front button . |
| Right-click the annotation and select Format > Send to Back. | Select the annotation. In the Simulink Toolstrip, on the Format tab, click the
Send to back button . |
Right-click the annotation and select one of these options:
| Right-click the annotation, and then click the Properties button
|
| Right-click the annotation and select Enable Tex Commands. | Right-click the annotation, and then click the Properties button
|
| Right-click the annotation and select Show in Library Browser. | Select the annotation. In the Simulink Toolstrip, on the Library tab, click Show Annotations in Library Browser. |
Simulation Analysis and Performance
The Simulink Profiler now provides information about how compilation time is distributed among compilation phases and among referenced models that simulate in normal mode. To view the compilation information, use one of these approaches:
In the Simulink Profiler, in the Profiler Report pane, click Show Execution Stack View
. Then, expand the simulate
and compilePhase nodes.Inspect the
rootExecNodeproperty of theSimulink.profiler.Dataobject returned with the results of the profiling simulation.
In previous releases, the Simulink Profiler provided only the total time required to compile the model.
Starting in R2026a, you can launch Model Slicer directly from the Breakpoints List when your Simulink model pauses at a breakpoint. This integration allows you to trace the signal values back to their sources so you can isolate the root cause of unexpected behavior in large models. A Simulink Check™ license is required to launch Model Slicer from the Breakpoints List.
In the Breakpoints List, Model Slicer:
Sets the starting point to the signal associated with the current breakpoint.
Updates the slice criteria to match the selected breakpoint when you add a new breakpoint or switch between existing breakpoints.
When model simulation hits a breakpoint, perform these steps to use Model Slicer from the Breakpoints List:
On the Debug tab, click Breakpoints List. The Breakpoints List opens at the bottom of the Simulink Editor.
In the Breakpoints List, click the Debug using Slicer button
to debug the signal. You can also:Add a starting point by clicking the Add Starting Point button
.View the upstream and downstream flow of the signals in the model using
button.
Click the Close Model Slicer button
to close the Model Slicer.
For more information, see Breakpoints List and Trace Faulty Signal Paths Using Model Slicer at Signal Breakpoints (Simulink Check).
Live streaming of data to XY visualizations in the Simulation Data Inspector, Record
block, and XY Graph block is supported again. Such live streaming was supported in R2024b
and earlier, but was not supported in R2025a. To live stream data to an XY visualization,
data must be plotted as a scatter plot. To change the line style to only data markers, click
Visualization Settings 
and in the Axes section, select
Markers and clear Line. Trend lines are not
supported while live streaming XY data.
You can now view the approximate storage size of data logged to the Simulation Data Inspector when a simulation is paused or stopped.
To interactively access storage size information, you can:
Add the Size column to the signal table in either the Inspect or Compare pane to display a specific property for all logged signals in the table.
View metadata for a signal, run, or comparison in the new Size row of the Properties pane.
For more information, see Inspect Signal, Run, and Comparison Metadata.
To programmatically access storage size information, you can:
Use the new
NumBytesproperty of aSimulink.sdi.RunorSimulink.sdi.Signalobject corresponding to a signal or run in the Simulation Data Inspector.Get a table of signal information, including signal size, for all signals in a run using the new
Simulink.sdi.getSizeInfofunction.
Comparison reports in the Simulation Data Inspector let you share comparison data without MATLAB dependency. When you generate comparison reports from the Simulation Data Inspector, the plots are now interactive. You can zoom, pan and use data cursors in the plots. Prior to R2026a, plots were static images that did not have any interactive functionality.
For more information about generating comparison reports, see Create Interactive Comparison Reports.
Component-Based Modeling
When a bus element port does not specify a Simulink.Bus object, you can
now create and assign Simulink.Bus objects from the Property
Inspector or port dialog box by clicking 
. The software compiles the model and then creates and
assigns the Simulink.Bus objects. In previous releases, creating and
assigning Simulink.Bus objects to bus element ports requires multiple
steps.
When you create Simulink.Bus objects after opening the
Property Inspector or port dialog box, to update the Data
type list, select Refresh data types from the
list. In previous releases, clicking 
updates the entire dialog box, including the
Data type list.
When a bus element port specifies a Simulink.Bus object
and the incoming bus hierarchy does not match the specified bus object, the Property
Inspector and port dialog box now display only the mismatched elements in red.
Mismatched elements include:
Elements that are accessed by blocks but are missing from the bus object
Elements that are specified by bus objects but do not match incoming elements
Parents of mismatched elements
In previous releases, when an element does not match, the entire bus hierarchy is red, not just the mismatched elements.
For more information, see In Bus Element and Out Bus Element.
You can now highlight the blocks within a bounded region created by Variant Start and Variant End blocks to distinguish them visually from other components. This feature enables you to trace data flow and logic specific to each variant implementation in large and complex models.
Consider the slexVariantStartAndEnd model, which contains the
Variant Start and Variant End blocks that define the
bounded regions.
To identify the blocks within the bounded region created at Port 2 of the Variant Start block:
In the Simulink Toolstrip, on the Debug tab, select Information Overlays > Start End Bounded Regions.
On the Variant Start End Bounded Regions tab, expand slexVariantStartAndEnd/Variant Start and choose Port 2. Alternatively, click the output signal connected to Port 2 of the Variant Start block to highlight the blocks within its bounded region.
Block highlighting applies only to the model in which it is enabled and does not extend to the bounded regions in the referenced models. To highlight blocks within a bounded region of a referenced model, open the referenced model and select the Start End Bounded Regions option within that model. For more information, see Control Variant Condition Propagation using Variant Start and Variant End Blocks.
When you automatically generate variant configurations by using Variant Manager or the
Simulink.VariantManager.generateConfigurations function, you can use
variant control variables with the same name defined in multiple sources, except in the
preconditions to be applied when generating configurations.
In the Generate Configurations tab of the Variant Manager window, the Configure Control Variables table has a new Source column that shows the source of the control variables used by the model hierarchy. The generated configurations also identify variables with multiple definitions by their source.
Starting in R2026a, you can simulate models that have variant configurations defined and
stored in an associated Simulink.VariantConfigurationData object without
installing the Variant Manager for Simulink support package.
You can view the variant configurations and constraints saved in the
Simulink.VariantConfigurationData object. If the object is defined in the
base workspace, double-click the object or use the open function at the
MATLAB command line. If the object is in a data dictionary, select the object in the
Model Explorer. Selecting the object opens the
Simulink.VariantConfigurationData dialog box in a read-only mode. For more
information, see Manage Variant Configurations Without Simulink Model.
You can run single or multiple parallel simulations on the model programmatically without specifying a named variant configuration. For example, these commands run successfully without the support package installed:
openExample("slexVariantManagement.slx"); sim("slexVariantManagement.slx")
Simulink.SimulationInput object by specifying a named variant
configuration, as shown below, results in an error if the support package is not
installed.simInp = Simulink.SimulationInput("slexVariantManagement.slx") simInp = setVariantConfiguration(simInp,'LinInterExpWithNoise') sim(simInp,"ShowProgress","on");
Previously, since R2022b, you could not simulate models containing variant configurations unless you installed the Variant Manager for Simulink support package.
In R2026a, when you activate a named variant configuration in Variant Manager for Simulink, the operation completes sooner for large models that contain many referenced models compared to R2025b.
In previous releases, variant conditions specified in variant blocks did not propagate to the blocks that form signal loops. The blocks forming these loops remained active during simulation and code generation. Starting in R2026a, variant conditions propagate through signal loops. The blocks inside and outside the loop along the signal path activate or deactivate based on their associated variant conditions. As a result, only blocks required for the active variant are simulated and included in the generated code, eliminating the unnecessary inclusion of inactive blocks.
For example, in this model, the variant condition V == 1 from the
Variant Source block propagates to the Sum,
Integrator, Gain, and Unit Delay blocks
that form the signal loop and to the Constant block outside the loop. These
blocks activate only when V == 1 evaluates to
true.
In R2026a, you can generate code for a model that includes a protected model when the
protected model contains variant parameters with code compile
variant activation time. The generated code for the parent model does not contain preprocessor
conditional statements for the declarations and definitions of these variant parameters. This
code is similar to code generated for such a model when you set the variant parameter
activation time to update diagram analyze all choices.
In this example, the parent model refers to a protected model that uses two variant
parameters K and Kv, that use a variant control
V, with code compile activation time.
When you generate code for this model using Embedded Coder, the code for the parent model defines the variant parameters without
conditionally compiling them based on variant control V, and the code
contains only the active choice of the variant
parameters.
/* File: varparam_top_model.h */
/* Model block global parameters (default storage) */
extern real_T rtP_K; /* Variable: K
* Referenced by: '<Root>/model_block_top'
*/
extern real_T rtP_Kv; /* Variable: Kv
* Referenced by: '<Root>/model_block_top'
*//* File: varparam_top_model_data.c */
/* Model block global parameters (default storage) */
real_T rtP_K = 2.0; /* Variable: K
* Referenced by: '<Root>/model_block_top'
*/
real_T rtP_Kv = 3.0; /* Variable: Kv
* Referenced by: '<Root>/model_block_top'
*/
/* File: varparam_ref_model.c */
/* Output and update for referenced model: 'varparam_ref_model' */
void varparam_ref_model(real_T *rty_Out1)
{
/* Gain: '<Root>/Gain' incorporates:
* Constant: '<Root>/Constant'
*/
*rty_Out1 = rtCP_Gain_Kv * rtCP_Constant_K;
}If the parent model uses the same variant parameter as the protected model with
code compile activation time, then the generated code for the
parent model guards that variant parameter using the preprocessor conditionals
#if and #elif.
In this example, the parent model also uses the variant parameter
K.
The code generator uses the macro V to emit #if and
#elif guards that conditionally compile
K.
/* File: varparam_top_model_has_vparam_types.h */
#ifndef V
#define V 1
#endif/* File: varparam_top_model_has_vparam.h */
/* Model block global parameters (default storage) */
#if V == 1 || V == 2
extern real_T rtP_K; /* Variable: K
* Referenced by: '<Root>/model_block_top'
*/
#endif
extern real_T rtP_Kv; /* Variable: Kv
* Referenced by: '<Root>/model_block_top'
*//* File: varparam_top_model_has_vparam_data.c */
/* Model block global parameters (default storage) */
real_T rtP_Kv = 3.0; /* Variable: Kv
* Referenced by: '<Root>/model_block_top'
*/
#if V == 1
real_T rtP_K = 2.0; /* Variable: K
* Referenced by: '<Root>/model_block_top'
*/
#elif V == 2
real_T rtP_K = 4.0; /* Variable: K
* Referenced by: '<Root>/model_block_top'
*/
#endifStarting in R2026a, you can specify the value of Simulink.VariantControl objects as Boolean values. You can also set the value of
a variant control object to a Simulink.Parameter object with a Boolean value.
This enhancement is supported for simulation and code generation workflows, including code
generation targets such as AUTOSAR. For
example,
vCtrl = Simulink.VariantControl(Value=true,ActivationTime="startup");vCtrlSP = Simulink.VariantControl(Value=Simulink.Parameter(Value=true));
This model uses a Simulink.VariantControl object vCtrl
with a Boolean value to switch between the choices of a Variant Source
block.
This code snippet shows the definition of the variant control vCtrl and
its usage in the model step function in the code generated using Simulink
Coder™.
/* Exported block parameters */
boolean_T vCtrl = true; /* Variable: vCtrl
* Referenced by:
* '<Root>/Constant'
* '<Root>/Constant1'
* '<Root>/vCtrl'
*/
/* Model step function */
void modelVCwithBool_step(void)
{
/* SignalConversion generated from: '<Root>/Variant Source' */
if (vCtrl) {
/* Outport: '<Root>/Out1' incorporates:
* Constant: '<Root>/Constant'
*/
modelVCwithBool_Y.Out1 = modelVCwithBool_P.Constant_Value;
} else {
/* Outport: '<Root>/Out1' incorporates:
* Constant: '<Root>/Constant1'
*/
modelVCwithBool_Y.Out1 = modelVCwithBool_P.Constant1_Value;
}
}You can now specify callback functions for Multiversion Co-simulation components in the Multiversion Co-simulation block dialog. These are the supported block callbacks and their corresponding model callbacks in Simulink.
CosimPreLoadFcn-PreLoadFcnCosimPostLoadFcn-PostLoadFcnCosimInitFcn-InitFcnCosimStartFcn-StartFcnCosimStopFcn-StopFcn
Before R2026a, only PreLoadFcn and PostLoadFcn were supported and had to be defined in a separate script. You can now manage component callbacks directly on the block dialog.
When you protect a Simulink model that uses variant parameters (Simulink.VariantVariable objects) with startup variant
activation time, make the variant parameters tunable during simulation by specifying only the
associated variant controls (Simulink.VariantControl objects) as tunable parameters. In previous releases, you
also had to specify the variant parameters as tunable.
Variant parameters with a variant activation time other than
startup are not tunable in protected models, so you cannot
select their variant controls as tunable parameters.
For example, this image shows the two variant parameters K and
Kv that use the Simulink.VariantControl object
V.
When you protect the model that uses these variant parameters by using Protected
Model Creator (Simulink Coder), select V as a tunable parameter for simulation to
configure K and Kv as tunable.
When you protect the model using the Simulink.ModelReference.protect (Simulink Coder) function, specify the
Simulink.VariantControl objects by using the TunableParameters (Simulink Coder)
name-value
argument.
Simulink.ModelReference.protect(modelName,TunableParameters=["V"]);When you get the list of tunable parameters for such a protected model using the Simulink.ProtectedModel.getTunableParameters (Simulink Coder) function, the function returns
only the Simulink.VariantControl objects that you specified as tunable
parameters.
The Simulink.ModelReference.protect function reports a warning if the
specified variant control has a variant activation time other than
startup.
Project and File Management
Data Management
The Open Signal Editor button in the Signal Editor block
now opens a version of the Signal Editor
tool that is synchronized with the Signal Editor block. In releases prior to
R2026a, all instances of the Signal Editor tool had the same characteristics.
For more information, see Differences Between the Signal Editors.
The block version of the Signal Editor tool has these changes:
When you click Open Signal Editor, the Signal Editor tool now opens populated with the active scenario. The active plot shows the last signal in the scenario.
A new Active column in the hierarchy shows the active scenario for the block. To change the active scenario, click the associated button.
New input properties support the corresponding block parameters.
Signal Editor Block Signal Editor Interface Output as bus object
Output a bus signal
Bus object
Select bus object
Enable zero-crossing detection
Enable zero-crossing detection
Form output after final data value by
Form output after final data value by
Sample time
Sample time Note
The Interpolate data and Unit parameters of the Signal Editor tool are only reflected in the Signal Editor block when the block parameter Use properties from is set to
Signal data in MAT file.To change the active scenario in the Signal Editor tool, click the associated button in the hierarchy Active column, and then click Save. Closing the tool updates the Signal Editor block.
Block parameters become read-only when you open the Signal Editor tool. To change control from the Signal Editor tool to the Signal Editor block, close the Signal Editor tool.
To see parameter changes for an active signal from the Signal Editor block in the associated Signal Editor tool, click the active signal in the signal hierarchy.
To aid the transition between the docked Type Editor and Interface Editor as you navigate between Simulink models and architecture models, the Type Editor supports new functionality and has updated button icons.
When you create a type, you can enter a new name right away. In previous releases, you must double-click the default name to enter a new name.
To sort types, you can now click individual column headers. In previous releases, the Type Editor does not support sorting.
When you specify a bus object in the Type column, the Type Editor displays the bus hierarchy regardless of whether you include the
Bus:prefix. In previous releases, the bus hierarchy displays only when you include theBus:prefix.When you rename a bus object, the Type Editor updates any references to the bus object in other bus objects. The Type Editor does not update references to the bus object in value types.
The Link external sources button has a new icon
. The former Link external sources icon is now
used by the Open standalone Type Editor button 
. This change aligns the button icons used by the
Type Editor and the Interface Editor for similar
actions. In previous releases, the Open standalone Type Editor button has a
different icon 
.
For more information, see Type Editor and Interface Editor (System Composer).
Block Enhancements
Starting in R2026a, the C
Function block addresses the limitations mentioned in C and C++ Language Limitations and
Limitations which
were previously applicable to locally specified C and C++ custom code. To specify
custom code locally, the Configure
custom code settings
parameter must be set to Use Block Custom
Code.
Before R2026a, the Neighborhood control block for the Neighborhood Processing Subsystem supported only these settings for the Output size parameter:
Same: The output matrix has the same dimensions as the input matrix.Full: The output matrix is larger than the input matrix and contains an element for each neighborhood that includes at least one unpadded value from the input matrix.Valid: The output matrix is smaller than the input matrix and contains elements for only the input matrix elements whose neighborhoods did not contain padded values outside the input matrix.
Starting in R2026a, you can generate other output sizes from the Neighborhood
Processing Subsystem block. The Neighborhood block parameter
Output size supports a new value,
Custom, which enables a new Neighborhood block
parameter, Padding size.
The Padding size parameter accepts a vector of nonnegative scalars
that define the amount of padding for the start and end, respectively, of each dimension of
the input matrix. For example, for a 2-dimensional input matrix, provide a vector of the
form [ where each element is a nonnegative scalar.
a
b
c
d]abcd
The following screenshot demonstrates the parameter behavior by passing a 5-by-5 matrix
through Neighborhood Processing Subsystem blocks that have different padding
sizes. Each subsystem uses a 1-by-1 neighborhood and returns the input value without
modifying it. For the padded values, each subsystem uses the constant value
0.
![Model that passes a 5-by-5 matrix through three Neighborhood Processing Subsystem blocks. Each element of the input matrix contains the value 1. The first subsystem has a padding size of "[0 0 0 0]" and produces a copy of the input matrix. The second subsystem has a padding size of "[1 0 2 0]" and returns a matrix that contains a row of zeros and two columns of zeros above and to the left of the input matrix. The third subsystem has a padding size of "[0 1 0 2]" and returns a matrix that contains a row of zeros and two columns of zeroes below and to the right of the input matrix.](neighborhood_processing_subsystem_custom_padding_model.png)
Use custom padding sizes to configure the dimensions of the output data in image processing tasks.
Starting in R2026a, you can use the C Caller block
dialog box buttons 
and 
to add global variables from custom code or delete global
arguments from the block, respectively. To automatically infer global variables from the
custom code using the block dialog box, use the 
button.
Starting in R2026a, the If block uses a new parser that allows you to:
Modify the If block input port labels to meet your modeling requirements. This change allows you to tailor the logical expressions within the block using custom names. Previously, you could only use the default names such as,
u1,u2, and so on for inputs.
Use a range of logical expressions that were not previously supported, including expressions that use:
Tunable parameters.
General MATLAB expressions, such as
x1 > x2 + 5.Data objects such as
Simulink.Parameter,Simulink.Signalwith custom storage classes. For more information, see Create and Apply Storage Class Defined in User-Defined Package (Embedded Coder).Fixed-point data type.
Enumerated data type.
MATLAB structure arrays.
Expressions with:
Arithmetic functions —
ceil,floor,abs, andsign.Trigonometric functions —
sin,cos,tan,asin,acos,atan,atan2,sinh,cosh, andtanh.Exponential, logarithmic and root functions —
log,log10,exp, andsqrt.
These capabilities are not supported for the Model Slicer tool in Simulink Check.
Starting in R2026a, you can programmatically add and position cursors on plots in the Record block and Playback block. For example, add two cursors to the Playback block and position the cursors at 3 and 7 seconds.
set_param("MyModel/Playback","ShowCursor",2) set_param("myModel/Playback","CursorPositions",[3,7])
You can also get descriptive statistics for signals in the Record and
Playback blocks using the new signal ID parameter. To get a set of
descriptive statistics for a signal using the signal ID, use Simulink.analytics.getMetrics. To get a single descriptive statistic, use
Simulink.sdi.Signal object functions such
as max and
min.
pbSigIDs = get_param("myModel/Playback","SignalIDs"); >> sigStats = Simulink.analytics.getMetrics(pbSigIDs(1))
sigStats =
struct with fields:
min: -0.9962
max: 0.9996
peakToPeak: 1.9957
mean: 0.1744
median: 0.3115
std: 0.6704
rms: 0.6863To focus your analysis on a specific time range, combine cursor placement and signal
statistics. Define the time span with cursors set either programmatically or interactively.
To analyze signal statistics within this time span, use get_param to
retrieve the cursor positions. Then use the positions as the start and end times in
Simulink.analytics.getMetrics.
sigBounds = get_param("myModel/Playback","CursorPositions"); sigStats = Simulink.analytics.getMetrics(pbSigIDs(1),sigBounds(1),sigBounds(2))
sigStats =
struct with fields:
min: -0.9962
max: 0.6570
peakToPeak: 1.6532
mean: -0.3948
median: -0.4646
std: 0.5189
rms: 0.6421
Dashboard panels are virtual dashboards to which you can add blocks from the Dashboard library (including the Customizable blocks library) or the Aerospace Blockset™ library. The panels float above the model canvas and follow you through the model hierarchy. Starting in R2026a, you can add blocks to dashboard panels using the quick insert menu.
To do so, enter edit mode. First, select the panel. Then, in the Simulink Toolstrip, on the Panels tab, click Edit Panels. If needed, resize the panel to make the panel big enough to hold the block you want to add by dragging the panel edges outward. Adding blocks that are bigger than the panel is not supported.
To add the block, double-click where you want to add the block. You must click a blank space on the panel. The quick insert menu appears. Start entering the name of the block you want to add. Select the block you want to add in the list of search results. The new block appears in the panel.
For more information about dashboard panels, see Getting Started with Dashboard Panels.
The Edit block connects to a parameter or variable value in your model. You can change the connected value before or during simulation by entering a new value in the edit box. When you use the version of the Edit block in the Customizable Blocks library, you can customize the appearance of the block to look like an edit box in an existing digital interface.
Choose from a list of WYSIWYG (what you see is what you get) fonts that look the same on all platforms.
Change the font size.
Change the text color.
Make the text bold, italic, or underlined.
Change the text position within the block.
Add a background image or choose a background color.
Add a foreground image.
Use the Edit block with other dashboard blocks to build an interactive dashboard of controls and indicators for your model.
Dashboard panels can have multiple tabs. You can now programmatically switch which tab a
panel displays using the simulink.dashboard.switchPanelTab function. For example, you can use this
capability to create a dashboard that switches tabs when you click a button by entering the
simulink.dashbaord.switchPanelTab function in the callback function
that runs when you click the button.
simulink.dashboard.switchPanelTab(model,tab)
model is the handle or name of the top-level model containing the tab to
which you want to switch. Specify the handle as a scalar, and the name as a string or
character array. For information about how to get a model handle, see Get Handles and Paths.
tab is the name of the tab to which you want to switch, specified as
a string or character array. To use the
simulink.dashbaord.switchPanelTab function, the model you specify
in the input arguments must be open. Loading the model is not sufficient.
Starting in R2026a, you can define and manage all types of parameter and port constraints by using the enhanced Constraints tab in Mask Editor.
Enhancements to the Constraints tab include:
Add all types of parameter and port constraints from the Constraint Gallery panel on the left side of the Constraints tab instead of selecting the constraint type from the toolstrip.
Simulink displays predefined constraints, called as Commonly Used Constraints, in the Constraint Browser panel. You can associate these constraints with mask parameters without creating them manually.
To avoid unintended changes, shared constraint files are locked. To modify a shared constraint file, click Edit File on the toolstrip.
Associate parameters and ports to their respective constraints by using the Associations section of the Constraints tab. Previously, you associated constraints to parameters from the Parameters and Dialog tab.
For more information, see Author Parameter and Port Constraints Using Standalone Constraint Manager.
MATLAB System properties with validation functions such as mustBeNonpositive and mustBeMember are validated in the mask dialog box of a MATLAB
System block when focus is moved to another control.
When you save a mask callback file with a model, use the fully qualified names to invoke
custom functions. If the callback file resides in a folder within the model, to avoid
path-related errors, reference the function with its full path. For example, if the name of
the model is engine.slx, the mask callback is
vehicles.m, and the custom function name is
calculateForce, then invoke the function as
engine.vehicles.calculateForce() in the mask callback file.
Graphical Icon Editor has these enhancements:
Default authoring mode for block icons — Graphical Icon Editor is now the default authoring mode to design masked block icons. To switch to mask drawing commands, in the Authoring Mode section of the toolstrip, click Graphical and then select Drawing Commands.
Customize shape of block frame — To customize the shape of the block frame, in the Icon Properties pane go to the Transform section, and select a shape from the Frame list. Click
to modify the frame as desired and then click close
button. Preview the icon in Simulink to view the modified block frame.Quick insert element shapes — Search for and insert shapes on the canvas. Double-click the icon canvas and type the name of a shape. A drop-down list of available shapes appears in the drop-down list. Select a shape from the list to insert it into the canvas. Alternatively, in the Tools pane, select Shape Finder to search and insert shapes.
Add port labels to block icons — To specify a port label, in Tools pane, select Port Label.
Properties pane enhancements — Updates to the Icon Properties, Element Properties and Text Properties panes make it easier to navigate and set various properties. You can also automatically generate port labels and associate parameters and expressions with text elements.
For more information, see Graphical Icon Editor Overview.
Use the Parameter Tree container in the Mask Editor to display mask parameters in a nested structure. The Parameter Tree container supports Group Box containers and Edit, Check Box, Popup, and Combo Box parameters.
For more information, see Use Mask Containers to Group Parameters on Mask Dialog Box. To programmatically
create and group mask parameters in a parameter tree container, use methods of Simulink.dialog.ParameterTree class.
Starting in 2026a, Simulink displays predefined constraints in the Constraints tab of the Mask Editor. You can associate these constraints with mask parameters without creating them manually. These constraints are available only for the Parameter Constraint type. The available constraints include:
NumericNumericScalarNumericScalarPositiveNumericScalarPositiveIntegerNumericScalarPositiveZero
The predefined constraints are read-only, and you cannot modify their rules. To associate a constraint with a mask parameter, select the parameter from the Associations section.
For more information, see Use Port Constraints to Validate Input and Output Signals.
When you modify a MATLAB System class associated with a MATLAB System block, the corresponding mask definition XML file can become outdated. Starting in R2026a, when you modify a MATLAB System class, a notification banner prompts you to open the Mask Editor and perform Save Mask. This action updates the mask definition in the XML file.
