Create Components to Send Messages

In the model, there are two software components that output messages, Send and StateflowSend.

In the Send component, the Sine Wave block is the signal source. The block generates a sine wave signal with an amplitude of 1. The sample time for the block is 0.1. The Send block converts the signal to a message that carries the signal value as data. The Send component sends messages to Send Buffer 1.

In the StateflowSend component, another Sine Wave block generates a sine wave signal and a Noise block injects noise into the signal. The Noise block outputs a signal whose values are generated from a Gaussian distribution with mean of 0 and variance of 1. The sample time of the block is 0.1.

The Stateflow chart represents a simple logic that filters the signal and decides whether to send messages. If the value of the signal is greater than 0.5 for a duration greater than 0.1, then the chart sends a message that carries the signal value. If the signal value is below 0, then the chart transitions to the ReceiveSignal state. The StateflowSend component sends messages to Send Buffer 2.

For more information about creating message interfaces, see Establish Message Send and Receive Interfaces Between Software Components.

Create Components to Receive Messages

In the model, there are two software components that receive messages, Receive and Listener.

In the Receive component, a Receive block receives messages and converts the message data to signal values.

In the Listener component, there is a Simulink Function block. The block displays the function, onOneMessage(data), on the block face.

When a message arrives at Receive Buffer 2, the Listener block is notified and it takes the argument data, which is the value from the message data, as the input signal. In the block, data values are multiplied by 2. The block outputs the new data value.

Routing Messages using SimEvents®

In the shared channel, the message paths originating from the two message-sending components are merged to represent a shared communication channel.

A SimEvents® Entity Input Switch block merges the message lines. In the block:

A SimEvents® Entity Server block is used to represent message transmission delay in the shared channel. In the block:

A SimEvents® Entity Replicator block is used to generate identical copies of messages. In the block:

A SimEvents® Entity Terminator block is used to model Receive Buffer 2. In the block:

Simulate the Model and Review Results

Simulate the model. Observe that the animation highlights the messages flowing through the model. You can turn off the animation by right-clicking on the model canvas and setting Animation Speed to None.

When you pause the animation, a magnifying glass appears on the blocks that store messages. If you point to the magnifying glass, you see the number of messages stored in the block.

To observe which messages are stored in the block, click the magnifying glass to open the Storage Inspector. For instance, the graphic below illustrates the messages stored in Send Buffer 1.

Turn the animation off and open the Sequence Viewer block to observe the Simulink Function calls and the flow of messages in the model.

For instance, observe the simulation time 0, during which a message carrying value 0 is sent from the Send component to Send Buffer 1. From simulation time 0.1 to 0.5, the Send component keeps sending messages to Send Buffer 1 with different data values. At time 0.5, the StateflowSend component sends a message to Send Buffer 2. For more information about using the Sequence Viewer block, see Use the Sequence Viewer to Visualize Messages, Events, and Entities.