Micromod MOD: 30ML Display Script Guide - Manual (Page 45)

MOD 30ML Display Guide
Display Scripts
Figure 3 .2.
Example: Display
Resource
Assignment
DEFAULTS:
{
{
MANUAL_PRESSED:
#LINE5 = “OP”;
#LINE6.SRC = OP;
OPMS = 0;
}
(Display State name)
(When manual key is pressed, then)
(Line 5 reads OP)
(Line 6 source is the Display Block Input
called “OP”)
(Output Mode is changed to 0 (manual))
In the above example, two inputs to the Display Block are the output (OP) attribute and
the output mode status (OPMS) attributes of a PID block. The value shown on Line 6 will
change with the actual output value. The value 0 (zero) is written to the OPMS attribute
of the PID block by the Display Block.
Note the open and closed brackets around the resource assignment script. This tells the
block that all script within these brackets belongs to the MANUAL_PRESSED event.
Also notice that semicolons follow each of the resource assignments.
When a key action at the front panel is used to cause a change in an attribute in an
algorithm block, the connection appears to work “backward”. That is, the new value
is written to a Display Block input, even though it acts as an output to the algorithm
block. The connection is always from the algorithm block to the Display Block, as
shown in Figure 3-3.
Figure 3 .3.
Sample connection
for writing from front
panel
PID DISP
OPMS I1
The Beeper (annunciator), LED and Up/Down display resources are normally defined by
the system. Table 3-3 defines expected display results based on values assigned to each of
these display resources. As can be seen in the table a display resource normally defined
by the system can be returned to the system by using a value as defined.
3 - 7