Table of Contents
Advertisement
Chapter 5
Run Mode
Dynamic Chaining
Example #1
5–14
This example does not use special messages #8 and #9, therefore, messages
may not be displayed in the exact order in which they are triggered. This is
acceptable for most applications, and requires a more simple application
program in the host controller. Dynamic chaining must be enabled.
Event 1: A machine or system fault occurs and message #21 is triggered.
Event 2: Message #21 is displayed immediately, and remains displayed until
another message is triggered.
Event 3: A second machine or system fault occurs and message #31 is
triggered.
Event 4: Message #21 remains displayed for the specified wait time. Then
message #31 is displayed for the specified wait time. Then back to message
#21. Then back to message #31. This continues until a third message is
triggered. Then the display will simply alternate between all three in a
similar fashion. Up to 20 such messages can be triggered.
Event 5: An operator observes the various messages, responds accordingly,
and acknowledges the faults using some input to the host controller. The
host controller then triggers special message #2 to clear the display and the
queue. The DL20 is ready to receive new message triggers.
For some applications, as described above, it is recommended that an
acknowledge button be provided to assure that particular messages have been
seen by an operator.
If more than 20 messages must be displayed at the same time, use the PRINT
MSG attribute (without dynamic chaining). Otherwise the host controller
must be programmed to handle the extra messages.
Advertisement
Chapters
Table of Contents
