This system configuration provides a framework for testing instances
LED_HMI FB types in one remote
FLASHER), with their control elements in a
separate remote device (
By using the Tagged Data design pattern for UDP
multicast communication, the
Resources can be configured identically to the
Resources of the
System configuration, respectively.
The side-by-side screen images below show the results of the following procedure:
FLASHERdevice from the screen on the right, which is connected to a Raspberry Pi 2 Model B running the Raspbian operating system, using the following terminal commands:
CONTROLdevice from the screen on the left, which is connected to 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:
- Launching the configuration with the FBDK in a separate terminal or one of the target devices.
- Resizing the CONTROL and FLASHER windows and moving them into adjacent positions on the two displays.
Changing the inter-event time interval
DTfrom the initial value of
MODEfrom the initial value of
- Initiating FLASHER operation by clicking on the RUN button.
This System configuration uses the Local
Multicast design pattern, as well as UDP
multicast, for the communication of data and events among
Resources. The FBDK uses the Tagged
Data design pattern to ensure consistency of the communicated
events and data, as shown in the table below. This is implemented in
TAGS Resources as shown below.
|Tag Name||Type(s)||UDP Channel||Description|