MOD 30ML Training Manual

MOD 30ML Training Manual Training Exercises for MOD 30ML

MicroMod Automation, Inc.

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 injury or death.

Note. Clarification of an instruction or additional information.

i Information. Further reference for more detailedinformation or technical details.

Caution. An instruction that draws attention to the risk of the product, process or surroundings.

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. Licensing, Trademarks and Copyrights MOD 30 and MOD 30ML are trademarks of MicroMod Automation, Inc. MODBUS is a trademark of Modicon Inc. Health and Safety To ensure that our products are safe and without risk to health, the following points must be noted: 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.

All software, including design, appearance, algorithms and source codes, is copyrighted by MicroMod Automation, inc. and is owned by

MicroMod Automation or its suppliers.

MOD 30ML TRAINING MANUAL

Contents

Contents

FRONT FACE FAMILIARIZATION................................................................................ 1-1 OPERATION.................................................................................................................. 2-1 SINGLE LOOP TEMPLATE .......................................................................................... 3-1 DIAGNOSTICS .............................................................................................................. 4-1 VIZAPP SETUP ............................................................................................................. 5-1 PID LOOP ...................................................................................................................... 6-1 TUNE LIST..................................................................................................................... 7-1 EXTENDED MODBUS OPC SERVER .......................................................................... 8-1 DEBUG .......................................................................................................................... 9-1 PEER-TO-PEER .......................................................................................................... 10-1 EXPRESSION BLOCK ................................................................................................ 11-1 SEQUENCE ................................................................................................................. 12-1 SUPERVISORY MESSAGE......................................................................................... 13-1 PROCESS ALARM DISPLAY ..................................................................................... 14-1 TOTALIZER DISPLAY................................................................................................. 15-1 CJC AND DISPLAY..................................................................................................... 16-1 SEQUENCE DISPLAY................................................................................................. 17-1 PIECEWISE AND LINEARIZATION............................................................................ 18-1 REPORTS.................................................................................................................... 19-1

i

MOD 30ML TRAINING MANUAL Contents

ASSIGNMENT STATEMENT REFERENCE................................................................. A-1 DISPLAYED CHARACTER SET................................................................................... B-1 DISPLAY EVENTS & RESOURCES............................................................................. C-1 FRONT FACE CONFIGURATION MAP ....................................................................... D-1

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.3 Equipment Required You need the following equipment for this lab:

1. 1 x MOD30ML

1 - 1

Training Manual MOD 30ML Front Face Familiarization Lab

2. 1 x Memory module (2010PZ10000A) marked FACEPLATE (and loaded with the FACEPLAT.CDB file)

3. 1 x Small flat screwdriver

1.4 Instructions 1.4.1 Before you power up the instrument

Step Procedure Comments 1 Make sure the SERV/RUN switch

under the front face is set to the RUN position

This ensures that after a download the database will be able to run. 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

memory module are set to READ ONLY and NORMAL

This ensures that the database stored in the memory module is downloaded to the instrument during a power-up sequence. Normal = Transfers the database contained in the memory module to the instrument. Module Load = Transfers the database contained in the instrument to the memory module

3 Loosen the retaining screw and slide

the instrument from the housing CAUTION ! Ensure that the main circuit board is 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

housing and tighten the retaining screw

You should see ******** appear for a short while, then a flashing loop display with the tag FIC-100 and the alarm light.

1 - 2

Training Manual

MOD 30ML Front Face Familiarization Lab

1.4.2 Operating the alarm page and power-up sequence

Step Procedure Comments 1.

Press the Alarm Key

MEM MOD will appear on line 1 WRTPROT will appear on line 2 UAK and RET will appear on lines 3 and 4 UAK = Unacknowledged alarm RET = Return to loop display (Operating) The AUTO and MANUAL keys now function as Acknowledge and Return keys.

2.

Press the Auto key next to UAK.

Line 3 will change to ACT (Active) indicating that the alarm is still present. The flashing red alarm lamp indicates that other alarms are still unacknowledged.

3.

Press the Alarm Key

INST, PWR UP will appear on lines 1 and 2 UAK and RET will appear on lines 3 and 4

UAK = Unacknowledged alarm

RET = Return to loop display (Operating) 4.


Line 3 will change to CLR (clear) indicating that the alarm is no longer present, but the flashing red alarm lamp indicates that other alarms are still present.

5.

Press the Alarm key.

INST, PWR DOWN will appear on lines 1 and 2 UAK and RET will appear on lines 3 and 4

6.


Line 3 will change to CLR (clear) indicating that the alarm is no longer present, but the flashing red alarm lamp indicates that other alarms are still present.

7.

Press the Alarm key.

PROCESS LOW will appear on line 1 The actual process value appears on line 6 UAK and RET will appear on lines 3 and 4

Advantage: Alarm displays provide complete information, not just codes 8.


Line 3 will change to ACT (Active) indicating that the alarm is still present. The flashing red alarm lamp will change to constant illumination. This indicates that all alarms have been acknowledged and one or more is still active

9.

Press the R/L key next to RET (return)

The display will return to the FIC-100 operating display.

1 - 3


Note: Active Diagnostics

An unacknowledged diagnostic condition is always indicated by flashing of the alarm LED. The indication may also include a flashing display and a beep signal depending on configuration. A dedicated alarm display provides information on all active diagnostics. An example of the display with control key information is shown in the next figure. When the alarm light indicates an alarm condition, press the alarm key to access the alarm displays. Pressing the key repeatedly scrolls through a series of displays covering all unacknowledged alarms and acknowledged alarms that are still active. Unacknowledged diagnostics are always displayed first in the viewing sequence. See IB-1800R-OPR, Section 3 for more information.

Figure 1 .2. MOD 30ML Alarm Example

Abbreviated diagnostic message. [UAK] indicates that the alarm is active and has not been acknowledged. Press the ‘A' key to acknowledge the alarm. If alarm is still active [ACT] appears. If alarm is no longer active [CLR] appears, and this display is deleted upon exit. [RET] indicates that the R/L key can be pressed to return to the runtime displays. [7] is the Diagnostic event code number. [AOUT] [2] indicates the block type and number. Use the block type and event code number to locate a description of the diagnostic event in IB-23M601 Section 7.3. For example, code 7 for the [AOUT] block indicates an AOUT (module) error because the output circuit has reported an output-too-high or output-too-low error.

1 - 4

Training Manual


1.4.3 Operating the Loop display Left Bar will display the Process variable

Middle Bar will display the setpoint

Right Bar will display the control output

Line 1 will display the loop tag = FIC-100

Line 2 will display the process input and units = 0.00 GPM

Line 3 will display the control mode = MAN (manual)

Line 4 will display the setpoint mode = LOC (local)

Line 5 will indicate what value is displayed on line 6 = SP (setpoint)

Up/Down arrows indicate that the value on line 6 = / can be manually altered

Line 6 will display the value indicated by line 5 = 0.00 %

1.4.4 Operating the Auto/Manual key

Step Procedure Comments

1. Press the Auto key You will notice that line 3 changes to AUT and the UP/DOWN arrows disappear indicating that manual manipulation of the output is not possible.

2. Press the Manual key.

You will notice that line 3 changes to MAN and the UP/DOWN arrows reappear indicating that manual manipulation of the output is possible.

1 - 5

Training Manual MOD 30ML Front Face Familiarization Lab 1.4.5 Operating the Ramp keys

Objective: To manually set the control output to a value of 24.8%. During the following procedure, if the time between key strokes is greater then 10 seconds, then the display will automatically change back to the operating loop display. If this is the case, simply press either the UP or DOWN key and select the character you wish to change using the FST and SLO keys.

Step Procedure Comments 1. Press the UP or DOWN key The rightmost digit of line 6 starts to flash

Lines 3 and 4 (also flashing) are now displaying FST (fast) and SLO (slow) The AUTO and R/L keys now function as cursor movement keys for the digits on Line 6

2. Press the AUTO key, next to FST, 3

times

The cursor is now blinking under the blank space to the left of the output value _0.00%

3.

Press the UP key

2 times

The output value increments to 20.00%

4. Press the R/L key , next to

SLO, 1 time

The cursor moves to the second digit to the left of the decimal point 20.00%

5.

Press the UP key

4 times

The character increments to a value of 4.

6. Press the R/L key , next to

SLO, 1 time

The cursor moves to the first digit to the right of the decimal point 24.00%

7.

Press the UP key 8 times

The character will increment to a value of 8 and the output value is 24.80%

8.

Press the TAG key

This will stop the flashing and change the display back to the FIC-100 loop display. Don’t forget that the display will automatically change after 10 seconds of no key strokes.

Advantage: The operator can set the exact desired value with no overshoot

1 - 6

Training Manual


1.4.6 Operating the Scroll key

Step Procedure Comments 1. Press the SCROLL key

Line 5 changes to display SP (Setpoint)

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

3.

Press the UP key twice to change the bottom number to 2, and

then press ENT

The tuning password for this configuration is 2. FIC-100 appears on Line 1 GAIN appears on Line 2 The base gain value appears on Line 6. Dual arrows indicate the gain value may be changed.

4. Press the NXT key

RESET appears on Line 2 The base reset value appears on Line 6 (RPM = Repeats Per Minute). Dual arrows indicate the gain value may be changed.

Derivative is not configured for this strategy.


ACTION appears on Line 2 The control action, REVERSE, appears on Line 6. Dual arrows indicate the action may be changed.

Advantage: information which is useful during commissioning can be included on tuning

displays 6. Press the NXT key

PID TYPE appears on Line 2 The configured PID type, ESPO, appears on Line 6. This represents gain on Error, Standard reset, derivative on Process, manual reset OFF.

Advantage: information which is useful during commissioning can be included on tuning

displays 7.

Press the UP key when you reach the EXIT TUNING display

This returns you to the FIC-100 operating display.

1 - 7

Training Manual MOD 30ML Front Face Familiarization Lab 1.4.7 Checking the Communication setup

Objective: Determine the Modbus address and communication parameters of this instrument

Step Procedure Comments 1.

Press and hold the TAG key

Line 6 changes to display DEV STAT (device status). This is the start of the Status and Configuration menus. The Remote Local (R/L) and SCROLL keys now function as “previous” PRV and “next” NXT keys.

2. Press the NXT (scroll) key

SETUP appears on the bottom line, with a down arrow indicating there are sub-menus

3.

Press the DOWN arrow key

The top of the display indicates SETUP BI COMM (Set up built-in communications) with a down arrow indicating there are further sub-menus

4.

Press the DOWN arrow key

The top of the display reads BI MSC 1 ADDRESS (built-in Modbus serial port 1 address) and the Modbus address for the built-in communication port is shown on the bottom line.


The top of the display changes to BI MSC 1 BAUDRATE and the baud rate is shown on the bottom line. Dual arrows indicate that the baud rate may be changed. Change the baud rate to 38400


The top of the display changes to BI MSC 1 PARITY and the parity is shown on the bottom line. Dual arrows indicate that the parity may be changed, however, for most applications you should leave this at default of NONE.


The top of the display changes to BI MSC 1 STOPBITS and the number of stop bits is shown on the bottom line. Dual arrows indicate that the number of stop bits may be changed, however, for most applications you should leave this at default of 1.


The top of the display changes to BI MSC 1 ENABLED. This tells you that the Modbus communications have been enabled. This occurred during the download.

9. Press the TAG key

This will return you to the beginning of the device status displays

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


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:

• integration of automatic sequential and continuous control

• front panel display of sequence steps

• cascade control

• front panel recipe selection and entry of recipe data

• manual control of sequence steps through front panel

2.2.1 The Control System The batch reaction is conducted according to a definite time-temperature cycle. The next figure illustrates a typical cycle of many industrial processes.

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 MOD 30ML Operation Lab 2

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

MOD 30ML Operation Lab 2

• Manual advance of sequence

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


2.3 Instructions 2.3.1 Download Reactor database from the memory module:













You should see ******** appear for a short while, then a display as shown in the next figure should appear.

Figure 2 .3. Batch main display

2 - 4

Training Manual


2.3.2 Scroll through the displays:

Step Activity Look For 1 The first display as shown in the

previous page is the main batch display. This is the display where we will start the batch. But before that, we will scroll through the other displays to get an overview.

Note that the batch is in AUTO mode and is not running right now (OFF). The setpoint is in local (LOC) mode.

2 Press the TAG key once to go to the

TIC-100 temperature control loop display. See the next figure. Read the temperature of the product. Read the output. Press the SCROLL key to show the setpoint at the bottom. Press the TAG key again to go to TIC-101 control loop display. See the next figure. Read the process, setpoint and output values. Press the TAG key to go to the next display. See the next figure.

This is the Master temperature controller. Master temperature controller TIC-100 setpoint 100ºF. This is the Slave temperature controller. Slave temperature controller TIC-101 setpoint 200ºF. Setpoint is in Remote mode (REM). Its value is same as the output value of the TIC-100 loop. This display shows the Flow rates of Product A and B and also the Level value in inches. Product A and B flow 0 GPM Level in vessel 0.0” H2O

Figure 2 .4. TIC-100, TIC-101 and Flow/Level Displays

2 - 5


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 and TIC-101. First switch to the control display (TIC-100 or TIC-101) and then hold down Scroll key to access the tuning display.

Tuning displays for controller algorithm type, controller action, gain, reset Commissioning activity can take place through front panel of instrument.

4 Display recipe selection by returning

to main batch display and holding down scroll key. Enter tuning password of 1 (if required; the tuning password from the previous activity may still be in effect) Select recipe 1 using UP/DOWN arrows and press ENT (Scroll key). Press NXT key to view recipe parameters Change Recipe 1 target level to 15 inches water. See the next figure.

This is a tuning display within the main batch display to select and change the recipe for the batch. Once tuning password is entered the recipe can be scrolled between the choices of Recipe 1 and Recipe 2 You can view and change the following parameters: Reaction temperature setpoint entry, Reactor level, Fill A rate, Fill B rate

Figure 2 .5. Recipe Tuning display

2 - 6

Training Manual


2.3.4 Run the Batch:

5 Press the TAG key to return to main Batch display Press AUTO key to start the batch See the next figure.

Batch status changes to RUN Setpoint status changes to REMOTE Step indication on Line 6 changes to START and then to FILL.

Figure 2 .6. Batch main display

6 Scroll to fill display See the next figure:

Fill A and Fill B flow rates displayed on lines 1 and 2, left and middle bar Reactor level displayed on Line 6 and right bar

Figure 2 .7. Batch Flow/Level display

2 - 7


7 Return to main batch display and

observe step.

8 When controller has entered

HEATUP step, scroll to temperature control displays (TIC-100 and TIC-101) Read the process value of TIC-100. Refer to the next figure.

Cascade control for temperature is now active Master controller setpoint value ramps to 111ºF. This will also ramp to 111 def F in a couple of minutes

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


2.3.5 Switch the batch control modes:

9 When batch cycle has entered HOLD step, return to main batch display Press MAN key to put batch cycle in manual control

Batch status on line 2 changes to MANUAL. STP indication appears next to Scroll key

Figure 2 .9. Batch in Hold

10 Press STP key (scroll key) to scroll

to COOLDOWN Press MAN key again to return batch cycle to automatic control

Batch time shows on line 2. Batch resumes automatic control in COOLDOWN step

Figure 2 .10. Cool Down Step

2 - 9


11 Scroll to TIC-100 display Temperature setpoint ramping down to cool setpoint

12 When batch cycle has entered

DRAIN cycle, scroll to level display Falling reactor level as vessel is drained

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 step to OFF, and press the AUTO key to return the batch to OFF status. Press the MAN key again to change to automatic mode.

The display will look like the initial display as shown in Figure 2 .3. The batch can be repeated now.

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. Sample Flow PID Loop

F E

F T

F Y F C

F C V

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 Single Loop Template Lab

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.

2. Power-up Instrument if it is not already powered up.

3.3.2 Acknowledge Alarms: 3. Press ALARM key. This will list all unacknowledged and active acknowledged alarms and

diagnostics that are currently present in the controller.

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

Single Loop Template Lab


CLeaRed Alarm

• The next figure shows an active alarm.


ACTive Alarm (Acknowledged, but still active)

3 - 3

Training Manual Single Loop Template Lab 3.3.3 Front face Configuration Map:

The front face configuration map shows an overview of the menus available front the front of the MOD 30ML controller. The major menu items at the top level can be scrolled through, by selecting NXT from the front face while DEVICE is displayed on line 1.

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.)

• INSTSATE – Read and change instrument state

• SHUTDOWN – Read and acknowledge the instrument shut down

• COMMANDS – Issue commands like acknowledge alarms, clear event queue, delete and restore main database etc., to the controller

• XTIME – Read the scan times

• TIME – Read and setup the real time clock of the controller

• DATE – Read and setup the real time date of the controller

• DAY – Read and setup the real time day of the week of the controller

2. SETUP – This menu is further divided into the following sub menus

• BI COMM – Setup built-in communication port parameters and instrument address

• PASSWORD – Setup configuration and tuning password for the controller

3. I/O – Read I/O and change outputs

4. EVENTS – Read and clear system event queue

5. ABOUT – Read the controller and display firmware revision levels

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


3.3.4 Scroll through the top level front face menus: Step Procedure Comments 1 Press and hold TAG key until

*DEVICE* is displayed on line 1. See the figure below:

2 Press the NXT (the key next to the

NXT display on the front face). See the menu items changing in line 6.

3 If you pressed any other key and do

not know where you are, press and hold the TAG key until *DEVICE* is displayed at the top.

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*

is displayed on line 1. See the figure below:

DEV STAT will be displayed on line 6. DEV STAT provides access to State Commands, Shutdown information and acknowledgment, Status Commands, Execution Times and Current Time, Date and Day.

2 Press DOWN key once. If PASSWORD is

not displayed on line 2, go to step 6. Otherwise continue with Step 3.

Figure 3 .5.

3 Use UP key three times to select the PASSWORD and then use ENT to enter.

Lines 1 and 2 will display CURRENT LEVEL and Line 6 will display CONFIG indicating that the controller is in configuration mode.

3 - 5


4 Press ENT again to enter

Configuration mode. You will be in DEV STAT menu mow. See the sequence of figures below:

Lines 1 and 2 will display DEV STATE and INSTATE (Instrument state). Line 6 will display RUN indicating that the controller is running a valid database.

5 Press the NXT key until COMMANDS is

displayed on line 2. You can issue commands to the controller from this menu.

Figure 3 .6.

6 Press the DOWN key once. 7 Press NXT key until ACK ALL is

displayed on line 2. Used for sending global acknowledge command causing all diagnostics, alarms and notification /request messages to be acknowledged.

8 Clear ACK ALL by pressing the DOWN

key. YES will be displayed on line 6.

9 Press the ENT key. Press NXT key RESET is used to complete tasks and then

perform a power-up 10 Press NXT key KILL is used to perform an immediate power-up 11 Press NXT key DEL MAIN will be displayed on Line 2. 12 Delete Main database by pressing the

DOWN key, then press the ENT key DEL MAIN is used to mark the main database as 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

pressing the ALARM key and the AUTO key.

The Alarm display will show INST UNCONFIG saying that the instrument is unconfigured.

14 Press RET key 15 If line 2 displays DEL MAIN go to

Step 17 otherwise continue at step 16. If the instrument state has not changed, you will 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.

16 Press DOWN and NXT key 2 times.

Press DOWN key again. Press NXT key 5 times.

Line 2 should now display DEL MAIN

17 Press NXT key RES MAIN is displayed on Line 2. This is

“Restore Main Database” which can be used to “upload” what is in the running database and restore it to the configuration database.

3 - 7


Figure 3 .8.

18 Press NXT key, then press the UP

key You are exiting the COMMAND section

19 Press NXT key XTIMES is displayed on Line 2. Scan groups 1

through 5 are user-defined intervals for loops. The fastest group has the highest priority. The lower numbered group has a higher priority if the interval is the same. Scan group 6 is a system group. Scan groups 7 to 9 are communications groups.

20 Press NXT key TIME is displayed on Line 2. Current time. The

instrument maintains this time even when off. Always keep set to current time

21 Press NXT key. DATE is displayed on Line 2. Current date. The

instrument maintains this date even when off. Always keep set to current date

22 Press NXT key DAY is displayed on Line 2. Current day (Sunday

= 1, Saturday = 7). The instrument maintains this day even when off. Always keep set to current day.

23 Press NXT key DEV STAT is displayed on Line 1 and DEVICE is

displayed on Line 2. 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


3.3.6 System Compound – Load Defaults:

1 Press NXT until TEMPLATE is displayed on

line 6. See figure below:

2 Press DOWN LOAD DEFAULTS will be displayed on lines 1 and 2.

We use the default template as a starting point for creation of a database. Default values are the basis for what is shown in the Operation manual.

3 Press DOWN “VERIFY LOAD” will be displayed on lines 1 and 2

Figure 3 .9.

4

Answer YES by pressing DOWN and ENT Defaults are the safe or most commonly used values.

5 Press PRV TEMPLATE is displayed on lines 2 and 6 as shown in

the figure below. 6 Press DOWN EDIT TEMPLATE appears on lines 1 and 2

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.

7 Press DOWN CMP LIST *SYSTEM* will be displayed on lines 1 and 2. See the third picture in the figure below. We are at the System Compound now.

3 - 9


Figure 3 .10.

3.3.7 System Compound – Edit System Template: We will change the System tag name and the system scan group 2 scan interval in this section.

1 Use the Arrow keys to scroll through INSERT, EDIT, and LIST. DO NOT PRESS ENTER

INSERT is used to add a user compound after system compound. 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,

press ENT We will now edit the system compound to 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

change the Tag to CLAS6000:

Modify device tag using standard set of characters. This tag identifies instrument itself, not the individual loops in the instrument

4 Use the arrow keys to make the first

character display a C

5 Press NXT to access the second

character

Continue on with this sequence until you have CLAS6000 displayed

See the next figure.

6 Press ENT

3 - 10

Training Manual


Figure 3 .11.

.

7

Press NXT to access System Scan Groups.

Scan groups defined update intervals for loops.

8 Press DOWN SYSTEM SCANGRPS should be displayed on lines 1 and 2. See the figure above. The arrow key will change the Scan Group time by 50 mSec steps. Scan groups 1 through 5 are user defined intervals for loops Leave at 0:00.100. The fastest group has the highest priority. The lower numbered group has a higher priority if the interval is the same

9 Press NXT SCAN GROUP 2 will be displayed on lines 1 and

2. 10 Press UP to select 0:00.300 All loops included in Scan Group 2 will

execute every 300 milliseconds 11 Press ENT 12

Press NXT until SYSTEM is displayed in line 1, Lines 2 and 6 are blank and the UP arrow is on.

13 Press UP System (Tasks Exit) 14

Press NXT SYSTEM PASWORDS on Lines 1 and 2.

3 - 11


We will change the system tune and configuration passwords in this section.

1 Press DOWN TUNE PASSWORD is displayed on lines 1 and 2. 2 Press UP key to set 1 as password then

press ENT. Enter a number required to access tuning parameters.

3 Press NXT CONFIG PASSWORD is displayed on lines 1 and 2. 4 Press UP arrow to set 2 as Configure

password. Press ENT This was a password established which is required to access configuration parameters

5 Press NXT 6 ACCESS TIMEOUT is displayed on

Lines 1 and 2. 0-54 minutes; 0=infinite. The time in minutes that the tune and configure access levels will timeout and return to the operate level after last keyboard activity.

7 Press UP to change line 6 to the number

5. Press ENT This will give us 5 minutes before the tune and configure access levels will timeout and return to the operator level after the last keyboard activity.

Figure 3 .12.

8 Press NXT 9 Press UP System (password exit) 10 Press NXT SYSTEM ALARMS displayed on lines 1 and 2

3 - 12

Training Manual


Next, we will change some of the system alarm settings.

1 Press DOWN DIAGNSTC RATE is displayed on lines 1 and 2. FAST = off 100mSec, on 300 mSec. SLOW = off 250mSec, on 750mSec. We will accept the FAST rate. Alarm indication rates apply to light, display and beeper. Alarms are: unacknowledged diagnostics, high or low process and deviation conditions, and input quality

2 Press NXT DIAGNSTC FLASH is OFF.

OFF = flashing is disabled. ENABLE = flash display (LED always flashes for diagnostic).

3

Press NXT. DIAGNSTC BEEP is OFF OFF = beeping is disabled. ENABLE = beep for diagnostic.

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.

6 Press NXT HIGH PRI RATE is FAST.

FAST = off 100mSec, on 300 mSec SLOW = off 250mSec, on 750mSec

7 Press NXT 8 Set HIGH PRI FLASH to ENABLE and press

ENT OFF = flashing is disabled ENABLE = flash display on alarm

Figure 3 .13.

3 - 13


9 Press NXT HIGH PRI BEEP is OFF. OFF = beeping is disabled ENABLE = beep on alarm

10 Press NXT LOW PRI RATE is SLOW.

FAST = off 100mSec, on 300 mSec SLOW = off 250mSec, on 750mSec

11 Press NXT LOW PRI FLASH is OFF 12 Press NXT LOW PRI BEEP is OFF. 13 Press NXT SYSTEM appears on line 1; Lines 2 and 6 are

blank 14 Press UP End of SYSTEM ALARMS 15 Press NXT End of SYSTEM functions. 16 Press UP Return to System List 17 Press NXT CMP LIST CTAG01 is displayed on lines 1 and 2.

LIST is displayed on Line 6.

3 - 14

Training Manual


3.3.8 Single Loop PID control template setup: When you loaded defaults, you automatically created a “blank” loop tag which was given the name CTAG01. We will now edit this loop.

1 Press UP arrow twice to select EDIT on

line 6 and press ENT TAG ID STRING on lines 1 and 2. CTAG01 on line 6.

2 Press UP arrow to change tag

characters. While display is flashing, press UP until F is displayed

DO NOT PRESS ENTER

3 Press NXT . 4 Press DOWN until the I is displayed as

the second character

5 Press NXT 6 Use the arrow keys to make the third

character display a C.

7 Press NXT

Figure 3 .14.

8 Continue on with this sequence until you

have FIC-100 displayed, then press ENT. Pressing ENT will enter the new tag name in the database

9 Press NXT FIC-100 is displayed on line 1. SNGLLOOP is

displayed on line 6. We will accept SINGLELOOP as our controller type for this lab.

10 Press NXT SCAN GRP 1 will be displayed on lines 2 and 6. This is the scan group to which this loop will be assigned.

3 - 15


11 Press the UP key, then ENT to change

loop to Scan Group 2

Figure 3 .15.

3 - 16

Training Manual


3.3.9 Process Input Setup

1 Press NXT PROC INP will be displayed on line 2. We are entering the process input setup for our PID control loop.

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

accept this. This is Built-In Analog Input 1. Inputs may be defined as NONE, BI AIN 1, BI AIN 2 or module slot S01- to S11- for input being configured

4 Press NXT INP TYPE will be displayed on line 2.

Figure 3 .16.

5 VOLTS is the default for the process input. Press UP and then ENT to change this to CURRENT.

Input types may be defined as: VOLTS, MVOLTS, CURRENT, RESIST, THRMOCPL 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

keys to change the low signal range to 4 Built-in analog input 1 is wired to a pot in the demonstration unit which has a range of 0 to 6 Volts

8 Press NXT HI SIGNL is displayed on line 2 9 Use the UP and FST keys to change the

high signal range to 20 and press ENT

10 Press NXT until HI ENGU is displayed on

line 2

11 Use the UP/DOWN keys and the FST Pressing the Up key, will cause the Least

3 - 17


key to set the range at 200. Then press ENT

Significant Digit to flash, indicating you can 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.

12 Press NXT EU LABEL will be displayed on line 2.

Figure 3 .17.

13 Using the UP/DOWN keys and NXT key, spell out GPM Then press ENT

Up to a 4 character label to appear after process input value. First character entered becomes leftmost character

14 Press NXT LO QUAL is displayed on line 2 15 Using the UP/DOWN keys enter -20.0 as

low quality limit. Then press ENT Result is set BAD if it goes below this value.

Figure 3 .18.

3 - 18

Training Manual


16 Press NXT HI QUAL is displayed on line 2. Result is set BAD if it goes above this value. High quality must be higher than the low quality value

17 Set line 6 at 220. Then press ENT 18 Press NXT until line 2 and 6 are blank

and only the up arrow is on

19 Press UP 20 Press NXT This completes the Process Input section. SETPT

will be displayed on line 2.

Figure 3 .19.

3 - 19

Training Manual Single Loop Template Lab 3.3.10 SETPOINT Setup

1 Press DOWN to enter setpoint section. 2 Press NXT until SETPOINT HI LIMIT is

displayed on lines 1 and 2. Setpoint values to the PID algorithm are limited to this number or below

3 Set the high limit at 200. Then press

ENT.

4 Press NXT until INITIAL VALUE is

displayed.

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

and only the up arrow is on. COMPOUND will be displayed on Line 1

7 Press UP This completes the Setpoint section 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


3.3.11 CONTROL Setup

1 Press DOWN to enter control section. This takes you down into the Control menus 2 ALGO TYP is displayed

on line 1. What is the ALGO TYPE ?

Gain (1st Character): O = Off P = On Process E = On Error

Reset (2nd Character): O = Off S = Standard M = Micro-Scan

Pre-Act (3rd Character): O = Off P = On Process E = On Error

Manual Reset (4th Character): O = Off E = Enabled

Figure 3 .21.

Figure 3 .22.

3 - 21


3 Press NXT until “GAIN” is displayed on line 1. Set Gain at 0.65. Then press ENT.

0.01 to 125.0 Proportional response in a fixed gain controller.

4 Press NXT, set Reset at 30.00 then

press ENT 0.01 to 125.0 Reset in repeats per minute.

5 Press NXT until INITIAL MODE is

displayed on lines 1 and 2.

6 Set Mode to AUTO. Then press ENT 7 Press NXT until lines 2 and 6 are blank

and only the up arrow is on. COMPOUND will be displayed on Line 1

8 Press UP. This completes the Control section 9 Press NXT This takes you to the OUTPUT section of the

configuration tree.

3 - 22

Training Manual


3.3.12 OUTPUT Setup

1 Press DOWN to enter output section 2 Leave the default value of BI1 AOUT in

place NONE, BI1 AOUT, BI2 AOUT, and 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 displayed

PID output limited to this number or above.

6 Set limit to 0.0. Then press ENT 7 Press NXT, OUTPUT HI LIMIT displayed PID output limited to this number or below.

3 - 23


Figure 3 .24.

8 Set limit to 100.0 and

press ENT

9 Press NXT until Line 2 displays OUTPUT

INIT VAL This is the initial value of the output on download

10 Change the initial value to 50 11 Press NXT until COMPOUND is displayed on

line 1

12 Press UP This completes the output section. 13 Press NXT This takes you to the ALARM section of the

configuration tree. We will not setup any process alarm in this lab.

14

Press NXT COMPOUND is displayed on line 1 and LIST on line 2.

3 - 24

Training Manual


3.3.13 Install the edited template

1 Press UP CMP LIST FIC 100 is displayed on lines 1 and 2. 2 Press NXT CMP LIST is displayed on line 1; lines 2 and 6 are

blank 3 Press UP EDIT TEMPLATE displayed on lines 1 and 2. 4 Press NXT INSTALL TEMPLATE displayed 5 Press DOWN. Select INITWARM INSTALL TYPE displayed. 6 Press ENT This compiles your configuration and loads it into

runtime memory. You should now see the FIC-100 display. Line 2 will display the process variable and the EU (GPM). Line 6 will display the output (50%)

7 Press the SCROLL key to see the Setpoint at the bottom.

8 Operate your PID loop by changing the

output, setpoint and also by getting into TUNING mode and by changing the GAIN and RESET values.

Refer to the MOD 30ML Operation Lab 1 for more information on operating the PID loop.

Figure 3 .25.

3 - 25


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.

4.3 Equipment Required You need the following equipment for this lab:

1. 1 x MOD30ML

2. 1 x Memory module (2010PZ10000A) marked SHUTDOWN (and loaded with the SHUTDOWN.CDB file)

3. 1 x Small flat screwdriver

4 - 1

Training Manual MOD 30ML Diagnostics Lab

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.

Step Procedure Comments 1 Press and hold the TAG key for a

few seconds The Device Status display as shown in the next figure (1) will be displayed.

2 Press NXT repeatedly until the Device

Events display appears. See the figure in the middle.

3 Press down arrow to enter the event

queue. Page 1 for the first event in the queue appears (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 page 2 for the first event

See the first picture in the next figure. Notice that 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).

5 Press the up arrow to return to Page 1 of this event will be displayed.

4 - 2

Training Manual

MOD 30ML Diagnostics Lab

page1 6 Press NXT to display the next event in

the queue. Page 1 of the next event will be displayed next.

7 Use the block type and event code,

to locate the event description and recommended action listed in Section 7 of the Maintenance manual.

Pressing the DOWN arrow will display the time at which the event occurred and line 6 will display the nature of this event – in this example, the “INST IN RUN” is the event and it means that the instrument 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

the queue. Page 1 of the next event will be displayed next.

9 Use the block type and event code,

to locate the event description and recommended action listed in Section 7 of the Maintenance manual.

Pressing the DOWN arrow will display the time at which the event occurred and line 6 will display the nature of this event – in this example, the “INST IN RUN” is the event and it means that the instrument was put in RUN mode. This is an information only type event and line 6 displays “INFOONLY”

10 Continue using the NXT, Down, Up

sequence to view all the event data in the queue.

11 Press the TAG key to return to the

DEVICE/EVENTS display.

4 - 3

Training Manual MOD 30ML Diagnostics Lab 4.3.2 Clearing events from the event history:

The controller can store up to a maximum of 1000 events in its queue. The default queue size is 50 events and is configured in the SE (System Event) block of the database. You can configure what goes in to the queue. By default, the following are entered in the event list: (see the next figure)

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.

We will clear the instrument’s event queue in this section:

Step Procedure Comments 1 Press and hold TAG key until

*DEVICE* is displayed on line 1. See the next set of figures.

The Device Status display will be displayed. DEV STAT will be displayed on line 6. DEV STAT provides access to State Commands, Shutdown information and acknowledgment, Status Commands, Execution Times and Current Time, Date and Day.

4 - 4

Training Manual


2 Press DOWN key once. If PASSWORD is not displayed on line 2, go to step 5. Otherwise continue with Step 3.

3 Use UP key three times to select the

PASSWORD and then use ENT to enter. See the next set of figures

Lines 1 and 2 will display CURRENT LEVEL and Line 6 will display CONFIG indicating that the controller is in configuration mode.

4 Press ENT again to enter

Configuration mode. Lines 1 and 2 will display DEV STATE and INSTATE (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

displayed on line 2. You will be in DEV STAT menu mow. See the sequence of figures below: You can issue commands to the controller from this menu.

Figure 4 .5.

4 - 5


6 Press the DOWN key once. CLR Q is displayed on line 2. 7 Press the UP arrow. YES will be displayed. 8 Press ENT (SCROLL key). The Events queue will be cleared and line 6 will

display NO again. 9 Press the TAG key. The DEVICE page will be displayed. 10 Pres the TAG key again. Your runtime display will be displayed.

4 - 6

Training Manual


4.5 Instrument Shutdown 4.5.1 Force a shutdown













You should see ******** appear for a short while, then a flashing loop display with the tag SD -100 and the alarm light.

Figure 4 .6.

6 Acknowledge alarms if any and

press the TAG key to go to the SD-100 display.

This database is configured with most of the diagnostic alarms suppressed (turned off). 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


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

and wait for a few seconds. The runtime PID display will disappear and FAILURE 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


4.5.2 Read the shutdown information and acknowledge it:

Step Procedure Comments 1 The first step in reading the

shutdown info is to cycle power the controller. Power down the controller and then power it.

After power up the DEVICE display will come up. The instrument will be in default mode and Line 3 will display DEF as shown in the first figure below. There will be diagnostic alarms and the RED LED will be flashing.

2 View the diagnostic alarms by

pressing the ALARM button. Acknowledge the alarms by pressing the button next to UAK on the display. Go to the next alarm by pressing the ALARM button again.

The diagnostic alarms that come up after an instrument shut down are:

1. Instrument Power up 2. Instrument SHUTDOWN 3. Spurious Interrupt

Refer to the following figures

Figure 4 .7.

Figure 4 .8.

4 - 9


3 Press the TAG button after viewing and acknowledging the alarms.

The instrument will display the DEVICE display. Line 6 will show DEV STAT. See the middle picture in the next figure.

4 Press the DOWN arrow to enter the

DEV STAT menu. The first page in this menu shows the Instrument’s 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

SHUTDOWN page. Line 2 will display SHUTDOWN and line 6 will display YES. This indicates that a Shutdown condition exists. See the above figure.

6 Press the DOWN arrow to view

details of the shut down. Record this shutdown information on the form at the end of this chapter.

The Shutdown information is provided in the next 4 pages (displays). Page 1 of the SHUTDOWN info as shown in the next figure.

Figure 4 .10.

4 - 10

Training Manual


7 Press the NXT key to view Pages1, 2, 3 and 4 and record the information

Shutdown page 2 displays the time and date of the shutdown.

8 Press NXT to go to Page 5 Page 5 displays ACK SD and NO on lines 2 and 6

respectively. See the next figure:

Figure 4 .11.

8 Press the UP/DOWN arrow to show

YES on line 6 and then press the key next to ENT on the display

This will acknowledge the Shutdown and line 6 will display NO again. Line 3 will now change to 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


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.1 System requirements: The following computer configuration is the minimum recommended for running ViZapp:

• 1GHz CPU with 512 MB RAM

• 500 MB of available hard disk space

• 4x CD ROM Drive

• 1024x768, 256 color video card and monitor

• Microsoft Windows 2000, Windows XP or Windows NT 4.0. with the latest service packs

• A mouse or other compatible pointing device

• Parallel or USB port for the copy protection key (dongle)

• RS-232 port, RS-485 or compatible USB to serial port adaptor

5 - 1

Training Manual ViZapp Setup Lab

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

5.2.1 ViZapp Setup

1. Insert MicroMod Systems Software CD into the CD-ROM drive.

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

Type D:\SETUP.EXE or E:\SETUP.EXE, (CD DriveLetter:\Setup.exe depending on the letter you use for the CD-ROM drive) and click on OK or press ENTER. The Master Setup screen shown below should appear.

5 - 2

Training Manual

ViZapp Setup Lab

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


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.

MICROMOD Software License Agreement is a legal document. Please read it carefully before clicking on Yes.

Figure 5 .6. ViZapp Setup –MICROMOD license Agreement

An Information dialog box will be displayed next as shown in the next figure:

5 - 4

Training Manual

ViZapp Setup Lab

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


• 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

ViZapp Setup Lab

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


Figure 5 .12. ViZapp Setup –Select Components

• Click on Next to continue.

Figure 5 .13. ViZapp Setup –Program Folder

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

ViZapp Setup Lab




• 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


• 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.


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

ViZapp Setup Lab

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



• The Finished dialog box will be displayed after the device driver is installed. See the figure below:


• Click on the Finish button on this dialog box.

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.


5 - 12

Training Manual

ViZapp Setup Lab


• The following will be displayed if you are installing the driver for the first time on a Windows XP system with a firewall.


• When the Sentinel driver installation is complete, ViZapp setup will continue.

5 - 13



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.

The MicroMod Systems Software CD contains all the technical documentation in Adobe PDF format. If your system does not have Adobe Acrobat Reader installed already, you can install it from the CD after the ViZapp Setup completes.


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

ViZapp Setup Lab


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 .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

• Click on Finish to complete the installation.

• If ViZapp had to overwrite any DLLs that were open in the system at the time of Setup, then you will need to restart the computer for the changes to be effective. You can opt to restart your computer at a later time.

5 - 15


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. Sample Flow PID Loop

F E

F T

F Y F C

F C V

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.

After completing this lab, you should:

• Be familiar with the ViZapp Designer's workspace, menus and toolbars

• Know how to create new workspace, project and instrument documents

• Know how to configure a MOD 30ML database using ViZapp Configurator for a simple PID Control loop.

• Be able to setup communications for communicating to the MOD 30ML/MODCELL instrument from the PC.

• Be able to build a PID loop display for displaying and changing process and operator parameters.

• Know how to compile and download the database to the instrument

6 - 1

Training Manual PID Loop Lab

6.3 Instructions Follow these instructions step-by-step to configure a simple PID loop:

6.3.1 Getting started

1. Launch ViZapp. Select Programs from the Windows Start menu. Select ViZapp from the menu. The ViZapp configurator will launch as shown in the next figure. As you will notice, the configurator will be blank with no workspace loaded on the screen.

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

PID Loop Lab

• 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:


• The New dialog box will redisplay

6 - 3



• 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

PID Loop Lab

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


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

PID Loop Lab

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


4. Let us first configure a scan group:

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

PID Loop Lab

• 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


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

7. Open the loop compound:

6 - 10

Training Manual

PID Loop Lab

• 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


Figure 6 .16. Loop Block

• Close the Loop block by clicking on the OK button.

9. Configure the PID loop shown in Figure 6.17:

• 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

PID Loop Lab

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 PID Loop Lab 6.3.2 Configuring the blocks:

11. Let us configure these blocks next.

• Configure the Analog Input block.

• Double-click on the AIN block to open its Properties menu as shown below:

Figure 6 .19. AIN Block

• Type FT-100 as the name.

• Select Current as the Input type from the drop-down menu.

• Type the Input number as 2 and Description as shown in the above figure. This is the built-in input 2 of the MOD 30ML. Note that changing the input type changes the Input Low and High signal ranges automatically. This can also be manually changed.

• Click on OK when done.

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

PID Loop Lab

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.

12. Save your Document.

Figure 6 .21. File Menu

• It is essential to save your document at frequent intervals.

• Refer to the above figure. The highlighted item is the instrument document. Click on the Save button on the toolbar at the top to save the document. You can also save a document by selecting File-Save from the menu bar. This saves the instrument document.

6 - 15


• 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

PID Loop Lab

Figure 6 .23. PID Properties

• Change the Setpoint low and high limits to 0 and 200.

• Click on the other tabs at the top (Control, Modes, Options etc, to view different pages of the PID block.

• We will accept default values for the other parameters. Click on OK to close the PID block.

14. Configure AOUT block to define the properties of the analog output:

• Configure this block as shown in the next figure:

• The name FCV-100 represents the output to the Flow Control Valve.

6 - 17


Figure 6 .24. Aout Properties

• Specify the Output number as 2. This is built-in analog output two.

• The source range of 0 to 100 from the PID block will be converted to 4 to 20mA output. Refer to the above figure.

• Click on OK.

6 - 18

Training Manual

PID Loop Lab

6.3.3 Connecting the blocks: 15. The next step is to connect the blocks together to realize the control loop shown in Figure

6.1.

• Click on the Multi-Segment connection item on the Algorithms menu to enable connection mode. See figure below:

Figure 6 .25. Algorithm - Connection

• 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.


• You will get a fly-by box that will say MODIN when you move over the input.

6 - 19


• Click on the input of the VCI block. See the figure above.


• 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

PID Loop Lab

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


Figure 6 .32. Cancel Connection

18. Add the blocks from the Component Gallery:

• From the top menubar, select Project/Gallery/Component Gallery

Figure 6 .33. Accessing the Component Gallery

• 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

PID Loop Lab

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


• 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

19. Connect the PID parameters to be displayed:

6 - 24

Training Manual

PID Loop Lab

• 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


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

PID Loop Lab

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


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

PID Loop Lab

Figure 6 .43. Changing engineering unit range for process line display

• Select the OK button at the bottom of this dialog box.

• Repeat this process for the following formats:

• setpointL

• processB

• Close the Display Block with the OK button at the bottom of the dialog box.

21. Close the loop compound:

• 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


Figure 6 .44. Closing Compound

• Select Close Compound at the bottom of this menu.

• You should be back in the original page where the IF, DIF and SE blocks are located.

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:


6 - 30

Training Manual

PID Loop Lab

• Click on the New button on this block as shown in figure below:


• 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.

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



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

PID Loop Lab

Figure 6 .48. CL block

• Click on the Add button on this page/tab.

Figure 6 .49. 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 must be seeing the Loop Compound Control also listed in this dialog.

6 - 33


• 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.

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

PID Loop Lab

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.

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.

• The Specify Input dialog will be displayed next.

• Type an alias FICOP in the Name field as shown below and then click on OK.

Figure 6 .52. Alias

• Repeat the above procedure to assign aliases for the other attributes as shown

below:

6 - 35


Figure 6 .53. CL block aliases

• Click on OK when you are done with the CL block.

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

PID Loop Lab

6.3.4 Setting up Communications for Modbus 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 RS-232 port of the instrument to download to the instrument via Modbus.

• Add a MSC block (Modcell serial communications) to the workspace by dragging it from Algorithms menu. Double-click on it to configure. The properties menu of the MSC block will display as shown below:

Figure 6 .54. MSC Communication block

• Type a name and description for this block.

• Select RS-232 (built-in) from the drop-down menu in the Type field.

• Leave all other entries in their default values and click on OK to save the configuration of this block.

26. Connect the Configured List foreground to the MSC block:

• 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


Figure 6 .55. CL to MSC connection

Save your document now.

Skip the next section and proceed to the following section, Compiling the database.

6 - 38

Training Manual

PID Loop Lab

Setting up Communications for ICN

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.

• Add an ICN block (Instrument Communication Network) to the workspace by dragging it from Algorithms menu. Double-click on it to configure. The properties menu of the ICN block will display as shown below:

Figure 6 .56. ICN Communication block

• Type a name and description for this block.

• Select Built-in as the Type.

• Type an ICN Address. This address should be same as that is set in the instrument.

• Check the box at the bottom of this dialog box if the ICN termination resister is connected to this instrument. This configuration only question is used to determine module current load.

• Click on OK to close the block.

26. Connect the Configured List foreground to the ICN block:

• 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


the connection at the ICN block by connecting it to FGLISTIN. Refer to the figure below:

Figure 6 .57. CL to MSC connection

Save your document now.

6 - 40

Training Manual

PID Loop Lab

6.3.5 Compiling the database It is necessary to compile the database without errors before downloading to the instrument.

Only compiled databases can be downloaded to the instrument.

27. Select Instrument-Compile from the menu bar.

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


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

PID Loop Lab

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


• 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:

1. Adding a 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.


7 - 1

Training Manual Creating a Tuning List

2. Configure the Tune List inputs:

• Double-click on the TL block to configure: The TL block Properties will open.

• Click on the Inputs tab to add inputs.

Figure 7 .2. TL block

• Click on the Add button on this page/tab.

7 - 2

Training Manual

Creating a Tuning List

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


• 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.

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.

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.

3. Configure text to be shown to the operator for each parameter:

• 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

• Click on the OK button in the Specify Input Data dialog box.

• Repeat this procedure for the remaining inputs as follows:

Input Data Point Display Format name Line 2 Text

2 BRESET reset RESET

3 BPREACT preact PREACT

4 ACTION action ACTION

5 CATYPE PIDtype PID TYPE

• The Inputs tab of the TL Properties dialog box will look like the next figure after you added the required inputs.

7 - 5


Figure 7 .7. Tune List Input Data

4. Define the display format for the inputs:

• Click on the Formats tab to add formats.

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

Type Low Limit

High Limit

Entry Method Eng. Units

Display State Table

Entry 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


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.

5. Connect the Tune List block:

• Click on the Multi-Segment connection item on the Algorithms menu to enable connection mode. See figure below:

Figure 7 .11. Algorithm - Connection

• 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



• Move the cursor to the Display block’s input now. Moving the cursor will draw a

line.


• 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.


• 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.

After completing this lab you should be able to:

• Configure a Extended MODBUS OPC database

• Download the Instrument document (strategy)

• View the signals using the built-in OPC Client

8.2.1 OPC Tag Database The database is typically made up of the following:

Devices: These are hardware devices (MODCELL / MOD 30ML) connected to the OPC Server.

8 - 1

Training Manual Extended MODBUS OPC Server

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.

8.2.2 Built-in OPC Client An OPC Client application is built-in with the Extended MODBUS OPC Server for monitoring and testing your Server’s configuration. It is this part of the OPC application that collects data received by the OPC Server and presents to the user. The data presented by the OPC Client is live.

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.

• The OPC Server will launch as shown in figure 4.1.

• A blank tag database Untitled is opened by default.

8 - 2

Training Manual

Extended MODBUS OPC Server

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


• 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.

• The Communication Setup dialog box will be displayed as shown below:

8 - 5


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

• Click on MMA.XMB.DA item to select it. It should now be displayed in the

Server Name field. Click on OK.

• The Communication Setup dialog box will redisplay with MMA.XMB.DA in the Server Name field as shown below:


7. Select the Device: Click on the Browse button next to the Device Name field.

8 - 7


• 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):

• Refer to the following display.

• Check the box Populate ViZapp and Server Tag lists by clicking on it and then select the MODBUS Interface File PIDLAB from the Available MIF Files list at he bottom.

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



• 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

• After successful download, the following message box saying “Download

completed without error” will be displayed. Click on OK.

Figure 8 .12. Download

• The OPC Server application will also be closed automatically if it was started by

ViZapp for downloading.

8 - 9

Training Manual Extended MODBUS OPC Server 8.3.3 Part 3 – XMODBUS Server OPC Client

9. Launch the XMODBUS OPC Server Application if it was not running already. It will be launched with your last saved database PidLab.MOPC as shown below:

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

• This will display the Device Properties dialog as shown below:

• This dialog gives details about the MIF file in addition to the device details. Important information about the MIF file are:

• MIF file name and location.

• Time-stamp

• Number of elements / tags.

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

• Click on Cancel on this dialog.

Figure 8 .16. OPC Live Data

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


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:

• Run the Modcell/MOD 30ML document in debug mode by communicating with the instrument.

• Start and use the Status Viewer to read and write instrument attributes.

Figure 9 .2. Instrument Status Viewer

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.

2. Start Debug for this 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


• 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.

3. View details of PID block.

• 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.

4. Change the value of PID Gain:

• 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


• 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

• Click on the cursor again to change its type to Debug mode.

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

9.3.2 Part B – Instrument Status Viewer

1. Start the Instrument Status Viewer:

• Select Instrument – Status from the menu bar at the top. This will display the Communication Setup dialog as shown below:


• 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.

2. Read the status of the instrument:

9 - 7


• Type R STATE in the command field and then click on the Enter button.


• 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.

Refer to MOD 30ML / Modcell / ViZapp Designer documentation or the in-program Help for syntax, commands and readable / writeable attributes listing.

Some common commands are listed below: ACK_SD Acknowledge shutdown fault CLR_Q Clear event queue ACK_ALL Ack all diagnostics, process alarms & notification messages R VERSION Read instrument version R Q Read instrument event queue R DIAGS Read instrument diagnostics

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


4. View Cross - Reference information of the control strategy:

• 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.

5. Write PID Setpoint:

9 - 9


• 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.


• Close the Instrument Status Viewer by clicking on the Exit button.

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

(Note that the IC and OC occurrence numbers and instrument addresses are only examples for the purposes of this lab. They do not imply any requirement to use these addresses.)

40.

AU LOCOP

FIC - 1065.

/ 25.2

AULO

OP

LI -1048.6

/

ARSP

TSTCI

ICN Addr 1

40.0

AULO

O

FIC - 1065.2

/

LIC-

40.0

AUT LO

S

MASTER

65.2

25.2

AULOC

OP

LI -1048.6

/

FIC-OP

OPTI

RSPI

48.6

SLAVE

25.2

OP/

AUTREM

/

ICN Addr 2

10 - 1

Training Manual Peer-to-Peer Communications

10.3 Equipment Required The following equipment will be needed for this lab:

• 2 MOD30ML Controllers • 2 ICN Modules (2030N) • 1 ICN Terminator (2030FZ00001A) • Cable, dual twisted pair (1 ft. min.) • Small Flat Blade Screwdriver • Wire Stripper/Cutter • ViZapp with XMB OPC Server and Download Cable

10.4 Instructions

Follow these instructions step-by-step to add and configure the peer-to-peer communications

Configure the First Instrument:

1. Install an ICN Module into the controller’s slots 7 and 8 set its address to 1.

2. Add an Input Communications Block to the instrument:

• 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.


3. Configure the Input Communication Block:

• Double-click on the IC block to configure: The IC block Properties will open.

• Click on the pull-down menu to configure the Data Type of the signal being received from the other instrument.

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


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


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


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.


4. Configure another Input Communication Block:

• Place another IC block and configure it from instrument 2’s OC2 to the PID block’s TCI (Track Command Input). Note that this will be a Discrete signal.

5. Configure the Output Communication Block:

• 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


Figure 10 .10. Algorithm – OC Block

• Double-click on the OC block to configure: The OC block Properties will open.


• We will use the default data type of Floating point.

Figure 10 .11. OC Block Properties

• Click on the Data Destination tab at the top of the dialog box.

10 - 7


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 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


• 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.


• Compile and download your database to instrument 1

10 - 9


Configure the Second Instrument:

1. Install an ICN Module into the controller’s slots 7 and 8 and set its address to 2.

2. Add an Input Communications Block to the instrument:

• 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.


3. Configure the Input Communication Block:

• Double-click on the IC block to configure: The IC block Properties will open.


Figure 10 .17. IC block

10 - 10

Training Manual


• 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 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


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)


• 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



4. Configure an Output Communication Block:

• 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

• Double-click on the OC block to configure: The OC block Properties will open.


• We will use the default data type of Floating point.

10 - 13


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 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


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



5. Configure another Output Communications Block:

• Place another OC block and configure it to send the PID block’s TS (track status) to IC2 of the first instrument. Note that this will be a Discrete signal.

• Compile and download your database to instrument 2.

6. Connect the ICN:

• Devices on an ICN are wired in parallel, with the +/- using one pair of wires and 24V/Com using the other pair.

• The terminals required for this exercise are as follows: 15: 24Vdc 14: COM 13: + 12: -

• Each ICN requires one terminator. The terminator is to be installed into the same terminals as the ICN wires on one of the instruments. Because the terminator has solid wires, care must be taken to ensure that both it and the ICN wires are secured into the terminal.

7. Test your configurations for proper operation:

• Look for ICN errors “Not Receiving Data” on either instrument.

• In normal operation, both controllers are in Auto mode, the Master is using a Local Setpoint and the Slave is using a Remote Setpoint.

• Placing the Slave controller into Manual, or changing its Setpoint mode to Local should force the Master controllers into Track mode.

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

• Type the expression: inp1 + inp2 under the Expression tab.

• Click on the Validate button to verify that the syntax is correct. See the figure below:

11 - 1

Training Manual Expression Block Lab

Figure 11 .2. EX block Example

• Specify the data type for the result as Floating point under the General tab of the EX block.

3. Compile the database.

Use the above techniques to configure the following 3 examples:

11 - 2

Training Manual

Expression Block Lab

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


11.4 Expression Operation Operator precedence in an expression starts with the unary (single operand) operators and continues with the binary (double operand) operators. The order of evaluation can be changed using parentheses or the conditional operators. The order of precedence is:

Precedence Operator

1 ** RAISED_TO_THE_POWER

2 SQRT

MOM

!

ABS

EXP

NLOG

LOG

INT

SQUARE_ROOT

MOMENTARY

Logical NOT

ABSOLUTE

EXPONENTIAL

NATURAL_LOG

LOG_10

INTEGER

3 *

/

TIMES

DIVIDE

4 +

–

PLUS

MINUS

5 <

>

<=

>=

LESS_THAN

GREATER_THAN

LESS_THAN_OR_EQUAL

GREATER_THAN_OR_EQUAL

6 ==

!=

EQUALS

UNEQUAL

7 && Logical AND

8 | | Logical OR

11 - 4

Training Manual

Expression Block Lab

11.4.1 General Rules For Boolean operators, data of any type is considered TRUE if non-zero. For logical operations, all operands are scaled to DISCRETE during evaluation.

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 MOMENTARY Operator

The MOMENTARY operator allows a user to embed an ‘edge detection’ in an expression. The result of the MOMENTARY operation is TRUE only if its operand was FALSE in the most recent evaluation and is now TRUE. Note that the MOMENTARY operator is distinct from the MOMENTARY DISCRETE input data type.

The INTEGER Operator

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

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


Figure 11 .3. If Then Else

Using Expression Blocks as Recipes

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.

Momentary Discrete Local Input

The value of a MOMENTARY DISCRETE local input is changed back to FALSE whenever a TRUE is found so that it is detected in only one evaluation of an expression. The momentary discrete feature allows a user to embed a ‘push-button’ in an expression. MOMENTARY DISCRETE is a unique data type which can only be used as a local input to an expression block. Another block pointed at this input will see a DISCRETE data type. A local input of this type is configured by setting the local data to HIGH or LOW.

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.

The basic P&ID for this demo looks like this:

Figure 12 .1. Sample Batch Reactor

TE

LSH

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.

After completing this lab, you should be able to

• Configure a Sequence block

• See the benefits of the Sequence block over traditional methods of configuring a sequence control scheme.

• Debug the sequencer online with the ViZapp Debug.

The Sequence Display Lab provides instructions on building a custom display to view the sequence constructed in this exercise.

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

• In the Name field, type Sequence Lab and click OK

• In the Choose Instrument Version dialog box, click Close

• A new database workspace appears on your screen.

2. Place a Loop Compound block

• 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.

3. Place Inputs, Outputs and Sequence block

• 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


Figure 12 .4. Blocks

4. Configure the I/O 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

5. Define locations for the I/O Modules on the board:

• 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


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

• Click on OK to close the WRIM Properties dialog.

• Close the I/O Graphic by clicking on the close button (X)

12 - 6

Training Manual

Sequence Lab

6. Configure the Sequence block:

• 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.

7. Add Sequence Inputs

• Click on the Inputs tab of this dialog. Refer to the next figure:

Figure 12 .10. SEQ Properties - Inputs Tab

Click here to add inputsClick here to add inputs

12 - 7


• 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

• Type StartPB (Start Push Button) in the Name field.

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


• Add more inputs to the SEQ block as below: Leave the initial value data field in its

default value.

Input # Name Type

2 LevelHI Discrete High Level Switch

3 Temp Floating Point Product Temperature

4 Draining Discrete Drain Valve Open Feedback Contact

5 HeatSP Floating Point Setpoint for Heating Product

6 CoolSP Floating Point Setpoint for Cooling Product

7 LevelLO Discrete Low Level Switch

Use the Modify button if you make a mistake. Select the input and then click on the Modify button.

12 - 9


After adding all the inputs, the Inputs tab should look like the following figure:


• 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.

8. Add Sequence Outputs:

• 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



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 Number

Name Type Initial 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


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.

9. Define the Sequence Steps

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


Figure 12 .19. SEQ Properties - Steps Tab

Step number

Step name

Step transition logic

Outputs

Step number

Step name

Step transition logic

Outputs

• Click on the Add button. The Specify Data for this Step dialog will be displayed:

Figure 12 .20. Specify Step dialog

• Type IDLE in the Step Name field.

• Type the step logic expression in the Transition Expression field:

IF StartPB && !Draining THEN Charge

In the above expression StartPB and Draining are inputs, and Charge is the step name.

• Click on the first blank field under the Data column in the Output Data window. Define values for each output as shown in the above figure. These are the values each output will assume when the sequence enters this step.

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.


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


• Enter the Transition Expressions for the steps as shown below:

Step # Step Name Transition Expression

2 Charge if LevelHI then Heat3 Heat if Temp >= HeatSP then Cook4 Cook if Time >= 0:0:20.0 then Cool5 Cool if Temp <= CoolSP then Drain6 Drain if LevelLO then Idle

• After adding all the steps, the Steps tab of the SEQ Properties dialog will look like the figure below:


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.

10. Make connections to the Sequencer:

• 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

• The Choose Parameter dialog of the SEQ block will be displayed.

12 - 17


Figure 12 .25. SEQ Choose Parameter - digital

• Select LevelLO from this dialog and then click on OK.

• Make the other connections in the same way. Use the following table:

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


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 Supervisory Message Lab

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.

A – ADD A TEMPERATURE CONTROLLER

Step Procedure Comments 1. Place a new Loop Compound block in the workspace and name

it TEMP CONTROL.

2. Right-click on the new compound block and select Open

Compound.

3. On the top toolbar, click on Project / Gallery / Component

Gallery

It is important to select Component 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

compound ML_PID and click the Export button. You can also double-click on the compound to be exported to your database instead of using the Export button.

13 - 2

Training Manual

Supervisory Message Lab

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


6. Double-click on the PID block to open it. 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


B – ADD THE SUPERVSIORY MESSAGE BLOCK

1. Select SM (Supervisory Message) from the Algorithm window and place it near the PID block.

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

is ‘Set’. There are several message types that can be sent by the Supervisory Message block. To change a control mode we need to use the SET command.

5. Click OK to close the block.

6. Select the Multi-Segment connector from the Algorithm window,

and click on the PID block.

7. Select the attribute OPMS from the connection window

8. Drag the cursor to the SM block and select it

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


10. Right-click in the open space of your database and close the compound.

You should be at the top level of your database, with the IF, DIF, ST and SE blocks visible on the screen as well as the BATCH and TEMP CONTROL compounds.

11. Click on the multi-segment connector, then the Batch compound.

The Choose Parameter window appears

12. Select Compound Internals and click OK (or double-click on

Compound Internals)

A list of all the blocks inside the BATCH compound appears

13 - 6

Training Manual


13. Double-click on StepMgr

A list of all the possible connection parameters in the Sequence block appears

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


17. Select Compound Internals, then A/M

18. The only possible connection is DATAINP, therefore double-

click on this parameter.

19. You should now have a connection between the two compounds

as shown:

13 - 8

Training Manual


20. Using the same method, make the following connections:

From: BATCH.StepMgr.SetMode To: TEMP CONTROL. A/M.SENDINP

This triggers the Supervisory Message block to send the data. It is triggered on a rising edge. This is why the output from the Sequence Block is only true for the HEAT and DRAIN steps, and false in all other steps.

From: BATCH.StepMgr.Setpoint To: TEMP CONTROL.PID.RSPI

This sends the new setpoint value to the PID controller.

21. Your blocks should now look like this:

C – ADD THE TEMPERATURE DISPLAY TO THE DIF BLOCK

In order to see the effect of the supervisory message on the temperature controller, we will need a display on the MOD 30ML.

1. Double-click on the DIF block

2. Add the display name PID-100 to the Display Tag List

3. Select User display under ‘Display to use at power-up’ and type PID-100

4. Close the block.

13 - 9

Training Manual Supervisory Message Lab D – DOWNLOAD TO THE CONTROLLER

1. Select an MSC block from the Algorithms window and place it in the database

No configuration of this block is necessary for this lab

2. Save your database

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

selected See the Extended Modbus OPC Server lab for assistance

6. If you already have a Device configured, double-click to open

the Configuration menu. Make sure the Primary Port settings are correct.

If you do not already have a device configured see Chapter 4, Extended 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

8. Click on the SEQUENCE.MIF file and click Open

9. Click OK to close the Extended Modbus Device Properties

window

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.

Refresh iconRefresh icon

E – TEST THE CONFIGURATION

We do not have a display for the Sequence, but we can use the ViZapp debug function to test the Supervisory Message configuration.

1. Open the BATCH compound

2. On the top toolbar select Project / Start Debug Mode

13 - 11


3. Double-click on the StepMGR block

4. Change the Mode from Auto to Manual, and then change the Current Step from Idle to Heat.

Did the PID controller come out of 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

Step Procedure Comments 1. Make sure your PID block is visible on the screen. 2. From the Algorithm library menu, select PAD

(Process Alarm Display)

3. Drag the box onto the screen and fix it in place by

clicking the left mouse key. Move and size the block so it is in an appropriate area of your screen.

You should now have a block on your screen called PAD

14 - 1

Training Manual Process Alarm Display Lab

B - CONFIGURE A HIGH PROCESS ALARM

Step Procedure Comments 4. Double-click on the PAD block to open it Refer to the next figure. 5. Enter the tag name PALM_H in the Name field. 6. Using the pull-down menu, change the Trip

Condition to Greater Or Equal The alarm will activate (trip) when the 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

“Float 1” by selecting it with the mouse The numerical display of the alarm will be floating point with one place to the right of the decimal point

10. In the Engineering Units field, type GPM 11. Select “Normal” for the Bar Format field The range fields are activated 12. Leave the Lo Range at the default value of 0 13. Change the Hi Range value to 200

14 - 2

Training Manual

Process Alarm Display Lab

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

display” to “Go to display with this tag” and type FIC-100 (or the Display Tag you used for your PID block)

When the alarm page is displayed, pressing the TAG key will automatically take you to the operator display for FIC-100

17. Close the block by selecting or pressing OK

C - CONNECT THE BLOCKS

Step Procedure Comments 1 Select one of the Connection methods from the

library

2 Click in the middle of the PID block A menu of possible connections appears 3 Move the scroll bar until you find the mnemonic

PVI (process variable input) and select it

14 - 3

Training Manual Process Alarm Display Lab 4 Drag the cursor into the PALM_H block and select

the block

5 The only possible connection is ALARMINP (alarm

input); this is done automatically by ViZapp You now have a line from the PID block to the PALM_H block

6 Return to EDIT mode by selecting the arrow on the

right toolbar

7 To check your connection, open the PAD block and

select the INCOMING tab.

D – CONFIGURE A LOW ALARM:

1 Using the printout provided, repeat this exercise to configure and connect a low process alarm with the following characteristics:

Block Tag PALM_L Display Tag FIC-100 Line 1 Text FIC-100 Line 2 Text FLOW LO Condition Less or equal Value 50 Display Format Float 1 Range 0 to 200 Engineering Units GPM

E – COMPILE THE DATABASE:

1 Save your database.

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

Step Procedure Comments 1. Make sure your PID block is visible on the screen.

2. From the Algorithm library menu, select TOT

(Totalizer)

3. Drag the box onto the screen and fix it in place by

clicking the left mouse key. Move and size the block so it is in an appropriate area of your screen.

You should now have a block on your screen called TOT.

4. Open the Totalizer block. Set the Analog Input to 1

as shown.

Because there are no actual inputs 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.

5. Click on the Initial/Restart tab.

6. Change the Initial Mode to Run The Totalizer will begin totalizing the

15 - 1

Training Manual Totalizer Display Lab

process variable as soon as the instrument download is complete.


B – CREATE THE TOTALIZER DISPLAY

Step Procedure Comments 8. Drag a new DISP block onto the workspace and place

it near the TOT block

9. Double-click to open the DISP block

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

STM TOT This is the tag name that will appear on the operating display.

12. In the Initial Data section, type Total in the blank

field next to Line 2 We will define an input called Total, and its value will appear on Line 2 of the display during operation.

13. In the Initial Data section, type “CLR”, including the

quotes, in the blank field next to Line 5 We will define a constant string value CLR to appear on Line 5 of the display during operation.

14. In the Initial Data section, type Clear in the blank

field next to Line 6 We will define an input called Clear, and 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

Totalizer Display Lab

input as shown below, then click OK to close the menu

The analog input from the PID block (PVI) is a Floating Point variable. TotalL is the name of the Format, which will be defined in the next activity. Bar format name is left blank because we will not display this value as a bargraph.

17. Click on the Add button and configure the new clear

input as shown below, then click OK to close the menu

clear is the name of the input. This will be a discrete input from the keypad on the controller. clearL is the name of the Format, which will be defined in the next activity. Bar format name is left blank because we will not display this value as a bargraph.

18. Select the Formats tab, click on the Add button and

configure the format for the Total value:

15 - 3


19. Add a format for the clear variable:

clearL is the format name The format type is a State variable. The State Table to show the operator command will be added in the next section. Entry method – the operator will be required to press ENT to clear the total. Note that there must always be a Display state table; it can be the same as the Entry state table.

20. Click OK to close the DISP block 21. Connect the totalizer block output TC to the display

block input Total This allows the totalized count to be shown on the display.

22. Connect the display block Clear to the totalizer block

input RESINP This allows the user to clear the totalized count from the display.

D - ADD NEW STATE TABLE

Step Procedure Comments 23. At the top level of your database, double-click on the

ST (State Table) block to open it. The State Table is required to provide text representation of the reset command (which in the instrument is “1” or “0”…not very meaningful to an operator).

24. Select the Tables tab and scroll to the bottom of the

list of tables. It does not matter where the tables are 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

of State Tables: Clear, 3, “???” { 1, “YES”; 0, “NO”; }

Clear is the table name 3 is the maximum number of characters to be displayed for the field in this table. The question marks will be shown on the display in the event the value is neither 1 nor 0.

15 - 4

Training Manual

Totalizer Display Lab

26. To verify your script is correct, click on the Checkmark icon on the toolbar. Correct any reported errors.

27. Click OK to close the ST block.

E – ADD THE TOTALIZER DISPLAY TO THE DISPLAY LIST

Step Procedure Comments 28. Double-click on the DIF block

29. Add STM TOT to the display list

30. Close the DIF block

F – COMPILE THE DATABASE:

Step Procedure Comments 31. Save your database.

32. Compile and download your configuration.

33. Press the TAG key to view the new STM TOT

totalizer display.

34. Press the up/down arrow key to select YES. Press

ENT. The total value resets to zero and begins totalizing again.

15 - 5


15 - 6

16 CJC and Display Lab

Intro to Custom Display Configuration 16.1 Foreword

In some applications you may wish to change the function of one or more keys and/or cause different information to appear on the display. This lab uses a cold junction compensated temperature input and display to explore some basic elements of custom display building.

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

Step Procedure Comments 1. Add a Loop Compound to the strategy, double-

click on the block, and give it the name TEMP

2. Close the block

3. Right-click on the new TEMP compound and

select Open Compound You are now “inside” the compound, and the

compound connection dialog box is visible.

4. Select AIN from the library window and place the block on the screen.

This is a built-in analog input.

5. Double-click on the AIN block.

6. Give the block the name TT-100

7. Use the pull-down menus to change the Input

Type to Thermocouple with CJC

8. Change the Linearization Type to

Thermocouple Type K

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 CJC and Display Lab

simulated input value.

11. Close the block with the OK button. B- CONFIGURE SIGNAL CONDITIONING

Step Procedure Comments 1. From the Library window, select a TI block and

place it on the screen near your AIN block. This block converts the mV to the selected

engineering units (Celsius, Fahrenheit, Rankine or Kelvin)

2. Double-click on the TI block 3. Enter the block name TI-100 We will accept the default configuration for the

block 4. Close the block

C - PLACE THE DISPLAY BLOCK

Step Procedure Comments 12. In the Library window, click on DISP , drag the

box onto the screen and fix it in place This is the Display block

13. Double-click on the Display 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

field. This is the tag name we will use to reference the

display in the Display Interface Block, and on the front of the instrument.

16. Under Initial display data, type DISPTAG in

the Line 1 field. This will cause the Display Tag (as entered in the

Display Tag field) to appear on Line 1 of the display.

17. Type “TI” in the Line 5 field. DO NOT close

the block. DOUBLE QUOTES ARE REQUIRED. The text

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

CJC and Display Lab

D - CONFIGURE THE BLOCK INPUTS

Step Procedure Comments 5. Click on the Inputs tab at the top of the dialog

box The Inputs window appears

6. At the bottom of the screen, select the Add

button The input editing menu appears

7. Change the name of Input 1 to TI This will be the temperature value. 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 10. Click on the Add button again 11. Give Input 2 the name CJC and type in CJCL

for the format name This will be the value being used for compensation.

12. Close the menu 13. Add Input 3 and give it the name SCRLCNT This counts the number of times the Scroll Key is

pressed 14. Use the pulldown menu to change the data type

to Count

15. Close the menu You should now have three inputs (TI, CJ and

SCRLCNT) listed in the Inputs window. C- EDIT THE DISPLAY FORMATS

Step Procedure Comment 1. Click on the Formats tab at the top of the dialog

box The display formats window appears

2. At the bottom of the screen, select the Add

button The Format editing menu appears

3. Select the field showing FMT1 and type in

TempL This was the format name we used when

configuring the display block inputs 4. Use the pull-down menu to change the format to

Float2 This will display the input as a floating point

variable with two places to the right of the decimal point

5. Change the Low and High limits to -200 and

1200 respectively This is the range for a Type K thermocouple

6. Change the Entry Method to None This is for display only, no operator entry 7. In the Engineering Units field, type oC Use a lower-case o, not a zero

16 - 3


8. Close the menu 9. Add a second format and give it the name

CJCL This is the name that was designated in the Inputs

menu 10. Make the following changes to this format:

Format Float2 Low Limit -10 High Limit 60 Eng Units oC (lower case o) Entry Method None

11. Close the menu You should now have two formats listed in the

Format window. D - CONFIGURE THE DISPLAY SCRIPTS

Step Procedure Comment 1. Click on the Scripts tab at the top of the dialog

box The display formats window appears

2. Following the formats shown below

EXACTLY, type in the display script shown below.

DEFAULTS: { SCROLL_PRESSED: { IF SCRLCNT >= 1 THEN SCRLCNT = 0; ELSE SCRLCNT = SCRLCNT + 1; CASE SCRLCNT OF { 0: #LINE5 = "TI"; #LINE6.SRC = TI; BREAK; 1: #LINE5 = "CJC"; #LINE6.SRC = CJC; BREAK; } } }

This script counts the number of times the scroll key is pressed (starting with the first press being “0”, increments the count accordingly, then determines what appears on Lines 5 and 6 for each count. The hashmark indicates an assignment statement, that is, a value, input or text is assigned to that resource (in this case Lines 5 and 6). There are predetermined assignment statements; these are listed in the MOD 30ML Display Guide. Text to appear on the display is enclosed in double quotation marks.

16 - 4

Training Manual

CJC and Display Lab

3. When you have finished typing the script, click on the Checkmark icon at the top of the window.

This will verify your script immediately, checking for syntax errors.

4. Once the script is verified without error, close

the Display Block using the OK button.

E – CONNECT THE BLOCKS

Step Procedure Comments 1. Click on the Connections icon You may use either right-angle or multi-segment 2. Using the mouse to select the blocks and entries,

make the following connections: TT-100.MODOUT to TI-100.MODIN TT-100.CJC to TempDisp.CJC TI-100.R to TempDisp.TI

F - ADD THE DISPLAY TO THE DISPLAY LIST

Step Procedure Comments 1 Close the compound. You should see the Environment Blocks (DIF, ST,

SE, IF) in your workspace. 2 Double-click on the DIF block 3 Click on the “NEW” icon above the Display List 4 At the bottom of your display list add:

TI-100 This is the Display Name, NOT the name of the

display block! 6 Select OK to close the block.

Save, compile and download the database. 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


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 steps in creating any custom display are:

1. Design the display: a. What will appear on each line (1 through 6) and what is the source? b. What will each bar represent? c. Will the text on any of the lines change based on a change in the source variable?

If YES, a State Table is required. d. Will any of the keys perform a different function than standard?

If YES, a Display Script is required. e. Will the information displayed on any of the lines be driven by different sources,

or change based on an event such as a key being pressed? If YES, a Display Script is required.

2. Build any State Tables that are required 3. Configure the Display Block

a. Define which inputs will be shown on the screen b. Define how each input will look c. Connect any inputs coming from other blocks d. Write Display Script if required

4. Add the display name to the Display List in the DIF (Display Interface) Block 5. Set up the overall display parameters in the DIF block

The diagram on the following page shows a simplified flowchart of custom display building:

17 - 1

Training Manual Sequence Display Lab

Variables to display:Lines 1 – 6Bars 1 – 3

Text change based on source variable?

State Table

YES

NO

Key function(s) other than standard?

Event-driven information changes?

Multiple sources for same line?

Configure Display Block-Inputs

-Display formats

DisplayScript

YES

YES

YES

Add display name to DIF block

Configure DIF block

Variables to display:Lines 1 – 6Bars 1 – 3

Text change based on source variable?

State Table

YES

NO







Configure Display Block-Inputs

-Display formats

DisplayScript

DisplayScript

YES

YES

YES



Configure DIF blockConfigure DIF block

Upon completing this lab you should have a basic understanding of how to:

1. Design and plan a custom display

2. Build State Tables to allow text changes based on a change in a variable

3. Write script to change key functions and change text based on an event

17 - 2

Training Manual

Sequence Display Lab

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.

A – DESIGN THE DISPLAY

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.

MOD 30ML CUSTOM DISPLAY PLANNING WORKSHEET

DISPLAYS:STATE

TABLE? SCRIPT?LINE 1 Current Step from Sequence Block Yes No

LINE 2 Time in step from Sequence Block No 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

LINE 6 YES/NO in Idle step, for operator start Yes Yes

Temperature in Heat, Cook and Cool steps

Blank in all other steps

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 Sequence Display Lab B – BUILD THE STATE TABLES

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.

Two State Tables are required for this display:

1. To display the current step on Line 1, at all times

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.

Step Procedure Comments 1. Double-click on the ST (State Table) block

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

table’s unique name; the maximum number of characters (usually 8 or 3); and what should be displayed if none of the conditions are met.

You can comment the state tables by enclosing your text with /* */

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:

Start, 3, “???”

{ 0, “NO”; 1, “YES”; }

Table name = Start; maximum characters = 3; if the input is neither 0 nor 1, display ??? (this must be enclosed in quotes) This will be used to make the bottom line of the Sequence display show “NO” or “YES” depending on the state of the StartPB input.

Multiple display blocks can refer to the same State Table. For example, there is only one set of State Tables for the PID loops, which is referenced by all standard PID displays.

5. Press the ENTER key on the keyboard twice 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,”????????” { 1, “IDLE”; 2, “CHARGE”; 3, “HEAT”; 4, “COOK”; 5, “COOL”; 6, “DRAIN”; }

We will create an input to the Sequence Display block and connected to the Sequence Block output “Step”. As the value of this input changes, the text displayed on Line 1 will change accordingly. 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

checkmark box in the toolbar of the State Table dialog box.

Any errors will be reported in the bottom panel of the ViZapp main window.

8. Click OK to close the State Table dialog box.

17 - 5

Training Manual Sequence Display Lab C – ADD AND CONFIGURE THE SEQUENCE DISPLAY BLOCK

Step Procedure Comments 1. Right-click on the BATCH compound and open it 2. Select DISP from the Algorithms window and place it to the

right of the Sequence Block, below the Digital Output blocks. Resize the block so it is a large rectangle.

It is helpful to make the Display Block rather large in this case, to allow space for the inputs to be correctly and clearly displayed.

3. Double-click on the Display Block.

Define the general parameters:

4. In the Name field type SeqDisp

5. For the Display Tag, enter BATCH

6. Enter the following for Initial Display Data: Line 1: Step We will define an input called Step, which

will be displayed on this line. Line 2: StepTime We will define an input that will be

connected to the sequence block’s TIME attribute, and display it on Line 2

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. Define the block inputs:

7. Click the Inputs tab

8. Click on the Add button The Specify Input Data dialog box opens

9. Make the following entries:

17 - 6

Training Manual


Name: StepTime Data Type: Millisecond time Internal Data: 0:00:00.000

10. Click OK to close the dialog box

11. Using the Add button, add the following inputs:

Name Data Type Internal Data Line Format

Name StartPB Discrete False StartL Step Count 0 StepL blank ASCII Temp Floating point 0 TempL LSH Discrete False LSL Discrete False Draining Discrete False

• The Line formats will be defined in the next step. They

are arbitrary names, chosen by the user. In this case “L” was used to designate a Line format, as opposed to a Bar format. For example, in a PID display block, there may be a format called processL to display the process in a line format; and processB to display it as a bargraph.

12. The Inputs tab should now look like this:

Define the display formats:

13. Click on the Formats tab

14. Click on the Add button The Specify Format Data dialog box appears


Name: StartL The name we defined in the Inputs tab Format type: State A state variable usually has three or more

discrete values

17 - 7

Training Manual Sequence Display Lab 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.

16. Using the Add button, add the following formats:

Name Format Type Low

Limit High Limit

Entry Method Display state table

Entry state table

Eng units

StepL State None StepName TempL Float1 0 100 None o

The Formats tab should look like this:

Write the display script: A script is required because the information displayed on Line 6

comes from different sources depending on the sequence step (the value of the input Step).

17. Click on the Scripts tab

18. Type the following script into the Scripts window. Be sure to

exactly follow the punctuation.

17 - 8

Training Manual


DEFAULTS: { ACTIVE: { CASE Step OF { 1: #LINE5 = "RUN"; #LINE6.SRC = StartPB; BREAK; 2: #LINE5 = ""; #LINE6 = ""; BREAK; 3: #LINE5 = ""; #LINE6.SRC = Temp; BREAK; 4: #LINE5 = ""; #LINE6.SRC = Temp; BREAK; 5: #LINE5 = ""; #LINE6.SRC = Temp; BREAK; 6: #LINE5 = ""; #LINE6 = ""; BREAK; DEFAULT: #LINE5 = ""; #LINE6.SRC = blank; } } }

This script consists of a Case statement, which is a list of labels and associated statements. The value of the expression is compared with these labels. If a match is found, the associated statements are executed. When the input called Step assumes any of the values 1 through 6, the display block compares that value to the script and displays lines 5 and 6 accordingly. For example, if the value of Step is 1, Line 5 displays the word RUN and Line 6 shows the state of the StartPB input. But if the value of Step is 3, there is no text on Line 5 and Line 6 displays the value of the Temp input (product temperature). If the value of Step is something other than 1 through 6, the DEFAULT case is used (both lines will be blank). For more information on the syntax of display scripts, and other ways to use them, refer to the instruction manual IB-1800R-SCR

19. You can check your script by clicking on the checkmark icon at

the top of the dialog box

Any errors will be reported in the bottom panel of the main ViZapp window.

20. Click OK to close the dialog box.

17 - 9

Training Manual Sequence Display Lab D – CONNECT THE SEQUENCE BLOCK TO THE SEQUENCE DISPLAY BLOCK

1. Using the Multi-Segment connector, make the following connections:

StepMGR.Step → SeqDisp.Step StepMGR.TIME → SeqDisp.StepTime SeqDisp.StartPB → StepMGR.StartPB LSH.R → SeqDisp.LSH LSL.R → SeqDisp.LSL Draining.R → SeqDisp.Draining

Note that the StartPB goes FROM the display block TO the Sequence Block

E – ADD A SUPERVISORY MESSAGE TO RESET THE OPERATOR ENTRY

2. At the moment, if the operator enters “YES” to start the batch, the text displayed does not change back to “NO” ready for the next start. We need to add a supervisory message to cause this.

3. Select SM from the Algorithm window and place it to the right

of the SeqDisp block

4. Double-click on the SM block and make the following entries:

Name: ResetEntry Description: Resets YES back to NO on display Date type: Discrete Data source: Click the “Internal” checkbox and leave the value at False

5. Click OK to close the block

6. Using the multi-segment connector, make the following

connections:

SeqDisp.StartPB → ResetEntry.SETENTRY SeqDisp.StartPB → ResetEntry.SENDINP

E – MODIFY THE TEMPERATURE INPUT TO RUN THE DEMO 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.

1. In the BATCH compound, delete the TE (WRIM) and TI (RTI) blocks, the connection between them, and the connection to the Temp input of the StepMGR (SEQ) block.

2. Close the compound.

3. At the top level of the database, make a connection between

TEMP CONTROL.VCI.R and BATCH.StepMGR.Temp

17 - 10

Training Manual


C – ADD THE SEQUENCE DISPLAY TO THE DIF BLOCK

1. Double-click on the DIF block

2. Add the display name BATCH to the Display Tag List

3. Under ‘Display to use at power-up’ type BATCH instead of

PID-100

4. Close the block.

D – COMPILE AND DOWNLOAD TO THE CONTROLLER

1. Save your database

2. 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”

The File Name for the MIF file should be SEQUENCE, which you created in a 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

selected See the Extended Modbus OPC Server lab for assistance

5. If you already have a Device configured, double-click to open

the Configuration menu. Make sure the Primary Port settings are correct.

If you do not already have a device configured see Chapter 4, Extended Modbus OPC Server, for assistance

17 - 11


6. In the Interface File Filename field, click on the Refresh icon

A list of available MIF files appears

7. Click on the SEQUENCE.MIF file and click Open

8. Click OK to close the Extended Modbus Device Properties

window

9. Return to ViZapp and download the database to the controller The BATCH display should be on the

controller front panel.

Refresh iconRefresh icon

E – TEST THE CONFIGURATION

As we do not have physical digital contacts to represent High Level and Low Level, we will simulate them from the ViZapp Debug screen.

1. In ViZapp, open the BATCH compound

2. Enter Debug mode (Project / Start Debug Mode)

3. If the PID-100 display is showing on the controller faceplate, press the TAG key to show the Sequence display. It should appear as follows (note the millisecond time will be actual):

4. On the front face of the controller, push either the UP or DOWN

button Line 5 displays a flashing ENT and Line 6 displays YES

NO

RUN

IDLE00:00:00

NO

RUN

IDLE00:00:00

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.

6. The top line will change to CHARGE. The millisecond time

displays the elapsed time in the current step.

7. Change the display on the controller front panel to PID-100. Use

the Scroll key to display Setpoint.

8. In Vizapp, double-click on the LSH block.

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

90 When the temperature reaches or exceeds 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

to MANUAL and set the result to ON. The sequence goes to the IDLE step.

17 - 13


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 Piecewise Linearization Lab

18.3 PART I – Piecewise and Linearization Blocks Instructions

A – SELECT AND PLACE THE REQUIRED BLOCKS

Step Procedure Comments 1. Open a new Mod Function Block Diagram.

2. Place a new Loop Compound block in the workspace and call it

DRUM LEVEL.

3. Open the compound. From the Algorithm library, select and

place the following blocks: Two AIN (built-in analog input) blocks Two VCI blocks One PID block One PW (piecewise) block One LN (linearization) block One AOUT (built-in analog output) block

Your workspace should look something like this:

18 - 2

Training Manual

Piecewise Linearization Lab

B - CONFIGURE THE INPUTS AND PID BLOCK

Step Procedure Comments 4. Open the AIN, VCI and PID blocks and make the following

configuration entries: We will leave all engineering units at 0 to 100 percent for the purposes of this lab.

AIN1 Name: FT-100 Input type: Current

AIN2 Name: LT-100 Input type: Current Input number: 2

VCI1 Name: STM FLOW Linearization type: Modified Square Root

VCI2 Name: LEVEL

PID Name: LIC-100 Feedforward Compensation Type: Add

5. Make the block connections as follows:

FT-100.MODOUT to STM FLOW.MODIN LT-100.MODOUT to LEVEL.MODIN LEVEL.R to LIC-100.PVI STM FLOW.R to LIC-100.FFCI

The strategy should now look something like this:

18 - 3

Training Manual Piecewise Linearization Lab C - CONFIGURE THE PIECEWISE TABLE BLOCK

6. Double-click the PW block to open it.

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

to the block. Since the actual values would almost 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


The table can be used by the linearization block for either piecewise (X coordinates) or inverse piecewise (Y coordinates) linearization. The appropriate coordinates must ALWAYS be in ascending order with no duplicates. Up to 60 pairs may be entered. Blocks can be cascaded if more pairs are required.

11. Close the block by clicking OK.

D - CONFIGURE THE LINEARIZATION BLOCK

12. Double-click the LN block to open it.

13. Type FW LN in the Name field and type a Description such as: Feedwater valve linearization

14. Use the pull-down menu to set the Linearization Type to

Piecewise

18 - 5


15. Click OK to close the block. E - CONNECT THE BLOCKS

Step Procedure Comments 16. Connect the output (OP) of LIC-100 PID block to the Input of

the FW LN linearization block.

17. Select the connection icon again and double-click on the

STM/FW piecewise block A menu of possible connections appears

18. Select TABLEOUT from the menu

19. Drag the cursor into the FW LN block and select the block

20. The only possible connection is TABLEIN; this is done

automatically by ViZapp. Click on this connection.

21. Return to EDIT mode by selecting the arrow on the right toolbar

22. To check your connection, open the Linearization block and

select the INCOMING tab.

F – COMPILE THE DATABASE:

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


18.4 PART II – Displaying Piecewise Coordinates Instructions

A – LOAD AND CONFIGURE A PID DISPLAY

Step Procedure Comments 1. Click on Project on the top toolbar of the workspace, then select

Gallery and Component Gallery.

It is important to select Component 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. Launch RestoreGallery from the MicroMod Automation\ViZapp folder of 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.

2. Click on the Compounds tab in the Gallery, and select PID

DISPLAY.

3. Click the Export button to place the compound in your

workspace. The resulting blocks overlay your original strategy. This will be fixed in the next steps!

4. Select and delete the Notes blocks.

5. Hold down the SHIFT key and select the TL and DISP blocks.

Move them to the right of your work area, away from the other blocks. Your workspace should resemble this:

Note that the connection line moves with the blocks.

18 - 7


6. Double-click on the DISP block to open it, and make the

following entries: Name: LVL DISP Description: Drum Level operating display Display Tag: LIC-100


8. Select the Multi-Segment connection icon from the Algorithms

window.

9. Click on the PID block and select OP from the list.

10. Drag the cursor over the DISP block and select it.

11. Select the attribute “output” from the list.

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


B – CONFIGURE THE TUNE LIST BLOCK

13. Double-click on the TL (Tune List) block to open it.

14. Click on the Inputs tab, then click the Add button at the bottom of the TL Properties menu.

The tag browser dialog box appears.

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 BRESET from the list in the middle column, then click the Add button at the bottom of the dialog box. DO NOT click “OK” yet!

This will allow adjustment of the controller Gain, Reset, and output Action (direct or reverse) from the front panel. As you select the attributes they will be highlighted. When you click the Add button they appear in the left window of the menu.

17. In the right window, double-click STM/FW

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


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…

button at the bottom of the window You can also double-click the number 1

22. Make the following entries in the Specify Input Data window:

Display Format Name: Action Line 2 Text: ACTION Click OK to close the dialog box.

The Display Format “Action” was predefined in the compound. The first line of text will be the Display Tag name (LIC-100)

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

26. Enter the following:

Name: F (an arbitrarily chosen name) Format type: Float 1 (floating point, one decimal place) Low limit: -1e+008 High limit: 1e+008 Entry method: Entry required

The new format is now added to the Format list, and ready to be used by inputs.

18 - 10

Training Manual


Click OK to close the window

27. Click on the Inputs tab at the top of the TL Properties window

28. Double-click on Input 4 (LoopCpd.STM/FW.X1)


Display Format Name: F Line 1 Text: click Use This Text and type FW OP X1 Line 2 Text: FW CV

30. Continue configuring the remaining X,Y attributes as shown in

the table below.

Input Data Point Display

Format Name Line 1 Text Line 2 Text

5 LoopCpd.STM/FW.Y1 F FW OP FW CV Y1 6 LoopCpd.STM/FW.X2 F FW OP X2 FW CV 7 LoopCpd.STM/FW.Y2 F FW OP FW CV Y2 8 LoopCpd.STM/FW.X3 F FW OP X3 FW CV 9 LoopCpd.STM/FW.Y3 F FW OP FW CV Y3 10 LoopCpd.STM/FW.X4 F FW OP X4 FW CV 11 LoopCpd.STM/FW.Y4 F FW OP FW CV 4 12 LoopCpd.STM/FW.X5 F FW OP X5 FW CV 13 LoopCpd.STM/FW.Y5 F FW OP FW CV Y5 14 LoopCpd.STM/FW.X6 F FW OP X6 FW CV 15 LoopCpd.STM/FW.Y6 F FW OP FW CV Y6 16 LoopCpd.STM/FW.X7 F FW OP X7 FW CV 17 LoopCpd.STM/FW.Y7 F FW OP FW CV Y7 18 LoopCpd.STM/FW.X8 F FW OP X8 FW CV 19 LoopCpd.STM/FW.Y8 F FW OP FW CV Y8 20 LoopCpd.STM/FW.X9 F FW OP X9 FW CV 21 LoopCpd.STM/FW.Y9 F FW OP FW CV Y9

31. Click OK to close the TL Properties window.

18 - 11

Training Manual Piecewise Linearization Lab B – COMPLETE THE DATABASE, COMPILE AND SAVE

32. Connect the Result (R) of the FW LN block to the INPUT of the Analog Output block.

33. Close the Loop Compound

34. Open the Display Interface Block (DIF) and add the tag LIC-100

to the Display Tag list. Specify User Display to be used at power up and enter LIC-100.

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.

37. SAVE YOUR DATABASE!

D – DOWNLOAD AND VIEW THE TUNING PAGES

38. Open the OPC server and add the device

39. Return to ViZapp and download the database

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

19.3.2 To create a new report:

1. Launch ViZapp Reports Builder Application

• 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.

2. Select the database:

• 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

• A Open Database dialog box will be displayed as shown next:

Figure 19 .4. Open 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


Figure 19 .5. VIZAPP Reports Wizard – Select Database

• The Create Report tab of the Wizard will be open next.

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.

The report file has an extension .RPT

• Click on the Next button to continue. The Open Report tab will be displayed now as shown in the next figure:

Figure 19 .8. VIZAPP Reports Wizard – Open Report

19 - 5


4. Preview the report.

• 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

5. Print the report:

• 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

If a printer is not available, Windows will display an error message.

6. Closing the report:

• 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


7. To open an existing report:

• 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


• Note that the default report title is also shown on the report.

9. Preview Window Controls:

• 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

10. Online Help

• To access help on the VIZAPP Reports Builder application, select Help-Contents or click on the Help button on the tool bar. This will display the help file.

19 - 10

Training Manual

Reports Tutorial

Figure 19 .19. Help

11. Exporting Reports:

Reports can be exported to the following common document types using the Reports Builder:

• Word for Windows (.DOC)

• Rich Text Format (.RTF)

• Text File (.TXT)

• Excel File (.XLS)

To export to Word:

• 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


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


Notes:

19 - 14

Training Manual

APPENDIX A - ASSIGNMENT STATEMENT REFERENCE

APPENDIX A ASSIGNMENT STATEMENT REFERENCE

A.1 ASSIGNMENT STATEMENTS

The assignment statement assigns a value to a given target. The target of an assignment can be an input name, a local attribute name, or one of several predefined names listed below. All assignment statements have an expression as their right hand side. The target will be assigned the value of that expression. Results of assignment statements depend upon the data type as listed below for the different assignment types. See Display Block for usage rules and an explanation of resources.

• Table A-1. Assignment Statement Results of Type ‘srcname1 = srcname2' For example, I1 = I2 or I1 = 4576, or RESULT = INPUT * RATIO + BIAS (where input, ratio and bias are unique names for display block inputs or local attribute names).

• Table A-2. Assignment Statements of Type 'display_resource = source_name' For example, #RBAR = OUTPUT (where #RBAR is a display resource and output is the unique name of a display block input or local attribute name).

• Table A-3. Assignment Statements of Type 'display_resource = constant’ For example, #LINE1 = 37.94 (where #LINE1 is a display resource).

• Table A-4. Assignment Statements of Type 'display_resource.SRC = srcname' For example, #RBAR.SRC = OUTPUT; (where #RBAR.SRC is a display resource having the suffix .SRC and output is the unique name of a display block input or local attribute name).

Table A-1. Assignment Statement Results of Type ‘srcname1 = srcname2'

Destination Type Source Type Result Discrete Discrete: = input Short State: True if input non-zero Long State: True if input non-zero Count: True if input non-zero Msec Time: True if input non-zero Floating Point True if input non-zero Date: True if input non-zero Hex: True if input non-zero

Short State Discrete: = input Short State: = input Long State: limits at 15 Count: limits at 15 Msec Time: treats input as 4 byte integer, limits at 15 Floating Point drops fractional part, limits at 15 Date: treats input as 3 byte integer, limits at 15 Hex: treats input as n byte integer, limits at 15

A-1

Training Manual APPENDIX A - ASSIGNMENT STATEMENT REFERENCE

Table A-1. Assignment Statement Results of Type ‘srcname1 = srcname2' (Cont’d)

Destination Type Source Type Result Long State Discrete: = input Short State: = input Long State: = input Count: limits at 255 Msec Time: treats input as 4 byte integer, limits at 255 Floating Point drops fractional part, limits at 255 Date: treats input as 3 byte integer, limits at 255 Hex: treats input as n byte integer, limits at 255 Count Discrete: = input Short State: = input Long State: = input Count: = input Msec Time: treats input as 4 byte integer, limits at 65535 Floating Point drops fractional part, limits at 65535 Date: treats input as 3 byte integer, limits at 65535 Hex: treats input as n byte integer, limits at 65535

Msec Time Discrete: = input Short State: = inputTreats output as Long State: = input 4 byte integer Count: = input Msec Time: = input Floating Point drops fractional part, limits at $FFFFFFFF Date: = input, treats input as 3 byte integer Hex: treats input as n byte integer, limits at $FFFFFFFF Floating Point Discrete: = input Short State: = input Long State: = input Count: = input Msec Time: treats input as 4 byte integer (lost resolution in large numbers) Floating Point = input Date: = input, treats input as 3 byte integer Hex: treats input as n byte integer (lost resolution in large numbers)

Date Discrete: = input Short State: = inputTreats output as Long State: = input 3 byte integer Count: = inputAccepts any input Msec Time: treats input as 4 byte integer, limits at $FFFFFF if output is local, Floating Point drops fractional part, limits at $FFFFFF but only valid dates Date: = input if output is remote. Hex: treats input as n byte integer, limits at $FFFFFF Ascii Discrete: 0 or 1 as ascii Short State: 0 - 15 as ascii Output truncated Long State: 0 - 255 as asciito fit available Count: 0 - 65535 as asciifield size Msec Time: 0 - 4294967295 as ascii Floating Point value to as many decimal places fit in output field Date: ascii date format.Accepts any input, so can look strange. Ascii: = input Hex: hex value as ascii

A-2

Training Manual


Table A-1. Assignment Statement Results of Type ‘srcname1 = srcname2' (Cont’d)

Hex Discrete: = input

Short State: = inputOutput limits at Long State: = inputavailable field Count: = inputsize (all FF's) Msec Time: = input, treats input as 4 byte integer Floating Point drops fractional part, input limits at $FFFFFFFF Date: = input, treats input as 3 byte integer Hex: = input

A-3


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) #UPDN 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-5


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

#LINE3.SRC Discrete: Integer1 0, 1

#LINE4.SRC State NOTE 1

#LINE5.SRC 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 alternate with 'OVF' (1000 - 65535)

State NOTE 1

Msec_time: Integer4 0 - 999 (0 - 999), first 3 digits alternate with 'OVF' (1000 and up)

Time1 :ss, alternates with 'OVF' if > 0:00:99.999

Time2 sss, alternates with 'OVF' if > 0:00:00.999

Time3 :mm, alternates with 'OVF' if > 0:99:59.999

Time4 .ss, alternates with 'OVF' if > 0:00:00.999

Floating_point 0.0-999 (0.0-999.0), first 3 digits alternate with 'OVERFLOW' (1000.0 & up)

Date: /yy (right justified)

Asc: = input, marqueed if necessary

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



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)


Dev

Count: None 1 - 50 segments on (0 - 50), 50 segments on (51 - 65535)


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)


Dev

Floating_point None 1 - 50 segments on (0.0 - 50.0), 50 segments on (51.0 and up)


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)


Count: None one of segments 1 - 50 on (0 - 50), segment 50 on (51 - 65535)


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)


Floating_point None one of segments 1 - 50 on (0.0 - 50.0), segment 50 on (51.0 and up)


#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



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


A-10

Training Manual

APPENDIX B - DISPLAYED CHARACTER SET

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!

Decimal Keyboard Display

0

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18


19

20

21

22 (space indicator)

23

24

25

26

27

28

29

30

31

32 † space

33 !

34 “

35 † #

36 $

37 † %


38 &

39 '

40 (

41 )

42 † *

43 † +

44 ,

45 † -

46 .

47 † /

48 † 0

49 † 1

50 † 2

51 † 3

52 † 4

53 † 5

54 † 6

55 † 7

56 † 8

B-1

Training Manual APPENDIX B - DISPLAYED CHARACTER SET


57 † 9

58 :

59 ;

60 † <

61 † =

62 † >

63 ?

64 @

65 † A

66 † B

67 † C

68 † D

69 † E

70 † F

71 † G

72 † H

73 † I

74 † J

75 † K

76 † L

77 † M

78 † N

79 † O

80 † P

81 † Q

82 † R

83 † S


84 † T

85 † U

86 † V

87 † W

88 † X

89 † Y

90 † Z

91 [

92 \

93 ]

94 ^

95 _

96 `

97 a

98 † b

99 † c

100 † d

101 † e

102 f

103 g

104 † h

105 i

106 j

107 † k

108 † l

109 † m

110 † n


111 † o

112 † p

113 q

114 † r

115 † s

116 † t

117 † u

118 † v

119 † w

120 x

121 y

122 z

123 {

124 |

125 }

126 ~

127

† Standard faceplate character

set.

B-2

Training Manual

APPENDIX C – DISPLAY EVENTS & RESOURCES

Display Script Events 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 Display Script Resources 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

APPENDIX C – DISPLAY EVENTS & RESOURCES

C-2

Front Face ConfigurationFront Face ConfigurationMapMap

Touring The MOD 30ML Front Face Configuration Menus

This Page Left Intentionally Blank

Page 1

NEXT

DEV STAST SET UP I/O EVENTS ABOUT TEMPLATE

See Page 2 See Page 3

EVENTS *DEVICE*

*DEVICE* ANY TAGI/O

BI AIN 1 AIN MABuilt in analog input 1

S11 UNCONFIGSlot 11 Unconfigured

I/O *DEVICE*

*EVENTS* ANY TAGEVENTS

INST IN RUNInformational event

MM/DD/YY HH:MM:SSInformation only

*DEVICE* ANY TAGABOUT

FW VERS I1A 1.0Firmware version

DISP VER 5.1Display version

*DEVICE* ANY TAGSETUP

SETUP BI COMMBuilt-in Commn.

BI MSC 1 BAUDRATEBuilt-in MSC 1 BaudrateBI MSC 1 PARITYBuilt-in MSC 1 parityBI MSC 1 STOPBITSBuilt-in MSC 1 stop bitsBI MSC 1 ENABLEDBuilt-in MSC 1 enabled

CURRENT LEVEL NONECurrent access level

BI ICN 1 ADDRESSBuilt-in ICN address

BI MSC 1 ADDRESSBuilt-in MSC 1 address

BI COMM SETUPBuilt-in Commn.

SETUP PASSWORDChange Access level

PASSWORDPassword entry

BI ICN 1 ENABLEDBuilt-in ICN enabled

SETUP *DEVICE*A2_FrontFace_Config.ppt


NEXT

INSTATE COMMANDS XTIMES TIME DATE DAY

COMMANDS CLR MTClear Maximum times

COMMANDS CLR QClear Queue

DEV STAT COMMANDSCommands

RUNDEFAULT

HOLD

SHUT DOWN

DEV STAT SHUTDOWNShutdown

SNWDOG 1 orSYSPI 1 xxxxxxxxxShutdown page 1

SNWDOG 6 orSYSPI 6 xxxxxxxxxShutdown page 6

COMMANDS ACK ALLGlobal Acknowledge

COMMANDS RESETReset

COMMANDS KILLKill

COMMANDS DEL MAINDelete main database

COMMANDS RES MAINRestore main database

COMMANDS DEV STATCommands

XTIMES T1 IMMEDScan 1 execution time

DEV STAT XTIMESExecution times

XTIMES T9 IMMEDScan 9 execution time

XTIMES T1 FILTDScan 1 Filtered time

XTIMES T9 FILTDScan 9 Filtered timeXTIMES T1 MAXScan 1 Maximum time

XTIMES T9 MAXScan 9 Maximum timeXTIMES BASE SCNBase Scan time

XTIMES IDLE TMScan idle time

XTIMES DEV STATExecution times

DEV STAT TIMETime

DEV STAT DATEDate

DEV STAT DAYDay

From DEV STATPage 2

DEV STAT *DEVICE*Device status

A2_FrontFace_Config.ppt


From TEMPLATE

INSTALL TEMPLATE

SYSTEM DEV TAGSystem device tagSYSTEM SCANGRPSSystem scan groups

SCAN GROUP 1Scan group 1 interval

SCAN GROUP 5Scan group 5 intervalSYSTEM

SYSTEM PASWORDSSystem passwords

TUNE PASSWORDSetup tune passwordCONFIG PASSWORDSetup config passwordACCESS TIMEOUTAccess timeoutSYSTEM

SYSTEM ALARMSSystem alarms

DIAGNSTC RATEDiagnostic rateDIAGNSTC FLASHDiagnostic Flash

EDIT TEMPLATE

LOAD DEFAULTS

CMP LIST SYSTEM (System compound)

LIST INSERT EDIT

CMP LIST CTAG01 (or any tag) (User compound)

DELETE

NEXT

NEXTNEXT

ENT

DIAGNSTC BEEPDiagnostic beepMINIMUM LOW PRIMinimum low priorityHIGH PRI RATEHigh priority alarm rateHIGH PRI FLASHHigh priority alarm flashHIGH PRI BEEPHigh prio alarm beepLOW PRI RATE

LOW PRI BEEPLow priority beepSYSTEM

SYSTEM

See Page 4

Edit user compound

Insert user compound

Delete user compound

User compounds

INSTALL TYPEInstallation typeCONFIG REQUESTRequest failed

TEMPLATE

VERIFY LOADVerify load

Page 3

(Lines 1&2)

(Line6)

(Lines 1&2)

(Line6)

LIST INSERT EDIT



From page 3 (EDIT user compound)NEXT

TAG IDSTRING SCAN GROUPCMP TYPE PROCESS I/P SETPOINT

TAG ID STRINGLoop tag ID

CTAG01 CMP TYPECompound type

CHANGE TYPE?Change compound type

CTAG01 SCAN GRPScan group

PROC INP TEMPSCALTemperature scale

CTAG01 PROC INPProcess input

PROC INP SLOTProcess input slotPROC INP TYPETypePROC INP FILTERFilterPROC INP LO SIGNLLow signalPROC INP HI SIGNLHi SignalPROC INP LINEARZTLinearizationPROC INP RES RNGEResistance rangePROC INP NOM RESNominal resistancePROC INP LW RESLeadwire resistancePROC INP TC TYPEThermocouple type

PROC INP ZEROZero

PROC INP SPANSpanPROC INP RTD TYPERTD typePROC INP DISP FMTDisplay formatPROC INP LO ENGULow engg unitsPROC INP HI ENGUHigh engg unitsPROC INP EU LABELEngg. unit labelPROC INP CJC SRCCold junction source

PROC INP LO QUALLow quality value

PROC INP BURNOUTBurnout detection

PROC INP HI QUALHigh quality valuePROC INP QUAL ALMQuality alarm

PROC INP QA PRIQuality priority

PROC INP QA DOUTQuality digital out

PROC INP

CTAG01 SETPTSetpoint

SETPOINT DISP FMTDisplay formatREMOTE SETPOINT

REMSETPT XXXXXXXRemote setpoint inp

LOCAL SETPOINTLocal setpointSETPOINT RATIOSetpoint ratio?SETPOINT RATIOSetpoint ratio valueSETPOINT BIASSetpoint bias?SETPOINT BIASSetpoint bias valueSETPOINT BIALANCESetpnt Balance typeSETPOINT LO LIMITSetpoint low limitSETPOINT HI LIMITSetpoint high limit

INITIAL SP MODEiNITIAL Setpnt mode

RESTART SP VALUESetpnt Restart valueRESTART VALUESetpnt preset value

SETPOINT TRACKSetpoint tracking?COMPOUND

REMSETPT

RESTART SP MODERestart Setpnt mode

INITIAL VALUESetpnt initial value

Page 4

To page 5 (CONTROL)

From page 5 (Alarms)



CONTROL OUTPUT ALARMS

CTAG01 CONTROLControl

CONTROL ALGO TYPControl algorithm typeCONTROL ACTIONControl actionGAINRESETPREACTCONTROL FILTYPEFilter typeFILTERFilter valueCONTROL MR TYPEManual reset balanceMR VALManual reset valueFEED FORWARD

FEED FWD xxxxxxxxFeed forward inputFEED FWD

FF GAINFeed forward gainFF BIASFeed forward biasFF CALCFeed fwrd calculationRESRTART MODEOutput mode restartINITIAL MODEInitial mode(Previous)COMPOUND

CTAG01 OUTPUTOutput

OUTPUT SLOTOutput slot positionOUTPUT LO SIGNLOutput low signalOUTPUT HI SIGNLOutput high signalOUTPUT DISP FMTOutput display formatOUTPUT LO LIMITOutput low limitOUTPUT HI LIMITOutput high limitRESTART TYPEOutput restart typeOUTPUT INIT VALOutput initial valueCOMPOUND

PV ALARMSPV ALM 1 TYPEProcess val alarm typePV ALM 1 TRIP VALTrip valuePV ALM 1 HYSTRSISHysteresisPV ALM 1 PRIORITYPriorityPV ALM 1 DIG OUTDigital output

ALARMSDEVIATN ALARMS

DEVALM 1 TYPEDeviation alarm typeDEVALM 1 TRIP VALTrip valueDEVALM 1 HYSTRSISHysteresisDEVALM 1 PRIORITYPriorityDEVALM 1 DIG OUTDigital output

ALARMSOUTPUT ALARMS

OUTALM 1 TYPEOutput alarm typeOUTALM 1 TRIP VALTrip valueOUTALM 1 HYSTRSISHysteresisOUTALM 1 PRIORITYPriorityOUTALM 1 DIG OUTDigital output

ALARMSCOMPOUND

CTAG01 ALARMSAlarms

COMPOUND list

To page 4 (TAG ID)

From page 4( SETPOINT)

Page 5


MicroMo75 To

RochesteTel. Fax

www.

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

IB-MLTUT, Issue 12 03/2010

d Automation, Inc.wn Centre Drive r, NY USA 14623

(585) 321-9200 (585) 321-9291 micromod.com

MOD 30ML Training Manual

Documents