|On this page…|
The following table lists blocks in the Simulink® and Stateflow® libraries that can operate directly on event-based input signals. If the block has an event-based input signal and a Sample time parameter in the block dialog box, you must set Sample time to -1 to indicate an inherited sample time.
Tip If the block of interest is not in the table but has an inherited or constant sample time, you can still use the block to perform a computation on an event-based signal. Connect the event-based signal to an Atomic Subsystem or Function-Call Subsystem block, and insert the computational block into the subsystem.
|Atomic Subsystem||Ports & Subsystems|
|Bus Creator||Signal Routing|
|Bus Selector||Signal Routing|
|Data Type Conversion||Signal Attributes|
|Dot Product||Math Operations|
|Function-Call Split||Ports & Subsystems|
|MATLAB Function||User-Defined Functions|
|Function-Call Subsystem||Ports & Subsystems|
|Goto Tag Visibility||Signal Routing|
|Logical Operator||Logic and Bit Operations|
|Math Function||Math Operations|
|Product of Elements||Math Operations|
|Reciprocal Sqrt||Math Operations|
|Relational Operator||Logic and Bit Operations|
|Slider Gain||Math Operations|
|Subsystem||Ports & Subsystems|
|Unary Minus||Math Operations|
These blocks in the Simulink Sinks library can display, report on, or terminate event-based input signals.
Except for the Timed to Event Signal and Timed to Event Function-Call blocks, all blocks in the SimEvents® libraries that have signal input ports require the input signals to be event-based signals rather than time-based signals.
A block that is not in one of the SimEvents libraries, Simulink libraries, or Stateflow library cannot directly operate on event-based signals. However, if the block has an inherited or constant sample time, you can connect the event-based signal to an Atomic Subsystem or Function-Call Subsystem block, and then insert the block that is not in one of the libraries into the subsystem.