Function-Call Subsystem

Subsystem whose execution is controlled by external function-call input

Libraries:
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, S-Function block, or Hit Crossing 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 any priority set on a Function-Call Subsystem block, but you can set the priority on a block connected to the function-call port of the subsystem. The function-call port can receive a function-call event from a Stateflow chart, MATLAB Function block, Function-Call Generator block, S-Function block, or Hit Crossing block.

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 block that 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

Function-Call Subsystem with Merged Signal As Input

In this model a merged signal serves as the input to a function-call subsystem.

Open Model

Ports

Input

expand all

In — Signal input to Subsystem block
scalar | vector | matrix

Signal input to a Subsystem block, specified as a scalar, vector, or 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 receive signals from the local environment.

Function Call — Function-call input to Subsystem block
scalar

A Trigger block in a Subsystem block adds an external input port to the block. A Trigger type of function-call makes the block a Function-Call port block that accepts function-call events.

Output

expand all

Out — Signal output from Subsystem block
scalar | vector | matrix

Signal output from a Subsystem block, returned as a scalar, vector, or matrix. Placing an Outport block in a Subsystem block adds an external output port to the block. The port label matches the name of the Outport block.

Use Outport blocks to send signals to the local environment.

Parameters

For an explanation of the Function-Call Subsystem block parameters, see Subsystem.

Block Characteristics

Data Types	`Boolean^a` \| `bus^a` \| `double^a` \| `enumerated^a` \| `fixed point^a` \| `half^a` \| `integer^a` \| `single^a` \| `string^a`
Direct Feedthrough	`no`
Multidimensional Signals	`yes^a`
Variable-Size Signals	`yes^a`
Zero-Crossing Detection	`no`
^a Actual data type or capability support depends on block implementation.

Extended Capabilities

C/C++ Code Generation
Generate C and C++ code using Simulink® Coder™.

Actual code generation support depends on block implementation.

PLC Code Generation
Generate Structured Text code using Simulink® PLC Coder™.

Fixed-Point Conversion
Design and simulate fixed-point systems using Fixed-Point Designer™.

Actual data type support depends on block implementation.

Version History

Introduced before R2006a

Function-Call Subsystem

Description