5ha029280 - 12 - 00 2

PAC Systems
Eycon 10/20
Visual Supervisor
Handbook
HA029280 Issue 12
December 2014
© 2014
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 prior written permission of the
manufacturer.
The manufacturer 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. The manufacturer will not accept responsibility for
any losses arising from errors in this document.
40
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
12 PRINTER/READER OPTION............................................................................................................ 12 - 1
A SPECIFICATION.................................................................................................................................. A - 1
B OPTIONS UPDATE............................................................................................................................. B - 1
C REFERENCE.......................................................................................................................................... C - 1
D LEGACY PROGRAMMER.................................................................................................................. D - 1
E PROGRAM APPLICATION EDITOR................................................................................................ E - 1
INDEX..................................................................................................................................................... Index - 1
EFFECTIVITY
This manual refers to instruments fitted with software version number V4.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
Programmer Wizard User Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HA029822
LIN Programmer Editor User Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HA029850
COMPATIBILITY
For LOGDEV blocks prior to version 3.0
The Visual Supervisor uses a block called 'LOGDEV' in its LIN database to configure
recorded values into .uhh files suitable for use with Review software. If LINtools is
upgraded, and if the existing LOGDEV block (prior to version 3.0) is then deleted and a
new LOGDEV block (version 3.0 or higher) is created, then Review software will not be
able to associate the data from the new block with that created with the old block.
HA029280 Contents
Issue 12 Dec 14 Page i
LIST OF CONTENTS
Section Page
SAFETY NOTES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
SYMBOLS USED ON THE EQUIPMENT LABELLING. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
PREVENTIVE MAINTENANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
COMPACT FLASH (CF) CARD PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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
Contents HA029280
Page ii Issue 12 Dec 14
LIST OF CONTENTS (Cont.)
Section Page
2.7 LOGGING PANE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
2.8 ACCESS PANE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
2.8.1 Gaining access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
STANDARD ACCESS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
STANDARD ACCESS (Cont.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
STANDARD ACCESS (Cont.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
USER ID ACCESS METHOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Chapter 3: OPERATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.1 RUNNING A PROGRAM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.1.1 Running a program now. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.1.2 Scheduling a program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
PROGRAM SELECTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
SPECIFYING THE PROGRAM START DATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
SPECIFYING THE PROGRAM START TIME. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
3.1.3 Skip. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
SEGMENT TRANSITION CONSEQUENCES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
From dwell, set or servo (SP or PV) to any other type. . . . . . . . . . . . . . . . . . . . . . 3-5
From ramp to set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
From ramp to dwell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
From ramp to end (Starting values). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
From ramp to complete (infinite dwell) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
To ramp from any other type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
3.1.4 Advance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
3.1.5 Edit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
EDIT OPTION KEYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 Program profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
3.3.2 Faceplates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
3.3.3 Segment status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
SEGMENT NAME. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
SEG TIME REMAINING. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
PROG TIME REMAINING. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
3.3.4 Push-button keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
ALARMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
BATCH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
PLOT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
REMAINING KEYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
3.3.5 PREVIEW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
3.4 LOGGING DATA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
3.4.1 Types of files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
ASCII. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
UHH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
HA029280 Contents
Issue 12 Dec 14 Page iii
Section Page
3.4.2 Name types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
TEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
HOURLY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
DAILY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
SEQUENCE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
3.4.3 Manage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
ARCHIVE EXPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
DATA INTEGRITY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
3.4.4 FTP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
3.5 ALARMS / MESSAGE RESPONSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
3.5.1 Alarm history page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
TWO LINE DISPLAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
FILTER KEYS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
ACK KEY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
ARCHIVE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
3.5.2 Alarm/Message Acknowledgement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
ALARMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
MESSAGES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
3.5.3. Adding notes to alarm history. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
3.5.4 Alarm history archive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
3.5.5 Alarm summary page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
3.5.6 Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
TWO LINE DISPLAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
3.6 AREA AND GROUP DISPLAYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
3.6.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
TREND DISPLAYS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
ALARM INDICATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
3.6.2 Function block faceplates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
RAMP FACEPLATES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
PID FACEPLATES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
3.6.3 Display modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
FACEPLATE DISPLAY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
NUMERIC DISPLAY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
VERTICAL BARGRAPH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
HORIZONTAL BARGRAPH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
VERTICAL TREND WITH FACEPLATE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
VERTICAL TREND WITH FACEPLATE(Cont.). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
VERTICAL TREND - FULL WIDTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
HORIZONTAL TREND WITH FACEPLATE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
HORIZONTAL TREND WITH FACEPLATE(Cont.). . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
HORIZONTAL TREND - FULL WIDTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
3.7 DOWNLOADING RECIPES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
3.7.1 Download procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
RECIPE SET SELECTION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
LOADING THE RECIPE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
SELECTING A RECIPE LINE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30
SELECTING A RECIPE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30
Contents HA029280
Page iv Issue 12 Dec 14
Section Page
3.7.2 Monitoring the recipe. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30
RECIPE STATUS PAGE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30
RECIPE MONITOR PAGE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31
3.8 BATCHES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
3.8.1 Batch loading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
3.8.2 Recipe selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
3.8.3 Batch customising. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
3.8.4 Batch initiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33
3.8.5 Batch monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33
3.8.6 Batch Hold. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33
3.8.7 Batch Abort. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33
3.8.8 Batch Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
Chapter 4: MANAGEMENT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.1. EDITING A PROGRAM (Spreadsheet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
JOG BUTTONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.1.1 INTRODUCTION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
CREATING A PROGRAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
PROGRAM EDIT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.1.2 Program Edit Page Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
4.1.3 SEGMENT NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
4.1.4 Channel name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
4.1.5 Segment type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
HOLDBACK AND ALARMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
4.1.6 User values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
4.1.7 Event displays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
COMPRESSED EVENTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
UNCOMPRESSED EVENTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
4.1.8 Wait and Exit conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
4.1.9 Option keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
LOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
SAVE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
SAVE AS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
NEW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
PROPERTIES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
LAYOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
VIEWS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
REVISION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
4.2 LOGGING GROUPS OF DATA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
4.2.1 Log initiation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
LOG CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
LOG CONFIGURATION (Cont.). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
4.2.2 FTP Transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
MULTIPLE COPY MODE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
SINGLE COPY MODE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
CONFIGURATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
HA029280 Contents
Issue 12 Dec 14 Page v
Section Page
4.3 MANAGING AN APPLICATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
4.3.1 Application summary page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
4.3.2 Application manager page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
4.3.3 Stopping an application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
4.3.4 Saving application data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
4.3.5 Unloading an application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
4.3.6 Loading or loading and running an application. . . . . . . . . . . . . . . . . . . . . . . . . 4-20
APPLICATION SELECTION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
APPLICATION LOADING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
4.3.7 Deleting an application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
4.3.8 Function Block Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
ALPHA-NUMERIC BLOCK DISPLAY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
FUNCTION BLOCK DETAILS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
4.4 CONTROLLING ACCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
4.4.1 First-time access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
4.4.2 Editing the passwords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
4.4.3 User ID system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
CHANGING TO THE USER ID SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
USER ID MANAGEMENT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
4.5 SETTING UP AND RE-SETTING THE INSTRUMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
4.5.1 Editing communications parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
SOFTWARE PARAMETER EDITING. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
PROTOCOLS AVAILABLE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
TALK-THRU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
ETHERNET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
MODBUS/TCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35
TIME SYNC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
4.5.2 Setting the start-up strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
HOT/COLD START CRITERIA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
START-UP STRATEGY PAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
CHANGING START-UP VALUES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38
4.5.3 Resetting the clock. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39
CLOCK SETUP PAGE ACCESS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39
CHANGING DATE AND TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39
TIME CHANGING. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
4.5.4 Changing language and date/time formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
LANGUAGE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-41
DATE FORMAT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-41
TIME FORMAT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-41
4.5.5 Time zone configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-42
CONFIGURATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-42
TIME SUFFIX DISPLAYS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-43
4.5.6 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
Contents HA029280
Page vi Issue 12 Dec 14
Section Page
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
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
4.10 BATCH MAINTENANCE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-56
4.11 COMPATIBILITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-57
4.12 EDITING A PROGRAM (APPLICATION EDITOR VERSION). . . . . . . . . . . . . . . . . . . . . 4-58
4.12.1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-58
4.12.2 Default edit page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-58
4.12.3 New program creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-59
FIXED FUNCTION KEYS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-61
VIEWS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-61
4.12.4 Program editing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-63
4.12.5 Small frame exceptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-63
4.12.6 Other notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-63
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
HA029280 Contents
Issue 12 Dec 14 Page vii
Section Page
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-29
5.2.6 Alarm/event customisation using the dictionary. . . . . . . . . . . . . . . . . . . . . . . . 5-32
5.3 THE ERROR TEXT DICTIONARY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33
5.3.1 Editing error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
5.3.2 Creating new language error text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
PROCEDURE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
5.4 THE EVENT TEXT DICTIONARY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35
5.4.1 Editing Event Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39
5.4.2 Creating new language event text. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39
PROCEDURE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39
5.4.3 Event priorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39
5.5 THE USER TEXT DICTIONARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
5.6 THE PROGRAMMER TEXT DICTIONARY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
5.7 PANEL NAVIGATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41
5.7.1 The Panel Navigation file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41
THE VERSIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41
AUDITOR OPTION VERSIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45
5.7.2 Editing the _default.pnl file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-48
5.7.3 Line types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-49
PANEL AGENT DECLARATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-49
PANEL DRIVER DECLARATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-50
HOME PAGE DECLARATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51
ROOT PAGE DECLARATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51
INITIAL PAGE DECLARATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51
5.7.4 Agent types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52
5.8 DATABASE NAMES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-54
5.8.1 Function block names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-54
5.8.2 Alarm names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-54
5.8.3 Enumerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-55
TAGS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-55
5.9 FORM FILES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-56
5.9.1 Report forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-56
UYF FILE ENTRIES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-57
UYF FILE ENTRIES (Cont.). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-58
UYF FILE ENTRIES (Cont.). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-59
5.9.2 Alarm forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-60
EXAMPLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-60
Contents HA029280
Page viii Issue 12 Dec 14
Section Page
5.10 RECIPE FILES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-61
5.10.1 Basic Recipe File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-61
FILE HEADER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-61
TITLE LINE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-62
VARIABLE LINES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-62
BASIC FILE EXAMPLE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-62
5.10.2 More complex files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-63
MULTI-LINE FILES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-63
FILES WITH OPTIONAL CAPTURE VARIABLES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-63
FILES WITH OPTIONAL MONITOR VARIABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-64
5.11 WRITABLE DICTIONARY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-64
5.12 THE RECIPE DICTIONARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-65
5.13 THE BATCH DICTIONARY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-66
5.13.1 Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-66
5.14 BATCH FILES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-67
5.14.1 File Header. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-67
5.14.2 Batch Phases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-68
5.15 BAR CODE READER FILES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-69
5.15.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-69
PATTERN DELIMITER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-69
5.15.2 Literal text. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-70
EMPTY STRINGS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-70
5.15.3 Dictionary text. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-71
5.15.4 LIN database variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-71
SYSTEM VARIABLES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-72
ENUMERATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-72
5.15.5 Number of characters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-73
5.15.6 Number of decimal places . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-73
5.15.7 Formatting attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-73
5.15.8 User actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-74
5.16 DATABASE CHANGE AUDIT TRAILING. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-75
5.16.1 Header Line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-75
5.16.2 Item Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-75
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 PAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
EXPIRES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
SCREEN KEYS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
HA029280 Contents
Issue 12 Dec 14 Page ix
Section Page
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
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.9 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 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
Contents HA029280
Page x Issue 12 Dec 14
Section Page
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
Chapter 11: FLUSH MOUNTING OPTION INSTALLATION. . . . . . . . . . . . . . . . . . . 11-1
11.1 UNPACKING. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
11.2 MECHANICAL INSTALLATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
11.2.1 Overlay recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5
11.3 SPECIFICATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5
Chapter 12: PRINTER/READER OPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
12.1 INTRODUCTION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
12.2 PRINTER SET-UP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
12.2.1 Assigning printers to ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
12.2.2 Printer parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3
PARAMETERS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3
12.2.3 Push buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
PLOT P1/PLOT P2 PUSH BUTTONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
12.2.4 Printout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
REPORTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
TRENDS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
ALARM AND EVENT OBJECTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
REPRINT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
12.2.5 Application notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6
12.3 READER INPUT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6
Appendix A: TECHNICAL SPECIFICATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Function Blocks supported. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
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
HA029280 Contents
Issue 12 Dec 14 Page xi
Section Page
Appendix D: LEGACY PROGRAMMER DETAILS. . . . . . . . . . . . . . . . . . . . . . . . . . D-1
D.1 RUNNING A PROGRAM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
D1.1 RUNNING A PROGRAM NOW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
D1.2 RUNNING FROM A POINT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3
D1.3 SCHEDULING A PROGRAM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4
D1.3.1 Specifying the Program start date. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-5
D1.3.2 Specifying the Program start time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-5
D1.3.3 Changing the number of iterations (runs). . . . . . . . . . . . . . . . . . . . . . . . . . . . D-6
D1.4 SEGMENT SKIP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-7
D1.4.1 Segment transition consequences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-7
FROM DWELL, SET OR SERVO TO ANY OTHER TYPE . . . . . . . . . . . . . . . . . . . . . . . D-7
FROM RAMP TO SET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-7
FROM RAMP TO DWELL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-7
FROM RAMP TO END (STARTING VALUES). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-7
FROM RAMP TO COMPLETE (INDEFINITE DWELL). . . . . . . . . . . . . . . . . . . . . . . . . D-7
TO RAMP FROM ANY OTHER TYPE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-7
D2 HOLDING A PROGRAM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-8
D3 ABORTING A PROGRAM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-8
D4 MONITORING A PROGRAM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-9
D4.1 THE MONITOR FACILITY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-9
D4.2 THE PREPLOT FACILITY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-10
D4.2.1 Standard display mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-10
D4.2.2 Review mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-10
D5 EDITING A PROGRAM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-11
D5.1 INTRODUCTION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-11
D5.1.1 Creating a program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-11
D5.1.2 Editing a program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-11
D5.2 PROGRAM EDITOR PAGE ACCESS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-12
D5.3 CHANGING A SETPOINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-13
D5.3.1 Changing Ramp Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-13
STEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-13
DWELL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-13
RAMP AT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-13
RAMP TO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-13
SERVO TO SETPOINT (SP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-13
SERVO TO PROCSS VARIABLE (PV) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-13
D5.3.2 Teminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-13
D5.3.4 Changing setpoint value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-15
D5.4 CHANGING A SEGMENT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-16
D5.4.1 Changing segment identifier. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-16
D5.4.2 Changing segment duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-17
D5.5 INSERTING/DELETING A SEGMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-17
D5.5.1 Inserting a Null segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-17
D5.5.2 Deleting a segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-18
Contents HA029280
Page xii Issue 12 Dec 14
Section Page
D5.6 CHANGING HOLD BACK PROPERTIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-18
D5.6.1 Choosing the setpoint. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-19
D5.6.2 Changing Holdback mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-19
D5.6.3 Changing Holdback value. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-19
D5.7 CHANGING PROGRAM PROPERTIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-20
D5.7.1 Changing program names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-20
D5.7.2 Changing rate units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-21
D5.7.3 Choosing End-of-Run action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-21
D5.7.4 Changing default iterations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-22
D5.8 CHANGING SETPOINT NAMES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-22
D5.9 SEGMENT TIMING DISPLAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-23
D6 THE PANEL NAVIGATION FILE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-24
D6.1 THE VERSIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-24
D6.2 AUDITOR OPTION VERSIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-27
APPENDIX E: PROGRAM APPLICATION EDITOR . . . . . . . . . . . . . . . . . . . . . . . . . E-1
E1 INTRODUCTION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
E2 BLOCK CREATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
E3 SEGMENT CLASS CREATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-3
CLASS SETTINGS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-5
E4 APPLICATION TEST. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-7
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
HA029280 Contents
Issue 12 Dec 14 Page xiii
Visual Supervisor Handbook
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 mul-
tiple 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 disconnecting 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 equip-
ment might be impaired.
4. The battery within the unit must not be short circuited. When exhausted, the battery must be disposed
of in accordance 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 pro-
tective 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 12 Dec 14 Page 1-1
PREVENTIVE MAINTENANCE
The unit may be cleaned using a lint-free cloth, moistened if necessary with a weak detergent solution. Ag-
gressive 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 bat-
tery should be replaced as soon as possible after the appearance of this alarm.
COMPACT FLASH (CF) CARD PRECAUTIONS

The Compact Flash card supplied with this unit contains data (such as the instrument’s MAC address and op-
tions settings), which, if lost, cause the instrument to malfunction. These items cannot be replaced by the
user, so if they are lost, they have to be replaced by the Visual Supervisor manufacturer, and the cost of this
procedure may include the full charge for the options.
The following ‘rules’ should therefore be observed:

1. The card must not be reformatted.
2. Folders and / or System files must not be deleted.
3. The card must not be removed from the reader without the correct removal procedure having first been
followed. This procedure varies according to the version of Windows being used.
4. A backup copy of all the folders and files on the card should be made, so that they may be restored in the
event of accidental removal. (This does not allow recovery from card reformatting or the loss of options
settings etc.)
For software updates, follow the published update procedure. This copies the relevant files to the Flash card,
overwriting files where necessary. Files should not first be deleted.
Notes:
1. It may be useful to keep a backup copy of details of any option changes. This should include the
MAC address, the Change Code and the Validation Code.
2. For units with software prior to V3.0: When moving a Flash card from one instrument to another
everything is transferred, including any options. The Visual Supervisor stores its options within its
internal memory and reads option information from the Flash card only if the options within its in-
ternal memory have become corrupt. For this reason, it ignores the options on the new card. This
problem can be resolved in two ways: firstly, by removing the battery for approximately two hours
(to force a fault) or secondly, by re-entering the options selection and the validation code.
Chapter 1 HA029280
Page 1-2 Issue 12 Dec 14
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 documenta-
tion.
Once the unit has been installed, store any internal packing with the external packing in case of future des-
patch.
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 sufficiently 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)
Right-hand side view
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
View on underside
Flash card Panel cutout

USB 1
138 mm x 138 mm
– – + +
(both -0 + 1 mm)
Ethernet Serial comms Power
Profibus Option
USB2 USB3 (Chapter 10)
USB option
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
USB1
––++
USB2 USB3 Profibus option
USB option
281.4 mm
298.4 mm Panel cutout = 282 mm x 282 mm
(both -0 + 1.3mm
314.4 mm


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 chap-
ter.
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. If any USB peripheral is to be left permanently inserted, it is recommended that the supply voltage
cable be twisted 1½ times through a ‘snap-on’ ferrite.
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 sections of the switches allow 120Ω terminating resistors to be switched in and out of circuit. The DIP
switches are accessible by carefully removing the access cover at the rear of the unit (taking care not to dam-
age any associated connector or loom).
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 poten-
tial 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
underside 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 Connectors
Caution
Both the user and the USB device must be at the same electrical potential as the instrument housing
before the USB device is connected.
USB1 is supplied as standard; USB2 and USB3 can be supplied as an option. The USB connectors are used to
connect a maximum of two printers, two readers (or any other device which produces an ASCII string output)
and one memory stick (but see notes 3 and 4 below). The maximum current which may be drawn is 500mA
per USB connector. The connectors are located as shown in figure 1.2a and figure 1.2b, above; pinout is shown
in figure 1.3.4, below
Notes
1. USB peripherals must be fitted with high quality screened cable.
2. Where the unit is to be used in an electrically ‘noisy’ environment (i.e. with fast transient bursts
exceeding ±500V) it is recommended that the user bring USB sockets to front of panel, via short
extension leads. This is because the USB may ‘lock up’ or reset in noisy environments and the only
means of recovery is to remove the device, then re-insert it. EMC-related failure during a write
might cause corruption of the data held on a USB memory stick. For this reason the data on a
memory stick should be backed-up before insertion, and checked after removal.
3. Printers and readers may also be communicated with using EIA485 connectors, but the maximum of
two printers and two readers per instrument is fixed, no matter which connector type is used.
4. Printers (but not readers) may also be communicated with using Ethernet connectors, but the maxi-
mum of two printers per instrument is fixed, no matter which connector type is used.
5. EMC compliance is not guaranteed if two high-power USB peripherals are connected to a Visual
supervisor with the Profibus option fitted.
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
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 temporary 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 recom-
mended.
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 for Profibus network topology recommendations.
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
installation. 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 leg-
ends 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 draw-
ings 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
keys
option key F4 F5 F6
Down
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
up
Menu key 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 F19 F20 F21 F22 F23 F24 F25 F26 F27
Down
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 run-
ning in a PC. This software, available from the Visual 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 download-
able 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.3a, 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.3a System Summary page
The System Summary page confirms the order options that were specified for this instrument.
Operation of the down arrow key calls a software options display, showing the software options fitted.
Software Options
Modbus Master: YES
MiniPCI Card: <NONE>
Software Opt1: L2:Batch Manager
Auditor: NO
Figure 2.1.3b Software options display
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 described in section 2.8 of this manual. This allows the display to be unlocked using an appro-
priate 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,
dialogue 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 background.
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 through-
out 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
manufacturer, 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, SYSTEM,
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 edit-
ing setpoint programs. This key is also the gateway to the operational (Operator) func-
tions 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 moni-
tored.
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
information 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, dis-
played after a timeout.
Of the two or three further levels in the hierarchy, all are available to Engineers, but only some are available
to Operators 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

Program name
Status RunninG Sample

Time to 14:18:23 Segment 1
completion Orange dot appears, flashing, if
10:22:04 a program is scheduled to run
Name of segment
currently running
Instrument
time
Figure 2.4 Typical Program pane display
Located at the top left of the screen, this area (which varies in appearance according to instrument type, and
options fitted) has the following 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.
3. If a flashing orange dot appears in the top right corner, it indicates that another program has been sched-
uled to run.
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 Segment 1,
5. another program has been scheduled to run
A loaded program can be in one of the following states, reported on the Program pane:
Unloaded, Inhibit, Running, Hold, Idle, Complete.
With the program in ‘Running’ 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 to 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’.
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 (e.g. comms failure), the whole Program pane flashes red.
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
PROGRAMS SCHEDULE EDIT
PREVIEW MONITOR START
HOLD ABORT RESET
SKIP ADVANCE REDO
Figure 2.5a The Programmer menu, display locked
With the display unlocked and a database loaded, the full menu appears:
Programmer
HOLD ABORT RESET
SKIP ADVANCE REDO
Figure 2.5b The Programmer menu, display unlocked
Disabled (greyed-out) buttons are not relevant to the current program status.
PROGRAMS Allows a program to be selected from those available in the instrument’s flash memory.
SCHEDULE Allows a time and date, to be entered as the start time of the program.
EDIT Allows Engineers to edit, and Operators to view, the setpoints of the current program,
displayed as a table.
PREVIEW PREVIEW is a graphical version of EDIT (below) and displays the profile of the loaded
program, so that it may be checked prior to being run. Target values for the variables can
be displayed for any time/date, by moving a vertical cursor along a horizontal time-base.
MONITOR Displays text and graphical details of the program currently loaded.
START/RESTART Runs a program from the start, or re-starts a program, after a Hold, from the point at
which it paused.
HOLD Stops a program running, and holds it paused at that point.
ABORT Switches a program from ‘Hold’ state to ‘Idle’.
RESET Resets a program from ‘Complete’ to‘ Idle’.
SKIP Terminates the current segment and proceeds immeditely to the next segment which
starts at the value obtaining when skipped (see figure below).
ADVANCE Ramps to the segment’s target value and proceeds immeditely to the next segment which
starts at that target value (see figure below).
REDO Repeats the current dwell or step segment. Disabled for other segment types
Segment A Segment B Segment A Segment B

Target Target
Skip Advance
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 opera-
tional threshold).
In general, there are four possible types of alarm annunciation as summarised in table 2.6.1 below. The ques-
tion mark symbol on a flashing orange/black background means that there is a new message to be investigat-
ed as described in ‘ACTIVE MESSAGE DISPLAY’ below.
Alarms can be set to be latching or non-latching (auto acknowledging). Latching alarms are annunciated until
acknowledged; 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 nor-
mal, without being acknowledged.
Steady red means there is at least one abnormal condition that requires attention, all of which have been
acknowledged, 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 displayed 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. Fur-
ther 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
condition 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
acknowledged. 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 ver-
sion.
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
appropriate, 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. Thereafter 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 old-
est 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 described 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)
(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 MANAGE
GROUPS FTP
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
(irreversibly) to the User ID version as described in section 4.4 of this manual. For units fitted with the ‘Audi-
tor’ option, see also section 6.
STANDARD ACCESS
For the Visual Supervisor there are nominally three types of users: Operators, Commissioning Engineers, and
Engineers.
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 Commis-
sioning 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 (high-
est). 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
facilities. 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
STANDARD ACCESS (Cont.) that shown here.
1. With the instrument powered up, press the menu key below the 2
screen. Press aCCESS key
In the Main pane the restricted version of the pop-up menu (figure
2.3) appears.
PROGRAMMER LOGGING HOME
2 Press ACCESS
1
The Security Access page appears. Press menu key
2/2
RESET E Y C O N -10 B A D B A T
13:12:30 Security Access 04/04/06
3 Press the field showing LOCKED on yellow, opposite ‘New Level’. Enter required level and password,
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 RESET
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,
5. Press the Return key (the green arrow ) then CHANGE
LOCKED
OPERATOR
COMMISSION
ENGINEER
New Level: LOCKED
Password: ********
***
CHANGE
HA029280 Chapter 2
2.8.1 GAINING ACCESS (Cont.)
STANDARD ACCESS (Cont.) RESET

2/2
The pick-list disappears, revealing the full Security Access page Enter required level and password,
again, showing the selected level (OPERATOR, COMMISSION or then CHANGE
ENGINEER) in the New Level field, on yellow.
New Level: OPERATOR
6 Press the Password field (shown as asterisks on pale yellow)
Password: ********
CHANGE
2/2
13:13:48 Security Access 040406
A ‘qwerty’ keyboard display appears, with a cursor flashing
under the first character-space in the black confirmation bar
at top left. q w e r t y u i o p
a s d f g h j k l ;
7 If the password contains characters not visible on this dis-
play, press the ‘up-arrow’ at bottom left to view others avail- z x c v b n m ,
able. A numeric/symbol keyboard appears. A further opera-
tion of the Up Arrow calls a keyboard of accented lower-case
letters. A final operation returns the original keyboard to the
Caps lock key
display.
In entering the password as described in step 8 below, the use up-arrow key to select
characters can be selected from all three keyboards as re- alternative keyboards
quired RESET
2/2
password
q w e r t y u i o p
8 Enter the first character of the password. It appears in the
black confirmation bar at top left, and the cursor moves a s d f g h j k l ;
under the next space. Enter the next character, and so on.
Erroneous characters can be deleted by positioning the cur- z x c v b n m ,
sor under the relevant character and pressing the ‘C’ key.
Alternatively, to return to the Security Access page, press the
‘red cross’ key.
2/2
9 When the confirmation bar shows the correct password, 13:14:20 Security Access 04/04/06
press the Return key. Enter required level and password,

then CHANGE
The Security Access page reappears, unchanged from step 6. Current Level: LOCKED
New Level: OPERATOR
Password: ********
CHANGE
10. Press CHANGE
2/2
The display blanks momentarily, and returns showing the selected 13:15:19 Security Access 04/04/06
level (OPERATOR, ENGINEER or COMMISSION) in the Current Enter required level and password,
Level field as well as the new level field. then CHANGE
If not, an incorrect password must have been entered. Check that Current Level: OPERATOR
the password is correct for the level selected in step 4, and then New Level: OPERATOR
repeat from step 3 onward. Password: ********
CHANGE
Chapter 2 HA029280
2.8.1 GAINING ACCESS (Cont.)
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 result-
ing keyboard to enter the relevant character strings. Once this has been completed, the LOG ON key is oper-
ated.
If the instrument fails to respond with the relevant access level, either the Identity or the Password has been
incorrectly entered.
Note: The character strings are case sensitive e.g. Identity ‘Fred’ is different from identity ‘FRED’.
HA029280 Chapter 2
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
3.8 Batch operations
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 facility if required.
3.1 RUNNING A PROGRAM

Programs can be run as soon as they are loaded (section 3.1.1), or they can be scheduled to start at a specified
time and date (section 3.1.2).
3.1.1 Running a program now
aCCESS SYStEM aLaRMS

1. Press the Menu key to call the Pop-up menu.
PRoGRaMMER LoGGinG uSER SCREEnS
The Program pane displays RESET if there is no program 2

loaded at the moment, or IDLE if a program has already 1 Press PRoGRaMMER
been selected. key
Press menu key
2. Select PROGRAMMER. Programmer

The Programmer window appears.
3. Select ‘PROGRAMS’. HOLD ABORT RESET
SKIP ADVANCE REDO
HA029280 Chapter 3
3.1.1 RUNNING A PROGRAM NOW (Cont.)

The Program Load 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.
08:52:33 Program Load 09/04/08
* Note: Up to eight setpoint programs can be supported simultane-
ously. Where more than one such program is running, the ‘Program Program: ????????
Load’ page has an additional field ‘Unit’ which allows the user to
specify which programmer is to run this program.
All display pages refer to the program associated with the currently
selected ‘Unit’.
LOAD
For any particular programmer display page, the identical page for
other valid units can be scrolled-through, using the right and left ar-
row keys.
4. Press the yellowed field of question marks. 09:05:57 Program Load 09/04/08
A pick-list of the available programs appears in the left-hand side SAMPLE

Name: ????????
Program:
File
of the screen. The small-frame display is shown to the right of DSAMPLE
this description. The large-frame product is similar but includes STMAXALL
the File Name and the Program Name, separated by a hyphen, as ENMAXSEG
ENMAXSP
shown below. SAMPLE
???????? LOAD
DSAMPLE-Steel spec 2
STMAXALL-Steel max 1
ENMAXSEG-Maximum mix
ENMAXSP - Maxim
09:20:21 �� 09/04/08
5 Press the name of the required program. The background of the
selected program’s name changes to yellow. Program: SAMPLE
6 Press the Return key (the green arrow). The pick-list disappears
and the Load/Save Program page now shows the name of the
selected program on a yellow background. ��
7. Press the LOAD key ��

��
09:25:20 �� 09/04/08
The full Programmer menu appears. The Program pane reads ��
IDLE, showing the program is loaded but idling, not running. ��
��

8. Press START
��
��
The Program pane changes to green, with status RUNNING. The ��
expected time of completion and the number of the segment
currently executing are also displayed. ��
��
If a program is configured to operate as part of a batch, then the 09:39:45 �� 09/04/08
batch pop-up appears, requiring confirmation of batch details ��

before the program and batch are started.
��
Batch Start ��

File Name: BATCH
��
Batch Id: 50462977 ��
��
START
Chapter 3 HA029820
3.1.2 Scheduling a program

This allows the setting of a date and time at which a program is to aCCESS SYStEM aLaRMS
start automatically. Once configured, a flashing orange dot appears in
the top right-hand corner of the program pane as shown in figure
2.4.
2
1 Press PRoGRaMMER
If another program is running at the scheduled start time, the key
Press menu key
program start is delayed. The late start is recorded in the Alarm
Programmer
History.

PROGRAM SELECTION
1. Press the Menu key. HOLD ABORT RESET
2. Select ‘PROGRAMMER’ from the pop-up menu that appears SKIP ADVANCE REDO
3 Select SCHEDULE.
13:38:05 Program Schedule 09/04/08

The Schedule Program page appears, with the instantaneous date
and time. File Name: ????????
Start Date: 09/04/08
4 Press the File Name (????????) field. Start Time: 13:38:03
ACCEPT
A pick-list of the available programs appears in the left-hand 13:38:40 Program Schedule 09/04/08
side of the screen. The small-frame display is shown to the right ????????
of this description. The large-frame product is similar but also File Name: ????????
includes the File Name and the Program Name, separated by a DSAMPLE Start Date: 09/04/08
STMAXALL Start Time: 13:38:03
hyphen, as shown below. ENMAXSEG
???????? ENMAXSP
SAMPLE
ACCEPT
DSAMPLE-Steel spec 2
STMAXALL-Steel max 1
ENMAXSEG-Maximum mix
ENMAXSP - Maxim

SAMPLE
5. Select the required program. File Name: ????????
DSAMPLE Start Date: 09/04/08
STMAXALL Start Time: 13:38:03
ENMAXSEG
The background of the program name changes to yellow. ENMAXSP
SAMPLE
ACCEPT
6. Press the Return key (the green arrow)
The pick-list disappears, and the File Name field shows the name
of the selected program. 13:38:48 Program Schedule 09/04/08
File Name: SAMPLE

The program is now ready for scheduling. Start Date: 09/04/08
Start Time: 13:38:03
Note: If the program is to run immediately after the currently-
running program ends, the Start Date and Start Time can be left at
ACCEPT
their current values, and ‘ACCEPT’ pressed.
HA029280 Chapter 3
3.1.2 SCHEDULING A PROGRAM (Cont.) 13:39:05 Program Schedule 09/04/08

09/04/08
SAMPLE
SPECIFYING THE PROGRAM START DATE 7 8File Name:
9
4 5
Start 6
Time: 13:38:03
7. Press the ‘Start Date:’ field. 1 2 3
The left side of the screen shows a numeric keyboard, with a . 0
ACCEPT
cursor flashing under the first number in the black confirmation
bar at the top.
10/04/08
8. Key in the required date, in the format set for your instrument SAMPLE
7 8File Name:
9
(ask your Engineer). Start Date: 09/04/08
4 5
Start 6
Time: 13:38:03
After the first digit has been keyed-in, the cursor moves to the 1 2 3
next character, and so on - there is no need to enter the’/’ char- . 0
ACCEPT
acter.
The field can be cleared to ??/??/?? by pressing the ‘C’ key. The 13:39:20 Program Schedule 09/04/08
red cross key can be used to abort the whole date-entry proc-
ess and return to the Program Schedule page. File Name: SAMPLE
9.When the required date has been entered, the Return key is
used to return to the Program Schedule page, which now shows
the newly specified date. ACCEPT
SPECIFYING THE PROGRAM START TIME 13:39:35 Program Schedule 09/04/08

13:38:03
SAMPLE
10 Press the ‘Start Time:’ field. 7 8File Name:
9
4 5
Start 6
Time: 13:38:03
The left side of the screen shows a numeric keyboard, with a 1 2 3
cursor flashing under the first number in the black confirmation . 0
ACCEPT
bar at the top.
11 Key in the time in the format hh:mm:ss. 13:39:40 Program Schedule 09/04/08
09:00:00
SAMPLE
7 8File Name:
9
After the first digit has been keyed-in, the cursor moves to the Start Date: 09/04/08
next character, and so on - there is no need to enter the colons. 4 5
Start 6
Time: 13:38:03
1 2 3
. 0
ACCEPT
The field can be cleared to ??:??:?? by pressing the ‘C’ key. The
red cross key can be used to abort the whole date-entry proc-
ess and return to the Program Schedule page.
File Name: SAMPLE

12. When the required time has been entered, the Return key is Start Time: 09:00:00
used to return to the Program Schedule page, which now shows
the newly specified start time.
ACCEPT
Chapter 3 HA029820
3.1.3 Skip
Skipping a program segment causes the program to stop running its current segment and start running the
next segment immediately, starting at the current value. Skip is initiated from the Programmer menu.
Programmer

Segment A Segment B
Target
Skip
HOLD ABORT RESET
Press
SKiP key SKIP ADVANCE REDO
Figure 3.1.3 Segment Skip
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 pro-
gram finishes early.
From ramp to set

Not Bumpless. The ramp is terminated early. The resulting bump is larger or smaller than that programmed
depending 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 un-
skipped.
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.1.4 Advance
Similar to ‘Skip’, described above. Advancing to the next program segment causes the program to stop run-
ning its current segment and start running the next segment immediately, but starting at the previous seg-
ment’s target value instead of the instantaneous current value. Advance is initiated from the Programmer
menu.
Programmer

Segment A Segment B
Target
Advance
HOLD ABORT RESET
SKIP ADVANCE REDO
Press
aDVanCE key
Figure 3.1.4 Segment advance
3.1.5 Edit
Edit allows the operator to view the program segments (small-frame default - see figure 3.1.5a) and if so con-
figured, (at Engineer level), to schedule, monitor and preview information. Not all this of information can be
displayed simultaneously on the small frame version. Full details of Programmer Edit are given in section 4.1.
SAMPLE 0/0
Segment name
RUNNING 6:47:44 PUMP DOW
14:07:29 Program Edit 16/04/08
HEAT Segment start
Segment duration 00: 15: 00
INITIALISE PUMP DOWN HEAT 01: 00: 00 Segment duration
00: 05: 00 00: 10: 00 01: 00: 00 01: 15: 00
STEP DWELL RAMPTIME Segment finish
Channel name TEMPERAT 30 30 800
DEGC
STEP STEP DWELL Segment time-display options
PRESSURE
1.00E+03 1.00E-03 1.00E-03
User value M B A R
V A C U U M A 0.00E+00 0.00E+00 0.00E+00

Events MBAR
EVENTS 000 100 001 100 001 100

Further Events, 1-6
'Wait' and 'Exit'
accessed via
vertical scroll bar
Events Details
Segment Name: Heat
Fan: OFF
Heat: Disable
Cool: Enable
Pressure: Enable
oK
Fig 3.1.5a Program edit - Default view
Chapter 3 HA029820
3.1.5 EDIT (Cont.)

The appearance of the page depends on how it has been configured. The default display shows Segment
Duration, but it is possible to configure (see section 4.1) any or all of Segment start, Segment duration and
Segment finish times to appear (where start and finish are relative to the start of the program, not real-time).
Figure 3.1.5a also shows that information related to the various ‘cells’ is displayed when the cells are touched.
At Operator level, these items are only viewable; editing can be carried out only at Engineer level of access.
The display can be configured to include Preview, Monitor and Schedule, although not all these items can
be displayed simultaneously on the small-frame unit. Figure 3.1.5b, below, shows the display configured to
include ‘Preview’. ‘Monitor’ adds the monitor function keys below the graph. Schedule displays the file name
and its start date and time.
SAMPLE 0/0
11:14:20 Program Edit 17/04/08
INITIALISE PUMP DOWN HEAT

00: 05: 00 00: 10: 00 01: 00: 00
STEP DWELL RAMPTIME
TEMPERAT 30 30 800
DEGC
STEP STEP DWELL
PRESSURE
MBAR
1.00E+03 1.00E-03 1.00E-03
Temperat
1050.0
Pressure
0.0
03:43:12 Soak
Figure 3.1.5b Program edit with ‘Preview’
EDIT OPTION KEYS

Operating the Option key produces a number of function keys. The small frame unit cannot display all these
keys at once, so the Option key is used a number of times in order to scroll through them all. At Operator
level, all these are disabled except for NEW and REVISION.
New Not used at Operator level
Revision Shows the number of times the program has been edited since it was first saved (version 1),
together with the time and date of the most recent edit.
HA029280 Chapter 3
3.2 HOLDING AND ABORTING A PROGRAM

The Hold facility allows the user to:
1 pause 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 make on-line changes to a running program (‘Engineer’ access level required).
This chapter is for Operator access level; see section 4.1 for item two in the above list.
SAMPLE 0/0
RUNNING 13:41:14 I NITIALI
15:25:58 Program Load 09/04/08
3.2.1 Holding a program
Programmer

1. With a program running, and the full Programmer menu dis-
played (as at step 8 in 3.1.1. Running a program), press HOLD. PREVIEW MONITOR START
HOLD ABORT RESET

LOAD
SKIP ADVANCE REDO
SAMPLE 0/0
HELD 13:35:04 I NITIALI
15:32:08 Program Load 09/04/08
The Program pane changes to yellow and reports HELD. Programmer
To the left of the page title is the current time. The MONITOR PREVIEW MONITOR RESTART
facility (section 3.3, below) can be used to view the time-into-
HOLD ABORT RESET
program.
LOAD
SKIP ADVANCE REDO
If the attempts to solve the problem are successful, the program is usually continued using RESTART. If the at-
tempts are unsuccessful, the program can be 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) above, press ABORT.
The Program pane 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 0/0
IDLE 00:00:00 ???
15:57:05 Program Load 09/04/08
Programmer
PREVIEW MONITOR RESTART
HOLD ABORT RESET

LOAD
SKIP ADVANCE REDO
Chapter 3 HA029820
3.3 MONITORING A PROGRAM SAMPLE

0/0
16:18:14 Program Load 09/04/08
Programmer
The default Program Monitor page is displayed by operating
the MONITOR key (see section 3.1.1 ‘Running a program now’ if PROGRAMS SCHEDULE EDIT
necessary).
HOLD ABORT RESET

LOAD
The monitor page contains: SKIP ADVANCE REDO
1. a profile of up to five* channels, together with a moving
cursor showing the current position.
SAMPLE 0/0
2. one‘faceplate’ per profiled channel RUNNING 6:47:44 PUMP DOW
16:33:05 Program Load 09/04/08
3. the name of the segment currently running Temperat
421.0
4. times to completion for the segment and for the program 0.0 1500.0
as a whole Pressure
0.0
0.0 1200.0
5. a number of push-button keys.
Segment Name: Heat

Seg Time Remaining: 00:58:12
3.3.1 Program profile Prog Time Remaining: 06:47:44
ALARMS PLOT START RESTART
This provides a graphical representation of the program. By de- Figure 3.3.1a Program monitor display
fault, omly the program channels are drawn on the graph. The
PLOT key (active only for Engineer level access) allows the graph
SAMPLE 0/0
content to be edited to include a maximum of five* items. RUNNING 6:47:44 PUMP DOW
16:33:05 Program Load 10/04/08
Temperat
Note: The first time the Visible Plot Select window is 421.0
Visible plot select 0.0 1500.0
opened all plots are set to ‘None’. All required plots Pressure
Plot: Temperature 0.0
must be entered (even those already appearing) as any 0.0 1200.0
Plot: Pressure
plots left at ‘None’ will be removed from the graph Plot: None
when ‘OK’ is pressed. Plot: None
Segment Name:
Plot:
Heat
None
Prog Time Remaining: 06:47:44
OK CANCEL
Vacuum A
None
Temperature
Pressure
Vacuum A
Thermal Head
ALARMS PLOT
Figure 3.3.1b Plot editing
*16 for large-frame units
HA029280 Chapter 3
3.3.2 Faceplates
Temperat
A faceplate for each configured plot appears to the right of the graph. The faceplates 421.0
show the plot colour and name, along with the current value and high and low range 0.0 1500.0
values. Pressure
0.0
Note: For the small-frame unit, parameter names are truncated to the first eight 0.0 1200.0
characters. Thus, for example, Temperature1’ and ‘Temperature2’ would both ap- Figure 3.3.2
pear as ‘Temperat’, whereas ‘Temp1’ and ‘Temp 2’ would appear in full. Sample faceplates
3.3.3 Segment status
SEGMENT NAME
The name of the segment which is currently running (or held).
SEG TIME REMAINING

The time until this segment is complete. The value decrements if the segment is running, or stops if the pro-
gram is held.
PROG TIME REMAINING

As for Seg Time Remaining, but for the entire program.
3.3.4 Push-button keys

A number of push-buttons appear at the bottom of the screen. With the large-frame unit, all the keys are vis-
ible at once; with the small frame unit up to four keys appear at any one time - hidden keys being accessed by
operating the ‘Option’ key. As well as these fixed-function keys, a number of user-specified keys can appear,
but these are not described here.
The keys are disabled (white text) if they are not appropriate, or if the user does not have a suitable access
level.
ALARMS
Operating this key calls the Alarm History display, described in section 3.5.1, below. This display contains only
those alarms and events relevant to the running program.
BATCH
If present, this key causes batch details to be displayed.
PLOT
Operating ‘PLOT’, allows the user to edit the graphical representation of the program, as described in section
3.3.1, above.
REMAINING KEYS
The remaining keys (START, RESTART, HOLD, ABORT, RESET, SKIP, ADVANCE, REDO) have functions described
in sections 3.1 and 3.2, above.
Chapter 3 HA029820
3.3.5 PREVIEW
This presents a graphical view of the program segments, including a vertical cursor which can be touch-
dragged across the width of the chart. Program parameters are represented by faceplates, to the right of the
graph, which contain the values of the parameters at the cursor position. The segment name and the time-
into-program appear below the graph, for the cursor position.
Operation of the option key causes a ‘PLOT’ key to appear, and if the instrument is configured with more than
one programmer, a ‘UNIT’ key also appears.
PLOT operates in the same way as described in section 3.3.1, above,, and as in that section, requires Engineer
level access before it is enabled.
UNIT calls a dialogue box showing the currently displayed unit name. This can be changed by touching the
name field and selecting the required unit from a pick-list.
SAMPLE 0/0
15:16:32 Program Load 15/04/08
Temperat
1050.0
0.0 1500.0
Pressure
0.0
0.0 1200.0
touch/Drag
Cursor
03:43:12 Soak
PLOT UNIT
Figure 3.3.5 Preview display
HA029280 Chapter 3
3.4 LOGGING DATA

This section describes how incoming data can be logged (ar-
chived) to an archive device.
3.4.1 Types of files
The selection of file type (ASCII or UHH) is made in the Archive
Groups page. Selection can be made only by users with Engi-
BATCH LOGGING
neer level access, and only when logging is ‘OFF’.
ASCII Logging
ASCII files are human-readable, and can be imported into MONITOR MANAGE
standard spreadsheets. Files of this type have ‘.ASC’ extensions.
GROUPS FTP
UHH 10:22:44 Logging groups 16/04/08

UHH format is a non human-readable file format which can be Group Name: loggrp
interpreted only by Review software. UHH files have Sequence Logging: OFF
file names (see below) and the extension .UHH. If ‘Hourly’ or Configuration
‘Daily’ is selected, then new UHH sequence files are created at Archive Int: 00:00:10
hour or day boundaries respectively.
File Type: UHH
Name Type: Text
3.4.2 Name types File Name: QQ00066.UHH
The selection of name type (Text, Hourly, Daily, Sequence) is SAVE MONITOR LOG NOW
made in the Logging Groups window, described in section 4.2,
later in this document. name type can be viewed but not se-
Figure 3.4.1 Logging ‘Manage’ page
lected at Operator level.
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 as-
signs the last six to indicate 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
(midnight) and run for 24 hours. The user supplies the first four letters of the file set and the instrument sup-
plies 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.
Chapter 3 HA029820
3.4.3 Manage
The Logging Manage facility allows the export of files to a re-
movable 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 de- BATCH LOGGING
leted from the internal archive.
Export This pushbutton causes the currently displayed Logging
file to be copied to the USB device, as selected.
Export all This pushbutton causes all files in the internal MONITOR MANAGE
archive to be copied to the USB device. If the
device becomes full during archive, a message ap- GROUPS FTP
pears asking the user to fit a new memory device.
16:50:37 Archive Manage 15/04/08
If a file to be exported has the same name as one already on the File Type: UHH
storage device, the following occurs:
File Name: 00000045.UHH
a. If the file is identical, the file will not be exported, but be File Size: 4 kBytes
marked as ‘skipped’. Media Size: 46848 kBytes
b. If the new file is longer than the one on the storage device, Free Space: 45954 kBytes
but has the same initial data, it will be exported to replace
Free Time: 907-17:16
the existing file.
c. If neither a. nor b. is true, the user is prompted for a deci-
EXPORT EXPORT ALL MONITOR
sion.
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 memo-
ry 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.
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.
3.4.4 FTP
Archive of data to a remote computer can also be carried out. See section 4.2.2
HA029280 Chapter 3
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 annunci-
ate 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
oVERViEW PRoGRaMMER RECiPE
1. Press the Menu key below the screen, then press ALARMS
in the pop-up menu , or BatCH LoGGinG
2. Press the Alarm pane
The Alarms menu appears. The name of the current alarm con- Alarms
dition is displayed in the Alarm pane.
aCK aCK aLL HiStoRY
3. Press HISTORY
SuMMaRY LoG notE
The Alarm History page, depicted in figure 3.5.1a, below, ap- aRCHiVE MESSaGES
pears.
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 following:
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).
Chapter 3 HA029820
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
database 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
HA029280 Chapter 3
3.5.1 ALARM HISTORY DISPLAY (Cont.)
ACK KEY
Pressing this key acknowledges (after confirmation) all current, unacknowledged (i.e. flashing) alarms. Touch-
ing 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 mes-
sage indication stops.
For other messages, touching the alarm pane, or operating the Menu/Alarms/Messages key displays the lat-
est message in a pop-up window. Subsequent operation of the OK button for this window, both clears and
acknowledges the message.
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 the alarm history as follows:.
Alarms
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
To abandon the note before completion, press CANCEL. This will add a note to the Alarm
History List
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. Your note:
OK CANCEL
Chapter 3 HA029820
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.
1. In the Alarms menu, press ARCHIVE Alarms

The Alarm Archive window appears. aCK aCK aLL HiStoRY
The File Name field shows the default of YYMMDDHH. ALH, SuMMaRY LoG notE
which the instrument supplies automatically. To change this
name, press the field to get the keyboard display, and enter a aRCHiVE MESSaGES
new name. The file extension is always .ALH, (not editable).
2. To abandon the name before completion, press CANCEL. Alarm Archive
3. When the correct name has been entered, press OK. Archive to disk the alarm history
If required the ‘Date Format’ field can be edited in a similar fash- File Name: 99072009.ALH
ion. The format options (Date Time, Spreadsheet and Integer) are Date Format: Date Time
described in sections 4.2.1 and 4.5.4.
3.5.5 Alarm summary page OK CANCEL

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
Alarms T2550/7 Comms 04/04 08:13
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 opera-
tion of the keys returns to the single alarm/block display, and so on.
HA029280 Chapter 3
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: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 second line to each event, used to display text that would not fit onto the single line display.
Chapter 3 HA029820
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 con-
tains 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 sec-
tion 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 - Hori-
zontal, Vertical, Full width horizontal, Full width vertical. In each case, it is possible to enter review mode,
allowing historical 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 acknowl-
edged.
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.
HA029280 Chapter 3
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
Chapter 3 HA029820
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 exceed-
ed; 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, with-
out triggering a holdback.
HA029280 Chapter 3
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 appears 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
Down arrow Option key
4. Vertical bargraph key
5. Horizontal bargraph
6. Vertical trend with point faceplates
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.
Chapter 3 HA029820
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 de-
scribed 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 propor-
tional 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
PV1/1
400
800
800
800
400
400
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
HA029280 Chapter 3
HORIZONTAL BARGRAPH
This mode shows the current point values as horizontal bars with faceplates. The length of each bar is propor-
tional 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 con-
figuration, 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 update 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
Chapter 3 HA029820
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, us-
ing 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
Cursor (initially at 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
28.05
values are
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)
Cursor date Cursor time Zoom
factor ‘Back Live’ key
Figure 3.6.3g Trend review controls
HA029280 Chapter 3
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
Chapter 3 HA029820
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.
Buttons have similar effect but spx7m
13:29:07 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
HA029280 Chapter 3
3.7 DOWNLOADING RECIPES

A recipe set consists of sets of instructions (recipes) for controlling between one and eight identical produc-
tion facilities. 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 applied 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 applied 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
Chapter 3 HA029820
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

1 From the main menu, select RECIPE
BATCH LOGGING
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
3. The Recipe Load/Save page appears with the recipe 15:18:42 Load/Save Recipe 04/04/06
set ID and name of any currently loaded recipe file,
or, if none, lines of question marks. Id: ????????
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 available selections can be scrolled through,
LOAD
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.
HA029280 Chapter 3
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 File name: RECIPES
possible to select which is to be the current line to
Line: Line 2 `
which the recipe is to be down loaded. With the
Recipe Status page displayed, (figure 3.7.1d), touch Recipe Name: Run Prog
the yellowed Line field and 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 DOWNLOAD ABORT
through the available items. The file can 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 Id: GasMixes

possible to select which recipe is to be the current
one. With the Recipe Status page selected (figure File name: GASCONC
`
3.7.1e), a touch on the recipe field will call a pick list Recipe Name: Amarillo
from which the required 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.
Chapter 3 HA029820
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 dif-
fer, the value is highlighted in red, providing a useful diagnostic should a recipe down-
load 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.
HA029280 Chapter 3
3.8 BATCHES
3.8.1 Batch loading

1 From the main menu, select BATCH, then select ACCESS SYSTEM ALARMS
BATCHES
BATCH LOGGING HOME
Batch
BATCHES STATUS
NOTE HOLD RESTART
RESET ABORT
SAMPLE 0/0
RUNNING 13:06:34 1
12:35:33 Load Batch 04/04/06
2 Touch the ID or filename area
File Name: ????????
3 Select the required item from the picklist which ap-
pears.
4 Operate the LOAD button. LOAD CREATE
Note: For the ‘Create’ function, see section 3.8.8,

below.
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.
Chapter 3 HA029820
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 one of the following to occur, depending on the way in which the OK CANCEL
batch has been configured:
1 The batch starts immediately
2 A dialogue box appears asking for confirmation of Batch Start. Op- Batch Start Confirm
eration of the OK button starts the batch. Please confirm your password to
start batch.
3 A dialogue box appears asking for the current user’s password. En-
Password: ********
try of 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 acknowledgement 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.
HA029280 Chapter 3
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 appro-
priate.
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.
Chapter 3 HA029820
Chapter 4: MANAGEMENT
This chapter is for those responsible for setting up the instrument, for managing applications, for editing
programs, 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 (spreadsheet) 4.7 File Manager.
4.2 Logging groups of data 4.8 Recipe management
4.3 Managing an application 4.9 OEM features
4.4 Controlling access 4.10 Batch Maintenance
4.5 Setting up and re-setting the instrument 4.11 Compatibility
4.6 Cloning an instrument 4.12 Editing a progam (Application editor)
4.1. EDITING A PROGRAM (Spreadsheet)

The editing process is carried out in one of two ways, according to the Visual Supervisor configuration. Sec-
tion 4.1 describes the ‘spreadsheet’ method where the program segments and their parameters are arranged
in a grid. Section 4.12 describes the ‘Application editor’ method, where programs can be created and edited
using a fixed set of segment types, these types being created using the ‘Programmer Application Editor’ soft-
ware.
JOG BUTTONS
Panel customisation (see section 5.2.5) includes six entries (2280 to 2285) which, if included in the _USER.UYL
file, cause ‘jog’ buttons to appear on the screen. Operation of these buttons moves the user forward through
a segment in steps of 1 minute (entry 2281), 10 minutes (2283) or 1 hour (2285) or backwards 1 minute (entry
2280), 10 minutes (2282) or 1 hour (2284).
For example, if the items below are included in the file, then three buttons will appear with legends ‘>’, ‘<<’
and ‘>>>’. Operation of these buttons cause the segment to jump forward one minute, backward 10 minutes
or forward one hour respectively.
S2281,>
S2282,<<
S2285,>>>
Note: The >, << and >>> characters are suggested as an example - any keyboard characters can be
used. To ensure manageable button sizes (defined automatically), each string should be limited to 12
characters.
HA029280 Chapter 4
4.1.1 INTRODUCTION
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 Program Editor Handbook.
PROGRAM EDIT
Notes:
1 The following tasks (changing setpoint value, segment duration, holdback value, rate, user value
and event value) can be performed while a program is running (but on Hold). Whilst the current
segment is in Hold mode, its values are displayed in green, instead of blue. It is possible to edit the
duration of a non-ramping segment using ‘Jog’ buttons (see below), if enabled. Durations of ramp-
ing segments cannot be edited using Jog buttons.
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. This allows the user to check
that any edits have produced the intended profile.
3. For systems with the Auditor option fitted, an edited program must be saved before it is run.
Chapter 4 HA029280
4.1.2 Program Edit Page Access aCCESS SYStEM aLaRMS
oVERViEW PRoGRaMMER LoGGinG

1. Press the Menu key
1 2
2. Press PROGRAMMER Programmer
Press Programmer key
The Programmer menu appears. Press menu key PROGRAMS SCHEDULE EDIT
3 PREVIEW MONITOR START

3. Press PROGRAMS Press
HOLD ABORT RESET
PRoGRaMS
SKIP ADVANCE REDO

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 09:39:38 Program Load 18/04/08
loaded.) Program: ????????
4. Press the File Name (????????) field.

A pick-list of the available programs appears in the left-hand
side of the screen. The small-frame display is shown to the right LOAD
of this description. The large-frame product is similar but also
includes the File Name and the Program Name, separated by a
hyphen, as shown below. 09:42:27 Program Load 18/04/08
SAMPLE
????????
Name: ????????
Program:
File
DSAMPLE
DSAMPLE-Steel spec 2 STMAXALL
STMAXALL-Steel max 1 ENMAXSEG
ENMAXSP
ENMAXSEG-Maximum mix SAMPLE
ENMAXSP - Maxim
LOAD
5. Press the name of the program to be edited

6. Press the green Return key 10:17:37 Program Load 18/04/08
The Load/Save program page displays the name of the selected Program: SAMPLE
program.
7. Press LOAD.
If the program has components (parameters) which are not in the
LIN database then an error message will appear and the program LOAD
will not load.
After a successful load, the Programmer menu reappears.
10:19:28 Program Load 18/04/08
8. Press EDIT
The Program Editor page appears showing various values in tabular Programmer
form, starting with channels, followed by any user values and PROGRAMS SCHEDULE EDIT
finally events. PREVIEW MONITOR START
In the default display, each column represents a segment, and each HOLD ABORT RESET
LOAD
segment is identified by a name or number shown at the top of the SKIP ADVANCE REDO
column. Under the segment identifier is the time duration of the seg-
ment. For each channel, the type of segment is given together with 0/0
SAMPLE
Segment name
its setpoint. User values show the current value of the parameter. 12:04:41
IDLE 00:00:00
Program Edit
???
18/04/08
Events are displayed as a six*-character string (large frame = 12 Segment duration I
Segment type
P D H
NITIALISE UMP OWN EAT
characters), which can be decoded by touching the relevant cell to 00: 05: 00
STEP
00: 10: 00
DWELL
01: 00: 00
RAMPTIME
Channel name T
display the event status.
EMPERAT
30 30 800
C DEG
STEP STEP DWELL
PRESSURE
1.00E+03 1.00E-03 1.00E-03
User value MBAR
The default screen can be edited as described in section 4.1.9, be- Events
V A C U U M A 0.00E+00 0.00E+00 0.00E+00
MBAR
low. This allows, amongst other things, segment start and end times EVENTS 000 100 001 100 001 100
to be added and events to be listed individually. 1-6
HA029280 Chapter 4
4.1.3 SEGMENT NAME

Touching on a segment name cell produces a ‘Segment details’ pop-up. Figure 4.1.3a, below shows the default
view.
Segment Details
SE PUMP DOWN Segment Name: Pump Down
00: 10: 00 01: 0
DWELL RA Segment Duration: 00:10:00 HEAT Segment start
00: 15: 00
30
Go back to: <Nowhere> 01: 00: 00 Segment duration
01: 15: 00
Segment finish
DELEtE inSERt oK CanCEL
Figure 4.1.3a Segment details default Figure 4.1.3b Segment time display options
Segment Name Allows the segment name to be edited if required.

Segment Start If selected for view (using the Editor ‘Layout’ key described below) this shows the seg-
ment start time relative to the start of the program. Not shown in fgure 4.1.3a above.
Segment Duration Allows the segment duration to be edited.
Segment Finish If selected for view (using the Editor ‘Layout’ key described below) this displays the seg-
ment end time relative to the start of the program. Not shown in fgure 4.1.3a above.
Go back to This allows a specific segment to be selected (from a picklist) to be returned to, once the
segment has completed. In our example, ‘Pump Down’ is the second segment, so only
‘Initialise’ and ‘<Nowhere>’ appear in the picklist.
DELETE This key allows the user to delete the segment from the program. The segment is de-
leted without confirmation.
INSERT Allows the user to insert a new segment, which appears immediately before the current
segment. The segment is named ‘n’, where ‘n’ is the number of the segment. For ex-
ample, if the new segment is the fourth segment it is named ‘4’. By default the segment
type is ‘Dwell’ and the default value is the target value of the previous segment.
OK, CANCEL OK accepts the new edits and closes the window; CANCEL ignores any edits and closes
the window.
Chapter 4 HA029280
4.1.4 Channel name

Touching a Channel Name cell causes a pop-up window to appear, with the same title as the channel. As
shown in figure 4.1.4 below, this window gives access to a number of parameters, depending on whether this is
a one channel application or multi-channel..
00: 0
STEP
TEMPERAT
DEGC
STEP
RESSURE
Channel name Channel name

Low Limit: 0 degC Low Limit: 0 degC
High Limit: 1500 degC High Limit: 1500 degC
Servo: PV Servo: PV
Hb & Alarm Mode: NONE PV Start: Off
Hb & Alarm Mode: None
oK CanCEL Rate Units: /sec
Multi-channel display End condition: Reset
oK CanCEL
Single-channel display
Figure 4.1.4 Channel Name display
Low limit The low limit for the channel.

High Limit The high limit for the channel.
Servo Off: No servo applied at start up.
PV: 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. Used only at the beginning of the program.
SP: 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. Used only at
the beginning of the program.
PV Start Appears here for single channel applications only. See ‘PROPERTIES’ in section 4.1.9,
below for multi-channel applications.
Off: the program starts at the beginning of the first segment.
Rising: the program advances to the first rising segment that contains the current PV.
Falling: the program advances to the first falling segment that contains the current PV.
Hb & Alarm Mode: None: No holdback or alarms used on this channel throughout the program.
PerProg: The holdback value used in segment one is used throughout the program on
this channel.
PerSeg: Each segment uses its own holdback value.
Rate Units Choose ‘/sec’, ‘/min’, ‘/hour’ or ‘/day’ as units for Ramp Rate segments (does not appear
for multi-channel applications, because ‘Ramp Rate’ is not allowed as a segment type).
End condition Appears here for single channel applications only. See ‘PROPERTIES’ in section 4.1.9,
below for multi-channel applications.
Reset: returns the setpoint value to the first segment start value
Dwell: the program remains at its end value(s) until restarted.
HA029280 Chapter 4
4.1.5 Segment type

Touching a Channel Segment Type cell causes a pop-up window to appear, with the same title as the channel.
As shown in figure 4.1.5,, this window gives the segment name (view only) and two configuration items: ‘Seg-
ment Type’ (Step, dwell, ramp rate, ramp time) and ‘Target’.
PUMP DOWN
00: 10: 00 01:
DWELL RAM
30
Channel name Channel name

Segment Name: pump down Segment Name: pump down
Segment Type: DWELL Segment Type: DWELL
Target: 30 degC Segment duration: 00:05:00
Holdback and Alarms Target: 30 degC
Hb & Alarm Value: 800 degC Holdback and Alarms
Holdback Type: Low Hb & Alarm Value: 800 degC
Deviation Alarms: Low Holdback Type: Low
OOB Alarm: High Deviation Alarms: Low
Alarm Delay: 00:00:00 OOB Alarm: High
oK CanCEL Alarm Delay: 00:00:00
Multi-channel display oK CanCEL
Single-channel display
Figure 4.1.5 Segment type displays
Segment Name The name of the segment - not editable in this window.
Segment Type Allows the user to select from:
STEP: Setpoint is set to the Target value immediately, and remains there for the remain-
ing segment duration.
DWELL: Segment value remains constant at the finish value of the previous segment.
RAMPTIME: The setpoint value ramps linearly from the current value to the Target value
over the segment duration time.
RAMPRATE: The setpoint value ramps from the current value to the Target value at the
specified rate. Segment duration is set to (New Target - Old Target)/Rate.
Target Allows the user to enter target setpoints, ramp rates etc. Not editable for Dwell seg-
ments.
Notes:
1. A segment may not ramp at less than 0.001 or greater than 9999.0 whether expressed explicitly in
a ‘Ramprate’ command, or implicitly in a ‘Ramptime’ command. Values outside this range cause the
segment to execute a ‘step’ function.
2. It is possible to make changes to any target setpoint, thus affecting the program ‘time remaining’
value. Where changes have been made to segments that have already been executed, the trend
shape and the cursor position in the Monitor display may be incorrect; the Monitor ‘time remain-
ing’ and faceplate setpoint values will, however, be accurate for the current program cycle. The
situation is self correcting in that the cursor position and graph shape will be accurate next cycle or
program run.
Chapter 4 HA029280
4.1.5 SEGMENT TYPE (Cont.)
HOLDBACK AND ALARMS

This section appears only if ‘Hb & Alarm Mode’ is set to a value other than ‘NONE’ in ‘Channel name’ (section
4.1.4).
Hb & Alarm Value Appears only if ‘Hb & Alarm Mode’ is set to ‘per Segment’ in ‘Channel name’ . Allows a
Holdback value to be set for this segment.
Holdback Type Appears if ‘Hb & Alarm Mode’ is set to ‘per Segment’ or ‘per Channel’ in ‘Channel name’.
Allows the user to select ‘None’, ‘Low’, ‘High’ or ‘Band’.
Deviation Alarms Appears if ‘Hb & Alarm Mode’ is set to ‘per Segment’ or ‘per Channel’ in ‘Channel name’.
Allows the user to select ‘None’, ‘Low’, ‘High’ or ‘Band’.
OOB alarm Appears if ‘Hb & Alarm Mode’ is set to ‘per Segment’ or ‘per Channel’ in ‘Channel name’
(section 4.1.4). Allows the user to select ‘None’, ‘Low’, ‘High’ or ‘Band’. Alarm is set
(latched) if any channel PV has been out of bounds during program execution and clears
only when the program is reset.
Alarm delay Appears only if ‘Hb & Alarm Mode’ is set to ‘per Segment’ or ‘per Channel’ in ‘Channel
name’ (section 4.1.4). Allows the user to enter a delay such that if a value returns to a
non-alarm state from an alarm state within this time, then the alarm is ignored.
4.1.6 User values

Touching a User Value title cell (to the left of the thick vertical bar), causes a pop-up window to appear, with
the same title as the channel. The pop-up contains non-editable values for High and Low limits.
Touching a user value segment cell causes a pop-up window to appear, with the same title as the channel. As
shown in figure 4.1.6, this window gives the segment name (view only) and a one editable item: ‘Value’.
Vacuum A
Segment Name: pump down
Value: 0.00E+00 mbar
oK CanCEL
Figure 4.1.6 User Value segment display
HA029280 Chapter 4
4.1.7 Event displays
COMPRESSED EVENTS
By default, event status is coded in groups of six (e.g. Events 1 to 6, Events 7 to 12) for the small-frame unit
or in groups of 12 for the large-frame unit. An example of such a code is: 100 100, indicating that Events one
and four of the group are active and events two, three, five and six are not active. Touching the relevant cell
produces a display showing what the actual events are, and allowing their status to be set:
Events Details
Segment Name: Initialise
1st event For small-frame units,
in group use scroll bar to dis-
A 0.00E+00 Fan: OFF close hidden events
MBAR
Heat: Disable
EVENTS 000 100
1-6 Cool: Disable
TS 101 100 4th event Pressure: Enable
in group
oK
Figure 4.1.7 Compressed Events
UNCOMPRESSED EVENTS
The Editor ‘Layout’ display (described in section 4.1.9 below) can be used to disable ‘Compressed events’, in
which case, each event appears as a separate row. Touching the relevant segment cell produces a display al-
lowing the status of the individual event to which the cell relates, to be edited.
4.1.8 Wait and Exit conditions

Each segment can have a a number of wait conditions (Open*, Closed*, NoWait) applied. These conditions are
displayed as described for compressed events, above.
‘Open’ means that the segment will wait until the relevant input is open; ‘Closed’ means that the segment will
wait until the relevant input is closed; No wait means that the condition is ignored. If any of the wait condi-
tions is true, then the segment waits.
‘Exit’ is similar to ‘Wait’ except that the segment terminates immediately on any of the conditions becoming
true. Exit is not applicable to Ramp segments.
*Note: The actual text which appears is defined in programmer configuration. ‘Open’ and ‘Closed’ are
used here only as examples.
Chapter 4 HA029280
4.1.9 Option keys

A number of keys (figure 4.1.9a) can appear at the lower edge of the screen, when the Option key is operated.
On the small frame unit, the Option key must be operated a number of times to ‘scroll through’ the complete
set of keys. On the large frame unit, all the keys are displayed simultaneously.
LOAD SAVE SAVE AS NEW PROPERTIES LAYOUT VIEWS REVISION

Option key
Figure 4.1.9a Option keys
LOAD
Produces a picklist allowing the user to select a different program
SAVE
Saves (without confirmation) the current program, including any edits.
SAVE AS
Allows the current program to be saved with a different Program name and/or File Name.
NEW
Allows the user to create a new program - initially containing just an ‘End’ segment. Further segments are
added by touching the End’ segment cell and Inserting a segment as described in section 4.1.3, above.
PROPERTIES
Calls the program ‘properties’ window shown in figure 4.1.9b below.
Properties Properties
Program Name: Test program Program Name: Test program
Cycles: 1 Cycles: 1
PV Start: Off
oK CanCEL End Condition: Reset
Single channel applications Rate Units: /sec
oK CanCEL
Multi-channel applications
Figure 4.1.9b Properties page
Program Name Allows the program name to be edited.
Cycles Allows the user to specify the number of program cycles (up to 999) to be performed. A
value of 0 causes the program to execute continuously for a maximum of 65535 cycles or
until stopped.
PV Start Appears here for Multi-channel applications only; located in ‘Channel’ (section 4.1.4) for
single channel applications.
Off: the program starts at the beginning of the first segment.
Rising: the program advances to the first rising segment that contains the current PV.
Falling: the program advances to the first falling segment that contains the current PV.
End condition Appears here for Multi-channel applications only; located in ‘Channel’ (section 4.1.4) for
single channel applications.
Reset: returns the setpoint value to the first segment start value
Dwell: the program remains at its the end value(s) until restarted.
Rate Units Choose ‘/sec’, ‘/min’, ‘/hour’ or ‘/day’ as units for Ramp Rate segments.
HA029280 Chapter 4
4.1.9 OPTION KEYS (Cont.)
LAYOUT
Allows to enable/disable a number of display layout features.
Editor layout
Long SP names: NO
Segment start: NO
Segment duration: YES
Segment finish: NO
Wide cells: NO
Transpose: NO
Compressed Events: YES
oK
Figure 4.1.9c Layout page
Long SP names: YES’ Allows non-truncated parameter / channel names to appear.
‘NO’ truncates segment and parameter names to eight characters.
Segment Start ‘YES’ causes the segment start time (relative to program start time) to appear under each
segment name.
Segment duration ‘YES’causes the duration of the segment to appear under each segment name. If ‘Seg-
ment Start’ is enabled, Segment duration appears after Segment start.
Wide Cells Increases the width of the cells.
Transpose This field appears only for the large frame unit an allows the display to appear with the
sements arranged vertically and the channels/user vaues etc. to appear across the top
(figure 4.1.9d).
Compressed events If ‘YES’, the event fields appear as a string of ‘1’s and ‘0’s according as the event is active
or not. See section 4.1.7, above, for details.
VIEWS
Allows the user to add different views of the process to the Edit display. These are all described in sections 3.1
to 3.3 for the small-frame version of the instrument. Figures 4.1.9d and 4.1.9e, below show the large-frame
instrument.
Preview adds a graphical representation of the program.
Monitor adds a graphical representation of the process, but includes the various monitor keys.
Schedule adds details of scheduled start and stop times.
REVISION
Shows how many times the program has been changed since ‘New’; also shows the date and time of the latest
edit.
Chapter 4 HA029280
4.1.9 OPTION KEYS (Cont.)

Test program 0/0
RUNNING Heat RESET ENGINEER
07: 11: 36 95% 897-14:0
11:42:43 Program Edit 22/04/08
Initialise Pump down Heat Equalise Heat 2 Soak Cool Quench Finalise
00:50:00 00:10:00 01:00:00 00:20:00 01:00:00 04:00:00 00:30:00 00:15:00 01:00:00
STEP DWELL RAMPTIME DWELL RAMPTIME DWELL RAMPTIME RAMPTIME RAMPTIME
Temperat 30 30 800 800 1050 1050 900 100 30
degC
STEP STEP DWELL DWELL DWELL DWELL DWELL DWELL STEP
Pressure 1.00E+03 1.00E-03 1.00E-03 1.00E-03 1.00E-03 1.00E-03 1.00E-03 1.00E-03 1.00E+03
mbar
Vacuum A 0.00E+00 0.00E+00 0.00E+00 0.00E+00 0.00E+00 0.00E+00 0.00E+00 0.00E+00 0.00E+00
mbar
Thermal 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
%
Spread H 0 0 0 0 0 0 0 0 0
degC
Events 000 100 000 100 001 100 001 100 010 100 010 100 000 100 100 100 100 000
1-6
Temperat Temperat
421.0 421.0
0.0 1500.0 0.0 1500.0 File Name: Sample - a
PREVIEW Pressure MONITOR Pressure Start Date: 22/04/08
0.0 0.0 SCHEDULE
0.0 1200.0 0.0 1200.0
touch/Drag
Cursor
Segment Name: Heat
Prog Time Remaining: 06:47:44 ACCEPT CANCEL
03:44:16 Soak
Figure 4.1.9d Edit page - large frame unit with Preview, Monitor and Schedule displayed
Test program 0/0
RUNNING Heat RESET ENGINEER
07: 11: 36 95% 897-14:0
15:00:01 Program Edit 22/04/08
Temperat
421.0
Temperature Pressure Vacuum A Thermal Hea Spread Hold Events 0.0 1500.0
degC mbar mbar % degC PREVIEW Pressure
1-6 0.0
Initialise STEP STEP 0.0 1200.0
00:50:00 30 1.00E+03 0.00E+00 0.0 0 000 100
Pump down DWELL STEP

00:10:00 30 1.00E-03 0.00E+00 0.0 0 000 100 touch/Drag
Cursor
Heat RAMPTIME DWELL

01:00:00 800 1.00E-03 0.00E+00 0.0 0 001 100 03:44:16 Soak
PLOT
Equalise DWELL DWELL Temperat

421.0
00:20:00 800 1.00E-03 0.00E+00 0.0 0 001 100 0.0 1500.0
MONITOR Pressure
0.0
Heat 2 RAMPTIME DWELL 0.0 1200.0
01:00:00
1050 1.00E-03 0.00E+00 0.0 0 010 100
Soak DWELL DWELL

04:00:00 1050 1.00E-03 0.00E+00 0.0 0 010 100 Segment Name: Heat
Prog Time Remaining: 06:47:44
Cool RAMPTIME DWELL
00:30:00 900 1.00E-03 0.00E+00 0.0 0 000 100
HOLD ABORT RESET SKIP
Quench RAMPTIME DWELL

00:15:00 100 1.00E-03 0.00E+00 0.0 0 100 100 File Name: Sample - a
SCHEDULE
Finalise RAMPTIME STEP Start Time: 09:53:40
01:00:00 30 1.00E+03 0.00E+00 0.0 0 100 000
End
ACCEPT CANCEL
LOAD SAVE SAVE AS NEW PROPERTIES LAYOUT VIEWS REVISION
Figure 4.1.9e Edit page - as fig 4.1.2a but with Transpose = YES (in LAYOUT) and Option key operated
HA029280 Chapter 4
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
simultaneously, 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
The Logging Groups page appears, showing data for a single PROGRAMMER LOGGING HOME
group.
To scroll between groups, press either the < or > keys can be 2
used. 1 Press LoGGinG
For any group, the fields are as follows: Press menu key
Logging
GROUP NAME This is an identifier given to each group of 3
MONITOR MANAGE
data. To name a file or to change a file name, Press GRouPS
first turn ‘Logging’ to ‘OFF’ (see next para- GROUPS FTP
graph), then re-enter the name.

LOGGING This shows ‘ON’, ‘OFF’, or ‘TRIGGER’. What is 09:08:23 Logging Groups 05/04/06
Group Name: lgrp1
shown depends upon whether logging is cur- Logging: ON
rently on, off, or set to start when an event Configuration
Archive Int: 00:01:00
is triggered. (The event is specified by the File Type: ASCII
customer and is configured at the factory or by Name Type: Hourly
the OEM.) File Name: AA000017.ASC
Column Titles: Present
To change the current setting, press the yel- Date Format: Date Time
lowed Logging field and select ON, OFF or SAVE MONITOR LOG NOW
TRIGGER as required, then press ENTER. The
Logging Groups page now shows the new set-
ting against ‘Logging’.
Chapter 4 HA029280
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 log-
ging 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 automati-
cally 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.
HA029280 Chapter 4
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 sam-
ples 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 pre-
vious 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 Septem-
ber 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
Chapter 4 HA029280
4.2.2 FTP Transfer

The FTP transfer mechanism allows the instrument to act as a FTP client to up to three FTP servers for the
purpose of transferring the internal archive files to a remote computer. If more than one FTP server is config-
ured then the transfer may be configured to operate in either multiple copy or single copy mode.
Notes:
1. The FTP Ethernet port must be correctly configured in the Comms set up page (section 4.5.1)
2. The host computer must be set up as an FTP server (this procedure depends on the FTP server soft-
ware being used).
3. Transfer frequency (daily, hourly etc.) is as configured in the LOGDEV LINTools block.
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 internal archive file. 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 configured).
CONFIGURATION
archive FtP Servers
Revision: 19 13/05/09 14:51:54 aDMin
Single copy: no
(1/3)
Appears only if Auditor
Host: 123.456.128.150 option enabled
Enabled: YES
user name: anonymous
+:
Password: *************************
Directory: FtP_Root1
+:
+:
(2/3)
Host: 123.456.128.172
Enabled: YES
+:
Password: *************************
+:
+:
(3/3)
Host: 123.456.128.230
Enabled: YES
+:
Password: *************************
+:
+:
SaVE
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 The IP 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. If more than 40 characters are
required, both fields must be used.
Password The password (max. 24 characters) to be used when logging in to the remote computer (this value is
not displayed for security reasons).
HA029280 Chapter 4
4.2.2 FTP TRANSFER (Cont.)
Directory: Known as an’ FTP virtual directory’, this is the directory (folder) on the remote computer where the
files are to be stored. For security reasons FTP servers normally permit access only to a limited area of
the host computer by re-mapping the directories. It is the re-mapped name that must be entered here.
If more than 40 characters are required, two or three fields must be used.
The instrument must be power cycled to effect the changes.
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 Ap-
plication 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 deleted. 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 Dis-
playing 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.
Chapter 4 HA029280
4.3.1 Application summary page 2

Press SYStEM
This page displays the percentage of the instrument’s various memo-
ry resources that are currently in use. ACCESS SYSTEM ALARMS

Press the Menu key and select SYSTEM from the pop-up menu.
System
1 SUMMARY APPLN
Press menu key 3
SETUP CLONING
Press aPPLn
Select APPLN then APP SUM.

Application
APP SUM APP MGR FB MGR

4
Press aPP SuM
The Application Summary page appears, showing:
09:10:00 Appl'n Summary 05/04/06
1 the name of the loaded application, Application: ise

Machine State: RUNNING
2 its state (RUNNING, IDLE, or STOPPED), Memory Usage

Control DB: 128 kB 76%
SFC DB: 73 kB
3 data about memory usage. 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.
2
Press the Menu key and select SYSTEM from the pop-up menu. Press SYStEM
System
1 SUMMARY APPLN
Select APPLN from the SYSTEM window to display the Applica-
Press menu key 3
tion window. SETUP CLONING
Press aPPLn
Select APP MGR.

Application
APP SUM APP MGR FB MGR

4
Press aPP MGR
09:10:34 Appl'n Manager 05/04/06

The Appl’n Manager page appears, displaying the name of
the current application and its state (i.e. RUNNING, IDLE or File: RISE
STOPPED. State: RUNNING
UNLOAD SAVE SAVE AS STOP
HA029280 Chapter 4
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 (ex-
cept for the actual file name) as shown in the figure.
To stop the application, press STOP UNLOAD SAVE SAVE AS STOP
09:11:08 Appl'n Manager 05/04/06
The display confirms that the application has STOPPED, File: RISE
State: STOPPED
Note: While an application is STOPPED, the Logging and Program-

mer facilities will be suspended. The duration of the current seg- UNLOAD SAVE SAVE AS START
ment 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 applica-
tion, 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.
Chapter 4 HA029280
4.3.4 Saving application data 09:11:08 Appl'n Manager 05/04/06
File: RISE
State: STOPPED
The application must be stopped before application data can be
saved.
UNLOAD SAVE SAVE AS START
09:11:25 Appl'n Manager 05/04/06
Select SAVE
File: RISE
STOPPED
State:Saving
File: RISE.DBF
Saving starts, confirmed by a ‘Saving’ window. Please wait...
To save the current application data under a different name, select 09:11:42 Appl'n Manager 05/04/06
SAVE AS.
File: RISE
SAVESTOPPED
State: AS
File: RISE
A ‘SAVE AS’ window appears, with a yellowed field into which anoth- OK CANCEL
er file name can be entered if required (not shown).

09:11:59 Appl'n Manager 05/04/06

To re-start the application, select START
File: RISE
State: RUNNING
The Appl’n Manager page reverts to its opening display, reporting the
current application running.
You can also use START to start another application that you might
have loaded. UNLOAD SAVE SAVE AS STOP
09:12:16 Appl'n Manager 06/04/06

4.3.5 Unloading an application
The application must be stopped before it can be unloaded. File: RISE
State: STOPPED
Select UNLOAD
The screen might go blank for a few seconds while the application
unloads.
When the unloading is complete, the Appl’n Manager page should 09:12:33 Appl'n Manager 06/04/06
look like this, with three keys offering LOAD, LD+RUN, and DELETE.
File: RISE
This is 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 an-

other application, or to delete an application.
LOAD LD+RUN DELETE
HA029280 Chapter 4
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 unload-
ed.
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 Re- State: IDLE
turn key.

The name is displayed in the File field.
09:13:07 Appl'n Manager 06/04/06
File: RISE
State: RUNNING
UNLOAD SAVE SAVE AS STOP
APPLICATION LOADING
If you select LOAD, there is a short delay before the page shows the
name of the application and its state, IDLE.
*** No application loaded ***
09:13:24 Appl'n Manager 06/04/06
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 File: RISE
can be achieved using LOAD, then START.
LOAD LD+RUN DELETE
4.3.7 Deleting an application

*** No application loaded ***
09:13:41 Appl'n Manager 06/04/06
File: RISE
The application must be stopped and unloaded before it is deleted.
Confirm Delete
File: RISE
OK CANCEL
Press DELETE
LOAD LD+RUN DELETE
The Confirm Delete window appears.
Press OK
Chapter 4 HA029280
4.3.8 Function Block Manager

Note: If IPRP is enabled, the function block manager is not available.
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. Refer-
ence 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
Rate
15.00
0.000
degC
degC
pair of arrow keys
RampUnit SEC appear at the right-
Out
NewTgtSP
15.00
20.00
degC
degC
hand edge of the
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
HA029280 Chapter 4
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
ddr_diag edbtable ramp5/2 mod5/03 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 cre-
ated.
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 ap-
plication.
Chapter 4 HA029280
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
ddr_diag edbtable ramp5/2 mod5/03
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.
HA029280 Chapter 4
FUNCTION BLOCK DETAILS

10:28:44 ramp5/1 : SPP_RAMP 06/04/06
ResetSP 15.00 degC
Once a function block has been highlighted, touching the down HL_SP
LL_SP
50.00 degC
0.000 degC
arrow key displays block details - Block name, Block type and Track
Alarms
Ramp Dis
FALSE
FALSE
update rate (figure 4.3.8e). PV
TgtSP
15.23
15.00
degC
degC
Rate 0.000 degC
RampUnit SEC
Out 15.00 degC
Note: Displayed units are not updated dynamically. NewTgtSP
NewRate
20.00
0.000
degC
degC
Sync FALSE
Changes in units are therefore not reflected until the Complete
Active
FALSE
FALSE
page is quit and then re-entered. NotActiv

Holdback
Hold
00:00:00
FALSE
FALSE
HB_Mode NONE
10:28:51 ramp5/1 : SPP_RAMP 06/04/06
Block name: ramp5/1

With the data base stopped, the Delete key allows function Block type: SPP_RaMP
blocks to be deleted from the database. update rate: 1000 ms
update rate appears only for applicable

DELEtE Block types. it is shown here only for
example purposes
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)
In the case of subfields, a number is displayed, which is the Wdg<<
number of connections when the database is running, or the Run<<
number of connectable 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 described 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.6, it is possible to set a time period (time-out) after which the access level returns
to ‘Locked’.
Chapter 4 HA029280
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
4.4.2 Editing the passwords Press aCCESS
To change the passwords, carry out the following procedure:
1 Press the Menu key.
The Pop-up menu appears. PROGRAMMER LOGGING HOME
2 Press ACCESS.
1
Press menu key
0/0
RESET
Enter required level and password,
The Security Access page appears, displaying the current access then CHANGE
level (ENGINEER) and two keys: CHANGE and PASSWDS.
Current Level: ENGINEER
New Level: ENGINEER
3 Press PASSWDS Password: ********
CHANGE PASSWDS
0/0
RESET
09:15:40 Passwords 06/04/06
The Passwords page appears. OPERATOR: ********

4 Press the password field you want to change - e.g. Opera- COMMISSION: ********
tor 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 ,
HA029280 Chapter 4
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 ;
z x c v b n m ,
6 Press the Return key
0/0
The Security Access page reappears RESET
Enter required level and password,
then CHANGE
Current Level: ENGINEER

New Level: ENGINEER
7 Press CHANGE Password: ********
CHANGE PASSWDS
For Commissioning Engineer and Operator passwords, the Security Access page reappears with either COM-
MISSION 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.
Chapter 4 HA029280
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, Commission 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.
1 Press the Menu key and select ACCESS from the pop-up menu. RESET
0/0
09:14:49 Passwords 06/04/06
If necessary, change the access level to Engineer
2 Press PASSWDS, then USERS. OPERATOR: ********
COMMISSION: ********
3 Confirm (twice) that the change is to be made.
ENGINEER: ********
4 Login at Admin level, by
a) touching the Identity field and entering ADMIN (must be in
capitals) followed by Return, then, OK CANCEL USERS
b) touching the Password field and entering ADMIN (must be in

capitals) followed by Return, then,
0/0
RESET
c) pressing LOG ON. 09:15:06 Security access 06/04/06
Acess: ADMIN
Name: ADMIN
It is now necessary to create IDs and passwords for other users, and Identity: ADMIN
assign access levels to them, as described in USER ID MANAGEMENT,
below.
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.
HA029280 Chapter 4
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 re-
quired, 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
09:36:13 Security access 06/04/06
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 (in-
cluding 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.
1 Touch the word ENGINEER in the Identity column.
Identity: EnGinEER
2 Touch the word ENGINEER in the Identity field of the resulting dialogue box Password:
********
(figure 4.4.3b). Confirm:
********
oK CanCEL DELEtE DiSaBLE
Figure 4.4.3b ID Edit page
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).
Otherwise press CANCEL.
Chapter 4 HA029280

Editing other fields
The editing of remaining fields is carried out in a similar manner, except for the access level field which is se-
lected 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 per-
missions.
FTP Users with this permission may log in via FTP. FTP users who are View only, are prevent-
ed 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.
HA029280 Chapter 4

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 necessary). 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 previ-
ously ‘retired’ ID. See Chapter 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
specified number of minutes has elapsed since the previous screen activity.
Chapter 4 HA029280

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 unus-
able. 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.
HA029280 Chapter 4
4.5 SETTING UP AND RE-SETTING THE INSTRUMENT

This section describes the following items
1. Editing Comms parameters including time synchronisation (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 time zone information for unambiguous date and time (Section 4.5.5).
6. Setting up the panel display (Section 4.5.6).
4.5.1 Editing communications parameters

The editing procedure for Communications Parameters consists of displaying the Comms Setup page and set-
ting up or editing the parameters for each port fitted to the unit. The SAVE button is used to save the chang-
es, 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 instru-
ment 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
1. Press the Menu key and select SYSTEM from the Pop-up menu. Press SYStEM

2. Press SETUP
System
1 SUMMARY APPLN
Press menu key
3. Press COMMS.
SETUP CLONING
3 4
Press SEtuP
Press CoMMS
Setup
STARTUP COMMS CLOCK
INTERNAT TIME ZONE PANEL
The Comms Setup page appears.
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:
09:41:19 Comms Setup 20/11/08
Hardware Standard (for example, RS485) PORT COM1 COM2 ENET1
Protocol (for example, Modbus Slave) Hardware RS485 RS485 Ethernet
Node Number (decimal) Protocol Modbus/S ELIN
Node No. 1
Baud (rate) Baud 9600
Parity Use the option Parity NONE

key to reveal
Data bits (number of) these keys
Data Bits 8
Stop bits (number of) SAVE CANCEL ETHERNET TIME SYNC

option key
Timeout (Modbus Master only, in milliseconds) and again MODBUS/M/TCP PRINTERS
TalkThru (Modbus slave only)
Figure 4.5.1a Comms setup page
Note: Some of the keys at the bottom of the display appear only if the relevant option is enabled.
Chapter 4 HA029280
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 slide-
bar. 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.
Printer CoM1, CoM2 used to send reports to a maximum of two serial printers.
Printer uSB1, 2, 3 used to send reports to a maximum of two uSB printers.
Printer EnEt6 used to send reports to an Ethernet printer.
Profibus PBuS1 Provides Profibus communications (if Profibus option fitted).
uSB1, 2, 3
Reader CoM1, CoM2 Barcode reader input
uSB1 is fitted as standard; uSB2 and uSB3 are supplied as a single uSB option
Table 4.5.1 Available protocols
Changes to Protocol selection become effective at different times, as follows:
COM1/COM2 On application start

ENET1,2,3 On power up
ENET4 On application start
ENET5 On power-up
ENET6 On power up
PBUS1 On power up
USB1, 2, 3 On power up
HA029280 Chapter 4
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 connected 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.
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, ‘SAVE’, ‘CANCEL’, ‘ETHERNET’
etc. buttons are hidden. The Option key is used one or more times to display these
Option key
buttons (overlaid on the scroll bar).
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
Chapter 4 HA029280

ETHERNET (Cont)
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.
MODBUS/TCP
For each relevant slave node, an entry must be made in the Modbus/TCP mapping table (figure 4.5.1c) which
is accessed by touching the MODBUS/TCP key at the bottom of the Comms setup page (figure 4.5.1a).
tREnD Run prog 3/5
LOCKED Eycon-20 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 dia-
logue 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 mes-
sage 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
documentation advises otherwise.
HA029280 Chapter 4
TIME SYNC
Operation of this key causes the ‘Time Synchronisation’ page to appear (figure 4.5.1d). ‘Server operation’
allows a user with suitable access permission to configure the unit to act as an SNTP server if required. ‘Cli-
ent operation’ allows the unit to act as an SNTP client (receiving time data from an external source), or as a
time-of-day (TOD) master or slave, in which case time synchronisation with other units is carried out using the
TOD_DIAG block in LINtools.
Note: If the unit is successfully synchronising, then the time and date setting fields do not appear in
the clock setup page (section 4.5.3) and a message (e.g. ‘Clock configured as SNTP client’) is displayed
in green text. If the unit is configured to synchronise, but it is not successfully communicating with the
synchronisation source, the same message appears, this time in red, and the time and date fields ap-
pear and can be edited as normal.
09:41:19 Comms Setup 20/11/08
PORT COM1 COM2 ENET1
Hardware RS485 RS485 Ethernet
Protocol Modbus/S ELIN
Node No. 1
Baud 9600
Parity NONE
Data Bits 8
SAVE CANCEL ETHERNET TIME SYNC

option key
0 9 : 4 2 : 0 3 Time Synchronisation 20/11/08
Server operation
Note: The unit can act as both
SntP: YES
SNTP server and SNTP client if
required. Client operation
Method: SntP
Server 1 iP: 123.456.789.012
Server 2 iP: 123.456.123.456
SAVE CANCEL COMMS
Figure 4.5.1d Time synchronisation configuration

SNTP If ‘YES’ is selected, the Unit will act as a time server.
Method SNTP.
If SNTP is selected, then the unit will synchronise with Server 1, if possible, or with Server
2 if Server 1 is not available. For successful operation, the unit and the time servers
must be on the same network as one another - see ‘Ethernet’, above, for details of the
unit’s IP address setting.
Server 1 IP The IP address of a suitable primary SNTP server.
Server 2 IP The IP address of a suitable secondary SNTP server.
NONE/TOD
If None/TOD is selected, then the unit will synchronise with other units according to the
setting of the TOD_DIAG block. If the unit is set up as a TOD master or slave, then the
clock setting is inhibited. Otherwise, the unit is not set up to synchronise and clock set-
ting can be carried out as described in section 4.5.3.
EVENTS
SNTP Svr 1 fail Indicates a failure to obtain a time from Server 1 after three consecutive attempts.
SNTP Svr 2 fail Indicates a failure to obtain a time from Server 2 after three consecutive attempts.
SNTP time jumps SNTP updates caused more than 5 time jumps within 24 hours. A time jump is made if
the unit time if found to differ from Server time by more than two seconds. For time dif-
ferences of up to two seconds, the unit time is corrected gradually, to avoid inconvenient
time jumps.
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 exam-
ple, 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 inappropriate.
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 instru-
ment 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 instru-
ment will do a Cold Start on power-up. 2
Press SYStEM
Neither Hot start nor Cold start
If both Hot start and Cold start are set to ‘No’ the instrument will not PROGRAMMER LOGGING HOME
restart automatically under any circumstances.

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

Press �
StaRtuP INTERNAT TIME ZONE PANEL
4. Select STARTUP
0/0
RESET
Startup Strategy
Hot Start: YES

Cold Start: YES
The Start-up Strategy page appears Hot-start time: 00:00:00
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 inappro-
priate.
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 atten-
tion, 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 warn-
ing, in case some special strategies exist that might need implementing in those circum-
stances, 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 RESET

0/0
09:16:14 Startup Strategy 06/04/06
Hot Start: YES

Cold Start: YES
Changing Hot/Cold start settings
Hot-start time: 00:00:00
Brown-out time: 00:05:00
SAVE CANCEL
In the Startup Strategy page, press the Startup setting to be changed.
Edit the entry using the pick-list which appears, then press Return.
The pick-list disappears and the Startup Strategy page displays the
new value.
simple 0/0
IDLE ??/??/??
09:16:31 Startup Strategy 06/04/06
Changing time-out values 00:10:00
7 8
Hot9Start: YES
Cold Start: YES
4 5 6
Hot-start time: 00:10:00
In the Startup Strategy page, press the time-out value to be changed. 1 2 3 time:
Brown-out 00:05:00
Key-in the new value using the pop-up keyboard, then press Return. . 0
SAVE CANCEL
The field shows the new value.
Chapter 4 HA029280
2
Press SYStEM
4.5.3 Resetting the clock
CLOCK SETUP PAGE ACCESS PROGRAMMER LOGGING HOME
1 Press the Menu key

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

Press �
CLoCK
0/0
RESET
Clock setup
The date/time setting page appears Date: 24/11/08

Time: 14:51:37
CHANGING DATE AND TIME

To increment or decrement the hours value, press the Hr+1 SET CANCEL Hr +1 Hr -1
or the Hr-1 key respectively. The change takes place immedi-

ately, and changes the date if appropriate.
Notes:
1. 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 seconds 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.
2. For time-synchronised systems, if communications with the time server are successfully established,
it is not possible to edit the time or date in the clock setup page. See section 4.5.1 TIME SYNC for
more details.
3. If Daylight saving is set to ‘Yes’ in Time zone configuration (section 4.5.5), then the ‘Hr+1’ and ‘Hr-1’
keys are not displayed.
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
To cancel all the digits (the ones at the top of the keyboard display, 06/04/06
Date: 06/04/06
but not the ones in the Clock Setup page in the background, or in 7 8 9
Time: 15:01:22
memory), press the ‘C’ key - the digits change to question marks. 4 5 6
1 2 3
To cancel the whole time-change operation and return to the Clock
Setup page, press the red cross key. . SET 0 CANCEL Hr +1 Hr -1
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
Before starting, please see note 3 on the previous page. RESET
0/0
15:07:33 Clock setup 06/04/06

15:08:00
From the Clock Setup page, press the time field. Date: 06/04/06
7 8 9
Time: 15:05:07
A keyboard is displayed, with the current time displayed in green at the 4 5 6
top with a cursor flashing under the first hours digit. 1 2 3
Type-in the required time (the cursor moves to the next character after . SET 0 CANCEL Hr +1 Hr -1
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.
1 Press the menu key. 2
Press SYStEM
The Pop-up menu appears.
2 Select SYSTEM. PROGRAMMER LOGGING HOME
The System Pages window appears.

System
SUMMARY APPLN
1
Press menu key SETUP CLONING
3 Select SETUP.
3
The Setup window appears 4 Press SEtuP
Setup
Press �
intERnat STARTUP COMMS CLOCK
4. Select INTERNAT.
0/0
RESET
Internationalise
Language: English
The Internationalise page appears. Date Format: DD/MM/YYYY (DD/MM/YY)
Time Format: HH:MM:SS
Duration Fmt: DD-HH:MM:SS.TTT
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
15:21:42 Internationalise 06/04/06

LANGUAGE English
Language: English
If the Language field is touched, a pick-list appears, showing which Date Format: DD/MM/YYYY (DD/MM/YY)
ENGLISH
languages are available. Select the required language and press FRENCH
GERMAN
Return. Duration Fmt: DD-HH:MM:SS.TTT
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 Date Format: DD/MM/YYYY (DD/MM/YY)
DD/MM/YYYY
Formats 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.
TIME FORMAT RESET

0/0

If the Time Format field is touched, a pick-list of the available time HH:MM:SS
Language: English
formats appears. Select the required format and press Return.
Date
HH:MM:SSFormat: DD/MM/YYYY (DD/MM/YY)
hh:MM
Time XM
Format: HH:MM:SS
The pick-list disappears. hh:MM xM
Duration Fmt: DD-HH:MM:SS.TTT
Press CHANGE. The Time Format field shows the selected time for-
mat. CHANGE
0/0
If the Duration Format field is touched, a pick-list of the available RESET
time duration formats appears. DD/MM/YYYY
Language: English
Select the required format and press Return. Date Format: DD/MM/YYYY (DD/MM/YY)
DD/MM/YYYY
MM/DD/YYYY
YYYY/MM/DD
The pick-list disappears. DD-mmm-YY Fmt: DD-HH:MM:SS.TTT
Duration
mmm-DD-YY
Press CHANGE. The Duration Format field shows the selected for- CHANGE
mat.
HA029280 Chapter 4
4.5.5 Time zone configuration

This allows the user to set up an offset to the instrument time display, to display the time zone either as just a
name, or as a name + offset from UTC (GMT), or, if daylight saving is active, as name +DST. The way in which
these offsets are displayed depends on the instrument model, and on the currently displayed page.
CONFIGURATION
1 Press the menu key.
2
2 Select SYSTEM.
Press SYSTEM
3 Select SETUP.

4 Select TIME ZONE.
System
The default setup page appears 1 SUMMARY APPLN
Press menu key

SETUP CLONING
Touch the yellow Name field and use the normal text/nu- 3
Press SETUP
meric entry techniques to enter a name.
Setup
4 STARTUP COMMS CLOCK

Select an offset direction from a drop down picklist (‘+’ =
Press
ahead of GMT; ‘-’ = behind GMT). TIME ZONE INTERNAT TIME ZONE PANEL
0/0
Enter an offset period, by typing in, for example, RESET
Time Zone
<0><8><Enter> for eight hours.
Name:
Select ‘Yes’ from the drop down menu if daylight savings Offset: + 00:00
time (DST) is to be applied. If ‘Yes’ is selected, the config- Daylight Saving: NO
uration changes to include start and end dates for DST as Time suffix format None
shown in fig 4.5.5b. Values are entered using the normal
SAVE CANCEL
text/numeric entry techniques, and selection from drop
down pick lists.
Figure 4.5.5a
Time suffix format. This allows the user to select ‘None’ Access to Time Zone configuration
(default), ‘Name’, ‘Name+DST’ or ‘GMT offset’ to appear
in association with the time/date display of subsequent RESET
0/0
displays. Time Zone

Name: PST
Offset: - 08:00
Daylight saving: YES
Press SAVE to confirm the changes. Starts at:
on the
01:00
Third
Sunday
of Mar
and ends at: 01:00
on the Third
Sunday
of Oct
Time suffix format: Name + DST
SAVE CANCEL
Figure 4.5.5b Configuration page

(Daylight saving = ‘YES’)
Notes:
1. The time and date in the status panes for small frame units do not include any time suffix format, as
there is insufficient space. Alarm and Event pages do include the information, as described below.
2. If daylight saving is set to ‘Yes’, then the Hr+1 and Hr-1 buttons are not displayed in Clock setup
(section 4.5.3).
3. If daylight saving start and end months are the same, then daylight saving is ignored.
Chapter 4 HA029280
4.5.5 TIME ZONE CONFIGURATION (Cont.)
TIME SUFFIX DISPLAYS

STATUS PANE
As previously stated the small frame version of the instrument does not include Time Zone suffix informa-
tion. The large frame version displays are as shown below. For ‘Name + DST’, the acronym ‘DST’ appears only
whilst daylight saving time is active.
Test program Test program Test program
RUNNING Heat RUNNING Heat RUNNING Heat
07: 11: 36 07: 11: 36 07: 11: 36
11:42:43 PST 11:42:44 PST DST 11:42:45 GMT-08
Name Name + DST GMT offset

Figure 4.5.5c Large frame time zone: Status pane suffix displays
ALARM HISTORY
07:49:50 GMT-08 Alarm History 06/11/08
TYPE ACTIVE GMT-08 CLEAR ACK
ENGINEER Log On 06/11/08 05:55:03 -------- -------- -------- --------

T2550/7 Comms 06/11/08 05:08:51 -------- -------- -------- --------
Eycon-20 BadBat 06/11/08 04:08:51 06/11/08 05:59:26
Database Loaded 06/11/08 05:08:51 -------- -------- -------- --------
Figure 4.5.5d1 Alarm history (large frame)

12:36:59 Alarm History 06/11/08
TYPE GMT-08 CLEAR
Database Restart 06/11 12:35
(Fred)
Database Resumed 06/11 12:35
(Fred)
Eycon-10 BrownOu 06/11 12:35 06/04 12:35
(Fred)
(Fred)
(Fred)
Figure 4.5.5d2 Alarm history: small frame - two line
EVENT LOG
16:14:23 Event Log 08/11/08
GMT-08
04/04 16:00 ACTIVE Shift DigA15
04/04 14:30 TREND Abort
04/04 14:20 TREND Finish
Figure 4.5.5e Event log (small frame shown; large frame similar)
TREND REVIEW
In small frame, the time zone suffix normally replaces the zoom factor. When the zoom factor is changed, the
zoom factor is displayed instead of the time zone suffix until the first cursor operation.
DSP 3 DSP 3
48.75 48.75
48.55 48.55
DSP 4 DSP 4
OPEN OPEN
07/11/08 10:27:05 (x2) 07/11/08 10:29:00 PST
Cursor date Cursor time
Zoom factor Time zone suffix
Figure 4.4.5f trend review display (small frame)
HA029280 Chapter 4
4.5.6 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-

2
out).
Press SYStEM
If this is enabled (by adding an entry into the text dictionary (Section
5.2.4, No. 331)) then a time-out period can be set. If the screen is ACCESS SYSTEM ALARMS
not touched during this period, the instrument access level returns PROGRAMMER LOGGING HOME
to ‘Locked’.
System
1 SUMMARY APPLN
Press menu key
SETUP CLONING
ACCESS TO THE PANEL SETUP PAGE 3
1 Press the menu key. Press SEtuP
2 Select SYSTEM. Setup
3 Select SETUP. STARTUP COMMS CLOCK
4 Select PANEL. 4
Press PanEL
Panel Setup
The Panel setup page appears BACK-LIGHT
Brightness: 70%
Saver brightness: 20%
Timeout: 0 minutes
PAGE TIMEOUTS
Home: 0 minutes
only if the relevant
Pop-up: 0 entry has been
seconds
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

70% BACK-LIGHT
Brightness:
Brightness 70%
Choose the required value(s), then Press Return Saver brightness
brightness: 20%
100% Timeout: 0 minutes
90%
80% PAGE TIMEOUTS
70% Home: 0 minutes
The pick-list disappears. 60% Pop-up: 0 seconds
Data Entry: 0 seconds
Access: 0 minutes
To save the selection, press SAVE.
SAVE CANCEL
Chapter 4 HA029280
4.5.6 SETTING UP THE PANEL DISPLAY (Cont.) 15:57:27 Panel Setup 06/04/06
BACK-LIGHT
BACK-LIGHT 0
Brightness: 70%
TIME-OUTS 7 Saver8 brightness:
9 20%
Timeout: 0 minutes
4 5 6
PAGE TIMEOUTS
1 2 Home: 3 0 minutes
Pressing any of the other fields brings up a numeric keyboard, from Home:
Pop-up: 0 seconds
. 0Entry:
DataPop-up: 0 seconds
which new values for the various time-outs can be entered. Da Access:
Data Entry: 0 minutes
SAVE CANCEL
After each entry, press Return.
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
replicate 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
16:14:25 Cloning 06/04/06
The Cloning page appears. Application
4 Press the Application field (yellowed)
EXPORT IMPORT
0/0
RESET
A pick-list appears, allowing ‘System’, ‘Application’ or ‘ALL‘ to be 16:14:55 Cloning 06/04/06
Application
selected
Application
System
Application
The highlighted field (‘Application’ in this example) indicates which All
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 SFCs: NO
fields, described below Programs/Recipes: NO
User Pages: NO
1 Control Database
Forms: NO
2 SFCs (Sequential Function Charts) Comms Profiles: NO
3 Programs/Recipes EXPORT CLEAR
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 been created on this instrument
and which the user now wishes to copy to another instrument. Recipes and Programs
consist of .uyy, .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
SELECTING SYSTEM DATA 16:24:26 Cloning 06/04/06

Application
Application
System
Application
From the Cloning page, showing the pick-list of System, Application and All
All, select System
EXPORT IMPORT
Press Return
0/0
RESET
16:26:20 Cloning 06/04/06
System
The Cloning page confirms the selection.
EXPORT IMPORT
EXPORTING SYSTEM DATA

0/0
RESET
Select EXPORT. 16:28:30 Cloning 06/04/06
System Data
Config Options: NO
The System Data Cloning page appears with three fields as described Dictionaries: NO
below: User Pages: NO
1, Config Options
EXPORT CLEAR
2. Dictionaries
3. User Pages
Config Options These are: startup strategy, panel settings, comms settings, and current language. Basi-
cally 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
preferences.
From the Cloning page, select IMPORT. The same page appears as for exporting (shown above) and the same
explanations 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,
networked instrument. It also allows files to be deleted from the internal memory (except from the ‘H’ drive
- the internal 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 ‘Mainte-
nance’ 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
Appl'n Manager
Application 16:41:25 06/04/06
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 FiLE MGR
Press StoP
BatCH Maint CoMPat
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 _DEFAULT.OFL must not be deleted or the faceplates in the overview page will fail to oper-
ate 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
OK CANCEL Files must not be deleted from the ‘E’ drive
unless it is certain that the control system
will not be impaired by so doing. See the
cautionary 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: ????????
SuMMaRY aCCESS aPP MGR 2

SEtuP Maint EVt LoG
Press aPP MGR
LoaD LD+Run DELEtE
1
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 edi-
tor 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 down-
loaded.
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 display 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 impor-
tant.
To add the first variable, press the RCP cell, then the INSERT key on the pop-up menu. The name and tag refer-
ences 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
ensure 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 oK
0.1037 D E L E t0.1037
E 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
references 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 incre-
mented 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 down-
load 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 applica-
tion, 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.
CAPTURE 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)

IPRP (also known as IP protection or OEM protection) is configured using LINtools software. For further
details see the LINtools help system (normally viewed on screen, but also available as a printable manual
HA236001U055.pdf).
IPRP allows individual files to be encrypted with a password. This means:

1. access to an encrypted file can be gained only by a user who is in possession of its password
2. an encrypted file can be used only on instruments authorised to use the file’s password.
A Visual Supervisor can be authorised with up to seven different passwords at any one time.
Encryptable file types are database files, sequences, actions and recipes.
Notes:
1. Each file can have the same password as one or more other files, it can have a unique password or it
can have no password at all.
2. Files with different passwords can run together provided that the Visual Supervisor on which they
are running is authorised to use all the relevant passwords.
3. The Flash memory cannot be cloned
4. If IPRP is configured, the Function Block manager (section 4.3.8) is not available, and the Control
Configurator (Section 8) cannot view or edit data.
5. If a recipe is encrypted, it is not possible to view or edit its values at the instrument.
HA029280 Chapter 4
4.10 BATCH MAINTENANCE

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
unLoaD SaVE SaVE aS StoP
SUMMARY APPLN
3 6
Press unLoaD
SETUP CLONING 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
7 8 Press Maint
Press menu key
Maintenance
StoP
5 9 CLoninG FiLE MGR FiLE MGR
Press StoP Press
BatCH Maint CoMPat
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
software, 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
4.11 COMPATIBILITY
This allows the user to set the instrument to operate with the previous programmer version (now called the
‘Legacy Programmer’) as described in Annex D to this manual. The feature also allows the user to to select
one of three different ratios of Function Block memory : SFC memory, as appropriate to the way in which the
instrument is to be used.
These settings are accessed via the Maintenance menu, which is itself accessed as described in section 4.10,
above.
Maintenance
CLoninG FiLE MGR FiLE MGR
BatCH Maint CoMPat
11:32:40 Compatibility 13/05/08
Select new compatibility features and

press CHANGE
Memory Model: Default
CHanGE CanCEL
11:32:40 Compatibility 13/05/08

Default
Select new compatib
compatibility features and
Legacy programmer
press CHANGE
Large SFC
Memory Model: Default
Default
Large Database
CHanGE CanCEL
Figure 4.11 Compatibility menu

Legacy programmer Sets the instrument programmer to the type used in previous instrument versions, and as
described in Annex D to this manual. 128 kB of database.
Large SFC SFC = 73 + 112 kB; database memory = 160 kB
Default SFC = 38 + 56 kB; database memory = 224 kB
Large DB SFC = 19 + 28 kB; database memory = 288 kB
HA029280 Chapter 4
4.12 EDITING A PROGRAM (APPLICATION EDITOR VERSION)

The editing process is carried out in one of two ways, according to the Visual Supervisor configuration. Sec-
tion 4.1 describes the ‘spreadsheet’ method where the program segments and their parameters are arranged
in a grid. Section 4.12 describes the ‘Application editor’ method, where programs can be created and edited
using a fixed set of segment types (segment classes), these types being created using the ‘Programmer Appli-
cation Editor’ software included with LINTools.
4.12.1 Introduction
As described in the preceding paragraph, this method of creating or editing programs involves the use of
a library of up to 20 segment classes which can be assembled, in any appropriate order, to create or edit a
program. Segments might range from those with no operator input (for example a dwell segment for a fixed
period) to more complex segments where, for example, the operator may have to choose between two or
more fixed values, or even to fill in a full set of parameters (e.g. ramp rate, set point, fall back value etc.).
The Visual Supervisor operator cannot create a segment type; this being done at a pc running LINTools and
the ‘Programmer Application editor’ software. The Help systems for these programs describe how to create
segment types and download them to the Visual Supervisor, but for completeness, some examples are given in
Appendix E to this manual.
As shown in the various illustrations in section 4.12.3, segments are represented by push buttons which con-
tain the ‘Short Name’ for the segment class against a background filled with the colour selected for that seg-
ment class when it was created. The text is black for all segments except for the current segment (parameters
displayed on the screen) the text of which is white. Text colours should be taken into account when selecting
background colour. See Appendix E for details of short names and background colour selection.
4.12.2 Default edit page
As shown in figure 1 ACCESS SYSTEM 2

Press menu key Press PROGRAMMER key
4.12.2, to display the 11:13:38 ALARMS PROGRAMMER Program Edit 18/05/09
default edit page, press
the menu key, then ‘PRO- Programmer 3 Unit: pro3
Press EDIT key Program: RKN - Heat1
GRAMMER’ and finally ‘EDIT’. File Program
PREVIEW MONITOR START Either 4 Name Name
The default edit page ap- HOLD ABORT RESET and Program.
pears. SKIP ADVANCE REDO
If there are previous pro- 5

grams, one of these can be LOAD SAVE SAVE AS DELETE
selected for edit from the

‘Programs’ area (in the top 0
NODATA
1290
right hand ‘quarter’ of the 0

NODATA
100
screen) and ‘LOAD’ pressed, 4

followed by a further opera-
tion of the ‘EDIT’ key. NEW INSERT DELETE PROPERTIES VIEWS REVISION UNIT DETAIL
To create a new program, New Program
press ‘NEW’ near the bottom File Name: NEW 5

Enter file name and
left-hand corner of the screen Program Name: New
program name 00:00:00
and enter an appropriate file OK CANCEL
name and program name as

requested. Figure 4.12.2 Default edit page access
Chapter 4 HA029280
4.12.3 New program creation

The following example creates a new program with six segments whose parameters are predefined in the Pro-
gram Application editor. The segments used are called (short names): Heat, Soak, Cool and End:
Note: This is not intended to be a realistic program - the example is intended only to show the editing
technique. The user will be able to carry out this procedure only if segment classes have been created
and downloaded to the Visual supervisor.
1. Press the ‘NEW’ key near the bottom left-hand corner of the screen, and enter
Insert Segment
a suitable file name and program name, as shown in figure 4.12.2, above.
Segment Class: Heat
2. Press the ‘INSERT’ key. - the ‘Insert Segment’ dialogue box appears.
3. The default segment class that appears is the next segment class in the tem- Insert After: YES
plate, starting with the first - in this example, ‘Heat’. Press OK. OK CANCEL
4. The Heat segment pushbutton appears, together with its editable parameters
and a preview (figure 4.12.3a). The Segment duration is displayed here even
though it is not editable except by changing the ‘Chan1 Target’ value and the selected Ramp speed.
14:20:02 Program Edit 19/05/09

Segment number Total number of
segments (so far) Unit: pro3
Program: NEW - New
Segment Name: Heater on (1/1)
Segment Class: Heater on
Segment Duration: 00:13:47 e.g Editable fields
. have yellow
Chan1 Target: 103.0 Deg C backgrounds
Chan1 Holdback Type: Band
Ramp Speed: Quick
LOAD SAVE SAVE AS DELETE
Text colour = white for 0.0

0.0
120
current segment; other- Locked
wise text colour = black
Heat
NEW INSERT DELETE PROPERTIES VIEWS REVISION UNIT DETAIL
00:00:00 Heater on
Figure 4.12.3a First segment.

5 Operate ‘Insert’ again. The ‘Insert Segment’ pop-appears again, with the default next segment (Maintain)
(Figure 4.12.3b.
6. Continue to insert segments in the order ‘Cool’, ‘Heater on’, ‘Cool’, ‘End’. to end up with the display
shown in figure 4.12.3c.
7. The program can now be Saved (SAVE) and Run (LOAD/START) if required.
HA029280 Chapter 4
4.12.3 NEW PROGRAM CREATION (Cont.)

14:33:08 Program Edit 19/05/09
Unit: pro3
Program: NEW - New
Segment Name: Maintain (1/2)
Segment Class: Maintain
80.0
0.0 120
Locked
Heat Soak
00:00:32 Maintain
Figure 4.12.3b Adding a second segment
16:01:42 Program Edit 19/05/09
Unit: pro3
Program: NEW - New
Segment Name: End (6/6)
Segment Class: End
27.5
0.0 120
Unlocked
Heat Soak Cool Heat Cool End
00:27:30 End
Figure 4.12.3c After adding the final segment
Chapter 4 HA029280

New Program
FIXED FUNCTION KEYS File Name: NEW
NEW Allows the user to start creating a new program. Program Name: New
INSERT Allows the user to append or to insert a new segment. Click- OK CANCEL
ing on ‘Segment Class’ calls a picklist of segment classes from
which to choose, these classes having previously been defined
in the Programmer Application editor. By default, Insert always Insert Segment
Segment Class: Heat

produces the next segment class, in the order created in the
Insert After: YES
Programmer Application Editor.
OK CANCEL
Insert after = Yes, causes the new segment to be added after
the current segment. Insert after = No, causes the new seg-
ment to appear before the current segment.
DELETE Deletes the currently selected segment (without confirmation Properties
Program Name: prog2
being required). PV Start: Off
PROPERTIES Displays editable information about the Program Servo: SP
Hb & Alarm Value: 100.00 Deg C
VIEWS Allows the user to include or to hide ‘Preview’, ‘Programs’ and
‘Schedule’ views. These three views are located in the right- OK CANCEL
hand third of the screen, with ‘Programs’ at the top, ‘Preview’

in the middle and ‘Schedule’ at the bottom. If any one or more
of these views is not present, the other views share the space
equally.
See ‘Views’, below, for more details.
REVISION Gives update details showing when the program was last saved.
UNIT Allows the user to select a unit, if more than one is configured.
DETAIL Shows full details of the configuration of the current segment.
VIEWS
By default, the screen is split vertically between the edit area (2/3rds the width of the screen) and the sup-
plementary views area (the right-most third of the screen) which itself is split in half horizontally, with the
‘Programs’ pane at the top and the ‘Preview’ pane at the bottom.
The ‘Views’ key allows the user to change the appearance of the display, to allow any or none of the supple-
mentary views (Programs, preview and Schedule) to be included. If one or more of the views is enabled for
viewing, they share the height of the screen equally. If none of these views is enabled for viewing, the edit
area expands to fill the full width of the screen.
Editor Supplementary Views

Preview: YES
Programs: YES
Schedule: NO
OK
Figure 4.12.3d Views key pop-up menu
HA029280 Chapter 4

PROGRAMS
This appears in the upper right hand corner of the display screen, and allows the user to select a program for
editing, or to save a new or edited program and so on.
Unit: pro3
Program: RKN - Heat1
File Program
Name Name
Figure 4.12.3e Programs view
PREVIEW
This appears (by default) in the lower right hand corner of the display, but the illustration below shows it in
the vertical centre illustrating the case where all three supplementary views are enabled.
Preview shows a profile of the entire program, with the current segment against a white background - the non
current segments being shown against a grey background.
A cursor (a vertical dotted line), initially located at the beginning of the segment, can be dragged horizontally
to any position within the current segment, and the values of the traced parameters at the cursor position can
be read using the faceplates. Cursor time and the segment name normally appear below the ‘chart’, but the
figure below shows the case where the option key has been operated in order to display the ‘Plot’ and ‘Unit’
keys. Plot allows the trace colours to be selected. Unit allows a different Unit (if any) to be selected.
Visible Plot Select

Plot: Temperatu
Plot: Pressure
Plot: Door
Plot: None
Plot: None
Plot: None
Cursor
Plot: None
800 Plot: None
0 1290
Plot: None
20.0
0 100 Plot: None
Locked
Plot: None
Plot: None
Plot: None
Plot: None
Plot: None
Plot: None
OK CANCEL
Option key
Figure 4.12.3f Preview view
Chapter 4 HA029280

SCHEDULE
This allows the user to configure a selected program to run, starting at a defined date and time. If a program
is so scheduled a circular orange beacon appears in the top left corner of the program pane.
Unit: pro3 Program scheduled

File Name: ?????????????????????? beacon (flashing)

Start Time: 11:55:11 RunninG Sample
01:18:23 Segment 1
ACCEPT CANCEL 13:51:55
Figure 4.12.3g Schedule view
4.12.4 Program editing

Program editing uses the same processes as described above for new program creation, except that the user
selects an existing program for editing, instead of using the New Key. Once a program has been edited, it
must be Saved before the edits become active.
4.12.5 Small frame exceptions

The above description shows the large frame Supervisor. The small frame unit is similar, except that fewer
items can be shown on the screen simultaneously. For example, if there are more segments than can be fitted
across the width of the screen, scroll keys appear allowing access to ‘hidden’ segments.
When being used with CJK style languages, Multi-pane viewing (supplementary views) is not available for the
small frame unit.
4.12.6 Other notes

1. If the program is edited without using the application editor (e.g. by direct block edits) then the program
might not subsequently display correctly .
2. If the segment ID has been modified, it will not display correctly. If a segment or question or answer is
deleted, the program will no display correctly.
3. Once programs have been created using an Application Manager template, only the following edits may
be made to the template:
a. New classes may be added to the end of the list
b. New ‘Answers’ may be added to the end of the list
c. Limits may be changed
d. Preset lists may be edited
e. New items may be added to the User list.
4. When programs are being visualised from more than one node, both nodes must use the same template
file (i.e. not two copies of the file). Otherwise the program might not display correctly.
5. No changes may be made to a running program, unless it has first been put into Hold mode. When in
Hold mode, only Target Setpoints, User Values and Events may be changed, (if these items have been
configured to be user editable).
HA029280 Chapter 4
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 Bar code reader files
5.8 Database names 5.16 Database change audit trailing
5.1 INTRODUCTION
5.1 to 5.8, show how to replace the supplied screen-displayed texts with ones more suited to a particular proc-
ess, 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 and section 5.16 describes audit trailing of application values.
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 dic-
tionaries 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 completely 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 enumerations 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
following:
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 vari-
able <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.
Simplified Chinese characters are supported and this may allow up to five Chinese/Japanese/Korean (CJK)
languages to be supported in files _SYST<n>.uyl, where n is 10 to 14.
Note: The appearance of the instrument pages may be altered when operating in CJK languages
5.2.4 The dictionary

On delivery of the Visual Supervisor, the contents of the System text dictionary (abridged) are as set out be-
low.
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.)

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 se-
lected filter.
56 ALH ALH_TITLE 8 ACK
57 ALH PAGE_TITLE 20 Alarm summary
59 ALH ALH_FILTER 8 =MSGS
60 FB_MGR BUTTON TEXT 12 SUPPRESSION
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:
65 FB_MGR PAGE_TITLE 20 Alarm suppression times
Chapter 5 HA029280

66 ALMMENU LEGEND 11 LOG
67 ALH PAGE_TITLE 20 Event Log
68 ALMMENU LEGEND 11 EVT LOG
69 FB_MGR BUTTON TEXT 8 ALARMS
70 ALMMENU PAGE_TITLE 20 Suppressed Alarms
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
98 ALMMENU LEGEND 11 SUPPRESSED
100 ALMMENU ALM SUP ITEM 11 CLEAR DUE
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 *
115 ALMMENU ALM SUP ITEM 11 ––––– –––––
116 ALMMENU ALM SUP ITEM 17 –––––––– ––––––––
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
HA029280 Chapter 5

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:
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 ITEM_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.
Chapter 5 HA029280

223 COMMS DIALOG_TITLE 28 Hardware check
224 COMMS DIALOG_TEXT 80 IMPORTANT: Ensure comms cables are unplugged
before pressing ‘OK’ to continue.
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
279 CLOCK INTRO 64 Clock configured as SNTP client
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
HA029280 Chapter 5

309 INTERNAT LANGUAGE 16 Portuguese
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 en-
tered (Section 4.5.5). If a non-zero value is entered,
then the Access level will return to ‘Locked’ when-
ever 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
Chapter 5 HA029280

375 ACCESS ACCESS_LEVEL 10 ADMIN
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
elsewhere
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
940 FILEMGR BUTTON_TEXT 12 COPY
Chapter 5 HA029280

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:
1012 ACCESS ITEM_TITLE 18 Name:
HA029280 Chapter 5

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
documentation 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
1092 ALMMENU LEGEND 11 MESSAGES
Chapter 5 HA029280

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
1169 RECIPE ITEM 8 TRUE
HA029280 Chapter 5

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:
1226 BATCH ITEM_TITLE 16 Started At:
Chapter 5 HA029280

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:
1307 ACCESS MESSAGE 128 Reducing password expiry period may result in im-
mediate account expiry.
HA029280 Chapter 5

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
support desk who will issue you with the recovery
password
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
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:
Chapter 5 HA029280

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
electronic 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
1513 SIGN SIG_LEVEL 16 Signature
1514 SIGN SIG_LEVEL 16 Sign & Authorise
1515 SIGN SIG_LEVEL 16 Action Disabled
HA029280 Chapter 5

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
1600 COMMS LEGEND 8 MODBUS_
1601 COMMS LEGEND 8 /TCP
1602 COMMS PAGE TITLE 20 MODBUS_
Chapter 5 HA029280

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
1800 COMPAT LEGEND 11 COMPAT
1801 COMPAT PAGE TITLE 20 Compatibility
1802 COMPAT INTRO 64 Select new compatibility features and press
CHANGE
1803 COMPAT MESSAGE 128 Compatibility changes have been applied. Power
cycle to take effect
1804 COMPAT BUTTON TEXT 12 CHANGE
1805 COMPAT ITEM TITLE 16 Memory Model:
1806 COMPAT PROG MON STATE 12 Legacy programmer
1807 COMPAT PROG MON STATE 11 Large SFC
1808 COMPAT PROG MON STATE 16 Default
1809 COMPAT PROG MON STATE 12 Large Database
1900 PROG BUTTON TEXT 12 VIEWS
1902 PROG PAGE TITLE 20 Insert segment
1903 PROG ITEM TITLE 16 Insert after:
1904 PROG ITEM TITLE 16 Segment Class:
1905 PROG ITEM TITLE 16 Segment Details:
HA029280 Chapter 5

1906 PROG ITEM TITLE 16 Programs:
1940 TIMEZONE LEGEND 11 TIME ZONE
1941 TIMEZONE PAGE TITLE 20 Time Zone
1942 TIMEZONE ITEM TITLE 20 Name:
1943 TIMEZONE ITEM TITLE 20 Offset:
1944 TIMEZONE ITEM TITLE 20 Daylight saving:
1945 TIMEZONE ITEM TITLE 20 Starts at:
1946 TIMEZONE ITEM TITLE 20 and ends at:
1947 TIMEZONE ITEM TITLE 20 on the
1948 TIMEZONE ITEM TITLE 20
1949 TIMEZONE ITEM TITLE 20 of
1950 TIMEZONE ITEM 16 Sunday
1951 TIMEZONE ITEM 16 Monday
1952 TIMEZONE ITEM 16 Tuesday
1953 TIMEZONE ITEM 16 Wednesday
1954 TIMEZONE ITEM 16 Thursday
1955 TIMEZONE ITEM 16 Friday
1956 TIMEZONE ITEM 16 Saturday
1957 TIMEZONE ITEM 16 First
1958 TIMEZONE ITEM 16 Second
1959 TIMEZONE ITEM 16 Third
1960 TIMEZONE ITEM 16 Fourth
1961 TIMEZONE ITEM 16 Second last
1962 TIMEZONE ITEM 16 Last
1965 TIMEZONE ITEM TITLE 20 Time suffix format:
1966 TIMEZONE Special 3 GMT [Set to empty for ISO8601]
1967 TIMEZONE FORMAT CHAR 1 :
1968 TIMEZONE FORMAT CHAR 1 [Set to ‘Z’ for ISO8601]
1969 TIMEZONE Special 3 DST
1970 TIMEZONE ITEM 16 None
1971 TIMEZONE ITEM 16 Name
1972 TIMEZONE ITEM 16 Name+DST
1973 TIMEZONE ITEM 16 GMT offset
1978 TIMEZONE ITEM 16 +
1979 TIMEZONE ITEM 16 -
1980 COMMS LEGEND 11 TIME SYNC
1981 COMMS PAGE TITLE 20 Time Synchronisation
1982 COMMS PARA 24 Server operation
1983 COMMS ITEM TITLE 20 SNTP:
1988 COMMS PARA 24 Client operation
1989 COMMS ITEM TITLE 20 Server 1 IP:
1990 COMMS ITEM TITLE 20 Server 2 IP:
1992 COMMS ITEM TITLE 16 Method:
1993 COMMS ITEM 16 None/TOD
1994 COMMS ITEM 16 SNTP
2000 PROG LEGEND 11 PROGRAMMER
2001 PROG MENU TITLE 16 Programmer
2011 PROG LEGEND 11 PROGRAMS
2012 PROG LEGEND 11 SCHEDULE
2013 PROG LEGEND 11 EDIT
2014 PROG LEGEND 11 PREVIEW
2015 PROG LEGEND 11 MONITOR
2016 PROG LEGEND 11 ANALYSIS
Chapter 5 HA029280

2021 PROG PAGE TITLE 20 Program Load
2022 PROG PAGE TITLE 20 Program Schedule
2023 PROG PAGE TITLE 20 Program Edit
2024 PROG PAGE TITLE 20 Program Preview
2025 PROG PAGE TITLE 20 Program Monitor
2026 PROG PAGE TITLE 20 Program Analysis
2031 PROG BUTTON TEXT 12 START
2032 PROG BUTTON TEXT 12 RESTART
2033 PROG BUTTON TEXT 12 HOLD
2034 PROG BUTTON TEXT 12 ABORT
2035 PROG BUTTON TEXT 12 SKIP
2036 PROG BUTTON TEXT 12 ADVANCE
2037 PROG BUTTON TEXT 12 REDO
2038 PROG BUTTON TEXT 12 RESET
2039 PROG BUTTON TEXT 12 PLOT
2040 PROG BUTTON TEXT 12 LOAD
2041 PROG BUTTON TEXT 12 SAVE
2042 PROG BUTTON TEXT 12 SAVE AS
2044 PROG BUTTON TEXT 12 LAYOUT
2045 PROG BUTTON TEXT 12 PROPERTIES
2046 PROG BUTTON TEXT 12 DELETE
2047 PROG BUTTON TEXT 12 INSERT
2048 PROG BUTTON TEXT 12 UNIT
2049 PROG BUTTON TEXT 12 REVISION
2050 PROG BUTTON TEXT 12 DELETE
2051 PROG BUTTON TEXT 12 NEW
2052 PROG BUTTON TEXT 12 BATCH
2053 PROG BUTTON TEXT 12 ALARMS
2060 PROG ITEM TITLE 16 File Name:
2061 PROG ITEM TITLE 16 Program Name:
2062 PROG ITEM TITLE 16 Program:
2069 PROG MESSAGE 128 Program Information Unavailable
2070 PROG PAGE TITLE 20 Program Loading
2071 PROG PAGE TITLE 20 Program Saving
2072 PROG DIALOG TITLE 28 SAVE
2075 PROG DIALOG TEXT 80 Overwrite file?
2080 PROG DIALOG TITLE 28 Program Load Failed
2081 PROG DIALOG TITLE 28 Program Save Failed
2082 PROG PROG LOAD FAIL 24 Bad file format
2083 PROG PROG LOAD FAIL 24 Too big
2084 PROG PROG LOAD FAIL 24 Illegal go back sequence
2085 PROG PROG LOAD FAIL 24 Invalid algorithm block
2086 PROG PROG LOAD FAIL 24 Invalid template file
2087 PROG PROG LOAD FAIL 24 File not found
2088 PROG PROG LOAD FAIL 24 File is read only
2089 PROG PROG LOAD FAIL 24 Other file error
2090 PROG PROG LOAD FAIL 24 Error9
2091 PROG DIALOG TITLE 28 UNSAVED EDITS
2092 PROG DIALOG TEXT 80 This operation will result in the loss of edits which
have not yet been saved
2093 PROG DIALOG TITLE 28 Program Delete Failed
2094 PROG DIALOG TITLE 28 PROGRAM SCHEDULED
HA029280 Chapter 5

2095 PROG DIALOG TEXT 80 A program is scheduled, continue with load?
2100 PROG ITEM TITLE 16 Segment Type:
2101 PROG ITEM 16 STEP
2102 PROG ITEM 16 DWELL
2103 PROG ITEM 16 RAMPTIME
2104 PROG ITEM 16 RAMPRATE
2105 PROG ITEM 16 END
2107 PROG ITEM 16 Live edit
2108 PROG ITEM 16 NO WAIT
2109 PROG ITEM 16 NO EXIT
2110 PROG ITEM TITLE 16 Hb & Alarm Mode:
2111 PROG ITEM 16 NONE
2112 PROG ITEM 16 Per Channel
2113 PROG ITEM 16 Per Segment
2115 PROG ITEM TITLE 16 Hb & Alarm Value:
2116 PROG ITEM TITLE 16 Alarm Delay:
2117 PROG ITEM TITLE 16 Holdback Type:
2118 PROG ITEM TITLE 16 Deviation Alarms:
2119 PROG ITEM TITLE 16 OOB Alarm:
2120 PROG ITEM 16 None
2121 PROG ITEM 16 low
2122 PROG ITEM 16 High
2123 PROG ITEM 16 Band
2124 PROG ITEM TITLE 16 Target:
2125 PROG ITEM TITLE 16 Rate:
2126 PROG ITEM TITLE 16 Value:
2127 PROG ITEM TITLE 16 Low Limit:
2128 PROG ITEM TITLE 16 High Limit:
2129 PROG ITEM TITLE 16 End condition:
2130 PROG ITEM 16 Reset
2131 PROG ITEM 16 Dwell
2132 PROG ITEM TITLE 16 Event Name:
2133 PROG ITEM TITLE 16 Exit name:
2134 PROG ITEM TITLE 16 Wait Name:
2135 PROG ITEM TITLE 16 Segment name:
2136 PROG ITEM TITLE 16 Segment Start:
2137 PROG ITEM TITLE 16 Segment duration:
2138 PROG ITEM TITLE 16 Segment Finish:
2140 PROG ITEM 16 Events
2141 PROG ITEM 16 Exit
2142 PROG ITEM 16 Wait
2143 PROG ITEM TITLE 16 Go Back To:
2144 PROG ITEM TITLE 16 Go Back Cycles:
2145 PROG ITEM 16 <Nowhere>
2146 PROG ITEM TITLE 16 Servo:
2148 PROG ITEM TITLE 16 SP
2149 PROG ITEM 16 PV
2150 PROG ITEM TITLE 16 Rate Units:
2151 PROG ITEM 16 Seconds
2152 PROG ITEM 16 Minutes
2153 PROG ITEM 16 Hours
2154 PROG ITEM 16 Days
2155 PROG ITEM 16 /sec
Chapter 5 HA029280

2156 PROG ITEM 16 /min
2157 PROG ITEM 16 /hour
2158 PROG ITEM 16 /day
2159 PROG PARA 24 Holdback and Alarms
2160 PROG PAGE TITLE 20 Revision Information
2161 PROG ITEM TITLE 16 Version:
2162 PROG ITEM TITLE 16 Edited At:
2165 PROG ITEM TITLE 16 PV Start:
2166 PROG ITEM 16 Off
2167 PROG ITEM 16 Rising
2168 PROG ITEM 16 Falling
2170 PROG PAGE TITLE 20 Unit Selection
2171 PROG ITEM TITLE 16 Unit:
2175 PROG PAGE TITLE 20 Program Load
2176 PROG PAGE TITLE 20 Program Save
2177 PROG PAGE TITLE 20 Program Delete
2180 PROG PAGE TITLE 20 Properties
2181 PROG ITEM TITLE 16 Rate Units:
2184 PROG ITEM TITLE 16 Algorithm File:
2185 PROG ITEM 16 (Continuous)
2190 PROG PAGE TITLE 20 Editor Layout
2191 PROG ITEM TITLE 16 Long SP names:
2192 PROG ITEM TITLE 16 Segment start:
2193 PROG ITEM TITLE 16 Segment duration:
2194 PROG ITEM TITLE 16 Segment finish:
2195 PROG ITEM TITLE 16 Wide cells:
2196 PROG ITEM TITLE 16 Transpose:
2197 PROG ITEM TITLE 16 Compressed Events:
2200 PROG FORMAT CHAR 1 0 (Comment: Event false)
2201 PROG FORMAT CHAR 1 1 (Comment: Event True)
2202 PROG FORMAT CHAR 1 - (Comment: Wait/Exit condition = None)
2203 PROG FORMAT CHAR 1 0 (Comment:Wait/Exit condition = Open)
2204 PROG FORMAT CHAR 1 1 (Comment: Wait/Exit condition = Closed)
2210 PROG PAGE TITLE 20 Editor Supplementary Views
2211 PROG ITEM TITLE 16 Preview:
2212 PROG ITEM TITLE 16 Monitor:
2213 PROG ITEM TITLE 16 Schedule:
2220 PROG PAGE TITLE 20 Segment Details
2221 PROG PAGE TITLE 20 Events Details
2222 PROG PAGE TITLE 20 Wait Condition Details
2223 PROG PAGE TITLE 20 Exit Condition Details
2224 PROG MESSAGE 128 Exit conditions are ignored in ramping segments
2240 PROG ITEM TITLE 16 Start Date:
2241 PROG ITEM TITLE 16 Start Time:
2242 PROG ITEM TITLE 16 File Name:
2248 PROG BUTTON TEXT 12 ACCEPT
2249 PROG BUTTON TEXT 12 CANCEL
2250 PROG ITEM TITLE 16 State:
2251 PROG ITEM TITLE 16 Segment Name:
2253 PROG ITEM TITLE 16 Seg Time Remaining:
2254 PROG ITEM TITLE 16 Prog Time Remaining:
2255 PROG ITEM TITLE 16 Cycle No:
2260 PROG PROG MON STATE 12 UNLOADED
HA029280 Chapter 5

2261 PROG PROG MON STATE 12 LOADING
2262 PROG PROG MON STATE 12 IDLE
2263 PROG PROG MON STATE 12 STARTING
2264 PROG PROG MON STATE 12 RUNNING
2265 PROG PROG MON STATE 12 COMPLETE
2266 PROG PROG MON STATE 12 HOLDING
2267 PROG PROG MON STATE 12 HELD
2268 PROG PROG MON STATE 12 RESTARTING
2269 PROG PROG MON STATE 12 ABORTING
2270 PROG PROG MON STATE 12 ABORTED
2271 PROG PROG MON STATE 12 RESETTING
2272 PROG PROG MON STATE 12 INHIBIT
2273 PROG MESSAGE 128 Maximum Program Time Exceeded
2274 PROB BUTTON TEXT 12 VIEWS
2275 PROG PAGE TITLE 20 Monitor Supplementary Views
2276 PROG ITEM TITLE 16 Segment:
2277 PROG ITEM TITLE 16 Programs:
2278 PROG ITEM TITLE 16 Schedule:
2279 PROG MESSAGE 128 PROGRAM NOT RUNNING
2286 PROG PAGE TITLE 20 Jog Disabled
2287 PROG MESSAGE 128 Jog operation not available
2290 PROG ITEM TITLE 16 Plot:
2291 PROG ITEM 16 None
2292 PROG PAGE TITLE 20 Visible Plot Select
2295 PROG MESSAGE 128 Missing program template file (.UYW).
2297 PROG MESSAGE 128 Caution: This node’s clock is not synchronised.
2298 PROG MESSAGE 128 Invalid program configuration.
2299 PROG MESSAGE 128 Unable to view program due to communication
error.
2320 COMMS BUTTON TEXT 12 PRINTERS
2321 COMMS TITLE 16 Printer1 Setup
2324 COMMS PAGE TITLE 20 Printers
2325 COMMS TITLE 16 Protocol:
2326 COMMS TITLE 16 Palette:
2327 COMMS TITLE 16 Page Format:
2328 COMMS TITLE 16 Host:
2329 COMMS TITLE 16 Port:
2330 COMMS TITLE 16 Print Columns:
2331 COMMS ITEM 16 Text Only
2332 COMMS ITEM 16 Graphics-PCL3
2333 COMMS ITEM 16 Graphics-ESC/P
2337 COMMS ITEM 16 Monochrome
2338 COMMS ITEM 16 Colour CMY
2339 COMMS ITEM 16 Colour CMYK
2340 COMMS ITEM 16 Colour KCMY
2343 COMMS ITEM 16 A4
2344 COMMS ITEM 16 Letter
2345 COMMS TITLE 16 Line Feed Space:
2346 COMMS BUTTON TEXT 12 Plot (P1)
2347 COMMS BUTTON TEXT 12 Plot (P2)
2353 COMMS TITLE 16 Plot Colour Select
Chapter 5 HA029280

2354 COMMS ITEM 16 Black
2355 COMMS ITEM 16 Cyan
2356 COMMS ITEM 16 Magenta
2357 COMMS ITEM 16 Blue
2358 COMMS ITEM 16 Yellow
2359 COMMS ITEM 16 Green
2360 COMMS ITEM 16 Red
2361 COMMS ITEM 16 Grey
2371 COMMS TITLE 16 Channel
2372 COMMS MESSAGE 128 NO DATA AVAILABLE
2373 COMMS TITLE 16 Extended Text:
2391 COMMS COMMS PORT 5 USB1
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
HA029280 Chapter 5
5.2.5 PANEL CUSTOMISATION (Cont.)

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
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
2031 PROG START Start a program
2032 PROG RESTART Restart a program
2033 PROG HOLD Hold a program
Chapter 5 HA029280
5.2.5 PANEL CUSTOMISATION USING THE DICTIONARY (Cont.)

2034 PROG ABORT Abort a program
2035 PROG SKIP Skip a segment
2036 PROG ADVANCE Advance to end of segment
2037 PROG REDO Re-do a dwell segment
2038 PROG RESET Reset a program
2039 PROG PLOT Display plot selection
2040 PROG LOAD Load a program
2041 PROG SAVE Save a program
2042 PROG SAVEAS Save a program under a new name
2043 PROG VIEWS Display editor view selection
2044 PROG LAYOUT Display editor layout selection
2046 PROG DELETE Delete a segment
2047 PROG INSERT Insert a segment
2048 PROG UNIT Display programmer unit selection
2049 PROG REVISION Display program revision information
2050 PROG DELETE Delete a program
2051 PROG NEW Creat a new program
2052 PROG BATCH Display batch information
2053 PROG ALARMS Display alarm information
2248 PROG ACCEPT Accept a program schedule
2249 PROG CANCEL Cancel a program schedule
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
2063 PROG Program file name filter to restrict the pick list of programs
2064 PROG Program name filter to restrict the pick list of programs
2280 PROG Jog back 1 minute
2281 PROG Jog forward 1 minute
2282 PROG Jog back 10 minutes
2283 PROG Jog forward 10 minutes
2284 PROG Jog back 60 minutes
2285 PROG Jog forward 60 minutes
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 particu-
lar industry 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 syn-
tax:
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 pos-
sible 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.)
No EVENT NAME MAX LENGTH MAX LENGTH

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
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
No EVENT NAME MAX LENGTH MAX LENGTH

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
V121 Start 8 characters 16 characters
V122 Hold 8 characters 16 characters
V124 Reset 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
V200 Delete 8 characters 16 characters
V203 Start 8 characters 16 characters
V204 Hold 8 characters 16 characters
V206 Skip 8 characters 16 characters
V207 Redo 8 characters 16 characters
V208 Advance 8 characters 16 characters
V210 Reset 8 characters 16 characters
V211 Jog 8 characters 16 characters
V212 Schedule 8 characters 16 characters
V213 Cancel 8 characters 16 characters
V214 New 8 characters 16 characters
V217 Program Edit 16 characters 16 characters
V218 Load schedule 8 characters 16 characters
V219 Late schedule 8 characters 16 characters
V220 Load fail 8 characters 16 characters
V222 Idle 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 2000 records, each consisting of up to 128 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
parameters 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 applica-
tion.
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
instrument 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 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,2090,2070
A2030,STARTUP,,3
A2040,COMMS,,4
A2050,CLOCK,3
A2060,INTERNAT,,4
A2070,PANEL,,2
A2090,TIMEZONE,,4
MAINTENANCE submenu
A2400,MENU,4,,3,#S930,#S931,2080,2140,2150,2160,2170
A2080,CLONE,4
A2140,FILE_MGR,4
A2150,SOFT_OPT,4
A2160,BATCH_MAINT_4
A2170,COMPAT,4
Alarm history (for event log only)

A9010,ALM_HIST,2,,2
A4000,ACCESS
Dialogue Agent
A100000,DIALOG,,,4
==== END OF FILE ====
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,6000,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,2090,2070
A2030,STARTUP,,3
A2040,COMMS,,4
A2050,CLOCK,3
A2060,INTERNAT,,4
A2070,PANEL,,2
A2090,TIMEZONE,,4
(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
Programmer
A6000,PROG_MENU,2,3,3,6010
A6010,PROG,2,3,2,6000,8020,9030
A8020,BATCH,2,3,3,0,1
A9030,ALM_HIST,2,,3
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 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,2090,2070
A2030,STARTUP,,3
A2040,COMMS,,4
A2050,CLOCK,3
A2060,INTERNAT,,4
A2070,PANEL,,2
A2090,TIMEZONE,,4
MAINTENANCE submenu
A2400,MENU,4,,3,#S930,#S931,2080,2140,2150,2160,2170
A2080,CLONE,4
A2140,FILE_MGR,4
A2150,SOFT_OPT,4
A2160,BATCH_MAINT,4
A2170,COMPAT,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 OPTION VERSIONS (Cont.)

====================================
====================================
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
I100
Root Menu
R1000
A1000,MENU,,,3,,,4000,2000,9000,1500,6000,7000,8000,5000,1
System Submenu
A2000,MENU,,,3,#S130,#S131,2010,2200,2300,2080,2500
A2010,SYS_SUM
A2080,CLONE,4
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,2090,2070
A2030,STARTUP,,3
A2040,COMMS,,4
A2050,CLOCK,3
A2060,INTERNAT,,4
A2070,PANEL,,2
A2090,TIMEZONE,,4
(Continued)
Chapter 5 HA029280
AUDITOR OPTION VERSIONS (Cont.)

Admin
A2500,MENU,5,,3,#S1400,#S1401,2510,2520
A2510,NET_AUDIT,5
A2520,SIGN_CFG,5
Security Access
A4000,ACCESS
Logging Submenu
A5000,LOG_MENU,2,3,5010
A5010,LOG,2,3,2
A1500,AGP,1,2,2
Programmer
A6000,PROG_MENU,2,3,3,6010
A6010,PROG,2,3,2,6000,8020,9030
A8020,BATCH,2,3,3,0,1
A9030,ALM_HIST,2,,3
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 possi-
ble, 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
characters 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
example) 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.
HA029280 Chapter 5
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 5.7.4b 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
available. ‘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
COMPAT 1 A Compatibility selection
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
PROG 7 B Programmer
PROG_MENU 1 B Programmer menu
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 Legacy Setpoint Programmer
SPP_MENU 1 B Legacy Setpoint Programmer Menu
STARTUP 1 Startup strategy definition
SYS_SUM 1 System summary
TIMEZONE 1 Time zone configuration
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.
PROG 0 Programs
1 Schedule
2 Edit
3 Preview
4 Monitor
5 Spreadsheet editor*
6 Application editor*
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)
*It is recommended that value ‘2’ be used to obtain the correct editor: a value of 5 may be used to call a
spreadsheet editor when an application editor has been configured; ‘6’ is for factory use only.
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. Database Names aliasing files (.uyn) also support references to dictionary file entries. Refer to section
5.1 for further information on dictionary files.
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 (or dictionary ID/entry) 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 (or dictionary ID/entry) 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)
‘Battery’.
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 logging 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.1a. 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.1a Sample .UYF file
If the Printer/reader option is fitted, graphical trends can be printed to a suitable printer (as described in sec-
tion 12 of this manual). The additional commands are shown in figure 5.9.1b, below.
Note: The page feed command “SP” works with many printers, for others “S1B&l0H” may be necessary
instead, where the character after the ampersand (&) is a lower case ‘l’, not the number ‘1’.
Figure 5.9.1b Sample .UYF file including trace print commands
*I3
"Temperature : ",[pid1.pv]:6.3,"$NPressure :"
[pid2.pv]:6.2,"$N"
Sheet feed command
[pid1.pv]>=30.0<=90.0{Cold,OK,Hot},"$N",_TIME:8,"$,",_DATE:8,"$N"
(Printer dependent)
“$P”
[HD_TREND]:400:200T
Bounding
rectangle size
Name of HISTDATA block
from which trend data is to
be retrieved
Figure 5.9.1b Sample .UYF file with Trend printing commands
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 vari-
ables) 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 for-
matting 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 differ-
ent 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 ‘tem-
perature =’ 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 Note: See Appendix C
${ open curly bracket 7B
for ASCII Unicode Latin-1
character set codes
$} Close curly bracket 7D
$nn aSCii character nn nn
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 fol-
lows:
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 brackets 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.SelMode.Track]{,TrackOn} would cause ‘TrackOn’ to be
printed when [Pid7.SelMode.Track] becomes ‘True’, but nothing would be printed when
the value becomes ‘False’.
This same syntax can be used to apply enumerations to integers, booleans, subfields and
enumerations.
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 variables, 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 vari-
able 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 asterisks. 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
different 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
necessary.
.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, respec-
tively.
*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 con-
sists 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/08,01:37:08,Fred Bloggs,09/04/08,23:37:08
Where
‘2’ is the revision level of the file
‘10/04/08’ is the day/month/year that revision was carried out (local time).
‘01:37:08’ is the hours:minutes:seconds that the revision was carried out (local time).
‘Fred Bloggs’ is the name of the person who last modified the file.
‘09/04/08’ is the day/month/year that revision was carried out (UTC *).
‘23:37:08’ is the hours:minutes:seconds that the revision was carried out (UTC *).
Line 3
Line three defines the recipe set block to be used and recipe download timeout value, in seconds (max. 60).
<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.
*Note: This UTC (GMT) time and date is accurate only if the instrument’s clock (section 4.5.3) and time
zone (section 4.5.5) are set correctly
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 consid-
ered 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,07/11/08,08:45:54,Richard,07/11/08,09:45:54
,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,07/11/08,08:56:13,Richard,07/11/08,09:56:13
,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,07/11/08,09:13:07,Richard,07/11/08,10:13:07
,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 column 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,07/11/08,09:18:09,Richard,07/11/08,10:18:09
,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 dif-
ferent 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 699 Names of variable numbers 1 to 299 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 5001-5999, Batch number 5
Also the section 1-999 represents the batch currently on view and is thus a duplicate of one of the other sec-
tions.
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 699 Names of recipe variable numbers 1 to 299
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/08,01:51:16,Fred Bloggs,09/04/08,23:51:16
Where: ‘2’ is the revision level of the file
‘10/04/08’ is the day/month/year that the revision was carried out (local time)
’01:51:16’ is the hours:minutes:seconds that revision was carried out (local time)
‘Fred Bloggs’ is the name of the person who last modified the file.
09/04/08 is the day/month/year that the revision was carried out (UTC*)
’23:51:16’ is the hours:minutes:seconds that revision was carried out (UTC*)
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 (maximum 3600 seconds).
‘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 exam-
ple, 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.)
*Note: This UTC (GMT) time and date is accurate only if the instrument’s clock (section 4.5.3) and time
zone (section 4.5.5) are set correctly
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 associ-
ated 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 corresponding .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 BAR CODE READER FILES

An application containing a READER block will reference a reader file (.UYD) file. These files allow for the
matching of bar codes and performing the corresponding actions required by those bar codes.
EXAMPLE
@r,”h”,%{GOTO:1}
@r,”a”,_ALM_LVL,%{ACK_ALL,GOTO:9010}
@r,”temp”,[PID1.SL]:4W2,”deg”,””
@r,”$09”,[Prog.RqNxtPrg]:8W,%{ST:”[Prog.NxtRdy]:=TRUE;”}
Notes:
1 The first line will match if the input is “h” (plus any trailing characters). It will cause the panel to
jump to the home page (user page with Id 1).
2 The second line will match if the input is “a” (plus any trailing characters) and there are some active
or unacknowledged alarms. It will cause acknowledgement of all alarms and jump to the Alarm His-
tory page (access level permitting, or overridden).
3 The third line will accept input such as “temp98.4deg” (no trailing characters permitted) and will
assign the value 98.4 to PID1.SL, provided the current access level is 2 or higher and not overridden.
4 The fourth line will accept a TAB character followed by e.g. “MyProg99”, and will load and run the
program via the ProgCtrl function block “Prog”.
5.15.1 Overview
A .UYD file contains an ordered set of potential patterns to be matched. When a bar code is read each of
these is checked in turn (in the order they appear in the file) until a match is found (i.e. if there is the poten-
tial to match more than one line in the file the first one will be matched).
Each test line (or pattern) comprises a number of items. These items must be separated by commas.
Rules
1. No line is to include more than 255 characters
2. No spaces or tabs may be included between items
PATTERN DELIMITER
Each line must commence “@r”
HA029280 Chapter 5
5.15.2 Literal text

A text item simply causes that piece of text to be matched with the input. The match fails unless every charac-
ter in the string appears in the input at the correct position. Certain characters may have been deemed to be
‘wildcards’, in which case they will match any character in the input, but this is specified elsewhere (e.g. in the
READER function block).
Constant literal text is represented by a string in double quotes, optionally followed by size and format specifi-
cations; the details of these are defined later, but the general syntax is:
<double-quoted string> [ ‘:’ <size info> <format> ]
Examples:
“PV = “
“ABC123“:8C (Uses 8 character positions and centre-justifies)
Where a width wider than the specified text is given, as in the second example, padding uses the ‘space’
character (which may or may not be a wildcard - see above). Non-printable ASCII characters are defined using
IEEE1131 ‘ST’ format; in particular, the following are supported:
Representation Character generated
$L or $N Linefeed or newline (hex 0A)
$P Form feed (hex 0C)
$R Carriage return (hex 0D)
$T Horizontal tab (hex 09)
$$ Dollar character: ‘$’ (hex 24)
$” or “” Double quotes character (hex 22)
$nn Arbitrary ASCII character in hex, e.g. $7F is ‘DEL’.
If any other character follows ‘$’, then the ‘$’ is ignored.
Example: “Cost $”5$$$”” would match Cost “5$”
EMPTY STRINGS
The empty literal string (“”). This matches the end of the input and therefore may be used to reject input that
includes trailing characters.
Note: Any suffix/terminating characters specified in the READER block do not count as part of the
input, for these purposes.
Example: @r,”temp”,[PID1.SL]:4W2,”deg”,”” will not allow trailing temperature characters.
Chapter 5 HA029280
5.15.3 Dictionary text

References to text in dictionaries are made using the format:
# <dictionary type id.> <entry number>
For example #U12 will match item 12 in the user dictionary.

Note: The “W” dictionary is writeable and may be written in a similar manner to LIN database variable.
E.G. #W10:8 will write 8 characters into the dictionary entry 10
Each dictionary also has the “special” entry number “*” which is the “current” indexed value. This is used in
conjunction with the user actions to modify the entry number written to.
5.15.4 LIN database variables

Variables may be used in three different ways.
1. A variable not specified to be writeable, and with a non-zero width, is formatted using the current value
of the variable and then matched against the input in exactly the same way as for constant strings (includ-
ing the possible use of wildcards).
2. A variable specified to be writeable (‘W’ attribute, defined later) will be matched, but only in the limited
sense that the required number of characters are present in the input, as specified by the width. If the
whole pattern matches then the variable will be assigned a value, just as if the characters had been en-
tered via a touch keypad. No assignment will be carried out if the characters are invalid, e.g. letters for a
decimal integer variable. Enumerations (defined later) are not currently supported in this context.
3. A variable specified to have zero width will be deemed to have matched if it is a boolean type and true, or
if it is a numeric type (integer, real, enum, subfield16, etc.) and is greater than zero, or if it is a string type
and is a non-empty string.
The syntax of variables is:
<name> [<enumerations>] [‘:’ <time flags>] [‘:’ <size info> <format>]
Enumerations, time flags, size and format information are defined later.
For most data types the nature of the printed text is obvious. For booleans, the digits 0 and 1 are used by
default, but typically an enumeration would be supplied to override this.
Variable names refer to objects in a database. Different databases may be available, and the one required is
specified by the structure of the name. The name is of the form
<FB instance>.<field> [.<subfield>], with the whole string enclosed in square brackets (this is mandatory), e.g.
[pid1.sp] or [pid2.SelMode.SelAuto].
HA029280 Chapter 5
5.15.4 LIN DATABASE VARIABLES (Cont.)
SYSTEM VARIABLES
The following system variables, identified by a leading underscore, are available :
_ACC_I Current access level (integer)
_ACC_S Current access level (string)
_ALM_ACT Number of active alarms (integer)
_ALM_NAK Number of unacknowledged alarms (integer)
_ALM_LVL Overall alarm level, bit encoded:
1 = Active, 2 = Unacknowledged
_ALM_URG Most urgent unacknowledged alarm (string)
_APP_NAME Name of currently loaded application, if any (string)
_DATE Current date, in appropriately internationalised format (string)
_TIME Current time (string)
_TITLE Title of currently active page in GUI main pane (string)
_USER_ID ID of currently logged on user (string)
_USER_NAME Name of currently logged on user (string)
_USER_REF Reference number of the user currently logged on (integer)
ENUMERATIONS
These apply to boolean, integer, and enumerated variables. They may be used for matching, but cannot (cur-
rently) be used in connection with data input.
Enumerations take the form of a comma-separated list of literal strings to be displayed, between curly braces,
immediately following the variable name.
Examples:
[door.In.Bit3]{closed,open}
[counter2.op]{Zero,One,Two,Three,Four}
[i.op]{Lo,Lo,Lo,,,,,,Hi,Hi,Hi}
For booleans the enumerations always refer to FALSE and TRUE respectively, whereas for integers they corre-
spond to values 0, 1, 2, etc. As with literal text, ST format may be used for non-ASCII characters; this will also
be necessary to obtain the characters ‘}’ (using “$}” or “$7D”) and ‘,’ (using “$,” or “$2C”) as well as ‘$’ itself
(using “$$” or “$24”).
In the case of ‘enum’ type variables, an explicit list may be given, as above; if omitted, then the value will still
be displayed as an enumeration, but using strings extracted from the database.
Where the enumeration text is not literal, but is to be obtained from a dictionary, the bracketed list is pre-
ceded with the dictionary character, “#”.
For example: door.In.Bit3#{U22,U23}
Chapter 5 HA029280
5.15.5 Number of characters

A width may be given for text and variables. For example,
[i.Count]:6
would allocate 6 characters to this variable.
If the width is omitted for variables, it will default to zero unless an enumeration has been specified, in which
case the width will default to that of the longest enumeration string.
5.15.6 Number of decimal places

For REAL variables, the width may be qualified by the number of decimal places, e.g.
[Loop1.PV]:7.3
This will condition the way the variable is formatted for matching, but in the case of a writeable variables the
input is not constrained to have the decimal point in the correct place.
5.15.7 Formatting attributes

These are specified for each individual pattern item, modifying the way it is formatted. Some are applicable
only to variables, others to constant text too. Some are specific to the data type. Those which apply generally
are:
C Centre justify
L Left justify
R Right justify
Centre justification normally tends to the left when the item width and the spaces available are neither both
even nor both odd. Adding ‘R’ to ‘C’ changes this to a tendency to the right.
Attributes which apply to any variable are:

Z Use the character ‘0’ instead of ‘ ’ for left padding
The following apply to REAL variables only:
S Scientific notation, e.g. 1.23E7
Note that this will condition the way the variable is formatted for matching, but in the case of a write-
able variable the input is not constrained; the ‘E’ (or ‘e’) format will always be acceptable as input
regardless of whether ‘S’ was specified.
The following may be applied to integer, boolean, subfield and ENUM variables only:
X Hex format, using upper case A-F
x Hex format, using lower case a-f
Y Binary format
If a hex integer is writeable, then either upper or lower case a-f will be accepted as input, regardless of
whether ‘x’ or ‘X’ was specified.
Note: Binary format is not currently available for writeable variables.
HA029280 Chapter 5
5.15.8 User actions

A pattern match may also cause the execution of a number of user actions. An action list may be included as:
%{<action>} for a single action
%{<action1>,<action2>} for 2 or more actions
The list of possible actions are shown in table 5.15.8, below.
Description Syntax Example
acknowledge all
alarms ACK_ALL
Go to a specified
display page GOTO:<Page> GOTO:9010
Descend to a speci-
fied display (i.e. Go DESC:<Page> DESC:9010
Back works)
General St ST:"<ST>" ST:"[PID1.SL]:=40.0;"
Set index into a dic-

tionary DICT_SET:"<dict>":<entry> DICT_SET:"W":1
increment or decre-
ment a dictionary DICT_ADD:"<dict>:<increment>:<limit> DICT_ADD:"W":1:14
index
Table 5.15.8 Action list
EXAMPLE
The following examples show how the input string “RESET” will reset the writeable dictionary index to 11.
Then each successive item beginning “ITEM:” will write its next 8 characters into the writeable dictionary and
increment the index. In this way a list of strings are scanned into dictionary entries 11 to 14.
@r,”RESET”,%{DICT_SET:”W”:11}
@r,”ITEM:”,#W*:8W,%{DICT_ADD:”W”:1:14}
This construct may particularly useful in scanning a list of text items into the “W” dictionary, which may then
be used as input to a report.
Chapter 5 HA029280
5.16 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 interaction. 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.
Note: Only the first eight characters of a string are monitored for changes.
5.16.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 oc-
curs audit trailing will stop to prevent over-filling the log until the value stabilises gain.
Default = 10
5.16.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 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 operations 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 ‘Pro-
vider’) to up to three E suite systems (the ‘Consumers’). Network Audit Trail is accessed from the Administra-
tion menu by operation 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 characters.
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
transmitted, and (if required) disabling one or more alarm or event types, so that only those items of interest
are transmitted.
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 seconds, 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 expired, 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 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
10:17:20 Security access 10/04/06
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 SECURITY ACCESS PAGE (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 termi-
nated. Retired 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 password is correct, the User is ‘re-enabled’, and is shown in the normal blue colour on the
screen. The expiry date remains as first set up for the user.
Notes:
1. If a user fails to log in within the number of times specified (see Max login attempts in ‘PROPER-
TIES’ below), then the user is ‘disqualified’. The effects are similar to being ‘Disabled’, but the ‘DIS-
ABLE’ key in the pop-up is replaced by a ‘REINSTATE’ key allowing the user’s login to be re-enabled.
2. In the situation where there is a Visual Supervisor security master and one or more associated Visual
Supervisor security slaves:
a. the identity pop-up (figure 6.1.3b, above) appears only at the master so it is not possible to rein-
state a user from a slave.
b. If a user is disabled on a slave unit, then this user can be reinstated only using Security Manager
software - reinstatement cannot be achieved just by redeploying the master unit security.
c. If a user is disabled on a particular slave unit, deploying the master unit security does not dis-
qualify the user at the master or at any other slave. In order to disqualify a user at the master,
the login should be attempted using an incorrect password more times than the ‘Max login at-
tempts’ setting for that login (see ‘PROPERTIES’ below). Once disqualified at the master, the user
cannot log in at the master or at any of the slaves.
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
Chapter 6 HA029280

ATTRIBUTES
Touching a particular user’s Attributes ‘cell’, calls the Attributes page. This is used to de- richard:Attributes
Identity: richard
fine the users ability to ‘sign’ and ‘authorise’ changes, and to define whether the user can Sign: YES
modify the instruments operation. Authorise:
View Only:
YES
NO
Admin Only: NO
The numbers which appear in the attributes column can be decoded as shown in table FTP:
Remote:
NO
NO
6.1.3. The values are additive, so if, for example, ‘Sign’ and ‘Authorise’ are both selected oK CanCEL
‘Yes’, and 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
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 Pass-
word 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
described in section 4.4.3, above.
NEW
Operating the NEW key calls the New User pop-up menu to the
New User
display. Once the details have been entered, and ‘OK’ pressed, the
Identity:
new user appears in Green, on the screen.
Name:
Note: Do not press SAVE until all other parameters (e.g. at- Access: OPERATOR
tributes) have been configured for this user,. Once SAVED, Password: ********
only the password can be changed.
Confirm: ********
Configure the users Attributes, as described above, then press SAVE.
The user Identity and Name change to Blue, and the Password oK CanCEL
expiry date appears as next day. If the user Password is to expire at
any period other than that set in the PROPERTIES menu (described Figure 6.1.3d New User screen
below), this should now be set.
ADMIN should now be logged out of, and the new user logged in and a new password entered.
HA029280 Chapter 6
6.1.3 USER ID CONTROL SECURITY ACCESS PAGE (Cont.) Account Properties

PROPERTIES Min User Id Length: 6
Min Password Length: 6
Max Login Attempts: 3
Similar to the Properties page described in section 4.4.3, this page, Password Expiry: 90 days
depicted with default values in figure 6.1.3e, allows the login param- User Timeout: 60 minutes
eters to be set, as described 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
previous screen activity.
MAINTENANCE
Account Maintenance
Operating the ‘MAINT’ key at the bottom of the Security Access screen
calls the ‘Account Maintenance’ screen to the display, as depicted in Recovery Account: YES
figure 6.1.3f, below. Master Access: YES
Recovery Account If recovery account is set to YES, this enables Edit Own Expired Password: YES
a recovery in the event of all ADMIN accounts
becoming unusable. This requires a maintenance oK CanCEL
contract with the manufacturer.
Master Access Setting Master Access to ‘NO’, means that the
Figure 6.1.3f Maintenance screen
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
‘Statistics’ screen, as depicted in figure 6.1.3g, below. Users: 5/100
This window shows: Retired Users: 1/200
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 oK
configured.
2. How many users have been retired. For example, 1/200 means that 1 user Figure 6.1.3g STATS window
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 configuration 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
remaining 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. Fig-
ure 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 Signa-
ture 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
administrators 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
performed.
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 request-
ed 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 ‘Func-
tion’ 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
instrument for FTP logon, the user-based access system (section 4.4.3) must be used, and the relevant user’s
attributes configured 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
permission (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
recommended
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 8: THE CONTROL CONFIGURATOR

Note: If IPRP is enabled, the control configurator cannot be used to view or modify block data.
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
efficiency, 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 strat-
egy, 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 indi-
cated 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>. Typing <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 unexpect-
ed because the configurator 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 display 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 exam-
ple.
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 over-
view 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 indi-
cated in a block overview.
Type: PID Compound:
|
Mode AUTO | Alarms
FallBack AUTO |
| HAA 100.0 Eng
PV 0.0 Eng | LAA 0.0 Eng
SP 0.0 Eng | HDA 100.0 Eng
OP 0.0 % | LDA 100.0 Eng
SL 0.0 Eng |
TrimSP 0.0 Eng | Timebase Secs
RemoteSP 0.0 Eng | XP 100.0 %
Track 0.0 % | TI 0.000
| TD 0.000
HR_SP 100.0 Eng |
LR_SP 0.0 Eng | Options 00001100
HL_SP 100.0 Eng | SelMode 00000000
LL_SP 0.0 Eng |
| ModeSel 00000000
HR_OP 100.0 % | ModeAct 00000000
LR_OP 0.0 % |
HL_OP 100.0 % | FF_PID 50.0 %
LL_OP 0.0 % | FB_OP 0.0 %
|
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 re-
started.
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. (Stop-
ping 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 <Enter>, 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 exam-
ple). This page gives general information about the block and has a common format.
FULL DESCRIPTION Block: PID_1 Type: PID
Refresh rate 0.1040

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 recalcu-
lated 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/Supervi-
sor. (Database names and their LIN addresses are specified via the main
menu NETWORK option, described in .)
section 8.4.5Rate ms. Rate is the minimum up-
date period (i.e. maximum rate) at which an individual 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 pad-
ding 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 Descrip-
tion page for the parameter (Figure 8.4.1d shows an example).
FULL DESCRIPTION Field: PV Block: PID_1 Type: PID
Value 80.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 100.0 Eng
PV MANUAL g LAA 0.0 Eng
SP AUTO g HDA 0.0 Eng
OP REMOTE g LDA 0.0 Eng
SL F_MAN g
TrimSP F_AUTO g TimeBase Secs
RemoteSP g XP 100.0 %
Track TI 0.000
TD 0.000
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
<Enter>. (Disabled options may not respond to selection.)
A quicker alternative to accessing the pop-up options menu is to type the required op-
tion, 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),
acknowledgement (e.g. Unackd), status (e.g. Active), and priority (0 to 15). Update the
acknowledgement 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 0
HighDev Active 10
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 Speci-
fication 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 correspond-
ing 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 evaluated.
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 con-
nection, any attempt to write to the connection destination is immediately ‘corrected’ by the next con-
nection 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 performed 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
strategy, in semi-graphical format as shown in Figure 8.4.2. The blocks are displayed from left to right in or-
der of creation. 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 connec-
tions 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 <Es-
cape> 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 <Es-
cape> 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 Com-
pound 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 direc-
tion. 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 >01
Beta >02
dBase_1 >03
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 to-
gether with a default node address >ØØ. (Non-unique or invalid names are ‘beeped’ and not accepted. Do
not use ØØ or FF as node addresses). Move the cursor to the default address and type in the required node
address (two hex digits). Press <Enter> 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 down-
loaded 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 Utili-
ties 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 pro-
gram running in the local Controller/Supervisor.
Note: When a database is started in RAM it is automatically saved to the file in FLASH called filena-
me.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 above regarding 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
cannot be performed during runtime. Select LOAD from the UTILITIES options menu — the default filename
specification, 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.9 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
information.
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 en-
tered.
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 Mod-
bus 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 maximum number of Tables as defined by the MAX_TABLES field in the instrument Configuration (Header)
block. The Tables List offers sixteen tables, so four 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 remaining, 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 ad-
dresses.
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, respec-
tively, 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 us-
ing 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.
Table 8.5.5b 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
Table 8.5.5b 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) ad-
dresses 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 ad-
dress 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 pur-
pose, 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 con-
secutive 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 un-
signed, 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 or-
der 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 associ-
ated 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 unal-
located 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 writ-
ten 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 func-
tion 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 represen-
tation. ‘Value’ is read-only.
HA029280 Chapter 8
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 voltage 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
manufacturer 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 bat-
tery 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.1b Battery location - small frame unit

Figure 9.1a
(Access cover/Profibus option removed)
Access cover/Profibus enclosure location - large frame unit
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’ ap-
pears (approximately 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 inter-
section 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 accepted, 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
connector 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 Configu-
ration 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
configuration 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 con-
tents to the Profibus 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
respectively. 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
USB1
Panel cutout
Ethernet Serial comms 138 mm x 138 mm
– – + +
(both -0 + 1 mm)
Power
USB2 USB3 Profibus

USB Option
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
USB1
– –++
USB2 USB3 Profibus
USB option
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) 8 Rx/Tx –ve (A)
Rx/Tx +ve 3 Rx/Tx +ve (B)
(B) (pin 3) 7 Not connected
+5V (pin 6) 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 con-
figuration 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 communi-
cate 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

Notes
1. 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.
2. For this option, the keyboard (below the screen) is fitted at the factory and cannot be changed by
the user
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 dam-
age, 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 documenta-
tion.
Once the unit has been installed, store any internal packing with the external packing in case of future des-
patch.
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 machine screws passing through the panel from the front (‘A’ and ‘B’ in figure 11.2a). M5
studs or screws are recommended; 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 window dimensions and
section 11.2.1 for overlay fitting recommendations).
Clamping Maximum torque settings
Rear face of Jacking screw: 50cNm
plate
panel A A Locking nut: 300cNm
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
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
B
Panel cutout (A x A):
Jacking screw (4 places) 144 mm x 144 mm (-0 +1)
USB1
A C Overlay window (C x C):
114.5 mm x 114.5 mm
– – + +
{centred left-right but
offset from top of panel
USB2 USB3 Profibus cutout by 18.3 mm (B)}
USB option option
137.5 mm C
Notes: A
1. Ensure that the ambient temperature does not exceed 50˚C. Vertical panels only.
2. The flush mounting option keyboard is not user interchange- Min. inter-unit spacing (vertical): 50 mm.
able 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
(6 mm dia.) Profibus
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)
USB1
––++
USB Option
USB 2 USB 3 Profibus option
A C Overlay window (C x D):
C = 240 mm; D = 250mm
281.4 mm {centred left-right, but offset
from top of panel cutout by
30 mm (B)}
D
A
Notes:
1. Ensure that the ambient temperature does not exceed 50˚C. Vertical panels only.
2. The flush mounting option keyboard is not user interchange- Min. inter-unit spacing (vertical): 50 mm.
able Min. inter-unit spacing (horizontal): 50 mm.
Figure 11.2e Large frame unit mechanical dimenssions.
Chapter 11 HA029280
11.2.1 Overlay recommendations

1. For service considerations, the overlay panel should not be bonded to the instrument. For the same rea-
sons, it should not be bonded to the panel in such a way as to prevent service access.
2. For ‘open’ windows, it is recommended that a foam gasket or similar is positioned between the overlay
and the front face of the instrument such that this gasket is compressed when the overlay is secured. The
gasket must avoid the touch-screen area, as shown in figure 12.2.1, below.
3. For obtain the best IP rating, the overlay should incorporate a clear, flexible membrane covering the sur-
face of the instrument touch screen. In such cases, the following should be considered:
a. Where the membrane and the touch screen come into close proximity, it is possible that optical inter-
ference patterns such as Newton’s rings may appear. In order to prevent this, it is recommended that
an ‘anti-Newton’ spray be applied to the inner face of the membrane before the membrane is installed.
b. A low tack adhesive (e.g. double-sided adhesive tape) should be used to provide a seal between the
membrane and the non-touch-sensitive areas of the display (in a similar way to that shown for open
window gasket sealing, in figure 11.2.1, below). The presence of dust, or other foreign matter, is not
only unsightly, but it can also lead to unreliable operation of the touch screen. Ensure that both the
touch screen and the membrane are clean before sealing.
Typical gasket location:

on front face of instrument,
but avoiding the touch area.
F1 F2 F3
F4 F5 F6
Figure 11.2.1 Typical gasket location for ‘open’ windows

(small-fame unit shown; large-frame unit similar)
11.3 SPECIFICATION
The specification for the flush-mounting option differs from the specification given in Annex A in the mechan-
ical dimensions (given in figures 11d and 11e), and in the following items:
IP rating without overlay IP40
IP rating with overlay Depends on the design of the overlay panel.
HA029280 Chapter 11
Chapter 12: PRINTER/READER OPTION
12.1 INTRODUCTION
Provided software option L2 or higher is fitted, then this option allows the connection of up to two printers
and up to two readers using USB and/or EIA485, and/or (for printers only) Ethernet connections. The location
of the connectors is as shown in figures 1.2a and 1.2b; the assignment of printer to port, and the editing of
printer parameters is carried out in the Communications setup page and is described below. Any application
must be stopped and unloaded before these parameters may be edited, as described in section 4.3.5.
Note: USB1 is always fitted. USB2 and USB3 are fitted if the ‘2USB’ option is fitted. This is a separate
option from the Printer/Reader option.
12.2 PRINTER SET-UP

Figure 12.2 shows the communications set-up page.
SEtuP Maint EVt LoG
Set up
StaRtuP CoMMS CLoCK
intERnat PanEL
*** no application Loaded

***
11:58:06 Comms Setup 16/07/08
PoRt CoM1 CoM2 PBuS1 uSB1 uSB2 uSB3 EnEt1 EnEt2 EnEt3 EnEt4 EnEt5 EnEt6
Hardware RS485 RS485 RS485 uSB 2.0 uSB 2.0 uSB 2.0 Ethernet Ethernet Ethernet Ethernet Ethernet Ethernet
Protocol Modbus/M none none none Printer none ELin FtP Modbus/S Modbus/M termCfg Printer
node no. 3
Baud 9600
Parity nonE
Data Bits 8
Stop Bits 1
timeout 250 1500 1500
talk thru EnEt4
SaVE CanCEL EtHERnEt MoDBuS/M/tCP PRintERS
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 12.2 Communications setup page.
HA029280 Chapter 12
12.2 PRINTER SETUP (Cont.)

Notes:
1. The items which appear on the screen are option dependent. E.G. if the Profibus option is not fit-
ted, the PBUS1 port does not appear on the screen. Similarly, if the Printer/Reader option is not
fitted, the ‘PRINTERS’ soft key does not appear.
2. The communications set up page is more fully described in section 4.5.1
12.2.1 Assigning printers to ports

Touching the ‘protocol’ cell for any suitable port calls a pick-list to the display (see examples below) allowing
‘Printer’ to be selected. Once two printers have been assigned to ports, then ‘Printer’ does not appear as a
picklist item for any other port.
Ports which can have printers assigned to them are ‘prioritised’ such that the printer port with the highest
priority is deemed to have printer 1 assigned to it; printer 2 being assigned to the lower priority port.
The priority is ‘ENET6’ (highest), ‘USB1’, ‘USB2’, ‘USB3’, ‘COM2’, ‘COM1’ (lowest).
PoRt CoM1 CoM2 PBuS1 uSB1 uSB2
Hardware RS485 RS485 RS485 RS485 RS485
Protocol Modbus/M none none Modbus/M none

None None
None None
Modbus/M Printer
Printer Reader
Reader
Figure 12.2.1 Printer/port assignment examples
Note: When port assignation is complete, operate the ‘SAVE’ key, or the changes will be lost when the
next display page is called.
Chapter 12 HA029280
12.2.2 Printer parameters

After saving any changes to the port configuration, clicking on the ‘Printers’ Key in the comms setup page calls
the top level Printer configuration page to the screen. This shows the current configuration for Printers 1 and
2. This page always appears, and always with two printers, even if fewer have been assigned. Touching any of
the yellow- highlighted fields causes a pick-list menu to appear allowing the user to select the required value
Figure 12.2.2 shows the relevant part of a typical top-level Printer configuration page.
*** no application Loaded

***
15:00:19 Printers 16/07/08
Graphics-PCL3
Text Only
Graphics-PCL3 Printer1 Setup
Graphics-ESC/P Protocol: Graphics-PCL3
Palette: Colour CYMK
Page Format: a4
Printer1 Setup
Printer2 Setup Protocol: Graphics-PCL3
Protocol: Graphhics-ESC/P
Host:
Palette: Monochrome
Port: 9100
Print columns: 0
Palette: Colour CMYK
Line Feed Space: 24
Page Format: a4
Ethernet Printer detail
Plot (P1) SaVE CanCEL CoMMS
Figure 12.2.2 Printer configuration page
PARAMETERS
Protocol Allows ‘Text only’ or one of two common graphical printer protocols (Graphics-PCL3 and
Graphics-ESC/P) to be selected*. The required protocol should be determined from the
printer documentation.
Host This field appears only for Ethernet printers and allows the IP address of the required
printer to be entered. This information can usually be found as an entry in the printer
test page, or for a large network, from the network administrator.
Port Usually set to 9100 for printers (Ethernet only).
Palette: For ESC/P printers this is a non-editable field: ‘Monochrome’ (i.e. black and white print-
ing only). For PCL3 printers, ‘Monochrome’, ‘Colour CMY’, ‘Colour CMYK’ or ‘Colour
KCMY’ can be selected, as specified in the printer documentation. This is related to the
type of ink cartridges fitted, so if an incorrect selection is made, incorrect colours result.
Page Format For PCL3 printers only, this allows A4 (297 x 210mm) or Letter size (11 x 8½ inch) paper
to be selected as printing stock.
Print Columns For ESC/P printers only, this specifies the number of columns to be printed across the
paper. The information should be found in the printer documentation.
Line feed Space For ESC/P printers only, this is a measure of the number of lines per unit height of
printer paper. Refer to Printer documentation for setting details.
* For the sake of brevity, these are referred to as PCL3 and ESC/P in the remainder of this description
HA029280 Chapter 12
12.2.3 Push buttons

A number of buttons appear, equally spaced across the width of the lower part of the screen. The func-
tions of ‘SAVE” and ‘CANCEL’ are self evident. ‘COMMS’ returns the user to the Comms Setup page (unsaved
changes are lost without warning).
PLOT P1/PLOT P2 PUSH BUTTONS

‘PLOT P1’ appears if printer 1 is setup as a colour printer, otherwise it is missing from the screen. ‘PLOT P2’
appears if printer 2 is setup as a colour printer, otherwise it is missing from the screen. Operating either but-
ton causes a ‘Plot Colour Select’ pop-up menu to appear, allowing the user to change the plot colour for each
channel . The pop-up, and its associated colour pick-list, is shown in figure 12.2.3, below.
Black
Black
Cyan
Magenta
Blue Plot Colour Select
Channel 1: Black
Yellow
Channel 2: Cyan
Green
Channel 3: Magenta
Red Channel 4: Blue
Grey
Channel 5: Yellow
Channel 6: Green
Channel 7: Red
Channel 8: Grey
Channel 9: Black
Channel 10: Cyan
Channel 11: Magenta
Channel 12: Blue
Channel 13: Yellow
Channel 14: Green
Channel 15: Red
Channel 16: Grey
OK CANCEL
Figure 12.2.3 Plot Colour Select display
Chapter 12 HA029280
12.2.4 Printout
REPORTS
The printing of reports using .UYF files, edited using a standard text editor is as described in section 5.9,
above.
TRENDS
If a HISTDATA block is referenced within a .UYF file, together with a trend qualifier (‘T’ or ‘D’), then it will be
considered to be trend data provided that the DATA field refers to a GROUP block. Otherwise an empty rec-
tangle is drawn.
Syntax example 1:
[HISTDATA]:400:200T{1,3}
causes a black, rectangle to be drawn 400 dots high by 200 dots wide, containing horizontal trends for chan-
nels 1 and 3, in the colours specified (colour printers only).
Syntax example 2 (note 2):
[HISTDATA]:400:200D
causes a black, rectangle to be drawn 400 dots high by 200 dots wide, containing vertical trends for all chan-
nels, in the colours specified (colour printers only).
Notes:
1. The lines making up the rectangle are 1 dot thick.
2. Vertical trending is not supported for ESC/P printers
3. Instrument and group tag, if available, are printed above the rectangle.
4. Point tags, units and span low and high values are printed below the rectangle. For PCL3 colour
printers, this information is presented in the relevant trace’s colour.
5. The sample start and end date/time from the HISTDATA block are also included.
Figure 12.2.4 (below) shows a sample colour printout for four channels.
ALARM AND EVENT OBJECTS

If a HISTDATA block is referenced within a .UYF file, without a trend qualifier, then it will be considered to be
alarm and event text data provided that the DATA field refers to a DR_ALARM block. If the DR_ALARM block
is not referenced, no output is generated.
All alarm and events which comply with the DR_ALARM block, and which have a start date and time later
than the sample start time and date are included, including any alarms or events that occur at the sample end
date and time. Alarms are filtered according to the filtering configuration in the DR_ALARM block.
REPRINT
A new input to the DR_REPRT block ‘Reprint’ causes the latest report to be regenerated. This feature is in-
cluded, in case the printer cartridge was exhausted or the printer was out of paper at the first attempt.
Note: The Report reprint facility is lost at power down.
HA029280 Chapter 12
12.2.4 PRINTOUT (Cont.)
Instrument and
zone1 : group1 group identifiers
Trends within
bounding rectangle Instrument and
group identifiers
Zone1 : GRP01
Lo
Hi
Youngest data
Oldest data Youngest data
Oldest data
Sample start
26/01/09 26/01/09
10:48:42 10:51:04
Sample end
Tag: Lo: Hi:
ana00 10.00 90.00
ana01 20.00 80.00 Channel Tags, Span
ana02 30.00 70.00
Low/High values and
ana03 40.00 60.00
Sample start Sample end Units
14/07/08 14/07/08 ana04 0.00 100.00
date/time date/time ana09 0.00 100.00 C
16:17:19 16:17:36
Tag: Lo: Hi:

chan1 0.00 100.00 C Channel tags, Span low/
chan2 0.00 100.00
chan3 0.00 300.00 high values and units
chan4 0.00 300.00
Figure 12.2.4 Typical printouts
12.2.5 Application notes
1. For the ESC/P protocol, only Mode 0 (8bit) and Mode 32 (24 bit) are supported
2. As there is no feedback facility from the printer to the LPTDEV block, the printout is sent even if the
cartridge is exhausted or the paper tray is empty.
12.3 READER INPUT

Touching the ‘Protocol’ cell for any suitable port calls a pick-list to the display (see examples in figure 12.2.1
above) allowing ‘Reader’ to be selected. Once two readers have been assigned to ports, then ‘Reader’ does not
appear as a picklist item for any other port.
Ports which can have readers assigned to them are ‘prioritised’ such that the reader port with the highest pri-
ority is deemed to have reader 1 assigned to it; reader 2 being assigned to the lower priority port.
The priority is ‘USB1’ (highest), ‘USB2’, ‘USB3’, ‘COM2’, ‘COM1’ (lowest).
Chapter 12 HA029280
Appendix A: TECHNICAL SPECIFICATION In order to comply fully with BS EN61010, all

General specification I/O and hardware alarms must be enabled
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: -20 to +60˚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
Clock (RTC) data

Temperature stability 0 to 50˚C: ± 20 ppm
Ageing ±5 ppm per year
HA029280 Appendix A
Issue 12 Dec 14 Page A-1
SPECIFICATION (Cont.)
Programmer
Maximum number of concurrent programs: 8
segments per program: 32
channels: 8
digital setpoints: 128
exit conditions: 64
user values: 32
wait conditions: 64
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 1000
Batch
Max. no. of concurrent batches (files) 8
Max. no. of phases per batch 40
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
Notes:
1. The maxima given here are defaults and are the recommended limits. 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, the maximum
is set to the new value and there may then be insufficient memory to load the entire database or to allow on-line
reconfiguration. In such a case ‘connections’ disappear first. FEATTs are not subject to this problem as, when a
database is saved, there are not normally any FEATTs present, so the maximum cannot be exceeded.
2. If the EDB maximum is exceeded some EDBs will malfunction, affecting LINtools functionality.
Legacy Large Large

Continuous database resource Default
Programmer SFC Database
Database size (kBytes) 145 181 255 319
Number of function blocks (max) 512 512 512 512
Number of templates (max.) 100 100 100 100
Number of libraries (max.) 50 50 50 50
Number of EDBs (max.) 32 32 32 32
Number of FEATTs (max.) 512 512 512 512
Number of TEATTs 128 128 128 128
Number of servers (max.) 2 2 2 2
Number of connections 1024 1024 1024 1024
Appendix A HA029280
Page A-2 Issue 12 Dec 14
SPECIFICATION (Cont.)
Sequence control resources
Legacy Large Large

Sequence control resource Default
Programmer SFC Database
Sequence memory program data (kBytes) 112 112 56 28
Sequence memory SFC resources (kBytes) 73 73 38 19
Simultaneously active
20 20 10 5
independent sequence tasks
SFC actions (including root SFCs) 100 100 50 25
Steps 320 320 160 80
Action associations 1200 1200 600 300
Actions 600 600 300 150
Transitions 450 450 225 115
Legacy programmer resources

No. of simultaneously running programs 8 max. (See table for resource distribution)
Profiled analogues 16 max.
Profiled digitals 32 max.
Segments per program 250 max.
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
.uyn file size limits

The figures given below are typical figures. The actual maximum number of lines depends on the length of aliases, and on the language(s) being used.
Small frame unit: 250 to 400 lines
Large frame units: 600 to 950 lines
HA029280 Appendix A
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 (EIA485)
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’), PCL3 printers, ESC/P printers, Bar-code readers
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
Appendix A HA029280
Function Blocks supported
Category Block Function

BATCH BAT_CTRL Batch controller / interface
DISCREP Transmitted/received digital signal-match to diagnose plant faults
RCP_SET Recipe set
RCP_LINE Recipe Line
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
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
TC_LIFE Thermocouple life expectancy block (AMS2750)
TC_SEL Thermocouple selector block. manages multiple thermocouples for
furnace applications
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
AN_CONN Analogue connections
ANMS Analogue manual station
DG_CONN Digital connections
DGMS Digital manual stations
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
REALTIME Converts real numbers to/from TIMEs
UINTENUM Converts from integer to enumerated type
DIAG AGA8DIAG AGA8 block diagnostics
ALH_DIAG Alarm history statistics
DIAG (Cont.) ALINDIAG ALIN MAC/LLC diagnostics
HA029280 Appendix A
FUNCTION BLOCKS SUPPORTED (Cont.)

AMC_DIAG Comms statistics on application master
DB_DIAG Database diagnostics
DDR_DIAG T800 data recording statistics
EDB_DIAG External database diagnostics block
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
NATCDIAG Audit Trail Consumer diagnostics
NATPDIAG Audit Trail Provider diagnostics
PBUSDIAG Profibus diagnostics
PMC_DIAG Profibus diagnostics
PNL_DIAG Front panel information
PRPDIAG Port Resolution Protocol diagnostics
ROUTETBL Routing table block
RSRCDIAG Database and system resource diagnostics
RTB_DIAG Routing table diagnostic block
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
ACT_2A2WT3 Action block with timers
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_ACC Access to panel system
PNL_CMD Panel Command
PNL_DICT Panel dictionary block. Interface between panel and dictionary files.
PNL_DLG Panel dialogue generation
PNL_MSG Panel message generation
READER Bar code reader
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
Appendix A HA029280
FUNCTION BLOCKS SUPPORTED (Cont.)

PROGRAMMER PROGCTRL Controls the overall execution of setpoint programs
PROGCHAN Data and options for a single profile channel
SEGMENT Shows up to four segments of the profiled program
RECORDER 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
HISTDATA Allows the inclusion of trend and event/alarm data into a printed
report. Refers to a period in history as defined by start/end date/time
markers.
SELECTOR 2OF3VOTE Selects ‘best’ input from three (averaging only the inputs in toler-
ance)
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
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.
HA029280 Appendix A
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
unLoaD SaVE SaVE aS StoP
SUMMARY APPLN
3 6
Press unLoaD
SETUP CLONING 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
9 CLoninG FiLE MGR
Press StoP
Press
SoFt oPtS BatCH Maint
SoFt oPS
Figure B2a Access to the SOFT OPS key.
(Continued)
HA029280 Appendix B
Issue 12 Dec 14 Page B-1
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 12 Dec 14
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 Ï CF
! 21 Q 51
“ 22 R 52 ¡ A1 Ð D0
# 23 S 53 ¢ A2 Ñ D1
$ 24 T 54 £ A3 Ò D2
% 25 U 55 ¤ A4 Ó D3
& 26 V 56 ¥ A5 Ô D4
‘ 27 W 57 A6 Õ D5
( 28 X 58 § A7 Ö D6
) 29 Y 59 ¨ A8 × D7
* 2A Z 5A © A9 Ø D8
+ 2B [ 5B ª AA Ù D9
, 2C \ 5C « AB Ú DA
- 2D ] 5D ¬ AC Û DB
. 2E ^ 5E – AD Ü DC
/ 2F _ 5F ® AE Ý DD
ˉ AF Þ DE
0 30 ` 60 ß DF
1 31 a 61 º B0
2 32 b 62 ± B1 à E0
3 33 c 63 2
B2 á E1
4 34 d 64 3
B3 â E2
5 35 e 65 ´ B4 ã E3
6 36 f 66 µ B5 ä E4
7 37 g 67 ¶ B6 å E5
8 38 h 68 · B7 æ E6
9 39 i 69 ¸ B8 ç E7
: 3A j 6A 1
B9 è E8
; 3B k 6B 0
BA é E9
< 3C l 6C » BB ê EA
= 3D m 6D 1
/4 BC ë EB
> 3E n 6E 1
/2 BD ì EC
? 3F o 6F 3
/4 BE í ED
¿ BF î EE
@ 40 p 70 ï EF
A 41 q 71 À C0
B 42 r 72 Á C1 ð F0
C 43 s 73 Â C2 ñ F1
D 44 t 74 Ã C3 ò F2
E 45 u 75 Ä C4 ó F3
F 46 v 76 Å C5 ô F4
G 47 w 77 Æ C6 õ F5
H 48 x 78 Ç C7 ö F6
I 49 y 79 È C8 ÷ F7
J 4A z 7A É C9 ø F8
K 4B { 7B Ê CA ù F9
L 4C | 7C Ë CB ú FA
M 4D } 7D Ì CC û FB
N 4E ~ 7E Í CD ü FC
O 4F Î CE ý FD
þ FE
Table C ASCII codes ÿ FF
HA029280 Appendix C
Issue 12 Dec 14 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, archiv-
ing 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.
CJK Refers to Chinese/Japanese/Korean type languages.
Configuration Configuration is the process of specifying the components of an application in order to
determine the performance and behaviour of an instrument. Configuration is usually car-
ried 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
instrument.
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
ESC/P Epson™ Standard Code for printers - The Epson standard open printer protocol.
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 fa-
cility. 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 ‘Application’.
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,
incorporates them into its own products, and sells these products onto other customers
under its own name.
PCL3 Printer Command Language. The Hewlett Packard standard printer open protocol.
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 12 Dec 14
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 tem-
perature, 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, cre-
ated by a user.
HA029280 Appendix C
Issue 12 Dec 14 Page C-3
Appendix D: LEGACY PROGRAMMER DETAILS

This Annex contains details of the Programmer used in previous versions of the Visual Supervisor. Details are
not included here for the araes where the previous version operation is the same as that of the current ver-
sion.
The appendix consists of the following sections:

D1 Running a program
D2 Holding a program
D3 Aborting a program
D4 Monitoring a program
D5 Editing a program
Sections D1 to D4 require Operator level access; section D5 requires Engineer level access.
The Menu key at the bottom of the screen can be operated to re-call the Pop-up menu and the beginning of
the task if required.
D.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.
D1.1 RUNNING A PROGRAM NOW

1. In the row of navigation keys at the bottom of the screen, PRoGRaMMER LoGGinG uSER SCREEnS
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 Press menu key
been selected.
2. Select PROGRAMMER.
Programmer
The Programmer window appears, offering two choices: MONITOR PROGRAMS SCHEDULE
PROGRAMS and SCHEDULE.
PREVIEW PRE-PLOT EDIT
3. Select PROGRAMS. RUN HOLD ABORT
RUN FROM SKIP
HA029280 Appendix D
Issue 12 Dec 14 Page D-1
D1.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 simultane-

ously. Where more than one such program is running, the load/save 09:12:37 Load/Save program 04/04/06
screen (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 File Name: ????????
this program.
All display pages refer to the program associated with the currently
selected ‘Id’.
LOAD
For any particular programmer display page, the identical page for
other valid Ids can be scrolled-through, using the right and left arrow
keys.
4. Press the yellowed field of question marks.
09:12:49 Load/Save program 04/04/06

On the left side of the screen a pick-list (vertical menu) appears, SAMPLE
showing the programs that the instrument currently holds. If nec- File Name: ????????
essary, the scroll bar at the bottom of list can be used to reveal dsample
STMAXALL
more. ENMAXSEG
ENMAXSP
5 Press the name of the required program. The background of the SAMPLE
selected program’s name changes to yellow. LOAD
6 Press the Return key (the green arrow)

IDLE
09:15:33 Archive Manage 04/04/06
The pick-list disappears and the Load/Save Program page now
shows the name of the selected program on a yellow background. File Name: SAMPLE
7. Press the LOAD key

LOAD
SAMPLE
IDLE ??:??:?? 1
09:15:57 Sample 04/04/06
The full Programmer menu appears. With no program running,
HOLD and ABORT are greyed out. The Program pane reads IDLE Programmer
on a white background, showing the program is loaded but idling, MonitoR PRoGRaMS SCHEDuLE
not running. PREViEW PRE-PLot EDit
Run
8. Press 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 Programmer
expected time of completion and the number of the segment MonitoR PRoGRaMS SCHEDuLE
currently executing are also displayed.
PREViEW PRE-PLot EDit
The program is now running. Run HoLD aBoRt
Run FRoM SKiP
Appendix D HA029820
Page D-2 Issue 12 Dec 14
D1.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 MonitoR PRoGRaMS SCHEDuLE
a user-specified point after its start point.
The first seven steps are the same as in D1.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 pro-
gram just loaded.
SAMPLE
The ‘Duration’ field shows how long the program will take to IDLE
0/0
complete. 08:54:07 Sample 04/04/06

Program
The ‘Run From’ field is waiting for a time-into-program value Duration: 03:55:00
to be entered, from which the program run is to be started. Run From: 00:00:00
Initially, the Run From field is set at the default of 00:00:00 (the Segment
start) so, under the Segment header below it, the segment name Name: 1
is 1, the first. Duration: 00:05:00
Time Through: 00:00:00
The ‘Time Through’ field shows at what time through the seg-
ment the program will start. RUN
9. Press the yellowed ‘Run From’ field.
In the left part of the display a numeric keyboard appears. At

the top a confirmation bar shows the current ‘Run From’ time as IDLE
SAMPLE
??/??/??
0/0
00:00:00 (hh:mm:ss), with a cursor blinking under the first ‘0’. 08:56:03 Sample 04/04/06
0 1:45:00
Program
7
Duration:
8 03:55:00
9
10 From the keyboard, key in the required ‘Run From’ time (in this Run From: 00:00:00
example 01:45:00. 4 5 6
Segment
1 2 Name:
3 1
Duration: 00:05:00
11 Press the green Return arrow . 0
Ti Through: 00:00:00
Time
RUN
SAMPLE
The keyboard disappears to reveal the full Run From page. If the IDLE ??/??/??
0/0
selected time starts running the program from beyond the first 08:57:30 Sample 04/04/06
Program
segment, the ‘Name’ and ‘Time Through’ fields will show differ- Duration: 03:55:00
ent values. Run From: 01:45:00
Segment
Name: 4
Duration: 01:50:00
12 To run the program now, press the RUN key RUN
The main display reverts to the Programmer menu. SAMPLE

RUNNING 1 3 : 4 1 : 0 4
0/0
08:59:43 Sample 04/04/06

Program
The Program pane changes to green, showing RUNNING, the Duration:Programmer
03:55:00
MONITOR
Run PROGRAMS SCHEDULE
From: 01:45:00
time of completion, and the segment number.
PREVIEW PRE-PLOT
Segment EDIT
Name: 4
The program is now running, from the specified point. RUN
Duration:HOLD
01:50:00ABORT
RUN FROM SKIP
RUN
HA029280 Appendix D
D1.3 SCHEDULING A PROGRAM aCCESS SYStEM aLaRMS

Scheduling a program means setting a time at which it will
start to run automatically. 2
Press
PRoGRaMMER key
1
Press menu key
If another program is running at the scheduled start time, the
scheduled program will be delayed and started later. The late Programmer
start is recorded in the Alarm History. MONITOR PROGRAMS SCHEDULE
1. In the row of navigation keys at the bottom of the screen, RUN HOLD ABORT
press the Menu key. RUN FROM SKIP
09:12:49 Schedule Program 20/02/00

2. Select PROGRAMMER from the pop-up menu that ap-
pears File Name: ????????`
Start Date: ??/??/??`
Start Time: ??:??:??`
With no program running, the Programmer menu which
Iterations: 1`
appears, has just two options: PROGRAMS and SCHEDULE.
ACCEPT
3 Select SCHEDULE.
The Schedule Program page appears, prompting for infor-

mation about the program to be scheduled. 09:13:00 Schedule Program 20/02/00
????????
File Name: ????????`
4 Press the File Name field. dsample Start Date: ??/??/??`
STMAXALL `
ENMAXSEG Start Time: ??:??:??
`
ENMAXSP Iterations: 1
The left side of the screen shows a pick-list of the pro- SAMPLE
grams that the instrument holds. ACCEPT
ACCE

5. Select the required program. SAMPLE
File Name: ????????`
dsample Start Date: ??/??/??`
STMAXALL `
ENMAXSEG Start Time: ??:??:??
ENMAXSP Iterations: 1`
SAMPLE
The background of the program name changes to yellow.
ACCEPT
ACCE
6. Press the Return key (the green arrow)

The pick-list disappears, and the File Name field shows File Name: SAMPLE `
the name of 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
ACCEPT
currently-running program ends, the Start Date and Start
Time can be left undefined, as shown here.
Appendix D HA029820
D1.3 SCHEDULING A PROGRAM (Cont.) 09:15:03 Schedule Program 04/04/06

? ?/??/??
File Name: SAMPLE `
D1.3.1 Specifying the Program start date 7 8 9
7. Press the Start Date field. 4 Start
5 Time:6 ??:??:??`
1 Iterations:
2 3 1`
The left side of the screen shows a numeric keyboard, with a . 0

ACCEPT
cursor flashing under the first number-space in the black confir-
mation bar at the top.
8. Key in the required date, in the format set for your instrument. 04/04/06
File Name: SAMPLE `
7 8 9
4 Start
5 Time:6 ??:??:??`
After the first digit has been keyed-in, the cursor moves under
the space for the next one, and so on. 1 Iterations:
2 3 1`
. 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 Program page, press the red cross key. 09:15:13 Schedule Program 04/04/06
File Name: SAMPLE `

9. When the process is complete, and the confirmation bar shows Start Date: 04/04/06`
the date in the correct format, press the Return key. Start Time: ??:??:??`
Iterations: 1`
The keyboard disappears and the Schedule Program page now
ACCEPT
shows the specified date in the Start Date field.


D1.3.2 Specifying the Program start time ??:??:??
File Name: SAMPLE `
7 8 9
10 Press the Start Time field. Start Date: 04/04/06`
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.

10:30:00
File Name: SAMPLE `
12. When time entry is complete and the confirmation bar shows 7 8 9
Start Date: 04/04/06`
the time in the correct format, press the Return key. 4 Start
5 Time:6 ??:??:??`
`
1 Iterations:
2 3 1
. 0
ACCEPT
The keyboard disappears and the Schedule Program page shows 09:18:04 Schedule Program 04/04/06
the specified time in the Start Time field.
File Name: SAMPLE `
Start Time: 10:30:00`
Iterations: 1`
ACCEPT
HA029280 Appendix D
D1.3 SCHEDULING A PROGRAM (Cont.)
D1.3.3 Changing the number of iterations (runs)
13 In the Iterations field, press the ‘1’ 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 oper- 4 5 Time:
Start 6 10:30:00`
ate as described in step 8. 1 Iterations:
2 3 1
`
. 0
ACCEPT
If the program is to repeat continuously until further notice,
press ‘0’.
15. The Schedule Program page displays the specified number of File Name: SAMPLE `
iterations. Start Date: 04/04/06`
Start Time: 10:30:00`
`
Iterations: 0(Continuous)
ACCEPT
The program is now scheduled.
Appendix D HA029820
D1.4 SEGMENT SKIP

Skipping a program segment causes the program to stop running its current segment and start running the
next segment immediately.
Skip is initiated from the Programmer menu.

Programmer
MonitoR PRoGRaMS SCHEDuLE
HoLD aBoRt
SKIP
Press
SKiP key
D1.4.1 Segment transition consequences
FROM DWELL, SET OR SERVO TO ANY OTHER TYPE

These transitions are ‘safe’ and provide a bumpless transition of SP from one segment to the next. The pro-
gram finishes early.
FROM RAMP TO SET

Not Bumpless. The ramp is terminated early. The resulting bump is larger or smaller than that programmed
depending 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 un-
skipped.
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 (INDEFINITE 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 Appendix D
D2 HOLDING 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 pro-
gram at that point while attempts are made to fix the problem
2 for Engineers to make on-line changes to a running program.
This section is for Operators, and so the following deals with the first situation.
SAMPLE
RUNNING 13:41:14 4
12:32:09 Sample 04/04/06
1. With a program running, and the full Programmer menu dis- Programmer
played (as at step 8 in D1.1. Running a program), press HOLD. MonitoR PRoGRaMS SCHEDuLE
HOLD aBoRt
SKiP
The Program pane changes to yellow and reports HELD.
SAMPLE
The estimated time of completion starts incrementing in sec- HELD
12:32:09
13:41:23 4
Sample 04/04/06
onds.
Programmer
Left of the page title is the current time. To view the time-into-
program you should use the MONITOR facility (section D.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 program is usually continued from that point using RUN (see section D1.1 Running a program
now). If the attempts are unsuccessful, the program is usually aborted, as described in D3 below.
D3 ABORTING A PROGRAM
Starting from the end of D2.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 D1.1 Running a
program now).
SAMPLE
IDLE ??:??:?? 4
12:34:54 Sample 04/04/06
Programmer
RUN HoLD ABORT
RUN FROM SKiP
Appendix D HA029820
D4 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.
D4.1 THE MONITOR FACILITY

With a program running and the Programmer menu displayed (step 8 in section D1.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 Appendix D
D4.2 THE PREPLOT FACILITY

spx7m 3/3
RUNNING 15:35:01 REF : 1 D25DO4B COMMS
D4.2.1 Standard display mode 15:30:57 spx7m 04/04/06
SP 1
41.9
With the Programmer menu displayed and a program running (see 41.9
SP 2
step 8 in section D1.1. Running a program now), press PREPLOT. 57.34
57.34
DSP 1
NO DATA
A display appears, showing a profile of the target and the actual DSP 2
PVs moving slowly (perhaps imperceptibly) from right to left past a OPEN
vertical cursor at the centre of the screen. DSP 3

NO DATA
DSP 4
Note: The trend resolution is such, that short duration events (in 03:56 00:00 03:56
OPEN
particular zero duration spikes), will not be visible. Figure D4.2.1a

Preplot display - program running.
The cursor marks the current time.
spx7m 3/3
The actual PVs, SPs and digital outputs are to the left of the cursor IDLE ??/??/?? D25DO4B COMMS
15:35:51 spx7m 04/04/06
and the target SPs are to the right. SP 1
28.3
28.3
SP 2
With the same program loaded but not running (Idle), the display 42.25
42.25
shown opposite appears, showing the profiles programmed for the DSP 1
NO DATA
four variables. DSP 2
OPEN
DSP 3
NO DATA
DSP 4
OPEN
07:56 00:00
Figure D4.2.1b
Preplot display - program idle
D4.2.2 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 D3.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.
Buttons have similar effect but spx7m
13:29:07 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
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)
factor 'Back Live’ key
Figure D4.2.2 Review mode controls
Appendix D HA029820
D5 EDITING A PROGRAM
D5.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 D1.1).
D5.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).
D5.1.2 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.
Before editing can start, the Program Editor page must be accessed as described in section D5.2. Once the
editor page has been accessed, the program can be edited in the following ways:
Changing a setpoint (section D5.3)
By changing the type of ramp to it

By changing its value
Changing a segment (section D5.4)
By changing its identifier

By changing its duration
Inserting or deleting a segment (section D5.5)
Inserting a segment
Deleting a segment
Changing the Hold Back properties for any analogue setpoint (section D5.6)
Choosing the setpoint

Changing the Holdback mode
Changing the Holdback value
Changing program properties (section D5.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
HA029280 Appendix D
D5.2 PROGRAM EDITOR PAGE ACCESS aCCESS SYStEM aLaRMS
1. Press the Menu key, then PROGRAMMER oVERViEW PRoGRaMMER LoGGinG
Programmer
1 2
MONITOR PROGRAMS SCHEDULE
Press Programmer key
Press menu key
The Programmer menu appears. RUN HOLD ABORT
RUN FROM SKIP

2. Press PROGRAMS
The Load/Save Program page appears, prompting you for the File Name: ????????
name of a file to Load or Save. (To edit a program, it must first
be loaded.)

3. Press the File Name field (the question marks).
On the left of the screen, a pick-list appears, containing the

programs held by the instrument. ????????
File Name: ????????
dsample
4. Press the name of the program to be edited STMAXALL
ENMAXSEG
ENMAXSP
5. Press the green Return key SAMPLE
LOAD SAVE AS DELETE
The Load/Save program page displays the name of the selected

program. 08:31:15 Load/Save program 05/04/06
File Name: SAMPLE

6. Press LOAD.
If the program has components (parameters) which are not in

the LIN database then an error message appears and the pro- LOAD SAVE SAVE AS DELETE
gram does not load.
After a successful load, the Programmer menu reappears. 08:31:23 Load/Save program 05/04/06
Programmer
File Name: SAMPLE
7. Press EDIT MONITOR PROGRAMS SCHEDULE

The Program Editor page appears showing the values of the RUN SAVE HOLD
LOAD SAVE AS ABORT
DELETE
setpoints in tabular form.
RUN FROM SKIP
Each row represents one setpoint along a horizontal timebase

SAMPLE
marked in segments. Some of the rows are for analog setpoints 08:31:49 05/04/06
SP 1 2 3
and some are for digital ones. 00:05:00 00:50:00 00:35:00
Ana In 1 S R R
to 50.0 to 100.0 to 0.0
Ana In 2 S R R
to 50.0 to 65.0 to 20.0
Each column represents a segment, and each segment is identi- Ana In 3 S
to 50.0
R
to 99.0
R
to 97.7
fied by a name or number shown at the top of the column. Un- Dig in 1 OPEN CLOSED OPEN
der the segment identifier is the time duration of the segment. Dig in 2 CLOSED OPEN CLOSED
Dig in 3 OPEN CLOSED OPEN
All the yellowed fields yield further information when pressed.
Appendix D HA029820
D5.3 CHANGING A SETPOINT
D5.3.1 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 seg-
ment 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 inter-
vention). As there is no change, power output remains constant. May be used only in the first segment.
SERVO TO PROCSS VARIABLE (PV)

The instrument reads the current process value and sets the setpoint to that value. Because the current proc-
ess 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 seg-
ment 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.
D5.3.2 Teminology
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.
HA029280 Appendix D
D5.3.3 CHANGING RAMP TYPE (Cont.)

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

08:33:15 SAMPLE 05/04/06
SP 1 2 3
Press the yellowed ‘Ramp’ field. 00:05:00 00:50:00 00:35:00
Ana 1 S
In Segment: 2 R
to 50.0 to 100.0
R
to 0.0
InSetpoint: AnaRtoIn 65.0
1
S R
Ana 2 to 50.0 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
Dig in 2 CLOSED OPEN CLOSED
DONE
A pick-list of ramp types appears, with ‘Ramp’ highlighted 08:33:49 SAMPLE 05/04/06
Rampp SP 1 2 3
00:05:00 000:50:00 00:35:00
1 S
Ana In Segment: 2 R
to 50.0 to 100.0
R
to 0.0
Dwell
Ana InSetpoint: AnaRtoIn 65.0
1
S R
Step 2 to 50.0 to 20.0
Press the required type (in this case, ‘Ramp@’). Ramp SType: RampR
Ana In 3 to 50.0 to 99.0
R
to 97.7
Ramp@ to: 100.0
Dig in 2 CLOSED OPEN
O
DONE
DON CLOSED
i 3 OPEN
Di in
Dig CLOSED
C OPEN
08:34:08 SAMPLE 05/04/06

Ramp@
p SP 1 2 3
00:05:00 000:50:00 00:35:00
1 S
Ana In Segment: 2 R
to 50.0 to 100.0
R
to 0.0
Dwell
Ana InSetpoint: AnaRtoIn 65.0
1
S R
Step 2 to 50.0 to 20.0
Ramp SType:
Ana In 3 to 50.0RampR
to 99.0
R
to 97.7
Ramp@ to: 100.0
‘Ramp@’ highlights yellow. Dig in 2 CLOSED

DONOOPEN
DONE CLOSED
i 3 OPEN
Di in
Dig CLOSED
C OPEN
Press the green ‘Return’ key.
08:35:13 SAMPLE 05/04/06

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

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

SP 1 1a 2
00:05:00 00:00:00 00:50:00
In the Program Editor page, select the analogue cell holding the value Ana 1 S
In Segment: 1 R R
to 50.0 to 100.0 to 00.0
to be changed. Ana InSetpoint:
S
2 to 50.0AnaRtoIn 65.0
1 R
to 65.0
SType: StepR R
Ana In 3 to 50.0 to 99.0 to 99.0
A dialogue box appears, showing: Dig
to: 50.0CLOSED
in 1 OPEN OPEN
1 the segment name or number DONE
2 the setpoint name for that row
3 the setpoint type
08:43:48 SAMPLE 05/04/06
4 the current target value for the setpoint in that cell. SP 500:05:00
01. 0 0 1a 2
00:00:00 00:50:00
7
Ana 18 to 50.0
S
In Segment: 9 1 to 100.0
R R
to 0.0
InSetpoint: AnaR In 1
S R
4
Ana
5
2 to 50.0
6 to 65.0 to 65.0
SType: StepR R
Ana In 3 to 50.0 to 99.0
To change the target value, touch the value and enter the new value to 99.0
1
Dig in 12 OPEN 3
to: 50.0CLOSED OPEN
using the keyboard display which appears.
. 0
DONE CLOSED
in 3 OPEN
Dig i CLOSED OPEN
Press the Return key
08:43:56 SAMPLE 05/04/06

SP 1 1a 2
00:05:00 00:00:00 00:50:00
The dialogue box reappears, this time showing the new value. Ana 1 S
In Segment:
to 50.0
R
1 to 100.0 R
to 00.0
InSetpoint: AnaRtoIn 65.0
1
S R
Ana 2 to 50.0 to 65.0
SType: Step R R
Ana In 3 to 50.0 to 99.0 to 99.0
Dig to: 60.0CLOSED
in 1 OPEN OPEN
Press DONE Dig in 2 CLOSED OPEN
DONE CLOSED
The Program Editor page returns, with the new value shown in the
selected cell.
08:44:23 SAMPLE 05/04/06
SP 1 1a 2
To save the setting, press the Option key (below the screen), and 00:05:00 00:00:00 00:50:00
Ana In 1 S D R
then the SAVE button. to 60.0
S
to 100.0
R
Ana In 2 to 50.0 D to 65.0
S R
Ana In 3 to 50.0 D to 99.0
Dig in 1 OPEN OPEN CLOSED
Dig in 2 CLOSED CLOSED OPEN
Dig in 3 OPEN OPEN CLOSED
Option key
HA029280 Appendix D
D5.4 CHANGING A SEGMENT

In the Program Editor page, press the identifier at the top of the col- 08:46:49 SAMPLE 05/04/06
umn of the segment to be modified. For example, segment 1. SP 1 2 3
00:05:00 00:50:00 00:35:00
Ana In 1 S R
to 50.0 to 100.0 to
R
0.0
A dialogue box appears with two fields: Segment and Duration, and Ana
Segment:
S 1 R R
In 2 to 50.0 to 65.0 to 20.0
Duration: 00:05:00
three buttons: INS SEG, DEL SEG and DONE. Ana
S R R
In 3 to 50.0 to 99.0 to 97.7
Dig inINS SEG DEL SEG
1 OPEN CLOSEDDONEOPEN
The following subsections show how to change a segment’s identifier Dig in 2 CLOSED OPEN CLOSED
and duration respectively. Inserting and deleting segments is de- Dig in 3 OPEN CLOSED OPEN
scribed in section D5.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.
D5.4.1 Changing segment identifier

In the dialogue box, press the Segment field.
A ‘qwerty’ keyboard appears.

08:44:03 SAMPLE 04/04/06
1
A numeric/symbol keyboard can be called by pressing the ‘up arrow’
key at bottom left. A further operation of the arrow key calls a q w e r t y u i o p
keyboard of accented lower-case letters. Pressing the up arrow key

a s d f g h j k l ;
again re-displays the original ‘qwerty’ keyboard.
z x c v b n m ,
The segment identifier can be a name, a number, a character or a
digit, but 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 key. 08:44:23 SAMPLE 05/04/06
a 2 3
SP 00:05:00 00:50:00 00:35:00
Once the segment identifier has been keyed in, the Return key is Ana In 1 S R
to 50.0 to 100.0
R
to 0.0
S R R
operated to save it. 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 97.7
The Program Editor page reappears, showing the new identifier for Dig in 1 OPEN CLOSED OPEN
the segment.
Appendix D HA029820
D5.4.2 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 effect of this upon the operation of the process
plant.
SAMPLE
In the dialogue box, press the Duration field. 09:01:37 05/04/06
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
Segment:
S 1 R R
Ana
4 5 6
In 2 to 50.0 to 65.0 to 20.0
Duration: 00:05:00
S R R
A numeric keyboard appears, with the current duration displayed at Ana In 3 to 50.0 to 99.0 to 97.7
1
Dig 2
inINS 3
SEG DEL SEG
1 OPEN CLOSEDDONEOPEN
the top in hh:mm:ss format. The format can be changed, as de-
scribed in section 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 09:02:09 SAMPLE 05/04/06
1 2 3
it. 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
S R R
The Program Editor page appears, showing the new duration for the Ana In 2 to 50.0 to 65.0 to 20.0
S R R
segment. Ana In 3 to 50.0 to 99.0 to 97.7
Note: Neither an individual segment duration nor the total
program duration may exceed 49 days.
D5.5 INSERTING/DELETING A SEGMENT
D5.5.1 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.
09:01:54 SAMPLE 05/04/06
1 2 3
In the segment preceding the new segment’s location, press the SP 00:06:00 00:50:00 00:35:00
segment-name cell at the top of the column. Ana In 1 S R R
Ana
to 50.0
S
In 2 to 50.0
New Segment to 100.0
R
to
R
0.0
Segment:
S
to 65.0
R
to 20.0
R
In the dialogue box in section D5.4, press the INS SEG key. 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 segment.
Press the Segment field (yellowed)

09:02:13 SAMPLE 05/04/06
A ‘qwerty’ keyboard appears. The procedure for entering the identi-

q w e r t y u i o p
fier for a new segment is the same as that described in section D5.4.
a s d f g h j k l ;
When the required segment name (for example, 1a) has been en-
tered, the Return key is operated. z x c v b n m ,
HA029280 Appendix D
D5 5.1 INSERTING A (NULL) SEGMENT (Cont.) 09:02:37 SAMPLE 05/04/06

SP 1 2 3
00:06:00 00:50:00 00:35:00
The New Segment window reappears, displaying the name of the new Ana S
In 1 to 50.0 R R
segment. Ana
S New Segment
In 2 to 50.0
to 100.0
R
to
R
0.0
Segment:
S
1a to 65.0
R
to 20.0
R
Ana In 3 to 50.0 to 99.0 to 97.7
This inserted segment will be a ‘null’ operation, until it has been Dig OK
in 1 OPEN CANCELOPEN
CLOSED
modified. A null operation consists of a dwell of zero duration. Dig in 2 CLOSED OPEN CLOSED
Press OK.
The Program Editor page returns with a new, but empty, segment SAMPLE
09:02:59 05/04/06
inserted after the one which was being modified. SP 1 1a 2
00:06:00 00:00:00 00:50:00
S
Ana In 1 to 50.0 R
D to 100.0
In order to view the whole setpoint sequence, it might be necessary S
Ana In 2 to 50.0
R
D to 65.0
to scroll right or left using the scroll bar/arrows at the bottom of the S
Ana In 3 to 50.0 D R
to 99.0
display. Dig in 1 OPEN OPEN CLOSED
Dig in 2 CLOSED CLOSED OPEN
The SAVE button is used to save the changes when completed. If Dig in 3 OPEN OPEN CLOSED
necessary, the SAVE button is called to the display by pressing the
‘option’ key located below the screen.
D5.5.2 Deleting a segment Option key
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.
D5.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 follow 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 appears at the bottom of the screen, press the SAVE button.
Option key
Appendix D HA029820
D5.6.1 Choosing the setpoint

In the Program Editor, choose the analog input for which the Hold 09:03:29 SAMPLE 05/04/06
Back properties are to be edited. SP 1
00:06:00
2
00:50:00
3
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
S R R
Ana In 3 to 50.0 to 99.0 to 97.7
The cell highlights, and a dialogue box appears Dig in 1 OPEN CLOSED OPEN
D5.6.2 Changing Holdback mode
09:05:17 SAMPLE 05/04/06

Press the Mode field (yellowed) SP 1
00:06:00
2
00:50:00
3
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
S R R
Ana In 3 to 50.0 to 99.0 to 97.7
DONE
A pick-list appears with None, Low, High, High & Low shown as
modes. 09:05:34 SAMPLE 05/04/06
NONE SP 1 2 3
00:06:00 00:50:00
0 00:35:00
‘None’ means no limits, which means no Hold Back. Ana In 1 S R R
NONE to 50.0
S
to 100.0
R
to
R
0.0
LOW
Ana In 2 to 50.0 to 65.0 to 20.0
‘Low’ specifies a limit below the current setpoint value. If the PV falls HIGH S
Ana In 3 to 50.0
R R
to 99.0 to 97.7
below this limit, then the program will compensate by holding the HIGH&LOW
setpoint steady until the PV has recovered to exceed the limit. Dig in 2 CLOSED OPEN
O CLOSED
DDONE
Dig
i iin 3 OPEN CLOSED
C OPEN
‘High’ specifies a limit above the current setpoint value. If the PV
exceeds this limit, then the program will compensate by holding the
setpoint steady until the PV has fallen below the limit. 09:05:51 SAMPLE 05/04/06
SP 1 2 3
00:06:00 00:50:00 00:35:00
‘High & Low’ sets both limits. Ana In 1 S R R
to 50.0 to 100.0 to 0.0
S R R
Choose the required limit (e.g. LOW). Ana In 2 to 50.0
S
to 65.0
R
to 20.0
R
Ana In 3 to 50.0 to 99.0 to 97.7
It highlights. Dig in 1 OPEN CLOSED OPEN
Press the Return key. Dig in 2 CLOSED OPEN CLOSED
DONE
The picklist disappears. Dig in 3 OPEN CLOSED OPEN
Press DONE.
The dialogue box disappears.
09:06:08 SAMPLE 05/04/06
SP 0 .00:06:00
0 01 0 0 2
00:50:00
3
00:35:00
D5.6.3 Changing Holdback value 7 In 18 S
Ana 9 R R
to 50.0 to 100.0 to 0.0
S R R
Press the Value field (yellowed). 4 5
Ana In 2 to
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 12 3
A numeric keyboard appears, showing the current value in a black Dig in OPEN CLOSED OPEN
confirmation bar at the top. . 0

in 3 OPEN
Dig i DONE
CLOSED OPEN
Key in the required value and press the Return key.
The keyboard disappears.
Press DONE.
The dialogue box disappears.
HA029280 Appendix D
D5.7 CHANGING PROGRAM PROPERTIES

In the Program Editor page, press the SP (Setpoint) cell at top left. The Properties window appears, prompt-
ing for:
Name: 09:06:25 SAMPLE 05/04/06
SP 1 2 3
Rate Units: 00:06:00 00:50:00 00:35:00
S Properties
R
Ana In 1 to 50.0 to 100.0 R
to 0.0
At End: S Name: SAMPLE
Ana In 2 to
R R
50.0 to 65.0 to 20.0
Iterations: Rate SUnits: Minutes
R
Ana In 3 to 50.0 to 99.0
R
to 97.7
At End: Indefinite Dwell
From this screen, the possible tasks are: Iterations: 1
OPEN
DONE
CLOSED OPEN
Dig in 3
To change the name of a program
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.
D5.7.1 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
In the Properties window, press the current name displayed in the yel- SAMPLE
lowed ‘Name’ field. q w e r t y u i o p
A ‘qwerty’ keyboard display, with a cursor flashing under the first a s d f g h j k l ;

character of the current name, shown in a black confirmation bar
above the keyboard. z x c v b n m ,
Key in the new name. IDLE

SAMPLE
??/??/??
0/0
09:06:59 SAMPLE 05/04/06
simple_
When the confirmation bar shows the correct new name (for example,
‘simple’), Press the Return key q w e r t y u i o p
a s d f g h j k l ;
z x c v b n m ,
The keyboard disappears, revealing the Properties window showing

the new name. SIMPLE 0/0
IDLE ??/??/??
09:07:16 simple 05/04/06
SP 1 2 3
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
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
Press DONE At End: Indefinite
Dig in 1 OPEN CLOSED
Dwell
OPEN
Dig in 2 CLOSED DONE
OPEN CLOSED
Appendix D HA029820
D5.7.2 Changing rate units 09:06:33 simple 05/04/06

Seconds
SP 1 2 3
00:06:00 000:50:00 00:35:00
In the Properties window, press the ‘Rate Units’ field. Ana In 1 S Properties
Proper
R R
Seconds to 50.0 to 100.0
S Name: simple
R
to
R
0.0
A pick-list appears with Seconds, Minutes, Hours as selectable op- Minutes

Ana In 2 to 50.0 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
tions. At
Dig in 1 OPEN
End: Indefinite
CLOSED
Dwell
OPEN
DONOPEN
O CLOSED
Select, say, Seconds i 3 OPEN
Di in
Dig CLOSED OPEN
Press Return
09:06:50 simple 05/04/06
SP 1 2 3
00:06:00 00:50:00 00:35:00
S Properties
Ana In 1 to 50.0 R
to 100.0
R
to 0.0
S Name: simple
The Properties window reappears, with the ‘Rate Units’ field showing Ana In 2 to
R
50.0 to 65.0
R
to 20.0
‘Seconds’ Rate
Ana In Units:
S
3 to
Seconds
R R
50.0 to 99.0 to 97.7
At End: Indefinite
Dwell
OPEN
OPEN CLOSED
Press DONE
09:07:07 simple 05/04/06
SP 1 2 3
00:06:00 00:50:00 00:35:00
S
The Program Editor page reappears (rate units are not shown). S
to 100.0
R
to
R
0.0
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 97.7
D5.7.3 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
09:07:24 simple 05/04/06
Indefinite
SP Dwell
1 2 3
This leaves all values as they are at the end of the program, until new 00:06:00 0
00:50:00 00:35:00
Ana In 1 S Properties
Proper
R R
action is taken to change them. A program with an end condition of Indefiniteto 50.0 to 100.0
S Dwell Simple
to 0.0
Ana In 2 toName:
R R
‘Indefinite Dwell’ does not terminate but adopts the COMPLETE state Starting Values50.0 to 65.0 to 20.0
Rate SUnits: Seconds
R R
Ana In 3 to 50.0 to 99.0 to 97.7
until ABORTED. At End: Indefinite
Dwell
OPEN
DON
OPEN
O CLOSED
Ending on an indefinite dwell is the only circumstance that puts a Di i
C OPEN
program into the ‘Complete’ state and the status panel will show
‘COMPLETE’.
Starting values
09:07:41 simple 05/04/06
This ends the program by restoring its starting values. In this case, Starting
SP g Values
1 2 3
00:06:00 0
00:50:00 00:35:00
the program adopts the ‘Idle’ state upon finishing. Ana In 1 S Properties
Proper
R R
Indefiniteto 50.0 to 100.0
S Dwell Simple
to 0.0
Ana In 2 toName:
R R
Starting Values50.0 to 65.0 to 20.0
Rate SUnits: Seconds
R R
Select the required action and press the Return key Ana In 3 to 50.0 to 99.0 to 97.7
At End: Indefinite
Dwell
OPEN
The Properties window reappears showing the selected action and, Dig in 2 CLOSED DONE
DON
OPEN
O CLOSED
below that, the message ‘DONE’. Di i

C OPEN
Press DONE.
The Program Editor page re-appears.
HA029280 Appendix D
D5.7.4 Changing default iterations 09:06:25 SAMPLE 05/04/06

SP 1 6 2
00:06:00 00:50:00
3
00:35:00
7
Ana In 18 to 50.0
S 9 to 100.0
Properties
R R
to 0.0
S Name: SAMPLE
R R
4
Ana
Rate5 SUnits:
In 2 to
6 Minutes
50.0 to 65.0
R
to 20.0
R
Ana In 3 to 50.0 to 99.0 to 97.7
1 At End: Indefinite Dwell
Dig in 12 OPEN 3 CLOSED OPEN
Iterations: 1
. 0
DONE
CLOSED
in 3
Dig i OPEN CLOSED OPEN
In the Properties window, press the current value for iterations
displayed in the ‘Iterations’ field. A numeric keyboard pop-up menu
appears allowing the default number of iterations to be set between 09:06:25 SAMPLE 05/04/06
0 and 999, where ‘0’ results in continuous running. SP 1 2 3
00:06:00 00:50:00 00:35:00
Ana S Properties
R R
In 1 to 50.0 to 100.0 to 0.0
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
D5.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
SIMPLE 0/0
can also be amended (see section D5.6, above). IDLE ??/??/??
09:07:15 simple 05/04/06
SP 1 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
With the program stopped, press the setpoint whose name is to be S R R
Ana In 3 to 50.0 to 99.0 to 97.7
edited - in this example, ‘Ana In 1’ Dig in 1 OPEN CLOSED OPEN
09:07:32 simple 05/04/06

For an analogue setpoint a window is displayed, offering the option 1 2 3
SP
to change Setpoint name and Mode (shown opposite). For a digital 00:06:00 00:50:00 00:35:00
Ana In 1 S R R
setpoint the only editable field is ‘Setpoint name’. to 50.0 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
Press the yellowed field.
Key in the new name, up to a maximum of 16 characters, FOLLOWED DONE
BY ENTER.
09:07:49 simple 05/04/06

SP 1 2 3
00:06:00 00:50:00 00:35:00
S
to 100.0 to 0.0
Press DONE. Ana In 2 S R R
to 50.0 to 65.0 to 20.0
S R R
Ana In 3 to 50.0 to 99.0 to 97.7
DONE
Appendix D HA029820
D5.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.
To change these options, press the LAYOUT button at the bottom of

09:08:06 simple 05/04/06
the Program Editor screen. 1 2 3
SP 00:06:00 00:50:00 00:35:00
Editor RLayout R
Ramp17a StoLong SP to
names:
100.0NOto
The Editor Layout window appears. 50.0 0.0
Ana In 2 S
toSegment
Rstart: NOR
50.0 to 65.0 to 20.0
Segment
S duration:
R YES
R
Ana In 3 to 50.0 to 99.0 to 97.7
Press any field to alternate between YES and NO. Segment finish: NO
Wide cells: NO
The ‘Long SP Names’ field re-formats the display to permit names up Dig in 3 OPEN
DONE
CLOSED OPEN
to 16 characters long, but this will reduce the number of cells visible.
LOAD SAVE SAVE AS NEW LAYOUT
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.
HA029280 Appendix D
D6 THE PANEL NAVIGATION FILE
D6.1 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
parameters 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 applica-
tion.
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
instrument 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 ver-
sion in ROM is used.
Appendix D HA029820
D6.1 THE VERSIONS (Cont.)

====================================
====================================
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
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
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,2090,2070
A2030,STARTUP,,3
A2040,COMMS,,4
A2050,CLOCK,3
A2060,INTERNAT,,4
A2070,PANEL,,2
A2090.TIMEZONE,,4
Programmer
A3000,SPP_MENU,2,3,3,3010
A3010,SPP,2,3,2,3000,1500
HA029280 Appendix D
D6.1 VERSIONS (Cont.)
Security Access
A4000,ACCESS
Logging Submenu
A5000,LOG_MENU,2,,3,5010
A5010,LOG,2,3,2
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
Appendix D HA029820
D6.2 AUDITOR OPTION VERSIONS

====================================
====================================
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
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
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,2090,2070
A2030,STARTUP,,3
A2040,COMMS,,4
A2050,CLOCK,3
A2060,INTERNAT,,4
A2070,PANEL,,2
A2090,TIMEZONE,,4
Admin
A2500,MENU,5,,3,#S1400,#S1401,2510,2520
A2510,NET_AUDIT,5
A2520,SIGN_CFG,5
HA029280 Appendix D
D6.2 AUDITOR PACK VERSIONS (Cont.)
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
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
Appendix D HA029820
APPENDIX E: PROGRAM APPLICATION EDITOR
E1 INTRODUCTION
This section describes how to use the LINTools Program Wizard and the Application Editor, both running on a
pc, to create ‘segment classes’, the use of which is described in section 4.12. It is assumed that an up-to-date
version (4.8 onwards) of LINTools is running on the pc and that a communications link has been successfully
established between the pc and the relevant Visual Supervisor allowing program data to be downloaded. It
is also assumed that an instrument folder has been created (in this example, ‘Eycon41’). Further operational
details are to be found in the Programmer Wizard User Guide and the LIN Programmer Editor User Guide.
E2 BLOCK CREATION
1. In the LINTools ‘Tools’ menu,

select ‘Programmer Wizard’.
2. The ‘PROGCTRL Name’ window opens. If there are exist-

ing blocks, the user can elect to use one of these. For
this example, click on the ‘Make new PROGCNTRL Block’
radio button, and enter (four characters max.) ‘Temp’ as
its name. Click on ‘Next’.
3. In a similar way, select ‘Make new program

Template File’ and enter a name for it (max eight
characters) - in this example ‘Temps’. Click on
‘Next’.
4. Calculate the maximum number of segments

required based on the number of segments
and the number of channels required. For
this example, the value is left at ‘16’.
HA029280 Appendix E
Issue 12 Dec 14 Page E-1
E2 BLOCK CREATION (Cont.)
5. Add the details for all the channels that are to be ‘profiled’ (drawn on the ‘chart’). For the sake of sim-
plicity, this example uses just one.
Click on ‘Next >’.
6. In a similar way, add User Values, Digital Events, and Wait Conditions (ignored for this example). Click on
‘Next >’
7, Select the response to power failure. In this case the default ‘Ramp back’ is used. Click ‘Next >’.
Appendix E HA029280
Page E-2 Issue 12 Dec 14
E2 BLOCK CREATION (Cont.)

8. The Summary Page appears, allowing the user to view the file contents. The ‘< Back’ key can be used to
return to previous pages to edit the entries, if required. Otherwise, the ‘Finish’ key is used to complete
the block creation process for this application.
Note: Any of the Wizard pages can be accesses at any point in the procedure by clicking on the short-
cuts in the left hand column.
Shortcuts
E3 SEGMENT CLASS CREATION
1. At the pc, click on ‘Start’, ‘All Programs’, ‘Eurotherm’, ‘Programmer Editor’, ‘Program Application
Editor’. When the application starts, click on the ‘Open a program template file’ icon in the
tool bar (or use the ‘Open template’ item in the ‘File’ menu, or use the shortcut <ctrl> + <o>).
2. The ‘Open’ browse window appears allowing the user to select the required template file.
HA029280 Appendix E
E3 SEGMENT CLASS CREATION (Cont.)

3. Clicking on the required template file (‘Temps’ for this example) causes the first of the configuration
pages to appear. This allows items which are to apply to the whole program to be set up. It is recom-
mended that as few ‘Do Nothings’ remain as possible.
Notes:
1. If ‘Show in First Segment’ is set to ‘Yes’, then the contents of this page appear in the edit screen for
the first segment.
2. Some blocks, known collectively as ‘Algorithm blocks’ require preset data (e.g. a recipe) or a se-
quence to be loaded at startup. This data is saved in an ‘Algorithm’ file. For such blocks, this page
allows a suitable Algorithm file name to be entered.
3. For all configuration pages, the ‘Visible’ column shows whether each item is always visible (tick),
never visible (cross) or that its visibility depends on the status of other items (?)
4. Click on ‘Application’ in the tree view, then click on ‘Add segment class’. The ‘New Segment Class’ window
opens, allowing the user to set up the configuration for the first segment. The segment Class name may
contain up to 24 characters. The figure below shows the first segment after it has been configured.
Items which are ‘SET’ are not configurable at the visual supervisor. Items which are ‘Ask’ mean that the
user may edit the default value from the Visual Supervisor screen.
Appendix E HA029280
CLASS SETTINGS
SHORT NAME
Initially, the short name is the first eight characters of the segment
name. The ‘Short Name:’ field allows the user to edit this name,
(which is the text that will appear on the segment pushbutton icon in
the Visual Supervisor Edit page).
CHOOSE COLOUR
Allows the user to select a colour for the segment icon in the edit page. Clicking within this area calls a pal-
ette to the display, showing which colours can be selected. As shown below, the various colours are over-
printed with the letter ‘A’ in both black text and white, in order to demonstrate the appearance on the Visual
Supervisor screen. RGB colour definitions are given in the accompanying table.
R = 255 R = 0 R = 128 R = 128 R=0 R = 192 R = 192 R = 164 R = 80 R = 96 R = 112

G = 128 G = 128 G = 128 G = 0 G = 128 G = 192 G = 220 G = 200 G = 80 G = 96 G = 112
B=0 B=0 B=0 B = 128 B = 128 B = 192 B = 192 B = 240 B = 80 B = 96 B = 112
R = 128 R = 144 R = 160 R = 176 R = 192 R = 224 R = 64 R = 64 R = 192 R = 255 R = 128
G = 128 G = 144 G = 160 G = 176 G = 192 G = 64 G = 64 G = 255 G = 128 G = 64 G = 128
B = 128 B = 144 B = 160 B = 176 B = 192 B = 255 B = 255 B = 64 B = 64 B = 64 B = 128
R = 224 R = 144 R = 136 R = 255 R = 255 R = 96 R = 128 R = 255 R=0 R = 255 R=0
G = 144 G = 144 G = 255 G = 176 G = 144 G = 96 G = 128 G = 0 G = 200 G = 0 G = 255
B = 255 B = 255 B = 136 B = 96 B = 144 B = 96 B = 128 B = 0 B=0 B = 255 B = 255
5. Once the various configurable items have been set up for the first segment, click on the ‘Application’
item again and then on ‘Add Segment Class’ again. A second Segment definition page appears. For this
segment. the segment name is to be ‘Maintain Temp’, with a Short Name of ‘Soak’. The segment type
should be sett to ‘Dwell’.
6. The above should be repeated for a third segment, this time with the name ‘Cooling Down’ (Short name =
‘Cool’). Set the Duration to ‘Do Nothing’ and the type to ‘RAMP TIME’.
HA029280 Appendix E
7. With the ‘Cooling Down’ Segment class highlighted, click on ‘Add question.
Enter the text “Cooling Rate?’ as the Question title, then click on ‘Add An-
swer’
The Answer configuration page appears
8. Type ‘Fast’ as the title of the answer. In the configuration area, all the items that were left as ‘Do nothing’
in the Cooling segment type can be edited here. For this example a duration of 30 minutes is entered and
the target setpoint is set to 25 degrees.
9. Click on the question (Cooling Rate?), then on ‘Add Answer’ again.
A similar Answer configuration page to that described above appears, but this time the duration should
be set to 1 hour, and the setpoint again set to 25 deg C. This second answer should be entitled ‘Slow’.
When this segment type is selected for use at the Visual Supervisor, an extra field (Cooling rate?) will
appear as a field in the edit area with the first entered answer on display. Touching the field will cause a
menu to appear containing ‘Fast’ and ‘Slow’.
Multi-layer questions
Note: As shown above, up to three levels of questions can be asked in any one segment, each with up
to 20 answers. Legends for questions and answers can be up to 20 characters in length, but it is recom-
mended that, for a neat appearance, a maximum of 10 characters be used on the small-frame unit.
10. A further segment class should be created which should be called ‘Finished’, with short name ‘End’.
Segment type should be selected as ‘Dwell’.
Figure E3, overleaf, shows the complete example.
Appendix E HA029280
Figure E3 Completed configuration
E4 APPLICATION TEST
Once all the required segments with any questions and answers have been configured the segments can be
‘tested’ by clicking on the ‘Test’ menu bar item, and appending segments to check that they have been cor-
rectly set up. Clicking on the button at the left edge of the screen allows segment data to be displayed in
tabular form. Figure E4a shows the default display with three segments added. Figure E4b shows the display
with tabular data enabled.
Click here to
open table view
Figure E4a Application test default screen
HA029280 Appendix E
E4 APPLICATION TEST (CONT.)
Click here to
close table view
Figure E4b Application test display with tabular detail
Appendix E HA029280
Index A (Cont.)
Symbols Application..........................................................................................E-4
Data.............................................................................................. 4-47
?...............................................................................................................E-4 Cloning................................................................................. 4-47
32-bit register...................................................................................8-18 Importing............................................................................ 4-47
‘>’ sign...................................................................................................8-7 Saving....................................................................................4-19
Deletion...................................................................................... 4-20
A Loading and Running.............................................................. 4-20
Management..............................................................................4-16
Abort.....................................................................................................2-8
Manager page............................................................................4-17
Batch.............................................................................................3-33
Reloading................................................................................... 4-52
Program..............................................................................3-8, D-8
Selection..................................................................................... 4-20
Access.......................................................................................... 2-5, 2-6
Stopping......................................................................... 4-18, 4-50
By user ID....................................................................................2-15
Summary page...........................................................................4-17
Control........................................................................................ 4-24
Unloading....................................................................................4-19
Display pane............................................................................... 2-12
APPLN..................................................................................................4-17
Levels............................................................................................6-11
APP MGR............................................................................................4-17
Pane................................................................................................ 2-2
APP SUM.............................................................................................4-17
Standard...................................................................................... 2-12
Archive................................................................................................3-16
to configuration........................................................................ 2-12
Alarm history.............................................................................3-17
Account Properties........................................................................ 4-30
Export...........................................................................................3-13
ACK......................................................................................................3-16
Interval.........................................................................................4-13
Acknowledge
Area......................................................................................................3-15
Alarms..........................................................................................3-16
Display..........................................................................................3-19
Messages.....................................................................................3-16
Arhive file transfer............................................................................ 7-1
Action Disabled................................................................................6-11
ASCII....................................................................................................3-12
Add Answer.........................................................................................E-6
Codes..............................................................................................C-1
Adding
File type.......................................................................................4-13
New segments............................................................................ 4-4
Assigning
New users................................................................................... 4-30
Card readers to ports..............................................................12-6
Add question......................................................................................E-6
Printers to ports........................................................................12-2
Address Assignment...................................................................... 4-35
Attributes column.......................................................................... 4-29
Add segment class.............................................................................E-4
Audit Trail............................................................................................6-1
Admin only....................................................................................... 4-29
Filtering..........................................................................................6-2
Advance...................................................................................... 2-8, 3-5
Agent types.......................................................................................5-51
Alarms.................................................................. 2-5, 2-6, 3-15, 8-11
B
Acknowledgement........................................................2-11, 3-16 BadBatt................................................................................................. 1-2
Active/Cleared/Ack'ed..............................................................6-2 Barcode Reader option.................................................................. 12-1
and event customisation........................................................5-32 Bargraph display mode
and event objects.....................................................................12-5 Horizontal bars..........................................................................3-24
Delay...............................................................................................4-7 Vertical bars.............................................................................. 3-23
Display pane.................................................................................2-9 Batch.......................................................................................... 2-6, 3-10
Field................................................................................................8-7 Abort............................................................................................3-33
Forms........................................................................................... 5-60 Create.......................................................................................... 3-34
History..........................................................................................2-10 Customising................................................................................3-32
Archiving..............................................................................3-17 Dictionary.................................................................................. 5-66
Display, addding notes to................................................3-16 Files.............................................................................................. 5-66
Page........................................................................................3-14 Hold..............................................................................................3-33
Time display........................................................................3-14 ID.....................................................................................................3-2
Two-line display......................................................2-11, 3-15 Initiation......................................................................................3-33
Indication....................................................................................3-19 Load..............................................................................................3-32
Key.................................................................................................3-10 Maintenance.............................................................................. 4-56
Log.................................................................................................8-11 Monitoring..................................................................................3-33
Names......................................................................................... 5-54 Phases.......................................................................................... 5-68
Pane................................................................................................ 2-2 Recipe selection........................................................................3-32
Responding to............................................................................3-14 Battery
Status..............................................................................................2-9 Replacement................................................................................9-1
Summary.....................................................................................3-17 Type............................................................................................... A-1
Algorithm file......................................................................................E-4 Baud rate............................................................................................8-14
ALL.......................................................................................................3-15 Bitfields.................................................................................................8-7
HA029280 Index
Issue 12 Dec 14 Page - i
Block (Cont.) C (Cont.)

Block..........................................................................................3-15, 8-4 Database........................................................................................8-3
Copy............................................................................................... 8-8 Modbus........................................................................................8-12
Creation...................................................................................... 4-22 Configurator
Delete............................................................................................ 8-8 Control...........................................................................................8-1
Events.............................................................................................6-2 Mode, selecting...........................................................................8-1
Inspect............................................................................................8-9 Running..........................................................................................8-2
Overview...................................................................................... 8-4 Confirm only.....................................................................................6-11
Tagname........................................................................................8-5 Connections............................................................................. 8-6, 8-8
Type................................................................................................8-5 Types.............................................................................................. 8-8
Value Change...............................................................................6-2 Consumer selection..........................................................................6-2
BootP.................................................................................................. 4-35 Continuous database resources................................................... A-2
+LL................................................................................................ 4-35 Control
Brightness of display......................................................................4-44 Configurator.................................................................................8-1
Brown-out......................................................................................... 4-37 Database..................................................................................... 4-47
Time............................................................................................. 4-38 Selecting efficiency....................................................................8-1
Copy blocks........................................................................................ 8-8
C Count...................................................................................................8-16
Create
Cached alarms....................................................................................6-2 Batch............................................................................................ 3-34
Calibration Blocks.......................................................................................... 4-22
Touch screen................................................................................9-2 Cross......................................................................................................E-4
CANCEL...............................................................................................6-11 ctrl shortcuts.......................................................................................8-2
Capture (recipe).............................................................................. 4-54 Cursor..........................................................................3-25, 3-27, 4-62
Changing Customising.........................................................................................5-1
a segment...................................................................................D-16 Panel............................................................................................ 5-29
Date/Time.................................................................................. 4-39 Cycles.....................................................................................................4-9
Date/Time format................................................................... 4-41
from Access level to User ID................................................ 4-27 D
Hot/Cold Start settings.......................................................... 4-38
Language.................................................................................... 4-41 Daily.....................................................................................................3-12
Setpoint value........................................................................... D-15 File names...................................................................................4-13
Start-up Strategy values........................................................ 4-38 Files...............................................................................................3-12
Time-out values....................................................................... 4-38 Database
Channel Change audit trailing...............................................................5-75
Name..............................................................................................4-5 Name & address..........................................................................8-9
Character set.......................................................................................C-1 Names................................................................................5-2, 5-53
Choose colour....................................................................................E-5 Resources..................................................................................... A-2
Clock Data Entry pop-up size................................................................. 4-45
Accuracy....................................................................................... A-1 Data integrity....................................................................................3-13
Clock configured as SNTP client................................................ 4-36 Date
Clock Setup page............................................................................ 4-39 Format..........................................................................................4-13
Cloning...............................................................................................4-46 Format selection...................................................................... 4-41
All data........................................................................................ 4-49 Daylight saving................................................................................ 4-39
Application data....................................................................... 4-47 DB Write.............................................................................................8-18
Instrument data.......................................................................4-48 Decimal point.................................................................................... 8-6
System data...............................................................................4-48 Default.................................................................................... 4-57, 6-11
Cold start...............................................................................4-37, 4-38 Gateway...................................................................................... 4-35
Column Titles....................................................................................4-13 Delete......................................................................................4-16, 4-20
Commission level access............................................................... 4-25 Blocks............................................................................................ 8-8
Communications............................................................................. 4-32 Segment............................................................................ 4-4, 4-61
Available protocols................................................................. 4-33 Segments....................................................................................D-18
Parameter setting.................................................................... 4-32 User IDs...................................................................................... 4-29
Profiles........................................................................................ 4-47 Deploy...................................................................................................6-7
Setup............................................................................................8-13 Detail.................................................................................................. 4-61
Specification................................................................................A-4 Deviation Alarms...............................................................................4-7
Compact Flash (CF) card precautions......................................... 1-2 Device................................................................................................. 4-51
Compound...........................................................................................8-5 DHCP.................................................................................................. 4-35
Compressed Events...............................................................4-8, 4-10 +LL................................................................................................ 4-35
Configuration Diagnostic..........................................................................................8-15
Index HA029280
Page - ii Issue 12 Dec 14
D (Cont.) E (Cont.)
Dictionary Text dictionary..........................................................................5-33
Batch............................................................................................ 5-66 ESC/P...................................................................................................12-3
Database names....................................................................... 5-54 Ethernet............................................................................................. 4-34
Error text.....................................................................................5-33 Connection...................................................................................1-8
Event text................................................................................... 5-35 LED interpretation.....................................................................A-4
List of..............................................................................................5-1 Events..................................................................................................3-15
Programmer text.....................................................................5-40 Log..................................................................................... 3-18, 8-11
System text......................................................................... 5-2, 5-3 Message
User text..................................................................................... 5-40 Editing.................................................................................. 5-39
Dictionary text.................................................................................5-71 New language.................................................................... 5-39
Digital...................................................................................... 8-15, 8-17 Priorities..................................................................................... 5-39
Digital Events...................................................................................... E-2 Status............................................................................................. 4-8
Directory:...........................................................................................4-16 Text dictionary......................................................................... 5-35
Disable User ID...................................................................... 4-29, 6-4 Exit......................................................................................................... 4-8
Display Export
Brightness..................................................................................4-44 Application data....................................................................... 4-47
Group.......................................................................................... 3-34 Export (All).................................................................................3-13
Mode........................................................................................... 3-22
Bargraph F
Horizontal................................................................3-24
Vertical...................................................................... 3-23 Faceplates...........................................................................................3-10
Faceplate............................................................................. 3-23 Display mode............................................................................ 3-23
Horizontal full width.........................................................3-27 FEATT.................................................................................................... A-2
Horizontal with faceplate................................................3-26 Field.....................................................................................................8-17
Numeric............................................................................... 3-23 File....................................................................................................... 4-51
Vertical fullwidth...............................................................3-26 Copy and delete....................................................................... 4-51
Vertical with faceplate.....................................................3-24 Filename specification............................................................8-10
Down key..............................................................................................2-3 Header............................................................................. 5-61, 5-67
Downloading a configuration........................................................8-1 Manager...................................................................................... 4-49
DP.........................................................................................................8-18 Name................................................................................3-34, 4-13
DR_ALARM block............................................................................12-5 System............................................................................................ 7-1
DR_REPRT block..............................................................................12-5 Type..............................................................................................4-13
Dwell................................................................................................... D-13 Text, Hourly, Daily, Sequence........................................3-12
End condition...............................................................................4-5 Utility............................................................................................8-11
Segmet type................................................................................ 4-6 Files with Capture Variables........................................................ 5-63
Files with Monitor Variables....................................................... 5-64
E Filter.................................................................................................... 4-51
Fixed................................................................................................... 4-35
EDB........................................................................................................ A-2 F keys.....................................................................................................2-3
Edit...............................................................................................2-8, 3-6 Flash card precautions..................................................................... 1-2
Alarm names............................................................................. 5-54 Flush-mounting option.................................................................. 11-1
Databases......................................................................................8-5 Format..................................................................................... 8-11, 8-18
Error messages......................................................................... 5-34 Formatting attributes.................................................................... 5-73
Event messages......................................................................... 5-39 Form files.......................................................................................... 5-55
Function block names............................................................ 5-54 Forms.................................................................................................. 4-47
Own Expired Password............................................................. 6-6 FTP............................................................................................3-13, 4-29
Recipes........................................................................................ 4-52 Logon.............................................................................................. 7-1
E:Eycon_10.DBF................................................................................8-10 Timeout......................................................................................... 7-1
EIA485 connection............................................................................ 1-7 Transfer........................................................................................4-15
Electrical installation........................................................................1-6 Function block
Profibus Master units............................................................. 10-4 Database configuration............................................................8-3
Electronic signatures......................................................................6-10 Detail display............................................................................. 4-24
Empty Strings....................................................................................5-70 Display order............................................................................. 4-23
Enabled...............................................................................................4-15 Faceplate.....................................................................................3-21
Encrypted files................................................................................. 4-55 PID......................................................................................... 3-22
End condition................................................................4-5, 4-9, D-21 Ramp......................................................................................3-21
Engineer level access..................................................................... 4-25 Manager.......................................................................................4-21
Enumerations........................................................................5-55, 5-72 Names......................................................................................... 5-54
Error Function blocks supported........................................................... A-5
Message editing....................................................................... 5-34 Functions............................................................................................8-16
HA029280 Index
Issue 12 Dec 14 Page - iii
G I (Cont.)
Glossary................................................................................................C-2 IP rating............................................................................................... A-1
Go back to.......................................................................................... 4-4 Flush mounting option........................................................... 11-5
Group..................................................................................................3-15 IPRP..................................................................................................... 4-55
Display..........................................................................................3-19 Iterations
GWF files............................................................................................10-1 Changing default number.....................................................D-22
GW index............................................................................................8-12
GWProfM_CON block................................................................... 10-4 J
Jog buttons..........................................................................................4-1
H
Hb & Alarm L
Mode..............................................................................................4-5 Labelling symbols.............................................................................. 1-1
Value...............................................................................................4-7 Language selection......................................................................... 4-41
HELD....................................................................................................3-21 Large
Hexadecimal fields............................................................................8-7 DB................................................................................................. 4-57
High Limit.............................................................................................4-5 SFC................................................................................................ 4-57
HISTDATA block...............................................................................12-5 LD+RUN..................................................................................4-16, 4-20
HOLD.....................................................................................................2-8 LED indicators (RJ45)........................................................................ 1-7
Holdback............................................................................................3-21 Left key.................................................................................................2-3
and alarms....................................................................................4-7 Legacy programmer............................................................. 4-57, D-1
Properties...................................................................................D-18 LIN database variables...................................................................5-71
Type................................................................................................4-7 Line feed Space................................................................................12-3
Value.............................................................................................3-21 Line type.............................................................................................8-14
Home page declaration.................................................................5-51 LINfiler..................................................................................................8-3
HOME/USER SCREENS......................................................................2-6 Link Local.......................................................................................... 4-35
Horizontal trend display mode LIN (Local Instrument Network)...................................................8-9
Full width....................................................................................3-27 Lin Mode..............................................................................................6-2
with faceplates..........................................................................3-26 Literal text..........................................................................................5-70
Host.............................................................................. 4-15, 4-35, 12-3 Load................................................................... 3-32, 4-9, 4-16, 4-20
Hot start.................................................................................4-37, 4-38 Utility............................................................................................8-10
Time............................................................................................. 4-38 Load/Save program Id setting...................................................... D-2
Hourly..................................................................................................3-12 Locked................................................................................................ 4-25
File names...................................................................................4-13 Logging..................................................................................... 2-6, 3-12
Files...............................................................................................3-12 Configuration.............................................................................4-13
Data groups................................................................................4-12
I File type.......................................................................................4-13
Identity................................................................................................. 6-4 Group.......................................................................................... 3-34
Id value................................................................................................ D-2 Initiation......................................................................................4-12
Importing application data.......................................................... 4-47 Interval.........................................................................................4-13
Information entry..............................................................................2-5 Manage........................................................................................3-13
Initial Name types................................................................................4-13
Menu..............................................................................................8-2 Pane.....................................................................................2-2, 2-12
Page declaration.......................................................................5-51 Report......................................................................................... 3-34
Input..................................................................................................... 8-6 Logic states..........................................................................................8-7
Inrush current.....................................................................................1-6 LOG NOW...........................................................................................4-14
Inserting segment........................................................................... D-17 Log on................................................................................................. 2-12
Insert segment....................................................................... 4-4, 4-61 Long SP names..................................................................................4-10
Inspect blocks.....................................................................................8-9 Low limit...............................................................................................4-5
Installation
Electrical........................................................................................1-6 M
Profibus Master units...................................................... 10-4 MAC ADDRESS................................................................................. 4-35
Mechanical.................................................................................... 1-3 Main pane...................................................................................2-2, 2-5
Flush mounting option.................................................... 11-1 Maintenance (security access)...................................................... 6-6
Profibus Master units.......................................................10-2 MAINT key...............................................................................4-31, 6-6
Instr No...................................................................................8-14, 8-16 Make..................................................................................................... 8-4
Instrument........................................................................................ 4-35 Manage...............................................................................................3-13
Data cloning..............................................................................4-48 Master Access.................................................................................... 6-6
Setting up................................................................................... 4-32 Master/Slave
Intellectual Property Right Protection..................................... 4-55 Connection................................................................................... 1-7
I/O calibration..................................................................................8-10 Selection........................................................................................ 1-7
IP Address......................................................................................... 4-35
Index HA029280
Page - iv Issue 12 Dec 14
M (Cont.) O (Cont.)
Maximum Option
Number of questions/answers...............................................E-6 Key...................................................................................................2-3
Number of segments................................................................. E-1 Keys.................................................................................................4-9
Max. Login attempts........................................................................ 6-6 Options
Mechanical installation.................................................................... 1-3 Menu fields.................................................................................. 8-6
Flush mounting option........................................................... 11-1 Moving to another instrument............................................... 1-2
Profibus Master units..............................................................10-2 Update...........................................................................................B-1
Menu key..............................................................................................2-3 Overlay recommendations........................................................... 11-5
Message............................................................................................. 3-34 Overview..............................................................................................2-6
Active/Cleared/Ack'ed..............................................................6-2 Data field entry...........................................................................8-5
Display/Acknowledge..............................................................3-16
Indicator......................................................................................2-10 P
Minimum
Alarm/event priority.................................................................6-2 Page Format......................................................................................12-3
ID length....................................................................................... 6-6 Palette.................................................................................................12-3
Password length......................................................................... 6-6 Pan control........................................................................................3-25
MODBUS Panel
Configuration.............................................................................8-12 Agent declaration.................................................................... 5-49
Connection................................................................................... 1-7 Customisation........................................................................... 5-29
Data tables...................................................................................A-4 Driver declaration................................................................... 5-50
Mapping table........................................................................... 4-35 Navigation.........................................................................5-2, 5-41
/TCP............................................................................................. 4-35 File......................................................................................... 5-41
MOD Write........................................................................................8-19 Navigation file..........................................................................D-24
Monitor......................................................................... 2-8, 4-10, 4-14 Parameter
A program..............................................................3-9, D-9, D-10 Database........................................................................................8-5
Moving options to another instrument...................................... 1-2 Units.............................................................................................. 8-6
MSGS...................................................................................................3-15 Values............................................................................................ 8-6
Multiple copy....................................................................................4-15 Parity...................................................................................................8-14
Password.............................................................................................4-15
N Editing......................................................................................... 4-24
Expiry....................................................................................6-5, 6-6
Name type............................................................................. 3-12, 4-13 PCL3.....................................................................................................12-3
Navigation keys..................................................................................2-3 PerProg.................................................................................................4-5
Network................................................................................................8-9 PerSeg...................................................................................................4-5
Audit Trail.....................................................................................6-1 Plot........................................................................................... 3-10, 3-11
FB manager key........................................................................ 4-22 P1/P2.............................................................................................12-4
Setup page....................................................................................8-9 Pop-up menu......................................................................................2-6
Specification................................................................................A-4 Port......................................................................................................12-3
New........................................................................................................4-9 no...................................................................................................8-14
Program...................................................................................... 4-61 Power
Creation............................................................................... 4-59 Fail Recovery................................................................................ E-2
Segment........................................................................................ 4-4 Power requirements.........................................................................1-6
User ID...............................................................................4-30, 6-5 Preventive maintenance.................................................................. 1-2
New Segment Class...........................................................................E-4 Preview..................................................................2-8, 3-7, 3-11, 4-10
No Confirmation..............................................................................6-11 PREVIEW............................................................................................ 4-62
Node................................................................................................... 4-51 Print Columns...................................................................................12-3
/Loop............................................................................................3-21 Printer
N................................................................................................... 4-35 Option.......................................................................................... 12-1
Number configuration............................................................. 6-8 Parameters..................................................................................12-3
No. of characters............................................................................ 5-73 Process value.....................................................................................3-21
Number of nodes........................................................................... 4-35 Profibus
Numeric display mode.................................................................. 3-23 Master option............................................................................10-1
Connector Pinout............................................................. 10-4
O GWProfM_CON block..................................................... 10-4
Specification................................................................................A-4
Offset..................................................................................................8-16 Profiled channels............................................................................... E-2
OOB alarm...........................................................................................4-7 PROGCTRL Name............................................................................... E-1
Operator Program................................................................................................2-8
Access level................................................................................ 4-25 Abort...................................................................................3-8, D-8
Note................................................................................................6-2 Application editor..........................................................4-58, E-1
Changing the name of............................................................D-20
Creation.................................................................4-2, 4-59, D-11
HA029280 Index
Issue 12 Dec 14 Page - v
Program (Cont.) Recipe (Cont.)

Duration (maximum).............................................................. D-17 Monitoring................................................................................. 3-30
Editing................................................................... 4-2, 4-63, D-11 Pane................................................................................................ 2-2
Editor, Access to............................................................ 4-3, D-12 Saving.......................................................................................... 4-54
End action..................................................................................D-21 Value............................................................................................ 4-53
Hold.....................................................................................3-8, D-8 Recovery Account............................................................................. 6-6
Monitoring a..................................................................... 3-9, D-9 Redo.......................................................................................................2-8
Name..............................................................................................4-9 Reference column.......................................................................... 4-29
New.............................................................................................. 4-61 Refresh rate.........................................................................................8-5
Pane.......................................................................................2-2, 2-7 Register................................................................................... 8-15, 8-17
Profile.............................................................................................3-9 REINSTATE key................................................................................... 6-4
Properties...................................................................................D-20 Remote
Running......................................................................................... D-1 Access............................................................................................. 7-1
From a point......................................................................... D-3 Device...........................................................................................8-11
From date.............................................................................. 3-4 Report forms.................................................................................... 5-56
Running more than one..................................................3-2, D-2 Reports...............................................................................................12-5
Schedule..................................................................................... 4-63 Reset......................................................................................................2-8
Scheduling......................................................................... 3-3, D-4 End condition...............................................................................4-5
Segments....................................................................................... E-1 Retire User ID.................................................................................... 6-4
Status.............................................................................................. 2-7 Review mode....................................................................................D-10
Template File................................................................................ E-1 Revision................................................................ 3-7, 4-10, 4-15, 6-7
Time remainiing........................................................................3-10 REVISION........................................................................................... 4-61
Programmer.....................................................................2-5, 2-6, 3-1 Right key...............................................................................................2-3
Menu..............................................................................................2-8 Root page declaration....................................................................5-51
Access...................................................................................... 2-7 RUN........................................................................................................2-8
Text dictionary.........................................................................5-40 Running...............................................................................................3-21
Programs........................................................................................... 4-62 A program.................................................................................... D-1
Programs/Recipes........................................................................... 4-47 Multiple programs............................................................3-2, D-2
Properties.............................................................................................4-9
Key.................................................................................... 4-30, 4-61 S
Protocol..............................................................................................12-3
Communications...................................................................... 4-33 Safety notes......................................................................................... 1-1
Name........................................................................................... 4-35 Save.........................................................4-9, 4-14, 4-16, 4-19, 6-11
PV...........................................................................................................4-5 Utility............................................................................................8-10
Start......................................................................................4-5, 4-9 Save as...................................................................................................4-9
Scan count.........................................................................................8-16
Q Schedule...................................................................................2-8, 4-10
A program.......................................................................... 3-3, D-4
Question, add.....................................................................................E-6 SCHEDULE......................................................................................... 4-63
Question mark..................................................................................2-10 Screen saver configuration..........................................................4-44
Question mark symbol....................................................................E-4 Security access page.........................................................................6-3
Segment
R Changing duration of............................................................. D-17
Changing the identifier..........................................................D-16
Ramp.................................................................................................. D-13 Class creation............................................................................... E-3
Ramp at....................................................................................... D-13 Classes......................................................................................... 4-58
Ramp to...................................................................................... D-13 Delete................................................................................ 4-4, 4-61
Type changing........................................................................... D-13 Deletion of.................................................................................D-18
Ramprate segments......................................................................... 4-6 Detail........................................................................................... 4-61
Ramptime segments........................................................................ 4-6 Duration..................................................................4-4, 4-6, 4-10
Ramp-to value..................................................................................3-21 Editing.........................................................................................D-16
Rate ms.................................................................................................8-5 Finish.............................................................................................. 4-4
Rate units................................................................................ 4-5, D-21 Insert................................................................................. 4-4, 4-61
Selection.....................................................................................D-21 Insertion..................................................................................... D-17
Reader option................................................................................... 12-1 Name........................................................................3-10, 4-4, 4-6
Recipe.......................................................................................... 2-5, 2-6 New Class......................................................................................E-4
Adding / Deleting.................................................................... 4-53 Properties................................................................................... 4-61
Capture....................................................................................... 4-54 Skip.......................................................................................3-5, D-7
Dictionary.................................................................................. 5-65 Start....................................................................................4-4, 4-10
Downloading..............................................................................3-28 Time remaining.........................................................................3-10
File properties.......................................................................... 4-54 Timing display...........................................................................D-23
Files.............................................................................................. 5-61 Transition......................................................................................3-5
Management............................................................................. 4-52 Type............................................................................................... 4-6
Index HA029280
Page - vi Issue 12 Dec 14
S (Cont.) System (Cont.)

Sequence................................................................................ 3-12, 4-13 Summary Page.............................................................................2-4
Control resources...................................................................... A-3 Text
Serial comms connection................................................................ 1-7 Editing.....................................................................................5-3
Serial master/slave..........................................................................8-13 New languages......................................................................5-3
Server number....................................................................................8-5 Text dictionary............................................................................5-3
Servo......................................................................................................4-5 System variables.............................................................................. 5-72
Servo to............................................................................................. D-13
Setpoint T
Edit.........................................................................4-6, D-13, D-15
Name T500 LINtools......................................................................................8-1
Changing..............................................................................D-22 Table....................................................................................................8-15
Setting Menus...........................................................................................8-17
Passwords................................................................................... 4-25 Tag references................................................................................. 4-53
Start-up strategy...................................................................... 4-37 Talk through..................................................................................... 4-34
SETUP................................................................................................. 4-32 Target................................................................................................... 4-6
SFCs..................................................................................................... 4-47 TCP
Short name..........................................................................................E-5 Master/slave...............................................................................8-13
Show in First Segment.....................................................................E-4 Port.............................................................................................. 4-35
Signature............................................................................................6-11 TEATT................................................................................................... A-2
Configuration.............................................................................6-11 Template File....................................................................................... E-1
Sign & Authorise..............................................................................6-11 Terminal
Single copy.........................................................................................4-15 Configurator
Single Copy........................................................................................4-15 Modbus Configuration
Size...................................................................................................... 4-51 TABLES command...................................................8-15
Skip........................................................................................................2-8 Mode..............................................................................................8-2
Slave Test......................................................................................................... E-7
Address....................................................................................... 4-35 Text......................................................................................................3-12
Connection................................................................................... 1-7 Files...............................................................................................3-12
Software options utility...................................................................B-1 Names...................................................................................4-13
SP............................................................................................................4-5 Only...............................................................................................12-3
Specification Tick.........................................................................................................E-4
Battery.......................................................................................... A-1 Tick Rate.............................................................................................8-16
Communications........................................................................A-4 Time
General......................................................................................... A-1 Display in Alarm history.........................................................3-14
Profibus.........................................................................................A-4 Format......................................................................................... 4-41
RTC................................................................................................. A-1 Synchronisation........................................................................ 4-36
USB.................................................................................................A-4 Units.............................................................................................3-21
Standard Zone............................................................................................. 4-42
Access........................................................................................... 2-12 Timeout..............................................................................................8-14
Interface...............................................................................2-1, 2-5 Display brightness................................................................... 4-45
START......................................................................................4-16, 4-20 Page Display..............................................................................4-44
Start/Stop utilities...........................................................................8-10 Pop-up menu............................................................................4-44
Startup Strategy.............................................................................. 4-37 Title
STATS key.................................................................................4-31, 6-6 Bar...................................................................................................8-5
Status indicators..............................................................................3-21 Line............................................................................................... 5-62
Step..................................................................................................... D-13 Touch screen calibration.................................................................9-2
Segments...................................................................................... 4-6 Transparent Modbus access........................................................ 4-34
Stop..........................................................................................4-16, 4-18 Transpose...........................................................................................4-10
Bits................................................................................................8-14 Trends..................................................................................................12-5
Subnet Mask..................................................................................... 4-35 Displays........................................................................................3-19
Summary Page.................................................................................... E-3 Review..............................................................................3-25, 3-27
Supply voltage Two-line display (Event Log)........................................................3-18
Requirements...............................................................................1-6 Type.....................................................................................................8-15
Wiring.............................................................................................1-6 of block..........................................................................................8-5
Switch on.............................................................................................. 2-1
Symbols used on labels................................................................... 1-1 U
System.................................................................. 2-5, 2-6, 4-17, 4-32 UHH.....................................................................................................3-12
Data File type.......................................................................................4-13
Cloning.................................................................................4-48 Unit..........................................................................................3-11, 4-61
Importing/exporting.......................................................4-48 UNLOAD.................................................................................4-16, 4-19
Event...............................................................................................6-2 Unpacking............................................................................................ 1-3
HA029280 Index
Issue 12 Dec 14 Page - vii
U (Cont.) UYT files............................................................................................ 5-60

Flush mounting option........................................................... 11-1
V
Unused................................................................................................8-15
UPB files..............................................................................................10-1 Value....................................................................................................8-19
Update period....................................................................................8-5 Variable lines (Recipe files)......................................................... 5-62
Up key...................................................................................................2-3 VDU package, quitting.....................................................................8-3
USB2, USB3........................................................................................ 12-1 Vertical display mode
USB connectors..................................................................................1-8 Full width....................................................................................3-26
User With faceplate...........................................................................3-24
Attributes......................................................................................6-5 View only........................................................................................... 4-29
Defined keys.................................................................................2-3 Views...................................................................................... 4-10, 4-61
Defined names.............................................................................8-5 VIEWS................................................................................................. 4-61
ID Visible column....................................................................................E-4
Access....................................................................................2-15 Voltage range......................................................................................1-6
Control....................................................................................6-3 VT100 mode........................................................................................8-2
Management...................................................................... 4-28
Password system............................................................... 4-27 W
Name..................................................................................4-15, 6-4
Pages............................................................................................ 4-47 Wait....................................................................................................... 4-8
Properties..................................................................................... 6-6 Wait Condition................................................................................... E-2
Text dictionary.........................................................................5-40 Wide Cells..........................................................................................4-10
Timeout........................................................................................ 6-6 Width...................................................................................................8-18
Value...............................................................................................4-7 Wild-card character........................................................................8-11
Values............................................................................................. E-2 Wiring
User actions.......................................................................................5-74 Ethernet.........................................................................................1-8
Utilities................................................................................................8-10 Profibus Master units............................................................. 10-4
UXM file............................................................................................. 4-47 Serial comms................................................................................ 1-7
UYB files............................................................................................ 5-66 Supply voltage.............................................................................1-6
UYF files................................................................................. 3-34, 5-57 to I/O units...................................................................................1-9
UYN file size limits........................................................................... A-3 Writable dictionary........................................................................ 5-64
UYR files................................................................................ 5-61, 5-66
Z
Zoom control....................................................................................3-25
Index HA029280
Page - viii Issue 12 Dec 14
Inter-Company sales and service locations
AUSTRALIA Melbourne GERMANY Limburg SPAIN Madrid
Invensys Process Systems Australia Invensys Systems GmbH Eurotherm España SA
Pty. Ltd. >EUROTHERM< T (+34 91) 661 6001
T (+61 0) 8562 9800 T (+49 6431) 2980 F (+34 91) 661 9093
F (+61 0) 8562 9801 F (+49 6431) 298119 E info.eurotherm.es@invensys.com
E info.eurotherm.au@invensys.com E info.eurotherm.de@invensys.com
SWEDEN Malmö
INDIA Mumbai Eurotherm AB
AUSTRIA Vienna T (+46 40) 384500
Eurotherm GmbH Invensys India Pvt. Ltd.l
T (+91 22) 6757 9800 F (+46 40) 384545
T (+43 1) 7987601
F (+91 22) 6757 9999 E info.eurotherm.se@invensys.com
F (+43 1) 7987605
E info.eurotherm.at@invensys.com E info.eurotherm.in@invensys.com
SWITZERLAND Wollerau
Eurotherm Produkte (Schweiz) AG
IRELAND Dublin
BELGIUM & LUXEMBOURG Moha T (+41 44) 787 1040
Eurotherm Ireland Limited
Eurotherm S.A/N.V. F (+41 44) 787 1044
T (+353 1) 469 1800
T (+32) 85 274080 E info.eurotherm.ch@invensys.com
F (+353 1) 469 1300
F (+32 ) 85 274081
E info.eurotherm.ie@invensys.com
E info.eurotherm.be@invensys.com
UAE DUBAI
Invensys Middle East FZE
ITALY Como T (+971 4) 807 4700
BRAZIL Campinas-SP Eurotherm S.r.l F (+971 4) 807 4777
Eurotherm Ltda. T (+39 031) 975111 E marketing.mena@invensys.com
T (+5519) 3112 5333 F (+39 031) 977512
F (+5519) 3112 5345 E info.eurotherm.it@invensys.com
E info.eurotherm.br@invensys.com UNITED KINGDOM Worthing
Eurotherm Limited
KOREA Seoul T (+44 1903) 268500
CHINA Invensys Operations Management Korea F (+44 1903) 265982
Eurotherm China T (+82 2) 2090 0900 E info.eurotherm.uk@invensys.com
Shanghai Office F (+82 2) 2090 0800
T (+86 21) 6145 1188 E info.eurotherm.kr@invensys.com
U.S.A Ashburn VA
F (+86 21) 6145 2602
Invensys Eurotherm
E info.eurotherm.cn@invensys.com
NETHERLANDS Alphen a/d Rijn T (+1 703) 724 7300
Eurotherm B.V. F (+1 703) 724 7301
Beijing Office
T (+31 172) 411752 E info.eurotherm.us@invensys.com
T (+86 10) 5909 5700
F (+86 10) 5909 5709/10 F (+31 172) 417260
ED69
E info.eurotherm.cn@invensys.com E info.eurotherm.nl@invensys.com
POLAND Katowice
FRANCE Lyon Invensys SYSTEMS Sp z o.o
Eurotherm Automation SA T (+48 32) 783 9500
T (+33 478) 664500 F (+48 32) 784 3608 / 784 3609
F (+33 478) 352490 E info.eurotherm.pl@invensys.com
E info.eurotherm.fr@invensys.com
Warsaw
Invensys Systems Sp z o.o
T (+48 22) 855 6010
F (+48 32) 855 6011
E biuro@invensys-systems.pl
HA029280/12 (CN32524)

5ha029280 - 12 - 00 2

Uploaded by

Copyright:

Available Formats

5ha029280 - 12 - 00 2

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

5ha029280 - 12 - 00 2

Uploaded by

Copyright:

Available Formats

PAC Systems

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

LIST OF CONTENTS (Cont.)

LIST OF CONTENTS (Cont.)

LIST OF CONTENTS (Cont.)

LIST OF CONTENTS (Cont.)

SYMBOLS USED ON THE EQUIPMENT LABELLING

Protective-conductor USB connector

This instrument Serial communications

Precautions against static elec- For environmental reasons, this

COMPACT FLASH (CF) CARD PRECAUTIONS

The following ‘rules’ should therefore be observed:

1.2 MECHANICAL INSTALLATION

1.2 MECHANICAL INSTALLATION (Cont.)

Right-hand side view

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

5 wire 5 wire 3-Wire

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 Connectors

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

2.1 SWITCH-ON AND THE OPENING DISPLAY

2.1.2 The standard interface

* no application loaded *