INFI 90 Function Block Library For AC 800M

INFI 90 Function Block Library for AC 800M
Function Block Evolution Guide

INFI 90 Function Block Library for AC 800M
Function Block Evolution Guide

NOTICE
This document contains information about one or more ABB products and may include a
description of or a reference to one or more standards that may be generally relevant to
the ABB products. ABB may have one or more patents or pending patent applications
protecting the intellectual property in the ABB product(s) described in this publication.
The presence of any such description of a standard or reference to a standard is not a
representation that all of the ABB products referenced in this document support all of the
features of the described or referenced standard. In order to determine the specific fea-
tures supported by a particular ABB product, the reader should consult the product spec-
ifications for the particular ABB product.
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 hard-
ware described in this document.
This document and parts thereof must not be reproduced or copied without written per-
mission 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.
TRADEMARKS
All rights to copyrights, registered trademarks, and trademarks reside with their respec-
tive owners.
Copyright © 2003-2013 by ABB.

All rights reserved.
Release: July 2013

Document number: 3BUA000937R301
TABLE OF CONTENTS
About This Book

General ............................................................................................................................25
Document Conventions ...................................................................................................25
Warning, Caution, Information, and Tip Icons................................................................25
Terminology.....................................................................................................................26
Related Documentation ...................................................................................................27
Section 1 - Introduction
General ............................................................................................................................29
800xA System .................................................................................................................29
800xA Base Platform ...........................................................................................29
Aspect Object .......................................................................................................30
Project Workflow Activities in 800xA System ....................................................31
Structures in 800xA System ............................................................................................33
Introduction to Structures in 800xA System ........................................................33
Structures Used for Administration in 800xA System.........................................34
User Structure......................................................................................34
Workplace Structure ............................................................................34
Structures Used for Application Engineering in 800xA System .........................35
Functional Structure ............................................................................35
Control Structure.................................................................................36
Other Support Structures in 800xA System .........................................................37
Location Structure ...............................................................................37
Library Structure .................................................................................37
Object Type Structure..........................................................................38
Service Structure .................................................................................38
3BUA000937R301 5
Table of Contents
Maintenance Structure ........................................................................ 38
Section 2 - Introduction to Engineering Tools

Control Builder................................................................................................................ 39
Function Designer ........................................................................................................... 41
Section 3 - Common Parameters

Common Properties......................................................................................................... 43
Common Analog Properties ............................................................................................ 48
Common Digital Properties............................................................................................. 52
Section 4 - Design Differences

Specification Handling .................................................................................................... 57
Segment Block FC82 and Executive Block (FC81) and Extended Executive Block (FC90)
Implementation .................................................................................................... 58
Specification Range Validity Check................................................................................ 61
Exception Report Handling............................................................................................. 61
Execution Order .............................................................................................................. 62
Using Control Builder as the Engineering Tool................................................... 62
Using Function Designer as an Engineering Tool ............................................... 62
Control Interface Implementation in zBlocks ................................................................. 63
OPC Error Indication In Graphical Interfaces................................................................. 63
Quality Propagation and Indication................................................................................. 64
String Handling for Faceplates........................................................................................ 65
Section 5 - Device Driver

Comparison of Object View ............................................................................................ 69
Comparison of DeviceDriver Parameters........................................................................ 71
Differences in Functionality............................................................................................ 73
Differences in Graphical Interfaces................................................................................. 74
Section 6 - Div2Real
Comparison of Object View ............................................................................................ 75
Comparison of Div2Real Parameters .............................................................................. 76
6 3BUA000937R301
Table of Contents
Section 7 - HiSel
Comparison of Object View ............................................................................................77
Comparison of HiSel Parameters ...................................................................................78
Section 8 - Lim
Comparison of Lim Parameters.......................................................................................80
Section 9 - Mul2Real
Comparison of Mul2Real Parameters..............................................................................82
Section 10 - MatrixAdd
Comparison of MatrixAdd Parameters............................................................................86
Section 11 - LoSel
Comparison of LoSel Parameters ...................................................................................90
Section 12 - MatrixMul
Comparison of MatrixMul Parameters ............................................................................94
Section 13 - ElapTimer
Comparison of ElapTimer Parameters.............................................................................98
Differences in Functionality ............................................................................................99
Differences in Graphical Interfaces .................................................................................99
Section 14 - INPOL
Comparison of Object View ..........................................................................................101
Comparison of INPOL Parameters ...............................................................................104
Differences in Functionality ..........................................................................................105
3BUA000937R301 7
Table of Contents
Differences in Graphical Interfaces............................................................................... 105
Section 15 - DelayReal
Comparison of Object View .......................................................................................... 107
Comparison of DelayReal parameters .......................................................................... 109
Differences in Functionality.......................................................................................... 109
Section 16 - FnGen
Comparison of FnGen parameters ................................................................................ 113
Section 17 - Integrator
Comparison of Integrator Parameters............................................................................ 116
Section 18 - MovAvg
Comparison of MovAvg Parameters ............................................................................. 120
Section 19 - DSum
Comparison of DSum Parameters ................................................................................. 125
Section 20 - SqRoot
8 3BUA000937R301
Table of Contents
Comparison of SqRoot Parameters ...............................................................................128

Differences in Graphical Interfaces ...............................................................................128
Section 21 - XferDint
Comparison of XferDint Parameters ............................................................................130
Section 22 - XferBool
Comparison of XferBool Parameters ...........................................................................132
Section 23 - TimerBool
Comparison of TimerBool Parameters .........................................................................134
Section 24 - UpDnCount
Comparison of UpDnCount Parameters .......................................................................137
Section 25 - XferReal
Comparison of XferReal parameters ............................................................................140
3BUA000937R301 9
Table of Contents
Section 26 - LeadLag
Comparison of LeadLag Parameters ............................................................................ 142
Section 27 - Sum2Real
Comparison of Sum2Real parameters........................................................................... 144
Section 28 - MuxReal
Comparison of MuxReal Parameters ............................................................................ 146
Section 29 - DMuxReal
Comparison of DmuxReal Parameters .......................................................................... 152
Real Signal Demultiplexer FC-126 behavior in Harmony................................. 154
General Behavior ............................................................................................... 154
Behavior 1 .......................................................................................................... 154
Behavior 2 .......................................................................................................... 154
Behavior 3 .......................................................................................................... 154
Behavior 4 .......................................................................................................... 155
Section 30 - MuxBool
Comparison of MuxBool Parameters............................................................................ 160
10 3BUA000937R301
Table of Contents

Section 31 - RecipeReal
Comparison of RecipeReal Parameters .........................................................................166
Section 32 - HiLowComp
Comparison of Object View .........................................................................................171
Comparison of HiLowComp Parameters.......................................................................172
Section 33 - ErrPID
Comparison of ErrPID Parameters ................................................................................175
New/Changed Parameters..............................................................................................175
Section 34 - DeltaPID
Comparison of DeltaPID Parameters ............................................................................179
Differences in Graphical Interfaces....................................................................180
Section 35 - QOR
Comparison of QOR Parameters ...................................................................................183
3BUA000937R301 11
Table of Contents
Section 36 - SRMem
Comparison of Object View ......................................................................................... 185
Comparison of SRMem Parameters.............................................................................. 186
Section 37 - TSTQ
Comparison of TSTQ Parameters ................................................................................. 188
Section 38 - REMSET
Comparison of REMSET Parameters .......................................................................... 191
Section 39 - RCM
Comparison of RCM Parameters .................................................................................. 195
Section 40 - DOL
Comparison of DOL Parameters ................................................................................... 201
Section 41 - AOL
Comparison of AOL Parameters ................................................................................... 207
12 3BUA000937R301
Table of Contents
Section 42 - Station
Comparison of Station Parameters ...............................................................................212
Section 43 - APID
Comparison of APID Parameters ..................................................................................226
Section 44 - MSDD
Comparison of MSDD Parameters ................................................................................231
Section 45 - TSTALM
Comparison of TSTALM Parameters ............................................................................238
Section 46 - DAANG
Comparison of DAANG Parameters ............................................................................242
Section 47 - RMCB
Comparison of RMCB Parameters ...............................................................................262
3BUA000937R301 13
Table of Contents
Section 48 - DADIG
Comparison of DADIG Parameters ............................................................................. 269
Section 49 - ISC
Comparison of ISC Parameters .................................................................................... 275
Section 50 - Exec
Comparison of Exec Parameters ................................................................................... 279
Section 51 - ExExec
Comparison of ExExec Parameters .............................................................................. 283
New/Changed Parameters ............................................................................................. 283
Section 52 - Device Monitor

Comparison of DevMon Parameters ............................................................................. 288
Section 53 - Exponential
Comparison of EXP1 Parameters.................................................................................. 292
Section 54 - Logarithm
14 3BUA000937R301
Table of Contents

Comparison of LOG1 Parameters .................................................................................294
Section 55 - Trigonometric
Comparison of TRIG Parameters ..................................................................................296
Section 56 - Power
Comparison of POWER Parameters..............................................................................298
Section 57 - Blink
Comparison of Blink Parameters...................................................................................300
Section 58 - RedAI
Section 59 - RedDI
Comparison of RedDI Parameters.................................................................................306
3BUA000937R301 15
Table of Contents
Section 60 - RecipeBool
Comparison of RecipeBool Parameters ........................................................................ 308
Section 61 - Rung5
Comparison of Rung5 Parameters................................................................................. 315
Section 62 - Rung10
Section 63 - Rung20
Comparison of Rung20 Properties ................................................................................ 326
Section 64 - Polynomial
Comparison of POLY Parameters ................................................................................. 332
Section 65 - SeqMstrSlv
Comparison of SeqMstrSlv Parameters ........................................................................ 337
16 3BUA000937R301
Table of Contents

Implementation of data type Bool3/Bool4 ....................................................................340
Section 66 - SeqMon
Comparison of SeqMon Parameters ..............................................................................345
New/Changed Parmeters ...............................................................................................346
Section 67 - Trip
Comparison of Trip Parameters.....................................................................................352
Section 68 - SeqMgr
Comparison of SEQMGR Parameters...........................................................................355
Section 69 - JumpMCR
Comparison of JumpMCR Parameters ..........................................................................360
Section 70 - SlSel
Comparison of SLSEL Parameters................................................................................363
Section 71 - MODST
3BUA000937R301 17
Table of Contents

Comparison of MODST Parameters ............................................................................. 368
Section 72 - MultiMon
Comparison of MULTIMON Parameters...................................................................... 387
Section 73 - TexSel
Comparison of Parameters ............................................................................................ 396
Section 74 - BasicStation
Comparison of BasicStation Parameters ....................................................................... 402
Section 75 - SeqGen
Comparison of SeqGen Parameters............................................................................... 417
Section 76 - Pulse Positioner

Comparison of PulsePosn Parameters........................................................................... 425
18 3BUA000937R301
Table of Contents
Section 77 - PulseRate
Comparison of PulseRate Parameters............................................................................430
Section 78 - RateLimiter
Comparison of RateLimiter Parameters ........................................................................435
Section 79 - Alarm and Event Handling

Alarm and Events Generation........................................................................................437
Alarm Inhibition ............................................................................................................440
Bad Quality Alarms............................................................................................441
Bad Quality Messages........................................................................................442
Section 80 - Programmatic Interface

Batch90/UDF Migration................................................................................................443
Harmony (Infi90H).............................................................................................443
INFI90FCLib (Infi90M).....................................................................................444
zBlock ....................................................................................445
zBlockList and zVarList FBs ............................................................446
zBlocks ..........................................................................................................................449
zAOL ...........................................................................................................449
Comparison of Object View ..............................................................449
Comparison of zAOL Parameters .....................................................452
zRCM ...........................................................................................................453
Comparison of zRCM Parameters.....................................................456
Differences in Graphical Interfaces...................................................457
zDeviceDriver.....................................................................................................457
3BUA000937R301 19
Table of Contents
Comparison of Object View.............................................................. 457

Comparison of zDeviceDriver Parameters........................................ 460
Differences in Graphical Interfaces .................................................. 461
zMSDD .......................................................................................................... 462
Comparison of zMSDD Parameters.................................................. 465
zFGen .......................................................................................................... 467
Compare FGEN and zFGen .............................................................. 467
zStation .......................................................................................................... 470
Comparison of zStation Parameters.................................................. 473
zDOL .......................................................................................................... 476
Comparison of Object View ............................................................. 476
Comparison of zDOL Parameters..................................................... 478
zRMCB .......................................................................................................... 479
Comparison of zRMCB Parameters ................................................. 482
Difference in Graphical Interface ..................................................... 483
zREMSET .......................................................................................................... 484
Comparison of zREMSET Parameters ............................................ 486
zTexSel .......................................................................................................... 487
Comparison of zTexSel Parameters .................................................. 489
zAPID .......................................................................................................... 491
Comparison of zAPID Parameters.................................................... 493
zISC .......................................................................................................... 495
20 3BUA000937R301
Table of Contents
Comparison of Object View .............................................................495

Comparison of zISC Parameters ......................................................496
zInteg ...........................................................................................................498
Comparison of Integrator and zInteg Parameters..............................498
zRamp ...........................................................................................................500
Comparison of Ramp and zRamp Parameters...................................500
zTimer ...........................................................................................................504
Comparison of Timer and zTimer Parameters ..................................504
zBlockList Function Blocks ..........................................................................................506
Comparison of BLOCK ARRAY and zBlockList Function Blocks ..................506
Configuration of BLOCK ARRAY and zBlockList Function Blocks506
Reading Status data from BLOCK ARRAY and zBlockList Function
Blocks .........................................................................510
Commands to a BLOCK ARRAY and zBlockList FBs....................510
zlMSDD ....................................................................................510
zVarList Function Blocks ..............................................................................................511
Compare VAR ARRAY and zVarList Function Blocks .....................................511
Configuration of VAR ARRAY and zVarList Function Blocks ........511
Reading Status Data from VAR ARRAY and zVarList Function Blocks
513
Commands to a VAR ARRAY and zBlockList Function Blocks......513
zlReal ....................................................................................513
Section 81 - Mapped Function Codes in 800xA Standard Library

Summer (4-Input)-FC14 ................................................................................................515
Comparison of Object View ...............................................................................515
Comparison of Summer (4-Input) Parameters ..................................................516
Additional Parameters in System Library ..........................................................516
Parameters Not in System Library .....................................................................517
Differences in Functionality...............................................................................517
3BUA000937R301 21
Table of Contents
AND (4-Input)-FC38 .................................................................................................... 517

Comparison of Object View............................................................................... 517
Comparison of AND (4-Input) Parameters ....................................................... 518
Additional Parameters in System Library.......................................................... 518
Parameters Not in System Library..................................................................... 519
Differences in Functionality .............................................................................. 519
OR (4-Input)-FC40........................................................................................................ 519
Comparison of OR (4-Input) Parameters .......................................................... 520
Exclusive OR-FC101 .................................................................................................... 521
Comparison of Exclusive OR Parameters ......................................................... 522
NOT-FC33 ..................................................................................................................... 523
Comparison of NOT Parameters ....................................................................... 524
Manual Set Constant-FC02 ........................................................................................... 525
Comparison of Object View .............................................................................. 525
Comparison of Manual Set Constant Parameters .............................................. 525
Manual Set Integer -FC52 ............................................................................................. 527
Comparison of Object View .............................................................................. 527
Comparison of Manual Set Integer Parameters ................................................. 527
22 3BUA000937R301
Table of Contents
Manual Set Constant -FC51 ..........................................................................................529

Comparison of Object View ..............................................................................529
Comparison of Manual Set Constant Parameters...............................................529
Manual Set Switch-FC50 ..............................................................................................531
Comparison of Object View ..............................................................................531
Comparison of Manual Set Constant Parameters...............................................531
Appendix A - List of Function Blocks

Introduction ...................................................................................................................533
Cross Reference - Alphabetical Listing.........................................................................533
Appendix B - Alarm Priority Severity Mapping

Introduction ...................................................................................................................537
INDEX
3BUA000937R301 23
Table of Contents
24 3BUA000937R301
About This Book
General
This document describes in detail the design and functionality differences between
the Function Class Modules in Harmony system and INFI90FCLib Function
Blocks. This document is intended to help users migrating from Wintools/Composer
engineering tool environment to Control Builder M or Function Designer
engineering tool environments in 800xA System.
Document Conventions
Microsoft Windows conventions are normally used for the standard presentation of
material when entering text, key sequences, prompts, messages, menu items, screen
elements, etc.
Warning, Caution, Information, and Tip Icons

This publication includes Warning, Caution, and Information where appropriate
to point out safety related or other important information. It also includes Tip to
point out useful hints to the reader. The corresponding symbols should be
interpreted as follows:
Electrical warning icon indicates the presence of a hazard which could result in
electrical shock.
Warning icon indicates the presence of a hazard which could result in personal
injury.
3BUA000937R301 25
Terminology About This Book
Caution icon indicates important information or warning related to the concept

discussed in the text. It might indicate the presence of a hazard which could
result in corruption of software or damage to equipment/property.
Information icon alerts the reader to pertinent facts and conditions.
Tip icon indicates advice on, for example, how to design your project or how to
use a certain function
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,
fully comply with all Warning and Caution notices.
Terminology
A complete and comprehensive list of Terms is included in the IndustrialIT
Extended Automation System 800xA, Engineering Concepts instruction
(3BDS100972Rxxxx). The listing included in Engineering Concepts includes terms
and definitions as they apply to the 800xA system where the usage is different from
commonly accepted industry standard definitions and definitions given in standard
dictionaries such as Webster’s Dictionary of Computer Terms.
26 3BUA000937R301
About This Book Related Documentation
Term/Acronym Description
Cold restart Cold Restart of the application in a controller means that
all the variables of an application are reinitialized to their
initial values unless they are labeled with the ColdRetain
attribute. All variables that are labeled with the
ColdRetain attribute retain their values during the
restart. Cold Restart of the application is accomplished
via the engineering tool by selecting that choice before
download of the application
Warm restart Warm Restart of the application in a controller means
that all the variables of application are reinitialized to
their initial values unless they are labeled with the Retain
attribute and/or the ColdRetain attribute. All variables
that are labeled with the Retain attribute and/or the
ColdRetain attribute retain their values during the
restart. Warm Restart of the user's application is
accomplished by cutting off and restoring the power to a
controller (power failure) or via the engineering tool or
changing the Run/stop switch from Stop to Run
Engineering Workplace Provides tools for system wide engineering.
FB Abbreviation for Function Block
pFB Programmable Function Block.
ciFB Function Block with control interface.
pM Programmable Module (Function Block or Control
Module).
zInterface Control Interface
Related Documentation
A complete list of all documents applicable to the 800xA IndustrialIT Extended
Automation System is provided in Released User Documents, 3BUA000263Rxxxx.
This document lists applicable Release Notes and User Instructions. It is provided in
PDF format and is included on the Release Notes/Documentation media provided
3BUA000937R301 27
Related Documentation About This Book
with your system. Released User Documents are updated with each release and a
new file is provided that contains all user documents applicable for that release with
their applicable document number. Whenever a reference to a specific instruction is
made, the instruction number is included in the reference.
28 3BUA000937R301
Section 1 Introduction
General
This document describes the variation of INFI90FCLib Library objects from the
INFI90 Function Codes with respect to design, implementation and engineering
procedures.
800xA System
The Plant Explorer is a unique engineering tool which is integrated as part of 800xA
System. It is used for building a plant model. The engineering tools for configuring
different functional areas of the 800xA System are integrated into Plant Explorer
and accessible through Engineering Workplace.
The Engineering Workplace/Plant Explorer tool is primarily used for 800xA System
configuration. The Engineering workplace is used for all projects executed by
application engineers.
Working within a common engineering environment, 800xA Engineering supports a
consistent information flow from design through installation and commissioning to
operation and maintenance.
800xA Base Platform

The foundation of the System 800xA products and system solutions is the concept
of Aspect ObjectsTM, which enables enterprise wide information availability,
browsing, and navigation in a unified way.
From a software architecture perspective, the foundation of 800xA system is the
800xA Base Platform.
3BUA000937R301 29
Aspect Object Section 1 Introduction
Figure 1. 800xA System Software Architecture
Controllers are connected to the system through connectivity components, which

are bundled together and offered as options to the 800xA System. Connectivity
packages provide access to real time data, historical data, and alarm and event data
from different types of controllers.
The 800xA system provides connectivity to 800xA controllers and controllers from
earlier system offerings that include:
• AC 800M
• Advant Master AC 400 and AC 100
• Symphony Harmony INFI-90
• Symphony Melody / AC870P
• Freelance / AC 800F
• MOD300
Aspect Object
All aspects of a plant and process entity should be organized, and managed. It
should also have access to all information.
30 3BUA000937R301
Section 1 Introduction Project Workflow Activities in 800xA System
The architecture of Aspect Objects is a base of the System 800xA concept. It

provides a consistent and scalable concept that integrates Process Control and
Automation, Substation Automation and Safety products.
Information-centric navigation is a consistent way to instantly access all
information without knowledge of the application used to handle the information.
Project Workflow Activities in 800xA System

Table 1 describes the broad activities to perform in the 800xA System.
Table 1. Overall Project Workflow Activities
Activity Description
Workflow Step Activities • Create Project Environment.
• Create System.
• Select and Load Standard Object Type Libraries.
• Load / Import other reusable entities and
standards.
• Customize Project Environment.
Build Project Library • Identify common equipment and devices from
P&IDs and select reusable entities and
applicable Object Types from Standard Libraries.
• Build New Object Type Libraries.
• Adapt Standard Object Type Libraries.
• Write Specifications / Guidelines.
Create Process • To create Basic Structures, create Upper Level
Functions Plant Structures (Functional, Control, Location,
Documentation) from Object Types.
• Build Lower Level Functional Structure from
Standard Object Types.
• Build Lower Level Functional Structure from
Adapted Object Types.
3BUA000937R301 31
Project Workflow Activities in 800xA System Section 1 Introduction
Table 1. Overall Project Workflow Activities (Continued)
Activity Description
Modify / Allocate Process • Add Specific Logic.
Functions • Assign I/O Signals.
• Allocate to Applications in Control Structure.
• Allocate I/O Signals to Boards in Control
Structure.
Design / Build Graphic • Finalize Graphic Displays from Object Types.
Displays • Design and Build New Upper Level Graphic
Displays.
• Using graphic elements defined during library
creation.
Extend Configuration • Add Production Management Functionality
(Batch Management and Manufacturing
Management).
• Add Information Management Functionality.
• Add Asset Optimization Functionality.
• Finalize Lower Level Location Structure.
• Finalize Documentation Structure.
General Application • Generate Controller Code.
Software
Download and Test • Deploy Graphic Displays.
Application Software • Download Controller Code, if required use Load-
Evaluate-Go procedure.
• Load other Run-time Configuration data
• Test complete Configuration.
32 3BUA000937R301
Section 1 Introduction Structures in 800xA System
Structures in 800xA System

Introduction to Structures in 800xA System
The Aspect Object concept allows organization of objects and aspects into different
structures, depending on the context it is viewed from. Structures are graphical
representations of the relations that exist between different aspect objects.
The Plant Explorer organizes the 800xA system into structures that can be accessed
from the drop-down appearing on top of the workplace. Figure 2 shows the
structures in the workplace.
Figure 2. Structures in Engineering Workplace
Same object can be seen in different structures.
There are 19 structures by default. There are at least 5 structures which are used for
modeling a physical plant or often used in operations. The usage of these structures
are different in each system, depending on the needs of the person(s) configuring
and using the system.
3BUA000937R301 33
Structures Used for Administration in 800xA System Section 1 Introduction
The following are the commonly used structures:

• Control Structure.
• Functional Structure.
• Location Structure.
Structures Used for Administration in 800xA System
User Structure
The User Structure contains the defined users groups and users of the system. User
roles are defined in Configuration Wizard.
All users must have a related Windows user account. The User aspect primarily
contains information about a user and what the user is allowed to do within the
system (his user role). Figure 3 shows the User Structure.
Figure 3. User Structure
Workplace Structure
The Workplace Structure is used to define and create the layout of the user interface
to the system. This includes workplaces for operations, maintenance, management
and so on.
The workplace Object Types of aspect that can be placed here are numerous, and
they control the layout and function of a workplace. For example, tool bars and
menu items.
34 3BUA000937R301
Section 1 Introduction Structures Used for Application Engineering in 800xA System
Figure 4. Workplace Structure
Structures Used for Application Engineering in 800xA System

This section describes the main application structures of the 800xA system. These
are primary structures, because it is assumed that most Application Engineers
perform most of their work within these structures.
Functional Structure
The Functional Structure describes the functionality of the plant. It is used to
structure the plant into systems and subsystems according to how the plant
equipment operates together.
It is also used to organize displays, alarm sectioning and functions related to the
structure of the plant.
3BUA000937R301 35
Structures Used for Application Engineering in 800xA System Section 1 Introduction
Figure 5. Functional Structure
Control Structure
The Control Structure contains the networks and nodes that are used to control the
process, which is the equipment of the system. It is also used to organize the process
control environment in the system. This structure contains control networks, control
projects, applications, controllers, stations, different types of sub-objects (such as
I/O boards, process objects, and signals assigned to different objects within this
structure).
36 3BUA000937R301
Section 1 Introduction Other Support Structures in 800xA System
Figure 6. Control Structure
Other Support Structures in 800xA System
Location Structure
The Location Structure (optional) helps the user to identify the geography or
location of objects in the plant. This structure is built with the knowledge of
different type of buildings, rooms and locations that exist in the site.
Library Structure
The Library Structure is used to categorize and store reusable entities. It contains all
Object Type libraries and its versions. The Object Types of these libraries are stored
in Object Type Structure. It also contains the templets for Object Types such as
Alarm and Event List configuration, History Logs, and Trends.
3BUA000937R301 37
Other Support Structures in 800xA System Section 1 Introduction
Object Type Structure

All aspect objects are instances of an Object Type. This helps the user to create and
efficiently reuse standardized solutions to recurring problems.
For example, a control valve. Instead of creating a new and unique Aspect Object
for every valve in a plant, it is more efficient to create a few valve types. When a
particular solution is needed, use an instance of one of the valve Object Types.
When an instance of the Object Type is used, the aspects that are predefined for the
Object Type are automatically instantiated and associated with the new instance.
Service Structure
The Service Structure holds the services, their groups and providers, and the
relations between these defined in a system. A service is a global function in the
network. The objects and aspects in the Service Structure control the definition and
deployment of the services.
Maintenance Structure
The Maintenance Structure is used to define and work on Backups, System
Configuration Versions, and Synchronizations.
• Admin Structure.
• Aspect System Structure.
• Node Administration Structure.
• Graphics Structure.
38 3BUA000937R301
Section 2 Introduction to Engineering Tools
Control Builder
The Control Builder Project Explorer helps to create and maintain various
automation projects. The user can load, edit and save these projects similar to
ordinary MS Windows functions.The software (programs, and functions) and
hardware (the actual hardware connected to the controller) required for an
automation task are modeled in a project.
A graphic display is used to visualize relationships. The following are five different
programming languages provided by Control Builder M according to IEC 61131-3:
• Function Block Diagram (FBD).
• Structured Text (ST).
• Instruction List (IL).
• Ladder Diagram (LD).
• Sequential Function Chart (SFC).
3BUA000937R301 39
Control Builder Section 2 Introduction to Engineering Tools
Figure 7. Typical View of Control Builder
40 3BUA000937R301
Section 2 Introduction to Engineering Tools Function Designer
Function Designer
The Function Designer is an engineering editor for function oriented planning in the
800xA system. The code is designed on a Function Diagram located in the
Functional Structure. The shape of this diagram is similar to the IEC-61131
Function Block Diagram language.
The Function Diagram layout is extended with some special objects like Signal
Objects and Fieldbus Builder Profibus/HART device objects. The Function
Designer generates the code for the Control Builder M based on the Function
Diagrams. There is the possibility to create user defined Control Modules Types
using the Function Designer.
Figure 8. From Sensor to Valve Loop
3BUA000937R301 41
Function Designer Section 2 Introduction to Engineering Tools
Execute the following steps in the Control Builder M to work with Functional
Designer:
a. Create function diagrams in the Functional Structure.
b. Open a new project in Control Builder. The code generated by the function
designer will be initially held in an unassigned application until the I/O
has been allocated and the appropriate application selected and assigned.
The code is then moved to that application.
c. Download the application to the controller. This should be done using the
Control Builder.
42 3BUA000937R301
Section 3 Common Parameters
Common Properties
The common Harmony properties appear in all Harmony tag types. Table 2 lists the
common properties which includes the data type, description and equivalent
parameter in INFI90FCLib Library.
Table 2. Common Properties
Harmony Connect Console Parameters as in Type

Comments
OPC Property Name Database Name INFI90FCLib String
ALARM Overall alarm Alarm bool
status.
BAD/ACKR Acknowledge AckReqBQ bool
required.
BAD/ACT Active. N/A N/A
BAD/ALARM Alarm state. N/A N/A
BAD/ALMEN Alarm event. EnableBQ bool
BAD/AREF Associated value. N/A N/A
BAD/COM Current event N/A N/A
comment.
BAD/COM0 Normal status N/A N/A
comment.
BAD/COM1 Active state N/A N/A
comment.
3BUA000937R301 43
Common Properties Section 3 Common Parameters
Table 2. Common Properties (Continued)

Comments
BAD/COMP Complement input N/A N/A
signal.
BAD/DESCRIPTION Signal description. N/A N/A
BAD/DUAL Dual acting event. N/A N/AN/A
BAD/EN Enable. EnableBQ bool
BAD/EPSCAT Sub category of N/A N/A
event point (high
limit).
BAD/PRI Current event N/A N/A
priority.
BAD/PRI0 Normal priority. AESevRtn dint
BAD/PRI1 Active priority. AESevBQ bool
BAD/SIG Boolean value. QualFlag bool
BAD/SIG0 Inactive state N/A N/A
description.
BAD/SIG1 Active state N/A N/A
description.
BAD/SUP Event suppressed N/A N/A
by signal.
BAD/UNACK Unacknowledged N/A N/A
alarm.
BAD/UNACKEP Unacknowledged N/A N/A
event point (status
or alarm).
BLOCK1 Harmony Block N/A N/A
number.
44 3BUA000937R301
Section 3 Common Parameters Common Properties

Comments
CURRENTEP/UNACK Unacknowledged N/A N/A
state of the event
point currently
determining the
priority.
DESCRIPTION Description of tag. Description String[40] Supported upto 40
characters
DISEST1 Tag is N/A N/A
disestablished.
INHB Overall inhibit N/A N/A
state.
INHBAUTO Events are N/A N/A
inhibited by an
other tag.
INHBMAN Manual inhibit N/A N/A
status.
INHBTAG Inhibiting N/A N/A
tag.property
reference.
INHBVAL Inhibit value. N/A N/A
LAST_PUT_TIME Time of last put. N/A N/A
LOOP Harmony loop N/A N/A
number.
MODULE1 Harmony module N/A N/A
number.
NAME Object name. Name String[30]
NODE Harmony node N/A N/A
number.
3BUA000937R301 45
Common Properties Section 3 Common Parameters

Comments
OBJECTID Unique object ID. N/A N/A
PRI Overall tag alarm N/A N/A
priority.
PTINDEX1 ICI index where N/A N/A
tag is established.
QUALITY Composite quality. This can be dint
achieved by
mapping to
parameter.quality
code
QUALITY:S Text version of N/A N/A
quality.
SERVER Name of Server N/A N/A
that the tag is
assigned to.
SERVERID UUID of Server N/A N/A
that the tag is
assigned to.
SPECSRCVD1 Blockware N/A N/A
specifications
received.
SPECTIMESTAMP1,2 Time of last spec N/A N/A
exception from
blockware.
SUBSTITUTED1 Tag values have N/A N/A
been substituted.
SUSPENDED1 Scanning enabled. N/A N/A
46 3BUA000937R301
Section 3 Common Parameters Common Properties

Comments
TEMPLATEID Object ID of the N/A
template used to
create this tag.
TYPE Object type name. N/A N/A
TYPEID Object type ID. N/A N/A
UNACK Unacknowledged UnAck bool
alarm.
USERDATA Writable user data N/A N/A
field.
USERTEXT User specific text N/A N/A
(optional).
XR_COUNT1 Number of Real N/A N/A
Time Data events.
N/A N/A OutA dword New parameter of
data type dword for
indicating output
alarm status. Present
in all faceplate Blocks
except REMSET.
N/A N/A AEClass dint The class for all
alarms in the object.
Range 1-9999.
Present in all
faceplate Blocks
except REMSET.
N/A N/A OutQ dword New parameter of
data type dword for
indicating output
quality
3BUA000937R301 47
Common Analog Properties Section 3 Common Parameters
Common Analog Properties

Table 3 lists the common analog properties which includes the data type, description
and equivalent parameter in INFI90FCLib Library. The REMSET Function Block is
an exception to all Analog Function Blocks.
Table 3. Analog Properties
Console Database Parameters as Type

OPC Property Name Comments
Name in INFI90FCLib String
ALMACKBC Broadcast alarm N/A N/A
acknowledge
events.
CALIBSTS Calibration status. N/A N/A
HIGH/ACKR Acknowledge AckReqH bool
required.
HIGH/ACT Active. N/A N/A
HIGH/ALARM Alarm state. N/A N/A
HIGH/ALMEN Alarm event. EnableH bool
HIGH/AREF Associated value. N/A N/A
HIGH/COM Current event N/A N/A
comment.
HIGH/COM0 Normal status MsgRtn String[60]
comment.
HIGH/COM1 Active state MsgH String[60]
comment.
HIGH/COMP Complement input N/A N/A
signal.
HIGH/DESCRIPTION Signal description. N/A N/A
HIGH/DUAL Dual acting event. N/A N/A
HIGH/EN Enable. EnableH bool
48 3BUA000937R301
Section 3 Common Parameters Common Analog Properties
Table 3. Analog Properties (Continued)

HIGH/EPSCAT Sub category of N/A N/A
event point (high
limit).
HIGH/PRI Current event N/A N/A
priority.
HIGH/PRI0 Normal priority. AESevRtn dint
HIGH/PRI1 Active priority. AESevH dint
HIGH/SIG Boolean value. HiAlm bool
HIGH/SIG0 Inactive state N/A N/A
description.
HIGH/SIG1 Active state N/A N/A
description.
HIGH/SUP Event suppressed N/A N/A
by signal.
HIGH/UNACK Unacknowledged N/A N/A
alarm.
HIGH/UNACKEP Unacknowledged N/A N/A
event point (status
or alarm).
LEVELALM Level alarm N/A N/A
summary.
LOW/ACKR Acknowledge AckReqL bool
required.
LOW/ACT Active. N/A N/A
LOW/ALARM Alarm state. N/A N/A
LOW/ALMEN Alarm event. EnableL bool
3BUA000937R301 49
Common Analog Properties Section 3 Common Parameters

LOW/AREF Associated value. N/A N/A
LOW/COM Current event N/A N/A
comment.
LOW/COM0 Normal status MsgRtn String[60]
comment.
LOW/COM1 Active state MsgL String[60]
comment.
LOW/COMP Complement input N/A N/A
signal.
LOW/DESCRIPTION Signal description. N/A N/A
LOW/DUAL Dual acting event. N/A N/A
LOW/EN Enable. EnableL bool
LOW/EPSCAT Sub category of N/A N/A
event point (high
limit).
LOW/PRI Current event N/A N/A
priority.
LOW/PRI0 Normal priority. AESevRtn dint
LOW/PRI1 Active priority. AESevL dint
LOW/SIG Boolean value. LoAlm bool
LOW/SIG0 Inactive state N/A N/A
description.
LOW/SIG1 Active state N/A N/A
description.
LOW/SUP Event suppressed N/A N/A
by signal.
50 3BUA000937R301
Section 3 Common Parameters Common Analog Properties

LOW/UNACK Unacknowledged N/A N/A
alarm.
LOW/UNACKEP Unacknowledged N/A N/A
event point (status
or alarm).
PV/DESCRIPTION Signal description. N/A N/A
PV/FOR Formatting PVDecimal dint Only represents
information. number of decimal
places
PV/PERCENT Signal (SIG) as a N/A N/A
percentage of span.
PV/SIG:QS Quality string. N/A N/A
PV/SPAN Difference between N/A N/A
low and high
ranges.
3BUA000937R301 51
Common Digital Properties Section 3 Common Parameters
Common Digital Properties

Table 4 lists the common digital properties which includes the data type, description
and equivalent parameter in INFI90FCLib Library.
Table 4. Digital Properties

ALMACKBC Broadcast alarm N/A
acknowledge
events.
OUT/ACKR Acknowledge AckReq bool
required.
OUT/ACT Active. N/A N/A
OUT/ALARM Alarm state. N/A N/A
OUT/ALMEN Alarm event. EnableAlm bool
OUT/AREF Associated value. N/A N/A
OUT/COM Current event N/A N/A
comment.
OUT/COM0 Normal status MsgRtn dint
comment.
OUT/COM1 Active state Message String[60]
comment.
OUT/COMP Complement input N/A N/A
signal.
OUT/DESCRIPTION Signal description. N/A N/A
OUT/DUAL Dual acting event. N/A N/A
OUT/EN Enable. EnableAlm bool
52 3BUA000937R301
Section 3 Common Parameters Common Digital Properties
Table 4. Digital Properties (Continued)

OUT/EPSCAT Sub category of N/A N/A
event point (high
limit).
OUT/PRI Current event N/A N/A
priority.
OUT/PRI0 Normal priority. AESevRtn dint
OUT/PRI1 Active priority. AESeverity dint
OUT/SIG0 Inactive state LSD0 string Supported
description. through
General
properties
Aspect
OUT/SIG1 Active state LSD1 string Supported
description. through
General
properties
Aspect
OUT/SUP Event suppressed N/A N/A
by signal.
OUT/UNACK Unacknowledged N/A N/A
alarm.
OUT/UNACKEP Unacknowledged N/A N/A
event point (status
or alarm).
STATECHANGE/ACKR Acknowledge N/A N/A
required.
STATECHANGE/ACT Active. N/A N/A
STATECHANGE/ALARM Alarm state. N/A N/A
3BUA000937R301 53

STATECHANGE/ALMEN Alarm event. N/A N/A
STATECHANGE/AREF Associated value. N/A N/A
STATECHANGE/COM Current event N/A N/A
comment.
STATECHANGE/COM0 Normal status N/A N/A
comment.
STATECHANGE/COM1 Active state N/A N/A
comment.
STATECHANGE/COMP Complement input N/A N/A
signal.
STATECHANGE/DESCRIPTION Signal description. N/A N/A
STATECHANGE/DUAL Dual acting event. N/A N/A
STATECHANGE/EN Enable. EnableEvt bool
STATECHANGE/EPSCAT Sub category of N/A N/A
event point (high
limit).
STATECHANGE/PRI Current event N/A N/A
priority.
STATECHANGE/PRI0 Normal priority. N/A N/A
STATECHANGE/PRI1 Active priority. N/A N/A
STATECHANGE/SIG Boolean value. N/A N/A
STATECHANGE/SIG0 Inactive state N/A N/A
description
STATECHANGE/SIG1 Active state N/A N/A
description.
54 3BUA000937R301
Section 3 Common Parameters Common Digital Properties

STATECHANGE/SUP Event suppressed N/A N/A
by signal
STATECHANGE/UNACK Unacknowledged N/A N/A
alarm.
STATECHANGE/UNACKEP Unacknowledged N/A N/A
event point (status
or alarm).
3BUA000937R301 55
56 3BUA000937R301
Section 4 Design Differences
Specification Handling
In the Harmony system, FB Inputs are referred to as Specifications (Specs). Specs
are divided into four categories based on the possible data sources and if it can be
modified during runtime.
• Input Spec - The only data source is FB Outputs. An FB Input Spec is
connected to some FB Output.
• Configured Spec - The data source is the Control Engineer (through the
Engineering Environment). The Control Engineer specifies the value offline
and the value remains unchanged during the execution of that version of the
configuration. It cannot be changed while in execute mode.
• Tunable (Not Adaptable) Spec - The possible data sources are the Control
Engineer (through the Engineering Environment) and the Operator (through the
Operations Environment). The Control Engineer specifies the initial value. The
Operator may subsequently change the value online and during execute mode.
The nonadaptable specifications cannot be adapted by another Block value.
• Tunable (Adaptable) Spec - The possible data sources are the Control
Engineer (through the Engineering Environment), the Operator (through the
Operations Environment) and FB Outputs (through the Adapt FB (FC 24)). If a
Tunable/Adaptable Spec is not Adapted (that is, not connected to an Adapt
FB), the Spec behaves as a Tunable Spec. If a Tunable/Adaptable Spec is
Adapted, the Spec behaves as an Input Spec.
The following are three Spec categories which are implemented for INFI90FCLib
Library:
• Input Spec - Same as Harmony Input Specs. The difference is that even if
these specs are not connected to a Block output, the complier does not generate
3BUA000937R301 57
an error and a Control Engineer can change these values from the engineering
workplace.
• Constant Spec - Similar to Harmony Configured Spec. The only difference is
that the Control Builder does not restrict the Control Engineer to modify these
values in runtime. Changing these values does not affect the FB functioning
until a cold restart is given.
• Tunable Spec - Similar to Harmony Tunable (Adaptable) Spec.
Segment Block FC82 and Executive Block (FC81) and

Extended Executive Block (FC90) Implementation
Segment control block is no longer supported in INFI90FCLib Library. Some
of the functionalities are now distributed across different function blocks in the
library. Some of them are supported by the Control Builder. Table 5 lists the
Harmony specifications and equivalent parameters in INFI90FCLib Library for
Function code 82.
Table 5. Harmony Specifications and Equivalent Parameters in INFI90FCLib for FC 82
Harmony INFI90FCLib
Spec Type Comments
Specifications Parameters
S1 Note1
S2 In AC800M, (Task Properties - Interval Time)
specified in Control Builder replaces the
functionality of 'target period' in Composer.
S3 In AC800M, 'segment priority' of a task is specified
in Control Builder (Task Properties - Priority)
replaces the functionality of Segment priority.
S4 Note1
S5 In Harmony, S5 applied to a Segment (task). In
INFI90FCLib, this Spec is replaced by the ExtRst
Parameter of the DeltaPID and ErrPID FB. This
Parameter is provided in each instance of ErrPID
and DeltaPID FB.
58 3BUA000937R301
Section 4 Design Differences Segment Block FC82 and Executive Block (FC81) and Extended
Table 5. Harmony Specifications and Equivalent Parameters in INFI90FCLib for FC 82
Harmony INFI90FCLib
Spec Type Comments
S6 In Harmony, S6 applied to a Segment (task). In
INFI90FCLib, this Spec is replaced by the MaxD
Parameter of the DeltaPID and ErrPID FB. This
Parameter is provided in each instance of ErrPID
and DeltaPID FB.
S7 Note1
S8 Note1
S9 Note1
S10 In Harmony, S10 applied to a Segment. In
INFI90FClib, this Spec is replaced by parameters of
the individual Function Blocks that use alarm
deadbands.
S11 In Harmony, S11 applied to a Segment. In
INFI90FCLib, this Spec is replaced by parameters
of the individual Function Blocks that use alarm
deadbands.
S12 Note1
S13 Note1
S14 Note1
S15 Note1
N Note1
N +1 Note1
N +2 Note1
N +3 Note1
N +4 Note1
Note 1 INFI90FCLib has no equivalent functionality.
3BUA000937R301 59
The INFI90FCLib Exec and ExExec FB's replace the Function code 81 and 90 in
harmony. StartUpInProgress functionality and Startup time are provided in the
global variable InfiAppData. StartUpInProgress functionality can be achieved even
without Exec and ExExec block.
Table 6 lists the different components of the global variable InfiAppData.
Table 6. Components of InfiAppData
Initial
Name Data type Attributes Description
value
HWStatus HWStatus retain HWStatus of local controller
ExecData InfiExecData
Table 7 lists the different components of the variable ExecData.
Table 7. Components of ExecData
Data Initial
Name Attributes Description
Type value
StartupInProgress bool retain false StartupInProgress
StartupTime dint retain 15000 msec
StartupState dint retain 0 0:Startup Needed
1: Startup in Progress
2: Startup Complete
ExecPresent bool retain false Used to detect multiple Exec FB's in the
Application
StartupTimer Timer retain Indicates startup timer
zVarIDGen dint coldretain 1 ID generator for zVars
zBlkIDGen dint coldretain 1 ID generator for zBlks
60 3BUA000937R301
Section 4 Design Differences Specification Range Validity Check
StartupInProgress is True while an Infi90M application is in Startup mode. Startup

mode is initiated by a Download with Init or Coldstart and lasts for a user specified
length of time (default value is 15 seconds).
Specification Range Validity Check

For each spec which has standard Datatype and full range based on its Datatype, the
input value range validity and data type mismatch checking is done by Control
BuilderM.
For each Constant or Tunable Spec with a Range that is not full in comparison to the
Datatype range, there is an associated Variable inside the code that holds the actual
value of the Spec. When a FB transfers the Parameter value to the associated
variable, it performs a validity check on the value. If the Parameter value is valid, it
just copies the value to the variable. If the value is not valid, it substitutes the nearest
valid value for the invalid value. If the invalid value is between two valid values, it
uses the lower value. The Parameter value is not affected by this check.
The following are some examples:
1. The range is 0 to 100. The Parameter value is 110. The value of the Variable is
100.
2. Same as (1) but the value is -10. The value of the Variable is 0.
3. The valid values are 1, 2, 4. The Parameter value is 3. The value of the Variable
is 2.
Exception Report Handling

Exception Report Handling is not supported in 800xA system. The Function Blocks
are exposed through OPC properties which allows for a subscription mechanism to
collect and display the data from the controller.
3BUA000937R301 61
Execution Order Section 4 Design Differences
Execution Order
Using Control Builder as the Engineering Tool
When Control Builder is used as an engineering tool, the Block execution is
dependent on the position of the Block in the program pane. The execution for a
pane of program is shown in Figure 9.
When instantiating the Block in Control Builder, the order of instantiation
determines the order of execution. Once the order of execution is set it cannot be
changed in Control Builder.
Figure 9. Control Builder as an Engineering Tool
Using Function Designer as an Engineering Tool

In Function Designer (FD), the order of execution is independent of the order of
instantiation. The FD allows the user to modify the data flow order or the execution
62 3BUA000937R301
Section 4 Design Differences Control Interface Implementation in zBlocks
order. In the Control Builder, the order of execution cannot be changed once it is
fixed. Figure 10 shows a function designer in which the order can be set and
modified.
Figure 10. Function Designer as an Engineering Tool
Control Interface Implementation in zBlocks

For details on the control interface implementation in zBlocks, refer to
Batch90/UDF Migration.
OPC Error Indication In Graphical Interfaces

The OPC Error is indicated by a Red Cross line across the feedback indicators and
command buttons. All operations from the faceplate become ineffective. The
appearance of the faceplate during an OPC failure is shown in Figure 11.
3BUA000937R301 63
Quality Propagation and Indication Section 4 Design Differences
Figure 11. Faceplate of Device Driver with OPC Error Indication
Quality Propagation and Indication

The Bad quality error is shown by a text "XXX" with red color
foreground/background across the PV Advant text box and operation from the
faceplate becomes ineffective. The appearance of the faceplate during a bad quality
is shown in Figure 12.
64 3BUA000937R301
Section 4 Design Differences String Handling for Faceplates
Figure 12. Appearance of the Faceplate During a Bad Quality
String Handling for Faceplates

• The Property Translations and General Properties aspect is provided for each
digital Block (DADIG, DOL, DeviceDriver, MSDD, RCM, RMCB) in the
object type structure. The General Properties aspect has logic state descriptors
(LSD1, LSD0,FB1SIG0, FB1SIG1) that can be configured by the user.
• The Property Translations aspect consists of single strings (For example,
FB1SIG, FB2SIG, Value). These strings are configured with an expression to
select the respective logic state descriptor (FB1SIG0 or FB1SIG1, LSD1 or
LSD0) from the General properties aspect based on the value of the logic state
(For example, FB1, Out, RS). However, the user should not modify anything in
the Property Translations Aspect.
• Indicators (Feedback, Error indicators) in the faceplates are linked to single
string (FB1SIG, SRC, ERRCODE) available in Property Translations Aspect.
3BUA000937R301 65
String Handling for Faceplates Section 4 Design Differences
• Command Buttons and indicators (for logic state outputs like Out, RS) in the
faceplates are linked to strings (LSD1, LSD0) available in General Properties
Aspect. The user can configure the Property Translations and General
Properties aspects to inherit to all instances to have same logic states for every
Function Block. Otherwise they will have individually configured logic states.
The lookup table concept of Logic states descriptors is removed. They are all
configured on the instance. For example refer the below Figure 13 and Figure 14 for
RMCB.
Figure 13. General Properties Aspect
66 3BUA000937R301
Section 4 Design Differences String Handling for Faceplates
Figure 14. Property Translation Aspect
3BUA000937R301 67
String Handling for Faceplates Section 4 Design Differences
68 3BUA000937R301
Section 5 Device Driver
Comparison of Object View

Table 8. Visual Comparison of Device Driver Function Block
Reduced View Extended View
View in Composer
View in Composer
N/A
View in Control BuilderM
3BUA000937R301 69
Comparison of Object View Section 5 Device Driver
Table 8. Visual Comparison of Device Driver Function Block (Continued)
View in Function Designer
70 3BUA000937R301
Section 5 Device Driver Comparison of DeviceDriver Parameters
Comparison of DeviceDriver Parameters
Table 9. DeviceDriver Parameters
Harmony INFI90FCLib
Spec Type Comment
S1 CI Input
S2 FB1 Input
S3 FB2 Input
S4 COS Tune The mask are of data type dint. The
One's place and Hundred's place digits
entered are taken as mask other digits
are ignored.
S5 OP Input
S6 OS Input
N/A. EnableOS Constant Enable OS. True=Enable Remote,
False=Disable Remote.
S7 FBM0 Tune The mask are of data type dint. The last
2 digits entered are taken as mask other
digits are ignored.
S8 FBM1 Tune The mask are of data type dint. The last
2 digits entered are taken as mask other
digits are ignored.
S9 FBTime Tune
S10 N/A Input Not Implemented in INFI90FCLib
N O
N+1 ST
N/A OutA Alarm Status Output.
3BUA000937R301 71
Comparison of DeviceDriver Parameters Section 5 Device Driver
Table 10. DeviceDriver (Console Database)
OPC Property Console Database Parameters as Type

Comments
Name Name in INFI90FCLib String
NAME Name Name string[30]
DESCRIPTION Description Description string[40]
AUTO Automatic mode Auto Bool
FB1/COMP Complement input signal N/A N/A
FB1/DESCRIPTION Signal description N/A N/A
FB1/SIG Boolean value FB1 Bool
FB1/SIG0 Inactive state description FB1SIG0 String The logic state
descriptors LSD’s
are defined in the
DeviceDriver
String properties
Aspect of the
object.
FB1/SIG1 Active state description FB1SIG1 String The logic state
descriptors LSD’s
are defined in the
DeviceDriver
String properties
Aspect of the
object.
FB2/COMP Complement input signal N/A N/A
FB2/DESCRIPTION Signal description N/A N/A
FB2/SIG Boolean value FB2 Bool
72 3BUA000937R301
Section 5 Device Driver Differences in Functionality
Table 10. DeviceDriver (Console Database) (Continued)

Comments
FB2/SIG0 Inactive state description FB2SIG0 String The logic state
descriptors LSD’s
are defined in the
DeviceDriver
String properties
Aspect of the
object.
FB2/SIG1 Active state description FB2SIG1 String The logic state
descriptors LSD’s
are defined in the
DeviceDriver
String properties
Aspect of the
object.
FBSTS Current feedback status FBSts Bool
REDTAG/ACT Red tagging is active N/A N/A
REDTAG/KEY1 Red tag key 1 N/A N/A
REDTAG/KEY2 Red tag key 2 N/A
REDTAG/KEY3 Red tag key 3 N/A N/A
REMOTE Remote mode Remote Bool
STATUS_OVR Status overridden StatusOvr Bool
USERTYPE User type code (0 to 255) N/A N/A
Differences in Functionality
Refer comments column in Table 9 and Table 10.
3BUA000937R301 73
Differences in Graphical Interfaces Section 5 Device Driver
Differences in Graphical Interfaces

There are no differences in the graphical interface of this Function Block.
74 3BUA000937R301
Section 6 Div2Real
Table 11. Visual Comparison of Div2Real Function Block
View in Composer View in Composer
N/A
3BUA000937R301 75
Comparison of Div2Real Parameters Section 6 Div2Real
Comparison of Div2Real Parameters

Table 12. Div2Real Parameters
Harmony Specifications INFI90FCLib Parameters Spec Type Comment

S1 In1 Input
S2 In2 Input
S3 G Tune
N Out
76 3BUA000937R301
Section 7 HiSel
Table 13. Visual Comparison of HiSel Function Block
NA
View in Composer
N/A
3BUA000937R301 77
Comparison of HiSel Parameters Section 7 HiSel
Table 13. Visual Comparison of HiSel Function Block (Continued)

Comparison of HiSel Parameters

Table 14. HiSel Parameters

S1 In1 Input
S2 In2 Input
S3 In3 Input
S4 In4 Input
N Out
78 3BUA000937R301
Section 8 Lim
Table 15. Visual Comparison of Lim Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 79
Comparison of Lim Parameters Section 8 Lim
Table 15. Visual Comparison of Lim Function Block (Continued)

Comparison of Lim Parameters

Table 16. Lim Parameters

S1 In1 Input
S2 Max Tune
S3 Min Tunes
N Out
80 3BUA000937R301
Section 9 Mul2Real
Table 17. Visual Comparison of Mul2Real Function Block
N/A

3BUA000937R301 81
Comparison of Mul2Real Parameters Section 9 Mul2Real
Comparison of Mul2Real Parameters

Table 18. Mul2Real Parameters

S1 In1 Input
S2 In2 Input
S3 G Tune
N Out
82 3BUA000937R301
Section 10 MatrixAdd
Table 19. Visual Comparison of MatrixAdd Function Block
N/A
View in Composer
3BUA000937R301 83
Comparison of Object View Section 10 MatrixAdd
Table 19. Visual Comparison of MatrixAdd Function Block (Continued)
N/A
84 3BUA000937R301
Section 10 MatrixAdd Comparison of Object View
Table 19. Visual Comparison of MatrixAdd Function Block (Continued)
N/A
3BUA000937R301 85
Comparison of MatrixAdd Parameters Section 10 MatrixAdd
Comparison of MatrixAdd Parameters

Table 20. MatrixAdd Parameters

S1 A11 Input
S2 A12 Input
S3 A13 Input
S4 A21 Input
S5 A22 Input
S6 A23 Input
S7 A31 Input
S8 A32 Input
S9 A33 Input
S10 B11 Input
S11 B12 Input
S12 B13 Input
S12 B21 Input
S14 B22 Input
S15 B23 Input
S16 B31 Input
S17 B32 Input
S18 B33 Input
N C11
N+1 C12
N+2 C13
86 3BUA000937R301
Section 10 MatrixAdd Comparison of MatrixAdd Parameters
Table 20. MatrixAdd Parameters (Continued)
N+3 C21
N+4 C22
N+5 C23
N+6 C31
N+7 C32
N+8 C33
3BUA000937R301 87
Comparison of MatrixAdd Parameters Section 10 MatrixAdd
88 3BUA000937R301
Section 11 LoSel
Table 21. Visual Comparison of LoSel Function Block
N/A
View in Composer
N/A
3BUA000937R301 89
Comparison of LoSel Parameters Section 11 LoSel
Table 21. Visual Comparison of LoSel Function Block
Comparison of LoSel Parameters

Table 22. LoSel Parameters

S1 In1 Input
S2 In2 Input
S3 In3 Input
S4 In4 Input
N Out
90 3BUA000937R301
Section 12 MatrixMul
Table 23. Visual Comparison of MatrixMul Function Block
N/A
View in Composer
3BUA000937R301 91
Comparison of Object View Section 12 MatrixMul
Table 23. Visual Comparison of MatrixMul Function Block (Continued)
N/A
92 3BUA000937R301
Section 12 MatrixMul Comparison of Object View
Table 23. Visual Comparison of MatrixMul Function Block (Continued)
N/A
3BUA000937R301 93
Comparison of MatrixMul Parameters Section 12 MatrixMul
Comparison of MatrixMul Parameters

Table 24. MatrixMul Parameters

S1 A11 Input
S2 A12 Input
S3 A13 Input
S4 A21 Input
S5 A22 Input
S6 A23 Input
S7 A31 Input
S8 A32 Input
S9 A33 Input
S10 B11 Input
S11 B12 Input
S12 B13 Input
S12 B21 Input
S14 B22 Input
S15 B23 Input
S16 B31 Input
S17 B32 Input
S18 B33 Input
N C11
N+1 C12
N+2 C13
94 3BUA000937R301
Section 12 MatrixMul Comparison of MatrixMul Parameters
Table 24. MatrixMul Parameters (Continued)
N+3 C21
N+4 C22
N+5 C23
N+6 C31
N+7 C32
N+8 C33
3BUA000937R301 95
Comparison of MatrixMul Parameters Section 12 MatrixMul
96 3BUA000937R301
Section 13 ElapTimer

Table 25. Visual Comparison of ElapTimer Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 97
Comparison of ElapTimer Parameters Section 13 ElapTimer
Table 25. Visual Comparison of ElapTimer Function Block (Continued)
Comparison of ElapTimer Parameters
Table 26. ElapTimer Parameters
Harmony INFI90FCLib Spec

Comment
Specifications Parameters Type
S1 Rst Input
S2 H Input
S3 Units Constant
S4 Alm Tune
S5 RV Tune
98 3BUA000937R301
Section 13 ElapTimer Differences in Functionality
Table 26. ElapTimer Parameters (Continued)

Comment
S6 Typ Constant For this Function Block the parameter Typ is a
constant spec. Any change in the values of this
parameter is effective only after a download with
cold restart is given. The value for parameter
Typ is checked for validity inside the code. The
valid values for this parameter are
000,001,101,100. For all values above 101, 101
is taken as the value for all values greater than
001 and less than 100, 001 is assumed to be
the value.
N V N/A The output V of ElapTimer Function Block in
INFI90FCLib is having range of 0.0 to
8.64E+13. In composer the range of output V is
0.0 to 9.18E+18. Set Typ parameter to 000 (Up
timer with tune), if RV, the reset value is set to
more than 8.64E+13, then the output V value is
considered as 0.00 on tune operation. The timer
starts up count form 0.00.
N+1 A N/A
This FB has no changes in functionality in comparison to Harmony Function Code
086, Elapsed Timer.

3BUA000937R301 99
Differences in Graphical Interfaces Section 13 ElapTimer
100 3BUA000937R301
Section 14 INPOL

Table 27. Visual Comparison of INPOL Function Block
View in Composer
View in Composer
3BUA000937R301 101
Comparison of Object View Section 14 INPOL
Table 27. Visual Comparison of INPOL Function Block (Continued)
N/A
102 3BUA000937R301
Section 14 INPOL Comparison of Object View
Table 27. Visual Comparison of INPOL Function Block (Continued)
3BUA000937R301 103
Comparison of INPOL Parameters Section 14 INPOL
Comparison of INPOL Parameters

Table 28. INPOL Parameters
Harmony INFI90FCLib
Spec Type Comment
S1 X Input
S2 Y Input
S3 Xmin Constant
S4 Ymax Constant
S5 Xmax Constant
S6 Ymin Constant
S7 Z11 Tune
S8 Z12 Tune
S9 Z13 Tune
S10 Z14 Tune
S11 Z15 Tune
S12 Z21 Tune
S13 Z22 Tune
S14 Z23 Tune
S15 Z24 Tune
S16 Z25 Tune
S17 Z31 Tune
S18 Z32 Tune
S19 Z33 Tune
S20 Z34 Tune
S21 Z35 Tune
104 3BUA000937R301
Section 14 INPOL Differences in Functionality
Table 28. INPOL Parameters (Continued)
Harmony INFI90FCLib
Spec Type Comment
S22 Z41 Tune
S23 Z42 Tune
S24 Z43 Tune
S25 Z44 Tune
S26 Z45 Tune
S27 Z51 Tune
S28 Z52 Tune
S29 Z53 Tune
S30 Z54 Tune
S31 Z55 Tune
N Out
N+1 B
This FB has no changes in functionality in comparison to Harmony Function
Code168.

3BUA000937R301 105
Differences in Graphical Interfaces Section 14 INPOL
106 3BUA000937R301
Section 15 DelayReal

Table 29. Visual Comparison of DelayReal Function Block
View in Composer
View in Composer
3BUA000937R301 107
Comparison of Object View Section 15 DelayReal
Table 29. Visual Comparison of DelayReal Function Block (Continued)
N/A
108 3BUA000937R301
Section 15 DelayReal Comparison of DelayReal parameters
Comparison of DelayReal parameters

Table 30. DelayReal Parameters
Harmony INFI90FCLib
Spec Type Comment
S1 X Input
S2 Rate Input
S3 TS Input
S4 L Constant
S5 N Constant
N Out
Code58.

3BUA000937R301 109
Differences in Graphical Interfaces Section 15 DelayReal
110 3BUA000937R301
Section 16 FnGen

Table 31. Visual Comparison of FnGen Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 111
Comparison of Object View Section 16 FnGen
Table 31. Visual Comparison of FnGen Function Block (Continued)
112 3BUA000937R301
Section 16 FnGen Comparison of FnGen parameters
Comparison of FnGen parameters
Table 32. FnGen parameters
Harmony INFI90FCLib
Spec Type Comment
S1 In Input
S2 X1 Tune
S3 Y1 Tune
S4 X2 Tune
S5 Y2 Tune
S6 X3 Tune
S7 Y3 Tune
S8 X4 Tune
S9 Y4 Tune
S10 X5 Tune
S11 Y5 Tune
S12 X6 Tune
S13 Y6 Tune
N Out
Code1.

3BUA000937R301 113
Differences in Graphical Interfaces Section 16 FnGen
114 3BUA000937R301
Section 17 Integrator

Table 33. Visual Comparison of Integrator Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 115
Comparison of Integrator Parameters Section 17 Integrator
Table 33. Visual Comparison of Integrator Function Block (Continued)
Comparison of Integrator Parameters
Table 34. Integrator Parameters
Harmony INFI90FCLib
Spec Type Comment
S1 PV Input
S3 IC Input
S4 TS Input
S2 Typ Constant
S5 HiLim Tune
S6 LOLim Tune
116 3BUA000937R301
Section 17 Integrator Differences in Functionality
Table 34. Integrator Parameters (Continued)
Harmony INFI90FCLib
Spec Type Comment
S7 Gain Tune
S8 AutoRst Tune
N Out
N+1 Q
Code166.

3BUA000937R301 117
Differences in Graphical Interfaces Section 17 Integrator
118 3BUA000937R301
Section 18 MovAvg

Table 35. Visual Comparison of MovAvg Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 119
Comparison of MovAvg Parameters Section 18 MovAvg
Table 35. Visual Comparison of MovAvg Function Block (Continued)
Comparison of MovAvg Parameters
Table 36. MovAvg Parameters
Harmony INFI90FCLib
Spec Type Comment
S1 In Input
S4 TS constant
S2 Num constant The parameter Num is a constant
spec. Any change in the values of
this parameter take effect only
after a download with cold restart
is given. The value for parameter
Num is checked for validity inside
the code. The valid values for this
parameter are from 1 to 255. For
all values above 255, 255 is taken
as the value and for values less
than 1, 1 is assumed to be the
value.
120 3BUA000937R301
Section 18 MovAvg Differences in Functionality
Table 36. MovAvg Parameters
Harmony INFI90FCLib
Spec Type Comment
S3 SI Tune
N Out
0165, Moving Average.

3BUA000937R301 121
Differences in Graphical Interfaces Section 18 MovAvg
122 3BUA000937R301
Section 19 DSum

Table 37. Visual Comparison of DSum Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 123
Comparison of Object View Section 19 DSum
Table 37. Visual Comparison of DSum Function Block (Continued)
124 3BUA000937R301
Section 19 DSum Comparison of DSum Parameters
Comparison of DSum Parameters

Table 38. DSum Parameters
Harmony INFI90FCLib
Spec Type Comment
S1 In1 Input
S2 In2 Input
S3 In3 Input
S4 In4 Input
S5 G1 Tune
S6 G2 Tune
S7 G3 Tune
S8 G4 Tune
N Out
065, Digital Sum with Gain.

3BUA000937R301 125
Differences in Graphical Interfaces Section 19 DSum
126 3BUA000937R301
Section 20 SqRoot

Table 39. Visual Comparison of SqRoot Function Block
View in Composer
View in Composer
N/A

3BUA000937R301 127
Comparison of SqRoot Parameters Section 20 SqRoot
Comparison of SqRoot Parameters

Table 40. SqRoot Parameters
Harmony INFI90FCLib
Spec Type Comment
S1 In Input
S2 Gain Tune
N Out
007, Square root.

128 3BUA000937R301
Section 21 XferDint

Table 41. Visual Comparison of XferDint Function Block
N/A
View in Composer
N/A
N/A
3BUA000937R301 129
Comparison of XferDint Parameters Section 21 XferDint
Comparison of XferDint Parameters

Table 42. XferDint Parameters
Harmony INFI90FCLib
Spec Type Comment
S1 In1 Input
S2 In2 Input
S3 TS Input
N Out1
013, Integer Transfer.

130 3BUA000937R301
Section 22 XferBool

Table 43. Visual Comparison of XferBool Function Block
N/A
View in Composer
N/A
N/A
3BUA000937R301 131
Comparison of XferBool Parameters Section 22 XferBool
Comparison of XferBool Parameters

Table 44. XferBool (Parameters)
Harmony INFI90FCLib
Spec Type Comment
S1 In1 Input
S2 In2 Input
S3 TS Input
N Out
059, Digital Transfer.

132 3BUA000937R301
Section 23 TimerBool

Table 45. Visual Comparison of TimerBool Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 133
Comparison of TimerBool Parameters Section 23 TimerBool
Comparison of TimerBool Parameters

Table 46. TimerBool Parameters
Harmony INFI90FCLib
Spec Type Comment
S1 In Input No
S2 Typ Constant No
S3 TD Tune No
N Out No
035.

134 3BUA000937R301
Section 24 UpDnCount

Table 47. Visual Comparison of UpDnCount Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 135
Comparison of Object View Section 24 UpDnCount
Table 47. Visual Comparison of UpDnCount Function Block (Continued)
View in Function Designer View in Function Designer
136 3BUA000937R301
Section 24 UpDnCount Comparison of UpDnCount Parameters
Comparison of UpDnCount Parameters

Table 48. UpDnCount Parameters
Harmony INFI90FCLib
Spec Type Comment
S1 Up Input
S2 Dwn Input
S3 Rst Input
S4 Hold Input
S5 RV Tune
S6 HA Tune
S7 LA Tune
N V
N+1 H
N+2 L
085.

3BUA000937R301 137
Differences in Graphical Interfaces Section 24 UpDnCount
138 3BUA000937R301
Section 25 XferReal

Table 49. Visual Comparison of XferReal Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 139
Comparison of XferReal parameters Section 25 XferReal
Comparison of XferReal parameters

Table 50. XferReal Parameters
Harmony INFI90FCLib
Spec Type Comment
S1 In1 Input
S2 In2 Input
S3 TS Input
S4 TC1 Tune
S5 TC2 Tune
N Out1
In the INFI90FCLib, when the time constants TC1 or TC2 are set as negative, the
output begins to move away from the input instead of moving towards the input
value. The output value increases till it reaches the overflow state.
In Harmony, if In1 = 100, In2 = 0, Out = 100, TC1= -1, TC2 = -1, and TS = 0, when
TS is switched to 1, the output begins to move away from In2, that is, the output It
starts to increase from 100 till its maximum value, Once it reaches maximum value
it swings to In2 and Out = In2 = 0. This behavior does not occur in INFI90FCLib
XferReal.

140 3BUA000937R301
Section 26 LeadLag

Table 51. Visual Comparison of LeadLag Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 141
Comparison of LeadLag Parameters Section 26 LeadLag
Comparison of LeadLag Parameters

Table 52. LeadLag Parameters
Harmony INFI90FCLib
Spec Type Comment
S1 In Input
S2 TS Input
S3 TC1 Tune
S4 TC2 Tune
N Out
There is a difference in functionality when the lag time constant TC2 is set negative.
The output begins to move away from the input instead of moving towards the input
value. The output increases till it reaches the overflow state.
In Harmony if the lag time constant is set to negative, the output increases to the
maximum value and stays constant. If it reaches the minimum value, the value is
reset and it starts moving towards minimum negative value.

142 3BUA000937R301
Section 27 Sum2Real

Table 53. Visual Comparison of Sum2Real Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 143
Comparison of Sum2Real parameters Section 27 Sum2Real
Comparison of Sum2Real parameters

Table 54. Sum2Real Parameters
Harmony INFI90FCLib
Spec Type Comment
S1 In1 Input
S2 In2 Input
S3 G1 Tune
S4 G2 Tune
N Out
Code15.

144 3BUA000937R301
Section 28 MuxReal

Table 55. Visual Comparison of MuxReal Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 145
Comparison of MuxReal Parameters Section 28 MuxReal
Table 55. Visual Comparison of MuxReal Function Block (Continued)
N/A
Comparison of MuxReal Parameters
Table 56. MuxReal Parameters
Harmony INFI90FCLib
Spec Type Comment
S1 InGrp.In0 Input The Input Parameter S1-S10 of Real
signal multiplexer is replaced by one
S2 InGrp.In1 Input
single Extensible parameter InGrp.
S3 InGrp.In2 Input InGrp is of Muxreal10 datatype
which consists of group of 10 real
S4 InGrp.In3 Input input parameter In0, In1...…In9. The
S5 InGrp.In4 Input ten values in the master Block are
zero through nine. The range of
S6 InGrp.In5 Input parameters associated with the next
Block in the link list is ten through 19,
S7 InGrp.In6 Input
and so on. If several Blocks are in
S8 InGrp.In7 Input series, the output always comes
from the first Block in the series. The
S9 InGrp.In8 Input output of the remaining blocks in the
S10 InGrp.In9 Input series are unused.
146 3BUA000937R301
Section 28 MuxReal Differences in Functionality
Table 56. MuxReal Parameters (Continued)
Harmony INFI90FCLib
Spec Type Comment
S11 IS Input
S12 Input This parameter is deleted. S12
parameter is used to indicate Block
address of next input Block in group.
A value of zero for this specification
indicates that there are no more
input Blocks in the group. In Muxreal
this feature is not required as all the
Ingrp comes under the same Block
and is directed to one output.
N Out
In the INFI90FCLib library, when inserting a Block, set the size of the Block
according to the number of real inputs to connect. For example:
• To connect less than ten real inputs, set the size of the MuxReal Block to one.
• To connect more than ten real inputs, set the size of the MuxReal Block to two.
InGrp belongs to one real signal multiplexer Block. To connect more than one real
multiplexer, increase the Multisize of the MuxReal Block by 1.
The look of the MuxReal Block will not match the existing Real signal multiplexer
in harmony. In Harmony, if four real signal multiplexer Blocks are connected the
appearance is as shown in Figure 15, but in the INFI90FCLib Library the
appearance is as shown in Figure 16.
3BUA000937R301 147
Differences in Functionality Section 28 MuxReal
Figure 15. Appearance of RealSignal Multiplexer in Harmony
148 3BUA000937R301
Section 28 MuxReal Differences in Graphical Interfaces
Figure 16. Appearance of MuxReal in Function Designer

3BUA000937R301 149
Differences in Graphical Interfaces Section 28 MuxReal
150 3BUA000937R301
Section 29 DMuxReal

Table 57. Visual Comparison of DmuxReal Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 151
Comparison of DmuxReal Parameters Section 29 DMuxReal
Table 57. Visual Comparison of DmuxReal Function Block (Continued)

Comparison of DmuxReal Parameters
Table 58. DmuxReal Parameters

Comment
S1 In Input
S2 Typ Input
S3 Input Nxt-In Real signal Demultiplexer the Nxt
address of next input Block in group. A
Value of zero for this specification
indicates that there are no more Mux
Blocks in the group. In DemuxReal this
feature is not required as all the Outgrp
comes under the same Block.
152 3BUA000937R301
Section 29 DMuxReal Differences in Functionality
Table 58. DmuxReal Parameters (Continued)

Comment
N OutGrp.Out0 Output The Output Parameter N to N + 7 of Real
signal DeMultiplexer is replaced by one
N+1 OutGrp.Out1 Output
single Extensible parameter OutGrp.
N+2 OutGrp.Out2 Output OutGrp is of DeMuxreal10 datatype
which consists of group of 8 Real Output
N+3 OutGrp.Out3 Output parameter Out0, Out1...Out9.
This Function Block has no changes in functionality in comparison to Harmony
Function Code126, but the implementation of the function has been changed.
In Harmony, the real signal demultiplexer function code outputs Boolean signals
based on a real input value. The real value can be converted to Boolean values in
three modes (select, integer and BCD). An unlimited number of real signal
demultiplexer Blocks may be linked together in the select mode (demultiplex the
real input into the required number of Boolean outputs).
Up to four Blocks may be linked together in the integer and BCD modes for
demultiplexing. The first Block in the link list is the group master. The master
accepts the input signal and drives the outputs for the group.
In INFI90FCLib, when inserting a Block, set the size of the Block according to the
number of Boolean outputs to connect. For example:
• To connect less than ten boolean outputs, set the size of the DmuxReal Block to
one.
• To connect more than ten Boolean Outputs, set the size of the DmuxReal Block
to two.
3BUA000937R301 153
Real Signal Demultiplexer FC-126 behavior in Harmony Section 29 DMuxReal
OutGrp belongs to one Real Signal Demultiplexer Block. To connect more than one
real Signal Demultiplexer, increase the size of the DMuxReal Block.
Real Signal Demultiplexer FC-126 behavior in Harmony

Set S2 (Typ) = 2 which is BCD mode.
General Behavior
In BCD mode while connecting 1 Real Signal Demultiplexer the maximum input
value it can take is 99 and its equivalent BCD output is 10011001. If its more than
99, for example, if 101, the output will still show the same output 10011001. If four
Real Signal Demultiplexers are connected, the maximum value it can take is
99999999 and the output for all the four Realdemux = 10011001.
Behavior 1
In Harmony, connect 3 real signal demultiplexer and set the input value
S1 = 999999 and the output for all the three real signal demultiplexer = 10011001. If
S1 value is changed to 999990, the harmony controller automatically approximates
the value and changes the input to 999984 and produces the output. This is not the
case in 800Xa demuxReal Block.
Behavior 2
In Harmony, connect 4 Real Signal Demultiplexer and set the input value
S1= 999999 the output for all the three real signal demultiplexer are not equal to
10011001. It shows different output.
Behavior 3
With 4 Real Signal Demultiplexer connected and the input value S1 = 99999999 or
greater and the output for all the four Real demux is not equal to 10011001.
The output it showed was first Block = 10101111 and rest of the output pins were
set to True. Set maximum real value like S1 = 10000000000 then the output for all
the four RealDemux = 10011001.
154 3BUA000937R301
Section 29 DMuxReal Behavior 4
Behavior 4
With 4 Real Signal Demultiplexer connected and the input value S1 = 99999990
The output in 800xA Function Block’s first Block was 01001001 and the rest of the
3 RealDemux output was 10011001.
The output in harmony Function Block’s first Block was 10101111 and the rest of
the 3 RealDemux output was set to TRUE.
This behavior has been rectified in INFI90FC library DmuxReal Block.
The appearance of the DeMuxReal Block does not match the existing Real Signal
Demultiplexer in Harmony. In Harmony if four Real signal Demultiplexer Blocks
are connected, the appearance is as shown in Figure 17, but in the INFI90FCLib
Library the DeMuxReal appearance is as shown in Figure 18.
3BUA000937R301 155
Behavior 4 Section 29 DMuxReal
Figure 17. Appearance of RealSignalDemultiplexer in Harmony
156 3BUA000937R301
Section 29 DMuxReal Differences in Graphical Interfaces
Figure 18. Appearance of DmuxReal in Function Designer

3BUA000937R301 157
Differences in Graphical Interfaces Section 29 DMuxReal
158 3BUA000937R301
Section 30 MuxBool

Table 59. Visual Comparison of MuxBool Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 159
Comparison of MuxBool Parameters Section 30 MuxBool
Table 59. Visual Comparison of MuxBool Function Block (Continued)
N/A
Comparison of MuxBool Parameters
Table 60. MuxBool Parameters

Comment
S1 InGrp.In0 Input The Input Parameter S1-S10 of Boolean
signal multiplexer is replaced by one
S2 InGrp.In1 Input
single Extensible parameter InGrp. InGrp
S3 InGrp.In2 Input is of Muxbool10 datatype which consists
of group of 10 Boolean input parameter
S4 InGrp.In3 Input In0, In1...In9. The ten values in the
S5 InGrp.In4 Input master Block are zero through nine. The
range of parameters associated with the
S6 InGrp.In5 Input next Block in the link list is ten through
19, and so on. If several Blocks are in
S7 InGrp.In6 Input
series, the output always comes from the
S8 InGrp.In7 Input first Block in the series. The outputs of
the rest of the Blocks in the series are
S9 InGrp.In8 Input unused.
S10 InGrp.In9 Input
S11 IS Input
160 3BUA000937R301
Section 30 MuxBool Differences in Functionality
Table 60. MuxBool Parameters (Continued)

Comment
S12 input S12 parameter is used to indicate Block
indicates that there are no more input
Blocks in the group. In MuxBool this
feature is not required as all the Ingrp
comes under the same Block and is
directed to one output.
N Out
Code119, but the implementation of the function has been changed.
number of real inputs to connect. For example:
• To connect less than ten boolean inputs, set the size of the MuxBool Block to
one.
• To connect more than ten real inputs, set the size of the MuxBool Block to two.
InGrp belongs to one boolean signal multiplexer Block. To connect more than one
boolean signal multiplexer, increase the Multisize of the MuxBool Block by 1.
The appearance of the Muxbool Block will not match the existing Boolean signal
multiplexer in Harmony. In Harmony if four Boolean signal multiplexer Blocks are
connected, the appearance is as shown in the Figure 19, but in the INFI90FCLib
Library the appearance is as shown in Figure 20.
3BUA000937R301 161
Differences in Functionality Section 30 MuxBool
Figure 19. Appearance of Boolean Signal Multiplexer in Harmony
162 3BUA000937R301
Section 30 MuxBool Differences in Graphical Interfaces
Figure 20. Appearance of MuxBool in Function Designer

3BUA000937R301 163
Differences in Graphical Interfaces Section 30 MuxBool
164 3BUA000937R301
Section 31 RecipeReal

Table 61. Visual Comparison of RecipeReal Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 165
Comparison of RecipeReal Parameters Section 31 RecipeReal
Table 61. Visual Comparison of RecipeReal Function Block (Continued)
N/A
Comparison of RecipeReal Parameters
Table 62. RecipeReal Parameters

Comment
S1 ParGrp.Par0 Tune The Input Parameter S1-S10 of Real
Recipe Table is replaced by one single
S2 ParGrp.Par1 Tune
Extensible parameter ParGrp. ParGrp is
S3 ParGrp.Par2 Tune of Parreal10 datatype which consists of
group of 10 real input parameter Par0,
S4 ParGrp.Par3 Tune Par1...Par9. The ten values in the
S5 ParGrp.Par4 Tune master Block are zero through nine.
The range of parameters associated
S6 ParGrp.Par5 Tune with the next Block in the link list is ten
through 19, and so on. If several Blocks
S7 ParGrp.Par6 Tune
are in series, the output always comes
S8 ParGrp.Par7 Tune from the first Block in the series. The
outputs of the rest of the Blocks in the
S9 ParGrp.Par8 Tune series are unused.
S10 ParGrp.Par9 Tune
166 3BUA000937R301
Section 31 RecipeReal Differences in Functionality
Table 62. RecipeReal Parameters (Continued)

Comment
S11 PS Input Yes
S12 Nxt Input Nxt-In RealRecipe Table the Nxt
indicates that there are no more input
Blocks in the group. In RecipeReal this
feature is not required as all the Ingrp
comes under the same Block and is
directed to one output.
S13 ES Input
S14 EPS Input
S15 ESV Input
N Out
Code118, but the implementation of the function has been changed.
number of real inputs to connect. For example:
• To connect less than ten real inputs, set the size of the RecipeReal Block to one.
• To connect more than ten real inputs, set the size of the RecipeReal Block to
two.
ParGrp belongs to one Real Recipe Block. To connect more than one Real Recipe
Block, increase the Multisize of the RecipeReal by 1.
The appearance of the RecipeReal Block will not match the existing
RealRecipeTable in Harmony. In Harmony if four RealRecipeTable Blocks is
3BUA000937R301 167
Differences in Functionality Section 31 RecipeReal
connected the appearance is as shown in the Figure 21, but in the INFI90FCLib
Library, RecipeReal appearance is as shown in Figure 22.
Figure 21. Appearance of Real Recipe in Harmony
168 3BUA000937R301
Section 31 RecipeReal Differences in Graphical Interfaces
Figure 22. Appearance of DmuxReal in Function Designer

3BUA000937R301 169
Differences in Graphical Interfaces Section 31 RecipeReal
170 3BUA000937R301
Section 32 HiLowComp

Table 63. Visual Comparison of HiLowComp Function Block
N/A

3BUA000937R301 171
Comparison of HiLowComp Parameters Section 32 HiLowComp
Comparison of HiLowComp Parameters

Table 64. HiLowComp Parameters
Harmony INFI90FCLib
Spec Type Comment
S1 In1 Input
S2 HiLim Tune
S3 LowLim Tune
N HA
N+1 LA
018, PID Error Input.

172 3BUA000937R301
Section 33 ErrPID

Table 65. Visual Comparison of ErrPID Function Block
View in Composer
View in Composer
3BUA000937R301 173
Comparison of Object View Section 33 ErrPID
Table 65. Visual Comparison of ErrPID Function Block (Continued)
N/A
174 3BUA000937R301
Section 33 ErrPID Comparison of ErrPID Parameters
Comparison of ErrPID Parameters

Table 66. ErrPID Parameters
Specifications
Parameters As in Type Of Console New/Changed
As in Functional
INFI90FCLib Spec Database Parameters
Harmony
Difference
(Yes/No)
ErrSig Input S1 N.A No No
TR Input S3 N.A No No
TS Input S4 N.A No No
ExtRst Constant N.A N.A Yes No
MaxD Constant N.A N.A Yes No
CO N N.A No No
LoopTune LoopTune N.A N.A No N.A.
LoopTune.K Tune S5 N.A No No
LoopTune.Kp Tune S6 N.A No No
LoopTune.Ki Tune S7 N.A No No
LoopTune.Kd Tune S8 N.A No No
LoopTune.HOLim Tune S9 N.A No No
LoopTune.LOLim Tune S10 N.A No No
LoopTune.PIDType - - N.A. Yes N.A.
New/Changed Parameters.
The parameters ExtRst and MaxD were previously supported in Segment control
function code (FC82) in Composer. Segment control block is no longer supported in
3BUA000937R301 175
Differences in Functionality Section 33 ErrPID
INFI90FCLib library and these two parameters are now provided as input
parameters in ErrPID block.
018, PID Error Input.

176 3BUA000937R301
Section 34 DeltaPID

Table 67. Visual Comparison of DeltaPID Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 177
Comparison of Object View Section 34 DeltaPID
Table 67. Visual Comparison of DeltaPID Function Block (Continued)
178 3BUA000937R301
Section 34 DeltaPID Comparison of DeltaPID Parameters
Comparison of DeltaPID Parameters

Table 68. DeltaPID Parameters
Harmony INFI90FCLib
Spec Type Comment
S2 SP Input
S1 PV Input
S3 TR Input
S4 TS Input
NA ExtRst Constant
NA MaxD Constant
N CO Output
N/A LoopTune LoopTune
S5 LoopTune.K Tune
S6 LoopTune.Kp Tune
S7 LoopTune.Ki Tune
S8 LoopTune.Kd Tune
S9 LoopTune.HOLim Tune
S10 LoopTune.LOLim Tune
S11 LoopTune.SPM Tune
S12 LoopTune.Dir Tune
N/A LoopTune.PIDType New parameter
New/Changed Parameters
The parameters ExtRst and MaxD were previously supported in Segment control
function code (FC82) in Composer. Segment control block is no longer supported in
INFI90FCLib library and these two parameters are now provided as input
parameters in DeltaPID block.
3BUA000937R301 179
Differences in Functionality Section 34 DeltaPID
019, PID (PV and SP).

180 3BUA000937R301
Section 35 QOR

Table 69. Visual Comparison of QOR Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 181
Comparison of Object View Section 35 QOR
Table 69. Visual Comparison of QOR Function Block (Continued)
182 3BUA000937R301
Section 35 QOR Comparison of QOR Parameters
Comparison of QOR Parameters

Table 70. QOR Parameters
Harmony INFI90FCLib
Spec Type Comment
S1 In1 Input
S2 In2 Input
S3 In3 Input
S4 In4 Input
S5 In5 Input
S6 In6 Input
S7 In7 Input
S8 In8 Input
S9 Mask Constant
S10 Mode Constant
N Out
This FB has no changes in functionality in comparison to Harmony Function Code.

3BUA000937R301 183
Differences in Graphical Interfaces Section 35 QOR
184 3BUA000937R301
Section 36 SRMem

Table 71. Visual Comparison of SRMem Function Block
N/A
3BUA000937R301 185
Comparison of SRMem Parameters Section 36 SRMem
Comparison of SRMem Parameters

Table 72. SRMem Parameters
Harmony INFI90FCLib
Spec Type Comment
S1 Set Input
S2 Rst Input
S3 Init Input
S4 Ovr Constant
N Out

186 3BUA000937R301
Section 37 TSTQ

Table 73. Visual Comparison of TSTQ Function Block
N/A
View in Composer
N/A
N/A
3BUA000937R301 187
Comparison of TSTQ Parameters Section 37 TSTQ
Comparison of TSTQ Parameters

Table 74. TSTQ Parameters

Comment
S1 InQ1 Input
S2 InQ2 Input
S3 InQ3 Input
S4 InQ4 Input
N Out

188 3BUA000937R301
Section 38 REMSET

Table 75. Visual Comparison of REMSET Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 189
Comparison of Object View Section 38 REMSET
Table 75. Visual Comparison of REMSET Function Block (Continued)
190 3BUA000937R301
Section 38 REMSET Comparison of REMSET Parameters
Comparison of REMSET Parameters

Table 76. REMSET Parameters

Comment
S1 EUD Constant Changed from Integer to string
S2 HoLim Tune
S3 LoLim Tune
S4 Init Constant
S5 TS Input
S6 TR Input
N Out
Table 77. REMSET (Console Database)
OPC
Console Database Parameters as in Type
Property Comments
Name INFI90FCLib String
Name
NAME Object name. Name string[30] Increased to 30
characters.
PV/DESCRIP Description of tag. Description string[40] Increased to 40
TION characters.
PV/SIG Analog Value Out real
PV/SIG:QS Quality string. N/A Not applicable
PV/HIGH High range of HOLim real
Signal.
PV/LOW Low range of LOLim real
Signal.
3BUA000937R301 191
Differences in Functionality Section 38 REMSET
Table 77. REMSET (Console Database) (Continued)
OPC
Console Database Parameters as in Type
Property Comments
Name INFI90FCLib String
Name
PV/UNITS Engineering Units EUD string[15] In Harmony this was an
Integer entered in
configuration, Now the
user enters the string
value directly.
PV/FOR Formating PVDecimal dint Only represents the
Information number of decimals, width
is not being supported.
TRACKING Value is tracking an TS bool
input value.
ALMACKBC N/A N/A Not supported
BAD/ N/A N/A Not applicable

192 3BUA000937R301
Section 39 RCM

Table 78. Visual Comparison of RCM Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 193
Comparison of Object View Section 39 RCM
Table 78. Visual Comparison of RCM Function Block (Continued)
194 3BUA000937R301
Section 39 RCM Comparison of RCM Parameters
Comparison of RCM Parameters

Table 79. RCM Parameters
Harmony INFI90FCLib
Spec Type Comment
S1 Set Input
S2 Perm Input
S3 Rst Input
S4 Ovr Input
S5 Init Input
S6 FB Input
S7 Alm Input
S8 Typ Input This parameter acts only as
a feedback indicator. When
it is set true, it displays the
feedback indicator (arrow)
in the faceplate elements.
N Out Output
Table 80. RCM (Console Database)
OPC Property Console Parameters as in Type

Comments
Name Database Name INFI90FCLib String
NAME Name Name String[30]
DESCRIPTION Description Description String[40]
FB1/COMP Complement input N/A
signal.
FB1/DESCRIPTION Signal description. N/A
3BUA000937R301 195
Comparison of RCM Parameters Section 39 RCM
Table 80. RCM (Console Database) (Continued)

Comments
FB1/SIG0 Boolean value. FB1SIG0 Bool The logic state
descriptors LSDs’
are defined in the
RCM String
properties Aspect of
the object.
FB1/SIG1 Active state FBISIG1 String The logic state
description. descriptors LSDs’
are defined in the
RCM String
the object.
FB1/SIG Boolean Value. Bool
OUTOVR State is Override
overridden.
REDTAG/ACT Red tagging is N/A
active.
REDTAG/KEY1 Red tag key 1. N/A
REDTAG/KEY2 Red tag key 2. N/A
REDTAG/KEY3 Red tag key 3. N/A l
RESCMD Reset Command ResetCmd Bool
received.
RESIN Logic reset input Rst Bool
received.
SETCMD Set Command SetCmd Bool
received.
SETIN Logic Set input Set Bool
received.
196 3BUA000937R301
Section 39 RCM Differences in Functionality
Table 80. RCM (Console Database) (Continued)

Comments
SETPER Set permissive. Perm
USERTYPE User type code (0 N/A String
to 255).
OUT/SIG Boolean value Out Bool
STATECHANGE/EN Enable EnableEvt Bool If alarms are
disabled and
StateChange is
enabled then events
are generated.
Refer the comments column in Table 79 and Table 80.

In Harmony connect system there is no feedback indicator in the faceplate elements.
In INFI90FCLib Library, an arrow has been added in the RCM faceplate elements to
indicate the feedback status. The appearance of the arrow in the faceplate can be
controlled by the parameter Typ.
3BUA000937R301 197
Differences in Graphical Interfaces Section 39 RCM
198 3BUA000937R301
Section 40 DOL

Table 81. Visual Comparison of DOL Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 199
Comparison of Object View Section 40 DOL
Table 81. Visual Comparison of DOL Function Block (Continued)
200 3BUA000937R301
Section 40 DOL Comparison of DOL Parameters
Comparison of DOL Parameters

Table 82. DOL Parameters

Comment
S1 In Input
S2 AlmDef Tune Parameter Spec Type changed from constant to
tune. Whenever AlmDef changes value from 0 or
1 to 2, alarm states are cleared on the output.
N Out
Table 83. DOL (Console Database)
Console Parameters as Type

Database Name in INFI90FCLib String
OUT/ACKR Acknowledge AckReq bool
required.
OUT/COM1 Active state State1Msg string[60]
comment.
OUT/COM0 Normal status State0Msg string[60]
comment.
OUT/EN Enable. EnableAlm bool
OUT/PRI1 Active priority. AESeverity dint
OUT/PRI0 Normal priority. AESevRtn dint
OUT/SIG Boolean value N/A bool
3BUA000937R301 201
Comparison of DOL Parameters Section 40 DOL
Table 83. DOL (Console Database) (Continued)

OUT/SIG0 Inactive state LSD0 string The logic state
are defined in the
DOL String
the object.
OUT/SIG1 Active state LSD1 string The logic state
are defined in the
DOL String
the object.
OUT/UNACK Unacknowledged N/A
alarm.
STATECHANGE/COM1 Active status State1Msg string[60]
comment.
STATECHANGE/COM0 Normal state State0Msg string[60]
comment.
STATECHANGE/EN Enable. EnableEvt bool
STATECHANGE/PRI0 Normal priority. N/A dint
STATECHANGE/PRI1 Active priority. N/A dint
status.
required.
BAD/COM0 Normal status N/A
comment.
BAD/COM1 Active state N/A
comment.
202 3BUA000937R301
Section 40 DOL Differences in Functionality
Table 83. DOL (Console Database) (Continued)

BAD/EN Enable. EnableBQ bool
BAD/PRI1 Active priority. AESeverity dint
BAD/PRI0 Normal priority. AESevRtn dint
BAD/SIG Boolean value. QualFlag bool
BAD/UNACK Unacknowledged N/A
alarm.
QUALITY Composite N/A dint The composite
quality. quality is supported
by QualFlag.Quality
Code in PPA
N/A N/A FilterTime real New parameter.
Refer to Section 79,
Alarm and Event
Handling for detailed
functionality.

3BUA000937R301 203
Differences in Graphical Interfaces Section 40 DOL
204 3BUA000937R301
Section 41 AOL

Table 84. Visual Comparison of AOL Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 205
Comparison of Object View Section 41 AOL
Table 84. Visual Comparison of AOL Function Block (Continued)
206 3BUA000937R301
Section 41 AOL Comparison of AOL Parameters
Comparison of AOL Parameters

Table 85. AOL Parameters

Comment
S1 In Input
S2 EUD Tune Data type changed from Integer to String
S3 Zero Tune
S4 Span Tune
S5 HALim Tune
S6 LALim Tune
S7 N/A N/A Exception reporting is no longer supported, so
this parameter is removed
N Out N/A
Table 86 lists the Harmony console specifications and equivalent parameters/visible

variables in INFI90FCLib Library.
Table 86. AOL (Console Database)

Comments
PV/HIGH High range of PVHigh real
signal.
PV/LOW Low range of Zero real
signal.
PV/SIG Analog value. Out real
PV/UNITS Engineering units. EUD String[15] Changed data type
from Integer to String
HIGHLIM High alarm limit. HALim real
3BUA000937R301 207
Differences in Functionality Section 41 AOL
Table 86. AOL (Console Database) (Continued)

Comments
LOWLIM Low alarm limit. LALim real
N/A N/A InQ dword New parameter of data
type dword for input
quality
N/A N/A ALDB real This is a new
parameter (Previously
a specification that
came from the segment
control Block).
Code030.
208 3BUA000937R301
Section 42 Station

Table 87. Visual Comparison of Station Function Block
View in Composer
View in Composer
3BUA000937R301 209
Comparison of Object View Section 42 Station
Table 87. Visual Comparison of Station Function Block (Continued)
N/A
210 3BUA000937R301
Section 42 Station Comparison of Object View
Table 87. Visual Comparison of Station Function Block (Continued)
3BUA000937R301 211
Comparison of Station Parameters Section 42 Station
Comparison of Station Parameters

Table 88. Station Parameters
Harmony INFI90FCLib
Spec Type Comment
S1 PV Input
S2 RSP Input
S3 A Input
S4 TR Input
S5 TS Input
S6 Imode Constant Imode Ranges 1, 2, 3 are not
supported here. Only 5,6,7,8 are
supported in INFI90FCLib
S7 PVHA Tune
S8 PVLA Tune
S9 DEVA Tune
S10 PVSpan Tune Spectype was changed from
Configurable to Tune.
S11 PVZero Tune Spectype was changed from
S12 PVEUD Tune Data type changed from Integer to
String. Spectype was changed
from Configurable to Tune.
S13 SPSpan Tune Spectype was changed from
S14 SPZero Tune Spectype was changed from
212 3BUA000937R301
Section 42 Station Comparison of Station Parameters
Table 88. Station Parameters (Continued)
Harmony INFI90FCLib
Spec Type Comment
S15 SPEUD Tune Data type changed from Integer to
String. Spectype was changed
from Configurable to Tune.
S16 N/A Not Implemented in INFI90FCLib
S18 MI Input
S19 AX Input
S20 CX Input
S23 Typ Typ 1,2 are not supported
S24 EHA Input
S25 ELA Input
S26 EHD Input
S27 ELD Input
S28 AO Input
S29 TRS2 Input
S20 TRPV Input
N CO
N+1 SP
N+2 Auto
N+3 N/A Not Implemented in INFI90FCLib
3BUA000937R301 213
Table 88. Station Parameters (Continued)
Harmony INFI90FCLib
Spec Type Comment
N+4 CR
N+5 N/A Not Implemented in INFI90FCLib
Table 89. Station (Console Database)
Parameters/
Console Type
OPC Property Name Variables as in Comments
Database Name String
INFI90FCLib
AUTO Station Mode Auto bool
BYPASS Control Output is N/A bool
bypassed
CMPTRSTS Computer Signal N/A
is OK
CO/Description Signal description N/A
CO/FOR Formatting CODecimal dint Only represents
Information the number of
decimal places
CO/HIGH High range of COHigh real
signal
CO/LOW Low range of COLow real
signal
CO/PERCENT Signal (SIG) as a N/A
percentage of
span
214 3BUA000937R301
Table 89. Station (Console Database) (Continued)
Parameters/
Console Type
INFI90FCLib
CO/SIG Analog Value CO real
CO/SIG:QS Quality String N/A
CO/SPAN Difference N/A
between low and
high ranges
CO/UNITS Engineering Units N/A
DEVALM Deviation alarm N/A
summary
DEVALM/DESCRIPTION Signal description N/A
DEVLIM/FOR Formatting DevDecimal dint Only represents
decimal places
DEVLIM/HIGH High Range of DEVA real
signal
DEVLIM/LOW Low Range of NegDEVA real
signal
DEVLIM/PERCENT Signal (SIG) as a N/A
percentage of
span
DEVLIM/SPAN Difference N/A
between low and
high ranges
DEVLIM/UNITS Engineering Units N/A
HIGHDEV/ACKR Acknowledge AckReqHDev bool
Required
HIGHDEV/ACT Active N/A
3BUA000937R301 215
Parameters/
Console Type
INFI90FCLib
HIGHDEV/ALARM Alarm State HiDevAlarm bool
HIGHDEV/ALMEN Alarm Event N/A
HIGHDEV/AREF Associate Value N/A
HIGHDEV/COM Current Event N/A
Comment
HIGHDEV/COM0 Normal Status MsgRtn string[60]
Comment
HIGHDEV/COM1 Active State MsgHDev string[60]
Comment
HIGHDEV/COMP Complement input N/A
signal
HIGHDEV/DESCRIPTION Signal Description N/A
HIGHDEV/DUAL Dual acting event N/A
HIGHDEV/EN Enable EnableHDev bool
HIGHDEV/EPSCAT Sub category Of N/A
event point (high
limit)
HIGHDEV/PRI Current Event N/A
Priority
HIGHDEV/PRI0 Normal Priority N/A
HIGHDEV/PRI1 Active Priority AESevHDev dint
HIGHDEV/SIG Boolean Value HiDevAlarm bool
HIGHDEV/SIG0 Inactive State N/A
description
216 3BUA000937R301
Parameters/
Console Type
INFI90FCLib
HIGHDEV/SIG1 Active State N/A
description
HIGHDEV/SUP Event suppressed N/A
by signal
HIGHDEV/UNACK Unacknowledged N/A
alarm
HIGHDEV/UNACKEP Unacknowledged N/A
Event point
LOWDEV/ACKR Acknowledge AckReqLDev bool
Required
LOWDEV /ACT Active N/A
LOWDEV /ALARM Alarm State LoDevAlarm bool
LOWDEV /ALMEN Alarm Event N/A
LOWDEV /AREF Associate Value N/A
LOWDEV /COM Current Event N/A
Comment
LOWDEV /COM0 Normal Status MsgRtn string[60]
Comment
LOWDEV /COM1 Active State MsgLDev string[60]
Comment
LOWDEV /COMP Complement input N/A
signal
LOWDEV/DESCRIPTION Signal Description N/A
LOWDEV /DUAL Dual acting event N/A
LOWDEV /EN Enable EnableLDev bool
3BUA000937R301 217
Parameters/
Console Type
INFI90FCLib
LOWDEV /EPSCAT Sub category Of N/A
event point
(high limit)
LOWDEV /PRI Current Event N/A
Priority
LOWDEV /PRI0 Normal Priority AESevRtn dint
LOWDEV /PRI1 Active Priority AESevLDev dint
LOWDEV /SIG Boolean Value LoDevAlarm bool
LOWDEV /SIG0 Inactive State N/A
description
LOWDEV /SIG1 Active State N/A
description
LOWDEV /SUP Event suppressed N/A
by signal
LOWDEV /UNACK Unacknowledged N/A
alarm
LOWDEV /UNACKEP Unacknowledged N/A
Event point
MODELOCK Module has mode MODELOCK bool
locked
OUTSTS Handheld station N/A
has failed
OUTTRACKING Output is tracking TR real
an input value
RATIO Ratio Index StationRatio real
RATIO:QS Quality String N/A
218 3BUA000937R301
Parameters/
Console Type
INFI90FCLib
REDTAG/ACT Red Tagging N/A Not supported
active
REDTAG/KEY1 Red Tag Key 1 N/A
SP/Description Signal description N/A
SP /FOR Formatting SPDecimal dint Only represents
decimal places
SP /HIGH High range of SPHigh real
signal
SP /LOW Low range of SPZero real
signal
SP /PERCENT Signal(SIG) as a N/A
percentage of
span
SP /SIG Analog Value SP real
SP /SIG:QS Quality String N/A
SP /SPAN Difference N/A real
between low and
high ranges
SP /UNITS Engineering Units SPEUD string[15]
SPTRACKING SP Tracking TRS2 bool
enabled
STNLVL Station is under N/A
Computer control
3BUA000937R301 219
Parameters/
Console Type
INFI90FCLib
STNMODE Cascade or ratio StationMode bool
Mode selected
STNTYPE Station Type TypInternal real
STNTYPE:S Text Version of StationType string[25]
quality
TUNEBLK Block number of N/A
feedback's tuning
Block
PV/Description Signal description N/A
PV/UNITS Engineering Units PVEUD string[15] Data type changed
from Integer to
String
QUALITY:S Text version of N/A
quality
PV/HIGH High range of PVHA real
signal
PV/LOW Low range of PVLA real
signal
PV/SIG Analog value PV real
status
information the number of
decimal places
PV/SIG:QS Quality string N/A
HIGH/SIG Boolean value HiAlarm bool
220 3BUA000937R301
Parameters/
Console Type
INFI90FCLib
HIGHLIM High alarm limit PVHA real
LOW/SIG Boolean value LoAlm bool
LOWLIM Low alarm limit LALim real
N/A QualFlag bool Boolean value.
Depending upon
the value (False-
good quality, true-
bad quality)
indication "XXX" is
shown in the
faceplate as per
800xA standards.
HIGH/COM1 Active state MsgH string[60]
description
HIGH/PRI1 Active priority AESevH dint Priorities in
harmony connect
are mapped to
severity
parameters
HIGH/EN Enable EnableH bool
required
LOW/COM1 Active state MsgL string[60]
description
LOW/PRI1 Active priority AESevL dint Priorities in
harmony connect
are mapped to
severity
parameters
3BUA000937R301 221
Parameters/
Console Type
INFI90FCLib
LOW/EN Enable EnableL bool
required
BAD/PRI1 Active priority AESevBQ dint Priorities in
harmony connect
are mapped to
severity
parameters
BAD/EN Enable EnableBQ bool
required
HIGH/COM0, LOW/COM0 Inactive state MsgRtn string[60] Return message is
description the same for both
high and low alarm
HIGH/PRI0,LOW/PRI0, Normal priority AESevRtn dint Return severity is
BAD/PRI0 the same for both
high and low
alarms
N/A N/A LoopTune LoopTune New composite
parameter used
for Tuning purpose
from faceplate.
N/A N/A PVQ dword New parameter of
data type dword
for input quality
222 3BUA000937R301
Section 42 Station Differences in Functionality
Parameters/
Console Type
INFI90FCLib
N/A N/A HLALMDB real This is a new
parameter
(Previously value
of this
specification came
from segment
control Block).
N/A N/A DEVALMDB real This is a new
parameter
(Previously value
of this
specification came
from segment
control Block).
Refer comments in the Table 88 and Table 89.

The Extended view of the station faceplate has been changed to enhance the tuning
facility along with trend display. This gives the flexibility for the operator to tune
3BUA000937R301 223
Differences in Graphical Interfaces Section 42 Station
the parameters for any type of controllers (ErrPID, DeltaPID, APID, and ISC) from
the faceplate.
Figure 23. Extended View of the Station Faceplate
224 3BUA000937R301
Section 43 APID

Table 90. Visual Comparison of APID Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 225
Comparison of APID Parameters Section 43 APID
Table 90. Visual Comparison of APID Function Block (Continued)
Comparison of APID Parameters
Table 91. APID Parameters
Harmony INFI90FCLib
Spec Type Comment
S1 PV Input
S2 SP Input
S3 TR Input
226 3BUA000937R301
Section 43 APID Comparison of APID Parameters
Table 91. APID Parameters (Continued)
Harmony INFI90FCLib
Spec Type Comment
S4 TS Input
S5 ExtRst Input
S6 FF Input
S7 N/A
S8 N/A
S9 II Input
S10 DI Input
S18 Ver Constant
S19 Typ Constant
S22 N/A
S23 N/A
N CO
N+1 BI
N+2 BD
N/A OutA
Table 92. LoopTune (Components)
Harmony INFI90FCLib
Spec Type Comment
S11 K Tune
S12 Kp Tune
S13 Ki Tune
3BUA000937R301 227
Differences in Functionality Section 43 APID
Table 92. LoopTune (Components) (Continued)
Harmony INFI90FCLib
Spec Type Comment
S14 Kd Tune
S15 Ka Tune
S16 HOLim Tune
S17 LOLim Tune
S20 SPM Tune
S21 Dir Tune
Harmony FC156 supports two versions of the algorithm, an original version and a
new version. INFI90FCLib APID supports only the new version. Algorithm types
10, 11, 12, and 13 in Harmony FC 156 maps to types 0, 1, 2,and 3 respectively in
INFI90FCLib APID.

228 3BUA000937R301
Section 44 MSDD

Table 93. Visual Comparison of MSDD Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 229
Comparison of Object View Section 44 MSDD
Table 93. Visual Comparison of MSDD Function Block (Continued)
230 3BUA000937R301
Section 44 MSDD Comparison of MSDD Parameters
Comparison of MSDD Parameters

Table 94. MSDD Parameters
Harmony INFI90FCLib
Spec Type Comment
S1 I1 Input
S2 I2 Input
S3 F1 Input
S4 F2 Input
S5 F3 Input
S6 F4 Input
S7 OM0 Constant The mask is of data type dint. The right
most 3 digits entered are taken as
mask, other digits are ignored.
S8 OM1 Constant
S9 OM2 Constant
S10 OM3 Constant
S11 FM1 Tune The feedback mask is of data type dint.
The right most 4 digits entered are
taken as the feedback mask, other
digits are ignored.
S12 FM2 Tune
S13 FM3 Tune
S14 COSO Tune The parameter is of data type dint. The
right most 3 digits entered are taken as
input, other digits are ignored.
S15 MP Tune
S16 FBWait Tune
3BUA000937R301 231
Comparison of MSDD Parameters Section 44 MSDD
Table 94. MSDD Parameters (Continued)
Harmony INFI90FCLib
Spec Type Comment
S17 FltWait Tune
S18 N/A Constant
S19 Nxt1 Tune
S20 Nxt2 Tune
S21 Nxt3 Tune
S22 Ptime Tune
S23 IM Constant
S24 TS Tune
S25 Ovr Input
N CO1
N+1 CO2
N+2 CO3
N+3 ST
Table 95. MSDD (Console Database)
OPC Property Console Parameters as Type

Comments
Name Database Name in INFI90FCLib String
AUTO Automatic mode. Auto Bool
CNTRL_OVR Control is CntrlOvr Bool
overridden.
FB1/COMP Complement input N/A Bool
signal.
FB1/DESCRIP Signal N/A String
TION description.
232 3BUA000937R301
Section 44 MSDD Comparison of MSDD Parameters
Table 95. MSDD (Console Database) (Continued)

Comments
FB1/SIG Boolean value. F1 Bool
FB1/SIG0 Inactive state FB1SIG0 String The logic state descriptors
description. LSD’s are defined in the
MSDD String properties
Aspect of the object.
FB1/SIG1 Active state FB1SIG1 String The logic state descriptors
signal.
TION description.
signal.
TION description.
3BUA000937R301 233
Comparison of MSDD Parameters Section 44 MSDD

Comments
signal.
TION description.
description LSD’s are defined in the
LASTGOOD Last good state. LastGood Int
LASTGOOD:S Text version of last N/A String
good state.
LS0 State 0 logic state LSD0 String The logic state descriptors
234 3BUA000937R301
Section 44 MSDD Differences in Functionality

Comments
REDTAG/ACT Red tagging is N/A Bool
active.
REDTAG/KEY1 Red tag key 1. N/A String
SP Requested state. SP Int
SP Requested state Value String The requested state in
in string string is configured in
property translation aspect
of the object.
STATUS_OVR Status overridden. StatusOvr Bool
USERTYPE User type code N/A Int
(0 to 255).
3BUA000937R301 235
Differences in Functionality Section 44 MSDD
236 3BUA000937R301
Section 45 TSTALM

Table 96. Visual Comparison of TSTALM Function Block
N/A
3BUA000937R301 237
Comparison of TSTALM Parameters Section 45 TSTALM
Comparison of TSTALM Parameters

Table 97. TSTALM (Parameters)
Harmony INFI90FCLib
Spec Type Comment
S1 In Input The parameter data type is dword.
S2 Mode Input Any values greater than 2 are taken as 2 and
any value less than 0 is taken as 0.
N H
N+1 L
This Function Block has no changed parameters.
238 3BUA000937R301
Section 46 DAANG

Table 98. Visual Comparison of DAANG Function Block
View in Composer
View in Composer
3BUA000937R301 239
Comparison of Object View Section 46 DAANG
Table 98. Visual Comparison of DAANG Function Block (Continued)
N/A
240 3BUA000937R301
Section 46 DAANG Comparison of Object View
Table 98. Visual Comparison of DAANG Function Block (Continued)
3BUA000937R301 241
Comparison of DAANG Parameters Section 46 DAANG
Comparison of DAANG Parameters

Table 99. DAANG Parameters
Harmony INFI90FCLib
Spec Type Comment
Name
Description
S1 HDisp Constant
S2 MDisp Constant
S3 LDisp Constant
S4 HL Constant
S5 LL Constant
S6 EUD Constant
S8 QOvr Input
S9 InSel Input InSel >128 i.e Report Mode is removed.
S10 PV Input
PVQ Input New Parameter of datatype dword
indicating the Input value quality.
S11 ShAlg Input
ShAlgEN Input New Parameter indicating Enable of
shaping Algorithm.
S12 CV Input
CVQ Input New Parameter of datatype dword
indicating the Calculated value quality.
S13 UvInsVal Constant
S14 InPmt Input
242 3BUA000937R301
Section 46 DAANG Comparison of DAANG Parameters
Table 99. DAANG Parameters (Continued)
Harmony INFI90FCLib
Spec Type Comment
S15 Spare1 Exception reporting is no longer
supported, so this parameter is removed.
S16 AlmSup Input
S17 VHA Input
S18 VLA Input
S19 DevAlm Input
S20 AlmCtrl Tune
S21 HADB Tune
S22 H3ADif Tune
S23 H2ADif Tune
S24 H1AFix Tune
S25 L1AFix Tune
S26 L2ADif Tune
S27 L3ADif Tune
S28 LADB Tune
S29 DevLmt Tune
S30 Spare2 Significant Change is no longer
supported, so this parameter is removed.
S31 TPSec Tune
S32 HRoC Tune
S33 LRoC Tune
S34 AlmCnt Tune
3BUA000937R301 243
Table 99. DAANG Parameters (Continued)
Harmony INFI90FCLib
Spec Type Comment
N Out The Output N is Divided to Out, OutA and
OutQ. Only the Real value of Input is
passed to Out.
N+1 ST
OutA OutA holds AlarmBit value of Output N.
OutQ OutQ holds Quality Bit value of Output N.
Table 100. DAANG (Console DataBase)
Parameter as Type
OPC Property Name Console Database Name Comment
in INFI90FCLib String
ALMACKBC Broadcastalarmacknowledg Bool
eevents.
CALIBSTS Calibrationstatus. Bool
HIGH/ACKR Acknowledgerequired. AckReqH Bool
HIGH/ACT Active. Bool
HIGH/ALARM Alarmstate. Bool
HIGH/ALMEN Alarmevent. EnableH Bool
HIGH/AREF Associatedvalue. Real
HIGH/COM Currenteventcomment. String
HIGH/COM0 Normalstatuscomment. MsgRtn String[60]
HIGH/COM1 Activestatecomment. MsgH String[60]
HIGH/COMP Complementinputsignal. Bool
HIGH/DESCRIPTION Signaldescription. String
HIGH/DUAL Dualactingevent. Bool
244 3BUA000937R301
Table 100. DAANG (Console DataBase) (Continued)
Parameter as Type
HIGH/EN Enable. EnableH Bool
HIGH/EPSCAT Subcategoryofeventpoint Int
(highlimit).
HIGH/PRI Currenteventpriority. Int
HIGH/PRI0 Normalpriority. AESevRtn Dint
HIGH/PRI1 Activepriority. AESevH Dint
HIGH/SIG Booleanvalue. HighSig Bool
HIGH/SIG0 Inactivestatedescription. String
HIGH/SIG1 Activestatedescription. String
HIGH/SUP Eventsuppressedbysignal. Bool
HIGH/UNACK Unacknowledgedalarm. HiUnAck Bool
HIGH/UNACKEP Unacknowledgedeventpoint Bool
(statusoralarm).
HIGHLIM Highalarmlimit. HL Real
LEVELALM Levelalarmsummary. Bool
LOW/ACKR Acknowledgerequired. AckReqL Bool
LOW/ACT Active. Bool
LOW/ALARM Alarmstate. Bool
LOW/ALMEN Alarmevent. EnableL Bool
LOW/AREF Associatedvalue. Real
LOW/COM Currenteventcomment. String
LOW/COM0 Normalstatuscomment. MsgRtn String[60]
LOW/COM1 Activestatecomment. MsgL String[60]
3BUA000937R301 245
Parameter as Type
LOW/COMP Complementinputsignal. Bool
LOW/DESCRIPTION Signaldescription. String
LOW/DUAL Dualactingevent. Bool
LOW/EN Enable. EnableL Bool
LOW/EPSCAT Subcategoryofeventpoint Int
(highlimit).
LOW/PRI Currenteventpriority. Int
LOW/PRI0 Normalpriority. AESevRtn Dint
LOW/PRI1 Activepriority. AESevL Dint
LOW/SIG Booleanvalue. LowSig Bool
LOW/SIG0 Inactivestatedescription. String
LOW/SIG1 Activestatedescription. String
LOW/SUP Eventsuppressedbysignal. Bool
LOW/UNACK Unacknowledgedalarm. LoUnAck Bool
LOW/UNACKEP Unacknowledgedeventpoint Bool
(statusoralarm).
LOWLIM Lowalarmlimit. LL Real
PV/DESCRIPTION Signaldescription. Description String
PV/FOR Formattinginformation. Decimal Int
PV/HIGH Highrangeofsignal. Real
PV/LOW Lowrangeofsignal. Real
PV/PERCENT Signal (SIG) as percentage Real
of span.
246 3BUA000937R301
Parameter as Type
PV/SIG Analog value. Value Real
PV/SIG:QS Quality string. String
PV/SPAN Difference between low and Real
high ranges.
PV/UNITS Engineering units. String
ALMSUP Alarm suppressed by Block. Bool
ALMTYPE Alarming type (standard, ALMTYPE Int
fixed, or variable).
ALTINSEL Alternate input value being CalValue Bool
used.
CNTRREF Display reference for bi MDISP Real
direction dynamic bar.
COMMQUAL Communications are bad. N/A Bool
CONSTR Tags value is being Limit Bool
constrained.
CONSTRPER Input constrain enabled. LimitR Bool
DEVALM Deviation alarm summary. N/A Bool
FORCEXR Force the Block to issue an N/A Bool
exception report.
HARDFAULT Hardware failure detected HardFail Bool
by Block ware.
HI2/ACKR Acknowledge required. AckReqHH Bool
HI2/ACT Active. N/A Bool
HI2/ALARM Alarm state. HHUnAck Bool
3BUA000937R301 247
Parameter as Type
HI2/ALMEN Alarm event. N/A Bool
HI2/AREF Associated value. N/A Real
HI2/COM Current event comment. N/A String
HI2/COM0 Normal status comment. MsgRtn String[60]
HI2/COM1 Active state comment. MsgHH String[60]
HI2/COMP Complement input signal. N/A Bool
HI2/DESCRIPTION Signal description. N/A String
HI2/DUAL Dual acting event. N/A Bool
HI2/EN Enable. EnableHH Bool
HI2/EPSCAT Sub category of event point N/A Int
(high limit).
HI2/PRI Current event priority. N/A Int
HI2/PRI0 Normal priority. AESevRtn Dint
HI2/PRI1 Active priority. AESevHH Dint
HI2/SIG Boolean value. HHSig Bool
HI2/SIG0 Inactive state description. N/A String
HI2/SIG1 Active state description. N/A String
HI2/SUP Event suppressed by N/A Bool
signal.
HI2/UNACK Unacknowledged alarm. HHUnAck Bool
HI2/UNACKEP Unacknowledged event N/A Bool
point (status or alarm).
HI3/ACKR Acknowledge required. AckReqHH Bool
248 3BUA000937R301
Parameter as Type
HI3/ACT Active. N/A Bool
HI3/ALARM Alarm state. N/A Bool
HI3/ALMEN Alarm event. EnableHHH Bool
HI3/AREF Associated value. N/A Real
HI3/COM Current event comment. N/A String
HI3/COM0 Normal status comment. MsgRtn String[60]
HI3/COM1 Active state comment. MsgHHH String[60]
HI3/COMP Complement input signal. N/A Bool
HI3/DESCRIPTION Signal description. N/A String
HI3/DUAL Dual acting event. N/A Bool
HI3/EN Enable. EnableHHH Bool
HI3/EPSCAT Sub category of event point N/A Int
(high limit).
HI3/PRI Current event priority. N/A Int
HI3/PRI0 Normal priority. AESevRtn Dint
HI3/PRI1 Active priority. AESevHHH Dint
HI3/SIG Boolean value. HHHSig Bool
HI3/SIG0 Inactive state description. N/A String
HI3/SIG1 Active state description. N/A String
HI3/SUP Event suppressed by N/A Bool
signal.
HI3/UNACK Unacknowledged alarm. HHHUnAck Bool
3BUA000937R301 249
Parameter as Type
HI3/UNACKEP Unacknowledged event N/A Bool
HICONSTRLMT High constraint limit. HL Real
HIGHDEV/ACKR Acknowledge required. AckReqHDev Bool
HIGHDEV/ACT Active. N/A Bool
HIGHDEV/ALARM Alarm state. N/A Bool
HIGHDEV/ALMEN Alarm event. EnableHDev Bool
HIGHDEV/AREF Associated value. N/A Real
HIGHDEV/COM Current event comment. N/A String
HIGHDEV/COM0 Normal status comment. MsgRtn String[60]
HIGHDEV/COM1 Active state comment. MsgHDev String[60]
HIGHDEV/COMP Complement input signal. N/A Bool
HIGH/DESCRIPTION Signal description. N/A String
HIGHDEV/DUAL Dual acting event. N/A Bool
HIGHDEV/EN Enable. EnableHDev Bool
HIGHDEV/EPSCAT Sub category of event point N/A Int
(high limit).
HIGHDEV/PRI Current event priority. N/A Int
HIGHDEV/PRI0 Normal priority. AESevRtn Dint
HIGHDEV/PRI1 Active priority. AESevHDev Dint
HIGHDEV/SIG Boolean value. HighDevSig Bool
HIGHDEV/SIG0 Inactive state description. N/A String
HIGHDEV/SIG1 Active state description N/A String
250 3BUA000937R301
Parameter as Type
HIGHDEV/SUP Event suppressed by N/A Bool
signal.
HIGHDEV/UNACK Unacknowledged alarm. DHUnAck Bool
HIGHDEV/UNACKEP Unacknowledged event N/A Bool
HIGHRATE/ACKR Acknowledge required. AckReqRH Bool
HIGHRATE/ACT Active. N/A Bool
HIGHRATE/ALARM Alarm state. N/A Bool
HIGHRATE/ALMEN Alarm event. EnableRH Bool
HIGHRATE/AREF Associated value. N/A Real
HIGHRATE/COM Current event comment. N/A String
HIGHRATE/COM0 Normal status comment. MsgRtn String[60]
HIGHRATE/COM1 Active state comment. MsgRH String[60]
HIGHRATE/COMP Complement input signal. N/A Bool
HIGHRATE/DESCRIPTION Signal description. N/A String
HIGHRATE/DUAL Dual acting event. N/A Bool
HIGHRATE/EN Enable. EnableRH Bool
HIGHRATE/EPSCAT Sub category of event point N/A Int
(high limit).
HIGHRATE/PACK Event page wide N/A Bool
acknowledge enable.
HIGHRATE/PRI Current event priority. N/A Int
HIGHRATE/PRI0 Normal priority. AESevRtn Dint
HIGHRATE/PRI1 Active priority. AESevRH Dint
3BUA000937R301 251
Parameter as Type
HIGHRATE/SIG Boolean value. HighRateSig Bool
HIGHRATE/SIG0 Inactive state description. N/A String
HIGHRATE/SIG1 Active state description. N/A String
HIGHRATE/SUP Event suppressed by N/A Bool
signal.
HIGHRATE/UNACK Unacknowledged alarm. RHUnAck Bool
HIGHRATE/UNACKEP Unacknowledged event N/A Bool
HIREF High reference limit. HDISP Real
LO2/ACKR Acknowledge required. AckReqLL Bool
LO2/ACT Active. N/A Bool
LO2/ALARM Alarm state. N/A Bool
LO2/ALMEN Alarm event. EnableLL Bool
LO2/AREF Associated value. N/A Real
LO2/COM Current event comment. N/A String
LO2/COM0 Normal status comment. MsgRtn String[60]
LO2/COM1 Active state comment. MsgLL String[60]
LO2/COMP Complement input signal. N/A Bool
LO2/DESCRIPTION Signal description. N/A String
LO2/DUAL Dual acting event. N/A Bool
LO2/EN Enable. EnableLL Bool
LO2/EPSCAT Sub category of event point N/A Int
(high limit).
252 3BUA000937R301
Parameter as Type
LO2/PRI Current event priority. N/A Int
LO2/PRI0 Normal priority. AESevRtn Dint
LO2/PRI1 Active priority. AESevLL Dint
LO2/SIG Boolean value. LLSig Bool
LO2/SIG0 Inactive state description. N/A String
LO2/SIG1 Active state description. N/A String
LO2/SUP Event suppressed by N/A Bool
signal.
LO2/UNACK Unacknowledged alarm. UnAckLL Bool
LO2/UNACKEP Unacknowledged event N/A Bool
LO3/ACKR Acknowledge required. AckReqLLL Bool
LO3/ACT Active. N/A Bool
LO3/ALARM Alarm state. N/A Bool
LO3/ALMEN Alarm event. EnableLLL Bool
LO3/AREF Associated value. N/A Real
LO3/COM Current event comment. N/A String
LO3/COM0 Normal status comment. MsgRtn String[60]
LO3/COM1 Active state comment. MsgLLL String[60]
LO3/COMP Complement input signal. N/A Bool
LO3/DESCRIPTION Signal description. N/A String
LO3/DUAL Dual acting event. N/A Bool
LO3/EN Enable. EnableLLL Bool
3BUA000937R301 253
Parameter as Type
LO3/EPSCAT Sub category of event point N/A Int
(high limit).
LO3/PRI Current event priority. N/A Int
LO3/PRI0 Normal priority. AESevRtn Dint
LO3/PRI1 Active priority. AESevLLL Dint
LO3/SIG Boolean value. LLLSig Bool
LO3/SIG0 Inactive state description. N/A String
LO3/SIG1 Active state description. N/A String
LO3/SUP Event suppressed by N/A Bool
signal.
LO3/UNACK Unacknowledged alarm. UnAckLLL Bool
LO3/UNACKEP Unacknowledged event N/A Bool
LOCONSTRLMT Low constraint limit. LL Real
LOREF Low reference limit. LDISP Real
LOWDEV/ACKR Acknowledge required. AckReqLDev Bool
LOWDEV/ACT Active. N/A Bool
LOWDEV/ALARM Alarm state. N/A Bool
LOWDEV/ALMEN Alarm event. EnableLDev Bool
LOWDEV/AREF Associated value. N/A Real
LOWDEV/COM Current event comment. N/A String
LOWDEV/COM0 Normal status comment. MsgRtn String[60]
LOWDEV/COM1 Active state comment. MsgLDev String[60]
254 3BUA000937R301
Parameter as Type
LOWDEV/COMP Complement input signal. N/A Bool
LOWDEV/DESCRIPTION Signal description. N/A String
LOWDEV/DUAL Dual acting event. N/A Bool
LOWDEV/EN Enable. EnableLDev Bool
LOWDEV/EPSCAT Sub category of event point N/A Int
(high limit).
LOWDEV/PRI Current event priority. N/A Int
LOWDEV/PRI0 Normal priority. AESevRtn Dint
LOWDEV/PRI1 Active priority. AESevLDev Dint
LOWDEV/SIG Boolean value. LowDevsig Bool
LOWDEV/SIG0 Inactive state description. N/A String
LOWDEV/SIG1 Active state description. N/A String
LOWDEV/SUP Event suppressed by N/A Bool
signal.
LOWDEV/UNACK Unacknowledged alarm. DLUnAck Bool
LOWDEV/UNACKEP Unacknowledged event N/A Bool
LOWRATE/ACKR Acknowledge required. AckReqRL Bool
LOWRATE/ACT Active. N/A Bool
LOWRATE/ALARM Alarm state. N/A Bool
LOWRATE/ALMEN Alarm event. EnableRL Bool
LOWRATE/AREF Associated value. N/A Real
LOWRATE/COM Current event comment. N/A String
3BUA000937R301 255
Parameter as Type
LOWRATE/COM0 Normal status comment. MsgRtn String[60]
LOWRATE/COM1 Active state comment. MsgRL String[60]
LOWRATE/COMP Complement input signal. N/A Bool
LOWRATE/DESCRIPTION Signal description. N/A String
LOWRATE/DUAL Dual acting event. N/A Bool
LOWRATE/EN Enable. EnableRL Bool
LOWRATE/EPSCAT Sub category of event point N/A Int
(high limit).
LOWRATE/PRI Current event priority. N/A Int
LOWRATE/PRI0 Normal priority. AESevRtn Dint
LOWRATE/PRI1 Active priority. AESevRL Dint
LOWRATE/SIG Boolean value. N/A Bool
LOWRATE/SIG0 Inactive state description. LowRateSig String
LOWRATE/SIG1 Active state description. N/A String
LOWRATE/SUP Event suppressed by N/A Bool
signal.
LOWRATE/UNACK Unacknowledged alarm. RLUnAck Bool
LOWRATE/UNACKEP Unacknowledged event N/A Bool
MULTLVL Multilevel alarming enabled. MulLvlEb Bool
NOREPORT Scanning disabled by N/A Bool
blockware.
NXTHILMT Next higher alarm limit. NxtHiVal Real
NXTLOLMT Next lower alarm limit. NxtLoVal Real
256 3BUA000937R301
Section 46 DAANG Differences in Functionality
Parameter as Type
OUTRANGE Value is out of range. OutOfRange Bool
PERINSEL User is permitted to select InPmt Bool
input value.
QUALOVR Quality is overridden by QualOvr Bool
blockware.
RATEALM Rate alarm summary. N/A Bool
REALM Periodic realarming RetAlarm Bool
enabled.
REDTAG/ACT Red tagging is active. N/A Bool
SRC Composite mode (AUTO N/A Int
and ALTINSEL).
USERVAL Manually entered value. UserVal Real
VARALM Variable alarming enabled. N/A Bool
177, DAANG.
3BUA000937R301 257
Differences in Functionality Section 46 DAANG
258 3BUA000937R301
Section 47 RMCB

Table 101. Visual Comparison of RMCB Function Block
View in Composer
View in Composer
3BUA000937R301 259
Comparison of Object View Section 47 RMCB
Table 101. Visual Comparison of RMCB Function Block (Continued)
N/A
260 3BUA000937R301
Section 47 RMCB Comparison of Object View
Table 101. Visual Comparison of RMCB Function Block (Continued)
3BUA000937R301 261
Comparison of RMCB Parameters Section 47 RMCB
Comparison of RMCB Parameters

Table 102. RMCB Parameters
Harmony INFI90FCLib
Spec Type Comment
S1 Start Input
S2 Stop Input
S3 ILK1 Input
S4 ILK2 Input
S5 ILK3 Input
S6 ILK4 Input
S7 FB1 Input
S8 FB2 Input
S9 Perm1 Input
S10 Perm2 Input
S11 FBWait Tune
S12 PON Tune
S13 POFF Tune
S14 N/A N/A Removed
S15 N/A N/A Removed
S16 HSTS Constant
S17 FBWait2 Constant
N RS N/A
N+1 OnP N/A
N+2 OffP N/A
N+3 ST N/A
262 3BUA000937R301
Section 47 RMCB Comparison of RMCB Parameters
Table 103 lists the Harmony console specifications and equivalent

parameters/visible variables in INFI90FCLib Library.
Table 103. RMCB (Console Database)

Comments
OUT/SIG Boolean value. RS bool
ERRCODE Status of RMCB ErrCode dint
startup string (0-9).
ERRCODE:S Status of RMCB ERRCODE string Individual error code
startup string (0-9). Strings
(ERRCODE0,
ERRCODE1,
ERRCODE2,
ERRCODE3,
ERRCODE4,
ERRCODE5,
ERRCODE6,
ERRCODE7,
ERRCODE8,
ERRCODE9)
are configurable by user
from RMCB String
properties aspect.
ErrCode String present
in the RMCB properties
aspect takes the value
of one of the strings
above based on the
error condition in the
Block.
FAULT Interlock/feedback Fault bool
lost when running.
FB1/COMP Complement input N/A N/A
signal.
3BUA000937R301 263
Comparison of RMCB Parameters Section 47 RMCB
Table 103. RMCB (Console Database) (Continued)

Comments
FB1/DESCRIPTION Signal description. N/A N/A
FB1/SIG Boolean value. FB1 bool
FB1/SIG0 Inactive state FB1SIG0 string The logic state
description. descriptors LSD’s are
defined in the RMCB
String properties Aspect
of the object.
FB1/SIG1 Active state FB1SIG1 string The logic state
defined in the RMCB
of the object.
FB2/DESCRIPTION Signal description. N/A N/A
FB2/SIG Boolean value. FB2 bool
FB2/SIG0 Inactive state FB2SIG0 string The logic state
defined in the RMCB
of the object.
FB2/SIG1 Active state FB2SIG1 string The logic state
defined in the RMCB
of the object.
REDTAG/ACT Red tagging is N/A N/A Not supported
active.
REDTAG/KEY1 Red tag key 1. N/A N/A Not supported
264 3BUA000937R301
Section 47 RMCB Comparison of RMCB Parameters

Comments
STARTPM1/COMP Complement input N/A N/A
signal.
STARTPM1/DESCR Signal description. N/A N/A
IPTION
STARTPM1/SIG Boolean value. Perm1 bool
STARTPM1/SIG0 Inactive state STARTPM1SIG0 string The logic state
defined in the RMCB
of the object.
STARTPM1/SIG1 Active state STARTPM1SIG1 string The logic state
defined in the RMCB
of the object.
STARTPM2/COMP Complement input N/A N/A
signal.
STARTPM2/DESCR Signal description. N/A N/A
IPTION
STARTPM2/SIG Boolean value. Perm2 bool
STARTPM2/SIG0 Inactive state STARTPM2SIG0 string The logic state
defined in the RMCB
of the object.
STARTPM2/SIG1 Active state STARTPM2SIG1 string The logic state
defined in the RMCB
of the object.
3BUA000937R301 265
Differences in Functionality Section 47 RMCB

Comments
STATECHANGE/AC Acknowledge AckReq bool
KR required.
TXTSET RMCB Text N/A N/A
message set.
USERTYPE User type code N/A N/A
(0 to 255).
Code136.
266 3BUA000937R301
Section 48 DADIG

Table 104. Visual Comparison of DADIG Function Block
N/A
3BUA000937R301 267
Comparison of Object View Section 48 DADIG
Table 104. Visual Comparison of DADIG Function Block (Continued)
268 3BUA000937R301
Section 48 DADIG Comparison of DADIG Parameters
Comparison of DADIG Parameters

Table 105. DADIG Parameters
Harmony INFI90FCLib
Spec Type Comment
S1 InSel Input
S2 InPmt Input
S3 PriIn Input
S4 AltIn Input
S5 CusIn Constant
S6 InCondMode Tune
S7 InCondTRef Tune
S8 InCondCntRef Tune
S9 AlmMode Tune
S10 AlmTRef Tune
S11 AlmCntRef Tune
S12 RDAlmTRef Tune
S13 EnAlmSupp Input
S14 QualOvr Input
S15 EnLatch Input
S16 N/A N/A Exception reporting is no longer
supported, so this parameter is removed
S17 N/A N/A
S18 N/A N/A
S19 N/A N/A
S20 N/A N/A
3BUA000937R301 269
Comparison of DADIG Parameters Section 48 DADIG
Table 105. DADIG Parameters (Continued)
Harmony INFI90FCLib
Spec Type Comment
N Out N/A
N+1 ST N/A
Table 106. DADIG (Console Database)
Parameters/
OPC Property Console Database
Variables as in Type String Comments
Name Name
INFI90FCLib
ALMSUP Alarms suppressed AlmSup Bool
by blockware.
ALTINSEL Alternate input AltInSel Bool
value being used.
FORCEXR Force the Block to N/A N/A
issue an exception
report.
LATCHED Output state is LATCHED Bool
latched.
NOREPORT Scanning disabled N/A N/A
by blockware.
OUTRANGE Value is out of OutSuspect Bool
range.
PERINSEL User is permitted to PerInSel Bool
select input value.
QUALOVR Quality is QualityOvr Bool
overridden by
blockware.
270 3BUA000937R301
Section 48 DADIG Differences in Functionality
Table 106. DADIG (Console Database) (Continued)
Parameters/
OPC Property Console Database
Variables as in Type String Comments
Name Name
INFI90FCLib
REALM Periodic realarming ReAlm Bool
enabled.
REDTAG/ACT Red tagging is N/A N/A Not supported
active.
SRC Composite mode SRC Dint Indicates input source
(AUTO and 0,1-Primary
ALTINSEL). 2-User Input
3-Alternate
SRC:S Composite mode SRC String Individual source strings
string. (SRC0, SRC1, SRC2) are
configurable by user from
DADIG String properties
aspect. SRC String
present in the DADIG
properties aspect takes the
value of one of the strings
above based on the
Parameter InSel.
USERTYPE User type code. N/A N/A
Code211.
3BUA000937R301 271
Differences in Functionality Section 48 DADIG
272 3BUA000937R301
Section 49 ISC

Table 107. Visual Comparison of ISC Function Block
N/A
3BUA000937R301 273
Comparison of Object View Section 49 ISC
Table 107. Visual Comparison of ISC Function Block (Continued)

274 3BUA000937R301
Section 49 ISC Comparison of ISC Parameters
Comparison of ISC Parameters

Table 108. ISC Parameters
Harmony INFI90FCLib
Spec Type Comment
S1 PV Input
S2 SP Input
S3 TR Input
S4 TS Input
S5 C Input
S6 ExtRef Input
N CO output
N.A LoopTune LoopTune
Table 109. LoopTune (Components) related to ISC
Harmony INFI90FCLib
Spec Type Comment
S7 K Tune
S8 DTim Tune
S9 Lag Tune
S10 Tun Tune
S11 HOLim Tune
S12 LOLim Tune
This FB has no changes in functionality.
3BUA000937R301 275
Differences in Functionality Section 49 ISC
276 3BUA000937R301
Section 50 Exec

Table 110. Visual Comparison of Exec Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 277
Comparison of Object View Section 50 Exec
Table 110. Visual Comparison of Exec Function Block (Continued)
278 3BUA000937R301
Section 50 Exec Comparison of Exec Parameters
Comparison of Exec Parameters

Table 111. Exec Parameters
Harmony INFI90FCLib
Spec Type Comments
S1 Tune Deleted (Note 1)
Blk number 0 BLK0 Output No
Blk number 10 SU Output No
Blk number 11 Output Deleted
Blk number 12 SFT Output No
AppStart Output New
3BUA000937R301 279
Differences in Functionality Section 50 Exec
Note 1: INFI90FCLib has no equivalent functionality
Note 2: In Harmony, BLK 2 is special. It has a flexible data type (Logic 0 or Real
0.0).The value and meaning of BLK 2 is determined by each Function Block Input
that connects to it. Some Harmony Function Block inputs treat BLK 2 simply as the
value 0 or 0.0. Some Function Block inputs treat BLK 2 as 'not connected'.
INFI90FCLib does not provide this flexibility. In INFI90FCLib, BLK 2 is an
ordinary output with data type real.
Code081.
280 3BUA000937R301
Section 51 ExExec

Table 112. Visual Comparison of ExExec Function Block
N/A
3BUA000937R301 281
Comparison of Object View Section 51 ExExec
Table 112. Visual Comparison of ExExec Function Block (Continued)

282 3BUA000937R301
Section 51 ExExec Comparison of ExExec Parameters
Comparison of ExExec Parameters

Table 113. ExExec Parameters

S1 Tune Deleted
S2 Tune Deleted
S3 Tune Deleted
S4 StartupTime Tune No
S5 Deleted
S6 Deleted
Blk20 Hour Output
Blk21 Min Output
Blk22 Sec Output
Blk23 Valid Output
Blk24 Year Output
Blk25 Month Output
Blk26 Day Output
Blk27 DoW Output
Week Output New
InhibitDL Tune New
DLInhibited Output New
The parameters InhibitDL and DLInhibited are added to support the new firmware
functions available in SV 5.0 SP2. When InhibitDL parameter is True, it restricts the
user from doing any further downloads. When it is set to False, it allows the user to
perform downloads.
INFI90FCLib does not have equivalent functionality to specifications S1, S2, S3, S5
and S6 of ExExec.
3BUA000937R301 283
Differences in Functionality Section 51 ExExec
284 3BUA000937R301
Section 52 Device Monitor

Table 114. Visual Comparison of DevMon Function Block
NA
View in Composer
3BUA000937R301 285
Comparison of Object View Section 52 Device Monitor
Table 114. Visual Comparison of DevMon Function Block (Continued)
N/A
286 3BUA000937R301
Section 52 Device Monitor Comparison of Object View
Table 114. Visual Comparison of DevMon Function Block (Continued)
NA
3BUA000937R301 287
Comparison of DevMon Parameters Section 52 Device Monitor
Comparison of DevMon Parameters

Table 115. DevMon Parameters

S1 COS1 Input
S2 COS2 Input
S3 COS3 Input
S4 COS4 Input
S5 COS5 Input
S6 COS6 Input
S7 COS7 Input
S8 COS8 Input
S9 COS9 Input
S10 COS10 Input
S11 COS11 Input
S12 COS12 Input
S13 COS13 Input
S14 COS14 Input
S15 COS15 Input
S16 COS16 Input
N ST Output
288 3BUA000937R301
Section 52 Device Monitor Differences in Graphical Interfaces

This Function Block does not have graphical interface.
3BUA000937R301 289
Differences in Graphical Interfaces Section 52 Device Monitor
290 3BUA000937R301
Section 53 Exponential

Table 116. Visual Comparison of EXP1 Function Block
View in Composer
View in Composer
N/A

3BUA000937R301 291
Comparison of EXP1 Parameters Section 53 Exponential
Comparison of EXP1 Parameters

Table 117. Exp1 Parameters

S1 X Input
S2 Gain Tune
N Out Output

292 3BUA000937R301
Section 54 Logarithm

Table 118. Visual Comparison of LOG1 Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 293
Comparison of LOG1 Parameters Section 54 Logarithm
Comparison of LOG1 Parameters

Table 119. LOG1 Parameters

S1 X Input
S2 Base Constant
S3 K Tune
N Out Output

294 3BUA000937R301
Section 55 Trigonometric

Table 120. Visual Comparison of TRIG Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 295
Comparison of TRIG Parameters Section 55 Trigonometric
Comparison of TRIG Parameters

Table 121. Trigonometric Parameters

S1 In Input
S2 InUnit Constant
S3 Typ Constant
S4 Gain Tune
N Out Output

296 3BUA000937R301
Section 56 Power

Table 122. Visual Comparison of POWER Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 297
Comparison of POWER Parameters Section 56 Power
Comparison of POWER Parameters

Table 123. Power Parameters
Harmony INFI90FCLib
Spec Type Comment
S1 Base Input
S2 Exp Input
S3 Gain Tune
N Out Output

298 3BUA000937R301
Section 57 Blink

Table 124. Visual Comparison of BLINK Function Block
N/A
View in Composer
N/A
N/A
3BUA000937R301 299
Comparison of Blink Parameters Section 57 Blink
Comparison of Blink Parameters

Table 125. Blink Parameters

S1 In1 Input
S2 In2 Input
N Out Output

300 3BUA000937R301
Section 58 RedAI

Table 126. Visual Comparison of RedAI Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 301
Comparison of Object View Section 58 RedAI
Table 126. Visual Comparison of RedAI Function Block (Continued)
Table 127. RedAI Parameters
Harmony Specification INFI90FCLib Parameters Spec Type Comment

S1 In1 Input
S1 In1Q Input In1 Input signal quality
S2 In2 Input
S1 In2Q Input In2 Input signal quality
S3 InSel Input
S4 DevLim Tune
S5 RateLim Tune
S6 ErrDB Tune
N Out Output
N Out Output Output signal quality
302 3BUA000937R301
Section 58 RedAI Differences in Functionality
Code96.

3BUA000937R301 303
Differences in Graphical Interfaces Section 58 RedAI
304 3BUA000937R301
Section 59 RedDI

Table 128. Visual Comparison of RedDI Function Block
N/A

3BUA000937R301 305
Comparison of RedDI Parameters Section 59 RedDI
Comparison of RedDI Parameters

Table 129. RedDI Parameters
Harmony Specification INFI90FCLib Parameters Spec Type Comment

S1 In1 Input
S1 In1Q Input In1 signal quality
S2 In2 Input
S1 In2Q Input In2 signal quality
S3 InSel Input
N Out Output
N OutQ Output Output signal
quality
Code97.

306 3BUA000937R301
Section 60 RecipeBool

Table 130. Visual Comparison of RecipeBool Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 307
Comparison of RecipeBool Parameters Section 60 RecipeBool
Table 130. Visual Comparison of RecipeBool Function Block (Continued)

N/A
Comparison of RecipeBool Parameters
Table 131. RecipeBool Parameters

Comment
S1 ParGrp.Par0 Tune The Input Parameter S1-S10 of Bool Recipe
Table is replaced by one single Extensible
parameter ParGrp. ParGrp is of ParBool10
datatype which consists of a group of 10 Bool
input parameter Par0, Par1...Par9. The ten
values in the master Block are zero through
nine. The range of parameters associated with
the next Block in the link list is ten through 19,
and so on. If several Blocks are in series, the
output always comes from the first Block in the
series.
S2 ParGrp.Par1 Tune
S3 ParGrp.Par2 Tune
S4 ParGrp.Par3 Tune
308 3BUA000937R301
Section 60 RecipeBool New/Changed Parameters
Table 131. RecipeBool Parameters (Continued)
S5 ParGrp.Par4 Tune
S6 ParGrp.Par5 Tune
S7 ParGrp.Par6 Tune
S8 ParGrp.Par7 Tune
S9 ParGrp.Par8 Tune
S10 ParGrp.Par9 Tune
S11 PS Input
S12 Nxt N.A. Deleted, In RecipeBool this feature is not
required as all the ParGrp comes under the
same Block and is directed to one output.
S13 ES Input
S14 EPS Input
S15 ESV Input
N Out
Code117, but the implementation of the function has been changed. In
INFI90FCLib, when inserting a Block, set the size of the Block according to the
number of bool inputs to connect. For example:
• To connect less than ten bool inputs, set the size of the RecipeBool Block to
one.
3BUA000937R301 309
Differences in Functionality Section 60 RecipeBool
• To connect more than ten bool inputs, set the size of the RecipeBool Block to
two.
ParGrp belongs to one Bool Recipe Block. To connect more than one Bool Recipe
Block, increase the Multisize of the RecipeBool by 1. The Look of the RecipeBool
Block will not match the existing BoolRecipeTable in harmony. In Harmony if four
BoolRecipeTable Blocks are connected, the appearance is as shown in the
Figure 24, but in the INFI90FCLib Phase2 Library, RecipeBool appearance is as
shown in Figure 25.
Figure 24. Appearance of Recipe Bool in Harmony
310 3BUA000937R301
Section 60 RecipeBool Differences in Graphical Interfaces
Figure 25. Appearance of Recipe Bool in Function Designer

3BUA000937R301 311
Differences in Graphical Interfaces Section 60 RecipeBool
312 3BUA000937R301
Section 61 Rung5

Table 132. Visual Comparison of Rung5 Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 313
Comparison of Object View Section 61 Rung5
Table 132. Visual Comparison of Rung5 Function Block (Continued)
314 3BUA000937R301
Section 61 Rung5 Comparison of Rung5 Parameters
Comparison of Rung5 Parameters

Table 133. Rung5 Parameters

S1 Mode Tune
S2 In1Op Tune If invalid value (255) is given
to InOp. The nearest valid
value (242) is taken. While in
Harmony, if invalid value
(255) is given, the default
value (200) is taken.
S3 In2Op Tune
S4 In3Op Tune
S5 In4Op Tune
S6 In5Op Tune
S7 In1 Input
S8 In2 Input
S9 In3 Input
S10 In4 Input
S11 In5 Input
JIn Input New Parameter is added to
perform Jump/MCR
functionality.
0=Normal operation
1=Jump Function activates
2=MCR Function activates
N Out Output
JOut Output New parameter added to
transfer JIn value to next
Rung block connected in
series.
3BUA000937R301 315
New/Changed Parameters Section 61 Rung5
Parameters JIn and JOut are the new parameters which are not available in
Harmony.

316 3BUA000937R301
Section 62 Rung10

View in Composer
View in Composer
3BUA000937R301 317

N/A
318 3BUA000937R301
Section 62 Rung10 Comparison of Object View

3BUA000937R301 319
Harmony INFI90FCLib
Spec Type Comment
S1 Mode Tune
S2 In1Op Tune If invalid value(255) is given to InOp. It takes the
nearest valid value (242). While in harmony, if
invalid value (255) is given, it takes the default
value (200).
S3 In2Op Tune
S4 In3Op Tune
S5 In4Op Tune
S6 In5Op Tune
S7 In6Op Tune
S8 In7Op Tune
S9 In8Op Tune
S10 In9Op Tune
S11 In10Op Tune
S12 In1 Input
S13 In2 Input
S14 In3 Input
S15 In4 Input
S16 In5 Input
S17 In6 Input
S18 In7 Input
S19 In8 Input
S20 In9 Input
320 3BUA000937R301
Section 62 Rung10 New/Changed Parameters
Table 135. Rung10 Parameters (Continued)
Harmony INFI90FCLib
Spec Type Comment
S21 In10 Input
JIn Input New Parameter is added to perform Jump/MCR
functionality.
0=Normal operation
N Out Output
JOut Output New Parameter added to transfer JIn value to next
Rung Block connected in series.
S1 Mode Tune
Parameters JIn and JOut are included in this block which are not available in
Harmony.

3BUA000937R301 321
Differences in Graphical Interfaces Section 62 Rung10
322 3BUA000937R301
Section 63 Rung20

View in Composer
View in Composer
3BUA000937R301 323

N/A
324 3BUA000937R301
Section 63 Rung20 Comparison of Object View


3BUA000937R301 325
Comparison of Rung20 Properties Section 63 Rung20
Comparison of Rung20 Properties


Comment
S1 Mode Tune
S2 In1Op Tune If invalid value(255) is given to InOp.It will take
nearest valid value (242).While in harmony, if
invalid value (255) is given, it takes the default
value (200).
S3 In2Op Tune
S4 In3Op Tune
S5 In4Op Tune
S6 In5Op Tune
S7 In6Op Tune
S8 In7Op Tune
S9 In8Op Tune
S10 In9Op Tune
S11 In10Op Tune
S12 In11Op Tune
S13 In12Op Tune
S14 In13Op Tune
S15 In14Op Tune
S16 In15Op Tune
S17 In16Op Tune
S18 In17Op Tune
S19 In18Op Tune
326 3BUA000937R301
Section 63 Rung20 Comparison of Rung20 Properties

Comment
S20 In19Op Tune
S21 In20Op Tune
S22 In1 Input
S23 In2 Input
S24 In3 Input
S25 In4 Input
S26 In5 Input
S27 In6 Input
S28 In7 Input
S29 In8 Input
S30 In9 Input
S31 In10 Input
S32 In11 Input
S33 In12 Input
S34 In13 Input
S35 In14 Input
S36 In15 Input
S37 In16 Input
S38 In17 Input
S39 In18 Input
S40 In19 Input
S41 In20 Input
3BUA000937R301 327
New/Changed Parameters Section 63 Rung20

Comment
JIn Input New Parameter is added to perform Jump/MCR
functionality
0=Normal operation
N Out Output
JOut Output New Parameter added to transfer JIn value to next
Rung Block connected in series.
Parameters JIn and JOut are included in this Block which are not available in
harmony.

328 3BUA000937R301
Section 64 Polynomial

Table 138. Visual Comparison of POLY Function Block
View in Composer
View in Composer
3BUA000937R301 329
Comparison of Object View Section 64 Polynomial
Table 138. Visual Comparison of POLY Function Block (Continued)

N/A
330 3BUA000937R301
Section 64 Polynomial Comparison of Object View
Table 138. Visual Comparison of POLY Function Block (Continued)

\
3BUA000937R301 331
Comparison of POLY Parameters Section 64 Polynomial
Comparison of POLY Parameters

Table 139. Polynomial Parameters

S1 In Input
S2 Hman Tune
S3 Hexp Constant
S4 Gman Tune
S5 Gexp Constant
S6 Fman Tune
S7 Fexp Constant
S8 Eman Tune
S9 Eexp Constant
S10 Dman Tune
S11 Dexp Constant
S12 Cman Tune
S13 Cexp Constant
S14 Bman Tune
S15 Bexp Constant
S16 Aman Tune
S17 Aexp Constant
N Out Output
332 3BUA000937R301
Section 64 Polynomial Differences in Graphical Interfaces

3BUA000937R301 333
Differences in Graphical Interfaces Section 64 Polynomial
334 3BUA000937R301
Section 65 SeqMstrSlv

Table 140. Visual Comparison of SeqMstrSlv Function Block
View in Composer
View in Composer
3BUA000937R301 335
Comparison of Object View Section 65 SeqMstrSlv
Table 140. Visual Comparison of SeqMstrSlv Function Block (Continued)
N/A
N/A
336 3BUA000937R301
Section 65 SeqMstrSlv Comparison of SeqMstrSlv Parameters
Comparison of SeqMstrSlv Parameters

Table 141. SeqMstrSlv Parameters
Harmony
INFI90FCLib Spec
Specifications Comment
Parameters Type
Master/Slv
S1/S1 N/A Input S1 (Block address of Sequence Slave) of
Sequence Master and S1 (Block address of
Next Sequence Slave) of Sequence Slave is
removed. The link between the two Blocks is
not provided because there is only one
Function Block SeqMstrSlv.In SeqMstrSlv
Function Block this feature is not required as
all the SeqMstrSlvGrp comes under the
same Block and is directed to output which is
in same Function Block.
S2 JT Input
S3 JN Input
S4 M00 Tune
S5/S2 SeqMstrSlvMask[].M01 Tune The Tunable Parameter S5-S36 of Sequence
master and Tunable Parameter S2-S33 of
sequence Slave is replaced by one single
Extensible parameter SeqMstrSlvGrp.
SeqMstrSlvGrp is of SeqMstrSlvmask
datatype which consists of group of 32 dint
parameter M1, M2, M3….M32.
S6/S3 SeqMstrSlvMask[].M02 Tune
3BUA000937R301 337
Comparison of SeqMstrSlv Parameters Section 65 SeqMstrSlv
Table 141. SeqMstrSlv Parameters (Continued)
Harmony
INFI90FCLib Spec
Parameters Type
Master/Slv
338 3BUA000937R301
Section 65 SeqMstrSlv Differences in Functionality
Table 141. SeqMstrSlv Parameters (Continued)
Harmony
INFI90FCLib Spec
Parameters Type
Master/Slv
N CM1 Output
N +1 CM10 Output
N +2 CM100 Output
N +3 CM1000 Output
N +4 STEP Output
This SeqMstrSlv sequence FB has no changes in functionality in comparison to
Harmony Function Code141, 142, but the implementation of the SeqMstrSlv is
handled differently.
As per the value in Step Jump number the harmony system searches the master and
other slave Blocks in the link for the required step no and transfers the step mask to
the output. In harmony if more than 32 steps are required then sequence slave
Blocks are added. For example, if 128 steps are required then one sequence master
and 3 sequence slave Blocks have to be connected.
SeqMstrSlv Block does not follow Master-slave concept. As per the value in Step
Jump number the SeqMstrSlv searches the Extensible group SeqMstrSvGrp for the
required step number and transfers the step mask to the output.
If less than 32 step masks have to be connected, set the size of the sequence Block to
one. If more than 32 step mask have to be connected, set the size of the sequence
Block to two and so on.
For 32 steps, size = 1
3BUA000937R301 339
Implementation of data type Bool3/Bool4 Section 65 SeqMstrSlv
64 steps, size = 2
96 steps, size = 3
128 steps, size =4
Implementation of data type Bool3/Bool4

In Sequence Master (S5-S36) and Sequence Slave (S2-S33) the Step mask
parameters can take values from 0000 to 2222. In composer each digit is considered
as a bit set to 0,1,2 inside the code. Now to implement this functionality in Control
Builder, use the data type dint. The dint values entered for these parameters are
broken to individual bits by a hidden Function Block IntergerToBoolSeq. The
Figure 26 and Figure 27 shows a series of sequence master and slave bocks run in
parallel to provide multiple outputs for Harmony and INFI90FCLib.
Figure 26. Parallel Sequence Master to Slave in Harmony
340 3BUA000937R301
Section 65 SeqMstrSlv Implementation of data type Bool3/Bool4
Figure 27. Parallel Sequence Master to Slave in INFI90FCLib
3BUA000937R301 341
Implementation of data type Bool3/Bool4 Section 65 SeqMstrSlv
342 3BUA000937R301
Section 66 SeqMon

Table 142. Visual Comparison of SeqMon Function Block
View in Composer
View in Composer
3BUA000937R301 343
Comparison of Object View Section 66 SeqMon
Table 142. Visual Comparison of SeqMon Function Block (Continued)
N/A

344 3BUA000937R301
Section 66 SeqMon Comparison of SeqMon Parameters
Comparison of SeqMon Parameters

Table 143. SeqMon Parameters
Harmony INFI90FCLib
Spec Type Comment
S1 N.A Input This concept is no longer used, so this
parameter is removed.
S2 CS Input
S3 T Input
S4 SH Input
S5 SAT Input
S6 ES Input
S7 ISN Input
S8 SAP Input
S9 SeqMonGrp.SP1 Tune The parameters S9-S32 are now provided
as single extensible parameter SeqMonGrp.
S10 SeqMonGrp.SP2 Tune
S17 SeqMonGrp.NS1 Tune
3BUA000937R301 345
New/Changed Parmeters Section 66 SeqMon
Table 143. SeqMon Parameters (Continued)
Harmony INFI90FCLib
Spec Type Comment
S25 SeqMonGrp.FS1 Tune
N JN Output
N+1 JT Output
S1 N.A Input This concept is no longer used, so this
New/Changed Parmeters
This SeqMon sequence FB has no changes in functionality in comparison to
Harmony Function Code124, but the implementation of the function Code has been
changed. When the Block is in auto or semi automatic mode and if trigger is
available, the step numbers in the structured parameter SeqMonGrp (NS1..NS8,
FS1..FS8) are passed to the output. Figure 28 shows the configuration of sequence
monitor Block in harmony system with eight steps configured. In Harmony, if more
346 3BUA000937R301
Section 66 SeqMon New/Changed Parmeters
than eight steps are required, then additional sequence monitor Blocks are added. If
16 steps are required, then two sequence monitor Blocks are used.
In INFI90FCLib library, set the size of the Block while inserting the blocks based
on the number of steps required to be connected. To connect less than eight steps,
set the size of the sequence Block to one (Refer Figure 29. It has one structured data
type SeqMonGrp[1] to accommodate eight steps). To connect more than eight steps,
set the size of the sequence Block to two (Refer Figure 30. It has two structured data
types SeqMonGrp[1], SeqMonGrp[2] to accommodate 16 steps) and so on.
16 steps, size = 2
24 steps, size = 3
32 steps, size =4.
3BUA000937R301 347
New/Changed Parmeters Section 66 SeqMon
Figure 28. Size=1, 8 steps (SeqMon Block configuration in Composer)
348 3BUA000937R301
Section 66 SeqMon New/Changed Parmeters
Figure 29. Size=1, 8 steps (SeqMon Block configuration in Function Designer)
3BUA000937R301 349
Differences in Graphical Interfaces Section 66 SeqMon
Figure 30. Size=2,16 Steps (SeqMon Block configuration in Function Designer)

350 3BUA000937R301
Section 67 Trip

Table 144. Visual Comparison of TRIP Function Block
N/A
View in Composer
N/A
N/A
3BUA000937R301 351
Comparison of Trip Parameters Section 67 Trip
Comparison of Trip Parameters

Table 145. Trip Parameters
Harmony
INFI90FCLib Parameters Spec Type Comment
Specifications
S1 In Input
N Out Output

352 3BUA000937R301
Section 68 SeqMgr

Table 146. Visual Comparison of SeqMgr Function Block
3BUA000937R301 353
Comparison of Object View Section 68 SeqMgr
Table 146. Visual Comparison of SeqMgr Function Block (Continued)
N/A

354 3BUA000937R301
Section 68 SeqMgr Comparison of SEQMGR Parameters
Comparison of SEQMGR Parameters

Table 147. SeqMgr Parameters

Comment
S1 N/A Input S1 (Block address of Sequence generator) of
Sequence Manager is removed. This feature is
not required because extensible parameter is
used and all are part of one Function Block.
S2 MT Constant
S3 HR Input
S4 HSTS Constant
S5 SeqMgrGrp.RT1 Input The parameters S5-S28 are now provided as
single extensible parameter SeqMgrGrp.
SeqMgrGrp is of SeqMgrReq datatype consisting
of 16 Boolean input parameter (RT1-CT8) and 8
Tunable real parameter SPR1-SPR8.
S6 SeqMgrGrp.RT2 Input
S13 SeqMgrGrp.CT1 Input
3BUA000937R301 355
Differences in Functionality Section 68 SeqMgr
Table 147. SeqMgr Parameters (Continued)

Comment
S21 SeqMgrGrp.SPR1 Tune
HRT Output
SPN Output
ARN Output
This SEQMGR FB has no functionality changes in comparison to Harmony
Function Code 135, but the implementation of the function Code has been changed.
Each sequence manager Block can accommodate eight requests for a single
subsequence. If more than eight main sequences need access to a subsequence, the
sequence manager Block size can be increased as required.
In the INFI90FCLib library, set the size of the Block according to the number of
requests that needs to be connected, while inserting a Function Block. If less than
356 3BUA000937R301
Section 68 SeqMgr Differences in Functionality
eight requests have to be connected, set the number of the SeqMgrGrp to one. If 16
requests have to be connected, set the number of the SeqMgrGrp to two.
For 8 Requests, SeqMgrGrp = 1
16 Requests, SeqMgrGrp = 2
32 Requests, SeqMgrGrp = 3
64 Requests, SeqMgrGrp = 4.
Figure 31 and Figure 32 shows a configuration with the connection between the
sequence monitor Block for the main sequence, the sequence manager Block, and
the sequence monitor Block for the subsequence in Harmony and INFI90FCLib.
Figure 31. Sample Configuration Using Sequence Manager Block in Harmony
3BUA000937R301 357
New/Changed Parameters Section 68 SeqMgr
Figure 32. Sample Configuration Using Sequence Manager Block in INFI90FCLib

358 3BUA000937R301
Section 69 JumpMCR

Table 148. Visual Comparison of JumpMCR Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 359
Comparison of JumpMCR Parameters Section 69 JumpMCR
Comparison of JumpMCR Parameters

Table 149. JumpMCR Parameters

Comment
S1 Trip Input
S2 - - This concept is no longer used and this parameter is
removed.
S3 Func Input
N Out1 Output
- JOut Output Not available in Harmony
Specification S2 is not used and parameter is removed. JOut Parameter of dint
datatype is included in INFI90FCLib.

360 3BUA000937R301
Section 70 SlSel

Table 150. Visual Comparison of SlSel Function Block
3BUA000937R301 361
Comparison of Object View Section 70 SlSel
Table 150. Visual Comparison of SlSel Function Block (Continued)
N/A
N/A
362 3BUA000937R301
Section 70 SlSel Comparison of SLSEL Parameters
Comparison of SLSEL Parameters

Table 151. SlSel Parameters
INFI90FCLib Spec
Harmony Specifications Comment
Parameters Type
S1 STSA1 Input
S2 STSB1 Input
S3 QA1 Input I/O Channel Quality dword is to be connected
S4 QB1 Input I/O Channel Quality dword is to be connected
S5 STSA2 Input
S6 STSB2 Input
S7 QA2 Input I/O Channel Quality dword is to be connected
S8 QB2 Input I/O Channel Quality dword is to be connected
S9 TOGGLE Input
N SL Output
N+1 INTL Output
S3, S4, S7 and S8: In Harmony system these parameters were I/O signal Bool or
Real with Quality. In INFI90FCLib these parameters are equivalent to QA1, QB1,
QA2 and QB2. These parameters are of type dword and only Quality dword of I/O
channel should be connected to QA1,QB1, QA2, and QB2.
3BUA000937R301 363
Differences in Functionality Section 70 SlSel
364 3BUA000937R301
Section 71 MODST

Table 152. Visual Comparison of Mdst Function Block
View in Composer
View in Composer
3BUA000937R301 365
Comparison of Object View Section 71 MODST
Table 152. Visual Comparison of Mdst Function Block (Continued)
N/A
366 3BUA000937R301
Section 71 MODST Comparison of Object View
Table 152. Visual Comparison of Mdst Function Block (Continued)
3BUA000937R301 367
Comparison of MODST Parameters Section 71 MODST
Comparison of MODST Parameters

Table 153. MODST Parameters

Comment
S1 SI Tune Default value is given as 2 sec.
S2 TargetIP Tune
- HWStat Tune HWState component of HWStatus of controller.
S3 Status Tune "Errors & Warnings" or "Extended Status" component of
HWStatus of Controller.
S4 - Tune
S5 Bit 0 Tune "Errors & Warnings" or "Extended Status" component of
HWStatus of Controller contains 32 bit for status. Status
parameter will select the status dword to be selected.
And Bit0 to Bit31 will define that which bit is to be
monitored.
S6 Bit 1 Tune
S7 Bit 2 Tune
S8 Bit 3 Tune
S9 Bit 4 Tune
S10 Bit 5 Tune
S11 Bit 6 Tune
S12 Bit 7 Tune
- Bit 8 Tune
- Bit 9 Tune
- Bit 10 Tune
- Bit 11 Tune
368 3BUA000937R301
Section 71 MODST Comparison of MODST Parameters
Table 153. MODST Parameters (Continued)

Comment
- Bit 12 Tune
- Bit 13 Tune
- Bit 14 Tune
- Bit 15 Tune
- Bit 16 Tune
- Bit 17 Tune
- Bit 18 Tune
- Bit 19 Tune
- Bit 20 Tune
- Bit 21 Tune
- Bit 22 Tune
- Bit 23 Tune
- Bit 24 Tune
- Bit 25 Tune
- Bit 26 Tune
- Bit 27 Tune
- Bit 28 Tune
- Bit 29 Tune
- Bit 30 Tune
- Bit 31 Tune
3BUA000937R301 369
Differences in Functionality Section 71 MODST
The Harmony modules (Controllers, Communication Modules and Interface
modules) give the 16 byte or 5 byte status. Each byte provides details about one
functionality group. Each bit of any byte signifies some status information. Only
one byte can be monitored at any instant. The output and the quality of the module
status Block depends on the bits to be monitored.
The output and quality of MODST depends on the selected byte and the bits of that
byte to be monitored.
But in 800xA System, each hardware unit gives the hardware status of that unit. So
a similar mapping of each parameter has to be done for 800xA System.
The HWStatus datatype will be used to obtain the status of any controller. This
datatype is in the system library. This data type contains the condition of a hardware
unit. It has six components.
Figure 33. MODST (Hwstatus of controller)
The following components of HWStatus datatype are used as described below:

1. HWState component of the HwStatus data type contains details about the
condition of a controller unit. It indicates the errors or warnings on the
controller. It is of datatype Dint.
2. Errors and Warnings component of the HwStatus data type contains details
about the logged ErrorsAndWarnings. When the error or warning becomes
370 3BUA000937R301
Section 71 MODST Differences in Functionality
inactive, the corresponding ErrorAndWarnings bit is reset. It is of datatype

dword.
Errors are detected after configuration, for example when I/O copying
starts. It is not necessary to handle them during operation. A new
controller download or a system restart may be required to take care of
these errors and return them to errorless condition.
Warnings are detected after configuration and during normal operation.
They can be activated and deactivated during normal operation.
General Warning and General Error is the status that indicates the severity of
Device Specific Status. It does not have a text representation but affects the state of
the hardware unit.
Device Specific Status is used to show a status that is specific for a certain unit. It
can be of all the above mentioned types and is always used with the General Error or
the General Warning status to indicate the severity of the status.
Errors and warnings with the corresponding values and descriptions are provided in
Table 154.
Table 154. MODST (Errors and Warnings)
Status
Bit Status Bit Value Description Severity
Type
_ Status OK 0x00000000 _ _ _
0 Connection down 0x00000001 Connection down Error High
1 I/O error 0x00000002 I/O error Error Medium
2 Module missing 0x00000004 Module missing Error High
3 Wrong module type 0x00000008 Wrong module type Error High
4 Channel error 0x00000010 Channel error Warning Medium
5 I/O warning 0x00000020 I/O warning Warning Low
6 Underflow 0x00000040 Underflow Warning Low
7 Overflow 0x00000080 Overflow Warning Low
3BUA000937R301 371
Table 154. MODST (Errors and Warnings) (Continued)
8 Forced 0x00000100 Forced Warning Low

9 Watchdog timeout 0x00000200 Watchdog timeout Error High
Status
Type
10 Device failure 0x00000400 Device failure Error High
11 Device not found 0x00000800 Device not found Error High
12 Wrong device type 0x00001000 Wrong device type Error High
13 I/O connection error 0x00002000 I/O connection error Error Medium
14 I/O configuration error 0x00004000 I/O configuration error Error Medium
15 Hardware configuration error 0x00008000 Hardware Error High
configuration error
16 GeneralError 2)
0x00010000 - Error -
17 GeneralWarning 2)
0x00020000 - Warning -
18 Warning on primary unit 0x00040000 Warning on primary Warning Low
unit
19 Warning on backup unit 0x00080000 Warning on backup Warning Low
unit
20 Error on backup unit 0x00100000 Error on backup unit Warning Medium
21 Waiting for hardware initialization 0x00200000
22 DeviceSpecific10 0x00400000
23 DeviceSpecific9 0x00800000 CEX-bus fuse on Warning Medium
backup
24 DeviceSpecific8 0x01000000 RPA on Backup Warning Medium
25 DeviceSpecific7 0x02000000 RPA on Backup Warning Medium
372 3BUA000937R301
Table 154. MODST (Errors and Warnings) (Continued)
26 DeviceSpecific6 0x04000000 Battery Low on Backup Warning Medium

27 DeviceSpecific5 0x08000000 No Time sync Warning Medium
Status
Type
28 DeviceSpecific4 0x10000000 CEX-bus fuse Warning High
29 DeviceSpecific3 0x20000000 RPA Warning Medium
30 DeviceSpecific2 0x40000000 RPB Warning Medium
31 DeviceSpecific1 0x80000000 Battery Low Warning Medium
2) Used together other status bits.

Note: DeviceSpecific1 to DeviceSpecific9 are specific to PM864 and PM861.
3. ExtendedStatus component of the HwStatus data type contains information

about a unit. HwStatus information may be errors or warnings, or pure
information. If it contains errors or warnings, this is also indicated by the
General error or General warning bits in ErrorsAndWarnings. When the
information is no longer valid, the ExtendedStatus bit is reset.
The information in ExtendedStatus is defined as follows:
Table 155. MODST (Extended Status)
Status
Type
_ No Extended Status 0x00000000 _ _ _
0 ExtendedStatus1 16#00000001 Backup CPU stopped Warning Medium
1 ExtendedStatus2 16#00000002 Switchover occurred Warning Medium
2 ExtendedStatus3 16#00000004 Hanging or invalid CEX Warning High
IRQ: All CEMs on the
upper CEX bus
segment are disabled
3BUA000937R301 373
Table 155. MODST (Extended Status) (Continued)

lower CEX bus
segment are disabled.
Status
Type
4 ExtendedStatus5 16#00000010 Hanging or invalid CEX Warning Medium
IRQ: A PM has been
shut down.
direct CEX bus
segment are disabled.
indirect CEX bus
segment are disabled
7 ExtendedStatus8 16#00000080 RCUcable connector is Warning Medium
open
8 ExtendedStatus9 16#00000100 1) 1) 1)
9 ExtendedStatus10 16#00000200 1) 1) 1)
10 ExtendedStatus11 16#00000400 1) 1) 1)
11 ExtendedStatus12 16#00000800 1) 1) 1)
12 ExtendedStatus13 16#00001000 1) 1) 1)
13 ExtendedStatus14 16#00002000 1) 1) 1)
14 ExtendedStatus15 16#00004000 1) 1) 1)
15 ExtendedStatus16 16#00008000 1) 1) 1)
16 ExtendedStatus17 16#00010000 1) 1) 1)
17 ExtendedStatus18 16#00020000 1) 1) 1)
374 3BUA000937R301
Table 155. MODST (Extended Status) (Continued)
18 ExtendedStatus19 16#00040000 1) 1) 1)
19 ExtendedStatus20 16#00080000 1) 1) 1)
20 ExtendedStatus21 16#00100000 1) 1) 1)
Status
Type
21 ExtendedStatus22 16#00200000 1) 1) 1)
22 Reserved 16#00400000 - - -
23 PrimaryIncompatibleFW 3) 16#00800000 Version of the running Error High
Primary is incompatible
24 BackupIncompatibleFW 3) 16#01000000 Version of the Running Warning Medium
Backup is incompatible
25 PrimaryNotPrefrdFW 3) 16#02000000 Version of the Running Warning Medium
Primary is not preferred
26 BackupNotPrefrdFW 3) 16#04000000 Version of the Running Warning Medium
Backup is not preferred
27 TimeoutOnBackup 3) 16#08000000 Watchdog timeout on Warning Low
Backup
28 DeviceFailureBackup 3) 16#10000000 Backup device failure Warning Low
3)
29 SwitchoverInProgress 16#20000000 Switchover in progress Warning Low
30 ConfiguredAsRedundant 2), 3) 16#40000000 Redundant mode - -
enabled. Unit A acts
Primary
31 UnitBPrimary 3) 16#80000000 Unit B acts Primary - -
1) Depends on the specific hardware device, defined within the hardware definition file.
2) If this bit is set and bit 31 is not set, the text Unit A acts primary will be shown.
3) Used only if the unit is configured as a redundant unit.
Note: Extended status 1 to Extended Status 8 are specific to PM864 and PM861.
3BUA000937R301 375
Hardware status (HWStatus) is included in InfiAppData. While configuration

controller's AllUnitStatus is to be connected to the HWStatus in one of the
application's InfiAppData as shown in Figure 34.
The Application Engineer has to write the path for HWStatus in the connection
tab of the controller.
Figure 34. ModStat (HWStatus connected to Local Controller)
AllUnitStatus applies to all applications in a controller irrespective of which

application HWStatus is connected. The Executive Block will publish a global
mms variable I90HwStatus when HWstatus is connected to AllUnitStatus tab.
The same name(I90HwStatus) is used for all controllers – since there is only one
AllUnitStatus for each controller.
A ModuleStatus Block connects to the controller, which specifies the
hardwareStatus. The IP address of target controller is typed as an Initial value for
parameter TargetIP. TargerIP is a parameter of type String. The Module Status
Block uses ‘MMS cyclic read’ to periodically read the I90HwStatus MMS variable
from the target controller.
In remote (target controller) application, the AllUnitStatus of the controller should
be connected to the HWStatus of that application as shown in Figure 34. In access
variables of remote (target) controller, MMS variable I90HwStatus should be
defined and the path for Application.InfiAppData.HWStatus should be provided
in path column as shown in Figure 35.
376 3BUA000937R301
Figure 35. ModStat (MMS variable connection to remote Controller)
Table 156 gives the Mapping of BRC400 controller Status to AC 800M (PM864)
controller.
Table 156. MODST (Mapping of BRC400 and PM 864 controller Status)
BRC 400 Module Status Corresponding HWStatus for PM 864

Byte / Errors &
Byte 1 Hwstate Extended Status
Field Warnings
Bit 7 ES Error Summary 0: 0:good
good, 1 Error 1:bad
2:warning
Bit 5 & 6 Mode Controller Mode
(configure/error/
execute)
Bit 0 - 4 Type Controller type
Byte 2
7 FTX first time in execute
BAC Redundant Status Redundant
Module Error
Status (Bit20)
3BUA000937R301 377
Table 156. MODST (Mapping of BRC400 and PM 864 controller Status) (Continued)
6
5 RIO Summary remote I/O Error (Bit 1)
input status:
4 LIO Summary local input I/O Error (Bit 1)
status:
3 CFG Online configuration
changes being made.
2 NVF Summary NVRAM
failure status:
1 NVI Summary NVRAM
initialized state:
0 DSS Digital station status:
Byte 3-5
NVRAM error
Analog input I/O Error (Bit1)
reference error: (1),
(2) = Block number of
control I/O controller
Block.
378 3BUA000937R301
Missing I/O controller Module missing

or expander board: (Bit 2)
(1), (2) = Block
number of I/O
controller or station
Configuration error - I/O configuration
undefined Block: or
HWConfiguration
data
(Bit 14, 15)
Configuration error -
input data type is
incorrect:
Trip Block activated:
Segment violation.
3BUA000937R301 379
Primary controller has

failed and the
redundant controller
configuration is not
current
Primary controller has
failed and the
dynamic RAM data in
the redundant
controller is not
current.
NVRAM write failure
error.
Duplicate device
label.
Program format error
- inconsistent format
table.
Reformat/download
program.
File system error:
Backup cannot
takeover due to
uninitialized file
system.Directory has
not been
configured.List of file
system free memory
is corrupted.
Invoke C error:
C program stack
overflow:
380 3BUA000937R301
UDF reference is
invalid:
UDF Block cannot
read program file:
Not enough memory
for UDF:
Missing UDF
declaration:
Wrong UDF type:
Missing UDF auxiliary
Block:
UDF compiler and
firmware
incompatible:
ETYPE Enhanced controller

Byte 6
type
Byte 7
7 CWA Controlway bus A
failure:
6 CWB Controlway bus B
failure:
5 R1F Redundancy link
channel 1 failure:
4 R2F Redundancy link
channel 2 failure:
1 Hnet A Hnet channel A
failure:
3BUA000937R301 381
0 Hnet B Hnet channel B

failure:
Byte 8 UnUsed
Byte 9
7 RA Hnet channel A relay
fault:
6 RB Hnet channel B relay
fault:
Byte 10
PRI Controller is primary Unit B acts Primary
versus redundant; (Bit 31)
7
6 CFC Configuration current
(latched until
redundant is reset).
CHK Redundant has
completed
checkpointing
(latched until
redundant is reset)
4
3 RID Redundancy ID.
Follows setting of
redundancy ID pole
382 3BUA000937R301
RDEXP Redundancy
expected. Always set
to 1 on the redundant
2 controller. Follows
state of FC 90,
specification S3,
1 OCE Online configuration
is enabled. Follows
setting of online
configuration enable
pole on dipswitch
RDDET Redundancy detected
(latched until
controller is reset or it
changes from
redundant to primary
or primary to
redundant)
0
Byte 11
SOA Status output alarm. RPA & RPB
4 Indicates the status of Errors &
the system +24 volt Warning: Bit 29 &
power and the Block 30
I/O power
3 RNO Redundancy NVRAM

overrun (latched
indication)
Byte UnUsed
12-13
Byte 14
3BUA000937R301 383
Byte 15
0-7 Revision letter (in
ASCII code), for
example,
Byte 16
0-7 Revision number (in
ASCII code), for
example,
384 3BUA000937R301
Section 72 MultiMon

Table 157. Visual Comparison of MultiMon Function Block
3BUA000937R301 385
Comparison of Object View Section 72 MultiMon
Table 157. Visual Comparison of MultiMon Function Block (Continued)
N/A

386 3BUA000937R301
Section 72 MultiMon Comparison of MULTIMON Parameters
Comparison of MULTIMON Parameters

Table 158. MULTIMON (Parameters)

Comment
S1 N.A Input This concept is no longer used and this
S2 CS Input
S3 T Input
S4 ES Input
S5 HR Input
S6 SAP Input
S7 SAT Input
S8 IT Input
S9 RES Input
S10 IS Input
S11 IR Input
S13 MSMGrp.ST1 Input The parameters S13-S44 are now provided as
single extensible parameter MSMGrp.
S14 MSMGrp.ST2 Input
S21 MSMGrp.NS1 Input
3BUA000937R301 387
Comparison of MULTIMON Parameters Section 72 MultiMon
Table 158. MULTIMON (Parameters) (Continued)

Comment
S29 MSMGrp.FP1 Input
S37 MSMGrp.RV1 Input
388 3BUA000937R301
Section 72 MultiMon New/Changed Parameters
Table 158. MULTIMON (Parameters) (Continued)

Comment
N JN Output
N+1 JT Output
N+2 JRV Output
N+3 CP Output
N+4 IDT Output
N+5 RH Output
This MULTIMON Function Block has no changes in functionality in comparison
with Harmony Function Code134, but the implementation of the function Code has
been changed. When the Block is in auto or semi automatic mode and if trigger is
available then the step numbers in the structured parameter MSMGrp (NS1..NS8,
FP1..FP8) are passed to the output. Figure 36 shows the configuration of Multi
sequence monitor Block in harmony system with 8 steps configured. In harmony if
more than 8 steps are required then additional Multi sequence monitor Blocks are
added. For example, if 16 steps are required then two Multi sequence monitor
Blocks are used.
In INFI90FCLib library, while inserting the Block, set the size of the block based on
the number of steps required to be connected. If less than 8 steps have to be
connected, set the size of the sequence Block to one (one structured data type
MSMGrp[1] to accommodate 8 steps). If more than 8 steps have to be connected,
set the size of the sequence Block to two (Two structured data types MSMGrp[1],
MSMGrp[2] to accommodate 16 steps) as shown in Figure 38 and so on.
16 steps, size = 2
3BUA000937R301 389
New/Changed Parameters Section 72 MultiMon
24 steps, size = 3
32 steps, size =4 etc.
Figure 36. Multiple Sequence and Auxiliary Logic Connections
390 3BUA000937R301
Section 72 MultiMon New/Changed Parameters
Figure 37. Multiple Sequence and Auxiliary Logic Connections
3BUA000937R301 391
Differences in Graphical Interfaces Section 72 MultiMon
Figure 38. Multiple Sequence Monitor Connected in Series

392 3BUA000937R301
Section 73 TexSel
Table 159. Visual Comparison of TexSel Function Block
View in Composer
View in Composer
3BUA000937R301 393
Comparison of Object View Section 73 TexSel
Table 159. Visual Comparison of TexSel Function Block (Continued)
N/A
394 3BUA000937R301
Section 73 TexSel Comparison of Object View
Table 159. Visual Comparison of TexSel Function Block (Continued)
3BUA000937R301 395
Comparison of Parameters Section 73 TexSel
Comparison of Parameters
Table 160. TexSel Parameters
Harmony INFI90FCLib
Spec Type Comments
S1 MsgNum Input
S2 Color Input
S3 Blink Input
S4 CtrlSts Input
N/A EnCtrlSts Constant New Parameter of Type bool for
enable /disable of CtrlSts
S5 GoodMsg Constant
S6 GoodClr Constant
S7 GoodBnk Constant
S8 BadMsg Constant
S9 BadClr Constant
S10 BadBnk Constant
S11 WaitMsg Constant
S12 WaitClr Constant
S13 WaitBnk Constant
S14 N/A
S15 N/A
S16 N/A
N Out Output Type is changed from Real to
Dint.
396 3BUA000937R301
Section 73 TexSel New/Changed Parameters
Table 161. TexSel (Console Database)
OPC Property Parameters as in String

Console Database Name Comments
Name INFI90FCLib Type
NAME ObjectName Name string[30]
DESCRIPTION Description of Tag Description string[40]
MSG Color to Display Text Out Dint
COLOR Color to display ColCode Dint
Blink Display Text should be Blinking BliSel Bool
MSG:S Current Text String MSGS String

3BUA000937R301 397
Differences in Graphical Interfaces Section 73 TexSel
398 3BUA000937R301
Section 74 BasicStation

Table 162. Visual Comparison of BasicStation Function Block
View in Composer
View in Composer
3BUA000937R301 399
Comparison of Object View Section 74 BasicStation
Table 162. Visual Comparison of BasicStation Function Block (Continued)
N/A
400 3BUA000937R301
Section 74 BasicStation Comparison of Object View
Table 162. Visual Comparison of BasicStation Function Block (Continued)
3BUA000937R301 401
Comparison of BasicStation Parameters Section 74 BasicStation
Comparison of BasicStation Parameters

Table 163. BasicStation Parameters
Harmony INFI90FCLib
Spec Type Comments
S1 PV Input
S2 RSP Input
S3 A Input
S4 TR Input
S5 TS Input
S6 Imode Constant Imode Ranges 1, 2, 3 won't be supported here.
Only 5,6,7,8 are supported in INFI90M
S7 PVHA Tune
S8 PVLA Tune
S9 DEVA Tune
S10 PVSpan Tune
S11 PVZero Tune
S12 PVEUD Tune Data type changed from Integer to String
S13 SPSpan Tune
S14 SPZero Tune
S15 SPEUD Tune Data type changed from Integer to String
S16 n/a Not Implemented in INFI90FCLib
S18 MI Input
S19 AX Input
S20 CX Input
402 3BUA000937R301
Section 74 BasicStation Comparison of BasicStation Parameters
Table 163. BasicStation Parameters (Continued)
Harmony INFI90FCLib
Spec Type Comments
S23 Typ Constant Typ 1,2 are not supported
S24 EHA Input
S25 ELA Input
S26 EHD Input
S27 ELD Input
S28 AO Input
S29 TRS2 Input
S20 TRPV Input
N CO
N+1 SP
N+2 Auto
N+3 n/a Not Implemented in INFI90FCLib
N+4 CR
3BUA000937R301 403
Table 164. BasicStation (Console Database)
Parameters/
Console Type
INFI90FCLib
AUTO Station Mode Auto bool
BYPASS Control Output is N/A bool
bypassed
CMPTRSTS Computer Signal N/A
is OK
CO/Description Signal description N/A
CO/FOR Formatting CODecimal dint Only represents
decimal places
CO/HIGH High range of COHigh real
signal
CO/LOW Low range of COLow real
signal
CO/PERCENT Signal (SIG) as a N/A
percentage of
span
CO/SIG Analog Value CO real
CO/SIG:QS Quality String N/A
CO/SPAN Difference N/A
between low and
high ranges
CO/UNITS Engineering Units N/A
404 3BUA000937R301
Table 164. BasicStation (Console Database) (Continued)
Parameters/
Console Type
INFI90FCLib
DEVALM Deviation alarm N/A
summary
DEVALM/DESCRIPTION Signal description N/A
DEVLIM/FOR Formatting DevDecimal dint Only represents
decimal places
DEVLIM/HIGH High Range of DEVA real
signal
DEVLIM/LOW Low Range of NegDEVA real
signal
DEVLIM/PERCENT Signal (SIG) as a N/A
percentage of
span
DEVLIM/SPAN Difference N/A
between low and
high ranges
DEVLIM/UNITS Engineering Units N/A
HIGHDEV/ACKR Acknowledge AckReqHDev bool
Required
HIGHDEV/ACT Active N/A
HIGHDEV/ALARM Alarm State HiDevAlarm bool
HIGHDEV/ALMEN Alarm Event N/A
HIGHDEV/AREF Associate Value N/A
HIGHDEV/COM Current Event N/A
Comment
3BUA000937R301 405
Parameters/
Console Type
INFI90FCLib
HIGHDEV/COM0 Normal Status MsgRtn string[60]
Comment
HIGHDEV/COM1 Active State MsgHDev string[60]
Comment
HIGHDEV/COMP Complement input N/A
signal
HIGHDEV/DESCRIPTION Signal Description N/A
HIGHDEV/DUAL Dual acting event N/A
HIGHDEV/EN Enable EnableHDev bool
HIGHDEV/EPSCAT Sub category Of N/A
event point (high
limit)
HIGHDEV/PRI Current Event N/A
Priority
HIGHDEV/PRI0 Normal Priority N/A
HIGHDEV/PRI1 Active Priority AESevHDev dint
HIGHDEV/SIG Boolean Value HiDevAlarm bool
HIGHDEV/SIG0 Inactive State N/A
description
HIGHDEV/SIG1 Active State N/A
description
HIGHDEV/SUP Event suppressed N/A
by signal
HIGHDEV/UNACK Unacknowledged N/A
alarm
406 3BUA000937R301
Parameters/
Console Type
INFI90FCLib
HIGHDEV/UNACKEP Unacknowledged N/A
Event point
LOWDEV/ACKR Acknowledge AckReqLDev bool
Required
LOWDEV /ACT Active N/A
LOWDEV /ALARM Alarm State LoDevAlarm bool
LOWDEV /ALMEN Alarm Event N/A
LOWDEV /AREF Associate Value N/A
LOWDEV /COM Current Event N/A
Comment
LOWDEV /COM0 Normal Status MsgRtn string[60]
Comment
LOWDEV /COM1 Active State MsgLDev string[60]
Comment
LOWDEV /COMP Complement input N/A
signal
LOWDEV/DESCRIPTION Signal Description N/A
LOWDEV /DUAL Dual acting event N/A
LOWDEV /EN Enable EnableLDev bool
LOWDEV /EPSCAT Sub category Of N/A
event point
(high limit)
LOWDEV /PRI Current Event N/A
Priority
LOWDEV /PRI0 Normal Priority AESevRtn dint
3BUA000937R301 407
Parameters/
Console Type
INFI90FCLib
LOWDEV /PRI1 Active Priority AESevLDev dint
LOWDEV /SIG Boolean Value LoDevAlarm bool
LOWDEV /SIG0 Inactive State N/A
description
LOWDEV /SIG1 Active State N/A
description
LOWDEV /SUP Event suppressed N/A
by signal
LOWDEV /UNACK Unacknowledged N/A
alarm
LOWDEV /UNACKEP Unacknowledged N/A
Event point
MODELOCK Module has mode MODELOCK bool
locked
OUTSTS Handheld station N/A
has failed
OUTTRACKING Output is tracking TR real
an input value
RATIO Ratio Index StationRatio real
RATIO:QS Quality String N/A
REDTAG/ACT Red Tagging N/A Not supported
active
408 3BUA000937R301
Parameters/
Console Type
INFI90FCLib
SP/Description Signal description N/A
SP /FOR Formatting SPDecimal dint Only represents
decimal places
SP /HIGH High range of SPHigh real
signal
SP /LOW Low range of SPZero real
signal
SP /PERCENT Signal(SIG) as a N/A
percentage of
span
SP /SIG Analog Value SP real
SP /SIG:QS Quality String N/A
SP /SPAN Difference N/A real
between low and
high ranges
SP /UNITS Engineering Units SPEUD string[15]
SPTRACKING SP Tracking TRS2 bool
enabled
STNLVL Station is under N/A
Computer control
STNMODE Cascade or ratio StationMode bool
Mode selected
STNTYPE Station Type TypInternal real
STNTYPE:S Text Version of StationType string[25]
quality
3BUA000937R301 409
Parameters/
Console Type
INFI90FCLib
TUNEBLK Block number of N/A
feedback's tuning
Block
PV/Description Signal description N/A
PV/UNITS Engineering Units PVEUD string[15] Data type changed
from Integer to
String
Quality:S Text version of N/A
quality
PV/HIGH High range of PVHA real
signal
PV/LOW Low range of PVLA real
signal
PV/SIG Analog value PV real
status
information the number of
decimal places
PV/SIG:QS Quality string N/A
HIGH/SIG Boolean value HiAlarm bool
HIGHLIM High alarm limit PVHA real
LOW/SIG Boolean value LoAlm bool
LOWLIM Low alarm limit LALim real
410 3BUA000937R301
Parameters/
Console Type
INFI90FCLib
N/A N/A QualFlag bool Boolean value.
Depending upon
the value (False-
good quality, true-
bad quality)
indication "XXX" is
shown in the
faceplate as per
800xA standards.
HIGH/COM1 Active state MsgH string[60]
description
HIGH/PRI1 Active priority AESevH dint Priorities in
harmony connect
are mapped to
severity
parameters
HIGH/EN Enable EnableH bool
required
LOW/COM1 Active state MsgL string[60]
description
LOW/PRI1 Active priority AESevL dint Priorities in
harmony connect
are mapped to
severity
parameters
LOW/EN Enable EnableL bool
required
3BUA000937R301 411
Parameters/
Console Type
INFI90FCLib
BAD/PRI1 Active priority AESevBQ dint Priorities in
harmony connect
are mapped to
severity
parameters
BAD/EN Enable EnableBQ bool
required
HIGH/COM0, LOW/COM0 Inactive state MsgRtn string[60] Return message is
description the same for both
high and low alarm
HIGH/PRI0,LOW/PRI0, Normal priority AESevRtn dint Return severity is
BAD/PRI0 the same for both
high and low
alarms
N/A N/A PVQ dword New parameter of
data type dword for
input quality
412 3BUA000937R301
Section 74 BasicStation New/Changed Parameters
Parameters/
Console Type
INFI90FCLib
N/A N/A HLALMDB real This is a new
parameter
(Previously value of
this specification
came from
segment control
Block).
N/A N/A DEVALMDB real This is a new
parameter
(Previously value of
this specification
came from
segment control
Block).

3BUA000937R301 413
Differences in Graphical Interfaces Section 74 BasicStation
414 3BUA000937R301
Section 75 SeqGen

Table 165. Visual Comparison of SeqGen Function Block
3BUA000937R301 415
Comparison of Object View Section 75 SeqGen
Table 165. Visual Comparison of SeqGen Function Block (Continued)
N/A
N/A
416 3BUA000937R301
Section 75 SeqGen Comparison of SeqGen Parameters
Comparison of SeqGen Parameters

Table 166. SeqGen Parameters

Comment
S1 N/A Input S1 (Block address of Sequence generator) of
sequence generator is removed. This feature is
not required as to increase the number of steps
SeqGenGrp[ ] attached to SeqGen are increased.
All the outputs N - N+10 will be directed from
SeqGen Block.
S2 T Input
S3 SH Input
S4 TH Input
S5 RST Input
S6 JT Input
S7 JN Input
S8 OD Input
S9 SeqGenGrp[ ].DOM Tune The Tunable Parameter S9-S25 of Sequence
generator is replaced by one single Extensible
parameter SeqGenGrp. SeqGenGrp is of
SeqGenmask datatype which consists of group of
17 real parameter OM1-OM8 and OT1-OT8 and
disable mask DOM.
S10 SeqGenGrp[ ].OM1 Tune
S11 SeqGenGrp[ ].OT1 Tune
3BUA000937R301 417
Comparison of SeqGen Parameters Section 75 SeqGen
Table 166. SeqGen Parameters (Continued)

Comment
N O1 Output
N +1 O2 Output
N +2 O3 Output
N +3 O4 Output
N +4 O5 Output
N +5 O6 Output
N +6 O7 Output
N +7 O8 Output
N +8 CS Output
N +9 TR Output
N +10 STEP Output
418 3BUA000937R301
Section 75 SeqGen Differences in Functionality
This SeqGen sequence FB has no changes in functionality in comparison to
Harmony Function Code 161, but the implementation of the function code has been
changed.
As per the value in step number, the harmony system searches the leading Blocks in
the link for the required step number and transfers the step mask and step time to the
output. In harmony if more than 8 steps are required then sequence generator Blocks
are added. For example if 32 steps are required then four sequence generator Blocks
have to be connected.
In the INFI90FCLib library, the size of the Block is set while inserting, according to
the number of steps required to be connected. If less than eight step masks have to
be connected, set the number of the SeqGenGrp to one. If 16 step masks have to be
connected, set the number of the SeqGenGrp to 2.
For 8 step masks, SeqGenGrp = 1
16 step masks, SeqGenGrp = 2
32 step masks, SeqGenGrp = 3
64 step masks, SeqGenGrp = 4 etc.
The Figure 39 and Figure 40 shows sequence generator bocks used to provide
multiple steps and multiple outputs in harmony and INFI90FCLib.
3BUA000937R301 419
Differences in Functionality Section 75 SeqGen
Figure 39. SeqGen Function Block in Series and Parallel to Provide 24 Steps for 16
Outputs in Harmony
420 3BUA000937R301
Section 75 SeqGen Differences in Functionality
Figure 40. SeqGen Function Block to Provide 24 Steps and 16 Outputs in

INFI90FCLib
3BUA000937R301 421
Differences in Functionality Section 75 SeqGen
422 3BUA000937R301
Section 76 Pulse Positioner

Table 167. Visual Comparison of Pulse Positioner Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 423
Comparison of Object View Section 76 Pulse Positioner
Table 167. Visual Comparison of Pulse Positioner Function Block
424 3BUA000937R301
Section 76 Pulse Positioner Comparison of PulsePosn Parameters
Comparison of PulsePosn Parameters

Table 168. PulsePosn Parameters

S1 SP Input
S2 FB Input
S3 FwdRate Tune
S4 RevRate Tune
S5 DB Tune
S6 CycTime Tune
S7 Raise N/A
S8 Lower N/A
PulsePosn Function Block has no changes in functionality in comparison to
Harmony Function block, but the implementation of the function code has been
changed.
PulsePosnMngr will get the input from the parent function block PulsePosn.
Depending on the Command input from PulsePosn the PulsePosnMngr will run
the timer to generate the Raise or Lower signal. The pulse duration of these signal
is in accordance with the Duration input from PulsePosn, once the timer elapses
the duration time, Raise or Lower signal will be set to zero. This iteration will
continue in the next scan cycles.
Raise and Lower signal of PulsePosnMngr is connected to the Raise and Lower
output of PulsePosn respectively.
The PulsePosn Function Block has a child Control Module named PulsePosMngr1.
The PulsePosMngr1 is designed to execute in every 10 msec. Therefore, the
PulsePosMngr1 must be connected to a 'fast task' with a 10 msec interval time and
High priority. Any other interval time will result in undefined behavior.
3BUA000937R301 425
New/Changed Parameters Section 76 Pulse Positioner
If an application contains one or more instances of PulsePosn Function Block, the

user must specify the 'fast task' connection by creating a global variable with the
following properties:
Name: InfiAppFastTask
Data Type: string
Attributes: constant
Initial Value: The initial value specifies the name of the 'fast task'.
The 'fast task' must have these properties.
Interval Time: 10 msec.
Priority: High or Highest.
Unrelated Control Modules and Function Blocks may also be connected to the 'fast
task', as long as the task executes within the 10msec interval time as shown in
Figure 41.
The program must not be connected to the same task type as that of
InfiAppFastTask. If connected to the same task type, then there will be an error in
downloading the application.
The parent function block is having a IN_OUT parameter, it will flag an error when
connected to the same task type as shown in Figure 42.
The following are boundary conditions:
1. The minimum pulse duration is ten milliseconds and the smallest incremental
pulse length possible is ten milliseconds.
2. Cycle Time should be always greater than the pulse duration else the output
will be continuously True.
3. Cycle Time must not be less than normal task time.
426 3BUA000937R301
Section 76 Pulse Positioner Differences in Graphical Interfaces
Figure 41. InfiAppFastTask Connected to Application
Figure 42. InfiAppFastTask and Program Connected to Same Task

3BUA000937R301 427
Differences in Graphical Interfaces Section 76 Pulse Positioner
428 3BUA000937R301
Section 77 PulseRate

Table 169. Visual Comparison of PulseRate Function Block
View in Composer
View in Composer
N/A
3BUA000937R301 429
Comparison of PulseRate Parameters Section 77 PulseRate
Comparison of PulseRate Parameters

Table 170. PulseRate Parameters

S1 In Input
S2 Scale Tune
S3 LowCutOff Tune
N PulseOut N/A
PulseRate Function Block has no changes in functionality in comparison to
Harmony Function block, but the implementation of the function code has been
changed.
The output parameter PulseOut will be getting the number of pulses/sec from the
control module PulseRateMngr.Input to PulseRateMngr will be given from the
parent function block PulseRate. PulseRateMngr will execute the pulse
management and the output will be given back to the parent PulseRate Function
block.
The output pulses are always 50 milliseconds in duration and the minimum time
between pulses is 50 milliseconds, so there is a limit of ten pulses per second.
The PulseRate Function Block has a child Control Module named
PulseRateMngr1. The PulseRateMngr1 is designed to execute in every 10 msec.
Therefore, the PulseRateMngr1 must be connected to a 'fast task' with a 10 msec
interval time and High priority. Any other interval time will result in undefined
behavior.
If an application contains one or more instances of PulseRate Function Block, the
user must specify the 'fast task' connection by creating a global variable with the
following properties:
Name: InfiAppFastTask
Data Type: string
430 3BUA000937R301
Section 77 PulseRate New/Changed Parameters
Attributes: constant
Initial Value: The initial value specifies the name of the 'fast task'.
The 'fast task' must have these properties.
Interval Time: 10 msec.
Priority: High or Highest.
Unrelated Control Modules and Function Blocks may also be connected to the 'fast
task', as long as the task executes within the 10msec interval time as shown in
Figure 43.
The program must not be connected to the same task type as that of
InfiAppFastTask. If connected to same task type, then there will be an error in
downloading the application.
The parent function block is having a IN_OUT parameter, it will flag an error when
connected to any task type as displayed in Figure 44.
Figure 43. InfiAppFastTask Connected to Application
3BUA000937R301 431
Differences in Graphical Interfaces Section 77 PulseRate
Figure 44. InfiAppFastTask and Program Connected to Same Task

432 3BUA000937R301
Section 78 RateLimiter

Table 171. Visual Comparison of RateLimiter Function Block
View in Composer
View in Composer
3BUA000937R301 433
Comparison of Object View Section 78 RateLimiter
Table 171. Visual Comparison of RateLimiter Function Block
N/A
434 3BUA000937R301
Section 78 RateLimiter Comparison of RateLimiter Parameters
Comparison of RateLimiter Parameters

Table 172. RateLimiter Parameters

S1 In Input
S2 TS Input
S3 IncLimit Tune
S4 DecLimit Tune
N Out Output

3BUA000937R301 435
Differences in Graphical Interfaces Section 78 RateLimiter
436 3BUA000937R301
Section 79 Alarm and Event Handling
Alarm and Events Generation

The following input parameters need to be defined in Function Blocks for the alarms
to work in INFI90FCLib library. Suffix X in the parameter name in different
Function Blocks denotes the various alarm conditions like High deviation, High rate
etc.
In case of digital Blocks, there are only two states of alarms visualize alarms active
and no alarms.
a. Name - It is a maximum 30 character string which appears in the alarm
and event list when the alarm is active. If Name parameter is empty, no
alarms and events are generated.
b. Description - Object description. It is a maximum 40 character string
which appears in the alarm and event list when the alarm is active.
c. AEClass - It defines the class for all the alarms generated by the Function
Block. Its valid range is 1 to 9999. Any value greater than 9999 assigned
to AEClass is internally taken as 9999, and any value less than 1 assigned
to AEClass is internally taken as 1. This internally taken value can be seen
through the visible variable AEClassInternal in PPA. When internally
taken value is out of the valid range (1-9999) the alarm symbol with
question mark indicating incorrect alarm configuration appears on
the faceplate.
d. MessageX - It is a maximum 60 character string which appears in the
alarm and event list when the alarm is active.
e. AESeverityX - It is the severity of the alarm condition. Its valid range is 1
to 1000. Where 1 is the lowest severity alarm and 1000 is the highest
severity alarm. If the AESeverity is given a value out side this range the
3BUA000937R301 437
Alarm and Events Generation Section 79 Alarm and Event Handling
alarms in the Function Block do not work and an alarm symbol with
question mark appears on the faceplate.
f. EnableX - The alarms for the condition are generated from the Function
Block only when this parameter is set to true. If it is set to false then no
alarms are generated for this Function Block. Eg. EnableBQ set to true
enables the generation of bad quality alarms if the quality goes bad.
g. AckReqX - When set to true then operator is required to acknowledge the
active alarms for the particular condition.
h. EnableEvt - If Alarms are enabled then, both alarm and events are
generated. If alarms are disabled and if event is enabled
(EnableEvt = true) then simple events are generated, otherwise no events
are generated. This is applicable for all digital Blocks except DOL. Incase
of DOL, events are generated only when AlmDef=2 (alarms disabled,
event mode) and EnableEvt is set true.
i. MsgRtn - Return to normal message is the maximum 60 character string
which appears in the alarm and event list when the alarm returns to
normal.
j. AESevRtn - It is the severity of the alarm condition return to normal. Its
valid range is 1 to 1000.
k. CondNameX - The condition name for the alarm conditions can be
modified in INFI90FCLib library through the INFI90FCLib Alarm and
Event Translator aspect as illustrated in Figure 45. For example,
'||I90_High' in INFI90FCLib Alarm and Event Translator aspect, indicates
the high alarm condition name for all high alarms configured in the
INFI90FCLib library.
l. FilterTime - Positive pulse on signal shorter than this is not noted. Range-
0 -3600s else warning (prev.valid value used) or Error (no alarm created).
Filter time allows the engineer to define a time delay on the input signal
before trigger and clearing of an event, and before the triggering of an
alarm, the filter time will not be triggered on clearing of an alarm. The
filter time does not have any impact on the output signal of DOL. The
Parameter OutA is updated only after the filter time is expired. The OutA
parameter can take one of the dwords as shown in Table 173.
438 3BUA000937R301
Section 79 Alarm and Event Handling Alarm and Events Generation
Table 173. Dword Alarm Status Codes (Project Constants) defined in INFI90FCLib Library
Name Default Value Data Type Description

cINFIAlmSts.Auto 16#4000 dword Mode= auto for MSDD or Device Driver
cINFIAlmSts.DHHHi 16#0400 dword Deviation HHH (future implementation)
cINFIAlmSts.DHHi 16#0040 dword Deviation HH (future implementation)
cINFIAlmSts.DHi 16#0004 dword Deviation H for DAANG or Station
cINFIAlmSts.DLLLo 16#0800 dword Deviation LLL (future implementation)
cINFIAlmSts.DLLo 16#0080 dword Deviation L (future implementation)
cINFIAlmSts.DLo 16#0008 dword Deviation L for DAANG or Station
cINFIAlmSts.HHHi 16#0100 dword HHH for DAANG
cINFIAlmSts.HHi 16#0010 dword HH for DAANG
cINFIAlmSts.Hi 16#0001 dword H for all analog and digital Blocks
cINFIAlmSts.LLLo 16#0200 dword LLL for DAANG
cINFIAlmSts.LLo 16#0020 dword LL for DAANG
cINFIAlmSts.Lo 16#0002 dword L for all analog Blocks
cINFIAlmSts.Remote 16#8000 dword Remote mode enabled for Device Driver
cINFIAlmSts.RHi 16#1000 dword Rate High for DAANG
cINFIAlmSts.RLo 16#2000 dword Rate Low for DAANG
3BUA000937R301 439
Alarm Inhibition Section 79 Alarm and Event Handling
Figure 45. INFI90FCLib Alarm and Event Translator Aspect
Alarm Inhibition
• Harmony system supports Tag Based Inhibit, Manual Inhibit and Group
Inhibit. In 800xA system alarm inhibition at Block level or through any aspect
does not exist. This functionality can be achieved from the plant explorer
through alarm hiding configuration.The alarm hiding function in 800xA, makes
it possible to eliminate the appearance in the alarm list of one or more alarms.
440 3BUA000937R301
Section 79 Alarm and Event Handling Bad Quality Alarms
Single alarms can be hidden as well as all alarms from an object and its
descendants.
Procedure to inhibit alarms

• Add a "Hiding mask object" in the library structure.
• Configuring hiding rules for all the objects to be hidden.
• When it is evaluated to true will hide alarms for specific objects or group of
objects. The condition can be an OPC property expression or an alarm
condition.
Using the above procedure functionalities like manual inhibit, tag based inhibit and
group inhibit can be achieved quite easily.
Bad Quality Alarms

Bad quality alarms are generated whenever the input/output quality is other than
16#0,16#D8,16#C0. To enable or disable the bad quality alarms the parameter
EnableBQ is set to true or false respectively. The parameters AESevBQ and
AESevRtn define the bad quality active alarm severity and return alarm severity
respectively. The condition name for the bad quality alarm condition can be
modified in INFI90FCLib library through the INFI90FCLib Alarm and Event
Translator aspect.
Table 174 provides the NLS ID used for bad quality alarm conditions.
Table 174. NLS ID used for Bad Quality Alarm Conditions
Name Data Type Description

'||I90_BadQ' string[15] Name of the Condition BQ
'||I90_BadQActive' string[60] Message for alarm condition BQ
'||I90_BadQRTN' string[60] Message for alarm condition BQRtn
When the quality is bad no other alarms or events are generated by the Function
Block.
3BUA000937R301 441
Bad Quality Messages Section 79 Alarm and Event Handling
Bad Quality Messages

In INFI90FCLib 1.0-0, bad quality messages are hard coded and NLS supported.
The message can be changed from the “INFI90FCLib Alarm and event translator
aspect” in the INFI90FCLib 1.0-0 library in the Object Type structure.
442 3BUA000937R301
Section 80 Programmatic Interface
Batch90/UDF Migration
Harmony (Infi90H)
In Infi90H, there are several Function Block types that are programmed by the user
- for example, BSEQ, UDF, Invoke C/C Allocation. Infi90H provides two
programming languages - B90 (Batch/UDF FB) and C (Invoke C FB). These
Function blocks can be referred to as the programmable Function Blocks (pFBs).
The user programs the behavior of a pFB in the Batch90 or C language.
Some normal (non-programmable) Infi90H Function blocks have a special, hidden
Control-Interface in addition to the regular Function block Input/Output
connections. These Function blocks are referred to as ciFBs. A pFB communicates
with a ciFB through the ciFBs Control-Interface. The pFB can send commands to
the ciFB and read status data from the ciFB through the ciFBs Control-Interface.
Control-Interface connections are not specified in Composer and are not visible in
Composer. Control-Interface connections are specified in the B90 or C
programming environment. In the programming environment, a Function Block is
identified by its Function Block number and Function Block type.
Infi90H also provides a means to specify a list of (array) Function block numbers.
This allows a pFB to access any ciFB in a list.
3BUA000937R301 443
INFI90FCLib (Infi90M) Section 80 Programmatic Interface
Figure 46. Control Interface Interaction between Non-programmable and

Programmable Function Blocks
INFI90FCLib (Infi90M)
INFI90FCLib contains a set of Function Blocks that provide functionality similar to
the Harmony' Function Blocks with a Control-Interface (ciFBs). These
INFI90FCLib Function Blocks are called zBlocks.
INFI90FCLib does not contain any Function Blocks equivalent to the Harmony's
programmable Function Blocks (BSEQ, PHASEX, UDF, etc).
Control Builder provides a rich programming environment (e.g., Structured Text,
Sequential Function Charts), but the B90 programming language is not supported.
Porting a B90 or C program from Harmony to AC800M will require manual
translation and usually some redesign.
Infi90M provides the following categories of Function Blocks:
1. zBlock
2. zBlockList
444 3BUA000937R301
Section 80 Programmatic Interface INFI90FCLib (Infi90M)
3. zVarList
zBlock
zBlock Function Blocks are similar to the Infi90H ciFBs. In INFI90FCLib, the
Control-Interface is called the zInterface. The zInterface is implemented explicitly
as an in_out parameter called the zi parameter.
In INFI90FCLib, for those Function blocks that need a Control-Interface, there are
two versions of the function block- the normal version (without the zInterface) and
the zBlock version (with the zInterface). The zBlock version provides functionality
that is equivalent to the normal Function Block and adds the zInterface
functionality.
Each zBlock type has exactly one zi parameter. The zi parameter (like the Infi90H
Control-Interface) accepts commands from a user defined Function Block (or
Control Module) and provides status data back to the pM's. Refer to the figures
below.
3BUA000937R301 445
Figure 47. Control Interface Interaction between zBlocks and User Defined
Programs
zBlockList and zVarList FBs

zBlockLists and zVarLists provide functionality similar to Arrays in the Harmony
B90 programming environment. User-defined code selects an item from a list and
sends commands to the selected item and reads status data from the selected item.
446 3BUA000937R301
Section 80 Programmatic Interface INFI90FCLib (Infi90M)
A zBlockList is a user-defined list (array) of zBlocks. There is a zBlockList type for

each zBlock type. For example, Function Block type zlAOL is the zBlockList for
Function Block type zAOL. All members of a zBlockList must be of the same type.
A zBlockList has the following two parameters:
1. zi - this is the control parameter. The user-defined Function Block (or Control
Module) connects to this parameter.
2. ziList - this parameter defines the list of zBlocks. It is an extensible parameter.
This means it is actually an array of parameters. The size (number of
parameters) is specified by the user for each instance of the Function Block.
Each ziList parameter connects to the zi parameter of a zBlock. All the zi
parameters must have the same data type.
A zVarList is a user-defined list (array) of simple variables. There are four zVarList
types - zlReal, zlDint, zlBool, zlString.
A zVarList has the following two parameters:
1. zi - this is the control parameter. The user-defined Function Block or Control
Module connects to this parameter.
2. ziList - this parameter defines the list of variables. It is an extensible parameter.
Each ziList parameter connects to a variable or a Function Block parameter.
The variable or zi parameter must have the same data type as the ziList.
For more details, refer to Fig.
Function Block A is user-defined. It has an in_out parameter named MyAOLList.
MyAOLList is connected to the zi parameter of the Function Block named
zAOLList1. Each ziList parameter is connected to the zi Parameter of a zAOL
Function Block. MyAOLList and all the connected zi parameters have date type
ziAOL. The 'zi' data types are defined in INFI90FCLib.
Function Block B is user-defined. It has an in_out parameter named MyRealList.
MyRealList connects to a list of reals. Note that the Function Blocks in this list are
type AOL, not zAOL. The list connections are to the In parameters of the AOL
blocks (which have type real).
Function Block B's real list has a very limited functionality as compared to Function
Block A's zi list.
3BUA000937R301 447
Figure 48. Example of using zBlock List FBs with corresponding zBlock FBs
448 3BUA000937R301
Section 80 Programmatic Interface zBlocks
zBlocks
zAOL

Table 175. Visual Comparison of zAOL Function Block
View in Composer
View in Composer
3BUA000937R301 449
zAOL Section 80 Programmatic Interface
Table 175. Visual Comparison of zAOL Function Block (Continued)
N/A
450 3BUA000937R301
Section 80 Programmatic Interface zAOL
Table 175. Visual Comparison of zAOL Function Block (Continued)
3BUA000937R301 451
zAOL Section 80 Programmatic Interface
Comparison of zAOL Parameters

Table 176 below lists the Harmony specifications and equivalent parameters in
INFI90FCLib Library.
Table 176. Comparison of zAOL Parameters
Harmony INFI90FCLib
Spec Type Comments
S1 N.A N.A In Harmony, the parameter S1 is connected to
Block No. 2 to enable control from pFB's. In
INFI90FCLib, they are no longer required.
S2 EUD Tune Data type changed from Integer to String
S3 Zero Tune Spec Type changed from Constant to Tune
S4 Span Tune Spec Type changed from Constant to Tune
S5 HALim Tune
S6 LALim Tune
S7 NA NA Exception reporting is no longer supported and
hence this parameter is removed
N Out NA
NA zVarError NA This is a new output parameter. When zInterface in
multiple FBs (of same type) are connected to same
variable, zVarError provides the error indication.
NA zi NA This is a new parameter added to provide
zInterface.
NA zRamp Input This is a new parameter added to provide the ramp
functionality that was available in ramp active data
structure used in B90/UDF programming language.
When zi.SetRamp=True, Out tracks the value of
parameter zRamp. The output from the zRamp
block or any other valid source can be connected to
the parameter zRamp of the zAOL block to match
the behavior in harmony system.
Console database of zAOL is same as that of standard AOL function block.
452 3BUA000937R301
Section 80 Programmatic Interface zRCM
zRCM

Table 177. Visual Comparison of zRCM Function Block
View in Composer
View in Composer
3BUA000937R301 453
zRCM Section 80 Programmatic Interface
Table 177. Visual Comparison of zRCM Function Block (Continued)
N/A
454 3BUA000937R301
Section 80 Programmatic Interface zRCM
Table 177. Visual Comparison of zRCM Function Block (Continued)
3BUA000937R301 455
zRCM Section 80 Programmatic Interface
Comparison of zRCM Parameters

Table 178. Comparison of zRCM Parameters
Harmony INFI90FCLib
Spec Type Comment
S1 Set Input
S2 Perm Input
S3 Rst Input
S4 Ovr Input
S5 Init Input
S6 FB Input
S7 Alm Input
S8 Typ Input This parameter acts only as a feedback indicator.
When set true, displays the feedback indicator
(arrow) in the faceplate elements.
N Out
N.A zi N.A This is a new parameter added to provide
zInterface.
Console database of zRCM is same as that of standard RCM function block.
456 3BUA000937R301
Section 80 Programmatic Interface zDeviceDriver

There are no major differences in graphical interface. A "Lock" text is added (NLS
supported) and it will appear in the indicator row in the faceplate when
zi.SetBlockFP=True.
zDeviceDriver

Table 179. Visual Comparison of zDeviceDriver Function Block
View in Composer
View in Composer
3BUA000937R301 457
zDeviceDriver Section 80 Programmatic Interface
Table 179. Visual Comparison of zDeviceDriver Function Block (Continued)
N/A
458 3BUA000937R301
Table 179. Visual Comparison of zDeviceDriver Function Block (Continued)
3BUA000937R301 459
zDeviceDriver Section 80 Programmatic Interface
Comparison of zDeviceDriver Parameters

Table 180. Comparison of zDeviceDriver
Harmony INFI90FCLib
Specifications Parameters Spec Type Comments
S1 N.A Input In Harmony, parameter S1 is connected to

Block No. 0 to enable control from pFBs. In
S2 FB1 Input
S3 FB2 Input
S4 COS Tune The mask are of data type dint. The One's place
and Hundred's place digits entered are taken as
mask other digits are ignored.
S5 OP Input
S6 OS Input
N.A. OSEnable Constant OSEnable.True=Enable Remote, False=Disable
Remote.
S7 FBM0 Tune The mask are of data type dint. The last 2 digits
entered are taken as mask other digits are
ignored.
S8 FBM1 Tune The mask are of data type dint. The last 2 digits
entered are taken as mask other digits are
ignored.
S9 FBTime Tune
S10 N.A. Input Not Implemented in INFI90FCLib
N O
N+1 ST
460 3BUA000937R301
Table 180. Comparison of zDeviceDriver (Continued)
Harmony INFI90FCLib
Specifications Parameters Spec Type Comments
N.A. OutA Alarm Status Output.

NA zVarError NA This is a new output parameter. When
zInterface in multiple FBs (of same type) are
connected to same variable, zVarError provides
the error indication.
zInterface.
Console database of zDeviceDriver is same as that of standard DeviceDriver

function block.

zi.SetBlockFP=True.
3BUA000937R301 461
zMSDD Section 80 Programmatic Interface
zMSDD

Table 181. Visual Comparison of zMSDD Function Block
View in Composer
View in Composer
462 3BUA000937R301
Section 80 Programmatic Interface zMSDD
Table 181. Visual Comparison of zMSDD Function Block (Continued)
N/A
3BUA000937R301 463
Table 181. Visual Comparison of zMSDD Function Block (Continued)

464 3BUA000937R301
Section 80 Programmatic Interface zMSDD
Comparison of zMSDD Parameters
Table 182. Comparison of zMSDD Parameters
Harmony INFI90FCLib
Spec Type Comment
S1 N.A N.A In Harmony, the Specs S1, S2 are connected to Block
No. 0 to enable control from pFB's. In INFI90FCLib,
they are no longer required.
S2 N.A N.A
S3 F1 Input
S4 F2 Input
S5 F3 Input
S6 F4 Input
S7 OM0 Constant The mask are of data type dint. The last 3 digits
entered are taken as mask other digits are ignored.
S8 OM1 Constant
S9 OM2 Constant
S10 OM3 Constant
S11 FM1 Tune The feedback mask are of data type dint. The last 4
digits entered are taken as feedback mask other
digits are ignored.
S12 FM2 Tune
S13 FM3 Tune
S14 COSO Tune The parameter is of data type dint. The last 3 digits
entered are taken as input, other digits are ignored.
S15 MP Tune
S16 FBWait Tune
S17 FltWait Tune
3BUA000937R301 465
Table 182. Comparison of zMSDD Parameters (Continued)
Harmony INFI90FCLib
Spec Type Comment
S18 N.A Constant
S19 Nxt1 Tune
S20 Nxt2 Tune
S21 Nxt3 Tune
S22 Ptime Tune
S23 IM Constant
S24 N.A N.A In harmony when S1, S2 are connected to Block No.
0, S24 does not provide any functionality. Hence TS
is removed in zMSDD.
S25 Ovr Input
N CO1
N+1 CO2
N+2 CO3
N+3 ST
N.A zi N.A This is a new parameter added to provide zInterface.
Console database of zMSDD is same as that of standard MSDD function block.

zi.SetBlockFP=True.
466 3BUA000937R301
Section 80 Programmatic Interface zFGen
zFGen

Table 183. Visual Comparison of zFGen Function Block
N/A N/A
View in Composer
View in Composer
N/A
N/A
Compare FGEN and zFGen

In a Harmony system, FGEN is an active data structure in the Batch90/UDF
3BUA000937R301 467
zFGen Section 80 Programmatic Interface
programming language. In INFI90FCLib, the related object is a zFGen Function

Block.
Configure a function generator
B90 Declaration for FGEN:
FGEN Name (( …,(timeN, ValueN),…), units
Where:
Name - Name of an FGEN instance
(timeN, ValueN) - Breakpoints
units - Time units
Table 184. Configuration of FGEN and zFGen
B90 Declaration Data zFGen Function Block Parameters

Name: User B90 code reads zi: User ST code reads status data from and writes commands
status data from and writes to the zFGen Function Block via a variable connected to the
commands to an FGEN using zFGen's zi parameter. In the sections below, this zi variable is
its name. In the sections below, referred to as ziVarName.
it's referred to as fgenName.
Breakpoints: The set of time- BrkPnt: This is an extensible parameter with one element for
value pairs that define the each breakpoint. Each element has two components - time and
function value
Units: Units of time Units: Unit of time. This is a constant parameter
(Sec, Min, Hour) 0=seconds
1=minutes
2=hours
N/A Val: Current value
N/A Tim: Current time value (sec/min/hour)
N/A Sts: Current Status. False=Holding, True=Running
468 3BUA000937R301
Section 80 Programmatic Interface zFGen
Reading Status Data from a Function Generator
Table 185. Comparison of Reading Status Data in B90 and zFGen FB
B90 Status Data zi Status Data

Value = fgenName.STS Value = ziVarName.Sts;
Value = fgenName.TIM Value = ziVarName.Tim;
Value = fgenName.VAL Value = ziVarName.Val;
Function Generator Commands
Table 186. Comparison of Writing Commands in B90 and zFGen FB
B90 Commands zi Commands

HOLD fgenName ziVarName.SetHold = True (or 1);
RESET fgenName (time) ziVarName.SetResetTim = time;
ziVarName.SetReset = True (or 1);
(Uses time from previous SetResetTim command)
START fgenName ziVarName.SetStart =True (or 1);
3BUA000937R301 469
zStation Section 80 Programmatic Interface
zStation

Table 187. Visual Comparison of zStation Function Block
470 3BUA000937R301
Section 80 Programmatic Interface zStation
Table 187. Visual Comparison of zStation Function Block (Continued)
N/A
3BUA000937R301 471
Table 187. Visual Comparison of zStation Function Block (Continued)
472 3BUA000937R301
Comparison of zStation Parameters

Table 188. Comparison of zStation Parameters
Harmony INFI90FCLib
Spec Type Comments
S1 PV Input
S2 RSP Input
S3 A Input
S4 TR Input
S5 TS Input
S6 Imode Constant Imode Ranges 1, 2, 3 won't be supported here.
Only 5,6,7,8 are supported in INFI90M
S7 PVHA Tune
S8 PVLA Tune
S9 DEVA Tune
S10 PVSpan Tune
S11 PVZero Tune
S12 PVEUD Tune Data type changed from Integer to String
S13 SPSpan Tune
S14 SPZero Tune
S15 SPEUD Tune Data type changed from Integer to String
S18 MI Input
S19 AX Input
S20 CX Input
3BUA000937R301 473
Table 188. Comparison of zStation Parameters (Continued)
Harmony INFI90FCLib
Spec Type Comments
S23 Typ Constant Typ 1,2 are not supported
S24 EHA Input
S25 ELA Input
S26 EHD Input
S27 ELD Input
S28 AO Input
S29 TRS2 Input
S20 TRPV Input
N.A zRampSP Input This is a new parameter added to provide the ramp
When zi.SetRampSP=True and conditions permit,
SP tracks the value of parameter zRampSP. The
output from the zRamp block or any other valid
source can be connected to the parameter
zRampSP of the zStation block to match the
behavior in harmony system.
N.A zRampCO Input This is a new parameter added to provide the ramp
When zi.SetRampCO=True and conditions permit,
CO tracks the value of parameter zRampCO. The
output from the zRamp block or any other valid
source can be connected to the parameter
zRampCO of the zStation block to match the
behavior in harmony system.
N CO
N+1 SP
N+2 Auto
474 3BUA000937R301
Table 188. Comparison of zStation Parameters (Continued)
Harmony INFI90FCLib
Spec Type Comments
N+4 CR
zInterface.
Console database of zStation is same as that of standard Station function block.

zi.SetBlockFP=True.
3BUA000937R301 475
zDOL Section 80 Programmatic Interface
zDOL
Table 189. Visual Comparison of zDOL Function Block
N/A
476 3BUA000937R301
Section 80 Programmatic Interface zDOL
Table 189. Visual Comparison of zDOL Function Block (Continued)
3BUA000937R301 477
zDOL Section 80 Programmatic Interface
Comparison of zDOL Parameters
Table 190. zDOL Parameters

Comment
S1 NA Input In Harmony, the Spec S1is connected to Block
No. 2 to enable control from pFBs. In
S2 AlmDef Tune Parameter Spec Type changed from constant to
tune. Whenever AlmDef changes value from 0 or
1 to 2, alarm states are cleared on the output.
N Out
N.A zVarError N.A This is a new output parameter. When zInterface
in multiple FBs (of same type) are connected to
same variable, zVarError provides the error
indication.
zInterface.
Console database of zDOL is same as that of standard DOL Function Block.
478 3BUA000937R301
Section 80 Programmatic Interface zRMCB
zRMCB
Table 191. Visual Comparison of zRMCB Function Block
3BUA000937R301 479
zRMCB Section 80 Programmatic Interface
Table 191. Visual Comparison of zRMCB Function Block (Continued)
N/A
480 3BUA000937R301
Table 191. Visual Comparison of zRMCB Function Block (Continued)
3BUA000937R301 481
zRMCB Section 80 Programmatic Interface
Comparison of zRMCB Parameters
Table 192. Comparison of zRMCB Parameters
Harmony INFI90FCLib
Spec Type Comment
S1 NA Input In Harmony, the parameter S1 is connected to
S2 NA Input In Harmony, the parameter S2 is connected to
S3 ILK1 Input
S4 ILK2 Input
S5 ILK3 Input
S6 ILK4 Input
S7 FB1 Input
S8 FB2 Input
S9 Perm1 Input
S10 Perm2 Input
S11 FBWait Tune
S12 PON Tune
S13 POFF Tune
S14 NA NA Removed
S15 NA NA Removed
S16 HSTS Constant
S17 FBWait2 Constant
N RS NA
N+1 OnP NA
482 3BUA000937R301
Table 192. Comparison of zRMCB Parameters (Continued)
Harmony INFI90FCLib
Spec Type Comment
N+2 OffP NA
N+3 ST NA
NA zVarError NA This is a new output parameter. When zInterface
in multiple FBs (of same type) are connected to
same variable, zVarError provides the error
indication.
zInterface.
Console database of zRMCB is same as that of standard RMCB Function Block.
Difference in Graphical Interface

There is no major difference in graphical interface. A “Lock” text is added (NLS
zi.SetBlockFP=True.
3BUA000937R301 483
zREMSET Section 80 Programmatic Interface
zREMSET
Table 193. Visual Comparison of zREMSET Function Block
View in Composer
View in Composer
NA
484 3BUA000937R301
Section 80 Programmatic Interface zREMSET
Table 193. Visual Comparison of zREMSET Function Block (Continued)

3BUA000937R301 485
zREMSET Section 80 Programmatic Interface
Comparison of zREMSET Parameters
Table 194. Comparison of zREMSET Parameters

Comment
S1 EUD Tune Changed from Integer to string
S2 HoLim Tune
S3 LoLim Tune
S4 Init Constant
S5 TS Input
S6 TR Input
N Out
NA zi NA This is a new parameter added to provide zInterface.
NA zRamp Input This is a new parameter added to provide the ramp
When zi.SetRamp=True and conditions permit, Out
tracks the value of parameter zRamp. The output from
the zRamp block or any other valid source can be
connected to the parameter zRamp of the zREMSET
block to match the behavior in harmony system.
Console database of zREMSET is same as that of standard REMSET Function

Block.
486 3BUA000937R301
Section 80 Programmatic Interface zTexSel

There is no major difference in the graphical interface of this Function Block. A
“Lock” text is added (NLS supported) and it will appear in the indicator row in the
faceplate when zi.SetBlockFP=True.
zTexSel
Table 195. Visual Comparison of zTexSel Function Block
View in Composer
View in Composer
3BUA000937R301 487
zTexSel Section 80 Programmatic Interface
Table 195. Visual Comparison of zTexSel Function Block (Continued)
N/A
488 3BUA000937R301
Section 80 Programmatic Interface zTexSel
Table 195. Visual Comparison of zTexSel Function Block (Continued)
Comparison of zTexSel Parameters

Table 196. Comparison of zTexSel Parameters
Comments
S1 NA Input In Harmony, S1 parameter is connected to Block No. 5
to enable control from pFB's. In INFI90FCLib, they are
not required.
3BUA000937R301 489
zTexSel Section 80 Programmatic Interface
Table 196. Comparison of zTexSel Parameters (Continued)

S2 NA Input In Harmony, the parameter S2 is connected to Block No.
5 to enable control from pFB's. In INFI90FCLib, they are
no longer required.
S3 NA Input In Harmony, the parameter S3 is connected to Block No.
0 to enable control from pFB's. In INFI90FCLib, they are
no longer required.
S4 CtrlSts Input
N/A EnCtrlSts Constant New Parameter of Type bool for enable /disable of
CtrlSts
S5 GoodMsg Constant
S6 GoodClr Constant
S7 GoodBnk Constant
S8 BadMsg Constant
S9 BadClr Constant
S10 BadBnk Constant
S11 WaitMsg Constant
S12 WaitClr Constant
S13 WaitBnk Constant
S14 N/A
S15 N/A
S16 N/A
N Out Output Type is changed from Real to Dint.
NA zi NA New parameter added to provide zInterface.
Console database of zTexSel is same as that of standard TexSel Function Block.
490 3BUA000937R301
Section 80 Programmatic Interface zAPID
zAPID
Table 197. Visual Comparison of zAPID Function Block
View in Composer
View in Composer
3BUA000937R301 491
zAPID Section 80 Programmatic Interface
Table 197. Visual Comparison of zAPID Function Block (Continued)
N/A
492 3BUA000937R301
Section 80 Programmatic Interface zAPID
Table 197. Visual Comparison of zAPID Function Block (Continued)
Comparison of zAPID Parameters
Table 198. Comparison of zAPID Parameters

S1 PV Input
S2 SP Input
S3 TR Input
S4 TS Input
3BUA000937R301 493
zAPID Section 80 Programmatic Interface
Table 198. Comparison of zAPID Parameters (Continued)

S5 ExtRst Input
S6 FF Input
S7 N/A
S8 N/A
S9 II Input
S10 DI Input
S18 Ver Constant
S19 Typ Constant
S22 N/A
S23 N/A
N CO
N+1 BI
N+2 BD
N/A OutA
NA zVarError NA This is a new output
parameter. When zInterface
in multiple FBs (of same
type) are connected to
same variable, zVarError
provides the error
indication.
N/A zi This is a new parameter
added to provide zInterface.
494 3BUA000937R301
Section 80 Programmatic Interface zISC
zISC
Table 199. Visual Comparison of zISC Function Block
View in Composer
View in Composer
NA
View in Control BuilderM View in Control BuilderM
3BUA000937R301 495
zISC Section 80 Programmatic Interface
Table 199. Visual Comparison of zISC Function Block (Continued)
Comparison of zISC Parameters
Table 200. Comparison of zISC Parameters
Harmony INFI90FCLib
Spec Type Comment
S1 PV Input
S2 SP Input
S3 TR Input
S4 TS Input
S5 C Input
S6 ExtRef Input
N CO output
496 3BUA000937R301
Section 80 Programmatic Interface zISC
Table 200. Comparison of zISC Parameters (Continued)
Harmony INFI90FCLib
Spec Type Comment
NA zVarError NA This is a new output parameter.
When zInterface in multiple FBs
(of same type) are connected to
same variable, zVarError provides
the error indication.
N.A zi This is a new parameter added to
provide zInterface.
3BUA000937R301 497
zInteg Section 80 Programmatic Interface
zInteg
Table 201. Visual Comparison of zInteg Function Block

NA NA
N/A
N/A
Comparison of Integrator and zInteg Parameters

In a Harmony system, INTEGRATOR is an active data structure in the
Batch90/UDF programming language. In INFI90FCLib, the related object is a
zInteg Function Block.
Configuring an Integrator
B90 Declaration for INTEGRATOR:
INTEGRATOR name (input, units)
498 3BUA000937R301
Section 80 Programmatic Interface zInteg
Where:
name Name of an INTEGRATOR instance
input Name of value to be integrated. This name must refer to a data object
that has already been declared (for example, batch data, data, phase
subroutine, state subroutine, and local data).
units Time units (Seconds, Minutes, Hours)
.
Table 202. B90 Declaration Data and zInteg FB Parameters
B90 Declaration Data zInteg Function Block Parameters

Name: User B90 code reads status data zi: User ST code reads status data from and writes
from and writes commands to an commands to the zInteg Function Block via a
INTEGRATOR using its name. In the variable connected to the zInteg's zi parameter. In
sections below, it’s referred to as the sections below, this zi variable is referred to as
integratorname. ziVarName.
Input: Name of value to be integrated. In: Input value that has to be integrated.
Units: Units of time Units: Unit of time. This is a constant parameter.
(SEC=Seconds, MIN=Minutes, 0=seconds, 1=minutes, 2=hours.
HOUR=Hours)
N/A Val: Current value of integrator
Reading Status Data from an Integrator

Table 203. Comparison of Reading Status Data in B90 and zInteg FB

Value = integratorname.STS Value := ziVarName.Sts ;
Value = integratorname.VAL Value := ziVarName.Val ;
Commands to an Integrator
Table 204. Comparison of Writing Commands in B90 and zInteg FB

HOLD integratorname ziVarName.SetHold := True (or 1);
3BUA000937R301 499
zRamp Section 80 Programmatic Interface
Table 204. Comparison of Writing Commands in B90 and zInteg FB (Continued)

RESET integratorname (value) ziVarName.SetResetVal := value;
ziVarName.SetReset := True (or 1); (Uses value from
previous SetResetVal command)
START integratorname ziVarName.SetStart :=True (or 1);
zRamp

Table 205. Visual Comparison of zRamp Function Block
N/A N/A
N/A
N/A
Comparison of Ramp and zRamp Parameters

In a Harmony system, RAMP is an active data structure in the Batch90/UDF
programming language.
500 3BUA000937R301
Section 80 Programmatic Interface zRamp
In INFI90FCLib, the related object is a zRamp Function Block.

Configuring a Ramp
B90 Declaration for RAMP:
RAMP name (vname, units)
Where:
name Name of a RAMP instance
vname Name of the value to be ramped. This value must be one of the
following types:
AOL.VAL,
CS.CO,
CS.SP,
REMSET.VAL,
RBUF.VAL,
VAR,
(or an array element of one of the above types)
Table 206. Comparison of B90 Declaration Data and zRamp FB Parameters
B90 Declaration Data zRamp Function Block Parameters

Name: User B90 code reads zi: User ST code reads status data from and writes commands to
status data from and writes the zRamp Function Block via a variable connected to the
commands to an RAMP using zRamp's zi parameter. In the sections below, this zi variable is
its name. In the sections below, referred to as ziVarName.
it's referred to as rampname.
3BUA000937R301 501
zRamp Section 80 Programmatic Interface
Table 206. Comparison of B90 Declaration Data and zRamp FB Parameters (Continued)
B90 Declaration Data zRamp Function Block Parameters

Vname: Name of value to be There is no equivalent parameter. But to support this
ramped. functionality, new input parameters are defined in zAOL,
zREMSET and zStation blocks.
E.g in zAOL, two parameters are added: zRamp, zi.SetRamp.
When zi.SetRamp=True, parameter Out tracks the value of
zRamp.
For details refer to the zAOL, zREMSET and zStation blocks.
Units: Units of time Units: Unit of time. This is a constant parameter. 0=seconds,
(SEC=Seconds, MIN=Minutes, 1=minutes, 2=hours.
HOUR=Hours)
N/A Val: Current value
Reading Status data from a Ramp
Table 207. Comparison of Reading Status Data in B90 and zRamp FB

Value = rampname.VAL Value := ziVarName.Val;
Value = rampname.STS Value := ziVarName.Sts;
Value = rampname.LIM Value := ziVarName.Lim;
Value = rampname.RATE Value := ziVarName.Rate;
502 3BUA000937R301
Section 80 Programmatic Interface zRamp
Commands to a Ramp
Table 208. Comparison of Writing Commands in B90 and zRamp FB

HOLD rampname ziVarName.SetHold := True (or 1);
RESUME rampname ziVarName.SetResume := True (or 1);
START rampname FROM (value1) To ziVarName.SetInitVal:=value1;
(value2) AT (value3) ziVarName.SetLim:=value2;
ziVarName.SetRate:=value3;
ziVarName.SetStart :=True (or 1); (Uses value1,
value2, value3 from previous SetInitVal, SetLim and
SetRate commands)
3BUA000937R301 503
zTimer Section 80 Programmatic Interface
zTimer
Table 209. Visual Comparison of zTimer Function Block
N/A N/A
N/A
N/A
Comparison of Timer and zTimer Parameters

In a Harmony system, TIMER is an active data structure in the Batch90/UDF
programming language.
In INFI90FCLib, the related object is a zTimer Function Block.
504 3BUA000937R301
Section 80 Programmatic Interface zTimer
Configure a Timer
B90 Declaration for TIMER:
TIMER name (units)
Where:
name Name of an TIMER instance
Table 210. Comparison of B90 Declaration Data and zTimer FB Parameter
B90 Declaration Data zTimer Function Block Parameters

from and writes commands to a TIMER commands to the zTimer Function Block via a variable
using its name. In the sections below, it’s connected to the zTimer's zi parameter. In the sections
referred to as timername. below, this zi variable is referred to as ziVarName.
Units: Units of time (SEC=Seconds, Units: Unit of time. This is a constant parameter.
MIN=Minutes, HOUR=Hours) 0=seconds, 1=minutes, 2=hours.
N/A Val: Timer value
N/A Sts: Status of timer: False=holding, True=running
N/A Alm: Alarm Status: False=No alarm, True=Alarm
Reading Status data from a Timer
Table 211. Comparison of Reading Status Data in B90 and zTimer FB

Value = timername.VAL Value := ziVarName.Val ;
Value = timername.STS Value := ziVarName.Sts ;
Value = timername.ALM Value := ziVarName.Alm ;
Value = timername.LIM Value := ziVarName.AlmLim ;
3BUA000937R301 505
zBlockList Function Blocks Section 80 Programmatic Interface
Commands to a Timer
Table 212. Comparison of Writing Commands in B90 and zTimer FB

HOLD timername ziVarName.SetHold := True (or 1);
RESET timername (time) ziVarName.SetResetTim := time;
ziVarName.SetReset := True (or 1);
(Uses time from previous SetResetTim command)
START timername (value) ziVarName.SetAlmTim:=value;
ziVarName.SetStart :=True (or 1);
(Uses value from previous SetAlmTim commands)
zBlockList Function Blocks

Comparison of BLOCK ARRAY and zBlockList Function Blocks
In a Harmony system, BLOCK ARRAY is a function in the Batch90/UDF
programming language and supports multi-dimensional arrays. In INFI90FCLib,
the related object is a Function Block of type "zBlockList" and supports only one-
dimensional array.
Configuration of BLOCK ARRAY and zBlockList Function Blocks

B90 Declaration for BLOCK ARRAY:
{for one dimensional array}
type ARRAY name (low:high1) (list)
Where:
Type is anyone of the following:
AOL Analog output over the loop.
BBUF Boolean buffer.
506 3BUA000937R301
Section 80 Programmatic Interface Comparison of BLOCK ARRAY and zBlockList Function Blocks
CS Control station.
DATAEXPT Data export.
DD Device driver.
DOL Digital output over the loop.
MSDD Multi-state device driver.
RBUF Real buffer.
RCM Remote control memory.
REMSET Remote manual set constant.
RMC Remote motor control block.
TEXT Text selector.
name Name of the array
low Lowest subscript value must be 0 or 1.
For second and third dimensional arrays, the lowest subscript is
optional but must match the value from the first dimension.
HighN Highest subscript value for the Nth dimension. This must a constant.
The total number of elements in an array must not exceed 16K.
list List of array element names. This 1 dimensional list has one entry
for each element of the array. The order of entries is determined by
varying the 1st (leftmost) subscript the fastest, then the 2nd and 3rd.
Example:
In the following example, the names included in the list correspond to the names
assigned to function block declarations in the data section.
MSDD ARRAY BlockArrayName (1:4) (MSDD1, MSDD2, MSDD3, MSDD4).
BLOCK ARRAY supports multidimensional arrays whereas INFI90FCLib
supports only one dimensional array. In INFI90FCLib for each zBlock FB, a
zBlockList FB is created. Table 213 shows the zBlocks and their corresponding
zBlockLists in INFI90FCLib.
3BUA000937R301 507
Comparison of BLOCK ARRAY and zBlockList Function Blocks Section 80 Programmatic Interface
Table 213. zBlocks and Corresponding zBlockLists
zBlock FBs zBlockList FBs

zAOL (Derived from AOL) zlAOL
zAPID (Derived from APID) zlAPID
zStation (Derived from Station) zlStation
zDeviceDriver (Derived from DeviceDriver) zlDeviceDriver
zDOL (Derived from DOL) zlDOL
zFGen zlFGen
zInteg zlInteg
zMSDD (Derived from MSDD) zlMSDD
zRamp zlRamp
zRCM (Derived from RCM) zlRCM
zREMSET (Derived from REMSET) zlREMSET
zRMCB (Derived from RMCB) zlRMCB
zISC (Derived from ISC) zlISC
zTexSel (Derived from TexSel) zlTexSel
zTimer zlTimer
508 3BUA000937R301
Section 80 Programmatic Interface Comparison of BLOCK ARRAY and zBlockList Function Blocks
For illustration, one of the zBlockList FB (zlMSDD) is explained here:
Table 214. Comparison of B90 Declaration Data and zlMSDD Function Block Parameters
B90 Declaration Data zlMSDD Function Block Parameters

from and writes commands to a BLOCK commands to the zlMSDD Function Block via a variable
ARRAY using its name. In the sections connected to the zlMSDD's zi parameter. In the sections
below, it is referred as BlockArrayName below, this zi variable is referred to as ziVarName.
Low: Defines the lowest subscript value. N.A
Value must be 0 or 1.
High1: Highest subscript value. This There is no equivalent parameter. The number of
defines the total number of elements in extensible parameters present in the zlMSDD block
a one-dimensional array. defines the highest subscript value (total number of
elements in the list)
List: Indicates the list of array names. ziList: Indicates the list of zMSDD blocks connected to
This 1 dimensional list has one entry for all extensible parameters defined in the zlMSDD block.
each element (individual block) of the For example if multisize is 4, zMSDD blocks connected
array to ziList[1],ziList[2], ziList[3] and ziList[4] defines the list
of the blocks from which data can be read and
commands can be written to.
3BUA000937R301 509
Comparison of BLOCK ARRAY and zBlockList Function Blocks Section 80 Programmatic Interface
Reading Status data from BLOCK ARRAY and zBlockList Function Blocks
Table 215. Comparison of Reading Status Data in B90 and zlMSDD FB

Value=BlockArrayName (Value1). Ref ext When ziVarName.Index=1,
E.g. Value:= ziVarName.CO ; ( Reads the value of zi.CO
from zMSDD block connected to ziList[1] parameter),
Value=BlockArraryName(1).CO
When ziVarName.Index=2,
Value=BlockArraryName(2).CO
Value:= ziVarName.CO ; ( Reads the value of zi.CO
from zMSDD block connected to ziList[2] parameter)
Commands to a BLOCK ARRAY and zBlockList FBs
Table 216. Comparison of writing Commands in B90 and zlMSDD FB

SET BlockArraryName (Value1).ref ziVarName.Index:=1;
ext=Value ziVarName.SetCO:=3; (Set the value of zi.SetCO
E.g. SET BlockArraryName (1).CO=3 in zMSDD block connected to ziList[1]
parameter),
ziVarName.Index:=2;
ziVarName.SetCO:=3; (Set the value of zi.SetCO
in zMSDD block connected to ziList[2] parameter)
zlMSDD
Table 217. Visual Comparison of zlMSDD Function Block
N/A N/A
510 3BUA000937R301
Section 80 Programmatic Interface zVarList Function Blocks
Table 217. Visual Comparison of zlMSDD Function Block (Continued)
N/A
N/A
The functionality of all zBlockList FB's are same and they differ only in the data
types. For functionality of zBlockList FBs refer to zBlockList Function Blocks.
zVarList Function Blocks

Compare VAR ARRAY and zVarList Function Blocks
In a Harmony system, VAR ARRAY is a function in the Batch90/UDF
programming language and supports multi-dimensional arrays. In INFI90FCLib,
the related object is a Function Block of type "zVarList" and supports only one-
dimensional array.
Configuration of VAR ARRAY and zVarList Function Blocks

B90 Declaration for VAR ARRAY:
{for one dimensional array}
VAR ARRAY name (low:high1)
3BUA000937R301 511
Compare VAR ARRAY and zVarList Function Blocks Section 80 Programmatic Interface
Where:
name Name of the variable array
low Lowest subscript value must be 0 or 1. For second and third
dimensional arrays, the lowest subscript is optional but must match
the value from the first dimension.
HighN Highest subscript value for the Nth dimension. This must a constant.
The total number of elements in an array must not exceed 16K.
Example:
In the following example, the names included in the list correspond to the names
assigned to variable declarations in the data section.
VAR ARRAY VarList (1:4) (Real1, Real2, Real3, Real4).
VAR ARRAY supports multidimensional arrays whereas INFI90FCLib supports
only one dimensional array. In INFI90FCLib, four types of zVarlist FB's are
supported namely: zlReal, zlBool, zlDint and zlString.
For illustration, one of the zVarList FB (zlReal) is explained here:
Table 218. Comparison of B90 Declaration Data and zlReal Function Block Parameters
B90 Declaration Data zlReal Function Block Parameters

Name: User B90 code reads zi: User ST code reads status data from and writes
status data from and writes commands to the zlReal Function Block via a variable
commands to a VAR ARRAY connected to the zlReal's zi parameter. In the sections
using its name. In the sections below, this zi variable is referred to as ziVarName. In the
below, it is referred as VarName sections below, this zi variable is referred to as ziVarName.
Low: Defines the lowest subscript N.A
value. Value must be 0 or 1.
High1: Highest subscript value. There is no equivalent parameter. The number of extensible
This defines the total number of parameters present in the zlReal block defines the highest
elements in a one-dimensional subscript value.
array.
N.A ziList: Indicates the list of all real variables connected to all
extensible parameters defined in the zlReal block.
512 3BUA000937R301
Section 80 Programmatic Interface Compare VAR ARRAY and zVarList Function Blocks
Reading Status Data from VAR ARRAY and zVarList Function Blocks
Table 219. Comparison of Reading Status Data in B90 and zlReal FB

VarName (Value) When ziVarName.Index=1,
E.g. Value=VarName(1), Value:= ziVarName.Val ;
( Reads the value of real variable connected to ziList[1] parameter),
Value=VarName(5)
When ziVarName.Index=2,
Value:= ziVarName.Val ;
( Reads the value of real variable connected to ziList[2] parameter)
Commands to a VAR ARRAY and zBlockList Function Blocks

Table 220. Comparison of Writing Commands in B90 and zlReal FB

VarName(Value1)=Value ziVarName.Index:=1;
E.g. VarName(1)=3, ziVarName.SetVal:=3;
(Set the value of real variable connected to extensible parameter
VarName(5)=3
ziList[1] to 3),
ziVarName.Index:=2;
ziVarName.SetVal:=3;
(Set the value of real variable connected to extensible parameter
ziList[2] to 3)
zlReal
Table 221. Visual Comparison of zlReal Function Block
N/A N/A
3BUA000937R301 513
Compare VAR ARRAY and zVarList Function Blocks Section 80 Programmatic Interface
Table 221. Visual Comparison of zlReal Function Block (Continued)
N/A
N/A
The functionality of all zVarList FB's (zlReal, zlBool,zlDint and zlString) are
same and they differ only in the data types. For functionality of zVarList FB's
refer to zBlockList and zVarList FBs.
514 3BUA000937R301
Section 81 Mapped Function Codes in 800xA
Standard Library
The following Function Blocks identifies the INFI90 function codes that have
similar functionality within the standard AC 800M libraries. These are not part of
INFI90FCLib.
Summer (4-Input)-FC14
The equivalent Block for summer (2-Input) and summer (4-Input) in 800xA system
library is add.
Table 222. Visual Comparison of Summer (4-Input)-FC14 Function Block
N/A
3BUA000937R301 515
Comparison of Summer (4-Input) Parameters Section 81 Mapped Function Codes in 800xA
Table 222. Visual Comparison of Summer (4-Input)-FC14 Function Block

Comparison of Summer (4-Input) Parameters

Table 223. Summer (4-Input) Parameters
Specifications As Parameters As in
Spec Type Comment
in Harmony 800xA System Library
S1 In1 Input
S2 In2 Input
S3 In3 Input
S4 In4 Input
N Out
Additional Parameters in System Library

This Function Block has no Additional parameters.
516 3BUA000937R301
Section 81 Mapped Function Codes in 800xA Standard Library Parameters Not in System Library
Parameters Not in System Library

This Function Block has all the parameters of Harmony Function code 14.
14, summer (4-Input). The Number of input pins can be extended up to 19.
AND (4-Input)-FC38
The equivalent Block for AND (2-Input) and AND (4-Input) in 800xA system
library is and.
Table 224. Visual Comparison of AND (4-Input)-FC38 Function Block
N/A
3BUA000937R301 517
Comparison of AND (4-Input) Parameters Section 81 Mapped Function Codes in 800xA Standard
Table 224. Visual Comparison of AND (4-Input)-FC38 Function Block
Comparison of AND (4-Input) Parameters

Table 225. AND (4-Input) Parameters
Parameters As in
Specifications As Spec
800xA System Comment
in Harmony Type
Library
S1 In1 Input
S2 In2 Input
S3 In3 Input
S4 In4 Input
N Out

518 3BUA000937R301

38, AND (4-Input). The Number of input pins can be extended up to 19.
OR (4-Input)-FC40
The equivalent Block for OR (4-Input) in 800xA system library is or.
Table 226. Visual Comparison of OR (4-Input) Function Block
N/A
3BUA000937R301 519
Comparison of OR (4-Input) Parameters Section 81 Mapped Function Codes in 800xA Standard
Table 226. Visual Comparison of OR (4-Input) Function Block

Comparison of OR (4-Input) Parameters

Table 227. OR (4-Input) Parameters
Parameters As in
Harmony Type Of
800xA System Comment
Specifications Spec
Library
S1 In1 Input
S2 In2 Input
S3 In3 Input
S4 In4 Input
N Out

520 3BUA000937R301

40, OR (4-Input). The Number of input pins can be extended up to 19.
Exclusive OR-FC101
The equivalent Block for Exclusive OR in 800xA system library is xor.
Table 228. Visual Comparison of Exclusive OR Function Block
N/A
View in Composer
View in Composer
N/A
N/A
3BUA000937R301 521
Comparison of Exclusive OR Parameters Section 81 Mapped Function Codes in 800xA Standard
Comparison of Exclusive OR Parameters

Table 229. Exclusive OR (Parameters)
Parameters As in
Harmony
800xA System Spec Type Comment
Specifications
Library
S1 In1 Input
S2 In2 Input
N Out


This Function Block has all the parameters of Harmony Function code101.
101, Exclusive OR.
522 3BUA000937R301
Section 81 Mapped Function Codes in 800xA Standard Library NOT-FC33
NOT-FC33
The equivalent Block for NOT in 800xA system library is not.
Table 230. Visual Comparison of Exclusive OR Function Block
N/A
N/A
N/A

3BUA000937R301 523
Comparison of NOT Parameters Section 81 Mapped Function Codes in 800xA Standard Library
Comparison of NOT Parameters

Table 231. NOT Parameters
Parameters As in
Harmony
800xA System Spec Type Comment
Specifications
Library
In Input S1
Out N


This Function Block has all the parameters of Harmony Function code33.
33, NOT.
524 3BUA000937R301
Section 81 Mapped Function Codes in 800xA Standard Library Manual Set Constant-FC02
Manual Set Constant-FC02

Table 232. Visual Comparison of Manual Set Constant -FC02 Function Block

Note1 Note1
Note1: Refer Figure 49 and Figure 50
Comparison of Manual Set Constant Parameters

N/A
In Control Builder (Function designer), this functionality can be achieved by
declaring a Variable of Data type Real with retain attribute. Assign values to this
variable, as shown in Figure 49.
3BUA000937R301 525
Differences in Functionality Section 81 Mapped Function Codes in 800xA Standard Library
Figure 49. Differences in Functionality 1
Define a variable with name 'TrackRef' and connect this to TR parameter pin, TR
will take value assigned to variable 'Trackref'.
The same variable can be connected to two or more Function Blocks as shown in
Figure 50.
526 3BUA000937R301
Section 81 Mapped Function Codes in 800xA Standard Library Manual Set Integer -FC52
Manual Set Integer -FC52

Table 233. Visual Comparison of Manual Set Integer -FC52 Function Block
View in Composer
View in Composer
Note 2 Note 2
Note 2: Refer Figure 51 and Figure 52
Comparison of Manual Set Integer Parameters

N/A
declaring a Variable of Data type Integer with retain attribute. Assign values to this
3BUA000937R301 527
Define a variable with name 'Input' and connect the variable to In1 parameter pin.
In1 has the value assigned to variable 'Input'.
Figure 52.
528 3BUA000937R301
Section 81 Mapped Function Codes in 800xA Standard Library Manual Set Constant -FC51
Manual Set Constant -FC51

Table 234. Visual Comparison of Manual Set Constant -FC51 Function Block

Note 3 Note 3

N/A
In Control BuilderM (Function Designer), this functionality can be achieved by
declaring a Variable of Data type real with coldretain attribute and initial value. By
declaring the variable value (for example, 10.0) as the port input and initial value
during the build, the variable can not be tuned on-line. Assign values to this
3BUA000937R301 529
Define a variable with name 'Input' and connect this variable to In1 parameter pin,
In1 will take value assigned to variable 'Input'.
Figure 54.
530 3BUA000937R301
Section 81 Mapped Function Codes in 800xA Standard Library Manual Set Switch-FC50
Manual Set Switch-FC50

Table 235. Visual Comparison of Manual Set Switch -FC50 Function Block

Note 4 Note 4

N/A
declaring a Variable of Data type Boolean with retain attribute. Change the state of
this variable, as shown in Figure 55. Define a variable with name 'Trackswitch' and
connect this to TS parameter pin. TS will change the state as per variable
'Trackswitch''.
3BUA000937R301 531
Figure 55. Difference in Functionality 1
Figure 56.
Figure 56. Difference in Functionality 2
532 3BUA000937R301
Appendix A List of Function Blocks
Introduction
Appendix A contains cross references for all the Function Blocks.
Table 236 is an alphabetical listing of the Function Blocks by Function Block name
and is followed by the function code number and description.
Cross Reference - Alphabetical Listing

Table 236. Alphabetical Listing
Function Block Name Function Code Number Description

AOL 30 Analog Exception Report
APID 156 Advanced PID Controller
BasicStation 21 Basic Station
BLINK 61 Blink
DAANG 177 Data Acquisition Analog
DADIG 211 Data Acquisition Digital
DelayReal 58 Time Delay
DeltaPID 19 PID (PV & SP)
DeviceDriver 123 Device Driver
DevMon 125 Device Monitor
DMuxReal 126 Real Signal De-Multiplexer
DOL 45 Digital Exception Report
DSum 65 Digital Sum with Gain
ElapTimer 86 Elapsed Timer
ErrPID 18 PID Error Input
3BUA000937R301 533
Cross Reference - Alphabetical Listing Appendix A List of Function Blocks
Table 236. Alphabetical Listing (Continued)

Exec 81 Executive
ExExec 90 Extended Executive
EXP1 172 Exponential
FnGen 1 Function Generator
HiLowComp 12 High / Low Compare
INPOL 168 Interpolator
Integrator 166 Integrator
ISC 160 Inferential Smith Controller
JumpMCR 116 Jump/Master Control Relay
LeadLag 3 Lead / Lag
LOG1 174 Logarithm
MODST 95 Module Status
MovAvg 165 Moving Average
MSDD 129 Multi-State Device Driver
MULTIMON 134 Multi Sequence Monitor
MuxBool 119 Boolean Signal Multiplexer
MuxReal 120 Real Signal Multiplexer
POLY 167 Polynomial
POWER 173 Power
PulsePosn 4 Pulse Positioner
PulseRate 5 Pulse Rate
QOR 36 Qualified OR
RateLimiter 8 Rate Limiter
RCM 62 Remote Control Memory
RecipeBool 117 Bool Recipe Table
RecipeReal 118 Real Recipe Table
RedAI 96 Redundant Analog Input
RedDI 97 Redundant Digital Input
REMSET 68 Remote Manual Set Constant
RMCB 136 Remote Motor Control Block
534 3BUA000937R301
Appendix A List of Function Blocks Cross Reference - Alphabetical Listing
Table 236. Alphabetical Listing (Continued)

Rung10 111 Rung10
Rung20 112 Rung20
Rung5 110 Rung5
SeqGen 161 Sequence Generator
SEQMGR 135 Sequence Manager
SeqMon 124 Sequence Monitor
SeqMstrSlv 141/142 Sequence Master Slave
SLSEL 98 Slave Select
Sqroot 7 Square Root
SRMem 34 S/R Memory
Station 80 Control Station
Sum2Real 15 Summer 2-Input
TexSel 151 Text Selector
TimerBool 35 Timer
TRIG 171 Trigonometric
TRIP 32 Trip
TSTALM 69 Test Alarm
TSTQ 31 Test Quality
UpDnCount 85 Up/Down Counter
XferBool 59 Digital Transfer
XferDint 13 Integer Transfer
XferReal 9 Analog Transfer
3BUA000937R301 535
Cross Reference - Alphabetical Listing Appendix A List of Function Blocks
536 3BUA000937R301
Appendix B Alarm Priority Severity Mapping
Introduction
Table 237 provides information regarding the alarm priority severity mapping.
Table 237. Alarm Prority Severity Mapping
Harmony Alarm Priority 800XA Severity 800XA Priority Level

1 1000 1
2 900 2
3 850 3
4 800 4
5 700 5
6 650 6
7 600 7
8 550 8
9 450 9
10 400 10
11 350 11
12 300 12
13 200 13
14 150 14
15 100 15
3BUA000937R301 537
Introduction Appendix B Alarm Priority Severity Mapping
Table 237. Alarm Prority Severity Mapping (Continued)
Harmony Alarm Priority 800XA Severity 800XA Priority Level

16 1 16
0 1 16
538 3BUA000937R301
INDEX
Numerics E
800xA Base Platform 29 ElapTimer 83, 91, 97
800xA System 29 ErrPID 173
Exclusive OR-FC101 521
A Exec 277
Alarm Handling 437 Execution Order 62
Analog Output 443 ExExec 281
AND (4-Input)-FC38 517 Exponential 291
AOL 205
APID 225 F
Aspect Object 30 FnGen 111
Function Designer 41
B Function Generator 75, 77, 79, 81
Basic Station 399 Functional Structure 35
Blink 299
G
C General 29
Common Analog Properties 48
Common Digital Properties 52 H
Common Properties 43 HiLowComp 171
Control Builder 39
Control Structure 36, 37 I
Cross Reference - Alphabetical 533 INPOL 101
Integrator 115
D Introduction to Engineering Tools 39
DAANG 239 ISC 273
DADIG 267
DelayReal 107 J
DeltaPID 177 JumpMCR 359
Device Driver 69
Device Monitor 285 L
DmuxReal 151 LeadLag 141
DOL 199 Library Structure 37
DSum 123 List of Function Blocks 533, 537
3BUA000937R301 539
Index
Location Structure 37 ReceipeReal 165

Logarithm 293 RecipeBool 307
LoopAMC 171 RedAI 301
RedDI 305
M REMSET 189
Maintenance Structure 38 RMCB 259
Manual Set Constant-FC02 525 Rung10 317
Manual Set Integer -FC52 527 Rung20 323
Manual Set Switch -FC50 531 Rung5 313
Mapped Function Codes 515
Module Status 365 S
MovAvg 119 Sequence Generator 415
MSDD 229 Sequence Manager 353
Multi Sequence Monitor 385 Sequence Master Slave 335
MuxBool 159 Sequence Monitor 343
MuxReal 145 Service Structure 38
Slave Select 361
N Specification Handling 57
NOT-FC33 523 Specification Range Validity Check 61
SqRoot 127
O SRMem 185
Object Type Structure 38 Station 209
OPC Error Indication 63 String Handling 65
OR (4-Input)-FC40 519 Structures 33
Sum2Real 143
Summer (4-Input)-FC14 515
P
Polynomial 329
Power 297 T
Pulse Positioner 423 Text Selector 393
PulseRate 429 TimerBool 133
Trigonometric 295
Trip 351
Q
TSTALM 237
QOR 181
TSTQ 187
Quality Propagation 64
U
R
UpDnCount 135
Rate Limiter-FC08 532
User Structure 34
RateLimiter 433
RCM 193
540 3BUA000937R301
Index
W
Workplace Structure 34
X
XferBool 131
XferDint 129
XferReal 139
3BUA000937R301 541
Index
542 3BUA000937R301
ABB AB
Control Systems
Västerås, Sweden
Phone: +46 (0) 21 32 50 00
Fax: +46 (0) 21 13 78 45
E-Mail processautomation@se.abb.com
www.abb.com/controlsystems
ABB Inc.
Control Systems
Wickliffe, Ohio, USA
Phone: +1 440 585 8500
Fax: +1 440 585 8756
E-Mail industrialitsolutions@us.abb.com
ABB Industry Pte Ltd

Control Systems
Singapore
Phone: +65 6776 5711
Fax: +65 6778 0222
E-Mail: processautomation@sg.abb.com
ABB Automation GmbH

Control Systems
Mannheim, Germany
Phone: +49 1805 26 67 76
Fax: +49 1805 77 63 29
E-Mail marketing.control-products@de.abb.com
www.abb.de/controlsystems
3BUA000937R301
Copyright © 2003-2013 by ABB. All Rights Reserved.
Power and productivity

for a better world TM

INFI 90 Function Block Library For AC 800M

Uploaded by

Copyright:

Available Formats

INFI 90 Function Block Library For AC 800M

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

INFI 90 Function Block Library For AC 800M

Uploaded by

Copyright:

Available Formats

INFI 90 Function Block Library for AC 800M

Function Block Evolution Guide

Function Block Evolution Guide

Copyright © 2003-2013 by ABB.

Release: July 2013

About This Book

Maintenance Structure ........................................................................ 38

Section 2 - Introduction to Engineering Tools

Section 3 - Common Parameters

Section 4 - Design Differences

Section 5 - Device Driver

Differences in Graphical Interfaces............................................................................... 105

Comparison of SqRoot Parameters ...............................................................................128

Differences in Functionality ..........................................................................................161

Differences in Functionality ..........................................................................................208

Section 52 - Device Monitor

Comparison of Object View ..........................................................................................293

Differences in Functionality ..........................................................................................339

Comparison of Object View .......................................................................................... 365

Section 76 - Pulse Positioner

Section 79 - Alarm and Event Handling

Section 80 - Programmatic Interface

Comparison of Object View.............................................................. 457

Comparison of Object View .............................................................495

Section 81 - Mapped Function Codes in 800xA Standard Library

AND (4-Input)-FC38 .................................................................................................... 517

Manual Set Constant -FC51 ..........................................................................................529

Appendix A - List of Function Blocks

Appendix B - Alarm Priority Severity Mapping

Warning, Caution, Information, and Tip Icons

Caution icon indicates important information or warning related to the concept

Information icon alerts the reader to pertinent facts and conditions.

800xA Base Platform

Figure 1. 800xA System Software Architecture

Controllers are connected to the system through connectivity components, which

The architecture of Aspect Objects is a base of the System 800xA concept. It

Project Workflow Activities in 800xA System

Table 1. Overall Project Workflow Activities

Table 1. Overall Project Workflow Activities (Continued)

Structures in 800xA System

Figure 2. Structures in Engineering Workplace

Same object can be seen in different structures.

The following are the commonly used structures:

Structures Used for Administration in 800xA System

Figure 3. User Structure

Figure 4. Workplace Structure

Structures Used for Application Engineering in 800xA System

Figure 5. Functional Structure

Figure 6. Control Structure

Other Support Structures in 800xA System

Object Type Structure

Figure 7. Typical View of Control Builder

Figure 8. From Sensor to Valve Loop

Table 2. Common Properties

Harmony Connect Console Parameters as in Type

Table 2. Common Properties (Continued)

Harmony Connect Console Parameters as in Type

Table 2. Common Properties (Continued)

Harmony Connect Console Parameters as in Type