| Contents | Index |

| On this page… |
|---|
Explicit solver used in model containing Physical Networks blocks |
The Editing Mode parameter controls the Simscape Editing Mode functionality, which allows you to open, simulate, and save models that contain blocks from add-on products in Restricted mode, without checking out add-on product licenses, as long as the products are installed on your machine. Simscape add-on products include SimDriveline™, SimElectronics®, SimHydraulics, and SimMechanics. Use this functionality to perform multidomain physical modeling and simulation while minimizing the number of required licenses.
Note Unless your organization uses concurrent licenses, see the Simscape product page on the MathWorks Web site for specific information on how to install add-on products on your machine, to be able to work in Restricted mode. |
The parameters in the Physical Networks Model-Wide Simulation Diagnostics section let you configure your preferences for solver-related warnings when you simulate models containing blocks from Simscape libraries.
The parameters in the Data Logging section let you log simulation data to workspace.
This pane appears only if your model contains a block from the Simscape libraries (including Simscape add-on products).
Set the editing mode of the model to either Full or Restricted.
Default: Full
Sets the editing mode of the model to Full. In this mode, you can make any modifications to the model.
When you open a model in Full mode, the license manager checks out all the add-on product licenses for the blocks present in the model.
When you switch from Restricted to Full mode, the license manager checks whether the required add-on product licenses are available and checks them out. If some of the add-on product licenses are not available, the license manager issues an error and the model stays in Restricted mode.
Sets the editing mode of the model to Restricted. In this mode, you can simulate the model, generate code, and make limited modifications.
When you open a model in Restricted mode, the license manager does not check out the add-on product licenses.
When you switch from Full to Restricted mode, all the add-on product licenses for the blocks present in the model remain checked out until the end of the MATLAB session.
| Parameter: EditingMode |
| Type: string |
| Value: 'Full' | 'Restricted' |
| Default: 'Full' |
Specify whether or not the system will issue a warning or error upon simulation if the model uses an explicit solver.
Default: warning
Makes the system issue a warning upon simulation if the model uses an explicit solver.
It is possible to choose any variable-step or fixed-step solver for models containing Simscape blocks. When you first create a model, the default Simulink solver is ode45. However, implicit solvers, such as ode14x, ode23t, and ode15s, are a better choice for a typical model. In particular, for stiff systems, implicit solvers typically take many fewer timesteps than explicit solvers, such as ode45, ode113, and ode1. To alert you to a potential issue, the system issues a warning when you use an explicit solver in a model containing Simscape blocks.
Makes the system issue an error upon simulation if the model uses an explicit solver.
If your model is stiff, and the use of explicit solvers undesirable, you may choose to select this option to avoid troubleshooting errors in the future.
Turns off issuing a warning or error upon simulation with explicit solver.
For models that are not stiff, explicit solvers can be effective, often taking fewer timesteps than implicit solvers. If you work with such models and use explicit solvers, select this option to turn off the warning upon simulation.
| Parameter: ExplicitSolverDiagnosticOptions |
| Type: string |
| Value: 'warning' | 'error' | 'none' |
| Default: 'warning' |
Switching from the Default Explicit Solver to Other Simulink Solvers
Specify whether or not the system will issue a warning or error upon simulation if the Zero-crossing control parameter in the Solver pane is set to Disable all, which means that zero-crossing control is globally disabled.
Default: warning
Makes the system issue a warning upon simulation if zero-crossing control is globally disabled.
Makes the system issue an error upon simulation if zero-crossing control is globally disabled.
| Parameter: GlobalZcOffDiagnosticOptions |
| Type: string |
| Value: 'warning' | 'error' |
| Default: 'warning' |
Enabling or Disabling Simulink Zero Crossing Detection
Specify whether or not the system logs simulation data to workspace.
Default: none
Performs no data logging upon simulation.
Upon simulating the model, logs all simulation data from Simscape blocks to a workspace variable specified by the Workspace variable name parameter.
| Parameter: SimscapeLogType |
| Type: string |
| Value: 'none' | 'all' |
| Default: 'none' |
Specify the name of the workspace variable for simulation data logging.
Default: simlog
The default value logs all the simulation data to a workspace variable named simlog.
You can specify any other valid string as the workspace variable name.
| Parameter: SimscapeLogName |
| Type: string |
| Value: any valid value |
| Default: 'simlog' |
Lets you limit data points being logged, by skipping time steps. Logs data points for the first time step and every nth time step thereafter, where n is the decimation factor.
Default: 1
The default value logs simulation data for each step.
You can specify any other positive integer number. For example, specifying 2 logs data points for every other time step, while specifying 10 logs data points for just one in ten steps.
Saving data to workspace can slow down the simulation and consume memory. Use this parameter to limit the number of data points saved.
Another way to limit the number of data points saved is using the Limit data points check box in conjunction with the Data history (last N steps) parameter. The two methods work independently from each other and can be used separately or together.
| Parameter: SimscapeLogDecimation |
| Type: numeric |
| Value: any positive integer value |
| Default: 1 |
Specify that the number of data points logged to workspace is limited to the value corresponding to the number of simulation steps specified by the Data history (last N steps) parameter.
Default: on
Limits the number of data points exported to workspace to those for the number of steps specified by the Data history (last N steps) parameter.
Does not limit the number of data points.
Saving data to workspace can slow down the simulation and consume memory. Use this parameter to limit the number of data points saved.
Another way to limit the number of data points saved is using the Decimation parameter. The two methods work independently from each other and can be used separately or together.
You must select the Limit data points check box before specifying the number of steps in the Data history (last N steps) parameter.
| Parameter: SimscapeLogLimitData |
| Type: string |
| Value: 'on' | 'off' |
| Default: 'on' |
Specify the number of simulation steps to limit the number of data points output to workspace. The workspace variable defined by the Workspace variable name parameter contains the data points corresponding to the last N steps of the simulation, where N is the value you specify for the Data history (last N steps) parameter. If the simulation contains fewer steps than the number specified, the workspace variable contains the data points for the whole simulation.
Default: 5000
The default value logs simulation data for the last 5000 steps.
You can specify any other positive integer number.
Saving data to workspace can slow down the simulation and consume memory. Use this parameter to limit the number of data points saved.
You must select the Limit data points check box before specifying the number of steps in the Data history (last N steps) parameter.
| Parameter: SimscapeLogDataHistory |
| Type: numeric |
| Value: any positive integer value |
| Default: 5000 |
![]() | Configuration Parameters | Bibliography | ![]() |

Learn more about Simulink through this collection of videos, articles, technical literature and the Getting Started with Simulink Guide.
| © 1984-2012- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |