Check safety-related diagnostic settings for bus connectivity

mathworks.hism.hisl_0307

Dependencies: Simulink^® Check™

Usage: High-Integrity System Modeling

Guideline: hisl_0307: Configuration Parameters > Diagnostics > Connectivity > Buses

Description

This check verifies that the model configuration uses optimal parameter settings that apply to bus connectivity when generating code for a safety-related application.

Recommended Actions and Results

Review the violations that are flagged by the check and the recommended action for fixing the issue. After applying the changes, save the model and rerun the check analysis.

You can use the Fix button to allow the Model Advisor to fix flagged violations. For this check, the Model Advisor configures model diagnostic settings that apply to bus connectivity and that can impact safety.

Modeling Condition	Recommended Action
The diagnostic that detects whether the root Outport block of a Model block is connected to a bus but does not specify a bus object is set to none or warning. For a bus signal to cross a model boundary, the signal must be defined as a bus object for compatibility with higher level models that use a model as a reference model.	Set model configuration parameter Unspecified bus object at root Outport block to error.
The diagnostic that detects whether the name of a bus element matches the name specified by the corresponding bus object is set to none or warning.	Set model configuration parameter Element name mismatch to error.
The diagnostic that detects when some blocks treat a signal as a mux or vector while other blocks treat the signal as a bus is set to none or warning. When the Simulink software automatically converts a muxed signal to a bus, an unintended operation or unpredictable behavior can occur.	Set model configuration parameter Bus signal treated as vector to error.
The diagnostic that detects when nonbus signals are treated as buses is not set to error.	Set model configuration parameter Non-bus signals treated as bus signals to error.

Capabilities and Limitations

• Does not run on library models

• Does not allow exclusions of blocks or charts

• Does not require model compilation

Version History

Introduced in R2007b