This System Configuration illustrates a distribution design of the ASM_MVCDL example in which the Model+View functions are located in a remote device named MODEL, the Control+HMI functions are in a local device named CONTROL, and the Diagnostic functions are in a local device named (surprise!) DIAGNOSTICS.

• See the ASM_MVCDR2 configuration for an example of using the efficient fbmgt2 device management scheme for the implementation of this configuration.

As shown in the table and figures below, each of the MODEL and DIAGNOSTICS devices contains a TAGS resource that uses the Tagged Data Design Pattern as follows:

• The MODEL.TAGS resource:
  • Gathers sensor data and publishes it remotely via the PRESS_SENSE and TRANSPORT_SENSE channels.
  • Receives remote actuator data and publishes it locally via the PRESS_ACT and TRANSPORT_ACT channels.
• The DIAGNOSTICS.TAGS resource:
  • Receives remote sensor data and publishes it locally to both DIAGNOSTICS and CONTROL devices via the PRESS_SENSE and TRANSPORT_SENSE channels.
  • Gathers actuator data from the CONTROL device and publishes it remotely via the PRESS_ACT and TRANSPORT_ACT channels.

Local Multicast channels are configured identically as in the ASM_MVCDL System configuration.