Message-Based Communication

Use messages to establish communication between Simulink^® model components

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

Message-based communication between software components is necessary in control system architectures in which 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. For more information, see Message-Based Communication Between Software Components.

Blocks

expand all

Send and Receive Messages

Send	Create and send message
Receive	Extract data from received messages
Hit Crossing Probe	Detect crossing point

Store Messages

Queue, Entity Queue

Enqueue messages and entities

Simulate and Visualize Messages

Sequence Viewer

Display messages, events, states, transitions, and functions between blocks during simulation

Topics

Message-Based Communication Between Software Components

This example shows how to model message-based communication between software components that run in different applications.

Use a Queue Block to Manage Messages

This example shows how to use a Queue block to customize the message-based communication between model components by storing and queuing messages.

Visualize, Animate, and Inspect Messages

This example shows how to visualize messages in a simple message-based communication framework using the Simulation Data Inspector, Animation, and Storage Inspector.

Use the Sequence Viewer Block to Visualize Messages, Events, and Entities

View the interchange of messages, events, and functions through the Sequence Viewer block.

Featured Examples

Run Based on Message Data Availability

Synchronize execution to data availability in message-based systems. We show how to model this behavior using events and actions. This example builds on another example, Message-Based Communication Between Software Components, where two software components communicate using messages.

Open Script