Documentation Center

  • Trial Software
  • Product Updates

Diagnostics Pane: Connectivity

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

  • To open the Connectivity pane, in the Simulink Editor, select Simulation > Model Configuration Parameters > Diagnostics > Connectivity.

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

See Also

Signal label mismatch

Select the diagnostic action to take when different names are used for the same signal as that signal propagates through blocks in a model. This diagnostic does not check for signal label mismatches on a virtual bus signal.

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

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionerror

See Also

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

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionerror

See Also

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

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionerror

See Also

Unconnected line

Select the diagnostic action to take when the Model contains an unconnected line or an unmatched GotoGoto or FromFrom 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

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionerror

See Also

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 OutportOutport blocks is connected to a bus but does not specify a bus object (see Simulink.BusSimulink.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

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionerror

See Also

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 SwitchSwitch block.

Command-Line Information

Parameter: BusObjectLabelMismatch
Type: string
Value: 'none' | 'warning' | 'error'
Default: 'warning'

Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionerror

See Also

Mux blocks used to create bus signals

Select the diagnostic action to take if Simulink detects a MuxMux block that creates a virtual bus.

Settings

Default: error

none

Simulink software takes no action.

This option disables checking for Mux blocks used to create virtual bus signals.

warning

Simulink software displays a warning.

With this option, if Simulink 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 block signals that it encounters that are treated as virtual buses.

error

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.

Tips

  • This diagnostic detects use of MuxMux 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 SelectorBus 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).

  • If you are using simplified initialization mode, you must set this diagnostic to error. For more information, see Underspecified initialization detectionUnderspecified initialization detection.

  • You can identify Mux blocks used to create virtual buses using the Model Advisor Check bus usage check. For more information, see Check bus usage.

  • See Prevent Bus and Mux Mixtures 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' | 'WarnOnBusTreatedAsVector' | 'ErrorOnBusTreatedAsVector'
Default: 'ErrorLevel1'

Due to the requirement that Mux blocks used to create bus signals be error before Bus signal treated as vector is enabled, one parameter, StrictBusMsg, can specify all permutations of the two controls. The parameter can have one of five values. The following table shows these values and the equivalent GUI control settings:

Value of StrictBusMsg (API) Mux blocks used to create bus signals (GUI)Bus signal treated as vector (GUI)
Nonenonenone
Warningwarningnone
ErrorLevel1errornone
WarnOnBusTreatedAsVectorerrorwarning
ErrorOnBusTreatedAsVectorerrorerror

Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionerror

See Also

Bus signal treated as vector

Select the diagnostic action to take when Simulink software detects a virtual bus signal that is used as a mux signal.

Settings

Default: warning

none

Disables checking for virtual buses used as muxes.

warning

Simulink software displays a warning if it detects a virtual bus used as a mux. 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.

Tips

  • 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 DemuxDemux block or to any block that can input a mux or a vector but is not formally defined as bus-capable. See Bus-Capable BlocksBus-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 detectionUnderspecified initialization detection.

  • You can identify bus signals that are treated as a vectors using the Model Advisor Check bus usage check. For more information, see Check bus usage.

  • See Prevent Bus and Mux Mixtures 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'

Due to the requirement that Mux blocks used to create bus signals be error before Bus signal treated as vector is enabled, one parameter, StrictBusMsg, can specify all permutations of the two controls. The parameter can have one of five values. The following table shows these values and the equivalent GUI control settings:

Value of StrictBusMsg (API) Mux blocks used to create bus signals (GUI)Bus signal treated as vector (GUI)
Nonenonenone
Warningwarningnone
ErrorLevel1errornone
WarnOnBusTreatedAsVectorerrorwarning
ErrorOnBusTreatedAsVectorerrorerror

Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionerror

See Also

Non-bus signals treated as bus signals

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.

Settings

Default: none

none

Implicitly converts non-bus signals to bus signals to support connecting the signal to a Bus Assignment or Bus Selector block.

warning

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.

error

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.

Tips

  • Using a Mux block to create a virtual bus does not support strong type checking and increases the likelihood of runtime 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 MixturesAvoiding Mux/Bus Mixtures 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: NonBusSignalsTreatedAsBus
Type: string
Value: 'none' | 'warning' | 'error'
Default: 'none'

Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionerror

See Also

Repair bus selections

Repair broken selections in the Bus Selector and Bus Assignment block parameter dialogs due to upstream bus hierarchy changes.

Settings

Default: Warn and repair

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.

Error without repair

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.

Tips

Dependency

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

Command-Line Information

Parameter: BusNameAdapt
Type: string
Values: 'WarnAndRepair' | 'ErrorWithoutRepair'
Default: 'WarnAndRepair'

Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionWarn and repair

See Also

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 subsystems" examples in the Simulink Subsystem SemanticsSubsystem 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

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionerror

See Also

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: Enable all as errors

Enable all as errors

Enables this diagnostic for all function-call subsystems in this model. Issues an error for context-dependent inputs.

Enable all as warnings

Enables this diagnostic for all function-call subsystems in this model. Issues a warning for context-dependent inputs.

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 SubsystemSubsystem block's parameter dialog box for more information).

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.

  • For examples of function-call subsystems, see the "Function-call systems" examples in the Simulink "Subsystem Semantics""Subsystem Semantics" library).

  • To fix an error or warning generated by this diagnostic, use one of these approaches:

    • For the Inport block inside of the function-call subsystem, enable the Latch input for feedback signals of function-call subsystem outputs parameter.

    • Place a Function-Call Feedback Latch block on the feedback signal.

    For examples of using these approaches, open the sl_subsys_fcncallerr12sl_subsys_fcncallerr12 model and press the more info button.

Command-Line Information

Parameter: FcnCallInpInsideContextMsg
Type: string
Value: 'EnableAllAsError'| 'EnableAllAsWarning'| 'UseLocalSettings' | 'DisableAll'
Default: 'EnableAllAsError'

Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionEnable all as errors

See Also

Was this topic helpful?