|
|
|
| R2011b Documentation → Simulink | |
Learn more about Simulink |
|
| Contents | Index |
| On this page… |
|---|
Connectivity Diagnostics Overview Unconnected block output ports Unspecified bus object at root Outport block Mux blocks used to create bus signals Non-bus signals treated as bus signals |
Specify the diagnostic actions that Simulink software should take when it detects a problem with block connections while compiling the 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 diagnostic action to take when Simulink software detects virtual signals that have a common source signal but different labels.
Default: none
Simulink software takes no action.
Simulink software displays a warning.
Simulink software terminates the simulation and displays an error message.
| Parameter: SignalLabelMismatchMsg |
| 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 the model contains a block with an unconnected input.
Default: warning
Simulink software takes no action.
Simulink software displays a warning.
Simulink software terminates the simulation and displays an error message.
| Parameter: UnconnectedInputMsg |
| 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 the model contains a block with an unconnected output.
Default: warning
Simulink software takes no action.
Simulink software displays a warning.
Simulink software terminates the simulation and displays an error message.
| Parameter: UnconnectedOutputMsg |
| 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 the Model contains an unconnected line or an unmatched Goto or From block.
Default: warning
Simulink software takes no action.
Simulink software displays a warning.
Simulink software terminates the simulation and displays an error message.
| Parameter: UnconnectedLineMsg |
| 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 while generating a simulation target for a referenced model if any of the model's root Outport blocks is connected to a bus but does not specify a bus object (see Simulink.Bus).
Default: warning
Simulink software takes no action.
Simulink software displays a warning.
Simulink software terminates the simulation and displays an error message.
| Parameter: RootOutportRequireBusObject |
| Type: string |
| Value: 'none' | 'warning' | 'error' |
| Default: 'warning' |
| Application | Setting |
|---|---|
| Debugging | No impact |
| Traceability | No impact |
| Efficiency | No impact |
| Safety precaution | error |
Outport block
Select the diagnostic action to take if the name of a bus element does not match the name specified by the corresponding bus object.
Default: warning
Simulink software takes no action.
Simulink software displays a warning.
Simulink software terminates the simulation and displays an error message.
You can use this diagnostic along with bus objects to ensure that your model meets bus element naming requirements imposed by some blocks, such as the Switch block.
| Parameter: BusObjectLabelMismatch |
| 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 Simulink detects a Mux block that creates a virtual bus.
Default: warning
Simulink software takes no action.
This option disables checking for Mux blocks used to create virtual bus signals.
Simulink software displays a warning.
This option does not enforce strict bus behavior. However, if it detects a Mux block that creates a virtual bus during model update or simulation, it displays a message in the MATLAB Command Window that identifies the offending block. It does this for the first ten Mux blocks that it encounters that violate strict bus behavior.
Simulink terminates the simulation and displays an error message identifying the first Mux block it encounters that is used to create a virtual bus. If this option is selected, a Mux block with more than one input is allowed to output only a vector signal, and a Mux block with only one input is allowed to output only a scalar, vector, or matrix signal.
This diagnostic detects use of Mux blocks to create virtual buses. The diagnostic considers a signal created by a Mux block to be a virtual bus if the signal meets either or both of the following conditions:
A Bus Selector block individually selects one or more of the signal elements (as opposed to the entire signal).
The signal components have differing data types, numeric types (complex or real), dimensionality, or sampling modes (see the DSP System Toolbox™ documentation for information on frame-based sampling).
Using a Mux block to create a virtual bus does not support strong type checking and increases the likelihood of run-time errors. In new applications, do not use Mux blocks to create bus signals. Consider upgrading existing applications to that use of Mux blocks.
Simulink generates a warning when you load a model created in a release prior to R2010a, if that model contains a Mux block to create a bus signal. For new models, Simulink generates an error.
If you are using simplified initialization mode, you must set this diagnostic to error. For more information, see Underspecified initialization detection.
– You can identify Mux blocks used to create virtual buses using the Model Advisor check Check for proper bus usage. For more information, see Check for proper bus usage.
You can avoid strict bus behavior errors and warnings by using slreplace_mux to remove Mux blocks that violate strict bus behavior from your model. Before executing the command, you should set this diagnostic to warning or none.
See Avoiding Mux/Bus Mixtures for more information.
Selecting error enables the following parameter:
Bus signal treated as vector
| Parameter: StrictBusMsg |
| Type: string |
| Value: 'none' | 'warning' | 'ErrorLevel1' | 'WarnOnBusTreatedAsVector' | 'ErrorOnBusTreatedAsVector' |
| Default: 'warning' |
For information about the impact of the command-line setting on the Mux blocks used to create bus signals and Bus signal treated as vector diagnostic dialog box settings, see Equivalent Parameter Values.
| Application | Setting |
|---|---|
| Debugging | No impact |
| Traceability | No impact |
| Efficiency | No impact |
| Safety precaution | error |
Mux block
Bus Creator block
Bus Selector block
Select the diagnostic action to take when Simulink software detects a virtual bus signal that is used as a mux signal.
Default: warning
Disables checking for virtual buses used as muxes.
Simulink software displays a warning if it detects a virtual bus used as a mux. This option does not enforce strict bus behavior.
Simulink software terminates the simulation and displays an error message when it builds a model that uses any virtual bus as a mux.
This diagnostic detects the use of virtual bus signals used to specify muxes. The diagnostic considers a virtual bus signal to be used as a mux if it is input to a Demux block or to any block that can input a mux or a vector but is not formally defined as bus-capable. See Bus-Capable Blocks for details.
Virtual buses can be used as muxes only when they contain no nested buses and all constituent signals have the same attributes. This practice is deprecated as of R2007a (V6.6) and may cease to be supported at some future time. MathWorks, therefore, discourages mixing virtual buses with muxes in new applications, and encourages upgrading existing applications to avoid such mixtures.
If you are using simplified initialization mode, you must set this diagnostic to error. For more information, see Underspecified initialization detection.
You can identify bus signals that are treated as a vectors using the Model Advisor check Check for proper bus usage. For more information, see Check for proper bus usage.
You can eliminate warnings and errors about virtual buses used as muxes by using Simulink.BlockDiagram.addBusToVector to insert a Bus to Vector block into any virtual bus signal that is used as a mux. Before executing the command, you should set this diagnostic to warning or none.
See Avoiding Mux/Bus Mixtures for more information.
This parameter is enabled only when Mux blocks used to create bus signals is set to error.
| Parameter: StrictBusMsg |
| Type: string |
| Value: 'none' | 'warning' | 'ErrorLevel1' | 'WarnOnBusTreatedAsVector' | 'ErrorOnBusTreatedAsVector' |
| Default: 'warning' |
For information about the impact of the command-line setting on the Mux blocks used to create bus signals and Bus signal treated as vector diagnostic dialog box settings, see Equivalent Parameter Values.
| Application | Setting |
|---|---|
| Debugging | No impact |
| Traceability | No impact |
| Efficiency | No impact |
| Safety precaution | error |
Demux block
Bus to Vector block
Detect when Simulink implicitly converts a non-bus signal to a bus signal to support connecting the signal to a Bus Assignment or Bus Selector block.
Default: none
Implicitly converts non-bus signals to bus signals to support connecting the signal to a Bus Assignment or Bus Selector block.
Simulink displays a warning, indicating that it has converted a non-bus signal to a bus signal. The warning lists the non-bus signals that Simulink converts.
Simulink terminates the simulation without performing converting non-bus signals to bus signals. The error message lists the non-bus signal that is being treated as a bus signal.
Using a Mux block to create a virtual bus does not support strong type checking and increases the likelihood of run-time errors. In new applications, do not use Mux blocks to create bus signals. Consider upgrading existing applications to that use of Mux blocks.
Simulink generates a warning when you load a model created in a release prior to R2010a, if that model contains a Mux block to create a bus signal. For new models, Simulink generates an error.
See Avoiding Mux/Bus Mixtures for more information.
This parameter is enabled only when Mux blocks used to create bus signals is set to error.
| Parameter: NonbusSignalsTreatedAsBus |
| Type: string |
| Value: 'none' | 'warning' | 'error' |
| Default: 'none' |
| Application | Setting |
|---|---|
| Debugging | No impact |
| Traceability | No impact |
| Efficiency | No impact |
| Safety precaution | error |
Demux block
Bus to Vector block
Repair broken selections in the Bus Selector and Bus Assignment block parameter dialogs due to upstream bus hierarchy changes.
Default: Warn and repair
Simulink displays a warning, indicating the block parameters for Bus Selector and Bus Assignment blocks that Simulink repaired to reflect upstream bus hierarchy changes.
Simulink terminates the simulation and displays an error message indicating the block parameters that you need to repair for Bus Selector and Bus Assignment blocks to reflect upstream bus hierarchy changes.
See Avoiding Mux/Bus Mixtures for more information.
This parameter is enabled only when Mux blocks used to create bus signals is set to error.
| Parameter: BusNameAdapt |
| Type: string |
| Values: 'WarnAndRepair' | 'ErrorWithoutRepair' |
| Default: 'WarnAndRepair' |
| Application | Setting |
|---|---|
| Debugging | No impact |
| Traceability | No impact |
| Efficiency | No impact |
| Safety precaution | Warn and repair |
Select the diagnostic action to take if Simulink software detects incorrect use of a function-call subsystem.
Default: error
Simulink software takes no action.
Simulink software displays a warning.
Simulink software terminates the simulation and displays an error message.
See the "Function-call subsystems" examples in the Simulink Subsystem Semantics library for examples of invalid uses of function-call subsystems.
Setting this parameter to none or warning can lead to invalid simulation results.
Setting this parameter to none or warning may cause Simulink software to insert extra delay operations.
| Parameter: InvalidFcnCallConnMsg |
| Type: string |
| Value: 'none' | 'warning' | 'error' |
| Default: 'error' |
| Application | Setting |
|---|---|
| Debugging | No impact |
| Traceability | No impact |
| Efficiency | No impact |
| Safety precaution | error |
Subsystem Semantics library
Select the diagnostic action to take when Simulink software has to compute any of a function-call subsystem's inputs directly or indirectly during execution of a call to a function-call subsystem.
Default: Use local settings
Issues a warning only if the corresponding diagnostic is selected on the function-call subsystem's parameters dialog box (see the documentation for the Subsystem block's parameter dialog box for more information).
Enables this diagnostic for all function-call subsystems in this model.
Disables this diagnostic for all function-call subsystems in this model.
This situation occurs when executing a function-call subsystem can change its inputs.
See the "Function-call systems" examples in the Simulink "Subsystem Semantics" library for examples of such function-call subsystems).
| Parameter: FcnCallInpInsideContextMsg |
| Type: string |
| Value: 'Use local settings' | 'Enable All' | 'Disable All' |
| Default: 'Use local settings' |
| Application | Setting |
|---|---|
| Debugging | No impact |
| Traceability | No impact |
| Efficiency | No impact |
| Safety precaution | Enable all |
Subsystem Semantics library
Subsystem block
 | Diagnostics Pane: Type Conversion | Diagnostics Pane: Compatibility |  |
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 |
