| Products & Services | Solutions | Academia | Support | User Community | Company |
| Download Product Updates | | | Get Pricing | | | Trial Software |
| Documentation → Simulink |
| Contents | Index |
| Learn more about Simulink |

| On this page… |
|---|
Model Referencing Diagnostics Overview |
Specify the diagnostic actions that Simulink software should take when it detects an incompatibility relating to a model reference hierarchy.
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 loading or updating this model if Simulink software detects a mismatch between the version of the model used to create or refresh a Model block in this model and the referenced model's current version.
Default: none
Simulink software takes no action.
Simulink software displays a warning and refreshes the Model block.
Simulink software displays an error message and does not refresh Model block.
If you have enabled display of referenced model version numbers on Model blocks for this model (see Displaying Referenced Model Version Numbers), Simulink software displays a version mismatch on the Model block icon, for example: Rev:1.0 != 1.2.
| Parameter: ModelReferenceVersionMismatchMessage |
| Type: string |
| Value: 'none' | 'warning' | 'error' |
| Default: 'none' |
| Application | Setting |
|---|---|
| Debugging | No impact |
| Traceability | No impact |
| Efficiency | No impact |
| Safety precaution | none |
Select the diagnostic action to take if Simulink software detects a port or parameter mismatch during model loading or updating.
Default: none
Simulink software takes no action.
Simulink software displays a warning and refreshes the Model block.
Simulink software displays an error message and does not refresh the Model block.
Port mismatches occur when there is a mismatch between the I/O ports of a Model block and the root-level I/O ports of the model it references.
Parameter mismatches occur when there is a mismatch between the parameter arguments recognized by the Model block and the parameter arguments declared by the referenced model.
Model block icons can display a message indicating port or parameter mismatches. To enable this feature, select Block displays > Model Block I/O Mismatch from the parent model's Format menu.
| Parameter: ModelReferenceIOMismatchMessage |
| 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 configuration parameters of a model referenced by this model do not match this model's configuration parameters or are inappropriate for a referenced model.
Default: none
Simulink software takes no action.
Simulink software displays a warning.
Simulink software terminates the simulation and displays an error message.
Set this diagnostic to warning or error if you suspect that an inappropriate or mismatched configuration parameter may be causing your model to give the wrong result.
| Parameter: ModelReferenceCSMismatchMessage |
| Type: string |
| Value: 'none' | 'warning' | 'error' |
| Default: 'none' |
| Application | Setting |
|---|---|
| Debugging | No impact |
| Traceability | No impact |
| Efficiency | No impact |
| Safety precaution | warning |
Select the diagnostic action to take if Simulink software detects invalid internal connections to this model's root-level Output port blocks.
Default: none
Simulink software silently inserts hidden blocks to satisfy the constraints wherever possible.
Simulink software warns you that a connection constraint has been violated and attempts to satisfy the constraint by inserting hidden blocks.
Simulink software terminates the simulation or code generation and displays an error message.
In some cases (such as function-call feedback loops), automatically inserted hidden blocks may introduce delays and thus may change simulation results.
Auto-inserting hidden blocks to eliminate root I/O problems stops at subsystem boundaries. Therefore, you may need to manually modify models with subsystems that violate any of the constraints below.
The types of invalid internal connections are:
A root Output port is connected directly or indirectly to more than one nonvirtual block port:

A root Output port is connected to a root Inport block, a Ground block, or a nondata port:

Two root Outport blocks are connected to the same block port:

An Outport block is connected to some elements of a block output and not others:

An Outport block is connected more than once to the same element:

| Parameter: ModelReferenceIOMsg |
| 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 this model contains To Workspace blocks or Scope blocks with data logging enabled.
Default: warning
Simulink software takes no action.
Simulink software displays a warning.
Simulink software terminates the simulation and displays an error message.
The default action warns you that Simulink software does not support use of these blocks to log data from referenced models.
See Logging Referenced Model Signals for information on how to log signals from a reference to this model.
| Parameter: ModelReferenceDataLoggingMessage |
| Type: string |
| Value: 'none' | 'warning' | 'error' |
| Default: 'warning' |
| Application | Setting |
|---|---|
| Debugging | No impact |
| Traceability | No impact |
| Efficiency | No impact |
| Safety precaution | error |
To Workspace block
Scope block
![]() | Diagnostics Pane: Compatibility | Diagnostics Pane: Saving | ![]() |

Learn more about Simulink through this collection of videos, articles, technical literature and the Getting Started with Simulink Guide.
| © 1984-2009- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |