Eycon HA029280 5

Eycon™10/20
Visual Supervisor
Handbook
E U ROT H E R M ®
®
®
E U ROT H E R M ®
Declaration of Conformity
Manufacturer's name: Eurotherm Limited
Manufacturer's address: Faraday Close, Worthing, West Sussex,

BN13 3PL, United Kingdom
Product type: Visual Supervisor
Models: Eycon-10 Status level A1 and above

Eycon-20 Status level A1 and above
Safety specification: EN61010-1: 2001
EMC emissions specification: EN61326-1: 1997 Class A

(including amendments A1, A2 and A3)
EMC immunity specification: EN61326-1: 1997 Industrial locations

(including amendments A1, A2 and A3)
Eurotherm Limited hereby declares that the above products conform to the safety and EMC
specifications listed. Eurotherm Limited further declares that the above products comply
with the EMC Directive 89 / 336 / EEC amended by 93 / 68 / EEC, and also with the Low
Voltage Directive 73 / 23 / EEC.
Signed: Dated:
Signed for and on behalf of Eurotherm Limited
William Davis
(General Manager)
IA249986U700 Issue 2 Aug 06 (CN22697)
© 2008 Eurotherm Limited
All rights are strictly reserved. No part of this document may be reproduced, modified, or transmitted in any form
by any means, nor may it be stored in a retrieval system other than for the purpose to act as an aid in operating the
equipment to which the document relates, without the prior written permission of Eurotherm limited.
Eurotherm Limited pursues a policy of continuous development and product improvement. The specifications in
this document may therefore be changed without notice. The information in this document is given in good faith,
but is intended for guidance only. Eurotherm Limited will accept no responsibility for any losses arising from
errors in this document.
40 ®
E U ROT H E R M ®
VISUAL SUPERVISOR HANDBOOK
VISUAL SUPERVISOR
HANDBOOK
LIST OF CHAPTERS
Section Page
1 INSTALLATION ...................................................................................... 1- 1
2 GETTING STARTED .............................................................................. 2 - 1
3 OPERATION ........................................................................................ 3 - 1
4 MANAGEMENT .................................................................................. 4 - 1
5 CUSTOMISING ................................................................................... 5 - 1
6 ADMINISTATIVE FUNCTIONS ............................................................... 6 - 1
7 REMOTE ACCESS ................................................................................ 7 - 1
8 THE CONTROL CONFIGURATOR .......................................................... 8 - 1
9 PREVENTIVE MAINTENANCE ............................................................... 9 - 1
10 PROFIBUS OPTION ............................................................................ 10 - 1
11 FLUSH MOUNTING OPTION .............................................................. 11 - 1
A SPECIFICATION ................................................................................... A - 1
B OPTIONS UPDATE ............................................................................... B - 1
C REFERENCE ......................................................................................... C - 1
EFFECTIVITY
This manual refers to instruments fitted with software version number V2.1
RELATED MANUALS
The Setpoint Program Editor Handbook ........................................ HA261134U005
The UserScreen Editor Handbook ................................................. HA260749U005
The LIN Blocks Reference Manual ................................................ HA082375U003
LINtools On-line user guide ......................................................... RM263001U055
The LIN/ALIN Installation and User Guide .................................... HA082429U005
The T2550 DIN rail controller User Manual .......................................... HA028898
Modbus/Profibus communications handbook ........................................ HA028014
All registered and unregistered trademarks are properties of their respective holders.
HA029280 Contents
Issue 5 Mar 08 Page 1
LIST OF CONTENTS
Section Page
SAFETY NOTES ........................................................................................... 1 - 1
SYMBOLS USED ON THE EQUIPMENT LABELLING ......................................... 1 - 1
PREVENTIVE MAINTENANCE ....................................................................... 1 - 2
Chapter 1: INSTALLATION .............................................................. 1 - 3
1.1 UNPACKING ........................................................................................ 1 - 3
1.2 MECHANICAL INSTALLATION ............................................................... 1 - 3
1.3 ELECTRICAL INSTALLATION ................................................................... 1 - 6
1.3.1 Supply voltage wiring .................................................................... 1 - 6
POWER REQUIREMENTS .............................................................. 1 - 6
1.3.2 EIA485 connections ...................................................................... 1 - 7
LED INDICATORS .......................................................................... 1 - 7
1.3.3 ETHERNET (100/10 Base-T) Connector ........................................... 1 - 8
1.3.4 USB Connector ............................................................................. 1 - 8
1.3.5 Wiring the Visual Supervisor to I/O units ........................................ 1 - 9
1.3.6 Profibus wiring ........................................................................... 1 - 10
Chapter 2: GETTING STARTED ........................................................ 2 - 1
2.1 SWITCH-ON AND THE OPENING DISPLAY ............................................ 2 - 1
2.1.1 Switch on ..................................................................................... 2 - 1
2.1.2 The standard interface ................................................................... 2 - 1
MAIN PANE ................................................................................. 2 - 2
PROGRAM PANE .......................................................................... 2 - 2
ALARM PANE ............................................................................... 2 - 2
LOGGING PANE .......................................................................... 2 - 2
ACCESS PANE ............................................................................. 2 - 2
RECIPE PANE ............................................................................... 2 - 2
NAVIGATION KEYS ...................................................................... 2 - 3
USER DEFINED KEYS .................................................................... 2 - 3
2.1.3 The opening display ...................................................................... 2 - 4
2.2 THE MAIN PANE .................................................................................. 2 - 5
2.2.1 Information display ....................................................................... 2 - 5
2.2.2 Information entry ........................................................................... 2 - 5
2.3 THE POP-UP MENU ............................................................................... 2 - 6
2.4 THE PROGRAM PANE ........................................................................... 2 - 7
2.4.1 Displaying program status ............................................................. 2 - 7
WITH NO PROGRAM LOADED ..................................................... 2 - 7
WITH A PROGRAM LOADED ......................................................... 2 - 7
2.4.2 Programmer menu access .............................................................. 2 - 7
2.5 THE PROGRAMMER MENU ................................................................... 2 - 8
2.6 THE ALARM PANE ................................................................................. 2 - 9
2.6.1 Alarm state indication ................................................................... 2 - 9
ACTIVE MESSAGE DISPLAY ......................................................... 2 - 10
2.6.2 Responding to alarms .................................................................. 2 - 10
DO NOTHING ........................................................................... 2 - 10
ALARM HISTORY PAGE ............................................................... 2 - 10
TWO LINE DISPLAY ..................................................................... 2 - 11
ALARM ACKNOWLEDGEMENT ................................................... 2 - 11
2.7 LOGGING PANE ................................................................................ 2 - 12
2.8 ACCESS PANE ................................................................................... 2 - 12
2.8.1 Gaining access ........................................................................... 2 - 12
STANDARD ACCESS ................................................................... 2 - 12
Contents HA029280
Page 2 Issue 5 Mar 08
LIST OF CONTENTS (Cont.)

Section Page
Chapter 3: OPERATION .................................................................. 3 - 1
3.1 RUNNING A PROGRAM ....................................................................... 3 - 1
3.1.1 Running a program now ................................................................ 3 - 1
3.1.2 Running from a point .................................................................... 3 - 3
3.1.3 Scheduling a program ................................................................... 3 - 4
3.1.3.1 SPECIFYING THE PROGRAM START DATE ......................... 3 - 5
3.1.3.2 SPECIFYING THE PROGRAM START TIME .......................... 3 - 5
3.1.3.3 CHANGING THE NUMBER OF ITERATIONS (RUNS) .......... 3 - 6
3.1.4 Segment skip ................................................................................ 3 - 7
3.1.4.1 SEGMENT TRANSITION CONSEQUENCES ...................... 3 - 7
FROM DWELL, SET OR SERVO (SP OR PV) TO ANY OTHER TYPE ..... 3 - 7
FROM RAMP TO SET .................................................................... 3 - 7
FROM RAMP TO DWELL ............................................................... 3 - 7
FROM RAMP TO END (STARTING VALUES) ..................................... 3 - 7
FROM RAMP TO COMPLETE (INFINITE DWELL) ............................... 3 - 7
TO RAMP FROM ANY OTHER TYPE ............................................... 3 - 7
3.2 HOLDING AND ABORTING A PROGRAM .............................................. 3 - 8
3.2.1 Holding a program ....................................................................... 3 - 8
3.2.2. Aborting a program ...................................................................... 3 - 8
3.3 MONITORING A PROGRAM ................................................................. 3 - 9
3.3.1 The monitor facility ........................................................................ 3 - 9
3.3.2 The preplot facility ...................................................................... 3 - 10
STANDARD DISPLAY MODE ......................................................... 3 - 10
REVIEW MODE .......................................................................... 3 - 10
3.4 LOGGING DATA ................................................................................ 3 - 11
3.4.1 Types of files .............................................................................. 3 - 11
ASCII ......................................................................................... 3 - 11
UHH .......................................................................................... 3 - 11
3.4.2 Name types ................................................................................ 3 - 11
TEXT .......................................................................................... 3 - 11
HOURLY ..................................................................................... 3 - 11
DAILY ......................................................................................... 3 - 11
SEQUENCE ............................................................................... 3 - 11
3.4.3 The Manage facility .................................................................... 3 - 12
ARCHIVE EXPORT ....................................................................... 3 - 12
3.4.4 Data integrity ............................................................................. 3 - 12
3.5 ALARMS / MESSAGE RESPONSE ........................................................ 3 - 13
TIME REPRESENTATION .............................................................. 3 - 13
3.5.1 Alarm history page ..................................................................... 3 - 13
TWO LINE DISPLAY ..................................................................... 3 - 14
FILTER KEYS ................................................................................ 3 - 14
ACK KEY ................................................................................... 3 - 15
ARCHIVE ................................................................................... 3 - 15
3.5.2 Alarm/Message Acknowledgement .............................................. 3 - 15
ALARMS .................................................................................... 3 - 15
MESSAGES ................................................................................ 3 - 15
3.5.3. Adding notes to alarm history ...................................................... 3 - 15
3.5.4 Alarm history archive .................................................................. 3 - 16
3.5.5 Alarm summary page .................................................................. 3 - 16
3.5.6 Event Log ................................................................................... 3 - 17
TWO LINE DISPLAY ..................................................................... 3 - 17
3.6 AREA AND GROUP DISPLAYS .............................................................. 3 - 18
3.6.1 Overview ................................................................................... 3 - 18
TREND DISPLAYS ........................................................................ 3 - 18
ALARM INDICATION .................................................................. 3 - 18
HA029280 Contents

Section Page
3.6.2 Function block faceplates ............................................................. 3 - 20
RAMP FACEPLATES ..................................................................... 3 - 20
PID FACEPLATES ......................................................................... 3 - 21
3.6.3 Display modes ............................................................................ 3 - 21
FACEPLATE DISPLAY .................................................................... 3 - 22
NUMERIC DISPLAY ..................................................................... 3 - 22
VERTICAL BARGRAPH ................................................................. 3 - 22
HORIZONTAL BARGRAPH ........................................................... 3 - 23
VERTICAL TREND WITH FACEPLATE .............................................. 3 - 23
VERTICAL TREND - FULL WIDTH ................................................... 3 - 25
HORIZONTAL TREND WITH FACEPLATE ....................................... 3 - 25
HORIZONTAL TREND - FULL WIDTH ............................................. 3 - 26
3.7 DOWNLOADING RECIPES .................................................................. 3 - 27
RECIPE SET SELECTION ............................................................... 3 - 28
3.7.1 Download procedure ................................................................... 3 - 28
LOADING THE RECIPE ................................................................ 3 - 28
SELECTING A RECIPE LINE .......................................................... 3 - 29
SELECTING A RECIPE .................................................................. 3 - 29
3.7.2 Monitoring the recipe .................................................................. 3 - 29
RECIPE STATUS PAGE .................................................................. 3 - 29
RECIPE MONITOR PAGE ............................................................. 3 - 30
3.8 BATCHES ........................................................................................... 3 - 31
3.8.1 Batch loading ............................................................................. 3 - 31
3.8.2 Recipe selection .......................................................................... 3 - 31
3.8.3 Batch customising ....................................................................... 3 - 31
3.8.4 Batch initiation ............................................................................ 3 - 32
3.8.5 Batch monitoring ......................................................................... 3 - 32
3.8.6 Batch Hold ................................................................................. 3 - 32
3.8.7 Batch Abort ................................................................................ 3 - 32
3.8.8 Batch Create .............................................................................. 3 - 33
Chapter 4: MANAGEMENT ............................................................. 4 - 1
4.1. EDITING A PROGRAM .......................................................................... 4 - 1
4.1.1 INTRODUCTION .......................................................................... 4 - 1
CREATING A PROGRAM ............................................................... 4 - 1
EDITING A PROGRAM .................................................................. 4 - 1
4.1.2 Program Editor Page access ........................................................... 4 - 3
4.1.3 Changing a setpoint ...................................................................... 4 - 4
CHANGING RAMP TYPE .............................................................. 4 - 4
TERMINOLOGY ............................................................................ 4 - 4
TO CHANGE THE TYPE OF RAMP ................................................. 4 - 5
CHANGING SETPOINT VALUE ...................................................... 4 - 6
4.1.4 Changing a segment ..................................................................... 4 - 7
CHANGING SEGMENT IDENTIFIER ............................................... 4 - 7
CHANGING SEGMENT DURATION ............................................... 4 - 8
4.1.5 Inserting/deleting segment ............................................................. 4 - 8
INSERTING A NULL SEGMENT ...................................................... 4 - 8
DELETING A SEGMENT ................................................................ 4 - 9
4.1.6 Changing hold back properties ...................................................... 4 - 9
CHOOSING THE SETPOINT ........................................................ 4 - 10
CHANGING HOLD BACK MODE ................................................ 4 - 10
CHANGING HOLDBACK VALUES ................................................ 4 - 10
4.1.7 Changing program properties ...................................................... 4 - 11
CHANGING PROGRAM NAMES ................................................. 4 - 11
CHANGING RATE UNITS ............................................................ 4 - 12
CHOOSING END-OF-RUN ACTION ............................................ 4 - 12
CHANGING DEFAULT ITERATIONS .............................................. 4 - 13
4.1.8 Changing setpoint names ............................................................. 4 - 13
4.1.9 Segment timing display ............................................................... 4 - 14
Contents HA029280

Section Page
4.2 LOGGING GROUPS OF DATA ............................................................. 4 - 15
4.2.1 Log initiation .............................................................................. 4 - 15
LOG CONFIGURATION .............................................................. 4 - 16
4.2.2 FTP Transfer ................................................................................ 4 - 18
MULTIPLE COPY MODE ............................................................... 4 - 18
SINGLE COPY MODE ................................................................. 4 - 18
CONFIGURATION ...................................................................... 4 - 18
4.3 MANAGING AN APPLICATION ........................................................... 4 - 19
4.3.1 Application summary page .......................................................... 4 - 20
4.3.2 Application manager page .......................................................... 4 - 20
4.3.3 Stopping an application .............................................................. 4 - 21
4.3.4 Saving application data .............................................................. 4 - 22
4.3.5 Unloading an application ............................................................ 4 - 22
4.3.6 Loading or loading and running an application ............................. 4 - 23
APPLICATION SELECTION ........................................................... 4 - 23
APPLICATION LOADING ............................................................. 4 - 23
4.3.7 Deleting an application ............................................................... 4 - 23
4.3.8 Function Block Manager .............................................................. 4 - 24
ALPHA-NUMERIC BLOCK DISPLAY ................................................ 4 - 26
FUNCTION BLOCK DETAILS ........................................................ 4 - 27
4.4 CONTROLLING ACCESS ..................................................................... 4 - 27
4.4.1 First-time access .......................................................................... 4 - 28
4.4.2 Editing the passwords .................................................................. 4 - 28
4.4.3 User ID system ............................................................................ 4 - 30
CHANGING TO THE USER ID SYSTEM ........................................ 4 - 30
USER ID MANAGEMENT ............................................................ 4 - 31
4.5 SETTING UP AND RE-SETTING THE INSTRUMENT ................................. 4 - 35
4.5.1 Editing communications parameters .............................................. 4 - 35
SOFTWARE PARAMETER EDITING ................................................ 4 - 36
PROTOCOLS AVAILABLE .............................................................. 4 - 36
TALK-THRU ................................................................................. 4 - 36
ETHERNET .................................................................................. 4 - 37
MODBUS/TCP ........................................................................... 4 - 38
4.5.2 Setting the start-up strategy .......................................................... 4 - 39
HOT/COLD START CRITERIA ........................................................ 4 - 39
START-UP STRATEGY PAGE .......................................................... 4 - 39
CHANGING START-UP VALUES .................................................... 4 - 40
4.5.3 Resetting the clock ....................................................................... 4 - 41
CLOCK SETUP PAGE ACCESS ..................................................... 4 - 41
CHANGING DATE AND TIME ..................................................... 4 - 41
TIME CHANGING ...................................................................... 4 - 42
4.5.4 Changing language and date/time formats ................................... 4 - 42
LANGUAGE ............................................................................... 4 - 43
DATE FORMAT ........................................................................... 4 - 43
TIME FORMAT ............................................................................ 4 - 43
4.5.5 Setting up the panel display ......................................................... 4 - 44
ACCESS TO THE PANEL SETUP PAGE ........................................... 4 - 44
DISPLAY BRIGHTNESS SETTINGS ................................................. 4 - 44
TIME-OUTS ................................................................................. 4 - 45
DATA ENTRY .............................................................................. 4 - 45
4.6 CLONING AN INSTRUMENT ............................................................... 4 - 46
4.6.1 Accessing the cloning page ......................................................... 4 - 46
4.6.2 Cloning application data ............................................................. 4 - 47
EXPORTING APPLICATION DATA ................................................. 4 - 47
IMPORTING APPLICATION DATA ................................................ 4 - 47
HA029280 Contents

Section Page
4.6.3 Cloning system (instrument) data .................................................. 4 - 48
SELECTING SYSTEM DATA .......................................................... 4 - 48
EXPORTING SYSTEM DATA ......................................................... 4 - 48
IMPORTING SYSTEM DATA ........................................................ 4 - 48
4.6.4 Cloning both application and system data (ALL) ............................. 4 - 49
4.7 FILE MANAGER .................................................................................. 4 - 50
4.7.1 Stopping the application .............................................................. 4 - 50
4.7.2 Calling the file manager .............................................................. 4 - 50
4.7.3 File Copy and Delete ................................................................... 4 - 51
4.7.4 Reloading the application ............................................................ 4 - 52
4.8 RECIPE MANAGEMENT ...................................................................... 4 - 52
4.8.1 Creating recipe files .................................................................... 4 - 52
4.8.2 Recipe editing ............................................................................ 4 - 52
ADD RECIPE LINE ....................................................................... 4 - 52
ADD A VARIABLE ........................................................................ 4 - 53
TAG REFERENCES ...................................................................... 4 - 53
RECIPE VALUE ............................................................................ 4 - 53
ADDING A RECIPE ..................................................................... 4 - 53
DELETING RECIPES ..................................................................... 4 - 53
SAVING RECIPES ........................................................................ 4 - 54
RECIPE FILE PROPERTIES ............................................................. 4 - 54
4.8.3 Capturing a Recipe ..................................................................... 4 - 54
4.9 OEM FEATURES .................................................................................. 4 - 55
4.9.1 Intellectual Property Right Protection (IPRP) ..................................... 4 - 55
MODIFYING IPRP SETTINGS ....................................................... 4 - 55
4.10 BATCH MAINTNEANCE .................................................................... 4 - 56
Chapter 5: CUSTOMISING ...............................................................5 - 1
5.1 INTRODUCTION ................................................................................... 5 - 1
5.1.1 The dictionaries ............................................................................ 5 - 1
5.1.2 Panel navigation and database names ............................................ 5 - 2
5.2 THE SYSTEM TEXT DICTIONARY ............................................................. 5 - 2
5.2.1 File structure .................................................................................. 5 - 2
5.2.2 Editing system text ......................................................................... 5 - 3
5.2.3 New language versions ................................................................. 5 - 3
5.2.4 The dictionary ............................................................................... 5 - 3
5.2.5 Panel customisation using the dictionary ......................................... 5 - 24
5.2.6 Alarm/event customisation using the dictionary ............................. 5 - 26
5.3 THE ERROR TEXT DICTIONARY ............................................................ 5 - 27
5.3.1 Editing error messages ................................................................ 5 - 28
5.3.2 Creating new language error text ................................................. 5 - 28
PROCEDURE .............................................................................. 5 - 28
5.4 THE EVENT TEXT DICTIONARY ............................................................ 5 - 29
5.4.1 Editing Event Messages ............................................................... 5 - 33
5.4.2 Creating new language event text ................................................ 5 - 33
PROCEDURE .............................................................................. 5 - 33
5.4.3 Event priorities ............................................................................ 5 - 33
5.5 THE USER TEXT DICTIONARY ............................................................... 5 - 34
5.6 THE PROGRAMMER TEXT DICTIONARY ................................................ 5 - 34
5.7 PANEL NAVIGATION .......................................................................... 5 - 35
5.7.1 The Panel Navigation file ............................................................. 5 - 35
THE VERSIONS .......................................................................... 5 - 35
AUDITOR OPTION VERSIONS ..................................................... 5 - 39
5.7.2 Editing the _default.pnl file ........................................................... 5 - 42
Contents HA029280

Section Page
5.7.3 Line types ................................................................................... 5 - 43
PANEL AGENT DECLARATION ..................................................... 5 - 43
PANEL DRIVER DECLARATION ..................................................... 5 - 44
HOME PAGE DECLARATION ....................................................... 5 - 45
ROOT PAGE DECLARATION ....................................................... 5 - 45
INITIAL PAGE DECLARATION ...................................................... 5 - 45
5.7.4 Agent types ................................................................................ 5 - 46
5.8 DATABASE NAMES ............................................................................. 5 - 48
5.8.1 Function block names .................................................................. 5 - 48
5.8.2 Alarm names .............................................................................. 5 - 48
5.8.3 Enumerations .............................................................................. 5 - 49
TAGS ......................................................................................... 5 - 49
5.9 FORM FILES ........................................................................................ 5 - 50
5.9.1 Report forms ............................................................................... 5 - 50
UYF FILE ENTRIES ....................................................................... 5 - 51
5.9.2 Alarm forms ............................................................................... 5 - 54
EXAMPLE ................................................................................... 5 - 54
5.10 RECIPE FILES ..................................................................................... 5 - 55
5.10.1 Basic Recipe File ....................................................................... 5 - 55
FILE HEADER .............................................................................. 5 - 55
TITLE LINE .................................................................................. 5 - 56
VARIABLE LINES .......................................................................... 5 - 56
BASIC FILE EXAMPLE ................................................................... 5 - 56
5.10.2 More complex files .................................................................... 5 - 57
MULTI-LINE FILES ......................................................................... 5 - 57
FILES WITH OPTIONAL CAPTURE VARIABLES ................................ 5 - 57
FILES WITH OPTIONAL MONITOR VARIABLES .............................. 5 - 58
5.11 WRITABLE DICTIONARY .................................................................... 5 - 58
5.12 THE RECIPE DICTIONARY .................................................................. 5 - 59
5.13 THE BATCH DICTIONARY ................................................................... 5 - 60
5.13.1 Example ................................................................................... 5 - 60
5.14 BATCH FILES ...................................................................................... 5 - 61
5.14.1 File Header ............................................................................... 5 - 61
5.14.2 Batch Phases ............................................................................. 5 - 62
5.15 DATABASE CHANGE AUDIT TRAILING ................................................ 5 - 63
5.15.1 Header Line ............................................................................... 5 - 63
5.15.2 Item Lines .................................................................................. 5 - 63
Chapter 6: ADMINISTRATIVE FUNCTIONS ....................................... 6 - 1
6.1 NETWORK AUDIT TRAIL ........................................................................ 6 - 1
6.1.1 Modes ......................................................................................... 6 - 2
6.1.2 Configuration (Provider) ................................................................ 6 - 2
CONSUMER SELECTION .............................................................. 6 - 2
AUDIT TRAIL FILTERING ................................................................. 6 - 2
PARAMETERS ............................................................................... 6 - 2
6.1.3 User ID control .............................................................................. 6 - 3
SECURITY ACCESS DISPLAY PAGE ................................................. 6 - 3
EXPIRES ....................................................................................... 6 - 5
SCREEN KEYS .............................................................................. 6 - 5
6.2 ELECTRONIC SIGNATURES .................................................................. 6 - 10
6.2.1 Enabling electronic signatures ...................................................... 6 - 10
6.2.2 Signature Configuration ............................................................... 6 - 11
ACCESS LEVELS ......................................................................... 6 - 11
HA029280 Contents

Section Page
Chapter 7: REMOTE ACCESS ........................................................... 7 - 1
7.1 FTP ...................................................................................................... 7 - 1
7.1.1 FTP logon ..................................................................................... 7 - 1
TIMEOUT ..................................................................................... 7 - 1
7.1.2 File system .................................................................................... 7 - 1
7.1.3 Archive File Transfer ...................................................................... 7 - 1
Chapter 8: THE CONTROL CONFIGURATOR .................................... 8 - 1
8.1 OVERVIEW .......................................................................................... 8 - 1
8.2 PREPARATION ...................................................................................... 8 - 1
8.2.1 Configurator mode selection .......................................................... 8 - 1
8.2.2 Control efficiency selection ............................................................ 8 - 1
8.3 RUNNING THE CONFIGURATOR .......................................................... 8 - 2
8.3.1 Initial menu access ........................................................................ 8 - 2
8.3.2 The Initial menu ............................................................................ 8 - 3
8.3.3 Quitting the VDU package & CPU configuration mode ...................... 8 - 3
8.4 DATABASE CONFIGURATION ............................................................... 8 - 3
8.4.1 MAKE .......................................................................................... 8 - 4
BLOCK OVERVIEW ....................................................................... 8 - 4
CONNECTION TYPES IN A CPU DATABASE .................................. 8 - 8
8.4.2 COPY .......................................................................................... 8 - 8
8.4.3 DELETE ......................................................................................... 8 - 8
8.4.4 INSPECT ...................................................................................... 8 - 9
8.4.5 NETWORK ................................................................................... 8 - 9
8.4.6 Utilities ....................................................................................... 8 - 10
START, STOP UTILITIES ................................................................. 8 - 10
SAVE UTILITY .............................................................................. 8 - 10
LOAD UTILITY ............................................................................. 8 - 10
FILE UTILITY ................................................................................ 8 - 11
8.4.7 ALARMS .................................................................................... 8 - 11
8.4.8 ALARM LOG .............................................................................. 8 - 11
8.4.8 EVENT LOG ............................................................................... 8 - 11
8.5 MODBUS CONFIGURATION ............................................................. 8 - 12
8.5.1 GW index .................................................................................. 8 - 12
8.5.2 MODE ....................................................................................... 8 - 12
8.5.3 INTERFACE ................................................................................ 8 - 13
8.5.4 SETUP ........................................................................................ 8 - 13
SERIAL MASTER .......................................................................... 8 - 13
SERIAL SLAVE ............................................................................. 8 - 13
TCP MASTER .............................................................................. 8 - 13
TCP SLAVE ................................................................................. 8 - 13
8.5.5 TABLES ....................................................................................... 8 - 15
TABLES LIST ................................................................................ 8 - 15
TABLE MENUS ............................................................................ 8 - 17
Chapter 9: PREVENTIVE MAINTENANCE ......................................... 9 - 1
9.1 BATTERY REPLACEMENT ........................................................................ 9 - 1
9.1.1 Replacement procedure ................................................................. 9 - 1
9.2 TOUCH SCREEN CALIBRATION ............................................................. 9 - 2
Chapter 10: PROFIBUS MASTER OPTION ...................................... 10 - 1
10.1 INTRODUCTION ............................................................................... 10 - 1
10.2 INSTALLATION .................................................................................. 10 - 1
10.2.1 Mechanical installation .............................................................. 10 - 1
10.2.2 Pinout details ............................................................................ 10 - 1
10.3 FUNCTION BLOCKS ......................................................................... 10 - 4
10.3.1 GWProfM CON ....................................................................... 10 - 4
Contents HA029280

Section Page
Chapter 11: FLUSH MOUNTING OPTION INSTALLATION ............... 11 - 1
11.1 UNPACKING .................................................................................... 11 - 1
11.2 MECHANICAL INSTALLATION ........................................................... 11 - 1
11.2.1 Specification ............................................................................ 11 - 2
Appendix A: TECHNICAL SPECIFICATION ........................................ A - 1
General specification .................................................................................... A - 1
Communications specification ........................................................................ A - 3
Function Blocks supported ............................................................................. A - 4
Appendix B: OPTIONS UPDATE ...................................................... B - 1
B1 INTRODUCTION .................................................................................... B - 1
B2 SOFTWARE OPTIONS UTILITY ACCESS ................................................... B - 1
Appendix C: REFERENCE ................................................................. C - 1
C1 ASCII CODES ........................................................................................ C - 1
C2 GLOSSARY ........................................................................................... C - 2
Index ............................................................................................... i -1
HA029280 Contents
This page is deliberately left blank
Contents HA029280
SAFETY NOTES
WARNING!
This unit is intended for use with low voltage dc supplies. Connection of mains (line) supply voltages will
not only damage the unit, but may also cause an electrical shock hazard to be present at operator accessible
surfaces.
WARNING!
The supply voltage connector has two 0V pins, commoned together by the circuit board backplane, and two
24V (nom) pins which are also shorted together internally. This allows easy ‘daisy-chaining’ of multiple
units. Two separate power supply units may not be connected as to do so may result in damage to the unit,
and/or a potential fire or explosion hazard.
CAUTION
Local lightning protection must be fitted if the dc power supply unit is located more than 30 metres from the
visual supervisor(s) it is supplying.
Note: in order to comply with the requirements of safety standard BS EN61010, the recorder shall have one
of the following as a disconnecting device, fitted within easy reach of the operator, and labelled as the discon-
necting device.
a. A switch or circuit breaker which complies with the requirements of IEC947-1 and IEC947-3
b. A separable coupler which can be disconnected without the use of a tool
c. A separable plug, without a locking device, to mate with a socket outlet in the building.
1. If a hazard could arise from an operator’s reliance on a value displayed by the equipment, the display must give
an unambiguous indication (e.g. a flashing alarm) whenever the value is over range or under range.
2. Where conductive pollution (e.g. condensation, carbon dust) is likely, adequate air conditioning/filtering/sealing
etc. must be installed in the equipment enclosure.
3 The equipment is designed for process monitoring and supervision in an indoor environment. If the equipment is
used in a manner not specified by the manufacturer, the protection provided by the equipment might be impaired.
4. The battery within the unit must not be short circuited. When exhausted, the battery must be disposed of in ac-
cordance with local regulations for poly-carbonmonofluoride/lithium cells.
5. When connecting a USB device, it must be plugged directly into the instrument. The use of extension USB leads
may compromise the unit’s ESD compliance.
6. There are no specific insulation requirements for external circuitry.
7. In order to comply with CE requirements, the Protective-conductor terminal must be connected to a protective
conductor.
SYMBOLS USED ON THE EQUIPMENT LABELLING

One or more of the symbols below may appear as a part of the unit's labelling.
Refer to the manual

! for instructions Ethernet connector
Protective-conductor USB connector

terminal
This instrument Serial communications

for dc supply only connector
Precautions against static elec- For environmental reasons, this

trical discharge must be taken unit must be recycled before
when handling this unit. its age exceeds the number of
years shown in the circle.
Caution
When accessing the battery, or setting DIP switches etc. the operator must be at the same electrical potential
as the casing of the instrument.
When fitting USB devices, both the operator and the device must be at the same electrical potential as the
casing of the instrument.
HA029280 Chapter 1
Issue 5 Mar 08 Page 1 - 1
PREVENTIVE MAINTENANCE
The unit may be cleaned using a lint-free cloth, moistened if necessary with a weak detergent solution. Aggressive
cleaning materials such as isopropyl alcohol may not be used as they damage the touch screen.
The average life of the battery is approximately five years. It is recommended that the ‘BadBatt’ flag is set in the
database header block, to trigger an instrument alarm when the battery needs to be replaced. The battery should be
replaced as soon as possible after the appearance of this alarm.
Chapter 1 HA029280
Page 1 - 2 Issue 5 Mar 08
CHAPTER 1: INSTALLATION
Note: See also chapter 10 for installation details for units fitted with the Profibus option and chapter 11 for
details of the ‘Flush-mounting’ option.
This chapter is intended for use by those responsible for the installation and commissioning of the instrument and
consists of the following sections:
1.1 Unpacking
1.2 Mechanical installation
1.3 Electrical installation
1.1 UNPACKING
The unit is despatched in a special pack designed to protect it during transit.
If the outer box of the pack shows signs of damage, please open it immediately and examine the instrument. If there is
evidence of damage, contact the manufacturer’s local representative for instructions. Do not operate the instrument in
the meantime.
If the outer box is not damaged, remove the instrument from its packing with all accessories and documentation.
Once the unit has been installed, store any internal packing with the external packing in case of future despatch.
1.2 MECHANICAL INSTALLATION
1. Check that the mounting panel is no thicker than 22mm (typically for wood or plastic) and no thinner than 2mm
(for steel).
2. In the panel, cut an aperture 138mm x 138mm (small frame) or 281mm x 281mm (large frame). If more than one
instrument is to be mounted in the panel, the recommended minimum spacings are as shown in figure 1.2a/1.2b.
3. From the front side of the mounting panel, insert the instrument (rear end first) through the aperture.
4. Insert the two panel clamps into the rectangular apertures at the sides of the instrument case.
5. Whilst ensuring that the sealing gasket is flat against the front of the panel, tighten the screws of the clamps suffi-
ciently to hold the unit firmly in position. IMPORTANT: Do not use excessive force to tighten the screws. It could
distort the case and render the instrument inoperative.
HA029280 Chapter 1
1.2 MECHANICAL INSTALLATION (Cont.)
6.7 mm
144.0 mm 87.7 mm
Profibus option
(chapter 10)
137.0 mm
144.0 mm
CL
Fixing Clip
(one each side)
F1 F2 F3
F4 F5 F6
Protective-conductor
terminal (M4)
Panel thickness: Max = 22 mm; Min = 2 mm
Flash card Panel cutout

USB
138 mm x 138 mm
– – + +
(both -0 + 1 mm)
Ethernet Serial comms Power
Profibus Option
(Chapter 10)
137.5 mm
154.5 mm
170.5 mm
PANEL MOUNTING DETAILS
Installed panel angle: Vertical panels only

Minimum inter-unit spacing: 50 mm. vertical or horizontal.
Note: where multiple units are mounted in close proximity

with one another, steps must be taken to ensure that the
resulting ambient temperature does not exceed the speci-
fied maximum operating temperature of 50 degrees Celsius
Figure 1.2a Small-frame unit mechanical installation
Chapter 1 HA029280
9.6 mm
288.0 mm 70.4 mm
Profibus option
(Chapter 10)
280.3 mm
288.0 mm
CL
Fixing Clip
(one each side)
F1 F2 F3 F4 F5 F6 F7 F8 F9
F10 F11 F12 F13 F14 F15 F16 F17 F18
F19 F20 F21 F22 F23 F24 F25 F26 F27 Protective-conductor
terminal (M4)

Serial
Ethernet Comms Power
Flash card
USB
– –++
Profibus option
(Chapter 10)
281.4 mm
298.4 mm Panel cutout = 282 mm x 282 mm
314.4 mm (both -0 + 1.3mm


Figure 1.2b Large-frame unit mechanical installation
HA029280 Chapter 1
1.3 ELECTRICAL INSTALLATION

Note: Before carrying out any wiring, please read the Safety Notes and warnings preceding this chapter.
1.3.1 Supply voltage wiring
The 24V dc supply voltage wiring is terminated at a four-way connector located on the underside of the unit, as shown
in figure 1.2a or 1.2b. The supply wiring should be terminated as shown in figures 1.3.1a, and 1.3.1b, below.
Note: Pins 1 and 2 are internally connected together, as are pins 3 and 4.
POWER REQUIREMENTS
Voltage range: 19.2 to 28.8 V dc (24V dc ± 20%)
Permissible ripple: 1 V max.
Maximum power requirements (at 24 V): Small frame = 20 Watts; Large frame = 24 Watts
Inrush current: 10A
Internal fusing: Not user replaceable
Front of instrument
– – + +
19.2 to 28.8V dc
Figure 1.3.1 a Supply voltage wiring

(view on underside of instrument)
Process supervisor 1 Process supervisor 2 Process supervisor

(Rear view) (Rear view) (Rear view)
24 24 0V 0V 24 24 0V 0V 24 24 0V 0V
Disconnect
device
24V 0V 24V 0V 24V 0V

19.2 to 28.8V dc Line 19.2 to 28.8V dc 19.2 to 28.8V dc
power supply supply power supply power supply
unit unit unit
Daisy-chain unit wiring

Disconnect Disconnect
device device
Line Line
supply supply
Redundant supplies
Figure 1.3.1b Supply voltage connection examples
Chapter 1 HA029280
1.3.2 EIA485 connections
This pair of adjacent RJ45 connectors, are located on the underside of the instrument, as shown in figures 1.2a and
1.2b. These connectors can be configured, by means of a 4-gang DIP switch each, as Master or Slave. Further sec-
tions of the switches allow 120Ω terminating resistors to be switched in and out of circuit. The DIP switches are ac-
cessible by removing the access cover at the rear of the unit.
Table 1.3.2a shows the pinout for master and slave connections. Figure 1.3.2 and table 1.3.2b show the switch details
for the small frame unit (large frame unit similar).
Note: When using a EIA485 port to communicate with a printer, the master or slave connection should be
chosen according to the type of cable being used.
5 wire 5 wire 3-Wire
Pin
Master Slave Master/Slave
1 RxB TxB B
pin 1
2 RxA TxA A
3 Common Common Common
4 NC NC NC
pin 8
5 NC NC NC
RJ 45 plug: View on underside 6 Common Common Common
7 TxB RxB NC
8 TxA RxA NC
Table 1.3.2a Serial communication port pinout.
Caution
BR2330 The user must be at the same electrical potential
as the instrument housing when accessing
internal items such as batteries and switches.
Cover retaining
screw location
Segment ON (left) OFF (right)

1 2 3 4
1 2 3 4
4 Slave Master
ON
ON
3 5-wire 3-wire
120 Ohm terminating
No terminating resistor
2 resistor fitted across
Port 1 Port 2 across pins 7 and 8
pins 7 and 8
Serial communications Ethernet
ports connector 120 Ohm terminating
1 resistor fitted across No terminating resistor
pins 1 and 2 across pins 1 and 2
Figure 1.3.2 Table 1.3.2b Communications DIP switch settings

Serial communications hardware configuration
LED INDICATORS
There are two LED indicators associated with the Serial Communications RJ45 connectors:
The yellow LED indicates when the unit is transmitting.
The green LED illuminates when 5-wire (full duplex) communications is selected (see above).
HA029280 Chapter 1
1.3.3 ETHERNET (100/10 Base-T) Connector
The pinout for the Ethernet RJ45 connector is as shown in figure 1.3.3, below. The connector is located on the under-
side of the unit, as shown in figure 1.2a and figure 1.2b, above.
Note: The LED indicators integral with the connector socket are not used in this application.
ELIN
1 TxD+
2 TxD-
pin 8 3 RxD+
4 Not used
5 Not used
pin 1
6 RxD-
RJ 45 plug: View on underside 7 Not used
8 Not used
Plug shroud wired to
cable screen
Figure 1.3.3 Ethernet (ELIN) connector pinout.
1.3.4 USB Connector
This connector may be used only for the connection of USB Bulk storage devices (‘memory sticks’). The connector
pinout is shown in figure 1.3.4. The connector is located on the underside of the unit, as shown in figure 1.2a and
figure 1.2b, above.
Note: Compliance with EMC directives cannot be guaranteed if the Bulk Storage Device is connected using
an extension cable.
Pin Definition
1 + 5V
2 USB - (D-)
1 2 3 4 3 USB + (D+)
4 Ground
View on non-solder
end of fixed socket
Figure 1.3.4 USB connector pinout
Caution
Both the user and the peripheral (e.g. USB device) must be at the same electrical potential as the instrument
housing before the peripheral is connected.
Chapter 1 HA029280
1.3.5 Wiring the Visual Supervisor to I/O units
For a fixed, permanent installation, cables should be a low-loss type (Eurotherm part no. S9508-5/2RJ45/xxx/- , where
xxx is the length in metres, with an implicit decimal point as in ‘xx.x’, and a maximum of 99.9 metres). For a tempo-
rary set-up, cables can be general purpose types. Category 5 cable can be used for runs of up to 100 metres. For runs
greater than this, one or more pairs of hubs using fibre optic connection is recommended.
Wiring between the Visual Supervisor and I/O units may be carried out using the EIA485 connectors, or the Ethernet
connector, all of which are located at the rear of the unit, as shown in figure 1.2a and 1.2b. Figure 1.3.5a shows two
simple wiring examples. Figure 1.3.5b gives a more complex example. For full details of the I/O unit wiring, consult
the documentation supplied with the I/O unit.
Visual supervisor
rear panel T2550R
I/O unit
EIA485 Master port

(RJ45)
Using serial comms
Visual supervisor
rear panel T2550R
Network Switch (RSTP) I/O unit Set up each I/O unit to
have a unique address.
T2550R
I/O unit
Ethernet port
(RJ45)
T2550R
I/O unit
Using Ethernet
Figure 1.3.5a. Visual Supervisor to I/O unit wiring examples (simplex operation).
HA029280 Chapter 1
1.3.5 WIRING THE VISUAL SUPERVISOR TO I/O UNITS (Cont.)
Supervisory PC
Visual supervisor
rear panel
Network Switch (RSTP) Network Switch (RSTP)
Ethernet port T2550R

(RJ45) I/O unit
T2550R
I/O unit
Figure 1.3.5b Visual Supervisor to I/O unit wiring example (redundant I/O operation)
1.3.6 Profibus wiring
Refer to chapter 10 for details of the Profibus Master 9-way D-Type connector,
Refer to the Modbus/Profibus communications handbook (HA028014) for Profibus network topology recommenda-
tions.
Chapter 1 HA029280
CHAPTER 2: GETTING STARTED
This chapter consists of the following sections:

2.1 Switch-on, and the opening display, including the navigation keys
2.2 The Main pane: information entry and display
2.3 The Pop-up menu
2.4 The Program pane
2.5 The Programmer menu
2.6 The Alarm pane
2.7 The Logging pane
2.8 The Access pane
2.1 SWITCH-ON AND THE OPENING DISPLAY
2.1.1 Switch on
The Instrument is not fitted with a power switch, so the switch-on arrangements depend upon the particular installa-
tion. After switch-on, the screen will remain blank for a few seconds before brightening, then, after approximately 15
seconds, an opening display appears that fills most or all of the screen area.
Note: The user interface is open to customisation, either before operation or with the instrument taken out of
service. For example the opening page (called the Home page) can differ, other pages can be changed, and
‘User pages’ (‘User screens’) can be added. The size of the panes can differ, the legends on the buttons can
differ, and indeed the buttons need not exist at all. In the extreme the entire architecture of the interface can
differ.
Chapters 2 to 4 of this manual describe the system of menus and pages supplied by the manufacturer, before
any customisation by the user. This menu system is called the Standard Interface. Chapter 5 describes how to
customise this Standard Interface, if required.
2.1.2 The standard interface
The Standard Interface consists of a number of display ‘panes’ and a group of ‘Navigation’ keys as described below.
Figure 2.1.2a shows a small-frame (1/4 VGA) unit; figure 2.1.2b, a large-frame (XGA) unit. (These drawings are not
to the same scale).
1/0
RESET
System Summary
Program Alarm Pane

Pane
Page title bar
Main pane
Up
MENU KEY
Left Right F1 User definable
F2 F3
Down keys
OPTION KEY F4 F5 F6
Figure 2.1.2a 1/4 VGA layout
HA029280 Chapter 2
2.1.2 THE STANDARD INTERFACE (Cont.)
TREND Run prog 3/5

LOCKED EYCON-20 BADBAT
RUNNING 05:07:45 2 TREND Fred
Page Title
Program Pane Alarm Pane

Recipe Pane
Logging Pane Access Pane
Page title bar
Main pane
MENU KEY Up F1 F2 F3 F4 F5 F6 F7 F8 F9
User definable
Left Right F10 F11 F12 F13
k eF14
y s F15 F16 F17 F18
OPTION KEY Down F19 F20 F21 F22 F23 F24 F25 F26 F27
Figure 2.1.2b XGA screen layout
MAIN PANE
This area contains the keys, menus, pick-lists, dialogue boxes, windows and pages that make up the standard menu
system of the Visual Supervisor.
PROGRAM PANE
This displays information about the state of the program that is currently loaded or running.
ALARM PANE
This displays alarm signals and messages.
LOGGING PANE
For XGA units only, touching this area calls the logging menu to the main pane. The logging pane does not appear on
1/4VGA units.
ACCESS PANE
For XGA units only, displays the currently logged-in user. Touching this area calls the access menu to the main pane.
The access pane does not appear on 1/4VGA units.
RECIPE PANE
For XGA units, fitted with the recipe software option only, this pane shows the status of the current recipe line. See
chapters 3 and 4 for details of the recipe application.
Chapter 2 HA029280
2.1.2 THE STANDARD INTERFACE (Cont.)
NAVIGATION KEYS
Up
Menu key Right

Left
Option key
Down
Figure 2.1.2c The Navigation keys
These touch-sensitive printed keys at the bottom of the screen carry the following functions:
UP Goes up one level of menu hierarchy.

DOWN Goes down one level or cycles the screen according to context.
LEFT Jumps across (left) in the hierarchy, at the same level. Also moves forward (left) between
successive pages of tabular data. Action depends upon context.
RIGHT Jumps across (right) in the hierarchy, at the same level. Also moves back (right) between
successive pages of tabular data. Action depends upon context.
OPTION Brings up a menu, or an extra set of keys, for options specific to the page on display.
MENU Brings up the main (top-level) Pop-up menu of the hierarchy.
USER DEFINED KEYS

These keys, F1 to F6, or F1 to F27, according to model, are configurable using User Screen Editor software running in
a PC. This software, available from the Process Supervisor manufacturer includes a full Help system to explain how
to carry out user screen configuration. A printable (html) form of this help system is downloadable under part number
HA260749U005.
HA029280 Chapter 2
2.1.3 The opening display

Note: if the system has been configured with an overview screen, then the opening display will be that
overview screen - refer to section 3.6.
The opening display of the Standard Interface is the System Summary page depicted in figure 2.1.3, below.
*** No application loaded ***

16:33:09 System Summary 03/04/06
Touch/keypad: TOUCH
Firmware: V1.0
DRAM: 64 MBytes
SRAM: 256 kBytes
Internal Archive: 45 MBytes
Figure 2.1.3 System Summary page
The System Summary page confirms the order options that were specified for this instrument.
Initially the opening display is ‘Locked’. In this state, the only interactive items are the Menu key, and, for the XGA
version of the instrument only, the ACCESS pane. Operation of the menu key causes the opening ‘Pop-up’ menu of
the Standard Interface to appear (section 2.3). Operation of the ACCESS pane calls the Security access page as de-
scribed in section 2.8 of this manual. This allows the display to be unlocked using an appropriate password or an
ident.
Chapter 2 HA029280
2.2 THE MAIN PANE
The Main pane is the display area for collecting information from the user by means of keys, menus, pick-lists, dia-
logue boxes and windows; and for displaying information to the user by means of dialogue boxes, windows, panes
and pages.
2.2.1 Information display

The Standard Interface is a menu system whose structure is hierarchical like a family tree. At the top is the Pop-up
menu which offers a choice of submenus as depicted below.
ACCESS SYSTEM ALARMS
OVERVIEW PROGRAMMER RECIPE
LOGGING HOME
Figure 2.2.1 The Standard Interface: top level
ACCESS, SYSTEM and ALARMS appear on every instrument; others appear only if configured. Of these, PRO-
GRAMMER and RECIPE are the most frequently used. Below this menu level, there are usually two or three further
levels of functions that give users successively more detailed control of different aspects of programs, applications,
and the instrument itself.
2.2.2 Information entry
Information entry is by touching areas on the screen with a finger, the eraser end of a pencil or similar. Hard, sharp or
pointed implements such as pens, keys and fingernails must never be used or damage will be caused to the touch
screen.
The keys and other items of the Standard Interface which appear in the Main Pane are not all touch-sensitive, and
those that are sensitive (‘active’) are not active all the time. You can tell which items are active at any time by their
pale yellow background, and you can tell which active item was the last one you selected by its bright yellow back-
ground.
HA029280 Chapter 2
2.3 THE POP-UP MENU

NOTE: In the following description of the Pop-up menu, and indeed of all the screen displays throughout this
manual, it is important to note that almost everything is open to customisation. On any particular instrument
the legends on the buttons can be different from those shown here, indeed the buttons need not exist at all, and
in fact the whole architecture of the interface can differ.
Throughout this manual what is called the Standard Interface is described. This is generated by the manufac-
turer, before any customisation by the user. This is not the same as the Minimum Interface, which is generated
by the minimum configuration necessary for the instrument to function.
The Minimum Interface Pop-up menu consists of three panes: ACCESS, SYSTEM and ALARMS. With the display
‘Locked’ - that is, before a password is entered and access gained, only ACCESS and SYSTEM are active.
However, most users will operate the Standard Interface. This features five more panes: PROGRAMMER, LOG-
GING, OVERVIEW, RECIPE and HOME/USER SCREENS. In this case, with the display locked, ACCESS, SYS-
TEM, OVERVIEW and HOME/USER SCREENS will be active. Other (i.e. non-active) keys are distinguishable by
having their text in white.
BATCH LOGGING HOME
Figure 2.3. The ‘Standard’ Pop-up menu, display locked
From this menu, without a password, menu systems can be explored and information displayed. The SYSTEM,
OVERVIEW and USER SCREENS displays are view-only at this locked stage; only ACCESS will respond fully to
menu and key selections, to grant access as described in Section 2.8 (Gaining access).
The functions of each pane:

ACCESS With a valid password, this pane is the gateway to the functions-sets below that are needed to
do the job.
SYSTEM is the gateway to the system functions of the instrument (that is, the instrument-specific and
application-specific functions, as opposed to the program-specific functions).
ALARMS is the gateway to the alarm functions.
PROGRAMMER If configured, this is the gateway to the programming (Engineer) functions of editing setpoint
programs. This key is also the gateway to the operational (Operator) functions of loading,
running, pausing and aborting setpoint programs.
RECIPE If configured, this allows access to the recipe monitoring and editing functions.
BATCH If configured, this provides a means by which batches can be loaded, started and monitored.
LOGGING If configured, this is the gateway to the data logging functions
OVERVIEW If configured, this provides an overview of the function blocks in the database, with informa-
tion about each.
HOME/USER SCREENS If configured, this returns you to the Home page. The Home page may be a single page, or it
may be the root page of a user-written hierarchy of pages. If HOME/USER SCREENS is not
configured, the System Summary page acts as a default Home page, displayed after a timeout.
Of the two or three further levels in the hierarchy, all are available to Engineers, but only some are available to Opera-
tors and Commissioning Engineers. This helps to improve usability, by hiding those facilities which are not currently
required.
Chapter 2 HA029280
2.4 THE PROGRAM PANE

SAMPLE RUNNING SAMPLE
RUNNING 14:18:23 1 14:18:23 Segment 1
Figure 2.4 A typical Program pane displays
Located at the top left of the screen, this area (which varies in appearance according to instrument type, and options
fitted) has two functions:
1 To display data about the status (state) of the program currently running, if any
2 As a touch pad, to call the Programmer menu directly.
2.4.1 Displaying program status
WITH NO PROGRAM LOADED

When there is no program loaded, the Program pane is white, and blank except for the word ‘RESET’.
WITH A PROGRAM LOADED

In the example shown in figure 2.4 the program pane reports the following:
1 that a program called SAMPLE is loaded,
2 that it is Running,
3 that it is expected to complete at 14hr 18mins 23secs
4 that the name of the segment currently running is ‘1’.
Generally, a loaded program can be in one of six states, reported on the Program pane:
Run, Hold, Held Back, Idle, Complete and Error.
Alone among these, Held Back is not under the control of the user. Programs adopt the Held Back state automatically
when a process value (PV) falls too far behind the setpoint (SP) value. What happens is that the program holds the SP
constant (holds it back). A constant SP is called a ‘dwell’.
With the program in Run state, the Program pane is green, and displays the following data:
1 The name of the program;
2 The program status (e.g. Running)
3 The estimated time or date of completion of the program
4 The name of the segment currently running.
The pane is similar with the program in Hold state, except that the Program pane is yellow, and has the word ‘HELD’
instead of ‘RUNNING’.
The program pane for the Held Back state, is similar to the ‘HELD pane except that ‘HELD BACK’ appears instead
of ‘HELD’.
In Idle state, the Program pane is white and displays the word ‘IDLE’ and the time is displayed as ??:??:??. There is
no current segment.
In Complete state, the Program pane is pale blue, with the word ‘COMPLETE’ displayed.
In Error state, the Program pane is red, with the word ‘ERROR’ (for example, provoked by a COMMS breakdown)
displayed.
2.4.2 Programmer menu access

With access granted, the Programmer menu is called either by touching the Program Pane.or by pressing the printed
Menu key below the screen, and then the PROGRAMMER key in the resulting Pop-up menu.
HA029280 Chapter 2
2.5 THE PROGRAMMER MENU
Broadly, the Programmer menu combines the programming functions (for the Engineer) of editing programs, with the
operational functions (for the Operator) of loading, scheduling, running, monitoring, pausing and aborting programs.
With the display locked, or with it unlocked but no program loaded, only PROGRAMS and SCHEDULE appear.
Programmer
MONITOR PROGRAMS SCHEDULE
PREVIEW PRE-PLOT EDIT
RUN HOLD ABORT
RUN FROM SKIP
Figure 2.5a The Programmer menu, display locked
With the display unlocked and a program loaded, the full menu appears:
Programmer
RUN HOLD ABORT
RUN FROM SKIP
Figure 2.5b The Programmer menu, display unlocked
Some of the buttons are greyed out because - taking the example shown above where the program either has yet to be
run or has just been aborted - these keys are not currently required.
MONITOR Displays text details of the program currently loaded.

PROGRAMS Loads a new program from those available in the instrument’s flash memory.
SCHEDULE Runs a program at a future time and date, repeating a specific number of times if necessary.
PREVIEW PREVIEW is a graphical version of EDIT (below). With a program loaded, it displays its
profile, so that Engineers can check it before running it. They can display the target values for
the variables at any point in time, by moving a vertical cursor along a horizontal time-base.
PRE-PLOT PRE-PLOT is a graphical version of MONITOR (above), but extended, showing a plot of both
target and actual variables. A vertical cursor at the centre of the display marks the current time
and the display moves from right to left past it, showing on the left the actual values of the
process variables (PVs), setpoints and digital outputs, and on the right the required (target)
setpoint profile.
EDIT Enables Engineers to edit, and Operators to view, the setpoints of the current program dis-
played in a table.
RUN Runs a program from the start, or re-starts a program after a Hold from the point where it
paused.
HOLD Stops a program running, and holds it paused at that point.
ABORT Switches a program from ‘Hold’ state to ‘Idle’.
RUN FROM Starts or re-starts a process from a specified time-into-program.
SKIP Terminates the current segment and proceeds immeditely to the next segment.
These are the functions most frequently used in normal operation.
Chapter 2 HA029280
2.6 THE ALARM PANE
The Alarm pane appears at the top right-hand corner of the screen and is used to display any alarm signals (triggered
by abnormal conditions detected in the process under control), instrument alarms etc.
2/2
E Y C O N -10 B A D B A T
Figure 2.6 A typical Alarm pane display

(In this particular example, BADBAT means that voltage delivered by the battery has fallen below its operational
threshold).
In general, there are four possible types of alarm annunciation as summarised in table 2.6.1 below. The question mark
symbol on a flashing orange/black background means that there is a new message to be investigated as described in
‘ACTIVE MESSAGE DISPLAY’ below.
Alarms can be set to be latching or non-latching (auto acknowledging). Latching alarms are annunciated until ac-
knowledged; auto-acknowledge alarms are annunciated until the alarm trigger returns to a non-alarm state. Decisions
on which conditions should trigger an Auto-Ack Alarm rather than an Acknowledge Alarm (latching alarm) are made
during configuration.
2.6.1 Alarm state indication
Alarm state is active or inactive, acknowledged or not. An alarm is triggered (becomes active) when the value it is
monitoring moves outside a pre-set value or range of values. It becomes inactive when the signal returns to within the
preset value or range of values. These values are set up during configuration.
Alarm indicators flash until the alarm has been acknowledged, at which time they become illuminated steadily. To
acknowledge an alarm, the alarm pane can be touched, followed by ‘ACK’. (Access permission needs to be set.)
Indication Definition
Flashing One or more active alarms are present, one or more of
Red/Black which have not been acknowledged.
Steady One or more active alarms are present, all of which have
Red been acknowledged.
Flashing One or more unacknowledged alarms were active, but
White black have now returned to their non-active states.
Steady There are no active alarms present and there are no non-
White active, unacknowledged alarms present.
Table 2.6.1 Alarm annunciation summary

In summary:
If the indication is red an active alarm is present and if it is flashing it has not been acknowledged.
In more detail:
Flashing red/black means that there is at least one abnormal condition that requires attention, and at least one active
alarm has not been acknowledged.
Flashing white/black means there has been at least one abnormal condition, which has now returned to normal, with-
out being acknowledged.
Steady red means there is at least one abnormal condition that requires attention, all of which have been acknowl-
edged, either manually or automatically
Steady white means that there are no current active or inactive/unacknowledged alarms.
HA029280 Chapter 2
2.6.1 ALARM STATE INDICATION (Cont.)
The Alarm pane gives a summary of all alarms, not information about a particular alarm. For instance, if the pane is
flashing red, it means that there is at least one current unacknowledged alarm which may or may not be the one dis-
played in the alarm pane.
In order to gain more details, the alarm history display can be referred to (section 2.6.2).
ACTIVE MESSAGE DISPLAY
In addition to the normal alarm displays described above, a further alarm icon, in the form of a question mark on a
orange/black flashing background, may appear at the left side of the alarm pane as shown in figure 2.6, above. If this
indicator appears, there are one or more messages to be acknowledged or reviewed. Further details of these messages
are to be found in section 3.5 of this manual
2.6.2 Responding to alarms
There are four possible responses to an alarm:

1 Do nothing
2 Get more information, by bringing up the Alarm History page, which is a list of past and current alarms and
events
3 Acknowledge the alarm, by bringing up the Alarm window and pressing a pane
4 Report and then remedy the abnormal condition.
DO NOTHING
Doing nothing is acceptable when the light just shows steady white. This indicates that a non-serious abnormal condi-
tion did exist but it has now returned to normal, and that it has been acknowledged.
Doing nothing is also acceptable with a steady red indication that is not the result of its having been manually ac-
knowledged. In this case, the alarm will have been triggered by an Auto-Ack alarm, which does not require active
intervention but will give information about a slightly abnormal condition.
ALARM HISTORY PAGE

Figures 2.6.2a and b show the alarm history page for XGA and 1/4VGA versions of the instrument respectively (not
drawn to the same scale). The major difference is the ‘ACK column which appears only in the XGA version.
07:49:50 Alarm History 03/04/06
TYPE ACTIVE CLEAR ACK
ENGINEER Log On 03/04/06 05:55:03 -------- -------- -------- --------
T2550/7 Comms 03/04/06 05:08:51 -------- -------- -------- --------
Database Started 03/04/06 04:08:51 -------- -------- -------- --------
Eycon-20 BadBat 03/04/06 04:08:51 03/04/06 05:59:26
Database Loaded 03/04/06 05:08:51 -------- -------- -------- --------
Figure 2.6.2a. Alarm History page (XGA)
12:00:59 Alarm History 03/04/06

TYPE ACTIVE CLEAR
ENGINEER Access 03/04 11:46
T2550/7 Comms 03/04 11:45
Database Started 03/04 11:45
Database Loaded 03/04 11:44
Figure 2.6.2b Alarm history page (1/4 VGA)
Chapter 2 HA029280
2.6.2 ALARM HISTORY PAGE (Cont.)
The Alarm History page displays a list of alarm conditions and Events, showing when they occurred, and if appropri-
ate, when they were cleared or acknowledged (large frame (XGA) versions only). Events and other items which are
not clearable or which cannot be acknowledged display -------- -------- in the Clear and ACK columns.
The Alarm History record starts in the first instance from when the instrument is powered up for the first time. There-
after it is preserved through any automatic restarts called hot starts (see section 4.5.2 Setting the Start-up strategy); but
the record is lost and a new one started whenever a new application database is loaded.
The instrument can retain and display a total of 500 alarms or Events. Once these limits are exceeded the oldest item
in each case is deleted when a new addition is made to the list.
TWO LINE DISPLAY

Operation of the down arrow key toggles between single-line and double-line working. Single line working is a de-
scribed above, and as shown in figures 2.6.2a/b. When in two-line working, each alarm has a second line showing
one or two User IDs.
For units without the Auditor option, one ID is displayed (in parenthesis), and this ID is that of the user who was
logged on at Event time (figure 2.6.2c).
12:36:59 Alarm History 04/04/06

TYPE ACTIVE CLEAR
Database Restart 04/04 12:35
(Fred)
Database Resumed 04/04 12:35
(Fred)
Eycon-10 BrownOu 04/04 12:35 04/04 12:35
(Fred)
Database Started 04/04 12:25
(Fred)
(Fred)
Figure 2.6.2c Two-line history display (1/4 VGA screen)
For units with the Auditor option:

a) If the event did not need signing, then one ID is displayed (in parenthesis), and this ID is that of the user who was
logged on at Event time (figure 2.6.2c).
b) If the event was signed, one ID is displayed, and this ID is that of the user who signed for the action.
c) If the event was authorised, two IDs are displayed, the first (left-most) ID is that of the user who signed for the
action, the second is that of the authoriser.
d) If a text reason for the event is given, when signing, then this (max. 16-character) text string also appears, E.G.:

New database Fred ADMIN
ALARM ACKNOWLEDGEMENT
Unacknowledged alarms are made evident by the flashing of the alarm pane, and a flashing background in the alarm
history page.
It is recommended that an alarm is acknowledged before any attempt is made to rectify the cause of the alarm. Alarms
are acknowledged by calling the ‘Alarms’ menu box (either by touching the alarm pane, or by touching the menu key,
then the ‘ALARMS’ key) and operating the ACK key.
HA029280 Chapter 2
2.7 LOGGING PANE
This area is displayed only on XGA versions of the instrument. Touching this area calls the logging menu shown
below. The logging function allows data to be saved to internal archive as described in section 3.4 of this manual.
That section also shows how to access the logging menu from the menu key.
Logging
MONITOR FTP
MANAGE GROUPS
Figure 2.7 Logging menu
2.8 ACCESS PANE
This area is displayed only on XGA versions of the instrument. Touching this area calls the first of the access pages
described in ‘Gaining access’ below. This is an alternative to using the menu key followed by ‘ACCESS’ as described
below.
2.8.1 Gaining access
There are two methods of gaining access to the instrument configuration, the standard system, and the User ID
method . The instrument is supplied with the standard access system in operation, but it can be converted (irrevers-
ibly) to the User ID version as described in section 4.4 of this manual. For units fitted with the ‘Auditor’ option, see
also section 6.
STANDARD ACCESS
For the Visual Supervisor there are nominally three types of users: Operators, Commissioning Engineers, and Engi-
neers.
Each of these three types has what is known as a level of access to the facilities of the instrument, based upon the
needs of the job, and they gain access to that level by typing in a password. The level of access is fixed for each type
of user. That is to say, all Operators share the same password to their level of access; all Commissioning Engineers
share the same password to their level of access; and all Engineers share the same password to their level of access.
The Engineer-level password gives access to every facility in the instrument. Only from Engineer-level can passwords
be changed.
The hierarchy of levels is LOCKED (lowest), OPERATOR (next lowest), COMMISSION (middle), ENGINEER
(highest). You need a password to change up levels, but not to change down. No password is needed for Locked.
What follows are step-by-step instructions on how to navigate the menu system to get access to your level of facili-
ties. The assumption is that you have your password ready. Passwords are set and re-set by the Engineer.
For first-time access, immediately after commissioning, Section 4.4 (Controlling Access) should be referred to.
Chapter 2 HA029280
2.8.1 GAINING ACCESS (Cont.)

Note: This menu is context sensitive.
The actual display may differ from that
STANDARD ACCESS (Cont.) shown here.
1. With the instrument powered up, press the menu key below the screen. 2
In the Main pane the restricted version of the pop-up menu (figure 2.3) Press ACCESS key
appears.
2 Press ACCESS PROGRAMMER LOGGING HOME
1
Press menu key
The Security Access page appears.
2/2
RESET E Y C O N -10 B A D B A T
13:12:30 Security Access 04/04/06
Enter required level and password,
3 Press the field showing LOCKED on yellow, opposite ‘New Level’. then CHANGE
Current Level: LOCKED

New Level: LOCKED
Password: ********
CHANGE
In the left half of the screen a pick-list of the access levels appears: 2/2
LOCKED 13:12:40 Security Access 04/04/06
OPERATOR LOCKED
Enter required lev
level and password,
COMMISSION then CHANGE
LOCKED
ENGINEER. OPERATOR
COMMISSION
ENGINEER
New Level: LOCKED
4 Select a level -Operator for example.
Password: ********
***
CHANGE
The background highlights yellow, confirming the choice:

2/2
OPERATOR
Enter required lev
level and password,
then CHANGE
LOCKED
OPERATOR
COMMISSION
ENGINEER
New Level: LOCKED
5. Press the Return key (the green arrow ) Password: ********
***
CHANGE
HA029280 Chapter 2
STANDARD ACCESS (Cont.) RESET

2/2
E Y C O N -10 B A D B A T
The pick-list disappears, revealing the full Security Access page again,
showing the selected level (OPERATOR, COMMISSION or ENGI- then CHANGE
NEER) in the New Level field, on yellow.
6 Press the Password field (shown as asterisks on pale yellow) New Level: OPERATOR
Password: ********
CHANGE
2/2
A ‘qwerty’ keyboard display appears, with a cursor flashing under 13:13:48 Security Access 040406
the first character-space in the black confirmation bar at top left.

q w e r t y u i o p
7 If the password contains characters not visible on this display,
a s d f g h j k l ;
press the ‘up-arrow’ at bottom left to view others available. A
numeric/symbol keyboard appears. A further operation of the Up z x c v b n m ,
Arrow calls a keyboard of accented lower-case letters. A final
operation returns the original keyboard to the display.
In entering the password as described in step 8 below, the charac-
Caps lock key
ters can be selected from all three keyboards as required
Use up-arrow key to select
alternative keyboards
2/2
8 Enter the first character of the password. It appears in the black RESET E Y C O N -10 B A D B A T
confirmation bar at top left, and the cursor moves under the next password
space. Enter the next character, and so on.
q w e r t y u i o p
Erroneous characters can be deleted by positioning the cursor
under the relevant character and pressing the ‘C’ key. Alterna- a s d f g h j k l ;
tively, to return to the Security Access page, press the ‘red cross’
z x c v b n m ,
key.
9 When the confirmation bar shows the correct password, press the
Return key.
2/2
The Security Access page reappears, unchanged from step 6. Enter required level and password,
then CHANGE

New Level: OPERATOR
Password: ********
CHANGE
10. Press CHANGE
2/2
The display blanks momentarily, and returns showing the selected Enter required level and password,
then CHANGE
level (OPERATOR, ENGINEER or COMMISSION) in the Current
Level field as well as the new level field.
Current Level: OPERATOR
New Level: OPERATOR
If not, an incorrect password must have been entered. Check that the Password: ********
password is correct for the level selected in step 4, and then repeat
CHANGE
from step 3 onward.
Chapter 2 HA029280
USER ID ACCESS METHOD
In order to gain access using this system, a ‘User Identity’ is entered, instead of an access level, before the password is
entered. User ID, access level and password are all entered as described in section 4.4.3.
To access the Security Access page, either touch the logging pane (XGA units only), or touch the menu key then the
ACCESS key as described above.
User ID and password, then LOG ON
Access: LOCKED
Identity:
Password: ********
LOG ON
Figure 2.8.1 Security access page (XGA)
The user identity and password can now be entered by touching each yellow area in turn and using the resulting key-
board to enter the relevant character strings. Once this has been completed, the LOG ON key is operated.
If the instrument fails to respond with the relevant access level, either the Identity or the Password has been incor-
rectly entered.
Note: The character strings are case sensitive e.g. Identity ‘Fred’ is different from identity ‘FRED’.
HA029280 Chapter 2
Chapter 2 HA029280
CHAPTER 3: OPERATION
The tasks in this chapter all require at least the ‘Operator’ level of access to the instrument.
The chapter consists of the following sections:

3.1 Running a program
3.2 Holding and aborting a program
3.3 Monitoring a program
3.4 Logging data
3.5 Responding to alarms
3.6 Area and group displays.
3.7 Downloading recipes
All the descriptions assume that access at Operator level has already been gained as described in Section 2.8 above
If, at any point, the display shows results that differ from those that the instructions tell you to expect, then the Menu
key at the bottom of the screen can be operated to call the Pop-up menu and the beginning of the task or another facil-
ity if required.
3.1 RUNNING A PROGRAM
There are three ways to run a program, depending upon requirements:

1. RUN. Runs the entire program now
2. RUN FROM. Runs the program now, but from a specified point, after its start.
3. SCHEDULE. Runs the entire program at a specified time.
3.1.1 Running a program now

PROGRAMMER LOGGING USER SCREENS

1. In the row of navigation keys at the bottom of the screen, press
the Menu key to call the Pop-up menu.
2
Press
The Program pane displays RESET if there is no program PROGRAMMER key
1
loaded at the moment, or IDLE if a program has already been Press menu key
selected.
Programmer
2. Select PROGRAMMER.
The Programmer window appears, offering two choices: PRO- PREVIEW PRE-PLOT EDIT
GRAMS and SCHEDULE.
RUN HOLD ABORT
RUN FROM SKIP
3. Select PROGRAMS.
HA029280 Chapter 3
3.1.1 RUNNING A PROGRAM NOW (Cont.)
The Load/Save Program page* appears, prompting for a file name. To the
left of the page title is the current time, and to the right is the current date.
* Note: Up to eight setpoint programs can be supported simultaneously.

Where more than one such program is running, the load/save screen
09:12:37 Load/Save program 04/04/06
(shown at the top of this page) has an additional field ‘Id’. This field can
take the value 1 to 8 to identify which programmer is to run this program. File Name: ????????
All display pages refer to the program associated with the currently
selected ‘Id’.
For any particular programmer display page, the identical page for other
valid Ids can be scrolled-through, using the right and left arrow keys. LOAD
4. Press the yellowed field of question marks.
On the left side of the screen a pick-list (vertical menu) appears, showing
the programs that the instrument currently holds. If necessary, the scroll SAMPLE
bar at the bottom of list can be used to reveal more. File Name: ????????
dsample
STMAXALL
5 Press the name of the required program. The background of the selected ENMAXSEG
program’s name changes to yellow. ENMAXSP
SAMPLE
LOAD
6 Press the Return key (the green arrow)
IDLE
The pick-list disappears and the Load/Save Program page now shows 09:15:33 Archive Manage 04/04/06
the name of the selected program on a yellow background.
File Name: SAMPLE
7. Press the LOAD key

LOAD
SAMPLE
IDLE ??:??:?? 1
The full Programmer menu appears. With no program running, HOLD 09:15:57 Sample 04/04/06
and ABORT are greyed out. The Program pane reads IDLE on a white Programmer
background, showing the program is loaded but idling, not running. MONITOR PROGRAMS SCHEDULE
8. Press RUN RUN
RUN FROM SKIP
SAMPLE
RUNNING 13:41:14 4
09:16:13 Sample 04/04/06
The Program pane changes to green, with status RUNNING. The ex- Programmer
pected time of completion and the number of the segment currently MONITOR PROGRAMS SCHEDULE
executing are also displayed.
The program is now running. RUN HOLD ABORT
RUN FROM SKIP
Chapter 3 HA029820
3.1.2 Running from a point SAMPLE

RUNNING 13:41:14 4
09:16:13 Sample 04/04/06
Programmer
Running a program from a point means running a new program from a MONITOR PROGRAMS SCHEDULE
user-specified point after its start point.
The first seven steps are the same as in 3.1.1 Running a program now, RUN HOLD ABORT
above. RUN FROM SKIP
8. Press the RUN FROM key at bottom left.
The ‘Run From’ page appears, headed with the name of the program IDLE
SAMPLE 0/0
08:54:07 Sample 04/04/06

just loaded. Program
Duration: 03:55:00
The ‘Duration’ field shows how long the program will take to com- Run From: 00:00:00
plete. Segment
Name: 1
The ‘Run From’ field is waiting for a time-into-program value to be Duration: 00:05:00
Time Through: 00:00:00
entered, from which the program run is to be started. Initially, the Run
From field is set at the default of 00:00:00 (the start) so, under the RUN
Segment header below it, the segment name is 1, the first.
The ‘Time Through’ field shows at what time through the segment the
program will start.
SAMPLE 0/0
IDLE ??/??/??
9. Press the yellowed ‘Run From’ field. 08:56:03 Sample 04/04/06
0 1:45:00
Program
7
Duration:
8 03:55:00
9
In the left part of the display a numeric keyboard appears. At the top a Run From: 00:00:00
confirmation bar shows the current ‘Run From’ time as 00:00:00 4 5 6
(hh:mm:ss), with a cursor blinking under the first ‘0’. Segment
1 2 Name:
3 1
Duration: 00:05:00
. 0
10 From the keyboard, key in the required ‘Run From’ time (in this exam- Ti Through: 00:00:00
Time
ple 01:45:00. RUN
11 Press the green Return arrow IDLE

SAMPLE
??/??/??
0/0
08:57:30 Sample 04/04/06

Program
Duration: 03:55:00
The keyboard disappears to reveal the full Run From page. If the se- Run From: 01:45:00
lected time starts running the program from beyond the first segment,
Segment
the ‘Name’ and ‘Time Through’ fields will show different values. Name: 4
Duration: 01:50:00
RUN
12 To run the program now, press the RUN key
SAMPLE 0/0
RUNNING 1 3 : 4 1 : 0 4
08:59:43 Sample 04/04/06
The main display reverts to the Programmer menu. Program
Duration:Programmer
03:55:00
The Program pane changes to green, showing RUNNING, the time of Run From: 01:45:00
completion, and the segment number. PREVIEW PRE-PLOT

Segment EDIT
Name: 4
RUN
Duration:HOLD
01:50:00ABORT
The program is now running, from the specified point.
RUN FROM SKIP
RUN
HA029280 Chapter 3
3.1.3 Scheduling a program ACCESS SYSTEM ALARMS
Scheduling a program means setting a time at which it will start to run PROGRAMMER LOGGING USER SCREENS
automatically.
2
If another program is running at the scheduled start time, the scheduled Press
PROGRAMMER key
1
program will be delayed and started later. The late start is recorded in the
Press menu key
Alarm History.
Programmer
1. In the row of navigation keys at the bottom of the screen, press the
Menu key.
2. Select PROGRAMMER from the pop-up menu that appears RUN HOLD ABORT
RUN FROM SKIP

With no program running, the Programmer menu which appears, has
just two options: PROGRAMS and SCHEDULE.
09:12:49 Schedule Program 20/02/00
3 Select SCHEDULE. File Name: ????????`

Start Date: ??/??/??`
The Schedule Program page appears, prompting for information about Start Time: ??:??:??`
Iterations: 1`
the program to be scheduled.
ACCEPT
4 Press the File Name field.
The left side of the screen shows a pick-list of the programs that the in- 09:13:00 Schedule Program 20/02/00
strument holds. ????????

File Name: ????????`
dsample Start Date: ??/??/??`
STMAXALL `
ENMAXSEG Start Time: ??:??:??
`
ENMAXSP Iterations: 1
5. Select the required program. SAMPLE
ACCEPT
ACCE

SAMPLE
File Name: ????????`
The background of the program name changes to yellow. dsample Start Date: ??/??/??`
STMAXALL `
ENMAXSEG Start Time: ??:??:??
ENMAXSP Iterations: 1`
SAMPLE
6. Press the Return key (the green arrow)
ACCEPT
ACCE
The pick-list disappears, and the File Name field shows the name of File Name: SAMPLE `
the selected program. Start Date: ??/??/??`
Start Time: ??:??:??`
The program is now ready for scheduling. Iterations: 1`
Note: If the program is to run immediately after the currently-running ACCEPT

program ends, the Start Date and Start Time can be left undefined, as
shown here.
Chapter 3 HA029820
3.1.3 SCHEDULING A PROGRAM (Cont.) 09:15:03 Schedule Program 04/04/06

??/??/??
File Name: SAMPLE `
3.1.3.1 SPECIFYING THE PROGRAM START DATE 7 8 9
Start Date: ??/??/??`
4 Start
5 Time:6 ??:??:??`
7. Press the Start Date field. 1 Iterations:
2 3 1`
. 0
The left side of the screen shows a numeric keyboard, with a cursor ACCEPT
flashing under the first number-space in the black confirmation bar at

the top.
04/04/06
8. Key in the required date, in the format set for your instrument (ask File Name: SAMPLE `
7 8 9
your Engineer). Start Date: ??/??/??`
4 Start
5 Time:6 ??:??:??`
1 Iterations:
2 3 1`
After the first digit has been keyed-in, the cursor moves under the
space for the next one, and so on. . 0
ACCEPT
The last-entered character can be deleted, by pressing the ‘C’ key. To

abort the whole date-entry process and return to the full Schedule 09:15:13 Schedule Program 04/04/06
Program page, press the red cross key.

File Name: SAMPLE `
Start Date: 04/04/06`
9. When you’ve finished and the confirmation bar shows the date, in the Start Time: ??:??:??`
correct format, press the Return key. Iterations: 1`
The keyboard disappears and the Schedule Program page now shows ACCEPT
the specified date in the Start Date field.

3.1.3.2 SPECIFYING THE PROGRAM START TIME ??:??:??
File Name: SAMPLE `
7 8 9
10 Press the Start Time field. 4 Start
5 Time:6 ??:??:??`
`
1 Iterations:
2 3 1
The numeric keyboard reappears
. 0
ACCEPT
11 Key in the time in the format hh:mm:ss. 09:17:18 Schedule Program 04/04/06
10:30:00
File Name: SAMPLE `
7 8 9
4 Start
5 Time:6 ??:??:??`
`
1 Iterations:
2 3 1
. 0
ACCEPT

12. When time entry is complete and the confirmation bar shows the time
in the correct format, press the Return key. File Name: SAMPLE `
Start Date: 04/04/06
Start Time: 10:30:00`
Iterations: 1`
The keyboard disappears and the Schedule Program page now shows
the specified time in the Start Time field. ACCEPT
HA029280 Chapter 3
3.1.3 SCHEDULING A PROGRAM (Cont.)
3.1.3.3 CHANGING THE NUMBER OF ITERATIONS (RUNS)

1
13 In the Iterations field, press the ‘1’ File Name: SAMPLE `
7 8 9
The numeric keyboard reappears. 4 5 Time:
Start 6 10:30:00`
`
1 Iterations:
2 3 1
. 0
ACCEPT

14 Key in the required number of runs, and press the Return key. 0
File Name: SAMPLE `
7 8 9
To change the entered value, the ‘C’ key and red cross key operate as 4 5 Time:6 10:30:00`
Start
described in step 8. Iterations: `
1 2 3 1
If the program is to repeat continuously until further notice, press ‘0’. . 0

ACCEPT
15. The Schedule Program page displays the specified number of itera- 09:18:58 Schedule Program 04/04/06
tions. File Name: SAMPLE `

Start Time: 10:30:00`
`
Iterations: 0(Continuous)
ACCEPT
The program is now scheduled.
Chapter 3 HA029820
3.1.4 Segment skip
Skipping a program segment causes the program to stop running its current segment and start running the next seg-
ment immediately.
Skip is initiated from the Programmer menu.

Programmer
HOLD ABORT
SKIP
Press
SKIP key
3.1.4.1 SEGMENT TRANSITION CONSEQUENCES
From dwell, set or servo (SP or PV) to any other type

These transitions are ‘safe’ and provide a bumpless transition of SP from one segment to the next. The program fin-
ishes early.
From ramp to set

Not Bumpless. The ramp is terminated early. The resulting bump is larger or smaller than that programmed depend-
ing on the direction of the ramp compared with the SET.
From ramp to dwell

Almost bumpless, with the SP being servoed to the current working SP at time of Skip. Usually results in a slight
bump in the opposite sense to that of the preceding ramp.
From ramp to ramp
1. Same direction; Same Rate
The ramp continues to the new target SP at the same rate. Combined duration is the same as if unskipped.
2. Same direction; Second Rate higher than the first
At Skip, the SP starts ramping at the new rate. Overall duration is less.
3. Same direction; Second Rate lower than the first
At Skip, the SP starts ramping at the new rate. Overall duration might be greater.
4. Opposite directions.
At Skip, the SP immediately changes ramp direction and it is likely that the previously programmed peak or
trough will not be reached. It is also likely that the SP will reach the new target sooner than expected and in such
a case, unless a further Skip is performed, the SP will dwell until the next segment starts.
From ramp to end (Starting values)

Not bumpless. Same effect as if the Program is aborted.
From ramp to complete (infinite dwell)

Not bumpless. Terminates the ramp and steps to the final target setpoint.
To ramp from any other type

1. Ramp-at-rate. Rate is maintained.
2. Time-to-target. Duration is maintained,
HA029280 Chapter 3
3.2 HOLDING AND ABORTING A PROGRAM
The Hold facility has two uses:

1 for Operators to halt a program when a problem arises in the process under control, and to hold the program at
that point while attempts are made to fix the problem
2 for Engineers to make on-line changes to a running program.
This chapter is for Operators, and so the following deals with the first situation.
SAMPLE
RUNNING 13:41:14 4
3.2.1 Holding a program 12:32:09 Sample 04/04/06
Programmer
1. With a program running, and the full Programmer menu displayed (as MONITOR PROGRAMS SCHEDULE
at step 8 in 3.1.1. Running a program), press HOLD. PREVIEW PRE-PLOT EDIT
HOLD ABORT
SKIP
The Program pane changes to yellow and reports HELD.

SAMPLE
HELD 13:41:23 4
The estimated time of completion starts incrementing in seconds. 12:32:09 Sample 04/04/06
Programmer
Left of the page title is the current time. To view the time-into-pro- MONITOR PROGRAMS SCHEDULE
gram you should use the MONITOR facility (section 3.3, below).
HOLD ABORT
SKIP
For most processes there will now be time available for solving the problem, before the pause itself starts causing new
problems. The time available will depend upon the process. If the attempts to fix the problem are successful, the pro-
gram is usually continued from that point using RUN (see section 3.1.1 Running a program now). If the attempts are
unsuccessful, the program is usually aborted, as described in 3.2.2 below.
3.2.2. Aborting a program
Starting from the end of 3.2.1. Holding a program, press ABORT.
The Program pane changes to white and reports IDLE.
The program is now idling, which means that it is still loaded in short-term memory but not being run. At this point
the same program can be run again from the start, or a new program run (see section 3.1.1 Running a program now).
SAMPLE
IDLE ??:??:?? 4
12:34:54 Sample 04/04/06
Programmer
RUN HOLD ABORT
RUN FROM SKIP
Chapter 3 HA029820
3.3 MONITORING A PROGRAM
There are two ways of monitoring a program as it’s running:

1. Viewing a textual/numeric display, generated by the Monitor facility
2. Viewing a graphical display, generated by the Pre-plot facility.
MONITOR displays text and numeric information about the program, as a list.
PREPLOT displays a graphic profile of the target and actual process variables (PVs).
Generally, MONITOR is used when precise values are needed; PREPLOT is used to provide an overview.
3.3.1 The monitor facility
With a program running and the Programmer menu displayed (step 8 in section 3.1.1 Running a program now), press
MONITOR.
The Current Program page appears, displaying the following information about the program as it is running (most of
the fields are self-explanatory):
PROGRAM
Name: Program name
Status: Run, Hold, Held Back, Idle, Error, Complete.
Duration: Running time, start to finish
Completion: Time of completion of current run (assuming no interruptions)
Iteration: Number of current run / number of runs requested.
SEGMENT
Name: Segment name (usually a number)
Time Remaining: Time remaining to completion of the current segment (decrementing second by second).
SAMPLE 0/0
RUNNING 17:06:34 1
13:13:31 Current Program 04/04/06
Program
Name: SAMPLE
Status: RUNNING
Duration: 03:55:00
Completion: 17:06:34 04/04/06
Iteration: 1/1
Segment
Name: 1
Time Remaining: 00:02:43
RUN HOLD ABORT
HA029280 Chapter 3
3.3.2 The preplot facility

spx7m 3/3
RUNNING15:35:01 REF : 1 D25DO4B COMMS
15:30:57 spx7m 04/04/06
STANDARD DISPLAY MODE SP 1
41.9
41.9
SP 2
With the Programmer menu displayed and a program running (see step 8 57.34
57.34
in section 3.1.1. Running a program now), press PREPLOT. DSP 1

NO DATA
DSP 2
OPEN
A display appears, showing a profile of the target and the actual PVs DSP 3
moving slowly (perhaps imperceptibly) from right to left past a vertical NO DATA
DSP 4
cursor at the centre of the screen. 03:56 00:00 03:56
OPEN
Figure 3.3.2a
Note: The trend resolution is such, that short duration events (in
Preplot display - program running.
particular zero duration spikes), will not be visible.
spx7m 3/3
IDLE ??/??/?? D25DO4B COMMS
The cursor marks the current time. 15:35:51 spx7m 04/04/06
SP 1
28.3
28.3
The actual PVs, SPs and digital outputs are to the left of the cursor and SP 2
42.25
42.25
the target SPs are to the right. DSP 1
NO DATA
DSP 2
With the same program loaded but not running (Idle), the display shown OPEN
DSP 3
opposite appears, showing the profiles programmed for the four vari- NO DATA
ables. DSP 4
OPEN
07:56 00:00
Figure 3.3.2b
Preplot display - program idle
REVIEW MODE
Operation of the option key calls the Option bar, which contains two keys - VIEW and LIVE. Operation of the VIEW
key, causes the page to re-draw, with zoom and pan controls as shown in figure 3.3.2c below. This screen contains
only the program traces, not the target profile.
To enter Review Mode, allowing the history of the program to be traced, the pan/zoom controls are adjusted, or the
trace is touched. Once in Review Mode, the traces on the screen are no longer updated. (This is purely a display
function; the program continues to run as normal.)
To leave review mode, and return to the ‘live’ zoom/pan display, the LIVE key beneath the zoom slider, or the LIVE
key in the option bar should be operated.
To return to the normal pre-plot display, the option bar ‘VIEW’ key should be operated.
Moving this (zoom) slider down

(up) increases (decreases) the
amount of time base displayed.
have similar effect but spx7m
13:29:07
Buttons 04/04/06
provide step changes. Zoom SP 1
factor is shown below the display. 28.3
28.3
SP 2
Cursor (initially at 42.25
right edge of screen) 42.25
DSP 1 Faceplate
NO DATA
values are
Use this (pan) slider (or the those at the
arrow keys) to select that part of DSP 2 cursor time
the time base to be viewed. OPEN and date.
(Left moves back in time.)
DSP 3
NO DATA
DSP 4
OPEN
03/04/06 13:31:17 (x2)
Cursor date Cursor time Zoom
factor 'Back Live’ key
Figure 3.3.2c Review mode controls
Chapter 3 HA029820
3.4 LOGGING DATA
This section describes how incoming data can be logged (archived) to an archive device.
3.4.1 Types of files
The selection of file type (ASCII or UHH) is made in the Logging Groups window, described in section 4.2, below.
ASCII
This is a text file that is human-readable, and which can be imported into standard spreadsheets. Files of this type
have ‘.ASC’ extensions.
UHH
This format is a non human-readable file format. UHH files can be interpreted only by Review software. UHH files
have Sequence file names (see below) and the extension .UHH. If ‘Hourly’ or ‘Daily’ is selected, then new UHH
sequence files are created at hour or day boundaries respectively.
3.4.2 Name types
The selection of name type (Text, Hourly, Daily, Sequence) is made in the Logging Groups window, described in sec-
tion 4.2, later in this document.
TEXT
A Text file is a continuous file that starts when logging starts and stops when logging stops. The file must have an 8-
character file name with the usual MS-DOS constraints; the instrument adds the file type suffix .asc or .uhh. If .uhh
files are used and TEXT is selected, the files are treated as SEQUENCE (see below).
HOURLY
Hourly means that the instrument automatically parcels the archive into files of one-hour length. For the sequence of
files that result, the user supplies the first two letters of the file name(s) and the instrument assigns the last six to indi-
cate the time (month hour day) that the recording started for that particular file. For example, were ‘Monday’ to be
typed-in, then a file name for an hourly-type file might be ‘mo010323’, which would mean that archive started at the
beginning of hour 23 of day 3 of month 1.
DAILY
Daily is similar to Hourly. The instrument parcels the recording into files that start at the beginning of each day (mid-
night) and run for 24 hours. The user supplies the first four letters of the file set and the instrument supplies the last
four (month day).
SEQUENCE
With Sequence filenames, only the first two characters are supplied by the user, the remainder of the file name being
automatically appended by the instrument as a six digit number, starting at 000001. This number is incremented each
time a new file of this form is created.
HA029280 Chapter 3
3.4.3 The Manage facility
The MANAGE facility allows the export of files to a removable storage device.
ARCHIVE EXPORT
The ability to export files to a ‘Memory stick’ is provided from the ‘Archive Manage’ page. Exported (copied) files
are not deleted from the internal archive. SAMPLE 0/0
RUNNING 13:09:28 1
11:24:10 Archive Manage 04/04/06
Export This pushbutton causes the currently displayed file to be File Type: UHH
copied to the USB device, as selected. File Name: AA000001.UHH
Export all This pushbutton causes all files in the internal archive to be File Size: 4 kBytes
copied to the USB device. If the device becomes full Media Size: 31206 kBytes
during archive, a message appears asking the user to fit a Free Space: 21744 kBytes
new memory device. Free Time: 368:08:06
EXPORT EXPORT ALL MONITOR

If a file to be exported has the same name as one already on the storage
device, the following occurs:
a. If the file is identical, the file will not be exported, but be marked as ‘skipped’.
b. If the new file is longer than the one on the storage device, but has the same initial data, it will be exported to
replace the existing file.
c. If neither a. nor b. are true, the user is prompted for a decision.
During export, the screen is normally ‘locked’ to the Archive Manage page. Setting ‘Page Locked’ to ‘No’, causes
normal screen navigation to be restored, with the export continuing as a background task. Once export is complete a
message appears to tell the user that the memory device may be removed. Any other export messages also appear at
the user’s current display page.
The user may return to the Archive manage page at any time.
Note: The large frame unit displays an ‘archiving in progress’ icon at the top of the screen. The icon consists
of a disk shape with an inward pointing arrow to the left. The arrow, and the upper central portion of the disk
shape, flash green during export.
3.4.4 Data integrity
Although the Visual Supervisor is designed to maintain logged data in a secure manner in the event of sudden loss of
power, it is not always possible to guarantee that no data will be lost, or that any data record currently being written
will be complete.
Such problems will be minimised if logging is stopped prior to a controlled power down. Logging can be stopped by
turning logging off in LOGGING/MONITOR or by using the STOP button in SYSTEM/APPLN/APP MGR.
Chapter 3 HA029820
3.5 ALARMS / MESSAGE RESPONSE
Section 2.6, above, describes the alarm pane and the way in which it is used by the instrument to annunciate alarm,
event and message occurrence. The sections below describe the alarm history page, and how to acknowledge alarms,
events and messages.
TIME REPRESENTATION
If time synchronisation is configured, then the date and time of a cached block are the date and time of alarm/event
occurrence at the originating block, and are displayed as DD/MM HH:MM. If it is not certain that the original block’s
instrument has its own clock synchronised, then the date and time of detection of the alarm or event will be used, and
these are displayed as DD*MM HH*MM.

3.5.1 Alarm history page
To display the alarm history page, either
1. Press the Menu key below the screen, then press ALARMS in BATCH LOGGING
the pop-up menu , or
2. Press the Alarm pane
Alarms
The Alarms menu appears. The name of the current alarm condition ACK ACK ALL HISTORY
is displayed in the Alarm pane.
SUMMARY LOG NOTE
3. Press HISTORY
ARCHIVE MESSAGES
The Alarm History page, depicted in figure 3.5.1a, below, appears.
TREND Run prog 3/5

LOCKED
Indicates there are RUNNING 05:07:45 2 TREND
Alarm History
further alarm history
pages accessible via TYPE ACTIVE CLEAR ACK
arrow key(s) TREND Abort 04/04/06 12:00:03 -------- -------- -------- --------
Program Aborted 04/04/06 12:00:03
TREND Loaded 04/04/06 11:59:13 -------- -------- -------- --------
Run Prog Download 04/04/06 11:57:12 -------- -------- -------- --------
PRINTER Config 04/04/06 11:57:12 04/04/06 12:09:33
Amarillo Download 04/04/06 11:57:12 -------- -------- -------- --------
T2550/7 Comms 04/04/06 11:44:51 04/04/06 12:09:33
GASCONIC Load 04/04/06 11:44:50 -------- -------- -------- --------
SFC_CON2 Clear 04/04/06 11:44:50 04/04/06 11:43:07 04/04/06 12:09:33
SFC_CON1 Clear 04/04/06 11:44:50 04/04/06 11:43:07 04/04/06 12:09:33
TREND Load 04/04/06 11:40:02 -------- -------- -------- --------
Eycon-20 BadBat 04/04/06 11:40:02 04/04/06 12:09:33
Database Loaded 04/04/06 11:40:02 -------- -------- -------- --------
Alarm / event / message Date/Time of Date/Time of Date/Time of

as configured in Lin Blocks occurrence alarm or alarm or message
(highlighted message acknowledgement
red if active) being cleared
Displays younger
history, if any F1 F2 F3 F4 F5 F6 F7 F8 F9
Displays older
F10 history,
F11 if F12
any F13 F14 F15 F16 F17 F18
Calls filter,
acknowledge and F19 F20 F21 F22 F23 F24 F25 F26 F27
archive keys
Figure 3.5.1a alarm history display (XGA version) to log (archive)
Information is arranged in a number of columns as shown above. (The figure shows the XGA version; the 1/4VGA
version is similar but does not have the ‘Ack’ column.) The CLEAR and ACK columns contain one of the follow-
ing:
1. Dashed lines (for events - defined as one-off occurrences which, by their nature are not ‘Clearable’).
2. Blank spaces (for alarms or messages that are still active).
3. Time and date (showing when the item ceased to be active or was acknowledged).
HA029280 Chapter 3
3.5.1 ALARM HISTORY DISPLAY (Cont.)
For brevity, ‘Alarms’, ‘Events’ and ‘Messages’ are all referred to as ‘events’ in the following description.
As can be seen from figure 3.5.1 above, the alarm history displays a list of events that have occurred since the data-
base was loaded*, giving the date and time of occurrence, and where appropriate, the time of clearing and (for XGA
units only) time of acknowledgement. Where more ‘events’ have occurred than can be displayed on one page, a ‘page
turn’ symbol appears at the top left of the page. Table 3.5.1, below, shows the various symbols which can appear.
Use right arrow key to view earlier events

Use right arrow key to view earlier events
or left arrow key to view later events
Use left arrow key to view later events
Table 3.5.1 Page turn symbol interpretation
It is possible to limit (filter) the display of ‘events’ in a number of ways, so that only those items of current interest are
included in the list. To achieve this, the ‘Option’ key at the bottom of the display is pressed, to cause the option bar to
be displayed (figure 3.5.1b). This contains not only ‘filter’ keys, but also ARCHIVE and ACK(nowledge) keys.
TREND Run prog 3/5
LOCKED
RUNNING 05:07:45 2 TREND
Alarm History
TYPE ACTIVE CLEAR ACK
TREND Abort 04/04/06 12:00:03 -------- -------- -------- --------
Program Aborted 04/04/06 12:00:03
TREND Loaded 04/04/06 11:59:13 -------- -------- -------- --------
Run Prog Download 04/04/06 11:57:12 -------- -------- -------- --------
PRINTER Config 04/04/06 11:57:12 04/04/06 12:09:33
Amarillo Download 04/04/06 11:57:12 -------- -------- -------- --------
T2550/7 Comms 04/04/06 11:44:51 04/04/06 12:09:33
GASCONIC Load 04/04/06 11:44:50 -------- -------- -------- --------
SFC_CON2 Clear 04/04/06 11:44:50 04/04/06 11:43:07 04/04/06 12:09:33
SFC_CON1 Clear 04/04/06 11:44:50 04/04/06 11:43:07 04/04/06 12:09:33
TREND Load 04/04/06 11:40:02 -------- -------- -------- --------
Eycon-20 BadBat 04/04/06 11:40:02 04/04/06 12:09:33
Database Loaded 04/04/06 11:40:02 -------- -------- -------- --------
ACK = ALL = ALARMS = AREA = GROUP = BLOCK = EVENTS = MSGS ARCHIVE
F1 F2 F3 F4 F5 F6 F7 F8 F9
F10 F11 F12 F13 F14 F15 F16 F17 F18
F19 F20 F21 F22 F23 F24 F25 F26 F27
Figure 3.5.1b Alarm history display with option bar.

TWO LINE DISPLAY
As described in section 2.6.2, above, operating the down arrow key toggles between single line working, (e.g. as
shown in figure 3.5.1, above), and two line working where the second line is used to display the operator ID of the
user who was logged on at the time of the alarm. See figure 2.6.2c for an example.
FILTER KEYS
ALL Displays all Alarms and Events.
= ALARMS Displays only Alarms.
= EVENTS Displays only Events.
= AREA If an Alarm name is touched (highlights yellow), then pressing =AREA causes only those alarms
configured to be in the same ‘Area’ as the highlighted alarm to be displayed.
= GROUP As for =AREA, but for Group.
= BLOCK As for =AREA, but for function block.
= MSGS Displays only messages
Chapter 3 HA029820
3.5.1 ALARM HISTORY DISPLAY (Cont.)
ACK KEY
Pressing this key acknowledges (after confirmation) all current, unacknowledged (i.e. flashing) alarms. Touching an
alarm name (highlights yellow) before pressing ACK, causes just that alarm to be acknowledged.
ARCHIVE
Allows the alarm history to be archived as described in section 3.5.4 below.
3.5.2 Alarm/Message Acknowledgement
ALARMS
Alarms can be acknowledged the following ways:

1. Press the Menu key below the screen. In the pop-up menu which appears, press ‘ALARMS’, then press ACK to
acknowledge the displayed alarm, or ‘ACK ALL’ to acknowledge all current unacknowledged alarms.
2. Press the Alarm Pane. In the pop-up menu which appears press ACK to acknowledge the displayed alarm, or
‘ACK ALL’ to acknowledge all current unacknowledged alarms.
3. From the option bar in the Alarm History page (Section 3.5.1) or the Alarm summary page (section 3.5.5), press
the ACK key.
MESSAGES
Some messages are cleared by the system itself without operator intervention. In such cases, entries appear in the
Alarm history page CLEAR column, but not in the acknowledge column (large frame units only). All message indica-
tion stops.
For other messages, touching the alarm pane, or operating the Menu/Alarms/Messages key displays the latest message
in a pop-up window. Subsequent operation of the OK button for this window, both clears and acknowledges the mes-
sage.
Batch Message
The batch has now started
OK
3.5.3. Adding notes to alarm history
The NOTE facility allows an operator-defined text message to be added to Alarms

the alarm history as follows:. ACK ACK ALL HISTORY
In the Alarms menu press NOTE SUMMARY LOG NOTE
The Add Note window appears. ARCHIVE MESSAGES
To enter the note, press the yellowed field, then key in a string of (max.) 16
characters at the pop-up keyboard, followed by ‘Enter’. Add Note
This will add a note to the Alarm
To abandon the note before completion, press CANCEL. History List
Your note:
When the message is compete, press OK. The note is added to the alarm
history, where it is displayed along with its time of entry. OK CANCEL
HA029280 Chapter 3
3.5.4 Alarm history archive
The ARCHIVE facility permits the current alarm history to be saved in ASCII format to the USB memory stick.
Note: In order to avoid the possibility of loss of logging data it is strongly recommended that archiving is performed
with normal logging turned off.
Alarms
1. In the Alarms menu, press ARCHIVE ACK ACK ALL HISTORY
SUMMARY LOG NOTE

The Alarm Archive window appears.
ARCHIVE MESSAGES
The File Name field shows the default of YYMMDDHH. ALH,
which the instrument supplies automatically. To change this name,
Alarm Archive
press the field to get the keyboard display, and enter a new name. Archive to disk the alarm history
The file extension is always .ALH, (not editable). File Name: 99072009.ALH
Date Format: Date Time
2. To abandon the name before completion, press CANCEL.
3. When the correct name has been entered, press OK. OK CANCEL
If required the ‘Date Format’ field can be edited in a similar fashion.

The format options (Date Time, Spreadsheet and Integer) are de-
scribed in sections 4.2.1 and 4.5.4.
3.5.5 Alarm summary page
This provides an alternative way of displaying only those alarms which are currently active (acknowledged or not)
and previously active alarms which are now cleared but which have not been acknowledged.
The alarm summary page is displayed by touching the SUMMARY key in the Alarm menu.
Operating the Option key calls an option bar like that described in section 3.5.1 for the alarm history display, except
that it includes only ACK, ALL, AREA, BLOCK and GROUP keys.
13:54:05 Alarm Summary 04/04/06

TYPE ACTIVE CLEAR
Eycon-10 CPFail 04/04 09:10 04/04 09:35
T2550/7 Comms 04/04 08:13
Alarms
ACK ACK ALL HISTORY
SUMMARY LOG NOTE
ARCHIVE MESSAGES
Figure 3.5.5 Alarm summary access
Note: Initially, the display shows only the highest priority alarm in each block. Operation of the down arrow
key below the screen causes the display to change such that it shows all alarms. A further operation of the
keys returns to the single alarm/block display, and so on.
Chapter 3 HA029820
3.5.6 Event Log
The event log page is accessed either a) by operating the ‘Log’ key in the alarm menu, or b) by operating the EVT
LOG key in the root menu (only with no application loaded). The page displays the alarms and events that have been
output to trend displays, printers or log files. This data is lost on power cycling.
SUMMARY ACCESS APP MGR
SET UP MAINT EVT LOG
1 2
Press EVT LOG key
Press menu key
16:!4:23 Event Log 04/04/06
04/04 16:00 ACTIVE Shift DigA15

04/04 14:30 TREND Abort
04/04 14:20 TREND Finish
04/04 14:19 TREND Skip
04/04 14:17 TREND Resume
04/04 14:16 TREND Held
04/04 14:11 TREND Resume
04/04 14:10 TREND Held
Figure 3.5.6 Event log display - single line display mode
TWO LINE DISPLAY

The down arrow key can be used to toggle between single line and two line display. The two line display adds a sec-
ond line to each event, used to display text that would not fit onto the single line display.
HA029280 Chapter 3
3.6 AREA AND GROUP DISPLAYS
3.6.1 Overview
As a part of configuration (Lintools), an 'area' page can be defined which can contain up to sixteen 'groups'. Each
group can contain up to 16 points, where each point represents a function block. The area page contains group
'faceplates' which, when any one is touched displays that group's first six point faceplates. For the 1/4VGA unit, if
there are more than six points in the group, a slider control appears at the right side of the display to allow access to
hidden points. To return to the area display, the up-arrow key is pressed.
If a point faceplate is touched a 'close-up' of the faceplate appears giving further information about the point, the
nature of this extra information depending on the type of faceplate.
To return to the group display, the up arrow key can be used. To return to the area display, the up arrow key can be
used twice, or the menu key can be pressed, followed by 'Overview'.
Note: If only one group is configured, the area page does not appear.
To access the area page, the menu key is pressed, followed by operation of the 'Overview' key as shown in figure
3.6.1a.
2
Press Overview key
OVERVIEW PROGRAMMER LOGGING
1
Press menu key
Figure 3.6.1a Access to 'area' page.
Figure 3.6.1b shows typical area, group and point displays. A selection of typical point displays is given in section
3.6.2 below.
TREND DISPLAYS
Operation of the down arrow key whilst in group display mode, calls one of up to four trend displays - Horizontal,
Vertical, Full width horizontal, Full width vertical. In each case, it is possible to enter review mode, allowing histori-
cal data to be viewed. Section 3.6.3, below gives more details.
ALARM INDICATION
Alarm annunciators take a variety of forms, and cover different groups of points or function blocks, but all operate the
same 'protocol' as follows:
Indicator colour Definition
Unfilled No active alarm.
Black There was an active alarm which returned to its non-active state before it was acknowledged.
Steady red There is an active alarm that has been acknowledged.
Flashing red There is an active alarm that has not been acknowledged.
For more details of alarms including acknowledgement see Section 3.5.
Chapter 3 HA029820
3.6.1 OVERVIEW (Cont.)
Show last faceplates (if any)

Touch a faceplate
to call its group 09:20:09 Area1 04/04/06
display (below) This group That group
Group name Group name
Fill colour
(red, black/white) Slide to show
defines alarm Group name required faceplates
Group name
status for point.
Show next faceplates (if any)
09:21:13 This group 04/04/06

Remote enabled
green = I/O currently Ramp name Ramp name
being ramped
Working setpoint
Ramp hold
Yellow = ramp held
Process value
Ramp name Ramp name
Out-of-range holdback
Yellow = heldback
Ramp name Ramp name
Figure 3.6.1b Typical area and group displays
Note: The vertical sliders/push-buttons appear only for 1/4VGA unit displays
HA029280 Chapter 3
3.6.2 Function block faceplates
The following section shows typical function block faceplates, called to the display by touching the relevant faceplate
in the group display (figure 3.6.1b, above).
RAMP FACEPLATES
09:25:31 Ramp name 04/04/06

NNN/L
Process
value Node/Loop
Working
setpoint
Ramp rate per
Ramp-to value
unit time
RUNNING
Status 12.45@23.45/ Seconds
indicators HELD
HOLD BACK Holdback 1.500 Time units
Holdback value
Figure 3.6.2a Ramp faceplate
Node/Loop Shows the system address (node number) of the I/O unit and the ramp number.
Process value Shows the last known process value associated with the ramp
Working setpoint Shows the last known working setpoint value associated with the ramp.
Status indicators RUNNING Shows that the associated I/O channel is being ramped. Filled green when
active, otherwise unfilled, with no text .
HELD When filled (yellow), this shows that the ramp demand is held to allow the
process to 'catch up'; otherwise unfilled, with no text .
HOLDBACK When filled (yellow), this shows that the holdback value has been exceeded;
otherwise unfilled, with no text .
Ramp-to value Shows the value to which the process variable is to ramp.
Ramp rate per unit time Shows how quickly the ramping is to take place, in the time units defined (seconds in this
case).
Time units Shows the time units set for the ramp rate.
Holdback value The 'safe' band (associated with this ramp), within which the process value may fall, without
triggering a holdback.
Chapter 3 HA029820
3.6.2 FUNCTION BLOCK FACEPLATES (Cont.)
PID FACEPLATES
Displays a process style faceplate for PID, PID_LINK and PID_CONN function blocks.
15:52:47 Loop name 04/04/06
100 Alarms
Mode AUTO
Process value
PV 48.8 Eng
Process value
SL 48.8 Local Setpoint
SP 48.8 Working Setpoint
Working Setpoint OP 48.6 % Output
R A M
Mode select buttons
Figure 3.6.2b PID faceplate
Process value Shows the last known process value associated with the loop
Working setpoint Shows the last known working setpoint value associated with the loop.
Local setpoint Shows the last known value for the local setpoint value associated with the loop.
Output percentage Shows the current percentage (0 to 100%) of full scale of the output.
Mode Shows the current mode (Auto, Manual or Remote).
Alarm The alarm beacon is red if the block is in alarm. The beacon is continuously red if the alarm
has been acknowledged, or flashes if unacknowledged.
Mode select These buttons allow the mode to be selected as ‘R’ (Remote), ‘A’ (Auto) or ‘M’ (Manual).
3.6.3 Display modes
Group data can be displayed in a number of formats, as listed below. When a group is touched, in the area display
(section 3.6.1 above), it will appear in the format last used. Other modes are scrolled-to by means of the down arrow
key. The display modes are described below in the order in which they appear after a power up. This order is:
1. User screen (if one has been set up) (not described here)
2. Faceplate display
3. Numeric
4. Vertical bargraph
5. Horizontal bargraph Down arrow Option key
6. Vertical trend with point faceplates key
7. Vertical trend - full width - without faceplates
8. Horizontal trend with point faceplates
9. Horizontal trend - full width - without faceplates
Each of the above-mentioned displays supplies a real-time display of point data. By using the option key, then
‘VIEW’, trend displays become trace-history displays. In such displays, real-time trending stops (although it is still
held in the database for later display), and using various control sliders, the history of the traces can be displayed at a
selectable magnification.
HA029280 Chapter 3
3.6.3 DISPLAY MODES (Cont.)
FACEPLATE DISPLAY
This display shows the contents of the group as what are called ‘faceplates’. This particular display is fully described
in the Overview (section 3.6.1 above). To scroll to the next display mode, touch the down arrow key.
09:21:13 This group 04/04/06

Ramp name Ramp name
Ramp name Ramp name
Ramp name Ramp name
Figure 3.6.3a Faceplate display mode
NUMERIC DISPLAY
This shows point values as seven segment displays, with faceplates.
09:54:17 Name 04/04/06
PV1/1
101
PV1/2
680
PV2/1
491
PV2/2
671
PV3/1
143
PV3/2
193
Figure 3.6.3b Numeric display mode
VERTICAL BARGRAPH
This mode shows the current point values as vertical bars with faceplates. The height of each bar is proportional to the
current value of its associated point. Zero and full scale values appear to the left of the bars.
10:03:34 Name 04/04/06
400
800
800
800
400
400
PV1/1
101
PV1/2
680
PV2/1
491
PV2/2
671
PV3/1
143
PV3/2
193
0
Figure 3.6.3c Vertical bargraph display mode
Chapter 3 HA029820
HORIZONTAL BARGRAPH
This mode shows the current point values as horizontal bars with faceplates. The length of each bar is proportional to
the current value of its associated point Zero and full scale values appear below the bars.
10:03:34 Name 04/04/06

PV1/1
101
0 400
PV1/2
680
0 800
PV2/1
491
0 800
PV2/2
671
0 800
PV3/1
143
0 400
PV3/2
193
0 800
Figure 3.6.3d Horizontal bargraph display mode
VERTICAL TREND WITH FACEPLATE
Standard display
This view displays points as though they are being traced on a chart which is rolling downwards. The latest data is at
the top of the display, and the extent of the data shown on the screen is displayed, at the bottom left of the screen, in
hours and minutes.
For 1/4 VGA (XGA) displays Only the faceplates associated with the first six (16) group items can be displayed.
Where there are more than six (16) trends, these are plotted without faceplate. As a part of the group’s configuration,
it is possible to re-order the group contents to define which faceplates are displayed.
The colour bar at the top of each faceplate is that of its associated trend.
Scroll bar display

An alternative view can be obtained by pressing the option key to display the options bar, then pressing ‘VIEW’. This
calls the scroll bar display shown in figure 3.6.3f below. If no further action is taken, trend data will continue to up-
date normally.
15:39:00 spx7m 04/04/06 15:41:17 spx7m 04/04/06

SP 1 SP 1
28.3 28.3
28.3 28.3
SP 2 SP 2
42.25 42.25
42.25 42.25
DSP 1 DSP 1
NO DATA NO DATA
DSP 2 DSP 2
OPEN OPEN
DSP 3 DSP 3
NO DATA NO DATA
DSP 4 DSP 4
OPEN OPEN
07:56 00:00 07:56 00:00
Figure 3.6.3e Vertical trend with faceplates Figure 3.6.3f Vertical trend with scroll bars
HA029280 Chapter 3
VERTICAL TREND WITH FACEPLATE (Cont.)
Review mode
It is possible to enter review (trace history) mode by
a. Touching the screen in either the Standard or the scroll bar displays described above or the full-width display
described below.
b. Using the slider or push-button controls in the scroll bar display
c. Touching the slide area between the slider and a push button.
Although data is still read and stored in ‘trace history’ by the instrument, the traces remain static on the screen (unless
the ‘zoom’ or ‘pan’ controls are used).
The Option/Live keys or the ‘Back Live’ key are used to return to the standard/scroll bar display
CURSOR On entry to review mode a cursor is located at the top of the screen. The cursor is repositioned either by
touching it and dragging it to the position required, or by touching the screen at the desired point (or a
combination of both), The exact temporal position of the cursor is shown at the bottom of the screen, and
the values shown in the faceplates are those at the cursor time and date.
ZOOM These controls allow the amount of data displayed on the screen to be varied, either continuously, using the
slider, or in steps (using the keys). The expansion/contraction of the trends is centred on the cursor position.
PAN These controls allow a particular section of the trend history to be selected for display. The length of this
displayed section is determined by the zoom setting.
Use this (PAN) slider (or the

arrow keys) to select that part of
the 15:41:17
time base to be viewed.
(Down moves back in time.)
spx7m 04/04/06
SP 1
28.3
top edge of screen) SP 2
42.25
42.25
Moving this (ZOOM) slider right DSP 1 Faceplate
(left) increases (decreases) the 27.35 values are
28.05
amount of time base displayed. those at the
Buttons have similar effect but DSP 2 cursor time
provide step changes. Zoom OPEN and date.
factor is shown below the display. DSP 3
48.75
48.55
DSP 4
OPEN
17/02/02 13:31:17 (x2)
factor ‘Back Live’ key
Figure 3.6.3g Trend review controls
Chapter 3 HA029820
VERTICAL TREND - FULL WIDTH

This view fills the width of the screen, with no faceplates displayed. Review mode is as described above.
13:55:19 spx7m 04/04/06
03:85 00:00
Figure 3.6.3h Vertical full width display mode
HORIZONTAL TREND WITH FACEPLATE

The horizontal trend displays are similar to the vertical trend displays. The main difference (apart from the length of
data displayed and that the traces move from right to left) is the swapping of the Pan and Zoom control locations in
Trend review mode.
Latest data is the right hand edge of the screen
15:35:51 spx7m 04/04/06

SP 1
28.3
28.3
SP 2
42.25
42.25
DSP 1
27.35
28.05
DSP 2
OPEN
DSP 3
48.75
48.55
DSP 4
07:56 00:00 CLOSED
Figure 3.6.3i Horizontal trend with faceplates
HA029280 Chapter 3
HORIZONTAL TREND WITH FACEPLATE (Cont.)
Review mode
The section describing ‘Vertical trend with faceplate’, above, gives full details of review mode.
The Cursor appears at the right hand edge of the screen for horizontal traces.
Moving this (zoom) slider down

(up) increases (decreases) the
amount of time base displayed.
have similar effect but spx7m
13:29:07
Buttons 04/04/06
provide step changes. Zoom SP 1
factor is shown below the display. 28.3
28.3
SP 2
right edge of screen) 42.25
Faceplate
DSP 1 values are
27.35
Use this (pan) slider (or the 28.05 those at the
arrow keys) to select that part of DSP 2 cursor time
the time base to be viewed. OPEN
and date.
(Left moves back in time.)
DSP 3
48.75
48.55
DSP 4
(x2) OPEN
17/02/02 13:31:17
factor 'Back Live’ key
Figure 3.6.3j Trend review controls
HORIZONTAL TREND - FULL WIDTH
13:50:43 spx7m 04/04/06
05:14 00:00
Figure 3.6.3k Horizontal full width
Chapter 3 HA029820
3.7 DOWNLOADING RECIPES
A recipe set consists of sets of instructions (recipes) for controlling between one and eight identical production facili-
ties. The examples below use paint mixers as an illustration of the four types of recipe available.
1. The simple recipe. This file contains references to a single set of equipment and a single set of values to be ap-
plied to the equipment (e.g. orange paint)
2. The multi-recipe. This file contains references to a single set of equipment and multiple sets of values to be ap-
plied to that equipment (e.g. orange, purple and brown paint.)
3. A multi-line recipe. This file contains a single set of values that may be applied, simultaneously, to up to four
sets of equipment (e.g. orange paint to line 1, orange paint to line 2, orange paint to line 3.)
4. A multi-line, multi-recipe. This file contains multiple values that may be applied, simultaneously, to up to four
sets of equipment. (e.g. orange paint to line 1, purple paint to line 2, brown paint to line 3, green paint to line 4.)
Figure 3.7a shows a simplistic view of example 4, and figure 3.7b, a sample recipe page.
Notes:
1 In cases 1 and 2 above, there is only a single line, so references to ‘lines’ do not appear in the user
interface.
2 The number of recipe files that can be loaded simultaneously depends on the application. The number of
files that can be loaded is defined by the number of sets (each with a separate ID). If only one set or ID is
configured, then references to set IDs do not appear at the user interface.
Paint maker recipe set (any line can make any colour)
Line 1 Line 2 Line 3 Line 4

Green Green Green Green
Recipe Recipe Recipe Recipe
Brown Brown Brown Brown

Purple Purple Purple Purple

Orange Orange Orange Orange

Signals
Signals
Signals
Signals
Control
Control
Control
Control
Red Pigment
Yellow Pigment
Blue Pigment
Mixer 1 Mixer 2 Mixer 3 Mixer 4
Orange Purple Brown Green

paint paint paint paint
Figure 3.7a Four paint-mixer set
Recipe set file name Recipe names
09:12:21 PAINT 04/04/06

RCP Orange Purple Brown
red pigment 50.0 50.0 35.0
blue pigment 0.0 50.0 35.0
yellow pigment 50.0 0.0 30.0
Variable Variable
names values
Figure 3.7b Sample recipe edit page
HA029280 Chapter 3
3.7.1 Download procedure
1. Select a recipe set ID (only if multiple recipe sets are supported).

2. Load a recipe file
3. Select a recipe line (only if multiple lines are supported)
4. Select a recipe (only if the file contains multiple recipes)
5. Download the recipe.
RECIPE SET SELECTION ACCESS SYSTEM ALARMS
1 From the main menu, select RECIPE OVERVIEW PROGRAMMER RECIPE
LOGGING HOME
Figure 3.7.1a Main menu

2 From the resulting pop-up menu, select RECIPES
Recipe
RECIPES STATUS MONITOR
EDIT DOWNLOAD ABORT
Figure 3.7.1b Recipe menu
15:18:42 Load/Save Recipe 04/04/06

3. The Recipe Load/Save page appears with the recipe set
ID and name of any currently loaded recipe file, or, if Id: ????????
none, lines of question marks. File name: ????????
To select a new set or recipe file, touch the ID or
Filename area and select the required item from the
picklist which then appears. Alternatively, the various LOAD
available selections can be scrolled through, using the
left/right arrow keys at the bottom of the display.
LOADING THE RECIPE

Once the required file has been selected, operation of the load button will call the recipe menu (figure 3.7.1b). The
recipe can now be loaded by operation of the DOWNLOAD key. If, however, it is necessary to select a particular
recipe line, or if it is necessary to select one recipe from a number in the file, the STATUS button should be operated
to display the Recipe Status page.
Note: The contents of the status page is context dependent, so it is unlikely that it will contain exactly the
same fields as shown in the figures below.
Chapter 3 HA029820
3.7 DOWNLOADING RECIPES (Cont.) 16:16:37 Recipe Status 04/04/06
SELECTING A RECIPE LINE Id: SET 1

If more than one line is present in a recipe set, it is possible
File name: RECIPES
to select which is to be the current line to which the recipe
is to be down loaded. With the Recipe Status page dis-
Line: Line 2 `
played, (figure 3.7.1d), touch the yellowed Line field and Recipe Name: Run Prog
select a new line from the resulting pick list. Alternatively,
the down-arrow key at the bottom of the screen can be
used to scroll through the available items. The file can DOWNLOAD ABORT
now be downloaded by pressing the DOWNLOAD key.
Figure 3.7.1d Status page for multi-line recipes
SELECTING A RECIPE 16:27:56 Recipe Status 04/04/06

If more than one recipe is present in a file, then it is possi-
ble to select which recipe is to be the current one. With the Id: GasMixes
Recipe Status page selected (figure 3.7.1e), a touch on the File name: GASCONC
recipe field will call a pick list from which the required Recipe Name: Amarillo `
item can be selected. The recipe can now be downloaded
using the DOWNLOAD key.
DOWNLOAD ABORT
Figure 3.7.1e Status page for recipe selection
3.7.2 Monitoring the recipe
A recipe can be monitored from the Recipe Status screen, and from the Recipe Monitor screen.
RECIPE STATUS PAGE

The recipe status screen contains the File name and the Recipe name, and any one or more of the following fields:
Set ID
Line
Status (if downloaded)*
Time/date of last download
* Status can be any one of the following:

DOWNLOADING - if a download is in progress
COMPLETE - if the latest download was completed successfully
FAILED - if the previous download was unsuccessful or aborted.
HA029280 Chapter 3
3.7.2 MONITORING THE RECIPE (Cont.)
RECIPE MONITOR PAGE

This page is called from the Recipe menu (figure 3.7.1b) by touching the MONITOR key. The monitor page gives
recipe values in tabular form as shown below.
As can be seen, the following columns are displayed:
RCP The recipe variables

SP The value held in the recipe file for each variable.
SP (Live) The current live database values for each variable. Where the SP and SP(Live) values differ, the value is
highlighted in red, providing a useful diagnostic should a recipe download fail.
PV Optional values monitored in conjunction with the recipe. Might not be present on any recipe file.
Capture Optional values that would be captured if a recipe CAPTURE is performed. Might not be present on any
recipe file.
TREND Run prog 3/5

Fred
Gas Mix
RCP SP SP (Live) PV CAPTURE
Methane 90.6724 90.6724 90.6724 90.6724
Nitrogen 3.1284 3.1284 3.1284 3.1284
Carbon Dioxide 0.4676 0.4676 0.4676 0.4676
Ethane 4.5279 4.5279 4.5279 4.5279
Propane 0.828 0.8280 0.8280 0.8280
Water 0.0 0.0000 0.0000 0.0000
HydrogenSulphide 0.0 0.0000 0.0000 0.0000
Hydrogen 0.0 0.0000 0.0000 0.0000
Carbon Monoxide 0.0 0.0000 0.0000 0.0000
Oxygen 0.0 0.0000 0.0000 0.0000
i Butane 0.1037 0.1037 0.1037 0.1037
n Butane 0.1563 0.1563 0.1563 0.1563
i Pentane 0.0321 0.0321 0.0321 0.0321
n Pentane 0.0443 0.0443 0.0443 0.0443
n Hexane 0.0393 0.0393 0.0393 0.0393
n Heptane 0.0 0.0000 0.0000 0.0000
n Octane 0.0 0.0000 0.0000 0.0000
n Nonane 0.0 0.0000 0.0000 0.0000
n Decane 0.0 0.0000 0.0000 0.0000
Helium 0.0 0.0000 0.0000 0.0000
SAVE CAPTURE CAPTURE AS DOWNLOAD ABORT
F1 F2 F3 F4 F5 F6 F7 F8 F9
F10 F11 F12 F13 F14 F15 F16 F17 F18
F19 F20 F21 F22 F23 F24 F25 F26 F27
Figure 3.7.2 Recipe monitor page (XGA version)
Note: For 1/4VGA units, the capture column is initially hidden, the scroll bar below the table allowing it to
be viewed. This scroll bar and the SAVE/CAPTURE keys (shown above) are toggled between by means of
the options key.
Chapter 3 HA029820
3.8 BATCHES
3.8.1 Batch loading

1 From the main menu, select BATCH, then select BATCHES OVERVIEW PROGRAMMER RECIPE
BATCH LOGGING HOME
Batch
BATCHES STATUS
NOTE HOLD RESTART
RESET ABORT
2 Touch the ID or filename area SAMPLE 0/0

RUNNING 13:06:34 1
12:35:33 Load Batch 04/04/06
3 Select the required item from the picklist which appears.
File Name: ????????
4 Operate the LOAD button.
Note: For the ‘Create’ function, see section 3.8.8, below.
LOAD CREATE
SAMPLE 0/0
RUNNING 13:06:34 1
12:35:33 Batch Start 04/04/06
File Name: BATCH

Batch Id: 50462977
Order No: <Order number>
Customer: <Company>
Contact: <Contact name>
SAVE AS START RESET
3.8.2 Recipe selection
If applicable, a specific recipe can be selected for loading, from a pick list which appears if the Recipe field area is
touched.
3.8.3 Batch customising
The Batch ID is initially chosen as unique by the instrument. The name can be edited in the normal way. In addition
to the batch ID there can be up to six custom items (in the example shown there are three, viz: Order No, Customer
and Contact). Again, these items are editable in the normal way. The titles of these custom items (e.g. Order No.) are
set up using the customising techniques described in Chapter 5, below.
HA029280 Chapter 3
3.8.4 Batch initiation Batch Start Confirm

Please confirm starting of batch
Once all the batch data has been entered, operation of the START key causes OK CANCEL
one of the following to occur, depending on the way in which the batch has
been configured:
1 The batch starts immediately Batch Start Confirm
2 A dialogue box appears asking for confirmation of Batch Start. Opera- Please confirm your password to
tion of the OK button starts the batch. start batch.
3 A dialogue box appears asking for the current user’s password. Entry of Password: ********
the password followed by operation of the OK button starts the batch.
OK CANCEL
3.8.5 Batch monitoring
The batch may be monitored from the Batch Status screen which is accessed from the main menu using the BATCH
key, then the STATUS key.
The batch status screen contains all the information present on the Batch Start screen, but also includes the State of
the batch, its ‘Started at’ and (if appropriate) ‘Ended at’ time and date, and phase information. If a batch message is
active, an annunciator bar appears near the top of the page flashing orange/black and a question mark with orange/
black flashing background appears at the left side of the alarm pane. Touching the alarm pane allows review and ac-
knowledgement of the message.
SAMPLE 0/0
RUNNING 13:06:34 1
12:35:19 Batch Status 05/04/06
Batch Message Batch message
annunciator
File Name: BATCH
Recipe Name: 1
Batch Id: 50562985
Order No: 060405
Customer: FishesRus
Contact: C. BASS
State: COMPLETE
Started At: 05/04/06 12:30:46
Ended At: 05/05/06 12:34:43
HOLD RESTART ABORT RESET
Figure 3.8.5 Batch status page
3.8.6 Batch Hold
With a batch running, operating the HOLD key from either the BATCH menu or the Batch Status screen, places the
batch into hold mode. The batch may be restarted as required, by pressing ‘RESTART’.
3.8.7 Batch Abort
With a batch running or held, operating the ABORT key from either the BATCH menu or the Batch Status screen,
immediately terminates the batch.
Chapter 3 HA029820
3.8.8 Batch Create
A new batch can be created by operating the CREATE key from the ‘Load batch’ page described in section 3.8.1,
above.
Operation of the CREATE key causes a pick list to appear allowing the user to define batch parameters, as shown in
the figure.
CREATE AS ..
Filename:
Recipe Line: <NONE>
Display Group: <NONE>
Message: <NONE>
Log Group: <NONE>
Log Report: <NONE>
OK CANCEL
Filename* Allows a filename (eight characters max.) to be entered for the Batch file.
Recipe line Allows a recipe line to be chosen for batch action.
Display Group Allows one of the display groups to be selected for batch action - see section 3.6 for further details
Message Allows a message (set up in LIN blocks configuration) to be selected for display as appropriate.
Log Group Allows a log group to be selected for Batch action (section 4.2).
Log Report A logging group may have been configured to have "reports". In such a case, one of the log group’s
report files may be selected to drive batch reports. A batch report is generated for start, stop and
abort. The create facility generates an elementary report file (.UYF) which may be customised by
being exported and edited (see section 5.9.1 for further details of .UYF files).
* Entry of a Filename is mandatory. Other field entries are optional.
HA029280 Chapter 3
Chapter 3 HA029820
CHAPTER 4: MANAGEMENT
This chapter is for those responsible for setting up the instrument, for managing applications, for editing setpoint pro-
grams, and for supervising the day-to-day operation and monitoring of the instrument. ‘Engineer’ level of access to
the instrument is required (see section 2.8.1 - gaining access).
This chapter consists of the following sections:

4.1 Editing a program
4.2 Logging groups of data
4.3 Managing an application
4.4 Controlling access
4.5 Setting up and re-setting the instrument
4.6 Cloning an instrument
4.7 File Manager.
4.8 Recipe management
4.9 OEM features
4.10 Batch Maintenance
If at any point the display differs from what is expected, the Menu key at the bottom of the screen on the right can be
used to return to the Pop-up menu from which the task can be repeated.
4.1. EDITING A PROGRAM
4.1.1 INTRODUCTION
Note: If more than one programmer has been configured then the right (left) arrow keys do not scroll through
the program, but to the next (previous) programmer ID. (section 3.1.1).
CREATING A PROGRAM
The PC based Setpoint program editor (supplied on CD as one of the components of the Eurotherm Project Studio) is
used to create programs. For details, see the Setpoint Program Editor Handbook (part no. HA261134U005).
EDITING A PROGRAM
Notes:
1 Only two tasks (changing setpoint value and changing segment duration) can be performed while a
program is running (but on Hold for the duration of the task). Whilst the current segment is in Hold mode,
its values are displayed in green, instead of blue. It is possible to edit this segment’s duration only to
times longer than the period of time already elapsed in that segment; other parameters can be edited as
normal.
2. The PREVIEW facility on the PROGRAMMER menu displays a profile of the loaded program over its
full duration, and target values can be displayed at any point in time. It is recommended that frequent use
be made of PREVIEW, when editing a program, in order to check that the edits have produced the
intended profile.
3. For systems with the Auditor option fitted, an edited program must be saved before it is run.
HA029280 Chapter 4
EDITING A PROGRAM (Cont.)
Before editing can start, the Program Editor page must be accessed as described in section 4.1.2. Once the editor page
has been accessed, the program can be edited in the following ways:
Changing a setpoint (section 4.1.3)

By changing the type of ramp to it
By changing its value
Changing a segment (section 4.1.4)

By changing its identifier
By changing its duration
Inserting or deleting a segment (section 4.1.5)

Inserting a segment
Deleting a segment
Changing the Hold Back properties for any analogue setpoint (section 4.1.6)
Choosing the setpoint
Changing the Holdback mode
Changing the Holdback value
Changing program properties (section 4.1.7)

Changing the name of a program
Changing the rate units for a program
Choosing an action to be taken at the end of each run
Chapter 4 HA029280
4.1.2 Program Editor Page access

1. Press the Menu key, then PROGRAMMER OVERVIEW PROGRAMMER LOGGING
Programmer
1 2
Press Programmer key
Press menu key
RUN HOLD ABORT
The Programmer menu appears. RUN FROM SKIP

2. Press PROGRAMS
File Name: ????????
The Load/Save Program page appears, prompting you for the name
of a file to Load or Save. (To edit a program, it must first be loaded.)
LOAD SAVE SAVE AS DELETE
3. Press the File Name field (the question marks).
On the left of the screen, a pick-list appears, containing the programs 08:31:49 Load/Save program 05/04/06
????????
held by the instrument. File Name: ????????
dsample
4. Press the name of the program to be edited STMAXALL
ENMAXSEG
ENMAXSP
SAMPLE
5. Press the green Return key
LOAD SAVE AS DELETE
The Load/Save program page displays the name of the selected pro-
gram.
6. Press LOAD. File Name: SAMPLE
If the program has components (parameters) which are not in the LIN
database then an error message will appear and the program will not
LOAD SAVE SAVE AS DELETE
load.
After a successful load, the Programmer menu reappears.

7. Press EDIT Programmer

File Name: SAMPLE
The Program Editor page appears showing the values of the setpoints PREVIEW PRE-PLOT EDIT
in tabular form.
LOAD RUN SAVE HOLD
SAVE AS ABORT
DELETE
Each row represents one setpoint along a horizontal timebase marked RUN FROM SKIP
in segments. Some of the rows are for analog setpoints and some are
for digital ones. 08:31:49 SAMPLE 05/04/06
SP 1 2 3
00:05:00 00:50:00 00:35:00
Each column represents a segment, and each segment is identified by Ana In 1 S
to 50.0
R
to 100.0
R
to 0.0
S R R
a name or number shown at the top of the column. Under the seg- Ana In 2 to 50.0 to 65.0 to 20.0
S R R
ment identifier is the time duration of the segment. Ana In 3 to 50.0 to 99.0 to 97.7
Dig in 1 OPEN CLOSED OPEN
Dig in 2 CLOSED OPEN CLOSED
All the yellowed fields yield further information when pressed. Dig in 3 OPEN CLOSED OPEN
HA029280 Chapter 4
4.1.3 Changing a setpoint
CHANGING RAMP TYPE
Generally there are up to six ways in which you can program the Visual Supervisor to control the value of a setpoint
(some may not be available on your instrument). These methods are called ‘Step’ (sometimes called ‘Set’), ‘Dwell’,
‘Ramp at’. Ramp to’, ‘Servo to setpoint’ and ‘Servo to process variable’.
Step
Value changes instantaneously. Can be used in any segment. Also called ‘Set’.
Dwell
Value remains constant. May be used in all segments except the first.
Ramp at
Value increases at a constant specified rate. May be used in all segments except the first.
Ramp to
Value increases linearly to a specified value
Notes:
1. ‘Ramp at’ and ‘Ramp to’ cannot be mixed within the same segment. If an attempt is made to change one
of the SPs from one type to the other, a message appears warning that all the other similar types in that
segment will be changed to conform.
2. A segment may not ramp at less than 0.001 or greater than 9999.0 whether expressed explicitly in a
‘Ramp At’ command, or implicitly in a ‘Ramp to’ command. Values outside this range cause the segment
to execute a ‘step’ function.
Servo to setpoint (SP)

The unit reads the current setpoint value, and sets the setpoint to that value (that is, it does not change it). Similar to
‘Dwell’ except that the instrument carries out the instruction automatically (without operator intervention). As there is
no change, power output remains constant. May be used only in the first segment.
Servo to process variable (PV)

The instrument reads the current process value and sets the setpoint to that value. Because the current process value
normally differs from the current setpoint value, this option usually results in a change in the power consumption of
the process.
Note: If the first segment is a Servo to PV or SP, the instrument assumes that it starts from an SP of 0.0. This
is unlikely to be the actual SP or PV. Therefore the Preview profile displayed for the first segment will differ
from the actual programmed profile. For the same reason, if the second segment is a ramp-at-rate, the segment
duration in Preview will differ from the actual duration; and if the second segment is ramp-to-target then the
slope in Preview will differ from the actual slope.
TERMINOLOGY
In this document any change in the value of the setpoint is referred to as a ‘ramp’, even when the result of that change
is zero. This means that the six methods of controlling the value of the setpoint, described above, all result in types of
ramp.
Chapter 4 HA029280
4.1.3 CHANGING A SETPOINT (Cont.)
TO CHANGE THE TYPE OF RAMP

08:31:49 SAMPLE 05/04/06
Example for Analog Input 1: The following example describes how to 1 2 3
SP 00:05:00 00:50:00 00:35:00
change the ramp in Segment 2 from a ‘time-to-target’ to a ‘ramp-to-tar- S R R
Ana In 1 to 50.0 to 100.0 to 0.0
get’. Ana In 2 S R R
to 50.0 to 65.0 to 20.0
Ana In 3 S R R
to 50.0 to 99.0 to 97.7
In the Program Editor page, the cell for Analog Input 1, Segment 2 Dig in 1 OPEN CLOSED OPEN
shows R for ‘Ramp’ and ‘to 100.0’ for the value, indicating that it is Dig in 2 CLOSED OPEN CLOSED
currently a ramp to a specified value.
Press the cell.

08:33:15 SAMPLE 05/04/06
A dialogue box appears displaying data about that cell. SP 1 2 3
00:05:00 00:50:00 00:35:00
S
In Segment: R R
Ana 1 to 50.02 to 100.0 to 0.0
Press the yellowed ‘Ramp’ field. Ana
S
InSetpoint:
2 to 50.0AnaRtoIn 65.0
1 R
to 20.0
SType: RampR R
Ana In 3 to 50.0 to 99.0 to 97.7
Dig to: 100.0
in 1 OPEN CLOSED OPEN
DONE
A pick-list of ramp types appears, with ‘Ramp’ highlighted

08:33:49 SAMPLE 05/04/06
Press the required type (in this case, ‘Ramp@’). Ramp SP 1 2 3
00:05:00 0 00:50:00 00:35:00
S R R
Dwell Segment: 2 to 100.0
Ana In 1 to 50.0 to 0.0
S AnaRtoIn 65.0 R
Ana InSetpoint:
Step 2 to 50.0 1 to 20.0
Ramp SType: Ramp R R
Ana In 3 to 50.0 to 99.0 to 97.7
Ramp@ to: 100.0
Dig in 2 CLOSED O
OPEN CLOSED
DONE
DON
Di i 3 OPEN
Dig in C
CLOSED OPEN
08:34:08 SAMPLE 05/04/06

‘Ramp@’ highlights yellow. Ramp@
p SP 1 2 3
00:05:00 000:50:00 00:35:00
S R R
Dwell Segment: 2 to 100.0
Ana In 1 to 50.0 to 0.0
S AnaRtoIn 65.0 R
Ana InSetpoint:
Step 2 to 50.0 1 to 20.0
Ramp SType: RampR R
Ana In 3 to 50.0 to 99.0 to 97.7
Ramp@ to: 100.0
Press the green ‘Return’ key. Dig in 1 OPEN CLOSED OPEN
Dig in 2 CLOSED O
OPEN CLOSED
DONE
DON
Di i 3 OPEN
Dig in C
CLOSED OPEN
08:35:13 SAMPLE 05/04/06

The dialogue box reappears, now showing ‘Ramp@’ in the ‘Type’ field, 1 2 3
SP 00:05:00 00:50:00 00:35:00
followed by an extra field ‘Ramp at’. (This field appears only when Ana Segment:
S 2 R
In 1 to 50.0 to 100.0 R
to 0.0
changing to a ‘Ramp@’). Ana
Setpoint:
S AnaR In 1
In 2 to 50.0 to 65.0
R
to 20.0
SType: Ramp@
R R
Ana In 3 to 50.0 to 99.0 to 97.7
Ramp at: 0.0/m
Press the yellowed ‘Ramp at’ field, currently showing 0.0/m (standing Dig in 1 OPEN CLOSED
to: 100.0 OPEN
for zero units per minute). DONE
HA029280 Chapter 4
4.1.3 CHANGING A SETPOINT (Cont.) 08:35:45 SAMPLE 05/04/06

SP 000:05:00
.01 00 2
00:50:00
3
00:35:00
Segment:
7 In 18 to 50.0
S 2
9 to 100.0
R R
TO CHANGE THE TYPE OF RAMP (Cont.) Ana
Setpoint: AnaR In 1
to 0.0
S R
Ana In 2 to 50.0 to 65.0
4 5 Type:6 Ramp@ to 20.0
S R R
Ana In 3 to 50.0 to 99.0 to 97.7
A numeric keyboard is displayed, showing the current value of the ramp in Ramp at: 0.0/m
1 in 12 OPEN 3
Dig CLOSED OPEN
to: 100.0
a black confirmation bar at the top. Dig in 2 CLOSED OPEN CLOSED
. 0
in 3 OPEN
Dig i
DONE
CLOSED OPEN
Key in the required ramp rate. As soon as the first digit is entered, the rest
of the bar clears.
08:36:23 SAMPLE 05/04/06
SP 1 2 3
00:05:00 00:50:00 00:35:00
When the new entry is complete, press Return. Segment:
S 2 R R
Ana In 1 to 50.0 to 100.0 to 0.0
The dialogue box reappears, displaying the new value for the ramp rate. Ana
Setpoint:
S AnaR In 1
In 2 to 50.0 to 65.0
R
to 20.0
SType: Ramp@
R R
Ana In 3 to 50.0 to 99.0 to 97.7
Ramp at: 1.0/m
Press DONE. Dig in 1 OPEN CLOSED
to: 100.0 OPEN
Dig in 3 OPEN
DONE
CLOSED OPEN
A new ‘Ramp to’ value is shown in the cell. To save the new ramp type,
press the Option key at the bottom of the screen, then press the SAVE but-
ton that appears on a bar at the bottom of the screen.
08:43:34 SAMPLE 05/04/06

SP 1 1a 2
00:05:00 00:00:00 00:50:00
S
In Segment: R R
Ana 1 to 50.0 1 to 100.0 to 00.0
CHANGING SETPOINT VALUE Ana
S
InSetpoint:
2 to 50.0 AnaRtoIn 65.0
1 R
to 65.0
SType: Step R R
Ana In 3 to 50.0 to 99.0 to 99.0
In the Program Editor page, select the analogue cell holding the value to be Dig
to: 50.0CLOSED
in 1 OPEN OPEN
Dig in 2 CLOSED
changed. OPEN
DONE CLOSED
A dialogue box appears, showing:
1 the segment name or number
2 the setpoint name for that row 08:43:48 SAMPLE 05/04/06
3 the setpoint type SP 500:05:00

01. 0 0 1a
00:00:00
2
00:50:00
7
Ana 18 S
In Segment: 9 R
1 to 100.0 R
4 the current target value for the setpoint in that cell. to 50.0
S
to 0.0
Ana
4 InSetpoint:
2 to 50.0
5
AnaR In 1
6 to 65.0
R
to 65.0
SType: StepR R
Ana In 3 to 50.0 to 99.0 to 99.0
To change the target value, touch the value and enter the new value using 1
Dig 2
in 1 OPEN
to:3 50.0
CLOSED OPEN
the keyboard display which appears. Dig in 2 CLOSED
. 0 OPEN
DONE CLOSED
in 3 OPEN
Dig i CLOSED OPEN
Press the Return key

08:43:56 SAMPLE 05/04/06
The dialogue box reappears, this time showing the new value. SP 1 1a
00:05:00 00:00:00
2
00:50:00
Ana 1 S
In Segment: 1 R
to 50.0 to 100.0
R
to 00.0
S AnaRtoIn 65.0 R
Press DONE Ana InSetpoint:
2 to 50.0 1 to 65.0
SType: StepR R
Ana In 3 to 50.0 to 99.0 to 99.0
Dig to: 60.0CLOSED
in 1 OPEN OPEN
The Program Editor page returns, with the new value shown in the selected
cell. DONE
08:44:23 SAMPLE 05/04/06

SP 1 1a 2
00:05:00 00:00:00 00:50:00
S
Ana In 1 to 60.0 D R
to 100.0
To save the setting, press the Option key (below the screen), and then the S
Ana In 2 to 50.0 D
R
to 65.0
SAVE button. S
Ana In 3 to 50.0 D
R
to 99.0
Dig in 1 OPEN OPEN CLOSED
Dig in 2 CLOSED CLOSED OPEN
Option key
Chapter 4 HA029280
4.1.4 Changing a segment

08:46:49 SAMPLE 05/04/06
1 2 3
In the Program Editor page, press the identifier at the top of the column of SP 00:05:00 00:50:00 00:35:00
Ana In 1 S R R
the segment to be modified. For example, segment 1. to 50.0 to 100.0 to
Segment: 1 R
0.0
S R
Ana In 2 to 50.0 to 65.0 to 20.0
Duration:
S 00:05:00
R R
Ana In 3 to 50.0 to 99.0 to 97.7
A dialogue box appears with two fields: Segment and Duration, and three Dig inINS SEG DEL SEG
1 OPEN CLOSEDDONEOPEN
buttons: INS SEG, DEL SEG and DONE. Dig in 2 CLOSED OPEN CLOSED
The following subsections show how to change a segment’s identifier and

duration respectively. Inserting and deleting segments is described in sec-
tion 4.1.5.
Once the segment changes are complete, the SAVE button is used to save
the changes. If necessary, the SAVE button is called to the display by
pressing the ‘option’ key located below the screen.
Option key
CHANGING SEGMENT IDENTIFIER
In the dialogue box, press the Segment field.
A ‘qwerty’ keyboard appears.
A numeric/symbol keyboard can be called by pressing the ‘up arrow’ key 08:44:03 SAMPLE 04/04/06
1
at bottom left. A further operation of the arrow key calls a keyboard of
q w e r t y u i o p
accented lower-case letters. Pressing the up arrow key again re-displays
the original ‘qwerty’ keyboard. a s d f g h j k l ;
The segment identifier can be a name, a number, a character or a digit, but z x c v b n m ,
DOS file name rules apply.
The required segment identifier (for example, ‘a’) is keyed-in using one or
more of these keyboards.
To clear the entry so far (but retaining the keyboard display), press the ‘C’
key.
To cancel the entry and return to the setpoint display, press the red cross 08:44:23 SAMPLE 05/04/06
key. SP
a 2
00:05:00 00:50:00
3
00:35:00
Ana In 1 S R
to 50.0 to 100.0
R
to 0.0
S R R
Once the segment identifier has been keyed in, the Return key is operated Ana In 2 to 50.0 to 65.0 to 20.0
S R R
Ana In 3 to 50.0 to 99.0
to save it. to 97.7
The Program Editor page reappears, showing the new identifier for the Dig in 3 OPEN CLOSED OPEN
segment.
HA029280 Chapter 4
4.1.4 CHANGING A SEGMENT (Cont.)
CHANGING SEGMENT DURATION
Caution:
1. Changing the duration of ‘ramp-at-rate’ segments is not permitted.
2. Changing the duration of ‘ramp-to’ segments changes the rate of ramp. Therefore, before making any
such change, you should consider the possible ef fect of this upon the operation of the process plant.
09:01:37 SAMPLE 05/04/06
In the dialogue box, press the Duration field. 0

SP0 : 000:05:00
5 :1 0 0 2 3
00:50:00 00:35:00
7
Ana In 18 S 9 R
to 50.0 to 100.0 to
R
0.0
Ana
Segment:
S 1 R R
In 2 to 50.0 to 65.0 to 20.0
A numeric keyboard appears, with the current duration displayed at the top 4 5
Duration: 600:05:00
S R R
Ana In 3 to 50.0 to 99.0 to 97.7
in hh:mm:ss format. The format can be changed, as described in section 1
Dig 2
inINS 3
SEG DEL SEG
1 OPEN CLOSEDDONEOPEN
4.5.4 Changing the language and date formats. Dig in 2 CLOSED
. 0 OPEN CLOSED
in 3 OPEN
Dig i CLOSED OPEN
Key-in the required duration.
Once the correct duration is keyed-in, the Return key is used to save it. 09:02:09 SAMPLE 05/04/06
SP 1 2 3
00:06:00 00:50:00 00:35:00
Ana In 1 S R R
The Program Editor page appears, showing the new duration for the seg- to 50.0
S
to 100.0
R
to
R
0.0
Ana In 2 to 50.0 to 65.0 to 20.0
ment. S
Ana In 3 to 50.0
R R
to 99.0 to 97.7
Note: Neither an individual segment duration nor the total program
duration may exceed 49 days. Dig in 3 OPEN CLOSED OPEN
4.1.5 Inserting/deleting segment
INSERTING A NULL SEGMENT
Notes:
1. A ‘null’ segment consists of a dwell of zero duration.
2. Inserting or deleting segments can have a knock-on effect on subsequent ‘ramp-to’ or ‘ramp-at-rate’
segments, because the setpoint value at the point when these segments ‘start’ could change. This could
affect the duration of ‘ramp-at–rate’ segments.
In the segment preceding the new segment’s location, press the segment- 09:01:54 SAMPLE 05/04/06
1 2 3
name cell at the top of the column. SP 00:06:00 00:50:00 00:35:00
Ana In 1 S
to 50.0
R
to 100.0
R
to 0.0
Ana
S
In 2 to 50.0
New Segment
R R
to 65.0 to 20.0
In the dialogue box in section 4.1.4, press the INS SEG key. Segment:
S R R
Ana In 3 to 50.0 to 99.0 to 97.7
Dig OK
in 1 OPEN DONE OPEN
CLOSED
The ‘New Segment’ window appears, requesting an identifier for the new Dig in 2 CLOSED OPEN CLOSED
segment. Dig in 3 OPEN CLOSED OPEN
Press the Segment field (yellowed)

09:02:13 SAMPLE 05/04/06
A ‘qwerty’ keyboard appears. The procedure for entering the identifier for
q w e r t y u i o p
a new segment is the same as that described in section 4.1.4.
a s d f g h j k l ;
When the required segment name (for example, 1a) has been entered, the
z x c v b n m ,
Return key is operated.
Chapter 4 HA029280
4.1.5 INSERTING/DELETING SEGMENTS (Cont.)

09:02:37 SAMPLE 05/04/06
INSERTING A (NULL) SEGMENT (Cont.) SP 1
00:06:00
2
00:50:00
3
00:35:00
Ana In 1 S
to 50.0
R
to 100.0
R
to 0.0
S New Segment
R R
The New Segment window reappears, displaying the name of the new Ana In 2 to 50.0
Segment: 1a to 65.0 to 20.0
S R R
Ana In 3 to 50.0
segment. to 99.0 to 97.7
Dig OK
in 1 OPEN CANCELOPEN
CLOSED
This inserted segment will be a ‘null’ operation, until it has been modified. Dig in 3 OPEN CLOSED OPEN
A null operation consists of a dwell of zero duration.
Press OK. 09:02:59 SAMPLE 05/04/06

SP 1 1a 2
00:06:00 00:00:00 00:50:00
The Program Editor page returns with a new, but empty, segment inserted S
Ana In 1 to 50.0 D
R
to 100.0
S R
after the one which was being modified. Ana In 2 to 50.0 D to 65.0
S D R
Ana In 3 to 50.0 to 99.0
Dig in 2 CLOSED CLOSED OPEN
In order to view the whole setpoint sequence, it might be necessary to Dig in 3 OPEN OPEN CLOSED
scroll right or left using the scroll bar/arrows at the bottom of the display.
The SAVE button is used to save the changes when completed. If neces-
sary, the SAVE button is called to the display by pressing the ‘option’ key
located below the screen.
Option key
DELETING A SEGMENT
The procedure for deleting a segment is the same as that for inserting a segment except that:
1 the DEL SEG key is used
2 the first segment of a program cannot be deleted - the DEL SEG key is greyed out (deactivated).
The setting is saved in the same way.
4.1.6 Changing hold back properties
‘Hold Back’ is a state that is automatically induced when the SP ramp rate is too fast for the process to be able to fol-
low it. When the process has fallen behind the SP by an amount equal to a pre-set ‘holdback value’, then the SP ramp
is stopped (‘held’) until the PV catches up. The Holdback value is set by the Engineer.
For example, if the setpoint is ramping up but the PV has fallen behind and is now falling below the pre-set lower
bound, the program will automatically switch the setpoint profile to a dwell to give the PV a chance to catch up. The
dwell will continue until the PV climbs above the lower bound (whose profile of course could now also be a dwell).
At this point the setpoint profile will switch back to a ‘ramp up’.
The result of this is that the overall process time extends by the length of time during which the PV was ‘out-of-
bounds’, which is the same as the length of the dwell.
The remainder of this section explains which type of limit or limits can be set, and how to set the values.
After setting the new values, they are saved by pressing the option key below the screen. On the Option bar that ap-
pears at the bottom of the screen, press the SAVE button.
Option key
HA029280 Chapter 4
4.1.6 CHANGING HOLDBACK PROPERTIES (Cont.)

09:03:29 SAMPLE 05/04/06
1 2 3
CHOOSING THE SETPOINT SP 00:06:00 00:50:00 00:35:00
S
Ana In 1 to 50.0 R R
to 100.0 to 0.0
S R R
Ana In 2 to 50.0 to 65.0 to 20.0
In the Program Editor, choose the analog input for which the Hold Back S
Ana In 3 to 50.0
R
to 99.0
R
to 97.7
properties are to be edited. Dig in 1 OPEN CLOSED OPEN
The cell highlights, and a dialogue box appears
CHANGING HOLD BACK MODE

09:05:17 SAMPLE 05/04/06
SP 1 2 3
00:06:00 00:50:00 00:35:00
Press the Mode field (yellowed) S
Ana In 1 to 50.0 R
to 100.0
R
to 0.0
S R R
Ana In 2 to 50.0 to 65.0 to 20.0
S R R
A pick-list appears with None, Low, High, High & Low shown as modes. Ana In 3 to 50.0 to 99.0 to 97.7
‘None’ means no limits, which means no Hold Back. DONE
‘Low’ specifies a limit below the current setpoint value. If the PV falls
below this limit, then the program will compensate by holding the setpoint
09:05:34 SAMPLE 05/04/06
steady until the PV has recovered to exceed the limit. NONE SP 1 2 3
00:06:00 0
00:50:00 00:35:00
Ana In 1 S
to 50.0
R
to 100.0
R
to 0.0
‘High’ specifies a limit above the current setpoint value. If the PV exceeds NONE S R R
Ana In 2 to 50.0
LOW to 65.0 to 20.0
S R R
this limit, then the program will compensate by holding the setpoint steady HIGH
Ana In 3 to 50.0 to 99.0 to 97.7
HIGH&LOW
Dig in 1 OPEN
until the PV has fallen below the limit. CLOSED OPEN
Dig in 2 CLOSED O
OPEN CLOSED
DDONE
i i
‘High & Low’ sets both limits.
Choose the required limit (e.g. LOW). 09:05:51 SAMPLE 05/04/06

It highlights. SP 1
00:06:00
2
00:50:00
3
00:35:00
Press the Return key. Ana In 1 S
to 50.0
R
to 100.0
R
to 0.0
S R R
The picklist disappears. Ana In 2 to 50.0 to 65.0 to 20.0
S R R
Ana In 3 to 50.0
Press DONE. to 99.0 to 97.7
The dialogue box disappears. Dig in 2 CLOSED OPEN CLOSED
Dig in 3 OPEN DONE
CLOSED OPEN
CHANGING HOLDBACK VALUES
Press the Value field (yellowed). 09:06:08 SAMPLE 05/04/06

SP 0 .00:06:00
0 01 0 0 2
00:50:00
3
00:35:00
A numeric keyboard appears, showing the current value in a black confir- 7 In 18 S
Ana to 9 R
50.0 to 100.0
R
to 0.0
S R R
mation bar at the top. Ana In 2 to
4 5 6 to
50.0 65.0 to 20.0
S R R
Ana In 3 to 50.0 to 99.0 to 97.7
1 in 12 OPEN
Dig 3 CLOSED OPEN
Key in the required value and press the Return key.
The keyboard disappears. . 0
in 3 OPEN
Dig i DONE
CLOSED OPEN
Press DONE.
The dialogue box disappears.
Chapter 4 HA029280
4.1.7 Changing program properties
In the Program Editor page, press the SP (Setpoint) cell at top left. The Properties window appears, prompting for:
SAMPLE
Name: 09:06:25 05/04/06
SP 1 2 3
Rate Units: 00:06:00 00:50:00 00:35:00
Ana In 1 S Properties
R
to 50.0 to 100.0
R
to 0.0
At End: S Name: SAMPLE
R R
Ana In 2 to 50.0 to 65.0 to 20.0
Iterations: Rate Units:
S Minutes
R R
Ana In 3 to 50.0 to 99.0 to 97.7
From this screen, the possible tasks are: At End: Indefinite Dwell
Iterations: 1
OPEN
DONE
CLOSED OPEN
To change the name of a program Dig in 3
To change the rate units

To choose an action to be taken at the end of each run
To change the default number of iterations
To save any new settings, press the Option key at the bottom of the screen and then the SAVE button.
CHANGING PROGRAM NAMES
Note: A program name should be changed only if ‘non-file name’ characters are to be included. If this is the
case, it should be remembered that the file name of the program takes the name of the program by default. In
other words, the program name overrides the file name. Therefore, if a program is saved to a new file, two
programs of the same name will exist, embedded within different files.
SAMPLE 0/0
IDLE ??/??/??
09:06:42 SAMPLE 05/04/06
SAMPLE
In the Properties window, press the current name displayed in the yellowed q w e r t y u i o p
‘Name’ field.
a s d f g h j k l ;
A ‘qwerty’ keyboard display, with a cursor flashing under the first charac-
z x c v b n m ,
ter of the current name, shown in a black confirmation bar above the key-
board.
SAMPLE 0/0
IDLE ??/??/??
Key in the new name. 09:06:59 SAMPLE 05/04/06
simple_
q w e r t y u i o p
When the confirmation bar shows the correct new name (for example,
a s d f g h j k l ;
‘simple’), Press the Return key
z x c v b n m ,
The keyboard disappears, revealing the Properties window showing the IDLE
SIMPLE
??/??/??
0/0
09:07:16 simple 05/04/06

new name.
SP 1 2 3
00:06:00 00:50:00 00:35:00
S R
Properties
Ana In 1 to 50.0 R
to 100.0 to 0.0
S Name: simple
R R
Ana In 2 to 50.0 to 65.0 to 20.0
Rate Units:
S Minutes
R
Ana In 3 to 50.0 to 99.0
R
to 97.7
At End: Indefinite
Dig in 1 OPEN CLOSED
Dwell
OPEN
Press DONE Dig in 2 CLOSED OPEN

DONE CLOSED
HA029280 Chapter 4
4.1.7 CHANGING PROGRAM PROPERTIES (Cont.) 09:06:33 simple 05/04/06

Seconds
SP 1 2 3
00:06:00 00:50:00 00:35:00
S R
Properties
Proper R
CHANGING RATE UNITS Ana In 1
Seconds StoName:
50.0 to 100.0 to 0.0
Ana In 2 to 50.0 simple
R R
Minutes to 65.0 to 20.0
Hours Rate
Ana In Units:
S
3 to
Minutes
R R
50.0 to 99.0 to 97.7
In the Properties window, press the ‘Rate Units’ field. At End: Indefinite
Dwell
OPEN
Dig in 2 CLOSED OPEN
DONE
DON CLOSED
A pick-list appears with Seconds, Minutes, Hours as selectable options. in 3 OPEN

Dig i
Di CLOSED OPEN
Select, say, Seconds

09:06:50 simple 05/04/06
SP 1 2 3
00:06:00 00:50:00 00:35:00
Press Return S R
Properties
Ana In 1 to 50.0 to 100.0
R
to 0.0
S Name: simple
R R
Ana In 2 to 50.0 to 65.0 to 20.0
Rate
Ana In Units:
S
3 to
Seconds
R R
50.0 to 99.0 to 97.7
At End: Indefinite
Dwell
OPEN
The Properties window reappears, with the ‘Rate Units’ field showing
Dig in 2 CLOSED OPEN
DONE CLOSED
‘Seconds’ Dig in 3 OPEN CLOSED OPEN
09:07:07 simple 05/04/06

Press DONE 1
SP 2 3
00:06:00 00:50:00 00:35:00
S
to 100.0 to 0.0
S R R
Ana In 2 to 50.0 to 65.0 to 20.0
The Program Editor page reappears (rate units are not shown). S
Ana In 3 to 50.0
R
to 99.0
R
to 97.7
CHOOSING END-OF-RUN ACTION
In the Properties window, press the yellowed ‘At End’ field.

A pick-list appears containing ‘Indefinite Dwell’ and ‘Starting Values’.
Indefinite dwell
This leaves all values as they are at the end of the program, until new ac- 09:07:24 simple 05/04/06
Indefinite Dwell
1 2 3
tion is taken to change them. A program with an end condition of ‘Indefi- SP 00:06:00 0
00:50:00 00:35:00
Ana In 1 S R
Properties
Proper R
nite Dwell’ does not terminate but adopts the COMPLETE state until IndefiniteStoName:
50.0
Dwell to 100.0 to 0.0
Ana In 2 to 50.0Simple
R R
ABORTED. Starting Values Seconds
to 65.0 to 20.0
Rate
Ana In
SUnits:
3 to
R R
50.0 to 99.0 to 97.7
At End: Indefinite
Dwell
OPEN
Ending on an indefinite dwell is the only circumstance that puts a program Dig in 2 CLOSED O
OPEN
DONE
DON CLOSED
into the ‘Complete’ state and the status panel will show ‘COMPLETE’. Di in 3 OPEN
Dig i CLOSED OPEN
Starting values
This ends the program by restoring its starting values. In this case, the
program adopts the ‘Idle’ state upon finishing. 09:07:41 simple 05/04/06
Starting
SP g Values
1 2 3
00:06:00 0
00:50:00 00:35:00
Ana In 1 S R
Properties
Proper R
IndefiniteStoName:
50.0
Dwell to 100.0 to 0.0
Ana In 2 to 50.0Simple
R R
Select the required action and press the Return key Starting Values Seconds
to 65.0 to 20.0
Rate
Ana In
SUnits:
3 to
R R
50.0 to 99.0 to 97.7
At End: Indefinite
Dwell
OPEN
The Properties window reappears showing the selected action and, below Dig in 2 CLOSED O
OPEN CLOSED
DONE
DON
that, the message ‘DONE’. i 3 OPEN
Di in
Dig CLOSED OPEN
Press DONE.
The Program Editor page re-appears.
Chapter 4 HA029280
4.1.7 CHANGING PROGRAM PROPERTIES (Cont.) 09:06:25 SAMPLE 05/04/06

SP 1 6 2
00:06:00 00:50:00
3
00:35:00
S Properties
7 In 18 to 50.0
9 to 100.0
R R
CHANGING DEFAULT ITERATIONS Ana to 0.0
S Name: SAMPLE
R R
Ana In 2 to
4 Rate5 SUnits:
6 Minutes
50.0 to 65.0
R
to 20.0
R
Ana In 3 to 50.0 to 99.0 to 97.7
At End:3 Indefinite Dwell
1 in 12 OPEN
Dig CLOSED OPEN
Iterations: 1
. 0 DONE
in 3
Dig i OPEN CLOSED OPEN
In the Properties window, press the current value for iterations displayed in
09:06:25 SAMPLE 05/04/06
the ‘Iterations’ field. A numeric keyboard pop-up menu appears allowing SP 1 2 3
00:06:00 00:50:00 00:35:00
the default number of iterations to be set between 0 and 999, where ‘0’ S Properties
R R
Ana In 1 to 50.0 to 100.0 to 0.0
results in continuous running. SName: SAMPLE
R R
Ana In 2 to 50.0 to 65.0 to 20.0
Rate Units:
S Minutes
R R
Ana In 3 to 50.0 to 99.0 to 97.7
At End: Indefinite Dwell
Dig in 1 OPEN
Iterations: 6 CLOSED OPEN
DONE
4.1.8 Changing setpoint names
Analogue and digital setpoint names can be changed, but not while the
program is running. For analogue setpoints the holdback values can also be IDLE
SIMPLE
??/??/??
0/0
amended (see section 4.1.6, above). 09:07:15 simple 05/04/06

SP 1 2 3
00:06:00 00:50:00 00:35:00
S
With the program stopped, press the setpoint whose name is to be edited - S
to 100.0
R
to
R
0.0
Ana In 2 to 50.0 to 65.0 to 20.0
in this example, ‘Ana In 1’ S
Ana In 3 to 50.0
R R
to 99.0 to 97.7
09:07:32 simple 05/04/06

SP 1 2 3
00:06:00 00:50:00 00:35:00
Ana In 1 S
to 50.0
R
to 100.0
R
to 0.0
Ana In 2 S
to 50.0
R
to 65.0
R
to 20.0
For an analogue setpoint a window is displayed, offering the option to S
Ana In 3 to 50.0
R
to 99.0
R
to 97.7
change Setpoint name and Mode (shown opposite). For a digital setpoint Dig in 1 OPEN CLOSED OPEN
the only editable field is ‘Setpoint name’. Dig in 2 CLOSED OPEN

DONE
CLOSED
Press the yellowed field.
Key in the new name, up to a maximum of 16 characters, FOLLOWED 09:07:49 simple 05/04/06
BY ENTER. SP 1
00:06:00
2
00:50:00
3
00:35:00
S
to 100.0 to 0.0
Ana In 2 S
to 50.0
R
to 65.0
R
to 20.0
S R R
Ana In 3 to 50.0 to 99.0 to 97.7
DONE
Press DONE.
HA029280 Chapter 4
4.1.9 Segment timing display
Normally segment timing is shown and edited in terms of the duration of each segment. It is possible to change this
to show the start time and/or the end time of the segment in addition to the duration, or it can be changed to show start
time only.
If ‘start time only’ is selected, the segment is edited by specifying how far into the program the segment is due to
start, not in terms of the segment duration. In this case, the time displayed for each segment must be greater than the
preceding segment and less than the following segment.
09:08:06 simple 05/04/06

To change these options, press the LAYOUT button at the bottom of the
SP 1 2 3
Program Editor screen. S
00:06:00 00:50:00 00:35:00
Editor RLayout R
Ramp17a toLong SP to
50.0 names:
100.0NOto 0.0
Ana In 2 S
toSegment
Rstart: NOR
50.0 to 65.0 to 20.0
The Editor Layout window appears. Segment
S duration:
R YES
R
Ana In 3 to 50.0 to 99.0 to 97.7
Segment finish: NO
Wide cells: NO
Press any field to alternate between YES and NO. Dig in 2 CLOSED OPEN CLOSED
Dig in 3 OPEN
DONE
CLOSED OPEN
The ‘Long SP Names’ field re-formats the display to permit names up to 16 LOAD SAVE SAVE AS NEW LAYOUT
characters long, but this will reduce the number of cells visible.
The ‘Wide Cells’ field widens each cell (reducing the number of segments on display) to allow eight-character values,
and values in ‘scientific’ notation (configured in the application) to be displayed.
Notes:
1. The settings for segment timing are preserved across power failure.
2. It is possible to switch between settings at any time, as this has no effect on the actual program, merely on
how the data is presented.
Chapter 4 HA029280
4.2 LOGGING GROUPS OF DATA
A ‘group’ is a set of up to 16 data values that are recorded to one file. The data can be drawn from the same source or
from different sources. If from the same source, the data can be recorded at different data rates, with each data rate
assigned to a different group.
It is possible to record just one group, or several groups simultaneously. If several groups are to be recorded simulta-
neously, the groups can be saved to one file or to separate files. Archiving to one or more remote computers using
FTP is described in section 4.2.2, below.
Typically, logging groups of data is used for:

1 General audit records (for subsequent analysis with MS Excel, for instance)
2 Quality control of product and plant
3 Monitoring staff performance.
4.2.1 Log initiation
1. Press the Menu key then LOGGING, then GROUPS ACCESS SYSTEM ALARMS
PROGRAMMER LOGGING HOME

The Logging Groups page appears, showing data for a single group.
2
To scroll between groups, press either the < or > keys can be used. Press LOGGING
1
Press menu key
For any group, the fields are as follows:
Logging
3
MONITOR MANAGE
GROUP NAME This is an identifier given to each group of data. Press GROUPS
To name a file or to change a file name, first turn GROUPS FTP
‘Logging’ to ‘OFF’ (see next paragraph), then re-
enter the name.
09:08:23 Logging Groups 05/04/06
Group Name: lgrp1
LOGGING This shows ‘ON’, ‘OFF’, or ‘TRIGGER’. What is Logging: ON
Configuration
shown depends upon whether logging is currently Archive Int: 00:01:00
on, off, or set to start when an event is triggered. File Type: ASCII
(The event is specified by the customer and is Name Type: Hourly
File Name: AA000017.ASC
configured at the factory or by the OEM.) Column Titles: Present
To change the current setting, press the yellowed Date Format: Date Time
Logging field and select ON, OFF or TRIGGER as SAVE MONITOR LOG NOW
required, then press ENTER. The Logging Groups

page now shows the new setting against ‘Logging’.
HA029280 Chapter 4
4.2.1 LOG INITIATION (Cont.)
LOG CONFIGURATION
The remaining fields concern the configuration of the files to be logged. To change any of these fields, Logging must
be selected OFF as described above.
Archive Int This is the interval at which data is archived during the logging process. The maximum rate is
1 file per sec: for example, 1 file @ 1 sec, 3 files @ 3 secs. If a ‘faster’ rate than this is entered
(for example, 4 files each @ 2 secs) then the specified rate may not be reached, in which case
data samples will be lost.
The default format for this field is hh:mm:ss, but this can be changed (see section 4.5 Setting
up and re-setting the instrument).
Values are entered using the numeric keyboard that appears on the left of the screen when the
field is touched.
File Type ASCII
This human-readable file type is for importing into standard, commercial spreadsheets. Files
of this type have extensions of the following type: .ASC, .AS1 to .AS9 or .A01 to .A99. Any
file name type may be used.
Uhh
UHH files can be interpreted only by Review software. UHH files can have only Sequence
file names. If ‘Hourly’ or ‘Daily’ is selected, then new Uhh sequence files are created at hour
or day boundaries respectively. The file extension is .Uhh.
Name Type Text
This results in a continuous file that starts when logging is initiated and stops when logging is
stopped.
Hourly
Logs data in hourly blocks starting on the hour. Each log is written to a different file name.
Daily
Logs data in 24 hour blocks starting at midnight.
Sequence
Logs data in sequentially-numbered continuous files.
File Name The operator specifies the first two letters and the remaining six are assigned automatically by
the instrument, starting at 000001, and incrementing each time a new file is started.
Column Titles This field appears only if ‘ASCII’ is selected as File Type.
Pressing the currently-displayed option causes a picklist to appear allowing the user to select
‘Present’ (column titles included in log) or ‘Absent’, (column titles are not logged).
Date Format This field appears only if ‘ASCII’ is selected as the file type, and is used to select the format
for the date/time or duration stamp recorded in the file, by means of a picklist containing the
formats described in table 4.2.1.
Compr Ratio Not supported by this release of software.
If ‘Binary’ is selected as File Type, then Compr[ession] Ratio replaces Column Titles and Date
Format. Compression ration can be selected, from a pick list, to be either Normal or High.
Normal provides an exact copy whilst High compresses the data more than ‘Normal’ but with
a slight loss of accuracy.
Chapter 4 HA029280
4.2.1 LOG INITIATION (Cont.)
LOG CONFIGURATION (Cont.)
Once configuration is complete, SAVE should be operated:
SAVE Saves the specifications for future logging.

MONITOR Calls the Logging Monitor page.
LOG NOW For ASCII files only, LOG NOW logs a sample immediately it has been selected. This manual
initiation can be used to take samples as and when required, in addition to samples taken under
timed logging.
FORMAT ABS/REL EXAMPLE DESCRIPTION

Date Time Absolute 25/09/98,10/30/00 Choose this format to set up the program to accept the date and time
as dd/mm/yy,hh:mm:ss. The first example in the previous column
means 25 September 1998 at 10.30 am.
09/25/98,10/30/00 The date format can be set to be mm/dd/yy, as described in section
4.5.4 below. The second example expresses the date and time in the
new format.
Spreadsheet Absolute 36068.51 Choose this format for data to be exported to a spreadsheet. The
format is a single floating point value, the integer part of which is the
number of days since 31 Dec 1899 at 0 hours and the decimal part is
the proportion of the day since midnight. For example, a value of 1.5
would represent 1 Jan 1900 at noon.
The example in the previous column represents 30 September 1998 at
10 mins and 5 secs past midday (that is, 30/09/98 at 12:10:05).
Integer Absolute 980930121005 An integer count of seconds since 31 Dec 1899 at 0 hours.
Duration Relative 00:04:30:00 A text format for expressing the time since start of logging.
The example represents 4hrs 30mins since start of logging.
Days Relative 0.1875 Choose this format for data to be exported to a spreadsheet.
A single floating point value.
DHMS Relative 00032000 Days Hours Minutes Seconds since start of logging.
Table 4.2.1 Date formats for logs
HA029280 Chapter 4
4.2.2 FTP Transfer
The FTP transfer mechanism allows the instrument to act as a FTP client to up to 3 FTP servers for the purpose of
transferring the files on the internal archive to a remote computer. If more than 1 FTP server is configured then the
transfer may be configured to operate in either multiple copy or single copy mode.
MULTIPLE COPY MODE

Every file is transferred to every configured FTP server so that every relevant remote computer receives every file.
SINGLE COPY MODE

In this mode only one copy is made of each file on the internal archive. The instrument attempts to send this file to the
first configured server but if the transfer fails then it will attempt the second and if that fails then the third (if config-
ured).
CONFIGURATION TREND
RUNNING 05:07:45
Run prog
2 TREND
LOCKED
Fred
3/5
Eycon-20 BadBat
Archive FTP Servers

Revision: 18 01/04/06 11:58:44 ADMIN
Single copy: NO
(1/3) Appears only if Auditor

Host: 149.121.128.150 option enabled
Enabled: YES
User Name: FTP
Password: *************************
Directory: FTP_ROOT1
+:
+:
(2/3)
Host: 149.121.128.169
Enabled: YES
User Name: FTP2
Password: *************************
+:
+:
(3/3)
Host: 149.121.128.231
Enabled: YES
User Name: FTP3
Password: *************************
+:
+:
SAVE
F1 F2 F3 F4 F5 F6 F7 F8 F9
F10 F11 F12 F13 F14 F15 F16 F17 F18
F19 F20 F21 F22 F23 F24 F25 F26 F27
Figure 4.2.2 Archive FTP servers configuration page
Revision Information appears only if the Auditor Option is enabled.

Single Copy If TRUE then single copy mode is used, otherwise multiple copy mode is used.
For each remote computer server:

Host Address of the remote computer which is running the FTP server.
Enabled If set FALSE then this server is not in use.
User Name The user name to be used when logging in to the remote computer
Password The password to be used when logging in to the remote computer (this value is not displayed for security
reasons).
Directory: This is the directory (folder) on the remote computer where the files are to be stored. For security reasons
FTP servers normally only permit access to a limited area of their host computer by re-mapping the directo-
ries. It is the re-mapped name that must be entered here.
NOTE: if the name is longer than 40 characters then it must be spread across multiple lines.
The instrument must be power cycled to effect the changes.
Chapter 4 HA029280
4.3 MANAGING AN APPLICATION
This section describes the stopping, saving, starting, unloading, loading, running and deleting of applications, using
the STOP, SAVE, START, UNLOAD, LOAD, LD+RUN and DELETE keys that appear at the foot of the Application
Manager page.
UNLOAD and DELETE: For many processes, the Visual Supervisor will control one application all the time. This
will be loaded and run at commissioning, or soon after, and thereafter will never be unloaded and will never be de-
leted. For many processes, therefore, UNLOAD and DELETE will not be used.
STOP, SAVE and START: All processes will use STOP, SAVE and START because an application has to be stopped
to save application data (to preserve cold-start values if they need changing). This is true even if the process runs only
one application. START simply restarts an application after a SAVE.
LOAD and LD+RUN: All processes require a LOAD or LD+RUN at least once.
These tasks are described under the following headings:
Displaying the Application Summary page (section 4.3.1)

Displaying the Application Manager page (section 4.3.2)
Stopping an application (section 4.3.3)
Saving application data (section 4.3.4)
Unloading an application (section 4.3.5)
Loading an application, or Loading and running (section 4.3.6)
Deleting an application (section 4.3.7)
Function Block Manager (section 4.3.8)
If the very first application is being loaded and run on an instrument, LOAD and then START, or just LD+RUN will
be used. If an application is already running and it is to be replaced by another, the sequence from Displaying the
Application Manager page to Loading an application (or Loading and running) should be referred to.
Application Summary and Function Block Manager provide useful summaries and overviews at any time.
HA029280 Chapter 4
4.3.1 Application summary page 2

Press SYSTEM
This page displays the percentage of the instrument’s various memory ACCESS SYSTEM ALARMS
resources that are currently in use. PROGRAMMER LOGGING HOME
Press the Menu key and select SYSTEM from the pop-up menu.
System
1 SUMMARY APPLN
Select APPLN then APP SUM. Press menu key 3
SETUP CLONING
Press APPLN
Application
APP SUM APP MGR FB MGR

4
Press APP SUM
09:10:00 Appl'n Summary 05/04/06
The Application Summary page appears, showing: Application: ise

1 the name of the loaded application, Machine State: RUNNING
2 its state (RUNNING, IDLE, or STOPPED), Memory Usage
Control DB: 128 kB 76%
3 data about memory usage. 73 kB
SFC DB:
SFC ST: 112 kB 0.4%
Programmer: 92 kB 0.0%
Modbus: 20 kB 0.0%
4.3.2 Application manager page

Note: If the Terminal Configurator is being used, the Application Manager page will not be accessible.
Conversely, if the Application Manager page is being used, the Terminal Configurator will not be usable.
Press the Menu key and select SYSTEM from the pop-up menu.
2
Press SYSTEM
Select APPLN from the SYSTEM window to display the Application PROGRAMMER LOGGING HOME
window.
System
1 SUMMARY APPLN
Press menu key 3
SETUP CLONING
Press APPLN
Select APP MGR.
Application
APP SUM APP MGR FB MGR

4
Press APP MGR
The Appl’n Manager page appears, displaying the name of the cur-
09:10:34 Appl'n Manager 05/04/06
rent application and its state (i.e. RUNNING, IDLE or STOPPED.
File: RISE
State: RUNNING
UNLOAD SAVE SAVE AS STOP
Chapter 4 HA029280
4.3.3 Stopping an application 09:10:51 Appl'n Manager 05/04/06
File: RISE
State: RUNNING
With an application running the Appl’n Manager page appears (except for
the actual file name) as shown in the figure.
09:11:08 Appl'n Manager 05/04/06
File: RISE
State: STOPPED
To stop the application, press STOP
The display confirms that the application has STOPPED,

UNLOAD SAVE SAVE AS START
Note: While an application is STOPPED, the Logging and Programmer

facilities will be suspended. The duration of the current segment will be
extended by the length of time the application stays STOPPED. Stopping
an application during a critical operation is not recommended.
The keys at the bottom of the display offer four options:

UNLOAD the application, without first saving the application data, typically prior to selecting a new application, or
cloning a new one.
SAVE the application data, typically because the Cold Start values have changed (usually from the Terminal
Configurator).
SAVE the data as a different file (SAVE AS).
START the application again.
SAVE, SAVE AS and START are covered in the next section.
Note: Any application data saved will not include the current setpoint program.
HA029280 Chapter 4
4.3.4 Saving application data 09:11:08 Appl'n Manager 05/04/06
File: RISE
The application must be stopped before application data can be saved. State: STOPPED
09:11:25 Appl'n Manager 05/04/06
Select SAVE
File: RISE
STOPPED
State:Saving
Saving starts, confirmed by a ‘Saving’ window. File: RISE.DBF
Please wait...
09:11:42 Appl'n Manager 05/04/06
To save the current application data under a different name, select SAVE
File: RISE
AS.
SAVESTOPPED
State: AS
File: RISE
A ‘SAVE AS’ window appears, with a yellowed field into which another OK CANCEL
file name can be entered if required (not shown).
To re-start the application, select START 09:11:59 Appl'n Manager 05/04/06
File: RISE
State: RUNNING
The Appl’n Manager page reverts to its opening display, reporting the cur-
rent application running.
You can also use START to start another application that you might have UNLOAD SAVE SAVE AS STOP
loaded.
4.3.5 Unloading an application 09:12:16 Appl'n Manager 06/04/06
File: RISE
The application must be stopped before it can be unloaded. State: STOPPED
Select UNLOAD
The screen might go blank for a few seconds while the application unloads.
09:12:33 Appl'n Manager 06/04/06
When the unloading is complete, the Appl’n Manager page should look
like this, with three keys offering LOAD, LD+RUN, and DELETE. This is File: RISE
referred to as the ‘bare’ panel. A new LIN database can be cloned only
when in this state.
At this point the choice must be made to load or load-and-run another ap-
LOAD LD+RUN DELETE
plication, or to delete an application.
Chapter 4 HA029280
4.3.6 Loading or loading and running an application
Before an application can be loaded, any previously-loaded application must have been stopped and unloaded.
APPLICATION SELECTION
09:12:50 Appl'n Manager 06/04/06
Press the File field

File: RISE
Select the required application from the pick list and press the Return key. State: IDLE
The name is displayed in the File field.
APPLICATION LOADING 09:13:07 Appl'n Manager 06/04/06
File: RISE
If you select LOAD, there is a short delay before the page shows the name State: RUNNING
of the application and its state, IDLE.
If LD+RUN is selected, there is a short delay before the page shows the
name of the application and its state, RUNNING. The same state can be
achieved using LOAD, then START.
4.3.7 Deleting an application
The application must be stopped and unloaded before it is deleted.

09:13:24 Appl'n Manager 06/04/06
File: RISE
Press DELETE
LOAD LD+RUN DELETE

The Confirm Delete window appears. 09:13:41 Appl'n Manager 06/04/06
File: RISE
Confirm Delete
File: RISE
OK CANCEL
Press OK LOAD LD+RUN DELETE
HA029280 Chapter 4
4.3.8 Function Block Manager
The function blocks set up in LinTools for this application can be viewed as a group, by touching the FB MGR button
of the Application pop-up. Touching a particular function Block calls its details to the display. Reference to the
LinTools manual will normally have to be made to understand the entries completely.
Highlighted items in the Function Block list can be edited.
Figure 4.3.8a shows how to access the Function Block Manager, and figure 4.3.8b shows the initial Function Block
Manager display pages.
2
Press SYSTEM
System
SUMMARY APPLN
1
3
Press menu key SETUP CLONING Press APPLN
Application
APP SUM APP MGR FB MGR 4

Press FB MGR
Figure 4.3.8a Access to the Function Block Manager
14:20:59 FB manager 06/04/06

Eycon-10 lin_dext 2500/5 mod5/01
ise_diag edb_diag ramp5/1 mod5/02
ddr_diag edbtable ramp5/2 mod5/03
pnl_diag elindiag loop5/1 mod5/04
alh_diag SppCtr1 To display mod5/05
loop5/2 further Function Blocks,
touch and drag slider, or press arrow key
amc_diag SppDig area1 mod5/06
db_diag 2404/4 moduls/5 2500/6
14:23:13 ramp5/1 : SPP_RAMP 06/04/06

ResetSP 15.00 degC
HL_SP 50.00 degC
LL_SP 0.000 degC
Track FALSE If the list is too long
Alarms to fit the page, a
Ramp Dis FALSE
PV 15.23 degC vertical slider and
TgtSP 15.00 degC pair of arrow keys
Rate 0.000 degC
RampUnit SEC appear at the right-
Out 15.00 degC hand edge of the
NewTgtSP 20.00 degC
NewRate 0.000 degC screen
Sync FALSE
Complete FALSE
Active FALSE
NotActiv 00:00:00
Holdback FALSE
Hold FALSE
HB_Mode NONE
Use Up arrow to return to
FB Manager page.
Figure 4.3.8b Function Block Manager Pages
Chapter 4 HA029280
4.3.8 FUNCTION BLOCK MANAGER (Cont.)
With the data base stopped, the options bar at the bottom of the display contains the keys ‘CREATE’, ‘SAVE’ and
‘NETWORK’.
Note: For small frame units, the option key toggles the option bar and the scroll bar at the bottom of the
screen.
14:20:59 FB manager 06/04/06

Eycon-10 lin_dext 2500/5 mod5/01
Option key
alh_diag SppCtr1 loop5/2 mod5/05
CREATE SAVE NETWORK
Block Create Network Set Up

Category: I-O Eycon-10_07 7
Block type: ANIN Eycon-10_08 8
Block name:
Eycon-10_06 6
OK CANCEL Eycon-10_05 5
Figure 4.3.8c Create, Save and Network keys
CREATE This key allows a new block to be created. Once the block category, block type and block
name have been entered, operation of the OK key causes the new block to be created.
Category and Type are selected from pop-up pick lists. The block name must be ‘typed in’.
SAVE Operating this key saves the database in the same way as the SAVE key in the Application
Manager (section 4.3.4).
NETWORK Operation of this key displays a list of all the external databases defined within the application.
HA029280 Chapter 4
ALPHA-NUMERIC BLOCK DISPLAY
Initially, the FB Manager page lists the blocks in ‘database order’. Touching the down arrow key re-orders the list in
alpha-numeric order, with numeric entries first (figure 4.3.8d). Further operations of the key toggle between the two
display orders.
05:34:47 FB manager 06/04/06

Eycon-10 lin_dext T2550/5 mod5/01
alh_diag SppCtr1 loop5/2 mod5/05
Use down arrow key

to re-order display
05:34:54 FB manager 06/04/06

2404/4 edb_diag mod5/01 pnl_diag
alh_diag elindiag mod5/02 ramp5/1
amc_diag Eycon-10 mod5/03 ramp5/2
area1 ise_diag mod5/04 SppCtr1
ddr_diag lin_dext mod5/05 SppDig
db_diag loop5/1 mod5/06 T2550/5
edbtable loop5/2 moduls/5 T2550/6
Figure 4.3.8d Alpha-numeric Function block ordering.
Note: For the sake of simplicity, only those function blocks shown in figure 4.3.8b have been included in the
above figure. In reality, function blocks hidden (off screen) in figure 4.3.8b would replace some of those
shown above.
Chapter 4 HA029280
FUNCTION BLOCK DETAILS 10:28:44 ramp5/1 : SPP_RAMP 06/04/06

ResetSP 15.00 degC
HL_SP 50.00 degC
LL_SP 0.000 degC
Track FALSE
Alarms
Ramp Dis FALSE
PV 15.23 degC
TgtSP 15.00 degC
Rate 0.000 degC
Once a function block has been highlighted, touching the down arrow RampUnit
Out
SEC
15.00 degC
key displays block details - Block name, Block type and update rate NewTgtSP
NewRate
20.00
0.000
degC
degC
Sync FALSE
(figure 4.3.8e). Complete
Active
FALSE
FALSE
NotActiv 00:00:00
Holdback FALSE
Hold FALSE
HB_Mode NONE
10:28:51 ramp5/1 : SPP_RAMP 06/04/06
Block name: ramp5/1

Block type: SPP_RAMP
Update rate: 1000 ms
With the data base stopped, the Delete key allows function blocks to DELETE
Update rate appears only for applicable
Block types. It is shown here only for
example purposes
be deleted from the database.
A further operation of the down arrow or cycle screens key calls the
function block ‘Connections’ page. If the data base is stopped, this
page allows the adding/deleting/modifying of the function block. 10:29:06 ramp5/1 : SPP_RAMP 06/04/06
Options<< (11)
TaskHalt<< (4)
Relays
Relays<< (2)
Wdg<<
In the case of subfields, a number is displayed, which is the number Run<<
of connections when the database is running, or the number of con-

nectable bits when stopped. Touching the field displays the details of
all relevant bits.
Figure 4.3.8e Function block details
4.4 CONTROLLING ACCESS

Note: for instruments fitted with the ‘Auditor’ option, see also chapter 8.
Access control consists of setting up (and changing, if necessary) the passwords for each of the three types of users:
Operators, Commissioning Engineers, and Engineers. Alternatively, a ‘User ID’ access system can be used, as de-
scribed in section 4.4.3, below.
Section 2.8.1, above, contains details of how the passwords/User ID is used to gain access to various parts of the
instrument configuration.
As described in section 4.5.5, it is possible to set a time period (time-out) after which the access level returns to
‘Locked’.
HA029280 Chapter 4
4.4.1 First-time access
LOCKED level: For access to the LOCKED level at first-time or at any other time, no password is required.
OPERATOR and COMMISSION (Commissioning Engineer) levels:
For first-time access, no password is required.
ENGINEER level: For first-time access, immediately after the instrument has been commissioned, the factory-set
default password for Engineer-level access should be entered. This password is:
<spacekey>default
I.E. a space character followed immediately by d e f a u l t (eight characters in all). The space key
on the screen keyboard is the blank key at bottom right, above the ‘C’ key.
2
Press ACCESS
4.4.2 Editing the passwords
To change the passwords, carry out the following procedure: PROGRAMMER LOGGING HOME
1 Press the Menu key.

The Pop-up menu appears.
1
Press menu key
0/0
RESET
2 Press ACCESS. Enter required level and password,

then CHANGE
The Security Access page appears, displaying the current access level
(ENGINEER) and two keys: CHANGE and PASSWDS.
Current Level: ENGINEER
New Level: ENGINEER
3 Press PASSWDS Password: ********
CHANGE PASSWDS
The Passwords page appears. RESET

0/0
09:15:40 Passwords 06/04/06
4 Press the password field you want to change - e.g. Operator OPERATOR: ********
COMMISSION: ********
ENGINEER: ********
OK USER CANCEL
A ‘qwerty’ keyboard display appears. RESET

0/0
09:15:06 Passwords 06/04/06
q w e r t y u i o p
(Continued)
a s d f g h j k l ;
z x c v b n m ,
Chapter 4 HA029280
4.4.2 EDITING PASSWORDS (Cont.) RESET

0/0
09:15:23 Passwords 06/04/06
operator
5 Key in the new password.
q w e r t y u i o p
a s d f g h j k l ;
6 Press the Return key
z x c v b n m ,
The Security Access page reappears

0/0
RESET
then CHANGE
Current Level: ENGINEER

New Level: ENGINEER
7 Press OK Password: ********
CHANGE PASSWDS
For Commissioning Engineer and Operator passwords, the Security Access page reappears with either COMMIS-
SION or OPERATOR displayed against both Current Level and New Level (depending upon the access level for
which you were setting the password).
For Engineer-level passwords only, a Confirm Password window appears, prompting a repeat of the password-
entry procedure, as follows in steps 8, 9 and 10.
8 Press the password field (still asterisked).
9 Key in the new password again, and press the Return key. The Confirm Password window pops up again.
10 Press OK. After a short delay, the Security Access page appears with ENGINEER displayed at both Current Level
and New Level.
HA029280 Chapter 4
4.4.3 User ID system
The standard system of access described in section 4.4.2 above, can be replaced by a system in which each individual
user has a password and ident to allow access to the instrument configuration. The access levels Engineer, Commis-
sion and Operator are retained, but with an additional level: Admin.
CHANGING TO THE USER ID SYSTEM
Note: Changing from the standard access-level system to the user id system is not a reversible process i.e. it
is not possible to return to the access-level system from the user id system.
0/0
1 Press the Menu key and select ACCESS from the pop-up menu. If RESET
09:14:49 Passwords 06/04/06
necessary, change the access level to Engineer
2 Press PASSWDS, then USERS. OPERATOR: ********
3 Confirm (twice) that the change is to be made. COMMISSION: ********
ENGINEER: ********
4 Login at Admin level, by
a) touching the Identity field and entering ADMIN (must be in capi-
tals) followed by Return, then, OK CANCEL USERS
b) touching the Password field and entering ADMIN (must be in
capitals) followed by Return, then,
c) pressing LOG ON. RESET
0/0
09:15:06 Security access 06/04/06
It is now necessary to create IDs and passwords for other users, and assign Acess: ADMIN
access levels to them, as described in USER ID MANAGEMENT, below. Name: ADMIN

Identity: ADMIN
LOG OFF PASSWD USERS
Notes:
1 For security reasons, it is recommended that new ADMIN Id and password are entered before any other
actions.
2 When logging on, it is recommended that the Identity field be cleared completely of any characters before
entry of the new Identity. This is be done by positioning the cursor under the first character and operating
the ‘C’ key.
Chapter 4 HA029280
4.4.3 USER ID SYSTEM (Cont.)
USER ID MANAGEMENT
Operation of the USERS key calls up a page which allows user identities, passwords and access levels to be assigned.
The USERS key appears only for users logged in at ADMIN level. Figure 4.4.3a below, depicts the page. Hidden
columns are accessed by a scroll bar which hides the SAVE, CANCEL, NEW etc. keys. When required, these keys
are called to the display by operating the Option key one or more times.
TREND Run prog 3/5
ADMIN Eycon-20 BadBat
Identity Name Access Attributes Reference
ADMIN ADMIN ADMIN 00000000 0

COMMISSI COMISSION COMMISSION 00000000 0
ENGINEER ENGINEER ENGINEER 00000000 0

OPERATOR OPERATOR OPERATOR 00000004 0
Use scroll bar (not to show hid-

den parts of screen.
Use option key to toggle between scroll
bar and pushbuttons.
SAVE CANCEL NEW PROPERTIES MAINT STATS
Figure 4.4.3a User ID Management page
As is depicted above, the opening display shows one user per access level. In order to edit the Identity (including
password), Name, Access level etc. it is necessary only to touch the relevant field (highlights yellow), and edit the
entry as required.
IDENTITY CHANGE EXAMPLE
Note: This procedure is not possible if the unit is fitted with the Auditor option.
To change the Identity ‘ENGINEER’ to ‘Roger” and assign Roger a password of 13. Identity: ENGINEER
Password:
********
Confirm:
1 Touch the word ENGINEER in the Identity column. ********
OK CANCEL DELETE DISABLE
2 Touch the word ENGINEER in the Identity field of the resulting dialogue box Figure 4.4.3b ID Edit page
(figure 4.4.3b).
3 Enter ‘Roger’ using the POP-UP keyboard, followed by Return.

4 Touch the yellow Password field, and enter the number 13 using the keyboard.
5 Touch the yellow Confirm field and enter the number 13 using the keyboard and press OK. If this entry differs
from the first, OK has no effect, and the Confirm field remains highlighted.
To write the changes to the data base, press the SAVE key (first using the Option key to display it, if necessary). Oth-
erwise press CANCEL.
HA029280 Chapter 4
Editing other fields

The editing of remaining fields is carried out in a similar manner, except for the access level field which is selected
from a pick list rather than being typed in as a keyboard entry.
Attributes column
Touching this column allows the ADMIN level user to enable or disable the following functions for all other users:
View only, Admin only, FTP, Remote, User button, User screen. All functions are set to ‘No’ by default. The display
column reflects the features set to ‘Yes’, as shown in the table below. The numbers are cumulative, so, for example, if
‘View only’ and ‘FTP’ were both selected ‘Yes’ and all other items ‘No’, the attribute display would be 00001004
View only Admin only FTP Remote Display
No No No No 00000000
Yes No No No 00000004
No Yes No No 00000010
No No Yes No 00001000
No No No Yes 00002000
Table 4.4.3 Attribute coding
View only Users with this attribute set, have Read Only permission
Admin only This attribute appears only for users with Admin Access level , and means that they can
modify only ADMIN pages. If View only is also set, such users are denied all write
permissions.
FTP Users with this permission may log in via FTP. FTP users who are View only, are prevented
from file system modification, and their logins are not recorded.
Remote If set, this allows the user to log into terminal configurator via telnet (if enabled). The View
Only attribute may be used to determine if the user has write/modify permission. If the
Auditor option is enabled, write permission for the terminal configurator is always disabled
regardless of the View Only setting.
Reference column
For use with user screens, set up in Lin Blocks, this allows individual users, or groups of users allocated the same
reference number, to be identified as being logged on.
Deleting (Retiring) users

To delete a user, touch the required name in the Identity column, and press DELETE in the resulting dialogue box. To
complete the process, press OK in the confirmation dialogue box.
Notes:
1. For units fitted with the Auditor option, the DELETE key is named ‘RETIRE’. See Chapter 6 for more
details.
2. It is not possible to delete the current user.
Disabling user IDs

To disable a user, touch the required name in the Identity column, and press DISABLE in the resulting dialogue box.
The Identity and name of the disabled user appear in red, and the user will not be able to log on, until the login has
been re-enabled. To re-enable the login, touch the required name in the Identity column, then re-enter the password
and confirm it. The Identity and Name return to their previous blue colour.
It is not possible to disable the current user.
Chapter 4 HA029280
New Users
New users are entered using the ‘NEW’ key at the bottom of the page (first using the Option key to display it, if nec-
essary). The new identity and the password are entered as described in the example above.
The new information appears in green, until the SAVE key is operated. (If necessary, use the Option key to display the
SAVE key.)
Notes:
1. For instruments fitted with the Auditor option, it is not possible to create a new user with a previously
‘retired’ ID. See Section 6 for more details.
2. For instruments fitted with the Auditor option, it is not possible to edit any aspect of an account once the
SAVE key has been operated. It is therefore essential to ensure that all entries are correct before saving.
Account properties
Figure 4.4.3c below, shows a typical properties page, called by operating the ‘PROPERTIES’ key at the bottom of the
screen.
Account Properties
Min User Id Length: 2
Min Password Length: 0
Max Login Attempts: 0
Password Expiry: 0 days
User Timeout: 0 minutes
OK CANCEL
Figure 4.4.3c Properties page (typical)
Note: Please also refer to Chapter 6 if the Auditor Option is fitted.
Min User ID Length 2 to 8

Min Password Length 0 to 8
Max Login attempts 0 to 99 (0 = no limit; Values greater than 0 show the number of attempts at logging in that
may be made before the account is disabled.
Password Expiry 0 to 180 0 = password never expires. For values greater than 0, the password will expire after
the specified number of days have elapsed since the last time the value was edited.
User Timeout 0 to 720 0 = no timeout. For values greater than 0 the user will be logged out after the speci-
fied number of minutes has elapsed since the previous screen activity.
HA029280 Chapter 4
Maintenance
Operating the ‘MAINT’ key at the bottom of the Security Access screen calls the ‘Account Maintenance’ screen to the
display, as depicted in figure 4.4.3d, below.
If recovery account is set to YES, this enables a recovery in the event of all ADMIN accounts becoming unusable.
This requires a maintenance contract with the manufacturer.
Account Maintenance
Recovery Account: YES
OK CANCEL
Figure 4.4.3d Maintenance screen
Note: See also Chapter 6 if the Auditor Option is fitted.
Statistics
Operating the STATS key at the bottom of the Security Access screen calls the ‘Statistics’ screen, showing how many
users have been configured out of the total available. For example, Users: 6/100 means that six of the 100 possible
users have been configured.
Note: For small frame instruments, a second operation of the Option key is necessary to reveal the STATS
key.
Chapter 4 HA029280
4.5 SETTING UP AND RE-SETTING THE INSTRUMENT
This section describes the following items
1. Editing Comms parameters (Section 4.5.1)

2. Setting the Start-up strategy (Section 4.5.2)
3. Re-setting the clock (Section 4.5.3)
4. Changing the language and the data entry formats (Section 4.5.4)
5. Setting up the panel display (Section 4.5.5).
4.5.1 Editing communications parameters
The editing procedure for Communications Parameters consists of displaying the Comms Setup page and setting up
or editing the parameters for each port fitted to the unit.
The SAVE button is used to save the changes, or to cancel the changes before saving them, the CANCEL button is
used.
Before any saved changes can take effect, the application must be stopped and then restarted, or the instrument must
be powered off and on again. Generally, ‘parameter’ changes (such as baud rate) require only a stop and restart of the
application, whereas ‘hardware’ changes (such as changing a Modbus master port to a slave port) require a power
down and up.
2
Press SYSTEM
1. Press the Menu key and select SYSTEM from the Pop-up menu.
2. Press SETUP System

1 SUMMARY APPLN
Press menu key
SETUP CLONING
3. Press COMMS.
3 4
Press SETUP
Press COMMS
Setup
STARTUP COMMS CLOCK
The Comms Setup page appears. INTERNAT PANEL
For each port (COM1, COM2, ENET1, ENET2…) there is a column of parameters (Hardware, Protocol, Mode
No…). If necessary, the vertical slidebar can be used to display more parameters hidden further down the page. The
full list is:
Hardware Standard (for example, RS485)
10:49:42 Comms Setup 06/04/06
Protocol (for example, Modbus Slave) PORT COM1 COM2 ENET1
Node Number (decimal) Hardware RS485 RS485 Ethernet
Baud (rate) Protocol Modbus/S ELIN
Parity Node No. 1
Baud 9600
Data bits (number of) If necessary, use
Parity NONE
Stop bits (number of) the option key to
reveal these keys Data Bits 8
Timeout (Modbus Master only, in milliseconds)
SAVE CANCEL ETHERNET
TalkThru (Modbus slave only)
Option key
Figure 4.5.1a Comms setup page
HA029280 Chapter 4
4.5.1 EDITING COMMUNICATIONS PARAMETERS (Cont.)
Cells with a yellow background are edited by pressing them. Others with a white background are fixed (not editable).
A blank cell shows that the parameter does not apply for the protocol selected for that port.
On 1/4VGA instruments a horizontal slide bar can be used to reveal the other ports. The Option key must be used (one
or more times) to display the SAVE, CANCEL, ETHERNET etc. keys, temporarily, in place of the slidebar. XGA
instruments always display these keys.
SOFTWARE PARAMETER EDITING

1. Select the required parameter
2. Select or enter the new value from a pop-up list or keyboard
3. Press the green Return key at the bottom of the pop-up. The new value is displayed.
4. Either press the SAVE button to save the change, or press the CANCEL key to abort the change.
PROTOCOLS AVAILABLE
Notes:
1. Ports in parentheses ( ) are not recommended for the associated protocol.
2. COM1/COM2 ports are always EIA485.
3. All protocols use 8 data bits
4. The Node Number (where presented) must be non-zero to enable the port.
PROTOCOL PORT NOTES

ELIN ENET1 Used to connect a Local Instrument network (LIN) across Ethernet.
FTP ENET2 Used to provide an FTP server.
COM1 (COM2)
MODBUS/M The full name of the protocol is 'Modbus RTU master'.
ENET4
COM2 (COM1) The full name of the protocol is 'Modbus RTU slave. Used for the 'Talk-thru' facility,
MODBUS/S ENET3 and for direct connection with a Modbus master. ENET3 port is for Modbus/TCP.
COM1 and /or
Printer Used to send reports and/or alarms to a serial printer
COM2
Table 4.5.1 Available protocols
Changes to Protocol selection become effective at different times, as follows:

ELIN1,2,3 On power up.
ENET4 On application start.
ENET5 On power-up.
COM1/COM2 On application start.
TALK-THRU
Talk-Thru, (or transparent Modbus access) is a facility provided to enable use of the Eurotherm iTools package to
configure Model 2500 controllers without having to disconnect them from the Visual Supervisor. The 2500s are con-
nected to the Instruments’s Modbus Master port as shown in section 1.3.5.
The PC is connected to the Modbus Slave port on the front panel via an EIA232 link. With the iTools package running
on the PC, the Model 2500 units can then be configured by ‘talking through’ the Visual Supervisor.
Notes:
1. In order for TalkThru to work, the database must contain a Gateway file (.GWF) for Modbus slave and
for Modbus master, both of which are referenced in GW_CON blocks.
2. PC/iTools can be connected to the Modbus COM1/2 port, but needs an EIA422/485 converter.
3. For more information refer to the iTools Help system.
4. The PC may be connected across Ethernet using Modbus/TCP instead of one of EIA422/485.
Chapter 4 HA029280
4.5.1 EDITING COMMUNICATIONS PARAMETERS (Cont.)
ETHERNET
The following applies only if the Ethernet option is fitted.
Notes:
1. Before operating the ‘ETHERNET’ button, operate the ‘SAVE’ button, or all changes made so far will be
lost.
2. Before operating the COMMS button to return to the Comms setup page, operate the SAVE button, or all
changes made in the Ethernet setup page will be lost.
3. On the small frame (1/4 VGA) version of the instrument, the three buttons ‘SAVE’, ‘CANCEL’
and ‘ETHERNET’ are hidden by a scroll bar. The Option key is used to toggle between the scroll
bar and these buttons. Option key
4. The user must have suitable access permission in order to edit the Ethernet setup.
Ethernet setup is accessed by operating the ‘Ethernet’ key at the bottom of the comms set-up page. Figure 4.5.1b
shows the relevant fields. To return to Comms setup, operate the Comms button.
LIN Protocol setup

Protocol Name: MYENET
All subnet Enable: YES
Local IP Setup
MAC Address: EO:00:05:4B:D1:0B
Address Assignment: Fixed
IP Address: 149.121.165.183
Subnet Mask: 255.255.252.0
Default Gateway: 149.121.164.253
Remote Subnet Node List

Number of Nodes: 1
Node 1: 0 . 0 . 0 . 0
SAVE CANCEL COMMS
Figure 4.5.1b Ethernet setup items
Protocol name Allows the user to enter a protocol name of up to 12 characters.

All Subnet enable Select Yes or no.
MAC ADDRESS This factory-set address is unique to the instrument and is non-editable.
Address Assignment Select one of: Fixed, DHCP, BootP, DHCP+LL, BootP+LL, Link Local.
IP Address May be edited only if ‘Fixed’ selected as Address assignment.
Subnet Mask May be edited only if ‘Fixed’ selected as Address assignment.
Default Gateway May be edited only if ‘Fixed’ selected as Address assignment.
Number of nodes Enter 0 to 50. This is the number of nodes in the remote subnet.
Node N: Allows the IP address of each remote node to be entered.
HA029280 Chapter 4
MODBUS/TCP
For each relevant slave node, an entry must be made in the Modbus/TCP mapping table (figure 4.5.1c) which is ac-
cessed by touching the MODBUS/TCP key at the bottom of the Comms setup page (figure 4.5.1).
TREND Run prog 3/5
LOCKED T800 BadBat
RUNNING 05:07:45 2 TREND Fred
MODBUS_1/TCP
4 4 149.121.128.234 502
7 7 141.121.128.231 502
Instrument No.: 7
OK CANCEL DELETE
Figure 4.5.1c Modbus mapping table
To edit the values for an existing slave, touch the relevant field (as shown above for ‘Instrument’), and then touch the
current value. This causes a pop-up keyboard to appear, allowing the user to enter a new value. Changes take place
only after the SAVE key at the bottom left of the screen has been operated.
New slaves can be added by touching the ‘NEW’ key, and editing the values which appear in the resulting dialogue
box.
Instrument This entry is the number which appears in the InstNo column in the GWF Modbus table.
Slave Address This value (sometimes called the Modbus address) is what the slave expects to see in any message sent
to it.
Host The IP address of the relevant Slave Node.
TCP Port This is the port used for the connection. The default (502) should be used unless the slave documenta-
tion advises otherwise.
Chapter 4 HA029280
4.5.2 Setting the start-up strategy
Hot and Cold starts are ways of starting the instrument automatically, after a power failure or after a power variation
large enough to trigger an alarm (a ‘brown out’). The strategy is set by choosing Hot Start, Cold Start or both, and by
choosing time-out intervals for Hot Start and Brown Out.
HOT/COLD START CRITERIA

The type of start selected depends upon the process, and upon the operational policy of the user. For example, some
processes are so sensitive that a power-loss of any duration will always mean that the process plant or the load, or
both, will need manual attention before re-starting. In this case automatic restart (either hot or cold) would be inappro-
priate.
Hot start and Cold start selected

The most common strategy is to set both the Hot Start and the Cold Start to YES so that, should power return before
the end of the time-out, the instrument will attempt a Hot Start. If the time-out has expired the instrument makes a
Cold Start.
Hot Start only.

A power loss, or a ‘brown-out’ lasting long enough to trigger an automatic restart, which returns to normal before the
Hot Start time-out, causes the instrument to attempt a Hot Start. If the power does not return to normal within the
time-out period, a manual restart will be required, as described in section 3.1.1 (Running a program now).
Cold start only

If a power loss, or a ‘brown-out’ lasting long enough to trigger an automatic restart occurs, then, provided that power
returns before the Hot-start time-out interval, the instrument will do a Cold Start on power-up.
Neither Hot start nor Cold start 2

If both Hot start and Cold start are set to ‘No’ the instrument will not re- Press SYSTEM
start automatically under any circumstances. ACCESS SYSTEM ALARMS

START-UP STRATEGY PAGE
System
1. Press the Menu key
1 SUMMARY APPLN
Press menu key
2. SYSTEM from the pop-up menu. SETUP CLONING
3
Press SETUP
3. Select SETUP Setup

4 STARTUP COMMS CLOCK
Press
STARTUP INTERNAT PANEL
4. Select STARTUP
0/0
RESET
09:16:14 Startup Strategy 06/04/06
Hot Start: YES

Cold Start: YES
Hot-start time: 00:00:00
The Start-up Strategy page appears
Brown-out time: 00:05:00
SAVE CANCEL
HA029280 Chapter 4
4.5.2 SETTING THE START-UP STRATEGY (Cont.)
Hot start A Hot start uses data about the current application that the instrument automatically saves in
case of power variation or failure. Using this information, which is preserved through any
power loss, the instrument can automatically restart the process at any time after normal power
returns.
In the fields on the Start-up Strategy page, the following items need to be configured:
1. Whether the process is to start automatically after a power loss
2. A maximum time period (time-out), after the expiry of which, a hot start is inappropriate.
Cold-Start Cold Start data is application data, not just program data, so its scope is much wider.
Hot start time: This depends upon the process under control. If the process can tolerate only a short time
without normal power before either the plant or the load requires manual attention, then a short
time-out needs to be set. If, however, the process is robust enough to regain normal processing
conditions even after a lengthy power-outage, then a longer Hot Start time-out may be set.
Actual times are process-dependent, but the general rule is that the process must not restart
automatically beyond the time when it requires manual attention.
Brown-out time This sets an alarm when a power-variation has persisted for longer than a preset time. Unless
the alarm is set up to take some action, the Brown-out time acts only as a warning, in case
some special strategies exist that might need implementing in those circumstances, or that
have been set up to run automatically.
If power totally fails but returns within the interval specified as Brown-out time, then the
instrument treats it as a brown-out. If it returns after the Brown-out time, then a restart is either
possible or certain, depending on how soon after the time limit it returns.
The type of restart attempted depends on the programmed strategy.
CHANGING START-UP VALUES

0/0
RESET
Changing Hot/Cold start settings 09:16:14 Startup Strategy 06/04/06
Hot Start: YES

In the Startup Strategy page, press the Startup setting to be changed. Edit Cold Start: YES
the entry using the pick-list which appears, then press Return. The pick- Hot-start time: 00:00:00
list disappears and the Startup Strategy page displays the new value. Brown-out time: 00:05:00
SAVE CANCEL
Changing time-out values

simple 0/0
IDLE ??/??/??
09:16:31 Startup Strategy 06/04/06
00:10:00
In the Startup Strategy page, press the time-out value to be changed. Key- 7 8
Hot9Start: YES
in the new value using the pop-up keyboard, then press Return. The field Cold Start: YES
4 5 6
shows the new value. Hot-start time: 00:10:00
1 Brown-out
2 3 time: 00:05:00
. 0
SAVE CANCEL
Chapter 4 HA029280
2
4.5.3 Resetting the clock
Press SYSTEM

CLOCK SETUP PAGE ACCESS
1 Press the Menu key

System
2. Select SYSTEM from the pop-up menu 1 SUMMARY APPLN
Press menu key SETUP CLONING
3 Select SETUP. 3
Press SETUP
Setup
STARTUP COMMS CLOCK 4

4 Select CLOCK. Press
INTERNAT PANEL CLOCK
0/0
RESET
14:52:06 Clock setup 06/04/06
The date/time setting page appears Date: 06/04/06

Time: 14:51:37
SET CANCEL Hr +1 Hr -1
CHANGING DATE AND TIME
To increment or decrement the hours value, press the Hr+1 or the Hr-1 key respectively. The change takes place im-
mediately, and changes the date if appropriate.
Notes:
1 Operating the SET key enters the time and date displayed on the page. These values are not updated in
real-time, but show the values obtaining when the page was called to the screen. As it is not possible to
SET the date separately from the time, it is recommended that the date be changed first, then the time.
2. The clock re-starts when the SET key is pressed. This happens after the time has been keyed in and after
the Return key has been pressed. It is therefore recommended that the keyed-in time is at least 20 sec-
onds ahead of real time, so that the SET key can subsequently be operated (to start the clock) when real-
time equals the keyed-in time.
3. For systems configured to have their clocks synchronised by another network node, it is not possible to
edit the time or date if the master clock is running.
Date changing
From the Clock Setup page, touch the date field.
A numeric keyboard is displayed, allowing the correct date to be entered.

The cursor moves to the next digit after each character has been entered. RESET
0/0
15:02:50 Clock Setup 06/04/06

06/04/06
To cancel all the digits (the ones at the top of the keyboard display, but not Date: 06/04/06
7 8 9
the ones in the Clock Setup page in the background, or in memory), press Time: 15:01:22
4 5 6
the ‘C’ key - the digits change to question marks.
1 2 3
To cancel the whole time-change operation and return to the Clock Setup . SET 0 CANCEL Hr +1 Hr -1
page, press the red cross key.
Once the correct date has been entered, operate the Return key. To save
the entry and re-set the date press the SET key.
HA029280 Chapter 4
4.5.3 RESETTING THE CLOCK (Cont.)
TIME CHANGING
0/0
RESET
15:07:33 Clock setup 06/04/06
Before starting, please see note 3 on the previous page.
15:08:00
Date: 06/04/06
7 8 9
From the Clock Setup page, press the time field. Time: 15:05:07
4 5 6
A keyboard is displayed, with the current time displayed in green at the top 1 2 3
with a cursor flashing under the first hours digit. . SET 0 CANCEL Hr +1 Hr -1
Type-in the required time (the cursor moves to the next character after each
number is keyed-in)
To cancel all the digits (the ones at the top of the keyboard display, but not the ones in the Clock Setup page in the
background, or in memory), press the ‘C’ key - the digits change to question marks.
To cancel the whole time-change operation and return to the Clock Setup page, press the red cross key.
When new time has been entered, press the green Return key.
When the actual time is the same as the time just entered, press the SET key to re-start the clock.
4.5.4 Changing language and date/time formats
A different language can be selected only if the instrument holds the appropriate language dictionary file. See section
5.2, The System text dictionary. 2
Press SYSTEM
1 Press the menu key. ACCESS SYSTEM ALARMS
The Pop-up menu appears.
2 Select SYSTEM. System

The System Pages window appears.
1 SUMMARY APPLN
Press menu key SETUP CLONING
3
3 Select SETUP.
Press SETUP
The Setup window appears Setup
4 STARTUP COMMS CLOCK
Press
4. Select INTERNAT.
INTERNAT INTERNAT PANEL
0/0
RESET
15:17:05 Internationalise 06/04/06
Language: English
Date Format: DD/MM/YYYY (DD/MM/YY)
Time Format: HH:MM:SS
Duration Fmt: DD-HH:MM:SS.TTT
The Internationalise page appears.
CHANGE
The following subsections describe each of the four yellowed fields displayed on the Internationalise page.
Chapter 4 HA029280
4.5.4 CHANGING LANGUAGE/DATE FORMAT (Cont.) RESET

0/0

English
LANGUAGE Language: English
If the Language field is touched, a pick-list appears, showing which lan- Date Format: DD/MM/YYYY (DD/MM/YY)
ENGLISH
guages are available. Select the required language and press Return. FRENCH
GERMAN
SPANISH
The pick-list disappears.
CHANGE
Press CHANGE. The Language field shows the selected language
0/0
RESET
DATE FORMAT DD/MM/YYYY

Language: English
If the Date Format field is touched, a pick-list of the available Date For- Date Format: DD/MM/YYYY (DD/MM/YY)
DD/MM/YYYY
mats appears. Select the required format and press Return. MM/DD/YYYY
YYYY/MM/DD
DD-mmm-YY Fmt: DD-HH:MM:SS.TTT
Duration
The pick-list disappears. mmm-DD-YY
CHANGE
Press CHANGE. The Date Format field shows the selected format.
0/0
RESET
TIME FORMAT HH:MM:SS
Language: English
If the Time Format field is touched, a pick-list of the available time for- Date
HH:MM:SSFormat: DD/MM/YYYY (DD/MM/YY)
mats appears. Select the required format and press Return. hh:MM
Time XM
Format: HH:MM:SS
hh:MM xM
CHANGE
Press CHANGE. The Time Format field shows the selected time format.
0/0
RESET
If the Duration Format field is touched, a pick-list of the available time 15:24:57 Internationalise 06/04/06
DD/MM/YYYY
duration formats appears. Language: English
Date Format: DD/MM/YYYY (DD/MM/YY)
DD/MM/YYYY
Select the required format and press Return. MM/DD/YYYY
YYYY/MM/DD
DD-mmm-YY Fmt: DD-HH:MM:SS.TTT
Duration
mmm-DD-YY
CHANGE
Press CHANGE. The Duration Format field shows the selected format.
HA029280 Chapter 4
4.5.5 Setting up the panel display
The following items can be edited from the Panel Setup page:
1. Backlight properties
Display Normal and Saver brightness
Saver Time-out (a value of 0 means no time-out)
Saver brightness is the screen brightness when the screen saver timeout expires.
2. Page time-out values (a value of 0 means no time-out)

Home (for any Home pages)
Pop-up (for the Pop-up menu)
Data Entry (for the pick-lists and keypads)
3. Time-out to return to Access Level ‘Locked’ (a value of 0 means no time-out). 2

If this is enabled (by adding an entry into the text dictionary (Section 5.2.4, Press SYSTEM
No. 331)) then a time-out period can be set. If the screen is not touched ACCESS SYSTEM ALARMS
during this period, the instrument access level returns to ‘Locked’.
ACCESS TO THE PANEL SETUP PAGE System
1 SUMMARY APPLN
1 Press the menu key. Press menu key SETUP CLONING
3
2 Select SYSTEM. Press SETUP
Setup
3 Select SETUP. STARTUP COMMS CLOCK
INTERNAT PANEL
4
Press PANEL
4 Select PANEL. 15:48:12 Panel Setup 06/04/06

BACK-LIGHT
Brightness: 70%
Saver brightness: 20%
Timeout: 0 minutes
The Panel setup page appears
PAGE TIMEOUTS
‘Access’ appears
Home: 0 minutes
only if the relevant
Pop-up: 0 seconds
entry has been
Data Entry: 0 made in the text
seconds
Access: 0 dictionary.
minutes
SAVE CANCEL
DISPLAY BRIGHTNESS SETTINGS

To prolong backlight life, it is recommended that the normal brightness be set to 70% or lower and that the screen
saver be used if the instrument is on but not continuously manned. Pressing either the Brightness or Saver Brightness
fields brings up a pick-list of alternative percentage values, staged at 10% intervals.
15:56:21 Panel Setup 06/04/06
Choose the required value(s), then Press Return 70% BACK-LIGHT
Brightnes
Brightness: 70%
Saver brightness:
brightnes 20%
The pick-list disappears. 100% Timeout: 0 minutes
90%
80% PAGE TIMEOUTS
70% Home: 0 minutes
To save the selection, press SAVE. 60% Pop-up: 0 seconds
Data Entry: 0 seconds
Access:
A ess: 0 minutes
SAVE CANCEL
Chapter 4 HA029280
4.5.5 SETTING UP THE PANEL DISPLAY (Cont.) 15:57:27 Panel Setup 06/04/06
BACK-LIGHT
BACK-LIGHT 0
Brightness: 70%
7 Saver8 brightness:
9
TIME-OUTS Timeout:
20%
0 minutes
4 5 6
PAGE TIMEOUTS
Pressing any of the other fields brings up a numeric keyboard, from which 1 2 Home: 3 0 minutes
Home:
Pop-up: 0 seconds
new values for the various time-outs can be entered. . DataPop-up:
0Entry: 0 seconds
Da
DataAccess:
Entry: 0 minutes
After each entry, press Return. SAVE CANCEL
The keyboard disappears.
To save the value, press SAVE.
DATA ENTRY
Note: The following adjustment applies only to XGA (large screen) units.
The size of the Data Entry pop-up can be reduced by selecting ‘Small’ for the item ‘Data entry’
HA029280 Chapter 4
4.6 CLONING AN INSTRUMENT
Cloning an instrument consists of copying data between instruments via a USB Bulk storage device, in order to repli-
cate either the characteristics of the instrument or of the application, or of both.
It can also be used to backup data (for example, programs).
Notes:
1. If Intellectual Property Rights Protection (IPRP) (section 4.9.1) is enabled, then data may be cloned only
to the original instrument, or to another with the same IPRP settings.
This section consists of the following subsections:

Accessing the Cloning page (Section 4.6.1)
Cloning application data (Section 4.6.2)
Cloning system (instrument) data (Section 4.6.3)
Cloning both application and system data (cloning ALL) (Section 4.6.4).
2
4.6.1 Accessing the cloning page Press SYSTEM
1 Press the Menu key PROGRAMMER LOGGING HOME
2 Select SYSTEM. System

1 SUMMARY APPLN
Press menu key
3 Select CLONING SETUP CLONING
3
Press CLONING
0/0
RESET
The Cloning page appears. 16:14:25 Cloning 06/04/06
Application
4 Press the Application field (yellowed)
EXPORT IMPORT
0/0
RESET
16:14:55 Cloning 06/04/06
Application
A pick-list appears, allowing ‘System’, ‘Application’ or ‘ALL‘ to be
Application
selected System
Application
All
The highlighted field (‘Application’ in this example) indicates which
type of data was last selected for cloning.
EXPORT IMPORT
Chapter 4 HA029280
4.6.2 Cloning application data
This consists of:

1. Exporting application data
2. Importing application data
EXPORTING APPLICATION DATA
From the Cloning page, select Application. 16:19:27 Cloning 06/04/06

Application Data
Control Database: NO
The Application Data Cloning page appears displaying the following fields, SFCs: NO
described below Programs/Recipes: NO
User Pages: NO
Forms: NO
1 Control Database
Comms Profiles: NO
2 SFCs (Sequential Function Charts)
EXPORT CLEAR
3 Programs/Recipes
4 User pages
5 Forms
6 Comms Profiles
Control Database This is the instrument’s LIN database, consisting of file types .cpf, .dbf, .gwf, .run, .uya, and
.uyn.
SFCs Sequential Function Charts are part of any special strategies in software that may have written
to support particular events, circumstances or requirements. They consist of .sdb files.
Programs/Recipes Setpoint programs and/or recipes that have typically have been created on this instrument and
which the user now wishes to copy to another instrument. Recipes and Programs consist of
.uys and .uyr files, and if Batch files are present, .uyb files.
User pages Written by users to satisfy the control requirements of their particular process. User pages may
consist of a single Home page, or a hierarchy of user pages with a Home page at its root. They
consist of .ofl and .pnl files.
Forms Text files that determine how reports are generated. Consist of .uyt and .uyf files.
Comms Profiles Parameters that determine how the instrument communicates with other instruments. Consist
of .uxm file.
Once the required fields have been set to YES the data is exported by touching the EXPORT key at the bottom of the
page.
IMPORTING APPLICATION DATA
From the Cloning page, select IMPORT. The same page as for exporting (shown above) appears with the same fields.
Notes:
1. Imported user pages take immediate effect.
2. .pnl files need the application to be unloaded and reloaded to take effect.
3. Imported Comms profiles need the application to be restarted to take effect.
HA029280 Chapter 4
4.6.3 Cloning system (instrument) data

0/0
RESET
16:24:26 Cloning 06/04/06
SELECTING SYSTEM DATA Application
Application
System
From the Cloning page, showing the pick-list of System, Application and Application
All
All, select System
EXPORT IMPORT
Press Return
0/0
RESET
16:26:20 Cloning 06/04/06
The Cloning page confirms the selection. System
EXPORT IMPORT
0/0
EXPORTING SYSTEM DATA RESET
16:28:30 Cloning 06/04/06
System Data
Select EXPORT.
Config Options: NO
The System Data Cloning page appears with three fields as described below: Dictionaries: NO
User Pages: NO
1, Config Options
2. Dictionaries EXPORT CLEAR
3. User Pages
Config Options These are: startup strategy, panel settings, comms settings, and current language. Basically they are
instrument operation preferences. If the Auditor pack option is enabled, Security Access (if the unit
is an Access System Master), Network Audit Trail Setup and Signature Setup are also presented.
Dictionaries Dictionaries are items within Customisation (see Chapter 5 of this manual).
User pages User pages also form part of Customisation.
Note: If Access is selected, the exported data must be imported into the destination unit within 60 minutes of
export time.
IMPORTING SYSTEM DATA
Imported config options apply on next power-up; dictionaries apply on next power-up or on next change of prefer-
ences.
From the Cloning page, select IMPORT. The same page appears as for exporting (shown above) and the same expla-
nations apply.
Note: An instrument may import access data only if it has been exported by the source unit within the
previous 60 minutes.
Chapter 4 HA029280
4.6.4 Cloning both application and system data (ALL)
From the Cloning page, select ALL.
Thereafter the procedures are similar to those in sections 4.6.2. and 4.6.3.
HA029280 Chapter 4
4.7 FILE MANAGER
The File Manager allows the copying of files between the internal Flash memory and a USB drive, or another, net-
worked instrument. It also allows files to be deleted from the internal memory (except from the ‘H’ drive - the inter-
nal archive). As shown in the figures below, any application must be stopped and unloaded before File Manager can
be accessed.
4.7.1 Stopping the application
Figure 4.7.1 shows the keystrokes necessary to stop the application.
4.7.2 Calling the file manager
Once the application has been stopped, it can be unloaded and the File Manager called from the 'Maintenance' pop-up
as shown in figure 4.7.2.
2 16:41:05 Appl'n Manager 06/04/06

Press SYSTEM key
File: Colours
1 ACCESS SYSTEM ALARMS
State: STOPPED
Press menu key OVERVIEW PROGRAMMER LOGGING
System
SUMMARY APPLN UNLOAD SAVE SAVE AS STOP

3 6
SETUP CLONING Press APPLN key Press UNLOAD
16:41:25 Appl'n Manager 06/04/06

Application
APP SUM APP MGR FB MGR File: ????????

4
Press APP MGR
SETUP MAINT EVT LOG
16:39:59 Appl'n Manager 06/04/06
File: Colours
LOAD LD+RUN DELETE
State: RUNNING
7 8 Press MAINT
Press menu key
9
STOP Maintenance
5 Press FILE MGR
CLONING FILE MGR
Press STOP
SOFT OPTS BATCH MAINT
Figure 4.7.1 Application stop Figure 4.7.2 Calling the file manager
Chapter 4 HA029280
4.7.3 File Copy and Delete
Operation of the 'FILE MGR' button in the 'Maintenance' pop-up calls the File Manager page. Once this page is on
display, either an individual file name can be selected from the relevant drive and the copy or delete key operated, or
the COPY ALL/DEL ALL keys can be used to copy or delete all the files, within the selected filter, on that drive.
CAUTION
1. Files of the form _SYSTEM.XYZ* must not be deleted or the instrument will not operate correctly and
revert to a factory configuration
2. The file _DEF AULT.OFL must not be deleted or the faceplates in the overview page will fail to operate
correctly ,
*XYZ is any three character extension..
16:57:14 File Manager 06/04/06

Node: 1
Device: E:
Filter: *.*
File: _SYSTEM1.UYL
Size: 11395 bytes
Free Space: 628084 bytes
COPY COPY ALL DELETE DEL ALL
Copy File Confirm Delete

File: E:_SYSTEM1.UYL File: E:_SYSTEM1.UYL
Copy to OK CANCEL
Node: 1
Device: E:
File: CAUTION
Files must not be deleted from the ‘E’ drive
OK CANCEL
unless it is certain that the control system will
not be impaired by so doing. See the caution-
ary notes above.
Figure 4.7.3 Copy and delete
Node For ELIN systems only, the (decimal) number of the LIN node to be accessed
Device Selectable as E (internal flash memory) or if any of the following are fitted: B (USB Bulk
storage device) or H (internal archive).
Filter Allows file display to be limited to certain types of files.
For example, *.* shows all files, whereas, an entry of *.DBF allows only files with .DBF
suffix to appear. See 'File' immediately below.
File Touching this area causes a scroll list of files to be displayed and to be selected (one at a time)
for copying or deleting. The range of files displayed can be limited by entering a display
'filter' to limit the scroll list to certain file names or file types.
Size Shows the size of the selected file.
Free space Shows the remaining capacity of the drive selected.
HA029280 Chapter 4
4.7.4 Reloading the application
Operation of the menu key, followed by the APP MGR button in the pop-up menu, returns to the Application Manager
page, which allows a file to be selected to be the application. Once a file name has been selected, operation of the
LOAD key and then the START key or the LD+RUN key, returns the unit to normal operation.
17:01:10 Appl'n Manager 06/04/06
File: ????????

10
SETUP MAINT EVT LOG Press APP MGR
LOAD LD+RUN DELETE
9
Press menu key
17:01:57 Appl'n Manager 06/04/06
File: ????????
LOAD LD+RUN DELETE
Figure 4.7.4 Regaining the Application Manager Page
4.8 RECIPE MANAGEMENT
4.8.1 Creating recipe files
A ‘blank’ recipe file (i.e. a recipe file with no values) can be created from the recipe file page. The recipe editor can
then be used to add values.
4.8.2 Recipe editing
The recipe editor is called by pressing ‘EDIT’ from the recipe menu.
Note: For units fitted with the Auditor Option, an edited recipe must be Saved before it can be downloaded.
ADD RECIPE LINE

If a spare line is available, a new line can be added by pressing the ‘ADD LINE’ button. (The Option key may need
pressing one or more times in order to display this key.) Once added, the RCP (Recipe) cell at the top left of the dis-
play can be pressed to change the name of the selected line.
Chapter 4 HA029280
4.8.2 RECIPE EDITING (Cont.)
ADD A VARIABLE
A new variable can be added by touching that cell in the left-most (RCP) column, which is immediately above the cell
where the new variable is to appear. A Properties Menu appears, which allows the variable name and tag references to
be entered.
Note: variables are executed in ‘top-down’ order, so the order in which variables appear can be important.
To add the first variable, press the RCP cell, then the INSERT key on the pop-up menu. The name and tag references
of the variable can now be entered. If applicable, Capture and Monitor values can also be edited. The verify field
allows the user to define ’Verify’ as ‘Yes’ or ‘No’. If set to No, the variable is not checked, during download, to en-
sure that the value is correctly written. ‘No’ is used, for example, where a variable may reset itself or change.
Figure 4.8.2a shows a typical properties dialogue box.

TREND Amarillo 3/5
Fred
RUNNING 05:07:45 2 GASCONC
Gas Mix
RCP Amarillo Q8 EkoFisk
Methane 90.6724 90.6724 90.6724
Nitrogen 3.1284 Properties 3.1284 3.1284
Carbon Dioxide 0.4676 Name: Carbon
Variable 0.4676
Dioxide 0.4676
Ethane 4.5279 V e r i f y : Y E S 4.5279 4.5279
Propane 0.828 0.8280 0.8280
Water 0.0 0.0000 0.0000
Tag references
HydrogenSulphide 0.0 0.0000 0.0000
Line: 1
Hydrogen 0.0 0.0000 0.0000
S P : GasConc.CrbDiOx
Carbon Monoxide 0.0 0.0000 0.0000
Oxygen 0.0 0.0000 0.0000
i Butane O
0.1037K D E L E T E
0.1037 INSERT 0.1037
n Butane 0.1563 0.1563 0.1563
i Pentane 0.0321 0.0321 0.0321
n Pentane 0.0443 0.0443 0.0443
n Hexane 0.0393 0.0393 0.0393
n Heptane 0.0 0.0000 0.0000
n Octane 0.0 0.0000 0.0000
n Nonane 0.0 0.0000 0.0000
n Decane 0.0 0.0000 0.0000
Helium 0.0 0.0000 0.0000
SAVE CAPTURE CAPTURE AS DOWNLOAD ABORT
F1 F2 F3 F4 F5 F6 F7 F8 F9
F10 F11 F12 F13 F14 F15 F16 F17 F18
F19 F20 F21 F22 F23 F24 F25 F26 F27
Figure 4.8.2a Properties dialogue box

TAG REFERENCES
Touching a variable in the RCP column , calls the Properties menu. This menu allows the variable name, tag refer-
ences and verification setting to be edited.
RECIPE VALUE
Touching a value in a recipe column, allows a new value to be entered.
ADDING A RECIPE
To add a new recipe, select an existing recipe to act as a model, and touch that recipe’s name. Select NEW from the
dialogue box which appears. The new recipe takes the values of the model, and can be edited as required.
DELETING RECIPES
Touch the recipe name (at the top of the column), then select DELETE from the pop-up dialogue box.
HA029280 Chapter 4
4.8.2 RECIPE EDITING (Cont.)
SAVING RECIPES
To save changes to the current file name, operate the SAVE button. To make a copy of the file, press SAVE AS.
RECIPE FILE PROPERTIES

Touching the RCP cell calls the Recipe File properties dialogue box to the display. This gives the name of the recipe
file and the line currently selected, as well as details of the previous file edit. The version field is incremented each
time the file is saved.
Further to this there is an editable timeout field allowing a value to be entered to timeout a successful download of a
recipe.
Id: SET1
File Name: GASCONIC
Line: 1
Version: 5
Edited by: Fred
At: 11:50:57 23/11/00
Timeout: 30 seconds
OK INSERT
Figure 4.8.2b Recipe File properties box
4.8.3 Capturing a Recipe
With a recipe file loaded and a recipe selected it is possible to ‘capture’ live values from the running application, for
display in the Recipe Monitor page (either in the ‘Capture’ column if available, or in the SP (Live) column if not).
Operation of the CAPTURE button in the monitor page overwrites the existing values in the selected recipe. CAP-
TURE AS, creates a new recipe with the captured values.
Once values have been captured, they can be modified as required in the Recipe edit page.
Chapter 4 HA029280
4.9 OEM FEATURES
4.9.1 Intellectual Property Right Protection (IPRP)
The IPRP feature is provided to allow OEMs, for example, to prevent unauthorized copying of application files. To
determine if a feature is enabled, view the software options page (section 2.1.3).
If IPRP is enabled:
1. Files on the E: drive may not be copied from the instrument either to the USB memory stick (if fitted) or via
network (ELIN or FTP) operations.
2. All files on the E: drive may be modified using normal user interface operations.
3. New files may be added to the E: drive, but they may not be copied from the instrument.
4. Existing files may be overwritten by new files, with the same name, across a network.
5. Files are ‘scrambled’ when cloned out of the instrument, so clone files can be used only in the source instrument
or in another instrument with the same IPRP password (see below).
MODIFYING IPRP SETTINGS

The procedure for modifying the IPRP settings is to create a text file, to copy it to the E: drive, and then to power
cycle the instrument.
The text file must be called _OEM.TXT and consists of a single line containing comma-separated items as follows:
OEM,1,current password,new password,enable/disable
Where the items have the following definitions:

OEM Non variable text string.
1 Non variable value.
Current password The current password. As despatched from the factory, this is:
_OEM_OEM
If the current password is entered incorrectly, the file is ignored.
New password The required new password of up to eight characters. If left blank, the password remains
unchanged.
Enable/disable 0 = IPRP disabled (off); 1 = IPRP enabled (on). If left blank, the setting remains unchanged.
For example, to change the default password to ‘Richard1’ and enable IPRP, the file content should be as follows:
OEM,1,_OEM_OEM,Richard1,1
Note: Space characters are included in the password. Commas are not allowable as password characters.
HA029280 Chapter 4
4.10 BATCH MAINTNEANCE
Whenever a batch is loaded, the instrument seeds the batch id with a sequence number (starting from 00000001) to
provide a unique batch ID. This number increases throughout the life of the instrument to ensure the batch ID is
unique within this instrument. If it is ever required to modify this sequence number the BAT MAINT utility may be
used to do this. Possible reasons are replacement of existing instrument or to reset after a commissioning phase. This
utility is accessed as shown in figure 4.10, below.
2 09:59:48 Appl'n Manager 07/04/06

Press SYSTEM key
File: Colours
1 ACCESS SYSTEM ALARMS State: STOPPED
System
SUMMARY APPLN
3 6
SETUP CLONING
Press UNLOAD
Press APPLN key
10:00:06 Appl'n Manager 07/04/06
Application

4
Press APP MGR
SETUP MAINT EVT LOG
09:29:59 Appl'n Manager 07/04/06
File: Colours LOAD LD+RUN DELETE

State: RUNNING
8 Press MAINT
7
Press menu key
STOP Maintenance
9
5 Press
CLONING FILE MGR
Press STOP BATCH MAINT
Figure 4.10 Batch Maintenance access
The batch sequence number (ID) that was last used is displayed. This may be modified to a new value (the next batch
run will take this new value +1). The ID is edited by touching the current Id value, then keying in the required value
using the pop-up keyboard which appears.
This facility must be used with caution as, if multiple log files with the same batch ID are imported into Review soft-
ware, it will view them as the same batch. Unless this is the intention, any records of previous batches with the same
ID should be removed from Review before the ID is reset.
Chapter 4 HA029280
CHAPTER 5: CUSTOMISING
This chapter describes how to customise the Standard Interface; it consists of the following sections:
5.1 Introduction 5.9 Form files
5.2 The System text dictionary 5.10 Recipe files
5.3 The Error text dictionary 5.11 The writeable dictionary
5.4 The Event text dictionary 5.12 The recipe dictionary
5.5 The User text dictionary 5.13 The batch dictionary
5.6 The Programmer text dictionary 5.14 Batch files
5.7 Panel navigation 5.15 Database change audit trailing
5.8 Database names
5.1 INTRODUCTION
5.1 to 5.8, show how to replace the supplied screen-displayed texts with ones more suited to a particular process, in a
different language and so on.
Each of these can involve either:

1. replacing text items displayed by the instrument’s Standard Interface; and/or
2. writing new text, either for any other national language versions of the Standard Interface that might be required,
or for any so-called User-screens being developed.
5.9 describes how to format reports. 5.10 to 5.15 contain details of how to create or edit recipe, batch and card-reader
files.
5.1.1 The dictionaries
Displayed texts are held in files called dictionaries, covered in sections 5.2 to 5.6 and 5.11 to 5.13. There are specific
customisable dictionary files for each of the following types of texts:
1. Standard Interface, excluding the Error and Event messages
2. Error messages
3. Event messages
4. The texts of any User pages (the ‘User screens’)
5. Programmer texts.
6. Writeable (modifiable) texts for use with the batch system and in reports.
7. Recipe texts
8. Batch texts
The texts of the Standard Interface are held in the System text dictionary, Error messages are held in the Error Text
dictionary, and Event messages are held in the Event Text dictionary. These three dictionaries make up the _system.uyl
file.
User screen and Programmer text dictionaries are initially empty, for users to fill as required. These two dictionaries
make up the _user.uyl file.
HA029280 Chapter 5
5.1.1 THE DICTIONARIES (Cont.)
DICTIONARY NAME FILE NAME RECORD SYNTAX

System text _system.uyl S<N>,<text>
Error text _system.uyl E<N>,<text>
Event text _system.uyl V<N>,<text>
User text _user.uyl U<N>,<text>
Programmer text _user.uyl P<N>,<text>
Writeable text _user.uyl W<N>,<initial text>
Recipe texts Not applicable Not applicable
Batch texts Not applicable Not applicable
where <N> is the index number of the record (section 5.2.2. File structure).
Customising an existing .uyl file or building a new one is done by editing the files on a PC using a standard text editor
(for example, Windows Notepad) and then cloning them into the Visual Supervisor by USB device.
5.1.2 Panel navigation and database names
Panel navigation (section 5.7) describes how to change the layout (the architecture) of the Standard Interface. A com-
pletely new architecture can be created if required.
Database names (section 5.8) describes how to change the names of function blocks, alarms, and of items called enu-
merations which are usually two-state Boolean variables such as ON/OFF and TRUE/FALSE.
5.2 THE SYSTEM TEXT DICTIONARY
The System text dictionary holds all the text displayed by the instrument’s Standard Interface, except for the follow-
ing:
1 Error messages
2 Event messages
3 Segment type names, and text in menus and column headers.
Of these, Error messages and Event messages are held in their own dictionaries and can be customised through those.
Commands, segment type names, and text in menus and column heads are held elsewhere and cannot be customised.
In customising the System dictionary, it is possible to:

1 replace any text item with text for a particular industry or application, and/or
2 the text can be internationalised by creating new dictionaries for each of up to ten languages
5.2.1 File structure

In the listing of the System text dictionary in section 5.2.4, the column header running throughout is:
NO. CONTEXT CLASS MAX TEXT
No. Stands for REFERENCE NUMBER

CONTEXT Describes the application to which the text relates. For example, STARTUP, COMMS, or
CLOCK.
CLASS Describes the type of text. For example, title of a dialogue box, button text, or error message.
MAX The maximum permissible length of the replacement text, in number of characters.
TEXT The default text that the instrument is supplied with for this item.
Chapter 5 HA029280
5.2.2 Editing system text
The System text dictionary is held in the _system.uyl file. In the print-out of this file in section 5.2.4:
1. Find the text to be replaced (first find its Context, then its Class, then the Text itself)
2. Note its reference number
3. Key in the reference number, and then the new text, related by the following syntax: S<N>, <text>
where:
<N> is the reference number of the record you want to change
<text> is the replacement text.
For example, S12,Display error.
For any text item not replaced in the .uyl file, the version in the ROM file will be used.
5.2.3 New language versions
For each language a file called a _system<n>.uyl file must be built, using the same syntax as above. The variable <n>
in each file name specifies the particular national language by taking integer values from 0 up to a maximum of 9,
one value for each language which is to be available. The correspondence (mapping) between language and integer is
decided by the user.
For example, the file holding terms in English might be the file named _system0.uyl
with a typical record S2,FILE UPDATE.
5.2.4 The dictionary
On delivery of the Visual Supervisor, the contents of the System text dictionary (abridged) are as set out below.
Notes:
1. Items where ‘ : ’ is the final character always have a space after the ‘ : ’ for formatting purposes
2. Leading space characters are significant
3. Any printable character of the Unicode Latin-1 set may be used.
HA029280 Chapter 5
5.2.4 THE DICTIONARY (Cont.)
NO. CONTEXT CLASS MAX TEXT

1 GLOBAL BUTTON_TEXT 12 OK
2 OIFL DIALOG_TITLE 28 FILE UPDATE
3 OIFL DIALOG_TEXT 80 The User Page file has changed. The panel system
will now reload.
4 GLOBAL HIDE_CHAR 1
5 GLOBAL UPDATE_ERROR 1
6 GLOBAL DISP_ERROR 1
12 OIFL OIFL_ERROR 20 OIFL ERROR
13 OIFL OIFL_ERROR 20 BAD FILE
14 OIFL OIFL_ERROR 20 BAD LINE
15 OIFL OIFL_ERROR 20 BAD EOF
16 OIFL OIFL_ERROR 20 MEMORY
17 OIFL OIFL_ERROR 20 SYNTAX
18 OIFL OIFL_ERROR 20 RANGE
19 OIFL OIFL_ERROR 20 NAME
20 OIFL OIFL_ERROR 20 DICTIONARY
21 OIFL OIFL_ERROR 20 TYPE
22 OIFL OIFL_ERROR 20 ACTION
31 ALMMENU MENU_TITLE 16 Alarms
32 ALMMENU LEGEND 11 ALARMS
33 ALMMENU LEGEND 11 ACK
34 ALMMENU LEGEND 11 ACK ALL
35 ALMMENU LEGEND 11 HISTORY
36 ALMMENU LEGEND 11 SUMMARY
37 ALMMENU DIALOG_TEXT 80 This will acknowledge every alarm.
38 ALMMENU BUTTON_TEXT 12 OK
39 ALMMENU BUTTON_TEXT 12 CANCEL
40 ALMMENU LEGEND 11 ABORT
41 ALH PAGE_TITLE 20 Alarm History
42 ALH LEGEND 11 ALM HIST
43 ALH ALH_TITLE 8 TYPE
44 ALH ALH_TITLE 8 ACTIVE
45 ALH ALH_TITLE 8 CLEAR
46 ALH LEGEND 11 FILTER
47 ALH ALH_FILTER 8 = ALL
48 ALH ALH_FILTER 8 = ALARMS
49 ALH ALH_FILTER 8 = AREA
50 ALH ALH_FILTER 8 = GROUP
51 ALH ALH_FILTER 8 = BLOCK
52 ALH ALH_FILTER 8 = EVENTS
53 ALH ALH_FILTER 8 = SYSTEM
54 ALH DIALOG_TEXT 80 This will acknowledge every alarm under the selected
filter.
56 ALH ALH_TITLE 8 ACK
57 ALH PAGE_TITLE 20 Alarm summary
59 ALH ALH_FILTER 8 =MSGS
61 ALMMENU PAGE_TITLE 20 Add Note
62 ALMMENU LEGEND 11 NOTE
63 ALMMENU INTRO 64 Adds a Note to the Alarm History list.
64 ALMMENU ITEM_TITLE 16 Your note:
Chapter 5 HA029280
No. Context Class Max Text

66 ALMMENU LEGEND 11 LOG
67 ALH PAGE_TITLE 20 Event Log
68 ALMMENU LEGEND 11 EVT LOG
71 ALMMENU PAGE_TITLE 20 Alarm Archive
72 ALMMENU LEGEND 11 ARCHIVE
73 ALMMENU INTRO 64 Archive to disk the alarm history
74 ALMMENU DIALOGUE_TITLE 28 Acknowledging All Cached Block Alarms
75 ALMMENU ITEM_TITLE 16 Remaining:
76 ALMMENU ITEM_TITLE 16 Block:
77 PRINTER ALM_TYPE 3 ACK
78 PRINTER ALM_TYPE 3 ACT
79 PRINTER ALM_TYPE 3 CLR
90 APPMGR DIALOG_TITLE 28 Load Error
91 FATAL FATAL_ERROR 20 No cold/hot start
92 FATAL FATAL_ERROR 20 No hot start
93 FATAL FATAL_ERROR 20 No cold start
94 SYSTEM DIALOG_TITLE 28 Missing template libraries
101 MONTH MONTH 3 Jan
102 MONTH MONTH 3 Feb
103 MONTH MONTH 3 Mar
104 MONTH MONTH 3 Apr
105 MONTH MONTH 3 May
106 MONTH MONTH 3 Jun
107 MONTH MONTH 3 Jul
108 MONTH MONTH 3 Aug
109 MONTH MONTH 3 Sep
110 MONTH MONTH 3 Oct
111 MONTH MONTH 3 Nov
112 MONTH MONTH 3 Dec
113 ALH DATE POOR CHAR 1 *
114 ALH TIME POOR CHAR 1 *
120 GLOBAL BUTTON_TEXT 12 OK
121 GLOBAL BUTTON_TEXT 12 OK ALL
122 GLOBAL BUTTON_TEXT 12 CANCEL
123 GLOBAL BUTTON_TEXT 12 ABORT
124 GLOBAL BUTTON_TEXT 12 SKIP
125 GLOBAL BUTTON_TEXT 12 SAVE
126 GLOBAL BUTTON_TEXT 12 ERROR
127 GLOBAL SYSSUM_ITEM 8 <NONE>
128 GLOBAL BUTTON_TEXT 12 NO
129 GLOBAL BUTTON_TEXT 12 YES
130 SYSMENU MENU_TITLE 16 System
131 SYSMENU LEGEND 11 SYSTEM
132 SYSSUM PAGE_TITLE 20 System Summary
133 SYSSUM LEGEND 11 SUMMARY
134 SYSSUM ITEM_TITLE 18 Instrument type:
136 SYSSUM ITEM_TITLE 18 Touch/keypad:
137 SYSSUM ITEM_TITLE 18 Firmware:
HA029280 Chapter 5

138 SYSSUM ITEM_TITLE 18 Media:
139 SYSSUM ITEM_TITLE 18 Option cards:
140 SYSSUM SYSSUM_ITEM 8 Eycon-10, or Eycon-20 according to model
141 SYSSUM SYSSUM_ITEM 8 Standard
145 SYSSUM SYSSUM_ITEM 8 kBytes
146 SYSSUM ITEM_TITLE 18 DRAM:
147 SYSSUM ITEM_TITLE 18 SRAM:
150 SYSSUM SYSSUM_ITEM 8 TOUCH
151 SYSSUM SYSSUM_ITEM 8 KEYPAD
154 SYSSUM SYSSUM_ITEM 8 MBytes
157 SYSSUM ITEM_TITLE 8 Internal Archive:
158 SYSSUM SYSSUM_ITEM 8 IDE
159 SYSSUM ITEM_TITLE 18 USB(Bulk)
160 SYSSUM PARA 20 Software options
163 SYSSUM SYSSUM_ITEM 8 ETHERNET
166 SYSSUM SYSSUM_ITEM 8 Report
167 SYSSUM SYSSUM_ITEM 8 Recipe
168 SYSSUM ITEM_TITLE 18 Reader:
169 SYSSUM ITEM_TITLE 18 Batch:
170 APPSUM PAGE_TITLE 20 Appl’n Summary
171 APPSUM LEGEND 11 APP SUM
172 APPSUM ITEM_TITLE 16 Application:
173 APPSUM ITEM_TITLE 16 Machine State:
174 APPSUM PARA 24 Memory Usage
180 APPSUM APPSUM_STATE 10 OFF
181 APPSUM APPSUM_STATE 10 RESET
182 APPSUM APPSUM_STATE 10 IDLE
183 APPSUM APPSUM_STATE 10 RUNNING
184 APPSUM APPSUM_STATE 10 STOPPED
185 APPSUM APPSUM_STATE 10 ERROR
189 APPSUM ITWM_TITLE 16 Ctrl VolDB:
190 APPSUM ITEM_UNITS 9 kB
191 APPSUM ITEM_TITLE 16 Control DB:
192 APPSUM ITEM_TITLE 16 Programmer:
193 APPSUM ITEM_TITLE 16 SFC DB:
194 APPSUM ITEM_TITLE 16 SFC ST:
195 APPSUM ITEM_TITLE 16 Modbus slave:
196 APPSUM ITEM_TITLE 16 Modbus master:
197 APPSUM ITEM_TITLE 16 transient:
198 APPSUM ITEM_TITLE 16 Profibus Master:
200 STARTUP PAGE_TITLE 20 Startup Strategy
201 STARTUP LEGEND 11 STARTUP
202 STARTUP ITEM_TITLE 18 Hot Start:
203 STARTUP ITEM_TITLE 18 Warm Start:
204 STARTUP ITEM_TITLE 18 Cold Start:
205 STARTUP ITEM_TITLE 18 Startup State:
206 STARTUP ITEM_TITLE 18 Hot-start time:
207 STARTUP ITEM_TITLE 18 Brown-out time:
220 COMMS PAGE_TITLE 20 Comms Setup
221 COMMS LEGEND 18 COMMS
222 COMMS DIALOG_TEXT 80 The settings specified are invalid.
223 COMMS DIALOG_TITLE 28 Hardware check
224 COMMS DIALOG_TEXT 80 IMPORTANT: Ensure comms cables are unplugged
before pressing ‘OK’ to continue.
Chapter 5 HA029280

228 COMMS COMMS_ITEM 8 Ethernet
240 COMMS COMMS_ATTR 9 PORT
241 COMMS COMMS_ATTR 9 Hardware
242 COMMS COMMS_ATTR 9 Protocol
243 COMMS COMMS_ATTR 9 Node No.
244 COMMS COMMS_ATTR 9 Baud
245 COMMS COMMS_ATTR 9 Parity
246 COMMS COMMS_ATTR 9 Data Bits
247 COMMS COMMS_ATTR 9 Stop Bits
248 COMMS COMMS_ATTR 9 Timeout
249 COMMS COMMS_ATTR 9 Talk Thru
251 COMMS COMMS_ITEM 8 None
253 COMMS COMMS_ITEM 8 TermCfg
254 COMMS COMMS_ITEM 8 Modbus/S
255 COMMS COMMS_ITEM 8 Modbus/M
261 COMMS COMMS_ITEM 8 NONE
262 COMMS COMMS_ITEM 8 EVEN
263 COMMS COMMS_ITEM 8 ODD
266 COMMS COMMS_ITEM 8 RS422
267 COMMS COMMS_ITEM 8 RS485
270 CLOCK PAGE_TITLE 20 Clock Setup
271 CLOCK LEGEND 11 CLOCK
272 CLOCK ITEM_TITLE 16 Date:
273 CLOCK ITEM_TITLE 16 Time:
274 CLOCK BUTTON_TEXT 12 SET
275 CLOCK BUTTON_TEXT 12 Hr +1
276 CLOCK BUTTON_TEXT 12 Hr -1
277 CLOCK INTRO 64 Clock configured as master
278 CLOCK INTRO 64 Clock configured as slave
280 SYSSUM ITEM_TITLE 18 SPP/SFC
281 SYSSUM ITEM 8 SPP
282 SYSSUM ITEM 8 SFC
283 SYSSUM ITEM 8 DB
288 SYSSUM ITEM_TITLE 21 IPR Protection:
289 SYSSUM SYSSUM_ITEM 8 Auditor:
290 INTERNAT PAGE_TITLE 20 Internationalise
291 INTERNAT LEGEND 11 INTERNAT
292 INTERNAT ITEM_TITLE 14 Language:
293 INTERNAT ITEM_TITLE 14 Date Format:
294 INTERNAT ITEM_TITLE 14 Time Format:
295 INTERNAT ITEM_TITLE 14 Duration Fmt:
296 INTERNAT BUTTON_TEXT 12 CHANGE
300 INTERNAT LANGUAGE 12 English
301 INTERNAT LANGUAGE 12 French
302 INTERNAT LANGUAGE 12 German
303 INTERNAT LANGUAGE 12 Italian
304 INTERNAT LANGUAGE 12 Spanish
305 INTERNAT LANGUAGE 12 Lang_5
309 INTERNAT LANGUAGE 16 Portuguese
HA029280 Chapter 5

310 PANEL PAGE_TITLE 20 Panel Setup
311 PANEL LEGEND 11 PANEL
312 PANEL PARA 24 BACK-LIGHT
313 PANEL ITEM_TITLE 32 Brightness:
314 PANEL ITEM_TITLE 32 Saver brightness:
315 PANEL ITEM_TITLE 32 Timeout:
316 PANEL PARA 24 PAGE TIMEOUTS
317 PANEL ITEM_TITLE 32 Home:
318 PANEL ITEM_TITLE 32 Pop-up:
319 PANEL ITEM_TITLE 32 Data Entry:
320 PANEL ITEM_UNITS 9 minutes
321 PANEL ITEM_UNITS 9 seconds
322 PANEL ITEM 16 100%
331 PANEL ITEM_TITLE 20 This item allows an access level timeout to be entered
(Section 4.5.5.3). If a non-zero value is entered, then
the Access level will return to ‘Locked’ whenever the
time between screen presses is greater than the
timeout period.
332 PANEL ITEM_TITLE 16 SIZES
333 PANEL ITEM 16 Standard
334 PANEL ITEM 26 Small
339 PANEL ITEM_UNITS 9 days
340 FILEMGR BUTTON_TEXT 12 COPY ALL
341 FILEMGR PAGE_TITLE 20 Copy Files
342 FILEMGR BUTTON_TEXT 16 DEL ALL
343 FILEMGR PAGE_TITLE 20 Confirm Delete All
344 FILEMGR ITEM_FILE 16 Files:
360 ACCESS PAGE_TITLE 20 Security Access
361 ACCESS LEGEND 11 ACCESS
362 ACCESS INTRO 64 Enter required level and password, then CHANGE
363 ACCESS ITEM_TITLE 18 Current Level:
364 ACCESS ITEM_TITLE 18 New Level:
365 ACCESS ITEM_TITLE 18 Password:
366 ACCESS BUTTON_TEXT 12 CHANGE
367 ACCESS BUTTON_TEXT 12 PASSWDS
368 ACCESS PAGE_TITLE 20 Passwords
369 ACCESS PAGE_TITLE 28 Confirm Password
370 ACCESS INTRO 64 Please re-enter top-level password:
371 ACCESS ACCESS_LEVEL 10 LOCKED
372 ACCESS ACCESS_LEVEL 10 OPERATOR
373 ACCESS ACCESS_LEVEL 10 COMMISSION
374 ACCESS ACCESS_LEVEL 10 ENGINEER
375 ACCESS ACCESS_LEVEL 10 ADMIN
Chapter 5 HA029280

380 APPMGR PAGE_TITLE 20 Appl’n Manager
381 APPMGR LEGEND 11 APP MGR
382 APPMGR ITEM_TITLE 16 File:
383 APPMGR ITEM_TITLE 16 State:
384 APPMGR BUTTON_TEXT 12 LOAD
385 APPMGR BUTTON_TEXT 12 LD+RUN
386 APPMGR BUTTON_TEXT 12 UNLOAD
387 APPMGR BUTTON_TEXT 12 SAVE
388 APPMGR BUTTON_TEXT 12 SAVE AS
389 APPMGR BUTTON_TEXT 12 DELETE
390 APPMGR BUTTON_TEXT 12 STOP
391 APPMGR BUTTON_TEXT 12 START
392 APPMGR DIALOG_TITLE 28 Confirm Delete
393 APPMGR MESSAGE 128 Application management is already in progress else-
where
394 APPMGR DIALOG_TITLE 28 Saving
396 APPMENU MENU_TITLE 16 Application
397 APPMENU LEGEND 11 APPLN
398 SETMENU MENU_TITLE 16 Setup
399 SETMENU LEGEND 11 SETUP
400 SPP SPP_STATUS 8 RESET
401 SPP SPP_STATUS 8 LOADING
402 SPP SPP_STATUS 8 PRE_RUN
403 SPP SPP_STATUS 8 RUNNING
404 SPP SPP_STATUS 8 HELD
405 SPP SPP_STATUS 8 HELDBACK
406 SPP SPP_STATUS 8 COMPLETE
407 SPP SPP_STATUS 8 IDLE
408 SPP SPP_STATUS 8 POST_RUN
409 SPP SPP_STATUS 8 ERROR
410 SPP SPP_FP_VALUE 8 CLOSED
411 SPP SPP_FP_VALUE 8 OPEN
412 SPP ITEM_TITLE 16 Segment:
413 SPP ITEM_TITLE 16 Setpoint:
414 SPP ITEM_TITLE 16 Ramp at:
415 SPP ITEM_TITLE 16 to:
416 SPP BUTTON_TEXT 12 DONE
417 SPP PAGE_TITLE 18 Current Program
418 SPP PARA 20 Program
419 SPP ITEM_TITLE 16 Name:
420 SPP ITEM_TITLE 16 Status:
421 SPP ITEM_TITLE 16 Duration:
422 SPP ITEM_TITLE 16 Completion:
423 SPP ITEM_TITLE 16 Iteration:
424 SPP Special 1 /
425 SPP PARA 24 Segment
427 SPP ITEM_TITLE 16 Time Remaining:
428 SPP BUTTON_TEXT 12 RUN
429 SPP BUTTON_TEXT 12 HOLD
430 SPP BUTTON_TEXT 12 ABORT
HA029280 Chapter 5

431 SPP PAGE_TITLE 20 Load/Save Program
432 SPP ITEM_TITLE 16 File Name:
433 SPP BUTTON_TEXT 12 LOAD
434 SPP BUTTON_TEXT 12 SAVE
435 SPP BUTTON_TEXT 12 SAVE AS
436 SPP BUTTON_TEXT 12 DELETE
437 SPP PAGE_TITLE 20 Schedule Program
439 SPP ITEM_TITLE 17 Start Date:
440 SPP ITEM_TITLE 17 Start Time:
441 SPP ITEM_TITLE 16 Iterations:
442 SPP BUTTON_TEXT 12 CLEAR
443 SPP BUTTON_TEXT 12 ACCEPT
444 SPP SPP_CELL 18 SP
445 SPP SPP_CELL_ABBR 8 D
446 SPP SPP_CELL_ABBR 8 S
447 SPP Special 2 to
448 SPP SPP_CELL_ABBR 8 R
449 SPP Special 2 R@
450 SPP SPP_CELL_ABBR 8 Servo SP
451 SPP SPP_CELL_ABBR 8 Servo PV
452 SPP PAGE_TITLE 20 Save As...
455 SPP DIALOG_TEXT 80 Overwriting
456 SPP DIALOG_TITLE 28 PROGRAM SAVE
457 SPP BUTTON_TEXT 12 OK
458 SPP BUTTON_TEXT 12 CANCEL
459 SPP DIALOG_TEXT 80 Deleting
460 SPP DIALOG_TITLE 28 PROGRAM DELETE
463 SPP DIALOG_TEXT 80 File Saved
464 SPP DIALOG_TITLE 28 PROGRAM SAVE
466 SPP DIALOG_TEXT 80 Program File not found
467 SPP DIALOG_TEXT 80 Program File too large
468 SPP DIALOG_TEXT 80 File read error
469 SPP DIALOG_TEXT 80 File write error
470 SPP DIALOG_TEXT 80 Unresolved block references
471 SPP DIALOG_TEXT 80 Program Already Running
472 SPP DIALOG_TEXT 80 Insufficient file space
473 SPP DIALOG_TEXT 80 Unrecognised file format
474 SPP DIALOG_TEXT 80 Schedule already loaded
475 SPP DIALOG_TEXT 80 Max nested subprograms limit exceeded
476 SPP DIALOG_TITLE 28 PROGRAM LOAD/SAVE ERROR
478 SPP MENU_TITLE 11 Programmer
479 SPP LEGEND 11 MONITOR
480 SPP LEGEND 11 PROGRAMS
481 SPP LEGEND 11 SCHEDULE
482 SPP LEGEND 11 PREVIEW
483 SPP LEGEND 11 PRE-PLOT
Chapter 5 HA029280

484 SPP LEGEND 11 EDIT
485 SPP LEGEND 11 PROGRAMMER
486 SPP SPP_FP_VALUE 8 NODATA
487 SPP ITEM_TITLE 16 Run From:
490 SPP LEGEND 11 RUN FROM
491 SPP BUTTON_TEXT 12 RUN
493 SPP ITEM_TITLE 16 Time Through:
494 SPP DIALOG_TEXT 80 A program is scheduled. Continue with LOAD?
495 SPP DIALOG_TITLE 28 LOAD PROGRAM
496 SPP PARA 24 Current Schedule:
497 SPP DIALOG_TITLE 28 UNSAVED EDITS
498 SPP DIALOG_TEXT 80 This operation will result in the loss of edits which
have not yet been saved.
499 SPP DIALOG_TITLE 28 RAMP TYPE CHANGE
500 SPP DIALOG_TEXT 80 This will require other ramp types in this segment to
be changed.
501 SPP BUTTON_TEXT 12 NEW
502 SPP PAGE_TITLE 20 New Program
503 SPP PAGE_TITLE 20 Load Program
504 SPP PAGE_TITLE 20 Properties
505 SPP SPP_HOLDBACK 8 Holdback
506 SPP ITEM_TITLE 16 Mode:
507 SPP ITEM_TITLE 16 Value:
508 SPP SPP_HOLDBACK 8 NONE
509 SPP SPP_HOLDBACK 8 LOW
510 SPP SPP_HOLDBACK 8 HIGH
511 SPP SPP_HOLDBACK 8 HIGH&LOW
513 SPP BUTTON_TEXT 12 INS SEG
514 SPP BUTTON_TEXT 12 DEL SEG
515 SPP PAGE_TITLE 20 New Segment
516 SPP PAGE_TITLE 20 Confirm Delete
517 SPP ITEM 16 (Continuous)
518 SPP MESSAGE 128 Building Display, please wait
519 SPP ITEM_TITLE 16 Type:
520 SPP SPP_CELL 8 Dwell
521 SPP SPP_CELL 18 Step
522 SPP SPP_CELL 18 Ramp
523 SPP SPP_CELL 18 Ramp@
524 SPP SPP_CELL 18 Expressn
525 SPP SPP_CELL 18 Servo SP
526 SPP SPP_CELL 18 Servo PV
528 SPP SPP_CELL 18 Dwell
529 SPP SPP_CELL 18 Step
532 SPP SPP_CELL 18 Expressn
536 SPP ITEM_TITLE 20 At End:
537 SPP SPP_AT_END 24 Indefinite Dwell
538 SPP SPP_AT_END 24 Starting Values
539 SPP ITEM_TITLE 16 Ref:
540 SPP DIALOG_TEXT 80 Program Limits Exceeded
HA029280 Chapter 5

550 SPP ITEM_TITLE 20 Rate Units:
551 SPP SPP_RATE_UNITS 16 Seconds
552 SPP SPP_RATE_UNITS 16 Minutes
553 SPP SPP_RATE_UNITS 16 Hours
554 SPP SPP_RATE_UNITS 16 days
555 SPP DIALOG_TEXT 80 No program loaded
561 SPP ITEM_TITLE 16 Id:
562 SPP DIALOG_TEXT 80 Common Block Refs
563 SPP ITEM_TITLE 16 Iterations:
570 SPP BUTTON_TEXT 12 SKIP
571 SPP BUTTON_TEXT 12 LAYOUT
572 SPP PAGE_TITLE 20 Editor layout
573 SPP ITEM_TITLE 16 Long SP names:
574 SPP ITEM_TITLE 16 Segment start:
575 SPP ITEM_TITLE 16 Segment duration:
576 SPP ITEM_TITLE 16 Segment finish:
577 SPP ITEM_TITLE 16 Start Time:
578 SPP ITEM_TITLE 16 Finish Time:
590 Audit ITEM 16 DYNAMIC
591 Audit ITEM 16 BURST
592 Audit ITEM 16 INITIAL
598 SIGN BUTTON_TEXT 12 OK
599 SIGN BUTTON_TEXT 12 CANCEL
600 SIGN PAGE_TITLE 20 Signature
601 SIGN PAGE_TITLE 20 Confirmation
602 SIGN PARA 24 Authorised by
603 SIGN ITEM_TITLE 16 Reason:
604 SIGN PARA 24 Signed by
605 SIGN ITEM_TITLE 16 Old Value:
606 SIGN ITEM_TITLE 16 New Value:
607 SIGN ITEM_TITLE 16 Confirm Action:
608 SIGN PAGE_TITLE 20 Signature Rejected
609 SIGN ITEM_TITLE 16 Action Result:
700 LOGGING MENU_TITLE 16 Logging
701 LOGGING LEGEND 11 LOGGING
702 LOGGING LEGEND 11 MONITOR
704 LOGGING LEGEND 11 MANAGE
705 LOGGING LEGEND 11 GROUPS
706 LOGGING PAGE_TITLE 20 Logging Monitor
707 LOGGING PAGE_TITLE 20 Logging Groups
709 LOGGING PAGE_TITLE 20 Archive Manage
711 LOGGING ITEM_TITLE 17 File Name:
712 LOGGING ITEM_TITLE 17 File Type:
715 LOGGING BUTTON_TEXT 12 MONITOR
717 LOGGING BUTTON_TEXT 12 MANAGE
718 LOGGING BUTTON_TEXT 12 GROUPS
720 LOGGRP MESSAGE 128 No logging groups configured
721 LOGGRP ITEM_TITLE 17 Group Name:
722 LOGGRP ITEM_TITLE 17 Logging:
723 LOGGRP ITEM_TITLE 17 Archive Int:
Chapter 5 HA029280

725 LOGGRP ITEM_TITLE 17 Name Type:
726 LOGGRP PARA 24 Configuration
727 LOGGRP ITEM_TITLE 17 Column Titles:
728 LOGGRP ITEM_TITLE 17 Date Format:
731 LOGGRP BUTTON_TEXT 12 SAVE
732 LOGGRP BUTTON_TEXT 12 LOG NOW
741 LOGGING ITEM 13 ASCII
743 LOGGING ITEM 13 UHH
745 LOGGRP ITEM 13 Normal
746 LOGGRP ITEM 13 High
751 LOGGRP ITEM 13 ON
752 LOGGRP ITEM 13 OFF
753 LOGGRP ITEM 13 TRIGGER
755 LOGGRP ITEM 13 Text
758 LOGGRP ITEM 13 Sequence
756 LOGGRP ITEM 13 Hourly
757 LOGGRP ITEM 13 Daily
761 LOGGRP ITEM 13 Date Time
762 LOGGRP ITEM 13 Spreadsheet
763 LOGGRP ITEM 13 Integer
764 LOGGRP ITEM 13 Duration
765 LOGGRP ITEM 13 Days
766 LOGGRP ITEM 13 DHMS
767 LOGGRP ITEM 13 Present
768 LOGGRP ITEM 13 Absent
770 LOGAMAN ITEM 16 Files Exported:
771 LOGAMAN ITEM 16 Files Skipped:
772 LOGAMAN ITEM 16 Page Locked:
773 LOGAMAN DIALOGUE_TITLE 28 Archive Manager Export
774 LOGAMAN DIALOG_TEXT 80 Complete. Device may now be removed.
775 LOGAMAN DIALOG_TEXT 90 Do you wish to skip ALL duplicate files, i.e. never
overwrite files on the export device?
776 LOGAMAN DIALOG_TEXT 80 Export device is full. Replace device and press OK to
continue.
777 LOGAMAN BUTTON_TEXT 12 EXPORT ALL
778 LOGAMAN ITEM 16 Export device:
779 LOGGING ITEM_UNITS 9 Bytes
780 LOGGING ITEM_UNITS 9 KBytes
781 LOGMON ITEM_TITLE 16 Media Size:
782 LOGMON ITEM_TITLE 16 Free Space:
783 LOGMON ITEM_TITLE 16 Logging:
784 LOGMON ITEM_TITLE 16 Free Time:
785 LOGMON ITEM 8 ON
786 LOGMON ITEM 8 OFF
787 LOGMON ITEM 8 On Event
789 LOGAMAN ITEM 16 Files
796 LOGAMAN BUTTON_TEXT 12 EXPORT
797 LOGAMAN MESSAGE 128 Please wait…
798 LOGAMAN ITEM_TITLE 16 File Size:
799 LOGAMAN BUTTON_TEXT 12 DELETE
HA029280 Chapter 5

800 CLONE PAGE_TITLE 20 Cloning
801 CLONE LEGEND 11 CLONING
802 CLONE ITEM 16 System
803 CLONE ITEM 16 Application
804 CLONE ITEM 16 ALL
805 CLONE BUTTON_TEXT 12 EXPORT
806 CLONE BUTTON_TEXT 12 IMPORT
807 CLONE INTRO 64 System Data
808 CLONE ITEM_TITLE 22 Config Options:
809 CLONE ITEM_TITLE 22 Config Resources:
810 CLONE ITEM_TITLE 22 Dictionaries:
811 CLONE ITEM_TITLE 18 User Pages:
812 CLONE INTRO 64 Application Data
813 CLONE ITEM_TITLE 22 Control Database:
814 CLONE ITEM_TITLE 22 SFCs:
815 CLONE ITEM_TITLE 22 Programs/Recipes:
816 CLONE ITEM_TITLE 22 User Pages:
817 CLONE ITEM_TITLE 22 Comms Profiles:
818 CLONE BUTTON_TEXT 12 CLEAR
819 CLONE BUTTON_TEXT 12 DELETE
820 CLONE ITEM_TITLE 22 Exporting:
821 CLONE ITEM_TITLE 22 Importing:
822 CLONE MESSAGE 128 Aborting...
823 CLONE DIALOG_TEXT 80 Storage device not present. Insert, then select OK to
continue.
824 CLONE DIALOG_TEXT 80 This file already exists. Do you wish to overwrite it?
825 CLONE DIALOG_TEXT 80 Destination device is full!
826 CLONE DIALOG_TEXT 80 Error encountered when copying file
827 CLONE DIALOG_TEXT 80 Destination file exists but source file does not. Re-
move it?
828 CLONE DIALOG_TEXT 80 No .RUN file found
829 CLONE DIALOG_TEXT 80 Multiple .RUN files found
839 CLONE DIALOG_TEXT 80 Storage device corrupted. Replace then select OK to
continue.
840 AGP PAGE_TITLE 20 Overview
841 AGP LEGEND 11 OVERVIEW
842 AGP BUTTON_TEXT 12 AUTO
843 AGP BUTTON_TEXT 12 MANUAL
845 AGP BUTTON_TEXT 8 VIEW
846 AGP BUTTON_TEXT 8 LIVE
930 MAINTMEN MENU_TITLE 16 Maintenance
931 MAINTMEN LEGEND 11 MAINT
932 FILEMGR PAGE_TITLE 20 File Manager
933 FILEMGR LEGEND 11 FILE MGR
934 FILEMGR ITEM_TITLE 16 Device:
935 FILEMGR ITEM_TITLE 16 Filter:
936 FILEMGR ITEM_TITLE 16 File:
937 FILEMGR ITEM_TITLE 16 Size:
938 FILEMGR ITEM_TITLE 16 Free Space:
939 FILEMGR ITEM_UNITS 9 Bytes
Chapter 5 HA029280

940 FILEMGR BUTTON_TEXT 12 COPY
941 FILEMGR BUTTON_TEXT 12 DELETE
942 FILEMGR PAGE_TITLE 20 Copy File
943 FILEMGR PARA 24 Copy To
944 FILEMGR PAGE_TITLE 20 Confirm Delete
945 FILEMGR ITEM_TITLE 16 Segment:
946 FILEMGR ITEM_TITLE 16 Node:
947 FILEMGR ITEM-UNITS 9 (Local)
948 FILEMGR MESSAGE 128 Remote file access. Please wait...
951 AGP ITEM_TITLE 12 Missing
952 AGP ITEM_TITLE 12 Wrong
953 AGP ITEM_TITLE 12 Unknown
954 AGP ITEM_TITLE 12 Comm Err
961 AGP ITEM_TITLE 12 Sensor Break
962 AGP ITEM_TITLE 12 CJC Fail
963 AGP ITEM_TITLE 12 Not Used
964 AGP ITEM_TITLE 12 OP Sat
965 AGP ITEM_TITLE 12 Init
966 AGP ITEM_TITLE 12 Inv Cal
968 AGP ITEM_TITLE 12 Mod Fail
970 AGP ITEM_TITLE 3 AI2
971 AGP ITEM_TITLE 3 DI4
972 AGP ITEM_TITLE 3 DO4
973 AGP ITEM_TITLE 3 AO2
977 AGP ITEM_TITLE 3 AO4
978 AGP ITEM_TITLE 3 DO8
990 AGP ITEM_TITLE 16 XP
991 AGP ITEM_TITLE 16 TI
992 AGP ITEM_TITLE 16 TD
993 AGP ITEM_TITLE 16 RCG
994 AGP ITEM_TITLE 16 CBH
995 AGP ITEM_TITLE 16 CBL
996 AGP ITEM_TITLE 16 MR
997 AGP ITEM_TITLE 16 Act
1000 AGP PAGE_TITLE 20 FB Manager
1001 AGP LEGEND 11 FB MGR
1002 FB_MGR ITEM_TITLE 16 Block name:
1003 FB_MGR ITEM_TITLE 16 Block type:
1004 FB_MGR ITEM_TITLE 16 Cached from:
1005 FB_MGR ITEM_TITLE 4 ms
1006 FB_MGR ITEM_TITLE 16 Update rate:
1009 FB_MGR ITEM 16 No connections
1010 ACCESS INTRO 64 User ID and password, then LOG ON
1011 ACCESS ITEM_TITLE 18 Ident:
HA029280 Chapter 5

1012 ACCESS ITEM_TITLE 18 Name:
1013 ACCESS BUTTON_TEXT 12 LOG ON
1014 ACCESS ITEM_TITLE 18 Access:
1015 ACCESS PAGE_TITLE 20 User Password
1016 ACCESS INTRO 64 please re-enter User password:
1017 ACCESS BUTTON_TEXT 12 PASSWD
1018 ACCESS BUTTON_TEXT 12 USERS
1020 ACCESS BUTTON_TEXT 12 LOG OFF
1021 ACCESS INTRO 64 To change to Multi-User mode, select OK. See docu-
mentation for password information
1023 ACCESS PAGE_TITLE 20 Multi-User select
1024 ACCESS DIALOG_TEXT 80 Changing to multi_user mode will be irreversible!
Select OK to continue
1025 ACCESS DIALOGUE_TITLE 28 Confirm Multi-User mode
1026 ACCESS COL_TITLE 10 Identity
1027 ACCESS COL_TITLE 10 Reference
1028 ACCESS COL_TITLE 10 Name
1029 ACCESS COL_TITLE 10 Access
1030 ACCESS ITEM_TITLE 18 Identity:
1031 ACCESS ITEM_TITLE 18 Password:
1032 ACCESS ITEM_TITLE 18 Confirm:
1033 ACCESS BUTTON_TEXT 12 NEW
1034 ACCESS BUTTON_TEXT 12 DELETE
1035 ACCESS DIALOGUE_TITLE 28 Delete User
1036 ACCESS DIALOGUE_TITLE 28 New User
1037 ACCESS MESSAGE 128 Sorting entries, please wait
1038 ACCESS BUTTON_TEXT 12 DISABLE
1039 ACCESS MESSAGE 128 Your password has expired. You must change it now.
1060 CLONE ITEM_TITLE 22 Forms:
1063 CLONE ITEM_TITLE 16 Security Access:
1064 CLONE ITEM_TITLE 16 Net Audit setup:
1065 CLONE ITEM_TITLE 16 Signature setup:
1066 CLONE ITEM_TITLE 16 Include Source Files:
1067 CLONE ITEM_TITLE 22 Category:
1068 CLONE DIALOG_TITLE 28 WARNING
1069 CLONE DIALOG_TEXT 80 No files have been transferred.
1071 FB_MGR BUTTON TEXT 12 CREATE
1072 FB_MGR BUTTON_TEXT 12 DELETE
1073 FB_MGR BUTTON TEXT 12 SAVE
1074 FB_MGR ITEM 16 (Unused)
1080 FB_MGR DIALOGUE TITLE 28 Block Create
1081 FB_MGR ITEM_TITLE 16 Category:
1082 FB_MGR ITEM_TITLE 16 Block Type:
1083 FB_MGR DIALOG_TITLE 28 Confirm Block Delete
1084 FB_MGR BUTTON_TEXT 12 NETWORK
1085 FB_MGR PAGE_TITLE 20 Network Set Up
1086 FB_MGR LEGEND 11 ADD EDB
1087 FB_MGR PAGE _TITLE 20 Add External Database
1088 FB_MGR ITEM 16 Page:
1089 FB_MGR ITEM 16 <local>
1090 MSG PAGE_TITLE 20 Messages
1091 MSG LEGEND 11 MSG LIST
Chapter 5 HA029280

1092 ALMMENU LEGEND 11 MESSAGES
1093 MSG MESSAGE 16 <None>
1100 RECIPE LEGEND 11 RECIPE
1101 RECIPE MENU_TITLE 16 Recipe
1102 RECIPE BUTTON_TEXT 12 DOWNLOAD
1103 RECIPE BUTTON_TEXT 12 ABORT
1104 RECIPE BUTTON_TEXT 12 LOAD
1105 RECIPE BUTTON_TEXT 12 SAVE
1106 RECIPE BUTTON_TEXT 12 SAVE AS
1107 RECIPE BUTTON_TEXT 12 CAPTURE
1108 RECIPE BUTTON_TEXT 12 CAPTURE AS
1109 RECIPE BUTTON_TEXT 12 NEW
1110 RECIPE BUTTON_TEXT 12 DELETE
1111 RECIPE BUTTON_TEXT 12 ADD LINE
1112 RECIPE BUTTON_TEXT 12 DELETE
1113 RECIPE BUTTON_TEXT 12 INSERT
1114 RECIPE BUTTON_TEXT 12 CREATE
1115 RECIPE BUTTON_TEXT 12 LINES
1120 RECIPE LEGEND 11 RECIPES
1121 RECIPE PAGE_TITLE 20 Load/Save Recipe
1122 RECIPE LEGEND 11 STATUS
1123 RECIPE PAGE_TITLE 20 Recipe Status
1124 RECIPE ITEM_TITLE 16 Downloaded at:
1125 RECIPE ITEM_TITLE 16 Version:
1126 RECIPE ITEM_TITLE 16 Edited by:
1127 RECIPE ITEM_TITLE 16 At:
1128 RECIPE ITEM_TITLE 16 Timeout:
1130 RECIPE ITEM_TITLE 16 Status:
1131 RECIPE ITEM 12 RESET
1132 RECIPE ITEM 12 DOWNLOADING
1133 RECIPE ITEM 12 COMPLETE
1134 RECIPE ITEM 12 FAILURE
1140 RECIPE DIALOG_TITLE 28 RECIPE ERROR
1141 RECIPE MESSAGE 128 Recipe File not found
1142 RECIPE MESSAGE 128 Recipe File limits exceeded
1143 RECIPE MESSAGE 128 Invalid block reference(s)
1144 RECIPE MESSAGE 128 Recipe download in progress
1145 RECIPE MESSAGE 128 Unrecognised file format
1146 RECIPE MESSAGE 128 File write error
1150 RECIPE LEGEND 11 MONITOR
1151 RECIPE PAGE_TITLE 20 Recipe Monitor
1152 RECIPE PAGE_TITLE 20 SP
1153 RECIPE PAGE_TITLE 20 SP(Live)
1154 RECIPE PAGE_TITLE 20 PV
1155 RECIPE PAGE_TITLE 20 Capture
1160 RECIPE PAGE_TITLE 20 RCP
1161 RECIPE ITEM_TITLE 16 Id:
1162 RECIPE ITEM_TITLE 16 File Name:
1163 RECIPE ITEM_TITLE 16 Line:
1164 RECIPE ITEM_TITLE 16 Recipe Name:
1165 RECIPE ITEM_TITLE 16 Variable Name:
1168 RECIPE ITEM 8 FALSE
HA029280 Chapter 5

1169 RECIPE ITEM 8 TRUE
1170 RECIPE LEGEND 11 EDIT
1171 RECIPE PAGE_TITLE 20 Recipe Editor
1172 RECIPE ITEM_TITLE 16 Verify:
1173 RECIPE PARA 24 Tag References
1174 RECIPE ITEM_TITLE 16 SP:
1175 RECIPE ITEM_TITLE 16 Monitor:
1176 RECIPE ITEM_TITLE 16 Capture:
1180 RECIPE DIALOG_TITLE 28 New Recipe
1181 RECIPE DIALOG_TITLE 28 Capture New Recipe
1182 RECIPE DIALOG_TITLE 28 Delete Recipe
1183 RECIPE DIALOG_TEXT 80 Deleting
1184 RECIPE DIALOG_TITLE 28 SAVE
1185 RECIPE DIALOG_TITLE 28 SAVE AS...
1186 RECIPE ITEM_TITLE 16 File Name:
1187 RECIPE DIALOG_TITLE 28 Load Recipe File
1188 RECIPE DIALOG_TEXT 80 Recipe already loaded.
1189 RECIPE DIALOG_TITLE 28 UNSAVED EDITS
1190 RECIPE DIALOG_TEXT 80 This operation will result in the loss of recipe edits
which have not yet been saved.
1191 RECIPE DIALOG_TEXT 80 Overwriting
1192 RECIPE DIALOG_TITLE 28 Delete Variable
1193 RECIPE DIALOG_TITLE 28 Properties
1194 RECIPE DIALOG_TITLE 28 Insert Variable
1195 RECIPE DIALOG_TITLE 28 RECIPE FILE DELETE
1196 RECIPE DIALOG_TITLE 28 CREATE AS...
1197 RECIPE DIALOG_TITLE 28 SELECT LINE
1198 RECIPE DIALOG_TITLE 28 Capture Recipe
1199 RECIPE DIALOG_TEXT 80 Capturing
1200 BATCH LEGEND 11 BATCH
1201 BATCH MENU_TITLE 16 Batch
1202 BATCH BATCH_STATE 12 RESET
1203 BATCH BATCH_STATE 12 IDLE
1204 BATCH BATCH_STATE 12 STARTING
1205 BATCH BATCH_STATE 12 RUNNING
1206 BATCH BATCH_STATE 12 COMPLETE
1207 BATCH BATCH_STATE 12 HOLDING
1208 BATCH BATCH_STATE 12 HELD
1209 BATCH BATCH_STATE 12 RESTARTING
1210 BATCH BATCH_STATE 12 PAUSING
1211 BATCH BATCH_STATE 12 PAUSED
1212 BATCH BATCH_STATE 12 RESUMING
1213 BATCH BATCH_STATE 12 STOPPING
1214 BATCH BATCH_STATE 12 STOPPED
1215 BATCH BATCH_STATE 12 ABORTING
1216 BATCH BATCH_STATE 12 ABORTED
1217 BATCH BATCH_STATE 12 FAILED
1220 BATCH LEGEND 11 BATCHES
1221 BATCH PAGE_TITLE 20 Load Batch
1222 BATCH ITEM_TITLE 16 File Name:
1223 BATCH ITEM_TITLE 16 Recipe Name:
1224 BATCH ITEM_TITLE 16 Id:
1225 BATCH ITEM_TITLE 16 State:
Chapter 5 HA029280

1226 BATCH ITEM_TITLE 16 Started At:
1227 BATCH ITEM_TITLE 16 Phase:
1228 BATCH ITEM_TITLE 16 Batch Id:
1229 BATCH ITEM_TITLE 16 Ended At:
1230 BATCH BUTTON_TEXT 12 LOAD
1231 BATCH BUTTON_TEXT 12 START
1232 BATCH BUTTON_TEXT 12 HOLD
1233 BATCH BUTTON_TEXT 12 RESTART
1234 BATCH BUTTON_TEXT 12 ABORT
1235 BATCH BUTTON_TEXT 12 RESET
1236 BATCH BUTTON_TEXT 12 NOTE
1237 BATCH BUTTON_TEXT 12 SAVE AS
1238 BATCH BUTTON_TEXT 12 CREATE
1240 BATCH LEGEND 11 STATUS
1241 BATCH PAGE_TITLE 20 Batch Status
1245 BATCH PAGE_TITLE 20 Batch Start
1250 BATCH DIALOG_TITLE 28 BATCH ERROR
1251 BATCH MESSAGE 128 Batch File not found
1252 BATCH MESSAGE 128 Batch File limits exceeded
1253 BATCH MESSAGE 128 Invalid block reference(s)
1254 BATCH MESSAGE 128 Incorrect batch state
1255 BATCH MESSAGE 128 Unrecognised file format
1256 BATCH MESSAGE 128 File write error
1257 BATCH MESSAGE 128 Bad block
1258 BATCH MESSAGE 128 Invalid dictionary reference
1259 BATCH MESSAGE 128 Incorrect password
1260 BATCH MESSAGE 128 Shared block reference(s)
1270 BATCH DIALOG_TITLE 28 Batch Start Confirm
1271 BATCH DIALOG_TEXT 80 Please confirm starting of batch.
1272 BATCH DIALOG_TEXT 80 Please confirm your password to start batch.
1273 BATCH ITEM_TITLE 16 Password:
1280 BATCH DIALOG_TITLE 28 BATCH NOTE
1281 BATCH DIALOG_TEXT 80 Add a batch note.
1282 BATCH ITEM_TITLE 16 Note:
1285 BATCH DIALOG_TITLE 28 SAVE AS ..
1286 BATCH DIALOG_TEXT 80 Save batch file
1287 BATCH ITEM_TITLE 16 Filename:
1288 BATCH DIALOG_TITLE 28 SAVE
1289 BATCH DIALOG_TEXT 80 Overwriting
1290 BATCH DIALOG_TITLE 28 CREATE AS ..
1292 BATCH ITEM_TITLE 16 Recipe Line:
1293 BATCH ITEM_TITLE 16 Display Group:
1294 BATCH ITEM_TITLE 16 Message:
1295 BATCH ITEM_TITLE 16 Log Group:
1296 BATCH ITEM_TITLE 16 Log Report:
1300 ACCESS BUTTON TEXT 12 PROPERTIES
1301 ACCESS PAGE TITLE 20 Account properties
1302 ACCESS ITEM_TITLE 18 Min User Id Length:
1303 ACCESS ITEM_TITLE 18 Min Password Length:
1304 ACCESS ITEM_TITLE 18 Max Login Attempts:
1305 ACCESS ITEM_TITLE 18 Password Expiry:
1306 ACCESS ITEM_TITLE 18 User Timeout:
HA029280 Chapter 5

1307 ACCESS MESSAGE 128 Reducing password expiry period may result in imme-
diate account expiry.
1308 ACCESS BUTTON_TEXT 12 REINSTATE
1309 ACCESS ITEM_TITLE 18 Password Expires In:
1310 ACCESS MESSAGE 128 Your password is due to expire. Please change it
1311 ACCESS ITEM_TITLE 18 Expires
1312 ACCESS ITEM_TITLE 18 Attributes
1313 ACCESS BUTTON_TEXT 12 ENABLE
1314 ACCESS PAGE _TITLE 20 Security Access - Retired
1315 ACCESS DIALOG_TITLE 28 Retire User
1316 ACCESS BUTTON_TEXT 12 RETIRE
1317 ACCESS DIALOG_TITLE 28 ACCESS ERROR
1318 ACCESS DIALOG_TEXT 80 Illegal Password
1319 ACCESS DIALOG_TEXT 80 Illegal User ID and/or Name
1320 ACCESS DIALOG_TEXT 80 User ID and/or Name Already In Use
1321 ACCESS ITEM_TITLE 18 Sign:
1322 ACCESS ITEM_TITLE 18 Authorise:
1323 ACCESS ITEM TITLE 18 View Only:
1325 ACCESS ITEM_TITLE 18 Admin Only:
1333 ACCESS ITEM_TITLE 18 FTP:
1334 ACCESS ITEM_TITLE 18 Remote:
1353 ACCESS BUTTON TEXT 12 STATS
1354 ACCESS PAGE_TITLE 20 Statistics
1355 ACCESS ITEM_TITLE 18 Users:
1356 ACCESS ITEM_TITLE 18 Retired Users:
1357 ACCESS ITEM_TITLE 18 New Users:
1359 ACCESS BUTTON_TEXT 12 MAINT
1360 ACCESS PAGE_TITLE 20 Account Maintenance
1361 ACCESS ITEM_TITLE 18 Recovery Account:
1362 ACCESS ITEM_TITLE 18 Master Access:
1363 ACCESS ITEM_TITLE 18 Edit Own Expired Password:
1393 ACCESS MESSAGE 128 Insuffcient Administrator Accounts
1394 ACCESS BUTTON_TEXT 12 RECOVER
1395 ACCESS PAGE_TITLE 20 Administration Recovery
1396 ACCESS INTRO 64 Please report the key, date and time below to the sup-
port desk who will issue you with the recovery pass-
word
1397 ACCESS ITEM_TITLE 18 Recovery Key:
1398 ACCESS ITEM_TITLE 18 Date/Time:
1399 ACCESS ITEM_TITLE 18 Minutes Left:
1400 ADMIN MENU_TITLE 16 Administration
1401 ADMIN LEGEND 11 ADMIN
1410 NET_AUDIT PAGE_TITLE 20 Network Audit Trail
1411 NET_AUDIT LEGEND 11 NET AUDIT
1412 NET_AUDIT PARA 24 Destination node
1413 NET_AUDIT ITEM_TITLE 18 LIN Node:
1414 NET_AUDIT ITEM_TITLE 18 LIN Segment:
1415 NET_AUDIT NAT_STATE 12 (Disabled)
1416 NET_AUDIT NAT_STATE 12 UNINIT
1417 NET_AUDIT NAT_STATE 12 INIT
1418 NET_AUDIT NAT_STATE 12 CONNECTED
Chapter 5 HA029280

1419 NET_AUDIT NAT_STATE 12 ACTIVE
1420 NET_AUDIT ITEM_TITLE 18 Alarm active:
1421 NET_AUDIT ITEM_TITLE 18 Alarm cleared:
1422 NET_AUDIT ITEM_TITLE 18 Alarm ack’ed:
1423 NET_AUDIT ITEM_TITLE 18 Cached alarms:
1424 NET_AUDIT ITEM_TITLE 18 System event:
1425 NET_AUDIT ITEM_TITLE 18 Block event:
1426 NET_AUDIT ITEM_TITLE 18 Operator note:
1427 NET_AUDIT ITEM_TITLE 18 Block value change:
1428 NET_AUDIT ITEM_TITLE 18 Message active:
1429 NET_AUDIT ITEM_TITLE 18 Message cleared:
1430 NET_AUDIT ITEM_TITLE 18 Message ack’ed:
1436 NET_AUDIT ITEM_TITLE 18 Min alarm priority:
1437 NET_AUDIT ITEM_TITLE 18 Min event priority:
1450 NET_AUDIT ITEM_TITLE 18 Mode:
1451 NET_AUDIT NAT_STATE 12 ISOLATED
1452 NET_AUDIT NAT_STATE 12 PROVIDER
1453 NET_AUDIT NAT_STATE 12 CONSUMER
1459 NET_AUDIT ITEM_TITLE 18 Revision:
1460 ACCESS BUTTON_TEXT 12 DEPLOY
1461 ACCESS PAGE_TITLE 20 Deploy Access
1462 ACCESS ITEM_TITLE 18 Number of Slave Nodes:
1463 ACCESS ITEM_TITLE 18 Slave Nodes:
1464 ACCESS BUTTON_TEXT 12 CONFIG
1465 ACCESS PAGE_TITLE 20 Deploy Access – Config
1466 ACCESS BUTTON_TEXT 12 CLEAR
1467 ACCESS BUTTON_TEXT 12 FILL
1468 ACCESS BUTTON_TEXT 12 SORT
1469 ACCESS MESSAGE 128 Deploying...
1470 ACCESS ITEM_TITLE 18 Node:
1471 ACCESS MESSAGE 128 Aborting...
1480 ACCESS BUTTON_TEXT 12 REVISION
1481 ACCESS PAGE_TITLE 20 Revision Information
1482 ACCESS ITEM_TITLE 18 Revision:
1483 ACCESS ITEM_TITLE 18 Revised On:
1484 ACCESS ITEM_TITLE 18 Revised By:
1485 ACCESS ITEM_TITLE 18 Authorised By:
1486 ACCESS ITEM_TITLE 18 Reason:
1487 ACCESS ITEM_TITLE 18 Bound to:
1488 ACCESS ITEM_TITLE 18 Operational Changes:
1500 SIGN PAGE_TITLE 20 Signature Configuration
1501 SIGN LEGEND 11 SIG CONFIG
1502 SIGN ITEM_TITLE 18 Function:
1503 SIGN BUTTON_TEXT 12 SAVE
1504 SIGN BUTTON_TEXT 12 DEFAULTS
1505 SIGN MESSAGE 128 The ‘ENABLE’ button may be used to turn on elec-
tronic signatures. Once signatures have been turned
on and saved, they cannot be turned off again.
1506 SIGN ITEM_TITLE 15 Revision:
1510 SIGN SIG_LEVEL 16 No Confirmation
1511 SIGN SIG_LEVEL 16 Confirm Only
1512 SIGN SIG_LEVEL 16 Password
HA029280 Chapter 5

1513 SIGN SIG_LEVEL 16 Signature
1514 SIGN SIG_LEVEL 16 Sign & Authorise
1515 SIGN SIG_LEVEL 16 Action Disabled
1520 SIGN ITEM_TITLE 18 Field Changes:
1521 SIGN ITEM_TITLE 18 Alarm priority Changes:
1522 SIGN ITEM_TITLE 18 Units Changes:
1523 SIGN ITEM_TITLE 16 Wiring Changes:
1524 SIGN ITEM_TITLE 16 Field Changes:
1525 SIGN ITEM_TITLE 16 Segment Change:
1526 SIGN ITEM_TITLE 16 Segment Change (held):
1527 SIGN ITEM_TITLE 16 Current Segment Change:
1528 SIGN ITEM_TITLE 16 RUN (edited)
1529 SIGN ITEM_TITLE 16 ACK (6-10)
1530 SIGN ITEM_TITLE 16 ACH (11-15)
1531 SIGN ITEM_TITLE 16 User Password Change:
1532 SIGN ITEM_TITLE 16 ModbusM/TCP SAVE:
1540 COMMS COMMS_PORT 5 ENET1
1550 COMMS COMMS_ITEM 8 ELIN
1551 COMMS COMMS_ITEM 8 FTP
1560 COMMS BUTTON TEXT 12 ETHERNET
1561 COMMS PAGE_TITLE 20 Comms - Ethernet
1562 COMMS PARA 24 LIN Protocol Setup
1563 COMMS PARA 24 Local IP Setup
1564 COMMS PARA 24 Remote Subnet Node List
1565 COMMS SEPARATOR 1 .
1566 COMMS ITEM_TITLE 16 Protocol Name:
1567 COMMS ITEM_TITLE 16 All Subnet Enable:
1569 COMMS ITEM_TITLE 16 Address Assignment:
1570 COMMS ITEM 16 Undefined
1571 COMMS ITEM 16 Fixed
1572 COMMS ITEM 16 DHCP
1573 COMMS ITEM 16 BootP
1574 COMMS ITEM 16 DHCP+LL
1575 COMMS ITEM 16 BootP+LL
1576 COMMS ITEM 16 Link Local
1580 COMMS ITEM_TITLE 16 IP Address:
1581 COMMS ITEM_TITLE 16 Subnet Mask:
1582 COMMS ITEM_TITLE 16 Default Gateway:
1583 COMMS ITEM_TITLE 16 Number of Nodes:
1584 COMMS ITEM_TITLE 16 Node:
1585 COMMS SEPARATOR 2 :
1586 COMMS ITEM_TITLE 16 MAC Address:
1587 COMMS DIALOG_TITLE 28 WARNING
1588 COMMS DIALOG_TEXT 80 The specified IP address/mask combination may be
invalid.
1590 COMMS ITEM 16 None
1591 COMMS ITEM 16 RO
1592 COMMS ITEM 16 RW
1593 COMMS ITEM 16 All
Chapter 5 HA029280

1600 COMMS LEGEND 8 MODBUS_
1601 COMMS LEGEND 8 /TCP
1602 COMMS PAGE_TITLE 20 MODBUS_
1603 COMMS PAGE_TITLE 20 /TCP
1604 COMMS ITEM_TITLE 16 INSTRUMENT
1605 COMMS ITEM_TITLE 16 SLAVE ADDRESS
1606 COMMS ITEM_TITLE 16 HOST
1607 COMMS ITEM_TITLE 16 TCP PORT
1608 COMMS LEGEND 11 NEW
1609 COMMS PAGE_TITLE 20 New Slave
1610 COMMS ITEM_TITLE 16 Instrument No:
1611 COMMS ITEM_TITLE 16 Slave Address
1612 COMMS ITEM_TITLE 16 Host IP:
1613 COMMS ITEM_TITLE 16 TCP Port No:
1614 COMMS LEGEND 11 ADD
1615 COMMS LEGEND 11 TUNING
1616 COMMS PAGE_TITLE 20 Tuning Parameters
1617 COMMS LEGEND 11 DEFAULTS
1618 COMMS LEGEND 11 DELETE
1619 COMMS LEGEND 11 DEL ALL
1620 COMMS DIALOG_TITLE 20 Confirm Delete All
1621 COMMS ITEM_TITLE 16 Host re. Retry delay:
1622 COMMS ITEM_TITLE 16 Connect initial delay:
1623 COMMS ITEM_TITLE 16 Connect retry 1 delay:
1626 COMMS ITEM_TITLE 16 Reconnect retry delay:
1627 COMMS ITEM_TITLE 16 Reconnect num retries:
1628 COMMS ITEM_TITLE 16 Asy conn Poll tmeout:
1629 COMMS ITEM_TITLE 16 Async connect timeout:
1680 SYSSUM ITEM_TITLE 16 MiniPCI Card:
1681 SYSSUM ITEM 16 None
1682 SYSSUM ITEM 16 Profibus
1683 SYSSUM ITEM 16 Spare
1691 SYSSUM ITEM 16 L11:CARB_DIFFx1
HA029280 Chapter 5
5.2.5 Panel customisation using the dictionary
It is possible to customise the standard panel interface by defining certain dictionary entries to be “empty”. An empty
dictionary entry takes the form “S<N>,” in the .uyl file. Note: the “,” is the last character on the line, it must not be
followed by any other (even a space character). If any of the dictionary entries listed below is set to be “empty” then
the corresponding function is removed from the standard interface.
Note: do not define dictionary entries other than those listed below to be empty.
NO. CONTEXT TEXT FUNCTION

62 ALMMENU NOTE Entering of notes into alarm history
340 FILE MGR COPY ALL Copy all selected files
342 FILE MGR DEL_ALL Delete all selected files
384 APP MGR LOAD Load a new application
385 APP MGR LD+RUN Load and run a new application
386 APP MGR UNLOAD Unload current application
387 APP MGR SAVE Save application files
388 APP MGR SAVE AS Save application files to a new name
389 APP MGR DELETE Delete an application
390 APP MGR STOP Stop a running application
391 APP MGR START Start a loaded application
428 SPP RUN Running the currently loaded program
429 SPP HOLD Hold the currently running program
430 SPP ABORT Aborting programs
433 SPP LOAD Load a program
434 SPP SAVE Save a program
435 SPP SAVE AS Save program to a new name
436 SPP DELETE Delete a program
479 SPP MONITOR Menu button to call Monitor page
480 SPP PROGRAMS Menu button to call Programs page
481 SPP SCHEDULE Scheduling programs
482 SPP PREVIEW Preview of program
483 SPP PRE-PLOT Live/preview combined display of program
484 SPP EDIT Editing of programs
490 SPP RUN FROM Starting a program part way through
501 SPP NEW Create a new program
513 SPP INS SEG Insert a new segment
514 SPP DEL SEG Delete a segment
517 SPP LAYOUT Modify editor page layout
570 SPP SKIP Skipping the currently executing segment
712 LOGGRP File Type: File type ASCII
725 LOGGRP Name Type: Type of log file name
727 LOGGRP Column Titles: Enable/disable column titles in ASCII files
728 LOGGRP Date Format: Format of date/time in ASCII files
732 LOGGRP LOG NOW Log an ASCII sample now
777 LOGAMAN EXPORT ALL Export from internal archive to removable medium
796 LOGAMAN EXPORT Export from internal archive to removable medium
805 CLONING EXPORT Export files from instrument
806 CLONING IMPORT Import files into instrument
940 FILE MGR COPY Copy a file
941 FILE MGR DELETE Delete a file
Chapter 5 HA029280
5.2.5 PANEL CUSTOMISATION USING THE DICTIONARY (Cont.)
NO. CONTEXT TEXT FUNCTION

1018 ACCESS USERS Change to multi-user access
1108 RCP CAPTURE AS Capture live value to a new recipe
1102 RECIPE DOWNLOAD Download the recipe
1103 RECIPE ABORT Abort recipe download
1104 RECIPE LOAD Load a recipe file
1105 RECIPE SAVE Save as recipe file
1106 RECIPE SAVE AS Save recipe to new file
1107 RECIPE CAPTURE Capture live values to current recipe
1109 RECIPE NEW Create a new recipe
1110 RECIPE DELETE Delete a recipe or recipe file
1111 RCP ADD LINE Add a production line to a recipe file
1112 RECIPE DELETE Delete a recipe variable
1113 RECIPE INSERT Insert a recipe variable
1114 RCP CREATE Create a new recipe file
1115 RCP LINES Display list of production lines
1120 RECIPE RECIPES Menu button to call Recipes page
1122 RECIPE STATUS Menu button to call Status page
1150 RECIPE MONITOR Menu button to call Monitor page
1166 RECIPE ITEM_TITLE File name filter
1170 RECIPE EDIT Menu button to call Editor
1220 BATCH LOAD Menu button to call Load page
1230 BATCH LOAD Load a new batch (batch can be loaded from strategy in blocks only
if this is removed)
1231 BATCH START Start a batch
1232 BATCH HOLD Put batch into hold
1233 BATCH RESTART Restart batch after putting into Hold
1234 BATCH ABORT Abort a running batch
1235 BATCH RESET Reset a batch
1236 BATCH NOTE Enter a batch note
1237 BATCH SAVE AS Save a batch that has been created
1238 BATCH CREATE Create a new batch file
1240 BATCH STATUS Menu button to call Status page
The following items are empty by default. If set, they enable the additional features as described.
NO. CONTEXT FUNCTION
788 LOGGRP Display the number of groups active out of total

1166 RECIPE File name filter
HA029280 Chapter 5
5.2.6 Alarm/event customisation using the dictionary
The following dictionary entries may be defined to add additional information into the alarm text. In all cases the text
(if defined) prefixes the another item. If a space is required between the prefix and the item this must be included in
the dictionary item when defined. The text is used in the following contexts:
1. Panel Event Log (See section 3.5.6)

2. Alarms and events recorded on trends (See section 3.6.1)
3. Alarms and events recorded in log files
4. Printer (if configured)
No Prefixes Notes
580 Original value in a block field change event.

581 New value in a block field change event.
582 Message acknowledge reason
583 Signature reason Auditor Option Only
584 Logged in user’s name
585 Signature Auditor Option Only
586 Authorisation Auditor Option Only
Chapter 5 HA029280
5.3 THE ERROR TEXT DICTIONARY
The contents of the Error text dictionary on delivery are as follows:
No. CODE TEXT

E1 8301 Bad template
E2 8302 Bad block number
E3 8303 No free blocks
E4 8304 No free database memory
E5 8305 Not allowed by block create
E6 8306 In use
E7 8307 Max length =
E8 8308 No spare databases
E9 8309 Not enough memory
E10 8320 Bad library file
E11 8321 Bad template in library
E12 8322 Bad server
E13 8323 Cannot create EDB entry
E14 8324 Bad file version
E15 8325 Bad template spec
E16 8326 Unable to make block remote
E17 8327 Bad parent
E18 8328 Corrupt data in .DBF file
E19 8329 Corrupt block spec
E20 832A Corrupt block data
E21 832B Corrupt pool data
E22 832C No free resources
E23 832D Template not found
E24 832E Template resource fault
E25 8330 Cannot start
E26 8331 Cannot stop
E27 8332 Empty database
E28 8333 Configurator in use
E29 8340 .DBF file write failed
E30 8341 More than one .RUN file found
E31 8342 .RUN file not found
E32 834A Connection source is not an O/P
E33 834B Multiple connection to same I/P
E34 834C Connection destination not I/P
E35 834D No free connection resources
E36 834E Bad conn. Src/dest block/field
E37 834F Invalid connection destination
E38 8350 Hot start switch is disabled
E39 8351 No database was running
E40 8352 Real-time clock is not running
E41 8353 Root block clock is not running
E42 8354 Hotstart time was exceeded
E43 8355 Root block is invalid
E44 8356 Too many control loops
E45 8357 Coldstart switch is disabled
HA029280 Chapter 5
5.3 THE ERROR TEXT DICTIONARY (Cont.)
As with the System text dictionary, it is possible to:

1. Replace any text item (Error message) in the Error text dictionary with messages customised for a particular in-
dustry or application and/or
2. Internationalise the messages by creating a new dictionary for each of up to ten languages
5.3.1 Editing error messages
The Error dictionary supplied, is a part of the _system.uyl file. To customise it, the principle is the same as for the
System text dictionary:
1. In the Error text dictionary, find the text to be replaced
3. Key in the reference number, and then the text you want to replace it with, related by the following syntax:
E<N>,<text>
where:
<N> is the reference number of the record you want to change
For example: E7,File not found.
5.3.2 Creating new language error text
Any additional language dictionaries that are created must be named _system0.uyl, _system1.uyl, _system2.uyl, and so
on up to _system9.uyl, (one dictionary for each language to be implemented)
PROCEDURE
In Excel or any similar spreadsheet program:

1. Write a first column of reference numbers, from E1 to at least E45
2. In the second column, assign code numbers
3. In the third column, write the error message in the required language.
Chapter 5 HA029280
5.4 THE EVENT TEXT DICTIONARY
On delivery, the Event text dictionary is as listed below. As with the System and Error dictionaries, it is possible to:
1. Replace any text item (Event message) in the Event dictionary with messages customised for a particular industry
or application, and/or
2. Internationalise the messages by creating a new dictionary for each of up to ten languages.
V11 to V13 take the User ID, V110 to 116 take the recipe file name or the recipe name.
No. EVENT NAME MAX LENGTH MAX LENGTH

1/4 VGA XGA
V1 Clock set 16 characters 16 characters
V3 Started N/A 16 characters Note 1
V4 Ack all 16 characters 16 characters
V5 Access Save N/A 16 characters
V6 Access Updated N/A 16 characters Note 1
V7 Timeout 8 characters 16 characters
V8 Retired User N/A 16 characters Note 1
V9 Disqualified 8 characters 16 characters
V10 Access change 16 characters 16 characters
V11 Log on 8 characters 16 characters
V12 Log off 8 characters 16 characters
V13 Log fail 8 characters 16 characters
V14 Password change 8 characters 16 characters
V15 Expired user 8 characters 16 characters
V16 Disable user 8 characters 16 characters
V17 Enabled user 8 characters 16 characters
V18 Deleted user 8 characters 16 characters Note 2
V19 Created user 8 characters 16 characters
V20 Purged user N/A 16 characters Note 1
V31 ITD mem full 16 characters 16 characters
V33 Database Running N/A 16 characters
V34 Deleted file 8 characters 16 characters
V35 Imported file 8 characters 16 characters
V36 Deleted Database 8 characters 16 characters
V37 Created Database 8 characters 16 characters
V38 Renamed Block 8 characters 16 characters Note 2
V39 Created Block 8 characters 16 characters Note 2
V40 Deleted Block 8 characters 16 characters Note 2
V41 Database Loaded 16 characters 16 characters
V42 Database Started 16 characters 16 characters
V44 Database Resumed 16 characters 16 characters
V45 Database Restart 16 characters 16 characters
V46 Database Stopped 16 characters 16 characters
V47 Database Saved 16 characters 16 characters
V48 Database Unload 16 characters 16 characters
V49 Database Stop 16 characters 16 characters
V50 Late 8 characters 16 characters
V51 Loaded 8 characters 16 characters
V52 No File 8 characters 16 characters
V53 Too big 8 characters 16 characters
Notes:
1 Applies only to units fitted with the Auditor Option
2 Not applicable to units fitted with the Auditor Option
HA029280 Chapter 5
5.4 THE EVENT TEXT DICTIONARY (Cont.)

1/4 VGA XGA
V54 Bad refs 8 characters 16 characters
V55 Sch load 8 characters 16 characters
V56 Run 8 characters 16 characters
V57 Held 8 characters 16 characters
V58 Resume 8 characters 16 characters
V59 Abort 8 characters 16 characters
V60 Finish 8 characters 16 characters
V62 Heldback 8 characters 16 characters
V63 Restart 8 characters 16 characters
V64 Overnest 8 characters 16 characters
V65 Bad Prog 8 characters 16 characters
V66 Sch Abrt 8 characters 16 characters
V67 OverLims 8 characters 16 characters
V68 Early 8 characters 16 characters
V69 Ramp Dis 8 characters 16 characters
V70 DBN Mem Full 16 characters 16 characters
V72 Bad _SYSTEM.OPT 16 characters 16 characters
V74 Comms Changed 16 characters 16 characters
V75 Startup Changed 16 characters 16 characters
V76 Instrument Reset 16 characters 16 characters
V77 Health Relay 16 characters 16 characters See Note
V78 Run Relay 16 characters 16 characters See Note
V79 Panel Save 16 characters 16 characters
V80 No .GWF Found 16 characters 16 characters
V82 Created .GWF 16 characters 16 characters
V83 Extra Modbus/S 16 characters 16 characters
V85 Language 16 characters 16 characters
V86 Date Format 16 characters 16 characters
V87 Time Format 16 characters 16 characters
V88 Duration Format 16 characters 16 character
V89 Program Edit 16 characters 16 characters
V90 Lost Ed 8 characters 16 characters
V91 Skip 8 characters 16 characters
V92 No Goto 8 characters 16 characters
V93 Common 8 characters 16 characters
V94 Save 8 characters 16 characters
V95 Deleted program 8 characters 16 characters
V96 Run From 8 characters 16 characters
V97 Skip Request N/A 16 characters See Note
V98 Segment Edit 16 characters 16 characters
V99 Segment Edit 16 characters 16 characters
V102 Gap 8 characters 16 characters
V103 Deleted Log File 8 characters 16 characters
V104 Too Big Log File 8 characters 16 characters
V108 Schedule 8 characters 16 characters
V109 Sch Clr 8 characters 16 characters
V110 Load 8 characters 16 characters
Note: Applies only to units fitted with the Auditor Option
Chapter 5 HA029280

1/4 VGA XGA
V111 Download 8 characters 16 characters
V112 Complete 8 characters 16 characters
V113 Failed 8 characters 16 characters
V115 Capture 8 characters 16 characters
V117 Deleted Recipe 8 characters 16 characters
V120 Load 8 characters 16 characters
V121 Start 8 characters 16 characters
V122 Hold 8 characters 16 characters
V124 Reset 8 characters 16 characters
V125 Restart 8 characters 16 characters
V126 Complete 8 characters 16 characters
V128 Pause 8 characters 16 characters
V129 Resume 8 characters 16 characters
V130 Stop 8 characters 16 characters
V131 Phase 8 characters 16 characters
V132 Create 8 characters 16 characters
V138 Ethernet Save 16 characters 16 characters
V139 Modbus/TCP Save 16 characters 16 characters
V140 Net Audit save N/A 16 characters See Note
V141 Lost Messages N/A 16 characters See Note
V142 Power Cycle N/A 16 characters See Note
V143 Net Audit Update 16 characters 16 characters See Note
V150 Sig Conf Save 16 characters 16 characters See Note
V151 Sig Conf Update 16 characters 16 characters See Note
V152 New Level (Sign) 16 characters 16 characters See Note
V153 Old Level (Sign) 16 characters 16 characters See Note
V154 Item (Sign) 16 characters 16 characters See Note
V155 Page (Sign) 16 characters 16 characters See Note
V156 Function (Sign) 16 characters 16 characters See Note
V157 Unused Signature 16 characters 16 characters See Note
V158 Sign Fail 16 characters 16 characters See Note
V159 Authorise Fail 16 characters 16 characters See Note
V160 Min ID 8 characters 16 characters
V161 Min Password 8 characters 16 characters
V162 Max Login Attemp 8 characters 16 characters
V163 Expire Pasword 8 characters 16 characters
V164 Logout Timeout 8 characters 16 characters
V168 Access Upd Fail 16 Characters 16 Characters See Note
V169 Reinstated 16 characters 16 characters See Note
V170 Recover Enable 16 characters 16 characters
V171 Recover Disable 16 characters 16 characters
V172 Master Access 16 characters 16 characters See Note
V173 Slave Access 16 characters 16 characters See Note
V174 Bind Access 16 characters 16 characters See Note
HA029280 Chapter 5
No EVENT NAME MAX LENGTH MAX LENGTH

1/4 VGA XGA
V175 Unbind Acces 16 characters 16 characters See Note
V176 Access Bind Fail 16 characters 16 characters See Note
V177 ForcNew on PwdEx 16 characters 16 characters See Note
V178 Disable on PwdEx 16 characters 16 characters See Note
V179 Deploy Access 16 characters 16 characters See Note
V180 Clock sync 16 characters 16 characters
V181 Clock master 16 characters 16 characters
V182 Clock slave 16 characters 16 characters
V183 Clock isolated 16 characters 16 characters
V185 Expired 16 characters 16 characters See Note
V186 Invalid 8 characters 16 characters See Note
V190 Log On Remote 8 characters 16 characters
V191 Log Off remote 8 characters 16 characters
V192 Log Fail Remote 8 characters 16 characters
V193 Timeout Remote 8 characters 16 characters
V195 Log On FTP 8 characters 16 characters
V196 Log Off FTP 8 characters 16 characters
V197 LogFail FTP 8 characters 16 characters
V198 Timeout FTP 8 characters 16 characters
Chapter 5 HA029280
5.4.1 Editing Event Messages
The Event dictionary supplied, forms a part of the _system.uyl file. To customise it, the principle is the same as for
the System and Error text dictionaries:
1. In the Event text dictionary, find the text to be replaced
3. Key in the reference number, and then the replacement text related by V<N>,<text>
where: <N> is the reference number of the record to be changed

For example: V41,Appn loaded.
5.4.2 Creating new language event text
Any additional language dictionaries that are created must be named _system1.uyl, _system2.uyl, and so on up to
_system9.uyl (one dictionary for each language to be implemented).
PROCEDURE
Using a standard text or spreadsheet editor,
1. Write a first column of reference numbers, from V1 to at least V116
2. In the second column, write the message in the required language.
Files should be saved as CSV files.
5.4.3 Event priorities
All events are initially, priority 1. It is possible to assign other priorities in order, for example, to filter events for
printing, logging or trending (using the DR_ALARM blocks). As with alarms, each event may be assigned a priority
of 0 to 15, inclusive, where priority 0 disables the event.
If such customisation is required, the optional file _SYSTEM.UYE may be added to the system. This is a text file,
containing a single line for each event requiring customisation. The syntax is : <Event number>,<Priority>, where the
event number is obtained from the table above, and Priority is 0 to 15.
For example: 41,0

42,0
would cause the events ‘Database loaded’ and ‘Database started’ to be disabled
HA029280 Chapter 5
5.5 THE USER TEXT DICTIONARY
This dictionary (initially empty) is available for users who wish to enter their own texts for display on their Home
page and User screens, with additional files to hold versions in other languages, if required. The User text dictionary
is used in conjunction with the User Screen Editor. For more details refer to The User Screen Editor Handbook (part
no. HA260749 U005).
For every System file there may be an optional User file to go with it.
Filenames and record syntaxes follow the pattern of those for the _system.uyl files. Filenames are:
_user.uyl for the file holding terms customised in English (or other home language).
_user<n>.uyl for files holding other-language (international) versions,
with n taking integer values from 0 up to 9, one value for each language to be made available.
The syntax of each record is: U<N>,<text>
where:
<N> is the index number of the record
<text> is the text.
The dictionary can hold a maximum of 200 records, each consisting of up to 32 characters.
5.6 THE PROGRAMMER TEXT DICTIONARY
The Programmer text dictionary holds user-generated text items for display by the Setpoint Program Editor. For more
details refer to The Setpoint Program Editor Handbook (part no. HA261134U005). Entries are user text, so the items -
when written - are held in the User text dictionary, _user.uyl.
The syntax of each record is: P<N>,<text>
where:
<N> is the index number of the record
<text> is the text.
The dictionary can hold 200 records, each up to 16 characters long.
Chapter 5 HA029280
5.7 PANEL NAVIGATION
This describes how to access the menu system in order to perform a task and achieve an objective.
This section consists of:
1 The Panel Navigation file (Section 5.7.1)
The versions
Coding - The Bare Panel version, _system.pnl
Coding - The Application Panel version, _default.pnl
2 Editing the _default.pnl file (Section 5.7.2)
3 Line types (Section 5.7.3)
Panel Agent declaration
Panel Driver declaration
Home Page declaration
Root Page declaration
Initial Page declaration
4 Agent types (Section 5.7.4)
The architecture of the Standard Interface is coded in the Panel Navigation file, more usually called the .pnl file. This
section of the manual describes the Panel Navigation file and how to edit it in order to customise the architecture of
the Standard Interface to your own requirements.
The architecture of the User Screen Interface is assembled using the User Screen Editor and is held in other files. To
customise the architecture of the User Screen Interface, see the User Screen Editor Handbook (part no.
HA260749U005).
5.7.1 The Panel Navigation file
THE VERSIONS
For any instrument there can be three versions of the Panel Navigation file held in software, with copies of two of
them in ROM. The file names are <appname>.pnl, _default.pnl, and _system.pnl, with ROM copies of _default.pnl
and _system.pnl.
Each of these versions is mostly a list of agents, with various parameters determining behaviour. Some of these pa-
rameters are agent-specific, others are generic.
Codings for _system.pnl (the Bare Panel version) and _default.pnl (called the Application Panel version here) follow.
Note: For units fitted with the Audit option, please see Auditor Option Versions (below) , for codings.
With an application (say, <appname>) loaded, the system looks for <appname>.pnl. This is a version that has been
customised for that application and which will generate an interface architecture specifically for it. For an instrument
that periodically runs different applications, there could be an <appname>.pnl for each application.
If <appname>.pnl cannot be found, the instrument searches for _default.pnl. This is a generic version that works for
all applications.
If _default.pnl cannot be found, the instrument loads a firmware copy that can always be found in ROM. (The instru-
ment is shipped with these files, and they are loss-proof.)
With no application loaded the system looks for a file called _system.pnl, known as the ‘bare’ panel version (see also
Chapter 4, section 4.3, Managing an Application). If this file cannot be found, the corresponding version in ROM is
used.
HA029280 Chapter 5
5.7.1 THE PANEL NAVIGATION FILE (Cont.)
THE VERSIONS (Cont.)
Coding - The Bare Panel version (_system.pnl)

==============================
SAMPLE BARE PANEL SYSTEM
==============================
(Quarter-) VGA Driver:
D1,QVGA
Home Agent (set up for user page 1; if this does not exist then it will
default to the System Summary, which has the lowest Id in the main pane)
H1
Initial page (first page after power-up) is the same
I1
Root Agent:
R1000
A1000,MENU,,,3,,,2010,4000,2210,2300,2130,2400,9012,1
A2010,SYS_SUM
A2210,APP_MGR,4,,,0
SETUP submenu
A2300,MENU,,,3,#S398,#S399,2030,2040,2050,2060,2070
A2030,STARTUP,,3
A2040,COMMS,,4
A2050,CLOCK,3
A2060,INTERNAT,,4
A2070,PANEL,,2
MAINTENANCE submenu
A2400,MENU,4,,3,#S930,#S931,2080,2140,2150,2160
A2080,CLONE,4
A2140,FILE_MGR,4
A2150,SOFT_OPT,4
A2160,BATCH_MAINT_4
Alarm history (for event log only)

A9010,ALM_HIST,2,,2
A4000,ACCESS
Dialogue Agent
A100000,DIALOG,,,4
==== END OF FILE ====
Continued
Chapter 5 HA029280
Coding - Sample Application Panel version (_default.pnl)
====================================
SAMPLE APPLICATION PANEL SYSTEM
====================================
(Quarter-) VGA Driver

D1,QVGA
Home page is first User Page (or will default to Overview else System Summary,
as this has the lowest Id in the main pane)
H1
Initial page (first page after power-up) is the user screen 100 (if present)
I100
Root Menu
R1000
A1000,MENU,,,3,,,4000,2000,9000,1500,3000,7000,5000,1
System Submenu
A2000,MENU,,,3,#S130,#S131,2010,2200,2300,2080
A2010,SYS_SUM
A2080,CLONE,4
Application sub-submenu
A2200,MENU,,,3,#S396,#S397,2020,2210,2230
A2020,APP_SUM
A2210,APP_MGR,4,,,0
A2230,FB_MGR,3,4,,0
Setup sub-submenu
A2300,MENU,,,3,#S398,#S399,2030,2040,2050,2060,2070
A2030,STARTUP,,3
A2040,COMMS,,4
A2050,CLOCK,3
A2060,INTERNAT,,4
A2070,PANEL,,2
Programmer
A3000,SPP_MENU,2,3,3,3010
A3010,SPP,2,3,2,3000,1500
(Continued)
HA029280 Chapter 5
Security Access
A4000,ACCESS
Logging Submenu
A5000,LOG_MENU,2,,3,5010
A5010,LOG,2,3,2
Area/Group/Point displays
A1500,AGP,1,2,2
Recipe
A7000,RCP_MENU,2,3,3,7010
A7010,RECIPE,2,3,2,7000
Batch
A8000,BATCH_MENU,2,,3,8010
A8010,BATCH,2,3,2,8011
Alarms
A9000,ALM_MENU,2,,3,9010,9011,9021
A9010,ALM_HIST,2,,2
A9020,MESSAGE,2,,3
Dialog Agent
A100000,DIALOG,,,4
Chapter 5 HA029280
AUDITOR OPTION VERSIONS
This sub section contains listing similar to those in 5.7.1.1 above, but for instruments with the Auditor option fitted.
Coding - The Bare Panel version (_system.pnl)

==============================
SAMPLE BARE PANEL SYSTEM
(Auditor Option fitted)
==============================
(Quarter-) VGA Driver:
D1,QVGA
Home Agent (set up for user page 1; if this does not exist then it will default to the System Summary, which has
the lowest Id in the main pane)
H1
Initial page (first page after power-up) is the same

I1
Root Agent:
R1000
A1000,MENU,,,3,,,2010,4000,2210,2300,2130,2400,2500,9012,1
A2010,SYS_SUM
A2210,APP_MGR,4,,,0
SETUP submenu
A2300,MENU,,,3,#S398,#S399,2030,2040,2050,2060,2070
A2030,STARTUP,,3
A2040,COMMS,,4
A2050,CLOCK,3
A2060,INTERNAT,,4
A2070,PANEL,,2
MAINTENANCE submenu
A2400,MENU,4,,3,#S930,#S931,2080,2140,2150,2160
A2080,CLONE,4
A2140,FILE_MGR,4
A2150,SOFT_OPT,4
A2160,BATCH_MAINT,4
Admin submenu
A2500,MENU,5,,3,#S1400,#S1401,2510,2520
A2510,NET_AUDIT,5
A2520,SIGN_CFG,5
A4000,ACCESS
Alarm History (for event log only)

A9010,ALM_HIST,2,,2
Dialogue Agent
A100000,DIALOG,,,4
Signature Agent
A200000,SIGN,,,5
HA029280 Chapter 5
AUDITOR PACK VERSIONS (Cont.)
Coding - Sample Application Panel version (_default.pnl)
====================================
SAMPLE APPLICATION PANEL SYSTEM
(Auditor Option fitted)
====================================
(Quarter-) VGA Driver

D1,QVGA
Home page is first User Page (or will default to Overview else System Summary,
as this has the lowest Id in the main pane)
H1
Initial page (first page after power-up) is the user screen 100 (if present)
I100
Root Menu
R1000
A1000,MENU,,,3,,,4000,2000,9000,1500,3000,7000,8000,5000,1
System Submenu
A2000,MENU,,,3,#S130,#S131,2010,2200,2300,2080,2500
A2010,SYS_SUM
A2080,CLONE,4
Application sub-submenu
A2200,MENU,,,3,#S396,#S397,2020,2210,2230
A2020,APP_SUM
A2210,APP_MGR,4,,,0
A2230,FB_MGR,3,4,,0
Setup sub-submenu
A2300,MENU,,,3,#S398,#S399,2030,2040,2050,2060,2070
A2030,STARTUP,,3
A2040,COMMS,,4
A2050,CLOCK,3
A2060,INTERNAT,,4
A2070,PANEL,,2
(Continued)
Chapter 5 HA029280
AUDITOR PACK VERSIONS (Cont.)
Admin
A2500,MENU,5,,3,#S1400,#S1401,2510,2520
A2510,NET_AUDIT,5
A2520,SIGN_CFG,5
Programmer
A3000,SPP_MENU,2,3,3,3010
A3010,SPP,2,3,2,3000,1500
Security Access
A4000,ACCESS
Logging Submenu
A5000,LOG_MENU,2,3,5010
A5010,LOG,2,3,2
Area/Group/Point displays
A1500,AGP,1,2,2
Recipe
A7000,RCP_MENU,2,3,3,7010
A7010,RECIPE,2,3,2,7000
Batch
A8000,BATCH_MENU,2,,3,8010
A8010,BATCH,2,3,2,8011
Alarms
A9000,ALM_MENU,2,,3,9010,9011,9021,9012
A9010,ALM_HIST,2,,2
A9020,MESSAGE,2,,3
Dialog Agent
A100000,DIALOG,,,4
Signature Agent
A200000,SIGN,,,5
HA029280 Chapter 5
5.7.2 Editing the _default.pnl file
In order to change the architecture (layout) of the menu system the _default.pnl file is edited.
For instance, for any one menu, it is possible to change:

1 its title and any other legends
2 which screen area it occupies (E.G. status area, Main pane, or pop-up menu)
3 which sub-menus it generates.
Note: It is possible to create a system that is un-navigable and unworkable. For instance, it is possible,
inadvertently, to create a system which generates no panel display, and which therefore offers no means of
recovery.
Chapter 5 HA029280
5.7.3 Line types
Please read the following in conjunction with the foregoing listings.
There are several distinct line types, each identified by its first character:
1 Panel Agent declaration, beginning with ‘A’
2 Panel Driver declaration, beginning with ‘D’
3 Home and Root page definitions, beginning with ‘H’ and ‘R’ respectively.
4 Initial page definition, beginning with ‘I’
5 Comment lines, beginning with a ‘space’ character.
Notes:
1. The system will ignore anything it cannot interpret, rather than crash or hang up.
2. The _default.pnl file is a CSV file with lines terminated by either LF or CR-LF.
3. The character ‘\’ placed at the end of a line combines two lines into one ‘logical line’. Repeated use will
combine several displayed or printed lines into one logical line. If logical lines are more than 255 charac-
ters long, the 255th character is overwritten by subsequent characters.
4. Line types may appear in any order.
5. Lines beginning with any other character other than A, D, H or R are ignored, effectively making them
comments.
6. The Comment line type is self-explanatory; explanations of the other line types follow.
PANEL AGENT DECLARATION
Syntax: A<Id>,<Type>,<Access>,<WrAccess>,<Pane>,<Specifics>
where all parameters beyond <Type> are optional.
PARAMETER MEANING
<Id> is the Agent Id, specified as a decimal number from 1000 to 232 - 1.
(or hex, if preceded by ‘X’). Ids 1-999 are reserved for user pages defined in the user screen
(OFL) file.
<Type> is a mnemonic for the panel agent type. For example, MENU, ALM_HIST, and so on. These
are listed later.
<Access> gives the security level required for entry to this agent, and is a digit from 1 to 4. The default is
1.
<WrAccess> gives the security level for ‘Write access’ within this agent. The precise interpretation of this is
agent-specific. The default is <Access>.
<Pane> is the pane in which the agent is to operate, specified as a digit from 1 to 4 as follows:
1 = Status Pane
2 = Main Pane
3 = Popup Pane
4 = Dialogue Pane.
If this parameter is omitted, then the Main Pane is selected by default.
Only the Dialog agent operates in the Dialogue pane.
(Continued)
HA029280 Chapter 5
5.7.3 LINE TYPES (Cont.)
PANEL AGENT DECLARATION (Cont.)
Example: A9010,ALM_HIST,2, ,2
Any further parameters are agent-specific in meaning. They must be comma separated, and each must be one of the
following types:
1 Positive decimal number from 0 to 232 - 1

2 Hex number, preceded by ‘X’, with up to 8 digits
3 String, within double-quotes
4 Dictionary string, using the format #S123, where S (for example) is the dictionary identifier and 123 (for exam-
ple) is the index number. See the User Screen Editor Handbook for more information.
For example, for a Menu agent, the first two specific arguments are the title and legend respectively, which may be
specified as either strings or dictionary strings. Most other panel agents supply their own title and legend, which may
be customised if necessary by modifying the system dictionary.
Parameter specifics are:
PANEL AGENT PARAMETERS

MENU Ids for the agents accessed in this menu
SPP Id for the associated SPP_MENU
SPP_MENU Id for the associated SPP
ALM_MENU Id for the associated ALM_HIST
APP_MGR: Bit-encoding* for displayed keys (buttons)
(A) Application system 1 UNLOAD
2 SAVE
4 SAVE AS
8 STOP/START
(B) Bare system 1 LOAD
2 LOAD AND RUN
4 DELETE
Example of a Menu Agent, using parameters to specify the agents to be accessed from the menu:
A1000,MENU, , ,3, , ,4000,2000,9000,3000,5000,1
* The bit-encoding in the table above for the Application panel version, refers to the last parameter in the line
A2210,APP_MGR,4, , ,0 in the corresponding listing.
PANEL DRIVER DECLARATION

Syntax: D<Id>,<Type>[,<Specifics>]
where
<Id> is the driver identity. In a single driver system, this has no real significance.
<Type> is the mnemonic for the panel driver type. Currently the only type supported is QVGA.
Example: D1,QVGA
where the ‘1’ in D1 is just an identifier for the driver, even if there is only one installed.
Currently there are no parameters for driver declarations.
Chapter 5 HA029280
5.7.3 LINE TYPES (Cont.)
HOME PAGE DECLARATION
Syntax: H<Id>
Example: H1
This defines the Home agent (the one active after power-up, or after a HOME timeout, which generates the Home
page) If there is no Home declaration, it will default to the agent of numerically-lowest Id in the Main pane.
ROOT PAGE DECLARATION
The Root page is displayed when the Pop-up menu key is pressed, and it usually consists of a menu.
Syntax: R<Id>
Example: R1000
This defines the Root agent.
With no Root declaration, it will default to the lowest Id in the Pop-up pane. If there are no pop-up agents then it will
be set equal to the Home agent.
INITIAL PAGE DECLARATION
The Initial page is displayed on start-up only. It offers the opportunity to have an introductory page that’s different
from the Home page.
Syntax I<Id>
Example: I1000
This defines the Initial agent.
HA029280 Chapter 5
5.7.4 Agent types
Table 5.7.4a sets out the types of agents used.
The Entry points column gives the number of entry points to each of the listed agents, and the number of IDs allocated
will be the number in this column, starting at the specified ID. This should be born in mind when assigning Ids to
agents, in order to avoid conflicts. Table 1.3.1b give details of those parameters with multiple entry points.
For each agent, the third column (headed ‘Invalid’) indicates under what circumstances, if any, the agent is not avail-
able. ‘A’ indicates that the agent is not available within an Application panel, and ‘B’ indicates that it is not available
within a Bare panel.
MNEMONIC ENTRY INVALID DESCRIPTION

POINTS
ACCESS 1 Security access
AGP 1 B Overview displays
ALM_HIST 2 B Alarm History/Summary
ALM_MENU 1 B Alarm Menu
APP_SUM 1 B Application summary
BAT_MENU 1 B Batch menu
BATCH 2 B See table 5.8
CLOCK 1 Real time clock maintenance
CLONE 1 ISE cloning utilities
COMMS 1 Communications setup
DIALOG 1 Dialogue box manager
FB_MGR 1 B Function Block Manager
FILE_MGR 1 A File Manager
INTERNAT 1 Internationalisation
LOGGING 4 B Logging control and monitoring
MENU 1 General purpose menu
MESSAGE 2 B See table 5.8
NET_AUDIT 1 Network Audit Trail Configuration
PANEL 1 Panel parameters, e.g. brightness
RCP_MENU 1 B Recipe menu
RECIPE 4 B See table 5.8
RESOURCES 1 A System resources allocation
SIGN 1 Electronic Signatures manager
SOFT_OPT 1 A Software options
SPP 7 B Setpoint Programmer
SPP_MENU 1 B Setpoint Programmer Menu
STARTUP 1 Startup strategy definition
SYS_SUM 1 System summary
Table 5.7.4a Agent types
Chapter 5 HA029280
5.7.4 AGENT TYPES (Cont.)
The second column in Table 5.7.4a, on the previous page, shows that some agents have more than one entry point.
The parameter values to invoke the respective sub-menus are as follows:
AGENT VALUE FACILITY
ALM_HIST 0 Alarm history

1 Alarm summary
2 Event Log
BATCH 0 Batch load/start
1 Batch status
LOGGING 0 Monitor
2 Archive Management
3 Groups
4 FTP
MESSAGE 0 All messages on view
1 Single message on view.
RECIPE 0 Recipe selection
1 Recipe status
2 Recipe Monitor
3 Recipe editor
SPP 0 Monitor
1 Programs
2 Schedule
3 Preplot
4 Edit
5 Preview
6 Run From
Table 5.7.4b Agent sub menus (for entry points >1)
HA029280 Chapter 5
5.8 DATABASE NAMES
The LIN database within any Visual Supervisor consists of a number of function blocks, some of which are set by
Instrument manufacturer and are common to all Visual Supervisors, and some of which (function block names, alarm
names and Enumerations) are specified by the user for the process to be controlled.
Function block names are open to change using LINtools, either by customers or by OEMs.
Enumerations are also editable, but not via LinTools (see section 5.8.3).
These three types of names/text items are held in Database Names files, called .uyn files. These files are optional, but
where they exist there will be one per database (application). They take the name <appname>.uyn.
5.8.1 Function block names
Function block names are displayed in two facilities - Alarm History and Logging Groups - and in addition are used in
logging files, where they are stored as ASCII.
The syntax for replacing an existing function block name is:

<Block Alias>,<Block Name>
where ‘Block Alias’ is the replacement text and ‘Block Name’ is the original LIN database name for the block.
For example: First Loop,Lp1 replaces the LIN database name ‘ Lp1’ with the new name ‘First Loop’ .
Note: The maximum number of characters for block aliases is eight for the small frame (1/4 VGA) unit and
16 for the large frame (XGA) unit.
5.8.2 Alarm names
These are displayed in the Alarm History page.

Syntax:
<Alarm Alias>,<Block Name>.Alarms.<Alarm Name> where ‘Alarm Alias’ is the replacement text and ‘Alarm
Name’ is the original LIN database name for the block.
For example: Battery,Root.Alarms.BadBat replaces the current name (text) ‘BadBat’ with the new name (text) ‘Bat-
tery’.
Note: The maximum number of characters for alarm aliases is seven for the small frame (1/4 VGA) unit and
16 for the large frame (XGA) unit (although only the first eight characters appear in the alarm pane - see
section 2.6 for alarm pane details).
Chapter 5 HA029280
5.8.3 Enumerations
Enumerations are nearly always Boolean two-state variables, such as TRUE/FALSE and OPEN/CLOSED. They are
displayed as part of the Programmer graphical facilities (PREVIEW, PREPLOT, and EDIT), and are also used in log-
ging files.
There are two types:
1 Syntax:
,<Block Name>.<Block Field>, “<Alias>,<Alias>”
For example: ,digital.Out,“OPEN,CLOSED”
This replaces the existing enumerations in block.field ‘digital.out’ with the new enumerations OPEN,CLOSED.
2 Syntax:
,<Block Name>.<Block Field>.<Block SubField>, “<Alias>,<Alias>”
For example: ,digital.Out.Bit1,“OPEN,CLOSED”
This replaces the existing enumerations in block.field.subfield ‘digital.out.bit1’ with the new enumerations
OPEN,CLOSED.
TAGS
Individual function block fields may be tagged, so that whenever a modification to the block is made from the touch
screen, the modification is recorded in Event History.
Syntax:
<Field Tag>,<Block Name>.<Field Name>.<Bit number>
where field tag is the name that is used to identify the value when changed.
For example: LowTemp,PID.SL.Bit0
Note: the maximum number of characters that may be used for a for a field tag is eight for small frame (1/
4VGA) units and sixteen for large frame (XGA) units.
HA029280 Chapter 5
5.9 FORM FILES
The instrument uses two types of form file to configure output to printers, one for the generation of reports, the other
for custom formatting of alarms (e.g. text colour change).
5.9.1 Report forms
An application containing DR_REPRT blocks will reference report (.UYF) files which feature:
Customised layout of information
Detailed control of the formatting of data items
Text (optionally internationalised)
LIN database variables
System variables – e.g. current date and time.
An example of a .UYF file is given in figure 5.9.1. The various highlighted items are discussed below.
Literal Text Lin database Total no of characters

Size
Directive variable No of decimal places
New Line
*I3
"Temperature : ",[pid1.pv]:6.3,"$NPressure :"
[pid2.pv]:6.2,"$N"
[pid1.pv]>=30.0<=90.0{Cold,OK,Hot},"$N",_TIME:8,"$,",_DATE:8,"$N"
Limit values Limit text Text comma

System variable
Figure 5.9.1 Sample .UYF file
Chapter 5 HA029280
5.9.1 REPORT FORMS (Cont.)
UYF FILE ENTRIES
The UYF file contains identification information (directive), followed by a list of those items (text and variables)
which are to be included in the report. These items must be separated by commas, OR by New Line, Line feed or
Carriage return instructions.
Rules
1. No line is to include more than 255 characters (not counting commas, linefeeds etc.)
2. No spaces or tabs may be included between items (although they may be included in text strings for formatting
purposes.
Directive The form identifier used to attach a number to the report for reference via function blocks.
Different reports can be included in one .UYF file by preceding them with different Directives.
The directive must precede the list of displayed items, and must occupy a line of its own. The
syntax is *I<number>, where <number> is an integer between 1 and 999 inclusive. No spaces
are allowed.
Literal Text Enclosed within double quotes, literal text is printed out as typed in. Special characters may
be included as shown in table 5.9.1a, below. Any ASCII character can be included by typing
$nn, where nn is the hex code for the required character.
If a colon followed by a number is included immediately after the text, then this will define the
width of the field. E.G. “temperature =”:20 would produce the text ‘temperature =’ followed
by seven spaces. Text is left justified, unless otherwise specified, as described below in
‘Formatting attributes’.
Entry Definition Hex

$L or $N Line feed/new line 0A
$P Form feed 0C
$R Carriage Return 0D
$T Horizontal tab 09
$" or "" Double quotes 22
$$ Dollar symbol 24
$, Comma 2C
${ Open curly bracket 7B
Note: See Appendix C for
$} Close curly bracket 7D
ASCII Unicode Latin-1 charac-
$nn ASCII character nn nn ter set codes
Table 5.9.1a Special characters
Dictionary text Any item from any of the dictionaries described in section 5 can be included in the report. The
syntax is #<dictionary ID><entry number>, where the dictionary ID is as follows:
Error Text dictionary ID = E
Event Text dictionary ID = V
Programmer Text dictionary ID = P
System dictionary ID = S
User Text dictionary ID = U
Thus, an entry of #U13 would cause item 13 of the User dictionary to be included in the
report.
HA029280 Chapter 5
UYF FILE ENTRIES (Cont.)
Lin database variables These variables consist of the block name, the field name and (if appropriate, the sub-field
name. When included in the UYF file, these variables must be enclosed within square brack-
ets e.g. [pid2.PV], and must be followed by a colon, then size information, giving the number
of characters to be displayed.
Total number of characters This gives the total number of characters (including any decimal point) to be displayed, with
leading zeros suppressed. Values are right justified unless otherwise specified as described
below in ‘Formatting attributes’.
Number of decimal places. If the total number of characters figure is followed by a full stop and a second number, then
this second number will be the number of decimal places. For example, and entry of 6.1
means that the number format is xxxx.x, or an entry of 6.5 results in a format of .xxxxx
New Line “$N” Causes the following items to appear on a new line. For some types of printer, a carriage
return ($R) may also be needed.
Limit values/Limit text As shown in figure 5.9.1a, it is possible for a status line to be printed out according to the
value of the variable. In the example given, the entry :
[PID1.pv]>=30.0<=90.0 {Cold,OK,Hot}
means that if the value of PID1 is 30.0 or more, but less than or equal to 90.0, the word ‘OK’
is printed. If the value is below 30.0 the word ‘Cold’ is printed, and if the value is above 90.0,
the word ‘Hot’ is printed.
It is possible to use alarm limits as the limit values, and also to use dictionary entries for the
limit text e.g.
[PID1.PV]>=[Pid.LL_SP]<=[PID1.HL_SP]{#U10,#U11,#U14}
would print the text string held in item 11 of the User dictionary if the value of PID1 lies
between the limits. If the value lies below the lower limit, the message held in U10 is printed,
and if the value lies above the upper limit, the text held in U14 is printed.
For Boolean variables, which are either false or true, the format is: [Variable]{,false text,true
text}. For example, [Pid7.mode]{,,Manual} would cause the word Manual to be printed when
[Pid7.mode] becomes ‘True’, but nothing will be printed when the value becomes ‘False’.
System variables System variables (some of which are listed in table 5.9.1b) can be used to include system
information in the report. In the example of Figure 5.9.1a, the items _TIME and _DATE are
included to cause the system time and date to be included in the report. As with other vari-
ables, a suitable size must be allocated to the items, for formatting purposes. See the User
Screen Editor handbook (HA260749U005) for a complete list.
_ALM_ACT Number of currently active alarms (integer)

_DATE Current date, in appropriately internationalised format (string)
_RCP_NAME Name of current recipe (string)
_SPP_NAME Name of current program (string)
_TIME Current time (string)
_USER_NAME Name of user curently logged on (string)
Table 5.9.1b System variables
Chapter 5 HA029280
UYF FILE ENTRIES (Cont.)
FORMATTING ATTRIBUTES
Any one letter from each of the following groups of formatting codes that are applicable to a particular variable can be
appended:
1. Enter C, L or R to format the associated value as centred, left justified or right justified respectively.
(Text defaults to Left justified (L); Numeric values default to right justified (R).)
2. Enter Z to include leading or trailing zeros
3. For REAL variables: enter S to display the value in scientific notation (e.g. 1.23E-3)
4. For INTEGER variables, one of the following may be chosen:
X = Display values in hexadecimal format using capital A to F
x = Display values in hexadecimal format using lower case a to f
Y = Display values in binary format
For examples: If the value of the block ‘PID1.options’ is 42, then:

[Pid1.options]:8YZ prints 42 as an 8-bit binary value with leading zeros: 00101010,
[Pid1.options]:8XZ prints 42 as 0000002A, and
[Pid1.options]:4xL prints 42 as 2a◊◊ (where ◊ represents a space).
If the value of the block ‘PID1.options’ is 42.0 then:
[Pid1.options]:8S prints 42 as ◊◊◊4.2E1 (where ◊ represents a space).
BARGRAPHS
Simple bargraphs, consisting of a horizontal line of asterisks, can be included in the report, by the entry of scale low
and high values and the adding of the letter B after the width character, For example, if the (user entered) scale is 0 to
50, and the width is 20, then a value of 0 is represented by zero asterisks, and a value of 50 is represented by 20 aster-
isks. Thus, for this example, each asterisk represents 20/50 or 0.4 of the scale. If the value is not a whole number of
asterisks, then ‘rounding’ is applied.
Thus, a value of 42 would be represented by 42 x 0.4 = 16.8 = 17 asterisks, but a value of 41, (41 x 0.4 = 16.4) would
be represented by 16 asterisks. The 17th asterisk would ‘turn on’ when the process value reached 41.5
The following entry, includes literal text entries to show the low and high scale values:
“0 [“,[Loop1.PV]>=0<=50:20B,”] 50” . For a value of 42, this produces the following printout:
0 [***************** ] 50
FURTHER INFORMATION
1 Variables of type ENUM are printed textually even in the absence of an enumeration list, using the text defined
within LIN. If an enumeration list is included, then all the desired strings must be included. Empty or Over
range valued do not default to the LIN strings.
2 Alarm subfields (e.g. [PID1.ALARMS.HIGHABS] behave as integers taking values 0 to 3:
0 = Alarm not active, Alarm not unacknowledged
1 = Alarm active and acknowledged
2 = Alarm no longer active, but remains unacknowledged
3 = Alarm active but not acknowledged.
If the entire field is specified (e.g. [PID1.ALARMS], a bitwise OR of all alarms is performed.
Note: The subfield ‘Combined’ ‘is also accessible. This is derived from the individual alarms using a differ-
ent algorithm.
3 It is mandatory to supply size information for all variables except when an enumeration list has been given, in
which case, the width defaults to that of the longest string.
HA029280 Chapter 5
5.9.2 Alarm forms

Note: Ensure correct operation of each customised IDs, as any error in the ID will not be reported as an alarm
in the LPTDEV block.
For any application with printer support, there can be an optional alarm message formatting form (.UYT) file. The
file syntax is similar to the .UYF file described in section 5.9.1 above, to which reference should be made if neces-
sary.
.UYT files are used to customise the way in which alarm and Event messages are printed in reports. These messages
are invoked, when certain actions occur within the instrument. Each alarm or event has an identifier assigned to it so
that the correct type of message can be selected.
The various identifiers are listed in table 5.9.2a, along with their applicability to various system variables which can
be included in the report. These system variables are listed in table 5.9.2b In the case where a system variable is
inapplicable, a blank is displayed.
Applicable to
ID Invoked on
_A_BLOCK _A_DATE _A_NAME _A_PRI _A_TIME _A_TYPE
1001 Alarm active Y Y N Y Y Y
1002 Alarm cleared Y Y N Y Y Y
1003 Alarm acknowledged Y Y N Y Y Y
1004 Block event Y Y N Y Y Y
1005 Block event with name Y Y Y Y Y Y
1006 System event N Y N Y Y Y
1007 System event with name N Y Y Y Y Y
1008 Operator note N Y Y Y Y N
Table 5.9.2a Alarm type identifiers
System variable Definition

_A_BLOCK The name of the associated function block
_A_DATE The date associated with the queue entry
_A_NAME A name associated with an event (e.g. SPP program name)
_A_PRI The priority asigned to the alarm or event
_A_TIME The time associated with the queue entry
_A_TYPE The alarm or event type
Table 5.9.2b Alarm system variables
EXAMPLE
The figures below show an example of a .UYT file and a typical resulting appearance in the report, respectively.
*I1001
_A_DATE:8," ",_A_TIME:8," "
_A_BLOCK:8R,"/",_A_TYPE:8L,"ACTIVE ("'_A_PRI:1,")$R$L"
*I1002
_A_DATE:8," ",_A_TIME:8," "
_A_BLOCK:8R,"/",_A_TYPE:8L,"Cleared$R$L"
Sample UYT file
23/01/07 10:07:08 Loop1/HighAbs ACTIVE (7)

23/01/07 10:13:22 Loop1/HighAbs Cleared
Typical .UYT file printout
Chapter 5 HA029280
5.10 RECIPE FILES
For instruments supporting Recipes, it is possible to create Recipe files (.UYR) on a PC, using a text editor or
spreadsheet that supports Comma separated variable (CSV) format files.
Each .UYR file consists of three parts. The first part is a 3-line header which describes, in a fixed format, the general
information contained in the file. The second part consists of a single ‘Title Line’. The final part consists of a
number of lines, each describing a single variable
Notes:
1. No line may exceed 512 characters, including line feed/carriage return instructions.
2. Spaces are counted as characters
3. String titles do not have to be unique
4. Trailing commas will be treated as illegal unless otherwise stated.
5. If a string length is exceeded, any ‘extra’ characters are lost when saving the file.
6. Commas, double quotes (“), single quotes (‘) and equals signs are all illegal in fields.
7. Non-printing characters (excluding <CR> and <LF>) are not permitted anywhere within the file
5.10.1 Basic Recipe File
FILE HEADER
Line 1
Line 1 must contain UYR,1 only
Line 2
Line two contains comma separated information about the current revision of the file e.g.
2,10/04/06,09:37:08,Fred Bloggs
Where
‘2’ is the revision level of the file
‘10/04/06’ is the day/month/year that revision was carried out
‘09:37:08’ is the hours:minutes:seconds that the revision was carried out.
‘Fred Bloggs’ is the name of the person who last modified the file.
Line 3
Line three defines the recipe set block to be used and recipe download timeout value, in seconds.
<Recipe Set Block>,<Timeout>
e.g. SET1,30
The recipe Set Block is the name of the RCP_SET block to be used. If left blank, this field implies any RCP_SET
block.
If the download timeout is exceeded, the recipe download is assumed to have been unsuccessful, and the recipe goes
into a failed state
HA029280 Chapter 5
5.10.1 BASIC RECIPE FILE (Cont.)
TITLE LINE
This line defines how many recipes there are in the file, (minimum = one):
,Setpoint:<Line Name>,<Recipe 1 Name>,-,-,-,<Recipe N name>
where:
<Line name> defines the name of the recipe line (not required for single line files)
<Recipe N name> is the name of the Nth recipe.
VARIABLE LINES
For each variable in the recipe, a line is required of the form:
<Name>,<Tag>,<Value 1>,-,-,<Value N>
where:
<Name> is the name of the variable
<Tag> is the tag name in the database. If the tag name is enclosed within braces ({}), the variable is considered to be
non-verifiable
<Value N> is the value of the Nth recipe. The number of values must correspond with the number of recipes.
BASIC FILE EXAMPLE

Figure 5.10.1 is an example of a basic UYR file with three recipes.
UYR,1
6,10/04/06,08:45:54,Richard
,30
,Setpoint:1,Amarillo,Gulf Coast,Ekofisk
Methane,GasConc.Methane,90.67241,96.52220,85.90631
Nitrogen,CasConc.Nitrogen,3.128400,0.2595000,1.006800
Carbon dioxide,GasConc.CrbDiOx,0.4676001,0.5956001,1.495400
Ethane,GasConc.Ethane,4.527901,1.818600,8.491899
Propane,GasConc.Propane,0.8280000,0.4596000,2.301500
Water,GasConc.Water,0.000000,0.000000,0.000000
Hydrogen Sulphid,GasConc.Hsulphid,0.000000,0.000000,0.000000
Hydrogen,GasConc.Hydrogen,0.000000,0.000000,0.000000
Carbon Monoxide,GasConc.CrbMonOx,0.000000,0.000000,0.000000
Oxygen,GasConc.Oxygen,0.000000,0.000000,0.000000
i Butane,GasConc.iButane,0.1037000,0.09770000,0.3846000
n Butane,GasConc.nButane,0.1563000,0.1007000,0.3506000
i Pentane,GasConc.iPentane,0.032100,0.0473000,0.0509000
n Pentane,GasConc.nPentane,0.0443000,0.0324000,0.0480000
n Hexane,GasConc.nHexane,0.393000,0.0664000,0.0000000
Figure 5.10.1 Basic file example
Chapter 5 HA029280
5.10.2 More complex files
MULTI-LINE FILES
Figure 5.10.2a, below shows a 2-line version of the basic file described above. The differences are:
In the Title line, field number 2 is included and the lines have been named.
In each variable line, a second field (GasConc2) is included. For the sake of consistency, GasConc has been changed
to GasConc1.
UYR,1
7,10/04/06,08:49:21,Richard
,30
,Setpoint:Line 1,Setpoint:Line 2,Amarillo,Gulf Coast,Ekofisk
Methane,GasConc1.Methane,GasConc2.Methane,90.67241,96.52220,85.90631
Nitrogen,GasConc1.Nitrogen,GasConc2.Nitrogen,3.128400,0.2595000,1.006800
Carbon dioxide,GasConc1.CrbDiOx,GasConc2.CrbDiOx,0.4676001,0.5956001,1.495400
Ethane,GasConc1.Ethane,GasConc2.Ethane,4.527901,1.818600,8.491899
Propane,GasConc1.Propane,GasConc2.Propane,0.8280000,0.4596000,2.301500
Water,GasConc1.Water,GasConc2.Water,0.000000,0.000000,0.000000
Hydrogen Sulphid,GasConc1.Hsulphid,GasConc2.Hsulphid,0.000000,0.000000,0.000000
Hydrogen,GasConc1.Hydrogen,GasConc2.Hydrogen,0.000000,0.000000,0.000000
Carbon Monoxide,GasConc1.CrbMonOx,GasConc2.CrbMonOx,0.000000,0.000000,0.000000
Oxygen,GasConc1.Oxygen,GasConc2.Oxygen,0.000000,0.000000,0.000000
i Butane,GasConc1.iButane,GasConc2.iButane,0.1037000,0.09770000,0.3846000
n Butane,GasConc1.nButane,GasConc2.nButane,0.1563000,0.1007000,0.3506000
i Pentane,GasConc1.iPentane,GasConc2.iPentane,0.032100,0.0473000,0.0509000
n Pentane,GasConc1.nPentane,GasConc2.nPentane,0.0443000,0.0324000,0.0480000
n Hexane,GasConc1.nHexane,GasConc2.nHexane,0.393000,0.0664000,0.0000000
Figure 5.10.2a Multi-line file example
FILES WITH OPTIONAL CAPTURE VARIABLES
To generate a recipe file with separate capture points, then for each recipe line there must be an additional field after
each column in the title line and for each variable. The title line entry should be an item called “Capture”, and the
field for the variable is the tag of the field to be captured. This field may be left blank if no capture value is to be
specified.
Figure 5.10.2b shows the 2-line file of figure 5.10.2a, with capture variable on the first two variables.
UYR,1
7,10/04/06,08:59:02,Richard
,30
,Setpoint:Line 1,Capture,Setpoint:Line 2,Capture,Amarillo,Gulf Coast,Ekofisk
Methane,GasConc1.Methane,loop11.pv,GasConc2.Methane,loop21.pv,90.67241,96.52220,85.90631
Nitrogen,GasConc1.Nitrogen,loop12.pv,GasConc2.Nitrogen,loop22.pv,3.128400,0.2595000,1.006800
Carbon dioxide,GasConc1.CrbDiOx,GasConc2.CrbDiOx,0.4676001,0.5956001,1.495400
Ethane,GasConc1.Ethane,GasConc2.Ethane,4.527901,1.818600,8.491899
Propane,GasConc1.Propane,GasConc2.Propane,0.8280000,0.4596000,2.301500
Water,GasConc1.Water,GasConc2.Water,0.000000,0.000000,0.000000
Hydrogen Sulphid,GasConc1.Hsulphid,GasConc2.Hsulphid,0.000000,0.000000,0.000000
Hydrogen,GasConc1.Hydrogen,GasConc2.Hydrogen,0.000000,0.000000,0.000000
Carbon Monoxide,GasConc1.CrbMonOx,GasConc2.CrbMonOx,0.000000,0.000000,0.000000
Oxygen,GasConc1.Oxygen,GasConc2.Oxygen,0.000000,0.000000,0.000000
i Butane,GasConc1.iButane,GasConc2.iButane,0.1037000,0.09770000,0.3846000
n Butane,GasConc1.nButane,GasConc2.nButane,0.1563000,0.1007000,0.3506000
i Pentane,GasConc1.iPentane,GasConc2.iPentane,0.032100,0.0473000,0.0509000
n Pentane,GasConc1.nPentane,GasConc2.nPentane,0.0443000,0.0324000,0.0480000
n Hexane,GasConc1.nHexane,GasConc2.nHexane,0.393000,0.0664000,0.0000000
Figure 5.10.2b UYR file example with Capture Variables
HA029280 Chapter 5
5.10.2 MORE COMPLEX FILES (Cont.)
FILES WITH OPTIONAL MONITOR VARIABLES
To generate a recipe file with monitor points for each recipe line, an additional field must be included after each col-
umn in the title line, and for each variable. The title line entry should be an item called “Monitor”. The field for the
variable is the tag of the field to be monitored. Monitor fields must be placed after capture fields (if any).
Figure 5.10.2c shows a single-line file with monitor and capture points. See section 3.7.2 for details of Capture and
Monitor
UYR,1
9,10/04/06,09:00:24,Richard
,30
,Setpoint:1,Capture,Monitor,Amarillo,Gulf Coast,Ekofisk
Methane,GasConc.Methane,GasConc.Methane,GasConc.Methane,90.67241,96.52220,85.90631
Nitrogen,CasConc.Nitrogen,CasConc.Nitrogen,CasConc.Nitrogen,3.128400,0.2595000,1.006800
Carbon dioxide,GasConc.CrbDiOx,GasConc.CrbDiOx,GasConc.CrbDiOx,0.4676001,0.5956001,1.495400
Ethane,GasConc.Ethane,GasConc.Ethane,GasConc.Ethane,4.527901,1.818600,8.491899
Propane,GasConc.Propane,GasConc.Propane,GasConc.Propane,0.8280000,0.4596000,2.301500
Water,GasConc.Water,GasConc.Water,GasConc.Water,0.000000,0.000000,0.000000
Hydrogen Sulphid,GasConc.Hsulphid,GasConc.Hsulphid,GasConc.Hsulphid,0.000000,0.000000,0.000000
Hydrogen,GasConc.Hydrogen,GasConc.Hydrogen,GasConc.Hydrogen,0.000000,0.000000,0.000000
Carbon Monoxide,GasConc.CrbMonOx,GasConc.CrbMonOx,GasConc.CrbMonOx,0.000000,0.000000,0.000000
Oxygen,GasConc.Oxygen,GasConc.Oxygen,GasConc.Oxygen,0.000000,0.000000,0.000000
i Butane,GasConc.iButane,GasConc.iButane,GasConc.iButane,0.1037000,0.09770000,0.3846000
n Butane,GasConc.nButane,GasConc.nButane,GasConc.nButane,0.1563000,0.1007000,0.3506000
i Pentane,GasConc.iPentane,GasConc.iPentane,GasConc.iPentane,0.032100,0.0473000,0.0509000
n Pentane,GasConc.nPentane,GasConc.nPentane,GasConc.nPentane,0.0443000,0.0324000,0.0480000
n Hexane,GasConc.nHexane,GasConc.nHexane,GasConc.nHexane,0.393000,0.0664000,0.0000000
Figure 5.10.2c Single-line file with Monitor and capture.
5.11 WRITABLE DICTIONARY
The writable dictionary holds text that may be used for the batch system or in reports. This dictionary is different from
all other dictionaries in that it can be modified from the Batch screen or from a user screen. The values of these texts
may optionally be initialised from the _USER.UYL file described in section 5.5, above.
All values are preserved across power failure, but any values in the .UYL file will over-write those on power up. The
dictionary holds up to 120 records, each of up to 40 characters in length.
Chapter 5 HA029280
5.12 THE RECIPE DICTIONARY
The recipe dictionary holds text that originates from the recipe files (.uyr). It may not be initialised from a .uyl file.
The text held by this dictionary changes whenever .uyr files are loaded or modified from the front panel.
The dictionary is divided up into sections, one for each recipe set, each spanning a range of up to 1000 records.
The sections are allocated as follows :-

1001-1999, Recipe set number 1
Also the section 1-999 represents the recipe set currently on view and is thus a duplicate of one of the other sections.
The following table indicates how the records are allocated in each recipe set. To get the actual record, from recipe set
number n, simply add 1000*n. For example, to get the record of the user who last edited the recipe 3 .uyr file, use
record number 3014
Record Value
1 File name (excluding .uyr)
11 Revisions number of .uyr file
14 Name of user who last edited the .uyr file
15 Returns “YES” if the file has been edited but not saved or “NO” if not edited.
111 Name of line number 1
112 Name of recipe selected on line 1
113 Name of recipe active on line 1
114 State of recipe on line 1
121 to 124 As 111 to 114 but for line 2.
301 to 316 Names of recipes 1 to 16 respectively
401 to 480 Names of variable numbers 1 to 80 respectively
HA029280 Chapter 5
5.13 THE BATCH DICTIONARY
The batch dictionary holds text that originates from the batch files (.uyb) and any corresponding recipe files (.uyr). It
may not be initialised from a .uyl file. The text held by this dictionary changes whenever the .uyb and/or .uyr files are
loaded or modified from the front panel.
The dictionary is divided up into sections, one for each batch controller, each spanning a range of up to 1000 records.
The sections are allocated as follows :-
1001-1999, Batch number 1
Also the section 1-999 represents the batch currently on view and is thus a duplicate of one of the other sections.
The following table indicates how the records are allocated for each batch. To get the record from batch n, add
1000*n. For example, to get the record of the user who last edited the batch 3 .uyb file, use record number 3014
Record Value
1 File name (excluding .ubr)
11 Revisions number of .uyb file
14 Name of user who last edited the .uyb file
41 Custom title number 1
51 Custom variable number 1
91 State of the batch
92 Name of recipe selected for batch
93 Name of current phase
101 to 120 Names of phase numbers 1 to 20
301 to 316 Names of recipes 1 to 16
401 to 480 Names of recipe variable numbers 1 to 80
5.13.1 Example
If ‘#B1001’ is included in a form file (section 5.9) then the .uyb file name is included in the report.
Chapter 5 HA029280
5.14 BATCH FILES
For instruments supporting Batch, it is possible to create Batch files (.UYB) on a PC using a text editor or spreadsheet
that supports Comma separated variable (CSV) format files. Each .UYB file consists of 2 parts. The first part is a 6-
line header, which describes, in a fixed format, the general information contained in the file. The second part consists
of a number of phases of the batch.
Notes:
1. No line may exceed 512 characters, including line feed/carriage return instructions.
2. Spaces are counted as characters.
3. Trailing commas will be treated as illegal unless otherwise stated.
4. Commas, double quotes (“), single quotes (‘) and equals signs are all illegal in fields.
5. Non-printing characters (excluding <CR> and <LF>) are not permitted anywhere in the file.
5.14.1 File Header
The format of the 6-line header is:

Line 1
Line 1 must contain UYB,1 only
Line 2
Line 2 contains comma-separated information about the current revision of the file e.g. 2,10/04/06,09:51:16,Fred
Bloggs
Where: ‘2’ is the revision level of the file
‘10/04/06’ is the day/month/year that revision was carried out
’09:51:16’ is the hours:minutes:seconds that revision was carried out
‘Fred Bloggs’ is the name of the person who last modified the file.
Line 3
Line 3 defines the batch engine interface as
<BAT_CTRL>,<End Action>,<Timeout>,<Confirm level>,<BatchID Prefix>
e.g. BATCH1,0,60,2,ABC:R
Where
‘BATCH1’ is the name of the BAT_CTRL block to run the batch.
‘0’ defines the action on RESET,
0 Requires a reload,
1 Can be re-started without a reload.
‘60’ defines the timeout (in seconds) for state transitions
‘2’ defines the level of confirmation required when starting from the front panel.
0 No confirmation required,
1 OK/CANCEL dialogue box,
2 Required re-entry of password.
ABC:R is an optional batch id prefix of the form <Prefix>:R,
where Prefix overwrites the batch ID, from the left, with the characters of the prefix. For example, a
prefix of RKN, would result in batch IDs such as RKN00014.
:R, if added, makes the batch ID read only (i.e. it cannot be changed from the front panel.)
HA029280 Chapter 5
5.14.1 FILE HEADER (Cont.)
Line 4
Line 4 defines the display interface as
<User Screen>,<Display Group>,<Message Filter>,<User Item1>…<User Item6>
Where:
<User Screen> is the number of a user screen page associated with the batch or 0 is none.
<Display Group> is the (optional) name of a GROUP block to be associated with the batch (or blank if none).
<Message Filter> is the (optional) name of block to be used to give the context for message to be associated with
this batch, this may the name of the BAT_CTRL block itself or a GROUP block containing the
BAT_CTRL plus other blocks of interest.
<User Item> specifies a title and value to be displayed on the BATCH start screen. The value may be edited
prior to starting the batch. Each user item is of the form <Title>:<Value>:<Width>=<Initial
value>:<Attributes>
where
<Title> is a dictionary reference of the #<Dict><Index> e.g. #U12
<Value> is either a writeable dictionary value e.g. #W12 or else a LIN dB value e.g.
[PID.SL]
<Width> is the number of characters wide to display the value.
<Initial value> (optional) is the text value to be used to initialise a writeable dictionary entry
value. For example #U13 = user dictionary entry 13. The value may only be
another dictionary reference, and must be applied at load.
<Attributes> (optional). Can have one of the following:
W = Value must be written. This implies that data entry must occur after load.
If the batch is not unloaded, it may be run without re-writing this value.
M = Value must be modified from its initial value (for ‘W’ dictionary items
only) after load. If the batch is not unloaded, it may be run without re-writing
this value.
Line 5
Line 5 defines the batch log interface as: <LOGROUP>,<Filename>,<Report>
e.g. BAT_LOG,[BATCH1.Id],BAT_REPT
Where:
‘BAT_LOG’ is the (optional) name of a LGROUP block for the batch log
‘[BATCH1.Id]’ is an (optional) LIN database field whose text value is used as the first two characters of the
filename.
‘BAT_REPT’ is the (optional) name of a DR_REPRT block to be used to generate batch reports. If a batch
report is to be generated then 3 reports are required in the .UYF file (1: start, 2: stop, 3: abort).
The .UYF must be the same name as the .UYB, e.g. if using SAMPLE.UYB then the corre-
sponding .UYF is SAMPLE.UYF.
Line 6
Line 6 defines the recipe interface e.g.
LINE1
Where ‘LINE1’ is the name of BAT_LINE block used to parameterise the batch. If SAMPLE.UYB is used then the
corresponding recipe file will be SAMPLE.UYR.
5.14.2 Batch Phases

For each phase of the batch a line is required of the form:
<Name>
where: <Name> is the name of the phase.
Chapter 5 HA029280
5.15 DATABASE CHANGE AUDIT TRAILING
This facility allows for audit trailing of changes of values in the application. This is independent of the other facilities
which audit trail values in response to user interaction. This facility is aimed at values that change without user inter-
action. In order to configure this facility a file of <database name>.UYA must be created. This is a simple text file in 2
parts, a header line and then a single line for each value of interest.
5.15.1 Header Line
The header line is of the form:
UYA,1[,[<burst_threshold>][,[<back_off_period>][,[<dynamic_threshold]]]
The three optional numeric fields are as follows
Burst threshold The number of consecutive database cycles that a value has changed before a “burst” condition
is seen to have occurred. Once the burst condition occurs audit trailing will stop to prevent
over-filling the log until the value stabilises gain. Default value = 10
Back off period The number of consecutive database cycles that a value must remain unchanged before a burst
condition is considered to have cleared and normal audit trailing resumes. Default value = 10
Dynamic threshold The percentage (in integer multiples) of database cycles that a value must have changed before
a “dynamic” condition is seen to have occurred. Once the dynamic condition occurs audit
trailing will stop to prevent over-filling the log until the value stabilises gain. Default = 10
5.15.2 Item Lines
Item lines are of the form depicted below. Each line identifies a field name to be monitored.
<BlockName>.<FieldName>
HA029280 Chapter 5
Chapter 5 HA029280
CHAPTER 6: ADMINISTRATIVE FUNCTIONS

Notes:
1. Access to all functions described in his chapter require ADMIN privileges.
2. The functions described in this chapter apply only to instruments fitted with the 'Auditor' option.
The Administration menu is accessed by operating the menu key at the bottom right of the screen, followed by opera-
tions of SYSTEM and ADMIN keys
Administration
NET AUDIT SIGN CONFIG
6.1 NETWORK AUDIT TRAIL
This function allows the Audit trail (i.e. alarm and event logs) to be transmitted from the instrument (the 'Provider') to
up to three E suite systems (the 'Consumers'). Network Audit Trail is accessed from the Administration menu by op-
eration of the NET AUDIT key, as depicted in figure 6.1, below.
Administration
TREND Run prog 3/5

ADMIN EYCON-20 BADBAT
10:03:35 Network Audit Trail 10/04/06
Mode: PROVIDER
Destination node 1
LIN Node: 1 INIT
Alarm active : YES
Alarm cleared: YES
Alarm ack'ed : YES
Cached alarms : NO
System event: YES
Block event: YES
Operator note: YES
Block value change YES
Message active : YES
Message cleared: YES
Message ack'ed : YES
Min alarm priority: 1
Min event priority: 1
Destination node 2
LIN Node: 0 (Disabled)
Destination node 3
LIN Node: 0 (Disabled)
SAVE CANCEL
F1 F2 F3 F4 F5 F6 F7 F8 F9
F10 F11 F12 F13 F14 F15 F16 F17 F18
F19 F20 F21 F22 F23 F24 F25 F26 F27
Figure 6.1 Network Audit trail access.
HA029280 Chapter 6
6.1.1 Modes
The function can be programmed in the following ways:
1. Isolated. The instrument displays only its own alarms and events. Alarms and events are not transmitted to any
other node.
2. Provider. As ‘Isolated’, except that the unit can also transmit its alarms and events to up to three other Audit Trail
consumers.
3. Consumer. The instrument displays its own alarms and events, plus those of up to eight other Visual Supervisors.
Alarms and events are not transmitted to any other node. The node number of the provider is prefixed to the
relevant line(s) in Alarm and Event Logs (section 3.5.6) - local Alarms and Events are prefixed with space char-
acters.
6.1.2 Configuration (Provider)
Configuration is in two parts - selecting the E suite systems (the Consumers) to which the Audit Trail is to be trans-
mitted, and (if required) disabling one or more alarm or event types, so that only those items of interest are transmit-
ted.
CONSUMER SELECTION
From 'Provider' mode, enter the (decimal) node addresses of the E suite systems to which the Audit Trail is to be sent.
Once this has been done the SAVE key should be operated, and power removed from the instrument for a few sec-
onds, then reapplied.
AUDIT TRAIL FILTERING
Again, from 'Provider' mode, the various parameters associated with each node's Audit trail can be enabled (set to
'Yes') or disabled (set to 'No').
PARAMETERS
Lin Mode UNINIT No attempt is currently being made to establish communications with the
Consumer.
INIT Initialised, but no communications have taken place as yet
CONNECTED Initial communications have been established, but no Audit Trail files are being
transmitted.
ACTIVE The Audit Trail is being transferred to the Consumer.
Alarm active YES = include active alarms
Alarm Cleared YES = include cleared alarms
Alarm Ack'ed YES = include acknowledged alarms
Cached Alarms No = do not include cached alarms (see note below)
System Event YES = include system events
Block events YES = include block events
Operator note YES = include operator notes
Block Value Change YES = include events recording changes to block field values
Message active YES = include active messages
Message Cleared YES = include cleared messages
Message Ack'ed YES = include acknowledged messages
Min. alarm priority 1 to 15: Specifies minimum alarm priority for inclusion
Min. event priority 1 to 15: Specifies minimum event priority for inclusion
Note: ‘Cached alarms’ is normally set to ‘No’ to prevent cached blocks being sent to the consumer. (It is
usual for the Consumer to have cached these blocks itself.)
Chapter 6 HA029280
6.1.3 User ID control
The use of passwords and user IDs is more strictly controlled in an instrument fitted with the Auditor option, than in
instrument not so fitted (section 4.4, above). Access to User IDs and passwords etc. requires ADMIN permissions.
The major points to note are as follows:
1. It is not possible to edit a user's Identity, Name, Access Level or 'Attributes' once the SAVE key has been
pressed.
2. Once a password has been allocated, it can not be used again either by the original user or by a new user.
3. A Password expiry period, amongst other things, can be set in the 'Properties' menu. Once this period has ex-
pired, the relevant passwords will no longer be usable.
4. A new user's initial password has a 24 hour expiry period. Within this time the user must log in and enter a new
password. Once this is done, the new password will be allocated the expiry period set up in the Properties menu
(default 90 days).
5. A Password must include one non-alpha character (i.e. it must have at least one character which is not one of A to
Z or a to z.)
6. The password may not be the same as the User identity.
7. The 'Delete' key in the non audit-pack instrument is replaced by a 'Retire' key. When the Retire key is operated,
with a user selected, that user's name is removed (after confirmation) from the security access page. The details
are, however, stored within the instrument to ensure that the same ID/password etc. cannot be used more than
once.
SECURITY ACCESS DISPLAY PAGE

This page is called by touching the ACCESS key from the root menu, and entering the ADMIN Identity and Password
(both 'ADMIN' when despatched from the manufacturer). Once logged in as ADMIN, operation of the USERS key
calls the Security Access Display page, shown in figure 6.1.3a, below.
Note: For a more detailed description of how to access the ADMIN login, see section 4.4.3
TREND Run prog 3/5
ADMIN EYCON-20 BADBAT
RUNNING 13:07:45 2 TREND 2% 04-10:03
Identity Name Access Attributes Expires Reference
ADMIN ADMIN ADMIN 00000003 27/11/04 0

ADMIN2 ADMIN2 ADMIN 00000003 27/11/04 0
COMMISSI COMISSION COMMISSION 00000000 27/11/04 0
ENGINEER ENGINEER ENGINEER 00000003 27/11/04 0

OPERATOR OPERATOR OPERATOR 00000000 27/11/04 0
richard LinMan1 ENGINEER 00000003 27/11/04 0
SAVE CANCEL NEW PROPERTIES MAINT STATS REVISION DEPLOY
F1 F2 F3 F4 F5 F6 F7 F8 F9
F10 F11 F12 F13 F14 F15 F16 F17 F18
F19 F20 F21 F22 F23 F24 F25 F26 F27
Figure 6.1.3a Security Access Page
As can be seen from the figure, the page is divided into a number of columns. Name, Access and Reference columns
are all as described in section 4.4.3 above. Other columns are used as follows:
HA029280 Chapter 6
6.1.3 USER ID CONTROL (Cont.)
IDENTITY
Touching a users Identity 'cell' calls the 'Identity' pop-up to appear (figure 6.1.3b). This allows a new password to be
entered for the ID in the normal way. The new password has a 24 hour expiry, so the user has to login and provide a
further new password within this time period. The pop-up also allows IDs to be 'Retired' or ‘Disabled’.
richard:Identity
Password:
********
Confirm:
********
OK CANCEL RETIRE DISABLE
Figure 6.1.3b Identity pop-up
RETIRE
A 'retired' user is permanently removed from the Security Access page, and all access privileges are terminated. Re-
tired users' Identities, Names and passwords may not be reused. It is therefore recommended that a note is kept of all
Retired users' details.
DISABLE
Users who are disabled (Identity and Name in Red) lose their access privileges in a non-permanent way. To reinstate
a Disabled user, the Identity cell is touched, the User's password entered and confirmed, and 'OK' touched. If the pass-
word is correct, the User is 're-enabled', and is shown in the normal blue colour on the screen. The expiry date re-
mains as first set up for the user.
NAME
Operating this button calls the Name pop-up to the screen. For new users whose details have not yet been Saved, the
name can be edited. Otherwise, as shown in figure 6.1.3c, this is a View only function.
Name: LinMan1
OK CANCEL
Figure 6.1.3c Name pop-up
ATTRIBUTES
Touching a particular user's Attributes 'cell', calls the Attributes page. This is used to define the richard:Attributes
Identity: richard
users ability to 'sign' and 'authorise' changes, and to define whether the user can modify the Sign: YES
Authorise: YES
instruments operation. View Only: NO
Admin Only: NO
FTP: NO
The numbers which appear in the attributes column can be decoded as shown in table 6.1.3. Remote: NO
The values are additive, so if, for example, ‘Sign’ and ‘Authorise’ are both selected ‘Yes’, and OK CANCEL
all other fields are selected ‘No’, then the attributes value would be 00000003.
Sign Authorise View only Admin only FTP Remote Display

No No No No No No 00000000
Yes No No No No No 00000001
No Yes No No No No 00000002
No No Yes No No No 00000004
No No No Yes No No 00000010
No No No No Yes No 00001000
No No No No No Yes 00002000
Table 6.1.3 Attribute coding
Chapter 6 HA029280
6.1.3 USER ID CONTROL (Cont.)
EXPIRES
This column shows the expiry date for each Password, For each new user, the expiry date is 24 hours after the new
user details are Saved. The user must log on and change the password within 24 hours, or the Password will lapse.
The new password will have the Expiry period set in the Properties menu (described below) of the Security Access
Page.
SCREEN KEYS
SAVE CANCEL NEW PROPERTIES MAINT STATS REVISION DEPLOY
These keys are located near the bottom of the screen. The SAVE and CANCEL keys operate in the same way as de-
scribed in section 4.4.3, above.
NEW New User

Operating the NEW key calls the New User pop-up menu to the display. Identity:
Once the details have been entered, and 'OK' pressed, the new user Name:
appears in Green, on the screen. Access: OPERATOR
Password: ********
Note: Do not press SAVE until all other parameters (e.g.
attributes) have been configured for this user,. Once SAVED, Confirm: ********
only the password can be changed.
OK CANCEL
Configure the users Attributes, as described above, then press SAVE.
The user Identity and Name change to Blue, and the Password expiry Figure 6.1.3d New User screen
date appears as next day. If the user Password is to expire at any period
other than that set in the PROPERTIES menu (described below), this
should now be set.
ADMIN should now be logged out of, and the new user logged in and a
new password entered. Account Properties
Min User Id Length: 6
Min Password Length: 6
Max Login Attempts: 3
PROPERTIES
Password Expiry: 90 days
Similar to the Properties page described in section 4.4.3, this page,
depicted with default values in figure 6.1.3e, allows the login param- User Timeout: 60 minutes
eters to be set, as shown below..
OK CANCEL
Figure 6.1.3e Properties default values

Min User ID Length 3 to 8
Min Password Length 3 to 8 Passwords must have at least one non-alpha character.
Max Login attempts 1 to 99 The number of attempts at logging-in that may be made before the account is disabled.
Password Expiry 1 to 180 The password expires after the specified number of days have elapsed since the last
time the value was edited.
User Timeout 1 to 720 The user is logged out after the specified number of minutes has elapsed since previ-
ous screen activity.
HA029280 Chapter 6
6.1.3 SECURITY ACCESS PAGE (Cont.)
MAINTENANCE
Operating the ‘MAINT’ key at the bottom of the Security Access screen calls the ‘Account Maintenance’ screen to the
display, as depicted in figure 6.1.3f, below.
Account Maintenance
Recovery Account: YES
Master Access: YES
Edit Own Expired Password: YES
OK CANCEL
Figure 6.1.3f Maintenance screen
Recovery Account If recovery account is set to YES, this enables a recovery in the event of all ADMIN accounts
becoming unusable. This requires a maintenance contract with the manufacturer.
Master Access Setting Master Access to 'NO', means that the editing of Account systems is not possible.
Edit Own Expired Password If set to Yes, the user will be forced to change password when attempting to log in. If set to
‘No’, only a user with ADMIN permissions may enable a new pasword for a user whose
password has expired.
STATISTICS
Operating the STATS key at the bottom of the Security Access screen calls the ‘Statistics’ screen, as depicted in figure
6.1.3g, below.
Statistics
Users: 5/100
Retired Users: 1/200
OK
Figure 6.1.3g STATS window

This window shows:
1. How many users have been configured out of the total available. For example, Users: 6/100 means that six of
the 100 possible users have been configured.
2. How many users have been retired. For example, 1/200 means that 1 user has been retired, and that 199 further
users may be retired.
Note: Retiring the 201st user causes the 1st Retired user (by time/date) to be removed from the list. This
results in Event 20 (Purged user) being set. This user's data can now be re-used.
Chapter 6 HA029280
REVISION
Touching this key, calls the configuration revision page, as depicted in figure 6.1.3h, below.
Revision Information
Revision: 0
Operational Changes: 0
Revised On: 10/04/06 10:23:25
Revised By: (Fred)
Reason: FACTORY DEFAULTS
OK
Figure 6.1.3h Revision page
DEPLOY
A master access system can ‘deploy’ its own access system to other Visual Supervisors across its ELIN network.
This ‘Deployment’ is in three stages:
1. Select the number of nodes (initially 0)
2. Enter the node numbers to be deployed to.
3. Initiate the deployment.
The initial display page appears when the ‘DEPLOY’ key is first pressed (Figure 6.1.3i), and shows that the number
of nodes is zero.
10;24:13 Deploy Access 10/04/06
Number of slave nodes: 0
CONFIG USERS
Figure 6.1.3i Initial Deploy configuration page
Touching the CONFIG key, allows the number of nodes to be deployed-to, to be entered. The display shows one con-
figuration box each, for the number of nodes selected, to allow the required node numbers to be entered. Initially, all
these contain ‘0’, although this value cannot be used. (Figure 6.1.3 k.)
HA029280 Chapter 6
10:26:06 Deploy Access - Config 10/04/06
Slave nodes:
0 0 0 0 0
OK CLEAR FILL SORT
Figure 6.1.3j Node number configuration.
Operation of the FILL key at this point will fill the node number configuration boxes with nodes 1 to n, where n is the
number of nodes selected.
If, instead, the first node is entered by the user (say node 10), the FILL operation will automatically fill in the remain-
ing node numbers, (starting at 11 in this example).
If non-consecutive node numbers are entered, say nodes 17, 3, 9, 103 and 14, then the SORT button can be used to
reorder the nodes in ascending order (3, 9, 14, 17, 103).
The CLEAR key is used to reset all the mode numbers to ‘0’.
Operation of the OK key, returns to the previous page, only this time, the newly configured items appear.
10:27:48 Deploy Access 10/04/06
Slave nodes:
3 9 14 17 103
DEPLOY CONFIG USERS
Figure 6.1.3k Completed configuration
Operation of the DEPLOY key causes the deploy to be initiated, once signed and authorized if necessary. Figure
6.1.3l shows the confirmation page.
Chapter 6 HA029280
Deploy Access
Slave nodes:
3 9 14 17 103
Confirm Action: DEPLOY
Reason:
Signed by
Ident: ADMIN
Password ********
Authorised by
Ident:
Password:
********
OK CANCEL
Figure 6.1.3l Deploy confirmation page
HA029280 Chapter 6
6.2 ELECTRONIC SIGNATURES
6.2.1 Enabling electronic signatures

Note: Once Electronic signatures have been enabled, they can not subsequently be disabled.
As shipped, electronic signatures are disabled. The ‘Enable signatures’ Signature Configuration page (figure 6.2.1)
appears on the first operation of the SIGN CONFIG key in the Administration menu.
The only choices are to quit the page (by selecting another page using the menu key) or Enable electronic signatures.
Administration
10:29:28 Signature Configuration 10/04/06
The "ENABLE' button may be used to turn on electronic signatures. Once signatures have been
turned on and saved, they cannot be turned off again.
ENABLE
Figure 6.2.1 Enable Signatures page
When ‘Enable’ is operated, a dialogue box appears requiring two separate ADMIN passwords before the Signature
Configuration page (figure 6.2.2) appears.
Chapter 6 HA029280
6.2.2 Signature Configuration
Figure 6.2.2a shows the Signature Configuration page. The administrator IDs in ‘Revision Level’ are, initially the IDs
of the administrators who enabled the Electronic Signature feature. Subsequently the IDs are those of the administra-
tors who signed/authorized the previous Configuration Save.
10:31:29 Signature configuration 10/04/06
Revision: 1 10/04/06 10:31:25 ADMIN ADMIN2

Function: Security Access
SAVE: No Confirmation
Account Properties: Confirm only
Account Maintenance: Signature
User Password Change: Sign & Authorise
RETIRE: Action disabled
DISABLE: Sign & Authorise
ENABLE: Sign & Authorise
REINSTATE: Action Disabled
DEPLOY: Signature
SAVE CANCEL DEFAULTS
Figure 6.2.2a Signature Configuration page
ACCESS LEVELS
As can be seen from figure 6.2.2a, above, a number of instrument features can have an access level assigned to them.
The possible access level definitions are as follows:
No Confirmation The instrument behaves as if electronic signatures are turned off.

Confirm only A dialogue box with OK and CANCEL buttons appears, before the action is undertaken.
Signature A password entry by a user with Signature Permissions is required before the action is per-
formed.
Sign & Authorise A password entry by a user with Signature Permission and a further entry by a user with
authorization permission are required before the instrument will respond to the requested
action.
Action Disabled This causes the relevant button caption to be ‘greyed out’ thus becoming inaccessible to the
user. Thus the action may not be undertaken at all.
Note: Some functions cannot be allocated some access levels. Administrative functions, for example, always
require a minimum level of ‘Signature’, and some functions cannot be assigned ‘Action Disabled’.
The available functions are in a number of categories, a picklist of categories being displayed when the ‘Function’
field is touched. Figure 6.2.2b, below shows this picklist.
The button functions at the bottom of the page are as follows:
SAVE Saves all changes to all functions.

CANCEL Cancels all changes made since last SAVE or DEFAULT operation.
DEFAULT Returns the access levels to those when initially enabled.
HA029280 Chapter 6
6.2.2 SIGNATURE CONFIGURATION (Cont.)
Securityy Access
Security Access
Application
Setup
Cloning
File Manager
Administration
Alarms
Overview
Programmer
Recipe
Batch
Logging
Figure 6.2.2b Function picklist
Chapter 6 HA029280
CHAPTER 7: REMOTE ACCESS
The instrument provides a limited set of facilities which allow remote users to access the instruments.
7.1 FTP
7.1.1 FTP logon
FTP access always requires the user to log on. Anonymous FTP logons are not permitted. To configure the instru-
ment for FTP logon, the user-based access system (section 4.4.3) must be used, and the relevant user’s attributes con-
figured to include FTP = ‘Yes’.
The instrument allows up to four users to be logged in at any one time, but only one of these may have write permis-
sion (attribute View Only = ‘No’). This user’s log on/ log off activity is recorded in the Event Log. Users with View
Only = ‘Yes’ do not have their log on/log off activity recorded.
Notes:
1. Any attempt to log into a non FTP account, or into a nonexistent account will be recorded in the Event
log.
2. The mis-typing of FTP passwords is included in the count of ‘failed attempts to log in’ (section 4.4.3.2),
and therefore may result in the account being disqualified.
3. Attempts to login to non FTP accounts are not included in the count of ‘failed attempts to log in’.
TIMEOUT
FTP users are automatically logged out after 2 minutes of inactivity. This happens regardless of any values for user
timeout which have been set at the instrument user interface.
7.1.2 File system
The file system, as viewed via FTP, is seen as a simple set of folders, with the characteristics shown in table 7.1.2.
Notes:
1. It is not possible to access the USB bulk storage device via FTP.
2. It is not possible to create new folders via FTP.
FTP LIN Write

Description Visibility
Name device Permission
/app E: Internal flash memory for application files Yes If IPRP not enabled
/history H: Internal archive (if fitted) No If archive fitted
Table 7.1.2 File system
7.1.3 Archive File Transfer
If Review software or any other FTP client is used to transfer files from the internal archive to a PC, then it is recom-
mended
a. That the user account attribute configuration includes FTP = ‘Yes’ and View Only = ‘Yes’ and
b. The access level for this account be set to ‘Operator’
c. The account is used only for this purpose.
HA029280 Chapter 7
Chapter 7 HA029280
CHAPTER 8: THE CONTROL CONFIGURATOR
This chapter describes the control configurator resident in the unit. The main topics covered are:
1. Overview of the configurator
2. Getting ready to run the configurator
3. Running the configurator
4. Database configuration
5. Modbus Slave Gateway configuration
8.1 OVERVIEW
The resident control configurator allows a control strategy to be set up directly within a CPU, as an alternative to
downloading a configuration created in the LINtools package. The configurator can also be used to load, start, stop,
and monitor databases, and to perform various filing operations. Note that with heavily-loaded running databases the
configurator may be significantly slowed down.
Configurations employ the standard LIN block-structured approach. The LIN Product Manual (Part number
HA082375U999) gives full details of the software function blocks available for strategies, and how to configure their
parameters.
The configurator program itself resides in the instrument's CPU and is accessed via any telnet client program. The
choice of serial or telnet communications must first be made in the comms setup page (section 4.5), and the user ID
access system must be enabled and a user set up with ‘Remote’ attribute enabled (section 4.4.3).
8.2 PREPARATION
8.2.1 Configurator mode selection
Set the ENET5 port protocol to TERMCFG as described in section 4.5.1
8.2.2 Control efficiency selection
The configurator can be run at the same time that the database is running. However, this affects the control effi-
ciency, in a way that depends on how the Options.CONFspd bit in the control strategy’s header block has been set.
With CONFspd TRUE, the CPU is allowed to spend up to 30% of its time updating blocks in the control strategy, and
the rest is available for serving the front panel and configurator task if running. Thus, if CONFspd is set TRUE, the
control strategy will not respond at full speed but the configurator can be run as often as needed without affecting
performance.
With CONFspd FALSE (the default state), and the configurator not in use, the CPU can spend up to 40% of its time
updating blocks.
HA029280 Chapter 8
8.3 RUNNING THE CONFIGURATOR
8.3.1 Initial menu access
1. Power up all components and run Hyperterminal®. The starting screen appears, offering a selection of options
numbered 0 to J.
2. Type <2> to select the Enter Terminal Mode option. The Terminal Emulator screen appears.
3. Press <Ctrl> + <K> to select Enter VT100 mode for T100 Configurator. (‘T100’ is the generic name of the
configurator).
Note: If the screen goes blank, press <Enter> once or twice to continue.
4. Type <1> for the ANSI-CRT option. A log-in screen appears. Once a valid user ID and password have been
entered for a user with Remote attribute enabled, the configurator Initial menu appears as depicted in figure 8.3.1.
INIT Choose option
>DATABASE - General configuration

GATEWAY - MODBUS configuration
Figure 8.3.1 Configurator initial menu
NOTE. The appearance of the Initial or Main menus indicates that the CPU has entered configuration mode.
Locate the cursor (>) at a menu item using the cursor keys, then press <Enter> to display the next level in the menu
hierarchy. This is selecting an item. In general, to access the next lower level of the menu hierarchy, press <Enter>.
To return to the next higher level menu or close a ‘pop-up’ options menu press the <Escape> key. <PageUp> and
<PageDown> access hidden pages in long tables.
For keyboards without cursor-control keys, equivalent ‘control’ character combinations may be used, as indicated in
Table 8.3.1. To use these, hold down the <Ctrl> key and type the specified character.
Function Key combination

Cursor Up <Ctrl> + U
Cursor Down <Ctrl> + D
Cursor Left <Ctrl> + L
Cursor Right <Ctrl> + R
Page Up <Ctrl> + P
Page Down <Ctrl> + N
Table 8.3.1 Cursor-control — equivalent key combinations
Some tables allow values to be entered directly, or to be called-up by a menu.
For direct entry, type the first character(s) of the chosen option, followed by <Enter>.
Alternatively, access the menu with <Enter> or <Tab> as the first character after the field is selected.
Chapter 8 HA029280
8.3.2 The Initial menu

The Initial menu (Figure 8.3.1) lists two options — Database and Gateway. Select Database to access the Main menu
for configuring a LIN database. This is described in section 8.4. Select Gateway to access the Gateway menu, for
setting up a Modbus configuration, described in section 8.5.
8.3.3 Quitting the VDU package & CPU configuration mode
The starting screen can be returned-to at any time while running the VDU package, by operation of <Ctrl>+<E>. Typ-
ing <A> in the starting screen quits the VDU program.
Note: this action does not quit configuration mode in the CPU itself.
Getting a CPU out of configuration mode must be done from the terminal. Press <Escape> repeatedly until the main
menu screen appears, then press <Escape> once more to clear the screen. The CPU is now out of configuration mode.
Notes
1. <Ctrl>+<O> (‘Exit VT100 mode…’) does not quit CPU configuration mode and must not be pressed.
2. Stop/start/download/upload files cannot be stopped via LINfiler (in the LINtools package) in a CPU if it
still in configuration mode. If any attempt is made to do so, Error 8333 (‘Configurator in use’) is reported.
It is necessary to quit CPU configuration mode before such operations are attempted.
Caution
Always quit the primary CPU from configurator mode after use. Otherwise, an operator, unaware that the
CPU is still in configurator mode, might subsequently plug in a terminal and type <Enter> <Enter> — hoping
to see the version and power-up/shutdown messages. The result could be totally unexpected because the con-
figurator would continue from its last operation. For example, if if the configurator were last used to start a
database it would execute the start sequence (twice).
8.4 DATABASE CONFIGURATION
Figure 8.4 shows the Main menu, and sections 8.4.1 to 8.4.7 describe its items.
MAIN MENU Select option

>MAKE - Create block
COPY - Copy block
DELETE - Delete block
INSPECT - Inspect block
NETWORK - Network setup
UTILITIES - Engineering utilities
ALARMS - Current Alarms
ALARM LOG - Alarm History Log
EVENT LOG - EVENT LOG
Figure 8.4 Configurator Main menu
HA029280 Chapter 8
8.4.1 MAKE
Installs function blocks in the control strategy. Note that a running database must be stopped before any blocks can be
added to it. (Stopping and starting the database is described in section 8.4.6.) Select MAKE to display the SET
MENU — the controller’s resident library of block categories, detailed in the LIN Product Manual (Part number
HA082375U003). Note that every strategy must contain a ‘header’ block (Eycon-10 or Eycon-20) the only block
initially available for a new strategy. Select a category to list its blocks. Figure 8.4.1a shows part of the screen dis-
play when LOGIC is selected, as an example.
LOGIC Select type

>PULSE
AND4
OR4
XOR4
Figure 8.4.1a Logic category menu (upper part)
Select the block to be installed. The block Overview appears listing the block parameters, default values and units in
a double 3-column format. Figure 8.4.1b shows the (default) overview for the PID block as an example.
BLOCK OVERVIEW
Refer to Figure 8.4.1b which shows the main features of a typical block overview, used to monitor and update block
parameters. (Overviews can also be accessed via the COPY and INSPECT main menu options.) The overview is
equivalent to a LINtools Specification menu and its fields have the same meanings, although data entry is different.
Note : Parameters being updated by incoming connections from other blocks are not specially indicated in a
block overview.
OVERVIEW Block: “NoName” Type: PID Compound:
Mode AUTO Alarms

FallBack AUTO
HAA 1ØØ.Ø Eng
PV Ø.Ø Eng LAA Ø.Ø Eng
SP Ø.Ø Eng HDA 1ØØ.Ø Eng
OP Ø.Ø % LDA 1ØØ.Ø Eng
SL Ø.Ø Eng
TrimSP Ø.Ø Eng TimeBase Secs
RemoteSP Ø.Ø Eng XP 1ØØ.Ø %
Track Ø.Ø % TI Ø.ØØØ
TD Ø.ØØØ
HR_SP 1ØØ.Ø Eng
LR_SP Ø.Ø Eng Options ØØØØ11ØØ
HL_SP 1ØØ.Ø Eng SelMode ØØØØØØØØ
LL_SP Ø.Ø Eng
ModeSel ØØØØØØØØ
HR_OP 1ØØ.Ø % ModeAct ØØØØØØØØ
LR_OP Ø.Ø %
HL_OP 1ØØ.Ø % FF_PID 5Ø.Ø %
LL_OP Ø.Ø % FB_OP Ø.Ø %
Figure 8.4.1b Overview — PID block
Chapter 8 HA029280
8.4.1 MAKE (Cont.)
BLOCK OVERVIEW (Cont.)
Title bar. Contains fields common to all overviews: Block, Type, and Compound. Block and Type have
their usual LIN meanings; Compound is equivalent to Dbase. Please refer to the LIN Blocks
Reference Manual (in the LIN Product Manual) for details of these fields. A blank Compound
field denotes that the block database is local.
Note that the block is not installed into the control strategy until (at the minimum) its Block
field has been assigned a value — i.e. tagname — and the database has been restarted.
Overview data field entry. To update a parameter field, locate the flashing ‘underline’ cursor (_) at the field using the
arrow keys, then proceed as described below for the different data field types. Some data
fields display further nested levels of data when entered. In such cases, press <Enter> to
access a deeper level; press <Escape> to return to a higher level.
Note that editing a database during runtime is possible but is not recommended. (Stopping the
database is described in section 8.4.6, below)
User-defined names. Type in a name (8 characters max.) and press <Enter> to overwrite existing data. To insert
characters, locate the cursor at the character to follow and type the insertions. A ‘beep’ warns
that excess characters have been typed. To abort the current entry and leave the database
unchanged, move the cursor to a field above or below the current field before pressing <En-
ter>, or press the <Escape> key.
Note that, remote database names entered in the Compound field must be prefixed by an
‘equals’ sign (=) which is included in the character count.
Pressing <Enter> with the cursor on the first character of the Block or Compound fields
(before starting to type) accesses a Full Description page (Figure 8.4.1c shows an example).
This page gives general information about the block and has a common format.
FULL DESCRIPTION Block: PID_1 Type: PID
Refresh rate Ø.1Ø4Ø

Server number 2
Compound: =Alpha
Rate ms
Figure 8.4.1c FULL DESCRIPTION page for block (example)
Block. (Read/write). Block tagname.

Type (Read-only). Block type.
Refresh rate. (Read-only). Time (secs) since the block was last scheduled to run. Note
that for a control block the PID algorithm is not necessarily recalculated
every time the block is scheduled.
Server number (Read-only).
Compound. (Read/write). Name of the block’s parameter database. A blank field means
the block database is local, i.e. in the current Controller/Supervisor. (Data-
base names and their LIN addresses are specified via the main menu NET-
WORK option, described in section 8.4.5.)
Rate ms. Rate is the minimum update period (i.e. maximum rate) at which an indi-
vidual cached block is transmitted across the Local Instrument Network
(LIN). The default is 10ms minimum, i.e. 100Hz maximum. Rate can be set
between 10ms and 64s. Note that rate values are minimum update times
only, and heavily loaded networks may not be able to reach the faster update
rates.
HA029280 Chapter 8
8.4.1 MAKE (Cont.)
Parameter values. Type in a value and press <Enter> to update the database. (Read-only parameters do not
accept new values.) The CPU automatically adds a following decimal point and padding zeros
if needed, but before a decimal point a zero must always be typed, e.g. 0.5, not .5.
Pressing <Enter> with the field selected, before starting to type, accesses a Full Description
page for the parameter (Figure 8.4.1d shows an example).
FULL DESCRIPTION Field: PV Block: PID_1 Type: PID
Value 8Ø.1 Real32

Input SIM 1.OP
Figure 8.4.1d FULL DESCRIPTION page for parameter (example)
Field, Block, Type. Read-only fields.

Value. (Read/write) Parameter value, editable as for the Overview.
Real32. (Read-only) Value type (Real32 = floating point number)
Input. (Read/write) Defines the source of any connection to the parameter from another
block, as Block Tagname.Output Mnemonic. A blank field means no connection. To make or
edit a connection, type in the source block tagname and output mnemonic (e.g. SIM 1.OP, or
SEQ.DIGOUT.BIT3), then press <Enter>. Invalid data is ‘beeped’ and is not accepted. The
field is not case sensitive. To delete a connection, type <space> then press <Enter>.
NOTE. See below for information and advice on types of database connections.
Parameter units. Type in a value and press <Enter>. All other related units in the database automatically copy
the edited unit. Pressing <Enter> with the field selected, before starting to type, accesses the
parameter Full Description page (as for the value field).
Options menu fields. Press <Enter> to display a pop-up menu of options for the field. Figure 8.4.1e shows an
example (PID Mode) in part of an overview page.
OVERVIEW Block: PID_1 Type: PID Compound:
Mode Alarms
Fallback >HOLD
TRACK HAA 1ØØ.Ø Eng
PV MANUAL g LAA Ø.Ø Eng
SP AUTO g HDA 1ØØ.Ø Eng
OP REMOTE LDA 1ØØ.Ø Eng
SL F_MAN g
TrimSP F_AUTO g TimeBase Secs
RemoteSP g XP 1ØØ.Ø %
Track TI Ø.ØØØ
TD Ø.ØØØ
Figure 8.4.1e Pop-up options menu (example)
Using the ‘arrow’ keys, move the cursor (>) to a menu option and select it by pressing <En-
ter>. (Disabled options may not respond to selection.)
A quicker alternative to accessing the pop-up options menu is to type the required option, or
enough of its initial letters to uniquely specify it, directly into the selected field and then press
<Enter>. E.g. entering just H selects HOLD; entering F_M selects F_MAN (Forced Manual).
Chapter 8 HA029280
8.4.1 MAKE (Cont.)
Alarms field Press <Enter> to display a 4-column Alarms page listing alarm name (e.g. HighAbs), acknowl-
edgement (e.g. Unackd), status (e.g. Active), and priority (0 to 15). Update the acknowledge-
ment or priority fields (the only editable ones) by typing in a value and pressing <Enter>.
(Any single letter can be used for the acknowledgement field.) Figure 8.4.1f, below, shows an
example Alarms page.
Alarms Block: PID_1 Type: PID
Software Unackd Active 15

HighAbs Unackd Active 15
LowAbs Ø
HighDev Active 1Ø
LowDev 2
Combined Unackd Active 15
Figure 8.4.1f Alarms page (example)
Bitfields Contain eight (or sixteen) binary digits showing the logic states of a corresponding set of up to
eight (or sixteen) parameters. To edit the bitfield directly, type in a bit-pattern then <Enter> it.
Alternatively, press <Enter> to display a Full Description page listing the parameter TRUE/
FALSE or HIGH/LOW states (in the same format used for LINtools Specification Menu
bitfields). Figure 8.4.1g shows an example. Alter a logic state by locating the cursor on the
state, typing in T(rue) or F(alse), and pressing <Enter>. (A bit may be read-only.)
FULL DESCRIPTION Field: ModeAct Block: PID_1 Type: PID
NotRem TRUE
HoldAct FALSE
TrackAct FALSE
RemAct FALSE
AutoAct TRUE
ManAct FALSE
FAutoAct FALSE
FManAct FALSE
Figure 8.4.1g FULL DESCRIPTION page for bitfield (example)
To connect an input to a bitfield, press the Æ key and type in the block name/field name from
which the connection is to be made.
Note: See below for information and advice on types of database connections.
Two- and four-digit ‘combined’ hexadecimal status fields.

Hex fields are marked with a ‘>’ sign and have the same format and significance as those
found in LINtools specification menus. The digits show the logic states of a corresponding set
of parameters, up to four per hex digit. To edit the field directly, type in new values then press
<Enter>. Alternatively, press <Enter> to display a Full Description page listing the parameter
TRUE/FALSE states and edit this list (as described for Bitfields, above).
HA029280 Chapter 8
8.4.1 MAKE (Cont.)
CONNECTION TYPES IN A CPU DATABASE

There are three types of connection used in a CPU database: local connections, connections writing to a cached
block, and connections from a cached block to a local block. The following explains how and when they are evalu-
ated.
1. Local connections. These are connections between two blocks that are both local to the CPU database. The
connection is always evaluated immediately prior to the execution of the destination block’s update procedure,
regardless of whether the source data has changed between iterations. With this sort of connection, any attempt
to write to the connection destination is immediately ‘corrected’ by the next connection evaluation.
2. Connections writing to cached block. These are connections whose destination block is a cached copy of a
block in another instrument. The source of the connection can be either a local database block or another cached
block. Such connections are evaluated only if the source and destination data do not match. All cached blocks in
the database are processed at regular intervals, and whenever a change is detected a single field write is per-
formed over the communications link.
3. Connections from cached block to local block. These are connections where the source block is a cached copy
of a block in another instrument, and the destination block is local to the CPU database. All cached blocks in the
database are tested at regular intervals, and if a change in the block data is detected, then all such connections out
of the cached block into local blocks are evaluated. The connections are not evaluated if the source data has not
changed.
8.4.2 COPY
Creates duplicates of existing blocks. Select COPY from the main menu to display all the blocks in the control strat-
egy, in semi-graphical format as shown in Figure 8.4.2. The blocks are displayed from left to right in order of crea-
tion. Move the cursor (>) to a block and press <Enter>. The block is duplicated and added to the strategy, and its
Overview page automatically appears ready for parameterising. The duplicate retains all the original parameter values
except for the Block field, which has the default tagname “NoName”. Input connections are not copied; nor are I/O
block site numbers.
COPY Select block
Root SIM_1 TIC_100 PID_1 FIC_101
Figure 8.4.2 COPY display (example)
Pressing <Escape> returns the COPY display, where the copied block can be seen added to the list. Press <Escape>
again to return to the top level menu.
8.4.3 DELETE
Deletes blocks from the control strategy. (Note that the control database must be halted, otherwise selecting DELETE
results in a warning ‘beep’ and no action. Stopping the database is described in the UTILITIES option described in
section 8.4.6. Also, a block cannot be deleted unless its input connections have been cleared.) Select DELETE from
the main menu to display all the blocks in the control strategy, in the same format as for the COPY option described in
section 8.4.2. Select a block and press <Enter>. The block and any connections from it are deleted, and the main
menu returns to the screen.
Chapter 8 HA029280
8.4.4 INSPECT
Allows blocks in the control strategy to be inspected and updated. Select INSPECT from the main menu to display all
the blocks in the control strategy, in the same format as for the COPY and DELETE options already described. Select
a block and press <Enter> to display its overview page, ready for monitoring/updating.
Pressing <Escape> returns the INSPECT display, where other blocks can be selected for inspection. Press <Escape>
again to return to the top level menu.
8.4.5 NETWORK
Allows block databases to be assigned names and node addresses on the LIN (Local Instrument Network) so that they
can be configured as ‘cached’ blocks and run in a remote instrument. (The cached block’s Compound field, in its
overview page, specifies the remote database name.)
Note: It is good practice when using cached blocks, always to cache at least one block in each direction. This
enables the status of the comms link between the nodes to be monitored from both ends — via the cached
blocks’ software alarms.
Select NETWORK from the main menu to display the Network setup page (initially blank). Figure 8.4.5 shows the
top part of an example page with several databases already assigned.
Network setup
Alpha >Ø1
Beta >Ø2
dBase_1 >Ø3
Figure 8.4.5 NETWORK setup page (example)
To assign a new database name and address, locate the underline cursor at the left hand column of a blank row, type in
a unique name (7 characters max.) and press <Enter>. The name appears added to the list together with a default node
address >ØØ. (Non-unique or invalid names are ‘beeped’ and not accepted. Do not use ØØ or FF as node ad-
dresses). Move the cursor to the default address and type in the required node address (two hex digits). Press <En-
ter> to complete the assignation.
To edit an existing name or address, locate the cursor at a field, type in the new value, and press <Enter>. Invalid
entries are not accepted.
To delete a complete name and address entry, edit its name field to a space character. Configurations downloaded
from LINtools (or Eurotherm Network) will have a Network page set up automatically.
HA029280 Chapter 8
8.4.6 Utilities
Allows program control, I/O calibration, and filing. Select UTILITIES from the main menu to display the Utilities
options, shown in Figure 8.4.6.
UTILITIES Select option
>START - Start runtime system

STOP - Stop runtime system
SAVE - Save database
LOAD - Load database
FILE - File page
CALIBRATE - Calibrate IO Sites
Figure 8.4.6 UTILITIES options menu
START, STOP UTILITIES

Select START or STOP from the UTILITIES options menu and press <Enter> to start or stop the control program
running in the local Controller/Supervisor.
Note: When a database is started in RAM it is automatically saved to the file in FLASH called
filename.DBF, where filename is indicated in the filename.RUN file. It is then reloaded from FLASH to
RAM and started.
SAVE UTILITY
Names and saves a control program to a specified memory area. Select SAVE from the UTILITIES options menu —
the default filename specification, E:Eycon_10.DBF* is displayed. (The prefix E: directs the save to the CPU’s
FLASH area; this is the only available memory area. To save a database to a remote instrument, prefix the filename
specification by the node address of the instrument separated by a double colon, e.g. FC::E:Eycon_10.DBF*).
Type in a new specification if needed, then press <Enter> to execute the save. After a short pause the CPU signals
completion with the message: ‘Type a key to continue’. Typing any key returns the UTILITIES menu.
An invalid filename specification aborts the save, and the CPU sends an error message, e.g. ‘Save failed — Invalid
device’.
Notes:
1 Please refer to the note in section 8.4.6 about automatic saves.
2 Modifications to a control database are carried out on the RAM image only, not directly to the .DBF file
in FLASH. They are copied to FLASH (overwriting the existing .DBF file) automatically when the
database is restarted, or when a SAVE operation is carried out .
LOAD UTILITY
Retrieves a control program from a specified memory area and loads it to the CPU RAM area. Note that LOAD can-
not be performed during runtime. Select LOAD from the UTILITIES options menu — the default filename specifica-
tion, E:Eycon_10.DBF* is displayed. Edit the specification if needed (to alter the filename or its source, as described
for the SAVE utility above), then press <Enter> to execute the load. After a short pause the CPU signals completion
as described for the SAVE option. Typing any key returns the UTILITIES menu.
An invalid filename specification aborts the load, and the CPU sends an error message, e.g. ‘Load failed — File not
found’. To load a file from a remote node, prefix the filename by the address of the remote node e.g.
FC::M:FRED.DBF.
* or Eycon_20.DBF, according to model.
Chapter 8 HA029280
8.4.6 UTILITIES (Cont.)
FILE UTILITY
Permits access to the CPU file page, allowing files to be deleted or copied, and the E: device to be formatted. The file
page displays files in the E-device and also in a configurable remote ??::?: device. To access a remote device, move
the cursor to the ??::?: field and type in the required node and device letter, e.g. FA::M:. Press <Enter> to display its
files (up to a maximum of 20).
Move the cursor up and down the file list and tag files with an asterisk (*) using the <Enter> key. Then move the
cursor to the top column-head field and press <Enter> to display the function menu: Copy, Delete, Find, and — for E-
device and A-device only — Format. Finally, select a function and press <Enter> to carry it out. (Note that the Find
function has wild-card characters (?) which help in the locating of filenames containing known character strings.)
Press <Escape> to return to the UTILITIES menu.
8.4.7 ALARMS
Select ALARMS to view the currently active alarms in the instrument. Move the cursor up and down the list; press
<Enter> to acknowledge an individual alarm. Press I to inspect the block containing the alarm.
8.4.8 ALARM LOG
Select ALARM LOG to view a reduced-functionality version of the front panel alarm history.
8.4.8 EVENT LOG
Select EVENT LOG to view a reduced-functionality version of the front panel event history.
HA029280 Chapter 8
8.5 MODBUS CONFIGURATION
Note: The resident Modbus configurator is similar in operation to the Modbus configurator in the T500
LINtools package. See the T500 LINtools Product Manual (Part No. HA082377U999) for more informa-
tion.
GATEWAY MODBUS configuration

-------------------------------------------------------------
>GWindex - Select GW index
MODE - Operating mode
INTERFACE - Select interface
SETUP - Serial line
TABLES - Register & bit configuration
Figure 8.5 Gateway menu
8.5.1 GW index
This command appears only for products which support multiple GW indices.
Select the GW index number ( 1 to 3 inclusive) that is to be viewed by the configurator. The filename (where the GW
index number was loaded) appears in the filename field.
GWindex Select GW index

-------------------------------------------------------------
GWindex 1
Filename Filename
8.5.2 MODE
Selecting MODE causes a pop-up menu to appear, allowing the user to select Master or Slave mode. The selected
mode is arrowed.
MODE Operating mode

-------------------------------------------------------------
Mode +--------+
|>Slave |
| Master |
+--------+
Chapter 8 HA029280
8.5.3 INTERFACE
Allows the interface type and instance of the instrument to be selected. The Interface type should be selected as Serial
or TCP/Ip, then the port number to which the Modbus instrument is to be connected should be entered.
INTERFACE Select interface

-------------------------------------------------------------
+--------+
Type Serial|>Serial |
COM1 | TCP/IP |
+--------+
8.5.4 SETUP
Configures the selected Interface Type and Interface Instance of the instrument defined in the INTERFACE menu.
Selecting SETUP displays a menu that is dependent on the INTERFACE and MODE configurations.
SERIAL MASTER
If Serial is selected in the INTERFACE menu and Master is specified in the MODE menu the SETUP menu shows
Baud rate, Parity, Stop bits, and Time out fields.
SERIAL SLAVE
If Serial is selected in the INTERFACE menu and Slave is specified in the MODE menu the SETUP menu shows
Baud rate, Parity, Stop bits, Time out, and Slave No. fields.
SETUP Configure interface
Baud rate 2400

Parity Odd
Stop bits 2
Instr No >63
Time out 1.000 secs
TCP MASTER
If TCP/IP is selected in the INTERFACE menu and Master is specified in the MODE menu the SETUP menu shows
only the Time out field.
TCP SLAVE
If TCP/IP is selected in the INTERFACE menu and Slave is specified in the MODE menu the SETUP menu will show
the Port no, Instr No, Time out, and CNOMO fields.
Note. If the instrument supports CNOMO registers, this field indicates that Register Offset values 121, to 124
will display specific Manufacturer and Product details.
HA029280 Chapter 8
8.5.4 SETUP COMMAND (Cont.)
This page gives general information about the Interface configuration.
Port no TCP/IP Interface and Slave Operating Mode only. It shows the TCP port via which this modbus-TCP-
slave instance communicates. 0 = default = 502.
Baud rate Highlight and enter this item to see a menu of the available baud rates, 110, 150, 300, 600, 1200, 2400,
4800, 9600, and 19200. Select and enter the required baud rate.
Parity Entering this item displays a menu of options, None, Odd, and Even. Select and enter the required parity.
Stop bits Enter this item, type in the required number of stop bits, and press <Enter> to update the SETUP menu,
Only 1 or 2 stop bits are permitted.
Line type Shown only if both Serial Interface is selected and the instrument supports software selection of 3-wire/5-
wire operation.
Note. This is not currently supported.
Time out Enter a Time out value, in the range 0 to 65.5 seconds. In slave mode, this parameter specifies a watchdog
period for all tables. That is, if a table has not been accessed for Time out seconds, the Online bit in the
slave mode diagnostic register for that particular table resets to zero. In master mode, Time out specifies a
maximum period between the end of a master’s request for data to the start of the slave’s response. If this
time is exceeded, the Online bit in the master mode diagnostic register for the particular table concerned
resets to zero.
Instr No Slave Operating Mode only. Input an ‘instrument number’, i.e. the address on the Modbus Serial link of
the slave device being configured. Slave addresses are in the range 01 to FF hexadecimal, but note that
for some equipment FF is invalid.
Chapter 8 HA029280
8.5.5 TABLES
Shows the Tables List dependant on the MODE configuration. To view the tables list, highlight TABLES and press
<Enter>. Individual menus can be displayed by selecting the required Table number, see Table Menus.
TABLES LIST
The Tables List provides an overview of all the tables in the Modbus configuration. Each instrument supports a maxi-
mum number of Tables as defined by the MAX_TABLES field in the instrument Configuration (Header) block. The
Tables List offers sixteen tables, so 4 pages are used to cover the 64 tables.
This menu allows tables to be created and the types, offsets, sizes, and for master mode, function codes, scan counts,
instrument numbers and tick rate to be specified. The Tables List also accesses individual Table Menus for detailed
configuration, i.e. LIN Database mapping, see Table Menus section.
The Tables List menu below shows an example Tables List with Table 1 configured as a Register Table. The first
four columns, Table, Type, Offset, and Count, are common to both the Master and Slave Operating Modes. The re-
maining, Functions, Scan count, Instr No, and TickRate appear only when Master Operating Mode is configured.
Table Type Offset Count Functions Scan count Instr No TickRate

-----------------------------------------------------------------------
1 Register 0 16 3 4 6 16 16 >00 100

2 Unused 0 0 - - - - 0 >00 0
3 Unused 0 0 - - - - 0 >00 0
4 Unused 0 0 - - - - 0 >00 0
5 Unused 0 0 - - - - 0 >00 0
6 Unused 0 0 - - - - 0 >00 0
7 Unused 0 0 - - - - 0 >00 0
8 Unused 0 0 - - - - 0 >00 0
9 Unused 0 0 - - - - 0 >00 0
10 Unused 0 0 - - - - 0 >00 0
11 Unused 0 0 - - - - 0 >00 0
12 Unused 0 0 - - - - 0 >00 0
13 Unused 0 0 - - - - 0 >00 0
14 Unused 0 0 - - - - 0 >00 0
15 Unused 0 0 - - - - 0 >00 0
16 Unused 0 0 - - - - 0 >00 0
This page gives general information about the Modbus Table configuration.
Table This is the Table number, which is not editable. Highlight and <Enter> a Table number field to display
the information related to the selected Table number. For a table with a Type other than Unused, the table
menu for that table is displayed, see Table Menu.
Type This field, defaults to Unused, allows the Table Type to be created or edited. Enter a Type field to see a
menu of four options. Select one and press <Enter> to create a new table or convert an existing one to a
new type.
Note. Other fields in the Tables List associated with the selection automatically adopt default values.
The Type options are:

Unused The table does not exist.
Register This type of table maps LIN Database parameters to standard 16-bit Modbus registers.
Digital This type of table maps LIN digital, boolean or alarm values to bits in the Modbus
address space.
Diagnostic This is a special table, similar to a Register Table, but the values in the table have
pre-defined values that are used to control the Modbus operation, or present diagnostic
information to the LIN Database.
HA029280 Chapter 8
8.5.5 TABLES (Cont.)
Offset This field selects the start address of the table on the Modbus network. These values are the
actual values used in the address field of the Modbus messages, i.e. the ‘protocol addresses’.
Note. PLCs differ in the correspondence between their register or bit addresses and the protocol addresses.
Count This field shows the number of registers or bits in a table. It allows the size of register and
digital tables to be changed from their default values of 64 registers or bits, respectively, to
optimise the use of memory. Diagnostic tables are fixed at 32 registers.
Functions Master mode only. This field allows the default Modbus function codes that can be used with
a particular Modbus table type to be enabled or disabled. Modbus function codes define the
type of data exchange permitted between Master and Slave instruments via a particular table.
To disable a default function code, highlight it with the mouse and press <Enter> to see a
menu of ‘-’ and the default code number. Selecting and entering ‘-’ disables that code for the
table concerned. Select the code number again to re-enable it if required.
Scan count Master mode only. This sets the maximum number of registers (register table) or bits (digital
table) that can be read or written in a single Modbus transmission. Scan count defaults to the
same value as Count, i.e. as the table size, which results in the whole table being updated each
polling cycle. If Scan count is made less than Count for a particular table, it takes more than
one cycle to be updated but the overall polling cycle speeds up. This may be required for
Modbus devices with limited buffer sizes.
Instr No Master mode only. This specifies the hexadecimal Slave number value of the instrument on
the Modbus network in which the data registers or bits associated with this master table are
located.
Tick Rate Each table of registers is assigned a Tick Rate, a value between 0 and 65535 ms, to define the
frequency at which it is scanned. The Tick Rate associated with each table can be configured.
If the LIN instrument does not support Tick Rates, and/or if the instrument is configured to
operate in Slave mode, the Tick Rate fields are disabled.
Chapter 8 HA029280
TABLE MENUS
Individual table menus are accessed from the tables list by highlighting of its table number (in the first column headed
Table) followed by <Enter>. To highlight fields, the arrow cursor is moved around the table menu using the mouse, or
the PC’s <Home>, <End>, and cursor keys can be used.
Table menus allow the mapping between the LIN database fields and the Modbus addresses to be configured.
Figure8.5.3b shows a typical default table menu for a register table.
Note that table headings differ for register and digital tables, but that some fields are common to both —
Field, DB Write, and MOD Write.
Register Field DP Format DB Write MOD Write Value

------------------------------------------------------------
0 0 Normal Enable Enable >0000
Figure 8.5.3b Register table menu — default
Register (Register and diagnostic tables only) This column shows the Modbus address of the particular register. The
first register in the table takes its address from the Offset value given to the table via the table list (described
above). The remaining (read-only) addresses follow on consecutively.
Digital (Digital tables only) This column shows the Modbus address of the digital bit on the selected line of the table.
If the line contains a bitfield rather than a single bit, the address shown is that of the first bit in the bitfield.
Mappings may be made for a single bit, or for an 8- or 16-bit field, according to the value defined in the
Width parameter (see later). The first bit address in the table takes its value from the Offset given to the table
via the table list. The remaining (read-only) addresses follow on, according to the numbers of bits on each
successive line of the table (1, 8, or 16).
Field. This is the LIN database field to which the Modbus address is mapped, or it can be left blank. Select a field
with the cursor and type in and enter a LIN function block name plus parameter (and subfield if needed),
separated by full stops (periods), e.g. PV1.Alarms.Software.
Notes:
1. If an attempt is made to enter an analogue parameter into a digital table Field, the entry is ignored. Any
type of parameter can, however, be typed into a register (or diagnostic) table.
2. In a digital table, LIN database parameters cannot be entered or overwritten if to do so would force an
entry lower down the table to change its address.
HA029280 Chapter 8
DP. (Register and diagnostic tables only) This column can be used either to specify a decimal point position, or to
create a 32-bit register.
1. Decimal point position. DP can store a decimal point scaling factor that is used when converting floating
point numbers to 16-bit Modbus registers. For this purpose, enter an integer from 0 to 4; the DP-value
represents the number of decimal places in the converted number.
2. 32-bit register. (Register tables only) A 32-bit register is created by ‘joining’ a consecutive pair of 16-
bit registers, as described below. The following restrictions are applied to ensure that the 32-bit value
created is transferred indivisibly:
a The multiread function (3) and multiwrite function (16) must both be enabled.
b The scan count must be even.
c The first register of the pair must be at an even offset within the table.
d The first register of the pair must not be the last register in the table.
e The second register of the pair must not already be assigned to a LIN database field.
f The field type of the 32-bit register pair must be a 32-bit long signed or unsigned, a 32-bit real or a
string. For a string, only the first four characters are transferred.
To create a 32-bit register pair, enter ‘d’ (or ‘D’) in the DP field of the first register of the pair. This causes the
register’s DP to adopt the value ‘D’, and the following register the value ‘d’. If any of the above restrictions
are violated, the entry will be rejected.
When the first register of the 32-bit pair is assigned to a LIN database field, the second register automatically
copies the same field name; assigning the name and the DP can be done in either order. A 32-bit register pair
can be restored to individual 16-bit registers by changing the DP of the first register to zero to four.
Format (Register and diagnostic tables only) This column specifies the format of the data in the register — normal or
binary coded decimal (BCD). Normal format means that the data is a simple 16-bit integer. In BCD format
the value is first limited to the range 0 to 9999, and then stored as four 4-bit nibbles in the register. The units
are stored in the low order nibble, the tens in the second nibble, the hundreds in the third, and the thousands in
the high-order nibble. BCD format allows the data to be used with certain devices such as displays.
NOTE. Format is ignored in 32-bit registers.
Width (Digital tables only) This column indicates the number of bits contained in the associated field. The default
Width is 16, but it automatically updates when a parameter is allocated to the field. Allocated field ‘widths’
are read-only, but the width of an unallocated field can be specified by highlighting its Width value and
entering a valid number in the range 1 to 16, (normally 1, 8, or 16).
Note Width values cannot be edited, if to do so would force an entry lower down the table to change its
address (Digital value).
DB Write This column allows selected values in the LIN database to be protected against being overwritten by values
received across the serial link. Highlight the required DB Write field and press <Enter> to see a menu of
options — Enable and Protect. Select ‘Protect’ to write-protect the LIN database parameter, or ‘Enable’ to
allow overwriting.
NOTE. For a 32-bit register pair, DB Write applies only to the first register. The DB Write-value of the
second register is ignored.
Chapter 8 HA029280
MOD Write This column allows selected values in the LIN database to be prevented from being written to their associated
Modbus registers or bits. Highlight the required MOD Write field and press <Enter> to see a menu of options
— Enable and Protect. Select ‘Protect’ to write-protect the Modbus register/bit(s), or ‘Enable’ to allow
overwriting.
Notes:
1. To protect an entire table (for a Modbus Gateway facility operating in Master mode), the write function
codes 5 and 15, or 6 and 16 can be disabled in the tables list.
2. For a 32-bit register pair, MOD Write applies only to the first register. The MOD Write-value of the
second register is ignored.
Value This column shows the current 16-bit value of the field in 4-digit hexadecimal representation. ‘Value’ is read-
only.
HA029280 Chapter 8
This page is deliberately left bank
Chapter 8 HA029280
CHAPTER 9: PREVENTIVE MAINTENANCE
This section shows how to replace the battery and how to calibrate the touch screen.
9.1 BATTERY REPLACEMENT
The battery replacement period depends on the cumulative length of time over which the instrument is left without
supply power. The battery maintains the real-time clock and SRAM data (e.g. hot start database). A flag (BadBatt)
can be set in the “Eycon-10 or Eycon-20” block. This flag will result in an instrument alarm should the battery volt-
age falls below the minimum necessary for it to function properly. It is recommended that the battery be replaced as
soon as possible after the appearance of this warning.
Caution
The user must be at the same electrical potential as the instrument housing when accessing the battery.
Notes:
1. All battery backed RAM data is lost during battery change unless power to the unit is maintained during
the change.
2. Battery type is BR2330 Poly-carbonmonofluoride/lithium. Available from the Visual Supervisor manu-
facturer under part number PA261095.
3. Dispose of exhausted batteries in accordance with local regulations regarding this battery type.
9.1.1 Replacement procedure

1. For non-Profibus units, remove the screw securing the access cover. Remove the cover. Replace the battery and
refit the cover.
2. For units fitted with the Profibus option, remove the screw securing the Profibus enclosure. Carefully separate
the enclosure from the instrument, taking care not to damage the wire harness which connects the option board to
the main board. Replace the battery and refit the enclosure.
Note: Drawings not to the same scale
Access cover,
or Profibus enclosure
BR2330
Cover retaining
screw location
Figure 9.1a Figure 9.1b Battery location - small frame unit

Access cover/Profibus enclosure location - large frame unit (Access cover/Profibus option removed)
HA029280 Chapter 9
9.2 TOUCH SCREEN CALIBRATION
This procedure ensures that the instrument responds to the exact point that has been touched by the user.
At switch-on, continuously hold a finger in contact with the display screen until the 'calibration display' appears (ap-
proximately 60 seconds after switch on) as depicted in figure 9.2.
Using a soft, small diameter item (e.g. a pencil point) which will not damage the touch screen, touch the intersection
of the upper set of crosshairs, as requested by the display.
Once the top left target has been accepted, continue as requested by the display. Once all the targets have been ac-
cepted, initialisation continues as normal.
Touch Target
Figure 9.2 Initial calibration display screen
Chapter 9 HA029280
CHAPTER 10: PROFIBUS MASTER OPTION
10.1 INTRODUCTION
This option provides GW Profibus Master functionality. The option circuit board and associated 9-way D-type con-
nector are housed in a rectangular enclosure located at the rear of the instrument. This chapter provides electrical and
mechanical details for the option and also describes how to access the Profibus Master Configuration page in
LINtools.
Details of recommended Profibus network wiring are to be found in the Modbus/Profibus communications handbook
(HA028014).
Configuration of the Profibus network is carried out using the Profibus editor within LINtools. To display the con-
figuration page (figure 10.1):
1. Click on ‘Add...’
2. In the pop-up dialogue box that appears, click on ‘New LIN Profibus Master’. This adds the GWProfM_CON
block (section 10.3) to the database, and creates a Profibus Network.
3. Click on the Profibus master symbol in the Contents Pane to display the Profibus Master Editor page.
Once configuration is complete, it should be saved. The Save operation automatically generates .gwf and .upb files
which are added to the ‘download list’. The next Download operation transfers the download list contents to the Pro-
fibus Master instrument. See the on-line help file included with LINtools for further details.
Add...
Download
Profibus Master
symbol
Figure 10.1 Profibus editor master configuration page example
10.2 INSTALLATION
10.2.1 Mechanical installation
Figures 10.2.1a and 10.2.1b show the mechanical installation details for the small frame and large frame units respec-
tively. See also chapter 11 for details of the ‘Flush-mounting’ option.
10.2.2 Pinout details
Figure 10.2.2 shows pinout details for the Profibus 9-way D-type connector.
HA029280 Chapter 10
10.2 INSTALLATION (Cont.)
6.7 mm
106.8 mm
144.0 mm
86.8 mm
Profibus
connector
137.0 mm
144.0 mm
CL
Fixing Clip
(one each side)
F1 F2 F3
F4 F5 F6
Protective-conductor
terminal (M4)
Flash card
USB
Panel cutout
Ethernet Serial comms 138 mm x 138 mm
– – + +
(both -0 + 1 mm)
Power
Profibus
137.5 mm
154.5 mm
170.5 mm


Figure 10.2.1a Mechanical installation - small frame unit
Chapter 10 HA029280
9.6 mm 90.0 mm
288.0 mm 70.0 mm
Profibus
connector
280.3 mm
288.0 mm
CL
Fixing Clip
(one each side)
F1 F2 F3 F4 F5 F6 F7 F8 F9
F10 F11 F12 F13 F14 F15 F16 F17 F18
F19 F20 F21 F22 F23 F24 F25 F26 F27 Protective-conductor
terminal (M4)

Serial
Ethernet Comms Power
Flash card
USB
– –++
Profibus
281.4 mm
298.4 mm Panel cutout = 282 mm x 282 mm
314.4 mm (both -0 + 1.3mm


Figure 10.2.1b Mechanical installation - large frame unit
HA029280 Chapter 10
5
5 0 Volts
9 0V (pin 5) 9 Not connected
Rx/Tx –ve 4 Not connected
(A) (pin 8) Rx/Tx +ve 8 Rx/Tx –ve (A)
3 Rx/Tx +ve (B)
+5V (pin 6)
(B) (pin 3) 7 Not connected
2 Not connected
6 1 6 +5V for pull-up
1 Not connected
Figure 10.2.2 Profibus option pinout
10.3 FUNCTION BLOCKS
10.3.1 GWProfM CON

Notes
1 All field names except ‘File Name’ and ‘Alarms’ are unavailable in Configuration mode.
2. More information is to be found in the Lin Blocks reference manual HA082375U003
File Name An eight-character string field containing the base file name of the GWF file to be loaded by
this block. The following rules must be adhered to or an alarm will be generated:
1. The GWF file referenced by this field must have been created using the Comms configura-
tion tool.
2. The GWF file must contain a reference to the currently loaded database file.
3. No path is specified as it is assumed that the file exists on the default ‘E’ drive.
Reload A writable field that, when set true, forces the GW instance to be suspended whilst it is
reloaded from the specified FileName. The field auto resets to False once the reload is
complete. This can be used to effect a crude form of reconfiguration by replacing an entire
GW instance.
GWIndex A read-only 8-bit unsigned integer field that shows the current GW instance number, between
1 and 3.
MaxIndex A read-only 8-bit field showing the maximum instance number for this instrument type (1 for
Profibus Master).
TableCnt The number of GW tables being used by this block.
Port A representation of the port being used by this instance.
Address The node address of the Profibus Master
BaudRate The current Baud Rate.
MaxDev The maximum number of slaves which the master is cabable of communicating with.
ConfDev The number of configured slave devices.
ActvDev The number of active (communicating) slave devices.
IpMemUse The amount of cyclic input space currently in use.
OpMemUse The amount of cyclic output space currently in use.
ScanRate The time (in µs) currently being taken to perform a single update cycle.
Tblrate The time (in µs) currently being taken to update all the input and output tables of all the active
slaves.
DiagRate The time (in µs) currently being taken to update all extended diagnostics tables.
AcycRate The time (in µs) currently being taken to update all the acyclic read/write tables.
Chapter 10 HA029280
10.3.1 GWPROFM CON (Cont.)
HWState The current status of the Profibus Master:

Inactive The Master is in the Stop state (the default at power-up).
Loading The Master is loading the binary configuration file.
Validating The Master is validating the loaded configuration file.
Searching The Master is searching the Profibus network for the devices defined in the
configuration file.
Starting The Master is starting communications channels with the devices detected during
the search.
Active The Master is actively communicating with all active configured slaves on the
network.
Stopping The Master is closing communications channels with all active slaves on the
network.
Stopped All communications (including network maintenance) have stopped.
Error The Master has experienced a ‘fatal’ error and is no longer able to communicate
with any slave(s).
ResetCnt Resets the following error counters.
CIpFail The number of failed attempts to read cyclic process input data. This failure is caused by the
Profibus Master denying a slave’s access to the ‘process input data’ area. Incremented each
time access is denied to any slave.
COpFail The number of failed attempts to write cyclic process output data. This failure is caused by the
Profibus Master denying access to the ‘process output data’ area. Incremented each time
access is denied to any slave.
AIpFail The number of failed attempts to read acyclic data. The failure might be caused by the Master
Profibus board, or by rejection by a slave.
AOpFail The number of failed attempts to write acyclic data. The failure might be caused by the
Master Profibus board, or by rejection by a slave.
SlaveAdd This user-enterd value is the address of the slave for which Profibus diagnostics are to be
displayed.
stdDiag1 Byte 1 of the standard Profibus diagnostics for the slave defned in ‘SlaveAdd’, above.
NonExist Slave did not respond last time.
NotReady Slave not ready for data transfer.
CfgFault Slave is reporting a configuration error.
ExtDiag Extended diagnostics data available and valid.
NotSupp Slave does not support a feature requested by the Master.
InSlvRes The slave’s response was not DP compatible.
ParamFlt The slave reported a parameter error.
MstLock The slave is already communicating with another master.
ParamReq Slave requires configuration.
StatDiag Slave is signalling that the static diagnosis/DPV1 slave application is not ready
for data exchange.
DPSlave Profibus DP slave
WdogOn Watchdog on.
FrzeMode DP slave is in Freeze mode.
SyncMode DP slave is Synchronising.
Reserve6 Not used at this release.
Deactive DP slave has been deactivated.
Reserve0
to Not used at this release.
Reserve6
ExDiagOv Too much extended diagnostic data.
MastAddr Byte 4 of the standard Profibus diagnostics for the slave defned in ‘SlaveAdd’, above.
IdentNum Bytes 5 and 6 of the standard Profibus diagnostics for the slave defned in ‘SlaveAdd’, above
giving the Slave identification number.
HA029280 Chapter 10
10.3.1 GWPROFM CON (Cont.)
Note: In the following Slave Comms Error subfields if a bit is set (true) then the Slave is off-line in an error
condition. When false, a bit indicates that the relevant slave is on-line and communicating.
ComsErr1 Slave comms error bits for slave addresses 0 to 15.

Alarms Software A software error has occurred.
BadFile The GWF is corrupt or missing.
BadDBF The GWF is not associated with the current database file (dbf).
BadCfg Profibus configuration error.
ImgSize The process image size for one or more slaves is too big.
HWError Profibus hardware error
ComsErr An ‘OR’ of all ComsErr values from all configured slaves.
TooMany No more GW instances available.
TableFlt One or more tables in this GW instance has an internal fault
BadPort A mismatch in the port configuration, between the GW configuration and the
system opt file in the target.
PendSave The memory image of this GW instance has been modified (probably by the
removal of invalid block references) since it was loaded from the GWF. A save of
the GWF must be performed in order to synchronise the file with the memory
image.
Spare
Spare
Spare
Spare
Combined Gives the priority level of the highest priority active alarm in the block
Chapter 10 HA029280
CHAPTER 11: FLUSH MOUNTING OPTION INSTALLATION
Note:This chapter gives details of the mechanical installation of the ‘Flush-mounting’ option. Wiring details
are as given in chapter 1 and (for the Profibus option) chapter 10.
11.1 UNPACKING
The unit is despatched in a special pack designed to protect it during transit.
If the outer box of the pack shows signs of damage, please open it immediately and examine the instrument. If there is
evidence of damage, contact the manufacturer’s local representative for instructions. Do not operate the instrument in
the meantime.
If the outer box is not damaged, remove the instrument from its packing with all accessories and documentation.
Once the unit has been installed, store any internal packing with the external packing in case of future despatch.
11.2 MECHANICAL INSTALLATION
The clamping plates can be mounted either at the top and bottom of the Visual Supervisor. or at left and right sides.
Figure 11.2c shows details of how to remove the clamping plates. The plates are fixed to the rear of the panel (see
figures 11.2d/11.2e for fixing centres) either by suitable screws into the rear of the panel or by means of studs, or ma-
chine screws passing through the panel from the front (‘A’ and ‘B’ in figure 11.2a). M5 studs or screws are recom-
mended; the clamping plate fixing holes are 6mm in diameter.
1. Check that the mounting panel is no thicker than 13mm and no thinner than 1mm.
2. Cut an aperture 144mm x 144mm (small frame) or 290mm x 290mm (large frame) in the panel. If more than one
instrument is to be mounted in the panel, the recommended minimum spacings are as shown in figure 11.2d/
11.2e.
3. From the rear of the panel, offer the front of the instrument to the aperture and secure the clamping plates to the
panel using fixings appropriate to the panel type (fixings ‘A’ and ‘B’).
4. Use the jacking screws to adjust the position of each corner of the Visual Supervisor such that the touch screen
surface is flush with the front surface of the panel. Adjustments may need to be made more than once for each
screw. When the adjustment process is complete, use the 6 mm locking nuts (10 mm across flats) to secure the
jacking screws.
5. Complete installation by fitting an overlay (see figures 11.2d/11.2e for overlay cutout dimensions).
Clamping
Rear face of
plate
panel A A
B
B
Panel cutout
Jacking
screw
Figure 11.2b Adjust each corner

Figure 11.2a Fixing the instrument to the panel
(Large frame unit shown - small frame unit similar)
(Large frame unit shown - small frame unit similar)
HA029280 Chapter 11
To remove a clamping plate (usually to change from top/bottom fixing to left/right fixing):
1. Remove the jacking screw locking nuts and retain them for later re-assembly.
2. Use a screwdriver to rotate the jacking screws clockwise, a few turns on each screw at a time, until they are free
of the lugs and the clamp can be removed. Note that a narrow screwdriver (4.5 mm max) is required for the last
few turns, when the blade must fit within the diameter of the M6 lug hole.
Re-fitting is the reverse of the above process.
Side mounting
lugs (4 places)
Clamping
plate 6mm Locking nuts (10mm A/F)
(two per clamping plate)
Jacking screw
(two per clamping plate)
Figure 11.2c Clamping plate fixing details
11.2.1 Specification
The specification for the flush-mounting option differs only in the mechanical dimensions, given in figures 11d and
11e, and in the IP rating which is as follows:
IP rating without overlay IP40

IP rating with overlay Depends on the design of the overlay panel.
Chapter 11 HA029280
183.6mm 109.1 mm
160.0 mm 90 mm
143.0 mm
Fixing holes Profibus

(6 mm dia.) option
143.0 mm
171.0 mm
133.0 mm
CL CL
F1 F2 F3
F4 F5 F6
Panel thickness: Max = 13 mm; Min = 1 mm PANEL MOUNTING DETAILS
Jacking screw (4 places) Panel cutout (A x A):

144 mm x 144 mm (-0 +1)
A C Overlay cutout (C x C):

114.5 mm x 114.5 m
– – + +
(offset (B) from top of
panel cutout = 18.3 mm)
Profibus option
137.5 mm C
A
Note: Ensure that the ambient temperature Vertical panels only.
does not exceed 50 degrees Celsius Min. inter-unit spacing (vertical): 50 mm.
Min. inter-unit spacing (horizontal): 50 mm.
Figure 11.2d Small frame unit mechanical dimensions
HA029280 Chapter 11

318.0 mm
289.0 mm 93.1 mm
140.0 mm 74.0 mm
Fixing holes
Profibus
(6 mm dia.) option
306.0 mm
330.0 mm
289.0 mm
274 mm
CL
Fixing holes
F1
(6 F2mm
F3
dia.)
F4 F5 F6 F7 F8 F9
F10 F11 F12 F13 F14 F15 F16 F17 F18
F19 F20 F21 F22 F23 F24 F25 F26 F27

B
Panel cutout (A x A):
Jacking screw (4 places) 290 mm x 290 mm (-0
+1)
––++
Profibus option
A C
281.4 mm Overlay cutout (C x D):
C = 240 mm; D = 250mm
(offset (B) from top of
panel cutout = 30 mm)
D
A
Note: Ensure that the ambient temperature Vertical panels only.

does not exceed 50 degrees Celsius Min. inter-unit spacing (vertical): 50 mm.
Min. inter-unit spacing (horizontal): 50 mm.
Figure 11.2e Large frame unit mechanical dimenssions.
Chapter 11 HA029280
APPENDIX A: TECHNICAL SPECIFICATION In order to comply fully with BS EN61010, all I/O
and hardware alarms must be enabled
General specification
Physical (1/4 VGA)
Dimensions
Bezel: 144 x 144 mm
Cut-out: 138 x 138 mm
Depth: 87.7 mm (106.8 with Profibus option)
Weight 1.5 kg
Screen Type: 1/4 VGA TFT colour
Display area: 111 x 84 mm
Touch panel: Resistive analogue
Character set: Unicode Latin-1
Physical (XGA)
Dimensions
Bezel: 288 x 288 mm
Cut-out: 282 x 282 mm
Depth: 70.4 mm (90 mm with Profibus option)
Weight 3.7 kg
Screen Type: XGA TFT colour
Display area: 245 x 188 mm
Touch panel: Resistive analogue
Character set: Unicode Latin-1
Environmental
Temperature Storage: -10 to +85˚C
Operation: 0 to + 50˚C
Humidity Storage: 5 to 95% RH (non-condensing)
Operation: 5 to 85% RH (non condensing)
RFI Emissions: BS EN50081-1
Susceptibility: BS EN50082-2
Electrical Safety BS EN61010-1:2001
Installation category II, Pollution degree 2.
Vibration BS EN60873, Section 9.18
Shock BS EN60068-2-31; BS EN60873, Section 9.12
Protection Front panel: IP65
Power requirements
Voltage range: 19.2 to 28.8V dc. (24V dc ± 20%)
Ripple: 1 V max.
Max. power requirement (at 24V): Small frame = 20 W; Large frame 24 W
Operating current (at 24V): Small frame = 0.8 A; Large frame = 1Amp
Inrush current: 10 A max.
User termination: 4-way connector
Internal fusing: No user replaceable fuses.
Battery
Battery BR2330 Poly-carbonmonofluoride/lithium. Part number PA261095. See also section 9.1.
Data Logging Storage

Disk Internal Flash memory
Data format ASCII (.asc) or compressed data
Data compression Proprietary
Log frequency 1 Hz
HA029280 Appendix A
Issue 5 Mar 08 Page A - 1
SPECIFICATION (Cont.)
Programmer
Max. no. of concurrent programs 8
Max. no. of segments 250
Max. no. of analogue setpoints 16
Max. no. of digital setpoints 32
Alarms and events
Number of records in history 500 lines maximum
History line format Name - Type - Date - Time
Acknowledgment Colour coded.
No. of records in event log 1000
Recipes
Max. no. of concurrent recipe sets (files) 8
Max. no. of production lines per set 8
Max. no. of recipes per set (file) 16
Max. no. variables per set 500
Batch
Max. no. of concurrent batches (files) 8
Max. no. of phases per batch 20
Trends
Max. no. of groups (trends) 16
Max. no. of points per group 16
Maximum frequency 1 sample per second
Maximum samples 15,000 for 1 group of 16 points.
Continuous database resources
Database size 128kBytes Notes:
No. of function blocks 512 max. 1. The maxima given here are defaults and are the recommended limits.
No. of templates 100 max. Subject to note 2, it is possible to exceed some of these values, but if a
database with more resources than the default maximum is loaded,
No. of libraries 50 max.
the maximum is set to the new value and there may then be insuffi-
No. of EDBs 32 max.
cient memory to load the entire database or to allow on-line reconfig-
No. of FEATTs 512 max. uration. In such a case ‘connections’ disappear first. FEATTs are not
No. of TEATTs 128 subject to this problem as, when a database is saved, there are not
No. of servers 2 max. normally any FEATTs present, so the maximum cannot be exceeded.
No. of connections 1024 2. If the EDB maximum is exceeded some EDBs will malfunction, affecting
LINtools functionality.
Sequence control resources

Sequence memory program data 112kBytes
Sequence memory SFC resources 76kBytes
Simultaneously active independent sequence tasks 10
SFC actions (including root SFCs) 100
Steps 320
Action Associations 1200
Actions 600
Transitions 450
Setpoint program resources
No. of simultaneously running programs (max.) 8 (See table for resource distribution)
Profiled analogues (max.) 16
Profiled digitals (max.) 32
Segments per program (max.) 250
No. of Max. no. of Max. no. of Max. no. of
programs analogues digitals segments
1 16 32 250
2 16 32 125
4 16 16 80
8 8 8 40
Appendix A HA029280
Page A - 2 Issue 5 Mar 08
Communications specification
Ethernet Communications
Type 10/100 base T (IEEE802.3)
Protocols TCP/IP, FTP, DHCP, BootP, ICMP.
Cable Type: CAT5
Maximum length: 100 metres
Termination: RJ45
Isolation IEEE802.3
RJ45 LED indicators Green: Indicates a 100MB link
Yellow: Indicates Ethernet activity
Modbus/Jbus (EIA422/485)
Connectors Shielded RJ45 connectors.
Protocol MODBUS/JBUS RTU master and slave
Data rate Selectable between 1200 and 38,400 Baud
Data format 8-bits, 1 or 2 stop bits, selectable parity
MODBUS data tables 64, configurable as registers or bits
Table length (max.) 200 registers or 999 bits
Memory allocated to tables 2000 bytes
Isolation Functional
Universal Serial Bus (USB)

Version 1.1 (2.0 devices are compatible)
Devices supported USB Bulk storage devices (‘Memory Stick’)
Isolation No signal isolation
Profibus
Safety Isolation (BS EN61010) Installation category II; Pollution degree 2
Any terminal to earth: 50 Vdc or RMS
Number of slave devices 124 Max. (83 with extended diagnostics)
Number of tables supported Maximum 250 (see table for maximum
number per type).
Baud rates supported 9.6kBaud; 19.2kBaud; 93.75kBaud, 187.5kBaud,
500kBaud, 1.5MBaud, 3.0MBaud, 6.0MBaud, 12.0MBaud.
Table No. required Max. per Max. no. of

Type per slave master data items
Cyclic input 1 124 Unlimited
Cyclic output 1 124 Unlimited
Extended diagnostics 1 124 Unlimited
Acyclic N/A 1 256
HA029280 Appendix A
FUNCTION BLOCKS SUPPORTED
CATEGORY BLOCK FUNCTION

BATCH BAT_CTRL Batch controller / interface
DISCREP Transmitted/received digital signal-match to diagnose plant faults
RECORD Storage/retrieval of analogue/digital values for runtime use
SFC_CON Sequence (SFC) control, selection and running
SFC_DISP Display/monitoring/control of remotely-running sequence (SFC)
SFC_MON Sequence (SFC) runtime monitoring
RCP_SET Recipe set
RCP_LINE Recipe Line
COMMS GW_CON To be issued later
GW_TBL To be issued later
GWProfM_CON Profibus DPV1 comms master
CONDITN AGA8DATA AGA8 calculation block for compressibility of gas mixtures
AN_ALARM Alarm, with absolute/deviation/rate alarms
CARB_DIFF On-line carbon diffusion modelling
CHAR 16-point analogue characteriser
DIGALARM Digital alarm
FILTER First-order filter
FLOWCOMP Computes flow-rate, corrected for pressure, temperature and density
GASCONC Contains gas concentration units in Mole% units
INVERT Analogue inversion block
LEAD_LAG Lead-lag
RANGE Re-ranges an analogue input
STEEL_SPEC Steel specification
UCHAR 16-point characteriser for analogue input blocks
CONFIG T800 System block
T2900 System block
Eycon-10 System block
Eycon-20 System block
CONTROL 3_TERM Incremental form of the PID block
ANMS Analogue manual station
AN_CONN Analogue connections
DGMS Digital manual stations
DG_CONN Digital connections
MAN_STAT Manual station, with connections to front panel displays
MODE Control mode selection, with push-button masking
PID PID control function
PID_LINK ‘Faceplate’ for SETPOINT/3_TERM/MAN_STAT/MODE combination
SETPOINT Generates a setpoint with bias, limits and alarms
SIM Simulates two first-order lags or capacity, with noise
TP_CONN Specifies up to nine fields as EEPROM ‘tepid data’ at power-down
CONVERT ENUMENUM Converts between enumerated number types
ENUMUINT Converts from enumerated type to integer type
UINTENUM Converts from integer to enumerated type
DIAG AGA8DIAG AGA8 block diagnostics
ALH_DIAG Alarm history statistics
ALINDIAG ALIN MAC/LLC diagnostics
AMC_DIAG Comms statistics on application master
DB_DIAG Database diagnostics
DDR_DIAG T800 data recording statistics
EDB_DIAG External database diagnostics block
Appendix A HA029280
FUNCTION BLOCKS SUPPORTED (Cont.)

DIAG (Cont.) EDB_TBL External database table
ELINDIAG ELIN Diagnostics
EMAPDIAG Ethernet mapping diagnostic
FDDADIAG FTP transfer from logging
IDENTITY Check list
ISE_DIAG Options and features
NATPDIAG Audit Trail Provider diagnostics
NATCDIAG Audit Trail Consumer diagnostics
PBUSDIAG Profibus diagnostics
PMC_DIAG Profibus diagnostics
PNL_DIAG Front panel information
PRPDIAG Port Resolution Protocol diagnostics
RSRCDIAG Database and system resource diagnostics
SFC_DIAG Sequence diagnostics
XEC_DIAG Task diagnostics
I/O AN_DATA Analogue data (e.g. for carbon diffusion)
LOGIC AND4 4-input AND Boolean function
COMPARE Indicates greater/less than/equal of two inputs
COUNT UP/DOWN pulse counter with START/END count target
LATCH D-type flip-flop function
NOT NOT Boolean function
OR4 4-input OR Boolean function
PULSE Pulse output (monostable) function
XOR4 4-input exclusive-OR Boolean function
MATHS ACTION Action control, with use of stored variables and elapsed time
ADD2 Adds two inputs
DIGACT Action control with use of stored digital variables and elapsed time
DIV2 Divides two inputs
EXPR Free-format maths expression with up to four inputs
MUL2 Multiplies two inputs
SUB2 Subtracts two inputs
OPERATOR EVENT Act upon as audit trail event
PNL_CMD Panel Command
PNL_DLG Panel dialogue generation
PNL_MSG Panel message generation
PNL_ACC Access to panel system
ORGANISE AREA Associates GROUP blocks into an AREA
GROUP Associates display and recorder channels into a GROUP
LOGDEV Specifies and controls access to an archive medium
LGROUP Collects data from point blocks for archiving
LOGGRPEX LGROUP extension block
LPTDEV Printer device block
PGROUP Printer Group
RECORDING DR_ALARM Filters alarms and events
DR_ANCHP Data recording analog channel point block
DR_DGCHP Data recording digital channel point block
DR_REPRT Report generator
SELECTOR 2OF3VOTE Selects ‘best’ input from three (averaging only the inputs in tolerance)
ALC Alarm collection producing a common logic O/P
SELECT Outputs the highest, middle and lowest inputs, or median of 2, 3 or 4
SWITCH Single-pole double-throw switch for analogue signals
TAG Specifies a user task (loop) tagname, selected from list of eight tags
HA029280 Appendix A
FUNCTION BLOCKS SUPPORTED (Cont.)

SPP SPP_CTRL Monitors, schedules and controls program running
SPP_DIG Wires out digital setpoints from the setpoint program
SPP_EXT Programmer extended functions
SPP_RAMP Local Ramp
TIMING DELAY Delay for dead-time applications
RATE_ALM Up/down-rate alarm applied to PV (OP held at last non-alarm value)
RATE_LMT Rate-limiter and ramp generator
SEQ Multi-segment slope/level/time, 15 O/P digitals
SEQE SEQ extender
TIMEDATE Clock and calendar event
TIMER Timer
TOTAL Totaliser (integrator) for analogue variable
TOT_CON Totalisation connector block
TPO Time proportioning o/p block. Produces a pulse stream with mark/space
ratio proportional to its (analogue) input value.
Appendix A HA029280
VISUAL SUPERVSOR HANDBOOK
APPENDIX B: OPTIONS UPDATE
B1 INTRODUCTION
The Software Options Utility allows the software options fitted in the instrument to be changed as follows:
1. The utility provides a ‘Change code’.

2. The user contacts the supplier with the Change Code.
3. The supplier provides a further ‘Validation’ code which is used to enable the relevant options.
B2 SOFTWARE OPTIONS UTILITY ACCESS
1. If necessary stop and unload any application currently running, and operate the SOFT OPS key in the MAINT
menu.
2 10:48:21 Appl'n Manager 11/04/06

Press SYSTEM key
File: Colours
1 ACCESS SYSTEM ALARMS State: STOPPED
System
SUMMARY APPLN
3 6
SETUP CLONING
Press UNLOAD
Press APPLN key
10:48:34 Appl'n Manager 11/04/06
Application

4
Press APP MGR
SETUP MAINT EVT LOG
10:47:57 Appl'n Manager 11/04/06
File: Colours LOAD LD+RUN DELETE

State: RUNNING
8 Press MAINT
7
Press menu key
STOP Maintenance
5
Press STOP 9 CLONING FILE MGR
Press
SOFT OPS
Figure B2a Access to the SOFT OPS key.
(Continued)
HA029280 Appendix B
Issue 5 Mar 08 Page B - 1
VISUAL SUPERVSOR HANDBOOK
B2 SOFTWARE OPTIONS UTILITY ACCESS (Cont.)
The first Software Option Change page appears.

2. Modify the displayed options as required, and press the ‘Change’ key. The second Software Option Change page
appears.
3. Contact the supplier of the instrument with the MAC address and Change Code as presented on the screen.
4. The supplier will provide a Validation Code, which must be entered and the ‘Validate’ key pressed.
5. The unit will have to be power cycled before the changes are effective.
11:32:07 Software Option Chan 1 1 / 0 4 / 0 6
Modbus Master: YES 10

Edit options as
Software Opt1: L2:Batch Manager
required
Auditor: No
11
Press CHANGE CHANGE CANCEL
11:32:57 Software Option Chan 1 1 / 0 4 / 0 6

Contact your representative and 12
supply the information below. Enter Phone-in with
the validation code you are given and MAC address and
press 'VALIDATE'. Change code
MAC Address: 00:0A:8D:00:00:00
13 Change Code: 3154131968
Enter Validation Validation Code: 0000000000
Code and press
VALIDATE CANCEL
VALIDATE
Figure B2b Software Options Change pages
Appendix B HA029280
Page B - 2 Issue 5 Mar 08
APPENDIX C: REFERENCE
C1 ASCII CODES
The following table contains representations of the characters set (UNICODE Latin-1) available on the unit.
Character Code Character Code Character Code Character Code

Space 20 P 50 D D0
! 21 Q 51 ¡ A1 Ñ D1
“ 22 R 52 ¢ A2 Ò D2
# 23 S 53 £ A3 Ó D3
$ 24 T 54 ¤ A4 Ô D4
% 25 U 55 ¥ A5 Õ D5
& 26 V 56 A6 Ö D6
‘ 27 W 57 § A7 × D7
( 28 X 58 ¨ A8 ∅ D8
) 29 Y 59 © A9 Ù D9
* 2A Z 5A ª AA Ú DA
+ 2B [ 5B « AB Û DB
, 2C \ 5C ¬ AC Ü DC
- 2D ] 5D – AD ´
Y DD
. 2E ^ 5E ® AE DE
/ 2F _ 5F ¯ AF ß DF
0 30 ` 60 º B0 à E0
1 31 a 61 ± B1 á E1
2
2 32 b 62 B2 â E2
3
3 33 c 63 B3 ã E3
4 34 d 64 ´ B4 ä E4
5 35 e 65 µ B5 å E5
6 36 f 66 ¶ B6 æ E6
7 37 g 67 · B7 ç E7
8 38 h 68 ç B8 è E8
1
9 39 i 69 B9 é E9
0
: 3A j 6A BA ê EA
; 3B k 6B » BB ë EB
1
< 3C l 6C /4 BC ì EC
1
= 3D m 6D /2 BD í ED
3
> 3E n 6E /4 BE î EE
? 3F o 6F ¿ BF ï EF
@ 40 p 70 À C0 ∂ F0
A 41 q 71 Á C1 ñ F1
B 42 r 72 Â C2 ò F2
C 43 s 73 Ã C3 ó F3
D 44 t 74 Ä C4 ô F4
E 45 u 75 Å C5 õ F5
F 46 v 76 Æ C6 ö F6
G 47 w 77 Ç C7 ÷ F7
H 48 x 78 È C8 ø F8
I 49 y 79 É C9 ù F9
J 4A z 7A Ê CA ú FA
K 4B { 7B Ë CB û FB
L 4C | 7C Ì CC ü FC
M 4D } 7D Í CD y´ FD
N 4E ~ 7E Î CE FE
O 4F Ï CF ÿ FF
Table C ASCII codes
HA029280 Appendix C
Issue 5 Mar 08 Page C - 1
C2 GLOSSARY
Application An application consists of a LIN database, a User Screen page set, possibly some Setpoint
Programs, Sequences and Dictionary files, plus actions, profile files and sometimes GSD files
for third party devices.
The application embodies the instrument’s control strategy, and also determines the behaviour
of its user interface.
Archiving Archiving is the process of recording the history of a set of data values onto a removable
floppy disk. The data can only be ‘replayed’ with an off-line tool. In this context, archiving is
the same as ‘logging’. See also ‘Logging’ and ‘Log group’.
Brown-out A brown-out is a transient power variation or partial power failure severe enough to provoke an
automatic re-set in the Visual Supervisor.
Configuration Configuration is the process of specifying the components of an application in order to deter-
mine the performance and behaviour of an instrument. Configuration is usually carried out by
the manufacturer or by an OEM. See also ‘Application’ and ‘LIN database’.
Configurator A configurator is a user interface or software tool that provides the editing capability to
configure the instrument.
Configurer A configurer is any person who configures, or who is responsible for configuring, the instru-
ment.
COSHH Control of Substances Hazardous to Health
Customisation This is the procedure by which a user can construct a Home page and sometimes other user
screens.
Database See ‘LIN database’.
Dictionary files Dictionary files hold items of text for display on the screen. Users can edit, replace or delete
many of the items.
EMC Electromagnetic compliance
Home page The Home page is that which is displayed on power-up, and to which the display returns when
no data has been entered during a specified time-out period. It can also be called up at any time.
The Home page will either stand on its own or be the root page of a hierarchy of user-written
pages.
LIN database LIN database stands for Local Instrument Network database, a Eurotherm proprietary facility.
For any Eurotherm instrument the LIN database is a set of software function blocks that
constitutes its control strategy. The manufacturer and/or OEMs select particular function blocks
from a library of LIN database function blocks to build a particular control strategy for that
instrument. The LIN database of an instrument forms part of its ‘application’. See ‘Applica-
tion’.
Log group A log group is a set of points that are logged (archived) together onto removable media for
review off-line.
Logging Same as ‘Archiving’
OEM Original Equipment Manufacturer. I.E. any organisation that buys Visual Supervisors, incorpo-
rates them into its own products, and sells these products onto other customers under its own
name.
Power outage A total power failure for a short time
Process variable (PV) Process Variable. Examples are temperature, pressure or valve aperture.
Ramp A ramp is
1 a generic term for all types of programmed change in a setpoint value. Can be a ‘dwell’ (no
change at all), a ‘step’ (an instantaneous change), a ‘ramp at’, a ‘ramp to’, a ‘servo to setpoint’
or a ‘servo to PV’ (all linear changes).
2 two of the types mentioned above (‘ramp at’ and ‘ramp to’).
Recording Recording is the process of saving the history of a set of data values in the instrument’s non-
volatile memory. The data can survive a power outage, and can be replayed on the instrument.
Appendix C HA029280
Page C - 2 Issue 5 Mar 08
C2 GLOSSARY (Cont.)
RFI Radio frequency interference

SCADA Supervisory Control and Data Acquisition
Sequences Sequences are programs that users may have written to deal with any particular events,
circumstances or requirements in the process under control.
Setpoint program (SP) A setpoint program is a strategy to control a number of process variables such as temperature,
pressure and valve apertures, over a period that can range, with the Visual Supervisor, from
less than a minute to more than seven weeks.
Standard Interface The Visual Supervisor Standard Interface is the name for the non-customised version of the
user interface for the instrument. It’s the default, factory-set interface, with no customised
features.
Start-up strategy This defines the way in which the process under control recovers from a partial or total power
loss. The Engineer may select one of several start-up strategies.
USB Universal Serial Bus. High speed serial communications bus.
User screen A user screen is a page or a set of linked pages for display on the Visual Supervisor, created by
a user.
HA029280 Appendix C
Issue 5 Mar 08 Page C - 3
Appendix C HA029280
Page C - 4 Issue 5 Mar 08
INDEX
Symbols A (Cont.)
32-bit register ........................................................ 8 - 18 APPLN ................................................................... 4 - 20
Archiving
A Alarm history ..................................................... 3 - 16
Abort ........................................................................ 2 - 8 Interval ............................................................... 4 - 16
Program ............................................................... 3 - 8 Area display .......................................................... 3 - 18
Access ........................................................... 2 - 5, 2 - 6 Arhive file transfer .................................................. 7 - 1
By user ID .......................................................... 2 - 15 Attributes column .................................................. 4 - 32
Control ............................................................... 4 - 27 Audit Trail ................................................................ 6 - 1
Display pane ..................................................... 2 - 12 Filtering ................................................................ 6 - 2
Levels ................................................................ 6 - 11 B
Pane .................................................................... 2 - 2
Standard ............................................................ 2 - 12 Bargraph display mode
to configuration ................................................. 2 - 12 Horizontal bars .................................................. 3 - 23
Account Properties ............................................... 4 - 33 Vertical bars ...................................................... 3 - 22
Acknowledge Batch ........................................................................ 2 - 6
Alarms ............................................................... 3 - 15 Abort .................................................................. 3 - 32
Messages .......................................................... 3 - 15 Create ................................................................ 3 - 33
Action Disabled ..................................................... 6 - 11 Customising ...................................................... 3 - 31
Adding new users ................................................. 4 - 33 Dictionary .......................................................... 5 - 60
Admin only ............................................................. 4 - 32 Files ................................................................... 5 - 61
Agent types ........................................................... 5 - 46 Hold ................................................................... 3 - 32
Alarm Initiation ............................................................. 3 - 32
Forms ................................................................. 5 - 54 Load ................................................................... 3 - 31
Alarm/event customisation ................................... 5 - 26 Maintenance ...................................................... 4 - 56
Alarms .............................................. 2 - 5, 2 - 6, 8 - 11 Monitoring .......................................................... 3 - 32
Acknowledgement ................................ 2 - 11, 3 - 15 Phases ............................................................... 5 - 62
Active/Cleared/Ack'ed ........................................ 6 - 2 Recipe selection ............................................... 3 - 31
Display pane ....................................................... 2 - 9 Battery replacement ............................................... 9 - 1
Field ..................................................................... 8 - 7 Baud rate ............................................................... 8 - 14
History ............................................................... 2 - 10 Bitfields .................................................................... 8 - 7
Archiving ........................................................ 3 - 16 Block ........................................................................ 8 - 4
Display, addding notes to ............................. 3 - 15 Copy .................................................................... 8 - 8
Page .............................................................. 3 - 13 Creation ............................................................. 4 - 25
Time display .................................................. 3 - 13 Delete .................................................................. 8 - 8
Two-line display ................................ 2 - 11, 3 - 14 Events .................................................................. 6 - 2
Indication ........................................................... 3 - 18 Inspect ................................................................. 8 - 9
Log ..................................................................... 8 - 11 Overview .............................................................. 8 - 4
Names ............................................................... 5 - 48 Tagname .............................................................. 8 - 5
Pane .................................................................... 2 - 2 Type ..................................................................... 8 - 5
Responding to ................................................... 3 - 13 Value Change ...................................................... 6 - 2
Status .................................................................. 2 - 9 Brightness of display ............................................ 4 - 44
Summary ........................................................... 3 - 16 Brown-out .............................................................. 4 - 39
APP MGR .............................................................. 4 - 20 Time ................................................................... 4 - 40
APP SUM .............................................................. 4 - 20
Application C
Data ................................................................... 4 - 47 Cached alarms ........................................................ 6 - 2
Cloning .......................................................... 4 - 47 Capture (recipe) .................................................... 4 - 54
Importing ....................................................... 4 - 47 Changing
Saving ............................................................ 4 - 22 a segment ............................................................ 4 - 7
Deletion ............................................................. 4 - 23 Date/Time .......................................................... 4 - 41
Loading and Running ....................................... 4 - 23 Date/Time format .............................................. 4 - 43
Management ..................................................... 4 - 19 from Access level to User ID ............................ 4 - 30
Manager page ................................................... 4 - 20 Hot/Cold Start settings ..................................... 4 - 40
Reloading .......................................................... 4 - 52 Language .......................................................... 4 - 43
Selection ............................................................ 4 - 23 Setpoint value ..................................................... 4 - 6
Stopping ............................................... 4 - 21, 4 - 50 Start-up Strategy values ................................... 4 - 40
Summary page .................................................. 4 - 20
Unloading .......................................................... 4 - 22
HA029280 Index
Issue 5 Mar 08 Page i - 1
C (Cont.) D (Cont.)
Clock Setup page ................................................. 4 - 41 Deploy ..................................................................... 6 - 7
Cloning .................................................................. 4 - 46 Diagnostic .............................................................. 8 - 15
All data .............................................................. 4 - 49 Dictionary
Application data ................................................ 4 - 47 Error text ............................................................ 5 - 27
Instrument data ................................................. 4 - 48 Event text .......................................................... 5 - 29
System data ...................................................... 4 - 48 List of ................................................................... 5 - 1
Cold-Start .............................................................. 4 - 40 Programmer text ............................................... 5 - 34
Commission level access ..................................... 4 - 28 System text ............................................. 5 - 2–5 - 63
COMMS ................................................................. 4 - 35 User text ............................................................ 5 - 34
Communications ................................................... 4 - 35 Digital ........................................................ 8 - 15, 8 - 17
Available protocols ........................................... 4 - 36 Disable User ID ........................................... 4 - 32, 6 - 4
Parameter setting ............................................. 4 - 35 Display Brightness ................................................ 4 - 44
Profiles ............................................................... 4 - 47 Display mode
Setup ................................................................. 8 - 13 Bargraph
Specification ........................................................ A - 3 Horizontal ...................................................... 3 - 23
Compound ............................................................... 8 - 4 Vertical ........................................................... 3 - 22
Compound. .............................................................. 8 - 5 Faceplate ........................................................... 3 - 22
Configuration Horizontal with faceplate .................................. 3 - 25
Database ............................................................. 8 - 3 Numeric ............................................................. 3 - 22
Modbus .............................................................. 8 - 12 Vertical fullwidth ................................................ 3 - 25
Configurator Vertical with faceplate ...................................... 3 - 23
Control ................................................................. 8 - 1 Down key ................................................................. 2 - 3
Mode, selecting ................................................... 8 - 1 Downloading a configuration ................................. 8 - 1
Running ............................................................... 8 - 2 DP .......................................................................... 8 - 18
Confirm only .......................................................... 6 - 11 Dwell ........................................................................ 4 - 4
Connection types .................................................... 8 - 8
Connections .................................................. 8 - 6, 8 - 8 E
Consumer selection ................................................ 6 - 2 E:MICRO_D.DBF .................................................. 8 - 10
Control EDIT ......................................................................... 2 - 8
Configurator ........................................................ 8 - 1 Editing
Database ........................................................... 4 - 47 Alarm names ..................................................... 5 - 48
Selecting efficiency ............................................. 8 - 1 Databases ........................................................... 8 - 5
Copy blocks ............................................................. 8 - 8 Error messages ................................................. 5 - 28
Count ..................................................................... 8 - 16 Event messages ............................................... 5 - 33
Create Blocks ........................................................ 4 - 25 Function block names ...................................... 5 - 48
Cursor ....................................................... 3 - 24, 3 - 26 Recipes .............................................................. 4 - 52
Customisation of Panel ........................................ 5 - 24 EIA485 connection .................................................. 1 - 7
Customising ............................................................ 5 - 1 Electrical installation ............................................... 1 - 6
D Profibus Master units ........................................ 10 - 4
Electronic signatures ............................................ 6 - 10
Daily ELIN ....................................................................... 4 - 37
File names ......................................................... 4 - 16 End action ............................................................. 4 - 12
Files ................................................................... 3 - 11 Engineer level access .......................................... 4 - 28
Data integrity ......................................................... 3 - 12 Enumerations ........................................................ 5 - 49
Database Error
Name & address ................................................. 8 - 9 Message editing ................................................ 5 - 28
Names ..................................................... 5 - 2, 5 - 48 Text dictionary ....................................... 5 - 27–5 - 63
Date format selection ........................................... 4 - 42 Ethernet ................................................................. 4 - 37
Daylight saving ..................................................... 4 - 41 Connection .......................................................... 1 - 8
DB Write ................................................................ 8 - 18 LED interpretation ............................................... A - 3
Decimal point .......................................................... 8 - 6 Event
Delete ....................................................... 4 - 19, 4 - 23 Log ......................................................... 3 - 17, 8 - 11
Blocks .................................................................. 8 - 8 Message
Deleting Editing ............................................................ 5 - 33
Files from disk ................................................... 3 - 12 New language ............................................... 5 - 33
Segments ............................................................ 4 - 9 Priorities ............................................................ 5 - 33
User IDs ............................................................. 4 - 32 Text dictionary ................................................... 5 - 29
Exporting application data .................................... 4 - 47
Index HA029280
Page i - 2 Issue 5 Mar 08
F I (Cont.)
F keys ...................................................................... 2 - 3 Information entry ..................................................... 2 - 5
Faceplate display mode ....................................... 3 - 22 Initial menu .............................................................. 8 - 2
Field ....................................................................... 8 - 17 Initial page declaration ......................................... 5 - 45
File Input ......................................................................... 8 - 6
Copy and delete ................................................ 4 - 51 Inrush current .......................................................... 1 - 6
Filename specification ...................................... 8 - 10 Inserting a Segment ............................................... 4 - 8
Header .................................................. 5 - 55, 5 - 61 Inspect blocks ......................................................... 8 - 9
Management ..................................................... 3 - 12 Installation
Manager ............................................................ 4 - 50 Electrical .............................................................. 1 - 6
System ................................................................. 7 - 1 Profibus Master units .................................... 10 - 4
Type ................................................................... 4 - 16 Mechanical .............................................. 1 - 3, 11 - 1
Text, Hourly, Daily ......................................... 3 - 11 Profibus Master units .................................... 10 - 2
Utility .................................................................. 8 - 11 Instr No ..................................................... 8 - 14, 8 - 16
Files with Capture Variables ................................ 5 - 57 Instrument
Files with Monitor Variables ................................. 5 - 58 Data cloning ...................................................... 4 - 48
Flush-mounting option ............................... 11 - 1–11 - 4 Setting up .......................................................... 4 - 35
Form files ............................................................... 5 - 50 Intellectual Property Right Protection ................. 4 - 55
Format ....................................................... 8 - 11, 8 - 18 INTERFACE .......................................................... 8 - 13
Forms ..................................................................... 4 - 47 IPRP ...................................................................... 4 - 55
FTP ........................................................................ 4 - 32 Iterations
Logon ................................................................... 7 - 1 Changing default number ................................. 4 - 13
Timeout ................................................................ 7 - 1 Number of ............................................................ 3 - 6
Transfer ............................................................. 4 - 18
Function block L
Database configuration ...................................... 8 - 4 Labelling symbols ................................................... 1 - 1
Detail display ..................................................... 4 - 27 Language selection .............................................. 4 - 42
Display order ..................................................... 4 - 26 LD+RUN ................................................... 4 - 19, 4 - 23
Faceplate ........................................................... 3 - 20 LED indicators (RJ45) ............................................ 1 - 7
PID ................................................................. 3 - 21 Left key .................................................................... 2 - 3
Ramp ............................................................. 3 - 20 LIN (Local Instrument Network) ............................. 8 - 9
Manager ............................................................ 4 - 24 Lin Mode .................................................................. 6 - 2
Names ............................................................... 5 - 48 Line type ................................................................ 8 - 14
Functions ............................................................... 8 - 16 LINfiler ..................................................................... 8 - 3
Load .............................................. 3 - 31, 4 - 19, 4 - 23
G Utility .................................................................. 8 - 10
Glossary .................................................................. C - 2 Load/Save program Id setting ................................ 3 - 2
Group display ........................................................ 3 - 18 Locked ................................................................... 4 - 28
GW index ............................................................... 8 - 12 Log on .................................................................... 2 - 12
GWF files ............................................................... 10 - 1 Logging ........................................................ 2 - 6, 3 - 11
GWProfM_CON block ........................................... 10 - 4 Configuration ..................................................... 4 - 16
Data groups ....................................................... 4 - 15
H File type ............................................................. 4 - 16
Initiation ............................................................. 4 - 15
Hexadecimal fields ................................................. 8 - 7
Interval ............................................................... 4 - 16
HOLD ....................................................................... 2 - 8
Name types ....................................................... 4 - 16
Holdback properties ................................................ 4 - 9
Pane ........................................................ 2 - 2, 2 - 12
Home page declaration ........................................ 5 - 45
Logic states ............................................................. 8 - 7
HOME/USER SCREENS ........................................ 2 - 6
Horizontal display with faceplates ....................... 3 - 25 M
Hot start ................................................................. 4 - 40
Time ................................................................... 4 - 40 Main pane ...................................................... 2 - 2, 2 - 5
Hourly MAINT Key .............................................................. 6 - 6
File names ......................................................... 4 - 16 MAINT key ............................................................. 4 - 34
Files ................................................................... 3 - 11 Maintenance (security access) .............................. 6 - 6
Master/Slave
I Connection .......................................................... 1 - 7
Selection .............................................................. 1 - 7
I/O Calibration ....................................................... 8 - 10
Max. Login attempts ............................................... 6 - 5
Id value .................................................................... 3 - 2
Mechanical installation ............................... 1 - 3, 11 - 1
Identity ..................................................................... 6 - 4
Profibus Master units ........................................ 10 - 2
Importing application data .................................... 4 - 47
HA029280 Index
M (Cont.) P (Cont.)
Menu key ................................................................. 2 - 3 Port no ................................................................... 8 - 14
Message Power requirements ............................................... 1 - 6
Active/Cleared/Ack'ed ........................................ 6 - 2 PRE-PLOT ............................................................... 2 - 8
Display/Acknowledge ....................................... 3 - 15 Preventive maintenance ......................................... 1 - 2
Indicator ............................................................. 2 - 10 PREVIEW ................................................................ 2 - 8
Minimum Profibus Master option ......................................... 10 - 1
Alarm/event priority ............................................ 6 - 2 Connector Pinout .............................................. 10 - 4
ID length .............................................................. 6 - 5 GWProfM_CON block ....................................... 10 - 4
Password length ................................................. 6 - 5 Program
MOD Write ............................................................. 8 - 19 Abort .................................................................... 3 - 8
Modbus Changing the name of ...................................... 4 - 11
Configuration ..................................................... 8 - 12 Creation ............................................................... 4 - 1
Connection .......................................................... 1 - 7 Duration (maximum) ........................................... 4 - 8
Mode ...................................................................... 8 - 12 Editing .................................................................. 4 - 1
Monitor ..................................................................... 2 - 8 Editor, Access to ................................................ 4 - 3
Monitoring a program ................................. 3 - 9, 3 - 10 Hold ..................................................................... 3 - 8
Multiple copy ......................................................... 4 - 18 Iterations .............................................................. 3 - 6
Monitoring a ........................................................ 3 - 9
N Pane .......................................................... 2 - 2, 2 - 7
Name type ............................................................. 4 - 16 Properties .......................................................... 4 - 11
Navigation keys ...................................................... 2 - 3 Running
Network ................................................................... 8 - 9 From a point .................................................... 3 - 3
Audit Trail ............................................................ 6 - 1 From date ........................................................ 3 - 5
FB manager key ................................................ 4 - 25 Running more than one ...................................... 3 - 2
Setup page .......................................................... 8 - 9 Scheduling ........................................................... 3 - 4
Specification ........................................................ A - 3 Status .................................................................. 2 - 7
New user ID ................................................ 4 - 33, 6 - 5 PROGRAMMER ...................................................... 2 - 5
No Confirmation .................................................... 6 - 11 Programmer ............................................................ 2 - 6
Node number configuration .................................... 6 - 8 Menu .................................................................... 2 - 8
Numeric display mode .......................................... 3 - 22 Access ............................................................. 2 - 7
Text dictionary ................................................... 5 - 34
O Programs ................................................................. 2 - 8
Programs/Recipes ................................................ 4 - 47
Offset ..................................................................... 8 - 16 PROPERTIES key ................................................ 4 - 33
Operator Protocols (communications) ................................. 4 - 36
Access level ...................................................... 4 - 28
Note ..................................................................... 6 - 2 Q
Option key ............................................................... 2 - 3
Options menu fields ................................................ 8 - 6 Question mark ....................................................... 2 - 10
Overview .................................................................. 2 - 6 R
Data field entry .................................................... 8 - 5
Ramp ....................................................................... 4 - 4
P Ramp at ............................................................... 4 - 4
Pan control ............................................... 3 - 24, 3 - 26 Ramp to ............................................................... 4 - 4
Panel Type changing ..................................................... 4 - 4
Agent declaration .............................................. 5 - 43 Rate ms ................................................................... 8 - 5
Customisation ................................................... 5 - 24 Rate units selection .............................................. 4 - 12
Driver declaration ............................................. 5 - 44 Recipe ........................................................... 2 - 5, 2 - 6
Navigation ............................................... 5 - 2, 5 - 35 Adding ............................................................... 4 - 53
File ................................................................. 5 - 35 Capture .............................................................. 4 - 54
Parameter Dictionary .......................................................... 5 - 59
Database ............................................................. 8 - 5 Downloading ..................................................... 3 - 27
Units ..................................................................... 8 - 6 Files ................................................................... 5 - 55
Values .................................................................. 8 - 6 Management ..................................................... 4 - 52
Parity ..................................................................... 8 - 14 Monitoring .......................................................... 3 - 29
Password Pane .................................................................... 2 - 2
Editing ................................................................ 4 - 27 Reference column ................................................. 4 - 32
Expiry ................................................................... 6 - 5 Refresh rate ............................................................ 8 - 5
Pop-up menu ........................................................... 2 - 6 Register .................................................... 8 - 15, 8 - 17
Remote Access ....................................................... 7 - 1
Index HA029280
R (Cont.) S (Cont.)
Remote device ...................................................... 8 - 11 System ................................. 2 - 5, 2 - 6, 4 - 20, 4 - 35
Report forms ......................................................... 5 - 50 Data
Retire User ID ......................................................... 6 - 4 Cloning .......................................................... 4 - 48
Revision ................................................................... 6 - 7 Importing/exporting ....................................... 4 - 48
Right key ................................................................. 2 - 3 Event .................................................................... 6 - 2
Root page declaration .......................................... 5 - 45 Summary Page ................................................... 2 - 4
RUN ......................................................................... 2 - 8 Text
FROM .................................................................. 2 - 8 Editing .............................................................. 5 - 3
Running multiple programs .................................... 3 - 2 New languages ............................................... 5 - 3
S T
Safety notes ............................................................ 1 - 1 T500 LINtools .......................................................... 8 - 1
Save .......................................................... 4 - 19, 4 - 22 Table ...................................................................... 8 - 15
Utility .................................................................. 8 - 10 Menus ................................................................ 8 - 17
Scan count ............................................................ 8 - 16 Talk through ........................................................... 4 - 36
SCHEDULE ............................................................. 2 - 8 TCP Master/slave ................................................. 8 - 13
Scheduling a program ............................................ 3 - 4 Terminal Configurator
Screen saver configuration .................................. 4 - 44 Modbus Configuration
Security access page ............................................. 6 - 3 TABLES command ........................................ 8 - 15
Segment Terminal Mode ........................................................ 8 - 2
Changing duration of .......................................... 4 - 8 Text files ................................................................ 3 - 11
Changing the identifier ....................................... 4 - 7 Names ............................................................... 4 - 16
Deletion of ........................................................... 4 - 9 The dictionary ......................................................... 5 - 3
Insertion ............................................................... 4 - 8 Tick Rate ............................................................... 8 - 16
Skip ...................................................................... 3 - 7 Time display in Alarm history ............................... 3 - 13
Timing display ................................................... 4 - 14 Time format ........................................................... 4 - 43
Serial comms connection ....................................... 1 - 7 Timeout .................................................................. 8 - 14
Serial master/slave ............................................... 8 - 13 Display brightness ............................................ 4 - 44
Server number ........................................................ 8 - 5 Page Display ..................................................... 4 - 44
Servo to ................................................................... 4 - 4 Pop-up menu ..................................................... 4 - 44
Setpoint Title bar .................................................................... 8 - 5
Editing .................................................................. 4 - 4 Title line ................................................................. 5 - 56
Name Trend
Saving ............................................................ 4 - 13 Displays ............................................................. 3 - 18
Setting and re-setting passwords ........................ 4 - 28 Review .................................................. 3 - 24, 3 - 26
SETUP ...................................................... 4 - 35, 8 - 13 Two-line display (Event Log) ................................ 3 - 17
SFCs ...................................................................... 4 - 47 Type ....................................................................... 8 - 15
Sign & Authorise ................................................... 6 - 11 of block ................................................................ 8 - 5
Signature ............................................................... 6 - 11
Configuration ..................................................... 6 - 11 U
Single copy ............................................................ 4 - 18 UNLOAD ................................................... 4 - 19, 4 - 22
Slave connection .................................................... 1 - 7 Unpacking ................................................... 1 - 3, 11 - 1
Specification Unused .................................................................. 8 - 15
Communications ................................................. A - 3 Up key ..................................................................... 2 - 3
General ................................................................ A - 1 UPB files ................................................................ 10 - 1
Standard Update period ......................................................... 8 - 5
Access ............................................................... 2 - 12 USB connector ........................................................ 1 - 8
Interface .................................................... 2 - 1, 2 - 5 User
START ...................................................... 4 - 19, 4 - 23 Attributes ............................................................. 6 - 4
Start/Stop utilities ................................................. 8 - 10 Defined keys ....................................................... 2 - 3
Startup Strategy .................................................... 4 - 39 ID access ........................................................... 2 - 15
STATS key ................................................... 4 - 34, 6 - 6 ID control ............................................................. 6 - 3
Step ......................................................................... 4 - 4 ID management ................................................ 4 - 31
Stop .......................................................... 4 - 19, 4 - 21 ID password system ......................................... 4 - 30
Bits ..................................................................... 8 - 14 Name ................................................................... 6 - 4
Supply voltage Pages ................................................................. 4 - 47
Requirements ...................................................... 1 - 6 Properties ............................................................ 6 - 5
Wiring .................................................................. 1 - 6 Text dictionary ................................................... 5 - 34
Switch on ................................................................. 2 - 1 Timeout ................................................................ 6 - 5
Symbols used on labels ......................................... 1 - 1 User-defined names ............................................... 8 - 5
HA029280 Index
U (Cont.) W
Utilities ................................................................... 8 - 10 Width ...................................................................... 8 - 18
UYF files ................................................................ 5 - 51 Wild character ....................................................... 8 - 11
UYR files ............................................................... 5 - 55 Wiring
UYT files ................................................................ 5 - 54 Ethernet ............................................................... 1 - 8
Profibus Master units ........................................ 10 - 4
V Serial comms ...................................................... 1 - 7
Value ...................................................................... 8 - 19 Supply voltage .................................................... 1 - 6
Variable lines (Recipe files) ................................. 5 - 56 to I/O units ........................................................... 1 - 9
VDU package, quitting ............................................ 8 - 3 Writable dictionary ................................................ 5 - 58
Vertical display mode
Full width ........................................................... 3 - 25 Z
With faceplate ................................................... 3 - 23 Zoom control ............................................ 3 - 24, 3 - 26
View only ............................................................... 4 - 32
Voltage range .......................................................... 1 - 6
VT100 mode ............................................................ 8 - 2
Index HA029280
Inter-Company sales and service locations
AUSTRALIA Sydney HONG KONG & CHINA NORWAY Oslo
Eurotherm Pty. Ltd. Eurotherm Limited North Point Eurotherm A/S
Telephone (+61 2) 9838 0099 Telephone (+85 2) 28733826 Telephone (+47 67) 592170
Fax (+61 2) 9838 9288 Fax (+85 2) 28700148 Fax (+47 67) 118301
E-mail info.au@eurotherm.com E-mail info.hk@eurotherm.com E-mail info.no@eurotherm.com
AUSTRIA Vienna Guangzhou Office POLAND Katowice

Telephone (+86 20) 8755 5099 Invensys Eurotherm Sp z o.o
Eurotherm GmbH
Fax (+86 20) 8755 5831 Telephone (+48 32) 218 5100
Telephone (+43 1) 7987601
E-mail info.cn@eurotherm.com Fax (+48 32) 217 7171
Fax (+43 1) 7987605
E-mail info.pl@eurotherm.com
E-mail info.at@eurotherm.com
Beijing Office
Telephone (+86 10) 6567 8506
Fax (+86 10) 6567 8509 SPAIN Madrid
BELGIUM & LUXEMBOURG Moha E-mail info.cn@eurotherm.com Eurotherm España SA
Eurotherm S.A/N.V. Telephone (+34 91) 661 6001
Telephone (+32) 85 274080 Shanghai Office Fax (+34 91) 661 9093
Fax (+32 ) 85 274081 Telephone (+86 21) 6145 1188 E-mail info.es@eurotherm.com
E-mail info.be@eurotherm.com Fax (+86 21) 6145 1187
E-mail info.cn@eurotherm.com
SWEDEN Malmo
BRAZIL Campinas-SP INDIA Chennai Eurotherm AB
Eurotherm Ltda. Eurotherm India Limited Telephone (+46 40) 384500
Telephone (+5519) 3707 5333 Telephone (+9144) 2496 1129 Fax (+46 40) 384545
Fax (+5519) 3707 5345 Fax (+9144) 2496 1831 E-mail info.se@eurotherm.com
E-mail info.br@eurotherm.com E-mail info.in@eurotherm.com
SWITZERLAND Wollerau
IRELAND Dublin Eurotherm Produkte (Schweiz) AG
DENMARK Copenhagen
Eurotherm Ireland Limited Telephone (+41 44) 787 1040
Eurotherm Danmark AS
Fax (+41 44) 787 1044
Telephone (+45 70) 234670 Telephone (+353 1) 4691800
E-mail info.ch@eurotherm.com
Fax (+45 70) 234660 Fax (+353 1) 4691300
E-mail info.dk@eurotherm.com E-mail info.ie@eurotherm.com
UNITED KINGDOM Worthing
Eurotherm Limited
FINLAND Abo ITALY Como Telephone (+44 1903) 268500
Eurotherm Finland Eurotherm S.r.l Fax (+44 1903) 265982
Telephone (+358) 22506030 Telephone (+39 031) 975111 E-mail info.uk@eurotherm.com
Fax (+358) 22503201 Fax (+39 031) 977512 Web www.eurotherm.co.uk
E-mail info.fi@eurotherm.com E-mail info.it@eurotherm.com
U.S.A Leesburg VA
FRANCE Lyon KOREA Seoul Eurotherm Inc.
Eurotherm Automation SA Eurotherm Korea Limited Telephone (+1 703) 443 0000
Telephone (+33 478) 664500 Telephone (+82 31) 2738507 Fax (+1 703) 669 1300
Fax (+33 478) 352490 Fax (+82 31) 2738508 E-mail info.us@eurotherm.com
E-mail info.fr@eurotherm.com E-mail info.kr@eurotherm.com Web www.eurotherm.com
ED54
GERMANY Limburg NETHERLANDS Alphen a/d Rijn
Eurotherm Deutschland GmbH Eurotherm B.V.
Telephone (+49 6431) 2980 Telephone (+31 172) 411752
Fax (+49 6431) 298119 Fax (+31 172) 417260
E-mail info.de@eurotherm.com E-mail info.nl@eurotherm.com
E U ROT H E R M ®
EUROTHERM LIMITED
Faraday Close, Durrington, Worthing, West Sussex, BN13 3PL
Telephone: +44 (0)1903 268500 Facsimile: +44 (0)1903 265982
e-mail: info.uk@eurotherm.com
Website: http://www.eurotherm.co.uk
Specification subject to change without notice. ©Eurotherm Limited. HA029280/5 (CN24241)

Invensys, Eurotherm, the Eurotherm logo, Chessell, EurothermSuite, Mini8, EPower, Eycon, Eyris and Wonderware
are trademarks of Invensys plc, its subsidiaries and affiliates. All other brands may be trademarks of their respec-
tive owners.

Eycon HA029280 5

Uploaded by

Copyright:

Available Formats

Eycon HA029280 5

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Eycon HA029280 5

Uploaded by

Copyright:

Available Formats

Eycon™10/20

Manufacturer's name: Eurotherm Limited

Manufacturer's address: Faraday Close, Worthing, West Sussex,

Product type: Visual Supervisor

Models: Eycon-10 Status level A1 and above

Safety specification: EN61010-1: 2001

EMC emissions specification: EN61326-1: 1997 Class A

EMC immunity specification: EN61326-1: 1997 Industrial locations

© 2008 Eurotherm Limited

LIST OF CONTENTS (Cont.)

LIST OF CONTENTS (Cont.)

LIST OF CONTENTS (Cont.)

LIST OF CONTENTS (Cont.)

LIST OF CONTENTS (Cont.)

LIST OF CONTENTS (Cont.)

LIST OF CONTENTS (Cont.)

This page is deliberately left blank

SYMBOLS USED ON THE EQUIPMENT LABELLING

Refer to the manual

Protective-conductor USB connector

This instrument Serial communications

Precautions against static elec- For environmental reasons, this

1.2 MECHANICAL INSTALLATION

1.2 MECHANICAL INSTALLATION (Cont.)

Panel thickness: Max = 22 mm; Min = 2 mm

Flash card Panel cutout

PANEL MOUNTING DETAILS

Installed panel angle: Vertical panels only

Note: where multiple units are mounted in close proximity

Figure 1.2a Small-frame unit mechanical installation

1.2 MECHANICAL INSTALLATION (Cont.)

F10 F11 F12 F13 F14 F15 F16 F17 F18

Panel thickness: Max = 22 mm; Min = 2 mm

PANEL MOUNTING DETAILS

Installed panel angle: Vertical panels only

Note: where multiple units are mounted in close proximity

Figure 1.2b Large-frame unit mechanical installation

1.3 ELECTRICAL INSTALLATION

1.3.1 Supply voltage wiring

Figure 1.3.1 a Supply voltage wiring

Process supervisor 1 Process supervisor 2 Process supervisor

24V 0V 24V 0V 24V 0V

Daisy-chain unit wiring

Figure 1.3.1b Supply voltage connection examples

1.3.2 EIA485 connections

Segment ON (left) OFF (right)

Figure 1.3.2 Table 1.3.2b Communications DIP switch settings

1.3.3 ETHERNET (100/10 Base-T) Connector

Figure 1.3.3 Ethernet (ELIN) connector pinout.

1.3.4 USB Connector

Figure 1.3.4 USB connector pinout

1.3.5 Wiring the Visual Supervisor to I/O units

EIA485 Master port

Using serial comms

1.3.5 WIRING THE VISUAL SUPERVISOR TO I/O UNITS (Cont.)

Network Switch (RSTP) Network Switch (RSTP)

Ethernet port T2550R

1.3.6 Profibus wiring

CHAPTER 2: GETTING STARTED

* No application loaded *