Main Content

Triggered Subsystem

Subsystem whose execution is triggered by external input

  • Library:
  • Simulink / Ports & Subsystems

    HDL Coder / Ports & Subsystems

  • Triggered Subsystem block

Description

The Triggered Subsystem block is a subsystem block preconfigured as a starting point for creating a subsystem that executes each time the control signal has a trigger value.

Use Triggered Subsystem blocks to model:

  • A task that runs with the detection of a trigger value.

  • An interrupt from I/O hardware.

  • A processor request to handle an exception or error.

For an explanation of the Triggered Subsystem block parameters, see Subsystem.

Ports

Input

expand all

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.

Data Types: half | single | double | int8 | int16 | int32 | int64 | uint8 | uint16 | uint32 | uint64 | Boolean | fixed point | enumerated | bus | image

Placing a Trigger block in a subsystem block adds an external input port to the block.

Data Types: single | double | int8 | int16 | int32 | int64 | uint8 | uint16 | uint32 | uint64 | fixed point

Output

expand all

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.

Data Types: half | single | double | int8 | int16 | int32 | int64 | uint8 | uint16 | uint32 | uint64 | Boolean | fixed point | enumerated | bus | image

Block Characteristics

Data Types

Booleana | busa | doublea | enumerateda | fixed pointa | halfa | integera | singlea | stringa

Direct Feedthrough

no

Multidimensional Signals

limiteda

Variable-Size Signals

limiteda

Zero-Crossing Detection

no

a Actual data type or capability support depends on block implementation.

Extended Capabilities

Version History

Introduced before R2006a