| Simulink® | |
| On this page… |
|---|
Specify what diagnostic action Simulink® software should take, if any, when it detects a condition that could compromise the integrity of data defined by the model, as well as the Data Validity parameters that pertain to code generation, and are used to debug a model.
Set the parameters displayed.
The options are typically to do nothing or to display a warning or an error message.
A warning does not terminate a simulation, but an error does.
Select the how Simulink software resolves signals to Simulink.Signal objects in the MATLAB® workspace.
Default: Explicit only
Do not perform implicit signal resolution. Only explicitly (locally) specified signal resolutions occur.
Perform implicit signal resolution wherever possible without posting any warnings.
Perform implicit signal resolution wherever possible, posting a warning of each implicit resolution.
Use the Signal Properties dialog box (see Signal Properties Dialog Box) to specify explicit resolution for signals.
Use the State Attributes pane on dialog boxes of blocks that have discrete states, e.g., the Discrete-Time Integrator block, to specify explicit resolution for discrete states.
Multiple signals can resolve to the same signal object and have the properties that the object specifies.
The MathWorks discourages using implicit signal resolution except for fast prototyping, because implicit resolution slows performance, complicates model validation, and can have nondeterministic effects. Simulink software provides the disableimplicitsignalresolution function, which you can use to change settings throughout a model so that it does not use implicit signal resolution.
| Parameter: SignalResolutionControl |
| Type: string |
| Value: 'UseLocalSettings' | 'TryResolveAll' | 'TryResolveAllWithWarning' |
| Default: 'UseLocalSettings' |
| Application | Setting |
|---|---|
| Debugging | No impact |
| Traceability | No impact |
| Efficiency | No impact |
| Safety precaution | Explicit only |
Discrete-Time Integrator block
Select the diagnostic action to take if the Product block detects a singular matrix while inverting one of its inputs in matrix multiplication mode.
Default: none
Simulink software takes no action.
Simulink software displays a warning.
Simulink software terminates the simulation and displays an error message.
| Parameter: CheckMatrixSingularityMsg |
| Type: string |
| Value: 'none' | 'warning' | 'error' |
| Default: 'none' |
| Application | Setting |
|---|---|
| Debugging | No impact |
| Traceability | No impact |
| Efficiency | No impact |
| Safety precaution | error |
Product block
Select the diagnostic action to take if Simulink software could not infer the data type of a signal during data type propagation.
Default: none
Simulink software takes no action.
Simulink software displays a warning.
Simulink software terminates the simulation and displays an error message.
| Parameter: UnderSpecifiedDataTypeMsg |
| Type: string |
| Value: 'none' | 'warning' | 'error' |
| Default: 'none' |
| Application | Setting |
|---|---|
| Debugging | No impact |
| Traceability | No impact |
| Efficiency | No impact |
| Safety precaution | error |
Select the diagnostic action to take when signals exceed specified minimum or maximum values.
Default: none
Simulink software takes no action.
Simulink software displays a warning.
Simulink software terminates the simulation and displays an error message.
Use a block's Output minimum or Minimum parameter to specify the minimum value that the block should output.
Use a block's Output maximum or Maximum parameter to specify the maximum value that the block should output.
Enable this diagnostic to check whether block outputs exceed the minimum or maximum values that you specified.
When Simulation range checking is enabled, Simulink software performs signal range checking at every time step during a simulation. Setting this diagnostic to warning or error can cause a decrease in simulation performance.
| Parameter: SignalRangeChecking |
| Type: string |
| Value: 'none' | 'warning' | 'error' |
| Default: 'none' |
| Application | Setting |
|---|---|
| Debugging | warning or error |
| Traceability | warning or error |
| Efficiency | none |
| Safety precaution | error |
Select the diagnostic action to take if the value of a signal or parameter is too large to be represented by the signal or parameter's data type.
Default: warning
Simulink software takes no action.
Simulink software displays a warning.
Simulink software terminates the simulation and displays an error message.
| Parameter: IntegerOverflowMsg |
| Type: string |
| Value: 'none' | 'warning' | 'error' |
| Default: 'warning' |
| Application | Setting |
|---|---|
| Debugging | No impact |
| Traceability | No impact |
| Efficiency | No impact |
| Safety precaution | error |
Select the diagnostic action to take if the value of a block output is Inf or NaN at the current time step.
Default: none
Simulink software takes no action.
Simulink software displays a warning.
Simulink software terminates the simulation and displays an error message.
| Parameter: SignalInfNanChecking |
| Type: string |
| Value: 'none' | 'warning' | 'error' |
| Default: 'none' |
| Application | Setting |
|---|---|
| Debugging | No impact |
| Traceability | No impact |
| Efficiency | No impact |
| Safety precaution | error |
Select the diagnostic action to take during code generation if a Simulink object name (the name of a parameter, block, or signal) begins with rt.
Default: error
Simulink software takes no action.
Simulink software displays a warning.
Simulink software terminates the simulation and displays an error message.
The default setting (error) causes code generation to terminate with an error if it encounters a Simulink object name (parameter, block, or signal), that begins with rt.
This is intended to prevent inadvertent clashes with generated identifiers whose names begins with rt.
| Parameter: RTPrefix |
| Type: string |
| Value: 'none' | 'warning' | 'error' |
| Default: 'error' |
| Application | Setting |
|---|---|
| Debugging | No impact |
| Traceability | No impact |
| Efficiency | No impact |
| Safety precaution | error |
Select the diagnostic action to take when a parameter downcast occurs during simulation.
Default: error
Simulink software takes no action.
Simulink software displays a warning.
Simulink software terminates the simulation and displays an error message.
A parameter downcast occurs if the computation of block output required converting the parameter's specified type to a type having a smaller range of values (for example, from uint32 to uint8).
This diagnostic applies only to named tunable parameters.
| Parameter: ParameterDowncastMsg |
| Type: string |
| Value: 'none' | 'warning' | 'error' |
| Default: 'error' |
| Application | Setting |
|---|---|
| Debugging | No impact |
| Traceability | No impact |
| Efficiency | No impact |
| Safety precaution | error |
Select the diagnostic action to take if a parameter overflow occurs during simulation.
Default: error
Simulink software takes no action.
Simulink software displays a warning.
Simulink software terminates the simulation and displays an error message.
A parameter overflow occurs if Simulink software encounters a parameter whose data type's range is not large enough to accommodate the parameter's ideal value (the ideal value is either too large or too small to be represented by the data type). For example, suppose that the parameter's ideal value is 200 and its data type is uint8. Overflow occurs in this case because the maximum value that uint8 can represent is 127.
Parameter overflow differs from parameter precision loss, which occurs when the ideal parameter value is within the range of the data type and scaling being used, but cannot be represented exactly.
Both parameter overflow and precision loss are quantization errors, and the distinction between them can be a fine one. The Detect overflow diagnostic reports all quantization errors greater than one bit. For very small parameter quantization errors, precision loss will be reported rather than an overflow when
where
Max is the maximum value representable by the parameter data type
Min is the minimum value representable by the parameter data type
Slope is the slope of the parameter data type (slope = 1 for integers)
Videal is the ideal value of the parameter
| Parameter: ParameterOverflowMsg |
| Type: string |
| Value: 'none' | 'warning' | 'error' |
| Default: 'error' |
| Application | Setting |
|---|---|
| Debugging | No impact |
| Traceability | No impact |
| Efficiency | No impact |
| Safety precaution | error |
Select the diagnostic action to take when a parameter underflow occurs during simulation.
Default: none
Simulink software takes no action.
Simulink software displays a warning.
Simulink software terminates the simulation and displays an error message.
Parameter underflow occurs when Simulink software encounters a parameter whose data type does not have enough precision to represent the parameter's ideal value because the ideal value is too small.
When parameter underflow occurs, casting the ideal value to the data type causes the parameter's modeled value to become zero, and therefore to differ from its ideal value.
| Parameter: ParameterUnderflowMsg |
| Type: string |
| Value: 'none' | 'warning' | 'error' |
| Default: 'none' |
| Application | Setting |
|---|---|
| Debugging | No impact |
| Traceability | No impact |
| Efficiency | No impact |
| Safety precaution | error |
Select the diagnostic action to take when parameter precision loss occurs during simulation.
Default: warning
Simulink software takes no action.
Simulink software displays a warning.
Simulink software terminates the simulation and displays an error message.
Precision loss occurs when Simulink software encounters a parameter whose data type does not have enough precision to represent the parameter's value exactly. As a result, the modeled value differs from the ideal value.
Parameter precision loss differs from parameter overflow, which occurs when the range of the parameter's data type, i.e., that maximum value that it can represent, is smaller than the ideal value of the parameter.
Both parameter overflow and precision loss are quantization errors, and the distinction between them can be a fine one. The Detect Parameter overflow diagnostic reports all parameter quantization errors greater than one bit. For very small parameter quantization errors, precision loss will be reported rather than an overflow when
where
Max is the maximum value representable by the parameter data type.
Min is the minimum value representable by the parameter data type.
Slope is the slope of the parameter data type (slope = 1 for integers).
Videal is the full-precision, ideal value of the parameter.
| Parameter: ParameterPrecisionLossMsg |
| Type: string |
| Value: 'none' | 'warning' | 'error' |
| Default: 'warning' |
| Application | Setting |
|---|---|
| Debugging | No impact |
| Traceability | No impact |
| Efficiency | No impact |
| Safety precaution | error |
Select the diagnostic action to take when an expression with tunable variables is reduced to its numerical equivalent.
Default: none
Simulink software takes no action.
Simulink software displays a warning.
Simulink software terminates the simulation and displays an error message.
If a tunable workspace variable is modified by Mask Initialization code, or is used in an arithmetic expression with unsupported operators or functions, the expression is reduced to a numeric expression and therefore cannot be tuned.
| Parameter: ParameterTunabilityLossMsg |
| Type: string |
| Value: 'none' | 'warning' | 'error' |
| Default: 'none' |
| Application | Setting |
|---|---|
| Debugging | No impact |
| Traceability | No impact |
| Efficiency | No impact |
| Safety precaution | error |
Select the diagnostic action to take if the model attempts to read data from a data store in which it has not stored data in this time step.
Default: Use local settings
For each data store defined by a Data Store Memory block, use the setting specified by the block. This option disables the diagnostic for global data stores (i.e., data stores defined by Simulink.Signal objects).
Disables this diagnostic for all data stores accessed by the model.
Displays diagnostic as a warning at the MATLAB command line.
Halts the simulation and displays the diagnostic in an error dialog box.
| Parameter: ReadBeforeWriteMsg |
| Type: string |
| Value: 'UseLocalSettings' | 'DisableAll' | 'EnableAllAsWarning' | 'EnableAllAsError' |
| Default: 'UseLocalSettings' |
| Application | Setting |
|---|---|
| Debugging | No impact |
| Traceability | No impact |
| Efficiency | No impact |
| Safety precaution | Enable all as errors |
Select the diagnostic action to take if the model attempts to store data in a data store after previously reading data from it in the current time step.
Default: Use local settings
For each data store defined by a Data Store Memory block, use the setting specified by the block. This option disables the diagnostic for global data stores (i.e., data stores defined by Simulink.Signal objects).
Disables this diagnostic for all data stores accessed by the model.
Displays diagnostic as a warning at the MATLAB command line.
Halts the simulation and displays the diagnostic in an error dialog box.
| Parameter: WriteAfterReadMsg |
| Type: string |
| Value: 'UseLocalSettings' | 'DisableAll' | 'EnableAllAsWarning' | 'EnableAllAsError' |
| Default: 'UseLocalSettings' |
| Application | Setting |
|---|---|
| Debugging | No impact |
| Traceability | No impact |
| Efficiency | No impact |
| Safety precaution | Enable all as errors |
Select the diagnostic action to take if the model attempts to store data in a data store twice in succession in the current time step.
Default: Use local settings
For each data store defined by a Data Store Memory block, use the setting specified by the block. This option disables the diagnostic for global data stores (i.e., data stores defined by Simulink.Signal objects).
Disables this diagnostic for all data stores accessed by the model.
Displays diagnostic as a warning at the MATLAB command line.
Halts the simulation and displays the diagnostic in an error dialog box.
| Parameter: WriteAfterWriteMsg |
| Type: string |
| Value: 'UseLocalSettings' | 'DisableAll' | 'EnableAllAsWarning' | 'EnableAllAsError' |
| Default: 'UseLocalSettings' |
| Application | Setting |
|---|---|
| Debugging | No impact |
| Traceability | No impact |
| Efficiency | No impact |
| Safety precaution | Enable all as errors |
Select the diagnostic action to take when one task reads data from a Data Store Memory block to which another task writes data.
Default: warning
Simulink software takes no action.
Simulink software displays a warning.
Simulink software terminates the simulation and displays an error message.
Such a situation is safe only if one of the tasks cannot interrupt the other, such as when the data store is a scalar and the writing task uses an atomic copy operation to update the store or the target does not allow the tasks to preempt each other.
You should disable this diagnostic (set it to none) only if the application warrants it, such as if the application uses a cyclic scheduler that prevents tasks from preempting each other.
| Parameter: MultiTaskDSMMsg |
| Type: string |
| Value: 'none' | 'warning' | 'error' |
| Default: 'warning' |
| Application | Setting |
|---|---|
| Debugging | No impact |
| Traceability | No impact |
| Efficiency | No impact |
| Safety precaution | error |
Data Store Memory block
Select the diagnostic action to take when the model contains multiple Data Store Memory blocks that specify the same data store name.
Default: none
Simulink software takes no action.
Simulink software displays a warning.
Simulink software terminates the simulation and displays an error message.
| Parameter: UniqueDataStoreMsg |
| Type: string |
| Value: 'none' | 'warning' | 'error' |
| Default: 'none' |
| Application | Setting |
|---|---|
| Debugging | No impact |
| Traceability | No impact |
| Efficiency | No impact |
| Safety precaution | No impact |
Data Store Memory block
Select the diagnostic action to take when blocks write data to locations outside the memory allocated to them.
Default: none
Simulink software takes no action.
Simulink software displays a warning.
Simulink software terminates the simulation and displays an error message.
Use this option to check whether execution of each instance of a block during model simulation writes data to memory locations not allocated to the block. This can happen only if your model includes a user-written S-function that has a bug.
Enabling this option slows down model execution considerably. Thus, you should enable it only if you suspect that your model contains a user-written S-function that has a bug.
This option causes Simulink software to check whether a block writes outside the memory allocated to it during simulation. Typically this can happen only if your model includes a user-written S-function that has a bug.
See Writing S-Functions for more information on using this option.
| Parameter: ConsistencyChecking |
| Type: string |
| Value: 'none' | 'warning' | 'error' |
| Default: 'none' |
| Application | Setting |
|---|---|
| Debugging | warning |
| Traceability | No impact |
| Efficiency | none |
| Safety precaution | No impact |
Enable model verification blocks in the current model either globally or locally.
Default: Use local settings
Enables or disables blocks based on the value of the Enable assertion parameter of each block. If a block's Enable assertion parameter is on, the block is enabled; otherwise, the block is disabled.
Enables all model verification blocks in the model regardless of the settings of their Enable assertion parameters.
Disables all model verification blocks in the model regardless of the settings of their Enable assertion parameters.
| Parameter: AssertControl |
| Type: string |
| Value: 'UseLocalSettings' | 'EnableAll' | 'DisableAll' |
| Default: 'UseLocalSettings' |
| Application | Setting |
|---|---|
| Debugging | No impact |
| Traceability | No impact |
| Efficiency | No impact |
| Safety precaution | Disable all |
| Diagnostics Pane: Sample Time | Diagnostics Pane: Type Conversion | |
| © 1984-2008- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |