Messages & Events

Blocks for modeling message-based communication

Message-based communication between software components is necessary in control system architectures where centralized architectures are replaced by distributed architectures due to system complexity. A message is a useful modeling artifact that combines events with related data.

Blocks

Hit Crossing	Detect crossing point
Hit Scheduler	Schedule major time steps for variable-step solver (Since R2022b)
Message Merge	Combine message paths (Since R2021a)
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

Topics

Simulink Messages Overview
Overview of the message-based communication for distributed architectures, code generation, and middleware modeling.

Featured Examples

Establish Message Send and Receive Interfaces Between Software Components

Create message send and receive interfaces, and prepare components for C++ code generation.

Open Model

Schedule When Traffic Camera Takes Snapshot

Use the Hit Scheduler block to schedule when a traffic camera captures an image of a speeding car.

Open Live Script