Subsystems

Group blocks into functional subsystems, create model hierarchy

As a model increases in size and complexity, you can simplify it by grouping blocks into subsystems. A subsystem is a set of blocks that you group into a single Subsystem block.

Using subsystems:

Establishes a hierarchical block diagram, where a Subsystem block is on one layer and the blocks that make up the subsystem are on another.
Keeps functionally related blocks together.
Helps reduce the number of blocks displayed in your model window.
Establishes an interface with inputs and outputs.

When you make a copy of a subsystem, that copy is independent of the source subsystem. To reuse the contents of a subsystem across a model or across models, consider referenced subsystems, referenced models, or subsystems linked to a block in a custom library. For more information, see Choose Among Types of Model Components.

A subsystem can be virtual or nonvirtual. A virtual subsystem provides graphical hierarchy in a model and does not impact the execution of a model. A nonvirtual subsystem executes as a single unit within a model.

Blocks

Subsystem

Group blocks to create model hierarchy

Functions

expand all

Subsystem Functions

`Simulink.BlockDiagram.createSubsystem`	Create subsystem containing specified set of blocks
`Simulink.BlockDiagram.copyContentsToSubsystem`	Copy graphical contents from system to empty subsystem
`Simulink.BlockDiagram.expandSubsystem`	Replace subsystem with subsystem contents
`Simulink.SubSystem.convertToModelReference`	Convert subsystem to model reference
`Simulink.SubSystem.copyContentsToBlockDiagram`	Copy graphical contents from subsystem to empty system
`Simulink.SubSystem.deleteContents`	Delete contents of subsystem