Ovation Functions Guide

Ovation Algorithms Reference Manual
OW351_R1100
(For use with Ovation 3.5.1 systems)

January 2018
Version 5
Copyright Notice
Since the equipment explained in this document has a variety of uses, the user and those
responsible for applying this equipment must satisfy themselves as to the acceptability of each
application and use of the equipment. Under no circumstances will Emerson Process
Management be responsible or liable for any damage, including indirect or consequential losses
resulting from the use, misuse, or application of this equipment.
The text, illustrations, charts, and examples included in this manual are intended solely to explain
the use and application of the OvationTM Unit. Due to the many variables associated with specific
uses or applications, Emerson Process Management cannot assume responsibility or liability for
actual use based upon the data provided in this manual.
No patent liability is assumed by Emerson Process Management with respect to the use of
circuits, information, equipment, or software described in this manual.
No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any
form or by any means, including electronic, mechanical, photocopying, recording or otherwise
without the prior express written permission of Emerson Process Management.
The document is the property of and contains Proprietary Information owned by Emerson Process
Management and/or its subcontractors and suppliers. It is transmitted in confidence and trust, and
the user agrees to treat this document in strict accordance with the terms and conditions of the
agreement under which it was provided.
This manual is printed in the USA and is subject to change without notice.
Ovation is the mark of Emerson Process Management. Other marks are the property of their
respective holders.
Copyright © Emerson Process Management Power & Water Solutions, Inc. All rights reserved.
Emerson Process Management
Power & Water Solutions
200 Beta Drive
Pittsburgh, PA 15238
USA
E-Mail: Technical.Communications@EmersonP rocess.com

Web site: https://www.ovationusers.com
Summary of Changes
Ovation Algorithms Reference Manual (for use with Ovation 3.5.1 systems)
OW351_R1100
Version 5
January 2018
This version of Ovation Algorithms Reference Manual contains the following new information:
 Updated the information regarding the parameters of the PID algorithm (see page 372).
 Made miscellaneous corrections and clarifications.
Contents
1 Introduction to Ovation Q-Line and Specialty algorithms 1

1.1 What are algorit hms? .................................................................................................. 1
2 General algorithm user information 3

2.1 What is hardware addressing for algorithms? ............................................................... 3
2.1.1 To determine an algorithm hardware address ................................................... 3
2.2 What is propagated point quality? ................................................................................ 4
2.3 Algorithm status and mode settings.............................................................................. 4
2.4 What is invalid number checking and quality checking for algorithms? ............................ 5
2.5 What are single precision floating point numbers? ......................................................... 6
2.6 What is the error information generated by algorithms ? ................................................. 6
2.7 Binary to hexadecimal conversion for algorithms ........................................................... 6
3 Understanding tracking 9
3.1 What is tracking? ........................................................................................................ 9
3.2 What is the purpose of tracking? ................................................................................ 10
3.3 What is the tracking process? .................................................................................... 11
3.4 What are the best practices for using tracking? ........................................................... 11
3.5 What algorithms support tracking? ............................................................................. 12
3.6 Tracking examples .................................................................................................... 14
3.7 Setting tracking signals for algorithms ........................................................................ 15
4 Algorithm classifications 19
4.1 What are algorit hm classification groups? ................................................................... 20
4.2 Alarm Manipulation algorithms ................................................................................... 21
4.3 Artificial I/O algorithms (signal generators) .................................................................. 21
4.4 Boolean Logic algorithms .......................................................................................... 22
4.5 Boolean Logic Memory algorithms ............................................................................. 22
4.6 Custom Calculation algorithms .................................................................................. 23
4.7 Device Control algorithms ......................................................................................... 23
4.8 Fieldbus algorithms ................................................................................................... 24
4.9 Filtering algorithms ................................................................................................... 25
4.10 Hardware Interface algorithms ................................................................................... 26
4.11 Link Controller Module Interface algorit hms ................................................................ 27
4.12 Loop Interface Module algorithms .............................................................................. 28
4.13 Mathematical and Statistical algorit hms ...................................................................... 29
4.14 Modulating Cont rol algorithms ................................................................................... 30
OW351_R1100 i
Table of Contents
4.15 Monitor Function algorithms ...................................................................................... 31

4.16 Operator Int erface algorithms .................................................................................... 32
4.17 Point Format Conversion algorithms .......................................................................... 33
4.18 Pulse Accumulator Module Interface algorithms .......................................................... 34
4.19 Q-Line Interface algorithms ....................................................................................... 35
4.20 Redundant Signal Processing algorithms ................................................................... 36
4.21 Sequential Logic algorithms ....................................................................................... 37
4.22 Signal Compensation algorithms ................................................................................ 38
4.23 System Diagnostic algorithms .................................................................................... 39
4.24 System Time Function algorithms .............................................................................. 39
4.25 Time/Counter Function algorithms ............................................................................. 40
4.26 Tracking algorithms................................................................................................... 41
4.27 Turbine Interface algorithms ...................................................................................... 42
5 Standard algorithm reference pages 43

5.1 Understanding algorithm descriptions......................................................................... 46
5.1.1 Algorithm functional symbols ......................................................................... 47
5.2 AAFLIPFLOP ........................................................................................................... 48
5.3 ABSVALUE .............................................................................................................. 50
5.4 ALARMLIMIT............................................................................................................ 51
5.5 ALARMMON ............................................................................................................ 56
5.6 ANALOG DEVICE (A DEVICE)................................................................................... 58
5.7 ANALOGDRUM ........................................................................................................ 61
5.8 AND......................................................................................................................... 65
5.9 ANNUNCIA TOR ....................................................................................................... 66
5.10 ANTILOG ................................................................................................................. 69
5.11 ARCCOS INE ............................................................................................................ 71
5.12 ARCS INE ................................................................................................................. 72
5.13 ARCTA NGE NT......................................................................................................... 73
5.14 ASSIGN ................................................................................................................... 74
5.15 ATREND .................................................................................................................. 75
5.16 AVALGEN ................................................................................................................ 77
5.17 BALANCE R.............................................................................................................. 78
5.18 BCDNIN ................................................................................................................... 83
5.19 BCDNOUT ............................................................................................................... 85
5.20 BILLFLOW ............................................................................................................... 87
5.21 BUFFER .................................................................................................................. 89
5.22 CALCBLOCK ......................................................................................................... 103
5.23 CALCBLOCKD ....................................................................................................... 112
5.24 COMPA RE ............................................................................................................. 118
5.25 COS INE ................................................................................................................. 119
5.26 COUNTE R ............................................................................................................. 120
5.27 DBEQUA LS ........................................................................................................... 122
5.28 DEVICE ................................................................................................................. 124
ii OW351_R1100
Table of Contents
5.29 DEVICESEQ .......................................................................................................... 144

5.30 DEVICE X ............................................................................................................... 148
5.31 DFIE LD .................................................................................................................. 167
5.32 DIGCOUNT ............................................................................................................ 168
5.33 DIGDRUM .............................................................................................................. 169
5.34 DIGITA L DEV ICE ................................................................................................... 174
5.34.1 SAMPLER (Cont rolled Sampler) .................................................................. 175
5.34.2 VALVE NC (Non-Controlled Valve) .............................................................. 177
5.34.3 MOTOR NC (Non-Controlled Motor) ............................................................ 178
5.34.4 MOTOR (Simple Controlled Motor) .............................................................. 180
5.34.5 MOTOR 2-SP D (Two Speed or Bi-Directional Controlled Motor) .................... 183
5.34.6 MOTOR 4-SP D (Two Speed and Bi-Directional Cont rolled Motor).................. 187
5.34.7 VALVE (Controlled Valve) ........................................................................... 192
5.35 DIS TRIBUTOR ....................................................................................................... 195
5.35.1 Input, FNUM parameter, and Output pins (IN, FNUM, and O UT[1-8]) ............. 195
5.35.2 Exclusion (E XCL) ....................................................................................... 196
5.35.3 Tracking Inputs (TK IN[1-8]) ......................................................................... 198
5.35.4 Correction Gain .......................................................................................... 199
5.35.5 Priority Deadband (PDB ) ............................................................................. 200
5.35.6 Base Gain .................................................................................................. 201
5.35.7 Tracking Out (TOUT) .................................................................................. 202
5.35.8 Internal and External Control ....................................................................... 203
5.35.9 Switching Between Internal and External Inputs ............................................ 204
5.35.10 First Pass Startup Options ........................................................................... 205
5.35.11 Point Quality ............................................................................................... 206
5.35.12 SID Storage ............................................................................................... 206
5.35.13 Distributor Algorithm Definitions ................................................................... 206
5.36 DIV IDE................................................................................................................... 215
5.37 DROPS TA TUS ....................................................................................................... 218
5.38 DRP I1A .................................................................................................................. 221
5.39 DVALGE N.............................................................................................................. 223
5.40 DXCS TA TUS ......................................................................................................... 224
5.40.1 DXCS TA TUS tuning parameters and site ratings .......................................... 243
5.40.2 DXCS TA TUS functions ............................................................................... 245
5.40.3 DXCS TA TUS state ..................................................................................... 247
5.41 FACEPLA TE .......................................................................................................... 249
5.41.1 FACEPLA TE -- DIGITAL DEV ICE template .................................................. 252
5.41.2 FACEPLA TE -- MAS TA TION template ......................................................... 256
5.42 FIELD .................................................................................................................... 257
5.43 FIFO ...................................................................................................................... 259
5.44 FIRS TOUT ............................................................................................................. 262
5.45 FLIPFLOP .............................................................................................................. 267
5.46 FUNCTION ............................................................................................................ 269
5.47 GAINBIAS .............................................................................................................. 273
5.48 GASFLOW ............................................................................................................. 277
5.49 HEARTBEA T.......................................................................................................... 284
5.50 HIGHLOWMON ...................................................................................................... 287
5.51 HIGHMON.............................................................................................................. 288
5.52 HISE LECT ............................................................................................................. 290
5.53 HSCLTP ................................................................................................................ 295
OW351_R1100 iii
Table of Contents
5.54 HSLT ..................................................................................................................... 296

5.55 HS TVSVP .............................................................................................................. 297
5.56 HSVSSTP .............................................................................................................. 298
5.57 INTE RP ................................................................................................................. 299
5.58 KEYBOARD ........................................................................................................... 303
5.59 LATCHQUAL.......................................................................................................... 306
5.60 LEADLA G .............................................................................................................. 308
5.61 LEVELCOMP ......................................................................................................... 312
5.62 LOG....................................................................................................................... 316
5.63 LOSELE CT ............................................................................................................ 317
5.64 LOWMON .............................................................................................................. 322
5.65 MAMODE ............................................................................................................... 323
5.66 MASTA TION .......................................................................................................... 325
5.67 MASTE RSEQ......................................................................................................... 335
5.68 MEDIA NSEL .......................................................................................................... 348
5.69 MULTIPLY ............................................................................................................. 356
5.70 NLOG .................................................................................................................... 359
5.71 NOT....................................................................................................................... 360
5.72 OFFDE LAY ............................................................................................................ 361
5.73 ONDELAY .............................................................................................................. 363
5.74 ONESHOT ............................................................................................................. 366
5.75 OR......................................................................................................................... 369
5.76 PACK16 ................................................................................................................. 370
5.77 PID ........................................................................................................................ 372
5.78 PIDFF .................................................................................................................... 389
5.79 PNTS TA TUS .......................................................................................................... 402
5.80 POLYNOMIA L ........................................................................................................ 404
5.81 PREDICTOR .......................................................................................................... 406
5.82 PRIORITY Algorithm Package ................................................................................. 410
5.82.1 PRIORITY .................................................................................................. 411
5.82.2 PRIORITY-E XT .......................................................................................... 428
5.82.3 PRIORITY-RE J .......................................................................................... 432
5.83 PSLT ..................................................................................................................... 435
5.84 PSVS..................................................................................................................... 436
5.85 PULSECNT ............................................................................................................ 437
5.86 QAVERAGE ........................................................................................................... 438
5.87 QUALITYMON........................................................................................................ 439
5.88 RAMPGEN ............................................................................................................. 440
5.89 RA TECHANGE ...................................................................................................... 444
5.90 RA TELIMIT ............................................................................................................ 446
5.91 RA TEMON ............................................................................................................. 449
5.92 RESETS UM ........................................................................................................... 451
5.93 RLICONFIG ........................................................................................................... 454
5.94 RPACNT ................................................................................................................ 457
5.95 RPAWIDTH ............................................................................................................ 458
iv OW351_R1100
Table of Contents
5.96 RSRS TA TUS ......................................................................................................... 459

5.97 RUNAVERA GE ...................................................................................................... 469
5.98 RUNTIME .............................................................................................................. 471
5.99 RVPSTA TUS .......................................................................................................... 476
5.100 SATOSP ................................................................................................................ 479
5.101 SELECTOR............................................................................................................ 480
5.102 SETPOINT ............................................................................................................. 482
5.103 SIMTIME ................................................................................................................ 485
5.104 SINE ...................................................................................................................... 485
5.105 SLCA IN.................................................................................................................. 486
5.106 SLCAOUT .............................................................................................................. 489
5.107 SLCDIN ................................................................................................................. 492
5.108 SLCDOUT.............................................................................................................. 495
5.109 SLCP IN.................................................................................................................. 498
5.110 SLCPOUT .............................................................................................................. 501
5.111 SLCS TA TUS .......................................................................................................... 504
5.112 SMOOTH ............................................................................................................... 508
5.113 SOFTSOE .............................................................................................................. 510
5.114 SPTOSA ................................................................................................................ 520
5.115 SQUAREFOOT ...................................................................................................... 521
5.116 SSLT ..................................................................................................................... 524
5.117 STA TIS TICS .......................................................................................................... 525
5.118 STEAMFLOW......................................................................................................... 542
5.119 STEAMTABLE ........................................................................................................ 544
5.120 STEP TIME ............................................................................................................. 547
5.121 SUM ...................................................................................................................... 552
5.122 SYSTEMTIME ........................................................................................................ 556
5.123 TA NGE NT.............................................................................................................. 557
5.124 TIMECHA NGE ....................................................................................................... 558
5.125 TIMEDE TE CT ........................................................................................................ 559
5.126 TIMEMON .............................................................................................................. 560
5.127 TRANSFE R............................................................................................................ 563
5.128 TRANS LA TOR ....................................................................................................... 571
5.129 TRANSPORT ......................................................................................................... 575
5.130 TRNSFINDX........................................................................................................... 577
5.131 TRUTHTB L ............................................................................................................ 578
5.132 TSLH ..................................................................................................................... 582
5.133 TSLP ..................................................................................................................... 583
5.134 UNPA CK16 ............................................................................................................ 584
5.135 VCLTP ................................................................................................................... 586
5.136 VSLT ..................................................................................................................... 587
5.137 XOR ...................................................................................................................... 588
5.138 X3S TEP ................................................................................................................. 589
5.139 2XSE LECT............................................................................................................. 599
OW351_R1100 v
Table of Contents
6 Q-Line algorithms 607

6.1 What are Q-Line algorithms ? ................................................................................... 608
6.2 PVSPSLI................................................................................................................ 609
6.3 PWDIN................................................................................................................... 612
6.4 QLIPASS ............................................................................................................... 615
6.5 QPACMD ............................................................................................................... 619
6.6 QPACMPAR........................................................................................................... 625
6.7 QPASTA T .............................................................................................................. 626
6.8 QSDDEMAND ........................................................................................................ 627
6.9 QSDMODE ............................................................................................................ 629
6.10 QSRMA ................................................................................................................. 630
6.11 QVP....................................................................................................................... 636
6.12 XFLOW .................................................................................................................. 639
6.13 XMA2..................................................................................................................... 645
6.14 XML2 ..................................................................................................................... 656
6.15 XP IDSLI ................................................................................................................. 661
7 Foundation Fieldbus algorithms 675

7.1 What are Foundation Fieldbus algorithms? ............................................................... 675
7.2 Ovation Fieldbus algorit hms and function blocks ....................................................... 676
7.2.1 STA T bits used with function blocks ............................................................. 677
7.3 FFAI ...................................................................................................................... 678
7.4 FFAO..................................................................................................................... 681
7.5 FFDI ...................................................................................................................... 684
7.6 FFDO..................................................................................................................... 687
7.7 FFISEL/FFISELX .................................................................................................... 690
7.8 FFMAI.................................................................................................................... 698
7.9 FFMAO .................................................................................................................. 702
7.10 FFMDI ................................................................................................................... 704
7.11 FFMDO .................................................................................................................. 708
7.12 FFPID .................................................................................................................... 712
8 Understanding the Ovation SIS algorithms 717

8.1 What are Ovation SIS Logic Solver algorit hms? ........................................................ 718
8.1.1 SIS algorithm types ..................................................................................... 720
8.2 LSAI ...................................................................................................................... 721
8.3 LSALM................................................................................................................... 723
8.4 LSAND................................................................................................................... 725
8.5 LSAVTR................................................................................................................. 727
8.6 LSBDE ................................................................................................................... 744
8.7 LSBFI .................................................................................................................... 746
8.8 LSBFO................................................................................................................... 749
vi OW351_R1100
Table of Contents
8.9 LSCALC................................................................................................................. 752

8.9.1 LSCALC Expression Editor.......................................................................... 757
8.10 LSCEM .................................................................................................................. 767
8.11 LSCMP .................................................................................................................. 790
8.12 LSDI ...................................................................................................................... 792
8.13 LSDO..................................................................................................................... 794
8.14 LSDVC................................................................................................................... 801
8.15 LSDV TR ................................................................................................................ 812
8.16 LSLIM .................................................................................................................... 829
8.17 LSMID ................................................................................................................... 832
8.18 LSNAND ................................................................................................................ 836
8.19 LSNDE................................................................................................................... 838
8.20 LSNOR .................................................................................................................. 840
8.21 LSNOT................................................................................................................... 842
8.22 LSOFFD ................................................................................................................ 843
8.23 LSOND .................................................................................................................. 845
8.24 LSOR..................................................................................................................... 847
8.25 LSPDE ................................................................................................................... 849
8.26 LSRE T ................................................................................................................... 851
8.27 LSRS ..................................................................................................................... 853
8.28 LSSEQ................................................................................................................... 855
8.29 LSSR ..................................................................................................................... 860
8.30 LSSTD ................................................................................................................... 862
8.31 LSTP ..................................................................................................................... 869
8.32 LS XNOR ................................................................................................................ 871
8.33 LS XOR .................................................................................................................. 872
8.34 SIS connector algorithm table .................................................................................. 873
8.35 GSECPARAMREF .................................................................................................. 874
8.36 NONSECPA RAM ................................................................................................... 875
8.37 SECPARAM ........................................................................................................... 876
8.38 SECPARAMREF .................................................................................................... 878
9 Migrated special functions 879

9.1 What are migrated special functions? ....................................................................... 879
9.2 WDPF to Ovation reference table............................................................................. 880
9.3 WDPF special functions to Ovation algorit hms .......................................................... 888
9.4 What are migration algorithms? ............................................................................... 893
9.4.1 MODE TRANS ............................................................................................ 894
9.4.2 SETS TA TES .............................................................................................. 895
Index 897
OW351_R1100 vii
SECTION 1
1 Introduction to Ovation Q-Line and Specialty

algorithms
IN THIS SECTION
What are algorit hms? .................................................................................................. 1
1.1 What are algorithms?
Algorithms are mathematical formulas that define a specific control strategy. An algorithm may be
thought of as a collection of system points that are controlled by the algorithm. The algorithm
reads values (inputs) and writes values (outputs) into points to accomplish certain des ired actions
in the system. (Refer, Ovation Record Types Reference Manual for information about point record
types.)
The Ovation Control Builder places these algorithms on control sheets to tell the Ovation control
system what algorithms to use, what points to associate with the algorithms, and in what order the
algorithms should execute. The Control Builder combines multiple algorithms and even multiple
control sheets to create an entire control strategy for a system process.
The Ovation algorithms are typically provided with the Ovation Controller, and are used to
implement a wide range of functionality for a Controller. Each algorithm is repres ented in the
Control Builder by a unique symbol.
For information on adding algorithms to sheets in the Control Builder, refer to Ovation Control
Builder User Guide.
Standard Ovation algorithms are described in Ovation Algorithms Reference Manual.
Q-line, Fieldbus, SIS, and migrated special function algorithms are described in Ovation Q-line
and Specialty Algorithms Reference Manual.
OW351_R1100 1
SECTION 2
2 General algorithm user information
IN THIS SECTION
What is hardware addressing for algorithms? ............................................................... 3

What is propagated point qualit y? ................................................................................ 4
Algorithm status and mode settings.............................................................................. 4
What is invalid number check ing and qualit y check ing for algorithms? ............................ 5
What are single precision floating point numbers? ......................................................... 6
What is the error information generated by algorithms ? ................................................. 6
Binary to hexadecimal conversion for algorithms ........................................................... 6
2.1 What is hardware addressing for algorith ms?
Some algorithms (for example, an MASTATION algorithm) require the hardware address of the
associated I/O module in order to perform their functions. You must enter the hardware address
for the algorithm into the hardware address field.
For a point that is read from or written to an I/O card, the hardware address parameter indicates
the offset from where the pertinent I/O register resides.
Addressing that is initialized in the algorithm is either for Ovation cards or Q-line cards.
 For Ovation, the address is determined by the module position in the I/O cabinet.
 For Q-line, the hardware address is equal to the address directly jumpered on the card plus
the offset into the proper channel number (no doubling required).
2.1.1 T o de te rmine an algorithm hardware address

1. Access the Point Information window to view the module record. Refer to Ovation Operator
Station User Guide.
2. Select the Hardware tab.
3. Note the hex representation of the hardware address for the module in the “HD” field.
4. The algorithm requires the base address, so take the “D” in the base address and convert it to
a zero.
5. Enter that value into the algorithm's hardware address field.
For example, if a Loop Interface module record's HD field is “0x9D” then “0x90” is entered in
the MASTATION'S hardware address field.
OW351_R1100 3
2.2 What is propagated point quality?
2.2 What is propagated point quality?
Many algorithms generate a quality setting for the output. In most cases, the quality of the output
equals the quality of the input. This is commonly called propagated quality. However, this simple
propagation is not true for all algorithms.
In general, the worst quality of the algorithm's input points is passed on to the output point for
each standard algorithm. For example, an input sensor failure causes BAD quality to propagate
through all standard algorithms that directly or indirectly use the input point. This BAD quality may
be used to reject certain algorithms to Manual mode. (Refer to the individual algorithm reference
pages for complete information.)
Process points may have one of the following quality values, assigned by the user or the system:
 GOOD = Point is functioning properly.
 FAIR = Typically an entered value.
 POOR = Generated from certain algorithms if some inputs were BAD and some were GOOD.
 BAD = Point is not functioning properly, typically caused by sensor failure.
Note: Algorithms propagate GOOD quality when in Manual mode.
2.3 Algorithm status and mode settings
The mode and status digital signals are set as follows:
S I G N AL AC TI O N
Auto Mode MASTATION sets the output Auto Mode signal TRUE when the algorithm is in
Auto mode.
High Limit Reached All algorithms set the High Limit Reached output signal TRUE when the output
is at the high lim it specified and the High Limit Reached output signal is not
scan removed.
Local Manual Mode MASTATION sets the Local Manual Mode output signal TRUE when the
algorithm is in Local Manual mode.
Low Limit Reached All algorithms set the Low Limit Reached output signal TRUE when the output
is at the low limit specified and the Low Limit Reached output signal is not
scan removed.
Manual Mode MASTATION sets the output Manual mode signal TRUE when the algorithm is
in Manual mode.
4 OW351_R1100
2.4 What is invalid number checking and quality checking for algorithms?
2.4 What is invalid number checking and quality checking for

algorithms?
Most algorithms perform invalid number checking on analog input points. These points include
tracking inputs. If an invalid number is detected, the drop goes into alarm and the problem is
identified by Fault Code 66, Fault ID 3.
For algorithms, Fault Parameter 3 contains the number of the algorithm sheet detecting an invalid
number. These numbers are reported as hexadecimal values. The Ovation System Viewer
application provides access to fault code information and suggests possible user actions to
correct the fault.
An invalid number is generated under exceptional conditions. An example of such conditions is

taking the square root of a negative number. The Function s ection in the individual algorithm
reference sheets identifies those algorithms, which provide additional checking to avoid specific
exceptional conditions.
When an invalid number is input to an algorithm, generally the output of the algorithm is also
invalid and is marked with BAD quality. In the following algorithm reference sheets, each
algorithm that performs invalid number checking discusses how the invalid number is treated and
the results that occur from the invalid number.
There are three types of invalid numbers: indefinite, NAN, and denormal.
 An indefinite invalid number is generated from a mathematical operation for which there is no
reasonable result.
 A NAN (not-a-number) invalid number is an unrecognizable real number format and should
never occur.
 A denormal invalid number is generated when the result of a mathematical operation is too
small to be represented in the 32-bit real number format used in the system. If an analog input
is a denormal invalid number, the drop is placed into alarm identified by Fault Code 66, Fault
ID 3.
However, certain algorithms store the denormal value into a temporary variable, convert it to zero,
and use that value (0) in the algorithm calculation. Consequently, these algorithms calculate a
valid output value with GOOD quality and the drop goes into alarm.
If the output of the algorithm is a denormal invalid number, then the value of the output is set to
zero and the drop is not placed into alarm. These denormal invalid numbers are displayed
throughout the system as zero.
If an invalid number is generated, the cause of the problem generate should be immediately
investigated and corrected since it could cause a control problem in the system.
In addition to invalid number checking, many algorithms generate a quality set ting on the output.
OW351_R1100 5
2.5 What are single precision floating point numbers?
2.5 What are single precision floating point numbers?
Single precision floating point numbers are represented within 32 binary bits. One-bit is the sign of
the characteristic, 23-bits show the binary value of the characteristic, one-bit for the sign of the
mantissa, and 7-bits for the value of the binary mantissa.
The Ovation system is limited to single precision floating point numbers, which can affect
algorithm precision. In certain cases, this may prevent an algorithm from writing a value beyond a
certain number if a single precision floating point limitation is reached. Although the internal
algorithm calculation can handle double precision floating point numbers, Ovation points are
limited to single precision values. More information is available by researching the IEEE754
floating point standard.
2.6 What is the error information generated by algorithms?
The second status word in an analog or digital process point may contain error information
generated by an algorithm that processed the value of that point.
For analog and digital points, the 2W record field contains the second status word.
 If a bit is TRUE, then the error indicated by that bit has been detected.
 If a bit is FALSE, then the error has not been detected.
2.7 Binary to hexadecimal conversion for algorithms
The following binary to hexadecimal conversion table is included to assist you in using algorithms
that require binary to hexadecimal conversion.
Binary to Hexadecimal Conversion
B I N AR Y TO HE X AD E C I M AL C O N V E R S I O N T AB L E
B I N AR Y H E X AD E C I M AL DE C I MAL
0000 0 0
0001 1 1
0010 2 2
0011 3 3
0100 4 4
0101 5 5
0110 6 6
0111 7 7
1000 8 8
1001 9 9
1010 A 10
1011 B 11
1100 C 12
6 OW351_R1100
2.7 Binary to hexadecimal conversion for algorithms
B I N AR Y TO HE X AD E C I M AL C O N V E R S I O N T AB L E
B I N AR Y H E X AD E C I M AL DE C I MAL
1101 D 13
1110 E 14
1111 F 15
For example, in DIGDRUM, the following binary number represents the states of the 16 outputs in
a given step. The right-most bit represents Output 001, and the left-most bit represents Output
016. For example, if you want Step 5 to have the outputs in these states, I05 would be initialized
to 0x53C6.
Byte = 8 bits, Integer = 16 bits
Binary: 0101 0011 1100 0110 0101001111000110B
Hexadecimal: 5 3 C 6 0x53C6
OW351_R1100 7
SECTION 3
3 Understanding tracking
IN THIS SECTION
What is track ing? ........................................................................................................ 9

What is the purpose of track ing? ................................................................................ 10
What is the track ing process? .................................................................................... 11
What are the best practices for using track ing? ........................................................... 11
What algorithms support track ing? ............................................................................. 12
Track ing examples .................................................................................................... 14
Setting track ing signals for algorithms ........................................................................ 15
3.1 What is tracking?
The tracking function is a sophisticated control feature that is implemented through the signals
that connect the algorithms. Tracking may be defined as aligning a portion of a control system
that is not in control to the portion of the control system that is in control.
To implement tracking in the Ovation system, tracking signals are sent between algorithms.
These signals tell the upstream algorithm whether or not to be in the tracking mode and what
value is required by the downstream algorithm to achieve the present output.
Typically, multiple control strategies (or “modes”) are defined to control a process. For example,
both manual and automatic control modes may be available. Multiple types of automatic control
may be available, such as flow control, level control, element control, and cascade control modes.
During the transition from one control mode to another, tracking is needed.
When transferring between control strategies (for instance, from manual to automatic control
modes), information is required by the newly selected control strategy to ensure a smooth
transition. These required values are obtained from the active control strategy and are provided to
the other available strategies. This exchange of information between control strategies is referred
to as tracking.
OW351_R1100 9
3.2 What is the purpose of tracking?
Tracking signals are automatically generated by the Control Builder. The Control Builder assigns
points to carry the tracking mode and value information. The insertion of tracking logic is
transparent to the user (requires no user input to implement). You have the option of turning
tracking off.
Tracking should be turned off for the following situations:

 Tracking from a mathematical calculation.
 When using PID to a setpoint to keep from winding up a PID, priority lower/raise. Typically, do
not allow tracking to change a setpoint.
Tracking can be blocked in the following ways:

 Place the algorithms on a separate sheet. Since automatic tracking only occurs within a
sheet, tracking is effectively blocked.
 Use Control Builder to remove tracking points from the TRIN entry fields.
3.2 What is the purpose of trackin g?
There are two purposes for tracking:

 Prevent bumps.
Changes in the mode of a process have the potential to disrupt the process. For example,
consider a situation where a control element is manually set to a low level, even though the
automatic control scheme is calculating a high level. If the control mode is changed to
automatic, a “bump” occurs as this control element’s setting goes from low to high. If the
change is extreme, equipment damage could result. Methods used to avoid this type of rapid
adjustment are referred to as “bumpless transfer.”
 Reduce process upsets.
A process upset may be defined as a condition in which the control system causes the
process to temporarily move to an operating point that differs from the desired point. Often the
process upset is caused by failing to hold the integral action of a PID Controller in check; this
condition is called reset windup.
For example, a PID control scheme sums a Proportional component and an Integral
component. In certain situations, the value of the output may reach its limit (100%) while one
of the components is still increasing. Although the output cannot be driven past 100%, it takes
time for the component value to return to the appropriate range. During this time, if it is
necessary to lower the output, the artificially high component value can cause a delay. In
order to keep the control scheme components within the appropriate range, an approach
called Anti-reset windup limiting is used.
To ensure bumpless transfer (during the transition from one control mode to another) and to
avoid reset windup, tracking is needed.
10 OW351_R1100
3.3 What is the tracking process?
3.3 What is the tracking process?
Tracking works by reverse calculation of the normal control functions. Control may be thought of
as proceeding from “top to bottom,” with inputs on the top, computations in the middle, and
outputs on the bottom. On the other hand, tracking may be thought of as proceeding from “bottom
to top,” with the output values on the bottom being used to calculate values for the computational
elements in the middle. Effectively, tracking calculates a value for an upstream control function,
so that the upstream objectives are satisfied.
One output point that is used for tracking is created for each algorithm that has an IN1 input. The
output is listed in the algorithm definitions as TOUT. TOUT contains the track output value, mode
and status output signals for the cascade IN1 variable.
Some algorithms have two to four additional tracking outputs for the Input 2, Input 3, and Input 4
as well. These are TRK2, TRK3, and TRK4.
The tracking output is input by the upstream algorithm as TRIN (Tracking Input Point) according
to the tracking rules outlined in the following sections. TRIN contains the tracking analog input
value and the tracking and limiting mode input signals.
Tracking values are generated by a reverse calculation of the normal algorithm function. That is,
when the algorithm is actively controlling the process, it uses one or more inputs to calculate an
output. When in the tracking mode, the algorithm is provided with the output value, and must
calculate the input value required to obtain that output. This value is sent to the upstream
algorithm that is generating the algorithm’s input. When there is more than one input, the value is
sent to the IN1 input.
Not all algorithms initiate tracking. All algorithms do not process the signals the same way. Refer
to the individual algorithm descriptions to determine how the signals are processed for a particular
algorithm.
3.4 What are the best practices for using tracking?
Refer to the following guidelines when using tracking:

 Tracking is typically done upstream.
 Do not unnecessarily use the GAINBIAS algorithm.
 Use MAMODE priority raise/lower instead of external transfers below MASTATION
algorithms.
 Tracking signals are always visible (except for BALANCER signals) and are typically shown in
green.
 If downstream tracking can come from more than one source, then the initial building order
determines the source unless manually changed. The exception to this is the BALANCER
algorithm, which can accept tracking from up to 16 downstream algorithms.
 Tracking may be broken after the signal wires are drawn. On the Windows platform, this may
be done with the Clear Tracking icon.
 If non-tracking algorithms are inserted between tracking algorithms, then the designer is
responsible for tracking across the “gaps.” Typically, the TRANSFER algorithm is used above
the gap to insert the user-computed tracking.
OW351_R1100 11
3.5 What algorithms support tracking?
 Reset Windup limiting is performed by tracking algorithms if:

 They are properly configured for tracking.
 The scale limits (TPSC and BTSC) are set to reflect the accepted signal range.
 In addition, the PID and PIDFF algorithms provide for enhanced windup limiting in the
cascade configuration.
 Cross sheet tracking is implemented by passing a tracking point “upstream” through the same
page connectors that pass control signals downstream.On the Windows platform, this is done
by using the Set Tracking icon with the signal wires.
 Tracking points are fully managed by OCB except when tracking crosses between sheets,
and when tracking from a downstream algorithm into a BALANCER algorithm.
Since the BALANCER algorithm tracks from many downstream algorithms, tracking
connections between a BALANCER algorithm and any downstream algorithms are not
graphically visible.
 Typically, there is only one tracking input (IN1) to an algorithm, except for TRANSFER and
SELECTOR algorithms.
 Before you implement tracking, consider the following:
 What are scaling factors, voltage, percentage, temperature?
 Where is the I/O located?
 What is the frequency of the point?
 The Track Ramp Rate (TRAT) referred to in the algorithm descriptions is used by the
algorithm when tracking action is terminated and normal control begins. It is the time in units
per second for the output to decay or ramp to the value dictated by the inputs under normal
(non-tracking) operation. The default Track Ramp Rate value is 2.5 units
The algorithms in the following table support tracking through dual-purpose analog inputs and
outputs (that is, track value in AV field, mode status bits in 3W field). See Ovation Record Types
Reference Manual for information on record fields and status bits.
Note: The following algorithms are described in the Ovation Q-Line and Specialty Algorithms
Reference Manual: FFAI, FFAO, FFDI, FFDO, FFMAI, FFPID, QSRM, XMA2, and XML2.
Tracking algorithm summary
A L G O R I TH M TRAT TOUT TRK1 TRK2 TRK3 TRK4 AC C E P T C AS C AD E

RAMP TO TO TO TO TO TRIN T R AC K
IN1 IN1 IN2 IN3 IN4 O P TI MI Z E
ANALOG x x
DEVICE
BALANCER x x TRK01-
TRK16
DIVIDE x x x
FIELD x
FFAI x
12 OW351_R1100
A L G O R I TH M TRAT TOUT TRK1 TRK2 TRK3 TRK4 AC C E P T C AS C AD E

RAMP TO TO TO TO TO TRIN T R AC K
IN1 IN1 IN2 IN3 IN4 O P TI MI Z E
FFAO x
FFDI x
FFDO x
FFMAI x
FFPID x1 x
FUNCTION x x x
GAINBIAS x x x
GASFLOW x x
HISELECT x x x x x x
LEADLAG x x x
LOSELECT x x x x x x
MASTATION x x x
MULTIPLY x x x
PID x x1 x x
PIDFF x x1 x x
QSRMA x x x
RATELIMIT x x
SETPOINT x2 x
SETSTATES x
SQUARE- x x x
ROOT
SUM x x x
TRANSFER 3 x4 x x x
XMA2 x x x
XML2 x2 x
X3STEP x x
1 Through S (setpoint) pin
2 Information Only
3 Supports switchable slewing and s witchable tracking
4 Ramps supported on both TRR1 and TRR2 pins
OW351_R1100 13
3.6 Tracking examples
3.6 Tracking examples
Tracking: Mode Transition
One of the most common uses of tracking is during the transition between manual mode and auto
mode. In this case, the control algorithm upstream of the MASTATION algorithm must be tracked
to the current output of the MASTATION algorithm. The input to the MASTATION station is the
same as the output from the MASTATION station at the moment of the mode change, and
bumping is prevented.
Tracking: SUM Algorithm
Another common use of tracking is for one input into a SUM algorithm. A two-input SUM algorithm
normally adds two inputs, A and B, to produce an output, C. That is, A + B = C. When the
algorithm is in tracking mode, C is dictated by downstream tracking requirements and one of the
inputs, which may be continually varying as process conditions change. Therefore, a value for the
other input must be calculated by the algorithm such that the sum of the inputs is equal to the
required output. Simple algebraic manipulation of the SUM equation reveals that the dependent
input must be tracked to the difference between required C and independent B. That is, A = C - B.
Tracking: PID Algorithm
Still another common tracking use involves one of the inputs to a PID algorithm’s error calculation.
As in the SUM example, the output of the PID is dictated by downstream tracking requirements
and the process variable acts as an independent variable. However, because integral action is
involved in this control algorithm, the concept for tracking changes. Here, the appropriate
technique is to cause a zero error to be presented to the PID during tracking periods to provide no
error-related movement of the PID output when tracking is initially released.
Therefore, the dependent input to the PID error function, the set point, should be tracked to the
value of the process variable input so that a zero-error condition is produced. Also, the PID output
must be tracked when the associated portion of the sys tem is not in control so that integral action
does not cause process upsets by following set point errors. As described previously, this
condition is called reset windup.
Typically, an MASTATION algorithm is placed below the PID algorithm on a control sheet.
In summary, there might be a change in your plant's process values (for example, the
temperature rose in a feedwater system). The applicable process control sheet contains the logic
that defines the desired value for the process. The algorithm PID looks at the difference between
the actual process value and the desired process value and reacts based on this difference. It
performs the necessary action (for example, add cold water to lower the water temperature) to
bring the process back to the desired value.
Tracking: Reset Windup
The concept of reset windup applies to normal control modes as well as to tracking modes. It is
undesirable to allow the integral action in a control algorithm to move any further in a direction
that tends to drive a control element past its limits of travel. Once the integrator winds past where
it should be, it takes time to wind back to the control region when the time comes. Control delays
result and process upsets may occur. The solution is to compute an integrator output that keeps
the downstream demand to the control element at the limit until it becomes time to drive the
control element into the control range. This approach is called anti-reset windup limiting.
14 OW351_R1100
3.7 Setting tracking signals for algorithms
Tracking: Anti-Reset Windup
The Ovation tracking functions performs the anti-reset windup limiting function if the following two
conditions are met:
 The sheets must be configured using the Ovation sheet tracking rules.
 The Scale Top and Scale Bottom parameters of the algorithms must be set to reflect the
actual control element ranges, usable controller ranges, and so forth.
The fact that an algorithm is at its top or bottom of scale is used to produce signals that inhibit the
upstream algorithm from moving too far in the wrong direction. If algorithms are properly
configured, reset windup is prevented. Reset windup is technically more of a concern in control
mode than in tracking mode.
The digital tracking signals are set and used as described in t he following table.
S I G N AL AC TI O N O F TH E AL G O R I TH M I MP L E ME N T A TI O N B Y TH E
I N I TI ATI N G TH E T R AC K I N G AL G O R I TH M BE I N G T O L D TO
T R AC K
Track PID and PIDFF set the Track output signal The output value is set equal to the
TRUE. Track input value. An internal track
buffer is set up to provide a
TRANSFER sets the Track output signal bumpless transfer when the Track
TRUE for the value that is not selected. input signal is removed.
MASTATION set the Track output signal
TRUE for one loop after it reads the
hardware value on the first pass.
MASTATION sets the Track output signal
TRUE when the algorithm is not in Auto
mode.
All algorithms set the Track output signal
TRUE when the Track input signal is
TRUE.
OW351_R1100 15
T R AC K
Track-if-Lower HISELECT sets the Track-if-Lower output If the output value of the PID or
signal TRUE for the value that is not PIDFF is less than the Track input
selected only when there are no Track, value, then a negative error causes
Track-if_Higher, or Track-if-Lower input the Controller to take action from the
signals and the gain on the input value is previous output value, and a positive
positive. error causes the Controller to take
action from the Track input value.
LOSELECT sets the Track-if-Lower output
signal TRUE for the value that is not
selected only when there are not Track,
Track-if-Higher, or Track-if-Lower input
signals and the gain on the input value is
negative.
All algorithms set the Tack-if-Lower output
signal TRUE when there is no Track input
signal and either:
 The Track-if-Lower signal is TRUE and
the gain on the input value is positive, or
 The Track-if-Higher input signal is TRUE
and the gain on the input value is
negative.
Track-if-Higher LOSELECT sets the Track-if-Higher output If the output value of PID or PIDFF
signal TRUE for the value that is not is greater than the Track input value,
selected only when there are no Track, then a positive error causes the
Track-if-Higher, or Track-if-Lower input Controller to take action from the
signals and the gain on the input value is previous output value, and a
positive. negative error causes the Controller
to take action from the Track input
HISELECT sets the Track-if-Higher output value.
signal TRUE for the value that is not
selected only when there are no Track,
Track-if-Higher, or Track-if-Lower input
signals and the gain on the input value is
negative.
All algorithms set the Track-if-Higher output
signal and :
positive, or
 The Track-if-Lower input signal is TRUE
negative.
16 OW351_R1100
T R AC K
Lower Inhibit PID and PIDFF set the Lower Inhibit output The output is prevented from
signal TRUE when the algorithm is in decreasing its value, but it is
Cascade mode, no Track input signal permitted to increase.
exists, and:
and either the gain on the setpoint is
positive with INDIRECT action on the
error or the gain on the setpoint is
negative with DIRECT action on the error,
or
negative with INDIRECT action on the
error, or the gain on the setpoint is
positive with DIRECT action on the error.
All algorithms set the Lower Inhibit output
signal and:
 The output value is at the low limit
specified and the gain on the output value
is positive, or
 The output value is at the high limit
specified and the gain on the input value
is negative, or
 The Lower Inhibit input signal is TRUE
positive, or
 The Raise Inhibit input signal is TRUE
negative.
OW351_R1100 17
T R AC K
Raise Inhibit PID and PIDFF set the Raise Inhibit output The output is prevented from
signal TRUE when the algorithm is in increasing its value, but it is
Cascade mode, no Track input signal permitted to decrease.
exists, and:
positive with INDIRECT action on the
negative with DIRECT action on the error,
or
negative with INDIRECT action on the
positive with DIRECT action on the error.
All algorithms set the Raise Inhibit output
signal, and:
 The output value is at the high limit
is positive, or
 The output value is at the low limit
is negative, or
 The Raise Inhibit input signal is TRUE
positive, or
 The Lower Inhibit input signal is TRUE
negative.
18 OW351_R1100
SECTION 4
4 Algorithm classifications
IN THIS SECTION
What are algorit hm classification groups? ................................................................... 20

Alarm Manipulation algorithms ................................................................................... 21
Artificial I/O algorithms (signal generators) .................................................................. 21
Boolean Logic algorithms .......................................................................................... 22
Boolean Logic Memory algorithms ............................................................................. 22
Custom Calculation algorithms .................................................................................. 23
Device Control algorithms ......................................................................................... 23
Fieldbus algorithms ................................................................................................... 24
Filtering algorithms ................................................................................................... 25
Hardware Interface algorithms ................................................................................... 26
Link Controller Module Interface algorit hms ................................................................ 27
Loop Interface Module algorithms .............................................................................. 28
Mathematical and Statistical algorit hms ...................................................................... 29
Modulating Cont rol algorithms ................................................................................... 30
Monitor Function algorithms ...................................................................................... 31
Operator Interface algorithms .................................................................................... 32
Point Format Conversion algorithms .......................................................................... 33
Pulse Accumulator Module Interface algorithms .......................................................... 34
Q-Line Interf ace algorithms ....................................................................................... 35
Redundant Signal Processing algorithms ................................................................... 36
Sequential Logic algorithms ....................................................................................... 37
Signal Compensation algorithms ................................................................................ 38
System Diagnostic algorithms .................................................................................... 39
System Time Function algorithms .............................................................................. 39
Time/Counter Function algorithms ............................................................................. 40
Track ing algorithms................................................................................................... 41
Turbine Interface algorithms ...................................................................................... 42
OW351_R1100 19
4.1 What are algorithm classification groups?
4.1 What are algorithm classificat ion groups?
Algorithms can be classified according to their function. Many algorithms can be placed in more
than one category because they can have multiple applications.
All of the standard Ovation algorithms can be found in at least one of the following algorithm
classification groups:
Note: Reference pages for standard Ovation algorithms are found in the Ovation Algorithms
Reference Manual. Reference pages for Q-Line, Fieldbus, SIS, and migrated algorithms are
found in Ovation Q-line and Specialty Algorithms Reference Manual.
 Alarm manipulation algorithms (see page 21).

 Artificial I/O algorithms (Signal Generators) (see page 21).
 Boolean logic algorithms (see page 22).
 Boolean logic memory algorithms (see page 22).
 Custom calculation algorithms (see page 23).
 Device control algorithms (see page 23).
 Fieldbus algorithms (see page 24).
 Filtering algorithms (see page 25).
 Hardware interface algorithms.
 Link Controller module interface algorithms (see page 27).
 Loop interface module algorithms (see page 28).
 Mathematical and statistical algorithms (see page 29).
 Migrated special function algorithms.
 Modulating control algorithms (see page 30).
 Monitor function algorithms (see page 31).
 Operator interface algorithms (see page 32).
 Point format conversion algorithms (see page 33).
 Pulse accumulator module interface algorithms (see page 34).
 Q-Line Interface algorithms (see page 35).
 Redundant signal processing algorithms (see page 36).
 Safety Instrumented System (SIS) algorithms.
 Sequential logic algorithms (see page 37).
 Signal compensation algorithms (see page 38).
 System diagnostic algorithms (see page 39).
 System time function algorithms (see page 39).
 Time/counter function algorithms (see page 40).
 Tracking algorithms (see page 41).
 Turbine interface algorithms (see page 42).
20 OW351_R1100
4.2 Alarm Manipulation algorithms
4.2 Alarm Manipulation algorithms
Description
Alarm manipulation algorithms provide a means of interfacing alarm information into the control
scheme.
Common uses
Alarm manipulation algorithms have the following uses:
 Drive alarm panels.

 Determine alarm states to trigger control functions.
Commonly used algorithms of this type

 ALARMLIMIT (see page 51) -- Allows logic to be driven using alarm limits and values
produced by analog points.
 ALARMMON (see page 56) -- Monitors up to 16 analog or digital points for alarm states.
 ANNUNCIATOR (see page 66) -- Calculates alarm state.
 SOFTSOE (see page 510) - Allows a Sequence of Events (SOE) to be generated by software
in control sheets.
4.3 Artificial I/O algorithms (signal generators)
Description
Artificial I/O algorithms generate a value and serve as place holders to input values into the
system.
Common uses
Artificial I/O algorithms have the following uses:

 Provide an interface for operator value entry.
 Input fixed constants into the control scheme.
 Change the point name of a signal.

 ASSIGN (see page 74) -- Transfers the value and quality of one process point to another
process point of the same type.
 AVALGEN (see page 77) -- Analog value generator.
 DVALGEN (see page 222) -- Digital value generator.
OW351_R1100 21
4.4 Boolean Logic algorithms
4.4 Boolean Logic algorithms
Description
Boolean logic algorithms represent logical gates for binary logic (1 or 0).
 AND - All inputs must be true to get true output. Implement as normally open contacts in a
series.
 OR - One or more inputs must be true to get true output. Implement as normally open
contacts in parallel.
 NOT - Inverts the input. Implement with normally closed contacts.
 XOR - Inputs must be different from each other to get true output. For example, out = (A AND
(NOT B)) OR ((NOT A) AND B).
Common uses
Boolean logic algorithms have the following use:

 Implement functions in binary logic.

 AND (see page 65) - Logical AND gate up to eight inputs.
 NOT (see page 360) - Logical NOT gate.
 OR (see page 369) - Logical OR gate up to eight inputs.
 TRUTHTB L (see page 578) - Condenses discrete logic elements (for example, AND, OR,
NOT, XOR, NAND, or NOR) into one algorithm call.
 XOR (see page 588) - Exclusive OR of two inputs.
4.5 Boolean Logic Memory algorithms
Description
Boolean logic memory algorithms remember the state of the input change.
Common uses
Boolean logic memory algorithms have the following uses:

 Implement on/off switches to initiate start/stop functions.
 Latch binary outputs.
 Implement toggle switches.

 AAFLIPFLOP (including alternate implementations) (see page 48) - Alternate action flip-flop
with reset.
 FLIPFLOP (see page 267) - S-R type flip-flop memory with set or reset override.
22 OW351_R1100
4.6 Custom Calculation algorithms
4.6 Custom Calculation algorithms
Description
Custom calculation algorithms support complex mathematical equations within a single algorithm.
These algorithms can be used to simplify mathematical processes instead of using separate
mathematical function algorithms.
Common uses
Custom calculation algorithms have the following uses:

 Enter mathematical functions and utilize the result in the control scheme.
 Convert gray codes to actual rod positions.

 CALCBLOCK (see page 103) - Allows you to define a mathematical calculation using a list of
operators.
 CALCBLOCKD (see page 112) - Operates like CALCBLOCK, but is used for logical functions
only (digital version).
 DRPI1A - Digital rod position indicator.
4.7 Device Control algorithms
Description
Device control algorithms are predefined control schemes used to quickly implement start/stop,
open/close logic.
Common uses
Device control algorithms have the following uses:

 Start/stop motors.
 Open/close valves, dampers, etc.
 Calculate running time.

 ANALOG DEVICE (ADEVICE) (see page 58) - Interfaces to Motor Control Centers (MCCs).
 DEVICE (see page 124) - Combines the commands to open/close/stop or start/stop a piece of
equipment with feedback signals indicating the command was accomplished.
 DEVICEX (see page 148) - Combines the commands to open/close or start/stop a piece of
equipment with feedback signals indicating the command was accomplished.
OW351_R1100 23
4.8 Fieldbus algorithms
 DIGITAL DEVICE (see page 174) - Provides logic to control the following seven types of
devices:
 MOTOR (see page 180) - Simple controlled motor.
 MOTOR NC (see page 178) - Non-controlled motor.
 MOTOR 2-SPD (see page 183) - Two-speed or bi-directional controlled motor.
 MOTOR 4-SPD (see page 186) - Two-speed and bi-directional controlled motor.
 SAMPLER (see page 175) - Controlled sampler (calculates running time).
 VALVE (see page 192) - Controlled valve.
 VALVE NC (see page 177) - Non-controlled valve.
 ELCCONTROL - Allows control logic to select which ELC module, of a redundant pair, is in
control.
4.8 Fieldbus algorithms
Description
Fieldbus algorithms interface to Fieldbus function blocks. Function blocks are self-contained
software modules that reside in Fieldbus devices. Therefore, Fieldbus devices can be controlled
by Ovation Fieldbus algorithms and integrated as part of an Ovation control scheme.
Note: Information on Fieldbus algorithms can be found in Ovation Q-Line and Specialty
Algorithm Reference Manual.
Common uses
Fieldbus algorithms have the following use:

 Implement Foundation Fieldbus logic at the transmitter level.

 FFAI (see page 678) - Foundation Fieldbus analog input.
 FFAO (see page 681) - Foundation Fieldbus analog output.
 FFARTHM - Foundation Fieldbus arithmetic.
 FFDI (see page 684) - Foundation Fieldbus digital input.
 FFDO (see page 687) - Foundation Fieldbus digital output.
 FFINT - Foundation Fieldbus integrator.
 FFISEL/FFISELX (see page 690) - Foundation Fieldbus input selector.
 FFMAI (see page 698) - Foundation Fieldbus multiple analog input.
 FFMAO (see page 702) - Foundation Fieldbus multiple analog output.
 FFMDI (see page 704) - Foundation Fieldbus multiple digital input.
 FFMDO (see page 708) - Foundation Fieldbus multiple digital output.
 FFPID (see page 712) - Foundation Fieldbus PID.
 FFSGCR - Foundation Fieldbus signal characterizer.
24 OW351_R1100
4.9 Filtering algorithms
4.9 Filtering algorithms
Description
Filtering algorithms stabilize I/O readings. In most cases, they are used to filter out noise or
compensate for a true delay.
Common uses
Filtering algorithms have the following uses:
 Smooth noisy signals.

 Compute averages.
 Compensate for transport delays.
 Implement derivative functions in the control scheme.

 LEADLAG - Lead/lag compensator.
 QAVERAGE (see page 438) - Average N analog points; exclude points with Bad quality;
N < 9.
 RATELIMIT - Rate limiter with fixed rate limit and flag when rate limit is exceeded.
 RUNAVERAGE (see page 469) - Running average transform.
 SMOOTH (see page 508) - Smoothed value transform.
 TRANSPORT (see page 575) - Transport time delay.
OW351_R1100 25
4.10 Hardware Interface algorithms
4.10 Hardware Interface algorithms
Description
Hardware interface algorithms read and/or write data to/from I/O modules or field devic es.
Common uses
Hardware interface algorithms have the following uses:

 Interface to a specific type of hardware.
 Allow monitoring and diagnosing of output signal status.
 Perform digital positioning of control devices.

 ANALOG DEVICE (ADEVICE) (see page 58) - Interfaces to local analog loop Controllers.
 ATREND (see page 75) - Trend an analog or digital point.
 ELCCONTROL - Allows control logic to select which ELC module, of a redundant pair, is in
control.
 FIELD (see page 257) - Write value to a hardware output point.
 DFIELD (see page 167) - Used only with hardware digital output variable points.
 DXCSTATUS (see page 224) - interfaces with the digital excitation controller for the purpose
of reconciling the module’s tuning parameters with the Ovation database server.
 RPACNT (see page 457) - Count pulses from the Pulse Accumulator card.
 RPAWIDTH (see page 458) - Pulse width from the Pulse Accumulator card.
 RSRSTATUS (see page 459) - Interface to the RSR card.
 RVPSTATUS (see page 476) - Reads the Value Positioner card status and information.
 X3STEP (see page 589) - Acts as a positioner control for field devices.
Also see Link Controller module interface algorithms (see page 27).
26 OW351_R1100
4.11 Link Controller Module Interface algorithms
4.11 Link Controller Module Interface algorithms
Description
Link Controller module interface algorithms manipulate inputs, outputs, and statuses to the
Ovation Link Controller module providing serial communications via standard protocols to external
devices (such as Modbus, Allen-Bradley, etc.).
Common uses
Link Controller algorithms have the following uses:

 Read/write registers to/from QLC or LC cards.
 Provide status for link diagnostics.

 SLCAIN (see page 486) - Reads analog input(s) from QLC/LC.
 SLCAOUT (see page 489) - Writes analog output(s) to QLC/LC.
 SLCDIN (see page 492) - Reads digital input(s) from QLC/LC.
 SLCDOUT (see page 495) - Writes digital output(s) to QLC/LC.
 SLCPIN (see page 498) - Reads packed digital input(s) from QLC/LC.
 SLCPOUT (see page 501) - Writes packed digital ouput(s) to QLC/LC
 SLCSTATUS (see page 504) - Status value of QLC/LC.
OW351_R1100 27
4.12 Loop Interface Module algorithms
4.12 Loop Interface Module algorithms
Description
Loop interface module algorithms enable the interface to the local loop controllers or electric
drives. For more information, see Ovation I/O Reference Manual.
Common uses
Loop interface module algorithms have the following uses:
 Interface to electric drives.

 Interface to remote auto/manual stations.

 MASTATION (see page 325) - Interfaces between a soft manual/auto station and the
functional processor.
 RLICONFIG (see page 454) - Configures the loop interface card.
 SETPOINT (see page 482) - Soft and/or hard manual loader station with an interface to the
RLI card setpoint.
 XMA2 (see page 645) - Interface between a soft manual/auto station and a QAM, QAA, or
QLI card and the functional processor.
 XML2 (see page 656) - Soft and/or hard manual loader station with an interface to the QAM
or QLI card setpoint.
Note: Refer to Ovation Q-Line and Specialty Algorithms Reference Manual for information on
the XMA2 and XML2 algorithms.
28 OW351_R1100
4.13 Mathematical and Statistical algorithms
4.13 Mathematical and Statistica l algorithms
Description
Mathematical and statistical algorithms perform calculations using standard math formulas and
properties.
Common uses
Mathematical and statistical algorithms have the following uses:
 Implement trigonometric functions.

 Perform custom calculations by entering a mathematical formula.
 Perform basic math functions like adding, multiplying, dividing, and so forth.
 Perform linear curve interpolation between segments.
 Calculate statistical values like average, mean, and standard deviation.

 ABSVALUE (see page 50) - Absolute value of an input.
 ANTILOG (see page 69) - Aantilog of scaled input, base 10 or natural base.
 ARCCOSINE (see page 71) - Arccosine on an input (in radians).
 ARCSINE (see page 72) - Arcsine of an input (in radians).
 ARCTANGENT (see page 73) - Arctangent of an input (in radians).
 CALCBLOCK (see page 103) - Defines a mathematical calculation using a list of operators.
 CALCBLOCKD (see page 112) - Defines a mathematical calculation using a list of operators
(performs logical functions only).
 COSINE (see page 119) - Cosine of an input (in radians).
 DIVIDE - Divides two gained and biased inputs.
 FUNCTION (see page 269) - Twelve breakpoint function generator.
 GAINBIAS - Limits a gained and biased input.
 INTERP (see page 299) - Provides a linear table lookup and interpolation function.
 LOG (see page 316) - Base10 logarithm and bias.
 MULTIPLY - Multiplies two gained and biased inputs.
 NLOG (see page 359) - Natural logarithm with bias.
 POLYNOMIAL (see page 404) - Fifth order polynomial equation.
 SINE (see page 485) - Sine of an input (in radians).
 SQUAREROOT - Square root of a gained and biased input.
 STATISTICS (see page 525) - Calculates variance and standard deviation of input samples,
based on values from TW (time window).
 SUM - Adds four gained and biased inputs.
 TANGENT (see page 557) - Tangent of an input (in radians).
OW351_R1100 29
4.14 Modulating Control algorithms
4.14 Modulating Control algorithms
Description
Modulating control algorithms implement modulating control strategies, such as level control,
feedwater control, flow/temperature controls, and so forth.
Common uses
Modulating control algorithms have the following uses:
 Implement modulating control scheme with balancing functions, selection functions, override
functions, proportional, integral and derivative functions, and operator interface functions.

 BALANCER (see page 78) - Controls up to 16 downstream algorithms.
 DISTRIBUTOR (see page 195) - Distributes an input signal (IN) into two or more (up to eight)
analog outputs (OUTx).
 FUNCTION (see page 269) - Twelve breakpoint function generator.
 HISELECT - Selects the greater of two gained and biased inputs.
 LOSELECT - Selects the smaller of four gained and biased inputs.
 MAMODE (see page 323) - Logic interface to MASTATION.
 MASTATION (see page 325) - Interface between a soft manual/auto station and the
 PID (see page 372) - Proportional plus integral plus derivative controller
 PIDFF (see page 389) - Proportional plus integral plus derivative controller with feed forward.
 PREDICTOR (see page 406) - Compensate for pure time-delay.
 RAMPGEN (see page 440) - Ramps its output to follow a setpoint target when in automatic
mode, or it ramps the output up or down at a fixed rate in manual mode.
 SETPOINT (see page 482) - Soft and/or hard manual loader station.
 TRANSFER - Selects a gained and biased input based on a flag.
See also Track ing algorithms (see page 41).
30 OW351_R1100
4.15 Monitor Function algorithms
4.15 Monitor Function algorithms
Description
Monitor function algorithms monitor point status with certain criteria such as limits, quality, and
transitions. These algorithms create discrete logic that can be used for program flow control.
Common uses
Monitor function algorithms have the following uses:
 Generate flags based on process conditions.

 Trigger control actions.
 Monitor signal status.

 COMPARE (see page 118) - Floating point compare.
 DBEQUALS (see page 122) - Deviation monitor between two variable inputs.
 DIGCOUNT (see page 168) - Digital counter with flag.
 HIGHLOWMON (see page 287) - High and low signal monitor with reset deadband and
fixed/variable limit.
 HIGHMON (see page 288) - High signal monitor with reset deadband and a fixed/variable
limit.
 LOWMON (see page 322) - Low signal monitor with reset deadband and a fixed/variable limit.
 PULSECNT (see page 437) - Pulse count.
 QUALITYMON (see page 438) - Quality check one input.
 RATECHANGE (see page 444) - Rate of change transform.
 RATEMON (see page 449) - Rate of change monitor with reset deadband and fixed/variable
rate limit.
 SOFTSOE (see page 510) - Allows a Sequence of Events (SOE) to be generated by software
in control sheets.
OW351_R1100 31
4.16 Operator Interface algorithms
4.16 Operator Interface algorithms
Description
Operator interface algorithms are control function algorithms that provide a means for the
operator to interact with the control system.
Common uses
Operator interface algorithms have the following uses:
 Provide a mechanism to actuate functions in the control scheme.

 Generate control commands.
 Dynamically move process set points.
 Interface to external loop controllers and drives.
 Auctioneer between multiple control signals.

 BUFFER (see page 89) - Gathers the value and status of a point and associates a timestamp
with this information.
 FACEPLATE (see page 249) - Generic algorithm used to collect all inputs necessary for a
graphic faceplate.
 KEYBOARD (see page 303) - Programmable/function key interface - P1 through P10 to
control key interface.
 MEDIANSEL (see page 348) - Monitors analog transmitter inputs for quality and deviation
from each other.
RLI card setpoint.
 2XSELECT (see page 599) - Selects and monitors two transmitter signals.
Also see Device control algorithms (see page 23).
the XMA2 and XML2 algorithms.
32 OW351_R1100
4.17 Point Format Conversion algorithms
4.17 Point Format Conversion algorithms
Description
Point format conversion algorithms provide the means to translate point values from one data
structure to another.
Common uses
Point format conversion algorithms have the following uses:
 Change a point name.

 Transfer to/from a binary-coded decimal (BCD).
 Manipulate packed signals.

 BCDNIN (see page 83) - Inputs n BCD digits to the functional processor from the DIOB.
 BCDNOUT (see page 85) - Outputs n BCD digits from the functional processor to the I/O bus.
 PACK16 (see page 370) - Packs up to 16 digital point values into a packed digital record.
 SATOSP (see page 479) - Transfers analog values to a packed digital record.
 SPTOSA (see page 520) - Transfers packed digital values to an analog record.
 TRANSLATOR (see page 571) - Translates the output based on the input of a predefined
table.
 UNPACK16 (see page 584) - Unpacks up to 16 digital point values from a packed digital
record.
OW351_R1100 33
4.18 Pulse Accumulator Module Interface algorithms
4.18 Pulse Accumulator Module Interface algorithms
Description
Pulse accumulator module interface algorithms read and reset accumulator pulses in the Ovation
Pulse Accumulator card.
Common uses
Pulse accumulator module interface algorithms have the following uses:
 Read the status for the pulse accumulator module.

 Write commands to the pulse accumulator module.

 QPACMD (see page 619) - Writes a command byte to a QPA card.
 QPACMPAR (see page 625) - Writes a comparator value to a QPA card.
 QPASTAT (see page 626) - Outputs the digital status from a QPA card.
 RPACNT (see page 457) - Counts pulses from the Pulse Accumulator (PA) card.
 RPAWIDTH (see page 458) - Pulse width from the Pulse Accumulator (PA) card.
the QPACMD, QPACMPAR, and QPASTAT algorithms.
34 OW351_R1100
4.19 Q-Line Interface algorithms
4.19 Q-Line Interface algorithms
Description
Q-Line interface algorithms are used specifically with Q-Line I/O hardware in an Ovation system.
These algorithms are the only Q-Line algorithms supported in Ovation.
Note: Information on Q-Line algorithms can be found in Ovation Q-Line and Specialty Algorithm
Reference Manual.
Common uses
Q-line algorithms have the following use:
 Used in Ovation for compatibility with Q-Line I/O.

 PVSPSLI (see page 609) - Writes the functional processor-defined process variable (PVAR)
and/or set point (STPT) values to the Q-Line Loop Interface (QLI) for display at the Loop
Interface Module (LIM).
 PWDIN (see page 612) - Converts a digital pulse to an analog value proportional to the width
of the pulse.
 QLIPASS (see page 614) - Changes the default station (or loop) number and password
number for up to 12 QLI cards
 QSDDEMAND (see page 627) - Writes demand and mode to a QSD card.
 QSDMODE (see page 629) - Indicates QSD mode.
 QSRMA (see page 630) - Interface manual/auto station to a QSR card.
 QVP (see page 636) - Interface to a QVP card.
 XFLOW (see page 639) - Calculates a pressure-and-temperature-compensated mass or
volumetric flow for ideal gases.
 XPIDSLI (see page 661) - PID controller with supervisory set point and QLI or QLJ card
interface
OW351_R1100 35
4.20 Redundant Signal Processing algorithms
4.20 Redundant Signal Processing algorithms
Description
Redundant signal process algorithms select which signal or which statistic (median, average,
maximum, minimum, and so forth) to use for control in a redundant configuration.
Common uses
Redundant signal processing algorithms have the following uses:
 Auctioneer between multiple control signals.

 Allow manual or automatic selection of the signal to be used for control purposes.

 MEDIANSEL (see page 348) - Monitors analog transmitter inputs for quality and deviation
from each other.
 SELECTOR (see page 480) - Transfer between n analog inputs, where n < 8.
 2XSELECT (see page 599) - Selects and monitors two transmitter signals.
36 OW351_R1100
4.21 Sequential Logic algorithms
4.21 Sequential Logic algorithms
Description
Sequential logic algorithms help you control processes that are sequential in nature and follow a
predetermined set of steps.
Common uses
Sequential logic algorithms have the following uses:
 Implement sequential logic.

 Selection of a specified output based on different input steps.
 Implement the step control functions.

 ANALOGDRUM (see page 61) - Drum controller with two analog outputs or with one analog
output.
 DEVICESEQ (see page 144) - Sequencer using MASTER/DEVICE arrangement.
 DIGDRUM (see page 169) - Drum controller with 16 digital outputs.
 FIFO (see page 259) - Transaction queue; first in - first out.
 FIRSTOUT (see page 262) - Monitors up to 16 digital inputs and provides an indication of the
first digital input to transition from zero to one.
 MASTERSEQ (see page 335) - Sequencer using MASTER/DEVICE arrangement.
 PRIORITY (see page 411) - Consolidates complex logic to perform priority-based sequencing
when turning devices ON and OFF.
 PRIORITY-E XT (see page 428) - Dynamically calculates external priorities and is designed
for use with the Priority algorithm.
 PRIORITY-RE J (see page 432) - Provides a method to manage load rejection up to a
predefined number of devices and is designed for use with the Priority algorithm.
 STEPTIME (see page 547) - Automatic step timer.
 TRANSLATOR (see page 571) - Translator.
 TRNSFNDX (see page 577) - Selects output analog value from up to 64 outputs which hold
the input.
OW351_R1100 37
4.22 Signal Compensation algorithms
4.22 Signal Compensation algorithms
Description
Signal compensation algorithms adjust the input signal based on density, volume, enthalpy, and
so forth in order to provide a true indication of the process value.
Common uses
Signal compensation algorithms have the following uses:
 Condition input signals to provide a true reading of the variable.

 Provide easy access to the steam tables to use for thermal dynamic conversions.
 Determine level and flow compensations based on density.

 BILLFLOW (see page 87) - Calculates gas flow.
 GASFLOW (see page 277) - Calculates a pressure and temperature compensated mass or
volumetric flow.
 LEVELCOMP (see page 312) - Calculates the density compensated water level in a
pressurized steam drum.
 STEAMFLOW (see page 542) - Flow compensation.
 STEAMTABLE (see page 544) - Calculates thermodynamic properties of water and steam.
 HSCLTP (see page 295) - Calculates Enthalpy (H) and Entropy (S) of Compressed Liquid
given its Temperature and Pressure.
 HSLT (see page 296)- Calculates Enthalpy (H) of Saturated Liquid given its Temperature.
 HSTVSVP (see page 297) - Calculates Enthalpy (H), Entropy (S), Temperature, and
Specific Volume of Saturated Vapor given its Pressure.
 HSVSSTP (see page 298) - Calculates Enthalpy (H), Entropy (S), and Specific Volume of
Superheated Steam given its Temperature and Pressure.
 PSLT (see page 435) - Calculates Pressure of Saturated Liquid given its Temperature.
 PSVS (see page 436) - Calculates Pressure of Saturated Vapor given its Entropy (S).
 SSLT (see page 524) - Calculates Entropy (S) of Saturated Liquid given its Temperature.
 TSLH (see page 582) - Calculates Temperature for Saturated Liquid given its Enthalpy
(H).
 TSLP (see page 583) - Calculates Saturation Temperature of Saturated Liquid given its
Pressure.
 VCLTP (see page 586) - Calculates Specific Volume of Compressed Liquid given its
Temperature and Pressure.
 VSLT (see page 587) - Calculates Specific Volume of Saturated Liquid given its
Temperature.
38 OW351_R1100
4.23 System Diagnostic algorithms
4.23 System Diagnostic algorithms
Description
System diagnostic algorithms directly interface and set system statuses in order to assist in
troubleshooting and monitoring Ovation points.
Common uses
System diagnostic algorithms have the following use:
 Provide a mechanism to monitor system status and initiate actions in the control system.

 DROPSTATUS (see page 218) - Drop status record monitor.
 HEARTBEAT (see page 284) - Generates heartbeat signals that can be received by other
drops.
 LATCHQUAL (see page 306) - Latches and unlatches the quality of an input analog or digital
point.
 PNTSTATUS (see page 402) - Point status.
For more information, refer to the Ovation Standard Algorithms Reference Manual.
4.24 System Time Function algorithms
Description
System time function algorithms read the UTC system clock and allow you to perform functions
based on time.
Common uses
System time function algorithms have the following use:

 Provide access to the system clock to implement time-related functions.

 SYSTEMTIME (see page 556) - Stores system date and time in analog points.
 TIMECHANGE (see page 558) - Time change.
 TIMEDETECT (see page 559) - Time detector.
 TIMEMON (see page 560) - Pulse digital points based on the system time.
OW351_R1100 39
4.25 Time/Counter Function algorithms
4.25 Time/Counter Function algorithms
Description
Timer/Counter function algorithms execute actions based on user-specified time input. These
algorithms manipulate an output based on time.
Common uses
Time/counter function algorithms have the following uses:
 Implement timing functions in the control scheme (such as delays and pulses).
 Monitor loop count to determine functions such as equipment running time.

 COUNTER (see page 120) - Interface up/down counter.
 OFFDELAY (see page 361) - Pulse stretcher.
 ONDELAY (see page 363) - Pulse timer.
 ONESHOT (see page 366) - Digital one-shot pulse.
 RESETSUM (see page 451) - Accumulates until told to reset.
 RUNTIME (see page 471) - Counts long lasting service times of devices.
 TIMEMON (see page 560) - Pulse digital points based on the system time.
40 OW351_R1100
4.26 Tracking algorithms
4.26 Tracking algorithms
Description
The tracking algorithms support tracking. Tracking may be defined as aligning a portion of a
control system that is not in control to the portion of the control system that is in control. Tracking
is used to prevent bumps and to reduce process upsets. Tracking algorithms support tracking
through dual-purpose inputs and outputs (that is, the track value in the AV field).
Common uses
Tracking algorithms have the following uses:

 Keep the system aligned while manual changes are performed in order to prevent bumps.
 Balance several large pieces of equipment in a plant.
 Maintain major plant loops inside their designed range of operation.

 ANALOG DEVICE (ADEVICE) (see page 58) - Interfaces to local analog loop controllers.
 BALANCER (see page 78) - Controls up to 16 downstream algorithms.
 DIVIDE - Divides two gained and biased inputs.
 FIELD (see page 257) - Writes value to I/O point.
 FUNCTION (see page 269) - Two-segment function generator.
 GAINBIAS - Limits a gained and biased input.
 GASFLOW (see page 277) - Calculates a pressure and temperature compensated mass or
volumetric flow.
 HISELECT - Selects the greater of two gained and biased inputs.
 LEADLAG - Lead/lag compensator.
 LOSELECT - Selects the smaller of four gained and biased inputs.
 MULTIPLY - Multiplies two gained and biased inputs.
 PID (see page 372) - Proportional plus integral plus derivative controller.
 PIDFF (see page 389) - Proportional plus integral plus derivative controller with feed forward.
RLI card setpoint.
 SETSTATES (see page 895) - Sets tracking bits in the Ovation tracking point based on the
inputs that are connected.
OW351_R1100 41
4.27 Turbine Interface algorithms
 SQUAREROOT - Square root of a gained and biased input.

 SUM - Adds four gained and biased inputs.
 X3STEP (see page 589) - Controls devices which must be kept within a certain tolerance.
the Foundation Fieldbus, QSRMA, XMA2, and XML2 algorithms.
Description
Turbine interface algorithms allow communication to the Ovation I/O interfaces and to hydraulic
servos dedicated to position control of process control valves.
Common uses
Turbine interface algorithms have the following uses:

 Read and write valve and status information to/from the Ovation RVP card.
 Read and write valve and status information to/from the Ovation QVP card.
 Read and write status information to/from the Ovation Servo Driver card.

 MASTATION (see page 325) - Interfaces between a soft manual/auto station and the
functional processor. This has been used to interface to the RVP I/O module in early Ovation
releases.
 QVP (see page 636) - Interfaces to a QVP card.
 QSRMA (see page 630) - Interfaces to the QSR card.
 RSRSTATUS (see page 459) - Reads the RSR card status and information.
 RVPSTATUS (see page 476) - Reads the RVP card status and information.
 XMA2 (see page 645) - Interfaces between a soft manual/auto station and a QAM, QAA, QLI,
or QVP card and the functional processor.
the QVP and QSRMA algorithms.
42 OW351_R1100
SECTION 5
5 Standard algorithm reference pages
..
IN THIS SECTION
Understanding algorithm descriptions......................................................................... 46

AAFLIPFLOP ........................................................................................................... 48
ABSVALUE .............................................................................................................. 50
ALARMLI MIT............................................................................................................ 51
ALARMMON ............................................................................................................ 56
ANALOG DEVICE (A DEVICE)................................................................................... 58
ANALOGDRUM........................................................................................................ 61
AND......................................................................................................................... 65
ANNUNCIATOR ....................................................................................................... 66
ANTILOG ................................................................................................................. 69
ARCCOSINE ............................................................................................................ 71
ARCSINE ................................................................................................................. 72
ARCTA NGE NT......................................................................................................... 73
ASSIGN ................................................................................................................... 74
ATREND .................................................................................................................. 75
AVALGEN ................................................................................................................ 77
BALANCE R.............................................................................................................. 78
BCDNIN ................................................................................................................... 83
BCDNOUT ............................................................................................................... 85
BILLFLOW ............................................................................................................... 87
BUFFER .................................................................................................................. 89
CALCBLOCK ......................................................................................................... 103
CALCBLOCKD ....................................................................................................... 112
COMPA RE ............................................................................................................. 118
COSINE ................................................................................................................. 119
COUNTE R ............................................................................................................. 120
DBEQUA LS ........................................................................................................... 122
DEVICE ................................................................................................................. 124
DEVICESEQ .......................................................................................................... 144
DEVICEX ............................................................................................................... 148
DFIELD .................................................................................................................. 167
DIGCOUNT ............................................................................................................ 168
DIGDRUM.............................................................................................................. 169
DIGITAL DEVICE ................................................................................................... 174
DISTRIBUTOR ....................................................................................................... 195
DIVIDE................................................................................................................... 215
DROPSTATUS ....................................................................................................... 218
DRPI1A .................................................................................................................. 221
DVALGE N.............................................................................................................. 222
DXCSTATUS ......................................................................................................... 224
FACEPLATE .......................................................................................................... 249
OW351_R1100 43
FIELD .................................................................................................................... 257

FIFO ...................................................................................................................... 259
FIRSTOUT ............................................................................................................. 262
FLIPFLOP .............................................................................................................. 267
FUNCTION ............................................................................................................ 269
GAINBIAS .............................................................................................................. 273
GASFLOW ............................................................................................................. 277
HEARTBEAT.......................................................................................................... 284
HIGHLOW MON ...................................................................................................... 287
HIGHMON.............................................................................................................. 288
HISELECT ............................................................................................................. 290
HSCLTP ................................................................................................................ 295
HSLT ..................................................................................................................... 296
HSTVSVP .............................................................................................................. 297
HSVSSTP .............................................................................................................. 298
INTERP ................................................................................................................. 299
KEYBOARD ........................................................................................................... 303
LATCHQUAL.......................................................................................................... 306
LEADLA G .............................................................................................................. 308
LEVELCOMP ......................................................................................................... 312
LOG....................................................................................................................... 316
LOSELE CT ............................................................................................................ 317
LOWMON .............................................................................................................. 322
MA MODE ............................................................................................................... 323
MASTATION .......................................................................................................... 325
MASTE RSEQ......................................................................................................... 335
ME DIANSEL .......................................................................................................... 348
MULTIPLY ............................................................................................................. 356
NLOG .................................................................................................................... 359
NOT....................................................................................................................... 360
OFFDE LAY ............................................................................................................ 361
ONDELAY .............................................................................................................. 363
ONESHOT ............................................................................................................. 366
OR......................................................................................................................... 369
PACK16 ................................................................................................................. 370
PID ........................................................................................................................ 372
PIDFF .................................................................................................................... 389
PNTSTATUS .......................................................................................................... 402
POLYNOMIAL ........................................................................................................ 404
PREDICTOR .......................................................................................................... 406
PRIORITY Algorithm Pack age ................................................................................. 410
PSLT ..................................................................................................................... 435
PSVS..................................................................................................................... 436
PULSECNT ............................................................................................................ 437
QAVERAGE ........................................................................................................... 438
QUALITY MON........................................................................................................ 438
RA MPGEN ............................................................................................................. 440
RATECHANGE ...................................................................................................... 444
RATELI MIT ............................................................................................................ 446
RATE MON ............................................................................................................. 449
RESETSUM ........................................................................................................... 451
RLICONFIG ........................................................................................................... 454
RPACNT ................................................................................................................ 457
RPAWIDTH ............................................................................................................ 458
RSRSTATUS ......................................................................................................... 459
RUNAVERA GE ...................................................................................................... 469
44 OW351_R1100
RUNTI ME .............................................................................................................. 471

RVPSTATUS .......................................................................................................... 476
SATOSP ................................................................................................................ 479
SELECTOR............................................................................................................ 480
SETPOINT ............................................................................................................. 482
SIMTI ME ................................................................................................................ 485
SINE ...................................................................................................................... 485
SLCAIN.................................................................................................................. 486
SLCAOUT .............................................................................................................. 489
SLCDIN ................................................................................................................. 492
SLCDOUT.............................................................................................................. 495
SLCPIN.................................................................................................................. 498
SLCPOUT .............................................................................................................. 501
SLCSTATUS .......................................................................................................... 504
SMOOTH ............................................................................................................... 508
SOFTSOE .............................................................................................................. 510
SPTOSA ................................................................................................................ 520
SQUAREFOOT ...................................................................................................... 521
SSLT ..................................................................................................................... 524
STATISTICS .......................................................................................................... 525
STEAMFLOW......................................................................................................... 542
STEAMTABLE ........................................................................................................ 544
STEPTIME ............................................................................................................. 547
SUM ...................................................................................................................... 552
SYSTEMTI ME ........................................................................................................ 556
TANGE NT.............................................................................................................. 557
TIMECHA NGE ....................................................................................................... 558
TIMEDE TECT ........................................................................................................ 559
TIME MON .............................................................................................................. 560
TRANSFE R............................................................................................................ 563
TRANS LATOR ....................................................................................................... 571
TRANSPORT ......................................................................................................... 575
TRNSFI NDX ........................................................................................................... 577
TRUTHTB L ............................................................................................................ 578
TSLH ..................................................................................................................... 582
TSLP ..................................................................................................................... 583
UNPA CK16 ............................................................................................................ 584
VCLTP ................................................................................................................... 586
VSLT ..................................................................................................................... 587
XOR ...................................................................................................................... 588
X3STEP ................................................................................................................. 589
2XSELECT............................................................................................................. 599
OW351_R1100 45
5.1 Understanding algorithm descriptions
Most of the algorithm reference pages contain the following information (where applicable):
 Description - Describes the algorithm's operation.
 Invalid Real Numbers and Quality - Describes how quality is set.
 Functional Symbol - Illustrates (in pictorial form) the algorithm's operation. See Algorithm
functional symbols (see page 47).
 Control Builder Symbols -- Shows how the algorithm will appear in the Control Builder and
Signal Diagram programs.
 Algorithm Record Type (if required) - Defines the type and size of the record generated for
storing parameters and other information necessary to the algorithm. (See Ovation Record
Types Reference Manual.)
 Algorithm Definitions - Provides the following information on the algorithm:
 Names of the parameters used.
 Algorithm record field used by each tuning constant or data initialization parameter; also,
the type of entry required in this field (integer, byte, or real).
 Parameter types such as those described below:
 Variable = Input or output signal to the algorithm (that is, analog or digital).
 Tuning Constant = Fixed parameter that remains constant unless it is changed by the
user at the Operator's Station or Control Builder.
 Data Initialization Parameter = Fixed constant that cannot be changed by the user at
the Operator's Station but can be changed by the Control Builder.
 Selectable = Can be either a Tuning constant in an algorithm record field or a point
record.
 Reconcilable Constant = Parameter can be tuned and reconciled through a special,
project-specific diagram.
 Algorithm Initialization = Internal parameter that is exposed by the algorithm.
 Definition of whether the parameter is required or optional.
If the parameter is optional and not initialized by the user, it defaults to zero.
If there are input points to the algorithm that are optional and not initialized by the user,
they have a value of zero for analog points and FALSE for digital inputs.
 Default value (if applicable).
 Brief description of the parameter.
 Minimum point record required by each variable.
Each algorithm defines the minimum size point record that can be used for each
algorithm input or output.
The quality (see page 4) of the points is set BAD when a detectable hardware failure is
encountered. This information can be used in control strategies or for alarming purposes
by detecting BAD quality using the QUALITYMON series of algorithms.
 Function - Explains the algorithm's operation in terms of a mathematical equation.
 Application Example - Provides an example to demonstrate the use of the algorithm.
 Miscellaneous Sections - Applicable to a specific algorithm only.
46 OW351_R1100
5.1.1 Algorithm functional symbols
The following table lists the items used in the algorithm functional symbols:
Functional symbols items description
FU N C TI O N AL D E S C R I P TI O N
S YMB O L
Required Analog (LA record type) input or output (solid line and solid
arrowhead).
Required Digital or Packed Digital (LD or LP record type) input or output (solid
line and hollow arrowhead).
Required Algorithm (LC record type) input or output (solid line and line
arrowhead).
Required Drop (DU) input or output (solid line and no arrowhead).
Optional or Selectable Analog (LA record type) input or output (dashed line and
solid arrowhead).
Optional or Selectable Digital or Packed Digital (LD, LP record type) input or
output (dashed line and hollow arrowhead).
Optional or Selectable Algorithm (LC record type) input or output (dashed line
and line arrowhead.
Optional or Selectable Drop (DU record type) input or output (dashed line and no
arrowhead)
Note: Symbols portrayed in this manual only serve as an example and can be configured
differently depending on the number and type of pins that are used. The Control Builder
application may show various symbol configurations of the same algorithm and may not directly
match what is shown in this document.
OW351_R1100 47
5.2 AAFLIPFLOP
5.2 AAFLIPFLOP
Description
The AAFLIPFLOP algorithm simulates a memory device whose output state is inverted by each
momentary TRUE signal on SRST (that is, the output state OUT is inverted when there is a
transition in the input SRST from a FALSE to a TRUE signal). OUT is set to FALSE anytime the
reset digital input signal RSET is TRUE.
Functional Symbol
Algorithm Record Type = LC
Algorithm Definitions
N AME LC AL G . T YP E RE Q U I R E D / D E F AU L T DE S C R I P TI O N MI N .
RE C O R D O P TI O N AL V AL U E POI N T
FI E L D RE C O R D
INIT - Variable Optional - Initial Value LD, LP
SRST - Variable Required - Input (digital) LD, LP

RSET - Variable Required - Reset Input LD, LP
(digital)
OUT - Variable Required - Output (digital) LD, LP
48 OW351_R1100
5.2 AAFLIPFLOP
Function
RSET OLD SRST SRST OUT
0 0 0 S
0 0 1 T
0 1 0 S
0 1 1 S
1 X X 0
where:
X = Value can be 0 or 1.
S = Output remains in the same or previous state.
T = Output toggles from the previous state.
OLD SRST = Value of the SRST input on the previous loop executed by the functional
processor.
On the first pass, OUT is set to FALSE if RSET is TRUE. Otherwise, OUT is set as follows:
 If the optional INIT input is initialized by the user, OUT is set to the value of INIT.
 If INIT is not initialized or has BAD quality on the first pass, OUT remains in the same
state. OUT is set to FALSE on power up/reset unless it is initialized to TRUE by the user
in the program.
OW351_R1100 49
5.3 ABSVALUE
5.3 ABSVALUE
Description
The output for the ABSVALUE algorithm is the absolute value of input IN1.
The value of IN1 is checked for invalid real numbers. If IN1 is valid, the quality of IN1 is
propagated to the quality of OUT and the real number value of OUT is written to the point record.
Invalid Numbers and Quality
If the value of IN1 is invalid or if the calculated value of OUT written to the point record is invalid,
the quality and the reason are set to BAD.
Functional Symbol
Algorithm Record Type = None
N AME LC AL G . T YP E RE Q U I R E D / DE F AU L T DE S C R I P TI O N MI N .
RE C O R D O P TI O N AL V AL U E P T.
FI E L D RE C .
IN1 - Variable Required - Input (analog) LA
OUT - Variable Required - Output (analog) LA
Function
OUT = ABS(IN1)
50 OW351_R1100
5.4 ALARMLIMIT
5.4 ALARMLIMIT
Description
The ALARMLIMIT algorithm allows logic to be driven using alarm limits and values produced by
analog points.
Functional Symbol
Alarm Limit Value (ALVAL)
The alarm limit value (ALVAL) parameter can be configured to output the current selected Limit
Type (LTYPE). This value is also stored in the Alarm Limit (ALIM) field. The ALIM field allows you
to reconcile the alarm limit to the control sheet for documentation purposes.
If the selected limit is not defined in the input point (as determined by the LB record field), the
algorithm will set ALVAL to 0 and BAD quality.
Note: Alarm Limits can be defined as values or points. In the case of a point, the algorithm will
use the value of the point during the executed control cycle.
Alarm Active (ACT)
The alarm active (ACT) output is set depending on the following three parameters: ATYPE,
LTYPE, and QUAL.
Alarm Type (ATYPE)
The chosen alarm type (ATYPE) determines how alarm limits and alarm cutouts should be
monitored.
ATYPE DE S C R I P TI O N
LQ Monitor Limit and Quality defined by LTYPE and QUAL.

LQC Monitor Limit and Quality defined by LTYPE and QUAL. Cutout bit is also
monitored. If a point is cutout, the algorithm will not set ACT output.
ALMQC Monitor Limit (including lower alarm limits) and Quality defined by QUAL. The
cutout bit is also monitored. If a point is cutout, the algorithm will not se t the ACT
output.
Note: If you choose ALMQC, the algorithm monitors the selected limit in LTYPE, and any lower
defined limits. For instance, if you choose LOW2, the algorithm monitors LOW2, LOW3, and
LOW4. The user-defined high and low limits are exempt from this and will only be monitored if
specifically selected.
OW351_R1100 51
5.4 ALARMLIMIT
Limit Type (LTYPE)
The chosen limit type (LTYPE) determines what limit the algorithm will use to determine if the
input point is in alarm. Deadbands are taken into account as well, using the same definition as the
DB and DJ record fields. Refer, Ovation Record Types Reference Manual for more information.
Description
LTYPE L I MI T FI E L D DE S C R I P TI O N
HIGH_UD UH User-defined high limit.

HIGH1 HL High limit 1.
HIGH2 ZH High limit 2.
HIGH3 3Y High limit 3.
HIGH4 4Y High limit 4.
LOW_UD UL User-defined low limit.
LOW1 LL Low limit 1.
LOW2 ZL Low limit 2.
LOW3 3Z Low limit 3.
LOW4 4Z Low limit 4.
Configured Quality (QUAL)
The configured quality parameter (QUAL) determines how quality is used in the calculation of the
ACT output. The QUAL table in the template describes the QUAL parameter options. For
instance, if "Value and GOOD quality" are selected, the output will be set to true if the LTYPE is
satisfied and the point quality is GOOD. If "Value or BAD quality" is selected, the output will be set
to true if the LTYPE is satisfied or the quality is BAD.
Description
QUAL DE S C R I P TI O N
LTYPE Alarm using LTYPE only; quality ignored.

LTYPE or BAD Alarm using LTYPE or BAD quality.
LTYPE or BAD, POOR Alarm using LTYPE or BAD or POOR quality.
LTYPE or BAD, POOR, FAIR Alarm using LTYPE or BAD or POOR, FAIR quality.
LTYPE and GOOD Alarm using LTYPE and GOOD quality.
LTYPE and GOOD, FAIR Alarm using LTYPE and GOOD or FAIR quality.
LTYPE and GOOD, FAIR, POOR Alarm using LTYPE and GOOD, FAIR, or POOR quality.
52 OW351_R1100
5.4 ALARMLIMIT
Output Quality
Point quality is not propagated. If the selected LTYPE is currently not defined in the attached
analog input point (LB field), then the ALVAL output will go to zero (0), and the ACT output will
reset. Both outputs will also go to BAD quality.
SID Storage
In order to assist with graphics programming, all input and output point SIDs are stored in fields in
the algorithm. This allows the graphic to access multiple SIDs by accessing a si ngle SID (the
algorithm LC record).
N AME LC AL G . T YP E RE Q U I R E D / DE F AU L T D E S C R I P TI O N MI N .
FI E L D RE C .
Inputs:
IN C0 - SID Variable Required -- Analog input point. LA
Outputs:
ALVAL R1 - Value Variable Optional -- Alarm limit value. LA

C1 - SID
ACT G0 - Value Variable Optional -- Alarm active. LD, LP
C2 - SID
Parameters:
ATYPE B0 - Enum Data Init. Required 0 Alarm Type --

Parameter:
 LQ - LTYPE and
QUAL - Value is
0.
 LQC - LTYPE,
QUAL, and
cutout. Value is 1.
 ALMQC - LTYPE
including lower
limits, QUAL, and
cutout. Value is 2.
OW351_R1100 53
5.4 ALARMLIMIT
FI E L D RE C .
LTYPE B1 - Enum Data Init. Required 0 Limit Type --

Parameter:
 HIGH_UD - UH.
Output is val(UH).
Value is 0.
 HIGH1 - HL.
Output is val(HL).
Value is 1.
 HIGH2 - ZH.
Output is val(ZH).
Value is 2.
 HIGH3 - 3Y.
Output is val(3Y).
Value is 3.
 HIGH4 - 4Y.
Output value is
val(4Y). Value is
4.
 LOW_UD - UL.
Output is val(UL).
Value is 5.
 LOW1 - LL.
Output is val(LL).
Value is 6.
 LOW2 - ZL.
Output is val(ZL).
Value is 7.
 LOW3 - 3Z.
Output is val(3Z).
Value is 8.
 LOW4 - 4Z.
Output is val(4Z).
Value is 9.
54 OW351_R1100
5.4 ALARMLIMIT
FI E L D RE C .
QUAL B2 - Enum Data Init. Required 0 Configured Quality --

Parameter:
 LTYPE - Value is
0.
 LTYPE or BAD -
Value is 1.
 LTYPE or BAD,
POOR - Value is
2.
 LTYPE or BAD,
POOR, FAIR -
Value is 3.
 LTYPE and
GOOD - Value is
4.
 LTYPE and
GOOD, FAIR -
Value is 5.
 LTYPE and
GOOD, FAIR,
POOR - Value is
6.
* ALIM R2 Alg. Init. Variable 0 Alarm limit, same --
value as ALVAL.
Used to reconcile
alarm limit to
database.
HDB R3 Alg. Init. Variable 0 High deadband --
value. Used to
reconcile alarm
limit for control
sheet display.
LDB R4 Alg. Init Variable 0 Low deadband --
value. Used to
reconcile alarm
limit for control
sheet display.
* HIAL R5 Alg. Init. Variable 0 High incremental --
alarm limit value.
Used to reconcile
alarm limit for
control sheet
display.
* LIAL R6 Alg. Init. Variable 0 Low incremental --
alarm limit value.
used to reconcile
alarm limit for
control sheet
display.
* Even though these parameters are listed as "Alg. Init.," they are reconciled to the control sheet for
display purposes.
OW351_R1100 55
5.5 ALARMMON
5.5 ALARMMON
Description
The ALARMMON algorithm sets OUT equal to TRUE if any of the inputs are in alarm (alarm
status is TRUE). OUT is set to TRUE if unacknowledged and alarm bits are set in the first status
word of the point or alarm bit is TRUE and unacknowledged is FALSE.
The inputs are optional, numbering from 1 through 16, and may be analog or digital types. The
ALRM flag determines the type of alarm check that the algorithm performs.
 If the ALRM flag is 0 (X1=0), the optional output (FOUT) is set FALSE if no inputs went into
alarm since the last loop. FOUT is set TRUE for one loop when inputs go into alarm.
 If the ALRM flag is 1 (X1=1), the digital output (FOUT) is set TRUE if one or more inputs have
their unacknowledged alarm bit set to TRUE.
 If the ALRM flag is 2 (X1=2), the OUT point is set to a 1 when any of the Inputs are in alarm.
The FOUT point is set to a 1 (for 1 loop) if any of the inputs go into alarm and they were not in
Alarm in the previous loop.
 If the ALRM flag is 3 (X1=3), the OUT point is set to TRUE when any of the input points are in
ALARM. The FOUT point is set to a TRUE whenever any of the input points have both their
'ALARM' and 'unacknowledged' bits set TRUE.
Functional Symbol
56 OW351_R1100
5.5 ALARMMON
FI E L D RE C .
DIAG LU-Integer Data Init. Required 16 Tuning Diagram -

Number
ALRM X1-Byte Data Init. Optional 0 Type of alarm -
check:
0 = New Alarm
1=
Unacknowledged
alarm
2 = New
alarm/Any alarm
3=
Unacknowledged
alarm/Any alarm
IN1 - Variable Optional - Input (analog or LA, LD
digital)
•
•
•
IN16
FOUT - Variable Optional - Alarm Check LD, LP

Output (digital)
State change digital points should not be used since the alarm status is set TRUE for each state change.
This is an improper use of this algorithm.
OW351_R1100 57
5.6 ANALOG DEVICE (ADEVICE)

Description
The Analog Output Device algorithm is used to interface to Motor Control Centers (MCCs). Under
normal operation, the analog device algorithm attempts to control the device.
When the Analog Device algorithm is in AUTO, the error is calculated by taking the feedback
minus the demand times a sensitivity factor. The default sensitivity factor is one. If the error is less
than the inner deadband, the analog output is set to zero. If the error is greater than the outer
deadband, the analog output is set equal to this error. If the error is between the two deadbands,
the error is scaled between zero and one. The closer the error is to the outer deadband, the
closer the scale factor to one. The closer the error is to the inner deadband, the closer the scale
factor is to zero. The output is simply the error multiplied by the scale factor. The output is
clamped to the clamping limits (MAX). The quality of OUT is set to the worst quality of the two
inputs when not in tracking mode.
The shed relay is a copy of the tracking flag (IN3). If the tracking flag (IN3) is reset or the tracking
input indicates that there is tracking, the tracking output is equal to the tracking input. When
tracking, quality is set to the quality of the track input variable.
Tracking Signals
Tracking is performed through signals passed in the upper 16 bits of the third status word of the
analog tracking point. This algorithm takes the following action in response to the information
found in the digital input signal TRIN:
Bit description
BI T DE S C R I P TI O N AC TI O N TOUT S I G N AL
16 Track Implemented Passed Through
17 Track if Lower No Action Not Used

18 Track if Higher No Action Not Used
19 Lower Inhibit No Action Not Used
20 Raise Inhibit No Action Not Used
21 Conditional Track Implemented Passed Through
22 Not Used No Action Not Used
23 Deviation Alarm No Action Not Used
24 Local Manual Mode No Action Not Used
25 Manual Mode No Action Not Used
26 Auto Mode No Action Not Used
30 Low Limit Reached Implemented Passed Through
31 High Limit Reached Implemented Passed Through
58 OW351_R1100
Functional Symbol
FI E L D RE C .
DIAG LU-Integer Data Init Optional 118 Tuning Diagram -

Number
IN1G R6 Tuning Required 1.0 Demand Gain -
Constant
IN1B R7 Tuning Required 0.0 Demand Bias -

Constant
IN2G R8 Tuning Required 1.0 Feedback Gain -
Constant
IN2B R9 Tuning Required 0.0 Feedback Bias -
Constant
TPSC S1 Tuning Required 100.00 Output Top of Scale -
Constant
BTSC S2 Tuning Required 0.0 Output Bottom of -
Constant Scale
DLAY G0 Tuning Required 0.0 Deviation Time -
Constant Delay
ODBN R1 Tuning Required 0.0 Outer Deadband -
Constant
IDBN R2 Tuning Required 0.0 Inner Deadband -
Constant
MAX R3 Tuning Required 0.0 Maximum Output -
Constant
SENS R4 Tuning Required 1.0 Sensitivity -
Constant
DEVA R5 Tuning Optional 0.0 Deviation -
Constant Deadband
IN1 - Variable Required - Demand LA
TOUT - Variable Required - Tracking Output LA

IN2 - Variable Required - Feedback LA
OW351_R1100 59
FI E L D RE C .
IN3 - Variable Required - Tracking Flag LD

OUT - Variable Required - Analog Output LA
TRIN - Variable Required - Track Input LA
OUT2/ - Variable Optional - Shed Relay LD
SHED
OUT3/ - Variable Optional - Up Analog LA
OUTU
OUT4/ - Variable Optional - Down Analog LA
OUTD
OUT5 - Variable Optional - Deviation Alarm LD
60 OW351_R1100
5.7 ANALOGDRUM
5.7 ANALOGDRUM
Description
The ANALOGDRUM algorithm is a software drum controller with one analog output value and up
to 30 steps OR a software drum controller with two analog output values and up to 15 steps. The
output selected is based on the current step number and a list of up to 30 /15 initialized real
values. The current step number may be tracked to a selected step (TRIN) when in tracking mode
(TMOD = TRUE), increased (INC), or decreased (DEC). The current step number is only
increased or decreased on a FALSE to TRUE transition of INC and DEC. The maximum number
of steps must be initialized. When the step number becomes greater than the maximum number
of steps, the current step number is reset to one.
The track input value (TRIN) and output value (OUT) are checked for invalid real numbers. If a
tracking request is received and TRIN is an invalid number, then the tracking request is ignored.
However, the current step can be increased (using INC) or decreased (using DEC) even when
TRIN is an invalid number. If the algorithm calculates an invalid real number output, the value is
invalid and the quality is set to BAD.
Functional Symbol
FI E L D RE C .
DIAG LU-Integer Data Init Required 101 Tuning Diagram -

number
INC - Variable Required - Input (digital signal LD, LP
to increase the step
number)
DEC - Variable Required - Input (digital signal LD, LP
to decrease the step
number)
TMOD - Variable Required - Input (digital signal); LD, LP
tracking request
TRIN - Variable Required - Input (analog); tracks LA
the step number to
this value
NMIN X1-Byte Tuning Required 1 Maximum number of -
Constant steps
R01 R1-Real Tuning Optional 0 Output value for -
Constant Step 1
(+ or -)
OW351_R1100 61
5.7 ANALOGDRUM
FI E L D RE C .
R02 R2-Real Tuning Optional 0.0 Output value for -

Constant Step 2
(+ or -)
Constant Step 3
(+ or -)
Constant Step 4
(+ or -)
Constant Step 5
(+ or -)
Constant Step 6
(+ or -)
Constant Step 7
(+ or -)
Constant Step 8
(+ or -)
Constant Step 9
(+ or -)
R10 S1-Real Tuning Optional 0.0 Output value for -
Constant Step 10
(+ or -)
Constant Step 11
(+ or -)
Constant Step 12
(+ or -)
Constant Step 13
(+ or -)
Constant Step 14
(+ or -)
Constant Step 15
(+ or -)
Constant Step 16 (+ or -) or
Output value 2 for
Step 1
62 OW351_R1100
5.7 ANALOGDRUM
FI E L D RE C .

Output value 2 for
Step 2
Output value 2 for
Step 3
R19 T1-Real Tuning Optional 0.0 Output value for -
Output value 2 for
Step 4
Output value 2 for
Step 5
Output value 2 for
Step 6
Output value 2 for
Step 7
Output value 2 for
Step 8
Output value 2 for
Step 9
Output value 2 for
Step 10
Output value 2 for
Step 11
Output value 2 for
Step 12
R28 U1-Real Tuning Optional 0.0 Output value for -
Output value 2 for
Step 13
OW351_R1100 63
5.7 ANALOGDRUM
FI E L D RE C .

Output value 2 for
Step 14
Output value 2 for
Step 15
STEP - Variable Required - Output (analog); first LA
selected by the
current step number
OUT - Variable Required - Output (analog); LA
selected by the
current step number
OUT2 - Variable Optional - Output (analog); LA
selected by the
current step number
64 OW351_R1100
5.8 AND
5.8 AND
Description
The AND algorithm is a logical AND gate that can implement up to eight inputs. For the AND
algorithm, the output equals the logical AND of two to eight inputs (that is, all inputs must be
TRUE for the output to be TRUE). AND requires at least two inputs and up to eight digital inputs.
Functional Symbol
FI E L D RE C O R D
IN1 - Variable Required - Input (digital) LD, LP

IN3 - Variable Optional - Input (digital) LD, LP
OUT - Variable Req'd./Opt. - Output (digital) LD, LP
Note: Output is required if connected to anything other than another OR or AND.
Function
OUT = IN1 AND IN2 AND IN3 AND IN4 AND IN5 AND IN6 AND IN7 AND IN8
OW351_R1100 65
5.9 ANNUNCIATOR
5.9 ANNUNCIATOR
Description
The ANNUNCIATOR algorithm calculates one alarm window state of a lamp box, based on the
result of annunciator logic (IN1), the previous window state (OUT), and the inputs from the
operator push-button interface (ACK, RSET, TEST). The algorithm also determines the state of
the horn (HORN) and the chime (CHIM) based on IN1, OUT, and the inputs PRHN and PCHM.
Annunciator Input (IN1)
IN1 can be an analog, digital, or packed point. If IN1 is a packed point, the algorithm will count
each bit. If all 16 bits are set, then the algorithm assigns a value of 16 to IN1. If 15 bits are set,
regardless of which bits, then the algorithm assigns a value of 15 to IN1, and so on. Once the
value is determined, the algorithm will compare the value with the value of the last alarm state
(OUT).
Last Alarm State (OUT)
If IN1<=OUT and the OUT 1W unacknowledged bit is set and the user sets the ACK input true,
the algorithm will attempt to reset the OUT 1W unacknowledged bit.
Once the IN1 value is processed, the algorithm will set OUT equal to IN1
Fast Light Output (FAST)
The FAST output will be set true in the following instances:
1. If IN1 > OUT

2. If IN1 <= OUT and the OUT 1W unacknowledged bit is set and the ACK input is false and
either OUT 1W better alarm bit is not set or IN1 >= 0.
Slow Light Output (SLOW)
The SLOW output will be set true in the following instances:
1. If IN1 = 0 and the OUT 1W unacknowledged bit is set and the ACK input is true.
2. If IN1 = 0 and the OUT 1W unacknowledged bit is not set and the OUT 1W reset bit is set and
the RSET input is false.
Modify Light Output (MDFY)
The MDFY output will be set true in the following instance:
1. If 0 < IN1 <= OUT and the OUT 1W unacknowledged bit is set and the ACK input is false and
the OUT 1W better alarm bit is set.
66 OW351_R1100
5.9 ANNUNCIATOR
Light Output (STAT)

The STAT output will be set true in the following instances:
1. If TEST input is true.

2. If FAST is true.
3. If SLOW is true.
4. If MDFY is true.
5. If 0 < IN1 <= OUT and the OUT 1W unacknowledged bit is set and the ACK input is true.
6. If IN1 <= OUT and the OUT 1W unacknowledged bit is not set.
Note: All lights will be turned off if IN1 = 0 and the OUT 1W unack nowledged bit and reset bits
are not set.
Chime Output (CHIM)
The CHIM output will be set true in the following instances:
1. IN1 < OUT

2. If IN1 = 0 and the OUT 1W unacknowledged bit is set and the ACK input is true.
3. If Previous Chime Input (PCHM) is set.
Horn Output (HORN)
The HORN output will be set true in the following instances:
1. IN1 > OUT

2. If Previous Horn Input (PRHN) is set.
If the value of IN1 is invalid or if the calculated value of OUT (written to the point record) is invalid,
the quality and reason of OUT is set to BAD.
Functional Symbol
OW351_R1100 67
5.9 ANNUNCIATOR
FI E L D RE C .
IN1 - Variable Required - Input LA, LD,

LP
ACK - Variable Required - Acknowledge Input LD, LP

(digital)
RSET - Variable Required - Reset Input (digital) LD, LP
TEST - Variable Required - Test Input (digital) LD, LP

PRHN - Variable Required - Previous Horn Input LD, LP
(digital)
PCHM - Variable Required - Previous Chime Input LD, LP

(digital)
FAST - Variable Required - Fast Flash Output LD, LP

(digital)
SLOW - Variable Required - Slow Flash Output LD, LP
(digital)
MDFY - Variable Required - Modified Flash Output LD, LP
(digital)
STAT - Variable Required - Window State (on/off) LD, LP

Output (digital)
HORN - Variable Required - Current Horn Output LD, LP
(digital)
CHIM - Variable Required - Current Chime Output LD, LP
(digital)
68 OW351_R1100
5.10 ANTILOG
5.10 ANTILOG
Description
The ANTILOG algorithm scales an input value and outputs the antilog of the scaled value.
If the scaled input is outside the range for which the antilog can be stored as a real number, an
optional “out-of-range” digital is set, and the output value is set to the corresponding limiting
value.
Two algorithm tuning parameters are used: one for the scaling factor, and one to select the base
to be used for the calculation (base 10 or the natural base e, where the natural base e is the
default).
The value of IN1 is checked for invalid real numbers. If IN1 is invalid, the value of OUT equals the
invalid value of IN1, and OUT's quality is set to BAD and conditional calculated reason is set. The
quality of flag FOUT also is set to BAD. If IN1 is valid, the quality and reasons of IN1 are
propagated to OUT.
Note: Other logarithmic algorithms are LOG and NLOG.
Functional Symbol
N AME LC AL G . T YP E RE Q U I R E D / D E F AU L T D E S C R I P TI O N MI N .
FI E L D RE C .
DIAG LU-Integer Data Init. Required 64 Tuning Diagram Number -
BASE X1-Byte Data Init. Optional 0 Base selection: -

0 = Natural base e
1 = Base 10
Note: Any positive

integer selects Base 10
operation.
OW351_R1100 69
5.10 ANTILOG
FI E L D RE C .
SCAL R1-Real Tuning Optional 0.0 Scaling factor -

Constant
OUT - Variable Required - Output (analog); antilog LA

of the input value
FOUT - Variable Optional - Output (digital); LD, LP

out-of-range alarm
Function
OUT = e (IN1 x SCAL) if BASE = 0

OR
OUT = 10(IN1 x SCAL) if BASE = 1
Note: For range-check ing purposes, the upper and lower limits of x such that e x can be
represented as a real number are:
HIGH = 88.72 (HIGH is less than

IN * (3.4E + 38) = 88.722)
LOW = -87.31 (LOW is greater than

IN * (4.4E - 38) = -87.316)
70 OW351_R1100
5.11 ARCCOSINE
5.11 ARCCOSINE
Description
The ARCCOSINE algorithm performs the mathematical arc cosine function. ARCCOSINE has
one input and one output analog point. Each time the algorithm is executed, if the output is on
scan, it is set to the ARCCOSINE of the input. The output of this algorithm is in radians. If an
output in degrees is desired, multiply it by 57.29579 to convert to degrees. If the input to this
algorithm is outside the range of -1.0 to +1.0, the output is an invalid number and the drop is
placed into alarm.
Invalid Real Numbers and Quality
Analog input values are checked for invalid real numbers. If the input value is invalid, the value of
the output is invalid and its quality is set to BAD. If the input is valid, the quality of the input is
propagated to the output.
Functional Symbol
FI E L D RE C O R D
Function
OUT = ARCCOSINE (IN1)
OW351_R1100 71
5.12 ARCSINE
5.12 ARCSINE
Description
The ARCSINE algorithm performs the mathematical arc sine function. ARCSINE has one input
and one output analog point. Each time the algorithm is executed, if the output is on scan, it is set
to the ARCSINE of the input. The output of this algorithm is in radians. If an output in degrees is
desired, multiply it by 57.29579 to convert to degrees. If the input to this algorithm is outside the
range of -1.0 to +1.0, the output is an invalid number and the drop is placed into alarm.
Functional Symbol
FI E L D RE C O R D
Function
OUT = ARCSINE (IN1)
72 OW351_R1100
5.13 ARCTANGENT
5.13 ARCTANGENT
Description
The ARCTANGENT algorithm performs the mathematical arc tangent function. ARCTANGENT
has one input and one output analog point. Each time the algorithm is executed, if the output is on
scan, it is set to the ARCTANGENT of the input. The output of this algorithm is in radians. If an
output in degrees is desired, multiply it by 57.29579 to convert to degrees.
Functional Symbol
FI E L D RE C O R D
Function
OUT = ARCTANGENT(IN1)
OW351_R1100 73
5.14 ASSIGN
5.14 ASSIGN
Description
The ASSIGN algorithm transfers point value and the quality of one point to another point of the
same record type. The algorithm allows value and quality to be passed from one analog to
another analog point, or from a digital to another digital point or from one packed to another
packed point. For deluxe point types, the ASSIGN algorithm transfer the U8 and U9 timestamps
from the input point to the output point. In this way, it is possible to determine the time at which
the control logic had the value from the I/O available for computation inside the control task. You
must specify an output point name - default points may not be used.
If the input point is an analog point, the value is checked for an invalid real number. If the input
value is invalid, the value of the output is invalid and its quality is set to BAD.
Functional Symbol
N AME LC A L G . T YP E RE Q U I R E D / D E F AU L T D E S C R I P TI O N MI N .
FI E L D RE C O R D
IN1 - Variable Required - Input LA, DA,

LD, DD,
LP, DP
OUT - Variable Required - Output LA, DA,
LD, DD,
LP, DP
74 OW351_R1100
5.15 ATREND
5.15 ATREND
Description
The ATREND algorithm outputs a user-specified point to a strip chart recorder for trending. By
tuning the algorithm, the operator may change the point being trended to any point in the system
that is on the Ovation network. Any point with a system identification (that is, LA/LD record size or
larger) can be trended, regardless of the Controller in which the point is located or used. The
output to the recorder is set to zero percent for five seconds and then to 100 percent for 10
seconds to indicate that the point being trended or its scaling has been changed. A Tuning
diagram allows the point name to be entered to change the point being trended.
To enter a point to trend, open the Signal Diagram that contains the ATREND algorithm. Right -
click on the ATREND algorithm, and select the Advanced Tuning option. Enter the point name
to be trended on the advanced tuning window. For more information on Signal Diagram s, refer to
Ovation Control Builder User Guide.
Top of scale and bottom of scale values may also be specified online and are used to convert an
analog point's current value to a percentage of full scale. A digital point's current value is output
as either 25 percent (FALSE) or 75 percent (TRUE). This converted value is then normalized to
be output to a specified analog output point card. To time tag each hour during a trend, the output
to the recorder may be set to zero percent for five seconds at the start of each hour when this is
initialized in the X3 field of algorithm record. If you are not trending a point, a value of zero is
output to the I/O card. The output (TRND) is set TRUE when a point is being trended. If no point
is being trended, TRND is set FALSE.
Note: ATREND can only trend points on a local network , not on a remote network .
Functional Symbol
FI E L D RE C O R D

Number
OW351_R1100 75
5.15 ATREND
FI E L D RE C O R D
TYPE X3-Byte Data Init. Optional 0 Recorder card -

type:
0 = 1 to 5 V or 4 to
20 mA
Q-Line
1 = 0 to 10 V Q-
Line
2 = 1 to 5 V or 4 to
20 mA
Q-Line with hourly
marks
3 = 0 to 10 V Q-
Line with
hourly marks
TRND - Variable Required - Output (digital) LD, LP
CARD - Variable Required - Point with LA

Recorder
hardware address
(analog).
Note: The following fields in the algorithm record are used to trend a particular point. The Tuning
diagram associated with the tuning of this algorithm enables you to initialize and tune these fields.
LC Alg. Rec. Field Type Description

R2-Real Tuning Constant Top of scale value (default value = 100)
R3-Real Tuning Constant Bottom of scale value (default value = -100)
G0-Integer Tuning Constant System identification of the point being
trended. The point name entered on the
tuning diagram is automatically converted to
the system identification to be stored in this
field.
76 OW351_R1100
5.16 AVALGEN
5.16 AVALGEN
Description
The AVALGEN algorithm initializes an analog point. For the AVALGEN algorithm, the output is
the analog value stored in the tuning constant (VALUE). This value is a set point or bias to other
algorithms. If VALUE is entered incorrectly or if the data is corrupted, then the algorithm
generates an invalid number, the value of OUT is invalid, and its quality is set to BAD.
Functional Symbol
FI E L D RE C .

Number
VALU R1-Real Tuning Required 0 Analog value -
Constant (+ or -) of output
Function
OUT = VALU
OW351_R1100 77
5.17 BALANCER
5.17 BALANCER
Description
The BALANCER algorithm monitors the modes of up to 16 downstream algorithms and performs
a user-defined type of tracking when all of the downstream algorithms are requesting the
upstream algorithm to track. A special configuration of the BALANCER algorithm enables it to be
used to balance the outputs of several downstream Manual/Auto (M/A) station algorithms.
The actual number of downstream algorithms is initialized by the user. You connect the output of
this algorithm to the IN1 input of any downstream algorithm or to the IN2 input of a downstream
selector type algorithm. When configuring the BALANCER algorithm, y ou specify which
algorithms (in other sheets and/or drops) use the output signal of the BALANCER algorithm. The
BALANCER algorithm checks the feedback signals to see how many of the downstream
algorithms are requesting the upstream algorithm to track (how many are in Manual mode). It then
uses this information, along with the type of control initialized, to calculate the analog output value
which is being sent to the inputs of these downstream algorithms.
Note: The first time BALANCER is executed, or in a RESET/POWER UP occurrence, the

algorithm does not use the track input values passed back by the downstream algorithms until
the track inputs have been calculated by the downstream algorithms.
Also, when connecting track ing points, you must connect them sequentially. For example, the
BALANCER algorithm assumes that if the number of track ing points is three, then they must be
TRK1, TRK2, TRK3. They cannot be TRK1, TRK2, TRK4.
Functional Symbol
Note: If the TRK inputs are all raise inhibit or lower inhibit or a combination of raise inhibit and
manual or lower inhibit and manual, the BALANCER output value will stay at the value prior to
the inhibit.
In a raise inhibit condition, the value cannot be raised; however it can be lowered. Conversely,
in a lower inhibit condition, the value cannot be lowered; however it can be raised.
78 OW351_R1100
5.17 BALANCER
Control Modes
There are two types of control: NORMAL and MA BALANCER. You must select a type of tracking
(highest, lowest or average) to be used for both types of control.
NORMAL
If all of the downstream algorithms are requesting the upstream algorithm to track, then the output
of the BALANCER algorithm is either the highest, the lowest or the average of the analog track
signals passed back from the downstream algorithms. The quality of the output is then the worst
quality of the analog track signals passed back.
The gains and biases of the downstream algorithms that are between the BALANCER and the
MASTATION algorithms must be equal to 1.0 and 0.0, respectively, for this type of control to be
implemented properly.
If any of the downstream algorithms are not requesting the upstream algorithm to track, then the
output of the BALANCER algorithm is the gained and biased analog input value. The quality of
the output is the quality of the input value.
The downstream algorithms may be any of the standard algorithms. Internal tracking within the
BALANCER algorithm is implemented when switching from the highest, lowest, or average of the
analog track signals to the gained and biased analog input value.
MA BALANCER
Note: When the algorithm is track ing in "Balancer" mode, the TOUT value is the average of all
the TRK inputs.
If all of the downstream MA algorithms are requesting the upstream algorithm to track, then the
output of the BALANCER algorithm is either the highest, the lowest or the average of the analog
track signals passed back from the downstream algorithms.
If any of the downstream algorithms are not requesting the upstream algorithm t o track, then the
output of the BALANCER algorithm is a value which causes the average of all the downstream
algorithm outputs to be equal to the gained and biased input value.
The quality of the output is the worst quality of the analog track signals pass ed back.
The downstream algorithms must be MASTATION and the gains and biases of these algorithms
must all be equal to 1.0 and 0.0, respectively, for this type of control to be implemented properly.
Internal tracking within the BALANCER algorithm is implemented when switching from the
highest, lowest, or average of the analog track signals to the value which balances the
downstream algorithm outputs.
The analog track signals are used regardless of their quality.
If the algorithm generates an` invalid output value, the last valid value is used for the output, and
the quality of OUTPUT point is set to BAD. In addition, if the algorithm receives an invalid value
as an input, or calculates an invalid value as the output, the drop is placed into alarm.
OW351_R1100 79
5.17 BALANCER
Initializing the Algorithm
CAUTION! The feedback tracking signals from the downstream algorithms must be initialized
before downloading the BALANCER algorithm. If the feedback tracking signal information is
missing, errors result.
The Control Builder allows you to type in or connect signal lines for TOUT point from the
downstream algorithms. The tracking point is fed back as an analog track input to the BALANCER
algorithm to be used to calculate the correct analog output value.
Tracking Signals
This algorithm takes the following action in response to the information found in the analog track
signals (in the third status field), which are passed back from the downstream algorithms:
Bit description
BI T D E S C R I P TI O N A C TI O N TRK S I G N AL
16 Track Implemented Passed through*
17 Track if lower No action Passed through**

18 Track if higher No action Passed through**
19 Lower inhibit No action Passed through***
20 Raise inhibit No action Passed through***
21 Conditional Track No action Not used.
22 Not used No action Not used.
23 Deviation Alarm No action Not used.
24 Local Manual mode No action Not used.
25 Manual mode No action Not used.
26 Auto mode No action Not used.
27 Not Used No action Not used.
30 Low limit reached No action Low limit reached.
31 High limit reached No action High limit reached.
* Only when all of the track signals from the downstream algorithms are requesting the upstream
algorithm to track.
** Only when none of the track signals from the downstream algorithm are requesting the
upstream algorithm to track and when all of the downstream signals are requesting this signal.
*** Only when none of the track signals from the downstream algorithms are requesting the
upstream algorithm to track and when all of the downstream signals are requesting this signal.
The signals are set according to the definitions given in setting tracking signals (see page 15).
80 OW351_R1100
5.17 BALANCER
The output is limited by high and low limits specified by the user. The high and low limit flags and
the tracking signal from the algorithm are output in the third status field of the TOUT, to be used
for display and by an upstream algorithm.
Note: If the algorithm generates an invalid track output value, the IN1 input is used as the track
output value, unless it is invalid. The track output value is not updated if both the calculated
track output and IN1 input values are invalid. See guidelines in MASTATION algorithm
description for setting MASTATION CNFG parameter.
Algorithm Record Type= LC
FI E L D RE C .

Number.
NMIN X1-Byte Data Init. Required 1 Number of -
downstream
algorithms (up to 16).
CNTL G3-Integer Data Init. Required NORMAL Type of control to be -
Bit 0 implemented:
NORMAL = Normal
control mode.
BALANCER = MA
Balancer control
mode.
TRK G3-Integer Data Init. Required HIGHEST Type of tracking to -
Bits 1 and 2 be implemented:
HIGHEST: Highest
value.
LOWEST: Lowest
value.
AVERAGE: Average
value.
If CNTL is set to
BALANCER, TRK will
be treated as
average.
GAIN R1-Real Tuning Required 1.0 Gain on input -
Constant variable. The gain on
the input should never
be initialized to zero; if
it is, the drop is
placed into alarm.
BIAS R2-Real Tuning Optional 0.0 Bias on input variable. -
Constant
TPSC R3-Real Tuning Required 100.0 Maximum value of the -

Constant output point.
OW351_R1100 81
5.17 BALANCER
FI E L D RE C .
BTSC R4-Real Tuning Required -100 Minimum value of the -

Constant output point.
TRAT R5-Real Tuning Required 2.5 Track ramp rate (units -
Constant per second).
IN1 - Variable Required - Analog input variable LA
TOUT - Variable Required - Upstream input track LA

value, mode and
status of the algorithm
OUT - Variable Required - Analog output LA

variable.
TRK01 - Variable Required - One feedback LA
tracking signal from a
downstream algorithm
which consists of
tracking value and
tracking signals (in
the third status field of
analog track point).
TRK02 - Variable Required - One feedback LA
tracking signal from a
downstream algorithm
which consists of
tracking value and
tracking signals (in
the third status field of
analog track point).
TRK03 - Variable Optional - One feedback LA
tracking signals from
• a downstream
algorithm which
• consists of tracking
• value and tracking
signals (in the third
TRK16 status field of analog
track point).
82 OW351_R1100
5.18 BCDNIN
5.18 BCDNIN
Description
The BCDNIN algorithm reads a packed point (IN) in Binary Coded Decimal (BCD), converts it to a
real number, and stores it in the AV field of the output record (OUT). You must indicate the type of
action to be taken on the input value. Direct action causes the input value to be read directly.
Inverse action causes the input value to be read and inverted (one's complement) before it is
used. You must specify the number of BCD digits to read and the bit position where the reading is
to begin.
Functional Symbol
Algorithm Definition
FI E L D RE C .

Number
BITP X2-Byte Tuning Required - Bit position of the first -

Constant digit
NDIG X1-Byte Data Init. Required 1 Number of digits to -
read: 1, 2, 3, or 4
CNTL X3-Byte Tuning Optional Direct Control Action Indicator: -
Constant
0 = Direct Action - Card
value is read from the
I/O Bus and used. This
is for a BCD display
where low is TRUE.
1 = Inverse Action -
Card value is read from
the I/O Bus, inverted
and then used. This is
for a BCD display where
high is TRUE.
IN - Variable Required - Input (packed) LP
OW351_R1100 83
5.18 BCDNIN
Example 1
To read four BCD digits starting at Bit Position 0:
BITP = 0
NDIG = 4
Then, the current value of OUT is 6281.0.
Example 2
To read two BCD digits starting at Bit Position 4:
BITP = 4
NDIG = 2
Then, the current value of OUT is 28.
84 OW351_R1100
5.19 BCDNOUT
5.19 BCDNOUT
Description
The BCDNOUT algorithm reads a real value from input IN, converts it to binary -coded-decimal
(BCD), and outputs a number of digits to a packed output point. You must indicate the type of
action to take on the output value. Direct action causes the output value to be written directly.
Inverse action causes the value to be inverted (one's complement) before it is written to the output
point. You must specify the number of BCD digits to write, and the bit position where the writing is
to begin.
Invalid Numbers
The analog input (IN) is checked for invalid real numbers. If an invalid real number is entered as
IN, it is not written to the output point.
Functional Symbol
FI E L D RE C .

Number
BITP X2-Byte Tuning Required 0 Bit position of the first -
Constant digit
NDIG X1-Byte Data Init. Required 1 Number of digits to -

read: 1, 2, 3, or 4
OW351_R1100 85
5.19 BCDNOUT
FI E L D RE C .
CNTL X3-Byte Tuning Optional Direct Control Action Indicator: -

Constant
0 = Direct Action - Card
value is read from the
hardware and used.
This is for a BCD
display where 0 is
TRUE.
1 = Inverse Action -
Card value is read from
the hardware, inverted
and then used. This is
for a BCD display where
1 is TRUE.
IN - Variable Required - Input (analog) LA
OUT - Variable Required - Output (packed) LP
Example 1
To write four BCD digits, starting at Bit Position 0, where the current value of IN is 6281.0:
BITP = 0
NDIG = 4.
Example 2
To write two BCD digits, starting at Bit Position 4, where the current value of IN is 28.0:
BITP = 4
NDIG = 2
86 OW351_R1100
5.20 BILLFLOW
5.20 BILLFLOW
Description
The BILLFLOW algorithm generates an AGA3 gas flow calculation for orifices. It is applicable for
downstream and upstream static pressure measurements. It can be used for both tap and flange
orifices.
The super compressibility factor can be calculated one of two ways. The value can be passed in
the compressibility (SC) point, or the algorithm can calculate the compressibility factor with
additional information from the N2 and C02 tuning fields.
Functional Symbol
FI E L D RE C .

Number
FLOW X2-Byte Data Init. Required Down- Flow Element -
stream Type
(Downstream or
Upstream)
XDO R1-Real Tuning Required 0.0 Orifice ID -
Constant
DI R2-Real Tuning Required 0.0 Pipe ID -
Constant
PB R3-Real Tuning Required 14.73 Pressure Base -
Constant
TB R4-Real Tuning Required 60.0 Temperature -
Constant Base
TAP X1-Byte Data Init. Required Pipe Tap Location -
(Flange or Pipe)
CU R6-Real Tuning Required 0.001 Cutoff -
Constant
C02 R7-Real Tuning Required 0.75 Mole % C02 -
Constant
N2 R8-Real Tuning Required 0.48 Mole % N2 -
Constant
OW351_R1100 87
5.20 BILLFLOW
FI E L D RE C .
SP - Variable Required - Static Flowing LA

Pressure
(PSIG)
DP - Variable Required - Orifice LA
Differential
Pressure (IN
WC)
TEMP - Variable Required - Temperature of LA
Gas (Deg. F)
GRAV - Variable Required - Specific Gravity LA
SC - Variable Optional - Super LA
compressibility
BP - Variable Required - Barometric LA
Pressure (PSIA)
OUT - Variable Required - Gas Flow LA
Output (CF/HR)
88 OW351_R1100
5.21 BUFFER
5.21 BUFFER
Description
The BUFFER algorithm gathers the value and status of a point and associates a timestamp with
this information. The data is stored in a queue and is accessible via the High Speed Data
Acquisition (HSDA) Application Programming Interface (API). An API is an interface implemented
by a software program to enable interaction with other software, much in the same way that a
user interface facilitates interaction between humans and computers.
Functional Symbol
Requirements
A limited number of BUFFER algorithms may be used in any given Controller and control task
depending on the Controller processor and memory usage. It is up to the user to test the
algorithm/API performance to ensure data is being adequately collected.
Note: The API allows for up to 1,000 BUFFER algorithms per Controller; however, depending
on Controller processing time and memory usage, the Controller may not be able to support
1,000 BUFFER algorithms. Emerson recommends that all BUFFER algorithms be tested in a
worst case scenario on actual Controllers in order to prevent data loss.
The HSDA task in each Controller supports up to five individual connections.
HSDA API in each MMI supports up to 10 sessions.
Enable (ENBL)
The enable input (ENBL) parameter allows you to enable or disable the BUFFER algorithm. When
disabled, the BUFFER algorithm will not store any data and will not send any data to the queue
for retrieval. It will also zero out its internal buffer.
When enabled, the algorithm will immediately send data to the queue and will store up to 10 data
values in its own internal buffer. If no point is connected to the enable pin, the algorithm will
always be enabled.
On initial startup or if the algorithm is disabled, the STAT queue overflow bit, ACNT, TCNT, CEW,
and CER fields will be reset to zero.
OW351_R1100 89
5.21 BUFFER
Buffer Input Point (IN)
The buffer input point (IN) allows you to connect any analog (LA), digital (LD), or packed (LP)
point to the algorithm. When the algorithm is enabled, the algorithm will collect the value,
timestamp, and 1W field - First Status Word for LA and LD points, and the A3 field - Invalidity bits
for LP points. Collection occurs by exception or is based on deadband.
Timestamp
The timestamp is accurate to 1 millisecond resolution. The Controller provides the time based on
UTC (Coordinated Universal Time) time in the Controller. This information is stored in two
variables called timestampSeconds and timestampNanoseconds. The times tampSeconds
variable contains the amount of seconds since 12:00 AM January 1, 1970. The
timestampNanoseconds variable contains the amount of nanoseconds since the last full second.
Note: The time stored in timestampSeconds is provided in UTC. The user's application converts
this time to local time and adjusts a nanoseconds part from timestampNanoseconds.
After initial startup, the Controller uses the NTP server to set its calendar time. During this time,
the algorithm timestamp values may be invalid.
Timestamp Mode (TMODE)
The BUFFER algorithm allows you to configure how the algorithm retrieves the timestamp. If an
individual algorithm is selected, each BUFFER algorithm will retrieve a timestamp based on when
the algorithm was executed. If a control task is selected, then the control task will retrieve the
timestamp based on when it was executed and all BUFFER algorithms within the same control
task will use the same timestamp for that control cycle.
Deadbands
Analog Deadband (ADB)
If the connected point is an analog point, an analog deadband may be associated. The algorithm
uses the deadband to determine whether or not to collect the point's information and send it to the
queue. It uses the deadband as follows: the algorithm compares the previously collected value
with the currently scanned value for changes beyond the specified deadband value. For instance,
if the deadband is set to 5, and the point's current value is 9, but during the next control cycle, the
value is 12, the point will not be collected. However, if the point's value increases from 9 to 15 in
the next control cycle, the point information will then be collected and sent to the queue.
90 OW351_R1100
5.21 BUFFER
Digital Deadband (DDB)
If the connected point is a digital or packed point, a digital deadband may be as sociated. The
algorithm determines whether to collect the point information depending on which option is
selected:
 0 to 1 Transition -- Information is collected when the point value or any bit in the point
transitions from a 0 to a 1.
 1 to 0 Transition -- Information will be collected when the point value or any bit in the point
transitions from a 1 to a 0.
 State Change -- Information will be collected when the point value or any bit in the point
changes.
Note: If a zero analog deadband is assigned, the algorithm will collect the point value by
exception. Also, if the 1W field - status word or the A3 field - invalidity bits change for the IN
point, then the point will be collected and placed into the queue regardless of deadbands.
High Speed Data Acquisition
When the BUFFER algorithm is enabled, the value, status, and timestamp of the input (IN) will be
written to element 1 of the fields defined in the template. For each subsequent loop time, if the
BUFFER algorithm determines the value/status is to be collec ted, it will continue to write to each
element, increasing the element by 1 each time. For instance, the algorithm writes to element 1,
then element 2, then element 3, and so forth. After the algorithm writes to the 10th element, it
starts with element 1 again. If the algorithm is disabled, it resets all elements and starts from
element 1 when enabled again.
HSDA task
The information stored in each element is read by the High Speed Data Acquisition task (HSDA)
and sent to the appropriate MMI that is requesting the information. If the HSDA task is unable to
read the values from the element fields prior to the algorithm rewriting to that element, the
algorithm will set the queue overflow bit in the status output (STAT). The algorithm continues
writing over each subsequent element. When the HSDA task is able to read the current element,
the queue overflow bit resets.
Note: The HSDA task runs at a higher priority than the control task s in order to avoid pre-
emption by the control task .
Busy
The algorithm sets the busy bit to true when it is executing. The busy bit prevents the high-speed
data acquisition task from reading values in the middle of a data write. When the algorithm
finishes executing during a control task cycle, it resets the busy bit.
Queue Overflows
In order to determine a queue overflow, the algorithm and the HSDA task store a count of how
many times it has accessed the first element. For instance, the first time that the algorithm
completes writing to the first 10 elements, it stores a zero to the ACNT field; the next time the
algorithm writes to the first 10 elements, it stores a 1 to the ACNT field, and so on. After the
HSDA task reads the first 10 elements, it stores a zero to the TCNT field; the next time the HSDA
task reads the first 10 elements, it stores a 1 to the TCNT field, and so on.
OW351_R1100 91
5.21 BUFFER
In addition, the algorithm stores the current element written to the current element written (CEW)
field, and the HSDA task stores the current element read to the current element read (CER) field.
The BUFFER algorithm uses the information to determine if it has overwritten a field that has not
been read from yet. When this occurs, the queue overflow bit in the STAT output is set, and the
buffer continues to write values to each element. Any data not read by t he HSDA task during this
time is lost. When the HSDA task is able to read the current element, the queue overflow bit
resets.
Note: To avoid overruns, the algorithm subtracts 10,000 from ACNT and TCNT once TCNT
reaches 10,000.
N AME LC A L G . T YP E RE Q U I R E D / DE F AU L T DE S C R I P TI O N MI N .
FI E L D RE C O R D
Inputs:
ENBL C0 - SID Variable Optional -- Enable buffering. LD/LP

IN C1 - SID Variable Required -- Point value to be LA/LD/LP
collected.
Outputs:
STAT C2 - SID Variable Optional -- Status and related bit LP

number
 Enable = 0
 Queue Overflow = 1
Parameters:
ADB R1 Tuning Required 0 Analog Deadband. --

Constant
DDB G1 Tuning Required 0 Digital Deadband: --
Constant  0 = 0 to 1 Transition
(Enum)
 1 = 1 to 0 Transition
 2 = State Change
TMODE X2 Data Init Required 0 Timestamp Mode: --
 0 = Individual algorithm
 1 = Control task
BUSY X1 Alg. Init. -- -- Algorithm is writing values. --
ACNT G2 Alg. Init. -- -- Algorithm Element Count. --
TCNT G3 Alg. Init. -- -- HSDA Task Element --
Count.
CEW G4 Alg. Init. -- -- Current Element Written. --
CER G5 Alg. Init. -- -- Current Element Read. --
ST1 B0 Alg. Init. -- -- Status for Element 1. --
92 OW351_R1100
5.21 BUFFER
FI E L D RE C O R D

ST4 YU Alg. Init. -- -- Status for Element 4. --
TS1 D0 Alg. Init. -- -- Timestamp in seconds for --
Element 1.
TS2 YQ Alg. Init. -- -- Timestamp in seconds for --
Element 2.
Element 3.
TS4 YP Alg. Init. -- -- Timestamp in seconds for --
Element 4.
Element 5
Element 6.
Element 7.
TS8 YN Alg. Init. -- -- Timestamp in seconds for --
Element 8.
Element 9.
Element 10.
TNS1 YM Alg. Init. -- -- Timestamp in --
nanoseconds for
Element 1.
TNS2 YL Alg. Init. -- -- Timestamp in --
nanoseconds for
Element 2.
TNS3 E2 Alg. Init. -- -- Timestamp in --
nanoseconds for
Element 3.
nanoseconds for
Element 4.
nanoseconds for
Element 5.
OW351_R1100 93
5.21 BUFFER
FI E L D RE C O R D
TNS6 YC Alg. Init. -- -- Timestamp in --

nanoseconds for
Element 6.
TNS7 Y9 Alg. Init. -- -- Timestamp in --
nanoseconds for
Element 7.
nanoseconds for
Element 8.
nanoseconds for
Element 9.
TNS10 Y8 Alg. Init. -- -- Timestamp in --
nanoseconds for
Element 10.
VAL1 S1 Alg. Init. -- -- Value for Element 1. --
VAL10 T1 Alg. Init. -- -- Value for Element 10. --
HSDA API Description and Usage
The HSDA User API for Windows applications consists of the following files on each MMI:
 hsda.dll
 hsda.lib
 hsda_defines.h
 hsda.h
You must use these files to create your own application to communicate with selected Controllers
in order to collect data from each BUFFER algorithm.
94 OW351_R1100
5.21 BUFFER
Supplied Functions:
 HsdaStatus Type HsdaStartup()
 HsdaStatus Type HsdaSIDs(Hsda DropIdTy pe originatingDro p,

HsdaSidType* pSidList, HsdaSid Type* pInputSidList,
HsdaPointD ata Type *pDataTyp es, UINT32* pCount)
 HsdaStatus Type HsdaSIDto Nam e(HsdaSidT ype sid, char * buffer,

UINT32* pCount)
 HsdaStatus Type HsdaStartLog gin g(Hs daSidTy pe * pSidList, UINT32 *

pCount, HsdaSessionIdTy pe * ID)
 HsdaStatus Type HsdaData(Hsda SessionIdT ype ID, HsdaEventTy pe *

pEventList, UINT32 * pCount, BOOL EAN * pMore)
 HsdaStatus Type HsdaDiagDrops(Hsda Sessio nId Type ID,

HsdaDro pDia gType * pDropDia gList, UINT32 * pCount)
 HsdaStatus Type HsdaDiagSids(Hsd aSessio nId Type ID,

HsdaSidDia gTyp e * pSidDia gList, UINT32 * pCount)
 HsdaStatus Type HsdaRes etStatisticalAttribute(Hs daSe ssionIdTyp e

ID, HsdaStatistic alAttributeIdType attributeId);
 HsdaStatus Type HsdaStopLo gging(H sdaSe ssionIdTyp e ID)
 HsdaStatus Type HsdaShutdo wn()
Definitions:
#define HSDA_MAX _SIDS_ON_DROP 1000

#define HSDA_CONNECTIONS_M AX 10
typedef UINT32 HsdaSessio nId Type;
typedef UINT16 HsdaDro pId Type;
typedef UINT32 HsdaSidType;
OW351_R1100 95
5.21 BUFFER
// Represe nts the status of an HSDA operation

typedef union {
UINT16 wholeW ord;
struct
{
// Invalid session Id was provided as an argument

to a HSDA function call
UINT16 invalid_id:1;
// Invalid SID was provided by user or drop returned
data corresponding to an unregistere d SID
UINT16 invalid_sid:1;
// The drop rejecte d the connection because the
limit of the clients it can service simultane ously
was excee ded
UINT16 max_conn ectio ns_e xcee ded:1;
// Drop not communicating
UINT16 drop_u navailable:1;
// One of the points for the session was not found on the
Controller or it is occupied by another sessio n.
UINT16 point_una vailable:1;
// The buffer which the user provide d as an argument for a
HSDA
functio n call was too short
UINT16 buffer_too _short:1;
// Operating system error
UINT16 os_error:1;
// Buffer overflow on workstation side
UINT16 overflow:1;
// Problem with input sid for at least one algorithm
UINT16 input_sid_problem :1;
} bits;
} HsdaStatu sTyp e;
// The value for a status where no errors occurred

#define HSDA_OK 0
typedef union {
REAL32 analog;
INT32 digital;
UINT32 packed;
} HsdaValueT ype;
typedef struct {
HsdaValueTy pe pointValue;
INT32 timestam pSec onds;
INT32 timestam pNan osec onds;
INT32 firstStatus;
} HsdaBufferDataTy pe;
96 OW351_R1100
5.21 BUFFER
typedef union {
HsdaBufferDataTy pe bufferData;
} HsdaDataTy pe;
typedef struct {
Sid_type sid;
HsdaDataTyp e data;
} HsdaEve ntT ype;
typedef enum {
HSDA_SID_ OK,
HSDA_SID_ USED,
HSDA_SID_ NOT_FOUND,
HSDA_SID_ DROP_UNREACHAB LE
} HsdaSidStatu sType;
typedef struct {
Sid_type sid;
HsdaSidStatus Type sidStatus;
} HsdaSidDiagTyp e;
typedef enum {
HSDA_CONN_CONNECTED,
HSDA_CONN_DROP_UNAV AILA BLE,
HSDA_CONN_M AX_CLIENTS _EXCEEDE D,
HSDA_CONN_BACKUP_ NOT_READY,
HSDA_CONN_CONNECTING,
HSDA_CONN_UNSUPPORT ED_PROTO_ VERSION,
HSDA_CONN_UNKNOW N
} HsdaConn StatusT ype;
typedef enum
{
HSDA_ANALOG_TYPE,
HSDA_DIGITAL_T YPE,
HSDA_PACKED_TY PE,
HSDA_UNKNOWN_ TYPE
} HsdaPointData Type;
OW351_R1100 97
5.21 BUFFER
// Defines a type for drop diagnostic s

typedef struct {
// Ovation Network Drop Number of this drop
HsdaDro pId Type dropNum ber;
// TRUE if this drop reports as the active unit,
FALSE otherwise
BOOLEAN isActiv e;
// The status of the connection between the workstation
and this drop
HsdaConnStatusT ype connectionStatu s;
// Ovation Highway Drop Number of this drop's partner
HsdaDro pId Type partnerN um ber;
// The status of the connection between the workstation
and this drop's partner
HsdaConnStatusT ype partnerC onnectionStatus;
// The number of events which were transferred to the
application from this drop
UINT32 eventCount;
// The number of lost data packets
UINT32 lostPack etCount;
// TRUE if an overflow occurred in the local HSDA
event buffer (indicate s too slow collection by client
application), FALSE otherwis e
BOOLEAN bufferOv erflo w;
// Total number of processe d data frames
UINT32 totalFram es Count;
} HsdaDro pDia gTyp e;
// Represe nts the possible statistical attribute identifiers

typedef enum
{
// Identifier of unknown statistical attribute
HSDA_UNKNOWN_ ATTRIBUTE,
// Identifier of statistical attribute indicating
the number of events which were transferre d to the
application from this drop
HSDA_DROP_EVENT _COUNT,
// Identifier of statistical attribute indicating the
number of lost data packets
HSDA_DROP_LOST_ PACKET_ COUNT,
whether an overflow occurred in the local HSDA event
buffer
HSDA_DROP_BUFFE R_OVERFL OW ,
the total number of data frames proces sed
HSDA_DROP_TOTAL _FRAM ES_ COUNT,
} HsdaStatisticalAttributeIdTyp e;
98 OW351_R1100
5.21 BUFFER
API Usage
Note: In the following procedure, steps that contain the word "must" are required by the user
application. Steps that contain the word "may" are optional.
Perform the following steps to collect the data:
1. You must call HsdaStartup () to initialize the HSDA mechanism.

2. You may call HsdaSIDs () to get a list of BUFFER algorithm SIDs defined within a given
Controller and the respective input point SIDs.
3. You may call HsdaSIDtoName () to get the point name of a specific SID.
4. You must call HsdaStartLogging () with a list of points to collect. This runs connections with
all originating drops and their partners. The connection to the backup Controller in a
redundant pair may be established only after the connection to the active (in control)
Controller has been established.
5. You must periodically call HsdaData () to get a list of value change events. The period must
be fast enough to prevent queue overflow.
6. If any problems with connections were detected during the HsdaData () call, then you may
call HsdaDiagDrops () to determine drop statuses.
7. If any problems with points were detected during the HsdaData () call, then you may call
HsdaDiagSids () to determine point SID statuses.
8. If you want to reset a statistical value, then you may call HsdaResetStatisticalAttribute()
with the value of the attribute identified by attributeId.
9. If you want to stop collecting data, call HsdaStopLogging (), to close connections for a
certain session.
10. When the application is finished, you must call HsdaShutdown () to terminate all HSDA
activity
Note: The Hsda API does not handle applications that share one session across multiple
threads. The behavior of such applications may be unpredictable.
HsdaStatusType HsdaStartup() – Initializes Hsda API internals
HsdaStatusType HsdaSIDs(HsdaDropIdType originatingDrop, HsdaSidType* pSidList,

HsdaSidType* pInputSidList, HsdaPointDataType *pDataTypes, UINT32* pCount) – Gets the
list of SIDs which belong to collection algorithms on the drop whose ID/number is equal to
originatingDrop. The list is returned in pSidList and the number of written entries is stored in
pCount. To prevent overflow, the caller places the maximum number of entries that can be
returned into pCount (as well as pInputSidList and pDataTypes). If more buffer algorithm SIDs
exist on the originatingDrop, the buffer_too_short bit is set in the returned status. Additionally,
for every buffer SID found, the function attempts to resolve the SID of the input point connected to
the buffer, and its corresponding data type (one of Analog/Digital/Packed). They are stored
respectively in the pInputSidList and pDataTypes arrays, at the index which corresponds to the
buffer algorithm sid entry in pSidList. If there were problems resolving any input point SID or its
data type, the input_sid_problem bit is set in the returned status.
OW351_R1100 99
5.21 BUFFER
HsdaStatusType HsdaSIDtoName(HsdaSidType sid, char* buffer, UINT32* pCount) - Gets

the name field of a point based on the supplied sid and copies it to the buffer pointed to by buffer.
The number of bytes copied into buffer is returned in the variable pCount. No null terminating
character is appended. If there is an error while trying to resolve the name, the function returns a
status code of invalid_sid. If the name was retrieved, but the buffer supplied by the caller is too
short, a status of buffer_too_short is returned. Otherwise, if the name was successfully resolved
and the buffer length is sufficient, a status of HSDA_OK is returned and the name is copied into
the user-supplied buffer.
HsdaStatusType HsdaStartLogging(HsdaSidType * pSidList, UINT32 * pCount,

HsdaSessionIdType * ID) – Identifies a list of algorithms, by SID to collect data from. pSidList
points to the list of SIDs and pCount indicates the number of items in the list. Connection threads
are started on originating drop pairs. One application may have at most 10 connection sets to
drops originating SIDs. Returns HSDA_OK and sets session ID (a positive integer number) if
successful. If any of the SIDs is an invalid collection point (point that is not a valid BUFFER
algorithm LC record), pSidList will contain the list of invalid points, pCount will indicate how many
are in the list and the invalid_sid bit is set in the returned status – in this case the communication
is not started. If the function is being called more than 10 times in one application, without closing
connections, then the function returns a status code with the max_connections bit set and the
communication is not started.
HsdaStatusType HsdaData(HsdaSessionIdType ID, HsdaEventType * pEventList, UINT32 *

pCount, BOOLEAN * pMore) – Puts any received events, for a given session ID, into pEventList
and puts the number of written entries into pCount. To prevent overflow, the caller places the
maximum number of events that can be returned into pCount. Returns HSDA_OK if no problems
occurred. Returns a status with the invalid_id bit set if session with a given ID was not found. If
there were problems with the connection to any drop, then the drop_unavailable bit is set (for
example, a maximum number of connections to certain drops have been exceeded or there is a
connection problem). If there were problems with getting events for any point (for example, the
BUFFER algorithm point is missing) then the point_unavailable bit is set. If more events exist,
pMore is set to TRUE. The function tries to get as much data as possible, even if there were
problems with the connection to any drop or any point defined for the session was unavailable.
HsdaStatusType HsdaDiagDrops(HsdaSessionIdType ID, HsdaDropDiagType *

pDropDiagList, UINT32 * pCount) – Puts drop connection diagnostics (for given session ID) for
all drops into pDropDiagList and puts the number of entries into pCount. To prevent overflow, the
caller places the maximum number of drop connection diagnostics that can be returned into
pCount. Returns a status with the invalid_id bit set if the session with the given ID was not found.
If more drops are defined than what are defined in pCount, then the buffer_too_short bit is set in
the return status. Returns HSDA_OK if no problems occurred. Possible types of drop connection
statuses are:
1. HSDA_CONN_CONNE CTE D – connection to drop is active.

2. HSDA_CONN_DROP_UNAVA ILABLE – communication to drop could not be established (it
will be recreated as soon as possible).
3. HSDA_CONN_MA X_CLIE NTS_E XCEEDE D – drop reported that it has the maximum
connections opened (the connection will be recreated as soon as possible).
4. HSDA_CONN_BACKUP_NOT_READY – drop is in backup and did not receive a list of SIDs
for the connection from its partner.
5. HSDA_CONN_CONNE CTING – reconnecting to the drop.
100 OW351_R1100
5.21 BUFFER
6. HSDA_UNSUPPORTE D_P ROTOCOL_VE RSION – protocol version mismatch between drop

and station or drop responded in unexpected way.
7. HSDA_CONN_UNK NOW N – initial state of connection to certain drop – no connection to the
drop has been attempted.
Additionally, the drop diagnostic information includes the number of processed data frames, lost
network frames, a flag indicating whether the drop is active or in standby, and a flag indicating
whether an overflow occurred in the local Windows-side event buffers.
HsdaStatusType HsdaDiagSids(HsdaSessionIdType ID, HsdaSidDiagType * pSidDiagList,

UINT32 * pCount) – Puts SID diagnostics (for given session ID) of all defined SIDs for the
session into pSidDiagList and puts the number of entries into pCount. To prevent overflow, the
caller places the maximum number of SID diagnostics that can be returned into pCount. Returns
with the invalid_id bit set if the session with a given ID was not found. If more SIDs are defined
than are in pCount, then the maximum possible amount of data is received and the
buffer_too_short bit is set in the returned status. Returns HSDA_OK if no problems occurred.
Possible point error types are:
1. HSDA_SID_OK – There is no problem with receiving data for the point.

2. HSDA_SID_USED – There is already another connection on the originating drop that uses
the point (this is for avoiding the problem that some events for the point are received by one
application and some by another one). The SID is still added to the list of SIDs on the drop,
but is always recognized as already used, even if the situation changes and it is not used by
any other application connected to the drop.
3. HSDA_SID_NOT_FOUND – The given SID was not found on the active Controller.
4. HSDA_SID_DROP_UNREACHABLE – No connection to originating drop.
HsdaStatusType HsdaResetStatisticalAttribute(Hsda Se ssionIdType ID,

HsdaStatisticalAttributeIdType attributeId) - Resets the value of the attribute identified by
attributeId for all drops in the session whose identifier is equal to ID. The statistical attributes that
can be reset include the buffer event overflow flag, number of processed data frames, and
number of lost data frames.
HsdaStatusType HsdaStopLogging(HsdaSessionIdType ID) – Ends logging of the algorithms

associated with a given session ID and closes all of the associated connections. ID is no longer
valid at this point.
HsdaStatusType HsdaShutdown() – Cleans up HsdaAPI internals.
API Responsibilities
The HSDA Windows API is responsible for maintaining a connection to the HSDA servers,
automatic retrieval of HSDA event data from the network, detecting communication
failures/delays, and re-establishing the connection. For the purpose of keeping track of the
connection state, the API periodically checks for incoming messages (data, diagnostic, or
heartbeat) from each server. If no data is received over an extended period of time, a Start
Logging request is resent to the server. Once the server has successfully processed the Start
Logging request, it starts to periodically send HSDA event data over the network. No explicit 'Get
Data' request is sent from the client to the server, which reduces network traffic. The events
obtained from the network are stored in internal data buffers on the workstation side, for later
retrieval by the client using the HsdaData call.
Connections to drops are not shared between HSDA sessions. Each HSDA session has its own
connection to each drop from which it receives data.
OW351_R1100 101
5.21 BUFFER
Ovation Station and Controller communication
All communication between the Ovation Station and the Ovation Controller is performed using the
UDP protocol. If the Windows firewall is turned on, you must create an exception for the end
application. On the Ovation Controller, the HSDA task listens on port 4599 for connections from
the Ovation Station. The active (in control) Controller initiates a connection to the backup
Controller. The backup Controller listens on port 4678 for HSDA connections from the active
Controller. The active Controller tries to establish the connection to its partner once a second. The
active Controller also checks if the number of connections is less than the maximum number of
connections when a new connection attempt is made.
UDP Protocol Retransmission Mechanism

 The UDP version of HSDA makes use of two mechanisms to provide limited retransmission
capability.
 The first mechanism assigns sequence numbers to UDP frames containing HSDA event
data. This enables the workstation API to determine whether a given received packet is a
duplicate or not.
 The second mechanism buffers the data frames on the Controller side in a dedicated
queue. After a data frame is sent from the Controller, it is appended to the queue. If the
workstation does not acknowledge reception of this frame within a fixed time (currently
500 ms), the frame is retransmitted. There is a fixed amount of frame buffers available
(currently 200). If there are no free buffers and a frame needs to be sent out, the oldest
frame buffer (the one which was added to the queue the earliest) is used.
102 OW351_R1100
5.22 CALCBLOCK
5.22 CALCBLOCK
Description
The CALCBLOCK algorithm is designed to allow you to solve complex mathematical equations
within a control sheet. The CALCBLOCK algorithm supports any operation from the following list.
For more complex equations, CALCBLOCK algorithms can be cascaded together. Logical
operations are supported by the CALCBLOCKD algorithm (see page 112).
Each CALCBLOCK algorithm can support up to 18 inputs and 10 floating point constants.
Each CALCBLOCK algorithm can support up to 15 operations (in any combination). Each
operator has two arguments.
The intermediate result of each operation is stored in the Real Fields (1-15) of the algorithm
record. These intermediate results display in the tuning window of the monitor graphic and can
be used by the user to debug a calculation.
The result of the defined calculation is stored in the OUT point. If an invalid number (for example,
divide by zero, 1n (negative number), infinity, and so forth), occurs, the VALID output is set to
logical FALSE. If the calculation does not result in an invalid number, the VALID output is set to
logical TRUE.
The real constant fields are the only tunable fields in the algorithm. All editing must be performed
via the Control Builder.
The optional ENBL input allows the algorithm to be conditionally executed. If the input is
connected, the calculation is carried out only if the ENBL input is TRUE. If the ENBL input is
FALSE, the calculation is not performed, and the output is set to the previous value.
If the ENBL input is not connected, then there is no conditional execution, and the calculation is
performed each execution loop.
Note: The round function rounds to the nearest integer value. If the number falls midway, it is
rounded to the nearest value above (for positive numbers) or below (for negative numbers). For
example, round (1.5) = 2 and round (-1.5) = -2.
CALCBLOCK operations
M ATH E M A TI C AL S TAN D AR D S C I E N TI F I C
Add (a + b) *Square Root (sqrt(a)) *Cosine (Cos (a))
Subtract (a - b) *Reciprocal (recip(a)) *Sine (Sin (a))
Multiply (a * b) Max (max (a,b)) *Tangent (Tan (a))
Divide (a / b) Min (min (a,b)) *Arccos (arccos (a))
Power (a^b) *Negate (neg (a)) *Arcsin (arcsin (a))
OW351_R1100 103
5.22 CALCBLOCK
M ATH E M A TI C AL S TAN D AR D S C I E N TI F I C
*Square (square(a)) Remain (remain (a,b)) *Arctan (arctan (a))
*Cube (cube(a)) *Round (round a) *Natural Log (Ln (a))
*Truncate (trunc a) *Log base 10 (log10(a))
*Absolute value (abs a) *Antilog (antilog (a))
*Exp (exp(a))
(*) = Unary Operator (Takes only one argument.)
Functional Symbol
104 OW351_R1100
5.22 CALCBLOCK
FI E L D RE C .
DIAG LU-Byte Data Init. Optional 46 Tuning Diagram Number -
QBAD Y5-Byte Data Init Optional YES Bad Quality on Invalid -

Number
YES = Set output to bad
quality
NO = Do not set output to
bad quality
OPR1 X0-Byte Variable Required - Operand #1 -
OPR2 X1-Byte Variable Optional - Operand #2 -
OP10 X9-Byte Variable Optional - Operand #10 -
OP11 Y0-Byte Variable Optional - Operand #11 -
ARG1 G0-Integer Variable Required - Argument #1 -
ARG2 G1-Integer Variable Optional - Argument #2 -
OW351_R1100 105
5.22 CALCBLOCK
FI E L D RE C .
AR10 G9-Integer Variable Optional - Argument #10 -
AR11 B0-Integer Variable Optional - Argument #11 -
AR14 YU-Integer Variable Optional - Argument #14 -
AR21 C0-Integer Variable Optional - Argument #21 -
AR30 YT-Integer Variable Optional - Argument #30 -
RES1 R1-Real Variable - - Result of operation #1 -
RE10 S1-Real Variable - - Result of operation #10 -
106 OW351_R1100
5.22 CALCBLOCK
FI E L D RE C .
CON1 S7-Real Tuning Optional - Constant 1 -

Constant

Constant

Constant
CON4 T1-Real Tuning Optional - Constant 4 -

Constant

Constant

Constant

Constant

Constant

Constant
CO10 T7-Real Tuning Optional - Constant 10 -

Constant
ENBL - Variable Optional - Enable Calculations LD
IN1 - Variable Required - Input 1 LA
IN2 - Variable Optional - Input 2 LA
OW351_R1100 107
5.22 CALCBLOCK
FI E L D RE C .
OUT - Variable Required - Calculation result value LA
VALI - Variable Optional - Valid output flag LD
Example 1
The following example illustrates a single calculation.
Figure 1: Single calculation
108 OW351_R1100
5.22 CALCBLOCK
Algorithm parameter
A L G O R I TH M V AL U E S TE P S O L U TI O N
P AR AME T E R
IN1 T Not applicable
ENBL SIG1 Not applicable
CON1 459.67 Not applicable
CON2 1164.83 Not applicable
OPR1 + RES1 = IN1 + CON1
OPR2 / RES2 = RES1 / CON2
OUT Y Y = RES2
VALI SIG2 Not applicable
Example 2
The following example illustrates a multiple calculation.
This calculation is divided into two parts using two CALCBLOCK algorithms as follows:
OW351_R1100 109
5.22 CALCBLOCK
CALCBLOCK #1 solves equation:

(-2.0296177 + 0.33158207Y + 1.7158422Y 2 + 6.2354116Y 3 - 14.042987Y 4 + 7.3749399Y 5)
Algorithm parameter
A L G O R I TH M V AL U E I N TE R ME D I AT E S TE P S TE P S O L U TI O N
P AR AME T E R
IN1 Y Not applicable Not applicable
ENBL SIG1 Not applicable Not applicable
CON1 2.0296177 Not applicable Not applicable
CON7 4 Not applicable Not applicable
CON8 5 Not applicable Not applicable
OPR1 power RES1 = power (IN1, CON8) Y5

OPR2 power RES2 = power (IN1, CON7) Y4
OPR3 cube RES3 = cube (IN1) Y3
OPR4 square RES4 = square (IN1) Y2
OPR5 * RES5 = CON6 * RES1 7.374 * (Y5)
OPR6 * RES6 = CON5 * RES2 14.042 * (Y4)
OPR7 * RES7 = CON4 * RES3 6.235 * (Y3)
OPR8 * RES8 = CON3 * RES4 1.715 * (Y2)
OPR9 * RES9 = CON9 * IN1 0.331 * Y
OP10 negative RE10 = neg (CON1) -2.029
OP11 + RE11 = RE10 + RES9 (-2.029 + (0.331 * Y))
OP12 + RE12 = RE11 + RES8 ((-2.029 + (0.331 * Y)) +

(1.715 * (Y2)))
OP13 + RE13 = RE12 + RES7 ((-2.029 + (0.331 * Y)) +
(1.715 * (Y2)) + (6.235 *
(Y3)))
OP14 - RE14 = RE13 - RES6 (((-2.029 + (0.331 * Y)) +
(1.715 * (Y2)) + (6.235 *
(Y3)) - (14.042 * (Y4)))
110 OW351_R1100
5.22 CALCBLOCK
P AR AME T E R
OP15 + RE15 = RE14 + RES5 ((((-2.029 + (0.331 * Y)) +

(1.715 * (Y2)) + (6.235 *
(Y3)) - (14.042 * (Y4))) +
(7.374 * (Y5)))
OUT OUT OUT = RE15 Not applicable
VALI VALI Not applicable Not applicable
CALCBLOCK #2 solves equation:
(2.62068 x 10-5 / 0.000672) exp(OUT1)
Algorithm parameter
P AR AME T E R
IN1 OUT Not applicable Not applicable
ENBL VALI Not applicable VALI signal from CALCBLOCK #1
CON1 0.0389982143 Not applicable (2.62068 x 10 -5 / 0.000672)

OPR1 exp RES1 = exp (IN1) (exp IN1)
OPR2 * RES2 = CON1 * RES1 (0.0389982143 * (exp IN1))
OUT OUT OUT = RES2 Not applicable
VALI VALI Not applicable Not applicable
OW351_R1100 111
5.23 CALCBLOCKD
5.23 CALCBLOCKD
Description
The CALCBLOCKD algorithm is the digital version of the CALCBLOCK algorithm (see page 103).
CALCBLOCKD can only perform logical functions. The list of functions is outlined in the following
table. For more complex calculations, CALCBLOCKD algorithms can be cascaded together.
Logical
L O G I C AL
And (a && b)
Nand (a ^& b)
Or (a || b)
Nor (a ^| b)
Xor (a xor b)
Not (not a)
Each CALCBLOCKD algorithm can support up to 18 inputs and 10 floating point constants. Each
CALCBLOCKD algorithm can support up to 15 of the above operations (in any combination).
Each operator has two arguments.
The intermediate result of each operation is stored in the Real Fields (1-15) of the algorithm
record. These intermediate results display in the tuning window of the monitor graphic and can be
used by the user to debug a calculation. The result of the defined calculation is stored in the OUT
point. If an invalid calculation occurs, the VALID output is set to logical FALSE. If the calculation
does not result in an invalid number, the VALID output is set to logical TRUE.
The real constant fields are the only tunable fields in the algorithm. All editing must be performed
via the Control Builder.
The optional ENBL input allows the algorithm to be conditionally executed. If the input is
connected, the calculation is carried out only if the ENBL input is TRUE. If the ENBL input is
FALSE, the calculation is not performed, and the output is set to the previous value. If the ENBL
input is not connected, then there is no conditional execution, and the calculation is performed
each execution loop.
112 OW351_R1100
5.23 CALCBLOCKD
Functional Symbol
FI E L D RE C O R D
DIAG LU-Byte Data Init. Optional 46 Tuning Diagram -

Number
OPR1 X0-Byte Variable Required - Operand #1 -
OP10 X9-Byte Variable Optional - Operand #10 -
OW351_R1100 113
5.23 CALCBLOCKD
FI E L D RE C O R D
ARG1 G0-Integer Variable Required - Argument #1 -
AR10 G9-Integer Variable Optional - Argument #10 -
AR14 YU-Integer Variable Optional - Argument #14 -
114 OW351_R1100
5.23 CALCBLOCKD
FI E L D RE C O R D
AR30 YT-Integer Variable Optional - Argument #30 -
RES1 R1-Real Variable - - Result of operation -

#1
#2
#3
#4
#5
#6
#7
#8
#9
RE10 S1-Real Variable - - Result of operation -
#10
#11
#12
#13
#14
#15
Constant

Constant

Constant

Constant
OW351_R1100 115
5.23 CALCBLOCKD
FI E L D RE C O R D

Constant

Constant

Constant

Constant

Constant
CO10 T7-Real Tuning Optional - Constant 10 -

Constant
ENBL - Variable Optional - Enable Calculations LD
IN1 - Variable Required - Input 1 LP
IN2 - Variable Optional - Input 2 LP
OUT - Variable Required - Calculation result LP

value
VALI - Variable Optional - Valid output flag LD
116 OW351_R1100
5.23 CALCBLOCKD
Example
The following example illustrates a single calculation:
A = NOT(IN1) && (IN2 XOR IN3)
Figure 2: Single calculation
A L G O R I TH M P AR AM E TE R V AL U E S TE P S O L U TI O N
IN1 I1 Not applicable
ENBL SIG1 Not applicable
OPR1 NOT RES1 = not(IN1)
OPR2 XOR RES2 = xor(IN2, IN3)
OPR3 AND RES3 = and(RES1, RES2)
OUT A A = RES3
VALI SIG2 Not applicable
OW351_R1100 117
5.24 COMPARE
5.24 COMPARE
Description
The COMPARE algorithm compares the value of IN1 with the value of IN2, and the appropriate
output is set TRUE.
Invalid Real Numbers
Analog input values are checked for invalid real numbers. If the input value is invalid, the output
points are set to FALSE.
Functional Symbol
FI E L D RE C O R D

(analog)
(analog)
OUT - Variable Required - IN1 equals IN2 LD
(digital)
OUTG - Variable Required - IN1 Greater LD
than IN2
(digital)
OUTL - Variable Required - IN1 Less than LD
IN2 (digital)
ENBL - Input Optional - When this LD
input is true,
IN1 is
compared to
IN2, and the
appropriate
output is set
TRUE.
118 OW351_R1100
5.25 COSINE
5.25 COSINE
Description
The COSINE algorithm performs the mathematical cosine function. COSINE has one input and
one output analog point. Each time the algorithm is executed, if the output is on scan, it is set to
the COSINE of the input. The input to this algorithm is in radians. If an input is only available in
degrees, multiply it by 0.01745329 to convert to radians.
If the absolute value of the input is greater than 10 18, then the output of the COSINE algorithm is
invalid and its quality is set to BAD.
Functional Symbol
FI E L D RE C O R D
Function
OUT=COSINE(IN1)
OW351_R1100 119
5.26 COUNTER
5.26 COUNTER
Description
The COUNTER algorithm counts up or down based on the input DIRECTION for the direction to
count. If DIRECTION (DRCT) is INC (one), the counter increments, otherwise it decrements.
While the ENABLE (ENBL) is TRUE, the count increments or decrements by one for each scan
that the IN1 input is TRUE.
If the COUNTER increments, the ACTUAL (ACT) continues to increment even if it is greater than
the TARGET (TARG). If the value stored in ACT reaches the maximum value (16,777,216), it
remains unchanged. The OUT is set TRUE when ACT is equal to or greater than TARG.
If the COUNTER decrements, it starts decrementing from the TARGET value. If the value stored
in ACT reaches the minimum value (-16,777,216), it disregards the IN1 input and remains at the
minimum value. The OUT is set TRUE when ACT is less than or equal to zero.
If either TARG or ACT is invalid, no operation occurs and OUT is set to FALSE. If ENBL is
FALSE, then ACT is set to zero when the COUNTER algorithm is configured to count up or set to
preset.
Functional Symbol
N AME LC A L G . T YP E RE Q U I R E D / D E F AU L T DE S C R I P TI O N MI N .
FI E L D RE C .
DIAG LU-Integer Data Required 1 Tuning Diagram -

Number
Init
IN1 - Variable Required - Start Input Digital LD, LP
ENBL - Variable Required - Enable Input Digital LD, LP

DRCT X1-Byte Data Init Required 0 Count Direction: -
DEC = Decrement
INC = Increment
120 OW351_R1100
5.26 COUNTER
FI E L D RE C .
*TARG R1-Real Selectable Required 0.0 Count Target LA

Number
*ACT R2-Real Selectable Required 0.0 Actual Count LA
Output
OUT - Variable Required - Count Complete LD, LP
Output
* When a parameter type is defined as "Selectable" and marked as "Required," the Con trol Builder may
default the parameter to a value and mark it as "Optional." However, for the control function to be
executed properly, you must enter a value for the parameter.
Example
Function
OW351_R1100 121
5.27 DBEQUALS
5.27 DBEQUALS
Description
The DBEQUALS high/low comparator algorithm monitors two analog input values. If the absolute
value of the difference between the signals exceeds the deadband value, the digital output is set
TRUE. If the absolute value of the difference between the signals is less than the absolute value
of the difference between DBND and RTRN, then the output is set FALSE.
Both analog input values are checked for invalid real numbers. If one of the input values is invalid,
the value of the output is invalid and its quality is set to BAD. If all the inputs are valid, the worse
quality among the inputs is propagated to the output.
Functional Symbol
FI E L D RE C .

Number
DBND R1-Real Tuning Required 0 Deadband -
Constant
RTRN R2-Real Tuning Optional 0 Deadband return -

Constant delta parameter

122 OW351_R1100
5.27 DBEQUALS
Function
TEMP = IN1 - IN2

IF ABS(TEMP) DBND
THEN OUT = TRUE
IF OUT = TRUE
THEN IF ABS(TEMP) <ABS(DBND - RTRN)
THEN OUT = FALSE
where:
TEMP = local, temporary, real variable
OW351_R1100 123
5.28 DEVICE
5.28 DEVICE
Description
The DEVICE algorithm combines the commands to open/close/stop or start/stop a piec e of

equipment with feedback signals indicating the command was accomplished. Devices allow
controlled access of the equipment they own and simplify the operation of the equipment. For
example, when an operator wants to close a large motor-driven valve, he could watch the
open/close verify contact signals and manually toggle the close contact output until the closed-
confirm is received or an excessive amount of time has passed. Conversely, if the Controller
takes over for the operator, the command is simpler (that is, the Controller closes the valve). This
algorithm provides digital outputs that reflect how the I/O outputs of the device are being
maintained and the different status/mode conditions of the device.
The DEVICE algorithm responds to the following signal combinations:
 One digital output and no feedback.

 One digital output and one digital feedback.
 Two digital outputs and two digital feedbacks.
 Two digital outputs and one feedback.
 Three digital outputs and two feedbacks.
One Digital Output and No Feedback
With one output and no feedback, the DEVICE algorithm sets the device to a defined state (on,
off, start, stop, open, close) when commanded.
124 OW351_R1100
5.28 DEVICE
One Digital Output and One Digital Feedback
With one output and one feedback, the DEVICE algorithm can set the output to a defined state,
set the “In Transition” bit (A2 field of bit 1 of the device record), and then monitor the input. If the
input's state does not match the output state within a user- specified amount of time, the device
indicates a failed operation has occurred. If the feedback indicates the desired state is reached
within the user-specified time, the device sets its current state field to the appropriate value. In
either case, the In Transition bit resets at the end of the operation.
OW351_R1100 125
5.28 DEVICE
Two Digital Outputs and Two Digital Feedbacks
With two digital outputs and two digital feedbacks, the DEVICE algorithm can set the appropriate
output to “1” or ON and wait for the appropriate feedback to be true. When the appropriate
feedback indicates true, the device sets its current state field to the appropriate state. If the
feedback does not indicate the appropriate state is reached within the user-specified time, the
device status display indicates a failed operation.
126 OW351_R1100
5.28 DEVICE
Two Digital Outputs and One Digital Feedback
With two digital outputs and one feedback, the DEVICE algorithm can set the appropriate output
to “1” or ON and wait for the feedback to go to the desired state. When the feedback indicates the
new state, the device sets its current state field to the appropriate state. If the feedback does not
indicate the appropriate state was reached within the user-specified time, the device indicates a
failed operation.
OW351_R1100 127
5.28 DEVICE
Three Digital Outputs and Two Digital Feedbacks
With three outputs and two feedbacks, the algorithm can set the appropriate output to “1”
according to the OPEN/CLOSE, START/STOP, or STOP TRAVEL command requested. If the
request is an Open or Close command, the feedbacks are monitored to see if the new state is
reached. When the feedbacks indicate the new state, the device's current state bit is updated to
the appropriate state. If the feedbacks do not indicate the appropriate state within the user-
specified time, the device indicates a failed operation. If the command is a Stop Operation
request, the algorithm writes a “1” to the Stop Travel output and indicates that the device is
stopped.
128 OW351_R1100
5.28 DEVICE
Control Operation
If the state of the I/O is indeterminate (that is, when both input status bit s are equal to 1, or both
are equal to zero and the device is not being commanded to another state), the Sensor Failure bit
(bits 2 and 3 of the 1W field in the DVCE point) is set. Note, that once a device is commanded to
another state, the “In Transition” status is set true as soon as the algorithm starts driving the
device to the commanded state. The “In Transition” status is reset when the device feedback
indicates the new state, and the operation is successful. If the operation fails, and the device
indicates it is neither open nor closed (both bits of the feedbacks are zero or one), the “In
Transition” status remains set and the Input Sensor Failure bit is not set. However, the Operation
Failed bit (bit 2 of the A2 field of the DVCE point) is set.
The device with two feedbacks may also be configured to display a “Failure to Respond” status. If
you configure the device to have a response time, the failure occurs if both feedbacks are not at a
zero (clear) state within the defined response time. If a “Failure to Respond” occurs, there is no
“Operation Failure” since the algorithm waits for a new command to process following the
response failure.
In the event of “Failure to Respond”, OUTPUT1, OUTPUT2, and OUTPUT3 all equal zero. In this
case, OUTPUT1 represents OPEN/START/ON bit, OUTPUT2 represents CLOSE/STOP/OFF bit,
and OUTPUT3 represents STOP (TRAVEL) bit.
In the event of “Failure to Operate,” OUTPUT1, OUTPUT2, and OUTPUT3 equal zero, as if
“Failure to Respond.” After any “Failure to Operate” or “Failure to Respond,” the OUTPUTs are
always zero.
The digital inputs and outputs used by the DEVICE algorithm can either be signals read from or
written to I/O cards, other digital process points contained in the system, or a combination of the
two.
Whenever a device experiences a failed operation (or response failure), it may ignore additional
requests for state changes or it may continue servicing such requests, depending on how the
device is configured (bit 4 of MODE parameter). You may want a DEVICE algorithm t o ignore
further requests after a piece of equipment has failed in order to prevent further damage to the
equipment. Regardless of how a device is configured, it services at least one request subsequent
to each change of operating mode (for example, Auto Mode to Manual Mode). If the device is
configured to ignore requests after a failure, it displays the status “LOCKOUT” when a failed
operation (or response failure) occurs.
Control Modes
A device is put into one of three modes by the operator by pressing the appropriate control key
(located on the Control Panel or Ovation Keyboard) or specified function key (located on a
standard keyboard). Note that the device must be configured to operate in that mode. Therefore,
the DEVICE has three modes of operation that can be adjusted during monitoring. These modes
are as follows:
 AUTO
 MANUAL
 LOCAL
OW351_R1100 129
5.28 DEVICE
Auto Mode
Auto Mode allows the Controller application program to control the device through user-
programmed logic. The device cannot go into Auto mode unless one or both of the following
conditions are true:
 The “Auto Permissive” bit is true.
 The device is configured so that its default mode (bit 7 in MODE parameter) is Auto.
Once either of the above conditions is satisfied, and the device is not in Local mode, the device
can enter Auto mode if:
 The operator presses the Auto mode request key.
 An Emergency Override occurs and the device's default mode is Auto.
 The Local Mode input goes false after being true, and the device's default mode is Auto.
 The default mode is Auto, and the DEVICE algorithm is in its first pass.
The device exits Auto mode whenever one of the following happens:
 The operator presses the Manual Mode Request key.
 The operator Tags Out the device.
 The “Auto Permissive” bit (bit 5 of the C5 field of the command word) goes False and the
default mode is not Auto mode (the device goes to Manual mode).
 Local Mode is commanded through the optional LRE input.
 Emergency Override occurs and the device's default mode is Manual (occurrence of an
override forces the mode to Manual).
The device may be configured (Bit 6 of MODE parameter) to go to Manual mode when a change
of state command is entered. If this is the case, pressing the following control keys causes the
device to go to Manual mode:
 Start/Open/Trip.
 Stop/Close/Reset.
 Stop Travel (discontinue operation in progress).
When in Auto Mode, the DEVICE algorithm accepts commands from the digital process points
that are linked to the device through the DEVICE algorithm. Possible commands are:
 Emergency OPEN/START Override.
 Emergency CLOSE/STOP Override.
130 OW351_R1100
5.28 DEVICE
Manual Mode
Manual Mode of operation allows the operator to control the device with the control keys. The
device goes into this mode when one of the following occurs:
 The operator requests Manual mode by pressing the Manual Mode request key.
 In Auto mode, the “Auto Permissive” bit (bit 5 of the C5 field of the command word) goes false
and the device default mode is not Auto.
 Upon startup of the Controller, if the default mode of the device is Manual.
 Occurrence of an Emergency Override and the default mode of the device is Manual, or in
Local mode, the hardware field input goes false and the default mode of the device is Manual.
The device may be configured to go to Manual mode when an Engineer Station or Operator
Station change of state command is entered. If this is the case, pressing the following control
keys causes the device to go to Manual mode:
The device exits Manual mode whenever one of the following happens:
 Local Mode is commanded through the optional LRE (reject to local) input.
 The operator requests Auto Mode (and the “Auto Permissive” bit is set or Auto is the device's
default mode), or the operator requests the device to be Tagged-Out with the appropriate
control key.
When in Manual Mode, the DEVICE algorithm executes the Emergency Override to the device
only if the device is configured (see bit 0 in MODE parameter) so that the overrides have
precedence over the operator's commands.
Local Mode
Local Mode is the lowest level mode of operation for the device. A device can enter this mode
only if the following two conditions are met:
 The device is configured to monitor the LRE input that indicates a local mode is active.
 The LRE point is in the set (true) state.
When this point goes true, the device immediately goes into Local Mode and stays in this mode
until the following occurs:
 The LRE point is reset (goes false).
As long as the LRE point is true, the device does not accept any commands from the Auto and
Manual modes. It does however, report the current state of the device. Device Trips, Sensor
Failures, and Failed Operations cannot be determined when in Local Mode; therefore, these
conditions are not checked for or reported when in Local Mode.
When the device goes into Local Mode, inputs are read and outputs are not energized; they are
left as they were when device went into Local Mode. When the device leaves the Local Mode, the
device goes to its default mode AUTO or MANUAL as defined by bit 7 in MODE parameter. If
input sensors cannot be determined (both = 0, or both = 1) and the device has not been
commanded to change state, all three outputs equal zero.
OW351_R1100 131
5.28 DEVICE
Mode Independent Commands
There are several commands that are requested with keys and are executed if the device is in
Auto or Manual mode. These commands are:
 Set “Override Failure” flag (Disable Lockouts).
 Clear “Override Failure” flag (Enable Lockouts).
 Tag Out the Device.
 Acknowledge Trip.
 Auto mode request.
 Manual mode request.
These commands are not accepted, however, if the device is in Local mode or is tagged-out.
Maintenance Modes
Tag Out
When in Tag Out Mode, the device ignores all commands except “Remove Tag Out.” The device
goes to its default mode when the Tag Out is removed.
Lock Out
A subset of the Tag Out Mode is the device “LOCK OUT” mode. Lock out occurs if the device is
configured (see bit 4 MODE parameter) to ignore subsequent commands to change state after an
operation fails. In other words, the device has only one opportunity to change state in a particular
mode. If the operation fails, the DEVICE algorithm does not accept another Open/Start or
Close/Stop command while locked out.
A device may be removed from Lock Out by any of the following actions:
 Pressing the Auto or Manual mode request keys.
 Setting the failure override flag (disabling lockouts) via the appropriate key.
 Tagging out the device.
 Control being transferred to Local mode (the LRE point goes true).
When returning from Lock Out, variables OUT1, OUT2, and OUT3 equal zero.
Change of State
In general, a change of state command in progress is continued until the device reaches the new
state or until a time out occurs. The following conditions cause an operation in progress to be
discontinued:
 The device is Tagged Out, resulting in inputs being read and outputs not energized, left as
they were at the time of Lock Out.
 The device goes to Local mode, resulting in inputs being read and outputs not being
energized, left as they were when device went to Local Mode
 A Stop (discontinue operation) command is requested by the current control mode and an
Emergency Override is not in progress. If the device is in Manual mode, however, and it is
configured so the Emergency Overrides do not have priority over Manual commands, a
Manual Stop request overrides the Emergency command.
132 OW351_R1100
5.28 DEVICE
In order for a change of state command to be executed, its proper permissive must be true. For
example, a Manual Close/Stop command only executes if the Close/Stop permissive of the device
is true. The Emergency Override and Stop (discontinue operation) commands do not require any
permissive to be true in order to be executed.
The permissives of a device are set true on start-up and remain true unless the DEVICE algorithm
is used to update them.
You can set the amount of time that a device allows for the equipment to change state following a
command. You must specify the units of time (0.1 seconds, seconds, or minutes) to measure
transition time, and the maximum number of time units to get to the set and reset states. You can
also specify a time period (in loops) for the equipment to respond to a command.
For devices with feedback, you can also configure the amount of time that the DEVICE algorithm
sets the appropriate output “ON”. The following modes are supported:
 Set output “ON” for a user-configured time period (less than the transition time), or until the
new state is reached, whichever occurs first. (Setting bit 1 of MODE parameter indicates this
mode.)
 Set output “ON” for a user-configured time period (equal to the transition time) or until the new
state is reached, whichever occurs first. (Indicate this mode by setting bit 2 of the MODE
parameter.)
 Maintain output “ON” continuously, until a new command is given. This mode also has a time-
out associated with it, but the pulsing continues after the time-out occurs. If the operation fails
(device does not reach the commanded state) the operation is flagged as a failure, and the
pulsing is discontinued until a new command is given. (This mode is indicated by bit 3 of the
MODE parameter.)
For the case where the device has only one output (no feedbacks), the output is set to “ON” (or
“OFF”) continuously depending on whichever command is requested. There are no time-outs for
this case.
A device always writes to its output(s) when a new change of state command occurs regardless
of the state of its input(s). If the device command is from other application logic, care should be
taken to ensure that the command is maintained or pulsed as needed.
The device continuously checks for change of state commands when it is not in the process of
executing one. The device executes a change of state command when it is first set “ON.” If the
command stays “ON,” the device treats it as a new command when it finishes executing the last
command. Since the device writes to its output(s) when a new command occurs, its output(s)
cycle continuously “ON” and “OFF” if the following are true:
 A change of state command is “ON” and it matches the state of the device's input(s).
 The device is configured to set its output(s) “ON” for a certain amount of time, then “OFF.”
Emergency Overrides
In addition to the change of state commands, in each of the operating modes there are two other
commands: Emergency Start/Open/Trip and Emergency Stop/Close/Reset.
These two commands are generated by external logic in the Controller and can act as emergency
overrides over all other commands, including Stop Travel.
OW351_R1100 133
5.28 DEVICE
Whenever either the Emergency Open, or Emergency Close input becomes true, the DEVICE
algorithm forces the device to its default state and attempts to get the device to the commanded
state. (If the DEVICE algorithm is not configured to ignore failures, t he emergency command
executes only once.) If both emergency overrides are set at the same time, the device remains on
its present course of action. Any occurrence of an override forces the device to its default mode.
As long as either Emergency input is set, the DEVICE algorithm ignores all Auto commands to
drive the device. The device may also be configured to have the Emergency inputs override the
Manual commands or the Manual commands override the Emergency inputs. Upon removal of
the emergency override, the device returns to servicing commands of its default mode.
Note: Emergency overrides, lik e all other commands, are ignored when the device is tagged out
or in Local Mode.
Alarming
The DEVICE algorithm supports seven types of alarms. All of these alarms , except Trips, require
operator acknowledgment. The device conditions which can produce alarms are:
 Failed Operations.
 Failures to Respond.
 Trips.
 Alarm State.
 Sensor Failures.
 Emergency Overrides.
 Attention (Trouble).
Failed Operations
If the Failed Operations alarm is configured, the DEVICE algorithm puts the device in alarm
whenever the equipment does not complete a change-of-state command (for example, if a valve
is commanded to open and it does not do so within the user-specified time). A Failed Operation
Alarm clears upon the next Open, Close, or Stop command to the device.
Failure to Respond
If the Failure to Respond alarm is configured, the DEVICE algorithm puts the device into alarm if
the feedbacks do not reflect an “In Transition” state within a user-specified number of loops. The
“In Transition” state must be that both feedbacks have a value of 0.
Trips
If Trip alarms are configured, the DEVICE algorithm puts the device into alarm whenever the
equipment unexpectedly changes state (for example, when a breaker trips open). A Trip Alarm
clears when you acknowledge the Trip by commanding the device to the Tripped state. Trip Alarm
returns do not require acknowledgment by the user.
Alarm State
The device can be configured to go into alarm based on a us er-defined state. The alarm clears
only when the device returns to the non-alarmed state. These alarms must be acknowledged by
the user.
134 OW351_R1100
5.28 DEVICE
Sensor Failures
A Sensor Failure alarm is caused by either or both of the following conditions:

 The device feedbacks are indeterminate (that is, both show a 00 or 11 status) and the device
is not in transition. This is an input sensor alarm.
 The outputs do not reflect the value written to them (output sensor alarm).
Emergency Override
The Emergency Override alarm is generated any time an override occurs and the device is not at
the override state. For example, the occurrence of an Emergency Open would generate an alarm
if the device is Closed. If both override inputs happen to become true at the same time, an alarm
is generated regardless of the state of the device.
Attention
The Attention (Trouble) alarm is caused by different conditions depending on how the device is
configured. Currently, the standard DEVICE algorithm does not generate an ATTENTION alarm.
If the device is configured to alarm a combination of conditions, the points are put into alarm when
either one or more of the alarm conditions exist.
The following alarming options are available:

 No Alarming.
 Failed Operations, Sensor Failures, Trips, Response Failures, Attention conditions, and
Emergency Overrides.
 Failed Operations, Sensor Failures, Trips, Response Failures, Attention conditions,
Emergency Overrides, and Alarm State.
Clearing Alarms
Upon Tagging Out, Scan Removing, or putting a device into Local mode, t he following alarms are
cleared:
 Failed Operation.
 Failure to Respond.
 Sensor Failures.
 Trips.
 Attention.
A State Alarm, however, is not cleared by any of the conditions mentioned above. It must be
cleared by commanding the device.
Tagging out or going to Local mode clears any Emergency Override present.
OW351_R1100 135
5.28 DEVICE
Device Status Reporting

The device record maintains information corresponding to the current status of a device.
Depending on the state of a device, its displayed status includes a combination of the following
conditions:
 Current State.
 In Transition.
 Operation Failed.
 Failure to Respond.
 Tripped.
 Stopped.
 Emergency Close.
 Emergency Open.
 Current Mode.
 Override Failure.
 Scan Removed.
 Alarm Checking Off.
 Tagged Out.
 Locked Out.
 Quality.
The status information mentioned above comes from various flags (bits) in certain fields in the
packed point and algorithm record.
The A2 field of the Packed point (DVCE) has the following information:
A2 Field Bit Information
BI T D E S C R I P TI O N
Bit 0 Current State. This bit indicates the current state of the feedback signals. In case feedback
signals give conflicting data, the last known state is reported. When scan removed, the last
command state is reported.
Bit 1 In Transition. This bit indicates the device algorithm is currently in the process of trying to
change the state of its equipment. The bit is set true when the device starts to execute a
command. It is reset when the feedback signals indicate the operation is complete or the
operation has failed.
Bit 2 Operation Failed. This bit is set following any unsuccessful attempt to change the state of
the equipment. It remains set until the next attempt is made to change the state of the
equipment. Failed operation is not indicated if the device is scanned off.
Bit 3 Tripped. This bit is set any time the equipment changes state on its own, not by the
algorithm. It remains set until the Trip Acknowledge command is received. If it is not
acknowledged, no other change of state operations, in any mode, is processed. The tripped
bit is not set when the device is Tagged Out or Scanned Removed.
Bit 4 Stopped. This bit is set whenever the device is commanded to stop. The bit remains set
until the next attempt is made by the device to change the state of the equipment.
Bit 5 Emergency Close. This bit reflects the status of the override inputs to the device.
136 OW351_R1100
5.28 DEVICE
Bit 6 Emergency Open. This bit reflects the status of the override inputs to the device.
Bit 7 Last Commanded State. This bit reflects the last known state of the device.
Bit 8 Local Mode. This bit indicates that the device is in local mode.
Bit 9 Manual Mode. This bit indicates that the device is in manual mode.
Bit 10 Auto Mode. This bit indicates that the device is in auto mode.
Bit 11 Reserved.
Bit 12 Attention. This bit indicates certain error conditions are present.
Bit 13 Failed to Respond. This bit indicates that the device did not respond to a command.
Bit 14 Locked Out. This bit indicates that the state of the device is locked out.
Bit 15 Tagged Out. This bit indicates that the state of the device is tagged out.
The C5 field in the device algorithm holds the command word. This command word is the
interface between a Controller and a device. The bits in the C5 field are defined in the following
table:
C5 Field Bit Information
Bit 0 Emergency Close/Stop.
Bit 1 Emergency Open/Start.

Bit 2 Auto Close/Stop/Reset.
Bit 3 Auto Open/Start/Set.
Bit 4 Stop.
Bit 5 Auto Permissive.
Bit 6 Current State of Input 1 (Open/Start).
Bit 7 Current State of Input 2 (Close/Stop).
Bit 8 Current State of Input 3 (Stop).
Bit 9 Value currently being written to Output 1 (Open/Start).
Bit 10 Value currently being written to Output 2 (Close/Stop).
Bit 11 Value currently being written to Output 3 (Stop).
Bit 12 Close/Stop permissive.
Bit 13 Open/Start permissive.
Bit 14 Local Reject.
OW351_R1100 137
5.28 DEVICE
Setting Device Parameters
Alarming
The following fields in the Packed point (DVCE) must be set for alarming:
Alarming Parameters
T YP E OF A L AR MI N G FI E L D S TO B E SET
No Alarming Set E0 and E1 to zero.
Operate, Sensor, Trips, Overrides and Attention Set E0 and E1 to 0x386c.

Operate, Sensor, Trips, Overrides and Attention, State Set(1) Set E0 and E1 to 0x386d.
Operate, Sensor, Trips, Overrides and Attention, State Set(0) Set E0 to 0x386d and E1 to 0x386c.
The C4 field in the algorithm record defines the mode configuration. The bits in the C4 field are
defined in the following table:
BI T MOD E DE S C R I P TI O N
Bit 0 Off The emergency Open/Start and Close/Stop commands override

Auto commands.
On The Emergency Open/Start and Close/Stop commands
override all other commands.
Bit 1 * On Set output 'ON' for a configured time period (less than the time -
out). If this bit is set, the algorithm maintains the appropriate
output for the number of loops in the Pulse Time or until the
operation is successful, whichever occurs first.
Bit 2 * On Set output 'ON' until a user-configured time-out (or the
operation is successful). The transition times for setting and
resetting the device are entered in the Set Time-out and Reset
Time-out fields.
Bit 3 * On Set output 'On' continuously until a new command is entered.
Bit 4 On Disable lock-outs. If this bit is set, the device does not go into
Lock Out mode when a failed operation occurs .
Bit 5 On Do not execute the STOP TRAVEL command.
Bit 6 Off Manual Open/Close/Stop commands force the device to
Manual mode.
On Manual Open/Close/Stop commands are processed only it the
device is in Manual mode.
Bit 7 Off Device default mode is Manual.
On Device default mode is Auto.
* Bits 1, 2, and 3 are not meant to b e used together. Only one of these b its should b e used at a time.
Also, these options apply to START/OPEN and STOP/CLOSE commands only. The STOP TRAVEL
command uses Bit 3 regardless of what is selected.
138 OW351_R1100
5.28 DEVICE
The C7 field in the algorithm record defines the emergency Open/Close configuration. The bits in
the C7 field are defined in the following table:
Bit 0 Not Used Not used.

Bit 1 Off Place the DEVICE algorithm in Local mode when:
 The LRE point is TRUE.
 Bit 2 of the C7 field is 1 and the LRE is TRUE.
On Place the DEVICE algorithm in Local mode when:
 The LRE point is FALSE.
 Bit 2 of the C7 field is 1 and the LRE is FALSE.
Bit 2 Off The LOC point is used to indicate the device is in Local mode.
On The LRE point is used as a “local mode request.”
Bit 3 Off The EMOP (Emergency Open) input is NOT inverted.
On The EMOP (Emergency Open) input is inverted.
Bit 4 Off The EMCL (Emergency Close) input is NOT inverted.
On The EMCL (Emergency Close) input is inverted.
Bit 5 Off The Trip Acknowledge action causes a command to the output(s)
based on the current feedback state.
On The Trip Acknowledge action does NOT cause a command to the

output(s).
Bit 6 Off The OPRM (Open Permissive) does NOT apply to the EMOP
(Emergency Open) input.
On The OPRM (Open Permissive) does apply to the EMOP

(Emergency Open) input.
Bit 7 Off The CPRM (Close Permissive) does NOT apply to the EMCL
(Emergency Close) input.
On The CPRM (Close Permissive) does apply to the EMCL

(Emergency Close) input.
OW351_R1100 139
5.28 DEVICE
Functional Symbol
FI E L D RE C O R D
DIAG LU - Data Init Required 121 Tuning diagram -

number.
Integer
SET D2 - Data Init. Required 20 Set time out -
(maximum of
Integer
255 if units are
tenth of a
second or
seconds.
Maximum of 100
minutes if units
are minutes).
RSET YT - Data Init. Required 20 Reset time out -
(maximum of
Integer 255 if units are
tenth of a
second or
seconds.
Maximum of 100
minutes if units
are minutes).
MODE C4 - Data Init. Required 9 Mode -
information.
Integer
EMRG C7 - Data Init. Required - Emergency -
open/close.
Integer
PT D4 - Data Init. Required - Pulse time. -
Integer
140 OW351_R1100
5.28 DEVICE
FI E L D RE C O R D
TR YP - Data Init. Required 0 Time response. -

Integer
TU DO - Data Init. Required 1 Units time out. -
Value time units:
Integer
0 = tenth of a
second
1 = seconds
2 = minutes
TYPE C8 - Data Init. Required Open/Close Device type. -
The choices are:
Integer
- Open/Close
- Start/Stop
OPRM - Variable Optional - Input (digital); LD, LP
OPEN
PERMISSIVE,
allows
OPEN/START
commands to be
honored.
CPRM - Variable Optional - Input (digital); LD, LP
CLOSE
PERMISSIVE;
allows
CLOSE/STOP
commands to be
honored.
IN1 - Variable Optional - Input (digital); LD, LP
feedback. If the
value is TRUE,
the device is
OPEN/ON.
IN2 - Variable Optional - Input (digital); LD, LP
feedback. If the
value is TRUE,
the device is
CLOSED/OFF.
IN3 - Variable Optional - Input (digital): LD, LP
Auto mode
request
DVCE point
goes to Auto
mode when IN3
is TRUE, AUTP
IS TRUE.
OW351_R1100 141
5.28 DEVICE
FI E L D RE C O R D
LRE - Variable Optional - Input (digital); LD, LP

Local reject
When EMRG Bit
2 = 1, point is
used as the
“local mode
request.”
AUTP - Variable Optional - Input (digital); LD, LP
AUTO
PERMISSIVE;
allows the
device to
operate in
AUTO mode.
STOP - Variable Optional - Input (digital); LD, LP
AUTO STOP
TRAVEL
command.
OPEN - Variable Optional - Input (digital); LD, LP
AUTO
OPEN/START
command.
CLOS - Variable Optional - Input (digital); LD, LP
AUTO
CLOSE/STOP
command.
EMOP - Variable Optional - Input (digital); LD, LP
emergency
OPEN/START
command.
EMCL - Variable Optional - Input (digital); LD, LP
emergency
CLOSE/STOP
command.
DVCE - Variable Required - Output device. LP
OUT1 - Variable Optional - Output (digital); LD, LP

TRUE when the
device is going
to or being kept
at the
OPEN/START
state.
TRUE when the
device is going
to or being kept
at the
CLOSED/STOP
state.
142 OW351_R1100
5.28 DEVICE
FI E L D RE C O R D

TRUE when a
device operation
has been
stopped.
LOC - Variable Optional - Output (digital); LD, LP
When EMRG Bit
2 = 0, LOC is
set TRUE when
the device is
operating in
Local mode.
MAN - Variable Optional - Output (digital); LD, LP
TRUE if the
device is
operating in
Manual mode.
AUTO - Variable Optional - Output (digital); LD, LP
TRUE if the
device is
operating in
Auto mode.
OPFL - Variable Optional - Output (digital); LD, LP
TRUE if a
device operation
failed or if a
failure to
respond
occurred.
TRIP - Variable Optional - Output (digital); LD, LP
TRUE if the
device tripped
(that is, changed
state without a
change state
command).
STAT - Variable Optional - Output (digital); LD, LP
current state of
the device.
1 = OPEN/ON
0=
CLOSED/OFF
OW351_R1100 143
5.29 DEVICESEQ
5.29 DEVICESEQ
Description
The DEVICESEQ algorithm provides an interface between a control logic function and a
MASTERSEQ algorithm. In the most common application configuration, the logic control is utilized
to control a particular device. In this configuration, the MASERSEQ algorithm typically provides a
supervisory control function of multiple devices. Refer to the MASTERSEQ reference pages (see
page 335) for details on the operation of the MASTERSEQ algorithm.
The DEVICESEQ algorithm communicates with the associated MASTERSEQ algorithm via a
packed group point status point. The DEVICESEQ algorithm interfaces to the control logic via
individual inputs and outputs. Refer to the template definition table for details on the algorithm
inputs, outputs, and configuration parameters.
Functional Symbol
Details of Operation
The DEVICESEQ algorithm provides the MASTERSEQ with the status information of the
associated device. This status information is outlined in the following status information section.
The DEVICESEQ algorithm also transfers the value of the GO bit in the status point to the STRT
output. As long as the GO bit in the status point is TRUE, the associated device is considered to
be running.
The algorithm can also be configured to utilize an internal failure timer. This timer monitors the
amount of time that elapses while the device is running. The timer stops accumulating time when
either the PASS or FAIL input becomes TRUE. The elapsed time is compared to the value of the
TARG parameter each execution cycle of the algorithm. The internal timer expires when the
accumulated time becomes greater than or equal to the value of TARG parameter and is greater
than zero. Setting the value of the TARG parameter greater than zero enables the failure timer. If
the failure timer is enabled, the accumulated time is always stored in the R3 field of the algorithm.
In addition, the accumulated time is also stored in the optional ACT output point.
The algorithm also incorporates an additional internal timer that stores the time that has elapsed
while the device was running. This timer value is stored in both the optional TIME output and the
R4 field of the algorithm record. This value is independent of the internal failure timer and is
always updated whether the internal failure timer is utilized or not. The accumulated time in both
timers is calculated based on loop time.
During the first pass mode of the controller and when the RESET bit in the status point (MSTR) is
TRUE, the DEVICESEQ algorithm sets the elapsed time for both the step timer and the internal
failure timer to zero.
144 OW351_R1100
5.29 DEVICESEQ
Status Information
The DEVICESEQ algorithm provides the attached MASTERSEQ algorithm with the following
status information:
 It provides an indication that the associated device is ready for a remote start. The device is
ready for remote start when the RDY input is TRUE. The value of the RDY input is then
transferred to the READY bit of the status point during each execution cycle of the algorithm.
 It provides an indication that the associated device has failed. The device is failed when the
FAIL input is TRUE. The value of the FAIL input is transferred to the FAILED bit in the status
point during each execution cycle of the algorithm.
 It provides an indication that the associated device has complet ed operation when the PASS
input is TRUE. The value of the PASS input is transferred to the SUCCESS bit during each
execution cycle of the algorithm.
Freeze Mode
The purpose of the freeze mode is to preserve the operating state of the algorithm after the
device has completed operation. The algorithm can be configured to freeze the value of the bits in
the status point after the algorithm has been selected by the attached MASTERSEQ. As a result,
this enables you to determine and evaluate the performance of the device at a later point in time.
A DEVICESEQ algorithm is selected when the INSTEP bit in the status point is TRUE. If the FRZ
field in the algorithm is initialized to “FREEZE”, the algorithm does not update the status point
after the INSTEP bit transitions from TRUE to FALSE. Thus, the status bits that originate with the
DEVICESEQ retain their previous values. This state is referred to as freeze mode.
In freeze mode, the algorithm sets the FROZEN bit to logic 1 in the status point. In order to clear
the freeze mode condition, the attached MASTERSEQ algorithm must be reset. This causes the
RESET bit in the status point to become TRUE and the DEVICESEQ resets according to the rules
outlined in the initial state and reset section.
Note: Emerson does not recommend using freeze mode with an associated MASTERSEQ
algorithm which is operating in priority mode. See the MASTERSEQ reference pages (see page
335) for more details on priority mode operation.
FI E L D RE C O R D
DIAG LU -Integer Data Required 5 Tuning Diagram -

Init Number
MSTR - Variable Required - Status point for LP

communication
with MASTERSEQ
FAIL - Variable Required - Input from device LD, LP

Logic functions
indicating that a
failure has
occurred.
OW351_R1100 145
5.29 DEVICESEQ
FI E L D RE C O R D
PASS - Variable Required - Input from device LD, LP

Logic functions
indicating that the
execution of the
device has
completed
successfully.
RDY - Variable Required - Input from device LD, LP
Logic functions
indicating that the
associated device
is ready for a start
command.
BASE R1-Real Tuning Required 1.0 Time Base in -
Constant Seconds.
Defines the units
that the internal
failure time and
accumulated time
are displayed in.
(Typical values are
1.0 or 0.1 sec.)
* TARG R2-Real Selectable Required 0.0 Delay Time. LA
Defines the amount
of time that can
elapse, while the
device is running,
before the
DEVICESEQ
algorithm sets the
failure bit in the
status point to
Logic Delay Time
1. If the value of
the parameters is
0.0, the internal
failure timer is
disabled.
FRZ X1-Byte Data Init Optional NO Options are: -
FREEZE  NO FREEZE
 FREEZE
Update Freeze
Flag.
Enables and
disables freeze
mode.
STRT - Variable Required - Start Device LD, LP
146 OW351_R1100
5.29 DEVICESEQ
FI E L D RE C O R D
ACT - Variable Optional - Output value of LA

internal failure
timer.
TIME - Variable Optional - Output value of LA
step timer.
Represents the
amount of time the
device has been
running
* When a parameter type is defined as "Selectable" and marked as "Required," the Control Builder may
Status Bit Definitions
B I T N U MB E R O R I G I N ATO R S I G N AL NAME DE S C R I P TI O N
0 MASTERSEQ GO Signal to Device to Begin Step.
1 DEVICESEQ FAILED Signal to MASTERSEQ that Current Step

Encountered a Failure.
2 DEVICESEQ READY Signal to MASTERSEQ that Current Step
Completed Successfully.
3 DEVICESEQ SUCCESS Signal to MASTERSEQ that the low-level
Logic is Ready to Receive a Remote Start
Command.
4 MASTERSEQ INSTEP Signal from MASTERSEQ that the Step is
Currently Being Executed.
5 MASTERSEQ OVERRIDE When TRUE indicates that the OVRD input

was used to Increment the step.
6 MASTERSEQ RESET MASTERSEQ sets this bit logic 1 when reset
input is TRUE.
7 DEVICESEQ FROZEN This bit is TRUE when DEVICESEQ has

Frozen updates to the status point.
8 - 15 Reserved for - -
future use
OW351_R1100 147
5.30 DEVICEX
5.30 DEVICEX
Description
The DEVICEX algorithm combines the commands to open and close or start and stop a piece of
equipment with feedback signals indicating the command was accomplished. Devices allow
controlled access of the equipment they own and simplify the operation of the equipment. This
algorithm provides digital outputs that reflect how the I/O outputs of the device are being
maintained and the different status/mode conditions of the device.
The DEVICEX algorithm responds to the following signal combinations:

 One digital output and no feedback.
 One digital output and one digital feedback.
 Two digital outputs and two digital feedback signals.
 Two digital outputs and one feedback.
 Three digital outputs and two feedbacks.
Signal Combinations
One Digital Output and No Feedback
With one output and no feedback, the DEVICEX algorithm sets the device to a defined state (on,
off, start, stop, open, close) when commanded.
148 OW351_R1100
5.30 DEVICEX
One Digital Output and One Digital Feedback
With one output and one feedback, the DEVICEX algorithm can set the output to a defined state,
set the “In Transition” bit (A2 field of bit 1 of the device record), and then monitor the input. If the
input's state does not match the output state within a user- specified amount of time, the device
indicates a failed operation has occurred. If the feedback indicates the desired state is reached
within the user-specified time, the device sets its current state field to the appropriate value. In
either case, the In Transition bit resets at the end of the operation.
OW351_R1100 149
5.30 DEVICEX
Two Digital Outputs and Two Digital Feedbacks
With two digital outputs and two digital feedbacks, the DEVICEX algorithm can set the appropriate
output to “1” or ON and wait for the appropriate feedback to be true. When the appropriate
feedback indicates true, the device sets its current state field to the appropriate state. If the
feedback does not indicate the appropriate state is reached within the user-specified time, the
device status display indicates a failed operation.
150 OW351_R1100
5.30 DEVICEX
Two Digital Outputs and One Digital Feedback
With two digital outputs and one feedback, the DEVICEX algorithm can set the appropriate output
to “1” or ON and wait for the feedback to go to the desired state. When the feedback indicates the
new state, the device sets its current state field to the appropriate state. If the feedback does not
indicate the appropriate state was reached within the user-specified time, the device indicates a
failed operation.
OW351_R1100 151
5.30 DEVICEX
Three Digital Outputs and Two Digital Feedbacks
With three outputs and two feedbacks, the algorithm can set the appropriate output to “1”
according to the OPEN/CLOSE, START/STOP, or STOP TRAVEL command requested. If the
request is an Open or Close command, the feedbacks are monitored to see if the new state is
reached. When the feedbacks indicate the new state, the device's current state bit is updated to
the appropriate state. If the feedbacks do not indicate the appropriate state within the user-
specified time, the device indicates a failed operation. If the command is a Stop Operation
request, the algorithm writes a “1” to the Stop Travel output and indicates that the device is
stopped.
152 OW351_R1100
5.30 DEVICEX
Control Operation
If the state of the I/O is indeterminate (that is, when both input status bits are equal to 1, or both
are equal to zero and the device is not being commanded to another state), the Sensor Failure bit
(bit 2 and 3 of the 1W field of the DVCE point) in the device record is set and the quality is set to
bad. Note, that once a device is commanded to another state, the “In Transition” status is set to
true as soon as the algorithm starts driving the device to the commanded state. The “In
Transition” status is reset when the device feedback indicates the new state, and the operation is
successful. If the operation fails, and the device indicates it is neither open nor closed (both bits of
the feedbacks are zero or one), the “In Transition” status remains set and the Input Sensor Failure
bit is not set. However, the Operation Failed bit (bit 2 of the A2 field of the DVCE point) is set.
The device with two feedbacks may also be configured to display a “Failure to Respond” status. If
you configure the device to have a response time, the failure occurs if both feedbacks are not at a
zero (clear) state within the defined response time. If a “Failure to Respond” occurs, there is no
“Operation Failure” since the algorithm waits for a new command to process following the
response failure. However, if the device is Stopped and the feedback s indicate a zero condition,
the Sensor Failure bit is not set.
The digital inputs and outputs used by the DEVICEX algorithm can either be signals read from or
written to I/O cards, other digital process points contained in the system, or a combination of the
two.
Whenever a device experiences a failed operation (or response failure), it may ignore additional
requests for state changes or it may continue servicing such requests. This depends on how the
device is configured (bit 4 of the C4 field of the algorithm record). You may want a DEVICEX
algorithm to ignore further requests after a piece of equipment has failed in order to prevent
further damage to the equipment. Regardless of how a device is configured, it services at least
one request subsequent to each change of operating mode (for example, Auto Mode to Manual
Mode). If the device is configured to ignore requests after a failure, it displays the status
“LOCKOUT” when a failed operation (or response failure) occurs.
Control Modes
A device is put into one of three modes by the operator by pressing the appropriate control key
(located on the Control Panel or Ovation Keyboard) or specified function key (located on a
standard keyboard). Note that the device must be configured to operate in that mode. Therefore,
the DEVICEX has three modes of operation that can be adjusted during monitoring. These modes
are as follows:
 AUTO
 MANUAL
 LOCAL
Auto Mode
Auto Mode allows the Controller application program to control the device through user-
programmed logic. The device cannot go into Auto mode unless it is configured to operate in that
mode.
Once configured for Auto mode, the device can enter Auto mode if one of the following occurs:
 The operator presses the Auto mode control key.

 The status of the device is a return from Tag Out and its default mode is Auto.
OW351_R1100 153
5.30 DEVICEX
 The Reject to Auto (ARE) input becomes true and both Manual (MRE) and Local (LRE)
rejects are false.
 The default mode of the device is Auto, and the DEVICEX algorithm is in its first pass.
 Upon a failed operation if the device is configured.
The device exits Auto mode whenever one of the following happens:
 The operator presses the Manual Mode control key.

 The operator presses the Local Mode control key.
 The Reject to Local (LRE) input goes true.
 The Reject to Manual (MRE) input goes true.
 A Failed Operation occurs and the device is configured to go to Manual mode when the
operation fails.
The device may be configured (bit 6 of the C4 field) to go to Manual mode when a change of state
command is entered. If this is the case, pressing the following control keys causes the device to
go to Manual mode:
 Start/Open
 Stop/Close
 Stop Travel (discontinue operation in progress)
When in Auto Mode, the DEVICEX algorithm accepts commands from the digital process points
that are linked to the device through the DEVICEX algorithm. Possible commands are:
 Stop/Close
 Start/Open
 Emergency OPEN/START Override
 Emergency CLOSE/STOP Override
The device does not process any Manual or Local commands while in Auto mode.
Manual Mode
Manual Mode allows the operator to control the device with the control keys. The device cannot
go into Manual Mode unless it is configured for that mode. Once the device is configured, it can
enter Manual Mode when one of the following occurs:
 The operator requests Manual mode by pressing the Manual Mode request key.
 The status of the device is a return from Tag Out and its default mode is Manual.
 Upon startup of the Controller, the default mode of the device is Manual.
 There is an occurrence of an Emergency Override and the default mode of the device is
Manual.
 Upon a failed operation, if the device is configured.
154 OW351_R1100
5.30 DEVICEX
The device may be configured to go to Manual mode when a change of state command is
entered. In this case, pressing the following control keys causes the device to go to Manual mode:
 Start/Open
 Stop/Close
The device exits Manual Mode whenever one of the following happens:
 The operator requests Local mode with a control key.

 The operator requests Auto mode with a control key.
 The Reject to Local (LRE) or Reject to Auto (ARE) input becomes true and Manual Reject
(MRE) is false.
 The operator requests the device to be Tagged-Out with the appropriate control key.
When in Manual Mode, the DEVICEX algorithm accepts commands from the following possible
commands:
 Start/Open
 Stop/Close
 Stop
When in Manual Mode, the DEVICEX algorithm allows the Emergency Override to the device only
if the device is configured (see bit 0 in C4 field) such that the overrides have precedence over the
operator's commands.
In addition, when in Manual Mode, the DEVICEX algorithm does not process any Auto and Local
commands to Close, Open, or Stop the devices.
Local Mode
Local Mode is the lowest level mode of operation for the device. A device can enter this mode
only if the following two conditions are met:
 The Reject to Local (LRE) input goes true.

 The operator requests Local mode with a control key.
The device exits Local mode whenever one of the following happens:
 A Failed Operation occurs and the device is configured to enter Manual mode when it fails.
When in Local Mode, the DEVICEX algorithm accepts commands. Commands are digital process
points that are linked to the device through the DEVICEX algorithm. Possible commands are:
 Stop/Close
 Start/Open
 Emergency OPEN/START Override
 Emergency CLOSE/STOP Override
As long as the device is in the Local mode, the DEVICEX algorithm does not execute any
commands from the Auto and Manual modes. However, the Emergency Overrides is honored
when the device is in Local mode.
OW351_R1100 155
5.30 DEVICEX
Mode Independent Commands
There are several commands that are requested with keys and are executed if the device is in
Auto, Manual or Local mode. These commands are:
 Tag Out the Device
 Acknowledge Trip
 Auto mode request
 Manual mode request
 Local mode request
These commands are not accepted, however, if the device is tagged-out.
Tag Out
When in Tag Out Mode, the device ignores all commands except “Remove Tag Out”. The device
goes to its default mode when the Tag Out is removed.
Lock Out
A subset of the Tag Out mode is the device “LOCK OUT” mode. Lock out occurs if the device is
configured (see bit 4 C4 field) to ignore subsequent commands to change state after an operation
fails. In other words, the device has only one opportunity to change state in a particular mode. If
the operation fails, the DEVICEX algorithm does not accept another Open/Start or Close/Stop
command while locked out.
A device may be removed from a Lock Out condition by any of the following actions:
 Pressing the Auto, Manual or Local mode control keys.
 Tagging out the device.
Emergency Overrides
In addition to the change of state commands, in each of the operating modes there are two other
commands: Emergency Start/Open/Trip and Emergency Stop/Close/Reset.
These two commands are generated by external logic in the Controller and can act as emergency
overrides over all other commands, including Stop Travel.
Whenever either the Emergency Open, or Emergency Close input becomes true, the DEVICEX
algorithm forces the device to its default state and attempts to get the device to the commanded
state. (If the DEVICEX algorithm is not configured to ignore failures, the emergency command
executes only once.) If both emergency overrides are set at the same time, the device remains on
its present course of action.
As long as either Emergency input is set, the DEVICEX algorithm ignores all Auto and Local
commands to drive the device. The device may also be configured to have the Emergency inputs
override the Manual commands or the Manual commands to override the Emergency inputs.
Upon removal of the emergency override, the device returns to its default mode.
Note: Emergency overrides, lik e all other commands, are ignored when the device is tagged
out or in Local Mode.
156 OW351_R1100
5.30 DEVICEX
Change of State
In general, when a change of state command is in progress, it is continued until the device
reaches the new state or until a time out occurs. The following conditions cause an operation in
progress to be discontinued:
 The device is Tagged Out, resulting in inputs being read and outputs not set to true. They are
left as they were at the time of Lock Out.
 A Stop (discontinue operation) command is requested by the current control mode and an
Emergency Override is not in progress. However, if the device is in Manual mode, and it is
configured such that the Emergency Overrides do not have priority over Manual commands, a
Manual Stop request overrides the Emergency command.
In order for a change of state command to be executed, its proper permissive bit must be true.
For example a Manual Close/Stop command is only executed if the Close/Stop permissive bit of
the device is true. The Emergency Override and Stop (discontinue operation) commands do not
require any permissives to be true in order to be executed.
The permissives of a device are set to true on start-up and remain true unless the DEVICEX
algorithm is used to update them.
The amount of time that a device allows for the equipment to change state following a command
can be set by the user. You must specify the units of time for transition (tenths of a second,
seconds, or minutes), and the maximum number of time units to get to the set and reset states.
You can also specify a time period (in loops) for the equipment to respond to a command.
For devices with feedback, the amount of time that the DEVICEX algorithm sets the appropriate
output to “ON” can also be configured by the user. The following modes are supported:
 Set output “ON” for a user-configured time period (less than the transition time), or until the
new state is reached, whichever occurs first. (Indicate this mode by setting bit 1 of C4 field.)
 Set output “ON” for a user-configured time period (equal to the transition time) or until the new
state is reached, whichever occurs first. (Indicate this mode by setting bit 2 of the C4 field.)
 Maintain output “ON” continuously, until a new command is given. This mode also has a time-
out associated with it, but the pulsing continues after the time-out occurs. If the operation
should fail (device does not reach the commanded state) the operation is flagged as a failure,
and the pulsing discontinues until a new command is given. (Indicate this mode by setting bit
3 of the C4 field.)
For the case where the device has only one output (no feedbacks), the output is set to “ON” (or
“OFF”) continuously depending on whichever command is requested. There are no time-outs for
this case.
A device always writes to its output(s) when a new change of state command occurs regardless
of the state of its input(s). If the device command is from other application logic, care should be
taken to ensure that the command is maintained or pulsed as needed.
The device continuously checks for change of state commands when it is not in the process of
executing one. The device executes a change of state c ommand when it is first set to “ON.” If the
command stays “ON,” the device treats it as a new command when it finishes executing the last
command. Since the device writes to its output(s) when a new command occurs, its output(s)
cycles continuously “ON” and “OFF” if the following are true:
 A change of state command is “ON” and it matches the state of the device's input(s).
 The device is configured to set its output(s) “ON” for a certain amount of time, then “OFF”.
OW351_R1100 157
5.30 DEVICEX
Alarming
The DEVICE algorithm supports seven types of alarms. All of these alarms, except Trips, require
operator acknowledgment. The device conditions which can produce alarms are:
 Failed Operations
 Failures to Respond
 Trips
 Alarm State
 Sensor Failures
 Emergency Overrides
 Attention (Trouble)
Failed Operations
If the Failed Operations alarm is configured, the DEVICEX algorithm puts the device in alarm
whenever the equipment does not complete a change-of-state command (for example, if a valve
is commanded to open and it does not do so within the user-specified time). A Failed Operation
Alarm clears upon the next Open, Close, or Stop command to the device.
Failure to Respond
If the Failure to Respond alarm is configured, the DEVICEX algorithm puts the device into alarm if
the feedbacks do not reflect an “In Transition” state within a user-specified number of loops. The
“In Transition” state must be that both feedbacks have a value of 0.
Trips
If Trip alarms are configured, the DEVICEX algorithm puts the device into alarm whenever the
equipment unexpectedly changes state (for example, when a breaker trips open). A Trip Alarm
clears when you acknowledge the Trip by commanding the device to the Tripped state. Trip Alarm
returns do not require acknowledgment by the user via the Alarm window since they are c leared
by commanding the device.
Alarm State
The device can be configured to go into alarm based on a user-defined state. The alarm clears
only when the device returns to the non-alarmed state. These alarms must be acknowledged by
the user.
Sensor Failures
Either one or both of the following conditions cause a Sensor Failure alarm:
 The device feedbacks are indeterminate (that is, both show a 00 or 11 status) and the device
is not in transition. This is an input sensor alarm.
 The outputs do not reflect the value written to them (output sensor alarm).
158 OW351_R1100
5.30 DEVICEX
Emergency Override
The Emergency Override alarm is generated any time an override occurs and the device is not at
the override state. For example, the occurrence of an Emergency Open generates an alarm if the
device is Closed. If both override inputs happen to become true at the same time, an alarm is
generated regardless of the state of the device.
Attention (Trouble)
The Attention (Trouble) alarm is caused by the following conditions:

 The device is in Auto mode and an Auto Open/Start command is present while the device
Open/Start permissive is OFF or and Emergency Close/Stop override is ON.
 The device is in Auto mode and an Auto Close/Stop command is present while the device
Close/Stop permissive if OFF or and Emergency Open/Start override is ON.
 The device is not in Auto mode and an Auto Open/Start command is present while the device
is not Open or Running.
 The device is not in Auto mode and an Auto Close/Stop command is present while the device
is not Closed or OFF.
If the device is configured to go into alarm based on a combination of conditions, the point is put
into alarm when either one or more of the alarm conditions exist.
The following alarming options are available:

 No Alarming
 Failed Operations, Sensor Failures, Trips, Response Failures, Attention conditions, and
Emergency Overrides
 Failed Operations, Sensor Failures, Trips, Response Failures, Attention conditions,
Emergency Overrides, and Alarm State
Clearing Alarms
Upon Tagging Out, Scan Removing, or putting a device into Local mode, the following alarms are
cleared:
 Failed Operation
 Failure to Respond
 Sensor Failures
 Trips
 Attention
A State Alarm, however is not cleared by any of the conditions mentioned above. It must be
cleared by commanding the device.
Tagging out or going to Local mode clears any Emergency Override present.
OW351_R1100 159
5.30 DEVICEX
Device Status Reporting

The device record maintains information corresponding to the current status of a device.
Depending on the state of a device, its displayed status includes a combination of the following
conditions:
 Current State
 In Transition
 Operation Failed
 Tripped
 Stopped
 Emergency Close
 Emergency Open
 Current Mode
 Override Failure
 Scan Removed
 Alarm Checking Off
 Tagged Out
 Locked Out
 Quality
 Permissives
 Rejects
The status information mentioned above comes from various flags (bits) in certain fields in the
packed point and algorithm record.
The A2 field of the Packed point (DVCE) has the following information: The bits in the A2 field are
A2 Field Bit Information
Bit 0 Current State. This bit indicates the current state of the feedback signals. In case feedback
signals give conflicting data, the last known state is reported. When scanned removed the
last command state is reported.
Bit 1 In Transition. This bit indicates the device algorithm is currently in the process of trying to
change the state of its equipment. The bit is set true when the device starts to execute a
command. It is reset when the feedback signals indicate the operation is complete or the
operation has failed.
Bit 2 Operation Failed. This bit is set following any unsuccessful attempt to change the state of
the equipment. It remains set until the next attempt is made to change the state of the
equipment. Failed operation are not indicated if the device is scanned off.
Bit 3 Tripped. This bit is set any time the equipment changes stage on its own, not by the
algorithm. It remains set until the Trip Acknowledge command. If it is not acknowledged, no
other change of state operations, in any mode are processed. The tripped bit is not set
when the device is Tagged Out or Scanned Removed.
Bit 4 Stopped. This bit is set whenever the device is commanded to stopped. The bit remains
set until the next attempt is made by the device to change the state of the equipment.
Bit 5 Emergency Close. This bit reflects the status of the override inputs to the device.
160 OW351_R1100
5.30 DEVICEX
Bit 6 Emergency Open. This bit reflects the status of the override inputs to the device.
Bit 7 Last Commanded State. This bit reflects the last known state of the device.
Bit 8 Local Mode. This bit indicates that the device is in local mode.
Bit 9 Manual Mode. This bit indicates that the device is in manual mode.
Bit 10 Auto Mode. This bit indicates that the device is in auto mode.
Bit 11 Reserved.
Bit 12 Attention. This bit indicates certain error conditions are present.
Bit 13 Failed to Respond. This bit indicates that the device did not respond to a command.
Bit 14 Locked Out. This bit indicates that the state of the device is locked out.
Bit 15 Tagged Out. This bit indicates that the state of the device is tagged out.
The C5 field in the DEVICEX algorithm holds the command word. This command word is the
interface between a Controller and the algorithm. The bits in the C5 field are defined in the
following table:
Bit 0 Emergency Close/Stop
Bit 1 Emergency Open/Start

Bit 6 Current State of Input 1 (Open/Start)
Bit 7 Current State of Input 2 (Close/Stop)
Bit 8 Current State of Input 3 (Stop)
Bit 9 Value currently being written to Output 1 (Open/Start)
Bit 10 Value currently being written to Output 2 (Close/Stop)
Bit 11 Value currently being written to Output 3 (Stop)
Bit 12 Close/Stop permissive
Bit 13 Open/Start permissive
OW351_R1100 161
5.30 DEVICEX
Setting Device Parameters
Alarming
The following fields in the Packed point (DVCE) must be set for alarming:
Alarming Parameters
T YP E OF A L AR MI N G FI E L D S TO B E SET
No Alarming Set E0 and E1 to zero.
Operate, Sensor, Trips, Overrides and Attention Set E0 and E1 to 0x386c

Operate, Sensor, Trips, Overrides and Attention, Set E0 and E1 to 0x386d
State Set(1)
Operate, Sensor, Trips, Overrides and Attention, Set E0 to 0x386d and E1 to 0x386c
State Set(0)
Pulse and Transition Timing
The amount of time a device allows for the equipment to change state following a command is
user-configurable. You must specify the units of the time (tenths of a second, seconds, or
minutes) to measure the transition time in, and the maximum number of tim e units to get to the
set and reset states. You may also specify a time period (in loops) for the equipment to respond
to a command.
 Time Units field (D0 field in the algorithm record) - holds the user-entered time units for
the set and reset time-outs. Valid values are 0 for tenth of seconds, 1 for seconds, and 2 for
minutes.
 Set Time-out field (D2 field in the algorithm record) - holds the user-entered value. The
maximum number for tenth of a second and second is 255. The maximum number for
minutes is 100.
 Reset Time-out field (YT field in the algorithm record) - holds the user-entered value. The
maximum number for tenth of a second and second is 255. The maximum number for
minutes is 100.
 Time to Respond field (YP field in the algorithm record) - applies only to devices with two
feedbacks. If this value is non-zero, the device feedbacks must respond to a command within
the response time or the operation is discontinued and a 'Failure to Respond' alarm is
generated.
The C4 field in the algorithm record defines the mode configuration. The bits in the C4 field are
BI T MOD E D E S C R I P TI O N
Bit 0 Off The emergency Open/Start and Close/Stop commands override

Auto and Local Mode commands.
On The Emergency Open/Start and Close/Stop commands override
all other commands.
162 OW351_R1100
5.30 DEVICEX
BI T MOD E D E S C R I P TI O N
Bit 1 On Set output 'ON' for a configured time period (less than the time -
out). If this bit is set, the algorithm maintains the appropriate
output for the number of loops in the Pulse Time or until the
operation is successful, whichever occurs first.
Bit 2 On Set output 'ON' until a user-configured time-out (or the operation
is successful). The transition times for setting and resetting the
device are entered in the Set Time-out and Reset Time-out fields.
Bit 3 On Set output 'On' continuously until a new command is entered.
Bit 4 On Set Override Failure bit in the A2 field of the DVCE point.
Bit 5 On Do not execute the STOP command

Bit 6 Off Manual Open/Close/Stop commands force the device to Manual
mode.
On Manual Open/Close/Stop commands are processed only it the

device is in Manual mode.
Bit 7 Off Device default mode is Manual.
On Device default mode is Auto
Note: If bits 1, 2, and 3 are all zero, then the information in bits 3, 4, and 5 in the Custom
Configuration word is used to maintain/pulse the outputs.
The custom configuration (C7 field in the algorithm record) bits are defined below. You may also
define the mode(s) a device may operate in, the position the device may be tagged out in, and so
forth as defined in the following table:
Bit 0 On The device is allowed to operate in Auto mode.
Bit 1 On The device is allowed to operate in Local mode.

Bit 2 On The device is allowed to operate in Manual mode.
Bit 3 On The Open (Start) output is maintained continuously.
Off The Open (Start) output is pulsed once on an Open/Start command.

Bit 4 On The Close (Stop) output is maintained continuously.
Off The Close (Stop) output is pulsed once on a Close/Stop.
Bit 5 On Only applicable to Open/Close/Stop type devices. The Stop output is

maintained continuously.
Off The Stop output is pulsed once on a Stop command.
Bit 6 On The Auto Stop is maintained input (always on until the alg orithm turns
it off).
Off The Auto Stop is pulsed input.
OW351_R1100 163
5.30 DEVICEX
Bit 7 On The Auto Start is maintained input (always on until the algorithm turns
it off).
Off The Auto Start is pulsed input.
Bit 8 On The Local Stop is maintained input (always on until the algorithm
turns it off).
Off The Local Stop is pulsed input.
Bit 9 On The Local Start is maintained input (always on until the algorithm
turns it off).
Off The Local Start is pulsed input.
Bit 10 On The Close/Stop permissive is internally generated.
Bit 11 On The Open/Start permissive is internally generated.

Bit 12 On The Travel (Transition) Timer Enabled is internally generated.
Bit 13 On The equipment may be Tagged-out in the open position.
Bit 14 On If Bit 14 is set, equipment may be Tagged-out in the closed position.

For Start/Stop devices only, equipment may be tagged out in the
Off/Stop position.
Bit 15 On The device is forced to Manual mode when a failed operation occurs.
Functional Symbol
164 OW351_R1100
5.30 DEVICEX
FI E L D RE C .
DIAG LU - Byte Data Init. Required 47 Tuning Diagram -

Number.
SET D2 - Integer Data Init. Required 20 Set time-out (Max of -
255 if units are 1/10
seconds or seconds.
Max. of 100 if units
are minutes.)
RSET YT - Integer Data Init. Required 20 Reset time-out (Max -
of 255 if units are
1/10 seconds or
seconds. Max. of
100 if units are
minutes.)
EM C4 - Integer Data Init. Required 9 Emergency override -
commands
PT D4 - Integer Data Init. Required 0 Pulse Time -

TR YP - Integer Data Init. Required 0 Number of Loops to -
Respond
CZ C7 - Integer Data Init. Required 0 Configuration -
TU D0 - Integer Data Init. Required 1 Units time-out -
Value Time Units
0 - Tenths of
Seconds
1 - Seconds
2 - Minutes
TYPE C8 - Integer Data Init. Required Open Device Type: -
Open/close or
Start/Stop
DTIM D5 - Integer Data Init. Required 0 Delay Time in -
Seconds
IN1 - Variable Optional - Device Input 1 - LD, LP
Feedback
Feedback
Feedback
CPRM - Variable Optional - Close Permissive LD, LP
OPRM - Variable Optional - Open Permissive LD, LP
ARE - Variable Optional - Auto Reject LD, LP
LRE - Variable Optional - Local Reject LD, LP
OW351_R1100 165
5.30 DEVICEX
FI E L D RE C .
MRE - Variable Optional - Manual Reject LD, LP

LOPL - Variable Optional - Local Open Logic LD, LP
LCLL - Variable Optional - Local Close Logic LD, LP
LSTL - Variable Optional - Local Stop Logic LD, LP
AOPL - Variable Optional - Auto Open Logic LD, LP
ACLL - Variable Optional - Auto Close Logic LD, LP
ASTL - Variable Optional - Auto Stop Logic LD, LP
TMEN - Variable Optional - Transition Timer LD, LP
Enable
EMCL - Variable Optional - Emergency LD, LP
Close/Stop
EMOP - Variable Optional - Emergency LD, LP
Open/Start
DVCE - Variable Required - Device record LP
OUT1 - Variable Optional - Output 1 LD, LP
LOC - Variable Optional - Local Mode LD, LP
MAN - Variable Optional - Manual Mode LD, LP
AUTO - Variable Optional - Auto Mode LD, LP
OPFL - Variable Optional - Failure-to-Respond LD, LP
TRIP - Variable Optional - Report Trip LD, LP
STAT - Variable Optional - State of the device LD, LP
DEST - Variable Optional - Delay Output LD, LP
166 OW351_R1100
5.31 DFIELD
5.31 DFIELD
Description
The DFIELD algorithm is used only with the hardware digital output variable points. It should be
used instead of “output digital hardware” I/O connectors in applications involving interfaces to
control elements (for example, valves and dampers).
The output digital point (FAIL) is TRUE when the algorithm detects a hardware error on the I/O
card.
Functional Symbol
FI E L D RE C O R D
DIAG LU Data Init. Required 0 Tuning Diagram -

Number
IN1 - Variable Required - Input (digital) LL
HWPT1 - Variable Required - Hardware Output LL

(digital)
FAIL - Variable Optional - Hardware Error Point LL
(digital)
1 You cannot scan remove the HWPT point.
OW351_R1100 167
5.32 DIGCOUNT
5.32 DIGCOUNT
Description
The DIGCOUNT algorithm sets the output digital FLAG TRUE if M inputs or more of the N digital
inputs are TRUE (where N < 12, and M and N are constants). The output analog record is set
equal to the number of TRUE digital inputs.
Functional Symbol
FI E L D RE C .

number
NMIN G4-Integer Data Init. Required 0 Total digital inputs -
(N)
* MTRU X1-Byte Selectable Required 0 Maximum TRUE LA
digital inputs (M)

•
•
IN12
FOUT - Variable Required - Output (digital flag) LD, LP

168 OW351_R1100
5.33 DIGDRUM
5.33 DIGDRUM
Description
The DIGDRUM algorithm is a software drum controller with up to 32 digital output values and up
to 50 steps. The outputs selected to be TRUE are based on the current step number and a list of
up to 50 initialized integer values. These integers contain 32 bits of data, which are then mapped
onto the 32 digital outputs. Thus, for each step, you can initialize any combination of TRUE and
FALSE states for any or all of the 32 outputs by converting a string of up to 32 bits into a
hexadecimal number.
Functional Symbol
G0= B0= C0= D0= YM=

G1= B1= C1= YQ= YL=
G2= B2= C2= D2= E2=
G3= YU= C3= YP= E3=
G4= B4= C4= D4= E4=
G5= B5= C5= D5= YC=
G6= B6= C6= D6= Y9=
G7= B7= C7= YN= E7=
G8= B8= C8= D8= E8=
G9 B9= YT D9= Y8=
OW351_R1100 169
5.33 DIGDRUM
These 50 integers should be input as hexadecimal numbers (for example, 0x1234). Refer to the
Binary to Hexadecimal Conversion Table (see page 6) for information on how to create a
hexadecimal number from 16 bits.
The current step number may be tracked to a selected step (TRIN) when in tracking mode (TMOD
= TRUE), increased (INC), or decreased (DEC). The current step number is only increased or
decreased on a FALSE to TRUE transition of INC and DEC. The maximum number of steps must
be initialized. When the current step number becomes greater than the number of steps, the
current step number is reset to one. If TRIN is a non-integer value, the algorithm rounds the value
to the nearest integer. Any value for TRIN not in the range of one to NMIN is converted to a one
by the algorithm.
The track input value (TRIN) and output value (OUT) are checked for invalid real numbers. If a
tracking request is received and TRIN is an invalid number, then the tracking request is ignored.
However, the current step can be increased (using INC) or decreased (using DEC) even when
TRIN is an invalid number.
If the algorithm calculates an invalid real number output, the value is invalid and the quality is set
to BAD.
FI E L D RE C O R D

Number
INC - Variable Required 0 Input (digital signal to LD, LP
increase the step
number)
DEC - Variable Required 0 Input (digital signal to LD, LP
decrease the step
number)
TMOD - Variable Required 0 Input (digital signal); LD, LP
tracking request
TRIN - Variable Required 0 Input (analog); tracks LA
the step number to
this value
NMIN X1-Byte Tuning Required 0 Maximum number of -
Constant steps
170 OW351_R1100
5.33 DIGDRUM
FI E L D RE C O R D
TYPE X2-Byte Data Init Optional Long Steps are Long or -

Short.
Long = Step 1 to
Step 50 defines up to
32 outputs.
Short = Double
number of steps to
100 since parameter
“I/01” contains Step 1
value in the lower 16
bits, and Step 2 value
in the higher 16 bits.
Therefore, only up to
16 outputs are used.
I01 G0-Integer Tuning Optional 0 Output values for -
Constant Step 1

Constant Step 2
Constant Step 3
Constant Step 4
Constant Step 5
Constant Step 6
Constant Step 7
Constant Step 8
Constant Step 9
Constant Step 10
I11 B0-Integer Tuning Optional 0 Output values for -
Constant Step 11
Constant Step 12
Constant Step 13
I14 YU-Integer Tuning Optional 0 Output values for -
Constant Step 14
Constant Step 15
Constant Step 16
OW351_R1100 171
5.33 DIGDRUM
FI E L D RE C O R D

Constant Step 17
Constant Step 18
Constant Step 19
Constant Step 20
I21 C0-Integer Tuning Optional 0 Output values for -
Constant Step 21
Constant Step 22
Constant Step 23
Constant Step 24
Constant Step 25
Constant Step 26
Constant Step 27
Constant Step 28
Constant Step 29
I30 YT-Integer Tuning Optional 0 Output values for -
Constant Step 30
I31 D0-Integer Tuning Optional 0 Output values for -
Constant Step 31
I32 YQ-Integer Tuning Optional 0 Output values for -
Constant Step 32
Constant Step 33
I34 YP-Integer Tuning Optional 0 Output values for -
Constant Step 34
Constant Step 35
Constant Step 36
Constant Step 37
I38 YN-Integer Tuning Optional 0 Output values for -
Constant Step 38
172 OW351_R1100
5.33 DIGDRUM
FI E L D RE C O R D

Constant Step 39
Constant Step 40
I41 YM-Integer Tuning Optional 0 Output values for -
Constant Step 41
I42 YL-Integer Tuning Optional 0 Output values for -
Constant Step 42
I43 E2-Integer Tuning Optional 0 Output values for -
Constant Step 43
Constant Step 44
Constant Step 45
I46 YC-Integer Tuning Optional 0 Output values for -
Constant Step 46
I47 Y9-Integer Tuning Optional 0 Output values for -
Constant Step 47
Constant Step 48
Constant Step 49
I50 Y8-Integer Tuning Optional 0 Output values for -
Constant Step 50
STEP - Variable Required - Output (analog); LA
current step number
O01 - Variable Optional - Output (digital signal); LD, LP
least-significant bit;
set or reset according
to the bits in the
integer selected by
the current step
number
set or reset according
. to the bits in the
. integer selected by
the current step
. number
O31
most significant bit set
or reset according to
the bits in the integer
selected by the
current step number
OW351_R1100 173
5.34 DIGITAL DEVICE
5.34 DIGITAL DEVICE

Description
The Digital Device algorithm provides logic to control the following seven types of devices:
 SAMPLER (Controlled Sampler) (see page 175).

 VALVE NC (Non-Controlled Valve) (see page 177).
 MOTOR NC (Non-Controlled Motor) (see page 178).
 MOTOR (Simple Controlled Motor) (see page 180).
 MOTOR 2-SPD (Two-Speed or Bi-directional Controlled Motor) (see page 183).
 MOTOR 4-SPD (Two-Speed and Bi-directional Controlled Motor) (see page 186).
 VALVE (Controlled Valve) (see page 192).
The Digital Device algorithm provides a digital alarm bit to be set for applicable devices. The
algorithm provides time delays for each device as needed, which keeps the device from failing
while the device is processing a command. The time delay for each device can be independently
tuned in the Control Builder. A run counter is maintained for the motor and the sampler devices
and can be reset by the Operator Keyboard. The algorithm keeps the count in local memory as
either hours, minutes, or seconds, and then saves it as an analog output.
Where applicable, there are three modes: AUTO, MANUAL, and OFF. When the device is in OFF
mode, the algorithm only tracks the inputs and does not respond to any control logic or operator
commands. When in AUTO mode, the device only responds to control logic, and in MANUAL
mode, the device only responds to the Program Keys on the Operator Keyboard (described in the
following table).
Interface Keys on the Operator Keyboard
P R O G R AM KE Y D E S C R I P TI O N
P1 Close/Stop
P2 Open/Start/Fast Forward Start/Forward Start/Fast Start

P3 Slow Forward Start/Reverse Start/Slow Start
P4 Fast Reverse Start
P5 Slow Reverse Start
P6 Reset Total Run Time
P7 Reset Device Algorithm
In order for a device to respond to a command, the device must be available - not failed - and in
either MANUAL or AUTO mode. Where applicable, the algorithm can be reset either by a remote
reset device point, or by the Operator Keyboard. When the device is reset, the alarm output point
is always reset, along with the packed status alarm bits. When a device is in either the Failed or
the Unavailable condition, the device remains in the OFF mode until the problem is resolved and
the device is reset. The device is always put in the MANUAL mode when the reset is set and the
device is READY. The algorithm responds for both the Remote Reset and the Operator Reset in
any mode.
174 OW351_R1100
5.34 DIGITAL DEVICE
5.34.1 SAM PLER (Controlled Sample r)
Description
The Controlled Sampler device has the option of having the Operator Keyboard on or off. The
priority is set in the Control Builder and can only be changed in the Control Builder. The list of
inputs and outputs are found in the Algorithm Definitions table.
If the Operator Keyboard is off, the keyboard keys are disabled, and the output (OUT1) of the
device follows the input (IN1). When the Operator Keyboard is on, the output follows the input
until the output is changed manually by the operator with either the STOP or START keys. The
output follows the input again once there is a change in the input.
The runtime counts when the output is set. The total runtime will not update when Sample Reset
Priority (SPRI) is set to "Operator Keyboard OFF." The operator has the ability to reset the
runtime when either priority is set. There are no modes, time delays, or alarms associated with
the Controlled Sampler. The runtime can be tuned by changing the RUNT parameter in the
Control Builder.
Functional Symbol
N AME LC T YP E RE Q U I R E D / DE F AU L T D E S C R I P TI O N MI N .
AL G . O P TI O N AL V AL U E POI N T
RE C O R D RE C .
FI E L D
DIAG LU- Data Init. Required 30 Tuning Diagram Number -

Integer
SPRI X2-Byte Data Init. Required Keyboard Sampler Reset Priority -
 Keyboard = Operator
Keyboard ON
 Input = Operator
Keyboard OFF
BASE C6- Tuning Optional Hours Time base for total run -
Integer Constant  Hours
 Minutes
 Seconds
RUNT R1 - Real Data Init Required 0 Tune the total runtime -
value.
OW351_R1100 175
5.34 DIGITAL DEVICE
N AME LC T YP E RE Q U I R E D / DE F AU L T D E S C R I P TI O N MI N .
AL G . O P TI O N AL V AL U E POI N T
RE C O R D RE C .
FI E L D
IN1 - Variable Optional - Remote Run (digital) LD
OUT1 - Variable Required - Running Output (digital) LD

RUN - Variable Optional - Total Run Time (analog) LA
Note: The RUN output (total run time) of the algorithm will not update if SPRI (sampler reset priority) is
selected as "Input" (that is, Operator Keyb oard is OFF) in the Control Builder, even though the device is
running.
176 OW351_R1100
5.34 DIGITAL DEVICE
5.34.2 VALVE NC (Non-Controlled Valv e)

Description
The Non-Controlled Valve does not accept control information from either the control logic or the
operator (see the Algorithm Definitions table for a list of inputs and outputs). The algorithm
activates the digital alarm bit when in the failed state (see the Truth table for states of the valve).
There are no modes, time delay, or run time associated with this device.
Functional Symbol
FI E L D RE C O R D

Number
IN1 - Variable Required - Open Contact LD
(digital)
IN2 - Variable Required - Close Contact LD
(digital)
IN3 - Variable Optional - Remote Reset LD
(digital)
ALRM - Variable Optional - Device Alarm LD
(digital)
Truth Table
OPEN S TATU S CLOSED S TATU S V AL V E S TATE
Set Set Moving
Set Reset Open

Reset Set Closed
Reset Reset Failed
OW351_R1100 177
5.34 DIGITAL DEVICE
5.34.3 M OT OR NC (Non-Controlled M otor)

Description
The Non-Controlled Motor does not accept control information from either the control logic or the
operator (refer to the Algorithm Definitions table for the list of inputs and outputs). The digital
alarm bit is set when the motor is either in the failed state or Unavailable state (refer to the Truth
table for the states of the motor). The Non-Controlled Motor has an analog run time output that
may be reset by the operator. The runtime value can be tuned in the Control Builder. There are no
modes or time delays associated with this device.
Functional Symbol
FI E L D RE C O R D

Number
BASE C6-Integer Tuning Optional 0 Time base for total -
Constant run.
0 = Hours
1 = Minutes
2 = Seconds
RUNT R1 - Real Data Init Required 0 Tune the runtime -
value.
IN1 - Variable Required - Ready Contact LD

(digital)
IN2 - Variable Required - Running Contact LD
(digital)
IN3 - Variable Optional - Remote Device LD
Reset (digital)

(digital)
RUN - Variable Optional - Total Run Time LA
(analog)
178 OW351_R1100
5.34 DIGITAL DEVICE
Truth Table
READ Y S TATU S RUNNI N G S TATU S M O TO R S TATE
Set Set Running
Set Reset Ready

Reset Set Failed
Reset Reset Unavailable
OW351_R1100 179
5.34 DIGITAL DEVICE
5.34.4 M OT OR (Simple Controlled M otor)

Description
The Simple Controlled Motor runs at one speed and in one direction when in operation. This
motor has the option of accepting start or stop commands from either the control logic or the
operator.
When the device is in AUTO mode, the algorithm accepts control commands from the Remote
Start (IN3) and Remote Stop (IN4) inputs. When the device is in MANUAL mode, the algorithm
accepts the control commands Stop and Start from the Operator Keyboard. Whenever a
command is processed in either AUTO or MANUAL mode, the outputs (OUT1 and OUT2) are set
accordingly for the duration of the time delay previously set in the Control Builder.
The Stop Permissive (IN8) must be set to allow the motor to be stopped. The Stop Permissive is
automatically set when no input is connect to IN8. Refer to the Algorithm Definitions table for the
list of inputs and outputs.
The digital alarm bit is set when:
 The device is in the Failed state.

 The device is in the Unavailable state.
 The device changes running states without being commanded to do so.
 The device fails to start or stop.
When the device fails to start or stop, the alarm triggers, but the device stays in the current mode
and continues looking for the proper combination of Running and Ready. When this combination
is detected, the alarm is reset and the device continues operating in a normal condition. All other
alarms put the device in OFF mode. Refer to the Truth table for the states of the motor.
The Simple Controlled Motor also has a status packed point that displays which alarm has been
set, the last command, and which mode it is currently in. Refer to the Output Status Bits table for
the list of the status bits.
Functional Symbol
180 OW351_R1100
5.34 DIGITAL DEVICE
FI E L D RE C O R D

Number
DLY1 C0-Integer Tuning Required 0 Time for Ready -
Constant after Stop
DLY2 C1-Integer Tuning Required 1 Time for Stop -

Constant
DLY3 C2-Integer Tuning Required 1 Time for Start -
Constant
BASE C6-Integer Tuning Optional 0 Time base for -
Constant total run.
0 = Hours
1 = Minutes
2 = Seconds
(digital)
IN2 - Variable Required - Running Contact LD
(digital)
IN3 - Variable Optional - Remote Start LD
(digital)
IN4 - Variable Optional - Remote Stop LD
(digital)
IN5 - Variable Optional - Remote Auto LD
(digital)
IN6 - Variable Optional - Remote Manual LD
(digital)
Reset (digital)
IN8 - Variable Optional - Stop Permissive LD

(digital)
OUT1 - Variable Required - Start Output LD
(digital)
OUT2 - Variable Required - Stop Output LD
(digital)
(digital)
OW351_R1100 181
5.34 DIGITAL DEVICE
FI E L D RE C O R D
STAT - Variable Optional - Alarm and Mode LP

Status (packed)

(analog)
RUNT R1-Real Data Init Required 0 Tune the total -
runtime value
Truth Table
READ Y S TATU S R U N N I N G S TATU S M O TO R S TATE
Set Set Running

Set Reset Ready
Reset Set Failed
Reset Reset Unavailable
Output Status Bits
BI T DE S C R I P TI O N
0 Failed to Stop
1 Failed to Start
2 Not Applicable
3 Not Applicable
4 Not Applicable
5 Device Unavailable
6 Device Deviation
7 Device Failed
8 Last Command Stop
9 Last Command Start
10 Not Applicable
11 Not Applicable
12 Not Applicable
13 Device Off
14 Device in Manual
15 Device in Auto
182 OW351_R1100
5.34 DIGITAL DEVICE
5.34.5 M OT OR 2-SPD (T wo Speed or Bi-Directional Controlled M ot or)

Description
The Two-Speed or Bi-Directional Controlled Motor has the option of either running fast or slow, or
running forward or backward when in operation. This motor has the option of accepting start or
stop commands from either the control logic or the operator.
Fast/Forward Start (IN4), Remote Slow/Reverse Start (IN5), and Remote Stop (IN6) inputs. When
the device is in MANUAL mode, the algorithm accepts the control commands Stop, Fast/Forward
Start, and Slow/Reverse Start from the Operator Keyboard. Whenever a command is processed
in either AUTO or MANUAL mode, the outputs (OUT1, OUT2, and OUT3) are set accordingly for
the duration of the time delay previously set in the Control Builder.
automatically set when no input is connected to IN10. This motor may be commanded to change
direction or speed without first being stopped. Refer to the Algorithm Definitions table for the list of
inputs and outputs.
The digital alarm bit is set when one of the following occurs:
and continues looking for the combination of Running and Ready. When this combination has
been detected, the alarm is reset and the device continues operating in a normal condition. All
other alarms put the device in OFF mode. See the Truth table for the states of the motor.
The Two Speed or Bi-Directional Controlled Motor also has a status packed point that displays
which alarm has been set, the last command, and which mode it is currently in. See Output Status
Bits for the list of status bits.
Functional Symbol
OW351_R1100 183
5.34 DIGITAL DEVICE
FI E L D RE C O R D

Number
DLY1 C0-Integer Tuning Required 0 Time for Ready -
Constant after Stop

Constant
Constant Fast/Forward
Constant Slow/Reverse
BASE C6-Integer Tuning Optional 0 Time base for total -
Constant run:
0 = Hours
1 = Minutes
2 = Seconds
(digital)
IN2 - Variable Required - Fast/Forward LD
Running Contact
(digital)
IN3 - Variable Required - Slow/Reverse LD
Running Contact
(digital)
IN4 - Variable Optional - Remote LD
Fast/Forward Start
(digital)
IN5 - Variable Optional - Remote LD
Slow/Reverse Start
(digital)
IN6 - Variable Optional - Remote Stop LD
(digital)
(digital)
(digital)
Reset (digital)

(digital)
OUT1 - Variable Required - Fast/Forward Start LD
Output (digital)
184 OW351_R1100
5.34 DIGITAL DEVICE
FI E L D RE C O R D
OUT2 - Variable Required - Slow/Reverse Start LD

Output (digital)
OUT3 - Variable Required - Stop Output LD
(digital)
(digital)
Status (packed)
RUN Variable Optional Total Run Time LA

(analog)
RUNT R1 - Real Data Init Required 0 Tune the total -
runtime value.
Truth Table
R E AD Y S TATU S FAS T / F O R W AR D S L O W /R E V E R S E M O TO R S TATE

R U N N I N G S TATU S RU N N I N G S TATU S
Set Set Set Not Applicable
Set Set Reset Running Fast or

Forward
Set Reset Set Running Slow or

Reverse
Set Reset Reset Ready
Reset Set Set Failed

Reset Set Reset Failed
Reset Reset Set Failed
Reset Reset Reset Unavailable
Output Status Bits
0 Failed to Stop
1 Failed to Start Fast/Forward

2 Failed to Start Slow/Reverse
3 Not Applicable
4 Not Applicable
6 Device Deviation
OW351_R1100 185
5.34 DIGITAL DEVICE
7 Device Failed
8 Last Command Stop
9 Last Command Start Fast/Forward
10 Last Command Start Slow/Reverse
11 Not Applicable
12 Not Applicable
13 Device Off
14 Device in Manual
15 Device in Auto
186 OW351_R1100
5.34 DIGITAL DEVICE
5.34.6 M OT OR 4-SPD (T wo Speed and Bi-Directional Controlled M otor)
Description
The Two-Speed and Bi-Directional Controlled Motor has the option of accepting start or stop
commands from either the control logic or the operator. This motor has the option of running in
any one of the following four states:
 Fast and forward
 Fast and reverse
 Slow and forward
 Slow and reverse
Fast Forward Start (IN6), Remote Slow Forward Start (IN7), Remote Fast Reverse Start (IN8),
Remote Slow Reverse Start (IN9), and Remote Stop (IN10) inputs.
When the device is in MANUAL mode, the algorithm accepts t he control commands Stop, Fast
Forward Start, Slow Forward Start, Fast Reverse Start, and Slow Reverse Start from the Operator
Keyboard. Whenever a command is processed in either AUTO or MANUAL mode, the outputs
(OUT1, OUT2, OUT3, OUT4, and OUT5) are set accordingly for the duration of the time delay
previously set in the Control Builder.
automatically set when no input is connected to IN14. This motor may be com manded to change
direction or speed without first being stopped. See the Algorithm Definitions table for the list of
inputs and outputs.
and continues looking for the proper combination of Running and Ready. When this combination
is found, the alarm is reset and the device continues operating in a normal condition. All other
alarms put the device in OFF mode. See the Truth table for the states of the motor.
The Two-Speed and Bi-Directional Controlled Motor also has a status packed point that displays
which alarm has been set, the last command, and which mode it is currently in. See the Output
Status Bits table for the list of status bits.
OW351_R1100 187
5.34 DIGITAL DEVICE
Functional Symbol
FI E L D RE C .

Number
DLY1 C0-Integer Tuning Required 0 Time for Ready after -
Constant Stop

Constant
DLY3 C2-Integer Tuning Required 1 Time for Fast Forward -
Constant Start
DLY4 C3-Integer Tuning Required 1 Time for Slow Forward -
Constant Start
DLY5 C4-Integer Tuning Required 1 Time for Fast Reverse -
Constant Start
DLY6 C5-Integer Tuning Required 1 Time for Slow Reverse -
Constant Start
BASE C6-Integer Tuning Optional 0 Time base for total run. -
Constant
0 = Hours
1 = Minutes
2 = Seconds
RUNT R1 - Real Data Init Required 0 Tune the total runtime -
value.
IN1 - Variable Required - Ready Contact (digital) LD
188 OW351_R1100
5.34 DIGITAL DEVICE
FI E L D RE C .
IN2 - Variable Required - Fast Forward Running LD

Contact (digital)
IN3 - Variable Required - Slow Forward Running LD

Contact (digital)
IN4 - Variable Required - Fast Reverse Running LD
Contact (digital)
IN5 - Variable Required - Slow Reverse Running LD
Contact (digital)
IN6 - Variable Optional - Remote Fast Forward LD
Start (digital)
IN7 - Variable Optional - Remote Slow Forward LD
Start (digital)
IN8 - Variable Optional - Remote Fast Reverse LD
Start (digital)
IN9 - Variable Optional - Remote Slow Reverse LD
(digital)
IN10 - Variable Optional - Remote Stop (digital) LD
IN11 - Variable Optional - Remote Auto (digital) LD

(digital)
IN13 - Variable Optional - Remote Device Reset LD
(digital)

(digital)
OUT1 - Variable Required - Fast Forward Start LD
Output (digital)
OUT2 - Variable Required - Slow Forward Start LD

Output (digital)
OUT3 - Variable Required - Fast Reverse Start LD
Output (digital)
OUT4 - Variable Required - Slow Reverse Start LD
Output (digital)
OUT5 - Variable Required - Stop Output (digital) LD
ALRM - Variable Optional - Device Alarm (digital) LD

Status (packed)

(analog)
OW351_R1100 189
5.34 DIGITAL DEVICE
Truth Table
R E AD Y FAS T SL OW FAS T SL OW M O TO R S TATE

S TATU S FO R W AR D FO R W AR D RE V E R S E RE V E R S E
RU N N I N G RU N N I N G RU N N I N G RU N N I N G
S TATU S S TATU S S TATU S S TATU S
Set Set Set Set Set Not Applicable
Set Set Set Set Reset Not Applicable

Set Set Set Reset Set Not Applicable
Set Set Set Reset Reset Not Applicable
Set Set Reset Set Set Not Applicable
Set Set Reset Set Reset Not Applicable
Set Set Reset Reset Set Not Applicable
Set Set Reset Reset Reset Running Fast
Forward
Set Reset Set Set Set Not Applicable
Set Reset Set Set Reset Not Applicable

Set Reset Set Reset Set Not Applicable
Set Reset Set Reset Reset Running Slow
Forward
Set Reset Reset Set Set Not Applicable
Set Reset Reset Set Reset Running Fast

Reverse
Set Reset Reset Reset Set Running Slow

Reverse
Set Reset Reset Reset Reset Ready
Reset Set Set/Reset Set/Reset Set/Reset Failed

Reset Set/Reset Set Set/Reset Set/Reset Failed
Reset Set/Reset Set/Reset Set Set/Reset Failed
Reset Set/Reset Set/Reset Set/Reset Set Failed
Reset Reset Reset Reset Reset Unavailable
190 OW351_R1100
5.34 DIGITAL DEVICE
Output Status Bits
0 Failed to Stop
1 Failed to Start Fast Forward

2 Failed to Start Slow Forward
3 Failed to Start Fast Reverse
4 Failed to Start Slow Reverse
6 Device Deviation
7 Device Failed
8 Last Command Stop
9 Last Command Start Fast Forward
10 Last Command Start Slow Forward
11 Last Command Start Fast Reverse
12 Last Command Start Slow Reverse
13 Device Off
14 Device in Manual
15 Device in Auto
OW351_R1100 191
5.34 DIGITAL DEVICE
5.34.7 VALVE (Controlled Valv e)

Description
The Controlled Valve has the option of accepting commands from either the control logic or the
operator.
Open (IN3) and Remote Close (IN4) inputs. When the device is in MANUAL mode, the algorithm
accepts the control commands Close and Open from the Operator Keyboard. Whenever a
command is processed in either AUTO or MANUAL mode, the outputs (OUT1 and OUT2) are set
accordingly for the duration of the time delay previously set in the Control Builder.
The Open and Close Permissives (IN8 and IN9) must be set to allow the valve to be opened or
closed. The Open and Close Permissives are automatically set when no input is connected to IN8
or IN9. See the Algorithm Definitions table for the list of inputs and outputs.
 The device opens or closes without being commanded to do so.
 The device fails to open or close.
When the device fails to open or close, the alarm triggers , but the device stays in the current
mode and continues looking for the proper Open and Close input combination. When this
combination is found, the alarm is reset, and the device continues operating in a normal condition.
All other alarms put the device in OFF mode. See the Truth table for the states of the valve.
The Controlled Valve also has a status packed point that displays which alarm has been set, the
last command, and which mode it is currently in. See the Output Status Bits table for the list of the
status bits.
Functional Symbol
192 OW351_R1100
5.34 DIGITAL DEVICE
FI E L D RE C O R D

Number
DLY1 C0-Integer Tuning Required 1 Time for Close -
Constant
(should be
greater than loop
time)
DLY2 C1-Integer Tuning Required 1 Time for Open -
Constant
(should be
greater than loop
time)
IN1 - Variable Required - Open Contact LD
(digital)
IN2 - Variable Required - Close Contact LD
(digital)
IN3 - Variable Optional - Remote Open LD
(digital)
IN4 - Variable Optional - Remote Close LD
(digital)
(digital)
(digital)
Reset (digital)
IN8 - Variable Optional - Open Permissive LD

(digital)
IN9 - Variable Optional - Close Permissive LD
(digital)
OUT1 - Variable Required - Open Output LD
(digital)
OUT2 - Variable Required - Close Output LD
(digital)
(digital)
Status (packed)
OW351_R1100 193
5.34 DIGITAL DEVICE
Truth Table
OPEN S TATU S CLOSED S TATU S V AL V E S TATE
Set Set Moving
Set Reset Open

Reset Set Closed
Reset Reset Failed
Output Status Bits
0 Failed to Close
1 Failed to Open
2 Not Applicable
3 Not Applicable
4 Not Applicable
5 Not Applicable
6 Device Deviation
7 Device Failed
8 Last Command Close
9 Last Command Open
10 Not Applicable
11 Not Applicable
12 Not Applicable
13 Device Off
14 Device in Manual
15 Device in Auto
194 OW351_R1100
5.35 DISTRIBUTOR
5.35 DISTRIBUTOR
Description
The DISTRIBUTOR algorithm distributes an input signal (IN) into two or more (up to eight) analog
outputs (OUTx). The final value of the outputs will be the balance of the IN value, the number of
devices needed to satisfy the demands of the system, and other configuration options.
The DISTRIBUTOR algorithm is available in the Ovation 3.5 release and later.
Functional Symbol
Note: Track ing signals are not shown.
5.35.1 Input, FNUM parame ter, and O utput pins (IN, FNUM, and OUT [1-8])
All algorithms connected to the IN and OUTx pins are required to be on a scale of 0 to 100. If an
IN pin is out of this range, the algorithm will substitute the closest boundary as the input value. If
the calculated OUTx value is out of range, the algorithm defaults to the nearest limit.
The FNUM parameter is defined as the number of devices required to cover a full load. It has a
range from 1 to the maximum number of algorithms connected to the OUTx pins. FNUM's default
value is 0, which the algorithm interprets and sets the FNUM parameter to the number of OUTx
pins currently connected to downstream algorithms. For example, if FNUM is set to zero and
three OUTx pins are connected, then the algorithm will use 3 as FNUM's value. In the default
configuration, each of the OUTx pins will be equal to the IN value, because FNUM would be equal
to the number of OUTx pins connected. See the following figure.
Figure 3: Default Distributor Equation
OW351_R1100 195
5.35 DISTRIBUTOR
In the default Distributor equation shown above, IN = the input value, FNUM = the number of
devices needed to satisfy the system demand, and Nc = the number of connected OUT pins.
In most cases, the sum of all the OUTx values will equal the product of the IN value and FNUM.
Figure 4: Steady State Equation
Note: For simplicity, equations are presented with default parameters when Base Gains (BG)
are equal to 100% and Corrections Gains are equal to 1.0.
All OUTx pins that are connected to another algorithm must be connected consecutively with no
sk ipped OUTx pins.
You can specify a lower number FNUM than the number of points connected to the OUTx pins.
For example, a Distributor algorithm is controlling three valves equally (such as an MASTATION
opening/closing physical valves), but the demand for this application is, at most. only what two
valves can provide. If all three valves were open 100%, the system would be overloaded. When
you lower FNUM from the number of OUTx pins to a lesser number (in this case, two), it is
equivalent to lowering the total output of three devices to a maximum output of what two devices
can provide.
You can set FNUM to exceed the number of OUTx pins connected, but this will have no effect on
the algorithm. The Distributor algorithm will reset FNUM internally back to the default (that is, to
the maximum OUTx pins connected).
Some configurations or tracking signals may change the Default Equation for the OUTx pins, but
the algorithm will achieve the Steady State, if possible.
5.35.2 Exclusion (EXCL)
The Exclusion (EXCL) feature allows you to ignore OUTx pins already connected to the algorithm
(this includes the tracking TRINx signals) by selecting the unwanted pins (see Internal and
External Control (see page 203) for how OUTx can be selected). The Distributor algorithm
subtracts these pins from the number of connected pins in the default equation. In addition, the
excluded OUTx pins are excluded from the Steady State equation.
When the OUTx pin is excluded, the values of the outputs will not change. This is achieved by
setting the Track Out (TOUT) TRACKing bit for one loop cycle. The value of Track Out is
calculated as follows:
Figure 5: Value of TOUT in exclusion mode
196 OW351_R1100
5.35 DISTRIBUTOR
In exclusion mode, the value of the OUTx pin is calculated as follows:
Figure 6: Value of OUT pins with Exclusion applied
Note: For simplicity, equations are presented with default parameters when Base Gains are
equal to 100% and Corrections Gains are equal to 1.0.
Example
If the default settings are used, IN's value is set 50 and there are three OUTx pins connected,
each will equal 50. If one pin is excluded, TOUT will change from 50 to 33.3 and the TOUT
TRACKing bit will be set. Depending on what is driving the Distributor input, the IN value may
drop from 50 to 33.3. The remaining OUTx points would remain at 50 through the transition. Once
the excluded OUTx pins are included again, the algorithm recalculat es the OUTx values and will
move to the new values incrementally using the TRAT. When the newly included pin is re-
considered in the equation, TOUT's value may change drastically.
Based on the information above, the two OUTx pins that are not excluded are set to 75 and the
OUTx pin that was just included is 50. TOUT in this instance will jump to the average of the three
OUTx pins. TOUT will also pulse its TRACKing bit. In an MAStation, this will change the OUT pin
(and the Distributor's input) to equal the value of TOUT. All of the OUTx pins that were excluded
are then re-apportioned incrementally based on the moving values of the recently included pin.
The included OUTx pin is moving to the new OUTx value using the TRAT parameter (multiplied
by BGx).
OW351_R1100 197
5.35 DISTRIBUTOR
5.35.3 T racking Inputs (T KIN[1-8])
Tracking is applied to the input pin and all eight output pins (TRINx). When a downstream
algorithm sends one of the following tracking signals, the OUTx value will be controlled by the
downstream algorithm connected to it:
 High/low limit.
 TRACK bit (for example, an MAStation in manual mode).
 Lower/raise inhibit
Note: TRACK if higher and TRACK if lower are not implemented.
When the TRACK bit is set in TRINx, the Distributor relinquishes control of the OUTx value and
assigns the TRINx value directly to OUTx. The other OUTx values controlled by the Distributor
are redistributed depending on the TRINx values, as well as other changes in the algorithm.
Figure 7: Sum value of all the pins that are tracking
Figure 8: Value of an OUT pin that is NOT tracking
Where:
Tsum = Sum of track OUT pins

BG = Base Gain parameter
Nt = Number of track OUT pins
Note: For simplicity, the figure above does not consider Base Gain (BG) and Correction Gains.
If high limit or raise inhibit tracking bits are set and the IN value is going up, the Distributor
algorithm will freeze the OUTx value on the last OUTx value, all other OUTx values will shift to
achieve SteadyState. This also applies when the low limit or lower inhibit bit is set and the IN
value is going down. When both a high and a low signal are set on the same TRINx, the OUTx pin
will equal TRINx until one (or both) of the downstream signals are released.
When the OUTx pin(s) are released from their downstream tracking signals, the Distributor will
rebalance the OUTx pins. The TRAT is applied to the released pins until all the OUTx values are
balanced.
198 OW351_R1100
5.35 DISTRIBUTOR
5.35.4 Correction Gain

The Correction Gain (CGAIN) parameter is used to make minor corrections to each of the OUTx
equations dynamically through input pins or through a user diagram (see Internal and External
Control (see page 203)). The default value is 1.0. By default, each of the eight CGAIN (GAINx
pins and IGx parameters) must be between the values of 0.5 and 1.5. You can also define an
even smaller range by changing the CMIN and CMAX in the Control Builder (refer to Ovation
Control Builder User Guide for more information). The valid range for the CMIN parameter is 0.5
through 1.0 and the valid range for CMAX is 1.0 through 1.5. Inputs that ex ceed the range are
forced to the closest limit.
For the algorithm to reach Steady State, the sum of all the CGAIN inputs must equal the number
of all the attached OUTx pins. Since the correction gain can change, the current values may not
equal the number of OUTx pins all the time. To ensure equalization, each CGAIN is divided by the
"CGAIN Average." The new CGAIN values are then multiplied by the OUTx fields:
Figure 9: Average CGain value
Figure 10: Value of OUT[x] after CGain is applied
The CGAIN values will be applied in proportion to one another but will not unbalance the
algorithm's Steady State. For example, if all of the CGAIN values were equal to the maximum
value (1.5 or CMAX) and applied directly to the OUTx values, the Steady State equation would
not work. However, if CGAIN_Avg divides into each CGAINx value, it will work within the Steady
State equation.
Example 1: CGAIN = (1.5, 1.5, 1.5) and Steady State = 3
OUT1 = 1 OUT2 = 1 OUT3 = 1 Steady State

Org. Value of CGAINx 1 * 1.5 1 * 1.5 1 * 1.5 4.5 != 3
Value after CGAIN_Avg 1*1 1*1 1*1 3 == 3
Using CGAIN_Avg changes the value of the CGAINx, but the OUTx values will still be the same
proportional difference from each other. If the CGAINx values are 1.5, 1.5, and 0.7 for the first
three OUTx pins, OUT1 and OUT2 should be equal to one another, and OUT3 should be
proportionally less than the other OUTx values.
OW351_R1100 199
5.35 DISTRIBUTOR
Example 2: CGAIN = (1.5, 1.5, 0.7) and Steady State = 3
OUT1 = 1 OUT2 = 1 OUT3 = 1 Steady State

Org. Value of CGAINx 1 * 1.5 1 * 1.5 1 * 0.7 3.7 != 3
Value after CGAIN_Avg 1 * 1.216 1 * 1.216 1 * 0.567 3 == 3
Note: Values are rounded.
The GAINx inputs have tracking signals attached to them (TRKGx). The TRKGx value is equal to
the internal input value IGx (Internal and External Control (see page 203)). This is provided for
external applications that change the OUTx values. If external inputs are switched to user control,
the external applications will have the information needed to make a smooth transition before
handing over control to a user diagram.
5.35.5 Priority De adband (PDB)
The Priority Deadband (PDB) function is defined as the priority of outputs that will be used to
compensate for small changes in the IN value. This mechanism is designed to protect devices
against excessive wear. For example, when a change in the IN value is small, only one or a few
selected outputs should be used; the rest of the signals should not change in value.
The Priority Deadband mechanism requires you to define which outputs are set in priority mode
and what is the value of the deadband parameter. The Deadband parameter defines the maximal
difference between the priority output and other non-priority outputs. If the difference in the
current step would exceed the deadband value. then all output signals (priority and non-priority)
are used in the calculations for this step. The following formula defines how the output value in
Priority mode is calculated.
Figure 11: Value of an OUT pin that is selected in Priority Mode
Where:
NPsum = Sum of non-priority OUT pins

Nnp = Number of non-priority OUT pins
200 OW351_R1100
5.35 DISTRIBUTOR
Consider the following:

 Priority mode is held temporarily if the distance between the high limit and the current output
is smaller than the deadband.
 Priority mode is turned off permanently if the output is tracked (TRACK, raise/lower inhibit,
TRACK if higher/lower).
 If an excluded OUTx is selected as a PDB, it is only counted as an excluded output.
 Priority mode can only be applied to outputs when BG is 100.
For a general example for how PDB is applied, refer to the following table:
CU R R E N T V AL U E TO OUT1 OUT2 OUT3 OUT4

T I ME IN V AL U E D I S TR I B U TI O N ( P R I O R I TY) ( P R I O R I TY)
0 50 200 50 50 50 50
1 49 196 48 48 50 50
2 48 192 46 46 50 50
3 47 188 47 47 47 47
4 46 184 45 45 47 47
5 45 180 43 43 47 47
6 44 176 44 44 44 44
Time 3, 6 At this time, the values are distributed normally because the differences between
priority and non-priority points would be bigger than the priority deadband (PDB=5).
5.35.6 Base Gain
The Base Gain (BGx) parameter gives the ability to re-apportion the final OUTx signals. The
range of BGx is from 100 (the default) to five (5) and anything outside that range will be
considered equal to 100.
BGx is applied to the OUTx equation only after everything else has been calculated.
Figure 12: Value of the OUTx after Base Gain is applied
When none of the OUTx pins have reached a high limit (for example: OUTx >= 100), BGx will
simply be the equation shown above. However, if the BGx causes an OUTx value to exceed its
high limits, then the Distributor algorithm will set those OUTx parameters to their limits (for
example: OUTx = 100) and the downstream algorithms will set the High Limit flags in the returned
TRINx fields. These pins are considered at a High Limit and need to be treated as if the High Limit
Flag was already set. To solve the other OUTx values and keep the Steady State, the algorithm
must solve all the other OUTx values with the Tracking Equation.
OW351_R1100 201
5.35 DISTRIBUTOR
5.35.7 T racking Out (T OUT)
The Distributor algorithm takes the following action in response to the information found in the
analog track signals (in the third status field), which are passed back from the downstream
algorithm:
16 TRACK Implemented Refer to Internal and External Control

(see page 203).
17 Track if Lower -- Passed through
18 Track if Higher -- Passed through
19 Lower Inhibit Implemented Passed through
20 Raise Inhibit Implemented Passed through
21 Conditional Track -- --
22 Not Used -- --
23 Deviation Alarm -- --
24 Local Manual Mode -- --
25 Manual Mode -- --
26 Auto Mode -- --
27 Not Used -- --
28 Not Used -- --
29 Not Used -- --
30 Low Limit Reached Implemented Passed Through
31 High Limit Reached Implemented Passed Through
The Tracking Out (TOUT) value is calculated as follows:
Figure 13: Value of TOUT Equation
The TRACK bit is set for TOUT on the following occasions:
1. The tracking bit is Pulsed ON if the selected EXCL outputs have changed from the previous
Task Cycle.
2. The tracking bit is set ON continually if all OUTx pins are excluded and/or all TRINx TRACK
bits are set.
The Lower Inhibits bit is set if all outputs are limited from down (TRACK, low limit, lower inhibit)
and Steady State equation is not met.
202 OW351_R1100
5.35 DISTRIBUTOR
The Raise Inhibits bit is set if all outputs are limited from top (TRACK, high limit, raise inhibit) and
the Steady State equation is not met.
The Low Limit bit is set if all outputs (excluded pins are not counted) are on low limit (0.0). In this
case, the Lower Inhibit bit is set as well.
The High Limit bit is set if all outputs (excluded pins are not counted) are on high limit (100.0). In
this case, the Raise Inhibit bit is set as well.
The other bits are “passed though” from the TRINx pins to the TOUT pin only if all the TRINx pins
have the same signal(s) set. This does not count pins that are excluded.
5.35.8 Inte rnal and Exte rnal Control
The Distributor has several parameters that can accept inputs from pin(s), as well as fields from
inside the algorithm record, but never both at the same time. These are called "selectable inputs,"
and they apply to the optional features EXCL mode, PDB Mode, and GAINx inputs.
External:
1. Two packed 16-bit input pins control the EXCL and PDB features. The packed points are
used to select the OUTx pins that are connected. Bit 0 is equal to OUT1 and Bit 7 is equal to
OUT8. (Bits 8 through 15 are not used.) To select the OUTx pin(s), set and hold a "1" in the
correct bit. To deselect an OUTx pin(s), set the required bit to "0."
2. The Correction Gain uses eight analog input pins (GAINx). Each pin corresponds to an
attached OUTx pin.
Internal (Record Fields):
1. The EXCL and PDB each use a set of parameters for internal control (EXON\EXOFF and
PDON\PDOFF). One field is used to select OUTx pins, while the other field is used to deselect
OUTx pins. This parameter uses bit maps to choose the selected OUTx pins. For example, if
EXON = 0x5 then OUT1 and OUT3 will be selected. If EXOFF = 0x1, OUT1 is deselected, but
OUT3 remains unchanged. The fields reset to zero after they are applied to the algorithm.
2. The CGAIN uses eight LC record parameters to control the gain internally (IGx parameters).
External vs. Internal
FE ATU R E S EX TE R N AL I N TE R N AL
Exclusion XSEL EXON\EXOFF

Priority Deadband PSEL PDON\PDOFF
Correction Gain GAINx IGx
Note: The use of the selectable pins are optional. If the pins are not used, the operator must
use the internal fields in order to utilize this feature.
OW351_R1100 203
5.35 DISTRIBUTOR
5.35.9 Switching Be tween Inte rnal and Exte rnal Inputs
You can switch between internal algorithm fields or external algorithm pins for EXCL mode, PDB
mode, and CGAIN. This can be done as follows:
1. The command signal pin (CMD) - a 16-bit packed point input pin:
a) To turn the input pin(s) ON for a specific function (and accept input from an external
application), the appropriate bit (1, 3, 5) must be set to "1."
b) To turn the input pin(s) OFF for a specific function (and accept input from the internal
algorithm field), the appropriate bit (0, 2, 4) must be set to "1."
c) If both appropriate bits (0, 1) or (2, 3) or (4, 5) are set to "1," the input pin(s) will be turned
OFF.
d) If both the appropriate bits (0, 1) or (2, 3) or (4, 5) are set to "0," the state will depend on
internal algorithm fields (see #2 below).
Note: The signals can be pulsed or held. If these signals are held at 1, you will not be able to
change its state from the internal algorithm fields.
2. The internal algorithm fields Y[0 - 5]:

a) To turn the input pin(s) ON for a specific function (and accept input from an external
application), the appropriate field (Y0, Y2, Y4) must be set to "1."
b) To turn the input pin(s) OFF for a specific function (and accept input from an internal
algorithm field), the appropriate field must be set to "1" (Y1, Y3, Y5).
c) If both fields are set to "1" for a specific function, the input pin(s) will be turned OFF.
d) If both fields are set to "0" for a specific function, the input pin(s) will not be changed.
e) The field is reset to "0" after the command(s) are read..
3. Special Case situations:
a) The Y0 field is set and the CMD:Bit 1 field is set at the same time (opposite commands
for the same function). If there is a conflict between CMD and the Y fields, the CMD pin
takes priority.
16-Bit Packed Point - CMD
Bits 0 and 1 Turn Correction Gain Control Pins ON/OFF

Bits 2 and 3 Turn the Exclusion Control Pin ON/OFF
Bits 4 and 5 Turn the Priority Control Pin ON/OFF
Bits 6 through 15 Not Implemented.
Algorithm Record Fields
Y0 and Y1 Turn Correction Gain Control Pins ON/OFF (GAIN[1 - 8] pins)
Y2 and Y3 Turn the Exclusion Control Pin ON/OFF (EXCL packed point)
Y4 and Y5 Turn the Priority Control Pin ON/OFF (PSEL packed point)
204 OW351_R1100
5.35 DISTRIBUTOR
Control type examples
C O N TR O L AL G O R I TH M 1 6 -BI T P AC K E D
T YP E RE F E R E N C E P O I N T " CMD" RE S U L TS
S TATE ON OFF ON OFF

EX AM P L E Y0 Y1 BI T 1 BI T 0
0 FALSE FALSE FALSE FALSE State does not change.

1 FALSE FALSE FALSE TRUE CMD changes the state to OFF.
2 FALSE FALSE TRUE FALSE CMD changes the state to ON.
3 FALSE FALSE TRUE TRUE CMD changes the state to OFF.
4 FALSE TRUE FALSE FALSE Algorithm field changes the state to OFF.
5 FALSE TRUE FALSE TRUE CMD changes the state to OFF.
6 FALSE TRUE TRUE FALSE CMD changes the state to ON.
7 FALSE TRUE TRUE TRUE CMD changes the state to OFF.
8 TRUE FALSE FALSE FALSE Algorithm field changes the state to ON.
9 TRUE FALSE FALSE TRUE CMD changes the state to OFF.
10 TRUE FALSE TRUE FALSE CMD changes the state to ON.
11 TRUE FALSE TRUE TRUE CMD changes the state to OFF.
12 TRUE TRUE FALSE FALSE Algorithm field changes the state to OFF.
13 TRUE TRUE FALSE TRUE CMD changes the state to OFF.
14 TRUE TRUE TRUE FALSE CMD changes the state to ON.
15 TRUE TRUE TRUE TRUE CMD changes the state to OFF.
5.35.10 First Pass Startup Options
There is a data init parameter for each of the selectable inputs to determine whether the input
pins are ON or OFF after first pass startup. If the pins XSEL and/or PSEL are OFF for the first
pass, an engineer can set the internal value of the EXCL and PBD selection bitmaps with the
FPEX and FPPR parameters. For example, an engineer can set FPEA to OFF , which will turn off
the XSEL pin for the first time the algorithm runs. Then they can exclude OUT1 and OUT3 for the
first pass by setting FPEX to 0x05.
First Pass Startup Options
FE ATU R E S FI R S T P AS S S TATE FI E L D S I N I T V AL U E S (O N L Y I F TH E P I N
I S OFF)
Exclusion FPEA (XSEL is ON/OFF after First FPEX (if FPEA is OFF)
pass)
Priority Deadband FPPA (PSEL is ON/OFF after First FPPR (if FPPA is OFF)
pass)
Correction Gain FPGA (GAINx is ON/OFF after First IG[1-8] (if FPGA is OFF)
pass)
OW351_R1100 205
5.35 DISTRIBUTOR
STAT1 Pins
B I TS DE S C R I P TI O N
0-7 A bitmap of OUTx pins that the Distributor has control over
8 GAIN input pins that are active
9 PDB input pins that are active
10 EXCL input pins that are active.
11 Track if Lower and Track if Higher conditions are active.
STAT2 Pins
0-7 Bitmap of EXCL selected OUTx

8 - 15 Bitmap of PDB selected OUTx
5.35.11 Point Quality
Quality is propagated from the IN pin to all OUTx pins that are excluded. If a point is excluded, the
value and quality is taken from the TRIN point.
5.35.12 SID Storage
In order to assist with graphics programming, all output point SIDs are stored in fields in the
algorithm. This allows the graphic to access multiple SIDs by accessing a single SID (the
5.35.13 Distributor Algorithm De finitions
FI E L D RE C O R D
Inputs (with attached Tracking signals)
IN D0 - SID Variable Required - Input (analog) LA

T1 - Value
TOUT Variable Required - Track output value LA
mode and status
signals for input
variable
GAIN1 S1 - Value Variable Optional - External Correction LA
Gain 1
206 OW351_R1100
5.35 DISTRIBUTOR
FI E L D RE C O R D
TRKG1 Variable Optional - Tracking Correction LA

Gain 1. This outputs
the value of IG1 (R1
field).
Gain 2
field).
Gain 3
field).
Gain 4
field).
Gain 5
field).
Gain 6
field).
Gain 7
field).
Gain 8
field).
OW351_R1100 207
5.35 DISTRIBUTOR
FI E L D RE C O R D
CMD G7 - Value Variable Optional - External Command LP

(16-bit Pack):
 Bits 0 and 1: GAIN#
pins (ON/OFF)
 Bits 2 and 3: XSEL
pin (ON/OFF)
 Bits 4 and 5: PSEL
pin (ON/OFF)
PSEL G8 - Value Variable Optional - Select OUTx to apply LP
the Priority deadband.
 Bits 0 - 7 used to
select OUTx pins.
(Hold bits TRUE to
Select Outputs)
XSEL G9 - Value Variable Optional - Select OUTx to LP
Excluded.
 Bits 0 - 7 used to
select OUTx pins.
(Hold bits TRUE to
Select Outputs)
Outputs (with attached Tracking signals):
OUT1 YQ - SID Variable Required - Analog Output 1 LA

T2 - Value
TRIN1 Variable Required - Tracking Input for LA
OUT1
OUT2 D2 - SID Variable Optional - Analog Output 2 LA
T3 - Value
TRIN2 Variable Optional - Tracking Input for LA
OUT2
OUT3 YP - SID Variable Optional - Analog Output 3 LA
T4 - Value
OUT3
T5 - Value
OUT4
T6 - Value
OUT5
T7 - Value
OUT6
208 OW351_R1100
5.35 DISTRIBUTOR
FI E L D RE C O R D
OUT7 YN - SID Variable Optional - Analog Output 7 LA

T8 - Value
TRIN7 Variable Optional - Tracking input for LA
OUT7
OUT8 D8 SID Variable Optional - Analog Output 8 LA
T9 Value
OUT8
STAT2 Variable Optional - Status (See "Stat2" LP
table)
STAT1 Variable Optional - Status 1 (See "Stat1" LP
table)
Parameters:
BG1 X1 Data Init Required 100 Base Gain 1 -

FPEA X9 Bit 2 Data Init Required OFF XSEL pin ON/OFF for -
the algorithm's
startup.
FPPA X9 Bit 4 Data Init Required OFF PSEL pin ON/OFF for -
the algorithm's
startup.
FPGA X9 Bit 0 Data Init Required OFF GAINx pins ON/OFF -
for the initial
algorithm's startup.
CGON *Y0 Variable Required 0 Internal command to -
turn GAINx pins "ON."
CGOFF *Y1 Variable Required 0 Internal command to -
turn GAINx pin
"OFF."
CEON *Y2 Variable Required 0 Internal command to -
turn the XSEL pin
"ON."
CEOFF *Y3 Variable Required 0 Internal command to -
turn the XSEL pin
"OFF."
OW351_R1100 209
5.35 DISTRIBUTOR
FI E L D RE C O R D
CPON *Y4 Variable Required 0 Internal command to -

turn the PSEL pin
"ON."
CPOFF *Y5 Variable Required 0 Internal command to -
turn the PSEL pin
"OFF."
FPEX G1 Data Init Required 0 If the FPEA is "OFF," -
then this is the
internal bit map of
Excluded OUTx pins
for initial algorithm
startup.
EXON *G2 Variable Required 0 Internal Command to -
Select OUTx pins to
Exclude. Reset to
zero after selection is
accepted. Only valid if
XSEL is turned
"OFF." (Range: 0x00
to 0xFF)
EXOFF *G3 Variable Required 0 Internal Command to -
deselect OUTx pins to
Exclude. Reset to
XSEL is turned
"OFF." (Range: 0x00
to 0xFF)
FPPR G4 Data Init Required 0 If the FPPA is "OFF," -
then this is the
internal bit map of
Excluded OUTx pins
for initial algorithm
startup.
PDON *G5 Variable Required 0 Internal Command to -
Select OUTx pins to
apply Priority
deadband. Reset to
PSEL is turned
"OFF." (Range: 0x00
to 0xFF)
PDOFF *G6 Variable Required 0 Internal Command to -
Select OUTx pins to
apply Priority
deadband. Reset to
PSEL is turned
"OFF." (Range: 0x00
to 0xFF)
210 OW351_R1100
5.35 DISTRIBUTOR
FI E L D RE C O R D
CMDVL G7 Variable Required 0 Information about -

CMD pin map.
PSELV G8 Variable Required 0 Information about -
PSEL pin map.
XSELV G9 Variable Required 0 Information about -
XSEL pin map.
CMIN U2 Data Init Required 0.5 Correction Gain's -
lowest value. Valid
range: 0.5 to 1.0
CMAX U3 Data Init Required 1.5 Correction Gain's -
highest value. Valid
range: 1.0 to 1.5
TRAT R9 Tuning Required 2.5 Track Ramp Rate. -
Constant
This is only applied to
situations that an
OUTx pin is released
from tracking or
Exclusion. TRAT is
always multiplied by
the OUTx pin's Base
Gain
TRAT = (TRAT *
100/BG[x])
PRDB S9 Tuning Required 5 Priority Deadband -
Constant value
TRDB V1 Tuning Required 1.0 Deadband for Track -
Constant conditions
OW351_R1100 211
5.35 DISTRIBUTOR
FI E L D RE C O R D
FNUM C0 Data Init Required 0 Number of devices -

needed to satisfy the
system demand. This
can never be more
than the devices
connected.
 0: Count of all
devices connected
to the OUTx pins.
 1: One device is
needed.
 2: Two devices are
needed.
 3: Three devices
are needed.
 4: Four devices are
needed.
 5: Five devices are
needed.
 6: Six devices are
needed.
 7: Seven devices
are needed.
 8: Eight devices are
needed.
IG1 R1 Tuning Required 1 Internal Correction -
Constant Gain 1
Constant Gain 2
Constant Gain 3
Constant Gain 4
Constant Gain 5
Constant Gain 6
Constant Gain 7
Constant Gain 8
VER U1 Alg Init Variable 0 Version of the -
Distributor
COMAP B0 Alg Init Variable 0 Bitmap of Connected -
OUTx
212 OW351_R1100
5.35 DISTRIBUTOR
FI E L D RE C O R D
ACMAP B1 Alg Init Variable 0 Bitmap of active -

OUTx pins. (These
are OUTx pins that
are not excluded,
tracking, ramping)
PAMAP B2 Alg Init Variable 0 Bitmap of passive -
OUTx pins. (These
are OUTx pins that
are excluded or
tracking.)
REMAP YU Alg Init Variable 0 Bitmap of released -
OUTx pins. (These
are OUTx pins that
are ramping.)
SPMAP B4 Alg Init Variable 0 Bitmap of tracking -
OUTx pins
EXCL B5 Alg Init Variable 0 Selected OUTx pins -
that are Excluded
(Bitmap)
PDB B6 Alg Init Variable 0 Selected OUTx pins -
that are PDB (Bitmap)
TRMAP C1 Alg Init Variable 0 Bitmap of OUTx pins -
that have
"_3W_Track_Bit_"
set.
LOWTR C2 Alg Init Variable 0 Bitmap of OUTx pins -
that have
_3W_LOW_TRACK_
set
HITRK C3 Alg Init Variable 0 Bitmap of OUTx pins -
that have
_3W_HIGH_TRACK_
set
LOLIM C4 Alg Init Variable 0 Bitmap of OUTx pins -
that have
_3W_LOW_LIMIT_
set
HILIM C5 Alg Init Variable 0 Bitmap of OUTx pins -
that have
_3W_HIGH_LIMIT_
set
OW351_R1100 213
5.35 DISTRIBUTOR
FI E L D RE C O R D
INLMP C6 Alg Init Variable 0 Bitmap of OUTx pins -

that have
_3W_LOWER_
INHIBIT_set
C7 Alg Init Variable 0 Bitmap of OUTx pins -
INHMP
that have
_3W_HIGH_INHIBIT_
set
* The asterisk indicates that this is a command field, not a feedback field. A command field can be used
as a user-interface to the algorithm. It drives the algorithm to perform a function.
214 OW351_R1100
5.36 DIVIDE
5.36 DIVIDE
Description
The DIVIDE algorithm divides two gained and biased inputs. The output of the DIVIDE algorithm
is the result of the gained and biased IN1 divided by the gained and biased IN2. If the gained and
biased IN2 is zero, or an invalid real number, then the output is either the high or low limit
according to the sign of the IN1.
Note: If the algorithm receives an invalid value as the input, or if it calculates an invalid value as
the output, the drop is placed into alarm.
Functional Symbol
Tracking Signals
Tracking and limiting are done through signals passed in the third status field of an analog point to
the algorithm. This algorithm takes the following action in response to the information found in the
input signal TRIN:
Bit description
16 Track Implemented Passed through
17 Track if lower No action Passed through*
18 Track if higher No action Passed through*
19 Lower inhibit No action Passed through**
20 Raise inhibit No action Passed through**
21 Conditional Track Implemented Passed through***
22 Not used No action Not used
23 Deviation Alarm No action Not used
24 Local Manual mode No action Not used
25 Manual mode No action Not used
26 Auto mode No action Not used
27 Not Used No action Not used
OW351_R1100 215
5.36 DIVIDE
30 Low limit reached No action Low limit reached
31 High limit reached No action High limit reached
* Only when the Track signal is not present.
** Only when the Track signal is not present; the signals are set according to the
definitions given in Setting Tracking Signals (see page 15).
*** If the algorithm is being told to track, then the Conditional track bit is ignored.
Otherwise, the value of the conditional track bit is transferred to all output track points.
If the Conditional Track bit is set in the track input point, the analog value of all output
track points is calculated based on the analog value of the track input point.
The high and low limit flags and the tracking signals from the algorithms are outputs to TOUT, to
be used for display and by an upstream algorithm. If the output value is invalid, the quality of OUT
is set BAD otherwise, the quality of OUT is set to the worst quality of the two inputs when not in
tracking mode. When tracking, the quality is set to the quality of the track input variable.
Note: If the algorithm generates an inverted track output, the IN1 value is used as t he track
output, unless it is invalid, The track output value is not updated if both the calculated track
output and INI input values are inverted.
FI E L D RE C O R D

Number
IN1G R1-Real Tuning Required 1.0 Gain (+ or -) on -
(NUMG) Constant input 1
IN1B R2-Real Tuning Required 0.0 Bias (+ or -) on -

(NUMB) Constant input 2
IN2G R3-Real Tuning Required 1.0 Gain on input 2 -

(DENG) Constant
IN2B R4-Real Tuning Required 0.0 Bias on input 2 -

(DENB) Constant
TPSC R5-Real Tuning Required 100.0 Maximum value of -

Constant the output point
BTSC R6-Real Tuning Required 0.0 Minimum value of -

216 OW351_R1100
5.36 DIVIDE
FI E L D RE C O R D
TRAT R7-Real Tuning Required 2.5 Track ramp rate -

Constant (units per second)
TBLK X3 - Byte Data Init. Required ON Enable tracking -

Bit 0 calculations and
local memory
operations. The
choices are:
 ON
 OFF
NUM - Variable Required - Input (analog) LA
(IN1)
TOUT - Variable Required - Track output LA

value, mode &
status for input
variable
DEN - Variable Required - Input (analog) LA
(IN2)
TRIN - Variable Optional - Tracking analog LA

value, tracking
and limiting mode
signals input
variance
Function
OW351_R1100 217
5.37 DROPSTATUS
5.37 DROPSTATUS
Description
The DROPSTATUS algorithm accesses and outputs the contents of any record field in the Drop
Status Record (DU) for a particular Controller. To access the contents of a record field, the field
number must be specified. If an invalid field number is entered, zero is written to the AOUT and
POUT output points.
The data in the DU record field is output as a packed point. If specified, the contents of the record
field can also be output as an analog value. (Refer to the Ovation Record Types Reference
Manual.)
Note: For Ovation 3.2 systems and later, the DROPSTATUS algorithm will allow any DU record
to be used as an input into the drop status.
Functional Symbol
Field Numbers
FI E L D NU MB E R FI E L D N AME
1 FA
2 FB
3 FC
4 FK
5 FS
6 FO
7 HC
8 TA
9 CT
10 RT
11 LN
12 E5
13 E6
14 GD
15 GL
218 OW351_R1100
5.37 DROPSTATUS
FI E L D NU MB E R FI E L D N AME
16 GI
17 GG
18 GH
19 NC
20 FF
21 JU
22 U4
23 U5
24 U6
25 U7
26 KM
27 VE
28 K0
29 K1
30 TR
31 NE
32 IS
33 IE
34 OP
35 OE
OW351_R1100 219
5.37 DROPSTATUS
FI E L D RE C O R D
RECD G0 - Data Init. Required 0 The field number in -

Integer the drop record.
AOUT - Variable Optional - Output (analog); LA

contents of the DU
record field.
POUT - Variable Required - Output (packed); LP
contents of the DU
record field.
DUID - Variable Optional - Input DU record DU
220 OW351_R1100
5.38 DRPI1A
5.38 DRPI1A
Description
The DRPI1A algorithm converts the gray codes (IN1) to actual rod positions. On the first pass, the
rod position is always a zero value with BAD quality. For control rods, the calculation for
converting gray codes into steps is converting the gray code to a decimal number and adding the
two gray codes together and multiplying the sum by STEP. If there is an error reading either gray
code, or if the gray code is above the maximum range, only the good code is used in the
calculation and the resultant quality is set to FAIR. If gray code A is BAD, then the rod position is
equal to: ((converted gray code B times 2 times STEP) + (1/2 times STEP)). If the gray code B is
BAD, then the rod position is equal to: ((converted gray code A times 2 times STEP) - (1/2 times
STEP)). If both gray codes are BAD or above the limits, then the rod position is set to zero with
BAD quality.
If the rod is a shutdown rod and the converted gray codes added together equal BOTS, then the
rod position is equal to GAP and POOR quality. If the converted gray codes added together is
greater than BOTS, then the rod position is equal to TOPG plus the calculated position.
If bit 12 of IN1 is set, then the algorithm sets a two-second timer. When the timer expires, the
algorithm saves the current rod being scanned. During the first scan of any rod after the two
second timer has expired, a rod value of zero is allowed. At all other times a zero is not valid. If a
zero is not allowed, then any zero reading is ignored by setting the rod number (RODZ) to zero.
Functional Symbol
FI E L D RE C O R D

Number
MNIN R1-Real Tuning Required 0.0 Maximum number -
Constant of steps per rod
GAP R2-Real Tuning Required 0.0 Shutdown Rod Gap -

Constant
TOPG R3-Real Tuning Required 0.0 Shutdown Top Gap -
Constant
FUEL R4-Real Tuning Required 0.0 Maximum Steps for -
Constant Rapid Refuel
BOTS G0-Integer Tuning Required 4 Number of Bottom -
Constant Coils for Shutdown
Rod
OW351_R1100 221
5.38 DRPI1A
FI E L D RE C O R D
MAXS G1-Integer Tuning Required 6 Maximum Coils in -

Constant Shutdown Rod
STEP G2-Integer Tuning Required 6 Number of Steps -
Constant Between Coils
IN1 - Variable Required 0 Input (packed): LP
Bits 0 - 4 = Gray
Bit 5 = Gray Code
A
Error Bit
Bits 6 - 10 = Gray
Code B
Bit 11 = Gray Code
B
Error Bit
Bit 12 = CD24
Monitor.
Indicator that zero
value can be
accepted.
Bit 13 = Rapid
Refuel in
progress
ROD - Variable Required - Rod Number Input LA
(analog)
SHUT - Variable Required - Shutdown Control LD, LP

Rod
Input (digital)
TRIP - Variable Optional - Unit Trip Input LD, LP
(digital)
OUT - Variable Required - Rod Position LA
Output (analog)
RODZ - Variable Required - Rod Number or LA

zero
Output (analog)
222 OW351_R1100
5.39 DVALGEN
5.39 DVALGEN
Description
The DVALGEN algorithm initializes a digital point. For the DVALGEN algorithm, the output is the
digital value stored in the tuning constant (VALU). This value can be used to force any digital
input to any algorithm to either a TRUE or FALSE statement that remains fixed unless changed
by a tuning function.
Functional Symbol
FI E L D RE C O R D
DIAG LU- Data Init. Required 69 Tuning Diagram -

Integer Number
VALU R1-Real Tuning Required 1.0 Real value -
Constant (0.0 = FALSE;
1.0 or any other non-
zero,
real number = TRUE)
Function
OUT = VALUE
OW351_R1100 223
5.40 DXCSTATUS
5.40 DXCSTATUS
Description
The Digital eXcitation Controller algorithm (DXCSTA TUS ) interfaces with the Digital Excitation
Controller (DEC) module for the purpose of reconciling the module’s tuning parameters with the
Ovation Database Server.
Note: For more information on the DEC module, refer to the Digital eXcitation Controller User
Guide and the Ovation Bus and Specialty I/O Reference Manual.
The DXCSTATUS algorithm interacts with the DEC module to:
 Exchange tuning parameters and site rating parameters with the module. Parameters can be
uploaded from and downloaded to the module using a custom graphic.
 Reconcile tuning parameters and site rating parameters with the Ovation Database Server.
 Perform on-demand calibration of excitation module inputs.
 Swap control between modules in a redundant system.
The DXCSTAUS algorithm operates in conjunction with a single excitation module or a redundant
pair of modules.
Functional Symbol
The following table describes the DXCSTATUS algorithm inputs.
DXCSTATUS algorithm inputs
NAME DE S C R I P TI O N
ACMD Algorithm command word input from control logic.

RDNT Indicates redundant configuration.
ENBL Enables the DXCSTATUS algorithm.
224 OW351_R1100
5.40 DXCSTATUS
The following table describes the DXCSTATUS algorithm output.
DXCSTATUS algorithm output
NAME DE S C R I P TI O N
ASTA1 Algorithm status word output to control logic for primary module.
ASTA2 Algorithm status word output to control logic for partner module.
STATE Algorithm internal state (see state diagram).
Algorithm Parameters
The following table describes the DXCSTATUS algorithm parameters.
 DSTA, DST2 -- Status returned by the driver after a processing command requests from the
algorithm. DSTA is the status returned from the module. DST2 is the status returned from the
redundant module.
 DIAG -- Tuning diagram number.
 DVNM -- Device number for Ethernet I/O.
 HWA1, HWA2 -- Hardware address of module and redundant module, respectively.
 Module tuning parameters.
 Module site rating parameters.
Note: Custom graphics are typically used to modify the site ratings parameters.
Most of the algorithm parameters consist of DEC module tuning parameters and site rating
parameters. A complete list of algorithm parameters appears in the Algorithm parameters table.
Initial values for module tuning parameters are specified as the default values for the parameters
in the DXCSTA TUS algorithm.
Note: In the following table, all parameters are required.
Algorithm parameters
N AME RE C O R D T YP E RE C O N C I L E TU N I N G DE F AU L T DE S C R I P TI O N
FI E L D R ATI N G
C ON F I G.
DVNM G1 Integer No N/A 0 Device number.

HWA1 G6 Int No N/A 0.0 Card hardware
address.
HWA2 G7 Int No N/A 0.0 Redundant card
hardware address.
DSTA G4 LP No N/A 0 Driver status.
DST2 G5 LP No N/A 0 Driver status second
module.
ERR1 G8 Int No N/A 0 Error code primary
module.
OW351_R1100 225
5.40 DXCSTATUS
FI E L D R ATI N G
C ON F I G.
ERR2 G9 Int No N/A 0 Error code partner

module.
DEC Tuning Information

DCKI R1 Yes Tuning 10 Inner loop integral
Real
Constant gain for AC control,
in volts DC / (per unit
* sec).
DCKP R2 Real Yes Tuning 10 Inner loop
Constant proportional gain for
AC control, in volts
DC / per unit.
ACKD R3 Real Yes Tuning 0 Derivative gain for
Constant the AC controller, in
volts DC * sec / in
fractional percent.
ACKI R4 Real Yes Tuning 20 AC controller integral
Constant gain for voltage
control, in 1 / sec.
ACKP R5 Real Yes Tuning 20 AC controller
Constant proportional gain for
voltage control, in
per unit.
KS1H R6 Real Yes Tuning 1.0 PSS variable, high
Constant range (normal) gain
of PSS, in per
unit/pu.
KS1L R7 Real Yes Tuning 1.0 PSS variable, low
Constant range (attenuated)
gain of PSS, in per
unit/pu.
KS1M R8 Real Yes Tuning 0.5 PSS variable, high
Constant range load to use
KS1H for PSS, in per
unit.
KS1N R9 Real Yes Tuning 0.45 PSS variable, low
Constant range load to use
KS1L for PSS, in per
unit/pu.
KS2 S1 Real Yes Tuning 0.78 PSS variable,
Constant integrator gain -
normally = T7/2H, in
per unit/pu.
KS3 S2 Real Yes Tuning 1.0 PSS variable,
Constant summation gain -
normally 1, in per
unit/pu.
226 OW351_R1100
5.40 DXCSTATUS
FI E L D R ATI N G
C ON F I G.
KSG S3 Real Yes Tuning 0.707 PSS variable,

Constant internal signal
generator gain -
amplitude control,
unitless.
KTI S4 Real Yes Tuning 0.01 PSS variable, test
Constant signal gain, in per
unit / volts DC.
LL1E X0 Byte Yes Tuning 1 PSS variable,
Constant enables the first
lead/lag filter:
 0 = disable
 1 = enable
Constant enables the second
lead/lag filter:
 0 = disable
 1 = enable
Constant enables the third
lead/lag filter:
 0 = disable
 1 = enable
UEKI S5 Real Yes Tuning 4 Integral gain of MEL,
Constant in fractional percent
terminal voltage (.%
MVA * sec).
UEKP S6 Real Yes Tuning 2 MEL proportional
Constant gain, in fractional
percent terminal
voltage / (.% MVA).
OEKI S7 Real Yes Tuning 15 MXL integrator gain,
Constant in fractional percent
terminal voltage / (.%
current * sec).
OEKP S8 Real Yes Tuning 10 MXL proportional
Constant gain, in fractional
percent terminal
voltage / .% Ifld.
NCHE X3 Byte Yes Tuning 0 PSS variable,
Constant enables the notch
filter:
 0 = disable
 1 = enable
NCHF S9 Real Yes Tuning 9.0 PSS variable, center
Constant frequency for the
notch filter, in Hz.
OW351_R1100 227
5.40 DXCSTATUS
FI E L D R ATI N G
C ON F I G.
NCHQ T1 Real Yes Tuning 10.0 PSS variable, quality

Constant factor for notch filter,
unitless.
PSSF T2 Real Yes Tuning 1.0 Scale factor to
Constant permit derating the
AC controller PID
gains if the PSS is
not operational,
unitless.
PSMW T3 Real Yes Tuning 0.1 PSS variable, sets
Constant the maximum value
of MW at which the
PSS will turn off, in
per unit.
PSOF T4 Real Yes Tuning 0.15 PSS variable, sets
Constant the minimum value
of MW at which the
PSS will turn on, in
per unit.
RTFE X4 Byte Yes Tuning 1 PSS variable, used
Constant to enable the ramp
tracking filter:
 0 = disable
 1 = enable
RTFM G2 Int Yes Tuning 5 PSS variable, ramp-
Constant tracking filter
exponent of
denominator,
unitless.
RTFN G3 Int Yes Tuning 1 PSS variable, ramp-
Constant tracking filter
exponent, unitless.
PST1 T5 Real Yes Tuning 0.1 PSS lead time
Constant constant in seconds.
PST2 T6 Real Yes Tuning 0.03 PSS lag time
PST3 T7 Real Yes Tuning 0.09 PSS lead time
PST4 T8 Real Yes Tuning 0.03 PSS lag time
PST7 T9 Real Yes Tuning 5 PSS integrator time
PEW1 X5 Byte Yes Tuning 1 PSS variable,
Constant washout filter 1
enable:
 0 = disable
 1 = enable
228 OW351_R1100
5.40 DXCSTATUS
FI E L D R ATI N G
C ON F I G.

enable:
 0 = disable
 1 = enable
enable:
 0 = disable
 1 = enable
enable:
 0 = disable
 1 = enable
PSOE X9 Byte Yes Tuning 1 PSS variable,
Constant enables the stabilizer
output:
 0 = disable
 1 = enable
AUX1 LC N/A No - - DXCSTATUS -
Auxiliary 1
Auxiliary 2
Auxiliary 3
AUX1: AN Char No - - -
AN
AN
AN
AUX1: R1 Real Yes Tuning 15 VHL integrator gain,
VHLI Constant in fractional percent
of terminal voltage /
PT VAC.
AUX1: R2 Real Yes Tuning 10 VHL controller
VHLP Constant proportional gain, in
fractional percent of
terminal voltage /
(PT VAC * sec).
AUX1: R3 Real Yes Tuning 0.05 PSS variable,
PSVT Constant stabilizer output
maximum limit, in
per unit.
OW351_R1100 229
5.40 DXCSTATUS
FI E L D R ATI N G
C ON F I G.
AUX1: R4 Real Yes Tuning -0.05 PSS variable,

PSVB Constant stabilizer output
minimum limit, in per
unit*/.
AUX1: R5 Real Yes Tuning 0.45 Compensation
PSXQ Constant reactance for internal
voltage calculation,
in per unit.
AUX1: R6 Real Yes Tuning 0.004 Maximum rate of
SCLR Constant change of the SCL
output, in per unit /
sec.
AUX1: R7 Real Yes Tuning 1.0 Inner loop feedback
KF2 Constant gain, in per unit.
AUX1: R8 Real Yes Tuning 0.15 Difference limit alarm
CTDL Constant set point for a dual-
CT system, units of
fractional
percentage.
AUX1: R9 Real Yes Config 1000 Machine current
CTR transformer ratio, in
AAC/AAC.
AUX1: X0 Enum Yes Config 0 Selects the exciter
EXCT type, which selects
the appropriate
control algorithm:
 0 = BRUSHLESS
 1 = STATIC
AUX1: S1 Real Yes Config 0.052 PT loss-of-sensing
FAIT timeout before a
failure condition is
declared, in
seconds.
AUX1: S2 Real Yes Config 0.1 PT loss-of-sensing
FAUT timeout before a fault
condition (for
example, three-
phase short to
ground) is declared,
in seconds.
AUX1: S3 Real Yes Config 2 Field current
FIXR transducer ratio,
converts the
transducer output to
field scaling, in
ADC/VDC.
230 OW351_R1100
5.40 DXCSTATUS
FI E L D R ATI N G
C ON F I G.
AUX1: S4 Real Yes Config 0.05 Field current

FIDF difference limit for
disagreement
between
transducers, in
fractional percent.
AUX1: S5 Real Yes Config 1.5 Maximum
FIMX instantaneous value
of field current, in
fractional percent.
AUX1: S6 Real Yes Config 0 Minimum reasonable
FIMN field current for
operating generator,
in ADC.
AUX1: S7 Real Yes Config 0.5 The amount of field
FION current required to
definitely be online
for detecting a failed
CT in one CT
system, in fractional
percent.
AUX1: S8 Real Yes Rating 1 Scale factor to
FIPU convert field current
into per unit.
AUX1: S9 Real Yes Rating 7.1 Field current rating,
FIRT in ADC.
AUX1: T1 Real Yes Rating 85 Field voltage rating,
FVRT in volts DC.
AUX1: T2 Real Yes Config 40 Field voltage
FVR transducer ratio,
converts the
transducer output to
the field scaling, in
VDC/VDC.
AUX1: X1 Byte Yes Config 0 Forcing + under-
FUVE voltage is an
indicator of a blown
exciter diode -
enable for unit trip:
 0 = disabled
 1 = enabled
AUX1: T3 Real Yes Config 0.00298 Forcing derating
FITS scale factor from the
C50.13 rotor current
inverse time curve,
unitless.
AUX1: T4 Real Yes Config 1.03 Field forcing alarm
FLIM set point, in fraction
percent of field
current.
OW351_R1100 231
5.40 DXCSTATUS
FI E L D R ATI N G
C ON F I G.
AUX1: T5 Real Yes Config 1 Length of time

FTMO forcing before
checking for an
under-voltage
condition, in
seconds.
AUX1: T6 Real Yes Config 0.95 Under-voltage set
FUV point associated with
forcing to indicate an
exciter rectifier
failure, in per unit of
terminal voltage.
AUX1: T7 Real Yes Rating 60 Rated frequency of
GFRT generator, in Hertz.
AUX1: T8 Real Yes Config 60 Specifies the exciter
EXSF frequency, used to
select field voltage
filter settings, in Hz.
AUX1: T9 Real Yes Rating 769.8 Generator stator
GIRT current rating, in
AAC.
AUX1: U1 Real yes Rating 18.4 Generator apparent
GMVR power rating, in
MVA.
AUX1: U2 Real Yes Config 0.7 Generator voltage
GVIL must go below this
value to be invalid -
set lower than
GVVL, in per unit.
AUX1: U3 Real Yes Rating 13800 Generator terminal
GVRT voltage rating (line-
line), in VAC-RMS.
AUX1: V1 Real Yes Config 0.8 Generator voltage
GVVL must go above this
value to be valid -
set higher than
GVIL, in per unit.
AUX1: V2 Real Yes Config 0 Set point for reactive
XCSP load compens ation,
in per unit.
AUX1: V3 Real Yes Config 0 Instantaneous
UELI limiting amount, in
terminal voltage.
AUX1: X2 Byte Yes Config 1 Enables the MEL:
UELE  0 = uninstalled
 1 = installed
232 OW351_R1100
5.40 DXCSTATUS
FI E L D R ATI N G
C ON F I G.
AUX1: V4 Real Yes Config 0.1 Size of hysteresis

UELH above MEL limit, in
fractional percent.
AUX1: V5 Real Yes Config 26.58 MEL curve circle
UELR radius for type 1
MEL algorithm, in
MVA.
AUX1: X3 Enum Yes Config 0 Selects type of MEL
UELT specification:
 0 = 5-point discrete
 1 = circular
AUX1: V6 Real Yes Config 0.9 How much the
UELW warning alarm is
derated from the
limiting alarm, in
fractional percent.
AUX2: R1 Real Yes Config 0 MEL type 1 MW (X)
UELX offset for circle
origin, in MW.
AUX2: R2 Real Yes Config 26.58 MEL type 1 MVAR
UELY (Y) offset for circle
origin, in MVAR.
AUX2: X0 Byte Yes Config 0 Enables minimum
UEPE excitation protection:
 0 = uninstalled
 1 = installed
AUX2: R3 Real Yes Config 10 Minimum excitation
UEPO protection offset
below MEL curve, in
VA.
AUX2: R4 Real Yes Config 2 Timeout before MEP
UEPT to trip the unit, in
seconds.
AUX2: R5 Real Yes Config 8 Minimum excitation
UEPW protection warning
offset from MEP set
point, in MVAR.
AUX2: R6 Real Yes Config 0 The first point of the
MW1 linearized x-axis of
the discrete version
of the capability
curve, in MW.
AUX2: R7 Real Yes Config 7.4 The second point of
MW2 the linearized x-axis
of the discrete
version of the
capability curve, in
MW.
OW351_R1100 233
5.40 DXCSTATUS
FI E L D R ATI N G
C ON F I G.
AUX2: R8 Real Yes Config 11 The third point of the

of the capability
curve, in MW.
AUX2: R9 Real Yes Config 12.9 The fourth point of
MW4 the linearized x-axis
of the discrete
version of the
MW.
AUX2: S1 Real Yes Config 18.4 The fifth point of the
of the capability
curve, in MW.
AUX2: S2 Real Yes Config 0.925 MXL total heat set
OELC point fraction to allow
ramp-down of field
current to limit, in
fractional percent.
AUX2: S3 Real Yes Config 0.99 MXL hysteresis set
OELH point, in fractional
percent.
AUX2: S4 Real Yes Config 0.39 MXL current limit for
OELO offline operation, in
rated current.
AUX2: S5 Real Yes Config 1.05 Maximum excitation
OELS limiter set point, in
rated current.
AUX2: S6 Real Yes Config 0 Instantaneous
OELI limiting amount, in
terminal voltage.
AUX2: X1 Byte Yes Config 1 Enables the
OELE maximum excitation
limiter:
 0 = uninstalled
 1 = installed
AUX2: S7 Real Yes Config 0.7 MXL derating scale
OELF factor from the
inverse time curve,
unitless.
AUX2: S8 Real Yes Config 0.42 OXP current limit for
OEPO offline operation, in
fractional percent.
234 OW351_R1100
5.40 DXCSTATUS
FI E L D R ATI N G
C ON F I G.
AUX2: S9 Real Yes Config 1.1 OXP field current set

OEPS point for online
operation, in
fractional percent.
AUX2: X3 Byte Yes Config 1 Enables OXP:
OEPE  0 = disabled
 1 = enabled
AUX2: T1 Real Yes Config 0.8 OXP derating scale
OEPF factor from the
inverse time curve,
unitless.
AUX2: T2 Real Yes Config 5 OXP regulator
OEPT timeout, in seconds.
AUX2: X4 Byte Yes Config 0 PSS variable, PSS
PSSE installation enable:
 0 = uninstalled
 1 = installed
AUX2: T3 Real Yes Config 0.08 PSS voltage limit
PSVO OFF set point -
creates hysteresis -
symmetrical around
rated voltage, per
unit.
AUX2: T4 Real Yes Config 0.1 PSS voltage limit ON
PSVN set point -
symmetrical around
rated voltage, per
unit.
AUX2: T5 Real Yes Config 0.025 The amount of
PTCL disagreement
between PT's to not
be considered
uncalibrated, in
fractional percent.
AUX2: T6 Real Yes Config 5 Sets the timeout
PTCT period for being out
of calibration, in
seconds.
AUX2: T7 Real Yes Config 0.035 The amount of
PTEL disagreement
between PT's to not
be in error, in
fractional percent.
AUX2: T8 Real Yes Config 1 Sets the timeout
PTET period for being in
error, in seconds.
OW351_R1100 235
5.40 DXCSTATUS
FI E L D R ATI N G
C ON F I G.
AUX2: T9 Real Yes Config 120 Ratio of potential

PTR transformers for the
phase voltages,
VAC/VAC.
AUX2: U1 Real Yes Config 600 Generator rotor
RIXR current transducer
ratio, in ADC/VDC.
AUX2: U2 Real Yes Rating 4396 Rated value of
RIRT generator rotor field
current, in ADC.
AUX2: U3 Real Yes Config 0.002 SCL error deadband,
SCLD in per unit of stator
current.
AUX2: V1 Real Yes Config 0.99 SCL hysteresis set
SCLH point, in fractional
percent.
AUX2: V2 Real Yes Config 1.5 Maximum
SCLM instantaneous value
of stator current, in
fractional percent.
AUX2: V3 Real Yes Config 1 Stator current limiter
SCLS set point, in
rated stator current.
AUX2: X5 Byte Yes Config 0 Stator current limiter
SCLE installed flag:
 0 = uninstalled,
 1 = installed
AUX2: V4 Real Yes Config 0.8 SCL derating scale
SCLF factor from the
C50.13 stator current
inverse time curve,
unitless.
AUX2: V5 Real Yes Config -7.4 The first point of the
VAR1 linearized y-axis of
of the capability
curve, in MVAR.
AUX2: V6 Real Yes Config -4.4 The second point of
VAR2 the linearized y-axis
of the discrete
version of the
MVAR.
AUX3: R1 Real Yes Config -2.9 The third point of the
of the capability
curve, in MVAR.
236 OW351_R1100
5.40 DXCSTATUS
FI E L D R ATI N G
C ON F I G.
AUX3: R2 Real Yes Config -2.4 The fourth point of

VAR4 the linearized y-axis
of the discrete
version of the
MVAR.
AUX3: R3 Real Yes Config 0 The fifth point of the
of the capability
curve, in MVAR.
AUX3: R4 Real Yes Config 1.05 VHL set point for the
VHLG generator, in
fractional percent.
AUX3: X0 Byte Yes Config 1 Enables the volts per
VHLE hertz limiter:
 0 = disable
 1 = enable
AUX3: R5 Real Yes Config 0.99 VHL limit set point
VHLL hysteresis, in
fractional percent.
AUX3: R6 Real Yes Config 0.9933 VHL warning set
VHLW point, in fractional
percent.
AUX3: R7 Real Yes Config 1.05 VHL set point for the
VHLX transformer, in
fractional percent.
AUX3: R8 Real Yes Config 1.1 VHP generator low
VPG1 limit set point (less
restrictive), in
fractional percent.
AUX3: R9 Real Yes Config 1.18 VHP generator high
VPG2 limit set point (more
restrictive), in
fractional percent.
AUX3: S1 Real Yes Config 0.995 Hysteresis point for
VPH VHP, in fractional
percent.
AUX3: X1 Byte Yes Config 1 Enables volts per Hz
VPE protection:
 0 = disable
 1 = enable
AUX3: S2 Real Yes Config 3 Timeout between
VPRT VHP regulator trip
and unit trip outputs,
in seconds.
OW351_R1100 237
5.40 DXCSTATUS
FI E L D R ATI N G
C ON F I G.
AUX3: S3 Real Yes Config 45 VHP timing limit

VPT1 associated with the
low VHP set point
(more restrictive of
VPG1 and VPX1), in
seconds.
AUX3: S4 Real Yes Config 6 VHP timing limit
VPT2 associated with the
high VHP set point
(more restrictive of
VPG2 and VPX2), in
seconds.
AUX3: S5 Real Yes Config 1.1 VHP transformer low
VPX1 limit set point (less
restrictive), in
fractional percent.
AUX3: S6 Real Yes Config 1.18 VHP transformer
VPX2 high limit set point
(more restrictive), in
fractional percent.
AUX3: S7 Real Yes Rating 13800 Transformer voltage
XVRT rating, in VAC-RMS.
AUX3: U1 Real Yes Tuning 0.5 PSS variable, low-
PST8 Constant pass filter time
constant, in seconds.
AUX3: U2 Real Yes Tuning 0.1 PSS variable, low-
PST9 Constant pass filter time
constant, in seconds.
AUX3: U3 Real Yes Tuning 0.09 PSS variable, lead
PSTA Constant time constant, in
seconds
AUX3: V1 Real Yes Tuning 0.03 PSS variable, lag
PSTB Constant time constant, in
seconds.
AUX3: V2 Real Yes Tuning 0.05 Derivative time
TDR Constant constant for the AC
controller, in
seconds.
AUX3: V3 Real Yes Tuning 5.0 PSS variable,
PTW1 Constant washout time
constant 1, in
seconds.
constant 2, in
seconds.
constant 3, in
seconds.
238 OW351_R1100
5.40 DXCSTATUS
FI E L D R ATI N G
C ON F I G.

constant 4, in
seconds.
Dual Input Parameters
The following table describes the DXCSTATUS algorithm’s dual input parameters.
Dual input parameters
N AME RE C O R D T YP E RE C O N - TU N I N G DE F AU L T D E S C R I P TI O N
FI E L D CILE R ATI N G
C ON F I G.
P1AV V1 LA / Real No N/A 0.0 PTA calibration voltage.

P1BV V2 LA / real No N/A 0.0 PTB calibration voltage.
P1CV V3 LA / Real No N/A 0.0 PTC calibration voltage.
P2AV U1 LA / Real No N/A 0.0 PT2 A calibration voltage.

P2BV U2 LA / Real No N/A 0.0 PT2 B calibration voltage.
P2CV U3 LA / Real No N/A 0.0 PT2 C calibration voltage

CTAI U4 LA / Real No N/A 0.0 CTA calibration current.
CTBI U5 LA / Real No N/A 0.0 CTB calibration current.
CTCI U6 LA / Real No N/A 0.0 CTC calibration current.
READ Y0 LL / Byte No N/A 0 Instruct algorithm to read and

execute ACMD. Set by
graphics, reset by algorithm.
The following table describes the DXCSTATUS algorithm’s input parameters.
Inputs
N AME T YP E DE S C R I P TI O N CO MME N T
ACMD LP Algorithm command. Specifies command input to algorithm.

RDNT LL Redundant flag. Indicates whether redundant modules are present.
ENBL LL Enable Flag. Conditional to run algorithm or not
OW351_R1100 239
5.40 DXCSTATUS
ACMD
The ACMD input bits are defined in the following table.
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Module Reserved PT2 PT1 CTs CMD
The module bits indicate which module (primary or backup) should receive the decoded
command. Since it is possible to send a message to both modules with the same command, the
encoding of bits 14 and 15 are as follows
ACMD Bits 14 and 15
FRC D E S C R I P TI O N
00 This pattern is reserved.

01 The command should be sent to module1.
10 The command should be sent to module 2.
11 The command should be sent to modules 1 and 2.
If the command encoded in the CMD field is to force a particular module into control, bit pattern
11 for the module bits becomes an invalid pattern. If a command is being sent to m odule 2 and
the redundant flag for the algorithm is not set, the command is ignored.
RESERVED bits are reserved for future use. RESERVED bits must be set to zero or undefined
behavior may result.
Bits 4-6 identify which devices are being calibrated when a calibrate command is issued.
Bits 4-6 commands and descriptions
CMD DE S C R I P TI O N
Bit 4 CTs
Bit 5 PT1
Bit 6 PT2
CMD provides commands which may affect the module or both modules in a redundant pair.
CMD commands and descriptions
0000 Null; no command.

0001 Upload tuning parameters (from controlling module).
0010 Download tuning parameters (to both modules in redundant pair).
0011 Trigger oscillography on controlling module.
240 OW351_R1100
5.40 DXCSTATUS
0100 Read low calibration.

0101 Read high calibration.
0110 Calculate calibration coefficients.
0111 Cancel calibration.
1000 Transfer control of module as specified by module bits of ACMD.
1001 Commit calibration coefficients.
Outputs
The following table describes the DXCSTATUS algorithm output pin.
Output pins
N AME T YP E D E S C R I P TI O N
ASTA1 LP Algorithm status for module 1.

ASTA2 LP Algorithm status for module 2.
STATE LA Algorithm internal state. See state diagram.
ASTA1, ASTA2
The following values are defined for the ASTA1 and ASTA2 outputs. ASTA1 refers to the primary
module, and ASTA2 refers to the partner module.
ASTA output bits
ASTA BI T M E AN I N G
0x0 Null (ready for command).

0x1 Driver message sent.
0x2 Driver in progress.
0x3 Cannot connect to the driver.
0x4 Command timeout (no response from the driver).
0x5 Invalid command.
0x6 Invalid flags in Calibration command.
0x7 Invalid flags in Transfer Control command.
0x8 Invalid flags in Upload command.
0x9 Invalid flags in Download command.
0xA Invalid flags in Start Oscillography command.
0xB Command timeout (no response from module).
0xC Error reported from module (error code in field G8 or G9).
OW351_R1100 241
5.40 DXCSTATUS
ASTA BI T M E AN I N G
0xD Invalid address for module.

0xE Command completed successfully.
0xF Command cancelled.
0x10 Unknown status from driver.
242 OW351_R1100
5.40 DXCSTATUS
5.40.1 DXCSTAT US tuning parame ters and site ratings
Tuning parameters are module-shared memory variables that contain the gains, time constants,
and other tuning values, which configure the control loops on the module. Tuning parameters
consist of the following items:
 Control loop PID gains.
 Limiter PI gains.
 PSS time constants and gains.
Site ratings are module-shared memory variables that contain rated values, ratios, and functional
enable parameters that govern operation of the system and scaling of process parameters. Site
ratings consist of the following items:
 PT and CT ratios.
 Rated field current.
 Rated terminal voltage.
 Individual limiter and protective enable parameters.
The Ovation system maintains the module tuning parameters and site ratings in the LC records of
the DXCSTA TUS algorithm. The Operator Station contains custom graphics that interact with the
DXCSTATUS algorithm to allow the tuning parameters to be transferred back and forth between
the LC record and the module. The tuning parameters are transferred on operator command from
the graphic; they do not update automatically when the values change on the graphic or module.
Note: Refer to Ovation Record Types Reference Manual for more information on LC record
fields.
OW351_R1100 243
5.40 DXCSTATUS
The following figure depicts the tuning parameter processing.
Figure 14: DXCSTATUS Tuning Parameter processing
Site ratings are typically entered using custom graphics during system configuration and may be
modified during testing. The site ratings must be downloaded to the module using the
DXCSTATUS algorithm after entry or modification. The site ratings should be reconciled with the
Ovation Database once they have been specified or modified.
Tuning parameters are typically modified by Emerson personnel during service or unit startup.
After the module has been properly tuned, the tuning parameters are uploaded from the module.
The updated tuning parameters are then reconciled with the Ovation Database.
The module tuning parameters and site ratings are stored locally in the module in the
installation.conf configuration file. This file is written upon downloading parameters to the
module from the DXCSTATUS algorithm. After uploading new tuning parameters, they must then
be downloaded back to the module(s) to force them to be written to the configuration file.
244 OW351_R1100
5.40 DXCSTATUS
5.40.2 DXCSTAT US functions
The DXCStatus algorithm provides an interface to a standalone or redundant pair of modules

allowing functions on the module(s) to be accessed. The following functions are available:
 Module parameter upload/download.

 Reconcile algorithm parameters.
Note: Reconciling the algorithm parameters is an Ovation function and not truly a function of the
DXCSTATUS algorithm or the module.
 I/O calibration.
 Swap control between modules in a redundant pair.
Upload/Download function
The Upload/Download function retrieves tuning and site rating parameters from the module to the
algorithm (upload) and sends tuning and site rating parameters from the algorithm to the module
(download).
The Upload from Module function is invoked by setting the CMD field in the algorithm’s ACMD
input. The algorithm sends a request to the module communications driver, instructing the driver
to read the controlling module’s parameters. When the module responds, the driver updates the
algorithm LC record with the parameters and then sets the completion status parameter in the LC
record indicating that the upload is complete.
The Download to Module function is invoked by setting the CMD field in the algorithm’s ACMD
input. The algorithm sends a request to the module communications driver, instructing the driver
to send the parameters contained in the algorithm’s LC record to the module. The driver locates
the algorithm LC record using the SID that was passed in with the request. When the transfer
completes, the driver updates the status parameter in the LC record indicating that the download
is complete.
Note: Refer to Ovation Record Types Reference Manual for more information on LC record
fields.
I/O Calibration function
All module I/O is calibrated during factory testing, but because CT and PT panels are not
assigned to a module until that module is used in a system, field calibration may be necessary.
The DXCSTATUS algorithm coordinates field calibration of the module PT and CT inputs. Other
I/O cannot be calibrated in the field.
All CTs are calibrated as a group. Each set of PTs is calibrated independently; the PTs within a
set are calibrated as a group. The devices being calibrated are identified by bits 4 - 6 in the
algorithm command word. If a bit is non-zero, then that set of devices (CTs, PT1, PT2) is affected
by the calibration command.
OW351_R1100 245
5.40 DXCSTATUS
Five commands support calibration:

 Read Low Cal -- transfers the calibration values (algorithm dual input parameters) to the
module and instructs the module to read the low calibration input(s).
 Read High Cal -- transfers the calibration values (algorithm dual input parameters) to the
module and instructs the module to read the high calibration input(s).
 Calculate Calibration Coefficients -- tells the module to calculate the new calibration
settings.
 Commit Calibration Coefficients -- tells the module to save the new calibration coefficients
to a file.
 Cancel calibration -- instructs the module to revert all calibrations to their previous values as
long as they have not been committed.
It is possible to calibrate all inputs simultaneously by applying appropriate signals to each input
and selecting all calibration devices with bits 4 - 6. Once new coefficients have been calculated,
they take immediate effect. Subsequent measurements will demonstrate the efficacy of the new
calibration. To make the new coefficients permanent, they must be committed to a file. If the new
calibration is unsatisfactory, the Cancel Calibration command will undo the change as long as it
has not been committed.
Transfer Control function
The Transfer Control function transfers control from the controlling module to the non-controlling
module. This supports the ability to force a particular module to control in order to perform
maintenance on the other module.
Note: The Transfer Control function is designed for maintenance purposes only and should
never be used during normal operation of the system.
246 OW351_R1100
5.40 DXCSTATUS
5.40.3 DXCSTAT US state
The following figure shows the DXCSTATUS algorithm state diagram. The state diagram
indicates the control flow between states and the values for each state.
State value
S TATE V AL U E S TATE NAME
0 RESET
1 READY
2 STARTING COMMAND (UPLOAD)
3 WAITING FOR COMMAND (UPLOAD)
4 FINISHING COMMAND (UPLOAD)
5 STARTING COMMAND (DOWNLOAD)
OW351_R1100 247
5.40 DXCSTATUS
S TATE V AL U E S TATE NAME
6 WAITING FOR COMMAND (DOWNLOAD)

7 FINISHING COMMAND (DOWNLOAD)
8 STARTING COMMAND (OSCILLOGRAPHY)
9 WAITING FOR COMMAND (OSCILLOGRAPHY)
10 FINISHING COMMAND (OSCILLOGRAPHY)
11 STARTING COMMAND (READ LOW CAL)
12 WAITING FOR COMMAND (READ LOW CAL)
13 FINISHING COMMAND (READ LOW CAL)
14 STARTING COMMAND (READ HIGH CAL)
15 WAITING FOR COMMAND (READ HIGH CAL)
16 FINISHING COMMAND (READ HIGH CAL)
17 STARTING COMMAND (CALC CAL)
18 WAITING FOR COMMAND (CALC CAL)
19 FINISHING COMMAND (CALC CAL)
20 STARTING COMMAND (CANCEL CAL)
21 WAITING FOR COMMAND (CANCEL CAL)
22 FINISHING COMMAND (CANCEL CAL)
23 STARTING COMMAND (TRANSFER CONTROL)
24 WAITING FOR COMMAND (TRANSFER CONTROL)
25 FINISHING COMMAND (TRANSFER CONTROL)
26 STARTING COMMAND (COMMIT CAL)
27 WAITING FOR COMMAND (COMMIT CAL)
28 FINISHING COMMAND (COMMIT CAL)
29 START ERROR
30 DELAY ERROR
31 DONE ERROR
248 OW351_R1100
5.41 FACEPLATE
5.41 FACEPLATE
Description
The FACEPLATE algorithm is a generic algorithm used to collect all inputs necessary for a
graphic faceplate. Its purpose is to reduce the amount of data needed by the graphic designer
when adding faceplates to a process diagram or window.
You need to pass only the name of the FACEPLATE algorithm to a graphic macro. The graphic
macro then retrieves all relevant input signals from the FACEPLATE algorithm and displays the
data accordingly.
The FACEPLATE algorithm sequences through all arguments and checks for a connection. It
then stores the system IDs for those connected points in the appropriate record fields of the
FACEPLATE algorithm.
The algorithm can have a maximum of two control algorithm points and up to 30 input points,
which can be analog, digital, or packed.
In addition to the generic template, two other templates exist for this algorithm.
 DIGITAL DEVICE template (see page 252).
 MASTATION template (see page 256).
Functional Symbol
FI E L D RE C O R D
TYPE X1 - Byte Data Init Required 0 Faceplate type --
WIN XU - Data Init Required 0 Default window --

Integer number
MAC XR - Data Init Required 0 Default macro --

Integer number
TTL1 TT - ASCII Data Init Optional TITLE Title --
ALG1 G0 Variable Required -- Control algorithm #1 LC
ALG2 G1 Variable Optional -- Control algorithm #2 LC
OW351_R1100 249
5.41 FACEPLATE
FI E L D RE C O R D
PM1 B0 Variable Optional -- Input #1. Could be LA, LD,

analog, digital, or LP
packed.
packed.
packed.
PM4 YU Variable Optional -- Input #4. Could be LA, LD,
packed.
packed.
packed.
packed.
packed.
packed.
packed.
PM11 C0 Variable Optional -- Input #11. Could be LA, LD,
packed.
packed.
packed.
packed.
packed.
packed.
250 OW351_R1100
5.41 FACEPLATE
FI E L D RE C O R D

packed.
packed.
packed.
PM20 YT Variable Optional -- Input #20. Could be LA, LD,
packed.
PM21 D0 Variable Optional -- Input #21. Could be LA, LD,
packed.
PM22 YQ Variable Optional -- Input #22. Could be LA, LD,
packed.
packed.
PM24 YP Variable Optional -- Input #24. Could be LA, LD,
packed.
packed.
packed.
packed.
PM28 YN Variable Optional -- Input #28. Could be LA, LD,
packed.
packed.
packed.
OW351_R1100 251
5.41 FACEPLATE
5.41.1 FACEPLAT E -- DIGITAL DEVICE te mplate

Description
This template should be used with the DIGITAL DEVICE algorithm. The following symbols show
an example of how this template could be used.
Note: Default symbols are not available for this template. Users are responsible for generating
their own symbols since the interface is defined within the individual graphics macros.
FI E L D RE C O R D
WIN XU - Data Init Required 9100 Default window --

Integer number
MAC XR - Data Init Required 9100 Default macro --
Integer number
CNTL X2 - Byte Data Init Required 0 Type of control to be --
implemented:
 Start/Stop Normally
Open Contact
 Start/Stop Normally
Closed Contact
 Open/Closed
Normally Open
Contact
 Open/Closed
Normally Closed
Contact
252 OW351_R1100
5.41 FACEPLATE
FI E L D RE C O R D
FBI X3 - Byte Data Init Required 1 Analog feedback for --

travel:
YES: Use feedback
NO: Do not use
feedback
TVST B0 Variable Optional -- Analog travel LA
feedback status.
PK12 B1 Variable Optional -- Feedback for P-key 1 LA
and 2 -- 1-3 Element
PK3 B2 Variable Optional -- Feedback for P-key 3 LA
- Auto
IND C0 Variable Optional -- 1-3 Element LD
indication
DEV1 D0 Variable Optional -- Device LP point name LP
for feedback
OW351_R1100 253
5.41 FACEPLATE
Example Using the Digital Device template
For the digital faceplate values to be displayed in a graphic using the FACEPLATE algorithm, use
the following example to place code in the main screen diagram.
In the DIAGRAM section (OCB010F001 will be replaced by the name of your faceplate):
******** Start Process Point Mappin g of Digital Faceplate Algorithm

*********
*** Digital Faceplate Algorithm Name = OCB01 0F00 1
* Analog feedback for Travel Status
DEF_VARIA BLE LOCAL TVST SYSID
SET_VARIABLE l:TVST OCB01 0F00 1 B0
* Feedba ck for P-KEY 1&2 - 1-3 Element
DEF_VARIA BLE LOCAL PK12 SYSID
SET_VARIABLE l:PK12 OCB01 0F00 1 B1
* Feedba ck for P-KEY 3 - AUTO
DEF_VARIA BLE LOCAL PK3 SYSID
SET_VARIAB LE l:PK3 OCB010 F001 B2
* 1-3 Element Indication
DEF_VARIA BLE LOCAL IND SYSID
SET_VARIABLE l:IND OCB01 0F00 1 C0
* Device LP Point Name for Feedback
DEF_VARIA BLE LOCAL DEV1 SYSID
SET_VARIABLE l:DEV1 OCB01 0F00 1 D0
254 OW351_R1100
5.41 FACEPLATE
In the BACKGROUND section (Optional):
TEXT 7346 1996 "TVST B0" HORZ VECTOR_OVER 108 351 1
TEXT 7345 2525 "PK12 B1" HORZ VECTOR_OVER 108 351 1
TEXT 7330 3031 "PK3 B2" HORZ VECTOR_OVER 108 351 1
TEXT 7329 3647 "IND C0" HORZ VECTOR_OVER 108 351 1
TEXT 7342 4198 "DEV1 D0" HORZ VECTOR_OVER 108 351 1
In the FOREGROUND section (to display specific values of the record field of the Faceplate
algorithm):
PROCESS _PT 5506 2017 15 -1 RIGHT OFF HORZ VECTOR_OVER 108

351 1 L:TVST AV

351 1 L:PK12 AV
PROCESS _PT 5521 3069 15 -1 RIGHT OFF HORZ VECTOR_ OVER 108
351 1 L:PK3 AV

351 1 L:IND DS
PROCESS _PT 5535 4231 15 -1 HEX OFF HORZ VECTOR_OV ER 108 351 1
L:DEV1 A2
To call the faceplate Macro (49100 in this case) using the one $D1 point - the LC faceplate
algorithm name.
Macro 49100 55 8201 0.3186 31 0.489620 1 0 3 1 3 0

\OCB010 F001.UNIT0@ FE222\
"Digital Faceplate Alg." "FE222-Drop 14 - Using Macro 49100 "

"OCB01 0F00 1"
28 28 2 3 0 0
Refer, Ovation Graphics Language Reference Manual for more information on graphic
commands.
OW351_R1100 255
5.41 FACEPLATE
5.41.2 FACEPLAT E -- M AST AT ION te mplate

Description
This template should be used with the MASTATION algorithm. The following symbols show an
example of how this template could be used.
Note: Default symbols are not available for this template. Users are responsible for generating
their own symbols since the interface is defined within the individual graphics macros.
FI E L D RE C O R D
WIN XU - Integer Data Init Required 9000 Default window --

number
MAC XR - Integer Data Init Required 9000 Default macro --
number

PV B0 Variable Optional -- Process variable LA
DEMD B1 Variable Optional -- Demand LA
BIAS B2 Variable Optional -- Bias LA
STPT YU Variable Optional -- Setpoint LA
OUT B4 Variable Optional -- Output LA
SMOD B5 Variable Optional -- Mode word for LA
setpoint
IND C0 Variable Optional -- 1 - 3 element LD
indication
MODE D0 Variable Optional -- Input mode point LP
256 OW351_R1100
5.42 FIELD
5.42 FIELD
Description
The FIELD algorithm is used only with the hardware analog output variable points. This algorithm
checks the value against the IO card limits and sets the appropriate bits in the track output point.
It should be used instead of “output analog hardware” I/O connectors in applications involving
interfaces to control elements (for example, valves and dampers).
The output digital point (FAIL) is TRUE when the algorithm detects a hardware error on the I/O
card. This algorithm is designed to read the value from the point record and output value TOUT
on the first pass.
Functional Symbol
FI E L D RE C O R D
DIAG LU Data Init. Required - Tuning Diagram -

Number
TOUT - Variable Required - Track Output Value LA
Mode and Status For
Input Variable
(analog)
HWPT1 - Variable Optional - Hardware Output LA

(analog)
FAIL - Variable Optional - Hardware Error Point LD, LP
(digital)
1 You cannot scan remove the HWPT point.
OW351_R1100 257
5.42 FIELD
Tracking Signals
The high and low limits flags and tracking signals from the algorithm are output to TOUT, to be
used for display and by an upstream algorithm.
The following information is output by this algorithm in the TOUT signal.
16 Track Implemented TRUE when output value is at

low limit of the card

19 Lower inhibit Implemented TRUE when output value is at the
low limit of the card**
20 Raise inhibit Implemented TRUE when output value is at

high limit of the card**
21 Conditional Track No action Not used

27 Supervisory mode No action Not used
28 Cascade mode No action Not used
29 DDC mode No action Not used
30 Low limit reached Implemented Low limit reached
31 High limit reached Implemented High limit reached
258 OW351_R1100
5.43 FIFO
5.43 FIFO
Description
The FIFO algorithm provides a basic First In - First Out operation. The order in which any of the
16 digital inputs transition from FALSE to TRUE is preserved. The order is stored using the input
number of the associated input (that is, 1 for IN1, 2 for IN2, 3 for IN3, and so forth).
Initially, the value of the output is zero. If the FIFO is empty, the output is also zero. For each
successive FALSE to TRUE Transition of the rotate (RTAT) input, the oldest input number stored
in the FIFO is removed from internal storage and that numerical value is written to the output
(OUT). Note that the output is considered separate from the actual FIFO.
The point retains the value until either the rotate (RTAT) or the clear (CLR) input transitions from
FALSE to TRUE. A FALSE to TRUE transition on the (RTAT) input causes the oldest entry in the
FIFO to be removed from the FIFO and placed in the output (OUT). At this point, the value in the
(OUT) variable is no longer included in the queue.
If multiple inputs transition from FALSE to TRUE on the same execution cycle of the Controller,
then they are ordered according to their numerical number. For example, IN1 is placed in the
FIFO first and thus is rotated out first.
A FALSE to TRUE transition on the clear (CLR) input causes the output and all the internal FIFO
entries to be set to zero. As long as the clear (CLR) input remains TRUE, the algorithm ignores all
the inputs and thus does not operate.
The FIFO is considered full when all 16 inputs have made a transition from FALSE to TRUE
without any subsequent FALSE to TRUE transition on the rotate (RTAT) input. When this full
condition exists, any further FALSE to TRUE transitions of any of the inputs are ignored until at
least one of the stored values is rotated out of the FIFO.
The FLAG output is set TRUE when the FIFO is NOT empty.
Note: The FIFO values are stored in the algorithm record fields G0-G9, B0-B5.
OW351_R1100 259
5.43 FIFO
Functional Symbol
FI E L D RE C O R D
IN1 - Variable Required - Digital Input LD
IN2 - Variable Optional - Digital Input LD

260 OW351_R1100
5.43 FIFO
FI E L D RE C O R D

RTAT - Variable Required - Digital Rotate FIFO LD
Input
CLR - Variable Required - Digital Clear FIFO LD
Input
variable
FLAG - Variable Optional - Digital output LD
variable
OW351_R1100 261
5.44 FIRSTOUT
5.44 FIRSTOUT
Description
The FIRSTOUT algorithm monitors up to 16 digital inputs and provides an indication of the first
digital input to transition from zero to one. The algorithm output is a packed group point whose 16
bits correspond to each of the 16 digital inputs. If more than 16 inputs need to be monitored,
multiple algorithms can be cascaded together. The resolution of the algorithm is equal to the
period of the control task in which it executes.
Note: The quality values of the digital inputs are not propagated to the digital outputs.
Functional Symbol
262 OW351_R1100
5.44 FIRSTOUT
Algorithm States
The FIRSTOUT algorithm operates in three states: armed, tripped and disabled.
In the disabled state, the algorithm does not operate. In the armed state, the algorithm monitors
the digital value of all connected inputs (IN1-IN16). If any of the inputs transition from a zero to a
one, the algorithm enters the tripped state.
When RST input is set to zero, the algorithm is in the disabled state. A zero to one transition on
the RST input sets the algorithm to the armed state. When this transition occurs, any inputs (IN1-
IN16) that are a one are ignored. Thus, it is not necessary to ensure that all inputs are a zero
when the algorithm is armed.
The current state of the algorithm is indicated in two ways: the X1 field of the algorithm LC record
and the STATE output. The following table shows the states and the indications.
S TATE X1 FI E L D STATE
O U TP U T
Armed or Disabled 0 0
Tripped 1 1
Once the algorithm enters the tripped state it remains in that state. The RST input must be set to
zero to enter the disabled state, and then set to a one in order to enter the armed stat e again.
Controlled Algorithm Execution
The FIRSTOUT algorithm can be selectively executed by using the reset (RST) input. The RST
input must be set to a one for the algorithm to operate. If the RST input is set to a zero, the
algorithm is disabled and the algorithm is not executed in each loop that the RST is set to zero.
Trip Reporting
Each of the 16 bits in the monitor (MNTR) output corresponds to the IN1 - IN16 inputs. Bit zero
corresponds to IN1, bit one corresponds to IN2, and so forth. When the algorithm is operating in
the armed state, all bits in the MNTR points are set to zero. If any of the inputs (IN1 - IN16)
transition to a one, the corresponding bit in the MNTR packed point output is set to one.
If multiple inputs transition to one on the same execution cycle, the algorithm can be configured to
report which input(s) caused the change. This can be done in one of two ways. First, the default is
for all inputs that transitioned to be reported in the MNTR output. Optionally, only the input with
the lowest input number can be reported in the MNTR output. Note that the MULT output point is
set to one when either of these conditions occur. The desired configuration is specified using the
MCFG (X2) field in the algorithm LC record.
The number of inputs that transitioned from zero to one is reported in the optional analog output
NTRP. During operation in armed mode, the NTRP output is set to zero.
OW351_R1100 263
5.44 FIRSTOUT
Dependencies among RST, IN1-IN16 inputs, and TRPD output are shown on the following timing
diagram.
1
RST 0
IN1 1
0
IN2 1
0
TRPD 1
0
Cascading Multiple Algorithms
If it is necessary to monitor more than 16 digital inputs, multiple FIRSTOUT algorithms can be
cascaded together. The TRPD output of each algorithm is connected to one of the inputs
(IN1 - IN6) of the subsequent algorithm.
FI E L D RE C .
DIAG LU -Integer Data Init Optional - Tuning diagram -

number
MCFG X2 - Byte Data Init Required 0 This field controls -

how the algorithm
reports multiple inputs
transitioning in the
same loop time. The
values are:
 0 = Report all inputs
that transitioned
 1 = Report only the
input with the lowest
input pin number
IN1 Input Variable Optional - Input 1 LD, LP
264 OW351_R1100
5.44 FIRSTOUT
FI E L D RE C .
RST Input Variable Required - Reset input. A zero LD, LP

on this input causes
the algorithm to enter
disabled mode. A
value of one causes
the algorithm to enter
armed mode.
MNTR Output Variable Required - Each bit 1 - 16 of this LP
point corresponds to
IN1 - IN16
respectively. When in
the armed state, all
16 bits are set to
zero. When in the
tripped state, the bit
that corresponds to
the first input to
transition to a one is
set.
MULT Output Variable Optional - This output is always LD, LP
set to zero when the
algorithm is operating
in the armed mode. If
more than one of the
inputs transition to
one, this output is set
to one. Note that
when this condition
occurs, the bit that
corresponds to the
lowest numbered
input that triggered
the trip condition is
set in the MNTR
point.
OW351_R1100 265
5.44 FIRSTOUT
FI E L D RE C .
TRPD Output Variable Required - This output is set to LD, LP

one when the
in the tripped state. It
is set to zero if the
in the armed state.
NTRP Output Variable Required - In the tripped state, LA
this output is equal to
the number of inputs
that transitioned from
zero to one in the
execution cycle in
which the algorithm
transitioned to the
tripped state. This
output is always set to
zero when the
in the armed state.
266 OW351_R1100
5.45 FLIPFLOP
5.45 FLIPFLOP
Description
The FLIPFLOP algorithm is a memory device. Its output states are defined in the Function for
Reset Override and Function for Set Override Truth tables.
Functional Symbol
FI E L D RE C O R D
TYPE X1-Byte Data Init. Required 0 Type of flip-flop: -
1 = Flip-flop with
set override
0 = Flip-flop with
reset override
SET - Variable Required - Input (digital); set LD, LP
RSET - Variable Required - Input (digital); reset LD, LP

Function for Reset Override
SET RESET OUT
0 0 S
0 1 0
1 0 1
1 1 0
where:
OW351_R1100 267
5.45 FLIPFLOP
On power up/reset of the Controller, OUT is set according to the truth table, unless SET and
RSET are both FALSE.
Function for Set Override
SET RESET OUT
0 0 S
0 1 0
1 0 1
1 1 1
where:
On power up/reset of the Controller, OUT is set according to the truth table, unless SET is set
FALSE.
268 OW351_R1100
5.46 FUNCTION
5.46 FUNCTION
Description
The FUNCTION algorithm generates a piecewise-linear function that is determined by elements

of a 12-element X-Y breakpoint array. Each Y-array element (dependent variable) has a
respective X-array element (independent variable), thereby portraying the desired function. The
number of breakpoints specifies the size of the array.
If the input value is invalid or less than the smallest element in the X-array, the output assumes
the value of the corresponding Y-array element. Also, if the input value is greater than the largest
X-array element, the output assumes the value of the corresponding Y-array element. If there is
more than one output value (Y-array) for a particular input value (X-array), the output is the first
element of the Y-array encountered.
The TPSC and BTSC algorithm definitions must match the highest and lowest Y-array values of
the function defined in order for tracking to be properly implemented. If the limits are different, the
algorithm tracks to the value. But upon releasing, it bumps back to the calculated output value.
Functional Symbol
Tracking Signals
Tracking and limiting are done through signals passed in the upper 16 bits of the third status word
of the analog point. This algorithm takes the following action in response to the information found
in the input signal TRIN:
Bit description

OW351_R1100 269
5.46 FUNCTION

Otherwise, the value of the conditional track bit is transferred to all output track points.
If the Conditional Track bit is set in the track input point, the analog value of all output
track points is calculated based on the analog value of the track input point.
The high and low limit flags and the tracking signals from the algorithm are output to TOUT, to be
used for display and by an upstream algorithm. If the output value is invalid, the quality of OUT is
set to BAD. Otherwise, the quality of OUT is set to the quality of the input when not in tracking
mode. When tracking, the quality is set to the quality of the track input variable.
When the FUNCTION algorithm is tracking, it forces the upstream algorithm to track to the X-
array value associated with the Y-array value to which the FUNCTION is told to track. However, if
there is more than one X-array value associated with the specified Y-array value, the FUNCTION
algorithm forces the upstream algorithm to track to the first X-array value encountered.
Note: If the algorithm generates an invalid track output value, the input value is used as the
track output, unless it is invalid. The track output value is not updated if both the calculated track
output and input values are invalid.
FI E L D RE C O R D

Number
GAIN T7-Real Tuning Required 1.0 Gain on the -
Constant input. The gain
on the input
should never be
initialized to zero;
if it is, the drop is
placed into
alarm.
270 OW351_R1100
5.46 FUNCTION
FI E L D RE C O R D
BIAS T8-Real Tuning Required 0.0 Bias on the input -

Constant
TPSC T9-Real Tuning Required 100.0 Maximum value -

Constant of the output
point
BTSC U1-Real Tuning Required 0.0 Minimum value of -
TRAT U2-Real Tuning Required 2.5 Track ramp rate -
Constant (units per
second).
BPTS X1-Byte Tuning Required 2.0 Number of break -
Constant points (number of
(x, y) coordinate
pairs)
X- 1 R1-Real Tuning Required - 100.0 X-coordinate 1 -
Constant
Y- 1 S4-Real Tuning Required - 100.0 Y-coordinate 1 -

Constant
X- 2 R2-Real Tuning Required 100.0 X-coordinate 2 -
Constant
Y- 2 S5-Real Tuning Required 100.0 Y-coordinate 2 -
Constant
X- 3 R3-Real Tuning Optional 0.0 X-coordinate 3 -
Constant
Y- 3 S6-Real Tuning Optional 0.0 Y-coordinate 3 -
Constant
Constant
Constant
Constant
Constant
Constant
Constant
Constant
Y- 7 T1-Real Tuning Optional 0.0 Y-coordinate 7 -
Constant
Constant
OW351_R1100 271
5.46 FUNCTION
FI E L D RE C O R D

Constant
Constant
Constant
X -10 S1-Real Tuning Optional 0.0 X-coordinate 10 -
Constant
Y -10 T4-Real Tuning Optional 0.0 Y-coordinate 10 -
Constant
Constant
Constant
Constant
Constant
IN1 - Variable Required - IN1 variable LA
analog input
value, mode and
status signals for
input variable
variable
value, tracking
and limiting mode
signals input
variance
272 OW351_R1100
5.47 GAINBIAS
5.47 GAINBIAS
Description
The GAINBIAS algorithm multiplies the analog input with an internal gain, adds a bias and then
limits the output value.
To scale the output proportionally to the input, calculate the required Gain and Bias as follows:
Note: If the algorithm receives an invalid value as an input, or calculates an invalid value as the
output, the drop is placed into alarm.
Functional Symbol
OW351_R1100 273
5.47 GAINBIAS
Tracking Signals
Tracking and limiting are done through signals passed in the upper 16 bits of the third status of
the analog point. This algorithm takes the following action in response to the information found in
the input signal TRIN:
** Only when the Track signal is not present; the signals are set according to the definitions
given in Setting Tracking Signals (see page 15).
*** If the algorithm is being told to track, then the Conditional track b it is ignored. Otherwise, the
value of the conditional track bit is transferred to all output track points. If the Conditional Track
bit is set in the track input point, the analog value of all output track points is calculated based on
the analog value of the track input point.
274 OW351_R1100
5.47 GAINBIAS
used for display and by an upstream algorithm. If the OUT value is invalid, the quality of OUT is
set to BAD. Otherwise, if the quality propagation (PROQ) option is ON, the quality of OUT is set to
the quality of the input when not in tracking mode. When tracking, the quality is set to the quality
of the track input variable. If the PROQ option is OFF, the quality of OUT is set to GOOD.
FI E L D RE C O R D

Number
GAIN R1-Real Tuning Required 1.0 Gain on input. -
Constant The gain on the
input should
never be
initialized to
zero; if it is, the
drop is placed
into alarm.
BIAS R2-Real Tuning Required 0 Bias on input -
Constant
TPSC R5-Real Tuning Required 100.0 Maximum value -

point
BTSC R6-Real Tuning Required 0.0 Minimum value -
point
Constant (units per
second)
local memory
operations. The
choices are:
 ON
 OFF
OW351_R1100 275
5.47 GAINBIAS
FI E L D RE C O R D
PROQ X1-Byte Data Init. Required ON Quality -

Bit 1 Propagation
option:
ON = Normal
quality selection
OFF = Quality
of the output is
always GOOD,
except when
OUTPUT is not
a valid real
number.
IN1 - Variable Required - Input analog LA

value, mode
and status
signals for input
variable
variable
value, tracking
and limiting
mode signals
input variable
Function
OUT = (IN1 x GAIN) + BIAS

IF OUT >= TPSC THEN
OUT = TPSC
ELSE
IF OUT <= BTSC THEN
OUT = BTSC
276 OW351_R1100
5.48 GASFLOW
5.48 GASFLOW
Description
The GASFLOW algorithm calculates a pressure-and-temperature-compensated mass or

The mass flow is calculated as shown below:
The volumetric flow is calculated as shown below:
It is possible to disable pressure compensation or temperature compensation. For no pressure

compensation, you must specify a negative pressure reference (PRES) value. For no temperature
compensation, you must specify a negative temperature reference (TEMP) value.
The TPSC and BTSC parameters are used to limit the output value of the algorithm.
Functional Symbol
Tracking Signals
Tracking and limiting are done through signals passed in the upper 16 bits of the analog tracking
point's third status word. This algorithm takes the following action in response to the information
found in the input signal TRIN:
Bit description
16 Track Ignored Not used
17 Track if lower Ignored Not used
18 Track if higher Ignored Not used
OW351_R1100 277
5.48 GASFLOW
19 Lower inhibit Ignored Not used
20 Raise inhibit Ignored Not used
The high and low limit flags are output to TOUT to be used for display.
The output has the worst quality of the analog inputs specified assigned to the quality of the
output.
FI E L D RE C .

Number
CALC G3-Integer Data Init. Required MASS- Type of flow -
Bit 5 FLOW calculation
performed:
MASSFLOW =
mass flow
VOLFLOW =
volume flow
GAIN R3-Real Tuning Required 1.0 Calculated flow -
Constant coefficient at base
operating
conditions.
278 OW351_R1100
5.48 GASFLOW
FI E L D RE C .
PRES R4-Real Tuning Required 2400.0 Reference -

Constant pressure; base
operating pressure
used in the
calculation of the
flow coefficient,
GAIN
TEMP R5-Real Tuning Required 1000.0 Reference -
Constant temperature; base
operating
temperature used
in the calculation of
the flow coefficient,
GAIN.
PABS G3-Integer Data Init. Required YES Convert pressure -
Bit 2 values to absolute
pressure option:
YES = Input and
reference pressure
values are
converted to
absolute pressure.
NO = Input and
reference pressure
values are not
converted to
absolute pressure.
PUNT G3-Integer Data Init. Required PSI Pressure -
Bits 0 and 1 conversion type
Absolute
Pressure
Conversion
Type Value
PSI 14.696
INH20 406.800
KGCM2 1.033
KPA 101.325
OW351_R1100 279
5.48 GASFLOW
FI E L D RE C .
TABS G3-Integer Data Init. Required YES Convert -

Bit 4 temperature values
to absolute
temperature option.
YES = Input and
reference
temperature values
are converted to
absolute
temperature.
NO = Input and
reference
temperature values
are not converted
to absolute
temperature.
TUNT G3-Integer Data Init. Required FAHR Temperature -
Bit 3 conversion type
Absolute
Temperature
Conversion
Type Value
FAHR 459.67
CENT 273.15
Constant the output

Constant the output
280 OW351_R1100
5.48 GASFLOW
FI E L D RE C .
PNEG G3-Integer Data Init. Required NO-CHECK Check for use of -

Bit 6 negative pressure
and temperature
reference values
NOCHECK = No
check is performed
to see if the
PACT(C) and
TACT(C) inputs
were specified. A
negative PRES
REF or TEMP REF
value causes the
associated term to
be omitted from the
equation.
CHECK = Check
whether the
PACT(C) and
TACT(C) inputs
were specified. If
an input is not
specified, the
associated term is
omitted from the
equation. When the
inputs are
specified, the
PRES REF and
TEMP REF values
are used regardless
of their sign.
PSEL G3-Integer Data Init. Required STANDARD Select pressure -
Bit 7 conversion type:
STANDARD - Use
the pressure
conversion value
defined by PRES
UNIT.
USER - Use the
pressure
conversion value
defined by USER
PRES.
PUSR R6-Real Tuning Required 0.0000 Value for -
Constant user-specified
pressure
conversion
TYPE X1-Byte Data Init. Required DEL-TAP Flow Differential or -
DELTAP
Default: DELTAP
OW351_R1100 281
5.48 GASFLOW
FI E L D RE C .
IN1 - Variable Required - Differential LA

pressure or flow.
Input (analog)
TOUT - Variable Required - Track output value LA
and status output
signals
PACT - Variable Optional - Actual pressure. LA
Input (analog)
TACT - Variable Optional - Actual temperature. LA
Input (analog)
variable
TRIN - Variable Optional - Track value, LA
tracking and limit
modes.
Input (analog)
282 OW351_R1100
5.48 GASFLOW
Function
IF ((PNEG = NOCHECK) AND (PRES REF < 0)) OR

((PNEG = CHECK) AND (PACT = UNDEFINED))
THEN
P1 = P2 = 1
ELSE
P1 = PACT + ABSPRES
P2 = PRES REF + ABSPRES
IF ((TNEG= NOCHECK) AND (TEMP REF < 0)) OR

((TNEG= CHECK) AND (TACT = UNDEFINED))
THEN
T1 = T2 = 1
ELSE
T2 = TACT + ABSTEMP
T1 = TEMP REF + ABSTEMP
IF MASSFLOW THEN
IF (P2 = 0) OR (T1 = 0) THEN
OUTVAL = 0
ELSE
IF DELTAP
OUTVAL = IN1 * (P1/P2) * (T1/T2)
ELSE
OUTVAL = (P1/P2) * (T1/T2)
ELSE
IF (P1 = 0) OR (T2 = 0) THEN
OUTVAL = 0
ELSE
IF DELTAP
OUTVAL = IN1 * (P2/P1) * (T2/T1)
ELSE
OUTVAL = (P2/P1) x (T2/T1)
IF OUTVAL < 0 THEN

OUT = 0
ELSE
IF DELTAP
OUT = GAIN * SQUARE ROOT OF OUTVAL
ELSE
OUT = (GAIN * IN1) * SQUARE ROOT OF OUTVAL
where:
P1,P2,T1,T2,OUTVAL = local, temporary, real variables
ABSPRES, ABSTEMP = constants from the pressure and temperature conversion tables
built into the algorithm
OW351_R1100 283
5.49 HEARTBEAT
5.49 HEARTBEAT
Description
The HEARTBEAT algorithm is designed to generate heartbeat signals that can be received by
other drops for use in safety critical applications. The algorithm can also be utilized to monitor up
to five heartbeat signals generated from heartbeat algorithms in other Controllers. If the algorithm
detects that a heartbeat signal being monitored has ceased, it sets the corresponding output to
one. It has a value of zero when it is communicating.
A heartbeat signal is a continuously changing signal that is generated and broadcast from an
Ovation Controller. A heartbeat signal that is continuously changing is an explicit indication that
the Controller generating the heartbeat signal is functioning properly.
Typically, the heartbeat signal allows a control strategy to monitor other heartbeat signals (ones
that are broadcast from other Controller drops) and take appropriate actions if the heartbeat
signals cease. It is common in power generation applications to have the loss of a heartbeat
signal from one or more Controllers generate a Master Fuel Trip (MFT) in the Controller that is
monitoring the heartbeat signals.
Functional Symbol
284 OW351_R1100
5.49 HEARTBEAT
Overview
The value of a heartbeat signal output (HTBT) is a continuously changing analog value. The
HTBT output is updated each loop time to a new number. The actual value of the heartbeat signal
is not important - it is important that the heartbeat signal updates each loop time by the originating
Controller and that the receiving Controller records a different value each loop time.
If any input heartbeat signals are connected to the HEARTBEAT algorithm, they are monitored to
ensure that the value changes on each successive loop. During each execution loop, the value of
each connected input is read and compared to that point's value that was read on the previous
loop. Under normal conditions, these two successive values should be different - that is, the
changing signal is being received from the originating drop(s) successfully. If the value of any of
the input points is unchanging for the user-entered timeout period (TIME1 - 5), the corresponding
trip output OUT1 - 5 is set to true.
Note that if the user-entered timeout period is not an exact multiple of the control task period in
which the algorithm is executing, then the algorithm rounds the user-entered value to the next
higher integer multiple of the task period. When this occurs, the resulting actual timeout is the
user-entered timeout plus the control task period. This action ensures that the tuning fields of the
algorithm always reflect the exact timeout period.
Emerson recommends that when the algorithm is used to generate a heartbeat signal, it should
be executed in a 0.1 second control task. When the algorithm is used to monitor other heartbeat
signals, Emerson recommends that it should be executed in a 0.1 second control task.
Also, note that the algorithm ensures that the user-entered timeout cannot be set to a value less
than the time that it takes the Ovation Network to detect a loss of communication on a primary
Controller and to initiate a failover. This time is typically five seconds.
FI E L D RE C .
DIAG LU - Integer Data Init Optional - Tuning diagram -

number
TIME1 R1 - Real Tuning Required - Timeout value for -
Constant heartbeat input 1*




IN1 Input Variable Optional - Input Heartbeat LA

signal 1
OW351_R1100 285
5.49 HEARTBEAT
FI E L D RE C .

signal 2
signal 3
signal 4
signal 5
HTBT Output Variable Required - Heartbeat Output LA
Note: Emerson
recommends that the
Heartb eat output
(HTBT) points b e b uilt
with a b roadcast
frequency of 100msec
instead of 1 second.
OUT1 - Variable Optional - Fail Output for LD, LP

Heartbeat input
signal 1
Heartbeat input
signal 2
Heartbeat input
signal 3
Heartbeat input
signal 4
Heartbeat input
signal 5
Note: The algorithm sets the parameter to a minimum value required for the Ovation network
sub system to detect a timeout. You only have the option to extend the timeout value. Also, if the user -
entered timeout is not an integer multiple of the control task period, the algo rithm rounds up to the user-
entered value to the next highest integer multiple of the control task period.
286 OW351_R1100
5.50 HIGHLOWMON
5.50 HIGHLOWMON
Description
The HIGHLOWMON algorithm is a high and low signal monitor with reset deadband and
fixed/variable limits. For the HIGHLOWMON algorithm, if the input value (IN1) is greater than the
high set point or less than the low set point, the digital output flag is set TRUE. To reset the flag,
the input must be less than the high set point minus the deadband on the high set point, and
greater than the low set point plus the deadband on the low set point.
Functional Symbol
FI E L D RE C O R D

Number
* HISP R1-Real Selectable Required 0.0 High set point LA
HIDB R2-Real Tuning Optional 0.0 Deadband on high -
Constant set point
* LOSP R3-Real Selectable Required 0.0 Low set point LA
LODB R4-Real Tuning Optional 0.0 Deadband on low -

Constant set point
OUT - Variable Required 0.0 Output (digital) LD

default the parameter to a value and mark it as "Optional." However, for the control function to be executed
properly, you must enter a value for the parameter.
Function
IF IN1 > HISP OR IN1 < LOSP

THEN OUT = TRUE
ELSE
IF IN1 < (HISP - HIDB) AND IN1 > (LOSP + LODB)
THEN OUT = FALSE
OW351_R1100 287
5.51 HIGHMON
5.51 HIGHMON
Description
The HIGHMON algorithm is a high signal monitor with reset deadband and a fixed/variable limit.
With the HIGHMON algorithm, if the input value (IN1) exceeds the fixed set point value, the digital
flag is set TRUE. To clear the flag, IN1 must be less than the set point value minus the deadband.
The value of IN1 is checked for invalid real numbers. If IN1 is invalid, OUT retains its last valid
value, and the quality of OUT is set to BAD. The quality of IN1 is not propagated.
Functional Symbol
FI E L D RE C O R D
DIAG LU-Integer Data Init. Required 63 Tuning -

Diagram
Number
* HISP R1-Real Selectable Required 0.0 Set point for LA
the high signal
monitor trip
point
HIDB R2-Real Tuning Required 0.0 Deadband -
Constant

288 OW351_R1100
5.51 HIGHMON
Function
IF IN1 > HISP

THEN OUT = TRUE
ELSE
IF IN1 < (HISP - HIDB)
THEN OUT = FALSE
Note the following:
In the Function above, if neither condition is satisfied, the value of the output is maintained from
the previous value. See below:
For the first loop, if IN1 = 51, HISP = 50, HIDB = 5, then the function would look like this:
IF 51 > 50
THEN OUT = TRUE
ELSE
IF 51 < (50 - 5)
THEN OUT = FALSE
For the first loop, OUT = TRUE
For the second loop, if IN1 = 48, HISP = 50, HIDB = 5, then the function would look like this:
IF 48 > 50
THEN OUT = TRUE
ELSE
IF 48 < (50 - 5)
THEN OUT = FALSE
For the second loop, neither condition is met. Therefore, the value of the output is maintained
from the previous value so OUT = TRUE.
For the third loop, if IN1 = 42, HISP = 50, HIDB = 5, then the function would look like this:
IF 42 > 50
THEN OUT = TRUE
ELSE
IF 42 < (50 - 5)
THEN OUT = FALSE
For the third loop, OUT = FALSE
OW351_R1100 289
5.52 HISELECT
5.52 HISELECT
Description
The HISELECT algorithm performs a gain and bias on four inputs. The output is equal to the
greater of the four values, according to the quality (QUAL) parameter.
The quality (QUAL) parameter contains three options that enable you to select the value and type
of quality that the output point receives.
The WORSE option selects the greater value for an output point, independent of the qualities of
the input points. The output point is assigned the worst quality of the input points.
The SELECTED option also selects the greater value, independent of the qualities of the input
points. The output point is assigned the value and quality of the selected input point. However, if
any of the gained and biased values are equal, the better quality is assigned to the output point.
The NOTBAD option selects the greater gained and biased input value, providing the qualities of
both inputs are not BAD. The quality of the output is set equal to t he quality of the input selected
or to the better quality of the two inputs if the gained and biased input values are equal. If one
input has BAD quality, the gained and bias input value and the quality of the input with the not
BAD quality are assigned to the output. The output is equal to the greater gained and biased input
value and contains BAD quality if both input qualities are BAD.
Note: If the algorithm calculates an invalid output value by using one of the gained and biased
inputs, the value of the other three points is used for the output. In addition, for the NOTBAD
option, if the quality of four input points is BAD, and only one of the inputs is a valid value, the
algorithm selects the valid gained and biased input for the output, and sets the quality of the
output point to BAD.
If the calculated track output is invalid, then the IN2 output is equal to the IN1 input, and the
cascade track output is equal to the IN1 input, if the inputs are valid. If the calculated track
output and the input values are invalid, then the IN1 and IN1 track outputs are not updated.
If the algorithm receives an invalid value as an input, or if it calculates an invalid value as an

Functional Symbol
290 OW351_R1100
5.52 HISELECT
Tracking Signals
of the analog tracking point. This algorithm takes the following action in response to the
information found in the analog input signal TRIN:
Bit description
BI T D E S C R I P TI O N AC TI O N TRK1 S I G N AL
16 Track Implemented and passed Implemented and passed through.

through. Passed through or set Passed through or set TRUE when
17 Track if lower TRUE when IN1 input is not IN2 input is not selected and IN2
selected and IN1 gain is >0* gain is >0*
18 Track if higher Passed through or set TRUE Passed through or set TRUE when
when IN1 input is not selected IN2 input < is not selected and IN2
and IN1 gain is >0* gain is >0*
19 Lower inhibit Passed through** Passed through**
20 Raise inhibit Passed through** Passed through**
22 Not used Not used Not used
23 Deviation Alarm Not used Not used
24 Local Manual mode Not used Not used
25 Manual mode Not used Not used
26 Auto mode Not used Not used
27 Not Used Not used Not used
30 Low limit reached Low limit reached Not used
31 High limit reached High limit reached Not used
** Only when the Track signal is not present; the signals are set according to the definitions given in
Setting Tracking Signals (see page 15).
*** If the algorithm is being told to track, then the Conditional track bit is ignored. Otherwise, the value of
the conditional track bit is transferred to all output track points. If the Conditional Track bit is set in the
track input point, the analog value of all output track points is calculated based on the analog value of the
track input point.
The high and low limit flags, and the tracking signals from the algorithm are output to TRK3 and
TRK4, to be used for display and by upstream algorithms. If the output value is invalid, the quality
of OUT is set to BAD. Otherwise, the quality of OUT is set according to the quality (QUAL)
parameter. When tracking, the quality is set to the quality of the track input variable.
OW351_R1100 291
5.52 HISELECT
FI E L D RE C .

Number
IN1G R1-Real Tuning Required 1.0 Gain on input 1. -
input1 should never
be initialized to
zero; if it is, the
drop is placed into
alarm.
IN1B R2-Real Tuning Optional 0.0 Bias on input 1 -
Constant

input 2 should
never be initialized
to zero; if it is, the
drop is placed into
alarm.
Constant
IN3G R8-Real Tuning Optional 1.0 Gain on input 3. -

input 3 should
drop is placed into
alarm
Constant
IN4G S1-Real Tuning Optional 1.0 Gain on input 4, the -

Constant gain on the input 4
should never be
initialized to zero; if
it is the drop is
placed into alarm
IN4B S2-Real Tuning Optional 0.0 Bias on input 4 -
Constant



292 OW351_R1100
5.52 HISELECT
FI E L D RE C .
QUAL X1-Byte Data Init. Required WORSE Output quality type: -

Bits 0 and 1
WORSE = Worst
quality of the four
inputs is selected.
SELECTED =
Output point is
assigned the
quality of the
selected input
point. If the values
of the input points
are equal, the best
quality is selected.
NOTBAD = The
output point is
assigned the
quality of the
selected input
point, providing the
qualities of the two
inputs are not BAD.
If one input point
quality is BAD, the
output is assigned
the quality of the
not BAD input. The
better quality of the
two inputs is
selected if the input
values are equal.
IN1 - Variable Required - Analog input 1 LA
TRK1 - Variable Required - Track output value LA

mode and status
signals for Input 1
variable

mode status
signals for Input 2
variable
IN3 - Variable Optional - Analog input 3 LA
TRK3 - Variable Optional - Track output value LA

mode signal for
Input 3
IN4 - Variable Optional - Analog input 4 LA
TRK4 - Variable Optional - Track output value LA

mode signal for
Input 4
OW351_R1100 293
5.52 HISELECT
FI E L D RE C .

variable
TRIN - Variable Optional - Tracking and LA
signals analog
input variable
Function
IN1GB = (IN1 x IN1G) + IN1B

IF IN2GB >= IN1GB THEN
OUT = IN2GB
ELSE
OUT = IN1GB
If IN3G >= OUT
OUT = IN3G
If IN4G >= OUT
OUT = IN4G
IF OUT >= TPSC THEN
OUT = TPSC
ELSE
IF OUT <= BTSC THEN
OUT = BTSC
IF OUT >= TPSC

OUT = TPSC
ELSE
IF OUT <= BTSC
OUT = BTSC
294 OW351_R1100
5.53 HSCLTP
5.53 HSCLTP
Description
HSCLTP calculates Enthalpy (H) and Entropy (S) of Compressed Liquid given its Temperature
and Pressure. It is one of the functions of the STEAMTABLE algorithm (see page 544).
Functional Symbol
The following table represents the lower and upper limits of valid values for the algorithm.
However, the calculated output values may be invalid even though the input values are valid.
In the following table, all values are in English units.
HSCLTP input and output values
P AR AME T E R P R O P E R TY L O W V AL U E HI G H V AL U E
(INPUT 1) TEMP 32.0 705.47

(INPUT 2) PRES 0.0885891400 16000.00
(INPUT 3) PRAT * Pressures are added together.
(OUT 1) ENTH -0.017864220 906.01
(OUT 2) ENTR -0.000036890 1.0612
Note: PRAT is set from 12 to 16 psi.
OW351_R1100 295
5.54 HSLT
5.54 HSLT
Description
HSLT calculates Enthalpy (H) of Saturated Liquid given its Temperature. It is one of the functions
of the STEAMTABLE algorithm (see page 544).
Functional Symbol
HSLT input and output values
(INPUT 1) TEMP 32.0 705.47

(OUT 1) ENTH -0.017864220 906.01
296 OW351_R1100
5.55 HSTVSVP
5.55 HSTVSVP
Description
HSTVSVP calculates Enthalpy (H), Entropy (S), Temperature, and Specific Volume of Saturated
Vapor given its Pressure. It is one of the functions of the STEAMTABLE algorithm
(see page 544).
Functional Symbol
HSTVSVP input and output values
(INPUT 1) PRES 0.08858914 32080.234

(OUT 1) ENTH 906.01 1204.8
(OUT 2) TEMP 32.0 705.47
(OUT 3) ENTR 1.0612 2.1873
(OUT 4) VOL 0.05078 3304.7
OW351_R1100 297
5.56 HSVSSTP
5.56 HSVSSTP
Description
HSVSSTP calculates Enthalpy (H), Entropy (S), and Specific Volume of Superheated Steam
given its Temperature and Pressure. It is one of the functions of the STEAMTABLE algorithm (see
page 544).
Functional Symbol
HSVSSTP input and output values
(INPUT 1) TEMP 32.0 1600.0

(INPUT 2) PRES 0.01 16000.0
(OUT 1) ENTH 715.570 1859.85
(OUT 2) ENTR 0.84797280 3.1233000
(OUT 3) VOL 0.0200 122690.0
298 OW351_R1100
5.57 INTERP
5.57 INTERP
Description
The INTERP algorithm provides a linear table-lookup and interpolation function. The algorithm
provides a lookup table for the value of a dependent variable (Y) based on the value of an
independent variable (X). The actual value X (XIN) is input to the algorithm along with up to ten
reference Y values (Y1...Y10) and their corresponding X values (X1...X10).
If the value of the XIN is not identically equal to any of the X1...X10 inputs, then resulting value of
YOUT is calculated by linear interpolation between the closest two values that the input XIN falls
between (that is, Xn + Xn+1). The formula to calculate YOUT is given as follows:
YOUT = Y n + ( (Yn+1 - Yn) * ( (XIN - Xn) / (Xn+1 - Xn) )
The value of YOUT is limited by the user-defined high and low limit values. Refer to the
accompanying figure that illustrates the interpolation procedure.
Functional Symbol
Quality
The algorithm propagates the worst quality between the XIN input and the associated Y inputs
used to determine the value of YOUT. If the output is an exact Y input, then the YOUT quality is
the worst quality of the XIN input and that particular Y input.
User Configuration
The values of X1...X10 MUST be monotonically increasing (that is, Xn+1 > Xn). If the value of the
XIN is found to fall between X1...X10, then the VALID output is set to logic one. If the
monotonicity of the X1 - X10 is not monotonically increasing, then the algorithm may yield
unpredictable results. If the algorithm can determine that the table is not monotonically increasing,
then YOUT is set equal to Y10 and the VALID output is set to logic 0.
If the value of XIN > X10, then YOUT is set equal to Y10. If XIN < X1, then YOUT is set equal to
Y1. In both of these cases, the VALID output is set to logic zero. If the algorithm calculates an
invalid number, then YOUT is set to the last GOOD value and the quality is set to BAD.
If the YOUT is calculated by interpolating between Y n and Y n+1, then the quality of YOUT is the
worst quality of the XIN, Y n and Y n+1 inputs.
OW351_R1100 299
5.57 INTERP
Interpolation Illustration
FI E L D RE C O R D

Number
TYPE X2-Byte Data Init Required Linear Interpolation -
Type. Currently
only linear is
supported.
NUMR X1-Byte Data Init Required 0 Number of X -
values.
X1 R1-Real Tuning Required 0.0 X value -
Constant corresponding to
Y1.
300 OW351_R1100
5.57 INTERP
FI E L D RE C O R D

Y2.
Y3.
Y4.
Y5.
Y6.
Y7.
Y8.
Y9.
X10 S1-Real Tuning Required 0.0 X value -
Y10.
TPSC S2-Real Tuning Required 100.0 Output top of -
Constant scale.
BTSC S3-Real Tuning Required 0.0 Output bottom of -
Constant scale.
XIN - Variable Required - Actual value of X LA
variable (analog)
Y1 - Variable Optional - Output Value LA
1(analog)
Y2 - Variable Optional - Output Value 2 LA
(analog)
(analog)
(analog)
(analog)
(analog)
OW351_R1100 301
5.57 INTERP
FI E L D RE C O R D

(analog)
(analog)
(analog)
(analog)
YOUT - Variable Required - Output Y value LA
(analog)
VALID - Variable Optional - Equals Logic 1 LD
when the XIN
value is found to
fall between two
X values in the
table (digital).
302 OW351_R1100
5.58 KEYBOARD
5.58 KEYBOARD
Description
The KEYBOARD (Key Interface) algorithm interfaces the following control keys (P1 - P8,
Start/Open, Stop/Close, AUTO, MAN, SPUP, SPDN, INC, and DEC) to the Controller in the most
basic form. The output of each key is available for use once the algorithm is activated via a
control select command.
The KEYBOARD algorithm interfaces the Operator Station programmable keys (P1 through P10)
to the Controller in the most basic form. The output of each programmable key is available for use
once the algorithm is activated via a control select key. When using this algorithm, none of the ten
Control keys may be used for the activated control select number.
For the INC, DEC, SPDN, and SPUP keys, the output maintains a TRUE signal for as long as the
key is pressed. For all other keys, the output of this algorithm is a pulse (TRUE signal) of variable
length. The pulse length is determined by the LENGTH (LENG) parameter, which specifies the
pulse length in loops. If LENGTH is equal to 0 or 1, the pulse is 1 loop long. The LENGTH
parameter may specify a pulse length up to 255 loops.
Note: P9 and P10 k eys are the same as Open and Close k eys.
Functional Symbol
OW351_R1100 303
5.58 KEYBOARD
FI E L D RE C O R D

Integer Number
LENG X2-Byte Data Init. Optional 1 Length of output -
pulse in loops.
PK1 - Variable Optional - Output (digital); LD, LP

passed on from
Function Key F1
or Programmable
Key P1.
passed on from
Function Key F2
or Programmable
Key P2.
passed on from
Function Key F3
or Programmable
Key P3.
passed on from
Function Key F4
or Programmable
Key P4.
passed on from
Function Key F5
or Programmable
Key P5.
passed on from
Function Key F6
or Programmable
Key P6.
passed on from
Function Key F7
or Programmable
Key P7.
passed on from
Function Key F8
or Programmable
Key P8.
304 OW351_R1100
5.58 KEYBOARD
FI E L D RE C O R D
OPEN - Variable Optional - Output (digital); LD, LP

Passed on from
KEYBOARD
START/OPEN
CLOS - Variable Optional - Output (digital): LD, LP
Passed on from
KEYBOARD
STOP/CLOSE
SPUP - Variable Optional - Output (digital): LD, LP
Passed on from
KEYBOARD set
point INCREASE
(up arrow).
SPDN - Variable Optional - Output (digital); LD, LP
Passed on from
KEYBOARD set
point Decrease
(down arrow).
AUTO - Variable Optional - Output (digital); LD, LP
Passed on from
KEYBOARD
AUTO
MAN - Variable Optional - Output (digital); LD, LP
Passed on from
KEYBOARD
MANUAL
INC - Variable Optional - Output (digital); LD, LP
Passed on from
KEYBOARD
Output Increase
(up triangle)
DEC - Variable Optional - Output (digital); LD, LP
Passed on from
KEYBOARD
Output Decrease
(down triangle).
OW351_R1100 305
5.59 LATCHQUAL
5.59 LATCHQUAL
Description
The LATCHQUAL algorithm latches and unlatches the quality of an input analog or digital point.
The algorithm sets or clears the “Latched Quality” bit of the IN1 point, depending on SET and
RSET points. Bit 14 of the 2W (second status word) of the analog point or bit 11 of the 2W
(second status word) of the digital point is the “Latched Quality” bit for the point.
Functional Symbol
If RSET is TRUE and the latched quality bit of IN1 is set, the Latched Quality bit is cleared.
If RSET is FALSE and SET is TRUE, then depending on the value of QUAL, the IN1 point sets its
Latched Quality bit and quality as follows:
 If QUAL = 0 and Latched Quality of IN1 is not set, then Latched quality bit is set at its current
state.
 If QUAL = 1 and Latched Quality of IN1 is not set or the Quality of IN1 is not GOOD, then the
Quality is set (latched) to GOOD.
 If QUAL = 2 and Latched Quality of IN1 is not set or the Quality of IN1 is not FAIR, then the
Quality is set (latched) to FAIR.
 If QUAL = 3 and Latched Quality of IN1 is not set or the Quality of IN1 is not POOR, then the
Quality is set (latched) to POOR.
 If QUAL is greater than or equal to 4 and Latched Quality of IN1 is not set or the Quality of
IN1 is not BAD, then the Quality is set (latched) to BAD.
RSET overrides SET. If both are TRUE, then the Latched Quality bit of IN1 is cleared.
Note: IN1 can be a digital or analog point, with the minimum point record being LD or LA. If a
smaller point record is used, then no action is tak en.
306 OW351_R1100
5.59 LATCHQUAL
FI E L D RE C O R D
SET - Variable Required - Digital input. Set LD, LP

Latched Quality bit
flag.
IN1 - Variable Required - Analog/Digital input LD, LA
QUAL - Variable Required - Packed input. Indicates LP

the quality to which IN1
is to be set.
RSET - Variable Required - Digital input. Clear LD, LP

Latched Quality bit
flag.
OW351_R1100 307
5.60 LEADLAG
5.60 LEADLAG
Description
LEADLAG is a nonlinear lead/lag function. The output value is a function of the old output, old
input, new input, gain, lead and lag time constants. In steady state, OUT = IN1 x GAIN (except
when limited). The output achieves 98 percent of the expected steady -state output value in five
time constants.
The algorithm can be configured to be a pure lead function. The output value is a function of the
old output, old input, new input, gain and lead time constants. The output achieves 98% of the
expected steady-state output value in five time constants.
Note: If the algorithm receives an invalid value as an input, or calculates an invalid value as the
Functional Symbol
Tracking Signals
of the analog track point. This algorithm takes the following action in response to the information
found in the analog input signal TRIN:
Bit description
BI T DE S C R I P TI O N A C TI O N TOUT S I G N AL
19 Lower inhibit Implemented Passed through**
20 Raise inhibit Implemented Passed through**
308 OW351_R1100
5.60 LEADLAG

** Only when the Track signal is not present; the signals are set according to the definition given
in Setting Tracking Signals (see page 15).
set to BAD. Otherwise, the quality of OUT is set to the quality of the input when it is not in trac king
Note: If the algorithm generates an invalid track output value, the IN1 input value is used as the
output and IN1 input values are invalid.
FI E L D RE C O R D

Number
GAIN R3-Real Tuning Required 1.0 Gain on input. The -
Constant gain on the input
should never be
placed into alarm

* LEAD R4-Real Selectable Required 0.0 Lead time LA

constant (second)
OW351_R1100 309
5.60 LEADLAG
FI E L D RE C O R D
* LAG R5-Real Selectable Required 30.0 Lag time constant LA

(second)
Note: This is
approximately
1/5 of the total
time to settle. For
example, for a 1
minute total, set
LAG to 12
seconds.
TYPE X2-Byte Tuning Required LEADLAG Type of Function. -

Constant The choices are:
 LEADLAG (0)
 LEAD_ONLY (1)
Default =
LEADLAG
Constant (units per
second).
IN1 - Variable Required - Analog input LA
variable
value, for mode
and status signals
for Input 1
variable
variable
Limiting mode
signals and
tracking value;
analog input
variable
310 OW351_R1100
5.60 LEADLAG
Function
LEADLAG:
OUT = (K1 X IN1) + (K2 X OLDIN1) + (K3 X OLDOUT)
where:
OLDOUT = Previous output
IN1 = Current input
OLDIN1 = Previous input
K1 = GAIN x (H + 2x LEAD) / (H + 2x LAG)
K2 = GAIN x (H - 2x LEAD) / (H + 2x LAG)
K3 = (2x LAG - H) / (2x LAG + H)
H = Sampling time (loop time)
LEAD-ONLY
OUT = [(Gain * (Input - Previous Input)) + k1 * Old Output]/K1 + 1
where:
GAIN = User Gain * (1 + K1)
K1 = Lead Constant/Sampling time (loop time)
OW351_R1100 311
5.61 LEVELCOMP
5.61 LEVELCOMP
Description
The LEVELCOMP algorithm calculates the density compensated water level in a pressurized
steam drum. This compensation assumes a differential pressure transmitter is inputting the raw
level signal. One leg of the transmitter is connected to a condensate reservoir which establishes
the transmitter's maximum water level. The other side of the transmitter is connected to the poi nt
which defines the minimum transmitter water level. The distance between these taps is the
transmitter range “D”. See the following figure for details of the assumed piping configuration.
312 OW351_R1100
5.61 LEVELCOMP
The steam and water inside the drum are at saturation conditions. The water in the condensated
reservoir is pressurized water. The LEVELCOMP algorithm uses the specific volume of the steam
in the drum (µs), the specific volume of the water in the drum (µw) and the specific volume of the
water in the reference leg(µr), and the specific volume of the water at calibration conditions (µcal)
to compute the compensated level. The LEVELCOMP algorithm does the steamtable calculations
to obtain values for µs, µw, and µr based on input points pressure and temperature. The
derivation of µr requires an estimation of the average temperature in the condensate reference
column. The temperature can be a variable point or entered as a tuning constant. The calibration
fluid specific volume (µcal) is an estimated value entered as a tuning constant.
The raw drum level input normally varies from a negative value for minimum level to a positive
value at a maximum to +20 inwc at a maximum with 0 inwc being normal water level. The
minimum (MIN) and maximum (MAX) values are not used in the compensation calculation. The
algorithm output has the same range as the input.
OW351_R1100 313
5.61 LEVELCOMP
If the output value is invalid, the quality of the OUT is set to BAD. If the pressure (PRES) or
temperature (TEMP) value is out of range for the compressed liquid, saturated liquid or saturated
vapor regions, the quality of OUT is set to BAD. Otherwise, the quality of OUT is set to the worst
quality of the inputs.
Functional Symbol
FI E L D RE C O R D
DIAG LU-Integer Data Init Required 112 Tuning diagram -

number
VCAL R1-Real Tuning Required 0.016049 Specific Volume -
Constant of Calibration
fluid (lbs per ft3)
MAX R2-Real Tuning Required 1.0 Maximum Level -
Constant Range
MIN R3-Real Tuning Required 0.0 Minimum Level -

Constant Range
* TEMP R4-Real Selectable Required - Temperature of LA

water in
reference leg (F)
PRES - Variable Required - Drum Pressure LA
(analog) (PSI)
IN1 - Variable Required - Drum Level LA

Transmitter
(analog)
OUT - Variable Required - Output variable LA
(analog)
executed properly, you m ust enter a value for the parameter.
314 OW351_R1100
5.61 LEVELCOMP
Function
Where as D = maximum range level - minimum range level

LIN = IN1 - Min
OW351_R1100 315
5.62 LOG
5.62 LOG
Description
The LOG algorithm performs the mathematical logarithmic function. For the LOG algorithm, the
output equals the base 10 logarithm of the input value plus a bias. If the input value is less than or
equal to zero, the output is set to a large negative number (-3.4 x 1038). The value of IN1 is
checked for invalid real numbers. If IN1 is valid, the quality of IN1 is propagated to the quality of
OUT and the real number value of OUT is written to the point record. If the value of IN1 is invalid
or if the calculated value of OUT written to the point record is invalid, the quality of OUT is set to
BAD.
Note: Other logarithmic algorithms are ANTILOG and NLOG.
Functional Symbol
FI E L D RE C O R D

Number
BIAS R1-Real Tuning Optional 0.0 Bias Factor -
Constant (+ or -)
Function
OUT = LOG10 (IN1) + BIAS
316 OW351_R1100
5.63 LOSELECT
5.63 LOSELECT
Description
The LOSELECT algorithm performs a gain and bias on the four inputs. The output is equal to the
smallest of the four values, according to the quality (QUAL) parameter.
The quality (QUAL) parameter contains three options that enable you to select the value and type
of quality that the output point receives.
The WORSE option selects the lower value for an output point, independent of the qualities of the
input points. The output point is assigned the worst quality of the input points.
The SELECTED option also selects the lowest value, independent of the qualities of the input
points. The output point is assigned the value and quality of the selected input point. However, if
any of the gained and biased values are equal, the best quality is assigned to the output point.
The NOTBAD option selects the lowest gained and biased input value, providing the qualities of
both inputs are not BAD. The quality of the output is set equal to the quality of the input selected
or to the better quality of the two inputs if the gained and biased input values are equal. If one
input has BAD quality, the gained and bias input value and the quality of the input with the not
BAD quality are assigned to the output. The output is equal to the lowest gained and biased input
value and contains BAD quality if both input qualities are BAD.
Note: If the algorithm calculates an invalid output value by using one of the gained and biased
inputs, the value of the other point is used for the output.
If the calculated track output is invalid, then the IN2 track output is equal to the IN2 input, and
the IN1 track output is equal to the IN1 input, if the inputs are valid. If the calculated track
outputs and the input values are invalid, then the IN2 and IN1 track outputs are not updated.
If the algorithm receives an invalid value as an input, or if it calculates an invalid value as an

Functional Symbol
OW351_R1100 317
5.63 LOSELECT
Tracking Signals
Tracking and limiting are done through signals passed in the upper 16 bits of the third status of
the analog tracking point. This algorithm takes the following action in response to the informati on
Bit description
BI T D E S C R I P TI O N AC TI O N TRK1 S I G N AL
16 Track Implemented and passed Implemented and passed

through. Passed through or set through. Passed through or set
17 Track if lower TRUE when IN1 input is not TRUE when IN2 input is not
selected and IN1 gain is >0*. selected and IN2 gain is >0*.
18 Track if higher Passed through or set TRUE Passed through or set TRUE
when IN1 input is not selected when IN2 input is not selected
and IN1 gain is >0*. and IN2 gain is >0*.
20 Raise inhibit Passed through** Passed through**
** Only when the Track signal is not present; the signals are set according to the definitions
given in Setting Tracking Signals (see page 15).
*** If the algorithm is being told to track, then the Conditional track bit is ignored. Otherwise,
the value of the conditional track bit is transferred to all output track points. If the Conditional Track bit
is set in the track input point, the analog value of all output track points is calculated based on the
analog value of the track input point.
318 OW351_R1100
5.63 LOSELECT
The high and low limit flags, and the tracking signals from the algorithm are output to TRK2,
TRK3, and TRK4, to be used for display and by upstream algorithms. If the output value is invalid,
the quality of OUT is set to BAD. Otherwise, the quality of OUT is set according to the QUALITY
(QUAL) parameter. When tracking, the quality is set to the quality of the track input variable.
FI E L D RE C O R D

Number
IN1G R1-Real Tuning Required 1.0 Gain on Input 1. -
input should never
be initialized to
zero; if it is, the
drop is placed into
alarm.
IN1B R2-Real Tuning Optional 0.0 Bias on Input 1. -
Constant

input should never
be initialized to
zero; if it is, the
drop is placed into
alarm.
IN2B R4-Real Tuning Optional 0.0 Bias on input 2. -
Constant
IN3G R8-Real Tuning Optional 1.0 Gain on Input 3. -

input should never
be initialized to
zero.
IN3B R9-Real Tuning Optional 0.0 Bias on Input 3. -
Constant
IN4G S1-Real Tuning Optional 1.0 Gain on Input 4. -

input should never
be initialized to
zero.
IN4B S2-Real Tuning Optional 0.0 Bias on Input 4. -
Constant


OW351_R1100 319
5.63 LOSELECT
FI E L D RE C O R D

Constant (units per second).
QUAL X1-Byte Data Init. Required WORSE Output quality type. -

Bits 0
WORSE = Worst
quality of the four
inputs is selected.
SELECTED =
Output point is
assigned the
quality of the
selected input
point. If the values
of the input points
are equal, the best
quality is selected.
NOTBAD = The
output point is
assigned the
quality of the
selected input
point, providing the
qualities of the two
inputs are not BAD.
If one input point
quality is BAD, the
output is assigned
the quality of the
not BAD input. The
better quality of the
two inputs is
selected if the input
values are equal.
IN1 - Variable Required - Input 1 (analog) LA

mode and status
signals for Input 1
IN2 - Variable Required - Input 2 (analog) LA

mode and status
signals for input 2
variable
IN3 - Variable Optional - Input 3 (analog) LA
TRK 3 - Variable Optional - Track output value LA

mode and status
signals for input 3.
IN4 - Variable Optional - Input 4 (analog) LA
TRK 4 - Variable Optional - Track output value LA

mode and status
signals for input 4.
320 OW351_R1100
5.63 LOSELECT
FI E L D RE C O R D

variable
Limiting mode
signals and
tracking value
analog input
variable
Function
IN1GB = (IN1 x IN1 GAIN) + IN1BIAS

IN2GB = (IN2 x IN2 GAIN) + IN2 BIAS
IN3GB = (IN3 x IN3 GAIN) + IN3BAS
IN4GB = (IN4 x IN4 GAIN) + IN4BAS
IF IN2GB <= IN1GB THEN
OUT = IN2GB
ELSE
OUT = IN1GB
If IN3G <= OUTPUT
OUT = IN3G
If IN4G <= OUTPUT
OUT = IN4G
IF OUT >= TPSC THEN
OUT = TPSC
ELSE
IF OUT <= BTSC THEN
OUT = BTSC
OW351_R1100 321
5.64 LOWMON
5.64 LOWMON
Description
The LOWMON algorithm is a low signal monitor with reset deadband and a fixed variable limit.
For the LOWMON (Low signal monitor, reset deadband) algorithm, if the input value (IN1) goes
below the fixed set point value (LOSP), the digital output is set TRUE. To clear the output, IN1
must be greater than the set point value plus the deadband. The value of IN1 is checked for
invalid real numbers. If IN1 is invalid, OUT retains its last valid value, and the quality of OUT is set
to BAD. The quality of IN1 is not propagated.
Functional Symbol
FI E L D RE C O R D

Number
* LOSP R1-Real Selectable Required 0.0 Set point for the low LA
signal monitor trip
point
LODB R2-Real Tuning Required 0.0 Deadband -
Constant
Function
IF IN1 < LOSP

THEN OUT = TRUE
ELSE
IF IN1 > (LOSP + LODB)
THEN OUT = FALSE
322 OW351_R1100
5.65 MAMODE
5.65 MAMODE
Description
MAMODE is used in conjunction with a MASTATION algorithm. This algorithm is used to send the
priorities (raise/lower), inhibits (raise/lower), reject (manual/auto), track bit and Slew Bias
commands to the MASTATION. If Bias is TRUE, then MASTATION can raise/lower the Bias
value. If Bias is FALSE, the Bias value is slewed to zero and the Bias value is not allowed to be
raised or lowered.
The output TRK, AUTO, MAN and LOC points are set TRUE based on the MASTATION's track
point connected to the algorithm.
Raise/Lower Inhibit and Priorities work as follows:

 When Raise Inhibit and Lower Inhibit occur at the same time, the MASTATION will be locked.
 When Priority Lower and Priority Raise occur at the same time, the MASTATION will ignore
the commands.
 When Raise Inhibit and Priority Raise occur at the same time, the output of the MASTATION
will be locked.
 When Lower Inhibit and Priority Lower occur at the same time, the output of the MASTATION
will be locked.
Functional Symbol
Bits In Mode
Bit 0 Priority Lower
Bit 1 Priority Raise

Bit 2 Low Inhibit
Bit 3 High Inhibit
Bit 4 Manual Reject
Bit 5 Auto Reject
Bit 6 Bias Active
Bit 7 Set Tracking Bit
Bit 8 Indicate Low Inhibit
Bit 9 Indicate High Inhibit
OW351_R1100 323
5.65 MAMODE
Bit 10 Local Mode

Bit 11 MASTATION is in manual mode
Bit 12 MASTATON is in auto
Bit 13 MASTATON is told to track
Bit 14 RLI priority lower
Bit 15 RLI priority raise
Note: If a mode word is provided, its contents are decoded and shown in the Control Builder i n
the bottom status bar along with the track words. See Ovation Control Builder User Guide for
more information.
FI E L D RE C O R D
PLW - Variable Optional - Priority Lower input LD, LP
PRA - Variable Optional - Priority Raise input LD, LP

LWI - Variable Optional - Lower Inhibit input LD, LP
RAI - Variable Optional - Raise Inhibit input LD, LP
MRE - Variable Optional - Manual Reject input LD, LP
ARE - Variable Optional - Auto Reject input LD, LP
BACT - Variable Optional - Bias Active input LD, LP
STRK - Variable Optional - Set MASTATION LD, LP
track bit
TRK - Variable Optional - MASTATION is LD, LP
based on TRIN
point
AUTO - Variable Optional - Auto Mode output LD, LP
MAN - Variable Optional - Manual Mode LD, LP

output
LOC - Variable Optional - Local Mode output LD, LP
MODE - Variable Optional - Output to LP
MASTATION
324 OW351_R1100
5.66 MASTATION
5.66 MASTATION
Description
MASTATION algorithm interfaces a CRT-based soft manual/auto station and an optional Ovation
Loop Interface module card with the functional processor.
The following modes are available: Auto, Manual, and Local.
You select one of the following interfaces with the TYPE Algorithm Field:
 SOFT - Soft manual/auto station only

 RLI - Ovation Loop Interface module
 RVP - Ovation Valve Position module
Functional Symbol
If an Ovation Loop Interface Module is set in TYPE and the Controller is reset, powered-up or
fails, the output is read from the Ovation Loop Interface module card and used initially in the OUT
field of the algorithm. This reports the status of the field device before any action is taken by either
the algorithm or the operator.
Note: The TPSC and BTSC parameters are used to limit the output value of the algorithm.
These values must always be 100% and 0%, respectively when a SLIM interfaces to an
Ovation Loop Interface module card.
OW351_R1100 325
5.66 MASTATION
Auto Mode
The output equals the gained and biased input plus the bias bar value
(OUT = (IN1 x IN1 GAIN) + IN1 BIAS + BIAS BAR) except:
 When the algorithm is told to track, the output equals the track input when the tracking signal
is present. The output ramps from the track input back to the gained and biased input when
the tracking signal is removed.
 When a raise inhibit or lower inhibit signal is present, it may prevent the output from following
the input.
The bias bar value is output as an analog value and may be raised or lowered by the
Increase/Decrease set point keys (arrow up/arrow down) on the Operator's Keyboard. This value
is only added to the output value in Auto mode; it has no effect on the output (but still may be
raised or lowered) in Manual or Local mode.
If an Ovation Loop Interface module is selected, the output value is written to the card.
The Increase/Decrease Output keys on the Operator's Keyboard have no effect in this mode.
Manual Mode
The output is raised or lowered by using the Increase/Decrease Out put requests. The raise inhibit
and lower inhibit signals override the Operator's Keyboard Increase/Decrease Output requests.
The tracking signal causes the output to equal the track input, regardless of the raise/lower inhibit
signals and the Increase/Decrease Output key requests. The bias bar value has no effect on the
output, but still may be raised and lowered.
If an LI interface is selected, the output value is written to the card. The output value may also be
raised or lowered from the Loop Interface Module (SLIM) in this mode.
Local Mode
This mode is only available if an LI Module, type interface has been selected. The
Increase/Decrease commands from the SLIM directly control the LI card, which is in Local mode.
The algorithm either reads the demand counter on the LI, and causes its output to track the card's
value. In this tracking mode, all directional commands inside the functional processor (for
example, Variable Input, Raise Inhibit and Lower Inhibit) and directional commands from the
Operator's/Alarm Console (for example, Increase, Decrease) have no effect on the algorithm.
Mode Transfers
The algorithm transfers between the Auto, Manual, and Local modes as follows:
 The digital reject signal from the MAMODE Algorithm rejects the algorithm from Auto to
Manual mode.
 The Auto Request and Manual Request signals from the AUTO and MAN mode request keys
on the Operator's Keyboard switch the algorithm to the desired mode if it is not in Local mode.
 If the LI is selected, the SLIM can switch the algorithm between Auto, Manual, and Local
modes.
 If the LI is selected, and if there are hardware errors, the algorithm rejects to Local mode. If
the card determines that there is a SLIM communications error while it is in Local mode, it
rejects the card to Manual mode. The algorithm also goes to Manual mode.
326 OW351_R1100
5.66 MASTATION
 If the Quality Reject (REJQ) feature is OFF, then the quality check is not performed on the
input when in Auto mode. If the algorithm is in Auto mode and the quality of the input goes
BAD or not GOOD depending on the Quality Reject flag, then the algorithm rejects the card to
Manual mode.
 Regardless of the REJQ parameter, the input value (IN1) is checked for an invalid value when
the algorithm is in Auto mode. If the algorithm is in Auto mode and the value of the i nput
becomes invalid, the algorithm rejects the card to Manual mode. If the algorithm is not in Auto
mode and the operator tries to select Auto mode when the input value is invalid, the algorithm
remains in the same mode and does not reject the card to Manual mode.
 The track input value is also be checked for invalid real numbers when the algorithm is being
told to track. While in Auto mode, if the algorithm is told to track and the track input value is
invalid, the algorithm rejects the card to Manual mode. In all modes, the track request is
ignored when the track input value is invalid.
 On reset/power-up, the algorithm is in Local mode if a LI interface is selected. If a soft
interface is selected, then the algorithm goes to the mode initialized by the First pass mode
(FP) parameter.
 On reset/power-up of the LI card, if LI interface is selected and RLI priority (PRLI) is YES,
then the algorithm is set to local mode and the output value is zero. If the LI interface is
selected and RLI priority (PRLI) is NO, then the algorithm changes the RLI card mode from
local to the last mode before the card is powered down. The LI analog output value is
initialized to the last output value before the card was powered off.
The interface keys of the Operator's Keyboard are:
Key usage
KE Y US E
AUTO Function Key Auto mode request
MAN Function Key Manual mode request

Set Point Increase Function Key Raise the bias bar (up arrow)
Set Point Decrease Function Key Lower the bias bar (down arrow)
Output Increase Function Key Raise the output (up triangle)
Output Decrease Function Key Lower the output (down triangle)
OW351_R1100 327
5.66 MASTATION
Manual Reject Output Point
The MRE point becomes true for the amount of time specified in the MRET parameter. The
algorithm sets the point true anytime the algorithm goes to manual (unless specified by operator
request).
Priority Raise/Lower
The Priority Raise/Lower functionality (PRAR, PRAT, PLWR, PLWT parameters) is available
when the MODE input pin is connected to output of MAMODE algorithm.
If bit 0 (Priority Lower) in MODE pin is active, the MASTATON output is decreased with the rate
defined by the PLWR (Priority Lower Rate) parameter. In that case, the output is going to the
value defined by the PLWT (Priority Lower Target) parameter. If the PLWT value is lower than the
BTSC limit, the MASTATION output stops on the BTSC limit.
If bit 1 (Priority Raise) in MODE pin is active, the MASTATON output is increased with the rate
defined by the PRAR (Priority Raise Rate) parameter. In that case, the output is going to the
value defined by the PRAT (Priority Raise Target) parameter. If the PRAT value is lower than the
TPSC limit, the MASTATION output stops on the TPSC limit.
If both bits (Priority Lower and Priority Raise) are active at the same time, the MASTATION will
ignore these commands.
Operational Symbol
The following symbol illustrates the operation of MASTATION via a SAMA representation.
328 OW351_R1100
5.66 MASTATION
Tracking Signals
of the analog track point. This algorithm takes the action shown in the following table in response
to the information found in the analog input signal TRIN.
Bit description
16 Track Implemented Passed through, set TRUE on first pass

to read the hardware, or set TRUE
when not in Auto mode.

19 Lower inhibit Implemented* Passed through*
20 Raise inhibit Implemented Passed through***
24 Local Manual mode No action Local mode
25 Manual mode No action Manual mode
26 Auto mode No action Auto mode
* Only when the Track s ignal is not present.
** Only when the Track signal is not present; the signals are set according to the definitions given
*** If the algorithm is being told to track, then the Conditional track bit is ignored. Otherwise, the
Note: If a mode word is provided, its contents are decoded and shown in the Control Builder in
the bottom status bar along with the track words. See Ovation Control Builder User Guide for
more information.
The high and low limit flags, the mode and the tracking signals from the algorithm are output to
TOUT, to be used for display and by an upstream algorithm. The configuration of the use of this
algorithm must be specified by the user for correct implementation of the track ing features. If the
upstream algorithm is BALANCER, then the configuration must indicate that this algorithm is
being used with the BALANCER algorithm. Otherwise, the configuration is specified as NORMAL.
OW351_R1100 329
5.66 MASTATION
If a BAD hardware status error caused the algorithm to reject to Local, the quality remains BAD
on the output and the algorithm remains in Local mode until the error is cleared. If a write error
caused the algorithm to reject to Local, the quality becomes GOOD on the output and the
algorithm remains in Local mode until Local mode is exited via the SLIM.
If there are no hardware errors, the quality of OUT is set to the quality of the track input variable
when tracking. Otherwise, the quality of OUT is GOOD when in Manual mode or set to the quality
of the input when in Auto mode.
If the algorithm calculates an invalid real number for the output in Auto mode, the quality of OUT
is set to BAD and the drop is placed into alarm.
The TPSC and BTSC parameters are used to limit the output value of the algorithm. These values
must always be 100% and 0%, respectively, when interfacing to an LI card which is connected to
a SLIM.
Any output raise or lower request, from the Operator Station is sent directly to the LI configured as
an electric drive card type when it is in Failed Local mode. The LI outputs any SLIM raise or lower
requests for the output, then outputs any controller raise or lower requests for the output to the
digital raise or lower outputs.
When the position feedback signal of an LI configured as an electric drive card type fails, the LI
goes to Failed Local mode and the value of output point is the feedback signal from the drive. The
output bar SLIM display flashes between 0 and 100% to indicate the Failed Local mode.
The options to have runbacks and/or interface to an electric drive on the LI card must be
configured through the I/O Builder.
CAUTION! When using the MASTATION algorithm with a BALANCER algorithm, follow these
guidelines:
1. If MASTATION precedes BALANCER, set the MASTATION CNFG parameter to NORMAL.
2. For all MASTATIONS that immediately follow BALANCER, set MASTATIONS CNFG
parameter to BALANCER.
3. For MASTATIONS that follow MASTATIONS in Guideline 2, set CNFG parameter to

NORMAL.
330 OW351_R1100
5.66 MASTATION
FI E L D RE C O R D

Number
IN1G R5-Real Tuning Required 1.0 Gain on input. The -
Constant cascade gain should
drop is placed into
alarm.
IN1B R6-Real Tuning Optional 0.0 Bias on input -
Constant
* TPSC R7-Real Selectable Required 100.0 Maximum value of LA

the output point
* BTSC R8-Real Selectable Required 0.0 Minimum value of LA
the output point
TPBS R2-Real Tuning Required 0.0 Maximum value of -
Constant the bias bar
BTBS R3-Real Tuning Required 0.0 Minimum value of -
PCNT X1-Byte Tuning Required 4 Percent change in -
Constant first four seconds
TIME X2-Byte Tuning Required 25 Number of seconds -
Constant remaining for ramp
to full scale
FP G0-Integer Data Init. Required MANUAL First pass mode. -

Bit 8 Algorithm goes to
this mode on
reset/power-up:
MANUAL: Manual
mode
AUTO: Auto mode
TYPE G0-Integer Data Init. Optional SOFT Interface Card type: -
Bits 0
SOFT: Soft M/A only
and 1
RLI: LI card
RVP: VP Card
DRVE G0-Integer Data Init Optional NO Electric Drive: -
Bit 9
NO
YES
OW351_R1100 331
5.66 MASTATION
FI E L D RE C O R D
CARD X5-Byte Data Init Optional 1 PCI Card Number -

(1, 2)
For OCR400 - 1 only
For OCR1100 - 1
only
HWAD B2-Integer Data Init. Optional 0 Card address (see -
page 3) for any
hardware interface
(in decimal bytes).
RDNT X3-Byte Data Init Required NO Redundant RVP -

Bit 0 cards:
NO
YES
HWA2 YU-Integer Data Init Required 0 Redundant RVP -
hardware address
PRLI G0-Integer Data Init Required YES RLI Priority: -

Bit 2
YES
NO
PRAR S1-Real Tuning Optional 2.5 Priority Raise Rate -
Constant
PRAT S2-Real Tuning Optional 100.0 Priority Raise Target -

Constant
PLWR S3-Real Tuning Optional 2.5 Priority Lower Rate -
Constant
PLWT S4-Real Tuning Optional 0.0 Priority Lower -
Constant Target
332 OW351_R1100
5.66 MASTATION
FI E L D RE C O R D
REJQ G0-Integer Data Init. Required BAD Quality reject type -

Bits 6 and 7 (only has meaning if
Manual Inhibit is
OFF):
BAD: Algorithm
rejects to Manual
mode when the
quality of the IN1
input goes BAD and
the algorithm is in
Auto mode.
NOTGOOD:
Algorithm rejects to
Manual mode when
the quality of the IN1
input is NOT GOOD
and the algorithm is
in Auto mode.
OFF: The quality of
the IN1 input is not
checked or used to
reject the algorithm
to Manual mode
when the algorithm
is in Auto mode.
CNFG G0-Integer Data Init. Required NORMAL Configuration type: -
Bit 5
NORMAL: -
Upstream algorithm
is not BALANCER
BALANCER: -
Upstream algorithm
is BALANCER
Constant
MRET G1 Tuning Optional 5 Manual reject time in -
Constant seconds.
MRE - Variable Optional - Manual reject point LD
IN1 - Variable Required - Input 1 variable LA

analog input

mode and status
signals for Input 1
variable
OW351_R1100 333
5.66 MASTATION
FI E L D RE C O R D
MODE - Variable Optional - Output point from LP

the MAMODE
algorithm
variable
Limiting mode
signals and tracking
value; analog Input
variable
BIAS - Variable Optional - Analog bias bar LA
variable output
334 OW351_R1100
5.67 MASTERSEQ
5.67 MASTERSEQ
Description
The MASTERSEQ (SEQUENCER, MASTER) algorithm provides a supervisory algorithm to

control sequential execution of control functions. The algorithm utilizes individual DEVICESEQ
algorithms to provide an interface to the logic functions being executed in each step of the
sequence. Each MASTERSEQ algorithm can have a maximum of 30 DEVICESEQ algorithms
attached. Each of the individual DEVICESEQ algorithms is referred to as a device. If more than
30 devices are required, then multiple MASTERSEQ algorithms can be cascaded together.
The algorithm monitors the device that corresponds to each step via a packed group point. This
packed group point is termed the status point. There is a unique status point for each device. The
status point serves as both input and output for the MASTERSEQ and DEVICESEQ algorithms
according to the bit definitions in the accompanying table. A device is considered “on” or “running”
when bit zero, in its associated packed group status point, is equal to logic 1. Likewise a device is
considered “off” or “stopped” when bit zero is equal to logic zero.
Functional Symbol
OW351_R1100 335
5.67 MASTERSEQ
User Configuration
The attached devices are numbered sequentially from 1-30 and the associated default status
points are named DV01-DV30 respectively. These 30 devices can be sequenced in any user-
defined order. The 30 integer fields in the algorithm template (ST01-ST30) correspond to the 30
possible steps. The steps are numbered sequentially. In order to associate a particular device
with a step number, the device number is included in the integer field that corresponds to that
step number. A particular device can be included in multiple steps in the sequence. The current
step number being considered by the MASTERSEQ is stored in the STEP output.
In the following sections, a step is considered complete when the DEVICE SEQ algorithm
assigned to that step indicates a success or failure or the user overrides the step via the OVRD
input. If a step references a device that does not exist or a zero is specified as the device number
for a particular step, then, that step is skipped and the algorithm increments the step.
The MASTERSEQ algorithm can operate in two modes. These are normal mode and priority
mode. In normal mode, the step numbers increase sequentially and the corresponding devices
are executed accordingly. In priority mode, the step number that corresponds to the device to be
executed is input to the algorithm via the TKIN input. That step is executed when the TMOD input
is TRUE. The order of the steps does not need to be sequential. This allows the sequence to be
dynamically adaptive based on the requirements of a particular application.
The algorithm is reset to the initial state when the RSET input is TRUE regardless of the mode of
operation. Any time the RSET input is TRUE, it causes the algorithm to clear all bit s in the status
point, stop any device that is currently running, and set the current step to zero. Refer to the reset
flow chart for a visual depiction of the actions performed when the RSET input is TRUE.
Initial State
The initial step of the algorithm, on power-up, is zero. At step zero, no devices are active. In
normal mode, if the ENBL input is equal to logic one, the algorithm sequences to the first
available step. If the ENBL input is equal to logic 0, then all devices are ignored and remain in
their previous state and the algorithm is inactive. A step is considered to be available if its
associated device number corresponds to a DEVICESEQ algorithm that is connected to the
MASTERSEQ algorithm. If the device number is valid, the device is considered for execution
according to the rules outlined in the following sections. If the ENBL input is FALSE the algorithm
is inactive regardless of the mode of operation.
Normal Mode Step Execution and Control
In the normal mode of operation, the sequential execution of the connected devices is controlled
via the PRCD and OVRD inputs on the algorithm. The PRCD input acts as a “start” button. If the
PRCD input is TRUE, the algorithm reads the value of the READY and FAILED bits from the
associated status point. Refer to the description of the DEVICESEQ algorithm for details on how
the READY and FAILED bits in the status point are initialized. If the associated device is READY
and not FAILED, the algorithm sets bit one, in the status point that corresponds to that devic e, to
logic 1.
If the READY bit in the status point is FALSE, the algorithm sets the HOLD output to logic 1. If the
FAILED bit is TRUE, the algorithm sets HOLD output to logic 1. In both of these conditions, the
algorithm remains at the current step.
336 OW351_R1100
5.67 MASTERSEQ
If while a device is running, the SUCCESS bit becomes TRUE in the corresponding status point,
the algorithm sets bit zero in the status point to logic 1 (thus stopping the device) and the step is
incremented to the next step sequential number. The next device is not started unless the PRCD
input is TRUE.
If while a device is running, the FAILED bit becomes TRUE in the status point, the step number is
not be incremented and both the HOLD and FAIL outputs are set to logic 1. Once this condition is
reached, one of the following actions must occur in order for the step to increment:
A. The FAIL condition must be cleared which causes the FAIL output to be set to logic zero and
the step is incremented to the next sequential number.
B. The OVRD input must be set to logic 1, which causes the step to increment to the next
sequential number.
If at any time during execution, the OVRD input becomes equal to logic 1, the algorithm
increments the current step. If the OVRD input is equal to logic 1 while a particular step is bei ng
executed, the algorithm turns the corresponding device off and the step number is incremented to
the next available step. Any tine the step is incremented as a result of the OVRD input, the
OVERRIDE bit is set to 1 at the status point. This provides a history feature for each step to
indicate how the step number was advanced. If the PRCD and OVRD inputs are equal to logic 1
simultaneously, the OVRD takes precedence.
When the last step in the sequence has completed, the algorithm sets the DONE output logi c to 1.
At this point, the algorithm must be reset to begin operation again.
Refer to the normal mode flow chart for a visual depiction of the operation of the algorithm when
operating in normal mode.
Priority Mode Step Execution and Control
In priority mode, the step number to be executed is determined by the analog value of the TKIN
input. Any fractional value to the right of the decimal point, in the TKIN input value, is truncated.
This gives you the ability to dynamically steer the algorithm to any desired step in the sequence.
The value of the TKIN input is used as the step number only if the TMOD input is TRUE. Thus the
algorithm is considered to be in priority mode when the step number is determined from the TKIN
input. As in normal mode, the PRCD input must be TRUE in order for the execution of the step to
begin.
If the value of TKIN is equal to a step that corresponds to a valid device, the TMOD input is TRUE
and PRCD input is FALSE, the algorithm sets the current step to the TKIN value. However, the
step is not executed until the PRCD input becomes TRUE. When operating in Priority Mode, the
algorithm ignores the OVRD input. If the value of the TKIN refers to a device that does not exist,
the algorithm remains at the previous step. If a device is running, the TKIN and TMOD inputs are
ignored until the step completes.
If the MODE parameter is advisory, TKIN must be less than the maximum number of steps
(NMIN). If the MODE parameter is priority, then TKIN must be less than 30 (the total number of
allowed steps). This applies only in priority mode. All other checks for valid device apply no matter
what the priority MODE parameter is set to.
If the READY bit, in the status point, is TRUE and the FAILED bit is FALSE, the algorithm issues
a start to the associated device. This is accomplished by setting bit zero in the status point to logic
1.
OW351_R1100 337
5.67 MASTERSEQ
If the READY bit in the status point is FALSE, the algorithm sets the HOLD output logic to 1. If the
FAILED bit is TRUE, the algorithm sets both the HOLD and FAIL output to logic 1. In both of
these conditions, the algorithm remains at the current step.
If while a device is running, the SUCCESS bit becomes TRUE in the corresponding status point,
the algorithm sets bit zero in the status point logic 0 (thus stopping the device). The step is set to
the value of the TKIN input if it is a valid step. The next device is not started unless the PRCD
input is TRUE.
If while a device is running, the FAILED bit becomes TRUE in the status point, both the HOLD
and FAIL outputs are set to logic 1. When this condition is reached, the current step can be
changed via the TKIN and TMOD inputs.
Refer to the priority mode flow chart for a visual depiction of the operation of the algorithm when
operating in priority mode.
If any time during the priority mode operation the TMOD input becomes FALSE, the algorithm
reverts to normal mode operation. The hybrid mode section outlines the operation of the algorithm
using a combination of normal mode and priority mode.
Hybrid Mode Operation
It is possible to operate the algorithm in a hybrid mode where some steps are performed in
normal mode and others in Priority Mode. The mode switch is controlled by the digital value of the
TMOD input and thus can be done dynamically. When operating in normal mode, the normal
mode rules outlined above apply and when operating in priority mode, the priority mode rules
above apply.
FI E L D RE C O R D

Number
MODE X2-Byte Data Init Required Advisory Mode of -
operation:
Advisory
Priority
NMIN X1-Byte Tuning Required 0 Number of Steps -
Constant
ST01 G0- Integer Tuning Required 0 Device Number -

Constant for Step 1

Constant for Step 2

Constant for Step 3
338 OW351_R1100
5.67 MASTERSEQ
FI E L D RE C O R D

Constant for Step 4

Constant for Step 5

Constant for Step 6

Constant for Step 7

Constant for Step 8

Constant for Step 9

Constant for Step 10
ST11 B0- Integer Tuning Required 0 Device Number -



ST14 YU- Integer Tuning Required 0 Device Number -







ST21 C0- Integer Tuning Required 0 Device Number -



OW351_R1100 339
5.67 MASTERSEQ
FI E L D RE C O R D






ST30 YT- Integer Tuning Required 0 Device Number -

ENBL - Variable Required - MASTERSEQ is LD, LP

inoperative
anytime this
signal is FALSE.
OVRD - Variable Required - Proceed to next LD, LP
step ignoring any
status of the
current step.
PRCD - Variable Required - Execute the LD, LP
current step.
RSET - Variable Required - Re-Initializes LD, LP
algorithm to step
zero.
TKIN - Variable Optional - Dynamic step LA
value.
TMOD - Variable Optional - Activate Priority LD, LP
mode.
FAIL - Variable Required - TRUE When a LD, LP
DEVICESEQ
algorithm reports
a failure.
HOLD - Variable Required - TRUE when LD, LP
algorithm is
waiting to
execute current
step.
340 OW351_R1100
5.67 MASTERSEQ
FI E L D RE C O R D
DONE - Variable Required - TRUE When LD, LP

Master
completes last
defined step.
(Can be used to
daisy chain
multiple
MASTERSEQ).
STEP - Variable Required - Number of LA
current step
(1-30)
DV01 - Variable Required - Communication LP
with Device
Algorithm 1
(See Bit
Definitions)
DV02 - Variable Optional - Communication LP
with Device
Algorithm 2
(See Bit
Definitions).
with Device
Algorithm 3
(See Bit
Definitions).
with Device
Algorithm 4
(See Bit
Definitions).
with Device
Algorithm 5
(See Bit
Definitions).
with Device
Algorithm 6
(See Bit
Definitions).
with Device
Algorithm 7
(See Bit
Definitions).
OW351_R1100 341
5.67 MASTERSEQ
FI E L D RE C O R D

with Device
Algorithm 8
(See Bit
Definitions).
with Device
Algorithm 9
(See Bit
Definitions).
with Device
Algorithm 10
(See Bit
Definitions).
with Device
Algorithm 11
(See Bit
Definitions).
with Device
Algorithm 12
(See Bit
Definitions).
with Device
Algorithm 13
(See Bit
Definitions).
with Device
Algorithm 14
(See Bit
Definitions).
with Device
Algorithm 15
(See Bit
Definitions).
with Device
Algorithm 16
(See Bit
Definitions).
342 OW351_R1100
5.67 MASTERSEQ
FI E L D RE C O R D

with Device
Algorithm 17
(See Bit
Definitions).
with Device
Algorithm 18
(See Bit
Definitions).
with Device
Algorithm 19
(See Bit
Definitions).
with Device
Algorithm 20
(See Bit
Definitions).
with Device
Algorithm 21
(See Bit
Definitions).
with Device
Algorithm 22
(See Bit
Definitions).
with Device
Algorithm 23
(See Bit
Definitions).
with Device
Algorithm 24
(See Bit
Definitions).
with Device
Algorithm 25
(See Bit
Definitions).
OW351_R1100 343
5.67 MASTERSEQ
FI E L D RE C O R D

with Device
Algorithm 26
(See Bit
Definitions).
with Device
Algorithm 27
(See Bit
Definitions).
with Device
Algorithm 28
(See Bit
Definitions).
with Device
Algorithm 29
(See Bit
Definitions).
with Device
Algorithm 30
(See Bit
Definitions).
344 OW351_R1100
5.67 MASTERSEQ
Status Bit Definitions
BI T O R I G I N ATO R S I G N AL N AME DE S C R I P TI O N
N U MB E R
0 MASTERSEQ GO Signal to Device to Begin Step.
1 DEVICESEQ FAILED Signal to MASTERSEQ that Current Step

Encountered a Failure.
2 DEVICESEQ READY Signal to MASTERSEQ that the low-level Logic is

Ready to Receive a Remote Start Command.
3 DEVICESEQ SUCCESS Signal to MASTERSEQ that current Step

Completed Successfully.
4 MASTERSEQ INSTEP Signal from Master that the step is currently being
Executed.
5 MASTERSEQ OVERRIDE When TRUE indicates that the OVRD input was
used to Increment the step.
6 MASTERSEQ RESET MASTERSEQ sets this bit logic 1 when reset

input is TRUE.
7 DEVICESEQ FROZEN This bit is TRUE when DEVICESEQ has Frozen

updates to the status point (see DEVICESEQ
section for data)
8 - 15 Reserved for - -
future use.
OW351_R1100 345
5.67 MASTERSEQ
346 OW351_R1100
5.67 MASTERSEQ
OW351_R1100 347
5.68 MEDIANSEL
5.68 MEDIANSEL
Description
The MEDIANSEL (Median value selector, quality and deviation checks) algorithm monitors analog
transmitter inputs for quality and deviation from each other. The output (OUT) of the algorithm is
the median of the three analog inputs as long as there are no Quality or Deviation Alarms.
Otherwise, the algorithm determines the best or most probably correct input or average of inputs
for the output value. In addition to the output signal (OUT), there is a High Alarm analog output
(HI), a Low Alarm analog output (LO) and 12 digital signals, indicating the states of the inputs,
which may be output as individual digital points or as a packed digital record.
Functional Symbol
The type of quality on the input that sets the Quality Alarm for that point is initialized in the Control
Indicator Word. The Control Deviation Alarm digital output signal between two points is set TRUE
when the difference of the two points is greater than the user-initialized Control Deviation
Deadband (CNDB) and the two points are not in Quality Alarm. Also, the Alarm Deviation Alarm
digital output signal between two points is set TRUE when the difference of the two points is
greater than the user-initialized Alarm Deviation Deadband (ALDB) and the two points are not in
Quality Alarm. The Alarm Deviation Deadband should be less than the Control Deviation
Deadband for the algorithm to function properly.
If all three transmitters are in Quality Alarm, the output value remains the last GOOD value. In
addition, if all three transmitters are in quality alarm or if the output (OUT) value is invalid, the
quality of the output is set to BAD.
If two transmitters are in Quality Alarm, the output value is the value of the transmitter that is
not in Quality Alarm.
If one transmitter is in Quality Alarm and there is no Control Deviation Alarm between the
two transmitters not in Quality Alarm, the output value is the average of the two transmitters
not in Quality Alarm.
348 OW351_R1100
5.68 MEDIANSEL
If one transmitter is in Quality Alarm and there is a Control Deviation alarm between the
two transmitters not in Quality Alarm, the output value is:
1. The higher value of the two transmitters not in Quality Alarm if the higher value is greater than
the High Alarm Monitor value (HMTR) and the lower value is not less than the Low Alarm
Monitor value (LMTR).
OR
2. The lower value of the two transmitters not in Quality Alarm if the lower value is less than the
Low Alarm Monitor value and the higher value is not greater than the High Alarm Monitor
value.
OR
3. Either the higher or lower value of the two transmitters not in Quality Alarm, depending on the
High/Low Output parameter initialized in the Control Indicator Word.
If none of the transmitters are in Quality Alarm but all three transmitters are in Control
Deviation with each other, the output value is:
1. The highest value of the transmitters if the higher value is greater than the High Alarm Monitor
value (HMTR) and the lowest value is not less than the Low Alarm Monitor value (LMTR).
OR
2. The lowest value of the transmitters if the lowest value is less than the Low Alarm Monitor
value and the highest value is not greater than the High Alarm Monitor value.
OR
3. Either the highest or lowest value of the transmitters, depending on the High/Low Output
parameter initialized in the Control Indicator Word.
If none of the transmitters are in Quality Alarm but one transmitter is in Control Deviation
with both of the other two transmitters and there is no Control Deviation alarm between the
other two transmitters, the output value is the average of the two transmitters not in Control
Deviation Alarm with each other. If none of the transmitters are in Quality Alarm and two
transmitters are in Control Deviation Alarm with each other but not with the third transmitter, the
output value is the value of the third (median) transmitter.
If none of the transmitters are in Quality or Control Deviation Ala rm and either all or none
of the three transmitters are in Alarm Deviation with each other, the output is the median
value of the transmitters.
If none of the transmitters are in Quality or Control Deviation Ala rm but one transmitter is
in Alarm Deviation with both of the other two transmitters and there is no Alarm Deviation
between the other two transmitters, the output value is the average of the two transmitters not
in Alarm Deviation with each other.
If none of the transmitters are in Quality or Control Deviati on Alarm and two transmitters
are in Alarm Deviation with each other but not with the third transmitter, the output value is
the value of the third (median) transmitter.
If none of the transmitters are in Control Deviation Alarm with each other, the high alarm
output and low alarm output values are set equal to the output value. Otherwise, the high alarm
output value is set equal to the highest transmitter value not in Quality Alarm, and the low alarm
output value is set equal to the lowest transmitter value not in Quality Alarm.
OW351_R1100 349
5.68 MEDIANSEL
The Transmitter Quality Alarm digital output (XBQ) is set TRUE when all three transmitters are in
Quality Alarm. The Transmitter A Quality Alarm digital output (XABQ) is set TRUE when
Transmitter A is in Quality Alarm. The Transmitter B Quality Alarm digital output (XBBQ) is set
TRUE when Transmitter B is in Quality Alarm. The Transmitter C Quality Alarm digital output
(XCBQ) is set TRUE when Transmitter C is in Quality Alarm.
The Transmitter A - Transmitter B Control Deviation Alarm digital output (ABDC) is set TRUE
when the deviation between Transmitter A and Transmitter B is greater than the Control Deviation
Deadband. The Transmitter A - Transmitter C Control Deviation Alarm digital output (ACDC) is set
TRUE when the deviation between Transmitter A and Transmitter C is greater than the Control
Deviation Deadband. The Transmitter B - Transmitter C Control Deviation Alarm digital output
(BCDC) is set TRUE when the deviation between Transmitter B and Transmitter C is greater than
the Control Deviation Deadband.
The Transmitter A - Transmitter B Alarm Deviation Alarm digital output (ABDA) is set TRUE when
the deviation between Transmitter A and Transmitter B is greater than the Alarm Deviation
Deadband. The Transmitter A - Transmitter C Alarm Deviation Alarm digital output (ACDA) is set
TRUE when the deviation between Transmitter A and Transmitter C is greater than the Alarm
Deviation deadband. The Transmitter B - Transmitter C Alarm Deviation Alarm digital output
(BCDA) is set TRUE when the deviation between Transmitter B and Transmitter C is greater than
the Alarm Deviation Deadband.
The Transmitter Malfunction Alarm digital output (XALM) is set TRUE when there is a Quality
Alarm on any of the three signals or when the deviation between any two transmitter values is
greater than either the Control Deviation Deadband or the Alarm Deviation Deadband.
The Manual Reject digital output (MRE) is set TRUE:
1. When all three transmitters are in Quality Alarm.

OR
2. When there is one point in Quality Alarm and there is a Control Deviation Alarm between the
two points not in Quality Alarm.
OR
3. When all three transmitters are in Control Deviation with each other.
The Manual Reject digital output is either a one-shot signal or a maintained output, depending on
the MRE output type that is initialized in the Control Indicator Word (CNTL).
The Packed output signal (PBPT) contains the Manual Reject output, the Transmitter Malfunction
Alarm, the Quality Alarms, the Control Deviation Alarms, and the Alarm Deviation Alarms for all
three transmitters.
The HOLD parameter holds the output value and quality for a desired number of loops when a
manual reject occurs.
350 OW351_R1100
5.68 MEDIANSEL
The Interface keys on the Operators Keyboard are:
FU N C TI O N KE Y US E
P1 Median Mode Requested

P2 Transmitter A Mode requested
P3 Transmitter B Mode requested
P4 Transmitter C Mode requested
P5 Toggle the inhibiting of the control deviation alarm check on the manual reject
(MRE) output
Note: If the transmitter selected goes to BAD quality, then the algorithm changes mode to
median.
The transmitter's input values to the algorithms are checked for invalid real numbers. If an input
value contains an invalid real number, it is not used in generating the output of the algorithm.
However, the Transmitter Quality Alarm digital output for the point is set to TRUE if the input value
is invalid.
If the algorithm calculates an invalid real number for the output, the quality of the output is set to
BAD and the output value is invalid.
INSEL parameter
The INSEL parameter determines which inputs of the MEDIANSEL algorithm are being used to
calculate the output. The Signal Diagram application displays green circles around the active pins.
If none of the pins are selected, then nothing will display. You can also view this information via
the Process Diagram System graphics as well. Refer to Ovation Operator Station User Guide for
more information on the Signal Diagrams application and the Process Diagram System graphics.
The MEDIANSEL algorithm activates individual bits in the Y0 field depending on the conditions in
the description field. If a signal is active, that signal is being used in the output calculation.
OW351_R1100 351
5.68 MEDIANSEL
FI E L D RE C .

Number.
CNTL X1-Byte Data Init. Optional 0 Control Indicator Word: -
Bit 0 = MRE Output

Type
(0 = One-shot signal
1 = Maintained signal)
Bit 1 = High/Low
Output
(0 = Selected high
GOOD quality output
1 = Select low GOOD
quality output)
Bit 2 = Quality Alarm
Type
(0 = BAD Quality Alarm
1 = Not GOOD Quality
Alarm)
ALDB R1-Real Tuning Required 0.0 Alarm Deviation -
Constant Deadband.
CNDB R2-Real Tuning Required 0.0 Control Deviation -

Constant Deadband.
HMTR R3-Real Tuning Required 0.0 High Alarm monitor -
Constant value.
LMTR R4-Real Tuning Required 0.0 Low Alarm monitor -
Constant value.
HOLD X7-Byte Data Init Required 0 Hold output during -
manual reject (number
based on loop time).
XA - Variable Required - Input (analog); LA

Transmitter A.
XB - Variable Required - Input (analog); LA
Transmitter B.
XC - Variable Required - Input (analog); LA
Transmitter C.
median value.
HI - Variable Optional - Output (analog); High LA

Alarm monitoring value.
LO - Variable Optional - Output (analog); Low LA
Alarm monitoring value.
352 OW351_R1100
5.68 MEDIANSEL
FI E L D RE C .
XBQ - Variable Optional - Output (digital); all LD, LP

transmitters in Quality
Alarm.
XABQ - Variable Optional - Output (digital); Quality LD, LP
Alarm for Transmitter
A.
XBBQ - Variable Optional - Output (digital); Quality LD, LP
B.
XCBQ - Variable Optional - Output (digital); Quality LD, LP
C.
ABDC - Variable Optional - Output (digital); Control LD, LP
Deviation Alarm
between Transmitters
A and B.
ABDA - Variable Optional - Output (digital); Alarm LD, LP
Deviation Alarm
A and B.
ACDC - Variable Optional - Output (digital); Control LD, LP
Deviation Alarm
between Transmitter A
and C.
ACDA - Variable Optional - Output (digital); Alarm LD, LP
Deviation Alarm
A and C.
BCDC - Variable Optional - Output (digital); Control LD, LP
Deviation Alarm
Transmitters B and C
BCDA - Variable Optional - Output (digital); Alarm LD, LP
Deviation Alarm
B and C.
XALM - Variable Optional - Output (digital); LD, LP
Transmitter Malfunction
Alarm.
MRE - Variable Optional - Output (digital); manual LD, LP
reject.
OW351_R1100 353
5.68 MEDIANSEL
FI E L D RE C .
PBPT - Variable Optional - Output (packed digital) LP

(bit and description
shown):
0 = Manual reject
1 = Transmitter
malfunction
2 = All transmitters in
Quality Alarm
3 = Quality Alarm for
Transmitter A
Transmitter B
Transmitter C
6 = Alarm deviation
A and B
7 = Alarm deviation
A and C
8 = Alarm deviation
B and C
9 = Control deviation
A and B
A and C
B and C
12 = Inhibit Control
Deviation Check for
MRE Output
13 = Transmitter A
mode
14 = Transmitter B
mode
15 = Transmitter C
mode
354 OW351_R1100
5.68 MEDIANSEL
FI E L D RE C .
INSEL* Y0 Alg. Init Required 0 Input Selected: --
Bit 1 - Signal A
 0 = Not Active
 1 = Active
Bit 2 - Signal B
 0 = Not Active
 1 = Active
Bit 3 - Signal C
 0 = Not active
 1 = Active
* If no inputs are selected, it indicates one of the following:
 the inputs are all BAD quality.
 the output is scan removed.
 Manual Reject is activated with HOLD.
 the calculated output is invalid.
OW351_R1100 355
5.69 MULTIPLY
5.69 MULTIPLY
Description
The MULTIPLY algorithm multiplies two gained and biased inputs. The output of the MULTIPLY
algorithm is the product of the two individually gained and biased inputs.
Functional Symbol
Tracking Signals
in the analog input signal TRIN:
Bit description
356 OW351_R1100
5.69 MULTIPLY
value of the conditional track bit is transferred to all output track points. If the Conditi onal Track bit
is set in the track input point, the analog value of all output track points is calculated based on the
analog value of the track input point.
set to BAD. Otherwise, the quality of OUT is set to the worst quality of the two inputs when not in
output and IN1input values are invalid.
FI E L D RE C O R D

Number
IN1G R1-Real Tuning Required 1.0 Gain on input 1. The -
Constant gain on input 1
should never be
initialized to zero; if
it is, the drop is
placed into alarm.
Constant
IN2G R3-Real Tuning Required 1.0 Gain on input 2 -

Constant

Constant

OW351_R1100 357
5.69 MULTIPLY
FI E L D RE C O R D



local memory
operations. The
choices are:
 ON
 OFF

mode and status
signals for input 1
variable

variable
TRIN - Variable Optional - Tracking and limiting LA
mode signals and
tracking value;
analog input variable
Function
IN1GB= (IN1 x IN1G) + IN1B

OUT = IN2GB x IN1GB
IF OUT >= TPSC THEN
OUT = TPSC
ELSE
IF OUT <= BTSC THEN
OUT = BTSC
358 OW351_R1100
5.70 NLOG
5.70 NLOG
Description
The NLOG algorithm performs the mathematical natural logarithmic function. For the NLOG
algorithm, the output equals the natural logarithm of the input value plus a bias. If the input value
is less than or equal to zero, the output is set to a large negative number (-3.4 x 1038).
Note: Other logarithmic algorithms are ANTILOG (see page 69) and LOG. (see page 316)
The quality of the input is propagated to the output. However, if the algorithm calculates an invalid
value for the output, the quality of the output is set to BAD, and the output value is invalid.
Functional Symbol
FI E L D RE C O R D

Number
BIAS R1-Real Tuning Optional 0.0 Bias -
Constant
Function
OUT = NATURAL LOG OF IN1 + BIAS
OW351_R1100 359
5.71 NOT
5.71 NOT
Description
The NOT algorithm is a logical NOT gate. For the NOT algorithm, the output is the logical NOT of
the input.
Functional Symbol
FI E L D RE C O R D
OUT - Variable Required/ - Output (digital) LD, LP

Optional
Note: Output is required if connecting to anything other than OR or AND.
Function
IF IN1 = TRUE
THEN OUT = FALSE
ELSE
OUT = TRUE
360 OW351_R1100
5.72 OFFDELAY
5.72 OFFDELAY
Description
The OFFDELAY algorithm extends the time that the output is TRUE. On a FALSE -to-TRUE state
level change of the IN1 (Pulse Stretcher), the Timer ACTUAL (ACT) is set to zero and the OUT
output is TRUE.
On a subsequent TRUE-to-FALSE state level change of the IN1, the ACTUAL (ACT) begins
accumulating time. When ACTUAL (ACT) is equal to the TARGET (TARG), accumulation stops,
the OUT output is set to FALSE, and ACTUAL (ACT) retains data until it is reset by another
FALSE-to-TRUE state level change of the IN1 input.
If the TARGET (TARG) value specifies a time which is less than or equal to the sheet scan time, it
is permissible for the OUT output to be set FALSE on the same scan that the IN1 input changed
from TRUE to FALSE.
The timers are re-triggerable (that is, the ACTUAL (ACT) can be reset before it reaches the
TARGET (TARG) value).
The OUT output is de-energized if (ACT >= TARG).
If the TARGET (TARG) or ACTUAL (ACT) operands contain a negative or invalid number, OUT is
set to FALSE but no other operation takes place.
When a Controller resets, if IN1 is FALSE, ACTUAL (ACT) remains unchanged and t he OUT
output is TRUE according to the comparison between the ACTUAL (ACT) and the TARGET
(TARG). However, if the ACTUAL (ACT) has an initial value, then the ACTUAL'S (ACT's) initial
value is compared to TARG. If IN1 is TRUE, ACTUAL (ACT) is set to zero and OUT is TRUE.
In redundant Controllers, during Fail over, if IN1 is FALSE, ACTUAL (ACT) remains unchanged
and both outputs are TRUE according to the comparison between the ACTUAL (ACT) and
TARGET (TARG). If IN1 is TRUE, ACT is set to zero and OUT is TRUE.
An optional time base (minimum of 0.1 second) can be entered in the R1 field of the algorithm
record. The default time base is 1 second.
Functional Symbol
OW351_R1100 361
5.72 OFFDELAY
FI E L D RE C O R D

number
BASE R1-Real Tuning Required 1.0 Time Base in -
Constant seconds
(minimum 0.1
second, default
1.0 seconds)
* TARG R2-Real Selectable Required 0.0 Delay Time LA

number
(analog)
* ACT R3-Real Selectable Required 0.0 Output (analog) LA

Function (Timing Diagram)
(IN1)
TARGET TARGET
362 OW351_R1100
5.73 ONDELAY
5.73 ONDELAY
Description
The ONDELAY algorithm delays the time that the output is set to TRUE. When the ONDELAY
algorithm is enabled with the IN1 input TRUE, the Timer ACTUAL (ACT) accumulates time per
the specified Time BASE (BASE) until it equals the Timer TARGET (TARG). At this point, it stops
accumulating and remains at the TARGET (TARG) value and OUT goes to TRUE.
If the IN1 input changes from TRUE to FALSE while the Timer is enabled (ENBL), the ACTUAL
(ACT) retains the current value. When the IN1 input changes back to the TRUE state, the
ACTUAL (ACT) resumes accumulating time.
You can reset ACTUAL (ACT) to zero at any time by making the ENBL input FALSE. This causes
OUT to go FALSE. Typically; however, the IN1 and ENBL inputs are tied together so that
ONDELAY acts as a “classical” timer.
Note: If ENBL is not connected, the algorithm work s as a “classical” timer. The same
functionality can be achieved when the IN1 and ENBL inputs are tied together.
If the ACTUAL (ACT) value is equal to or greater than the TARGET (TARG) value, transitions of
the IN1 input have no effect.
Of special consideration is the case when the Timer TARGET (TARG) equals zero. In this
instance, the OUT output follows the IN1 input as long as the Timer is enabled.
If the TARGET (TARG) specifies a time which is less than or equal to the sheet scan time, it is
permissible for the OUT output to be TRUE on the first scan that the IN1 and ENBL i nputs are
TRUE.
set to FALSE but no other operation takes place.
When a Controller resets, if ENBL is TRUE, ACTUAL (ACT) remains unchanged and the OUT
output is energized according to the comparison between ACTUAL (ACT) and TARGET (TARG).
However, if ACTUAL (ACT) has an initial value, then ACT's initial value is compared to TARGET
(TARG). If ENBL is FALSE, ACTUAL (ACT) is set to zero and OUT is FALSE.
In redundant Controllers, during Failover, if ENBL is energized, ACTUAL (ACT) remains

unchanged and both outputs are energized according to the comparison between ACTUAL (ACT)
and TARGET (TARG). If ENBL is FALSE, ACTUAL (ACT) is set to zero and OUT is FALSE.
record. The default time base is 1 second.
OW351_R1100 363
5.73 ONDELAY
Functional Symbol
FI E L D RE C O R D

number
BASE R1-Real Tuning Required 1.0 Time Base -
Constant seconds
(minimum 0.1
second, default
1.0 seconds)
ENBL - Variable Optional - Input (digital) LD, LP
* TARG R2-Real Selectable Required 0.0 Delay Time LA

number (analog)
* ACT R3-Real Selectable Required 0.0 Output (analog) LA
364 OW351_R1100
5.73 ONDELAY
Function (Tuning Diagram)
(IN1)
TARGET TARGET TARGET
OW351_R1100 365
5.74 ONESHOT
5.74 ONESHOT
Description
The ONESHOT algorithm sets the output TRUE on a transition for a specified period of time. On a
FALSE-to-TRUE transition of the IN1 input, the OUT output energizes. The ACTUAL (ACT) is
reset to zero and immediately begins accumulating time, and continues to accumulate until it
equals the TARGET (TARG) or until another FALSE-to-TRUE transition of the IN1 input has
occurred.
When ACTUAL (ACT) equals TARGET (TARG), the OUT output de-energizes and the ACTUAL
(ACT) retains its value until a FALSE-to-TRUE transition of the IN1 input has occurred.
The function is retriggerable (that is, if the ACTUAL (ACT) is accumulating time and the IN1 input
makes a FALSE-to-TRUE transition before it reaches the TARGET (TARG) value, the function is
reset and begins accumulating from time zero).
If the ACTUAL (ACT) is greater than the TARGET (TARG), it is inhibited from acc umulating time
and the OUT output is de-energized.
If TARGET (TARG) equals zero, the OUT output never energizes.
de-energized but no other operation takes place.
When a Controller resets, regardless of the IN1 state, ACTUAL (ACT) continues to accumulate
and OUT output is energized according to the comparison between ACTUAL (ACT) and TARGET
(TARG). However, if ACTUAL (ACT) has an initial value, then ACTUAL's (ACT) init ial value is
compared to TARGET (TARG).
In redundant Controllers, during Failover, regardless of the IN1 state, ACTUAL (ACT) continues to
accumulate and the OUT output is energized according to the comparison between ACTUAL
(ACT) and TARGET (TARG).
When a control sheet is modified and then loaded, the algorithm behavior depends on the
algorithm state and the changes made on the sheet.
 If the ONESHOT is in a triggered state (IN1 = TRUE) and any changes were made to any of
the ONESHOT’s parameters, the OUT resets to zero and the ACTUAL (ACT) is also reset to
zero upon a sheet load.
 In other cases, when the ONESHOT is not in a triggered state or no changes are made to any
of the ONESHOT’s parameters, the OUT keeps the current value and ACTUAL (ACT)
continues to count (if the target value has not been reached).
If a tuning change is made to the TARGET (TARG) from the signal diagram, it is ignored if the
ONESHOT is in its triggered state (IN1 = TRUE). For example, if the TARGET (TARG) is 10 and
the ONESHOT is triggered, changing the target to 20 will not change the time when the OUT
transitions to zero (it will still be a 10 second pulse).
If a tuning change is made (via the signal diagram) to the BASE, the ONESHOT will recalculate
its ACTUAL (ACT) time and if the recalculated time has not reached its TARGET (TARG), the
OUT will remain at a one state until the target is reached. For example, assume the ONESHOT
with a BASE of 1 and a TARGET of 20 is triggered. At count 10, the base is then changed to 2.
The ACTUAL (ACT) will immediately change to 5 and the OUT will stay at a one state until the
count reaches 20 which will actually be 40 seconds from the time it was triggered.
366 OW351_R1100
5.74 ONESHOT
In the Ovation Developer Studio, the TARGET is actually labeled "Pulse Time Number."
If the TARGET input is connected to another algorithm output, the ONESHOT behaves differently
than the manner described above. Tuning changes (via the signal diagram) will not be ignored but
will function as follows: Assume a TARGET of 30 and the ONESHOT is triggered. The ACTUAL
(ACT) time will increment normally. If the TARGET input is changed to a greater value before the
30 seconds has timed out, the pulse will obey the new value. Therefore, if the value was changed
to 60, the pulse length will now be 60 seconds instead of 30 (but only if the TARGET input value
changed before the original 30 seconds had timed out).
Conversely, if the TARGET input time is shortened before the original target is reached, the
ONESHOT will obey the new TARGET. Assume an initial TARGET of 30 and the ONESHOT is
triggered. A change is made to the TARGET input to 20 so now the pulse length will be
shortened to 20. If the ACTUAL (ACT) value is greater than 20 when the change is made, the
OUT will immediately transition to zero. Tying the TARGET to an AVALGEN algorithm offers
additional flexibility especially in cases where it is not known exactly how long the ONESHOT
should be and online tuning changes are desired.
Connecting the TARGET to other algorithms can be done to create additional functions such as a
variable ONESHOT pulse output.
record. If a value is not entered or a zero is entered into BASE (R1), the default time base is
assumed to be 1 second.
Functional Symbol
OW351_R1100 367
5.74 ONESHOT
FI E L D RE C O R D

number
BASE R1-Real Tuning Optional 1.0 Time Base in -
Constant seconds (minimum
0.1 second, default
1.0 seconds);
(0 implies 1.0
second)
IN1 - Variable Required - Input (digital signal) LD, LP
* TARG R2-Real Selectable Required 1.0 Pulse Time number LA

(analog signal)
* ACT R3-Real Selectable Required 0.0 Output (analog LA

signal)
OUT - Variable Required - Output (digital LD, LP
signal)
Function (Timing Diagram)
(IN1)
TARGET TARGET TARGET
368 OW351_R1100
5.75 OR
5.75 OR
Description
The OR (Logical OR gate up to 8 inputs) algorithm changes the Boolean of the output based on
the input. The output equals the logical OR of two to eight inputs (that is, at least one input must
be TRUE for the output to be TRUE).
Functional Symbol
N AME LC A L G . T YP E RE Q U I R E D / DE F AU L T D E S C R I P TI O N MI N .
FI E L D RE C O R D

OUT - Variable Required/ - Output (digital) LD, LP
Optional
Function
OUT = IN1 OR IN2 OR IN3 OR IN4 OR IN5 OR IN6 OR IN7 OR IN8
OW351_R1100 369
5.76 PACK16
5.76 PACK16
Description
The PACK16 algorithm specifies up to 16 optional digital values as inputs, which are placed into
their corresponding positions in the A2 record field of an LP or larger point record. Inputs may be
of any size (that is, LD, or DD). Variable PBPT functions as an output LP point record, which is
broadcast on the Data Highway for use by other drops. PBPT also functions as an input, when
desired, to pack the LP record from multiple algorithms. These other algorithms can be additional
PACK16 algorithms or other types. For example, you could pack Bits 0 through 10 from Algorithm
X, Bits 11 through 15 from algorithm Y. Bit locations can be left unpacked as spares, if desired.
Note: If digital inputs have bad quality, then the pack ed point (PBPT) bit remains unchanged.
Functional Symbol
FI E L D RE C O R D
D0 - Variable Optional - Input (digital) for LD

Bit 0
Bit 1
Bit 2
Bit 3
370 OW351_R1100
5.76 PACK16
FI E L D RE C O R D

Bit 4
Bit 5
Bit 6
Bit 7
Bit 8
Bit 9
D10 - Variable Optional - Input.(digital) for LD
Bit 10
Bit 11
Bit 12
Bit 13
Bit 14
Bit 15
PBPT - Variable Required - Output (packed LP
(POUT) point)
OW351_R1100 371
5.77 PID
5.77 PID
Description
The PID algorithm provides a proportional, integral, derivative controller function. The algorithm is
a parallel PID implementation that utilizes integral tracking signals for bumpless transfer. The
output value is limited via user-defined limits and anti-reset windup is handled internally.
Functional Symbol
Guidelines
Note: PV = Process Variable

STPT = Set Point
1. PV GAIN and PV BIAS must be used to normalize the process variable inputs to a 0 to 100
percent value.
(PV x PV GAIN) + PV BIAS = PV percent. Thus:
2. STPT GAIN and STPT BIAS must be used to normalize the set point to a 0 to 100 percent
value. If setpoint input units are not 0 to 100 percent, then:
(STPT x STPT GAIN) + STPT BIAS = set point percent. Thus:
3. Determine set point high and low limits with these equations:
set point high limit = (100 - STPT BIAS)/STPT GAIN
set point low limit = (0 - STPT BIAS)/STPT GAIN
372 OW351_R1100
5.77 PID
Auto-scaling options
The Auto-scaling option consists of a configuration parameter (AUSC) and Engineering Units
limits parameters (high and low limits) for PV and STPT inputs of the PID algorithm.
Possible settings for the AUSC parameter are:
 NONE
 PV_ONLY
 SP_ONLY
 BOTH
If the setting NONE is used:
Auto-scaling is disabled. The PID uses the gain and bias values that are configured by the user
for each input (R1, R2 for PV and R3, R4 for SP).
If the setting PV_ONLY is used:
Auto-scaling is enabled for the process variable only. The STPT input (setpoint) uses the gain and
bias values configured by the user. For the PV gain and bias values, the top and bottom
engineering units range are read depending on the Auto-Scaling parameter option. The
appropriate gain and bias values are calculated so that the PV auto-scale high and low limits are
scaled to 0%-100%, according to the formulas:
The calculated gain and bias values are then written to the R1 and R2 LC record fields by the
algorithm. These changes will be reconcilable from the database in the same manner as if it were
tuned.
If the setting SP_ONLY is used:
Auto-scaling is enabled for the Set Point only. The PV (Process Variable) input uses the gain and
bias values configured by the user. For the SP gain and bias values, the top and bottom
engineering units range are read depending on the Auto-Scaling parameter option. The
appropriate gain and bias values are calculated so that the SP auto-scale high and low limits are
scaled to 0%-100%, according to the formulas:
The calculated gain and bias values are then written to the R3 and R4 LC record fields by the
algorithm. These changes will be reconcilable from the database in the same manner as if it were
tuned.
OW351_R1100 373
5.77 PID
If the setting BOTH is used:
Auto-scaling is enabled for both the PV and SP. The PV auto-ranging is handled as outlined in
PV_ONLY and the SP auto-scaling is handled as outlined in SP_ONLY.
Auto-scaling parameter options
The Auto-scaling parameter option consists of the configuration parameter (AUSCP). This
parameter allows the user to configure what scaling parameters to use.
Possible settings for the AUSCP parameter are:

 INT – INTERNAL. If auto-scaling is enabled, use internal user-defined scaling (V1 – V4).
 EXT – EXTERNAL. If auto-scaling is enabled, use PV input TW (top scale) and BW (bottom
scale) to calculate gain and bias. This is dependent on the AUSC option.
Error conditions: Auto-scale range values are invalid
This case applies to any configuration of auto-scaling. The auto-scaling range values are
considered invalid if any one of the following occurs:
 Bottom and Top Scale values are equal.

 Bottom Scale value > Top Scale value.
In the case where the range values are invalid for a particular input, the output will not change
and will be marked as BAD quality. Also, the PID will post an Invalid Calculated Number message
in the Error Log and will place the drop in alarm.
Output Calculation
The output (which is in either engineering units or percent and limited by the high and low limits
specified) equals the result of the PID equation except:
is present. The output ramps at the user-specified track rate, from the track input back to the
controlled value when the tracking signal is removed.
 When a raise inhibit or lower inhibit signal is present, it may prevent the PID controller from
controlling.
 If the algorithm calculates an invalid real number for the output, the quality of the output is set
to BAD. Consequently, if an invalid value is entered as an input to the algorithm, or if the
algorithm generates an invalid value for the output, the drop is placed into alarm. In all cases,
the output is set to the last GOOD value.
 If the algorithm generates an invalid track output value, the set point input value is used as
the track output, unless it is invalid. The track output value is not updated if both the
calculated track output and the set point input values are invalid.
Error Deadband and Deadband Gain
The algorithm can be configured to utilize a Deadband region in the Controller error signal. This
Deadband region is used to modify the error signal that is presented to the PID equation.
The Controller error signal is calculated as the difference between the normalized proc ess
variable and normalized set point and is passed as the input to the PID equation. If the algorithm
is configured to utilize an error Deadband and the error is within the deadband limits, the error
that is presented to the PID equation is Error = Error X Error Deadband Gain.
374 OW351_R1100
5.77 PID
When the algorithm is configured to use deadband, transitions into and out of the deadband
region are smoothed internally by utilizing a hold and track operation. During this transition cycle,
the Controller output is set to its previous value and the integral term is re-calculated to account
for the apparent proportional gain change in the new region. This effectively eliminates the abrupt
change in the proportional term due to the deadband transition. Derivative action is disabled when
the algorithm is operating within the deadband region.
If no deadband action is desired, the inner deadband limit (DBND) should be set to zero.
Single Deadband
The Single Deadband mode is configured by initializing the inner deadband limit (DBND field) to a
non-zero value and setting the deadbands option (DOPT) parameter to SINGLE. This value
represents the normalized Controller error signal to be used as the Deadband region limits.
Deadband is symmetrical with respect to zero. For example, if the DBND field equals 5, then the
deadband region is between -5% and +5%. If the Controller error signal is within the deadband,
then the actual error that is presented to the PID equation is the product of the error signal and
the error deadband gain. The ERRD field contains the value of the error deadband gain. The valid
values for this field are any real numbers between zero and one [0 - 1].
As an example, consider the following: DBND is 5 and ERRD is 0.5. For a normalized Controller
error signal of 2%, the actual error signal that is applied to the PID equation is 2% x 0.5 = 1%. In
general, for these example values of DBND and ERRD, any normalized error signal between -5%
and +5% is reduced by 50% before being applied to the PID equation. Derivative action is
disabled when the algorithm is operating within the deadband region.
Double Deadband
The Double Deadband configuration utilizes two deadband limits. These are the inner (DBND)
and the outer deadband limit (ODBND). Once the absolute value of the error signal is less than or
equal to the inner deadband, then the deadband gain is applied. The deadband gain is applied
until the absolute value of the error signal is greater than the outer deadband.
The Double Deadband mode is configured by initializing the Outer Deadband (ODBND) field to a
value greater than the inner deadband limit (DBND) and setting the deadbands option (DOPT)
parameter to DOUBLE. The Double Deadband mode is designed to be used when a noisy
process variable is present. When noise is present in the Process Variable signal, it causes
fluctuations in the magnitude of the error signal. When a Single Deadband is used, the Controller
error signal can fluctuate in and out of the deadband region (DBND) on successive execution
loops. In severe cases, this can lead to reduced performance of the PID algorithm. An example of
this situation is shown graphically in the following figure.
In this figure, at time t1, the signal has entered the inner deadband region. At time t2, the noise
has caused the signal to exit the inner deadband region, and at t3, it enters it again. The same
problem is seen again as the signal leaves the inner deadband region, as seen at t4, t5 and t6.
At each transition into and out of the deadband, the algorithm performs a track and hold
operation. This prevents the output from spiking due to the abrupt change in the proportional
term.
In Singe Deadband mode, subsequent transitions into and out of the deadband region can lead to
reduced performance of the PID algorithm.
OW351_R1100 375
5.77 PID
The following graph depicts the inner deadband limits.
To prevent this situation, a second outer deadband region (ODBND) can be defined by the user.
This should be larger than the inner deadband region (DBND) as shown in the following figure.
More specifically, the outer deadband (ODBND) should be defined as equal to, or larger than, the
noise seen in the signal PLUS the inner deadband region (DBND).
376 OW351_R1100
5.77 PID
For example, if the DBND field is equal to 5, then that deadband region is between -5% and +5%.
Once the Controller error signal reaches this inner deadband region of + or -5%, a noise in the
signal with a peak of + or -3% could push the Controller error signal back out of the inner
deadband region up to + or -8% on the next scan. Therefore, the outer deadband (ODBND)
should be set larger than + or -8% to compensate for noise. In the following figure, we set the
ODBND to +/- 10. If the outer deadband (ODBND) region is less than the defined inner deadband
(DBND) region, then the outer deadband region is set equal to the inner deadband value.
OW351_R1100 377
5.77 PID
Hard Inhibit Parameter
If the Hard Inhibit parameter (INHB) of PID is set to ENABLED, and PID receives an inhibit signal
from downstream, PID stops updating the PID output and holds the last calculated value prior to
the receipt of the inhibit signal. As long as the inhibit condition remains, normal control action will
resume only after the PID error changes sign.
If the Hard Inhibit parameter (INHB) is set to DISABLED, and PID receives the inhibit signal from
downstream, PID continues calculating a new output value each loop time. PID compares the
new value to the previous output value and if updating the output point with the new value would
violate the inhibit condition, then the previous output value is maintained. If the new value would
not violate the inhibit condition, then the output point is updated with the new output value.
Example
If INHB is set to ENABLED when PID receives a lower inhibit signal (LWI) via track input from a
downstream algorithm, PID output cannot decrease. The output value remains constant until
either the LWI signal is removed, or the process error changes to where PID output increases and
resumes normal control action.
If INHB is set to DISABLED when PID receives a lower inhibit signal (LWI) via track input from a
downstream algorithm, PID continues to calculate a PID output each loop time. The calculated
value is stored in the algorithm and compared to the output calculated during the previous loop
time. If a lower inhibit occurs, the actual PID output will be the greater of the two calculated
values. If a raise inhibit occurs, the actual PID output will be the lesser of the two calculated
values.
Note: In either case, PID uses internal mechanisms to ensure that an integral windup condition
does not occur during an inhibited situation.
Tracking Signals
External tracking and limiting are done through signals passed in the upper 16 bits of the third
status word of the analog track points. This algorithm takes the following action in response to
information found in the third status word of the analog input signal TRIN:
Bit description
16 Track Implemented Passed through or set

TRUE when not in
Cascade mode.
17 Track if lower Implemented Not used
18 Track if higher Implemented Not used

19 Lower inhibit Implemented* Passed through**
20 Raise inhibit Implemented* Passed through**
21 Conditional Track See description of Passed through if in the
cascaded mode. cascaded mode.
378 OW351_R1100
5.77 PID

The High and Low limit flags, the mode, and the tracking signals from the algorithm are output to
TOUT to be used for display and by upstream algorithms.
FI E L D RE C O R D

Number
SPTG R3-Real Tuning Required 1.0 Gain on set point. -
Constant The gain on the s et
point should never
be initialized to
zero.
SPTB R4-Real Tuning Optional 0.0 Bias on set point -
Constant
PVG R1-Real Tuning Required 1.0 Gain on process -

Constant variable input. The
gain on the set
point should never
be initialized to
zero.
PVB R2-Real Tuning Optional 0.0 Bias on process -
Constant variable input

OW351_R1100 379
5.77 PID
FI E L D RE C O R D
PVTS V1-Real Tuning Required 100.0 Top scale for PV -

Constant input point -- used
only when AUSC is
set to PV_ONLY or
BOTH.
PVBS V2-Real Tuning Required 0.0 Bottom scale for PV -
only when AUSC is
set to PV_ONLY or
BOTH.
SPTS V3-Real Tuning Required 100.0 Top scale for STPT -
only when AUSC is
set to SP_ONLY or
BOTH.
SPBS V4-Real Tuning Required 0.0 Bottom scale for -
Constant STPT input point --
used only when
AUSC is set to
SP_ONLY or
BOTH.
380 OW351_R1100
5.77 PID
FI E L D RE C O R D
AUSC X7-Byte Data Init. Required NONE Auto-scaling option: -

Bits 0 and 1
NONE - No auto-
scaling enabled.
GAINs and BIASes
defined in R1-R4
fields will be used.
PV_ONLY - Only
GAIN and BIAS for
PV (R1 and RS) are
automatically
calculated, using
TOP (V1) and
BOTTOM (V2)
scale parameters
for PV.
SP_ONLY - GAIN
and BIAS for SP
only (R3 and R4)
are automatically
calculated, using
TOP (V1) and
BOTTOM (V2)
scale parameters
for PV.
BOTH - GAIN and
BIAS for both PV
and SP inputs are
automatically
recalculated, using
appropriate TOP
and BOTTOM scale
parameters for PV
(V1 and V2) and for
SP (V3 and V4).
AUSCP X8-Byte Data Init. Required INT Auto-scaling -
Bit 0 parameters option:
INT - If auto-scaling
is enabled, use
user-defined
internal scaling (V1
- V4)
EXT - If auto-
scaling is enabled,
use PV input TW
(top scale) and BW
(bottom scale) to
calculate gain and
bias.
OW351_R1100 381
5.77 PID
FI E L D RE C O R D
TYPE X5-Byte Data Init. Required NORMAL Type of PID -

Bits 1 and 0 controller:
NORMAL =
Regular PID control
ESG = PID control
with error squared
on the proportional
gain term
ESI = PID control
with error squared
on the integral term
ACTN X5-Byte Data Init. Required INDIRECT Direction Flag: -
Bit 2 INDIRECT = Error
= Set point -
process variable
DIRECT: Error =
Process variable -
set point
INHB X6-Byte Data Init. Required ENABLED Defines algorithm -
behavior when a
Bit 0 raise or lower inhibit
signal is received
from a downstream
algorithm.
ENABLED =
Normal PID action.
Output is not
updated and last
value is held until
PID error changes
sign.
DISABLED = See
description of Hard
Inhibit Parameter.
CASC X5-Byte Data Init Required NORMAL Controller is -
Bit 3 downstream in a
cascaded
configuration.
NORMAL = Normal
PID action.
CASCADED = See
description of
Cascaded Mode
and Conditional
Tracking.
382 OW351_R1100
5.77 PID
FI E L D RE C O R D
PACT X6-Byte Selectable Required NORMAL Type of -

Proportional action:
Bit 1
 NORMAL = Error
 PROCESS =
Process variable
DACT X5-Byte Data Init Required NORMAL Type of Derivative -
Bit 4 action:
NORMAL =
Derivative applied
to change in error.
SET POINT =
Derivative applied
to change in set
point.
PROCESS =
Derivative applied
to change in
process variable.
IACT X6-Byte Selectable Required NORMAL Type of Integral -
Bit 2 action:
 NORMAL = Reset
time cannot be
less than task
loop time.
 ALLOW < LOOP
TIME = Reset
time can be less
than task loop
time.
DBND S3-Real Tuning Required 0.0 PID error -
Constant deadband*
DOPT X5-Byte Bit Data Init. Required SINGLE SINGLE - Single -

6 and 7 deadband mode
DOUBLE - Double
deadband mode
ODBND S7-Real Tuning Required 0.0 PID outer error LA
Constant deadband**
ERRD S4-Real Tuning Required 0.0 PID error deadband -
Constant gain
*** PGAIN R8-Real Selectable Required 1.0 PID proportional LA
gain. If the
proportional gain
equals zero, the
proportional part is
not included in the
output.
OW351_R1100 383
5.77 PID
FI E L D RE C O R D
*** INTG R9-Real Selectable Required 10.0 PID integral time in LA

seconds per repeat.
If the integral time
equals zero, the
integral part is not
included in the
output.
*** DGAIN S1-Real Selectable Required 0.0 PID derivative gain. LA
If the derivative
gain equals zero,
the derivative part
is not included in
the output.
*** DRAT S2-Real Selectable Required 0.0 PID derivative rate LA
decay constant in
seconds:
 When the DRAT
parameter is set
to equal to half of
the task loop
time, then the
time derivative is
0.
 When the DRAT
parameter is less
than half of the
task loop time,
then it is set to
half of the task
loop time
internally and the
derivative term is
0.
PV - Variable Required - Process variable LA
analog input.
STPT - Variable Required - Set point analog LA
input
384 OW351_R1100
5.77 PID
FI E L D RE C O R D
TOUT - Variable Required - Track output value. LA

variable
input variable
DVAL - Variable Optional - Derivative term LA

output
DEVA - Variable Optional - Error between LA
process variable
and set point for
PID. This is
calculated using the
normalized set
point PVAR.
* A value of 0.0 for this field disables all deadband action.
** Anytime that the value of this field is greater than the inner deadband (DBND), the double deadband
action results. This value should be set to zero if single deadband action is desired.
*** When a parameter type is defined as "Selectable" and marked as "Required," the Control Builder may
For selectable parameters, the record field associated with the param eter will reflect the value of what is
currently selected.
OW351_R1100 385
5.77 PID
386 OW351_R1100
5.77 PID
Cascaded Mode and Conditional Tracking:
Conditional tracking is a scheme which allows tighter control of the process variable when the
control strategy is implemented using cascaded Controllers. Essentially, the conditional tracking
scheme allows the upstream Controller to have immediate influence on the final output when the
error between the process variable and the set point changes direction while the downstream
Controller is in a saturation condition. Conditional tracking is incorporated when the downstream
Controller (Controller “B” in figure) operates in cascaded mode.
The purpose of cascaded mode is to allow two PID algorithms to be used in a cascaded
configuration where the output of one PID is the set point for another. When you desire to arrange
two PID Controllers in this configuration, the type parameter should be set to c ascaded in the
downstream Controller only. It is not necessary to configure the upstream Controller in the
cascaded configuration.
When the downstream Controller is configured in the cascaded mode, the Controller operates as
a conventional PID controller so long as the Controller is not in a saturation condition. However, if
the Controller output is saturated at the HI or LO limit or if the Controller receives an inhibit signal
from a downstream algorithm the behavior of the cascaded pair is as follows:
The downstream Controller (Controller “B” in figure) asserts the conditional track signal in its
output tracking point along the applicable limit or inhibit bit. The downstream Controller also
calculates a track output value that if applied as a set point input, yields a Controller error of zero
(see Equation 1 in the previous figure).
When the upstream Controller sees the conditional track bit set, it adjusts its output as follows: If
the error signal causes the Controller output to move against the inhibit s ignal (for example,
output attempts to increase when the algorithm is receiving a raise inhibit), then the algorithm sets
its output equal to the track input received from downstream.
If the error signal causes the output to move away from the inhibit signal, the algorithm sets its
output equal to the track input and begin controlling.
Without this mode, the upstream Controller would first have to move enough to zero the error on
the downstream Controller before having any effect on the process. This would introduce
additional dead-time in the Controller response and in the case of processes with slow dynamics
(for example, temperature control), this additional dead-time may be significant.
Only the PID algorithm configured to be in cascaded mode asserts the conditional track bit. The
upstream Controller (Controller “A” in the previous figure) does not pass the conditional track bit in
its track output.
OW351_R1100 387
5.77 PID
Hard Inhibit Parameter
If the Hard Inhibit parameter (INHB) of the PID algorithm is set to ENABLED, and PID receives an
inhibit signal from downstream, the PID algorithm stops updating the PID output and holds the
last calculated value prior to the receipt of the inhibit signal. As long as the inhibit condition
remains, normal control action will resume only after the PID error changes sign.
If the Hard Inhibit parameter (INHB) is set to DISABLED, and the PID algorithm receives the
inhibit signal from downstream, PID continues calculating a new output value each loop time. PID
compares the new value to the previous output value and if updating the output point with the new
value would violate the inhibit condition, then the previous output value is maintained. If the new
value would not violate the inhibit condition, then the output point is updated with the new output
value.
Example
If INHB is set to ENABLED when PID receives a lower inhibit signal (LWI) via track input from a
downstream algorithm, the PID algorithm output cannot decrease. The output value remains
constant until either the LWI signal is removed, or the process error changes to where PID output
increases and resumes normal control action.
If INHB is set to DISABLED when PID receives a lower inhibit signal (LWI) via track input from a
downstream algorithm, the PID algorithm continues to calculate a PID output each loop time. The
calculated value is stored in the algorithm and compared to the output calculated during the
previous loop time. If a lower inhibit occurs, the actual PID output will be the greater of the two
calculated values. If a raise inhibit occurs, the actual PID output will be the lesser of the two
calculated values.
Note: In either case, PID uses internal mechanisms to ensure that an integral windup condition
does not occur during an inhibited situation.
388 OW351_R1100
5.78 PIDFF
5.78 PIDFF
Description
The PIDFF algorithm is designed to accept an externally generated analog signal that is used as
a feed-forward bias. This analog signal is summed with the actual PID output (sum of the
proportional, integral and derivative terms) to become the final control output. The advantage to
having the feed-forward input incorporated in the PID algorithm is that saturation conditions,
caused by either the final control output exceeding the algorithms limits or raise/lower inhibit
signals generated by the downstream algorithms, are handled internally to the algorithm. This can
greatly improve Controller response times to sudden changes in the direction (algebraic sign) of
the Controller error signal when the Controller is in a saturation condition.
The PID portion of the algorithm provides a proportional, integral, derivative Controller function.
The algorithm is a parallel PID implementation that utilizes integral tracking signals for bumpless
transfer. The output value is limited via user-defined limits and anti-reset windup is handled
internally.
Functional Symbol
Guidelines
Note: PV = Process Variable

STPT = Set Point
FF = FF Input
1. PV GAIN and PV BIAS must be used to normalize the process variable inputs t o a 0 to 100
percent value. Use this equation:
(PV x PV GAIN) + PV BIAS = PV percent. Thus,
OW351_R1100 389
5.78 PIDFF
2. STPT GAIN and STPT BIAS must be used to normalize the set point to a 0 to 100 percent
value. If setpoint input units are not 0 to 100 percent, then:
(STPT x STPT GAIN) + STPT BIAS = set point percent. Thus:
3. The external feed-forward input should be normalized to 0-100%

(FF x FF GAIN) + FF BIAS = FF percent
Error Deadband and Deadband Gain
The algorithm can be configured to utilize a Deadband region in the Controller error signal. This
Deadband region is used to modify the error signal that is presented to the PID equation.
The Controller error signal is calculated as the difference between the normalized process
variable and normalized set point and is passed as the input to the PID equation. If the algorithm
is configured to utilize an error Deadband and the error is within the deadband limits, the error
that is presented to the PID equation is Error = Error X Error Deadband Gain.
When the algorithm is configured to use deadband, transitions into and out of the deadband
region are smoothed internally by utilizing a hold and track operation. During this transition cycle,
the Controller output is set to its previous value and the integral term is re-calculated to account
for the apparent proportional gain change in the new region. This effectively eliminates the abrupt
change in the proportional term due to the deadband transition. Derivative action is disabled when
the algorithm is operating within the deadband region.
If no deadband action is desired, the inner deadband limit (DBND) should be set to zero.
Single Deadband
The Single Deadband mode is configured by initializing the inner deadband limit (DBND field) to a
non-zero value and setting the deadbands option (DOPT) parameter to SINGLE. This value
represents the normalized Controller error signal to be used as the Deadband region li mits.
Deadband is symmetrical with respect to zero. For example, if the DBND field equals 5, then the
deadband region is between -5% and +5%. If the Controller error signal is within the deadband,
then the actual error that is presented to the PID equation is the product of the error signal and
the error deadband gain. The ERRD field contains the value of the error deadband gain. The valid
values for this field are any real numbers between zero and one [0 - 1].
As an example, consider the following: DBND is 5 and ERRD is 0.5. For a normalized Controller
error signal of 2%, the actual error signal that is applied to the PID equation is 2% x 0.5 = 1%. In
general, for these example values of DBND and ERRD, any normalized error signal between -5%
and +5% is reduced by 50% before being applied to the PID equation. Derivative action is
disabled when the algorithm is operating within the deadband region.
390 OW351_R1100
5.78 PIDFF
Double Deadband
The Double Deadband configuration utilizes two deadband limits. These are the inner (DBND)
and the outer deadband limit (ODBND). Once the absolute value of the error signal is less than or
equal to the inner deadband, then the deadband gain is applied. The deadband gain is applied
until the absolute value of the error signal is greater than the outer deadband.
The Double Deadband mode is configured by initializing the Outer Deadband (ODBND) field to a
value greater than the inner deadband limit (DBND) and setting the deadbands option (DOPT)
parameter to DOUBLE. The Double Deadband mode is designed to be used when a noisy
process variable is present. When noise is present in the Process Variable signal, it causes
fluctuations in the magnitude of the error signal. When a Single Deadband is used, the Controller
error signal can fluctuate in and out of the deadband region (DBND) on successive execution
loops. In severe cases, this can lead to reduced performance of the PID algorithm. An example of
this situation is shown graphically in the following figure.
In the following figure, at time t1, the signal has entered the inner deadband region. At time t2, the
noise has caused the signal to exit the inner deadband region, and at t3, it enters it again. The
same problem is seen again as the signal leaves the inner deadband region, as seen at t4, t5 and
t6.
At each transition into and out of the deadband, the algorithm performs a track and hold
operation. This prevents the output from spiking due to the abrupt change in the proportional
term.
In Singe Deadband mode, subsequent transitions into and out of the deadband region can lead to
reduced performance of the PID algorithm.
OW351_R1100 391
5.78 PIDFF
To prevent this situation, a second outer deadband region (ODBND) can be defined by the user.
This should be larger than the inner deadband region (DBND) (see the following figure). More
specifically, the outer deadband (ODBND) should be defined as equal to, or larger than, the noise
seen in the signal PLUS the inner deadband region (DBND).
For example, if the DBND field is equal to 5, then that deadband region is between -5% and +5%.
Once the Controller error signal reaches this inner deadband region of + or -5%, a noise in the
signal with a peak of + or -3% could push the Controller error signal back out of the inner
deadband region up to + or -8% on the next scan. Therefore, the outer deadband (ODBND)
should be set larger than + or -8% to compensate for noise. In the following figure, the ODBND
was set to +/- 10. If the outer deadband (ODBND) region is less than the defined inner deadband
(DBND) region, then the outer deadband region is set equal to the inner deadband value.
392 OW351_R1100
5.78 PIDFF
Output Calculation
The output (which is in either engineering units or percent and limited by the high and low limits
specified) equals the algebraic sum of the result of the PID equation and the feed-forward input
except:
is present. The output ramps at the user-specified track rate, from the track input back to the
controlled value when the tracking signal is removed.
 When a raise inhibit or lower inhibit signal is present, it may prevent the PID Controller from
controlling.
 When the sum of the actual PID output and the normaliz ed feed-forward input exceeds either
the high or low limit of the algorithm, the output in this case is clipped at the corresponding
limit.
 If the algorithm calculates an invalid real number for the output, the quality of the output is set
to BAD. Consequently, if an invalid value is entered as an input to the algorithm, or if the
algorithm generates an invalid value for the output, the drop is placed into alarm. In all cases,
the output is set to the last GOOD value.
 If the algorithm generates an invalid track output value, the set point input value is used as
the track output, unless it is invalid. The track output value is not updated if both the
calculated track output and the set point input values are invalid.
Tracking Signals
Bit description
16 Track Implemented Passed through or set TRUE

when not in Cascade mode.
17 Track if lower Implemented when not in Not used
Manual mode*
18 Track if higher Implemented when not in Not used

Manual mode*

21 Conditional Track See description of Passed through if in the
cascaded mode. cascaded mode.
23 Deviation Alarm No action Set when the deviation of

process variable and set point is
greater than the given Deviation
Alarm deadband.
OW351_R1100 393
5.78 PIDFF

The High and Low limit flags, the mode, and the tracking signals from the algorithm are output to
FI E L D RE C O R D

Number
DOPT X5-Bit 6 Data Init Required Single Deadband -
options:
Single
Double
CDLY B7-Real Non- Required 0 Cascade Delay -
tunable Time in
Seconds
SPTG R3-Real Tuning Required 1.0 Gain on set -
Constant point. The gain
on the set point
should never be
initialized to
zero.
SPTB R4-Real Tuning Optional 0.0 Bias on set -
Constant point
PVG R1-Real Tuning Required 1.0 Gain on process -

Constant variable input.
The gain on the
set point should
never be
initialized to
zero.
PVB R2-Real Tuning Optional 0.0 Bias on process -
394 OW351_R1100
5.78 PIDFF
FI E L D RE C O R D
FFG S5-Real Tuning Required 1.0 Gain on -

Constant Feedforward.
The gain on
feedforward
should never be
initialized to
zero.
FFB S6-Real Tuning Optional 0.0 Bias on -
Constant Feedforward
input
DACT X5-Byte Data Init Required Normal Type of -
Bit 4 Derivative
action:
Normal -
Derivative
applied to
change in error.
Set point -
Derivative
applied to
change in set
point.
Process -
Derivative
applied to
change in
process
variable.
point
point
OW351_R1100 395
5.78 PIDFF
FI E L D RE C O R D
TYPE X5-Byte Data Init. Required NORMAL Type of PID -

Bits 0 and controller:
1
NORMAL=
Regular PID
control
ESG = PID
control with
error squared
on the
proportional
gain term
ESI = PID
control with
error squared
on the integral
term
ACTN X5-Byte Data Init. Required INDIRECT Direction Flag: -
Bit 2
INDIRECT =
Error = Set point
- process
variable
DIRECT = Error
= Process
variable - set
point
CASC X5-Byte Data Init Required NORMAL Controller is -
Bit 3 downstream in a
cascaded
configuration.
NORMAL =
Normal PID
action.
CASCADED =
See description
of cascaded
mode and
conditional
tracking.
DBND S3-Real Tuning Required 0.0 PID error inner -
Constant deadband *
DOPT X5-Byte Data Init. Required SINGLE SINGLE - Single -

Bit 6 and 7 deadband mode
DOUBLE -
Double
deadband mode
ODBND S7-Real Tuning Required 0.0 PID error outer LA
Constant deadband **
ERRD S4-Real Tuning Required 0.0 PID error -
Constant deadband gain
396 OW351_R1100
5.78 PIDFF
FI E L D RE C O R D
*** PGAIN R8-Real Selectable Required 1.0 PID proportional -

gain. If the
proportional
gain equals
zero, the
proportional part
is not included
in the output.
*** INTG R9-Real Selectable Required 10.0 PID integral -
time in seconds
per repeat. If the
integral time
equals zero, the
integral part is
not included in
the output.
*** DGAIN S1-Real Selectable Required 0.0 PID derivative -
gain. If the
derivative gain
equals zero, the
derivative part is
not included in
the output.
*** DRAT S2-Real Selectable Required 0.5 PID derivative -
rate decay
constant in
seconds
Constant (units per
second)
PV - Variable Required - Process LA
variable analog
input.
FF - Variable Required - Feedforward LA
Input
STPT - Variable Required - Set point. LA
OW351_R1100 397
5.78 PIDFF
FI E L D RE C O R D

value
variable
DVAL - Variable Optional - Derivative term LA
output

input variable
* A value of 0.0 for this field disables all deadband action.
** Anytime that the value of this field is greater than the inner deadband (DBND), the double
deadband action results. This value should be set to zero if single deadband action is desired.
*** When a parameter type is defined as "Selectable" and marked as "Required," the Control Builder
may default the parameter to a value and mark it as "Optional." However, for the control function to be
398 OW351_R1100
5.78 PIDFF
OW351_R1100 399
5.78 PIDFF
Feed-Forward Control Example
Refer to the “Functional Operation of PIDFF” diagram for the following example. Consider the
case where the output limits on the PIDFF algorithm are 0-100%, the external feed-forward input
has a normalized value of 75%, the actual PID output is 50% and the error between process
variable and set point causes the PID output to increase. This condition would require that the
final output be 125%, which violates the algorithm's high limit of 100%. The final PIDFF output is
clipped at 100%. If the error between the process variable and the set point were to change
direction, the PID output would have to move 25% before it had any effect on the final control
output and thus the process variable. Depending on the tuning parameters, the time that this
takes can be significant.
By incorporating the feed-forward input into the PIDFF algorithm, this direction change in the error
between the process variable and set point has an immediate effect on the final control output.
The PIDFF begins integrating from the high limit of 100% and thus has immediate influence on
the final control output and subsequently on the process variable.
Cascaded Mode and Conditional Tracking
Conditional tracking is a scheme which allows tighter control of the process variable when the
control strategy is implemented using cascaded Controllers. Essentially, the conditional tracking
scheme allows the upstream Controller to have immediate influence on the final output when the
error between the process variable and the setpoint changes direction while the downstream
controller is in a saturation condition. Conditional tracking is incorporated when the downstream
Controller (Controller “B” in previous figure) operates in cascaded mode.
The purpose of cascaded mode is to allow two PID algorithms to be used in a cascaded
configuration where the output of one PID is the set point for another. When you desire to arrange
two PID Controllers in this configuration, the type parameter should be set to cascaded in the
downstream Controller only. It is not necessary to configure the upstream Controller in the
cascaded configuration.
400 OW351_R1100
5.78 PIDFF
When the downstream controller is configured in the cascaded mode, the Controller operates as a
conventional PIDFF Controller so long as the Controller is not in a saturation condition. However,
if the controller output is saturated at the HI or LO limit or if the Controller receives an inhibit
signal from a downstream algorithm, the behavior of the cascaded pair is as follows:
The downstream Controller (Controller “B” in the previous figure) asserts the conditional track
signal in its output tracking point along the applicable limit or inhibit bit. The downstream
Controller also calculates a track output value that if applied as a set point input, yields a
Controller error of zero (see the previous Equation 1).
When the upstream Controller sees the conditional track bit set it adjusts its output as follows: If
the error signal causes the Controller output to move against the inhibit signal (for example,
output attempts to increase when the algorithm is receiving a raise inhibit), then the algorithm sets
its output equal to the track input received from downstream.
If the error signal causes the output to move away from the inhibit signal, the algorithm sets its
output equal to the track input and begin controlling.
Without this mode, the upstream Controller would first have to move enough to zero the error on
the downstream Controller before having any effect on the process. This would introduce
additional dead-time in the Controller response and in the case of processes with slow dynamics
(for example, temperature control) this additional deadtime may be significant.
Only the PIDFF algorithm configured to be in cascaded mode asserts the conditional track bit.
The upstream Controller (Controller “A” in previous figure) does not pass the conditional track bit
in its track output.
OW351_R1100 401
5.79 PNTSTATUS
5.79 PNTSTATUS
Description
The PNTSTATUS algorithm outputs the states of two specified bits of the point record's status
word. When the ENBL input is TRUE, the states of BITA and BITB of the point record's status
word are output to OUTA and OUTB, respectively. For example, if the bit specified by BITA is a
one, then OUTA is TRUE. Conversely, if the bit specified by BITA is a zero, then OUTA is FALSE.
This example also holds TRUE for BITB and OUTB.
For analog and digital records, the valid range for BITA and BITB is 0 through 31.
When the ENBL input is TRUE and either the BITA or BITB operand contains an invalid bit
number, no operation occurs and the BITA and BITB outputs are FALSE.
Functional Symbol
FI E L D RE C O R D

number
STAT X1-Byte Data Init. Required 1W Status word 1W, 2W, -
3W
BITA X2-Byte Data Init. Optional 0 Which bit in the point -
record's status word
is output to OUTA
BITB X3-Byte Data Init. Optional 0 Which bit in the point -

record's status word
is output to OUTB
402 OW351_R1100
5.79 PNTSTATUS
FI E L D RE C O R D
ENBL - Variable Required - Enable Input Flag LD, LP

(digital)
IN1 - Variable Required - Input LA, LD
OUTA - Variable Optional - When the ENBL LD, LP
input is TRUE, this
output reflects the
state of the bit
specified by BITA.
OUTB - Variable Optional - When the ENBL LD, LP
input is TRUE, this
output reflects the
state of the bit
specified by BITB.
OW351_R1100 403
5.80 POLYNOMIAL
5.80 POLYNOMIAL
Description
The POLYNOMIAL algorithm performs a mathematical fifth order polynomial function. The output
of the POLYNOMIAL algorithm is the result of a fifth order polynomial equation of the input using
the coefficients listed in this description.
The quality of the analog input is propagated to the output. However, if the algorithm calculates an
invalid value for the output, the quality of the output is set to BAD, and the output value is invalid.
Functional Symbol
FI E L D RE C O R D

Number
CX0 R1-Real Tuning Required 0.0 Zero coefficient -
Constant of the polynomial
equation
404 OW351_R1100
5.80 POLYNOMIAL
FI E L D RE C O R D
CX1 R2-Real Tuning Required 0.0 First coefficient of -

Constant the polynomial
equation
CX2 R3-Real Tuning Required 0.0 Second -
Constant coefficient of the
polynomial
equation
CX3 R4-Real Tuning Required 0.0 Third coefficient -
equation
CX4 R5-Real Tuning Required 0.0 Fourth coefficient -
equation
CX5 R6-Real Tuning Required 0.0 Fifth coefficient of -
Constant the polynomial
equation
Function
OUT = CX0 (IN1)0 + CX1 (IN1)1 + CX2 (IN1)2 + CX3 (IN1)3 + CX4 (IN1)4 + CX5 (IN1)5
OW351_R1100 405
5.81 PREDICTOR
5.81 PREDICTOR
Description
This algorithm can be utilized to implement a standard Smith Predictor control system structure in
processes that are characterized by dynamics that include a deadtime. The advantage of using a
Smith Predictor is that the Controller (typically a PID) tuning can be performed as if no dead time
exists in the process, and hence a relatively high gain can be applied to expedite the response.
The output of the PREDICTOR is the result of the summation of the actual process variable and a
no-delay model output minus the with-delay model output. This is illustrated mathematically in the
functional diagram. The process input to the algorithm is gain and biased. The algorithm output
directly connects to the downstream PID algorithm process input. When no dead time is present
in the process (and the model), the process variable input to the PREDICTOR directly passes
through unmodified to the downstream PID process input. You have the option to configure the
algorithm to use either a first or second order model of the plant.
Since the internal memory size for each algorithm is limited, a long dead time must be realized by
an internal time delay plus a chain of cascaded external delays (implem ented by TRANSPORT
algorithm).
The plant model dead time is realized by storing N samples of the process variable. The value of
N is a function of the Process dead-time and the control area loop time. The value of N is
calculated as follows:
N = (dead time (secs)) / (loop time (secs))
Due to memory limitations, the PREDICTOR algorithm can store up to eight samples. If the value
of N is greater than eight, the remainder of the samples can be realized by using Transport Delay
algorithms as shown in the configuration example of the PREDICTOR.
If the algorithm receives an invalid value as the input, or if it calculates an invalid value as the
output, the drop is placed into alarm and the output is set to the last GOOD value with quality set
to BAD. Under normal operation, the output propagates the quality of the PV input.
Functional Symbol
406 OW351_R1100
5.81 PREDICTOR
Algorithm Tuning
Algorithm Definitions listed as Tuning Constants for this algorithm are monitored and modified
with the Tuning Diagrams. Parameters for the process model (gain, first and second time
constants) can also be modified by outside algorithms through selectable pins. The guideline for
tuning is that the model gain and time constants should be set as close as possible to the
parameters reflecting the real process. Tuning for the length of dead time can be implemented by
modifying the internal time delay (in T3 field) and/or the number of samples in the TRANSPORT
algorithms.
If a first order model of the plant is desired, the FOTC field of the algorithm is initialized to the
value of the time constant (in seconds) of the 1st order model. The SOTC field should be set to a
value of zero. Here the time constant refers to the time (in seconds) that is required for t he Step
response of the process to achieve 66% of its final value.
If a second order model of the plant is desired, more advanced system identification methods can
be used to determine the values of the FOTC and the SOTC.
Both the gain and the dead time can be calculated by applying a step input to the control output
(output of M/A in the configuration example) of the Control Loop. The time (in seconds) that it
takes for the process variable to begin to respond is the dead time. The gain value is calculated
by taking the ratio of the change in the process output divided by the change in input (change in
the process variable divided by the change in control output).
FI E L D RE C O R D
DIAG LU- Data Init Required 106 Tuning diagram -

Integer number
PVG R1 -Real Tuning Required 1.0 Gain on process -
Constant input. The gain
on the input
should never be
placed into
alarm.
PVB R2 -Real Tuning Required 0.0 Bias on process -
TPSC R3 -Real Tuning Required 100.0 Output top of -

Constant scale
BTSC R4-Real Tuning Required 0.0 Output bottom of -

Constant scale
* TDLY T3-Real Selectable Required 0.0 Process time LA

delay
PV - Variable Required - Process variable LA

analog input
OW351_R1100 407
5.81 PREDICTOR
FI E L D RE C O R D
CTRL - Variable Required - Down stream LA

PID control
output
DLIN - Variable Optional - Output of the LA
TRANSPORT
algorithm(s)
* GAIN T4 - Real Selectable Required 1.0 Gain on process LA
MODEL
* FOTC T1- Real Selectable Required 10.0 The 1st time LA
constant in the
model.
* SOTC T2 - Real Selectable Required 0.0 The 2nd time LA
constant
variable
DOUT - Variable Optional - Input to the LA
downstream
TRANSPORT.
Analog
outvariable
The control system structure can be illustrated by the following diagram. The dashed line box
contains the Predictor.
408 OW351_R1100
5.81 PREDICTOR
where:
y(s) = process variable
u(s) = control output
r(s) = set point
 = dead time.
In the ideal case , ,
and the closed-loop transfer function is:
OW351_R1100 409
5.82 PRIORITY Algorithm Package
The PRIORITY algorithm package is a combination of three individual algorithms that can be
used together to perform priority-based sequencing of devices:
 PRIORITY algorithm -- consolidates complex logic to perform priority-based sequencing

when turning devices ON and OFF. The PRIORITY algorithm allows you to attach up to 16
devices and control these devices by turning them on or off based on a set of priorities
configured by the user.
 PRIORITY-EXT algorithm -- dynamically calculates external priorities and is designed for use
with the PRIORITY algorithm. The algorithm allows priorities to be assigned to input device
channels by means of operating hours or other analog parameters related to devices.
 PRIORITY-REJ algorithm -- provides a method to manage load rejection up to a predefined
number of devices and is designed for use with the PRIORITY algorithm. The algorithm
gathers information about priorities of devices and current devices in service, and then uses
this information to turn devices ON or OFF.
410 OW351_R1100
5.82.1 PRIORITY
Description
The purpose of this algorithm is to consolidate complex logic to perform priority-based sequencing
when turning devices ON and OFF. The PRIORITY algorithm allows the user to attach up to 16
devices and control these devices by turning them on or off based on a set of priorities configured
by the user.
Functional Symbol
OW351_R1100 411
Operation
The device status is determined from the feedback inputs (FBx) and the ready for control inputs
(RDYx). An FBx input is the ON/OFF status of a device (1 = ON, 0 = OFF). A RDYx input
indicates if the device is available for control (1 = ready, 0 = not ready).
The following describes the rules of operation:

 A device can be switched ON only when the device is OFF and ready (FBx = 0 and
RDYx = 1).
 A device can be switched OFF only when the device is ON and ready (FBx = 1 and
RDYx = 1).
 If not connected, the RDYx input is considered ON if the corresponding FBx input is
connected.
 If not connected, the RDYx input is considered OFF if the corresponding FBx input is also not
connected.
 If not connected, the device status FBx input is considered OFF.
Number of devices required (NUMRQ)
The algorithm automatically detects the maximum number of devices available for control. This is
calculated by counting the number of devices connected to the FBx pins. At most, 16 individual
devices can be controlled by one Priority algorithm. The number of devices currently ON
(NUMON) is determined by the active FBx inputs. The user, and/or control logic, determines the
number of devices currently required to turn on (NUMRQ). That value is reflected in the NUMRQ
output and is determined by the configured limitations and system inputs.
NUMRQ is determined by:

 Minimum/Maximum Required Devices:
The default range of NUMRQ is 0 to the maximum number of devices connected (up to 16).
Using Low Limit (LLIM), the value of NUMRQ can be forced to keep a minimum number of
devices on. Using High Limit (HLIM), the maximum number of devices allowed to be active
can be held less than the number connected, if desired. For example, if LLIM is set to 3 and
HLIM is set to 5, then the minimal number of devices active will not fall below 3 and the
maximum number of devices active will not exceed 5. If NUMON surpasses either one of
these limits, a high or low flag will be set in STAT (status section). If LLIM and HLIM are 0, the
algorithm will use its default range (0-16).
 If LLIM < 0, LLIM will default to 0.
 If LLIM > 16 or LLIM > HLIM, it will default to the value of HLIM.
 If HLIM < LLIM, it will default to the value of LLIM.
 If HLIM > 16, it will default to the maximum number of devices connected.
Note: If LLIM and HLIM are configured via signal diagrams, the fields will only allow a value
between 0 - 15 for LLIM and 1 - 16 for HLIM.
 Increment/Decrement with INCDV / DECDV

A pulse into INCDV/DECDV will cause an increase/decrease (respectively) of NUMRQ. The
algorithm ensures this number will not drop below or exceed the range of required devices.
Holding in both of these inputs will cancel out both commands and holding in ei ther input will
Increment/Decrement by only one device.
412 OW351_R1100
 Change Several devices with ANUM / NUM

The requested number of devices input (NUM) can override the current number of required
devices, but only if it is in a valid range and the activate NUM input (ANUM) is set. The
INCDV/DECDV signals will be locked out while the ANUM input is set true.
Commanding Devices ON and OFF
The algorithm commands devices ON and OFF using the Command Device ON (DVON) and
Command Device OFF (DVOFF) packed output points, where each of the 16 bits represents the
corresponding device. The algorithm calculates when to turn a device ON and OFF based on
device priority and NUMRQ. In both the DVON and DVOFF outputs, bits for unconnected devices
(FBx) are always OFF.
The algorithm calculates the next device to switch ON or OFF and sets the appropriate bit for
these devices in the Next On (NON) and Next Off (NOFF) packed output points. This calculation
is based on device priority and whether the appropriate FBx and RDYx pins are set. Both outputs
provide an indication of what device would turn on/off next, if the priorities increase/decrease or
NUMRQ is changed.
A bit map of the devices the algorithm expects to be ON is displayed in the REQON output.
Note: Devices whose RDYx signal is off, but FBx is currently on, will be added to the REQON
bit map and to the NUMON value, as well.
Priority Management
Part of the calculation for turning a device ON or OFF is based on the device priority. Priorities are
set by the user using the DPRx fields or EDPRx pins. The priority for each device can be set from
1 to 16 using the DPRx fields, or 0x0 through 0xF using the EDPRx pins, with 1 or 0x0 being the
highest priority and 16 or 0xF being the lowest. More than one device can have the same priority,
in which case higher priority is given to the lower numbered device. For example, if device 1 and
device 13 have the same priority assigned, then device 1 will always be treated as the higher
priority.
The PRIORITY algorithm will try to run the highest priority device first, and work its way to the
lowest priority device, until the NUMRQ is reached (or there are no more devices ready to
activate). For example, if device 1 has a priority of 6 and device 2 has a priority of 3, then device 2
will run before device 1. However, if device 2’s RDYx pin is deactivated and device 1’s RDYx pin
is activated, then device 1 will turn on, even though it has a lower priority.
Priorities can be set in two ways:

 In Automatic Mode:
Priorities can be changed via pins using the external device priority (EDPRx) inputs. Each
input contains packed priorities for four devices. Algorithms will only accept external priorities
if the submit device priority pin (SDPR) is set.
 In Manual Mode:
Priorities can be changed via fields using the device priority DPRx fields. The algorithm will
set the new values, if the user sets the submit device priority SDPR field.
After the algorithm accepts the new priorities, they will be displayed in the CPRx fields. If DPRx is
set to any value outside the range of 1 to 16, CPRx will be set to 16, but the algorithm will not
change the DPRx fields.
OW351_R1100 413
Disabled/Auto/Manual Mode
Selecting between disabled, automatic, and manual modes can be done using the
DSABL/AUTO/MAN inputs or the Disable/Auto/Manual buttons.
In disabled mode, the algorithm will only update the status and number of active devices currently
on (NUMON) and will accept user priority changes. It will not attempt to turn on devices. In
addition, if the rotation mode (RTMOD) parameter is configured as on - ignore disabled
(ON_IGN_DSABL), the algorithm will continue to rotate priorities.
In Manual mode, certain algorithm commands are controlled by fields.
In Auto mode, certain algorithm commands are controlled via input pin connections.
The following parameters are affected by AUTO/MAN mode: INCDV, DECDV, NUM, ANUM,
CODV, CMAN, CAUTO, SDPR, and EDPRx/DPRx.
In addition, you may configure the algorithm to allow both manual and auto commands at the
same time while the algorithm is in auto mode using the manual/auto control (MACTL) parameter.
This allows the operator to direct the algorithm via pushbutton, even though the algorithm is in
auto.
If more than one of the mode signals is set at the same time, the algorithm will give precedence to
Disabled mode, then Manual mode, then Auto mode. For instance, if Manual and Auto are both
set at the same time, the algorithm will reject to Manual mode.
Operation Mode
There are three different ways to turn on several different devices. Using the operating mode
(OPMOD) parameter, devices can be turned on/off in three different modes: SERIAL, PARALLEL,
or serial on, parallel off (S_ON_P_OFF). In serial mode, the devices will be activated or
deactivated one at a time, until the NUMRQ and NUMON equal each ot her. In parallel mode, the
algorithm will calculate the difference between NUMRQ and NUMON and attempt to turn on/off
that many devices all at once. In serial on, parallel off mode, the algorithm will turn on devices in
serial mode but will turn off devices in parallel mode.
Rotation Mode
The PRIORITY algorithm provides the capability to automatically change device priorities
internally, based on the changing states of the FBx inputs. When Rotation mode is activated,
priorities are rotated each time one of the devices is turned on or off. When a device turns off, its
priority is set to the number of connected devices (lowest priority). Devices not connected are set
to a lower priority than all connected devices. For instance, if eight devices are connected, then all
the devices not connected are set to a higher number than 8, as long as the user didn’t tune the
priorities manually. Turning on a device sets it to the highest priority of 1. Priorities of all other
devices are incremented or decremented respectively.
This mode can be switched off (NO_ROTATION), switched on (ROTATION), or switched on when
the algorithm is disabled (ON_IGN_DSABL) using the RTMOD parameter.
414 OW351_R1100
Changeover Mode
The algorithm can be configured to rotate devices based on a set of timers, rather than an
external mechanism. This functionality is called Changeover, and it is designed to even out the
wear of devices while they are running for an extended period of time.
In order to activate changeover, RTMOD must be in an active state (that is, ROTATION or
ROT_WHEN_ENBL modes). In addition, COMOD must be configured to UP_CHNGOVER or
DN_CHNGOVER modes and the three changeover timers need to be configured. The input signal
changeover enable (COEN) indicates that changeover is ready to run (when it is not connected
changeover is enabled by default).
Example:
First, a command is given to the algorithm to start a changeover via the Changeover Device
(CODV) signal. The algorithm will increase the NUMRQ from 3 to 4 (COMOD is set to
UP_CHNGOVER). The fourth Device would have the length of TAC timer (allowed time for
changeover) to turn on. If the device turns on in time, then NUMRQ will hold four devices until the
TTC (transition time) timer counts down to zero. Once TTC reaches zero, NUMRQ is set t o 3
again and then the device that had the highest priority needs to turn off before TAC reaches zero.
Changeover will continue depending on whether the algorithm is in Changeover manual or

Changeover automatic. This is determined by the CMAN and CAUTO parameters. If both
parameters are set, or neither is set, then the algorithm will default to Changeover Manual. In
changeover manual mode, the user must start changeover via the CODV signal. In changeover
auto mode, the TBC (time between changeovers) timer determines the time between
changeovers. At the end of the TBC time, changeover will start again.
The following state table displays the possible states that changeover can be in. These states are
reported through the CSTAT output.
Bit description
0 Idle flag
1 Changeover manual
2 Changeover auto
3 On hold flag
4 Started flag
5 Pending flag
6 Finished flag
7 Ready flag
8 Reinitialize flag
9 Timeout flag
10 External Change flag
11 Manual reject flag
OW351_R1100 415
A description of the states is listed below:

 Idle State
 Job: To wait for algorithm to be ready.
 Reason: If there are no devices to start-up or if the algorithm is disabled or RTMOD is
equal to NO_ROTATION or COMOD is equal to NO_CHNGOVER
 Outputs “Idle” flag is set.
 Next State: “Ready”
 Ready State
 Job: Wait for changeover sequence start.
 Reason: Algorithm was idle, there are ready devices to turn ON/OFF, algorithm is
enabled and RTMOD and COMOD are set and the number of ON devices is equal to the
required number.
 Outputs: “Ready” flag is set.
 Next State: “Started”, “On hold”
 Started State
 Job: Start TAC count down. Increase/decrease required devices number.
 Reason: Algorithm was ready and TBC time elapsed or changeover command was given.
 Outputs: TAC is output to CTIME (Changeover Timer) pin. “Started” flag is set. New
REQON output is set.
 Next State: “Pending,” “On hold,” “Timeout”
 Pending State
 Job: Start TTC count down.
 Reason: Changeover was started and the number of ON devices is equal to the required
number.
 Outputs: TTC is output to CTIME pin. “Pending” flag is set.
 Next State: “Finished” or “On hold”
 Finished State
 Job: Start TAC count down. Increase/decrease required devices number.
 Reason: Changeover was in “Pending” state, devices have been in the same state for
time set in TTC counter.
 Outputs: TAC is output to CTIME pin. “Finished” Flag is set. New REQON output is set.
 Next State: “Idle,” “Timeout”
 On hold State
 Job: To wait for enable changeover signal (COEN input).
 Reason: Algorithm is ready to change state but COEN signal is not present.
 Outputs: ”On hold” flag is set.
 Next State: “Started,” “Pending,” “Finished”
416 OW351_R1100
 Timeout State
 Job: Abandon changeover sequence, reject to manual changeover mode, restart TBC
countdown.
 Reason: Requested change of device states did not occur during TAC countdown.
 Outputs: “Timeout” flag is set. Changeover mode is set to manual. “Manual reject” flag is
set. TBC is output to CTIME pin.
 Next State: “Idle”
 External Change State
 Job: Abandon changeover, reinitialize TBC countdown.
 Reason: External change occurred during changeover sequence.
 Outputs: “External Change” flag is set. TBC is output to CTIME pin.
 Reinitialize State
 Job: Reinitialize TBC countdown.
 Reason: External change occurred when changeover was idle.
 Outputs: “Reinitialize” flag is set. TBC is output to CTIME pin.
 Manual Reject
 Job: This is the error state for automatic changeover.
 Reason(s): If there is an interruption in the sequence during Auto Changeover, then the
sequence will default to Manual Changeover.
 Interruptions include the following:
- Unexpected change in the number of required devices.
- The control mode is changed from auto, to manual or disabled.
- SDPR is activated and new device priorities are excepted.
- One of the timers (TAC, TBC, TTC) finished counting down before its task could
complete.
- TBC is initially set to zero or less.
 To clear the Manual Reject, start the sequence again. However, if the interruption was
never taken care of, or accrues again, then the sequence will again abort to this state.
OW351_R1100 417
Prohibited Configurations (PCx)
The algorithm allows the user to specify up to 32 prohibited configurations. This is represented as
32 individual bit maps. For example, if bits 0, 2, and 10 are set, then devices 1, 3 and 11 cannot
run at the same time. If the algorithm tries to change devices to a configuration that is forbidden,
then the algorithm will try to find another configuration that will work.
Note: Prohibited configurations only apply to exact instances of running devices. For instance, if
devices 1, 2, and 3 are prohibited from running, and devices 1, 2, 3, and 4 are requested to run,
then the prohibited configuration will not apply, and all four devices will run. However, if only
devices 1, 2, and 3 are attempting to run, then the algorithm will prevent the devices from
running.
Algorithm Status
Algorithm status and error information is stored in the STAT output. The STAT output bits are
defined as shown:
Bit description
0 Disabled mode.
1 Manual mode.
2 Auto mode.
3 Increasing.
4 Decreasing.
5 Priorities rotated.
6 Priority rotation enabled.
7 External priorities accepted.
8 Algorithm load or tuning change.
9 No more available devices to turn OFF.
10 No more available devices to turn ON.
11 Maximum or minimum number of ON devices reached.
12 Reserved.
13 Prohibited configuration.
14 External Priorities are different than current Priorities.
15 RESERVED.
418 OW351_R1100
SID Storage
FI E L D RE C O R D
Inputs:
AUX1 C7-SID Auxiliary Required -- Priority Auxiliary LC

Record
DSABL G1 Variable Optional -- Disabled Mode LD, LP
Request
RDY1 - Variable Optional -- Device 1 is LD, LP
ready and
available.
FB1 - Variable Required -- Device 1 On/Off LD, LP
Feedback
ready and
available
FB2 - Variable Required -- Device 2 On/Off LD, LP
Feedback
ready and
available
FB3 - Variable Optional -- Device 3 On/Off LD, LP
Feedback
ready and
available
Feedback
ready and
available
Feedback
ready and
available
Feedback
OW351_R1100 419
FI E L D RE C O R D

ready and
available
Feedback
ready and
available
Feedback
ready and
available
Feedback
ready and
available
FB10 - Variable Optional -- Device 10 LD, LP
On/Off
Feedback
ready and
available
On/Off
Feedback
ready and
available
On/Off
Feedback
ready and
available
On/Off
Feedback
ready and
available
On/Off
Feedback
420 OW351_R1100
FI E L D RE C O R D

ready and
available
On/Off
Feedback
ready and
available
On/Off
Feedback
INCDV CN:9 Variable Optional -- Increase LD, LP
number of
required ON
devices
DECDV CN:8 Variable Optional -- Decrease LD, LP
number of
required ON
devices
MAN CN:12 Variable Optional -- Manual mode LD, LP
request
AUTO CN:13 Variable Optional -- Auto mode LD, LP
request
NUM G8 Variable Optional -- Required LA
number of ON
devices (used
with ANUM).
ANUM G2 Variable Optional -- Activate LD, LP
"Number of
Required ON
Devices"
CODV G3 Variable Optional -- Request device LD, LP
changeover
COEN -- Variable Optional -- Device LD, LP
changeover
enabled
CMAN D4 Variable Optional -- Changeover LD, LP
Manual mode
CAUTO D5 Variable Optional -- Changeover LD, LP
Auto mode
LLIM G9 Selectable Optional -- Lowest number LA
of requested
devices
HLIM B0 Selectable Optional -- Highest number LA
of requested
devices
OW351_R1100 421
FI E L D RE C O R D
EDPR1 - Variable Optional -- External LP

priorities for
devices 1 - 4.
priorities for
devices 5 - 8.
priorities for
devices 9 - 12.
priorities for
devices 13 - 16.
SDPR G5 Variable Optional -- Submit device LD, LP
priority pin.
Outputs:
DVON B1 - SID Variable Required -- Devices to be LP
switched ON,
but not OFF.
DVOFF B2 - SID Variable Required -- Devices to be LP
switched OFF,
but not ON
NON YU - SID Variable Optional -- Next device to LP
go ON
NOFF B4 - SID Variable Optional -- Next device to LP
go OFF
REQON B5 - SID Variable Optional -- Devices LP
required to be
ON
CURON B6 - SID Variable Optional -- Devices LP
currently ON
RDYDV B7 - SID Variable Optional -- Devices ready LP
and available
STAT B8 - SID Variable Optional -- Status LP
NUMRQ B9 - SID Variable Optional -- Number of LA
devices
required to be
ON
NUMON C0 - SID Variable Optional -- Number of LA
devices
currently ON
PRI1 C1 - SID Variable Optional -- Priorities for LP
devices 1 - 4.
devices 5 - 8
devices 9 - 12
422 OW351_R1100
FI E L D RE C O R D

devices 13 - 16
CSTAT C5-SID Variable Optional -- Changeover LP
status
CTIME C6-SID Variable Optional -- Changeover LA
timer
Input Parameters:
MACTL D0 Tuning Required 0 Manual/Auto

Constant Control mode:
0 - Normal
1 - Man in Auto
OPMOD YQ Tuning Required 0 Operation --
Constant mode:
0 - SERIAL
1 - PARALLEL
2 -
S_ON_P_OFF
Serial on
parallel off
RTMOD D2 Tuning Required 0 Rotation mode: --
Constant
0 - OFF
1 - ON
2 -
ON_IGN_DSAB
L
COMOD YP Tuning Required 0 Changeover --
Constant modes:
0 -
NO_CHNGOVE
R
1 -
UP_CHNGOVE
R
2 -
DN_CHNGOVE
R
TBC D6 Tuning Required 1 Time period --
Constant between
changeovers.
TAC YN Tuning Required 1 Time allowed --
Constant for changeover
(between start
and stop).
OW351_R1100 423
FI E L D RE C O R D
TTC D8 Tuning Required 1 Time to remain --

Constant in the "Pending
State" during
changeover.
CTMOD D9 Alg. Init. Variable 0 Control Mode: --
0 - Disabled
1 - Manual
2 - Auto
DVFB YM Alg. Init. Variable 0 Map of devices --
feedback
connections
STATS YL Alg. Init. Variable 0 STAT value --
(lower 16 bits)
and CSTAT
value (higher 16
bits).
CPR1 E3 Alg. Init. Variable 0 Current Priority --
for Device 1.
for Device 2.
CPR3 YC Alg. Init. Variable 0 Current Priority --
for Device 3.
CPR4 Y9 Alg. Init. Variable 0 Current Priority --
for Device 4.
for Device 5.
for Device 6.
for Device 7.
for Device 8.
for Device 9.
CPR10 XY Alg. Init. Variable 0 Current Priority --
for Device 10.
CPR11 XW Alg. Init. Variable 0 Current Priority --
for Device 11.
CPR12 F4 Alg. Init. Variable 0 Current Priority --
for Device 12.
for Device 13.
for Device 14.
424 OW351_R1100
FI E L D RE C O R D
CPR15 XV Alg. Init. Variable 0 Current Priority --

for Device 15.
CPR16 XU Alg. Init. Variable 0 Current Priority --
for Device 16.
Auxiliary Priority Algorithm Definitions
FI E L D RE C O R D
DPR1 G0 Tuning Required 1 Priority for --

Constant Device 1
(1 - 16)
Constant Device 2
(1 - 16)
Constant Device 3
(1 - 16)
Constant Device 4
(1 - 16)
Constant Device 5
(1 - 16)
Constant Device 6
(1 - 16)
Constant Device 7
(1 - 16)
Constant Device 8
(1 - 16)
Constant Device 9
(1 - 16)
Constant Device 10
(1 - 16)
DPR11 B0 Tuning Required 11 Priority for --
Constant Device 11
(1 - 16)
Constant Device 12
(1 - 16)
OW351_R1100 425
FI E L D RE C O R D

Constant Device 13
(1 - 16)
DPR14 YU Tuning Required 14 Priority for --
Constant Device 14
(1 - 16)
Constant Device 15
(1 - 16)
Constant Device 16
(1 - 16)
PC1 C8 Tuning Required 0 Prohibited --
Constant configuration 1
PC2 YT Tuning Required 0 Prohibited --
PC3 D0 Tuning Required 0 Prohibited --
PC4 YQ Tuning Required 0 Prohibited --
PC6 YP Tuning Required 0 Prohibited --
PC10 YN Tuning Required 0 Prohibited --
PC13 YM Tuning Required 0 Prohibited --
PC14 YL Tuning Required 0 Prohibited --
PC15 E2 Tuning Required 0 Prohibited --
426 OW351_R1100
FI E L D RE C O R D

PC18 YC Tuning Required 0 Prohibited --
PC19 Y9 Tuning Required 0 Prohibited --
PC25 XY Tuning Required 0 Prohibited --
PC26 XW Tuning Required 0 Prohibited --
PC27 F4 Tuning Required 0 Prohibited --
PC30 XV Tuning Required 0 Prohibited --
PC31 XU Tuning Required 0 Prohibited --
PC32 XR Tuning Required 0 Prohibited --
OW351_R1100 427
5.82.2 PRIORITY-EXT
Description
The PRIORITY-E XT algorithm allows the user to dynamically calculate external priorities and is
designed for use with the PRIORITY algorithm. The algorithm allows priorities to be assigned to
input device channels by means of operating hours or other analog parameters related to devices.
Functional Symbol
Sorting
The PRIORITY-E XT algorithm sorts inputs using the status of each analog input based on the
status priority mode (SPMOD), and the value of the analog input (AINx) based on the sorting
mode (SOMOD).
Status Priority Mode
The algorithm sorts by Status first. The status priority mode is configured via the SPMOD
parameter:
Note: Even if SPMOD is set to NONE, inputs that are not connected will have the lowest
priorities.
 Standard
 Status Priority 0 – Quality - Good
 Status Priority 1 – Quality - Fair
 Status Priority 2 – Quality - Poor
 Status Priority 3 – Quality - Bad
 Status Priority 4 – Sensor
 Status Priority 5 – Timeout
 Status Priority 7 – Point Not Connected
 Custom – user can assign each status (SPG, SPF, SPP, SPB, SPS, SPT) a custom priority
(0-5)
 None - Priorities are not taken into account while sorting inputs
Note: It is possible for a point to have an assigned quality and also be in Sensor or Timeout
status. In this scenario, Timeout tak es precedence over Sensor, and Sensor tak es precedence
over all Quality statuses.
428 OW351_R1100
Sorting Mode
Once the algorithm sorts by status, it will then sort the inputs by value. Sorting mode (SOMOD)
determines how the algorithm will sort the inputs. If ascending, the algorithm will assign a greater
priority to the lower numbered input with the lowest value. If descending, the algorithm will assign
greater priority to the higher numbered input with the highest value.
External Device Priority (EDPR) Outputs
Each output contains packed priorities for four devices. Priorities are zero based (Highest priority -
0x0 through Lowest priority - 0xF) are output through four packed points EDPR1-EDPR4. Bits 0-3
of EDPR1 contain the priority for input/device 1; bits 4-7 in EDPR1 contain the priority for
input/device 2; bits 8-11 in EDPR1 contain the priority for input/device 3; and bits 12-15 contain
the priority for input/device 4. EDPR2 applies to inputs 5-8, EDPR3 applies to inputs 9-12, and
EDPR4 applies to inputs 13-16. The EDPRx outputs can be connected directly to the EDPRx
inputs of the PRIORITY algorithm.
Current Device Priority (CPR) Fields
The current device priority fields store the same values that are in the EDPR outputs for use with
graphics applications. The priorities in these fields are one based. For instance, if the priority
displayed in EDPRx is 0x0, the priority will display as 1 in the CPR field. If it is a 0x5 in EDPRx, it
will display as a 6 in the CPR field.
FI E L D RE C O R D
Inputs:
AIN1 -- Variable Required -- Analog input 1 to LA

use for sorting.
AIN2 -- Variable Required -- Analog input 2 to LA
use for sorting.
AIN3 -- Variable Optional -- Analog input 3 to LA
use for sorting.
use for sorting.
use for sorting.
use for sorting.
use for sorting.
use for sorting.
use for sorting.
AIN10 -- Variable Optional -- Analog input 10 LA
to use for sorting.
OW351_R1100 429
FI E L D RE C O R D

to use for sorting.
to use for sorting.
to use for sorting.
to use for sorting.
to use for sorting.
to use for sorting.
Outputs:
EDPR1 -- Variable Required -- Priorities for LP
devices
1 - 4.
EDPR2 -- Variable Optional -- Priorities for LP
devices
5 - 8.
devices
9 - 12.
devices
13 - 16.
Input Parameters:
SOMOD X1 Tuning Required 0 Sorting mode: --
Constant
0 - Ascending
1 - Descending
SPMOD X2 Tuning Required 0 Status Priority: --
Constant
0 - Standard
1 - Custom
2 - None
SPG X4 Tuning Required 0 Assigned Priority --
Constant for status: GOOD
quality.
SPF X5 Tuning Required 1 Assigned Priority --
Constant for status: FAIR
quality.
SPP X6 Tuning Required 2 Assigned Priority --
Constant for status: POOR
quality.
430 OW351_R1100
FI E L D RE C O R D
SPB X7 Tuning Required 3 Assigned Priority --

Constant for status: BAD
quality.
SPS X8 Tuning Required 4 Assigned Priority --
Constant for status:
SENSOR.
SPT X9 Tuning Required 5 Assigned Priority --
Constant for status:
TIMEOUT.
CPR1 G0 Alg. Init. Variable 0 Current Priority --
for Device 1.
for Device 2.
for Device 3.
for Device 4.
for Device 5.
for Device 6.
for Device 7.
for Device 8.
for Device 9.
for Device 10.
CPR11 B0 Alg. Init. Variable 0 Current Priority --
for Device 11.
for Device 12.
for Device 13.
CPR14 YU Alg. Init. Variable 0 Current Priority --
for Device 14.
for Device 15.
for Device 16.
OW351_R1100 431
5.82.3 PRIORITY-REJ
Description
The PRIORITY-REJ algorithm provides a method to manage load rejection up to a predefined

number of devices and is designed for use with the PRIORITY algorithm. The algorithm gathers
information about priorities of devices and current devices in service, and then uses this
information to turn devices on or off.
Functional Symbol
Current State of Devices
1. Devices Ready for Control (RDYDV)

Each bit in the packed RDYDV input represents one device. If a bit is active, then the
algorithm assumes the device is ready to be controlled and can be turned on/off as needed.
When a bit is not active, the required on (RQON) output will reflect the current state of that
device based on the CURON input.
The RDYDV input is designed to be used with the RDYDV output from the PRIORITY
algorithm. If the RDYDV input is not connected, all devices are considered “ready for control”
by this algorithm.
2. Devices Currently ON (CURON)
Each bit in the packed CURON input represents one device. If a bit is active, then the
algorithm assumes the device is currently on. The algorithm then limits the number of devices
the operator wants to remain on, based on this input and the required number of devices
(NUM) input. Only devices that are ON and ready (RDYDV) can be activated or deactivated.
The resulting algorithm calculation is reflected in the required on (RQON) output. If NUM is
greater than the number of devices currently on, then the algorithm will not attempt to turn
additional devices on.
The CURON input is designed to be used with the CURON output from the PRIORITY
algorithm. However, the CURON input can also be connected to another PRIORITY -REJ
algorithm (RQON) output if cascading algorithms are being used.
3. Required Number of Devices (NUM)
Required Number of Devices (NUM) controls the number of devices that the algorithm will
activate using RQON. For example, if seven devices are available (both CURON and
RDYDV) and NUM is set to 3, then three devices will be selected to keep on. The algorithm
will choose the devices based on the priority assigned to them via the PRIx pins. Higher
priority devices will be selected first.
432 OW351_R1100
4. Devices Currently OFF (DVOFF) and Reject (REJ)

Each bit in the packed DVOFF input represents one device. When the reject input (REJ) is
inactive, the required off (RQOFF) output will reflect the DVOFF input . When the REJ input is
active, the RQOFF output will attempt to turn off all devices that are not currently selected to
stay on (RQON).
The DVOFF input is designed to be used with the DVOFF output from the PRIORITY
algorithm. This input may also be connected to the ‘Devices required off’ (RQOFF) output
from another PRIORITY-RE J algorithm.
Device Priority Inputs
Each PRIx input contains the packed priorities for four devices (PRI1 though PRI4). For example,
Bits 0-3 of PRI1 contain the priority for device 1; bits 4-7 contain the priority for device 2; bits 8-11
contain the priority for device 3; and bits 12-15 contain the priority for device 4. PRI2 applies to
devices 5-8, PRI3 applies to devices 9-12, and PRI4 applies to devices 13-16.
The PRIx inputs are designed to be used with the PRIx outputs of the PRIORITY algorithm. The
priorities of each device can only be set between 0x0 (the highest priority) and 0xF (the lowest
priority). If two (or more) devices have the same priority, then the lowest numbered device will be
given higher priority.
Algorithm Status
Algorithm status and error information is stored in the STAT output. The STAT output bits are
defined as shown:
Bit description
0 OK flag -- set when it is possible to keep the required number of devices.

1 Reject flag -- set when the REJ command is given.
2 Equal flag -- set when the number of currently active devices equals the required
number of devices.
3 Inadequate Number of Devices flag -- set when the required number of devices is
greater than the number of devices that can be activated.
4 Surplus Number of Devices flag -- set when it is not possible to turn off sufficient
number of devices.
5 Tuning error flag -- set when the required number of devices is less than 0 or g reater
than 16.
OW351_R1100 433
SID Storage
algorithm LC record). Output SIDs are mapped into the C0 - C2 fields.
FI E L D RE C O R D
Inputs:
REJ -- Variable Required -- Active Reject LD

mode
RDYDV -- Variable Optional -- Devices available LP
for control
CURON -- Variable Optional -- Devices currently LP
on
NUM G0 Selectable Required -- Required number LA
of ON devices
DVOFF -- Variable Optional -- Devices currently LP
off
PRI1 -- Variable Optional -- Packed priorities LP
for channels 1-4
for channels 5-8
for channels 9-12
for channels 13-
16
Outputs:
RQOFF B0 Variable Required -- Devices required LP
C0-SID to be OFF.
RQON B1 Variable Optional -- Devices required LP
C1-SID to be ON.
STAT B2 Variable Optional -- Algorithm status. LP
C2-SID
434 OW351_R1100
5.83 PSLT
5.83 PSLT
Description
PSLT calculates Pressure of Saturated Liquid given its Temperature. It is one of the functions of
the STEAMTABLE algorithm (see page 544).
Functional Symbol
PSLT input and output values
(INPUT 1) TEMP 32.0 705.47

(OUT 1) PRES 0.0885891400 16000.00
OW351_R1100 435
5.84 PSVS
5.84 PSVS
Description
PSVS calculates Pressure of Saturated Vapor given its Entropy (S). It is one of the functions of
the STEAMTABLE algorithm (see page 544).
Functional Symbol
PSVS input and output values
(INPUT 1) ENTR 1.0612 2.1873

(OUT 1) PRES 0.08858914 3208.234
436 OW351_R1100
5.85 PULSECNT
5.85 PULSECNT
Description
The PULSECNT algorithm counts the number of FALSE to TRUE transitions of the digital input
point. If the Reset flag is TRUE, the output count is set to zero before the digital value is checked.
Functional Symbol
FI E L D RE C O R D
RSET - Variable Required - Input (digital); reset LD, LP

flag
IN1 - Variable Required - Input (digital signal) LD, LP
count
Function
IF RSET
THEN OUT = 0
IF IN1 = TRUE AND OLDIN = FALSE
THEN OUT = OUT + 1
where:
OLDIN = locally retained variable
OW351_R1100 437
5.86 QAVERAGE
5.86 QAVERAGE
Description
The QAVERAGE algorithm output is the unweighted average of the N inputs. Analog inputs
whose quality is BAD, or whose value is not being updated, are excluded from the average
calculation so that only the remaining inputs are averaged. The quality of the output equals the
worst quality of all the input values averaged. If all points have BAD quality, the old output value is
retained, and the quality of the output is set BAD.
The values of the analog inputs to the algorithm are checked for invalid real numbers. If the value
of an input is invalid, that input is considered to have BAD quality.
Functional Symbol
FI E L D RE C O R D
IN1 - Variable Optional - Input (analog) LA

•
•
•
IN8
Function
If the quality is GOOD for all points, and the points are being updated,
THEN OUT = (IN1 + ...INN)/N
Any point with BAD quality is excluded from the average. If all points have BAD quality,
THEN OUT = OLDOUT
and the quality is BAD.
438 OW351_R1100
5.87 QUALITYMON
5.87 QUALITYMON
Description
The QUALITYMON algorithm sets the digital output signal (OUT) TRUE if the input value (IN1)
has the same quality as selected in the quality type field(X1). IN1 can be either an analog or
digital variable.
The value of the input (IN1) to the algorithm is checked for invalid real numbers. If the input value
is invalid, that input is considered to have BAD quality, and the digital output (OUT) is set TRUE.
Functional Symbol
FI E L D RE C O R D

number
CHK X1-Byte Data Init Required BAD Quality check type: -
BAD, FAIR, Not
GOOD, GOOD
IN1 - Variable Required - Input (analog or LA, LD
digital)
Function
If the quality of IN1 is the selected quality type, or if its value is not being updated,
THEN OUT = TRUE

ELSE
OUT = FALSE
OW351_R1100 439
5.88 RAMPGEN
5.88 RAMPGEN
Description
The RAMPGEN algorithm ramps its output to follow a setpoint target when in automatic mode, or
it ramps the output up or down at a fixed rate in manual mode.
Functional Symbol
Functionality
The bits in the STIN input pin control the behavior of the RAMPGEN algorithm.
Bit description
Bit 0 Initialize OUT to INIT input. If this bit is active, OUT is set immediately to the INIT value.
If the INIT value is higher than HILM or lower than LOLM, then OUT is cut to the limit.
Note: If Bit 0 is set to TRUE, it overrides the other b its. The algorithm initializes OUT to INIT and
ignores the other b its.
Bit 1 Ramp Auto/Manual Mode (0 - MAN, 1 - AUTO).

In AUTO mode the algorithm ramps its output signal to follow a target setpoint (TARG)
with the rate defined by LORT or HIRM (depending on the value of bit 4).
In MAN (manual) mode, the algorithm can ramp the output down (if bit 2 is TRUE) or up
(if bit 3 is TRUE). The rate is defined by LORT or HIRT (depending on the value of bit
4).
Bit 2 Ramp Down in manual mode.
Bit 3 Ramp Up in manual mode.
Bit 4 Fast Ramp Rate (0 - NORMAL, 1 - FAST).
440 OW351_R1100
5.88 RAMPGEN
Bit 5 Implied manual mode. When TRUE and a Ramp Up or Down (bit 2=1 or bit 3 =1), the
algorithm will ramp in manual mode without respect to the Ramp Auto/Manual mode (bit
1).
Bit 6 Inhibit increase.
Bit 7 Inhibit decrease.
Bits 8 - 15 NOT USED.
The state of the algorithm is presented from the STOU output pin. It is a word of 16 consecutive
bits. They are:
Bit description
Bit 0 Output is at minimum.

Bit 1 Output is at maximum.
Bit 2 Initialize input status.
Bit 3 Setpoint is increasing.
Bit 4 Setpoint is decreasing.
Bit 5 Manual “Raise/Lower” is active.
Bits 6 - 15 NOT USED.
The OUT output pin keeps the current value for setpoint.
Also note:
 Fast and slow ramp has to be a positive value.
 DDBND parameter has to be greater or equal to 0.0. This parameter defines the minimum
value of output change to set Bit 3 or Bit 4 in the STOU output pin.
BIT 3 is TRUE when (OUT – LAST_OUT) > DDBND * task_area.
BIT 4 is TRUE when (OUT – LAST_OUT) < -DDBND * task_area.
OW351_R1100 441
5.88 RAMPGEN
Tracking and Limits
Tracking and limiting are done through signals passed in the upper 16 bits of the third stat us word
found in the analog input signal TRKIN:
Bit description
BI T D E S C R I P TI O N AC TI O N TOUT S I G N AL

442 OW351_R1100
5.88 RAMPGEN
Quality
The quality of the OUT pin will be set to the same value as the lowest quality analog input pin. For
example, if the INIT pin quality is BAD, LORT quality is FAIR, and all other inputs quality are
GOOD, then the OUT quality is set to BAD. In this case, the algorithm calculates the value based
on the bits in the STIN input and updates the OUT and TOUT pins in each loop.
The quality of the STIN input is not considered in the quality calculations.
If the value of inputs used for OUT calculations is invalid (INF or NAN), then the algorithm does
not update the SETPT and TOUT pins – the outputs are set to the last correct value.
FI E L D RE C O R D
DIAG LU-Integer Data Init Required Not defined Tuning Diagram -

yet Number.
DDBND R1 Tuning Required 0.0 Deadband for -
parameter changes
INIT R2 Selectable Required 0.0 Initial value LA
LORT R3 Selectable Required 1.0 Slow ramp rate per LA
second.
HIRT R4 Selectable Required 5.0 Fast ramp rate per LA
second.
TPSC R5 Selectable Required 100.0 Output Top of LA
Scale
BTSC R6 Selectable Required 0.0 Output Bottom of LA
Scale
STIN Variable Required Input status bits LP
TARG Selectable Required 0.0 Setpoint target LA

TOUT Variable Required Track out LA
OUT Variable Required Setpoint LA
STOU Variable Optional Output status bits LP
TRKIN Variable Optional Tracking input LA
OW351_R1100 443
5.89 RATECHANGE
5.89 RATECHANGE
Description
The RATECHANGE algorithm calculates the analog value of OUT as the smoothed rate of
change of IN1. The smoothing time constant (SMTH) can either be dynamic, using an input pin, or
a constant, by defining it within the algorithm. This calculation is performed once per loop cycle
giving OUT units of [IN1] per loop time.
If the smoothing time constant (SMTH) is less than zero, the negative value is ignored and the
calculation is performed with a smoothing time constant of 0. The quality of OUT is then set to
BAD. The quality of OUT will also be set to BAD if an invalid real number is read from IN1. Unless
either of these situations occur, the quality of OUT will be the same as the quality of IN1.
Functional Symbol
FI E L D RE C .

Number
* SMTH R1-Real Selectable Required 0.0 Smoothing time LA
constant in seconds
Note: This is
approximately 1/5
of the total time to
settle. For
example, for 1
minute total, set
SMTH to 12
seconds.
444 OW351_R1100
5.89 RATECHANGE
FI E L D RE C .

Function
where:
S(N) = smoothed value of the analog variable (alpha x IN1) + (beta x old
smoothed value)
SS(N) = double smoothed value of the analog variable (alpha x S(N)) + (beta x old
double smoothed value)
alpha = 1 - E(-loop time/SMTH)
beta = E(-loop time/SMTH)
loop time = sampling time (loop time)
OW351_R1100 445
5.90 RATELIMIT
5.90 RATELIMIT
Description
The RATELIMIT algorithm is a rate limiter with fixed rate limit and flag when rate limit is
exceeded. For the RATELIMIT algorithm, if the rate of change of the output is less than or equal
to the rate limit, the output equals the input, and the digital output flag is set FALS E. If the rate of
change of the output is greater than the rate limit, the output change is limited to the rate limit
value and the digital output flag is set to TRUE. The quality of the analog input is propagated to
the output.
The input value (IN1) to the algorithm is checked for invalid real numbers. If the input value is
invalid, the output is invalid and the quality of the output is set to BAD. Also, if the input is invalid,
the digital output flag retains its last value and its quality is set to BAD. If the input value is valid,
the quality of the input is propagated to the output.
Functional Symbol
Tracking Signals
Bit description
446 OW351_R1100
5.90 RATELIMIT

** Only when the Track signal is not present; the signals are set according to the definition gi ven
FI E L D RE C .

Number

point
point
TRAT R4-Real Tuning Required 2.5 Track Ramp -
Constant Rate (units per
second)
* RALM R1-Real Selectable Required 0.0 Rate of change LA
limit in units per
second
OW351_R1100 447
5.90 RATELIMIT
FI E L D RE C .

value; For mode
and status
signals for input

limiting mode
signals and track
value
FOUT - Variable Required - Output (digital) LD, LP
Function
PLR = RALM * (TS/1000)

TEMP = (IN1 - OLDOUT)
IF ABS(TEMP) < PLR
THEN OUT = IN1
FOUT = FALSE
ELSE
IF TEMP > 0.0
THEN OUT = OLDOUT + PLR
ELSE
OUT = OLDOUT - PLR
FOUT = TRUE
IF OUT > TPSC
OUT = TPSC
ELSE
IF OUT < BTSC
OUT = BTSC
where:
PLR = rate per loop
OLDOUT = locally retained variable
TEMP = local, temporary variable
TS = sampling time (loop time) in milliseconds
448 OW351_R1100
5.91 RATEMON
5.91 RATEMON
Description
The RATEMON algorithm is a rate of change monitor with reset deadband and fixed/variable rate
limit. For the RATEMON algorithm, if the input value (IN1) increases at a rate faster than the user-
specified rate of change limit in the positive direction, or decreases at a rate faster than the user-
specified rate of change limit in the negative direction, the digital output flag (OUT) is set TRUE.
To reset the output flag, the input value must increase at a rate slower than the rate of change
limit in the positive direction minus the deadband on the positive rate of change limit, or decrease
at a rate slower than the rate of change limit in the negative direction minus the deadband on the
negative rate of change limit.
The input value (IN1) is checked for invalid real numbers. If IN1 is invalid, the digital flag retains
its last value and its quality is set to BAD.
Functional Symbol
FI E L D RE C O R D

Number
* PRAT R1-Real Selectable Required 0.0 Rate of change LA
limit in the
positive
direction
(absolute value)
PDB R2-Real Tuning Optional 0.0 Deadband on -
Constant the positive rate
of change limit
(absolute value)
OW351_R1100 449
5.91 RATEMON
FI E L D RE C O R D
* NRAT R3-Real Selectable Required 0.0 Rate of change LA

limit in the
negative
direction
(absolute value)
NDB R4-Real Tuning Optional 0.0 Deadband on -
Constant the negative
rate of change
limit (absolute
value)

Function
RATE = (IN1 - OLDIN)/TS

IF (RATE > PRAT)
OR (RATE < (0 - NRAT))
THEN OUT = TRUE
ELSE
IF (RATE < (PRAT - PDB))
AND (RATE > (0 - (NRAT - NDB)))
THEN OUT = FALSE
where:
RATE = local, temporary, variable
OLDIN = locally retained, real variable
TS = sampling time (control task loop time)
450 OW351_R1100
5.92 RESETSUM
5.92 RESETSUM
Description
The RESETSUM algorithm accumulates until told to reset. For the RESETSUM algorithm, if the
Run flag is TRUE, the output value (OUT) is the sum of the gained input value (IN1) and the old
output value. If the Freeze flag is TRUE, the output value is also stored in the frozen output
(FOUT). As OUT continues to totalize IN1, the value in FOUT is frozen when the Freeze flag
reverts back to FALSE.
If the Reset flag is TRUE, OUT is set to the reset count stored in the RCNT (R1) field of the
algorithm record. If the Run flag is FALSE, the algorithm does nothing. You may tune the output
value anytime by setting the TRST (R3) field of the algorithm record to a non-zero value. The
algorithm will set the TRST (R3) field back to zero after it detects a non-zero value. The TRST
(R3) value is checked first; then, the Reset flag is checked before the summation is made.
Note: The Ovation system is limited to single precision floating point numbers, which can affect
algorithm precision. This may be seen if the RESETSUM algorithm stops updating its output and
lock s at what appears to be a maximum value (though no max value is defined or reached). For
more information on this, refer to: What are single precision floating point numbers?
(see page 6).
Functional Symbol
The quality of the input is propagated to the output points (OUT and FOUT) under the following
conditions:
 The RUN flag is TRUE.

 The outputs are not scan-removed.
 The values of the inputs and outputs are valid real numbers.
 The RSET flag must be FALSE for the quality of the output (OUT) to be updated. However, if
the RSET flag is TRUE, the output retains its last quality value.
 The freeze flag (FFLG) must be TRUE for the quality of the frozen point (FOUT) to be
updated. However, if the freeze flag is FALSE, the frozen output (FOUT) retains its last quality
value.
The quality of the output is not affected by requests to tune the value of the output through the
use of the R3 record field or by setting the RSET flag to TRUE.
OW351_R1100 451
5.92 RESETSUM
Quality propagation is overruled by invalid real numbers. If the input (IN1) contains an invalid real
number, the quality of the output (OUT) is set to BAD, providing the point is not scan-removed
and that the RUN flag is TRUE. The quality of the frozen output point (FOUT) is also set to BAD if
the point is not scan-removed and the freeze flag (FFLG) is TRUE.
The value of the input (IN1) is checked for invalid real numbers. If the input value is invalid, the
output (OUT) retains its last valid value. If the input value is valid, the quality of IN1 is propagated
to OUT.
If the FFLG flag is TRUE and the input is invalid, the value of the frozen output (FOUT) is equal to
the output (OUT).
If the input is invalid, any requests to digitally reset the output value (OUT) through the use of the
RSET flag are ignored.
FI E L D RE C O R D

Number
RCNT R1-Real Tuning Required 0.0 Reset count -

Constant
GAIN R2-Real Tuning Required 1 Gain on the input -

Constant
TRST R3-Real Tuning Optional 0.0 Tuning reset count -
Constant
FFLG - Variable Required - Input (digital); Freeze LD, LP

flag
RSET - Variable Required - Input (digital); Reset LD, LP
flag
RUN - Variable Required - Input (digital); Run LD, LP
flag
FOUT - Variable Required - Output (analog); LA
frozen value
452 OW351_R1100
5.92 RESETSUM
Function
IF TRST  0
THEN OUT = TRST
IF RUN = TRUE
THEN TEMP = OUT + (GAIN x IN1)
IF FFLG = TRUE
THEN FOUT = TEMP
IF RSET = TRUE
THEN OUT = RCNT
ELSE
OUT = TEMP
where:
TEMP = local, temporary, real variable
OW351_R1100 453
5.93 RLICONFIG
5.93 RLICONFIG
Description
The RLICONFIG algorithm is used to send data constant information to the Loop Interface card. If
the data stored in the card versus the data stored in the algorithm is different, then the algorithm
sends the information in the algorithm to the card. The algorithm supports tuning either the
Control Defined Process Variable, the Setpoint or Output/Drive, Analog Input 1, or Analog Input 2
sections of the Loop Interface card.
The optional STAT output point contains the status of the Loop Interface card. The following
conditions apply:
 If bit 0 is true, then the algorithm cannot communicate with the card.
 If bit 1 is true, the algorithm is configuring the setpoint section.
 If bit 2 is true, the algorithm is configuring the process variable section.
 If bit 3 is true, the algorithm is configuring the electric drive section.
 If bit 4 is true, the algorithm is configuring the analog input 1 section.
 If bit 5 is true, the algorithm is configuring the analog input 2 section.
Functional Symbol
FI E L D RE C O R D
CARD X4 - Byte Data Init Required 1 PCI card number -
HWAD B2 - Integer Data Init Required 0 Card hardware -

address
TYPE X1 - Byte Data Init Required Setpoint Section to -

configure. The
choices are:
 Setpoint
 CTLR_PV
 Drive
 Analog
ATYP X9 - Byte Data Init Required AI1 Analog point
section to
configure:
AI1
AI2
454 OW351_R1100
5.93 RLICONFIG
FI E L D RE C O R D
PCST X2 -Byte Data Init Required 25 Setpoint seconds -

for full scale
TIST X3 - Byte Data Init Required 4 Setpoint percent -
change
TPST R1 - Real Data Init Required 100 Setpoint top of -
scale
BTST R2 - Real Data Init Required 0 Setpoint bottom -
of scale
EUST AJ - ASCII Data Init Required PCT Setpoint -

engineering units
TPPV R3 - Real Data Init Required 100 Process variable -
AI1, AI2 top of
scale
BTPV R4 - Real Data Init Required 0 Process variable -
AI1, AI2 bottom
of scale
EUPV AK - ASCII Data Init Required PCT Process variable -
AI1, AI2
engineering units
FINE G0 - Integer Data Init Required 1 Fine deadband -
CRSE G1 - Integer Data Init Required 5 Coarse -

deadband
FIN10 R5 – Data Init Required 0.0 Fine deadband -
Integer with tenths for
deadbands
smaller than 1.
FIN10 is used
instead of FINE if
FINE is
configured as
non-zero
CRS10 R6 – Data Init Required 0.0 Coarse -

Integer deadband with
tenths for
deadband
smaller than 1.
CRS10 is used
instead of CRSE
if CRSE is
configured as
non-zero
SLOW G2 - Integer Data Init Required 771 Slow raise/lower -
pulse on/off
(See note below.)
FAST G3 - Integer Data Init Required 65280 Fast raise/lower -
pulse on/off
(See note below.)
OW351_R1100 455
5.93 RLICONFIG
FI E L D RE C O R D
PCNT X5 - Byte Data Init Required 4 Narrow band -

percent change
TIME X6 - Byte Data Init Required 25 Seconds for full -
scale
PRAT X7 - Byte Data Init Required 3 Priority runback -
rate
CTYP X8 - Byte Data Init Required 1 Conversion Type -
(Valid choices
are 1 - 6)
COE00 S1 -Real Data Init Required 0 Coefficient 0 -

COE09 T1 -Real Data Init Required 0 Coefficient 9 -

COE13 T5 - Real Data Init Required 0 Coefficient 13 -
ENBL - Variable Optional - Enable flag LD, LP
STAT - Variable Optional - Status of the RLI LP

card
Note: The slow/fast, raise/lower pulse on/off times for electric drive signals (low byte = off time;
high byte = on time) are in units of 0.1 or 0.004 seconds.
Two ranges of value (0.1 or 0.004 second resolution) are available for the electric drive slow/fast
action pulse on/off values.
For 0.1 second resolution, byte values in the range of 0 to 127 (00 to 7FH) are used. For
example, 03H represents a 0.3 second pulse time (3 x 0.1).
For 0.004 second resolution, byte values in ranges 128 to 255 (80 to FFH) are used to represent
the range 0 to 127. For example, 83H represents a 0.012 second pulse time (3 x 0.004).
456 OW351_R1100
5.94 RPACNT
5.94 RPACNT
Description
The RPACNT algorithm reads the pulse count from the Ovation Pulse Accumulator card. The
algorithm uses the hardware address in the OUT point to access the Ovation Pulse Accumulator
card.
When IN1 is TRUE, the algorithm reads the pulse count from the card, resets the counter to zero
and stores the pulse counts in OUT. Conversion may be done on the pulse value before the pulse
count is stored in the OUT point. A linear conversion, if chosen, is taken from the CV, 1V and 2V
of the OUT point. For example, consider the case in which the input is a count of contact closures
from a watt hour meter. The number of megawatt hours per pulse can be accounted for in the
coefficients that are calculated as part of the point record. For example, to get the megawatt
hours per hour, the rate would be:
PULSES KWH MWH MIN MWH

3 * 10 * * 60 = 1.8
MIN PULSE 1000 KWH HR HR
The FOUT point contains accumulated pulse count until the reset flag (RSET) is TRUE. If IN1 and
RSET are TRUE, then FOUT contains the pulse count read from the card.
Functional Symbol
FI E L D RE C O R D
IN1 - Variable Required - Input, read trigger of LD, LP

the RPA card (digital)
RSET - Variable Optional - Input to reset count LD, LP

(digital)
OUT - Variable Required - Output value from LA
RPA card (analog)
FOUT - Variable Optional - Accumulated count LA

output value (analog)
OW351_R1100 457
5.95 RPAWIDTH
5.95 RPAWIDTH
Description
The RPAWIDTH algorithm reads the pulse width from the Ovation Pulse Accumulator card. (See
Ovation I/O Reference Manual.) The algorithm uses the hardware address in the OUT point to
access the Ovation Pulse Accumulator card. If there is a hardware error, the OUT is set to BAD
quality.
Functional Symbol
FI E L D RE C O R D
OUT - Variable Required - Pulse Width LA

output (analog)
458 OW351_R1100
5.96 RSRSTATUS
5.96 RSRSTATUS
Description
The RSRSTATUS algorithm performs the following:
 Displays the status register and command register for the Ovation Servo Driver (RSR) card.
 Calibrates Channel 1 and Channel 2 of the RSR card using a project-specific graphic
(diagram 8799) instead of using the RSR serial port.
 Uploads and downloads configurable parameters used by the RSR card. (See Ovation I/O
Reference Manual.)
If a point is assigned to the ENBL input, and the point is TRUE, then the STAT1, STAT2, and
CMD outputs are updated. If ENBL is FALSE, then the last value of STAT1, STAT2, and CMD is
retained.
Note: Use the RSRSTATUS algorithm only with E or greater level of RSR firmware.
Functional Symbol
Figure 15: Functional symbol
Calibration Commands
There are three different types of calibrations that can be done to the valve:
 0% or Low Calibration command - moves the actuator until the 0% position is re-
established. The feedback gain is not re-established.
 100% or High Calibration command - moves the actuator until the 100% position is re-
 Full Calibration command - moves the actuator until both the 0% and 100% positions are
re-established. It also re-establishes the feedback gain.
During the travel sequence, the actuator moves the valve at a programmable rate. While the
Valve Positioner is traveling, the graphic displays and continuously updates the current voltage
value based on the position. There is also a Clear Calibration command that may be used if the
calibration command is no longer desired.
The UTYP parameter can be configured to allow the constant value to be automatic ally uploaded
after any calibration command.
OW351_R1100 459
5.96 RSRSTATUS
Upload Command
The upload command is used to retrieve the constant values currently stored in the RSR card
memory. When the upload command is executed, the X3 value is changed and the RSR card is
commanded to send the current values stored in its memory to the 32-bit real number fields of the
algorithm record. The standard graphic then displays the values in these selected algorithm
record fields for the user when the upload is finished. Note these values can only be uploaded
when the RSR card is in local or normal mode.
Note: For the Ovation 3.5 release and later, the UPLOAD operation can change the OutputMin
and OutputMax values maximally about +/-2 but only one time. For example, if you set
OutputMax=9000, this value will be changed to 8999 after download and upload operations and
will not be changed until you type a new value. This property is related to a numerical rounding
issue and the fact that the RSR card tunes parameters as a short unsigned INT.
Download Command
The download command is used to update the constant values currently stored in the RSR Card
memory. When the download command is requested, the X3 field is changed, and the values
entered into the graphic are stored in the 32-bit real number fields of the algorithm record. Then
the values in the selected fields of the algorithm record are written to the RSR memory. Note
these values can only be downloaded when the RSR card is in local or normal mode.
The DTYP parameter can be configured to automatically download the constant values when the
RSR card is replaced or reseated in the slot.
Interface Information
The calibration commands are sent to the X3 field in the algorithm record.
Command description
C AL I B R AT E CO MM AN D C O MM AN D DE S C R I P TI O N
0 No Command.
1 Channel 1 Calibrate 0%.
2 Channel 1 Calibrate 100%.
3 Channel 1 Full Calibration.
7 Clear Calibration Request.
8 Upload Request.
9 Download Request.
11 Channel 2 Calibrate 0%
12 Channel 2 Calibrate 100%
13 Channel 2 Full Calibration
15 Channel 1 Normal Mode
16 Channel 1 Local Mode
460 OW351_R1100
5.96 RSRSTATUS
17 Channel 1 Raise 0.5%
18 Channel 1 Lower 0.5%
19 Channel 2 Normal Mode
20 Channel 2 Local Mode
21 Channel 2 Raise 0.5%
22 Channel 2 Lower 0.5%
24 Display Feedback Voltage
25 Display DAC Setting
As the commands are being executed, messages are displayed on the graphic by the status
value in the X5 field of the algorithm record.
Status description
S TATU S D E S C R I P TI O N
0 No Message.
1 Calibration in Progress.
2 Poor Calibration.
3 Calibration Time-out.
4 Upload Error.
5 Download in Progress.
6 Download Error.
7 Download Time-out.
8 Channel 1 Not Ready.
11 Command cannot be processed.
12 Channel 2 Not Ready.
RSR CALIBRATION DIAGRAMS
There is one calibration diagram linked to an RSR module:
 Diagram 8799 = Project-specific diagram.
OW351_R1100 461
5.96 RSRSTATUS
Accessing Diagram 8799
In order to perform tuning calibrations on the RSR module, you need to use a tuning diagram
such as diagram 8799. This diagram is accessed from a custom graphic. You can use the
Ovation Graphics Builder to create code that will call the 8799 calibration diagram. Refer to the
Ovation Graphics Builder User Guide for more information on building Ovation graphics.
The following is an example of calling the 8799 diagram from diagram 1000 by using a standard
OL_BUTTON command in Ovation Graphics Builder:
OL_BUTTON 6868 6044 HORZ SQUARED TEXT_LABEL VECTOR 137 438 1 "RSR
TUNING" EXEC_POKE 7 2 6 0 5 \RSRSTAT\ ID \RSRSTAT\ ID 3 83 3 117 8799 20 0 0 0 0
15 \RSR-DMD1\ ID \RSR-POS1\ ID\RSR-INTGV1\ ID \RSR-DMD2\ ID \RSR-POS2\ ID \RSR-
INTGV2\ ID \RSR-STAT1\ ID \RSR-STAT2\ ID \RSR-CMD\ ID \MASTATION1\ ID
\MAMODE1-MODE\ ID \MASTATION2\ ID \MAMODE2-MODE\ ID \RSR-OUT1\ ID \RSR-
OUT2\ ID
* RSRSTAT - RSRSTAT LC point

* RSR-DMD1 - RSR IO point - channel 5
* RSR-POS1 - RSR IO point - channel 1
* RSR-INTGV1 - RSR IO point - channel 3
* RSR-DMD2 - RSR IO point - channel 6
* RSR-POS2 - RSR IO point - channel 2
* RSR-INTGV2 - RSR IO point - channel 4
* RSR-STAT1 - RSRSTAT STAT1 output point
* RSR-STAT2 - RSRSTAT STAT2 output point
* RSR-CMD - RSRSTAT CMD output
* MASTATION1 - MASTATION1 LC point
* MAMODE1-MODE - MAMODE1 - MODE output point
* MASTATION2 - MASTATION2 LC point
* MAMODE2-MODE - MAMODE2 - MODE output point
* RSR-OUT1 - RSRSTAT OUT1 output point
* RSR-OUT2 - RSRSTAT OUT2 output point
462 OW351_R1100
5.96 RSRSTATUS
Diagram 8799
Diagram 8799 consists of three main sections: Common, Channel 1 and Channel 2:
 Common section contains configuration pushbuttons and tuning constant entry fields common
for both channels.
 Channel 1 section contains configuration pushbuttons, tuning constant entry fields and
message lines used only for Channel 1.
 The Channel 2 section contains configuration pushbuttons, tuning constant entry fields and
message lines used only for Channel 2.
Figure 16: Servo Driver tuning diagram
OW351_R1100 463
5.96 RSRSTATUS
Common Section of 8799 Diagram

Calibration is performed by using command pushbuttons and entering tuning constants in the
entry fields. Some of the pushbuttons are accompanied with rectangular confirmation boxes –
when the function is selected, the color changes from black to yellow.
The pushbuttons and entry fields that are used to set configuration values are described in the
following table.
Calibration Fields in Common Section of 8799 Diagram
B U TTO N OR EN TR Y FI E L D DE S C R I P TI O N
Upload button Read data command given to RSR module.
Download button Write data command given to RSR module.
Clear EF’s button Clear diagram entry field command.
INTEGRAL button DAC is displayed in RawVoltage and OutputValue for both channels -
the yellow rectangle confirms selection.
LVDT button Feedback voltage is displayed in RawVoltage and OutputValue for
both channels - the yellow rectangle confirms selection.
PROPOR button Proportional output option flag to 1 - the yellow rectangle confirms
selection.
REGUL button Proportional output option flag to 0 - the yellow rectangle confirms
selection.
REDUND button Redundant LVDT option flag to 1 - the yellow rectangle confirms
selection.
SINGLE button Redundant LVDT option flag to 0 - the yellow rectangle confirms
selection.
INPLACE button Fail-in-place flag to 1 - the yellow rectangle confirms selection.
TOZERO button Fail-in-place flag to 0 - the yellow rectangle confirms selection.
CASCADE button Cascade flag to 1- the yellow rectangle confirms selection.
NORMAL button Cascade flag to 0 (normal configuration) - the yellow rectangle

confirms selection.
contingencyTime entry field The time in milliseconds - if the error between target position and
actual position exceeds contingency for this amount of time, then the
condition is reported to the Controller.
posErrorRetreat entry field The output will not retreat until ABS| posFB - TargetPos|
<posErrorRetreat.
retreatRate entry field Volts per second rate of output retreat.
retreatHoldT entry field The time in milliseconds - retreat occurs after this time has expired,
and (ABS|Target-Feedback| < posErrorRetreat).
464 OW351_R1100
5.96 RSRSTATUS
Channels 1 and 2 of 8799 Diagram
Calibration is performed by using command push buttons and entering tuning constants in the
entry fields. Some of the push buttons are accompanied with rectangular confirmation boxes –
when the function is selected the box color is changed. The full, zero hot and t op hot calibration
sequences can be started selecting proper push buttons. The calibration sequence can be
stopped at any time. It is not possible to start calibration sequence for both channels
simultaneously. When the calibration of any channel is in progress DOWNLOAD, UPLOAD,
CLEAR EF’s, OUTPUT, LVDT push buttons are disabled.
When the calibration is finished, the tuning of the PI position control should be performed. It can
be done in RSR local or normal mode. When local mode is selected the only way to change the
valve position demand is to press UP or DOWN push buttons. Normal mode is selected by
pressing DPU push button and the valve position demand is changed by pressing up/down arrow
push buttons, or entering demand in DEO entry field.
The following push buttons and entry fields are used to set the values of important configuration.
Calibration Fields in Channel Sections of 8799 Diagrams
0% button Calibrate zero% - the yellow rectangle confirms selection.
100% button Calibrate 100% - the yellow rectangle confirms selection.
FULL button Full Calibration - the yellow rectangle confirms selection.
STOP button Stop Calibration - the yellow rectangle confirms selection.
UP button Raise - the yellow rectangle confirms selection.
DOWN button Lower - the yellow rectangle confirms selection.
DPU button RSR channel 1(2) to normal mode - the green rectangle confirms
selection.
LOC button RSR channel 1(2) to local mode - the yellow rectangle confirms selection.
AUT button Mastation channel 1(2) to auto mode - the blue rectangle confirms
selection.
MAN button Mastation channel 1(2) to manual mode - the red rectangle confirms
selection.
up arrow push button Raise Mastation channel 1(2) output.
down arrow push button Lower Mastation channel 1(2) output.
DEO button Mastation channel 1(2) output digital entry.
piGain entry field PI Controller gain outside of deadband.
piResetT entry field PI Controller reset time outside of deadband.
demodGain entry field The A/D converter gain to achieve a voltage range representing 0 to 100
%.
errorDbS entry field When the absolute value of the difference between the target position and
the actual position is less than this value, the valve is considered to be
stable.
OW351_R1100 465
5.96 RSRSTATUS
errorDbF entry field When the absolute value of the difference between the target position and
the actual position is greater that this value, the valve is considered to be
in motion.
piGainDb entry field PI Controller gain inside deadband.
piResetTDb entry field PI Controller reset time inside deadband.
Outoffset entry field RSR output offset for the proportional mode.
iLimit entry field Integration limit - 100% no limit, 0% no integration.
calRateCh1(2) entry field Automatic calibration demand change rate – channel 1(2).
DIRECT entry field PI mode.
seatLimit entry field When target valve position is equal to or less than this value, seating
action controls the output.
backSeatLimit entry field When the target valve position is equal to or greater than this valu e,
backseating action controls the output.
exitSeatVal entry field When the RSR is seating the valve, then decides to retreat, this is the
output in mV to which the output goes.
exitBkSeatVal entry field When the RSR is backseating the valve, then decides to retreat, this is the
output in mV to which the output goes.
Calzero entry field The converted to decimal hexadecimal A/D converter reading for the 0%
position.
Calhndrd entry field The converted to decimal hexadecimal A/D converter reading for the 1 00%
position.
Contingency entry field The difference between Servo Driver target position and actual
Position.
The following display fields in the bottom of the 8799 diagram are used to display the status and
calibration of the RSR module.
Display Fields in Channel Sections of 8799 Diagrams
FI E L D DE S C R I P TI O N
RSR Status Options are:

 LOCAL mode
 Normal MANUAL
 Normal AUTO
Message line Options are:
 Retreat in progress
 Retreat is disabled
 Contingency
466 OW351_R1100
5.96 RSRSTATUS
FI E L D DE S C R I P TI O N
Calibration status Options are:

 Not in calibration
 CAL0 in Progress
 CAL100 in Progress
 FULL Calibration in Progress
 Calibration is Finished.
General Messages Messages that appear in the bottom of the 8799 diagram.
FI E L D RE C O R D

Number
PCI X4-Byte Data Init. Required 1 PCI Card Number -
(1 or 2)
HWAD B2-Integer Data Init. Required 0 Card Hardware -
Address
UTYP X6-Byte Data Init. Required YES Automatically upload -
after a Calibration.
Bit 0
 YES (Default)
 NO
DTYP X6-Byte Data Init. Required YES Automatically -
download
Bit 1
 YES (Default)
 NO
ENBL - Variable Optional - Enable Flag (digital) LD,LP
CC - Variable Optional - Cascade close LD, LP

command
CCF - Variable Optional - Cascade close freeze LD, LP

tracking
CCV - Variable Optional - Cascade close value LA
IDMD1 - Variable Optional - Channel 1 demand LA

input
IDMD2 - Variable Optional - Channel 2 demand LA
input
STAT1 - Variable Required - RSR Status register LP
(packed)
STAT2 - Variable Required - RSR Status register 2 LP

(packed)
OW351_R1100 467
5.96 RSRSTATUS
FI E L D RE C O R D
CMD - Variable Optional - RSR Command LP

register (packed)
ODMD1 - Variable Optional - Channel 1 demand LA

output
ODMD2 - Variable Optional - Channel 2 demand LA

output
OUT1 - Variable Optional - Channel 1 output value LA
OUT2 - Variable Optional - Channel 2 output value LA
X8 X8 – Byte Data Init Required 0 Allows you to specify if -

Bit 0 the Output Min/Max
parameter should
accept real or integer
numbers:
 0 – INTEGER
 1 – REAL
468 OW351_R1100
5.97 RUNAVERAGE
5.97 RUNAVERAGE
Description
The RUNAVERAGE algorithm performs a running average calculation on a number of samples

collected at a sampling interval time. The input (IN1) is sampled periodically as specified by the
user from the Number of Units and Units of Time fields. Any decimal part in the Number of Units
field is ignored. If the time specified is less than the loop time, the input is sampled every loop.
Otherwise, the input is sampled on the first loop after the specified number of time boundaries
have elapsed.
The output, which is calculated every loop, is the average of the last N samples of the input,
where N is 8 or less. Thus, the time period for the average is the product of t he sampling interval
time and the number of samples. If the quality of the input is BAD, that value of the input is not
included in the calculation. If the quality of the samples for a given period is BAD, then the output
value remains unchanged, but the quality is set BAD. During initial operation before N samples
exist, the output that is calculated is based on the available samples.
The values of all IN1 samples are checked for invalid real numbers. If an IN1 sample value is
invalid, the stored, internal quality of that IN1 is set to BAD. Only sample values with GOOD,
FAIR, and POOR quality are used to calculate the value of OUT; the quality of OUT is set
according to the rules listed in the Function section of this description.
At any given time, the output is the average of N samples, made up of the most current sample
and the previous N-1 samples. Every sampling time, the oldest sample is discarded and replaced
with a new sample.
Functional Symbol
FI E L D RE C O R D

Number
TIME R1-Real Tuning Optional 0.0 Number of units -
Constant
OW351_R1100 469
5.97 RUNAVERAGE
FI E L D RE C O R D
UNIT X1-Byte Data Init. Optional 0 Units of time -

0 = tenths of a
second
1 = seconds
2 = minutes
3 = hours
4 = days
NUM R2-Real Tuning Required 0 Number of samples -
Constant to be averaged (1
through 8)
Function
The quality of the output is as follows:
 On the first pass: BAD

 If all samples during the period are BAD: BAD
 If less than half the samples are GOOD: POOR
 If more than half the samples are GOOD: FAIR
 If all samples during the period are GOOD: GOOD
470 OW351_R1100
5.98 RUNTIME
5.98 RUNTIME
Description
The RUNTIME algorithm counts long-lasting service times of devices. This algorithm consists of
two counters; run time (RTIME) and number of starts (NUMST).
Functional Symbol
Algorithm Activation (START)
The algorithm is activated when you set the START input. When this occurs, the algorithm begins
to increment the RTIME counter and also increments the NUMST parameter by 1. The START
input must remain set to activate the algorithm. If the START input is unset, the algorithm will stop
incrementing the RTIME counter.
Reset Counters (TRST and SRST)
You can reset the algorithm through the time reset (TRST) and number of starts reset (SRST)
inputs. Resetting the algorithm through these inputs will set both the RTIME and the NUMST
counters to 0 and qualities to GOOD.
There are several reset options available through the tuning parameters: time reset option
(TROP) and starts reset option (SROP). These options are summarized in the following table:
Parameters
TU N I N G P AR AM E TE R V AL U E N AME RE S E T S E L E C TE D
0 (default) RST_ON xRST input = 1 resets counter.

1 RST_OFF xRST input = 0 resets counter.
2 RST_CH1 xRST input change 0->1 resets counter.
3 RST_CH0 xRST input change 1->0 resets counter.
4 RST_CHG xRST any input change resets counter.
OW351_R1100 471
5.98 RUNTIME
Run Time (RTIME)
The run time (RTIME) parameter is determined by the difference between the Controller time in
the current loop and the Controller time in the previous loop and added to an internal counter. The
internal counter is a 32-bit integer number. This allows counting up to 2^32 = 4,294,967,296
seconds which is equivalent to 136 years or 1,193,046 hours. For simplicity, the algorithm uses a
maximum of 999,999 hours at which time the counter will not increment any further. The
maximum value is equivalent to more than 100 years. The number of seconds is recalculated to
hours represented by a floating value and is reflected in the RTIME algorithm output.
Number of Starts (NUMST)
The number of starts (NUMST) parameter is determined by the amount of times the START input
transitions from 0 to 1. This counter is reflected in the number of starts (NUMST) output and is
internally stored in the algorithm. The maximum number of starts is 999,999, at which time the
counter will not increment any further.
Splitting time values
The algorithm supports splitting the time represented in RTIME into hours, minutes, and seconds.
Each part is reflected in optional outputs; run hours (RHRS), run minutes (RMIN), and run
seconds (RSEC).
Calculations are performed according to the following equations:
RHRS = int (RTIME / 3600)
RMIN = int ((RTIME mod 3600) / 60)
RSEC = RTIME mod 60
Manually updating counters
A manual update of either the RTIME counter or the NUMST counter can be achieved by
changing either the incremental tuning value for the time parameter (TTIM) or the incremental
tuning value for the number of starts parameter (TNST) respectively. Changing these parameters
will cause the algorithm to add the value entered to the current RTIME or NUMST value. The
algorithm will then zero out each field (TTIM and/or TNST) and update the current incremental
tuning value for time (CTTIM) or current incremental tuning value for number of starts (CTNST)
respectively. The CTTIM and CTNST fields store the user-entered values for future references.
If you want to start the algorithm with either the TTIM or TNST values, you must first reset each
counter to zero out the current RTIME and NUMST counters. Then the TTIM and TNST values
can be entered.
Note: Entering a number less than zero or greater than 999,999 will cause the algorithm to
ignore the value and reset the TTIM and TNST fields to zero.
472 OW351_R1100
5.98 RUNTIME
Reconcile Option (RECOP)

The reconcile option allows you to determine how the algorithm initializes its outputs after a clear
and load of both Controllers at the same time.
When the reconcile option is off, the algorithm initializes its outputs to 0 and POOR quality after a
clear and load of both Controllers. When the reconcile option is on, the algorithm will initialize its
outputs using the previously reconciled values in the RTIME - R1 and NUMST - G3 fields and set
all outputs to GOOD quality. The initialized values will also be stored in the CTTIM and CTNST
fields for future reference. When the algorithm is started, it begins counting from the initialized
values.
Output Point Quality
If the RECOP option is off, any time a loaded Controller is restarted without an operable partner
drop (and with the INITP option set to OFF), the RTIME and NUMST are initialized to 0, and the
outputs will be marked with POOR quality. POOR quality indicates that the value is not
trustworthy because the output values will be initialized to 0. The qualities are changed to GOOD
after a reset by the time reset (TRST) and/or start reset (SRST) inputs. Also, updating the TTIM
field will set the RTIME quality to GOOD and updating the TNST field will set the NUMST quality
to GOOD.
Initialize from Saved Points Option (INITP)
If the INITP option is ON, the algorithm will initialize its outputs from the NUMST and RTIME
output points that are periodically saved by the Controller. This allows the RTIME and NUMST
values to persist in cases of dual power failures to a Controller pair. The saved point values do
not persist when both Controllers are cleared at the same time; however, you may use the
RECOP option described above. If both the INITP and RECOP option are ON, the algorithm will
initialize its outputs using whichever value is greater.
Note: You must separately configure the RTIME and NUMST points to be “Periodic save” using
the Ovation Developer Studio. The resolution of the INITP option is limited by the Controller
parameter “Save Variables @ Interval (sec)” defined by the Ovation Developer Studio. See
Ovation Developer Studio User Guide for more information on configuration.
SID Storage
OW351_R1100 473
5.98 RUNTIME
FI E L D RE C .
Inputs:
START -- Variable Required -- Algorithm activation. LD, LP
TRST * X4 Variable Optional -- Reset run timers. LD, LP
SRST * X5 Variable Optional -- Reset number of LD, LP

starts.
Outputs:
RTIME R1 - Value Variable Optional -- Total run time in LA

B0 - SID hours (floating point).
RHRS G0 - Value Variable Optional -- Run time in hours LA
B1 - SID (integer).
RMIN G1 - Value Variable Optional -- Run time in minutes LA
B2 - SID (integer).
RSEC G2 - Value Variable Optional -- Run time in seconds LA
YU - SID (integer)
NUMST G3 - Value Variable Optional -- Number of device LA
B4 - SID starts.
Parameters:
TROP X1 Tuning Required 0 Time Reset Option: --

Constant  0 (default) -
RST_ON
 1 - RST_OFF
 2 - RST_CH1
 3 - RST_CH0
 4 - RST_CHG
SROP X2 Tuning Required 0 Starts Reset Option: --
Constant  0 (default) -
RST_ON
 1 - RST_OFF
 2 - RST_CH1
 3 - RST_CH0
 4 - RST_CHG
RECOP X3 Data Init. Required 0 Reconcile option: --
 0 = Off
 1 = On
TTIM R2 Tuning Required 0 Incremental tuning --
Constant value for time (in
hours).
474 OW351_R1100
5.98 RUNTIME
FI E L D RE C .
TNST G4 Tuning Required 0 Incremental tuning --

Constant value for number of
starts.
CTTIM R3 Alg. Init. Required 0 Current incremental --
tuning value for time.
CTNST G5 Alg. Init. Required 0 Current incremental --
tuning value for
number of starts.
INITP X4 Data Init. Required 0 Initialize from saved --
points option:
 0 = OFF
 1 = ON
* The asterisk indicates that this is a command field, not a feedback field. A command field can be used
as a user-interface to the algorithm. It drives the algorithm to perform a function.
OW351_R1100 475
5.99 RVPSTATUS
5.99 RVPSTATUS
Description
The RVPSTATUS algorithm performs the following:
 Displays the status register and command register for the Ovation Valve Positioner (RVP)
Card.
 Calibrates the RVP card using a standard graphic (diagram 8719) instead of using the RVP
serial port.
 Uploads and downloads configurable parameters used by the RVP card. (See Ovation I/O
Reference Manual.)
If a point assigned to the ENBL input and point is TRUE, then the STAT and CMD outputs are
updated. If ENBL is FALSE, then the last value of STAT and CMD is retained.
Functional Symbol
Calibration Commands
There are four different types of calibrations that can be done to the valve:
 0% or Low Calibration command - moves the Valve Positioner until the 0% position is re-
 100% or High Calibration command - moves the Valve Positioner until the 100% position is
re-established. The feedback gain is not re-established.
 Full Calibration command - moves the Valve Positioner until both the 0% and 100%
positions are re-established. It also re-establishes the feedback gain.
 Null-Point Calibration command - moves the Valve Positioner to the electrical null point of
the LVDT. The Null-Point Calibration can be requested at the same time as the Full
Calibration. If this is done, the Positioner moves through the sequences of the full cal ibration,
but stops at the null point when encountered.
When the calibration command is executed, the controlling MASTATION enters manual mode
and tracks the position demand feedback. During the travel sequence, the Valve Positioner
moves the valve at a programmable rate. While the Valve Positioner is traveling, the graphic
displays and continuously updates the current voltage value based on the position. There is also
a Clear Calibration command that may be used if the calibration command is no longer desired.
476 OW351_R1100
5.99 RVPSTATUS
Upload Command
The upload command is used to retrieve the constant values currently stored in the RVP Card
memory. When the upload command is executed, the X3 value is changed and the RVP Card is
commanded to send the current values stored in its memory to the 32-bit real number fields of the
algorithm record. The standard graphic then displays the values in these selected algorithm
record fields for the user when the upload is finished. Note these values can only be uploaded
when the RVP card is in local or normal mode.
Download Command
The download command is used to update the constant values currently stored in the RVP Card
memory. When the download command is requested, X3 field is changed, and the values entered
into the graphic are stored in the 32-bit real number fields of the algorithm record. Then the values
in the selected fields of the algorithm record are written to the RVP memory. Note these values
can only be downloaded when the RVP card is in local or normal mode.
Interface Information
The calibration commands are sent to the X3 field in the algorithm record.
Calibrate command
0 No Command.
1 Calibrate 0%.
2 Calibrate 100%.
3 Full Calibration.
4 Go to Null Point Calibration.
7 Clear Calibration Request.
8 Upload Request.
9 Download Request.
As the commands are being executed, messages are displayed on the graphic by Status Value in
the X5 field of the algorithm record.
Status description
0 No Message.
1 Calibration in Progress.
2 Poor Calibration.
3 Calibration Time-out.
4 Upload Error.
OW351_R1100 477
5.99 RVPSTATUS
5 Download in Progress.
6 Download Error
7 Download Time-out
8 RVP Card Not Ready.
FI E L D RE C O R D

Integer Number
PCI X4-Byte Data Init. Required 1 PCI Card Number -
(1
or 2)
HWAD B2- Data Init. Required 0 Card Hardware -
Integer Address
ENBL - Variable Optional - Enable Flag (digital) LD,LP
STAT - Variable Required - RVP Status register LP
(packed)
CMD - Variable Optional - RVP Command LP

register (packed)
478 OW351_R1100
5.100 SATOSP
5.10 0 SATOSP
Description
The SATOSP algorithm transfers one analog value to a packed point record for use by
programmable controllers.
The analog point record value field is converted to an integer and stored in the packed digital
value field. Conversion is done by rounding off fractional values less than 0.50 to zero and
fractional values greater than or equal to 0.50 to the next highest integer. If the value of the
analog point record is less than the smallest integer (-32767), or greater than the largest integer
(32767), the minimum or maximum integer value is used.
The bit pattern used to store negative numbers is the sign and magnitude method.
If the quality of the analog point record is BAD, or if the value of the analog point is an invalid
number, then the packed point value remains at its last valid value. The quality of the input is not
Functional Symbol
FI E L D RE C O R D
IN - Variable Required - Input (analog) LA
PACK - Variable Required - Output (packed) LP
OW351_R1100 479
5.101 SELECTOR
5.10 1 SELECTOR
Description
The SELECTOR algorithm transfers between N analog inputs. For the SELECTOR algorithm, the
output is equal to one of N analog inputs, where N is an integer less than eight. The input
selected is based on a binary address formed by three digital inputs per the table. If address 000
or an address greater than N is selected, the output signal is zero.
Input states
Digital Input States
S E L E C TE D DIN1 DIN2 DIN3

I N P U T NO .
None 0 0 0
1 1 0 0
2 0 1 0
3 1 1 0
4 0 0 1
5 1 0 1
6 0 1 1
7 1 1 1
The value of the selected input is checked for invalid real numbers. If the input value is invalid, the
output value is invalid and the quality of the output is set to BAD. Otherwise, the quality of the
selected input is propagated to the output.
Functional Symbol
480 OW351_R1100
5.101 SELECTOR
FI E L D RE C O R D

number
NMIN X1-Byte Data Init. Required 0 Number of inputs -
IN1 - Variable Optional - Input (analog) LA
•
•
•
IN7
DIN1 - Variable Required - Input (digital); LD, LP
Input Address 1

Input Address 2
Input Address 3
OW351_R1100 481
5.102 SETPOINT
5.10 2 SETPOINT
Description
The SETPOINT algorithm performs a manual loader function. The algorithm provides an interface
to the Control Builder or Operator Station diagram. Interface to the hard setpoint portion of the
Ovation Loop Interface (LI) card may be initialized. If the LI hardware address is initialized, the
algorithm reads the setpoint stored on the LI setpoint counter to use as its output value. If the LI
or hardware address is not initialized, the algorithm uses the last output value as its output value.
Note: The rate of change is constant in Signal Diagrams regardless of the settings for the
algorithm parameters.
Functional Symbol
The output of this algorithm may be increased and/or decreased by the SLIM station or the
Operator's Soft Station diagram.
It continually checks the Set Point Increase/Decrease function keys from the Operator's Station
for increase/decrease requests for the setpoint output. If requests are received from both the hard
and soft stations at the same time, the station contacts override the Operator's Keyboard keys.
On power-up or reset of the Controller, the output is the initial value of the algorithms output
(default value = 0.0) if the LI is not initialized. Otherwise, the output is the current value stored on
the LI setpoint counter.
If the LI card is selected in the TYPE algorithm field and the Controller is reset, powered-up or
fails, the setpoint is read from the LI card and used initially in the OUT field of the algorithm. This
reports the status of the field device before any action is taken by either the algorithm or the
operator.
The interface keys of the Operator's Keyboard are:
Key usage
KE Y US E
Set Point Increase Function Key (Control Up Arrow) Raise the output
Set Point Decrease Function Key (Control Down Arrow) Lower the output
Note: If the top and bottom scales are equal, the high limit flag is set and the output value is
equal to the top scale.
If the algorithm is told to track and the track input is invalid, the track request is ignored and the
drop is placed into alarm.
482 OW351_R1100
5.102 SETPOINT
If the LI hardware address is initialized, this value is written to the setpoint counter on the
specified card. If the algorithm is operating with an LI, and the LI card is in Local mode, the output
of the algorithm cannot be changed from the Operator Station. In this case, the output of the
algorithm can be changed from the SLIM station only.
If SETPOINT is to write the setpoint value to the LI card, then changes to the setpoint value (that
is, tracking, Control Builder or Operator Station raise/lower requests, and so forth) are
implemented as described previously.
The SETPOINT algorithm monitors the LI card for any raise and lower requests from the SLIM.
Raise/lower requests from the SLIM override any other setpoint change requests received by this
algorithm (that is, tracking, Operator Station raise/lower requests, and so forth). If there are no
SLIM requests, then the setpoint value is changed as described previously. The setpoint value is
only written to the output point.
Tracking Signals
to the information found in the analog input signal TRIN:
Bit description
BI T D E S C R I P TI O N A C TI O N TOUT S I G N AL
16 Track Implemented Not used

OW351_R1100 483
5.102 SETPOINT
The high and low limit flags and tracking signals from the algorithm are output to TOUT for
display. If the LI hardware address is initialized, the quality of OUT is BAD if there are any LI
hardware errors. Otherwise, the quality of OUT is GOOD when not tracking or set to the quality of
the track input variable when tracking.
FI E L D RE C O R D
DIAG LU-Integer Data Init. Required 9 Tuning diagram -

number
Constant the point

Constant the point
PCNT X1-Byte Tuning Required 4 Percent change of -
Constant output in first four
seconds
TIME X2-Byte Tuning Required 25 Number of seconds -
to full scale
CARD X3-Byte Data Init. Required SOFT Card type: -

SOFT = No
hardware interface
RLI = Ovation Loop
Interface card
CNUM X5-Byte Data Init Optional 1 PCI card number -

(1,2)
HWAD B2-Integer Data Init Optional 0 Card Hardware -
Address (see page
3)
variable
TRIN - Variable Optional - Tracking & limiting LA
mode signals and
tracking value;
analog input
variable
TOUT - Variable Required - Mode and Status LA
output signals
484 OW351_R1100
5.103 SIMTIME
5.10 3 SIMTIME
Description
The SIMTIME algorithm is used to set time in the Controller. It is reserved for Emerson use only.
5.10 4 SINE
Description
The SINE algorithm performs a mathematical sine function. The SINE algorithm has one input
to the SINE of the input. The input to this algorithm is in radians. If an input is only available in
degrees, multiply it by 0.01745329 to convert to radians.
If the absolute value of the input greater than 10 18 then the output of the SINE algorithm is invalid
and its quality is set to BAD.
Functional Symbol
FI E L D RE C O R D
Function
OUT = SINE(IN1)
OW351_R1100 485
5.105 SLCAIN
5.10 5 SLCAIN
Description
The SLCAIN algorithm reads up to 16 analog values from a Group 1 QLC or Ovation Link
Controller (LC) card (or redundant pair of Group 1 QLC cards).
Functional Symbol
Primary and Secondary QLCs/LCs
The Hardware addresses of the primary and secondary QLC/LC cards are specified by the PHW
and SHW parameters (if no secondary QLC/LC is used, SHW is set to zero).
Digital inputs PSTA and SSTA define whether the points are to be read from the primary or
secondary QLC/LC, as shown below:
 If PSTA = TRUE, the points are read from the primary QLC/LC (status of SSTA does not
matter).
 If PSTA = FALSE and SSTA = TRUE, the points are read from the secondary QLC.
 If PSTA = FALSE and SSTA = FALSE, the point values are not updated and the points are
assigned BAD quality.
 If PSTA = FALSE and SSTA is not defined, the point values are not updated and the points
are assigned BAD quality.
 If PSTA and SSTA are not defined, the point values are not updated and the points are
Note: Although both PSTA and SSTA are optional parameters, at least one must be defined for
the points to be updated.
486 OW351_R1100
5.105 SLCAIN
Point Data Formats
The FRMT parameter is used to specify the format of the analog point data to be read from the
QLC/LC registers. The four available formats are as follows:
Formats
FRMT * FO R M AT DE S C R I P TI O N
0 Integer Integer value in the range +32767 to -32768. Each

point occupies one data register.
1 Intel Real Floating-point real number. Each point occupies two

data registers.
2 Intel Real with status Status word followed by floating-point real number.
Each point occupies three data registers.
3 Intel Real with quality Status word followed by floating-point real number.
Each point occupies three data registers.
* When the FRMT = 2, the following bits are placed into the 1W field of the analog point record:
Bit 4 - Undefined
Bits 8 and 9 - Quality
Bit 12 - Limit checking off
Bit 13 - Alarm checking off
When the FRMT = 3, only the quality bits 8 and 9 of the 1W field of the analog point record are
updated.
The remaining bits of the 1W field are used for alarm status, operator entry, and Ovation
Network status information. (See Ovation Record Types Reference Manual.)
QLC/LC Data Registers
The point data is retrieved from consecutive QLC/LC data registers, starting at the register
specified by parameter REG1. Depending on the format selected, the total area required for the
16 analog points could be 16, 32, or 48 registers.
The point parameters (OUT1 through OUT16) are associated with consecutive QLC/LC data
registers, even if some points are omitted from the argument list. For example, if REG1 = 4,
FRMT = 1, and point OUT1 is omitted, then OUT2 is read starting at data register 6 (no read is
performed from data registers 4 and 5).
The location from which a given point is read can be calculated using the following formula:
point_address = REG1 + (FRMT + 1) * (point_number - 1)
where:
point_address QLC/LC data register containing the first word of data from the point
point_number 1 for parameter A1, 2 for parameter A2, and so on.
Any point which lies (completely or partially) beyond the end of the 2048 QLC/LC data regi sters is
assigned BAD quality. For example, if REG1 = 2044 and FRMT = 2, only the first point value
(parameter Al) can be obtained.
OW351_R1100 487
5.105 SLCAIN
Analog Point Record Types
If alarm and/or limit checking are to be performed on points read from the QLC/LC, use point
record type Long Analog (LA).
FI E L D RE C O R D
DIAG LU- Data Init Required 11 Tuning diagram -

Integer number
FRMT B0- Data Init. Required 0 QLC/LC data format -
Integer
REG1 B1- Data Init. Required 0 First QLC/LC data -
Integer register
PHW B2- Data Init. Required 0 Primary QLC -
Integer hardware address or
LC address (see
page 3)
SHW YU- Data Init. Required 0 Secondary QLC -
Integer hardware address or
LC address (see
page 3)
CARD X4-Byte Data Init. Required 1 PCI Card Number -
(1,2)
TYPE X1-Byte Data Init Required QLC Interface Card Type: -
 QLC
 RLC
OUT1 - Variable Optional - Input from QLC/LC LA
registers (analog)
•
•
•
OUT16
PSTA - Variable Optional - Primary QLC/LC LD, LP
status input (digital)
SSTA - Variable Optional - Secondary QLC/LC LD, LP

488 OW351_R1100
5.106 SLCAOUT
5.10 6 SLCAOUT
Description
The SLCAOUT algorithm writes up to 16 analog points to a Group 1 QLC or LC card

(or redundant pair of Group 1 QLC cards).
Functional Symbol
The hardware addresses of the primary and secondary QLC/LC cards are specified by the PHW
Digital inputs PSTA and SSTA define whether the points are to be written to the primary or
 If PSTA = TRUE, the points are written to the primary QLC/LC (status of SSTA does not
matter).
 If PSTA = FALSE and SSTA = TRUE, the points are written to the secondary QLC.
 If PSTA = FALSE and SSTA = FALSE, the points are not output.
 If PSTA = FALSE and SSTA is not defined, the points are not output.
 If PSTA and SSTA are not defined, the points are not output.
the points to be output.
Point Data Formats
The FRMT parameter is used to specify the format of the analog point data to be written to the
QLC/LC registers. The three available formats are as follows:
FRMT FO R M AT DE S C R I P TI O N
0 Integer Integer value in the range +32767 to -32768. Each point occupies
one data register.
1 Intel Real Floating-point real number. Each point occupies two data registers.
2 Intel Real with status Status word followed by floating-point real number. Each point
occupies three data registers.
Note that depending on the format selected, each point value occupies between 1 and 3 data
registers.
OW351_R1100 489
5.106 SLCAOUT
The point data is written to consecutive QLC/LC data registers, starting at the register specified by
parameter REG1. Depending on the format selected, the total area required for the 16 anal og
points could be 16, 32, or 48 registers.
The point parameters (A1 through A16) are associated with consecutive QLC/LC data registers,
even if some points are omitted from the argument list. For example, if REG1 = 4, FRMT = 1, and
point A1 is omitted, then A2 is written starting at data register 6 (no data is written to registers 4
and 5).
The location to which a given point is written can be calculated using the following formula:
point_address = REG1 + (FRMT + 1) * (point_number - 1)
where:
point_address QLC/LC data register containing the first word of data from the point.
point_number 1 for parameter A1, 2 for parameter A2, and so on.
No data is written to registers beyond the valid range (0 through 2047). Points which lie partially
beyond the valid range of registers are written to the extent possible; points which lie completely
beyond the valid range of registers are not written. For example, if REG1 = 2044 and FRMT = 2,
only the first point value (parameter Al) can be written.
Timed-Out Points
The TIME parameter determines what action is taken when a received point (to be written to the
QLC/LC) is timed-out. Depending on the selected TIME setting, the point is either not written to
the QLC/LC, or the last received value is written.
TIME is interpreted as a mask of bits to determine the selected setting for each point, as shown
below:
Point IN IN IN IN IN IN IN IN IN IN IN IN IN IN IN IN
16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
TIME bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
 For each point, a value of 0 (zero) in the corresponding bit indicates that the point should not
be written if it is timed-out.
 For each point, a value of 1(one) in the corresponding bit indicates that the last received value
should be written if the point is timed-out.
490 OW351_R1100
5.106 SLCAOUT
FI E L D RE C O R D
DIAG LU- Data Init. Required 12 Tuning diagram -

Integer number
FRMT B0 - Data Init. Required 0 QLC/LC data -
Integer format
REG1 B1 - Data Init. Required 0 First QLC/LC data -

Integer register
PHW B2 - Data Init. Required 0 Primary QLC/LC -
Integer hardware address
(see page 3).
SHW B3 - Data Init. Required 0 Secondary QLC/LC -
(see page 3).
(1, 2)
TYPE X1-Byte Data Init Required QLC Interface Card -
Type:
QLC or RLC
TIME B4 - Data Init. Required 0 Bit map for -
Integer handling of timed-
out points
(1 = Use last value,
0 = Skip)
IN1 - Variable Optional 0 Output to QLC/LC LA
registers (analog)
•
•
•
IN16

OW351_R1100 491
5.107 SLCDIN
5.10 7 SLCDIN
Description
The SLCDIN algorithm reads up to 16 digital values from a Group 1 QLC or Ovation Link
Functional Symbol
The Hardware addresses of the primary and secondary QLC cards are specified by the PHW and
SHW parameters (if no secondary QLC is used, SHW is set to zero).
matter).
 If PSTA = FALSE and SSTA = TRUE, the points are read from the secondary
QLC/LC.
 If PSTA = FALSE and SSTA = FALSE, the point values are not updated and the points are
 If PSTA = FALSE and SSTA is not defined, the point values are not updated and the points
are assigned BAD quality.
 If PSTA and SSTA are not defined, the point values are not updated and the points are
492 OW351_R1100
5.107 SLCDIN
Point Data Format
Each digital point occupies one data register (equivalent to the 1W field of the point data record).
The FRMT parameter is used to specify the format of the Digital point data to be read from the
QLC/LC register. The three available formats are as follows:
The following bits are placed into the 1W field (no other bits cleared) of the digital point record:
Format description
FRMT DE S C R I P TI O N
0 Bit 0 - Digital value

Bit 12 - Limit checking off
Bit 13 - Alarm checking off
The remaining bits of the 1W field are used for alarm status, operator entry, and Data Highway
status information. (See Ovation Record Types Reference Manual.)
specified by parameter REG1. The total area required for the 16 digital points is 16 registers.
registers, even if some points are omitted from the argument list. For example, if REG1 and point
OUT1 is omitted, then OUT2 is read from data register 5
(no read is performed from data register 4).
The location from which a given point is read can be calculated using the following form ula:
point_address = REG1 + (point_number - 1)
where:
point_address = QLC/LC data register containing the digital point

point_number = 1 for parameter OUT1, 2 for parameter OUT2, and so on.
Any point which lies beyond the end of the 2048 QLC/LC data regist ers is assigned BAD quality.
For example, if REG1 =2044, only the first three point values (parameters OUT1, OUT2, and
OUT3) can be obtained.
OW351_R1100 493
5.107 SLCDIN
Digital Point Record Types
If alarm checking is to be performed on digital points read from the QLC/LC, use point record type
Long Digital.
FI E L D RE C O R D

Number
FRMT B0 - Integer Data Init. Required - Point Format -
REG1 B1 - Integer Data Init. Required 0 First QLC/LC data -

register
PHW B2 - Integer Data Init. Required 0 Primary QLC/LC -
hardware address
(see page 3).
SHW YU - Integer Data Init. Required 0 Secondary -
QLC/LC hardware
address
(see page 3).
(1,2)
TYPE X1-Byte Data Init Required QLC Interface Card -
Type:
QLC or RLC
OUT1 - Variable Optional - Input from LD
QLC/LC registers
• (digital)
•
•
OUT16
status input
(digital)
SSTA - Variable Optional - Secondary LD, LP
QLC/LC status
input (digital)
494 OW351_R1100
5.108 SLCDOUT
5.10 8 SLCDOUT
Description
The SLCDOUT algorithm writes up to 16 digital points to a Group 1 QLC or Ovation Link
Functional Symbol
matter).
 If PSTA = FALSE and SSTA = TRUE, the points are written to the secondary QLC/LC.
OW351_R1100 495
5.108 SLCDOUT
Point Data Format
Each digital point occupies one data register (equivalent to the 1W field of the point data record).
(See Ovation Record Types Reference Manual.)
parameter REG1. The total area required for the 16 digital points is 16 registers.
The point parameters (IN1 through IN16) are associated with consecutive QLC/LC data registers,
even if some points are omitted from the argument list. For example, if REG1 = 4 and point IN1 is
omitted, then IN2 is written to data register 5 (no data is written to register 4).
where:
point_address = QLC/LC data register containing the digital point
point_number = 1 for parameter IN1, 2 for parameter IN2, and so on.
No data is written to registers beyond the valid range (0 through 2047). For example, if REG1 =
2044, only the first three point values (parameters IN1 through IN3) can be written.
Timed-Out Points
below:
16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
TIME bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
 For each point, a value of 1 (one) in the corresponding bit indicates that the last received
value should be written if the point is timed-out.
496 OW351_R1100
5.108 SLCDOUT
FI E L D RE C O R D

Integer Number
REG1 B1 - Data Init. Required 0 First1 QLC/LC data -
Integer register
PHW B2 - Data Init. Required 0 Primary QLC/LC -

(see page 3).
SHW YU - Data Init. Required 0 Secondary QLC/LC -
(see page 3).
(1,2)
TYPE X1-Byte Data Init Required QLC Interface Card Type: -
QLC or RLC
TIME B4 - Data Init. Required 0 Bit map for handling -

Integer of timed-out points (1
= Use last value, 0 =
Skip)
IN1 - Variable Optional - Output to QLC/LC LD
register (digital)
•
•
•
IN16

OW351_R1100 497
5.109 SLCPIN
5.10 9 SLCPIN
Description
The SLCPIN algorithm reads up to 16 packed points from a Group1 QLC card or LC
(or redundant pair of Group 1 QLC cards).
Functional Symbol
Note: For the Windows platform, the parameters OUT10 - OUT16 are represented as
OT10 - OT16.
matter).
 If PSTA = FALSE and SSTA = TRUE, the points are read from the secondary QLC/LC.
 If PSTA = FALSE and SSTA = FALSE, the point values are not updated.
 If PSTA = FALSE and SSTA is not defined, the point values are not updated.
 If PSTA and SSTA are not defined, the point values are not updated.
498 OW351_R1100
5.109 SLCPIN
Data Format
Each packed point value occupies one QLC/LC data register. For packed points, the value is
stored in the A2 field of the LP point data record. See Ovation Record Types Reference Manual.)
specified by parameter REG1. The total area required for the 16 packed point values is 16
registers.
registers. For example, if REG1 = 4, the value of OUT1 is read from register 4, OUT2 is read from
register 5, and so on. These point parameters are required and may not be omitted from the
argument list, regardless of the number of points which are actually used by the application.
The location from which a given point is read can be calculated using the following formula:
where:
point_address = QLC/LC data register containing the packed value

point_number = 1 for parameter OUT1, 2 for parameter OUT2, and so on.
Any value which lies beyond the end of the 2048 QLC data registers or 4096 LC data register is
not read. For example, if REG1 = 2044, only the first three point values (parameters OUT1,
OUT2, and OUT3) can be obtained.
FI E L D RE C O R D

Number
REG1 B1 - Integer Data Init. Required 0 First QLC data -
register
PHW B2 - Integer Data Init. Required 0 Primary QLC DIOB -
address or LC
address
SHW YU - Integer Data Init. Required 0 Secondary QLC -
DIOB address or
LC address
CARD X4 - Byte Data Init. Required 1 PCI Card Number -
(1,2)
TYPE X1 - Byte Data Init. Required QLC Interface Card -
Type.
QLC or RLC
OW351_R1100 499
5.109 SLCPIN
FI E L D RE C O R D
OUT1 - Variable Optional - Input from QLC/LC LP

register (packed)
•
•
•
OUT16

500 OW351_R1100
5.110 SLCPOUT
5.11 0 SLCPOUT
Description
The SLCPOUT algorithm writes up to 16 packed points to a Group 1 QLC card or LC (or
redundant pair of Group 1 QLC cards).
Functional Symbol
matter).
 If PSTA = FALSE and SSTA = TRUE, the points are written to the secondary QLC/LC.
OW351_R1100 501
5.110 SLCPOUT
Data Format
Each packed group point value occupies one QLC/LC data register.
For packed points, the value is obtained from the A2 field of the LP point data record. (See
Ovation Record Types Reference Manual.)
parameter REG1. The total area required for the 16 packed point values is 16 registers.
The point parameters (IN1 through IN16) are associated with consecutive QLC/LC data registers.
For example, if REG1 = 4, the value of IN1 is written to register 4, IN2 is written to register 5, and
so on. These point parameters are required and may not be omitted from the argument list,
regardless of the number of points which are actually used by the application.
where:
point_address = QLC/LC data register containing the packed group or holding register value
point_number = 1 for parameter IN1, 2 for parameter IN2, and so on.
No data is written to registers beyond the valid range (0 through 2047 for QLC and 0-4096 for
LC). For example, if REG1 = 2044, only the first three point values (parameters IN1 through IN3)
can be written.
Timed-Out Points
below:
16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
TIME bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
 For each point, a value of 1 (one) in the corresponding bit indicates that the last received
value should be written if the point is timed-out.
502 OW351_R1100
5.110 SLCPOUT
FI E L D RE C O R D

number
REG1 B1-Integer Data Init. Required 0 First QLC/LC data -
register
PHW B2-Integer Data Init. Required 0 Primary QLC/LC -
address
SHW YU- Integer Data Init. Required 0 Secondary QLC/LC -
address

(1, 2)
TYPE X1 - Byte Data Init. Required QLC Interface Card Type. -
 QLC
 RLC
TIME B4 - Integer Data Init. Required 0 Bit map for handling -
of timed-out points
(1 = Use last value,
0 = Skip)
IN1 - Variable Optional - Output to QLC/LC LP
register (packed)
•
•
•
IN16

OW351_R1100 503
5.111 SLCSTATUS
5.11 1 SLCSTATUS
Description
The SLCSTATUS algorithm reads hardware and user application status information from a Group
1 QLC or Ovation Link Controller (LC) card (or redundant pair of Group 1 QLC cards). The status
information is placed in packed group points.
Functional Symbol
and SHW parameters.
An additional parameter is also provided to indicate whether both QLC/LC are present in the drop.
Bits 0 and 1 of the AVBL parameter are used for the primary and secondary QLC/LC,
respectively. If the bit is set to 0, then that QLC/LC card is not present. If the bit is set to 1, then
that QLC/LC card is present.
The application status information is retrieved from four consecutive QLC/LC data registers,
starting at the register specified by parameter REG1. The integer values read from these
locations are stored in the user-initialized packed (LP) points, as follows:
Register points
D AT A RE G I S TE R LP P O I N TS
REG1 PFID/SFID
REG1 + 1 PPR1/SPR1
REG1 + 2 PPR2/SPR2
REG1 + 3 PAUX/SAUX
504 OW351_R1100
5.111 SLCSTATUS
The fault ID obtained from REG1 (PFID or SFID) is also used by SLCSTATUS to place the drop
into QLC/LC fault. If this value is non-zero, a fault is reported with the following values:
Fault Code = 129
Fault ID = PFID/SFID
Fault Parameter 1 = PPR1/SPRl
Fault Parameter 2 = PPR2/SPR2
Note: Fault Code 129 is reported for either the primary or secondary QLC/LC. The Fault ID or
Fault Parameter(s) must be appropriately defined to indicate which QLC/LC is in fault.
The PAUX/SAUX parameters may be used to define additional information for use by the
application.
QLC Hardware Status Information
QLC hardware status information is placed in the PSTA and SSTA variables (for the primary and
secondary QLCs, respectively). The bits in these parameters are defined as follows:
BI T D E F I N I TI O N
0 Watchdog timer:
0 = Timed-out
l = Not timed-out
1 SBX module:
0 = Module is attached
1 = Module is not attached
2 DRAM parity:
0 = No parity error
1 = Parity error
3 Configuration switch 6 setting:
0 = QLC boot from external disk
1 = QLC boot from flash memory
4 Configuration switch 5 setting:
0 = 80C187 installed
1 = 80C187 not installed
5 Configuration switch 4 setting (Baud rate for communication with external
personal computer)
6 Configuration s witch 3 setting. (Baud rate for communication with external

personal computer)
7 Configuration switch 2 setting (user defined)
8 - 15 Undefined
Note: The term 'configuration switch' refers to QLC DIP switch SW3. The switch settings are
defined as 0 = ON = closed; 1 = OFF = open.
The watchdog timer must be reset by the user application. Otherwise, bit 0 of PSTA/SSTA is
always = 0.
OW351_R1100 505
5.111 SLCSTATUS
LC Hardware Status Information
LC Hardware Status information is placed in the PSTA and STA variables (for the primary and
secondary LCs, respectively). The bits in these parameters are defined as follows:
Bit definition
BI T D E F I N I TI O N
0 Watchdog Timer:
0 - Timed-Out
1 - Not Timed-out
1-2 Personality Module Type:
0 - RS - 232 Applications Port
1 - RS - 485 Full Duplex Applications Port
3 Boot up Serial Link Controller from:
0 - External PC via Local Serial Port
1 Internal Flash Memory
5 BAUD RATE on Serial Port:
0 - Use 9600 BAUD RATE
1 - Use 19200 BAUD RATE
6-15 Undefined
FI E L D RE C O R D
DIAG LU - Integer Data Init Required 15 Tuning diagram -

number
REG1 B0 - Integer Data Init. Required 0 First QLC/LC status -
register
AVBL B1 - Integer Data Init. Required 0 Bit mask for -
available QLCs/LCs
PHW B2 - Integer Data Init. Required 0 Primary QLC/ LC -
hardware
SHW YU - Integer Data Init. Required 0 Secondary QLC/ LC -
hardware
(1,2)
PFID - Variable Required - Primary QLC/ LC LP
fault ID (packed)
PPR1 - Variable Required - Primary QLC/ LC LP

fault parameter 1
(packed)
506 OW351_R1100
5.111 SLCSTATUS
FI E L D RE C O R D
PPR2 - Variable Required - Primary QLC/ LC LP

fault parameter 2
(packed)
PAUX - Variable Required - Primary QLC/ LC LP
auxiliary fault
information (packed)
PSTA - Variable Required - Primary QLC/ LC LP
hardware status
SFID - Variable Required - Secondary QLC/ LC LP

fault ID (packed)
SPR1 - Variable Required - Secondary QLC/ LC LP

fault parameter
1(packed)
SPR2 - Variable Required - Secondary QLC/ LC LP
fault parameter 2
(packed)
SAUX - Variable Required - Secondary QLC/ LC LP
auxiliary fault
SSTA - Variable Required - Secondary QLC/ LC LP

hardware status
OW351_R1100 507
5.112 SMOOTH
5.11 2 SMOOTH
Description
This algorithm “smooths” an analog input value. Smoothing of an analog input (sometimes
referred to as digital filtering) consists of giving the most weight to the most recent sample and the
diminishing weight to all preceding readings. The relative weight given to the most recent value is
determined by the smoothing time constant specified for input filtering. The input (IN1) is sampled
each loop. If the smoothing time constant is less than or equal to zero, t he output is equal to the
input value. If the smoothing time constant is less than zero, the quality of the output is set to
BAD.
The value of IN1 is checked for an invalid real number. If the calculated value of the output is
invalid, the quality of OUT is set to BAD; otherwise, the quality of IN1 is propagated to the output.
Note: Algorithm record fields that contain real number values are not updated if the new value is
an invalid real number.
Functional Symbol
FI E L D RE C O R D

Number
* SMTH R1-Real Selectable Required 0.0 Smoothing time -
constant in
seconds

508 OW351_R1100
5.112 SMOOTH
Function
OUT = (alpha x IN1) + (beta x oldout)
where:
alpha = 1 - E(- loop time/SMTH)
beta = E (- loop time/SMTH)

loop time = sampling time (loop time)
oldout = locally retained, real variable
OW351_R1100 509
5.113 SOFTSOE
5.11 3 SOFTSOE
Description
The SOFTSOE algorithm allows a Sequence of Events (SOE) to be generated by placing an

algorithm on a control sheet. Prior to the release of the SOFTSOE algorithm, an SOE event could
only be generated by a Sequence of Events hardware module. A sequence of events hardware
module is not required to use the SOFTSOE algorithm.
The SOE events generated by the SOFTSOE algorithm are identical to any hardware SOE events
and are stored in the same history, combined on the same reports, and so forth.
Note: Even though the resolution of events that are generated using the SOFTSOE algorithm is
to the nearest one millisecond, the accuracy is only as good as the control task period in which
the algorithm executes. SOFTSOE is designed to generate an SOE event based on the time the
algorithm samples the trigger point. This is only accurate to the period of the control task , which
could be significantly different from the time when the trigger point actually changed state. That
is, the time tag on the SOE event only reflects the time (to the nearest millisecond) when the
algorithm sampled the input.
Functional Symbol
SOE Event Trigger
The state of an input digital point triggers the SOE event. The event trigger state is user
configurable. Available options are rising edge, falling edge, rising or falling edge (both), or time
change.
Note: The point connected to the TRIG input must be a digital point; it cannot be a bit of a
pack ed point.
The SOE Event Trigger point should not have the SOE point flag enabled in its definition. If the
SOE point flag is enabled, it uses one of the available 1,024 SOE point slots per Controller. These
slots are typically used for hardware SOE points only.
Although the system does not prevent it, you should not use the same digital point in more than
one SOFTSOE algorithm since this is a redundant configuration. It is also redundant to connect
hardware SOE points to SOFTSOE algorithms.
510 OW351_R1100
5.113 SOFTSOE
Event Time Tagging
The time that is assigned to the SOE event can be one of the following:
 Current system time at the time the associated digital point changes to the triggering state.
 Optional external event time provided to the algorithm of which the user provides the format
(see External Time Formats).
 U8 and U9 fields of deluxe records. This is useful for third-party links.
If you cannot guarantee that the change of trigger value and related external time value are
delivered to the algorithm at the same execution loop, the tunable parameters TMDLY and VDLY
can be used to set the maximum allowed delay between the trigger change and the external time
value change.
When a trigger value changes, but the time value does not change at the same execution loop,
the algorithm waits. The VDLY parameter specifies how long to wait for a change of time value. If
the time value changes within this time, an SOE event is generated with the new time value. If the
time value does not change before this time passes or before the trigger value changes once
more, the action taken depends on the NOTME parameter.
The NOTME parameter defines the action taken when a trigger value changes, but a relevant
change of external time value is not observed. Depending on this parameter, the algorithm can do
one of the following:
 Send no SOE events.
 Send an SOE event with the current system time.
 Send an SOE event with the last received external time value.
Conversely, when the external time value changes, but the trigger value does not change at the
same execution cycle, the algorithm waits. The TMDLY parameter specifies how long to wait for a
change of triggering value. If the trigger value changes within this time, the SOE event is
immediately generated with the previously received time value. If the trigger value does not
change within this time, the algorithm waits for another change of time value before generating an
SOE event.
The TMCHG parameter tells whether the external time value changes every time the trigger value
changes or only when new SOE events are triggered. This information allows the algorithm to
associate changes of the external time value with proper changes of the trigger value.
The time change option is useful for external events (received from third-party systems) which do
not have an associated digital value, but only have the time when a particular event occurred. In
this configuration, the time used for tagging the events cannot be the current system time.
When the external time value is passed to the algorithm using two or more points, the algorithm
assumes that the entire time value changes whenever any of those points change. The algorithm
cannot detect when one of those points was already updated while the other still has the old
value. Therefore, if two or more points are used for the external time value, it should be
guaranteed that either both are delivered to the algorithm at the same time, or that both are
delivered before or at the same time as the triggering value.
OW351_R1100 511
5.113 SOFTSOE
Algorithm Internal Event Buffer

Whenever a new SOE event is generated, the SOFTSOE algorithm tries to immediately send the
event message to the SOE subsystem. If it is not possible to send the message (because the
SOE subsystem is too busy processing hardware or software SOE events, or the historian is
temporarily not available), the algorithm stores the event in its internal buffer.
The events stored in the internal buffer are sent to SOE in subsequent algorithm executions, as
soon as there is enough space for them in the software SOE queue. However, the SOFTSOE
algorithm never sends more than three buffered messages in one execution cycle.
The Number of Pending Events (G0) field in the LC record indicates the number of events that are
currently stored in the internal buffer, pending to be sent to the SOE. This number does not
include possible messages already inserted in the queue, waiting to be processed by the SOE
subsystem.
If for some reason the algorithm internal event buffer becomes full before the pending events can
be transferred to the SOE, and there is no place in it for the newly generated event, the event is
lost and the algorithm sets the optional ERR output to true for one execution cycle.
Optional ENBL Input
You can use the optional ENBL input to control the operation of the algorithm. The algorithm only
generates SOE events when the ENBL input is true. If the ENBL input is not connected, the
algorithm will always be enabled and generate events.
External Time Formats
As an option, the timestamp that is stored in the resulting SOE event can be input externally. You
select one of the available formats of the time values passed to the algorithm.
The timestamp in SOE messages is actually made of the seconds and nanoseconds fields, even
though SOE information is stored in the history with microsecond resolution.
Seconds and Microseconds Format
This format presents the timestamp information in two parts -- seconds and microseconds.
Timestamp
The timestamp is built using the following scheme:
Event timestamp = Seconds [S] + Microseconds x 1000 [nS]
512 OW351_R1100
5.113 SOFTSOE
Seconds
The "seconds" part is represented as the number of full seconds since January 1, 1970. You
cannot pass this value with one packed or analog point because it has a wider range than can be
precisely represented by those point types.
You can utilize either two packed (LP/DP) or analog (LA/DA) points or one packed digital (PD)
point for the "seconds" part. When using two packed points, the first contains Low Order Word
(bits 0 - 15) and the second contains High Order Word (bits 16 - 31) of the value.
Two points used for seconds
I N P U T NAME FU N C TI O N
TSEC1 (LP/DP, LA/DA) Seconds -- bits 0 - 15

The algorithm calculates the seconds field as follows:
Seconds = TSEC1 + 65536 x TSEC2
One point used for seconds
TSEC1 (PD) Seconds
Seconds = TSEC1
Microseconds
The "microseconds" part specifies the number of microseconds in the specified second when the
event occurred.
As with seconds, this value can either be passed to the SOFTSOE algorithm using two packed
(LP/DP) or analog (LA/DA) points or one packed digital (PD) point.
Two points used for microseconds
ETIM1 (LP/DP, LA/DA) Microseconds -- bits 0 - 15
ETIM2 (LP/DP, LA/DA) Microseconds -- bits 16 - 31
OW351_R1100 513
5.113 SOFTSOE
The algorithm calculates the microseconds field as follows:

Microseconds = ETIM1 + 65536 x ETIM2
One point used for microseconds
ETIM1 (PD) Microseconds
The algorithm calculates the microseconds field as follows:
Microseconds = ETIM1
Seconds and Milliseconds format
This format presents the timestamp information in two parts - seconds and milliseconds.
Timestamp
Event timestamp = Seconds [S] + Milliseconds x 1000000 [nS]
Seconds
The "seconds" part is represented as the number of full seconds since January 1, 1970.
You can utilize either two packed (LP/DP) or analog (LA/DA) points or one packed digital (PD)
point for the "seconds" part. When using two packed points, the first contains Low Order Word
(bits 0 - 15) and the second contains High Order Word (bits 16 - 31) of the value.
Two points used for seconds

Seconds = TSEC1 + 65536 x TSEC2
One point used for seconds
TSEC1 (PD) Seconds
Seconds = TSEC1
514 OW351_R1100
5.113 SOFTSOE
Milliseconds
The "milliseconds" part specifies the number of milliseconds in the specified second when the
event occurred.
One packed (LP or DP) or packed digital (PD) point is used for the "milliseconds" part.
Input point functions
ETIM1 (LP/DP, LA/DA, PD) Milliseconds
The algorithm calculates the milliseconds field as follows:
Milliseconds = ETIM1
Milliseconds of Hour Format
This format presents the timestamp information as a single value -- the total number of
milliseconds since the last full hour. A packed digital point is required.
The time provided to the algorithm is relative and can be definitely interpreted only within a
specified period of time. This puts several constraints on the mechanism of generating and
passing the time value to the algorithm:
 It must be guaranteed that every timestamp is transferred from the third-party system to the
Ovation system and processed by the SOFTSOE algorithm in less than an hour from the
moment when it was generated. If a time value older than 59 minutes and 55 seconds is
received, it is interpreted incorrectly and an invalid timestamp is generated.
 The source of time must be synchronized with the Ovation system. If a time value more than
four seconds in the future is received, it is interpreted incorrectly and an invalid timestamp is
generated.
 This format should be avoided when an SOE event is triggered by a change of time value. If
two consecutive events are received by the algorithm with the exact one hour interval
between timestamps, the algorithm is unable to detect a change of time, and the SOE event
is not generated.
ETIM1 (PD) Milliseconds in an hour
Timestamp
Timestamp = Seconds [S] + Milliseconds x 1000000 [nS]
OW351_R1100 515
5.113 SOFTSOE
Seconds
Calculate time of last full hour.

Full Hour Seconds = Current Seconds - (Current Seconds modulo 3600)
Add received time value (seconds).
Seconds = Full Hour Seconds + (ETIM1 div 1000)
Adjust if the event occurred in the previous full hour.
if Seconds >= Current Seconds + 5
Seconds = Seconds - 60
Adjust if the event has a timestamp in the future - in the next full hour. This can only occur
when the source of time is not accurately synchronized with Ovation.
else if Seconds < Current Seconds - 3595
Seconds = Seconds + 60
Milliseconds
Milliseconds = (ETIM1 modulo 1000)
Milliseconds of Minute Format
This format presents the timestamp information as a single value - the total number of
milliseconds since the last full minute.
This is a relative format of time value. The following constraints apply:

 It must be guaranteed that every timestamp is transferred from the third-party system to the
Ovation system and processed by the SOFTSOE algorithm in less than 55 seconds from the
moment when it was generated. If a time value older than 55 seconds is received, it is
interpreted incorrectly and an invalid timestamp is generated.
 The source of time must be synchronized with the Ovation system. If a time value more than
four seconds in the future is received, it is interpreted incorrectly and an invalid timestamp is
generated.
 You should avoid this format when an SOE event is triggered by a change of time value. If
two consecutive events are received by the algorithm with the exact one minute interval
between timestamps, the algorithm is unable to detect a change of time and the SOE event is
not generated.
ETIM1 (LP, LA, PD) Milliseconds in a minute
Timestamp
Timestamp = Seconds [S] + Milliseconds x 1000000 [nS]
516 OW351_R1100
5.113 SOFTSOE
Seconds
Calculate time of last full minute.

Full Minute Seconds = Current Seconds - (Current Seconds modulo 60)
Add received time value (seconds).
Seconds = Full Minute Seconds + (ETIM1 div 1000)
Adjust if the event occurred in the previous full minute.
if Seconds >= Current Seconds + 5
Seconds = Seconds - 60
Adjust if the event has a timestamp in the future - in the next full minute. This can only occur
when the source of time is not accurately synchronized with Ovation.
else if Seconds < Current Seconds - 55
Seconds = Seconds + 60
Milliseconds
Milliseconds = (ETIM1 modulo 1000)
Deluxe Records Time of Scan
This format is supported for Ovation deluxe records only. The Ovation deluxe records support the
U8 and U9 time scan fields. These fields are designed to hold seconds and nanoseconds
respectively. Third-party interfaces typically use these fields to store the time when the point was
processed.
This format also allows the U8 and U9 to be used for the SOE event timestamp.
Seconds = U8
Nanoseconds = U9
Event timestamp = Seconds [S] + Nanoseconds [nS]
FI E L D RE C .
TRIG -- Variable Required -- SOE trigger input LD
ENBL -- Variable Optional -- Enable input LD, LP
OW351_R1100 517
5.113 SOFTSOE
FI E L D RE C .
TSEC1 -- Variable Optional -- External seconds PD

External seconds (bits LP, LA
0 - 15)
TSEC2 -- Variable Optional -- External seconds (bits LP, LA
16 - 32)
ETIM1 -- Variable Optional -- External microseconds PD
External microseconds LP, LA
(bits 0 - 15)
External milliseconds
PD, LP,
LA
ETIM2 -- Variable Optional -- External microseconds LP, LA
(bits 16 - 32)
ERR -- Variable Optional -- Buffer full error output LD
ETYPE X1 - byte Data Init Required 0 Event trigger type: --
00 = Rising edge
01 = Falling edge
02 = Both
03 = Time change
TSFMT X2 - byte Data Init Required 0 Time stamp format: --
0 = Use current
system time
1 = Deluxe record
U8/U9
2 = Seconds +
Microseconds
3 = Seconds +
Milliseconds
4 = Milliseconds in
hour
5 = Milliseconds in
minute
TMDLY X3 - byte Tuning Required 1 Maximum delay --
Constant between timestamp
change and value
change in loops
VDLY X4 - byte Tuning Required 1 Maximum delay --
Constant between value change
and timestamp change
in loops
518 OW351_R1100
5.113 SOFTSOE
FI E L D RE C .
NOTME X5 - byte Tuning Required 0 Action when value --

Constant changes without
timestamp change:
0 = Send no event
1 = Send event with
current system time
2 = Send event with
last timestamp
TMCHG X6 - byte Tuning Required 0 Change of time --
Constant expected:
0 = On every change
of value
1 = When new event is
to be generated
PDEVT G0 - Alg. Init N/A 0 Number of pending --
integer events
OW351_R1100 519
5.114 SPTOSA
5.11 4 SPTOSA
Description
The SPTOSA algorithm transfers a packed point record into an analog point record.
The packed digital value field is converted to a whole (real) number (for example, 4.0) and stored
in the analog point value field.
If Bit 15 is a zero, a positive number results. If Bit 15 is a one, a negative number results. The bit
pattern for each packed word produces a real number between -32767 and +32767. The method
for converting bit patterns into negative numbers is the sign and magnitude method.
Functional Symbol
FI E L D RE C O R D
* PACK - Variable Required - Input (packed) LP

* Parameter names may vary depending on software release.
520 OW351_R1100
5.115 SQUAREFOOT
5.11 5 SQUAREFOOT
Description
The SQUAREROOT algorithm multiplies the analog input with an internal gain, adds a bias and
then takes the square root.
Functional Symbol
Tracking Signals
Bit description
OW351_R1100 521
5.115 SQUAREFOOT
The high and low limit flags and the tracking signals from the algorithm are output to TOUT to be
FI E L D RE C O R D

Number
IN1G R1-Real Tuning Required 1.0 Gain on input. The -
Constant gain on the input
(GAIN) should never be
placed into alarm.
IN1B R2-Real Tuning Required 0.0 Bias on input -
Constant
(BIAS)

522 OW351_R1100
5.115 SQUAREFOOT
FI E L D RE C O R D

IN1 - Variable Required - Analog input LA

value, mode and
status signal for
Input 1 variable
variable
limiting mode
signals and
tracking value;
analog input
variable
Function

IF IN1GB > 0 THEN
OUT = SQUARE ROOT OF IN1GB
ELSE
OUT = 0
IF OUT >= TPSC THEN
OUT = TPSC
ELSE
IF OUT <= BTSC THEN
OUT = BTSC
OW351_R1100 523
5.116 SSLT
5.11 6 SSLT
Description
SSLT calculates Entropy (S) of Saturated Liquid given its Temperature. It is one of the functions
of the STEAMTABLE algorithm (see page 544).
Functional Symbol
SSLT input and output values
(INPUT 1) TEMP 32.0 705.47

(OUT 1) ENTR -0.000036890 1.0612
524 OW351_R1100
5.117 STATISTICS
5.11 7 STATISTICS
Description
The STATISTICS algorithm performs running calculations of weighted arithmetic mean, variance
and standard deviation of sampled input, based on values from TW (Time Window). The TW
parameter is defined by the user. This algorithm also tracks input samples to determine their
minimal and maximal value from TW last time. Additionally a user can divide the time window into
a maximum of four regions and define weights for each region. Weights can be defined by a point
or as a static, non-negative real value. Values from a given partition are taken with the same
weight.
Functional Symbol
The parameters for the Functional Symbols are defined below:

 IN1 – input
 W1 – weight for 1st partition
 W2 – weight for 2nd partition
 W3 – weight for 3rd partition
 W4 – weight for 4th partition
 MEAN – weighted arithmetic mean of input values (denoted as )
 VAR – variance of input values (denoted as )
 SDEV – standard deviation of input values (denoted as )

 MIN – minimal value of input
 MAX – maximal value of input
 ROC – rate of change of MEAN
 STATE – information about state of the buffer 0/1 (not full/full)
 STATUS – information about accuracy of configuration parameters
OW351_R1100 525
5.117 STATISTICS
Algorithm Parameters and Rules
Time Window Definition
User must define:
UNIT — units of time. The user can select from one of five units:
0 = tenths of a second
1 = seconds
2 = minutes
3 = hours
4 = days
TIME — number of units
Time window (Tw) is defined as:
TW = UNIT x TIME
Below is a graphical representation of the Time window.
Figure 17: Time Window
Because the time window can encompass a large number of input samples, it is divided into NUM
(up to 60) subregions. For each subregion, a set of DISTANCE subsequent input samples is
taken. Only valid samples without BAD quality are used. Each time the algorithm takes the next
set of DISTANCE subsequent input samples into a new subregion, it stores a number of
acceptable samples, their sum and the sum of their squares for this subregion. Those values are
then used to calculate outputs.
526 OW351_R1100
5.117 STATISTICS
The recommended length of time window is a multiple of p (control area time). The following
guidelines are recommended for best performance:
 If NUM is smaller than 60, then the algorithm uses M last input values itself to calculate
outputs. Value of NUM is set to M. DISTANCE is set to 1.
 If NUM is a multiple of 60, then the algorithm divides the time window into 60 subregions with
the same length (DISTANCE). For each sub region number of acceptable input values, the
sum and sum of squares is computed and then used to calculate outputs. The value of NUM
is set to 60, its maximal number. DISTANCE is set to M/60.
The following description illustrates how the algorithm calculates NUM parameter and
DISTANCE.
First, the algorithm calculates the number of all cycles (number of input samples) during the time
window:
where:
NUMBER_ALL_CYCLES is rounded down
Next, the algorithm calculates the distance (number of input samples taken into each subregion):
where:
DISTANCE is rounded up
Based on the number of all cycles during time window and distance, the algorithm calculates the
number of subregions, as:
If the length of time window is not a multiple of p then bit 1 in the STAT output point is set to 1. In
this case, the length of time window is shorter than original settings.
OW351_R1100 527
5.117 STATISTICS
For example, assume the follow parameters:
p = control area time = 20[sec]
UNIT = seconds
TIME = 90
The equations are solved as follows:
TW = UNIT x TIME = 90 x 1[s] = 90s
If the length of time window is a multiple of p but M is not a multiple of 60, then bit 0 in the STAT
output point is set to 1. In this case, the length of time window is not changed, but the last
subregion is smaller. Distance for the last shorter subregion is calculated as a remainder of
NUMBER_ALL_CYCLES / DISTANCE.
For further explanation, the following two examples are shown. The first example shows a
situation when the recommended conditions are followed. The second example shows a situation
when the recommended conditions are not followed.
528 OW351_R1100
5.117 STATISTICS
Example 1
In this example, the following parameters are used:
UNIT = seconds
TIME = 300
For these settings, the time window is equal to 300 control cycles and NUM parameter (number of
subregion) is equal to 60 (maximal value).
The following figure represents a distribution of subregions in the time window.
Figure 18: Distribution of Subregions in Time Window (recommended conditions)
OW351_R1100 529
5.117 STATISTICS
Example 2
This example represents a situation when the length of time window is not divided by 60 and the
recommended parameters are not followed. This situation can happen when a user sets
parameters that do not follow the recommendations. A second situation can happen when the
control time area changes (sheet is run in a different time area). The algorithm works correctly
with these parameters, but they are different from the recommended parameters.
For this example, assume the following parameters:
UNIT = seconds
TIME = 303
The equations are solved as follows:
TW = UNIT x TIME = 303 x 1[s] = 303s
530 OW351_R1100
5.117 STATISTICS
The following figure represents a distribution of sums in the time window using non-recommended
parameter conditions.
Figure 19: Distribution of Subregions in Time Window (not recommended conditions)
In this case, the number of subregions is reduced to NUM=51. This number makes a steady
distribution of subregions – number of input samples used to calculate each sum (except last) is
the same. Each sum is calculated from six input samples; however, the last sum only has three
input samples.
OW351_R1100 531
5.117 STATISTICS
Weights definition
The Time window can be divided into a maximum of four regions. The user defines ranges of
regions and weights.
PART 1 - end range of first partition defined by number of units
PART 2 - end range of second partition defined by number of units
PART 3 - end range of third partition defined by number of units
PART 4 - end range of fourth partition defined by number of units
W1 - weight for first partition
W2 - weight for second partition
W3 - weight for third partition
W4 - weight for fourth partition
Note: Ranges are defined in the same units as the time window. Weight value has to be a non-
negative real value.
Below is an example with definitions, ranges and weights (expanded Example 1).
Example 3
This example assumes the following parameters:
UNIT = seconds
TIME = 300
R1 =6
R2 = 150
R3 = 293
R4 = TIME = 300
For these settings, the time window is equal to 300 control cycles and the NUM parameter is
equal to 60.
532 OW351_R1100
5.117 STATISTICS
The following figure shows a distribution of subregions in the time window.
Figure 20: Time Window with Weights
OW351_R1100 533
5.117 STATISTICS
In the case with weights, the algorithm must check membership to a region for each sum. The
algorithm calculates where the end for each region is supposed to be. Calculations are based on
the following equations:
Next, the algorithm calculates the final output as:
In Example 3, the parameters were defined as follows:
UNIT = seconds
TIME = 300
PART1 = 6
PART2 = 150
PART3 = 293
PART4 = TIME = 300
NUM =60
534 OW351_R1100
5.117 STATISTICS
Therefore, the equations are solved as follows:
These results are shown in the Time Window with Weights figure.
Number of sums for region 1 is equal to 1.
Number of sums for region 2 is equal to 30-1=29.
Number of sums for region 3 is equal to 58-30=28.
Number of sums for region 4 is equal to 60-58=2 .
Final output (if all samples are not BAD) is solved with the following equation:
OW351_R1100 535
5.117 STATISTICS
Quality of Input and Output Points
Qualities of MEAN, VAR, SDEV and ROC outputs are based on qualities for subregions.
Quality for each subregion is as follows:

 If all input samples taken into subregion are BAD - BAD
 If less than half of the input samples are GOOD - POOR
 If more than half of the input samples are GOOD - FAIR
 If all input samples taken into subregion are GOOD - GOOD
Qualities of MEAN, VAR, SDEV and ROC outputs are as follows:

 Until the first subregion is not filled (MEAN, VAR, SDEV) - BAD
 Until the first two subregions are not filled (ROC) - BAD
 If the quality of all subregions is BAD - BAD
 If the quality of less than half the subregions is GOOD - POOR
 If the quality of less than half of the sub regions is FAIR or POOR - FAIR
 If the quality of more than half the subregions is GOOD - FAIR
 If the quality of more than half (or all) of the sub regions is FAIR or POOR - POOR
 If the quality of all subregions is GOOD - GOOD
If the QUAL parameter is set to NO, then the following is true:

 The output quality will be set to the worst quality of the weight inputs. If the output quality is
calculated as bad, the algorithm will stop calculating the ROC, VAR, SDEV, and MEAN
outputs.
If the weight signals are set to a negative real value, then the ROC, VAR, SDEV, and MEAN
outputs will be set to BAD quality.
 If the weighted parameters are defined by the input pins, then the outputs will remain BAD
until the W1 through W4 input(s) are set to GOOD again.
 If the weighted parameters are defined in the algorithm, then the algorithm will set the
negative value to zero, and the quality will be set to GOOD.
Weight parameters are only used for calculating the MEAN.
Qualities of MIN and MAX outputs are set to qualities of input samples with minimum and
maximum value during time window Tw. In addition, those qualities are set to BAD until the first
subregion is filled.
536 OW351_R1100
5.117 STATISTICS
Function
MEAN output
The STATISTICS algorithm calculates the weighted arithmetic mean of input samples.
If weights are equal to 1.0, then the algorithm calculates the standard mean of input samples.
VAR and SDEV Outputs
Additionally, the algorithm calculates sample variance and standard deviation, which are defined
as the following (note that “NUM” is changed to “N”):
where:
= input sample value from time k-i
n = number of all samples in time window Tw
= mean value of input sample values in time window Tw
OW351_R1100 537
5.117 STATISTICS
The algorithm cannot store all the values for the above equation. Therefore, the standard
deviation and variance are derived by the following equations:
Using the sum in each region, the equation can be written as follows:
where:
= sum of samples from subregion i
= sum of squares of samples from subregion i
= number of samples used to calculate sum
If N equals 1, then and are set to zero.
538 OW351_R1100
5.117 STATISTICS
MIN and MAX Outputs

The STATISTICS algorithm reports the minimal and maximal input sample from N (NUM) last
subregions:
where:
= input sample with minimal value from i subregion;
where:
= input sample with maximal value from i subregion;
The outputs minimum value MIN and maximum value MAX are calculated at every loop, based on
stored min/max input values of samples from N last subregions. Qualities of t hese outputs are set
to qualities of samples with minimum value and maximum value.
ROC Output
The STATISTICS algorithm also calculates the rate of change of MEAN output value defined as:
where:
= Actual value of MEAN output
= Previous value of MEAN output
OW351_R1100 539
5.117 STATISTICS
Additional Information
During initial operation, the algorithm calculates outputs based on the configuration of “TOPT”
parameters. TOPT is defined as:
0 (yes) Mean value is equal to current input value (until buffer is full). STDV and VAR
are equal to 0.0. When the buffer is full, the algorithm starts working according
to the explanations listed in the examples above.
1 (no) Algorithm calculates MEAN, STDV and VAR values based on the samples as
they become available in the Time window.
Each change of the TIME parameter clears all stored data. STATE value is reset to 0.
FI E L D RE C O R D
DIAG LU - Data Init Required 149 Tuning diagram —

Integer number
TOPT X3 - Byte Data Init Optional YES Track output: —

 Yes
 No
QUAL X2 - Byte Data Init Optional No Ignore quality of —
weighted points:
 No
 Yes
UNIT X1 - Byte Data Init Optional 0 Units of time —
0 = tenths of a
second
1 = seconds
2 = minutes
3 = hours
4 = days
TIME G0 - Tuning Required 1 Number of units —
Integer Constant
PART 1 G2 - Tuning Required 0 End of range of first —

Integer Constant partition
PART 2 G3 - Tuning Required 0 End of range of —
Integer Constant second partition
Integer Constant third partition
Integer Constant fourth partition
IN1 — Variable Required — Input (analog) LA
540 OW351_R1100
5.117 STATISTICS
FI E L D RE C O R D
* W1 R1 - Real Selectable Required 1.0 Weight for first LA

partition
* W2 R2 - Real Selectable Required 1.0 Weight for second LA
partition
* W3 R3 - Real Selectable Required 1.0 Weight for third LA

partition
* W4 R4 - Real Selectable Required 1.0 Weight for fourth LA
partition
MEAN — Variable Optional — Output (analog) - LA

weighted arithmetic
VAR — Variable Optional — Output (analog) - LA
variance
SDEV — Variable Optional — Output (analog) - LA
standard deviation
MIN — Variable Optional — Output (analog) - LA
minimal value
MAX — Variable Optional — Output (analog) - LA
maximum value
ROC — Variable Optional — Output (analog) - LA
rate of change
STATE — Variable Optional — Buffer state LD, LP
STAT — Variable Optional — Configuration LP

status
OW351_R1100 541
5.118 STEAMFLOW
5.11 8 STEAMFLOW
Description
The STEAMFLOW algorithm performs a flow compensation based on a flow measurement on an

input as a differential pressure input or a flow input (IN1). Correction is applied from specific
volume (IN2), which comes from the output of the STEAMTABLE algorithm (see page 544).
If the output value is invalid, the quality of OUT is set to BAD. Otherwise, the quality of OUT is set
to the worst quality of the two inputs.
Note: You are responsible for the input’s units.
Functional Symbol
FI E L D RE C O R D
DIAG LU-Integer Data Init. Required 22 Tuning Diagram —

Number
TYPE X1-Byte Data Init. Required DELTAP Input Type (Deltap —
or Flow)
SCAL R1-Real Tuning Required 1.0 Scaling factor —
Constant
BASE R2-Real Tuning Required 1.0 Base specific —

Constant volume
GAIN R3-Real Tuning Required 1.0 Gain on Specific —
Constant Volume
542 OW351_R1100
5.118 STEAMFLOW
FI E L D RE C O R D
* IN1 — Variable Required — Analog Flow LA

Transmitter Delta
Pressure Input
* IN2 — Variable Required — Analog Specific LA
Volume Input
OUT — Variable Required — Analog output LA
variable
* Parameter name many vary depending on s oftware release.
Function
DELTAP:
FLOW:
OW351_R1100 543
5.119 STEAMTABLE
5.11 9 STEAMTABLE
Description
The STEAMTABLE algorithm calculates thermodynamic properties of water and steam. The
STEAMTABLE algorithm supports both English and SI engineering units. The inputs are checked
to determine if they are in range. If they are not, the output point is set to BAD, the last GOOD
value is retained, and the Flag output is set to TRUE. If more than one input is required, they are
also checked to determine if the combination of input is reasonable. If they are not reasonable,
the output point is set to BAD, the last GOOD value is retained, and t he Flag output is set to
TRUE. Otherwise, the quality of the OUT is set to the worst quality among the inputs.
Note: The steam tables are based on the 1967 American Society of Mechanical Engineers
(ASME) steam tables.
There are eleven individual symbols for the functions the STEAMTABLE algorithm performs. They
are as follows:
Region
RE G I O N CO N TR O L BU I L D E R RE Q U I R E D I N P U T O U TP U T
AL G O R I TH M S YMB O L
Compressed Liquid (CL) HSCLTP Temperature (IN1) Entropy (OUT)

(see page 295)
Pressure (IN2) Enthalpy (OUT1)
Atm. Pressure (IN3)
VCLTP (see page 586) Temperature (IN1) Specific Volume
(OUT)
Pressure (IN2)
Atm. Pressure (IN3)
Saturated Liquid (SL) HSLT (see page 296) Temperature (IN1) Enthalpy (OUT)
SSLT (see page 524) Temperature (IN1) Entropy (OUT)
VSLT (see page 587) Temperature (IN1) Specific Volume

(OUT)
PSLT (see page 435) Temperature (IN1) Pressure (OUT)
TSLP (see page 583) Pressure (IN1) Temperature (OUT)
Atm. Pressure (IN2)
TSLH (see page 582) Enthalpy (IN1) Temperature (OUT)
544 OW351_R1100
5.119 STEAMTABLE
RE G I O N CO N TR O L BU I L D E R RE Q U I R E D I N P U T O U TP U T
AL G O R I TH M S YMB O L
Saturated Vapor (SV) PSVS (see page 436) Entropy (IN1) Pressure (OUT)
HSTVSVP Pressure (IN1) Enthalpy (OUT)
(see page 297) Temperature (OUT1)
Atm. Pressure (IN2)
Entropy (OUT2)
Specific Volume
(OUT3)
Superheated Steam (SS) HSVSSTP Temperature (IN1) Entropy (OUT)

(see page 298)
Pressure (IN2) Enthalpy (OUT1)
Atm. Pressure (IN3) Specific Volume
(OUT2)
Control Builder Algorithm Symbol
The Control Builder Algorithm Symbol table provides a definition for each abbreviation used to
create the name for each STEAMTABLE function . They are as follows:
A B B R E V I ATI O N DE F I N I TI O N
CL Compressed Liquid
H Enthalpy
P Pressure
S Entropy
SL Saturated Liquid
SS Super Heated
SV Saturated Vapor
T Temperature
V Specific Volume
Functional Symbol
OW351_R1100 545
5.119 STEAMTABLE
FI E L D RE C O R D
UNIT X1-Byte Data Init Required 0.0 Engineering Units —

(0 - English
(Default), 1 - SI)
See Engineering
Units Table below.
PROQ X4-Byte Data Init Required ON Quality is —
propagated:
 ON
 OFF
IN1 — Variable Required — Analog Input LA
IN2 — Variable Required/ — Analog Input LA

Optional
(depending on
algorithm)
IN3 — Variable Optional — Analog Input LA
OUT — Variable Required/ — Analog output LA
Optional variable
(depending on
algorithm)
OUT1 — Variable Optional — Analog output LA
variable
variable
variable
FLAG — Variable Optional — Digital output LD
variable
Engineering Units
N AME SI EN G L I S H
Temperature (T) C (Celsius) F (Fahrenheit)
Pressure (P) BAR psig

Specific Volume (V) M3/Kg FT3/LBM
Enthalpy (H) KJ/Kg BTU/LBM
Entropy (S) KJ/Kg x K BTU/LBM x R (Rankine)
546 OW351_R1100
5.120 STEPTIME
5.12 0 STEPTIME
Description
The STEPTIME algorithm is an automatic step timer. For the STEPTIME algorithm, the output
(STEP) is an analog real value that always equals an integer from one through 50. The value
increments after a predetermined time delay, which may be different for each time interval. For
example, STEP may stay at 1 for 10 seconds, and then stay at 2 for five minutes. The time
intervals for each step are initialized integers in the algorithm record. The units of time to be used
for all the time intervals must be the same. The X1 field of the algorithm record should be
initialized to indicate which units are to be used according to the table. When all used steps are
completed, the output reverts to Step 1. Steps that have a time interval of zero are skipped.
Functional Symbol
G0= B0= C0= D0= YM=

G1= B1= C1= D1= YL=
G2= B2= C2= D2= E2=
G3= YU= C3= YP= E3=
G4= B4= C4= D4= E4=
G5= B5= C5= D5= YC=
G6= B6= C6= D6= Y9=
G7= B7= C7= YN= E7=
G8= B8= C8= D8= E8=
G9 B9= YT D9= Y8=
The value of STEP is tracked to the value of the track input (TRIN) when the tracking request
(TMOD) is TRUE. If the algorithm is told to track a step that has a zero time interval, the value of
STEP is the next step after this step that has a non-zero time interval. If the algorithm is not
tracking (TMOD = FALSE), the current time and the current step are held constant when the hold
request (HOLD) is TRUE. The time remaining in the timing cycle for the current step is output as
hours (RHRS), minutes (RMIN), and seconds (RSEC) with resolution down to a tenth of a second.
The hours (EHRS), minutes (EMIN), and seconds (ESEC) with resolution down to a tenth of a
second of the time elapsed in the timing cycle for the current step are also available if the optional
outputs are initialized by the user.
OW351_R1100 547
5.120 STEPTIME
Rules
1. The outputs are not scan-removable, but may be set to certain values using the TMOD and
TRIN inputs to track the algorithm to a particular step.
2. The track input and output values are checked for invalid real numbers. If a track request is
received and the track input is invalid, the tracking request is ignored.
If the algorithm calculates an invalid real number for the output, the quality of the output is set
to BAD and the output value is invalid. Otherwise, the quality of the output is set to GOOD.
3. The algorithm is also reset to the first step if a drop failover occurs and the value of the
current step number is invalid. Otherwise, the algorithm remains in the current step.
4. Controller loop time must be set to 100, 200, 500, or 1,000 milliseconds.
FI E L D RE C O R D
DIAG LU - Data Init. Required 100 Tuning Diagram —

Integer Number
HOLD — Variable Required — Input (digital); hold LD, LP
request
TMOD — Variable Required — Input (digital); LD, LP
tracking request
TRIN — Variable Required — Input (analog); tracks LA

the step to this value
UNIT X1-Byte Data Init. Optional 0 Code number for the —
units of time to be
used. (value - units
of time)
0 - 0.1 seconds
(default)
1 - seconds
1 - minutes
3 - hours
T01 G0-Integer Tuning Optional 0 Time interval for —
Constant Step 1

Constant Step 2
Constant Step 3
Constant Step 4
Constant
Step 5
548 OW351_R1100
5.120 STEPTIME
FI E L D RE C O R D

Constant Step 6
Constant Step 7
Constant Step 8
Constant Step 9
Constant Step 10
T11 B0-Integer Tuning Optional 0 Time interval for —
Constant Step 11
Constant Step 12
Constant Step 13
T14 YU-Integer Tuning Optional 0 Time interval for —
Constant Step 14
Constant Step 15
Constant Step 16
Constant Step 17
Constant Step 18
Constant Step 19
Constant Step 20
T21 C0-Integer Tuning Optional 0 Time interval for —
Constant Step 21
Constant Step 22
Constant Step 23
Constant Step 24
Constant Step 25
Constant Step 26
Constant Step 27
OW351_R1100 549
5.120 STEPTIME
FI E L D RE C O R D

Step 28
Constant
Step 29
Constant
T30 YT-Integer Tuning Optional 0 Time interval for —
Constant Step 30
T31 D0-Integer Tuning Optional 0 Time interval for —
Constant Step 31
Constant Step 32
Constant Step 33
T34 YP-Integer Tuning Optional 0 Time interval for —
Constant Step 34
Constant Step 35
Constant Step 36
Constant Step 37
T38 YN-Integer Tuning Optional 0 Time interval for —
Constant Step 38
Constant Step 39
Constant
Step 40
T41 YM-Integer Tuning Optional 0 Time interval for —
Constant Step 41
T42 YL-Integer Tuning Optional 0 Time interval for —
Step 42
Constant
T43 E2-Integer Tuning Optional 0 Time interval for —
Constant Step 43
Step 44
Constant
Constant Step 45
T46 YC-Integer Tuning Optional 0 Time interval for —
Constant Step 46
T47 Y9-Integer Tuning Optional 0 Time interval for —
Constant Step 47
550 OW351_R1100
5.120 STEPTIME
FI E L D RE C O R D

Constant Step 48
Constant Step 49
T50 Y8-Integer Tuning Optional 0 Time interval for —
Constant Step 50
STEP — Variable Required — Output (analog); the LA
current step number
RHRS — Variable Required — Output (analog); the LA
number of hours for
the time remaining in
the current timing
cycle
RMIN — Variable Required — Output (analog); the LA
number of minutes
for the time
remaining in the
current timing cycle
RSEC — Variable Required — Output (analog); the LA
number of seconds
for the time
remaining in the
current timing cycle
EHRS — Variable Optional — Output (analog); the LA
number of hours for
the time elapsed in
the current timing
cycle
EMIN — Variable Optional — Output (analog); the LA
number of minutes
for the time elapsed
in the current timing
cycle
ESEC — Variable Optional — Output (analog); the LA
number of seconds
for the time elapsed
in the current timing
cycle
OW351_R1100 551
5.121 SUM
5.12 1 SUM
Description
The output of the SUM algorithm is the sum of the four individually gained and biased inputs.
Functional Symbol
Tracking Signals
of the analog tracking point. Make sure to connect the upstream algorithm which needs tracking
to SUM’s IN1. This algorithm takes the following action in response to the information found in the
analog input signal TRIN:
Bit description
552 OW351_R1100
5.121 SUM
definitions given in Setting Tracking Signals.
Otherwise, the value of the conditional track bit is transferred to all ou tput track
points. If the Conditional Track bit is set in the track input point, the analog value of
all output track points is calculated based on the analog value of the track input point.
set to BAD. Otherwise, the quality of OUT is set to the worst quality of the two inputs when not in
track output, unless it is invalid. The track output value is not updated if both t he calculated track
Algorithm Record Type =LC
FI E L D RE C O R D
DIAG LU-Integer Data Init Required 84 Tuning diagram —

number
IN1G R1-Real Tuning Required 1.0 Gain on input 1. —
input 1 should
drop is placed into
alarm.
IN1B R2-Real Tuning Required 0.0 Bias on input 1. —
Constant
IN2G R3-Real Tuning Required 1.0 Gain on input 2. —

Constant
IN2B R4-Real Tuning Required 0.0 Bias on input 2. —
Constant
IN3G R8-Real Tuning Required 1.0 Gain on Input 3. —
Constant
OW351_R1100 553
5.121 SUM
FI E L D RE C O R D
IN3B R9-Real Tuning Required 0.0 Bias on Input 3. —

Constant
IN4G S1-Real Tuning Required 1.0 Gain on Input 4. —
Constant
IN4B S2-Real Tuning Required 0.0 Bias on Input 4. —
Constant


TRAT R7-Real Tuning Required 2.5 Track ramp rate —

TBLK X3 - Byte Data Init. Required ON Enable tracking --

local memory
operations. The
choices are:
 ON
 OFF
IN1 — Variable Required — Input 1 analog LA
input
TRIN — Variable Optional — Tracking and LA
Limiting mode
signals and tracking
value; analog input
variable
IN2 — Variable Required — Input 2 analog LA
input
IN3 — Variable Optional — Input 3 analog LA
input
IN4 — Variable Optional — Input 4 analog LA
input
variable
TOUT — Variable Required — Track output value, LA
mode and status
signal for input 1
variable
554 OW351_R1100
5.121 SUM
Function
OUT = IN1GB + IN2GB + IN3GB + IN4GB
IF OUT >= TPSC THEN
OUT = TPSC
ELSE
IF OUT <= BTSC THEN
OUT = BTSC
OW351_R1100 555
5.122 SYSTEMTIME
5.12 2 SYSTEMTIME
Description
While the RUN flag is set, the SYSTEMTIME algorithm accesses the time from the Contoller’s
time (expressed in Universal Time Coordinates (UTC)) and stores it in the separate, optional,
analog outputs for seconds, minutes, hours, day, month, and year.
If the month value is zero (indicating that the time is not updated), or if the RUN flag is FALSE, the
optional Time Not Updated digital output is set.
Functional Symbol
FI E L D RE C O R D
RUN — Variable Required — Input (digital); Run flag LD, LP
SEC — Variable Optional — Output (analog); seconds LA

MIN — Variable Optional — Output (analog); minutes LA
HOUR — Variable Optional — Output (analog); hours LA
DAYM — Variable Optional — Output (analog); day of LA
month
MNTH — Variable Optional — Output (analog); month LA
YEAR — Variable Optional — Output (analog); year LA

TNUP — Variable Optional — Output (digital); time not LD, LP
updated
556 OW351_R1100
5.123 TANGENT
5.12 3 TANGENT
Description
The TANGENT algorithm performs a mathematical tangent function. TANGENT has one input
to the TANGENT of the input. The input to this algorithm is in radians. If an input is only available
in degrees, multiply it by 0.01745329 to convert to radians. If the input is +/ - pi/2 or any integer
multiple of pi, plus pi/2, the output is an invalid number and the drop is placed into alarm.
If the absolute value of the input is greater than 10 18 then the output of the TANGENT algorithm is
invalid and its quality is set to BAD.
Functional Symbol
FI E L D RE C O R D
OUT — Variable Required — Output (analog) LA
Function
OUT=TANGENT(IN1)
OW351_R1100 557
5.124 TIMECHANGE
5.12 4 TIMECHANGE
Description
The TIMECHANGE algorithm checks the Controller’s time (expressed in Universal Time
Coordinates (UTC)) against the old values of the time. If the hours, minutes, or seconds have
changed, the appropriate output digital flags are set; otherwise, they are reset. Each output
produces a one loop, one shot pulse when hours, minutes, or seconds change from a previous
value.
Functional Symbol
FI E L D RE C O R D
OLD H R1-Real Data Init. Optional 0.0 Internal Data —

only. Not to be
initialized by
user.
OLD M R2-Real Data Init. Optional 0.0 Internal Data —
only. Not to be
initialized by
user.
OLD S R3-Real Data Init. Optional 0.0 Internal Data —
only. Not to be
initialized by
user.
HCHG — Variable Required — Output (digital): LD, LP
Change in
Hours flag
MCHG — Variable Required — Output (digital); LD, LP
Change in
Minutes flag
SCHG — Variable Required — Output (digital); LD, LP
Change in
Seconds flag
558 OW351_R1100
5.125 TIMEDETECT
5.12 5 TIMEDETECT
Description
The TIMEDETECT algorithm checks the hour value from the Controller’s time (expressed in
Universal Time Coordinates (UTC)) against the old hour value for a change. If the hour has
changed, the current hour and day of the week are checked against the hour for the change of
day, the hours for the change of shift, and the day and hour for the change of week. The flags are
reset if the hour has not changed. If a change has occurred for the day, shift, or week, the digital
output for that change is TRUE for one loop.
Functional Symbol
FI E L D RE C .
DIAG LU - Data Init. Required 87 Tuning diagram —

Integer number
SHF1 X1-Byte Tuning Required 0 First shift hour/day —

Constant hour
(0 - 23)
SHF2 X2-Byte Tuning Optional 0 Second shift hour —
Constant (0 - 23)
SHF3 X3-Byte Tuning Optional 0 Third shift hour (0 - —
Constant 23)
WEEK X4-Byte Tuning Optional 0 Day of the week —
Constant
(Day range. For
example, 1 = Sunday)
DCHG — Variable Required — Output (digital); LD, LP
Change of Day flag
SHFT — Variable Required — Output (digital); LD, LP

Change of Shift flag
WCHG — Variable Required — Output (digital); LD, LP
Change of Week flag
Note: SHF1 must be initialized. If SHF2 and SHF3 are not initialized or are initialized to zero, the SHFT is
not updated. If WEEK is not initialized or is initialized to zero, WCHG is not updated. DCHG is always
updated.
OW351_R1100 559
5.126 TIMEMON
5.12 6 TIMEMON
Description
If the RUN flag is set, the TIMEMON algorithm provides the following functions:
 If the Controller Date/Time is between the Date 1/Time 1 and Date 2/Time 2 tuning constants,
the optional digital output flag, FLG1 is set TRUE.
 When the Date 2/Time 2 tuning constants are zero, FLG1 is pulsed when the Controller
Date/Time is equal to Date 1/Time 1.
 The MON, DAY, DWK fields of the tuning constants are ignored if zero; therefore, the tuning
constants can represent time-into-year, time-into-month, time-into-week, or time-into-day. (For
example: if HR1 is set to 15.0 and no other FLG1 tuning constants are specified, FLG1 is
pulsed every day at 3:00 p.m.)
 The optional digital output FLG2 is set when the Controller time equals the Start Time tuning
constants, and at every following incremental boundary in the day, as specified by the
Incremental Time tuning constants.
For example: if SHR = 15, SMIN = 30, IMIN = 1, and ISEC = 30, FLG2 is pulsed at 3:30 p.m.
and at each following 90-sec interval until 23:59:59.
Note: Controller time is expressed in Universal Time Coordinates (UTC).
Functional Symbol
Note: The Incremental Time constant should be at least three times the Loop time for the FLG2
output to be seen as a pulse.
FI E L D RE C O R D
DIAG LU - Data Init Required 88 Tuning diagram —

Integer number
RUN — Variable Required — Input (digital); RUN LD, LP
flag
MON1 B1-Integer Tuning Optional 0 Date 1 month —
Constant
DAY1 B2-Integer Tuning Optional 0 Date 1 day —

Constant
560 OW351_R1100
5.126 TIMEMON
FI E L D RE C O R D
DWK1 YU-Integer Tuning Optional 0 Date 1 day of week —

Constant
Valid values are:
0 - none
1 - Monday
2 - Tuesday
3 - Wednesday
4 - Thursday
5 - Friday
6 - Saturday
7 - Sunday
HR1 B4-Integer Tuning Optional 0 Time 1 hour —
Constant
MIN1 B5-Integer Tuning Optional 0 Time 1 minute —
Constant
SEC1 B6-Integer Tuning Optional 0 Time 1 second —
Constant
MON2 B7-Integer Tuning Optional 0 Date 2 month —
Constant
DAY2 B8-Integer Tuning Optional 0 Date 2 day —
Constant
DWK2 B9-Integer Tuning Optional 0 Date 2 day of week —
Constant
Valid values are:
0 - none
1 - Monday
2 - Tuesday
3 - Wednesday
4 - Thursday
5 - Friday
6 - Saturday
7 - Sunday
HR2 C1-Integer Tuning Optional 0 Time 2 hour —
Constant
MIN2 C2-Integer Tuning Optional 0 Time 2 minute —
Constant
SEC2 C3-Integer Tuning Optional 0 Time 2 second —
Constant
SHR C4-Integer Tuning Optional 0 Start time hour —
Constant
SMIN C5-Integer Tuning Optional 0 Start time minute —
Constant
OW351_R1100 561
5.126 TIMEMON
FI E L D RE C O R D
SSEC C6-Integer Tuning Optional 0 Start time second —

Constant
IHR G3-Integer Tuning Optional 0 Incremental time —
Constant hour
IMIN G4-Integer Tuning Optional 0 Incremental time —
Constant minute
ISEC B0-Integer Tuning Optional 0 Incremental time —
Constant second
FLG1 — Variable Optional — Output (digital); LD, LP
FLG1 flag output
FLG2 — Variable Optional — Output (digital); LD, LP
FLG2 flag output
562 OW351_R1100
5.127 TRANSFER
5.12 7 TRANSFER
Description
The TRANSFER algorithm performs a transfer between two inputs. The output is equal to the IN2
input if the digital input FLAG is TRUE, and to the IN1 input if the digital input FLAG is FALSE.
If the algorithm generates an invalid output value for the selected input, the other input is
selected, and the algorithm generates a valid output value if the input for the other point is valid.
The algorithm automatically performs a bumpless transfer between the track input and the
selected input when a tracking request is removed. The algorithm ramps to the selected input
(IN1 or IN2) at the specified track ramp rate TRRx (TRR1 or TRR2).
Internal tracking may be selected to allow a bumpless transfer between IN1 and the IN2 inputs.
Individual track ramp rates may be initialized to ramp from the IN1 to the IN2 and from the IN2 to
the IN1.
The Output Direction Forcing (ODF) option forces a change in the direction of an output value in
the transition state. When the ODF option is ON, the output value changes monotonically (strictly
increasing or decreasing the function between ordered sets that preserves the given order)
towards the value of the selected input. If the ODF option is OFF, the output value changes
towards the value of the selected input; however, this may not always be monotonically.
Differences in the algorithm behavior depend on the direction of changes of the selected input.
Refer to the following two examples of ODF:
Example 1
The following example presents a scenario when the transfer algorithm behavior is same
regardless of whether ODF = ON or ODF = OFF.
Properties
P R O P E R TI E S DE S C R I P TI O N
Scenario Transfer from a lower to a higher value.

During the transition, the selected value is constant in a few steps and then
the value starts increasing.
Parameters  ODF = ON
 SLEW = ON
 TRRx = 1.0 (TRR1 = 1.0 and TRR2 = 1.0)
Results when ODF = OFF Output value (green line) increases with TRRx ramp rate when the selected
signal (blue line) is constant.
When the selected value increases, the output value changes with ramp
rate equal to RAMP_OF_SELECTED_SIGNAL + TRRx. This means that
the output changes with the speed equal to the speed of changes of the
selected signal and TRR1 parameter.
Results when ODF = ON The algorithm behavior is the sam e as when ODF = OFF.
OW351_R1100 563
5.127 TRANSFER
The following figure shows that the Transfer algorithm behavior is same regardless of whether
ODF = ON or ODF = OFF.
Figure 21: Transfer algorithm behavior is same for ODF = ON and ODF = OFF
Example 2
The following example presents a scenario when the Transfer algorithm behavior is different
when the ODF = ON or ODF = OFF.
Note: ODF=ON is the default setting.
Properties
P R O P E R TI E S D E S C R I P TI O N
Scenario Transfer from a lower to a higher value.

During the transition, the selected value is constant in a few steps and then
the value starts decreasing.
Parameters  ODF = ON
 SLEW = ON
 TRRx = 1.0 (TRR1 = 1.0 and TRR2 = 1.0)
564 OW351_R1100
5.127 TRANSFER
P R O P E R TI E S D E S C R I P TI O N
Results when ODF = OFF Output value (green line) decreases with TRRx ramp rate when the
selected signal (blue line) is constant.
When the selected value decreases, the output value changes with ramp
rate equal to RAMP_OF_SELECTED_SIGNAL + TRRx. This means that
the output changes with the speed equal to the speed of change of the
selected signal and TRR1 parameter.
Note: In this example, the RAMP_OF_SELECTED_SIGNAL is negative

and the output value decreases; however, it will not happen when ODF is
ON. See the following description "Results when ODF = ON."
Results when ODF = ON Output (green line) moves towards the selected signal (blue line) with the
ramp rate is equal to TRRx in both cases: when the selected value is
constant and also when selected value decreases.
The ramp rate equals to RAMP_OF_SELECTED_SIGNAL + TRRx only
when the value of the selected signal and the value of the output are
moving in the same direction. One of the following situations is possible:
 The output is transferring from a lower to a higher value and the selected
value is increasing.
 The output is transferring from a higher to a lower value and the selected
value is decreasing.
The following figure shows the Transfer algorithm behavior when ODF = OFF (default settings).
Figure 22: Transfer algorithm behavior when for ODF = OFF (default settings)
OW351_R1100 565
5.127 TRANSFER
The following figure shows that the Transfer algorithm behavior when ODF = ON.
Figure 23: Transfer algorithm behavior when for ODF = ON
The rules are analogical (this means that the algorithm behavior is very similar; however, not
identical) for transfer from a higher to a lower value and from a lower to a higher value.
566 OW351_R1100
5.127 TRANSFER
Summary
 When the ODF parameter is OFF (default value), the output value changes with ramp rate
equal to RAMP_OF_SELECTED_S IGNAL + TRRx.
 When the ODF parameter is ON, the output value changes with ramp rate equal to
RAMP_OF_SELECTED_SIGNA L + TRRx only, when the value of the selected signal and
value of the output are going in the same direction (Example 1). Otherwise (Example 2), the
output value is changing with ramp rate equal to TRRx.
Note: If the algorithm receives an invalid value as the selected input, or calculates an invalid
value as the output, the drop is placed into alarm.
Functional Symbol
Packed Digital Tracking Signals
in the analog input signal TRIN:
Bit description
BI T DE S C R I P TI O N TRK1 S I G N AL TRK2 S I G N AL
16 Track Implemented and passed Implemented and passed through or

through or set TRUE when IN1 set TRUE when IN2 input is not
input is not selected. selected.
17 Track if lower Passed through* Passed through*
18 Track if higher Passed through* Passed through*
20 Raise inhibit Passed through*** Passed through***
21 Conditional Track No Action Not used
OW351_R1100 567
5.127 TRANSFER
BI T DE S C R I P TI O N TRK1 S I G N AL TRK2 S I G N AL
*** If the algorithm is being told to track, then the Conditional track bit is ignored. Otherwise, the value of
the conditional track bit is transferred to all output track points. If the Conditional Track bit is set in the
track input point, the analog value of all output track points is calculated based on the analog value of the
track input point.
The high and low limit flags, and the tracking signals from the algorithm are output to, TRK1 and
TRK2, to be used for display and by upstream algorithms. If the output value is invalid, the quality
of OUT is set to BAD. Otherwise, the quality of OUT is set to the quality of the selected input.
When tracking, the quality is set to the quality of the track input variable.
Note: If the calculated track output is invalid, then the IN2 output is equal to the IN2 inputs, and
the IN1 track output is equal to the IN1 variable input, if the inputs are valid. If the calculated
track outputs and the input values are invalid, then the IN2 and IN1 track outputs are not
updated.
FI E L D RE C .

number
* IN1G R3-Real Tuning Required 1.0 Gain on input1. The —
Constant gain on the input1
should never be
initialized to zero; if it
is, the drop is placed
into alarm.
* IN1B R4-Real Tuning Required 0.0 Bias on input 1 —
Constant
* IN2G R1-Real Tuning Required 1.0 Gain on input2. The —

Constant gain on the input2
should never be
initialized to zero; if it
is, the drop is placed
into alarm.
568 OW351_R1100
5.127 TRANSFER
FI E L D RE C .
* IN2B R2-Real Tuning Required 0.0 Bias on input2 —

Constant


SLEW X1-Byte Data Init. Required OFF Internal tracking —

Bit 0 option:
OFF: No tracking
during a transfer.
ON: Tracking is
implemented during
a transfer.
TRR1 R7-Real Tuning Required 2.5 Tracking ramp rate —
Constant from input1 to input2
or from the track
input to the input2
(units per second)
TRR2 R9-Real Tuning Required 2.5 Tracking ramp rate —
Constant from input2 to
input1or from the
track input to the
input1 (units per
second)
OTRK X1-Byte Data Init. Required ON Output Tracking —
Bit 2 Option:
OFF = output value
does not track.
ON = output value
tracks.
FLAG — Variable Required — Digital input signal to LD, LP
select output
(required); you must
enter the name of a
point.
* IN2 — Variable Required — Input2 (analog) LA
* TRK2 — Variable Required — Track output value, LA

node and status
signals for Input 2
variable
* IN1 — Variable Required — Input1 (analog) LA
* TRK1 — Variable Required — Track output value LA

mode and status
signals for input 1
variable
OW351_R1100 569
5.127 TRANSFER
FI E L D RE C .

variable
TRIN — Variable Optional — Tracking and limiting LA
mode signals and
tracking value;
analog input variable
ODF X1-Byte Data Init Required ON Output direction
Bit 4 forcing option:
 OFF = Output
value direction is
not forced in
transition state.
 ON = Output value
direction is forced
in transition state.
* Parameter name may vary depending on software release.
Function
IF FLAG = TRUE THEN

OUT = (IN2 x IN2 GAIN) + IN2 BIAS
ELSE
OUT = (IN1 x IN1 GAIN) + IN1 BIAS
IF OUT >= TPSC THEN
OUT = TPSC
ELSE
IF OUT <= BTSC THEN
OUT = BTSC
570 OW351_R1100
5.128 TRANSLATOR
5.12 8 TRANSLATOR
Description
The TRANSLATOR algorithm translates the output based on the input of a predefined table. For
the TRANSLATOR algorithm, the input value (IN1) is first rounded to an integer value. This
integer is then used as an index number to access one of the 50 integers initialized in the
algorithm record. The selected integer from the algorithm record is output as a real number in the
output record (OUT). If the input value (always rounds down to an integer) is less than one or
greater than 50, no action is taken and OUT is not changed.
If the input value selects an integer between 1 and 50 that has not been initialized, then OUT
equals zero. The maximum integer number that can be initialized for I01 through I50 is + 32,767.
If the input value (when rounded to an integer) is less than 1 or greater than 50, or if the input
value is invalid, no action is taken, and OUT is not changed. However, if the input value is invalid,
the quality of OUT is set to BAD.
The quality of the input is propagated to the output.
Functional Symbol
G0= B0= C0= D0= YM=

G1= B1= C1= YQ= YL=
G2= B2= C2= D2= E2=
G3= YU= C3= YP= E3=
G4= B4= C4= D4= E4=
G5= B5= C5= D5= YC=
G6= B6= C6= D6= Y9=
G7= B7= C7= YN= E7=
G8= B8= C8= D8= E8=
G9 B9= YT D9= Y8=
OW351_R1100 571
5.128 TRANSLATOR
FI E L D RE C .
DIAG LU-Integer Data Init. Required 103 Tuning diagram —

Number
I01 G0-Integer Tuning Optional 0 Possible selected —
Constant output value

I11 B0-Integer Tuning Optional 0 Possible selected —
I14 YU-Integer Tuning Optional 0 Possible selected —
572 OW351_R1100
5.128 TRANSLATOR
FI E L D RE C .

I21 C0-Integer Tuning Optional 0 Possible selected —
I30 YT-Integer Tuning Optional 0 Possible selected —
I31 D0-Integer Tuning Optional 0 Possible selected —
I32 YQ-Integer Tuning Optional 0 Possible selected —
I34 YP-Integer Tuning Optional 0 Possible selected —
I38 YN-Integer Tuning Optional 0 Possible selected —
I41 YM-Integer Tuning Optional 0 Possible selected —
OW351_R1100 573
5.128 TRANSLATOR
FI E L D RE C .
I42 YL-Integer Tuning Optional 0 Possible selected —

I43 E2-Integer Tuning Optional 0 Possible selected —
I46 YC-Integer Tuning Optional 0 Possible selected —
I47 Y9-Integer Tuning Optional 0 Possible selected —
I50 Y8-Integer Tuning Optional 0 Possible selected —
574 OW351_R1100
5.129 TRANSPORT
5.12 9 TRANSPORT
Description
The TRANSPORT algorithm samples the analog input point and outputs the sample value with a
time delay. The sampling time (TSAM) and the number of samples (NSAM) control the delay
(DELAY = TSAM x NSAM). If TSAM is less than the loop time of TRANSPORT, TSAM equals the
loop time. The output is zero until the number of samples have been collected. Additional
TRANSPORT algorithms can be strung together in series to obtain longer delay times, if required.
NSAM is continually limited to a range of 1 through 25. If NSAM is negative or zero, then NSAM
goes to 1. If NSAM is greater than 25, NSAM goes to 25.
The value of the analog input (IN1) is checked for invalid real numbers. If the input value is
invalid, the output value is invalid and the quality of the output is set to BAD. Otherwise, the
quality of the output is set to GOOD.
Functional Symbol
IN1
~ OR
IN1 ~ OUT
OUT
FI E L D RE C O R D

number
TSAM T9-Real Data Init. Required 0 Sampling time in —
seconds
NSAM G0-Integer Data Init. Required 0 Number of samples —
(1-25)
OW351_R1100 575
5.129 TRANSPORT
FI E L D RE C O R D
INIT X1-Byte Data Init. Optional 2 Sample initialization —

0 or 1 = Samples
are initialized to zero
when the algorithm
is first added to the
drop; samples are
not changed at
power-up, reset, or
failover, and may
contain old values.
2 = Samples are
initialized to the
current value of the
IN1 analog input on
power-up, reset, and
failover (as well as
when the algorithm
drop).
3 = Samples are
initialized to the
current value of the
OUT analog output
on power-up, reset,
and failover (as well
as when the
algorithm is first
added to the drop).
4 = Samples are
initialized to zero on
power-up, reset, and
failover (as well as
when the algorithm
drop).
576 OW351_R1100
5.130 TRNSFINDX
5.13 0 TRNSFINDX
Description
The TRNSFINDX algorithm selects the output analog value from up to 64 outputs which hold the
input IN1. The number of outputs is determined by NMIN which must be less than or equal to 64.
The output selected is based on the index which is the second analog input (IN2). If the index is
less than or equal to 0, or if an index greater than NMIN is selected, the input is not stored.
Functional Symbol
FI E L D RE C O R D
NMIN X1-Byte Data Init Required 1 Select maximum —

number
IN1 — Variable Required — Analog input value LA
IN2 — Variable Required — Analog index LA
value
O01 — Variable Required — Analog output LA
value
O02 — Variable Optional — Analog output LA
value
•
•
•
O64
OW351_R1100 577
5.131 TRUTHTB L
5.13 1 TRUTHTBL
Description
This digital output of TRUTHTB L is selected from one of 256 possible digital values. The 16
integer values (field B0 through C5) contain the 256 possible digital output states; each bit in an
integer represents a possible digital output (where: 0 = FALSE and 1 = TRUE). The output
selected is based on a binary address formed by eight digital inputs. The integer binary address
values may be input as hexadecimal numbers. Refer to "Converting Algorithm Binary to
Hexadecimal" (see page 6) for information on how to create a hexadecimal number from 16 bits.
The inputs are optional; therefore, any input that is not specified is assumed to have a value of
zero (FALSE). The input binary address may range from zero to 255. The letter "A" represents Bit
0 in the address and the letter "H" represents Bit 7 in the address. For example, if the input binary
address is 36 (C and F are TRUE), the digital output would be based on the value of Bit 4 (the
fifth bit) in the third integer.
Symbol
Note: The size of the algorithm symbol varies as required to enclose the logic symbols being
executed by this algorithm.
FI E L D RE C O R D
A - Variable Optional - Input (digital signal) LD, LP
B - Variable Optional - Input (digital signal) LD, LP

C - Variable Optional - Input (digital signal) LD, LP
D - Variable Optional - Input (digital signal) LD, LP
E - Variable Optional - Input (digital signal) LD, LP
F - Variable Optional - Input (digital signal) LD, LP
578 OW351_R1100
5.131 TRUTHTB L
FI E L D RE C O R D
G - Variable Optional - Input (digital signal) LD, LP

H - Variable Optional - Input (digital signal) LD, LP
DIAG LU - Byte Data Init. Optional 91 Tuning Diagram -
Number (default
value = 91)
I01 B0 - Integer Tuning Optional 0 Output States 0 -
Constant through 15
Constant through 31
Constant through 47
Constant through 63
Constant through 79
Constant through 95
Constant through 111
I11 C0 - Integer Tuning Optional 0 Output States 160 -
OW351_R1100 579
5.131 TRUTHTB L
FI E L D RE C O R D

OUT - Variable Required - Output (digital LD, LP
signal)
Note: Note the following regarding this algorithm:
1. The truth table is constructed as an ordered binary sequence from 0 to 255.

2. The output of the truth table is defined by the user via the integers B0 through C5.
3. The integer parameters in the Control Builder and Signal Diagrams must be input in decimal form.
The least significant group of 16 bits is located in the first output control state 0 through 15 (B0), and
so on until the most significant bit group.
Application Example
TRUTHTB L is a general purpose, logic algorithm. The output represents a Boolean equation of up
to eight inputs. In general, TRUTHTBL condenses discrete logic elements (for example, AND,
OR, NOT, XOR, NAND, or NOR) into one algorithm call. The logic statement of the output is
stated as a Boolean equation and then translated into the proper tuning constants. This
translation can be done manually.
The following figure illustrates how TRUTHTBL is shown on a functional drawing.
580 OW351_R1100
5.131 TRUTHTB L
The following figure shows how the tuning contents can be manually derived.
OW351_R1100 581
5.132 TSLH
5.13 2 TSLH
Description
TSLH calculates Temperature for Saturated Liquid given its Enthalpy (H). It is one of the functions
of the STEAMTABLE (see page 544) algorithm.
Functional Symbol
TSLH input and output values
(INPUT 1) ENTH -0.017864220 906.01

(OUT 1) TEMP 32.0 705.47
582 OW351_R1100
5.133 TSLP
5.13 3 TSLP
Description
TSLP calculates Saturation Temperature of Saturated Liquid given its Pressure. It is one of the
functions of the STEAMTABLE algorithm (see page 544).
Functional Symbol
TSLP input and output values
(INPUT 1) PRES 0.0885891400 3208.23

(OUT 1) TEMP 32.0 705.47
OW351_R1100 583
5.134 UNPACK16
5.13 4 UNPACK16
Description
The UNPACK16 algorithm specifies up to 16 optional, packed digital values in the A2 record field
of a packed LP point record as optional outputs of this algorithm. These outputs may be initial ized
as any combination of LD and DD records. The bit in the A2 record field that corresponds to the
output digital point number is moved to the output digital point record.
Note: The UNPACK16 algorithm only tak es LP and DP record types as inputs.
Functional Symbol
FI E L D RE C O R D
PBPT — Variable Required — Input (packed point) LP, DP

(PIN)
D0 — Variable Optional — Output (digital) for LD
Bit 0
Bit 1
Bit 2
Bit 3
Bit 4
584 OW351_R1100
5.134 UNPACK16
FI E L D RE C O R D

Bit 5
Bit 6
Bit 7
Bit 8
Bit 9
Bit 10
Bit 11
Bit 12
Bit 13
Bit 14
Bit 15
OW351_R1100 585
5.135 VCLTP
5.13 5 VCLTP
Description
VCLTP calculates Specific Volume of Compressed Liquid given its Temperature and Pressure. It
is one of the functions of the STEAMTABLE algorithm (see page 544).
Functional Symbol
VCLTP input and output values
(INPUT 1) TEMP 32.0 705.47

(INPUT 2) PRES 0.0885891400 16000.00
(OUT 1) VOL 0.0152 0.05078
586 OW351_R1100
5.136 VSLT
5.13 6 VSLT
Description
VSLT calculates Specific Volume of Saturated Liquid given its Temperature. It is one of the
functions of the STEAMTABLE algorithm (see page 544).
Functional Symbol
VSLT input and output values
(INPUT 1) TEMP 32.0 705.47

(OUT 1) ENTR -0.000036890 1.0612
OW351_R1100 587
5.137 XOR
5.13 7 XOR
Description
The XOR algorithm performs a mathematical exclusive OR function. For the XOR algorithm, the
output is the logical, exclusive “OR” of the two inputs (that is, if one input is TRUE and the other
input is FALSE, the output is TRUE; otherwise, the output is FALSE).
Functional Symbol
FI E L D RE C O R D
IN1 — Variable Required — Input (digital) LD, LP
IN2 — Variable Required — Input (digital) LD, LP

OUT — Variable Required/ — Output (digital) LD, LP
Optional
Function
IF IN1 = IN2
THEN OUT = FALSE
ELSE
OUT = TRUE
588 OW351_R1100
5.138 X3STEP
5.13 8 X3STEP
Description
The X3STEP algorithm controls devices that must be kept within a certain tolerance and tuned by
an operator. The algorithm receives the Input demand (IN1) and the position feedback (IN2) of a
device (both are defined within a range of 0-100%). The difference (Error = IN11 - IN2), along with
other user-entered configuration parameters determine how the algorithm attempts to position the
equipment so that the error is zero.
The algorithm moves the equipment by energizing two digital outputs (DIG1 and DIG2)
associated with the device. The digital outputs may be energized in one of three ways (thus, the
algorithm's name X3STEP) to move the device to the demanded position:
 Maintained steadily ON.
 Pulsed (coarse-pulsed and fine pulsed) ON and OFF.
 Maintained steadily OFF.
Functional Symbol
The action of each digital output depends on the value of the error, and the user-entered
parameters: ON1, COR1, FNE1, ON2, COR2, and FNE2.
The parameters ON1, COR1, and FNE1, affect DIG1 when the error is above zero. The
parameters ON2, COR2, and FNE2, affect DIG2 when the error is below zero. The bar graph
below shows the relationship of the parameters with respect to the error.
% Error below zero % Error above zero

-----------------------------------------------------------
ON2 COR2 FNE2 0 FNE1 COR1 ON1
OW351_R1100 589
5.138 X3STEP
where:
FO R DIG2 FO R DIG1
ON2 = If the error is below or equal to ON2, the ON1 = If the error is above or equal to ON1 the
digital output DIG2 is maintained ON. digital output DIG1 is maintained ON.
COR2 = If the error is below or equal to COR2, the COR1 = If the error is above or equal to COR1,
digital output DIG2 is coarse pulsed. the digital output DIG1 is coarse pulsed.
FNE2 = If the error is below or equal to FNE2, the FNE1= If the error is above or equal to FNE1, the
digital output DIG2 is fine pulsed. If the error is digital output DIG1 is fine pulsed. If the error is
below zero, but above FNE2, DIG2 is maintained above zero, but below FNE1, DIG1 is maintained
OFF. OFF.
Operation
Suppose an X3STEP algorithm had the following parameters:
ON2 COR2 FNE2 0 FNE1 COR1 ON1
-----------------------------------------------------------
-15 -12 -8 8 12 15
If the initial error is above or equal to 15, the digital output (DIG1) is set ON. DIG1 is maintained
ON until the error falls below 15. At this point, the DIG1 output begins and continues coarse
pulsing until the error is below 12. Once this occurs, the DIG1 output begins and continues fine
pulsing until the error is below 8. When this occurs, DIG1 is set OFF. Please note that the
converse of the above definitions are TRUE when the error is below 0.
In general, X3STEP turns off both its digital outputs when it detects errors in configuration or
operation. They remain OFF until the error conditions clear. Also, when errors occur on input IN2,
OUT is not updated but retains its last valid value.
The digital outputs are both set OFF (DIGI1 = 0 and DIGI2 = 0) under any of the following
conditions:
 The IN1 input has BAD quality, is an invalid real number, or is not being updated across the
Ovation network.
 The IN2 input has BAD quality, is an invalid real number, or is not being updated across the
Ovation network.
 The digital input DEVO (Operational Status of Device) is set indicating that there is a problem
with the device.
 The error is zero or below FNE1 for DIG1. The error is zero or above FNE2 for DIG2.
 An on time span of 0 or less is invalid. This invalid configuration is reported by setting t he
quality of OUT to BAD and setting bit 3 of its 1W field. This error is reported at runtime.
590 OW351_R1100
5.138 X3STEP
 The algorithm has been incorrectly configured by setting ON1, COR1, FNE1, or ON2, COR2,
and FNE2 all to zero. This invalid configuration is reported by setting the quality of OUT to
BAD and bit 3 of its 1W field. This error is reported at runtime. The outputs are set to 0 for one
execution loop under any of the following conditions:
 The Controller is reset (hardware or software reset).
 A failover occurs.
 The algorithm is modified and downloaded.
Tracking Signals
This algorithm ignores the TRIN tracking signals. During first pass after a reset, or failover, and
anytime the DEVO digital is TRUE, Bit 16 of TOUT is set TRUE causing the upstream algorithm
to track OUT. Bit 16 of TOUT is set FALSE at all other times.
Bits 20 and 31 of TOUT are set ON when the IN2 value reaches 100 percent or greater. This
indicates the algorithm has reached the High Limit and requests the upstream algorithm to inhibit
raising the output.
Bits 19 and 30 of TOUT are set ON when the IN2 value reaches 0 percent or less. This indicates
that the algorithm has reached the Low Limit and requests the upstream algorithm to inhibit
lowering the output. All other bits (17-18 and 21-29) of TOUT are not used.
The TOUT value output is set equal to OUT and its quality is always set to GOOD.
Algorithm Configurations
 To maintain the digital outputs ON at all times when the error is not zero, the settings
presented in the following tables are required:
DIG1 is ON all time, coarse and fine pulsing is eliminated
DIG1 ER R O R FNE1 COR1 ON1
ON >0 0 0 >0 (close to zero)
Example for DIG1 is ON all time, coarse and fine pulsing is eliminated
ON 0.1 0 0 0.00001
ON all time, coarse and fine pulsing is eliminated
ON <0 0 0 0 (close to zero)
OW351_R1100 591
5.138 X3STEP
Example for DIG2 is ON all time, coarse and fine pulsing is eliminated
ON -0.1 0 0 -0.00001
 To eliminate coarse pulsing of a digital the settings presented below in the tables are
required.
If the error is initially above ON1 (or below ON2), the digital remains ON until the error falls below
ON1 (or above ON2). When this occurs and COR1 (or COR2) equals zero, coarse pulsing is
ignored and fine pulsing begins. Fine pulsing continues until the error falls below FNE1
(or above FNE2). At this point the digital is maintained OFF.
DIG1 is ON or fine pulsing (coarse pulsing is eliminated)
ON >ON1 <ON1 0 >FNE1

Fine pulsing >FNE1 and <ON1 <ON1 0 >FNE1
OFF >0 and <FNE1 <ON1 0 >FNE1
Example DIG1 is ON or fine pulsing (coarse pulsing is eliminated)
ON 11 2 0 10
Fine pulsing 5 2 0 10
OFF 1 2 0 10
DIG2 is ON or fine pulsing (coarse pulsing is eliminated)
ON <ON2 >ON2 0 <FNE2

Fine pulsing >ON2 and <FNE2 >ON2 0 <FNE2
OFF <FNE2 and <0 >ON2 0 <FNE2
592 OW351_R1100
5.138 X3STEP
Example DIG2 is ON or fine pulsing (coarse pulsing is eliminated)
ON -11 -2 0 -10
Fine pulsing -5 -2 0 -10
OFF -1 -2 0 -10
 To eliminate fine pulsing of a digital the settings presented below in the tables are required.
If the error is initially above ON1 (or below ON2), the digital remains ON until the error falls below
ON1 (or above ON2). At this point, coarse pulsing begins and is maintained until the error falls
below COR1 (or above COR2). When this occurs and FNE1 (or FNE2) equals zero, fine pulsing is
ignored and the digital is maintained OFF.
DIG1 is ON or coarse pulsing (fine pulsing is eliminated)
ON >ON1 0 <ON1 >COR1

Coarse pulsing >COR1 and <ON1 0 <ON1 >COR1
OFF >0 and <COR1 0 <ON1 >COR1
Example DIG1 is ON or coarse pulsing (fine pulsing is eliminated)
ON 11 0 2 10
Coarse pulsing 5 0 2 10
OFF 1 0 2 10
DIG2 is ON or coarse pulsing (fine pulsing is eliminated)
ON <ON2 0 >ON2 <COR2
Coarse pulsing >ON2 and <COR2 0 >ON2 <COR2

OFF >COR2 and <0 0 >ON2 <COR2
OW351_R1100 593
5.138 X3STEP
Example DIG2 is ON or coarse pulsing (fine pulsing is eliminated)
ON -11 0 -2 -10
Coarse pulsing -5 0 -2 -10

OFF -1 0 -2 -10
 To eliminate maintaining the digital outputs ON steady when the error is not zero, the settings
presented below in the tables are required.
Assumes a non-zero value for COR1, COR2, FNE1, or FNE2. If the error is initially above COR1
(or below COR2), the digital is pulsed coarsely until the error falls below COR1 (or above COR2).
When this occurs, fine pulsing begins and continues until the error falls below FNE1 (or above
FNE2). At this point the digital is maintained OFF.
DIG1 is coarse or fine pulsing (ON state is eliminated)
Coarse pulsing >COR1 <COR1 >FNE1 0
Fine pulsing >FNE1 and <COR1 >FNE1 0

<COR1
OFF >0 and <FNE1 <COR1 >FNE1 0
Example DIG1 is coarse or fine pulsing (ON state is eliminated)
Coarse pulsing 11 2 5 0
Fine pulsing 3 2 5 0
OFF 1 2 5 0
DIG2 is coarse or fine pulsing (ON state is eliminated)
Coarse pulsing <COR2 <COR2 >FNE2 0
Fine pulsing >COR2 and <COR2 >FNE2 0

<FNE2
OFF >FNE2 and <0 <COR2 >FNE2 0
594 OW351_R1100
5.138 X3STEP
Example DIG2 is coarse or fine pulsing (ON state is eliminated)
Coarse pulsing -11 -2 -5 0
Fine pulsing -3 -2 -5 0
OFF -1 -2 -5 0
 The ON and OFF times for the coarse and fine pulses are determined from the user-entered
off-time and on-time span tuning fields.
 OUT is assigned the value of IN2, where IN2 is the position feedback of device defined and
should be defined in range 0-100 percent.
 If IN2 is less than zero, OUT is assigned a value of zero. If IN2 is greater than 100, OUT
is assigned a value of 100. Otherwise, OUT is assigned the value of IN2.
 If IN2 has BAD quality, or is an invalid real number, OUT retains its last valid value and its
quality is set to BAD.
The quality of OUT and its 1W field report algorithm error conditions are described below:
Quality
OUT Q U AL I T Y 1 W BI T S E T DE S C R I P TI O N
GOOD NONE Normal .
BAD NONE The position feedback IN2 has BAD quality.
BAD Bit 3 Invalid configuration has been entered. BAD parameter

(ON1, COR1, FNE1, ON2, COR2, FNE2) or time span
(CTM1, FTM1, CTM2, FTM2) or on-time/off-time (FDY1,
FDY2, CDY1, CDY2).
Tuning Constants
 For proper operation, ON2 < COR2 and COR1 < ON1, if any of ON2, COR2, COR1 and ON2
have non-zero values. The algorithm does not check for this invalid configuration and
algorithm results may be improper for the wrong configuration.
 For proper operation, COR2 < FNE2 and FNE1 < COR1, if any of COR2, FNE2, FNE1 and
COR1 have non-zero values. The algorithm does not check for this invalid configuration and
algorithm results may be improper for the wrong configuration.
 Set CTM1, CTM2, FTM1, FTM2 (time spans for pulsing) in multiples of the control task’s loop
time.
If CTM1, CTM2, FTM1, and FTM2 and the accompanying ON and OFF times that are less
than one loop time, the algorithm assumes those times are equal to one loop time.
OW351_R1100 595
5.138 X3STEP
N AME LC T YP E RE Q U I R E D / DE F AU L T D E S C R I P TI O N M I N I MU M
AL G O R I TH M O P TI O N AL V AL U E POI N T
RE C O R D RE C O R D
FI E L D
DIAG LU-Integer Data Init. Required 58 Tuning diagram. —
ON1 T9-Real Tuning Required 10 Steady ON limit —

Constant (number of error
above 0 at which
DIG1 turns ON).
COR1 S1-Real Tuning Required 5 Coarse ON limit —
above 0 at which
DIG1 begins coarse
pulsing).
FNE1 T1-Real Tuning Required 2 Fine ON limit —
above 0 at which
DIG1 begins fine
pulsing).
ON2 U1-Real Tuning Required -10 Steady ON limit —
below 0 at which
DIG2 turns ON).
COR2 S2-Real Tuning Required -5 Coarse ON limit —
below 0 at which
DIG2 begins coarse
pulsing).
FNE2 T2-Real Tuning Required -2 Fine ON limit —
below 0 at which
DIG2 begins fine
pulsing).
CTM1 S6-Real Tuning Required 2000 Coarse on-time span —
Constant in millisecond for
DIG1.
CDY1 S7-Real Tuning Required 2000 Coarse off-time span —
DIG1.
CTM2 S8-Real Tuning Required 2000 Coarse on-time span —
DIG2.
CDY2 S9-Real Tuning Required 2000 Coarse off-time span —
DIG2.
FTM1 T4-Real Tuning Required 1000 Fine on-time span in —
Constant millisecond for DIG1.
596 OW351_R1100
5.138 X3STEP
FI E L D
FDY1 T5-Real Tuning Required 1000 Fine off-time span in —

FTM2 T6-Real Tuning Required 1000 Fine on-time span in —

FDY2 T7-Real Tuning Required 1000 Fine off-time span in —

IN1 — Variable Required — Analog input – it is LA

the demand value
for the device
defined in range 0-
100%.
IN2 — Variable Required — Analog input – it is LA
the feedback value
from the device
defined in range 0-
100%.
TOUT — Variable Required — Analog output - track LA
output value.
Bit 16 is set TRUE
during the first pass
and when DEVO
input is TRUE.
Typically used for
initialize upstream
PID algorithm to
accomplish
bumpless transfer.
Bit 19 and 30
indicate POS is at
low limit.
Bit 20 and 31
indicate POS is at
high limit.
Contains the value
of the position
feedback signal. The
quality of TOUT is
always GOOD;
sensor errors are not
reported. Used to
initialize upstream
PID algorithms with
bump transfer.
OW351_R1100 597
5.138 X3STEP
FI E L D
DEVO — Variable Optional — Packed Input - Bit 0 LP

indicates the
operational state of
the device where:
0 = operational
1 = non-
operational
OUT — Variable Required — Analog output – it LA
contains the value of
the position
feedback signal IN2.
The quality and IN
field of OUT are
used to report error
conditions.
TRIN — Variable Optional — Analog input - LA
tracking and limiting
mode. Signals,
tracking value, and
analog input
variable.
DIG1 — Variable Required — Digital output1. LD
DIG2 — Variable Required — Digital output2. LD
598 OW351_R1100
5.139 2XSELECT
5.13 9 2XSELECT
Description
The 2XSELECT algorithm monitors two analog transmitter inputs for quality and deviation from
each other. The output is either one of the two input values; the higher value, the lower value, or
the average of the two values, depending on the mode selected. You select the mode through the
use of the TMOD and MODE tracking inputs, the Operator’s Keyboard function keys, or the
Control Builder.
Functional Symbol
The Control Indicator Word is used to specify which of the Average, Lower and Higher modes are
inhibited, and the type of quality of the input that sets the Quality Alarm for that point. The
Average, Lower, and Higher modes cannot be selected if they are inhibit ed by the Control
Indicator Word, or when either of the transmitters is in Quality Alarm, or when the deviation
between the two transmitter values is greater than the Control Deviation Deadband tuning
constant (CNDB).
The Transmitter A mode cannot be selected when Transmitter A is in Quality Alarm and
Transmitter B is not in Quality Alarm. The algorithm goes to Transmitter A mode when both
transmitters are in Quality Alarm, or when Transmitter B is in Quality Alarm. The Transmitter B
mode cannot be selected when Transmitter B is in Quality Alarm. The algorithm goes to
Transmitter B mode when Transmitter A is in Quality Alarm and Transmitter B is not in Quality
Alarm.
OW351_R1100 599
5.139 2XSELECT
On the first pass of the algorithm, if the Tracking Input (MODE) is initialized by the user, the mode
is set according to the rounded value of the tracking input as follows:
Mode
M O D E V AL U E M O D E S E L E C TE D
1 Average
2 Lower
3 Higher
4 Transmitter A
5 Transmitter B
If the rounded value of the tracking input is not 1 through 5, or if the trac king input was not
initialized, the mode is set to Average mode. If the mode selected on the first pass is inhibited, or
if it is blocked by a Quality Alarm or a Deviation Alarm, as described above, the mode is set to the
next lowest priority mode (where the Average mode has the highest priority and Transmitter B
mode has the lowest priority) until a mode is selected that is not inhibited or blocked. If both
transmitters are in Quality Alarm, the output of the algorithm latches onto the last good value and
the mode is set to the Transmitter A mode.
If the Tracking Mode Request digital input (TMOD) is initialized, the mode is set according to the
rounded value of the tracking input and the above table when the Tracking Mode Request signal
is TRUE and there are no Quality Alarms. The mode remains unchanged if the rounded value of
the tracking input is not 1 through 5 when the Tracking Mode Request signal is TRUE.
You may select a different mode by using the function keys on the Operator’s Keyboard when the
Tracking Mode Request signal is FALSE. The value of the analog output (OUT) is according to
the mode of the algorithm:
Mode
MOD E O U TP U T V AL U E
Average Average value of the two transmitter input values.
Lower Lower value of the two transmitter input values.

Higher Higher value of the two transmitter input values.
Transmitter A Value of Transmitter A.
Transmitter B Value of Transmitter B.
The Transmitter Deviation Alarm digital output (XDEV) is set TRUE when the deviation between
the two transmitter values is greater than the Alarm Deviation Deadband tuning constant (ALDB),
or when one or both transmitters contain invalid real numbers.
The Transmitter A Quality Alarm digital output (XABQ) is set TRUE when the quality of the
Transmitter A analog input goes BAD or NOT GOOD, depending on the Quality Alarm Type flag.
The Transmitter B Quality Alarm digital output (XBBQ) is set TRUE when the quality of the
Transmitter B analog input point goes BAD or NOT GOOD, depending on the Quality Alarm Type
flag.
600 OW351_R1100
5.139 2XSELECT
The Transmitter Malfunction Alarm digital output (XALM) is set TRUE when there is a Quality
Alarm on either of the two signals, when one or both input points contain invalid values, or when
the deviation between the two transmitter values is greater than the Control Deviation Deadband
tuning constant (CNDB).
The Manual Reject digital output (MRE) is set TRUE when both transmitters are in Quality Alarm,
or when the deviation between the two transmitter values is greater than the Control Deviation
Deadband tuning constant (CNDB). The P3 function key on the Operator’s Keyboard toggles the
inhibiting of the deviation check. For example, by pressing the P3 function key on the Operator’s
Keyboard, the Manual Reject output is only set TRUE when both transmitters are in Quality
Alarm. Then, by pressing the P3 function key again, the Manual Reject output is set TRUE when
both transmitters are in Quality Alarm or when the deviation is too large.
The packed digital output signal (PBPT) contains the Quality Alarms for both transmitt ers, the
Manual Reject output, the Transmitter Malfunction Alarm, the Tracking Request signal, the mode
of the algorithm, and the state of the Inhibit Control Deviation Alarm Check for the MRE digital
output feature.
The HOLD parameter holds the output value and quality for a desired number of loops when a
manual reject occurs.
Note: The information in the pack ed digital output signal is also stored in the B7 field of the
algorithm record.
When using the RATE or DBNB parameters, the following apply:
 2XSELECT ramps at the user-entered rate (specified in Units/Sec. via the RATE template
parameter) during mode changes. If no entry is made in the RATE parameter or a value of 0
is entered, 2XSELECT changes its output value to the new value during mode changes.
 2XSELECT returns from a deviation (XDEV) condition (that is, when the absolute difference
between the XA and XB inputs is greater than the ALDB parameter) only when absolute
difference between the XA and XB inputs return to a value which is less than or equal to
Alarm Limit Deadband (ALDB) minus DBND. If no entry is made in the DBND parameter or a
value of 0 is entered, 2XSELECT returns from an XDEV condition.
 2XSELECT returns from a CNDB condition (that is, when the absolute difference between the
XA and XB inputs is greater than the CNDB parameter) only when absolute difference
between the XA and XB inputs return to a value which is less than or equal to CNDB minus
DBND. If no entry is made in the DBND parameter or a value of 0 is entered, 2XSELECT
returns from a CNDB condition.
The interface keys on the Operator’s Keyboard are:
Function keys
P1 Transmitter A mode request.
P2 Transmitter B mode request.

P3 Toggle the inhibiting of the Control Deviation Alarm check on the
manual reject (MRE) output.
OW351_R1100 601
5.139 2XSELECT
P4 Average mode request.
P5 Lower mode request.

P6 Higher mode request.
The transmitter input values to the algorithm are checked for invalid real numbers. If a transmitter
contains an invalid value, its Quality Alarm digital output is set TRUE.
If both transmitters are in Quality Alarm, or contain invalid values, the value of the algorithm
output (OUT) quality is set to BAD.
If the algorithm calculates an invalid real number for the output, the quality of the output is set to
BAD and the output value is invalid.
INSEL parameter
The INSEL parameter determines which inputs of the 2XSELECT algorithm are being used to
calculate the output. The Signal Diagram application displays green circles around the active pins.
If none of the pins are selected, then nothing will display. You can also view this information via
the Process Diagram System graphics as well. Refer to Ovation Operator Station User Guide for
more information on the Signal Diagrams application and the Proc ess Diagram System graphics.
The 2XSELECT algorithm activates individual bits in the Y0 field depending on the conditions in
the description field. If a signal is active, that signal is being used in the output calculation.
602 OW351_R1100
5.139 2XSELECT
FI E L D RE C .
DIAG LU-Integer Tuning Required 99 Tuning diagram —

Constant number.
MODE — Selectable Optional — Input (analog); LA

tracks the algorithm
to a mode on first
pass and when
TMOD is TRUE.
This point must be
initialized if the
TMOD point is
initialized.
TMOD — Variable Optional — Input (digital); LD, LP
request to track the
mode to the value of
MODE. If this point
is initialized, the
MODE point must
also be initialized.
CNTL G0-Integer Data Init. Optional 0 Control Indicator —
Word (bit and
description):
0 - Average
Selection
(0 = Not allowed
1 = Allowed)
1 - Lower Selection
(0 = Not allowed
1 = Allowed)
2 - Higher Selection
(0 = Not allowed
1 = Allowed)
3 - Quality Alarm
Type
(0 = BAD Quality
Alarm
1 = NOT GOOD
Quality Alarm)
ALDB R1-Real Tuning Required 0.0 Alarm Deviation —
Constant Deadband.
CNDB R2-Real Tuning Required 0.0 Control Deviation —

Constant Deadband.
RATE R3-Real Tuning Optional 0.0 Ramping rate —
Constant parameter.
OW351_R1100 603
5.139 2XSELECT
FI E L D RE C .
DBND R4-Real Tuning Optional 0.0 Deadband delta —

Constant parameter.
HOLD X7-Byte Data Init Required 0 Hold output during —
manual reject.
XA — Variable Required — Input (analog); LA
Transmitter A.
XB — Variable Required — Input (analog); LA
Transmitter B.
XDEV — Variable Optional — Output (digital); LD, LP
Transmitter Alarm
Deviation signal.
XABQ — Variable Optional — Output (digital); LD, LP
Quality Alarm for
Transmitter A.
XBBQ — Variable Optional — Output (digital); LD, LP
Quality Alarm for
Transmitter B.
XALM — Variable Optional — Output (digital); LD, LP
Transmitter
Malfunction Alarm.
MRE — Variable Optional — Output (digital); LD, LP
Manual Reject
signal.
OUT — Variable Required — Output (analog). LA
604 OW351_R1100
5.139 2XSELECT
FI E L D RE C .
PBPT — Variable Optional — Output (packed LP

digital) (bit and
description):
0 - Manual Reject
Output signal.
1 - Transmitter
Malfunction Alarm.
2 - Inhibit Control
Deviation Check for
MRE output.
3 - Quality Alarm for
Transmitter A.
4 - Quality Alarm for
Transmitter B.
5 - Mode selection
being made by
TMOD.
6 - Transmitter
Alarm
Deviation signal.
7 - Average mode.
8 - Lower mode.
9 - Higher mode.
10 - Transmitter A
mode.
11 - Transmitter B
mode.
INSEL* Y0 Alg. Init. Required 0 Input Selected: --
Bit 1 - Signal A
 0 = Not Active
 1 = Active
Bit 2 - Signal B
 0 = Not Active
 1 = Active
* If no inputs are selected, it indicates one of the following:
 the inputs are all BAD quality.
 the output is scan removed.
 Manual Reject is activated with HOLD.
 the calculated output is invalid.
OW351_R1100 605
SECTION 6
6 Q-Line algorithms
IN THIS SECTION
What are Q-Line algorithms ? ................................................................................... 608

PVSPSLI................................................................................................................ 609
PWDIN................................................................................................................... 612
QLIPASS ............................................................................................................... 614
QPACMD ............................................................................................................... 619
QPACMPAR........................................................................................................... 625
QPASTAT .............................................................................................................. 626
QSDDE MAND ........................................................................................................ 627
QSDMODE ............................................................................................................ 629
QSRMA ................................................................................................................. 630
QVP....................................................................................................................... 636
XFLOW .................................................................................................................. 639
XMA2..................................................................................................................... 645
XML2 ..................................................................................................................... 656
XPIDSLI ................................................................................................................. 661
OW351_R1100 607
6.1 What are Q-Line algorithms?
6.1 What are Q-Line algorithms?
Q-Line algorithms are algorithms that are used specifically with Q-Line I/O hardware in an Ovation
system. These algorithms are the only Q-Line algorithms supported in Ovation. They can be
added to an Ovation control sheet by the Ovation Control Builder and then used in your Ovation
control scheme.
The Q-Line algorithms are listed below, The reference pages for Q-Line algorithms use the same
format as the standard Ovation algorithm reference pages (see page 46).
 PVSPSLI (see page 609) - Writes the functional processor-defined process variable (PVAR)
and/or set point (STPT) values to the Q-Line Loop Interface (QLI) for display at the Loop
Interface Module (LIM).
 PWDIN (see page 612) - Converts a digital pulse to an analog value proportional to the width
of the pulse.
 QLIPASS (see page 614) - Changes the default station (or loop) number and password
number for up to 12 QLI cards
 QSDDEMAND (see page 627) - Writes demand and mode to a QSD card.
 QSDMODE (see page 629) - Indicates QSD mode.
 QVP (see page 636) - Interface to a QVP card.
 XFLOW (see page 639) - Calculates a pressure-and-temperature-compensated mass or
 XPIDSLI (see page 661) - PID controller with supervisory set point and QLI or QLJ card
interface.
608 OW351_R1100
6.2 PVSPSLI
6.2 PVSPSLI
Description
The PVSPSLI algorithm writes the functional processor-defined process variable (PVAR) and/or
set point (STPT) values to the Q-Line Loop Interface (QLI) for display at the Loop Interface
Module (LIM). These analog inputs must be of type AC or greater so that the top of bar, bottom of
bar, and engineering units fields may be used to initialize the c onfiguration data sections of the
QLI card for the process variable and set point values. The top of bar and bottom of bar fields
from each input are also used to scale the values to be written to the card.
Symbol
You specify which values are written to the QLI card by initializing the bits in the configuration
byte parameter (INIT). This information and the appropriate values are written to the QLI card. If
the algorithm is initialized to perform the special functional processor-defined process variable for
the QLI card, do not use an XFLOW algorithm configured to interface to the same QLI card, and
do not configure the QLI card as a massflow card-type. Also, if the algorithm is initialized to
perform the special functional processor-defined set point for the QLI card, do not use the
XPIDSLI algorithm to interface to the same QLI card.
If this algorithm is initialized to write the functional processor-defined set point to the QLI card,
then the QLI no longer raises or lowers the set point value in response to raise/lower requests
from the LIM. If you desire to have raise and lower set point requests from the LIM, and XML
algorithm, configured to interface to the same QLI card, must be used. Refer to t he description of
the XML2 algorithm (see page 656).
Bit 10 is set in the second status word of the digital output (STAT) for one loop whenever the
process variable (flow configuration) or the set point configuration data sections are reconfigured.
This does not affect the quality of the digital point (that is, the quality is not set BAD when the QLI
is reconfigured).
OW351_R1100 609
6.2 PVSPSLI
The digital output point is set TRUE and the quality of the digital output is BAD if invalid values or
any hardware errors are detected when either the process variable or the set point information is
written to the QLI card. The following hardware errors are reported in the second status word of
the digital output (STAT):
Bit description
0 Invalid hardware address. User-specified hardware address outside legal range of 0 to

3FCH.
1 Write verification error. The algorithm tried to reconfigure either the process variable or
set point section of the card, but was unable to do so.
2 Bad hardware status . The power and card OK bits on the QLI card were not set.
3 QLI configuration error. The algorithm tried to reconfigure the QLI card for two
consecutive loops. This could be caused by another algorithm having the same QLI
address, where both algorithms are trying to reconfigure the same section on the QLI
card.
4 Normalization error. Input point to be written to the QLI card contains an invalid real
number.
The process variable (PVAR) and set point (STPT) inputs are checked for invalid real numbers.
The QLI Card retains its last valid value if the point chosen to be written to the QLI card contains
an invalid value.
FI E L D RE C O R D
PVAR -- Variable Required -- Input (analog); LA

process variable
STPT -- Variable Required -- Input (analog); set LA
point
CARD X4 - Byte Data Init. Required 1 PCI card number --
(1, 2)
HWAD B2 - Integer Data Init. Required -- Hardware address --
of QLI card (in
decimal bytes)
610 OW351_R1100
6.2 PVSPSLI
FI E L D RE C O R D
INIT X1 - Byte Data Init. Required -- Configuration byte. --

Only bits 1 and 0
are used.
0 = No action
1 = Functional
processor-defined
process variable
2 = Functional
processor-defined
set point
3 = Functional
processor-defined
variable and set
point
PVTP R1 - Real Variable Required 100.0 Process variable --
top of scale
PVBT R2 - Real Variable Required 0.0 Process variable --
bottom of scale
PVEU1 AK - ASCII Variable Required PCT Process EU
PVEU G4 - Integer Variable Optional 0 Process variable - --

Holding register
STTP R3 - Real Variable Required 100.0 Setpoint top of --
scale
STBT R4 - Real Variable Required 0.0 Setpoint bottom of --
scale
STEU G5 - Integer Variable Optional 0 Setpoint - Holding --
register
STEU1 A5 - ASCII Variable Optional PCT Setpoint -- EU --
STAT -- Variable Required -- Output (digital); QLI LD, LP

card hardware
status
OW351_R1100 611
6.3 PWDIN
6.3 PWDIN
Description
The PWDIN algorithm converts a digital pulse to an analog value proportional to the width of the
pulse. A QSE Card is used to time tag a digital signal’s transition from FALSE to TRUE and then
from TRUE to FALSE. The time difference between these two events is the pulse width, which
may vary from a minimum of 5 msec to a maximum of 65 sec. The pulse width is then multiplied
by a scaling factor to obtain the output analog value. (The output analog value is always zero,
except in the loop where the TRUE to FALSE transition occurs. In this loop, the width is
calculated and its value is output.)
Note: The PWDIN algorithm must run in a 300 millisecond or faster task area.
Functional Symbol
The digital outputs of the algorithm are used to reflect the current state of their corresponding
digital signals on the QSE Card.
The second status word of each digital output indicates error conditions; Bit 0 is set when an
invalid QSE Card hardware address is used, while Bit 2 is set when the QSE Card is bad.
Bit 2 of the second status word of an analog output is set when an event is missed for that point.
Note: The use of PWDIN for a particular QSE card precludes the use of any of the points in this
card for SOE purposes. The remaining bit positions on this QSE Card may be used as regular,
digital inputs (DI records).
612 OW351_R1100
6.3 PWDIN
FI E L D RE C O R D
DIAG LU - Byte Data Init. Optional -- Tuning diagram --

number (default
value = 5)
PCI X4 - Byte Data Init. Required 1 PCI card number --
(1, 2)
HWAD B2 - Integer Data Init. Required -- Hardware address --
of the QSE card
NUM X1 - Byte Data Init. Required -- Number of QSE --
digitals to be
monitored
(maximum of four;
bit positions 0
through 3 of the
QSE card
CON1 R1 - Real Tuning Required -- Scaling factor for --
Constant OUT1. CON1 is
multiplied by the
pulse width in
seconds to
calculate the
output value.
multiplied by the
pulse width in
seconds to
calculate the
output value.
multiplied by the
pulse width in
seconds to
calculate the
output value.
OW351_R1100 613
6.3 PWDIN
FI E L D RE C O R D

multiplied by the
pulse width in
seconds to
calculate the
output value.
OUT1 -- Variable Required -- Output (analog) LA
DIG1 -- Variable Required -- Output (digital) LD
DIG2 -- Variable Required -- Output (digital) L D
614 OW351_R1100
6.4 QLIPASS
6.4 QLIPASS
Description
The QLIPASS algorithm changes the default station (or loop) number and password number for
up to 12 QLI cards. It is used under two conditions:
 If there is more than one Q-Line Loop Interface (QLI) card per Loop Interface Module (LIM),
this algorithm is needed to assign a particular station (or loop) number to a QLI card. This
station (or loop) number is selected at the LIM to display values from the specified QLI c ard.
 If tuning of the PID gain, reset time, derivative gain and rate parameters from the LIM is
desired, a password must be set up. The valid range for passwords is 0 through OFFFFH, or
0 through 65,535 (although LIM tuning will be locked out for passwords exceeding 9999
decimal).
Functional Symbol
CNT = B0= C0= D4= E8=

B1= C1= D5= E9=
B2= C6= D6= F0=
B3= C7= D7= F1=
B4= C8= E2= F2=
B5= C9= E3= F3=
B6= D0= E4=
B7= D1= E5=
B8= D2= E6=
B9= D3= E7=
The value of the STAT output variable is TRUE if an invalid hardware address, a write verification
error, or a QLI configuration error is detected for any QLI specified. If no errors are detected in
any QLI’s, the value of STAT is FALSE.
The second status word of the STAT output variable contains the group status of up to 12 QLI
cards. Up to four bits can be set by any of 12 QLI cards as follows:
Bit description
0 Invalid hardware address; specified address is out of range (2<= QLI address <= 3F0H)
1 Write verification error that can be caused by:
 No power in QLI
 No QLI card at specified address
 An unsuccessful QLI configuration attempt
OW351_R1100 615
6.4 QLIPASS
3 QLI configuration error caused by two consecutive configuration updates. This cou ld be
caused by another algorithm having the same QLI address, where both algorithms are
trying to reconfigure the same section on the QLI card.
10 Configuration update this loop.
The first 12 bits of the PNTS packed group, output record represent the s tatus of the 12 possible
QLI cards. For a bit not scan-removed, that bit will be set for any of the following conditions:
 Bad hardware address

 Configuration data update
 QLI configured on two consecutive loops
 Write verification error
Rules
1. When assigning station numbers, the final (maximum) station number should be specified as
a negative number. For example, if there are nine stations assigned to one LIM, the ninth
station should be added to the template as - 9. This will signal the LIM to loop from Station 1
through Station 9, and back to Station 1.
2. When adding an additional QLI loop to a LIM (thereby, increasing the last station number
used), it is necessary to recycle power on the LIM and select the new final loop at the LIM.
This enables the LIM to sequence from Station 1 through the new station number, and back to
Station 1.
FI E L D RE C O R D
CNT X1 - Byte Data Init. Required -- Number of QLI --

cards to be
initialized
CARD X4 - Byte Data Init. Required 1 PCI card number --
(1, 2)
AD01 B0 - Integer Tuning Required` -- Hardware address --
Constant for QLI No. 1
ST01 C6 - Integer Tuning Required -- Station number for --
Constant QLI No. 1
PS01 E2 - Integer Tuning Required -- Password for QLI --
Constant No. 1
AD02 B1 - Integer Tuning Optional -- Hardware address --
ST02 C7 - Integer Tuning Optional -- Station number for --
Constant QLI No. 2
616 OW351_R1100
6.4 QLIPASS
FI E L D RE C O R D
PS02 E3 - Integer Tuning Optional -- Password for QLI --

Constant No. 2
ST03 C8 - Integer Tuning Optional -- Station number for --
Constant QLI No. 3
Constant No. 3
AD04 YU - Integer Tuning Optional -- Hardware address --
ST04 YT - Integer Tuning Optional -- Station number for --
Constant QLI No. 4
PS04 YC - Integer Tuning Optional -- Password for QLI --
Constant No. 4
ST05 D0 - Integer Tuning Optional -- Station number for --
Constant QLI No. 5
PS05 Y9 - Integer Tuning Optional -- Password for QLI --
Constant No. 5
ST06 YQ - Integer Tuning Optional -- Station number for --
Constant QLI No. 6
Constant No. 6
Constant QLI No. 7
Constant No. 7
ST08 YP - Integer Tuning Optional -- Station number for --
Constant QLI No. 8
Constant No. 8
Constant QLI No. 9
Constant No. 9
OW351_R1100 617
6.4 QLIPASS
FI E L D RE C O R D

Constant QLI No. 10
Constant No. 10
AD11 C0 - Integer Tuning Optional -- Hardware address --
Constant QLI No. 11
PS11 XY - Integer Tuning Optional -- Password for QLI --
Constant No. 11
AD12 C1 - Integer Tuning Optional -- Hardware address --
ST12 YN - Integer Tuning Optional -- Station number for --
Constant QLI No. 12
PS12 XY - Integer Tuning Optional -- Password for QLI --
Constant No. 12
STAT -- Variable Required -- Output (digital) LD, LP
PNTS -- Variable Required -- Output (packed LP
group)
618 OW351_R1100
6.5 QPACMD
6.5 QPACMD
Description
QPACMD writes a command byte to the QPA Card. The command byte may be written to a
particular QPA Card or to many cards through a group write address. The group write address
must be between 0x1F8 and 0x1FF. If the GADR parameter is initialized, the group write address
is used; otherwise, the hardware address from the IN1 record is used.
The bits in the command byte are set or reset according to the data initialization parameters
FRZ0, STR0, RST0, FRZ1, STR1, and RST1. If the command byte is to be written to a particular
card and a parameter is zero, the corresponding bit in the command byte remains unchanged
from its present value. When writing to the group write address, each bit must be set or reset and
both counters on all the cards with that group write address are affected. The digital input signal
(RUN) must be TRUE for the algorithm to execute.
Note: If QPASTAT is used in conjunction with QPACMD, mak e sure that QPASTAT runs before
QPACMD. Otherwise, the flag CMPF in QPASTAT clears prematurely.
Functional Symbol
N AME LC T YP E RE Q U I R E D / D E F AU L T DE S C R I P TI O N MI N .
AL G . O P TI O N AL V AL U E P T.
RE C . RE C .
FI E L D
GADR G0 - Data Init. Optional — Group Write Offset Write —

Integer
FRZ0 X1 - Data Init. Optional — Freeze/unfreeze selector for —

Byte Counter 0
CNTR CNTR GADR
Select. Address Address
0 No Action Unfreeze
1 Freeze Freeze
2 Unfreeze Unfreeze
OW351_R1100 619
6.5 QPACMD
N AME LC T YP E RE Q U I R E D / D E F AU L T DE S C R I P TI O N MI N .
AL G . O P TI O N AL V AL U E P T.
RE C . RE C .
FI E L D
STR0 X2 - Data Init. Optional — Start/Stop selector for —

Byte Counter 0
CNTR CNTR GADR
0 No Action Stop
1 Start Start
2 Stop Stop
RST0 X3 - Data Init. Optional — Reset selector for Counter 0 —
Byte
CNTR CNTR GADR
0 No Action No Action
1 Reset Reset
FRZ1 X4 - Data Init. Optional — Freeze/unfreeze selector for —
Byte Counter 1
CNTR CNTR GADR
0 No Action Unfreeze
1 Freeze Freeze
2 Unfreeze Unfreeze
RST1 X6 - Data Init. Optional — Reset selector for Counter 1 —
Byte
CNTR CNTR GADR
0 No Action No Action
1 Reset Reset
RUN — Variable Required — Input (digital) LD
620 OW351_R1100
6.5 QPACMD
Application Example
Three algorithms can access the QPA card: QPACMD, QPASTAT, and QPACMPAR. This is one
example of how to use the QPACMD command (see QPACMPAR (see page 625) for another
example).
In this example, a QPA card is used to count a pulsed input. The input is a count of contact
closures from a megawatt meter. The number of megawatts per pulse is accounted for in the
coefficients that are calculated as part of the point record.
Be careful when selecting hardware addresses for QPA cards. They require four consecutive
addresses each, even though there are only two inputs for each card. The extra two addresses
are used for control and status word transfer. In this example, the QPA card is located in the first
slot of Q-crate 1 in a Controller (where: half-shell = A1 and card hardware address = 0x80).
In this example, the input for Counter 1 (IN1) is assigned analog point EW1. This is the second
card input. Counter 0 uses the first card input.
IN1 must be initialized as an analog input point in the Controller. The following is an example of
such a point (EW1).
Field value
FI E L D V AL U E
RT LA
EU ‘MWH’
ED ‘MWH To PHOSIE- ACBNO1’
CV 1
IV 0.6
2V 0.0
Other points needed by algorithms used in this example are added to the database.
Point
P O I N T NAME T YP E FR E Q U E N C Y
HOUR LD 1.0
PMIN LD 1.0
SECND LD 1.0
EW1R LA 1.0
EW1TOT LA 1.0
DX1PASS LD 1.0
OW351_R1100 621
6.5 QPACMD
EW1 may have non-zero values for parameters such as TOPBAR, BOTBAR, and LIMITS, as
desired, just as any other analog input point.
In this example, if one pulse from a megawatt meter equals 10 kilowatt hours, in order to make
EW1 equivalent to megawatt hours, a conversion coefficient must be used on the point.
This means that if there were three pulses per minute in an one hour period, the coefficient would
calculate a value as follows:
PULSES KWH MWH MIN MWH

3 * 10 * * 60 = 1.8
MIN PULSE 1000 KWH HR HR
Alternate Example
An alternate method of converting pulse counts into megawatts per hour is to leave the CI and CV
record fields blank so that the value of EW1 represents the actual pulse count from the QPA card.
A gain could be used in the RESETSUM algorithm to calculate megawatts per hour.
The following application is used to control the QPA card in this example.
Example
A L G O R I TH M AL G O R I TH M P AR AM E TE R S P O I N T /V AL U E S
TIMECHANGE (110) HCHG HOUR
SCHG SECND
MCHG PMIN
QPACMD (111) IN1 EW1
FRZ0 0
RST0 0
STR0 0
FRZ1 0
RST1 0
STR1 1
RUN DX1PASS
FRZ0 0
RST0 0
STR0 0
FRZ1 2
RST1 0
STR1 0
RUN PMIN
622 OW351_R1100
6.5 QPACMD
A L G O R I TH M AL G O R I TH M P AR AM E TE R S P O I N T /V AL U E S
FRZ0 0
RST0 0
STR0 0
FRZ1 1
RST1 1
STR1 0
RUN PMIN
RESETSUM (115) IN1 EW1
FFLG HOUR
RSET HOUR
RUN PMIN
RCNT 0.0
GAIN 1.0
OUT EW1R
FOUT EW1T0T
The execution of the example application is as follows:
1. Algorithm 110 (TIMECHANGE) generates PMIN and HOUR, which are flags denoting a
change in minutes and hours, respectively. These flags are used by the QPACMD and
RESETSUM algorithms. HOUR, PMIN, and SECND must be initialized as digital points.
2. Algorithm 111 (QPACMD) sends the control command START to Counter 1 (STR1 = 1) of the
QPA card when the digital input DX1PASS point is set. DX1PASS is a point from some
control scheme, which is set to 1 only during the first pass through t he application. Therefore,
the QPA starts collecting pulse counts upon start-up, after a hardware reset, or Controller
failover.
3. The algorithm pair of 112 and 113 reads the data from QPA Counter 1 (IN1 = EW1). There
are two counters working within the QPA card. One is an actual counter linked directly with
the pulse input, which is always accumulating data unless reset. The other counter is Counter
1, which reads data from the actual counter upon command.
4. Algorithm 112 unfreezes (FRZ = 2) Counter 1 so that the values in Counter 1 reflect the data
in the actual counter. Algorithm 113 then freezes (FRZ = 1) the value stored in Counter 1 and
resets the actual counter to zero before accumulating more pulse data. Only the reset
operation (RST1 = 1) affects the actual QPA count. The freeze/unfreeze operation only
causes the current value to be placed on the DIOB or removed from the DIOB.
OW351_R1100 623
6.5 QPACMD
These four algorithms (110, 111, 112, and 113) only run when the digital flag PMIN is true. PMIN
may be generated any number of ways, but in this application, PMIN is set as an output flag from
the TIMECHANGE algorithm every minute. By holding the QPA Counter 1 value frozen for one
minute, a valid QPA reading is present on the DIOB during the entire one-minute period, allowing
other algorithms to access the data.
RESETSUM (115) totals the values read from the QPA over a period of time. The values are
summed, based on the state of the flags PMIN and HOUR. In this example, EW1R contains the
number of megawatts accumulated every minute for an hour. Output EW1TOT is an hourly total
of megawatts generated and is triggered by HOUR. The value of EW1R is stored into EW1TOT
on the hour and EW1R is reset to zero, ready to accumulate the next hour’s information.
The commands START, STOP, FREEZE, and UNFREEZE may be hard-wired in the field if the
availability of the QPA count is to be controlled by hardware rather than software.
624 OW351_R1100
6.6 QPACMPAR
6.6 QPACMPAR
Description
QPACMPAR writes a comparator value (VALU) to a comparator register on a QPA Card at the
hardware address found in the counter input (IN1). If IN1 has a linear conversion (to normalize its
current value), the input VALUE is denormalized before it is written to the QPA Card as the
comparator value. If the conversion on IN1 is not linear, the value of VALU is assumed to have
been already denormalized. The denormalized value of VALU is high and low limited between
zero and 32767 so that it can be properly written to the QPA Card. The digital input signal (RUN)
must be TRUE for the algorithm to execute.
The new value (VALU) to be written to the QPA card is checked for invalid real numbers. If the
new value is invalid, it is not written to the QPA card, and a “Hardware Error” is reported in the
second status work (2W record field) of the analog input CNTR.
Functional Symbol
FI E L D RE C O R D
VALU — Variable Required — Input (analog) LA

RUN — Variable Required — Input (digital) LD
Application Example
This example describes one method of using the QPACMPAR, QPASTAT, and QPACMD
algorithms together to access the data stored on the QPA card.
1. Use QPACMPAR to write a comparator value to the QPA card. This value is stored in a QPA
hardware register (VALU). When the value stored in IN1 equals the value stored in VALU, the
QPA card automatically sets the CMPF flag (a bit in the status register).
2. Use QPASTAT to read the status flags: CMPF, RUNF, and FRZ1. If CMPF is set, use
QPACMD to reset the QPA CNTR.
CAUTION! If both counters on the QPA card are being used, reading the status of one
Counter with QPASTAT clears the other Counter’s CMPF flag if that flag was set.
OW351_R1100 625
6.7 QPASTAT
6.7 QPASTAT
Description
QPASTAT reads the status byte from a QPA card at the hardware address found in the counter
input (IN1). The hardware address is checked to determine which counter on the card is used.
The corresponding status flags are checked and output as digital records.
Functional Symbol
FI E L D RE C O R D
CMPF — Variable Optional — Output (digital); LD

Comparator flag
RUNF — Variable Optional — Output (digital); LD

Running flag
FRZF — Variable Optional — Output (digital); LP
Frozen flag
626 OW351_R1100
6.8 QSDDEMAND
6.8 QSDDEMAND
Description
The QSDDEMAND algorithm controls the servo driver card (QSD) demand signal and controls
the operation mode (Auto, Manual) of the QSD card. It also services the watchdog timer by
setting the keep alive bit upon each call.
The algorithm places the QSD in automatic if the auto request input (AREQ) is TRUE, the ready
bit read from the QSD card has been TRUE for the specified amount of time (RDY), and the card
in place bit read from the QSD is TRUE.
The algorithm rejects the QSD to local manual if the local manual request input (LREQ) is TRUE,
if the card in place bit from the QSD is FALSE, or if the demand output to the QSD does not equal
the value read back.
The algorithm sets the sensor alarm bits if either the card in place bit is not set or the demand
read back from the QSD card does not equal the demand written to the card.
Note: The OUT point must contain the hardware address for the QSD card.
Functional Symbol
OW351_R1100 627
6.8 QSDDEMAND
FI E L D RE C O R D
DIAG LU-Integer Data Init. Required 28 Tuning Diagram —

Number
RDY R1-Real Tuning Required 2 Ready Time —
Constant
IN1 — Variable Required — Analog Calculate LA

Demand Input
LREQ — Variable Required — Digital Local Request LD
Input
AREQ — Variable Required — Digital Auto Request LD
Input
variable
ERRB — Variable Optional — Digital Output LD
628 OW351_R1100
6.9 QSDMODE
6.9 QSDMODE
Description
The QSDMODE algorithm reads the mode in which the QSD card is operating. The output is
TRUE if the QSD card is in Auto Mode. The algorithm also checks the card in place bit and if it is
not set, the sensor alarm bit is set.
Note: The IN1 point must contain the hardware address for the QSD card.
Functional Symbol
FI E L D RE C O R D
IN1 — Variable Required — Demand Output LA

(analog)
MODE — Variable Required — Digital output LD
variable (digital);
QSD mode
OW351_R1100 629
6.10 QSRMA
6.10 QSRMA
Description
The QSRMA algorithm interfaces the manual/auto station to a QSR card. The QSRMA algorithm
writes a demand and shutdown option to one channel on the QSR card. The algorithm also
outputs status information for the channel such as the card is okay or shutdown is active.
Functional Symbol
Auto Mode
The output equals the gained and biased input plus the bias bar value (OUT = (IN1 x IN1G) +
IN1B + BIAS) except:
the input.
Increase/Decrease set point keys on the Control Panel or Operator’s Keyboard. This value is only
added to the output value in Auto mode; it has no effect on the output (but still may be raised or
lowered) in Manual or Local mode.
The output value is written to the demand register to a channel on the QSR card.
The Increase/Decrease Output keys on the Operator’s Keyboard have no effect in this mode.
Manual Mode
The output is raised or lowered by using the Increase/Decrease Output requests. The raise inhibit
and lower inhibit signals override the Operator’s Keyboard Increase/Decrease Output requests.
The tracking signal causes the output to equal the track input, regardless of the raise/lower inhibit
The output value is written to the demand register to a channel on the QSR card.
630 OW351_R1100
6.10 QSRMA
Local Mode
If the QSR card has any hardware error, then the algorithm stays in Local Mode.
Mode Transfers
 The digital reject signal rejects the algorithm from Auto to Manual mode or from Auto to Local
mode (when the Manual Inhibit feature is ON).
on the Control Panel or Operator’s Keyboard switches the algorithm to the desired mode if it
is not in Local mode.
 If the QSR has hardware errors, the algorithm rejects to Local mode.
input when in Auto mode. If the algorithm is in Auto mode and the quality of the input goes
BAD or not GOOD depending on the Quality Reject flag, then the algorithm rejects to Manual
mode as long as the Manual inhibit feature is OFF. If the Manual inhibit feature is on, the
algorithm rejects to Local mode.
 Regardless of the REJQ parameter, the input value is checked for an invalid value when the
algorithm is in Auto mode. If the algorithm is in Auto mode and the value of the input becomes
invalid, the algorithm rejects to Manual mode, providing the Manual Inhibit feature is OFF. If
the Manual Inhibit feature is ON, the algorithm rejects to Local mode if the QSR is selected. If
the algorithm is not in Auto mode and the operator tries to select Auto mode when the input
value is invalid, the algorithm remains in the same mode and does not reject to Manual mode.
 The track input value is also checked for invalid real numbers when the algorithm is being told
to track. While in Auto mode, if the algorithm is told to track and the track input value is
invalid, the algorithm rejects to Manual mode, providing the Manual Inhibit feature is OFF. In
all modes, the track request is ignored when the track input value is invalid.
 On reset/power-up, the algorithm is in Local mode if a QSR interface is, then the algorithm
goes to the mode initialized by the Firstpass mode (FP) parameter unless that mode is
blocked by the Manual Inhibit feature.
Note: The Manual Inhibit feature prevents the algorithm from entering Manual mode when it is
on.
The interface keys of the Control Panel and Operator’s Keyboard are:
Key usage
KE Y US E
MANUAL Function Key Manual mode request

OW351_R1100 631
6.10 QSRMA
Tracking Signals
of the analog point. This algorithm takes the action shown in the following table in response to the
information found in the analog input signal TRIN:
Bit description
16 Track Implemented Passed through, set TRUE on first pass to

read the hardware, or set TRUE when not in
Auto mode.
20 Raise inhibit Implemented* Passed through*
The high and low limit flags, the mode and the tracking signals from the algorithm are output to
algorithm must be specified by the user for correct implementation of the tracking features. The
following hardware related errors are set in the second status word of the analog output record
and cause the analog output to have BAD quality:
Bit description
2 BAD hardware status. The Data Valid and Card OK bits on the QSR card.
If an invalid hardware address or BAD hardware status error caused the algorithm to reject to
Local, the quality remains BAD on the output and the algorithm remains in Local mode until the
error is cleared.
632 OW351_R1100
6.10 QSRMA
of the input when in Auto mode.
is set to BAD, the OUT value is invalid, and the drop is placed into alarm.
FI E L D RE C O R D

number
IN1G R5-Real Tuning Required 1.0 Gain on input. The —
Constant gain should never
be initialized to
zero; if it is, the
drop is placed into
alarm.
IN1B R6-Real Tuning Required 0.0 Bias on input —
Constant
* TPSC R7-Real Selectable Required 100.0 Maximum value of LA

the output point
* BTSC R8-Real Selectable Required 0.0 Minimum value of LA
the output point
TPBS R2-Real Tuning Required 0.0 Maximum value of —
BTBS R3-Real Tuning Required 0.0 Minimum value of —
PCNT X1-Byte Tuning Required 4 Percent change in —
TIME X2-Byte Tuning Required 25 Number of seconds —
to full scale
FP G0-Integer Data Init. Required MANUAL First pass mode. —

Bit 8 Algorithm goes to
this mode on
reset/power-up:
MANUAL: Manual
mode
AUTO: Auto mode
OW351_R1100 633
6.10 QSRMA
FI E L D RE C O R D
HWAD B2-Integer Data Init. Required 0 Card address for —

any hardware
interface (see page
3).
PCI X5-Byte Data Init. Required 1 PCI Card Number —
(1,2)
CHNL X6-Byte Data Init. Required 0 QSR Channel —
PRAR S1-Real Tuning Required 2.5 Priority Raise Rate —
Constant
PRAT S2-Real Tuning Required 100.0 Priority Raise —
Constant Target
PLWR S3-Real Tuning Required 2.5 Priority Lower Rate —
Constant
PLWT S4-Real Tuning Required 0.0 Priority Lower —
Constant Target
REJQ G0-Integer Data Init. Required BAD Quality reject type —
Bits 6 and 7 (only has meaning
if Manual Inhibit is
OFF):
BAD - Algorithm
rejects to Manual
mode when the
quality of the IN1
input goes BAD
and the algorithm is
in Auto mode.
NOTGOOD -
Manual mode when
the quality of the
IN1 input is NOT
GOOD and the
algorithm is in Auto
mode.
OFF - The quality
of the input is not
checked or used to
reject the algorithm
to Manual mode
when the algorithm
is in Auto mode.
Constant
IN1 — Variable Required — Input variable LA

analog input
634 OW351_R1100
6.10 QSRMA
FI E L D RE C O R D
TOUT — Variable Optional — Track output value LA

mode and Status
digital output
signals for Input
variable
MODE — Variable Optional — Input Mode Point LP
SHUT — Variable Optional — Shutdown signal to LD, LP

Card
variable
TRIN — Variable Optional — Tracking and LA
Limiting signals
and tracking value;
analog input
variable
BIAS — Variable Optional — Analog bias bar LA
variable output
VALI — Variable Optional — Data Valid: LD, LP

1 = Valid
0 = Invalid)
SMOD — Variable Optional — Shutdown Mode: LD, LP
1 = Open
0 = Closed
SACT — Variable Optional — Shutdown Active LD, LP
CARD – Variable Optional — Card Okay: LD, LP

1 = Okay
0 = Not Okay
* When a parameter type is defined as "Selectable" and marked as "Require d," the Control Builder may
OW351_R1100 635
6.11 QVP
6.11 QVP
Description
The QVP algorithm provides an interface to the Controller for communicating to the QVP card.
The algorithm provides set point position information as well as providing a calibration interface to
the QVP card. (See QVP Servo Controller User Guide.)
Normal Mode
The QVP algorithm provides an interface between the Ovation system and a QVP card. It allows
you to input two digital command words to the QVP and receive two digital status words in return.
Also, you may input and output analog utility points (one in, one out) for use in conjunction with
the command/status words. Optionally, you may output the internal working set point of the QVP.
Primarily, the algorithm’s function is to provide communication between a QVP card and the
Ovation system. However, it also stores certain card information and may be called upon to
configure a card as detailed below.
When you initiate a request to change some of the QVP working values (gain, reset, and so forth),
this algorithm intercepts the value and wait for the QVP’s response to the user. If the operation
was successful, the algorithm stores that information in the algorithm record. At next QVP startup,
if you have set a QVP jumper (JS6) for “configure from controller,” the algorithm sends all
configuration information currently stored.
At the end of a QVP calibration sequence, if the card was calibrated properly, the card sets a bit
in the second status word indicating that the calibration is done. If the algorithm sees this bit set, it
queries the card for all calibration data and store this information in the algorithm record. Again, at
card startup, the algorithm attempts to send this information to the QVP if the jumper has been set
to warrant this operation.
The algorithm also signals an error if it or the user has attempted to send a command to the card
and no response has been given.
Special Test Mode
The special test mode has the system set point input from the SPIN analog point and the valve
position output to the VPOT analog point. This way, all functions may be tested without the need
for adding any other algorithms. In order to execute the special test mode, valid point names must
be entered for the optional SPIN and VPOT entry fields in the algorithm template, the algorithm
must be made tunable, and the U1 tuning constant must be set to 356.0 through a tuning
diagram.
636 OW351_R1100
6.11 QVP
Registers
Each QVP card uses eight registers and each QVP algorithm interfaces to one QVP card. With
each scan of the Controller, the algorithm writes the appropriate value to a register and waits for a
response. If there is no response, it sets an error bit in the status word for that card. The QVP
responds by putting a response value into the same register, which is read and processed by the
algorithm. QVP registers are defined below:
Registers
R E G I S TE R W R I TTE N TO QVP R E TU R N E D F R OM QVP
QVP Hardware Address Set Point in (real, 1st word) Position out (real, 1st word)
QVP Hardware Address + 1 Set Point in (real, 2nd word) Position out (real, 2nd word)
QVP Hardware Address + 2 Dummy input word 1 Digital status word 1
QVP Hardware Address + 3 Dummy input word 2 Digital status word 2
QVP Hardware Address + 4 Digital input word 1 Set point out (real, 1st word)
QVP Hardware Address + 5 Digital input word 2 Set point out (real, 2nd word)
QVP Hardware Address + 6 Analog utility input point (real, Analog utility output point
1st word) (real, 1st word)
QVP Hardware Address + 7 Analog utility input point (real, Analog utility output point
2nd word) (real, 2nd word)
Functional Symbol
OW351_R1100 637
6.11 QVP
FI E L D RE C O R D
DIAG LU-Integer Data Init Required 114 Tuning Diagram —

Number
PCI X5-Byte Data Init Required 1 PCI Card Number —
(1,2)
HWAD B2-Integer Data Init Required 0 Card Hardware —
address (see page
3)
DIN1 — Variable Required — Digital Input 1 LP

ANIN — Variable Required — Analog Input Value LA
SPNT — Variable Optional — Analog demand to LA
QVP
DST1 — Variable Required — Digital Output 1 LP
DST2 — Variable Required — Digital Output 2 LP
AOUT — Variable Required — Analog Output LA
SPIN — Variable Required — Analog Output LA
VPOT — Variable Required — Analog Output LA
638 OW351_R1100
6.12 XFLOW
6.12 XFLOW
Description
The XFLOW algorithm calculates a pressure-and-temperature-compens ated mass or volumetric

flow for ideal gases.
The mass flow is calculated as shown below:
The volumetric flow is calculated as shown below:
where:
P1 = PACT + ABSPRES
P2 = PREF + ABSPRES
T1 = TACT + ABSTEMP
T2 = TREF + ABSTEMP
The algorithm can be operated with or without a Q-Line Loop Interface (QLI) card. If interfacing to
a QLI card, the inputs should be read from the QLI card by using the AIN algorithm and specifying
a QLI card type.
When operating with a QLI interface, the QLI card should be configured for mass flow operation.
This is specified through the card-type jumpers on the QLI card. A QLI hardware address of zero
indicates no QLI card interface.
No pressure compensation or temperature compensation is available. For no pressure

compensation, the user must specify a negative pressure reference (PRES REF) value. For no
temperature compensation, the user must specify a negative temperature reference (TEMP REF)
value.
The SCALE TOP and SCALE BOT parameters are used to limit the output value of the algorithm.
If the QLI hardware address is not zero, the QLI configuration data for the flow section is written
onto the QLI card. If the switch on the QLI card is not in Ignore EEPROM position, the
configuration data is saved in EEPROM on the QLI card. The top of bar, bottom of bar and the
first four characters of the engineering units parameters for the output are used for the
configuration data.
You must initialize these parameters to be displayed at the Loop Interface Module (LIM).
If the QLI hardware address is not zero, then Bit 10 is set in the second status word of the output
record for one loop whenever the QLI card is reconfigured. This does not affect the quality of the
output record (that is, the output quality is not set BAD when the QLI card is reconfigured).
OW351_R1100 639
6.12 XFLOW
Functional Symbol
Tracking Signals
Tracking and limiting are done through signals passed in the upper 16 bits of the third st atus word
found in the digital input signal TRIN:
Bit description
16 Track Ignored Not used

23 Deviation alarm No action Not used
24 Local manual mode No action Not used
27 Supervisory mode No action Not used
28 Cascade mode No action Not used
29 DDC mode No action Not used
640 OW351_R1100
6.12 XFLOW
The high and low limit flags are output TOUT to be used for display.
If the QLI hardware address is not zero, the following hardware related errors are set in the
second status word of the analog output record and cause the analog output to have BAD quality:
0 Invalid hardware address. The user specified a hardware address outside the legal range of
0 to 3FCH.
1 Write verification error. The algorithm tried to reconfigure the flow section of the QLI card,
was unable to do so.
3 QLI configuration error. The algorithm tried to reconfigure the QLI card for two consecutive
loops. This could be caused by another algorithm having the same QLI address, where both
algorithms are trying to reconfigure the same section on the QLI card.
The output will have bad quality if any QLI hardware-related errors are detected. If this is not the
case, the worst quality of the analog inputs specified is assigned to the quality of the output.
N AME LC AL G . T YP E DE F AU L T DE S C R I P TI O N MI N .
RE C O R D V AL U E POI N T
FI E L D RE C O R D
DIAG LU - Integer Data Init. 59 Tuning diagram number --
FLOW G3 - Integer Data Init. MASSFLOW Type of flow calculation --

Bit 5 performed:
MASSFLOW = mass flow
VOLFLOW = volume flow
GAIN R3 - Real Tuning 1.0 Calculated flow coefficient at --
Constant base operating conditions.
PRES R4 - Real Tuning 2400.0 Reference pressure; base --

Constant operating pressure used in the
calculation of the flow
coefficient, GAIN
TEMP R5 - Real Tuning 1000.0 Reference temperature; base --
Constant operating temperature used in
the calculation of the flow
coefficient, GAIN.
PABS G3 - Integer Data Init. YES Convert pressure values to --
Bit 2 absolute press option.
YES = input and reference
pressure values are converted
to absolute pressure.
NO = input and reference
pressure values are not
converted to absolute
pressure.
OW351_R1100 641
6.12 XFLOW
FI E L D RE C O R D
PUNT G3 - Integer Data Init. PSI Pressure conversion type. See --

Bits 0 below for Type and Absolute
and 1 Pressure Conversion Value:
PSI -- 14.696
INH20 -- 406.800
KGCM2 -- 1.033
KPA -- 101.325
TABS G3 - Integer Data Init. YES Convert temperature values to --
Bit 4 absolute temperature option.
YES = input and reference
temperature values are
converted to absolute
temperature.
TUNT G3 - Integer Data Init. FAHRA Temperature conversion type. --
Bit 3 See below for Type and
Absolute Temperature
Conversion Value:
FAHR -- 459.67
CENT -- 273.15
TPSC R1 - Real Tuning 100.0 Maximum value of the output --
Constant
BTSC R2 - Real Tuning 0.0 Maximum value of the output --
Constant
HWAD B2 - Integer Data Init. 0 Hardware address of QLI card. --
PCI X4 - Byte Data Init. 1 PCI card number --
PNES G3 - Integer Data Init. NOCHECK Check for use of negative --
Bit 6 pressure and temperature
reference values.
NOCHECK = No check is
performed to see if the
PACT(C) and TACT(C) inputs
were specified. A negative
PRES REF or TEMP REF
value causes the associated
term to be omitted from the
equation.
CHECK = Check whether the
PACT(C) and TACT(C) inputs
were specified. If an input is
not specified, the associated
term is omitted from the
equation. When the inputs are
specified, the PRES REF and
TEMP REF value are used
regardless of their sign.
IN1 -- Variable -- Differential pressure analog LA
input
642 OW351_R1100
6.12 XFLOW
FI E L D RE C O R D
PACT -- Variable -- Actual pressure analog input LA

(optional)
TACT -- Variable -- Actual temperature analog LA
input (optional)
OUT -- Variable -- Analog output variable LA
TOUT -- Variable -- Mode status and track output LA
value
PSEL G3 - Integer Data Init. STANDARD Select pressure conversion --
Bit 7 type:
STANDARD = use the
pressure conversion value
defined by PRES UNIT.
USER = use the pressure
conversion value defined by
USER PRES.
PUSR R6 Data Init. 0.0000 Value for user-specified --
pressure conversion
TRIN -- Variable -- Tracking input LA
Function
IF ((OPT INIT = NOCHECK) AND (PRES REF < 0)) OR
((OPT INIT = CHECK) AND (PACT = UNDEFINED))
THEN
P1 = P2 = 1
ELSE
P1 = PACT + ABSPRES
P2 = PRES REF + ABSPRES
IF ((OPT INIT = NOCHECK) AND (PRES REF < 0)) OR
((OPT INIT = CHECK) AND (PACT = UNDEFINED))
THEN
T1 = T2 = 1
ELSE
T1 = TACT + ABSTEM P
OW351_R1100 643
6.12 XFLOW
T2 = TEMP REF + ABSTEM P
IF MASSFLOW THEN
IF (P2 = 0) OR (T1 = 0) THEN
OUTVAL = 0
ELSE
OUTVAL = PDIF * (P1/P2) * (T2/T1)
ELSE
IF (P1 = 0) OR (T2 = 0) THEN
OUTVAL = 0
ELSE
OUTVAL = PDIF * (P2/P1) * (T1/T2)
IF OUTVAL < 0 THEN
OUTPUT = 0
ELSE
OUTPUT = GAIN * SQUARE ROOT OF OUTVAL
where:
P1, P2, T1, T2, OUTVAL = local, temporary, real variables
ABSPRES, ABSTEMP = constraints from the pressure and temperature conversion
tables built into the algorithm
644 OW351_R1100
6.13 XMA2
6.13 XMA2
Description
The XMA2 algorithm interfaces a CRT-based soft manual/auto station and an optional QAM,
QAA, QVP, QLI, or QLJ card with the functional processor.
You select one of the following interfaces with TYPE:
 SOFT - Soft manual/auto station only

 QAM - QAM card demand interface with soft manual/auto station
 QAA - QAA card demand interface with soft manual/auto station
 QLI - QLI or QLJ card interface
 QVP - QVP card interface
Functional Symbol
If QLI is set in TYPE and the Controller is reset, powered-up or fails, the output is read from the
QLI or QLJ card and used initially in the OUT field of the algorithm. This reports the status of the
field device before any action is taken by either the algorithm or the operator.
Note: The TPSC and BTSC parameters are used to limit the output value of t he algorithm.
These values must always be 100% and 0%, respectively when a SLIM interfaces to a QLI or
QLJ card.
OW351_R1100 645
6.13 XMA2
Auto Mode
The output equals the gained and biased input plus the bias bar value (OUT= (IN1 x IN1G) +
IN1G + IN1B) except:
the input.
Increase/Decrease set point keys on the Operator’s Keyboard. This value is only added to the
output value in Auto mode; it has no effect on the output (but still may be raised or lowered) in
Manual or Local mode.
If a QAM or QAA interface is selected, the output value is written to the demand counter on the
QAM or QAA card. A digital signal may be written to a QBO card as an optional indication of the
Auto mode by using the ALITE point. This point has the hardware address for the QBO card.
The Increase/Decrease Output keys on the Operator’s Keyboard have no effect in this mode.
Manual Mode
The output is raised or lowered by using the Increase/Decrease Output requests. The raise inhibit
and lower inhibit signals override the Operator’s Keyboard Increase/Decrease Output requests.
The tracking signal causes the output to equal the track input, regardless of the raise/lower inhibi t
If a QAM or QAA interface is selected, the output value is written to the demand counter on the
QAM or QAA card. A digital signal may be written to a QBO card output as an optional indication
of the Manual mode by using the MLITE point.
The output value may also be raised or lowered from the small Loop Interface Module (SLIM) in
this mode.
Local Mode
This mode is only available if a QAM, QAA, QVP, QLI, or QLJ type interface has been selected.
The Increase/Decrease commands from the Operator Interface Module (OIM) directly control the
QAM or QAA card, which is in Manual. The Increase/Decrease commands from the SLIM directly
control the QLI card, which is in Local mode. The algorithm either reads the demand counter on
the QAM or QLI, or the position feedback value on the QAA and causes its output to track the
card’s value. In this tracking mode, all directional commands inside the functional processor (for
example, Variable Input, Raise Inhibit and Lower Inhibit) and directional commands from the
Operator’s station (for example, Increase, Decrease) have no effect on the algorithm.
The QAM card can be optionally put in Auto (Computer) mode when the algorithm receives either
a Manual or Auto mode request from the Operator’s Keyboard. This Auto request is output as a
signal to a QBO card by using the REQ Point.
646 OW351_R1100
6.13 XMA2
Mode Transfers
 The digital reject signal rejects the algorithm from Auto to Manual mode or from Auto to Local
mode when the Manual Inhibit feature is ON.
on the Operator’s Keyboard switch the algorithm to the desired mode if it is not in Local mode
(or if the REQ point has been initialized for a QAM card).
 If the QAM or QAA interface is selected, the OIM can reject the algorithm to Local mode. The
COMP (computer) pushbutton at the OIM causes the algorithm to enter a previously selected
mode.
 If the QAM or QAA interface is selected and there are hardware errors, the algorithm rejects
to Local mode if the NO FAIL feature if OFF. If the QAM interface is selected and the NO
FAIL feature is on, then the algorithm remains in the previous mode and continues to function
normally. The quality of OUTPUT is set to BAD when there are any QAM or QAA hardware
errors.
 If the QLI or QLJ interface is selected, the SLIM can switch the algorithm between Auto,
Manual, and Local modes.
 If the QLI or QLJ interface is selected, and if there are hardware errors, the algorithm rejects
to Local mode. If the card determines that there is a SLIM communications error while it is in
Local mode, it rejects the card to Manual mode. The algorithm also goes to Manual mode.
input when in Auto mode. If the algorithm is in Auto mode and the quality of the cascade input
goes BAD or not GOOD depending on the Quality Reject flag, then the algorithm rejects to
Manual mode as long as the Manual inhibit feature is OFF. If the Manual inhibit feature is on,
the algorithm rejects to Local mode.
 Regardless of the REJQ parameter, the input value is checked for an invalid value when the
algorithm is in Auto mode. If the algorithm is in Auto mode and the value of the input becomes
invalid, the algorithm rejects to Manual mode, providing the Manual Inhibit feature is OFF. If
the Manual Inhibit feature is ON, the algorithm rejects to Local mode if the QAM, QAA, QLI or
QLJ interface is selected. If the algorithm is not in Auto mode and the operator tries to select
Auto mode when the input value is invalid, the algorithm remains in the same mode and does
not reject to Manual mode.
 The track input value is also checked for invalid real numbers when the algorithm is being told
to track. While in Auto mode, if the algorithm is told to track and the track input value is
invalid, the algorithm rejects to Manual mode, providing the Manual Inhibit feature is OFF. In
all modes, the track request is ignored when the track input value is invalid.
 On reset/power-up, the algorithm is in Local mode if a QAM, QAA, QLI or QLJ interface is
selected. If a soft interface is selected, then the algorithm goes to the mode initialized by the
Firstpass mode (FP) parameter unless that mode is blocked by the Manual Inhibit feature.
Note: The Manual Inhibit feature prevents the algorithm from entering Manual mode when it is
on.
OW351_R1100 647
6.13 XMA2
The interface keys of the Operator’s Keyboard are:
Key usage
KE Y US E
MANUAL Function Key Manual mode request

Tracking Signals
to the information found in the input signal TRIN:
Bit description
16 Track Implemented Passed through, set TRUE on first pass to

read the hardware, or set TRUE when not
in Auto mode.

20 Raise inhibit Implemented* Passed through*
648 OW351_R1100
6.13 XMA2
The high and low limit flags, the mode and the tracking signals from the algorithm are output,
algorithm must be specified by the user for correct implementation of the tracking features. If the
upstream algorithm is BALANCER, then the configuration must indicate that this algorithm is
being used with the BALANCER algorithm. Otherwise, the configuration is specified as NORMAL.
If the QAM, QAA, QLI, or QLJ interface is selected, the following hardware related errors are set
in the second status word of the analog output record and cause the analog output to have BAD
quality:
Bit description
2 BAD hardware status. The Power and Card OK bits on the QLI or QLJ card were
not set.
If an invalid or BAD hardware status error caused the algorithm to reject to Local, the quality
remains BAD on the output and the algorithm remains in Local mode until the error is cleared.
The error bit in the second status word remains set in Local mode, even though the quality is
GOOD, which enables you to determine the cause of the reject.
of the cascade input when in Auto mode.
is set to BAD, the OUT value is invalid, and the drop is placed into alarm.
The TPSC and BTSC parameters are used to limit the output value of the algorithm. These values
must always be 100% and 0%, respectively, when interfacing to a QLI card which is connected to
an SLIM.
When the LI is configured as an electric drive card type, a difference between the actual position
and the demand value < FINE causes no raise or lower action to be taken. A difference in CRSE
causes fast raise or lower action to be taken. The slow rates specified by the ONOFF parameter
determines the raise or lower action taken when the difference is between FINE and CRSE.
Any output raise or lower request, from Operator station, are sent directly to the QLI configured as
an electric drive card type when it is in Failed Local mode. The QLI outputs any LIM raise or lower
requests for the output, then outputs any Controller raise or lower requests for the output to the
digital raise or lower outputs.
When the position feedback signal of a QLI configured as an electric drive card type fails, the QLI
goes to Failed Local mode and the value of output point is the feedback signal from the drive. The
output bar LIM display flashes between 0 and 100% to indicate the Failed Local mode.
The Reverse (Inverse) voltage configuration parameter on the QLI or QLJ card causes the output
voltage to be zero for an output value of 100%. The default for this configuration parameter is
Normal Voltage (that is, the output voltage is full voltage for an output of 100% and is zero volts
for an output of 0%).
OW351_R1100 649
6.13 XMA2
The options to have runbacks and/or interface to an electric drive on the QLI card must be
configured through the card-type jumpers on the QLI card.
CAUTION! When using the XMA2 algorithm with a BALANCER algorithm, follow these
guidelines.
If XMA2 precedes BALANCER, set the XMA2 CNFG parameter to NORMAL.
For all XMA2s that immediately follow BALANCER, set XMA2’s CNFG parameter to
BALANCER.
For XMA2s that follow XMA2s in guideline 2, set CNFG parameter to NORMAL.
FI E L D RE C O R D

number
IN1G R5-Real Tuning Required 1.0 Gain on input. The —
Constant cascade gain should
never be initialized to
zero; if it is, the drop is
placed into alarm.
IN1B R6-Real Tuning Required 0.0 Bias on input —

Constant
TPSC R7-Real Tuning Required 100.0 Maximum value of the —

Constant output point
BTSC R8-Real Tuning Required 0.0 Minimum value of the —
Constant output point
TPBS R2-Real Tuning Required 0.0 Maximum value of the —
Constant bias bar
BTBS R3-Real Tuning Required 0.0 Minimum value of the —
Constant bias bar
PCNT X1-Byte Tuning Required 4 Percent change in first —
Constant four seconds
Constant remaining for ramp to
full scale
650 OW351_R1100
6.13 XMA2
FI E L D RE C O R D
TYPE G0-Integer Data Init. Required SOFT Algorithm type: —

Bits 0 and 1
SOFT — Soft M/A only
QAM — QAM interface
QAA — QAA interface
QLI — QLI or QLJ
interface
HWAD B2-Integer Data Init. Required 0 Card address for any —
hardware interface
(see page 3).
CARD X5-Byte Data Init Required 1 PCI Card Number (1, —

2)
FP G0 - Integer Data Init. Required MANUAL First pass mode. —
Bit 8 Algorithm goes to this
mode on
reset/power-up:
MANUAL: Manual
mode
AUTO: Auto mode
QVPO G0-Integer Data Init. Required NO Select QVP interface —
Bit 9 (NO, YES)
OIM G0-Integer Data Init. Required AUTO OIM computer push —

Bit 2 button action
(for QAM and QAA
interface only)
AUTO — Algorithm
goes from Local to
Auto mode when
pushed.
MAN — Algorithm
goes from Local to
Manual mode when
pushed.
FAIL G0-Integer Data Init. Required OFF No card failure option —
Bit 3 (for QAM interface
only)
OFF — Algorithm goes
to local mode upon
power failure or loss of
the Keep Alive
watchdog timer.
ON — Algorithm
remains in the previous
mode upon loss of the
card.
CHK G1-Integer Data Init. Required NO Check healthy bit for —
Bit 0 QAA card.
OW351_R1100 651
6.13 XMA2
FI E L D RE C O R D
REJQ G0-Integer Data Init. Required BAD Quality reject type —

Bits 6 and 7 (only has meaning if
Manual Inhibit is OFF):
BAD — Algorithm
rejects to Manual
mode when the quality
of the CAS input goes
BAD and the algorithm
is in Auto mode.
NOTGOOD —
Manual mode when
the quality of the CAS
input is NOT GOOD
and the algorithm is in
Auto mode.
OFF — The quality of
the cascade input is
not checked or used to
reject the algorithm to
Manual mode when
the algorithm is in Auto
mode.
INHB G0-Integer Data Init. Required OFF Manual inhibit: —
Bit 4
OFF — Manual mode
is allowed.
ON — Manual mode is
not allowed. The OIM
pushbutton is set to
AUTO.
CNFG G0-Integer Data Init. Required NORMAL Configuration type: —

Bit 5
NORMAL — Upstream
algorithm is not
BALANCER.
BALANCER —
Upstream algorithm is
BALANCER.
Constant
INVR X3-Byte Data Init Required NO Inverse voltage for the —

QLI card:
NO — Normal voltage
YES — Inverse voltage
652 OW351_R1100
6.13 XMA2
FI E L D RE C O R D
ONOFF G3-Integer Data Init Required 771 Slow raise/lower pulse —

on/off times for electric
drive signals (low byte
= Off time; high byte =
On time) in units of 0.1
or 0.004 seconds. This
field is used only for
the QLI card.
Note: 771 = 0303H)
Two ranges of values

(0.1 or 0.004 second
resolution) are
available for the
electric drive slow
action pulse on/off
values (ONOFF TIME
field):
For 0.1 second
resolution, byte values
in the range 0 to 127
(00 to 7FH) are used.
For example, 03H
represents a 0.3
second pulse time (3 *
0.1).
For 0.004 second
(80 to FFH) are used
to represent the range
0 to 127. For example,
83H represents a
0.012 second plus time
(3 * 0.004).
The second range of
values (0.004 second
resolution) is available
only with Group 3 QLI
cards (3QLI31).
OW351_R1100 653
6.13 XMA2
FI E L D RE C O R D
FAST G4-Integer Data Init Required 65280 Fast raise/lower pulse —

on/off times for electric
drive signals (low byte
= Off time; high byte =
On time) in units of 0.1
or 0.004 seconds. This
field is used only for
the QLI card.
Note: 771=0303H)
Two ranges of values

(0.1 or 0.004 second
resolution) are
available for the
electric drive slow
action pulse on/off
values (ONOFF TIME
field):
For 0.1 second
(00 to 7FH) are used.
For example, 03H
represents a 0.3
second pulse time (3 *
0.1).
For 0.004 second
(80 to FFH) are used
to represent the range
0 to 127. For example,
83H represents a
0.012 second plus time
(3 * 0.004).
The second range of
values (0.004 second
resolution) is available
only with Group 3 QLI
cards (3QLI31).
PRAT X6-Byte Data Init Required 3 Priority runback rate in —
percent per second for
an electric drive QLI
card type.
FINE S9-Real Data Init Required 1 Difference (in percent) —

between the actual
position and the
demand value below
which no raise or lower
action is taken.
Applicable only for a
QLI card configured for
an electric drive.
654 OW351_R1100
6.13 XMA2
FI E L D RE C O R D
CRSE T1-Real Data Init Required 5 Difference (in percent) —

between the actual
position and the
demand value above
which fast raise or
lower action is taken.
Applicable only for a
QLI card configured for
an electric drive.
IN1 — Variable Required — Variable analog input LA
TOUT — Variable Required — Mode and Status LA

output signals
REJ — Variable Optional — Manual Reject digital LD, LP

input signal; you may
enter the name of a
point.
OUT — Variable Required — Analog output variable LA
TRIN — Variable Optional — Tracking analog input LA

variable
BIAS — Variable Optional — Analog bias bar LA

variable output
REQ — Variable Optional — Auto Request output LD
ALITE — Variable Optional — Auto Light output LD

MLITE — Variable Optional — Manual Light output LD
LIOUT G0-Integer Data Init Required — Specifies output —
Bit 11 significance when
configured for Electric
Drive:
 0 – DEMAND
 1 – POSITION
OW351_R1100 655
6.14 XML2
6.14 XML2
Description
The XML2 algorithm performs a manual loader function. The algorithm provides an interface to
the Operator’s soft station. Interfaces to the hard Operator Interface Module (OIM) station and set
point portion of the QAM, QLI or QLJ card may each be initialized. If the QAM, QLI or QLJ
hardware address is initialized, the algorithm reads the set point stored on the QAM, QLI or QLJ
set point counter to use as its output value. This counter may be incremented/decremented at any
time by external Increase/Decrease contacts from an OIM station which is wired directly to the
QAM, QLI or QLJ card. If the QAM, QLI or QLJ hardware address is not initialized, the algorithm
uses the last output value as its output value.
Functional Symbol
The output of this algorithm may be increased and/or decreased by the hard OIM station or the
Operator’s soft station. If the hardware addresses of the Increase and Decrease contacts from the
hard OIM station are initialized, then the algorithm monitors the contacts that it reads from the
QCI or QBI inputs (which are connected to the hard OIM station) for increase and/or decrease
requests for the set point.
This initialization is typically used when a QAA card is used in place of the QAM card and an OIM
set point adjustment feature is desired. It continually checks the Set Point Increase/Decrease
function keys from the Operator’s station for increase/decrease requests for the set point output. If
requests are received from both the hard and soft stations at the same time, the hard OIM station
contacts override the Operator’s Keyboard keys. On power-up or reset of the functional
processor, the output is the initial value of the algorithms output (default value = 0.0) if the QAM,
QLI or QLJ interface is not initialized. Otherwise, the output is the current value stored on the
QAM, QLI or QLJ set point counter.
656 OW351_R1100
6.14 XML2
If the QLI card is selected in the CARD algorithm field and the Controller is reset, powered-up or
fails, the set point is read from the QLI or QLJ card and used initially in the OUT field of the
algorithm. This reports the status of the field device before any action is taken by either the
algorithm or the operator. The interface keys of the Operator’s Keyboard are:
Key usage
KE Y US E
Set Point Increase Function Key Raise the output
Set Point Decrease Function Key Lower the output
Note: If the top and bottom scales are equal, the high limit flag is set and the output value is
equal to the top scale.
If the algorithm is told to track and the track input is invalid, the track request is ignored and the
drop is placed into alarm.
If the QAM, QLI or QLJ hardware address is initialized, this value is written to the set point
counter on the specified card.
If the algorithm is operating with a QLI or QLJ interface and the QLI or QLJ card is in Local mode,
the output of the algorithm cannot be changed from the Operator’s station. In this case, the output
of the algorithm can be changed from the SLIM station only.
If a QLI or QLJ interface is selected and the QLI or QLJ hardware address is not zero, the default
configuration data for the set point section is written to the QLI or QLJ card. If the switch on the
QLI or QLJ card is not in the “Ignore EEPROM” position, the data is saved in EEPROM on the
QLI or QLJ card. The set point top of scale, bottom of scale and units parameters for the
configuration data are taken from the top of bar, bottom of bar, and the first four characters of the
engineering units fields in the output record. The output record must be modified by the user to
contain the correct engineering units that display at the SLIM. The top of bar and bottom of bar
fields in the output record are initialized to the SCALE TOP and SCALE BOT values by the
algorithm.
If XML2 is to write the set point value to the QLI or QLJ card, then changes to the set point value
(that is, tracking, Operator’s station raise/lower requests, etc.) are implemented as described
previously. The top of bar, bottom of bar and engineering units parameters of the out put point are
used to initialize the set point section of the configuration data on the QLI or QLJ card.
OW351_R1100 657
6.14 XML2
However, if the QLI or QLJ set point value is being written to the QLI or QLJ card by the PVSPSLI
algorithm, then the set point value for this algorithm is not read from the QLI or QLJ card, but is
determined by the last output value. Under these conditions, the XML2 algorithm monitors the QLI
or QLJ card for any raise and lower requests from the SLIM. Raise/lower requests from the SLIM
override any other set point change requests received by this algorithm (that is, tracking,
Operator’s station raise/lower requests, etc.). If there are no SLIM requests, then the set point
value is changed as described previously. The set point value is only written to the output point.
Neither the set point value nor the configuration data is written to the QLI or QLJ card under these
conditions.
If a card interface is specified, the following, hardware-related errors are set in the second status
word of the analog output record and cause the analog output to have BAD quality:
Bit description
2 BAD hardware status. The Power and Card OK bits on the QLI or QLJ card were
not set or the Power and Alive Bits on the QAM card were not set.
658 OW351_R1100
6.14 XML2
Tracking Signals
of the analog point. This algorithm takes the action shown in the following table in response to the
information found in the input signal TRIN:
Bit description
16 Track Implemented Not used

The high and low limit flags are output to TOUT to be used for display. If the QAM, QLI or QLJ
hardware address is initialized, the quality of OUT is BAD if there are any QAM, QLI or QLJ
hardware errors. Otherwise, the quality of OUT is GOOD when not tracking or set to the quality of
the track input variable when tracking.
OW351_R1100 659
6.14 XML2
FI E L D RE C O R D

number
TPSC R2-Real Tuning Required 100.0 Maximum value of the —
Constant point
BTSC R3-Real Tuning Required -100.0 Minimum value of the —

Constant point
PCNT X1-Byte Tuning Required 4 Percent change in —
Constant remaining for ramp to
full scale
CARD X3-Byte Data Init. Required SOFT Card type: —

SOFT =No hardware
interface
QLI = QLI or QLJ card
interface
QAM = QAM card
interface
PCI X5 - Byte Data Init Required 1 PCI Card Number —
(1, 2)
HWAD B2 - Integer Data Init. Required 0 Hardware address —
(see page 3) of the
QAM / QLI/QLJ card.
Note: The QAM card

hardware address is
the jumpered
address plus one.
INCR — Variable Optional — Hardware address LD

(see page 3) of the
Increase contact (in
decimal bytes).
DECR — Variable Optional — Hardware address LD
(see page 3) of the
Decrease contact.
variable
TRIN — Variable Optional — Tracking analog input LA
variable
TOUT — Variable Required — Mode and Status LA

output signals
660 OW351_R1100
6.15 XPIDSLI
6.15 XPIDSLI
Description
The XPIDSLI algorithm combines the functions of a PID controller with a soft M/A station interface
on a calculated set point and a soft M/A station interface on the output with a Q-Line Loop
Interface (QLI) or Q-Line Loop Interface with Output Readback (QLJ) card interface. The
algorithm functions in Supervisory, Cascade, Auto, or Manual modes.
Note: You cannot operate this algorithm without a QLI or QLJ card interface.
Functional Symbol
The following modes are available:
Mode
XPIDSLI M O D E M O D E DI S P L AY E D AT LIM
Local Local
Manual Manual
Auto Auto
Cascade Cascade
Supervisory Cascade
In the event of reset, power-up, or failover, both the set point and output values are read from the
card.
CAUTION! You MUST follow Guidelines 1 and 2. Failure to do so could result in a negative
value which causes the process to become uncontrollable.
OW351_R1100 661
6.15 XPIDSLI
Guidelines
1. You MUST use PV GAIN and PV BIAS to normalize the proces s variable inputs to a 0 to 100
percent value. Use this equation: (PV x PV GAIN) + PV BIAS = PV percent.
2. You MUST use SET GAIN and SET BIAS to normalize the set point to a 0 to 100 percent
value. The set point definition depends on which mode is operating: CAS, SUPV, or internal
set point. Use this equation: (SP x SP BIAS) + SP BIAS = set point percent.
3. Determine set point high and low limits with these equations:
set point high limit = (100 - SP BIAS)/SP GAIN
set point low limit = (0 - SP BIAS)/SP GAIN
Note: The SCALE TOP and SCALE BOT parameters are used to limit the output value of the
algorithm. These values must always be 100% and 0% respectively when an LIM interfaces to a
QLI or QLJ card.
662 OW351_R1100
6.15 XPIDSLI
Supervisory and Cascade Modes
The Increase/Decrease Output keys and the Increase/Decrease Set Point keys on the LIM have
no effect in these modes. Both the set point and output values are written to the card in these
modes.
Auto Mode
The Increase/Decrease Set Point keys on the LIM override any other set point change requests
except digitally entered set points (DES). However, the Increase/Decrease Output keys on the
LIM have no effect in this mode.
Note: A digitally entered set point (DES) is a value entered by the user in a MAC Monitoring
Program tuning diagram. Lik ewise, a digitally entered output (DEO) is a value entered by the
user.
The internal set point is read from the card, raised or lowered, and written back to the card. Also,
the calculated output value is written to the card in this mode.
Manual Mode
The Increase/Decrease Output keys and the Increase/Decrease Set Point keys on the LIM
override any other set point and output change requests except digitally entered outputs (DEO).
Both the set point and output values are read from the card, either raised or lowered, and then
written back to the card in this mode.
Local Mode
The set point and output values may only be changed by the Increase/Decrease Set Point keys
and the Increase/Decrease Output keys at the LIM in this mode. The algorithm reads the set point
and output values from the card and causes these output values to track the card’s values. In this
tracking mode, all set point and output raise and lower requests from the functional processor, the
Operator’s/Alarm Console or DEO or DES are ignored.
Mode Transfers
The algorithm transfers between the Supervisory, Cascade, Auto, Manual, and Local modes as
follows:
 The digital reject signal will reject the algorithm to Manual mode or to Local mode when the
Manual Inhibit feature is ON and when it is TRUE and the quality is not BAD.
 The Supervisory Request, Cascade Request, Auto Request and Manual Request signals
from the SUPV, CAS, AUTO and MAN mode request keys on the Operator’s Keyboard will
switch the algorithm to the desired mode if it is not in Local mode.
 The Cascade Request, Auto Request, Manual Request, and Local Request signals from the
CASC, AUTO, MAN and LOC mode request keys on the LIM will switch the algorithm to the
desired mode.
 The algorithm rejects to Local mode if there are any hardware errors.
 On reset/power-up, the algorithm goes to the mode initialized by the Firstpass mode (FP
MODE) parameter unless that mode is blocked by either the Manual Inhibit or Auto Inhibit
features. If both the Manual and Auto Inhibit features are ON, then the Firstpas s mode is
Cascade mode. Otherwise, the Firstpass mode is the mode which has its inhibit feature OFF.
OW351_R1100 663
6.15 XPIDSLI
 If the Quality Reject (QUAL REJ) feature is OFF, then no quality checks are performed on any
of the input variables. Otherwise, the controller automatically rejects to the Manual mode (or
Local mode if the Manual Inhibit feature is ON) when:
 The mode is Cascade and the quality of the cascade set point goes BAD or not GOOD,
depending on the Quality Reject flag.
 The mode is Supervisory and the quality of the supervisory set point goes BAD or not
GOOD, depending on the Quality Reject flag.
 The mode is Cascade, Supervisory or Auto and the quality of the process variable goes
BAD or not GOOD, depending on the Quality Reject flag.
 If the algorithm is in a given mode and the quality of one of the points being checked goes
BAD or not GOOD (depending on the Quality Reject flag), then the algorithm rejects to
Manual mode as long as the Manual Inhibit feature is OFF, or to Local mode if the Manual
Inhibit Feature is ON. If the algorithm is in a given mode and the operator tries to select a
mode which has BAD or not GOOD quality (depending on the Quality Reject flag) on one of
the points being checked, then the algorithm remains in the same mode and does not reject.
 Regardless of the Quality Reject parameter (QUAL REJ), the input values to the algorithm are
checked for invalid real numbers. In a given mode, the following inputs are checked:
 AUTO: process variable input
 CASCADE: process variable and cascade input
 SUPERVISORY: process variable and supervisory input
 If the algorithm is in a given mode and the value of one of the inputs being checked become
invalid, the algorithm rejects to Manual mode, providing the Manual Inhibit feature if OFF, or
to Local mode if the Manual Inhibit Feature is ON. If the algorithm is in a given mode and the
operator tries to select a mode where one of the input values being checked is invalid, the
algorithm remains in the same mode and does not reject.
 The track input value is also checked for invalid real numbers when the algorithm is told to
track. If the algorithm is told to track and the track input value is invalid, then the algorithm
rejects to Manual mode, providing the Manual Inhibit feature is OFF, or to Local mode if the
Manual Inhibit Feature is ON. In all modes, the track request is ignored when the track input
value is invalid.
Note: The Auto and Manual Inhibit flags prevent the algorithm from going to either the Auto or
Manual modes, respectively. The algorithm remains in the previous mode when it tries to enter a
mode that is block ed by one of these Inhibit flags.
The set point top of scale, bottom of scale and units parameters for the configuration data are
taken from the top of bar, bottom of bar and the first four characters of the engineering units fields
in the set point output record. The set point output record must be modified by the user to contain
the correct engineering units that will be displayed at the LIM. The set point top of bar and bottom
of bar are initialized by the XPIDSLI algorithm according to the GAIN and BIAS parameters
specified.
The configuration data for the set point and for the output sections is written to the card. If the
switch on the card is not the Ignore EEPROM position, the data is saved in EEPROM on the card.
664 OW351_R1100
6.15 XPIDSLI
The Reverse (Inverse) Voltage configuration parameter on the card causes the output voltage to
be zero for an output value of 100% and to be full voltage for an output value of 0%. The default
for this configuration parameter is Normal Voltage (that is, the output voltage is full voltage for an
output of 100% and is zero volts for an output of 0%). In order to use the Reverse (Inverse)
Voltage option, the Inverse Voltage, INV VOLT, configuration parameter in this algorithm must be
set to ON.
CAUTION! Due to the possibility of causing a process upset, use extreme care when
reversing the output voltage of the QLI or QLJ card while online.
The configuration is not written to the card when it is in Local mode.
Note: When the QLI or QLJ is configured as an electric drive card type, a difference between
the actual position and the demand value <=1% will cause no raise or lower action to be tak en.
A difference >= 5% will cause fast raise or lower action to be tak en.
These values are fixed and cannot be changed. The slow rates specified b y the ONOFF TIME
Parameter determine the raise/ lower action tak en when the difference is between 1% and 5%.
The same slewing rates are used for both the output and the set point changes.
The interface keys of the Operator’s Keyboard are:
Key usage
KE Y US E
AUTO function key Auto mode request

MAN function key Manual mode request
CASC function key Cascade mode request
SUPV function key Supervisory mode request
Set Point Increase function key Raise the set point
Output Increase function key Raise the output
Output Decrease function key Lower the output
OW351_R1100 665
6.15 XPIDSLI
Optional Function
The algorithm has the option of using either a digital or a packed point for the manual reject signal
(REJ).
If the reject input is a packed point and the requested mode is valid for a given type of algorithm,
a packed reject input will cause the algorithm to reject to the requested mode as long as it is not
blocked by other options such as MANUAL or AUTO INHIBIT.
Mode
M O D E RE Q U E S T BI T
Manual 0
Auto 1
Supervisory 2
Cascade 3
DDC 4
Tracking Signals
Tracking is incorporated into the algorithm to ensure a bumpless transfer between each of the
modes. External tracking and limiting are done through signals passed in the upper 16 bits of the
third status word of the analog track point. This algorithm takes the following action in response to
the information found in the input signal TRIN:
16 Track Implemented Passed through or set TRUE

when not in Cascade mode
17 Track if lower Implemented when not in Not used
Manual mode*
18 Track if higher Implemented when not in Not used
Manual mode*
23 Deviation alarm No action Set when the deviation of
process variable and set point is
greater than the given Deviation
Alarm deadband
27 Supervisory mode No action Supervisory mode
28 Cascade mode No action Cascade mode
666 OW351_R1100
6.15 XPIDSLI
29 DDC mode No action No used

"Understanding tracking" (see page 9).
The high and low limit flags, the mode, and the tracking signals from the algorithm are output as
TOUT, to be used for display and by an upstream algorithm. When tracking, the quality of the
output is set to the quality of the track input variable. Otherwise, the qualities of the outputs are
set according to the following if there are no hardware errors:
Mode
MOD E S E T P O I N T Q U AL I TY O U TP U T Q U AL I T Y
Supervisory Quality of SUPV Worse quality of PV or SUPV

Cascade Quality of CAS Worse quality of PV or CAS
Auto GOOD quality Quality of PV
Manual Good quality GOOD quality
Other outputs consist of:
1. The set point for the PID (in the same units as the cascade input).
2. A real analog value representing the process variable deviation from the set point (in percent
of full scale).
 If the algorithm calculates an invalid real number for the output, the quality of the output is
set to BAD and the output value will be invalid. Consequently, if an invalid value is
entered as an input to the algorithm, or if the algorithm generates an invalid value for the
 If the algorithm generates an invalid track output value, the cascade input value is used
as the track output unless it is invalid. The track output value is not updated if both the
calculated track output and the cascade input values are invalid.
 If the algorithm generates an invalid real number as the new value of the set point, the
internal set point is not updated. However, when the set point value becomes invalid the
drop is placed into alarm, and the quality of the set point is set to BAD.
OW351_R1100 667
6.15 XPIDSLI
Bit 10 is set in the second status word of the output record for one loop whenever the output
configuration data section is reconfigured. Bit 10 is set in the second status word of the set point
record for one loop whenever the set point configuration data section is reconfigured. This does
not affect the quality of either record (that is, the output and/or set point quality is not set BAD
when the card is reconfigured).
The following hardware related errors are set in the second status word of the analog output
record and cause the analog output to have BAD quality.
Bit description
0 Invalid hardware address. The user specified a hardware address outside the legal range of 0
to 3FCH.
1 Write verification error. The algorithm tried to reconfigure the output section of the card but was
unable to do so.
2 Bad hardware status. The power and card OK bits on the card were not set
3 Configuration error. The algorithm tried to reconfigure the card for two consecutive loops. This
could be caused by another algorithm having the same address, where both algorithms are
trying to reconfigure the same section of the card.
4 Normalization error. The Read back error failed on QLJ; the mode is not changed. Position
feedback signal below 3.4 milliamps on QLI configured as an electric drive card type; QLI goes
into Failed Local mode. Once the signal returns above 3.7 milliamps, the error clears and BAD
quality is removed. QLI goes to Local mode if LIM is present; otherwise, it goes into Man ual
mode.
Any of these errors will cause the algorithm to reject to Local mode. If an invalid hardware
address or bad hardware status error caused the algorithm to reject to Local, the quality will
remain BAD on the output, and the algorithm will remain in Local mode until the error is cleared.
If a write verification error or configuration error caused the algorithm to reject to Local, the quality
will become GOOD on the output and the algorithm will remain in Local mode until Local mode is
exited via the LIM. The error bit in the second status word will remain set in Local mode, even
though the quality is GOOD, so as to enable the user to determine the cause of the reject.
Note: If the card determines that there is a LIM communications error while it is in Local mode, it
will reject the card to Manual mode. The algorithm will also go to Manual mode.
668 OW351_R1100
6.15 XPIDSLI
The following hardware related errors are set in the second status word of the analog set point
record and cause the analog set point to have BAD quality:
Bit description
0 Invalid hardware address. The user specified a hardware address outside the legal range
of 0 to 3FCH.
1 Write verification error. The algorithm tried to reconfigure the set point section of the card
but was unable to do so.
2 Bad hardware status. The power and card OK bits on the card were not set
3 Configuration error. The algorithm tried to reconfigure the card for two consecutive loops.
This could be caused by another algorithm having the same address, where both
algorithms are trying to reconfigure the same section of the card.
Any of these errors will cause the algorithm to reject to Local mode. If an invalid hardware
address or bad hardware status error caused the algorithm to reject to Local, the quality wil l
remain BAD on the set point and the algorithm will remain in Local mode until the error is cleared.
If a write verification error or configuration error caused the algorithm to reject to Local, the quality
will become GOOD on the set point and the algorithm will remain in Local mode until Local mode
is exited via the LIM. The error bit in the second status word will remain set in Local mode (even
though the quality if GOOD) to enable the user to determine the cause of the reject.
N AME LC A L G . T YP E DE F AU L T DE S C R I P TI O N MI N .
FI E L D RE C O R D
DIAG LU - Data Init. 223 Tuning diagram number --

Integer
ERRD T2 - Real Tuning 0.0 PID error deadband --
Constant
PGAIN S6 - Real Selectable 1.0 PID proportional gain (Š>=0). LA
If the proportional gain equals
zero, the proportional part will
not be included in the output
INTG S7 - Real Selectable 10.0 PID integral reset time in LA
seconds. If the reset time
equals zero, the integral part
will not be included in the
output. If the reset time does
not equal zero, its value must
be greater than or equal to
the sampling time.
OW351_R1100 669
6.15 XPIDSLI
FI E L D RE C O R D
DGAIN* S8 - Real Selectable 0.0 PID derivative gain (>=0). If LA

the derivative gain equals
zero, the derivative part will
not be included in the output
and the rate constant will be
set to half the sampling time
when in Auto, Cascade, or
Supervisory modes and the
algorithm is not tracking.
If the derivative gain does not
equal zero, the derivative rate
constant must be greater than
or equal to half the sampling
time.
DRAT S9 - Real Tuning 0.0 PID derivative rate constant in --
Constant seconds.
TYPE Y0 - Bits 0 Data Init. NORMAL Type of PID controller: --
and 1
NORMAL: Regular PID
control
ESG: PID control with error
squared on the proportional
gain term
ESI: PID control with error
squared on the integral term
ACTN Y0 - Bit 2 Data Init. INDIRECT Direction flag: --
INDIRECT: Error = Set point
process variable
DIRECT: Error = Process
variable - set point
* These fields may be displayed and tuned at the LIM.
TPSC R7 - Real Tuning 100.0 Maximum value of the output --

Constant point
BTSC R8 - Real Tuning 0.0 Minimum value of the output --
Constant point
PVG S1 - Real Tuning 1.0 Gain on the process variable --
Constant input and set point. The gain
on the set point should never
be initialized to zero; if it is, an
invalid real number is
generated as the new set-
point value.
PVB S2 - Real Tuning 0.0 Bias on the process variable --
Constant input and set point
670 OW351_R1100
6.15 XPIDSLI
FI E L D RE C O R D
FP X6 - Bits 5 Data Init. MANUAL Firstpass mode (algorithm --

and 6 goes to this mode on
reset/power-up):
MANUAL: Manual mode
AUTO: Auto mode
CASCADE: Cascade mode
MINH Y0 - Bit 4 Data Init. OFF Manual inhibit: --
OFF: Manual mode is
allowed.
ON: Manual mode is not
allowed.
AINH Y0 - Bit 5 Data Init. OFF Auto inhibit: --
OFF: Auto mode is allowed.
ON: Auto mode is not
allowed.
QUAL Y0 - Bits 6 Data Init. BAD Quality reject type (only has --
and 7 meaning if Manual inhibit is
OFF):
BAD: Algorithm rejects to
Manual mode when the
quality of the point being
checked is BAD.
NOTGOOD: Algorithm rejects
to Manual mode when the
quality of the point being
checked is not GOOD.
OFF: The quality of the input
variables is not checked and
does not cause the algorithm
to reject to Manual mode.
STRK Y0 - Bit 3 Data Init. OFF Set point tracks process --
variable in Manual mode:
ON: SET POINT tracks
process variable.
OFF: SET POINT does not
track process variable.
DEVD T1 - Real Tuning 5.0 Deviation alarm deadband --
Constant
ALRM G4 - Tuning 0 Number of seconds for No --
Integer Constant Deviation Alarm signal when
the set point changes by more
than one percent.
TRAT R9 - Real Tuning 2.5 Track ramp rate (units per --
Constant second)
OW351_R1100 671
6.15 XPIDSLI
FI E L D RE C O R D
PCNT X1 - Byte Data Init. 4 Percentage of change in firs t --

four seconds
TIME X2 - Byte Data Init. 25 Seconds left for ramp to full --
scale
INVR X3 - Bit 0 Data Init. OFF Inverse voltage from card to --
drive:
OFF: Voltage from card to
drive is normal.
ON: Voltage from card to
drive is reversed.
HWAD B2 - Data Init. 0 Hardware address of QLI --
Integer card; must be entered in
decimal bytes
CARD X4 - Byte Data Init. 1 PCI card number --
ONOFF G6 - Data Init. 771 Slow raise/lower pulse on/off --
Integer times for electric drive signals
(low byte = Off time; high byte
= On time) in units of 0.1 or
0.004 seconds. This field is
used only for the QLI card.
Note: 771 = 0303H
Two ranges of values (0.1 or

0.004 second resolution) are
available for the electric drive
slow action pulse on/off
values (ONOFF TIME field):
For 0.1 second resolution,
byte values in the range 0 to
127 (00 to 7FH) are used. For
example, 03H represents a
0.3 second pulse time (3 x
0.1).
For 0.004 second resolution,
byte values in the range 128
to 255 (80 to FFH) are used
to represent the range 0 to
127. For example, 83H
represents a 0.012 second
pulse time (3 x 0.004).
The second range of values
(0.004 second resolution) is
available only with Group 3
QLI cards (3QLI31).
PRAT X9 - Data Init. 3 Priority runback rate in --
Byte percent per second for an
electric drive QLI card type.
PV -- Variable -- Process variable analog input LA
672 OW351_R1100
6.15 XPIDSLI
FI E L D RE C O R D
CAS -- Variable -- Cascade variable analog LA

input (optional); the user may
draw a line to initialize a point.
TOUT -- Variable -- Mode and status track value LA
for CAS variable.
SUPV -- Variable -- Supervisory variable analog LA
input (optional); the user may
draw a line to initialize a point.
REJ -- Variable -- Manual Reject digital input LD, LP
signal (optional); the user may
enter the name of a point.
OUT -- Variable -- Analog output variable LA
TRIN -- Variable -- Tracking analog input variable LA
SET POINT -- Variable -- Set point selected for the PID LA
controller
DEVIATION -- Variable -- Error between process LA
variable and set point for PID
OW351_R1100 673
SECTION 7
7 Foundation Fieldbus algorithms
IN THIS SECTION
What are Foundation Fieldbus algorithms? ............................................................... 675

Ovation Fieldbus algorit hms and function blocks ....................................................... 676
FFAI ...................................................................................................................... 678
FFAO..................................................................................................................... 681
FFDI ...................................................................................................................... 684
FFDO..................................................................................................................... 687
FFISEL/FFISELX .................................................................................................... 690
FFMAI .................................................................................................................... 698
FFMA O .................................................................................................................. 702
FFMDI ................................................................................................................... 704
FFMDO .................................................................................................................. 708
FFPID .................................................................................................................... 712
7.1 What are Foundation Fieldbus algorithms?
Fieldbus algorithms interface to Foundation Fieldbus function blocks. Function blocks are self-
contained software modules that reside in Foundation Fieldbus devices. Fieldbus algorithms
Implement Foundation Fieldbus logic at the transmitter level. Therefore, Fieldbus devices can be
controlled by Ovation Fieldbus algorithms and integrated as part of an Ovation control scheme.
The Fieldbus algorithms are listed below, The reference pages for Fieldbus algorithms use the
same format as the standard Ovation algorithm reference pages (see page 46).

 FFARTHM - Foundation Fieldbus arithmetic.
 FFINT - Foundation Fieldbus integrator.
 FFISEL/FFISELX (see page 690) - Foundation Fieldbus input selector.
 FFMAO (see page 702) - Foundation Fieldbus multiple analog output.
 FFMDI (see page 704) - Foundation Fieldbus multiple digital input.
 FFMDO (see page 708) - Foundation Fieldbus multiple digital output.
 FFSGCR - Foundation Fieldbus signal characterizer.
OW351_R1100 675
7.2 Ovation Fieldbus algorithms and function blocks
Fieldbus devices are digital field instruments containing processors that monitor the performance
and state of the device. Self-contained software modules known as function blocks, reside in the
Fieldbus devices.
While function blocks reside in a device, the Ovation control system uses algorithms on control
sheets that mimic the function blocks. Therefore, Fieldbus devices can be controlled by Ovation
Fieldbus algorithms and can be part of an Ovation control scheme.
Foundation Fieldbus allows you to execute control algorithms in the Controller, in the Fieldbus
devices, or in both. However, the key to successful control is making an algorithm choice that best
supports your plant’s needs.
Examples
The Ovation Controller can handle Fieldbus function block to Fieldbus function block or Ovation
Algorithm to Fieldbus function block control schemes. For example:
Scenario 1
Scenario 2
676 OW351_R1100
7.2.1 ST AT bits use d with function blocks
The STAT point can be used to indicate problems with a function block.
0-3 Fieldbus communication errors:

 3 - Invalid device name.
 4 - Gateway not configured.
 6 - No Fieldbus map file.
 7 - Communication time out.
 8 - Loss of communication with the Gateway.
 9 - Cannot write link data.
 11 - Invalid function block.
 12 - Invalid function block parameter.
4-7 Indicate Mode/Tuning Information:
 1 - Mode change requested.
 2 - Tune change requested.
8 - 11 Tuning/Mode Errors:
 1 - Error changing modes.
 2 - Error tuning parameter.
 3 - Algorithm tuning parameter is mismatched with the function block.
 4 - Invalid mode.
12 - 15 Mode Requested:
 1 - Request Auto mode.
 2 - Request Manual mode.
 3 - Request Cascade mode.
OW351_R1100 677
7.3 FFAI
7.3 FFAI
Description
The FFAI algorithm is used to interface to a Fieldbus Analog Input function block. The FFAI
algorithm shadows a single measurement value and status from a Fieldbus device to an Ovation
point (Out).
The STAT point indicates status and error information of the function block. See the STAT bits
table (see page 677) for bit definitions.
The PV point displays the Process Variable value and status from the function block. The TOUT
point displays the algorithm’s mode and tracking signals.
The FFAI algorithm supports Manual and Auto modes. These modes are tunable from both the
Ovation tuning graphic as well as the Fieldbus Module Engineering window in the Developer
Studio.
Fieldbus algorithm quality
All Fieldbus algorithms shadow the actual Fieldbus function block quality unless a communication
error occurs. In the case of a communication error, the output quality will be defined by the FERR
parameter. If the actual Fieldbus function block output quality is BAD or the FERR parameter is
set to BAD and a communication error occurs, the output quality will be marked as BAD and the
output value will latch at the last known GOOD quality value. The AMODE parameter will display
an unknown mode or no mode in this scenario.
Functional Symbol
Tracking Signals
The high and low limits flags and tracking signals from the algorithm are output to TOUT, and are
to be used for display and by an upstream algorithm. All Fieldbus function blocks support different
modes, which is also reflected in the TOUT point. The following information is TOUT’s output
associated with the algorithm.
Bit description
BI T DE S C R I P TI O N TOUT S I G N AL
16 Track TRUE when mode is Auto/Manual/Local.
17 Track if lower Not used.

18 Track if higher Not used.
19 Lower inhibit Not used.
20 Raise inhibit Not used.
21 Conditional Track Not used.
678 OW351_R1100
7.3 FFAI
22 Not used Not used.

23 Deviation Alarm Not used.
24 Local Manual mode Local mode.
25 Manual mode Manual mode.
26 Auto mode Auto mode.
27 Supervisory mode Not used.
28 Cascade mode Not used.
29 DDC mode Not used.
30 Low limit reached Low limit reached.
31 High limit reached High limit reached.
O V ATI O N FI E L D B U S T YP E RE Q U I R E D / DE F AU L T DE S C R I P TI O N MI N .
P AR AM P AR AM O P TI O N AL V AL U E POI N T
RE C .
DIAG — LU - Byte Required 130 Tuning diagram —

number.
NORM MODE. X3 - Byte Required Manual Normal mode for —
NORMAL FFAI. The choices
are: MANUAL and
AUTO.
QUAL — X4 - Byte Required Bad If Fieldbus quality is —
uncertain, set the
output points to one
of the following
qualities: BAD,
GOOD, FAIR, or
POOR.
FERR — X5 - Byte Required Bad If an error occurs —
between
reading/writing to the
Fieldbus device, then
set the output point’s
quality to: BAD,
GOOD, FAIR, or
POOR.
OUT OUT — Required — Required analog LA
output point.
TOUT — — Required — Mode and tracking LA

signals
PV PV — Optional — Optional analog LA
output point for
process variable.
OW351_R1100 679
7.3 FFAI
RE C .
STAT — — Required — Required output LP

point. This point
contains status
(see page 677) of the
Fieldbus algorithm.
AMODE BLOCK_ Y0 - Optional -- Actual mode of the LA
MODE_ Variable function block. The
ACTUAL modes display in
decimal format:
 0 = Invalid or No
mode
 1 = Remote Output
(Rout)
 2 = Remote
Cascade (Rcas)
 3 = Cascade (Cas)
 4 = Automatic
(Auto)
 5 = Manual (Man)
 6 = Local Override
(LO)
 7 = Initialization
Manual (IMan)
 8 = Out of Service
(O/S)
680 OW351_R1100
7.4 FFAO
7.4 FFAO
Description
The FFAO algorithm is used to interface to a Fieldbus Analog Output function block. The FFAO
algorithm shadows a single measurement value and status from a Fieldbus device to the Ovation
point (Out).
The FFAO algorithm supports Manual, Auto and Cascade modes. These modes are tunable from
both the Ovation tuning graphic as well as the Fieldbus Module Engineering window in the
Developer Studio.
Functional Symbol
Tracking Signals
to be used for display and by an upstream algorithm.
Bit description

19 Lower inhibit TRUE when output value is at the low limit.
20 Raise inhibit TRUE when output value is at the high limit.
OW351_R1100 681
7.4 FFAO

28 Cascade mode Cascade mode.
RE C .

number.
NORMAL FFAO. The
choices are:
MANUAL, AUTO,
CASCADE.
QUAL — X4 - Byte Required Bad If Fieldbus quality —
is uncertain, set
the output points
to one of the
following
qualities: Bad,
Good, Fair, or
Poor.
between
reading/writing to
the Fieldbus
device, then set
the output point’s
quality to: Bad,
Good, Fair, or
Poor.
IN1 CAS_IN — Required Bad Required analog LA
input point.
TOUT BKCAL_OUT — Required — Mode and LA

tracking signals .
OUT OUT — Optional — Optional analog LA
output point.
682 OW351_R1100
7.4 FFAO
RE C .
PV PV — Optional — Optional analog LA

output point for
process variable.
point. This point
contains status
(see page 677) of
the Fieldbus
algorithm.
AMODE BLOCK_MODE_ Y0 - Optional -- Actual mode of LA
ACTUAL Variable the function
block. The
modes display in
decimal format:
 0 = Invalid or
No mode
 1 = Remote
Output (Rout)
 2 = Remote
Cascade
(Rcas)
 3 = Cascade
(Cas)
 4 = Automatic
(Auto)
 5 = Manual
(Man)
 6 = Local
Override (LO)
Manual (IMan)
 8 = Out of
Service (O/S)
OW351_R1100 683
7.5 FFDI
7.5 FFDI
Description
The FFDI algorithm is used to interface to a Fieldbus Discrete Input function block. The FFDI
algorithm shadows a single discrete input and status from a two-state field to an Ovation point
(OUT).
The PV point displays the Process Variable value and status from the function block. The TOUT
point displays the algorithms mode and tracking signals.
The FFDI algorithm supports Manual and Auto modes. These modes are tunable from both the
Studio.
Some Fieldbus device manufacturers put additional information in bits 1 through 7 of the
value/status register. To access these bits, select "octet" in the Type parameter field (see the
Algorithm Definitions table).
Functional Symbol
Tracking Signals
Bit description

684 OW351_R1100
7.5 FFDI

O V ATI O N FI E L D B U S T YP E RE Q U I R E D / D E F AU L T DE S C R I P TI O N MI N .
RE C .

number.
NORMAL FFDI. The choices
are: MANUAL and
AUTO.
is uncertain, set the
output points to
one of the following
qualities: BAD,
GOOD, FAIR, or
POOR.
FERR — X5 - Byte Required Bad A field in the —
algorithm record. If
an error occurs
between
reading/writing to
the Fieldbus
device, then set the
output point’s
quality to: BAD,
GOOD, FAIR, or
POOR.
OW351_R1100 685
7.5 FFDI
RE C .
TYPE — X9 - Byte Required Bit Read output value —

as a bit or octet.
The choices are:
 Bit
 Octet
OUT OUT_D — Optional — Optional digital LD
output point.
signals.
PV PV_D — Optional — Optional digital LD
output point for
process variable.
point. This point
contains status
(see page 677) of
the Fieldbus
algorithm.
POUT — — Optional — Optional packed LP
output point. Allows
you to specify
which bits to use
from the packed
point.
decimal format:
mode
 1 = Remote
Output (Rout)
 2 = Remote
Cascade (Rcas)
 3 = Cascade
(Cas)
 4 = Automatic
(Auto)
 6 = Local
Override (LO)
Manual (IMan)
 8 = Out of
Service (O/S)
686 OW351_R1100
7.6 FFDO
7.6 FFDO
Description
The FFDO algorithm is used to interface to a Fieldbus Discrete Output function block. The FFDO
algorithm shadows a discrete value and status from a fieldbus device to an Ovation point (OUT).
The FFDO algorithm supports Manual, Auto, and Cascade modes. These modes are tunable from
both the Ovation tuning graphic as well as the Fieldbus Module Engineering window in the
Developer Studio.
Some Fieldbus device manufacturers put additional information in bits 1 through 7 of the
value/status register. To access these bits, select "octet" in the Type parameter field (see the
Algorithm Definitions table).
Functional Symbol
Tracking Signals
to be used for display and by an upstream algorithm. All fieldbus function blocks support different
Bit description

OW351_R1100 687
7.6 FFDO

O V ATI O N FI E L D B U S T YP E RE Q U I R E D / DE F AU L T D E S C R I P TI O N MI N .
RE C .

number.
NORMAL FFDO. The
choices are:
MANUAL, AUTO,
and CASCADE.
is uncertain, set
the output points
to one of the
following qualities:
Bad, Good, Fair,
or Poor.
between
reading/writing to
the Fieldbus
device, then set
quality to: Bad,
Good, Fair, or
Poor.
TYPE — X9 - Byte Required Bit Read output value —
as a bit or octet.
The choices are:
 Bit
 Octet
688 OW351_R1100
7.6 FFDO
RE C .
IN CAS_IN_D — Optional — Required digital LD

input point.
signals.
OUT OUT — Optional — Required digital LD
output point.
point. This point
contains status
(see page 677) of
the Fieldbus
algorithm.
PIN — — Optional — Optional packed LP
input point. Allows
you to specify
which bit to use
from the packed
point.
BKCAL BKCAL_ — Required — Track out value. LD
OUT_D For use with
BKCAL_IN_D.
MODE_ Variable function block.
ACTUAL The modes
display in decimal
format:
mode
 1 = Remote
Output (Rout)
 2 = Remote
Cascade (Rcas)
 3 = Cascade
(Cas)
 4 = Automatic
(Auto)
 5 = Manual
(Man)
 6 = Local
Override (LO)
Manual (IMan)
 8 = Out of
Service (O/S)
OW351_R1100 689
7.7 FFISEL/FFISELX
7.7 FFISEL/FFISELX
Description
The FFISEL algorithm interfaces to a Foundation Fieldbus Input Selector function block. The Input
Selector function block generates an output selected from up to four inputs based on a configured
selection type. The following selection types are used:
 Maximum.
 Minimum.
 Middle.
 Average.
 First GOOD (first input with GOOD quality).
The FFISEL algorithm shadows the Input Selector function block input and output values. The
Input Selector function block does not support back calculation so Ovation tracking is not
supported.
The FFISEL algorithm supports Manual and Auto modes.
The FFISEL algorithm also supports the Extended Input Selector function block, as implemented
in Rosemount field devices. The extended function block is often referred to as ISELX. The
extended function block adds four additional inputs for a total of eight.
All Fieldbus algorithms shadow the actual Fieldbus function block quality unless a communicatio n
Functional Symbol for FFISEL
690 OW351_R1100
7.7 FFISEL/FFISELX
Functional Symbol for FFISELX
Direct Entered Output (DEO) Support
The FFISEL algorithm supports Direct Entered Output functionality for the OUT parameter, but
only in Manual mode.
Signal Diagram Support
The FFISEL algorithm supports the capability to change the Fieldbus mode between MAN and
AUTO from an Ovation Signal Diagram. A mode indication displays on the Signal Diagram. The
Signal Diagram provides an entry field for the Direct Entered Output of the OUT parameter.
Controller Failover Support
During Controller failover and also during Fieldbus port download, it may not be possible to get
GOOD values from the device. The FFISEL algorithm supports failover and port download by
using the last GOOD values and quality during this time.
OW351_R1100 691
7.7 FFISEL/FFISELX
SELECT_TYPE Parameter
The SELECT_TYPE parameter configures the type of selection the Input Selector function block
performs. It is a contained parameter; and therefore, is not available as an input to the FFISEL
algorithm. Selection processing takes place after input processing. Inputs with corresponding
Disable inputs set to TRUE are discarded. Inputs whose status is BAD are discarded. If no inputs
or fewer than those defined in MIN_GOOD remain, selection does not take place.
The SELECT_TYPE parameter must be entered through the Control Builder Properties Editor
(see Ovation Control Builder User Guide for more information on the Property Editor).
The following table shows the select types and corresponding values:
V AL U E S E L E C TI O N T YP E
1 First Good -- transfer the first remaining input to the output of the function block.
2 Minimum -- transfer the lowest remaining input value to the output of the function
block.
3 Maximum -- transfer the highest remaining input value to the output of the function
block.
4 Middle -- transfer the middle value to the output. If two inputs are in the middle,
transfer the average of the two.
5 Average -- transfer the average of the remaining inputs to the output of the function
block.
Tracking Signals
The Foundation Fieldbus Input Selector function block does not support back calculation so
Ovation tracking is not supported. However, the TOUT parameter is still used to indicate the
mode of the underlying function block.
16 Track Not used.

21 Conditional track Not used.
23 Deviation alarm Not used.
24 Local Manual mode Not used.
692 OW351_R1100
7.7 FFISEL/FFISELX
30 Low limit reached Not used.

31 High limit reached Not used.
Extended Input Selector Function Block Support
The FFISEL algorithm also supports the Extended Input Selector function block as implemented
in Rosemount field devices. The extended function block is often referred to as ISELX, and adds
four additional inputs IN5 through IN8. It also adds four disable inputs, DIS5 through DIS8. An
additional output, DOUT, indicates an alarm state for the function block's analog output.
Two functional symbols are defined for the FFISEL algorithm. One symbol supports the Input
Selector function block and has four analog inputs. The second symbol supports the extended
Input Selector function block (ISELX) and has eight analog inputs, eight digital inputs, and the
additional digital output, DOUT. Both symbols display in the Control Builder's Add Algorithm
dialog box (see Ovation Control Builder User Guide for more information on the Add Algorithm
dialog box).
Note: The Developer Studio view of the FFISEL algorithm will show all of the possible
parameters (IN1-IN8 and DIS1-DIS8) whether it is extended or not.
RE C O R D
Inputs:
IN1 IN_1 Variable Optional -- Optional analog LA

input point.

input point.

input point.
input point.
IN5* IN_5 Variable Optional -- Optional analog LA
input point.
Used with
FFISELX.
input point.
Used with
FFISELX.
OW351_R1100 693
7.7 FFISEL/FFISELX
RE C O R D

input point.
Used with
FFISELX.
input point.
Used with
FFISELX.
DIS1 DISABLE_1 Variable Optional -- Optional digital LD
input point
disables
corresponding
input:
 0 = Use
 1 = Disable
input point
disables
corresponding
input:
 0 = Use
 1 = Disable
input point
disables
corresponding
input:
 0 = Use
 1 = Disable
input point
disables
corresponding
input:
 0 = Use
 1 = Disable
DIS5* DISABLE_5 Variable Optional -- Optional digital LD
input point
disables
corresponding
input:
 0 = Use
 1 = Disable
Used with
FFISELX.
694 OW351_R1100
7.7 FFISEL/FFISELX
RE C O R D

input point
disables
corresponding
input:
 0 = Use
 1 = Disable
Used with
FFISELX.
input point
disables
corresponding
input:
 0 = Use
 1 = Disable
Used with
FFISELX.
input point
disables
corresponding
input:
 0 = Use
 1 = Disable
Used with
FFISELX.
OPSEL OP_SELECT Variable Optional -- Operator Select LA
-- optional input
used to force
selection of a
given input.
 0 = Not forced
Outputs:
OUT OUT Variable Required -- Required LA

analog output
point.
TOUT -- Variable Required -- Mode and LA
tracking signals.
DOUT* OUT_D Variable Optional -- Optional packed LD
output point
indicates alarm
condition.
SEL SELECTED Variable Optional -- Optional analog LA
output indicates
which input is
selected.
OW351_R1100 695
7.7 FFISEL/FFISELX
RE C O R D
STAT -- Variable Required -- Required output LP

point. This point
contains the
status of the
Fieldbus
function block.
AMODE BLOCK_MODE_ Y0 - Optional -- Actual mode of LA
ACTUAL Variable the function
block. The
modes display
in decimal
format:
 0 = Invalid or
No mode
 1 = Remote
Output (Rout)
 2 = Remote
Cascade
(Rcas)
 3 = Cascade
(Cas)
 4 = Automatic
(Auto)
 5 = Manual
(Man)
 6 = Local
Override (LO)
7 =
Initialization
Manual (IMan)
 8 = Out of
Service (O/S)
Parameters:
NORM MODE.NORMAL X3 - Data Required Manual Normal mode --

Init. for FFISEL. The
choices are:
 Man
 Auto
QUAL -- X4 - Data Required BAD If Fieldbus --
Init. quality is
uncertain, set
the outputs to
one of the
following:
 BAD
 POOR
 FAIR
 GOOD
696 OW351_R1100
7.7 FFISEL/FFISELX
RE C O R D
FERR -- X5 - Data Required BAD If an error --

Init. occurs
reading/writing
the Fieldbus
device, set the
outputs to one
of the following:
 BAD
 POOR
 FAIR
 GOOD
STYPE SELECT_TYPE B8 -- Required First Select Type for --
Tuning GOOD algorithm
Constant operation:
 Maximum
 Minimum
 Middle
 Average
 First GOOD
XTYPE -- B9 - Data Required Not Indicates --
Init. Extended whether or not
the function
block is
extended.
BERR BLOCK_ERR G0 - Alg. -- -- Block error --
Init. storage
* Extended Input Selector variables (as used in certain Rosemount devices). Used if XTYPE = Extended.
OW351_R1100 697
7.8 FFMAI
7.8 FFMAI
Description
The FFMAI algorithm is used to interface to a Fieldbus Multiple Analog Input function block. The
FFMAI algorithm shadows up to eight measurement values and statuses from a fieldbus device to
Ovation output points.
The FFMAI algorithm supports Manual and Auto modes. These modes are tunable from both the
Studio.
Note: The FFMAI algorithm also supports the FFMAI_RMT function block .
Functional Symbol
Tracking Signals
Bit description

698 OW351_R1100
7.8 FFMAI

RE C .
DIAG — LU - Byte Required 133 Tuning diagram. —

number
NORM MODE. X3 - Byte Required Manual Normal mode —
NORMAL for FFMAI. The
choices are:
MANUAL and
AUTO.
QUAL — X4 - Byte Required BAD If Fieldbus —
quality is
uncertain, set
the output
points to one of
the following
qualities: BAD,
GOOD, FAIR,
or POOR.
OW351_R1100 699
7.8 FFMAI
RE C .
FERR — X5 - Byte Required BAD If an error —

occurs between
reading/writing
to the Fieldbus
device, then set
the output
point’s quality
to: BAD,
GOOD, FAIR,
or POOR.
OUT1 OUT_1 — Optional — Optional analog LA
output point.
output point.
output point.
output point.
output point.
output point.
output point.
output point.
TOUT — — Required — Mode and LA
tracking signals.
point. This point
contains status
(see page 677)
of the Fieldbus
algorithm.
700 OW351_R1100
7.8 FFMAI
RE C .
AMODE BLOCK_ Y0 - Optional -- Actual mode of LA

MODE_ Variable the function
ACTUAL block. The
modes display
in decimal
format:
 0 = Invalid or
No mode
 1 = Remote
Output (Rout)
 2 = Remote
Cascade
(Rcas)
 3 = Cascade
(Cas)
 4 = Automatic
(Auto)
 5 = Manual
(Man)
 6 = Local
Override (LO)
7=
Initialization
Manual (IMan)
 8 = Out of
Service (O/S)
OW351_R1100 701
7.9 FFMAO
7.9 FFMAO
Description
The FFMAO algorithm is used to interface to a Foundation Fieldbus Multiple Analog Output
function block. The FFMAO algorithm shadows up to eight measurement values and statuses
from Ovation analog process points to a Fieldbus device.
Functional Symbol
RE C .
DIAG -- LU - Required Tuning diagram --

Byte number.
QUAL -- X4 - Required BAD If Fieldbus quality is --
Byte uncertain, set the
outputs to one of the
following: BAD, POOR,
FAIR, GOOD.
FERR -- X5 - Required BAD If an error occurs --

Byte reading/writing the
Fieldbus device, set
the outputs to one of
the following: BAD,
POOR, FAIR, GOOD.
702 OW351_R1100
7.9 FFMAO
RE C .
IN1 IN_1 -- Optional -- Optional analog input LA

point.
point.
point.
point.
point.
point.
point.
point.
STAT -- -- Required -- Required output point. LP
This point contains the
status (see page 677)
of the Fieldbus function
block.
decimal format:
mode
(Rout)
 2 = Remote Cascade
(Rcas)
 4 = Automatic (Auto)
(LO)
Manual (IMan)
(O/S)
OW351_R1100 703
7.10 FFMDI
7.10 FFMDI
Description
The FFMDI algorithm is used to interface to a Foundation Fieldbus Multiple Digital Input function
block. The FFMDI algorithm shadows up to eight digital states and statuses from a Fieldbus
device to Ovation digital process points.
Functional Symbol
704 OW351_R1100
7.10 FFMDI
Tracking Signals
The FFMDI function block, as an input, does not support back calculation or the Cas mode, and
so Ovation tracking is not supported. However the TOUT parameter is still used to indicate the
mode of the underlying function block.
Bit description
16 Track Not used.

24 Local Manual mode Local Override mode.
RE C .
DIAG -- LU - Byte Required Tuning diagram --

number.
NORM MODE. X3 - Byte Required Manual Normal mode for --
NORMAL FFMDI. The choices
are: MANUAL and
AUTO.
QUAL -- X4 - Byte Required BAD If Fieldbus quality is --
uncertain, set the
outputs to one of the
following: BAD,
POOR, FAIR, GOOD.
OW351_R1100 705
7.10 FFMDI
RE C .
FERR -- X5 - Byte Required BAD If an error occurs --

reading/writing the
Fieldbus device, set
the outputs to one of
the following: BAD,
POOR, FAIR, GOOD.
TYPE -- X9 - Byte Required Bit Read input values as a --
bit or octet. The
choices are:
 Bit
 Octet
OUT1 OUT_D1 -- Optional -- Optional digital output LD
point.
point.
point.
point.
point.
point.
point.
point.
POUT1 OUT_D1 -- Optional -- Optional packed digital LP
output point.
output point.
output point.
output point.
output point.
output point.
output point.
output point.
TOUT -- -- Required -- Mode and tracking LA
signals.
706 OW351_R1100
7.10 FFMDI
RE C .
STAT -- -- Required -- Required output point. LP

This point contains the
status (see page 677)
of the Fieldbus
function block.
decimal format:
mode
(Rout)
 2 = Remote Cascade
(Rcas)
 4 = Automatic (Auto)
(LO)
Manual (IMan)
(O/S)
OW351_R1100 707
7.11 FFMDO
7.11 FFMDO
Description
The FFMDO algorithm is used to interface to a Foundation Fieldbus Multiple Digital Output
function block. The FFMDO algorithm shadows up to eight digital states and statuses from
Ovation digital process points to a Fieldbus device.
Functional Symbol
708 OW351_R1100
7.11 FFMDO
Tracking Signals
The FFMDO function block does not support back calculation or the Cas mode, and so Ovation
tracking is not supported. However the TOUT parameter is still used to indicate the mode of the
underlying function block.
Bit description
16 Track Not used.

24 Local Manual mode Local Override mode.
25 Manual mode Not used.
30 Low limit reached Not used.
31 High limit reached Not used.
RE C .
DIAG -- LU - Byte Required Tuning diagram --

number.
QUAL -- X4 - Byte Required BAD If Fieldbus quality --
is uncertain, set the
outputs to one of
the following: BAD,
POOR, FAIR,
GOOD.
OW351_R1100 709
7.11 FFMDO
RE C .
FERR -- X5 - Byte Required BAD If an error occurs --

reading/writing the
Fieldbus device,
set the outputs to
one of the
following: BAD,
POOR, FAIR,
GOOD.
TYPE -- X9 - Byte Required Bit Read input values --
as a bit or octet.
The choices are:
 Bit
 Octet
IN1 IN_D1 -- Optional -- Optional digital LD
input point.
input point.
input point.
input point.
input point.
input point.
input point.
input point.
PIN1 IN_D1 -- Optional -- Optional packed LP
digital input point.
710 OW351_R1100
7.11 FFMDO
RE C .
TOUT -- -- Required -- Mode and tracking LA

signals.
STAT -- -- Required -- Required output LP
point. This point
contains the status
(see page 677) of
the Fieldbus
function block.
decimal format:
mode
 1 = Remote
Output (Rout)
 2 = Remote
Cascade (Rcas)
 3 = Cascade
(Cas)
 4 = Automatic
(Auto)
 6 = Local
Override (LO)
Manual (IMan)
 8 = Out of
Service (O/S)
OW351_R1100 711
7.12 FFPID
7.12 FFPID
Description
The FFPID algorithm shadows the Fieldbus FFPID function block input and output values. It also
maps the Fieldbus back-calculation points to Ovation tracking points.
The FFPID algorithm supports Manual, Auto, and Cascade modes. These modes are tunable
from both the Ovation tuning graphic as well as the Fieldbus Module Engineering window in the
Developer Studio.
Functional Symbol
Tracking Signals
Bit description
16 Track Set TRUE when not in Cascade mode.

712 OW351_R1100
7.12 FFPID

The High and Low limit flags, the mode and the tracking signals from the algorithms are output to
RE C .

number.
NORMAL function block.
The choices are:
MANUAL, AUTO
and CASCADE.
QUAL — X4 - Byte Required BAD If Fieldbus —
quality is
uncertain, set the
output points to
one of the
following
qualities: BAD,
GOOD, FAIR,
OR POOR.
FERR — X5 - Byte Required BAD If an error occurs —
between
reading/writing to
the Fieldbus
device, then set
quality to: BAD,
GOOD, FAIR,
OR POOR.
FGAIN FF_GAIN R1 - Real Required 1.0 Feed forward —
gain.
OW351_R1100 713
7.12 FFPID
RE C .
GAIN GAIN R4 - Real Required 1.0 Device gain. —

TPSC OUT_HI_LIM R2 - Real Required 100.0 Maximum output —
value.
BTSC OUT_LO_LIM R3 - Real Required 0.0 Minimum output —
value.
DRAT RATE R6 - Real Required 0.0 Derivative action. —
INTG RESET R5 - Real Required 10.0 Integral time. —
TPBS SP_HI_LIM R7 - Real Required 100.0 Maximum —
setpoint value.
BTBS SP_LO_LIM R8 - Real Required 0.0 Minimum —
setpoint value.
PV IN — Required — Required analog LA
input.
CAS CAS_IN — Optional — Optional analog LA
input.
TOUT BKCAL_OUT — Required — Mode and LA
tracking signals.
FF FF_VAL — Optional — Optional analog LA

input for feed
forward value.
OUT OUT — Required — Required analog LA
input.
TRIN BKCAL_IN — Optional — Optional analog LA
input point. This
is the track input
point.
SP SP — Optional — Optional analog LA
output for set
point.
point. This point
contains the
status
(see page 677)
of the Fieldbus
function block.
714 OW351_R1100
7.12 FFPID
RE C .
AMODE BLOCK_ Y0 - Optional -- Actual mode of LA

MODE_ Variable the function
ACTUAL block. The
modes display in
decimal format:
 0 = Invalid or
No mode
 1 = Remote
Output (Rout)
 2 = Remote
Cascade
(Rcas)
 3 = Cascade
(Cas)
 4 = Automatic
(Auto)
 5 = Manual
(Man)
 6 = Local
Override (LO)
Manual (IMan)
 8 = Out of
Service (O/S)
OW351_R1100 715
SECTION 8
8 Understanding the Ovation SIS algorithms
IN THIS SECTION
What are Ovation SIS Logic Solver algorit hms? ........................................................ 718
LSAI ...................................................................................................................... 721
LSALM................................................................................................................... 723
LSAND................................................................................................................... 725
LSAVTR................................................................................................................. 727
LSBDE ................................................................................................................... 744
LSBFI .................................................................................................................... 746
LSBFO................................................................................................................... 749
LSCALC................................................................................................................. 752
LSCE M .................................................................................................................. 767
LSCMP .................................................................................................................. 790
LSDI ...................................................................................................................... 792
LSDO..................................................................................................................... 794
LSDVC................................................................................................................... 801
LSDVTR ................................................................................................................ 812
LSLI M .................................................................................................................... 829
LSMI D ................................................................................................................... 832
LSNAND ................................................................................................................ 836
LSNDE................................................................................................................... 838
LSNOR .................................................................................................................. 840
LSNOT................................................................................................................... 842
LSOFFD ................................................................................................................ 843
LSOND .................................................................................................................. 845
LSOR..................................................................................................................... 847
LSPDE ................................................................................................................... 849
LSRET ................................................................................................................... 851
LSRS ..................................................................................................................... 853
LSSEQ................................................................................................................... 855
LSSR ..................................................................................................................... 860
LSSTD ................................................................................................................... 862
LSTP ..................................................................................................................... 869
LSXNOR ................................................................................................................ 871
LSXOR .................................................................................................................. 872
SIS connector algorithm table .................................................................................. 873
GSECPARA MREF .................................................................................................. 874
NONSECPA RA M ................................................................................................... 875
SECPARA M ........................................................................................................... 876
SECPARA MREF .................................................................................................... 878
OW351_R1100 717
8.1 What are Ovation SIS Logic Solver algorithms?
Safety Instrumented System (SIS) algorithms are self-contained software modules that reside in
Logic Solvers. All Logic Solver output channel algorithms can only be accessed by the Logic
Solver where the physical connection is performed.
Note: The term "Logic Solver" refers to both the 1508 Logic Solver and the CSLS.
The use of SIS algorithms and the SIS system, is described in Ovation Safety Instrumented
System (SIS) User Guide.
The SIS algorithms are listed and briefly described in the following table. Note that the SIS
algorithm reference pages follow the same format as the standard Ovation algorithms
(see page 43).
Note: Some SIS algorithm parameters may show "LX" in the Minimum Point Record column in
the Algorithm Definitions table. LX indicates that the parameter can tak e any (LA (analog), LD
(digital), or LP (pack ed)) point record.
Algorithms from the SIS family are not valid in control macros or standard control functions
Algorithm Reference table
A L G O R I TH M DE S C R I P TI O N FU N C TI O N
LSAI Analog Input Accesses a single analog measurement value and quality from an I/O
(see page 721) channel. The input value is a transmitter's 4 to 20 mA signal.
LSALM Alarm Performs alarm detection on a user-specified input. The parameters
(see page 723) generated can then be used to generate alarm events at the user
interface.
LSAND Logical AND Generates a digital output value based on the logical AND of 2 to 16
(see page 725) digital inputs. The algorithm supports signal quality propagation.
LSAVTR Analog Voter Monitors a number of input values and determines if there are enough
(see page 727) votes to trip. If a configured number of the inputs vote to trip, the
algorithm trips and sets the output of the algorithm to 0 (zero).
LSBDE Bi-Directional Generates a True (1) digital pulse output when the digital input makes
(see page 744) Edge Trigger a positive (False-to-True) or negative (True-to-False) transition since
the last execution of the algorithm. The algorithm supports signal
quality propagation.
LSBFI Boolean Fan In Generates a digital output based on the weighted binary sum, binary
(see page 746) coded decimal (BCD) representation, or logical OR of 1 to 16 digital
inputs. The algorithm supports signal quality propagation.
LSBFO Boolean Fan Decodes a binary weighted input to individual bits and generates a
(see page 749) Out digital output value for each bit (as many as 16 outputs). The
algorithm supports signal quality propagation.
LSCALC Calculation/ Allows you to specify an expression that determines the algorithm's
(see page 752) Logic output. Mathematical functions, logical operators, constants and
parameter references can be used in the expression.
LSCEM Cause Effect Defines interlock and permissive logic that associates as many as 16
(see page 767) Matrix (uses inputs and 16 outputs. Configure one or more inputs to trip each
advanced output. When an input becomes active, all outputs associated with
editor) that input trip.
718 OW351_R1100
LSCMP Comparator Compares two values and sets a Boolean output based on that
(see page 790) comparison.
LSDI Digital Input Accesses a single digital measurement value and quality from a two -
(see page 792) state field device and makes the processed physical input available to
other algorithms. The algorithm supports signal inversion, and signal
quality propagation..
LSDO Digital Output Takes a digital input value repres enting the commanded output state
(see page 794) and writes it to a specified Digital Output channel. The algorithm
supports fault state detection and field device confirmation.
LSDVC Digital Valve Drives a HART Two-state Output channel connected to a digital valve
(see page 801) Controller controller. The algorithm supports partial stroke testing, fault state
detection, and field device confirmation.
LSDVTR Digital Voter Monitors a number of input values and determines if there are enough
(see page 812) votes to trip. If a configured number of the inputs vote to trip, the
algorithm trips and sets the output of the algorithm to 0 (zero).
LSLIM Limit Limits an input value between two reference values. The algorithm
(see page 829) has options that set the output to a default value or the last value if
the input becomes out of range.
LSMID Middle Signal Selects between multiple analog signals. The algorithm selects the
(see page 832) Selector mid-valued input from the inputs that are not disabled and do not
have Bad status. If there is an even number of inputs, the average of
the two middle valued inputs is used as the middle value.
LSNAND Logical NAND Generates a digital output value based on the logical AND of 2 to 16
(see page 836) digital inputs, then performs a NOT on the result. The algorithm
supports signal quality propagation.
LSNDE Negative Edge Generates a True (1) digital pulse output when the digital input makes
(see page 838) Trigger a negative (True-to-False) transition since the last execution of the
algorithm. The algorithm supports signal quality propagation.
LSNOR (see Logical NOR Generates a digital output value based on the logical OR of 2 to 16
page 840) digital inputs, then performs a NOT on the result. The algorithm
supports signal quality propagation.
LSNOT Logical NOT Logically inverts a digital input signal and generates a digital output
(see page 842) value. The algorithm supports signal quality propagation.
LSOFFD Off-Delay Delays the transfer of a False (0) digital input value to the output by a
(see page 843) Timer specified time period. The algorithm supports signal quality
propagation.
LSOND On-Delay Delays the transfer of a True (1) digital input value to the output by a
(see page 845) Timer specified time period. The algorithm supports signal quality
propagation.
LSOR Logical OR Generates a digital output value based on the logical OR of 2 to 16
(see page 847) digital inputs. The algorithm supports signal quality propagation.
LSPDE Positive Edge Generates a True (1) digital pulse output when the digital input makes
(see page 849) Trigger a positive (False-to-True) transition since the last execution of the
algorithm. The algorithm supports signal quality propagation.
LSRET Retentive Generates a True (1) digital output after the input has been True for a
(see page 851) Timer specified time period. The elapsed time the input has been True and
the output value are reset when the reset input is set True.
LSRS Reset/Set Generates a digital output value based on NOR logic of reset and set
(see page 853) Flip-Flop inputs.
OW351_R1100 719
LSSEQ Sequencer Associates system states with actions to drive outputs based on the
(see page 855) (uses current state.
advanced
editor)
LSSR Set/Reset Flip- Generates a digital output value based on NAND logic of set and
(see page 860) Flop reset inputs.
LSSTD State Implements a user-defined state machine. The state machine
(see page 862) Transition describes the possible states, and the transitions between those
Diagram (uses states, that can occur.
advanced
editor)
LSTP Timed Pulse Generates a True (1) digital output for a specified time duration whe n
(see page 869) the input makes a positive (False-to-True) transition. The output
remains True even when the input returns to its initial digital value
and returns to its original False value only when the output is True
longer than the specified time duration.
LSXNOR Logical XNOR Performs a NOT on the exclusive OR of two inputs.
(see page 871)
LSXOR Logical XOR Performs an exclusive OR of two inputs to produce an output.
(see page 872)
8.1.1 SIS algorithm type s
There are five types of SIS logic algorithms:
 Input/Output (I/O) algorithms – Used to reference hardware points.

 Math algorithms – Perform mathematical functions for conversion, integration, and totaling.
 Timer/Counter algorithms – Perform timing and counting functions for control and
sequencing.
 Logical algorithms – Perform logic functions for sequencing, scheduling, and interlocking.
 Advanced Control algorithms – Perform complex algorithms for advanced process control.
720 OW351_R1100
8.2 LSAI
8.2 LSAI
Description
The Logic Solver Analog Input (LSAI) algorithm accepts a single analog input signal from an input
channel and makes it available to other algorithms.
The LSAI algorithm provides an interface to analog input devices connected to Logic Solvers that
are on the same SIS Data Server. Some typical analog devices are differential pressure, flow,
temperature, and level transmitters.
Analog inputs can be from conventional or HART channels. This algorithm does not use digital
values from HART channels.
The LSAI algorithm does not have alarms.
Functional Symbol
Algorithm Execution
The LSAI algorithm accesses a single analog measurement value and quality from an input
channel.
The LSAI algorithm supports signal scaling and signal quality calculation.
The algorithm's output parameter (OUT) reflects the process variable (PV) value and quality.
When you configure the LSAI algorithm, you select the input channel associated with an analog
measurement by configuring the Ovation point. You select the point and the parameter the LSAI
algorithm accesses on that channel. The channel specified can be one of the 16 channels on this
Logic Solver or an input channel on a Logic Solver on the same SIS Data Server.
The Ovation system cannot change the scaling in a HART device connected to a Logic Solver
channel. Such changes must be done using AMS Device Manager or a handheld configurator.
These changes do not propagate into the Ovation database.
OW351_R1100 721
8.2 LSAI
Quality Handling
The SOP8 (Quality Opt:Bad if Limited) parameter allows you to select options for quality handling
and processing. This parameter is set in channel properties (see Ovation Safety Instrumented
System (SIS) User Guide for more information). The supported quality option for the Analog Input
algorithm is:
 Bad if Limited
When this option is selected, the quality of PV and OUT is Bad if the quality of the referenced
channel is Bad due to exceeding the overrange, underrange, NAMUR, or sensor failure limits.
FI E L D RE C .
OUT R2 - Real Variable Required - Analog Output with Quality LA

PV R3 - Real Variable Optional - Analog Output Value Only LA
FVAL R4 - Real Variable Optional - Hardware Channel Value LA
BLERR G0 - Integer Variable Optional - Block Error Status LX
 256 - Input Failure/Bad
PV
TPSC S1 - Real Data Init Required 100 Output Scale: Top. -
This parameter is copied
from the channel
configuration and can't be
changed in algorithm
configuration.
BTSC S2 - Real Data Init Required 0 Output Scale: Bottom. -
This parameter is copied
from the channel
configuration.
SOP8 YQ - Data Init. Required 0 Quality Opt: Bad if Limited. -
Integer This parameter is copied
Bit 8 from the channel
configuration.
 0 - No
 1 - Yes
722 OW351_R1100
8.3 LSALM
8.3 LSALM
Description
The Logic Solver Alarm (LSALM) algorithm detects alarm conditions on an analog input you
specify. Use the algorithm to generate an alarm condition that can be referenced by an alarm in
the control modules.
Functional Symbol
Algorithm Execution
Use the Alarm algorithm to detect alarm conditions for analog parameters from other algorithms.
You can choose the alarm detection type (High or Low) and the alarm limit. The algorithm
provides enable and delay parameters for the alarm you configure.
The following configurable parameters are available:

 ADTYP - Indicates if the alarm detection type is High or Low.
 AENCV - Enables and disables processing for the alarm condition. The default value is
Enabled (1).
When AENCV is 0 (alarm detection is disabled):
 AACT is immediately forced to 0 (Inactive)
 No alarm condition detection occurs.
 ADLON - Delays the time it takes for AACT to be set to Active (1) after the alarm condition is
detected. If the alarm condition clears before the delay time is reached, the AACT parameter
remains Inactive (0) and the timer is reset. The timer resets every time the alarm condition
clears.
 ADLOF - Delays the time it takes for AACT to be set to Inactive (0) after the alarm condition
clears. If the alarm condition reoccurs before the delay time is reached, the AACT parameter
remains Active (1) and the timer is reset. The timer resets every time the alarm condition is
detected.
 AENDL - The time before alarm condition processing begins immediately after the alarm is
enabled (AENCV becomes True). The AACT parameter is forced to 0 for the time specified.
The timer resets whenever AENCV goes from Disabled (0) to Enabled (1).
 AHYS - Used as a deadband when resetting alarm conditions for analog values.
OW351_R1100 723
8.3 LSALM
Quality Handling
The algorithm does not support quality. Alarm detection is performed regardless of the quality of
the input.
FI E L D RE C O R D
IN R1 - Real Variable Required - Monitored Input LA

AACT X1 - Byte Variable Required - Alarm activation state. LD
The choices are:
0 - Inactive
1 - Active
ATMR R2 - Real Variable Required - Alarm Delay Timer LA
ADTYP X2 - Byte Tunable Required 1 Alarm Detection Type -
0=Low
1=High
ALIM R3 - Real Tunable Required 0 Alarm Condition Limit -
AENCV X3 - Byte Tunable Required 1 Enable Alarm: Activate -
Bit 0 0=No
1=Yes
ADLOF R4 - Real Tunable Required 0 Alarm Delay Off -
ADLON R5 - Real Tunable Required 0 Alarm Delay On -
AENDL R6 - Real Tunable Required 0 Alarm Enable Delay -
AHYS R7 - Real Tunable Required 0.5 Alarm Hysteresis -
TPSC R8 - Real Tunable Required 100 Input Scale: Top -
BTSC R9 - Real Tunable Required 0 Input Scale: Bottom -
SCDML X5 - Byte Tunable Required 1 Input Scale: Decimal -
Place
724 OW351_R1100
8.4 LSAND
8.4 LSAND
Description
The Logic Solver AND (LSAND) algorithm generates a digital output value based on the logical
AND of 2 to 16 digital inputs. The algorithm supports signal quality propagation.
IN1 through INx are the digital input values and quality (as many as 16 inputs).
OUT is the digital output value and quality.
Functional Symbol
Algorithm Execution
The number of inputs to the LSAND algorithm is an extensible parameter. The algorithm default i s
two inputs. Use the Control Builder (see Ovation Control Builder User Guide) to add additional
input pins.
The LSAND algorithm examines the inputs you define and applies the logical AND function to the
inputs. When all inputs are True (1), the output is True. When one or more of the inputs is False
(0), the output is False.
Quality Handling
The output quality is set to the worst quality among the selected inputs unless at least one input is
False and its quality is not Bad. When this is the case, the out put quality is set to Good.
FI E L D RE C O R D
-- Number of Inputs
NOFIN Y0 - Byte Required 2 (automatically incremented -
by system)
IN1 - Variable Required - Input 1 LD
IN2 - Variable Required - Input 2 LD
IN3 - Variable Optional - Input 3 LD
OW351_R1100 725
8.4 LSAND
FI E L D RE C O R D

OUT - Variable Required - Output LD
726 OW351_R1100
8.5 LSAVTR
8.5 LSAVTR
Description
The Logic Solver Analog Voter (LSAVTR) algorithm provides an analog voter function for safety
instrumented functions. A voter algorithm monitors a number of input values and determines if
there are enough votes to trip. The LSAVTR algorithm monitors as many as 16 analog inputs. If a
configured number of the inputs vote to trip, the algorithm trips and sets the output of the
algorithm to 0 (zero).
For example, a process shutdown might be required if a tank exceeds a certain temperature.
Three temperature sensors are installed in the tank and an analog voter algorithm is configured to
monitor the sensors and trip if two of the three transmitters detect a high temperature.
Because the Logic Solver is a De-energize to Trip system, the normal operating value of the
output is 1 (On) and the tripped value is 0 (Off).
Functional Symbol
Algorithm Execution
The LSAVTR algorithm has one or more floating-point inputs with quality and one digital output
with quality. The algorithm compares each input to a common configured trip limit to determine
whether that input is a vote to trip the output (change it from the normal operating value to the
tripped value). The inputs are typically the engineering unit values from multiple field transmitters
measuring the same process value.
Basic Algorithm Operation
Voting in the Analog Voter algorithm is an M out of N function or "MooN". That is, M inputs of the
total N inputs must vote to trip. For example, the algorithm can be configured as a 2 out of 3 voter
(2oo3), where two of the three inputs must exceed the trip limit before the output is tripped. The
output of the algorithm is typically connected to an LSCEM (Cause and Effect Matrix) algorithm,
which interprets the value as either a safe or dangerous process state.
The LSAVTR algorithm has three inputs by default. The number of inputs is extensible from 1 to
16. The M value corresponds to the parameter N2TRP (Votes needed to trip, default value is 2).
Common voting schemes include 2 out of 3 (2oo3), 1 out of 2 (1oo2), and 2 out of 2 (2oo2). Other
features of the algorithm make it useful for single transmitter applications as a 1oo1 voter.
To determine whether an input is a vote to trip, the value is compared to the limit value (TRLIM -
Voted-to-Trip Limit Value). The configuration parameter DTYPE (Input Detection Type)
determines whether the comparison is Greater Than (high limit) or Less Than (low limit).
OW351_R1100 727
8.5 LSAVTR
In addition to trip limit detection, the algorithm also compares the inputs to a common PTLIM (Pre-
Trip Limit Value) and applies voting to determine a pre-tripped condition. Pre-trip voting is typically
used as a pre-alarm condition, but it is possible to expose the POUT parameter as an algorithm
output so that a single voter algorithm can initiate trip demand logic for two different trip points.
A vote to trip must remain a vote to trip for a configured time (TRDLY - Trip Delay) before the
output changes to tripped. When the vote to trip clears, it must remain clear for NDLY (Output
Reset Delay) before the output changes to the normal state. The delays apply to both the OUT
and POUT (Output of Pre-Trip Vote) outputs. The default value for both delays is 0.0 seconds.
The TRSTS (Trip Status Indicator) and PSTAT (Pre-Trip/Startup Inhibit Status) parameters
indicate the state of the vote to trip.
For example, the possible values for TRSTS are:

 Normal - the conditions for tripping are not fulfilled.
 Tripped -- the conditions for tripping are fulfilled.
 Voted to Trip, Delayed -- transition of TRSTS can be delayed when this parameter is a non-
zero number and a transition is occurring between the tripped state.
 Voted Normal, Delayed -- transition of TRSTS can be delayed when this parameter is a non-
zero number and a transition is occurring between the normal state.
 Trip Inhibited (when applicable) -- occurs whenever a startup bypass is active or when it is
not possible to trip because there are not enough inputs participating in voting. The latter case
can occur when inputs are bypassed or when inputs have bad quality and the selected
STATUS_OPT option is Trip inhibited.
Startup and Maintenance Bypass Options
It is often necessary to force a voter algorithm's output to remain at the Normal value during plant
startup to prevent a trip caused by inputs that have not stabilized at their normal operating values.
You may also want to bypass inputs to allow for sensor maintenance. By default, you can bypass
only one input of the algorithm at a time. The bypassed input cannot vote to trip.
The following sections explain how to use the BOPx options to implement startup and
maintenance bypasses.
Bypassing Inputs
If you have voter algorithms with 1 out of 2 (1oo2)) or 1 out of 1 (1oo1) voting schemes you may
want the ability to bypass inputs to allow for maintenance. Voters that require multiple votes to trip
can benefit from bypass functions as well, resulting in more predictable behavior during
transmitter maintenance. Default algorithm behavior requires that BPERM (Permit Input Bypass)
be true to bypass inputs. You can configure BPERM to be set by a display button or physical
switch (digital input to the Control module).
If your application does not require permission before inputs can be bypassed, you can select the
BOPTx option "Bypass Opt: PermitNotReq" (Bypass permit is not required to bypass).
Reducing the Number to Trip
By default, an algorithm configured as an M out of N voter becomes an M out of (N-1) algorithm (a

2 out of 3 voter becomes a 2 out of 2 voter) when an input is bypassed because the bypassed
input cannot vote to trip. Selecting the BOPTx option "Bypass Opt: MaintBypRed" (A maintenance
bypass reduces the number to trip) causes an M out of N voter to become an (M -1) out of (N-1)
voter (reduces the number required to trip by one when an input is bypassed).
728 OW351_R1100
8.5 LSAVTR
The following table shows the effect the BOPTx option "Bypass Opt: MaintBypRed" has on the
actual number to trip (ANTRP) for several voting schemes. Note that in no case is ANTRP less
than one.
BOPTx effect on ANTRP
CO N F I G U R E D BOPT X O P TI O N - A MAI N TE N AN C E B YP AS S R E D U C E S TH E N U MB E R TO
V O TI N G S C H E ME TR I P .
T H E O P TI O N I S N O T S E L E C TE D . T H E O P TI O N I S S E L E C TE D .
(U S E S C O N F I G U R E D N2 TRP) (RE D U C E S ANTRP)
2 out of 3 2 out of 2 1 out of 2

2 out of 2 Trip Inhibited 1 out of 1
1 out of 1 Trip Inhibited Trip Inhibited
Allowing Multiple Bypasses
If your application requires, you can enable bypassing multiple inputs simultaneously by selecting
the BOPTx option "Bypass Opt: MulBypAllowed" (Multiple maintenance bypasses are allowed).
If multiple bypasses are set, deselecting the BOPTx option "Bypass Opt: MulBypAllowed"
prevents further bypasses being set but existing bypasses remain set. Additional bypasses
cannot be set until all existing bypasses are cleared.
Maintenance Bypass Timeout
You can configure a maintenance bypass to be active for a finite time using BTOUT (Input Bypass
Reset Timeout). Its default value is 0.0 seconds, which means no timeout is applied (maintenance
bypasses remain active until BYPx (Voting Bypass for Input x) parameters become False, either
by changing True BYPx parameters to False or changing BPERM to False).
When BTOUT is non-zero, BTMR (Bypass Countdown Timer) is preset to BTOUT seconds when
the first BYPx parameter becomes True (not when BPERM becomes True). Each module scan
thereafter BTMR is decremented until it times out (unless all BYP x parameters become False, in
which case the algorithm resets BTMR to 0.0). The smallest possible configured time for BTOUT
parameter is 0.05 seconds. This value must be multiple of 0.05 seconds or it will be rounded off to
its nearest multiple.
BTMR is common to all inputs. The value of BTMR does not change when a second BYP x
parameter is changed to True (if multiple bypasses are allowed). When BTMR times out, the
algorithm default behavior changes all True BYPx parameters to False. If you use bypass
timeouts, do not expose BYPx parameters as algorithm inputs and connect to them. Doing so will
prevent the algorithm from removing bypasses upon timeout.
Optionally, you can use the bypass timer for indication only by selecting the BOP x option
"Maintenance bypass timeout is for indication only." This causes the timeout of BTMR to activate
a notification alarm (AALRT Expiration Reminder), but does not undo bypasses.
OW351_R1100 729
8.5 LSAVTR
Bypass Timeout Reminder
You can configure the algorithm to remind operators that a bypass timeout is imminent. By
default, the algorithm does not notify. There are two ways you can cause a notification:
 For bypasses with a configured timeout, you can cause notific ation in advance of the timeout
by setting RMTIM (Reminder Alarm Duration) to a non-zero value. When BTMR is non-zero
but less than or equal to RMTIM, the alarm condition (AALRT Expiration Reminder) is active.
The bypass timer is re-armed only after the first bypass. However, BTMR is a writeable
parameter. After notification that a timeout is about to happen, BTMR can be incremented
using a display button or some other suitable technique to extend the time.
 A second approach is available when you are using the bypass timeout for indication only,
that is, bypasses are not removed when BTMR expires (the BOPx option "Maintenance
bypass timeout is for indication only" is selected). In this case the reminder alarm condition
becomes active when BTMR times out even if RMTIM is 0.0. If RMTIM is non-zero, the
reminder occurs prior to timeout. If BTMR times out, the reminder is active and remains active
until all bypasses have been removed.
The following table describes the behavior of the bypass timeout and reminder function for three
different configuration setups.
Bypass timeout behavior
C O N D I TI O N BTOUT AN D BOP X C O N F I G U R ATI O N
BTOUT = 0 .0 BTOUT > 0 .0 AN D BTOUT > 0 .0 AN D

( N O TI ME O U T ) BOP X O P TI O N BOP X O P TI O N
" M AI N TE N AN C E B YP AS S " M AI N TE N AN C E B YP AS S
TI ME O U T I S F O R TI ME O U T I S F O R
I N D I C ATI O N O N L Y" I S I N D I C ATI O N O N L Y" I S
N O T S E L E C TE D S E L E C TE D
(BYP X R E MO V E D O N ( TI ME O U T F OR
TI ME O U T ) I N D I C ATI O N O N L Y)
BPERM changes to BTMR stays 0.0 BTMR stays 0.0 BTMR stays 0.0
True.
First input is bypassed BTMR stays 0.0 BTMR = BTOUT seconds BTMR = BTOUT seconds
(BYPx changes to True) and begins timing down. and begins timing down.
Second input is BTMR stays 0.0 BTMR continues timing BTMR continues timing
bypassed (assuming the down. down.
BOPx option "Multiple
maintenance bypasses
are allowed" is
selected).
BTMR > RMTIM N/A No reminder No reminder
BTMR <= RMTIM No reminder Reminder alarm condition is Reminder alarm condition
active. is active.
Bypass timer times out N/A The algorithm changes all Reminder alarm condition
BYPx parameters to False. remains active until all
Reminder alarm condition bypasses are removed
clears on the following manually.
scan.
730 OW351_R1100
8.5 LSAVTR
Startup Bypass Trip Inhibit
This startup bypass allows the process to reach normal operating conditions without tripping. Use
the STUP (Inhibit Startup Trip Detection) parameter and associated parameters for startup
bypasses. Do not use maintenance overrides for this purpose.
Timed Startup Bypass (the BOPx option Startup bypass duration is event-based is not
selected)
On a rising edge of the STUP parameter the algorithm forces OUT and POUT to the normal state
value for a configurable length of time defined by SUTM (Startup Inhibit Duration). When the
countdown timer SUTMR (Startup Inhibit Timer) times out, the algorithm resumes normal trip
detection. The default behavior of the algorithm is such that a subsequent rising edge of STUP
does not affect the startup time while SUTMR is timing down. To avoid a pending trip on timeout,
you can allow each rising edge of STUP to re-arm SUTMR (by selecting the BOPx option "Startup
bypass preset is allowed while active").
A reminder becomes available to STUP bypasses by selecting the BOP x option "Reminder
applies to startup bypass." When SUTMR is greater than 0.0 but less than RMTIM, the reminder
alarm condition (AALRT Expiration Reminder) is active. The reminder alarm condition is common
to the timeout of maintenance and startup bypasses.
Another option is to have the startup timer expire when inputs have stabilized, that is, when there
have not been enough votes to trip for a configurable period of time. When the BOPx option
"Startup bypass expires upon stabilization" is selected, the bypass timer expires when the
process stabilizes. While SUTMR is timing down, STMR times out whenever there are not enough
votes to trip and resets whenever the trip votes equal or exceed the number required to trip.
If STMR reaches the configured STM, SUTMR resets to 0.0 and normal trip detection resumes.
While SUTMR is timing down, the algorithm increments T2STB (Time to Stable) and stops as
soon as the STMR is triggered. T2STB (Time to Stable) indicates the total number of seconds
during the startup bypass until the inputs become and remain stable (assuming SUTM is
sufficiently long).
STMR does not reset at the end of the startup time period, but is reset at the beginning of a
startup and at any time during the startup when there are enough trip votes. T2STB is reset at the
beginning of a startup bypass. STMR and T2STB are processed even when the stabilization
option is not used (the BOPx option "Startup bypass expires upon stabilization" is not selected).
You can use the value of T2STB to optimize the configured SUTM.
Event-Based Startup Bypass (the BOPx option Startup bypass duration is event-based is
selected)
When the startup bypass expires based on an event rather than a fixed time period, select the
BOPx option "Startup bypass duration is event based." This ends the startup bypass when the
parameter STUP becomes False. STMR and T2STB are not processed. They are set to 0.0 when
STUP becomes True.
OW351_R1100 731
8.5 LSAVTR
Bypass Permit Control

You can use the BOPx option "Bypass permit control should be visible in operator interface" to
control the visibility of a button on a graphic representing this algorithm. Operators can use this
button to set the BPERM parameter. Do not select this option if logic in the control module is
writing to BPERM (for example, a keyswitch is used to permit bypassing).
The following table summarizes the BOPx options and their effects.
BOPx parameter options
O P TI O N B E H AV I O R W H E N O P TI O N IS BE H AV I O R W H E N O P TI O N I S SET
S E T TO 1 (T R U E ) TO 0 (FAL S E )
A maintenance bypass An M out of N voter becomes an An M out of N voter becomes an M

reduces the number to trip. (M-1) out of (N-1) voter (number out of (N-1) voter when an input is
(BOP1 - MaintBypRed) required to trip by is reduced by bypassed.
one) when an input is bypassed.
Multiple maintenance You can bypass multiple inputs at Only one input can be bypassed at a
bypasses are allowed. the same time. time.
(BOP2 - MulBypAllowed)
Maintenance bypass When BTMR times out AALRT When BTMR times out, AALRT
timeout is for indication Bypass Active remains set and Bypass Active clears and all
only. input bypasses remain in effect. bypasses are cleared.
(BOP3 - IndicateOnly)
Startup bypass preset is Each time STUP is set to True, SUTMR is not reset.
allowed while active. SUTMR is reset to the configured
(BOP4 - ReArmAllowed) value of SUTM.
Startup bypass expires Startup bypass and SUTMR clear Startup bypass ends when SUTMR
upon stabilization. if STMR reaches STM (after there reaches 0 (zero).
(BOP5 - BypExpires) are not enough votes to trip for the
configured amount of time).
Reminder applies to startup When SUTMR is greater than 0.0 AALRT Expiration Reminder does not
bypass. but less than RMTIM, the AALRT apply to startup bypass.
(BOP6 - ReminderApplies) Expiration Reminder is set. The
reminder alarm condition is
common to maintenance and
startup bypass timeouts.
Startup bypass duration is Startup bypass expires only when Startup bypass is time based.
event-based. STUP becomes False. STMR and
(BOP7 - BypDurEvent) T2STB are not processed.
Bypass permit is not BPERM does not need to be set to BPERM must be set to True for inputs
required to bypass. True for inputs to be bypassed. to be bypassed.
(BOP8 - PermitNotReq)
Bypass permit control Bypass permit controls appear in Bypass permit controls do not appear
should be visible in the standard LSAVTR faceplate. in the standard LSAVTR faceplate.
operator interface. (BOP9 - Do not select this option if the
BypPerVisible) control module logic writes to
BPERM (for example, bypass
permitting is done using a
keyswitch).
732 OW351_R1100
8.5 LSAVTR
Quality Handling
The quality of the inputs influences algorithm behavior based on how the SOPT (Status Options if
Bad input) parameter is configured. The three choices of SOPT are:
 Always Use Value — The value of the input is always used regardless of quality. In this way a
hardware failure does not necessarily cause a shutdown and time is allowed for repair.
Detected hardware failures are indicated by standard alarms on the Logic Solver card. This is
the default option.
 Will Not Vote if Bad — The input value is not counted as a vote to trip if its quality is Bad.
 Vote to Trip if Bad — The input value is counted as a vote to trip if the input quality is Bad.
The following table shows how several common voting schemes degrade when a single input has
bad quality based on the option chosen for SOPT.
Example of voting scheme degradation
O R I G I N AL V O TI N G RE S U L TI N G V O TI N G S C H E ME F OR SOPT V AL U E S
S C H E ME
AL W AYS US E V AL U E 1 W I L L NO T V O TE IF BAD V O TE TO TR I P IF
BAD
2 out of 3 2 out of 3 or 1 out of 2 2 out of 2 1 out of 2

2 out of 2 2 out of 2 or 1 out of 1 Will Not Vote if Bad 1 out of 1
1 out of 2 1 out of 2 or Tripped 1 out of 1 Tripped
1 out of 1 1 out of 1 or Tripped Trip Inhibited Tripped
Note: The degraded voting scheme depends on the value of the input with Bad quality.
The LSAVTR algorithm determines the quality of OUT and POUT in the same way no matter
which quality option is chosen. The quality calculation is completely separate from the value
calculation.
The quality of OUT and POUT is Good if the number of non-bypassed inputs with Good quality is
greater than or equal to ANTRP (Actual Votes Needed to Trip), or all inputs are bypassed;
otherwise, the quality is Bad. Uncertain quality on inputs is treated as Good.
When any input has Bad quality, the AALRT Input Bad becomes active.
TRSTS and PSTAT Indication
The TRSTS parameter indicates the state of the trip vote functions. The typical value for TRSTS
is Normal, and less commonly, Tripped. As shown in the following figure, TRSTS can be delayed
when TRDLY or NDLY is non-zero and a transition is occurring between normal and tripped
states.
A fifth state, Trip Inhibited, occurs whenever a startup bypass is active or when it is not possible to
trip because there are not enough inputs participating in voting. The latter case can occur when
inputs are bypassed or when inputs have bad quality and the selected SOPT option is Trip
inhibited.
OW351_R1100 733
8.5 LSAVTR
The solid lines in the figure show the common state transitions of TRSTS expected as the
process value moves above and below the trip point. The dashed lines show less common state
transitions.
Figure 24: State diagram for TRSTS
FI E L D RE C O R D
AUX1 G3 - SID Data Init. Required - Auxiliary record 1 LC

NOFIN Y0 - Byte -- Required 1 Number of Inputs -
(automatically
incremented by
system).
IN1 R1 - Real Variable Required - Input 1 LA
IN2 R2 - Real Variable Optional - Input 2 LA
734 OW351_R1100
8.5 LSAVTR
FI E L D RE C O R D
IN10 S1 - Real Variable Optional - Input 10 LA
OUT X1 - Byte Variable Required - Output LD
PVN1 G4 - Integer Variable Optional - Pre-Trip Check LD

Bit 0 Status Input 1
OW351_R1100 735
8.5 LSAVTR
FI E L D RE C O R D

PVOT X6 - Byte Variable Optional - Num of Inputs LA
Voted to Pre-Trip
PDTMR AUX1:R1 - Variable Optional - Countdown Timer LA
Real for Pre-Delay
POUT X7 - Byte Variable Optional - Output of Pre-Trip LD
Vote
PSTAT X8 - Byte Variable Optional - Pre-Trip/Startup LA
Inhibit Status
TVN1 G5 - Integer Variable Optional - Voted-to-Trip LD
736 OW351_R1100
8.5 LSAVTR
FI E L D RE C O R D
TRPVT X9 - Byte Variable Optional - Number of Inputs LA

Voted-to-Trip
TRSTS Y2 - Byte Variable Optional - Trip Status LA
Indicator. The
choices are:
 0 = Normal
 1 = Tripped
 2 = Trip inhibited
 3 = Voted to
Trip, Delayed
 Voted Normal,
Delayed
See explanation
given above.
T2STB AUX1:R2 - Variable Optional - Time to Stable in LA
Real seconds.
SUTMR AUX1:R3 - Variable Optional - Startup Inhibit LA
Real Timer in seconds.
STMR AUX: R4 - Variable Optional - Startup No-Vote- LA
Real to-Trip Timer in
seconds.
OUTNB Y4 - Byte Variable Optional - Output with No LD
Bypass
DLYTM AUX1:R5 - Variable Optional - Countdown Timer LA
Real for Delay in
seconds.
BTMRH AUX1:R6 - Variable Optional - Bypass LA
Real Countdown Timer
(hrs)
AALRT G6 - Integer Variable Optional - Alarms Conditions LX
Set by algorithm
ANTRP Y3 - Byte Variable Optional - Actual Votes LA
Needed to Trip
BYP1 C0 - Integer Selectable Optional 0 Voting Bypass for -
Input 1
0=No, 1=Yes
Input 2
0=No, 1=Yes
Input 3
0=No, 1=Yes
Input 4
0=No, 1=Yes
OW351_R1100 737
8.5 LSAVTR
FI E L D RE C O R D

Input 5
0=No, 1=Yes
Input 6
0=No, 1=Yes
Input 7
0=No, 1=Yes
Input 8
0=No, 1=Yes
Input 9
0=No, 1=Yes
BYP10 YT - Integer Selectable Optional 0 Voting Bypass for -
Input 10
0=No, 1=Yes
BYP11 D0 - Integer Selectable Optional 0 Voting Bypass for -
Input 11
0=No, 1=Yes
BYP12 YQ - Integer Selectable Optional 0 Voting Bypass for -
Input 12
0=No, 1=Yes
Input 13
0=No, 1=Yes
BYP14 YP - Integer Selectable Optional 0 Voting Bypass for -
Input 14
0=No, 1=Yes
Input 15
0=No, 1=Yes
Input 16
0=No, 1=Yes
BOP1 G0 - Integer Tunable Required 0 Bypass Opt: -
Bit 0 MaintBypRed
0=False, 1=True
Bit 1 MulBypAllowed
0=False, 1=True
Bit 2 IndicateOnly
0=False, 1=True
Bit 3 ReArmAllowed
0=False, 1=True
738 OW351_R1100
8.5 LSAVTR
FI E L D RE C O R D

Bit 4 BypExpires
0=False
1=True
Bit 5 ReminderApplies
0=False, 1=True
Bit 6 BypDurEvent
0=False, 1=True
Bit 7 PermitNotReq
0=False, 1=True
Bit 8 BypPerVisible
0=False, 1=True
BPERM X2 - Byte Tunable Required 0 Permit Input -
Bypass
0=No, 1=Yes
BTOUT S8 - Real Tunable Required 0.0 Input Bypass -
Reset Timeout
(sec)
BTMR S9 - Real Alg Init Required 0.0 Bypass -
Countdown Timer
(sec)
DTYPE X3 - Byte Tunable Required 1 Input Detection -
Type
1=GreaterThan
2=LessThan
DVHYS T1 - Real Tunable Required 0 Input Range Limit -
Deadband
DVLIM T2 - Real Tunable Required 0 Input Value Range -
Limit
TPSC T3 - Real Tunable Required 100 Input Scale: Top -
BTSC T4 - Real Tunable Required 0.0 Input Scale: -

Bottom
SCDML Y5 - Byte Tunable Required 1 Input Scale: -
Decimal Places
NDLY T5 - Real Tunable Required 0 Output Reset -
Delay (sec)
N2TRP X4 - Byte Tunable Required 2 Votes Needed to -
Trip
PTLIM T6 - Real Tunable Required 80 Pre-Trip Limit -
Value
RMTIM T7 - Real Tunable Required 0 Reminder Alarm -
Duration (sec)
OW351_R1100 739
8.5 LSAVTR
FI E L D RE C O R D
ROP1 G1 - Integer Tunable Required 0 Report Opt: -

Bit 0 NoRollUp
0=False
1=True
Bit 1 NoEventRecords
0=False
1=True
STM T8 - Real Tunable Required 0 Process -
Stabilization Time
(sec)
STUP X5 - Byte Tunable Required 0 Inhibit Startup Trip -
Detection
0=No
1=Yes
SUTM T9 - Real Tunable Required 0 Startup Inhibit -
Duration (sec)
SOPT G2 - Integer Tunable Required 0 Status Options if -
Bad Input
0=Always Use
Value
1=Will Not Vote if
Bad
2=Vote to Trip if
Bad
TRDLY U1 - Real Tunable Required 0 Trip Delay (sec) -
TRHYS U2 - Real Tunable Required 0.5 Trip Limit -

Deadband
TRLIM U3 - Real Tunable Required 90 Voted-to-Trip Limit -
Value
DI1 - Data Init. Optional VOTER1 Description of -
Voter 1.
For Control
Builder/Signal
Diagram
application use
only.
Voter 2.
For Control
Builder/Signal
Diagram
application use
only.
740 OW351_R1100
8.5 LSAVTR
FI E L D RE C O R D

Voter 3.
For Control
Builder/Signal
Diagram
application use
only.
Voter 4.
For Control
Builder/Signal
Diagram
application use
only.
Voter 5.
For Control
Builder/Signal
Diagram
application use
only.
Voter 6.
For Control
Builder/Signal
Diagram
application use
only.
Voter 7.
For Control
Builder/Signal
Diagram
application use
only.
Voter 8.
For Control
Builder/Signal
Diagram
application use
only.
Voter 9.
For Control
Builder/Signal
Diagram
application use
only.
OW351_R1100 741
8.5 LSAVTR
FI E L D RE C O R D

Voter 10.
For Control
Builder/Signal
Diagram
application use
only.
Voter 11.
For Control
Builder/Signal
Diagram
application use
only.
Voter 12.
For Control
Builder/Signal
Diagram
application use
only.
Voter 13.
For Control
Builder/Signal
Diagram
application use
only.
Voter 14.
For Control
Builder/Signal
Diagram
application use
only.
Voter 15.
For Control
Builder/Signal
Diagram
application use
only.
Voter 16.
For Control
Builder/Signal
Diagram
application use
only.
742 OW351_R1100
8.5 LSAVTR
AALRT
The following table shows the alerts that can appear for an LSAVTR algorithm, an explanation of
each alert and its bit position.
The alerts listed below will be sent to the Ovation Process Historian as SIF Alerts. For more
information on SIF Alerts, refer to Ovation Safety Instrumented System (SIS) User Guide.
LSAVTR alerts
B I T V AL U E EX P L AN A TI O N BI T P O S I TI O N
Trip Active Inactive when OUT is in the normal operating state, 0

active when OUT is in the trip state.
Pre-Trip Active Inactive when POUTD is in the normal operating state, 1
active when POUT is in the trip state.
Bypass Active Active when there is a maintenance bypass on any input 2
(any BYPx parameter is True).
Startup Override Active whenever the startup bypass is active. 3
Active
Deviation Limit Active when the difference between the highest and 4
Exceeded lowest non-bypassed INn value exceeds DVLIM. Forced
inactive when DVLIM is 0.0.
Expiration Reminder Active when either a maintenance bypass or a startup 5
bypass is about to expire.
Bypassed Input Active if one or more bypassed inputs have exceeded the 6
Pre-Tripped pre-trip limit.
Bypassed Input Active if one or more bypassed inputs have exceeded the 7
Tripped trip limit.
Input Bad Active if any input has bad quality. 8
OW351_R1100 743
8.6 LSBDE
8.6 LSBDE
Description
The LSBDE algorithm generates a True (1) digital output when the digital input makes a positive
(False-to-True) or a negative (True-to-False) transition since the last execution of the algorithm. If
there has been no transition, the digital output of the algorithm is False (0).
The LSBDE algorithm supports signal quality propagation.
IN is the digital input signal and quality.
OUT is the digital output signal and quality.
Functional Symbol
Algorithm Execution
The Bi-directional Edge Trigger algorithm examines the input value, compares it to the previous
input value, and sets the output True for one scan period when the input has changed. Otherwise,
the output is False. The quality of the output value is set to the quality of the input value.
The following figure illustrates how the Bi-directional Edge Trigger algorithm responds to a
change in input:
Figure 25: LSBDE algorithm execution example
744 OW351_R1100
8.6 LSBDE
Quality Handling
The output quality is set to the input quality.
FI E L D RE C O R D
IN X1 - Byte Variable Required - Input LD

OW351_R1100 745
8.7 LSBFI
8.7 LSBFI
Description
The Logic Solver Boolean Fan Input (LSBFI) algorithm generates a digital output based on the
weighted binary sum, binary coded decimal (BCD) representation, transition state, or logical OR
of one to 16 digital inputs. The algorithm supports signal quality propagation.
RST (Reset First Weighted Output) is the input that, when True (1), clears FOUT (First Binary
Weighted Output) and activates the trap condition after all the inputs go False.
OUTI is the unsigned 32-bit binary weighted output value that represents the bit combination of
the inputs (INx).
OUT is the output value that represents the logical OR of the inputs (INx).
FOUT is the binary weighted output of the digital input values when one or more inputs is set after
RST is set.
Functional Symbol
Algorithm Execution
The Boolean Fan Input algorithm examines the digital input values at each algorithm execution.
The OUTI output is set to the sum of the bit values of the True inputs (IN1 is weighted as 1, IN2
as 2, IN3 as 4, IN4 as 8, and so on). The quality of OUTI is set to the worst quality among the
inputs.
When FOUT indicates a trap has not yet occurred (its value is False[0]) and one or more of the
inputs have become True, a trap condition is flagged and held by copying the value of OUTI to
FOUT. Thereafter, the FOUT value updates when the INx values transition from all False (0) to
one or more True (1). The quality of FOUT is equal to the quality of OUTI when the trap occurred.
The value of OUT is the logical OR of the digital inputs. OUT quality is set to the worst quality
among the inputs.
Note: Once the FOUT output is reset, the Boolean Fan Input algorithm does not set it again until
all of the INx values return to the False (0) state.
To support thumbwheel switch interfaces, the Boolean Fan Input algorithm uses a parameter to
store the binary coded decimal (BCD) representation of the digital inputs. The first four digital
inputs are used to construct the BCD ones digit. (Within these first four bits, the first input is the
least-significant bit.) The remaining sets of four inputs indicate the BCD tens, hundreds, and
thousands digits. When the four bits representing a digit are greater than nine, the digit is limited
to nine.
746 OW351_R1100
8.7 LSBFI
The following figure is an example of Boolean Fan Input algorithm execution for OUTI = 5510.
The result is BCD = 1586 and OUT = True.
Figure 26: LSBFI algorithm execution example
Quality Handling
The quality of OUTI and OUT is set to the worst quality among the inputs. The FOUT quality is the
worst quality among the inputs when the FOUT value is written. The FOUT quality is reset when
the FOUT value is cleared.
FI E L D RE C O R D
-- Number of Inputs
(automatically
NOFIN Y0 - Byte Required 2 -
incremented by
system)
Input 1
IN1 G4 Tunable Required 0 0 = No LD
1 = Yes
Input 2
IN2 G5 Tunable Required 0 0 = No LD
1 = Yes
Input 3
IN3 G6 Tunable Optional 0 0 = No LD
1 = Yes
Input 4
1 = Yes
Input 5
1 = Yes
Input 6
1 = Yes
OW351_R1100 747
8.7 LSBFI
FI E L D RE C O R D
Input 7
IN7 B0 Tunable Optional 0 0 = No LD
1 = Yes
Input 8
1 = Yes
Input 9
1 = Yes
Input 10
IN10 YU Tunable Optional 0 0 = No LD
1 = Yes
Input 11
1 = Yes
Input 12
1 = Yes
Input 13
1 = Yes
Input 14
1 = Yes
Input 15
1 = Yes
Input 16
1 = Yes
Variable Reset First Weighted
RST - Required - LD
Output
Variable First Binary Weighted
FOUT - Required - LX
Output
Variable BCD Representation
BCD - Optional - LX
of Inputs
OUT - Variable Optional - Logical Output LD
OUTI - Variable Optional - Binary Weighted LX
Output
ATRAP X1 - Byte Tunable Required 1 Enable First-Out Trap -
0=No, 1=Yes
748 OW351_R1100
8.8 LSBFO
8.8 LSBFO
Description
The Logic Solver Boolean Fan Output (LSBFO) algorithm decodes a binary weighted input to
individual bits and generates a digital output value for each bit. The algorithm supports signal
quality propagation.
IN is the unsigned 32-bit binary weighted input value and quality.
OUT1 through OUTx are the digital output values and quality (as many as 16 outputs) that
represent the bit of the input.
Functional Symbol
Algorithm Execution
The number of outputs to the LSBFO algorithm is an extensible parameter. The algorithm default
is two outputs. Use the Control Builder (see Ovation Control Builder User Guide) to add additional
output pins.
The LSBFO algorithm treats the unsigned 32-bit input as a binary weighted value. The individual
bits that comprise this value are translated to the algorithm's digital outputs.
The first digital output represents the least-significant bit of the translated input value. The second
digital output is the next least-significant bit, and so on. The quality of the input (IN) is passed to
the quality of the digital outputs (OUTx).
The following is an example of Boolean Fan Output algorithm execution for IN = 5153.
OW351_R1100 749
8.8 LSBFO
Quality Handling
The quality of the algorithm outputs (OUTx) is set equal to the quality of the algorithm input (IN).
FI E L D RE C O R D
NOFOT Y0 - Byte Data Init Required 2 Number of Outputs -

G0 - Variable Binary Weighted
IN Required - LX
Integer Input
G1 - Variable
OUT1 Integer Optional - Output 1 LD
Bit 0
G1 - Variable
Bit 1
G1 - Variable
Bit 2
G1 - Variable
Bit 3
G1 - Variable
Bit 4
G1 - Variable
Bit 5
G1 - Variable
Bit 6
G1 - Variable
Bit 7
G1 - Variable
Bit 8
G1 - Variable
Bit 9
G1 - Variable
Bit 10
750 OW351_R1100
8.8 LSBFO
FI E L D RE C O R D
G1 - Variable
Bit 11
G1 - Variable
Bit 12
G1 - Variable
Bit 13
G1 - Variable
Bit 14
G1 - Variable
Bit 15
OW351_R1100 751
8.9 LSCALC
8.9 LSCALC
Description
The Logic Solver Calculation (LSCALC) algorithm evaluates an expression you define to
determine the algorithm's outputs. You can use mathematical functions, logical operators,
constants, and input and output references of the LSCALC algorithm in the expression.
IN1 through INx are the inputs to the algorithm (as many as 16 inputs).
OUT1 through OUTx are the algorithm outputs (as many as 16 outputs).
Functional Symbol
Algorithm Execution
The LSCALC algorithm uses as many as 16 inputs and 16 outputs to evaluate its contained
expression. In addition, the expression evaluator uses constants and input and output parameter
references of the LSCALC algorithm that you specify to evaluate the expression. External
references from LSCALC algorithm expressions and algorithm parameters, SIF errors, and SIF
alerts are not allowed. The calculated values are assigned to algorithm outputs for use as
parameters or inputs to the control strategy in other algorithms.
Expressions
Expressions are structured text in a specific syntax and are made up of operands, operators,
functions, constants, and keywords. You can write expressions using the LSCALC editor window
(refer, Ovation Control Builder User Guide).
Note: The values of temporary variables in expressions are not preserved on load or restored
on reboot. Temporary variables start with a value of 0 (zero) on the first scan after a load or
reboot.
Quality Handling
The algorithm's outputs are initialized to Bad. You must explicitly set the qual ity of outputs by
writing to the .ST field of an OUTx parameter. The .ST field is not automatically written when the
.CV field of an OUTx parameter is written.
If the LSCALC algorithm executes a divide by zero expression, the only effect is that quality of the
output is set to BAD.
752 OW351_R1100
8.9 LSCALC
FI E L D RE C O R D
AUX1 G1 - SID Data Init Required - Auxiliary record 1 LC

NOFIN X1 - Byte Data Init. Required 1 Number of Inputs -
(automatically
incremented by system)
NOFOT Y0 - Byte Data Init Required 1 Number of Outputs -
CRC G1 - Data Init Optional 0 Program Checksum -
Integer
LCKD - Data Init. Required 0 Program Edits: -
0 = Unlocked
1 = Locked
NOANL - Data Init. Required 0 Number of analog -
constants
AC01 - Data Init. Required 0.000000 Analog Constant 1 -
$(AC1)
$(AC2)
$(AC3)
$(AC4)
$(AC5)
$(AC6)
$(AC7)
$(AC8)
$(AC9)
$(AC10)
$(AC11)
$(AC12)
$(AC13)
$(AC14)
$(AC15)
OW351_R1100 753
8.9 LSCALC
FI E L D RE C O R D

$(AC16)
NODIG - Data Init. Required 0 Number of digital -
constants
DC01 - Data Init. Required 0 Digital Constant 1 -
$(DC1)
0 = False
1 = True
$(DC2)
0 = False
1 = True
$(DC3)
0 = False
1 = True
$(DC4)
0 = False
1 = True
$(DC5)
0 = False
1 = True
$(DC6)
0 = False
1 = True
$(DC7)
0 = False
1 = True
$(DC8)
0 = False
1 = True
$(DC9)
0 = False
1 = True
$(DC10)
0 = False
1 = True
$(DC11)
0 = False
1 = True
754 OW351_R1100
8.9 LSCALC
FI E L D RE C O R D

$(DC12)
0 = False
1 = True
$(DC13)
0 = False
1 = True
$(DC14)
0 = False
1 = True
$(DC15)
0 = False
1 = True
$(DC16)
0 = False
1 = True
IN1 R1 - Real Variable Optional - Input 1 LX
IN10 S1 - Real Variable Optional - Input 9 LX
OUT1 AUX1:R1 - Variable Required - Output 1 LX
Real
OUT2 AUX1:R2 - Variable Optional - Output 2 LX
Real
Real
OW351_R1100 755
8.9 LSCALC
FI E L D RE C O R D

Real
Real
Real
Real
Real
Real
OUT10 AUX1:S1 - Variable Optional - Output 10 LX
Real
Real
Real
Real
Real
Real
Real
BLERR G0 - Variable Optional - Block Error Status LX
Integer 64 = Memory Failure
(6th Bit)
128 = Output Failure
(7th Bit)
16384 = Configuration
Error (14 th Bit)
756 OW351_R1100
8.9 LSCALC
8.9.1 LSCALC Expre ssion Editor
Description
The Logic Solver is capable of executing Structured Text Language expressions. Expressions
represent calculations and have a specific syntax. Expressions for the Logic Solver are created in
the Logic Solver Calculation (LSCALC) algorithm. To facilitate the writing of expressions, use the
Expression Editor. For specific help on using the Expression Editor, select the Help button in the
Expression Editor window.
CAUTION! When writing expressions using an external editor, only use a plain ASCII
text editor (Notepad is recommended). Using other editors can cause the expression to
change during the load and save process.
The following functions and features are not supported in expressions in the Logic Solver:
 References to I/O DSTs.
 References to external parameters (outside the module containing the LSCALC algorithm).
 References to algorithm parameters.
 Writing to an OUT parameter of another LSCALC algorithm.
 Reading or writing .CST and .AWST fields for any parameter.
 String functions.
 Array declarations.
 Looping constructs:
 While-Do-End_While
 Goto
 Label
 Exit
OW351_R1100 757
8.9 LSCALC
Syntax Rules for Expressions in the Logic Solver
An expression is comprised of operands, constants, operators, functions, and comments. Each

expression must follow a specific syntax to be valid. The Expression Editor validates the
expression when parsing.
The Option Explicit behavior is enforced even if the statement is not present in the expression,
requiring declaration of temporary variables.
References (LSCALC algorithm Inputs, Outputs)
The Logic Solver subset of expressions supports only references to the inputs and outputs of the
Logic Solver Calc algorithm. External and dynamic references are not supported.
If you do not specify the field, CV is assumed.
Notes:
 INx and OUTx parameters do not require quotes.

 If you do not specify the field, CV is assumed.
Statements for Expressions in the Logic Solver
The following statement types are allowed in Logic Solver Calc expressions. Statements are
separated by semicolons.
Statement types
S TATE M E N T T YP E EX AM P L E S
Assignment OUT1 := ABS(IN1);

If Then Else IF IN1 = 1 THEN
OUT1 := 1;
ELSE
OUT1 := 0;
ENDIF;
Explicit declaration of temporary Option Explicit; (* optional *)
variables using VAR...END_VAR
VAR
TEMP1;
TEMP2;
END_VAR;
Comment (* *) (* some comment *)
Comment (REM) REM some comment
758 OW351_R1100
8.9 LSCALC
Assignment Statements
The assignment (:=) statement allows the assignment of an expression to a reference, a

temporary variable, or an output to locations inside and outside of the current algorithm.
Syntax:
'referen ce' := expression;

(* only references to 'OUTx' are possible *)
or
tempvar := expression;
or
OUTn := expres sion;
The assignment (:=) statement syntax has these parts:
Description
P AR T D E S C R I P TI O N
Reference One of the following is required: reference, tempvar, or

or output.
tempvar
or
output
Expression Required. Any valid expression.
If...Then...Else...End_If
The IF-THEN-ELSE-END_IF structure allows you to execute conditional code in expressions.

When an algorithm tests a condition that evaluates to TRUE, it executes the set of statements
after THEN. If the condition evaluates to FALSE, it executes the set of statements after ELSE. If
the condition evaluates to FALSE, and there is no ELSE, then the IF-THEN-ELSE-END_IF
structure takes no action.
Syntax:
If condition Then [statements]
[Else [elsestatements]]
End_If
OW351_R1100 759
8.9 LSCALC
The IF-THEN-ELSE-END_IF statement syntax has the following parts:
Description
Condition Required. An expression that evaluates to True or False.

Statements Required. One or more statements separated by semi-colons; executed if
condition is True.
Elsestatements Optional -- but required if the keyword ELSE is used. One or more statements
separated by semi-colons; executed if the condition is False.
Note: The Structured Text Language requires the use of END_IF (with underscore). However,
the Ovation software allows you to use either END_IF or ENDIF.
Using Variables in Expressions for Logic Solvers
You can simplify complex calculations by using variables to temporarily store values. All variables
are floating point numbers. The value of the variable is retained from one scan to t he next. The
initial (first scan) value of a variable is zero. The scope/visibility of variables is limited to the Logic
Solver Calc algorithm in which they exist.
Declaring Variables
You must declare variables used in the Logic Solver, because the Option Explicit statement is
implied. Option Explicit enables checking to ensure that a variable has been created in a
VAR...END_VAR statement before it is used in an expression. Variable names must start with a
letter or underscore. Variable names can contain only letters (A-Z, a-z), numbers (0-9), and
underscores ( _ ) and are not case sensitive.
Note: Some k eywords are reserved for Ovation expressions and cannot be used as local
variable names.
Syntax:
Option Explicit; (* optional *)

VAR
[identifers]
END_VAR;
The VAR...END_VAR statement syntax has these parts:
Description
Identifiers Required. One or more names of temporary variables separated by semi -

colons.
760 OW351_R1100
8.9 LSCALC
Operands
Operands can be any of the following:

 Constants - an unchangeable value.
 Inputs - references to Logic Solver Calc (LSCALC) algorithm inputs (IN1..IN16, float with
status).
 Outputs - references to Logic Solver Calc (LSCALC) algorithm outputs (OUT1..OUT16, float
with status).
 Temporary variables.
Constants
Constants are predefined, unchangeable values represented by keywords in expressions.

Constants let you test values against system values without having to know their internal
representations. These constants can be used as numerical values only. Never use keywords as
temporary variables in Logic Solver Calc algorithms.
The Logic Solver Calc algorithm accepts the following constant types:
 Integer.
 Float.
 Named Constants.
 Enumerated Constants.
Named Constants
The following tables list the named constants supported in expressions for the Logic Solver.
These tables are organized into types of named constants for easy reference.
TRUE/FALSE Constants
C O N S TAN T EX P L AN A TI O N
FALSE Boolean FALSE. This is always equivalent to 0.0 whether comparing or assigning.
True Boolean TRUE. If as signing ('item' := TRUE) then 'item' is set to 1.0. If comparing to
TRUE ('item' = TRUE), the statement is TRUE if the value of 'item' is >= 1.0.
Note: Comparing TRUE/FALSE constants in an expression should only be used against

Boolean elements or when the floating point value is either 0.0 (FALSE) or >=1.0 (TRUE).
Status Constants
Status constants are implemented as an 8-bit status word. The numeric value of the status word
is determined by which bits are set.
A Logic Solver Calc algorithm's OUT parameters default to a status of BAD (0). The expression
must explicitly set the status. Status propagation is not automatic in the Logic Solver Calc
algorithms. You can set the status to a numeric value.
OW351_R1100 761
8.9 LSCALC
You can also use the GOOD, BAD or UNC constants (for example, 'out1.st' := UNC). There are
also constants for the limit status (the two least significant bits of the status word). If the signal is
also limited or constant, you can use these additional constant words (LIMITED_CONS TA NT,
LIMITED_HIGH, LIMITED_LOW), but you must combine them with the status constant (GOOD,
BAD, UNC). For example, to set the status to GOOD High Limited, use the expression 'out1.st':=
GOOD | LIMITED_HIGH. The "|" operator is a bitwise OR function. The expression writes a value
of 130 to the status.
Status Constants
C O N S TAN T EX P L AN A TI O N
BAD If assigning BAD to a parameter status, the status is set to BAD NonSpecific
NotLimited (numeric value 0).
When comparing a status to BAD, the expression evaluates to TRUE if the
status is <=63.
GOOD If assigning GOOD to a parameter's status, the status is set to
GoodNonCascade NonSpecific NotLimited (numeric value 128).
When comparing a status to GOOD, the expression evaluates to TRUE if the
status is GoodNonCascade (that is, in the range of (inclusive) 128 to 191).
To test a status for the entire range of GOOD statuses (GoodNonCascade and
GoodCascade), use the greater than or equal to operator (>=). That is, the
value is >= 128.
LIMITED_CONSTANT When a status field is compared to LIMITED_CONSTANT using the equality
operator (=), the result will be TRUE if the limit status is
LIMITED_CONSTANT.
LIMITED_HIGH When a status field is compared to LIMITED_HIGH using the equality operator
(=), the result will be TRUE if the limit status is LIMITED_HIGH.
LIMITED_LOW When a status field is compared to LIMITED_LOW using the equality operator
(=), the result will be TRUE if the limit status is LIMITED_LOW.
UNC If assigning UNC to a parameter status, the status is set to Uncertain
NonSpecific NotLimited (numeric value 64).
When comparing a status to UNC, the expression evaluates to TRUE if the
status has a value in the range of (inclusive) 64 to 127.
Operators
The Logic Solver Calc/Logic algorithm supports the following operators:
Unary Operators
O P E R AT O R T YP E EX AM P L E
unary minus (change sign) -'a'

unary plus +'a'
logical not !'a' or NOT 'a'
bitwise not ~'a'
762 OW351_R1100
8.9 LSCALC
Binary Operators
O P E R AT O R T YP E EX AM P L E
logical or 'a' OR 'b'

logical exclusive or 'a' XOR 'b'
logical and 'a' AND 'b'
bitwise or 'a' | 'b'
bitwise exclusive or 'a' ^ 'b'
bitwise and 'a' & 'b'
equals comparison 'a' = 'b'
not equals comparison 'a' <> 'b' or
'a' != 'b' or
'a' ~= 'b'
less than comparison 'a' < 'b'
greater than comparison 'a' > 'b'
less than or equal to comparison 'a' <= 'b'
greater than or equal to 'a' => 'b'
comparison
addition 'a' + 'b'
subtraction 'a' - 'b'
multiply 'a' * 'b'
divide 'a' / 'b'
modulus (remainder) 'a' MOD 'b' or
'a' % 'b'
power 'a' ** 'b'
Conditional Operator
The conditional operator (?) evaluates one of two expressions, depending on the value of a
condition. The syntax for using the operator is
condition?[expression1]:[expression2]
For example, the condition out1:=(in1=1)?in2:in3 means if IN1 is equal to 1 then OUT1 is set to
the value of IN2, if IN1 is NOT equal to 1 OUT1 is set to the value of IN3.
OW351_R1100 763
8.9 LSCALC
Functions
The Logic Solver Calc/Logic algorithm supports the following functions.
Math Functions
FU N C TI O N DE S C R I P TI O N N O TE S
ABS (x) Absolute value of x Returns the absolute value of parameter x.

EXP (x) Exponential of x Returns the exponential of parameter x if
successful. On overflow, the function returns
the MAX floating point (3.4E38). On
underflow, the function returns a zero value.
EXPT (x,y) Raise x to the power of y Computes x raised to the power of y. If x
equals zero and y equals zero, EXPT
returns a value of one (1). If x is less than
zero and y is not an integer, EXPT returns a
value of zero (0).
FRACT (x) Returns fractional part of a Returns the fractional part of x. The result is
number positive if x is greater than or equal to zero.
The result is negative if x is less than zero.
LN (x) Natural logarithm of x Returns the natural logarithm of x if
successful. If x is not positive, LN returns a
zero value.
LOG (x) Log base 10 of x Returns the logarithm base 10 of x if
successful. If x is not positive, LOG returns a
zero value.
LOG2 (x,y) Log base x of y Returns the logarithm base x of y if
successful. If x or y is not positive, LOG2
returns a zero value.
MAX (x,y) Maximum of x and y The return value is the greater of the two
specified values.
MIN (x,y) Minimum of x and y The return value is the smaller of the two
specified values.
ROUND (x) Round x to nearest float Rounds x to the nearest integer value.
SIGN (x) Sign indicator of x Returns a Boolean True value (1) if x is non-
negative. Returns a Boolean False value (0)
if x is negative.
SQRT (x) Square root of x Returns the square-root of x. If x is negative,
SQRT returns x.
TRUNC (x) Floor function Returns a value representing the largest
integer that is less than or equal to x. That
is, TRUNC rounds x to the next lowest
integer value.
764 OW351_R1100
8.9 LSCALC
Trigonometric Functions
FU N C TI O N DE S C R I P TI O N N O TE S
ACOS (x) Arc cosine of x Returns the arccosine of x in the range 0 to pi radians. If x is
less than -1 or greater than 1, ACOS returns a zero value.
ASIN (x) Arc sine of x Returns the arcsine of x in the range -pi/2 to pi/2 radians. If x is
less than -1 or greater than 1, ASIN returns a zero value.
ATAN (x) Arc tangent of x Returns the arctangent of x in radians.
COS (x) Cosine of x Returns the cosine of x where x is in radians.
SIN (x) Sine of x Returns the sine of x where x is in radians.
TAN (x) Tangent of x Returns the tangent of x where x is in radians.
Bitwise Functions
FU N C TI O N DE S C R I P TI O N NO TE S
ASR16 (i,n) Arithmetic Shift i Right n bits. Assumes 16-bit operand for sign preservation.
ROL (x,y) Rotate x to the left by y bits. Rotates the unsigned x by y bits to the left. The
function wraps bits rotated off one end of the value
to the other end. (Same as ROTL.)
ROR (x,y) Rotate x to the right by y bits. Rotates the unsigned x by y bits to the right. The
to the other end. (Same as ROTR.)
ROTL (x,y) Rotate x to the left by y bits. Rotates the unsigned x by y bits to the left. The
to the other end. (Same as ROL.)
ROTR (x,y) Rotate x to the right by y bits. Rotates the unsigned x by y bits to the right. The
to the other end. (Same as ROR.)
ROTL16 (i,n) Rotate i Left n bits Assumes 16-bit operand.
ROTR16 (i,n) Rotate i Right n bits Assumes 16-bit operand.
SHL (x,y) Shift x left by y bits, no carry Shifts x left by y number of positions and fills with
zeroes (0).
SHR (x,y) Shift x right by y bits, no carry Shifts x right by y number of positions and fills with
zeroes (0).
OW351_R1100 765
8.9 LSCALC
Miscellaneous Functions
FU N C TI O N DE S C R I P TI O N NO TE S
EUP (e,p0,p100) Conversion from Engineering Units Standard linear interpolation.

(EU) (e) to percent given the values at
0% (p0) and 100% (p100).
PEU (p,p0,p100) Conversion from Percent (p) to Standard linear interpolation.
Engineering Units (EU) given the
values at 0% (p0) and 100% (p100).
STBT (i,b,n) Set a bit position (n) in an integer
value (i) to a given Boolean value (b).
SYSSTAT (x) This function returns a TRUE or Allowable values for
FALSE when queried for system $sysstat_ls_opts are:
condition x. User passes one of the  Switchover
enumerated values for
 MyDownload
$sysstat_ls_opts.
 Powerfail
Comments
Comments are statements placed in an expression that act solely as a documentation tool for
users. The content of a comment has no effect on any processing. The structures of a comment
can take two forms:
 (* *) - Anything between "(*" and "*)" is treated as a comment, even if it spans lines. These
comments do not nest - the first occurrence of "*)" will terminate the comment no matter how
many "(*" have occurred.
 REM - Text on a line following "REM " (note the required space) is treated as a comment.
766 OW351_R1100
8.10 LSCEM
8.10 LSCEM
Description
Use the Logic Solver Cause and Effect Matrix (LSCEM) algorithm to define interlock and
permissive logic that associates as many as 16 inputs (CSx Input Cause parameters) and 16
outputs (EFFx Output Effect parameters). Use the algorithm's MATRX parameter to identify one
or more causes that cause each effect to trip. When a CSx becomes active, all effects associated
with that CSx also trip.
An LSCEM algorithm provides the logic for one or more safety instrumented functions (SIF). CSx
inputs are typically connected from upstream voter algorithms, but may come from any source
indicating either an active (0) or inactive (1) process trip condition. The EFFx outputs are typically
connected to downstream output algorithms.
Because the Logic Solver is a de-energize to trip environment, the Normal operating value of
EFFx parameters is 1 and the Tripped value is 0.
By default, the algorithm has four CSx inputs and one EFFx output. In addition, you can use the
DCx and DEx parameters to label causes and effects.
Functional Symbol
OW351_R1100 767
8.10 LSCEM
Algorithm Execution
Each EFFx output has a corresponding STAx (Current State of Effect) parameter. EFFx can be
either 1 (Normal) or 0 (Tripped). STAx can have one of six values shown in the following figure.
The arrows in the figure show the possible transitions between state values during normal
operation.
Figure 27: State Transition diagram for STAx parameters
The values of STAx depend on whether EFFx is Tripped or Normal. The following table shows the
combinations that can occur.
Combinations
EFFX STA X
Normal Normal
Trip Initiated-Delayed
Tripped Tripped
Waiting for Reset Permit
Ready to Reset
Waiting to Start Permit
After an initial load or a reboot of the Logic Solver, the initial value of every EFFx is Tripped. An
effect remains Tripped as long as any causes assoc iated with that effect are tripped. After all
associated causes clear the effect become Normal.
The default behavior of the algorithm is for EFFx output values to be a function of the value and
quality of the CSx inputs. EFFx Trips when one or more CSx associated with it is active.
768 OW351_R1100
8.10 LSCEM
You can modify this behavior with the LSCEM algorithm's parameters in a number of ways:
 Use DTMx (Trip Delay for Effect) to set a delay time for EFFx to transition to Tripped.
 Use RPTx (Reset Permit) to require an operator reset to transition EFFx to Normal. RPTx can
be set from process feedback or it could be a manual operator reset, such as from a key
switch.
 Use SPTx (Start Permit) to force STAx to Waiting for Start Permit, which prevents EFFx from
becoming Normal unless SPTx is True.
 Use CMASK (Cause Mask) to prevent selected causes from becoming active.
If you require a simple, time-based sequencing, use DTMx (Trip Delay for Effect) to prevent EFFx
from going directly to Tripped when an associated cause becomes inactive. W hile DTMx is
greater than 0 (zero), STAx (Current State) is Trip Initiated - Delayed, which keeps EFFxNormal.
To require an operator reset before an effect can return to Normal, use RRS x (Require Reset for
Effect), RPTx (Reset Permit), and RSTx (Reset). When RRSx is True, EFFx remains Tripped
when an associated cause is active. How STAx transitions depends on RPTx.
If RPTx is True (the default value), STAx transitions from "Tripped directly" to "Ready to Reset."
Configure RPTx to False to make STAx transition from "Tripped" to "Waiting for Reset Permit."
The reset permit can be written from process feedback or set by an operator from a key switch or
other hardware device. When RPTx becomes True, STAx transitions to "Ready to Reset." From
here, setting RSTx to True transitions STAx and EFFx to Normal.
Use SPTx (Start Permit) in a similar way to require permission to transition STA x from "Waiting for
Start Permit." The default value of SPTx is True, which allows the transition. If SPTx is False and
associated causes are cleared, STAx transitions from "Tripped" to "Waiting for Start Permit." To
move STAx and EFFx to Normal, set SPTx to True.
Manipulate the parameter CMASK to prevent one or more causes from becoming active under
certain process conditions. Setting a bit in CMASK to True prevents the corresponding CSx from
tripping any associated effects. If after an effect is tripped CMASK masks the causes that tripped
that effect, STAx transitions out of Tripped. The state it transitions to depends on the configuration
of the algorithm parameters FEFx, SPTx, RRSx, and RPTx. Do not manipulate CMASK directly
from runtime interfaces. To bypass process conditions use upstream voter algorithms instead.
ACSx indicates the currently active causes that are associated with EFFx that are not masked in
CMASK. FOTx indicates the cause or causes that first tripped EFFx. If additional causes become
active, FOTx does not change. FOTx retains its value until EFFx returns to Normal.
For example, if CS2 becomes active and EFF1 trips, ACS1 and FOT1 are both set to 2. If CS3
(which is also associated with EFF1) subsequently becomes active, FOT1 remains 2 and ACS1
becomes 6 (bits 2 and 3 of ACS1 are set).
OW351_R1100 769
8.10 LSCEM
The following table summarizes the state-dependent conditions necessary to transition EFFECTx
value between Tripped and Normal.
Conditions
RRS X S TATE - D E P E N D E N T CO N D I TI O N S RE Q U I R E D TO T R AN S I TI O N EFFX

V AL U E
FR O M T R I P P E D TO NO R MAL FR O M N O R MAL TO TR I P P E D
False (All associated non-masked causes are Any associated non-masked cause is active
inactive or
and SPTx = True) SOPT is set to Trip if Bad and any CSx
quality is Bad.
True (All associated non-masked causes are Any associated non-masked cause is active
inactive or
and RPTx = True SOPT is set to Trip if Bad and any CSx
and RSTx = True quality is Bad.
and SPTx = True)
The following descriptions and tables explain each state and the conditions necessary to
transition to other allowable states. Note that the value of the RSTx parameter is set to False at
the end of every execution independent of the current value of STAx.
STAx: Tripped
If STAx is Tripped, EFFx is also Tripped. STAx remains Tripped as long as one or more
associated non-masked causes are active.
EFFx transitions from Tripped when all the associated non-masked causes are inactive. If an
operator reset is not required and SPTx is True, STAx is set to Normal. If SPTx is False, STAx
moves to Waiting for Start Permit. If an operator reset is required and RPTx is True, STAx
becomes Ready to Reset. If RPTx is False, STAx becomes Waiting for Reset Permit.
The following table summarizes the possible changes STAx can make from Tripped.
Conditions
T O T R AN S I TI O N STA X T O ... RE Q U I R E S TH E FO L L O W I N G CO N D I TI O N S
Waiting for Reset Permit ACSx = 0

and RRSx = True
and RPTx = False
Ready to Res et ACSx = 0
and RRSx = True
and RPTx = True
Waiting for Start Permit ACSx = 0
and RRSx = False
and SPTx = False
Normal ACSx = 0
and RRSx = False
and SPTx = True
or
FEFx = Force Normal
770 OW351_R1100
8.10 LSCEM
STAx: Waiting for Reset Permit
While STAx is Waiting for Reset Permit, EFFx is set to Tripped. STAx can transition to this state
from Tripped or Ready to Reset if RRSx is True. If RRSx becomes False while STAx is Waiting
for Reset Permit, STAx does not change until a reset occurs.
STAx changes back to Tripped if an associated non-masked cause becomes active.
STAx changes to Ready to Reset if RPTx becomes True.
The following table summarizes the possible changes from Waiting for Reset Permit.
Tripped ACSx is not equal to 0

or
SOPT is set to Trip if Bad and any CSx quality is Bad.
Ready to Reset RPTx = True
STAx: Ready to Reset
STAx can transition to Ready to Reset from Tripped or Waiting for Reset Permit. EFFx is Tripped
when STAx is Ready to Reset.
To reach this state RRSx must be True. If RRSx becomes False while STAx is Ready to Reset,
the STAx does not change until a reset occurs.
If an associated non-masked cause becomes active or FEFx is Force Trip, STAx changes to
Tripped. If RPTx becomes False, STAx changes back to Waiting for Reset Permit.
If SPTx is True, the STAx changes to Normal when RSTx is True. If SPTx is False, RSTx
becoming True causes STAx to change to Waiting for Start Permit.
The following table summarizes the possible changes of STA,i>n from Ready to Reset.
Conditions

or
Waiting for Reset Permit RPTx = False
Waiting for Start Permit RSTx = True

and SPTx = False
Normal (RSTx = True
and SPTx = True)
OW351_R1100 771
8.10 LSCEM
STAx: Waiting for Start Permit
STAx can change from Tripped or Ready to Reset to Waiting for Reset Permit. EFFx is Tripped
when STAx is Waiting for Start Permit.
If an associated non-masked cause becomes active or FEFx is Force Trip, STAx changes to
Tripped.
If SPTx is True, STAx changes to Normal.
The following table summarizes the possible changes of STAx from Waiting for Start Permit.
Conditions

or
Normal SPTx = True
STATEn: Normal
STAx changes when a trip is initiated, that is, when one or more non-masked causes associated
with EFFx become active. If EFFx is not being sequenced with other effects, STAx becomes
Tripped immediately. Use DTMx to set how long to delay the transition to Tripped. If DTMx is non-
zero STAx changes to Trip Initiated-Delayed.
The following table summarizes the possible changes from Normal.
Conditions

and DTMx = 0
or
Trip Initiated - Delayed ACSx is not equal to 0
and DTMx > 0
or
772 OW351_R1100
8.10 LSCEM
STAx: Trip Initiated - Delayed
When STAxs Trip is Initiated - Delayed the trip condition has occurred, but EFFx continues to be
Normal until DTMx seconds have elapsed.
The timer DTRx (Trip Delay Timer for Effect) decrements from DTMx each scan based on the
algorithm's scan rate. The timer continues to count down even if no causes remain active.
When DTRx reaches zero, STAx changes to Tripped even if there are no active causes.
The following table summarizes the possible changes from Trip Initiated-Delayed.
Tripped DTRx = 0
or
Quality Handling
The quality of the CSx inputs influences block behavior based on how the SOPT (Status Options
if Bad Input) parameter is configured. The value of SOPT impacts the calculation of ACSx. The
status of the EFFx outputs is based on the quality of the associated causes and is not affected by
the value of SOPTS.
There are three options for SOPT: Always Use Value (the default option), Use Last Good Value if
Bad, and Trip if Bad.
When SOPT is set to Always Use Value, Bad status on an associated cause has no impact on the
value of ACSx. However, a sensor failure could cause an immediate shutdown as a result of the
process value changing. The setting of Use Last Good Value if Bad prevents the transition of an
associated cause to bad quality from initiating a shutdown, because the value used to calculate
ACSx is the value the last time the quality was Good. This allows time for repair. The third option
for SOPT is Trip if Bad. If this option is set, a Bad status on a cause input trips any associated
effect.
The quality of the effect outputs is set to Bad if any unmasked associated cause has Bad quality
and the effect is not forced to Normal or Tripped; otherwise, it is set to Good.
FI E L D RE C O R D
CMASK F4 - Integer Selectable Optional 0 Cause Mask LP
AUX1 G0 - SID Data Init Required - Auxiliary Record 1 LC
NOCS Y0 - Byte Data Init Required 1 Number of Causes -
NOEFF Y2 - Byte Data Init Required 1 Number of Effects -
Tunable Trip Delay for Effect 1

DTM1 R1 - Real Required 0.0 -
(sec)
OW351_R1100 773
8.10 LSCEM
FI E L D RE C O R D

(sec)
(sec)
(sec)
(sec)
(sec)
(sec)
(sec)
(sec)
DTM10 S1 - Real Required 0.0 -
(sec)
(sec)
(sec)

(sec)
(sec)

(sec)
(sec)
RRS1 X6 – Byte Tunable Required 1 Require Reset for -
Bit 0 Effect 1
0 - False
1 - True
Bit 1 Effect 2
0 - False
1 - True
Bit 2 Effect 3
0 - False
1 - True
774 OW351_R1100
8.10 LSCEM
FI E L D RE C O R D

Bit 3 Effect 4
0 - False
1 - True
Bit 4 Effect 5
0 - False
1 - True
Bit 5 Effect 6
0 - False
1 - True
Bit 6 Effect 7
0 - False
1 - True
Bit 7 Effect 8
0 - False
1 - True
Bit 0 Effect 9
0 - False
1 - True
Bit 1 Effect 10
0 - False
1 - True
Bit 2 Effect 11
0 - False
1 - True
Bit 3 Effect 12
0 - False
1 - True
Bit 4 Effect 13
0 - False
1 - True
Bit 5 Effect 14
0 - False
1 - True
Bit 6 Effect 15
0 - False
1 - True
OW351_R1100 775
8.10 LSCEM
FI E L D RE C O R D

Bit 7 Effect 16
0 - False
1 - True
FOP1 X4 – Byte Tunable Required 0 Force Opt: -
Bit 0 MulForceAllowed
0 - No
1 - Yes
ROP1 X5 – Byte Tunable Required 0 Report Opt: NoRollUp -
Bit 0 0 - False
1 - True
ROP2 X5 – Byte Tunable Required 0 Report Opt: -
0 - False
1 - True
SOPT X3 - Byte Tunable Required 3 Status Options if Bad -
Input
1 - Always Use Value
2 - Use Last Good
Value if Bad
3 - Trip if Bad
CS1 X8 - Byte - Variable Required - Input Cause 1 LD
Bit 0
AUX2:G0 -
SID
CS2 X8 - Byte - Variable Optional - Input Cause 2 LD
Bit 1
AUX2:G1 -
SID
Bit 2
AUX2:G2 -
SID
Bit 3
AUX2:G3 -
SID
Bit 4
AUX2:G4 -
SID
Bit 5
AUX2:G5 -
SID
Bit 6
AUX2:G6 -
SID
776 OW351_R1100
8.10 LSCEM
FI E L D RE C O R D

Bit 7
AUX2:G7 -
SID
Bit 0
AUX2:G8 -
SID
Bit 1
AUX2:G9 -
SID
Bit 2
AUX2:B0 -
SID
Bit 3
AUX2:B1 -
SID
Bit 4
AUX2:B2 -
SID
Bit 5
AUX2:YU -
SID
Bit 6
AUX2:B4 -
SID
Bit 7
AUX2:B5 -
SID
EFF1 AUX1:YC - Variable Required - Output Effect 1 LD
Integer Bit 0
AUX2:B6 -
SID
EFF2 AUX1:YC - Variable Optional - Output Effect 2 LD
Integer Bit 1
AUX2:B7 -
SID
Integer Bit 2
AUX2:B8 -
SID
OW351_R1100 777
8.10 LSCEM
FI E L D RE C O R D

Integer Bit 3
AUX2:B9 -
SID
Integer Bit 4
AUX2:C0 -
SID
Integer Bit 5
AUX2:C1 -
SID
Integer Bit 6
AUX2:C2 -
SID
Integer Bit 7
AUX2:C3 -
SID
Integer Bit 8
AUX2:C4 -
SID
Integer Bit 9
AUX2:C5 -
SID
Integer Bit
10
AUX2:C6 -
SID
Integer Bit
11
AUX2:C7 -
SID
Integer Bit
12
AUX2:C8 -
SID
Integer Bit
13
AUX2:YT -
SID
778 OW351_R1100
8.10 LSCEM
FI E L D RE C O R D

Integer Bit
14
AUX2:D0 -
SID
Integer Bit
15
AUX2:YQ -
SID
AUX1:B6 - Variable First Causes to Trip
FOT1 Optional - LP
Integer Effect 1
FOT2 Optional - LP
Integer Effect 2
FOT3 Optional - LP
Integer Effect 3
FOT4 Optional - LP
Integer Effect 4
AUX1:C0 - Variable First Causes to Trip
FOT5 Optional - LP
Integer Effect 5
FOT6 Optional - LP
Integer Effect 6
FOT7 Optional - LP
Integer Effect 7
FOT8 Optional - LP
Integer Effect 8
FOT9 Optional - LP
Integer Effect 9
FOT10 Optional - LP
Integer Effect 10
FOT11 Optional - LP
Integer Effect 11
FOT12 Optional - LP
Integer Effect 12
FOT13 Optional - LP
Integer Effect 13
AUX1:YT - Variable First Causes to Trip
FOT14 Optional - LP
Integer Effect 14
AUX1:D0 - Variable First Causes to Trip
FOT15 Optional - LP
Integer Effect 15
AUX1:YQ - Variable First Causes to Trip
FOT16 Optional - LP
Integer Effect 16
OW351_R1100 779
8.10 LSCEM
FI E L D RE C O R D
STA1 AUX1:YM – Variable Optional - Current State of Effect LA

Integer 1
Bits 0-3 5 - Normal
6 - Trip Initiated-
Delayed
1 - Tripped
2 - Waiting for Reset
Permit
3 - Ready to Reset
4 - Waiting for Start
Permit
Integer 2
Bits 4-7 5 - Normal
6 - Trip Initiated-
Delayed
1 - Tripped
Permit
3 - Ready to Reset
Permit
Integer 3
Bits 8-11 5 - Normal
6 - Trip Initiated-
Delayed
1 - Tripped
Permit
3 - Ready to Reset
Permit
Integer 4
6 - Trip Initiated-
Delayed
1 - Tripped
Permit
3 - Ready to Reset
Permit
Integer 5
6 - Trip Initiated-
Delayed
1 - Tripped
Permit
3 - Ready to Reset
Permit
780 OW351_R1100
8.10 LSCEM
FI E L D RE C O R D

Integer 6
6 - Trip Initiated-
Delayed
1 - Tripped
Permit
3 - Ready to Reset
Permit
Integer 7
6 - Trip Initiated-
Delayed
1 - Tripped
Permit
3 - Ready to Reset
Permit
Integer 8
6 - Trip Initiated-
Delayed
1 - Tripped
Permit
3 - Ready to Reset
Permit
STA9 AUX1:YL – Variable Optional - Current State of Effect LA
Integer 9
Bits 0-3 5 - Normal
6 - Trip Initiated-
Delayed
1 - Tripped
Permit
3 - Ready to Reset
Permit
Integer 10
Bits 4-7 5 - Normal
6 - Trip Initiated-
Delayed
1 - Tripped
Permit
3 - Ready to Reset
Permit
OW351_R1100 781
8.10 LSCEM
FI E L D RE C O R D

Integer 11
6 - Trip Initiated-
Delayed
1 - Tripped
Permit
3 - Ready to Reset
Permit
Integer 12
6 - Trip Initiated-
Delayed
1 - Tripped
Permit
3 - Ready to Reset
Permit
Integer 13
6 - Trip Initiated-
Delayed
1 - Tripped
Permit
3 - Ready to Reset
Permit
Integer 14
6 - Trip Initiated-
Delayed
1 - Tripped
Permit
3 - Ready to Reset
Permit
Integer 15
6 - Trip Initiated-
Delayed
1 - Tripped
Permit
3 - Ready to Reset
Permit
782 OW351_R1100
8.10 LSCEM
FI E L D RE C O R D

Integer 16
6 - Trip Initiated-
Delayed
1 - Tripped
Permit
3 - Ready to Reset
Permit
ACS1 AUX1:D2 - Variable Optional - Active Causes for LP
Integer Bits Effect 1
0-15
16-31
ACS3 AUX1:YP - Variable Optional - Active Causes for LP
0-15
ACS4 AUX1:YP - Variable Optional - Active Causes for LP
16-31
0-15
16-31
0-15
16-31
0-15
16-31
ACS11 AUX1:YN - Variable Optional - Active Causes for LP
0-15
ACS12 AUX1:YN - Variable Optional - Active Causes for LP
16-31
OW351_R1100 783
8.10 LSCEM
FI E L D RE C O R D

0-15
16-31
0-15
16-31
AUX1:R1 - Variable Trip Delay Timer for
DTR1 Optional - LA
Real Effect 1
DTR2 Optional - LA
Real Effect 2
DTR3 Optional - LA
Real Effect 3
DTR4 Optional - LA
Real Effect 4
DTR5 Optional - LA
Real Effect 5
DTR6 Optional - LA
Real Effect 6
DTR7 Optional - LA
Real Effect 7
DTR8 Optional - LA
Real Effect 8
DTR9 Optional - LA
Real Effect 9
AUX1:S1 - Variable Trip Delay Timer for
DTR10 Optional - LA
Real Effect 10
DTR11 Optional - LA
Real Effect 11
DTR12 Optional - LA
Real Effect 12
DTR13 Optional - LA
Real Effect 13
DTR14 Optional - LA
Real Effect 14
DTR15 Optional - LA
Real Effect 15
DTR16 Optional - LA
Real Effect 16
784 OW351_R1100
8.10 LSCEM
FI E L D RE C O R D
CALRT AUX1:E8 - Variable Optional - Alarms Conditions Set LP

Integer by Block
1 - An Effect is forced
to Trip or Normal
2 - An Effect has a
non-zero FIRST_OUT
LTRIP X2 - Byte Variable Optional - Latent Trip Indicator LD
RPT1 G2 - Integer Selectable Optional 1 Reset Permit 1 LD
0 - False
1 - True
0 - False
1 - True
0 - False
1 - True
0 - False
1 - True
0 - False
1 - True
0 - False
1 - True
0 - False
1 - True
0 - False
1 - True
RPT9 B0 - Integer Selectable Optional 1 Reset Permit 9 LD
0 - False
1 - True
0 - False
1 - True
0 - False
1 - True
RPT12 YU - Integer Selectable Optional 1 Reset Permit 12 LD
0 - False
1 - True
0 - False
1 - True
OW351_R1100 785
8.10 LSCEM
FI E L D RE C O R D

0 - False
1 - True
0 - False
1 - True
0 - False
1 - True
SPT1 D8 - Integer Selectable Optional 1 Start Permit 1 LD
0 - False
1 - True
SPT2 D9 - Integer Selectable Optional 1 Start Permit 2 LD
0 - False
1 - True
SPT3 YM - Integer Selectable Optional 1 Start Permit 3 LD
0 - False
1 - True
SPT4 YL - Integer Selectable Optional 1 Start Permit 4 LD
0 - False
1 - True
SPT5 E2 - Integer Selectable Optional 1 Start Permit 5 LD
0 - False
1 - True
0 - False
1 - True
0 - False
1 - True
SPT8 YC - Integer Selectable Optional 1 Start Permit 8 LD
0 - False
1 - True
SPT9 Y9 - Integer Selectable Optional 1 Start Permit 9 LD
0 - False
1 - True
0 - False
1 - True
0 - False
1 - True
0 - False
1 - True
0 - False
1 - True
786 OW351_R1100
8.10 LSCEM
FI E L D RE C O R D

0 - False
1 - True
SPT15 XY - Integer Selectable Optional 1 Start Permit 15 LD
0 - False
1 - True
SPT16 XW - Integer Selectable Optional 1 Start Permit 16 LD
0 - False
1 - True
MTR1 AUX1:G0 - Data Init Required 0 CEM Matrix Column 1; -
Integer Parameter value visible
in LC record only
in LC record only
in LC record only
in LC record only
in LC record only
in LC record only
in LC record only
in LC record only
in LC record only
MTR10 AUX1:G9 - Data Init Required 0 CEM Matrix Column -
Integer 10; Parameter value
visible in LC record
only
MTR11 AUX1:B0 - Data Init Required 0 CEM Matrix Column -
only
only
OW351_R1100 787
8.10 LSCEM
FI E L D RE C O R D

only
MTR14 AUX1:YU - Data Init Required 0 CEM Matrix Column -
only
only
only
RST1 B8 - Integer Selectable Optional 0 Reset 1 LD
0 - False
1 - True
RST2 B9 - Integer Selectable Optional 0 Reset 2 LD
0 - False
1 - True
RST3 C0 - Integer Selectable Optional 0 Reset 3 LD
0 - False
1 - True
0 - False
1 - True
0 - False
1 - True
0 - False
1 - True
0 - False
1 - True
0 - False
1 - True
0 - False
1 - True
0 - False
1 - True
788 OW351_R1100
8.10 LSCEM
FI E L D RE C O R D

0 - False
1 - True
RST12 YT - Integer Selectable Optional 0 Reset 12 LD
0 - False
1 - True
RST13 D0 - Integer Selectable Optional 0 Reset 13 LD
0 - False
1 - True
RST14 YQ - Integer Selectable Optional 0 Reset 14 LD
0 - False
1 - True
RST15 D2 - Integer Selectable Optional 0 Reset 15 LD
0 - False
1 - True
RST16 YP - Integer Selectable Optional 0 Reset 16 LD
0 - False
1 - True
AUX2 G1 - SID Data Init Required - Auxiliary Record 2 LC
CALRT
The following table shows the alert that can appear for an LSCEM algorithm; an explanation and
the bit position is given.
This alert will be sent to the Ovation Process Historian as a SIF alert. For more information on SIF
alerts, refer, Ovation Safety Instrumented System (SIS) User Guide.
Bit description
An Effect has a non-zero FOT (First Active when there is a non-zero FOTx. 1
Causes to Trip Effect).
OW351_R1100 789
8.11 LSCMP
8.11 LSCMP
Description
The Logic Solver Comparator (LSCMP) algorithm compares two values (DSCV and CMPV1 -
Input and First Comparative Value respectively) and sets a Boolean output for each of the
following comparisons: LT (Less Than), GT (Greater Than), EQ (Equal To), NEQ (Not Equal).
Additionally, the LSCMP algorithm compares the DSCV against the range defined by CMPV2 and
CMPV1 to determine the Boolean output, INRGE (In-Range Comparison Output).
Functional Symbol
Algorithm Execution
The LSCMP algorithm has two algorithm calculations; the comparison calculation and the quality
propagation.
Comparison Calculation
The LSCMP algorithm compares the DSCV input with the CMPV1 input, the primary comparison
value. Based on the relationship between DSCV and CMPV1, the LT, GT, EQ, and NEQ outputs
are set to 0 (False) or 1 (True). A secondary comparison determines if DSCV is within the range
of CMPV1 to CMPV2. If DSCV is within this range, then the INRGE output is set to 1 (True),
otherwise 0 (False).
Quality Propagation
Bad quality on any of the input values propagates to the output. If the DSCV has bad quality, all
outputs reflect this bad quality. If DSCV has good quality but CMPV1 or CMPV2 has bad quality,
then the outputs associated with the bad input are also set to bad. The quality calculation is totally
independent of the comparison calculations.
The following table shows an example of the LSCMP algorithm outputs based on different input
values.
Sample LSCMP algorithm outputs
P AR AME T E R EX AM P L E 1 EX AM P L E 2 EX AM P L E 3
DSCV 2.25 -233.0 37.5

CMPV1 15.0 -200.0 37.5
CMPV2 1.0 0.0 10.0
LT 1 1 0
GT 0 0 0
790 OW351_R1100
8.11 LSCMP
P AR AME T E R EX AM P L E 1 EX AM P L E 2 EX AM P L E 3
EQ 0 0 1
NEQ 1 1 0
INRGE 1 0 1
Quality Handling
Quality of each output is set to the worst quality of the inputs for each output, except that
Uncertain status is treated as Good for determining quality.
For example, if the quality on CMPV1 is bad, the quality on LT, GT, EQ, and NEQ are all set to
BAD. Also, if the quality on CMPV1 or CMPV2 is BAD, then the quality on INRGE is BAD.
FI E L D RE C .
DSCV R1 - Real Variable Required - Input LA

CMPV1 T1 - Real Selectable Optional 0 First Comparative LA
Value
CMPV2 T2 - Real Selectable Optional 0 Second Comparative LA
Value
EQ X1 - Byte Variable Optional - Equal Comparison LD
Output
GT X2 - Byte Variable Optional - Greater Than LD
Comparison Output
INRGE X3 - Byte Variable Optional - In-Range LD
Comparison Output
LT X4 - Byte Variable Optional - Less Than LD
Comparison Output
NEQ X5 - Byte Variable Optional - Not Equal LD
Comparison Output
OW351_R1100 791
8.12 LSDI
8.12 LSDI
Description
The Logic Solver Digital Input (LSDI) algorithm accesses a single digital input from a two-state
field device and makes the processed physical input available to other algorit hms. You can
configure inversion on the input value.
The LSDI algorithm supports signal quality propagation.
The input can come from a local input channel on the Logic Solver or from input channel data
sent across the SIS Net from another Logic Solver.
Functional Symbol
Algorithm Execution
The LSDI algorithm accesses a single digital input from a two-state field device and makes the
processed physical input available to other algorithms. You can configure inversion on the input
value.
After calculation, the process variable (PVD) is copied to the output (OUT).
I/O Selection
When you configure the Digital Input algorithm, you select the input channel associated with the
digital measurement by configuring the Ovation point. You select the point and the parameter the
Digital Input algorithm accesses on that channel. Note that points can be specified for channels
directly attached to this Logic Solver or channels attached to Logic Solvers that reside in the
same SIS Data Server.
When you select Digital Input Channel for the channel type, the only selectable channel
parameter is:
FVALD – The last digital value with quality reported by the channel.
Field Value Processing
You can select the Invert input option (IOP1) to process FVALD:
 Invert
When Invert is selected a NOT is performed on FVALD and the resulting value is copied to PVD
and OUT.
792 OW351_R1100
8.12 LSDI
Quality Handling
Under normal conditions, a GOOD quality is passed through to OUT.
When the quality becomes Bad on the input channel, FVALD, PVD, and OUT are set to Bad
quality and the BLERR parameter shows Bad PV. Quality becomes Bad when line fault detection
is enabled and a line fault has been detected.
FI E L D RE C O R D
OUT X5 - Byte Variable Required - Digital Output with LD

Quality
PVD X6 - Byte Variable Optional - Digital Output Value LD
Only
FVALD X7 - Byte Variable Optional - Hardware Channel LD
Value
BLERR G1 - Integer Variable Optional - Block Error Status LX
 256 - Input
Failure/Bad PV
IOP1 G0 - Integer Data Required 0 IO Opt: Invert Input. -
Bit 0 Init. This parameter is
copied from the channel
configuration and can't
be changed in algorithm
configuration.
 0 - No
 1 - Yes
OW351_R1100 793
8.13 LSDO
8.13 LSDO
Description
The LSDO algorithm drives a Logic Solver output channel (for example, a Digital Output channel)
to manipulate a solenoid or other final element. In a typical application, the algorithm's input is
from an output of a Logic Solver Cause and Effect Matrix (LSCEM) algorithm. The LSDO
algorithm must be used in the same Logic Solver as the physical connection of the channel.
Functional Overview
The following algorithm diagram shows a simple application that uses the LSDO algorithm to
operate a solenoid valve.
Figure 28: Simple LSDO application diagram
In this example, the input to the Logic Solver Digital Output algorithm is an effect output from a
Cause and Effect Matrix algorithm. During normal operation the effect output's value is 1. When
the inputs to the Cause and Effect Matrix algorithm indicate a hazardous condition exists, the
effect output is set to 0 (zero). This, in turn, trips the output of the Digital Output algorithm, driving
the associated Logic Solver channel to close the valve.
The Logic Solver Digital Input algorithm is wired to a limit switch or other indicator to confirm that
the valve closes. If the valve does not close, the PV input to the Digital Output algorithm from the
Digital Input algorithm eventually sets a fault state in the Digital Output algorithm.
794 OW351_R1100
8.13 LSDO
This simple example does not illustrate a number of configurable functions the algorithm supports:
 Options for detecting a fault state.
 Timers to delay sending a signal to close the valve or set the fault state.
 Requiring permission before resetting the algorithm to normal operation after being tripped.
Functional Symbol
Algorithm Execution
Because the Logic Solver is a De-energized to Trip environment the normal operating value of the
output is On (1) and the tripped value is Off (0).
To use the LSDO algorithm in a safety shutdown application, as sign IOOUT to a Logic Solver
Digital Output channel connected to a valve controller. Typically, the CASND input of the LSDO
algorithm would be wired from an EFFECT output of an upstream LSCEM algorithm. Default
LSDO algorithm behavior passes the value of CASND to OUTD.
You can wire feedback from the final element to the RDBK input parameter of the LSDO
algorithm. This input would typically be wired from an LSDI algorithm representing a limit switch.
The RDBK value becomes the PVD of the LSDO algorithm. If the configurable time CTTM expires
before PVD confirms the off state, the DALRT Failed to confirm after trip command becomes
True. If RDBK is not wired, PVD has the same value as OUTD, so confirmation is immediate.
Fault State Detection
The LSDO algorithm enters a fault state when any of three conditions is detected and a
corresponding option has been selected for the detected condition. When the fault state is active,
the algorithm forces OUTD to Off, sets the Fault State Active bit in BLERR, and sets FSTAT to
Active. The FOPx options are selected by default and include:
 Enable detection based on CASND quality.
If the quality of CASND becomes Bad, FTMR begins incrementing from 0.0. If the quality
remains Bad for FTIM seconds, OUTD is forced to Off (0). FTMR continues to increment
while the quality of CASND is Bad. The fault state condition clears immediately when the
quality transitions away from Bad.
 Enable detection based on output channel quality.
OUTD is forced to Off if the Logic Solver detects a short or open in the field wiring (quality of
OUTD is Bad) while OUTD is being commanded On. The LSDO algorithm reacts to this
quality by forcing the output Off to track the state of the final element. Note that FTIM has no
effect when the fault state is a result of OUTD quality.
Note: If you use this option, you must also require a reset, either in this algorithm or in an
upstream LSCEM algorithm, because an active fault state condition clears when the algorithm
drives the output Off. Requiring a reset prevents the algorithm from driving the output back to
On during the next scan.
OW351_R1100 795
8.13 LSDO
 Enable detection based on PVD value.

OUTD is forced to 0 based on feedback from the final element wired into RDBK. The final
element is confirmed Off (PVD is 0) while OUTD is commanded On. Use this option to force
the output Off if a failure of the final element is not detected by a Logic Solver diagnostic.
RDBK should be wired when using this option; otherwise, PVD has the same value as OUTD.
Note that FTIM has no effect when the fault state is a result of the value of PVD.
Note: If you use this option, you must also require a reset, either in this algorithm or in an
FTMR is a writeable parameter. Be advised that writing to FTMR can cause the state of OUTD to
change depending on the value written.
Determining the Value of OUTD and Writing the Output Channel Value
The following figure is the state transition diagram for OSTAT. When OSTAT is Off or Off - Ready
to Reset, the value of OUTD is Off (0) and the Logic Solver channel defined by IOOUT is written
to Off. When OSTAT is On, OUTD is On (1) and IOOUT is written to On.
Figure 29: OSTAT Transition diagram
Note: To require a manual reset to transition OUTD to On (1), Emerson recommends that you
configure this in an upstream LSCEM algorithm, not the LSDO algorithm. The LSCEM algorithm
has a number of features that enhance the reset logic. The ability to require resets in the LSDO
algorithm (using the RQRST parameter) is provided if you do not have voter and LSCEM
algorithms to implement shutdown logic.
796 OW351_R1100
8.13 LSDO
If you set the LSDO algorithm's RQRST parameter to True, any transition of OUTD to Off (0)
causes OUTD to remain Off until all of the following conditions are met:
 CASND equals 1.
 FSTAT is not active.
 RST is True.
RST should be changed to True using a button on a process display. The algorithm changes RST
back to False. Do not expose RST as an input on the algorithm and wire to it. If you need to reset
an LSDO algorithm from control module logic, use an LSCALC algorithm to do a conditional
assignment to RST.
When OSTAT is Off or Off - Ready to Reset, the value of OUTD is 0 and the channel on this
Logic Solver defined by IOOUT is written to Off.
When OSTAT is On, OUTD is 1 and the channel is written to On.
Determining the Value of PVD
PVD normally gets its value from RDBK. If the quality of RDBK is bad quality, PVD has the same
value as OUTD. Use the invert input option in the upstream LSDI algorithm if you are using a
closed limit switch.
Determining the Value of DALRT
The DALRT parameter reports two alarm conditions set by the algorithm (inactive = 0, active = 1):
 Failed to confirm after trip command.

The device fails to confirm after being commanded to trip. On any transition of OUTD to Off,
the algorithm starts a confirmation timer. If the value of PVD is not 0 within CTTM seconds,
the alert Failed to confirm after trip command becomes True. The alert clears when OUTD
transitions to On (1).
 Confirm lost while commanded On.
The device confirms Off while it is being commanded On. When OSTAT is On and PVD has
transitioned to 1, the condition is detected if PVD becomes 0, for example if the device has a
failure that causes it to confirm in the Off state. The alert clears on the next transition of
OSTAT to On.
OW351_R1100 797
8.13 LSDO
Event Generation
The LSDO algorithm generates a SIF Error/SIF Alert event record when any of the following
conditions become active and the ROPx option "Event records are not generated" is not selected.
The following alerts will be sent to the Ovation Process Historian. For more information on SIF
Errors and SIF Alerts, refer to Ovation Safety Instrumented System (SIS) User Guide.
 The algorithm has set DALRT Failed to confirm following a command to trip.
 The algorithm has set DALRT Confirm lost while commanded On.
 The command to trip was successful and RDBK has been wired.
Alarm Detection
You can configure alarms to reference bits in DALRT and BLERR. You can reference these alarm
conditions upstream of the LSDO algorithm when required.
The Failed to confirm after trip command alert in DALRT propagates to the module level and
Module Event is sent to the Ovation Process Historian when the ROP x option "Alarm conditions
do not roll up to module level" is not selected.
Quality Handling
Quality is considered in the detection of the fault state.
The quality of OUTD is normally Good. If the fault state is active, the quality is Good. If the quality
on the output channel is Bad, the quality of OUTD is set to Bad. Bad SensorFailure LowLimited
indicates an open or short circuit has been detected. Bad DeviceFailure NotLimited indicates a
channel error.
The quality of PVD is that of RDBK unless its quality is not connected, in which case the quality of
PVD is the same as OUTD.
FI E L D RE C .
CASND X1 - Byte Variable Required - Input LD

Variable Actual Element
RDBK X2 - Byte Optional - LD
Feedback Input
PVD X3 - Byte Variable Optional - Readback Value LD
OSTAT X4 - Byte Variable Optional - Output Current State LA
 0 - Off
 1 - Off - Ready to
Reset
 2 - On
Variable Feedback Confirm
CTTMR R6 - Real Optional - LA
Timer
Variable Fault Detection Timer
FTMRH R7 - Real Optional - LA
(hrs)
798 OW351_R1100
8.13 LSDO
FI E L D RE C .
BLERR G2 - Variable Optional - Block Error Status. The LX

Integer choices are:
 128 - Output Failure
 256 - Input
Failure/Bad PV
 1024 - Fault State is
Active
FSTAT X5 - Byte Variable Optional - Fault State Status LA
 0 - Not Active
 1 - Active
DALRT G3 - Variable Optional - Alarm Conditions Set by LX
Integer Block
 1 - Failed to Confirm
after trip command
 2 - Confirm lost while
commanded ON
OUTD X9 - Byte Variable Optional 0 Output Value LD
FOP2 G0 - Tunable Required 1 FState Opt: -
Integer FaultDetectbyCASND
(Bits 1) 0=No
1=Yes
Integer FaultDetectbyOUTD
(Bits 2) 0=No
1=Yes
Integer FaultDetectbyPVD
(Bits 3) 0=No
1=Yes
FTIM R4 - Real Tunable Required 300 Fault Detection Delay -
Time (sec)
FTMR R5 - Real Variable Optional - Fault Detection Timer -
(sec)
CTTM R1 - Real Tunable Required 5 Output Feedback Time -
(sec)
ROP1 G1 - Tunable Required 0 Report Opt: NoRollUp -
Integer 0=False
(Bits 0) 1=True
ROP2 G1 - Tunable Required 0 Report -
Integer Opt:NoEventRecords
(Bits 1) 0=False
1=True
RQRST X7 - Byte Tunable Required 0 Require Reset -
(Bit0) 0=False
1=True
RST X8 - Byte Selectable Optional 0 LD
Reset
OW351_R1100 799
8.13 LSDO
DALRT
The following table shows the alerts that can appear for an LSDO algorithm and the bit position of
each alert.
Bit value
B I T V AL U E BI T P O S I TI O N
Failed to confirm after trip command. 0

Confirm lost while commanded On. 1
800 OW351_R1100
8.14 LSDVC
8.14 LSDVC
Description
The Logic Solver Digital Valve Controller (LSDVC) algorithm provides an interface to the Fisher
Controls DVC6000ESD digital valve controller for safety shutdown applications. The algorithm's
output is assigned to a HART Two-state Output Channel on a Logic Solver. In a typical
application the algorithm's input is from an output of a Cause And Effect Matrix (LSCEM)
algorithm. The LSDVC algorithm must be used in the same Logic Solver as the physical
connection of the channel.
Functional Overview
The LSDVC algorithm contains all of the parameters found in the Digital Output (LSDO) algorithm.
In addition, the LSDVC algorithm performs automatic and manual partial stroke testing on the
associated valve.
The following algorithm diagram shows a simple application that uses the LSDVC algorithm to
operate a DVC6000ESD digital valve controller.
Figure 30: Simple LSDVC application diagram
OW351_R1100 801
8.14 LSDVC
In this example, the input to the Digital Valve Controller algorithm is an effect output from a Cause
and Effect Matrix algorithm. During normal operation, the effect output's value is 1. When the
inputs to the Cause and Effect Matrix algorithm indicate a hazardous condition exists, the effect
output is set to 0 (zero). This, in turn, trips the output of the Digit al Valve Controller algorithm,
driving the associated Logic Solver HART Two-state Output Channel to the configured off-current
value, which closes the valve.
The Digital Input algorithm is wired to a limit switch or other indicator to confirm that the valve
closes. If the valve does not close, the PV input to the Digital Valve Controller algorithm from the
Digital Input algorithm eventually sets a fault state in the Digital Valve Controller algorithm.
This simple example does not illustrate a number of configurable functions the algorithm supports:
 Options for detecting a fault state.
 Timers to delay sending a signal to close the valve or set the fault state.
 Requiring permission before resetting the algorithm to normal operation after being tripped.
 A number of features that support partial stroke testing.
Functional Symbol
Algorithm Execution
Because the Logic Solver is a De-energized to Trip environment, the normal operating value of
the output is On (1) and the tripped value is Off (0).
To use the LSDVC algorithm in a safety shutdown application, assign IOOUT to a Logic Solver
HART Two-state Output Channel connected to a Fisher Controls DVC6000ESD digital valve
controller. Typically, the CASND input of the LSDVC algorithm would be wired from an EFFECT
output of an upstream LSCEM algorithm. Default LSDVC algorithm behavior passes the value of
CASND to OUT.
You can wire feedback from the DVC6000ESD to the RDBK input parameter of the LSDVC
algorithm. This input would typically be wired from an LSDI algorithm representing a limit switch.
The RDBK value becomes the PVD of the LSDVC algorithm. If the configurable time CTTM
expires before PVD confirms the off state, the "DALRT Failed to confirm after trip" c ommand
becomes True. If RDBK is not wired, PVD has the same value as OUT, so confirmation is
immediate.
802 OW351_R1100
8.14 LSDVC
Fault State Detection
The LSDVC algorithm enters a fault state when any of three conditions is detected and a
corresponding option has been selected for the detected condition. When the fault state is active,
the algorithm forces OUT to Off, sets the Fault State Active bit in BLERR, and sets FSTAT to
Active. The FOPx options are selected by default and include:
 Enable detection based on CASND quality.
If the quality of CASND becomes Bad, FTMR begins incrementing from 0.0. If the quality
remains Bad for FTIM seconds, OUT is forced to 0 (zero). FTMR continues to increment while
the quality of CASND is Bad. The fault state condition clears immediately when the quality
transitions away from Bad.
 Enable detection based on output channel quality.
OUT is forced to Off if the Logic Solver detects a short or open in the field wiring (quality of
OUT is bad quality) while OUT is being commanded On. The LSDVC algorithm reacts to this
quality by forcing the output Off to track the state of the DVC6000ESD. Note that FTIM has no
effect when the fault state is a result of OUT quality.
Note: If you use this option you must also require a reset, either in this algorithm or in an
 Enable detection based on PVD value.

OUT is forced to 0 based on feedback from the final element wired into RDBK. The final
element is confirmed Off (PVD is 0) while OUT is commanded On. Use this option to force the
output off if a failure of the final element is not detected by a Logic Solver diagnostic. RDBK
should be wired when using this option; otherwise, PVD has the same value as OUT. Note
that FTIM has no effect when the fault state is a result of the value of PVD.
Note: If you use this option you must also require a reset, either in this algorithm or in an
FTMR is a writeable parameter. Be advised that writing to FTMR can cause the state of OUT to
change depending on the value written.
OW351_R1100 803
8.14 LSDVC
Determining the value of OUT and writing the output channel value
The following figure is the state transition diagram for OSTAT. When OSTAT is Off or Off - Ready
to Reset, the value of OUT is Off (0) and the Logic Solver channel defined by IOOUT is written to
Off. When OSTAT is On, OUT is On and IOOUT is written to On.
Figure 31: OSTAT Transition diagram
Note: To require a manual reset to transition OUT to On (1), Emerson recommends that you
configure this in an upstream LSCEM algorithm, not the LSDVC algorithm. The LSCEM
algorithm has a number of features that enhance the reset logic. The ability to require resets in
the LSDVC algorithm (using the RQRST parameter) is provided if you do not have voter and
LSCEM algorithms to implement shutdown logic.
If you set the LSDVC algorithm's RQRST parameter to True, any transition of OUT to Off (0)
causes OUT to remain Off until all of the following conditions are met:
 CASND equals 1.
 FSTAT is not active.
 RST is True.
RST should be changed to True using a button on a process display. The algorithm changes RST
back to False. Do not expose RST as an input on the algorithm and wire to it. If you need to reset
an LSDVC algorithm from control module logic, use an LSCALC algorithm to do a conditional
assignment to RST.
When RQRST is False, OUT's value is based on the value of CASND unless the fault state is
active.
When OSTAT is Off or Off - Ready to Reset, the value of OUT is Off and the channel on this
Logic Solver defined by IOOUT is written to Off. This results in the configured OFCUR value (0 or
4 mA) being sent to the Logic Solver's HART Two-state Output Channel defined in IOOUT.
When OSTAT is On, OUT is On and the channel is written to On. This results in 20 mA being sent
to the Logic Solver's HART Two-state Output Channel.
804 OW351_R1100
8.14 LSDVC
Determining the value of PVD
PVD normally gets its value from RDBK. If the RDBK is Bad, PVD has the same value as OUT.
Use the invert input option in the upstream LSDI algorithm if you are using a closed limit switch.
Determining the value of DALRT
The DALRT parameter reports two alarm conditions set by the algorithm (inactive = 0, active = 1):
 Failed to confirm after trip command.
The device fails to confirm after being commanded to trip. On any transition of OUT to Off, the
algorithm starts a confirmation timer. If the value of PVD is not 0 within CTTM seconds, the
alert Failed to confirm after trip command becomes True. The alert clears when OUT
transitions to On (1).
 Confirm lost while commanded On.
The device confirms Off while it is being commanded On. When OSTAT is On and PVD has
transitioned to 1, the condition is detected if PVD becomes 0, for example if the device has a
failure that causes it to confirm in the Off state. The alert clears on the next transition of
OSTAT to On.
Partial stroke testing
Perform partial stroke testing of a DVC6000ESD in one of the following ways:

 Initiate a test from a workstation using the Advanced Tuning window on Signal Diagrams by a
SIS write to the PSSRT parameter in the LSDVC algorithm.
 Configure the LSDVC algorithm to periodically initiate the test based on the algorithm's PSPT
parameter.
Note: Do not attempt to initiate consecutive partial strok e tests from the logic unless you verify
that each test completes before initiating the next. Otherwise, the first test succeeds and
subsequent tests fail or are denied until the first test completes.
The partial stroke testing facility in the LSDVC algorithm is in one of three states as indicated in
the PSSTA parameter, whose state transition diagram is shown in the following figure.
Figure 32: PSSTA Transition diagram
OW351_R1100 805
8.14 LSDVC
The partial stroke testing state is Idle when the algorithm has not been configured to initiate tests
periodically, that is, PSPT is zero hours, and the algorithm is waiting for a manual test to be
initiated by PSSRT.
The state is Armed when PSPT is greater than zero and PSNTR is timing down. A test starts
when PSNTR reaches zero (times out), or if prior to timing out, a manual test is started.
The state transitions to PST in Progress when a test is started from Idle or Armed. The algorithm
sends a request to the IO subsystem to initiate a partial stroke test. The algorithm generates an
event based on whether the test was successful, failed, or denied. The state then transitions to
Armed or Idle based on the value of PSPT.
The PST events will be sent to the Ovation Process Historian as Module Events. For more
information on module events, refer to Ovation Safety Instrumented System (SIS) User Guide.
A partial stroke test can fail for a number of reasons:
 The DVC6000ESD returns a test failed response.

 The Logic Solver I/O processor is not in the Ready state when the algorithm requests a test.
 The Logic Solver I/O processor goes to the NoComm state after the t est is initiated.
 The Logic Solver control subsystem does not get a response from the Logic Solver I/O
processor for 180 seconds while PSSTA is PST In Progress.
When a partial stroke test fails, the algorithm sets the PSALR Test failed. The alert remains set
until the next time PSSTA is PST in Progress.
The partial stroke test can be denied by the DVC6000ESD when it is in some modes of operation;
for example, it is being calibrated or a test has been initiated from Valve link, or the connected
HART device does not support partial stroke testing. When a test is denied, the algorithm sets the
PSALR Test Denied, where it remains set until the next time PSSTA is PST in Progress.
When PSSTA is Armed or Idle, the algorithm compares the elapsed time since the last successful
test (PSSNT) to the maximum allowed time between successful tests (PSRIN) and sets the
PSALR No successful test in the required interval if the time has been exceeded (unless the
required interval is zero). PSSNT is set to zero after a test suc ceeds. PSSNT does not begin
incrementing after an initial load of the Logic Solver until a successful test has occurred.
A transition can occur between Idle and Armed when PSPT is written in runtime, or on the first
scan after a load if PSPT has changed. W hen the state is Idle, changing PSPT to a value greater
than zero causes the state to change to Armed and PSNTR to be initialized. When the state is
Armed, writing PSPT to zero changes the state to Idle. When Armed, a greater than zero write to
PSPT changes PSNTR to the value written to PSPT if that value is less than the current value of
PSNTR. PSNTR is decremented when the state is Armed.
When a load of the Logic Solver occurs where there is an existing configuration running, the
current state and timer values are copied from running LSDVC algorithms to retain the values.
Event Generation
The LSDVC algorithm generates a SIF Error or Module Event record when any of the following
conditions become active and the ROPx option "Event records are not generated" is not selected:
 The algorithm has set DALRT Failed to confirm following a command to trip.
 The algorithm has set DALRT to "Confirm lost while commanded On."
 The command to trip was successful and RDBK has been wired.
806 OW351_R1100
8.14 LSDVC
 The algorithm has set PSALR Test failed.

 The algorithm has set PSALR Test denied.
 The algorithm has set PSALR No successful test in the required interval.
 The partial stroke test is successful.
Quality Handling
Quality is considered in the detection of the fault state.
The quality of OUT is normally Good. If the fault state is active, the quality is Good. If the quality
on the output channel is Bad, the quality of OUT is set to Bad. Bad SensorFailure LowLimited
indicates an open or short circuit has been detected. Bad DeviceFailure NotLimited indicates a
channel error.
The quality of PVD is that of RDBK unless its quality is Bad, in which case the quality of PVD is
the same as OUT.
FI E L D RE C O R D
CASND X1 - Byte Variable Required - Input LD

RDBK X2 - Byte Variable Optional - Actual Element Feedback LD
Input
IOOUT - Data Init. Required CHxx HART 2-State I/O Output -
Channel
PVD X3 - Byte Variable Optional - Readback Value LD
OSTAT Y2 - Byte Variable Optional - Output Current State LA
0 = Off
1 = Off - Ready to Reset
2 = On
BLERR G2 - Variable Optional - Block Error Status LX
Integer  128 = Output Failure
 256 = Input Failure/ Bad
PV
 1024 = Fault State is
Active
FSTAT X5 - Byte Variable Optional - Fault State Status LA
 0 = Not Active
 1 = Active
DALRT G3 - Variable Optional - Alarm Conditions Set by LX
Integer Block
1 = Failed to Confirm after
trip command
2 = Confirm lost while
commanded On
CTTMR R2 - Real Variable Optional - Feedback Confirm Timer LA
FTMRH R3 - Real Variable Optional - Fault Detection Timer LA
(Hours)
OW351_R1100 807
8.14 LSDVC
FI E L D RE C O R D
PSSTA Y3 - Byte Variable Optional - PST State LA

PSALR G4 - Variable Optional - PST Alerts LX
Integer
PSNTR S1 - Real Variable Optional - Periodic PST Timer LA
PSSNT S2 - Real Variable Optional - Last Success PST Elapsed LA
Time
OUT X9 - Byte Variable Optional 0 Output Value -
CTTM R1 - Real Tunable Required 5 Output Feedback Time -
(sec)
Integer FaultDetectbyCASND
Bit 1 0=No
1=Yes
Integer FaultDetectbyOUTD
Bit 2 0=No
1=Yes
Integer FaultDetectbyPVD
Bit 3 0=No
1=Yes
FTIM R4 - Real Tunable Required 300 Fault Detection Delay Time -
(sec)
FTMR R5 - Real Variable Optional 0 Fault Detection Timer (sec) LA
ROP1 G1 - Tunable Required 0 Report Opt: NoRollUp -
Integer 0=False
Bit 0 1=True
ROP2 G1 - Tunable Required 0 Report Opt: -
Integer NoEventRecords
Bit 1 0=False
1=True
OFCUR X6 - Byte Tunable Required 0 Valve Controller Off -
Current
0=0 milliamps
1=4 milliamps
RST X7 - Byte Tunable Required 0 Reset -
Bit 0 0=False
1=True
RQRST X8 - Byte Tunable Required 0 Require Reset -
Bit 0 0=False
1=True
PSSRT X4 - Byte Tunable Required 0 Start On-Demand PST -
Bit 0 0=False
1=True
PSRIN R8 - Real Tunable Required 0 Required PST Interval (hrs) -
PSPT R7 - Real Tunable Required 0 Periodic PST Time (hrs) -
808 OW351_R1100
8.14 LSDVC
DALRT
The following table shows the alerts that can appear for an LSDVC algorithm and the bit position
of each alert.
Failed to confirm after trip command. 0

Confirm lost while commanded On. 1
PSALR
The following table shows the alerts that can appear for an LSDVC algorithm and the bit position
of each alert.
Bits
Last test denied. 0

No successful test in the required interval. 1
Last test failed. 2
Using output algorithms with the DVC6000ESD
The LSDVC algorithm provides an interface to the DVC6000ESD for safety shutdown and for
partial stroke testing. The HART Two-state Output Channel provides the control signal and the
HART communications path to the digital valve controller. You can configure the output channel
to have an OFCUR of 0 mA or 4 mA. The control signal can command the valve controller to the
tripped state regardless of the configured OFCUR value. Using an OFCUR value of 4 mA allows
HART communication between the Logic Solver and the valve controller whether the valve
controller is in the normal or the trip state. When the OFCUR is 0 mA, the power is removed
entirely when the LSDVC algorithm drives the channel Off.
CAUTION! Emerson recommends keeping the travel cutoffs in the DVC6000ESD (Travel
Cutoff High and Travel Cutoff Low) at their default value of 50%. Do not set Travel Cutoff Low
below 15% or set Travel Cutoff High above 85%.
OW351_R1100 809
8.14 LSDVC
Implementation Example
 Outfit the valve with a solenoid as shown in the figure below.
 Use two output channels on the Logic Solver, one configured as a Digital Output Channel and
one as HART Two-state Output Channel.
 Set the OFCUR parameter to 4 mA.
 Use two output algorithms in the SIS module, one LSDO and one LSDVC.
 Wire the EFFECTn output from the LSCEM algorithm to the CASND input on both algorithms.
Figure 33: Example implementation
An advantage of this implementation is HART communication is active whether the valve is in the
normal or trip state.
810 OW351_R1100
8.14 LSDVC
Alternate Implementation
 The DVC6000ESD is not outfitted with a solenoid valve.
 Use a single output channel configured as HART Two-state Output Channel.
 Set the OFCUR parameter to 0 mA.
 Use one output algorithm, an LSDVC algorithm, in the control module
 Wire the EFFECTx output from the LSCEM algorithm to the CASND input of the LSDVC
algorithm.
Figure 34: Alternate implementation
An advantage of this implementation is that only one output channel is required. The
disadvantage is not having HART communication when the DVC6000ESD is in the shutdown
state.
OW351_R1100 811
8.15 LSDVTR
8.15 LSDVTR
Description
The Logic Solver Digital Voter (LSDVTR) algorithm provides a digital voter function for safety
instrumented functions. A voter algorithm monitors a number of input values and determines if
there are enough votes to trip. The LSDVTR algorithm monitors as many as 16 digital inputs. If a
configured number of the inputs vote to trip, the algorithm trips and sets the output of the
algorithm to 0 (zero).
For example, a process shutdown might be required if a tank exceeds a certain temperature.
Three temperature sensors are installed in the tank and a digital voter algorithm is configured to
monitor the sensors and trip if two of the three transmitters detect a high temperature.
Because the Logic Solver is a De-energized to Trip environment, the normal operating value of
the output is 1 (On) and the tripped value is 0 (Off).
Functional Symbol
Algorithm Execution
The LSDVTR algorithm has one or more digital inputs with quality and one digital output with
quality. The algorithm examines each input to determine whether that input is a vote to trip the
output (change it from the normal operating value to the tripped value).
Basic Algorithm Operation
Voting in the Digital Voter algorithm is an M out of N function, that is, M inputs of the total N inputs
must vote to trip. For example, the algorithm can be configured as a 2 out of 3 voter, where two of
the three inputs must vote to trip before the output is tripped. The output of the algorithm is
typically wired to an LSCEM (Cause and Effect Matrix) algorithm, which interprets the value as
either a safe or dangerous process state.
The LSDVTR algorithm has three inputs by default. The number of inputs is extensible from 1 to
16. The M value corresponds to the parameter N2TRP (default value is 2). Common voting
schemes include 2 out of 3, 1 out of 2, and 2 out of 2. Other features of the algorithm make it
useful for single transmitter applications as a 1 out of 1 voter.
A vote to trip must remain a vote to trip for a configured time (TRDLY) before the output changes
to tripped. When the vote to trip clears, it must remain clear for NDLY before the output changes
to the normal state. The default for both delays is 0.0 seconds. The trip voting function has the
status parameter TRSTS that indicates the status of the trip vote.
812 OW351_R1100
8.15 LSDVTR
For example, the possible values for TRSTS are:

 Normal
 Tripped
 Voted to Trip, Delayed
 Voted Normal, Delayed.
 Trip Inhibited (when applicable)
Startup and Maintenance BYPx Options
You may also want to bypass inputs to allow for sensor maintenance. By default, you can bypass
only one input of the algorithm at a time. The bypassed input cannot vote to trip.
The following sections explain how to use the BOPx options to implement startup and
maintenance bypasses.
Bypassing Inputs
If you have voter algorithms with 1 out of 2 or 1 out of 1 voting schemes you may want the ability
to bypass inputs to allow for maintenance. Voters that require multiple votes to trip can benefit
from bypass functions as well, resulting in more predictable behavior during transmitter
maintenance. Default algorithm behavior requires that BPERM be true to bypass inputs. You can
configure BPERM to be set by a display button or physical switch (digital input to the SIS module).
If your application does not require permission before inputs can be bypassed you can select the
BOPx option "Bypass permit is not required to bypass."
Reducing the Number to Trip
By default, an algorithm configured as an M out of N voter becomes an M out of (N-1) algorithm (a

2 out of 3 voter becomes a 2 out of 2 voter) when an input is bypassed because the bypassed
input cannot vote to trip. Selecting the BOPx option "A maintenance bypass reduces the number
to trip" causes an M out of N voter to become an (M-1) out of (N-1) voter (reduces the number
required to trip by one when an input is bypassed).
OW351_R1100 813
8.15 LSDVTR
The following table shows the effect the BOPx option "A maintenance bypass reduces the number
to trip" has on the actual number to trip (ANTRP) for several voting schemes. Note that in no case
is ANTRP less than one.
Effects
C O N F I G U R E D V O TI N G BOP X O P TI O N - A MAI N TE N AN C E B YP AS S R E D U C E S TH E N U MB E R
S C H E ME TO TR I P .
T H E O P TI O N I S N O T S E L E C TE D . T H E O P TI O N I S S E L E C TE D .
(U S E S C O N F I G U R E D N2 TRP) (RE D U C E S ANTRP)

2 out of 2 Trip Inhibited 1 out of 1
1 out of 1 Trip Inhibited Trip Inhibited
814 OW351_R1100
8.15 LSDVTR
Allowing Multiple Bypasses
If your application requires, you can enable bypassing multiple inputs simultaneously by selecting
the BOPx option "Multiple maintenance bypasses are allowed."
If multiple bypasses are set, deselecting the BOPx option "Multiple maintenance bypasses are
allowed" prevents further bypasses being set but existing bypasses remain set. Additional
bypasses cannot be set until all existing bypasses are cleared.
Maintenance Bypass Timeout
You can configure a maintenance bypass to be active for a finite time using BTOUT. Its default
value is 0.0 seconds, which means no timeout is applied (maintenance bypasses remain active
until BYPx parameters become False, either by changing True BYPx parameters to False or
changing BPERM to False).
When BTOUT is non-zero, BTMR is preset to BTOUT seconds when the first BYPx parameter
becomes True (not when BPERM becomes True). Each module scan thereafter BTMR is
decremented until it times out (unless all BYPx parameters become False, in which case the
algorithm resets BTMR to 0.0). The smallest possible configured time for BTOUT parameter is
0.05 seconds. This value must be multiple of 0.05 seconds or it will be rounded off to its nearest
multiple.
BTMR is common to all inputs. The value of BTMR does not change when a second BYP x
parameter is changed to True (if multiple bypasses are allowed). When BTMR times out, the
algorithm default behavior changes all True BYPx parameters to False. If you use bypass
timeouts, do not expose BYPx parameters as algorithm inputs and wire to them. Doing so will
prevent the algorithm from removing bypasses upon timeout.
Optionally, you can use the bypass timer for indication only by selecting the BOPx option
"Maintenance bypass timeout is for indication only." This causes the timeout of BTMR to activate
a notification alarm (DALRT Expiration Reminder), but does not undo bypasses.
Bypass Timeout Reminder
You can configure the algorithm to remind operators that a bypass timeout is imminent. By
default, the algorithm does not notify. There are two ways you can cause a notification:
 For bypasses with a configured timeout, you can cause notification in advance of the timeout
by setting RMTIM to a non-zero value. When BTMR is non-zero but less than or equal to
RMTIM, the alarm condition DALRT Expiration Reminder is active.
The bypass timer is re-armed only after the first bypass. However, BTMR is a writeable
parameter. After notification that a timeout is about to happen, BTMR can be incremented
using a display button or some other suitable technique to extend the time.
OW351_R1100 815
8.15 LSDVTR
 A second approach is available when you are using the bypass timeout for indication only,
that is, bypasses are not removed when BTMR expires (the BOPx option "Maintenance
bypass timeout is for indication only" is selected). In this case the reminder alarm condition
becomes active when BTMR times out even if RMTIM is 0.0. If RMTIM is non-zero, the
reminder occurs prior to timeout. If BTMR times out, the reminder is active and remains active
until all bypasses have been removed.
The following table describes the behavior of the bypass timeout and reminder function for three
different configuration setups.
Maintenance Bypass Timeout and Reminder Function Behavior
C O N D I TI O N BTOUT AN D BOP X C O N F I G U R ATI O N
BTOUT = 0 .0 BTOUT > 0 .0 AN D TH E BTOUT > 0 .0 AN D

( N O TI ME O U T ) BOP X O P TI O N TH E BOP X O P TI O N
" M AI N TE N AN C E B YP AS S " M AI N TE N AN C E
TI ME O U T I S F O R I N D I C ATI O N B YP AS S TI ME O U T IS
O N L Y" I S N O T S E L E C TE D F O R I N D I C ATI O N
(BYP X R E MO V E D O N O N L Y" I S S E L E C TE D
TI ME O U T ) ( TI ME O U T F OR
I N D I C ATI O N O N L Y)
BPERM changes to BTMR stays 0.0 BTMR stays 0.0 BTMR stays 0.0
True
First input is BTMR stays 0.0 BTMR = BTOUT s econds and BTMR = BTOUT
bypassed (BYPx begins timing down seconds and begins
changes to True) timing down
Second input is BTMR stays 0.0 BTMR continues timing down BTMR continues timing
bypassed down
(assuming the
BOPx option
"Multiple
maintenance
bypasses are
allowed" is
selected).
BTMR > RMTIM N/A No reminder No reminder
BTMR <= RMTIM No reminder Reminder alarm condition is Reminder alarm
active condition is active
Bypass timer times N/A The algorithm changes all BYPx Reminder alarm
out parameters to False. Reminder condition remains active
alarm condition clears on the until all bypasses are
following scan. removed manually.
816 OW351_R1100
8.15 LSDVTR
Startup Bypass Trip Inhibit
This startup bypass allows the process to reach normal operating conditions without tripping. Use
the STUP parameter and associated parameters for startup bypasses. Do not use maintenance
overrides for this purpose.
Timed Startup Bypass (the BOPx option "Startup bypass duration is event-based" is not
selected)
On a rising edge of the STUP parameter, the algorithm forces OUT to the normal state value for a
configurable length of time defined by SUTM. When the countdown timer SUTMR times out, the
algorithm resumes normal trip detection. The default behavior of the algorithm is such that a
subsequent rising edge of STUP does not affect the startup time while SUTMR is timing down. To
avoid a pending trip on timeout, you can allow each rising edge of STUP to re-arm SUTMR (by
selecting the BOPx option "Startup bypass preset is allowed while active").
A reminder becomes available to STUP bypasses by selecting the BOP x option "Reminder
applies to startup bypass." When SUTMR is greater than 0.0 but less than RMTIM the reminder
alarm condition (DALRT Expiration Reminder) is active. The reminder alarm condition is common
to the timeout of maintenance and startup bypasses.
Another option is to have the startup timer expire when inputs have stabilized, that is, when there
have not been enough votes to trip for a configurable period of time. When the BOP x option
"Startup bypass expires upon stabilization" is selected, the bypass timer expires when the
process stabilizes. While SUTMR is timing down, STMR times up whenever there are not enough
votes to trip and resets whenever the trip votes equal or exceed the number required to trip.
If STMR reaches the configured STM, SUTMR resets to 0.0 and normal trip detection resumes.
While SUTMR is timing down, the algorithm increments T2STB and stops as soon as the STMR
is triggered. T2STB indicates the total number of seconds during the startup bypass until the
inputs become and remain stable (assuming SUTM is sufficiently long).
STMR does not reset at the end of the startup time period, but is reset at the beginning of a
startup and at any time during the startup when there are enough trip votes. T2STB is reset at the
beginning of a startup bypass. STMR and T2STB are processed even when the stabilization
option is not used (the BOPx option "Startup bypass expires upon stabilization" is not selected).
You can use the value of T2STB to optimize the configured SUTM.
Event-Based Startup Bypass (the BOPx option "Startup bypass duration is event-based" is
selected)
When the startup bypass expires based on an event rather than a fixed time period, select the
BOPx option "Startup bypass duration is event based." This ends the startup bypass when the
STUP parameter becomes False. STMR and T2STB are not processed. They are set to 0.0 when
STUP becomes True.
Bypass Permit Control
When the BOPx option "Bypass permit control should be visible in operator interface" is selected,
the algorithm faceplate contains a button which operators can use to set BPERM. Do not select
this option if logic in the SIS module is writing to BPERM (for example, a keyswitch is used to
permit bypassing).
OW351_R1100 817
8.15 LSDVTR
The following table summarizes the BOPx options and their effects.
BOPx parameter options
O P TI O N W H E N O P TI O N IS S E L E C TE D W H E N O P TI O N IS N OT
S E L E C TE D
A maintenance bypass An M out of N voter becomes an (M- An M out of N voter becomes an M

reduces the number to 1) out of (N-1) voter (number required out of (N-1) voter when an input is
trip. (BOP1 - to trip by is reduced by one) when an bypassed.
MaintBypRed) input is bypassed.
Multiple maintenance You can bypass multiple inputs at the Only one input can be bypassed at
bypasses are allowed. same time. a time.
(BOP2 -
MulBypAllowed)
Maintenance bypass When BTMR times out DALRT When BTMR times out DALRT
timeout is for indication Bypass Active remains set and input Bypass Active clears and all
only. bypasses remain in effect. bypasses are cleared.
(BOP3 - IndicateOnly)
Startup bypass preset is Each time STUP is set to True, SUTMR is not reset.
allowed while active. SUTMR is reset to the configured
(BOP4 - ReArmAllowed) value of SUTM.
Startup bypass expires Startup bypass and SUTMR clear if Startup bypass ends when SUTMR
upon stabilization. STMR reaches STM (after there are reaches 0 (zero).
(BOP5 - BypExpires) not enough votes to trip for the
configured amount of time).
Reminder applies to When SUTMR is greater than 0.0 but DALRT Expiration Reminder does
startup bypass. less than RMTIM, the DALRT not apply to startup bypass.
(BOP6 - Expiration Rem inder is set. The
ReminderApplies) reminder alarm condition is common
to maintenance and startup bypass
timeouts.
Startup bypass duration Startup bypass expires only when Startup bypass is time based.
is event-based. STUP becomes False. STMR and
(BOP7 - BypDurEvent) T2STB are not processed.
Bypass permit is not BPERM does not need to be set to BPERM must be set to True for
required to bypass. True for inputs to be bypassed. inputs to be bypassed.
(BOP8 - PermitNotReq)
Bypass permit control Bypass permit controls appear in the Bypass permit controls do not
should be visible in standard LSDVTR faceplate. Do not appear in the standard LSDVTR
operator interface. select this option if SIS module logic faceplate.
(BOP9 - BypPerVisible) writes to BPERM (for example,
bypass permitting is done using a
keyswitch)
818 OW351_R1100
8.15 LSDVTR
Quality Handling
The quality of the inputs influences algorithm behavior based on how the SOPT parameter is
configured. The three choices of SOPT are:
 Always Use Value — The value of the input is always used regardless of quality. In this way a
hardware failure does not necessarily cause a shutdown and time is allowed for repair.
Detected hardware failures are indicated by standard alarms on the Logic Solver card. This is
the default option.
 Will Not Vote if Bad — The input value is not counted as a vote to trip if its quality is Bad.
 Vote to Trip if Bad — The input value is counted as a vote to trip if the input quality is Bad.
The following table shows how several common voting schemes degrade when a single input has
bad quality based on the option chosen for SOPT.
Schemes
O R I G I N AL RE S U L TI N G V O TI N G S C H E ME F OR SOPT V AL U E S
V O TI N G S C H E ME
AL W AYS US E V AL U E 1 W I L L NO T V O TE IF V O TE TO TR I P IF BAD
BAD
2 out of 3 2 out of 3 or 1 out of 2 2 out of 2 1 out of 2

2 out of 2 2 out of 2 or 1 out of 1 Will Not Vote if Bad 1 out of 1
1 out of 2 1 out of 2 or Tripped 1 out of 1 Tripped
1 out of 1 1 out of 1 or Tripped Trip Inhibited Tripped
1 The degraded voting scheme depends on the value of the input with Bad quality.
The LSDVTR algorithm determines the quality of OUT the same way no matter which quality
option is chosen. The quality calculation is completely separate from the value calculation.
The quality of OUT is Good if the number of non-bypassed inputs with Good quality is greater
than or equal to ANTRP or all inputs are bypassed; otherwise, the quality is Bad. Uncertain quality
on inputs is treated as Good.
When any input has Bad quality, the DALRT Input Bad bec omes active.
OW351_R1100 819
8.15 LSDVTR
TRSTS Indication
The TRSTS parameter indicates the state of the trip vote functions. The typical value for TRSTS
is Normal, and less commonly, Tripped. As shown in the following figure, TRSTS can be delayed
when TRDLY or NDLY is non-zero and a transition is occurring between normal and tripped
states.
A fifth state, Trip Inhibited, occurs whenever a startup bypass is active or when it is not possible to
trip because there are not enough inputs participating in voting. The latter case can occur when
inputs are bypassed or when inputs have bad quality and SOPT selected is Trip inhibited.
The solid lines in the figure show the common state transitions of TRSTS expected as the
process value moves above and below the trip point. The dashed lines show less common state
transitions.
Figure 35: State diagram for TRSTS
FI E L D RE C O R D
NOFIN Y0 - Byte Data Init. Required 1 Number of Inputs -

IN1 G3 - Integer Variable Required - Input 1 LD
Bit 0
IN2 G3 - Integer Variable Optional - Input 2 LD
Bit 1
820 OW351_R1100
8.15 LSDVTR
FI E L D RE C O R D

Bit 2
Bit 3
Bit 4
Bit 5
Bit 6
Bit 7
Bit 8
Bit 9
Bit 10
Bit 11
Bit 12
Bit 13
Bit 14
Bit 15
OUTNB X3 - Byte Variable Optional - Output with No LD
Bypass
OW351_R1100 821
8.15 LSDVTR
FI E L D RE C O R D

ANTRP X6 - Byte Variable Optional - Actual Votes LA
Needed to Trip
BTMRH R3 - Real Variable Optional - Bypass Countdown LA
Timer (hrs)
DLYTM R4 - Real Variable Optional - Countdown Timer LA
for Delay
DALRT G5 - Integer Variable Optional - Alarm Conditions LX
Set by algorithm.
 1 = Trip Active
 4 = Bypass Active
 8 = Startup
Override Active
 32 = Expiration
Reminder
 128 = Bypassed
Input Tripped
 256 = Input Bad
STMR R5 - Real Variable Optional - Startup No-Vote-to- LA
Trip Timer
SUTMR R6 - Real Variable Optional - Startup Inhibit LA
Timer in seconds.
T2STB R7 - Real Variable Optional - Time to Stable in LA
seconds.
822 OW351_R1100
8.15 LSDVTR
FI E L D RE C O R D
TRSTS X7 - Byte Variable Optional - Trip Status LA

Indicator
0 = Normal
1 = Tripped
2 = Trip Inhibited
3 = Voted to Trip -
Delayed
4 = Voted Normal -
Delayed
TRPVT X8 - Byte Variable Optional - Num of Inputs LA
Voted-to-Trip
Bit 0 MaintBypRed
0=False
1=True
Bit 1 MulBypAllowed
0=False
1=True
Bit 2 IndicateOnly
0=False
1=True
Bit 3 ReArmAllowed
0=False
1=True
Bit 4 BypExpires
0=False
1=True
Bit 5 ReminderApplies
0=False
1=True
Bit 6 BypDurEvent
0=False
1=True
Bit 7 PermitNotReq
0=False
1=True
Bit 8 BypPerVisible
0=False
1=True
OW351_R1100 823
8.15 LSDVTR
FI E L D RE C O R D
BYP1 C0 - Integer Selectable Optional 0 Voting Bypass for LD

Input 1
0=No
1=Yes
Input 2
0=No
1=Yes
Input 3
0=No
1=Yes
Input 4
0=No
1=Yes
Input 5
0=No
1=Yes
Input 6
0=No
1=Yes
Input 7
0=No
1=Yes
Input 8
0=No
1=Yes
Input 9
0=No
1=Yes
BYP10 YT - Integer Selectable Optional 0 Voting Bypass for LD
Input 10
0=No
1=Yes
BYP11 DO - Integer Selectable Optional 0 Voting Bypass for LD
Input 11
0=No
1=Yes
BYP12 YQ - Integer Selectable Optional 0 Voting Bypass for LD
Input 12
0=No
1=Yes
824 OW351_R1100
8.15 LSDVTR
FI E L D RE C O R D
BYP13 D2 - Integer Selectable Optional 0 Voting Bypass for LD

Input 13
0=No
1=Yes
BYP14 YP - Integer Selectable Optional 0 Voting Bypass for LD
Input 14
0=No
1=Yes
Input 15
0=No
1=Yes
Input 16
0=No
1=Yes
BPERM X2 - Byte Selectable Optional 0 Permit Input LD

Bypass 0=No
1=Yes
BTOUT R1 - Real Tunable Required 0.0 Input Bypass Reset -
Timeout (sec)
BTMR R2 - Real Data Init. Required 0.0 Bypass Countdown -
Timer (sec)
NDLY S4 - Real Tunable Required 0 Output Reset Delay -
(sec)
N2TRP X4 - Byte Tunable Required 2 Votes Needed to -
Trip
DI1 - Data Init Optional VOTER1 Description Voter 1 -
For Control
Builder/Signal
Diagram
applications use
only
For Control
Builder/Signal
Diagram
applications use
only
For Control
Builder/Signal
Diagram
applications use
only.
OW351_R1100 825
8.15 LSDVTR
FI E L D RE C O R D

For Control
Builder/Signal
Diagram
applications use
only
For Control
Builder/Signal
Diagram
applications use
only

For Control
Builder/Signal
Diagram
applications use
only
For Control
Builder/Signal
Diagram
applications use
only
For Control
Builder/Signal
Diagram
applications use
only
For Control
Builder/Signal
Diagram
applications use
only
DI10 - Data Init Optional VOTER10 Description Voter -
10
For Control
Builder/Signal
Diagram
applications use
only
826 OW351_R1100
8.15 LSDVTR
FI E L D RE C O R D

11
For Control
Builder/Signal
Diagram
applications use
only
12
For Control
Builder/Signal
Diagram
applications use
only
13
For Control
Builder/Signal
Diagram
applications use
only
14
For Control
Builder/Signal
Diagram
applications use
only
15
For Control
Builder/Signal
Diagram
applications use
only
16
For Control
Builder/Signal
Diagram
applications use
only
RMTIM S5 - Real Tunable Required 0 Reminder Alarm -
Duration (sec)
Bit 0 NoRollUp
0=False
1=True
OW351_R1100 827
8.15 LSDVTR
FI E L D RE C O R D

0=False
1=True
STM S6 - Real Tunable Required 0 Process -
Stabilization Time
(sec)
STUP X5 - Byte Selectable Optional 0 Inhibit Startup Trip LD
Detection
0=No
1=Yes
SUTM S8 - Real Tunable Required 0 Startup Inhibit -
Duration (sec)
SOPT Y5 - Byte Tunable Required 0 Status Options if -
Bad Input
0=Always Use
Value 1=Will Not
Vote if Bad
2=Vote to trip if Bad
TRDLY T2 - Real Tunable Required 0 Trip Delay (sec) -
DALRT
The following table shows the alerts that can appear for an LSDVTR algorithm, an explanation of
each alert, and the bit position of each alert.
The following LSDVRT alerts will be sent to the Ovation Process Historian as SIF Alerts. For more
information on SIF Alerts, refer to Ovation Safety Instrumented System (SIS) User Guide.
Bit description
Trip Active Inactive when OUT is in the normal operating state, 0

active when OUT is in the trip state.
Bypass Active Active when there is a maintenance bypass on any 2
input (any BYPx parameter is True).
Startup Override Active Active whenever the startup bypass is active. 3
Expiration Reminder Active when either a maintenance bypass or a startup 5
bypass is about to expire.
Bypassed Input Tripped Active if one or more bypassed inputs have exceeded 7
the trip limit.
Input Bad Active if any input has bad quality. 8
828 OW351_R1100
8.16 LSLIM
8.16 LSLIM
Description
The Logic Solver Limit (LSLIM) algorithm limits an input value between two reference values. The
algorithm has options that set the output to a default value or the last value if the input becomes
out of range.
IN is the analog input value and quality.
OUT is the analog output value and quality.
LMIND is set True (1) when the input is limited to the OHLIM value. It remains True until the input
is limited to the OLLIM value, at which time it is set False (0). It remains False until the input is
again limited to the OHLIM value.
OUTLA is a Boolean value set True when the input is limited t o the minimum value.
OUTHA is a Boolean value set True when the input is limited to the maximum value.
If the LMOPT option is CLAMP, then OUT is set to either OHLIM or OLLIM when there is a
corresponding limit violation.
You can use other LMOPT options instead of passing the clamped value to the output. If the
UseLast option is set then the output is set to the last output when the high or low limit is
exceeded. If the UseDefault option is set then the output is set to the DEFLT parameter value.
Functional Symbol
OW351_R1100 829
8.16 LSLIM
Algorithm Execution
The LSLIM algorithm restricts the output value between a high limit and a low limit. When IN is
less than or equal to the configured minimum value (OLLIM), OUT equals OLLIM and OUTLA is
set True.
When IN is greater than or equal to the configured maximum value (OHLIM), OUT equals OHLIM
and OUTHA is set True.
When the value is within the limits, OUTHA and OUTLA are set False.
When IN becomes greater than or equal to OHLIM, LMIND is set True.
When IN becomes less than or equal to OLLIM, LMIND is set False.
If the LMOPT option is CLAMP, then OUT is set to either OHLIM or OLLIM when there is a
corresponding limit violation.
You can use other LMOPT options instead of passing the c lamped value to the output. If the
UseLast option is set then the output is set to the last output when the high or low limit is
exceeded. If the UseDefault option is set then the output is set to the DEFLT parameter value.
The following table shows an example of the Limit algorithm outputs when OLLIM = 5 and
OHLIM = 90:
LSLIM algorithm execution example
IN OUT OUTLA OUTHA LMIND
0 5 True False False

5 5 True False False
50 50 False False Equal to the previous value
90 90 False True True
100 90 False True True
830 OW351_R1100
8.16 LSLIM
Quality Handling
The quality of the outputs (OUT, OUTHA, and OUTLA) are set to the input quality. The quality of
LMIND is always Good.
N AME LC AL G . T YP E RE Q U I R E D / DE F AU L T D E S C R I P TI O N MI N . POI N T
RE C O R D O P TI O N AL V AL U E RE C O R D
FI E L D
IN R4 - Real Variable Required - Input LA

OUT R5 - Real Variable Required - Output LA
OUTLA X2 - Byte Variable Optional - Low-Limited Input LD
Status
OUTHA X3 - Byte Variable Optional - High-Limited Input LD
Status
LMIND X4 - Byte Variable Optional - Hi-Low Limit LD
Indicator
OLLIM R3 - Real Tunable Required 0 Min Output Value -
Allowed
OHLIM R2 - Real Tunable Required 100 Max Output Value -
Allowed
LMOPT X1 - Byte Tunable Required 1 Limit Options -
1=Clamp
2=UseLast
3=UseDefault
DEFLT R1 - Real Tunable Required 0 Output Default -
value
OW351_R1100 831
8.17 LSMID
8.17 LSMID
Description
The Logic Solver Mid Selector (LSMID) algorithm selects the mid-valued input from multiple
analog signals. This algorithm selects only from those inputs that are not bad. When there is an
even number of inputs, the average of the two middle valued inputs is used as the OUT value and
SEL is the number of the lowest-valued input of the two that are averaged.
Functional Symbol
Algorithm Execution
This algorithm selects the mid-valued input from those inputs that are not bad from as many as 16
inputs. When the algorithm has an odd number of inputs, OUT is the value of the selected input
and SEL is the number of the selected input. When the algorithm has an even number of inputs,
OUT is the average of the two mid-valued inputs and SEL is the number of the lowest-valued
input of the two mid-valued inputs. For example, an algorithm has the following inputs:
 IN1 = 17
 IN2 = 20
 IN3 = 19
 IN4 = 66
In this example OUT is equal to 19.5 (the average of IN2 and IN3) and SEL is 3 (IN3 is 19, the
least-valued of the two mid-valued inputs).
Alarm Detection
This algorithm calculates a DVACT parameter that can be used for alarming. This parameter is
True if one or more of the inputs used in the selection process is farther than DVLIM away from
the middle signal. A DVHYS parameter is used when DVACT is set for the calculation of when the
alarm has cleared.
832 OW351_R1100
8.17 LSMID
Quality Handling
Typically (see exceptions below), when an input is selected, the quality of OUT and SEL are set
to the quality of the selected input.
 Quality Use And Propagation

 A bad input is never used.
 Any input which has poor quality will be used.
 If three I/P LSMID algorithms are used and all three I/Ps are BAD (the number of poor or
good quality inputs is zero), then BAD quality is propagated to OUT and GOOD quality is
propagated to SEL.
 If three I/P LSMID algorithms are used and all three I/Ps are FAIR (the number of poor or
good quality inputs is zero indicating the inputs are forced), then POOR quality is
propagated to OUT and GOOD quality is propagated to SEL.
 Limit Status Propagation
 If an even number of inputs used by the algorithm: propagate not limited, unless both
inputs have the same limit status, in which case propagate that limit status.
FI E L D RE C O R D

OUT T3 - Real Variable Required - Calculated / LA
Selected Output
SEL X1 - Byte Variable Optional - Number of Selected LA
Input
OW351_R1100 833
8.17 LSMID
FI E L D RE C O R D
DVACT X2 - Byte Variable Optional - Input Deviation LD

Status
DIS1 G0 - Selectable Optional 0 Disable Input 1 LD
Integer 0=No
1=Yes
Integer 0=No
1=Yes
Integer 0=No
1=Yes
Integer 0=No
1=Yes
Integer 0=No
1=Yes
Integer 0=No
1=Yes
Integer 0=No
1=Yes
Integer 0=No
1=Yes
Integer 0=No
1=Yes
Integer 0=No
1=Yes
DIS11 B0 - Selectable Optional 0 Disable Input 11 LD
Integer 0=No
1=Yes
Integer 0=No
1=Yes
Integer 0=No
1=Yes
DIS14 YU - Selectable Optional 0 Disable Input 14 LD
Integer 0=No
1=Yes
Integer 0=No
1=Yes
834 OW351_R1100
8.17 LSMID
FI E L D RE C O R D

Integer 0=No
1=Yes
DVHYS S8 - Real Tunable Required 0 Dev Status Reset -
Hysteresis
DVLIM S9 - Real Tunable Required 0 MID Deviation Limit -
Value
TPSC T1 - Real Tunable Required 100 Input Scale: Top -
BTSC T2 - Real Tunable Required 0 Input Scale: Bottom -
SCDML Y5 - Byte Tunable Required 1 Input Scale: Decimal -
Places
OW351_R1100 835
8.18 LSNAND
8.18 LSNAND
Description
The Logic Solver Not AND (LSNAND) algorithm generates a digital output value based on
inverting the logical AND of two to 16 digital inputs. The algorithm supports signal quality
propagation.
Functional Symbol
Algorithm Execution
The number of inputs to the LSNAND algorithm is an extensible parameter. The algorithm default
is two inputs. Use the Control Builder (see Ovation Control Builder User Guide) to add additional
input pins.
The LSNAND algorithm examines the inputs you define and applies the logical AND function to
the inputs, then applies the logical NOT function. When all inputs are True (1), the output is False.
When one or more of the inputs is False (0), the output is True.
Quality Handling
The output quality is set to the worst quality among the selected inputs unless at least one input is
False and its quality is not Bad. When this is the case, the output quality is set to GOOD.
FI E L D RE C O R D

Bit 0
Bit 1
Bit 2
Bit 3
836 OW351_R1100
8.18 LSNAND
FI E L D RE C O R D

Bit 4
Bit 5
Bit 6
Bit 7
Bit 8
Bit 9
Bit 10
Bit 11
Bit 12
Bit 13
Bit 14
Bit 15
OW351_R1100 837
8.19 LSNDE
8.19 LSNDE
Description
The Logic Solver Negative Edge Detect Trigger (LSNDE) algorithm generates a True (1) digital
output when the digital input makes a negative (True-to-False) transition since the last execution
of the algorithm. If there has been no transition, the digital output of the algorithm is False (0).
The LSNDE algorithm supports signal quality propagation.
IN is the digital input value and quality.
Functional Symbol
Algorithm Execution
The LSNDE algorithm is used to trigger other logical events based on the falling transition of a
logical signal. If the input value has changed from True to False since the algorithm was last
executed, the output of the algorithm is set True. If the value has not changed from True to False,
the algorithm output is set False. The following figure shows how the LSNDE algorithm responds
to a change in input:
Figure 36: LSNDE algorithm execution example
838 OW351_R1100
8.19 LSNDE
Quality Handling
FI E L D RE C O R D

OW351_R1100 839
8.20 LSNOR
8.20 LSNOR
Description
The Logic Solver Not OR (LSNOR) algorithm generates a digital output value based on inverting
the logical OR of two to 16 digital inputs. When one or more of the inputs is True (1), the output is
set to False.
The algorithm supports signal quality propagation.
Functional Symbol
Algorithm Execution
The number of inputs to the LSNOR algorithm is an extensible paramet er. The algorithm default is
input pins.
When one or more of the inputs is True (1), the output is set to False. Otherwise, the output is set
to True.
Quality Handling
The output quality is set to the worst among the input quality. However, when at least one input is
True and its quality is not Bad, the output quality is set to Good.
FI E L D RE C O R D

G0 - Variable
IN1 Integer Required - Input 1 LD
Bit 0
G0 - Variable
IN2 Integer Required - Input 2 LD
Bit 1
G0 - Variable
IN3 Integer Optional - Input 3 LD
Bit 2
840 OW351_R1100
8.20 LSNOR
FI E L D RE C O R D
G0 - Variable
Bit 3
G0 - Variable
Bit 4
G0 - Variable
Bit 5
G0 - Variable
Bit 6
G0 - Variable
Bit 7
G0 - Variable
Bit 8
G0 - Variable
Bit 9
G0 - Variable
Bit 10
G0 - Variable
Bit 11
G0 - Variable
Bit 12
G0 - Variable
Bit 13
G0 - Variable
Bit 14
G0 - Variable
Bit 15
OW351_R1100 841
8.21 LSNOT
8.21 LSNOT
Description
The Logic Solver NOT (LSNOT) algorithm logically inverts a digital input signal and generates a
digital output value. When the input is True (1), the output is False (0). When the input is False,
the output is True.
Functional Symbol
Algorithm Execution
The LSNOT algorithm generates an output value that is the logical NOT of its input. When the
input is False, the output is True. When the input is True (1), the output is False.
Quality Handling
FI E L D RE C O R D

842 OW351_R1100
8.22 LSOFFD
8.22 LSOFFD
Description
The Logic Solver Off Delay Timer (LSOFFD) algorithm delays the transfer of a False (0) digital
input value to the output by a specified time period. The algorithm supports signal quality
propagation.
IN is the digital input value and quality used to trigger the timed digital output value.
The Off-Delay Timer algorithm immediately transfers the digital input value (IN) to the output
(OUT) and resets the ETIME when IN is True (1). When IN transitions to False (0), OUT is reset
to False after a specified time period (TIMED). During this time period, ETIME tracks the time
starting when IN transitions to False until the time specified by TIMED expires.
Functional Symbol
Algorithm Execution
The following figure shows the timed response of the Off-Delay Timer algorithm.
Figure 37: LSOFFD algorithm timing diagram
OW351_R1100 843
8.22 LSOFFD
When IN is True, OUT is set True and the elapsed time counter (ETIME) is set to zero. When IN
is False for longer than TIMED, OUT is set False.
Quality Handling
FI E L D RE C O R D
IN X1 - Byte Variable Required - Input Trigger LD

ETIME R1 - Real Variable Optional - Elapsed Timer (sec) LA
Tunable Required Output Reaction Tim e
TIMED R2 - Real 2 -
Delay (sec)
844 OW351_R1100
8.23 LSOND
8.23 LSOND
Description
The Logic Solver On Delay Timer (LSOND) algorithm delays the transfer of a True (1) digital input
value to the output by a specified time period. The algorithm supports signal quality propagation.
IN is the digital input value and quality used to trigger the timed digital output value.
The On-Delay Timer algorithm immediately transfers the digital input value (IN) to OUT and resets
the ETIME when IN is False. When IN transitions to True, OUT is set True after a configured time
period (TIMED). During this time period, ETIME tracks the time starting when IN transitions to
True until the time specified by TIMED expires.
Functional Symbol
Algorithm Execution
The following figure shows the timed response of the LSOND algorithm.
Figure 38: LSOND algorithm timing diagram
When IN is False, OUT is set False and the elapsed time counter (ETIME) is set to zero. When IN
is True longer than TIMED, OUT is set True.
OW351_R1100 845
8.23 LSOND
Quality Handling
FI E L D RE C O R D

ETIME R1 - Real Variable Optional - Elapsed Timer (sec) LA
TIMED R2 - Real Tunable Required 2 Output Reaction -
Time Delay (sec)
846 OW351_R1100
8.24 LSOR
8.24 LSOR
Description
The Logic Solver OR (LSOR) algorithm generates a digital output value based on the logical OR
of two to 16 digital inputs. When one or more of the inputs is True (1), the output is set to True.
Functional Symbol
Algorithm Execution
The number of inputs to the LSOR algorithm is an extensible parameter. The algorithm default is
input pins. When one or more of the inputs is True (1), the output is set to True. Otherwise, the
output is set to False.
Quality Handling
The output quality is set to the worst among the input qualities. However, when at least one input
is True and its quality is not Bad, the output quality is set to GOOD.
FI E L D RE C O R D

G0 - Variable Required
IN1 Integer - Input 1 LD
Bit 0
G0 - Variable Required
Bit 1
G0 - Variable Optional
Bit 2
Bit 3
OW351_R1100 847
8.24 LSOR
FI E L D RE C O R D
Bit 4
Bit 5
Bit 6
Bit 7
Bit 8
Bit 9
Bit 10
Bit 11
Bit 12
Bit 13
Bit 14
Bit 15
848 OW351_R1100
8.25 LSPDE
8.25 LSPDE
Description
The Logic Solver Positive Edge Trigger (LSPDE) algorithm generates a True (1) digital output
when the digital input makes a positive (False-to-True) transition since the last execution of the
algorithm. If there has been no transition, the digital output of the algorithm is False (0).
The LSPDE algorithm supports signal quality propagation.
Functional Symbol
Algorithm Execution
Use the LSPDE algorithm to trigger other logical events based on the rising transit ion of a logical
signal. If the input value has changed from False to True since the algorithm was last executed,
the output of the algorithm is set True. Otherwise, the output is False. The following drawing
shows how the Positive Edge Trigger algorithm responds to a change in input:
Figure 39: LSPDE algorithm execution example
OW351_R1100 849
8.25 LSPDE
Quality Handling
FI E L D RE C O R D

850 OW351_R1100
8.26 LSRET
8.26 LSRET
Description
The LSRET algorithm generates a True (1) digital output after the input has been True for a
specified time period. The time for which the input has been True and the output value are reset
only when the reset input is set True.
IN is the digital input value and quality to be timed.
RST is the digital input value and quality used to reset OUT and ETIME.
Functional Symbol
Algorithm Execution
The algorithm output (OUT) is set True when the input (IN) has been True for a specified time
period (TIMED) while the RST input is False (0). When the RST input is False and the IN value
transitions to False, the ETIME stops and retains its value until IN transitions to True again. When
the RST value transitions to True, the ETIME is reset to zero and OUT is set False.
The following figure shows the timed response of the Retentive Timer algorithm.
Figure 40: LSRET algorithm timing diagram
OW351_R1100 851
8.26 LSRET
Quality Handling
The output quality is set to Good.
FI E L D RE C O R D

RST X2 - Byte Variable Required - Reset In LD
Variable Optional Elapsed Timer
ETIME R1 - Real - LA
(sec)
Tunable Required Output Reaction
TIMED R2 - Real 2 -
Time Delay (sec)
852 OW351_R1100
8.27 LSRS
8.27 LSRS
Description
The Logic Solver Reset/Set Flip-Flop (LSRS) algorithm generates a digital output value based on
NOR logic of reset and set inputs:
 If the reset input is False (0) and the set input is True (1), the output is True. The output
remains True, regardless of the set value, until the reset value is True. When reset becomes
True, the output is False.
 When both inputs are True, the output is False.
 When both inputs become False, the output remains at its last state and can be either True or
False.
RST is the reset digital input value and quality.
SET is the set digital input value and quality.
Functional Symbol
Algorithm Execution
The LSRS algorithm is used to detect when the set input (SET) transitions to True. It holds the
output True, even when SET transitions to False, until another event changes the reset input
(RST) to True.
The following table shows the algorithm output value based on the possible SET and RST
combinations:
LSRS algorithm truth table
SET RST OUT
False False Last OUT

False True False
True False True
True True False
OW351_R1100 853
8.27 LSRS
Quality Handling
The output quality is equal to the worst quality among the inputs.
FI E L D RE C O R D
RST X2 - Byte Variable Required - Reset Input LD

SET X1 - Byte Variable Required - Set Input LD
854 OW351_R1100
8.28 LSSEQ
8.28 LSSEQ
Description
The LSSEQ algorithm associates system states with actions. The combination of LSSTD
algorithms (which associate transitions with states you define) and LSSEQ algorithms provide a
sequencing capability.
The LSSEQ algorithm can have as many as 16 states and 16 digital outputs. For each state, the
algorithm sets the value of the outputs based on the pattern defined by the MATRX parameter.
See the topic "To access the LSSEQ advanced editor window" in the Ovation Control Builder
User Guide for more information on the MATRIX parameter. The algorithm can step through the
states in sequence using internal increment and decrement parameters, or the algorithm can be
set to specific states (and the corresponding outputs set) from logic external to the algorithm.
Functional Symbol
Algorithm Execution
The LSSEQ algorithm has a configurable number of states and a configurable number of outputs.
By default the number of states is 16 and the number of outputs is 2. The MATRX parameter
defines a mask for each state that indicates how the outputs should be set when the algorithm is
in that state. The LSSEQ algorithm's state can be set in two ways:
 If the STIND parameter is 1 (True) then STATE is set to the value of the STIN parameter.
This allows the algorithm to be driven from another algorithm, for example a State Transition
algorithm (LSSTD) whose STATE parameter is wired to STIN of the LSSEQ algorithm.
 If the STIND parameter is 0 (False) the algorithm remains at its current state unless either the
INC or DEC parameter is set to True, thereby incrementing or decrementing STATE
accordingly. If the WRAP parameter is False STATE stops incrementing when the integer
value of STATE equals NOSTA and stops decrementing when the integer value of S TATE
equals 1. If the WRAP parameter is True STATE wraps around from NOSTA to 1 for an
increment and from 1 to NOSTA for a decrement.
You can disable the LSSEQ algorithm by setting the ENBLE parameter to False. This sets STATE
to 0 and sets all the outputs to 0 (False). When the ENBLE parameter is changed to True and the
STIND parameter is not set, the algorithm sets STATE to 1 and drives the outputs based on the
mask for state 1.
If the STIND parameter is 0 (False), setting RST to True resets STATE back t o state 1. RST
automatically resets to False after use.
OW351_R1100 855
8.28 LSSEQ
Overrides
In normal operation the outputs of the algorithm are a function of the current state and the
configured pattern for that state. However, the parameter OMASK can be manipulated to prevent
one or more outputs from being True. Setting bits in OMASK to 1 masks the corresponding output
from becoming 1 (True) regardless of what is configured for that state.
Quality Handling
The algorithm behavior is not affected by the quality of the input paramet ers. The algorithm's
outputs always have good quality.
FI E L D RE C O R D
NOOUT Y0 - Byte Data Init Required 1 Number of Outputs -

Data Init Required Number of Valid
NOSTA X1 - Byte 16 -
States
Variable Optional Set CurrentState to
STIND X4 - Byte - LD
InputState
INC X5 - Byte Variable Optional - Move to Next State LD
Variable Optional Back to Previous
DEC X6 - Byte - LD
State
STIN X7 - Byte Variable Optional - Input State LA
Variable Optional Enable/Disable
ENBLE X8 - Byte - LD
algorithm
YP - Integer Variable Required
OUT1 - Output 1 LD
- Bit 0
YP - Integer Variable Optional
OUT2 - Output 2 LD
- Bit 1
OUT3 - Output 3 LD
- Bit 2
OUT4 - Output 4 LD
- Bit 3
OUT5 - Output 5 LD
- Bit 4
OUT6 - Output 6 LD
- Bit 5
OUT7 - Output 7 LD
- Bit 6
OUT8 - Output 8 LD
- Bit 7
OUT9 - Output 9 LD
- Bit 8
OUT10 - Output 10 LD
- Bit 9
856 OW351_R1100
8.28 LSSEQ
FI E L D RE C O R D

- Bit 10
- Bit 11
- Bit 12
- Bit 13
- Bit 14
- Bit 15
STATE X9 - Byte Variable Optional - Current State LA
OMASK D2 - Integer Tunable Required 0 Output Mask -
RST X2 - Byte Selectable Optional 0 Force to Initial LD
State 1
0=False
1=True
WRAP X3 - Byte Tunable Required 0 Stop DEC/INC if -
Bit 0 First/Last State
0=False
1=True
DO1 - Data Init Optional Output1 Description Output 1 -
For Control
Builder/Signal
Diagram applications
use only
For Control
Builder/Signal
use only
For Control
Builder/Signal
use only
For Control
Builder/Signal
use only
OW351_R1100 857
8.28 LSSEQ
FI E L D RE C O R D

For Control
Builder/Signal
use only
For Control
Builder/Signal
use only
For Control
Builder/Signal
use only
For Control
Builder/Signal
use only
For Control
Builder/Signal
use only
For Control
Builder/Signal
use only
For Control
Builder/Signal
use only
For Control
Builder/Signal
use only
For Control
Builder/Signal
use only
858 OW351_R1100
8.28 LSSEQ
FI E L D RE C O R D

For Control
Builder/Signal
use only
For Control
Builder/Signal
use only
For Control
Builder/Signal
use only
OW351_R1100 859
8.29 LSSR
8.29 LSSR
Description
The Logic Solver Set/Reset Flip-Flop (LSSR) algorithm generates a digital output value based on
NAND logic of set and reset inputs:
 When the reset input is False (0) and the set input is True (1), the output is True. The output
remains True until the reset input is True and the set input is False.
 When the reset input is True, the output is equal to the set input.
 When both inputs are True, the output is True.
 When both inputs become False, the output remains at its last state and can be either True or
False.
RST is the reset digital input value and quality.
SET is the set digital input value and quality.
Functional Symbol
Algorithm Execution
The LSSR algorithm is used to detect a change in the set input (SET). When the reset input
(RST) is False, OUT is set True after SET changes to True. OUT remains True, even when SET
returns to False, and remains True until RST is changed to True and SET is False.
The following table shows the algorithm output value based on the possible SET and RST
combinations:
LSSR algorithm output values
SET RST OUT
False False Last OUT

False True False
True False True
True True True
860 OW351_R1100
8.29 LSSR
Quality Handling
The output quality is equal to the worst quality among the inputs.
FI E L D RE C O R D
SET X1 - Byte Variable Required - Set Input LD

RST X2 - Byte Variable Required - Reset Input LD
OW351_R1100 861
8.30 LSSTD
8.30 LSSTD
Description
The Logic Solver State Transition Diagram (LSSTD) algorithm implements a user-defined state
machine in the Logic Solver. A state machine describes the possible states, and the transitions
between those states, that can occur in a system. The combination of LSSTD and LSSEQ
algorithms provide a sequencing capability. LSSTD algorithms associate transitions with system
states. LSSEQ algorithms associate system states with actions.
State machines may be described by state transition diagrams. For example, a burner
management system could be defined by the following diagram of the allowed transitions (arrows)
between system states (circles).
The algorithm's MATRX parameter describes the state diagram (the association of states and
input transitions). See the topic "To access the LSSTD advanced editor window" in the Ovation
Control Builder User Guide for more information on the MATRIX parameter.
Functional Symbol
862 OW351_R1100
8.30 LSSTD
Algorithm Execution
The Logic Solver State Transition Diagram (LSSTD) algorithm implements a state transition
diagram. The algorithm can have up to 16 states (outputs) and up to 16 transitions (inputs). You
configure the number of transition inputs, the number of output states, and a matrix of states
versus transitions where each entry indicates the state that the algorithm goes to when that
transition is active. By default the number of inputs (transitions) is 3 and the number of outputs
(states) is 2.
The LSSTD algorithm has a digital input with status (INx) for each transition, a STATE indicating
the current state, and a digital output with status for each state (OUTx). When the algorithm
executes it loops through the transition inputs until an active input is found that has an entry for
the current state in the state-transition matrix. STATE is then set to the matrix value and the
corresponding OUTx output is also set. Once an active transition is found that has a non-zero
matrix entry, no more transitions are checked. If the c urrent state is a terminal state, that is, there
are no entries in the matrix for this state that are not zero, or if masked transitions prevent
transition to another state, the TRMNL parameter is set to True.
The initial state for the algorithm is state 1. When RST is set to True, the algorithm returns to the
initial state. The RST parameter automatically resets to False after it has been used.
The LSSTD algorithm also has an ENBL input. When ENBL is False, STATE is set to 0 and all
OUTx outputs are set to 0. When ENBL is changed from False to True the algorithm is forced into
state 1 and OUT1 is set to True. This allows an LSSTD algorithm to control other LSSTD
algorithms which implement sub-state machines. The Boolean output of the final sub-state
machine can then be wired into a transition of the top level algorithm which causes the sub-state
algorithm ENBL parameter to be set to False.
Overrides
In normal operation the algorithm transitions between states based on the beginning state, the
active transition inputs, and the configuration of the state-transition matrix. The normal behavior
can be overridden in two ways.
 The parameter TMASK prevents one or more transition inputs from causing the state of the
algorithm to change. Setting bits in TMASK prevent the algorithm from seeing the
corresponding transition as active regardless of the transition's value or status.
 The algorithm can also be forced into a specific state by setting the STIND parameter to 1
and setting STIN to the desired state.
The OVRRD parameter indicates when the normal logic is being overridden. It can take on one of
the following values from lowest to highest priority:
 None — No overrides in effect.
 All Associated Transitions Masked — All transitions that would be active have been masked
in TMASK.
 State Forced — STIND has been set to 1.
OW351_R1100 863
8.30 LSSTD
Quality Handling
The quality of the input transition parameters influences the behavior of the LSSTD algorithm
based on the configuration of the SOPT parameter. The SOPT parameter has three values:
 Always Use Value (the default) — Use an input's value regardless of the input's quality.
 Ignore If Bad — If an input's quality is Bad, the input value has no effect on the algorithm.
 Use Last Good Value — While an input's quality is Bad, any change in input value is ignored.
Quality is not propagated to OUTx parameters, which always have Good quality.
FI E L D RE C O R D
NOSTA Y0 - Byte Data Init Required 1 Number of States -

NOTRA Y2 - Byte Data Init Required 1 Number of -
Transitions
IN1 D2 - Integer - Variable Required - Transition Input 1 LD
Bit 0
IN2 D2 - Integer - Variable Required - Transition Input 2 LD
Bit 1
IN3 D2 - Integer - Variable Optional - Transition Input 3 LD
Bit 2
Bit 3
Bit 4
Bit 5
Bit 6
Bit 7
Bit 8
Bit 9
Bit 10
Bit 11
Bit 12
Bit 13
864 OW351_R1100
8.30 LSSTD
FI E L D RE C O R D

Bit 14
Bit 15
ENBL X1 - Byte Variable Optional - Enable State Output LD
STIN X4 - Byte Variable Optional - Input State LA
STIND X5 - Byte Variable Optional - Set CurrentState to LD
InputState
OUT1 D4 - Integer - Variable Required - Output State 1 LD
Bit 0
OUT2 D4 - Integer - Variable Optional - Output State 2 LD
Bit 1
Bit 2
Bit 3
OUT5 D4 - Integer- Variable Optional - Output State 5 LD
Bit 4
Bit 5
Bit 6
Bit 7
Bit 8
Bit 9
Bit 10
Bit 11
Bit 12
Bit 13
Bit 14
Bit 15
OVRRD X6 - Byte Variable Optional - Logic Override LA
Indicator
STATE X7 - Byte Variable Optional - Current State LA
OW351_R1100 865
8.30 LSSTD
FI E L D RE C O R D
TRMNL X8 - Byte Variable Optional - Terminal State LD

Status
VTRAN D5 - Integer Variable Optional - Valid Transitions LA
Indicator
RST X2 - Byte Selectable Optional 0 Force to LD
Initial State 1
0=No
1=Yes
SOPT X3 - Byte Tunable Required 1 Status Options if Bad -
Input
1=Always Use
2=Ignore if Bad
3=Use Last Good
Value
TMASK YP - Integer Tunable Required 0 Transition Mask -
DI1 - Data Init Optional Input1 Description Input 1 -
For Control
Builder/Signal
use only
For Control
Builder/Signal
use only
For Control
Builder/Signal
use only
For Control
Builder/Signal
use only
For Control
Builder/Signal
use only
For Control
Builder/Signal
use only
866 OW351_R1100
8.30 LSSTD
FI E L D RE C O R D

For Control
Builder/Signal
use only
For Control
Builder/Signal
use only
For Control
Builder/Signal
use only
For Control
Builder/Signal
use only
For Control
Builder/Signal
use only
For Control
Builder/Signal
use only
OW351_R1100 867
8.30 LSSTD
FI E L D RE C O R D

For Control
Builder/Signal
use only
For Control
Builder/Signal
use only
For Control
Builder/Signal
use only

For Control
Builder/Signal
use only
868 OW351_R1100
8.31 LSTP
8.31 LSTP
Description
The Logic Solver Timed Pulse (LSTP) algorithm generates a True (1) digital output for a specified
time duration when the input makes a positive (False-to-True) transition. The output remains True
even when the input returns to False. The output returns to False only when the elapsed time is
more than the specified time duration. A False to True transition causes the timer to restart from
zero but the output remains True.
Functional Symbol
Algorithm Execution
The LSTP algorithm sets the output True for a specified time. You can use the algorithm to run a
motor for a specified time period.
The following figure shows the timed response of the LSTP algorithm.
OW351_R1100 869
8.31 LSTP
Quality Handling
The algorithm always sets the quality of OUT to Good.
FI E L D RE C O R D

Elapsed Timer
ETIME R1 - Real Variable Optional - LA
(sec)
Output Reaction
TIMED R2 - Real Tunable Required 2 -
Time Delay (sec)
870 OW351_R1100
8.32 LSXNOR
8.32 LSXNOR
Description
The Logic Solver Not Exclusive OR (LSXNOR) algorithm performs an exclusive OR of two inputs,
then performs a NOT on that result to produce an output. If neither input is True or if both inputs
are True, the output of the algorithm is True. If either input is False, the output of the algorithm is
False.
Functional Symbol
Algorithm Execution
The following table shows the algorithm output value based on the possible IN1 and IN2
combinations:
LSXNOR algorithm output values
IN1 IN2 OUT
False False True

False True False
True False False
True True True
Quality Handling
If one or more of the inputs of the LSXNOR algorithm has Bad quality, the output has Bad quality.
N AME LC AL G . T YP E RE Q U I R E D / DE F AU L T DE S C R I P TI O N MI N . POI N T
RE C O R D O P TI O N AL V AL U E RE C O R D
FI E L D
IN1 X1 - Byte Variable Required - Input 1 LD

OW351_R1100 871
8.33 LSXOR
8.33 LSXOR
Description
The Logic Solver Exclusive OR (LSXOR) algorithm performs an exclusive OR of two inputs to
produce an output that is True if one, and only one, of the inputs is true.
Functional Symbol
Algorithm Execution
The following table shows the algorithm output value based on the possible IN1 and IN2
combinations:
LSXOR algorithm output values
IN1 IN2 OUTD
False False False

False True True
True False True
True True False
Quality Handling
If one or more of the inputs of the LSXOR algorithm has bad quality, the output has bad quality.
NAME LC A L G T YP E RE Q U I R E D / DE F AU L T D E S C R I P TI O N MI N .
FI E L D RE C O R D

872 OW351_R1100
8.34 SIS connector algorithm table
8.34 SIS connector algorithm table
SIS connector algorithms are used to connect data between control modules and between Logic
Solvers. These algorithms accept points into sheets from inside and from outside the SIS
network.
Algorithm description
SECPARAM (see Connects data Connects data on sheets that belong to the same SIS Data
page 876) Server.
SECPARAMREF Connects data Accepts data from a SECPARAM algorithm on sheets that
(see page 878) belong to the same SIS Data Server.
GSECPARAMREF Connects data Accepts data from a SECPARAM algorithm on sheets that
(see page 874) belong to different SIS Data Servers.
NONSECPARAM Connects data Accepts points into a sheet from outside the SIS network.
(see page 875)
OW351_R1100 873
8.35 GSECPARAMREF
8.35 GSECPARAMREF
Description
Note: The GSECPARAMREF algorithm is only supported in Ovation SIS. It is not supported in
Ovation SIS CHARMs.
The GSECPARAMREF algorithm is used as a connector. GSECPARAMREF accepts points into

a sheet from another sheet that belongs to a different SIS Data Server and accepts data from a
SECPARAM algorithm through fiber-optic repeaters.
The SECPARAM and GSECPARAMREF algorithms operate as a pair. This pair (parameter and
parameter reference) is required when the SIS sheets do not belong to the same SIS Data
Server.
Global secure parameters are similar to SIS secure parameters, but may be published globally.
When using global secure parameters, you must also configure the Logic Solver to publish its
secure parameters globally so that you can connect to other SIS Data Servers. This sends the
secure parameter data to the SISNet Repeater and then to all other Logic Solvers. A total of 32
Logic Solvers can publish globally.
Functional Symbol
FI E L D RE C O R D
OUT - Variable Required - Input Point Name LD
874 OW351_R1100
8.36 NONSECPARAM
8.36 NONSECPARAM
Description
The NONSECPARAM algorithm is used as a connector. NONSECPARAM accepts points into a

sheet from outside the SIS network.
Use a page connector on an Ovation sheet to connect to a NONSECPARA M algorithm on SIS

sheet on the SIS network.
Ovation SIS
Ovation SIS supports 24 non-secure parameters per Logic Solver.
Ovation SIS CHARMs
Ovation SIS CHARMs supports 96 non-secure parameters per CSLS.
Functional Symbol
FI E L D RE C O R D
OUT - Variable Required - Input Point LX

Name
OW351_R1100 875
8.37 SECPARAM
8.37 SECPARAM
Description
Note: The Ovation SIS through SIS Data Server (SDS) allows LSs to communicate with other
LS and the Controller. The Ovation SIS CHARMs through Local Safety Network (LSN) allows
CSLSs to communicate with other CSLS and the Controller.
The SECPARAM algorithm is used as a connector. SECPARAM accepts points into a sheet from
inside a SDS/LSN and transfers data to a SECPARAMREF algorithm.
Use the SECPARAM algorithm when connecting a SIS sheet in a Control Module to another
sheet that belongs to the same SDS/LSN. The SECPARAM algorithm can connect sheets in the
same or different Control Modules or Logic Solvers, as long as they all belong to the same SIS
Data Server/LSN.
The SECPARAM and SECPARAMREF algorithms operate as a pair. This pair (parameter and
parameter reference) is required when the SIS sheets belong to the same SDS/LSN. The number
of secure parameters a module can contain depends on the number of available secure
parameters available in the Logic Solver the module is assigned to.
Ovation SIS
Ovation SIS supports 16 high density secure parameters on a Logic Solver. Secure parameters
can be read by other modules in Logic Solvers on the same SIS Data Server. You must configure
a Logic Solver to publish its secure parameters globally so that you can connect to other SIS Data
Servers (see GSECPARAMREF (see page 874)). This sends the secure parameter data to the
SISNet Repeater and then to all other Logic Solvers. A total of 32 Logic Solvers can publish
globally.
Ovation SIS CHARMs.
Ovation SIS CHARMs
Ovation SIS CHARMs supports 96 secure parameters per CSLS.
Note: The Ovation SIS CHARMs product does not support or use SIS Data Server (SDS) and
SISNet Repeater.
876 OW351_R1100
8.37 SECPARAM
Functional Symbol
Algorithm Definition
FI E L D RE C O R D
IN - Variable Required - Output Point LD

Name
OW351_R1100 877
8.38 SECPARAMREF
8.38 SECPARAMREF
Description
Note: The Ovation SIS through SIS Data Server (SDS) allows LSs to communicate with other
LS and the Controller. The Ovation SIS CHARMs through Local Safety Network (LSN) allows
CSLSs to communicate with other CSLS and the Controller.
The SECPARAMREF algorithm is used as a connector, and works in conjunction with the
SECPARAM algorithm. SECPARAMREF accepts points into a sheet that belong to the same
SDS/LSN and accepts data from a SECPARAM (see page 876) a (see page 876)lgoritm.
When a SECPARAM algorithm is used on a sheet, it connects to a SECPARAMREF algorithm on

another sheet that belongs to the same SDS/LSN. You can have any number of Secure
Parameter References in a configuration.
Ovation SIS
To connect to a sheet that belongs to a different SDS, use GSECPARAMREF (see page 874)
algorithm.
Ovation SIS CHARMs.
Ovation SIS CHARMs
Note: The Ovation SIS CHARMs product does not support or use SIS Data Server (SDS) and
SISNet Repeater.
Functional Symbol
FI E L D RE C O R D
OUT - Variable Required - Input Point LD

Name
878 OW351_R1100
SECTION 9
9 Migrated special functions
IN THIS SECTION
What are migrated special functions? ....................................................................... 879

WDPF to Ovation reference table............................................................................. 880
WDPF special functions to Ovation algorit hms .......................................................... 888
What are migration algorithms? ............................................................................... 893
9.1 What are migrated special functions?
Migration refers to the process of upgrading a system from WDPF to Ovation, while still using the
original Q-Line wiring and/or Q-Line I/O cards. This method of upgrade can save a company time
and money since the existing field wiring does not have to be replaced.
Typically, ladders are used only by Migration projects. After a system has been migrated, any
ladder logic that was used in the original system is preserved in the new Ovation system, and
may need to be edited.
Ladder control can be edited or built with a special user interface provided in the Control Builder.
The ladder control application contains a set of functions which duplicates relay -type circuits,
devices, and the operation sequence of a conventional, electrical relay system.
A ladder is edited or built in a dialog box that consists of a 7 by 9 cell array. Each cell can be
edited to display a shape (such as a coil, contact, or special function) and to store information
about that shape.
These shapes or functions form a relay diagram that depicts the types of inputs, controls, and
outputs. The diagram shows how these user-selected inputs are configured to cause an assigned
device to operate in a desired manner.
The information provided here is applicable for systems that have migrated control and databases
from a WDPF system to an Ovation system. The following table lists the Special Functions names
and parameter interface.
OW351_R1100 879
9.2 WDPF to Ovation reference table
The following table shows the WDPF algorithms (text, graphic, and special functions) with the
equivalent Ovation algorithms. The last column of the table tells you where you can find more
information about the algorithm.
Standard WDPF Algorithms with Equivalent Standard Ovation Algorithms
S TAN D AR D W DPF EQ U I V AL E N T S O U R C E D O C U ME N T
A L G O R I TH M O V ATI O N A L G O R I TH M
AAFLFLR AAFLIPFLOP Ovation Algorithms Reference Manual
ABSVAL ABSVALUE Ovation Algorithms Reference Manual

ADD ADD WDPF Special Functions Reference Manual and
WDPF special functions to Ovation algorithms (see
page 888)
ALARMMTR ALARMMON Ovation Algorithms Reference Manual
ALOG OUT ALOGOUT WDPF Special Functions Reference Manual
AND4 AND Ovation Algorithms Reference Manual
AND REGS ANDREGS WDPF Special Functions Reference Manual and
page 888)
AND TBLS ANDTBLS WDPF Special Functions Reference Manual and
page 888)
ANLOG IN ANLOGIN WDPF Special Functions Reference Manual and
page 888)
ANTILOG ANTILOG Ovation Algorithms Reference Manual
ARCCOSIN ARCCOSINE Ovation Algorithms Reference Manual
ARCSINE ARCSINE Ovation Algorithms Reference Manual
ARCTANGT ARCTANGENT Ovation Algorithms Reference Manual
ASC_BIN ASC_BIN WDPF Special Functions Reference Manual and
page 888)
ATREND ATREND Ovation Algorithms Reference Manual
AVALGEN AVALGEN Ovation Algorithms Reference Manual
AVGNW AVGNW WDPF Standard Control Algorithm User Guide
AVGXFM2 AVGXFM2 WDPF Standard Control Algorithm User Guide
AXTOPB AXTOPB WDPF Standard Control Algorithm User Guide
BCD_BIN BCD_BIN WDPF Special Functions Reference Manual and
page 888)
BCDNIN BCDNIN Ovation Algorithms Reference Manual
BCDNOUT BCDNOUT Ovation Algorithms Reference Manual
880 OW351_R1100
BIN_ASC BIN_ASC WDPF Special Functions Reference Manual and

page 888)
BIN_BCD BIN_BCD WDPF Special Functions Reference Manual and
page 888)
BITCLEAR BITCLEAR WDPF Special Functions Reference Manual and
page 888)
BITL BITL WDPF Special Functions Reference Manual and
page 888)
BITOP BITOP WDPF Special Functions Reference Manual and
page 888)
BITR BITR WDPF Special Functions Reference Manual and
page 888)
BITSET BITSET WDPF Special Functions Reference Manual and
page 888)
BLK MOVE BLKMOVE WDPF Special Functions Reference Manual and
page 888)
BTFOLLOW BTFOLLOW WDPF Special Functions Reference Manual and
page 888)
BYT MOVE BYTMOVE WDPF Special Functions Reference Manual and
page 888)
COMPDIG COMPDIG WDPF Standard Control Algorithm User Guide
COMP REG COMPREG WDPF Special Functions Reference Manual and
page 888)
COMP TBL COMPTBL WDPF Special Functions Reference Manual and
page 888)
COMPARE COMPARE Ovation Algorithms Reference Manual
COSINE COSINE Ovation Algorithms Reference Manual
CRTMA CRTMA WDPF Standard Control Algorithm User Guide
CRTML CRTML WDPF Standard Control Algorithm User Guide
DBDLTA DBDLTA WDPF Standard Control Algorithm User Guide
DBEQUALS DBEQUALS Ovation Algorithms Reference Manual
DELTAW DELTAW WDPF Standard Control Algorithm User Guide
DEVICE DEVICE Ovation Algorithms Reference Manual
OW351_R1100 881
DEVICEX DEVICEX Ovation Algorithms Reference Manual

DIGCNTNF DIGCOUNT Ovation Algorithms Reference Manual
DIVIDE W2DIVIDE WDPF Special Functions Reference Manual and
page 888)
DIVIDEGB DIVIDEGB WDPF Standard Control Algorithm User Guide
DN COUNT W2COUNT WDPF Special Functions Reference Manual and
page 888)
DRUMA1 ANALOGDRUM Ovation Algorithms Reference Manual
DRUMA2 ANALOGDRUM Ovation Algorithms Reference Manual
DRUM CTL DRUMCTL WDPF Special Functions Reference Manual and
page 888)
DRUMD16 DIGDRUM Ovation Algorithms Reference Manual
DVALGEN DVALGEN Ovation Algorithms Reference Manual
FCTGEN FUNCTION Ovation Algorithms Reference Manual
FIRST IN FIRSTIN WDPF Special Functions Reference Manual and
page 888)
FRST OUT FRSTOUT WDPF Special Functions Reference Manual and
page 888)
FLIPFLRO FLIPFLRO WDPF Standard Control Algorithm User Guide
GAINBI GAINBIAS Ovation Algorithms Reference Manual
HILMTVFL HILMTVFL WDPF Standard Control Algorithm User Guide
HILOLMTV HILOLMTV WDPF Standard Control Algorithm User Guide
HILOMTR HIGHLOWMON Ovation Algorithms Reference Manual
HISEL10 HISEL10 WDPF Standard Control Algorithm User Guide
HISEL4 HISELECT Ovation Algorithms Reference Manual
HISIGMTR HIGHMON Ovation Algorithms Reference Manual
HISIGMTV HIGHMON Ovation Algorithms Reference Manual
HL2MTR HL2MTR WDPF Standard Control Algorithm User Guide
INTEGVGR INTEGVGR WDPF Standard Control Algorithm User Guide
I DNCNT W2COUNT WDPF Special Functions Reference Manual and
page 888)
I ONESHT W2ONESHT WDPF Special Functions Reference Manual and
page 888)
882 OW351_R1100
I TIMOFF W2OFFDELAY WDPF Special Functions Reference Manual and

page 888)
I TIMON W2ONDELAY WDPF Special Functions Reference Manual and
page 888)
I UPCNT W2COUNT WDPF Special Functions Reference Manual and
page 888)
INVERTER NOT Ovation Algorithms Reference Manual
LAGVTC LAGVTC WDPF Standard Control Algorithm User Guide
LAST OUT LASTOUT WDPF Special Functions Reference Manual and
page 888)
LIMIT LIMIT WDPF Special Functions Reference Manual and
page 888)
LOG LOG Ovation Algorithms Reference Manual
LOLMTVFL LOLMTVFL WDPF Standard Control Algorithm User Guide
LOSEL10 LOSEL10 WDPF Standard Control Algorithm User Guide
LOSEL4 LOSELECT Ovation Algorithms Reference Manual
LOSIGMTR LOWMON Ovation Algorithms Reference Manual
LOGSIGMTV LOWMON Ovation Algorithms Reference Manual
MASSFLOW MASSFLOW WDPF Standard Control Algorithm User Guide
MEDSEL2 MEDIANSEL Ovation Algorithms Reference Manual
MULTGB MULTGB WDPF Standard Control Algorithm User Guide
MULTIPLY W2MULTIPLY WDPF Special Functions Reference Manual and
page 888)
MULTSL MULTSL WDPF Special Functions Reference Manual and
page 888)
MULTSR MULTSR WDPF Special Functions Reference Manual and
page 888)
NEGATE NEGATE WDPF Special Functions Reference Manual and
page 888)
NLOG NLOG Ovation Algorithms Reference Manual
NOTIN NOT Ovation Algorithms Reference Manual
ONESHOT2 ONESHOT2 WDPF Standard Control Algorithm User Guide
ONE SHOT ONESHOT Ovation Algorithms Reference Manual
ONESHOTR ONESHOT Ovation Algorithms Reference Manual
OW351_R1100 883
OR4 OR Ovation Algorithms Reference Manual

OR REGS ORREGS WDPF Special Functions Reference Manual and
page 888)
OR TBLS ORTBLS WDPF Special Functions Reference Manual and
WDPF special functions to Ovation algorithms" (see
page 888)
PACKPB PACKPB WDPF Standard Control Algorithm User Guide
PBTOAX PBTOAX WDPF Standard Control Algorithm User Guide
PID W2PID WDPF Standard Control Algorithm User Guide

PIDVGRR PIDVGRR WDPF Standard Control Algorithm User Guide
PIDVLIM PIDVLIM WDPF Standard Control Algorithm User Guide
PKEY1TO10 KEYBOARD Ovation Algorithms Reference Manual
PNT_STAT PNTSTAT WDPF Special Functions Reference Manual and
page 888)
POLY POLYNOMIAL Ovation Algorithms Reference Manual
PT SHF L PTSHFL WDPF Special Functions Reference Manual and
page 888)
PT SHF R PTSHFR WDPF Special Functions Reference Manual and
page 888)
PULSECNT PULSECNT Ovation Algorithms Reference Manual
PULSELAT PULSELAT WDPF Standard Control Algorithm User Guide
PVSPSLI PVSPSLI WDPF Standard Control Algorithm User Guide
PWDIN PWDIN WDPF Standard Control Algorithm User Guide
QAVGN QAVERAGE Ovation Algorithms Reference Manual
QBEST4 QBEST4 WDPF Standard Control Algorithm User Guide
QBLOCK QBLOCK WDPF Standard Control Algorithm User Guide
QCHK1BAD QUALITYMON Ovation Algorithms Reference Manual
QCHK2NG QCHK2NG WDPF Standard Control Algorithm User Guide
QCOMPARE QCOMPARE WDPF Standard Control Algorithm User Guide
QLATCH LATCHQUAL Ovation Algorithms Reference Manual
QLCAIN SLCAIN Ovation Algorithms Reference Manual
QLCAOUT SLCAOUT Ovation Algorithms Reference Manual
884 OW351_R1100
QLCCMD QLCCMD WDPF Standard Control Algorithm User Guide
QLCDIN SLCDIN Ovation Algorithms Reference Manual

QLCDOUT SLCDOUT Ovation Algorithms Reference Manual
QLCGPIN SLCPIN Ovation Algorithms Reference Manual
QLCGPOUT SLCPOUT Ovation Algorithms Reference Manual
QLCNTWRK SLCNETWORK WDPF Standard Control Algorithm User Guide (see
QLCNTWRK algorithm)
QLCSTAT SLCSTATUS Ovation Algorithms Reference Manual
QLIPASS QLIPASS WDPF Standard Control Algorithm User Guide
QPACMD QPACMD Ovation Algorithms Reference Manual
QPACMPAR QPACMPAR Ovation Algorithms Reference Manual
QPASTAT QPASTAT Ovation Algorithms Reference Manual
QTBCHK QTBCHK WDPF Standard Control Algorithm User Guide
QTRANSN QTRANSN WDPF Standard Control Algorithm User Guide
QVP QVP Ovation Algorithms Reference Manual
QWORST4 QWORST4 WDPF Standard Control Algorithm User Guide
RATECHG RATECHANGE Ovation Algorithms Reference Manual
RATELIMF RATELIMIT Ovation Algorithms Reference Manual
RATEMTR RATEMON Ovation Algorithms Reference Manual
RATEMTRV RATEMON Ovation Algorithms Reference Manual
RATLIMVF RATELIMIT Ovation Algorithms Reference Manual
RESETSUM RESETSUM Ovation Algorithms Reference Manual
ROLLOVER ROLLOVER WDPF Standard Control Algorithm User Guide
RQAMSP RQAMSP WDPF Standard Control Algorithm User Guide
RR COMP RRCOMP WDPF Special Functions Reference Manual and
page 888)
RR MOVE RRMOVE WDPF Special Functions Reference Manual and
page 888)
RT COMP RTCOMP WDPF Special Functions Reference Manual and
page 888)
RT MOVE RTMOVE WDPF Special Functions Reference Manual and
page 888)
RUNAVG RUNAVERAGE Ovation Algorithms Reference Manual
SCALE SCALE WDPF Special Functions Reference Manual and
page 888)
OW351_R1100 885
SEARCH 1 SEARCH1 WDPF Special Functions Reference Manual and

page 888)
SEARCH E SEARCHE WDPF Special Functions Reference Manual and
page 888)
SINE SINE Ovation Algorithms Reference Manual
SM2XMTRS 2XSELECT Ovation Algorithms Reference Manual
SMOOTH SMOOTH Ovation Algorithms Reference Manual
SQROOT SQROOT WDPF Special Functions Reference Manual and
page 888)
SQRTGB SQUAREROOT Ovation Algorithms Reference Manual
SRCH GE SRCHGE WDPF Special Functions Reference Manual and
page 888)
STATMTR STATMTR WDPF Standard Control Algorithm User Guide
STEPTIME STEPTIME Ovation Algorithms Reference Manual
SUBTRACT SUBTRACT WDPF Special Functions Reference Manual and
page 888)
SUM4W SUM Ovation Algorithms Reference Manual
SYSTIME SYSTEMTIME Ovation Algorithms Reference Manual
TANGT TANGENT Ovation Algorithms Reference Manual
TIMECHG TIMECHANGE Ovation Algorithms Reference Manual
TIMEDEL TIMEDEL WDPF Standard Control Algorithm User Guide
TIMEDET TIMEDETECT Ovation Algorithms Reference Manual
TIMEMTR TIMEMON Ovation Algorithms Reference Manual
TIME OFF OFFDELAY Ovation Algorithms Reference Manual
TIMEOFFR OFFDELAY Ovation Algorithms Reference Manual
TIMEONR ONDELAY Ovation Algorithms Reference Manual
TIMER ON ONDELAY Ovation Algorithms Reference Manual
TR MOVE TRMOVE WDPF Special Functions Reference Manual and
page 888)
TRACK TRACK WDPF Standard Control Algorithm Us er Guide
TRANSF TRANSFER Ovation Algorithms Reference Manual
TRANSFNI SELECTOR Ovation Algorithms Reference Manual
TRANSITN TRANSITN WDPF Special Functions Reference Manual and
page 888)
886 OW351_R1100
TRANSLAT TRANSLATOR Ovation Algorithms Reference Manual

TRKHOLD TRKHOLD WDPF Standard Control Algorithm User Guide
TRNSPTDL TRANSPORT Ovation Algorithms Reference Manual
TRUTHTBL TRUTHTABLE WDPF Standard Control Algorithm User Guide
TT COMP TTCOMP WDPF Special Functions Reference Manual and
page 888)
TT MOVE TTMOVE WDPF Special Functions Reference Manual and
page 888)
UNPACKPB UNPACKPB WDPF Standard Control Algorithm User Guide
UP COUNT W2COUNT WDPF Special Functions Reference Manual and
page 888)
XDELTA SUM Ovation Algorithms Reference Manual
XDIVIDE DIVIDE Ovation Algorithms Reference Manual
XFCTGEN FUNCTION Ovation Algorithms Reference Manual
XFLOW XFLOW WDPF Standard Control Algorithm User Guide
XHISEL HISELECT Ovation Algorithms Reference Manual
XLEADLAG LEADLAG Ovation Algorithms Reference Manual
XLIMIT GAINBIAS Ovation Algorithms Reference Manual
XLOSEL LOSELECT Ovation Algorithms Reference Manual
XMA2 XMA2 Ovation Algorithms Reference Manual
XMASTER BALANCER Ovation Algorithms Reference Manual
XML2 XML2 Ovation Algorithms Reference Manual

XMULT MULTIPLY Ovation Algorithms Reference Manual
XOR2 XOR Ovation Algorithms Reference Manual
XOR REGS XORREGS WDPF Special Functions Reference Manual and
page 888)
XOR TBLS XORTBLS WDPF Special Functions Reference Manual and
page 888)
XPDSPV XPDSPV WDPF Standard Control Algorithm User Guide
XPID XPID WDPF Standard Control Algorithm User Guide
XPIDOVD XPIDOVD WDPF Standard Control Algorithm User Guide
XPIDSLI XPIDSLI WDPF Standard Control Algorithm User Guide
XPIDSPV XPIDSPV WDPF Standard Control Algorithm User Guide
XPIDV XPIDV WDPF Standard Control Algorithm User Guide
OW351_R1100 887
9.3 WDPF special functions to Ovation algorithms
XSQROOT SQUAREROOT Ovation Algorithms Reference Manual

XSUM SUM Ovation Algorithms Reference Manual
XTRANSF TRANSFER Ovation Algorithms Reference Manual
X3STEP X3STEP Ovation Algorithms Reference Manual
ZERO TBL ZEROTBL WDPF Special Functions Reference Manual and
page 888)
The following table lists the original WDPF Special Function parameter and the corresponding
migrated Ovation Special Function parameter names.
WDPF to Ovation Migration
W DPF S P E C I AL W DPF O V ATI O N O V ATI O N

FU N C TI O N P AR AME T E R S AL G O R I TH M P AR AME T E R S
ADD REG 1 ADD REG1

REG 2 REG2
RESULT RSLT
ALOG OUT SRCE REG ALOGOUT SRCE
DEST REG DEST
AND REGS REG 1 ANDREGS REG1
REG 2 REG2
RESULT RSLT
AND TBLS TABLE 1 ANDTBLS TBL1
TABLE 2 TBL2
LENGTH LENG
DEST TBL DTBL
ANLOG IN SRCE REG ANLOGIN SRCE
DEST REG DEST
ASC_BIN SOURCE ASC_BIN SRCE
TARGET TRGT
BCD_BIN SRCE REG BCD_BIN SRCE
DEST REG DEST
BIN_ASC SOURCE BIN_ASC SRCE
TARGET TRGT
BIN_BCD SRCE REG BIN_BCD SRCE
DEST REG DEST
888 OW351_R1100

BITCLEAR REGISTER BITCLEAR REG

BIT BIT
BITL REGISTER BITL REG
LENGTH LENG
BITOP TABLE BITOP TBLE
LENGTH LENG
BIT POS BITP
BITR REGISTER BITR REG
LENGTH LENG
BITSET REGISTER BITSET REG
BIT BIT
BLK MOVE TABLE 1 BLKMOVE TBL1
TABLE 2 TBL2
LENGTH LENG
BTFOLLOW REGISTER BTFOLLOW REG
BIT BIT
BYT MOVE SRCE REG BYTMOVE SRCE
MOV PTRN MOVE
DEST REG DEST
COMP REG REGISTER COMPREG REG
RESULT RSLT
COMP TBL SRC TBL COMPTBL STBL
DEST TBL DTBL
LENGTH LENG
COMPARE REG 1 COMPARE IN1
REG 2 IN2
DIVIDE REG 1 W2DIVIDE REG1
REG 2 REG2
WHOLE WHOL
REMAINDER RMDR
DN COUNT PRESET W2COUNT TARG
ACTUAL ACT
DRCT = 0
DRUM CTL SRC TABL DRUMCTL SRCE
LENGTH LENG
DEST REG DEST
POINTER PTR
OW351_R1100 889

FIRST IN SOURCE FIRSTIN SRCE

TABLE TBLE
LENGTH LENG
POINTER PTR
FRST OUT TABLE FRSTOUT TBLE
LENGTH LENG
REGISTER REG
POINTER PTR
I DNCNT PRESET W2COUNT TARG
ACTUAL ACT
DRCT = 0
I ONESHT PRESET W2ONESHOT TARG
ACTUAL ACT
TIMEBASE BASE
I TIMOFF PRESET W2OFFDELAY TARG
ACTUAL ACT
TIMEBASE BASE
I TIMON PRESET W2ONDELAY TARG
ACTUAL ACT
TIMEBASE BASE
I UPCNT PRESET W2COUNT TARG
ACTUAL ACT
DRCT = 1
INVERTER Not Applicable NOT Not Applicable
LAST OUT TABLE LASTOUT TBLE

LENGTH LENG
REGISTER REG
POINTER PTR
LIMIT REGISTER LIMIT REG
LOW LOW
HIGH HIGH
MULTIPLY REG 1 W2MULTIPLY REG1
REG 2 REG2
RESULT RSLT
890 OW351_R1100

MULTSL STRT REG MULTSL STRT

LENGTH LENG
DATA REG DATA
COUNT CNT
MULTSR STRT REG MULTSR STRT
LENGTH LENG
DATA REG DATA
COUNT CNT
NEGATE REGISTER NEGATE REG
RESULT RSLT
ONE SHOT PRESET ONESHOT TARG
ACTUAL ACT
BASE = 0.1
ONESHOTR PRESET ONESHOT TARG
ACTUAL ACT
BASE = 0.1
OR REGS REG 1 ORREGS REG1
REG 2 REG2
RESULT RSLT
OR TBLS TABLE 1 ORTBLS TBL1
TABLE 2 TBL2
LENGTH LENG
DEST TBL DTBL
PNT_STAT POINT PNTSTAT PNT
BITA BITA
BITB BITB
PT SHF L POINT PTSHFL PNT
PT SHF R POINT PTSHFR PNT

RR COMP REG 1 RRCOMP REG1
REG 2 REG2
RR MOVE REG 1 RRMOVE REG1
REG 2 REG2
RT COMP REGISTER RTCOMP REG
TABLE TBLE
LENGTH LENG
POINTER PTR
OW351_R1100 891

RT MOVE REGISTER RTMOVE REG

TABLE TBLE
LENGTH LENG
POINTER PTR
SCALE HI LIM1 SCALE HI1
LO LIM1 LOW1
DATA 1 DAT1
HI LIM2 HI2
LO LIM2 LOW2
DATA 2 DAT2
SEARCH 1 TABLE SEARCH1 TBLE
LENGTH LENG
POINTER PTR
SEARCH E REF REG SEARCHE REG
TABLE TBLE
LENGTH LENG
POINTER PTR
SQROOT REGISTER SQROOT REG
RESULT RSLT
SRCH GE REF REG SRCHGE REG
TABLE TBLE
LENGTH LENG
POINTER PTR
SUBTRACT REG 1 SUBTRACT REG1
REG 2 REG2
RESULT RSLT
TIME OFF PRESET OFFDELAY TARG
ACTUAL ACT
BASE = 0.1
TIMEOFFR PRESET OFFDELAY TARG
ACTUAL ACT
BASE = 0.1
TIMEONR PRESET ONDELAY TARG
ACTUAL ACT
BASE = 0.1
892 OW351_R1100
9.4 What are migration algorithms?

TIMER ON PRESET ONDELAY TARG

ACTUAL ACT
BASE = 0.1
TR MOVE TABLE TRMOVE TBLE
POINTER PTR
LENGTH LENG
REGISTER REG
TRANSITN IN STATE TRANSITN INST
TT COMP TABLE 1 TTCOMP TBL1

TABLE 2 TBL2
LENGTH LENG
POINTER PTR
TT MOVE TABLE 1 TTMOVE TBL1
TABLE 2 TBL2
LENGTH LENG
POINTER PTR
UP COUNT PRESET W2COUNT TARG
ACTUAL ACT
DRCT = 1
XOR REGS REG 1 XORREGS REG1
REG 2 REG2
RESULT RSLT
XOR TBLS TABLE 1 XORTBLS TBL1
TABLE 2 TBL2
LENGTH LENG
DEST TBL DTBL
ZERO TBL TABLE ZEROTBL TBLE
LENGTH LENG
The MODETRANS and SETSTATES algorithms are specifically used for migration.
OW351_R1100 893
9.4.1 M ODETRANS
Description
The MODETRANS algorithm transfers the Ovation tracking point status bit information (bits 16 -
32 stored in the 3W field) to an Ovation packed point. The Ovation packed point represents the
WDPF mode point. By recreating the WDPF mode point in Ovation, it allows the custom graphics
to remain the same because the same WDPF point is used.
Note: This is reserved for migration systems use only.
Functional Symbol
FI E L D RE C O R D
IN Input Variable Required - Ovation Tracking LA

Point
OUT Output Variable Required - WDPF Mode Point LP
894 OW351_R1100
9.4.2 SET STAT ES

Description
The SETSTATES algorithm sets tracking bits in the Ovation tracking point based on the inputs
that are connected.
Note: This is reserved for migration systems use only.
Functional Symbol
FI E L D RE C O R D
TRK Input Variable Optional -- Tracking bit LD
TRKL Input Variable Optional -- Track if Lower bit LD

TRKR Input Variable Optional -- Track if Higher bit LD
LWI Input Variable Optional -- Lower Inhibit bit LD
RAI Input Variable Optional -- Raise Inhibit bit LD
AUTO Input Variable Optional -- Auto Mode bit LD
MAN Input Variable Optional -- Manual Mode bit LD
TOUT Input Variable Required -- Ovation Tracking LA
point
OW351_R1100 895
Index
2 D
2XSELECT • 595 DBEQUALS • 122
Determining hardware addressing • 3
A DEVICE • 124
AAFLIPFLOP • 48 Device Control algorithms • 23
ABSVALUE • 50 DEVICESEQ • 144
Alarm Manipulation algorithms • 21 DEVICEX • 148
ALARMLIMIT • 51 DFIELD • 167
ALARMMON • 56 DIGCOUNT • 168
Algorithm classification groups • 20 DIGDRUM • 169
Algorithm classifications • 19 DIGITAL DEVICE • 174
Algorithm functional symbols • 47 DISTRIBUTOR • 195
Algorithm status and mode settings • 4 Distributor Algorithm Definitions • 206
Algorithms • 1 DIVIDE • 215
Algorithms that support tracking • 12 DROPSTATUS • 218
ANALOG DEVICE (ADEVICE) • 58 DRPI1A • 221
ANALOGDRUM • 61 DVALGEN • 223
AND • 65 DXCSTATUS • 224
ANNUNCIATOR • 66 DXCSTATUS functions • 241
ANTILOG • 69 DXCSTATUS state • 243
ARCCOSINE • 71 DXCSTATUS tuning parameters and site
ARCSINE • 72 ratings • 239
ARCTANGENT • 73 E
Artificial I/O algorithms (signal generators) •
21 Error information • 6
ASSIGN • 74 Exclusion (EXCL) • 196
ATREND • 75
AVALGEN • 77 F
B FACEPLATE • 245
FACEPLATE -- DIGITAL DEVICE template •
BALANCER • 78 248
Base Gain • 201 FACEPLATE -- MASTATION template • 252
BCDNIN • 83 FFAI • 674
BCDNOUT • 85 FFAO • 677
BILLFLOW • 87 FFDI • 680
Binary to hexadecimal conversion • 6 FFDO • 683
Boolean Logic algorithms • 22 FFISEL/FFISELX • 686
Boolean Logic Memory algorithms • 22 FFMAI • 694
BUFFER • 89 FFMAO • 698
FFMDI • 700
C FFMDO • 704
CALCBLOCK • 103 FFPID • 708
CALCBLOCKD • 112 FIELD • 253
COMPARE • 118 Fieldbus algorithms • 24
Copyright Notice • 2 FIFO • 255
Correction Gain • 199 Filtering algorithms • 25
COSINE • 119 First Pass Startup Options • 205
COUNTER • 120 FIRSTOUT • 258
Custom Calculation algorithms • 23 FLIPFLOP • 263
OW351_R1100 897
Index
Foundation Fieldbus algorithms • 671 LSDO • 790

FUNCTION • 265 LSDVC • 797
LSDVTR • 808
G LSLIM • 825
GAINBIAS • 269 LSMID • 828
GASFLOW • 273 LSNAND • 832
General algorithm user information • 3 LSNDE • 834
GSECPARAMREF • 870 LSNOR • 836
LSNOT • 838
H LSOFFD • 839
LSOND • 841
Hardware addressing • 3
LSOR • 843
Hardware Interface algorithms • 26
LSPDE • 845
HEARTBEAT • 280
LSRET • 847
HIGHLOWMON • 283
LSRS • 849
HIGHMON • 284
LSSEQ • 851
HISELECT • 286
LSSR • 856
HSCLTP • 291
LSSTD • 858
HSLT • 292
LSTP • 865
HSTVSVP • 293
LSXNOR • 867
HSVSSTP • 294
LSXOR • 868
I M
Input, FNUM parameter, and Output pins
MAMODE • 319
(IN, FNUM, and OUT[1-8]) • 195
MASTATION • 321
Internal and External Control • 203
MASTERSEQ • 331
INTERP • 295
Mathematical and Statistical algorithms • 29
Introduction to Ovation Q-Line and Specialty
MEDIANSEL • 344
algorithms • 1
Migrated special functions • 875
Invalid number checking and quality
Migration algorithms • 889
checking • 5
MODETRANS • 890
K Modulating Control algorithms • 30
Monitor Function algorithms • 31
KEYBOARD • 299 MOTOR (Simple Controlled Motor) • 180
L MOTOR 2-SPD (Two Speed or Bi-
Directional Controlled Motor) • 183
LATCHQUAL • 302 MOTOR 4-SPD (Two Speed and Bi-
LEADLAG • 304 Directional Controlled Motor) • 187
LEVELCOMP • 308 MOTOR NC (Non-Controlled Motor) • 178
Link Controller Module Interface algorithms • MULTIPLY • 352
27
LOG • 312 N
Loop Interface Module algorithms • 28 NLOG • 355
LOSELECT • 313 NONSECPARAM • 871
LOWMON • 318 NOT • 356
LSAI • 717
LSALM • 719 O
LSAND • 721
OFFDELAY • 357
LSAVTR • 723
ONDELAY • 359
LSBDE • 740
ONESHOT • 362
LSBFI • 742
Operator Interface algorithms • 32
LSBFO • 745
OR • 365
LSCALC • 748
Ovation Fieldbus algorithms and function
LSCALC Expression Editor • 753
blocks • 672
LSCEM • 763
LSCMP • 786
LSDI • 788
898 OW351_R1100
Index
SATOSP • 475
P SECPARAM • 872
PACK16 • 366 SECPARAMREF • 874
PID • 368 SELECTOR • 476
PIDFF • 385 Sequential Logic algorithms • 37
PNTSTATUS • 398 SETPOINT • 478
Point Format Conversion algorithms • 33 SETSTATES • 891
Point Quality • 206 Setting tracking signals • 15
POLYNOMIAL • 400 SID Storage • 206
PREDICTOR • 402 Signal Compensation algorithms • 38
PRIORITY • 407 SIMTIME • 481
PRIORITY Algorithm Package • 406 SINE • 481
Priority Deadband (PDB) • 200 Single precision floating point numbers • 6
PRIORITY-E XT • 424 SIS algorithm types • 716
PRIORITY-RE J • 428 SIS connector algorithm table • 869
Propagated point quality • 4 SLCAIN • 482
PSLT • 431 SLCAOUT • 485
PSVS • 432 SLCDIN • 488
Pulse Accumulator Module Interface SLCDOUT • 491
algorithms • 34 SLCPIN • 494
PULSECNT • 433 SLCPOUT • 497
PVSPSLI • 605 SLCSTATUS • 500
PWDIN • 608 SMOOTH • 504
SOFTSOE • 506
Q SPTOSA • 516
SQUAREFOOT • 517
QAVERAGE • 434
SSLT • 520
Q-Line algorithms • 603, 604
Standard algorithm reference pages • 43
Q-Line Interface algorithms • 35
STAT bits used with function blocks • 673
QLIPASS • 611
STATISTICS • 521
QPACMD • 615
STEAMFLOW • 538
QPACMPAR • 621
STEAMTABLE • 540
QPASTAT • 622
STEPTIME • 543
QSDDEMAND • 623
SUM • 548
QSDMODE • 625
Summary of Changes • 3
QSRMA • 626
Switching Between Internal and External
QUALITYMON • 435
Inputs • 204
QVP • 632
System Diagnostic algorithms • 39
R System Time Function algorithms • 39
SYSTEMTIME • 552
RAMPGEN • 436
RATECHANGE • 440 T
RATELIMIT • 442
TANGENT • 553
RATEMON • 445
Time/Counter Function algorithms • 40
Redundant Signal Processing algorithms •
TIMECHANGE • 554
36
TIMEDETECT • 555
RESETSUM • 447
TIMEMON • 556
RLICONFIG • 450
Tracking • 9
RPACNT • 453
Tracking (best practices) • 11
RPAWIDTH • 454
Tracking (purpose of) • 10
RSRSTATUS • 455
Tracking algorithms • 41
RUNAVERAGE • 465
Tracking examples • 14
RUNTIME • 467
Tracking Inputs (TKIN[1-8]) • 198
RVPSTATUS • 472
Tracking Out (TOUT) • 202
S Tracking process • 11
TRANSFER • 559
SAMPLER (Controlled Sampler) • 175 TRANSLATOR • 567
OW351_R1100 899
Index
TRANSPORT • 571
TRNSFINDX • 573
TRUTHTB L • 574
TSLH • 578
TSLP • 579
Turbine Interface algorithms • 42
U
Understanding algorithm descriptions • 46
Understanding the Ovation SIS algorithms •
713
Understanding tracking • 9
UNPACK16 • 580
V
VALVE (Controlled Valve) • 192
VALVE NC (Non-Controlled Valve) • 177
VCLTP • 582
VSLT • 583
W
WDPF special functions to Ovation
algorithms • 884
WDPF to Ovation reference table • 876
What are Foundation Fieldbus algorithms? •
671
What are Ovation SIS Logic Solver
algorithms? • 714
X
X3STEP • 585
XFLOW • 635
XMA2 • 641
XML2 • 652
XOR • 584
XPIDSLI • 657
900 OW351_R1100

Ovation Functions Guide

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Ovation Functions Guide

Загружено:

Авторское право:

Доступные форматы

Ovation Algorithms Reference Manual

(For use with Ovation 3.5.1 systems)

E-Mail: Technical.Communications@EmersonP rocess.com

1 Introduction to Ovation Q-Line and Specialty algorithms 1

2 General algorithm user information 3

4.15 Monitor Function algorithms ...................................................................................... 31

5 Standard algorithm reference pages 43

5.29 DEVICESEQ .......................................................................................................... 144

5.54 HSLT ..................................................................................................................... 296

5.96 RSRS TA TUS ......................................................................................................... 459

6 Q-Line algorithms 607

7 Foundation Fieldbus algorithms 675

8 Understanding the Ovation SIS algorithms 717

8.9 LSCALC................................................................................................................. 752

9 Migrated special functions 879

1 Introduction to Ovation Q-Line and Specialty

What are algorit hms? .................................................................................................. 1

1.1 What are algorithms?

Standard Ovation algorithms are described in Ovation Algorithms Reference Manual.

2 General algorithm user information

What is hardware addressing for algorithms? ............................................................... 3

2.1 What is hardware addressing for algorith ms?

2.1.1 T o de te rmine an algorithm hardware address

2.2 What is propagated point quality?

Note: Algorithms propagate GOOD quality when in Manual mode.

2.3 Algorithm status and mode settings

The mode and status digital signals are set as follows:

2.4 What is invalid number checking and quality checking for

An invalid number is generated under exceptional conditions. An example of such conditions is

2.5 What are single precision floating point numbers?

2.6 What is the error information generated by algorithms?

2.7 Binary to hexadecimal conversion for algorithms

Binary to Hexadecimal Conversion

Byte = 8 bits, Integer = 16 bits

Binary: 0101 0011 1100 0110 0101001111000110B

What is track ing? ........................................................................................................ 9

3.1 What is tracking?

Tracking should be turned off for the following situations:

Tracking can be blocked in the following ways:

3.2 What is the purpose of trackin g?

There are two purposes for tracking:

3.3 What is the tracking process?

3.4 What are the best practices for using tracking?

Refer to the following guidelines when using tracking:

 Reset Windup limiting is performed by tracking algorithms if:

3.5 What algorithms support tracking?

Tracking algorithm summary

A L G O R I TH M TRAT TOUT TRK1 TRK2 TRK3 TRK4 AC C E P T C AS C AD E

A L G O R I TH M TRAT TOUT TRK1 TRK2 TRK3 TRK4 AC C E P T C AS C AD E

1 Through S (setpoint) pin

3 Supports switchable slewing and s witchable tracking

4 Ramps supported on both TRR1 and TRR2 pins

3.6 Tracking examples

Tracking: Mode Transition

Tracking: SUM Algorithm

Tracking: PID Algorithm

Tracking: Reset Windup

Tracking: Anti-Reset Windup

3.7 Setting tracking signals for algorithms

What are algorit hm classification groups? ................................................................... 20

4.1 What are algorithm classificat ion groups?

 Alarm manipulation algorithms (see page 21).

4.2 Alarm Manipulation algorithms

Alarm manipulation algorithms have the following uses: