| Simulink® Release Notes |
  |
Referencing Model Limitations
A model can reference other models if it meets the following conditions:
- The Model Browser does not display Model blocks in its tree view.
- Tools that require access to a model's internal data or configuration, including the Model Coverage Tool, Report Generator, the Simulink and Stateflow debuggers, and the Profiler, do not work when invoked from a top model on models that the top model references. This is because the referenced models appear as black boxes to the top model. For example, you cannot use the Simulink Debugger to step from a top model into a referenced model.
- You cannot print a referenced model from a top model.
- You can initialize the states of a top model from the workspace only if you use structure format or you use array format and the top model does not reference any models that have states. You cannot use the workspace to initialize the states of models that the top model references.
- To Workspace and Scope blocks in models referenced by a top model do not log data when you simulate or run code generated from a top model.
- This release does not let you use signal logging to log, or floating scopes to view, the data of Stateflow charts residing in referenced models.
- An enabled or action subsystem cannot reference a model that uses absolute time.
- A continuous sample time cannot be propagated to a Model block that is sample-time independent.
- Linearization is not supported for models containing Model blocks.
- Right clicking on a subsystem to build an S-function from it works for subsystems containing Model blocks only if the model is configured to use
ert.tlc.
| | Model Referencing Limitations | | Referenced Model Limitations | |
© 1994-2005 The MathWorks, Inc.