Professional Documents
Culture Documents
Version 4.1
Configuration Manual
Configuration Manual
Release:
Document number:
Oct 2007
9AKK101130D1382
TRADEMARKS
Registrations and trademarks used in this document include:
Acrobat
Adobe
Advant
AdvaBuild
Industrial IT
Microsoft
Windows
Note 1: 87
Command Parameters 89
Alarm Processing Parameters 89
Alarm Level Parameters 96
Alarm Option Parameters 96
Alarm Comment Parameters 96
Network Parameters 98
OPC Parameters 100
Totalization Parameters 104
Device Status Parameters 104
Documentation Parameters 104
Hardware Description Parameters 105
Application Parameters 109
Digital Tag Definition 113
General Parameters 114
Process Parameters 117
Generic Scanner Input Parameters 118
Generic Scanner Output Parameters 119
Symphony Input Parameters 119
Command Parameters 121
Alarm Processing Parameters 123
Alarm Level Parameters 123
Alarm Option Parameters 123
Alarm Comment Parameters 123
Network Parameters 124
OPC Parameters 124
Totalization Parameters 125
Device Status Parameters 126
Documentation Parameters 129
Hardware Description Parameters 129
Application Parameters 129
Analog Tag Definition 129
General Parameters 129
Process Parameters 134
Generic Scanner Input Parameters 135
Functionality 435
Master/Slave 436
Real-time Utilities 437
Distributed Architecture 439
Introduction 439
Assumptions 441
Server Functions 442
On-line Features 442
Initialization Features 443
Client Functions 444
ALIGNSPECS Program 444
Tables 469
Tag Types 469
Tag Sources 471
Default Color Map 471
Digital Tag Field Applicability 474
ICI Action Codes 474
ICI Point Types 475
Time Units 477
Instrument Types 477
Tag Quality Bits 477
System Information 479
Tag Configuration Retrieving Parameters 489
Gas Index Table and Gas Molecular Weight 518
Item Types for Field Assignment 518
Word Offset Prefixes 520
Field Types 520
Alarm Types 522
Dynamic Symbol Table 523
Data Processor file 525
AC800F Support 527
Overview 527
Functionalities 527
Plc File parsing results xml file/s (Temporary File) 529
FreelanceTemplate.xml (Temporary File) 529
Intended User
This manual can be used by anyone who performs the functions of a system
manager or configuration manager on a PGP application.
Document Structure
The Power Generation Portal Configuration Manual contains seven major
sections:
The structures of the databases for tags, trend groups and calculations
are explained giving description of each field. Customers will use this
section commonly since it is strictly related to application entities.
9AKK101130D1382
13
The last three sections introduce the distributed architecture and the
OPC server and client.
14
9AKK101130D1382
personal injury or death. Therefore, comply fully with all Warning and
Caution notices.
Related Documentation
On-line Documentation
All documentation is supplied in Adobe Acrobat reader (.pdf) format.
The Power Generation Portal User Manual is also available as online Help.
Category
Software
Installation
Title
Power Generation Portal
Installation Manual
Description
How to install Power Generation Portal.
Power Generation Portal Release Known problems, fixed problems and other
Notes
release information.
Power Generation Portal
Configuration Manual
Power Generation Portal Registry List all registry settings used by Power
Settings
Generation Portal Software
Power Generation Portal 800xA
Connectivity Package
9AKK101130D1382
15
Category
Operation
Title
Description
16
9AKK101130D1382
9AKK101130D1382
17
Parameter or Feature
Min.
Default
Max.
Current
Database
Tags Number of Analog Tags
100
5,000
256,000
100
5,000
256,000
200
10,000
512,000
128
512
512
2,048
100
1,024
N/A
N/A
Unlimited N/A
N/A
N/A
N/A
10
272
1,024
64
16
20
32
512
100
2,000
100
10,000
N/A
256
256
Alarm Handling
18
256
9AKK101130D1382
Parameter or Feature
Min.
Default
Max.
Current
Human Interface
Displays Number of Displays
N/A
N/A
Unlimited
100
500
32
32
N/A
500
1,000
0.2
99.0
4.0
99.0
60
20
100
18
18
18
18
256/SER
Security
Process Events
SOE Number of SOE Tags
5,000/SE
M
Number of SOE Devices
10
N/A
N/A
Unlimited
N/A
N/A
Unlimited
24
24
10
100
Summaries
Tags realtime Tag Summaries
Tag Operating Parameters
Hist. Archiving
9AKK101130D1382
19
Parameter or Feature
Min.
Default
Max.
Current
100
1,000
60
512
15
15
15
N/A
10,000
100,000
100
1,000
100
1,000
10,000
100
9,999
N/A
N/A
Unlimited N/A
50
1,000
N/A
99
N/A
N/A
Unlimited N/A
32
64
32
64
15
Reports
Printing
Printers Number of Printers
Ext. Interfacing
Interfaces Number of Unique Interfaces
Hardware
Communication
Infinet Number of INICIs
20
9AKK101130D1382
Parameter or Feature
Details
Database
General Configuration
Tags Standard Format
Compatibility to ...
Alarm Handling
General Alarm Acknowledgment
Alarm Inhibit
9AKK101130D1382
21
Parameter or Feature
Details
Configurable.
Default: 16 main groups and 16 subgroups for each main group.
Beep,
Wave file (one shot or continuous),
Horn (via RCM).
Audible on Alarm
Audible on RTN
Global.
Alarm Filtering
per Priority,
per Alarm Group.
Alarm Summary
22
Configurable.
1 Millisecond.
9AKK101130D1382
Parameter or Feature
Date and Time
Details
Configurable.
Standard: dd-mmm-yy or
Alternate: according to Regional
Option settings.
International Date
Calculations
General Configuration
Triggering
Statements Statement Length
Operators Arithmetical Operations
Logical Operators
Relational Operators
IF-THEN-ELSE,
WHILE-DO.
9AKK101130D1382
Tag Functions
File Functions
READFILE, WRITEFILE.
Time Functions
Steam Functions
23
Parameter or Feature
Details
Historical Functions
Human Interface
General Language
Multi-language supported.
Default English or Italian.
Other languages supported if
translation files are provided.
Support for UNICODE characters
and Right-To-Left aligned languages
available.
Embedded Editor,
SODG (via translation),
Loox Maker.
SODG
24
9AKK101130D1382
Parameter or Feature
Windows Multi-screen
Draggable Windows
Process Control SP and CO Increment
Details
Configurable (default NO).
Configurable (default NO).
Configurable (default 0.2%).
Security
General Access
Technology
Log In Log In
Individual users.
Proprietary.
Username and Password.
Username
No case sensitivity.
Password
No case sensitivity.
Configurable.
Log-in Display
Configurable.
Manual on demand or
Automatic on time-out.
Log-out Time-out
Configurable.
Log-out Display
Configurable.
Process Events
General Sequence of Events
Sequence of Events Resolution
Tags Number of SOE Events
Duplication of SOE to Digital Inputs
Logs Multiple SOE Logs
9AKK101130D1382
25
Parameter or Feature
Details
Summaries
Tags realtime Tag Summary
Hist. Archiving
General Types of Data
Playback,
Historical Trend Groups,
Post Trip Groups,
Chronological Alarm Messages
Slope Band.
Istantaneous Value, Minimum,
Maximum, Total, Count, Monitor and
Ratio.
Trend or Table.
realtime or Historical.
Default: 0 - 100 % or
E.U. Scale of Selected Tag.
26
On-line or Off-line.
9AKK101130D1382
Parameter or Feature
Trend Group Display Configurability
Details
On-line.
Tag Scale, Curve Color and Display
Coordinates.
On Demand.
Average, Minimum and Maximum,
Time of Minimum and Maximum.
Archival Storage
On-line, Remote
Configurable.
Manual Archiving
Supported.
Reports
General Template Configuration
Logged Data
Triggering
On event or On schedule.
Latency on Disk
9AKK101130D1382
27
Parameter or Feature
Details
Standard Text File,
Custom Excel Work-sheet.
Printing
Alarms Type of Printing
Configurable.
Manual.
Configurable.
Reports Timing
Automatically Scheduled,
Manual on Demand.
Ext. Interfaces
OLE OLE/DDE Interface
ODBC ODBC Interface
DDE Functions.
Oracle, Access, dBase IV, Excel, MS
SQL Server.
Hosts Architecture
Client/Server.
Hardware
Host PC
Custom
(Dell and Compaq suggested).
28
Automatic or Manual.
Configurable.
9AKK101130D1382
Parameter or Feature
Nodes Redundancy
Field Field Hardware
Details
Multi-Master Nodes.
Freelance 2000, Symphony, Infi 90,
Network 90, Foreign Devices.
Communication
Standard Supported
Scanner Suite Capability to Host Drivers for
Modbus Protocol,
Generic Serial Protocol,
Text Files,
Relational Database (OBDC),
TCP/IP IEC 8070-5-104 Protocol,
System Six through DAS API.
Configuration Overview
These instructions provide information to configure PGP. The configuration
steps assume that the system is being generated for the first time, and
therefore may include some steps that could be skipped on subsequent
generations.
Some configurations can be performed just to reflect the hardware
configuration of the system, others may be performed to implement
archiving, or to customize alarm management. The former takes place
during the system set up or when new hardware equipment is going to be
installed, the latter may take place several times during the life-cycle of the
PGP application.
9AKK101130D1382
29
Outline of Configuration
This section outlines the general steps for configuring PGP. The following
sections provide the necessary information to actually perform the
configuration steps outlined here.
PGP database is mainly loaded by a set of (at least one) DBF or XLS files.
The content of these files is processed and loaded in the PGP data files by
running a build procedure. These files are located, unless differently
specified, in the CONFIG folder and sub-folders.
PGP is mainly off-line customized editing a set of XML files. They are
commonly named (for historical reason) DECK files or DECKs. These files
are located, unless differently specified, in the DECK folder.
The content of DECK files is processed and loaded in the PGP data files by
running a build procedure.
Database configuration and system customizations are separated activities.
They can be performed in different time and, with some restrictions, in
whatever order. Each operation can be performed separately from the
others. Only changing the system sizes or rebuilding the file system requires
a complete build procedure. A single DECK can be processed to change a
specific configuration. Restrictions in the sequence of processing take place
when DECKs have some relationship.
Changes to the configuration of a DECK file must be carried out by copying
the DECK file to the CONFIG\DECK folder as 2DECK (e.g. to change
BATTDECK configuration, copy the file as BATT2DECK in the
CONFIG\DECK folder). A 2DECK file must contain only changes to the
default (defined by DECK file) configuration.
A DECK file automatically references the 2DECK file, if existing, during the
build phase.
Displays are configured by a dedicated procedure, it is described in a
separated manual. Here just the directions to convert and compile displays
are given.
In the following description, bold and underlined characters are used to
highlight mandatory configuration actions and bold characters are used to
highlight optional configuration actions to be performed for each installation.
30
9AKK101130D1382
9AKK101130D1382
31
Export the menu and tool-bar database file(s) to the computer running PGP
and build the menu and tool-bar database file(s) on board the PGP
computer.
PGP provides a default menu and tool-bar configuration.
Configure the language.
Create and/or update the language dictionary definition file BLANG2DECK.
Set the database cross-reference.
The database configuration may require updating the database crossreference file DBXRFDECK. The definition of all database fields requiring
non-standard processing, such as site-specific field assignments or reject
rules, must be included in the cross-reference definition.
Create and/or update the database cross-reference definition file
DBXRF2DECK.
Configure engineering unit database.
Generate engineering unit database(s) on a Personal Computer using the
Dbase III/IV or Excel utility or the SLDG utilities provided by the Bailey
Engineering Work Station.
Export the engineering unit database file(s) to the computer running PGP
and build the engineering unit database file(s) on board the PGP computer.
This operation must be carried out if engineering units are referenced by an
index within the tag database. The configuration is not required if the
engineering unit texts are defined within the tag database.
Configure logic state descriptor database.
Generate logic state descriptor database(s) on a Personal Computer using
the Dbase III/IV or Excel utility.
32
9AKK101130D1382
Export the logic state descriptor database file(s) to the computer running
PGP and build the logic state descriptor database file(s) on board the PGP
computer.
Typically, logic state descriptors are defined within the tag database.
Configure tag database.
Generate tag database(s) on a Personal Computer using the Dbase III/IV or
Excel utility. There are some utilities that allow you to import the DataBase
generated by different Engineering Tools. The SLDG utility provided by the
Bailey Engineering Work Station allows you to import DataBases generated
for the Harmony system. The PlcFileBuilder utility allows you to import
DataBases generated for the AC800F, while the Ac800mBuilder tool allows
you to import DataBases generated for the AC800M systems.
Export the tag database file(s) to the computer running PGP and build the
tag database file(s) on board the PGP computer
For more information on how to configure the AC800M database refer to the
manual: 9AKK101130D1482 - 800xA Connectivity Manual.
For more information on how to configure the AC870P database refer to the
manual: 9AKK105130D3258 - PGP for AC870P.
Configure calculation database.
Create a source file for each calculation block, defining the algorithm and all
input and output tags.
Determine name, number, description and rate of all calculation blocks.
Generate calculation database(s) on a Personal Computer using the Dbase
III/IV or Excel utility. Export the calculation database file(s) to the computer
running PGP and build the calculation database file(s) on board the PGP
computer.
The definition file associates calculation blocks with related algorithm source
files.
9AKK101130D1382
33
34
9AKK101130D1382
9AKK101130D1382
35
36
9AKK101130D1382
System Configuration
This section defines configuration parameters and discusses things to
consider in determining appropriate values. Configuration parameters are
defined into the Windows Registry.
For a complete list of PGP registry read the manual 9AKK101130D8771PGP Registry Settings.
Creating or modifying these parameters is the first step in configuring PGP.
Values of these symbols will be used to size global commons, data files, to
select options and roughly customize the PGP application.
PGP installation sets a default value for each configuration parameter in
order to allow correct operation without any change.
The parameters are located under the:
Hkey_Local_Machine\Software\ABB\Power Generation Portal
registry key of the Windows Registry.
PGP supplies a utility, named SysSetup, which allows viewing and
modifying the configuration parameters. The following section describes the
SysSetup utility.
9AKK101130D1382
37
When selecting the Registry button, the process dialog window changes.
The tree of registry folders is displayed on the left side of the dialog window.
On the right side of the dialog window the registry items are listed by
selecting the registry folder.
The dialog window of the process is shown below.
38
9AKK101130D1382
String.
Both types have a name, a description, a value and can also have
comments.
9AKK101130D1382
39
A integer or real format registry value may have reference values such as
the minimum and maximum allowed values and the default value. These
values together with the notes help in changing the current value.
40
9AKK101130D1382
9AKK101130D1382
41
System Options
This section defines a set of symbols, called System Options, that allow
customization of some running features of PGP.
The System Option registry set is read each time PGP starts up. After some
options have been changed, the shutdown and start-up of PGP must be
performed in order for changes to be applied.
Changing System Options could affect performance and operation of the
PGP application
For details on size parameters please refere to the 9AKK101130D8771PGP Registry Settings manual.
Configuration Procedure
Introduction
A set of configuration operations customizes PGP for the operational
conditions. They allow PGP to meet specific application requirements, and
to carry out monitoring and control on the specific process.
The number of configuration operations depends on the kind, the size and
complexity of the PGP application.
They range from a simple tag database configuration to a full tag, Trend
Group and calculation configuration.
42
9AKK101130D1382
9AKK101130D1382
43
The main dialog window of the process deploys five buttons on the left side,
and the process welcome page on the right side.
44
9AKK101130D1382
When the Export button is selected the main process dialog window
changes once again, a window similar to the builder one is displayed on the
left side.
The icons of all the available builder processors are shown, but the Build All
icon is replaced by the Unbuild All icon.
Once the selection has been performed, both a set of action buttons and a
set of build options are displayed on the right side of the window.
9AKK101130D1382
45
The figure below shows the scheme of the builder window when the
Unbuild All icon is selected.
The Export button will be operational only if the selected builder has a
corresponding process for downloading the PGP database.
In the following section is a description of the configuration procedure. It
does not refer to specific builders. It is a general description. The input file to
a builder is generically named definition file.
46
9AKK101130D1382
Building Procedure
Each configuration activity typically involves a single definition file or a few
definition files. For example, changes in the tag database involve the tag
database definition file if all tags are kept in a single file, or the set of tag
database definition files if multiple files are used.
In this section, the most frequent usage of builder environment is described.
First Step
The first step upon entering the builder environment is the identification of
the builder. The builder identification is mandatory both for editing and
building (importing or exporting) in order to point to the right set of definition
files.
Second Step
Editing the definition file(s) is the second step. Changing the existing
definition file(s) or creating new definition file(s) take place at this stage.
Depending on the type of definition file submitted for editing, Excel or
Notepad are invoked.
9AKK101130D1382
47
Builder Window
The following sections describe the elements of the builder window.
Builder List
The builder list section lists all the available builders. Each builder is
designed to process an XML definition file. A definition file defines all the
information to transfer in the internal PGP database at build time.
The following information is a complete list of the database builders with a
brief description. Refer to Section 2, Database Configuration and Section 3,
System Configuration for a detailed description of each definition file.
Direct Access File System (DAFS) builder
The DAFS builder creates the PGP file system and common area. It is the
key builder since the whole internal PGP database is created on the basis of
the information it processes.
The builder processes file definitions. All definitions are in terms of:
File name.
Number of records.
Size of record.
48
9AKK101130D1382
9AKK101130D1382
49
50
9AKK101130D1382
9AKK101130D1382
51
52
9AKK101130D1382
9AKK101130D1382
53
54
9AKK101130D1382
9AKK101130D1382
55
Extension XML files: they are ASCII files and can be changed by using
the Wordpad editor,
Extension DBF files: they are Database files and can be modified by
using DBase IV or Excel,
Extension XLS files: they are Database files and can be modified by
using Excel,
Extension CF files: they are ASCII files in a Bailey format and can be
modified by using the Notepad editor.
All files may be opened on the same computer running PGP, the only
requirement is the availability of standard editors: Notepad, Excel, etc. Files
can also be exported to other computers for modifications and then imported
for processing (building).
Tag database, engineering unit, logic state descriptor, alarm comment and
text selector files may be produced and updated by using the Bailey SODG
utility or the ABB Symphony Composer utility and then copied to the PGP
computer.
The following description only presents the on-board editing.
56
9AKK101130D1382
The figure below shows the builder window after a builder has been
selected: in the example the tag database builder is shown.
9AKK101130D1382
57
When a specific builder icon has been selected, the import function enables
the user to process a definition file after an editing phase.
When modifications have been done on a definition file, the operator must
submit the file to the proper builder in order to transfer modifications to the
internal PGP database, and to make modifications operational.
By clicking the Import button, definition files related to the selected
(highlighted on blue) builder are used for building.
58
9AKK101130D1382
window is opened. The OK button confirm the file initialization. The Cancel
button starts to process without performing any file initialization.
The figure below shows an example of file initialization window displayed
when the alarm group builder runs.
9AKK101130D1382
59
operations when the definition file must be changed. The build operation is
usually very fast and the Abort button is not used.
60
9AKK101130D1382
of heavy changes it is useful to process all definition files rather than to run
single builders separately.
Basically, the windows used by the build all function are those used by the
build function. Refer to the build section for an explanation of the various
windows.
Builder Options
Before running builders, a set of options may be selected for specific
purposes.
9AKK101130D1382
61
62
9AKK101130D1382
The figure below shows an example of builder window where two options
are selected.
9AKK101130D1382
63
64
9AKK101130D1382
9AKK101130D1382
65
Replace Option
This option, when it is selected, forces the builder to replace in the PGP
internal database the items found in the submitted definition file. The notexisting items are added in the PGP internal database.
By default the replace option is already selected. It means that items are
added or replaced in the PGP database.
Delete Option
When selected, this option, reverses the builder operation in order to delete
from the PGP internal database the items found in the submitted definition
file.
For example, if the tag database builder has been selected, the delete
option forces the builder to delete from PGP tag database all the tags found
in the submitted tag definition DBF file.
By default, the delete option is not selected. It means that tags are added or
replaced in the PGP database.
Log File
When the log file option is selected, a log file specification may be entered in
the field of this area. Disk drive, folder path and file name identify the file
specification.
The default file name is BUILD.LOG and will be allocated in the \LOGS
folder.
Export Window
The following sections describe the structure of the elements the export
window.
See the previous section Builder List for further details on the builder
description.
66
9AKK101130D1382
Tag database,
Calculation database,
Pegboard database.
Audible database,
Report database,
Security database,
Node database,
9AKK101130D1382
67
68
9AKK101130D1382
Select Option
When selected, this option allows you to define selection criteria during the
export procedure.
Criteria allows you to set a modification time interval within which it is
possible to select the items going to be processed. The initial and the final
date and time can be defined.
Further, a SQL like specification allows you to filter items satisfying a
selection criteria. Database field names must be typed in uppercase. For
example, the select condition TAGTYPE = CALCANG allows you to refer
only analog calculated tags.
9AKK101130D1382
69
70
9AKK101130D1382
Description
Name
Format
Field format.
Allowed field formats are:
- character (char),
- integer (int) or
- real.
If a numeric (integer or real) field is left blank, it is treated as zero.
Width
Field width.
It is the maximum number of characters or digits (including decimal point if real
number) allowed to assign a value to the field.
Opt/Mnd
Description
Field description.
Range
9AKK101130D1382
69
Description
Default value.
It applies to optional fields only and defines the value assigned to the field if the
user does not define a value.
Parameters
Each field has a format and a width defined. Most of them have a range of
legal values and a default value defined. Further, sizing parameters may be
defined.
In the on-line configuration most of boolean fields are set using the check
mark. A check mark means Y(es), nothing (empty cell) means N(o).
The tables in the following sections always refer to the database
configuration, and boolean fields have values Y(es) or N(o).
70
9AKK101130D1382
Tag Database
The tag database consists of one or more files generated on a Personal
Computer using standard packages like DBase III/IV or EXCEL, the SLDG
9AKK101130D1382
71
72
9AKK101130D1382
Fields are classed into sub-sections for an easy use and reference. The
three main sections contain the same number of sub-sections to allow easy
cross-reference. If a section does not define any field for the specific main
section, it will be left empty.
General Parameters
The fields in Table 4 and Table 5 define the name and other additional
parameters used to identify the tag, and to give an explicit reference to the
process.
They define three key characteristics of a tag: the index and the name to
uniquely identify the tag, and the type to characterize it. Tag name and tag
type are mandatory fields.
9AKK101130D1382
73
Name
INDEX
Range
Default
Parameter(s)
Description
Integer
Tag index.
{0, 1...128000}
Optional
[mxindx]
Character
Tag name.
<string>
20
<blank>
Mandatory
[sznam]
<string>
Character
36
Mandatory
Character
Tag description.
<string>
64
<blank>
Optional
[szdesc]
74
9AKK101130D1382
Name
TAGTYPE
Description
Range
Default
Parameter(s)
Character
UNDEF
[sztype]
Mandatory
CUSTTAGID
PRIMDISP
SEC_LEVEL
Character
7
Optional
Character
<string>
32
<blank>
Optional
Character
<string>
80
<blank>
Optional
Integer
Security level.
{0, 1...16}
0
This field is checked whenever an user
attempts to operate over the tag. Only
None
users whose security level is greater or
equal to what's hereby defined are
enabled to access the tag for changes or
control.
Optional
9AKK101130D1382
<blank>
None
None
75
Name
SEC_GROUP
Range
Default
Parameter(s)
{0, 1...32}
Integer
Security group.
0
This field is checked whenever an user
attempts to operate over the tag. Only
None
users whose security group mask
includes what's hereby defined are
enabled to access the tag for changes or
control.
Optional
EXTDESC
Description
Character
<string>
80
<blank>
Optional
[szedsc]
Note 1:
The TAGUID code is internally generated the first time a tag is added to the
PGP database (i.e. each time a tag database build follows a database
initialization).
Add the TAGUID field to the tag database and leave it initially blank when
the tag database file is filled in.
Following a tag database build, an un-build operation must be executed in
order the TAGUID field is filled. If the TAGUID is left blank, later on the tag
cannot be replaced within the PGP database, an error message is issued for
duplicate tag since a new TAGUID is generated. A PGP database
initialization only allows replacing (actually adding) the tag.
Once assigned, the TAGUID may be kept unchanged for the whole history
of a tag. The tag name or the tag index may change, the TAGUID is not
affected. That allows you to keep track of a tag during the history of the
application (for example within the trend historical groups).
76
9AKK101130D1382
Name
PLANTUNIT
Range
Default
Parameter(s)
Description
Integer
Plant unit.
{0, 1...12}
Optional
None
Process Parameters
The fields of Table 6 and Table 7 define the basic information for the tag
configuration: initial condition (setting at start-up time), alarm processing,
playback saving, application program activation, output transferring, value
exporting, triggering (calculation, report, totalization), process control inhibit.
All fields are optional.
9AKK101130D1382
77
Name
AL_REM
OFFALINI
{Y, N}
Character
Y
If set, the alarm processing for this tag
will be performed remotely (PCU level or None
PLC level), otherwise it will be performed
locally (computer level). This field is
meaningful for tags coming from smart
devices able to check for an alarm
condition. For all other tags, alarm
processing is always performed locally.
Optional
OFFSCINI
Range
Default
Parameter(s)
Description
{Y, N}
Character
1
Optional
Character
{Y, N}
Optional
None
PLAYBACK
Character
{Y, N}
Optional
Character
{Y, N}
Optional
78
None
None
9AKK101130D1382
Name
AAP_NUM
Description
Range
Default
Parameter(s)
{ 0, 1...63}
Integer
0
If greater than 0, this field defines a link
which will cause an user defined
None
application program to be activated upon
status changes for this tag.
Optional
{0, 1...999}
Integer
0
If greater than 0, it identifies the
calculation block to be triggered when the [mxxcal]
tag goes into alarm or returns to normal.
Optional
{0,1...50}
Integer
Optional
64
Optional
FACEPLATE
<string>
Character
80
Optional
9AKK101130D1382
<string>
Character
79
Name
CONFIRMCM
CTRLINHTAG
Description
Range
Default
Parameter(s)
Character
1
Optional
Char
<string>
20
<blank>
Optional
{Y,N}
[sznam]
Character
<string>
56
<blank>
Optional
Character
Optional
80
{Y,N}
9AKK101130D1382
Name
MAINTTRIG
Range
Default
Parameter(s)
Description
{0, 1...100}
Integer
0
If greater than 0, it identifies the
maintenance log to be triggered when the [n.hrtl]
tag goes into alarm or returns to normal.
Optional
Integer
{0, 1, 2}
Optional
0 = NO
1 = Read only
2 = R/W
The EXP_VAL field that allows you to specify a relational database (i.e.
Oracle, Access) must be updated with the values of the tag. That requires
the installation of a specific (ODBC Connection Support) optional PGP
license and a relational database package to manage the tag values.
The parameters listed in the following table are not included in the Process
Tab of the on-line configuration.
9AKK101130D1382
81
Name
ACK_PROG
Range
Default
Parameter(s)
Description
Character
Optional
N
None
Char
<string>
20
<blank>
Optional
EXPFIL
PLAYBACKLT
[sznam]
{Y, N}
Character
1
Optional
Character
{Y,N}
Optional
None
82
9AKK101130D1382
Name
PLAYBACKSP
Description
Range
Default
Parameter(s)
{Y,N}
Character
Y
If set, tag exception reports will be
submitted to specific processing on
None
playback archiving. A specific application
routine must be implemented.
Optional
Character
1
Optional
TOT_LOG
{0,1...100}
Integer
Optional
9AKK101130D1382
83
process interface devices. They are meaningful only for tags acquired from
external (foreign) acquisition devices. In any other case, their contents will
be ignored.
These fields only provide an addressing criterion for external tags. The base
system does not support any type of driver for foreign acquisition devices.
Such drivers, whenever required, must be developed as specific application
packages.
All fields are mandatory if an external acquisition device is used. Otherwise
they must not be defined.
The Generic Scanner parameters replace previous External and Modbus
Acquisition parameters. Their description has been removed from the
configuration manual.
However, those parameters are still supported for compatibility with previous
versions of PGP. Refer to configuration manual of release 1.3 (or previous)
for details.
Table 8. Generic Tag Generic Scanner Input Parameters.
Format
Width
Opt/Mnd
Name
FIELD_AD1
...................
FIELD_AD10
FIELD_TX1
................
84
Integer
Range
Default
Parameter(s)
Description
Field input address 1.
Mandatory
None
................
.................................
Integer
............
Mandatory
None
Character
<string>
80
<blank>
Optional
[mxopcn]
................
..................................
.............
9AKK101130D1382
Name
FIELD_TX10
Character
FIELD_DRV
Description
Field input driver text 10.
Range
Default
Parameter(s)
<string>
80
<blank>
Optional
[mxopcn]
Character
<string>
20
<blank>
Mandatory
[sznam]
9AKK101130D1382
85
Name
OUT1_AD1
Integer
0
None
Mandatory
.................
................
..................................
OUT1_AD10
Integer
Mandatory
........
0
None
.................
................
..................................
OUT5_AD10
Integer
OUT1_TX1
Range
Default
Parameter(s)
Description
........
Mandatory
None
Character
<string>
64
<blank>
Optional
[szdesc]
..............
................
....................................
............
OUT1_TX10
Character
<string>
64
<blank>
Optional
[szdesc]
..............
................
....................................
............
OUT5_TX10
Character
<string>
86
64
<blank>
Optional
[szdesc]
9AKK101130D1382
Name
OUT1_DRV
Description
Range
Default
Parameter(s)
<string>
Character
20
<blank>
This name identifies the kind of driver
interfacing PGP to the process for output [sznam]
communication.
Mandatory
................
....................................
............
OUT5_DRV
Character
<string>
20
<blank>
This name identifies the kind of driver
interfacing PGP to the process for output [sznam]
communication.
Mandatory
Note 1:
The OUT1_ADn fields replace the OUT_ADn fields. The description of
OUT_ADn has been removed from the configuration manual. However, the
field is still supported for compatibility with previous PGP versions. Refer to
configuration manual of release 4.0 (or previous) for details.
Note 2:
The OUT1_TXn fields replace the OUT_TXn fields. The description of
OUT_TXn has been removed from the configuration manual. However, the
field is still supported for compatibility with previous PGP versions. Refer to
configuration manual of release 4.0 (or previous) for details.
Note 3:
The OUT1_DRV field replaces the OUT_DRV field. The description of
OUT_DRV has been removed from the configuration manual. However, the
field is still supported for compatibility with previous PGP versions. Refer to
configuration manual of release 4.0 (or previous) for details.
9AKK101130D1382
87
Name
ICI_NUM
ICI_NDX
Range
Default
Parameter(s)
Description
Integer
ICI Number.
{1...8}
Optional
Integer
ICI index.
{-1, 0...29999}
Optional
[mxciu] or [mxxciu]
88
Integer
Ring number.
{0..63}
Mandatory
None
9AKK101130D1382
Name
PCU
Integer
MODULE
{1...256}
0
Mandatory
None
Module number.
{0...31}
Mandatory
None
Integer
ICISTA_CD
PCU number.
3
Integer
BLOCK
Range
Default
Parameter(s)
Description
Block number.
{0...99999}
Mandatory
None
{X, E, C, D}
Character
Optional
Command Parameters
Fields of this sub-section apply to digital tags only. Refer to the analogue
sub-section of digital tag definition for details.
9AKK101130D1382
89
Name
DS_ALARM
PR_ALARM
Range
Default
Parameter(s)
Description
Character
1
Optional
Character
{Y, N}
Optional
{Y, N}
None
AUD_ALARM
BOT_ALARM
REM_ONACK
Character
{Y, N}
Optional
Character
{Y, N}
Optional
Character
{Y, N}
Optional
Character
{Y, N}
Optional
90
None
None
None
9AKK101130D1382
Name
INFO_ONACK
DS_RTN
PR_RTN
Range
Default
Parameter(s)
Description
Character
1
Optional
Character
1
Optional
Y
If set, a RTN message concerning this
tag will be displayed on alarm display
None
pages (LADs). An alarm acknowledge will
then remove the message.
Character
{Y, N}
Optional
N
None
None
Character
{Y, N}
Optional
AUD_RTN
Character
1
Optional
9AKK101130D1382
None
91
Name
PR_STCHNG
Range
Default
Parameter(s)
Description
{Y, N}
Character
N
If set, the changes of state concerning
this tag will be printed on alarm printer(s). None
State changes are intended as
alarms/RTNs of digital tags defined as
events (field EVENTTAG set to Y).
Optional
DS_STCHNG
PR_OPACT
{Y, N}
Character
1
Optional
Y
If set, the changes of state concerning
this tag will be recorded into the Operator None
Journal.
Character
{Y, N}
Optional
Character
{Y, N}
Optional
None
PR_INFO
{Y, N}
Character
1
Optional
Character
{Y, N}
Optional
None
92
9AKK101130D1382
Name
SV_INFO
EXP_ALA
APPL_ALA
Range
Default
Parameter(s)
Description
Character
1
Optional
Character
Optional
Character
{Y, N}
Optional
{Y, N}
None
None
ALMGROUP
Character
{Y, N}
Optional
Integer
{0, 1...272}
0
This field allows you to group all tags
belonging to a given plant area or
[sladnm] or [mxxagp]
component. Alarm group numbers are
used to sort the alarms for the
presentation on screen. Alarm groups are
customer defined. By default, groups 1 to
16 are defined as first level groups,
directly addressed by alarm displays and
summaries. Groups 17 to 32 are defined
as sub-groups of group 1, groups 33 to
48 are defined as sub-groups of group 2
and so on.
Optional
9AKK101130D1382
None
93
Name
AL_PRI
Range
Default
Parameter(s)
Description
{1 ... 16}
Integer
Optional
AUDINDEX
20
Optional
<blank>
Name of a tag that, while in alarm, will
disable the generation of alarm
[sznam]
messages for this tag. If the field is blank,
no alarm inhibit tag is defined.
Integer
{0, 1...32}
Optional
94
<string>
Char
[mxaud]
9AKK101130D1382
Name
ALMPRINTER
Range
Default
Parameter(s)
Description
{1...99}
Integer
1
Reference index to the printer where
messages concerning the tag are printed. None
See the fields PR_xxx (e.g. PR_ALARM)
also.
Optional
Integer
3
Optional
0
None
9AKK101130D1382
95
Name
ALPRI_RTN
Range
Default
Parameter(s)
Description
Integer
Optional
[mxalpr] or [mxxapr]
Integer
0
This is the priority assigned to the tag
when a hardware channel failure takes
[mxalpr] or [mxxapr]
place. If set to 0 then the default priority is
assigned.
Optional
96
9AKK101130D1382
The index is used to address an alarm comment defined within the alarm
comment database. This approach requires the separate configuration of an
alarm comment database in order to define all referenced alarm comments.
If the index is defined, the text type field (if any) is ignored.
If the text type field is used, it is added to the alarm comment database at
the first vacant index. This approach does not require the separate
configuration of an alarm comment database.
If the text is defined, the index type field must not be included in the tag
database.
Refer to the Alarm Comment definition chapter for more information about
the contents of these fields. Refer to the analogue sub-sections of analog
and digital tag definitions for specific alarm comments.
The on-line configuration allows selection of alarm comment either by index
(typing the number) or text (selecting from a list).
Table 13. Generic Tag Alarm Comment Parameters.
Format
Width
Opt/Mnd
Name
ALRMCMNT1
ALRMCTXT1
ALRMCMNT2
Integer
{1...100}
0
Optional
[mxalcm]
Character
<string>
80
<blank>
Optional
[szalcm]
Integer
Optional
Character
80
Optional
9AKK101130D1382
5
ALRMCTXT2
Range
Default
Parameter(s)
Description
97
Name
ALRMCMNT13
ALRMCTXT13
Integer
Range
Default
Parameter(s)
Description
Optional
[mxalcm]
Character
<string>
80
<blank>
Optional
[szalcm]
Network Parameters
The fields in Table 14 refer to the PGP network communication subsystem.
They are used when multiple PGP servers in a multi-master architecture
exchange data (values, alarm acknowledges, messages, configurations)
among them.
All fields are optional and they must be defined when servers (nodes) are
intended to cooperate in a multi-master architecture.
The fields reference the node definition. Refer to the Nodes database for
details.
98
9AKK101130D1382
Name
CNFNODMSK
Format
Width
Opt/Mnd
Sequence {Y, N}
Optional
None
Character
Sequence {Y, N}
Sequence {Y, N}
Sequence {Y, N}
Optional
16*N
The mask applies to nodes from 49 to 64 None
Character
Sequence {Y, N}
16
16*N
Operator actions are routed from the
current node to the nodes set in the
None
destination mask. First bit refers to node
1 in the node definition, second bit refers
to node 2, and so on.
16
Optional
CNFNODMS3
Character
16
Optional
CNFNODMS4
Character
16
DESTNODMSK
Optional
DESTNODMS2
16*N
The mask applies to nodes from 33 to 48. None
Character
16
Sequence {Y, N}
None
Character
16
Optional
9AKK101130D1382
16*N
16*N
The mask applies to nodes from 17 to 32. None
Optional
DESTNODMS3
Range
Default
Parameter(s)
Character
16
CNFNODMS2
Description
Sequence {Y, N}
None
99
Name
DESTNODMS4
Format
Width
Opt/Mnd
Description
Character
16
Optional
DESTVALMSK
None
16
16*N
Tag values are routed from the current
node to the nodes set in the destination
None
mask. First bit refers to node 1 in the
node definition, second bit refers to node
2, and so on.
Character
16
Character
16
SRCNODMS2
Character
16
Sequence {Y, N}
None
Character
Sequence {Y, N}
16
16*N
Optional
Character
Sequence {Y, N}
16
Optional
100
Sequence {Y, N}
None
Optional
SRCNODMSK
Sequence {Y, N}
None
Optional
DESTVALMS4
Sequence {Y, N}
Optional
DESTVALMS3
Sequence {Y, N}
Character
Optional
DESTVALMS2
Range
Default
Parameter(s)
None
None
9AKK101130D1382
Name
SRCNODMS3
Description
Character
16
Optional
SRCNODMS4
Range
Default
Parameter(s)
Sequence {Y, N}
None
Character
16
Optional
Sequence {Y, N}
None
OPC Parameters
OPC (OLE for Process Control) is a standard mechanism based on the
Microsoft OLE/COM technology for communicating to numerous data
sources in order to grant inter-operability between automation/control
application, field systems/devices and business/office applications in the
process control industry.
The PGP OPC Client provides Data Access (in accordance to the 1.0a and
2.03 specifications) and Alarm&Event (in accordance to the 1.02
specification) functionalities and allows simultaneous connections to local
and remote OPC servers.The PGP OPC Server provides Data Access and
Alarm&Event functionalities as well but, as far as the DA specification is
concerned, only the 2.03 is supported..
The fields in Table 15 and Table 12 refer to the PGP OPC subsystem and
can be used to define the database from the OPC point of view. They are
meaningful for OPC tag types only.
OPC tags can be successfully used only if the PGP OPC Support has been
installed and licensed. In such a case, the on-line configuration provides a
Tab for OPC parameters.
9AKK101130D1382
101
Name
OPCPROGID
OPCPROGAE
OPCCMPTR
OPCITEMID
OPCACCPATH
Format
Width
Opt/Mnd
Range
Default
Parameter(s)
Character
Server name.
80
Mandatory
Character
80
Mandatory
Character
Computer name.
80
Optional
Character
Item identification.
80
Mandatory
<blank>
This is the unique identification of data
item to be accessed in the server specific [mxopci]
address space. The value to be specified
depends on the OPC server.
Character
Access path.
80
Optional
102
Description
<string>
<string>
<string>
<string>
<string>
9AKK101130D1382
Name
OPCREFRESH
Integer
Optional
Range
Default
Parameter(s)
Description
1
None
Integer
Read type.
Optional
OPCEXPCLNT
120
None
Character
{Y,N}
Optional
None
Description
500
500 milliseconds.
1 second.
2 second.
3 seconds.
9AKK101130D1382
103
Description
5 second.
10
10 seconds.
30
30 seconds.
60
60 seconds.
Description
Synchronous read from DEVICE (the physical device).
The OPC client send a data read request and waiting for response.
110
120
The parameters listed in the following table are not included in the OPC Tab
of the on-line configuration.
104
9AKK101130D1382
Name
OPC_ALA
OPCPROGHS
Range
Default
Parameter(s)
Description
Character
{Y, N}
Optional
Character
<string>
80
<blank>
Mandatory
None
[mxopcn]
Totalization Parameters
Fields of this sub-section differ for analog and digital tags. Refer to the
analogue sub-section of analog and digital tags for details.
Documentation Parameters
The fields in Table 19 allow linking tag conditions and documentation.
Currently, PGP does not manage these fields, but they may be loaded in the
tag database for a future use.
9AKK101130D1382
105
Name
ALMDHF
Integer
5
Optional
ALMDRN
Integer
5
Optional
ALMDHA
Integer
5
Optional
Range
Default
Parameter(s)
Description
0
None
0
None
Refer to the analogue sub-sections of digital and analog tag definition for
additional fields.
106
9AKK101130D1382
Name
S_COORD
S_MODULE
S_CHANNEL
S_TYPE
TO_BOARD
TO_TU_TY
TO_TU_CO
TO_TB_ID
9AKK101130D1382
Character
Range
Default
Parameter(s)
Description
Slave module coordinates.
<string>
10
<blank>
Optional
None
Character
<string>
<blank>
Optional
None
Character
<string>
<blank>
Optional
None
Character
<string>
<blank>
Optional
None
Character
<string>
14
<blank>
Optional
None
Character
<string>
<blank>
Optional
None
Character
<string>
10
<blank>
Optional
None
Character
<string>
<blank>
Optional
None
107
Name
TO_PIN1
TO_PIN2
TO_PIN3
DRAW_REF
DESC_CABLE
FR_BOARD
FR_TB_ID
FR_ROW
108
Character
Range
Default
Parameter(s)
Description
First pin on termination board.
<string>
<blank>
Optional
None
Character
<string>
<blank>
Optional
None
Character
<string>
<blank>
Optional
None
Character
14
<blank>
Optional
None
Character
<string>
20
<blank>
Optional
Character
<string>
14
<blank>
Optional
Character
<string>
None
None
<blank>
Optional
None
Character
<string>
<blank>
Optional
None
9AKK101130D1382
Name
FR_PIN1
FR_PIN2
Character
<blank>
Optional
None
Character
Character
Optional
None
Character
Character
<string>
<blank>
Optional
None
Character
Character
14
Character
14
Optional
<string>
<blank>
None
Optional
9AKK101130D1382
<blank>
None
Optional
WIN_ROW3
<string>
14
WIN_ROW2
<string>
<blank>
Optional
WIN_ROW1
<blank>
8
WIN_NUMBER
<string>
None
Optional
WIN_PANEL
<string>
3
FR_PIN3
Range
Default
Parameter(s)
Description
<string>
<blank>
None
<string>
<blank>
None
109
Application Parameters
The fields in Table 21 and Table 22 are available for additional tag
qualification or to be used by application specific programs.
All fields are optional.
Application parameters may be statically used by defining a value for them.
Values will be unchanged. They may also be dynamically used to update
values by application programs. Initial values may be set.
Table 21. Generic Tag - Application Parameters.
Format
Width
Opt/Mnd
Name
USER3
USER7
USER10
UT_IN1
UT_IN2
UT_IN3
110
Character
Range
Default
Parameter(s)
Description
ASCII text.
<string>
<blank>
Optional
None
Character
ASCII text.
<string>
16
<blank>
Optional
None
Character
ASCII text.
<string>
32
<blank>
Optional
None
Integer
Integer value.
{-32767...+32767}
Optional
None
Integer
Integer value.
{-32767...+32767}
Optional
None
Integer
Integer value.
{-32767...+32767}
Optional
None
9AKK101130D1382
Name
UT_IN4
UT_RE1
UT_RE2
UT_RE3
UT_RE4
UT_RE5
UT_RE6
9AKK101130D1382
Integer
Range
Default
Parameter(s)
Description
Integer value.
{-32767...+32767}
Optional
None
Real
Real number.
Optional
None
Real
Real number.
Optional
None
Real
Real number.
Optional
None
Real
Real number.
Optional
None
Real
Real number.
Optional
None
Real
Real number.
Optional
None
111
Name
ASPECT1NAM
Description
Range
Default
Parameter(s)
<string>
Character
20
Optional
Character
<string>
80
<blank>
Optional
[szedsc]
...............
..............................................
............
......................
...............
..............................................
............
ASPECT5NAM
Character
<string>
20
<blank>
Optional
ASPECT5CMD
[sznam]
Character
<string>
80
<blank>
Optional
[szedsc]
Note 1:
The aspect command line defines the command to be executed when the
menu item is selected. The syntax of the command line is
<program name>
112
9AKK101130D1382
or
<program name> <parameters>
The program name identifies the program to be activated and the
parameters to define possible input data to the program.
A parameter can be a tag name. It can be symbolically referenced using the
syntax %TAG%. At execution time the symbolic reference will be replaced
with the actual tag name.
The parameters listed in the following table are not included in the
Application Tab of the on-line configuration.
Table 22. Generic Tag - Application Parameters (cntd.).
Format
Width
Opt/Mnd
Name
ATOM1NAM
Character
Range
Default
Parameter(s)
Description
Atom name 1.
<string>
64
<blank>
Optional
[szdesc]
...................
...............
....................
............................
ATOM50NAM
Character
<string>
64
<blank>
Optional
ATOM1TYP
Integer
[szdesc]
Atom type 1.
Optional
None
...................
...............
....................
ATOM50TYP
Integer
Optional
9AKK101130D1382
............................
0
None
113
Name
ATOM1VAL
Integer
Range
Default
Parameter(s)
Description
Atom value 1.
{-32767...+32767}
10
Optional
None
...................
...............
....................
............................
ATOM50VAL
Integer
{-32767...+32767}
10
Optional
None
DD (Device Driver).
114
9AKK101130D1382
General Parameters
The fields in Table 23 define the text strings to be associated as logic state
descriptors to each possible status of the tag.
The total number of status text descriptors to be defined in a tag definition
depends on the tag type. For example, a MSDD tag has four statuses and,
in general, it will need four text descriptors.
Since all digital tags have at least two statuses, the first two logic state
descriptors are mandatory, all others are optional.
Table 23. Digital Tag - General Parameters.
Name
ZEROSTATE
ONESTATE
Format
Width
Opt/Mnd
Description
Range
Default
Parameter(s)
Character
<string>
16
Mandatory
Character
<string>
16
Mandatory
TWOSTATE
[sztags]
Character
<string>
16
<blank>
Optional
THREESTATE
[sztags]
Character
<string>
16
<blank>
Optional
FOURSTATE
9AKK101130D1382
Character
[sztags]
Same as above for state 4.
<string>
16
<blank>
Optional
[sztags]
115
Name
FIVESTATE
SIXSTATE
SEVENSTATE
EIGHTSTATE
NINESTATE
TENSTATE
ELEVNSTATE
TWELVSTATE
116
Format
Width
Opt/Mnd
Character
Description
Same as above for state 5.
Range
Default
Parameter(s)
<string>
16
<blank>
Optional
[sztags]
Character
<string>
16
<blank>
Optional
[sztags]
Character
<string>
16
<blank>
Optional
[sztags]
Character
<string>
16
<blank>
Optional
[sztags]
Character
<string>
16
<blank>
Optional
[sztags]
Character
<string>
16
<blank>
Optional
[sztags]
Character
<string>
16
<blank>
Optional
[sztags]
Character
<string>
16
<blank>
Optional
[sztags]
9AKK101130D1382
Name
THTEESTATE
Character
FRTEESTATE
Optional
[sztags]
Same as above for state 14.
<string>
16
<blank>
Optional
[sztags]
Same as above for state 15.
<string>
16
<blank>
Optional
[sztags]
Integer
16
Optional
None
..................
...............
.................................................
LSD16INDEX
Integer
ISALARM0
<string>
<blank>
Character
LSD1INDEX
16
Character
FVTEESTATE
Range
Default
Parameter(s)
Description
.........
16
Optional
None
Character
{Y, N}
Optional
None
..................
...............
.................................................
.........
ISALARM31
Character
{Y, N}
Optional
None
Note 1:
9AKK101130D1382
117
The IsAlarm0, IsAlarm1, ... IsAlarmn fields replace the Refstat field. The
description of Refstat has been removed from the configuration manual.
However, the field is still supported for compatibility with previous PGP
versions. Refer to configuration manual of release 1.4 (or previous) for
details.
The IsAlarm<i> set of fields allow defining multiple alarm statuses for a
multi-state tag. A tag can have:
Process Parameters
The fields in Table 24 define some alarm processing information concerning
digital tags. All fields are optional.
Table 24. Digital Tag - Process Parameters.
Format
Width
Opt/Mnd
Name
EVENTTAG
Integer
Initial value.
{0...15}
15
Optional
118
{Y, N}
Character
Optional
INITVAL
Range
Default
Parameter(s)
Description
None
9AKK101130D1382
Name
MAX_ROC
ALM_PROG
EVT_PROG
{0...999}
Integer
0
This field defines the maximum number
of state changes allowed for this tag
None
during 1 minute. If the number of changes
exceeds this limit, the tag is automatically
put out of scan. The function is useful for
filter exception reports due to hardware
failures in the digital contacts. Those nomeaningful exception reports might
significantly reduce or saturate the
playback storage area.
Optional
TRIP_NUM
Range
Default
Parameter(s)
Description
Integer
{0,1...100}
Optional
Character
{Y,N}
Optional
Character
{Y,N}
Optional
[mxhgrp]
None
None
9AKK101130D1382
119
120
9AKK101130D1382
Name
SER_NUMBER
Integer
SER_INDEX
Range
Default
Parameter(s)
Description
SER number.
{0, 1, 2}
Optional
[mxsedv]
Integer
SER index.
{0, 1...512}
Optional
[mxsept]
When the extended sequence of events (FC 241) is used, the blocks for
standard and summary sequence of events are allocated to the
addresses 5000 and 5001 and cannot be defined elsewhere.
The parameters listed in the following table are not included in the
Symphony Tab of the on-line configuration.
Table 26. Digital Tag - Symphony Input Parameters (cntd.).
Format
Width
Opt/Mnd
Name
SOELOG
SOETYPE
Range
Default
Parameter(s)
Description
Integer
Optional
Integer
{0, 1}
Optional
0 - Standard SOE,
None
None
1 - Summary SOE.
9AKK101130D1382
121
Name
SOETIMEOUT
SOETUNITS
Range
Default
Parameter(s)
Description
Integer
3
Optional
Integer
{0, 1}
Optional
0 - Seconds,
None
1 - Minutes.
SOEMAXEVT
SOEOUTLOG
Integer
5
Optional
0
The current sequence of event log is
closed if it reaches the maximum number None
of events. A new SOE log is opened to
collect exceeding events.
Integer
Optional
Command Parameters
The fields in Table 27 define the descriptive text strings associated with
each possible status of feedbacks from the process. All fields are optional.
They are meaningful only for those digital tags acquired from Symphony
modules that support feedback (DD and MSDD). See also Appendix A.
122
9AKK101130D1382
Name
FB1_0STATE
FB1_1STATE
FB2_0STATE
FB2_1STATE
FB3_0STATE
FB3_1STATE
FB4_0STATE
FB4_1STATE
9AKK101130D1382
Format
Width
Opt/Mnd
Description
Range
Default
Parameter(s)
Character
<string>
16
Optional
Character
16
Optional
Character
<string>
16
<blank>
Optional
[sztags]
Character
16
<blank>
Optional
[sztags]
Character
16
<blank>
Optional
[sztags]
Character
16
<blank>
Optional
[sztags]
Character
16
<blank>
Optional
[sztags]
Character
16
<blank>
Optional
[sztags]
123
Name
ALPRI_STCH
Description
Range
Default
Parameter(s)
{0, 1 ... 16}
Integer
0
This is the priority assigned to the tag
(defined as status only tag and not alarm [mxalpr] or [mxxapr]
tag) when a status change takes place
and the condition must be displayed. If
set to 0 then the default priority is
assigned.
Optional
124
9AKK101130D1382
Name
ALRMCMNT12
Integer
ALRMCTXT12
Description
Range
Default
Parameter(s)
<blank>
Optional
[mxalcm]
Character
<string>
80
<blank>
Optional
[szalcm]
Refer to the Alarm Comment definition chapter for more information about
the contents of these fields. Refer to the analogue sub-sections of the
generic tag definition for other alarm comment fields.
The on-line configuration allows selection of alarm comment either by index
(typing the number) or text (selecting from a list).
Network Parameters
Fields of this sub-section apply to both analog and digital tags. Refer to the
analogue sub-section of generic tag definition for details.
OPC Parameters
Fields of this sub-section apply to both analog and digital tags. Refer to the
analogue sub-section of generic tag definition for details.
9AKK101130D1382
125
Totalization Parameters
The fields in Table 30 allow defining totalizations associated to the digital
tag. They are meaningful only if the TOT_LOG field is defined as non zero
value (i.e. a totalization has been associated to the digital tag).
This kind of totalization collects maintenance information related to dual
state devices like motors, pumps, breakers, etc.
Basically, the totalization collects the number activations (i.e. the changes
from a steady to a operational condition), the operating time (sum of times in
the operational condition) and the total time elapsed from the last service of
the device the tag is associated to.
Those collected values are compared to maximum values defined by the
fields during processing.
Table 30. Digital Tag - Totalization Parameters.
Format
Width
Opt/Mnd
Name
HRTRUNSTAT
HRTMAXCHGS
HRTMAXRUN
{0, 1}
Integer
1
Optional
0
This field defines the status identifying
the operational condition of the dual-state None
device.
Integer
5
Optional
Integer
Optional
126
Range
Default
Parameter(s)
Description
0
None
0
None
9AKK101130D1382
Name
HRTMAXRUNU
HRTMAXSRV
Integer
1
Optional
Integer
Optional
HRTMAXSRVU
Integer
Optional
Range
Default
Parameter(s)
Description
0
None
0
None
0
None
9AKK101130D1382
127
Name
DEV_NAME
Range
Default
Parameter(s)
Description
<string>
Character
Device name.
20
Optional
Integer
Device number.
<integer>
15
Optional
1 - Printer,
None
2 - Node,
3 - Disk.
DEV_TYPE
Integer
Device type.
15
Optional
None
Integer
Device sub-type.
Optional
128
0
None
9AKK101130D1382
Name
MODTYPE
Description
Range
Default
Parameter(s)
Character
Module type.
20
<blank>
Optional
[sznam]
Character
Module revision.
<string>
<blank>
Optional
None
Note 1:
The name of devices are the names as known by Windows operating
system. That is, a printer name is the name as defined during the printer
definition (e.g. LPT1 or \\SERVERNODE\LASERPRT1), a node name is the
computer name (e.g. PGPSERVER1) as defined in the Network tab (access
from Settings and Control Panel) and a disk name is the identifier of disk
(e.g. C or D).
Note 2:
The diagnostic function surveys the availability of printers, the existence (or
the operability) of nodes and the space allocation of disks.
Nodes are checked issuing a ping through the Ethernet. All nodes, and not
only PGP nodes, can be submited for diagnostic check.
Disks are checked for allocation and alarm messages are issued when a
high or a very high limit is reached. Two optional registries, the
DiskUsageHighLimit and the DiskUsageVeryHighLimit, define the high and
very high limits of the disk space allocation.
9AKK101130D1382
129
Documentation Parameters
The field in Table 32 allows linking tag conditions and documentation.
Currently, PGP does not manage the field, but it may be loaded in the tag
database for a future use.
Refer to the analogue sub-section of generic tag definition for additional
fields.
Table 32. Digital Tag Documentation Parameters.
Format
Width
Opt/Mnd
Name
ALMDST
Integer
5
Range
Default
Parameter(s)
Description
Reference to status change
documentation
Optional
0
None
Application Parameters
Fields of this sub-section apply to both analog and digital tags. Refer to the
analogue sub-section of generic tag definition for details.
General Parameters
The fields in Table 33 define the engineering unit index or text, the floating
point presentation format, the presentation scale and other parameters
typical of analog tags. All fields are optional.
130
9AKK101130D1382
Name
EUDESC
NUMDECPL
I4_DATA
PLAYBACKCM
INITVAL
Range
Default
Parameter(s)
Description
Character
<string>
16
<blank>
Optional
Integer
{0...9}
Optional
Character
{Y,N}
1
Optional
N
If set, the value of the tag will be stored
into realtime database as a 32-bit signed None
integer.
Character
{Y,N}
Optional
Real
Initial value.
{lowlim...higlim}
15
Optional
[sztags]
None
None
None
9AKK101130D1382
131
Name
SCA_VAL_0
Range
Default
Parameter(s)
Description
Real
0% scale value.
{lowlim...higlim}
15
Optional
None
Real
{lowlim...higlim}
15
Optional
None
Real
Playback dead-band.
{lowlim...higlim}
10
Optional
None
Integer
Playback timer.
Optional
30
None
132
9AKK101130D1382
Name
PLBCOMPRDB
{0...100}
Integer
15
0
This value (expressed in percentage)
defines the dead-band for playback
None
compression algorithm. If defined, must
be wider than the significative change the
tag value can take.
Optional
FILTER_TAU
Range
Default
Parameter(s)
Description
Integer
0
This field defines a time constant for
filtering a tag value before updating the
None
realtime database. A value of zero will
disable filtering. The value stored in the
realtime database is computed using new
input (raw) value and old realtime
database value.
Optional
Real
10
Optional
{0...100}
0.0
None
Note 1:
In the range boxes, values of lowlim and higlim are defined by the
general formulas:
lowlim
= VAL0
higlim
= VAL0 + SPAN
Values of VAL0 and SPAN are defined in the alarm level definition subsection.
Note 2:
9AKK101130D1382
133
Vr
Vn-1
dt
FILTER_TAU
If the filter factor is zero (no filtering applied), the weight of the current value
in the realtime database is zero and the input raw value of the tag will be
stored in the realtime database.
Note 3:
Playback dead-band and timer provide a mechanism to allow re-building the
actual history of the tag in trend displays and trip analysis.
If they are defined, each time a new packet is going to be queued to
playback, its value is compared to last stored packet.
If the difference between values is greater than the defined playback deadband, and last stored packet is older than the defined playback timer, an
additional dummy packet is queued to playback with the same value and
quality as the old one and the same time as the new one. Then the new
packet is stored.
That allows a higher reliability in data trending. This mechanism allows you
to exactly re-build the step graphic trend of the tag in the historian mode
operating with such tags that can change suddenly after a long steady
period (i.e. currents or pressures).
134
9AKK101130D1382
This mechanism must be used carefully and only when necessary, as it may
considerably decrease the playback archive capacity.
The parameters listed in the following table are not included in the Analog
General Tab of the on-line configuration.
Table 34. Analog Tag - General Parameters (cntd.).
Format
Width
Opt/Mnd
Name
EUINDEX
Integer
{-1, 0...127}
-1
Real
{lowlim...higlim}
10
Optional
CONSTDELTA
Range
Default
Parameter(s)
Description
Optional
[mxeutx]
None
9AKK101130D1382
135
Process Parameters
Fields of this sub-section apply to both analog and digital tags. Refer to the
analogue sub-section of generic tag definition for details.
Name
CONVCODE
Format
Width
Opt/Mnd
Character
20
Optional
CONVMIN
Integer
15
Integer
15
Integer
15
<blank>
0
None
Optional
CONVOFFS
<string>
[sznam]
Optional
CONVMAX
Range
Default
Parameter(s)
Description
0
None
Optional
0
None
136
9AKK101130D1382
Command Parameters
Fields of this sub-section apply to digital tags only.
Name
ALPRI_3H
ALPRI_2H
Range
Default
Parameter(s)
{0, 1 ... 16}
Integer
2
Optional
0
This is the priority assigned to the tag
when a 3-high alarm condition takes
[mxalpr] or [mxxapr]
place. If set to 0 then the default priority is
assigned.
Integer
0
This is the priority assigned to the tag
when a 2-high alarm condition takes
[mxalpr] or [mxxapr]
place. If set to 0 then the default priority is
assigned.
Optional
9AKK101130D1382
Description
137
Name
ALPRI_H
ALPRI_L
ALPRI_2L
ALPRI_3L
ALPRI_HROC
ALPRI_LROC
Integer
2
Optional
0
This is the priority assigned to the tag
when a high alarm condition takes place. [mxalpr] or [mxxapr]
If set to 0 then the default priority is
assigned.
Integer
2
Optional
0
This is the priority assigned to the tag
when a low alarm condition takes place. If [mxalpr] or [mxxapr]
set to 0 then the default priority is
assigned.
Integer
Optional
Integer
2
Optional
0
This is the priority assigned to the tag
when a 3-low alarm condition takes
[mxalpr] or [mxxapr]
place. If set to 0 then the default priority is
assigned.
Integer
Optional
Integer
Optional
138
Range
Default
Parameter(s)
Description
[mxalpr] or [mxxapr]
[mxalpr] or [mxxapr]
[mxalpr] or [mxxapr]
9AKK101130D1382
Name
ALPRI_HDEV
ALPRI_LDEV
Range
Default
Parameter(s)
Description
Integer
Optional
Integer
Optional
[mxalpr] or [mxxapr]
[mxalpr] or [mxxapr]
The on-line configuration includes the fields above in the Alarm Level Tab
and in the Alarm Option Tab.
9AKK101130D1382
139
Two further fields allow definition of dynamic high and low alarm thresholds.
A dynamic threshold is defined by the name of an analog tag. In such a
case, the value of the alarm threshold is not fixed and defined at
configuration time, it is retrieved from the realtime database when the alarm
processing is being performed for the current analog tag.
Raw and current threshold values are compared to decide if an alarm
condition must be notified. Of course, the dynamic threshold tags and the
current analog tag should represent the same physical entity to be
comparable.
Typically, dynamic thresholds are calculated tags.
Table 37. Analog Tag - Alarm Level Parameters.
Format
Width
Opt/Mnd
Name
HINS_LIMIT
SPAN
Real
15
Optional
Real
Instrument span.
15
Optional
Range
Default
Parameter(s)
Description
0
None
0
None
140
Character
{Y, N}
Optional
None
9AKK101130D1382
Name
HI_PROG
{Y, N}
Optional
None
Real
{lowlim...higlim}
15
Character
1
H3ALARM
Range
Default
Parameter(s)
Description
Optional
None
H2ALARM
Character
{Y, N}
Optional
None
Real
{lowlim...higlim}
15
Optional
None
H23_PROG
Character
{Y, N}
Optional
None
Character
1
Optional
9AKK101130D1382
{Y, N}
None
141
Name
HALARM
Range
Default
Parameter(s)
Description
Real
{lowlim...higlim}
15
Optional
None
H_PROG
LALARM
Character
{Y, N}
Optional
None
Character
{Y, N}
Optional
Real
{lowlim...higlim}
15
Optional
None
None
L_PROG
Character
{Y, N}
Optional
None
Character
{Y, N}
Optional
142
None
9AKK101130D1382
Name
L2ALARM
L2_ACTIVE
L3ALARM
Range
Default
Parameter(s)
Description
{lowlim...higlim}
Real
15
Optional
0
This value (expressed in engineering
units) defines the second low alarm level. None
See Note 1 at the end of the table.
Character
{Y, N}
Optional
None
Real
{lowlim...higlim}
15
Optional
None
L23_PROG
Character
LI_ACTIVE
9AKK101130D1382
{Y, N}
Optional
None
Program activation flag on 2 and 3-Low
alarm.
{Y, N}
Optional
None
Real
15
Optional
Character
Character
1
VAL0
{Y, N}
Optional
None
143
Name
LI_PROG
Optional
Character
20
Optional
Character
20
Optional
Character
20
Optional
Real
{lowlim...higlim}
15
Character
1
HVARALMTAG
H2VARALMTG
H3VARALMTG
H2DELTA
Range
Default
Parameter(s)
Description
Optional
<string>
<string>
<string>
None
144
9AKK101130D1382
Name
H3DELTA
Format
Width
Opt/Mnd
Range
Default
Parameter(s)
Description
Real
{lowlim...higlim}
15
Optional
None
L2VARALMTG
20
Optional
Character
20
Optional
L3VARALMTG
<string>
<string>
Character
20
Optional
9AKK101130D1382
<string>
Character
145
Name
L2DELTA
Format
Width
Opt/Mnd
Description
Range
Default
Parameter(s)
{lowlim...higlim}
Real
15
0
This value (expressed in engineering
units) will be subtracted from the low
None
variable alarm tag value (if defined) to
determine the 2-Low variable alarm limit.
It is ignored if the L3VARALMTAG field is
defined.
Optional
{lowlim...higlim}
Real
15
0
This value (expressed in engineering
units) will be subtracted from the low
None
variable alarm tag value (if defined) to
determine the 3-Low variable alarm limit.
It is ignored if the L3VARALMTAG field is
defined.
Optional
Note 1:
In the range boxes, values of lowlim and higlim are defined by the
general formulas:
lowlim
= VAL0
higlim
= VAL0 + SPAN
Values of VAL0 and SPAN are defined in the alarm level definition subsection.
The SPAN field, defined in the database, is the full range of the tag (e.g.
the range of the instrument). The high instrument field, in the on-line
configuration, defines the high instrument limit and correspond to the
HINS_LIMIT field. They match only if the VAL0 field value is zero.
146
9AKK101130D1382
> H2ALARM
> HALARM
>
LALARM
> L2ALARM
>L3ALARM
>
VAL0
9AKK101130D1382
147
The alarm transition from a lower to a higher level alarm takes place
immediately when the raw value of tag exceeds the alarm limit threshold.
The alarm transition from a higher to a lower level alarm or from an alarm
level to a normal condition takes place when the raw value of tag is below
the alarm limit threshold minus the dead band.
Neither rate of change processing nor alarm dead-band definitions are
affected by instrument limits.
The last two fields in the table concern the instrument limit violation. They
allow defining actions to be performed on tag database value when an
instrument limit is exceeded.
Table 38. Analog Tag Alarm Option Parameters.
Format
Width
Opt/Mnd
Name
HR_ACTIVE
Character
1
{Y, N}
N
None
Optional
HROC_LIMIT
Range
Default
Parameter(s)
Description
{lowlim...higlim}
Real
15
0
This value (expressed in engineering
units) defines the maximum positive
None
change allowed for the tag value during a
period of one minute. If the value is
exceeded, a increasing rate of change
alarm is generated.
Optional
Character
1
Optional
148
9AKK101130D1382
Name
LR_ACTIVE
Character
1
Optional
LROC_LIMIT
Range
Default
Parameter(s)
Description
None
{lowlim...higlim}
Real
15
0
This value (expressed in engineering
units) defines the maximum negative
None
change allowed for the tag value during a
period of one minute. If the value is
exceeded, a decreasing rate of change
alarm is generated.
Optional
{Y, N}
Optional
None
Real
Alarm dead-band.
{lowlim...higlim}
15
0
This value (expressed in engineering
units) defines a dead-band below the
None
high alarm limits and above the low alarm
limits. A high (low) alarm will return to
normal only when the value is below
(above) the high (low) alarm limit minus
(plus) the alarm dead-band.
Character
1
ALARMDB
Optional
9AKK101130D1382
149
Name
LIMITDB
Real
Instrument dead-band.
15
0
This value (expressed in engineering
units) defines a dead-band above the
None
high instrument limit and below the low
instrument limit. A high (low) instrument
violation will be considered only when the
value is above (below) the high (low)
instrument limit plus (minus) the
instrument dead-band.
Optional
VIOL_CD
Range
Default
Parameter(s)
Description
Integer
{0, 1, 2}
Optional
None
Character
Optional
Note 1:
In the range boxes, values of lowlim and higlim are defined by the
general formulas:
lowlim
150
= VAL0
9AKK101130D1382
higlim
= VAL0 + SPAN
Values of VAL0 and SPAN are defined in the alarm level definition subsection.
When defining the alarm dead-band be sure the value does not exceed
the absolute difference between two consecutive alarm levels.
9AKK101130D1382
151
Name
ALRMCMNT3
ALRMCTXT3
ALRMCMNT4
ALRMCTXT4
ALRMCMNT5
ALRMCTXT5
ALRMCMNT6
ALRMCTXT6
152
Integer
Range
Default
Parameter(s)
Description
Low alarm comment index.
{1...100}
Optional
[mxalcm]
Character
<string>
80
<blank>
Optional
[szalcm]
Integer
{1...100}
Optional
[mxalcm]
Character
<string>
80
<blank>
Optional
[szalcm]
Integer
{1...100}
Optional
[mxalcm]
Character
<string>
80
<blank>
Optional
[szalcm]
Integer
{1...100}
Optional
[mxalcm]
Character
<string>
80
<blank>
Optional
[szalcm]
9AKK101130D1382
Name
ALRMCMNT7
ALRMCTXT7
ALRMCMNT8
ALRMCTXT8
ALRMCMNT9
ALRMCTXT9
ALRMCMNT10
Integer
Optional
[mxalcm]
Character
<string>
80
<blank>
Optional
[szalcm]
Integer
{1...100}
Optional
[mxalcm]
Character
<string>
80
<blank>
Optional
[szalcm]
Integer
{1...100}
Optional
[mxalcm]
Character
<string>
80
<blank>
Optional
[szalcm]
Integer
Optional
9AKK101130D1382
{1...100}
5
ALRMCTXT10
Range
Default
Parameter(s)
Description
Character
{1...100}
0
[mxalcm]
<string>
80
<blank>
Optional
[szalcm]
153
Name
ALRMCMNT11
Integer
5
Optional
ALRMCTXT11
Character
Range
Default
Parameter(s)
Description
Decreasing rate of change comment
index.
{1...100}
0
[mxalcm]
80
<blank>
Optional
[szalcm]
Network Parameters
Fields of this sub-section apply to both analog and digital tags. Refer to the
analogue sub-section of generic tag definition for details.
OPC Parameters
Fields of this sub-section apply to both analog and digital tags. Refer to the
analogue sub-section of generic tag definition for details.
Totalization Parameters
The fields in Table 40 allow definition of analog totalizations associated to
the analog tag. They are meaningful only if the TOT_LOG field is defined as
non zero value (i.e. a totalization has been associated to the tag).
154
9AKK101130D1382
Name
ENELOST
ENEBAD
ENEEUINDEX
Integer
1
Optional
Integer
1
Optional
Integer
{-1, 0 ...127}
-1
Optional
ENELOSC1M
Real
15
Optional
ENELOSC10M
Real
15
Real
15
Real
15
Real
15
Optional
9AKK101130D1382
[mxeutx]
0
0
None
Optional
ENELOSC8H
{0, 1}
None
Optional
ENELOSC1H
{0, 1}
None
Optional
ENELOSC30M
Range
Default
Parameter(s)
Description
0
None
0
None
155
Name
ENELOSCDAY
Format
Width
Opt/Mnd
Real
15
Optional
ENELOSCMON
Real
15
Real
15
Real
15
Real
15
Real
15
Real
15
Real
15
Optional
156
0
None
Optional
ENEHISC8H
0
None
Optional
ENEHISC1H
0
None
Optional
ENEHISC30M
0
None
Optional
ENEHISC10M
0
None
Optional
ENEHISC1M
0
None
Optional
ENELOSCYEA
Range
Default
Parameter(s)
Description
0
None
0
None
9AKK101130D1382
Name
ENEHISCDAY
Format
Width
Opt/Mnd
Real
15
Optional
ENEHISCMON
Real
15
Real
15
Real
15
Real
15
Real
15
Real
15
Real
15
Optional
9AKK101130D1382
0
None
Optional
ENERESC8H
0
None
Optional
ENERESC1H
0
None
Optional
ENERESC30M
0
None
Optional
ENERESC10M
0
None
Optional
ENERESC1M
0
None
Optional
ENEHISCYEA
Range
Default
Parameter(s)
Description
0
None
0
None
157
Name
ENERESCDAY
Real
15
Optional
ENERESCMON
Real
15
Real
15
0
None
0
None
Optional
ENERESCYEA
Range
Default
Parameter(s)
Description
Optional
0
None
Documentation Parameters
The fields in Table 41 allow linking tag conditions and documentation.
Currently, PGP does not manage these fields, but they may be loaded in the
tag database for a future use.
Refer to the analogue sub-section of the generic tag definition for additional
fields.
158
9AKK101130D1382
Name
ALMDLA
Integer
Range
Default
Parameter(s)
Description
Reference to low alarm documentation
5
Optional
ALMDHH
Integer
5
Optional
ALMDLL
ALMDSH
ALMDSL
ALMDHD
Integer
Optional
None
Integer
Optional
None
Integer
Optional
None
Integer
5
Optional
ALMDLD
Integer
5
Optional
9AKK101130D1382
0
None
0
None
159
Name
ALMDHR
Integer
5
Optional
ALMDLR
Integer
5
Range
Default
Parameter(s)
Description
0
None
0
None
Optional
Name
INSTR_TYPE
Range
Default
Parameter(s)
<string>
Character
Instrument type.
Optional
160
Description
9AKK101130D1382
Name
JBOX
Character
RTD_COMP
Description
Thermocouple junction box
Range
Default
Parameter(s)
<string>
<blank>
Optional
None
Character
14
Optional
<string>
<blank>
None
Application Parameters
Fields of this sub-section apply to both analog and digital tags. Refer to the
analogue sub-section of generic tag definition for details.
Alarm Comments
Outline
Alarm comments are descriptive texts associated with all possible alarm
conditions of analog and digital tags.
These texts are collected into a dedicated file on a Personal Computer using
standard packages like DBase III/IV or EXCEL or the SLDG package
(provided by the Bailey Engineering Work Stations). Then, the file must be
copied to the computer running the PGP application (if it is a different one)
for final download. Tags will refer to alarm comments by index.
Alternatively, texts can be included in the tag database file. The alarm
comment database will be filled when the tag database is processed.
A non-existing text will be added in the first available location of the alarm
comment database and an index will be assigned to it. After a new text has
been added, all tags using the same text will point to the same location of
alarm comment database.
9AKK101130D1382
161
In this case, the ALRMCTXTn field will be filled, and the ALRMCMNTn will
be omitted in the tag database.
This section describes the structure of the Alarm Comment Database (the
first option is chosen).
Name
ALARMINDEX
ALARMTEXT
Integer
Range
Default
Parameter(s)
Description
Alarm comment index.
{1...100}
Mandatory
[mxalcm]
Character
<string>
80
<blank>
Mandatory
[szalcm]
Engineering Units
Outline
An engineering unit (E.U) may be associated with an analog tag. The
engineering unit is a descriptive text used to physically qualify values, and
give meaning to the scale of analog tags.
These texts are usually collected into a dedicated file on a Personal
Computer using standard packages like DBase III/IV or EXCEL or the SLDG
package (provided by the Bailey Engineering Work Stations).
Then, the file must be copied to the computer running the application PGP
(if it is a different one) for final download.
162
9AKK101130D1382
Analog tags will refer to engineering units by their index. In this case, analog
tags can directly point to this database by means of the field EUINDEX,
while the field EUDESC can be omitted.
Alternatively, texts can be included into the tag database file. The
engineering unit database will be filled when the tag database is processed.
A non-existing text will be added in the first available location of the
engineering unit database, and an index will be assigned to it.
After a new text has been added, all tags using the same text will point to the
same location of engineering unit database.
In this case, the EUDTEXT field will be filled and the EUDINDEX will be
omitted in the tag database.
This section describes the structure of Engineering Units Database (if first
option is chosen).
Name
EUDINDEX
EUDTEXT
9AKK101130D1382
Integer
Range
Default
Parameter(s)
Description
Engineering unit index.
{1...127}
Mandatory
[mxeutx]
Character
<string>
16
<blank>
Mandatory
[sztags]
163
164
9AKK101130D1382
Name
LSDINDEX
Integer
LSDTEXT
Range
Default
Parameter(s)
Description
Logic state descriptor index.
{0...511}
Mandatory
Character
<string>
16
<blank>
Mandatory
[sztags]
Text Selector
Outline
Text selectors are descriptive texts that are associated to the values of a
particular type (TEXT) of analog tags.
These texts are usually collected into a dedicated file on a Personal
Computer using standard packages like Dbase III/IV or EXCEL or the SLDG
package (provided by the Bailey Engineering Work Stations).
Then, the file must be copied to the computer running the application PGP
(if it is a different one) for final download.
This section describes the structure of Text Selector Database.
9AKK101130D1382
165
Name
TEXTSINDEX
TEXTSTEXT
166
Integer
Range
Default
Parameter(s)
Description
Text selector index.
{0...9999}
Mandatory
[mxtxts]
Character
<string>
80
<blank>
Mandatory
[sztxts]
9AKK101130D1382
Outline
The main goal of alarm subsystem is to process up to three types of events
(information events, return-to-normal events and alarm events) and to notify
operators by a wide range of peripheral devices, such as LADs (Latest
Alarm Displays), printers, OJ (Operations Journal) and audible alarms.
All these events may be queued by a scan subsystem (in the simplest
scheme) as well as by calculation package, configuration subsystem or user
programs.
The following section shows how to configure alarm groups requested by
alarm subsystem to process these events. The configuration of color/blink
override can be found in Color/Blink Override on page 367.
9AKK101130D1382
167
The database builder may also perform export operations, creating a target
database file (DBase III/IV format) containing all items as they are currently
defined in the PGP internal database.
If a target database does not exist, the builder processor creates it using the
whole PGP database structure.
Alternatively, a target database file may be specified as template. In this
case, the builder processor updates the target database file handling only
the fields specified in it. The target database file may have just a single
alarm group, or may be a full or partial database file. It must contain all (and
only) fields to be exported.
General Parameters
The fields in Table 47 define the name and other additional parameters
used to identify the alarm group.
Table 47. Alarm Groups General Parameters.
Name
ALMINDEX
Format
Width
Opt/Mnd
Range
Default
Parameter(s)
{0, 1...272}
Integer
Optional
168
Description
9AKK101130D1382
Name
ALMNAME
Integer
Description
Alarm group name.
Range
Default
Parameter(s)
<string>
20
Character
<string>
64
<blank>
Optional
[szdesc]
Grouping Parameters
The fields in Table 48 define the level of an alarm group within the tree
structure and the sub-groups belonging to the alarm group.
9AKK101130D1382
169
Name
ALMLEVEL
Format
Width
Opt/Mnd
Integer
Range
Default
Parameter(s)
Description
{0,1...99}
Character
<string>
ALMLIST
Alarm list.
254
None
<blank>
None
Character
254
Optional
Description
UNACKD
Unacknowledged alarms.
ALMTYP
Alarm type.
ITMTYP
Item type.
170
9AKK101130D1382
Description
ALMGRP
Alarm group.
ALMPRI
Alarm priority.
Note 1:
Basically, there are two methods for specifying alarm lists. Either an external
file or a internal alarm list can be used.
Alarm list
The alarm list is directly included in the alarm group database file. A field
defines all sub-groups.
The alarm list is a sequence of group definitions (a comma is the separator
between alarm sub-groups) prefixed by the alarm attribute.
An example of alarm list is the following:
ALMGRP, 17,18,19,20,21,22,23,24,25;
This method can be used when the tag list does not exceed the maximum of
254 characters (upper limit for Dbase III/IV fields).
Alarm list file
The list of sub-groups is contained in an ASCII file. A field in the alarm group
database file allows definition of the file name. The alarm list file must be
located in the same folder hosting the alarm group database file: typically
this folder is \CONFIG\Almgr.
Since the alarm group name is referenced in the alarm list file, a unique
alarm list file for all alarm groups or an alarm list file for each alarm group
can be used. The syntax of the alarm list is the same defined above.
This method must be used when the total number of characters for the
alarm list definition is greater than 254.
9AKK101130D1382
171
Security Parameters
The fields in Table 50 define the security parameters of the alarm group.
Security parameters control the access to alarm pages. Only authorized
users can gain access.
172
9AKK101130D1382
Name
Format
Width
Opt/Mnd
Description
Range
Default
Parameter(s)
SEC_LEVEL
Integer
Security level.
{0, 1...16}
Optional
SEC_GROUP
{0, 1...32}
Integer
Security group.
Optional
Additional Parameters
The fields in Table 51 define other additional parameters of the alarm group.
9AKK101130D1382
173
Name
Format
Width
Opt/Mnd
Description
ALMSUMMTYP
Integer
3
Optional
Character
20
ALMSUMMTAG
Optional
PRIMDISP
Range
Default
Parameter(s)
<string>
<string>
Character
80
Optional
Audible Alarms
Outline
The audible alarm defines the tones PGP uses to notify alarms to the
operator. An audible can be played by the computer or played by horns
Symphony driven.
These audible tones are collected into a dedicated file on a Personal
Computer using standard packages like DBase III/IV or EXCEL.
Then, the file must be copied to the computer running the PGP application
(if it is a different one) for final download. Tags will refer to audible tones by
index.
174
9AKK101130D1382
Name
AUDINDEX
AUDCODE
Integer
Range
Default
Parameter(s)
Description
Audible index.
{0...32}
Mandatory
[mxaud]
Integer
Audible code.
{0...4}
Mandatory
0 = No sound,
None
1 = Beep sound,
2 = Wave file sound (continuous),
3 = Wave file sound (single shot),
4 = horn activation via RCM tag.
AUDFILE
Character
<string>
64
<blank>
Optional
[szdesc]
\Config\Sound folder.
AUDRCM
9AKK101130D1382
Character
<string>
20
<blank>
Optional
175
Calculation Subsystem
Calculations
Outline
The PGP calculation package gives the user the functions of a scientific
calculator using data from the process and the customer database. It allows
complex calculations to be defined, documented and run by people who
know the most about the process.
Calculated tags (tag type CALCANG or CALCDIG) are driven by the
calculation package by defining calculation blocks.
A calculation block is a set of statements that are executed at a given period
(minimum is 1 second). These statements look like mathematical
expressions that consist of operands, arithmetic operators, functions,
relational and logic operators, and control structures (such as WHILE-DO
and IF-THEN-ELSE).
The package also provides functions to interact with the steam table. Input
operands may be either system tags or local variables.
The example in the following section shows the typical structure of a
calculation block.
Calculation example
As an example, let consider a user wishes to do a very rough leak detection
system on a section of an oil pipeline. This can be accomplished by
checking that the input flow is roughly equivalent to the output flow, setting
an alarm digital tag if the difference is greater than a fixed value stored in a
lab data entry tag.
Assume the following tags have been defined:
P100 - Accumulator input from flow station at beginning of pipeline.
P200 - Accumulator input from flow station at end of pipeline.
PDIF - Lab data entry tag containing the maximum allowed difference.
176
9AKK101130D1382
9AKK101130D1382
177
The item Dif_Flow above is a local variable. Its value is meaningful within
the calculation and cannot be exported outside unless it is assigned to a
calculated analog tag.
Calculation Database
The calculation database is generated on a Personal Computer using
standard packages like DBase III/IV or EXCEL. Then, it must be copied to
the computer running the application PGP (if it is a different one) for final
import.
Calculation database is imported submitting the database file to the
database builder. During this phase, the field contents of the input file will be
used to compile PGP internal database structures following the directives
given by a field assignment cross-reference file, previously processed by
builder program DBXRF.
The database builder may also perform export operations, creating a target
database file (DBase III/IV format) containing all items as they are currently
defined in the PGP internal database.
If a target database does not exist, the builder processor creates it using the
whole PGP database structure.
Alternatively, a target database file may be specified as template. In this
case, the builder processor updates the target database file handling only
the fields specified in it.
The target database file may have just a single calculation or may be a full
or partial database file. It must contain all (and only) fields to be exported.
Calculation Definition
General Parameters
The fields in Table 54 define the name and other additional parameters
used to identify the calculation and to give an explicit reference to the
process.
The last four fields in Table 54 are not included within the Tab of general
parameters.
178
9AKK101130D1382
Name
Format
Width
Opt/Mnd
Description
Range
Default
Parameter(s)
CALCINDEX
Integer
{0, 1...300}
<string>
<blank>
Character
<string>
Optional
CALCNAME
Integer
20
CALCDESC
CALCINACT
NOSLAVE
[mxclbk]
[sznam]
64
<blank>
Optional
[szdesc]
Character
Deactivate flag.
{Y, N}
Optional
Character
{N, Y}
Optional
None
None
Log Parameters
The fields in Table 54 allow defining logs for operator actions and generic
information.
The on-line configuration does not provide a data entry Tab for such fields.
9AKK101130D1382
179
Name
Format
Width
Opt/Mnd
Description
PR_OPACT
Character
Optional
Character
{Y, N}
{Y, N}
Optional
None
Character
{Y, N}
PR_INFO
Optional
SV_OPACT
Character
1
SV_INFO
Optional
Range
Default
Parameter(s)
None
None
N
None
Frequency Parameters
The fields in Table 55 define the basic information to perform the
calculation.
180
9AKK101130D1382
Name
CALCFRQ
CALCUNITS
Range
Default
Parameter(s)
Description
Integer
Calculation period.
{1...9999}
Mandatory
Integer
{0...3}
Mandatory
None
None
{1...9999}
Integer
Calculation offset.
0
This field defines a delay added to the
execution time of the calculation. See the None
OFFSUNITS field also. Calculation offset
must always be less than calculation
period.
Optional
Integer
{0...3}
Optional
None
9AKK101130D1382
181
Name
SAMPLFRQ
Integer
Sampling period.
{0...99999}
Integer
{0...3}
Optional
SAMPLUNITS
Range
Default
Parameter(s)
Description
Optional
None
None
Note 1:
The calculation offset is applied to the base time of the calculation block,
that is the greatest integer multiple of the calculation period less or equal
than calculation period itself (second zero if period is seconds, minute zero if
period is minutes, midnight if period is hours). For instance, to have a
calculation block running every 30 minutes at minute 5, the offset must be 5
minutes.
182
9AKK101130D1382
Format
CALCFILE
Description
Range
Width
Default
Opt/Mnd
Parameter(s)
Character
254
Mandatory
<string>
<blank>
The full path allows locating the source
None
file anywhere. Usually source calculation
files are allocated within the
\PGP\Config\Calc folder.
Network Parameters
The fields in Table 57 refer to PGP network communication subsystem.
They are used when multiple PGP servers in a multi-master architecture
exchange data (values, alarm acknowledges, messages, configurations)
among them.
All fields are optional and they must be defined when servers (nodes) are
intended to cooperate in a multi-master architecture.
The fields reference the node definition. Refer to the Nodes database for
details.
9AKK101130D1382
183
Name
CNFNODMSK
Sequence {Y, N}
Optional
None
Character
Sequence {Y, N}
Sequence {Y, N}
Sequence {Y, N}
Character
16
CNFNODMS2
16
Optional
CNFNODMS3
Character
16
Optional
CNFNODMS4
Range
Default
Parameter(s)
Description
Character
16
Optional
16*N
16*N
The mask applies to nodes from 17 to 32. None
16*N
The mask applies to nodes from 33 to 48. None
16*N
The mask applies to nodes from 49 to 64 None
Name
Format
Width
Opt/Mnd
NUMPAR
Integer
3
Optional
184
Description
Number of parameters of the macro
function.
This field is used in the macro function
definition only.
Range
Default
Parameter(s)
0
None
9AKK101130D1382
Character Set
The character set of calculation package consists of all printable characters.
Blanks have no significance (unless used within a valid tag name). They
may be used to make the equation more readable.
Both upper case and lower case can be used.
TAB characters cannot precede and cannot be embedded within the
statements of a calculation. They can only be used beyond the end of a
statement to space a comment.
Operands
Operands are numbers, tag names, internal variables, constant names,
functions or macros.
Numbers
In the calculations, numeric values are processed as floating point numbers.
Expressions are calculated in double precision, but the inputs and the
results are single precision.
9AKK101130D1382
185
Tag Names
Tag names are used in the calculation blocks to represent values from the
realtime Database. Tag name may be up to 20 character long and must be
delimited by double quote characters.
In the calculation structure tag names represent a special kind of variables.
All the tags belonging to the calculation block are fetched from the realtime
Database at the same time, thus granting consistency to the data of the
block.
Internal Variables or Constants
The calculation packages allows the definition of internal variables that may
represent constants (physical values used in many different statements) or
intermediate results propagated from one statement to another.
The name of internal variables may be a maximum of 20 characters long
and must contain an alphabetic character in the first position. To be
distinguished by tag names, the names of the internal variables must not be
delimited by double quotes. The name of internal variables is case sensitive.
The number of internal variables is limited by the system parameter
MaxTagsPerCalculationBlock.
Functions
Functions are predefined names. Typically, they accept a number of input
parameters and produce a result. See the list of intrinsic functions for
capabilities and syntax.
Macros
Macros are predefined and reserved names. Typically, they accept a
number of input parameters and produce a number result. Refer to the
Calculation Macros manual for details on the syntax.
186
9AKK101130D1382
Comments
Comments may be placed anywhere to make the calculation block definition
more readable. The calculation processor recognizes the following
delimiters as comment:
C like comments
All characters delimited by /* (slash-asterisk) and */ (asterisk-slash) are
treated as a comment. The comment delimiters must be defined in the same
statement.
FORTRAN like comments
The characters following ! (exclamation mark) until the end of the line are
treated as comments.
The exclamation mark may be placed after an executable statement.
C++ like comments
The characters following // (double slash) until the end of the line are
treated as comments.
9AKK101130D1382
187
}
The statement continuation not necessarily must begin at column 1. It
can be indented to improve readability.
Insert a blank character before the continuation line symbol.
Expressions
An expression is a set of single items that, when evaluated, gives a result.
Operators act on variables (tag names, internal variables and constants) in
an expression.
In the syntax to exemplify expressions, the following symbols will be used:
<calc> - identifies an internal generic variable used as calculation result,
<ana_n> - identifies an generic analog value,
<dig_n> - identifies a generic digital value.
Constants, internal variables and tag names may represent analog and
digital values. For example, 5.6 may be a constant analog value; VAR may
be a variable analog value if VAR is an internal variable and PV-TAG may
be an analog value representing the current value of the tag PV-TAG in the
database.
Items related to expressions are listed in the following description.
188
9AKK101130D1382
Operator priorities
Operators are executed in order of priority, from highest priority to lowest.
Within the same priority, operators are executed from left-to-right or right-toleft, according to the Table 59.
Table 59. Calculation - Operator Priorities.
Operator
Priority
Order
OR
Left to Right
AND
Left to Right
NOT
Left to Right
Left to Right
+, -
Left to Right
*, /
Left to Right
*, /
Right to Left
- (prefix)
Left to Right
Parentheses
Parentheses may be used anywhere to affect the order of calculations.
Regardless of operator priority, operations within parentheses are evaluated
before operations outside those parentheses. Operations within
parentheses are evaluated according to Table 59.
Arithmetic Operators
Except the prefix minus, arithmetic operators apply to a couple of operands
and give a result according to the rules of arithmetic. The prefix minus
applies to a single operand. The Table 60 lists the arithmetic operands.
Operands are numeric entities.
9AKK101130D1382
189
Description
The plus (+) is the addition operator.
Syntax
<calc> = <ana_1> + <ana_2>
<calc> = - <ana_1>
Logical Operators
Except NOT, logical operators apply to a couple of operands and give a
result according to the rules of Boolean logic. The NOT operator applies to a
single operand. Table 61 lists the logic operands.
190
9AKK101130D1382
Description
Syntax
The AND operator returns the value 1 when both <calc> = <dig_1> AND <dig_2>
arguments are true (not equal to zero).
If one argument is false (zero) it returns zero.
OR
9AKK101130D1382
191
Relational operators
Relational operators compare two values. They return 1 if the relation is
true, 0 if the relation is false. Table 62 lists the relational operators.
Table 62. Calculation - Relational Operators.
Operator
Description
Syntax
<
The < (less than) operator gives a true result if the ( <ana_1> < <ana_2> )
first operand is less than the second.
==
( <ana_1> == <ana_2> )
>
<=
The <= (less than or equal to) operand gives a true ( <ana_1> <= <ana_2> )
result if the first operand is less than or equal to the
second.
!=
( <ana_1> != <ana_2> )
>=
192
9AKK101130D1382
Control Structures
Two control structures are available to calculation subsystem: IF-THENELSE and WHILE-DO.
IF-THEN-ELSE
The IF-THEN-ELSE structure is a compound operator. Its operands are one
logical expression (the IF clause) and several expressions (the THEN and
the ELSE clauses).
The processor evaluates the first (IF clause) expression. If that expression is
true (not equal to zero), the expressions comprised in the THEN branch are
evaluated and the expression comprised in the ELSE branch are skipped.
Otherwise the expressions comprised in the THEN branch are skipped and
the expressions comprised in the ELSE branch are evaluated.
The ELSE branch is optional and can be omitted. In such a case, if the IF
clause is false, no expressions of the IF-THEN-ELSE structure are
evaluated.
There are two formats allowed for the syntax of the IF-THEN-ELSE
structure: a C like structure and a Fortran like structure. The two structures
are shown in the following examples.
C like syntax
IF (expression_0)
{
expression_1_1
expression_2_1
....
expression_N_1
}
ELSE
{
expression_1_2
9AKK101130D1382
193
expression_2_2
....
expression_N_2
}
WHILE-DO
The WHILE-DO structure is a compound operator. Its operands are one
main expression (the WHILE clause) and several expressions which are
executed if the main expression is true (not equal to zero).
When all expressions have been executed, the main clause expression is
evaluated again; if its value continue to be true then all expressions are
executed again.
There are two formats allowed for the syntax of the WHILE-DO structure: a
C like structure and a Fortran like structure. The two structures are shown in
the following examples.
C like syntax
194
9AKK101130D1382
WHILE (expression_0)
{
expression_1
expression_2
....
expression_N
}
Using the WHILE-DO statement may cause never ending loops. In such
a case the main clause expression never become false and the
functionality of the calculation package will result compromised.
Be sure to avoid such cases carefully checking the main clause.
IF-THEN-ELSE and WHILE-DO structures can be nested. That is, the THEN
and the ELSE clause may include IF-THEN-ELSE and WHILE-DO
structures, the WHILE-DO body may include IF-THEN-ELSE and WHILEDO structures.
The Fortran like syntax of the IF-THEN-ELSE cannot be nested. Use the
C like syntax.
The C like syntax of the IF-THEN-ELSE and WHILE-DO structures
cannot have the two brackets which include the ELSE or WHILE clause
on the same line.
9AKK101130D1382
195
Intrinsic Functions
Functions are special operands, that return a value based on a set of input
parameters. Input parameters are enclosed between parentheses.
Functions follow the usual precedence rules of operands.
The following section gives a complete list and description of the intrinsic
functions available in the calculation subsystem.
For each function, the syntax lists the input parameters together the
engineering units (where applicable). The syntax of a generic function
having a total of n input parameters is shown below.
<calc> =
<function name>
(Input variables
[1]
<parameter 1>,
[2]
<parameter 2>,
......................
[n]
<parameter n>,
End Variables)
196
9AKK101130D1382
Execution Functions
These functions affect the algorithm execution of a calculation.
Table 63. Calculation - Execution Functions.
Function
EXITCALC
Description
The function forces exit from the
calculation block.
Syntax
Eng. Unit
<calc> =
EXITCALC
(Input variables
End Variables)
9AKK101130D1382
197
Logical Functions
These functions perform logical calculations. They are an optimization of the
basic logical operators AND and OR.
Table 64. Calculation - Logical Functions.
Function
F_AND
Description
Syntax
Eng. Unit
<digital> =
The function returns the value 1 when
arguments are true (not equal to zero). If F_AND
one argument is false (zero) it returns
(Input variables
zero.
<digital_1>,
A variable number of arguments can be
<digital_2>,
passed to the function and only good
.......................
quality values are taken into account.
A maximum of 99 input parameters can <digital_n>
be defined.
End Variables)
F_OR
<digital> =
The function returns the value 1 when
one argument is true (not equal to zero). F_OR
If both arguments are false (zero) it
(Input variables
returns zero.
<digital_1>,
A variable number of arguments can be
<digital_2>,
passed to the function and only good
.......................
quality values are taken into account.
A maximum of 99 input parameters can <digital_n>
be defined.
End Variables)
198
9AKK101130D1382
Mathematical Functions
These functions perform mathematical calculations. They are typical
mathematical functions.
Table 65. Calculation - Mathematical Functions.
Function
ABS
Description
The function returns the absolute
value of a number.
Syntax
Eng. Unit
<calc> =
ABS
(Input variables
<analog>
End Variables)
ACOS
<calc> =
ACOS
(Input variables
<angle>
rad
End Variables)
ASIN
<calc> =
ASIN
(Input variables
<angle>
rad
End Variables)
ATAN
<calc> =
ATAN
(Input variables
<angle>
rad
End Variables)
9AKK101130D1382
199
Description
Syntax
<calc> =
(Input variables
Eng. Unit
AVR
<analog_1>,
<analog_2>,
.......................
<analog_n>
End Variables)
COS
rad
End Variables)
EXP
INT
<calc> =
EXP
(Input variables
<analog>
End Variables)
<integer part> =
INT
(Input variables
<real number>
End Variables)
200
9AKK101130D1382
Description
The function computes the
interpolation of pair of values in a
table.
The interpolation value is the entry
within the table. Pairs must be
ordered in increasing order of Xi
elements.
Syntax
Eng. Unit
<calc> =
INTERP
(Input variables
<interpolation value>,
X1, Y1, ... , Xn, Yn
End Variables)
<calc> =
LN
(Input variables
<positive real>
End Variables)
LOG10
MAX
<calc> =
(Input variables
MAX
<analog_1>,
.......................
<analog_n>
End Variables)
9AKK101130D1382
201
Description
Syntax
<calc> =
(Input variables
Eng. Unit
MIN
<analog_1>,
.......................
<analog_n>
End Variables)
PIGREEK
<calc> =
PIGREEK
(Input variables
End Variables)
SIGN
SIN
<calc> =
SIGN
(Input variables
<analog>
End Variables)
rad
End Variables)
SQR
<calc> =
SQR
(Input variables
<analog>
End Variables)
202
9AKK101130D1382
Description
The function returns the tangent of
an angle.
Syntax
Eng. Unit
<calc> =
TAN
(Input variables
<angle>
rad
End Variables)
VALMAX
<calc> =
(Input variables
VALMAX
<% validity>,
<analog_1>,
.......................
<analog_n>
End Variables)
9AKK101130D1382
203
Description
Syntax
<calc> =
(Input variables
Eng. Unit
VALMED
<% validity>,
<% deviation>,
<analog_1>,
.......................
<analog_n>
End Variables)
<calc> =
(Input variables
VALMIN
<% validity>,
<analog_1>,
.......................
<analog_n>
End Variables)
204
9AKK101130D1382
Tag Functions
The functions allow operating on tags and interacting with the configuration
database and the realtime database.
Table 66. Calculation - Tag Functions.
Function
FORCE_APPL1
Description
The function forces the application
bit 1 of a tag, irrespective of the
quality of input tag.
Syntax
Eng. Unit
<tag> =
FORCE_APPL1
(Input variables
<tag>,
<digital>
End Variables)
FORCE_APPL2
<tag> =
FORCE_APPL2
(Input variables
<tag>,
<digital>
End Variables)
FORCE_APPL3
<tag> =
FORCE_APPL3
(Input variables
<tag>,
<digital>
End Variables)
<tag> =
FORCE_QUALITY The function forces the quality of a
tag, irrespective of the quality of input FORCE_QUALITY
tag.
(Input variables
Value 0 forces good quality, value 1
<tag>,
forces bad quality.
<digital>
End Variables)
9AKK101130D1382
205
GETINFO
Description
Syntax
<tag> =
<calc> =
Eng. Unit
DESCR_OR
(Input variables
<elem_1>, ... ,<elem_n>,
<qual_1>, ... ,<qual_n>
End Variables)
GETINFO
(Input variables
<system parameter>
End Variables)
GETTAG
<calc> =
GETTAG
(Input variables
<tag>,
<config. parameter>
End Variables)
SAVEVALUE
206
9AKK101130D1382
Description
The function writes database
configuration parameters of tags.
Configuration parameters are
identified by a symbolic code as
defined in the Configuration
Parameter Table (see Appendix A).
Syntax
Eng. Unit
<calc> =
SETTAG
(Input variables
<tag>,
<config. parameter>,
<parameter value>
End Variables)
TEST_ALARM
<digital> =
TEST_ALARM
It returns 1 if the tag is alarmed and 0 (Input variables
if not.
<tag>
End Variables)
<digital> =
TEST_INSERTED
(Input variables
<tag>
End Variables)
TEST_QUALITY
<digital> =
(Input variables
TEST_QUALITY
<tag>
End Variables)
TEST_UNACKED
<digital> =
(Input variables
TEST_UNACKED
<tag>
End Variables)
9AKK101130D1382
207
Description
The function returns the application
bit 1 of the quality tag.
Syntax
Eng. Unit
<digital> =
TEST_APPL1
(Input variables
<tag>
End Variables)
TEST_APPL2
<digital> =
TEST_APPL2
(Input variables
<tag>
End Variables)
TEST_APPL3
<digital> =
TEST_APPL3
(Input variables
<tag>
End Variables)
208
9AKK101130D1382
Time Functions
The functions deal with the time and its components. They allow retrieving
information on time and date. Most of them do not require parameters at all.
Table 67. Calculation - Time Functions.
Function
DAY
Description
Syntax
<calc> =
(Input variables
Eng. Unit
DAY
End Variables)
DAYOFWEEK
<calc> =
<calc> =
(Input variables
DAYOFWEEK
The value is in the range 0 to 6 and 0 (Input variables
refers to sunday.
End Variables)
DAYOFYEAR
DAYOFYEAR
End Variables)
9AKK101130D1382
209
Description
Syntax
Eng. Unit
sec
<month of time1>,
<year of time1>,
<hour of time1>,
<minute of time1>,
min
<second of time1>,
sec
<day of time2>,
<month of time2>,
<year of time2>,
<hour of time2>,
<minute of time2>
min
<second of time2>
sec
End Variables)
HOUR
JULSEC
<calc> =
<calc> =
(Input variables
sec
JULSEC
The reference date is assumed to be (Input variables
January, 1 1991.
End Variables)
MINUTE
min
MINUTE
End Variables)
210
9AKK101130D1382
Description
Syntax
<calc> =
(Input variables
Eng. Unit
MONTH
End Variables)
SECOND
<calc> =
(Input variables
sec
SECOND
End Variables)
WEEKOFYEAR
<calc> =
(Input variables
WEEKOFYEAR
End Variables)
YEAR
9AKK101130D1382
211
Steam Functions
The functions allow computing and retrieving data on steam and water
properties. They involve temperature, pressure, enthalpy, entropy and
specific volume of steam.
Table 68. Calculation - Steam Functions.
Function
CP_at_TP
Description
Syntax
<specific heat> =
The function computes the specific
heat, relative to steam and water, as CP_at_TP
function of temperature and
(Input variables
pressure.
<temperature>,
<pressure>
Eng. Unit
kJ/kg/C
C
bar
End Variables)
DV_at_TP
<water viscosity> =
kg/s m
DV_at_TP
(Input variables
<temperature>,
<pressure>
bar
End Variables)
H_at_PS
kJ/kg
<pressure>,
bar
<entropy>
kJ/kg C
End Variables)
H_at_TP
kJ/kg
C
bar
End Variables)
212
9AKK101130D1382
Description
The function computes the water
conducibility, relative to steam and
water, as function of temperature
and pressure.
Syntax
<water conducibility> =
Eng. Unit
W/m C
K_at_TP
(Input variables
<temperature>,
<pressure>
bar
End Variables)
P_sat_at_T
<saturation pressure> =
bar
PSAT_at_T
(Input variables
<temperature>
End Variables)
S_at_PH
<entropy> =
kJ/kg C
S_at_PH
(Input variables
<pressure>,
bar
<enthalpy>
kJ/kg
End Variables)
S_at_TP
<entropy> =
kJ/kg C
S_at_TP
(Input variables
<temperature>,
<pressure>
bar
End Variables)
9AKK101130D1382
213
Description
The function computes the
temperature, relative to steam and
water, as function of pressure and
enthalpy.
Syntax
Eng. Unit
C
<temperature> =
T_at_PH
(Input variables
<pressure>,
bar
<enthalpy>
kJ/kg
End Variables)
T_at_PS
<temperature> =
T_at_PS
(Input variables
<pressure>,
bar
<entropy>
kJ/kg C
End Variables)
T_sat_at_P
<saturation temp.> =
TSAT_at_P
(Input variables
<pressure>
bar
End Variables)
V_at_TP
<specific volume> =
The function computes the specific
volume, relative to steam and water, V_at_TP
as function of temperature and
(Input variables
pressure.
<temperature>,
<pressure>
m3/kg
C
bar
End Variables)
214
9AKK101130D1382
Description
The function computes the specific
heat of a gas as function of the
temperature.
Syntax
<specific heat> =
<enthalpy> =
9AKK101130D1382
C
nbr
kJ/kg
H_GAS
(Input variables
The gas is defined according to the
<temperature>,
gas table. See Appendix A for the list
<gas index>
of gas indexes.
End Variables)
M_GAS
kJ/kg C
CP_GAS
(Input variables
The gas is defined according to the
<temperature>,
gas table. See Appendix A for the list
<gas index>
of gas indexes.
End Variables)
H_GAS
Eng. Unit
C
nbr
kg/Mole
nbr
215
Description
Syntax
Eng. Unit
kJ/kg C
C
bar
nbr
End Variables)
V_GAS
m3/Kg
C
bar
nbr
End Variables)
216
9AKK101130D1382
Description
SEAW
Syntax
<property> =
Eng. Unit
Table 71
SEAW
(Input variables
<temperature>,
<salt concentration>,
<function index>
nbr
End Variables)
Index
Eng. Unit
Enthalpy
kJ/kg
Specific Heat
kJ/kg C
Density
kg/m3
Thermal Conducibility
W/m C
Dynamic Viscosity
kg/s m
9AKK101130D1382
217
218
9AKK101130D1382
Description
The function computes the specific
heat of flue gas as function of the
temperature and the flue gas
composition. An index specifies if
flue gas composition is expressed in
weight (index = 0) or volume (index =
1).
Syntax
<specific heat> =
Eng. Unit
kJ/kg C
CP_FGAS_T
(Input variables
<temperature>,
<index>,
nbr
<carbon bi-oxide>,
<oxygen>,
<carbon oxide>,
<sulphur bi-oxide>,
<water>,
%
%
<argon>
End Variables)
H_FGAS_T
<enthalpy> =
kJ/kg
H_FGAS_T
(Input variables
<temperature>,
<index>,
nbr
<carbon bi-oxide>,
<oxygen>,
<carbon oxide>,
<sulphur bi-oxide>,
<water>,
<argon>
End Variables)
9AKK101130D1382
219
Description
The function computes the entropy of
flue gas as function of the
temperature, the pressure and the
flue gas composition. An index
specifies if flue gas composition is
expressed in weight (index = 0) or
volume (index = 1).
Syntax
<entropy> =
Eng. Unit
kJ/kg C
S_FGAS_TP
(Input variables
<temperature>,
<index>,
bar
<pressure>,
nbr
<carbon bi-oxide>,
<oxygen>,
<carbon oxide>,
<sulphur bi-oxide>,
<water>,
%
%
<argon>
End Variables)
220
9AKK101130D1382
Description
The function computes the
temperature of flue gas as function of
the enthalpy and the flue gas
composition. An index specifies if
flue gas composition is expressed in
weight (index = 0) or volume (index =
1).
Syntax
<temperature> =
Eng. Unit
C
T_FGAS_H
(Input variables
<enthalpy>,
kJ/kg
<index>,
nbr
<carbon bi-oxide>,
<oxygen>,
<carbon oxide>,
<sulphur bi-oxide>,
<water>,
%
%
<argon>
End Variables)
T_FGAS_PS
<temperature> =
T_FGAS_PS
(Input variables
<pressure>,
bar
<entropy>,
kJ/kg C
<index>,
nbr
<carbon bi-oxide>,
<oxygen>,
<carbon oxide>,
<sulphur bi-oxide>,
<water>,
%
%
<argon>
End Variables)
9AKK101130D1382
221
Description
The function computes the
stechiometric air in the fuel as
function of the fuel composition.
The stechiometric air is returned in
kg dry air/kg fuel.
Syntax
<air in fuel>=
Eng. Unit
kg/kg
AIR_MIN
(Input variables
<carbon>,
<hydrogen>,
<sulphur>,
<oxygen>
End Variables)
CP_FCOMB_T
<specific heat> =
The function computes the specific
heat of air and fuel as function of the CP_FCOMB_T
temperature and the fuel
(Input variables
composition.
<temperature>,
kJ/kg C
<carbon>,
<hydrogen>,
<sulphur>,
<oxygen>,
<nitron>,
<dry air/fuel>
kg/kg
End Variables)
222
9AKK101130D1382
Description
The function computes the enthalpy
of air and fuel as function of the
temperature and the fuel
composition.
Syntax
<enthalpy> =
Eng. Unit
kJ/kg
H_FCOMB_T
(Input variables
<temperature>,
<carbon>,
<hydrogen>,
<sulphur>,
<oxygen>,
<nitron>,
<dry air/fuel>
kg/kg
End Variables)
S_FCOMB_TP
kJ/kg C
<pressure>,
bar
<carbon>,
<hydrogen>,
<sulphur>,
<oxygen>,
<nitron>,
<dry air/fuel>
kg/kg
End Variables)
9AKK101130D1382
223
Description
The function computes the
temperature of air and fuel as
function of the enthalpy and the fuel
composition.
Syntax
<temperature> =
Eng. Unit
C
T_FCOMB_H
(Input variables
<enthalpy>,
kJ/kg
<carbon>,
<hydrogen>,
<sulphur>,
<oxygen>,
<nitron>,
<dry air/fuel>
kg/kg
End Variables)
T_FCOMB_PS
<temperature> =
The function computes the
temperature of air and fuel as
T_FCOMB_PS
function of the pressure, entropy and
(Input variables
the fuel composition.
<pressure>,
bar
<entropy>,
kJ/kg C
<carbon>,
<hydrogen>,
<sulphur>,
<oxygen>,
<nitron>,
<dry air/fuel>
kg/kg
End Variables)
224
9AKK101130D1382
9AKK101130D1382
225
Description
The function computes the specific
heat of wet air as function of the
temperature and absolute humidity.
The absolute humidity is expressed
in kg vapor/kg dry air.
Syntax
Eng. Unit
kJ/kg C
<specific heat> =
CP_AIR_T
(Input variables
<temperature>,
<absolute humidity>
kg/kg
End Variables)
H_AIR_T
kJ/kg
<enthalpy> =
H_AIR_T
(Input variables
<temperature>,
<absolute humidity>
kg/kg
End Variables)
226
9AKK101130D1382
Description
Syntax
Eng. Unit
kJ/kg C
C
bar
kg/kg
End Variables)
T_AIR_H
<temperature> =
T_AIR_H
(Input variables
<enthalpy>,
kJ/kg
<absolute humidity>
kg/kg
End Variables)
T_AIR_PS
<temperature> =
T_AIR_PS
(Input variables
<pressure>,
bar
<entropy>,
kJ/kg C
<absolute humidity>
kg/kg
End Variables)
WHY
<humidity> =
WHY
(Input variables
<dry bulb temp.>,
9AKK101130D1382
C
bar
%
227
Description
READFILE
Syntax
<calc> =
(Input variables
Eng. Unit
READFILE
<file name>,
<record number>,
<word number>,
<format>
End Variables)
WRITEFILE
<calc> =
(Input variables
<record number>,
WRITEFILE
<file name>,
<word number>,
<format>,
<value>
End Variables)
Description
BYTE
USHORT
SHORT
228
9AKK101130D1382
Description
UINT
INT
FLOAT
DOUBLE
9AKK101130D1382
229
Historical Functions
Historical functions involve a single database tag. Samples are collected at
fixed time intervals and at calculation time they are processed to provide the
calculation result.
Table 77. Calculation - Historical Functions.
Function
COUNTER
Description
Syntax
Up/down counter.
<calc> =
COUNTER
<reset flag>,
(Input variables
<pv_tag>,
<threshold value>,
<increment value>,
<initial value>,
3
End Variables)
DELAY
Delay.
<calc> =
DELAY
<tag>,
(Input variables
<reset flag>,
2
End Variables)
230
9AKK101130D1382
Description
Derivative.
Syntax
<calc> =
EVENTTIME
(Input variables
<tag>,
<value>
End Variables)
FILT
Filter.
<calc> =
FILT
(Input variables
Vn = Vn1*(tau/(dt+tau)+Vi(dt/(dt+tau) <pv_tag>,
where:
<time constant>,
Vn1 - previous FILT calculated value, <reset flag>,
Vi - current sampled value,
<initial value>
dt - sampling time.
End Variables)
9AKK101130D1382
231
Description
Gradient.
Syntax
<calc> =
Historical average.
<calc> =
H_AVR
(Input variables
GRAD
<pv_tag>,
<min. % good>,
<discharge bad flag>,
<number of samples>
Bad samples are discharged if the
discharge flag is set to 0. Elsewhere, End Variables)
they are taken into account in
computing the average.
232
9AKK101130D1382
Description
Historical maximum.
Syntax
<calc> =
Historical minimum.
<calc> =
9AKK101130D1382
233
Description
Syntax
Historical sum.
<calc> =
H_SUM
<pv_tag>,
(Input variables
<min. % good>,
<discharge bad flag>,
<number of samples>
End Variables)
Bad samples are discharged if the
discharge flag is set to 0. Elsewhere,
they are taken into account in
computing the sum.
INTEG
Integral.
<calc> =
INTEG
The function returns the integral of
last sampled values according to the (Input variables
following formula:
<pv_tag>,
Vn = Vn1 + (Vi * dt)
<reset flag>,
where:
<initial value>,
Vn1 - previous INTEG calculated
3
value.
End Variables)
Vi - current sampled value.
dt - sampling time.
When the reset flag is set to 1, the
function is set to the initial value.
234
9AKK101130D1382
Description
Historical value.
Syntax
<calc> =
<year>,
<hour>,
<minute>,
min
<second>,
sec
<offset>
End Variables)
HIST_WRT
<calc> =
HIST_WRT
sample.
<year>,
<hour>,
(Input variables
<minute>,
min
<second>,
sec
<offset>,
<value>
End Variables)
9AKK101130D1382
235
Description
Historical regression.
Syntax
<calc> =
HIST_REGR
(Input variables
<hist group name>,
<tag>,
<filter tag>,
<filter high value>,
<Filter low value>,
<day>,
<month>,
<year>,
<hour>,
<minute>,
min
<second>,
sec
<offset value>,
<offset time unit>,
<number of samples>,
<analisys interval>,
<interval time unit>,
<min. % good>,
<discharge bad flag>,
<angle coeff>,
<const coeff>,
<error on angle coeff>,
<error on const coeff>,
<standard error>
End Variables)
236
9AKK101130D1382
Description
Syntax
Standard deviation.
<calc> =
SDEV
(Input variables
<pv_tag>,
<min. % good>,
<discharge bad flag>,
<number of samples>
End Variables)
Timer.
<calc> =
TIMER
(Input variables
<pv_tag>,
<timing code>,
<delay>,
sec
2
End Variables)
NUM_ALARM
NUM_ALARM
(Input variables
9AKK101130D1382
237
238
9AKK101130D1382
Historic group.
A group of tags is gathered for periodical archiving or sampled and
periodically processed for archiving. Different kinds of processing criteria are
selectable. Bad samples may be discharged or taken into account.
Post trip group.
A group of tags is gathered for archiving when a digital tag, defined as
trigger of the post trip, changes to an alarm condition. Data are archived
beginning from the pre trip time to the post trip time.
9AKK101130D1382
239
There are both mandatory and optional parameters. A field (type of the trend
group) allows the identification of group and establishes which other fields
must be filled in to complete the configuration. Additional fields are listed in
the specific sections following this one.
General Parameters
The fields in Table 78 define the name and other additional parameters
used to identify and characterize the trend group.
Table 78. Generic Trend Group General Parameters.
Format
Width
Opt/Mnd
Name
GROUPINDEX
GROUPNAME
GROUPUID
GROUPDESC
240
Description
Range
Default
Parameter(s)
{0, 1...100}
Integer
Group index.
6
Optional
Character
Group name.
<string>
20
<blank>
Mandatory
Character
<string>
36
Optional
Character
Group description.
[sznam]
<string>
64
<blank>
Optional
[szdesc]
9AKK101130D1382
Name
EUINDEX
Range
Default
Parameter(s)
Description
{-1, 0 ...127}
Integer
-1
This field defines the index into the
engineering unit database. It can be used [mxeutx]
to assign a unique engineering unit to the
group. It supersedes the engineering
units of the tags belonging to the group.
Optional
Character
<string>
16
<blank>
Optional
GROUPCLASS
ARCHTYPE
None
Integer
Optional
Character
Type of archiving.
<string>
Mandatory
None
Character
1
Optional
9AKK101130D1382
{Y, N}
None
241
Note 1:
The GROUPUID code is internally generated the first time a group is added
to the PGP database (i.e. each time a group database build follows a
database initialization).
Add the GROUPUID field to the group database and left it initially blank
when the group database file is filled in.
Following a group database build, an un-build operation must be executed
in order for the GROUPUID field is filled.
If the GROUPUID is left blank, the group cannot be replaced later within the
PGP database. An error message will be issued for a duplicate group, since
a new GROUPUID is generated. A PGP database initialization only allows
replacing (actually adding) the group.
Once assigned, the GROUPUID may be kept unchanged for the whole
history of a group. The group name or the group index may change, the
GROUPUID is not affected. That allows you to keep track of a group during
the history of the application.
As a general rule, perform a database export immediately after a build
operation in order to fill in a non-assigned GROUPUID field within a group
database file.
The Table 79 lists all types of trend groups. The third column is the key to
establish the additional parameters to fully configure the group. In the
following pages, specific sections exist to define each kind of group.
Depending on the type of trend group refer to the section corresponding to
the kind.
Table 79. Trend Group - Archiving Types.
Type
Description
Kind
REALTIM
realtime group.
realtime.
INST
Historical.
AVERAGE
Historical.
TOTAL
Historical.
242
9AKK101130D1382
Description
Kind
MIN
Historical.
MAX
Historical.
COUNT
Counting group.
Historical.
MONITOR
Monitoring group.
Historical.
RATIO
Ratio group.
Historical.
TRIP
Post trip.
Display Parameters
The fields in Table 80 define some displaying parameters of the trend group.
Table 80. Generic Trend Group Display Parameters.
Format
Width
Opt/Mnd
Name
TIMESPAN
Integer
Optional
Range
Default
Parameter(s)
Description
0
None
Integer
{0...5}
Optional
9AKK101130D1382
None
243
Name
DISPFRQ
Range
Default
Parameter(s)
Description
Integer
0
It is the time interval between two
consecutive values when a trend group is None
displayed as a table (discrete values).
Optional
CURVETYPE
Optional
None
Integer
{0,1,2}
Optional
None
Integer
{0...5}
0 - default (interpolation),
1 - step,
2 - interpolation.
Link Parameters
The fields in Table 81 define links to displays or other trend groups for
exploring purposes.
244
9AKK101130D1382
Name
PRIMDISP
FWDNAME
BWDNAME
ESCNAME
ENTNAME
Format
Width
Opt/Mnd
Range
Default
Parameter(s)
Character
<string>
80
<blank>
Optional
Character
<string>
20
Optional
<blank>
This field defines the name of another
group chained as following to the current [sznam]
one.
Character
<string>
20
<blank>
Optional
Character
<string>
20
<blank>
Optional
Character
<string>
20
<blank>
Optional
9AKK101130D1382
Description
None
[sznam]
[sznam]
[sznam]
245
Log Parameters
The fields in Table 82 allow defining logs for operator actions and generic
information.
Table 82. Generic Trend Group General Parameters.
Format
Width
Opt/Mnd
Name
PR_OPACT
PR_INFO
SV_OPACT
SV_INFO
Character
{Y, N}
Optional
Character
{Y, N}
Optional
Character
{Y, N}
1
Optional
N
If set, database modifications and all
other operator actions concerning this
None
group will be logged to Operator Journal.
Character
{Y, N}
Optional
246
Range
Default
Parameter(s)
Description
None
None
None
9AKK101130D1382
Name
TAGFILE
Character
254
TAGLIST
Range
Default
Parameter(s)
<string>
<blank>
Optional
Character
<string>
254
<blank>
{0...60}
Optional
NUMTAGS
Description
Integer
3
Optional
None
0
If not specified, it is assumed to be the
[grptag]
total number of tags in the group as found
in the tag list or tag file (see next fields). If
specified, it must be greater or equal to
the total number of defined tags. If
greater, it keeps space allocated to allow
adding tags later on without collected
historical data are lost (i.e. the group
initialization is not required).
The field is not included within the fileds
of the on-line configuration Tab.
Note 1:
Basically, there are two methods for specifying tags belonging to a trend
group. Either an external tag file or a internal tag list can be used.
9AKK101130D1382
247
Tag list.
The list of tags is directly included in the trend group database file. A field
defines all tags.
The tag list is a sequence of tag definitions (a semicolon is the separator
between tag definitions). Each definition concerns a tag and is a set of three
items: the tag name, the low and the high limits for trend format
presentations (a comma is the separator between items).
An example of tag list is the following:
TAG-1, 0, 100; TAG-2, -10, 10; TAG-3, 0, 200;
This method can be used when the tag list does not exceed the maximum of
254 characters (upper limit for Dbase III/IV fields).
The on-line configuration provides a dialog window to enter the tag list.
Select the entry in the tag list and then type the tag name and the display
limits in the fields of the dialog.
Tag file.
The list of tags is contained in an ASCII file. A field in the trend group
database file allows definition of the file name. The tag file must be located
in the same folder hosting the trend group database file: typically this folder
is PGP\Config\Group. Since the trend group name is referenced in a tag file,
a unique tag file for all groups or a tag file for each group may be used. The
syntax of the tag list is the same defined above.
This method must be used when the total number of characters for the tag
list definition is greater than 254.
Below the definition of two tag lists is shown.
$BEGIN_GROUP GROUP-01
PV-TAG-01, 0, 100; PV-TAG-02, 0, 110;
PV-TAG-03, 0, 120; PV-TAG-04, 0, 130;
PV-TAG-05, 0, 140; DI-TAG-01, 0, 1;
DI-TAG-02, 0, 2;
DI-TAG-03, 0, 3;
$END_GROUP
248
9AKK101130D1382
$BEGIN_GROUP GROUP-02
PV-CAL-01, 0, 100;PV-CAL-02, 0, 100;
PV-CAL-03, 0, 6000; DI-CAL-01, 0, 1;
$END_GROUP
9AKK101130D1382
249
Network Parameters
The fields in Table 84 refer to PGP network communication subsystem.
They are used when multiple PGP in a multi master architecture exchange
data (values and configurations).
All fields are optional.
Table 84. Generic Trend Group - Network Parameters.
Name
CNFNODMSK
Format
Width
Opt/Mnd
Sequence {Y, N}
Optional
None
Character
Sequence {Y, N}
Sequence {Y, N}
Sequence {Y, N}
Sequence {Y, N}
16
Optional
CNFNODMS3
Character
16
Optional
CNFNODMS4
Character
16
Optional
DESTVALMSK
Character
16
Optional
250
Range
Default
Parameter(s)
Character
16
CNFNODMS2
Description
16*N
16*N
The mask applies to nodes from 17 to 32. None
16*N
The mask applies to nodes from 33 to 48. None
16*N
The mask applies to nodes from 49 to 64 None
16*N
Tag values of group are routed from the None
current node to the nodes set in the
destination mask. First bit refers to node
1 in the node definition, second bit refers
to node 2, and so on.
9AKK101130D1382
Name
DESTVALMS2
Character
16
Optional
DESTVALMS3
Character
16
Optional
DESTVALMS4
Character
16
Optional
Description
Range
Default
Parameter(s)
Sequence {Y, N}
Sequence {Y, N}
Sequence {Y, N}
16*N
The mask applies to nodes from 17 to 32. None
16*N
The mask applies to nodes from 33 to 48. None
16*N
The mask applies to nodes from 49 to 64. None
9AKK101130D1382
251
History Parameters
The parameters listed in Table 85 allow defining archive and size of an
historical trend group.
Table 85. Historic Trend Group - History Parameters (Archiving).
Format
Width
Opt/Mnd
Name
ARCHFRQ
Range
Default
Parameter(s)
Description
Integer
Archiving frequency.
0
The value defines the time interval
between two consecutive values stored in None
a historical group. Data are processed
and archived with the frequency defined
bu this field.
Mandatory
{0...5}
Mandatory
None
Integer
Archiving offset.
Integer
1
OFFSET
Optional
0
None
Integer
{0...5}
Optional
252
None
9AKK101130D1382
Name
TOTSAMPLES
Integer
Mandatory
Range
Default
Parameter(s)
Description
0
None
Character
<string>
20
<blank>
Optional
[sznam]
Note 1:
The archiving offset is applied to the base time of the trend group, that is the
greatest integer multiple of the archiving period less or equal than archiving
period itself (second zero if period is seconds, minute zero if period is
minutes, midnight if period is hours). For instance, to have a group archiving
every 30 minutes at minute 5, the offset must be 5 minutes.
The parameters listed in Table 86 must be defined only when the archive
type is TOTAL, AVERAGE, MIN or MAX. These type of archiving only
process a set of samples to archive a computed value. Samples are
collected within the archiving period.
9AKK101130D1382
253
Name
SAMPLFRQ
Integer
Sampling frequency.
Mandatory
Range
Default
Parameter(s)
Description
0
None
{0...5}
Mandatory
None
Integer
{0...99}
Integer
1
BADSAMPLES
Optional
254
9AKK101130D1382
Name
DERIVED
INPGROUP
Character
{Y,N}
Optional
Character
<string>
20
<blank>
Optional
9AKK101130D1382
Range
Default
Parameter(s)
Description
None
[sznam]
255
Name
MONVALUE
Range
Default
Parameter(s)
Description
Character
{Y, N}
Optional
None
{Y, N}
Character
Optional
256
9AKK101130D1382
Name
MONREVERSE
MONUNITS
Range
Default
Parameter(s)
Description
{Y, N}
Character
1
Optional
Integer
{0...5}
Optional
None
Integer
Monitor factor.
Optional
TARGETLOW
Integer
TARGETHIGH
10
Optional
None
Integer
TARGETQUAL
None
10
Optional
None
Sequence {0, 1}
Character
32
<blank>
This bit mask must match the bit mask
organization of quality bits (see Appendix None
A for the quality bit structure).
Optional
9AKK101130D1382
257
Trip Parameters
Post trip groups activation is set during the configuration of the tag
database. A field in the tag database allows defining the number of post trip
group to be activated. Refer to tag database configuration for details.
Table 89. Historic Trend Group - Trip Parameters.
Format
Width
Opt/Mnd
Name
PRETIME
POSTTIME
{0...99999}
Integer
Optional
PREUNITS
Range
Default
Parameter(s)
Description
Integer
{0...5}
Optional
Integer
{0...99999}
Optional
None
None
Integer
{0...5}
Optional
258
None
9AKK101130D1382
Name
TRIPCOUNT
TRIPCLOS
Range
Default
Parameter(s)
Description
<string>
Character
20
Optional
Character
{Y,N}
Optional
None
Note 1:
The post trip time defines the post trip duration also. In order to gather
incoming exception reports, the post trip archiving is kept active until the
post trip time elapses.
For example, a post trip archiving will last 5 minutes if post trip time is set to
5 minutes. If the close trip flag is set, the post trip archiving will last at least 5
minutes. It will last less than 5 minutes if the triggering tag will return to
normal before 5 minutes elapses.
9AKK101130D1382
259
Report Subsystem
Report
Outline
PGP provides a complete set of functionalities for generating and managing
reports.
Report logs are used to obtain data from the PGP database, either from the
realtime and the historical archives, and to load data into spreadsheets,
allowing the user to format, store and perform calculations using live and
historic process data.
The reports are generated and maintained on the PGP Server computer.
The report generation program produces files that may be printed and/or
archived on the hard disk. To control the disk allocation of the report archive,
the maximum number of files kept archived and the maximum latency time
can be defined for each report.
The report configuration is based on Microsoft Excel work-sheets.
PGP provides the features listed in the following items.
The reports provide the capability to include into the Excel work-sheet
data coming from the PGP realtime and historical databases by using
the Dynamic Data Exchange (DDE) functionality.
The user will have the possibility to view the archived reports, print
and/or delete them, using the PGP report interface.
This chapter does not deal with the structure of a report. Refer to Microsoft
Excel manuals for details about work-sheet implementation.
260
9AKK101130D1382
In the following sections the structure of the definition database and the set
of functions to access PGP data are described.
Report Database
The report definition database is generated on a Personal Computer using
standard packages like DBase III/IV or EXCEL. Then, it must be copied to
the computer running the application PGP (if it is a different one) for final
import.
The report is imported submitting the database file to the database builder.
During this phase, the field contents of the input file will be used to compile
PGP internal database structures following the directives given by a field
assignment cross-reference file, previously processed by builder program
DBXRF.
The database builder may also perform export operations, creating a target
database file (DBase III/IV format) containing all items as they are currently
defined in the PGP internal database. If PGPa target database does not
exist, the builder processor creates it using the whole PGP database
structure. Alternatively, a target database file may be specified as template.
In this case, the builder processor updates the target database file handling
only the fields specified in it. The target database file may have just a single
report or may be a full or partial database file. It must contain all (and only)
fields to be exported.
Report Definition
The following sub-sections defines the parameters required to configure
reports within PGP (i.e. to notify PGP a report exists), to schedule them at
specified time intervals, to link the report to the Excel work-sheet template
and to keep controlled the disk allocation (limiting the number or the age of
reports stored on the hard disk).
The following section introduces the functions to interface PGP databases
from Excel work-sheets.
9AKK101130D1382
261
General Parameters
The fields in Table 90 define the name and other additional parameters
used to identify the report. A field (report index) allows the report
identification within other databases (e.g. in the tag database to define the
report activated on event). Additional fields are listed in the specific subsections following this one.
Table 90. Report - General Parameters.
Format
Width
Opt/Mnd
Name
REPINDEX
REPNAME
REPDESC
REPINHTAG
Range
Default
Parameter(s)
{0...50}
Integer
Report index.
6
Optional
Character
Report name.
20
Mandatory
Character
Report description.
<string>
<string>
64
<blank>
Mandatory
[szdesc]
<string>
Character
20
<blank>
Name of a tag that, while in alarm, will
disable the generation of the report. If the [sznam]
field is blank, no report inhibit is defined.
Optional
262
Description
9AKK101130D1382
Activation Parameters
The fields in Table 91 define scheduling or activation parameters used to
generate the report.
Table 91. Report - Activation Parameters.
Format
Width
Opt/Mnd
Name
SCHDFRQ
Range
Default
Parameter(s)
Description
Integer
Schedule frequency.
{1...99999}
Optional
None
OFFSET
Integer
Optional
Integer
Report offset.
{0...99999}
Optional
None
None
9AKK101130D1382
263
Name
OFFSUNITS
ACTONEVENT
Range
Default
Parameter(s)
Description
Integer
{0...3}
Optional
Character
{Y,N}
Optional
None
Note 1:
The report offset is applied to the base time of the report, that is the greatest
integer multiple of the scheduling period less or equal than scheduling
period itself (second zero if period is seconds, minute zero if period is
minutes, midnight if period is hours). For instance, to have a report
scheduled every 30 minutes at minute 5, the offset must be 5 minutes.
Archiving Parameters
The fields in Table 92 define the additional parameters used to archive
report on the hard disk and to control disk space allocation.
A parameter allows selecting to archive generated reports on the hard disk.
Two parameters, meaningful when archiving is selected, allow deleting from
the hard disk reports older than a latency time or exceeding a maximum
limit. Both latency time and maximum limit can be defined for the same
report. It is strongly suggested to define latency time and maximum number
of reports (at least one of them) when the disk archiving is selected.
264
9AKK101130D1382
Name
ARCHIVE
MAXLATENCY
MAXREPORTS
SAVEHTM
Character
{Y,N}
Optional
Integer
5
Optional
Integer
4
Optional
Character
Optional
9AKK101130D1382
Range
Default
Parameter(s)
Description
None
0
None
{Y,N}
265
Printing Parameters
The fields in Table 93 define the parameters involved in printing the report.
Table 93. Report - Printing Parameters.
Format
Width
Opt/Mnd
Name
PRINT
PRINTER
Character
Print flag.
{Y,N}
Optional
Character
Printer name.
<string>
20
<blank>
Optional
266
Range
Default
Parameter(s)
Description
None
[sznam]
9AKK101130D1382
Excel Parameters
The fields in Table 94 define the parameters used to reference the Excel
work-sheet. They allow linking the report definition and the report Excel
template.
Table 94. Report - Excel Parameters.
Name
XLSDATCELL
Format
Width
Opt/Mnd
Description
Range
Default
Parameter(s)
<string>
Character
10
Optional
9AKK101130D1382
267
Name
XLSFILE
Description
Range
Default
Parameter(s)
Character
<string>
64
<blank>
Mandatory
[szdesc]
{1...99)
Integer
Mandatory
SOE Parameters
The fields in Table 95 define the additional parameters used to link the
report to a Sequence of Event. That is, these parameters allow defining
sequence of event reports based on Excel work-sheets.
268
9AKK101130D1382
Name
SOETYPE
Range
Default
Parameter(s)
Description
Integer
{0, 1}
Optional
0 - Standard SOE
None
1 - Summary SOE
SOEDEVICE
Integer
Optional
{0, 1, 2}
Excel Work-Sheet
A report is generated on demand or periodically based on scheduling
parameters as introduced in the previous section. A template work-sheet
created by Excel is the cell matrix used to generate the actual report.
<parameter 1>,
[2]
<parameter 2>,
......................
[n]
9AKK101130D1382
<parameter n>,
269
End Variables)
Each parameter is numbered to allow easy checks in the cell formulas. The
Input Variables string opens the declaration of input variables to the
function. The End Variables string closes the declarations.
The ordering number and the declaration strings must not be typed in the
function call.
All these functions may be called both from the Excel work-sheet and the
VBA Excel code (macro Excel). These functions are for use with Microsoft
Excel only.
In the syntax of functions, square brackets enclose the assignment valid for
VBA Excel code only.
Libraries of Functions
The following sub-sections define the functions available with the PGP
software to provide an additional interface to the Microsoft Excel work-sheet
package. The libraries of functions can be included within each report or can
be added to Excel as Add-In. Refer to the Microsoft Excel manual for details
on Add-In and the inclusion of library modules within Excel.
The public library is named Tnt.xla and is located within the
\PGP\Config\Reports. It includes all the public functions listed in the
following description.
The thermodynamic library is named Steamlib.xla and is located within the
\PGP\Config\Calc. It includes steam functions, gas property functions, sea
water functions, wet air functions and fuel combustion functions as listed in
the following description.
Public functions
A set of public functions allow interacting PGP in order to retrieve data for
reporting. They include function to interface the tag configuration database,
the realtime database, the playback and the historic groups. Time
manipulation functions are included also.
270
9AKK101130D1382
Description
The function de-allocates data structures
previously allocated for data retrieving from
historical archives or playback.
Syntax
BLKDEALLOC
(Input variables
The subroutine can be called from VBA Excel
End Variables)
code only.
FPBLKQUAL
FPBLKQUALTIME
9AKK101130D1382
271
Description
Syntax
[<long> =]
FPBLKSAMPLE
(Input variables
<group name>,
<tag name>,
<start time>,
<end time>,
> 0 - The function searches forward beginning
<number of records>
from start time,
= 0 - The function retrieves all records within End Variables)
the time interval,
< 0 - The function searches backward
beginning from the end time.
If the absolute value is not null, only the first
<number of records> (or less) are returned.
FPBLKVALD
(Input variables
<group name>,
<tag name>,
<retrieving time>
End Variables)
FPBLKVALDTIME
[<double> =]
FPBLKVALDTIME
<retrieving time>
(Input variables
End Variables)
272
9AKK101130D1382
Description
The function retrieves the value of a tag from
a data packet (as returned by Fpblksample
function) of an historical group.
Syntax
[<double> =]
FPFROMBLKVALD
(Input variables
The record index is a number from 1 to N
<record index>
where N is the number of records returned by
End Variables)
the Fpblksample function.
On error, a null value is returned.
FPGET
[<string> =]
(Input variables
<tag name>,
FPGET
<force recalculation>
End Variables)
FPGETD
[<double> =]
(Input variables
<tag name>,
FPGETD
<force recalculation>
End Variables)
FPHGETD
[<double> =]
(Input variables
FPHGETD
<tag name>,
<retrieving time>
End Variables)
9AKK101130D1382
273
Description
The function retrieves the value of a tag from
a data packet (as returned by Fphxnumval
function) of the playback archive.
Syntax
[<double/string/date> =]
FPHXGETVAL
(Input variables
The record index is a number from 1 to N
<record index>,
where N is the number of records returned by
<returned type>
the Fphxnumval function.
End Variables)
The record type is represented by a character
d - Return a double precision value,
s - Return a string format value
t - Return the time (in string format) when the
value was collected.
FPHXNUMVAL
[<long> =]
FPHXNUMVAL
(Input variables
<tag name>,
<start time>,
<end time>,
<number of records>
> 0 - The function searches forward beginning
End Variables)
from start time,
= 0 - The function retrieves all records within
the time interval,
< 0 - The function searches backward
beginning from the end time.
If the absolute value is not null, only the first
<number of records> (or less) are returned.
274
9AKK101130D1382
GETDATEFROMSEC
Description
Syntax
[<long> =]
GETAPMSTIME
(Input variables
DD/MM/YY hh:mm:ss.
End Variables)
[<string> =]
GETDATEFROMSEC
[<long> =]
GETSECFROMDATE
(Input variables
<force recalculation>
If defined, the input parameter references a
End Variables)
cell in the work-sheet representing a date and
time in the Excel format.
If the input parameter is not defined, the
current date and time is converted.
The returned date and time is formatted
according to the format of the cell containing
the function reference.
See Note 1 at the end of table.
9AKK101130D1382
275
Description
Syntax
TAGINFO
[<double> =]
(Input variables
<tag name>,
TAGREAD
<force recalculation>
End Variables)
TAGREADBINARY
[<binary string> =]
(Input variables
<tag name>,
TAGREADBINARY
<force recalculation>
End Variables)
TAGREADVAL
[<double> =]
(Input variables
<tag name>,
TAGREADBINARY
<force recalculation>
End Variables)
Note 1:
276
9AKK101130D1382
Steam Functions
Steam functions of calculations can be used and referenced within Excel
work-sheets. They are listed in Table 97.
Table 97. Report - Steam Functions.
Function
CP_at_TP
Description
Specific heat as function of temperature and
pressure.
Syntax
[<specific heat> =]
CP_at_TP
(Input variables
<temperature>,
<pressure>
End Variables)
DV_at_TP
[<viscosity> =]
DV_at_TP
(Input variables
<temperature>,
<pressure>
End Variables)
H_at_PS
[<enthalpy> =]
H_at_PS
(Input variables
<pressure>,
<entropy>
End Variables)
9AKK101130D1382
277
Description
Enthalpy, relative to steam and water, as
function of temperature and pressure.
Syntax
[<enthalpy> =]
H_at_TP
(Input variables
<temperature>,
<pressure>
End Variables)
K_at_TP
[<conducibility> =]
K_at_TP
(Input variables
<temperature>,
<pressure>
End Variables)
PSAT_at_T
[<sat. pressure> =]
PSAT_at_T
(Input variables
<temperature>
End Variables)
S_at_PH
[<entropy> =]
S_at_PH
(Input variables
<pressure>,
<enthalpy>
End Variables)
278
9AKK101130D1382
Description
Entropy, relative to steam and water, as
function of temperature and pressure.
Syntax
[<entropy> =]
S_at_TP
(Input variables
<temperature>,
<pressure>
End Variables)
T_at_PH
[<temperature> =]
T_at_PH
(Input variables
<pressure>,
<enthalpy>
End Variables)
T_at_PS
[<temperature> =]
T_at_PS
(Input variables
<pressure>,
<entropy>
End Variables)
TSAT_at_P
[<saturation temp.> =]
TSAT_at_P
(<pressure>)
V_at_TP
[<specific volume> =]
V_at_TP
(Input variables
<temperature>,
<pressure>
End Variables)
9AKK101130D1382
279
Description
Specific heat of a gas as function of the
temperature.
Syntax
[<specific heat> =]
CP_GAS
(Input variables
<temperature>,
<gas index>
End Variables)
H_GAS
[<enthalpy> =]
H_GAS
(Input variables
<temperature>,
<gas index>
End Variables)
M_GAS
[<molecular weight> =]
M_GAS
(Input variables
<gas index>
End Variables)
S_GAS
[<entropy> =]
S_GAS
(Input variables
<temperature>,
<pressure>,
<gas index>
End Variables)
280
9AKK101130D1382
Description
Property of the sea water as function of the
temperature and salt concentration. The
property to be returned is specified as third
parameter.
Syntax
[<property> =]
SEAW
(Input variables
<temperature>,
<salt concentration>,
<function index>
End Variables)
9AKK101130D1382
281
Description
Specific heat of flue gas as function of the
temperature and the flue gas composition.
Syntax
[<specific heat> =]
CP_FGAS_T
(Input variables
<temperature>,
<gas index>,
<% CO2>,
<% O2>,
<% CO>,
<% SO2>,
<% H2O>,
<% AR>
End Variables)
H_FGAS_T
[<enthalpy> =]
H_FGAS_T
(Input variables
<temperature>,
<gas index>,
<% CO2>,
<% O2>,
<% CO>,
<% SO2>,
<% H2O>,
<% AR>
End Variables)
282
9AKK101130D1382
Description
Entropy of flue gas as function of the
temperature, the pressure and the flue gas
composition.
Syntax
[<entropy> =]
S_FGAS_TP
(Input variables
<temperature>,
<pressure>,
<gas index>,
<% CO2>,
<% O2>,
<% CO>,
<% SO2>,
<% H2O>,
<% AR>
End Variables)
9AKK101130D1382
283
Description
Temperature of flue gas as function of the
enthalpy and the flue gas composition.
Syntax
[<temperature> =]
T_FGAS_H
(Input variables
<enthalpy>,
<gas index>,
<% CO2>,
<% O2>,
<% CO>,
<% SO2>,
<% H2O>,
<% AR>
End Variables)
T_FGAS_PS
[<temperature> =]
T_FGAS_PS
(Input variables
<pressure>,
<entropy>,
<gas index>,
<% CO2>,
<% O2>,
<% CO>,
<% SO2>,
<% H2O>,
<% AR>
End Variables)
284
9AKK101130D1382
Description
Stechiometric air in the fuel as function of
the fuel composition.
Syntax
[<air in fuel> =]
AIR_MIN
(Input variables
<% C>,
<% H>,
<% S>,
<% O>
End Variables)
H_FCOMB_T
[<enthalpy> =]
H_FCOMB_T
(Input variables
<temperature>,
<% C>,
<% H>,
<% S>,
<% O>,
<% N>,
<dry air/fuel>
End Variables)
9AKK101130D1382
285
Description
Specific heat of air and fuel as function of
the temperature and the fuel composition.
Syntax
[<specific heat> =]
CP_FCOMB_T
(Input variables
<temperature>,
<% C>,
<% H>,
<% S>,
<% O>,
<% N>,
<dry air/fuel>
End Variables)
S_FCOMB_TP
[<entropy> =]
S_FCOMB_T
(Input variables
<temperature>,
<pressure>,
<% C>,
<% H>,
<% S>,
<% O>,
<% N>,
<dry air/fuel>
End Variables)
286
9AKK101130D1382
Description
Temperature of air and fuel as function of
the enthalpy and the fuel composition.
Syntax
[<temperature> =]
T_FCOMB_H
(Input variables
<enthalpy>,
<% C>,
<% H>,
<% S>,
<% O>,
<% N>,
<dry air/fuel>
End Variables)
T_FCOMB_PS
[temperature=]
T_FCOMB_PS
(Input variables
<pressure>,
<entropy>,
<% C>,
<% H>,
<% S>,
<% O>,
<% N>,
<dry air/fuel>
End Variables)
9AKK101130D1382
287
Description
Specific heat of wet air as function of the
temperature and absolute humidity.
Syntax
[<specific heat> =]
CP_AIR_T
(Input variables
<temperature>,
<absolute humidity>
End Variables)
H_AIR_T
[<enthalpy> =]
H_AIR_T
(Input variables
<temperature>,
<absolute humidity>
End Variables)
S_AIR_TP
[<entropy> =]
S_AIR_TP
(Input variables
<temperature>,
<pressure>,
<absolute humidity>
End Variables)
288
9AKK101130D1382
Description
Temperature of wet air as function of the
enthalpy and absolute humidity.
Syntax
[<temperature> =]
T_AIR_H
(Input variables
<enthalpy>,
<absolute humidity>
End Variables)
T_AIR_PS
[<temperature> =]
T_AIR_PS
(Input variables
<pressure>,
<entropy>,
<absolute humidity>
End Variables)
WHY
[<humidity> =]
Percentage of humidity per kg of dry air as
function of dry bulb temperature, atmospheric WHY
pressure and measured relative humidity.
(Input variables
<dry bulb temp.>,
<atmospheric press.>,
<relative humidity>
End Variables)
9AKK101130D1382
289
Pegboard Subsystem
Outline
PGP provides an integrated pegboard subsystem for process control. The
pegboard package, like all PGP subsystems, can be configured to meet
specific application requirements without programming. It maintains sets of
control tags organized as special mimics.
Process control devices (stations, MSDD, RCM etc.) can be defined as
components of a pegboard. Also displaying devices for analog and digital
tags can be defined as pegboard components. A pegboard is a special
mimic where space is divided in 32 rectangles. Up to 32 process control
devices can be arranged within the space. Since control devices require
different space for allocation, the total number of devices depends on the
their type. For example, stations requires 4 unit rectangles and up to 8
stations may fit the pegboard space.
Each pegboard allows process control by interacting with the control devices
it hosts.
Pegboard Database
The pegboard database is generated on a Personal Computer using
standard packages like DBase III/IV or EXCEL. Then, it must be copied to
the computer running the application PGP (if it is a different one) for final
import.
Pegboard database is imported submitting the database file to the database
builder. During this phase, the field contents of the input file will be used to
compile PGP internal database structures following the directives given by a
field assignment cross-reference file, previously processed by builder
program DBXRF.
The database builder may also perform export operations, creating a target
database file (DBase III/IV format) containing all items as they are currently
defined in the PGP internal database. If a target database does not exist,
the builder processor creates it using the whole PGP database structure.
Alternatively, a target database file may be specified as template. In this
case, the builder processor updates the target database file handling only
290
9AKK101130D1382
the fields specified in it. The target database file may have just a single
pegboard or may be a full or partial database file. It must contain all (and
only) fields to be exported.
Pegboard Definition
The following sections list the parameters to characterize all kind of
pegboards. There are both mandatory and optional parameters.
General Parameters
The fields in Table 103 define the name and other parameters used to
identify the pegboard. Additional fields are listed in the specific sections
following this one.
Table 103. Pegboard - General Parameters.
Format
Width
Opt/Mnd
Name
PAGEINDEX
Range
Default
Parameter(s)
Description
Integer
{0, 1...100}
Optional
[nmopds]
PAGEDESC
9AKK101130D1382
Character
Pegboard name.
<string>
20
<blank>
Mandatory
Character
Pegboard description.
<string>
[sznam]
64
<blank>
Optional
[szdesc]
291
Link Parameters
The fields in Table 104 define links to displays or other pegboards. Those
links are used when exploring the pegboards as a continuous sequence.
Table 104. Pegboard - General Parameters.
Name
FWDNAME
BWDNAME
ESCNAME
ENTNAME
Format
Width
Opt/Mnd
Range
Default
Parameter(s)
Character
<string>
20
<blank>
Optional
Character
<string>
20
<blank>
Optional
Character
<string>
20
<blank>
Optional
Character
<string>
20
<blank>
Optional
292
Description
[sznam]
[sznam]
[sznam]
[sznam]
9AKK101130D1382
Popup Parameters
The fields in Table 105 define structure of the pegboard.
Two parameters: type of popup and tag name identify each popup within the
pegboard.
Table 105. Pegboard - Popup Parameters.
Format
Width
Opt/Mnd
Name
POP01TYPE
{0...3}
Optional
None
Character
<string>
Integer
POP01TAG
Range
Default
Parameter(s)
Description
20
<blank>
Optional
[sznam]
..................
...............
.................................................
.........
POP32TYPE
Integer
{0...3}
Optional
None
Character
<string>
POP32TAG
20
<blank>
Optional
[sznam]
Description
Buckets
Undefined
Normal
9AKK101130D1382
293
Description
Buckets
Large
Small
Note 1:
Up to 32 popup may fit within a pegboard. The actual number of pop-ups
within a pegboard depends on the number of buckets required by each
single popup to fit and on the type of pop-ups included within a pegboard.
A control station, for example, has a size of 4 buckets and, consequently, 8
control stations may fit within a pegboard. A MSDD has a size of 2 buckets
and up to 16 MSDDs may fit within a pegboard. An analog or digital
visualization popup has a size of one bucket and up to 32 visualization
popup may fit within a pegboard. Be careful on configuring pegboards to
allocate pop-ups in the correct positions to avoid overlaps.
Note 2:
Other than control tags, lab data entry tags also can be defined in a
pegboard. Of course, they will only set a value in the realtime database.
294
9AKK101130D1382
9AKK101130D1382
295
Identification Parameters
The fields in Table 109 define the name and other additional parameters
used to identify and qualify menu and tool-bar items. They define the type of
item to be a menu, a tool-bar (button) or a display tree element.
Additional fields allow characterizing the item depending on the type.
Additional fields are listed in the specific sections following this one.
Table 107. Menu and Tool-bar - Identification Parameters.
Format
Width
Opt/Mnd
Name
MENUINDEX
Description
Range
Default
Parameter(s)
Integer
Item number.
{1...100}
[n.menu]
Optional
Item description.
64
Mandatory
BUTTONTYPE
<string>
Character
Character
Item type.
None
Mandatory
296
9AKK101130D1382
Description
NONE
Null element.
BUTTON
MENU
Element of a menu.
An action is associated to this item.
TREE
Action Parameters
The fields in Table 109 define the additional parameters used to qualify
action related to menu and tool-bar items. They define the action to be
performed upon selection. Action can be display a mimic, execute a
program, activate a PGP function.
Table 109. Menu and Tool-bar - Action Parameters.
Format
Width
Opt/Mnd
Name
BUTTONACT
Description
Range
Default
Parameter(s)
Character
None
Mandatory
9AKK101130D1382
297
Name
MENUPGM
MENUCMDLIN
Description
Range
Default
Parameter(s)
<string>
Character
Program name.
9
Optional
<blank>
The field is the name of the program to
activate when the menu or tool-bar item is None
selected. It is valid only if the action is
program activation.
Character
Program parameter.
128
<blank>
This field is a parameter (if any) to be
passed to the program at activation time. None
Standard command lines are listed in
Table 111
Optional
<string>
Description
None to do.
This field defines a root or sub-root of a menu or display tree.
ALMDIS
PROGRAM
Program activation.
This field allows activating a program (the name must be defined in the
Program Name field).
DISPLAY
Mimic displaying.
This field allows displaying a mimic (the name must be defined in the
Command Line field).
298
9AKK101130D1382
Description
SHELL
Document displaying.
This field allows displaying a document (the name must be defined in the
Command Line field).
TRENDS
FACEPLATE
Faceplate displaying.
This field allows displaying a faceplate (the faceplate name must be defined
in the Command Line field).
INTKEY
Internal key.
This field allows activating a program (the name must be defined in the
Program Name field).
BROWSER
Page displaying.
This field allows displaying a local HTML page or browsing to a Internet
address (the HTML page name or the Internet address must be defined in
the Command Line field).
Program Name
ALMDIS
Command Line
Description
<alarm group>
- 100
BROWSER
<HTML page>
BROWSER
<www address>
ALMDIS
ICISTA
9AKK101130D1382
299
Program Name
DISPLAY
Command Line
Description
<display name>
PROGRAM
EIXKEY
PAGE_PRINT
PROGRAM
EIXKEY
PAGE_HOME
PROGRAM
EIXKEY
PAGE_PREV
PROGRAM
EIXKEY
PAGE_BWRD
PROGRAM
EIXKEY
PAGE_FWRD
PROGRAM
EIXKEY
PAGE_ACKN
PROGRAM
EIXKEY
PAGE_BYNAME
PROGRAM
EIXKEY
PAGE_SAVE
PROGRAM
EIXKEY
PAGE_RECA
PROGRAM
EIXKEY
PRTENB
PROGRAM
IBLSD
EUD
300
9AKK101130D1382
Program Name
Command Line
Description
PROGRAM
IBLSD
LSD
PROGRAM
ITXTS
ALMC
PROGRAM
ITXTS
TXTS
9AKK101130D1382
301
Presentation Parameters
The fields in Table 112 and Table 116 define additional parameters used to
graphically qualify menu and tool-bar items. These fields defines the icon
names of buttons and optionally the functional key of the keyboard to be
used instead of the mouse (track-ball) to select.
Table 112. Menu and Tool-bar - Presentation Parameters.
Name
IMGNORMAL
Format
Width
Opt/Mnd
Description
Range
Default
Parameter(s)
Character
<string>
10
<blank>
Mandatory
None
Character
<string>
10
<blank>
Mandatory
None
302
9AKK101130D1382
Name
IMGBLINK
Range
Default
Parameter(s)
Description
Character
Icon name.
<string>
10
<blank>
Mandatory
None
Integer
Function key.
Optional
None
Integer
Menu level.
{0, ..., 9}
Optional
None
{Y, N}
Character
Item separator.
Optional
Note 1:
The icons whose names are defined above must exist or must be included
within the \PGP\Icons folder.
9AKK101130D1382
303
Program Name
ALMDIS
Normal Icon
GRAn
Description
Gray number n inside a button.
By default n can range between 1 and
20.
ALMDIS
ICISTA
GREENLED
BROWSER
EXPLORER
BROWSER
WFOLDER
DISPLAY
PLANT
DISPLAY
FOLDER
DISPLAY
FILE
NONE
FOLDER
NONE
WFOLDER
PROGRAM
ACKAUD
AUDSILENCE
PROGRAM
EIXKEY
HOME
PROGRAM
EIXKEY
LEFTKEY
PROGRAM
EIXKEY
PROGRAM
EIXKEY
RIGHTKEY
PROGRAM
EIXKEY
UPKEY
PROGRAM
LOGON
LOGON
PROGRAM
TGROUP
TRENDS
304
9AKK101130D1382
Program Name
ALMDIS
Normal Icon
REDn
Description
Red number n inside a button.
By default n can range between 1 and
20.
ALMDIS
ICISTA
REDLED
DISPLAY
OPFOLDER
NONE
OPFOLDER
Program Name
ALMDIS
Normal Icon
YELn
Description
Yellow number n inside a button.
By default n can range between 1 and
20.
The parameters listed in Table 116 are not included in the on-line
configuration utility.
Table 116. Menu and Tool-bar - Presentation Parameters (cntd.).
Name
MENUTAG
Format
Width
Opt/Mnd
Range
Default
Parameter(s)
Character
Tag name.
<string>
20
<blank>
Optional
9AKK101130D1382
Description
[sznam]
305
Allowed Parameters
The fields in Table 117 define security parameters to grant access to
various menu and tool-bar items.
Table 117. Menu and Tool-bar - Allowed Parameters.
Format
Width
Opt/Mnd
Name
MENUOPSTA
Integer
{0, 1...32}
{Y,N}
Optional
SECGROUP1
Range
Default
Parameter(s)
Description
Character
1
Optional
[nmcrts]
N
None
..................
...............
.................................................
.........
SECGROUP32
Character
{Y,N}
None
Optional
SECLEVEL
Integer
Security level.
0
The value is compared to the security
level assigned to the user before to grant None
access. A value of 0 means no security
check.
Optional
306
9AKK101130D1382
Privilege Parameters
The fields in Table 118 define security parameters to grant access to
various menu and tool-bar items.
Table 118. Menu and Tool-bar - Privilege Parameters.
Format
Width
Opt/Mnd
Name
ALARMS
Character
1
Character
1
Optional
APPL2
Character
1
CLSERVER
Character
{Y,N}
N
{Y,N}
N
Optional
None
Character
Character
1
Optional
Character
1
Optional
9AKK101130D1382
None
Optional
DIAGNOSTIC
{Y,N}
1
CONFIG
None
Optional
CALCUL
{Y,N}
None
Optional
APPL1
Range
Default
Parameter(s)
Description
{Y,N}
N
None
{Y,N}
Privilege for configuring some
miscellaneous functions (e.g. engineering N
units, logic state descriptors).
None
Privilege for executing diagnostic
functions.
{Y,N}
N
None
307
Name
GRAPHICS
Character
1
Optional
GROUPS
Character
1
Character
1
Optional
INFINET
Character
1
Character
1
Optional
LTERMHIST
Character
1
ODBC
Character
{Y,N}
N
None
{Y,N}
N
None
{Y,N}
Optional
None
Character
1
Optional
308
{Y,N}
Optional
NAVIGATE
None
Optional
LOGS
{Y,N}
None
Optional
HISTORY
Range
Default
Parameter(s)
Description
{Y,N}
N
None
9AKK101130D1382
Name
REMWRITEF
Character
1
Optional
SECURITY
Character
1
TRENDS
UTILITY
Character
{Y,N}
N
Optional
None
Character
{Y,N}
Optional
None
Character
Character
1
{Y,N}
N
None
Optional
{Y,N}
N
None
Character
{Y,N}
Optional
9AKK101130D1382
{Y,N}
None
Optional
VIEWDISP
1
VIEWCONFIG
{Y,N}
None
Optional
TIMEDATE
Range
Default
Parameter(s)
Description
None
309
Name
VIEWHIST
WINDOWSNT
Character
{Y,N}
Optional
None
Character
1
Optional
310
Range
Default
Parameter(s)
Description
{Y,N}
N
None
9AKK101130D1382
Network Subsystem
Nodes
Outline
A network structure may involve two or more PGP. Data exchange can be,
in general, required to transfer process information or configuration data
from a node to the other(s).
As an example, the alarm acknowledge broadcasting from a PGP to the
other(s) can be required.
The node definition allows defining the structure of the cooperating PGPs
within a network.
Node Database
The node database is generated on a Personal Computer using standard
packages like DBase III/IV or EXCEL. Then, it must be copied to the
computer running the application PGP (if it is a different one) for final import.
Node database is imported submitting the database file to the database
builder. During this phase, the field contents of the input file will be used to
compile PGP internal database structures following the directives given by a
field assignment cross-reference file, previously processed by builder
program DBXRF.
The database builder may also perform export operations, creating a target
database file (DBase III/IV format) containing all items as they are currently
defined in the PGP internal database. If a target database does not exist,
the builder processor creates it using the whole PGP database structure.
Alternatively, a target database file may be specified as template. In this
case, the builder processor updates the target database file handling only
the fields specified in it. The target database file may have just a single node
or may be a full or partial database file. It must contain all (and only) fields to
be exported.
9AKK101130D1382
311
Node Definition
The following sections list parameters to characterize nodes within a
network. There are both mandatory and optional parameters.
A node item is configured as a pseudo-tag: it is not included within tags, but
has some of fields typical of tag configuration.
General Parameters
The fields in Table 119 define the name and other additional parameters
used to identify nodes in the network. Additional fields are listed in the
specific sections following this one.
Table 119. Node - General Parameters.
Format
Width
Opt/Mnd
Name
NODEINDEX
NODENAME
NODEDESC
PRIMDISP
Range
Default
Parameter(s)
{0...32}
Integer
Node index.
5
Optional
Character
Node name.
<string>
20
<blank>
Mandatory
Character
Node description.
<string>
[sznam]
64
<blank>
Optional
[szdesc]
<string>
Character
Optional
312
Description
9AKK101130D1382
Name
ZEROSTATE
ONESTATE
PLANTUNIT
WEIGHT
Character
6
Optional
Character
6
Optional
Integer
2
Optional
Integer
Node weight.
Sequence {Y, N}
Optional
None
Character
Sequence {Y, N}
Sequence {Y, N}
Optional
SNAPALGMSK
Character
16
SNAPALGMS2
16
Optional
SNAPALGMS3
Character
16
Optional
9AKK101130D1382
Range
Default
Parameter(s)
Description
<string>
<string>
0
None
None
16*N
16*N
The mask applies to nodes from 17 to 32. None
16*N
The mask applies to nodes from 33 to 48. None
313
Name
SNAPALGMS4
Format
Width
Opt/Mnd
Character
Sequence {Y, N}
Sequence {Y, N}
Optional
None
Character
Sequence {Y, N}
Sequence {Y, N}
Sequence {Y, N}
Sequence {Y, N}
Optional
None
Character
Sequence {Y, N}
Optional
Character
16
CNFALGMS2
16
Optional
CNFALGMS3
Character
16
Optional
CNFALGMS4
Character
16
Optional
OJALGMSK
Character
16
OJALGMS2
16
Optional
314
Range
Default
Parameter(s)
16
CNFALGMSK
Description
16*N
The mask applies to nodes from 49 to 64 None
16*N
16*N
The mask applies to nodes from 17 to 32. None
16*N
The mask applies to nodes from 33 to 48. None
16*N
The mask applies to nodes from 49 to 64 None
16*N
16*N
The mask applies to nodes from 17 to 32. None
9AKK101130D1382
Name
OJALGMS3
Format
Width
Opt/Mnd
Character
Sequence {Y, N}
Sequence {Y, N}
Sequence {Y, N}
Optional
None
Character
Sequence {Y, N}
Sequence {Y, N}
Sequence {Y, N}
Sequence {Y, N}
None
Optional
Character
16
Optional
PLBALGMSK
Character
16
PLBALGMS2
16
Optional
PLBALGMS3
Character
16
Optional
PLBALGMS4
Character
16
Optional
HISTALGMSK
Character
16
Optional
9AKK101130D1382
Range
Default
Parameter(s)
16
OJALGMS4
Description
16*N
The mask applies to nodes from 33 to 48. None
16*N
The mask applies to nodes from 49 to 64 None
16*N
16*N
The mask applies to nodes from 17 to 32. None
16*N
The mask applies to nodes from 33 to 48. None
16*N
The mask applies to nodes from 49 to 64 None
16*N
315
Name
HISTALGMS2
Character
16
Optional
HISTALGMS3
Character
16
Optional
HISTALGMS4
Character
16
Optional
Description
Range
Default
Parameter(s)
Sequence {Y, N}
Sequence {Y, N}
16*N
The mask applies to nodes from 33 to 48. None
16*N
The mask applies to nodes from 49 to 64 None
(1)
316
9AKK101130D1382
Name
DS_ALARM
DS_RTN
Range
Default
Parameter(s)
Description
Character
{Y, N}
Optional
Character
{Y, N}
Optional
None
None
{Y, N}
Optional
None
Character
{Y, N}
Optional
Character
{Y, N}
Character
1
REM_ONACK
INFO_ONACK
Optional
9AKK101130D1382
None
None
317
Name
PR_ALARM
Range
Default
Parameter(s)
Description
Character
{Y, N}
Optional
None
Character
{Y, N}
Optional
None
Character
{Y, N}
Optional
None
SV_ALARM
SV_OPACT
1
Optional
Character
1
Optional
Character
Y
If set, database modifications and all
other operator actions concerning this
None
pseudo-tag will be logged to the Operator
Journal.
Optional
318
{Y, N}
Character
{Y, N}
{Y, N}
9AKK101130D1382
Name
SV_RTN
SV_INFO
ALMPRINTER
Range
Default
Parameter(s)
Description
{Y, N}
Character
1
Optional
Y
If set, a RTN message concerning this
pseudo-tag will be logged to the Operator None
Journal.
Character
1
Optional
Integer
0
Reference index to the printer where
messages concerning the tag are printed. None
See the fields PR_xxx (e.g. PR_ALARM)
also.
Optional
{Y, N}
AL_PRI
Integer
Alarm group.
{0, 1...272}
Optional
Integer
Alarm priority.
{0, 1...15}
{Y,N}
Optional
AUD_ALARM
Character
1
Optional
9AKK101130D1382
[sladnm] and
[mxxagp]
[mxalpr] and
[mxxapr]
Y
None
319
Name
AUDINDEX
Integer
{0, 1...32}
{Y, N}
Optional
AUD_RTN
Character
1
EXP_ALA
Character
{Y,N}
Optional
Character
{Y,N}
Optional
320
[mxaud]
None
Optional
APPL_ALA
Range
Default
Parameter(s)
Description
None
None
9AKK101130D1382
Security Subsystem
Security
Outline
PGP offers a security subsystem allowing definition of internal users. Each
user is identified by a name and a password.
A set of access rights and permissions can be assigned to each user. In
such a way access to PGP functions or operations (e.g. tag configuration)
can be denied.
In configuring PGP, various security level validity masks can be defined to
limit access to functions or items (e.g. tags). Those masks are used to
control operator actions on the following items.
Program Activation,
Display Retrieval,
Process Control.
The masks associated with the above items will be referred to as the
"validity masks" throughout this section.
PGP provides the following validity masks:
Tag Access Right Mask.
Enable or disable operations related to single tags. The following security
rights are defined:
9AKK101130D1382
Monitor,
321
Configure,
Process Control,
Tune,
Delete,
Enter Data,
Alarms Acknowledgment.
Utilities,
Alarm Management,
Graphics,
Historical Archives,
Diagnostic,
Security,
Trend Groups,
322
9AKK101130D1382
The security definition file contains the information to define the User
Authorization File and to provide operator passwords.
PGP provides a security scheme that allows functions to be grouped so that
access to a group of functions and/or displays may be denied. Any operator
of a PGP station must enter his password to gain rights and permissions.
This password has a list of allowed and denied functions/displays
associated. Attempts to perform a denied operation will results in an
operator message.
Security Database
The security database is generated on a Personal Computer using standard
packages like DBase III/IV or EXCEL. Then, it must be copied to the
computer running the application PGP (if it is a different one) for final import.
Security database is imported submitting the database file to the database
builder. During this phase, the field contents of the input file will be used to
compile PGP internal database structures following the directives given by a
field assignment cross-reference file, previously processed by builder
program DBXRF.
The database builder may also perform export operations, creating a target
database file (DBase III/IV format) containing all items as they are currently
defined in the PGP internal database. If a target database does not exist,
the builder processor creates it using the whole PGP database structure.
Alternatively, a target database file may be specified as template. In this
case, the builder processor updates the target database file handling only
the fields specified in it. The target database file may have just a single user
or may be a full or partial database file. It must contain all (and only) fields to
be exported.
Security Definition
The following sections list a set of parameters to define a PGP user. There
are both mandatory and optional parameters.
9AKK101130D1382
323
General Parameters
The fields in Table 121 define the name and other additional parameters
used to identify the PGP user.
Table 121. Security - General Parameters.
Format
Width
Opt/Mnd
Name
USERINDEX
USERNAME
PASSWORD
Description
Range
Default
Parameter(s)
{0...20}
Integer
User index.
3
Optional
0
This field identifies the PGP user by
number. It must be unique for each user [n.pswd]
in the database. If omitted or zero (blank),
the first vacant index will be allocated.
Character
User name.
<string>
18
<blank>
Mandatory
Character
User password.
<string>
18
<blank>
Mandatory
[szunam]
[szunam]
Integer
18
Mandatory
None
324
9AKK101130D1382
Name
USERCODE
LANGUAGE
Integer
User code.
4
Optional
Integer
Optional
ACTIVE USER
Character
1
Mandatory
WINGROUP
Character
64
Optional
9AKK101130D1382
Range
Default
Parameter(s)
Description
0
None
0
None
325
326
9AKK101130D1382
Name
LOGOFFTMO
Range
Default
Parameter(s)
Description
Character
Log-off on time-out.
{Y,N}
Optional
None
LOGOFFDISP
LOGINPROG
LOGOFFPROG
Character
Log-in display.
9
Optional
Character
Log-off display.
9
Optional
Character
Log-in program.
<string>
<blank>
Optional
Character
Log-off program.
<string>
<blank>
Optional
9AKK101130D1382
<string>
<string>
None
None
327
Name
MAXLOGINFAIL
Range
Default
Parameter(s)
Description
Integer
{0, 1...9999}
Optional
None
Optional
328
{0, 1...9999}
Integer
9AKK101130D1382
Name
TAGMONITOR
TAGCONFIG
TAGCONTROL
Character
Optional
None
Character
TAGENTDATA
TAGOFFSCAN
9AKK101130D1382
{Y,N}
Optional
None
Character
Optional
TAGDELETE
{Y,N}
1
TAGTUNE
Range
Default
Parameter(s)
Description
Character
{Y,N}
N
None
{Y,N}
Optional
None
Character
{Y,N}
Optional
None
Character
{Y,N}
Optional
None
Character
Optional
None
329
Name
TAGOFFALM
Character
1
Optional
TAGLIMIT
TAGACK
TAGMONALL
TAGREMOTE
TAGENTHIST
Character
Range
Default
Parameter(s)
Description
{Y,N}
N
None
{Y,N}
Optional
None
Character
{Y,N}
Optional
None
Character
{Y,N}
1
Optional
Character
{Y,N}
Optional
None
Character
{Y,N}
Optional
None
330
9AKK101130D1382
Name
ALARMS
Character
1
Character
1
Optional
APPL2
Character
1
CLSERVER
Character
{Y,N}
Optional
None
Character
Character
Optional
Character
1
Character
1
Optional
{Y,N}
N
None
{Y,N}
{Y,N}
Optional
9AKK101130D1382
{Y,N}
GRAPHICS
None
Optional
DIAGNOSTIC
{Y,N}
1
CONFIG
None
Optional
CALCUL
{Y,N}
None
Optional
APPL1
Range
Default
Parameter(s)
Description
N
None
N
None
{Y,N}
N
None
331
Name
GROUPS
Character
1
Optional
HISTORY
Character
1
Optional
INFINET
Character
1
Character
1
Optional
LTERMHIST
Character
1
Character
1
{Y,N}
{Y,N}
Character
1
Character
1
Optional
332
None
N
{Y,N}
N
None
{Y,N}
N
None
Optional
REMWRITEF
None
Optional
ODBC
Optional
NAVIGATE
{Y,N}
None
Optional
LOGS
Range
Default
Parameter(s)
Description
{Y,N}
N
None
{Y,N}
N
None
9AKK101130D1382
Name
SECURITY
Character
1
Optional
TIMEDATE
TRENDS
UTILITY
Character
Optional
None
Character
Optional
None
Character
Character
{Y,N}
N
None
{Y,N}
N
None
Character
{Y,N}
Optional
Character
{Y,N}
None
Optional
None
Character
1
Optional
9AKK101130D1382
{Y,N}
Optional
WINDOWSNT
{Y,N}
N
VIEWHIST
N
None
Optional
VIEWDISP
{Y,N}
1
VIEWCONFIG
Range
Default
Parameter(s)
Description
{Y,N}
N
None
333
The fields in Table 125 define the security group mask. Each field refers to a
security group. Another field to control the access is the security level.
Table 125. Security - Group and Level Parameters.
Format
Width
Opt/Mnd
Name
SECGROUP1
Character
1
Range
Default
Parameter(s)
Description
Privilege to access tags and displays
belonging to the security group 1.
{Y,N}
N
None
Optional
.....................
.............
.....................................
........................
SECGROUP32
Character
{Y,N}
1
Optional
SEC_LEVEL
N
None
Integer
Security level.
{0, 1...16}
Optional
None
334
9AKK101130D1382
Client Parameters
The fields in Table 126 define the remote access parameters. They define
which clients are entitled to log in as privileged user. Each parameter is a bit
mask and each bit refers to a client. The clients must be defined in a client
list on the server.
Table 126. Security - Remote Access Parameters.
Name
CRTMASK1
Format
Width
Opt/Mnd
Description
Range
Default
Parameter(s)
Character
Sequence {Y, N}
16
16*Y
Optional
None
Sequence {Y, N}
16
16*Y
Optional
Character
Sequence {Y, N}
16
16*N
Optional
.....................
.............
.....................................
........................
PLANTUMSK9
Character
Sequence {Y, N}
16
Same as above.
16*N
CRTMASK2
PLANTUMSK1
Optional
PLANTUMS10
None
Character
Sequence {Y, N}
16
16*N
Optional
9AKK101130D1382
None
None
335
Name
Format
Width
Opt/Mnd
Description
Range
Default
Parameter(s)
.....................
.............
.....................................
........................
PLANTUMS16
Character
Sequence {Y, N}
16
Same as above.
16*N
Optional
None
336
9AKK101130D1382
9AKK101130D1382
337
338
9AKK101130D1382
Select each group (by double clicking on it) and add users to it. If you add
the user which is currently logged on you will have to logoff and logon again
before the modification takes effect.
The previously described procedures may also be applied on a domain
server, centralizing the user management
Some Hints
In case Power Generation Portal is started by an Interactive User (i.e. not
started as a Window Service), then the currently logged user has to have
Windows Administrator privileges,
and a Local Policy right named act as part of the Operating System. This
right is granted automatically when the Client/Server function from the
Power Generation Portal Setup is performed.
Whenever a Power Generation Portal User Logon is performed the Power
Generation Portal User Database is scanned first, then the Windows
Database is checked. In case of duplicated names the Power Generation
Portal user will be taken in charge.
The Windows Group Database is checked by looking in the local groups (the
groups defined in the machine where the user logon) and then looking in the
domain server.
In case of multiple definitions the one in the local machine will be
considered.
The Windows user must belong only to one Power Generation Portal group.
In case of multiple assignments then the first in the alphabetical order will be
considered.
9AKK101130D1382
339
Security Defaults
PGP provides a default security configuration to grant its basic operation.
This section lists those default settings in Table 127 The table lists security
level, security groups, tag operation rights and privileges of each user.
The end user may want to change user names and/or passwords according
to his organization and his needs. Follow the general directions on
configuration and the previous security database description to change user
names or passwords.
Table 127. Security - Default Settings.
User Name
Password
Sec.
Level
Sec.
Groups
Privileges
OPERATOR
LEVEL0
All
TagMonitor,
TagControl, TagAck
ViewDisp
ENGINEER
LEVEL1
All
TagMonitor,
TagConfig, TagDelete,
TagEntData,
TagOffScan,
TagOffAlm, TagLimit.
Alarms, Graphics,
Logs, History, Security,
TimeDate, Trends,
Infinet, Groups, Utility,
ViewConfig, ViewDisp,
LTermHist, ClServer,
Calcul, ViewHist,
Windows.
SYSMGR
PRIV
16
All
All rights.
All privileges.
340
9AKK101130D1382
Static data.
Dynamic data.
9AKK101130D1382
MS Access,
341
Oracle 8
The target DBMS engine may run on the same machine as PGP, as well as
on a remote machine connected via network.
Although PGP operates as a simple data provider, it expects the target
database to have a known structure for what concerns the number, name
and format of the tables. Thus, such tables are created and maintained
automatically by PGP, and their structure must never be changed. In
addition, a maintenance application tool (Data Export Manager) is
provided.
The only manual action required to put foreign database support at work, is
a simple setup procedure to configure ODBC data source. Once the ODBC
driver is installed on PGP machine, just add a new data source using the
Data Export Manager. Depending on the DBMS, this setup procedure will
interactively ask for all required information such as server node name,
security information and so on.
Static Tables
As mentioned, static tables contain configuration parameters for tags and
trend groups. The maximum number of tags and trend groups limits the size
of static tables in the system. Static tables reflect the current configuration of
the system, and they must be kept aligned by the system itself. Once PGP
exports the data to the target database, it has no kind of control over them.
That is, if the contents of static tables are changed, the only way to recover
the original situation is to realign the target database by the Data Export
Manager.
The structure of static tables may be changed to fit particular system
requirements. These changes must be set up on PGP by compiling a deckfile for database cross reference builder DBXRF (see Configuration Guide)
before the tables are created on target database. Once a table is created,
initialized and aligned, its structure must never change, unless another
realignment is made.
Static tables are created and initialized by PGP at system generation time,
regardless they already exist or not. Then, they are updated whenever the
342
9AKK101130D1382
Name
TAGINDEX
Decimal
Description
Range
Default
Parameter(s)
Tag index.
6
Optional
TAGNAME
Character2
None
Tag name.
20
Optional
TAGDESC
Character2
None
Tag description.
64
Optional
9AKK101130D1382
None
343
Name
TAGTYPE
Character2
Description
Range
Default
Parameter(s)
Tag type.
8
Optional
EUDESC
Character2
None
Engineering unit description.
16
Optional
VAL0
Dbl. Prec.
None
Value of 0% scale.
Optional
SPAN
Dbl. Prec.
None
Instrument range.
Optional
ZEROSTATE
Character2
None
Descriptor for state 0.
16
Optional
ONESTATE
Character2
None
Descriptor for state 1.
16
Optional
TWOSTATE
Character2
None
Descriptor for state 2.
16
Optional
344
None
9AKK101130D1382
Name
THREESTATE
Character2
Description
Range
Default
Parameter(s)
16
Optional
FOURSTATE
Character2
None
Descriptor for state 4.
16
Optional
None
Table 129. Foreign Database Support - Trend Groups Static Table (GROUPS).
Format
Width
Opt/Mnd
Name
GROUPINDEX
Decimal
Description
Range
Default
Parameter(s)
Group index.
6
Optional
GROUPNAME
Character2
None
Group name.
20
Optional
GROUPDESC
Character2
None
Group description.
64
Optional
ARCHTYPE
Character2
None
Archive type.
7
Optional
9AKK101130D1382
None
345
Table 129. Foreign Database Support - Trend Groups Static Table (GROUPS).
Format
Width
Opt/Mnd
Name
EUDESC
Character2
Description
Range
Default
Parameter(s)
16
Optional
ARCHFRQ
Decimal
None
Archive frequency.
6
Optional
ARCHUNITS
Decimal
None
Archive time units.
6
Optional
OFFSET
Decimal
None
Archive time offset.
6
Optional
OFFSUNITS
Decimal
None
Archive time offset units.
6
Optional
SAMPLFRQ
Decimal
None
Sample frequency.
6
Optional
SAMPLUNITS
Decimal
None
Sample time units.
6
Optional
TOTSAMPLES
Decimal
None
Total number of samples.
6
Optional
346
None
9AKK101130D1382
Table 129. Foreign Database Support - Trend Groups Static Table (GROUPS).
Format
Width
Opt/Mnd
Name
TAG1
Character2
Description
Range
Default
Parameter(s)
20
Optional
None
..................
...............
.................................................
TAG60
Character2
.........
20
Optional
None
Dynamic tables
As mentioned, dynamic tables contain historical process values for tags,
alarms and trend groups. Since new values are always inserted into target
database in form of new records, the size of dynamic tables can indefinitely
grow up. That requires some kind of maintenance activity on target
database. On the other hand, since dynamic tables contain volatile
information, there is no need to keep any kind of alignment with PGP
database. That is, target databases administrator can manipulate dynamic
table contents as desired, for instance deleting or dumping to tape old
records.
Like static tables, the structure of dynamic tables may be changed to fit
specific application requirements. These changes must be set up on PGP
by compiling a deck-file for database cross reference builder DBXRF (see
Configuration Guide) before the tables are created on target database.
Once a table is created and initialized, its structure must never change,
unless another initialization is made.
At start-up time, PGP creates and initializes tag and alarm dynamic tables,
unless they already exist. Trend group dynamic tables are created at group
creation or when a change takes place.
9AKK101130D1382
347
Name
TAGTIME
Date
Description
Tag time and date.
Optional
TAGMILSEC
Decimal
Range
Default
Parameter(s)
None
Tag milliseconds.
3
Optional
348
None
9AKK101130D1382
Name
TAGINDEX
Decimal
Description
Range
Default
Parameter(s)
Tag index.
6
Optional
TAGUID
Character2
None
Tag unique identification.
36
Optional
TAGVALUE
Dbl. Prec.
None
Tag value.
Optional
TAGSTATE
Character2
None
Tag state.
16
Optional
TAGQUALITY
Character2
[sztags]
Tag quality.
4
Optional
9AKK101130D1382
None
349
Name
ALARMTIME
Date
Description
Alarm message time and date.
Optional
ALARMILSEC
Decimal
Range
Default
Parameter(s)
None
Alarm message milliseconds.
3,0
Optional
TAGINDEX
Decimal
None
Tag index.
6
Optional
TAGUID
Character2
None
Tag unique identification.
36
Optional
ALARMTYPE
Character2
None
Alarm type.
6
Optional
ALARMTEXT
Character2
None
Alarm text.
132
Optional
350
[s.aldb]
9AKK101130D1382
Table 132. Foreign Database Support - Group Dynamic Table (<group name>).
Name
TAGTIME
Fmt
Date
Description
Tag time and date.
Optional
TAGMILSEC
Decimal
Param
None
Tag milliseconds.
3
Optional
TAGINDEX
Decimal
None
Tag index.
6
None
TAGVALUE
Dbl.Prec.
Tag value.
None
TAGSTATE
Character2
Tag state.
16
[sztags]
TAGQUALITY
Character2
Tag quality.
2
None
TRIPTIME
Date
Optional
9AKK101130D1382
351
Table 132. Foreign Database Support - Group Dynamic Table (<group name>).
Name
Fmt
TRIPMILSEC
Decimal
Description
Param
Trip milliseconds.
3
Optional
GROUPINDEX
Decimal
None
Group index.
6
Optional
None
To activate the maintenance tool, choose Programs from the Start Menu,
then PGP and then Data Export Manager. The main dialog window is
displayed.
As the program is activated, the only function available is Open
Connection, associated with the icon key:
This key displays the Windows standard ODBC setup wizard, listing all the
data sources already configured on the machine.
352
9AKK101130D1382
The first time the program is activated, it creates a new data source
specifically dedicated to PGP. To do it, press the New button, choose one
of the ODBC drivers available and provide all required information. Such
information depends on the selected driver, and may range from simple file
specification (i.e. desktop databases like MS Access) to network path and
security (i.e. distributed databases like Oracle or MS SQL Server).
Since it is not possible to give a standard procedure for all DBMS, please
refer to manufacturers documentation. After the data source has been
properly setup, the program will ask the operator to make the selection
permanent and to link all PGP internal fields to the newly selected DBMS
native data types. Next, after the automatically spawned build of DBXRF is
completed, all the tables actually configured on the target database are
listed.
If the PGP data source has been already set up, just select it to get the table
list described above. The table list may also be recalled at any time by the
List function, associated with the icon key:
Usually, PGP creates and initializes static tables at generation time, and
then maintains them updated to guarantee the alignment of their contents
with itself. In any case, they can also be created and realigned manually.
For instance, to support the database export function after PGP has been
originally generated or to realign tables after a communication failure, a
manual realignment can be done. This function, indicated as Create and
Align, is associated with the icon key:
Each table in list may be inspected to get its structure by the function
Properties, associated with the icon key:
9AKK101130D1382
353
To get the table structure, select the desired table and press the icon key or
just double click the desired table.
The table structure is displayed.
A table, once selected, may also be deleted (dropped) by the function
Delete, associated with the icon key:
Finally, the target data source, may be queried by any standard SQL
command using the function Query associated with the icon key:
Setup Guidelines
The support to foreign database export may be added at any time to an
existing (and licensed) PGP version 1.2 or higher (even if it has been
generated without this feature), using the Data Export Manager. In any
case, it is suggested to setup this function just BEFORE the very first build
all (last step of post-installation procedure), by following the procedure
itemized below:
354
9AKK101130D1382
Run the Data Export Manager and define the PGP specific data
source, according to whats described in previous section. Exit the Data
Export Manager.
Add the proper fields to tag database (EXP_VAL and EXP_ALA) and
trend group database (EXP_VAL), and decide which tags and/or
groups must be exported.
9AKK101130D1382
355
356
9AKK101130D1382
TagTable.
Name of tag static table. The default is TAGS.
After these parameters are changed, the system must be restarted. If the
change affects one of the table names, the table must be created and
realigned.
9AKK101130D1382
357
358
9AKK101130D1382
9AKK101130D1382
353
In the following description lists the parameters that are defined as xxx in
the previous XML snapshot. They define the structure of the file. The form
essentially defines the file key, the number of records and the record size.
Files defined here may be disk files, core files (memory resident) and
parallel files.
Parallel files are both disk and memory resident. At PGP start-up time the
contents of a parallel file is copied from the disk file to the memory.
Table 133. Builder BFIL XML Format File System General Definition.
Parameter
action
Format
Opt/Mnd
Character
Action Code.
Mandatory
Range
Default
{init, add, replace,
delete}
None
Description
name
Character
Mandatory
description
Character
Optional
type
<string>
<blank>
<string>
Character
Mandatory
None
D - Disk file,
C - Core file,
P - Parallel file.
354
9AKK101130D1382
Table 133. Builder BFIL XML Format File System General Definition.
Parameter
key
Format
Opt/Mnd
Character
Mandatory
path
Character
Optional
records
Character
Mandatory
remote_write
Character
Optional
size
Character
Optional
save_snapshot
Character
Optional
save_initial
Character
Optional
9AKK101130D1382
Description
File key.
The file key is an integer numeric name of
three digits, which refer to the file.
It must correspond with the number
assegned internally to the software for
accessing the files.
Specifies the path of the file.
Range
Default
{1...999}
None
None
None
{Y,N}
N
{Y,N}
N
355
Table 133. Builder BFIL XML Format File System General Definition.
Format
Opt/Mnd
skip_initialization Character
Parameter
Optional
Range
Default
Description
Skip Initialization.
{Y,N}
Process Scheduling
Process scheduling allows management of timers in order to activate
system and possibly application programs.
These functions take typically place when timers expire.
The file BTIMDECK.XML, located in the \Deck folder, defines the PGP
timers for process scheduling and the file BFIL2DECK, located in the
\Config\Deck folder, may define the application specific timers. Both files
define the whole system timers. The format of the two files is the same.
The base PGP does not provide an empty BTIM2DECK file. It may be
derived from BTIMDECK when application specific timers must be added.
The processor BTIM performs the definition of timers. The XML format,
support the standard XMl syntax, and is defined in the following example:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<TIMERS action="xxx">
<TIMER name=xxx" active=xxx" frequency=xxx" freq_unit=xxx" offset=xxx"
offs_unit=xxx" delay=xxx" delay_unit=xxx"/>
...
...
</TIMERS>
356
9AKK101130D1382
Format
Opt/Mnd
Character
Action code.
Range
Default
{init,add,replace}
Mandatory
None
Description
Character
frequency
Mandatory
Integer
freq_unit
Optional
Character
0
None}
Optional
None
offset
Integer
Optional
offs_unit
Character
1Optional
delay
Integer
Optional
9AKK101130D1382
None
357
Format
Opt/Mnd
Character
Optional
active
Range
Default
Description
Units for initial delay.
Character
None
{Y,N}
Mandatory
358
9AKK101130D1382
Format
Opt/Mnd
Character
Action code.
Range
Default
{init, add}
Mandatory
None
Description
<string>
<string>
auto
Character
None
Automatic generation of DST Periods starting from {yes, no}
Windows Operating System
No
start
Character
Mandatory
end
Character
Mandatory
9AKK101130D1382
359
360
9AKK101130D1382
where yyyy and zzzz represent respectively the italian and the french
translation of the english text xxxx.
Of course other languages can be added.
Database Subsystem
Field Assignment Cross-Reference
The Field Assignment Cross-Reference definition file (DBXRFDECK.XML
located in the \Deck folder) contains all field definitions and all site-specific
changes to be used when processing a database file. Database files are the
tag database file, the trend group database file, the calculation database file,
the tag related (engineering units, alarm comments, logical state descriptors
and text selectors) database files, the node network database file, the
pegboard database file, the alarm grouping database file.
The file DBXRFDECK, located in the \Deck folder, defines the PGP field
assignment definition and the file BFIL2DECK.XML, located in the
\Config\Deck folder, may define the application specific field assignments.
Both files define the field assignment definition of the whole system. The
format of the two files is the same.
The base PGP does not provide an empty DBXRF2DECK file. It may be
derived from DBXRFDECK when application specific field assignments
must be added.
9AKK101130D1382
361
362
9AKK101130D1382
Format
Opt/Mnd
Character
Action code.
Mandatory
Range
Default
{init,add,replac
e}
None
Description
descr
Character
code
Optional
Character
None
<string>
Mandatory
None
name
Character
Mandatory
default
Character
Optional
callback
Character
Optional
<string>
None
<string>
None
9AKK101130D1382
363
dbfunbuild
Optional
Character
Optional
Range
Default
<string>
None
{Y, N}
Description
xlsunbuild
Character
Optional
{Y, N}
364
9AKK101130D1382
Format
Opt/Mnd
Character
Mandatory
Description
Item type to which field assignment is applied.
Item type is an string value according to the
parameter file SYSPRM.
Range
Default
<string>
None
name
Character
Optional
name
Character
type
Mandatory
Character
None
{C, N}
Mandatory
None
C - Character.
N - Numeric.
length
Integer
dbf
Mandatory
Character
xls
Optional
Character
Optional
9AKK101130D1382
<number>
0
Flag specifiing if the field will be exported to DBF {Y,N}
files (see above)
N
Flag specifiing if the field will be exported to XLS {Y,N}
files (see above)
N
365
366
9AKK101130D1382
CbkRejText.
Accepts only those records whose text fields specified by arguments 1,3,5,7
are not equal to values specified by arguments 2,4,6,8.
Color/Blink Override
The color/blink override table configures the attributes for displaying analog
and digital tags.
PGP supports the colored display of tags. The operator can easily
understand the status of a displayed variable.
Tag values are displayed using different foreground and background colors
and blink, depending on the status of the tag and its priority. In addition, one
or two trailing characters may be appended to a value to qualify the status.
This prevents problems resulting from color-blindness, monochromatic
visual display units, hard-copy, etc.
The table allows the user to have flexibility in what combinations of blink
colors and appended characters are displayed, given various status
conditions.
9AKK101130D1382
367
The file BATTDECK.XML, located in the \Deck folder, defines the PGP
color/blink override table and the file BATT2DECK.XML, located in the
\Config\Deck folder, may define the application specific overrides.
Both files define the override table of the whole system. The format of the
two files is the same. The base PGP does not provide an empty
BATT2DECK file. It may be derived from BATTDECK when application
specific overrides must be added or changed.
The processor BATT performs the configuration of the override table. The
XML format, support the standard XML syntax, and is defined in the
following example:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<PRIORITIES action="xxx">
<PRIORITY number=xxx" type=xxx" >
<PROCESSING ds_alarm="xxx pr_alarm=xxx sv_alarm=xxx aud_alarm=xxx
bot_alarm=xxx ds_rtn=xxx pr_rtn=xxx sv_rtn=xxx ds_stchng=xxx pr_stchng=xxx
sv_stchng=xxx pr_opact=xxx sv_opact=xxx pr_info=xxx sv_info=xxx
rem_onack=xxx appl_ala=xxx info_onack=xxx exp_ala=xxx opc_ala=xxx
audidx=xxx />
<ITEM pos=xxx descr=xxx bit=xxx type=xxx color=xxx symbol=xxx invert=xxx/>
...
...
</PRIORITY>
...
...
</PRIORITIES>
368
9AKK101130D1382
Format
Opt/Mnd
Character
Action code.
Range
Default
{init, add, replace}
Mandatory
None
Description
number
Integer
type
Mandatory
Character
Mandatory
copy_from_priority Integer
Optional
bit
Character
Mandatory
type
{1...16}
None
{PV,DI}
None
{1...16}
{0...31}
None
Character
Mandatory
None
BL - Blink,
BC - Background color,
FC - Foreground color.
9AKK101130D1382
369
Format
Opt/Mnd
Characte
Mandatory
symbol
Character
Description
Color.
The names refers an entry in the
BattColors.ins file located in the \Config
folder.
See the Appendix for the default allowed
colors and the syntax of the BattColors file.
The color scheme can be modified
changing the BattColors file.
Quality symbol.
Range
Default
<string>
None
<string>
None
Optional
ds_alarm
Character
PROCESSING
Display alarm.
{Y, N}
pr_alarm
Optional
Character
Print alarm.
N
{Y, N}
sv_alarm
Optional
Character
Archive alarm.
N
{Y, N}
aud_alarm
Optional
Character
Audible on alarm.
N
{Y, N}
bot_alarm
Optional
Character
N
{Y, N}
ds_rtn
Optional
Character
N
{Y, N}
Optional
invert
Character
Optional
descr
Character
Optional
370
{Y, N}
<string>
None
9AKK101130D1382
pr_rtn
Format
Opt/Mnd
Character
{Y, N}
sv_rtn
Optional
Character
N
{Y, N}
ds_stchng
1
Character
Display event.
N
{Y, N}
pr_stchng
Optional
Character
Print event.
N
{Y, N}
sv_stchng
Optional
Character
Archive event.
N
{Y, N}
pr_opact
Optional
Character
N
{Y, N}
sv_opact
Optional
Character
N
{Y, N}
pr_info
Optional
Character
N
{Y, N}
sv_info
Optional
Character
N
{Y, N}
rem_onack
Optional
Character
N
{Y, N}
info_onack
Optional
Character
Log on acknowledge.
N
{Y, N}
app_ala
Optional
Character
N
{Y, N}
exp_ala
Optional
Character
N
{Y, N}
opc_ala
Optional
Character
N
{Y, N}
audidx
Optional
Integer
N
{0,16}
Parameter
Optional
9AKK101130D1382
Range
Default
Description
371
Message Subsystem
Alarm message
PGP allows user configuring of a great number of different formats to display
and print an event according to alarm category definition.
The file BALMDECK.XML, located in the \Deck folder, defines the PGP
alarm messages and the file BALM2DECK.XML, located in the \Config\Deck
folder, may define the application specific messages.
Both files define the alarm messages of the whole system. The format of the
two files is the same.
The base PGP does not provide an empty BALM2DECK file. It may be
derived from BALMDECK when application specific alarm messages must
be added.
The processor BALM performs the configuration of alarm messages. The
XML format, support the standard XMl syntax, and is defined in the following
example:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<ALARM_MESSAGES action="xxx">
<MESSAGE code=xxx" value=xxx" >
<PARAMETERS p1=xxx l1=xxx ....p30=xxx l30=xxx />
<PROCESSING ds_alarm="xxx pr_alarm=xxx sv_alarm=xxx aud_alarm=xxx
bot_alarm=xxx ds_rtn=xxx pr_rtn=xxx sv_rtn=xxx ds_stchng=xxx pr_stchng=xxx
sv_stchng=xxx pr_opact=xxx sv_opact=xxx pr_info=xxx sv_info=xxx
rem_onack=xxx appl_ala=xxx info_onack=xxx exp_ala=xxx opc_ala=xxx
audidx=xxx prtidx=xxx opstation=xxx priority=xxx group=xxx translate=xxx
opc=xxx/>
</MESSAGE>
...
...
</ALARM_MESSAGES>
372
9AKK101130D1382
Format
Opt/Mnd
Character
Action code.
Range
Default
{init,add,replace}
Mandatory
None
Description
Char or Int
Mandatory
value
Character
Mandatory
PARAMETERS
p1
Character
l1
Optional
Integer
PROCESSING
ds_alarm
Character
Optional
9AKK101130D1382
{1...999}
Optional
<string> or
<string>
None
Integer
Display alarm.
{Y, N}
N
373
pr_alarm
Format
Opt/Mnd
Character
Print alarm.
{Y, N}
sv_alarm
Optional
Character
Archive alarm.
N
{Y, N}
aud_alarm
Optional
Character
Audible on alarm.
N
{Y, N}
bot_alarm
Optional
Character
N
{Y, N}
ds_rtn
Optional
Character
N
{Y, N}
pr_rtn
Optional
Character
N
{Y, N}
sv_rtn
Optional
Character
N
{Y, N}
ds_stchng
1
Character
Display event.
N
{Y, N}
pr_stchng
Optional
Character
Print event.
N
{Y, N}
sv_stchng
Optional
Character
Archive event.
N
{Y, N}
pr_opact
Optional
Character
N
{Y, N}
sv_opact
Optional
Character
N
{Y, N}
pr_info
Optional
Character
N
{Y, N}
sv_info
Optional
Character
N
{Y, N}
N
{Y, N}
Parameter
Optional
rem_onack Character
Optional
374
Range
Default
Description
9AKK101130D1382
Range
Default
Description
Log on acknowledge.
{Y, N}
app_ala
Optional
Character
N
{Y, N}
exp_ala
Optional
Character
N
{Y, N}
opc_ala
Optional
Character
N
{Y, N}
audidx
Optional
Integer
N
{0,16}
opstation
Optional
Integer
Operator station.
0
{0...32}
Optional
priority
Integer
Optional
group
Integer
Optional
translate
Character
Optional
prtiidx
Integer
Optional
[nmcrts]
{0...8}
{0...SLADNM}
Number
0
The message text may contain symbols and ASCII text in a specific order.
These symbols represent variable text to be formatted at run time. The data
for these fields is supplied from the alarm queue header or the alarm queue
data buffer or the item description record when the message is requested for
displaying.
9AKK101130D1382
375
Field Type
String
Description
The field will be filled by a sequence of characters.
Error messages
This section describes the configuration of the message texts that are
presented to the PGP user.
Error messages are generated by validation processes and presented within
appropriate windows.
Messages and helps are provided with the basic system. Texts may be
customized and/or translated into national languages, before running the
appropriate builder processors.
The file BEMFDECK.XML, located in the \Deck folder, defines the PGP error
messages.
The file BEMF2DECK.XML, located in the \Config\Deck folder, may define
the application specific messages.
Both files define the error messages of the whole system. The format of the
two files is the same.
The base PGP does not provide an empty BEMF2DECK file. It may be
derived from BEMFDECK when application specific error messages must be
added.
The processor BEMF performs the configuration of error messages. The
XML format, support the standard XMl syntax, and is defined in the following
example:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<ERR_MESSAGES action="xxx">
<MESSAGE code=xxx" value=xxx" />
376
9AKK101130D1382
...
...
</ERR_MESSAGES>
Format
Opt/Mnd
Character
Action code.
Range
Default
{init,add,replace}
Mandatory
None
Description
code
Character
or integer
Mandatory
value
Character
Mandatory
None
<string>
None
The syntax of error messages is not quite the same as the syntax used for
alarm messages. A dynamic is represented by the symbol %. The following
table lists possible symbols used in text definitions.
Table 141. Message Subsystem - Text Definition Symbols.
Symbol
%s
%d
Field Type
String
Digit
9AKK101130D1382
Description
The field will be filled by a sequence of characters.
The field will be filled by a set of digits to represent an integer or a
real number.
377
The format of the dynamic is specified as part of the text. It is located at the
end of the message and is preceded by a comma.
Below, an example of an error message with a dynamic is given.
Name %s already defined for another item, a20
The message text includes the dynamic %s. That is, a string will be
embedded within the text and its length is 20 characters as defined by a20
at the end of the message.
Each message text is closed by a double quote.
378
9AKK101130D1382
Start PGP
Overview
PGP can be activated on demand or automatically. The Start PGP function
allows for on-demand activation.
Activating PGP
Select following menu:
> Start (on the desktop)
> Programs
> ABB Industrial IT
> Power Generation Portal
9AKK101130D1382
379
PGP Description
Refer to the InformIT Power Generation Portal User Manual.
PGP Explorer
Overview
PGP Explorer is the main interface window to the operator, it can be opened
on demand. The PGP Explorer function allows on demand activation.
When PGP starts up, PGP Explorer automatically opens the interface
window. If the interface window closes or is closed for any reason PGP
Explorer function re-opens it without to completely shutdown and restart
PGP.
380
9AKK101130D1382
This is the folder available to host the application displays, i.e. the graphic
pages to be presented on the screen.
STD_SYM
9AKK101130D1382
381
SYM
382
9AKK101130D1382
9AKK101130D1382
383
384
9AKK101130D1382
<INSTALLDIR>\Config\Sodg\Sym\<appl_symbol_name>.dt
<INSTALLDIR>\Config\Sodg\Display\*.dt
<INSTALLDIR>\Config\Sodg\Display\<display_name>.dt
The wild-card allows specifying all elements in the path. The file
specifications <std_symbol_name>, <appl_symbol_name> and
<display_name> identify a generic name.
This is the syntax to be used to process a single element.
The figure below shows the path identification and selection window.
9AKK101130D1382
385
Displays can be stretched to fully fit the display area or can be forced to
keep the horizontal/vertical aspect ratio. This option allows selecting
one of the two display formats. The keep ratio option is the default
setting.
386
9AKK101130D1382
9AKK101130D1382
387
Picture - This field is inserted in the symbol name only for the "graphic"
symbols (Advanced dynamic analog/digital) and is the name of the first
graphic object included to define the dynamic.
_XX - This field is automatically included when the symbol name file is
already existing but defines a different dynamic (could change a color, a
name of one graphic symbol, etc.); in this case is necessary to assign
another name to the new symbol in order to distinguish symbols similar but
not equal. You can verify the differences opening with a text editor the .DT
files.
At the end of the processing of the custom SODG .DT files (first standard
symbols, then symbols and then displays) in the SODGLIBSYM you can
found the new .DT files; processing these files, will be created global
dynamic symbols (in the eix_work folder the editable files, in the eix_bin
folder the executable files).
These global symbols will be displayed by the DisplayBuilder in the list of the
global symbols and could be selected to insert them in the displays.
These global symbols are "simple" because they include only a single
dynamic object without actions: therefore details (like parts of valves to
define the type), sensible areas, etc. are missing.
These global symbols can be customized with more details using the
DisplayBuilder.
In these global symbols the tags are defined normally as %TAG%, but,
where is required a specific tag type, you can found also %TAG_DIGITAL%,
%TAG_ANALOG%, %TAG_MSDD%, etc.
NOTES: in the displays generated with the SODG translator there aren't link
with these global symbols: the graphic pages are created like old releases.
DT Symbols Files
The SODG.EXE program manages the symbols pages (in the previous
release was skipped) to generate from them the PGP global symbols; these
symbols could be many complexes according to the commands included in
the .DT file.
388
9AKK101130D1382
9AKK101130D1382
389
Double clicking EIXCMP in the right view, the interface window of the
display compiler will be opened.
Compiling Displays
The figure below shows the schematic of the compiler window.
390
9AKK101130D1382
<INSTALLDIR>\Display\Upg\*.g
<INSTALLDIR>\Display\Upg\<display_name>.g
The wild-card allows specifying all elements in the path. The file
specification <display_name> identifies a generic name. This is the syntax
to be used to process a single element.
The figure below shows the Path identification and selection window.
9AKK101130D1382
391
Display Builder
Overview
A built-in display builder allows you to edit application displays on board the
PGP. Translated displays or new displays can be edited. Edit of drawing is
based on an on-board editor.
Refer to the InformIT Power Generation Portal Display Builder Manual for
more information.
392
9AKK101130D1382
Once the target database has been created and initialized, PGP connects
and updates it whenever a change occurs in its internal structures, either in
case of configuration changes or historical archiving. All the data exported to
the target database is then fully accessible by any tool supported by the
target database itself, although for some data structure the recommended
access is read-only.
Historical Backup
Overview
PGP gives the capability of historical backup archiving for most important
medium term archives.
9AKK101130D1382
393
The words historical backup classes a set of archives kept for a non predefined amount of time. All medium term archives last a fixed time interval or
keep a fixed number of items thus limiting de-facto the time interval or keep
a fixed number of files. Historical backup archiving allows keeping
snapshots of medium term archives for a long period of time without any
time or counter expires.
That does not mean historical backup archiving enlarges medium term
archiving time capabilities. Medium term archiving keeps its time limits as
configured. Historical backup archiving saves images of medium term
archives.
Historical backup archiving media may be the same hard disk hosting PGP
or may be an external device as a tape or a CD device. Historical backup
data files are created on the hard disk, then they can be possibly copied to
the external device.
The backup files produced by the Historical backup will not saved to
the Long Term Archive, also if it is configured.
The hard disk area will be called intermediate storage in the following
description.
This section describes the procedures to activate the utility. Moreover, it
describes the steps to save archives, to retrieve saved archives.
Archives
Some of the medium term archives are eligible for historical backup
archiving. They can be saved and, in a later time, retrieved for analysis.
The archives listed below are eligible for historical backup archiving:
> Alarm Archive
> Trend Group Archive
> Playback Archive
> Post Trip Archive
> Totalization Archive
394
9AKK101130D1382
Alarm Archive
The alarm archive, called Operator Journal or OJ also, stores the most
recent alarm messages, information messages, diagnostic messages, etc.
generated as result of the alarm processing.
Historical backup archiving copies the current contents of the archive to the
intermediate storage area.
Retrieving dumps data from the intermediate storage to the PGP internal
area. That area is parallel to the current alarm archive area. Retrieved
historical alarm archive does not overwrite current alarm archive.
The viewer of historical alarm archive allows switching between current and
retrieved archive.
Playback Archive
Playback archive keeps the history on the medium term for all tags
configured in the PGP database. Only tags whose playback flag is set within
the PGP database are kept on playback.
9AKK101130D1382
395
Totalization Archive
The value of a tag can be involved in a totalization archive at configuration
time. Totalizers periodically process playback data of tags involved and
store the result of processing.
Both analog and digital tags can be configured for totalization. Refer to the
tag database configuration for details.
Archiving saves both analog and digital totalizations.
Retrieving restores data from a previously saved totalization archive and
overwrites the current one.
396
9AKK101130D1382
> Programs
> ABB Industrial IT
> Power Generation Portal
> System Setup
In this way, the interface window of the System setup management is
opened. Open on the left the tree of the item Utility to show the list of
configured utilities: click on
Historian Backup Manager
Double clicking HISBACKUP in the right view, the interface window of the
historian backup manager will be opened.
Archiving Interface
After the historical backup archiving has been activated the main interface
window opens. The figure below shows the main interface window of the
historian backup manager. The archive save-set list is empty: any archive
has been saved before for historical backup keeping.
9AKK101130D1382
397
398
9AKK101130D1382
In the following description the generic save, restore and delete procedures
are outlined. Specific save procedures may differ a little depending on the
kind of archive involved. The examples refer to trend groups.
Saving Procedure
Click the save icon or the save item of the Save menu to initiate a save
procedure.
9AKK101130D1382
399
400
9AKK101130D1382
Restoring Procedure
Click the Restore icon or select the Restore item of the Restore menu to
initiate a restore procedure.
The Restore dialog window opens. It lists all historical backup files located in
the default intermediate backup (hisbackup) folder. Navigate through folders
to locate the location folder if it differs from the default folder.
Select the archive to be restored. The figure below shows a dialog window
where a file has been selected for restoring.
9AKK101130D1382
401
Deleting Procedure
Click the delete icon or select the delete item of the Delete menu to initiate a
delete operation.
402
9AKK101130D1382
9AKK101130D1382
403
The one shot backup utility can be configured to run periodically (each
individual day can be flagged for activation) and the running time (hh:mm)
can be defined. Archives involved in backup can be flagged also. By default
all archives are involved.
A set of registries, defined under the OneShotBckp sub-root of the PGP
registries, allows defining all environment parameters. Refer to Section 1 of
the Configuration Manual (Chapter on System Configuration) for details on
OneShotBckp registry set. The utility itself can set default registry values.
All files produced with one shot backup will be sent to the Long Term
Archive, if it is configured.
This section describes the procedures to activate the utility.
404
9AKK101130D1382
9AKK101130D1382
405
Save/Restore Configuration
Overview
A specific application PGP configuration is generically based on registry
values, configuration and displays files.
Registry values are located under the PGP folder of registry keys.
Configuration files are located under the <INSTALLDIR>\Config folder.
Displays files are located under the <INSTALLDIR>\display folder.
The Save/Restore Configuration utility allows you to save and to restore
registry and files of configuration and displays.
Save Config/Display/Data
When the Save item is selected, the right side of the dialog window
changes.
Check boxes, which select the elements of the configuration in order to save
them, are shown on the right side. Registry values are always saved as a
whole. The file configuration or displays can be either fully or partially saved.
406
9AKK101130D1382
The interface window of the utility is shown in below: the procedure shows
the interface to save the configuration files; the same procedure can be
followed to save the displays files.
9AKK101130D1382
407
408
9AKK101130D1382
At the bottom of the interface window a data entry field allows you to type
the destination folder. The path and file name can be typed within or a
browser can be opened clicking on the square button on the right side.
Since the save settings utility uses a DOS program, the file names must be
limited to 8 characters.
The figure below shows the browser window.
9AKK101130D1382
409
containing the saved configuration. All files are named as defined in the file
name field.
Is possible also to send the backup files to the Long Term Archive function;
a specific question will be showed at the end of the save function: choosing
YES, the backup files will be saved in a compressed file (using the
command defined in the registry APPS\OneShotBckp\ZipCmdLine) that will
be archived in the Long Term Archive as Miscellaneous file.
Restore
A saved configuration can be restored in the same application or on another
application (another machine).
When the Restore icon is selected the right side of the dialog window
changes again. The figure below shows the selection to restore the
previously saved configuration.
410
9AKK101130D1382
9AKK101130D1382
411
412
9AKK101130D1382
The LTA saves on a specific drive these files; the drive may be the same
hard disk hosting PGP or may be an external device.
Archives
The archives listed below are eligible for LTA: they can be saved and, in a
later time, retrieved for analysis; the boldface text describes the suffix to
identify the file type:
> ALM - Alarm Archive (One Shot Backup)
> GRP - Trend Group Archive (One Shot Backup)
> PLB - Playback Archive (One Shot Backup)
> PTL - Post Trip Archive (One Shot Backup)
> REP - Report Archive (RPTPRN)
> MSC - Total Counter Archive (TENESM)
> MSC - Maintenance Archive (HRTLSM)
> MSC - Sequence of Events Archive (ALACSOE - RISPRN)
> MSC - SysSetup saved files (SYSSETUP)
Registry
In the PGP server(s) must be written in the registry
APPS\OneShotBck\LTAServer the name of the PGP where is activated
the LTA function (LTA server): can be itself or another server; defining this
registry with a valid server name, will be enabled the function to send the
medium term historical files to the LTA.
On the LTA server must be changed in Sizes following registry:
9AKK101130D1382
413
> N.DAYS - defines the number of days of the Circular Buffer (default 0;
insert a positive value to enable LTA function)
> N.LTAS - defines the number of record for file F_LTAS (default 0; set
to 1 to enable the LTA function because onle one record is necessary
for this file)
> N.SRVR - defines the number of servers configured to collect
historical files (default 0; set equal at the value assigned to the registry
Sizes\MXNODE to enable the LTA function)
In the LTA server must be defined the registry Directories\LTAHisBackup
defining the path where the medium term archives will be sent.
On the LTA server must be defined for Directories\LTA following registry:
> CircleBufferPath - defines the main path where will be saved the files
of the Circular Buffer.
> EmergencyPath - defines the path where will be saved the daily files
when some error will be found on search room in the Circular Buffer.
> InBufferPath - defines the path where are copied momentarily the
daily files received from PGP servers.
> ReportPath - defines the folder where will be saved the report
produced after the save of the daily files.
On the LTA server must be defined for APPS\LTA following registry:
> InitialWait - defines the number of milliseconds to delay the start of
the LTA manager (default 30000).
> PollingDeadLine - defines the end polling time (string - hour.minutes)
(default 08.15)
> PollingStartTime - defines the start polling time (string hour.minutes) (default 08.10)
> PollingTime - defines in milliseconds the timer used in the polling
phase to check the received daily files (default 30000).
> StatusTagName - defines the name of the tag defined on the linked
servers to notify the status of the LTA function; the tag must be
configured as:
414
9AKK101130D1382
9AKK101130D1382
415
> Trace - enables the complete trace in the LTA log file of all messages
produced by LTA manager (default NO).
Additional APPS\LTA registry used to define the parameters to archive files
(LTADrive functionality) on specific path (LTADrivePath) organized by
servername/date/type without time limits (suspended only when the drive is
FULL):
> LTADriveIsToActivate - flag to enable LTADrive function
Additional Directories\LTA registry for LTADrive functionality:
> LTADrivePath - defines the path where will be saved the files by
servername/date/type.
Installing on the LTA server a program like NERO InCD (only for
rewritable disks) or Sonic DLA to format discs (CD/DVD) in such a way
that they can be used like hard disks, you can define in the LTADrivePath
registry directly the path of the CD/DVD to archive on it the files. Using
one of these tools you can archive your files to a removable drive without
use the LTADriveCmd program: in this case is necessary to
remove/rename the PGP registry trees named RemovableDrive
(APPS\LTA and Directories\LTA) following described.
Additional APPS\LTA\RemovableDrive registry used to activate specific
program to transfer files from LTADrivePath to a removable drive:
> CmdGetInfo- command string to send to the specified program to
have the info about the used removable drive; the activated program will
write following registry:
> SizeFree - free size of the removable drive
> SizeTotal - total size of the removable drive
> SizeUmCode - Number to indicate the E.U. used for the Size*
(0=GB, 1=MB, 2=Blocks)
> CmdPgmCode - resulting command code - defines the status of the
last requested command (-1=InProgress, 0=Good, Other=Error).
> CmdPgmName - Name of the program to active to write the archived
files on the removable drive.
416
9AKK101130D1382
Functionality
The managers of medium term archives send to the LTA server, in the folder
defined by the LTAHisBackup registry, a copy of the produced files, naming
servername+filename
servername can be the name of sending server, if is not defined the
PlantUnit, or PLANT_UNIT_n where n is the number of defined PlantUnit.
Following the main phases of LTAExplorer:
> Internal timer - with a specific delta time (5 seconds) are executed
following actions:
- all configured server are checked to get the status;
- to all connected server is updated the tag (named as defined in the
StatusTagName registry) with the current status of the LTA function
- all files written by the PGP servers to the folder defined by
LTAHisBackup are copied to the folder defined by InBufferPath,
removing from the file name the servername+; the files are ordered by
server name/archive type.
9AKK101130D1382
417
> Polling - When a start polling time is found, is activated a timer scheduled
as defined in the PollingTime registry; each time, are checked all received
files to send a message to the server when not all historical configured types
are found.
> Updating Circular Buffer- When the end polling time is found, all files in
the InBufferPath are copied to the circular buffer ordered by server
name/archive type.
> Writing to LTA drive - this phase is activated only if is enabled the
LTADrive function; the files archived in the CB are copied to the
LTADrivePath; the files will be saved on LTA drive by server
name/date/archive type. If is defined also the RemovableDrive program
management, in this phase will be executed also the transfer from the
LTADrivePath to the removable drive; all transferred files will be removed
from the LTADrivePath.
The phases in boldface can be also forced manually by operator using
specific dialog.
LTA Interface
After the LTA Explorer has been activated, the main interface window is
opened. The figure below shows the main interface window of the LTA
Explorer.
The window includes different areas to show LTA informations.
418
9AKK101130D1382
FileView
This area shows the folders of different intermediate storage used by LTA.
9AKK101130D1382
419
420
9AKK101130D1382
> Emergency - this folder is used by the LTA Explorer only to save the files
received by the servers when no place is found in the CB (for example when
is found a file too much old to be inserted in the CB).
> LTA Drive or Recording drive - LTA Drive is displayed only when the
LTADrive function is active; if an external drive manager is defined (used
LTADriveCmd), will be showed Recording Drive. Shows the folder/files of
Long Term Archive files ordered by server/date/type.
Configured Servers
This area shows the configured servers.
9AKK101130D1382
421
LTA Status
This area shows informations about the status of the LTA manager.
422
9AKK101130D1382
> Message Log - in this area are written all LTA messages (trace and
errors); double clicking on one row, you can remove, selecting YES in the
displayed window, all rows currently showed in this area.
> LTA phases - In this area are showed all possible status of the LTA
manager:
Waiting Start Time - The Day is changed and the program is waiting for
the Polling Start Time
Polling - The polling phase is in progress
Polling - Time Terminated - Intermediate status between end of Polling
and activation of Server to In; probably never visible because the
execution time is very short.
Server to In - After the polling the program check in the LTAHisBackup
folder to transfer files received by servers to InBufferPath folder; this
phase will be selected only if a big number of files will be sent by
servers because normally this copy is executed periodically by the
internal LTA timer.
Updating Circular Buffer - all files received form the connected servers
are copying to the CB folders.
Writing to LTA Drive - If configured, the LTA drive manager is copying
all files from CB to the LTA drive and, if configured, from LTA drive to
Removable drive.
LTA drive status
This area shows the status of the drives used by LTA manager.
9AKK101130D1382
423
424
9AKK101130D1382
9AKK101130D1382
425
Writing to LTA Drive (if configured) - all new files will be written from CB
to archive disk
Waiting Tomorrow - wait tomorrow
The changes will be accepted selecting Update LTA Status button.
LTADriveCmd program
LTADriveCmd works using NERO 6 utilities and is necessary to install
NERO 6 on the LTA server to can use it; derives from NeroCmd and
manages the access to the defined removable drive. Is activated by
LTAExplorer using following PGP APPL\LTA\RemovableDrive registry:
> CmdGetInfo - this is the command line used to activate the program
when is necessary to have the informations about the drive: the
program will load these registry
> SizeFree - free size of the removable drive
> SizeTotal - total size of the removable drive
> SizeUmCode - Number to indicate the E.U. used for the Size*
(0=GB, 1=MB, 2=Blocks)
> CmdWrite - this is the command line used to activate the program
when is necessary to write archived files to the drive if is not empty.
> CmdWriteEmpty - cthis is the command line used to activate the
program when is necessary to write archived files to the drive if is
empty.
> CmdPgmCode - in this registry (initialized with -1 by LTAExplorer
before activate the program) will be written the resulting command
code:
> -1 - In Progress
> 0 - command executed
> Other values - Error on command execution
In the command lines you can use following specific keys:
426
9AKK101130D1382
> ?WRITE - this key will be replaced with the default command line to
write files to the drive
> ?WRITE_EMPTY - this key will be replaced with the default command
line to write files to the drive when is empty
> ?APPEND - normally a new log file is produced when is executed a
write to the drive: you can add this key to the write command lines to
append the trace lines to the existing log file (for example you can use
this key only for CmdWrite command line to create a new log file only at
the first write to an empty drive).
> %drive - this key will be automatically replaced by LTAExplorer
before activate the program with the root of the defined drive.
> %label - this key will be automatically replaced by LTAExplorer before
activate the program with the label to assigne to the drive: the label is
formatted as YYMMDD-yymmdd where YYMMDD is the date of the
oldest file archived on the drive and yymmdd is the most recently.
> %folder - this key will be automatically replaced by LTAExplorer
before activate the program with the folder including the files to archive
to the drive (defined in the LTADrivePath registry).
LTADriveCmd program produces in the folder defined by the system
environment registry TEMP following trace files:
> LTADriveCmdInfo.log when are requested the informations about the
managed drive
> LTADriveCmdWrite.log when is executed a write to the drive.
9AKK101130D1382
427
People Finder
Overview
The People Finder application allows the notification to the assigned staff of
the occurrence of alarm situations by means of the dispatch of a SMS to a
mobile phone.
Following a user defined event, like any type of configurable alarms, the
OGP server, using a GSM modem (not included in the PGP supply, will send
a SMS to the shift operator defined in the shift book, and a warning call to
his/her mobile phone. The answer to the warning call will determine the
acknowledgement of the alarm.
If the shift operator does not answer the call (which is repeated for a
configurable number of times) the program repeats the dispatch of the
message and dials a call to the mobile phone defines as Recovery.
Following the list of GSM modems tested for People Finder function:
Digicom Pocket GSM
Falcon A2D-1
Siemens TC35t-AT
Database
In order to trigger the sending of a SMS in case of alarms, the corresponding
tags in the PGP database must be configured with a positive value (1-15) in
the SMS Index field. This index refers to the SMS to use in case of the
occurrence of an alarm for that tag (see section: Shift book configuration
file).
Registry
In the PGP server must be defined for APPS\Finder following registry:
Serial Port configuration parameters (name - default):
> Port - COM3
> BaudRate - 19200
428
9AKK101130D1382
> ByteLength - 8
> StopBits - 1
> Parity - NONE
Function customizing parameters (name - default - description):
> CPIN - 8629 - PIN code
> Repeat - 3 - Number of call attempts to the shift operator before
transferring to the recovery number
> Read_Timer - 11000 - Wait time (in milliseconds) for an answer from the
modem
> Drin-Timer - 20 - Wait time (in seconds) for an answer to the call
> CnfPhonesFile - <INSTALLDIR>\Config\PeopleFinderPhones.xml - Name
of the Finder configuration file
> CnfShiftsFile - <INSTALLDIR>\Config\PeopleFinderShifts.txt - Removed
since 4.1 release
> WebFile - data\eMaintenanceStatus.xml - Web file definition for log
recording
> SendTagDescription - NO - YES to send in the SMS message the tag
description rather then the alarm comment
> SendExTagDescription - NO - YES to send in the SMS message the
extented tag description rather then the description
> DataCall - NO - YES to make a data call to the mobile phone (a voice call
is otherwise made)
> DisableAckFromSms - NO - YES to acknowledge the alarms only
answering to the mobile phone call
> TraceLog - NO - YES to have more details in the log file about the
operations executed by the program
9AKK101130D1382
429
430
9AKK101130D1382
9AKK101130D1382
431
New Phone
Selecting New Phone will be showed following window
432
9AKK101130D1382
Phones
When the Phones item is selected, the right side of the dialog window
changes.
9AKK101130D1382
433
434
9AKK101130D1382
Sms Index
Opening all items in the Index tree and selecting an item Index n, the right
side of the dialog window changes.
9AKK101130D1382
435
remove the SMS Index configuration; is possible to cancel a SMS Index also
select it on the right view and after press the Delete key of the keyboard.
Shift and Phones configuration files (before PGP 4.1 release)
To manage also the old configuration files, People Finder can read the
configured shifts and phones from two different files defined in the specific
registry: the old configuration is managed only when in the CnfPhonesFile
registry is defined a file name not .xml.
Shift Book Configuration File
Each record of the Shift Book Configuration File must have the following
structure:
IDXSMS,START_DATE,END_DATE,CODGSM,TIMEOUTACK
Where:
> IDXSMS - SMS index (1-15)
> START_DATE - Shift start date (DD MMM YYYY hh:mm:ss)
> END_DATE - Shift end date (DD MMM YYYY hh:mm:ss)
> CODGSM - identification code of the shift operator (0-9 A-Q)
> TIMEOUTACK - Wait time (in minutes) for ack
Example:
1,28 NOV 2003 02:00:00,31 DEC 2003 23:00:00,A,1
2,28 NOV 2003 02:00:00,31 DEC 2003 23:00:00,B,1
Notes:
> The comment lines in the file are identified by the character !
> Dont use numbers or upper case letters after a space in comments
> The identification code of the shift operator is used to access the phone
book definition file: dont use the R code (recovery)
> The SMS Index, together with the date/time when the alarm happened, is
the access key to the file, and will identify the code of the shift operator to
which the event must be reported
436
9AKK101130D1382
Functionality
Following the occurrence of an alarm for a tag where SMS Index field is
greater than zero, the People Finder program (Finder.exe) will use this index
combined with the current date and time to retrieve from the Shift Book
configuration the code of the shift operator to which the notification must be
sent.
With this code, it will access the Phone Book parameters to retrieve the
mobile phone number and send the SMS formatted as follow:
9AKK101130D1382
437
438
9AKK101130D1382
Real-time Utilities
By clicking with the right mouse button on the icon (a small phone) in the
System Tray showing the program activity, a menu containing the following
items are displayed:
Close - closes the menu
Open Log File - opens a window to access and display the log file
Function Status - presents the state of the function
Enable - enables the function suspended
Disable - disables the function if active
Update Shifts - after the modification of the shifts, loads the new
configuration
Acknowledge all Alarms - acknowledges all pending alarms
Stop - stops the program
9AKK101130D1382
439
440
9AKK101130D1382
9AKK101130D1382
439
440
9AKK101130D1382
Assumptions
The following assumptions apply to a distributed architecture.
9AKK101130D1382
441
Server Functions
PGP maintains a consistent configuration and operational environment on
all nodes of the distributed architecture.
The Server nodes exchange information and data, either during the on-line
operation or in off-line mode. Some data exchange is performed
automatically by the system, while other exchanges are activated by a user
request, as described in the following description.
On-line Features
The main data exchanged among servers, during the normal on-line
operations, is related to the following functions.
442
acknowledge alarms,
9AKK101130D1382
Initialization Features
The following functions are performed during the start-up phase of a server,
in order to keep it updated the most as possible.
9AKK101130D1382
443
chronological alarms,
periodic logs,
playback data,
calculated tags,
historical groups.
Client Functions
Similar to the standard Client/Server architecture, each Client participating
to a distributed architecture can be connected to one or more Servers at a
time.
Each Client, however, may connect every Server in the system, without any
restriction. Each Client maintains a list of known Servers, which is used by
the following functions; the first Server in the list is considered as the
referring Server.
444
9AKK101130D1382
of known Servers, and try to connect to the Server until the connection
is successful. The same procedure is performed during the Client startup.
ALIGNSPECS Program
This program manages the alignment of the specs of the INFI stations to the
configured servers (parameters defined in the APPS\ALIGNSPECS
registries) when is defined a PGP architecture with PGP servers not directly
connected to INFINET via ICI.
Runs only at PGP startup and the initial delay must be enough to grant that
the servers connected to the ICI have their database updated.
9AKK101130D1382
445
446
9AKK101130D1382
9AKK101130D1382
445
OPC Overview
The OPC specification describes the OPC COM Objects and their interfaces
implemented by OPC Servers. An OPC Client can connect to OPC Servers
provided by one or more vendors as shown in the figure below.
446
9AKK101130D1382
9AKK101130D1382
447
There are two types of groups, public and local (or private). Public is for
sharing across multiple clients, local is local to a client.
The PGP OPC server does not support public groups, neither any
specific interfaces about such a groups. Only private groups are
supported.
Within each Group the client can define one or more OPC Items.
448
9AKK101130D1382
9AKK101130D1382
449
450
9AKK101130D1382
9AKK101130D1382
451
Default Value
2 seconds
4 seconds
See note 1 at the end of the table.
StatusTimeOut
1 seconds
ItemPacketSize
500
Note 1:
Generally the DeviceTimeOut value is greater than CacheTimeOut one.
The PGP OPC server supports six group update rates.
Refer to Table 189 for the DataAccess Client refresh rates.
Table 143. Client DA Refresh Rates
Code
Description
500
500 milliseconds.
1 second
4 seconds
10
10 seconds
30
30 seconds
60
60 seconds
Note 2:
Any other refresh rate configured by the user will be rounded towards one of
the above PGP supported rates.
452
9AKK101130D1382
The server requires periodically to PGP the values of the active items
belonging to groups that are active and scheduled in that specific time.
The group refresh rate establishes when group must be managed (in
other words, whether it is scheduled) in that specific time. This is done
in order to avoid server overhead but read is done regardless item value
changes.
The server periodically checks the PGP queue for item changes. Items
not changed are not managed (because they are not contained in
queue) but it is possible to receive items not active or belonging to
inactive and/or not scheduled groups (the PGP ignores OPC
specifications).
These read methods can be set from the windows registry. Open the
KEY_LOCAL_MACHINE key, then the SOFTWARE key, then the ABB key,
then the PGP key, then the APPS key and finally the OPC key.
ReadFromQueue registry can be set to the following values:
1.
2.
9AKK101130D1382
453
In both cases, the data value could be slightly different from the value at the
time when the client requires data.
The PGP OPC server supports several group update rates. Refer to the
refresh rates in the description of OPC parameters of a database tag.
Client refresh rates less than 500 msec will be set to 500 msec.
Client refresh rates between two server supported rates will be set to
the higher one.
454
9AKK101130D1382
Implemented
IOPCServer
Yes
IOPCServerPublicGroups (optional)
No
IOPCBrowseServerAddressSpace (optional)
Yes
Yes
Yes
Yes
IPersistFile (optional)
No
Implemented
IOPCGroupStateMgt
Yes
IOPCPublicGroupStateMgt (optional)
No
Yes
No
IOPCItemMgt
Yes
Yes
IOPCSyncIO
Yes
No
9AKK101130D1382
455
Implemented
Yes
The 1.0a interfaces have not been implemented. However 1.0a registry
setting are still present. An OPC client 1.0 is able to connect to the PGP
OPC Server. For example reading items in the synchronous read mode
version 2.03 differs from the 1.0a in the exception and asynchronous read
mode.
The PGP OPC AE Client does support only condition related events and
does not allow any filtering on the OPC Server.
The PGP system supports Level, Deviation and Rate Of Change alarm
categories for analog tags. Therefore, PGP OPC AE Client manages related
PGP structures for these alarms but uses the Bad quality flag of the tag to
notify alarm to PGP.
456
9AKK101130D1382
The PGP OPC AE Client does not support any generic alarms from an OPC
Event server not related to a PGP tag. It is required that the Tag Name
configured in the PGP database corresponds to the OPC alarm source.
OPC Server AE
The OPC AE Server implements all the mandatory interfaces related to the
1.02 OPC specifications and also the optional interface
IOPCEventAreaBrowser.
Table 193, Table 194 and Table 195 summarize.
Table 147. OPC Event Server
Interface
Implemented
IOPCEventServer
Yes
IOPCCommon
Yes
IConnectionPointContainer
Yes
Implemented
Yes
Implemented
IOPCEventSubscriptionMgt
Yes
IConnectionPointContainer
Yes
It is losely coupled (as the PGP DA OPC) to the PGP system. All the alarms
provided by the server are received from the PGP system and forwarded to
any connected client.
9AKK101130D1382
457
458
9AKK101130D1382
DA opc groups and AE subscription will be activated for the source machine
only (they will be inactive in all the other machines). In accordance with the
OPC Specification, data will be received from one server only (the "active"
one) that is no multiple read will take place.
If the client reads by exception, it periodically calls the opc "GetStatus"
method to know the server status. If some errors occur (wrong server state
or RPC errors) it will switch onto another available server, simply making its
opc group active (quick data reception and short transition time).
If the client reads in sync way, errors on the periodical "SyncRead" opc call
will get the client switched to another server. Therefore, the automatic
switchover policy during client's activity is basically based on errors on OPC
calls.
Note that the client does not "switch" among the servers actually. It is always
connected to them and it simply sets the opc groups inactive/active (in other
words, it is the data source that is different).
9AKK101130D1382
459
2.
3.
460
9AKK101130D1382
Allow Launch
INTERACTIVE
Allow Launch
SYSTEM
Allow Launch
4.
Administrators
Full Control
CREATOR OWNER
Full Control
Everyone
Read
INTERACTIVE
Special Access
SYSTEM
Full Control
2.
Default Properties and Default Security Tabs can be left the same as
the ones of the client machine.
3.
Select the OPC Server from the list of the available applications.
4.
Click the Properties button: a new dialog box appears on the screen.
5.
9AKK101130D1382
461
Allow Access
Allow Launch
Everyone
Allow Launch
INTERACTIVE
Allow Launch
SYSTEM
Allow Launch
Full Control
CREATOR OWNER
Full Control
Everyone
Read
INTERACTIVE
Special Access
SYSTEM
Full Control
Identity:
The interactive user
462
6.
7.
9AKK101130D1382
PGP
OPC
1 - 200
201 - 400
401 - 600
601 - 800
801 - 1000
9AKK101130D1382
463
Note that the opc priority values range ("OpcRange") can be represented by
using "[" or "(" parenthesis, where "[" means "value included" and "(" means
"value not included" and therefore both range "[1,300)" and "[1,299]" have
the same meaning.
Mappings can be accomplished both on a opc AE server and alarm category
basis. If the name (ProgID) of the current connected AE server is not
defined in the OpcPriority.xml file, the below default section will be used
during OPC to PGP priority translation:
464
9AKK101130D1382
The proposed mapping is the default one described in the table above. Note
that you can define different alarm categories inside this section. In this
case, not any category is defined but the "DEFAULT" one, meaning that all
received alarms/events priorities will be mapped that way regardless any
category.
If you want to define a different mapping for a specific opc AE server, you
should define that AE server inside the file. You can manually copy and
paste the section below and change it on the basis of your needs:
9AKK101130D1382
465
466
9AKK101130D1382
The following table lists the proxy dll names corresponding to the different
opc specifications:
Name
OPC Specification
"OPCCOMN_PS.DLL
"OPCPROXY.DLL
"Data Access
"OPC_AEPS.DLL
"OPCHDA_PS.DLL
9AKK101130D1382
467
468
9AKK101130D1382
Appendix A Tables
Tag Types
Table 150. Tag Types.
Code
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
Tag Type
ANALOG
CLIF
DAANALG
DADIG
DADIGTL
DANG
DD
DEVSTAT
DIGITAL
INTANG
INTDIG
MSDD
N90STA
RCM
RMCB
RMSC
STATION
TEXT
TEXTSTR
UNDEF
EXTANG
EXTDIG
ANGRPT
DIGRPT
LABANG
9AKK101130D1382
Description
Analog.
Configured logic interface function (not supported).
Data acquisition analog.
Data acquisition digital.
Data acquisition digital (not supported).
Data acquisition analog.
Device driver.
Device status.
Digital.
Internal analog.
Internal digital.
Multi state device driver.
Symphony status.
Remote control memory.
Remote motor control block.
Remote manual set constant.
Station.
Text selector tag.
Text string.
Undefined tag type.
External analog.
External digital.
Symphony generated analog.
Symphony generated digital.
Analog lab data entry.
469
470
Tag Type
LABDIG
CALCANG
CALCDIG
APMSSTA
NODESTA
BITMASK
COMPOSIT
INTEGER
UINTEGER
BYTEARR
ANAEIN
ANAEOUT
DIGEIN
DIGEOUT
DATETIME
DELTATIME
TCPADR
Description
Digital lab data entry.
Analog calculated tag.
Digital calculated tag.
Node status.
Node status.
Mask of bits.
Composite.
Integer format.
Unsigned integer format.
Byte array format.
Analog Extended input.
Analog Extended output.
Digital Extended input.
Digital Extended output.
Date and Time format.
Deltatime format.
TCP address.
9AKK101130D1382
Tag Sources
Table 151. Tag Sources.
Code
1
2
3
4
5
6
7
8
9
10
11
12
13
14
Tag Source
C-NET
EXT
CALC
LAB
USER
DEVSTA
TAGGEN
OPC
AC800F
AC800M
MELODY
AC870P
PROP13
Description
Infinet tag.
Generic external communication.
Internal calculated tag.
Lab data entry tag.
User application tag
Device status tag.
Generated tag.
OPC tag.
Reserved
AC800F tag.
AC800M tag.
MELODY tag.
AC870P tag.
PRO Control P13 tag.
9AKK101130D1382
Color
Black
Red
Green
Yellow
Blue
Magenta
Cyan
White
Orange
Slate Blue
471
Color
Hot Pink
Sea Green
Spring Green
Chocolate
Lavender
Sandy Brown
Tomato
Turquoise
Deep Pink
Dark Violet
For compatibility with older PGP versions, the first eight colors in the table
match the old color table.
The color table above is defined in the BattColors file. The default color
scheme defined in the BattColors file can be modified changing the RGB
pattern definition (e.g. RGB(80,80,80), RGB(FF,00,FF)) and typing the color
name (e.g. gray, fuchsia) as defined in the Internet Explorer color table.
When a Internet Explorer color name is used, the RGB definition can be left
undefined typing RGB(-1,-1,-1). The color name is always mandatory.
Since a Internet Explorer color may not have a name defined, a color name
must be associated to such color in order to use it in the BattColors file.
Valid color definitiona are the following:
RGB(-1,-1,-1) - fuchsia
RGB(FF,00,FF) - fuchsia // Same as previous
RGB(FF,99,FF) - lightfuchsia // New color name
RGB(-1,-1,-1) - gray
RGB(80,80,80) - gray // Same as previous
RGB(CC,CC,CC) - dust // New color name
RGB(-1,-1,-1) - lime
472
9AKK101130D1382
9AKK101130D1382
473
DI
*
*
RCM
*
*
DD
*
*
MSDD
*
*
*
*
SPDT
*
*
*
*
DCS
*
*
MS
*
*
*
*
*
FVTEESTATE
FB1_0STATE
FB1_1STATE
FB2_0STATE
FB2_1STATE
FB3_0STATE
FB3_1STATE
FB4_0STATE
FB4_1STATE
*
*
*
*
*
*
*
*
*
*
*
*
474
Action Code
X
E
C
D
Description
Skip. ICI ignore the tag.
Establish Only.
Establish and Connect.
Define for Output.
9AKK101130D1382
9AKK101130D1382
Point Type
Not defined.
Process Variable.
Set-point Read.
Control Output Read.
Ratio Index Read.
Analog Read.
Station Status.
Digital Read.
Set-point Write.
Control Output Write.
Ratio Index Write.
Station Mode.
Analog Report.
Digital Report.
Module Status.
RCM Read.
RCM Write.
Single Index Station.
Station Report.
RMSC Read.
RMSC Report.
R4 Analog Read.
R4 Analog Report.
Extended Module Status.
Not Defined.
DANG.
Not Defined.
Not Defined.
DD.
MSDD.
475
476
Point Type
SPDT.
Not Defined.
RMCB.
DDIG.
Not Defined.
Text Selector.
9AKK101130D1382
Time Units
Table 156. Time Units.
Code
Time Unit
0
1
2
3
4
5
Sec.
Min.
Hours
Days
Months
Years
Description
Seconds
Minutes
Hours
Days
Months
Years
Instrument Types
Table 157. Instrument Types.
Instrument Type
1-5 V
4-20 mA
TCK
TCJ
TCT
RTD
Description
High Level.
High Level.
Type K thermocouple.
Type J thermocouple.
Type T thermocouple.
RTD 100 ohms.
Description
Implemented
Unacknowledged
In alarm
9AKK101130D1382
477
478
Description
Old data
Off scan
Reserved
Inserted value
Alarm check disabled
Alarm inhibited
Reserved
Bad calculated value
Application specific 3
Red tagged
Hardware channel failure
Application specific 1
Application specific 2
9AKK101130D1382
Description
High instrument range
2-High alarm limit
High alarm limit
Low alarm limit
2-Low alarm limit
Low instrument range
Increasing ROC
Decreasing ROC
High deviation
Low deviation
Integer format
Tracking
3-High alarm limit
3-Low alarm limit
Auto/Manual
Dummy Packet (Playback only)
System Information
Table 160. Tag Configuration Retrieving Parameters.
Parameter
ProductName
ShortProductName
FullProductName
ProductFamily
ProductVersion
ProductCompany
ProductCorporate
Version
SubVersion
Build
9AKK101130D1382
Description
Name of the Product
Short name of the Product
Full name of the Product
Family Name of the Product
Version of the product
Company Name of the Product
Corporate Name of the Product
Release version
Release sub-version
Build Version
479
480
Description
Hot Fix
Number of tags
Numer of Tags Configured
Maximum number of Clients
Maximum number of PV
Maximum number of DI
Apms Parameter
Maximum number of Printers
Maximum number of ICIs
Number of ICI index
Maximum number of Calculation Blocks
Maximum Number of Historical Groups
Maximum Tag Info Type
Maximum File Key
Maximum Number of Totalizations
Maximum Events for SOE
Maximum Number of maintenance
Maximum Number of Post Trip Logs
Maximum Nuber of Displays
Maximum Nuber of Op Conf Displays
Maximum Numer of Alarm Priorities
Maximum # of alarm groups
Maximum number of Files
Maximum Lenght of Tag Name in presentations
Maximum Lenght of Tag Description in presentations
Maximum Lenght of Logic State Descr in presentations
Apms Parameter
Apms Parameter
Apms Parameter
Apms Parameter
Apms Parameter
Apms Parameter
9AKK101130D1382
9AKK101130D1382
Description
Apms Parameter
Maximum tags per Historical Group
Number of Alarm Action Programs
Maximum Number of Days for Keeping Playback archive
Maximum Tag Index
Maximum SOE Device
Number of files reserved for Playback
Maximum Number of Days for Keeping PTL archive
Apms Parameter
Number of Clients licensed
API is Licensed
Specific API is Licensed
ODBC is Licensed
WEB is Licensed
Process Control for INFI is Licensed
Display Builder is Licensed
Licensed DA Opc Server
Licensed AE OPC Server
Licensed HDA OPC Server
Licensed DA- write OPC Server
Numer of tags licensed for OPC
DDE is Licensed
Number of Tags licensed
Number of Tags Licensed
Simulation is Licensed
Calculation is Licensed
Steam Calculation is Licensed
Macro Calculation is Licensed
Scanner Drivers are Licensed
API RunTime is Licensed
Process Control is Licensed
Driver for INFI is Licensed
481
482
Description
Driver for DCI is Licensed
Driver for ODBC is Licensed
Driver for Modbus is Licensed
Driver for is Licensed
Driver for Spabus is Licensed
Driver for Iec101 is Licensed
Driver for Iec104 is Licensed
Driver for Text is Licensed
Driver for teleperm is Licensed
Driver for GsmMarkV is Licensed
Driver for Iec103 is Licensed
Driver for XX2 is Licensed
Driver for XX3 is Licensedr
Driver for XX4 is Licensed
Driver for XX5 is Licensed
Application Driver is Licensed
Maint Trigger Application is Licensed
Xml To CMMS Application is Licensed
PPP Application is Licensed
DPP Application is Licensed
TSE Application is Licensed
BSE Application is Licensed
TPA Application is Licensed
STP Application is Licensed
TSEOP Application is Licensed
BSEOP Application is Licensed
MSFDPP Application is Licensed
CPA Application is Licensed
Harmony Cfg Application is Licensed
XX2 Application is Licensed
XX3 Application is Licensed
XX 4Application is Licensed
9AKK101130D1382
9AKK101130D1382
Description
XX5 Application is Licensed
People Finder is Licensed
Licensed Process Control for Ac870P
Licensed Process Control for ProP13
License expiration
Server Name
Apms Parameter
The system is active
System shutdown in progress
Simulation is Active
Simulation is Frozen
Name of Client
Current Time
Current Time (string)
Current Time
Converted Time
Current Time from OS
Time of Last Startup
Percentage of use of Disk A
Percentage of use of Disk B
Percentage of use of Disk C
Percentage of use of Disk D
Percentage of use of Disk E
Percentage of use of Disk F
Percentage of use of Disk G
Percentage of use of Disk H
Percentage of use of Disk I
Percentage of use of Disk J
Percentage of use of Disk A
Percentage of use of Disk L
Percentage of use of Operator Journal File
Percentage of use of Playback Archive
483
484
Description
Percent of CPU Load
Apms Parameter
Size of Physical Memory
Low System Resources
Name of Logged User
Time of Login
Timeout For Auto Logoff
Record Index of Logged User
ID of Logged User
Local Node
The system is master
Index of the Master Node
Node Weight
Configuration is Aligned
Operator Journal file is Aligned
Historical Files are aligned
Playback Archive is Aligned
Post Trip Log Archive is Aligned
Node is Aligned
Node Alignment in Progress
Apms Parameter
Node Status Mask
Life Cycle for Networker
Nmber of nodes connected
Connection time
Connection Update
Mask of Enabled Alarm Printers
Ignore Remote IO Alarms
Time Synch INFI as OIS
DST sent on INFI
Apms Parameter
Time Synch Infi
9AKK101130D1382
9AKK101130D1382
Description
New Alarms are Uncked
Apms Parameter
Update tag value on Alarm Display
Queue Sequence of Events to Data Processor
Queue Sequence of Events to Log processor
Apms Parameter
Apms Parameter
Compress Playback
Invert Feedbacks on MSDD popup
Bad Quality marked as Alarms
Apms Parameter
Alarm Time includes Milliseconds
Broadcast Alarm Acknowledgements
Broadcast Alarm Silencing
Human Machine Language
Commands arfe enabled if Red Tag
Enable Printouts of all alarms
Rate for Control Increment
Rate for Control Fast Increment
Demo System
Maximum Alarm Messages per Display
Engineering Unit Text
Logic State Descriptor Tests
Mask of Quality Flag 1 for Bad
Mask of Quality Flag 2 for Bad
Time Unit Text
Tag Type Text
Historical Archive Text
Historical Archive DB
Type Info
Tag Info Type
Alarm Bitmap
485
486
Description
Day Of the Week
Day Light Saving Time is ON
Entries in Sequence of Events Queue
TIme in Composite Format
System Standalone
Entries in Alarm Action Queue
Key for First Playback File
Key of first Post Trip Log File
Number of files reserved for PTL
Key of first Historical File
Key of first Historical Retrieved File
Key of first Historical GhostFile
Number of Historical Retrived Files
Operator Station Layout
Operator Station Display
Alarm Mimic
ODBC Interface
ODBC Tag History
Rundown Not In Progress
Entries in Data Input Processor Queueu
Entries in ODBC queue
Status of the ICI
Text Selector
Tagset
Alarm Comment
National language
User Application Parameter 1
User Application Parameter 2
User Application Parameter 3
User Application Parameter 4
User Application Parameter 5
User Application Parameter 6
9AKK101130D1382
9AKK101130D1382
Description
User Application Parameter 7
User Application Parameter 8
Playback Saved for Long Term
Playback Compression Horizontal DeadBand
Playback Compression Slope Band
Time Zoner
Ignore Alarms belonging to Group Zero
Number of Nodes in Network
Timeout for Popups
Popups with Black Background
Trigger for requesting Reports
Use tag UID in Network messages
Entries in Network queue
Popu to be selected to enable commands
Trigger for Reloading Calculations
Security Group
Security Level
Security Privileges
Nodes Connection Count
Enable Pinting of Event Messages
Enable STD time format for alarms
Acknowledgement fo Control is Required
Rate for Control Increment
Entriesd in OPC queue
General Diagnostic Status
NetWorker Status
OPC Client Status
OPC Server Status
Trigger for Reloading the Data Input Processor
Trigger for Reloading OPC
Trigger for Reloading History
Trigger for Reloading People Finder
487
488
Description
Code of Alarm Audible
File for Alarm Audible
Character for Atom Sepatation
People Finder is Enabld
People Finder Error logging is Active
People Finder Error logging is Enabled
People Finder Acknowlege All Alarms
People Finder Acknowlege Alarms
Tag Builder is in Progress
Trigger for Reloading the Scanner
Simulation State
Simulation Reate
Apms Parameter
Apms Parameter
Apms Parameter
OPC AE Refresh
File Info
File Version
Disable Auto-Switch from Master to Slave
Tag for Local-Remote Control
Trigger for Reloading V23 logic
Recalculate Voting 2 of 3
Number of Output Drivers
Data Input Process is Frozen
Playback Switch
9AKK101130D1382
9AKK101130D1382
Description
Index
Name
Description
Internal Tag Index
Tag Type
Tag Type Description
Tag Source
Current Value
Current Raw Value
Numeric Value
Numeric Unsigned Value
Percent Value
Current Quality
Time Stamp
Time Stamp Text
Time Stamp
Current Value and Quality
Current Value and Quality
Current Quality
Current Value and Quality
Current Value and Quality
Timestamp
Timestamp (string)
Plant Tag Name
Current Alarm Priority
Alarm Processing Categorized
Alarm Group
Engineering Unit
EU Index
Decimal Places
489
490
Description
Integer Format
Foreground Color
Background Color
Foreground Color Ref.
Background Color Ref.
Foreground Color String
Background Color String
RTN Comment
Hi Alarm Comment
Lo Alarm Comment
2-Hi Alarm Comment
2-Lo Alarm Comment
3-Hi Alarm Comment
3-Lo Alarm Comment
Hi Deviation Comment
Lo Deviation Comment
Hi ROC Alarm Comment
Lo ROC Alarm Comment
Event Comment
Channel Failure Comment
Primary Display
Primary Trend Group
Security Level
Security Group
Alarm Action Program
Activate on Ack
Activate on RTN
Activate on Alarm
Activate on Event
Activate on HI
Activate on H3-H2
Activate on H
9AKK101130D1382
9AKK101130D1382
Description
Activate on L
Activate on L3-L2
Activate on LI
Activate on PROC
Activate on NROC
Remote Alarm Processing
Triggered Calculation
ICI Number
ICI Index
Ring
Pcu
Module
Block
SER Number
SER Index
ICI Action Code
Audible Alarm Index
OIS Alarm Proc.
Display Alarms
Print Alarms
Save Alarms
Activate Audible
Audible on RTNs
Bottom of Screen
Display RTNs
Print RTNs
Save RTNs
Display Events
Print Events
Save Events
Print Actions
Save Actions
491
492
Description
Print Infos
Save Infos
Remove on Ack
Info on Ack
Do not set Unack
Display Mimic when alarm
Broadcast Ack to the field
Trigger Application Event
Export Alarms to Foreign DB
Export Alarms to OPC Server
SMS index for Alarms
Alarm Inhibit Tag
Control Inhibit Tag
Need Confirm Command
Control Commad Tag
Hi Variable Alarm Tag
2-Hi Variable Alarm Tag
3-Hi Variable Alarm Tag
Lo Variable Alarm Tag
2-Lo Variable Alarm Tag
3-Lo Variable Alarm Tag
Control Inhibit
Remote Control Inhibit
Local Control Inhibit
Slave Module Coordinates
Slave Module Type
Termination Unit Type
Termination Unit Identifier
Termination Unit Coordinates
S-Slave Module
S-Slave Channel
Field Cabinet Identifier
9AKK101130D1382
9AKK101130D1382
Description
Slave Module
Slave Channel
Off Scan Initially
Off Alarm Check Initially
Initial Value
0% Presentation Scale
100% Presentation Scale
Violation Code
Off Scan on Violation
Text (10 characters)
Text (16 characters)
Text (32 characters)
Integer 1
Integer 2
Integer 3
Integer 4
Real 1
Real 2
Real 3
Real 4
Real 5
Real 6
High Instrument Limit
Low Instrument Limit
Low Alarm Limit
2-Low Alarm Limit
3-Low Alarm Limit
High Alarm Limit
2-High Alarm Limit
3-High Alarm Limit
Increasing Rate Of Change
Decreasing Rate Of Change
493
494
Description
3-Hi Variable Alarm Delta
2-Hi Variable Alarm Delta
2-Lo Variable Alarm Delta
3-Lo Variable Alarm Delta
Span
H-Limit Active
H2-Limit Active
H3-Limit Active
L-Limit Active
L2-Limit Active
L3-Limit Active
HR Active
LR Active
LI Active
HI Active
Alarm Deadband
Alarm Deadband (percent)
Event Tag
State is Alarm
State is Alarm
State is Alarm
State is Alarm
State is Alarm
State is Alarm
State is Alarm
State is Alarm
State is Alarm
State is Alarm
State is Alarm
State is Alarm
State is Alarm
State is Alarm
9AKK101130D1382
9AKK101130D1382
Description
State is Alarm
State is Alarm
State is Alarm
State is Alarm
State is Alarm
State is Alarm
State is Alarm
State is Alarm
State is Alarm
State is Alarm
State is Alarm
State is Alarm
State is Alarm
State is Alarm
State is Alarm
State is Alarm
State is Alarm
State is Alarm
Alarm BitMask
Maximum Rate of Change
Dest. node mask for alarm ack
Source node mask
Dest. node mask for values
Dest. node mask for config
Totalization Log
Trip Log
Report Number
Totalizer 1 min.
Totalizer 10 min.
Totalizer 30 min.
Totalizer 1 hour
Totalizer 8 hour
495
496
Description
Totalizer 1 day
Totalizer 1 month
Totalizer 1 year
Totalized 1 min.
Totalized 10 min.
Totalized 30 min.
Totalized 1 hour
Totalized 8 hour
Totalized 1 day
Totalized 1 month
Totalized 1 year.
Totalized number of start
Totalized number of stop
Totalized running time
Totalized time from last reset
Totalized stop time
Totalized BAD quality time
Totalized system shutdown time
Playback Compression
Long Term Playback Archive
Playback Archive
Export Values to Foreign DB
Export Values to File
State 0
State 1
State 2
State 3
State 4
State 5
State 6
State 7
State 8
9AKK101130D1382
9AKK101130D1382
Description
State 9
State 10
State 11
State 12
State 13
State 14
State 15
Feedback 1 State 0
Feedback 1 State 1
Feedback 2 State 0
Feedback 2 State 1
Feedback 3 State 0
Feedback 3 State 1
Feedback 4 State 0
Feedback 4 State 1
Set Point index
Control Point Index
Ratio Index
Station Status Index
Hourly Constancy Delta
Increment/decrement %
Fast Inc./dec. %
Playback Deadband
Playback Timer
Alarm Active Mask
Alarm Inhibition Chain
Control Type
Last Data Base Update
Tag Defined
Alarm Group Level
Alarm Group With Subgroups
Alarm Group Summary
497
498
Description
Local Host
Node Weight
Current Decoded Quality
Alarm Color Attributes
Current Alarm Comment
Any Alarm Comment
Plant Unit
Plant Unit Name
Alarm ack broad. node list
OPC Server visibility
Alarm printer number
Tag global UID
Tag global UID (formatted)
Triggered SOE number
Triggered SOE type
Plb compr. span (%)
Device Type
Device Number
Device Name
Module Type
Module Rev.
Output Transfer Tag Index
Output Transfer Enabled
Operating Parameter
OPC Program ID
OPC Computer name
OPC Item ID
OPC Access path
OPC Refresh time
OPC Read type
Export to Client OPC
Export to Server OPC
9AKK101130D1382
9AKK101130D1382
Description
OPC Alarm Source
Extended Description
Maintenance Trigger
Field Address 1
Field Address 2
Field Address 3
Field Address 4
Field Address 5
Field Address 6
Field Address 7
Field Address 8
Field Address 9
Field Address 10
Field Driver Name
Field Drv Text 1
Field Drv Text 2
Field Drv Text 3
Field Drv Text 4
Field Drv Text 5
Field Drv Text 6
Field Drv Text 7
Field Drv Text 8
Field Drv Text 9
Field Drv Text 10
Driver Index 1
Driver Index 2
Driver Index 3
Driver Index 4
Driver Index 5
Driver Input Index
Data Processor Name
Output Address 1
499
500
Description
Output Address 2
Output Address 3
Output Address 4
Output Address 5
Output Address 6
Output Address 7
Output Address 8
Output Address 9
Output Address 10
Output Driver Name
Output Drv Text 1
Output Drv 1 Text 2
Output Drv 1 Text 3
Output Drv 1 Text 4
Output Drv 1 Text 5
Output Drv 1 Text 6
Output Drv 1 Text 7
Output Drv 1 Text 8
Output Drv 1 Text 9
Output Drv 1 Text 10
Output 1 Address 1
Output 1 Address 2
Output 1 Address 3
Output 1 Address 4
Output 1 Address 5
Output 1 Address 6
Output 1 Address 7
Output 1 Address 8
Output 1 Address 9
Output 1 Address 10
Output Driver Name
Output 2 Drv Text 1
9AKK101130D1382
9AKK101130D1382
Description
Output 2 Drv Text 2
Output 2 Drv Text 3
Output 2 Drv Text 4
Output 2 Drv Text 5
Output 2 Drv Text 6
Output 2 Drv Text 7
Output 2 Drv Text 8
Output 2 Drv Text 9
Output 2 Drv Text 10
Generator Tag
Component Tag
Faceplate
Feedback 1
Feedback 2
Feedback 3
Feedback 4
Auto/Manual
Good State
Requested State
Red Tag
Permissive 1
Permissive 2
Name of Aspect #1
Command for Aspect #1
Name of Aspect #2
Command for Aspect #2
Name of Aspect #3
Command for Aspect #3
Name of Aspect #4
Command for Aspect #4
Name of Aspect #5
Command for Aspect #5
501
502
Description
Number of Atoms
Name for Atom #1
Value for Atom #1
Name for Atom #2
Value for Atom #2
Name for Atom #3
Value for Atom #3
Name for Atom #4
Value for Atom #4
Name for Atom #5
Value for Atom #5
Name for Atom #6
Value for Atom #6
Name for Atom #7
Value for Atom #7
Name for Atom #8
Value for Atom #8
Name for Atom #9
Value for Atom #9
Name for Atom #10
Value for Atom #10
Name for Atom #11
Value for Atom #11
Name for Atom #12
Value for Atom #12
Name for Atom #13
Value for Atom #13
Name for Atom #14
Value for Atom #14
Name for Atom #15
Value for Atom #15
Name for Atom #16
9AKK101130D1382
9AKK101130D1382
Description
Value for Atom #16
Name for Atom #17
Value for Atom #17
Name for Atom #18
Value for Atom #18
Name for Atom #19
Value for Atom #19
Name for Atom #20
Value for Atom #20
Name for Atom #21
Value for Atom #21
Name for Atom #22
Value for Atom #22
Name for Atom #23
Value for Atom #23
Name for Atom #24
Value for Atom #24
Name for Atom #25
Value for Atom #25
Name for Atom #26
Value for Atom #26
Name for Atom #27
Value for Atom #27
Name for Atom #28
Value for Atom #28
Name for Atom #29
Value for Atom #29
Name for Atom #30
Value for Atom #30
Name for Atom #31
Value for Atom #31
Name for Atom #32
503
504
Description
Value for Atom #32
Name for Atom #33
Value for Atom #33
Name for Atom #34
Value for Atom #34
Name for Atom #35
Value for Atom #35
Name for Atom #36
Value for Atom #36
Name for Atom #37
Value for Atom #37
Name for Atom #38
Value for Atom #38
Name for Atom #39
Value for Atom #39
Name for Atom #40
Value for Atom #40
Name for Atom #41
Value for Atom #41
Name for Atom #42
Value for Atom #42
Name for Atom #43
Value for Atom #43
Name for Atom #44
Value for Atom #44
Name for Atom #45
Value for Atom #45
Name for Atom #46
Value for Atom #46
Name for Atom #47
Value for Atom #47
Name for Atom #48
9AKK101130D1382
9AKK101130D1382
Description
Value for Atom #48
Name for Atom #49
Value for Atom #49
Name for Atom #50
Value for Atom #50
Name for Atom #51
Value for Atom #51
Name for Atom #52
Value for Atom #52
Name for Atom #53
Value for Atom #53
Name for Atom #54
Value for Atom #54
Name for Atom #55
Value for Atom #55
Name for Atom #56
Value for Atom #56
Name for Atom #57
Value for Atom #57
Name for Atom #58
Value for Atom #58
Name for Atom #59
Value for Atom #59
Name for Atom #60
Value for Atom #60
Name for Atom #61
Value for Atom #61
Name for Atom #62
Value for Atom #62
Name for Atom #63
Value for Atom #63
Name for Atom #64
505
506
Description
Value for Atom #64
Name for Atom #65
Value for Atom #65
Name for Atom #66
Value for Atom #66
Name for Atom #67
Value for Atom #67
Name for Atom #68
Value for Atom #68
Name for Atom #69
Value for Atom #69
Name for Atom #70
Value for Atom #70
Name for Atom #71
Value for Atom #71
Name for Atom #72
Value for Atom #72
Name for Atom #73
Value for Atom #73
Name for Atom #74
Value for Atom #74
Name for Atom #75
Value for Atom #75
Name for Atom #76
Value for Atom #76
Name for Atom #77
Value for Atom #77
Name for Atom #78
Value for Atom #78
Name for Atom #79
Value for Atom #79
Name for Atom #80
9AKK101130D1382
9AKK101130D1382
Description
Value for Atom #80
Name for Atom #81
Value for Atom #81
Name for Atom #82
Value for Atom #82
Name for Atom #83
Value for Atom #83
Name for Atom #84
Value for Atom #84
Name for Atom #85
Value for Atom #85
Name for Atom #86
Value for Atom #86
Name for Atom #87
Value for Atom #87
Name for Atom #88
Value for Atom #88
Name for Atom #89
Value for Atom #89
Name for Atom #90
Value for Atom #90
Name for Atom #91
Value for Atom #91
Name for Atom #92
Value for Atom #92
Name for Atom #93
Value for Atom #93
Name for Atom #94
Value for Atom #94
Name for Atom #95
Value for Atom #95
Name for Atom #96
507
508
Description
Value for Atom #96
Name for Atom #97
Value for Atom #97
Name for Atom #98
Value for Atom #98
Name for Atom #99
Value for Atom #99
Name for Atom #100
Value for Atom #100
Type of Atom #1
Type of Atom #2
Type of Atom #3
Type of Atom #4
Type of Atom #5
Type of Atom #6
Type of Atom #7
Type of Atom #8
Type of Atom #9
Type of Atom #10
Type of Atom #11
Type of Atom #12
Type of Atom #13
Type of Atom #14
Type of Atom #15
Type of Atom #16
Type of Atom #17
Type of Atom #18
Type of Atom #19
Type of Atom #20
Type of Atom #21
Type of Atom #22
Type of Atom #23
9AKK101130D1382
9AKK101130D1382
Description
Type of Atom #24
Type of Atom #25
Type of Atom #26
Type of Atom #27
Type of Atom #28
Type of Atom #29
Type of Atom #30
Type of Atom #31
Type of Atom #32
Type of Atom #33
Type of Atom #34
Type of Atom #35
Type of Atom #36
Type of Atom #37
Type of Atom #38
Type of Atom #39
Type of Atom #40
Type of Atom #41
Type of Atom #42
Type of Atom #43
Type of Atom #44
Type of Atom #45
Type of Atom #46
Type of Atom #47
Type of Atom #48
Type of Atom #49
Type of Atom #50
Type of Atom #51
Type of Atom #52
Type of Atom #53
Type of Atom #54
Type of Atom #55
509
510
Description
Type of Atom #56
Type of Atom #57
Type of Atom #58
Type of Atom #59
Type of Atom #60
Type of Atom #61
Type of Atom #62
Type of Atom #63
Type of Atom #64
Type of Atom #65
Type of Atom #66
Type of Atom #67
Type of Atom #68
Type of Atom #69
Type of Atom #70
Type of Atom #71
Type of Atom #72
Type of Atom #73
Type of Atom #74
Type of Atom #75
Type of Atom #76
Type of Atom #77
Type of Atom #78
Type of Atom #79
Type of Atom #80
Type of Atom #81
Type of Atom #82
Type of Atom #83
Type of Atom #84
Type of Atom #85
Type of Atom #86
Type of Atom #87
9AKK101130D1382
9AKK101130D1382
Description
Type of Atom #88
Type of Atom #89
Type of Atom #90
Type of Atom #91
Type of Atom #92
Type of Atom #93
Type of Atom #94
Type of Atom #95
Type of Atom #96
Type of Atom #97
Type of Atom #98
Type of Atom #99
Type of Atom #100
Description for Atom #1
Description for Atom #2
Description for Atom #3
Description for Atom #4
Description for Atom #5
Description for Atom #6
Description for Atom #7
Description for Atom #8
Description for Atom #9
Description for Atom #10
Description for Atom #11
Description for Atom #12
Description for Atom #13
Description for Atom #14
Description for Atom #15
Description for Atom #16
Description for Atom #17
Description for Atom #18
Description for Atom #19
511
512
Description
Description for Atom #20
Description for Atom #21
Description for Atom #22
Description for Atom #23
Description for Atom #24
Description for Atom #25
Description for Atom #26
Description for Atom #27
Description for Atom #28
Description for Atom #29
Description for Atom #30
Description for Atom #31
Description for Atom #32
Description for Atom #33
Description for Atom #34
Description for Atom #35
Description for Atom #36
Description for Atom #37
Description for Atom #38
Description for Atom #39
Description for Atom #40
Description for Atom #41
Description for Atom #42
Description for Atom #43
Description for Atom #44
Description for Atom #45
Description for Atom #46
Description for Atom #47
Description for Atom #48
Description for Atom #49
Description for Atom #50
Description for Atom #51
9AKK101130D1382
9AKK101130D1382
Description
Description for Atom #52
Description for Atom #53
Description for Atom #54
Description for Atom #55
Description for Atom #56
Description for Atom #57
Description for Atom #58
Description for Atom #59
Description for Atom #60
Description for Atom #61
Description for Atom #62
Description for Atom #63
Description for Atom #64
Description for Atom #65
Description for Atom #66
Description for Atom #67
Description for Atom #68
Description for Atom #69
Description for Atom #70
Description for Atom #71
Description for Atom #72
Description for Atom #73
Description for Atom #74
Description for Atom #75
Description for Atom #76
Description for Atom #77
Description for Atom #78
Description for Atom #79
Description for Atom #80
Description for Atom #81
Description for Atom #82
Description for Atom #83
513
514
Description
Description for Atom #84
Description for Atom #85
Description for Atom #86
Description for Atom #87
Description for Atom #88
Description for Atom #89
Description for Atom #90
Description for Atom #91
Description for Atom #92
Description for Atom #93
Description for Atom #94
Description for Atom #95
Description for Atom #96
Description for Atom #97
Description for Atom #98
Description for Atom #99
Description for Atom #100
Quality Status: APP2
Quality Status: APP1
Quality Status: HCFV
Quality Status: RTAG
Quality Status: APP3
Quality Status: BAD
Quality Status: B9
Quality Status: ALIA
Quality Status: ALIN
Quality Status: INSV
Quality Status: EVT
Quality Status: OFSC
Quality Status: OLDD
Quality Status: ALRM
Quality Status: UNAK
9AKK101130D1382
9AKK101130D1382
Description
Quality Status: IMP
Quality Status: DUMM
Quality Status: AM
Quality Status: SLAV
Quality Status: SHAV
Quality Status: TRAK
Quality Status: I4
Quality Status: LDEV
Quality Status: HDEV
Quality Status: DROC
Quality Status: IROC
Quality Status: LIRV
Quality Status: LLAV
Quality Status: LAV
Quality Status: HAV
Quality Status: HHAV
Quality Status: HIRV
Conversion Code
Conversion Code String
Conversion Min
Conversion Max
Conversion Offset
RTN Alarm Comment
High Alarm Comment
Low Alarm Comment
2-high Alarm Comment
2-low Alarm Comment
3-high Alarm Comment
3-low Alarm Comment
H dev Alarm Comment
L dev Alarm Comment
H roc Alarm Comment
515
516
Description
L roc Alarm Comment
Status Chg Alarm Comment
HCF Alarm Comment
Default Alarm Priority
Alarm Priority: RTN
Alarm Priority: H
Alarm Priority: L
Alarm Priority: 2H
Alarm Priority: 2L
Alarm Priority: 3H
Alarm Priority: 3L
Alarm Priority: HDEV
Alarm Priority: LDEV
Alarm Priority: HROC
Alarm Priority: LROC
Alarm Priority: STCH
Alarm Priority: BAD
Node mask for snap align.
Node mask for cnf align
Node mask for OJ align
Node mask for plb align
Node mask for hist align
Archive Type
Time Span
Archive Hist. Type
Archive Frequency
Archive Offset
Sample Frequency
Display Frequency
Derived Group
Input Group
# of Tags
9AKK101130D1382
9AKK101130D1382
Description
# of Archive Samples
Pre-trip Time
Post-trip Time
Archive End Time
Archive Start Time
Group Class
Close trip on return
Curve Type
Initial Presentation Mode
Trend Frame Color
Trend Border Color
Trend Grid Color
Trend Text Color
Trend Draw Mode
Trend List Mode
Trend List Mode
Report file name
Group viewer program
User Password Expired
User Password Aging
User Language
User Login Display
User Login Program
User Logout Display
User Logout Program
User Payroll Code
User Password Changed
User Active
Mask of user allowed CRT
Reserved for Command by User
This node is Local source for the tag
Row Count for Alarm retrieval
517
Gas
Hydrogen
Carbon monoxide
Methane
Acetylene (Ethyne)
Ethylene
Ethane
Propane
N-Butane
Iso-Butane
N-Pentane
Neohexane
Hydrogen sulfide
Carbon dioxide
Oxygen
Water
Sulfur dioxide
Nitrogen
Argon
Air
Chemical Formula
H2
CO
CH4
C2H2
C2H4
C2H6
C3H8
C4H10-N
C4H10-I
C5H12-N
C6H14
H2S
CO2
O2
H2O
SO2
N2
Ar
Air
Molecular Weight
2.016
28.010
16.043
26.038
28.054
30.070
44.097
58.124
58.124
72.151
86.178
34.080
44.010
31.999
18.015
64.063
28.016
39.948
28.959
518
Code
1
2
3
4
5
Description
Analog tag.
Digital tag.
Multi State Device Driver.
Calculation.
Trend group.
9AKK101130D1382
9AKK101130D1382
Code
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
29
Description
Retrieved trend group.
Node (network server).
Device.
Logic state descriptor.
Engineering unit.
Alarm comment.
Text selector.
Alarm summary group.
Generic alarm.
Pegboard.
Display.
Report.
Audible alarm.
Security (user and authorization).
Menu and tool-bar.
Application specific item.
519
Database
Audible tones database and alarm grouping database.
Calculation database.
Tag related databases (Engineering Units, Logic State Descriptors, Alarm
Comments, Text Selectors).
Trend group database.
Menu and tool-bar database.
Node database.
Security database.
Pegboard database.
Report database.
Tag database.
Export to foreign database.
Field Types
Table 165. Field Types.
Type
DT_CHAR
DT_VARCHAR
DT_LONGVARCHAR
DT_BIT
DT_TINYINT
DT_SMALLINT
DT_INTEGER
DT_BIGINT
DT_DECIMAL
DT_NUMERIC
DT_REAL
DT_DOUBLE
520
Code
1
2
3
4
5
6
7
8
9
10
11
12
9AKK101130D1382
9AKK101130D1382
Code
13
14
15
16
17
18
19
521
Alarm Types
Table 166. Alarm Types.
Code
1
2
3
4
5
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
40
41
42
43
44
522
Symbol
ALEINF
ALERTN
ALEOPE
ALEACK
ALEEVT
ALEDIA
ALEHIR
ALELIR
ALESHA
ALESLA
ALEHHA
ALELLA
ALEHAL
ALELAL
ALERCP
ALERCN
ALEHDV
ALELDV
ALEHCF
ALEALA
ALEVOT
ALEMUL
ALERTM
ALEOPR
ALELST
Description
Information event.
Return to normal.
Operator action.
Alarm acknowledge event.
Digital status event.
Digital alarm.
High instrument alarm.
Low instrument alarm.
3-high alarm.
3-low alarm.
2-high alarm.
2-low alarm.
High alarm.
Low alarm.
Increasing rate of change alarm
Decreasing rate of change alarm
High deviation alarm.
Low deviation alarm.
Hardware channel failure.
Generic alarm.
Voting alarm (reserved).
9AKK101130D1382
Symbol
A_NAME
A_DESC
A_INDX
A_CUST
A_GROU
A_PRIO
A_EU
A_CMNT
A_ITMT
A_ITMN
A_VAL
A_VALQ
A_STAT
A_STAQ
A_TIME
A_DATE
A_DATI
A_HTIM
A_HDAT
A_HDTI
A_OPER
A_CANC
A_ASCI
A_REAL
A_LONG
A_INTE
A_HEXL
A_HEXA
A_YENO
A_TUTS
9AKK101130D1382
Description
Tag name
Tag description
Tag index
Customer tag id (plant tag name)
Alarm group
Alarm priority
EU descriptor
Alarm comment (buffer, 2W value + 2W quality)
Item type
Item number
Value (buffer, 2W value + 2W quality)
Value and quality (buffer, 2W value + 2W quality)
Status (buffer, 2W value + 2W quality)
Status and quality (buffer, 2W value + 2W quality)
Time
Date
Date and Time
Historical time (buffer, 2W)
Historical date (buffer, 2W)
Historical date and time (buffer, 2W)
Operator name (buffer, 1W)
Cancode parameter (buffer, n/3 W)
Ascii parameter (buffer, n/2 W)
Real parameter (buffer, 2W)
Long integer parameter (buffer, 2W)
Short integer parameter (buffer, 1W)
Long integer (hex) parameter (buffer, 2W)
Short integer (hex) parameter (buffer, 1W)
Yes (1) / Not (0) (buffer, 1W)
Timer units (buffer, 1W)
523
524
Symbol
A_NREF
A_EDSC
A_NODE
A_QUAL
A_PROD
A_SKVL
A_BKVL
A_DBXF
A_UTX1
A_UTX2
A_UTX3
A_UTX4
A_UTX5
A_CHAR
Description
Item number referenced (buffer, 4W)
Extended description
Local node name
Tag quality
Product name
Skip value
Backward Skip value
Data Base Reference
Text from OPC AE (1)
Text from OPC AE (2)
Text from OPC AE (3)
Text from OPC AE (4)
Text from OPC AE (5)
Plain ASCII text (non UNICODE Compliant)
9AKK101130D1382
9AKK101130D1382
525
Item
MACRO
name
separator
mainatom
type
ATOM
name
descr
type
526
Description
Identifies the section of the xml file to specify the object
type (including the list of the atoms of the type)
Name of the type specified in the DataProcessor field in
the data base of the tag (for example
AC450.Block.XmlFileName.CFG)
Character separator of the OPC items
Used to identify the name of the atom that will be used by
PGP as main
Tagtype used in the PGP database. Accepted values:
DIGITAL, ANALOG, INTEGER
Identifies the section to specify the name and the
attributes of the atoms in the macro
Atom name
Atom description
Canonical OPC item type (like distribuited by OPC
server) Accepted values: BOOL, INTEGER, DINT, REAL,
STRn (where n is the number of characters in the string)
9AKK101130D1382
Functionalities
The PLC File Builder is an application (the process name is
PlcFileBuilder.exe located in the PGP\Bin folder) that operates using the
following three main steps:
9AKK101130D1382
527
PARSING.
It parses the specified PLC File first, listing all the OPC gateway stations
found (See the AC800F manuals for information about gateway station
definition).
CREATE DB.
After parsing, a temporary database is created that corresponds to the
selected OPC gateway.
The database name is created from the gateway name with the suffix
_tmp.
For example, if the gateway name is OPC1, then the database name
will be OPC1_tmp.dbf.
BUILDING.
After database creation, the database is imported in to the PGP system.
There is no need to close the database before importing.
The PGP PLC File Builder temporarily stores some needed information in an
XML format. It also uses some additional information permanantly stored in
the same format.
The PLC File Builder creates (and optionally removes) the temporary
database (.dbf extension) file and locates it in the usual PGP\Config\Tag
folder.
Be sure that a your own database file named <Gateway name>_tmp.dbf
does not already exist in the folder. If it does, then the PLC File Builder
will overwrite the existing file without checking. Any previously stored
information will be lost.
If a large amount of information is retrieved during parsing, the Builder can
store the information in more than one XML file. This reduces the size of
528
9AKK101130D1382
each XML file, which can improve performance during the processing of
these files. This feature is only available for one checked OPC gateway.
The Builder stores and uses some informations stored in the following XML
format files:
FreelanceTemplate.xml
DBHeader.xml
Correspondences.xml
9AKK101130D1382
529
530
9AKK101130D1382
9AKK101130D1382
531
532
9AKK101130D1382
9AKK101130D1382
533
534
9AKK101130D1382
In this example, two opc gateways have been defined in the opened plc file
and, for some reason, the IP addresses have not been resolved
successfully with the corresponding host names.
9AKK101130D1382
535
536
9AKK101130D1382
3 select areas you want to be excluded. In this way all the CBF tags
referring to those areas will not be imported in the database. These settings
work as a filter option during plc file browsing. As an example, we have
9AKK101130D1382
537
Note:
1.you are able to set a computer name (and the "Alias.xml" file will be
updated accordingly) and such name will be retrieved later by the opc client
and used for connection to server.
2.you can set the initial tag index for each gateway but the PlcFileBuilder
does not make any check or notification about common indexes among
different temporary databases. In the example above, let's suppose 1500
tags be defined for both the gateways. If the initial tag index has been set to
1000 and to 2000 for gateways "OPC1" and "OPC2" respectively, the
indexes range in "OPC1_tmp.dbf" will be [1000,2500] and in
"OPC2_tmp.dbf" will be [2000,3500]. This means that indexes from 2000 to
2500 will result common to both databases and you must take care yourself
538
9AKK101130D1382
about the appropriate initial index value to set in order to avoid having
common indexes.
3.The "Tagindex" column is included in the temporary database. If you don't
set any initial index, all indexes will be set to "0" the first time (CBF tags not
imported yet in PGP). After importing, the index value will be retrieved
directly from PGP (for all the tags already imported in PGP).
9AKK101130D1382
539
540
9AKK101130D1382
The Builder will go back to the initial condition, as if it were started the first
time, ready to open another PLC file.
Click the Build button to display the Builder interface window as shown
below.
9AKK101130D1382
541
Then, after building, the Builder scans the PGP internal database and
checks if each AC800F tag in the PGP database is going to be re-built.
If a AC800F tag in the PGP database is not managed by the PLC File
Builder, such a tag is considered unused. That means, it is no longer in the
AC800F Configuration Project, but it is still configured in the PGP database.
Such a tag can manually be removed from the PGP database. It is NOT
automatically removed.
In order to find out the "Unused Tags", in the PGP database, the
PlcFileBuilder application "marks" optionally these tags by adding a "?"
character at the end of the string stored in the "User3" PGP database field.
This is done after the optional UnBuild operation and therefore the updated
field doesn't appear in the current exported database
(TAGS_19_06_2001_12_09.dbf in the above example).
The Builder displays all such unused tags in the Messages window at
runtime. See the Messages window and Log File sections for further
explanations about.
542
9AKK101130D1382
You can keep the temporary database files by clearing the Remove
Temporary databases option.
Figure 49.
The Remove Temporary databases option is selected by default. With this
option any older temporary files will be overwritten by new files.
Eventually, the PGP Tag Description database field can be optionally
updated by the PlcFileBuilder, by using the correspondent AC800F tag
description (this is done by checking the optional checkbox). Otherwise, the
original PGP tag description will result unchanged.
9AKK101130D1382
543
Messages window
All the messages are trace/debug messages and/or error messages. Among
the other, the following messages could be found.
Tag IDF_1 successfully managed (# tags managed: 170)
This message is displayed for each AC800F Tag (or Variable) successfully
managed by the PLC File Builder during the creation of the
FreelanceTemplate.xml file. Such tag will be later included in the temporary
database and then imported within the PGP database. In the message
example, related to the tag IDF_1, a total of 170 tags have been
successfully managed.
*** Error: Tag "C_ANA" NOT MANAGED ! (# 4)
This message is displayed for each AC800F Tag (or Variable) NOT
successfully managed by the PLC File Builder during the creation of the
FreelanceTemplate.xml file. Such tag will NOT be later included in the
temporary database and, consequently, it will NOT be imported within the
PGP database. In the message example, related to the tag C_ANA, a total
of 4 tags have been discharged.
Variable PStx.ProjectName: type STRING[16] not imported
This message is displayed only for AC800F variable types that PGP is not
able to manage. Such variable will be ignored.
Found PGP unused tag : ANALOG1
This message is displayed for each PGP tag (AC800F tag and/or variable)
still configured in the PGP database but no longer configured in the parsed
PLC File. Such tags can be manually removed. In the message example,
ANALOG1 is the name of the tag (i.e. the value of the TAGNAME field in
the PGP database).
544
9AKK101130D1382
Log file
The PLC File Builder displays a few messages in the Messages window
during execution. All these messages are also logged in the
PlcParserLog.txt file located in the \PGP\Logs folder.
9AKK101130D1382
545
folder, the new PGPfield (e.g. CUSTTAGID) must be added to the template
file.
In the Correspondences.xml file, a AC800F parameter cannot be
associated to multiple PGP fields.
AC800F Requirements
As described above, the client PGP retrieves data from the AC800F server
via OPC only.
The FreelanceAC800F software tools need to configure a gateway station
(GS) for each defined AC800F OPC Server. Since a GS can be of different
types, it must be defined as an OPC gateway (such gateways are the only
ones the PGP PLC File Builder must manage to get OPC data).
The PLC file doesnt have any information about the gateway type; therefore
the AC800F OPC gateway names MUST contain the OPC character
string. Valid OPC gateways names (no case-sensitive) are OPC1, Opc2,
OPCA, 1OPC, etc.
PGP Requirements
PGP needs the following DLLs.
PLCPARSER.DLL
Build # 1392, used to parse the PLC File for AC800F system version 6.1
FREELANCE.DLL
MSXML.DLL
The Microsoft XML parser version 2.5a, number 5.0.2919.6303, included
with Internet Explorer 5.0.1.
546
9AKK101130D1382
Alias.xml
The PlcFileBuilder creates the PGP database but hides both the opc
server's ProgID (both DA and AE) and the computer name by inserting in
the corresponding DB fields the same "alias" name and the key word
"MULTI_CMP" respectively. The mapping between the alias name and the
true ProgIDs (as well as the MULTI_CMP key word and the computer name)
is stored in the "Power Generation Portal\deck\alias.xml" file. Note that such
file is created automatically by the Builder, if missing.
The Builder opens the file and looks for the exact matching between both
the DA/AE ProgIDs being managed and the ones listed inside the file and
retrieves the stored alias name if search succeeds. If not, it updates the file
by choosing a default unique alias name ("Server1", "Server2" "ServerN",
depending on the alias names inside the file). See the example below:
9AKK101130D1382
547
548
9AKK101130D1382
The PGP opc client will be in charge of resolving such mapping on the basis
of the configured alias in the database. If "Server2" is defined, the opc client
will connect to "Freelance.30" DA/AE servers on the "PC2" machine.
The alias.xml file is also used to accomplish the PGP OPC Client
Redundancy by defining a list of computers instead of one only as in figure
above. Note that in order to set up redundancy, the configuration of the file
must be done manually. See the example below referring to the
"OPC.Iconics.1" DA server and the list of three different machines:Before
entering in details about the configuration above, it is important to highlight
that both the DA and AE ProgIDs are always common to the listed
computers, meaning that the same opc server and the same ProgID must
be installed on those machines. Therefore the configuration for client
redundancy cannot be applied in case of "Freelance" OPC Servers for
instance because the Freelance ProgID must be different on different
machines.
9AKK101130D1382
549
550
9AKK101130D1382
http://www.abb.com/powergeneration
ABB Power Systems
Via Hermada 6
16154 Genova - Italy
e-mail pgp.supportline@it.abb.com