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

MOD 30ML Display Guide
Application Examples
5.6 Example 6: Multiple Tune Lists
In some applications it may be either desirable or necessary to use more than one Tune
List block with a single Display Block. Uses of this feature might include:
• the number of variables to be considered “tuneable” is greater than 40;
• tuning parameters are to be grouped in different lists; or
• Tune Lists are used for separate recipe definition.
This example is uses the compound PID&DISP as a starting point. This compound is
supplied with Visual Application Designer. The inputs and formats are the same, and key
functions are almost identical. Pressing the SCROLL key in this example scrolls through
OP, SP and a new option, TUN, where the user selects the desired Tune List. Also, a new
state-type input, TUNE_REQ, and an associated format are needed to allow the operator
to select between Tune Lists.
Because only one graphical connection can be made between a TL block and a Display
Block, and because Tune List blocks cannot be ‘nested’, two Display Block internal
attributes are provided called TUNING and TUNELIST. These attributes are used
exclusively when multiple TL Blocks are associated with a single Display Block.
TUNING is a discrete attribute monitored by the Display block to determine if a Tune List
is being shown on the front of the instrument. If a Tune List is displayed, then the value
of TUNING for the Display Block associated with that list will be TRUE. If no list is
showing, this attribute will have a value of FALSE
TUNELIST is a local count attribute used to identify which tune list is to be placed on the
display. It uses the actual occurrence numbers of the individual TL blocks.
Three new inputs are added to the Display Block for this example:
• TUNE_REQ – a Count input. The associated format defines the Entry Method as
Entry Req’d, meaning the operator must press the flashing ENT (enter) key to
access the tuning displays. A case statement is added to the Display Script for
selecting which tune list will be displayed.
• TL_CTRL – a count input representing a tuning list which contains Gain, Reset,
Preact, Action, etc. This is set as a constant with a value equal to the occurrence
number of that tuning list.
• TL_ALARM - a count input representing a tuning list which contains alarm related
parameters such as trip points. This is set as a constant with a value equal to the
occurrence number of that tuning list.
Caution: Although the user can estimate the occurrence numbers by the order in which
the blocks were placed in the strategy, occurrence numbers are actually assigned at
the time of a successful compile. After compiling the strategy be sure the Internal value
in the Display Block Input menu for each Tune block matches its true occurrence
number.
5 - 23