This System Configuration implements a Distribution Design for the pallet handling example.The screenshot above shows the result of performing the following actions:

1. Launching the MODEL Device on a Raspberry Pi 2 Model B running the Raspbian operating system, using the following terminal commands:
   

   cd fbdk8
   java -jar device.jar MODEL RMT_FRAME MGR_ID 192.168.0.14:61499

2. Launching the system from a desktop PC running the Bodhi Linux operating system with a single-core, 32-bit CPU clocked at 2.6 GHz with a 64-GB disk drive, using the following terminal commands:
   

   cd fbdk8
   java -jar system.jar LIFTER_MVCDR

3. Clicking the RESET button to initialize the system.
4. Clicking the LOAD button to load a pallet onto the FEED conveyor.
5. Clicking the RUN button.
6. Allowing the system to run through a complete cycle as shown in Steps 1-7 of the animation.
7. Causing a fault by clicking on the lifter.
8. Clicking the LOAD button to load another pallet.
9. Observing the occurrence of the TIMEOUT_LOADING diagnostic as shown above.
10. Clicking on the lifter to clear the fault, then creating another fault by clicking again while the pallet is rising.
11. Observing the occurrence of the TIMEOUT_UP diagnostic as shown above.

Additional faults can be introduced into the system at appropriate points in the operational cycle to produce the TIMEOUT_UNLOADING and TIMEOUT_DOWN diagnostic codes.

As shown below, this system configuration is derived from the LIFTER_MVCDL configuration by adding and configuring MODEL.TAGS and DIAGNOSTICS.TAGS resources. These resources map the local multicast services within the device boundaries, to UDP messaging between devices, using the Tagged Data Design Pattern, as shown in the table below (only the changes from the LIFTER_MVCDL System configuration are shown).