This is machine translation

Translated by Microsoft
Mouseover text to see original. Click the button below to return to the English verison of the page.

Note: This page has been translated by MathWorks. Please click here
To view all translated materals including this page, select Japan from the country navigator on the bottom of this page.

Simulink Blocks Supported for Range Analysis

Overview of Simulink Block Support

The following tables summarize range analysis support for Simulink® blocks. Each table lists all the blocks in each Simulink library and describes support information for that particular block. If the software does not support a given block, where possible, automatic stubbing considers the interface of the unsupported blocks, but not their behavior, during the analysis. However, if any of the unsupported blocks affect the simulation outcome, the analysis may achieve only partial results. If the analysis cannot use automatic stubbing for a block, the block is marked as "not stubbable". For more information, see Automatic Stubbing.

Not all blocks that are supported for range analysis are supported for fixed-point conversion. To check if a block supports fixed-point data types, see Using Blocks that Don't Support Fixed-Point Data Types.

 Additional Math and Discrete Library

 Commonly Used Blocks Library

 Continuous Library

 Discontinuities Library

 Discrete Library

 Logic and Bit Operations Library

 Lookup Tables Library

 Math Operations Library

 Model Verification Library

 Model-Wide Utilities Library

 Ports & Subsystems Library

 Signal Attributes Library

 Signal Routing Library

 Sinks Library

 Sources Library

 User-Defined Functions Library

Limitations of Support for Model Blocks

Simulink Design Verifier supports the Model block with the following limitations. The software cannot analyze a model containing one or more Model blocks if:

  • The referenced model is protected. Protected referenced models are encoded to obscure their contents. This allows third parties to use the referenced model without being able to view the intellectual property that makes up the model.

    For more information, see Protected Model (Simulink).

  • The parent model or any of the referenced models returns an error when you set the Configuration Parameters > Diagnostics > Connectivity > Element name mismatch parameter to error.

    You can use the Element name mismatch diagnostic along with bus objects so that your model meets the bus element naming requirements imposed by some blocks.

  • The Model block uses asynchronous function-call inputs.

  • Any of the Model blocks in the model reference hierarchy creates an artificial algebraic loop. If this occurs, take the following steps:

    1. On the Diagnostics pane of the Configuration Parameters dialog box, set the Minimize algebraic loop parameter to error so that Simulink reports an algebraic loop error.

    2. On the Model Referencing Pane of the Configuration Parameters dialog box, select the Minimize algebraic loop occurrences parameter.

      Simulink tries to eliminate the artificial algebraic loop during simulation.

    3. Simulate the model.

    4. If Simulink cannot eliminate the artificial algebraic loop, highlight the location of the algebraic loop by selecting Simulation > Update Diagram.

    5. Eliminate the artificial algebraic loop so that the software can analyze the model. Break the loop with Unit Delay blocks so that the execution order is predictable.

  • The parent model uses the base workspace and the referenced model uses a data dictionary.

  • The parent model and the referenced model have mismatched data type override settings. The data type override setting of the parent model and its referenced models must be the same, unless the data type override setting of the parent model is Use local settings. You can select the data type override settings for your model in the Analysis menu, in the Fixed Point Tool dialog box under the Settings for selected system pane.

  • The referenced model is a Model Reference block with virtual bus inports, and the signals in the bus do not all have the same sample time at compilation. To make the model compatible with Simulink Design Verifier analysis, convert the port to a nonvirtual bus, or specify an explicit sample time for the port.

Was this topic helpful?