Diagnostics Pane: Connectivity :: Configuration Parameters Dialog Box (Simulink®)

Simulink^®

Diagnostics Pane: Connectivity

On this page…
Connectivity Diagnostics Overview Signal label mismatch Unconnected block input ports Unconnected block output ports Unconnected line Unspecified bus object at root Outport block Element name mismatch Mux blocks used to create bus signals Bus signal treated as vector Invalid function-call connection Context-dependent inputs

On this page…

Connectivity Diagnostics Overview

Signal label mismatch

Unconnected block input ports

Unconnected block output ports

Unconnected line

Unspecified bus object at root Outport block

Element name mismatch

Mux blocks used to create bus signals

Bus signal treated as vector

Invalid function-call connection

Context-dependent inputs

Connectivity Diagnostics Overview

Specify the diagnostic actions that Simulink^® software should take when it detects a problem with block connections while compiling the model.

Configuration

Set the parameters displayed.

Tips

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.

Signal label mismatch

Select the diagnostic action to take when Simulink software detects virtual signals that have a common source signal but different labels.

Settings

Default: none

none: Simulink software takes no action.
warning: Simulink software displays a warning.
error: Simulink software terminates the simulation and displays an error message.

Command-Line Information

Parameter: SignalLabelMismatchMsg

Type: string

Value: 'none' | 'warning' | 'error'

Default: 'none'

Recommended Settings

Application	Setting
Debugging	No impact
Traceability	No impact
Efficiency	No impact
Safety precaution	`error`

Unconnected block input ports

Select the diagnostic action to take when the model contains a block with an unconnected input.

Settings

Default: warning

none: Simulink software takes no action.
warning: Simulink software displays a warning.
error: Simulink software terminates the simulation and displays an error message.

Command-Line Information

Parameter: UnconnectedInputMsg

Type: string

Value: 'none' | 'warning' | 'error'

Default: 'warning'

Recommended Settings

Application	Setting
Debugging	No impact
Traceability	No impact
Efficiency	No impact
Safety precaution	`error`

Unconnected block output ports

Select the diagnostic action to take when the model contains a block with an unconnected output.

Settings

Default: warning

none: Simulink software takes no action.
warning: Simulink software displays a warning.
error: Simulink software terminates the simulation and displays an error message.

Command-Line Information

Parameter: UnconnectedOutputMsg

Type: string

Value: 'none' | 'warning' | 'error'

Default: 'warning'

Recommended Settings

Application	Setting
Debugging	No impact
Traceability	No impact
Efficiency	No impact
Safety precaution	`error`

Unconnected line

Select the diagnostic action to take when the Model contains an unconnected line or an unmatched Goto or From block.

Settings

Default: warning

none: Simulink software takes no action.
warning: Simulink software displays a warning.
error: Simulink software terminates the simulation and displays an error message.

Command-Line Information

Parameter: UnconnectedLineMsg

Type: string

Value: 'none' | 'warning' | 'error'

Default: 'warning'

Recommended Settings

Application	Setting
Debugging	No impact
Traceability	No impact
Efficiency	No impact
Safety precaution	`error`

Unspecified bus object at root Outport block

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).

Settings

Default: warning

none: Simulink software takes no action.
warning: Simulink software displays a warning.
error: Simulink software terminates the simulation and displays an error message.

Command-Line Information

Parameter: RootOutportRequireBusObject

Type: string

Value: 'none' | 'warning' | 'error'

Default: 'warning'

Recommended Settings

Application	Setting
Debugging	No impact
Traceability	No impact
Efficiency	No impact
Safety precaution	`error`

Element name mismatch

Select the diagnostic action to take if the name of a bus element does not match the name specified by the corresponding bus object.

Settings

Default: warning

none: Simulink software takes no action.
warning: Simulink software displays a warning.
error: Simulink software terminates the simulation and displays an error message.

Tip

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.

Command-Line Information

Parameter: BusObjectLabelMismatch

Type: string

Value: 'none' | 'warning' | 'error'

Default: 'warning'

Recommended Settings

Application	Setting
Debugging	No impact
Traceability	No impact
Efficiency	No impact
Safety precaution	`error`

Mux blocks used to create bus signals

Select the diagnostic action to take if Simulink software detects a signal that some blocks treat as a mux/vector, while other blocks treat the signal as a bus.

Settings

Default: warning

none

Simulink software takes no action.

This option disables checking for Mux blocks used to create buses.

warning

Simulink software displays a warning.

This option does not enforce strict bus behavior. However, if it detects a Mux block that creates a 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.

error

Simulink software terminates the simulation and displays an error message identifying the offending Mux block.

This option enforces the following "strict bus" behavior during model editing, updating, and simulation:

A Mux block with more than one input is allowed to output only a vector signal. A Mux block with only one input is allowed to output only a scalar, vector, or matrix signal. Simulink software displays all nonscalar Mux outputs as wide signals.
The dialog boxes for Bus Creator and Bus Selector blocks allow you to select input signals created by Mux blocks but not the individual elements of those signals. For example, suppose that the bus connected to a Bus Selector includes a vector signal created by a Mux block. The Bus Selector allows you to select the vector signal but not any of its elements.

Tips

This diagnostic detects use of Mux blocks to create buses. The diagnostic considers a signal created by a Mux block to be a bus if the signal meets either or both of the following conditions:
- A Bus Selector block individually selects one or more of the signal's elements (as opposed to the entire signal).
- The signal's components have differing data types, numeric types (complex or real), dimensionality, storage classes (see the Real-Time Workshop^® User's Guide for information on storage classes), or sampling modes (see the Signal Processing Blockset™ documentation for information on frame-based sampling).
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 Intermixing Composite Signal Types for more information.

Dependency

Selecting error enables the following parameter:

Bus signal treated as vector

Command-Line Information

Parameter: StrictBusMsg

Type: string

Value: 'none' | 'warning' | 'ErrorLevel1' | 'WarnOnBusInputToNonBusBlock' | 'ErrorOnBusInputToNonBusBlock'

Default: 'warning'

Recommended Settings

Application	Setting
Debugging	No impact
Traceability	No impact
Efficiency	No impact
Safety precaution	`error`

Bus signal treated as vector

Select the diagnostic action to take when Simulink software detects that virtual bus signals are used to specify muxes/vectors.

Settings

Default: warning

none: Disables checking for buses used as muxes/vectors.
warning: Simulink software displays a warning if it detects a bus used as a mux/vector. This option does not enforce strict bus behavior.
error: Simulink software terminates the simulation and displays an error message when it builds a model that uses any virtual bus as a mux/vector.

Tips

This diagnostic detects the use of virtual bus signals used to specify muxes/vectors. The diagnostic considers a virtual bus signal to be used as a mux/vector 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/vectors 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. The MathWorks therefore discourages mixing vectors, muxes, and virtual buses in new applications, and encourages upgrading existing applications to avoid such mixtures.
You can eliminate warnings and errors about buses used as muxes/vectors by using Simulink.BlockDiagram.addBusToVector to insert a Bus to Vector block into any bus signal that is used as a mux/vector. Before executing the command, you should set this diagnostic to warning or none.
See Intermixing Composite Signal Types for more information.

Dependency

This parameter is enabled only when Mux blocks used to create bus signals is set to error.

Command-Line Information

Parameter: StrictBusMsg

Type: string

Value: 'none' | 'warning' | 'ErrorLevel1' | 'WarnOnBusTreatedAsVector' | 'ErrorOnBusTreatedAsVector'

Default: 'warning'

Recommended Settings

Application	Setting
Debugging	No impact
Traceability	No impact
Efficiency	No impact
Safety precaution	`error`

Invalid function-call connection

Select the diagnostic action to take if Simulink software detects incorrect use of a function-call subsystem.

Settings

Default: error

none: Simulink software takes no action.
warning: Simulink software displays a warning.
error: Simulink software terminates the simulation and displays an error message.

Tips

See the "Function-call systems" 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.

Command-Line Information

Parameter: InvalidFcnCallConnMsg

Type: string

Value: 'none' | 'warning' | 'error'

Default: 'error'

Recommended Settings

Application	Setting
Debugging	No impact
Traceability	No impact
Efficiency	No impact
Safety precaution	`error`

Context-dependent inputs

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.

Settings

Default: Use local settings

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).
Enable all: Enables this diagnostic for all function-call subsystems in this model.
Disable all: Disables this diagnostic for all function-call subsystems in this model.

Tips

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).

Command-Line Information

Parameter: FcnCallInpInsideContextMsg

Type: string

Value: 'Use local settings' | 'Enable All' | 'Disable All'

Default: 'Use local settings'

Recommended Settings

Application	Setting
Debugging	No impact
Traceability	No impact
Efficiency	No impact
Safety precaution	`Enable all`