Beruflich Dokumente
Kultur Dokumente
800xA - System
800xA for Harmony
System Version 4.1
Configuration
IndustrialIT
800xA - System
800xA for Harmony
System Version 4.1
Configuration
NOTICE
The information in this document is subject to change without notice and should not be
construed as a commitment by ABB. ABB assumes no responsibility for any errors that
may appear in this document.
In no event shall ABB be liable for direct, indirect, special, incidental or consequential
damages of any nature or kind arising from the use of this document, nor shall ABB be
liable for incidental or consequential damages arising from use of any software or hardware described in this document.
This document and parts thereof must not be reproduced or copied without written permission from ABB, and the contents thereof must not be imparted to a third party nor used
for any unauthorized purpose.
The software or hardware described in this document is furnished under a license and
may be used, copied, or disclosed only in accordance with the terms of such license.
This product meets the requirements specified in EMC Directive 89/336/EEC and in Low
Voltage Directive 72/23/EEC.
Copyright 2003-2005 by ABB.
All rights reserved.
Release:
Document number:
May 2005
3BUA000157R4101
TRADEMARKS
All rights to trademarks reside to their respective owners.
TABLE OF CONTENTS
About This Book
General ............................................................................................................................17
Use of Warning, Caution, Information, and Tip ..............................................................17
Document Conventions ...................................................................................................18
Terminology.....................................................................................................................19
Related Documentation ...................................................................................................20
Section 1 - Introduction
Overview .........................................................................................................................21
Intended User...................................................................................................................21
Functional Description ....................................................................................................21
Harmony OPC Server........................................................................................22
Configuration Overview.......................................................................................22
INFI 90 Harmony Objects....................................................................................22
Connectivity Server (RTDS) ................................................................................22
Tags
.............................................................................................................22
3BUA000157R4101
Table of Contents
3BUA000157R4101
Table of Contents
Tabs
.............................................................................................................47
Body
.............................................................................................................47
Footer
.............................................................................................................48
Life Cycle
......................................................................................48
Locked By
......................................................................................48
......................................................................................49
......................................................................................49
......................................................................................50
......................................................................................55
Advanced
......................................................................................56
Version Tab...........................................................................................................56
3BUA000157R4101
Table of Contents
...................................................................................... 62
3BUA000157R4101
Table of Contents
Section 6 - Tags
Introduction .....................................................................................................................67
Tag Types.........................................................................................................................67
Online Tag Configuration................................................................................................67
Harmony Tag Objects......................................................................................................71
Event Point Configuration ...............................................................................................72
Harmony Tab ...................................................................................................................72
Loop
......................................................................................73
Node
......................................................................................73
Module
......................................................................................74
Block
......................................................................................74
.............................................................................................................89
Cascade
.............................................................................................................90
Ratio
.............................................................................................................90
3BUA000157R4101
Table of Contents
.................................................................................... 104
Release
.................................................................................... 104
Design
.................................................................................... 104
.................................................................................... 108
Summary
.................................................................................... 108
Pre-fault
.................................................................................... 108
Post-fault
.................................................................................... 108
Snapshot
.................................................................................... 109
10
3BUA000157R4101
Table of Contents
....................................................................................116
....................................................................................117
....................................................................................118
Active
....................................................................................118
3BUA000157R4101
csum
....................................................................................125
date
....................................................................................125
dfs
....................................................................................125
hist
....................................................................................125
port
....................................................................................125
psum
....................................................................................126
rhis
....................................................................................126
status
....................................................................................126
11
Table of Contents
12
3BUA000157R4101
Table of Contents
...........................................................................................................160
Import
...........................................................................................................163
3BUA000157R4101
13
Table of Contents
14
3BUA000157R4101
Table of Contents
....................................................................................258
Bad
....................................................................................258
Suspended
....................................................................................258
INDEX
3BUA000157R4101
15
Table of Contents
16
3BUA000157R4101
Tip icon indicates advice on, for example, how to design your project or how to
use a certain function
3BUA000157R4101
17
Document Conventions
Although Warning hazards are related to personal injury, and Caution hazards are
associated with equipment or property damage, it should be understood that
operation of damaged equipment could, under certain operational conditions, result
in degraded process performance leading to personal injury or death. Therefore,
comply fully with all Warning and Caution notices.
Document Conventions
The following conventions are used for the presentation of material:
The words in names of screen elements (for example, the title in the title bar of
a window, the label for a field of a dialog box) are initially capitalized.
Capital letters are used for the name of a keyboard key if it is labeled on the
keyboard. For example, press the ENTER key.
Lowercase letters are used for the name of a keyboard key that is not labeled on
the keyboard. For example, the space bar, comma key, and so on.
Press CTRL+C indicates that you must hold down the CTRL key while
pressing the C key (to copy a selected object in this case).
Press ESC E C indicates that you press and release each key in sequence (to
copy a selected object in this case).
The names of push and toggle buttons are boldfaced. For example, click OK.
The names of menus and menu items are boldfaced. For example, the File
menu.
The Start menu name always refers to the Start menu on the Windows
Task Bar.
18
3BUA000157R4101
Terminology
You may be told to enter the string TIC132 in a field. The string is shown as
follows in the procedure:
TIC132
Variables are shown using lowercase letters.
sequence name
Terminology
The following is a list of terms associated with 800xA for Harmony that you should
be familiar with. The list contains terms and abbreviations that are unique to ABB
or have a usage or definition that is different from standard industry usage.
Term
Description
CO
Control Output.
DCS
DEW
FC
Function Code.
PV
Process Variable.
SER
SOE
Sequence of Events.
SP
Set Point.
TSP
3BUA000157R4101
19
Related Documentation
Related Documentation
The following table provides a list of documentation related to the 800xA for
Harmony Configuration instruction. Use these instructions to reference 800xA for
Harmony information.
Category
Title
Description
3BUA000158R4101
3BSEO24545R4101
3BSEO34678R4101
WBPEEUI240768??
WBPEEUI210504??
Miscellaneous
20
3BUA000157R4101
Section 1 Introduction
Overview
800xA for Harmony software allows connection to and control of Symphony
Harmony INFI 90 systems via the 800xA Systems Operator Workplace.
This instruction describes the configurations related to 800xA for Harmony specific
functions. 800xA for Harmony communicates with the INFI 90 control systems via
a Cnet-to-computer interface (INICI03, INICI12, or Harmony Network
Communications Coupler). Also, connectivity to Plantloop controlway via an
INPCI01 and INPCI02 is supported.
Intended User
This instruction is intended for use by personnel responsible for configuring 800xA
for Harmony to operate within the 800xA System. This instruction assumes the
configuration engineer or technician is familiar with Windows operating systems,
Microsoft Internet Explorer, and the installed control system.
Functional Description
800xA for Harmony is a distributed process management and control system. Using
a series of integrated Harmony control units, the system allows monitoring and
control of process variables such as flow rate, temperature, and pressure according
to a control configuration that the engineer or technician defines. A Harmony
control unit is a controller and its I/O devices connected for communication on
control network (Cnet).
800xA for Harmony operates in a Windows environment on personal computer
hardware. Using interactive process graphics, the operator can monitor and control
3BUA000157R4101
21
Section 1 Introduction
all Analog loops and Digital devices interfaced to the network via Harmony control
units.
800xA for Harmony also provides maintenance personnel with the capability to
globally monitor the operating status of any system component on the network, and
to diagnose component failures from any workstation.
Configuration Overview
This section discusses the following topics:
Object configuration.
Object management.
Tags
A Harmony tag is configured for each process point that is to be monitored by the
Harmony RTDS. A tag is required to perform control actions from a workstation
22
3BUA000157R4101
Section 1 Introduction
Tag Importer
running 800xA for Harmony software. Section 6, Tags describes the configuration
of the different Harmony tag types.
Tag Importer
The Tag Importer utility adds Harmony configuration data from offline
configuration tools such as Composer, WinTools (WLDG), and SLDG. Section 7,
Tag Importer describes the use of the Tag Importer.
Tag Exporter
The Tag Exporter utility sends Harmony configuration data to an offline
configuration tool such as Composer in an MDB format. Section 8, Tag Exporter
describes the use of the Tag Exporter.
SOE Reporting
SOE Reports allow monitoring of critical Digital points where the sequence of state
changes for points or groups of points must be exactly known. Section 9, SOE
Reporting describes the configuration of SOE Reports.
System Definition
System definition features such as security properties are defined in the system
definition object. Section 10, System Definition describes the system definition.
Configuration Tools
Explains operation of the export/import configuration tool and the bulk
configuration manager. Section 12, Configuration Tools describes the configuration
tools.
3BUA000157R4101
23
Section 1 Introduction
Signal Structure
A tag contains all information required to find a point in the process control
configuration (function block) and to establish communication between it and
Harmony. Appendix A, Signal Structure lists the Harmony tags with their signal
structures.
Quality Definition
The purpose of this appendix is to describe the tag.property qualities in 800xA for
Harmony. Appendix B, Quality Definition lists the Harmony tag property qualities
with definitions.
OCS Colors
The purpose of this appendix is to list all of the OCS color names, RGB value, and a
description of what they are. Appendix C, OCS Colors lists the defaults colors used
in faceplate and graphical elements.
24
3BUA000157R4101
Right-click the My ePlant icon on the desktop and select the Plant Explorer
Workplace.
2.
When the Plant Explorer Workplace area opens, open the Control Structure
from the drop-down list box as shown in Figure 1.
3.
4.
5.
6.
Select Harmony OPC Server Network from the list of objects (Figure 2).
7.
Enter a name.
8.
Click Next. The Additional Arguments dialog box will be displayed (Figure 3).
9.
Click the Add button. The Select Connectivity Server(s) dialog box will be
displayed.
3BUA000157R4101
25
Configuration
TC04575A
26
3BUA000157R4101
Configuration
TC04576A
3BUA000157R4101
27
Configuration
TC04577B
TC04578A
28
3BUA000157R4101
16. Select the domain that the Configuration Server is located in from the dropdown list box to the right of the Configuration Server Domain Name
(Figure 4). The rest of the information will fill in on its own.
For backup Connectivity Servers, verify that the primary Harmony Connectivity
Server name is selected in the Tag Server Name drop-down list box.
17. Click Apply.
18. In the Aspect list area, select Harmony Synchronizer. The Harmony
Synchronizer Aspect will be displayed. Refer to Harmony Synchronizer Aspect
on page 169 for more information.
19. Click the Synchronize button to synchronize the Configuration Server
Database with the Harmony OPC Server Network Object list.
Right-click the My ePlant icon on the desktop and select Plant Explorer
Workplace.
2.
When the Plant Explorer Workplace area opens, open the Control Structure
from the drop-down list box as shown in Figure 1.
3.
4.
5.
6.
7.
Click Create.
3BUA000157R4101
29
8.
From the Control Structure, right-click on the new Generic Object just created.
9.
TC04579A
30
3BUA000157R4101
TC04557A
3BUA000157R4101
31
TC04558B
32
3BUA000157R4101
37. From here, select Services > Server Aspect Controller, Service > SAC
Group, Service Group > SAC_Group_(machine name).
The machine name that is entered here is the name that was used in Step 18.
38. Right-click on SAC_Group_(machine name).
39. Select Service Provider Definition aspect.
40. Select the Configuration tab.
41. Uncheck the Enabled box.
42. Click Apply.
43. Recheck the Enabled box.
44. Click Apply.
45. Exit.
2.
3.
If they do not already exist, create the Service Group and Service Provider
Objects by right-clicking on EventCollector, Service and select New Object
from the context menu that appears.
4.
The New Object dialog appears. Select Service Group and enter a name, such
as Harmony_AE_SGx (where x is a running number) and click Create.
5.
Right-click on the newly created Service Group object and select New Object
from the context menu that appears.
3BUA000157R4101
33
6.
The New Object dialog appears. Select Service Provider and enter a name,
such as Harmony_AE_SP_nodename (where nodename is a Connectivity
Server name) and click Create.
7.
8.
9.
Select the name of the Harmony Connectivity Server in the Node drop-down
list box.
34
3BUA000157R4101
2.
3.
Assign the Security Settings for the Operating Parameters Aspect. Refer to
Security Settings for Operating Parameters on page 174 for more information.
4.
5.
Use the Configuration Wizard to assign users to the groups in the user structure
(Operator to Operators group).
3BUA000157R4101
35
36
3BUA000157R4101
Object configuration.
Object management.
3BUA000157R4101
37
Design.
Release.
Running.
Out of Service.
An object in the Design or Release Life Cycle is not effective in the system. These
Life Cycles are for configuration data being prepared for later use. Objects in the
Design or Release Life Cycle are offline versions.
An object in the Running Life Cycle is currently effective in the system. Objects in
the Running Life Cycle are online versions.
An object in the Out of Service Life Cycle was in the Running Life Cycle
previously, but has been overwritten by a newer object version. The user can
manually change to the Out of Service version if desired. The Out of Service
version can be used to go back to the previous Running version of the object if the
changes cause undesirable behavior.
38
3BUA000157R4101
reverse direction. This is a copy operation. In this case, multiple versions will exist
unless they are deleted. When an object is changed from run to Design, for example,
the run version remains intact and additionally there will be a Design version
created. Both exist at the same time.
3BUA000157R4101
39
Edit Mode
Edit Mode
An object must be locked for editing before any changes can be made. Only objects
in the Design Life Cycle can be edited. The correct access rights are required to edit
an object. The object cannot be locked by another user to edit.
To edit an object:
1.
2.
Verify that the object is in the Design Life Cycle and is not locked by another
user.
3.
Saving Changes
After changes have been made to an object they need to be submitted to the
Connectivity Server. During the submission they are also validated according to
their Life Cycle.
To save changes to the Connectivity Server:
1.
2.
3.
Click the submit changes button (). This also automatically clears the edit lock.
Canceling Changes
Click the cancel changes button () to cancel all changes made during an edit session.
This also automatically clears the edit lock.
Version Management
The highest version of an object is automatically increased by one when a new
version of the object is created. An object can have multiple versions in different
Life Cycles. For example, an INFI 90 Harmony Analog object can have instances in
Design, Release, Running, and Out of Service Life Cycles at the same time. Each
one of these versions will remain in the Configuration Server until they are deleted.
Only one version of an object can exist per Life Cycle.
40
3BUA000157R4101
Validation
Validation
When an object is stored or the Life Cycle is changed, a set of validation rules are
executed. There are both generic validation and object type specific rules. When a
validation error occurs, the action being attempted cannot be finished. An example
of a validation rule is shown in Table 1.
Table 1. Life Cycle Validation
Life Cycle
Validate Against
Description
Design 1
Release or Running
Release
Release
Running
Running
Out of Service
No validation.
3BUA000157R4101
41
Text Length
The lengths specified in Table 2 for the different properties are the maximum
number that can be handled by the system. This does not imply that the maximum
number of characters will always be shown in every display or application. The
character space in some applications is limited, and in some cases, field widths are
user adjustable. When a string is truncated in a display, the whole string is usually
shown in the form of a tool tip.
Table 2. Text Lengths
42
Entity
Maximum
Characters
Object Name
32
Property
Name
32
Description
64
Descriptions
3BUA000157R4101
Character Sets
Character Sets
Three groups of characters for object names and property names are used.
Legal Character Set
ASCII Value
0 to 9
048 to 057
A to Z
065 to 090
a to z
097 to 122
Since Harmony INFI 90 is most often used with other systems, these other systems
have their own legal character set. The legal characters are actually a combination
of all the restrictions of Harmony INFI 90 and the connected system.
Illegal Character Set
Harmony INFI 90 and commonly used applications, such as SQL Server and Excel,
support the illegal character set listed in Table 4. These characters, however, must
not be used in names.
Table 4. Illegal Character Set
Character
ASCII Value
Reserved Use
(quotation)
034
# (pound)
035
% (percent)
037
& (and)
038
(apostrophe)
039
( (parentheses open)
040
For arrays.
3BUA000157R4101
43
Character Sets
ASCII Value
Reserved Use
) (parentheses close)
041
For arrays.
* (asterisk)
042
, (comma)
044
. (period)
046
Separator tag.property.
/ (slash)
047
: (colon)
058
Subscription suffix.
; (semicolon)
059
? (question mark)
063
[ (bracket open)
091
\ (backslash)
092
Delimiter
] (bracket close)
093
123
125
127
00 through 31
Table 5 lists the characters that cannot be used for the first or last character in a
name.
Characters that are classified as not allowed can be addressed with an escape
sequence. Characters not supported by an application but supported by Harmony
INFI 90 can be addressed using an escape sequence. The escape sequence is:
\nn
44
3BUA000157R4101
Character Sets
ASCII Value
Space 1
032
! (exclamation
point)
033
+ (plus sign)
043
- (negative sign)
045
_ (underscore)
095
3BUA000157R4101
45
Character Sets
46
3BUA000157R4101
Tabs.
Body.
Footer.
Tabs
The tabs associated with the Aspect view depend on the type of object that is
selected for Harmony. Harmony data that is common to multiple object types is
presented in the same way to help make Harmony tasks easier and to improve
efficiency. The General and Version tabs are included for every object type.
Body
The body area contains all of the configurable properties of any selected tab. The
fields are only editable in the Design Life Cycle version of an object, when the user
has Harmony access rights, and after the user has locked the object for editing.
Refer to Section 2, Harmony OPC Server for more information on security.
3BUA000157R4101
47
Footer
Footer
The footer area shows general object information; contains controls to change the
Life Cycle; and contains controls to edit, submit, and cancel changes (). Different
buttons are available in the footer depending on the Life Cycle of the object as
shown in Figure 9.
The Life Cycle field shows the Life Cycle of the object. This is a display only field.
Locked By
The Locked By field shows the name of the user that has locked the object for
editing. If the object is not locked this field will be blank.
Validate Against
The Validate Against shows the current method of validation. Objects in the Design
Life Cycle present user selectable validation options. Objects in the Release and
Running Life Cycles show Release and Running validation respectively.
48
3BUA000157R4101
Life Cycle
The Life Cycle buttons change the object to a desired Life Cycle. These buttons will
be displayed or hidden based on the current Life Cycle and the user access rights.
Delete Version
Copies this object and creates a new object in Design mode. The new object retains
all of the configured properties of the original except for the ID.
Submit Changes
Only visible when the object is being edited. It submits changes to the Harmony
Server.
Edit Object
Locks the object and allows editing its definitions. This button is only enabled if the
user has access rights, the object is not currently locked, and the object is in the
Design Life Cycle.
Cancel Changes
Only visible when the object is being edited. It cancels any changes without
updating the Harmony Server and unlocks the object.
3BUA000157R4101
49
Unlocked
When an object in the Design Life Cycle is first called up, it is unlocked (unless it
has already been locked by another user). Any user with access rights can edit the
object. The body of the view contains view only fields.
The Life Cycle of the object can be changed to Release, Running, or Out of Service
when unlocked. Clicking a Life Cycle change button causes the Server to attempt to
change the object to the selected Life Cycle. This involves obtaining a lock,
performing a validation, and if successful, moving the object into the new Life
Cycle.
Locked by Current User
For an object in the Design Life Cycle, the Server attempts to obtain a lock when the
edit object button is clicked. Once the lock has been obtained, the view changes to
the locked by user view, which updates the Locked By field and changes the fields
within the body of the view from view only to editable. The Life Cycle of the object
can be changed to Release, run, or Out of Service when unlocked.
Locked by Other User
For an object in the Design Life Cycle, the object is called up in the locked by other
user view when another user is currently editing the object. In this case, the Locked
By field will show the name of the user currently editing the object and the fields
within the body of the view are view only.
The locked by user is not updated automatically but only on interaction with the
Harmony Server.
Release Life Cycle
In the Release Life Cycle, the user can view the object or change its Life Cycle. The
Locked By field is not visible. The validate against field is fixed to Release.
Running Life Cycle
In this Life Cycle, the user can view the object or change its Life Cycle. The Locked
By: field is not visible. The validate against field is fixed to run.
50
3BUA000157R4101
Configuration Actions
In this Life Cycle, the user can view the object or change its Life Cycle. The Locked
By and Validate Against fields are not visible.
Configuration Actions
All of the configurations actions for the Harmony INFI 90 system are done through
the TagConfig aspect views.
INFI 90 Harmony Server Objects are automatically created when the Harmony
Synchronizer is first run after installation.
2.
3.
4.
Right-click on the Harmony OPC Server Network Object and select New
Object.
5.
6.
7.
8.
Select Create.
9.
A template of the tag is created. This template version of the tag is an interim
version and is not usable by the Harmony INFI 90 system.
If the TagConfig aspect is selected, before running the Harmony Synchronizer, a
message will appear saying that Harmony Tag Objects are initially instantiated as
templates. Run the Harmony Synchronizer Aspect if a message is displayed.
Click OK.
10. Repeat Step 1 through Step 9 until all the required Objects have been defined.
11. Right-click on the Harmony OPC Server Network Object.
3BUA000157R4101
51
12. Run the Harmony Synchronizer Aspect. Use the default options.
13. Once the tag is created, open the TagConfig Aspect for the Design version of
the tag Object, to make changes.
If the TagConfig Aspect is open it will still be pointing to the initial template for
the tag. Close and then open it again to point to the Design version.
14. Click on Edit Object. Refer to Figure 9 for more information.
15. Make any attribute changes.
16. Save the changes.
17. Change Life Cycle to Running.
Once a Tag object is assigned Harmony address information, it will be
automatically moved to the appropriate location in the Control Structure
hierarchy.
2.
3.
4.
5.
6.
7.
8.
9.
52
3BUA000157R4101
2.
3.
4.
5.
6.
Select each of the tabs for Out of Service and Design, and click on the Delete
This Version button for each.
7.
Select the Release tab and change its Life Cycle to Out of Service.
8.
9.
Select the Running tab and change its Life Cycle to Out of Service.
2.
3.
4.
5.
6.
7.
8.
9.
3BUA000157R4101
53
11. Run the Harmony Synchronizer or wait for the automatic Server Monitor
Object Synchronize to occur.
12. The name will propagate back to the Harmony INFI 90 system.
2.
3.
4.
5.
General Tab
The General tab contains the following sections (Table 6):
Identification.
Template.
Advanced.
Identification
The identification section shows the information that identifies the object to the user
throughout the Harmony INFI 90 system.
54
3BUA000157R4101
General Tab
Description
Identification
Type
Name
Description
Template
Based On
Advanced
User Text
User Index 2
NOTES:
1. Refer to See Naming Conventions and Guidelines for a description of the legal character set for
names.
2. This field is currently used by Operate IT conversion tools to map the original object in Operate IT
to a new object in Harmony INFI 90.
Template
The templates section provides information about the template the object was
created from.
3BUA000157R4101
55
Version Tab
Advanced
Click the advanced arrow to expose the user text and the user index fields.
Version Tab
The Version tab is used to add and view comments about the object. The Comment
field is used to enter a user defined comment related to the specific version of the
object. Comments can be added independent of the Life Cycle the object is in. The
object does not have to be in edit mode to add a comment. The design engineer, as
well as the person putting the object into operation, can make comments. Security
does not apply to this feature.
Every Life Cycle change and submit will automatically create a version entry
containing the user name, time, and action performed.
To enter a comment:
1.
2.
Click Add Now. This adds the comment to the list that appears at the bottom of
the window. Version, User, Date, and Life Cycle are automatically filled in.
The area below the comment entry field provides a list of the version information
for the object in a table form. Table 7 describes the columns in the information
section.
Table 7. Version Tab Columns
Field
56
Description
Get Version
User
Shows the name of the user who entered the comment. This
field is filled in automatically.
Date
Life Cycle
Shows the Life Cycle the object was in when the comment
was added. This field is filled in automatically.
Comments
3BUA000157R4101
Description
Common
Server
Harmony
RMCB Text Refer to Remote Motor Control Block Text Tab on page 64 for more
information.
3BUA000157R4101
57
Harmony Tab
Harmony Tab
The Harmony tab is used to configure specific information related to the Harmony
control system (Figure 10). The fields in this view are described in the following
paragraphs:
TC04817A
58
3BUA000157R4101
the alarm summary for an alarm is the time the exception report was read and is
displayed to the second.
1. The Module Timestamping option is not available when the Scanner is an
INFI-NET Scanner option is unchecked.
2. It is recommended that the module timestamping option be enabled for each
Connectivity Server in a pair.
Time Synchronization
Determines whether or not the Server receives and sends the time synchronization
on the network. When enabled, the Server is in time synchronization with the
control network.
Scanner is an INFI-NET Scanner
Identifies the type of control network as either Cnet (INFI-NET) or Plant Loop.
Checked is for Cnet (INFI-NET) and cleared is for Plant Loop.
Global Alarm Acknowledgment
The global alarm acknowledgment function allows Harmony INFI 90 to send and
receive global alarm acknowledgment messages to or from other nodes on the
control network. Refer to the following heading for more information.
3BUA000157R4101
59
TC08155A
60
3BUA000157R4101
A client application can put a non-zero value to the Silence atom to cause a global
silence to be transmitted to the loop. An information message is logged in the
system event log when a global silence message is transmitted to the loop.
Configure the Harmony Server tag to receive silence messages from other nodes on
the loop.
On the Harmony tab, check the Global Alarm Silencing check box to inform the
active RTDS to process the Global Alarm Silence messages received through the
INFI-NET loop.
An information message is logged in the system event log when a global silence
message is received from the loop.
Configuring Node to Send Global Silence to Navigator from RTDS
The Silence atom of the Harmony Server tag is configured to feed the Reset In atom
in the Function Block Trigger object. When a global silence message is received
from the loop, the RTDS sets the Silence atom to 1 momentarily. This resets the
OUTPUT/SIG of the Function Block Trigger object to 0 which silences the tone tag.
3BUA000157R4101
This enables the RTDS to broadcast the alarm acknowledgement for this tag on the
communication highway.
Enable Acknowledgment Transmission
Configured the module status tag for each node to which the RTDS transmits the
alarm acknowledgment messages. For each module status tag, on the Module tab,
check the Enable Alarm Acknowledgment Transmission check box to have the
RTDS transmit any recently acknowledged alarms.
Broadcasts will only be sent to a node when the corresponding module status tag is
configured and has alarm acknowledgment transmission enabled.
Time Synchronization
Accuracy
Time synchronization accuracy of the Server. Valid when the Server is in time
synchronization mode. The options are:
62
3BUA000157R4101
Communication Errors
These accuracy settings are only used when negotiating for time mastership with
other nodes in the underlying Harmony INFI 90 control network.
Master Update Period
Frequency that Harmony Server synchronizes time with the underlying Harmony
INFI 90 control network. This property is only used when Time Synchronization is
enabled. Valid entry 120 to 3540 seconds.
Message Wait Period
Period that Harmony Server waits before attempting to assume time mastership on
INFI 90 control network. This property is only used when Time Synchronization is
enabled. Valid entries are between 180 and 3660 seconds. Additionally, the
configured value must greater than the Master Update Period.
Run RTDS in OIS Mode
Allows the RTDS to time sync properly with an OIS component. This setting should
only be set if both OIS nodes and Harmony INFI 90 are being time synchronized on
the same loop.
Communication Errors
The communication errors section configures the text and priority for the errors.
Advanced Options
Harmony Namespace Support
Allows the Harmony Server to process requests for non tag information, such as
block detail and module detail status information. This setting should be enabled on
the RTDS in order for the Block Details and Module Details applications to function
properly.
3BUA000157R4101
63
Tells the Harmony Server to not persist values written to export type tags in bulk
mode to the persistent database. This allows for faster and more efficient bulk data
exporting.
No error.
Stopped.
Interlock one.
Interlock two.
Interlock three.
Interlock four.
Feedback one = 0.
Feedback two = 0.
Feedback one = 1.
Feedback two = 1.
The interlock codes indicate not set or logic zero conditions for each of four
interlocks.
Each error code text set has an assigned number. Up to 100 sets can be defined
numbered zero to 99. A text set field for an RMCB tag selects which text set is to be
used for the tag. Refer to Remote Motor Control Block Text Tab on page 64 for
more information on configuring an RMCB tag. The specific text string that
displays depends on the error code returned in an exception report from the RMCB
block.
The RMCB Text tab configures text for RMCB error codes (Figure 12). This tab
contains a line of 100 selectable fields for displaying different RMCB sets. The
fields are marked blue when they are used and white when available. When one of
64
3BUA000157R4101
these fields is selected the set number of the text set is automatically filled in. The
set name is followed by a list of the ten text strings for an RMCB tag.
TC02474B
Select an unused set to add a new one or select a configured one to edit it.
2.
3.
Enter all the text information for the error states, interlocks, and feedbacks.
3BUA000157R4101
65
66
3BUA000157R4101
Section 6 Tags
Introduction
This section describes the configuration of Harmony tags. A tag is required to
access Harmony data and to perform control actions from a workstation. The tags
can be configured from any system node.
The system must have a Harmony RTDS installed. Once configured, Harmony tag
data can be used in Harmony INFI 90 functions such as process displays, reports,
event pages, alarming, etc.
Tag Types
Harmony INFI 90 allows online tag configuration. Tags can be added, deleted,
changed, and updated to the system according to their Life Cycle.
3BUA000157R4101
67
Section 6 Tags
Refer to Appendix A, Signal Structure for the signal structure of all the Harmony
tag types.
Table 9. INFI 90 Harmony Tag Types
Type
68
Support
Function
Code1
Purpose
FC 136
Analog
Export
N/A
FC 30
ASCIIText2
FC 194
DAANG2
Data Acquisition
Analog
FC 177
DADIG
Data Acquisition
Digital
FC 211
Used internally
3BUA000157R4101
Section 6 Tags
Support
Device Driver
Function
Code1
Purpose
FC 123
N/A
Digital Read
Digital exception
report
FC 45
Enhanced
Analog
Input2
Enhanced Analog
exception report
FC 222
Enhanced
Analog
Output2
Enhanced Analog
exception report
FC 223
Enhanced Digital
Enhanced
Digital Input2 exception report
FC 224
Enhanced
Digital
Output2
Enhanced Digital
exception report
FC 225
ModStat
Read
Module Status
monitor
FC 95
FC 129
3BUA000157R4101
69
Section 6 Tags
Support
Purpose
PhaseX
Read
Phase execution
FC 218
RCM Read
Remote Control
Memory
FC 62
FC 136
FC 68
SOE
Recorder
SOE Report
Read
Sequence of Events
Logs
FC 99,
SEM
blocks:
5000 and
5001
FC 21
FC 22
FC 23
FC 80
70
Function
Code1
3BUA000157R4101
Section 6 Tags
Support
Function
Code1
Purpose
Text Read
Text Selector
FC 151
System
Definition
NOTES:
1. Refer to the Function Code Application Manual for more information and for descriptions
of FC specifications.
2. Not supported by Plant Loop.
Description
Common
Same common object properties as other objects (general, aspects, views, and
version).
Harmony
3BUA000157R4101
71
Section 6 Tags
Description
Tag specific Each type of tag object has unique properties. Refer to Analog Tab on page 74,
Analog Export Tab on page 76, Enhanced Analog Input/Output Tab on page 76, ASCII
Tab on page 76, Data Acquisition Analog Tab on page 77, Device Driver Tab on page
79, Digital Tab on page 79, Digital Export Tab on page 80, Enhanced Digital
Input/Output Tab on page 81, Data Acquisition Digital Tab on page 82, Module Status
on page 82, Multi State Device Driver Tab on page 83, PhaseX Tab on page 85,
Remote Control Memory Tab on page 86, Remote Motor Control Block Tab on page
87, and Remote Manual Set Constant Tab on page 88 for more information. The Text
Selector object does not have any tag specific properties. Refer to Text Selector on
page 92 for more information.
Harmony Tab
The Harmony tab is configured for every Harmony tag object (Figure 13). This tab
determines system information that identifies the tag in the Harmony system and the
actions that can be performed on the tag in the control system.
To configure the Harmony tab:
72
1.
In the Server field select the Server that will host the tag from the list of
available Servers. Click the ellipsis () to open the list of available Servers.
2.
Configure the bad quality event point. Refer to Event Point Configuration on
page 72 for more information.
3BUA000157R4101
Section 6 Tags
Harmony Tab
TC04567A
In the Inhibit area, select a tag.property for automatic alarm inhibiting. This
property is used to inhibit alarm indications for selected tag. Alarm inhibiting
is based on the current value of the inhibit tag. Leave it blank to disable
automatic alarm inhibiting.
4.
Enter the address of the function block that contains the FC that the tag is to
monitor. The fields are:
Loop.
Node.
Module.
Block.
Loop
The communication highway for the Harmony system. Valid entries are 0 to 250.
Node
3BUA000157R4101
73
Analog Tab
Section 6 Tags
Module
Location of a specific FC in the controller. Valid entries are one to 9,998 for the
BRC-100/BRC-200, IMMFP11, and IMMFP12 controllers and 31,998 for the HAC
controller.
The loop, node, module, and block settings must be unique within a system.
5.
Analog Tab
The Analog tag accesses information provided by an Analog exception report FC
(refer to Table 9). The Analog exception report FC allows an Analog value to be
sent on the communication highway if the value changes outside a configured
deadband. This function also generates an alarm if the high or low limit values are
reached. The Analog tab of the Analog tag object configures the Analog exception
report FC that is to be monitored by the Harmony RTDS (Figure 14).
To configure the Analog tab:
74
1.
Configure the low alarm and the high alarm event points for the Analog tag.
Refer to Event Point Configuration on page 72 for more information.
2.
Set the alarm limits for the tag. The alarm limits trigger the high and the low
alarm event points when the value goes outside the respective limit.
3.
Set the high and low range values of the process value.
3BUA000157R4101
Section 6 Tags
Analog Tab
TC04562A
5.
Set the display format using the width (number of characters) and digits
(number of decimal digits) controls. The syntax of this field is:
The values set in Step 2 through Step 4 are configurable for initial value purposes
only. They will be overwritten by values reported from the function block after
startup.
3BUA000157R4101
75
Section 6 Tags
ASCII Tab
The ASCII Text string tag interfaces with a user defined data export FC (refer to
Table 9). The user defined data export FC outputs user data via an exception report.
The ASCII tab of the ASCII Text string tag object configures a user defined data
export FC that is to be monitored by a Harmony RTDS (Figure 15).
To configure the ASCII tab:
1.
76
Configure the alarm status event point for the tag. Refer to Event Point
Configuration on page 72 for more information.
3BUA000157R4101
Section 6 Tags
TC04563A
Set the maximum text width. If this string length is less than the actual length
of the exception reported text string, truncation will occur. This is considered to
be remote truncation since the communications interface unit of Harmony INFI
90 uses the value to determine the maximum length of the text string it will
accept. Valid entry 0 to 80.
3.
4.
3BUA000157R4101
77
Section 6 Tags
TC04564A
78
1.
Configure the low alarm and the high alarm event points. Refer to Event Point
Configuration on page 72 for more information.
2.
Set the alarm limits for the tag. The alarm limits trigger the high and the low
alarm event points when the value goes outside the respective limit.
3.
Set the high and low range values of the process value.
4.
Click the ellipsis () and select a configured engineering unit descriptor. The
controller reports the index number that associates an engineering unit of
measurement with this tag. A list of valid fixed and user defined engineering
units can be viewed in the system definition object.
3BUA000157R4101
Section 6 Tags
5.
Set the display format using the width (number of characters) and digits
(number of decimal digits) controls. The syntax of this field is:
Number of characters X 10 + number of decimal digits
The values set in Step 2 through Step 4 are configurable for initial value purposes
only. They will be overwritten by values reported from the function block after
startup.
6.
Scroll down through the page and configure the event points for the DAANG
tag. Refer to Event Point Configuration on page 72 for more information.
Configure the output state and the state change event points. Refer to Event
Point Configuration on page 72 for more information.
2.
Set the normal and the active signal text for the first feedback state by clicking
the ellipsis () and selecting one from the list.
3.
If reverse logic is to be used for this tag (zero is active) enable complement
input signal.
4.
Digital Tab
The Digital tag accesses information provided by a Digital exception report FC
(refer to Table 9). The Digital exception report FC exception reports the output state
of the block. Exception reports are activated by a report enable signal from the
module bus. The maximum number of exception reports allowed depends on the
3BUA000157R4101
79
Section 6 Tags
TC04565A
80
3BUA000157R4101
Section 6 Tags
TC04566A
3BUA000157R4101
81
Section 6 Tags
Module Status
The Module Status tag accesses information provided by a Module Status FC (refer
to Table 9). Module Status tags can be configured for every process controller and
process node, gateway, bridge, and computer interface in the Harmony control
system. The Module Status tab of the Module Status tag object configures the
Module Status FC that is to be monitored by a Harmony RTDS (Figure 19).
To configure the Module Status tab:
82
1.
Configure all the event points on the tab. Refer to Event Point Configuration on
page 72 for more information.
2.
3BUA000157R4101
Section 6 Tags
TC04568A
3BUA000157R4101
83
Section 6 Tags
control mode. The MSDD block provides four state controls with feedback. Two
control inputs or an operator input selects one of four output masks for control
action. The MSDD tab of the MSDD tag object configures the MSDD FC that is to
be monitored by the Harmony RTDS (Figure 20).
TC04569A
84
1.
Configure the output state and the state change event points. Refer to Event
Point Configuration on page 72 for more information.
2.
Set the normal and the active signal texts for the first feedback state by clicking
the ellipsis () and selecting one from the list.
3.
If reverse logic is to be used for this tag (zero is active) enable complement
input signal.
4.
5.
Configure the logic state descriptor zero through three by clicking the ellipsis
() and selecting a logic descriptor from the list.
3BUA000157R4101
Section 6 Tags
PhaseX Tab
PhaseX Tab
The PhaseX tag accesses information provided by a phase execution FC (refer to
Table 9). The phase execution FC provides the execution environment for a Batch
90 program that is interfaced to Produce IT Batch or the batch data manager (BDM)
software. A Batch 90 program is comprised of all the phases that can be run on a
specific class of equipment. Recipes define the order in which the Batch 90 phases
are executed (the procedure) and the specific formulation values such as target flow
rates, temperatures and times. The PhaseX tab of the PhaseX tag object configures
the phase execution FC that is to be monitored by the Harmony RTDS (Figure 21).
TC04570A
3BUA000157R4101
Configure the system fault, user defined fault, and the user defined message
event points. Refer to Event Point Configuration on page 72 for more
information.
85
Section 6 Tags
2.
When handshaking is enabled the block uses fast reporting max. time value (in
seconds) for exception reports until a confirmation is received by the block. If
handshaking is disabled the block uses slow reporting max. time value (in
seconds) to report new values.
3.
Set the fast reporting max. time. The fast reporting max. time is the time value
used to monitor exception reports when handshaking is enabled.
4.
Set the slow reporting max. time. The slow reporting max. time is the time
value used to monitor exception reports when handshaking is disabled.
TC04571A
86
3BUA000157R4101
Section 6 Tags
Configure the output state and the state change event points. Refer to Event
Point Configuration on page 72 for more information.
2.
Set the normal and the active signal texts for the first feedback state by clicking
the ellipsis () and selecting one from the list.
3.
If reverse logic is to be used for this tag (zero is active) enable complement
input signal.
Configure the output state and the state change event points. Refer to Event
Point Configuration on page 72 for more information.
2.
Set the normal and the active signal texts for the first feedback state by clicking
the ellipsis () and selecting one from the list.
3.
If reverse logic is to be used for this tag (zero is active) enable complement
input signal.
4.
5.
Set the normal and the active signal texts for the first permissive state by
clicking the ellipsis () and selecting one from the list.
6.
If reverse logic is to be used for this tag (zero is active) enable complement
input signal.
7.
8.
Select a text set index by clicking the ellipsis () and selecting one from the
list. The text set that contains the text identifiers for each of the 10 error codes
3BUA000157R4101
87
Section 6 Tags
TC04572A
88
Set the high and the low range for the process variable. These are the maximum
and minimum values allowed for the RMSC tag.
3BUA000157R4101
Section 6 Tags
Station Tab
TC04573A
Click the ellipsis () and select a configured engineering unit descriptor. The
controller reports the index number that associates an engineering unit of
measurement with this tag. A list of valid fixed and user defined engineering
units can be viewed on the system definition configuration page.
3.
Set the display format using the width (number of characters) and digits
(number of decimal digits) controls. The syntax of this field is:
Number of characters X 10 + number of decimal digits
The values set in Step 1 and Step 2 are configurable for initial value purposes
only. They will be overwritten by values reported from the function block after
startup.
Station Tab
The Station tag accesses information provided by a Station FC (refer to Table 9).
There are three types of Stations, each controllable through a control station and
Harmony INFI 90. The types include basic, cascade, and ratio Stations. The Station
tab of the Station tag object configures the Station FC that is to be monitored by the
Harmony RTDS (Figure 25).
Basic
A basic Station generates a set point and provides manual/automatic transfers,
control output adjustments in manual control mode, and set point adjustments in
automatic control mode.
3BUA000157R4101
89
Cascade
Section 6 Tags
TC04574A
Cascade
A cascade Station provides the same functions as a basic Station plus an additional
mode that allows the set point to be controlled by external input signal.
Ratio
A ratio Station provides the same functions as a basic Station, but differs from the
cascade Station in its method of set point generation when in the ratio mode. A wild
variable multiplied by a ratio adjustment factor (ratio index) determines the set point
output when in ratio mode. The initial ratio index value is calculated by the Station
to maintain the current set point output value when the Station is placed into the
ratio mode. When in the ratio mode, the ratio index value is displayed in place of the
set point value and can be adjusted (ramped up or down) by the operator to obtain
the desired set point output.
90
3BUA000157R4101
Section 6 Tags
Ratio
Station control allows changing the mode, set point, ratio index and control output
of a control Station by manipulating a control Station element. The control output
(CO) value during startup is configurable.
To configure the Station tab:
1.
Configure the low alarm and the high alarm event points. Refer to Event Point
Configuration on page 72 for more information.
2.
Set the alarm limits for the tag. The alarm limits trigger the high and the low
alarm event points when the value goes outside the respective limit.
3.
4.
Click the ellipsis () and select a configured engineering unit descriptor. The
controller reports the index number that associates an engineering unit of
measurement with this tag. A list of valid fixed and user defined engineering
units can be viewed on the system definition configuration page.
5.
Set the display format using the width (number of characters) and digits
(number of decimal digits) controls. The syntax of this field is:
Number of characters X 10 + number of decimal digits
6.
Configure the low deviation and the high deviation event points. Refer to Event
Point Configuration on page 72 for more information.
7.
8.
Click the ellipsis () and select a configured engineering unit descriptor. The
controller reports the index number that associates an engineering unit of
measurement with this tag. A list of valid fixed and user defined engineering
units can be viewed on the system definition configuration page.
9.
Set the display format using the width (number of characters) and digits
(number of decimal digits) controls. The syntax of this field is:
Number of characters X 10 + number of decimal digits
The values set in Step 2 through Step 4 and Step 6 through Step 8 are
configurable for initial value purposes only. They will be overwritten by values
reported from the function block after startup.
10. Repeat Step 7 through Step 11 for the deviation limit and the set point.
3BUA000157R4101
91
Text Selector
Section 6 Tags
11. Select a tune block by clicking the increment or decrement arrows beside the
field. The tuning block is the function block to appear in the Block Details
portion of a tuning display (normally a PID block). A valid entry is 1 to 31,998
and is for the block address of the function block providing the Station block
input or any function block in the controller. This allows the tuning display to
be requested without any further input.
Text Selector
The Text Selector tag defines text strings that can be associated with status reported
for DD, MSDD, and RMCB tags. These text strings can describe the good, bad, and
waiting condition being reported by a Device Driver or MSDD function block and
the good, alarm, and waiting condition being reported by a remote motor control
function block. The conditions are exception reported by a PCU module.
In the module, a Text Selector function block (FC 151) must be defined in the
control configuration to reference a DD, MSDD, and RMCB function block. The
Text Selector function block can also be configured as a standalone Text Selector.
Each Text Selector message defined in the Configuration Server has a message
number. The Text Selector function block in the controller selects one of these
messages by its number. The function block exception reports a message number
and also a color and blink parameter. A Text Selector tag must be configured in
Harmony INFI 90 to receive this information.
The configuration view of the Text Selector tag is shown in Figure 26. To configure
a Text Selector tag, configure the Harmony tab to monitor the desired Text Selector
function block (FC 151) in the Harmony control system configuration.
92
3BUA000157R4101
Section 6 Tags
Text Selector
TC04426A
3BUA000157R4101
93
Text Selector
94
Section 6 Tags
3BUA000157R4101
Configuration Data
Configuration data includes ASCII text strings, alarm comments, engineering unit
descriptors, logic state descriptors, RMCB error code text sets, text selections, and
tag definitions. The tag definitions can be in one of the following formats:
Conductor NT 2.1.
.X1.
Files with a .cp extension must be assumed to use run length compression (SLDG
standard) during the import process.
The configuration importer utility requires the use of a temporary working directory
to perform file modifications (file decompression, record delimiter insertion, etc.).
Normally these variables are defined by Windows 2000 to specify a directory at the
system root called \temp. However, these variables can be configured otherwise.
The replication of configuration changes is disabled during the import operation. It
is enabled at the end of a successful import. If an import operation stops before
being completed, enable Synchronize data after each object update (on the
management tab of the system definition object properties) before trying to import
the tag data again.
3BUA000157R4101
95
In the Select Import Option window, select the type of tag information to be
imported (Figure 27). It is recommended that any other information besides the
tag definitions be imported first. If tag definitions is selected, refer to the next
topic in this section. Click Next to continue.
If tags are defined with custom logic state descriptors, then the logic state
descriptors must be imported before tag definitions. Otherwise the logic state
settings for each tag will need to be reconfigured.
2.
In the File Name: field, click the ellipsis () and select the file that is to be
imported. Click Next to continue.
3.
A final window stating that all the necessary information has been entered will
appear. Click Finish to perform the operation.
4.
A log window appears confirming the completion of the text import function.
5.
Repeat these steps for all the text information types to be imported.
96
3BUA000157R4101
TC02489C
In the select import window, enable Tag Definitions (Figure 27). Click Next to
continue.
2.
In the Import Tag Definitions window, select the format, then click the ellipsis
() to select file to import (Figure 28).
3.
4.
The default selection is to include the engineering unit descriptors, logic state
descriptors, PhaseX fault code list, and alarm comments in the import. Deselect
3BUA000157R4101
97
TC02491C
98
5.
6.
Select the templates to be used during import. Any new tags will be copied
from the template and then updated with the information imported.
7.
A final window stating that all the necessary information has been entered
appears. Click Finish to perform the operation.
8.
A log window appears confirming the completion of the tag import function.
3BUA000157R4101
Import Progress
Import Progress
If more than 100 objects are imported, a dialog box will appear asking to restart or
to not restart the affected Servers. If Restart the Affected Servers is chosen, the
changes will not be replicated for the affected Server until it is restarted. Restarting
the Server can be done automatically or manually:
Manually - User may choose to restart the Server at any given time required,
but changes will not be recognized on the Server until it is restarted.
When Do not restart the Server(s) is chosen, the changes will be replicated online
to the Server and may take some time to complete. If the changes are significant,
some performance affect may be visible to the user. Refer to Figure 29.
TC04819A
3BUA000157R4101
99
Import Progress
100
3BUA000157R4101
In the Export Tag Definitions window, click the ellipsis () to select the file
name of the configuration database (.MDB) and export the data (Figure 30) if
one is not already selected.
2.
3BUA000157R4101
101
Select Tags
TC03796A
Select Tags
In the Select Tags To Export window, a list of Harmony tags will be shown
(Figure 31). The tag name, type, and Server they are on are displayed in separate
columns.
List of Tags
Selecting a name from the list enables that tag for exporting. Multiple items in the
list can be selected. Press and hold the CTRL key to highlight a non contiguous
group of tags to add or remove them from the list to export. Press and hold the
SHIFT key to highlight a contiguous group of tags to add or remove them from the
list to export. Use the Select All button to select all of the tag names in the list. Use
the Invert button to invert the selected state of all tags in the list.
102
3BUA000157R4101
Tag Types
TC03797A
Tag Types
A separate drop-down list box in the same window (Figure 31) displays all the tag
types found in the list. By selecting a tag type in the box, all the names of that
specific tag type are selected in the list. This is updated immediately whenever a
Life Cycle (Running, Release, or Design) is checked or unchecked (if Running is
selected, only Running tag types appear in the drop-down list box and etc.).
A counter to the right of the drop-down list box (Figure 31) indicates both the
number of tags highlighted and the total currently in the list. This is updated
whenever a tag is selected, unselected, or the number of items in the list changes.
Life Cycles
A Life Cycles group contains the three Life Cycles of an object that the utility will
look for when exporting an object (Figure 31). These Life Cycles are Running,
Release, and Design.
3BUA000157R4101
103
Columns To Export
Running
Select Running to only list and export Running objects. Running objects are the
operating versions of an object in a system.
Release
Select Release to only list and export Release objects. Release versions may become
the next Running or operating versions of objects in the system.
Design
Select Design to list and export Design objects. Design objects have not been
implemented to be Release or Running objects, and are currently being configured.
If multiple Life Cycles are selected, the exporter will choose Release over Design
and Running over Release and/or Design.
Columns To Export
In some cases, changes in data are only made to specific columns. Rather than
export all columns, this step allows those specific columns to be selected for export.
The list begins with the known columns found in the tag list table. All data fields
will be highlighted. If a column is not highlighted, the column is removed from the
tag list table before exporting begins.
As a minimum, the OBJECTID, NAME, and TYPEID columns must be exported
from Composer for Harmony INFI 90 to import Composer tag data. When
importing new tags that will have a Life Cycle of Running, the LOOP, NODE,
MODULE, and BLOCK columns must also have been exported. To update only one
column of data, that column and the three minimum columns must have exported
from Composer.
This step adds any properties for each tag type being exported that is not already
covered by the known, fixed columns supported by Composer. These are not
highlighted. Any column that is highlighted is added as a column to the tag list table
before the export process begins (Figure 32). Select the appropriate data fields to be
exported.
104
3BUA000157R4101
Export Progress
TC03798A
Export Progress
As with importing, progress is displayed when exporting. An output window shows
the current progress and any warning or error messages. Progress is updated each
time 50 tags are exported or the final tags of a type are exported. A copy of the tag
list table is made for each Harmony Server that is associated with the tags selected
for export. The tags selected for exporting are sorted and data is exported by Server
and then by type: all the Analogs, then all the Digitals, and etc.
3BUA000157R4101
105
Export Progress
106
3BUA000157R4101
Description
Harmony INFI 90 SOE reporting is intended for use by plant personnel to closely
monitor critical Digital points where the sequence of state changes for points or
groups of points must be known in the most exacting ways possible. SOE reporting
lists all Digital state transitions in time order and with one millisecond resolution.
The SOE log data can originate in an ABB Distributed SOE system (DSOE) or in a
Rochester Instrument Systems SOE Recorder (Rochester SER).
The SOE reporting system can interface with a SOE (IMSEM01) module containing
fixed blocks 5000 and 5001 or with a Harmony bridge controller (BRC-100 or
BRC-200) or a multifunction processor (MFP) containing FC 99 (sequence of
events log) blocks.
In both cases, SOE trigger tags can be configured for the blocks to monitor SOE
trigger points in the control system. The SOE reporting system then collects SOE
Reports whenever the trigger points indicate the presence of SOE data.
Specific Features
The following are features of SOE reporting on Harmony INFI 90:
3BUA000157R4101
107
Specific Features
Build SOE Reports from the data that it has gathered through communications
with semAPI, using preconfigured report formats.
Standard
In a standard log, any SOE point state change will result in a timestamped SOE
Report for this point. This SOE log will be stored in the controller (FC 99) or in the
IMSEM01 module (DSOE) for the length of time specified within the
corresponding block (the aging time). This log must be read in by the SOE reporting
system before the aging time expires.
Summary
A summary log contains a report of all timestamped SER points which are not in
normal state (inactive, deleted from scan, or in SOE alarm). This report can be
demanded by changing the RCM block output of the corresponding IMSEM01
block 5001 or FC 99 in the controller (the summary trigger point) from zero to one.
Pre-fault
SER point state changes are stored by a designated quantity or time period (50
events prior to trigger; 10 minutes prior to trigger). They are then reported, in
ascending time order, when the pre-fault trigger is changed from zero to one by the
operator (Rochester SOE reporting only).
Post-fault
SER point state changes are reported only after the post-fault trigger is changed
from zero to one by the user. The points will continue to be reported until the
postfault trigger reverts back to zero. The SOE system must remove these reports
from the SOE or DSOE system before its aging time expires (Rochester SOE
reporting only).
108
3BUA000157R4101
Snapshot
Snapshot reports will have points listed in ascending numerical order, but only after
the snapshot trigger is changed from zero to one by the user. Snapshot points can be
designated in groups such as those which are normal, those which are deleted from
scan, etc. (Rochester SOE reporting only).
1. DSOE reporting supports only two SOE log types, standard (through
IMSEM01 block 5000) and summary (through IMSEM01 block 5001).
2. Snapshot reports are not available on all Rochester SOE reporters. Consult the
documentation of the Rochester SER hardware in this case.
3. If SOE reporting is running on a pair of Connectivity servers, SOE Reports
will be identically collected on both Servers. Refer to SOE Reporting and
Redundancy on page 110 for more information.
3BUA000157R4101
109
REPORTREAD property to zero. The report system makes the SOE data available
for the user to view.
110
One or more multifunction processors (firmware revision F.0 or later) or BRC100/BRC-200 modules are needed for use as a controller for the SET/SED
module pair.
3BUA000157R4101
3BUA000157R4101
111
112
3BUA000157R4101
A Rochester reporter consisting of one (or more) Rochester event capture units
(ECU) and an Rochester SOE communication interface unit with one fiber
optic communications board per event capture unit. The communication
interface unit also needs a special ABB communications board, manufactured
by Rochester Instrument Systems.
One or more multifunction processors (firmware revision F.0 or later) or BRC100/BRC-200 modules to contain FC 99 for the Rochester reporter.
Access to at least one network printer for sending SOE Reports to.
3BUA000157R4101
113
Required termination units and cables to connect each of the modules. Refer to
the product instructions for wiring diagrams.
The points collected by the Rochester system are only available to the system in
the form of SOE Reports. If these points are needed in the process control system
as Digital points, then these points must be physically wired into Digital input
modules as well as the Rochester reporter. Include these points in calculations
when determining the number of I/O modules required.
114
Each SOE log trigger tag must be specified as an SOE Report tag within the
Harmony INFI 90 tag database, with its loop, node, module and block being
the same as that of the corresponding fixed output blocks 5000 and 5001 within
the SEM module or the corresponding FC 99 output block within a controller.
SEM fixed output blocks 5000 and 5001 interface with the distributed SOE
system to input millisecond timestamp distributed SOE events. Block 5000 is
used for collecting standard SOE events. Block 5001 is used for collecting
summary SOE events upon command by using a point display or an SOE
Report faceplate to set this SOE Report tag to one. These SEM blocks are not
configurable.
A Rochester SOE system requires that each controller have at least one FC 99
trigger block to accept SOE Reports from the Rochester equipment or Digital
input modules.
Digital tags must be configured in the tag database for all input field points
used by the SOE system.
3BUA000157R4101
SOE Objects
SOE Objects
The SOE Reports are configured with SOE recorder and SOE Report objects.
Digital points are assigned to the SOE recorders. The recorders are then assigned to
the SOE Report objects.
The SOE Report object is configured for each SOE Report that is to be done by
Harmony INFI 90. An SOE Report tag is used for triggering SOE Reports. Each
SOE Report object has an SOE recorder associated to it.
The report object is triggered by the REPORTREAD property. The Harmony INFI
90 report system will create the report from the data collected from the RTDS.
TC02494B
3BUA000157R4101
115
Digital Tags
Displays the Digital tag associated with the SER point number if there is one
assigned to the number selected. Clicking the ellipsis () opens a list of Digital tags
available on the RTDS.
SOE Recorder Number
The name of the tag that corresponds to the point number in the SOE input device.
For example, a physical point hard wired into the SOE device as input point one has
the name of the Digital tag for the corresponding Digital exception report (FC 45)
configured in the list in slot one.
SER Point Number
The point number in the corresponding SOE input device. For example, if a physical
point hard wired into the SOE device as input point one corresponds to that Digital
tag specified in the tag name, then it would be assigned SER point index one.
Select a tag name from the points associated list, or create a new point number
by clicking the add icon.
2.
For a new point select the point number from the list.
3.
Click () and select a tag from the list to associate to the new point, or select a
tag to replace the existing tag. The tag association can be removed from a point
number by selecting blank from the list.
A tag name and point number can be deleted from the list by selecting the tag name
and clicking delete. The deleted number can be replaced by entering the number in
the SER point number field and then associating a tag to it.
116
3BUA000157R4101
TC04816A
The recorder field shows the SOE recorder that is associated with the SOE Report
object.
3BUA000157R4101
117
Report Type
This is the SOE Report type. There are five available report types. They are
described in Specific Features on page 107 in this section.
Wait Time
The wait time applies only to SOE Reports of type standard and post-fault. This is
the time difference between when the state of the trigger tag changes from zero to
one (when the SOE system in the control system begins filling its internal buffer
with new SOE Reports) and when the SOE reporting system begins collecting these
reports from the control system.
The wait time must be much less than the aging time configured in the SOE
system in the control system for this trigger point. Otherwise, valuable SOE data
may be aged out of the internal buffer of the SOE system and be lost before it is
collected by Harmony INFI 90.
Active
The Active check box indicates whether an SOE Report is active and being
monitored and collected by the SOE system, or if the report is inactive.
To configure the SOE Report object:
118
1.
Configure the output state and the state change event points. Refer to Section 6,
Tags for more information.
2.
Set the normal and the active signal text for the first feedback state by clicking
the ellipsis () and selecting one from the list.
3.
If reverse logic is to be used for this tag (zero is active) enable complement
input signal.
4.
Select an SOE recorder to use for the report. Click the ellipsis () and select
one from the list.
5.
6.
Click on the Active box to toggle this report from inactive to active, or from
active to inactive.
7.
3BUA000157R4101
8.
SOE Reports
Set the cache time to that of the cache time defined in the module. The cache
time is the time the SOE information is retained in the cache. All data will be
deleted once the cache time has expired.
SOE Reports
Reports are defined in the Scheduling Structure. There should be one Job
Description for each SOEReport object in the system. First, a job object must be
created to set up and configure an SOE report. This object is created in the
Scheduling Structure, under Schedules and Jobs > Job Descriptions (see
Figure 37, Configuration of SOE Report Job). This contains the Scheduling
Definition aspect.
The Scheduling Definition needs to be configured as an Expression Schedule. The
report can then be triggered by the value of an object property. For SOE reports, this
is the REPORTREAD property of an SOEReport object.
Procedure
1.
2.
Then, select the Schedule field and select Expression Schedule from the drop
down list.
3.
Enter the expression that is the path to the appropriate SOEReport object
REPORTREAD property to initiate the report.
4.
Select Start when TRUE from the Scheduling Mode to initiate the report only
when the expression evaluates to TRUE, Figure 38.
5.
Assign the Service Group to an appropriate group selected from the drop
down list. Reports may be run on a specific node according to your particular
system configuration.
3BUA000157R4101
119
Procedure
The Enabled field must be set in order for reports to be triggered. Reports can also
be triggered manually using the Run Now button, but will only be valid if SOE data
is available as indicated in the SOEReport object faceplate.
TC06648A
TC06649A
120
3BUA000157R4101
Procedure
The Report Action aspect must also be configured to define the input object for the
report and how the report will be retained and optionally printed or archived using
the 800xA Information Manager.
For long-term archival of completed reports, the system must include the 800xA
Information Manager that is configured to archive report data. The 800xA
Information Manager Configuration guide - Section 8 Historizing Reports defines
how this is configured.
Before reports can be historized, you must configure a Report Log using an
appropriate log access name for each report type. The report log access name will
then be used to identify the log to send archived reports to.
6.
Select the Action Aspect (Figure 39) to configure the report action parameters.
Select Report Action from the Action drop down list. If desired, a timeout
value may be specified, but in most situations the default values for the Time
Limit, Isolated, Priority, Attempts and System Messages should be used.
TC06650A
7.
3BUA000157R4101
Next, select the report template to be used. To export a report, click the
Report Template Path button and select the Harmony SOE log template.
The location of this template is shown in Figure 41, Harmony SOE Log
Template Location.
121
Procedure
8.
There is only one Report Parameter to configure, the SOEReport object. Click
Add Parameter and enter TagName in the Name field and the SOEReport
object name in the Value field.
9.
10. Reports are saved on the local system by exporting. Select the Export Paths
option.
11. Then select Add Object Path to save the reports in the Aspect system. These
will be retained under Reports> folder Name (in this example, SoeReport
Folder). These may then be later reviewed and/or printed by any clients on the
system that have Microsoft Excel installed locally (see Figure 8 and Figure 9).
12. If required, output reports can also be saved to a local file folder. Select Add
File Path to configure the output folder and file name.
The print area is predefined in the Excel spreadsheet. This can be modified and
saved in the template if required. This definition is used when the printer option is
selected and configured in the Action Aspect, Figure 40.
TC06651A
122
3BUA000157R4101
13. To save the completed report in a long-term archive, select Save to History and
select the appropriate report log name from the drop down list. Select .xls
format to save in the correct format. The 800xA Information Manager
Operation guide - Section 5 Creating Reports - Save to History defines how
this is configured.
For more information on the scheduler and reports refer to the IndustrialIT 800xA Information Management System Version 3.1 Operation Guide (Section 5 Creating
Reports and Section 6 Scheduling).
TC06652A
3BUA000157R4101
123
SOE Reports of report type pre-fault and post-fault, which are available only with
FC 99, require that the Rochester communication interface unit be specially
configured, to enable it to send pre-fault and post-fault SOE events to Harmony
INFI 90. Each of these report types need a Boolean trigger equation to determine if
and when pre-fault or post-fault trigger situations exist. Also, Rochester SER
Digital points must be specifically designated as pre-fault points and post-fault
points in order to show up in SOE Reports of these particular types.
Then, to designate Rochester SER Digital points to be pre-fault points, use the ISM1 command:
prepoints s <pointnumbers>
The Rochester SER is now ready to report pre-fault reports. In this example, points
21 through 30, plus point 48, are the only Digital points that would show up in the
SER pre-fault SOE Reports.
To remove the pre-fault designation on points 16 through 20, enter:
prepoints r 16-20
124
3BUA000157R4101
Then, to designate Rochester SER Digital points to be post-fault points, use the
ISM-1 command:
postpoints s <pointnumbers>
The Rochester SER is now ready to report post-fault reports. In this example, points
one through 10, plus point 16 are the only Digital points that would show up in the
SER post-fault SOE Reports.
To remove the pre-fault designation on points six through ten, enter:
postpoints r 6-10
3BUA000157R4101
125
psum
126
3BUA000157R4101
System protocol.
System text.
Quality indicators.
Project history.
The system definition object is not subject to Life Cycle management. All
changes to information in this object are directed to the runtime system.
Only one system definition object can be configured in the project. Table 11
describes the system definition object properties.
Table 11. System Definition Object Properties
Properties
Description
Common
Indexed Text
3BUA000157R4101
127
Configurable Text
Description
Substitutable
Text
Quality Text
Configurable Text
Some system text is maintained in the system definition object. This text is used in
the configuration of other objects. The objects refer to this text in their definitions.
The advantage of maintaining them centrally is that if changes are required they can
be done and will be applied to all referring objects. Also, translation to other
languages can be done in one place instead of in every object in the project.
Configurable Text includes Indexed Text and Substitutable Text. These text items
appear in displays as informative text, engineering units, logic state descriptors, and
error indications. System text configuration is performed in two different tabs of the
system definition object:
Indexed text.
Substitutable text.
Event comment.
128
3BUA000157R4101
TC04818A
Click on the Add Text button. An empty text index is added at the bottom of
the table.
2.
3BUA000157R4101
129
3.
Select a Server type. The selection of a Server type assigns the index to that
Server type. This allows multiple text entries for the same index for each type
of Server. Selecting Common makes it available to all Server types.
4.
5.
Click the Submit Changes button to save the information to the Configuration
Server.
Event Comment
An alarm priority can be represented by text. There are 17 alarm priorities. Each
priority can be assigned different priority text including both active and normal state
events. The alarm priorities are shown in Table 12.
Only the default alarm priorities are available. No others can be added.
Table 12. Alarm Priorities
130
Priority
Descriptor
Priority
Descriptor
Priority
Error!
WARNING
DIRE
10
warning
3BUA000157R4101
Descriptor
Priority
Descriptor
dire
11
ADVISE
CRUCIAL
12
advise
crucial
13
NOTIFY
CRITICAL
14
notify
critical
15
INFORM
ALERT
16
inform
alert
Engineering unit descriptors (EUD) relate to Analog signals in the control system.
They describe the unit of measurement (DEG F, GPM, AMPS, LB/HR) for the
Analog signal.
A list of common engineering units is provided. Theoretically, an unlimited number
of engineering unit descriptors can be defined in the database; although, zero
through 15 are fixed. Table 13 lists the fixed engineering unit descriptors and their
index numbers.
For Harmony control systems, the actual reporting of engineering unit descriptors is
done by the controller. The controller sends an EUD index number along with the
process value to identify the unit associated with the value. This index number is
then cross referenced with the database list of descriptors. Since the controller
reports the EUD index number, all devices on a common communication network
should use the same EUD list.
PhaseX Fault Code
This is an error code returned by the PhaseX FC. It describes what went wrong with
a particular phase.
3BUA000157R4101
131
Descriptor
Index
Descriptor
(Blank)
GPM
(Blank)
CFS
10
CFM
DEG F
11
LB/HR
DEG C
12
GAL
PSIA
13
AMPS
PSIG
14
IN HG
IN H2O
15
KLB/HR
Logic state descriptors (LSD) describe logic states for Digital signals. These
descriptors show the current logic state (on or off, zero or one, run or stop, or closed
or open) of a device. A descriptor follows a tag throughout all Harmony INFI 90
functions after being defined for a tag.
A list of common logic state descriptors is provided. Theoretically, an unlimited
number of logic state descriptors can be defined in the database; although, zero
through 15 are fixed. Table 14 lists the fixed logic state descriptors and their index
numbers.
Text Selector Text
Each text message has a unique index number assigned to it. The message can be a
maximum of 80 characters long. Although there are no predefined messages,
message 0 is always blank to allow displays to show no message.
132
3BUA000157R4101
Descriptor
Index
Descriptor
ZERO
LOW
ONE
HIGH
ON
10
EMPTY
OFF
11
FULL
NO
12
RUN
YES
13
STOP
CLOSED
14
TRIP
OPEN
15
(Blank)
TC04555A
Click the item to be edited. This displays a table at the bottom of the window
that has four columns: Value, Text, Default Text, and Description.
2.
Enter the desired text in the text field. The default text remains in the Default
Text column so that the field can be easily returned to default if desired.
3.
3BUA000157R4101
133
TC04554A
Enter the desired character in the Symbol field. The default character remains
in the Default column so that the field can be easily returned to default if
desired.
2.
134
3BUA000157R4101
TC04553A
3BUA000157R4101
135
136
3BUA000157R4101
System Overview
Events are generated by Servers in the system. Event concentrators collect the
events from the Servers and distribute them between the different nodes and make
the event stream accessible for client applications. All client applications can be
configured to be sensitive to a group of events defined by an event filter and applied
to the event stream in the system. Figure 46 is a functional diagram of the Harmony
INFI 90 event system.
The design and implementation of the alarm and event system is closely related to
the OPC definitions for alarms and events. For a clearer understanding, this
instruction refers to the OPC terms where appropriate indicating similarities and
potential differences.
3BUA000157R4101
137
Event Point
Event Point
An event point represents a defined condition in the system. The event point
generates events at the occurrence of a state change of the defined condition. It
maintains its current state in terms of active or inactive, acknowledged or
unacknowledged, inhibited or uninhibited, and enabled or disabled.
Usually an event point exists as part of a tag in a RTDS. The system also provides
the option to maintain transient event points for non tag related events.
Since the event point maintains the various states of a condition, only events
generated by an event point (as opposed to non event point related events) can be
inhibited or disabled.
138
3BUA000157R4101
The similar entity in the OPC definition is a condition. Consider the event point
implementation of Harmony INFI 90 similar to the implementation of the abstract
OPC condition model.
Event Concentrators
In order to minimize system and network load, event concentrators work in a
hierarchical order. Two categories of event concentrators are supported:
Local event concentrators subscribe to the event streams of all Servers running on
the same system node (computer). A local event concentrator needs to be configured
for all nodes in the system that host RTDSs like the Harmony Servers. If not, events
generated from the respective Servers will not be accessible for clients.
Redundancy is handled automatically by the event concentrators; no special
configuration is required.
3BUA000157R4101
139
Event Classifications
Client event concentrators subscribe to the event streams of all local event
concentrators in the system that belong to the same Harmony INFI 90 domain as
they do. A client event concentrator combines the event stream of all local event
concentrators into a complete event stream of the system.
Event Classifications
Events are separated into two classifications:
Alarm.
Status.
Typically alarm events are events that require action to resolve the reason for their
generation. An example of an alarm event is a boiler temperature exceeding a limit.
Status events do not require action to resolve the reason of their generation. An
example of a status event is a motors state changing from on to off. The event is
identified as an alarm or a status in the event point configuration.
140
3BUA000157R4101
Event Categories
Event Categories
Event categories can be used to condense the event state of a tag. Multiple event
points in a tag can belong to the same event category. Event client applications
(event pages and alarm bars) can interpret the event categories and only present the
most important events to an operator instead of all events. This lowers the event
noise to the operator. Some example categories are:
Boolean.
Limit.
Deviation.
Rate.
Behavioral.
Informational.
3BUA000157R4101
141
Description
Name of the source of the event point. Every event
point instance is related to one source. For an event
point defined as part of a tag the source is the tag
name.
Config Property
Yes
EventPointName Identifies the event point inside the source. The event Class1
point name is defined in the class of the tag as the
signal name and is not configurable. The signal name
in combination with the sender name uniquely identifies
the event point: <Source>.<SignalName>.
Yes2
No
NOTES:
1. The configuration is inherited from the class of the object.
2. Only if the event point is defined as part of the tag.
Description
Config Property
SIG
No
Yes
PRI
No
Yes
Class1
Yes
Yes
Yes
SUP
No
Yes
COM
Yes
ALARM
Yes
AREF
142
No
3BUA000157R4101
Description
Config Property
Yes
Behavioral Attributes
Behavioral attributes impact the behavior of the event point in terms of its state
machine and actions processed upon state change. The behavioral attributes are
shown in Table 17.
Table 17. Behavioral Attributes
Attribute
Description
Config Property
ACKR
Yes
EN
Yes
Yes
DUAL
Yes
COMP
Not implemented
3BUA000157R4101
143
Informational Attributes
Informational attributes do not impact the behavior of the event point. They serve to
qualify events generated by the event point to be interpreted by client applications.
The informational attributes are shown in Table 18.
The list in Table 18 represents a complete set of possible configuration attributes.
The actual attributes are dependent on the implementation of the tag type, some
of them are defined by default.
Event points that are not part of a tag are defined by the application generating the
associated events. The configuration of such event points is up to the application
itself.
Table 18. Informational Attributes
Attribute
1
Description
Config
Property
Yes
Yes
EPSCAT
No
Yes
SIG0
Defines the logic state descriptor for the zero state of the
event point. Usually this attribute is defined through
configuration.
Yes
Yes
SIG1
Defines the logic state descriptor for the one state of the event Yes
point. Usually this attribute is defined through configuration.
Yes
PRI0
Yes
Yes
PRI1
Yes
Yes
COM0
Yes
Yes
COM1
Yes
Yes
DESC
144
3BUA000157R4101
Description
Event point represents an alarm (abnormal condition).
Config
Yes
Property
Yes
NOTES:
1. Only if the event point is defined as part of the tag.
Acknowledged.
Active.
Enabled.
Suppressed.
Inhibited.
Acknowledged
An event acknowledgment generates an acknowledge event notification. This
notification contains the event point description, the current event point state, and
the ID of the operator who made the acknowledgment. Figure 48 describes the event
point acknowledgement flow. Harmony INFI 90 supports three different methods
for acknowledging an event:
Tag Acknowledgment.
3BUA000157R4101
145
146
3BUA000157R4101
Most of the event points have dual behavior. Dual events generate event
notifications for active to inactive and inactive to active state transitions. Refer to
Figure 48.
Non Dual Event Point Behavior
Non dual event points have slightly different behavior. Non dual event points only
generate event notifications for inactive to active transitions. They automatically go
inactive when they receive a valid acknowledgment.
3BUA000157R4101
147
148
3BUA000157R4101
3BUA000157R4101
149
Accessing
Accessing
To access the bulk configuration manager, select Start > Programs > ABB
Industrial IT 800xA > 800xA for OCS Systems > Harmony > Configuration >
Bulk Configuration Manager. This action starts Excel and loads the configuration
manager worksheet.
The bulk configuration manager document adds an additional menu item called
Operate IT to the Excel menu bar. The menu provides the commands for
interaction with an Harmony INFI 90 configuration.
150
3BUA000157R4101
Querying Objects
By default, the window uses information in the local registry to determine the
Configuration Server to contact. Use the Advanced button to specify another
computer or website of a running Configuration Server. The selection list will be
repopulated with the projects found at the specified location.
Changing the configuration causes any existing worksheets to be deleted.
Querying Objects
With a project selected, select Operate IT > Query Objects from the menu bar to
query the configuration for data. The query configuration command opens a window
that provides options to specify the data to perform bulk configuration on
(Figure 50). The window supports retrieving information by type.
TC02471B
3BUA000157R4101
151
Displaying Data
2.
Specify the Life Cycle of the data. A selection list displays a list of supported
Life Cycles.
3.
Further filter the data by name by entering a filter string. The filter string can
contain any pattern supported by the T-SQL LIKE operator (refer to T-SQL
LIKE Pattern Syntax on page 158).
4.
Select the desired attributes from the list of possible attributes. Multiple
attributes are selected by using CTRLand SHIFT.
5.
Displaying Data
Once the method of filtering and retrieving data is selected, a new worksheet opens
and the spreadsheet is populated with the data. The first row in the spreadsheet
contains heading information. The name of each attribute retrieved is listed in each
column. The remaining rows are populated with data returned in the query. For each
record, data is placed in the column corresponding to the attribute. An example of
the spreadsheet view is shown in Figure 51.
TC02472A
152
3BUA000157R4101
Insert Object
Insert Object
New database entries can be added using the Insert Object option. One or multiple
objects can be added at a time. To add database entries:
1.
2.
3.
Define the Name Prefix, Separator, and Seed fields for the new objects. New
objects are named and sequentially numbered according to these entries. The
name assigned to the new objects is in the form:
<prefix><separator><seed>
where:
prefix
separator
seed
4.
5.
2.
Select Operate IT > Lock Selected Objects from the menu bar. The selected
objects will be locked and their background color will be changed to white.
3BUA000157R4101
153
Modifying Data
Only the user that locked the objects can modify and unlock them. Any non Design
mode objects or objects that are already locked by another user are considered read
only. In this case, the color of the corresponding row is gray and the row is not
editable. This is sometimes useful for cross reference purposes.
The objects must be unlocked before the spreadsheet is released. If an attempt is
made to close the spreadsheet with locked objects, a notification of the locked
objects will appear. If the objects are not unlocked, they will remain locked in the
Configuration Server after the spreadsheet is closed.
To unlock objects:
1.
2.
Select Operate IT > Unlock Selected Objects from the menu bar. The
selected objects will be unlocked and their background color will be changed to
gray.
Modifying Data
Only query results that have been locked in the configuration can be modified. In a
read only worksheet, the user is only able to move around the spreadsheet and copy
data.
1. Life Cycle changes can only be made if an object is not locked.
2. The bulk configuration manager only supports deleting objects by changing a
Design or Out of Service object to the delete Life Cycle. Removing rows and
columns from the spreadsheet does not delete the object and will cause
unpredictable results.
Individual cells can be edited by changing the data. The user can select a range of
cells (typically within a column) to make many changes. Basically, any feature of
Excel can be utilized, including replace and macros, to modify the data. When a cell
is modified, its color is changed to blue. This gives a visual indication of the
changes.
Certain information, such as relationships, is displayed using the underlying GUID
data. To simplify changes to this data, the bulk configuration manager provides a
method to pick the relationship and have the corresponding GUID information
written into the cell.
154
3BUA000157R4101
2.
Click the search button on the column header. This opens a selection window
with the available changes.
3.
When the bulk configuration manger is online (able to communicate with the
Configuration Server), the window displays information queried directly from the
Configuration Server. When working offline, the window displays information from
a cached copy of this information saved in the workbook at the time when it was
taken offline. Refer to Working in Offline Mode on page 157 for more information.
3BUA000157R4101
155
Refreshing Data
cleared. The original value is retrieved from a hidden worksheet that retains the
original information.
Refreshing Data
The data viewed in the spreadsheet can be refreshed at any time by selecting
Operate IT > Refresh Data from the menu bar. This action queries the
Configuration Server to refresh the data.
2.
3.
4.
5.
Select Life Cycle, Name, and Block attributes from the attribute list.
6.
7.
Click the binocular icon beside the Life Cycle heading. A dialog should appear
that shows all of the Life Cycles.
8.
Select the Design Life Cycle from list, then click OK.
9.
Select Operate IT > Submit Changes. This changes all of the selected records
from Running to Design Life Cycle.
156
3BUA000157R4101
14. Select Operate IT > Unlock Selected Objects from the menu bar.
15. Select the Life Cycle cells in the spreadsheet table.
16. Click the binocular icon beside the LIFECYCLE heading.
17. Select the Running Life Cycle from the list, then click OK.
18. Select Operate IT > Submit Changes from the menu bar.
19. Click Yes to refresh the worksheet.
If for some reason the objects have permanent locks, they can be deleted from the
SymLock table in the Configuration Server database.
Exporting Data
Query results stored in a worksheet can easily be exported to any of the formats
supported by Excel.
Limitations
A query is limited to 65,536 rows of data and 256 columns of attributes. The
number of logged changes is limited to the number of rows and cells that a
worksheet can store (65,536). The number of worksheets containing queried
information is limited by the number of worksheets that Excel can support (limited
by memory). The size of the data stored in the offline xls file is limited to what
Excel can support (four gigabytes).
3BUA000157R4101
157
where:
match_expression Any valid SQL Server expression of
character string data type.
pattern
escape_character
158
Description
Example
[]
[^]
Any single character not within the WHERE au_lname LIKE de[^l]% all
specified range ([^a-f]) or set
author last names beginning with de and
([^abcdef]).
where the following letter is not l.
3BUA000157R4101
Import/Export Configuration
Import/Export Configuration
The import/export configuration tool supports exporting and importing of objects to
and from an intermediate repository. The repository stores exported data in an XML
format that can be easily modified if necessary by third party applications. All
objects except for the system definition object, template objects, and structure
objects can be imported or exported. By default, templates are read only objects.
The tool provides the functions required to move data between configuration
databases. The tool can import and export data between Harmony projects within a
Configuration Server as shown in Figure 52 and between projects from different
Configuration Servers as shown in Figure 53.
3BUA000157R4101
159
Export
The import/export tool exports objects to an intermediate storage called the
repository. Once in the repository, the configuration data can be view and modified.
The tool provides the ability to filter the information to export. For example, a filter
can be applied to select a group of tags that belong to a particular area. The
import/export tool supports all Life Cycles for export.
Care should be taken when making changes to the data in the repository. Any
inconsistency or corruption to the repository can cause an import tool to fail. Data
in the repository can only be modified and not added to or delete from. The tool
does not correct data that has been modified that later imports with errors.
When exporting data to a repository, data can be appended to an existing repository
or to a newly created repository. The appending option allows multiple
configuration databases to be merged into one repository for later importing.
The tool supports exporting all the system defined property types and relationships.
Any relationships to an object are exported. The name of the related object, any user
data, and the relationship type are exported. Similarly, for context menus, any object
references such as overrides and actions are converted to the name of the
corresponding object when exported.
160
3BUA000157R4101
Export
TC04561A
2.
3BUA000157R4101
Select the project or database to export from, define the path and name of the
file (xml) to export to, and then click Next (Figure 56).
161
Export
TC02664A
Click Options to choose Life Cycle options; click OK when finished. This
determines which versions of the selected objects are to be exported. The
options are Running, Release, Design, and user templates.
The standard templates provided cannot be selected for export.
162
4.
Select the objects to export, and then click Next (Figure 57). A check mark
indicates selected. This browser allows displaying objects based on area, unit,
and equipment assignment or by object type or object template.
5.
The export status bar shows the percentage complete. The time it takes to
export data depends on the number of objects selected and the Life Cycles
chosen for export. Click Exit after the dialog shows 100 percent complete.
3BUA000157R4101
Import
TC04560A
Import
The import/export tool imports data to a configuration database. The tool allows
selecting the objects from the repository to be imported.
When objects being imported reference an object that does not exist in the
configuration database, the tool allows specifying whether a new reference should
be created. If enabled, the tool creates the necessary object and connects the link to
that object. The object template to use for the new object can be selected or the
standard templates will be used by default. If disabled, the tool does not create any
object and the reference is set to NULL.
3BUA000157R4101
163
Import
2.
Define the path and name of the file (xml) to import from, select the project or
database to import to, and then click Next (Figure 58).
Currently, the only option for Server is Local.
TC02666A
164
3.
Select the objects to import, and then click Next (Figure 59). A check mark
indicates selected.
4.
3BUA000157R4101
Import
TC02667A
3BUA000157R4101
165
Import
TC04559B
The options exposed by the More/Hide button are not supported. The standard
object templates will be used on object creation.
5.
166
b.
c.
The import status bar shows the percentage complete. The time it takes to
import data depends on the number of objects selected. Click Exit after the
dialog shows 100 percent complete.
3BUA000157R4101
Import
If more than 100 objects are imported, a dialog box will appear asking to restart or
to not restart the affected Servers. If Restart the Affected Servers is chosen, the
changes will not be replicated for the affected Server until it is restarted. If
Automatically is chosen, select the Server to be restarted and it will happen
automatically, but the Server will lose communication while this is performed. If
Manually is chosen, the user may choose to restart the Server at any given time
required, but changes will not be recognized on the Server until it is restarted. When
Do not restart the Server(s) is chosen, the changes will be replicated online to the
Server and may take some time to complete. If the changes are significant, some
performance affect may be visible to the user. Refer to Figure 61.
TC03677A
3BUA000157R4101
167
Import
168
3BUA000157R4101
Associates new Configuration Server tags with the Server referenced by the
parent OPC Control Network object.
Import Options
New tags - Used to import new tags from the Configuration Server.
Tag name/description properties - Used to import the tag name and description
from the Configuration Server.
3BUA000157R4101
169
Export Options
Functional structure objects (Area, Equipment, and Unit) - Used to import the
objects of the Functional Structure from the Configuration Server.
Tag security associations - Used to import the tag associations from the
Configuration Server.
TC04549B
Export Options
170
New tags - Select this to export new tags created in the Aspect Directory to the
Configuration Server.
Tag name / description properties - Select this to export the tag name and
description to the Configuration Server.
3BUA000157R4101
Advanced Tab
Advanced Tab
When the Advanced tab is pressed (Figure 63), it displays selections, which would
not normally be used, unless you are wanting to selectively make changes.
1. For the Advanced features to work correctly and to let you selectively make
changes, you must first disable the Harmony Server Monitor. Refer to Harmony
Server Monitor Object on page 29.
2. When the Harmony Synchronizer is complete, the Harmony Server Monitor
must be reenabled.
TC04550A
Delete Button - This option will delete tags from the Aspect directory if they no
longer exist in the Configuration Server.
Add to structure button (default) - This option will create a reference to the tag
object in the specified functional structure node.
3BUA000157R4101
171
Analyze Tab
Export button - This option will create a corresponding tag in the Configuration
Server by copying a system template of the appropriate tag type, and applying
the name and description of the tag object to the resulting object.
Associate new tags with Area tick box - Select this to insert tags into an associated
area. This could be used to store all tags into a temporary area which all have a
common association.
Analyze Tab
This will create lists of changes that would have been made had the synchronize
button been selected. You can then selectively synchronize parts of the changes.
This would be used as a maintenance type function, where not all changes are
required to be made at one time (Figure 64).
TC04551A
Tags, Tag name / description and Area, Units and Equipment objects fields.
172
3BUA000157R4101
Modifications
Edit Button - Selecting this will display a list of the changes that would be imported
or exported. You can now highlight the changes that you would like to take action
on.
Use the CTRL+C (copy) and CTRL+C (paste) to copy and paste into Notepad or
Excel, for documentation purposes.
Clicking the Apply button in the list will apply the selected changes, just as if the
Synchronize button from the General tab was clicked.
Modifications
Changes to the name and/or description that are made directly in the name aspect of
the Harmony tag object in the Operator Workplace area automatically propagated
back to the Harmony INFI 90 Configuration Server. In some cases, a new version of
the tag object will be created to accommodate the change. since the tag could exist
in one of the several Life Cycles in the Configuration Server, the Harmony
Synchronizer uses the logic shown in Table 20 to determine which Life Cycle
version it will change, and what it does after the change is made.
In some cases, additional action will be required by the user to complete the
change.
Table 20. Life Cycle Modifications
Initial Life Cycles in
the Configuration
Server
Version Modified by
the Harmony
Synchronizer
Subsequent Action
Required by User
Running Only
Release Only
Design Only
None.
3BUA000157R4101
None.
173
Version Modified by
the Harmony
Synchronizer
Subsequent Action
Required by User
None. 1
None. 1
NOTE: Changing the object name in the Design or Release version will prevent the object from operating. This is
because the name in the Running version will be different from the object in the Aspect Directory. In this case,
running the Harmony Synchronizer import changes from the Configuration Server will result in changing the object
name to be that of the Running version. It is recommended that changes made to a Design or Running version be
reviewed for correctness and transferred into the Running Life Cycle. This will ensure that operation is not
interrupted and that no inconsistencies exist between the Configuration and Aspect Server objects.
174
1.
Refer to and perform all steps in the System Domain in the 800xA System
Security Users Guide instruction.
2.
3.
Select Domains.
4.
3BUA000157R4101
5.
6.
7.
8.
When setting the OpParms Permission, select the Allowed check box as
shown in Figure 65.
TC04434A
3BUA000157R4101
175
Operation Overview
The active Harmony INFI 90 Server synchronizes time with the control loop. The
active Harmony Server also broadcasts that time via TSP to all of the Time
Synchronization Daemons (although only the Master Time Synchronization
Daemon will process the message.
The Control Loop Time Synch. Master may be configured elsewhere on the
network, in which case the time will be read from the control loop by the
Harmony Server, and then forwarded to the Time Synch. Daemons.
The Master Time Synchronization Daemon will post the time to all other Time
Synchronization Daemons on the network. If necessary, slewing of time will begin
at a rate of one second adjustment per minute on nodes that need to have their time
adjusted.
The 800xA System Time Server will periodically broadcast the time on the active
(in Service state) Time Server to all Client Time Handlers. If a Client Time Handler
detects a time difference between the Time Servers time and the local time that is
greater than the configured deviation limit, it will attempt to adjust the time on the
local node (by doing a step change to the system time). (Note: under normal
operation, this should only happen on nodes not running the Time Synchronization
Daemon).
When a Connectivity Server node is added to the system, a Time Server service
provider is automatically added to Services > Time, Service > Basic, Service
176
3BUA000157R4101
Operation Overview
Group > Time Basic > <computername> > Service Provider. The service
provider can be configured via the Service Provider Definition aspect. Refer to
Figure 66 as shown below.
TC04435A
3BUA000157R4101
177
Time Synchronization
TC04436A
Time Synchronization
The Connectivity Server or Harmony Server nodes should be configured to allow
Time Synchronization in the Server tags TagConfig aspect. Refer to Figure 68 as
shown below.
If a node other than the Connectivity Server is to act as Time Synchronization
Master on the control loop, then the Accuracy setting should be left as Low
Accuracy Battery on both Servers.
If the Connectivity Server pairs are to act as Time Synchronization master on the
control loop, then the Accuracy setting should be set at some level higher then Low
Accuracy Battery for both nodes, with the primary setting being slightly higher then
the redundant.
In addition, if the node is to act as the default TSP master, then the TSP timesync
priority should be set a number higher than any of the other nodes on the network.
If a node other then Connectivity Servers is to act as the default TSP Time Sync
Master, then the TIMESYNC PRIORITY should be left at the default of 1. The
default is 1 and the range is 1 to 10, where 10 is the highest priority.
The following registry entry should be modified on each Connectivity Server node
as follows:
HKEY_LOCAL_MACHINE\SOFTWARE\ABB\PWC\TIMESYNC_PRIORITY
178
3BUA000157R4101
Time Adjustment
TC04815A
Time Adjustment
A Harmony INFI 90 system time adjust window can be launched from the Windows
2000 start menu (Figure 69) which will allow the user to adjust system time to a
maximum of plus or minus five minutes. To access Time Synchronization click
Start > Programs > ABB Industrial IT 800xA > 800xA for OCS Systems >
Harmony > Set Harmony Time.
3BUA000157R4101
179
TC02713B
180
3BUA000157R4101
Authentication
close the window. These buttons will be dimmed and inactive if the current user
does not have database configuration access.
The Estimated Time Remaining field is the time it will take for the local clock to
adjust to the requested time change. Each time an adjustment is being done, the
Adjust Local Clock Adjustment check box will be selected.
This time adjustment can be initiated from any Harmony Connectivity Server
node on the network.
Authentication
To configure a system for reauthentication or double authentication:
1.
2.
3.
4.
TC05259A
3BUA000157R4101
181
Authentication
The list of Properties displays the available atoms that can be flagged for
reauthentication or double authentication. Only one atom at a time can be selected
to configure.
5.
6.
Select the desired check box in the Flags portion of the window.
Refer to the 800xA for Harmony Operation instruction for more information on
how to operate this function.
182
3BUA000157R4101
The sessions on screen status entries are appended to a backup or restore log
file. The user must manually erase any unwanted entries or Rename/Delete the
log file to start a fresh log. The log file is initially created in the Windows 2000
accounts temporary directory location. The screen form contains a log file icon
that opens the log file in a Notepad application window for viewing, printing,
or editing of the log file.
2.
Function
The Harmony INFI 90 Backup or Restore feature allows the user to manually
initiate a backup or restore that supports either the full backup or full restore of the
SQL Harmony INFI 90 configuration contained in its SQL database. The backup or
restore operation sequences through all steps required to complete the operation
requested.
The user backup process consists of the user selecting an aspect system name and
file location to contain a standard SQL backup set and initiating the backup. The
3BUA000157R4101
183
Backup
user restore process consists of the user selecting an existing SQL backup set
filename and initiating the restore operation.
Backup
Use the following steps to back up an existing configuration:
1.
Select Start > Programs > ABB Industrial IT 800xA > 800xA for OCS
Systems > Harmony > Configuration > Backup Configuration.
2.
3.
The filename is auto generated using the Configuration Server name, date and
time (ConfigServerHC_20020521_1034.bak for example).
Refer to the MSSQL file folders for the .bak files generated upon successful
backup.
4.
The Backup button manually initiates the SQL database backup operation.
Only one single backup is stored per file. If the backup file already exists it is
overwritten.
5.
If completed successfully, the Exit button is activated and the user can then exit
to quit.
Restore
Use the following steps to restore an existing configuration:
184
1.
Restore Configuration is launched from the Start menu. The path is as follows:
Start > Programs > ABB Industrial IT 800xA > 800xA for OCS Systems >
Harmony > Configuration > Restore Configuration.
2.
3BUA000157R4101
Restore
4.
5.
Restore target backup file to the Configuration Server database. The restore
operation overwrites the current database if it exists.
6.
7.
8.
3BUA000157R4101
If completed successfully, Exit button is activated and the user manually exits
the application.
185
Restore
186
3BUA000157R4101
Common.
Common Analog.
Station.
Common Digital.
Device Driver.
Text.
PhaseX.
Module Status.
SOE Report.
Server.
3BUA000157R4101
187
Description
Bool
Boolean.
St
String.
Int
Integer value.
Unit
Date
Date format.
Real
Real value.
Common Properties
The common Harmony properties appear in all Harmony tag types. Table 22 lists
the common properties and includes the data type and a description for each.
Table 22. Common Harmony Properties
Name
188
Type
Description
ALARM
Bool
BAD/ACKR
Bool
Acknowledge required.
BAD/ACT
Bool
Active.
BAD/ALARM
Bool
Alarm state.
BAD/ALMEN
Bool
Alarm event.
BAD/AREF
Bool
Associated value.
BAD/COM
St
BAD/COM0
St
3BUA000157R4101
Common Properties
Type
Description
BAD/COM1
St
BAD/COMP
Bool
BAD/DESCRIPTION
St
Signal description.
BAD/DUAL
Bool
BAD/EN
Bool
Enable.
BAD/EPSCAT
Int
BAD/PRI
Int
BAD/PRI0
St
Normal priority.
BAD/PRI1
St
Active priority.
BAD/SIG
Bool
Boolean value.
BAD/SIG0
St
BAD/SIG1
St
BAD/SUP
Bool
BAD/UNACK
Bool
Unacknowledged alarm.
BAD/UNACKEP
Bool
BLOCK1
Int
CURRENTEP/
UNACK
Bool
DESCRIPTION
St
Description of tag.
DISEST1
Bool
Tag is disestablished.
INHB
Bool
INHBAUTO
Bool
INHBMAN
Bool
3BUA000157R4101
189
Common Properties
Description
INHBTAG
St
INHBVAL
Int
Inhibit value.
LAST_PUT_TIME
St
LOOP
Int
MODULE1
Int
NAME
St
Object name.
NODE
Int
OBJECTID
St
PRI
Int
PTINDEX
Int
QUALITY
Int
Composite quality.
QUALITY:S
St
SERVER
St
SERVERID
St
SPECSRCVD1
Bool
SPECTIMESTAMP1,2 St
SUBSTITUTED1
Bool
SUSPENDED
Bool
Scanning enabled.
TEMPLATEID
St
TYPE
St
TYPEID
St
UNACK
Bool
Unacknowledged alarm.
190
Type
3BUA000157R4101
Type
Description
USERDATA
Unit
USERTEXT
St
XR_COUNT1
Int
NOTES:
1. Not in the HarmServer tag.
2. Not in the HarmAngExport and HarmDigExport
Type
Description
ALMACKBC
Bool
CALIBSTS
Bool
Calibration status.
HIGH/ACKR
Bool
Acknowledge required.
HIGH/ACT
Bool
Active.
HIGH/ALARM
Bool
Alarm state.
HIGH/ALMEN
Bool
Alarm event.
HIGH/AREF
Real
Associated value.
HIGH/COM
St
3BUA000157R4101
191
192
Type
Description
HIGH/COM0
St
HIGH/COM1
St
HIGH/COMP
Bool
HIGH/DESCRIPTION
St
Signal description.
HIGH/DUAL
Bool
HIGH/EN
Bool
Enable.
HIGH/EPSCAT
Int
HIGH/PRI
Int
HIGH/PRI0
St
Normal priority.
HIGH/PRI1
St
Active priority.
HIGH/SIG
Bool
Boolean value.
HIGH/SIG0
St
HIGH/SIG1
St
HIGH/SUP
Bool
HIGH/UNACK
Bool
Unacknowledged alarm.
HIGH/UNACKEP
Bool
HIGHLIM
Real
LEVELALM
Bool
LOW/ACKR
Bool
Acknowledge required.
LOW/ACT
Bool
Active.
LOW/ALARM
Bool
Alarm state.
LOW/ALMEN
Bool
Alarm event.
3BUA000157R4101
Type
Description
LOW/AREF
Real
Associated value.
LOW/COM
St
LOW/COM0
St
LOW/COM1
St
LOW/COMP
Bool
LOW/DESCRIPTION
St
Signal description.
LOW/DUAL
Bool
LOW/EN
Bool
Enable.
LOW/EPSCAT
Int
LOW/PRI
Int
LOW/PRI0
St
Normal priority.
LOW/PRI1
St
Active priority.
LOW/SIG
Bool
Boolean value.
LOW/SIG0
St
LOW/SIG1
St
LOW/SUP
Bool
LOW/UNACK
Bool
Unacknowledged alarm.
LOW/UNACKEP
Bool
LOWLIM
Real
PV/DESCRIPTION St
Signal description.
PV/FOR
Int
Formatting information.
PV/HIGH
Real
3BUA000157R4101
193
Type
Description
PV/LOW
Real
PV/PERCENT
Real
PV/SIG
Real
Analog value.
PV/SIG:QS
St
Quality string.
PV/SPAN
Real
PV/UNITS
St
Engineering units.
194
Type
Description
ALMSUP
Bool
ALMTYPE
Int
ALTINSEL
Bool
AUTO
Bool
Automatic mode.
CNTRREF
Real
COMMQUAL
Bool
CONSTR
Bool
CONSTRPER
Bool
DEVALM
Bool
3BUA000157R4101
Type
Description
FORCEXR
Bool
HARDFAULT
Bool
HI2/ACKR
Bool
Acknowledge required.
HI2/ACT
Bool
Active.
HI2/ALARM
Bool
Alarm state.
HI2/ALMEN
Bool
Alarm event.
HI2/AREF
Real
Associated value.
HI2/COM
St
HI2/COM0
St
HI2/COM1
St
HI2/COMP
Bool
HI2/DESCRIPTION
St
Signal description.
HI2/DUAL
Bool
HI2/EN
Bool
Enable.
HI2/EPSCAT
Int
HI2/PRI
Int
HI2/PRI0
St
Normal priority.
HI2/PRI1
St
Active priority.
HI2/SIG
Bool
Boolean value.
HI2/SIG0
St
HI2/SIG1
St
HI2/SUP
Bool
3BUA000157R4101
195
196
Type
Description
HI2/UNACK
Bool
Unacknowledged alarm.
HI2/UNACKEP
Bool
HI3/ACKR
Bool
Acknowledge required.
HI3/ACT
Bool
Active.
HI3/ALARM
Bool
Alarm state.
HI3/ALMEN
Bool
Alarm event.
HI3/AREF
Real
Associated value.
HI3/COM
St
HI3/COM0
St
HI3/COM1
St
HI3/COMP
Bool
HI3/DESCRIPTION
St
Signal description.
HI3/DUAL
Bool
HI3/EN
Bool
Enable.
HI3/EPSCAT
Int
HI3/PRI
Int
HI3/PRI0
St
Normal priority.
HI3/PRI1
St
Active priority.
HI3/SIG
Bool
Boolean value.
HI3/SIG0
St
HI3/SIG1
St
HI3/SUP
Bool
3BUA000157R4101
Type
Description
HI3/UNACK
Bool
Unacknowledged alarm.
HI3/UNACKEP
Bool
HICONSTRLMT
Real
HIGHDEV/ACKR
Bool
Acknowledge required.
HIGHDEV/ACT
Bool
Active.
HIGHDEV/ALARM
Bool
Alarm state.
HIGHDEV/ALMEN
Bool
Alarm event.
HIGHDEV/AREF
Real
Associated value.
HIGHDEV/COM
St
HIGHDEV/COM0
St
HIGHDEV/COM1
St
HIGHDEV/COMP
Bool
HIGHDEV/DESCRIPTION
St
Signal description.
HIGHDEV/DUAL
Bool
HIGHDEV/EN
Bool
Enable.
HIGHDEV/EPSCAT
Int
HIGHDEV/PRI
Int
HIGHDEV/PRI0
St
Normal priority.
HIGHDEV/PRI1
St
Active priority.
HIGHDEV/SIG
Bool
Boolean value.
HIGHDEV/SIG0
St
HIGHDEV/SIG1
St
3BUA000157R4101
197
198
Type
Description
HIGHDEV/SUP
Bool
HIGHDEV/UNACK
Bool
Unacknowledged alarm.
HIGHDEV/UNACKEP
Bool
HIGHRATE/ACKR
Bool
Acknowledge required.
HIGHRATE/ACT
Bool
Active.
HIGHRATE/ALARM
Bool
Alarm state.
HIGHRATE/ALMEN
Bool
Alarm event.
HIGHRATE/AREF
Real
Associated value.
HIGHRATE/COM
St
HIGHRATE/COM0
St
HIGHRATE/COM1
St
HIGHRATE/COMP
Bool
HIGHRATE/DESCRIP- St
TION
Signal description.
HIGHRATE/DUAL
Bool
HIGHRATE/EN
Bool
Enable.
HIGHRATE/EPSCAT
Int
HIGHRATE/PACK
Bool
HIGHRATE/PRI
Int
HIGHRATE/PRI0
Int
Normal priority.
HIGHRATE/PRI1
Int
Active priority.
HIGHRATE/SIG
Bool
Boolean value.
HIGHRATE/SIG0
St
3BUA000157R4101
Type
Description
HIGHRATE/SIG1
St
HIGHRATE/SUP
Bool
HIGHRATE/UNACK
Bool
Unacknowledged alarm.
HIGHRATE/UNACKEP Bool
HIREF
Real
LO2/ACKR
Bool
Acknowledge required.
LO2/ACT
Bool
Active.
LO2/ALARM
Bool
Alarm state.
LO2/ALMEN
Bool
Alarm event.
LO2/AREF
Real
Associated value.
LO2/COM
St
LO2/COM0
St
LO2/COM1
St
LO2/COMP
Bool
LO2/DESCRIPTION
St
Signal description.
LO2/DUAL
Bool
LO2/EN
Bool
Enable.
LO2/EPSCAT
Int
LO2/PRI
Int
LO2/PRI0
St
Normal priority.
LO2/PRI1
St
Active priority.
LO2/SIG
Bool
Boolean value.
3BUA000157R4101
199
200
Type
Description
LO2/SIG0
St
LO2/SIG1
St
LO2/SUP
Bool
LO2/UNACK
Bool
Unacknowledged alarm.
LO2/UNACKEP
Bool
LO3/ACKR
Bool
Acknowledge required.
LO3/ACT
Bool
Active.
LO3/ALARM
Bool
Alarm state.
LO3/ALMEN
Bool
Alarm event.
LO3/AREF
Real
Associated value.
LO3/COM
St
LO3/COM0
St
LO3/COM1
St
LO3/COMP
Bool
LO3/DESCRIPTION
St
Signal description.
LO3/DUAL
Bool
LO3/EN
Bool
Enable.
LO3/EPSCAT
Int
LO3/PRI
Int
LO3/PRI0
St
Normal priority.
LO3/PRI1
St
Active priority.
LO3/SIG
Bool
Boolean value.
3BUA000157R4101
Type
Description
LO3/SIG0
St
LO3/SIG1
St
LO3/SUP
Bool
LO3/UNACK
Bool
Unacknowledged alarm.
LO3/UNACKEP
Bool
LOCONSTRLMT
Real
LOREF
Real
LOWDEV/ACKR
Bool
Acknowledge required.
LOWDEV/ACT
Bool
Active.
LOWDEV/ALARM
Bool
Alarm state.
LOWDEV/ALMEN
Bool
Alarm event.
LOWDEV/AREF
Real
Associated value.
LOWDEV/COM
St
LOWDEV/COM0
St
LOWDEV/COM1
St
LOWDEV/COMP
Bool
LOWDEV/DESCRIPTION
St
Signal description.
LOWDEV/DUAL
Bool
LOWDEV/EN
Bool
Enable.
LOWDEV/EPSCAT
Int
LOWDEV/PRI
Int
LOWDEV/PRI0
St
Normal priority.
3BUA000157R4101
201
202
Type
Description
LOWDEV/PRI1
St
Active priority.
LOWDEV/SIG
Bool
Boolean value.
LOWDEV/SIG0
St
LOWDEV/SIG1
St
LOWDEV/SUP
Bool
LOWDEV/UNACK
Bool
Unacknowledged alarm.
LOWDEV/UNACKEP
Bool
LOWRATE/ACKR
Bool
Acknowledge required.
LOWRATE/ACT
Bool
Active.
LOWRATE/ALARM
Bool
Alarm state.
LOWRATE/ALMEN
Bool
Alarm event.
LOWRATE/AREF
Real
Associated value.
LOWRATE/COM
St
LOWRATE/COM0
St
LOWRATE/COM1
St
LOWRATE/COMP
Bool
LOWRATE/DESCRIPTION
St
Signal description.
LOWRATE/DUAL
Bool
LOWRATE/EN
Bool
Enable.
LOWRATE/EPSCAT
Int
LOWRATE/PRI
Int
LOWRATE/PRI0
St
Normal priority.
3BUA000157R4101
Type
Description
LOWRATE/PRI1
St
Active priority.
LOWRATE/SIG
Bool
Boolean value.
LOWRATE/SIG0
St
LOWRATE/SIG1
St
LOWRATE/SUP
Bool
LOWRATE/UNACK
Bool
Unacknowledged alarm.
LOWRATE/UNACKEP
Bool
MULTLVL
Bool
NOREPORT
Bool
NXTHILMT
Real
NXTLOLMT
Real
OUTRANGE
Bool
PERINSEL
Bool
QUALOVR
Bool
RATEALM
Bool
REALM
Bool
REDTAG/ACT
Bool
REDTAG/KEY1
St
REDTAG/KEY2
St
REDTAG/KEY3
St
SRC
Int
3BUA000157R4101
203
Type
Description
USERVAL
Real
VARALM
Bool
204
Type
Description
AUTO
Bool
Override enable.
CONFERR
Int
Configuration error.
CURRLEN
Int
EUCHG
Real
EXTRANGE
Int
External range.
INPTYPE
Int
Input type.
LABEL
St
Channel label.
ORIGLEN
Int
OVRENBL
Bool
Override enabled.
OVRVAL
Real
Override value.
PROPQUAL
Int
Propagated quality.
RANGE
Int
RDBKSTS
Int
3BUA000157R4101
Type
Description
REFSTS
Int
Reference status.
SEIMODE
Int
SIM
Bool
Simulation enable.
SIMBLK
Int
SUSPERR
Int
Suspect error.
TRUNC
Bool
Type
Description
AUTO
Bool
Override enable.
CONFERR
Int
Configuration error.
CURRLEN
Int
EUCHG
Real
EXTRANGE
Int
External range.
LABEL
St
Channel label.
ORIGLEN
Int
OVRENBL
Bool
Override enabled.
OVRVAL
Real
Override value.
PROPQUAL
Int
Propagated quality.
RANGE
Int
RDBKSTS
Int
REFSTS
Int
Reference status.
3BUA000157R4101
205
Station Properties
Type
Description
SEIMODE
Int
SIM
Bool
Simulation enable.
SIMBLK
Int
SUSPERR
Int
Suspect error.
TRUNC
Bool
Station Properties
The Harmony Station tag contains all the properties listed in Table 23 and Table 27.
Table 27. Station Properties (HarmStation)
Name
206
Type
Description
AUTO
Bool
Station mode.
BYPASS
Bool
CMPTRSTS
Bool
CO/DESCRIPTION
St
Signal description.
CO/FOR
Int
Formatting information.
CO/HIGH
Real
CO/LOW
Real
CO/PERCENT
Real
CO/SIG
Real
Analog value.
CO/SIG:QS
St
Quality string.
CO/SPAN
Real
CO/UNITS
St
Engineering units.
3BUA000157R4101
Station Properties
Type
Bool
Description
Deviation alarm summary.
DEVLIM/DESCRIPTION St
Signal description.
DEVLIM/FOR
Int
Formatting information.
DEVLIM/HIGH
Real
DEVLIM/LOW
Real
DEVLIM/PERCENT
Real
DEVLIM/SIG
Real
Analog value.
DEVLIM/SPAN
Real
DEVLIM/UNITS
St
Engineering units.
HIGHDEV/ACKR
Bool
Acknowledge required.
HIGHDEV/ACT
Bool
Active.
HIGHDEV/ALARM
Bool
Alarm state.
HIGHDEV/ALMEN
Bool
Alarm event.
HIGHDEV/AREF
Real
Associated value.
HIGHDEV/COM
St
HIGHDEV/COM0
St
HIGHDEV/COM1
St
HIGHDEV/COMP
Bool
HIGHDEV/DESCRIPTION
St
Signal description.
HIGHDEV/DUAL
Bool
HIGHDEV/EN
Bool
Enable.
HIGHDEV/EPSCAT
Int
3BUA000157R4101
207
Station Properties
208
Type
Description
HIGHDEV/PRI
Int
HIGHDEV/PRI0
St
Normal priority.
HIGHDEV/PRI1
St
Active priority.
HIGHDEV/SIG
Bool
Boolean value.
HIGHDEV/SIG0
St
HIGHDEV/SIG1
St
HIGHDEV/SUP
Bool
HIGHDEV/UNACK
Bool
Unacknowledged alarm.
HIGHDEV/UNACKEP
Bool
LOWDEV/ACKR
Bool
Acknowledge required.
LOWDEV/ACT
Bool
Active.
LOWDEV/ALARM
Bool
Alarm state.
LOWDEV/ALMEN
Bool
Alarm event.
LOWDEV/AREF
Real
Associated value.
LOWDEV/COM
St
LOWDEV/COM0
St
LOWDEV/COM1
St
LOWDEV/COMP
Bool
LOWDEV/DESCRIPTION
St
Signal description.
LOWDEV/DUAL
Bool
LOWDEV/EN
Bool
Enable.
LOWDEV/EPSCAT
Int
3BUA000157R4101
Station Properties
Type
Description
LOWDEV/PRI
Int
LOWDEV/PRI0
St
Normal priority.
LOWDEV/PRI1
St
Active priority.
LOWDEV/SIG
Bool
Boolean value.
LOWDEV/SIG0
St
LOWDEV/SIG1
St
LOWDEV/SUP
Bool
LOWDEV/UNACK
Bool
Unacknowledged alarm.
LOWDEV/UNACKEP
Bool
MODELOCK
Bool
OUTSTS
Bool
OUTTRACKING
Bool
RATIO
Real
Ratio index.
RATIO:QS
St
Quality string.
REDTAG/ACT
Bool
REDTAG/KEY1
St
REDTAG/KEY2
St
REDTAG/KEY3
St
SP/DESCRIPTION
St
Signal description.
SP/FOR
Int
Formatting information.
SP/HIGH
Real
SP/LOW
Real
3BUA000157R4101
209
Type
Description
SP/PERCENT
Real
SP/SIG
Real
Analog value.
SP/SIG:QS
St
Quality string.
SP/SPAN
Real
SP/UNITS
St
Engineering units.
SPTRACKING
Bool
STNLVL
Bool
STNMODE
Bool
STNTYPE
UInt
Station type.
STNTYPE:S
St
TUNEBLK
Int
210
Type
Description
ALMACKBC
Bool
OPHILM
Real
OPLOLM
Real
PV/DESCRIPTION St
Signal description.
PV/FOR
Int
Formatting information.
PV/HIGH
Real
3BUA000157R4101
Type
Description
PV/LOW
Real
PV/PERCENT
Real
PV/SIG
Real
Analog value.
PV/SIG:QS
St
Quality string.
PV/SPAN
Real
PV/UNITS
St
Engineering units.
TRACKING
Bool
Type
Description
ALMACKBC
Bool
OUT/ACKR
Bool
Acknowledge required.
OUT/ACT
Bool
Active.
OUT/ALARM
Bool
Alarm state.
OUT/ALMEN
Bool
Alarm event.
OUT/AREF
Bool
Associated value.
OUT/COM
St
3BUA000157R4101
211
212
Type
Description
OUT/COM0
St
OUT/COM1
St
OUT/COMP
Bool
OUT/DESCRIPTION
St
Signal description.
OUT/DUAL
Bool
OUT/EN
Bool
Enable.
OUT/EPSCAT
Int
OUT/PRI
Int
OUT/PRI0
St
Normal priority.
OUT/PRI1
St
Active priority.
OUT/SIG
Bool
Boolean value.
OUT/SIG0
St
OUT/SIG1
St
OUT/SUP
Bool
OUT/UNACK
Bool
Unacknowledged alarm.
OUT/UNACKEP
Bool
STATECHANGE/ACKR
Bool
Acknowledge required.
STATECHANGE/ACT
Bool
Active.
STATECHANGE/ALARM
Bool
Alarm state.
STATECHANGE/ALMEN
Bool
Alarm event.
STATECHANGE/AREF
Bool
Associated value.
STATECHANGE/COM
St
3BUA000157R4101
Type
Description
STATECHANGE/COM0
St
STATECHANGE/COM1
St
STATECHANGE/COMP
Bool
STATECHANGE/DESCRIP- St
TION
Signal description.
STATECHANGE/DUAL
Bool
STATECHANGE/EN
Bool
Enable.
STATECHANGE/EPSCAT
Int
STATECHANGE/PRI
Int
STATECHANGE/PRI0
St
Normal priority.
STATECHANGE/PRI1
St
Active priority.
STATECHANGE/SIG
Bool
Boolean value.
STATECHANGE/SIG0
St
STATECHANGE/SIG1
St
STATECHANGE/SUP
Bool
STATECHANGE/UNACK
Bool
Unacknowledged alarm.
STATECHANGE/UNACKEP Bool
3BUA000157R4101
213
214
Type
Description
ALMSUP
Bool
ALTINSEL
Bool
AUTO
Bool
Automatic mode.
FORCEXR
Bool
LATCHED
Bool
NOREPORT
Bool
OUTRANGE
Bool
PERINSEL
Bool
QUALOVR
Bool
REALM
Bool
REDTAG/ACT
Bool
REDTAG/KEY1
St
REDTAG/KEY2
St
REDTAG/KEY3
St
SRC
Int
SRC:S
St
USERTYPE
Int
3BUA000157R4101
Type
Description
AUTO
Bool
Automatic mode.
FB1/COMP
Bool
FB1/DESCRIPTION
St
Signal description.
FB1/SIG
Bool
Boolean value.
FB1/SIG0
St
FB1/SIG1
St
FB2/COMP
Bool
FB2/DESCRIPTION
St
Signal description.
FB2/SIG
Bool
Boolean value.
FB2/SIG0
St
FB2/SIG1
St
FBSTS
Bool
REDTAG/ACT
Bool
REDTAG/KEY1
St
REDTAG/KEY2
St
REDTAG/KEY3
St
REMOTE
Bool
Remote mode.
STATUS_OVR
Bool
Status overridden.
USERTYPE
Int
3BUA000157R4101
215
Type
Description
AUTO
Bool
Override enable.
CONFERR
Int
Configuration error.
CURRLEN
Int
LABEL
St
Channel label.
ORIGLEN
Int
OVRENBL
Bool
Override enable.
OVRVAL
Int
Override value.
PROPQUAL
Int
Propagated quality.
RANGE
Int
RDBKSTS
Int
SEIMODE
Int
SIM
Bool
Simulation enable.
SIMBLK
Int
SUSPERR
Int
Suspect error.
TRUNC
Bool
216
3BUA000157R4101
Type
Description
AUTO
Bool
Override enable.
CONFERR
Int
Configuration error.
CURRLEN
Int
LABEL
St
Channel label.
ORIGLEN
Int
OVRENBL
Bool
Override enable.
OVRVAL
Int
Override value.
PROPQUAL
Int
Propagated quality
RANGE
Int
RDBKSTS
Int
SEIMODE
Int
SIM
Bool
Simulation enable.
SIMBLK
Int
SUSPERR
Int
Suspect error.
TRUNC
Bool
Type
Description
AUTO
Bool
Automatic mode.
CNTRL_OVR
Bool
Control is overridden.
FB1/COMP
Bool
FB1/DESCRIPTION
St
Signal description.
3BUA000157R4101
217
218
Type
Description
FB1/SIG
Bool
Boolean value.
FB1/SIG0
St
FB1/SIG1
St
FB2/COMP
Bool
FB2/DESCRIPTION
St
Signal description.
FB2/SIG
Bool
Boolean value.
FB2/SIG0
St
FB2/SIG1
St
FB3/COMP
Bool
FB3/DESCRIPTION
St
Signal description.
FB3/SIG
Bool
Boolean value.
FB3/SIG0
St
FB3/SIG1
St
FB4/COMP
Bool
FB4/DESCRIPTION
St
Signal description.
FB4/SIG
Bool
Boolean value.
FB4/SIG0
St
FB4/SIG1
St
LASTGOOD
Int
LASTGOOD:S
St
LS0
St
LS1
St
LS2
St
3BUA000157R4101
Type
Description
LS3
St
REDTAG/ACT
Bool
REDTAG/KEY1
St
REDTAG/KEY2
St
REDTAG/KEY3
St
SP
Int
Requested state.
STATUS_OVR
Bool
Status overridden.
USERTYPE
Int
Type
Description
FB1/COMP
Bool
FB1/DESCRIPTION
St
Signal description.
FB1/SIG
Bool
Boolean value.
FB1/SIG0
St
FB1/SIG1
St
OUTOVR
Bool
State is overridden.
REDTAG/ACT
Bool
REDTAG/KEY1
St
3BUA000157R4101
219
Type
Description
REDTAG/KEY2
St
REDTAG/KEY3
St
RESCMD
Bool
RESIN
Bool
SETCMD
Bool
SETIN
Bool
SETPER
Bool
Set permissive.
USERTYPE
Int
220
Type
Description
ERRCODE
Int
ERRCODE:S
St
FAULT
Bool
FB1/COMP
Bool
FB1/DESCRIPTION
St
Signal description.
FB1/SIG
Bool
Boolean value.
FB1/SIG0
St
FB1/SIG1
St
3BUA000157R4101
Type
Description
FB2/COMP
Bool
FB2/DESCRIPTION
St
Signal description.
FB2/SIG
Bool
Boolean value.
FB2/SIG0
St
FB2/SIG1
St
REDTAG/ACT
Bool
REDTAG/KEY1
St
REDTAG/KEY2
St
REDTAG/KEY3
St
STARTPM1/COMP
Bool
STARTPM1/DESCRIPTION
St
Signal description.
STARTPM1/SIG
Bool
Boolean value.
STARTPM1/SIG0
St
STARTPM1/SIG1
St
STARTPM2/COMP
Bool
STARTPM2/DESCRIPTION
St
Signal description.
STARTPM2/SIG
Bool
Boolean value.
STARTPM2/SIG0
St
STARTPM2/SIG1
St
STATECHANGE/ACKR
Bool
Acknowledge required.
TXTSET
Int
USERTYPE
Int
3BUA000157R4101
221
222
Type
Description
ALMACKBC
Bool
HIGH/ACKR
Bool
Acknowledge required.
HIGH/ACT
Bool
Active.
HIGH/ALARM
Bool
Alarm state.
HIGH/ALMEN
Bool
Alarm event.
HIGH/AREF
Real
Associated value.
HIGH/COM
St
HIGH/COM0
St
HIGH/COM1
St
HIGH/COMP
Bool
HIGH/DESCRIPTION
St
Signal description.
HIGH/DUAL
Bool
HIGH/EN
Bool
Enable.
HIGH/EPSCAT
Int
HIGH/PRI
Int
HIGH/PRI0
St
Normal priority.
HIGH/PRI1
St
Active priority.
HIGH/SIG
Bool
Boolean value.
3BUA000157R4101
Type
Description
HIGH/SIG0
St
HIGH/SIG1
St
HIGH/SUP
Bool
HIGH/UNACK
Bool
Unacknowledged alarm.
HIGH/UNACKEP
Bool
HIGHLIM
Real
ICI_INDEX
Int
LOW/ACKR
Bool
Acknowledge required.
LOW/ACT
Bool
Active.
LOW/ALARM
Bool
Alarm state.
LOW/ALMEN
Bool
Alarm event.
LOW/AREF
Real
Associated value.
LOW/COM
St
LOW/COM0
St
LOW/COM1
St
LOW/COMP
Bool
LOW/DESCRIPTION
St
Signal description.
LOW/DUAL
Bool
LOW/EN
Bool
Enable.
LOW/EPSCAT
Int
LOW/PRI
Int
LOW/PRI0
St
Normal priority.
3BUA000157R4101
223
Text Properties
Type
Description
LOW/PRI1
St
Active priority.
LOW/SIG
Bool
Boolean value.
LOW/SIG0
St
LOW/SIG1
St
LOW/SUP
Bool
LOW/UNACK
Bool
Unacknowledged alarm.
LOW/UNACKEP
Bool
LOWLIM
Real
PV/DESCRIPTION
St
Signal description.
PV/FOR
Int
Formatting information.
PV/HIGH
Real
PV/LOW
Real
PV/PERCENT
Real
PV/SIG
Real
Analog value.
PV/SIG:QS
St
Quality string.
PV/SPAN
Real
PV/UNITS
St
Engineering units.
Text Properties
The Harmony Text tags are the ASCII and the Text Selector tag. The properties for
the ASCII tag are provided in Table 23 and Table 39. The properties for the Text
Selector tag are provided in Table 23 and Table 40.
224
3BUA000157R4101
Text Properties
Type
Description
ALMACKBC
Bool
ICI_INDEX
Int
OUT/ACKR
Bool
Acknowledge required.
OUT/ACT
Bool
Active.
OUT/ALARM
Bool
Alarm state.
OUT/ALMEN
Bool
Alarm event.
OUT/AREF
Bool
Associated value.
OUT/COM
St
OUT/COM0
St
OUT/COM1
St
OUT/COMP
Bool
OUT/DESCRIPTION
St
Signal description.
OUT/DUAL
Bool
OUT/EN
Bool
Enable.
OUT/EPSCAT
Int
OUT/PRI
Int
OUT/PRI0
St
Normal priority.
OUT/PRI1
St
Active priority.
OUT/SIG
Bool
Boolean value.
OUT/SIG0
St
OUT/SIG1
St
3BUA000157R4101
225
Text Properties
226
Type
Description
OUT/SUP
Bool
OUT/UNACK
Bool
Unacknowledged alarm.
OUT/UNACKEP
Bool
STATECHANGE/ACKR
Bool
Acknowledge required.
STATECHANGE/ACT
Bool
Active.
STATECHANGE/ALARM
Bool
Alarm state.
STATECHANGE/ALMEN
Bool
Alarm event.
STATECHANGE/AREF
Bool
Associated value.
STATECHANGE/COM
St
STATECHANGE/COM0
St
STATECHANGE/COM1
St
STATECHANGE/COMP
Bool
STATECHANGE/DESCRIP- St
TION
Signal description.
STATECHANGE/DUAL
Bool
STATECHANGE/EN
Bool
Enable.
STATECHANGE/EPSCAT
Int
STATECHANGE/PRI
Int
STATECHANGE/PRI0
St
Normal priority.
STATECHANGE/PRI1
St
Active priority.
STATECHANGE/SIG
Bool
Boolean value.
STATECHANGE/SIG0
St
3BUA000157R4101
Text Properties
Type
Description
STATECHANGE/SIG1
St
STATECHANGE/SUP
Bool
STATECHANGE/UNACK
Bool
Unacknowledged alarm.
STATECHANGE/UNACKEP Bool
Type
Description
ALM/ACKR
Bool
Acknowledge required.
ALM/ACT
Bool
Active.
ALM/ALARM
Bool
Alarm state.
ALM/ALMEN
Bool
Alarm event.
ALM/AREF
Bool
Associated value.
ALM/COM
St
ALM/COM0
St
ALM/COM1
St
ALM/COMP
Bool
ALM/DESCRIPTION
St
Signal description.
ALM/DUAL
Bool
ALM/EN
Bool
Enable.
ALM/EPSCAT
Int
ALM/PRI
Int
ALM/PRI0
St
Normal priority.
3BUA000157R4101
227
Text Properties
228
Type
Description
ALM/PRI1
St
Active priority.
ALM/SIG
Bool
Boolean value.
ALM/SIG0
St
ALM/SIG1
St
ALM/SUP
Bool
ALM/UNACK
Bool
Unacknowledged alarm.
ALM/UNACKEP
Bool
ALMACKBC
Bool
ALMSUP
Bool
AUTO
Bool
Automatic mode.
BLKLEN
Int
CNTRLPER
Bool
LEN
Int
LOCTRUNC
Bool
MODELOCK
Bool
NAK
Bool
ORIGLEN
Int
PDT_ECHO
Bool
QUALOVR
Bool
RCV_LEN
Int
REALM
Bool
Periodically realarm.
REDTAG/ACT
Bool
REDTAG/KEY1
St
3BUA000157R4101
Text Properties
Type
Description
REDTAG/KEY2
St
REDTAG/KEY3
St
SEQ_NUM
Int
SET_PRIO
Int
SIG
St
STR_LOCK
Bool
TRUNC
Bool
Type
Description
ALMACKBC
Bool
BLINK
Bool
COLOR
Int
MSG
Int
Current text.
MSG:S
St
3BUA000157R4101
229
230
Type
Description
ALARM:N
Int
ALMACKBC
Bool
BACKUP_STS
Bool
HEX_BYTES
St
ICI_TYPE
Bool
LOCIOSTS
Bool
MODERR
Bool
MODMODE
Int
Module mode.
MODMODE:S
St
MODREV
Int
MODTYPE
Int
MODTYPE:S
St
MODVER
Int
NCOMMERR/ACKR
Bool
Acknowledge required.
NCOMMERR/ACT
Bool
Active.
NCOMMERR/ALARM
Bool
Alarm state.
NCOMMERR/ALMEN
Bool
Alarm event.
NCOMMERR/AREF
Bool
Associated value.
NCOMMERR/COM
St
3BUA000157R4101
Type
Description
NCOMMERR/COM0
St
NCOMMERR/COM1
St
NCOMMERR/COMP
Bool
NCOMMERR/DESCRIPTION
St
Signal description.
NCOMMERR/DUAL
Bool
NCOMMERR/EN
Bool
Enable.
NCOMMERR/EPSCAT
Int
NCOMMERR/PRI
Int
NCOMMERR/PRI0
St
Normal priority.
NCOMMERR/PRI1
St
Active priority.
NCOMMERR/SIG
Bool
Boolean value.
NCOMMERR/SIG:TS
Date
Timestamp.
NCOMMERR/SIG0
St
NCOMMERR/SIG1
St
NCOMMERR/SUP
Bool
NCOMMERR/UNACK
Bool
Unacknowledged alarm.
NCOMMERR/UNACKEP
Bool
NMODERR/ACKR
Bool
Acknowledge required.
NMODERR/ACT
Bool
Active.
NMODERR/ALARM
Bool
Alarm state.
NMODERR/ALMEN
Bool
Alarm event.
3BUA000157R4101
231
232
Type
Description
NMODERR/AREF
Bool
Associated value.
NMODERR/COM
St
NMODERR/COM0
St
NMODERR/COM1
St
NMODERR/COMP
Bool
NMODERR/DESCRIPTION
St
Signal description.
NMODERR/DUAL
Bool
NMODERR/EN
Bool
Enable.
NMODERR/EPSCAT
Int
NMODERR/PRI
Int
NMODERR/PRI0
St
Normal priority.
NMODERR/PRI1
St
Active priority.
NMODERR/SIG
Bool
Boolean value.
NMODERR/SIG0
St
NMODERR/SIG1
St
NMODERR/SUP
Bool
NMODERR/UNACK
Bool
Unacknowledged alarm.
NMODERR/UNACKEP
Bool
NODE_TYPE
Int
NOFFLINE/ACKR
Bool
Acknowledge required.
NOFFLINE/ACT
Bool
Active.
NOFFLINE/ALARM
Bool
Alarm state.
3BUA000157R4101
Type
Description
NOFFLINE/ALMEN
Bool
Alarm event.
NOFFLINE/AREF
Bool
Associated value.
NOFFLINE/COM
St
NOFFLINE/COM0
St
NOFFLINE/COM1
St
NOFFLINE/COMP
Bool
NOFFLINE/DESCRIPTION
St
Signal description.
NOFFLINE/DUAL
Bool
NOFFLINE/EN
Bool
Enable.
NOFFLINE/EPSCAT
Int
NOFFLINE/PRI
Int
NOFFLINE/PRI0
St
Normal priority.
NOFFLINE/PRI1
St
Active priority.
NOFFLINE/SIG
Bool
Boolean value.
NOFFLINE/SIG0
St
NOFFLINE/SIG1
St
NOFFLINE/SUP
Bool
NOFFLINE/UNACK
Bool
Unacknowledged alarm.
NOFFLINE/UNACKEP
Bool
NSYSERR/ACKR
Bool
Acknowledge required.
NSYSERR/ACT
Bool
Active.
NSYSERR/ALARM
Bool
Alarm state.
3BUA000157R4101
233
234
Type
Description
NSYSERR/ALMEN
Bool
Alarm event.
NSYSERR/AREF
Bool
Associated value.
NSYSERR/COM
St
NSYSERR/COM0
St
NSYSERR/COM1
St
NSYSERR/COMP
Bool
NSYSERR/DESCRIPTION
St
Signal description.
NSYSERR/DUAL
Bool
NSYSERR/EN
Bool
Enable.
NSYSERR/EPSCAT
Int
NSYSERR/PRI
Int
NSYSERR/PRI0
St
Normal priority.
NSYSERR/PRI1
St
Active priority.
NSYSERR/SIG
Bool
Boolean value.
NSYSERR/SIG0
St
NSYSERR/SIG1
St
NSYSERR/SUP
Bool
NSYSERR/UNACK
Bool
Unacknowledged alarm.
NSYSERR/UNACKEP
Bool
REMIO_STS
Bool
SECONDARY
Bool
3BUA000157R4101
Type
Description
SPECSRCVD
Bool
SPECTIMESTAMP
St
STATECHANGE/ACKR
Bool
Acknowledge required.
STATECHANGE/ACT
Bool
Active.
STATECHANGE/ALARM
Bool
Alarm state.
STATECHANGE/ALMEN
Bool
Alarm event.
STATECHANGE/AREF
Bool
Associated value.
STATECHANGE/COM
St
STATECHANGE/COM0
St
STATECHANGE/COM1
St
STATECHANGE/COMP
Bool
STATECHANGE/DESCRIPTION
St
Signal description.
STATECHANGE/DUAL
Bool
STATECHANGE/EN
Bool
Enable.
STATECHANGE/EPSCAT
Int
STATECHANGE/PRI
Int
STATECHANGE/PRI0
St
Normal priority.
STATECHANGE/PRI1
St
Active priority.
STATECHANGE/SIG
Bool
Boolean value.
STATECHANGE/SIG0
St
STATECHANGE/SIG1
St
3BUA000157R4101
235
PhaseX Properties
Type
Description
STATECHANGE/SUP
Bool
STATECHANGE/UNACK
Bool
Unacknowledged alarm.
STATECHANGE/UNACKEP
Bool
XMIT_ACK
Bool
XMIT_SILENCE
Bool
PhaseX Properties
The Harmony PhaseX tag contains all the properties listed in Table 8 and Table 42.
Table 42. PhaseX Properties (HarmPhaseX)
Name
236
Type
Description
ACQ
Bool
Acquired status.
ALMACKBC
Bool
BATCH
St
Batch ID.
BATCH1
St
BATCHMGR
St
CAMPAIGN
St
Campaign ID.
COMMAND
Int
Batch command.
DBGSTOP
Bool
DEBUG
Real
Debug.
FASTCNTR
Int
FASTTM
Real
3BUA000157R4101
PhaseX Properties
Type
Description
FLTCODE
Int
Fault code.
FLTDATA
Real
Fault data.
HANDSH
Int
Handshaking option.
HOLDDISABLED
Bool
Disable.
LEAD
Bool
Lead PhaseX.
LOT
St
Lot ID
MODE
Int
PHASE
St
Phase name.
PHASEDATA
St
PHASENO
Int
Phase number.
PHASENO:S
St
PRGDESC
St
Program description.
PRGID
Real
Program ID.
PRGID:S
St
Program ID string.
PRGTM
St
Program timestamp.
PROG
Bool
Program status.
RECIPE
St
Recipe ID.
REDTAG/ACT
Bool
REDTAG/KEY1
St
REDTAG/KEY2
St
REDTAG/KEY3
St
SEQDATA
St
3BUA000157R4101
237
PhaseX Properties
238
Type
Description
SEQMODE
Bool
Sequence mode.
SLOWCNTR
Int
SLOWCNTRXRP
Int
SLOWTM
Real
STATE
Int
State.
STATE:S
St
State string.
STOPDISABLED
Bool
Disable.
SYSFAULT/ACKR
Bool
Acknowledge required.
SYSFAULT/ACT
Bool
Active.
SYSFAULT/ALARM
Bool
Alarm state.
SYSFAULT/ALMEN
Bool
Alarm event.
SYSFAULT/AREF
Bool
Associated value
SYSFAULT/COM
St
SYSFAULT/COM0
St
SYSFAULT/COM1
St
SYSFAULT/COMP
Bool
SYSFAULT/DESCRIPTION
St
Signal description.
SYSFAULT/DUAL
Bool
SYSFAULT/EN
Bool
Enable.
SYSFAULT/EPSCAT
Int
SYSFAULT/PRI
Int
SYSFAULT/PRI0
Int
Normal priority.
3BUA000157R4101
PhaseX Properties
Type
Description
SYSFAULT/PRI1
St
Active priority.
SYSFAULT/SIG
Bool
Boolean value.
SYSFAULT/SIG0
St
SYSFAULT/SIG1
St
SYSFAULT/SUP
Bool
SYSFAULT/UNACK
Bool
Unacknowledged alarm.
SYSFAULT/UNACKEP
Bool
USERFAULT/ACKR
Bool
Acknowledge required.
USERFAULT/ACT
Bool
Active.
USERFAULT/ALARM
Bool
Alarm state.
USERFAULT/ALMEN
Bool
Alarm event.
USERFAULT/AREF
Bool
Associated value.
USERFAULT/COM
St
USERFAULT/COM0
St
USERFAULT/COM1
St
USERFAULT/COMP
Bool
USERFAULT/DESCRIP- St
TION
Signal description.
USERFAULT/DUAL
Bool
USERFAULT/EN
Bool
Enable.
USERFAULT/EPSCAT
Int
USERFAULT/PRI
Int
USERFAULT/PRI0
St
Normal priority.
3BUA000157R4101
239
PhaseX Properties
240
Type
Description
USERFAULT/PRI1
St
Active priority.
USERFAULT/SIG
Bool
Boolean value.
USERFAULT/SIG0
St
USERFAULT/SIG1
St
USERFAULT/SUP
Bool
USERFAULT/UNACK
Bool
Unacknowledged alarm.
USERFAULT/UNACKEP Bool
USERMSG/ACKR
Bool
Acknowledge required.
USERMSG/ACT
Bool
Active.
USERMSG/ALARM
Bool
Alarm state.
USERMSG/ALMEN
Bool
Alarm event.
USERMSG/AREF
Bool
Associated value.
USERMSG/COM
St
USERMSG/COM0
St
USERMSG/COM1
St
USERMSG/COMP
Bool
USERMSG/DESCRIPTION
St
Signal description.
USERMSG/DUAL
Bool
USERMSG/EN
Bool
Enable.
USERMSG/EPSCAT
Int
USERMSG/PRI
Int
USERMSG/PRI0
St
Normal priority.
3BUA000157R4101
Type
Description
USERMSG/PRI1
St
Active priority.
USERMSG/SIG
Bool
Boolean value.
USERMSG/SIG0
St
USERMSG/SIG1
St
USERMSG/SUP
Bool
USERMSG/UNACK
Bool
Unacknowledged alarm.
USERMSG/UNACKEP
Bool
XRCONF
Bool
XREREV
Int
XRE revision.
XRPREV
Int
XRP revision.
Type
Description
ACTIVE
Bool
ALMACKBC
Bool
CACHETIME
Real
3BUA000157R4101
241
242
Type
Description
FB1/COMP
Bool
FB1/DESCRIPTION
St
Signal description.
FB1/SIG
Bool
Boolean value.
FB1/SIG0
St
FB1/SIG1
St
OUT/ACKR
Bool
Acknowledge required.
OUT/ACT
Bool
Active.
OUT/ALARM
Bool
Alarm state.
OUT/ALMEN
Bool
Alarm event.
OUT/AREF
Bool
Associated value.
OUT/COM
St
OUT/COM0
St
OUT/COM1
St
OUT/COMP
Bool
OUT/DESCRIPTION
St
Signal description.
OUT/DUAL
Bool
OUT/EN
Bool
Enable.
OUT/EPSCAT
Int
OUT/PRI
Int
OUT/PRI0
St
Normal priority.
OUT/PRI1
St
Active priority.
OUT/SIG
Bool
Boolean value.
3BUA000157R4101
Type
Description
OUT/SIG0
St
OUT/SIG1
St
OUT/SUP
Bool
OUT/UNACK
Bool
Unacknowledged alarm.
OUT/UNACKEP
Bool
OUTOVR
Bool
State is overridden.
RECORDER
St
RECORDERID
St
REDTAG/ACT
Bool
REDTAG/KEY1
St
REDTAG/KEY2
St
REDTAG/KEY3
St
REPORTREAD
Bool
REPORTTYPE
Int
REPORTTYPE:S
St
RESCMD
Bool
RESIN
Bool
SETCMD
Bool
SETIN
Bool
SETPER
Bool
Set permissive.
SOEDATA
St
3BUA000157R4101
243
244
Type
Description
STATECHANGE/ACKR
Bool
Acknowledge required.
STATECHANGE/ACT
Bool
Active.
STATECHANGE/ALARM
Bool
Alarm state.
STATECHANGE/ALMEN
Bool
Alarm event.
STATECHANGE/AREF
Bool
Associated value.
STATECHANGE/COM
St
STATECHANGE/COM0
St
STATECHANGE/COM1
St
STATECHANGE/COMP
Bool
STATECHANGE/DESCRIP- St
TION
Signal description.
STATECHANGE/DUAL
Bool
STATECHANGE/EN
Bool
Enable.
STATECHANGE/EPSCAT
Int
STATECHANGE/PRI
Int
STATECHANGE/PRI0
St
Normal priority.
STATECHANGE/PRI1
St
Active priority.
STATECHANGE/SIG
Bool
Boolean value.
STATECHANGE/SIG0
St
STATECHANGE/SIG1
St
STATECHANGE/SUP
Bool
STATECHANGE/UNACK
Bool
Unacknowledged alarm.
3BUA000157R4101
Server Properties
Type
Description
STATECHANGE/UNACKEP Bool
USERTYPE
Int
WAITTIME
Real
Server Properties
The Harmony Server object contains all the properties listed in Table 23 and
Table 44.
Table 44. Harmony Server Properties (HarmServer)
Name
Type
Description
ACTIVE
Bool
Server is active.
ACTIVE:S
St
ALARM
Bool
ALARM:N
Int
ALARM:S
St
ANG_XR_CNT
Int
ASCII_XR_CNT
Int
COMM_ERR/ACKR
Bool
Acknowledge required.
COMM_ERR/ACT
Bool
Active.
COMM_ERR/ALARM
Bool
Alarm state.
COMM_ERR/ALMEN
Bool
Alarm event.
COMM_ERR/AREF
Bool
Associated value.
3BUA000157R4101
245
Server Properties
246
Type
Description
COMM_ERR/COM
St
COMM_ERR/COM0
St
COMM_ERR/COM1
St
COMM_ERR/COMP
Bool
COMM_ERR/DESCRIPTION
St
Signal description.
COMM_ERR/DUAL
Bool
COMM_ERR/EN
Bool
Enable.
COMM_ERR/EPSCAT
Int
COMM_ERR/PRI
Int
COMM_ERR/PRI0
St
Normal priority.
COMM_ERR/PRI1
St
Active priority.
COMM_ERR/SIG
Bool
Boolean value.
COMM_ERR/SIG0
St
COMM_ERR/SIG1
St
COMM_ERR/SUP
Bool
COMM_ERR/UNACK
Bool
Unacknowledged alarm.
COMM_ERR/UNACKEP
Bool
DAANG_XR_CNT
Int
DADIG_XR_CNT
Int
DD_XR_CNT
Int
3BUA000157R4101
Server Properties
Type
Description
DIG_XR_CNT
Int
DOMAIN
St
Servers domain.
EAIN_XR_CNT
Int
EAOUT_XR_CNT
Int
EDIN_XR_CNT
Int
EDOUT_XR_CNT
Int
FILTERBQ
Bool
FILTERXR
Bool
GROUPID
St
HARM_NS_ENBL
Bool
HOST
St
ICI_MODE
Int
ICI_REV
St
ICI_TYPE
Int
INFINET
Bool
INTERNALERROR/ACKR
Bool
Acknowledge required.
INTERNALERROR/ACT
Bool
Active.
INTERNALERROR/ALARM Bool
3BUA000157R4101
Alarm State.
247
Server Properties
248
Type
Description
INTERNALERROR/ALEM
Bool
Alarm event.
INTERNALERROR/AREF
Bool
Associated value.
INTERNALERROR/COM
St
INTERNALERROR/COM0
St
INTERNALERROR/COM1
St
INTERNALERROR/COMP
Bool
INTERNALERROR/
DESCRIPTION
St
Signal description.
INTERNALERROR/DUAL
Bool
INTERNALERROR/EN
Bool
Enable.
INTERNALERROR/
EPSCAT
Int
INTERNALERROR/PACK
Bool
INTERNALERROR/PRI
Int
INTERNALERROR/PRI0
St
Normal priority.
INTERNALERROR/PRI1
St
Active priority.
INTERNALERROR/SIG
Bool
Boolean value.
INTERNALERROR/SIG0
St
INTERNALERROR/SIG1
St
INTERNALERROR/SUP
Bool
INTERNALERROR/UNACK Bool
Unacknowledged alarm.
INTERNALERROR/
UNACKEP
Bool
3BUA000157R4101
Server Properties
Type
Description
LOOP_TIME
St
MAX_TAGS
Int
MOD_TSTAMP
Bool
MSDD_XR_CNT
Int
MSTAT_XR_CNT
Int
NO_BULK_EXPORT_PER
SIST
Bool
OISMODE
Bool
PERCSYNC
Real
RCM_XR_CNT
Int
RCVGBLACK
Bool
RCVGBLSIL
Bool
REDID
St
ID of redundant Server.
REDSTATE/ACKR
Bool
Acknowledge required.
REDSTATE/ACT
Bool
Active.
REDSTATE/ALARM
Bool
Alarm state.
REDSTATE/ALMEN
Bool
Alarm event.
REDSTATE/AREF
Bool
Associated value.
REDSTATE/COM
St
3BUA000157R4101
249
Server Properties
250
Type
Description
REDSTATE/COM0
St
REDSTATE/COM1
St
REDSTATE/COMP
Bool
REDSTATE/DESCRIPTION St
Signal description.
REDSTATE/DUAL
Bool
REDSTATE/EN
Bool
Enable.
REDSTATE/EPSCAT
Int
REDSTATE/PRI
Int
REDSTATE/PRI0
St
Normal priority.
REDSTATE/PRI1
St
Active priority.
REDSTATE/SIG
Bool
Boolean value.
REDSTATE/SIG0
St
REDSTATE/SIG1
St
REDSTATE/SUP
Bool
REDSTATE/UNACK
Bool
Unacknowledged alarm.
REDSTATE/UNACKEP
Bool
RESTARTS
Int
RMCB_XR_CNT
Int
RMSC_XR_CNT
Int
SILENCE
Bool
3BUA000157R4101
Server Properties
Type
Description
SIMULATE
Bool
STARTUPTIME
St
STARTUPTIME:TS
Date
STAT_XR_CNT
Int
STATS/EVENT_SUBS
Int
STATS/GET_SUBS
Int
STATS/PUT_SUBS
Int
STATS/PUTS
Int
STATS/STREAM_SUBS
Int
STATS/TAGS
Int
STATUS
Int
Server status.
STATUS:S
St
SYS_DESC
St
SYSTEMID
St
ID of system (project).
TEXT_XR_CNT
Int
TS/ACC
Int
TS/ENBL
Bool
TS/MSTR
Bool
TS/MSTR_ACC
Int
3BUA000157R4101
251
Server Properties
252
Type
Description
TS/MSTR_LOOP
Int
TS/MSTR_NODE
Int
TS/UPDATE
Int
TS/WAIT
Int
UPTIME
Time
3BUA000157R4101
Description
Every property consists of following three pieces of information: a value, a quality,
and a timestamp. The quality describes the state of the property that originates
anywhere in the process control system.
An application in the process control system (function block in a controller or in
Harmony INFI 90) can evaluate the provided quality information and can apply
rules for further processing (use of values with a determined quality, displaying of
values with quality, use the quality for filter purposes).
Indicators
Tag quality is indicated with ASCII characters. The quality indicator appears in
several functions in the Harmony INFI 90 system (event page, faceplate, reports).
Table 45 contains a list of the quality indicators and their descriptions.
3BUA000157R4101
253
Uncertain
quality
Good quality
Character
X
Configuration error
Not connected
Communication failure
Out of Service
<blank>
&
Increasing/
decreasing
Quality
<blank>
Nonspecific
Local override
Not increasing, not decreasing, not amended, not annotation
Value increasing
Value decreasing
Annotation
Amended
Unknown
state
Unknown
Unknown
state
Unknown
for vendor specific use (vendor specific status). The OPC quality structure is shown
in Table 46.
L = limit status.
S = substatus.
Q = quality status.
254
3BUA000157R4101
15
14
13
12
11
10
09
08
07
06
05
04
03
02
01
00
Use
VS
VS
VS
VS
VS
VS
VS
VS
15
14
13
12
11
10
09
08
07
06
05
04
03
02
01
00
Use
VS
VS
VS
VS
VS
VS
VS
VS
Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
IVI
DVI
UTS
Use AMD
INT
3BUA000157R4101
NOD DLS NLD ANN CLC CER PRJ RES RES RES RES
255
Abbreviation
Description
00 01
02 05
OPC substatus.
06 07
08 15
VS
16
UTS
17
DVI
18
INI
19 22
RES
23
PRJ
24
CER
Scaling/conversion error.
25
CLC
Calculated result.
256
3BUA000157R4101
Tag Quality
OPC defines a quality specified on property basis. In addition, Harmony INFI 90
also provides a quality on tag basis. The tag class (SymTag) provides separate
3BUA000157R4101
257
Properties
properties for the tag related quality. These properties are derived from other
properties.
Properties
Quality
This property is part of the SymTag class. It represents the overall quality of the tag.
It provides this quality in the same format defined previously for tag property
quality. Specifically the value component of this property returns numerically the
Harmony INFI 90 quality word and textually the three character quality string. The
quality component of this property always returns the quality status GOOD
non_specific as it represents the quality of this property, not the tag. The timestamp
represents the last change in the value of this property.
Bad
This property is part of the SymTag class. It represents the overall BAD quality of
the tag. It provides this quality as a Boolean status signal with an associated event
point. The quality component of this property always returns the quality status
GOOD non_specific as it represents the quality of this property, not the tag. The
timestamp represents the last change in the value of this property.
Suspended
This property is a part of the HarmonyTag class (used for the Harmony functionality
substitution and off scan). It provides this quality as a Boolean status signal. The
quality component of this property always returns the quality status GOOD
non_specific as it represents the quality of this property, not the tag. The timestamp
represents the last change in the value of this property.
258
3BUA000157R4101
Description
No connection to gateway
(control system).
Cause
Communication error,
component failure.
Configuration change.
3BUA000157R4101
OPC Quality
OPC Substatus
Connection gateway
BAD
Comm_Failure
Connection tag
BAD
Not_Connected
BAD
Configuration_Error
BAD
Configuration_Error
RTDS quality
259
OPC Quality
OPC Substatus
Value decreasing
DVI
Value increasing
IVI
Quality Bits
Table 51 describes the values for the quality bits.
Table 51. OPC Quality Bits
QQ
Bit Value
Define
Description
00SSSSLL Bad
01SSSSLL Uncertain
10SSSSLL N/A
11SSSSLL Good
Substatus Bits
The layout of these bits depends on the value of the quality bits. The substatus bits
for bad quality are shown in Table 52. Table 53 shows the substatus bits for
uncertain quality. Table 54 shows the substatus bits for good quality.
260
3BUA000157R4101
Substatus Bits
Define
Description
000001LL Configuration
error
000101LL Last known value Communications have failed. However, the last
known value is available. Note that the age of the
value may be determined from the TIMESTAMP in
the OPCITEMSTATE.
8 - 15
N/A
NOTE: Servers that do not support substatus should return 0. An old value can be returned with the quality
set to bad (0) and the substatus set to 5. This is for consistency with the fieldbus specification. This is
the only case in which a client may assume that a bad value is still usable by the application.
3BUA000157R4101
261
Substatus Bits
Bit Value
Define
Description
010001LL Last usable value Whatever was writing this value has stopped doing
so. The returned value should be regarded as
stale. This differs from a bad value with substatus
5 (last known value). That status is associated
specifically with a detectable communications
error on a fetched value. This error is associated
with the failure of some external source to put
something into the value within an acceptable
period of time. The age of the value can be
determined from the TIMESTAMP in
OPCITEMSTATE.
2-3
N/A
010101LL Engineering
units exceeded
010110LL
Subnormal
N/A
7 - 15
262
3BUA000157R4101
Limit Bits
Limit Bits
The limit bits are valid regardless of the quality and substatus. In some cases, such
as sensor failure, it can provide useful diagnostic information. Table 54 provides the
descriptions of the limit bits.
Table 54. Limit Bits
LL
Bit Value
Define
Description
QQSSSS01 Low
limited
QQSSSS10 High
limited
QQSSSS11 Constant
OPCHDA Quality
OPCHDA_QUALITY values identify quality values specific to retrieval of
historical data. These quality values are described in Table 55.
Table 55. OPCHDA_QUALITY Values
Quality Values
Description
OPC_EXTRADATA
OPC_INTERPOLATED
OPC_RAW
OPC_CALCULATED
OPC_BADSOURCE
OPC_NOBOUND1
3BUA000157R4101
263
OPCHDA Quality
Description
OPC_NODATA
OPC_DATALOST
Collection started/stopped/lost.
OPC_CONVERSION
OPC_ANNOTATION
264
3BUA000157R4101
RGB Value
Definition
OCS3Dframe1
198,220,220
OCS3Dframe2
110,140,140
OCSDynamicBarAck
Alarm
255,30,102
OCSDynamicBar
Limits
255,166,0
OCSDynamicBar
Normal
122,237,109
OCSDynamicBar
UnackAlarm
255,30,102
185,4,58
OCSDynamicBar
UnackNormal
122,237,109
82,165,82
3BUA000157R4101
265
Introduction
RGB Value
Definition
OCSPointTraceCO
255,255,255
OCSPointTracePV
0,255,255
OCSPointTraceSP
255,0,0
OCSStaticText
0,0,0
OCSStationSP
DynamicBar
122,237,109
OCSValBorderAckAlarm 255,30,102
OCSValBorderNormal
81,145,17
OCSValBorderUnack
Alarm
255,30,102
185,4,58
OCSValBorderUnack
Normal
81,145,17
38,69,7
OCSValEnergizedBg
255,245,51
OCSValQuality
0,0,0
OCSValQualityBg
0,196,196
266
3BUA000157R4101
Introduction
RGB Value
Definition
OCSValue
0,0,0
OCSValueBg
0,196,196
OCSValueUserSelBg
0,255,0
3BUA000157R4101
267
Introduction
268
3BUA000157R4101
INDEX
A
Alarm system 137
Analog export tab 76
Analog tab 74
ASCII tab 76
Aspects
Harmony synchronizer 169
Operating parameters 174
Time adjustment 179
Time synchronization 178
B
Bulk configuration manager 149
C
Communication errors 63
Configurable text 128
Configuration
Data access 37
Life cycle changes 38
Object life cycle 38
Object management 37
Overview 37
Validation 41
Version management 40
Connectivity Server (RTDS) 57
E
Enhanced analog input tab 76
Enhanced analog output tab 76
Enhanced digital input tab 81
Enhanced digital output tab 81
Event 137
Categories 141
Classifications 140
Concentrator 139
Distribution 139
Event point 138, 141
Attributes 141
Dual 147
Non dual 147
States 145
Event system 137
Export configuration 159
F
Functional description 21
H
D
DAANG 68
DAANG tab 77
DADIG tab 82
DD 69
Device driver tab 79
3BUA000157R4101
269
Index
Server object 58
Tag object 72
I
Import configuration 159
Indexed text tab 128
T
M
Module status tab 82
MSDD tab 83
P
PhaseX tab 85
Project history tab 135
Q
Quality 253
Quality indicators 253
Quality text tab 134
R
RCM tab 86
Related documentation 24
RMCB tab 87
RMCB text tab 64
RMSC tab 88
RTDS 57
S
Server atoms 245
Server object 57
Signal structure 187
SOE 107
Architecture 110
External interfaces 114
Function blocks 114
Hardware 110, 113
SOE objects 115
SOE Recorder 70
270
Tab
Analog 74
Analog export 76
ASCII 76
DAANG 77
DADIG 82
Device driver 79
Digital 79
Digital export 80
Enhanced analog input 76
Enhanced analog output 76
Enhanced digital input 81
Enhanced digital output 81
Harmony, server object 58
Harmony, tag object 72
Module status 82
MSDD 83
PhaseX 85
RCM 86
RMCB 87
RMCB text 64
RMSC 88
SOE Recorder 115
SOE report 117
Station 89
Tag atoms
Analog export 222
Common 188
Common analog 191
Common digital 211
DAANG 194
DADIG 214
Device driver 215
3BUA000157R4101
Index
3BUA000157R4101
RMCB read 70
RMSC read 70
SOE report 70
Station read 70
Text read 71
Text selector 92
Time adjustment
Current time adjust status 179
New time adjust target 180
Time synchronization 62
W
Wildcard characters 158
271
Index
272
3BUA000157R4101
http://www.abb.com
Automation Technology Products
Wickliffe, Ohio, USA
www.abb.com/controlsystems