Model Reference

Purpose

Reference a subsystem or netlist from the same or another model

Library

System

Description

../../_images/modelreference.svg

The Model Reference block allows you to reference a Subsystem, Netlist or Netlist File Reference from the same or another model. The reference is synchronized when the original component has changed. This concept is similar to library links with the difference that the referenced model file path can be specified relative to the referencing model.

The model reference is defined in the Model Reference dialog. Double-click on the Model Reference block to open the dialog, then drag the component that you want to reference into it. The labels Model file and Component path will be updated to reflect the component that is referenced. By default, the referenced model file is specified with a path relative to the referencing model. You can change this with the Model file reference selector.

When you click OK to apply the settings, the Model Reference block is replaced with a copy of the referenced component that is marked with a small solid curved arrow (arrow) in the lower left corner of the component icon. A right-click on this arrow opens a context menu that allows you to break the link, to edit the model reference, or to show the original component. This context menu can also be accessed by right-clicking the component and selecting Link.

If the referenced component is in the same model, the Model file label shows the text local reference.

Note

  • For technical reasons, you can only reference components in the same model (local references) or PLECS Standalone models. See Opening a PLECS Standalone Model to learn how to open a PLECS Standalone model in PLECS Blockset.

  • Synchronization is performed when the model is loaded, when the reference is changed in the dialog, or before a simulation. To force an update, choose Synchronize all external links… from the Edit menu.

  • Synchronization loads and updates all referenced models and libraries as necessary.

  • The model file is marked as modified if an update was required.

  • Only the reference to the model file and subsystem is stored. To simulate a model, all referenced model files are required.