Function-Call Subsystem

Subsystem whose execution is controlled by an external function-call input

Library:
Simulink / Ports & Subsystems

Description

The Function-Call Subsystem block is a Subsystem block preconfigured as a starting point for creating a subsystem that executes when a function-call input port receives a function-call event. A Stateflow^® chart, Function-Call Generator block, or anS-function block can provide function-call events. See Using Function-Call Subsystems.

Use Function-Call Subsystem blocks to:

Schedule the execution order of model components.
Control the rate of model component execution.

Simulink ignores a priority set on a Function-Call Subsystem block. Instead, set the priority on a Inport block connected to the control port. The Inport block can receive a function-call event from a Stateflow chart, Function-Call Generator block, or an S-function block.

For an explanation of Function-Call Subsystem block parameters, see Subsystem, Atomic Subsystem, Nonvirtual Subsystem, CodeReuse Subsystem.

Ports

Input

expand all

`In` — Signal input to a subsystem block
scalar | vector | matrix

Placing an Inport block in a subsystem block adds an external input port to the block. The port label matches the name of the Inport block.

Use Inport blocks to get signals from the local environment.

`Function Call` — Function-call input port to a subsystem block
scalar

Placing a Trigger block in a subsystem block adds an external input port to the block. Selecting function-call from the Trigger type list, changes the block to a Function-Call port block that accepts function-call events.

Output

expand all

`Out` — Signal output from a subsystem
scalar | vector | matrix

Placing an Outport block in a subsystem block adds an output port from the block. The port label on the subsystem block is the name of the Outport block.

Use Outport blocks to send signals to the local environment.

Model Examples

Simulink Subsystem Semantics

This set of examples shows different types of Simulink® Subsystems and what semantics are used when simulating these Subsystems. Each example provides a description of the model and the subtleties governing how it will be executed.

Open Model

Model Reference Function-Call

Use a model reference block which is explicitly triggered by means of its function-call trigger port.

Open Model

Function-Call Blocks Connected to Branches of the Same Function-Call Signal

In this model, a Function-Call Feedback Latch block is on the feedback signal between the branched blocks.

Open Model

Function-Call Feedback Latch on Feedback Signal Between Child and Parent

In this model, the Function-Call Feedback Latch block is on the feedback signal between the child and the parent.

Open Model

Single Function-Call Subsystem

In this example, a single function-call subsystem output serves as its own input.

Open Model