Subsystem whose execution is controlled by an external function-call input
Simulink / Ports & Subsystems
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.
In— Signal input to a subsystem block
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.
fixed point |
Function Call— Function-call input port to a subsystem block
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
Out— Signal output from a subsystem
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.
fixed point |
Actual code generation support depends on block implementation.
Actual data type support depends on block implementation.