Main Content

Messages

R2026b
Establish message-based communication between Simulink® model components

Messages are used to model communication between Simulink components for the purpose of system integration. You can use messages to establish communication in a composition model whose components perform a defined set of functionalities with I/O boundaries.

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. Use message blocks to manage the production, consumption, and storage of messages.

To learn more about Simulink messages, see Simulink Messages Overview.

Blocks

expand all

Send blockSendCreate and send message
Receive blockReceiveReceive messages
Hit Crossing blockHit Crossing ProbeDetect crossing point
Queue blockQueue, Entity QueueEnqueue messages and entities
Message Merge blockMessage MergeCombine message paths
Block icon for Message Triggered Subsystem blockMessage Triggered SubsystemSubsystem whose execution is controlled by message input (Since R2022a)
Sequence Viewer blockSequence ViewerDisplay messages, events, states, transitions, and functions between blocks during simulation

Tools

expand all

Sequence ViewerVisualize messages, events, states, transitions, and functions

Topics

Understanding Simulink Messages

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

Model Message Send and Receive Interfaces

Model Event-Driven Receive Interfaces

Message-Based Computation

Simulate Middleware Effects on a Distributed Architecture