Training Exercises For MOD 30ML
Training Exercises For MOD 30ML
The Company
MicroMod Automation is dedicated to improving customer efficiency by providing the most cost-effective, application-specific process solutions
available. We are a highly responsive, application-focused company with years of expertise in control systems design and implementation.
We are committed to teamwork, high quality manufacturing, advanced technology and unrivaled service and support.
The quality, accuracy and performance of the Company's products result from over 100 years experience, combined with a continuous
program of innovative design and development to incorporate the latest technology.
Use of Instructions
Ì Warning. An instruction that draws attention to the risk of Note. Clarification of an instruction or additional
injury or death. information.
q Caution. An instruction that draws attention to the risk of i Information. Further reference for more detailed
the product, process or surroundings. information or technical details.
Although Warning hazards are related to personal injury, and Caution hazards are associated with equipment or property damage, it
must be understood that operation of damaged equipment could, under certain operational conditions, result in degraded process
system performance leading to personal injury or death. Therefore, comply fully with all Warning and Caution notices.
Information in this manual is intended only to assist our customers in the efficient operation of our equipment. Use of this manual for
any other purpose is specifically prohibited and its contents are not to be reproduced in full or part without prior approval of MicroMod
Automation, Inc.
The relevant sections of these instructions must be read carefully before proceeding.
1. Warning Labels on containers and packages must be observed.
2. Installation, operation, maintenance and servicing must only be carried out by suitably trained personnel and in accordance with the
information given or injury or death could result.
3. Normal safety procedures must be taken to avoid the possibility of an accident occurring when operating in conditions of high
4. pressure and/or temperature.
5. Chemicals must be stored away from heat, protected from temperature extremes and powders kept dry. Normal safe handling
procedures must be used.
6. When disposing of chemicals, ensure that no two chemicals are mixed.
Safety advice concerning the use of the equipment described in this manual may be obtained from the Company address on the back
cover, together with servicing and spares information.
Contents
Contents
REPORTS.................................................................................................................... 19-1
i
MOD 30ML TRAINING MANUAL
Contents
ii
1 MOD 30ML Front Face Familiarization
Lab
1.1 Foreword
Many processes involve flow control loops, whether they are in the food, pharmaceutical,
chemical, pulp & paper, mining or virtually any of the industries served by MODCELL
Multi-loop Processors. This lab is designed to help you learn the basic features of the
Application Builder, as well as how to easily demonstrate configuration of a PID loop.
1.2 Objectives
In this lab we will download a simple PID control database from a memory module to the
MOD 30ML controller and get familiarized with the controller’s front face.
Figure 1 .1.
MOD 30ML Front
Face
After completing this lab, you should know how to download a database from a memory
module to a MOD 30ML controller and operate standard PID control loop from the front
face.
1. 1 x MOD30ML
1-1
Training Manual
1.4 Instructions
1.4.1 Before you power up the instrument
Step Procedure Comments
1 Make sure the SERV/RUN switch This ensures that after a download the database
under the front face is set to the will be able to run.
RUN position This switch is located behind the front panel in the
NEMA 4 option. You will need to remove the
instrument from its housing to set it.
2 Make sure the switches on the This ensures that the database stored in the
memory module are set to READ memory module is downloaded to the instrument
ONLY and NORMAL during a power-up sequence.
3 Loosen the retaining screw and slide CAUTION ! Ensure that the main circuit board is
the instrument from the housing supported at all times.
4 Install the memory module With the catalogue number of the memory module
facing upwards, install the memory module onto
the connector of the main circuit board
5 Place the instrument back into the You should see ******** appear for a short while,
housing and tighten the retaining then a flashing loop display with the tag FIC-100
screw and the alarm light.
1-2
Training Manual
1-3
Training Manual
1-4
Training Manual
Line 2 will display the process input and units = 0.00 GPM
1-5
Training Manual
2. Press the AUTO key, next to FST, 3 The cursor is now blinking under the blank space
times to the left of the output value _0.00%
4. Press the R/L key , next to The cursor moves to the second digit to the left of
the decimal point 20.00%
SLO, 1 time
6. Press the R/L key , next to The cursor moves to the first digit to the right of the
decimal point 24.00%
SLO, 1 time
Advantage: The operator can set the exact desired value with no overshoot
1-6
Training Manual
You can use the method described in section 1.4.5 - OPERATING THE RAMP KEYS to
change the value of the setpoint.
2. Press and hold the SCROLL key The top of the display indicates TUNE
PASSWORD
FST, SLO, and ENT indicators are flashing
Arrows appear to allow changing of the numerical
tuning password on the bottom line
1-7
Training Manual
10. Press the TAG key again This will return you to the FIC-100 loop display
11. Record the communication information for this instrument in the next table.
1-8
Training Manual
Communication Information:
Modbus
Address
Baud Rate
Stop bits
Built-In Comm
Enabled
1-9
Training Manual
Notes:
1 - 10
2 MOD 30ML Operation Lab 2
2.1 Foreword
MOD 30ML can perform complex continuous control as well as discrete control. The
Sequencer block in the MOD 30ML can be used for executing complex batch and
sequencing control. Custom displays can be built for information and operation of the
advanced control.
2.2 Objectives
In this lab we will download a batch control strategy from the memory module to the
MOD 30ML controller and run the batch from the custom displays.
Control of a batch reactor includes sequential and continuous elements, and tight control
of the reaction temperature. Ideally, only one device is used to perform both types of
control, with a common local display interface providing complete process information.
The following demonstration will show:
Reactants are added to the reactor at room temperature; the reaction mass is heated to
reaction temperature; the reaction is carried out to form products; the batch is cooled; and
the reactor is emptied. Total batch time in reactors used in the manufacture of PVC or
polystyrene, for example, is approximately fourteen to eighteen hours. The progression of
the batch cycle is controlled by the sequence operation. It may sometimes be necessary
for the operators to pause, stop, or manually advance the cycle to another step.
2-1
Training Manual
Figure 2 .1.
Batch Temperature
Cycle
During the heat stage of the batch cycle, a cascade temperature loop is used to control
temperature. At the time the sequence enters the heating step, the setpoint of the master
controller is ramped to the reaction temperature; the master controller measures the
product temperature while the slave measures jacket temperature. At the cooling stage,
the setpoint is ramped back to the cool setpoint.
Figure 2 .2.
Batch Reactor
The MOD 30ML is performing the process simulation as well as the sequence control and
temperature cascade control. Once started, the batch cycle will progress automatically
unless it is switched to manual mode.
The following operations may be done from the front panel displays:
• Batch initialization
• Recipe selection
• Recipe parameter entry
2-2
Training Manual
Initial Conditions:
1. Batch AUTO, OFF (Note: once the batch has been started, Line 2 will indicate
the Time in Step for each step. If the batch is put into manual mode, Line 2 will
display Manual. The “time in step” timer does not stop if the batch is put into
manual. However, if you manually advance to another step, the step timer re-
starts).
2. RECIPE 1 selected
3. Temperature setpoint LOCAL
4. Level 0.0” H2O
5. Step OFF
2-3
Training Manual
2.3 Instructions
2.3.1 Download Reactor database from the memory module:
Step Procedure Comments
1 Make sure the SERV/RUN switch This ensures that after a download the database
under the front face is set to the will be able to run.
RUN position This switch is located behind the front panel in the
NEMA 4 option. You will need to remove the
instrument from its housing to set it.
2 Make sure the switches on the This ensures that the database stored in the
memory module are set to READ memory module is downloaded to the instrument
ONLY and NORMAL during a power-up sequence.
3 Loosen the retaining screw and slide CAUTION ! Ensure that the main circuit board is
the instrument from the housing supported at all times.
4 Install the memory module With the catalogue number of the memory module
facing upwards, install the memory module onto
the connector of the main circuit board
5 Place the instrument back into the You should see ******** appear for a short while,
housing and tighten the retaining then a display as shown in the next figure should
screw appear.
Figure 2 .3.
Batch main display
2-4
Training Manual
2 Press the TAG key once to go to the This is the Master temperature controller.
TIC-100 temperature control loop
display. See the next figure.
Read the temperature of the product. Master temperature controller TIC-100 setpoint
Read the output. Press the SCROLL 100ºF.
key to show the setpoint at the
bottom.
Press the TAG key again to go to This is the Slave temperature controller.
TIC-101 control loop display. See
the next figure.
Slave temperature controller TIC-101 setpoint
Read the process, setpoint and 200ºF.
output values.
Setpoint is in Remote mode (REM). Its value is
same as the output value of the TIC-100 loop.
Figure 2 .4.
TIC-100, TIC-101
and Flow/Level
Displays
2-5
Training Manual
You can display and manipulate on one instrument, all process and calculated values
associated with the process unit, including both sequence and continuous control.
2.3.3 View the Tuning displays and change the batch recipe:
3 Display tuning pages for TIC-100 Tuning displays for controller algorithm type,
and TIC-101. controller action, gain, reset
First switch to the control display Commissioning activity can take place through
(TIC-100 or TIC-101) and then hold front panel of instrument.
down Scroll key to access the tuning
display.
4 Display recipe selection by returning This is a tuning display within the main batch
to main batch display and holding display to select and change the recipe for the
down scroll key. batch.
Enter tuning password of 1 (if Once tuning password is entered the recipe can be
required; the tuning password from scrolled between the choices of Recipe 1 and
the previous activity may still be in Recipe 2
effect)
Press NXT key to view recipe You can view and change the following
parameters parameters: Reaction temperature setpoint entry,
Reactor level, Fill A rate, Fill B rate
Figure 2 .5.
Recipe Tuning
display
2-6
Training Manual
Press AUTO key to start the batch Batch status changes to RUN
Figure 2 .6.
Batch main display
6 Scroll to fill display Fill A and Fill B flow rates displayed on lines 1 and
2, left and middle bar
See the next figure: Reactor level displayed on Line 6 and right bar
Figure 2 .7.
Batch Flow/Level
display
2-7
Training Manual
8 When controller has entered Cascade control for temperature is now active
HEATUP step, scroll to temperature Master controller setpoint value ramps to 111ºF.
control displays (TIC-100 and TIC-
101)
Read the process value of TIC-100. This will also ramp to 111 def F in a couple of
minutes
Refer to the next figure.
Figure 2 .8.
Master
Temperature
control loop
Note that in MOD 30Ml, continuous control is completely integrated with sequential
control without the need for an external device. Cascade with full tracking provides
tight temperature control.
2-8
Training Manual
Press MAN key to put batch cycle in STP indication appears next to Scroll key
manual control
Figure 2 .9.
Batch in Hold
Press MAN key again to return batch Batch time shows on line 2.
cycle to automatic control
Batch resumes automatic control in COOLDOWN
step
Figure 2 .10.
Cool Down Step
2-9
Training Manual
12 When batch cycle has entered Falling reactor level as vessel is drained
DRAIN cycle, scroll to level display
13 Scroll back to the main display When drain cycle is finished (level has returned to
0) and current step shows as END.
Figure 2 .11.
Batch End
13 Press the MANUAL key, change the The display will look like the initial display as
step to OFF, and press the AUTO shown in Figure 2 .3.
key to return the batch to OFF
status.
Press the MAN key again to change The batch can be repeated now.
to automatic mode.
2 - 10
3 Single Loop Template Lab
3.1 Foreword
Many processes involve flow control loops, whether they are in the food, pharmaceutical,
chemical, pulp & paper, mining or virtually any of the industries served by MODCELL
Multi-loop Processors. This lab is designed to help you learn simple PID loop
configuration from the MOD 30ML front face.
3.2 Objectives
In this lab we will design a simple flow loop with a 4-20mA signal from a dP transmitter,
a square root extractor, a PID control loop and a modulating control valve. The P&ID for
this loop looks like this:
Figure 3 .1. FY FC
Sample Flow PID
Loop
FT
FCV
FE
After completing this lab, you should know how to configure a MOD 30ML database
using ViZapp Configurator for a simple PID Control loop.
3-1
Training Manual
3.3 Instructions
3.3.1 Power up the controller
1. We will remove the memory module if any from the controller. Loosen 2 screws on
Faceplate on controller and remove Instrument from housing. Remove Memory module from
Instrument. Return Instrument to housing. Removing the memory module will prevent
downloading of configuration from the memory module in case the instrument is powered
up.
4. Read lines 1 and 2 on the display. These lines describe the alarm.
5. Read line 3. This line will describe condition of alarm. If line 3 displays UAK then the
current alarm displayed is an unacknowledged alarm. If line 3 displays ACT then the alarm
is acknowledged, but still active.
Figure 3 .2.
MOD 30ML Alarm
UnAcKnowledged
Alarm
6. Acknowledge the alarm: Press the key next to line 3 (the AUTO or “A” key) to
acknowledge. This will change the condition of the alarm. For example, if the alarm was
unacknowledged (UAK), then the message will change to ACT if the alarm is still active
or CLR if the alarm cleared.
3-2
Training Manual
Figure 3 .3.
MOD 30ML Alarm
CLeaRed Alarm
3-3
Training Manual
1. DEV STAT – This menu allows you to access the following sub menus: (The sub
menus are reached by pressing the DOWN arrow from the main menu.)
6. TEMPLATE – Read and edit System compound for system parameters and insert and
edit user templates for configuring Single loop and Cascade PID control loops. This
menu has the following sub menus:
• System Compound
• User Compounds
The front face configuration map is shown in appendix. You can use this map for
reference and as a navigation tool for going through and setting up the menus and
configuration from the controller front face.
3-4
Training Manual
2 Press the NXT (the key next to the See the menu items changing in line 6.
NXT display on the front face).
3.3.5 Delete the main database and familiarize with the DEV STAT
menu:
We will delete the database that is running in the controller, before configuring a new one.
Follow the steps below to delete the main database:
1 Press and hold TAG key until *DEVICE* DEV STAT will be displayed on line 6.
is displayed on line 1. DEV STAT provides access to State
Commands, Shutdown information and
See the figure below: acknowledgment, Status Commands, Execution
Times and Current Time, Date and Day.
Figure 3 .5.
3 Use UP key three times to select the Lines 1 and 2 will display CURRENT LEVEL and Line
PASSWORD and then use ENT to 6 will display CONFIG indicating that the controller
enter. is in configuration mode.
3-5
Training Manual
4 Press ENT again to enter Lines 1 and 2 will display DEV STATE and
Configuration mode. You will be in INSTATE (Instrument state). Line 6 will display
DEV STAT menu mow. See the RUN indicating that the controller is running a
sequence of figures below: valid database.
5 Press the NXT key until COMMANDS is You can issue commands to the controller from
displayed on line 2. this menu.
Figure 3 .6.
7 Press NXT key until ACK ALL is Used for sending global acknowledge command
displayed on line 2. causing all diagnostics, alarms and notification
/request messages to be acknowledged.
8 Clear ACK ALL by pressing the DOWN YES will be displayed on line 6.
key.
9 Press the ENT key. Press NXT key RESET is used to complete tasks and then
perform a power-up
12 Delete Main database by pressing the DEL MAIN is used to mark the main database as
DOWN key, then press the ENT key bad and set the instrument state to DEFAULT.
The controller ALARM light will be flashing at
this time.
3-6
Training Manual
Figure 3 .7.
13 Acknowledge UNCONFIG alarm by The Alarm display will show INST UNCONFIG
pressing the ALARM key and the saying that the instrument is unconfigured.
AUTO key.
15 If line 2 displays DEL MAIN go to If the instrument state has not changed, you will
Step 17 otherwise continue at step 16. return to the same line in the database DEL MAIN.
If the instrument state has changed you will
abort to top level with DEV STAT displayed on line
6.
3-7
Training Manual
Figure 3 .8.
18 Press NXT key, then press the UP You are exiting the COMMAND section
key
24 Press UP key. You are now at the “top” level of the template
configuration tree. Line 1 will display DEVICE and
Line 6 will display DEV STAT
3-8
Training Manual
Figure 3 .9.
4 Answer YES by pressing DOWN and ENT Defaults are the safe or most commonly used
values.
There are two types of compounds available in the instrument database. They are:
• System Compound and
• User Compound.
The System Compound sets some global parameters that will be used by user compounds.
We do not want to make changes to the System compound. We will insert a template for a
User compound and edit it to perform our Flow control loop.
3-9
Training Manual
Figure 3 .10.
1 Use the Arrow keys to scroll through INSERT is used to add a user compound after
INSERT, EDIT, and LIST. DO NOT system compound.
PRESS ENTER LIST allows you to use the NXT key to scroll
through any configured Loop Compounds, or tags
EDIT allows you to access the compound to
change parameters
2 When EDIT is displayed on line 6, We will now edit the system compound to
press ENT establish some global parameters. SYSTEM DEV TAG
should be displayed on lines 1 and 2. TEMP 100,
the default device tag, should be displayed on
Line 6 as shown in the next figure.
3 Use the following procedure to Modify device tag using standard set of
change the Tag to CLAS6000: characters. This tag identifies instrument itself, not
the individual loops in the instrument
6 Press ENT
3 - 10
Training Manual
Figure 3 .11.
.
7 Press NXT to access System Scan Scan groups defined update intervals for
Groups. loops.
8 Press DOWN SYSTEM SCANGRPS should be displayed on lines
1 and 2. See the figure above.
11 Press ENT
3 - 11
Training Manual
We will change the system tune and configuration passwords in this section.
2 Press UP key to set 1 as password then Enter a number required to access tuning
press ENT. parameters.
5 Press NXT
7 Press UP to change line 6 to the number This will give us 5 minutes before the tune and
5. Press ENT configure access levels will timeout and return
to the operator level after the last keyboard
activity.
Figure 3 .12.
8 Press NXT
3 - 12
Training Manual
4 Press NXT
5 Set MINIMUM LOW PRI to 5 and press ENT. All process alarms with priority >= this value (2
- 255) are considered LOW priority for display
purposes.
7 Press NXT
8 Set HIGH PRI FLASH to ENABLE and press OFF = flashing is disabled
ENT ENABLE = flash display on alarm
Figure 3 .13.
3 - 13
Training Manual
3 - 14
Training Manual
1 Press UP arrow twice to select EDIT on TAG ID STRING on lines 1 and 2. CTAG01 on line 6.
line 6 and press ENT
3 Press NXT
.
4 Press DOWN until the I is displayed as
the second character
5 Press NXT
7 Press NXT
Figure 3 .14.
8 Continue on with this sequence until you Pressing ENT will enter the new tag name in the
have FIC-100 displayed, then press ENT. database
3 - 15
Training Manual
Figure 3 .15.
3 - 16
Training Manual
2 Press DOWN This takes you into the process input definition
menus. SLOT will be displayed on line 2.
3 BI 1 AIN is the default input. We will This is Built-In Analog Input 1. Inputs may be
accept this. defined as NONE, BI AIN 1, BI AIN 2 or module
slot S01- to S11- for input being configured
Figure 3 .16.
5 VOLTS is the default for the process input. Input types may be defined as: VOLTS, MVOLTS,
Press UP and then ENT to change this CURRENT, RESIST, THRMOCPL
to CURRENT. 1 Slot: RTD2WIRE, CURRNT2W
2 Slots: RTD3WIRE, WIDERES
Built-in only: TC W/CJC, RTD
6 Press NXT until LO SIGNL is displayed on
Line 2
7 Press the DOWN arrow and FST/SLO Built-in analog input 1 is wired to a pot in the
keys to change the low signal range to 4 demonstration unit which has a range of 0 to 6
Volts
11 Use the UP/DOWN keys and the FST Pressing the Up key, will cause the Least
3 - 17
Training Manual
key to set the range at 200. Then press Significant Digit to flash, indicating you can
ENT change that digit. Each time you press the FST
key the flash digit will move one digit to the left.
Pressing one of the arrows will cause the flashing
digit to ramp up or down.
Figure 3 .17.
13 Using the UP/DOWN keys and NXT key, Up to a 4 character label to appear after process
spell out GPM input value. First character entered becomes
Then press ENT leftmost character
15 Using the UP/DOWN keys enter -20.0 as Result is set BAD if it goes below this value.
low quality limit. Then press ENT
Figure 3 .18.
3 - 18
Training Manual
19 Press UP
Figure 3 .19.
3 - 19
Training Manual
2 Press NXT until SETPOINT HI LIMIT is Setpoint values to the PID algorithm are limited
displayed on lines 1 and 2. to this number or below
5 Set the value at 100.0. Then press ENT. Setpoint value when configuration is complete.
6 Press NXT until lines 2 and 6 are blank COMPOUND will be displayed on Line 1
and only the up arrow is on.
8 Press NXT This takes you to the top of the Control section.
Line 2 will display CONTROL.
Figure 3 .20.
3 - 20
Training Manual
Figure 3 .21.
Figure 3 .22.
3 - 21
Training Manual
7 Press NXT until lines 2 and 6 are blank COMPOUND will be displayed on Line 1
and only the up arrow is on.
3 - 22
Training Manual
2 Leave the default value of BI1 AOUT in NONE, BI1 AOUT, BI2 AOUT, and
place S01 to S11. Only available outputs are listed.
3 Press NXT
OUTPUT LO SIGNL displayed. 0% of the output
range.
4 Press NXT
OUTPUT HI SIGNL displayed. 100% of the output
range
Figure 3 .23.
5 Press NXT until OUTPUT LO LIMIT PID output limited to this number or above.
displayed
7 Press NXT, OUTPUT HI LIMIT displayed PID output limited to this number or below.
3 - 23
Training Manual
Figure 3 .24.
9 Press NXT until Line 2 displays OUTPUT This is the initial value of the output on
INIT VAL download
3 - 24
Training Manual
8 Operate your PID loop by changing the Refer to the MOD 30ML Operation Lab 1 for more
output, setpoint and also by getting into information on operating the PID loop.
TUNING mode and by changing the
GAIN and RESET values.
Figure 3 .25.
3 - 25
Training Manual
3 - 26
4 MOD 30ML Diagnostics Lab
4.1 Foreword
The MOD 30ML provides a comprehensive way of displaying active diagnostic
information as well as a history of events. Events are a combination of alarms and
information only activities that the instrument had gone through.
4.2 Objectives
We learned how to read the active diagnostics and acknowledge them in Chapter 1. In this
lab we will read the diagnostics history by using the Event Viewer available from the
front-face. We will also force the instrument to shutdown and read the shutdown
information.
After completing this lab, you should know how to read the Event Queue of the controller
and also the Shutdown information.
1. 1 x MOD30ML
4-1
Training Manual
4.4 Instructions
4.4.1 Event Viewer
The System Event block stores diagnostics reported by the data base blocks. Viewing the
system event queue provides data on all diagnostics that have occurred since the current
data base was down loaded or the queue was cleared. The queue contains both
informational and diagnostic data. The data for each event in the queue is displayed on
two pages. View the data in the event queue using the following procedure:
Note: The procedure given here is an example. You may get a completely different set
of events in the event viewer depending on what is in your event queue.
2 Press NXT repeatedly until the Device See the figure in the middle.
Events display appears.
3 Press down arrow to enter the event Page 1 for the first event in the queue appears
queue. (third figure). You may see a different event
depending on what is in your event queue. Notice
that the first two lines show the event in short form
and the line 6 shows the block type and its
occurrence number in the instrument database.
Figure 4 .1.
4 Press the down arrow again to view See the first picture in the next figure. Notice that
page 2 for the first event the date and the time in ms (14:45:50.350 in this
example) is displayed. If the event is a diagnostic
alarm, page 2 will also display the acknowledged
state of the alarm (ACT / UAK / CLR).
4-2
Training Manual
page1
6 Press NXT to display the next event in Page 1 of the next event will be displayed next.
the queue.
7 Use the block type and event code, Pressing the DOWN arrow will display the time at
to locate the event description and which the event occurred and line 6 will display the
recommended action listed in nature of this event – in this example, the “INST IN
Section 7 of the Maintenance RUN” is the event and it means that the instrument
manual. was put in RUN mode. This is an information only
type event and line 6 displays “INFOONLY”
Figure 4 .2.
8 Press NXT to display the next event in Page 1 of the next event will be displayed next.
the queue.
9 Use the block type and event code, Pressing the DOWN arrow will display the time at
to locate the event description and which the event occurred and line 6 will display the
recommended action listed in nature of this event – in this example, the “INST IN
Section 7 of the Maintenance RUN” is the event and it means that the instrument
manual. was put in RUN mode. This is an information only
type event and line 6 displays “INFOONLY”
4-3
Training Manual
1. Informational events
2. Block state changes
3. Process alarms
4. Diagnostic alarms
5. Notification message events
6. System Event events
Figure 4 .3.
You can configure process alarms and diagnostic alarms associated with each block to be
entered in to the event list on an individual basis.
4-4
Training Manual
3 Use UP key three times to select the Lines 1 and 2 will display CURRENT LEVEL and Line 6
PASSWORD and then use ENT to will display CONFIG indicating that the controller is in
enter. See the next set of figures configuration mode.
4 Press ENT again to enter Lines 1 and 2 will display DEV STATE and INSTATE
Configuration mode. (Instrument state). Line 6 will display RUN indicating
that the controller is running a valid database.
Figure 4 .4.
5 Press the NXT key until COMMANDS is You will be in DEV STAT menu mow. See the
displayed on line 2. sequence of figures below:
You can issue commands to the controller from
this menu.
Figure 4 .5.
4-5
Training Manual
8 Press ENT (SCROLL key). The Events queue will be cleared and line 6 will
display NO again.
10 Pres the TAG key again. Your runtime display will be displayed.
4-6
Training Manual
2 Make sure the switches on the This ensures that the database stored in the
memory module are set to READ memory module is downloaded to the instrument
ONLY and NORMAL during a power-up sequence.
3 Loosen the retaining screw and slide CAUTION ! Ensure that the main circuit board is
the instrument from the housing supported at all times.
4 Install the memory module With the catalogue number of the memory module
facing upwards, install the memory module onto
the connector of the main circuit board
5 Place the instrument back into the You should see ******** appear for a short while,
housing and tighten the retaining then a flashing loop display with the tag SD -100
screw and the alarm light.
Figure 4 .6.
6 Acknowledge alarms if any and This database is configured with most of the
press the TAG key to go to the SD- diagnostic alarms suppressed (turned off).
100 display.
The SD-100 display is a typical PID display with
the tag name, process value and output shown on
lines 1, 2 and 6 respectively.
4-7
Training Manual
7 Press the SCROLL key ONCE. The PID setpoint will be shown on line 6 and the
text “SP” on line 5.
8. Press the SCROLL key twice more The runtime PID display will disappear and FAILURE
and wait for a few seconds. will be displayed on line 1 with an audible
continuous alarm.
At this point, you cannot operate the PID loop or
use the controller.
This is an indication that the controller is in
SHUTDOWN mode.
4-8
Training Manual
2 View the diagnostic alarms by The diagnostic alarms that come up after an
pressing the ALARM button. instrument shut down are:
Figure 4 .7.
Figure 4 .8.
4-9
Training Manual
3 Press the TAG button after viewing The instrument will display the DEVICE display.
and acknowledging the alarms. Line 6 will show DEV STAT. See the middle picture
in the next figure.
4 Press the DOWN arrow to enter the The first page in this menu shows the Instrument’s
DEV STAT menu. state as shown in the last picture in the next figure.
The device state is DEFAULT after a SHUTDOWN.
Figure 4 .9.
5 Press the NXT to view the Line 2 will display SHUTDOWN and line 6 will display
SHUTDOWN page. YES. This indicates that a Shutdown condition
exists. See the above figure.
6 Press the DOWN arrow to view The Shutdown information is provided in the next 4
details of the shut down. pages (displays).
Record this shutdown information on Page 1 of the SHUTDOWN info as shown in the
the form at the end of this chapter. next figure.
Figure 4 .10.
4 - 10
Training Manual
7 Press the NXT key to view Pages1, 2, Shutdown page 2 displays the time and date of the
3 and 4 and record the information shutdown.
Figure 4 .11.
8 Press the UP/DOWN arrow to show This will acknowledge the Shutdown and line 6 will
YES on line 6 and then press the key display NO again. Line 3 will now change to display
next to ENT on the display RUN. This means that the instrument state is back to
RUN.
The database we used for forcing the instrument to shutdown has a configuration error
in the display script for the PID. If you press the SCROLL key to switch between
setpoint and output for line 6 will force the instrument to shutdown again.
This type of error can be prevented by ensuring that display script case statements handle
all possibly cases. For example, if your script counts the number of times that the scroll
button is pressed, it must reset the count before it exceeds the number of cases defined in
the statement. If only two cases are defined and the count reaches three, it will cause a
shutdown fault when it attempts to evaluate the statement.
In certain cases where shutdown occurred due to serious hardware problems, you will still
be able to acknowledge the shutdown, but you may not be able to put the instrument to
RUN mode. Please visit http://www.micromodautomation.com for instructions to send the
instrument for repair.
4 - 11
Training Manual
Notes:
4 - 12
5 ViZapp Setup Lab
5.1 Objectives
In this lab we will setup the ViZapp Software on your computer. After completing this lab
you should know how to install and setup ViZapp on your computer.
5-1
Training Manual
5.2 Instructions:
The following procedure explains how to install ViZapp on your computer.
ViZapp Setup will install a Microsoft Software component called MDAC (Microsoft Data
Access Components) if the minimum required version was not present in the system
already. This program is required by the ViZapp Reports. MDAC is also installed by other
Microsoft and third party programs.
ViZapp also requires another software package called OPC Core Components.
The above programs are installed by ViZapp in the background during ViZapp Setup and
do not require any user inputs.
Close all applications that are running in your computer currently before starting the
ViZapp setup. If a previous installation of ViZapp exists, uninstall it and reboot
before continuing. This can be done through the Control Panel’s Add/Remove
Programs.
Uninstalling ViZapp will not delete user files or the Gallery
If the Master Setup shell does not launch automatically, select Run from the Start Menu
of Windows. The Run dialog box will appear as shown below:
Figure 5 .1.
Run dialog box
5-2
Training Manual
Figure 5 .2.
Run dialog box
2. Click on ViZapp Setup, acknowledge the license note and the introductory screen will
display briefly while installation is initiating.
Figure 5 .3.
ViZapp Setup
Figure 5 .4.
ViZapp Setup
5-3
Training Manual
3. The setup will display the Welcome dialog box as shown below. Click on Next to
continue.
Figure 5 .5.
ViZapp Setup -
Welcome
4. The MICROMOD Software License Agreement will appear next and will display the
legal information about using the ViZapp Software. Click on Yes if you accept the
agreement. Clicking on No will terminate the Setup. Refer to the next figure.
An Information dialog box will be displayed next as shown in the next figure:
5-4
Training Manual
Figure 5 .7.
ViZapp Setup –
Information
5. Customer Information: The User Information dialog box will be displayed next as
shown below. Type your name and company name. Note that ViZapp versions prior to
3.01 also required a serial number to be entered. This serial number can be found on the
CD case or the ViZapp package you received. Click on Next to continue.
Figure 5 .8.
ViZapp Setup –
Destination
Location
6. The Choose Destination Location dialog box will be displayed next as shown in the next
figure. We will choose the default location for the setup. Click on Next to continue.
If you want to install ViZapp onto a different folder, click on the Browse button to
open the Choose Folder dialog box and then browse to the desired folder or create a
new folder by typing its name in the Path field.
5-5
Training Manual
• Click on OK to continue.
Figure 5 .9.
ViZapp Setup –
Choose Destination
7. The Data Root Directory dialog box will be displayed next as shown in the next figure.
We will choose the default location for the data files. Click on Next to continue.
If you want to specify a different default folder for your data files (configuration files
such as workspace, project, database files etc.), click on the Browse button to open the
Choose Folder dialog box and then browse to the desired folder. You can always
choose a new folder after installation from within the application. Click on OK to
continue.
Figure 5 .10.
ViZapp Setup –
Choose Destination
5-6
Training Manual
8. Select Components for installation: The ViZapp Software package consists of the main
software and a few options. You can choose the options at the time of setup. The Select
Components choices will vary depending on which version of ViZapp is being installed.
By default, all available options are selected. Note that selecting On-line Documentation
installs all documentation onto the hard drive. Otherwise, it will be necessary to have the
CD in the drive to access the documents.
These options will be displayed as check boxes on the dialog box. See the next figure for
example.
This dialog box also shows the space required on the hard disk to install the selected
options and the total free space on the disk. Accept the defaults and then click on Next to
continue.
Figure 5 .11.
ViZapp Setup –
Select Components
9. Choose the Program Folder: The ViZapp setup will also create a program folder and
will create program shortcuts inside that folder. You can use these shortcuts to start the
programs. The default program folder that will be automatically created will be:
MicroMod Automation\ViZapp.
If you want to create a new program folder you can type its name in the Program
Folders field on this dialog box. If you want to use one of the existing program folders,
you can choose it from the Existing Folders list box on this dialog box by clicking on
it.
5-7
Training Manual
Figure 5 .12.
ViZapp Setup –
Select Components
10. Setup will display a message box as shown in the next figure. The OPC Core Components
will be installed in your computer.
5-8
Training Manual
Figure 5 .14.
ViZapp Setup –
Program Folder
• Click on OK to continue.
Figure 5 .15.
ViZapp Setup –
Program Folder
• The OPC Core Components setup will also install .NET components for OPC if
you have the .NET framework from Microsoft already present in the system,
though the .NET framework is not required for ViZapp. Click on OK to continue.
11. If you have a pre-existing Gallery file in the installation folder, the dialog box shown
below will be displayed next. This enables you to over-write an existing gallery file or
rename it before installing the new gallery file. The file may be overwritten if you did not
make any changes to it that you wish to keep.
Figure 5 .16.
ViZapp Setup -
Component Gallery
5-9
Training Manual
• If you chose to rename the existing file, the following Rename Gallery dialog will
be displayed. You can type a name for the old gallery file. Click on Next. See next
figure:
Gallery File: The gallery is a library of configuration compounds (collection of
function blocks configured for a specific functionality), smart symbols and static
symbols that can be used in your applications. Frequently used compounds may be
added to the default gallery or a separate user gallery.
Figure 5 .17.
ViZapp Setup -
Component Gallery
• A message box confirming the renaming of the file will appear next. Click on OK
on this message box to continue.
Figure 5 .18.
ViZapp Setup
12. The device drivers for the software protection keys will be installed during the setup.
ViZapp may have been supplied with either a HardLock key or a Rainbow key. The
drivers are required for the software protection key to work. The key may be either a
parallel port or USB port style. First, the HardLock driver will be installed. See the next
figure.
The set of next 4 figures do not appear in Windows 95, 98 or ME. They appear only in
Windows NT, 2000 or XP.
• An Information window as shown in the next figure will appear in Windows NT,
2000 and XP. Click on OK to continue.
5 - 10
Training Manual
Figure 5 .19.
HardLock Device
Driver
Figure 5 .20.
HardLock Device
Driver
• If you have a USB style key on you computer, remove it before continuing. Click
on Next on the Welcome dialog in the HardLock Device Driver Installation. If you
do not have a HardLock key, you may click Cancel on this dialog to skip to the
Rainbow driver installation.
Figure 5 .21.
HardLock Device
Driver Setup
• The HardLock device driver installation will start and the files will be installed. A
Dialog box showing the progress of the installation will be displayed next as
shown in the next figure.
5 - 11
Training Manual
Figure 5 .22.
HardLock Device
Driver Setup
• The Finished dialog box will be displayed after the device driver is installed. See
the figure below:
Figure 5 .23.
HardLock Device
Driver Setup
13. The Rainbow device drivers will be installed next. See the next figure:
Figure 5 .24.
Rainbow Device
Driver
Remove any USB keys that are connected to the computer before continuing.
• Click on OK to continue.
5 - 12
Training Manual
Figure 5 .25.
Rainbow Device
Driver
• The following will be displayed if you are installing the driver for the first time on
a Windows XP system with a firewall.
Figure 5 .26.
Rainbow Device
Driver
• When the Sentinel driver installation is complete, ViZapp setup will continue.
5 - 13
Training Manual
Figure 5 .27.
ViZapp Setup
14. The ViZapp setup will start now and will display a progress bar as shown above. After the
ViZapp Setup copied all the required files, the following Information box will be
displayed.
15. ViZapp Setup will register all the software components with the Windows registry and a
message box as shown below will be displayed.
5 - 14
Training Manual
Figure 5 .29.
ViZapp Setup
16. After the files are registered, the setup will display a message ass shown in the next figure.
Refer to the License admin section of this manual to add licenses to the software.
Figure 5 .30.
ViZapp Setup
Figure 5 .31.
ViZapp Setup
17. ViZapp setup will now be complete and a dialog box as shown in the next figure will be
displayed.
Figure 5 .32.
ViZapp Setup –
Setup Complete
5 - 15
Training Manual
5 - 16
6 PID Loop Lab
6.1 Foreword
Many processes involve flow control loops, whether they are in the food, pharmaceutical,
chemical, pulp & paper, mining or virtually any of the industries served by MODCELL
and MOD 30ML. This lab is designed to help you learn the basic features of the ViZapp
configurator, as well as how to easily learn/demonstrate configuration of a PID loop.
6.2 Objectives
In this lab we will design a simple flow loop with a 4-20mA signal from a dP transmitter,
a square root extractor, a PID control loop and a modulating control valve. The P&ID for
this loop looks like this:
Figure 6 .1. FY FC
Sample Flow PID
Loop
FT
FCV
FE
We will use the built-in analog input 2 of MOD 30ML for connecting the process variable
(FT). We will use the built-in analog output 2 for sending the output of the PID. We will
also build a display for this PID loop.
6-1
Training Manual
6.3 Instructions
Follow these instructions step-by-step to configure a simple PID loop:
Figure 6 .2.
ViZapp
Configurator
• Note that the configurator screen has two frames (left and right).
2. We will create a new Workspace and a new project in this step. Click on the File
menu on the menu bar at the top. Select New from the drop-down menu as shown in the
next figure:
Figure 6 .3.
File-New
6-2
Training Manual
• This will open the New dialog box as shown in the next figure. There are 2 tabs
(sections) in this dialog box and it displays the Project tab as default.
Figure 6 .4.
New Project
• Click on the little button next to the Location field to open the Browser for
Folder dialog as shown in the next figure:
• Select the C: drive from this folder and select on it by double-clicking on it. See
next figure:
Figure 6 .5.
New Project
6-3
Training Manual
Figure 6 .6.
New Project
• Type the name CLASS for your project in the name field. Notice that the name of
the location for this project changes to C:\Class. It creates a folder under the C:
drive (or any other drive you choose) automatically.
All project files and the instrument and display documents will be saved in this folder.
This makes project portability easier.
• Click on the option Create a new Workspace. This will create a new workspace
for us. Click on OK.
• The configurator will redisplay with a new workspace and a project as shown
below:
6-4
Training Manual
Figure 6 .7.
Class Workspace
• The left frame shows the project tree. The Workspace is at the root of this tree and
contains the Project, and other components such as Event Log and Components.
• The newly created workspace is given the same name as that of the project. The
project sub-tree or branch contains the components Security and Tags.
3. With what we have above, we have only created an environment to configure instrument
database and display files. Next we will create an instrument database. We will hereafter
call it the instrument document.
• Click on the New Document button on the tool bar or Select File-New form the
menu bar to display the New dialog box again as shown below:
6-5
Training Manual
Figure 6 .8.
New Document
• The New dialog box shows the Document tab now. Select the type MOD
Function Block diagram by clicking on it and then type the name PIDLAB for
the document in the Name field.
• This document will be created in the project folder \class automatically and will be
added to your Class project by default. See figure above.
When you create a new project, a file with the project name and file extension .APRJ
will be created. This file is called project file in the ViZapp installation directory.
The instrument document/ configuration files (MOD Function block diagram files) will
have extension .AFBD and will be saved in the project folder.
The workspace we created will be saved as a file with extension .AWSP (Class.awsp) and
a file with same name and .FEQP extension (Class.feqp) in the root folder where the
project folder is located.
IF you move your workspace and project to a different location/ drive, move the
project folder and the two files for the workspace (.AWSP and .FEQP), maintaining
their relative location.
• Click on OK. This will display the Choose Instrument Version dialog box as
shown in the next figure: This dialog box will display the different instrument ID
module versions (MODCELL and MOD 30ML).
6-6
Training Manual
Figure 6 .9.
Instrument Versions
• Select MOD 30ML 2 from this list as our instrument version by clicking on it and
then click on the Close button.
• The Configurator will redisplay as shown below. The instrument database will be
opened on the right frame and the default blocks (IF, SE, ST and DIF) for the
MOD 30ML database will be loaded.
• Notice that the newly created document PIDLAB is shown in the project tree
attached to the Project Class.
Figure 6 .10.
Default instrument
database
• The algorithm blocks belonging to the instrument version selected will be shown
as a menu on the left frame.
6-7
Training Manual
There could be as many as five scan groups in an instrument database. The control
loops (database blocks connected together) are grouped into Loop Compounds. The
Loop Compounds can be assigned to any of these scan groups. All the blocks and
compounds in a particular scan group will be executed at the same scan rate configured
for the group.
This way you can have many loops in the database and they can be executed at different
rates depending on their priority and speed of the process they are controlling.
• Notice that all the four blocks on the screen are selected. Deselect them by clicking
on a blank space and then double-click on the IF (Interface) block. The Interface
block will open as shown in the next figure: The block is displayed in a visual
notebook format, with tabbed “pages” containing the parameters for configuration.
The Execution tab (page) of this block will be displayed by default.
Figure 6 .11.
IF Block
• Change the Group 1 scan interval from 250 ms to 200 ms by typing in the ms field
of Scan Intervals:Group 1.
Notice that the Properties menu of the block has the following tabs:
• Execution
• Startup
• Diagnostics
• Incoming
6-8
Training Manual
• Outgoing
• Connect map
• Shape
Configuration parameters related by common nature are grouped into these tabs. This
helps to display of information in a logical manner. Most fields under these tabs contain
default values that need not be changed.
5. Add a loop compound. We will configure our control loop inside this loop compound.
• Select the Loop Cpd (Loop compound) block from the Algorithms window add it
to the document. Do this by first locating the block in the menu by selecting the
All submenu at the bottom and then by dragging the scroll bar on the right
up/down. See the next figure:
Figure 6 .12.
Algorithms menu
• Drag the Loop Cpd block (Loop Compound) from the Algorithms menu on the left
frame to the right frame. Click on the Loop Cpd block with your left mouse button
and then drag it to the instrument document. Click on the mouse button to place
the Loop compound block with the other existing blocks (IF, SE, DIF and ST) on
the right frame.
6. Configure a name and description for the Loop Compound: Click once on this block
with your right mouse button. A menu as shown in the next figure will appear.
6-9
Training Manual
Figure 6 .13.
Loop Compound
Properties
• Select Properties from the menu. The Algorithm Properties of the Loop Cpd block
will be displayed next as shown in the next figure.
• Type Control in the Name field.
• Type a description "This compound is for the Flow Control Loop"
• Click on OK to close the Properties.
Figure 6 .14.
Loop Compound
Properties
6 - 10
Training Manual
• Right-Click on the Control compound (Loop compound you just named) again and
select Open compound at the bottom of this menu.
• The loop compound will open as shown below and will have a Loop block (LP) by
default.
Figure 6 .15.
Loop Block
A loop compound is a compound or group that contains a loop block. You configure
other blocks and compounds inside the loop compound. The compound can be added
to one of the five scan groups defined in the Interface block. All the blocks inside the
compound will be executed at that scan rate.
• The compound will also have a Compound Signals menu that can be used to
make pre-defined connections in and out of this block. (We will not use this for
now. You can close it by clicking on the close button on its right hand side top –
the X button)
8. Open the Loop block (LP-1) by double-clicking on it. The block will open as shown in
the next figure. We will not change anything in this block. Just notice that scan group this
compound belongs to defaults to Scan Group 1. (200 ms– refer to step 4 - Interface block).
6 - 11
Training Manual
Figure 6 .16.
Loop Block
• Let us start doing this by adding the necessary algorithm blocks to the Loop
Compound on the workspace on the right frame. Add the following blocks to the
database:
• AIN – Built-in Analog Input
• VCI – Voltage or Current Input function block
• PID – PID algorithm block
• AOUT – Built-in Analog Output block
You can either select the specific category at the bottom of the Algorithms menu first and
then the blocks or you can select the category All to pick any block.
After you placed the above blocks in the database, the right frame on your configurator
screen should look something like the next figure.
6 - 12
Training Manual
Figure 6 .17.
Algorithm blocks in
the Loop
Compound
10. Resize and move these blocks to fit them on the database workspace.
• Select a block by clicking on it. The selected block will have handles around it.
See figure below:
• Move the block with the left mouse button pressed on it and by moving the mouse.
• Resize the block by dragging one of the handles (corner or side)
Figure 6 .18.
Move, Resize and
Configure
6 - 13
Training Manual
If you are using the MOD 30ML Demo box, leave the Input type as Volts in the above
configuration. Specify the Input signal range as 1 to 5 Volts.
• Configure the VCI block: Double-click on the VCI block. We will configure this
to specify the input function for the analog input configured above. The VCI block
Properties will open as shown in the next figure:
6 - 14
Training Manual
Figure 6 .20.
VCI Properties
• Type the name and description for this block as shown above. Move the cursor to
the Linearization Type field and click on the down arrow. Select Modifies Square
Root as the type from the drop-down menu. This will compensate for errors at very
low flow measurements.
• Change the Range to 0 to 200 and Quality limits also to 0 to 200. The measured
signal (4-20mA or 1-5V) will be interpreted as 0 to 200 flow units.
• We will not change anything else in this menu. Click on the OK button to
complete the configuration of this block.
Figure 6 .21.
File Menu
6 - 15
Training Manual
• Select File – Save All from the menu bar. This will save the document, the project
file and the workspace file.
Note that Save only saves the currently opened document. Unless you have made
changes in other documents that you do not wish to save, you may select Save-All
instead.
13. Continue configuring the other blocks. Double-click on the PID block. Give the block the
tag name FIC-100.
• Change the Process Input range to 0 and 200. Type the description as shown in the
next figure. Note that the default Control Action is Reverse.
Figure 6 .22.
PID Block
• Click on the Setpoint tab at the top of this block to configure the setpoint for this
control loop. The Setpoint page will display as shown in the next figure:
6 - 16
Training Manual
Figure 6 .23.
PID Properties
14. Configure AOUT block to define the properties of the analog output:
6 - 17
Training Manual
Figure 6 .24.
Aout Properties
6 - 18
Training Manual
• Move to the workspace on the right and click on the AIN block’s (FT-100 –
source block) output connection point as shown in the next figure. Notice that
moving the cursor over the output of a block, shows a fly-by box. This box shows
the name of the output (for example, in this case MODOUT).
Figure 6 .26.
Connecting blocks
• Move the cursor to the VCI block’s (destination block FY-100) input now.
Moving the cursor will draw a line.
Figure 6 .27.
Connecting blocks
• You will get a fly-by box that will say MODIN when you move over the input.
6 - 19
Training Manual
• Click on the input of the VCI block. See the figure above.
Figure 6 .28.
Connecting blocks
• The connection will now be complete. The connection line will have the source
name and destination name displayed right on it as shown in the above figure.
The input connection points are on the left side of the blocks and the output connection
points are on the right hand side.
There might be more than one input or output for each block. All the inputs or outputs
need not be shown as connections attached to the block. To see all the inputs or outputs of
a block, you need to click right on the block in the connection mode.
As an example, the figure below shows the possible inputs of the PID block (destinations
for inputs into this block).
Figure 6 .29.
Choose parameter
for connecting
16. Connect the corrected flow as the process variable input the PID block.
• Let us take Right angle connector this time. The right angle connector will connect
the blocks by horizontal and vertical lines instead of making a point to point
straight connection.
• Select the right angle connector from the Algorithms menu as shown below:
6 - 20
Training Manual
Figure 6 .30.
Right Angle
connection
• Click on the output point of the FY-100 block. This point is the result of the FY-
100 input function block. The fly-by box will say R when you click on the output.
Drag the line to the input point of the PID block and clock on it (PVI) to complete
the connection.
17. Connect the output of the PID (FIC-100) to the INPUT of the AOUT (analog output)
block with the right angle connector as shown below.
Figure 6 .31.
Right Angle
connection
If you made a mistake while connecting, or if you do not know where to connect, you
can always cancel it or get out of the connection mode by clicking on the right mouse
button to show a menu as shown below:
• Select Cancel from this menu to cancel the connection.
6 - 21
Training Manual
Figure 6 .32.
Cancel Connection
• When the Component Gallery dialog box appears, select the Compounds tab. A
library of pre-configured Compounds, or groups of algorithm blocks, appears.
6 - 22
Training Manual
Figure 6 .34.
Compound Library
• Move the cursor to the PID Display compound and either double-click, or select it
and then select the Export button. The Component Gallery dialog box closes and a
set of blocks is placed in your workspace. The blocks are highlighted with small
green boxes.
Figure 6 .35.
Loaded compound
6 - 23
Training Manual
• Click elsewhere on the screen to deselect them. The loaded blocks include a
Display (DISP) block, a Tuning List block (TL) and two text boxes. The text boxes
contain information about the compound. You can read the text and move them to
a different area of the screen or delete them from the screen.
• Delete the TL (Tuning List) block from the screen. Delete also the connection from
the TL block to the display block.
Figure 6 .36.
Workspace with
new Display block
• Move the Display block close to the PID block as shown above.
Figure 6 .37.
Workspace with
new Display block
connected
6 - 24
Training Manual
• Using the Multi-Segment connector, click on the PID block and select PVI from
the resulting dialog box. Double-click on PVI or select and click on the OK button.
Figure 6 .38.
Selecting PID block
parameters to
connect
• Drag the cursor over the Display block and click. Select process from the resulting
dialog box. See the next figure:
6 - 25
Training Manual
Figure 6 .39.
Choose parameter
for connecting
• The connection between the Process variable in the PID block and the Dsiplay
Block input called “process” is now complete.
• Continue connecting from the PID block to the Display block until the following
inputs are connected:
• SP to setpoint
• OP to output
• OPMS to mode
• SPMS to spmode
6 - 26
Training Manual
Figure 6 .40.
Connections from
PID block
parameters to
Display block inputs
20. The display compound from the Component Gallery is set up for 0 to 100. This must be
changed to match the PID block that we configured for 0 to 200. We must also designate
a display tag.
• Double-click on the Display block. In the resulting dialog box, type FIC-100 in
the Display Tag field (overwrite the PID-100).
Figure 6 .41.
Entering the
Display Tag in the
Display Block
6 - 27
Training Manual
This tag must be unique to this display. It can also be used as the tag name that appears
on the front face. The default DISPTAG in Line 1 of the Intial Values causes the value
or name typed in the Display Tag field to appear on Line 1 of the display on the front
panel. For more detailed information on display building, refer to IB-1800R-SCR,
Display Guide.
• Select the Formats tab in the Display Block
Figure 6 .42.
Display Block
Formats tab
• Double-click on the name processL and change the High Limit in the resulting dialog
box to 200.
6 - 28
Training Manual
Figure 6 .43.
Changing
engineering unit
range for process
line display
• Right-click (click on the right button of the mouse) on the empty workspace to get
a menu as shown in the next figure:
6 - 29
Training Manual
Figure 6 .44.
Closing Compound
22. Add the Display Tag to the Display Interface Block: The next step is to add the display tag
of the display block we configured in the previous steps to the display list in the display
interface block. During runtime, you can scroll through the displays in this list by pressing
the Tag button on the instrument.
• Start by opening the DIF (Display Interface) block as shown in the figure below:
Figure 6 .45.
Closing Compound
6 - 30
Training Manual
• A text edit box will appear in the area below and you will see a text edit cursor
blinking.
• Type the name of your display tag (FIC-100). Refer to the next figure.
• Click on the OK button when you are done.
a If you had more than one display blocks in your configuration, you will need to add
their display tags in the DIF block as explained in the above step. The order in which
the display tags appear in this list is the order in which the displays will scroll when
you press the Tag button on the instrument. The display block gets executed by the
instrument when it is loaded on the face of the instrument. If you did not add the
display tag of a display block to this list, that display will not appear on the instrument
when you press the Tag button.
6 - 31
Training Manual
Figure 6 .47.
Closing Compound
23. Add a Configured list block and add signals to it: Next we will need to add parameters to
pass on the Extended Modbus that can be served by the XModbus OPC Server or a
XModbus Device Driver to Client Software packages like HMI/HSI clients. This is
needed only if you connect your controller to a host computer. If your controller will be
stand-alone, you do not need to send parameters over Modbus/ XModbus. In this course,
we will be using XModbus to pass parameters such as PV, SP, OP etc.
• Pick a CL block from the Algorithms window and add it to the document
(strategy) workspace.
• Double-click on it to configure: The CL block Properties will open as shown
below.
• Click on the Inputs tab to add inputs
6 - 32
Training Manual
Figure 6 .48.
CL block
• The Browse dialog will be displayed as shown above and will list all the blocks
and compounds that are present in your document as a tree structure. These will be
shown with box icons next to them meaning that there groups and there are further
items inside each group.
• You must be seeing the Loop Compound Control also listed in this dialog.
6 - 33
Training Manual
• Double-click on this item to open it. The tree will expand and will display the
blocks inside the Control group.
Figure 6 .50.
Browse
• Click on the item FIC-100. This will display the attributes of the FIC-100 (PID
block) in the box on the right.
• Click on OP (PID output) and then on the Add button at the bottom to add the PID
output to the CL block. DO not hit the OK button !
• Select SP, PVI, SPMS and OPMS from this list and add them in the same way.
a You can select multiple attributes by pressing the Ctrl key on the keyboard and by
clicking on them with the left mouse button. Hit the Add button after multiple selection
to all the selected attributes.
6 - 34
Training Manual
Figure 6 .51.
CL block
• Click on OK on the Browse dialog. This will redisplay the CL block Properties as
shown above. The Inputs Tab will now display the attributes you just added.
a The attributes will be displayed with full source path name of the connections. An alias
can be entered by selecting an item and typing in any alias name. This name will then
be displayed instead of the block tag and attribute name.
24. Assign Aliases to the tags added to the CL block: Select Control.FIC-100.OP by clicking
on it and then clicking on the Modify button.
Figure 6 .52.
Alias
• Repeat the above procedure to assign aliases for the other attributes as shown
below:
6 - 35
Training Manual
Figure 6 .53.
CL block aliases
The next step is to setup communications. The MOD 30ML can communicate using
Modbus or ICN. If you are using Modbus, proceed with the next section. If you are using
ICN, skip the next section and proceed to the following section, Setting up
communications for ICN.
6 - 36
Training Manual
• Make a connection from the CL block by selecting the right angle connection from
the Algorithms window and select CL block’s LISTOUT as the source. Terminate
the connection at the MSC block by connecting it to FGLISTIN. Refer to the
figure below:
6 - 37
Training Manual
Figure 6 .55.
CL to MSC
connection
Skip the next section and proceed to the following section, Compiling the database.
6 - 38
Training Manual
25. We need to setup communications for communicating with the MOD 30ML instrument so
that we can download the database to the instrument. We will use the built-in ICN port of
the instrument to download to the instrument via ICN.
• Make a connection from the CL block by selecting the right angle connection from
the Algorithms window and select CL block’s LISTOUT as the source. Terminate
6 - 39
Training Manual
the connection at the ICN block by connecting it to FGLISTIN. Refer to the figure
below:
Figure 6 .57.
CL to MSC
connection
6 - 40
Training Manual
Figure 6 .58.
Instrument Compile
• The Compile Setup dialog box as shown below will appear. Click on OK (Do not
reassign block occurrence numbers).
Figure 6 .59.
Compile Setup
• The Interface File Options dialog box will be displayed as shown next. We want to
create a .MIF file (Modcell Interface File) for this control strategy. This file will be
used by the OPC Server to create tags.
• Look at the Produce MIF section of this dialog box. Note that the MSC/ICN
block’s Type and its Tag Name are shown in this section.
6 - 41
Training Manual
Figure 6 .60.
Interface File
Options for Modbus
• Check the box next to it (on the right) and type a name for the MIF file.
• Type PIDLAB (if you are using Modbus) or ICNLAB (if you are using ICN) as
shown in the above figure or the figure below:
6 - 42
Training Manual
Figure 6 .61.
Interface File
Options for ICN
• Click on OK. If the database has errors, it will not be compiled successfully. A list
of errors will be displayed on the screen in a sub-window along with other
information such as the number of errors, warnings and info messages as shown
below:
Figure 6 .62.
Information Window
• You can double-click on an error to open the block that has a configuration
problem. If the database has no errors, there is a message saying that the Compile
was completed without error.
• Also look for messages on successful MIF file creation, database size and current
consumption of the instrument.
6 - 43
Training Manual
• You can close this info sub-window by right-clicking on the window and then
clicking on the resulting Hide Window button or by selecting View-Information
from the menu bar at the top.
6 - 44
7 Creating a Tuning List
7.1 Foreword
During commissioning and normal operation it is desirable to change the tuning
parameters from the front panel of the instrument. In addition, MOD 30ML allows the
user to create ‘tuning displays’ that contain many other types of information including
recipe parameters and lookup values. This lab leads you through creating a basic Tune
List for a PID block, which is accessed by pressing and holding the Scroll key on the front
panel. Although the Component Gallery contains a complete PID loop with algorithm
blocks, Display block, and Tune List, it is useful to use the PID tuning list as an example.
7.2 Objective
In this lab we will add a Tune List block to the PID strategy created in the PID Loop Lab,
and configure it to show basic tuning and commissioning parameters. You will need the
Mod Function Block Diagram that you created in the PID Loop Lab.
7.3 Instructions
Follow these instructions step-by-step to add and configure the Tune List block:
• Open the PIDLoop instrument document in the ViZapp workspace and then open
the loop compound that contains the PID and Display blocks.
• Select the TL (Tune List) block from the Algorithms window and add it to the
document next to the display block.
Figure 7 .1.
Algorithms menu
7-1
Training Manual
7-2
Training Manual
Figure 7 .3.
Browse
• The Browse dialog will be displayed as shown above and will list all the blocks
and compounds that are present in your document as a tree structure. These will be
shown with box icons next to them meaning that there groups and there are further
items inside each group.
• You should see the FIC-100 block (the PID block) on this tree.
• Click on FIC-100 to open it. The tree will expand and will display the PID block
parameters.
Figure 7 .4.
Browse
• Click on BGAIN (base gain) and then on the Add button at the bottom to add the
Gain to the Tune List. DO not hit the OK button !
7-3
Training Manual
• Select BRESET, BPREACT, ACTION, and CATYPE from this list and add them
in the same way. In addition to the three tuning terms, Controller Action
(ACTION) and Control Algorithm Type (CATYPE) are useful attributes to see
during commissioning.
a You can select multiple attributes by pressing the Ctrl key on the keyboard and by
clicking on them with the left mouse button. Hit the Add button after multiple selection
to all the selected attributes.
Figure 7 .5.
TL block
• Click on OK on the Browse dialog. This will redisplay the TL block Properties as
shown above. The Inputs Tab will now display the attributes you just added.
a The attributes will be displayed with full source path name of the connections. An alias
can be entered by selecting an item and typing in any alias name. This name will then
be displayed instead of the block tag and attribute name.
• Double-click on Input 1 (1 in the first column). The Specify Input Data dialog box
appears as shown in the next figure.
• Type gain in the Display Format Name field, and GAIN in the Line 2 Text field.
7-4
Training Manual
Figure 7 .6.
Tune List Input
Data
7-5
Training Manual
Figure 7 .7.
Tune List Input
Data
7-6
Training Manual
Figure 7 .8.
TL block formats
• Click on the Add button on this page/tab. The Specify Format Data dialog box
appears.
• Fill in the format fields as shown in the diagram below, to add the following
formats (where there is a blank do not make an entry):
Name Format Low High Entry Method Eng. Display Entry
Type Limit Limit Units State Table State
Table
PIDType State none PidTypT
Action State Enter Required PidActT PidActT
Gain Float2 .01 125 Enter Required
Reset Float2 0 25 Enter Required RPM
Preact Float2 0 32 Enter Required MIN
• The Specify Format Data dialog box is shown in the next figure:
7-7
Training Manual
Figure 7 .9.
Tune List Format
Data for PIDtype
format
The Name(s) should match the format names that were assigned in the Input tab. The
Format Type must match the data type of the input (e.g. gain is floating point with x
decimal places, PID type is State). This information may be found in the Help menus
associated with this dialog box). Entry method designates whether an operator entry is
allowed, and if so, whether the data is accepted immediately or a confirmation is
required. High and low limits may be entered if appropriate, along with Engineering
units. To restrict the conditions under which a parameter may be changed, enter an
expression in the Allow edit when this expression is true field. Display and Entry state
tables control text associated with the possible entries for the tuning parameter. This
text is contained in the State Table Block. For additional information on state tables,
refer to IB-1800R-SCR, Display Guide.
• The TL block should look like the next figure after you added the required formats.
• You can also change the name of the TL block to TuneList on the General tab of
this block’s Properties.
7-8
Training Manual
Figure 7 .10.
TL Block
• Close the dialog box and the Tune List block with the OK buttons.
• Move to the workspace on the right and click on the TL block’s output connection
point as shown in the next figure. Notice that moving the cursor over the output of
a block, shows a fly-by box. This box shows the name of the output (for example,
in this case LISTOUT).
7-9
Training Manual
Figure 7 .12.
Connecting blocks
• Move the cursor to the Display block’s input now. Moving the cursor will draw a
line.
Figure 7 .13.
Connecting blocks
• You will get a fly-by box that will say LISTIN when you move over the input.
• Click on the input of the Display block. See the figure above.
Figure 7 .14.
Connecting blocks
• The connection will now be complete. The connection line will have the source
name and destination name displayed right on it as shown in the above figure.
Once the configuration has been compiled and downloaded to the controller, the Tune
List attributes may be accessed by pressing and holding down the Scroll key.
7 - 10
8 Extended MODBUS OPC Server
8.1 Foreword
The Extended MODBUS OPC Server is an OPC compliant Server able to communicate
with Extended MODBUS devices (MODCELL / MOD 30ML) and serve data to OPC
clients. This MODBUS OPC server was implemented using advanced programming
concepts of OPC specifications.
This OPC Server also supports generic MODBUS protocol and can be used to connect
ABB Commander series instruments and other instruments that support MODBUS
RTU protocol.
The Extended MODBUS Server is installed in the same manner as the ViZapp Software.
Refer to the ViZapp installation lab for details.
8.2 Objectives
In this lab, we will install the Extended MODBUS OPC Server, configure a server
database and add a device to it. We will use this database to download the PIDLAB
Strategy from the previous lab to the MOD 30ML instrument.
We will also populate the OPC database with tags using the MODBUS Interface File
(.MIF) created in the previous lab and monitor the data by reading them from the
instrument using the built-in OPC Client of the Extended MODBUS OPC Server.
Devices: These are hardware devices (MODCELL / MOD 30ML) connected to the OPC
Server.
8-1
Training Manual
Groups: Tags/Signals can be placed together into groups. Groups, if used, are shown at
the top level under a device. In the Extended MODBUS OPC database, the
grouping will be based on the grouping in the CL block in the instrument
database database.
Each block in the database will be one group and will have the selected attributes of
that block. For example, if you have a block named FIC-100, the group will be called
FIC-100 and the signals like PVI, SP, OP etc, will be tags belonging to that group.
Blocks inside a compound will be grouped into a bigger group with name as the
compound name.
Grouping is only for the user’s convenience. If aliases are configured in the CL block for
tags, then the tags will be attached to the devices directly (at the root level).
Tags: Tags define the properties of signals such as address of the signal, group and
device it belongs to, data type and scaling. Examples of tags are PVI, SP, OP
etc, of a PID block.
Having a .MIF file is very handy. Connecting the MIF file to a device in the OPC tag
database will create the groups and signals automatically. This will save a tremendous
amount of time compared to creating them manually.
In the case of generic MODBUS devices such as ABB Commander series instruments,
you have to create the groups and tags manually and should define their properties.
OPC Client is useful for testing the communication between the devices and the OPC
Server. It can also be used for testing other 3rd party OPC applications connected to the
server.
8.3 Instructions
8.3.1 Part 1
1. Install the Extended MODBUS OPC Server. Refer to the ViZapp setup lab for help.
2. Launch the Extended MODBUS OPC Server: From the Windows Start menu, select
Programs-MicroMod Automation-XMBOPC.
8-2
Training Manual
We will add a device to this database. We will save this database later.
Figure 8 .1.
MICROMOD
Extended MODBUS
OPC Server
3. Add a hardware device to the database: Click on the New XMODBUS Device button
on the toolbar or select Add-New XMODBUS Device from the menu bar at the top. This
will open the Extended MODBUS Device Properties dialog box as shown in the figure
below:
• We will configure the properties of the MOD 30ML device we are adding in this
dialog box.
Figure 8 .2.
Add new Extended
MODBUS Device
8-3
Training Manual
• Type the name MOD30ML in the Name field (the name is user-configurable and
can be anything!).
• Select the serial communication port of the computer to which the MOD 30ML is
connected, in the Port field. Click on the down arrow in this field to show the drop-
down menu and then select the port. (COM1 for example).
• Type the instrument’s MODBUS address in the address field.
• Leave the Timeout in the default value of 500 ms.
Timeout value in ms is the time for which the OPC server tries to re-establish
communication with the device in the case of a communication failure.
4. Configure the serial port for the communication: Click on the Edit – Ports button on
this dialog box. The Port Properties dialog box will be displayed as shown below:
Figure 8 .3.
Port Properties
• Select the COMM port from the drop-down menu in the Port field and then enable
it by checking the box next to the Enable field.
• Choose the Baud Rate, Parity, Flow Control, Data bits and Stop bits from this
dialog box. Make sure these entries match the settings of the instrument.
• Click on OK to complete the Port configuration.
• The Extended MODBUS Device Properties dialog box will redisplay with the
port number. Leave other fields on this dialog box at their default values.
• Click on OK. The added device will be displayed in the Device Tree on the left
frame as shown in the next figure:
8-4
Training Manual
Figure 8 .4.
MICROMOD
Extended MODBUS
OPC Server
database
5. Save the database: The OPC tag database can be save as a file with an extension
.MOPC.
• Select File – Save from the menu bar. Refer to the following figure.
• The Save As dialog box will be displayed next as shown below:
• Choose the same folder where you have saved the PIDLAB database for saving
this file and then type a name for the OPC tag database file in the File name field.
Figure 8 .5.
File – Save As
• Click on the Save button to save the file. The Title bar of the OPC Server will
redisplay with the saved file name.
• You can now either close the Extended MODBUS OPC Server application by
selecting File – Exit from the menu bar at the top or minimize it.
8.3.2 Part 2
6. Switch back to the ViZapp Designer. Your instrument document should be on the right
frame. Select Instrument – Download from the menu bar at the top.
8-5
Training Manual
Figure 8 .6.
Communication
Setup
• Click on the Browse button next to the Server name field to browse the OPC
Servers registered in the system.
• The Select OPC Server dialog box will be displayed as shown in the next figure:
• Look at the Available Servers box at the bottom. The MICROMOD XMODBUS
Server should be listed there.
You have installed the XMODBUS OPC Server which registered it into the Windows
system. If you have other OPC Servers registered in the system, you will see them in
the Available Servers list as well.
8-6
Training Manual
Figure 8 .7.
Select OPC Server
7. Select the Device: Click on the Browse button next to the Device Name field.
8-7
Training Manual
• The Select Device dialog box will display as shown below next. You will also
notice the XMODBUS OPC Server application started automatically with the OPC
database file you last saved.
Figure 8 .9.
Select Device
• This Select Device dialog box will show the name of the device you added to the
OPC Database in Part A of this lab. Select the device and then click on OK.
The devices in the Select Device list are populated from the last saved/opened
XMODBUS OPC Server database file
• The Communication dialog box will redisplay as shown below with the name of
the device in the Device Name field.
8. Populate OPC Server tag database with attributes selected in the MODBUS Interface File
(.MIF file):
By doing this you can populate the OPC Server tag database with tags that will be
automatically created from the attributes defined in the MIF file (attributes added to
your Configured List blocks in the strategy). This will save a tremendous amount of
engineering time as you do not have to create each tag manually.
This will also create a list of Tags in the ViZapp Configurator automatically. These
tags can be used to add graphic objects to your instrument documents and display
documents.
8-8
Training Manual
Figure 8 .10.
Communication
Setup
• Click on OK on this dialog box. The Download Status Indicator will display as
shown below if the communication with the instrument was established. If there
was no communication, you will get error message boxes.
Figure 8 .11.
Downloading
• The OPC Server application will also be closed automatically if it was started by
ViZapp for downloading.
8-9
Training Manual
Figure 8 .13.
OPC Server
database with tags
• Do you notice that the OPC database is populated with tags from the MIF file
automatically? Also notice that the tags are shown with alias names.
• Select the device (MOD30ML1) and right-click on it. Select Properties from the
resulting menu.
Figure 8 .14.
Device Properties
By clicking on the button next to the MIF File field, you can choose a different MIF
file to attach to this device. Do not do that for this lab as the MIF file is already used to
populate the tags.
8 - 10
Training Manual
Figure 8 .15.
Device Properties
10. View Live data by starting the built-in OPC client application:
• Select View - Monitor from the menu bar at the top. This will start the built-in
OPC client and show live data from the instrument in the Value column of the
OPC Server application. Refer to the figure above.
• To change a value for a tag that is writable in the device, right-click on the tag
name and select Write Value. Writing to a read-only tag will produce an error.
8 - 11
Training Manual
11. View more details of the tags: Double-click on FICPVI. This will display further
properties of that tag as shown below:
Figure 8 .17.
Tag properties
• The above dialog displays the LSP, High and Low ranges, Read/Write of the tag.
• Click on the Close button to close this dialog.
8 - 12
9 Debug Lab
9.1 Foreword
It is important to debug the control strategy after it is downloaded to the instrument to see
if the instrument does what it is supposed to do. The ViZapp Designer provides a way to
debug the control strategy by displaying the live data from the instrument on the algorithm
blocks in the strategy.
ViZapp also provides a Status Viewer using which diagnostics from the instrument can be
read and acknowledged. The Status Viewer can also be used to read and write instrument
attributes.
Figure 9 .1.
ViZapp Debug
Display
9-1
Training Manual
Debug Lab
9.2 Objectives
In this lab we will run the PIDLAB document in debug mode using Vizapp Designer. We
will also read diagnostics from the instrument and acknowledge them from ViZapp using
the Status Viewer. After completing this lab, you should know how to:
9.3 Instructions
9.3.1 Part A
1. Launch ViZapp Designer if it was not running already. Open the PIDLAB instrument
document. The document (strategy) will open as shown in the figure below: (the position
and size of the blocks might be different). This is a static display.
• Select Project – Start Debug Mode from the menu bar at the top.
If you get perpetual communication error boxes popping up, force the server closed,
acknowledge the remaining pop-ups and correct the communication problem before
launching Debug Mode again.
9-2
Training Manual
Debug Lab
Figure 9 .3.
Debug
• This will start the OPC Server (XModbus or ICN) if it was not running already and
minimize it to the Windows task bar.
• You should also now see live data from the instrument displayed on the algorithm
blocks as shown below:
Figure 9 .4.
Debug mode
9-3
Training Manual
Debug Lab
• Notice that only the standard/important attributes of the algorithm blocks such as
PVI, SP, OP for PID block, Mode and R for AIN block are displayed on the
blocks.
• Double-click on the PID block. The Algorithm Properties dialog will be displayed
as shown below:
Figure 9 .5.
Debug mode
Algorithm
Properties
• This dialog will show more attributes of PID such as Gain, Preact, Reset, mode etc.
• Click on the little button next to the Gain field on this dialog. This will popup a
key pad on the screen as shown below:
9-4
Training Manual
Debug Lab
Figure 9 .6.
Enter Value Pad
• Click on the text field at the top on this pad and then type a new value for the Gain.
You can either click on the number buttons on this pad or type using the number
keys on your keyboard.
• Click on Enter. This will change the PGAIN attribute of the PID running in the
instrument. Do not click on the OK button now! Click on the Diagnostics tab on
the Algorithms Properties dialog.
Figure 9 .7.
Diagnostics
• The diagnostics tab will display diagnostics related to the PID lab. You can also
acknowledge the diagnostic alarms.
9-5
Training Manual
Debug Lab
• Click on OK. Try changing the Set point and Mode of the Controller in the same
way.
Edit – Debug Cursor: There are two different modes for the cursor during Debug.
The default cursor type after entering Debug mode is “Debug” and the cursor will be
white. Refer to the following figure. During this mode, you cannot edit the document –
cannot move blocks, resize them or open them etc.
To be able to edit during the debug mode, click once on the cursor/selection button on the
Draw toolbar. The cursor will appear black now. Now you can edit the document, add
objects, open a loop compound or close it, etc. If you now double-click on the PID block,
it will display the PID block properties.
Figure 9 .8.
Edit / Debug Cursor
You can also add graphic objects such as bar-graphs, trends, color changes to the
Modcell / MOD 30ML documents (strategy) and can animate in Debug mode. We will
do that later in a different lab.
9-6
Training Manual
Debug Lab
• Select Instrument – Status from the menu bar at the top. This will display the
Communication Setup dialog as shown below:
Figure 9 .9.
Communication
Setup
• This will show the Server name and the Device name in the respective fields. Just
make sure these are correct.
• Click on OK. This will start the Instrument Status display as shown below:
Figure 9 .10.
Instrument Status
• This Instrument Status display has a text field to enter commands and a set of
buttons.
Debug Lab
• Type R STATE in the command field and then click on the Enter button.
Figure 9 .11.
Instrument Status
• The command you entered will be echoed on the main window above, followed by
the response from the instrument.
3. Read diagnostics:
• Type R DIAGS in the command field and then click on Enter. Instrument
diagnostics will be displayed as shown in the next figure. You may get more
diagnostic errors or none.
Commands are not case-sensitive. When reading/writing attributes, use the block type
with occurrence number, as shown in the CRF file.
9-8
Training Manual
Debug Lab
Figure 9 .12.
Instrument Status
• Click on the View CRF button. This will display the cross reference information as
shown below:
Figure 9 .13.
Cross Reference
• The Cross Reference Information gives the Tag Name of each algorithm block
with its path and block’s Type with occurrence number.
9-9
Training Manual
Debug Lab
• Type W PID1.SP 90 F in the command line and press Enter to change the value
of the setpoint to 90. The instrument will report the current value of the setpoint.
• Note that in this case, the “F” denoting floating point data type is not required,
though it is required for attributes such as an expression block input, because the
data type is variable. Please refer to table 2-1 in IB-23G600 for data type details.
Figure 9 .14.
Instrument Status
9 - 10
10 Peer-to-Peer Communications
10.1 Foreword
Communications between MOD30ML instruments takes place over the Instrument
Communications Network (ICN). The ICN is a token passing, deterministic network,
which updates every 250ms. Using the ICN, MOD30ML can also communicate with
MODCELL Multiloop Processors and MOD30 1700 Series instruments on a peer-to-peer
basis. “Peer-to-peer” means there is no network master and each instrument is guaranteed
access to the network within a certain timeframe.
ICN signals are received in the Input Communications Blocks. ICN signals are sent via
the Output Communications Blocks. MOD 30ML, MODCELL and MOD 30 all have
these blocks. When configuring the Input Communications Block of a MOD 30ML, the
user must specify the ICN address and Output Communications Block number from the
instrument sending the data. When configuring an Output Communications Block in
MOD 30ML, the user must specify the ICN address and Input Communications Block
number of the instrument receiving the data.
There are 32 Input Communications Blocks and 32 Output Communications Blocks
available in each MOD 30ML controller.
10.2 Objective
In this lab we will configure PID master/slave signals between two MOD 30MLs over the
ICN as shown below. The lab is based on a strategy already containing a PID block and
display.
Figure 10 .1.
ICN Architecture
OP RSPI
(Note that the IC
LIC-
FIC -10 FIC-
LI -10
and OC
65.
65.2 48.6 occurrence
numbers and
OPTI ARSP
AU
AUT AU
AUT instrument
LOC
LO
TCI
LO
LOC
REM addresses are only
OP
O
S TS OP
/ /
examples for the
40.0
40. 25.2
purposes of this
lab. They do not
imply any
MASTER SLAVE
requirement to use
ICN Addr 1 ICN Addr 2 these addresses.)
10 - 1
Training Manual
Peer-to-Peer Communications
10.4 Instructions
Follow these instructions step-by-step to add and configure the peer-to-peer communications
1. Install an ICN Module into the controller’s slots 7 and 8 set its address to 1.
• Select the IC (Input Communications) block from the Algorithms window and add
it to the document, near the PID block. Note: The IC blocks can only be added
from within a Loop Compound.
Figure 10 .2.
Algorithms menu
10 - 2
Training Manual
Peer-to-Peer Communications
Figure 10 .3.
IC block
• Analog signals are generally Floating Point. For this exercise, choose this option by
moving the cursor over “Floating point” and clicking it.
• Click on the Data Source tab at the top of the dialog box.
Figure 10 .4.
Data Source
• The Instrument Number is the ICN Address of the instrument from which the data will be
received. For this lab, we will use 2.
• The OC Number is the Occurrence Number of the Output Communications Block in the
instrument from which the data will be received. We will use 1 for now, though it will need
verification after the other instrument’s database has been completed and compiled.
In an actual application, you must refer to the CRF (Cross Reference File) for the
instrument sending data, to obtain the Occurrence Number of the OC block. This is for MOD
30ML or MODCELL instruments. MOD 30 instruments have fixed OCOM numbers; refer to
the instrument’s configuration.
10 - 3
Training Manual
Peer-to-Peer Communications
The Cross Reference File gives the Tag Name of each algorithm block with its path and block’s Type
with occurrence number. To view the Cross Reference information, select Instrument from the menu
bar at the top and select View CRF from the menu. You could also right-click on a blank are of the
function block diagram and then select View CRF.
The next figure shows Cross Reference information for a sample database.
Figure 10 .5.
Cross Reference
• The Port Number can be either 1 or 2 for a MOD 30ML. The Built-In Port or a module in slots
9 and 10 would be Port 1. For this lab, you will be using a module plugged into slots 7 and 8,
the Port 2 location.
MOD 30 1700 series instruments have slightly different data types than MOD 30ML and
MODCELL. The MOD 30 Conversion side of this menu is for data being received from
MOD 30 instruments.
• Click OK to close the dialog box.
• Select the Multi-Segment Connection icon in the Algorithms window
10 - 4
Training Manual
Peer-to-Peer Communications
Figure 10 .6.
Multi-Segment
Connection Icon
• Click on the IC block in the workspace: the Parameter connection list will appear.
• Double-click on R (the output of the block, which is the signal from the other instrument)
Figure 10 .7.
IC Block
Connection Menu
• Drag the line from the IC block directly over the middle of the PID block
• Click on the PID block: the Parameter connection list will appear.
• Double-click on OPTI (the output track input)
10 - 5
Training Manual
Peer-to-Peer Communications
Figure 10 .8.
PID Block
Connection Menu
• The connection will now be complete. The connection line will have the source name and
destination name displayed right on it as shown in the figure below. The signal from the other
instrument on the ICN will now be the Output Track signal for this PID block.
Figure 10 .9.
PID Block
Connection Menu
• Select the OC (Output Communications) block from the Algorithms window and add it to the
document near to the PID block. Note: The OC blocks can only be added from within a Loop
Compound.
10 - 6
Training Manual
Peer-to-Peer Communications
Figure 10 .10.
Algorithm – OC
Block
• Click on the Data Destination tab at the top of the dialog box.
10 - 7
Training Manual
Peer-to-Peer Communications
Figure 10 .12.
Data Destination
• The Instrument Number is the ICN Address of the instrument to which the data will be sent.
For the purposes of this lab we will enter an address of 2.
• The IC Number is the Occurrence Number of the Input Communications Block in the
instrument to which the data will be sent. We will use 1 for now, though it will need
verification after the other instrument’s database has been completed and compiled.
• For this lab, you will be using a module plugged into slots 7 and 8, the Port 2 location.
• Click OK to close the dialog box.
• Select the Multi-Segment Connection icon in the Algorithms window
• Click on the PID block in the workspace: the Parameter connection list will appear.
• Double-click on OP (the output)
Figure 10 .13.
Alarm Block
Connection Menu
10 - 8
Training Manual
Peer-to-Peer Communications
• Drag the line from the PID block directly over the middle of the OC block
• Click on the OC block: the Parameter connection list will appear.
• Double-click on INPUT
Figure 10 .14.
OC Block
Connection Menu
• The connection will now be complete. The connection line will have the source name and
destination name displayed right on it as shown in the figure below. The output signal from the
PID block will be sent to the other instrument on the ICN for use in its control strategy.
Figure 10 .15.
Connecting blocks
10 - 9
Training Manual
Peer-to-Peer Communications
1. Install an ICN Module into the controller’s slots 7 and 8 and set its address to 2.
• Select the IC (Input Communications) block from the Algorithms window and add it to the
document, near the PID block. Note: The IC blocks can only be added from within a Loop
Compound.
Figure 10 .16.
Algorithms menu
10 - 10
Training Manual
Peer-to-Peer Communications
• Analog signals are generally Floating Point. For this exercise, choose this option by moving the
cursor over “Floating point” and clicking it.
• Click on the Data Source tab at the top of the dialog box.
Figure 10 .18.
Data Source
• The Instrument Number is the ICN Address of the instrument from which the data will be
received. For this lab, we will use 1.
• The OC Number is the Occurrence Number of the Output Communications Block in the
instrument from which the data will be received. We will use 1 for now, though it will need
verification after the other instrument’s database has been completed and compiled.
• The Port Number can be either 1 or 2 for a MOD 30ML. The Built-In Port or a module in slots
9 and 10 would be Port 1. For this lab, you will be using a module plugged into slots 7 and 8,
the Port 2 location.
• Click OK to close the dialog box.
• Select the Multi-Segment Connection icon in the Algorithms window
• Click on the IC block in the workspace: the Parameter connection list will appear.
• Double-click on R (the output of the block, which is the signal from the other instrument)
10 - 11
Training Manual
Peer-to-Peer Communications
Figure 10 .19.
IC Block
Connection Menu
• Drag the line from the IC block directly over the middle of the PID block
• Click on the PID block: the Parameter connection list will appear.
• Double-click on RSPI (the remote setpoint input)
Figure 10 .20.
PID Block
Connection Menu
• The connection will now be complete. The connection line will have the source name and
destination name displayed right on it as shown in the figure below. The signal from the other
instrument on the ICN will now be the Remote Setpoint signal for this PID block.
10 - 12
Training Manual
Peer-to-Peer Communications
Figure 10 .21.
PID Block
Connection Menu
• Select the OC (Output Communications) block from the Algorithms window and add it to the
document near to the PID block. Note: The OC blocks can only be added from within a Loop
Compound.
Figure 10 .22.
Algorithm – OC
Block
10 - 13
Training Manual
Peer-to-Peer Communications
Figure 10 .23.
OC Block
Properties
• Click on the Data Destination tab at the top of the dialog box.
Figure 10 .24.
Data Destination
• The Instrument Number is the ICN Address of the instrument to which the data will be sent.
For the purposes of this lab we will enter an address of 1.
• The IC Number is the Occurrence Number of the Input Communications Block in the
instrument to which the data will be sent. We will use 1 for now, though it will need
verification after the other instrument’s database has been completed and compiled.
• For this lab, you will be using a module plugged into slots 7 and 8, the Port 2 location.
• Click OK to close the dialog box.
• Select the Multi-Segment Connection icon in the Algorithms window
• Click on the PID block in the workspace: the Parameter connection list will appear.
• Double-click on ARSP (the adjusted remote setpoint)
10 - 14
Training Manual
Peer-to-Peer Communications
Figure 10 .25.
Alarm Block
Connection Menu
• Drag the line from the PID block directly over the middle of the OC block
• Click on the OC block: the Parameter connection list will appear.
• Double-click on INPUT
Figure 10 .26.
OC Block
Connection Menu
• The connection will now be complete. The connection line will have the source name and
destination name displayed right on it as shown in the figure below. The output signal from the
PID block will be sent to the other instrument on the ICN for use in its control strategy.
10 - 15
Training Manual
Peer-to-Peer Communications
Figure 10 .27.
Connecting blocks
10 - 16
11 Expression Block Lab
11.1 Foreword
The Expression Block is one of the most powerful blocks and perhaps the most often used
block in MOD 30ML. This lab will provide a series of partial applications where an
Expression Block would be the best tool to solve the requirement. Enter the appropriate
expression and input names. Be prepared to demonstrate to the class your proposal for
each problem.
11.2 Objectives
In this lab you will configure 3 process applications using the Expression block. Refer to
the example given below and the reference material provided in this chapter to get more
information about the EX block.
11.3 Instructions
11.3.1 Example: Add 2 Inputs (Note: See the end of this section for operators and rules)
1. Configure 2 analog inputs and their corresponding Signal conditioning (Input Function)
blocks as shown in the next figure. See the end of this section for additional information.
2. Configure an EX block:
• Add 2 inputs under the Inputs tab of the EX block by typing names inp1 and inp2
and data type as Floating Point.
Figure 11 .1.
EX block Example
11 - 1
Training Manual
Figure 11 .2.
EX block Example
• Specify the data type for the result as Floating point under the General tab of the
EX block.
11 - 2
Training Manual
11.3.2 Application #1
Find the average pressure between four boiler headers.
Hints: Add 4 analog input (4-20 mA) and corresponding Signal conditioning blocks. Add
an EX block and configure 4 inputs. Use these 4 inputs in your expression to find the
average.
11.3.3 Application #2
Turn on a fan when the temperature is greater than 82 degrees and provided the room door
is not open.
Hints: You need a thermocouple or RTD input and a signal conditioning blocks.
Configure a DIM block for the room door and a DOM block for the fan. Use If Then Else
statement or simple mathematical expression in the EX block.
11.3.4 Application #3
Select the one input out of 4 that is the lowest value.
Hints: Configure 4 inputs. There are more than one ways of configuring this in the EX
block. One of them is to use nested If Then Else statements. Take one input at a time and
compare that with the other 3 inputs to see if it is the lowest.
11 - 3
Training Manual
Precedence Operator
1 ** RAISED_TO_THE_POWER
2 SQRT SQUARE_ROOT
MOM MOMENTARY
! Logical NOT
ABS ABSOLUTE
EXP EXPONENTIAL
NLOG NATURAL_LOG
LOG LOG_10
INT INTEGER
3 * TIMES
/ DIVIDE
4 + PLUS
– MINUS
5 < LESS_THAN
> GREATER_THAN
<= LESS_THAN_OR_EQUAL
>= GREATER_THAN_OR_EQUAL
6 == EQUALS
!= UNEQUAL
11 - 4
Training Manual
For comparison or arithmetic operations, all operands are scaled to floating point during
evaluation. DATE operands are expanded to include the century and treated as 4 byte
unsigned integers. Prior to applying the operator(s), if the year is in the range 0–89, 100 is
added to make comparisons work properly across the calendar year 2000 (valid for 1990
to 2089). Thus 3/18/95 (stored internally as $5F0312) is treated as $005F0312, or decimal
6226706, while 7/25/2012, (stored internally as $0C0719) is treated as $00700719, or
decimal 7341849. HEX and ASCII operands are not allowed.
Evaluation Results
The result of an expression evaluation is DISCRETE if the last operator processed was
logical, or FLOATING POINT if it was arithmetic. This result is then scaled to the
configured data types for the result and auxiliary result outputs of the expression block.
The INTEGER operator removes the decimal portion of a number, leaving only the
integer portion. It does not round the number. For example, INT(12.678) = 12 and
INT(-746.21) = -746.
The conditional operators (IF, THEN, and ELSE) let you specify when operations are
evaluated. The IF expression (between the IF and THEN conditionals) is evaluated first.
This expression may be enclosed in parentheses. When the calculated value of the IF
expression is TRUE (non-zero), the THEN expression is evaluated. When it is FALSE
(zero), the ELSE expression is evaluated. The ELSE expression is optional. When the IF
expression evaluates to FALSE and there is no ELSE, the result is not updated. Brackets
({}) should be used for nesting conditionals. If brackets are not present, an ELSE
expression is paired with the last unpaired IF. Notice how the brackets change the pairing
of the IF and ELSE expressions in the following example.
11 - 5
Training Manual
Figure 11 .3.
If Then Else
Expression block inputs can be used as a recipe. Any number of local or remote inputs to
the block can be configured without using them in the expression, and for this purpose
only, HEX and ASCII inputs are allowed.
Syntax Errors
When there is a syntax error in the expression or a stack overflow during evaluation (can
only happen with a very deeply nested expression), the expression error diagnostic will be
reported, the results will not be updated and output qualities will be set bad.
11 - 6
12 Sequence Lab
12.1 Foreword
Configuring a sequence, logic or batch application is easier than ever with ViZapp. You
can configure names for the inputs, outputs and steps in a sequence block and they will be
reflected in the connections and debug screen. Unlike a PLC, the user is not required to
keep track of database or memory locations, and the use of step names instead of numbers
in the logic makes adding, moving or deleting steps much less engineering-intensive.
12.2 Objectives
This lab is designed to show some of the power of the Sequence Block. We will configure
a very simple sequence that includes starting a batch, filling a tank, heating the contents
and maintaining them at a certain temperature for a certain time, cooling them down and
draining the tank.
NOTE: Because this lab is for demonstration purposes, it does NOT contain all the
logic elements that would be required for a real application.
Figure 12 .1.
Sample Batch
Reactor
LSH
TE
LSL
The operator starts the sequence from the front panel of the controller (configured in a
later lab). If the drain valve is closed, the charge valve opens and the vessel begins to fill.
When the level reaches a certain point, a high level switch is tripped and the Charge valve
shuts. A setpoint of 90 degrees is sent to a temperature controller (also part of a later lab)
and begins heating the product.
When the product temperature reaches setpoint, it is held there for one hour, then allowed
to cool to 20 degrees (a setpoint of 20 is sent to the same temperature controller).
12 - 1
Training Manual
Sequence Lab
When the product temperature reaches 20 degrees, the drain valve is opened and remains
open until the low level switch is tripped. The drain valve shuts and the process remains
in Idle until the operator pushes the start button again.
12.3 Instructions
1. Add a new Mod Function Block Diagram (database document) to your workspace:
• Right-click on the Mod Function Block Diagrams icon in the top right window
• Click New MOD Function Block Diagram document
Figure 12 .2.
New MOD Function
Block Diagram
• Select the LoopCpd icon from the Algorithms window and place it in your workspace.
• Double-click the compound block and enter a name such as Batch, and a description like
the one shown below. Then click OK to close the block
12 - 2
Training Manual
Sequence Lab
Figure 12 .3.
Loop Compound
• Right-click on the Loop Compound block and select Open Compound from the menu.
• Select from the Algorithms window and place the following blocks in your database for
the inputs and outputs to the sequence:
• 3 Digital Input Modules - DIM
• 2 Digital Output Modules - DOM
• 1 Wide Resistance Input Module WRIM
• 1 Resistance Temperature Input Function RTI
• Select a SEQ (Sequencer) block from the Algorithms window and place it on the
document workspace.
• Your screen should look something like the next figure. The placement of the blocks can
be different.
12 - 3
Training Manual
Sequence Lab
Figure 12 .4.
Blocks
• Digital Inputs/Outputs: Change the tag names and descriptions. Accept all other entries in
their default. The tag names and descriptions are as below:
• LSL - Level Switch LOW DIM
• LSH - Level Switch HIGH DIM
• Draining - Feed back from the drain valve DIM
• Drain - Output to Drain Valve DOM
• Charge - Output to Charge valve DOM
• Analog Inputs and Function blocks: Change the tag names and descriptions. For the RTI
block configure the quality limits as -5 to 105 Degrees Celsius.
• TE - Reactor Temperature sensor WRIM
• TI - Reactor Temperature RTI
• Select Instrument - I/O Graphic - MOD30ML from the menu bar at the top. See next
figure:
12 - 4
Training Manual
Sequence Lab
Figure 12 .5.
I/O Graphic menu
• The I/O Graphic will be displayed next as shown below: Notice that except for the built-
in I/O and Communication, all the modules are placed on Slot 1 by default.
• Move the modules with the left mouse button held down to other locations so that the
modules do not overlap.
Figure 12 .6.
MOD30ML I/O
Graphic - default
placement
• After relocating the modules, your I/O Graphic should look something like the one in the
next figure.
12 - 5
Training Manual
Sequence Lab
Figure 12 .7.
MOD30ML I/O
Graphic
• Double-click on the TE block on this I/O Graphic. This will open the WRIM Properties
dialog. Notice the change in the Module Slots on this dialog.
Figure 12 .8.
WRIM Properties
12 - 6
Training Manual
Sequence Lab
• Double-click on the SEQ block to open the SEQ Properties dialog as shown below:
Figure 12 .9.
SEQ Properties -
General Tab
• Type a tag name and description as shown above under the General tab.
• Click on the Inputs tab of this dialog. Refer to the next figure:
Figure 12 .10.
SEQ Properties -
Inputs Tab
12 - 7
Training Manual
Sequence Lab
• Click on the Add button at the bottom. This will open the Specify Input Data dialog box
as shown below:
Figure 12 .11.
Specify Input dialog
One of the powerful attributes of the Sequence block is the ability to assign names to
inputs, then use the names in the step logic. This makes it very easy for someone to
look at the block and understand the logic.
• Click on the down arrow in the Data Type field and select Discrete from the list. The
dialog should look like the figure below:
Figure 12 .12.
Specify Input dialog
• Click on OK to close this dialog. The input you just added will be listed under the Inputs
tab of the SEQ Properties dialog as shown below.
This discrete input will be used for starting the batch and will be later connected to the
StartPB digital input module wired to the Start Push Button on the control panel.
12 - 8
Training Manual
Sequence Lab
Figure 12 .13.
SEQ Properties -
Inputs Tab
• Add more inputs to the SEQ block as below: Leave the initial value data field in its
default value.
Use the Modify button if you make a mistake. Select the input and then click on the
Modify button.
12 - 9
Training Manual
Sequence Lab
After adding all the inputs, the Inputs tab should look like the following figure:
Figure 12 .14.
SEQ Properties -
Inputs Tab
• Notice that these inputs are assumed to be local until we connect them external inputs and
are assigned initial values as shown in the figure below.
• The inputs can be in any order. To rearrange the entries, use the Move Up / Move Down
buttons.
• We need to add the outputs to the sequencer now. Click on the Outputs tab of the SEQ
Properties dialog box.
12 - 10
Training Manual
Sequence Lab
Figure 12 .15.
SEQ Properties -
Outputs Tab
• The Outputs tab will be displayed next as shown above. Click on the Add button on this
tab. The Specify Output Data dialog will be displayed next.
Figure 12 .16.
Specify Output
Data dialog
• Type ChargeV for the name of this output and select Data Type as Discrete. This output
will be locally generated and will be connected to the Charge valve via a digital output
module.
• Click on OK. This added output will be displayed in the Outputs list as shown below:
12 - 11
Training Manual
Sequence Lab
Figure 12 .17.
SEQ Properties -
Outputs Tab
Another powerful feature of the Sequence Block is that each output can be assigned
names. These names can be used in the step logic expressions. The outputs can be
assigned different values in each step based on the logic. Outputs can be any data type
supported by MOD30ML, including discrete and floating point.
• Add more outputs as per the following table:
Output Name Type Initial
Number Data
2 DrainV Discrete False Drain Valve
3 Setpoint Floating Point 0.0 Heating/Cooling
Setpoint
4 CtrlMode Short State 0 Sends new mode status
to temp controller
5 SetMode Discrete False Triggers temp
controller mode change
After adding all the outputs, the Outputs tab should look like the following figure:
12 - 12
Training Manual
Sequence Lab
Figure 12 .18.
SEQ Properties -
Outputs Tab
Notice that these outputs are assigned initial values that can be changed by the step
logic. These outputs can be connected to other blocks in the database and also to the
field via the output modules.
We have defined the inputs to the sequence block, and the outputs it will control. All that
remains is to define the steps in the sequence, and the logic that controls the step changes.
We will add 6 steps to the sequencer (IDLE, CHARGE, HEAT, COOK, COOL and DRAIN).
• Click on the Steps tab of the SEQ Properties dialog.
12 - 13
Training Manual
Sequence Lab
Figure 12 .19.
SEQ Properties -
Steps Tab
• Click on the Add button. The Specify Data for this Step dialog will be displayed:
Figure 12 .20.
Specify Step dialog
12 - 14
Training Manual
Sequence Lab
• Click on OK to close the dialog box. The Steps tab of the SEQ Properties dialog shows
the step you added.
Figure 12 .21.
SEQ Properties -
Steps Tab
)Notice that there are columns for the step number, step name, and expression, and
for each output you added in the Outputs tab. Up to 64 outputs can be configured in
one Sequence block, and each output can assume a different state or value for each
step.
• Add more steps as per the following table:
Step # Step Name ChargeV DrainV Setpoint CtrlMode SetMode
2 Charge True False 0 0 False
3 Heat False False 90 1 True
4 Cook False False 90 1 False
5 Cool False False 20 1 False
6 Drain False True 0 0 True
The outputs “CtrlMode” and “SetMode” will be used to change the temperature
controller from Manual to Automatic in the Supervisory Message lab.
12 - 15
Training Manual
Sequence Lab
• After adding all the steps, the Steps tab of the SEQ Properties dialog will look like the
figure below:
Figure 12 .22.
SEQ Properties -
Steps Tab
Remember, the Transition Expression defines what makes the sequence leave the
current step and go to another. TIME is a sequence block attribute which indicates the
time in the step. There is a timer that starts as soon as you enter each step, and resets
upon transition to the next one.
• Click on OK to close the SEQ block.
• Select the Multi-segment connector from the Algorithms window and then click on the
LSL (DIM) block.
• The Choose Parameter dialog of the DIM block will be displayed next.
• Select R (Result) from the list (Refer to the next figure)
12 - 16
Training Manual
Sequence Lab
Figure 12 .23.
Dim Choose
Parameter
• Drag the cursor to the StepMGR (SEQ) block and click on it.
Figure 12 .24.
Connect to SEQ
block
12 - 17
Training Manual
Sequence Lab
Figure 12 .25.
SEQ Choose
Parameter - digital
Source Destination
LevelHI.R (DIM block) StepMGR.LevelHI (SEQ)
TE.Modout (WRIM block) TI.Modin (RTI block)
Draining.R (DIM block) StepMGR.Draining
TI.R (TI block) StepMGR.Temp
StepMGR.DrainV Drain.Input (DOM block)
StepMGR.ChargeV Charge.Input (DOM block)
After making the connections, your screen should look like the next figure:
12 - 18
Training Manual
Sequence Lab
Figure 12 .26.
SEQ and other
blocks connected
• Save your document. Click on the Save icon on the tool bar.
• Compile your document.
Note: because this database does not include a Display Block, we will not download to
the instrument. A display for this sequence will be created in another exercise.
12 - 19
Training Manual
Sequence Lab
12 - 20
13 Supervisory Message Lab
13.1 Foreword
The Supervisory Message block is a function block that sends or receives messages based upon
being triggered via a “send” source input transition from 0 to 1, or the send command being issued
via operator write.
It is used to send a single message over the ICN to another controller or internally (within the MOD
30ML or MODCELL) to an addressable attribute. Some attributes, such as controller mode, can
only be written to via a supervisory message.
13.2 Objectives
This lab is a continuation of the Sequence lab and builds on the database constructed to control the
batch. In that lab, the sequence logic sends new setpoint values and control modes to a Temperature
Controller which was not actually present in the database.
In this lab we will load the temperature control loop from the Component Gallery, set up
supervisory messages to switch the control mode between Manual and Auto, and connect the
setpoint value outputs from the Sequence block to the temperature controller’s remote setpoint.
When the sequence is in IDLE and CHARGE modes the temperature controller is in Manual.
When the sequence reaches the HEAT step, the sequence block sends a Supervisory Message to the
controller to place it in Auto, and sends the remote setpoint value 90 to the temperature controller’s
Remote Setpoint Input. The controller remains in Auto with a setpoint of 90 through the COOK
step. When the sequence enters the COOL step it sends a new setpoint value of 20 to the
temperature controller, and when the COOL step is finished it places the controller back in Manual
mode.
13 - 1
Training Manual
13.3 Instructions
Make sure the Sequence database you constructed in the Sequence Lab is loaded in ViZapp. You
should be at the top level with the DIF, IF, ST, and SE blocks visible along with the BATCH
compound.
3. On the top toolbar, click on Project / Gallery / Component It is important to select Component
Gallery Gallery rather than Open Component
Gallery or New Component Gallery, both
of which will try to install a new gallery
file.
If your Component Gallery appears empty,
close ViZapp. Run Restore Gallery from
the MicroMod Automation\ViZapp folder
in the Windows Start menu, then follow
the directions.
Re-open ViZapp, load your strategy and
open the Loop Compound, then access the
Component Gallery as shown at right.
4. Click on the Compounds tab in the Gallery dialog box, select the You can also double-click on the
compound ML_PID and click the Export button. compound to be exported to your database
instead of using the Export button.
13 - 2
Training Manual
5. With the new compound selected (it will have green “handles” at
the corners), on the top toolbar select Objects / Uncompound
Your database workspace should now look like the figure below.
13 - 3
Training Manual
7. Click on the Modes tab and change the Initial Setpoint Mode to
Remote, then click OK to close the block.
13 - 4
Training Manual
2. Open the SM block and give it the following tag name and
description:
Name: A/M
Description: mode change signal from sequence block
3. Change the Data Type to Short State using the pull-down menu
This block will change the controller mode
based on the sequence step. Controller
mode is a short-state variable.
4. Click on the Message tab. Notice that the default Message Type There are several message types that can
is ‘Set’. be sent by the Supervisory Message block.
To change a control mode we need to use
the SET command.
9. Click on SETENTRY in the connection window. The connection between the SM block and
the block receiving the SET command
actually goes from the destination block to
the SM block, and appears to be
“backward”.
13 - 5
Training Manual
10. Right-click in the open space of your database and close the You should be at the top level of your
compound. database, with the IF, DIF, ST and SE
blocks visible on the screen as well as the
BATCH and TEMP CONTROL
compounds.
13 - 6
Training Manual
14. Move the scroll bar at the bottom of the window all the way to
the right. You should see the Inputs and Outputs you added to
the SEQ block in the Sequence lab.
15. Select CtrlMode and click OK This sends either a “0” or “1” to the
controller mode to switch between Manual
and Auto, when the message is triggered.
16. Drag the cursor to the TEMP CONTROL compound and select it
13 - 7
Training Manual
19. You should now have a connection between the two compounds
as shown:
13 - 8
Training Manual
In order to see the effect of the supervisory message on the temperature controller, we will need a display on the MOD
30ML.
13 - 9
Training Manual
1. Select an MSC block from the Algorithms window and place it No configuration of this block is necessary
in the database for this lab
3. Compile the database and fix any reported errors. When your
database compiles properly, in the Interface File dialog window
check the first box under “Produce MIF” and type the name
SEQUENCE, then click OK.
4. Open the OPC server by clicking on the OPC Server icon on the
top toolbar
5. Make sure the correct Server Name, Server Node and Server are See the Extended Modbus OPC Server lab
selected for assistance
6. If you already have a Device configured, double-click to open If you do not already have a device
the Configuration menu. Make sure the Primary Port settings are configured see Chapter 4, Extended
correct. Modbus OPC Server, for assistance
13 - 10
Training Manual
7. In the Interface File Filename field, click on the Refresh icon A list of available MIF files appears
Refresh icon
10. Return to ViZapp and download the database to the controller The PID-100 display should be on the
controller front panel, with the control
loop in manual and a setpoint of 0.
We do not have a display for the Sequence, but we can use the ViZapp debug function to test the Supervisory Message
configuration.
13 - 11
Training Manual
4. Change the Mode from Auto to Manual, and then change the Did the PID controller come out of
Current Step from Idle to Heat. manual? Is the setpoint 90?
5. Now change the Current Step from Heat to Cool. Did the setpoint change to 20?
6. Finally, change the Current Step to Drain. Did the PID controller change to manual
mode? Is the setpoint zero?
7. Remember to stop Debug mode when you are done with the lab.
13 - 12
14 Process Alarm Display Lab
2.1 Foreword
In most process control applications, the user wishes to detect, view and acknowledge
alarm conditions from the front panel of the instrument. MOD 30ML provides extensive,
flexible alarm information, which is completely configurable and extremely easy to
define. This lab will teach you how to define and display process and deviation alarms
using the Process Alarm Display blocks.
2.2 Objectives
In this lab, we will add a high and low alarm to the PID loop you configured in the earlier
lab. Ensure you have loaded the file with the PID loop.
Using the Process Alarm Display blocks, defining the alarms and creating the displays are
the same activity.
2.3 Instructions
A - LOAD A PROCESS ALARM DISPLAY BLOCK
3. Drag the box onto the screen and fix it in place by You should now have a block on your
clicking the left mouse key. Move and size the block screen called PAD
so it is in an appropriate area of your screen.
14 - 1
Training Manual
6. Using the pull-down menu, change the Trip The alarm will activate (trip) when the
Condition to Greater Or Equal process value is greater than or equal to
the trippoint
7. Enter a trip value of 150 Since the flow is 0 to 200 GPM, the alarm
will trip at 150 GMP or 75%
8. Select the Display tab of the PAD block Refer to the next figure.
9. Change the Display Format field from “Float 6” to The numerical display of the alarm will be
“Float 1” by selecting it with the mouse floating point with one place to the right
of the decimal point
11. Select “Normal” for the Bar Format field The range fields are activated
14 - 2
Training Manual
14. In the Line 1 Text field, type FIC-100 This is what will appear on the top line of
the alarm display
15. In the Line 2 Text field, type FLOW HI This is the label that will appear on the
second line of the display
16. Change the Action button from “Return to previous When the alarm page is displayed,
display” to “Go to display with this tag” and type pressing the TAG key will automatically
FIC-100 (or the Display Tag you used for your PID take you to the operator display for FIC-
block) 100
2 Click in the middle of the PID block A menu of possible connections appears
14 - 3
Training Manual
5 The only possible connection is ALARMINP (alarm You now have a line from the PID block
input); this is done automatically by ViZapp to the PALM_H block
1 Using the printout provided, repeat this exercise to configure and connect a low process
alarm with the following characteristics:
2 Compile and download your configuration. Check your alarms by changing the input to
the unit to create the alarm conditions. View and acknowledge the alarms.
3 If you are using the MOD 30ML demonstration box, use Pot #2 to vary the “process”
input and trigger the alarms.
14 - 4
15 Totalizer Display Lab
15.1 Foreword
In many process control applications, indication of a totalized variable is required. The
user may also wish to operate the totalizer from the front panel. This lab uses a totalizer
and display to examine some of the elements of custom display building.
15.2 Objectives
In this lab, we will add a totalizer block to the database and construct a display to view
and clear the total value from the front panel. Make sure you have a database loaded that
contains a PID block and associated DISP block.
15.3 Instructions
A - LOAD A TOTALIZER BLOCK
3. Drag the box onto the screen and fix it in place by You should now have a block on your
clicking the left mouse key. Move and size the block screen called TOT.
so it is in an appropriate area of your screen.
4. Open the Totalizer block. Set the Analog Input to 1 Because there are no actual inputs
as shown. connected to the controller we will totalize
an internal constant. Normally there
would be an external connection to
another block, such as the PVI from a PID
block.
6. Change the Initial Mode to Run The Totalizer will begin totalizing the
15 - 1
Training Manual
10. In the Name field, type a name such as DispTOT This identifies the block within the
database and is NOT the tag name that
will appear on the display.
11. In the Display Tag field type a tag name such as This is the tag name that will appear on
STM TOT the operating display.
12. In the Initial Data section, type Total in the blank We will define an input called Total, and
field next to Line 2 its value will appear on Line 2 of the
display during operation.
13. In the Initial Data section, type “CLR”, including the We will define a constant string value
quotes, in the blank field next to Line 5 CLR to appear on Line 5 of the display
during operation.
14. In the Initial Data section, type Clear in the blank We will define an input called Clear, and
field next to Line 6 its value will appear on Line 6 of the
display during operation.
15. Select the Inputs tab We will add the totalized value and the
ability to reset the totalizer from the front
face. This requires two new inputs.
16. Click on the Add button and configure the new Total Total is the name of the input.
15 - 2
Training Manual
17. Click on the Add button and configure the new clear clear is the name of the input.
input as shown below, then click OK to close the
menu This will be a discrete input from the
keypad on the controller.
18. Select the Formats tab, click on the Add button and
configure the format for the Total value:
15 - 3
Training Manual
19. Add a format for the clear variable: clearL is the format name
21. Connect the totalizer block output TC to the display This allows the totalized count to be
block input Total shown on the display.
22. Connect the display block Clear to the totalizer block This allows the user to clear the totalized
input RESINP count from the display.
24. Select the Tables tab and scroll to the bottom of the It does not matter where the tables are
list of tables. added; however, be sure not to embed
them within an existing State Table. It is
usually best to add State Tables to the end
of the file.
25. Add the following script to the BOTTOM of the list Clear is the table name
of State Tables:
3 is the maximum number of characters to
Clear, 3, “???” be displayed for the field in this table.
{
1, “YES”; The question marks will be shown on the
0, “NO”; display in the event the value is neither 1
} nor 0.
15 - 4
Training Manual
33. Press the TAG key to view the new STM TOT
totalizer display.
34. Press the up/down arrow key to select YES. Press The total value resets to zero and
ENT. begins totalizing again.
15 - 5
Training Manual
15 - 6
16 CJC and Display Lab
16.2 Objectives
In this lab, we will configure a compensated temperature input and create a display that
toggles between compensated temperature and CJC temperature when the Scroll key is
pressed.
16.3 Instructions
A - PLACE AND CONFIGURE THE TEMPERATURE MEASUREMENT
3. Right-click on the new TEMP compound and You are now “inside” the compound, and the
select Open Compound compound connection dialog box is visible.
4. Select AIN from the library window and place This is a built-in analog input.
the block on the screen.
9. In the Initial Results field, enter 10 Since we do not have an actual thermocouple
connected, we will simulate a 10mV input.
10. Change the Mode to Manual This is to allow the block to operate with the
16 - 1
Training Manual
3. Enter the block name TI-100 We will accept the default configuration for the
block
14. Change the block name to TempDisp This is NOT the tag name that appears on the
display during operation; it is the block reference
name.
15. Type in the name TI-100 in the Display Tag This is the tag name we will use to reference the
field. display in the Display Interface Block, and on the
front of the instrument.
16. Under Initial display data, type DISPTAG in This will cause the Display Tag (as entered in the
the Line 1 field. Display Tag field) to appear on Line 1 of the
display.
17. Type “TI” in the Line 5 field. DO NOT close DOUBLE QUOTES ARE REQUIRED. The text
the block. TI will appear on line 5 of the display after the
download. The quotes indicate text rather than an
input name.
18. Type TI in the Line 6 field. DO NOT use quotes! This will be an input name,
and the value will be displayed in Line 6.
16 - 2
Training Manual
6. At the bottom of the screen, select the Add The input editing menu appears
button
8. In the Line Format field, type TempL We have not yet set up the display formats; we will
do this in the next part of the lab.
9. Close the menu The new input appears on the Inputs window
11. Give Input 2 the name CJC and type in CJCL This will be the value being used for compensation.
for the format name
13. Add Input 3 and give it the name SCRLCNT This counts the number of times the Scroll Key is
pressed
15. Close the menu You should now have three inputs (TI, CJ and
SCRLCNT) listed in the Inputs window.
2. At the bottom of the screen, select the Add The Format editing menu appears
button
3. Select the field showing FMT1 and type in This was the format name we used when
TempL configuring the display block inputs
4. Use the pull-down menu to change the format to This will display the input as a floating point
Float2 variable with two places to the right of the decimal
point
5. Change the Low and High limits to -200 and This is the range for a Type K thermocouple
1200 respectively
6. Change the Entry Method to None This is for display only, no operator entry
16 - 3
Training Manual
9. Add a second format and give it the name This is the name that was designated in the Inputs
CJCL menu
11. Close the menu You should now have two formats listed in the
Format window.
DEFAULTS:
{
SCROLL_PRESSED: This script counts the number of times the scroll
{ key is pressed (starting with the first press being
IF SCRLCNT >= 1 THEN “0”, increments the count accordingly, then
SCRLCNT = 0; determines what appears on Lines 5 and 6 for each
ELSE SCRLCNT = SCRLCNT + 1; count.
CASE SCRLCNT OF
{ The hashmark indicates an assignment statement,
0: that is, a value, input or text is assigned to that
#LINE5 = "TI"; resource (in this case Lines 5 and 6). There are
#LINE6.SRC = TI; predetermined assignment statements; these are
BREAK; listed in the MOD 30ML Display Guide.
1:
#LINE5 = "CJC"; Text to appear on the display is enclosed in double
#LINE6.SRC = CJC; quotation marks.
BREAK;
}
}
}
16 - 4
Training Manual
3. When you have finished typing the script, click This will verify your script immediately, checking
on the Checkmark icon at the top of the for syntax errors.
window.
TT-100.MODOUT to TI-100.MODIN
TT-100.CJC to TempDisp.CJC
TI-100.R to TempDisp.TI
4 At the bottom of your display list add: This is the Display Name, NOT the name of the
TI-100 display block!
When you select the tag TI-100, the scroll key will toggle between the measured temperature and the cold junction
temperature (which should be room temperature in degrees Celsius).
16 - 5
Training Manual
16 - 6
17 Sequence Display Lab
17.1 Foreword
One of the features that set the MOD 30ML apart from other multiloop controllers is the ability to
construct custom displays for many types of applications, including sequential control.
17.2 Objectives
This lab is a continuation of the Supervisory Message lab and builds on that database. We will add
a display block to the BATCH compound and configure it to allow the operator to initiate the batch,
view the current step, the elapsed time in the step, and the batch temperature.
The diagram on the following page shows a simplified flowchart of custom display building:
17 - 1
Training Manual
Variables to display:
Lines 1 – 6
Bars 1 – 3
NO
YES
Key function(s) other
than standard?
Event-driven
YES Display
information
Script
changes?
Upon completing this lab you should have a basic understanding of how to:
17 - 2
Training Manual
17.3 Instructions
Make sure the database you constructed in the Sequence Lab and modified in the Supervisory
Message lab is loaded in ViZapp. You should be at the top level with the DIF, IF, ST, and SE
blocks visible along with the BATCH and TEMP CONTROL compounds.
The first step to creating a custom display is to plan what will appear on each line, and whether the
keys will perform different functions than the standard configuration (PID loop). In this particular
display some of the keys are not used at all.
For the purposes of this lab the display design has already been done. Study the Planning
Worksheet below to make sure you understand what the display will do.
STATE
DISPLAYS: TABLE? SCRIPT?
LINE 1 Current Step from Sequence Block Yes No
LINE 3 Blank No No
LINE 4 Blank No No
LINE 5 RUN or ENT when in Idle step, blank in all other sNo No
FUNCTION
Bar 1 Not used TAG Change displays (standard) No No
Bar 2 Not used MANUAL Not used No No
Bar 3 Not used AUTO Not used No No
R/L Not used No No
SCROLL ENT (enter) to start batch No No
UP/DN Changes between YES and NO on line 6 Yes No
17 - 3
Training Manual
State Tables serve as “lookup tables” for the Display Block, when a variable changes its value. For example,
each time the Sequence Block changes to a new step, the Display Block compares the step number to the
State Table and displays the appropriate text.
2. To show “NO” and “YES” on Line 6 when the sequence is in the Idle step, and the operator
pushes the UP or DOWN key to start the sequence.
2. Click on the Tables tab and use the scroll bar to scroll to the
bottom of the list of tables
3. Click in the blank space under the last table and press the
ENTER key on the keyboard twice, to add two lines
• Each State Table begins with a line that includes the You can comment the state tables by
table’s unique name; the maximum number of characters enclosing your text with /* */
(usually 8 or 3); and what should be displayed if none of
the conditions are met.
17 - 4
Training Manual
4. Create the table that will be associated with the Start Pushbutton
(StartPB) input.
Enter the state table as shown below:
6. Create the table that will cause the current step name to appear
on Line 1.
Enter the state table as shown below:
StepName,8,”????????” We will create an input to the Sequence
{ Display block and connected to the
1, “IDLE”; Sequence Block output “Step”. As the
2, “CHARGE”; value of this input changes, the text
3, “HEAT”; displayed on Line 1 will change
4, “COOK”; accordingly.
5, “COOL”;
6, “DRAIN”; The brackets, quotes and semicolons must
} be entered exactly as shown. This is the
syntax of the State Table block.
7. You can check the syntax of your entries by pressing the Any errors will be reported in the bottom
checkmark box in the toolbar of the State Table dialog box. panel of the ViZapp main window.
17 - 5
Training Manual
2. Select DISP from the Algorithms window and place it to the It is helpful to make the Display Block
right of the Sequence Block, below the Digital Output blocks. rather large in this case, to allow space for
Resize the block so it is a large rectangle. the inputs to be correctly and clearly
displayed.
Line 5: “RUN” (must enclose in quotes) On initial download the word RUN will be
displayed on Line 5.
Line 6: StartPB We will define an input called StartPB and
its status will be displayed here.
8. Click on the Add button The Specify Input Data dialog box opens
17 - 6
Training Manual
Name: StepTime
Data Type: Millisecond time
Internal Data: 0:00:00.000
14. Click on the Add button The Specify Format Data dialog box
appears
Entry method: Enter required The operator must push an Enter key.
When “Enter required” is specified, ENT
will appear on Line 5 when the arrow key
is pressed.
Display state table: Start The name of the table we defined in the
State Table block.
Entry state table: Start The name of the table we defined in the
State Table block. This will be used when
the operator is required to press the ENT
key.
Note that Display and Entry state tables may be the same, or
they can be different, so that a different set of text is shown when
the operator pushes a key for entry. If Entry Method is set to
None, an Entry state table is not required.
Name Format Type Low High Entry Method Display state Entry state Eng units
Limit Limit table table
StepL State None StepName
TempL Float1 0 100 None o
18. Type the following script into the Scripts window. Be sure to
exactly follow the punctuation.
17 - 8
Training Manual
DEFAULT:
#LINE5 = "";
#LINE6.SRC = blank;
}
}
}
19. You can check your script by clicking on the checkmark icon at Any errors will be reported in the bottom
the top of the dialog box panel of the main ViZapp window.
17 - 9
Training Manual
Since we have only one wired input we will modify the database to use it as the input to the PID temperature controller
and the Temperature input to the Sequence block.
17 - 10
Training Manual
2. Compile the database and fix any reported errors. When your The File Name for the MIF file should be
database compiles properly, in the Interface File dialog window SEQUENCE, which you created in a
check the first box under “Produce MIF” previous lab
3. Open the OPC server by clicking on the OPC Server icon on the
top toolbar
4. Make sure the correct Server Name, Server Node and Server are See the Extended Modbus OPC Server lab
selected for assistance
5. If you already have a Device configured, double-click to open If you do not already have a device
the Configuration menu. Make sure the Primary Port settings are configured see Chapter 4, Extended
correct. Modbus OPC Server, for assistance
17 - 11
Training Manual
6. In the Interface File Filename field, click on the Refresh icon A list of available MIF files appears
Refresh icon
9. Return to ViZapp and download the database to the controller The BATCH display should be on the
controller front panel.
As we do not have physical digital contacts to represent High Level and Low Level, we will simulate them from the
ViZapp Debug screen.
IDLE
00:00:00
RUN
NO
4. On the front face of the controller, push either the UP or DOWN Line 5 displays a flashing ENT and Line 6
button displays YES
17 - 12
Training Manual
5. Press the SCROLL key next to the flashing ENT (enter) If the display times out before you can
press Enter, simply press the UP or
DOWN key again.
9. Change the mode to Manual and set the Result to ON. The sequence enters the HEAT step
The controller changes to AUTO mode
with a setpoint of 90
10. Change the result back to OFF and the mode to AUTO, then
close the block.
11. Using the potentiometer, slowly raise the process temperature to When the temperature reaches or exceeds
90 90, the sequence enters the COOK stage.
12. On the controller, switch to the sequence display The top line shows COOK, and line 2
shows the time in step. When 20 seconds
has elapsed the sequence proceeds to the
COOL stage.
13. Switch to the PID-100 display on the controller. The setpoint should be 20.
14. Using the potentiometer, slowly decrease the temperature to 20 The sequence enters the DRAIN step and
the controller switches to Manual mode
with a setpoint of zero.
15. In the ViZapp database, open the LSL block. Change the mode The sequence goes to the IDLE step.
to MANUAL and set the result to ON.
17 - 13
Training Manual
17 - 14
18 Piecewise Linearization Lab
18.1 Foreword
In many applications it is necessary to use one or more X,Y lookup tables. MOD 30ML provides
multiple piecewise blocks with up to 60 x,y pairs which provide the lookup values for the
Linearization blocks. Tuning displays can be created which allow the user to enter the X,Y
coordinates from the front panel of the controller if desired.
The piecewise table block is a data only block. The table consists of two or more pairs of X, Y
floating point coordinates (up to 60 pairs). A piecewise table can be constructed for supporting a
linearization block or as a source of floating point recipe data. In addition, the X and Y coordinates
are tunable parameters.
In this lab we will configure a piecewise block and a linearization block, and use them to linearize
steam flow to a feedwater valve position, a typical requirement in a two or three-element boiler
drum level controller. We will also construct a simple operating display and create tuning displays
that will allow entry of new X,Y coordinates from the front panel.
18.2 Objectives
In this lab, we will create a very simple two-element drum level control strategy with a steam flow
input, a drum level input, and a feedwater flow output. We will also place a piecewise table block
and a linearization block in the strategy to adjust the output before it goes to the field. In Part II we
will load a simple operating display from the Component Gallery and modify the Tune List to
include the X,Y coordinates from the piecewise table so they will appear on the controller front face
when the Tuning password is entered.
NOTE: This lab assumes you have already completed all the standard ViZapp labs and you are
familiar with the methods of placing and connecting blocks and configuring the OPC server for
downloading to a controller.
18 - 1
Training Manual
18 - 2
Training Manual
18 - 3
Training Manual
7. Type STM/FW in the Name field and type a Description such as:
linearize steam flow to feedwater valve position
8. Click the Add button in the right of the PW Properties menu The Specify Point Data dialog box
appears
9. Click OK. The X and Y coordinates for the first point are added Since the actual values would almost
to the block. always change when the controller is
installed and commissioned, we will use
linear values for initial configuration.
10. Create 8 more points using the Add button, with the following
coordinates:
18 - 4
Training Manual
13. Type FW LN in the Name field and type a Description such as:
Feedwater valve linearization
18 - 5
Training Manual
17. Select the connection icon again and double-click on the A menu of possible connections appears
STM/FW piecewise block
19. Drag the cursor into the FW LN block and select the block
21. Return to EDIT mode by selecting the arrow on the right toolbar
Save and compile your database. It is not necessary to download at this time since we have not yet
constructed a display to view the coordinates.
18 - 6
Training Manual
3. Click the Export button to place the compound in your The resulting blocks overlay your original
workspace. strategy. This will be fixed in the next
steps!
5. Hold down the SHIFT key and select the TL and DISP blocks. Note that the connection line moves with
Move them to the right of your work area, away from the other the blocks.
blocks.
Your workspace should resemble this:
18 - 7
Training Manual
10. Drag the cursor over the DISP block and select it.
12. Make the following additional connections from the PID block to
the DISP block:
PID.PVI to DISP.process
PID.SP to DISP. setpoint
18 - 8
Training Manual
14. Click on the Inputs tab, then click the Add button at the bottom The tag browser dialog box appears.
of the TL Properties menu.
15. In the right column of the Browser, double-click LIC-100 All the attributes in the PID block appear
in the middle column.
16. While holding down the Ctrl key, select ACTION, BGAIN and This will allow adjustment of the
BRESET from the list in the middle column, then click the Add controller Gain, Reset, and output Action
button at the bottom of the dialog box. (direct or reverse) from the front panel.
18. Hold down the SHIFT key and click on X1, then Y9. All the X,Y attributes from 1 to 9 should
be highlighted
19. Click the Add button All the X,Y attributes are added to the
right window
18 - 9
Training Manual
20. Click OK to close the Browse dialog All the added attributes now appear in the
TL Properties Inputs tab.
21. Select the number 1 under Inputs and click on the Modify… You can also double-click the number 1
button at the bottom of the window
22. Make the following entries in the Specify Input Data window: The Display Format “Action” was
Display Format Name: Action predefined in the compound.
Line 2 Text: ACTION The first line of text will be the Display
Tag name (LIC-100)
Click OK to close the dialog box.
23. Enter the Input Data for Inputs 1 and 2 (Gain, Reset) as follows:
Input 2
Display Format Name: Gain
Line 2 Text: GAIN
Input 3
Display Format Name: Reset
Line 2 Text: RESET
24. Click on the Formats tab at the top of the TL Properties window
25. Click the Add button at the bottom of the window The Specify Format Data window appears
18 - 10
Training Manual
27. Click on the Inputs tab at the top of the TL Properties window
18 - 11
Training Manual
32. Connect the Result (R) of the FW LN block to the INPUT of the
Analog Output block.
34. Open the Display Interface Block (DIF) and add the tag LIC-100
to the Display Tag list.
35. Add an MSC block to the database and make sure it is set for
RS-232 Built In communications.
36. Compile the database and create a MIF file using a filename of
your choice, such as DRUM or LEVEL.
40. From the front panel of the controller, press and hold the Scroll
key. Enter the Tuning password, then scroll through the displays
to view the X,Y coordinate entry pages.
18 - 12
19 Reports Tutorial
19.1 Foreword
ViZapp Reports Builder application is used for creating different types of reports for the
Instrument database. It is a stand-alone application and can be run independent of the
ViZapp Application Builder. It supports the following functions:
• Report Creation
• Report Preview
• Report Printing
• Report Export to most common document types
19.2 Report Creation
The first step in creating reports is to export the Instrument document/configuration to an
MS Access database file. This can be done from the ViZapp Applications Builder.
The database reports are generated, by using preformatted templates. During report
creation, the templates are populated with data read from the exported database.
19.3 Instructions
19.3.1 To export instrument configuration to Access database:
Run the ViZapp application and open your instrument configuration. The instrument
configuration will be displayed in the workspace. Select Tools-Export from the menu bar
at the top. You will be prompted for a name for the exported database and its path as
shown in the figure below:
19 - 1
Training Manual
Reports Tutorial
Figure 19 .1.
ViZapp Database
Export
• Select the Windows Start menu and then Programs – MicroMod Automation -
ViZapp – ViZapp Reports. The ViZapp Reports application will start and
display the Welcome window as shown below:
Figure 19 .2.
Welcome dialog
• At this point, you can create a new report or open an existing report or cancel out
to go to the Reports Builder application. Let us create a new report.
• Click on the Create Report button on this Welcome window. The Report wizard
will be displayed as show in the next figure:
The Report Wizard can also be opened by clicking on the Create button on the tool
bar or by selecting File-Create Report from the menu bar.
• Select the database you exported from The Application Builder. Click on the Open
Database button on this Wizard.
19 - 2
Training Manual
Reports Tutorial
Figure 19 .3.
VIZAPP Reports
Wizard – Select
Database
• Select your database by choosing its path first and then by clicking on it. Click on
the Open button.
• This name of this database will be displayed in the Report Database field as shown
below.
• Click on the Next button to open the Create Report tab of the Wizard.
19 - 3
Training Manual
Reports Tutorial
Figure 19 .5.
VIZAPP Reports
Wizard – Select
Database
3. Select type of report: Click on the down arrow on the drop-down menu as shown in the
next figure and select Cross Reference Report.
Figure 19 .6.
VIZAPP Reports
Wizard – Create
Report
• Click on the Create Report button next to create the report you selected.
• After a few seconds, the name of the report that was created will be displayed in
the text box on the right hand side as shown below with a message above that.
19 - 4
Training Manual
Reports Tutorial
Figure 19 .7.
VIZAPP Reports
Wizard – Create
Report
• Notice that the name of this report has been derived from the database name.
“CRF” has been added to the end to indicate that this is a Cross Reference Report.
19 - 5
Training Manual
Reports Tutorial
• Click on the Open Report for Preview button on the wizard. The report will be
opened and shown in a child window on the main application window as shown in
the next figure:
Figure 19 .9.
Report Preview
• To print the report, click on the Print button on the tool bar or select Print-
Printer from the menu bar. The report will be printed to Windows default
printer.
You need to have a default printer defined in Windows. Otherwise you will get an
error message when you try to print. You can define a default printer by double-
clicking on the Printers icon in the Windows Control Panel.
• To print to a different printer, make it the default printer in the Printers dialog box
from the Windows Control Panel.
Refer to the following figure for help on different buttons on the tool bar. The same
actions with some more additional actions are also available from the menu bar at the
top.
19 - 6
Training Manual
Reports Tutorial
Figure 19 .10.
Tool bar buttons
• A Progress dialog (Printing Records) will be displayed while the report is printed.
Figure 19 .11.
Progress dialog
• Click on the Close button on the tool bar or select File-Close from the menu bar.
The report will be closed and the workspace will be blank as shown in the figure
above. The Report file field will be blank.
Figure 19 .12.
Close Report
19 - 7
Training Manual
Reports Tutorial
• Click on the Open button on the tool bar or select File-Open from the menu bar.
The Open Report dialog box will be displayed next as shown below:
Figure 19 .13.
Open Report
• Select the path and the report from this dialog box and then click on the Open
button to open he report.
The name and path of the report that is open at any time will be displayed in the
Report field of the Reports Builder application as shown below:
Figure 19 .14.
Report File
You can preview, print or export the opened report file only. Only one report can be
open at any time.
8. Formatting a Report:
• Only limited formatting such as adding a custom title and specifying date,
collation, is possible as the reports are already pre-formatted.
• To add a custom title for your report, select Print-Options from the menu bar. The
Reports Options dialog box will be displayed as shown in the next figure:
• You can also specify the number of copies on this dialog box. Type a title (type
your company name for example!) for the report and then click on either Print or
Preview.
19 - 8
Training Manual
Reports Tutorial
Figure 19 .15.
Print - Options
• A dialog box as shown below will be displayed. Click on YES to modify the report
with the custom title.
Figure 19 .16.
Format Options
• The report will be modified and will be previewed automatically with the custom
title. Refer to the figure below:
Figure 19 .17.
Format Options –
Custom Title
19 - 9
Training Manual
Reports Tutorial
• Note that the default report title is also shown on the report.
• There are some useful controls on the Preview window. Some of the important
controls on the preview are (Refer also to the next figure):
• Refresh - If you updated your database, you need not create the reports again. By
clicking on the Refresh button you can re-post data from the database.
• Zoom Control: You can custom zoom the preview by selecting the percentage
options in the zoom menu.
• Navigation buttons: These are used for going to the next/previous and first/last
page of the report.
• Close button: This is for closing the report preview window.
Figure 19 .18.
Format Options –
Custom Title
19 - 10
Training Manual
Reports Tutorial
Figure 19 .19.
Help
Reports can be exported to the following common document types using the Reports
Builder:
• Open the report you created (PIDLABCRF.RPT) from the File-Open dialog. You
can preview it by clicking on the preview button.
• Select Export from the menu bar or click on the Export button. The Export dialog
box as shown next will be displayed. Click on the down arrow on this dialog box.
Select Word for Windows from this menu and then click on OK.
19 - 11
Training Manual
Reports Tutorial
Figure 19 .20.
Report Export
• The Choose Export File dialog box will be displayed next as shown below: The
File Name for the export file is same as the report file, but has a different extension
(.DOC) and the path is same as that of the report file.
• You can choose a different path or different file name for the export file.
Figure 19 .21.
Export File
• Click on the SAVE button when done. You can now open this file in Word and
modify or print it.
13. View the About box: Click on the C button on the tool bar: The About box will be
displayed as in the next figure and display the version and copy right information. You
can also view details about your computer system by clicking on the System Info on this
dialog.
19 - 12
Training Manual
Reports Tutorial
Figure 19 .22.
About
19 - 13
Training Manual
Reports Tutorial
Notes:
19 - 14
Training Manual
APPENDIX A
ASSIGNMENT STATEMENT REFERENCE
A-1
Training Manual
A-2
Training Manual
A-3
Training Manual
Table A-2. Assignment statements of type 'display_resource = source_name' (ex. #LINE1 = I1)
Resource Format Displayed Result
#LINE1 Discrete: Integer1 0, 1
#LINE2 State Note 1
#LINE3 Short_State: Integer1 0 - 15
State Note 1
Long_State: Integer1 0 - 255
State Note 1
Count: Integer2 0 - 65535
State Note 1
Msec_time: Integer4 0 - 99999999 (0 - 99999999), first 8 digits (100000000 and up)
Time1 hh:mm:ss (00:00:00.000 to 99:59:59.999), hhhh:mm (100:00:00.000
and up)
Time2 m:ss.sss (0:00.000 to 9:59.999), mm:ss.ss (10:00.000 to
99:59.999),
hh:mm:ss (00:00:00.000 to 99:59:59.999), hhhh:mm (100:00:00.000
and up)
Time3 hhhh:mm
Time4 mm:ss.ss (10:00.000 to 99:59.999), hh:mm:ss (00:00:00.000 to
99:59:59.999),
hhhh:mm (100:00:00.000 and up)
Floating_point Floatn 0.0 - 99999999 (0.0 - 99999999.0), first 8 digits (100000000.0 and
up)
Date: Date mm/dd/yy or dd/mm/yy
Asc: Ascii truncated to 8 characters.
Hex: Hex leftmost characters discarded if more than 8.
#LINE3 Discrete: Integer1 0, 1
#LINE4 State Note 1
#LINE5 Short_state: Integer1 0 - 15
State Note 1
Long_state: Integer1 0 - 255
State Note 1
Count: Integer2 0 - 999 (0 - 999), First 3 digits (1000 - 65535)
State Note 1
Msec_time: Integer4 0 - 999 (0 - 999), first 3 digits alternate (1000 and up)
Time1 :ss (even if > 0:00:99.999)
Time2 sss (even if > 0:00:00.999)
Time3 :mm (even if > 0:99:59.999)
Time4 .ss (even if > 0:00:00.999)
Floating_point 0.0 - 999 (0.0 - 999.0), first 3 digits (1000.0 and up)
Date: /yy (right justified)
Asc: truncated to 3 characters
Hex: leftmost characters discarded if more than 3.
Note 1 If the source value is found in the state table, the associated mnemonic is displayed. Otherwise the
default mnemonic is displayed. All mnemonics in a state table have the same configured width. If not
entered full width, they are padded with trailing spaces during compile. If the mnemonic field is wider
than the display it is truncated to fit. Otherwise it (the entire field) is right justified.
A-4
Training Manual
Table A-2. Assignment statements of type 'display_resource = source_name' (ex. #LINE1 = I1)
Resource Format Displayed Result
#LBAR Discrete: None off, segment 1 on
#MBAR Bar 0 - 50 segments on (lo_limit - hi_limit), 50 segments on (> hi_limit)
#RBAR Dev
Short_state: None 0 - 15 segments on
Bar 0 - 50 segments on (lo_limit - hi_limit), 50 segments on (> hi_limit)
Dev
Long_state: None 0 - 50 segments on (0 - 50), 50 segments on (51 - 255)
Bar 0 - 50 segments on (lo_limit - hi_limit), 50 segments on (> hi_limit)
Dev
Count: None 0 - 50 segments on (0 - 50), 50 segments on (51 - 65535)
Bar 0 - 50 segments on (lo_limit - hi_limit), 50 segments on (> hi_limit)
Dev
Msec_time: None 0 - 50 segments on (00:00:00.000 - 00:00:00.050), 50 segments on
(00:00:00.051 and up)
Bar 0 - 50 segments on (lo_limit - hi_limit), 50 segments on (> hi_limit)
Dev
Floating_point None 0 - 50 segments on (0.0 - 50.0), 50 segments on (51.0 and up)
Bar 0 - 50 segments on (lo_limit - hi_limit), 50 segments on (> hi_limit)
Dev
DEV format is not valid for intensified segments and causes a 'INVALID DISP OP' diagnostic
#LISEGn Discrete: None off, segment 1 on
#MISEGn Bar off (< lo_limit), one of segments 1 - 50 on (lo_limit - hi_limit), segment 50 on
(> hi_limit)
#RISEGn Short_state: None off (0), one of segments 1 - 15 on (1 - 15)
Bar off (< lo_limit), one of segments 1 - 50 on (lo_limit - hi_limit), segment 50 on
(> hi_limit)
Long_state: None off (0), one of segments 1 - 50 on (1 - 50), segment 50 on (51 - 255)
Bar off (< lo_limit), one of segments 1 - 50 on (lo_limit - hi_limit), segment 50 on
(> hi_limit)
Count: None off (0), one of segments 1 - 50 on (1 - 50), segment 50 on (51 - 65535)
Bar off (< lo_limit), one of segments 1 - 50 on (lo_limit - hi_limit), segment 50 on
(> hi_limit)
Msec_time: None off (0), one of segments 1 - 50 on (00:00:00.001 - 00:00:00.050), segment 50
on (00:00:00.051 and up)
Bar off (< lo_limit), one of segments 1 - 50 on (lo_limit - hi_limit), segment 50 on
(> hi_limit)
Floating_point None off (0.x), one of segments 1 - 50 on (1.0 - 50.0), segment 50 on (51.0 and up)
Bar off (< lo_limit), one of segments 1 - 50 on (lo_limit - hi_limit), segment 50 on
(> hi_limit)
#LED Discrete: na off, on
#BEEPER Short_state: na off (0), on (1), system use (2 - 15)
Long_state: na off (0), on (1), system use (2 - 255)
Count: na off (0), on (1), system use (2 - 65535)
Msec_time: na off (00:00:00.000), on (00:00:00.001), system use (00:00:00.002 and up)
Floating_point na off (0.x), on (1.x), system use (2.0 and up)
A-5
Training Manual
Table A-3. Assignment statements of type 'display_resource = constant' - ex. #LINE1 = 37.94
Resource Constant Type Displayed Result
#LINE1 Discrete: 0, 1
#LINE2 Short_state: 0 - 15
#LINE6 Long_state: 0 - 255
Count: 0 - 65535
Msec_time: hh:mm:ss
Floating_point rounded to nearest storeable value (23 bit precision) and truncated to fit 8
characters.
Date: mm/dd/yy or dd/mm/yy
Asc: truncated to 8 characters.
Hex: leftmost characters discarded if more than 8.
#LINE3 Discrete: 0, 1
#LINE4 Short_state: 0 - 15
#LINE5 Long_state: 0 - 255
Count: 0 - 999 (0 - 999), First 3 digits (1000 - 65535)
Msec_time: :ss
Floating_point rounded to nearest storeable value (23 bit precision) and truncated to fit 3
characters.
Date: /yy (pretty useless)
Asc: truncated to 3 characters
Hex: leftmost characters discarded if more than 3.
#LBAR Discrete: off, segment 1 on
#MBAR Short_state: 0 - 15 segments on
#RBAR Long_state: 0 - 50 segments on (0 - 50), 50 segments on (51 - 255)
Count: 0 - 50 segments on (0 - 50), 50 segments on (51 - 65535)
Msec_time: 0 - 50 segments on (00:00:00.000 - 00:00:00.050), 50 segments on
(00:00:00.051 and up)
Floating_point 0 - 50 segments on (0.0 - 50.x), 50 segments on (51.0 and up)
#LISEGn Discrete: off, segment 1 on
#MISEGn Short_state: off (0), one of segments 1 - 15 on (1 - 15)
#RISEGn Long_state: off (0), one of segments 1 - 50 on (1 - 50), segment 50 on (51 - 255)
Count: off (0), one of segments 1 - 50 on (1 - 50), segment 50 on (51 - 65535)
Msec_time: off (0), one of segments 1 - 50 on (00:00:00.001 - 00:00:00.050), segment 50
on (00:00:00.051 and up)
Floating_point off (0.x), one of segments 1 - 50 on (1.0 - 50.x), segment 50 on (51.0 and up)
#LED Discrete: off, on
#BEEPER Short_state: off (0), on (1), system use (2 - 15)
Long_state: off (0), on (1), system use (2 - 255)
Count: off (0), on (1), system use (2 - 65535)
Msec_time: off (00:00:00.000), on (00:00:00.001), system use (00:00:00.002 and up)
Floating_point off (0.x), on (1.x), system use (2.0 and up)
#UPDN Discrete: off, up arrow on
Short_state: dn arrow, slash and up arrow show binary value (0 - 7), system use (8 - 15)
Long_state: dn arrow, slash and up arrow show binary value (0 - 7), system use (8 - 255)
Count: dn arrow, slash and up arrow show binary value (0 - 7), system use (8 - 65535)
Msec_time: dn arrow, slash and up arrow show binary value (0 - 00:00:00.007), system use
(00:00:00.008 and up)
Floating_point dn arrow, slash and up arrow show binary value of integer part (0.x - 7.x),
system use (8.0 and up)
A-6
Training Manual
Table A-4. Assignment statements of type 'display_resource.SRC = source_name' (ex. #LINE1.SRC = I1)
Resource Format Displayed Result
#LINE1.SRC Discrete: Integer1 0, 1
#LINE2.SRC State NOTE 1
#LINE3.SRC Short_state: Integer1 0 - 15
State NOTE 1
Long_state: Integer1 0 - 255
State NOTE 1
Count: Integer2 0 - 65535
State NOTE 1
Msec_time: Integer4 0 - 99999999 (0 - 99999999), first 8 digits alternate with 'OVERFLOW'
(100000000 and up)
Time1 hh:mm:ss (00:00:00.000 to 99:59:59.999), hhhh:mm alternates with
'OVERFLOW' (100:00:00.000 and up)
Time2 m:ss.sss (0:00.000 to 9:59.999), 'OVERFLOW' alternates with mm:ss.ss
(10:00.000 to 99:59.999),
hh:mm:ss (00:00:00.000 to 99:59:59.999), hhhh:mm (100:00:00.000 and up)
Time3 hhhh:mm
Time4 mm:ss.ss (10:00.000 to 99:59.999), 'OVF' alternates with
hh:mm:ss (00:00:00.000 to 99:59:59.999), hhhh:mm (100:00:00.000 and up)
Floating_point Floatn 0.0 - 99999999 (0.0 - 99999999.0), first 8 digits alternate with 'OVERFLOW'
(100000000.0 and up)
Date: Date mm/dd/yy or dd/mm/yy
Asc: Ascii = input, marqueed if necessary
Hex: Hex = input, marqueed if necessary
Note 1: If the source value is found in the state table, the associated mnemonic is displayed. Otherwise the
default mnemonic is displayed.All mnemonics in a state table have the same configured width. If not
entered full width, they are padded with trailing spaces during compile. If the mnemonic field is wider
than the display it is truncated to fit. Otherwise it (the entire field) is right justified.
A-7
Training Manual
Table A-4. Assignment statements of type 'display_resource.SRC = source_name' (ex. #LINE1.SRC = I1)
Resource Format Displayed Result
segment 1 remains on for source <= 0 to indicate bar is in use.
#LBAR.SRC Discrete: None segment 1 on
#MBAR.SRC Bar 1 - 50 segments on (lo_limit - hi_limit), 50 segments on (> hi_limit)
#RBAR.SRC Dev
Short_state: None 1 - 15 segments on
Bar 1 - 50 segments on (lo_limit - hi_limit), 50 segments on (> hi_limit)
Dev
Long_state: None 1 - 50 segments on (0 - 50), 50 segments on (51 - 255)
Bar 1 - 50 segments on (lo_limit - hi_limit), 50 segments on (> hi_limit)
Dev
Count: None 1 - 50 segments on (0 - 50), 50 segments on (51 - 65535)
Bar 1 - 50 segments on (lo_limit - hi_limit), 50 segments on (> hi_limit)
Dev
Msec_time: None 1 - 50 segments on (00:00:00.000 - 00:00:00.050), 50 segments on
(00:00:00.051 and up)
Bar 1 - 50 segments on (lo_limit - hi_limit), 50 segments on (> hi_limit)
Dev
Floating_point None 1 - 50 segments on (0.0 - 50.0), 50 segments on (51.0 and up)
Bar 1 - 50 segments on (lo_limit - hi_limit), 50 segments on (> hi_limit)
Dev
segment 1 remains on for source <= 0 to indicate bar is in use. DEV format is not valid for iseg's and causes
a 'INVALID DISP OP' diagnostic.
#LISEGn.SRC Discrete: None segment 1 on
#MISEGn.SRC Bar one of segments 1 - 50 on (lo_limit - hi_limit), segment 50 on (> hi_limit)
#RISEGn.SRC Short_state: None one of segments 1 - 15 on
Bar one of segments 1 - 50 on (lo_limit - hi_limit), segment 50 on (> hi_limit)
Long_state: None one of segments 1 - 50 on (0 - 50), segment 50 on (51 - 255)
Bar one of segments 1 - 50 on (lo_limit - hi_limit), segment 50 on (> hi_limit)
Count: None one of segments 1 - 50 on (0 - 50), segment 50 on (51 - 65535)
Bar one of segments 1 - 50 on (lo_limit - hi_limit), segment 50 on (> hi_limit)
Msec_time: None one of segments 1 - 50 on (00:00:00.000 - 00:00:00.050), segment 50 on
(00:00:00.051 and up)
Bar one of segments 1 - 50 on (lo_limit - hi_limit), segment 50 on (> hi_limit)
Floating_point None one of segments 1 - 50 on (0.0 - 50.0), segment 50 on (51.0 and up)
Bar one of segments 1 - 50 on (lo_limit - hi_limit), segment 50 on (> hi_limit)
#LED.SRC Discrete: NA off, on
#BEEPER.SRC Short_state: NA off (0), on (1), system use (2 - 15)
Long_state: NA off (0), on (1), system use (2 - 255)
Count: NA off (0), on (1), system use (2 - 65535)
Msec_time: NA off (00:00:00.000), on (00:00:00.001), system use (00:00:00.002 and up)
Floating_point NA off (0.x), on (1.x), system use (2.0 and up)
A-8
Training Manual
Table A-4. Assignment statements of type 'display_resource.SRC = source_name' (ex. #LINE1.SRC = I1)
Resource Format Displayed Result
#UPDN.SRC Discrete: NA off, up arrow on
Short_state: NA dn arrow, slash and up arrow show binary value (0 - 7), system use (8 - 15)
Long_state: NA dn arrow, slash and up arrow show binary value (0 - 7), system use (8 - 255)
Count: NA dn arrow, slash and up arrow show binary value (0 - 7), system use (8 -
65535)
Msec_time: NA dn arrow, slash and up arrow show binary value (0 - 00:00:00.007), system
use (00:00:00.008 and up)
Floating_point NA dn arrow, slash and up arrow show binary value of integer part (0.x - 7.x),
system use (8.0 and up)
A-9
Training Manual
A-10
Training Manual
APPENDIX B
DISPLAYED CHARACTER SET
The Application builder allows any character in the ASCII range of 0 to 127 (decimal 32 to 126 can be entered
through the normal keyboard characters). Of this set, many will display as blank or some other symbol. The
set usable from the instrument front face is indicated by a †. The table below shows the complete displayed
character set for the range 0 to 127.
CAUTION. The instrument does not check communications messages from other devices that may send
ascii data for display. If ascii data exceeds the valid range of 0 to 127, the display may behave erratically
or lock up. DO NOT USE ASCII DATA IN THE RANGE OF 128 TO 255 FOR DISPLAY!
0 19 38 &
1 20 39 '
2 21 40 (
(space
3 22 41 )
indicator)
4 23 42 † *
5 24 43 † +
6 25 44 ,
7 26 45 † -
8 27 46 .
9 28 47 † /
10 29 48 † 0
11 30 49 † 1
12 31 50 † 2
13 32 † space 51 † 3
14 33 ! 52 † 4
15 34 “ 53 † 5
16 35 † # 54 † 6
17 36 $ 55 † 7
18 37 † % 56 † 8
B-1
Training Manual
57 † 9 84 † T 111 † o
58 : 85 † U 112 † p
59 ; 86 † V 113 q
60 † < 87 † W 114 † r
61 † = 88 † X 115 † s
62 † > 89 † Y 116 † t
63 ? 90 † Z 117 † u
64 @ 91 [ 118 † v
65 † A 92 \ 119 † w
66 † B 93 ] 120 x
67 † C 94 ^ 121 y
68 † D 95 _ 122 z
69 † E 96 ` 123 {
70 † F 97 a 124 |
71 † G 98 † b 125 }
72 † H 99 † c 126 ~
73 † I 100 † d 127
74 † J 101 † e
† Standard faceplate character
75 † K 102 f
set.
76 † L 103 g
77 † M 104 † h
78 † N 105 i
79 † O 106 j
80 † P 107 † k
81 † Q 108 † l
82 † R 109 † m
83 † S 110 † n
B-2
Training Manual
Key Event
ALARM_PRESSED ALARM_HELD ALARM_RELEASED
TAG_PRESSED TAG_HELD TAG_RELEASED
MANUAL_PRESSED MANUAL_HELD MANUAL_RELEASED
AUTO_PRESSED AUTO_HELD AUTO_RELEASED
RL_PRESSED RL_HELD RL_RELEASED
SCROLL_PRESSED SCROLL_HELD SCROLL_RELEASED
UP_PRESSED UP_HELD UP_RELEASED
DOWN_PRESSED DOWN_HELD DOWN_RELEASED
Display Event
ENTRY ACTIVE EXIT
Constant:
#RBAR #RISEG1 #RISEG2 #RISEG3 #RISEG4
#MBAR #MISEG1 #MISEG2 #MISEG3 #MISEG4
#LBAR #LISEG1 #LISEG2 #LISEG3 #LISEG4
#LINE1 #LINE2 #LINE3 #LINE4 #LINE5 #LINE6
#LED #BEEPER #UPDN
Variable:
#RBAR.SRC #RISEG1.SRC #RISEG2.SRC #RISEG3.SRC #RISEG4.SRC
#MBAR.SRC #MISEG1.SRC #MISEG2.SRC #MISEG3.SRC #MISEG4.SRC
#LBAR.SRC #LISEG1SRC #LISEG2.SRC #LISEG3.SRC #LISEG4.SRC
#LINE1.SRC #LINE2.SRC #LINE3.SRC #LINE4.SRC #LINE5.SRC #LINE6.SRC
#LED.SRC #BEEPER.SRC #UPDN.SRC
C-1
Training Manual
C-2
Front Face Configuration
Map
NEXT
RUN DEV STAT SHUTDOWN DEV STAT COMMANDS DEV STAT XTIMES DEV STAT TIME
DEFAULT Shutdown Commands Execution times Time
HOLD SNWDOG 1 or COMMANDS CLR Q XTIMES T1 IMMED
SYSPI 1 xxxxxxxxx Clear Queue Scan 1 execution time DEV STAT DATE
Shutdown page 1 Date
COMMANDS CLR MT
Clear Maximum times DEV STAT DAY
COMMANDS ACK ALL Day
XTIMES T9 IMMED
SNWDOG 6 or Global Acknowledge Scan 9 execution time
SYSPI 6 xxxxxxxxx DEV STAT *DEVICE*
COMMANDS RESET XTIMES T1 FILTD Device status
Shutdown page 6
Reset Scan 1 Filtered time
COMMANDS KILL
Kill
COMMANDS DEL MAIN XTIMES T9 FILTD
Delete main database Scan 9 Filtered time
XTIMES T1 MAX
COMMANDS RES MAIN
Scan 1 Maximum time
Restore main database
COMMANDS DEV STAT
Commands
XTIMES T9 MAX
Scan 9 Maximum time
XTIMES BASE SCN
Base Scan time
XTIMES IDLE TM
Scan idle time
XTIMES DEV STAT
Execution times
A2_FrontFace_Config.ppt
This Page Left Intentionally Blank
Page 3
From TEMPLATE
EDIT
NEXT LOAD
INSTALL
TEMPLATE TEMPLATE DEFAULTS
SCAN GROUP 5
Scan group 5 interval DIAGNSTC BEEP
SYSTEM Diagnostic beep
SYSTEM PASWORDS MINIMUM LOW PRI
System passwords Minimum low priority
TUNE PASSWORD HIGH PRI RATE
Setup tune password High priority alarm rate
CONFIG PASSWORD HIGH PRI FLASH
Setup config password High priority alarm flash
ACCESS TIMEOUT HIGH PRI BEEP
Access timeout High prio alarm beep
SYSTEM LOW PRI RATE
SYSTEM ALARMS
System alarms
DIAGNSTC RATE
Diagnostic rate LOW PRI BEEP
DIAGNSTC FLASH Low priority beep
Diagnostic Flash SYSTEM
SYSTEM
A2_FrontFace_Config.ppt
This Page Left Intentionally Blank
Page 4
From page 3 (EDIT user compound) From page 5
NEXT (Alarms)
TAG ID
CMP TYPE SCAN GROUP PROCESS I/P SETPOINT
STRING To page 5
(CONTROL)
TAG ID STRING CTAG01 SCAN GRP CTAG01 PROC INP CTAG01 SETPT
Loop tag ID Scan group Process input Setpoint
PROC INP SLOT SETPOINT DISP FMT
CTAG01 CMP TYPE Process input slot PROC INP SPAN Display format
Compound type Span
PROC INP TYPE REMOTE SETPOINT
Type PROC INP RTD TYPE
CHANGE TYPE? RTD type
Change compound type PROC INP FILTER REMSETPT XXXXXXX
Filter PROC INP DISP FMT Remote setpoint inp
Display format
PROC INP LO SIGNL REMSETPT
Low signal PROC INP LO ENGU
Low engg units
PROC INP HI SIGNL LOCAL SETPOINT
Hi Signal PROC INP HI ENGU Local setpoint
High engg units
PROC INP LINEARZT SETPOINT RATIO
Linearization PROC INP EU LABEL Setpoint ratio?
Engg. unit label
PROC INP RES SETPOINT RATIO
RNGE PROC INP CJC SRC Setpoint ratio value
Resistance range Cold junction source
PROC INP NOM RES SETPOINT BIAS
Nominal resistance PROC INP BURNOUT Setpoint bias?
Burnout detection
PROC INP LW RES SETPOINT BIAS
PROC INP LO QUAL
Leadwire resistance Setpoint bias value
Low quality value
PROC INP TC TYPE SETPOINT BIALANCE RESTART SP VALUE
Thermocouple type PROC INP HI QUAL Setpnt Balance type Setpnt Restart value
High quality value
PROC INP ZERO SETPOINT LO LIMIT RESTART VALUE
PROC INP QUAL ALM Setpoint low limit
Zero Setpnt preset value
Quality alarm
PROC INP TEMPSCAL SETPOINT HI LIMIT INITIAL VALUE
Temperature scale PROC INP QA DOUT Setpoint high limit Setpnt initial value
Quality digital out
RESTART SP MODE SETPOINT TRACK
PROC INP QA PRI Restart Setpnt mode Setpoint tracking?
Quality priority
INITIAL SP MODE COMPOUND
PROC INP iNITIAL Setpnt mode
A2_FrontFace_Config.ppt
This Page Left Intentionally Blank
To page 4 (TAG ID)
Page 5
CONTROL OUTPUT ALARMS
From page 4
( SETPOINT)
A2_FrontFace_Config.ppt
The Company’s policy is one of continuous product improvement and the right
is reserved to modify the information contained herein without notice, or to
make engineering refinements that may not be reflected in this bulletin.
MicroMod Automation assumes no responsibility for errors that may appear in
this manual.
© 2010 MicroMod Automation, Inc. Printed in USA