Messages & Events
R2026bBlocks for modeling message-based communication between components, such
as Send, Receive, and Queue
Use blocks from the Messages & Events library to model message-based communication between components. Message-based communication is necessary in distributed control system architectures where system complexity prevents a centralized approach. A message combines an event with related data, letting components communicate without requiring simultaneous execution.
To add blocks from this library to your model, see Add Blocks to Models.
Blocks
| Hit Crossing | Detect crossing point | |
| Hit Scheduler | Schedule major time steps for variable-step solver (Since R2022b) | |
![]() | Message Merge | Combine message paths |
| Message Triggered Subsystem | Subsystem whose execution is controlled by message input (Since R2022a) | |
| Queue | Enqueue messages and entities | |
| Receive | Receive messages | |
| Send | Create and send message | |
| Sequence Viewer | Display messages, events, states, transitions, and functions between blocks during simulation |
Tools
| Library Browser | Find and add blocks to model |
Topics
- Add Blocks to Models
Use the Library Browser and quick insert menu to insert blocks.
- Simulink Messages Overview
Overview of the message-based communication for distributed architectures, code generation, and middleware modeling.




