This System Configuration illustrates the use of the Local Multicast design pattern to implement the Time-Stamped Messaging design pattern. As shown at right:

• The AGENT1 resource of the AGENTS device contains an instance of the REQUESTER FB type to simulate the operation of a software agent.
  • An event from an IN_EVENT button triggers the operation of an instance of the E_TRAIN type.
  • The E_TRAIN outputs drive an instance of the RQSTR_TGEN type to produce a sequence of test events and data for the simulated agent.
  • The resulting outputs from the simulated agent are then converted to service primitive format by an instance of the E_TO_PRIM2 type, time stamped by an instance of the STAMP_MSG type, and transmitted for logging via the MSG_LOG local multicast channel.
• the LOG_RES of the LOG device receives the generated service primitive reports from the MSG_LOG local multicast channel and displays them on an instance of the MSG_LOG HMI FB type.

The figure below shows the result of clicking the Agent 1 button; waiting 6 seconds for the sequence of messages to complete; clicking the Agent 2 button and waiting again; then clicking the Agent 1 button immediately followed by the Agent 2 button.